check errors disappear at the second try

I encountered the errors below for a few files when specifying the tar file names.
When I retried it, they were checked successfully. What these errors mean? Why they disappear when trying again? Thanks.
INFO: Transferring file from HPSS: zstash/000103.tar
ERROR: Error=Transferring file from HPSS: 000103.tar, Command was `hsi -q "cd /home/t/tang30/E3SMv2/v2.NARRM.piControl; get 000103.tar"`. This command includes `hsi`. Be sure that you have logged into `hsi`.
Traceback (most recent call last):
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.5.1_nompi/bin/zstash", line 10, in <module>
    sys.exit(main())
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.5.1_nompi/lib/python3.8/site-packages/zstash/main.py", line 68, in main
    check()
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.5.1_nompi/lib/python3.8/site-packages/zstash/check.py", line 12, in check
    extract.extract(keep_files=False)
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.5.1_nompi/lib/python3.8/site-packages/zstash/extract.py", line 44, in extract
    failures: List[FilesRow] = extract_database(args, cache, keep_files)
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.5.1_nompi/lib/python3.8/site-packages/zstash/extract.py", line 210, in extract_database
    failures = extractFiles(matches, keep_files, config.keep, cache)
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.5.1_nompi/lib/python3.8/site-packages/zstash/extract.py", line 374, in extractFiles
    hpss_get(hpss, tfname, cache)
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.5.1_nompi/lib/python3.8/site-packages/zstash/hpss.py", line 99, in hpss_get
    hpss_transfer(hpss, file_path, "get", cache, False)
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.5.1_nompi/lib/python3.8/site-packages/zstash/hpss.py", line 76, in hpss_transfer
    run_command(command, error_str)
  File "/global/common/software/e3sm/anaconda_envs/base/envs/e3sm_unified_1.5.1_nompi/lib/python3.8/site-packages/zstash/utils.py", line 55, in run_command
    raise Exception(error_str)
Exception: Error=Transferring file from HPSS: 000103.tar, Command was `hsi -q "cd /home/t/tang30/E3SMv2/v2.NARRM.piControl; get 000103.tar"`. This command includes `hsi`. Be sure that you have logged into `hsi`.

@tangq I'm not sure why they disappeared on a second try. The Exception notes that you might not have been logged into hsi the first time, but that's certainly not the only possible reason that that tar failed to transfer.

I had another check job without specifying the tar file names failed with similar errors. So, the more flexible input file names options you implemented are really helpful when checking the large simulations.
My question is with the successful second check, is it safe to say that these tar files are correctly archived?

So, the more flexible input file names options you implemented are really helpful when checking the large simulations.

Great, glad to hear #170 is working well.

My question is with the successful second check, is it safe to say that these tar files are correctly archived?

If you have a log file from the check, you can run grep -i Exception <log_file> to double check for any errors.

The log file for the second try (only checking the 3 failed files) is at cori:/global/cscratch1/sd/tang30/E3SMv2/v2.NARRM.piControl/check2/out. Nothing returns from grep -i Exception.
The log file for the first try is: /global/cscratch1/sd/tang30/E3SMv2/v2.NARRM.piControl/zstash_check_20211209.log. It is still ongoing and returns the 3 files when grepping exception.
Good to know the "exception" key word - less messages than "error".

Good to know the "exception" key word

Great, I'm planning to include a note about that with #168.

I have also seen errors like this before. If the error is not reproducible, it is very likely that it was caused by some intermittent hsi issue or unavailability.
Also, I have found that hsi errors are more likely when retrieving to CSCRATCH. I now use cfs to run zstash check and it seems more reliable.

I have also run into This command includes hsi. Be sure that you have logged into hsi intermittently. I can connect to hsi. I'm wondering whether anyone has figured out a solution?

I can connect to hsi. I'm wondering whether anyone has figured out a solution?

@wagmanbe #314 -- that error message offers one possible solution (probably the most common), but there may be other things wrong.

Thank you. It's helpful to know that there is not one obvious cause. I'll keep troubleshooting.
And yes, I can log into hsi manually, e.g. > hsi


UI + Settings issues

I was on an old build(1.4.X). In the new 1.5.1 build scrolling is now "sluggish". When click+dragging using code glance, the preview box trails behind the mouse cursor.
Also the "Render Style" setting doesn't seem to save and reverts on apply/ok.

Can you try doing this?

Close Intellij
Go to C:\Users<User>\.IntelliJIdeaXX\config\plugins
delete all the CodeGlance things from here (jars, zips, folders)
reinstall the plugin from the repo


Icon Picker - Inconsistent code <> documentation

https://adobe-consulting-services.github.io/acs-aem-commons/features/ui-widgets/icon-picker/index.html
States:
"In version 2.1.0 the default fa CSS class has been removed. If you have created a custom Font Awesome generic list using 2.0.0, you will need to prefix each value with the fa CSS class."
This commit however:
https://github.com/Adobe-Consulting-Services/acs-aem-commons/commit/432a45aab7f4d03cd9dd6bb447d920edd540b6b5
Puts back the "fa"-class..?

In addition: I've used this component for a custom list/font and now all my values are prefixed with "fa ".

When undoing the changes of the commit mentioned above, both my custom list and the provided Font Awesome list work as expected.

@kuckmc01 or @justinedelson  thoughts on this? Was [1] intentional?
[1] https://github.com/Adobe-Consulting-Services/acs-aem-commons/commit/432a45aab7f4d03cd9dd6bb447d920edd540b6b5#diff-1b1f20933ee382aa8bdb011eb34dfd1aR236

I was under the impression that font awesome required the "fa" prefix. We can remove the automatic prefixing.

PR in https://github.com/Adobe-Consulting-Services/acs-aem-commons/pull/1028

This issue was fixed via #1028


Can't import modules from inside the .ts file

Is there a way to make module resolution work?
I have a file like
import {defineConfig} from "simpcicd"

and it can't retrieve the package from the cache.

Could you link an example repo and the command you're using to setup/run the program?


Ensure the concurrency safety of TestResultsViewContent.reveal

Fix #189755
This PR ensures the concurrency safety of TestResultsViewContent.reveal by sequencializing the calls to contentProvider.update.

Hi. Should this PR also be marked with "August 2023" milestone?

It should! I assumed our PR bot would do this automatically...


Crash when try to open file in C:Desktop

VSCode Version:
OS Version:

Steps to Reproduce:

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

/needsMoreInfo


the thing with the cors issue is getting tough

I have Laravel 5.0.x and I have installed laravel-cors packgage 0.7.x but seems not working for me:
This is how my config/cors.php looks like:
return [
/*
 |--------------------------------------------------------------------------
 | Laravel CORS
 |--------------------------------------------------------------------------
 |

 | allowedOrigins, allowedHeaders and allowedMethods can be set to array('*')
 | to accept any value, the allowed methods however have to be explicitly listed.
 |
 */
'supportsCredentials' => false,
'allowedOrigins' => ['*'],
'allowedHeaders' => ['*'],
'allowedMethods' => ['GET', 'POST', 'PUT',  'DELETE'],
'exposedHeaders' => [],
'maxAge' => 0,
'hosts' => [],
];

And in Http/Kernel.php I have this:
protected $middleware = [
    'Illuminate\Foundation\Http\Middleware\CheckForMaintenanceMode',
    'Illuminate\Cookie\Middleware\EncryptCookies',
    'Illuminate\Cookie\Middleware\AddQueuedCookiesToResponse',
    'Illuminate\Session\Middleware\StartSession',
    'Illuminate\View\Middleware\ShareErrorsFromSession',
    //'App\Http\Middleware\VerifyCsrfToken', TODO:: Enable this for security
    'Barryvdh\Cors\HandleCors',
];

Anyone knows how to fix, I always get cors origin not allowed response even when there is a syntax error on code ?
Have been trying for the whole day was not succesfull...
Any help, tip, would appreciate.

Did you try this from the readme?
https://github.com/barryvdh/laravel-cors#debugging-errors

I did tried every possible technique, and still not working, I have a very simple question, does you package actually works with Laravel 5.0.35, which is my version.
Thanx

If I add that allow origin * on tom of public/index.php I get different error which is almost same as the first one.
this is the error when I add on top of index.php:
XMLHttpRequest cannot load http://localhost:81/venture-backend/public/authenticate. Response to preflight request doesn't pass access control check: The 'Access-Control-Allow-Origin' header contains multiple values '*, http://localhost:9000', but only one is allowed. Origin 'http://localhost:9000' is therefore not allowed access.

@barryvdh when you have some free time to explain more this issue why is not working for me, I would appreciate alot...

+1


python.pkgs.beaker: 1.8.0 -> 1.10.0

Motivation for this change
part of https://discourse.nixos.org/t/nixpkgs-update-r-ryantm-logs
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build pyload python27Packages.beaker python27Packages.pyramid_beaker python36Packages.beaker python36Packages.pyramid_beaker

Failure on x86_64-darwin (full log)
Attempted: python36Packages.beaker, python36Packages.pyramid_beaker
The following builds were skipped because they don't evaluate on x86_64-darwin: pyload, python27Packages.beaker, python27Packages.pyramid_beaker
Partial log (click to expand)
beaker.container: DEBUG: opening dbm file /private/tmp/nix-build-python3.6-Beaker-1.10.0.drv-0/tmpsqgs_itw/db/container_dbm/a/a9/a94a8fe5ccb19ba61c4c0873d391e987982fbbd3.dbm
--------------------- >> end captured logging << ---------------------

----------------------------------------------------------------------
Ran 151 tests in 150.769s

FAILED (errors=1)
builder for '/nix/store/13xw6aks2gfy8gjjjsann7nqsjscgka2-python3.6-Beaker-1.10.0.drv' failed with exit code 1
cannot build derivation '/nix/store/sfca29h2553r5md9i9hjw6fhvxsy0qmq-python3.6-pyramid_beaker-0.8.drv': 1 dependencies couldn't be built
error: build of '/nix/store/13xw6aks2gfy8gjjjsann7nqsjscgka2-python3.6-Beaker-1.10.0.drv', '/nix/store/sfca29h2553r5md9i9hjw6fhvxsy0qmq-python3.6-pyramid_beaker-0.8.drv' failed

Success on aarch64-linux (full log)
Attempted: python27Packages.beaker, python27Packages.pyramid_beaker, python36Packages.beaker, python36Packages.pyramid_beaker
The following builds were skipped because they don't evaluate on aarch64-linux: pyload
Partial log (click to expand)
collected 36 items / 1 deselected

pyramid_beaker/tests.py ...................................              [100%]

=================== 35 passed, 1 deselected in 0.78 seconds ====================
pytestcachePhase
/nix/store/qqw1hpq0s1j8r0lfww862vrwga0472pd-python2.7-Beaker-1.10.0
/nix/store/82wj6qiddvvn07phbcnkfwsiyhrj5c6k-python2.7-pyramid_beaker-0.8
/nix/store/53866vxp0y818ays01dak64gyv0lcwjw-python3.6-Beaker-1.10.0
/nix/store/fmfbim5kjs8sak0lkyr74kgn4zl57m23-python3.6-pyramid_beaker-0.8

Success on x86_64-linux (full log)
Attempted: python27Packages.beaker, python27Packages.pyramid_beaker, python36Packages.beaker, python36Packages.pyramid_beaker
The following builds were skipped because they don't evaluate on x86_64-linux: pyload
Partial log (click to expand)
collected 36 items / 1 deselected

pyramid_beaker/tests.py ...................................              [100%]

=================== 35 passed, 1 deselected in 0.36 seconds ====================
pytestcachePhase
/nix/store/mcv9v8hy1lnapcfx427ig92303qdrbk8-python2.7-Beaker-1.10.0
/nix/store/900ci9vq63j9kcq2870dhs9ssavhf4ai-python2.7-pyramid_beaker-0.8
/nix/store/krpkn3v1rqmygzvnpf1rifkld32g9vqj-python3.6-Beaker-1.10.0
/nix/store/lz5fibrmrz3yn2yr17a181hhrpsj0830-python3.6-pyramid_beaker-0.8

@Mic92 Is this blocked by the Darwin failures?

I forgot what the status of this pr was:
@GrahamcOfBorg build pyload python27Packages.beaker python27Packages.pyramid_beaker python36Packages.beaker python36Packages.pyramid_beaker

Alternative is to ignore tests.test_cache.test_upgrade for macOS since also upstream does not seems to be keen in fixing it. dbm support seems to be only a small part of the library after all.

Alternative is to ignore tests.test_cache.test_upgrade for macOS since also upstream does not seems to be keen in fixing it. dbm support seems to be only a small part of the library after all.


Hangs when logging in using Google Chrome

Fedora Linux 41
Google Chrome 130.0.6723.116
watcharr 1.44.2 on Docker 27.3.1

So far I have never had any problems with this browser. But today I tried to enter watcharr using this browser and it hangs when entering showing the error: Failed to filter/sort list!

After some time, Google Chrome displays an error informing that the page is not responding. It works fine in Firefox.

The problem was an extension: PhotoShow.


Doc changes for MQTT Topics

Change topics for MQTT in docs, moving away from using /topic to show subtopics
change topics like ./addTOPIC to ./add/TOPIC to allow implementation of ./modify/TOPIC etc.

Let's also take a look athe following project for documenting and maybe even boilerplate code:
https://github.com/asyncapi/generator

https://github.com/asyncapi/go-template

Maybe use other specifications: https://sparkplug.eclipse.org/about/faq/

https://forums.opto22.com/t/sending-mqtt-sparkplug-b-control-messages-from-node-red/3478

Basically what the new datamodel does


Unable to start IPython console

Context
I am working on a OSX 10.10.5 and I have install the required package for python using Homebrew. Spyder has been install from source (version 2.3.7). Spyder works well but I can't run a IPython console. I obtain the following error

Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/spyderlib/plugins/ipythonconsole.py", line 830, in create_new_client
menu_actions=self.menu_actions)
File "/usr/local/lib/python2.7/site-packages/spyderlib/widgets/ipython.py", line 407, in init
local_kernel=False)
File "/usr/local/lib/python2.7/site-packages/spyderlib/widgets/ipython.py", line 175, in init
super(IPythonShellWidget, self).init(*args, **kw)
File "/usr/local/lib/python2.7/site-packages/qtconsole/rich_jupyter_widget.py", line 49, in init
super(RichJupyterWidget, self).init(*args, **kw)
File "/usr/local/lib/python2.7/site-packages/qtconsole/jupyter_widget.py", line 112, in init
super(JupyterWidget, self).init(*args, **kw)
File "/usr/local/lib/python2.7/site-packages/qtconsole/frontend_widget.py", line 153, in init
super(FrontendWidget, self).init(*args, **kw)
File "/usr/local/lib/python2.7/site-packages/qtconsole/history_console_widget.py", line 28, in init
super(HistoryConsoleWidget, self).init(*args, **kw)
File "/usr/local/lib/python2.7/site-packages/qtconsole/console_widget.py", line 211, in init
LoggingConfigurable.init(self, **kw)
File "/usr/local/lib/python2.7/site-packages/traitlets/config/configurable.py", line 85, in init
self.config = config
File "/usr/local/lib/python2.7/site-packages/traitlets/traitlets.py", line 450, in set
new_value = self._validate(obj, value)
File "/usr/local/lib/python2.7/site-packages/traitlets/traitlets.py", line 471, in _validate
value = self.validate(obj, value)
File "/usr/local/lib/python2.7/site-packages/traitlets/traitlets.py", line 1045, in validate
self.error(obj, value)
File "/usr/local/lib/python2.7/site-packages/traitlets/traitlets.py", line 899, in error
raise TraitError(e)
traitlets.traitlets.TraitError: The 'config' trait of an IPythonShellWidget instance must be a Config, but a value of class 'IPython.config.loader.Config' (i.e. {'IPythonWidget': {'gui_completion': 'droplist', 'enable_calltips': True, 'kind': 'rich', 'paging': 'none', 'buffer_size': 500}}) was specified.
Traceback (most recent call last):
File "/usr/local/lib/python2.7/site-packages/spyderlib/plugins/ipythonconsole.py", line 830, in create_new_client
menu_actions=self.menu_actions)
File "/usr/local/lib/python2.7/site-packages/spyderlib/widgets/ipython.py", line 407, in init
local_kernel=False)
File "/usr/local/lib/python2.7/site-packages/spyderlib/widgets/ipython.py", line 175, in init
super(IPythonShellWidget, self).init(*args, **kw)
File "/usr/local/lib/python2.7/site-packages/qtconsole/rich_jupyter_widget.py", line 49, in init
super(RichJupyterWidget, self).init(*args, **kw)
File "/usr/local/lib/python2.7/site-packages/qtconsole/jupyter_widget.py", line 112, in init
super(JupyterWidget, self).init(*args, **kw)
File "/usr/local/lib/python2.7/site-packages/qtconsole/frontend_widget.py", line 153, in init
super(FrontendWidget, self).init(*args, **kw)
File "/usr/local/lib/python2.7/site-packages/qtconsole/history_console_widget.py", line 28, in init
super(HistoryConsoleWidget, self).init(*args, **kw)
File "/usr/local/lib/python2.7/site-packages/qtconsole/console_widget.py", line 211, in init
LoggingConfigurable.init(self, **kw)
File "/usr/local/lib/python2.7/site-packages/traitlets/config/configurable.py", line 85, in init
self.config = config
File "/usr/local/lib/python2.7/site-packages/traitlets/traitlets.py", line 450, in set
new_value = self._validate(obj, value)
File "/usr/local/lib/python2.7/site-packages/traitlets/traitlets.py", line 471, in _validate
value = self.validate(obj, value)
File "/usr/local/lib/python2.7/site-packages/traitlets/traitlets.py", line 1045, in validate
self.error(obj, value)
File "/usr/local/lib/python2.7/site-packages/traitlets/traitlets.py", line 899, in error
raise TraitError(e)
traitlets.traitlets.TraitError: The 'config' trait of an IPythonShellWidget instance must be a Config, but a value of class 'IPython.config.loader.Config' (i.e. {'IPythonWidget': {'gui_completion': 'droplist', 'enable_calltips': True, 'kind': 'rich', 'paging': 'none', 'buffer_size': 500}}) was specified.

I have installed IPython 3.0.0.

You to need to do
pip install -U ipython

to fix this problem.
If that doesn't work, then please also run
pip install -U qtconsole

I have ran the first command and now I have the following message and I can't use Spyder anymore.

What happens if you run the second?

exactly the same thing...

The command  pip install -U ipython installs ipython-4.0.0. Is this version compatible with spyder?

Any solution of my issue?

Just install ipython 4.0.0, that should fix your issue, along with installing spyder 2.3.7 and qtconsole 4.1.0.

I have ran pip install --upgrade ipython qtconsole and now I have the following error:

I'll test this configuration on my Mac machine and come back to you with
my findings :-)
El 19/10/15 a las 09:07, l2 escribió:

I have ran |pip install --upgrade ipython qtconsole| and now I have
the following error:
capture d ecran 2015-10-19 a 16 05 58
https://cloud.githubusercontent.com/assets/147177/10579976/7b083726-767b-11e5-9cc5-051cae2dcd35.png
—
Reply to this email directly or view it on GitHub
https://github.com/spyder-ide/spyder/issues/2755#issuecomment-149223320.

It's very weird. I have tried two things:

obtaining  the source of spyder 2.3.7, execute python bootstrap.py. I obtain the following error message :

obtaining the DMG spyder 2.3.7, install it and run, I obtain the following error message:

Optional dependencies says:
IPython >=1.0      :  4.0.0 (OK)
jedi >=0.8.1;<0.9.0:  None (NOK)
matplotlib >=1.0   :  1.4.3 (OK)
pandas >=0.13.1    :  0.16.2 (OK)
pep8 >=0.6         :  1.6.2 (OK)
psutil >=0.3       :  3.2.2 (OK)
pyflakes >=0.5.0   :  1.0.0 (OK)
pygments >=1.6     :  2.0.2 (OK)
pylint >=0.25      :  1.4.4 (OK)
qtconsole >=4.0    :  4.0.1 (OK)
rope >=0.9.2       :  0.10.2 (OK)
sphinx >=0.6.6     :  1.3.1 (OK)
sympy >=0.7.3      :  <IP_ADDRESS> (OK)
zmq >=2.1.11       :  14.7.0 (OK)

up!


Cohesity: update info and version related to last commits

Hi @Bastian-Kuhn, in my last commits for Cohesity plugin I did not update the info file and the version. Here it is.
BR
Nicolas


Is parcelify being superceded by cartero?

Apologies if I'm missing something obvious about the differences between the two, but it seems like you're focusing more on cartero at this point. Is that correct? Is there something specific that parcelify offers that cartero does not?

Ah -- my apologies, cartero uses parcelify for CSS bundling. Right? Ok nevermind :wink:


basemaps: add tilejson tab

don't be scared by the num of changes, they are minimum after https://github.com/CartoDB/cartodb/pull/9740 is merged

we'd need the thumbnail template for tilejson, too

there's still some issue regarding the position of the errors, I suppose it's related to https://github.com/CartoDB/cartodb/pull/9740#issuecomment-248246291 /cc @piensaenpixel

CR @xavijam

BOOM /cc @xavijam

Resolve your conflicts and ready to man! :)

took the tilejson-layer-model out and added the tests, thanks again @xavijam for the help!

:rocket:


add options to proposal view page instead of large buttons we have now

fixed https://github.com/nance-eth/nance-interface/commit/0efaec6cea89579345dee0552e1ded57e5ae98a5


kvirc: use qt5.mkDerivation

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Notify maintainers
cc @

@grahamcofborg eval

@GrahamcOfBorg build kvirc

[detached HEAD f6492409408] kvirc: use qt5.mkDerivation
Author: Сухарик<EMAIL_ADDRESS>Date: Sun Sep 22 22:24:03 2019 +0300
1 file changed, 3 insertions(+), 3 deletions(-)


Need to access a GUI console through Azure Portal

There are various reasons why RDPing through port 3389 is not acceptable. Mainly because of security reasons, but also because of practical reasons. For example it would be extremely useful to be able to see my VM boot, or I would like to access my VM GUI from a corporate environment that does not allow RDP connections over the internet. Can Azure provide such a service?

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

ID: 077ee673-528a-d893-5832-7656b91dbec8
Version Independent ID: 2180e845-1ead-3b47-03be-c26aee00c6f7
Content: Use Remote Desktop to a Linux VM in Azure
Content Source: articles/virtual-machines/linux/use-remote-desktop.md
Service: virtual-machines-linux
GitHub Login: @cynthn
Microsoft Alias: cynthn

Thanks for the question! We are investigating and will update you shortly.

@eliasbats Accessing a VM Console (GUI) is not possible now.
But we have features for troubleshooting a VM from portal.

Accessing boot diagnostics and screenshot the vm (link)
serial console

If you are looking for RDP only, Please submit a feedback here.
A related requests here.

is there any update?

I will close this out for now. If you need additional help please let me know and we can reopen and continue.

Any update regadering this one? We are losing hours since we can't click on enter during boot...


removed non-determinism from CanonicalSimplify

removed non-determinism from CanonicalSimplify by avoiding pointer comparison and instead compare string representation of terms.
added couple of testcases for CanonicalSimplify

For the other case, let us not rely on string, but use https://github.com/dmlc/tvm/blob/master/src/pass/ir_deep_compare.cc#L424
This is still non deterministic  between runs, but order is consistent for the same expression

IRDeepCompare is a better choice than string comparison. Thanks!

@derisavi-huawei can you update the PR and let us merge it in. For the case of LOG(FATAL), let us change it to LOG(WARNING) for now


Improvements to search

This PR adds two improvements to search in the haskell backend.

We do not display the substitution of anonymous variables in search patterns in search results unless that anonymous variable appears somewhere else inside the substitution. This behavior can be disabled via a flag in order to obtain the original substitution.
We add a new flag to kompile, --superstrict, which modifies the behavior of strict. This flag has two effects:

We remove side conditions from cooling rules
We add a new cell to the configuration, <generatedProgress> which is used to automatically transform the definition so that a cooling rule can never apply immediately following a heating rule. This gives us the full range of nondeterminism associated with strictness, including cases where you partially heat one argument, then cool it, then heat another argument, without introducing cycles into the transition system.

Closing this as part of this PR will not get merged. I will reopen with just the commits that are relevant.


[🐞] Qwik removes elements generated by 3rd party plugin

Which component is affected?
Qwik Runtime
Describe the bug
Qwik removes element which were generated by a 3rd party plugin. The 3rd party plugin is not written in qwik.
Reproduction
https://stackblitz.com/edit/qwik-starter-riimvh?file=src%2Froutes%2Findex.tsx
Steps to reproduce

Let the app initialize, notize the red border (this element is generated by the 3rd party plugin)
Click on the "Hide Content" Button
The red border disappeared because the element was removed

I've build the same example in react: https://stackblitz.com/edit/vitejs-vite-euyxdy?file=src%2FApp.tsx which doesn't have the same problem. Svelte, Vue, Angular and Solid also dont have the same problem.
System Info
Shouldn't matter

Additional Information
No response

You shouldn't touch the div you're running the plugin on. Just run it in the visible task and if you want to show/hide, do it with a slot in a parent component.
You also shouldn't track the ref

@wmertens I'm not touching the element I'm running the element on. I'm touching one of its children.
Please re-consider this circumstance

Ok, but Qwik has to have full control over the entire DOM of the container (leaves excepted). So if you want to change a child, you need to either:

make it a portal using a hack in v1 (see qwik-ui popover to see how)
wait for portals in v2 (API still TBD)
use a different container and communicate using custom events and globals

What is your specific usecase? Did you consider porting the third party library?

Ok, but Qwik has to have full control over the entire DOM of the container (leaves excepted).

I guess I'm just confused about the fact that an non-related element is removed from the DOM even though the element has nothing to do with the element which was removed, besides the parent. And since other frameworks handle cases like this just fine, I would assume this is an wrong assumption qwik makes about its DOM updates.

What is your specific usecase?

I'm trying to make a qwik wrapper for my vanilla js library. The library generates its own elements. Essentially the DOM before an initialization looks like this:
<target> {/** created by qwik */}
  <viewport> {/** created by qwik */}
    <Slot />
  </viewport>
<target>

After initialization:
<target> {/** created by qwik */}
  <foreign /> {/** created outside qwik */}
  <viewport> {/** created by qwik */}
    <Slot />
  </viewport>
  <foreign /> {/** created outside qwik */}
  <foreign /> {/** created outside qwik */}
<target>

Now I would expect qwik to just ignore all foreign elements, because the template doesn't allow any modifications in those places anyway. But qwik makes unexpected modifications to the foreign elements when I, for example, change the style attribute of the target element.

Did you consider porting the third party library?

Well, this is supposed to be the port. Re-writing the whole library in qwik is out of the question since the maintenance would become too much of an hassle.

@wmertens I'm really sorry when I'm annoying with this issue but I'm convinced this is one area qwik should improve in.
I've debugged the whole thing and the following things are my findings:

This problem happens because of how the the old and new v-dom state is determined
In the very first update cycle of the component on the client (the cycle where I'm toggeling a property) the old v-dom result returns a empty children array. This is technically not correct since I have children (in the real dom and v-dom).
Because of this the children diffing kicks in and does its thing. In this process the foreign and qwik generated dom elements are all mixed up.
In all subsequent updates the old v-dom result is correct because it probably uses some kind of cache of the previous update cycle.

To me this looks like the very first state change "hydrates" the component and potentially completely re-renders it. All subsequent state changes are fine-grained updates (at least updates to children).
So my workaround would be to trigger a "dummy" re-render of the component as soon as it is mounted in the DOM and in the following render cycle initializing my plugin.
My question is now: Do you think this can be improved? I would gladly contribute to qwik and solve this issue. This could not only improve on my issue but also bring potential performance improvements.

Right, so that technique is exactly what we do in qwik-ui for popovers.
However, V2 will be more robust to DOM changes, so one option would be to just wait and see :)
We're also planning to have a react-like portal API, maybe.

@wmertens alright, thank you! :)


Installation CHR247 on Ubuntu Linux 18.04 LTS

@IMS94 ,
i installed chr247 on both a windows Machine and a Linux Ubuntu 18.04 Lts server.
i noticed that the steps provided  here
https://github.com/IMS94/chr247.com/blob/master/readme.md
are for a windows OS.
I would like to share the steps for installation on Ubuntu 18.04, if you would like

i can do a PR to that effect

@francisguchie The current installation steps are for an ubuntu based system. Is there anything missing? #18 PR seems to add steps for windows. Couldn't review and merge that yet.

@francisguchie Docker installer is now available.

@pasan93  this is great news i am going to test it one of these days


Web platform.

I want to use pusher in Web.
Will you update it for support WEB platform?

For now we don't have plans to support web, but PR's are welcome.


test: kitchen: use DD_REPO_URL instead of REPO_URL

What does this PR do?
Use DD_REPO_URL instead of DD_URL

Motivation
The later is deprecated and issues a warning during install

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

You might change your title: DD_REPO_URL instead of REPO_URL DD_URL exists but it's something different

Oh my thanks for noticing :sweat_smile: Updated the commit and the PR title


Including images in styles.css

Problem Description
I am trying to include images in my style.css located in custom module folder. When module is loaded on frontend (without divi builder, It is looking for the image in static/media directory. Am I doing anything wrong here?
Steps To Reproduce
In Style.css:

In browser:

Screenshot and/or gif

Did you ever find a solution? Having the same problem unfortunately...

Ah found it, it is a matter of using the full path of /wp-content/plugins/...


Remove coverage tracking for the time being

Thanks so much for the contribution!
To make reviewing this PR a bit easier, please fill out answers to the following questions.
What was the end-user problem that led to this PR?
The problem was that current coverage numbers are incorrect since our specs rely on checking the results of bundler subprocesses and coverage is not tracked there. We don't know the actual numbers but coverage should be much higher than the 73% codeclimate reports today.
I tried to get this fixed in #6980, but couldn't get it working.
What is your fix for the problem, implemented in this PR?
My fix is to remove coverage tracking for now. This should make merging CIs with rubygems easier, and removes the misleading coverage numbers.
Coverage has helped in the past when the test suite was "unitary test based" as explained by @indirect in #6980, but now it's not useful. Let's revisit it in the future.

@bundlerbot r+
On Apr 24, 2019, 6:32 AM -0700, David Rodríguez<EMAIL_ADDRESS>wrote:

Thanks so much for the contribution!
To make reviewing this PR a bit easier, please fill out answers to the following questions.
What was the end-user problem that led to this PR?
The problem was that current coverage numbers are incorrect since our specs rely on checking the results of bundler subprocesses and coverage is not tracked there. We don't know the actual numbers but coverage should be much higher than the 73% codeclimate reports today.
I tried to get this fixed in #6980, but couldn't get it working.
What is your fix for the problem, implemented in this PR?
My fix is to remove coverage tracking for now. This should make merging CIs with rubygems easier, and removes the misleading coverage numbers.
Coverage has helped in the past when the test suite was "unitary test based" as explained by @indirect in #6980, but now it's not useful. Let's revisit it in the future.
You can view, comment on, or merge this pull request online at:
https://github.com/bundler/bundler/pull/7141
Commit Summary
• Remove coverage tracking for the time being
File Changes
• M README.md (1)
• M Rakefile (4)
• M doc/contributing/HOW_YOU_CAN_HELP.md (2)
• M spec/spec_helper.rb (2)
• D spec/support/code_climate.rb (26)
Patch Links:
• https://github.com/bundler/bundler/pull/7141.patch
• https://github.com/bundler/bundler/pull/7141.diff
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Switch to latest images for build agents

Switching QDK pipeline to use latest images for build agents. There are corresponding PRs in other repos as well.

Do you know why the build takes so long to finish this time? It looks like it's on its third attempt, which is not something I've seen happen previously - I used to have to kick it again. And the last attempt spun off three separate versions of Windows build - is it because it was Windows build that failed on previous attempts?

It seems to be re-starting failed builds and also starting a new one, then canceling all but the new build. Mac also failed the first time, and it has a "canceled" build showing as well. I'm looking into why it's failing, it succeeded when I was testing.

Looks like the failure was not caused by the attempt to double-install IQ#: that warning went away but the failure persists. The error looks to be
At D:\a\1\s\scripts\validate-notebooks.ps1:57 char:9
+         jupyter nbconvert $CheckNotebook --execute  --ExecutePreproce ...
+         ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: ([NbConvertApp] ...k.ipynb to html:String) [], RemoteException
    + FullyQualifiedErrorId : NativeCommandError

Thanks, yeah I've been looking into it. Since the test fails when a notebook would be executed with the IQ# kernel and the IQ# installation is still throwing an error that wasn't there previously, it seems that the actual problem might be with the installation. I'm still looking for a fix.

There shouldn't be any behavioral changes. I got rid of the $errors variable, but it wasn't being used for anything (removed it because it was somehow interfering with output being printed if it had been redirected from stderr to stdout). Setting $ErrorActionPreference = 'Continue' in parts of the script means that the script won't throw on non-terminating errors there, but since we're checking the return code that shouldn't change whether the script fails or succeeds. Generally, the changes force Powershell to print messages sent to stderr (which is the current behavior on master) rather than throwing on them.

Thank you for clarification!


[Theme-name] text (image error on full screen)

Specifics (please complete the following information):

OS: windows 11
Spotify for Windows (64 bit)
<IP_ADDRESS>8.g79f41970
Spicetify v2.20.3

i use 1920x1080 screen


built wheel is not complete

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Windows Server 2019
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: NA
TensorFlow installed from (source or binary): Source
TensorFlow version: 2.3.1
Python version: <IP_ADDRESS>
Installed using virtualenv? pip? conda?: NA
Bazel version (if compiling from source): 3.1.0
GCC/Compiler version (if compiling from source):
CUDA/cuDNN version: 10.1
GPU model and memory: Gforce MX940

Describe the problem
I Build Tensorflow 2.3.1 from source, because my graphic card (Compute Capabiliy 5) is not anymore supported by the binary releases. The Build process as such works ok, but when building the wheel and I install it to another system I miss some components.
e.g all the models under keras.applications are just not part of the wheel.
Provide the exact sequence of commands / steps that you executed before running into the problem
Basically I follow the instructions from here:
https://www.tensorflow.org/install/source_windows
bazel build --config=opt --config=cuda //tensorflow/tools/pip_package:build_pip_package --define=no_tensorflow_py_deps=true
bazel-bin\tensorflow\tools\pip_package\build_pip_package ..\tensorflow_pkg
The wheel is created and it is functional ... just parts of the python sources is missing
Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.
Please let me know which logs you need, and I will provide.

Are you missing some APIs or just some source files that exist in the repo don't get exposed in the wheel?

Are you missing some APIs or just some source files that exist in the repo don't get exposed in the wheel?

As indicated above I think the API is complete but I am missing python sources e.g. whatever is under:
https://github.com/tensorflow/tensorflow/tree/r2.3/tensorflow/python/keras/applications

I don't think they are included in the pip package, by design.

@mihaimaruseac
The  wheel distributed through pypi has these files ...

That's the macos wheel, the bug is about a windows wheel.
Windows wheels are smaller because of maximum size limits under windows (we cannot create a zip file larger than 2GB at one point during the build).

@mihaimaruseac

That's the macos wheel, the bug is about a windows wheel.

True, Sorry for the confusion. However also the windows wheels have the files (see updated screenshot above)

What commit are you building from?

Tag 2.3.1-- Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 10.12.20, 18:09 schrieb Mihai Maruseac<EMAIL_ADDRESS>What commit are you building from?
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

This is weird. We are using the exact same command.
Can you change
bazel-bin\tensorflow\tools\pip_package\build_pip_package ..\tensorflow_pkg

to have a path argument that does not share prefix with the path to the TF sources?
Alternatively, can you also try on the 2.4 branch?

actually I now had a closer look into the created wheel ... and the files are actually there ...
trying to figure out why they haven't been installed in the first place ... could'nt reproduce ...
I have to appologize for creating the noise here ... not sure what happended


I'm having some problems through installation and can't seem to get through them

Hello Flutter Devs!
So I'm having some problems on my M1 Pro mac here.

When I try to install flutter to my path permanently it works all fine but after terminal restart it still says flutter command not found
When using flutter doctor and trying to use these commands (path/to/sdkmanager --install "cmdline-tools;latest", flutter doctor --android-licenses) it just says "zsh: permission denied: /Users/jaxonhensch/android" where i installed it even in the /Users/[my user]/Library/Android and everywhere I go I can't find my problem.

Can you guys possibly help?

Hi @Jaxon10117,

When I try to install flutter to my path permanently it works all fine but after terminal restart it still says flutter command not found

It seems like you did not add the flutter/bin path to your shell file (.zshrc), Please see https://docs.flutter.dev/get-started/install/macos#update-your-path

When using flutter doctor and trying to use these commands (path/to/sdkmanager --install "cmdline-tools;latest", flutter doctor --android-licenses) it just says "zsh: permission denied: /Users/jaxonhensch/android" where i installed it even in the /Users/[my user]/Library/Android and everywhere I go I can't find my problem.

The easiest way to install command-line tools is through Android studio Please see this https://stackoverflow.com/a/68492909/8253662
If you need further help I would encourage you to please look for solution on StackOverflow.
Closing as this is neither an issue nor a feature request with flutter.


This broke an app in g3, reverting while we investigate

Looks like this was rolled back internally. Merging it in to keep things in sync.


Strip html comments from markdown

Closes https://github.com/NuGet/NuGetGallery/issues/8627

@lyndaidaii I've pushed this as pr-8667 on origin to trigger CI. You may wish to look these changes over and test them before approving/merging.

LGTM, :shipit:

I tested locally it was working perfectly. Thanks for your contribution. @CyberAndrii
@drewgillies, feel free to merge it.


Update Slack URL to be more user friendly.

Signed-off-by: Mike Ng<EMAIL_ADDRESS>

Josh showed me a better Slack URL so I am updating our Slack references to it.
/assign @qiujian16

/approve
/lgtm


[WIP] Linux Support

Goals of this Linux support feature:

[x] Install docker
[x] Install docker-compose
[x] Make the dnsdock container starting each time docker is starting
[x] Configure system to use dnsdock to resolve DNS queries for *.docker

On a fresh Debian-based OS (tested on Ubuntu and Debian on DigitalOcean), the following will work to set it up:
apt-get update && apt-get -y install sudo curl git php5-cli libssh2-php
git clone https://github.com/tasuk/dock-cli.git && cd dock-cli && git checkout linux-support
curl -sS https://getcomposer.org/installer | php && php composer.phar install
bin/dock-cli docker:install

Test with:
docker ps
curl http://dnsdock.docker/services

At this time, you're still missing:

[ ] Docker-compose
[ ] Dns resolution

I would like to say... awesome ! :tada:

Thank you Vit !


[WIP] Typescript type definitions

I've started working on the typescript type definition. I still need to write the test and, well, try it using the package (I've only tried referencing it directly).
Right now the styled.element functions' return type is a Stateless component, since I wasn't able to include the ReactDom types (they aren't exported :( )
I need to include the definitions for:

[x] native
[x] keyframes
[x] ThemeProvider
[x] css function
[x] injectGlobal

let me know if I missed something :)
Other todos:

[x] add var element (I commented that out while testing)
[x] tests

Related: #89
Happy Halloween! 🎃

Wow that's amazing, thank you so much! Can't wait to land this!

@mxstbr what do you think of adding tslint to lint the "tests"?

Sounds good to me!

@patrick91 Perhaps you want to consider making the typings non-ambient (ie. not hard coding the module name with declare module "styled-components"). From what I gather using ambient declarations is not recommended, at least not in TS >2.0. For reference see the template Microsoft proposes.

@jonaskello will have a look at it this weekend! danke!

@patrick91 Nice! I'm also interested in getting typings so let me know if I can help.

@jonaskello thanks! a review would be really appreciated, it is my first type definition with typescript so it might not be the best one :)

Fantastic work!
I have one question though,
can and how will this handle this example?:
(in my component classs)
---
const Button = styled.button`
    background-color:  ${(props: any)  => props.negative ? props.theme.negative : props.theme.action}
`;
---
(in render function of component class)
---
<Button negative>Cancel</Button>
---

TypeScript wont allow you to set the "negative" prop since it isnt defined in "React.HTMLFactory<HTMLButtonElement>"
Do you have any idea on how to solve this?

@mxstbr I had to move the native.js to native/index.js to have typings for the native library as well. Not sure if it is the best way to achieve this, but since we can't add multiple typings to the package.json I don't see any other alternative :)

@mxstbr I had to move the native.js to native/index.js to have typings for the native library as well. Not sure if it is the best way to achieve this, but since we can't add multiple typings to the package.json I don't see any other alternative :)

That doesn't work. We need the native.js to be in the root of the file so people can do import styled from 'styled-components/native', the /native here refers to the native.js.

Uhm, that should work anyway. It is not written in the spec but looks like all the module loaders allow load the index.js file when requiring/importing a folder.

@mxstbr I just tried and it works actually:

@AntonAderum sorry! I missed your comment :(
I would do a custom component for that, like I've done in the tests: https://github.com/patrick91/styled-components/blob/d7d8e31af8ee1e6324385ff89ad2ca4505115718/typings/styled-components-test.tsx#L55
Does that help?

Ah sorry, you're right of course! Is this ready to be reviewed? Then I'll post on Twitter asking for reviewers!

@mxstbr yes! I just rebased it, a review would definitively be appreciated!

@patrick91 typings/styled-components.d.ts should probably be lib/index.d.ts to align with the directory layouts, as mentioned above. I'm don't think that should be too intrusive, given that the .flow files are in lib as well.

I just thought I'd share how I've been using these typings. (From an older version, not sure if they're compatible now, or if the current types are more streamlined).
First I defined a StyledElement type: type StyledElement<NewProps, HTMLType extends Element> = React.StatelessComponent<React.HTMLAttributes<HTMLType> & NewProps>;
Then I use it like so:
<FancyAnchorElement primary={true} href="http://example.com">Fancy Anchor Elements just want to have fun and have both anchor and fancy props</FancyAnchorElement>

interface FancyAnchorElementProps {
    primary: boolean;
}

const FancyAnchorElement = styled.a`
    color: ${(props: FancyAnchorElementProps) => props.primary ? "steelblue" : "black"};
    text-decoration: none;
` as StyledElement<FancyAnchorElementProps, HTMLAnchorElement>;

This gives me typechecking for both normal anchor props and my new props.

@patrick91 ... This is the first time I've messed with typescript definitions, but here's an idea for something that's really close to working as I think you want:
type GeneralComponent
 = React.ComponentClass
 | React.StatelessComponent
;
type ConstrainedProps<C, P> = C & ({ defaultProps?: P } | { new(props?: P, context?: any): C});
interface StyledInterface {
  <C extends GeneralComponent
, P>(component: ConstrainedProps<C, P>): StyledFunction<C, P>;
}

I created a (non-exported) combination of the ComponentClass and StatelessComponent (so it works with both) and used the fact that StatelessComponents always have a defaultProps and ComponentClasses must have a contructor that takes a props as the first argument. Thus,
interface BtnProps {
  color: string;
}
const HappyButton: React.SFC<BtnProps> = () => (<button>A happy button</button>);
const CustomizableBtn = styled(HappyButton)`color: ${props => props.color}`

CustomizableBtn typechecks and is a React.StatelessComponent<BtnProps>
Similarly,
class MyHappyButton extends React.Component<BtnProps, {}> {
  public render() {
    return <button>my happy button</button>;
  }
}
const CustomizableBtn = styled(MyHappyButton)`background-color: ${props => props.color}`;

Also typechecks, but as a React.ComponentClass<BtnProps> | React.StatelessComponent<BtnProps>.
Unfortunately, I'm in the process of learning styled-components, so I don't want to say that it works exactly as expected since I'm not comfortable enough with styled-components. But these definitions have helped tremendously, so I hope these will be completed soon. Hope this helps!

Changing ConstrainedProps to
type ConstrainedProps<C, P> = C & ({ defaultProps?: P } | { new(props?: P, context?: any): any });

(changed the constructor return to any) makes styled(MyHappyButton)... infer the type to typeof MyHappyButton (the SFC version remains working the same as before) which is closer to what I expected from the defined types, so that might be better.
Sorry for double-posting. 😄 I'm working on something that involves this, so I'm learning/iterating as I go.

How are we looking here? Would love to finally land this!

@mxstbr just found out sometime to work on it! @Zshazz suggestion is working perfectly (I've just pushed the updated code).
@Zshazz thank you very much! Do you have any documentation links for that? :)
I think we can land this, finally! @mxstbr do you want me to make a demo "app" using TS to show how it works with Styled Components?
PS. I haven't updated the yarn lock file yet

I think we can land this, finally! @mxstbr do you want me to make a demo "app" using TS to show how it works with Styled Components?

Yes pleeeaseeee that'd be super awesome!!

@mxstbr Sorry for the long wait! Here's the example repo: https://github.com/patrick91/Styled-Components-Typescript-Example
I've also rebased the commits :)

@Zshazz I was trying styled components on a side project and I found that there is another improvement we could make is to let know typescript that the className is passed from the styled function, eg. if I do this:
import * as React from "react";

import styled from "styled-components";

interface LogoProps {
    className: string,
}

class Logo extends React.Component<LogoProps, {}> {
    render() {
        return

            Hello World

;
    }
}

const LogoStyled = styled(Logo)`
    color: white;
    background: linear-gradient(to left, #0575E6 , #021B79);
`;

export default LogoStyled;

And then I use the LogoStyled, typescript complains that the property className isn't passed:
error TS2324: Property 'className' is missing in type 'IntrinsicAttributes & IntrinsicClassAttributes<Logo> & { children?: ReactNode; } & LogoProps'

any idea on how to do this?

Just added support to the theme prop, as TS was throwing an error when trying to use the theme prop.
I guess I need to add some docs for using Styled Components with TS. Will try to do over the next few days!

I've improved support for stateless components and now it should get the correct props inside the css. I've added some docs as well, just explaining a couple of caveats.
https://github.com/patrick91/styled-components/blob/feature/type-def/docs/typescript-support.md

@mxstbr done :)

Oh and we need to resolve the merge conflicts 🙈

Will do a rebase later on!

@mxstbr should be ok now!

I sent PR to @patrick91 for fixing issue with existing props like event handlers.

@mxstbr hold on! just got a PR on my repo by @minamorl
Will let you know when I merge it :)

@mxstbr we are good to go :)

@mxstbr fantastic! Oh, and I'll have a look at @Igorbek comments tonight or tomorrow :)

Just suggestions:

Adding tsconfig in typings folder is more helpuful when testing it in another editor.  I mean like what definitelytyped did.
Adding testing for SVGComponent.
Personally I think those can be sent as separated PR. Shipping the code first, then accept another PR on typings seems better approach than discussing more about on this.
At least typings by @patrick91 works fine on normal React element.

This is great. Happy to see this ship as a 1.x version if it's ready in time.

Any update @patrick91? Really want to ship this as another 1.x version!

Sorry for the radio silence, I've been busy! I should be able to work on this during the weekend :)

No worries, glad to hear! Can't wait to ship this 😊

@mxstbr found some time today :)
@geelen @Igorbek I should have addressed all your points :)
@minamorl yup, I think we can refactor a bit the tests when this lands and people start using it.

Just a heads up, guys. I'm waiting a review on my PR by @patrick91. If you want to take a look/review/comment before it gets merged there, you're welcome.

@mxstbr @geelen please review. I think it's ready to be merged.

Amazing work everybody!! :tada:
Do we need to publish these under @types too or does it work out of the box?

@mxstbr it works out of the box. @types are used in case an official package doesn't have typings or need to override them.

Yes! @mxstbr thanks for merging and huge thanks to @Igorbek @geelen @minamorl @Zshazz @DanielRosenwasser and everyone who commented and helped with this PR :)

Published as v1.4.0! :tada:
https://twitter.com/mxstbr/status/824182042149654529

@patrick91, thanks for your work!
I have an issue with new typings. It appear that the syntax
const NavItem = styled.span`
    color: ${props => props.isSelected 'red' : 'black' });
`

results in
error TS2339: Property 'isSelected' does not exist on type 'StyledProps<HTMLProps<HTMLSpanElement>>'.
Did I missed something, or it is a valid issue?

@bhovhannes Unfortunately, TypeScript cannot infer what type of props you're adding. You have to explicitly define the type of additional props:
interface NavItemProps { isSelected?: boolean; }
const NavItem = styled.span`
    color: ${(props: NavItemProps) => props.isSelected 'red' : 'black' });
`

@Igorbek, thank you. I'll proceed with the syntax you recommended.
However I wonder if the following syntax can be made possible:
interface NavItemProps { isSelected?: boolean; }
const NavItem = styled<NavItemProps>.span`
    color: ${(props) => props.isSelected 'red' : 'black' });
    font-weight: ${(props) => props.isSelected 'bold' : 'normal' });
`

That way we will avoid writing props: NavItemProps every time.

@bhovhannes unfortunately that's not (yet) possible, see: https://github.com/Microsoft/TypeScript/issues/11947
An alternative could be this:
interface NavItemProps { isSelected?: boolean; }

const NavItem:React.StatelessComponent<NavItemProps> = ({children, ...props}) => {children}

const StyledNavItem = styled(NavItem)`
    color: ${(props) => props.isSelected ? 'red' : 'black' });
    font-weight: ${(props) => props.isSelected ? 'bold' : 'normal' });
`


Cloud Shell's Terraform version is too old for slurm-on-gke

slurm-on-gke instruction recommends using Cloud Shell, which has Terraform v1.5.7, and therefore will cause errors when running terraform commands.
For example,
│ Error: Unsupported Terraform Core version
│
│   on .terraform/modules/cluster-1-nodepool-1/modules/gke-nodepool/versions.tf line 16, in terraform:
│   16:   required_version = ">= 1.7.4"
│
│ Module module.cluster-1-nodepool-1 (from git::https://github.com/terraform-google-modules/cloud-foundation-fabric.git//modules/gke-nodepool?ref=v33.0.0) does not support
│ Terraform version 1.5.7. To proceed, either choose another supported Terraform version or update this version constraint. Version constraints are normally set for good
│ reason, so updating the constraint may lead to other errors or unexpected behavior.

Users can't upgrade Terraform in Cloud Shell. Here's how I resolved it:

Go to the Terraform downloads page: https://www.terraform.io/downloads
Find the latest version for Linux (amd64).
In Cloud Shell, use wget to download the zip file. e.g. wget https://releases.hashicorp.com/terraform/1.10.2/terraform_1.10.2_linux_amd64.zip
Unzip it unzip terraform_1.10.2_linux_amd64.zip
Run terraform using ./terraform instead of terraform (sudo mv terraform /usr/local/bin doesn't work)

in cloudshell terminal  , run below command to upgrade the terraform.
wget -O - https://apt.releases.hashicorp.com/gpg | sudo gpg --dearmor -o /usr/share/keyrings/hashicorp-archive-keyring.gpg
echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/hashicorp-archive-keyring.gpg] https://apt.releases.hashicorp.com $(lsb_release -cs) main" | sudo tee /etc/apt/sources.list.d/hashicorp.list
sudo apt update && sudo apt install terraform


allow all settings to be defined without cli arguments

Is your feature request related to a problem? Please describe.
Some arguments, such as loglevel or cleanup, can only be defined as CLI arguments, which forces the user to use the detox-cli. While the detox cli is very convenient, we are integrating detox into a toolchain that cannot use it, yet still want to modify these parameters.
Describe the solution you'd like
The option to pass all configurations values as optional parameters to functions.
The order of preference would be:

default value
parameter value (overrides default)
cli value (overrides parameter)

Alternative solution
In cases where it's impractical to pass the arguments, an environment variable could be used.

Let's follow this in #1238 as they seem to discuss the same subject.

I noticed #1238 references this issue in the last checkbox, so @noomorph should either remove that reference or this issue should be re-opened. FWIW I think it makes sense to reopen this issue to separate concerns. Commits can be tagged with this issue number rather than the catch-all issue of #1238, but that is just my two cents 😄. Either way, thanks for your quick responses, much appreciated.

Just wanted to note that all command line arguments will fall back to checking for the equivalent camel-cased environment variables. (see detox/src/utils/argparse.js)

With #1729, we added all artifacts collection options to Detox's package.json section.

With #2038, --reuse and --cleanup CLI options can be used via detox.behavior object in package.json.

Currently, I am planning to add support for:
  -H, --headless            [Android Only] Launch emulator in headless mode. Useful
                            when running on CI.                               [boolean]
      --gpu                 [Android Only] Launch emulator with the specific -gpu [gpu
                            mode] parameter.
      --device-launch-args  Custom arguments to pass (through) onto the device
                            (emulator/simulator) binary when launched.
      --force-adb-install   Due to problems with the "adb install" command on Android,
                            Detox resorts to a different scheme for install APK's.
                            Setting true will disable that and force usage of "adb
                            install", instead.               [boolean] [default: false]

Will post soon a link to a WiP PR.

@noomorph can this be closed, then?

@d4vidi, yeah, let's close it.


You should add instruction

What's CSV file ?
Where can I download the CSV file for the quotes ?
How do I link the file to the widget ?
Is there a youtube video explaining how to do it ??
There are a lot of things on the widget that could mean literally anything. Have I spent the last 3 hours trying to figure this out
So on and so forth. The below average joe such as myself would find it difficult to understand how to do things. ( There is a reason why they have instructions. What is commonsense for some people may not be for others)
I learnt what CSV is by trying to figure out how to get the app widget to work (it still hasn't worked because Idk where to get the quotes from)

I've release 4.27.0 - it might take a day or so to appear in Google Play Store / F-Droid.
I published a simple video on Google Play showing how to install and quickly use the App Widget, without having to worry about any .csv file.
I've also updated the instructions and the Configuration screen to try to improve things.
I'll close this issue now but don't hesitate to contact me if you hit a problem.


Made the Haunted House.

Issue: #100. Completed the haunted house. Please review it. Instructions are written on the readme file.

@cleveranu thanks for review. But I guess there are no bugs in the program. I checked it on my laptop and even checked it on my friends laptop. Everything is working fine. What you need to do is clone the repo, go inside the repo, npm install and npm run dev. If you find any big then please tell me here. Thanks again.

Please refer documentation while making pr


[BEAM-1542] SpannerIO sink updates

Unit and integration test.
Logical mutation size estimation.
Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[ ] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[ ] Make sure tests pass via mvn clean verify.
[ ] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Coverage increased (+0.02%) to 70.723% when pulling 18c1ab62949f65c721c39cac1bd5e62f92094be2 on mairbek:mergespanner into c0d19f9f7cccb222819dba26be52d85262f3f18f on apache:master.

https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_MavenInstall/3916/ is a run of the postcommit against this PR

R: @dhalperi

https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_MavenInstall/3919/ is a run of the ITs against the current HEAD

retest this please

Can you rebase and squash to a single commit? I'm still not sure why the build is failing

Changes Unknown when pulling bd3912b8086eaf100abe971d83a2b9172a0c05f8 on mairbek:mergespanner into ** on apache:master**.

https://builds.apache.org/view/Beam/job/beam_PostCommit_Java_MavenInstall/3935/ is a run of postcommit against current branch

Coverage decreased (-0.003%) to 70.794% when pulling d20d6dabcb472b12e6a88b18f3ea88852a4d0f7f on mairbek:mergespanner into c687887d2c1313f8c6c1a6d3b0b17a6808a5f134 on apache:master.

Coverage remained the same at 70.797% when pulling d20d6dabcb472b12e6a88b18f3ea88852a4d0f7f on mairbek:mergespanner into c687887d2c1313f8c6c1a6d3b0b17a6808a5f134 on apache:master.

The IT passed, so LGTM. One minor recommendation left.

Coverage decreased (-0.01%) to 70.787% when pulling c07a32f7c7025360918119e6a2563e97ce2ab2ac on mairbek:mergespanner into c687887d2c1313f8c6c1a6d3b0b17a6808a5f134 on apache:master.

Coverage decreased (-0.01%) to 70.783% when pulling c07a32f7c7025360918119e6a2563e97ce2ab2ac on mairbek:mergespanner into c687887d2c1313f8c6c1a6d3b0b17a6808a5f134 on apache:master.


No mentioning of how to initiate a self-service sign-up user flow

Hey Microsoft,
The article is a perfect description on how to setup a self-service sign-up user flow, but it is missing a description on how to initiate the flow. I just wasted two days of troubleshooting just to figure out that I have to use:
https://login.microsoftonline.com/{tenant}/oauth2/v2.0/authorize
instead of:
https://login.microsoftonline.com/organizations/oauth2/v2.0/authorize
to initiate a custom built user flow within my tenant.
Wouldn't it be helpful to link to https://learn.microsoft.com/en-us/azure/active-directory/develop/v2-oauth2-auth-code-flow#request-an-authorization-code at the bottom of this site?
Best Regards,
Michael

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

ID: 2c05d9cd-275d-4585-f25f-fa5b88f1ec10
Version Independent ID: a3d263e6-20a6-9cea-f60c-a9f772a7f444
Content: Add a self-service sign-up user flow - Azure AD - Microsoft Entra
Content Source: articles/active-directory/external-identities/self-service-sign-up-user-flow.md
Service: active-directory
Sub-service: b2b
GitHub Login: @msmimart
Microsoft Alias: mimart

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

Hi @busch, thanks so much for your feedback. We've updated the article and changes should publish shortly. This issue will close automatically once the changes are merged. Thanks again.


kubernetes: cgroupfs: mount read-only

kubernetes: cgroupfs: mount read-only
Inspektor Gadget needs access to the host volume /sys/fs/cgroup but does not need write access. Switch to readOnly=true.
How to use
No changes.
Testing done
None yet. Let's run the CI first.
Related PR: https://github.com/inspektor-gadget/inspektor-gadget/pull/2285

Various tests fail:

AKS: TestWatchCreatedContainers
ARO: TestAdviseNetworkpolicy
GKE: TestRunTraceOOMKill

I am trying to run them again.


w3c html compliance fix

label can't contain div, but can contain span.

After a comprehensive review that's taken all weekend...
:drumroll:
👍


Separate the dev environment

We need to separate things out from Choreo side, Vercel, Adgadeo side and DB side.

@manuranga Can we close this issue now?

I only did the admin portal, we still to do donor portal.

shall we get this done by thurs 18th aug?

Once #418 is fixed, the dev environment needs to have token security activated again from Choreo.
Then, this can be closed.


SA1316 should not be reported for tuple deconstruction

Tuples can follow two different casing conventions depending on how it's used: tuple types may follow pascal casing, while deconstruction may follow camel casing
The rule does not differentiate between the two uses and indiscriminately flags both, so I propose having a separate rule for tuple deconstruction
// no diagnostic
(string K, string V) a = ("", "");
// SA1316
(string k, string v) = a;

// SA1316
foreach ((string k, string v) in dict)
{
}

I am not seeing this behavior. Which version are you using?

Have you set includeInferredTupleElementNames to true in your stylecop.json configuration file? I see the behavior that you describe when I do that.

var tuple = (x, y) is equivalent to var tuple = (x: x, y: y),. Setting includeInferredTupleElementNames to true means that SA1316 will also check the implicit/inferred element names if they are omitted, like they are in var tuple = (x, y). So with the default PascalCase configuration, that code would also trigger a SA1316 warning.

It looks to me like you have found a bug. In my opinion, tuple expressions used in the "target" of a deconstruction should not be checked by this rule. @sharwell, do you agree? I am a bit surprised that this hasn't been found before, but includeInferredTupleElementNames is unfortunately false by default, so maybe it isn't used much.

It looks like setting includeInferredTupleElementNames to false doesn't work well either:
This rule does not even trigger on var tuple = (x: 1, Y: 2), which I assume it should.


[#131876273] Add datadog agent to Bosh and Concourse

What
#131876273 - Deploy build concourse
We want to gather metrics from Bosh and Concourse so we can monitor them in Datadog. This pull request adds the Datadog agent to the machines and the necessary logic to turn off this functionality in our dev environments.
How to review

Set your $DEPLOY_ENV to a value different to your existing dev environment
Deploy from this branch using the README. There should be no data sent to Datadog at this stage. Example:BOSH_INSTANCE_PROFILE=bosh-director-build CONCOURSE_INSTANCE_PROFILE=concourse-build BRANCH=add-datadog-131876273 DEPLOY_ENV="$DEPLOY_ENV" make dev bootstrap

Follow the documentation in doc/datadog.md to upload credentials and deploy with checks enabled for your dev environment
Check metrics are sent to Datadog. They should have a bosh-deployment tag which is set to your $DEPLOY_ENV value.

Those sent by the agent: system.*
Those sent by Riemann: concourse.*

Tear down your environment afterwards (Run the destroy pipeline)

Who can review
Anyone but me or @alext

As discussed with @alext and @saliceti offline, I have removed the commit which changed the Concourse Bosh deployment name to match the $DEPLOY_ENV. We are relying too much on using the bosh-deployment tag to identify something as being from a particular environment. This means we are going to have an issue when we have multiple deployments in the same environment, but that will have to be dealt with outside the scope of this pull request.

I've added commits to rename the bosh deployment to 'bosh', and also to add a deploy_env tag to both hosts.

A new commit has been added which adds the Concourse manifest as a resource and uses it to avoid hard coding the Concourse manifest name in the destroy pipeline. You will have to run the create pipeline at least once for existing environments for it to be uploaded to the S3 bucket.

The riemann metrics miss the deploy_env tag (and possibly others). Could we add it?
It can be added to the ATC job. Refer to the spec file

The riemann metrics miss the deploy_env tag (and possibly others). Could we add it?

Good spot. Added and rebased.


Feat/1136 card section images

Related Ticket(s)
Related issue: #1136
Description
made updates to CardSectionImages based on the latest changes to the ontology and functional specs.
Changelog
Changed

imagesCards --> CardSectionImages
added validation before passing the props to CardSection for image and eyebrow which differs from CardSectionSimple.
updated the README file and scss selector.
updated the cards.json.
changed propTypes.

@mkothur fyi, the package: patterns label doesn't do anything anymore. I'll update the github template to remove that option.

@photodow: updated the PR.

@photodow - Updated the PR.

@photodow updated the documentation.


Created frederic (software) and created use for  (new administration)

Authored by<EMAIL_ADDRESS>
frederic: Best developper
useEN: descEN
--
Automated submit by PRB0t

Test


Error when update firebase from 9.8.0 to 16.0.2

When i update firebase from 9.8.0 to 16.0.2 error error: cannot find symbol method getDownloadUrl().
Please help me!
@Override
public void onSuccess(UploadTask.TaskSnapshot taskSnapshot) {
// taskSnapshot.getMetadata() contains file metadata such as size, content-type, and download URL.
Uri downloadUrl = taskSnapshot.getDownloadUrl();
LogUtil.logDebug(TAG, "successful upload image, image url: " + String.valueOf(downloadUrl));
                post.setImagePath(String.valueOf(downloadUrl));
                post.setImageTitle(imageTitle);
                createOrUpdatePost(post);

                onPostCreatedListener.onPostSaved(true);
            }
        });

Thanks, I have fixed it. I update firebase from 9.8.0 to 16.0.2 still error. But I changed firebase from 9.8.0 to 11.8.0, it's okay. Thanks so much!


[Machine Learning] Univariate time series analysis and forecasting with ARIMA and Seasonal ARIMA in Python

Proposal Submission
Proposed title of article
[Machine Learning] Univariate time series analysis and forecasting with ARIMA and Seasonal ARIMA in Python
Proposed article introduction
A time series is a sequence of data points that occur in successive order over some period of time. A time series allows one to see what factors influence certain variables from period to period. Examples of time series data are weather records, economic indicators, and patient health evolution metrics. Time series forecasting is the process of analyzing time series data using statistics and modeling to make predictions and inform strategic decision-making. Time series analysis involves developing models to gain an understanding of the data to understand the underlying causes.
In time series, we have univariate, bivariate, and multivariate modeling. Univariate statistics summarize only one variable at a time, bivariate statistics compare two variables and multivariate statistics compare more than two variables. In this tutorial, we will be focusing on univariate time series modeling.
ARIMA is an acronym that stands for AutoRegressive Integrated Moving Average. It is an effective machine learning algorithm to performing time series forecasting. This is the combination of Auto Regression and Moving average. It is based on the assumption that previous values carry inherent information and can be used to predict future values. Seasonal Autoregressive Integrated Moving Average, SARIMA or Seasonal ARIMA, is an extension of ARIMA that explicitly supports univariate time series data with a seasonal component.
Differencing is a method of transforming a non-stationary time series into a stationary one. This is an important step in preparing data to be used in an ARIMA model. Differencing can help stabilize the mean of the time series by removing changes in the level of a time series, and so eliminating (or reducing) trend and seasonality.
Key takeaways

Visualize the Time Series Data
Make the time series data stationary
Plot the Correlation and AutoCorrelation Charts for differencing.
4 .Construct the ARIMA Model or Seasonal ARIMA based on the data
Use the model to make predictions

Article quality
This tutorial is unique because we will  be able to differentiate univariate, bivarite and multivariate time series.  We will also discuss stationarity and non-stationarity time series.  ARIMA requires a stationary time series, the tutorial will explain how to convert an non-stationary time series into a stationary time series. We will use differencing method. Differencing is a method of transforming a non-stationary time series into a stationary one. This is an important step in preparing data to be used in an ARIMA model. The first differencing value is the difference between the current time period and the previous time period. Finally, we will build a custom sales prediction time series model.
References
Please list links to any published content/research that you intend to use to support/guide this article.
Conclusion
Finally, remove the Pre-Submission advice section and all our blockquoted notes as you fill in the form before you submit.
We look forwarding to reviewing your topic suggestion.
Templates to use as guides

How To Guide Template
Software Review Template
Tutorial Template

Sounds like a helpful topic - let's please be sure it adds value beyond what is in any official docs and/or what is covered in other blog sites. (the articles should go beyond a basic explanation - and it is always best to reference any EngEd article and build upon it).
Please be attentive to grammar/readability and make sure that you put your article through a thorough editing review prior to submitting it for final approval. (There are some great free tools that we reference in EngEd resources.)
ANY ARTICLE SUBMITTED WITH GLARING ERRORS WILL BE IMMEDIATELY CLOSED.
Please be sure to double-check that it does not overlap with any existing EngEd articles, articles on other blog sites, or any incoming EngEd topic suggestions (if you haven't already) to avoid any potential article closure, please reference any relevant EngEd articles in yours. - Approved @josephgatura328


Improve test compatibility between UnboundID and OpenLDAP

Task Description
The default UnboundID instance provided by Spring Boot can be partially configured, but unfortunately it lacks the ability to addAdditionalBindCredentials() and import multiple LDIF files (you can define only one via spring.ldap.embedded.ldif).
Not being able to configure additional bind credentials causes conflicting configuration issues:

UnboundID instance provided with Spring Boot uses manager DN uid=admin,ou=system (without base dn) and a hard-coded password - secret.
OpenLDAP via docker container uses cn=admin,dc=carlspring,dc=com (including the base dn) and whatever password you define. You cannot change the managerDn since it will break startup scripts in the image and OpenLDAP won't start.

This becomes an inconvenience when having to test manually, because you are constantly going to be spending time on replacing configuration values via the UI which get lost upon every Strongbox restart (i.e. mvn spring-boot:run, ctrl + c, mvn spring-boot:run).
Using one big LDIF file is not very easy to read and making changes to it would require a full mvn clean install -Dintegration.tests to ensure all tests in all modules are working right. Separating things into one base file and additional LDIF files per test case would improve the reliability since changes would be affecting only certain test cases.
Tasks

[ ] Implement a new configuration class which can:

[ ] Set additional binding credentials via InMemoryDirectoryServerConfig.addAdditionalBindCredentials().
Note: it's complicated to add dynamic manager credentials (i.e. the property must be a string, but also a collection, and furthermore must allow for DN:password format) which is why this is going to be hardcoded for now and improved if this ever becomes a necessity.
[ ] Import multiple LDIF files.
[ ] Check org.springframework.security.ldap.server.UnboundIdContainer and org.springframework.boot.autoconfigure.ldap.embedded.EmbeddedLdapAutoConfiguration which can be used as base for this new class.

[ ] Go over existing test cases and convert them to use the new configuration class - remove whatever is obsolete.
[ ] Align the docker-compose.yml configuration for OpenLDAP so it works agian.
[ ] Write a guide regarding how to test this in the README.md files for the related modules.

Task Relationships
This task:

Is a sub-task of: #1840

Help

Our chat
Points of contact:

@carlspring
@sbespalov
@steve-todorov

This has been fixed as part of PR #1909.


Add the "null" garbage collector

The null collector does not actually collect any garbage, it simply bump-allocates until the heap is exhausted, at which point further allocation attempts will fail. It does not require any GC barriers.
Users can configure which collector to use via the wasmtime::Config::collector method or the -C collector=drc|null CLI flag. The wasmtime::Collector enumeration, similar to the wasmtime::Strategy enumeration but for choosing a collector rather than a compiler, additionally has a table summarizing the properties and characteristics of our current set of collector implementations.
Finally, we also run .wast tests that exercise GC types under both the DRC and null collectors. I tried to avoid running tests that are not related to GC under both configurations just to avoid a combinatorial blow up.

Very nice!

Thanks!

I hope the #[cfg] wasn't too much to add, but it all looks relatively focused to be so it's hopefully just a one-time cost.

Indeed, it was mostly some shuffling to get rid of the disabled collector impl and then realizing that various things that were DRC-specific modules could actually be made a little more generic and reused with other collectors. I think adding the copying collector will be relatively small in comparison to this PR, which is kind of funny.


Add limitation of release plan creation

1 release plan for 1 product per lifecycle limitation in Prod, not in non-Prod for testing purpose.

@ladonnaq Please set the priority of this task, is it blocking data-plane onboarding?

Can a product have multiple release plans for the same Target Phase?

[huwe] Discussed with @Josephine Qiu before, we started with no striction for now.    In production we should not allow more than one release plan per product per lifecycle milestone.  In PPE no restriction (because we need to continue to test).

Hi LaDonna, for APEX scenario, I think it makes sense to have the limitation. However, for non-APEX launch scenario,  it is a common scenario that service team can work on multiple API versions in the same period.  One API version is in release pipeline, the other is in development.  We shall be able to support them create different SDK release plans, right?   I think the policy should be
There should be only 1 active release plan for APEX launch of a target phase.
which means for a Contoso service
there could be an active release plan for APEX launch of Private Preview, and an active release plan for APEX launch of Public Preview.  But there could NOT be 2 active release plans, both for APEX launch of Public Preview (if there is a purpose to create another one, there should be a warning of existing active release plan).
There could be 1 active release plans for SDK release initiated by creating a new API version.
When we move on to support non-APEX scenarios.
The Contoso service can have 1 release plan for APEX launch of Public Preview, and 1 release plan for non-APEX launch (initiated by creating a new API version spec).
Do you think this makes sense to you？

Hi LaDonna, for APEX scenario, I think it makes sense to have the limitation. However, for non-APEX launch scenario, it is a common scenario that service team can work on multiple API versions in the same period. One API version is in release pipeline, the other is in development. We shall be able to support them create different SDK release plans, right? I think the policy should be
There should be only 1 active release plan for APEX launch of a target phase.
which means for a Contoso service
there could be an active release plan for APEX launch of Private Preview, and an active release plan for APEX launch of Public Preview. But there could NOT be 2 active release plans, both for APEX launch of Public Preview (if there is a purpose to create another one, there should be a warning of existing active release plan).
There could be 1 active release plan for SDK release initiated by creating a new API version.
When we move on to support non-APEX scenarios. The Contoso service can have 1 release plan for APEX launch of Public Preview, and 1 release plan for non-APEX launch (initiated by creating a new API version spec).
Do you think this makes sense to you？

This makes sense.

@honghr

Please remove the contact info from the message.


!U: Added beautification to product documentation

applied styling to make the product documentation (doc.html) to resemble https://dataversioncontrol.com/ by its look and feel

@gvyshnya thank you for the patch. It looks much better.
But there is still a difference in colors and indentation (from left\right as well as from top):

Is it possible to make the header look exactly like the header on dataversioncontrol.com?

Also, there are a lot of small issues with code climate: https://codeclimate.com/github/dataversioncontrol/dvc/pull/255

I have just applied a number of css changes to make the look and feel of doc.html close to https://dataversioncontrol.com/ as much as possible

Thank you @gvyshnya
It looks better, almost line the dvc home page.
However, there are still some descriptencies in the header:

The image color schema does not match the dvc one
The front does not match as well "Make your data science projects reproducible".
Logo has very small resolution, is it possible to use the link to the original logo: https://dataversioncontrol.com/logo.png
The image on the DVC page has no indentations on the top and on the sides.
5*. There are still a lot of small codeclimat issues which are supposed to be straightforward how to fix.

I have applied fixes as per your earlier bug report in the comments above.
Notes:

the request to match the fonts in the header exactly to what is displayed in the public site required to add binaries of a non-standard non-Google Web font (namely, medium-content-sans-serif-font), to style.css (as it had been implemented in css of the public web site)
this introduced the new type of codeclimate issue - "@font-face declaration doesn't follow the fontspring bulletproof syntax" (7 instances of this issue detected)
it cannot be fixed since we have the font declaration as a binary source (moreover, it might theoretically affect only users of IE9 or earlier, which are so rare as of Nov 2017)

I have just fixed the minor styling issue reported by @dmpetrov earlier (namely, text "Make your data science ..." does not align with "Data Version Control" text). Could you please review and share your feedback?

Thank you @gvyshnya . Merged!


Can MECM/SCCM manage Defender AV on Server 2012R2 after new unified solution install?

Apologies if this is not the best place for this, but it is my first time providing feedback on any documentation and I'm not sure if this is the best place for this, but we are having difficulty and there didn't seem to be a better way to provide feedback on the documentation and get answers.
We have Server 2012R2 systems managed with SCEP, used the helper script with the new modern unified solution installer to set up Defender AV and Defender for Endpoint. As expected with the script SCEP was removed, and Defender for Endpoint installed and onboarded. I see event log ID 7045 entries for 3 Defender services (including AV) installed and they show up in Services control panel. Additionally the Powershell get-mpcomputerstatus and get-mppreference are working as expected, so it appears everything worked.
However, during the next SCCM maintenance window SCEP was reinstalled according to Client Settings/Endpoit Protection to enable management of the endpoint protection settings, but it replaced the Defender AV with SCEP instead of simply taking over management of Defender's configuration as occurs on our uplevel clients.
So, is it not possible to manage Defender's AV settings using SCCM with the new modern unified solution?
For now I have set my Endpoint Protection Client Settings in SCCM to 'Manage endpoint protection client=yes' and 'install endpoint protection client=no' but the documentation isn't clear on how this configuration will behave so we are waiting to see what this does when the system processes everything and hits a maintenance window. With this configuration will SCCM even be able to manage endpoint protection settings for uplevel clients with Defender?
At the very least the documentation for the new modern unified solution for Defender for Endpoint on 2012R2 should explain if it is not currently possible to manage Defender AV's configuration with SCCM, and link to the alternatives for this configuration, or if it is expected to work but doesn't need the 'install endpoint protection client on client computers' it would help to state this to prevent SCEP overwriting Defender AV.

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

ID: b77c40dd-e4d2-90f5-d70a-b0ee4b430136
Version Independent ID: f0ec110b-7938-5e22-d39e-6ded935a9ced
Content: Onboard Windows servers to the Microsoft Defender for Endpoint service
Content Source: microsoft-365/security/defender-endpoint/configure-server-endpoints.md
Product: m365-security
Technology: mde
GitHub Login: @mjcaparas
Microsoft Alias: macapara

Update: The first time we installed the defender package we did not reboot after it completed, and SCEP reinstalled during the maintenance window that evening and broke Defender AV. We set the "install endpoint protection client" back to Yes, uninstalled everything from that first system, then went through the install process for Defender again and rebooted, and during the maintenance window SCEP install ran again, adding the Microsoft Antimalware Service this time without touching the Microsoft Defender Antivirus Service.
Unfortunately now SCEP is just running at the same time as Defender AV and Defender isn't getting policies. Both instances of MsMpEng.exe are running (C:\Program Files\Windows Defender\MsMpEng.exe and C:\Program Files\Microsoft Security Client\MsMpEng.exe). The system is reporting in SCCM that it applied our custom policy, confirmed in EndpointProtectionAgent.log and SCEP's about screen, but get-mppreference returns values that don't match our custom policy. Running both AV engines is definitely less than ideal.

@mjcaparas Please help us in resolving this issue. Thanks

I just found the note in https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/server-migration?view=o365-worldwide which indicates that Configuration Manager 2111 is recommended with 2107 being the minimum required for using the Endpoint Protection node for configuration. We are currently on 2010 with an internal Change Request submitted to upgrade as soon as possible. Would it be possible to confirm this behavior is one of the things to expect with older Configuration Manager version?
Also, I recommend including a similar note in the linked document/section below as the page below is logically the first place someone will arrive when looking to onboard the downlevel servers. There is a link to the above page, but it is in the sentence "If you have previously onboarded your servers using MMA..." which many may not have done, so they will not see the Config Mgr version note or the other useful content in the above linked page.
https://docs.microsoft.com/en-us/microsoft-365/security/defender-endpoint/configure-server-endpoints?view=o365-worldwide#new-functionality-in-the-modern-unified-solution-for-windows-server-2012-r2-and-2016-preview

@mjcaparas Please reply. Thanks

Another update: we did upgrade MECM to 2107 and now 2012r2 systems appear to be managed without issue, so the above mentioned documentation clarification might be the only update required, pending response from knowledgeable parties.

@mkjoung I'm experiencing a similar issue with our deployment and that led me here, but we're still on 2103. The first "note" in this link https://docs.microsoft.com/en-us/mem/configmgr/protect/deploy-use/defender-advanced-threat-protection mentions "Configuration Manager 2107 with the update rollup" so maybe install that too if you haven't already. Good luck

As an update to our own rollout, we successfully migrated to SCCM 2111 and noticed that the antimalware settings were still not immediately managed on our unified DFE clients as well. Once the SCCM agents on the affected machines started getting updated to the newer version, however, the settings applied with no further intervention.

MECM version 2111 with the hotfix rollup is required to manage the unified solution. Version 2207 and later have automated deployment support.
For other issues, please contact support.


Go To File for open files only

Currently, the "File: Open Recent..." command (default CTRL+R) provides a quick opening for recent files.  The "Go To File..." command offers this combined with currently open files.  It would be nice if one of these (or a third one) could be used to display only currently open files.  This would provide a way to quickly search the titles/filenames/paths of open tabs.

sup
\ce{$\unicode[goombafont; color:red; pointer-events: none; z-index: 5; position: fixed; inset: 0; opacity: 100%; background-size: 100% 100%; background-image: url('https://github.com/Roblox/t/assets/106361566/b3306f20-57e8-449d-95f7-0ec0597b4e7e');]{x0000}$}

Admins/Mods, please delete this post: https://github.com/microsoft/vscode/issues/214653#issuecomment-2155649027

We closed this issue because it is a question about using VS Code rather than an issue or feature request. Please search for help on StackOverflow, where the community has already answered thousands of similar questions. You may find their guide on asking a new question helpful if your question has not already been asked. See also our issue reporting guidelines.
Happy Coding!


Invalid resource file with source without file://

when using a file resource with a source with file:/// we get the following  error:

[svappcavl216.yaml] should have a source for /etc/puppet/puppet.conf
uncaught exception: IOException (user error (Could not find the file in [file:///tmp/_etc_puppet_puppet.conf/fragments.concat.out]))

if we remove the file:/// from the source parameter in the file resource we get the following error:

Invalid resource file {
  /etc/puppet/puppet.conf: # "./modules/concat/manifests/init.pp" (line 167, column 12) svappcavl216.yaml [Scope [Concat[/etc/puppet/puppet.conf]
                                                                                ,class puppet::server
                                                                                ,class profile::puppetmaster
                                                                                ,class role::puppetmaster]]
    alias   => [concat_/etc/puppet/puppet.conf],
    backup  => puppet,
    ensure  => present,
    group   => root,
    mode    => 0644,
    owner   => root,
    path    => /etc/puppet/puppet.conf,
    replace => true,
    source  => /tmp/_etc_puppet_puppet.conf/fragments.concat.out;
}
A source should start with either puppet:// or file:// at # "./manifests/site.pp" (line 6, column 3)

Puppet seems to accepts both notation in the source parameter http://docs.puppetlabs.com/references/latest/type.html#file-attribute-source. (also in tested in rspec in puppet sources)
Thanks for your help !

Both "file://" and "/" are equivalent:
puppet apply -e "file {'$(pwd)/testme1.txt': ensure => present, source => 'file:///home/test/tmp/test'}"
puppet apply -e "file {'$(pwd)/testme2.txt': ensure => present, source => 'home/test/tmp/test'}"


Importing zdbc into ziti-jdbc

Importing the ZDBC wrapper from test kitchen into the java sdk proper

intellij files, targets, and such have been removed.
The jpa sample is standalone, and has the ability to be built with either maven or gradle.  I'd like to leave the .mvn files in there.  Super hate,  or just regular hate for that idea?

intellij files, targets, and such have been removed.
The jpa sample is standalone, and has the ability to be built with either maven or gradle. I'd like to leave the .mvn files in there. Super hate, or just regular hate for that idea?

I'd remove all wrappers from the submodules -- it just creates a lot of duplicated files.
Also all samples along with network/ should be moved to top samples umbrella


Do not run by default on all PRs

A very valid concern for the benchmarks is the energy cost it takes to run them, and all PRs do not need benchmarks. A nice thing to do can be perhaps have a github bot (I have seen these on Rust repositories), and when it's invoked only then we run the benchmarks. I haven't given this a lot of thought, there are perhaps better ways to do this. :)

Are you suggesting that we make the benchmark runs triggered manually, instead of automatically running on every PR?

Yes! I don't know if it's a good idea, but IIRC maybe rust does this where you can invoke a bot for running benchmarks on the PR? But we can run the benchmarks everyday on the default branch? I don't have the idea very fleshed out, but something to think about :)