The error of running the example

When I run the example of pi-exchange, the following error happens
(py3.7-helics-2.6.1) lei@lei-VirtualBox:~/Install_package/helics-cli/examples/pi-exchange$ helics --version
helics, version 0.1.0a
(py3.7-helics-2.6.1) lei@lei-VirtualBox:~/Install_package/helics-cli/examples/pi-exchange$ helics run --path runner.json
Traceback (most recent call last):
  File "/home/lei/anaconda3/envs/py3.7-helics-2.6.1/bin/helics", line 8, in <module>
    sys.exit(cli())
  File "/home/lei/anaconda3/envs/py3.7-helics-2.6.1/lib/python3.7/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/home/lei/anaconda3/envs/py3.7-helics-2.6.1/lib/python3.7/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/home/lei/anaconda3/envs/py3.7-helics-2.6.1/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/lei/anaconda3/envs/py3.7-helics-2.6.1/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/lei/anaconda3/envs/py3.7-helics-2.6.1/lib/python3.7/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/home/lei/anaconda3/envs/py3.7-helics-2.6.1/lib/python3.7/site-packages/helics_cli/cli.py", line 168, in run
    if config["broker"] is True:
KeyError: 'broker'

Is there anything I forget to do before run it? I just install the helics-cli, and I also cannot run the validation successfully.

Can you try the latest main branch?

You'll need to use this to install:
pip install git+git://github.com/GMLC-TDC/helics-cli.git@main

You'll need to use this to install:
pip install git+git://github.com/GMLC-TDC/helics-cli.git@main

Just check it, but it leads to another error
(py3.7-helics-2.6.1) lei@lei-VirtualBox:~/Install_package/helics-cli/examples/pi-exchange$ helics
Traceback (most recent call last):
  File "/home/lei/anaconda3/envs/py3.7-helics-2.6.1/bin/helics", line 5, in <module>
    from helics_cli.cli import cli
  File "/home/lei/anaconda3/envs/py3.7-helics-2.6.1/lib/python3.7/site-packages/helics_cli/cli.py", line 18, in <module>
    from . import observer
  File "/home/lei/anaconda3/envs/py3.7-helics-2.6.1/lib/python3.7/site-packages/helics_cli/observer.py", line 23, in <module>
    broker: h.HelicsBroker
AttributeError: module 'helics' has no attribute 'HelicsBroker'

Can you pip uninstall helics and then run pip install helics. You need the one of the pyhelics interfaces instead of the swig interface. You can do pip install helics==2.6.1.post11 if you want HELICS v2.6.1.
See this link for all available releases: https://github.com/GMLC-TDC/pyhelics/releases

Can you pip uninstall helics and then run pip install helics. You need the one of the pyhelics interfaces instead of the swig interface. You can do pip install helics==2.6.1.post11 if you want HELICS v2.6.1.
See this link for all available releases: https://github.com/GMLC-TDC/pyhelics/releases

But in my project(C++), I want to use helics dynamic library to compile it, does it will influence my project?

It shouldn’t affect. You can use any version. We recommend using the latest since that contains the most bug fixes.

With the pyhelics interface, you can also use an environment variable to tell the Python package to use the helics library in a specific local path.

Okay, I'll have a try after my project is done, because Ｉ built helics from source code which took me much time, I'm worried different version of helics (I mean build from source code and pip install helics) will lead to unexpected error, thank you so much.
By the way, if I use pip to install helics, how can I run the hello world example in this link https://docs.helics.org/en/latest/introduction/hello-world.html, I mean how I compile C++ files.

When you pip install helics you’ll always get a separate HELICS library which is what is used in Python (this is usually precompiled). Whether or not you use the same library that Python uses to link to your C++ application is up to you. You can also have the pyhelics interface use the same library that your C++ application uses if you want but you can’t do this last thing with the swig interface. Hope that makes sense?

Yes, I will use anaconda to get a new environment to pip install helics, and test it, thank you so much.

When you pip install helics you’ll always get a separate HELICS library which is what is used in Python (this is usually precompiled). Whether or not you use the same library that Python uses to link to your C++ application is up to you. You can also have the pyhelics interface use the same library that your C++ application uses if you want but you can’t do this last thing with the swig interface. Hope that makes sense?

I've created a new environment with anaconda, and then pip install helics, and pip install git+git://github.com/GMLC-TDC/helics-cli.git@main, but the error is still here.
Successfully installed helics-2.7.0.post8
(helics-cli) lei@lei-VirtualBox:~$ helics
Traceback (most recent call last):
  File "/home/lei/anaconda3/envs/helics-cli/bin/helics", line 5, in <module>
    from helics_cli.cli import cli
  File "/home/lei/anaconda3/envs/helics-cli/lib/python3.7/site-packages/helics_cli/cli.py", line 18, in <module>
    from . import observer
  File "/home/lei/anaconda3/envs/helics-cli/lib/python3.7/site-packages/helics_cli/observer.py", line 23, in <module>
    broker: h.HelicsBroker
AttributeError: module 'helics' has no attribute 'HelicsBroker'

And there is a strange thing that, I certainly installed helics-2.7.0 in the new anaconda environment.
>>> h.helicsGetVersion()
'2.6.1 (2020-10-15)'
>>>

If you can delete the python folder in your installation from source that’ll do it.

Yes, it works, but there is still an error if I enter the direction I install helics from source, but it will disappear in other directory.
(helics-cli) lei@lei-VirtualBox:~$ pwd
/home/lei
(helics-cli) lei@lei-VirtualBox:~$ helics
Usage: helics [OPTIONS] COMMAND [ARGS]...

  HELICS Runner command line interface

Options:
  --version      Show the version and exit.
  -v, --verbose  [x>=0]
  --help         Show this message and exit.

Commands:
  observe
  run       Run HELICS federation
  server
  setup     Setup HELICS federation
  validate  Validate config.json
(helics-cli) lei@lei-VirtualBox:~$ cd software/
(helics-cli) lei@lei-VirtualBox:~/software$ ls
boost_1_65_0  ga        ga-5.7     helics-2.6.1  openmpi1.8.1  xerces-3.2.3
boost_1_70_0  ga-5.6.1  gridlab-d  openmpi       openmpi4.1.0  zeromq
(helics-cli) lei@lei-VirtualBox:~/software$ helics
Traceback (most recent call last):
  File "/home/lei/anaconda3/envs/helics-cli/bin/helics", line 5, in <module>
    from helics_cli.cli import cli
  File "/home/lei/anaconda3/envs/helics-cli/lib/python3.7/site-packages/helics_cli/cli.py", line 18, in <module>
    from . import observer
  File "/home/lei/anaconda3/envs/helics-cli/lib/python3.7/site-packages/helics_cli/observer.py", line 16, in <module>
    file_out = logging.FileHandler("observer.log", mode='w')
  File "/home/lei/anaconda3/envs/helics-cli/lib/python3.7/logging/__init__.py", line 1087, in __init__
    StreamHandler.__init__(self, self._open())
  File "/home/lei/anaconda3/envs/helics-cli/lib/python3.7/logging/__init__.py", line 1116, in _open
    return open(self.baseFilename, self.mode, encoding=self.encoding)
PermissionError: [Errno 13] Permission denied: '/home/lei/software/observer.log'
(helics-cli) lei@lei-VirtualBox:~/software$

That file handler shouldn’t be created at module import time. I think this is a bug in the cli. If so, I’ll fix it. But also, you don’t seem to have write permissions in the software folder. That’s what is causing this error.

Okay, I got it, but there still another problem.
(helics-cli) lei@lei-VirtualBox:~/Install_package/helics-cli$ helics run --path examples/pi-exchange/runner.json
helics-cli [info]: Running federation: pi-exchange
helics-cli [info]: Running federate pisender1 as a background process
helics-cli [info]: Running federate pisender2 as a background process
helics-cli [info]: Running federate pisender3 as a background process
helics-cli [info]: Running federate pireceiver1 as a background process
helics-cli [info]: Running federate pireceiver2 as a background process
helics-cli [info]: Running federate pireceiver3 as a background process
helics-cli [info]: Running federate observer as a background process
Error: FileNotFoundError: [Errno 2] No such file or directory: './bin/helics': './bin/helics'

And another problem raised when I run the validation
(helics-cli) lei@lei-VirtualBox:~/Install_package/helics-cli$ helics run --path examples/echo-federation/HELICSFederation/config.json
helics-cli [info]: Running federation: HELICSFederation
helics-cli [info]: Running federate Federate1 as a background process
helics-cli [info]: Running federate Federate2 as a background process
helics-cli [info]: Waiting for 2 processes to finish ...
helics-cli [error]: Process Federate1 exited with return code 2
helics-cli [error]: Process Federate2 exited with return code 2
helics-cli [info]: Done.
Error: Process Federate1 has failed, killing other processes
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/home/lei/anaconda3/envs/helics-cli/lib/python3.7/threading.py", line 926, in _bootstrap_inner
    self.run()
  File "/home/lei/anaconda3/envs/helics-cli/lib/python3.7/site-packages/helics_cli/status_checker.py", line 39, in run
    raise HELICSRuntimeError("Error has occurred")
helics_cli.exceptions.HELICSRuntimeError: Error has occurred

I don't understand why it is trying to run the observer for you. Can you share the output of cat examples/pi-exchange/runner.json? Also, I don't understand why it is trying to run ./bin/helics?

Here is the output
(helics-cli) lei@lei-VirtualBox:~/Install_package/helics-cli$ cat examples/pi-exchange/runner.json
{
  "federates": [
    {
      "directory": ".",
      "exec": "python -u pisender.py 1",
      "host": "localhost",
      "name": "pisender1"
    },
    {
      "directory": ".",
      "exec": "python -u pisender.py 2",
      "host": "localhost",
      "name": "pisender2"
    },
    {
      "directory": ".",
      "exec": "python -u pisender.py 3",
      "host": "localhost",
      "name": "pisender3"
    },
    {
      "directory": ".",
      "exec": "python -u pireceiver.py 1",
      "host": "localhost",
      "name": "pireceiver1"
    },
    {
      "directory": ".",
      "exec": "python -u pireceiver.py 2",
      "host": "localhost",
      "name": "pireceiver2"
    },
    {
      "directory": ".",
      "exec": "python -u pireceiver.py 3",
      "host": "localhost",
      "name": "pireceiver3"
    },
    {
      "directory": "../../",
      "exec": "./bin/helics observe --federates 6",
      "host": "localhost",
      "name": "observer"
    }
  ],
  "name": "pi-exchange"
}
(helics-cli) lei@lei-VirtualBox:~/Install_package/helics-cli$

Remove the last block, i.e.
    {
      "directory": "../../",
      "exec": "./bin/helics observe --federates 6",
      "host": "localhost",
      "name": "observer"
    }

Or use the most recent commit in helics-cli.

Remove the last block, i.e.
    {
      "directory": "../../",
      "exec": "./bin/helics observe --federates 6",
      "host": "localhost",
      "name": "observer"
    }

Or use the most recent commit in helics-cli.

Yes, this works, but the last problem is still here.
(helics-cli) lei@lei-VirtualBox:~/Install_package/helics-cli$ helics run --path examples/echo-federation/HELICSFederation/config.json
helics-cli [info]: Running federation: HELICSFederation
helics-cli [info]: Running federate Federate1 as a background process
helics-cli [info]: Running federate Federate2 as a background process
helics-cli [info]: Waiting for 2 processes to finish ...
helics-cli [error]: Process Federate1 exited with return code 2
helics-cli [error]: Process Federate2 exited with return code 2
helics-cli [info]: Done.
Error: Process Federate1 has failed, killing other processes
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/home/lei/anaconda3/envs/helics-cli/lib/python3.7/threading.py", line 926, in _bootstrap_inner
    self.run()
  File "/home/lei/Install_package/helics-cli/helics_cli/status_checker.py", line 39, in run
    raise HELICSRuntimeError("Error has occurred")
helics_cli.exceptions.HELICSRuntimeError: Error has occurred

Please note that the path of the json file is in examples/echo-federation/HELICSFederation/config.json

I made some changes that should fix this. You’ll need to update to the latest version of helics-cli.  Can you delete the echo-federation folder and try again?

This works for me:
$ helics --version
helics, version 0.5.1

$ helics setup
~/gitrepos/helics-cli/HELICSFederation/config.json

$ helics run --path HELICSFederation/config.json
helics-cli [info]: Running federation: HELICSFederation
helics-cli [info]: Running federate Federate1 as a background process
helics-cli [info]: Running federate Federate2 as a background process
helics-cli [info]: Waiting for 2 processes to finish ...
helics-cli [info]: Done.

Yes, this works for me, but I think you can revise the README.md, so that it will include HELICSFederation in the path.


Dynamic page title based on error kind

Asana: https://app.asana.com/0/1206594217596623/1208270234071170/f

Sets the page title to match translated heading for that kind of error, e.g.

Phishing: "Warning: This site puts your personal information at risk"
SSL error: "Warning: This site may be insecure"

Testing

Run the macOS app with this branch of C-S-S
Follow the steps to reproduce in the Asana task
Verify that the page title in the back button popover matches the kind of error

Sorry I'm only just getting to this now - I've tested this fix and I think it properly addresses this bug: https://app.asana.com/0/1204023833050360/1208270234071170/f. Are we in a position to rebase and merge this?


Setup CI for our project

We should setup CI pipeline to check if it builds correctly, runs test etc

Implemented in https://github.com/readme-experts/cyberchef/pull/80


Icon Colour Options

The default behaviour of the CDN is to currently display the brand colour version.
I propose that we amend this, so by default no fill colour is used - but a user can use 'brand' in either the light/dark colour to display the brand colour.

 https://cdn.simpleicons.org/adobe/brand
 https://cdn.simpleicons.org/adobe
 https://cdn.simpleicons.org/adobe/black/brand

They should use the jsDelivr or unpkg instead if they want the black one.
This CDN is made for those people who want colors.

But we could feasibly expand the functionality of this CDN. Assuming we're well below Vercel free tier usage?

I don't want this change. This will be a breaking change for my users. I prefer to keep the current logic.
For those Notion users, they need color by default.

How's about this then. Don't break existing functionality, but reserve brand as a keyword that can be used in either place, that and inherit so that people can explicitly call for the brand colour, or for the icon to inherit the colour given by external styles.

The currentColor won't work. The CSS styles cannot cross HTML documents.
Currently, any non-color inputs will be treated as brand color. For example: https://cdn.simpleicons.org/discord/nothing.
So, reserving the brand keyword is unnecessary.

The currentColor won't work. CSS styles cannot cross HTML documents.

Fair enough. I'll remove 'inherit' from the PR.

Currently, any non-color inputs will fallback to brand color.

What about in the dark mode color - for example:
https://cdn.simpleicons.org/adobe/black/nothing

As my documentation mentioned:

Passing in an invalid value will use the default color as a fallback.

As my documentation mentioned:

Passing in an invalid value will use the default color as a fallback.

It doesn't work for the dark-mode colour.
See https://cdn.simpleicons.org/adobe/white/nothing

It should be fixed now.


[Feature Request]

FAQ

[X] I have checked the FAQ and it didn't resolve my problem.

Announcement

[X] I have checked Breaking change announcement.

Minimal reproducible full config
.
Description
Would be awesome to have nvim-cmp enabled in macro.
To implement this, probabily the logic is:
When something is selected in nvim-cmp (inside macro), edit the macro to insert the text that nvim-cmp instead of recording the tabs, up, down, etc.
Steps to reproduce
.
Expected behavior
.
Actual behavior
.
Additional context
No response

Sorry. I gave up supporting the macro. So it's out of scope. If you can implement it, feel free to create PR or separate repo or fork.


Configurable backpack status effect string

Pls make string statusEffects.Effect.m_name at Assets.Backpacks.UpdateStatusEffects() configurable.
It's so long and spammy entry at the effect list.
statusEffects.Effect.m_name = $"{backpackName} $vapok_mod_level {backpackQuality} $vapok_mod_effect";
I can set $vapok_mod_effect to "" but not $vapok_mod_level  as it breaks Extensions.InventoryExtensions.IsBackPackInventory()
I don't think anyone needs to know their backpack quality all the time.
As we can't equip more than one backpack all the info except backpack name and icon is irrelevant.
I couldn't find any string comparison on Effect.m_name so it looks safe.
As a simple solution string could be localized whole with {0} and {1} parameters for name and quality.

I'm aligned with this feeling.  I'll look and see what I can do next time I have the code open.

This will be implemented in release 1.6.23


Build for xenial

testing done:

make itest_lucid
make itest_trusty
make itest_xenial

ugh, it actually failed late with my favorite error:
strip: debian/synapse-tools/opt/venvs/synapse-tools/lib/python2.7/site-packages/stAqfNED: Not enough room for program headers, try linking with -N
strip:debian/synapse-tools/opt/venvs/synapse-tools/lib/python2.7/site-packages/stAqfNED[.note.gnu.build-id]: Bad value
dh_strip: strip --remove-section=.comment --remove-section=.note --strip-unneeded debian/synapse-tools/opt/venvs/synapse-tools/lib/python2.7/site-packages/_cffi_backend.so returned exit code 1
debian/rules:18: recipe for target 'binary' failed

will fix tomorrow

itest_xenial passes now


Bump to release 2.05.58 of deconz

@phdelodder I've invited you to the repo as a collaborator; thanks so much for your PR's recently to help keep the image up-to-date. I could use a maintainer to help me keep up with updates on an ongoing basis.
I'd just ask that you don't make any major changes without us both discussing, but of course do version updates without my input.
My approach is to do an update PR so that you can make sure the travis build passes (meaning that .deb files for both arches are available and that no new dep has been introduced for deCONZ) and that the Docker images will therefore build. Squash merge to master and name the squash merge "Bump deCONZ to 2.05.XX".

Thanks for the invite, I have accepted it. I'll make sure to do always a PR.


Create a dev mode for operator deployment

Currently, the operator always watching the Kubeflow resources to reconcile when something is missing. This is good for production environment, but not very friendly when we need to remove and test resources in our development and testing setup. It would be nice to have a dev_mode flag to disable the operator watcher for development.
/cc @moficodes

How would the reconcilation be triggered then? (I.e. what would the operator do if not watch:) )

I think the goal is to make the operator more like kfctl. With the dev mode operator is just wrapping kfctl running the command once and thats it.
its useful for quickly iterating and testing the operator deployment.

I can take a look at it.

/assign

Why not just use kfctl then?
Or even better, use the operator-sdk tooling for development - https://github.com/operator-framework/getting-started#2-run-locally-outside-the-cluster

This is coming from one of our users who doesn't have much experience as a devops. We probably don't have to disable all the watchers, we only want to disable the watcher for monitoring the k8s resources https://github.com/kubeflow/kfctl/blob/master/pkg/controller/kfdef/kfdef_controller.go#L119

also, this is an opt-out feature, so it shouldn't change the behavior of the current operator deployment.

Why not just use kfctl then?
Or even better, use the operator-sdk tooling for development - https://github.com/operator-framework/getting-started#2-run-locally-outside-the-cluster

For most of our users, kfctl is sufficient in this case. However, we have some users that are using window or have very little experience with terminal. So able to use operator for development would be nice for them.

Can you help me to understand the use case again - maybe with more details? It sounds like there is a very specific case which would get treatment in the operator where it should rather be treated by educating the user(s).

Since the default behavior for operator now is to reapply the kfdef if there a delete event from any kfctl resource, users that made changes to the Kubeflow deployment with kubectl edit instead of updating kubeflow/manifests will lose their configuration. I do agree educating the users is the right approach, but I'm seeing some users are afraid to use operator when they see a big learning curve for deployment.
I suggest only use this flag for users that are deploying Kubeflow by themselves in a dev setup. So those who are interested in the Kubeflow project will be more committed to learn about kustomize and kfdef to deploy Kubeflow with the operator in the right way.

@Tomcli I don't think it is a good idea to override a normal operator workflow to satisfy a small set of users. Another option they can do as @tumido pointed out is to install the operator, install Kubeflow and then pull down the operator pod instance to 0. This will remove the operator pod watching and doing the reconcile function. I am absolutely not a fan of adding code that breaks the fundamental function of an operator.

Thanks @nakfour, pull down the operator pod instance to 0 can be a good option. Then we probably want to add some instructions for:

How to stop watching kubeflow deployment (using kubectl, k8s/ocp ui to cover different audiences)
When to resume watching (e.g. deleting kubeflow, update kfdef)

Hopefully this way we should able to help out our users without changing the operator behaviors.

I was looking for this issue and couldn't find it.😁
Precisely as @nakfour says. My experience with dev setup, when working on adjusting ODH components, I've found out that only either manual kfctl or scaling down the operator after the initial deploy gives me the control I need.
If you need to test the operator interaction with your kfdef, the best way is to let it operate. And if you need to manually modify the manifests after the initial deploy, you should pause the operator - scaling it down is the far most easy option.
This way you also have control over the updated manifests from the repositories specified in kfdef since the operator holds the repository cache in the pods, so when you scale it up again, you have the most fresh manifests available.
I think, if you need to do manual adjustmets, you need to turn the autopilot off first.

btw, @Tomcli this way the whole "dev mode" toggle experience can be as simple as this:
Disable operator
oc patch deployment opendatahub-operator -n openshift-operators -p '{"spec":{"replicas":0}}'

Enable operator
oc patch deployment opendatahub-operator -n openshift-operators -p '{"spec":{"replicas":1}}'

you can also alias it in you bash to something shorter, which makes it even more convenient to use. :slightly_smiling_face:

Thanks @tumido, I can add these instructions to the kubeflow/website and close this issue.


Different NameFormat Types

Hello! First of all: thank you for this great tool. I don't want to miss it in some of my projects :-)
I came across the issue, that I can set NameFormat convention to (eg) hyphenated_lowercase, but when I also want to set function_convention and mixin_convetion to camel_case, the linter still complains that the function and mixin should be written in lowercase with hyphens.
My yml:
NameFormat:
    enabled: true
    variable_convention: hyphenated_lowercase
    function_convention: camel_case
    mixin_convetion: camel_case

Any ideas why this is happening? Thanks for your help in advance! :-)
PS: I am using the current scss-lint version 0.51.0 (and Sass 3.4.22 on macOS Sierra 10.12.1).

This sounds like a bug to me. I don't have time to look into this myself, but we're definitely open for a PR fixing this.

Hey @bennom, I can't reproduce this behavior with the latest version of SCSS-Lint (0.54.0 at time of writing).
Make sure you have the NameFormat linter under the linters key, i.e.
linters:
  NameFormat:
    enabled: true
    ...

Furthermore, you misspelled mixin_convetion (missing an n).
Using the following .scss-lint.yml:
linters:
  NameFormat:
    enabled: true
    variable_convention: hyphenated_lowercase
    function_convention: camel_case
    mixin_convention: camel_case

...against the following SCSS file:
$myVar: 'hello';

@function my-func() {
}

@mixin my-mixin() {
}

...I get the following output:
test.scss:1:2 [W] NameFormat: Name of variable `myVar` should be written in all lowercase letters with hyphens instead of underscores
test.scss:3:1 [W] NameFormat: Name of function `my-func` should be written in camelCase format
test.scss:6:1 [W] NameFormat: Name of mixin `my-mixin` should be written in camelCase format

Hope that helps!


Don't override/monkey patch String class

This is pretty unexpected : https://github.com/awesome-print/awesome_print/blob/master/lib/awesome_print/core_ext/string.rb
Defining those methods here https://github.com/awesome-print/awesome_print/blob/master/lib/awesome_print/colorize.rb with a string argument would be cleaner.

Yes, i notice, ap auto require awesome_print/core_ext/string.rb
if make String#instance_methods more confusing ...

Maybe we should add a config option to permit disable it.

Maybe we should add a config option to permit disable it.

or implement it properly : https://github.com/awesome-print/awesome_print/pull/421


Bug: List Domains not showing domains

What were you trying to achieve?
list domains
What are the expected results?
A list of my domains
What are the received results?
I receive an empty list:
{
    "total": 0,
    "offset": 0,
    "limit": 10,
    "status": "all"
}

I would like when I list domains with http://localhost:8189/domains , I should receive a list of my domains, at least the enabled ones.
Seems that when I list domains with status=all query parameter, I receive an empty response
Steps To Reproduce

log into magistrala
create domain
list domains with status=all

In what environment did you encounter the issue?
Magistrala current main branch
Additional information you deem important
I think it is related to this https://github.com/absmach/magistrala-old/pull/248
No response

@ianmuchyri Please double-check, this is supposed to be fixed. Please add a reference to the PR that fixed it.

It was resolved in this pr: https://github.com/absmach/magistrala-old/pull/248
However, is it suitable to list all domains by default, or should we only be listing enabled domains by default?
@arvindh123 , @dborovcanin . This is based on this discussion:

We should list only enabled domains (also everything else) by default, if not specified otherwise.


Which subprojects are part of the Servo Project?

The main servo/servo project and servo/servo.org are part of the move to an independent Servo project, but we need a process for other projects to move too.

It seems we have been following what @SimonSapin suggested on the last comment, so we can close this now.


Process comments in template literal

When writing styles which go beyond 10 or so lines, you may want to add in comments. Or you may just want to write a comment to explain to your team why you wrote a specific line. As far as I know the only way to do that inside a template literal is to do ${/* comment */''}.
Using this processor, the comment will be processed as undefined, so when you have multiple comments in your style you will get the stylelint error Unexpected duplicate "undefined"   declaration-block-no-duplicate-properties.
Example:
${/* My comment */''}

.something {
    color: red;
}

My guess would be that the solution to try and process these as normal CSS comments?

Yes comments can definitely be necessary, but then you can just do this:
import styled from 'styled-components'

const Container = styled.div`
  /* a comment here */
  /* and one here */
  margin: 0 auto;
  /* and another one here */
  max-width: 30rem;
  padding: 1rem;
`

export default Container

I'll close this since parsing js comments to css comments would be unnecessarily complex when you can just use css comments. However, it is unexpected that ${''} is evaluated to undefined. I'll open a new issue for that. Thanks for reporting this and let me know if you have any other questions.


[util] remove allowDoNotWait from example config

Missed in https://github.com/doitsujin/dxvk/pull/2815

Thank you.


action on user leave room

What should happen to the hand  of a player when he/ she leaves the room?
At the moment the cards in the hand just 'disappear'. Possibly move cards to the sink, as mentioned in issue #129 . Other option if to place card back in the deck or just on the table. Maybe we should make this configurable.
Other thing that should be added is a pop up 'Are you sure you want to leave (you will lose your current hand)'

I think at least for now (as we don't have a sink yet) we should implement that the cards go back to the deck or the table, so that you can't completely lose cards if someone leaves.


Add test support for @RequestMapping(path = "/"). Fixes gh-387.

@calaroche Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@calaroche Thank you for signing the Contributor License Agreement!

Thanks, @calaroche. Will review this tomorrow.

Closing due to lack of activity.


add getMultipleAccounts for Token

impl of getMultipleAccounts allows to request multiple token accounts in a single RPC call compared to getAccount which can only get 1 account per RPC call

Ah sorry, looks like you'll need to rebase on https://github.com/solana-labs/solana-program-library/pull/2995 to fix the audit issue

There's a build issue when updating to the new @solana/web3.js, so I'll take care of that in #3001, then you'll have to rebase once more before we can merge.  We're close!

Looks great, thanks for the contribution!


GradientModelSelection.select_model_ep_inference test fails on buildbot

Logs can be found here.

Next build was successful.

This is a random error that is caused by an ill posed optimization problem so NLOPT reaches floating point epsilon. This should not cause an error but simply a warning...thats the fix


Deep vs Shallow Copy in Java

This code is associated with the article titled "Deep Copy vs Shallow Copy in Java"

Closed this, as this is only for evaluation.


[DS-3182] Metadata Registry deletion of field - JSPUI Test Plan Ref MR1

https://jira.duraspace.org/browse/DS-3182
While the code is open:  change all instances of sending equals(constant) to a String variable into constant.equals(variable).

+1 This looks like a very obvious win to me.

inspected and tested (creation, move and deletion of a metadata field). +1


Mark large_image_changer tests as not flaky

They appear to be passing now.

Landing on red to kick infra.


Use a pointer cursor when hovering the Show in File Manager button

This isn't consistent with other buttons, but helps people notice the button is actually clickable.
This partially addresses https://github.com/godotengine/godot-proposals/issues/619.

For me it's the same as #31620, I don't like hardcoding a custom cursor for only specific editor widgets, when there are hundreds of Buttons in the editor which won't follow the same logic.
Either this is made a feature of Button itself, or it's not used.
If Buttons don't appear clickable currently, that's a bug and it should be solved in the theme for all buttons, not just for this single one.

Superseded by https://github.com/godotengine/godot/pull/45642.


Add Mission documentation

This adds mission/auto mode documentation as discussed in #220.
The documentation includes two examples, example pages, and a guide topic. It does not include test code, though I have tested the example code :-)
The documentation concentrates on basic operations. It advises use of GUIDED mode. It mentions that this can be useful for replacing missing guided mode functionality but does not go into this in any detail (I would like to have, but kept running into too many race condition bugs).

@tcr3dr @mrpollo  This should be fairly solid, but would still appreciate review (it is hard to review your own material immediately after creating it).

@hamishwillee This looks really good! :) Added a few suggestions. Let me know when you've looked at them and I will review again for merge.

@tcr3dr Thanks for the review - much appreciated. I've fixed the open issues and this should not be ready to push live.

@tcr3dr Still not live.


Identifiers validation failed for dataset Seabirds in Norway - Estimated population sizes (SEAPOP)

Identifier validation failed for the dataset Seabirds in Norway - Estimated population sizes (SEAPOP):

Crawler attempt: 299
Publishing organization: Norwegian Institute for Nature Research
Publishing country: NORWAY
Installation: NINA IPT service
Number of occurrences indexed for this dataset at the time of the issue: 20191
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 20176 total records; 20176 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3412657/step

New IDs sample:

Old IDs sample:

17
12
15
1
25
18
8
7
5
20

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Seabirds in Norway - Estimated population sizes (SEAPOP) : https://doi.org/10.15468/vomcvi.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

The observations are machine observation and the change of ID went from integers to actual identifiers like "1375C07C-77A9-44C5-A874-0003971A6EC8" so I believe the change was intentional and I doubt they will have documented to ID change.


Depreciate whitelisted function.

Closes #985
I also noticed a reference to whitelisted_function within the book, should this be updated as well?
https://github.com/rust-lang-nursery/rust-bindgen/blob/a371de097f5e37eb01754525fb1e2029ca88b0be/book/src/whitelisting.md
I've started to learn rust recently, so please let me know if there is anything I missed.

@bors-servo r+

I also noticed a reference to whitelisted_function within the book, should this be updated as well?

Nice catch! Want to make a follow up pull request?

:pushpin: Commit f308fbc has been approved by fitzgen

:hourglass: Testing commit f308fbcf19b1de0d4cdbf85cafe5c0043c213b38 with merge 169adb111e3e8c6daa4ea42beb938e2e0874c64e...

And thanks for this PR!

:sunny: Test successful - status-travis
Approved by: fitzgen
Pushing 169adb111e3e8c6daa4ea42beb938e2e0874c64e to master...


CODEOWNERS <-> OWNERS

As an FYI, over on https://github.com/grpc/grpc we're adopting this format for OWNERS files, and have built a conversion script between this format and the new .github/CODEOWNERS format supported by GitHub.
An initial script to do the conversion is included in https://github.com/grpc/grpc/pull/11774.
If there's interest, I'd be happy to get a PR together to share this work here.

Please see https://github.com/bkeepers/OWNERS/pull/6#issuecomment-314157339. This is not the repository that powers the feature.
@bkeepers I'm going to unwatch the repo; seems like our little project has taken off an gone into a different direction. 😆  It was a good spike.

I realize this isn't the code that powers the feature. What we've done is to add a conversion script between this and the CODEOWNERS feature (since we've got some reservations about CODEOWNERS being scalable enough for our purposes).


[WFCORE-772] Rename capabilities provided by extensions

This also includes the commit from #803 as this change is to code modified by that commit.

Linux Build 1999 is now running using a merge of 384237bea5329cd1a37adc3db2b3006e99aa88f3

Core - Full Integration Build 1140 is now running using a merge of 384237bea5329cd1a37adc3db2b3006e99aa88f3

Windows Build 1547 is now running using a merge of 384237bea5329cd1a37adc3db2b3006e99aa88f3

Windows Build 1547 outcome was SUCCESS using a merge of 384237bea5329cd1a37adc3db2b3006e99aa88f3
Summary: Tests passed: 3209, ignored: 71 Build time: 0:23:32

Linux Build 1999 outcome was SUCCESS using a merge of 384237bea5329cd1a37adc3db2b3006e99aa88f3
Summary: Tests passed: 3209, ignored: 71 Build time: 0:26:11

Core - Full Integration Build 1140 outcome was FAILURE using a merge of 384237bea5329cd1a37adc3db2b3006e99aa88f3
Summary: Tests failed: 3 (3 new), passed: 2874, ignored: 377, muted: 1 Build time: 0:50:27
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).noFailover: <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).simpleFailover: <no details avaliable>

org.jboss.as.test.clustering.cluster.web.authentication.FormAuthenticationWebFailoverTestCase(SYNC-tcp).test: <no details avaliable>

Linux Build 2005 is now running using a merge of 04ba52307af24e95d0c4a2d9f9c001ad504d424f

Windows Build 1552 is now running using a merge of 04ba52307af24e95d0c4a2d9f9c001ad504d424f

Core - Full Integration Build 1145 is now running using a merge of 04ba52307af24e95d0c4a2d9f9c001ad504d424f

Windows Build 1552 outcome was SUCCESS using a merge of 04ba52307af24e95d0c4a2d9f9c001ad504d424f
Summary: Tests passed: 3209, ignored: 71 Build time: 0:22:47

Linux Build 2005 outcome was SUCCESS using a merge of 04ba52307af24e95d0c4a2d9f9c001ad504d424f
Summary: Tests passed: 3209, ignored: 71 Build time: 0:25:28

Core - Full Integration Build 1145 outcome was SUCCESS using a merge of 04ba52307af24e95d0c4a2d9f9c001ad504d424f
Summary: Tests passed: 2879, ignored: 377 Build time: 0:53:04

Core - Full Integration Build 1155 is now running using a merge of 36bba15115c3cc1422eb3aa5f8430055b481ad4d

Windows Build 1562 is now running using a merge of 36bba15115c3cc1422eb3aa5f8430055b481ad4d

Linux Build 2016 is now running using a merge of 36bba15115c3cc1422eb3aa5f8430055b481ad4d

Windows Build 1562 outcome was SUCCESS using a merge of 36bba15115c3cc1422eb3aa5f8430055b481ad4d
Summary: Tests passed: 3212, ignored: 71 Build time: 0:22:39

Linux Build 2016 outcome was FAILURE using a merge of 36bba15115c3cc1422eb3aa5f8430055b481ad4d
Summary: Execution timeout (new); tests passed: 2909, ignored: 56; org.wildfly.core:wildfly-core-testsuite-domain Build time: 0:45:09
Build problems:
Execution timeout
Process exited with code 137

Core - Full Integration Build 1155 outcome was FAILURE using a merge of 36bba15115c3cc1422eb3aa5f8430055b481ad4d
Summary: Tests failed: 2 (2 new), passed: 2873, ignored: 395, muted: 1 Build time: 0:48:59
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.deployment.structure.ear.EarJBossDeploymentStructureTestCase: <no details avaliable>

org.jboss.as.test.clustering.cluster.ejb.stateful.StatefulFailoverTestCase(SYNC-tcp).failoverOnStop: <no details avaliable>

retest this please

Linux Build 2026 is now running using a merge of 36bba15115c3cc1422eb3aa5f8430055b481ad4d

Windows Build 1570 is now running using a merge of 36bba15115c3cc1422eb3aa5f8430055b481ad4d

Core - Full Integration Build 1164 is now running using a merge of 36bba15115c3cc1422eb3aa5f8430055b481ad4d

Windows Build 1570 outcome was SUCCESS using a merge of 36bba15115c3cc1422eb3aa5f8430055b481ad4d
Summary: Tests passed: 3212, ignored: 71 Build time: 0:22:35

Linux Build 2026 outcome was SUCCESS using a merge of 36bba15115c3cc1422eb3aa5f8430055b481ad4d
Summary: Tests passed: 3212, ignored: 71 Build time: 0:25:18

Core - Full Integration Build 1164 outcome was FAILURE using a merge of 36bba15115c3cc1422eb3aa5f8430055b481ad4d
Summary: Tests failed: 1 (1 new), passed: 2879, ignored: 395 Build time: 0:48:54
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.clustering.cluster.sso.ClusteredSingleSignOnTestCase(SYNC-tcp).testNoAuthSingleSignOn: <no details avaliable>

Linux Build 2030 is now running using a merge of 7013d324214549f510ff0cfd52d29b72112c9bdd

Windows Build 1575 is now running using a merge of 7013d324214549f510ff0cfd52d29b72112c9bdd

Core - Full Integration Build 1169 is now running using a merge of 7013d324214549f510ff0cfd52d29b72112c9bdd

Windows Build 1575 outcome was SUCCESS using a merge of 7013d324214549f510ff0cfd52d29b72112c9bdd
Summary: Tests passed: 3212, ignored: 71 Build time: 0:24:51

Linux Build 2030 outcome was SUCCESS using a merge of 7013d324214549f510ff0cfd52d29b72112c9bdd
Summary: Tests passed: 3212, ignored: 71 Build time: 0:27:30

Core - Full Integration Build 1169 outcome was FAILURE using a merge of 7013d324214549f510ff0cfd52d29b72112c9bdd
Summary: Tests failed: 2 (2 new), passed: 2877, ignored: 395, muted: 1 Build time: 0:53:48
Build problems:
Failed tests detected
Failed tests
org.jboss.as.test.integration.ejb.mdb.dynamic.DynamicMessageListenerTestCase.test1: <no details avaliable>

org.jboss.as.test.integration.ws.wsse.signencrypt.EJBSignEncryptTestCase.encryptedAndSignedRequest: <no details avaliable>

Looks good


Bug 1997237: Enable Dashboard when ODF is installed

Disable Production mode for now
Use original ODF Storage System Model until https://github.com/openshift/console/pull/9852 is merged.

/bugzilla refresh

/bugzilla refresh


Bootstrap 3.0

with 2.0 theme
Original issue by @bmesuere on Fri Oct 18 2013 at 10:58.
Closed by @bmesuere on Mon Oct 28 2013 at 18:04.

The twitter-bootstrap-rails gem doesn't support bootstrap 3.0 and rails 4.0.
Switch to https://github.com/anjlab/bootstrap-rails or add the files manually: http://www.erikminkel.com/2013/09/01/twitter-bootstrap-3-in-a-rails-4-application/
I prefer the second method.
Original comment by @bmesuere on Sun Oct 20 2013 at 21:20.


FileNotFoundError: [Errno 2] No such file or directory: '/sys/class/power_supply/BAT0/capacity' when trying to initialize "wmcompanion.events.power.PowerActions"

Greetings, so, I have this snippet of code here:
from wmcompanion.events.power import PowerActions

when I run it, it seems that WMCompanion runs into an error whilst trying to connect with the "/sys/class/power_supply/BAT0/capacity" file, necessary for PowerActions to work. This is because many systems actually store this file at "/sys/class/power_supply/BAT1/capacity" or "/sys/class/power_supply/BAT2/capacity" and so on and so forth. This same issue occured in bpytop and was fixed via a merge. I can attempt to fix this via a merge as well if needed. (this is the fix in bpytop -> https://github.com/lwhsu/bpytop/commit/6643dc2605f4eca017c2c5b53ee902c11670157a).
Regards,
Trayambak.

After a bit of tinkering, it seems this (line 202 of wmcompanion/events/power.py) is the causative code. This is not designed to handle anything apart from BAT0.

Good finding. Yes, there are several hard-coded BAT0 instances in power.py that would need to be refactored in order to fully support non-0 indexes by default. I'll take a look at that.

I've mashed up a fix for it, it kinda works. Would you like to check it out?

@xTrayambak I just pushed a fix for it on main, would you mind testing and see if it works out for you?

Sure.

Yeah, it works now. Thanks!


Feature: Add data compression

Since we send everything in clear text we use a large network bandwidth on AWS.
By using zlib and base64 encoding, we should be able to compress/decompress easily (http://devdocs.io/node~6_lts/zlib).
A better alternative would be msgpack5

This also means that all NATS client implementations must support compression. Given that NATS messages can simply be considered as a bag of bytes, it is easy for your applications to compress/decompress as necessary (simply compress before publishing/decompress on receiving a message).

I get your point. I have not thought of other clients.
We will implement it on our application side.

List of available implementation of msgpack5 for different languages


A disabled text input can still be focused, the cursor is blinking

I think this behavior can confuse users if disabled input images are not obvious enough.
The user would think that there is a problem with their keyboard (or other input method).
I would assume that disabled element can't receive focus; or at least the text cursor shouldn't show up (neither blink).

This should be fixed now


Pod objects py3fixes

Support the output of additional data related to Pod objects, namely pod.hostip, pod.internaip and pod.services via sysprint;
Some smaller fixes, cleanup, update of inline documentation.

Forgot the linting step ... will update after that

Added the changes coming from linting

Thanks for this PR!


Add announcement banner feature

What kind of changes does this PR include?

Changes or translations of Starlight docs site content
Changes to Starlight code

Description

Adds a banner feature to Starlight that makes it easy to display an announcement at the top of a page.
Also uses this feature to add a banner to the Starlight docs homepage in preparation for Product Hunt launch next week.

Took a bit of time to research a bit more about the banner role and I am starting to think this may not be a good idea in the end:

We saw Docusaurus using this role but this was added in the initial commit of the feature and not as an improvement which could contains a report / discussion regarding the choice of this role.
The MDN documentation contains some infos that do not really fit an announcement bar:

The description of the banner role does not really match the content of an announcement bar "global site header, which usually includes a logo, company name, search feature, and possibly the global navigation or a slogan".
It "should be reserved for globally repeating site-wide content" but the announcement bar is not global in this implementation.
"each page should generally be limited to a single element with the role of banner" and considering  the HTML's <header> element has an identical role, this would mean that pages with an announcement bar would have two element with the banner role.

I researched a lot of websites that have this kind of announcement bar like Microsoft, Apple, etc. and could not find a single one using the banner role for this purpose.

Considering all this, I think we may not want to use the banner role for this purpose. complementary could be a better choice but only in some cases due to the "can stand alone when separated" requirement. This would be ok for a Product Hunt banner but not for a "Deprecation notice" banner for example. So personally, I think we should not use any specific role for this.

I think we may not want to use the banner role for this purpose. complementary could be a better choice but only in some cases due to the "can stand alone when separated" requirement.

Yeah, I also considered <aside> given that, in the current implementation, it's inside <main> but is not part of the main flow (notably positioned above the first <h1>). Need to think more if that would work or whether the concern for content that isn't strictly complementary means we should avoid it.
Definitely +1 on removing the role=banner though.

Just a random thought. While checking the mobile version of the banner wouldn't this look better if the lines break completely in 2 separate lines, what do you think Chris?

Good shout @dreyfus92! Spent some time making this match @doodlemarks’s designs, so should be good now.


Footer Component Implementation

This component is a must for the project

i agree with that so it will be easier to get footer example


Diffuse texture does not appear when converting from .obj on Sceneform plugin

Hi again,
I am having troubles with getting diffuse texture when rendering .sfb converted by Sceneform plugin from .obj. Interesting is, that models converted by latest version of google-ar-asset-converter works (thanks to @necrostylery https://github.com/necrostylery/google-ar-asset-converter).

Sceneform plugin result

google-ar-asset-converter result
Setup:
Android Studio 3.1.3
Build #AI-173.4819257, built on June 4, 2018
JRE: 1.8.0_152-release-1024-b01 amd64
JVM: OpenJDK 64-Bit Server VM by JetBrains s.r.o
Linux 4.15.0-23-generic
Assets, with both results:
sceneform_vs_necorstylery.zip
Any suggestions how to proceed are appreciate. We are debugging our assets with modelers and this inconsistency makes the process a bit insecure. I notice also troubles with shadow of sofa, which is better for Sceneform. Any advice on what could be wrong with our model would be amazing too.

@terezo - Are you using the 1.3.0 version of the Sceneform gradle plugin or an earlier version?  You should see a dependency in your project gradle file that looks like this classpath 'com.google.ar.sceneform:plugin:1.3.0'

@tpsiaki my mystake, I was using earlier version. I was thinking I've got 1.3.0, since I reinstalled plugin from settings where I saw Install v1.3.0. It did not update my gradle dependency, I think that's not intuitive.

@terezo Thanks. Can you please file a separate request for auto updating the gradle dependency?


chore: Update README.md

What this PR does / why we need it:
Update README.md to include kubernetes.core collection version and simplify install command.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

None

/approve
/lgtm


ARROW-440: [C++] Support pkg-config

pkg-config is a tool to get build flags.
If Arrow supports pkg-config, users can set build flags easily.
For example, CMake supports pkg-config.
To support pkg-config, we just install .pc file that includes build
flags information.

Looking good! Can you add Apache License headers to the new files?

Sure. I've amend the commit and force pushed.


Process is not defined when setting workdirName or mounting files to a specific directory

Describe the bug
Using Vivaldi (Chromium) on MacOS, upon setting a workdirName during WebContainer boot or attempting to mount a FileSystemTree to a mountPoint, the browser console outputs the following error and either fails to boot the WebContainer or fails to mount the FileSystemTree.
Error is reproducible on the WebContainer starter StackBlitz.
StackBlitz:
https://webcontainer.new/
Replace boot line with:
webcontainerInstance = await WebContainer.boot({ workdirName: 'test' });
or replace mount line with:
await webcontainerInstance.mount(files, {mountPoint: 'myFolder'});
Both result in the following error:
Uncaught (in promise) ReferenceError: process is not defined
    at Object.resolve (webcontainer.023ad0e3.js:1:106318)
    at _0x2c9c53._unsynchronizedBuild (webcontainer.023ad0e3.js:1:158741)

Link to the blitz that caused the error
https://stackblitz.com/edit/stackblitz-webcontainer-api-starter-uwntrk?file=main.js
Steps to reproduce
StackBlitz:
https://webcontainer.new/
Replace boot line with:
webcontainerInstance = await WebContainer.boot({ workdirName: 'test' });
or replace mount line with:
await webcontainerInstance.mount(files, {mountPoint: 'myFolder'});
Expected behavior
Should properly set workdirName and properly mount FileSystemTree to mountPoint
Parity with Local

[X] I have run the project in my local machine and I could not reproduce the issue.

Screenshots
No response
Platform

OS: macOS
Browser: Vivaldi (Chromium)
Version: 6.2.3105.48

Additional context
No response

hi! :wave: thanks for reporting this!
we are working on a fix and it should be available soon!

Hello, thanks. Just to add it looks like this is affecting ALL webcontainer.fs operations.

@YeomansIII, yes definitely! The fix should probably land in 3-4 hours at most (maybe less). It's one of those "I screwed up big time" moment. Really sorry for the inconvenience caused.
We'll keep you posted!

Thank you! I'm curious is this some remote code that is loaded? It looks like the @webcontainer/api package hasn't been updated in 3 months, so obviously the issue wasn't a result of the code in that package? Or I just haven't tested this bit in that long :)

The fix has just been deployed! :tada:
So sorry for the inconvenience caused!

I'm curious is this some remote code that is loaded? It looks like the @webcontainer/api package hasn't been updated in 3 months, so obviously the issue wasn't a result of the code in that package?

Correct, the code loaded in the iframe is remote. The @webcontainer/api package contains the code that gets bundled in your application.
It hasn't been updated in 3 months, but it will see updates as we expose more features in the near future! :smiley:
(can't say much more just yet, but it's something that has been requested a couple of times :grin:)

Working great, thanks! Seems like the functionality of mount may be slightly different as it now requires the directory to exist in the fs, which is easy to fix on my end. Is there anywhere these changes are documented?

@YeomansIII Do you have a small repro of the breaking change regarding mount?


403 errors with the python version

In case anyone faces the same issue, I fixed it by changing the two lines (https://github.com/hufman/vgmdb/blob/ed5c3093a11e1d37ef7cd8c3a38724c862d9d40e/vgmdb/parsers/utils.py#L21) to:
                data = requests.get(url, timeout=30)
                data = data.content.decode('utf-8', 'ignore')

as well as
import requests

What does requests do differently compared to urllib2? I'm surprised requests even still works in Py2.

No idea, maybe urllib2 has unsupported ssl ciphers or something. Bumping urllib2 version might even fix it, but I'm more comfortable with requests so this was the first fix I tried.

The 403 errors seem to be coming from Cloudflare. I wonder if Cloudflare has flagged the custom urllib2 user agent, and requests isn't using that and getting through differently.
If you change the requests module to use the same user agent as the urllib2 code, does it show the same 403?


Over the last several months we have made some improvements in this area and I believe that as part of that work this scenario was also addressed. I will go ahead and optimistically close this issue, but in case you are still able to reproduce the problem please feel free to reopen this issue so that I investigate this further. Thanks!


Retry windows wsaserror connection error in HTTPEndpoints TLS test

Windows will sometimes fail integration HTTPEndpoint TLS tests because of wsasend: An existing connection was forcibly closed by the remote host.. PR updates the test to retry the on this specific error when running on windows machines.
See https://github.com/dapr/dapr/actions/runs/6555545725/job/17804233986?pr=7022

LGTM


KyberNetworkProxyInterface is missing trade()

As it is written currently, swapEtherToTokenWithChange() will error on compilation, because KyberNetworkProxyInterface is missing trade(), even though it is implemented in KyberNetworkProxy.
To fix this, you will have to edit KyberNetworkProxyInterface.sol yourself as follows:
function trade(ERC20 src,uint srcAmount,ERC20 dest,address destAddress,
   	uint maxDestAmount,uint minConversionRate,address walletId) public payable returns(uint);

I am not farmiliar with the function swap ether to token with change. Please explain what you mean

Hi yaronvel,
I am following the dApp integration guide here: https://developer.kyber.network/docs/DappsGuide/
Is this still current?

it seems that the guide is using KyberNetworkProxy.sol directly and not the interface. Which is not optimal. We will contact them to fix it.
In the mean time, either import the KyberNetworkProxy.sol or use tradeWithHint. If you pass empty hint, you will get the same effect as trade.
To have an empty hint h, just do:
bytes h = new bytes;

and pass h as hint.

Thanks, using the newer guide now.


app crash after build upload

when I'm uploading my build for testing it successfully uploaded but when I open the app the app crashed everytime,and when I'm integrating react-viro in my existing app it gives error like invalid binary so please help in this
im using latest version of react-viro
"react": "16.3.1",
"react-native": "0.55.1",
"react-viro": "^2.9.1"

Hi @hiteshagja ,
Thanks for reaching out to us. We would need a little more info to be able to look into this. Please fill in details for everything in the checklist below so we know what environment you are running. Also, getting a crash log from your device when the app crashes would be helpful.

[ ] Review the documentation: https://docs.viromedia.com/
[ ] Search for existing issues: https://github.com/viromedia/viro
[ ] Use the latest ViroReact release: https://docs.viromedia.com/docs/releases

Environment
Please provide the following information about your environment:

Development OS: Mac, Windows, Linux
Device OS & Version: What Android OS version (7.0, 8.0, etc.) or iOS version (11.0, 11.2) is your device running on?
Version: ViroReact version and React Native version
Device(s): What device(s) are you are seeing the issue on (i.e. iPhone X, Samsung Note 8, etc)

Description
Describe your issue in detail. Include screenshots if needed. If this is a regression, let us know.
Reproducible Demo
Let us know how to reproduce the issue. Include a code sample, screen capture, video recording. The more information you provide, the better we can support you.


handle null snapshot reference descriptions in markdown editor [AS-799]

DA: smoke-tested locally, but not comprehensively!

Checks passed. I'm setting up my local environment to poke around and also test.

I tested locally and the change looks good. I'll also test in dev once this PR is merged.
Below are the test case steps I ran through:

add snapshot to an existing workspace
rename snapshot
update snapshot description
repeat 2 and 3 with different input strings
delete snapshot from workspace
repeat 1 to 4
rename snapshot using text/strings like 'null', 'undefined'
update snapshot description using text/strings like 'null', 'undefined', empty string
Add snapshot to a new workspace and repeat the above steps


non-ASCII characters, is there a reason?

Question
I would like to create keys which contains Thai letters (ex: "ป็นไรครับ").
Unfortunately, I'm facing the error of non-ascii characters.
Right now, my keys are stored in Firebase and I wanted to sync with Hive.
Is there a technical reason why we couldn't do something like that?
Thanks
Code sample
openBox.put("ป็นไรครับ", 10);
Version

Platform: Mac; ios ; android
Flutter version: 1.9.4+hotfix.4
Hive version: 1.0

Yes there is. Keys have to be read very quickly. It is super fast to read ASCII strings compared to Unicode strings...

Ok.
I'll write that content as a value then :)
Thanks


Created methods to append and finish body content on Request

Replaces #1310
original description
Hi! I just created two methods to append and finish the body content "feed" on request.py so the underlying body instance can have certain flexibility (example: one could use BytesIO instead of a list for storing the body data if a custom Request-like class is provided to the Sanic constructor).
I also modified server.py to reflect the changes on the Request class.
If any documentation is required regarding this, please let me know. Also, I'm not sure if this change is the best approach to the Request.body attribute so I'm open to suggestions :wink:

Codecov Report

Merging #1379 into master will increase coverage by 0.04%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #1379      +/-   ##
==========================================
+ Coverage    81.5%   81.54%   +0.04%
==========================================
  Files          17       17
  Lines        1692     1696       +4
  Branches      321      321
==========================================
+ Hits         1379     1383       +4
  Misses        246      246
  Partials       67       67

Impacted Files
Coverage Δ

sanic/app.py
80.88% <ø> (ø)
:arrow_up:

sanic/cookies.py
82.6% <ø> (ø)
:arrow_up:

sanic/request.py
76.16% <100%> (+0.5%)
:arrow_up:

sanic/testing.py
94.8% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

@sjsadowski would you mind passing over the Project and Milestone from PR #1310 to this one? I really appreciate it, sorry for the mess I made.

Yeap, I had this idea previously.
I'm 900km away from my workstation atm, but I think I'll tackle this with
one idea or another in the docs and also in tests, probably next weekend.
Em dom, 28 de out de 2018 04:26, Adam Hopkins<EMAIL_ADDRESS>escreveu:

@ahopkins commented on this pull request.
In sanic/request.py
https://github.com/huge-success/sanic/pull/1379#discussion_r228737204:

@@ -106,6 +106,12 @@ def bool(self):
return True
return False

def body_append(self, data):

I really like this approach because of the flexibility it provides. But, I
am not keen on the naming of this method. The word append is naturally
tied to lists in Python. If the goal is to allow for any data
structure, I would suggest making a change to abstract the initialization
of the body, and provide a more generic term for body_append.
def init(self, ...):
self.body_init()
def body_init(self):
self.body = []
def body_push(self, data):
self.body.append(data)
def body_finish(self):
    self.body = b"".join(self.body)

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/huge-success/sanic/pull/1379#pullrequestreview-169081109,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABeAsyZ7HHeowrcEA_9_hSVPL9loNTfPks5upVwKgaJpZM4X3xrH
.

I'm holding off on this until @vltr returns and updates the method name.

this is cool, I'm a bit confused by the diff here as there are a bunch of other PR's commits in it but the core content LGTM. Out of curiosity @vltr what sparked your desire to extend the request class?

Oh my, I did a rebase instead of a merge. Where can I hang myself?

@ahopkins done, everything is cleaned up :+1:

Out of curiosity @vltr what sparked your desire to extend the request class?

@abuckenheimer I want to use io.BytesIO or even an asyncio.queues in the future in personal projects instead of an array of bytes, as it is today. Take a look on the custom request class test I made to get a better idea :wink:

The only mention I find of these functions in Sanic archives is in this PR and am wondering whether these were for Sanic internal use only or if some extensions might depend on them. @vltr Do you have any objections to removing these in the streaming branch? Alternatively I could make receive_body call these functions to do the work and avoid breaking them, if that is a concern. Such implementation should be fully compatible with existing code but is also slightly slower and requires more support code.


Chore: update backport bot os

Signed-off-by: Charlie Chiang<EMAIL_ADDRESS>Description of your changes
The backport bot uses ubuntu-18.04, which will be deprecated by 12/1/22 and failures are expected to start since 8/22/22
This pr upgrades it to ubuntu-20.04.
Should buy us two more years.
https://github.blog/changelog/2022-08-09-github-actions-the-ubuntu-18-04-actions-runner-image-is-being-deprecated-and-will-be-removed-by-12-1-22/
Fixes #
I have:

[ ] Read and followed KubeVela's contribution process.
[ ] Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

Special notes for your reviewer

Is it possible to directly upgrade to ubuntu-22?

I assume yes.


Depricate org_special

org_special is used in several view, it will be replaced with org_type.
All the views using this need to be refactored.
We need a plan.

I can extract a report of Organizations and ReferralEntities to help us see how to approach this. Ultimately, I believe we will change the types by hand and then drop the "special" column (not that hard, as we have 55 organizations at the moment).

@pedro-walter I have assigned a type to most Organizations. I need to talk to the client to take care of the rest. Deprecating org_special will also require modifying a few views.


Possibility to access website from multiple teams

Describe the feature or enhancement
In our working environment, we have different teams that need to have access to some websites, that other teams have already access to. Currently I cant enable the following:
team_1:

website-1
website-2
website-3

team_2:

website-2
website-4

Also as admin I would like to see all websites that are created, to have a better overview.
Thanks!

Can't you just add team members to both teams?

No, because the first team is just for internals and the second is shared with some members that should not have access to all internal pages.


TS2304: Cannot find name 'bool'.

I'm getting errors in puremvc-typescript-standard-1.0.d.ts when compiling:
Error:(13, 41) TS2304: Cannot find name 'bool'.
http://www.typescriptlang.org/Handbook#basic-types-boolean
Should the types perhaps be converted to boolean? If so, I can make the change and do PR.

Thanks Josef, if you could PR that would be great.
Cheers,
-=Cliff>
On Jun 11, 2015, at 7:32 AM, Josef van Niekerk<EMAIL_ADDRESS>wrote:

I'm getting errors in puremvc-typescript-standard-1.0.d.ts when compiling:
Error:(13, 41) TS2304: Cannot find name 'bool'.
http://www.typescriptlang.org/Handbook#basic-types-boolean
Should the types perhaps be converted to boolean? If so, I can make the change and do PR.
—
Reply to this email directly or view it on GitHub.

PR created: https://github.com/PureMVC/puremvc-typescript-standard-framework/pull/2

Thank you, sir.


Come up with different name to replace "inline extern"

The "inline externs" in the top level PNA diagram are in a way kind of misnamed, from a strict P4 language specification perspective.
An extern in P4 is either a function, or an object with methods.  Such functions and methods are all intended to be called from a developer's P4 code, and in some cases they return useful values (some have return type void).
The blocks that do encryption and decryption in PNA are more like the packet buffer/traffic manager in PSA -- they receive packets + metadata fields, and then process those packets in a way that can be at least partially controlled by the values of those metadata fields.  Later they send out packets (perhaps modified) plus metadata (derived from the input metadata, the packet contents, and perhaps state internal to the traffic manager, etc.).
I think we should have a different name for such things in general in P4 architectures, preferably used consistently across P4 architectures.
Possibilities:

I have heard them called "fixed function components" or "fixed function blocks", which distinguishes them from P4-programmable blocks in an architecture.
Another name I've heard proposed recently is "Inline Architecture Component"

I am open to other names, but preferably without "extern" anywhere in the name, for the reasons mentioned above.  I really think the name should not be confused with "extern" as used in the P4_16 language specification, which has a precise technical meaning already.

How about "offload engine" ?

@thomascalvert-xlnx We could call them that, but it leads me to wonder: would you be willing to call a switch ASIC's traffic manager an "offload engine"?


what about background image download

is it possible to supply a 100 images may be which the app keeps fetching and storing in the cache even when the app goes to background?

I haven't investigated it yet, but it should be implement using background NSURLSession. I would appreciate any code snippets/PR.
The next release (0.2.0) will be available shortly and will feature AFNetworking as a primary networking option for DFImageManager. It is already available in master. It would be a good idea to implement background downloads with a help of AFNetworking.

This feature should not be included in this framework. You should use background NSURLSession directly in order to do that.


Mining things

About the PR

For https://github.com/space-wizards/space-station-14/issues/14226.
Added mining structures for mining pods, shuttles, etc. for Lavaland Station.
Why / Balance

Technical details

Media

usage example:

mining window:

mining tiles:

[x] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl: NULL882

add: Added Mining Airlock.
add: Added Mining Tiles.
add: Added Mining Window.

Can i see what it looks like with FoV and lighting?

Corner windows please.  Many mappers simply need this. Thank you in advance

shouldnt have a cl since not visible to players

Diagonal windows please. Many mappers simply need this. Thank you in advance

Maybe in the next PR I'll do it.


JavaScript heap out of memory

Hi, we just started using this test reporter with our project and love it! Sometimes the reporter throws a heap out of memory error - is there anything we can configure to help with this? We are running a kotlin and run tests with junit. this is the step:
      - name: Surefire Report
        if: ${{ failure() }}
        uses: ScaCap/action-surefire-report@v1
        with:
          github_token: ${{ secrets.github_token }}
          report_paths: '**/build/test-results/test/TEST-*.xml'

this is the task in our gradle file:
    tasks.withType<Test> {
        reports.junitXml.isEnabled = true
    }

FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

<--- Last few GCs --->

[1937113:0x2c650d0]   137686 ms: Scavenge 2028.3 (2034.9) -> 2028.2 (2040.2) MB, 7.4 / 0.0 ms  (average mu = 0.214, current mu = 0.244) allocation failure
[1937113:0x2c650d0]   137706 ms: Scavenge 2031.5 (2040.2) -> 2031.9 (2040.9) MB, 11.7 / 0.0 ms  (average mu = 0.214, current mu = 0.244) allocation failure
[1937113:0x2c650d0]   137719 ms: Scavenge 2032.1 (2040.9) -> 2031.7 (2052.2) MB, 12.1 / 0.0 ms  (average mu = 0.214, current mu = 0.244) allocation failure

 1: 0x9da7c0 node::Abort() [/home/ubuntu/actions-runner/externals/node12/bin/node]
<--- JS stacktrace --->

==== JS stack trace =========================================

    0: ExitFrame [pc: 0x1374fd9]
Security context: 0x0ce84d3408a1 <JSObject>
    1: write [0x2b782946e3a9] [/home/ubuntu/actions-runner/_work/_actions/ScaCap/action-surefire-report/v1/dist/index.js:~2942] [pc=0x19647738b311](this=0x2ba0bf6a7ba1 <SAXParser map = 0x36e25b3f11c1>,0x2ba0bf6a7b41 <Uint8Array map = 0x2027dce65191>)
    2: /* anonymous */ [0x1fdda25d8fa9] [/home/ubuntu/actions-runner/_work/_actions/ScaCap/action-surefire-report/...

 2: 0x9db976 node::OnFatalError(char const*, char const*) [/home/ubuntu/actions-runner/externals/node12/bin/node]
 3: 0xb39f1e v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [/home/ubuntu/actions-runner/externals/node12/bin/node]
 4: 0xb3a299 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [/home/ubuntu/actions-runner/externals/node12/bin/node]
 5: 0xce5635  [/home/ubuntu/actions-runner/externals/node12/bin/node]
 6: 0xce5cc6 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/home/ubuntu/actions-runner/externals/node12/bin/node]
 7: 0xcf1b5a v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::GCCallbackFlags) [/home/ubuntu/actions-runner/externals/node12/bin/node]
 8: 0xcf2a65 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/home/ubuntu/actions-runner/externals/node12/bin/node]
 9: 0xcf410f v8::internal::Heap::HandleGCRequest() [/home/ubuntu/actions-runner/externals/node12/bin/node]
10: 0xca30f4 v8::internal::StackGuard::HandleInterrupts() [/home/ubuntu/actions-runner/externals/node12/bin/node]
11: 0xff1af7 v8::internal::Runtime_StackGuard(int, unsigned long*, v8::internal::Isolate*) [/home/ubuntu/actions-runner/externals/node12/bin/node]
12: 0x1374fd9  [/home/ubuntu/actions-runner/externals/node12/bin/node]

please let me know if there's any additional useful information i can provide!

i was able to resolve by adding this environment variable in my actions config:
        env:
          NODE_OPTIONS: '--max_old_space_size=4096'

Hi @dwayneyuen, I'm glad you solved it. I never hit this problem. Can you please describe your project a bit: # of files in the repo, # of tests,...

@dwayneyuen Thanks, its working for me :)

check this answer: https://stackoverflow.com/questions/38558989/node-js-heap-out-of-memory/66914674#66914674

i was able to resolve by adding this environment variable in my actions config:
        env:
          NODE_OPTIONS: '--max_old_space_size=4096'

Thanks, it works for me!

dwayneyuen
env:
NODE_OPTIONS: '--max_old_space_size=4096'

Thanks, It's works

i was able to resolve by adding this environment variable in my actions config:
        env:
          NODE_OPTIONS: '--max_old_space_size=4096'

not working for me


Friendship.create return empty responce

Feature Request
Read the Notes and fill out the form.
Notes
Your issue will be closed if you violate any rule below.

You need to include a meaningful description of the feature (and e.g. a screenshot of the app)
Read the Docs.
You can delete this section after reading it.

Form
Put an [x] if you meet the condition, else leave [ ].

[ ] I've searched the Issues
[ ] I've read the basic concepts
[ ] I'm using the latest version

Description
**Friendship.create return empty responce
in log i receive {} , but there is no exeptions appears
my code
async followUser(id) {
     const info = await this.ig.user.info(id).catch(error => error)
     const friendshipStatus = await this.ig.friendship.show(id).catch(error => error);
     if (friendshipStatus.following === true) return friendshipStatus;
     let result = await User.findOrCreate({
         where: {
             pk: id,
             username: info.username
         }
     });
     console.log(JSON.stringify(result[1]))
     if (result[1]) {
         try {
             let makeFriend = await this.ig.friendship.create(id)
             console.log(JSON.stringify(makeFriend))
             return makeFriend
         } catch (error) {
             console.log("Error" + error.responce.body)
             return error
         }

     }
     console.log(JSON.stringify(result[0]))
     return result[0]
 }

**

You might have stringified the error (see #1508). The response will stringify fine.


Add info about carthage usage with xcframeworks and swift pm

Without using --use-xcframeworks the carthage update will fail with:
shell task (...) failed with exit code 1:
fatal error: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/lipo: ... have the same architectures (arm64) and can't be in the same fat output file

Building universal frameworks with common architectures is not possible. The device and simulator slices for "Swinject" both build for: arm64
Rebuild with --use-xcframeworks to create an xcframework bundle instead.

So I updated the readme, I've also added info about swift pm

Hello Tomas!
Thanks for your PR explaining the issue.
I see the CI is breaking at the Linux SPM validation.
I believe we forgot to generate the new Spec (test bundle) for XCTest when we removed Quick/Nimble from the Project.
I'm sorry for that.
Do you want to add it by yourself, or should I make a commit for you?


LLVM 7.0 and clang 7 compiles

Modernize the way we generate memset and memcpy ops -- we still had
some artifacts of LLVM 3.x; since LLVM 4+, there has been a more
direct way to generate the equivalent of memset/memcpy (and be
careful, the API changes slightly for LLVM 7.0).

Some header file changes with llvm 7.

Minor ref-vs-ptr miscellany for WriteBitcodeToFile and CloneModule.

Slight change to addPassesToEmitFile call signature.

I don't expect any measurable speed gain. I think it's just a matter of better notation since real API calls were added instead of hoop jumping with intrinsics.

Can you backport this to the 1.9 branch please?

backport proposed in #919


Draft: Feature/integration

Important change: database is inside docker on <IP_ADDRESS>. You must change it on HOST inside .env file

Things to repair/add:

celary
update document


Clean up warnings

WARNING:py.warnings:/home/vagrant/regulations-site/regulations/generator/layers/utils.py:30:  RemovedInDjango110Warning: render() must be called with a dict, not a Context.
return template.render(c).strip('\n')
WARNING:py.warnings:/home/vagrant/regulation-site/regulations/generator/layers/internal_citation.py:28: RemovedInDjango110Warning: render() must be called with a dict, not a Context.
self.rendered[key] = template.render(c).strip('\n')
WARNING:py.warnings:/usr/lib/python2.7/importlib/init.py:37: RemovedInDjango110Warning: django.core.context_processors is deprecated in favor of django.template.context_processors.
import(name)
WARNING:py.warnings:/home/vagrant/regulations-site/regulations/templatetags/render_nested.py:8: RemovedInDjango110Warning: render() must be called with a dict, not a Context.
return loader.get_template(template).render(Context(context))

This was resolved in the Django 1.11 support PRs


[Parsers] Artefacts with no parser implemented don't take into account "Schema" name

Artefacts such as TableFunction, Procedure and ScalarFunction, which don't have Antlr parser implemented don't use  schema name in their Processors. By default this data objects are created in "DBADMIN" schema, but should be created in the schema defined in their definitions.
This issue has been fixed for hdbsequence artefact and can be used as a reference.

All of the mentioned in the description artefacts TableFunction, Procedure and ScalarFunction have been tested using different, but not DBADMIN schema. All of the artefacts have been created in the schema stated in the artefact's definition.
1. Testing .hdbprocedure

Result:

2. Testing .hdbtablefunction

Result:

3. Testing .hdbscalarfunction

Result:


MCS API to be decomissened on July 2023

Summary
According to this URL:
<EMAIL_ADDRESS>
TL;DR: The legacy Mobile Content Service is going away in July 2023. Please
switch to Parsoid or another API before then to ensure service continuity.
I'm writing about a service decommission we hope to complete mid-July 2023.
The service to be decommissioned is the legacy Mobile Content Service
("MCS"), which is maintained by the Wikimedia Foundation's Content
Transform Team. We will be marking this service as deprecated soon.
We hope that with this notice, people will have ample time to update their
systems for use of other endpoints such as Parsoid [1] (n.b., MCS uses
Parsoid HTML).
The MCS endpoints are the ones with the relative URL path pattern
/page/mobile-sections* on the Wikipedias. For examples of the URLs see the
"Mobile" section on the online Swagger (OpenAPI) specification
documentation with matching URLs here:
https://en.wikipedia.org/api/rest_v1/#/Mobile
[...]

However, those URLs with /page/mobile-sections still seem to be used in Commons app:
./data-client/src/main/java/org/wikipedia/dataclient/RestService.java:    String ACCEPT_HEADER_MOBILE_SECTIONS = ACCEPT_HEADER_PREFIX + "mobile-sections/0.12.4\"";
./data-client/src/main/java/org/wikipedia/dataclient/RestService.java:    String REST_PAGE_SECTIONS_URL = "page/mobile-sections-remaining/{title}";
./data-client/src/main/java/org/wikipedia/dataclient/RestService.java:    @GET("page/mobile-sections-lead/{title}")

Steps to reproduce
API (that seems to be used by Commons app) is deprecated and about to be decommissioned in less than a month.
(it is possible that those strings are some benign leftovers which can be safely removed; but it is also possible that the decommissioning of that API will break things. It should probably be addressed in either case)
Expected behaviour
Commons app should not use deprecated API that is about to be decommissioned
Actual behaviour
Commons app seems to use MCS API that is about to be decomissioned
Device name
n/a
Android version
n/a
Commons app version
4.1.0~1649d1e2c
Device logs
No response
Screen-shots
No response
Would you like to work on the issue?
None

Thanks for the notification! This is being tracked via #5165. So, closing this one :-)


Windows: StdIn being closed when the handle is no longer valid

This bug is for tracking purposes.
Output of docker version:
Client:
 Version:      1.12.0-dev
 API version:  1.25
 Go version:   go1.6.2
 Git commit:   cccfe63
 Built:        Mon Jun 27 11:49:16 2016
 OS/Arch:      windows/amd64

Server:
 Version:      1.12.0-dev
 API version:  1.25
 Go version:   go1.6.2
 Git commit:   cccfe63
 Built:        Mon Jun 27 11:49:16 2016
 OS/Arch:      windows/amd64

Output of docker info:
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 7
Server Version: 1.12.0-dev
Storage Driver: windowsfilter
 Windows:
Logging Driver: json-file
Plugins:
 Volume: local
 Network: nat null overlay
Swarm: inactive
Security Options:
Kernel Version: 10.0 14367 (14367.1000.amd64fre.rs1_onecore_container_hyp.160614-1704)
Operating System: Windows Server 2016 Standard
OSType: windows
Architecture: x86_64
CPUs: 8
Total Memory: 1.61 GiB
Name: WIN-V571EC4DS8B
ID: GEHF:KDWU:3MPT:EIZ6:X7CY:QO4V:5P6O:I6UQ:USWL:TBL4:ZP6C:NGOJ
Docker Root Dir: C:\ProgramData\docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
 <IP_ADDRESS>/8

Additional environment details (AWS, VirtualBox, physical, etc.):
Windows
Steps to reproduce the issue:

docker run -i --rm windowsservercore cmd

exit

Describe the results you received:
Error appears in log:
time="2016-06-27T12:50:18.678035800-07:00" level=error msg="process 6896 in container ade1ce2f92ad8d6a7d81ee428ba78a7b47a95665e39ee7590ae0e6318df6526c CloseStdin failed in Win32: The handle is invalid. (0x6)"

Describe the results you expected:
No error

dibs

#dibs

@darrenstahlmsft were you still working on this?

Yep, will have a PR ready soon

reopening this per https://github.com/docker/docker/pull/26764#issue-178217872


Unable to remove annotation processor warnings from integration tests sourceset

I am using lombok in my gradle project. I have simplified the problem into a very simple project example attached. By following official docs, I am creating a separate source set for integration tests. I am including into integration tests the classpath of common tests, in order to be able to reuse their utils (com.company.utils.Utils in the attached project). I am getting the warning about annotation processors due to this integration tests sourceset, and I am scared I won't be able to move to gradle 5.0 in the future
Expected Behavior

gradlew clean build --warning-mode all

BUILD SUCCESSFUL in 2s
7 actionable tasks: 7 executed

Current Behavior

gradlew clean build --warning-mode all

Task :compileIntegTestJava
The following annotation processors were detected on the compile classpath: 'lombok.launch.AnnotationProcessorHider$AnnotationProcessor' and 'lombok.launch.AnnotationProcessorHider$ClaimingProcessor'. Detecting annotation processors on the compile classpath is deprecated and Gradle 5.0 will ignore them. Please add them to the annotation processor path instead. If you did not intend to use annotation processors, you can use the '-proc:none' compiler argument to ignore them.
BUILD SUCCESSFUL in 2s

Context
I think this is the relevant part:
 sourceSets {
    integTest {
        java.srcDir file('src/integTest/java')
        resources.srcDir file('src/integTest/resources')
        compileClasspath += sourceSets.main.output + sourceSets.test.output+ configurations.compileClasspath + configurations.testRuntimeClasspath
        runtimeClasspath += output + compileClasspath
    }
}

I am scared I can not migrate in the future to new gradle 5.0
Steps to Reproduce (for bugs)

gradlew clean build --warning-mode all

Your Environment

gradlewrapper 4.8
jdk 10.0.2

Download: integration-tests.zip

If you want to use annotation processors, put them into the processor path of your sourceSet, i.e. integTestAnnotationProcessor

@oehme Would you mind specifying in what closure should I write that exactly, and where should it target? I'm unable to make it work
I mean, I understand the compileClasspath += sourceSets.main.output... etc, but
integTestAnnotationProcessor += <?>

I am using lombok annotations (for example @SLF4J) for my source code. I do also want to use those annotations in tests, so I do intend to use those annotation processing, but taking it from source code.
Considering your suggestion, this worked for me, is it correct?
annotationProcessorPath += sourceSets.main.annotationProcessorPath

That works.


Uses relative references in init.py

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Mark Steadman seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Mark Steadman seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


XDG directory functions do not respect XDG variables on macOS

Due to long standing difficulties with (a/the) maintainer of dirs-rs, they refuse to recognize XDG environment variables explicitly defined by the user on macOS: https://github.com/dirs-dev/directories-rs/issues/47. config_directory() will always go to /Users/<username>/Library/Application Support on macOS, even if you have set XDG_CONFIG_HOME. I would suggest using https://github.com/lunacookies/etcetera instead, though there may be other alternatives that also respect user preferences.

Yeah that's sound good, we should still update the documentation for the normal config_directory() functions to clarify that they return the path for the operating system specification - right now they are literally called "XDG Directories", that name (and description) would be fitting for xdg_config_directory() instead :)

Well, dirs is used for other features like global justfile locating:
https://github.com/casey/just/blob/4f31853835afcd8d511fccf7b2b6680f6a628446/src/search.rs#L14-L19
But since that wouldn't affect the backwards compatability of the justfiles themselves would that be a change that could be made at some point as well?

Regarding #2439, I see the benefit, but it seems unfortunate to add a bunch more functions that are very close to existing functions.
An alternative option would be to add a setting, like set use-xdg-directories, which would change the behavior of directory functions to respect the XDG variables.

@uncenter

Due to long standing difficulties with (a/the) maintainer of dirs-rs

Please explain.

@uncenter

Due to long standing difficulties with (a/the) maintainer of dirs-rs

Please explain.

Not sure what you want me to say. Read the issue you just closed and locked conversation on. That kind of response is both childish and a clear example of why moving away from your library is necessary in the first place. There is no reason not to respect environment variables that must be EXPLICITLY DEFINED by the user - it's an intentional disrespect to their choices. If you want to have this conversation, let's unlock that issue and continue over there as to not bother the maintainers of this repository.

Look, I do not have to tolerate targeted harassment for maintaining a library in my own free time and ensuring that the library does exactly what it promises on the tin to its users.
You are not the first person who

thinks their opinion trumps the needs of millions of users of the library that rely on it doing what they chose the library for,
throws a fit when their demands aren't met,
goes around filing issues against projects using dirs and
tries to talk shit behind my back because they cannot respect the choices I have made in my own project.

If you think your behavior is even remotely acceptable, four days before Christmas, please seek appropriate help from a professional, i. e. not me. Because I'm not going to deal with it in any way, shape or form any longer.

If you want to have this conversation

I really don't. Go away.

I'm going to hide as off topic all comments related to what dirs should or shouldn't do. This is the repo for just, and discussion of what other libraries should or shouldn't do is off topic.
I'm actually not sure just should make any changes here.
If users want to use the value of the $XDG_* variables, they can do env('XDG_CONFIG_HOME'), which is short and explicit, and if they don't, they can use the provided functions, like home_directory().
In any case, the documentation should be changed to reflect what the current functions actually do, which is provide paths to system directories.

Updated the readme in #2535.

I think since just provides an easy way to get environment variables, I'm going to close this for now.
I think it's not a bad situation that the functions always return system-specified locations, and users that want the XDG locations can use env.
If we want, we could additionally document the names of the corresponding XDG_* environment variables are for each existing function.


data: yashpandey002

Check List (Check all the applicable boxes)

[X] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[X] This PR does not contain plagiarized content.
[X] The title of my pull request is a short description of the requested changes.

Note to reviewers
PR for Profile addition

Don't over review a particular PR if it been reviewed by couple of people, until unless if there is required changes only then provide you review.

Don't over review a particular PR if it been reviewed by couple of people, until unless if there is required changes only then provide you review.

Really sorry @yashdev9274, will take care of that


the 3D point clouds often jump...

SR305 415 425
I tend to use pyrealsense2 to get the 3d coordinate of a skull model. But the three dimensional pointcloud alwasy change any time, even I used a maching holder. How to get a stable 3d image?

Hi @timeanddoctor   Could you provide an RGB color image of the location where the camera is please so that I can see if there are lighting and environmental factors that could affect the depth measurement, please?  Thanks!

Hi @timeanddoctor  Do you require further assistance with this case, please?  Thanks!

Thank you!
I will update the picture to show what I am doing.

You are very welcome.  Please do provide an image.

Hi @timeanddoctor  If you still require assistance with this case, can you provide an image please?  Thanks!


Can an article be shown without any review?

Since we are storing only associations between article DOIs and review DOIs, if an article without reviews needs to be shown it means we need a different Aggregate Root named Article or similar.

If we do https://github.com/libero/prc/issues/32 this will mean the answer is yes.


downloads dont work, images and videos not loading.

Some images works but most are blank videos also don't work and download out right doesn't work.

same problem!

What does  it do is that the fix? I dont know any of that stuff.

@CaliAlec I'm experiencing the same issue. I attached the screenshot of my extension's console, hope it helps.

Fixed in https://github.com/CaliAlec/ChromeIGStory/pull/73 and in Chrome Web Store version 2.1.5


Fix "unused local variable" and "constant in condition" compilation warnings Fix compilation warnings

Under strict compilation modes, build reports "unused local variable" and "constant in condition" warnings.
This fix is a contribution from Microsoft.

Could you please provide some more background information, such as the compiler error, compiler version and platform. Also, some notes on why changes are necessary in each commit.
I understand the ret variable is probably unused, but it is hard to review without more information.
The ASSERT_REASON macro - where is it defined. It is unlikely from flatcc runtime library and thus likely not portable. What is it trying to fix?

Could you please provide some more background information, such as the compiler error, compiler version and platform. Also, some notes on why changes are necessary in each commit. I understand the ret variable is probably unused, but it is hard to review without more information.
The __ASSERT_REASON__ macro - where is it defined. It is unlikely from flatcc runtime library and thus likely not portable. What is it trying to fix?

yea, sorry about that, pull request was sent prematurely.
provided some more information.

yea, sorry about that, pull request was sent prematurely.
provided some more information.

Thats fine, take your time. Just keep in mind that the project is used by all sorts of different platforms.


MBEDTLS_PSA_CRYPTO_CONFIG for hashes

Continuation of #3670
Continue the process for hash algorithms, HMAC and the hash-based KDF.
If RSA has not been converted to the new style yet (it's a parallel task: https://github.com/ARMmbed/mbedtls/issues/3673), disable it when testing.

There's a commit for the config_psa.h part in https://github.com/ARMmbed/mbedtls/pull/3912.


What if a routine does not require any materials? Enter it in with no materials?

I presume a Routine can be run with no Materials if it's a Mentalist type routine.  Will need to test if the site will allow for no-material Routines.

Yea, there's lots of routines that don't need materials.  I've done tests and it works fine.  In fact, the View page says 'None'.


[1.0] Feature ds:init command

Hi Luan,
This PR adds the command php artisan ds:init.
Using an Artisan command can provide an easier setup process and also saving time, given that users might install LaraDumps during stressful bug chasing  moments.

Some benefits are:

Running ds:init will already publish the config file, if it hasn't been published yet.
The configuration is written in the .env file.
Users will be presented with different settings and tweaks for LaraDumps, knowing what the app has to offer and giving user full control for adjustments without the need to browse the documentation.
The command will detect the files docker-compose.yml and Homestead.yaml, thus suggesting the appropriated host for the app.
The ds:init command counts with a --no-interaction flag, which provides the possibility to automatize the LaraDumps installation process using a single command like:

composer require --dev laradumps/laradumps && php artisan ds:init --no-interaction --host=host.docker.internal --port=9191 --send_queries=true --send_logs=true --send_livewire=false --ide=sublime

The --no-interaction Artisan command  will be output to the user with his preferences at the setup completion.
A ds() is performed after the setup, already giving the user something to see.

The code is not executing artisan config:clear. I am uncertain if it is a good idea to do it without the user consent.
Please let me know if any change is required...
Greetings and thanks,
Dan

Thanks, this is very helpful!


mixer_module: fix poll error in SITL lockstep

This fixes the case where the mixer_module would subscribe and use its own test_motor publication which was created only to make sure the topic is advertised and subsequent updates will work properly.
This happened in SITL lockstep because the timestamp would be 0 at the very beginning, and hence elapsed time would be 0 as well.
This lead to an actuator publication which would then get lockstep out of sync causing poll errors on the Gazebo side.
This fixes #13377 and maybe fixes #13334 and maybe closes #13371.

Grinding this change in https://github.com/PX4/Firmware/commits/pr-poll_timeout_grind to get a better sense of the overall failure rate.


Rename Signing Events to Prevent Naming Collisions

Bug described here: #132
Basically, the events emitted by the SigningManager.ts are very common terms e.g. 'processed' which leads to collisions in the browser with other extensions/pages using the same nomenclature.
Resolution: Prefix the events with 'Signer:' to minimise the chance of collisions.

I would even name it CasperSigner to be extra sure to have no collision at all 👀

Should be fixed by #194

Closed by #251