ModuleNotFoundError: No module named 'PyQt5.sip'

Fresh Ubuntu 18.04 install...
Fresh electron-cash checkout and build...
Trying to start app throws this error:

Traceback (most recent call last):
File "./electron-cash", line 391, in
d.init_gui(config, plugins)
File "/home/mschoenebeck/dev/crypto/bch/Electron Cash-3.3.1/lib/daemon.py", line 303, in init_gui
gui = import('electroncash_gui.' + gui_name, fromlist=['electroncash_gui'])
File "/home/mschoenebeck/dev/crypto/bch/Electron Cash-3.3.1/gui/qt/init.py", line 36, in
from PyQt5.QtGui import *
ModuleNotFoundError: No module named 'PyQt5.sip'

Why? Do I really need to downgrade my system again to run electron anymore?

Do you have PyQt5 installed?  pip install pyqt5?  Or apt-get pyqt5?

Hey! Thanks for your help. And sorry for late reply..
I have:
python3-pyqt5 is already the newest version (5.10.1+dfsg-1ubuntu2).
Since electron uses python3 that's correct, right?

Hmm.. yeah that's all correct.  Let me see if I can reproduce this...

Hmm.  Can you try pip3 install PyQt5-sip?  Maybe that'll do it..

I installed the missing package.
pip3 install PyQt5-sip
Collecting PyQt5-sip
  Downloading https://files.pythonhosted.org/packages/d7/db/06ad1f62a1f80a5df639c322066f03db381c1a6322c02087e75092427838/PyQt5_sip-4.19.12-cp36-cp36m-manylinux1_x86_64.whl (66kB)
    100% |████████████████████████████████| 71kB 1.1MB/s
Installing collected packages: PyQt5-sip
Successfully installed PyQt5-sip-4.19.12

But the problem persists. Do I need to reference the package somehow? All these different python versions and pip-stuff really confuses me..

./electron-cash
Traceback (most recent call last):
  File "./electron-cash", line 391, in <module>
    d.init_gui(config, plugins)
  File "/home/mschoenebeck/dev/crypto/bch/Electron Cash-3.3.1/lib/daemon.py", line 303, in init_gui
    gui = __import__('electroncash_gui.' + gui_name, fromlist=['electroncash_gui'])
  File "/home/mschoenebeck/dev/crypto/bch/Electron Cash-3.3.1/gui/qt/__init__.py", line 36, in <module>
    from PyQt5.QtGui import *
ModuleNotFoundError: No module named 'PyQt5.sip'

Honestly I have no idea.  It should "just work".  I don't have Ubuntu 18.  I am on 17.  It works here.
I'm really sorry this is not working.  Perhaps someone else that actually uses Linux daily can chime in (I used to be a Linux geek but I've moved onto macOS these days).
You can maybe try the linux flat pack: https://github.com/fyookball/electrum/issues/825

Thank you very much. I'm also very confused and a little disappointed from Ubuntu 18.04. I always wait some time until I switch to new LTS because of stuff like this.
I will try further and let you guys know! Thanks again.

FYI I just upgraded to Ubuntu 18.04 and it still works fine.
I am not sure what the issue is for you.
In case you were wondering, here is a list of all the python 3.6.5 module I have installed (listed via pip3 list).  I hope you have PyQt5 in there...!
python365_modules.txt

Same error for me. Using Mint 19, based off Ubuntu 18.04. The same error appears to be mentioned here:
https://aur.archlinux.org/packages/electron-cash/
I tried running those 2 lines
sudo pip3 uninstall PyQt5_sip
pip3 install --user PyQt5_sip

but it still does not work.

what happens if you blow away (or rename) ~/.local, then reinstall the dependencies for electron cash?

I am confused too!  And yes, I don't have SIP installed.. and it just works.
Hmm.  I noticed you have Electron Cash installed!  Maybe that's conflicting with running from source?  I had problems with that in the past!
Try:
pip3 uninstall Electron-Cash

what happens if you blow away (or rename) ~/.local, then reinstall the dependencies for electron cash?

I renamed the ".local" folder but it didn't have any effect.

Also try it as root too: sudo -H pip3 uninstall Electron-Cash

I removed Electron-Cash with sudo -H pip3 uninstall Electron-Cash and it did work.
However, the problem persists. Just to let you know: I built all Electrum clients from source (BTC, BCH, DASH, LTC) and all worked well on Ubuntu 16.04. I recently made the upgrade to 18.04 and from that point in time I have this "sip"-module error. So I never had trouble with electrum clients being installed all together on one machine.

Yeah sorry about that.  I really don't know what's going on there.

I only have one version of Electron Cash installed. I installed it via python3 setup.py install. I do however have Electrum installed as well. Is it possible that the Electrum installation is conflicting?
thanks,

I am on Mint 19. For what it's worth, I had some odd QT errors on Mint 18.1 after installing electron cash. Since then I always avoid installing. I just untar and run from ./electron-cash or ./run_electrum. It seems likely that Electrum and Electron installations could have silent naming conflicts if they are installed.
Some relevant pip freeze content from me (I think the same as yours):
PyQt5==5.11.2
PyQt5-sip==4.19.12

I never had to explicitly install PyQt5-sip. Something else did that.
Some packages that I have installed through apt rather than pip:
pyqt5-dev-tools
python3-pyqt5

If you are familiar with environment management systems, you could try setting up a new environment to avoid conflicts with requirements for other systems. If you don't know how, I could walk you through it if you ping me on the Electron-Cash slack.

I made a fresh python 3.7 environment with only ipython and requirements installed.
from ~/Electron Cash-3.4.1/ (same behavior on version 3.3.1)

./electron-cash

Error: Could not import PyQt5 on Linux systems, you may try 'sudo apt-get install python3-pyqt5'

pip install pyqt5

You may need sudo if you are installing on the OS python.
That installs both PyQt5-sip-4.19.12 and pyqt5-5.11.2.
If you have problems with that, maybe try:

sudo apt-get install pyqt5-dev-tools python3-pyqt5
pip install --upgrade pyqt5

./electron-cash

Works for me!
Note: If you want to use hardware wallets, there are some additional non-obvious installations you need to do.

Again based on my experience, I recommend not using setup.py install, especially if you are going to use both Electron and Electrum.


Issue with the 'ts' task in gulpfile

I excluded the 'ts' task from the default gulp task, it was breaking the build: https://github.com/limonte/sweetalert2/commit/77c6f65f3993a19c792bb58389b6578d1710f2d3

@toverux is that okay?

@toverux the issue is reproducible right now, it seems that gulp-typescript is going all the recursive way into node_modules which is slow and wrong.

Strange! I can't reproduce (even after reinstalling all the devdeps) :/
What surprises me the most is that the task explores that /home/limon/node_modules directory (the paths in red). What's that directory exactly?

What surprises me the most is that the task explores that /home/limon/node_modules directory (the paths in red). What's that directory exactly?

Good catch! That's the node_modules folder inside my home folder. It's strange that it causes errors, but anyways, reverted

Hm, I think that this is due to how Node-style module resolution works in general.
Found this in TS docs:

Node will look for your modules in special folders named node_modules. A node_modules folder can be on the same level as the current file, or higher up in the directory chain. Node will walk up the directory chain, looking through each node_modules until it finds the module you tried to load.

Node resolution doesn't magically know where your project root is. That' why it traverses the filesystem from the file to the root. I think that TS does the same thing here for some reason, so - it's likely a normal behaviour.

Thanks @toverux!


Add Harrison Shoebridge to the team page

90% sure this is the final step of my (rather prolonged) onboarding process.
If @zachlatta has a better photo of me somewhere, I'd be OK with using that.

@zachlatta: Assigning you to merge/reivew.


♻ Left shift could be replaced by mul

https://github.com/artgobblers/art-gobblers/blob/c821b6d48f836ccf5d152c75584bb9792bba774f/src/ArtGobblers.sol#L844

closing as hopefully someone reports this via c4


CaaS subdomain validation in UI is incorrect

Description - What happened? *
The subdomain field should validate for following regular expression
[a-z\\d]+([-_][a-z\\d]+){0,10}
Min. length: 6
Max. length: 23
Expected Behavior *
.
Observed Behavior *
.
Steps to Reproduce
No response
Context Information
No response
Relevant log output
No response
Screenshots
No response

False alarm


Tensorflow

Tensorflow audio commands recognition as shown here: https://www.tensorflow.org/versions/master/tutorials/audio_recognition
Model and Label file can be downloaded here: http://download.tensorflow.org/models/speech_commands_v0.01.zip
An example can be like this:
import speech_recognition as sr
r = sr.Recognizer()
m = sr.Microphone()
def callback(recognizer, audio):
try:
spoken = recognizer.recognize_tensorflow(audio, tensor_graph='speech_recognition/tensorflow-data/conv_actions_frozen.pb', tensor_label='speech_recognition/tensorflow-data/conv_actions_labels.txt')
print(spoken)
with m as source:
r.adjust_for_ambient_noise(source)
stop_listening = r.listen_in_background(m, callback, phrase_time_limit=1)

Hi @chriamue,
Looks good to me! If you're done with this PR, I'd be happy to merge it. I did notice you also have a deepspeech branch, so if you'd rather merge that one, just let me know.

I cannot fix following error, because without this import the given graph can not been used.
$ flake8 --ignore=E501,E701 speech_recognition tests examples setup.py
speech_recognition/init.py:1234:13: F401 'tensorflow.contrib.framework.python.ops.audio_ops as contrib_audio' imported but unused

You can merge now. The needed tensorflow import depends on the model. So the user has to import
it himself, like in the tensorflow commands example.

LGTM :+1:


Stop using DEFAULT node definition

NOTE: Port of approved PR https://github.com/GoogleCloudPlatform/slurm-gcp/pull/170
# BEFORE
NodeName=DEFAULT State=UNKNOWN RealMemory=1351440 Boards=1 SocketsPerBoard=1 CoresPerSocket=48 ThreadsPerCore=1 CPUs=48
NodeName=cluster-ns-[0-3] State=CLOUD Gres=gpu:8
NodeSet=ns Nodes=cluster-ns-[0-3]
# AFTER
NodeName=cluster-ns-[0-3] State=CLOUD Gres=gpu:8 RealMemory=1351440 Boards=1 SocketsPerBoard=1 CoresPerSocket=48 ThreadsPerCore=1 CPUs=48
NodeSet=ns Nodes=cluster-ns-[0-3]

Also:

Add license to test files;
Move "common" test utils in one file;
Add test coverage to touched code.

Can you verify that this change has been tested against the examples/hpc-enterprise-slurm.yaml blueprint in the HPC Toolkit?

In progress


Unable to turn nat off once enabled

Doing a initenv-tui, you cannot turn off nat.  You can only select the 3 types of nat.
running cbsd natoff results in just stopping nat, but does not disable nat from being configured and starting back up when cbsdd is restarted or on system boot.
The only way I found to be able to disable nat once it's been enabled is doing a:
cbsdsql local update local set nat_enable='0'
then rebooting machine.

Thank you. Good idea, I'll add a "nat off" option soon.

"Disable" option added via https://github.com/olevole/cbsd/commit/2c32c3f450c8cd144b74bd250aca18768a8c9378


Node Activities & Messages

Design and implement the  node's activities according to the paper

Dev steps

[x]  a simple process without faults handling
[x] thinking again, and then elaborating the design
[ ] a full process in a static network (no latency, no join/leave, no dynamic selection of collector & witness)
[ ] a full process in a dynamic network

In this dev phase, We should take off the dynamic  & collaboration parts, and make a single node network, in which all the collect -> witness -> mint process are doing by this node.
By this means we could efficiently build up the fundamental blocking building code.

In the developing of W3Node, we should separate of concerns, separate logics in the Two-Stages-Mint(TSM) activities apart from logics in the collaboration among nodes in the W3Network.
That means each time we change the TSM logic, we can test it under the singleNodeMode, and then the full network mode.
This kind of separation will make our dev life easier and happier :)

We need to sync collectors, they may have different local-facts at AFW.


Write/Link methods

Write/Link methods
The purpose of this proposal to make more public and more explicit two already internally implemented functions in worker (under different names). They serves to mapping data instances to file system. The proposed concepts are:

linking - Linking a data object to file system creates read-only representation on filesystem. If data instance already lays on the file system in workdir it actually creates a symlink to these data.
writing - Creates a stand-alone copy of data on the file system that has no further connection with the data instance and can be freely modified.

(1) Note that linking may silently fallback to writing, for example when we have only in-memory representation of a data object.
(2) Note that in upcomming directory support, it is expect that linking/writing "dir" data object creates directory representation on filesystem.
Write/Link in @remote
I propose to implement two new methods on data instance: link and write. They should behave as described above.
@remote()
def my_remote(ctx, data):
    data.write("mydata")  # creates stand-alone copy of data instance into file "mydata"
    data.link("mydata2")  # creates a read-only copy of data instance (may possibily create a symlink)

Write/Link in tasks.execute()
I propose to add a new parameter write for class Input. When set to True, it forces write operation when data object is mapped to the file system.
tasks.execute(["/some/binary", Input("mydata", write=True, dataobj=x)])

When write is False, then link operation is used (this is behaviour in the current version).

Fully implemented in #16


Documentation site anchor links broken

All the anchor links on the doc site link to the homepage and not the current page.
Eg, on https://facebook.github.io/react-native/docs/network.html the link to WebSockets goes to https://facebook.github.io/react-native/#websocket instead of https://facebook.github.io/react-native/docs/network.html#websocket as you'd expect.
It seems the <base> tag is causing the links to go to the homepage instead of the current page. Here is a SO article on the issue: http://stackoverflow.com/questions/8108836/make-anchor-links-refer-to-the-current-page-when-using-base

I think the issue is missing docs/ prefix - we had few PR's adding them recently, so that might be the way to go. Not all pages have it though, so I think for better clarity it's just better to just leave the base.
However, I cannot see a broken link to WebSockets on the page you've linked (in fact - I can't see any link on that page), so would appreciate if you can share some examples (and ideally - send over a PR).
See this for reference:  #6173

It appears it was fixed in the last day or so. I verified the issue on multiple pages of the docs site, so it wasn't an isolated incident but glad it's fixed!


Bug: Adaptor is not pathmapping the output path.

Expected Behaviour
When using job attachments or when specifying a custom output path, the adaptor should overwrite any settings saved in the scene file. When using job attachments, the output path should be somewhere in the assetroot directory in the openjd session folder. When a custom output path and storage profile are used, the custom output path should be used.
Current Behaviour
The render will always export to the path defined in the render settings.
Reproduction Steps
Create a new scene. Define an output path that is accessible by your render job user in your render settings. Save your scene.
Bring up the submitter and change the output directory or submit to a queue that uses job attachments.
After the render completes, DCM will report no output files to download and your output will appear in the original output directory defined in the render settings.
Code Snippet
n/a

It looks like the adaptor isn't setting the path at all.
These couple of lines set the frame range of the render by editing the render data: https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/blob/9f3813c65451f073cea4d256817dd2f927b906c0/src/deadline/cinema4d_adaptor/Cinema4DClient/cinema4d_handler.py#L42C1-L44C50
To edit the path, you'd just edit the RDATA_PATH key in the render data. Docs on RDATA_PATH here: https://developers.maxon.net/docs/py/2024_2_0/modules/c4d.documents/RenderData/index.html#c4d.documents.RenderData

Confirmed that adding a line like
self.render_data[c4d.RDATA_PATH] = "C:/some/random/path/output_filename"
Added to the section I linked in my last message successfully redirects the output. I'd make a PR, but I don't know how to extract the pathmapped output directory from the openjd description.

This is partially resolved by https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/pull/57
However, that's a quick fix to get the existing output paths in the scene path mapped. The longer term solution is for us to pass along the output directory and multipass directory through to the adaptor such that users can override the path from the submitter without being forced to save it in the scene file.

To do the actual fix, we'll need to:

Add the options to the submitter. Not sure how we want to present the multipass path. Optional checkbox to enable to match how C4D does it?

load from scene: https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/blob/mainline/src/deadline/cinema4d_submitter/cinema4d_render_submitter.py#L247
add to UI: https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/blob/mainline/src/deadline/cinema4d_submitter/ui/components/scene_settings_tab.py#L99-L100

Add job parameters for output path and multipass output:

https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/blob/mainline/src/deadline/cinema4d_submitter/adaptor_cinema4d_job_template.yaml#L20-L27

Add output and multipass output to the adaptor interface

schema: https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/blob/mainline/src/deadline/cinema4d_adaptor/Cinema4DAdaptor/schemas/init_data.schema.json
first actions: https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/blob/mainline/src/deadline/cinema4d_adaptor/Cinema4DAdaptor/adaptor.py#L29
create functions to set the output/multipass output and add to action dict: https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/blob/mainline/src/deadline/cinema4d_adaptor/Cinema4DClient/cinema4d_handler.py#L27-L32

Add job parameters to the init_data.yml

https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/blob/mainline/src/deadline/cinema4d_submitter/adaptor_cinema4d_job_template.yaml#L40-L45

Resolving this issue as the PR with the fix has been merged!


Update docstring for tf.setBackend() re disposing the old backend.

fixes tensorflow/tfjs#277

This change is

Review status: 0 of 1 files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


feat(validation-result)!: bump to go-oscal v0.6.0 jsonschema v6 update

feat(validation-result)!: remove validation-result in favor of new go…
chore(go-oscal): update w/ go-oscal jsonschema v6 changes

Description

[X] Update go-oscal to v0.6.0.
[X] replace duplicated validate logic with go-oscal library methods.
[x] update references to jsonschema

Related Issue
https://github.com/defenseunicorns/go-oscal/pull/282
#584
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Other (security config, docs update, etc)

Checklist before merging

[x] Test, docs, adr added or updated as needed
[ ] Schema Updates applied
[ ] Contributor Guide Steps followed

were those whitespaces there on purpose to validate linting in the case where it's one big wrapped yaml string?

were those whitespaces there on purpose to validate linting in the case where it's one big wrapped yaml string?

in the component-definition  test file where the trailing whitespace was removed? I think that may have just been my linter.


Create CODE_OF_CONDUCT.md

Codecov Report

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

@@           Coverage Diff           @@
##           master       #3   +/-   ##
=======================================
  Coverage   84.14%   84.14%
=======================================
  Files           4        4
  Lines         227      227
=======================================
  Hits          191      191
  Misses         36       36

Continue to review full report at Codecov.

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


Amazon Version <IP_ADDRESS> not supported

As the title says.
Are there different version <IP_ADDRESS> ?

Is this a questing? I haven't tested the Amazon version as I only have access to the Play Store version. If you have access to it and it's not working could you provide more details?

Sure, what exact information do you need?

Is there any error message, does it crash? In general what happens when you try to run it.

That it's an "unsupported version".
I can share the <IP_ADDRESS> version of Amazon if needed with you.

Ok, I see. Could you DM me on Discord?


Fix create button flickering after component detection

Fixes

https://issues.redhat.com/browse/RHTAPBUGS-583

Description

isValidating gets updated multiple times as soon as detected components are added to formik values. We don't need to disable the submit button while validating because there's no async validation happening on the form.

Type of change

[x] Bugfix

Screen shots / Gifs for design review

Before ---
https://github.com/openshift/hac-dev/assets/6041994/01b19de9-2752-4b4d-946d-91aa57825de5
After ---
https://github.com/openshift/hac-dev/assets/6041994/9cd9ffb5-34c9-48a3-944c-cb1b62fce833
Browser conformance:

[x] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

/retest


HDDS-3400. Extract test utilities to separate module

What changes were proposed in this pull request?
Create hadoop-hdds/test-utils module for test utilities (eg. GenericTestUtils and LambdaTestUtils).  This should not depend on any other HDDS/Ozone modules: the goal is to be able to use test listeners defined in this module (currently only TimedOutTestsListener) in all other modules.
https://issues.apache.org/jira/browse/HDDS-3400
How was this patch tested?
CI:
https://github.com/adoroszlai/hadoop-ozone/runs/592403416
Applied the addition of listener from #813, verified that no ClassNotFoundException happens.

Thanks @elek for reviewing and committing it.


Fix getColumnType determination logic

The alpha sort wasn't behaving as expected, identifying alpha column content as a numeric value. Validates the entire column for column type, as opposed to the first non-null cell.

Thanks @stevenorell. We elected to go a different wrote and allow types both to be customized and specified directly by a data- attribute on the th. An update to the docs will be coming shortly, but in the meantime, please check out https://github.com/HubSpot/sortable/commit/cab1613b721e7a7512417ded8fb62d163c647777 for more information. Thanks again!

Docs have just been updated: http://github.hubspot.com/sortable/api/options/.


✅

✅

[ ] ```

Originally posted by @Bdrake317 in https://github.com/devcontainers/images/pull/1229#discussion_r1889614574

这是来自QQ邮箱的自动回复邮件。您的邮件，我已经收到，O(∩_∩)O谢谢


Correct the output remoteUrl of action publish:azure

Signed-off-by: Trong Tran<EMAIL_ADDRESS>Hey, I just made a Pull Request!
This PR fix this issue: https://github.com/backstage/backstage/issues/13657
:heavy_check_mark: Checklist

[ ] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thank you! 👍
Could you add a changeset as well? It also looks like the tests need updating

Thank you! 👍
Could you add a changeset as well? It also looks like the tests need updating

Sure


Call native autocomplete

TabNine very useful, but sometimes I want to ask IDE about intelligence smart request. How can I do it?

This behaviour is not interfered as far as I know & tested. If you come across bugs in this area, please let us know. Thanks!


Switch back to qmake

Unfortunately, I have run into what appears to be an insurmountable wall with CMake. No matter how hard I have tried, I cannot find a way to properly get post-build commands to run in the correct sequence. Therefore I am switching NitroShare back to qmake. This is not a decision that I have made lightly, however, it is one that must be made.
qmake will still allow virtually all of the current behavior to be duplicated, perhaps even simplified. Once I have finished with another bug that I am currently working on, I will begin the transition.

As of commit c3537d3, this has now been completed.


Can user-defined types be returned by value from non-static member functions?

"User-defined types can be returned by value from global functions and static member functions. "

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

ID: a87b11e0-0214-175b-0926-0f8a4653e444
Version Independent ID: 43e8bf4a-9a0d-ea28-d432-ead828604d5e
Content: x64 calling convention
Content Source: docs/build/x64-calling-convention.md
Product: visual-cpp
Technology: cpp-tools
GitHub Login: @corob-msft
Microsoft Alias: corob

@scyclzy
Yes, but perhaps not efficiently in a register. For non-POD types too large to fit in a register, your caller has to allocate space for the return value and pass a pointer to this location as the first parameter. The C++ compiler does this behind the scenes on your behalf, but you need to know what's going on "under the hood" if you want to interface compiled code with x64 assembly.

Maybe I should say, "for any type too large to fit in a register" above.


New release of AKS Engine v0.63.0

We have a new version of AKS Engine v0.63.0. there are only new K8s version, not new features. We need to apply the following changes to the release notes:

In table "AKS engine and Azure Stack version mapping" add a new row mapping ASH version 2102 to AKSe versions 0.60.1 and 0.63.0

In table "Kubernetes version upgrade path in AKS engine v0.60.1" change:
a. change the title to reference v0.63.0 instead of v0.63.0
b. add new 3 rows to the table to map each of these (one per line): 1.18.15 to 1.18.18, 1.18.18 to 1.19.10, and 1.19.10 to 1.20.6

In table "AKS engine and corresponding image mapping" add a new row with the following information:

v0.63.0 | AKS Base Ubuntu 18.04-LTS Image Distro, 2021 Q2 (2021.05.24), AKS Base Windows Image (17763.1935.210520) | 1.18.18, 1.19.10, 1.20.6 | API Model Samples (Linux, Windows)
Each of the items in the table have links:
v0.63.0 = https://github.com/Azure/aks-engine/releases/tag/v0.63.0
AKS Base Ubuntu 18.04-LTS Image Distro, 2021 Q2 (2021.05.24) = https://github.com/Azure/aks-engine/blob/v0.63.0/vhd/release-notes/aks-engine-ubuntu-1804/aks-engine-ubuntu-1804-202007_2021.05.24.txt
AKS Base Windows Image (17763.1935.210520) = https://github.com/Azure/aks-engine/blob/v0.63.0/vhd/release-notes/aks-windows/2109-datacenter-core-smalldisk-17763.1935.210520.txt
Linux = https://github.com/Azure/aks-engine/blob/v0.63.0/examples/azure-stack/kubernetes-azurestack.json
Windows = https://github.com/Azure/aks-engine/blob/v0.63.0/examples/azure-stack/kubernetes-windows.json

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

ID: e69382e4-c307-4dfe-9885-92d2436ef858
Version Independent ID: 135ea653-550b-039d-121c-95f2e7c93f10
Content: Release notes for Azure Kubernetes Service (AKS) engine on Azure Stack Hub - Azure Stack Hub
Content Source: azure-stack/user/kubernetes-aks-engine-release-notes.md
Service: azure-stack
Sub-service: azure-stack-hub
GitHub Login: @mattbriggs
Microsoft Alias: mabrigg

@walterov Thanks Walter
#in-progress

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

Updated.
#please-close


Adjust function focusLast, "end key" now goes to last result(resolves #21096).

Goodmorning,
To resolve #21096 , I adjusted the function focusLast in src\vs\base\parts\tree\browser\treeImpl.ts.
The problem was that only the last element was retrieved, but never checked if that element has any children, so in case the last element is a folder it would focus the folder instead of the files it contains.
Note that I created a while loop to check for children, since multiple folders could be nested.
Since I'm not familiar with the treeImpl.ts, please let me know if anything needs to be adjusted.

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

Good evening @joaomoreno ,
I saw my pull request is still open. Are there any changes which need to be made? If so, please let me know! Thanks in advance!

The real bug was in the tree navigator, so I just made the change there directly: eae373999
Thanks for the help!


[cli-plugin-pwa] - Splash screen is not displayed on Safari

Version
3.1.1
Reproduction link
http://test-dev-gyhi.s3-website-eu-west-1.amazonaws.com/
Node and OS info
Node 8.12.0 / NPM 6.2.0
Steps to reproduce
I've created

a new vue project thanks to vue-cli 3.
select PWA support in the CLI options
and add assets and meta tag for Apple ios support

you can clone this Repo: https://github.com/cde06/splashscreen-vue-cli3-pwa
or direct access to my demo: http://test-dev-gyhi.s3-website-eu-west-1.amazonaws.com/
Then deploy the webapp on your favorite host, and open it on iphone iOS safari browser.

Add your PWA shortcut to your home screen.
Open your PWA webapp from the icon just created.

=> You will receive a white screen during the loading of the webapp instead of the branded assets ref in the index.html file.
What is expected?
I expect that the PWA webapp from my home screen can launch a splash screen like a native mobile app.
Like it's successfully done in this example:
https://medium.com/@applification/progressive-web-app-splash-screens-80340b45d210
This is a static example that work with a splash screen. (So Safari browser from iOS correctly support this feature)
What is actually happening?
We have a white screen during the loading of my webapp instead of our branded screen.

You might chalk this up to a Safari issue. Configuring splash screens for Safari is somewhat of a huge pain since Safari requires the exact specific device resolution for every splash screen, otherwise it will return a blank white screen. Considering the fact that new iOS devices are released each year, each with different resolutions, this quickly becomes difficult to manage. Other have gone into more detail on this here and here.
Thankfully, the Chrome team has made this easier by creating PWA Compat. Just include PWA Compat in your index, as well as a manifest file, and this will configure icons properly.

It looks like you might need to make sure and add an apple-touch-icon tag, as well as making sure to add all images to your manifest.

I'm also facing this issue as of today.
I tried PWA Compat, it did helped to create ios splash screen based on theme color, app icons and name, but is not the image i put in public/index.html
Has anyone got the solution?
Version
@vue/cli-service: 3.4.1
vue: 2.6.8
nodejs: 10.15.1
npm: 6.9.0

If you're using PWACompat, you need to set up a manifest file that points to two images, one that's 192x192 and one that's 512x512, and it should work. At least it works for me. Something like this:
{   "name": "Aspen Valley Company",   "short_name": "AVHC",   "icons": [     {       "src": "/img/icons/192x192.png",       "sizes": "192x192",       "type": "image/png"     },     {       "src": "/img/icons/512x512.png",       "sizes": "512x512",       "type": "image/png"     }   ],   "start_url": "/",   "display": "standalone",   "background_color": "#ffffff",   "theme_color": "#004D40" }

Yea i got that working, what i needed is custom ios "apple-touch-startup-image".

For people who run in this issue:
I use generated splash screens for iOS (https://itnext.io/pwa-splash-screen-and-icon-generator-a74ebb8a130). I found that you need to declare <meta name="apple-mobile-web-app-capable" content="yes" /> in front of this, otherwise they don't show up.
Problem with Vue PWA is that it adds this meta-tag double (because it's also added by appleMobileWebAppCapable: "yes",).
See also https://github.com/vuejs/vue-cli/issues/3269


Ensure factory() helper is gone in Laravel 8+

⚠ Includes 🍒 from #181.

@mr-feek This PR is ready to be merged now.
Afterwards I will rebase #157, because that PR also contains feature: support stubs per major version. This PR has a smaller scope, so I think it's better to add that feature here (#182).

thanks!


Don't rebuild typings folder after install

Until we find an elegant way to manage custom typings, we're going to
avoid deleting this folder.

:shipit:


[Feature Request]: Adding Dark Mode Toggle

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
I’d love to see a dark mode toggle added to the site! It would be a great addition and compliment your website, especially for users who prefer darker themes or browse in low-light environments.
Use Case
What I’m Thinking:
-There could be a toggle switch in the header that lets users easily switch between light and dark modes.
-When dark mode is turned on, any content that’s currently in black (or other dark colors) would automatically switch to lighter colors (like white or light gray) to keep everything readable and looking good.
-I will make sure all text, buttons, icons, and other interactive elements still pop and are easy to interact with in both modes.
Benefits
Why This Would Be Awesome:
-It’ll improve accessibility for users who prefer dark mode or browse at night.
-Plus, it’s a cool, modern feature that users expect from sites nowadays
Add ScreenShots
No response
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

Kindly assign this issue to me with the appropriate label. @manikumarreddyu

hey this feature this super cool...kindly assign me as well @manikumarreddyu

hi @sumitkumar9128 please make sure to use dark property in tailwindcss..

hi @AnushkaS77 first of all thank you for showing interest in this project..
according to rules of GSSOC ..the issues are assigned like first come..first serve..the admins must follow this rule..
i hope you got my point and also..in mean time you can create new issues in agrotech ai with some cool ideas and innovative thoughts..
thank you @AnushkaS77
all the best...

Thank you so much @manikumarreddyu
I will take care of dark mode according to your need

can you please let me know how much time do you need to complete this issue @sumitkumar9128

Hi @manikumarreddyu ,
I wanted to provide a quick update regarding the dark mode feature. Implementing the feature itself isn't an issue; however, the main challenge I'm facing right now is cloning the repository to my local machine. I'm actively troubleshooting this, and once resolved, I'll proceed with the changes quickly.

I appreciate your understanding, and I'll keep you posted as I work through this.


original port should not be ignored (fusionauth-issues/issues/2250)

Summary
original port should not be ignored (https://github.com/FusionAuth/fusionauth-issues/issues/2250)
Steps to reproduce
Start docker image with port mapping 2222:9011
--- docker-compose.yml ---
services:
fusionauth:
image: fusionauth/fusionauth-app:1.45.2
ports:
- 2222:9011
--- docker-compose.yml ---
Configure "Google Identity Provider" (possibly any other provider)
Goto URL http://loalhost:2222/admin
Click on "Google Identity Provider" button to log in
Login fails because of wrong redirect_uri:
redirect_uri=http://localhost:9011/oauth2/callback
Expected redirect_uri:
redirect_uri=http://localhost:2222/oauth2/callback
Change in PR
Change is tested with version 1.45.2 by replacing just one java class (HTTPRequest) in docker image using the following technique:
Dockerfile
FROM fusionauth/fusionauth-app:1.45.2
USER root
RUN apt update && apt install unzip zip
USER fusionauth
WORKDIR /usr/local/fusionauth/fusionauth-app/lib
COPY --chown=fusionauth ./build/ ./build/
RUN unzip ./java-http-0.1.13.jar -d unzipped
RUN cp ./build/classes/io/fusionauth/http/server/HTTPRequest.class ./unzipped/io/fusionauth/http/server/HTTPRequest.class
RUN (cd ./unzipped ; zip -u ../java-http-0.1.13.jar)
RUN rm -rf ./build ./unzipped

@voidmain thoughts on this one?

Left some comments. This looks good in principle. It just needs some cleanup and some defensive coding.


Changelog Fix - 'import_dangerfile' entry previously added to release instead of master #trivial

Previous PR had the 'import_dangerfile' Changelog.md entry added to 3.4.0 version instead of master.

No problem, you're welcome to merge on green. I added #trivial because it makes danger not complain about no changelog changes, though - you have a changelog change - so it was useless, but now you know.

          1 Message

  :book:
  @felipesabino is not a contributor yet, would you like to join the Danger org?

  Generated by :no_entry_sign: danger

@orta ok, thanks!
Oh, and about

@felipesabino is not a contributor yet, would you like to join the Danger org?

Any idea if this is related to #128 ?

NP, you're not publicly an org member, so you don't show as one to the bot - which has no access, I wonder if I can add the bot but give no repos - I'll try

Nah, can't give the bot access to the org, without giving access to all the repos without having to do a bunch of GitHub faffing

Oh, got it! And I forgot about the org profile visibility thing, just changed mine to public then, no worries. Thanks


Optimizating ForInObjectEnumerator overhead

The overhead for ForInObjectEnumerator can become significant if we enumerate a lot of object with small number of properties.
This change improves Sunspider by about 3.5ms (or 1.6%) and Speedometer by about 60ms (or 0.6%) on my machine.
No change on Octane or Kraken.

Allocate ForInObjectEnumerator on the stack instead of dynamically

Keep track of the maximum for..in loop depth at byte code generation.
Change the for..in byte code to InitForInEnumerator and BrOnEmpty to refer to the for..in loop depth
Allocate stack space for the ForInObjectEnumerator for interpreter and JIT'ed code.
When bailing out of JIT'ed code, the bailout interpreter frame will not allocate new stack space for the ForInObjectEnumerator, but instead reuse the space allocated on the JIT'ed frame.
When we are in JIT loop body, it also won't allocate new ForInObjectEnumerator. the loop body code will instead refer to the ForInObjectEnumerator allocated in the interpreter frame.
In JIT inlining, we need to keep track of inlinee for..in loop depth as well to allocate enough space for all of them.

Reduce the size of ForInObjectEnumerator

Remove scriptContext and flags fields in ForInObjectEnumerator by reusing the same fields in DynamicObjectPropertyEnumerator and always initializing those.
Move all the fields needed to keep track of properties shadowing in prototypes into a dynamically allocated structure.  We already needed to allocate the sparse bit vector before already, so this is not a new allocation, but it will minimize stack usage for cases that doesn't have enumerable properties on the prototype.

Add inline cache that maps the object type to DynamicObjectPropertyEnumerator::CacheData on InitForInEnumerator

The cache is pass to all GetEnumerator API to be given to DynamicObjectPropertyEnumerator to avoid the dictionary look up
Since we clear the type to cache data map on every GC, we also clear the inline cache on every GC as well.

Implemented JIT fast path for OP_InitForInEnumerator and improved JIT fast path for BrOnEmpty

Implemented the OP_InitForInEnumerator when we have an inline cache match, with a plain dynamic object, doesn't have enumerable property on the prototype and doesn't index properties (object array)
Instead of checking multiple conditions, initialize a single bool on ForInObjectEnumerator canUseJITFastPath to indicate whether we can use the fast path, that combines the check for no prefix/array enumerator, no enumerable property on the prototype and have cache data
Avoid going to the helper before we exit the loop by adding a loop exit check for whether the cache is complete at the end of the enumeration
If prototype doesn't have any enumerable property, we don't have to keep track of shadowing.  So just ask the object enumerator to return enumerable property only, so that the for in object enumerator and the jit fast path doesn't have to check whether the property is enumerable or not.

Minor cleanup

Delete JavascriptEnumeratorIterator, which is no longer used.
Refactor code in the backend to add loop in lower

Tab Check failure is attributed to @LouisLaf. @Penguinwizzard is already fixing it in https://github.com/Microsoft/ChakraCore/pull/1636. If that is merged in first and then this PR is rebased the problem will be resolved.

Said tab check failure fix is now merged in.

@curtisman , done looking at the changes. Let me know what you think of the comments/questions

nit: Title of PR / Commit message "optimizating" -> "optimizing"

:shipit:

@dotnet-bot test Ubuntu ubuntu_linux_debug_static

@dotnet-bot Ubuntu ubuntu_linux_test

@dotnet-bot test Ubuntu ubuntu_linux_test

@dotnet-bot test Ubuntu ubuntu_linux_test_static


comparison of performance? like Accuracy

Is there any plan to provide a comparison of model performance besides efficiency?

Meaningful issue.
I have same question.
And I think, the performance(likes accuracy) of algorihtm is heavyly based on the task.
E.g.  I tested (a few compositions) the function fitting by CKAN and MLP, same parametes number, the performance of MLP is worse than KAN's.

There are other repositories for that, like: https://github.com/yu-rp/kanbefair. And research has already been done on that side. The conclusion is that KANs underperform in typical deep learning tasks like computer vision and natural language processing but outperform on other tasks like symbolic learning. It seems a good discovery for interpretabitily research but not much for performance research.

@Jerry-Master are there ways to see which version of KAN is the best for some of the major ML benchmarks for table (regression or classification)? There are some cases where there is a need for proxy similar to picking sub-columns of a table and creating mathematical equations, instead of CV and NLP where the data is more "rich".

I would say try? There is no way of knowing for sure before trying. As far as I am concerned, there is no rigorous analysis on the effect of KAN for tabular data. And I would say that is true for any other deep learning methodology. Tabular data is normally private and public benchmarks are not representative of the real world. In my experience, you have to try and every time is different.


Discriminate doc comments from single line comments

It would be helpful to discriminate doc comments (///) from single line comments (//). Currently, they are assigned to the same token

Just curious, what is your use case? why do you need to discriminate them?

I find it more ergonomic to see at a glance where doc comments are, and which parts of code have (or have no) doc comments.

Just curious, what is your use case? why do you need to discriminate them?

It would be helpful to compute metrics that determine how much a code is documented in percentage

Just curious, what is your use case? why do you need to discriminate them?

Another usecase mentioned in https://github.com/tree-sitter/tree-sitter-rust/pull/99#issuecomment-772129346 is to highlight doc comments as they are markdown. It would be especially useful for long documentation, for example in modules.


bug in del_word

In add_word, it should be:
freq = int(freq) if freq is not None else self.suggest_freq(word, False)
in order to be compatible to:
def del_word(self, word):
self.add_word(word, 0)

You can make a PR.


Prototype: "light mode" for cardano-wallet

Issue number
ADP-1370
Overview
This prototype explores whether we can implement a "light mode" for cardano-wallet which aims to make synchronisation faster by using a less trusted source for blockchain data.
Result: Yes, the implementation of a "light mode" is feasible, but restricted to Shelley wallets.
For the full report, see the README.
The prototype is a Cabal project contained in the folder /prototypes/light-mode-test/.
Comments

This prototype uses https://blockfrost.io as external data source. In order to run the actions in the Demo module, you have to register with Blockfrost and put your API token in secrets/blockfrost.mainnet.token.
How do we get a rendered version of the report for easier reading? 🤔

All good - are you happy to merge this?

Yes. But I still have to add the package to nix.

You could probably not worry about nix or CI, and just add a separate cabal.project in the prototypes subdirectory.


Develop a consistent strategy on "automatically resetting or not resetting all qubits on release".

Discussion.
Copy:
cgranade
This appears to automatically reset all qubits on release, but that's not the semantics used in any other of our simulators, I believe. I know @swernli led a discussion on that about a year ago, may be good to get his take here.
swernli
I appreciate the callout! This is indeed an area fraught with options, and one we've gone back and forth on. We fixed the fullstate simulator's QIR execution to treat releasing non-zero qubits as errors, making it consistent with how local simulation via C# works, only to get the feedback that this behavior interferes with running QIR programs from non-Q# languages where this convention is not enforced. Given that feedback, I think there was desire to remove the error even for the fullstate simulator, at least when running QIR, but I believe it's still something of an open question.
Given all of that, I think the behavior written here makes sense, even though it can cause side effects. Changing it to be an error is something we should leave until we have a more definitive decision regarding the behavior of our other simulators.
cgranade
Sounds good. Whatever way we decide to go on that, we should probably be consistent and make sure that's well documented. I think there's likely still a lot of parts of the Q# docs, for instance, that assume that implicit resets don't happen after releasing qubits, such that optimizations from coherent unpreparation are allowed — if we decide for always implicitly resetting, those docs and samples will likely need to be updated.

For additional context, see previous issues on this topic for QIR (https://github.com/microsoft/qsharp-runtime/issues/552) and C# infrastructure (https://github.com/microsoft/qsharp-runtime/issues/206). As mentioned above, we may be phasing out this behavior for QIR, but there are still open questions.
@bettinaheim FYI.


systemd.timers: automatically convert string to list

Motivation for this change
488f0d9cb362342081ece69e6ef52cd4adf4fa5a introduced the possibility to set startAt to a list.
When we generate the timer units, we only check for startOn != "".
Instead of checking for empty string and empty list, wrap strings automatically in a list and only check for empty list.
nix-optimise module was wrongly using optional instead of optionals on a list, causing another list wrapped around it.
Fixes #19610
CC @NeQuissimus (bug report) @Profpatsch (introduced startAt as list)
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS

[x] Fits CONTRIBUTING.md.

Makes sense to me. Any reason to hold off on this?

@joachifm @groxxda There’s still the issue I commented. Better to deprecate the string-only version so we can get rid of the hack at next release.

Which issue is that?

See https://github.com/NixOS/nixpkgs/pull/19668#discussion-diff-84037641R329

I still don't get it?

apply = v: if isList v then v else (throwDeprecationWarning [ v ]);

and move to type = listOf [ str ]; with next release.

Adding the deprecationWarning is a good idea.

We still got problems with nix-env that doesn’t like deprecation throws, but I just thought that until that works, we can create something like throwDeprecationWarning = identity.

Note that startAt = optionalString false x generates invalid timer units (used by nixos-upgrade and nix-gc), which is kind of a regression. Not sure if we want to handle this in the apply or change those uses of optionalString to optional?
As for deprecating startAt as strings, the new mkChangedOptionModule might fit the bill.

Oh that's true - I think we should fix the callers and not add more "legacy-support"....


Vue routing?

Does Weex have its own way of doing routing?
Using weex create it says:
Use vue-router to manage your view router (not recommended)
So, if I don't use Vue router... what do I use for routing?

Ran into the same issue, You should probably use the weex navigator. explained in the docs:
https://weex.incubator.apache.org/references/modules/navigator.html

@dcohenb - Thanks!

@dcohenb can you tell me how to pass the URL while navigating? As the docs do not say much about that. Say I have set up a route "/example", opening a certain component then how should I put it in the navigation object?
Or is it completely unrelated to routing and if so then how exactly it will identify which component to load and where to load?

This issue is outdated for a long time and will be closed now. You can create a new one if you still have questions.


Suggestion: remove "Active cases estimate" data

As the subject says, suggesting removal of "Active cases estimate" data and related to it graphs.
Considering that:

We only have confirmed cases, that come from tests and not everyone is being tested
We have no numbers of actual recoveries, but simply discharged from hospitals (I assume, such people still may be infected, but simply need no hospital care anymore and can finish recovering at home in self-isolation)
In general even total confirmed cases number is relatively small value - just 0.12% from total population of Estonia
There's seemingly no explanation of how "Active cases estimate" numbers are calculated

It may lead some people to feeling, that it's totally safe to ignore all kinds of restrictions put by the government.

Alternatively make it so, that this data is shown in opt-in manner - some switch to display estimated data + some fair warning, that this is just estimation (and how estimated).
Also, it might be a good idea to add somewhere in the website something like "please, follow recommendations from the government and the restrictions put by it".

The "Active cases estimate" follows the guidelines from terviseamet. If you have no symptoms after 2 weeks you are cured. Something like this is needed to show how the virus is evolving in the comunity. Just everyday new confirmed cases doesnt show anything. After a month we might have 2000 confirmed, but nobody is actually sick anymore...

In this case, this guideline has poor value when trying to estimate the current status. Since according to available preliminary data, the median time from onset to clinical recovery is 2 weeks for mild cases and 3-6 weeks for patients with severe or critical disease, then I would suggest that it could be safely said that all people who were tested positive 6 weeks ago, have recovered.


Update pip.js

Add a keyFile option, so you could replace the default keyfile for one that is not id_rds
This change was made to make possible a work arround for https://github.com/UnitedIncome/serverless-python-requirements/issues/272
But it mey also be a interesting feature.

I really would like this keyfile option!

@revmischa  check the line that I've changed in this PR, chage it to the .ssh folder instead of a single file. It will work. Sure there may be some secutiry issues. But, on my understanding it uses it just for building.


Support tfx 1.14

This PR updates the kFP compiler build and test to support TFX 1.14. TFX 1.14 official container is built with Python 3.10, so compiler build/test is updated for that. It also removes support for Python 3.7, which is no longer required.
The following changes were required:

dependencies updated

python = ">=3.8,<3.11" - removes support for 3.7; adds support for 3.10
PyYAML = ">=5.4.1" - this was updated in conjunction with a breaking change (see below)
pytest = "7.4.0" - this was found to be necessary to get some NBCU pipeline unit tests to work, so also upgraded here
shapely = "<2" - see this Google AI Platform issue

updates to compiler Dockerfile to remove Python 3.7 and add 3.10
fixed breaking change in compiler unit test - yaml.load() now needs a Loader arg, or use safe_load() method. The latter was used.
updated integration-test Python versions
fixed integration-test - was missing --execution_mode arg and compiler expects --pipeline_config arg to be a file
in integration-test Dockerfile, the initial shapely downgrade on single pip command  RUN pip install tfx==$TFX_VERSION "shapely<2" did not work and introduced null errors and segmentation faults when importing TFX packages in compiler.py. Following the exact instructions in the issue above, ie. pip install -U google-cloud-aiplatform "shapely<2" fixed the issue
tested v1 and v2 args on --execution_mode
while debugging the shapely issue, noticed ::// in PYTHONPATH in compile.sh- it obviously did 'work' before, but corrected it anyway
corrected compiler path in README.md

:white_check_mark: unit tests passing
:white_check_mark: acceptance test passing
:white_check_mark: integration test passing

OK to test

OK to test

ok to test

OK to test

My main concern is how to document the shapely pinning to version <2. Should it be an issue on this repo that we link from both places with a "FIXME" comment?

It should be noted somehow. At least referring to the issue it fixes would explain to OSS users why it's there.

OK to test

OK to test

OK to test

OK to test

OK to test


add prettier code formatting and linting for import/export values

This adds prettier code formatting.  It will be applied when eslint --fix is run.  It also adds eslint-plugin-import which lints imports and exports.  For example if you try to import { fooBlah } from "./lib.js" and lib.js doens't have a fooBlah export, eslint will error.
It also adds husky and lint-staged to allow linting to happen when a file is staged in git. There was already a precommit npm script but precommit requires husky and (optionally) lint-staged to be installed in order to work.  npm itself doesn't have a precommit script.

I would recommend adding the examples directory to the ESLint scan as well - turns out, there are quite a few issues there.
So, that would mean that in the package.json we would change the scripts definition to:
"scripts": {
        "..."
        "eslint": "./node_modules/.bin/eslint src examples",
        "eslint-fix": "./node_modules/.bin/eslint --fix src examples",
        "..."
}

Also, I think missing JSDoc comments should be a warning rather than an error - any thoughts on this?

@blalasaadri I also wanted to add the examples dir, but it required cleanup I wasn't ready to do yet (time constraints).  Part of the problem is the lib dir, which has files we definitely don't want to lint.  I'll update this PR with a .eslintignore file to exclude lib.

Thanks @blalasaadri !

It seems the Travis build is now failing because it's merging this branch onto master and the main_text.js file there doesn't yet follow the new guidelines. I've looked into it and the only problem I can't seem to be able to fix is that the variable text is unused; maybe @JeffreyBrettColeman (who added that variable) can help here? My change with everything working except for that is at https://github.com/blalasaadri/hero-engine/commit/f43159358d824a35f566f13b715fbc9b649c68ec.

@blalasaadri  @JeffreyBrettColeman  I applied @blalasaadri's fix and also removed the line length linting rule (prettier handles that for everything but comments, which don't seem worth enforcing).


[Docs] Example of polling a bigquery job is wrong.

job.state == 'running' does not exhaustively describe the non-complete states (and in fact is not a valid state at all as running jobs have state RUNNING
But since jobs can also have state PENDING it should be not job.state == 'DONE'

@elibixby Thanks for the report!


can not create new twin

dashboard
version : v2.0.0-rc14
network : QAnet
Description
after creating an account and then accepting terms and condition the request gets rejected

Screencast from 06-21-2023 02:50:31 PM.webm

This needs investigation

After some investigation found that accepting terms & conditions fails due to the document hash being empty.

Verified on QAnet, 2.0.0-rc15.
Accept terms and condition are accepted and relay created, Twin was successfully created.


LXD Proxy crashes on first connection

Required information

Distribution: Ubuntu
Distribution version: 18.04
The output of "lxc info" or if that fails:

config: {}
api_extensions:
- storage_zfs_remove_snapshots
- container_host_shutdown_timeout
- container_stop_priority
- container_syscall_filtering
- auth_pki
- container_last_used_at
- etag
- patch
- usb_devices
- https_allowed_credentials
- image_compression_algorithm
- directory_manipulation
- container_cpu_time
- storage_zfs_use_refquota
- storage_lvm_mount_options
- network
- profile_usedby
- container_push
- container_exec_recording
- certificate_update
- container_exec_signal_handling
- gpu_devices
- container_image_properties
- migration_progress
- id_map
- network_firewall_filtering
- network_routes
- storage
- file_delete
- file_append
- network_dhcp_expiry
- storage_lvm_vg_rename
- storage_lvm_thinpool_rename
- network_vlan
- image_create_aliases
- container_stateless_copy
- container_only_migration
- storage_zfs_clone_copy
- unix_device_rename
- storage_lvm_use_thinpool
- storage_rsync_bwlimit
- network_vxlan_interface
- storage_btrfs_mount_options
- entity_description
- image_force_refresh
- storage_lvm_lv_resizing
- id_map_base
- file_symlinks
- container_push_target
- network_vlan_physical
- storage_images_delete
- container_edit_metadata
- container_snapshot_stateful_migration
- storage_driver_ceph
- storage_ceph_user_name
- resource_limits
- storage_volatile_initial_source
- storage_ceph_force_osd_reuse
- storage_block_filesystem_btrfs
- resources
- kernel_limits
- storage_api_volume_rename
- macaroon_authentication
- network_sriov
- console
- restrict_devlxd
- migration_pre_copy
- infiniband
- maas_network
- devlxd_events
- proxy
- network_dhcp_gateway
- file_get_symlink
- network_leases
- unix_device_hotplug
- storage_api_local_volume_handling
- operation_description
- clustering
- event_lifecycle
- storage_api_remote_volume_handling
- nvidia_runtime
- candid_authentication
- candid_config
- candid_config_key
- usb_optional_vendorid
api_status: stable
api_version: "1.0"
auth: trusted
public: false
auth_methods:
- tls
environment:
  addresses: []
  architectures:
  - x86_64
  - i686
  certificate: |
    -----BEGIN CERTIFICATE-----
    ...
    -----END CERTIFICATE-----
  certificate_fingerprint: c1a6a8b489f5848dec104da0a78e0160da90f1e4627bc96400581d7074094e3f
  driver: lxc
  driver_version: 3.0.3
  kernel: Linux
  kernel_architecture: x86_64
  kernel_version: 4.15.0-47-generic
  server: lxd
  server_pid: 1850
  server_version: 3.0.3
  storage: dir
  storage_version: "1"
  server_clustered: false
  server_name: ns359011
  project: ""

Issue description
After creating a proxy, the /usr/lib/lxd/lxd forkproxy crashed after first connection.
Steps to reproduce

Create a container (ubuntu:18.10 in my case)
Inside container, launch nc -l 6899
Create a device proxy

$ lxc config device add mycontainer myport6889 proxy listen=tcp:<IP_ADDRESS>:6899 connect=tcp:localhost:6899

Try to connect to host:6899

$ nc host 6899
TEST <= after the return key, connection is closed
$

5:  The log of /var/log/lxd/mycontainer/proxy.myport6899.log shows:
Starting to proxy
/usr/lib/lxd/lxd: relocation error: /lib/x86_64-linux-gnu/libnss_files.so.2: symbol __libc_readline_unlocked version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

Information to attach

[ ] Any relevant kernel output (dmesg)
[x] Container log (lxc info NAME --show-log)
[x] Container configuration (lxc config show NAME --expanded)
[x] Main daemon log (at /var/log/lxd/lxd.log or /var/snap/lxd/common/lxd/logs/lxd.log)
[ ] Output of the client with --debug
[ ] Output of the daemon with --debug (alternatively output of lxc monitor while reproducing the issue)

Packages version:
root@ns359011:/var/log/lxd# apt policy libnss3
libnss3:
  Installed: 2:3.35-2ubuntu2.2
  Candidate: 2:3.35-2ubuntu2.2
  Version table:
 *** 2:3.35-2ubuntu2.2 500
        500 http://ubuntu.mirrors.ovh.net/ubuntu bionic-updates/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages
        100 /var/lib/dpkg/status
     2:3.35-2ubuntu2 500
        500 http://ubuntu.mirrors.ovh.net/ubuntu bionic/main amd64 Packages
root@ns359011:/var/log/lxd# apt policy lxd
lxd:
  Installed: 3.0.3-0ubuntu1~18.04.1
  Candidate: 3.0.3-0ubuntu1~18.04.1
  Version table:
 *** 3.0.3-0ubuntu1~18.04.1 500
        500 http://ubuntu.mirrors.ovh.net/ubuntu bionic-updates/main amd64 Packages
        100 /var/lib/dpkg/status
     3.0.0-0ubuntu4 500
        500 http://ubuntu.mirrors.ovh.net/ubuntu bionic/main amd64 Packages

lxc-config.log
lxc-info.log
lxd.log

Sounds like a local linker issue, trying now in a 18.04 container with stock LXD but according to Ubuntu, the proxy tests succeeded during build.

I confirm that it works with a 18.04 container

Oh, so that's interesting, I wouldn't have expected the container to matter, what I meant above was that I was going to run nested LXD to quickly reproduce the issue, but if you only get the link error when the container is 18.10, that suggests we're doing something pretty weird somewhere in there.

Replace localhost with <IP_ADDRESS> and you'll be fine I think, we should ban anything that's not an IP and this will fix the issue as nss won't get loaded anymore.

The fix for this issue is to add a validator which prevents both listen and connect from using anything other than an IP address as anything else may call nss in the container, doing god knows what.

I just tested with <IP_ADDRESS> with ubuntu:18.10 and issue has disappeared !
Thanks, I'll let you close this issue


bump ansible community.kubernetes depedency to <1.1.0

Not sure if this will work.

@fabianvf mentioned to me "I think that will pin it to 1.x, which we probably don't want to do until the k8s_status collection is fixed" so hold this PR for now

/hold
Until make the 1.1.0 works with the projects

I believe we need the '>=1.1.0' operator. Once we have this we can replicate the dependency update downstream

Hi @jberkhahn,
This pr requires to be rebased with the master. It is in a very old stage.
I think we might already in the stage to make the operator works with the upper versions.
Maybe the problem faced with 1.1.0 is solved.
Could you please rebase it with teh master and check if we are in the place to in fact use the upper version?
Otherwise we can track an issue for that (if do not exist) and close this one. WDYT?

This is being handled by #4594 now.


Does this Integration support agile outgoing for export?

Does this Integration support agile outgoing for export?
Krs
Mark

Hello.
This integration should create sensors for both your import and export. The issue is it's harder to test for tariffs that I'm not on.
If there are any issues, let me know.
Thanks,
Dave

Thanks for the prompt reply.
Do you create sensors for best time to export for a certain period block?  I.e the highest priced block?
I wasn't sure if this was handled from a brief look at the code.
If the answer is a YES then I will get on and download and answer all my other questions myself!
Krs
Mark

You can create binary sensors (referred to as target rates), which I believe can target your export sensors. However, I don't have this setup and so this functionality was contributed by another user, so this might not be working as intended (e.g. picking the point where the price is lowest instead of highest). It would be great if you had a chance to try out the integration and raise any issues in this area that need fixing :)

I can confirm that now I have 2 MPAN numbers (one import one export) both are shown in the integration as different devices. Rates are stored in the attributes of the sensors. I have not tried target rates yet on either import or export so will have a play and update. Just need to figure out how to pull the data from the attributes into a nice card but thats a different issue. For the question "Does this integration support agile outgoing for export" I can confirm this is a hard yes. To what extent, different question but any issues I will assume this issue should be closed and any issue relating to the support should be a different issue entirely. Thanks for this @BottlecapDave

@BottlecapDave
Just tested this for Export (already using it for Import).
Unfortunately it shows lowest rates, not highest.
Please could you take a look as this would be incredibly useful?
Thanks

Sorry to hear this isn't working @usbrit. I'm taking a look now, but it would be useful if you could send me some diagnostics of your setup so that I have an idea of what data I'm working with.
You can download diagnostics of your account by going to your electricity meter device by

Navigate to http://bottlecapha.local:8123/config/devices/dashboard
Search for octopus
Click on the device titled Electricity Meter
Click Download diagnostics
Upload file here.

@BottlecapDave Update: so have figured timers work on export BUT are finding the lowest tariffs rather than the highest. So I have set a 22 hour timer which is ON for the worst export times on flips OFF for the best. Not ideal, but it works. Could you add a toggle on the UI to flip the logic for export meters instead?
Thanks for providing this, really makes life easy for charge/discharge times.

Sorry to hear this isn't working @usbrit. I'm taking a look now, but it would be useful if you could send me some diagnostics of your setup so that I have an idea of what data I'm working with.
You can download diagnostics of your account by going to your electricity meter device by

Navigate to http://bottlecapha.local:8123/config/devices/dashboard
Search for octopus
Click on the device titled Electricity Meter
Click Download diagnostics
Upload file here.

Here's the diagnostics too
{   "home_assistant": {     "installation_type": "Home Assistant OS",     "version": "2022.10.3",     "dev": false,     "hassio": true,     "virtualenv": false,     "python_version": "3.10.5",     "docker": true,     "arch": "armv7l",     "timezone": "Europe/London",     "os_name": "Linux",     "os_version": "5.15.61-v7",     "supervisor": "2022.11.2",     "host_os": "Home Assistant OS 9.2",     "docker_version": "20.10.17",     "chassis": "embedded",     "run_as_root": true   },   "custom_components": {     "octopus_energy": {       "version": "4.6.4",       "requirements": []     },     "mass": {       "version": "2022.11.0",       "requirements": [         "music-assistant==1.8.7"<EMAIL_ADDRESS>     ]     },     "solis": {       "version": "3.1.0",       "requirements": []     },     "hacs": {       "version": "1.28.3",       "requirements": [         "aiogithubapi>=22.2.4"       ]     },     "hildebrandglow_dcc": {       "version": "0.6.0",       "requirements": []     },     "octopusagile": {       "version": "2022.10.0b0",       "requirements": []     },     "solarman": {       "version": "1.0.0",       "requirements": [         "pyyaml"       ]     },     "nodered": {       "version": "1.1.2",       "requirements": []     }   },   "integration_manifest": {     "domain": "octopus_energy",     "name": "Octopus Energy",     "config_flow": true,     "documentation": "https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/",     "issue_tracker": "https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/issues",     "ssdp": [],     "zeroconf": [],     "homekit": {},     "dependencies": [],     "codeowners": [       "@bottlecapdave"     ],     "version": "4.6.4",     "iot_class": "cloud_polling",     "is_built_in": false   },   "data": {     "electricity_meter_points": [       {         "mpan": "**REDACTED**",         "meters": [           {             "serial_number": "**REDACTED**",             "is_export": true,             "is_smart_meter": true           }         ],         "agreements": [           {             "valid_from": "2022-07-16T23:00:00+00:00",             "valid_to": "2023-07-16T23:00:00+00:00",             "tariff_code": "E-1R-AGILE-OUTGOING-19-05-13-A"           }         ]       },       {         "mpan": "**REDACTED**",         "meters": [           {             "serial_number": "**REDACTED**",             "is_export": false,             "is_smart_meter": true           }         ],         "agreements": [           {             "valid_from": "2022-06-30T23:00:00+00:00",             "valid_to": "2023-06-30T23:00:00+00:00",             "tariff_code": "E-1R-AGILE-18-02-21-A"           }         ]       }     ],     "gas_meter_points": [       {         "mprn": "**REDACTED**",         "meters": [           {             "serial_number": "**REDACTED**"           }         ],         "agreements": [           {             "valid_from": "2021-05-27T23:00:00+00:00",             "valid_to": null,             "tariff_code": "G-1R-VAR-21-04-09-A"           }         ]       }     ]   } }

Hello @usbrit - This should be fixed with https://github.com/BottlecapDave/HomeAssistant-OctopusEnergy/releases/tag/v4.7.0

@BottlecapDave tested and confirmed to be working 👍🏻👍🏻 Thanks!

Excellent. Thanks for reporting back.


Middleware to intercept server errors related to installation issues

Issue type
[x] Feature request
[ ] Bug report
[ ] Documentation
Environment

Python version:  3.5.2
NetBox version:  2.2.4

Description
It may be worthwhile to implement a lightweight middleware to intercept common exceptions related to installation issues. For example, a ProgrammingError typically indicates that database migrations have not been applied following an upgrade. Returning hints at possible solutions to the user would help shorten the support cycle and cut down on invalid bug reports.

I think you are on the right track. I have seem somewhat similar things done with https://docs.djangoproject.com/en/1.11/topics/http/middleware/#process-exception


Not seeing the "did you mean" predictions.

When I miss type I don't see the "did you mean" message showing me the possible fixes.

System Details:

macOS: 10.12.4 (Beta)
bash shell

Is there something I'm missing?

"Did you mean" prediction isn't function of thefuck. Don't know about bash, but in zsh some https://github.com/robbyrussell/oh-my-zsh plugins can do that.

Ahh ok, thanks for clarifying that.


Find out why in some cases e2e test fails on CircleCI

Not sure, but I haven't seen bug for a while now. Probably fixed somewhere.


Update languageSelector.ts

Updated comments style.
Code is up-to-date with 'main' branch.
You can't test these changes because it's only comments.

@microsoft-github-policy-service agree

@denipolis please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.
@microsoft-github-policy-service agree [company="{your company}"]

Options:

(default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

(when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement
@microsoft-github-policy-service agree

Closing as these changes don't seem to add value


Flow kernel name to Enterprise Gateway

Turns out the kernel name was not properly conveyed to EG - resulting in a local python3 kernel being used.
Fixes #1030
Developer's Certificate of Origin 1.1
   By making a contribution to this project, I certify that:

   (a) The contribution was created in whole or in part by me and I
       have the right to submit it under the Apache License 2.0; or

   (b) The contribution is based upon previous work that, to the best
       of my knowledge, is covered under an appropriate open source
       license and I have the right under that license to submit that
       work with modifications, whether created in whole or in part
       by me, under the same open source license (unless I am
       permitted to submit under a different license), as indicated
       in the file; or

   (c) The contribution was provided directly to me by some other
       person who certified (a), (b) or (c) and I have not modified
       it.

   (d) I understand and agree that this project and the contribution
       are public and that a record of the contribution (including all
       personal information I submit with it, including my sign-off) is
       maintained indefinitely and may be redistributed consistent with
       this project or the open source license(s) involved.

Tested it with Conductor and it works. Thanks @kevin-bates


[Feature Request]:  Add hover effects on FAQ

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
When someone hovers over a question card, the color of the question text on that card will change to the green color used in the website theme.
Use Case
User feel.
Benefits
User interaction.
Add ScreenShots

Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

@Ajay-Dhangar Please assign me this task !
Thank You !


Return error if there are multiple same name params

Changes
Right now pipeline accepts multiple parameters with
the same name. This sometime causes the pipeline to
not finish.
This change adds a simple check and returns error
when there are multiple parameters with the same
name in the spec.params.
Fixes #2016

Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[x] Includes tests (if functionality changed/added)
[x] Includes docs (if user facing)
[x] Commit messages follow commit message best practices

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
After this change it is not allowed to have multiple parameters with the same name
within pipeline spec.

/kind bug

/assign bobcatfish

/ok-to-test

/lgtm


ci: use crate cache for e2e and forge jobs - (45)

Motivation
Updated builds crate cache to latest.
Testplan
CI/CD's existing test cases will cover the above change.

/canary

:broken_heart: Test Failed - ci-test

/canary

:sunny: Canary successful

/land

:broken_heart: Test Failed - ci-test

/land


show_FPNet.py 跑不通

第27行的引用
from model_recon_3layers_robustness import _netlocalD,_netG
没有来源，报错为
ModuleNotFoundError: No module named 'model_recon_3layers_robustness'
麻烦解决一下

I will update the code in the next few days.

Please add a file named "Checkpoint" before training and use show_recon.py to generate final txt files.Then you can use Meshlab to visualize the point cloud.


SPDY Protocol Framing Layer

Encoder, decoder, session handler and their related message types for the SPDY protocol.

Thanks a lot, Jeff!


2018-12-17 add IFWallet logo to wallets list

@maplesyrupsucker, IFWallet support BCH, please help me add IFWallet logo to wallet list.
support languages: 简体中文/繁體中文/English

@bibodeng check your Telegram messages or hit me up on WeChat using the same handle

Ah, the structure of the website changed. I am closing this and opening a PR with the appropriate changes myself

thanks a lot


Can't load a project with Gantt chart

In which chart does the bug happen?

Gantt chart

RAWGraphs Version
RAWGraphs 2.0
Web browser and version
Chrome
Operating System
Mac os
Steps to reproduce this

I create a project using a Gantt chart
I export the project .rawgraphs
I upload the project
Error: Can't open your project. Can't open your project. Selected project is not valid

Project file
GanttChart.zip
Additional context

I have the same issue.


#362: Fixed ModelInfo not containing a target map for types mapped to…

… CQL interval types.

Github Issue:
[X ] I've read the contribution guidelines
[X] Code compiles without errors

The test is actually in the translator, which I verify prior to submitting the PR here. Not ideal, but workable.


GDC dev container name converts dash to underscore

Expected
When launching GDC development container, the name of the container is the name of the project, with suffix -dev-1 appended
Actual
Almost as expected, except that a dash in the project name is converted to an underscore
Example

project name: my-project
generated dev container name: my_project-dev-1

This is by design.
Docker Compose automatically appends the service name "dev" and instance num "1" using hyphens, hence the "-dev-1".
To make it easier to see / parse the GDC name portion of the compose project name all spaces and hyphens are converted to underscore.
I believe having hyphens in the name other than those automatically added by compose caused problems with older versions of compose as well.

Ah, thanks for the explanation! Very cool project.


6.0.0 breaks AoT: datatable.component.scss not found

I'm submitting a ...  (check one with "x")
[X] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here

Current behavior
AOT build using angular-cli beta 26 fails:
ERROR in ENOENT: no such file or directory, open<EMAIL_ADDRESS>Expected behavior

Reproduction of the problem

What is the motivation / use case for changing the behavior?

Please tell us about your environment:

Table version: 0.7.x
6.0.0

Angular version: 2.0.x
2.4.5

Browser: [all | Chrome XX | Firefox XX | IE XX | Safari XX | Mobile Chrome XX | Android X.
n/a

Language: [all | TypeScript X.X | ES6/7 | ES5]
Typescript 2.1.4

+1
I've got the same issue

same issue

Are you manually including that file? You shouldn't have to now.

I never included that file manually. As a workaround I copied it to the components directory and now AoT works. I do not know why it ends up in the parent directory, it is correctly referenced to in the component with its relative path.

+1
same issue

I'm working on a fix now

Is this only breaking in AoT? I'm not hitting this but I'm almost not running AoT.

Aot only

If you need some test feedback on a PR, let us know!

+1
Same issue

Anyone have any ideas how to fix this? I converted it to the styleUrls to literally help with this (lol).

+1
Same issue in AOT compile.  Copied file to release branch.

I see this file getting built? Is that not it? -> https://github.com/swimlane/ngx-datatable/blob/master/release/components/datatable.component.scss.ngstyle.ts

Fixed in 6.0.1

Unfortunately this doesn't fix the issue.
$ node_modules/.bin/ng build --aot
Hash: d62e3fb109fef7d2f5d2
Time: 35039ms
chunk    {0} styles.bundle.css, styles.bundle.map, styles.bundle.map (styles) 249 kB {4} [initial] [rendered]
chunk    {1} main.bundle.js, main.bundle.map (main) 45 kB {3} [initial] [rendered]
chunk    {2} scripts.bundle.js, scripts.bundle.map (scripts) 64.1 kB {4} [initial] [rendered]
chunk    {3} vendor.bundle.js, vendor.bundle.map (vendor) 1.7 MB [initial] [rendered]
chunk    {4} inline.bundle.js, inline.bundle.map (inline) 0 bytes [entry] [rendered]

ERROR in ENOENT: no such file or directory, open<EMAIL_ADDRESS>
ERROR in ./src/main.ts
Module not found: Error: Can't resolve './$$_gendir/app/app.module.ngfactory' in '/foo/frontend/src'
 @ ./src/main.ts 11:0-74
 @ multi ./src/main.ts

ERROR in<EMAIL_ADDRESS>Module not found: Error: Can't resolve '/foo/frontend/src/$$_gendir' in '/foo/frontend/node_modules/@angular/core/src/linker'
<EMAIL_ADDRESS>71:15-36 87:15-102
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS> @ ./src/main.ts
 @ multi ./src/main.ts

You can reproduce it by creating an sample angular-cli project and import the module.

I can too confirm the issue is not fixed yet.
I have even prepared a sample setup here https://github.com/smoke/ngx-datatable-aot-issue you can just execute ng build -aot -prod to reproduce the issue.
Hope this helps fixing the issue sooner.
====
On a side note, you should correct the path in https://github.com/swimlane/ngx-datatable/blob/master/docs/introduction/themes.md
Change:
@import<EMAIL_ADDRESS>
->
@import<EMAIL_ADDRESS>

Thanks looking into this today!

Please retest. I made a temp fix to move the scss for now.

I confirm, the fix seems to be working.
If anyone else wants to take a look, I have updated the repo https://github.com/smoke/ngx-datatable-aot-issue

Im trying to build aot version 6.0.2 result:
Module parse failed: @swimlane\ngx-datatable\release\components\datatable.component.scss Unexpected token (1:0)
You may need an appropriate loader to handle this file type.
| .ngx-datatable {
|   display: block;
|   overflow:hidden;:
SyntaxError: Unexpected token (1:0)
Im using webpack, In my project im using less, do I need also scss loader to use this library?

Ya, thats the side effect of that hack. I thought that might happen.
I'm still investigating the best way to do this without it being even more hacky...

@amcdnl I am having the same issue with Angular 4.0.3 and version 2.3.0 typscript

Is this issue fixed? I'm still having same problem on 6.3.0 release with angular 2.4.10.

@sh977218 can you upgrade to latest and test?
@xtianus79 can you post the error?

I am having the same problem with 10.0.5 building AOT. Here is the error:
Child<EMAIL_ADDRESS>1 module
ERROR in<EMAIL_ADDRESS>Module build failed: Error: "extract-text-webpack-plugin" loader is used without the corresponding plugin, refer to https://github.com/webpack/extract-text-webpack-plugin for the usage example
    at Object.module.exports.pitch (node_modules\extract-text-webpack-plugin\loader.js:26:9)

You are getting this in your project?

@amcdnl post the error?

Any update on this?
I am using angular 4.1.0  & typescript 2.3.2 for datatable version 9.1.0.
Getting below error while trying to run build in AOT mode
ERROR in Child compilation failed:
Module parse failed<EMAIL_ADDRESS>Unexpected token (1:0)
You may need an appropriate loader to handle this file type.
| .ngx-datatable {
|   display: block;
|   overflow: hidden;:
SyntaxError: Unexpected token (1:0)
For AOT, webpack config for parsing is
{
test: /.css$/,
loader: 'raw-loader',
exclude: /node_modules/
},
{
test: /.scss$/,
loaders: ['to-string-loader', 'css-loader', 'sass-loader']
},

@kabilya do you have solved this problem? i met the same one too.

thank you for any suggestions!

@kabilya @we125182 something new about this problem?

Make sure to use the @imports from the Theming Documentation.
https://swimlane.gitbooks.io/ngx-datatable/introduction/themes.html

I am also experiencing this issue using WebPack, scss and css excluding node_modules from loaders..

@we125182 I abandoned this library last year due to its issue with AOT.  I tried it again this year as it has currently have more features/functions than Material's MatTable.. I downloaded the entire source code from their repo and just include the entire ./src folder in my project.
import { NgxDatatableModule } from './ngx-datatable/index';
It's building now with my Angular 4.x project both in dev and production.
I don't know what's causing it, could be the combination of webpack and ExtractTextPlugin.
Hope this helps.

In my case I resolved the issue by simply removing module import statement.
Now it works, and compiles with AoT.
For reference I am using version 9.3.1 of ngx-datatable

Kinda same issue here, but it's actually JIT only, AOT works great (though, a while ago, it was the exact opposite 🙄).
"@swimlane/ngx-datatable": "^11.3.0",
"@angular/core": "^5.2.0",

I end up with error at runtime : Failed to load datatable.component.css
I fixed it using webpack :
  new CopyWebpackPlugin([
    { context: 'src', to: '', from: { glob: 'assets/**/*', dot: true } },
    { context: 'src', to: '', from: { glob: 'favicon.ico', dot: true } },
    { context: 'node_modules/@swimlane/ngx-datatable/release/components', to: '', from: { glob: 'datatable.component.css', dot: true } },
  ], { ... }),

Though, using angular-cli I did not find any way to fix it.
There's many issues (opened or closed) about datatable.component.css, and I personally struggled more than once with it (always after upgrading some packages). I tried to have a look, but I really can't find the issue :(


feat: add more extension api hooks

Description
Adds remainder of extension api hooks.
Task Item
closes #4357

Coverage decreased (-0.08%) to 55.073% when pulling 6d75a2ea947e57b777dc923200cc569da41b86d7 on abrown/extension-apis into 77ad8e1b440bb9ff77bd3373f5e03e5371b567e5 on main.


new category options

With the existing category posts and the new category page listing (#42), it needs to be possible to enable or disable each of them. Here's what I'm thinking.
/* category posts, the blog-like feature */
@cat.posts.enable;
@cat.posts.per_page: 5;

/* category list, the mediawiki-like feature */
@cat.list.enable;

Also, there will be two separate category roots. It will be called root.cat, and root.category will be deprecated.
@root.cat.posts<EMAIL_ADDRESS>@root.cat.list<EMAIL_ADDRESS>
I'm thinking that cat.posts.enable will be off by default, while cat.list.enable will be enabled by default. The category post view is more for blog-type sites, similar to wordpress. The page listing is more appropriate for most wikis.

Maybe we should forget the cat.*.enable directives. Just enable it if root.cat.* are present.

ok actually i will have @cat.posts.enable and @cat.list.enable but they will both be enabled by default. @root.cat.posts and @root.category will be equivalent for compatibility.


google colab pro: Failed to validate prompt for output 364

I am using google collab pro.
After generating any image, when trying to make a second one, the following message appears. Failed to validate prompt for output 364:
Output will be ignored
After this the notebook disconnects and I have to run the last cell again

Those warnings appear when the upscaler is not connected. It's expected to see these warnings and they do not cause any issues. I don't know much about Google Collab, I've never used it and can unfortunately not help with the disconnect issue


Rule engine not triggering the Command for Device

Files.zip
Hi
I have added a rule for rule engine using the following URL using POST method. But even though the data has the rule satisfy the command is not triggering
http://<IP_ADDRESS>:48075/api/v1/rule
Body:    {"name":"HighHeatSignal4", "condition": {"device":"258890a3-e4b3-4967-acfe-b6895fe7a48d","command":"cc9afa10-2443-411e-aff6-ccb6d32870c4","checks":[ {"parameter":"Random", "operand1":"Integer.parseInt(value)", "operation":">","operand2":"1" } ] }, "action" : {"device":"258890a3-e4b3-4967-acfe-b6895fe7a48d","command":"cc9afa10-2443-411e-aff6-ccb6d32870c4","body":"{\"value\":\"3\"}"},"log":"Heat reported is too high" }
output of below command is attached in file "Curl_output"
curl http://localhost:48082/api/v1/device/name/RandNum-Device01
I have also attached the device profile file - "Device_profile"
Attached the zip file. Both files are inside
Can you please tell whats the issue and how do I fix it.

@debukhra - do you have both the rules engine and the command service logging set to DEBUG?  This might give us more data and help us narrow the issue search.  Also, can you share what version of EdgeX you are using?
It appears you are trying to call on one of the put commands on the random device service (impossible to know with just the ids provided for devices and commands).  If this is the case, I think that there are a few items incorrect in your rule body (more logging might give us more clues on this).  Here is an example rule post to trigger the the put of the Min_Int16 value of the GenerateRandomValue_Int16 command.
{"name":"HighHeatSignal4", "condition": {"device":"Random-Integer-Generator01","checks":[ {"parameter":"RandomValue_Int32", "operand1":"Integer.parseInt(value)", "operation":">","operand2":"1" } ] }, "action" : {"device":"2bd79151-aa51-4a00-9538-89e611897d9b","command":"cd18fa87-9448-471f-b53a-d0ffa5c5634c","body":"{\"Min_Int16\":\"3\"}"},"log":"Heat reported is too high" }

@jpwhitemn
Thanks for the answer.
There were couple of mistakes in the rule that I was setting.
name":"HighHeatSignal4", "condition": {"device":"Random-Integer-Generator01","checks":
One of the mistake,  I was using device Id instead of device name by following the example given in
https://docs.edgexfoundry.org/Ch-RulesEngine.html
{"name":"motortoofastsignal", "condition": {"device":"562114e9e4b0385849b96cd8","checks":[ {"parameter":"RPM", "operand1":"Integer.parseInt(value)", "operation":">","operand2":"1200" } ] }, "action" : {"device":"56325f7ee4b05eaae5a89ce1","command":"56325f6de4b05eaae5a89cdc","body":"{\"value\":\"3\"}"},"log":"Patlite warning triggered for engine speed too high" }
device under "condition:{device: < >" is only working if it is device name but if I use device ID it is not working.

@debukhra - can I consider this issued closed then?

Can we correct the sample in "https://docs.edgexfoundry.org/Ch-RulesEngine.html".
We can also add a note that command must be a "put" request. The command id for get and put are same and hence we can not specify if the command is fir get or put. i found a comment in rule engine code that for now, all rule engine requests are "put" request.


debug: test and fix race conditions in debug endpoints

This makes it so during a few tests we call all the debug endpoints.
This found a few races which have been fixed in this PR

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test lint

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test lint

unit-tests-arm64_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test unit-tests-arm64

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test lint

unit-tests-arm64_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test unit-tests-arm64

unit-tests_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test unit-tests

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test lint

unit-tests-arm64_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test unit-tests-arm64

unit-tests_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test unit-tests

integ-security-istiodremote_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test integ-security-istiodremote

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test lint

unit-tests-arm64_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test unit-tests-arm64

unit-tests_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test unit-tests

integ-security-istiodremote_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test integ-security-istiodremote

integ-ambient_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test integ-ambient

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

@howardjohn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test unit-tests-arm64

unit-tests_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test unit-tests

integ-security-istiodremote_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test integ-security-istiodremote

integ-ambient_istio
5c1f2c777bd2d8c167156768bd53434f73638f1b
link
true
/test integ-ambient

lint_istio
7735928c501f9d7542d8e0754e73ae6db16221a9
link
true
/test lint

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

/cherry-pick release-1.24

@hzxuzhonghu: once the present PR merges, I will cherry-pick it on top of release-1.24 in a new PR and assign it to you.

In response to this:

/cherry-pick release-1.24

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@hzxuzhonghu: #54463 failed to apply on top of branch "release-1.24":
Applying: debug: test and fix race conditions in debug endpoints
Using index info to reconstruct a base tree...
M	pilot/pkg/xds/debug.go
M	pilot/pkg/xds/workload.go
M	pkg/kube/krt/collection.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/kube/krt/collection.go
CONFLICT (content): Merge conflict in pkg/kube/krt/collection.go
Auto-merging pilot/pkg/xds/workload.go
Auto-merging pilot/pkg/xds/debug.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
hint: When you have resolved this problem, run "git am --continue".
hint: If you prefer to skip this patch, run "git am --skip" instead.
hint: To restore the original branch and stop patching, run "git am --abort".
hint: Disable this message with "git config advice.mergeConflict false"
Patch failed at 0001 debug: test and fix race conditions in debug endpoints

In response to this:

/cherry-pick release-1.24

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@hzxuzhonghu: new issue created for failed cherrypick: #54467

In response to this:

/cherry-pick release-1.24

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.


scion-pki: allow referencing predecessor certificates in payload

When creating a TRC update, support referencing the predecessor certificates. This simplifies the TRC ceremony, as the already included certificates do not need to be redistributed in case they do not change.

This change is