sunrise-sunset

Added an extra component that displays the sunrise and sunset times. It also calculates the time left before sunrise or sunset.
The UI changes according to the time of the day: background color and sun/moon image.

@ASLManasa

@LiubovRukhlina  looks good to me.


Generated SQL statement contains wrong bindings

Describe the bug
When dumping Query Builder, it generates incorrect SQL statement.
What version does this affect?

Laravel Version: 9.0.0
Package Version: 1.0.0

To Reproduce
dd(User::where('name', 'test')->whereBetween('id', [1, 2]));

It generates following SQL: select * from "users" where "name" = 'test' and "id" between 'test' and 'test'
Expected behavior
SQL: select * from "users" where "name" = 'test' and "id" between 1 and 2
Additional context
That lost me a few hours, trying to hunt down the bug in my app, then in Eloquent itself, then checking if it is affected by me being on PHP 8.1, etc.

Oof. Sorry about how much time that cost you! This is fixed in the 1.0.1 release.

Thanks. That's alright and is an unavoidable part of a developer's life :)


Add description for face-detection-retail-0005

Jenkins please retry a build

@sovrasov it seems you also need to add new file into index.md
15:42:29  + /home/jenkins/workspace/omz/precommit/documentation_ubuntu16/jenkins/omz/scripts/documentation_check.py src/intel_models
15:42:29  face-detection-retail-0005 not in index.md file

Jenkins please retry a build

@sovrasov could you please check other models descriptions to see what is the correct link to benchmark data? I think benchmark data not available at the moment, so other models have 'Performance' section just empty.
19:03:04  FILE: face-detection-retail-0005/description/face-detection-retail-0005.md
19:03:31  [✖] https://software.intel.com/en-us/openvino-toolkit/benchmarks
19:03:31
19:03:31  ERROR: dead links found!

Jenkins: ok to test


Azure Powershell Task lacks Select-AzureRmContext

I have noticed, after recently upgrading AzureRM module, that Azure Powershell Task uses wrong credentials. I mean it correctly:

adds account,
it correctly selects subscription

but then it forgets to select an appropriate context and effectively tasks are executing using a random account available on this machine.
I believe that Azure Powershell task should call Select-AzureRmContext to ensure Service Principal account is used.

@mkosieradzki With the new Azure powershell verion >6, a breaking change has been introduced regarding auto save of ARM context. There is an isssue on github for the same: https://github.com/Azure/azure-powershell/issues/6680
We will get back to you soon on our resolution plan.

@mkosieradzki As a workaround we will Clear-AzureRmContext before logging in. This will ensure only relevant context is used for calls henceforth.

Closing the issue since fix has been deployed. Please feel free to reopen if required.


THRIFT-4330: Allow unused extern crates

This PR adds attribute to the Rust generated code to allow unused crates, since some libraries may not use imports and generate warnings.
#![allow(unused_extern_crates)]

@allengeorge could you have a look at this change? Thanks!

CI failures do not seem to be related.

@sadikovi The change seems fine, but I don't understand when this warning gets triggered. Could you explain a bit more what you mean? When does this happen, and why? Thanks!

@sadikovi The change seems fine, but I don't quite understand when this problem happens. Could you explain when it gets triggered? In what sort of code setup? Thanks!

@allengeorge When I compile parquet-rs library I get following warnings (parquet.thrift)
warning: unused extern crate
 --> src/parquet_thrift/parquet.rs:8:1
  |
8 | extern crate ordered_float;
  | ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: #[warn(unused_extern_crates)] on by default

warning: unused extern crate
  --> src/parquet_thrift/parquet.rs:10:1
   |
10 | extern crate try_from;
   | ^^^^^^^^^^^^^^^^^^^^^^

This happens when extern crate ... is already defined in lib.rs for the library.

@Jens-G could you review this PR, please? Thanks!

@sadikovi Sorry for the delay - was away this weekend.
Ah, ok. That makes total sense. You probably don't have any floats in your IDL, or anything that would use the TryFrom conversion. LGTM.
@Jens-G LGTM; could you merge this please? TY!


Unclear on what the account admin is or how to find this

This page has a description of account admins, but nothing about how these are assigned, or how to find out what the current account admins are.

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

ID: 80be7853-c235-4280-7be9-75dfcee89b3d
Version Independent ID: fe446deb-5733-c3df-5c0f-9fe14a0844f4
Content: Azure Databricks administration guide - Azure Databricks
Content Source: databricks/administration-guide/index.md
Service: azure-databricks
GitHub Login: @mssaperla
Microsoft Alias: saperla

@johnmreynolds
Thanks for your feedback! We will investigate and update as appropriate.

@johnmreynolds
Please go through this below link for your reference.
https://learn.microsoft.com/en-us/azure/databricks/administration-guide/account-settings/account

@johnmreynolds We are going to close this thread as resolved but if there are any further questions regarding the documentation, please tag me in your reply and we will be happy to continue the conversation.

@Naveenommi-MSFT That link doesn't cover much about how account admins work. In particular, I can't see anything in that covers the second part of the query as to how to work out who the current account admins are.


 This could cause new errors during test teardown to go by unnoticed.
Moreover, the integration test use a different reporting mechanism which also handled errors differently (this is extra reason to do #12730).
This patch fixes the issues by consistently handling errors in suiteStarted and suiteDone in both reporting mechanisms.
Fixes #18319.

Before this patch:
Suite error: Stamp Editor Copy/paste from a tab to an other
  Message:
    ProtocolError: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
  Stack:
        at <instance_members_initializer> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:89:14)
        at new Callback (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:93:16)
        at CallbackRegistry.create (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:19:26)
        at Connection._rawSend (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/Connection.js:86:26)
        at CdpCDPSession.send (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/CDPSession.js:63:33)
        at #evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:353:50)
        at ExecutionContext.evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:268:36)
        at IsolatedWorld.evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/IsolatedWorld.js:96:30)
        at CdpFrame.evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/api/Frame.js:335:43)
        at CdpFrame.<anonymous> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/util/decorators.js:94:27)

Ran 1 of 193 specs
1 spec, 1 failure
Finished in 25.025 seconds

Run 193 tests
All integration tests passed.
integration tests runtime was 28.8 second

After this patch:
Suite error: Stamp Editor Copy/paste from a tab to an other
  Message:
    ProtocolError: Runtime.callFunctionOn timed out. Increase the 'protocolTimeout' setting in launch/connect calls for a higher timeout if needed.
  Stack:
        at <instance_members_initializer> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:89:14)
        at new Callback (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:93:16)
        at CallbackRegistry.create (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/common/CallbackRegistry.js:19:26)
        at Connection._rawSend (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/Connection.js:86:26)
        at CdpCDPSession.send (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/CDPSession.js:63:33)
        at #evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:353:50)
        at ExecutionContext.evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/ExecutionContext.js:268:36)
        at IsolatedWorld.evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/cdp/IsolatedWorld.js:96:30)
        at CdpFrame.evaluate (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/api/Frame.js:335:43)
        at CdpFrame.<anonymous> (file:///home/timvandermeij/Documenten/Ontwikkeling/pdf.js/Code/node_modules/puppeteer-core/lib/esm/puppeteer/util/decorators.js:94:27)

Ran 1 of 193 specs
1 spec, 1 failure
Finished in 25.006 seconds

Run 193 tests
OHNOES!  Some integration tests failed!
  1 of 193 failed
integration tests runtime was 28.4 seconds

/botio unittest

/botio integrationtest

Notice how the two runs above now fail correctly because this patch was deliberately not rebased onto #18320 yet: they now both log TEST-UNEXPECTED-FAIL | Copy/paste from a tab to an other and both end with OHNOES!  Some integration tests failed!.
I have now rebased onto the current master branch with #18320, so now the integration tests should succeed for that test:
/botio integrationtest

/botio integrationtest


Bucket attrs

[closes #199, #272, #273, #274, #275, #276, #277]

@blowmage I believe this PR is ready to be merged


How to set path for every database?

hi, I have two databases and I want to save on different volume, but inlfuxdb.conf just have a global config item. How to set path for every database?
thanks.

Currently there is no way to set a per-database data directory configuration, however the database name is always set as the first-level directory name in the InfluxDB data directory. For example, if you have the config set to:
[data]
...
  dir = "/var/lib/influxdb/data"
...

Then a database with the name mydb will be placed in the directory:
/var/lib/influxdb/data/mydb


Store Newsletter Email and Send Thank You Email

Feature Description
Implement functionality to store the email address of a user who subscribes to the newsletter in the database, and send a thank you email to the registered email address upon successful registration.
-Create an endpoint to accept the email address and store it in the database.
-After successful registration, trigger an email to the registered address.
-The email should thank the user for subscribing to the newsletter.
I will use nodemailer to send the mail to registered email
Use Case
this will increase user interaction and will help us to track the all the email that want to subscribe to the newsletter

@soham0005 please assign me this issue

@soham0005 please assign this to me under gssoc-extended and with levels.

@17arindam you can start working on it,


Feature Request - Error paths in console jump to file in editor when clicked

Often when I'm debugging lots of files at once it can be hard to quickly determine which file an error relates to, especially with long file paths that are often very similar to each other. I was thinking about whether it would it be possible to hyperlink the file name in the terminal to jump to the file in vscode (or another configurable editor)?
If I have the file's directory open in vscode I can jump to it by running code filepath/terragrunt.hcl in a terminal.
A few terminals even do support hyperlinks apparently, including gnome-terminal, iTerm2, tmux and others.
As a bonus, the link could even go to error's the line number. You can do this with code -g filepath/terragrunt.hcl:5.
What are your thoughts on a feature like this?

It seems like a great idea, but how do you actually implement it?


Benchmark HTML parsing

See https://github.com/rust-lang/docs.rs/pull/671, https://github.com/servo/html5ever/issues/414 for rationale.
This makes the extract_head_and_body function public since I couldn't
find a cfg flag that would do so only during tests.
This does not run benchmarks in CI, but makes it easy to do so locally. I plan to run benchmarks whenever dependencies are updated in the future.

Looks good to me. I guess the idea is to gather benchmarks before/after changes locally?
Feel free to merge.

I guess the idea is to gather benchmarks before/after changes locally?

Right, this would give me some idea of 'is rendering faster or slower after switching to kuchiki' without having to deploy to prod and possibly have the site go down again.


Fix 21863 - FieldNameTuple returns emptry string for interfaces

Symbols without members should produce an empty tuple. "" is also not a member and hence requires additional special casing.

@Geod24 This is silently modifying code behavior. The least we could do is to add a changelog entry

Also, what is the motivation of this change?

Created #8014 to restrict this change to interfaces


Test coverage

I just ran stack test --coverage on https://github.com/haskell-unordered-containers/unordered-containers/commit/964edca40d415c7f0b70c99fda2a4d9dc0949b9f. Here's the summary of the combined coverage report for all testsuites:

Not terrible, but could be better. Maybe there's even some dead code we could get rid of?

'Twould be nice to have more detail on what's not covered.

Yeah. It's hard to verbally summarize though. Maybe you can just generate the report yourself and take a look.
Sorry for the vague issue description. I think we should probably try to aim for >95% or so.

Please provide the information above in an alternative accessible format by editing the issue text.


Library breaks with more than 3 sequences

Everything works fine with up to three variables being sequenced. But as soon as a fourth target is added the sketch stops working.
This happens on Arduino Uno (ATMEGA328P)
However it seems to be working on an Arduino Mega (AT,EGA2560) up to 12 targets but not more. If these are the limitations perhaps you could explain this on the documentation so we are not wondering why things stop working.
Thank you for the lib anyway ;)

ATMEGA328 has limited memory, so you can't run many tweens. Please consider a more powerful MCU.


Update codebuild builder x64 container from Ubuntu 20.04 to 22.04

Why is this needed as the default? Is it better/faster somehow?
You can override it with:
new CodeBuildImageBuilder(stack, 'fargate builder', {
  // ...
  buildImage: codebuild.LinuxBuildImage.STANDARD_6_0,
});

Good timing. Just got this email from AWS:

Hello,
We are reaching out to you because you ran a build using the Ubuntu standard 5.0 [1] Docker Image, Amazon Linux 2 ARM standard 1.0 [2], or Amazon Linux 2 standard 3.0 [3] in the last 30 days. Starting March 30, 2023, AWS CodeBuild will be moving these images to an unsupported status and they will not be cached on the build hosts anymore.
You may continue using these images for your builds, but you will notice an increase in provisioning latency after March 30, 2023.
These images will also not be getting any new updates. We recommend updating your Build Projects to use the latest build images in order to get the latest language runtimes and tools. For more information on how to do this you can follow 'Docker images provided by CodeBuild' [4].
If you have any questions or concerns, please reach out to AWS Support [5].
[1] Platform: Ubuntu 20.04 - Image: aws/codebuild/standard:5.0 - Definition: ubuntu/standard/5.0
[2] Platform: Amazon Linux 2 - Image: aws/codebuild/amazonlinux2-x86_64-standard:3.0 - Definition: al2/standard/3.0
[3] Platform: Amazon Linux 2 - Image: aws/codebuild/amazonlinux2-aarch64-standard:1.0 - Definition: al2/aarch64/standard/1.0
[4] https://docs.aws.amazon.com/codebuild/latest/userguide/build-env-ref-available.html
[5] https://aws.amazon.com/support
Sincerely,
Amazon Web Services
Amazon Web Services, Inc. is a subsidiary of Amazon.com, Inc. Amazon.com is a registered trademark of Amazon.com, Inc. This message was produced and distributed by Amazon Web Services Inc., 410 Terry Ave. North, Seattle, WA 98109-5210


Feature/bdi co  migration utility

Critical Changes
Changes
Issues Closed
New Metadata
Deleted Metadata

@psadie - I had to re-create this PR, long story!


No option to select GPUs while creating models in DIGITS

I have installed NVIDIA drivers for the associated GPU in my laptop and corresponding CUDA toolkit and set the paths in LD_LIBRARY_PATH to the cuda package in usr/local . Cuda is working fine, as can be verified using the nvcc command. However, when I launch digits-devserver, I do not see any option to use an existing GPU while creating a model. Can anyone tell me what might be missing over here?
PS: I verified that all the steps mentioned in https://github.com/NVIDIA/DIGITS/blob/master/docs/BuildDigits.md are followed!
Thanks!

I have a similar error while building DetectNet  see


Add layer management

The basic functionality from MapContrib v1 is layer management.
We need to implement this to be able to have a somewhat functional app.
Structure
Based on v1, each layer should have

name
type (overpass, osmose, csv, geojson...)
description
marker
representationType (cluster or heatmap)
isVisible
sources

I feel these are not necessary:

popup content (info could be displayed on the sidebar)
min zoom level (this could be a general option, or even not an option at all)

Sources
The sources (plural) is mainly to allow one layer to have multiple sources. This is interesting especially for Osmose, because this will allow to regroup similar osmose items under the same layer.
We could accept multiple sources only for osmose layers.
The sources field will hold either the overpass query, the osmose items, or the files' path.
UX
We could have a layer edition right sidebar for creation/modification, and a quick left toolbar for toggle display and representation type.

I totally agree on that first step to be functional. And your proposition to implement multiple sources per layer is a great idea but I think we should push it further.
In your proposal you talk about specific layer types (overpass, files, etc.) and multiple sources (and source types). It is confused IMHO.
What do you think about having:

Layers

which handle name, description, visibility, representation type

Sources

which have types, marker customization, visibility (too), content display (former popup content)

The content display is really important to the theme creators, but the popup form is really annoying and has to be removed. Sidebars and modals are sufficient enough.

@iOiurson I will work on that today. Since I don't see any branch related to that issue, I assume there is no started work on your side. Is it correct?
My goal is to publish a first version of MapContrib Next very soon, with a minimal layer handling.

I confirm no work has been started on my side.
Be careful though, for the osmose basic functionality, i set the store so that it stores the entire leaflet layer. I do not think this is an optimal solution for store persistance, and was planning on giving it a deeper thought.
Maybe store just the osmose item (probably better for simplicity) and recreate the layer on each render if the item has changed (but need to check on perfs).

I was thinking about tackling this baby, so that we are able to read/write layers from the database with MC Next.
Layers server-side
What should I expect from the server in terms of layer data ?
How is it structured ?
What's the API ? (I have tried to read the api folder from MC, but I must admit it's a bit harsh...)
Is the server capable of handling sources ? (My guess is no)
One thought about layers and sources.
In my opinion, layers should handle all about the type and representation (marker, color, ...), and sources should only be about the data sources (and consequently the leaflet-layer).
When I brought up the concept of sources, I had Osmose in mind and the fact that one could want to have all School items (Osmose items can be very similar) into one single layer, and all being represented by the same marker. This leads to having multiple sources for one layer.
The other case that could benefit from having multiple sources is external files. We can think of some person that has data of the same kind in different files, and that would make sense to import all the data into one single layer, represented by the same marker.
But I think that in the vast majority of cases, people shouldn't have multiple sources per layer. If they absolutely want to, ok, but a layer represents one kind of data, and has one style. If you want multiple styles, you probably have different kinds of data, and should have different layers too then.
This would lead to such structure, layers and sources being 2 different stores:
Layers

id
name
type (overpass, osmose, csv, geojson..., one layer, one type)
description
marker
representationType (cluster or heatmap)
isVisible
sources (array of sources id)

Sources

id
type
origin (the Osmose item, the Overpass request, the file name,...)
features

Great to hear! :)
I understand your point but I kind of feeling it weird to seperate the data type (in the layer) and the data ID (item/request in the source). Such hard bond should be avoided IMHO.
What about that kind of use case:
I'm concerned about the environment, so I create an MC theme to improve the OSM database about that.
I want to improve several things: trees, parks, etc.
So I would like to have a layer per category of things: one for trees, one for parks and so on.
In each layer, it might make sense to have multiple source types and customizations:

an Overpass request to see the current data state in OSM
some Osmose items to see what can be easily improved
etc.

That way I can hide/show the layers/things I want to focus on (a main subject of contribution for today) and I also can see a visual difference between Overpass and Osmose data, making it easier to me to navigate and analyse.
In the end, I think we should remove constraints/bond as much as we can, without sacrifying the UX of casual users nor expert users.
What bout that?

Put the data type in the source
Handle a customization in the layer to apply to all the sources by default
Handle a customization in the source to override the default if the user wants to make a difference

That way, all the users/use cases should be addressed don't you think?

Ok I get your point.
I still believe that sources should have nothing to do with visual customization (marker, isVisible, ...). Layers only should handle that.
Let's take the use case you provided.
The user creates a layer for OSM trees, and adds the corresponding Overpass request as source.
The user creates a layer for osmose trees, and adds the 3 existing Osmose ids as sources.
The user creates a layer for custom points (his personal feelings about missing trees for instance), using a local JSON for source.
The same thing happens for parks, trash bins.
The user now has 9 layers, connected to 15 sources (because 3 osmose sources each time).
For UX purposes, he needs to separate these 9 layers into 3.
For this case, we can imagine that the user creates a meta layer, which would be a group/layer of layers, with no sources, but all the display functionalities of layers: markers, isVisible, ... that would be the default styles for child layers if no style is defined.
Of course, the UX of such story would need to be well designed to make sure this stays comfortable to do. We can imagine a folder-like display of layers, that we could drag and drop.
I really have a bad feeling about mixing sources and layers in terms of display controls.
And about your concern of data types being in the layers, this could be a "fake" property of the layer, coming directly from the source just for user information purposes.
What do you think ?

I will work on that soon. Reassign it to me if it's ok for you @iOiurson

The repository moved to https://gitlab.com/mapcontrib/mapcontrib.next.


Re-Captcha

Thanks for this beautiful and nice template!
I don't know if this is an issue, maybe more a question, i try to use google re-captcha in contact form, but without success, can you help to solve this?

Your questions has nothing to do with the startbootstrap-agency template itself.
If you are not able to implement this feature on your own, search on google for someone who implement it for you - but not here.


Finding difficult to make it work with Python3

Thanks for your effort to bring in Vizdxp. Appreciate your due diligence in building this framework.
My issue is about making it work with Python3 which seems to be not working.

ng-2.4.7 pyrsistent-0.16.0 pyzmq-19.0.2 retrying-1.3.3 streamlit-0.65.2 terminado-0.8.3 testpath-0.4.4 toml-0.10.1 toolz-0.10.0 tornado-6.0.4 traitlets-4.3.3 tzlocal-2.1 validators-0.18.0 vizdxp-0.0.5 watchdog-0.10.3 wcwidth-0.2.5 webencodings-0.5.1 widgetsnbextension-3.5.1
WARNING: You are using pip version 20.1.1; however, version 20.2.2 is available.
You should consider upgrading via the '/Library/Frameworks/Python.framework/Versions/3.8/bin/python3.8 -m pip install --upgrade pip' command.
DAdoor:~ dixitac$ pip install --upgrade pip
DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Collecting pip
Downloading https://files.pythonhosted.org/packages/5a/4a/39400ff9b36e719bdf8f31c99fe1fa7842a42fa77432e584f707a5080063/pip-20.2.2-py2.py3-none-any.whl (1.5MB)
|████████████████████████████████| 1.5MB 996kB/s
Installing collected packages: pip
Found existing installation: pip 19.2.3
Uninstalling pip-19.2.3:
ERROR: Could not install packages due to an EnvironmentError: [Errno 13] Permission denied: '/Library/Python/2.7/site-packages/pip-19.2.3-py2.7.egg/EGG-INFO/PKG-INFO'
Consider using the --user option or check the permissions.

DEPRECATION: Python 2.7 will reach the end of its life on January 1st, 2020. Please upgrade your Python as Python 2.7 won't be maintained after that date. A future version of pip will drop support for Python 2.7. More details about Python 2 support in pip, can be found at https://pip.pypa.io/en/latest/development/release-process/#python-2-support
Collecting vizdxp
ERROR: Could not find a version that satisfies the requirement vizdxp (from versions: none)
ERROR: No matching distribution found for vizdxp

close

Thanks @DikshithAC for trying vizdxp. Hopefully you could try the package successfully, if you are facing any other issues, pls log it. Will do the needful


NVM and PATH issues

VSCode Version: 1.26.1
OS Version: Ubuntu 18.04

Suggested by @ruslan-bikkinin to bring the conversation over here.
Please see: https://github.com/Microsoft/vscode-react-native/issues/755

Does this issue occur when all extensions are disabled?: Yes

The problem very likely lies in
# If not running interactively, don't do anything
case $- in
    *i*) ;;
      *) return;;
esac

Try moving the NVM setup code before that snippet in your .bashrc, does that fix it?

Hi @joaomoreno, Ruslan from vscode-react-native is here. If you need any help/comments from my side feel free to ask me.

@joaomoreno Just tried that, still no luck :(.

@joaomoreno That may have worked! I normally get the errors 'cannot find flow in path/cannot find node in path' but that no longer appears. I'm going to try and see whether command palette and debugger works tomorrow.

Hi there,
I faced pretty similar issue while running react-native project "Debug iOS" with vscode-react-native extension.
I did not manage to determine what is a root of an issue. Since here are representatives of both teams I'd like to add some info.
Issue: console.log('something') did not print message into a 'DEBUG CONSOLE'. Debug logtrace of react-native project do not appear in a 'DEBUG CONSOLE'. All messages appear, if debug remotely via chrome.
Additional info when start debugging on iOS there is an exception related to web socket appears. Since it's a clean project without web-socket specific code, maybe VS Code can't instantiate connection with an RN debug module on simulator?
Conditions:

VS Code 1.26.1
No nvm (completely uninstalled, while tried to fix an issue)
Fresh install of node 8.11.4 from nodejs.org
Fresh RN project via react-native init helloworld

SOLUTION:

Uninstall VS Code 1.26.1
Install VS Code 1.25.1

NOTES
I did not have any issues until I upgraded VS Code to 1.26.1. Even though I had an nvm installed before.
If you need some additional info/logs from my side - feel free to contact me.

@joaomoreno ok, thank you

@joaomoreno Everything works as long as I initially launch code from the terminal. I no longer have to set nvm use default every time before launching vscode and things seem to still work even when I load new folders or workspaces.

So, even after moving that code before # If not running interactively, don't do anything, it still doesn't work when not launching from the terminal?

@dominictwlee did you manage to resolve this or still waiting for help?
@joaomoreno could you please reopen this issue?

If you follow the discussion, you'll realize the issue is more a user configuration error than a VS Code issue.

@joaomoreno That may have worked! I normally get the errors 'cannot find flow in path/cannot find node in path' but that no longer appears. I'm going to try and see whether command palette and debugger works tomorrow.

@dominictwlee Did you follow up on our investigation here?

@joaomoreno Command palette and debugger still doesn't work unless vscode is launched from the terminal.

Have you tried messing around with your .bashrc to figure out where it bails out?

Just heads up @joaomoreno @ruslan-bikkinin even with vscode being launched from terminal it no longer works.

@dominictwlee did you check whether your case related with the known nvm issues:

https://github.com/creationix/nvm#compatibility-issues
https://github.com/creationix/nvm#problems (last item in the list)?


taxon restriction "host cell nucleus"

Re
https://github.com/geneontology/go-annotation/issues/3170
Can we get a taxon restriction for "host cell nucleus"
There are now. 54,000 annotations in GOA for vertebrates.
Should be able to add "never vertebrates"?
Can add never in S. pombe and never in S. cerevisiae. (Cerevisiae can cause opportunistic infections, but this does not appear to be by entering cells, it is more 'immunogenic' as far as I can tell.
https://www.ebi.ac.uk/QuickGO/annotations?goUsage=descendants&goUsageRelationships=is_a,part_of,occurs_in&goId=GO:0042025&taxonId=9606&taxonUsage=descendants
Question, are taxon restrictions now a hard check? do we drop violating annotations immediately?

Probably only unicellular organisms can enter other cells ? Maybe we can even use 'never in Opisthokonta' - since even if fungus can enter cells, they probably do not enter the nucleus ?
@mgiglio99
@dsiegele
Any suggestions ?

@Achchuthan How about eukaryotic parasites ? Do they live/transit in specific organelles?

From PMID:26195306, "Microsporidia: Eukaryotic Intracellular Parasites Shaped by Gene Loss and Horizontal Gene Transfers"
Living inside other cells appears to have triggered many reductive changes in the genomes of microsporidia, but this lifestyle also offers unique opportunities to acquire new genetic information. Specifically, intracellular pathogens can be in physical contact with the genetic material of the host (e.g., the microsporidium Nucleospora obligatorily develops inside host nuclei, and others such as Nosema and Encephalitozoon use the nucleus as the developmental niche on occasion) or of coinfecting organisms.
So yes, eukaryotic parasites do specifically enter the host cell nucleus.

Thanks for the feedback @addiehl
I used NCBITaxon:33154	Opisthokonta, so I think the case you mention is covered.
Thanks, Pascale

Hi @pgaudet
Sorry for the delayed response. Yes, protozoan parasites such as Plamodium and Trypanosoma do transit into specific organelles. In addition, they can also target their proteins into organelles even if they reside in parasitophorous vacuole/ cytosol.
Thanks,
Achchuthan

Thanks @Achchuthan
Does that include any Opisthokonta ?

@pgaudet, they do not include Opisthokonta

Changed to 'never in Vertebrata ' after query #19742
Thanks, Pascale


The edgemesh-agent of the edge node reports an error

When I deployed the agent, the agent of the edge node reported an error as follows. What is the reason?
I1221 03:39:10.863914       1 nocamanager.go:44] Private key exist, skip generate
I1221 03:39:10.866516       1 module.go:34] Module tunnelagent registered successfully
I1221 03:39:10.866537       1 server.go:119] [4] Install go-chassis plugins
I1221 03:39:10.866781       1 log.go:184] DEBUG: Installed strategy plugin: [RoundRobin].
I1221 03:39:10.866802       1 log.go:184] DEBUG: Installed strategy plugin: [Random].
I1221 03:39:10.866806       1 log.go:184] DEBUG: Installed strategy plugin: [ConsistentHash].
I1221 03:39:10.866865       1 log.go:184] DEBUG: ConfigurationFactory Initiated
I1221 03:39:10.866873       1 log.go:184] INFO: Configuration files: []
I1221 03:39:10.867410       1 log.go:184] WARN: empty configurtion from [FileSource]
I1221 03:39:10.867430       1 log.go:184] INFO: invoke dynamic handler:FileSource
I1221 03:39:10.867482       1 log.go:184] INFO: archaius init success
I1221 03:39:10.867488       1 server.go:124] [5] Start informers manager
I1221 03:39:10.867667       1 log.go:184] INFO: create new watcher
W1221 03:39:10.869020       1 shared_informer.go:372] The sharedIndexInformer has started, run more than once is not allowed
W1221 03:39:10.869039       1 shared_informer.go:372] The sharedIndexInformer has started, run more than once is not allowed
W1221 03:39:10.869164       1 shared_informer.go:372] The sharedIndexInformer has started, run more than once is not allowed
W1221 03:39:10.869183       1 shared_informer.go:372] The sharedIndexInformer has started, run more than once is not allowed
I1221 03:39:11.068423       1 server.go:128] [6] Start all modules
I1221 03:39:11.068490       1 core.go:24] Starting module edgedns
I1221 03:39:11.068667       1 core.go:24] Starting module edgeproxy
I1221 03:39:11.069096       1 core.go:24] Starting module tunnelagent
I1221 03:39:11.069150       1 module.go:55] Runs CoreDNS v1.8.7 as a node-level dns
W1221 03:39:11.069374       1 tunnel.go:28] Connection between agent and server [/ip4/<IP_ADDRESS>/tcp/20004 /ip4/<IP_ADDRESS>/tcp/20004 /ip4/<IP_ADDRESS>/tcp/20004] is not established, try connect
I1221 03:39:11.069413       1 tunnel.go:31] Tunnel agent connecting to tunnel server
I1221 03:39:11.075171       1 tunnel.go:50] agent success connected to server [/ip4/<IP_ADDRESS>/tcp/20004 /ip4/<IP_ADDRESS>/tcp/20004 /ip4/<IP_ADDRESS>/tcp/20004]
W1221 03:39:11.083984       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1221 03:39:11.084084       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
W1221 03:39:12.280063       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1221 03:39:12.280105       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
W1221 03:39:14.487879       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1221 03:39:14.487927       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
[WARNING] plugin/kubernetes: starting server with unsynced Kubernetes API
.:53 on <IP_ADDRESS>
[INFO] plugin/reload: Running configuration MD5 = 870d75cba1333871a6b2a32d5bbf8835
CoreDNS-1.8.7
linux/amd64, go1.17.5,
[INFO] <IP_ADDRESS>:58311 - 65041 "HINFO IN<PHONE_NUMBER>659534307.5681697611251028163. udp 57 false 512" NXDOMAIN qr,rd,ra 132 0.003606863s
W1221 03:39:20.138248       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1221 03:39:20.138302       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
W1221 03:39:30.684671       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1221 03:39:30.684703       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"

Try to add namespaces RBAC to cloudcore serviceaccount.

Try to add namespaces RBAC to cloudcore's clusterrole.

It seems that the clusterrole of edgemesh-agent needs to add namespaces. I'm going to fix this problem right away.

/assign

/assign

Added, no effect

the clusterrole of edgemesh-agent needs to add namespaces

the clusterrole of edgemesh-agent needs to add namespaces
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
name: {{ .Release.Name }}-agent
labels:
k8s-app: kubeedge
kubeedge: edgemesh-agent
rules:

apiGroups: [""]
resources: ["pods", "endpoints","namespaces"]
verbs: ["get", "list", "watch"]
apiGroups: [""]
resources: ["secrets", "services", "configmaps"]
verbs: ["get", "list", "watch", "create", "update"]
apiGroups: ["networking.istio.io"]
resources: ["*"]
verbs: ["get", "list", "watch"]

t *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1222 09:24:00.513023       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
[WARNING] plugin/kubernetes: starting server with unsynced Kubernetes API
.:53 on <IP_ADDRESS>
[INFO] plugin/reload: Running configuration MD5 = 870d75cba1333871a6b2a32d5bbf8835
CoreDNS-1.8.7
linux/amd64, go1.17.5,
[INFO] <IP_ADDRESS>:41533 - 6752 "HINFO IN<PHONE_NUMBER>081795990.7055275809264103211. udp 57 false 512" NXDOMAIN qr,rd,ra 132 0.002663423s
W1222 09:24:04.943876       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1222 09:24:04.943943       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
W1222 09:24:14.245973       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1222 09:24:14.246009       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
W1222 09:24:33.512288       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1222 09:24:33.512334       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"

What version of kubenertes and kubeedge did you use? I used k8s 1.21.0 and kubeedge 1.9.1 and meet the same errors when deploy edgemesh agent.

k8s：1.19.8
kubeedge：1.8.2
edgemesh：images  latest

What version of kubenertes and kubeedge did you use? I used k8s 1.21.0 and kubeedge 1.9.1 and meet the same errors when deploy edgemesh agent.

k8s：1.19.8
kubeedge：1.8.2
edgemesh：images latest

fix this issue in PR #256

fix this issue in PR #256

When I deploy the helm package of the main branch, I still report an error
E1223 09:13:01.304906       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
W1223 09:13:01.861472       1 tunnel.go:28] Connection between agent and server [/ip4/<IP_ADDRESS>/tcp/20004 /ip4/<IP_ADDRESS>/tcp/20004] is not established, try connect
I1223 09:13:01.861505       1 tunnel.go:31] Tunnel agent connecting to tunnel server
W1223 09:13:01.862294       1 tunnel.go:34] Connect to server err: failed to dial Qmbe93hGR9Q5QgwdjUdPDQFapZfYNwKBrQQvTFqMbZE6ny: all dials failed
  * [/ip4/<IP_ADDRESS>/tcp/20004] dial tcp4 <IP_ADDRESS>:20004: connect: connection refused
  * [/ip4/<IP_ADDRESS>/tcp/20004] dial tcp4 <IP_ADDRESS>:20004: connect: connection refused
I1223 09:13:03.863105       1 tunnel.go:31] Tunnel agent connecting to tunnel server
W1223 09:13:03.863337       1 tunnel.go:34] Connect to server err: dial backoff
I1223 09:13:05.863495       1 tunnel.go:31] Tunnel agent connecting to tunnel server
W1223 09:13:05.863675       1 tunnel.go:34] Connect to server err: dial backoff
W1223 09:13:17.864274       1 tunnel.go:28] Connection between agent and server [/ip4/<IP_ADDRESS>/tcp/20004 /ip4/<IP_ADDRESS>/tcp/20004] is not established, try connect
I1223 09:13:17.864310       1 tunnel.go:31] Tunnel agent connecting to tunnel server
I1223 09:13:17.867193       1 tunnel.go:50] agent success connected to server [/ip4/<IP_ADDRESS>/tcp/20004 /ip4/<IP_ADDRESS>/tcp/20004]
W1223 09:13:47.068996       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1223 09:13:47.069046       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
W1223 09:14:28.892018       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1223 09:14:28.892062       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
W1223 09:15:09.376970       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1223 09:15:09.377019       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
W1223 09:15:47.187998       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1223 09:15:47.188036       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
W1223 09:16:31.788130       1 reflector.go:324] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"
E1223 09:16:31.788191       1 reflector.go:138] github.com/coredns/coredns/plugin/kubernetes/controller.go:408: Failed to watch *v1.Namespace: failed to list *v1.Namespace: no kind "NamespacList" is registered for version "v1" in scheme "k8s.io/client-go/kubernetes/scheme/register.go:74"

Is this edgemesh-agent on the cloud or edgemesh-agent on the edge?

I see the clusterrole of cloudcore in: https://github.com/kubeedge/kubeedge/blob/master/build/cloud/03-clusterrole.yaml
should "list" be added in "namespaces"?
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: cloudcore
  labels:
    k8s-app: kubeedge
    kubeedge: cloudcore
rules:
- apiGroups: [""]
  resources: ["nodes", "nodes/status", "serviceaccounts/token", "configmaps", "pods", "pods/status", "secrets", "endpoints", "services", "persistentvolumes", "persistentvolumeclaims"]
  verbs: ["get", "list", "watch", "create", "update"]
- apiGroups: [""]
  resources: ["namespaces"]
  verbs: ["get", "create"]       <---------------------------------------  should "list" be added here
- apiGroups: [""]
  resources: ["nodes", "pods/status"]
  verbs: ["patch"]
- apiGroups: [""]
  resources: ["pods"]
  verbs: ["delete"]
- apiGroups: ["coordination.k8s.io"]
  resources: ["leases"]
  verbs: ["get", "list", "watch", "create", "update"]
- apiGroups: ["devices.kubeedge.io"]
  resources: ["devices", "devicemodels", "devices/status", "devicemodels/status"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["reliablesyncs.kubeedge.io"]
  resources: ["objectsyncs", "clusterobjectsyncs", "objectsyncs/status", "clusterobjectsyncs/status"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["rules.kubeedge.io"]
  resources: ["rules", "ruleendpoints", "rules/status", "ruleendpoints/status"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["apiextensions.k8s.io"]
  resources: ["customresourcedefinitions"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["networking.istio.io"]
  resources: ["*"]
  verbs: ["get", "list", "watch"]

I see the clusterrole of cloudcore in: https://github.com/kubeedge/kubeedge/blob/master/build/cloud/03-clusterrole.yaml
Should "list" and "watch" be added in "namespaces"?
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: cloudcore
  labels:
    k8s-app: kubeedge
    kubeedge: cloudcore
rules:
- apiGroups: [""]
  resources: ["nodes", "nodes/status", "serviceaccounts/token", "configmaps", "pods", "pods/status", "secrets", "endpoints", "services", "persistentvolumes", "persistentvolumeclaims"]
  verbs: ["get", "list", "watch", "create", "update"]
- apiGroups: [""]
  resources: ["namespaces"]
  verbs: ["get", "create"]       <---------------------------------------  should "list" and "watch" be added here?
- apiGroups: [""]
  resources: ["nodes", "pods/status"]
  verbs: ["patch"]
- apiGroups: [""]
  resources: ["pods"]
  verbs: ["delete"]
- apiGroups: ["coordination.k8s.io"]
  resources: ["leases"]
  verbs: ["get", "list", "watch", "create", "update"]
- apiGroups: ["devices.kubeedge.io"]
  resources: ["devices", "devicemodels", "devices/status", "devicemodels/status"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["reliablesyncs.kubeedge.io"]
  resources: ["objectsyncs", "clusterobjectsyncs", "objectsyncs/status", "clusterobjectsyncs/status"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["rules.kubeedge.io"]
  resources: ["rules", "ruleendpoints", "rules/status", "ruleendpoints/status"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["apiextensions.k8s.io"]
  resources: ["customresourcedefinitions"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["networking.istio.io"]
  resources: ["*"]
  verbs: ["get", "list", "watch"]

This kind of operation is fine

This kind of operation is fine

@lgy1027 Do you mean that after modifying 03-clusterrole.yaml above, edgemesh will run normally?

This kind of operation is fine

@lgy1027 Do you mean that after modifying 03-clusterrole.yaml above, edgemesh will run normally?

yes

Great, and maybe we can close this issue.

I see the clusterrole of cloudcore in: https://github.com/kubeedge/kubeedge/blob/master/build/cloud/03-clusterrole.yaml
Should "list" and "watch" be added in "namespaces"?
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRole
metadata:
  name: cloudcore
  labels:
    k8s-app: kubeedge
    kubeedge: cloudcore
rules:
- apiGroups: [""]
  resources: ["nodes", "nodes/status", "serviceaccounts/token", "configmaps", "pods", "pods/status", "secrets", "endpoints", "services", "persistentvolumes", "persistentvolumeclaims"]
  verbs: ["get", "list", "watch", "create", "update"]
- apiGroups: [""]
  resources: ["namespaces"]
  verbs: ["get", "create"]       <---------------------------------------  should "list" and "watch" be added here?
- apiGroups: [""]
  resources: ["nodes", "pods/status"]
  verbs: ["patch"]
- apiGroups: [""]
  resources: ["pods"]
  verbs: ["delete"]
- apiGroups: ["coordination.k8s.io"]
  resources: ["leases"]
  verbs: ["get", "list", "watch", "create", "update"]
- apiGroups: ["devices.kubeedge.io"]
  resources: ["devices", "devicemodels", "devices/status", "devicemodels/status"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["reliablesyncs.kubeedge.io"]
  resources: ["objectsyncs", "clusterobjectsyncs", "objectsyncs/status", "clusterobjectsyncs/status"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["rules.kubeedge.io"]
  resources: ["rules", "ruleendpoints", "rules/status", "ruleendpoints/status"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["apiextensions.k8s.io"]
  resources: ["customresourcedefinitions"]
  verbs: ["get", "list", "watch", "create", "update", "patch", "delete"]
- apiGroups: ["networking.istio.io"]
  resources: ["*"]
  verbs: ["get", "list", "watch"]

This kind of operation is fine

Hi, when did you modify 03.clusterrole.yaml? before running keadm init or what? And I didn't see this file in my system, can you show me its directory? Thank you!!!

@pi-bit  Try to kubectl get clusterrole | grep cloudcore and kubectl edit clusterrole cloudcore.

I tried kubectl edit clusterrole cloudcore but it gets below errors.

So I create a file name 03.clusterrole.yaml with above content, then kubectl apply -f 03.clusterrole.yaml? Is it oke to do that?
Then I deploy edgemesh-agent again and all pods go to this errors. (Its works normal before apply edgemesh-agent)

K8s: 1.21.0
Kubeedge" 1.9.1
Edgemesh:latest

@pi-bit  Is your cloudcore startup method a container or process?

I used container to start up cloudcore.
Edgemesh used to work normally with k8s 1.21.0 and kubeedge 1.8.1, but now I can't init the keadm 1.8.1 version anymore. just keadm 1.9.1 init is fine. So I think kubeege 1.9.1 is not compatible with edgemesh?

I used container to start up cloudcore.

How did you install cloudcore and why your kubeedge cluster does not have the clusterrule of cloudcore?

So I think kubeege 1.9.1 is not compatible with edgemesh?

I don't think so.  According to issue kubeedge/kubeedge#3489, it may be a kubeedge bug.

https://kkh913.github.io/kubernetes/kubeedge-(2)-installation-on-ubuntu-/
I follow this instruction to install cloudcore (keadm). Sorry for korean's blog.

It's OK, but I am not sure whether it has expired.
If you use a container to install cloudcore, you can refer to https://github.com/kubeedge/kubeedge/tree/master/build/cloud.
PS: KubeEdge official document: https://kubeedge.io/en/

fix in pr: https://github.com/kubeedge/kubeedge/pull/3533
/close


workflows: add stale pr/issue detection

let's start in the shallow end...

whats the criteria for it becoming stale?

Would be great to revive this! The defaults can be seen here: https://github.com/actions/stale#arguments
My proposed configuration:
days-before-stale: 90
days-before-close: 30

Addressing this with @lightninglabs-deploy bot.


Key is missing from snippet

WHen I go to upload page I get Key is missing from snippet error in js console.
https://nullvideo.com/upload
vendors~rollbar.noconflict.umd.min.b85c4defab2fb2e589f8.js:1 Key is missing from snippet

Looks like it's wrong logic here:
middlewares/custom/zopim.js:1
I can fix this a bit later should only take a second

what does zopim do? i disabled it.

It's live chat support. I'll fix this logic next coding session for NodeTube I do.


Implement GET /api/clients in Haskell Scotty (WIP)

@BartMassey My first Haskell code! I'm starting to get a feel for the basics. Started with some pretty ugly code, and managed to refine it down to this. Before I try to introduce a db connection and pull some real data, what do you think? What changes would you make at this point?

@BartMassey Hit a wall here, just trying to get a simple value out of mysql. I'm pretty sure I'm blocked on a lack of understanding monads. I can get an IO String out of mysql but I'm not sure how to turn that into a String. Reading through some documentation, I thought that forM and mapM are supposed to help cross what seems like the monad "bridge", but they're not doing the trick. I suspect my mental model   is not correct.

Yeah, the monad stuff is pretty confusing. The short answer is that you can't get the String out of an IO String: that restriction is there for your protection :-). Instead, you have to use the IO String inside an IO monad (or a monad that can work with one) and use the <- operator with the do notation to work with the String. Anyway, query_ returns a 64-bit integer, not a String in this context.
Not sure what happened to my old patches, but I've pushed a bunch of changes onto haskell_scotty for you to look at. The description of the big one should help explain what's going on.
The short answer is that I'm using pattern matching in fetchId to get the integer client id out, returning it wrapped in the IO monad, then using liftIO inside the clients action handler to get the thing wrapped in an ActionM monad instead of just IO; then <- can unwrap the integer for use in constructing the Client record for the JSON.
It gets easier, I promise. :-)
BTW, I also modified fetchId to hit a passworded test database. Be careful out there.
So I'm closing this pull request without merging it, I think, and just leaving my commits instead. Sorry my commits are such a mess. You can refactor them if it bothers you. At least they also brought the branch up to date with master.

Thanks, Bart! I think this will get me moving again, or at least it'll give me something concrete to study as I try to wrap my brain around monads. My mental model is now that monads "infect" values. Once a value is infected by a monad, everything that consumes it downstream has to be monad-infected as well, which means everything that consumes them has to be monad-infected, and so on. Is this somewhat accurate? Reminds me of JavaScript async functions, which are viral in the same way. :fearful:

This is pretty accurate. You can extract a value from some monads (usually by a "run" function that executes the monadic code and returns the result). The IO monad is not one of them.

Cool, I'm starting to get it. Just pushed a commit that changes the MySQL access credentials from file to environment variables, and I think I understand everything I've done! It's happening!!

:tada: :neckbeard:

Crap just realized this merge was premature... still tons of slime in the index action. Reverting.


Docstring examples

Added docstring examples to some string methods (#6793)
[ ]Closes #xxxx
[ ]Tests added
[ ]User visible changes (including notable bug fixes) are documented in whats-new.rst
[ ]New functions/methods are listed in api.rst

Thanks @harshitha1201 Nice work!


Security log + Dateformat at logger.conf template to work with Fail2ban

@TECH7Fox and @felipecrs, please, take a look at config.yaml and logger.conf.gtpl.
Refs: https://www.fail2ban.org/wiki/index.php/Asterisk
Fail2ban + logger.conf configurable #178

We can't really change the log_level options because it's also used for other things.
Maybe a new option like Security_messages or something? (Maybe not the best naming but you get the point)
Rest looks good.
Btw, just for me, does fail2ban read the asterisk messages? I thought it would use the console.
Where do the messages even go?

Maybe a new option like Security_messages or something? (Maybe not the best naming but you get the point)

Are these logs annoying? If they aren't much perhaps we can add this by default without any option.

Are these logs annoying? If they aren't much perhaps we can add this by default without any option.

Not sure. Maybe if you get a lot of bots from different ip's? But if they are going to messages, the user won't notice them anyways right?
Maybe we should add security to some higher log levels. Like from info to trace?

@TECH7Fox

We can't really change the log_level options because it's also used for other things. Maybe a new option like Security_messages or something? (Maybe not the best naming but you get the point)
Rest looks good.

Yeah, that´s good.

Btw, just for me, does fail2ban read the asterisk messages?

I think do so.

I thought it would use the console. Where do the messages even go?

Maybe this path?
First link:
; Directory for log files is configures in asterisk.conf
; option astlogdir
Second link:
astlogdir => /var/log/asterisk
@felipecrs

Are these logs annoying? If they aren't much perhaps we can add this by default without any option.

My miniPC (8GB / 128GB) even crashed due to brute force attack.

Maybe we should also add security to some higher log levels. Like from info to trace?

It might be like that, and there is another option:
security.log => security
A security file could be generated in the folder, couldn't it?

My miniPC (8GB / 128GB) even crashed due to brute force attack.

So ,because the security messages got in the console it crashed when you got brute forced because of the amount of logs?
Then we should probably not include it if it is that many messages right?

A security file could be generated in the folder, couldn't it?

Yeah, but if fail2ban needs to read those updated files we first need to make a symlink from the log file to something like /config/asterisk/logs. Then we could also always keep that enabled since it doesn't use the console at all.

So ,because the security messages got in the console it crashed when you got brute forced because of the amount of logs? Then we should probably not include it if it is that many messages right?

It could be like that too.

Yeah, but if fail2ban needs to read those updated files we first need to make a symlink from the log file to something like /config/asterisk/logs. Then we could also always keep that enabled since it doesn't use the console at all.

Nice, I got it.
Off: We can integrate HA and Fail2ban

Guys, let's please try to have this finished for 3.0.0.


botbuilder-dialogs {legacy-install-failure}

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
What package version of the SDK are you using.
Bot-builder-Samples/multi-turn-prompt
Describe the bug
Give a clear and concise description of what the bug is.
I was installing botbuilder-dialog using "pip install botbuilder-dialog==4.14.0 or 4.14.2".
but i am unable to install this module, as I encountered this error
"legacy-install-failure"
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Give a clear and concise description of what you expected to happen.
I am expecting the module to be installed, so that i can able to run the multi-turn-prompt bot
Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here.

pip install botbuilder-dialog==4.14.0 or 4.14.2

@SahuSomesh, can you verify for me if this is the command you actually used? I only ask as the package you have in the command should be botbuilder-dialogs (with an 's'), instead of botbuilder-dialog.
Also, I'm not sure if you are intending the 'or' in the install command to work or if that is just informational. But, if you are intending to have two versions installed, please read this Stack Overflow post for clarification on how you could achieve this. The statement you have above will not work, as-is.

pip install botbuilder-dialog==4.14.0 or 4.14.2

@SahuSomesh, can you verify for me if this is the command you actually used? I only ask as the package you have in the command should be botbuilder-dialogs (with an 's'), instead of botbuilder-dialog.
Also, I'm not sure if you are intending the 'or' in the install command to work or if that is just informational. But, if you are intending to have two versions installed, please read this Stack Overflow post for clarification on how you could achieve this. The statement you have above will not work, as-is.

Hey @stevkan I used this command
"pip install botbuilder-dialogs==4.14.0" this is not working so I have used this command
"pip install botbuilder-dialogs==4.14.2" this is also not working.
I have also tried to use this command "pip install botbuilder-dialogs" but i am unable to install the module.
and yeah that 'or' in the install command is just for informational purpose.

@SahuSomesh - Unfortunately, I am unable to repro the issue. I can install both versions of the botbuilder-dialogs library without issue. Looking at the attached image of the error you are receiving, it mentions a 'legacy-install-failure' to which I see this when I install:
Using legacy 'setup.py install' for aiounittest, since package 'wheel' is not installed.
Using legacy 'setup.py install' for regex, since package 'wheel' is not installed.
Using legacy 'setup.py install' for emoji, since package 'wheel' is not installed.
Using legacy 'setup.py install' for grapheme, since package 'wheel' is not installed.

I am using version Python version 3.10.2 and looking in Python's install folder in 'Project Files', I can find the 'setup.py' script located in a couple different folders (I'm not sure which is referenced). Perhaps verify that you have these files installed?

You can also double check that the environment settings are setup correctly for Python so that all commands are available. I have the following in my system environment path (Windows system).
C:\Program Files\Python310\Scripts\
C:\Program Files\Python310\

Lastly, I also noticed in the attached image that your version of 'pip' is outdated. You may want to try updating that, in case that is a factor. That being said, I currently have pip version 21.2.4.

Hey @stevkan Thanks for updating,
i will try to update pip and also try to install the wheel package.
Thanks :)


chore: fix warnings

Related issue(s)

Resolves #1532
Resolves #1533
Resolves #1528

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

6 of 6 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.008%) to 92.231%

Totals

Change from base Build<PHONE_NUMBER>:
-0.008%

Covered Lines:
5276

Relevant Lines:
5578

💛  - Coveralls


Dev ram/message parcer

Help to create a function & way to get and show the data from the JSON file scraped

Is ocurring something in here, in my code happens the same.
The data in some files is obtained corrected, but in the last, it doesn't. It isn't obtaining the data, because if the cell is empty, the title should have '---' as a description.


Normalize bootstrappers

Changes
Remove internal Artisan mode from main binary
Because there's no reason to clutter the main entry point with local development code.
Updates to Hyde binary

Use require once instead of require
Add recursion guard

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (55d358e) 93.69% compared to head (dcb8a5f) 93.69%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##             master       #9   +/-   ##
=========================================
  Coverage     93.69%   93.69%
  Complexity       22       22
=========================================
  Files             5        5
  Lines           111      111
=========================================
  Hits            104      104
  Misses            7        7

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


[torrserver] Chart init

Description of the change
Added new chart to stream torrents to m3u
Checklist

[X] Chart version bumped in Chart.yaml according to semver.
[X] Title of the PR starts with chart name (e.g. [home-assistant])
[X] Variables are documented in the README.md (this can be done with using our helm-docs wrapper ./hack/gen-helm-docs.sh stable <chart>)

It's not really great form to be bumping/tagging people after < 24 hours, since we all have other responsibilities as well ;)
I'll try to take a look at the PR later today/this evening though.

It's not really great form to be bumping/tagging people after < 24 hours, since we all have other responsibilities as well ;)
I'll try to take a look at the PR later today/this evening though.

Really sorry about disturbing you


What version of pnp works for SPFX 1.1.0 for SharePoint 2016 ?

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.
(DELETE THIS PARAGRAPH AFTER READING)

Category

[# ] Question
[ ] Typo
[ ] Bug
[ ] Additional article idea
[ ] Example checked item (delete this line)

For the above list, an empty checkbox is [ ] as in [SPACE]. A checked checkbox is [x] with no space between the brackets. Use the PREVIEW tab at the top right to preview the rendering before submitting your issue.
If you are planning to share a new feature request (enhancement / suggestion), please use SP Dev UserVoice at http://aka.ms/sp-dev-uservoice. (DELETE THIS PARAGRAPH AFTER READING)
(DELETE THIS PARAGRAPH AFTER READING)

Expected or Desired Behavior

If you are reporting a bug, please describe the expected behavior. If you are suggesting an enhancement please describe thoroughly the enhancement, how it can be achieved, and expected benefit.
(DELETE THIS PARAGRAPH AFTER READING)

Observed Behavior

If you are reporting a bug, please describe the behavior you expected to occur when performing the action. If you are making a suggestion, you can delete this section.
(DELETE THIS PARAGRAPH AFTER READING)

Steps to Reproduce

If you are reporting a bug please describe the steps to reproduce the bug in sufficient detail to allow testing. Only way to fix things properly, is to have sufficient details to reproduce it. If you are making a suggestion, you can delete this section.
(DELETE THIS PARAGRAPH AFTER READING)

Submission Guidelines

All suggestions or bugs are welcome, please let us know what's on your mind.
If you are reporting an issue around any of the documents or articles, please ensure that you have clear > reference on the specific file or URL, which should be fixed.
If you have technical questions about the framework, we’ll be monitoring #spfx, #spfx-webparts, and > #spfx-tooling on (SharePoint StackExchange)[http://sharepoint.stackexchange.com/]. You can also > alternatively submit your question to (SharePoint Developer group)> [https://network.office.com/t5/SharePoint-Developer/bd-p/SharePointDev] at Office Network.
Remember to include sufficient details and context.
If you have multiple suggestions or bugs please submit them in separate bugs so we can track resolution.

(DELETE THIS PARAGRAPH AFTER READING)

Thanks for your contribution! Sharing is caring.

Can you clarify what information you are looking for? Are you looking to use PnPJs with SPFx?

This question should be posted to the PNPJS project as it's specific to that library.
With that being said, I don't think there's any specific SPFx version requirement as PNPJS simply calls the REST API.


Working with more than 1 argument + slightly better code

title says all

Thank you for making tra.sh even better!


Calculate size of subscription map and retained map,

Calculate size of subscription map and retained map
Fix for reference counting in retained map

Thanks. Merged. I added one commit to apply coding rule.
Please check https://github.com/redboltz/mqtt_cpp/wiki/Coding-Rules , next time.


batch, java SDK configure for startTime

SDK config.
No API change.
Data Plane API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

API Info: The Basics
Most of the information about your service should be captured in the issue that serves as your API Spec engagement record.

Link to API Spec engagement record issue:

Is this review for (select one):

[ ] a private preview
[ ] a public preview
[ ] GA release

Change Scope
This section will help us focus on the specific parts of your API that are new or have been modified. Please share a link to the design document for the new APIs, a link to the previous API Spec document (if applicable), and the root paths that have been updated.

Design Document:
Previous API Spec Doc:
Updated paths:

Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.
Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
Swagger-Suppression-Process
to get approval.
❔Got questions? Need additional info?? We are here to help!

 Contact us!
The Azure API Review Board is dedicated to helping you create amazing APIs. You can read about our mission and learn more about our process on our wiki.

💬 Teams Channel
💌 email

Click here for links to tools, specs, guidelines & other good stuff
Tooling

Open API validation tools were run on this PR. Go here to see how to fix errors
Spectral Linting

Guidelines & Specifications

Azure REST API Guidelines
OpenAPI Style Guidelines
Azure Breaking Change Policy

Helpful Links

Schedule a data plane REST API spec review

Getting help

First, please carefully read through this PR description, from top to bottom.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.Batch

SDK would fail from
cmderr	[Java-Sdk-Automation] /mnt/vss/_work/1/s/azure-sdk-for-java/sdk/batch/azure-compute-batch/TempTypeSpecFiles/Azure.Batch/models.tsp:725:4 - error ambiguous-symbol: "nextLink" is an ambiguous name between TypeSpec.nextLink, Azure.Core.nextLink. Try using fully qualified name instead: TypeSpec.nextLink, Azure.Core.nextLink

And that is what we are bumping emitter for (and this PR unblocks Java emitter version bump).


Create VPC and endpoints for isolated sagemaker VPC

As noted in https://github.com/ministryofjustice/modernisation-platform/issues/5878, shared infrastructure isn't appropriate for the electronic-data-monitoring AWS SageMaker implementation.
This PR creates the following:

A VPC with three subnets
VPC endpoints for SageMaker as detailed [here](create interface VPC endpoints (AWS PrivateLink) to allow Studio Classic to access the following services with the corresponding service names)
Simple security group allowing all traffic inside VPC to endpoints that can be improved at a later time

@dms1981 Terraform plan evalaution detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform

@dms1981 Terraform plan evalaution detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform

@dms1981 Terraform plan evalaution detected changes to resources that require approval from a member of @ministryofjustice/modernisation-platform

Closed as this should have been created for data-platform-compute


(PEAR-1764): properly use mantine Switch component built in label

Description

change instances of mantine Switch component to use built in label in preparation for mantine patch
convert SwitchSpring to use mantine Switch component
adjust tests and test ids to better match new SwitchSpring code

Checklist

[x] Added proper unit tests
[x] Left proper TODO messages for any remaining tasks
[x] Scanned for web accessibility with aXe, and mitigated or documented
flagged issues

the issues found in wave will be fixed when we update mantine

One issue I noticed is that the original switch has a round control:

But this does not:

This should be fixed: unless @wteouchicago approves.
Additionally the new control is a bit wider than the original

@craigrbarnes @wteouchicago
The initial design of the switch buttons on the tables was square. The main reason for this decision is to differentiate these buttons from the on/off buttons on the filters and to customize the column list. Please refer to the table mockup link below and the reference screenshots for more details.
If we are going to follow this design decision, we should also ensure that the background part matches the same shape as the foreground part.
However, if this is not something we can implement, then please make the switch buttons round; otherwise, please keep the design as it is.

Table mockups: https://xd.adobe.com/view/9494a67c-0198-434e-a925-ac008f31c9b4-c1c7/grid

@cemile-ctds updated styling to have square background please re evaluate

Look really good @ocshawn. Thank you so much.


Code snippet style bug

Scroll bar should be flush to the right
Adding width:100% to .cds--snippet-container should fix this.
https://next.carbondesignsystem.com/libraries/carbon-components-angular/latest/pages/tutorial/step-1

This isn't noticeable if OS scrollbars auto hide. Since this bug is visible on desktop, we the site has a lot of code snippets, and the fix appears to be small, I'm comfortable adding it to v1.

Hey team! Please add your planning poker estimate with Zenhub @alisonjoseph @andreancardona @francinelucca @jdharvey-ibm


Tracking feature for DepoCuration

As a curator I want to view curation events in order to determine the history of a publication and its attached submission(s). Tracking used to be at study level in the Curation App but should be at the publication level in DepoCuration.
User story is here:
https://docs.google.com/document/d/153J9wSsO-tPiyc_2JdQcqU9-nWKgB6DgGJYuysV8ddY/edit?usp=sharing

Tested and working in prod


test_done

Hello @GaetanDu! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file autopycoin/models/nbeats_test.py:

Line 664:80: E501 line too long (86 > 79 characters)
Line 670:80: E501 line too long (86 > 79 characters)


Add FocalPlaneResolutionUnit

Signed-off-by: Patrick José Pereira<EMAIL_ADDRESS>

This information is necessary to calculate sensor size.

@pmoulon done.

Thanks @patrickelectric


Run Tests Against Python 3.10

Expected Behavior
Unit tests are run against python310. This would be nice to have as we're developing a runtime that uses
Actual Behavior
Unit tests don't run against 3.10
https://github.com/GoogleCloudPlatform/appengine-python-standard/blob/6ea19dde91c149398c0d9aa9b8f5c1e6e65dfd9b/.github/workflows/unit.yml#L16
CC: @shreejad @asriniva

Turns out ruamel.yaml doesn't support Python 3.10 yet, so we're waiting on that.


AKS Provisioning (iFrame)

Need to use the new aks-v2 ID

To validate:
User should be able to provision and edit, add nodepools and save a

AKS v2 hosted cluster
AKSv2 - Register cluster or import clusters

Test report:
Tested on rancher/rancher:master-head cf5a75f

Hosted AKS was succesfully provisioned and updated over Rancher - resources ok

I was unable to test adding nodepools and scaling pools due reached quota in Azure The maximum node count you can select is 1 due to the remaining quota in the selected subscription (0 cores).

Imported AKS was succesfully imported into Rancher (selected from dropdown) but the update failed - resources were ok

https://github.com/rancher/rancher/issues/33534
https://github.com/rancher/rancher/issues/33536

As the bugs are open I'm closing this one.


Migrate to Cobra

Have a Cobra implementation of the weather command just to have experience with a more popular go cli framework compared to bonzai.

Tagging some cobra repo examples:
https://github.com/alexellis/arkade/tree/master
https://github.com/rwxrob/lab/tree/b3d097cabbe7225388b1159ce801edc1de7e9912/go/cobra/simple-go
https://github.com/cli/cli/tree/trunk/pkg/cmd

Weather uses the vars branch to have persistent storage for API Key, location and region ids. Cobra has no equivalent command package. Will have to either set them as env vars or use persistent flags.

Breakdown of the current command map:

weather

site

list
find
set
forecast

I could use Viper to load in a env file from os.UserCacheDir() I can put this stuff in the app package? or make a new package called conf?

Having mixed thoughts on the project structure. Git hub gh cli groups the cmds by package and each sub command gets its own package. This does mean that you will have multiple create packages in different places for common command names. I did initially think that there would be a conflict but from go pov it would package them together during compile. Not entirely sure this is a good approach either.
Option 1:
cmd/
site/
list/
find/
Option 2:
cmd/
site.go
site/
region/

With option 2, the business logic is lifted to a higher level. Whereas with option 1, there is command level isolation. More directory depth.

Or alternatively, I can still put site.go into site/ and rename to cmd.go and export Cmd. So imports to the root cmd will be site.Cmd

Actually, cobra already has a OnInitialize function to load in config file function. This effectively makes the conf package redundant.

Should be added to the root node based.

Actual implementation is still to keep the conf sub command because it's useful to have around as a way to output the conf as a command

Current command tree:
weather conf init
weather conf data
weather site list
weather site set
weather site forecast


Disallow identically named type parameters

The Roy code
data Maybe a a = Nothing | Just a

generates (0.1.3) the JS
var Nothing = function(){};
var Just = function(a){this._0 = a};

where it should generate a compile error, like GHC: "Repeated type variable "a" on left hand side"

30db61531ece2c40e87f3a4e29a1276af85d9c04


chore: add support for new friends APIs

Related PR
https://github.com/RetroAchievements/RAWeb/pull/2887
Waiting to main PR to be merged/release before removing the draft state

Thank you!


control the global_connections section in common_pdn.tcl with a flag

This section causes trouble for OpenSTA because it's unable to deal with the power connections when they are too many for some reason. This needs to be opened as an issue on the OpenROAD side. However, let's apply this quick workaround for now since this section isn't really needed for most of the designs.

Pulled and merged.


Avoid usage of JsonConvert in test host process

Putting the following code in a test case, or executing something like this some where in your application wil cause tests to run indefinitely. My guess it is messes up the communication with VSTest, because JsonConvert will fall back to the settings returned by JsonConvert.DefaultSettings.
JsonConvert.DefaultSettings = () => new JsonSerializerSettings
{
    ContractResolver = new DefaultContractResolver
    {
        NamingStrategy = new SnakeCaseNamingStrategy()
    }
}

I've found that JsonConvert is being called here. But replacing it with this.Serialize() doesn't solve the issue so I think it must be used somewhere in TranslationLayer package which isn't open-source(?).

@ObeA can you please provide us with a basic sample repro? Create a github repo with a bare minimum project where this repros and we'll take it from there.

@ShreyasRmsft you can reproduce it by running the test case in https://github.com/ObeA/vstest-issue-1757.

@ObeA thanks, we'll get back to you on this.

Great! Sounds excellent. Can you give any indication of when this should be fixed?

@ShreyasRmsft any updates?

this issue in result crashes both Resharper and Rider
https://youtrack.jetbrains.com/issue/RSRP-471623

Fixed.


[SPARK-29331][SQL] create DS v2 Write at physical plan

What changes were proposed in this pull request?

create DS v2 write at physical plan instead of logical plan, for streaming write.
Why are the changes needed?

We may need some physical information when creating DS v2 write, e.g. https://github.com/apache/spark/pull/25990 . This also matches batch write.
Does this PR introduce any user-facing change?

no
How was this patch tested?

existing tests

cc @brkyvz @jose-torres @edrevo

Test build #111692 has started for PR 26001 at commit e112af9.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/16685/
Test PASSed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/111692/
Test FAILed.

Test build #111708 has started for PR 26001 at commit 79f94f5.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder-K8s/16701/
Test PASSed.

Test build #111708 has finished for PR 26001 at commit 79f94f5.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/111708/
Test PASSed.

also cc @rdblue

Anything I can do to help push this PR forward? I'd love to get this in so I can finish the PR to add the number of partitions to DSv2

all the checks have passed in this PR. could it be merged?


[language text] Debug PII entity recognition task

Packages impacted by this PR
Issues associated with this PR
Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.

The issue has been resolved in another PR


Recurrent event by months or years

I would like to have recurrent events not only by week, but by month and years as well

Also looking for this functionality, yearly in particular

Yeah, came here looking for this too.
Might even get into the code myself and do a pull request, if I find the time...

+1 for recurring yearly

Any news on this?


[Tree view] Refine and update the design specs for this new Carbon for ibm.com component (part 1)

Part 1: adopter interviews to figure out a list of specific requirements
Task
This is a new component for us. Bulk of the design work should be done and specs exist. It needs a little bit of review / evaluation with adopters (IBM Docs, SDMA) to make sure the design is complete and will serve their needs. Then functional spec, and development, website and QA.
The website ticket we may work with Carbon core team. Here are the existing documentations:
Draft PR:
https://carbon-website-git-fork-designertyler-treeview03092020-c-54d75e.vercel.app/components/tree-view/usage
Notion (latest from Lauren):
https://carbondesignsystem.notion.site/Usage-941b49cbba5c4f0abc7b072294f61bbf
Enhancements needed on

Text label wrap to multiple lines
Micro animation
Number of tiers of indent

Regarding accessibility
Regarding keyboard accessibility: https://w3c.github.io/aria-practices/#TreeView
from Michael Gower (IBM)

Trees are also very keyboard friendly :)
There are no tabs in a tree view. It's one tab stop
all arrow interaction

Acceptance criteria

[ ] Updated designs are reviewed with adopters and DDS designers
[ ] Updated Design specs are posted in Carbon for ibm.com environment

There will not be enough time to do the design work included in this issue.  We will proceed to the build the component and address the design iteratively in the future.  Closing for historical reference, if needed.


Icon: support icons that are available in Fomantic UI

Feature Request
Update FontAwesome Icons so that the latest icons are supported

This cannot be done only on our side as we don't handle CSS in this repo. If you need the latest version of FontAwesome I suggest to use Fomantic UI as they include FA 5.13.0.
With icons that are not present in Icon.propTypes you may get a warning, to solve it you can use <Icon className="ICON_NAME" /> instead.
I am tagging this issue as a compat with Fomantic UI. However, not sure about the implementation yet.

Partially it could be solved by changing SemanticICONS type to an interface. We could use Declaration Merging to add new icons (at least for TS)... Speaking of CSS, I'm using fomantic's CSS with https://github.com/Semantic-Org/Semantic-UI-React with no single issue.

Thanks for getting back to me on this issue. I would love to be able to use Formantic UI, but as my project uses React, I have to stay away from jQuery. I have implemented the Formantic UI styles successfully, but unfortunately it doesn't help with the use of the new Icons directly. We are not using TS, but I will see if I can do something along the lines of what @kusmierz suggested.

I have implemented the Formantic UI styles successfully, but unfortunately it doesn't help with the use of the new Icons directly.

But a workaround with className works, correct?

Adding a className works indeed. 👍
Maybe you can just update the list of Icons once in a while ? It seems it was generated.
https://github.com/Semantic-Org/Semantic-UI-React/blob/40903c29a0592a6cb7060e68a107eeb1446ae84b/src/lib/SUI.js#L61-L62

Maybe you can just update the list of Icons once in a while ?

I think the problem with updating that list is not all recommended ways of consuming CSS with SUIR have the most up to date FontAwesome icons. Some of them still only support the icon list that is currently defined for the name prop. If we updated that list for the most recent available fonts, we are going to give some users a false impression that those icons are available from all recommended style solutions.
If someone is savvy enough to be consuming CSS in a more advanced way than just using the baseline SUI CSS files without changes, it is probably still best to use the className workaround to avoid the prop-type errors.
@layershifter if we are still relying on SUI as our source of truth... I think we close this? If I recall, there was also a performance hit from using the name prop in a long list of rendered items due to having to iterate over that list to validate on each item. I do not recall if that edge case was ever solved. Should not be an issue in production.

@layershifter How are the icons array for SUI currently generated? Is there some script? I'd like to make an external package (or can be merged into this repo) that enables new icons.


Storage of additional files alongside lure.sh

Just curious: is this not possible currently? obsidian.desktop creation for example is imho horrendous currently and could just be stored as e.g. obsidian/files/obsidian.desktop alongside obsidian/lure.sh and installed to ${pkgdir} from the directory.
For reference on Void's xbps-src this is possible with the ${FILESDIR} global variable.

Closing in favor of https://github.com/Arsen6331/lure/issues/38.


Feature idea : set(key, value) on Field

A generic option setter
Sometimes, especially with plugins, I need to set some specific key that aren't registered within ACF API. $config is protected and there is no way (or I missed something) to create an arbitrary configuration.
Before doing a PR  I want to discuss the idea :
set() proposition
A set() method could serve as a bridge to add new config keys.
FlexibleContent::make(__('Composants', THEME_TEXTDOMAIN), 'flexibles')
                    ->layouts([
                        $this->block('banner-homepage')
                    ])
                   ->set('btn-icon-only', true)
                   ->set('collapse_all_flexible', true)
                   ->set('hide_collapse', true)

append() proposition
An append() method could be used to add multiple keys
FlexibleContent::make(__('Composants', THEME_TEXTDOMAIN), 'flexibles')
                    ->layouts([
                        $this->block('banner-homepage')
                    ])
                   ->append([
                      'btn-icon-only' => true,
                      'collapse_all_flexible' => true,
                      'hide_collapse' => true
                  ])

We've discussed this internally and decided to not add this feature for now. This can be solved by users of this package by extending the default fields. We'll document custom fields before releasing the next major version. We're very thankful for the pull request and might revisit this in the future if more people request this feature.
Again, thanks for all pull requests you send us Jonathan! Keep up the good work 🙌


HTTP/1.1: not found

I grabbed the reop and used the docker-compose process. It pulled the info down and started but all I get is the above notice when I try to go to the page. Unfortunately, and docker logs on the container does not report anything back. I am on a Mac with Apple silicon.

I confirmed it working on apple silicon (M2 in my case) just fine. However, I provided the wrong link to localhost in the readme. Fixed that in https://github.com/zeidlos/hamclock-docker/commit/f651d3e7ef142cdc1194b233373eaa8b17fe3347
Sorry for the inconvenience.


feat/show-resource-diff

This PR adds a generic mechanism to reconcile resource properties that can be used in all resource reconcilers. This also provides logging in a consistent way because until now, only Deployment and StatefulSet resources were logging differences when updates are required, which makes it hard to debug problems.
Also upgraded to go 1.20.
Please take a careful look in case I have mistakenly deleted reconciliation of some property.
/kind feature
/priority important-soon
/assign

/approve


Create Azure Marketplace Azure Application entry for tWAS cluster.

Initial creation.
Fill out marketing verbiage
Upload zip.
Test preview.

gh-8-marketplace-offer.docx

Pushed to preview status 2021-04-30 21:17 EDT

Offer is live.


Java 8 Distributable

Please maintain the Java 8 distributable. There are still many organizations that use Java 8 in production.
(see Welcome to (the new home of) UCanAccess)

I have moved to Java 11 as the minimum required Java version to take advantage of new features, optimizations, and security enhancements introduced in Java 11 LTS, which will ultimately contribute to a more robust and maintainable codebase.
Maintaining support for multiple target run-time Java versions in parallel is unfortunately out of scope for me.

[heart]         Manuel Vicente Garcia Rodriguez reacted to your message:

From: Markus Spann @.>
Sent: Thursday, January 25, 2024 11:17:12 AM
To: spannm/ucanaccess @.>
Cc: Subscribed @.***>
Subject: Re: [spannm/ucanaccess] Java 8 Distributable (Issue #3)
PRECAUCIÓN: Este mensaje es de un REMITENTE EXTERNO - sea CUIDADOSO, en particular con los enlaces y archivos adjuntos. / CAUTION: This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.
I have moved to Java 11 as the minimum required Java version to take advantage of new features, optimizations, and security enhancements introduced in Java 11 LTS, which will ultimately contribute to a more robust and maintainable codebase.
Maintaining support for multiple target run-time Java versions in parallel is unfortunately out of scope for me.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/spannm/ucanaccess/issues/3*issuecomment-1909949977__;Iw!!BvtVhh717i4!5NswSqXPiTWCeRwN6FLnu1Q3tKCA5I4YDI0ugKazrvq2jnHyU40Ly_RRVhsQ67COsBXT65xifXSABGS5V6zo_mOKqPZgUg$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AV2QZBSOJIOEZSRDCRMGZJ3YQI5LRAVCNFSM6AAAAABBQPDAZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBZHE2DSOJXG4__;!!BvtVhh717i4!5NswSqXPiTWCeRwN6FLnu1Q3tKCA5I4YDI0ugKazrvq2jnHyU40Ly_RRVhsQ67COsBXT65xifXSABGS5V6zo_mOLFnJeDw$.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

[0]     Manuel Vicente Garcia Rodriguez reacted to your message:

From: Markus Spann @.>
Sent: Thursday, January 25, 2024 11:17:12 AM
To: spannm/ucanaccess @.>
Cc: Subscribed @.***>
Subject: Re: [spannm/ucanaccess] Java 8 Distributable (Issue #3)
PRECAUCIÓN: Este mensaje es de un REMITENTE EXTERNO - sea CUIDADOSO, en particular con los enlaces y archivos adjuntos. / CAUTION: This message is from an EXTERNAL SENDER - be CAUTIOUS, particularly with links and attachments.
I have moved to Java 11 as the minimum required Java version to take advantage of new features, optimizations, and security enhancements introduced in Java 11 LTS, which will ultimately contribute to a more robust and maintainable codebase.
Maintaining support for multiple target run-time Java versions in parallel is unfortunately out of scope for me.
—
Reply to this email directly, view it on GitHubhttps://urldefense.com/v3/__https://github.com/spannm/ucanaccess/issues/3*issuecomment-1909949977__;Iw!!BvtVhh717i4!5NswSqXPiTWCeRwN6FLnu1Q3tKCA5I4YDI0ugKazrvq2jnHyU40Ly_RRVhsQ67COsBXT65xifXSABGS5V6zo_mOKqPZgUg$, or unsubscribehttps://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AV2QZBSOJIOEZSRDCRMGZJ3YQI5LRAVCNFSM6AAAAABBQPDAZ2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMBZHE2DSOJXG4__;!!BvtVhh717i4!5NswSqXPiTWCeRwN6FLnu1Q3tKCA5I4YDI0ugKazrvq2jnHyU40Ly_RRVhsQ67COsBXT65xifXSABGS5V6zo_mOLFnJeDw$.
You are receiving this because you are subscribed to this thread.Message ID: @.***>