Create install-simple module

Create an installation module that will install simple_grid_puppet_module.

Code will sit in the manifest/install folder to avoid creating several modules.
Actions that need to be performed on Config Master nodes:

Download ENC
Edit puppet.conf

[master]
node_terminus = exec
external_nodes = {path to ENC}
[agent]
server = fqdn of node
runinterval = 0
environment = config

Create a dummy site level config file in /etc/simple_grid/site_level_config/site_level_configuration_file.yaml
Restart puppet server for ENC to be picked up

/manifests/install/{cm/lc}/simple_installer.pp has been implemented


Update documentation.yml

Adding env vars for DocSearch API key and App ID

Moving these changes into PR #120


Fixes for a few more of the issues in the bugs doc

Only bugfixes, no changes to the structure really:

Multiplication by floats, by multiplying xs and dividing ys
Hook up the distToFloat functions (probably should have been a separate PR, sorry)
Remove broken normalization code in MixedShapeBuilder, which fixes the rendering of mm(1, 2, normal(0,1))
Clean up the PointwiseCombination.combine code, to fix the CDF plot of mm(1, 2, normal(0, 1)), and also to pull the magical parts out of that big JS function into reusable & understandable interpolator functions

I got a few other small things, but, will put those into a separate branch.
This is probably going to have a few conflicts with the sampling branch, happy to help you deal with those tomorrow

I've also noticed that downsampling seems to behave pretty weird when multiplication is used, for some reason.
Just multiplying the distribution by 10 changes it significantly.

Yeah, this continues to be a problem. I'm taking out the automatic downsampling for now (to be pushed soon, I've not had the time yet to finish the changes I started two days ago). We'll have to come up with a better solution, at least for the discrete × continuous case

Lots of stuff going on here. I left some comments, most should be pretty straightforward to fix. I'm looking forward to getting all of this integrated.

Also, I think I'm having trouble getting this to work? My impression is that this should have helped get normal(5,2)*2 to work, but it still seems to use sampling for me. Also, sampling with discrete values is kind of buggy now.

I made a quick PR to get it to use non-sampling again, to test much of this functionality.


[5.1] Comment show the process in a wrong way

the method first checks for the custom driver and then normal creator method but comment says the opposite.

Please rebase too.

I fixed it.


Speed up sphinx builds

It would be awfully convenient to be able to build a single notebook, only the notebooks, or specific module docstrings.
The make html command is very helpful. However, the build takes some time
https://github.com/pymc-labs/pymc-marketing/blob/91564cfbcce3d341d3d9bdab91a5b25766764b5a/Makefile#L20-L22
For notebooks, the sphinx rendering is a bit different than the jupyter notebook which can cause render issues not seen.
Not sure if this is possible though!

It is possible to some extent. It should work to quickly check some rendering issues, but many cross-references might break, as sphinx needs to generate the documentation as a whole for all cross-references to be resolvable.
Full background and examples (foldable)
For example, if I use sphinx-build docs/source docs/build -b html -D include_patterns=index.md,notebooks/mmm/mmm_example.ipynb I get a 2 page build that takes a couple seconds and renders the notebook page:
"fast" build page:

whole/regular build page (from website):

Save the sidebar and navbar that are mostly missing (given there are now no other pages in the website so they aren't being populated) everything looks good. If we take a bit more in depth look however, to the "tip" box:
"fast" build page:

whole/regular builg page:

The other notebooks are not part of the "fast" build, so the cross-references pointing to them can't be resolved and therefore don't result in any link, but that doesn't mean their syntax is wrong, they are in fact valid cross-references.
If we modify a bit the build command to include these referenced pages sphinx-build docs/source docs/build -b html -D include_patterns=index.md,notebooks/mmm/mmm_example.ipynb,notebooks/mmm/mmm_lift_test.ipynb,notebooks/mmm/mmm_budget_allocation_example.ipynb now we get:

the nabvar and sidebar are still broken as there is no proper navigation path with only the files included, but the cross-references are now resolved successfully.

What do you think would be the best way to go about that? Documenting how to use include_patterns and exclude_patterns with sphinx-build directive? Or are there common subsets which would make it preferrable to add the commands to the makefile with make mmm to generate the docs of mmm related files or make no-notebooks to exclude notebooks?


Please clean up old cached images

I haven't used lxd that many times yet, and already I have quite a sizable image cache:
$ sudo du -hs /var/lib/lxd/images/
2,7G	/var/lib/lxd/images/
$ lxc image list
+-------+--------------+--------+-----------------------+--------+---------+-------------------------------+
| ALIAS | FINGERPRINT  | PUBLIC |      DESCRIPTION      |  ARCH  |  SIZE   |          UPLOAD DATE          |
+-------+--------------+--------+-----------------------+--------+---------+-------------------------------+
|       | 147b4fdcc090 | no     | Ubuntu xenial (amd64) | x86_64 | 67.04MB | Nov 24, 2015 at 10:52am (CET) |
|       | 1b20851236d5 | no     | Ubuntu xenial (amd64) | x86_64 | 66.87MB | Dec 1, 2015 at 6:47am (CET)   |
|       | 23f3395b9409 | no     | Ubuntu trusty (amd64) | x86_64 | 64.57MB | Dec 1, 2015 at 7:27am (CET)   |
|       | 25fcf43cb929 | no     | Ubuntu trusty (amd64) | x86_64 | 64.56MB | Nov 26, 2015 at 3:49pm (CET)  |
|       | 3e9577f7a954 | no     | Ubuntu wily (amd64)   | x86_64 | 73.36MB | Dec 1, 2015 at 6:40am (CET)   |
|       | b35f2aa010db | no     | Ubuntu xenial (amd64) | x86_64 | 67.06MB | Nov 25, 2015 at 8:29am (CET)  |
+-------+--------------+--------+-----------------------+--------+---------+-------------------------------+

It's of course very desirable to cache the latest version of a particular image. But it would be nice to automatically clean up older versions of the same image type,so that they don't pile up. It seems every image inflates to roughly 400 MB in /var/lib/lxd/images/.
FTR, these were created with something like lxc launch images:ubuntu/trusty/amd64 t1 where images: is https://images.linuxcontainers.org:8443.
Thanks!

Alternatively, is there some "cache prune" command that one could run from cron? I'm planning to use this for production autopkgtest, and they will create and remove containers all the time (and thus quickly pile up huge caches).

Hmm, images should be automatically flushed 10 days after they were last used (configurable), seems like there's something off there.
@hallyn

@martinpitt for autopkgtest, you probably want to use "lxd-images import ubuntu SERIES ARCH --alias SOME-NAME --sync" which will get you the official cloud images rather than the unofficial images our Jenkins builds. The --sync combined with the cronjob we ship with LXD in Ubuntu will also mean that the image will be updated for you every hour by cron.

(and yes, we know it's a bit confusing right now with the two ways to get Ubuntu images, we will merge simplestream support directly in LXD in the next couple of months which will make the lxd-images script go away and hopefully simplify things a bit)

TBH, your images are much better than the cloud images -- they have tons of stuff on them which I don't want and which is even detrimental for testing. I have a big list of apt-get purge in my image preparation scripts for creating my own base images from the cloud images. It seems at some point I'll need to do that anyway for lxd then (once you drop your images).
Thanks for the hint with importing! However, will that actually give me any benefit over the lazy downloading with specifying a remote image source? The nice thing there is that I get exactly the images that are needed, and I don't need any extra maintenance/cron jobs to sync images explicitly.

Hmm, images should be automatically flushed 10 days after they were last used (configurable),

Ah, it hasn't been 10 days yet, just 7 :-) I'll watch this and report back in 4 days when the oldest image gets 11 days old. Thanks!

You can also change the value:
lxc config set images.remote_cache_expiry 2

I've never really seen this work here but that's mostly likely due to me never having images that are unused and old enough to be pruned. Looking at the code, just reducing the expiry should trigger an immediate expiry run.

And no, if you're happy with the super minimal LXC images, you can keep using them.
As images.linuxcontainers.org appears as a LXD server, expiry is automatically setup for you and you don't need a cron job or anything.
I just thought you'd prefer the cloud images as I believe that's what's currently used for the VM based autopkgtest setup and would make sense as a way to provide a consistent environment across arches.

(but for Xenial, there sure is the benefit that our own images are actually built daily, which is not yet the case with the cloud images :))

I just thought you'd prefer the cloud images as I believe that's what's currently used for the VM based autopkgtest setup

As a basis, yes, as that's all I get to start from. But I adjust them quite a bit (http://anonscm.debian.org/cgit/autopkgtest/autopkgtest.git/tree/setup-commands/cloud-vm-setup) to downsize them again.

TBH, your images are much better than the cloud images -- they have tons of stuff on them which I don't want

My 2 cents: I totally agree.

I close this for now. I'm quite sure I was just missing the 10 day cleanup period. If I really still have the old images next week I'll reopen. Thanks for the hint about lowering the cache time, that's going to be useful!

Hmm, I checked today again and I now have images which are more than 10 days old:
|              | b35f2aa010db | no     | Ubuntu xenial (amd64) | x86_64 | 67.06MB  | Nov 25, 2015 at 8:29am (CET)  |
|              | 147b4fdcc090 | no     | Ubuntu xenial (amd64) | x86_64 | 67.04MB  | Nov 24, 2015 at 10:52am (CET) |
| xenial/amd64 | 322b76d2e1d4 | no     |                       | x86_64 | 122.00MB | Dec 4, 2015 at 9:45am (CET)   |

So reopening.

@hallyn any idea what may be going wrong?

@martinpitt
could you shut down lxd, then do
sudo sqlite3 /var/lib/lxd/lxd.db
SELECT value FROM config WHERE key='images.remote_cache_expiry';
I think what's going wrong is we're not setting a default of 10 like we meant to do.

Oh, I see, we're supposed to cache there being no value and return 10 in that case.

There are a few little errors there.  I will push a fix later today plus a real test case.

Note that the specs/configuration.md file says of the expiry time:
Number of days after which an unused cached remote image will be flushed
There are other bugs in the code anyway (expiry date was calculated wrong) which i fixed  locally, but this description would not apply to the lxd-images imported images because they are not marked as cached, and presumably are not unused.
Do we want to change this to say that any image created before current date - expiry-days is deleted?

No, lxd-images indeed aren't cached images and that's fine.
lxd-images itself has a --sync flag which does the auto-update and garbage collection.
With lxd-images going away soon, the LXD caching mechanism will then be used for the cloud images too.
@martinpitt is using the LXC images I believe.

ok thx, then i'll post what i have to fix.

It seems you already have this figured out, but for the record:
``
sqlite> SELECT value FROM config WHERE key='images.remote_cache_expiry';
There is no hit at all. `SELECT * FROM config` only has keys `core.https_address` and `core.trust_password`. I think that confirms what @hallyn said.

> @martinpitt is using the LXC images I believe.

Yes, e. g. `ubuntu/xenial/amd64` from https://images.linuxcontainers.org:8443. They are really nice!


Revert "Revert "DOMNodeList::item() returns DOMNode instead of DOMElement""

Reverts JetBrains/phpstorm-stubs#515
@MaXal @smoench here is test code: https://3v4l.org/VsnW7

NB: is_a(DOMElement::class, DOMNode::class, true) === true

@b1rdex Thank you :-)

I'm sorry my code sample was really bad and not illustrative at all. But the main point remains so far - the return type is DOMElement. Yes DOMElement extends DOMNode` but we should specify the most specific class, not the parent.
Please note that my change was caused by new false positive inspections errors that occured after the change on the real-life code in the popular projects (Zend, Mediawiki, b2c).
Consider the following code:
<?php
$html = '

   ';
$dom = new domDocument;
$dom->loadHTML($html);
$tags = $dom->getElementsByTagName("tr");
f($tags->item(0));

function f(DOMElement $a){
    echo "in f";
}

It will produce a warning in case we change the return type to DOMNode.
Please also note that I have nothing against adding |null to the return type. I just against changing
DOMElement to DOMNode.
If you have any real example when the item returns DOMNode and not DOMElement please provide it and I will merge the request right away.

The PHP documentation says it returns DOMNode so phpstub should do it. Please read the class name carefully: DOMNodeList. It says it is a list of DOMNode's. So don't change the API of PHP by your own!
In my case phpstan has been failed and said my code is wrong as they are all relying on the PHP Api. So once again don't change the API of PHP by your own!

I've modified the code snippet to demonstrate that DOMNodeList::item() might actually return something that is not a DOMElement.
https://3v4l.org/GvRgi
Here, the last call returns an instance of DOMText which – like DOMElement – extends DOMNode.
Depending on the context, it can be safe to assume that a particullar DOMNodeList only contains DOMElement instances, but in general, you cannot make that assumption.
DOMNode is the correct return type.

@smoench Unfortunately, PHP documentation is not a definite source of API and it contains errors and inaccuracies but in this case, it's indeed correct.
Thanks to @nikic for the following code example that produces DOMNode elements as a result of item call: https://3v4l.org/oSb9N
Once again I'm sorry for jumping to conclusions and thank you all for being persistent!

@derrabus Thank you for another example!


Unable deploy wave dashboard metadata with any Salesforce API version

Error when tried to deploy the wave dashboard through meta data api
Steps To Reproduce:

retrieve the wave dashboard from the org
deploy the same wave dashboard to the org with same api version / package.xml version

Expected result
Should be able to deploy successfully without any issue
Actual result
Property 'dateVersion' not valid in version 51.0
System Information
    "cliVersion": "sfdx-cli/7.133.0",
    "architecture": "darwin-x64",
    "nodeVersion": "node-v16.4.2",
    "pluginVersions": [
            "@oclif/plugin-autocomplete 0.3.0 (core)",
            "@oclif/plugin-commands 1.3.0 (core)",
            "@oclif/plugin-help 3.3.1 (core)",
            "@oclif/plugin-not-found 1.2.6 (core)",
            "@oclif/plugin-plugins 1.10.11 (core)",
            "@oclif/plugin-update 1.5.0 (core)",
            "@oclif/plugin-warn-if-update-available 1.7.3 (core)",
            "@oclif/plugin-which 1.0.4 (core)",
            "@salesforce/sfdx-plugin-lwc-test 0.1.7 (core)",
            "alias 1.2.0 (core)",
            "apex 0.7.0 (core)",
            "auth 1.8.0 (core)",
            "config 1.3.14 (core)",
            "custom-metadata 1.0.12 (core)",
            "data 0.6.8 (core)",
            "generator 1.2.2 (core)",
            "info 1.2.0 (core)",
            "limits 1.3.0 (core)",
            "org 1.11.0 (core)",
            "salesforce-alm 53.7.2 (core)",
            "schema 1.1.0 (core)",
            "sfdx-cli 7.133.0 (core)",
            "sfdx-git-delta 4.11.0",
            "source 1.7.0 (core)",
            "telemetry 1.4.0 (core)",
            "templates 52.7.0 (core)",
            "trust 1.1.0 (core)",
            "user 1.7.0 (core)"
    ],
    "osVersion": "Darwin 21.1.0"

Same issue after getting retrieving wave dashboard from production org and trying to deploy to any sandbox.
Analytics-Lens ... Property 'dateVersion' not valid in version 52.0
Issue came up in the last 2 days, may be related to spring/summer release switch?
sfdx-cli/7.150.0 win32-x64 node-v16.15.0

Hi Shetzel,
Thanks for your inputs.
I am actually passing the below in package.xml & sfdx-project.json version and using the option[SFDX:Retrieve Source in Manifest from Org] visual studio code.

Track_Files_and_Attachments
WaveDashboard

51.0

-------
{
"packageDirectories": [
{
"path": "force-app",
"default": true
}
],
"name": "Test-profile",
"namespace": "",
"sfdcLoginUrl": "https://login.salesforce.com",
"sourceApiVersion": "51.0"
}
I am able to retrieve the files but when I try to deploy that back to same org I am getting this error.
Property 'dateVersion' not valid in version 51.0
I tried this with 52 and 53 version both in package.xml and also sfdx-project.json files.
I looked for this error in community but no luck.
What would be the fix for this ? Is it bug ? I am observing this after summer'22 release

Retrieving from the VS Code extension is similar but not exactly the same.  Retrieve source from manifest means you're pointing to a manifest file.  Does the manifest have <version>51.0</version> in the contents?  Does this reproduce with the CLI by running:
sfdx force:source:retrieve -x <path-to-manifest> -u <org-username>  (optionally append --apiversion=51.0)
sfdx force:source:deploy -x <path-to-manifest> -u <org-username>
If you are specifying API version 51.0 and the retrieved dashboard contains dateVersion then that would be a serverside problem and the owning team (i.e., not CLI) would have to fix it.  The work item attached to this issue will handle that.

@AzaruddinKhan  @micha-voigt - I've heard from the owning team that it's a serverside bug that was recently fixed and in the process of being rolled out.  I will try to get dates for you.  If you are seeing this fixed already please let me know here.

The fix should be available now.  Please reopen if you're still seeing problems.


Skeleton: in some cases, cannot determine if a field being accessed in a method really belongs to the enclosing class

We need more than just the name to determine if a class is using its own attribute or that of another one. We should somehow include the fully qualified name of the class that owns the field that is being operated on.
To illustrate the problem, consider two classes:
public final class Foo {
    private static String NAME = "hey";

    public void test() {
      Bar.NAME = "test";
    }
}
public final class Bar {
    public static String NAME = "hey";

    public void test() {
      Bar.NAME = "test";
    }
}

The resulting skeleton for Foo.test() does not tell us whether the field NAME is its own attribute or that of another class:
<method abstract="false"
        ctor="false"
        desc="()V"
        name="test"
        public="true"
        static="false">
   <return>V</return>
   <args/>
   <ops>
      <op code="put_static">NAME</op>
   </ops>
</method>

@yegor256/z please, pay attention to this issue

Job #156 is now in scope, role is DEV

Bug was reported, see §29: +15 points just awarded to @llorllale/z, total is +495

The job #156 assigned to @paulodamaso/z, here is why; the budget is 30 minutes, see §4; please, read §8 and §9; if the task is not clear, read this and this; there will be a monetary reward for this job

@0crat please wait, looks like there is no reviewer for this issue yet.

@0crat please wait for #257 review (here)

@paulodamaso Can't understand "please", try one of these:

assign Assign a performer to this issue
boost Set a boost for the job
hello Just say hello
in Register this issue in scope (WBS)
out Close the order and remove this job from scope
pay Pay a user some extra cash
quality Review a task
resign Resign from this issue
status Check the status of the job
version Print current version of the bot
wait Register an impediment for a job

@0crat wait for #257 review

@0crat wait for #257 review (here)

@paulodamaso The impediment for #156 was registered successfully by @paulodamaso/z

@llorllale the puzzle #261 is still not solved.

@llorllale #257 merged and puzzle #261 left for improving implementation, please close.

@paulodamaso thanks

@elenavolokhova/z please review this job completed by @paulodamaso/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

The job #156 is now out of scope

@0crat quality good

Order was finished, quality is "good": +35 point(s) just awarded to @paulodamaso/z

Quality review completed: +8 point(s) just awarded to @elenavolokhova/z

@llorllale the puzzle #358 is still not solved; solved: #261.

@llorllale all 2 puzzles are solved here: #261, #358.


579 config cleanup3

:clipboard: Add associated issues, tickets, docs URL here.
Overview
Describe what your Pull Request is about in a few sentences.
Changes
Describe your changes and implementation choices. More details make PRs easier to review.

Change 1
Change 2
...

Testing
Describe how to test your new feature/bug fix and if possible, a step by step guide on how to demo this.

Coverage decreased (-11.6%) to 73.022% when pulling 7f86e07db2ee5a8c48ec733c45ef0461ce162fe2 on 579-config-cleanup3 into 6df52caa9f7aee079cb9b7f78e63ee8d1d44a80d on master.


Create a Logo for FFIG

Maybe a wasp? FFIG ~= fig and fig-wasps are cool (if a bit creepy).
Maybe a fig?
http://www.bbc.co.uk/earth/story/20160429-a-tale-of-loyalty-and-betrayal-starring-figs-and-wasps

looks closed to me. I like the logo. Where did you get it from?

@ajbennieston created it.


GitHub worklow setup to build apk for every PR.

For every PR new buidl will be launched and you could get apk after
build.
Gradle scripts is updated also. Because there are no scripts for
Windows:)

To get artifact go to Checks tab in PR

Then, open poup Artifacts and download the build

If for some reason build failed check would marked ask failed and no artifacts will be available.


Flannel not using SubnetLen json key

Expected Behavior
"SubnetLen": 26 should make networks with a /26 bit net mask for kubernetes nodes
I had this behavior with flannel 0.8( k8s 1.7.5) and 0.9( k8s 1.8.1)
Current Behavior
"SubnetLen": 26 appears to be ignored and I get the default /24 bit mask
Your Environment

Flannel version: 0.8 and 0.9, at different times and currently 0.9
Backend used (e.g. vxlan or udp): vxlan
Etcd version: 3.0.17, what came with kubernetes
Kubernetes version (if used): 1.7.5 and 1.8.1
Operating System and version: ubuntu LTS 16.04
Link to your project (optional):

from kube-flannel.yml:
data:
  cni-conf.json: |
    {
      "name": "cbr0",
      "type": "flannel",
      "delegate": {
        "isDefaultGateway": true
      }
    }
  net-conf.json: |
    {
      "Network": "{{ k8s_pod_network }}",
      "SubnetLen": {{ k8s_pod_local_netmask }},
      "Backend": {
        "Type": "vxlan"
      }
    }

this is from inside a flannel pod:
root@kube-m2:/etc/cni/net.d# kubectl -n kube-system exec -it kube-flannel-ds-thj8w -- /bin/sh
/ # cd /etc/kube-flannel/
/etc/kube-flannel # ls
cni-conf.json  net-conf.json
/etc/kube-flannel # cat cni-conf.json
{
  "name": "cbr0",
  "type": "flannel",
  "delegate": {
    "isDefaultGateway": true
  }
}
/etc/kube-flannel # cat net-conf.json
{
  "Network": "<IP_ADDRESS>/21",
  "SubnetLen": 26,
  "Backend": {
    "Type": "vxlan"
  }
}

and "ip address for the cni0 and flannel.1 interface, with cni0 getting a /24 :
60: flannel.1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UNKNOWN group default
    link/ether da:37:51:4d:4b:c3 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/32 scope global flannel.1
       valid_lft forever preferred_lft forever
    inet6 fe80::d837:51ff:fe4d:4bc3/64 scope link
       valid_lft forever preferred_lft forever
61: cni0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1450 qdisc noqueue state UP group default qlen 1000
    link/ether 0a:58:0a:69:81:01 brd ff:ff:ff:ff:ff:ff
    inet <IP_ADDRESS>/24 scope global cni0
       valid_lft forever preferred_lft forever
    inet6 fe80::a86b:38ff:fe7c:cc25/64 scope link
       valid_lft forever preferred_lft forever

When using flannel with the kubernetes subnet manager (--kube-subnet-mgr), flannel will just use the podCIDR that's assigned to the node. See https://github.com/coreos/flannel/blob/master/Documentation/troubleshooting.md#kubernetes-specific

thanks for the help


Add pytest push marker for CI

Added pytest marker for the models which are to be part of Push CI

Seems like pre-commit checks are failing. Please checkout this doc section for more details:

https://docs.tenstorrent.com/tt-forge-fe/tools.html

@vmilosevic is this something that can fit our push/nightly test split? :))

Yes, we can use mark to select which tests will be run in workflow.
pytest  -m "push"
pytest  -m "not push"
pytest -v -m "nightly"
...

We can also pass this in as workflow input to keep everything generic.
Best to avoid negative filters if possible.


Added support for Cross Domain css loading

Added a new variable config: { css: { crossorigin : '' } }
If this exists, it sets the attribute crossorigin for the link created inside linkLoad method.

Appreciated for the contribution. This project isn't really maintained anymore unfortunately though.

@tHBp besides, Could u please add test case for testing this new property, so that we could be sure end customers will be fine with or without that property.


database: create mocks

needed to write unit tests for systemservices pkg. ASAP

Why do you want to mock database? there is no need to mock it, you can easily create a new instance of database under /tmp filesystem (or current test directory like in other packages).

Why do you want to mock database? there is no need to mock it, you can easily create a new instance of database under /tmp filesystem (or current test directory like in other packages).
Mocking it only completes the test (that uses a database) with no visible pros.

I like the idea of not depending on external systems -like filesystem in this case- as much as possible. Creating a database mock with mockery is dead simple and providing fakes with testify/mock is very straightforward.
Yes, I agree that having  some piece of code that interacts with filesystem is not a problem with unit testing but if avoiding it also simple, I prefer avoiding. As addition to this, in future we might depend on an external database that runs as an independent server which requires mocking. So having a mock in the beginning is a win win situation.

I agree this one was not really necessary but I like that we have this interface and concrete implementation maybe the mocks are too much but again it's just one command to execute to have this flexibility so it's nice and we could like that create some tests that mimics some issues with the system so i don't see any problem to merge that


Allow custom port on ReturnURL for all api endpoints

Hi,
I don't know if this is an issue with the php sdk or with the web api in general.
Some api endpoints remove the port part of the ReturnURL field.
This is not consistant, because a lot of other api endpoints keep the port when a port is part of the return url.
Keeping the port is important on local environment, for test purpose.
For example, when creating a mandate/direct debit direct payin, we can see that the return url in the request is http://mywebsite.com:8080/fr/campaigns/33/donation/158/mandate_return and is changed to http://mywebsite.com/fr/campaigns/33/donation/158/mandate_return in the api response:
[2018-05-02 10:30:05] local.DEBUG: New request
[2018-05-02 10:30:05] local.DEBUG: FullUrl : https://api.sandbox.mangopay.com/v2.01/xxx/mandates/directdebit/web
[2018-05-02 10:30:05] local.DEBUG: RequestType : POST
[2018-05-02 10:30:05] local.DEBUG: HTTP Headers : Array
(
    [0] => Content-Type: application/json
    [1] => User-Agent: MangoPay V2 PHP/2.8.0
    [2] => Authorization: bearer xxxxxxxxx
)

[2018-05-02 10:30:05] local.DEBUG: RequestData object :Array
(
    [BankAccountId] => 48081404
    [Culture] => FR
    [ReturnURL] => http://mywebsite.com:8080/fr/campaigns/33/donation/158/mandate_return
)

[2018-05-02 10:30:05] local.DEBUG: RequestData JSON :{"BankAccountId":"48081404","Culture":"FR","ReturnURL":"http:\/\/mywebsite.com:8080\/fr\/campaigns\/33\/donation\/158\/mandate_return"}
[2018-05-02 10:30:06] local.DEBUG: Response JSON : {"Scheme":null,"BankAccountId":"48081404","BankReference":null,"Culture":"FR","DocumentURL":"https://api.sandbox.mangopay.com/public/mandates/e8a73d/927a5989df0141ed850cd03aacd04c0a/document","ReturnURL":"http://mywebsite.com/fr/campaigns/33/donation/158/mandate_return?MandateId=48081406","RedirectURL":"https://api.sandbox.mangopay.com/public/mandates/e8a73d/927a5989df0141ed850cd03aacd04c0a/confirmation","Id":"48081406","CreationDate":1525257006,"Status":"CREATED","UserId":"48080934","ExecutionType":"WEB","MandateType":"DIRECT_DEBIT","Tag":null,"ResultCode":null,"ResultMessage":null}
[2018-05-02 10:30:06] local.DEBUG: Decoded object : stdClass Object
(
    [Scheme] =>
    [BankAccountId] => 48081404
    [BankReference] =>
    [Culture] => FR
    [DocumentURL] => https://api.sandbox.mangopay.com/public/mandates/e8a73d/927a5989df0141ed850cd03aacd04c0a/document
    [ReturnURL] => http://mywebsite.com/fr/campaigns/33/donation/158/mandate_return?MandateId=48081406
    [RedirectURL] => https://api.sandbox.mangopay.com/public/mandates/e8a73d/927a5989df0141ed850cd03aacd04c0a/confirmation
    [Id] => 48081406
    [CreationDate] =><PHONE_NUMBER>
    [Status] => CREATED
    [UserId] => 48080934
    [ExecutionType] => WEB
    [MandateType] => DIRECT_DEBIT
    [Tag] =>
    [ResultCode] =>
    [ResultMessage] =>
)

This issue has been fixed in our last Caimans release, which is already live.


Fixes #2: Use components from website

(This PR is WIP only because https://github.com/datenanfragen/website/pull/902 isn't merged yet and thus I can't properly add the package.)
Thanks to https://github.com/datenanfragen/website/pull/902, it is now easy to use the website components here.
Two other, unrelated changes in this PR:

I explicitly set the webPreferences to secure values, even though those are already the defaults. I don't anticipate Electron regressing on the secure defaults in the future but I think it's good practice to be explicit regardless, just in case.

I upgraded from Electron 17 to 19.

tsc (which I previously used for transpiling the Electron main process code) doesn't bundle dependencies. Thus, we couldn't use any external modules in that code. Now we also bundle the main code using Parcel, just like the renderer code.
This change broke electron-reloader, which can't deal. I switched to electronmon, which seems nicer anyway.

This is ready for review and merge now.


⚠ Cioos Pacific CKAN Sitemap has degraded performance

In 9cf2c93, Cioos Pacific CKAN Sitemap (https://catalogue.cioospacific.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 11615 ms

Resolved: Cioos Pacific CKAN Sitemap performance has improved in 7d759e4 after 6 minutes.


Book Recommendation:Project Added

Pull Request for DL-Simplified 💡
Issue Title : [Project Addition]: AI Based Book Recommendation System

Info about the related issue (Aim of the project) : To develop an AI-based book recommendation system that suggests books of similar type or genre based on the book name provided by the user.
Name: Sanjeev Kumar
GitHub ID: Sanjeev-Kumar78
Email ID<EMAIL_ADDRESS>Idenitfy yourself: (Mention in which program you are contributing in. Eg. For a JWOC 2022 participant it's, JWOC Participant) GSOCC'24 Contributor

Closes: #614
Type of change ☑
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist: ☑

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[ ] I have commented my code, particularly wherever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[ ] My changes generate no new warnings.
[ ] I have added things that prove my fix is effective or that my feature works.
[ ] Any dependent changes have been merged and published in downstream modules.

Got it, but what's the problem with using streamlit for a web app?
@abhisheks008

Got it, but what's the problem with using streamlit for a web app? @abhisheks008

No problem with the Streamlit app, I am requesting you follow the project structure.

Okay 👍

If you want to create a web app for the same project then please follow the project structure for the same and update accordingly. @Sanjeev-Kumar78
For your reference, https://github.com/abhisheks008/DL-Simplified/tree/main/Brain Tumor Detection

Based on the reference, I have made updates to the project structure. Please take another look at it.
@abhisheks008

I'm sorry for the confusion earlier. I've made the necessary updates to the dataset model, and it turns out that my project didn't need any images, so I didn't create an images folder.
@abhisheks008

Done. @abhisheks008 Please review.

Images folder is missing in this project. Please add the EDA results and accuracy graphs inside the Images folder.

Please check the Images folder. Is everything okay?


How to not let mapbox override a download

We are using mapbox offline to download offline data about countries and cites. Is there a way to do this separation of two destinations being on the same bounds? For example, if i download Berlin with zoom level 15, and then download Germany with zoom level 8, Berlin is overwritten and it can only be seen with zoom level 8.

Berlin is overwritten did you verify that in the sqlite database?
If both regions were downloaded with the same style, this should work.


shareViaWhatsAppToReceiver

Hi guys! i'm trying to share the screenshot to specific receiver but no way..
Do you know if i need to do something more?
this is my code:
ShareWhatsapp(){
this.socialSharing.shareViaWhatsAppToReceiver(this.whatsapp_number, this.text, this.screen, this.url)
}
When i try to use shareViaWhatsApp without Receiver everything works fine.
any suggestion?

I will recommend - https://developer.mozilla.org/en-US/docs/Web/API/Navigator/share

That article didn't make much sens to me. If I am shareing base64 image, do I still need to check "canShare"?
I am getting base64 image via domToImage pulgin that I want to send to a whatsapp number llike
var node = document.getElementById('body') ;
domtoimage.toPng(node)
    .then((dataUrl) => {
      this.socialSharing.shareViaWhatsAppToPhone('+61xxxxxxxxx','share toPhone', dataUrl,null).then((res) => {
        console.log('image shared with whatsapp');
      }).catch((e) => {
        console.error('social share, something went wrong!', e);
      });
    })
    .catch((error) => {
        console.error('oops, something went wrong!', error);
    });

As @ademir10  said, this all works fine with "socialSharing.shareViaWhatsApp" for me as well. But with ToPhone or ToReceiver its just not attaching image. Text message works fine though.


Making vector comparisons pluggable

Description
Opening an issue to continue discussion originating here:
https://github.com/apache/lucene/pull/13076#issuecomment-1930363479
Making vector similarities pluggable via SPI will enable users to provide their own specialized similarities without the additional burden of Lucene core having to provide BWC for all the various similarity functions (e.g. hamming, jaccard, cosine).
It is probably best that the plug-in-play aspect is placed on FieldInfo, though this would be a bit of work as FieldInfo isn't currently pluggable. Attaching it directly to a particular Vector Format would place undue burden on users, requiring a new format for any field that desires a separate similarity.
While I am not 100% sure how to add it to FieldInfo, I do want to try and figure out the API for such a change.
When used within a particular vector format, the following scenarios would be useful:

Indexing, comparing on-heap vectors accessible via ordinals
Merging, comparing off-heap vectors, possibly reading them directly on-heap via ordinals
During search, an on-heap user provided vector being compared with off-heap vectors via ordinals (potentially reading them on-heap).

Some of the optimizations discussed here: https://github.com/apache/lucene/pull/12703 show some significant gains in being able to simply have a memory segment and an ordinal offset. While we are not there yet in Lucene, it indicates that we shouldn’t force the API to reading off-heap vectors into a float[] or byte[] arrays..
I was thinking of something like this. 100%, this is not finalized, just wanting to start the discussion.

public abstract class VectorSimilarityInterface implements NamedSPILoader.NamedSPI {

  private static final class Holder {
    private static final NamedSPILoader<VectorSimilarityInterface> LOADER =
      new NamedSPILoader<>(VectorSimilarityInterface.class);
    private Holder() {}
    static NamedSPILoader<VectorSimilarityInterface> getLoader() {
      if (LOADER == null) {
        throw new IllegalStateException(
          "You tried to lookup a VectorSimilarityInterface name before all formats could be initialized. "
            + "This likely happens if you call VectorSimilarityInterface#forName from a VectorSimilarityInterface's ctor.");
      }
      return LOADER;
    }
  }

  public static VectorSimilarityInterface forName(String name) {
    return VectorSimilarityInterface.Holder.getLoader().lookup(name);
  }

  private final String name;
  protected VectorSimilarityInterface(String name) {
    NamedSPILoader.checkServiceName(name);
    this.name = name;
  }
  @Override
  public String getName() {
    return name;
  }

  // Comparing an "on heap" query with vectorValues that may or may not be on-heap
  // Maybe we don't need this and the `byte[]` version as we could hide the "on-heap query"
  // in an "IdentityRandomAccessVectorValues" which only returns the query vector...
  public abstract VectorScorer getVectorScorer(RandomAccessVectorValues<float[]> vectorValues, float[] target) throws Exception;

  public abstract VectorComparator getFloatVectorComparator(RandomAccessVectorValues<float[]> vectorValues) throws Exception;

  public abstract VectorScorer getVectorScorer(RandomAccessVectorValues<byte[]> vectorValues, byte[] target) throws Exception;

  public abstract VectorComparator getByteVectorComparator(RandomAccessVectorValues<byte[]> vectorValues) throws Exception;
  static interface VectorScorer extends Closeable {
    float score(int targetOrd);
  }

  static interface VectorComparator {
    float compare(int vectorOrd1, int vectorOrd2);
  }
}

It looks like the SPI injection could occur in FieldInfosFormat#read & FieldInfosFormat#write (though a new one would have to be built Lucene911FieldInfosFormat or something).
This would also include a new codec as the field format will change.
I am not 100% sold on how this API looks myself. I don't think RandomAccessVectorValues is 100% the correct API as it either exposes too much (e.g. ordToDoc) or too little (for off-heap, we don't get access to the MemorySegment nor files...).

Closing as fixed by https://github.com/apache/lucene/pull/13288


the texture and figure structure can be changed to be simpler

[x] Textures should be extracted from the Figures directory (#391)
[ ] Below would be the new structure:
Textures

Texture.png

Figures
FigureImage1.png
FigureImage2.png

Renders

Image.#.png
Image.#.thumbnail.png

Textures

Texture.thumbnail.png

Okay with me.

I'm pretty sure this has already been fixed


WIP: Various improvements in controller

Description
Minor improvements in the repo CI scritps.
Type of change

[x] New feature (non-breaking change which adds functionality)

Testing steps
Please check CI

Seems good
Oh wait, it's a WIP. Well, I was tagged for a review, so I'm reviewing. ¯_(ツ)_/¯

np TY. I just realized that there are issues found by shellcheck. Now it should be ok, hopefully :)


Add PEP8Speaks to contributors

PEP8Speaks is an alternative code styler used to scan code for rubbish styling

@all-contributors please add @pep8speaks for review


initial commit

what
Initial commit
why
Provide information on kops IAM roles with minimal dependencies

Just one thing... The README.md is generated from the README.yaml. Make all your changes to the README.yaml, then rebuild.
Please rebuild the README.md by running the following commands:
make init
make readme/deps
make readme

There might be a lot of changes in the README.md as a result. That's okay!
Sorry for the inconvenience!

@osterman I ran those command before submitting the PR. I ran them again and there were no changes.

@nuru the file is not committed =)


Difference between code and paper

Hi, first, thanks for sharing for this great work !
I was reading the paper and the code and I notice in the Mean Teacher exp, the paper said you use x1 and x2 with two different augmentations, but in the code you simply use x to feed the teacher and the student ? Is it normal or did I miss something ?
Moreover, could you release the mean teacher experience for cityscapes ? Because I could not reproduce the results from the paper
Thanks

Hi, GCT finds that using x1 and x2 for mean teacher has no benefit on the performance, thus we follow them and use x as input only.
For MeanTeacher on Cityscapes, the unsup_weight is 100, too. The supervised loss is OHEM, which is different from that of VOC.


Fix/use custom contains matcher

Description
Replace some problematic expectations with custom matcher intoduced in #54756
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I signed the CLA.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[x] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: Replace with a link to your migration guide

NOTE: must be landed after https://github.com/flutter/flutter/pull/54756

Created cleaner version in #55088 and therefore closing.


Add buffers_type

template<class BufferSequence>
using buffers_type = ...

This will be boost::asio::const_buffer or boost::asio::mutable_buffer depending on the buffer sequence. Goes in <boost/beast/core/type_traits.hpp>.
This can replace some of the uses of std::conditional such as in buffers_suffix.

Done


BUG: Use itk.array_from_image for array

Experimentation through use has found that the use of a view
for np.asarray can result in unexpected behavior or crashes.

Does this approach use copy-on-write, or immediate copy?

An immediate copy.


[BUG] CognitiveServices TextAnalytics DetectLanguage has an invalid default as country hint

Describe the bug
DetectLanguageAsync defaults countryHint to "en" which is not a valid ISO 3166-1 alpha-2 code

Expected behavior
Should default to a valid country code like "gb" or "us"
Actual behavior (include Exception or Stack Trace)
Returns an error as the country code is invalid
To Reproduce
Steps to reproduce the behavior (include a code snippet, screenshot, or any additional information that might help us reproduce the issue)

Call DetectLanguageAsync with just the input text

Environment:

Name and version of the Library package used:
Microsoft.Azure.CognitiveServices.Language.TextAnalytics 4.0.0

Hi @DiegoFaFe .
What version of the library are you using?
We did notice that bug and was fixed in preview.2 . See package here.
I would like to encourage you to take a look at the new client library for Text Analytics under namespace Azure.AI.TextAnalytics. This new library targets the latest version of the service (3.0-preview) which includes new and improved functionalities.

Hi @maririos , I was using the latest stable 4.0.0, if that's already solved then I can close the issue :) Just a quick question before closing it though, Is there any ETA for the stable release?

Release for Text Analytics 3.0 for service and client library Azure.AI.TextAnalytics 1.0.0 is expected around April-May.
Next week we are going to be releasing Azure.AI.TextAnalytics1.0.0.preview.3.0 in case you want to start trying it :)

Thanks @maririos I'll give it a go, I'm closing this issue as its resolved on the preview package


fix error because of new ci requirements & safe updated packages

upping the actions versions took care of the following issue.
The add-path command is disabled. Please upgrade to using Environment Files or opt into unsecure command execution by setting the ACTIONS_ALLOW_UNSECURE_COMMANDS environment variable to true. For more information see: https://github.blog/changelog/2020-10-01-github-actions-deprecating-set-env-and-add-path-commands/


LuckPerms Web Editor doesn't re-add groups

I was using the LP Web Editor then I had to remove a few groups and re-add them because weights weren't setup correctly (The weights were for the web editor to look organised so I can manage it), so I deleted them, re-added them and saved the data and ran the command it gave me. Then I saw that those specific groups I re-added were just removed, not re-added.

Fixed in the above merge ^ this can be closed (and preferably moved to the LuckPermsWeb repo) 👌


Avoid some synchronization replot in matplotlib backend

This PR uses the matplotlib Axes.apply_aspect method to synchronize plot limits rather than doing a full replot.
This avoids to replot when getting the limits of a plot with keep aspect ratio.

Sounds very good. As it was a big problem on plot blinking.
This could have an impact. I think it is a good idea to check pyFAI.


flutter pub should support recently added subcommands from dart pub.

The following dart pub commands all seem to lack a flutter pub counterpart:

dart pub add
dart pub remove
dart pub logout
dart pub login
dart pub upgrade --null-safety
dart pub upgrade --major-versions

And dart pub global activate puts things into a different directory from flutter pub global activate.  Yes, you need to add two elements to your PATH, and you can install the same thing in both dirs, which can get very confusing.

@RandalSchwartz are you sure? I believe those should go to the same directory: $PUB_CACHE/bin.
What directories are you seeing for each command? What platform are you on?

@RandalSchwartz are you sure? I believe those should go to the same directory: $PUB_CACHE/bin.
What directories are you seeing for each command? What platform are you on?

@RandalSchwartz, yes, flutter uses a different default path for PUB_CACHE, but that's an orthogonal issue.

@RandalSchwartz, yes, flutter uses a different default path for PUB_CACHE, but that's an orthogonal issue.

One more missing option --trace:
flutter pub --trace get
Could not find an option named "trace".

Run 'flutter -h' (or 'flutter <command> -h') for available flutter commands and options.

One more missing option --trace:
flutter pub --trace get
Could not find an option named "trace".

Run 'flutter -h' (or 'flutter <command> -h') for available flutter commands and options.

Fixed in https://github.com/flutter/flutter/pull/74060
We're only missing --trace, but that is something we  can sync on later.

Fixed in https://github.com/flutter/flutter/pull/74060
We're only missing --trace, but that is something we  can sync on later.


fix: add bee-v6-pre

Trying out new BeeJS v6.0.0-pre
Additionally, all significant dependencies got updated.
Remaining:

[ ] make Jest work with ESM import.

Resolves #171

bee-js version 6.0.0-pre.2 works


Added option to throw exception when first auth attempt rejected by peer

This gives us a way to achieve two things that were previously not possible:

Poll the ADB server to determine whether our public key has been saved
Attempt a connection without risking an auth popup appearing (eg. connecting from a background process)

Looks like compilation failed. Please make sure you thoroughly test everything before sending a PR.

Sorry, I forgot to stage the exception file for the commit. I've just committed it now.

Thanks!


Can't connect?

Hello!
I'm looking to set my Neewer 660 Pro and 176 RGB lights up for using with my Twitch stream. I've been having trouble getting the software to work so I thought I'd check for help here.

If I open up the Windows Bluetooth settings and scan for a device, I'm able to see both the lights and connect to them through Windows.
If I run 'bleakdiscover.py', I can see the MAC addresses of both the lights.
However, NeewerLite-Python (UI or through the command line) won't see the lights and I have been unable to connect to them. I've tried all the troubleshooting steps I can think of, including disconnecting my phone from the lights, changing the channels, turning off/on and changing channels etc.
I was only able to see the 660 Pro one time when trying to get it to work, but was unable to link to it, and have been unable to see it since then.

I've tried a few older versions of the app and nothing's worked.
Let me know if you guys have any ideas! Would be great to get this working but I'm struggling to find a solution!

Hi @hezmoz!  Hmm, interesting - ha, one possibility would to just get a stronger Bluetooth adaptor, but that's a bit of a lazy answer 😊  I'm wondering - in both Windows and the bleakdiscover.py methods, do the lights return their actual names each time?  -74dBm is a fairly low Bluetooth signal, kind of on the fringe, but should theoretically still work...  NeewerLite-Python scans the devices that Bleak finds and only adds them to the list if the name comes up as "NEEWER-" something (so it doesn't grab a bunch of random Bluetooth devices that aren't lights) so it may be possible that it can see the lights, but the signal isn't strong enough to broadcast the name information?  Just brainstorming here - what kind of setup are you using at the moment, dongle, or on-board Bluetooth, and how far away are the lights from the system that's connecting to them?

Hi @hezmoz! Hmm, interesting - ha, one possibility would to just get a stronger Bluetooth adaptor, but that's a bit of a lazy answer 😊 I'm wondering - in both Windows and the bleakdiscover.py methods, do the lights return their actual names each time? -74dBm is a fairly low Bluetooth signal, kind of on the fringe, but should theoretically still work... NeewerLite-Python scans the devices that Bleak finds and only adds them to the list if the name comes up as "NEEWER-" something (so it doesn't grab a bunch of random Bluetooth devices that aren't lights) so it may be possible that it can see the lights, but the signal isn't strong enough to broadcast the name information? Just brainstorming here - what kind of setup are you using at the moment, dongle, or on-board Bluetooth, and how far away are the lights from the system that's connecting to them?

Hey @taburineagle  thanks for the reply and your wonderful work!
Using a TP Link UB400 adapter in the front of my PC - doesn't seem to be a range issue as I've tried from all angles, literally right next to the transmitter etc and didn't get anything. Have tried multiple ports, usb cable extenders etc.
It's worth noting that when Bleak finds the devices, I just see the MAC addresses and no mention of NEEWER.

That's the MAC addresses and both lights will appear like that, but do not appear when I try to control them through the software.
If I'm looking at changing my Bluetooth adapter, is there a "known good" one I can grab on Amazon Japan?

  And thanks for saying so! 😊
Ha!  That's even weirder, because that's the same dongle I'm using!  I've been looking into getting a stronger one myself, but haven't found one I like yet.  Even more strange, when I run the bleakdiscover.py script, this is the result I'm getting:

This has me really curious now 😄  Which versions of Python and Bleak are you using?

@taburineagle yeah really weird... Completely new to all this, I installed bleak and pyhton yesterday with no previous experience.
Python 3.10.2
Pyhton 3 3.9.10
Bleak 1.1.1

Maybe a reinstall will fix things?

Possibly... hmm, that's also strange, as I have the same exact Python and Bleak versions too - my bleak-winrt version is 1.1.0 though, that's the only difference.  I wonder if there might be a permission set somewhere that's affecting it - most likely not, but it's not out of the question.

@taburineagle Really weird. Just re-installed everything and didn't fix anything. I did actually see the 660 Pro show up on the list one time when I was running bleakdiscover.py but then scanned again and it didn't show up. Really not sure what I'm doing wrong!

Update... was able to briefly see the light appear with the correct name again after scanning multiple times, but it only did it twice before is disappeared again and went back to show the MAC without any useful information.

so clearly it is working, it just looks like bleak isn't able to consistently pull up the name with the light when it finds the MAC address. @taburineagle is there some time of tweak I can do to force the application to ignore the check for a light containing "Neweer"? As I know the two MAC addresses of the light, can try to force it to identify them as the correct lights and run anyway?

Hello again @hezmoz!  OK, I pushed a new commit that adds capabilities for whitelisted MAC addresses.  To use this, create a text document called NeewerLite-Python.prefs in the same path as NeewerLite-Python with this line added, spelled exactly like this:
whiteListedMACs=
and then the MAC addresses you want to whitelist after that, separated with semicolons - for example,
whiteListedMACs=AA:BB:CC:DD:EE:FF;GG:HH:II:JJ:KK:LL;11:22:33:44:55:66, etc.
Make sure the file is called NeewerLite-Python.prefs, not NeewerLite-Python.prefs.txt, save it, and try launching NeewerLite-Python again.  If a MAC address of a device matches the MAC address you added to the list, NeewerLite-Python will add it regardless of whether it says "NEEWER" or not -

Although for the ones that don't specify a name, there may be other errors that come up.  Hopefully this helps!

Thank you thank you THANK YOU @taburineagle for the new commit, absolute legend, that worked perfectly and both lights are now Sync'd up, albiet without names. Fantastic stuff!!

Ah, excellent, excellent - glad to hear it's working out @hezmoz!  You could go into the Light Preferences for each light and give them custom names individually if you'd like - that's still so bizarre that the names aren't showing up!

Hello @hezmoz!  I'm going to close this for now as it's (hopefully) been resolved for a while.


Delete .nvmrc

Summary
Tiny PR that removes an old orphaned .nvmrc file (added in 2018 and not touched since then).
Most likely the project does not work with Node.js 8.11.3 anymore. There is (no longer) a need to attempt to strictly enforce a specific version client-side. package.json already declares
"node": ">=12"

in the engines section, so we should be good.
Changelog
[General] [Removed] - Delete .nvmrc
Test Plan
Nothing to test...

Pacifying pull-bot takes longer than the actual PR... 🙄 🤣

Pacifying pull-bot takes longer than the actual PR... 🙄 🤣


[BC-Breaking] Relax dtype for MVDR

Allow users to use torch.cfloat dtype input for MVDR module. It internally convert the spectrogram into torch.cdouble and output the tensor with the original dtype of the spectrogram.

LGTM.
This looks like backward-compatible to me as cdouble will keep working. Can you double check?

Sure. The auto_grad test passed on my local machine. The reason why it failed last time is that I hard coded the output to cfloat.
I will merge after the unit tests finish and pass.


Make it so some kind of widgets can be used in the header instead

Description
Basically at the moment the docker module / integration is only displayed as a button in the sidebar.
1 - We could turn it into a Widget that would do the same thing as it currently does but form the main page directly.
2 - We could do the opposite and allow for other widgets to be turned into full page widgets like the Torrent widget or the Usenet widget for example.
Personally I think we should go with 1. It takes more space on the main page tho. 🤔
Please tick the boxes

[X] You've read the docs
[X] You've checked for duplicate issues

Hi I think we should use the second to free some space on the main page for futures widgets.
I also think we should move the date / time widget to nav bar

I disagree. I think that this feature is not needed. Plex & Jellyfin widget, many bugfixes, more customization seem to be much more wanted.
I also think that such a feature would add many edge cases which would barely be used by the average user.
Sure, there'll always be a few power users who want a certain feature, but we just can't waste our time on small things.

You can at least leave the docker widget as is?

Sure. Perhaps we could add a new Docker widget though, which reuses some components?

Big dreams

I really like the idea of having the weather in the top nav bar. Lots of empty space there.


chore: update @vueuse/head 1.0.25

When using useHead in components that use <KeepAlive >, useHead works even after the page is disabled (onDeactivated).
A recent update of the dependency @vueuse/head fixes this problem.
🔗 Linked issue
https://github.com/unjs/unhead/pull/92
https://github.com/elk-zone/elk/issues/197

❓ Type of change

[ ] 📖 Documentation (updates to the documentation or readme)
[x] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

📝 Checklist

[x] I have linked an issue or discussion.
[x] I have updated the documentation accordingly.

The test failed in a strange place, and I'm not quite sure exactly why it failed 🤔

I believe it's a flaky test, not to do with this change.


[BUG] Investigate regexp failures with unicode input

Describe the bug
Investigate regexp issue discovered during testing https://github.com/NVIDIA/spark-rapids/pull/5450
The following test failed in CI but could not be reproduced locally. The issue appears to be specific to the superscript character ¹.
  test("issue 5450 ci failure") {
    val pattern = Seq("D?")
    val inputs = Seq("\u000E\u0011\u0006h¹TEST\ud720AA")
    assertCpuGpuMatchesRegexpReplace(pattern, inputs)
  }

Steps/Code to reproduce bug
See above.
Expected behavior
Behavior should be consistent between CPU and GPU or we should fall back to CPU.
Environment details (please complete the following information)
Failed in CI.
Additional context
None

This should get fixed by https://github.com/NVIDIA/spark-rapids/pull/5627

Fixed with https://github.com/NVIDIA/spark-rapids/pull/5776


Update database.py to support server defaults and avoid implicit IO

Follows the guidance from here to support server defaults and avoid unexpected async IO that can be caused when sqlalchemy attempts to refresh an expired property on access outside of an await.
These settings place greater emphasis on explicit use of refresh which makes more sense in applications focused on carefully managing their IO and blocking

Follows the guidance from here to support server defaults and avoid unexpected async IO that can be caused when sqlalchemy attempts to refresh an expired property on access outside of an await.
These settings place greater emphasis on explicit use of refresh which makes more sense in applications focused on carefully managing their IO and blocking

Brilliant! Thank you for this.


docs: ios shortcut

I made an iOS shortcut to share URLs between machines. It makes them clickable to open the url 👍 I saw there was only a fileshare iOS Shortcut in the docs (which is also done by executing curl using another app!) so I thought I'd share this one, which is much simpler and also does URLs.

Oops, I let prettier fix all the spacings on this docs page.  (Un)Fixed.


[BugFix]keep connector/catalog map in consistent as much as possible (backport #46995)

Why I'm doing:
What I'm doing:
Fixes #issue
cp #46995
What type of PR is this:

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

[x] This is a backport pr

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[x] 3.3
[ ] 3.2
[x] 3.1
[ ] 3.0
[ ] 2.5

https://github.com/Mergifyio backport branch-3.3

https://github.com/Mergifyio backport branch-3.1


Unit Tests for Sync and Async callable callbacks in ExecutionCall.callable constructor

I've implemented the following unit test which fails as the callback to the guard only works with a non-future callback.
I think we have a fundamental problem in that we have a method which we are trying to use for both async and sync callbacks.
From this thread:
https://github.com/dart-lang/language/issues/2033
Irhn - one of the dart language devs states:

There is no idiomatic way to return a potentially synchronous/potentially asynchronous result because you should never do that.
...
Providing a way to have the same code act as both synchronous and asynchronous is not just not a goal, it's something I'd try to actively discourage.

This would appear in line with darts idiomatic style of having methods such as 'readLine' and 'readLineSync'.
DCli takes an reversed naming convention as it was originally trying to provide a mostly pure sync API and uses xxx and xxxAsync.  We can argue whether reversing this was a good idea but the point is the need for two methods.
So I believe the way forward is to have a sync and an async version of the guard method.
NamedLock.guard - returns a future and takes a future callback
NamedLock.guardSync - returns a non-future and takes a non-future callback.

I will submit a PR along these lines and then we can discuss further :)
import 'dart:async';

import 'package:runtime_named_locks/runtime_named_locks.dart'
    show ExecutionCall, NamedLock;
import 'package:test/test.dart';

class IntentionalTestException implements Exception {
  final String message;
  IntentionalTestException(
      {String this.message = "Intentional test exception message."});
  @override
  String toString() => message;
}

void main() {
  test('check guard implements async callbacks correctly', () async {
    final results = <String>[];

    final execution = ExecutionCall<FutureOr<void>, IntentionalTestException>(
      callable: () async {
        results.add('line 1');
        await Future.delayed(Duration(milliseconds: 100), () {
          results.add('line 2');
        });
      },
      safe: true,
    );

    final call = await NamedLock.guard<void, IntentionalTestException>(
        name: 'async test', execution: execution);

    await call.completer;

    results.add('line 3');

    await Future.delayed(Duration(milliseconds: 500));

    expect(results.length, 3);
    expect(results[0], 'line 1');
    expect(results[1], 'line 2');
    expect(results[2], 'line 3');
  });
}


Add post-upgrade command for Renovate

Perform the same steps as a pre-commit by running
npm ci and npm run test.
Change-type: patch
Signed-off-by: Kyle Harding<EMAIL_ADDRESS>

@balena-ci I self-certify!


Updates telemetry dependency to 1.0

Thanks for open-sourcing this! Let me know if there are any requested changes or blockers on this PR.

Thanks!


Disable LTO for host (plugin, build script) builds

When building host code, -C prefer-dynamic is passed, but that option
is mutually exclusive with -C lto. Thus when LTO is specified, rustc
errors out.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @wycats (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

Could you add a test for this as well?

Here's a test. Travis failure doesn't seem related.

@bors: r+ a79c7ea
Thanks!

:hourglass: Testing commit a79c7ea with merge 98e4872...

:sunny: Test successful - cargo-linux-32, cargo-linux-64, cargo-mac-32, cargo-mac-64, cargo-win-32, cargo-win-64

Thanks :)


Fix: expect-expect edge cases

Problem

Explicit any is used in Typescript implementation (Not recommended)
Numerous edge-cases where implementation would give potentially false results due to not using the recursive algorithm pattern.

Solution

This fix removes explicit any types since it defeats the purpose of using Typescript.
Added error handling for the edge cases
Added tests cases of possible valid and invalid code snippets that would affect the accuracy of this rule.

ruleTester.run("expect-expect", rule, {
    valid: [
        // ...originalTestCases,
        // Chained expect
        `test("foo", async t => {
            await t
                .click(button)
                .expect(foo)
                .eql(bar)
        })`,
        // More than 1 function on t
        `test("foo", async t => {
            await t.click(button)
            await t.expect(foo).eql(bar)
        })`,
        // Multiple expects
        `test("foo", async t => {
            await t.click(button)
            await t.expect(foo).eql(bar)
            await t.expect(true).ok()
        })`,
        // chained function with callback parameter
        `test.before(async t => {
            await t.useRole(adminRole).wait(1000);
        })("foo", async t => {
            await t.click(button);
            await t.expect(foo).eql(bar);
        })`,
        // Multiple tests
        `fixture("My Fixture")
            .page("https://example.com");

        test("test1", async t => {
            await t.useRole(adminRole);
            await t.expect(foo).eql(bar);
        });
        test("test2", async t => {
            await t.click(button);
            await t.expect(foo).eql(bar);
        });`
    ],
    invalid: [
        // ...originalTestCases,
        {
            code: `test.before(async t => {
                await t.useRole(adminRole).wait(1000);
                await t.expect(Login).ok();
            })("foo", async t => {
                await t.click(button);
            })`,
            errors: [{ messageId: "missingExpect" }]
        },
        {
            code: `test("foo", async t => {
                await t
                    .useRole(adminRole)
                    .click(button)
                    .wait(1000)
            })`,
            errors: [{ messageId: "missingExpect" }]
        },
        {
            // Missing one expect across 2 tests
            code: `fixture("My Fixture")
                .page("https://example.com");

            test("test1", async t => {
                await t.useRole(adminRole).wait(500);
                await t.expect(foo).eql(bar);
            });

            test("test2", async t => {
                await t.click(button);
            });`,
            errors: [{ messageId: "missingExpect" }]
        }
    ]
});

Discussion
In order to have this PR pass all testing results, I resorted to lowering the jest acceptance thresholds for coverage testing.  IMO, 100% thresholds across the code is unreasonable even though I saw you previously were able to obtain it.  I maintained the 100% of all functions called which I think is relevant but each branch/line/statement is a bit difficult (reasoning below).
Specifically to this rule expect-expect, and the way it backs up the function call stack to find if it is within the test() scope is heavily reliant on the eslint implementation of CallExpression hooks.  The error handling added to appease the Typescript compiler causes these valid edge cases that are difficult to simulate given this plugin's implementation.  I think the error handling is necessary within the plugin because if eslint changes its
interpretation of syntax or a user provides something weird/unexpected
this plugin will not immediately cause cause eslint to crash.
As I know coverage testing thresholds are important to some developers, I also added an explicit call out for the expect-expect.ts rule and the current state of acceptable non tested lines/statements to encourage re-evaluation if this changes in the future. However, the global configuration thresholds will have to remain at a lower level, I chose 90%.
My last argument for allowing a lower threshold is that given this plugin is intended to be a community of contributions to rules, it would help to lower the barrier to entry (knowledge/skill) since there is the likelihood there will be more rules that have the same problem as this one.  Unless you can make an implementation that somehow bypasses eslint & the createRule() of the default export.

@codejedi365 thank you for this detailed and well crafted PR. Everything looks good to me but the coverage days it's actually at 74%...

Everything looks good to me but the coverage days it's actually at 74%...

@benmonro, good catch. However that was due to a Typescript error that caused an entire test file not to compile therefore no coverage determined.  After this rebase onto the more up-to-date next branch, coverage was bumped back up to the 90's.


Border between menu and content should have transparency

Ionic version:  (check one with "x")
(For Ionic 1.x issues, please use https://github.com/ionic-team/ionic-v1)
[ ] 2.x
[ ] 3.x
[x] 4.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
After discussion with @bensperry, the border between menu and content for MD mode should have transparency:

It should be black (or super dark) but with opacity to get it close to the same color as the solid one in there now.

Here is the value that the item border color should use in order to show a transparent border that still shows up as #dedede
1px solid rgba(var(--ion-item-md-border-color-rgb, var(--ion-item-border-color-rgb, 0, 0, 0)), var(--ion-alpha-md-border-medium, var(--ion-alpha-border-medium, 0.13)))

We don't have an alpha variable with the value of 0.13 though, so these are the current options:

Variable
Opacity
Rendered Color

$alpha-border-low
.1
#e5e5e5

$alpha-border-medium
.2
#cccccc


Improve formating of data provided to Weekly View details

If the tasks are available under local cache, show the task name instead of ID.
Show Day of weeks rather than August 31.. ->

Almost done. We just have to check the scenarion when task is closed hence not available on client side. @yohangz can u check that scenario.

Curretnly Id of the issue is shown.


Fix InvalidTokenTest and update the licence year for the 2 affected tests

This PR completes the #164 PR.
Fixes #135

@radcortez, Hi Roberto, I've run Quarkus TCK with this update and I'm pretty sure it is all good now, this test's invalid issue test was failing because it was relying before on the issuer property set in those mciroprofile properties. Also updated the license year of the updated tests.
CC @rdebusscher

Looks good. Let me try to run this in SmallRye too.
We can now run the TCK there as well :)
https://github.com/smallrye/smallrye-jwt/pull/200

@radcortez Cool, thanks a million

I think there are other tests that we need to explicitly add the microprofile config file (because they were relying on the default location):

ClaimValueInjectionTest
JsonValueInjectionTest
PrimitiveInjectionTest
ProviderInjectionTest
RequiredClaimsTest
RolesAllowedTest

I can do that.

@radcortez I did verify that on the jwe branch, then switched and copied the wrong code, but I'm 100% verified the Quarkus build...

Sure. I've just found it by running in my local TCK branch :)

@radcortez Cool, let me complete it then, thanks for offering to help

@radcortez Figured out how I ended up copying that wrong code, I forgot to rebase and assumed it was already correct when copying from PublickeyAsPEMTest, glad you have checked :-)

Cool :)

@radcortez I've cleaned it up and also removed few unused properties, double check please when you have some time :-)
Rudy @rdebusscher - any concerns, ping us please

Hum... I'm getting a 401 running the tests now.
Shouldn't microprofile-config-publickey.properties have the content of publicly.pem in mp.jwt.verify.publickey? It doesn't seem to match.
The tests use the default privateKey.pem to sign the token.

And we missed PrincipalInjectionTest.

@radcortez I'll investigate a bit later, it probably means that those tests did not need those properties then. I'll start from scratch...Thanks

Yes, I thought about that as well, but if we had the microprofile-config.properties before, it should have been using that by default.
If you look into Wildfly TCK they do setup a microprofile-config.properties if there is none:
https://github.com/wildfly/wildfly/blob/9160a2ca507b909b818ccc128291a5468b83b11a/testsuite/integration/microprofile-tck/jwt/src/test/java/org/wildfly/extension/microprofile/jwt/test/DeploymentProcessor.java#L43
And the file has the publickKey-pem:
https://github.com/wildfly/wildfly/blob/9160a2ca507b909b818ccc128291a5468b83b11a/testsuite/integration/microprofile-tck/jwt/src/test/resources/META-INF/microprofile-config-local.properties
I did the same for SmallRye JWT TCK.

Hi @radcortez I suspect these TCK tests are not actually set up properly and we have opened something bigger here :-).  While I was off on a walk (now I know why I have a terrible headache :-)) I realized that sll of these tests already add publicKey.pem and TCK Readme does say that this microprofile-config.properties (now renamed to microprofile-config-publickey.properties) is only for the config tests. But TCK META-INF folder also has a microprofile-config-location.properties or something like that and it is really that file which should be used here.
I'll have a look tomorrow, I'll likely close this PR and restart afresh.
Thanks for your feedback, cheers

@sberyozkin I think I got it.
These tests are from MP 1.0, when we didn't have MP Config integration yet and keys and other configurations were provided by vendor specific ways. So the tests didn't have a way to provide the configuration.
When we introduced the MP Config integration, some tests started to use microprofile-config.properties, but the vendor specific way will always have priority over that, so even if the microprofile-config.properties was not right for the test, the previous configuration from the vendor would take over and pass the TCK (if they were already passing it for 1.0).
Does this make sense? I think we can change these tests to provide the right configuration and not rely on vendors to provide their way (or projects supplying their own microprofile-config.properties, like Wildfly or Quarkus).

Hi @radcortez
That is very helpful, so yeah, I've just updated the branch locally and confirmed with the smallrye-jwt tck (I still can't suppress a happy smile the project finally has it :-), it won't guarantee in itself the integrators are compliant but it does offer a robust first barrier check), by commenting out the existing microprofile-config.properties there, that having the proper configuration shipped with the TCK itself, all works. So the implementers won't have to create local properties.
PR update follows shortly.
CC @rdebusscher, others

Cool :)

@radcortez Done. I've introduced META-INF/microprofile-config-publickey-location.properties and removed META-INF/microprofile-config-location.properties because it was not referenced in README, not used anywhere in TCK and had an issuer property mistyped, so pretty sure it can go...
Verified with smallrye-jwt that it works with the project specific microprofile-config.properties or without it - please verify independently.
Note I'm going to open another issue to update the optional tests too as well as fix the full tck suite file as it contains a fraction of the base tests only
CC @radcortez

Thanks! I'll have a look.

I've also tested with SmallRye and it does work with the base tests.

@radcortez Thanks, going to go ahead with the merge shortly


New Wiggle Supported?

Does this work for the new skill check wiggle or the spamming one? I can use either, right now it's easier for me to use the new one

I don't much understand you, but it works well for the newest game version. and the answer is the new one.


[BUG]

I try to groupify a SharePoint site by an Azure function under an managed identity. I can do many actions by a managed identity like create a new site, provision a pnp template, set theme, add group owners and members. But I cannot groupify a SharePoint team site. I got this error:
2024-07-09T18:46:25Z   [Error]   ERROR: An error occurred while processing this request.

Exception             :
    Type        : System.Management.Automation.PSInvalidOperationException
    ErrorRecord :
        Exception             :
            Type    : System.Management.Automation.ParentContainsErrorRecordException
            Message : An error occurred while processing this request.
            HResult : -2146233087
        CategoryInfo          : InvalidOperation: (:) [], ParentContainsErrorRecordException
        FullyQualifiedErrorId : InvalidOperation
    TargetSite  :
        Name          : ProcessRecord
        DeclaringType : PnP.PowerShell.Commands.Base.PnPConnectedCmdlet
        MemberType    : Method
        Module        : PnP.PowerShell.dll
    Message     : An error occurred while processing this request.
    Source      : PnP.PowerShell
    HResult     : -2146233079
    StackTrace  :
   at PnP.PowerShell.Commands.Base.PnPConnectedCmdlet.ProcessRecord() in c:\build\src\Commands\Base\PnPConnectedCmdlet.cs:line 101
   at PnP.PowerShell.Commands.PnPSharePointCmdlet.ProcessRecord() in c:\build\src\Commands\Base\PnPSharePointCmdlet.cs:line 131
   at System.Management.Automation.Cmdlet.DoProcessRecord()
   at System.Management.Automation.CommandProcessor.ProcessRecord()
CategoryInfo          : InvalidOperation: (:) [Add-PnPMicrosoft365GroupToSite], PSInvalidOperationException
FullyQualifiedErrorId : InvalidOperation,PnP.PowerShell.Commands.Admin.AddMicrosoft365GroupToSite
InvocationInfo        :
    MyCommand        : Add-PnPMicrosoft365GroupToSite
    ScriptLineNumber : 28
    OffsetInLine     : 1
    HistoryId        : 1
    ScriptName       : C:\home\site\wwwroot\ModifyExistingSite\run.ps1
    Line             : Add-PnPMicrosoft365GroupToSite -Url $targetProjectSiteURL -Alias "contosokhha" -DisplayName "contosokhha" -KeepOldHomePage

    PositionMessage  : At C:\home\site\wwwroot\ModifyExistingSite\run.ps1:28 char:1
                       + Add-PnPMicrosoft365GroupToSite -Url $targetProjectSiteURL -Alias "con …
                       + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    PSScriptRoot     : C:\home\site\wwwroot\ModifyExistingSite
    PSCommandPath    : C:\home\site\wwwroot\ModifyExistingSite\run.ps1
    InvocationName   : Add-PnPMicrosoft365GroupToSite
    CommandOrigin    : Internal
ScriptStackTrace      : at <ScriptBlock>, C:\home\site\wwwroot\ModifyExistingSite\run.ps1: line 28

Expected behavior
I expect no errors, and a group based SharePoint site
Steps to reproduce behavior
Connect-PnPOnline -ManagedIdentity -Url "[https://myCompany-admin.sharepoint.com"
Add-PnPMicrosoft365GroupToSite -Url "https://myCompany.sharepoint.com/teams/someNonGroupBasedTeamSite" -Alias "someNonGroupBasedTeamSite" -DisplayName "someNonGroupBasedTeamSite" -KeepOldHomePage
What is the version of the Cmdlet module you are running?
2.5.0
Which operating system/environment are you running PnP PowerShell on?
Azure Functions
I implemented these API permissions on my managed itentity/azure function. Do I miss some API permission?

I can confirm the same issue when connecting with app id and certificate:

When connecting with -Interactive , somehow I get a different error:
Add-PnPMicrosoft365GroupToSite: User does not have permissions to Groupify

Hello, we investigated this.
It is a backend API issue. You need to use delegated permissions for this cmdlet and ensure that you are the site collection admin of the site getting groupified . Application permissions wont work in this case. We can't fix it from PnP PowerShell side as we are consuming SPO endpoints.


Friends patching does not work

Since the old patcher has been deprecated, I'm forced to update to this patcher that never work since the first version. I already reset steam and everything.
log:
[5/15/2022 5:47:44 PM][Info] Parsing cache...
[5/15/2022 5:47:44 PM][Info] Found 0 matches...
[5/15/2022 5:47:44 PM][Info] Scanner started
[5/15/2022 5:47:44 PM][Info] friends.css is already patched.
[5/15/2022 5:49:37 PM][Info] Resetting Steam
[5/15/2022 5:49:37 PM][Info] Shutting down Steam
[5/15/2022 5:49:39 PM][Info] Deleting c:\program files (x86)\steam\steamui\css
[5/15/2022 5:49:39 PM][Info] Deleting C:\Users\micro\AppData\Local\Steam\htmlcache\Cache
[5/15/2022 5:49:39 PM][Info] Starting Steam
[5/15/2022 5:50:17 PM][Info] Parsing cache...
[5/15/2022 5:50:17 PM][Info] Found 0 matches...
[5/15/2022 5:50:17 PM][Info] Parsing cache...
[5/15/2022 5:50:17 PM][Info] Found 0 matches...
[5/15/2022 5:50:17 PM][Info] Parsing cache...
[5/15/2022 5:50:17 PM][Info] Found 0 matches...
[5/15/2022 5:50:17 PM][Info] Parsing cache...
[5/15/2022 5:50:17 PM][Info] Found 0 matches...
[5/15/2022 5:50:17 PM][Info] Parsing cache...
[5/15/2022 5:50:17 PM][Info] Found 0 matches...
[5/15/2022 5:50:17 PM][Info] Parsing cache...
[5/15/2022 5:50:17 PM][Info] Found 0 matches...
[5/15/2022 5:50:17 PM][Info] Parsing cache...
[5/15/2022 5:50:17 PM][Info] Found 0 matches...
[5/15/2022 5:50:17 PM][Info] Parsing cache...
[5/15/2022 5:50:17 PM][Info] Found 0 matches...
[5/15/2022 5:50:17 PM][Info] Parsing cache...
[5/15/2022 5:50:17 PM][Info] Found 0 matches...
[5/15/2022 5:50:17 PM][Info] Parsing cache...
[5/15/2022 5:50:17 PM][Info] Found 0 matches...
[5/15/2022 5:50:17 PM][Info] Parsing cache...
[5/15/2022 5:50:17 PM][Info] Found 0 matches...
[5/15/2022 5:50:32 PM][Info] Parsing cache...
[5/15/2022 5:50:32 PM][Info] Found 0 matches...

this is the log when I use the old patcher (that works):
[5/15/2022 5:57:32 PM] [Info] Downloaded friends.css with etag: "D18GcwC82oVA"
[5/15/2022 5:57:33 PM] [Info] Downloaded friends.css with etag: "D18GcwC82oVA"
[5/15/2022 5:57:33 PM] [Info] Successfully downloaded friends.css files.
[5/15/2022 5:57:33 PM] [Info] Cache Watcher Started.
[5/15/2022 5:57:33 PM] [Info] Cache Watcher Stopped.
[5/15/2022 5:57:33 PM] [Info] Force scan started.
[5/15/2022 5:57:33 PM] [Info] Finding list of possible cache files...
[5/15/2022 5:57:33 PM] [Info] Found 73 possible cache files.
[5/15/2022 5:57:33 PM] [Info] Checking cache files for match...
[5/15/2022 5:57:33 PM] [Info] Successfully found matching friends.css for "D18GcwC82oVA" at C:\Users\micro\AppData\Local\Steam\htmlcache\Cache\f_000012.
[5/15/2022 5:57:33 PM] [Info] Overwriting with patched version...
[5/15/2022 5:57:33 PM] [Info] Reloading friends window...
[5/15/2022 5:57:34 PM] [Info] Done! Put your custom css in c:\program files (x86)\steam\clientui\friends.custom.css
[5/15/2022 5:57:34 PM] [Info] Close and reopen your Steam friends window to see changes.
[5/15/2022 5:57:34 PM] [Info] Cache Watcher Started.

current config:
{
  "userSettings": {
    "roaming": {
      "SFP.Properties.Settings": {
        "CacheDirectory": "C:\\Users\\micro\\AppData\\Local\\Steam\\htmlcache\\Cache",
        "CheckForUpdates": "False",
        "MinimizeToTray": "True",
        "RestartSteamOnPatch": "True",
        "ScanOnly": "False",
        "ShouldPatchFriends": "True",
        "ShouldPatchLibrary": "False",
        "ShouldPatchOnStart": "True",
        "ShouldScanFriends": "True",
        "ShouldScanLibrary": "False",
        "ShouldScanOnStart": "True",
        "ShowTrayIcon": "True",
        "StartMinimized": "True",
        "SteamDirectory": "c:\\program files (x86)\\steam",
        "SteamLaunchArgs": "-silent"
      }
    }
  }
}

Is that log from 0.0.4?
Is the behavior the same with 0.0.3? Or does it crash? Is the log the same in 0.0.3?

I find out that the bug only occurs when SFP start itself before steam startup (due to #5), if I manually start steam and start SFP after that, everything is fine.

Is that log from 0.0.4?

yes

Is the behavior the same with 0.0.3? Or does it crash? Is the log the same in 0.0.3?

yes

EDIT: Also can you try running the program as admin and see if that works? Which version of Windows are you running?
same as admin. Windows 11 (21H2 22000.675)

So just to clarify:
If you start SFP while Steam is not running and then start Steam, once Steam loads and the friends list opens neither the scanner nor the patch button work to patch the friends list until SFP is restarted while Steam is already running?

So just to clarify:
If you start SFP while Steam is not running and then start Steam, once Steam loads and the friends list opens neither the scanner nor the patch button work to patch the friends list until SFP is restarted while Steam is already running?

my friend list isn't set to automatically sign in when steam client starts. If a press patch button it does nothing. if a sign in on friends window it's not patched. if I press patch button after sign in on friends steam is restarted

This issue should be fixed in 0.0.6! :)

Closing this, feel free to reopen if you are still having this problem.


BUG in connection between SignStream Sign Bank and Utterances in the DAI2 Sign Bank

Hi,
I was demoing the latest version of SignStream (v15) yesterday,
and discovered that the connection between the SignStream
Sign Bank lookup and the Web is broken.
Consider, e.g., looking up the occurrences of NEW

Clicking on “view occurrences” brings this up:

Play sign video, and play composite video, bring up correct videos.
But systematically the “view occurrences” command shows the wrong signs.
For example, for REALLY, what comes up is REDUCE.
We had discussed the importance of having unique identifiers for signs
that remain constant with new versions of the Sign Bank…
Not sure if this is the source of the problem.  But the wrong results
seem to be close alphabetically to what is being sought, i.e., it
seems that we’re getting the wrong item from the list, but an item
that is “in the neighborhood”.
THANKS,
Carol

Fixed


[Chore] Update repo to meet some of the cc-open-source github

We can update the repo to meet the creative commons opens source guidelines. I think this might be pure overkill, but it would be a good learning experience :)

[ ] add ./cc-metadata.yml file see
[ ] update pull request template see
[ ] add support resources (?) see

Currently the only "support" available is to create an issue here. We will create a discord room in the future if there is a need.

[ ] update labels in repo to standard, see
[ ] update branch protections

This is the full checklist:
https://opensource.creativecommons.org/contributing-code/github-repo-guidelines/

I'd be happy to jump in on a few of these. 🙂


Add example using pm2 to manage and keep your application online

pm2  is a daemon process manager that will help you manage and keep your application online 24/7.
This can be useful to run node.js applications in production.

I think this info would be better served in the ibmi-oss-docs repo instead.