Forms: Updating "Sending form data"

https://developer.mozilla.org/en-US/docs/Learn/HTML/Forms/Sending_and_retrieving_form_data
This one is OK, but could do with its screenshots updating to modern Firefox, etc.
Also, we should move this to later in the series, as it's the most likely to not be understood, given what other knowledge the readership is likely to have?
Acceptance criteria

[ ] Screenshots updated

GET - do a screen shot of the get header instead of listing what it reads (confusing to readers)
The "localhost:8888" image: make the URL visible.
check MAMP links

[ ] Other updates required

give example of XSS and CSRF
give example of zombie
look into best practices and update them
add a sentence about how client side validation is not enough.

[X] Article moved to a suitable place later in series. This article should be put just before https://developer.mozilla.org/en-US/docs/Learn/HTML/Forms/Sending_forms_through_JavaScript, and they should both be put near the end of the article series.

Moved sending data toward the end of the series.
Move the sending via JS to an advanced section and out of the tutorial flow.

This is done.


Adds spo file rename command. Closes #1763

Adds spo file rename command. This closes #1763

Awesome. Thanks for your work. Will review it shortly 👍

@Adam-it That is true, however I've noticed that the "Recycle()" functionallity is used in quite a lot of other commands, so we should change it in all these commands then.

@Adam-it That is true, however I've noticed that the "Recycle()" functionallity is used in quite a lot of other commands, so we should change it in all these commands then.

yes that may be true... but it may also mean we are doing it wrongly in all of those other places as well 😋. TBH I would need to review each occurrence to be sure. Lets check it/discuss it in a separate issue 👍

@Adam-it I've applied your feedback in this PR. Could you please review?

Awesome. Thanks for your quick response 👍. You rock 🤩
I will review try to review it asap 🙂

@MathijsVerbeeck did you maybe managed to have a look at the tests 🤔? did they work on your end?
I pulled the latest changes locally and I got 4 failing tests

Maybe I am doing something wrong 🙂. Could you double check and let me know ?

Odd, I've run them locally and they appeared to run just fine.
I'll let you know tomorrow.

@Adam-it I forgot to commit my updated test files after changing the this.recycleFile(). My bad!

@Adam-it I forgot to commit my updated test files after changing the this.recycleFile(). My bad!

That's totally fine. Thanks for the quick reaction 👍.
I will try to get back to the review today during night 🙂

Sorry @MathijsVerbeeck I didn't manage to recheck this PR yesterday 😥.
But I plan/hope to do it today 👍. Thanks for your patience

@Adam-it I've implemented your requested changes. Could you please verify that it is working as intended?

@MathijsVerbeeck recheck ✅
Added small formating fixes ✅
Works like a charm 🙂 you rock 🤩
@pnp/cli-for-microsoft-365-maintainers.request(doubleCheck); 🙏

Hey @MathijsVerbeeck, are you still working on this?

Hi @waldekmastykarz. Was planning to work (and finish) this tomorrow. Been quite busy with work lately 😄

@waldekmastykarz Apologies for the very delayed response, however the issues should now be resolved. Could you please recheck?
Thanks!

Thank you for the update @MathijsVerbeeck we will review shortly 👍

@MathijsVerbeeck I unresolved one comment added by Waldek. Could you give it a double check 😉🙏?

thanks @MathijsVerbeeck for your quick commits 😊. Will try to review it asap 👍👍

all good. Ready to be merged 👍

merged manually. good job 👍


Bypass batched fetching for small numbers of resources

Bug report
Reported in https://github.com/Shopify/kubernetes-deploy/issues/313. The root cause there is that the namespace being deployed to has over 4000 pods, most of which are old evicted pods. Since we are unconditionally using the batched fetching strategy, our sync cycles fetch and initialize all 4000+ pods even though in the example given only a single one was needed.
Expected behavior: Polling is instant for small resource groups.
Actual behavior: Polling can take forever for small resource groups, if the cluster contains a large number of resources of that type.
Version(s) affected: Latest.
Proposed solution
Wrap https://github.com/Shopify/kubernetes-deploy/blob/master/lib/kubernetes-deploy/sync_mediator.rb#L32-L37 in something along the lines of if resources.length < LARGE_BATCH_THRESHOLD and add/adjust tests.
cc @dwradcliffe @csfrancis (likely affects overall core deploy speed too) @Shopify/cloudx

The PR has been merged. It still need to be released (waiting to ship 2 or 3 more PRS) then bumped in core.


"IndexError: list index out of range" when parsing line with ;

The issue can be replicated as follows with code is valid python.
$ cat > test.py
import warnings; warnings.filterwarnings("ignore")

$ ufmt check test.py
Traceback (most recent call last):
  File "/usr/local/bin/ufmt", line 8, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1130, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1055, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1657, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1404, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 760, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/ufmt/cli.py", line 119, in check
    changed, error = echo_results(results, quiet=options.quiet)
  File "/usr/local/lib/python3.9/site-packages/ufmt/cli.py", line 41, in echo_results
    msg = lines[0]
IndexError: list index out of range

It looks like the origin of this error is a failed assertion in µsort: see facebookexperimental/usort#203 for details, but then results in an exception with no str() content, triggering a bug in µfmt.

Thank you for reporting this!

I released v2.0.1, which now handles this with a more clear error message:
Error formatting /Users/amethyst/workspace/ufmt/foo.py: AssertionError()
✨ 1 errors ✨

The actual fix will have to happen in usort.


ingress-url-format support $appName under path

Add support for ingress-url-format to allow
ingress.cluster.com/{{$appName}}
We have a use case that we want to use Nginx ingress to host spark ui under DNS name.
And put each spark ui under a path
for example: spark.ui.dns.name.com/{{$appNamespace}}/{{$appName}}
We have it working locally with Nginx ingress, and willing to make a contribution.

@liyinan926 Hi, Li.

i followed the ingressUrlFormat and it got deployed fine. i can see the host and path in kubectl describe ingress. But I'm getting 503 error when i access the UI using http://sample.eastus2.cloudapp.azure.com/spark-apps/spark-pi
Rules:
Host Path Backends
sample.eastus2.cloudapp.azure.com
/spark-apps/spark-pi spark-pi-ui-svc:4040 )

i followed the ingressUrlFormat and it got deployed fine. i can see the host and path in kubectl describe ingress. But I'm getting 503 error when i access the UI using http://sample.eastus2.cloudapp.azure.com/spark-apps/spark-pi
Rules: Host Path Backends
sample.eastus2.cloudapp.azure.com /spark-apps/spark-pi spark-pi-ui-svc:4040 )

Do you solve this problem? I have met this too.
https://github.com/GoogleCloudPlatform/spark-on-k8s-operator/pull/1008
@arthuersundar

I'm also getting 503 error when i access the UI did you get any solutions ?@arthuersundar @andyzheung


Unexpected never-ending repeat exec of command against target at regular intervals

Bug Report
General Troubleshooting steps

[x] Verified running latest release of dbatools?
[x] Verified errors are not related to permissions?
[x] Can duplicate in new/fresh PowerShell.exe session?

Version Information

Operating System (Name|Version): Windows Server 2012 R2 Standard
PowerShell Versions: 5.1.14409.1005 and 5.0.10586.117
SQL Server (Edition|Version): Enterprise 2012

Steps to Reproduce
Run database activity monitoring tool of your choice on target database instance to capture dbatools activity.  Run a command like the following in PowerShell ISE, observe expected activity in monitoring tool.  Wait three minutes, then observe duplicate activity against the target from dbatools when no additional commands have been executed.
Problem to solve
Unexpected and never-ending repeat execution of command against target instance at regular intervals.  Running a command like the following in PowerShell ISE queries the target server for the needed info and returns the results, but then continues to query the target server once every three minutes (without displaying any additional output in PowerShell ISE), and the connection to the server is never closed.  I've seen these stay open for days on end.  Additionally, when PowerShell ISE is finally closed, the PowerShell_ise.exe process in Windows does not end, and the connections to the database are STILL open.  You must force kill the connections on the target server and/or force kill the PowerShell_ise.exe process in Windows.
Example command execution:
Get-DbaDatabaseSpace -sqlserver myservername
Additional information
I'm a fairly new dbatools user, so I'm not certain if this is expected or intentional behavior, but it seems odd.  I mentioned it in the #dbatools Slack channel, and @wsmelton suggested I report it here.  The Get-DbaDatabaseSpace command is mentioned above as an example, but I've seen similar behavior with other commands as well.  Same behavior observed on two clients (clients in this case were running Windows Server OS) against multiple SQL Server instances of multiple versions / builds.  The delay between repeat execution may vary depending on the dbatools command in question.  Same behavior observed in both PowerShell ISE and PowerShell command-line utility (slight difference is that exiting command-line PowerShell process does actually end the Windows process and close database connections without requiring Windows process kill or database connection kill).

Super interesting! We rely on SQL Server Connection pooling to kill threads. If you'd like to force closures, you can Clear-DbaSqlConnectionPool or close the application (ISE/cmd) executing the commands.
Commands should not repeat, however, that's not something I've ever seen. I'll dig into it, thanks for the report.

I can confirm and duplicate this at least from the basic instance I have on my local machine. Ran a command with an XE session monitoring logins and I get multiple.
Left my PS session running in VS Code and restarted my instance (SQL Server) and immediately had two connections show up for dbatools module (application name that we set was showing up) as soon as the instance accepted connections.

Looks like this may have gotten some attention in recent builds like 0.9.42; thank you for this.  It appears that commands such as Get-DbaDatabaseSpace are no longer executed once every three minutes after initial execution.
Interestingly, a portion of the original issue remains -- if running from PowerShell ISE, exiting ISE via the "exit" command does result in closing of the ISE application window, but the corresponding process is still running in Windows and it retains an open connection to any servers which were queried via Get-DbaDatabaseSpace (and possibly other commands/functions) prior to exiting.  User must terminate the ISE process via "End Task" in Windows Task Manager (or similar) to end the process, which in turn closes the open database connections.
The exit behavior from PS.EXE is different -- if you run DbaDatabaseSpace from PS.EXE, then enter "exit" to quit, the application window closes and the corresponding Windows process closes as well, closing any remaining database connections.
Is additional work planned on this issue, or is this the expected behavior when running via ISE?

hey @sqlgb - thanks for reporting this issue (and updating so often 👍 ). We did change our caching from async to sync. I'm not sure about the powershell.exe vs ISE but will have someone look into it.

That behavior is part of the ISE with regards to the process (powershell.exe) still running if you close via exit in the console window. The module would have no control over that application. We cannot control the process not closing itself when you close the ISE.


Add get_preset_name func to EditorExportPlugin

Added get_preset_name func to EditorExportPlugin
Added binding of get_preset_name to EditorExportPlugin
Added documentation for get_preset_name func
Hello everyone, this is my first PR here :)
I expose export preset name to use it inside EditorExportPlugin

Please open a proposal to track the support and details of this feature

There's already a PR (https://github.com/godotengine/godot/pull/90782) that adds a way to get the export preset from an EditorExportPlugin, and then getting the name from there is easy:
get_export_preset().get_preset_name()

Superseded by #90782. Thanks for the contribution!


C::ParseError on normal typedef

I'm trying to parse an header file that includes stdint, but I'm getting a parse error and can't explain the reason. The parse method is raising at line 12 of the following code:
typedef __signed char int8_t;
typedef short int16_t;
typedef int int32_t;
typedef long long int64_t;

typedef unsigned char uint8_t;
typedef unsigned short uint16_t;
typedef unsigned int uint32_t;
typedef unsigned long long uint64_t;

typedef int8_t int_least8_t;

And I get the following error message:

c.y:593:in `parse': 12:0: parse error on ID (int_least8_t) (C::ParseError)

I don't see a reason why this would be an error. Is this a bug?

I got the reason, and it's the first line. The parser does not appear to handle __signed. Changing that line to the following appears to solve the problem:
typedef signed char int8_t;
Unfortunately this is not an option, as this is a system header.

It also applies to __darwin_va_list. The parser doesn't seem to handle types starting with double underscore.

The problem is that these aren't part of the C99 standard. There's some commentary in the readme under "parsing full programs." You can prime the parser with a list of these built in types with C.parser.type_names << '__darwin_va_list'. Less sure about __signed, but the preprocessor may knock that out; otherwise you'll need to do a little massaging prior to passing it to Cast.

Makes sense. The parser can't recognize platform specific types. I'll try using type_names. Thank you!


Using Jenkins automatic instalation on CI/CD provide error

Receive next output:
# sudo python3 -m pip install -U poetry
Requirement already satisfied: poetry in /usr/local/lib/python3.7/dist-packages (1.2.0)
...
Collecting cleo<2.0.0,>=1.0.0a5
  Using cached cleo-1.0.0a5-py3-none-any.whl (78 kB)
...
Installing collected packages: cleo
Successfully installed cleo-1.0.0a5
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
poetry install -vvv --no-ansi
Traceback (most recent call last):
  File "/usr/local/bin/poetry", line 5, in <module>
    from poetry.console.application import main
  File "/var/lib/jenkins/.local/lib/python3.7/site-packages/poetry/console/__init__.py", line 1, in <module>
    from .application import Application
  File "/var/lib/jenkins/.local/lib/python3.7/site-packages/poetry/console/application.py", line 3, in <module>
    from cleo import Application as BaseApplication
ImportError: cannot import name 'Application' from 'cleo' (/usr/local/lib/python3.7/dist-packages/cleo/__init__.py)

Could you please help with this error?

Looking at the paths in the traceback, it looks like some mixup of Poetry 1.1 and 1.2. pip reports Poetry 1.2 and path here:
File "/var/lib/jenkins/.local/lib/python3.7/site-packages/poetry/console/application.py", line 3, in <module>
  from cleo import Application as BaseApplication

is from Poetry 1.1 source code.
Are you sure you don't have both versions of Poetry installed in the same environment?

Are you sure you don't have both versions of Poetry installed in the same environment?

Yep. Look like in system two poetry is exists:
$ find / -name poetry
/var/lib/jenkins/.local/lib/python3.7/site-packages/poetry
/var/lib/jenkins/.local/bin/poetry
/usr/local/bin/poetry
/usr/local/lib/python3.7/dist-packages/poetry

Thank you. Problem was solved.


Publish docker images for ROS 1 + ROS 2 nodes

One method of releasing binaries ahead of the ROS .deb release schedule is via Docker publishing. While this workflow doesn't support everyone's needs, there is enough community interest in Docker images that I think it merits the extra one-time investment in setting it up.

My general take on this is that it isn't the typical mode of using a package in ROS. Some of the items linked are stale and none of them point to that much interest. Its true you can do this - but is anyone that we want testing this today asking for this mode of packaging or will they run from source builds?


Failed with No Reponse Warnings Before HA Core Crash

Version of the custom_component

5.0.1
Configuration
config_entry-meross_lan-bad25ae10b5ed89af4f761002dc837e4.json
Describe the bug
There might be an issue with the latest version of this integration causing a HA core to crash. My normally stable Home Assistant OS setup has crashed three times today with the following error as the last one in the logs:
msg100_###############################7] Appliance.Control.Multiple failed with no response: requests=2 expected size=1030

Debug log
The first log is from the second crash. The second is after enabling debug logging and up to Home Assistant crashing a third time. While not visible or copyable, the final line is full of NULLs like so.
home-assistant-crash-1.log
home-assistant-crash-2.log

Since downgrading to 5.0.0 Home Assistant hasn't crashed.

Hello @Nerwyn,
I'm always a bit suspicious about a piece of python code able to crash the whole application (at least for HA) since any software error in the component is (in the end) managed by the core framework which should just dump a verbose log about the issue and not crash at all. The only thing that comes to mind, since re-installing a previous version fixed the issue, is that the previous 5.0.1 installation was somewhat corrupted. It happens more than it should and I suspect sometimes the HACS download silently fails with no critical errors and so the component looks correctly installed but the whole file base is not properly in place maybe missing some files or even worse, and likely causing the crash, having some files with polluted data...
I wonder if this could also happen when manually using git to download the repository files or any other utility.
At the moment there are no other reports about v5.0.1 hard-crashes like this, and differences in code between 5.0.0 and 5.0.1 are so tiny and mainly pointed at the RollerShutter and Smart Fan/Air purifier that I'm still convinced the issue was not effectively related to a bug in 5.0.1 but, as explained above, to an 'unfortunate' install.
We'll keep an eye on this, nevertheless.

Yup, it happened again twice today despite downgrading. It looks like it's a Zigbee bellows ezsp problem.


(MAINT) Updated changelog for 0.6.1, bumped version to 0.6.2-SNAPSHOT

Updated changelog to reflect changes from https://github.com/puppetlabs/jvm-certificate-authority/pull/43

:+1:

:+1:


Crafting terminal don't get items if the pipe have a Retrieval Module

A pipe that has a retrieval module is not considered a part of the network because the retrieval module is used to export items out of the network.
This is by design.


Within WSL, az artifacts universal download downloads an artifact to wrong destination when supplied with absolute path on Windows fs.

Describe the bug
When inside WSL2 Ubuntu 20.04 terminal, invocation of az artifacts universal download with --path argument specifying and absolute (linux) path located on a Windows filesystem mountpoint, - for example --path /mnt/c/some/dir, - will download the artifact into a totally different C:\mnt\c\some\dir instead of /mnt/c/some/dir.
When --path is supplied with relative path, the downloader works correctly for Windows mountpoints.
To replicate locally:

launch WSL2 Ubuntu20.04 image (probably any other image would do also)
in bash terminal type az artifacts universal download command for some Azure Artifact and set --path /mnt/c/some/dir as a destination to download artifact. This is an absolute path to a native Windows filesystem directory C:\some\dir
run the command and observe that C:\some\dir was not created (if it did’t exist before) or updated. Instead, C:\mnt\c\some\dir directory was created and the artifact was downloaded there.

Environment: reproducible on current latest Windows 10 22H2 build 19045.3693 with the latest WSL2 image of Ubuntu 20.04 with the latest az script, however, this problem persists for more that year and a half already.
Related command
az artifacts universal download
Errors
no errors, command behavior is incorrect
Issue script & Debug output
There's too much of sensitive info in the log and I'm not sure I can clean it up completely (my company has strict infosec policy to which I must comply).
The command works nicely, it just assumes it works in Windows filesystem and therefore it assumes that (Linux abs) path /mnt/c/some/dir  is actually just a path relative to C:\.
Expected behavior
When command is invoked in Linux with absolute path such as /mnt/c/some/dir it must download artifact to that path. On a native Windows filesystem this abs path corresponds to C:\some\dir, not C:\mnt\c\some\dir
Environment Summary
Note, this is the result of az --version invoked from WSL Linux shell and it still assumes it works under Windows, which explains the filesystem issue.
$ az --version
azure-cli                         2.54.0

core                              2.54.0
telemetry                          1.1.0

Extensions:
azure-devops                      0.26.0

Dependencies:
msal                            1.24.0b2
azure-mgmt-resource             23.1.0b2

Python location 'C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe'
Extensions directory 'C:\Users\arechins\.azure\cliextensions'

Python (Windows) 3.11.5 (tags/v3.11.5:cce6ba9, Aug 24 2023, 14:21:31) [MSC v.1936 32 bit (Intel)]

Legal docs and information: aka.ms/AzureCliLegal

Your CLI is up-to-date.

Additional context
No response

Thank you for opening this issue, we will look into it.

Duplicate of https://github.com/Azure/azure-cli/issues/19517


Issue - Large image fails LocalStorage

Add validation to not accept image more then 1MB

Unhandled Rejection (QuotaExceededError): Failed to execute 'setItem' on 'Storage': Setting the value of 'resume' exceeded the quota.


Create comprehensive tests

Create comprehensive tests to run

Tests have been created in version 0.3.0 branch


⚠ ClamAV has degraded performance

In 0fdfe8a, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 202 ms

Resolved: ClamAV performance has improved in ebf8cc1.


RuntimeError: Expected to have finished reduction in the prior iteration before starting a new one.

I'm trainning mask-rcnn with coco dataset meet the erro:
Traceback (most recent call last):
File "./tools/train.py", line 161, in
main()
File "./tools/train.py", line 157, in main
meta=meta)
File "/dicom/Adam/code/mmdetection/mmdet/apis/train.py", line 176, in train_detector
runner.run(data_loaders, cfg.workflow, cfg.total_epochs)
File "/home/ubuntu/miniconda2/envs/Adam_mmlab2.0/lib/python3.7/site-packages/mmcv-0.5.1-py3.7-linux-x86_64.egg/mmcv/runner/runner.py", line 383, in run
epoch_runner(data_loaders[i], **kwargs)
File "/home/ubuntu/miniconda2/envs/Adam_mmlab2.0/lib/python3.7/site-packages/mmcv-0.5.1-py3.7-linux-x86_64.egg/mmcv/runner/runner.py", line 282, in train
self.model, data_batch, train_mode=True, **kwargs)
File "/dicom/Adam/code/mmdetection/mmdet/apis/train.py", line 77, in batch_processor
losses = model(**data)
File "/home/ubuntu/miniconda2/envs/Adam_mmlab2.0/lib/python3.7/site-packages/torch/nn/modules/module.py", line 550, in call
result = self.forward(*input, **kwargs)
File "/home/ubuntu/miniconda2/envs/Adam_mmlab2.0/lib/python3.7/site-packages/torch/nn/parallel/distributed.py", line 462, in forward
self.reducer.prepare_for_backward([])
RuntimeError: Expected to have finished reduction in the prior iteration before starting a new one. This error indicates that your module has parameters that were not used in producing loss. You can enable unused parameter detection by (1) passing the keyword argument find_unused_parameters=True to torch.nn.parallel.DistributedDataParallel; (2) making sure all forward function outputs participate in calculating loss. If you already have done the above two steps, then the distributed data parallel module wasn't able to locate the output tensors in the return value of your module's forward function. Please include the loss function and the structure of the return value of forward of your module when reporting this issue (e.g. list, dict, iterable).
This is my Environment:
sys.platform: linux
Python: 3.7.7 (default, Mar 26 2020, 15:48:22) [GCC 7.3.0]
CUDA available: True
CUDA_HOME: /usr/local/cuda-10.1/
NVCC: Cuda compilation tools, release 10.1, V10.1.243
GPU 0,1: GeForce RTX 2080
GCC: gcc (GCC) 7.3.0
PyTorch: 1.5.0
PyTorch compiling details: PyTorch built with:

GCC 7.3
C++ Version: 201402
Intel(R) Math Kernel Library Version 2020.0.0 Product Build 20191122 for Intel(R) 64 architecture

I try to set find_unused_parameters = cfg.get('find_unused_parameters', True), then the error disappeared, but my training process got stuck.
such as:
2020-06-03 11:29:53,918 - mmdet - INFO - Start running, host: ubuntu@ln-mass, work_dir: /dicom/Adam/code/mmdetection/log/mask_rcnn_r50_fpn_1x
2020-06-03 11:29:53,918 - mmdet - INFO - workflow: [('train', 1)], max: 15 epochs
2020-06-03 11:29:57,301 - mmdet - INFO - Epoch [1][1/53]        lr: 0.00002, eta: 0:43:37, time: 3.296, data_time: 2.563, memory: 3177, loss_rpn_cls: 0.4322, loss_rpn_bbox: 0.0274, loss_cls: 0.2866, acc: 98.8281, loss_bbox: 0.0340, loss_mask: 0.8534, loss: 1.6336
2020-06-03 11:29:57,653 - mmdet - INFO - Epoch [1][2/53]        lr: 0.00012, eta: 0:24:25, time: 0.400, data_time: 0.088, memory: 3456, loss_rpn_cls: 0.0118, loss_rpn_bbox: 0.0035, loss_cls: 0.3228, acc: 98.0957, loss_bbox: 0.0695, loss_mask: 0.7520, loss: 1.1596
2020-06-03 11:29:57,997 - mmdet - INFO - Epoch [1][3/53]        lr: 0.00022, eta: 0:17:46, time: 0.344, data_time: 0.055, memory: 3457, loss_rpn_cls: 0.0452, loss_rpn_bbox: 0.0075, loss_cls: 0.2955, acc: 99.2188, loss_bbox: 0.0237, loss_mask: 0.9116, loss: 1.2836
2020-06-03 11:29:58,332 - mmdet - INFO - Epoch [1][4/53]        lr: 0.00032, eta: 0:14:25, time: 0.335, data_time: 0.040, memory: 3457, loss_rpn_cls: 0.0580, loss_rpn_bbox: 0.0158, loss_cls: 0.3211, acc: 97.9980, loss_bbox: 0.0808, loss_mask: 0.8483, loss: 1.3239
2020-06-03 11:29:58,678 - mmdet - INFO - Epoch [1][5/53]        lr: 0.00042, eta: 0:12:25, time: 0.347, data_time: 0.051, memory: 3457, loss_rpn_cls: 0.0464, loss_rpn_bbox: 0.0083, loss_cls: 0.2969, acc: 97.8027, loss_bbox: 0.0857, loss_mask: 0.9451, loss: 1.3825
2020-06-03 11:29:59,013 - mmdet - INFO - Epoch [1][6/53]        lr: 0.00052, eta: 0:11:04, time: 0.334, data_time: 0.040, memory: 3458, loss_rpn_cls: 0.0614, loss_rpn_bbox: 0.0079, loss_cls: 0.2728, acc: 98.5840, loss_bbox: 0.0533, loss_mask: 0.6696, loss: 1.0650
2020-06-03 11:29:59,348 - mmdet - INFO - Epoch [1][7/53]        lr: 0.00062, eta: 0:10:06, time: 0.336, data_time: 0.052, memory: 3458, loss_rpn_cls: 0.0196, loss_rpn_bbox: 0.0042, loss_cls: 0.2600, acc: 98.8770, loss_bbox: 0.0439, loss_mask: 0.7691, loss: 1.0968
2020-06-03 11:29:59,684 - mmdet - INFO - Epoch [1][8/53]        lr: 0.00072, eta: 0:09:23, time: 0.335, data_time: 0.040, memory: 3458, loss_rpn_cls: 0.0177, loss_rpn_bbox: 0.0068, loss_cls: 0.2538, acc: 97.7539, loss_bbox: 0.0863, loss_mask: 0.8242, loss: 1.1888
it's getting stuck,If you have method to solve the erro ,pls tell me！Thanks

I'm facing similar issue when training Group Norm based models.
How did you resolve this?


how to evaluate maddpg?

how to load .pkl file to evaluate maddpg? Have a  function or related code?
thanks

I am not sure I understood your question properly but here is something that might help...
The code uses torch.load to load pickled files from the tmp/maddpg/<FILE_NAME>. You will have to put your files there and name them accordingly. However, your trained model architecture has to be the same as that provided in the repo, otherwise, it won't work.


Using services in automation actions

Discussed in https://github.com/lbbrhzn/ocpp/discussions/150

Originally posted by jonasbkarlsson September  7, 2021
Not sure what the problem is so I try to ask here.
If I configure the automation action as
service: ocpp.configure
data:
  ocpp_key: MeterValueSampleInterval
  value: "120"

it works well. But if I try
service: ocpp.configure
data:
  ocpp_key: MeterValueSampleInterval
  value: "{{ states('input_number.ocpp_test') | round (0)}}"

I get the ERROR:
2021-09-07 09:47:56 ERROR (MainThread) [homeassistant.components.automation.ocpp_test] OCPP test: Error executing script. Invalid data for call_service at pos 1: expected str for dictionary value @ data['value']
2021-09-07 09:47:56 ERROR (MainThread) [homeassistant.components.automation.ocpp_test] Error while executing automation automation.ocpp_test: expected str for dictionary value @ data['value']

How to convert the numerical value to a string? Or what should be done?

I got some comments on this issue here: (https://community.home-assistant.io/t/creating-string-value-from-input-number-state-in-automation-actions/336473)
So it seems like it needs to be fixed in this integration.

@jonasbkarlsson , I have not tested #153 but according to your link it should solve the templating issue. Please test.

I have tested #153. It solves the templating issue. Great!
PS. I have noticed that this component floods the home-assistant.log with a lot of INFO-level logger messages. Should it really be like that? I needed to add the following four lines in configuration.yaml in order to turn it off.  (And note ocpp and not custom_components.ocpp, which didn't have any effect.)
logger:
  default: warning
  logs:
    ocpp: warning

Ocpp controls the underlying MobilityHouse python logger used to communicate with the charger. Up to you if you want to disable the messages but while the integration is in its infancy it is useful for debugging (eg if an ocpp message is rejected)

Also if your default is warning then I don't think you'll get anything logged when using the custom ocpp services as they are at info level.


Make "page" clickable in info popover

Should open navigator to "page" (ang, panaa, ...)
Requires #441

Note potential scenario:


Failed to read Firebase options from the app's resources.

Please fill in the following fields:
Unity editor version: 2019.3.06f
Firebase Unity SDK version: 6.6.0
Firebase plugins in use (Auth, Database, etc.):https://assetstore.unity.com/packages/tools/network/cross-platform-leaderboard-151816?_ga=2.216116694.174958842.1582891597-1598787340.1576925179
Additional SDKs you are using (Facebook, AdMob, etc.):
Platform you are using the Unity editor on (Mac, Windows, or Linux): Windows 8.1
Platform you are targeting (iOS, Android, and/or desktop): Android
Scripting Runtime (Mono, and/or IL2CPP): Mono
Please describe the issue here:
I'm working on unity project that will post SCORE data to Firebase realtime database (https://assetstore.unity.com/packages/tools/network/cross-platform-leaderboard-151816), and it works when I test on UnityEditor, but not on real mobile android device. :(
Here is the logcat:
02-23 11:34:41.889 13194-13271/com.devzuky.dumpy E/Unity: Failed to read Firebase options from the app's resources. Either make sure google-services.json is included in your build or specify options explicitly.
UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object)
UnityEngine.DebugLogHandler:LogFormat(LogType, Object, String, Object[])
UnityEngine.Logger:Log(LogType, Object)
UnityEngine.Debug:LogError(Object)
Firebase.Platform.FirebaseLogger:LogMessage(PlatformLogLevel, String) (at Z:\tmp\tmp.YjzkX82xZ8\firebase\app\client\unity\src\Unity\FirebaseLogger.cs:95)
Firebase.LogUtil:LogMessage(LogLevel, String) (at Z:\tmp\tmp.BahqeQHBdV\firebase\app\client\unity\proxy\LogUtil.cs:68)
Firebase.LogUtil:LogMessageFromCallback(LogLevel, String) (at Z:\tmp\tmp.BahqeQHBdV\firebase\app\client\unity\proxy\LogUtil.cs:76)
Running on desktop I found Assets\StreamingAssets\google-services-desktop.json -> and if i remove this file, and try to run, it will show the same errors as above.
So I think the android build didn't have the file google-services.json ? How can I added to the build and which location ?

Hi @tkminh,
If this is a bug, I will need you to to try to reproduce this in one of the Unity Quick Start's if possible so we can get a good starting point to work from.
Additionally, upgrading to the latest plugin (version 6.11.0) might help as well. In particular, I see a potentially related fix in 6.8.0.
Since you do see a google-services-desktop.json, I assume that you did download the google-services.json file needed for Android. You can drop it anywhere in your Assets/ directory, although I like to place it under Assets/Data.
Finally, since you do list Auth as one of the SDKs you're using, did you enable the authentication providers you plan on using? You can follow the instructions in the video on this page.
If any of those above steps work, let us know! Otherwise, repro steps in the quickstart will help us a ton!
Thanks,
--Patrick

Hi @patm1987 ,
I solved it by adding below in the mainTemplate.gradle
sourceSets { main { res.srcDirs += '<fullpath>\\Assets\\Plugins\\Android\\Firebase\\res\\values\\googleservices.xml' } }
Many thanks.
Minh

What happen or what changed that we need to add that sourceSets { main { res.srcDirs += something something? What is that thing and why we just need it now to build firebase?

I have the same problem, even adding sourceSets and the google-services.json file, it didn't work, I use UNITY 2019.3.6f1, firebase sdk 6.12.0, windows 10, to create android. I've tested it on other versions of unity and the same error happens.
"Failed to read Firebase options from the app's resources. Either make sure google-services.json is included in your build or specify options explicitly."
I followed the video tutorial https://www.youtube.com/watch?v=A6du3DUTIPI&feature=youtu.be but it doesn't work.
Any other solution?
sorry for the english ... I don't know much ... :)

What happen or what changed that we need to add that sourceSets { main { res.srcDirs += something something? What is that thing and why we just need it now to build firebase?

Because the google file is missing when we build to APK, you can try to debug ABK Profiler to see it. So we just need to find a way to add in our APK.

I have the same problem, even adding sourceSets and the google-services.json file, it didn't work, I use UNITY 2019.3.6f1, firebase sdk 6.12.0, windows 10, to create android. I've tested it on other versions of unity and the same error happens.
"Failed to read Firebase options from the app's resources. Either make sure google-services.json is included in your build or specify options explicitly."
I followed the video tutorial https://www.youtube.com/watch?v=A6du3DUTIPI&feature=youtu.be but it doesn't work.
Any other solution?
sorry for the english ... I don't know much ... :)
After testing a little more, I realized that Unity was not generating the googleservices xml.
Searching I found a site that converts google-services.json to XML values.
  https://dandar3.github.io/android/google-services-json-to-xml.html
I created an xml file, and saved it to the folder, Assets \ Plugins \ Android \ Firebase \ res \ values
I managed to generate the apk and run it without a problem after this change, but there is still an error when I open it
Windows / Firebase / Documentation
"Project Bundle ID com.FirebaseTestProject does not match any bundle IDs in your google-services.json files. This will result in an app that will fail to initialize."
I believe that the error is in the files generate_xml_from_google_services_json exe and py, I'm not sure about that or it could be a Unity error.
Hope this helps.

Please try to add the script in the mainTemplate.gradle
I've tested and it really work.
// Android Resolver Exclusions End
android {
compileSdkVersion APIVERSION
buildToolsVersion 'BUILDTOOLS'
compileOptions {
    sourceCompatibility JavaVersion.VERSION_1_8
    targetCompatibility JavaVersion.VERSION_1_8
}

defaultConfig {
    minSdkVersion **MINSDKVERSION**
    targetSdkVersion **TARGETSDKVERSION**
    ndk {
        abiFilters **ABIFILTERS**
    }
    versionCode **VERSIONCODE**
    versionName '**VERSIONNAME**'
    consumerProguardFiles 'proguard-unity.txt'**USER_PROGUARD**
}

lintOptions {
    abortOnError false
}

**sourceSets** {
    **main** {
        res.srcDirs += 'C:\\Working\\game\\dumpy\\Assets\\Plugins\\Android\\Firebase\\res\\values\\googleservices.xml'

    }
}

aaptOptions {
    noCompress = ['.unity3d', '.ress', '.resource', '.obb', 'google-services.json']
    ignoreAssetsPattern = "!.svn:!.git:!.ds_store:!*.scc:.*:!CVS:!thumbs.db:!picasa.ini:!*~"
}**PACKAGING_OPTIONS**

}REPOSITORIES****SOURCE_BUILD_SETUP
EXTERNAL_SOURCES

@tkminh I see, so the point is, we must do everything to add \res\ folder back into sourceSets with gradle
But I wonder why we never need to do that and unity will always build correctly. it seem this 2020 change was affect too many things

@tkminh
I added the script but it doesn't work for me.

@Thaina right, we must do that, maybe Unity ignore that file when building to APK. Hope they will fix it in some early release.
@srkoga can you try to copy the xml in Assets\Plugins\Android\Firebase\res\values\googleservices.xml to the correct file google-services.xml
then try again.

As I said before, the problem is in the generate_xml_from_google_services_json exe and py files.
I made a new project, installed firebase sdk 6.13.0. I put google-services.json in the Assets folder. I created the apk and ran it, and it didn't work.
I downloaded another version of sdk 6.8.0 and replaced only those files, without changing maintemplate or any other file. I created the apk and ran it ... it worked on the first try. :)
And when opening the Firebase menu in unity, no error appears.
I will continue my project this way because I already lost more than a week with this error.
unity 2019.3.7f1 + sdk 6.13.0 + with sdk files 6.8.0 = :)
Thank you all for your help.


Update in-code docs for TikiPlatformChannel.swift

The TikiPlaformChannel defines how the iOS SDK communicates with Dart SDK through Flutter. Its docs needs:

[ ] improved class-level docs with a detailed explanation about the Platform Channel
[ ] more details on the methods docs and examples of how they are used

just public classes will be documented


ARROW-17480 [Java] add setNull() to FieldVector interface

Implemented setNull for vector types where it was not supported (including the abstract ExtensionTypeVector class), and added it to the FieldVector interface.
The change makes it possible to call setNull() on arbitrary field vectors without casting.

@davisusanibar or @lidavidm could one or both of you take a look. The changes are small and simple.


Issue with Glimpse badly interoperating with EF.BulkInsert

I have an EF6 / ASP.NET 4.5 Webforms solution up and running, and now I need to add some functionality to allow bulk inserts from Excel files.
I am aware that EF out of the box isn't optimized for bulk operations, so I looked around and found "EF BulkInsert" (https://efbulkinsert.codeplex.com/) to facilitate just this.
I tried it in a test app, and it worked wonderfully - but when I included it in my actual main app, it broke down. When trying to do the actual bulk insert call, the system crashes with an exception:

BulkInsertProviderNotFoundException: BulkInsertProvider not found for 'Glimpse.Ado.AlternateType.GlimpseDbConnection. To register new provider use EntityFramework.BulkInsert.ProviderFactory.Register() method'

Now I'm unsure if this is the fault of Glimpse or EF BulkInsert (or both), and unfortunately, but I was unable to find a solution so far.

Same issue here.   Wondering if you were able to find any suitable solution  ??

Issue #795 was closed due being unable to reproduce, but the problem is actually very easy to reproduce. Please fix it!


Reproduces without extensions: Yes/No

File > New Untitled File


Write Readme

[ ] Links to ROS2
[ ] Links to RT Pendulum Demo
[ ] Goal
[ ] Screenshots
[ ] ?

I can take on the initial writing of the README, i.e., the basics for all the topics mentioned above. and we can improve upon that based on guidance from @guilyx

@sampreets3 don't forget one issue one PR ahah


Review Indexes

Some FreeCEN fields are not indexed (e.g. Birth County Chapman Code).  The missing indexes need to be identified and implemented.
E 1, U 6, S 7, C?: P

As a start it would appear that a large number of searches include a birth_county which is unindexed. Most of those do not include a census_county which is indexed. Is that because of the form layout?
The SSD is not used in CEN so is not required as a search index element
a) The first step is to write a rake task to determine the actual search parameters used
b) Secondly modify the search performance statistics to display the search parameters for Cen
c) Thirdly modify the site statistics to list the Cen records.

Purely from my own usage ... I am guessing that if the tree has been built from BMD and REG info, the birth county is known, but and maybe marriage (giving a married surname) but 'current location' decades later is unknown.  With rarer surnames, and a known/approximate birth date, searching without limiting by census county reduces the results to a manageable.  I wonder if we can get the json files from FreeCEN1, to see what happens there?  [if we can analyse them].

@Captainkirkdawson please change priority I have given if I've got it wrong, and estimate size.  TY, Pat

This is an Epic. The first cut has been done. Will review after completion of the 3 tasks identified

Based on the statistics of usage where 50% of searches include only a birth_county the fact that we include indexes only for census counties must have a significant impact. We should replicate the indexes used for census county with birth county and adjust the hinting accordingly. Once that is done we should consider a dual chapman birth_chapman set of indices.
While doing so we should eliminate the secondary date field of the index as CEN does not use that field.

Indexes designed and created for CSVProc


Verify that the if i=='final' logic still works when downloading a form on the final page

It looks like this is not working correctly in the wizard-generated code on 2/12. Need to investigate this.

[ ] Works in a markdown template
[ ] Works in a PDF
[ ] Works in a Docx

Trying again on 2/17 and it looks like it works. Could have been a false alarm or a corrupted PDF


Added warning to disclaimer

Description of the change
This changes adds a warning to the Disclaimer as it gets easily missed
Existing or Associated Issue(s)
N/A
Additional Information
We often have Adopters with issues on Discord as they are trying to do things with the default image that just are not possible. They often don't read this Disclaimer. Once we point that out and help explain how to properly get started they are able to head in the right direction. This is not a perfect solution but it may help some.
Checklist

[ ] Chart version bumped in Chart.yaml according to semver.
[ ] Variables are documented in the values.yaml and added to the README.md. The helm-docs utility can be used to generate the necessary content. Use helm-docs --dry-run to preview the content.
[ ] JSON Schema generated.
[ ] List tests pass for Chart using the Chart Testing tool and the ct lint command.

lgtm

Yeah, noticed those but I'm not sure how to resolve them, might be that the file I changed doesn't like the GitHub Markdown syntax 🤔

Gave this some thought and I don't really think this is going to help and isn't a good solutions, I'm going to close this PR and think of a better approach. Sorry for any wasted time on this.


Error if I use sarama as 'gopkg.in/Shopify/sarama.v1'

The code files in bsm/sarama-cluster are based on sarama and they import github.com/Shopify/sarama.
So if I want to use both producer and consumer in my project, and I'd like to use Sarama-cluster to build the consumer, I have to import both Sarama and Sarama-cluster.
If I import Sarama like: 'sarama "gopkg.in/Shopify/sarama.v1" ', and import Sarama-cluster, there would be some type assignment error like:
cannot use "gopkg.in/Shopify/sarama.v1".CompressionSnappy (type "gopkg.in/Shopify/sarama.v1".CompressionCodec) as type "vendor/github.com/Shopify/sarama".CompressionCodec in assignment
That's because sarama-cluster import github.com/Shopify/sarama but not gopkg.in/Shopify/sarama.v1
How can I use sarama-cluster while use sarama with gopkg.in/Shopify/sarama.v1?
Thank you very much!

The use of gopkg.in is deprecated since vendoring was introduced (for the exact same reason you mentioned above). Especially with the release of https://github.com/golang/dep it will become obsolete. That said, you could vendor both, saramaV1 "gopkg.in/Shopify/sarama.v1" and sarama "github.com/Shopify/sarama" and use them in your package side-by-side


[Mapping]  FAIL - The entity-class mapping is invalid: #translatable refers to the inverse side field #translations which does not exist.

Hello, when running php index.php orm:validate im encountering warnings like this:
[Mapping]  FAIL - The entity-class 'Directa\Application\InputTranslation' mapping is invalid:
* The association Directa\Application\InputTranslation#translatable refers to the inverse side field Directa\Application\Input#translations which does not exist.

Input.php:
<?php

namespace Directa\Application;

use Doctrine\Common\Collections\ArrayCollection;
use Doctrine\ORM\Mapping as ORM;
use Directa\Doctrine\Attributes\Identifier;
use Kdyby\Doctrine\Collections\ReadOnlyCollectionWrapper;
use Knp\DoctrineBehaviors\Model\Timestampable\Timestampable;
use Knp\DoctrineBehaviors\Model\Translatable\Translatable;
use Nette\SmartObject;

/**
 * @ORM\Entity
 */
class Input
{
	use Identifier;
	use Timestampable;
	use Translatable;
	use SmartObject;

	/**
	 * @ORM\Column(type="string", nullable=TRUE, unique=true)
	 * @var string
	 */
	private $name;

	/**
	 * @ORM\Column(type="integer", nullable=TRUE)
	 * @var integer
	 */
	private $position;

	/**
	 * @ORM\OneToMany(targetEntity="InputOption", mappedBy="input", cascade={"persist", "remove"})
	 * @var InputOption|ArrayCollection
	 */
	private $options;

    // getters, setters, logic ...
}

InputTranslation.php:
<?php

namespace Directa\Application;

use Doctrine\ORM\Mapping as ORM;
use Knp\DoctrineBehaviors\Model\Timestampable\Timestampable;
use Knp\DoctrineBehaviors\Model\Translatable\Translation;
use Nette\SmartObject;

/**
 * @ORM\Entity
 */
class InputTranslation
{
	use Translation;
	use Timestampable;
	use SmartObject;

	/**
	 * @ORM\Column(type="string", nullable=TRUE)
	 * @var string
	 */
	private $label;

	/**
	 * @ORM\Column(type="string", nullable=TRUE)
	 * @var string
	 */
	private $description;

	/**
	 * @ORM\Column(type="boolean", nullable=TRUE)
	 * @var boolean
	 */
	private $enabled;

	/**
	 * @ORM\Column(type="boolean", nullable=TRUE)
	 * @var boolean
	 */
	private $required;

    // getters, setters, logic ...
}

This is quite strange, because i normally use $translatable->getTranslations() in code (trait is used properly).
Any hints how to suppress/solve these warnings?
If that helps you, here is my composer.json:
{
	"repositories": [
		{
			"type": "vcs",
			"url": "https://github.com/Lexinek/Translation"
		}
	],
	"require": {
		"nette/application": "^2.4",
		"nette/bootstrap": "^2.4",
		"nette/caching": "^2.5",
		"nette/component-model": "^2.3",
		"nette/di": "^2.4",
		"nette/finder": "^2.4",
		"nette/forms": "^2.4",
		"nette/http": "^2.4",
		"nette/mail": "^2.4",
		"nette/neon": "^2.4",
		"nette/robot-loader": "^2.4",
		"nette/security": "^2.4",
		"nette/utils": "^2.4",
		"latte/latte": "^2.4",
		"tracy/tracy": "^2.4",
		"janmarek/WebLoader": "@dev",
		"joseki/webloader-filters": "1.1.*",
		"oyejorge/less.php": "1.7.0.*",
		"twbs/bootstrap": "3.3.*",
		"kdyby/doctrine": "3.1.*",
		"kdyby/events": "3.0.*",
		"kdyby/translation": "@dev",
		"zenify/doctrine-behaviors": "2.5.*",
		"ramsey/uuid-doctrine": "^1.2",
		"zenify/doctrine-migrations": "^2.3",
		"fortawesome/font-awesome": "^4.6"
	}
}

My guess is that TranslatableSubscriber is not working correctly. No idea why though. First I would investigate the compiled DI container if the subscriber is there and is connected to the right events. If that's ok then debug TranslatableSubscriber::loadClassMetadata().

@enumag thank you for hint. i have set break points inside of loadClassMetadata event in TranslatableSubscriber and found out that $this->isTranslatable($classMetadata) is ALWAYS returning false, i will go further and edit this comment when i find out more.

Ok, i have found out what is wrong, probably im just stupid :-)
I am not using Zenify trait (i dont need that functionality), but using Knp translatable trait only.
Solution is change translatableTrait option in extension config.
Anyways i think that Knp trait could be used as default value for that config option - all functionallity is contained in it, Zenify translatable trait is only sugar.

Thanks for reporting where the problem was. I'm glad that you solved it. :-)
I would like to avoid BC breaks like that if possible. Maybe if there are other people than you with the same opinion. I agree with you but since I don't use this library my opinion doesn't matter much.


How to solve the problem of slow Commissioning process？

In the process of production, we found that when we carried out application testing (add the device to Apple home app-> Test onoff and level control -> Remove the device), we found that it took about 5 minutes to successfully add the device to Apple home app each time. What's the reason, I wonder? Or is there anything that can optimize the speed of the distribution network? It is worth mentioning that our speed will not be so slow at the beginning, but when more and more devices are added, you can obviously feel the speed is getting slower and slower.
I was wondering what else could be done to make things faster in terms of production testing? Because so far we've only tested on Apple home, we haven't tried any other ecosystem
we use Nordic52840 and the matter certification version is 1.0.
The following is my network log, can you help me see where the response is slow?
Commissioning log.txt

So looking at that log, the device starts advertising over BLE here:
00> I: 30270 [DL]Chuck:CHIPoBLE advertising started

The BLE connection is established 17 seconds later (assuming those are millisecond timestamps):
00> I: 47306 [DL]BLE connection established (ConnId: 0x00)

Then commissioning starts here:
00> I: 49201 [EM]>>> [E:36424r M:249843416] (U) Msg RX from 0:10EABFD526874AF4 [0000] --- Type 0000:20 (SecureChannel:PBKDFParamRequest)

and completes pretty quickly:
00> I: 60088 [FS]GeneralCommissioning: Received CommissioningComplete

Then there is a second commissioning (one for keychain, one for Home), which completes here:
00> I: 66459 [FS]GeneralCommissioning: Received CommissioningComplete

Then the device hears nothing from the other site for a while until:
00> I: 162148 [EM]>>> [E:36467r M:120959253] (S) Msg RX from 1:00000000457B8B14 [E86A] --- Type 0001:02 (IM:ReadRequest)

Then the other side tries to subscribe to the device:
00> I: 165060 [EM]>>> [E:77r M:77935753] (S) Msg RX from 1:00000000457B8B14 [E86A] --- Type 0001:03 (IM:SubscribeRequest)

and the priming data gets sent, about one packet per 100ms:
00> I: 165620 [EM]<<< [E:77r M:23793268 (Ack:77935764)] (S) Msg TX to 1:00000000457B8B14 [E86A] --- Type 0001:05 (IM:ReportData)
00> I: 165731 [EM]>>> [E:77r M:77935765 (Ack:23793268)] (S) Msg RX from 1:00000000457B8B14 [E86A] --- Type 0001:01 (IM:StatusResponse)
00> I: 165742 [EM]<<< [E:77r M:23793269 (Ack:77935765)] (S) Msg TX to 1:00000000457B8B14 [E86A] --- Type 0001:05 (IM:ReportData)
00> I: 165860 [EM]>>> [E:77r M:77935766 (Ack:23793269)] (S) Msg RX from 1:00000000457B8B14 [E86A] --- Type 0001:01 (IM:StatusResponse)
...etc

This continues until:
00> I: 167645 [EM]<<< [E:77r M:23793286 (Ack:77935782)] (S) Msg TX to 1:00000000457B8B14 [E86A] --- Type 0001:04 (IM:SubscribeResponse)

By this point:
00> I: 191064 [EM]>>> [E:87r M:77935795] (S) Msg RX from 1:00000000457B8B14 [E86A] --- Type 0001:08 (IM:InvokeCommandRequest)

the other side is sending lighting "on" commands to the device.
So it's taking 30s to start advertising over BLE, another 17s to establish the BLE connection, then 20s to do the commissioning, then for close to 100s the client goes off an does ... something.  Then subscription takes about 2s, and I would expect the device to be considered "added" at or before that point, at about the 3 minute mark.

In terms of why there's that 100s gap: I recommend filing a feedback assistant ticket per the directions below, which would include logs from the Apple device in question that would perhaps allow that to be pinned down.  Please mention the ticket ID in this issue, and I will see about getting someone to look at it.
Feedback assistant ticket:

File a feedback assistant ticket.
https://developer.apple.com/bug-reporting/#feedback-assistant
Click on the link below using your account:
https://feedbackassistant.apple.com/new-form-response
Choose iOS/iPadOS to file an issue
Choose the area as Home App and fill in the details of the type of issue and the description

Technical Information
Please provide the following
a) Sysdiagnose logs for iPhone / iPad with the timestamp / timeframe of the issue
b) Sysdiagnose logs for all the Home Hubs (HomePod mini / HomePod / Apple TV) with the timestamp / timeframe of the issue
c) Accessory logs with the timestamp / timeframe of the issue
d) mDNS network logs with timestamp / timeframe of the issue
e) Video or screenshot describing the issue (optional but beneficial)
Please make sure you download and install the profiles for iOS and tvOS as provided here. The instructions are also in these links.
iOS:

https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios&name=homekit
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios&name=network
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=ios&name=mdns

tvOS:

https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=tvos&name=homekit
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=tvos&name=network
https://developer.apple.com/bug-reporting/profiles-and-logs/?platform=tvos&name=mdns
For installation instructions, refer to https://developer.apple.com/bug-reporting/profiles-and-logs.
Note: Once you have the profile on the iPhone, it will ask you if you want to install it on other devices. Follow the prompts to install on the HomePod, Apple TV, etc., where you have the described issue and reproduce it.


Should Daily Notes core plug-in be disabled?

Sorry for asking a dumb question, but after a bit of research I'm still not clear on whether the user is expected to disable the Daily Notes core plug-in when using obsidian-periodic-notes?

this superseeds the daily notes you should be able to turn it off and switch to using this icon for daily notes.

Thank you @anantshri for the explanation. To be clear, are you saying that other plugins that depend on the core Daily Notes plugin (for example, the Calendar community plugin) are expected to work with no issues when obsidian-periodic-notes is enabled, and the core Daily Notes plugin is disabled?

Yes correct. calendar and periodic notes are replacements of daily notes. periodic note is a direct 1:1 replacement with sidebar icon also.

Understood, thanks again!

Just to be clear, MUST one disable the daily notes, or can one use both concurrently?

You could use both, but it might be confusing (but I can have 2 sets of daily notes), if you define different paths for daily notes I dont know which one will be picked by calendar, et cetera


LXD 3.7 dead and won't start

Required information

Distribution: Centos
Distribution version: 7.5
The output of "lxc info" or if that fails:

Kernel version:  4.18.7-1.el7.elrepo.x86_64
LXC version:  3.7        9664
LXD version:  3.7        9664
Storage backend in use: zfs

Issue description
After an automated snap update to 3.7, LXD fails to start.  Containers are still running.  This was noticed when a routine "lxc list" failed.
Steps to reproduce
I have 5 LXD based production systems.  All updated to 3.7 but only 1 did so successfully.  Three have running containers without LXD and one seems to have lost all containers.
Information to attach
/var/lib/snapd/snap/bin/lxd --debug
DBUG[11-28|23:34:30] Connecting to a local LXD over a Unix socket
DBUG[11-28|23:34:30] Sending request to LXD                   method=GET url=http://unix.socket/1.0 etag=
INFO[11-28|23:34:30] LXD 3.7 is starting in normal mode       path=/var/snap/lxd/common/lxd
INFO[11-28|23:34:30] Kernel uid/gid map:
INFO[11-28|23:34:30]  - u 0 0<PHONE_NUMBER>
INFO[11-28|23:34:30]  - g 0 0<PHONE_NUMBER>
INFO[11-28|23:34:30] Configured LXD uid/gid map:
INFO[11-28|23:34:30]  - u 0 1000000<PHONE_NUMBER>
INFO[11-28|23:34:30]  - g 0 1000000<PHONE_NUMBER>
WARN[11-28|23:34:30] AppArmor support has been disabled because of lack of kernel support
INFO[11-28|23:34:30] Kernel features:
INFO[11-28|23:34:30]  - netnsid-based network retrieval: no
INFO[11-28|23:34:30]  - uevent injection: yes
INFO[11-28|23:34:30]  - unprivileged file capabilities: no
INFO[11-28|23:34:30] Initializing local database
DBUG[11-28|23:34:30] Initializing database gateway
DBUG[11-28|23:34:30] Start database node                      address= id=1
DBUG[11-28|23:34:30] Raft: Restored from snapshot 1-6529-1542258162322
DBUG[11-28|23:34:31] Raft: Initial configuration (index=1): [{Suffrage:Voter ID:1 Address:0}]
DBUG[11-28|23:34:31] Raft: Node at 0 [Leader] entering Leader state
DBUG[11-28|23:34:31] Dqlite: starting event loop
DBUG[11-28|23:34:31] Dqlite: accepting connections
DBUG[11-28|23:34:31] Connecting to a local LXD over a Unix socket
DBUG[11-28|23:34:31] Sending request to LXD                   method=GET url=http://unix.socket/1.0 etag=
DBUG[11-28|23:34:31] Detected stale unix socket, deleting
INFO[11-28|23:34:31] Starting /dev/lxd handler:
INFO[11-28|23:34:31]  - binding devlxd socket                 socket=/var/snap/lxd/common/lxd/devlxd/sock
INFO[11-28|23:34:31] REST API daemon:
INFO[11-28|23:34:31]  - binding Unix socket                   socket=/var/snap/lxd/common/lxd/unix.socket
INFO[11-28|23:34:31]  - binding TCP socket                    socket=[::]:8443
INFO[11-28|23:34:31] Initializing global database
DBUG[11-28|23:34:31] Dqlite: handling new connection (fd=20)
DBUG[11-28|23:34:31] Dqlite: connected address=0 attempt=0
INFO[11-28|23:34:31] Updating the LXD global schema. Backup made as "global.bak"
DBUG[11-28|23:34:31] Updating global DB schema from 9 to 10
DBUG[11-28|23:34:31] Updating global DB schema from 10 to 11
DBUG[11-28|23:34:31] Updating global DB schema from 11 to 12
DBUG[11-28|23:34:31] Database error: &errors.errorString{s:"failed to apply update 11: Failed to add project_id column: unable to open database file"}
EROR[11-28|23:34:31] Failed to start the daemon: failed to open cluster database: failed to ensure schema: failed to apply update 11: Failed to add project_id column: unable to open database file
INFO[11-28|23:34:31] Starting shutdown sequence
INFO[11-28|23:34:31] Stopping REST API handler:
INFO[11-28|23:34:31]  - closing socket                        socket=[::]:8443
INFO[11-28|23:34:31]  - closing socket                        socket=/var/snap/lxd/common/lxd/unix.socket
INFO[11-28|23:34:31] Stopping /dev/lxd handler:
INFO[11-28|23:34:31]  - closing socket                        socket=/var/snap/lxd/common/lxd/devlxd/sock
DBUG[11-28|23:34:31] Stop database gateway
DBUG[11-28|23:34:31] Stop raft instance
DBUG[11-28|23:34:31] Dqlite: stopping event loop
EROR[11-28|23:34:31] Dqlite: aborting (fd=20 state=header msg=(null))
DBUG[11-28|23:34:31] Dqlite: event loop stopped
DBUG[11-28|23:34:31] Not unmounting temporary filesystems (containers are still running)
INFO[11-28|23:34:31] Saving simplestreams cache
INFO[11-28|23:34:31] Saved simplestreams cache
Error: failed to open cluster database: failed to ensure schema: failed to apply update 11: Failed to add project_id column: unable to open database file
Any help would be appreciated.  These are production systems and I believe I already lost the containers on one.  I'd like to reduce the damage by trying to restore the other three servers.

The log above suggests you're updating from LXD 3.4 to 3.7, is that what you're doing here or is there something else going on that would have caused your database to go back to that older version?

That is possible.  We were running 3.4 for sometime.

Ok, so I suspect it's the database hitting some kind of timeout when processing so many schema updates in a row. We've seen some cases of this here and there and have made changes that should have prevented this issue, but clearly there's still something going on.
On one of the affected systems, please do (as root):

systemctl stop snap.lxd.daemon snap.lxd.daemon.unix.socket &
pkill -9 -f lxd.*logf
lxd --debug --group lxd

And post the output here.

lxd --debug --group lxd
INFO[11-28|23:50:55] LXD 3.7 is starting in normal mode       path=/var/snap/lxd/common/lxd
INFO[11-28|23:50:55] Kernel uid/gid map:
INFO[11-28|23:50:55]  - u 0 0<PHONE_NUMBER>
INFO[11-28|23:50:55]  - g 0 0<PHONE_NUMBER>
INFO[11-28|23:50:55] Configured LXD uid/gid map:
INFO[11-28|23:50:55]  - u 0 1000000<PHONE_NUMBER>
INFO[11-28|23:50:55]  - g 0 1000000<PHONE_NUMBER>
WARN[11-28|23:50:55] AppArmor support has been disabled because of lack of kernel support
INFO[11-28|23:50:55] Kernel features:
INFO[11-28|23:50:55]  - netnsid-based network retrieval: no
INFO[11-28|23:50:55]  - uevent injection: yes
INFO[11-28|23:50:55]  - unprivileged file capabilities: no
INFO[11-28|23:50:55] Initializing local database
DBUG[11-28|23:50:55] Initializing database gateway
DBUG[11-28|23:50:55] Start database node                      id=1 address=
DBUG[11-28|23:50:55] Raft: Restored from snapshot 1-6529-1542258162322
DBUG[11-28|23:50:55] Raft: Initial configuration (index=1): [{Suffrage:Voter ID:1 Address:0}]
DBUG[11-28|23:50:55] Raft: Node at 0 [Leader] entering Leader state
DBUG[11-28|23:50:55] Dqlite: starting event loop
DBUG[11-28|23:50:55] Dqlite: accepting connections
INFO[11-28|23:50:55] Starting /dev/lxd handler:
INFO[11-28|23:50:55]  - binding devlxd socket                 socket=/var/snap/lxd/common/lxd/devlxd/sock
INFO[11-28|23:50:55] REST API daemon:
INFO[11-28|23:50:55]  - binding Unix socket                   socket=/var/snap/lxd/common/lxd/unix.socket
INFO[11-28|23:50:55]  - binding TCP socket                    socket=[::]:8443
INFO[11-28|23:50:55] Initializing global database
DBUG[11-28|23:50:55] Dqlite: handling new connection (fd=20)
DBUG[11-28|23:50:55] Dqlite: connected address=0 attempt=0
INFO[11-28|23:50:55] Updating the LXD global schema. Backup made as "global.bak"
DBUG[11-28|23:50:55] Updating global DB schema from 9 to 10
DBUG[11-28|23:50:55] Updating global DB schema from 10 to 11
DBUG[11-28|23:50:55] Updating global DB schema from 11 to 12
DBUG[11-28|23:50:55] Database error: &errors.errorString{s:"failed to apply update 11: Failed to add project_id column: unable to open d                                            atabase file"}
EROR[11-28|23:50:55] Failed to start the daemon: failed to open cluster database: failed to ensure schema: failed to apply update 11: Fa                                            iled to add project_id column: unable to open database file
INFO[11-28|23:50:55] Starting shutdown sequence
INFO[11-28|23:50:55] Stopping REST API handler:
INFO[11-28|23:50:55]  - closing socket                        socket=[::]:8443
INFO[11-28|23:50:55]  - closing socket                        socket=/var/snap/lxd/common/lxd/unix.socket
INFO[11-28|23:50:55] Stopping /dev/lxd handler:
INFO[11-28|23:50:55]  - closing socket                        socket=/var/snap/lxd/common/lxd/devlxd/sock
DBUG[11-28|23:50:55] Stop database gateway
DBUG[11-28|23:50:55] Stop raft instance
DBUG[11-28|23:50:55] Dqlite: stopping event loop
EROR[11-28|23:50:55] Dqlite: aborting (fd=20 state=header msg=(null))
DBUG[11-28|23:50:55] Dqlite: event loop stopped
DBUG[11-28|23:50:55] Not unmounting temporary filesystems (containers are still running)
INFO[11-28|23:50:55] Saving simplestreams cache
INFO[11-28|23:50:55] Saved simplestreams cache
Error: failed to open cluster database: failed to ensure schema: failed to apply update 11: Failed to add project_id column: unable to open database file

Well, that's not helping very much and it also excludes the idea that this is timeout related since the whole thing happens in a second...
Can you make a tarball of /var/snap/lxd/common/lxd/database and send that to<EMAIL_ADDRESS>That should let me replicate the issue here and track down what's going on with this update, hopefully I can then send you a patched up database until the fix for whatever's going on hits the snap.

Certainly. Thank you.

So the issue here appeared to be unrelated to LXD but instead be something very odd going on with the snap's mount namespace apparently showing different mounts than the host, leading to those confusing errors above showing a database update on a system which should have otherwise been up to date.
The short version of the "fix" was to force snapd to create a new namespace with:

umount -l /var/snap/lxd/common/ns/shmounts
umount -l /var/snap/lxd/common/ns
umount -l /run/snapd/ns/lxd.mnt
rm /run/snapd/ns/lxd.mnt

I suspect this is something funny going on with this particular mix of recent kernel on Centos 7 with snapd as we'd otherwise have seen many more reports of this, but if someone else runs into this, it'd be useful to get the output of:

nsenter --mount=/run/snapd/ns/lxd.mnt cat /proc/self/mountinfo
cat /proc/self/mountinfo

Prior to running the commands above. This may show us exactly what happened to that namespace.


Support drag and drop of IIIF resources into empty slot

As a user, if I find a IIIF resource in my discovery system, I want to be able to drag a thumb of that resource to an empty mirador slot such that it allows me to view the object in that slot, and the object is made available to me in the Mirador load window.

@mikeapp

See: http://zimeon.github.io/iiif-dragndrop/
#656, #655


Getting Started With Web Parts

NPM Errors

[x] Question

I am a newbie here, so I hope I'm putting this in the right spot and that you guys take it easy on me! I'm brand-new to the site and using a web part from the site. I got started by doing the Microsoft tutorial creating the Hello Webpart. It worked fine. I then downloaded some files for another webpart that I wanted to do. I got an error message. I went through and tried to delete things that I had installed. I uninstalled some things through windows power shell and programs through the control panel that are required for setting up your developmental environment.
I went back to square one and started with the Hello Webpart tutorial (reinstalled everything) and I am now getting NPM errors. I would just like to get back to square one with being able to install it without any errors like I did the very first time I went through the process.
Windows 10
SharePoint Online
.NET Framework v 4.8x
Chrome 83
Please see attached text document.

I could not tell if the attachment went through. Here is the text from it:
After I give it the commands to create the hello world web part these errors now show up.
npm WARN deprecated<EMAIL_ADDRESS>gulp-util is deprecated - replace it, following the guidelines at https://medium.com/gulpjs/gulp-util-ca3b1f9f9ac5
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>This module relies on Node.js's internals and will break at some point. Do not use it, and update to<EMAIL_ADDRESS>npm WARN deprecated<EMAIL_ADDRESS>Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
npm WARN deprecated<EMAIL_ADDRESS>use String.prototype.padStart()
npm WARN deprecated<EMAIL_ADDRESS>request has been deprecated, see https://github.com/request/request/issues/3142
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN deprecated<EMAIL_ADDRESS>not actively maintained anymore
npm WARN deprecated<EMAIL_ADDRESS>fsevents 1 will break on node v14+ and could be using insecure binaries. Upgrade to fsevents 2.
npm WARN deprecated<EMAIL_ADDRESS>Legacy versions of mkdirp are no longer supported. Please update to mkdirp 1.x. (Note that the API surface has changed to use Promises in 1.x.)
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to kleur@3 or migrate to 'ansi-colors' if you prefer the old syntax. Visit https://github.com/lukeed/kleur/releases/tag/v3.0.0\ for migration path(s).
npm WARN deprecated<EMAIL_ADDRESS>https://github.com/lydell/resolve-url#deprecated
npm WARN deprecated<EMAIL_ADDRESS>Please see https://github.com/lydell/urix#deprecated
npm WARN deprecated<EMAIL_ADDRESS>This package is broken and no longer maintained. 'mkdirp' itself supports promises now, please switch to that.
npm WARN deprecated<EMAIL_ADDRESS>please upgrade to graceful-fs 4 for compatibility with current and future versions of Node.js
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
Then, right before it tells me it is finished and I can run the gulp serve command these error messages are showing up.
Binary found at C:\helloworld-webpart\node_modules\node-sass\vendor\win32-x64-64\binding.node
Testing binary
Binary is fine
npm notice created a lockfile as package-lock.json. You should commit this file.
npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"<8.10.0"} (current: {"node":"10.20.1","npm":"6.14.4"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\watchpack\node_modules\chokidar\node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ^2 || ^2.1.0-beta || ^2.2.0-rc || ^3.0.0 but none is installed. You must install peer dependencies yourself.

What's the details you want to get from another web part ?
If you want to use some third party api like pnp.js , just use npm to install.
Currently, can you create a new web part using yo @microsoft/sharepoint in your environment ?

There is what I did. I just went through the Microsoft tutorial and created the hello web part. The yeoman generator worked fine.
This is the web part that I am now trying to create: https://tahoeninjas.blog/2018/06/05/creating-a-calendar-feed-web-part-part-ii/. When I get to step three to run the yeoman generator here air message that I get:
PS C:> cd react-calendar-feed-1
PS C:\react-calendar-feed-1> yo @Microsoft/sharepoint
Error @Microsoft/sharepoint
You don't seem to have a generator with the name “@Microsoft/sharepoint” installed.
But help is on the way:
You can see available generators via npm search yeoman-generator or via http://yeoman.io/generators/.
Install them with npm install @Microsoft/generator-sharepoint.
To see all your installed generators run yo without any arguments. Adding the --help option will also show subgenerators.
If yo cannot find the generator, run yo doctor to troubleshoot your system.
PS C:\react-calendar-feed-1>

The command is case sensitive, please modify as below, "m" for microsoft should be lower case:
yo @microsoft/sharepoint


"Remove repository" button in MPS plugin is ineffective

Situation: I have two repositories asdded in my Cloud tool window
What I did:

I remove one of the two repositories: right-click --> Remove Repository
I restart MPS

What happens:

Upon removal, the repository is gone
Upon restart of MPS, the repository has returned again.

I can reproduce this consistently.
Working with MPS 2020.3 under Windows 10.

maybe related to #59

You can verify it is related to #59 by looking at .mps/cloudRepository.xml. If your repository it is there then it is related. This system is a bit complicated by the fact that MPS decides when to actually persist the changes


Update CONTRIBUTE.md to reflect the new version of required tools and github pull request path

I was following CONTRIBUTE.md instructions to setup Debezium locally and it incurred into an error, since JDK 8 is no longer supported. I'm opening this PR to reflect the change.
I've also edited some parts of the GitHub pull request instructions because the path described there is not available anymore, after some Github UI changes.

Thx for this update, really appreciated!


Detect no user from previous service spec

The commons used in universe packages doesn't set the user, and Mesos interprets this as it should set user to root.
Upon an update from release to master, even overriding the default user from "nobody" to "root" doesn't work as the user-change validation fails since the comparison is actually null vs "root".
This fixes that by detecting if the user has been set.
Only the last commit is relevant to this PR as it's currently rebased on @mrbrowning's https://github.com/mesosphere/dcos-commons/pull/1308 to reflect incoming updates

@NimaVaziri you'll probably need to fix this to be based off of master, this includes un-squashed commits from the default executor branch before it was merged.

@mrbrowning Yeah, I'll just rebased off master and force-push after your PR gets merged


Fix linkerd autoscaling metrics match

Looks like the metric is exposed with peer: dest after we wrapper
gateway with linkerd proxy

https://github.com/rancher/rio/issues/479


Sc fix txn query

I fixed these queries as i need them to 'actually' work (rather than just compiling) for the file versioning stuff i'm working on. :) They now have tests too.

@yetti @danielbaker @MingtaoSun @AaronCMuller @JonathanShaw
Would anyone mind having a quick look ?

looks good :+1:

:+1:

:+1:


Using pgb unlock

Hi there, I'm trying to use the unlock method with a CI Gitlab setup.  Unfortunately it always prompts for the keystore password and key passwrod - it seems to delete the env variables that could have possibly been passed in.
Any reason why this is the case?
Thanks

i havent used the gitlab CI. maybe try just echo'ing the env vars to ensure theyre there.

Yeah the env vars are there, maybe I just don't understand how to unlock.
It is getting the error android key xxxxx not found (maybe wrong platform?)
I'm doing
pgb unlock android appid

are you using the “key id”? this error is server side so id is incorrect.

How do I find the key id? I can't seem to find the value anywhere on the interface online

> pgb keys android

Thank you worked like a charm, it is now auto deploying to google play store, thanks for your help!


Many edits to clean up move of recirculate decision to ingress

Changes include:

Eliminate recirculate and resubmit extern objects from psa.p4.
Proposed addition of a new struct that contains only egress_port field, to be given as 'in' parameter to the egress deparser, so it can distinguish between recirculated packets vs. others.  It something like this to implement psa_recirculate() function correctly.  This is one of several ways to do it, but we could choose something else.
Many small changes to PSA.mdk mentioning things about recirculate, and updating them to the current planned way to do it.
A few other small corrections and occurrences of rewording that I hope are improvements in PSA.mdk.

I have also added an appendix with reasoning given for some high level PSA design choices.  I don't think any of that will be surprising to anyone that has looked at high speed switching devices before -- it is there primarily for those who might be new to these things.


Disable prettier from changing file formatting

We want to disable prettier in the codebase as it usually interferes with the formatting and linting rules of the codebase. To prevent unnecessary format changes it would be best to disable prettier for anyone who might have it installed so it doesn't take precedence over the linting of the codebase.
Requirements

[ ] Create a prettierignore  file that disables prettier in all files to ignore semicolons being added or reformatting of files by all contributors who use prettier, so as to not have to go back and reformat files in a PR or file.

Dependencies

None

pro tip for writing issues, start with the problem statement first before listing out the requirements.
why do we want to disable prettier?

Updated! I hope that is clearer

Updated! I hope that is clearer

Stellar ⭐


Retry in procedure should use the latest route table

What type of enhancement is this?
Other
What does the enhancement do?
Currently the procedure will take a "snapshot" of the route table for the entire lifecycle. Once region failover occurs during a procedure, it will keep retrying on the outdated node. This can be improved by refreshing the region id -> node id part on each retry
Implementation challenges
No response

@MichaelScofield Please take a look at this issue.


Show slider component on landing page.

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #1590
Description

Show slider component on landing page.
Change existing question to How many children does client have and max count to 15.

Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
Type
Choose one: Bug fix
Screenshots (if applicable)
Checklist

[x] I have read and acknowledged the Code of conduct.
[x] I have read the Contributing page.
[x] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
[x] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
[x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
[x] I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

@shelaghm


Project paths added to an open project are lost after closing and reopening the project

ISSUE
Root folders added to an open project, either using the update project dialog or project manager's "Add Project Folder" action, are lost after closing and re-opening the project.
Environment

OS: macOS 10.12.1;
Atom: 1.12.2;

Steps

right click on an existing project
click "update"
click "Add root paths:"
select a folder not already in the project
observe: new path appears in project
close the project
open the project
observe: the added path is no longer in the project

I am able to add root paths if I close the project, add the path(s), and then re-open the project

hey @GreenGremlin,
Thanks for reporting this. Will investigate this!

@GreenGremlin can you please validate this?

How do I install the fix?

you just need to update the package, Atom notifies you of outdated packages

Ah, didn't realize you had pushed a release out. Yes, it is fixed for me, thank you!


UI favicon and title of login page editable via config.json

ISSUE TYPE

Improvement Request

COMPONENT NAME

UI

CLOUDSTACK VERSION

<IP_ADDRESS>

SUMMARY

I would be nice to be able to change favicon of the UI and the title of the login page via config.json.
You are unable to change the favicon via config.json. It looks hard coded and points to cloud.ico.
You can edit the titles of the UI after login via appTitle, but this will not change the title of the login page. It looks like it is hard coded in index.html.

Please assign me this issue

go ahead @abhinavs1920, but please let us know if you abandon it.

Hi @DaanHoogland, is this issue still open? I am interested in working on this issue, and have created a PR for this as well.

Hi @DaanHoogland,
have created a PR - https://github.com/apache/cloudstack/pull/7418

I think Harshit has solved the issue already.

PR has been merged https://github.com/apache/cloudstack/pull/7418 closing this


openpomodoro-cli: init at 0.3.0

Description of changes
Add openmodoro-cli
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

The package should be located at pkgs/by-name/op/openpomodoro-cli/packages.nix.

Thanks for the feedback, I have done it!

@fabaff it works too!

Result of nixpkgs-review pr 305515 run on x86_64-linux 1

1 package built:

openpomodoro-cli

Could you please squash the commits? Thanks

done! thanks for your support.


Promote StrictlyPositiveInt's deprecations

Description
Promote deprecations declared in io.github.kotools.types.int.StrictlyPositiveInt.
Checklist

[ ] Implement.
[ ] Test.
[ ] Refactor.
[ ] Update Work in progress section in changelog.

Fixed by #45.


[camera] Remove a potential deadlock on Android

Here is the scenario fixed by this PR:

Open the camera in a Flutter app
Move this app to the background (= no dispose method called)
Open a third-party app requiring the camera

In that case, the native Android code will call onDisconnected from CameraDevice.StateCallback.
In this call, the close() method is launched but never ends because stopBackgroundThread is blocked in the join() method.
To prevent this, I have simply added a timeout.
2500 milliseconds is totally arbitrary. I can change it.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/plugins repo does use dart format.)
[ ] I signed the CLA.
[ ] The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
[ ] I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making, or this PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Thanks for the submission!
In the future, please do not delete the checklist that is in the PR template; it is there for a reason. This PR is missing required elements described in the checklist (I’ve restored it to the PR description), which need to be addressed before it moves forward with review.
I am marking the PR as a Draft. Please review the checklist, updating the PR as appropriate, and when that’s complete please feel free to mark the PR as ready for review.

Since this is marked as a draft and hasn't been updated in several months I'm going to close it to clean out our review queue. Please don't hesitate to submit a new PR if you decide to revisit this. Thanks!


Parameter description Typo

The description of the  -AGName param states "are being added", it should be "are being removed"

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

ID: 91e233cd-fcb2-61f7-497f-892750b8d911
Version Independent ID: 4d8addc0-298a-e79d-6f20-c93dd7e4c1b6
Content: Remove-DatabaseFromAvailabilityGroup (sharepoint-server)
Content Source: sharepoint/sharepoint-ps/sharepoint-server/Remove-DatabaseFromAvailabilityGroup.md
Service: unspecified
GitHub Login: @techwriter40
Microsoft Alias: kirks

Submitted #757 for this.

@bentoncity  Steve, who on the SQL Team can you ask about this parameter?

@DeanGross Thank you for this feedback
It looks like there was a merge request put in by Trevor that got approved and merged already so it looks like this is resolved. I am going to close this issue if this issue is not resolved please reopen the issue.


Generation of docs fails on windows network share because of different paths

Hey!
I just came across an issue with the following environment:
I'm on Windows 10 and my python files are placed on a network volume (R:). Im calling lazydocs as an external tool from PyCharm. Therefore the path given to lazydocs starts with the drive letter. This all works fine until I initialise git. After this the docs creation fails. I think, the the reason are those lines:
https://github.com/ml-tooling/lazydocs/blob/f19810ef020684abc7cac8e705ca1258478cdcbb/src/lazydocs/generation.py#L927
The git command returns the path as UNC.
https://github.com/ml-tooling/lazydocs/blob/f19810ef020684abc7cac8e705ca1258478cdcbb/src/lazydocs/generation.py#L512
os.path.relpath(path, src_root_path) tries to combine the path with a drive letter with the unc path which does not work.
Maybe the src_root_path could also be set via the cli? In that case the git command wouldn't run and the path would always start with the drive letter.
Thanks,
Claus

Any ideas about this issue? :)


PRIDE returns empty lists

If you try loading the pride dataset no peptides show up, the ebi server returns an empty list for some reason.
I checked the API documentation, and it has not changed,
https://www.ebi.ac.uk/pride/ws/archive/#!/peptide/getPsmsByAssay
I assume this is a temporary problem on their part. The issue is to remind ourselves about the problem.

Request URL
https://www.ebi.ac.uk:443/pride/ws/archive/peptide/list/assay/8500?show=1&page=0
Response Body
{
  "list": []
}

Response Code
200

Response Headers
    {
      "Access-Control-Allow-Headers": "x-requested-with,Content-Type",
      "Access-Control-Allow-Methods": "GET, OPTIONS",
      "Access-Control-Allow-Origin": "*",
      "Access-Control-Max-Age": "3600",
      "Content-Type": "application/json",
      "Date": "Thu, 08 Mar 2018 18:58:16 GMT",
      "Server": "Apache-Coyote/1.1",
      "Strict-Transport-Security": "max-age=0",
      "Transfer-Encoding": "chunked",
      "X-Clacks-Overhead": "GNU Terry Pratchett"
    }

Original issue by @beardhatcode on Thu Mar 08 2018 at 20:01.
Closed by @beardhatcode on Mon Mar 26 2018 at 15:42.

seems to be resolved
Original comment by @beardhatcode on Mon Mar 26 2018 at 15:42.


version2

Completely re-did the pcb layout.

larger size (210x38mm)
flippable design
fixed sadness w. silkscreen
improved silkscreen
better routing
holes for a trrs soldering jig

Order placed today.


Bump up Gradle version to 2.13.

Summary
Bump up Gradle version to 2.13, for building Asakusa Gradle plugins and Asakusa applications.
Background, Problem or Goal of the patch
N/A.
Design of the fix, or a new feature
see https://docs.gradle.org/2.13/release-notes
Related Issue, Pull Request or Code
N/A.
Wanted reviewer
@akirakw

BUILD SUCCESS.


storybook is broken

the demo storybook http://airbnb.io/react-dates seems to be resolving to a 404 page

Thanks; the gh-pages branch was accidentally deleted by a contributor, and altho i restored it, it seems like it hasn’t redeployed.
I believe whichever of @lencioni @majapw @backwardok @nkinser has admin access will have to fix the gh-pages settings to ensure its redeployed properly.

Thanks for flagging! It should be working again now.


Got error when running "Use 'mock' flag to tell package rest that you would like to use mockups."

The Code:
package rest

import (
	"github.com/mercadolibre/golang-restclient/rest"
	"github.com/stretchr/testify/assert"
	"net/http"
	"os"
	"testing"
)

func TestMain(m *testing.M) {
	rest.StartMockupServer()
	os.Exit(m.Run())
}

func TestLoginUserTimeoutFromApi(t *testing.T) {
	rest.FlushMockups()
	rest.AddMockups(&rest.Mock{
		HTTPMethod:   http.MethodPost,
		URL:          "http://localhost:8282/users/login",
		ReqBody:      `{"email":"firman@gmail.com","password":"firman123"}`,
		RespHTTPCode: -1,
		RespBody:     `{}`,
	})

	repo := usersRepository{}
	user, err :=<EMAIL_ADDRESS>"the-password")

	assert.Nil(t, user)
	assert.NotNil(t, err)
	assert.EqualValues(t, http.StatusInternalServerError, err.Status)
	assert.EqualValues(t, "invalid restclient response when trying to login user", err.Message)
}

The error:
Usage of  .........
flag provided but not defined: -test.v
-mock
    	Use 'mock' flag to tell package rest that you would like to use mockups.
Process finished with exit code 1

Tests where working go v1.12 but with v1.13 and v1.14 getting the same error me too as well

Any update here?

@golanshy like @rajsr357 said, for now the solution is using go v1.12

Hi,
i can see it's closed. Does it mean there's something on the roadmap or it's already fixed for gov1.14 ?
Best.

There's a Pull request to fix this. here, Alternatively, you can modify the same files locally as you're waiting for the PR to be merged

Hi I'm also experiencing the same issue. I just downloaded today.
Use 'mock' flag to tell package rest that you would like to use mockups.
exit status 2
FAIL	github.com/jayzyaj/bookstore_oauth-api/src/repositories/external-api	0.307s

I have go 1.15.2 and am using GoLand 2020.2.  I'm getting "Use 'mock' flag to tell package rest that you would like to use mockups" even though I've get rest.StartMockupServer() specified

The problem seems to be in the func init() for mockup.go where it looks like the command line is being looked at to see if a -mock is being passed in. If you comment out the flag.Parse() the tests run ok.  Not sure what changed, maybe GoLand used to pass a mock into the Unit Test command line, and now it doesn't?

This still seems to be an issue.

Hello there, I'm trying to run tests with this library in go1.19.4 darwin/arm64
Unfortunately getting a log error when trying to pass the mocks flags in code as in the terminal.

Davids-MBP-14-M1:rest david.gamboa$ go test -mock
flag provided but not defined: -test.paniconexit0
Usage of /var/folders/47/yy34nm7x16j16bl5t_7bbtd40000gt/T/go-build111689661/b001/rest.test:
-mock
Use 'mock' flag to tell package rest that you would like to use mockups.
exit status 2
FAIL    github.com/BFDavidGamboa/bookstore_oauth-api/src/repository/rest        0.385s

This is the code for users_repository_test.go file
package rest

import (
	"net/http"
	"os"
	"testing"

	"github.com/mercadolibre/golang-restclient/rest"
	"github.com/stretchr/testify/assert"
)

func TestMain(m *testing.M) {
	rest.StartMockupServer()
	os.Exit(m.Run())
}

func TestLoginUserTimeoutFromApi(t *testing.T) {
	rest.FlushMockups()
	rest.AddMockups(&rest.Mock{
		HTTPMethod:   http.MethodPost,
		URL:          "https://api.bookstore.com/users/login",
		ReqBody:      "{"email":"email@gmail.com","password":"the-password"}",
		RespHTTPCode: -1,
		RespBody:     "{}",
	})

	repository := usersRepository{}

	user, err :=<EMAIL_ADDRESS>"the-password")

	assert.Nil(t, user)
	assert.NotNil(t, err)
	assert.EqualValues(t, http.StatusInternalServerError, err.Status)
	assert.EqualValues(t, "invalid restclient response when trying to login user", err.Message)
}


use TracingFilter for Http.Server

linkerd's TracingFilter captures a lot of useful information, namely req.uri and http.req.host:
https://github.com/BuoyantIO/linkerd/blob/master/router/http/src/main/scala/io/buoyant/router/http/TracingFilter.scala
this filter is added to Http.Router.client, but not Http.Server.stack:
https://github.com/BuoyantIO/linkerd/blob/master/router/http/src/main/scala/io/buoyant/router/Http.scala
it would be useful if both client and server traces recorded the same set of data, particularly for linker-to-linker vs. non-linker-to-linker modes.

Why is it necessary to track this twice?

We don't necessarily need it tracked twice, but it would be helpful to have this data on the server.

What's the exact server-side data we want? The request as it enters the router? Or after identification? or?

Specifically, I think it's more "correct" for linkerd to trace the exact request it received before all rewriting/processing. But I suspect that this won't actually help you with your task.

We talked about this offline: what we really want is to ensure that client spans are emitted even when the client fails to bind properly.  I think we want to do this by moving the client tracing filter up into the bottom of the path stack.


CSS change for Text highlight and link hover

References to the Djangodocs theme are still being used when highlighting text and hovering over a link:

I don't mind the green highlight to be honest. :)
Should we switch it back to the browser default, or yellow? Not sure about yellow at all.

Not very high priority according to me. I am creating a laundry list and will mark the priority on each one.

Fixed the issue