text:
[HELP WANTED]: Tester(s) and maintainer(s) needed

:no_entry::triangular_flag_on_post: Help wanted :triangular_flag_on_post::no_entry:
As a team we have been unable to maintain communications with the main tester and developer for the USB legacy devices. If you want to help us maintain the USB code by joining (or reaching out to @brefra) contact us through this issue.

@brefra, @CoMPaTech I am using the usb stick on my (production) homeassistant for a few years now. If you can help me how to setup a dev hass instance for development/testing of this module I can help you test/maintain it.

Just to let you know, I'm still around but unfortunately less active and involved as people would like to see. Sorry about that.
A long time ago I already started to (re)write the backend library to kind of resolve most of the current performance issues,  especially for larger setups or when the communication is less stable.
Due to the minimal spare time I have this will take some more time.

@brefra good to hear from you again, glad you are still with us - as life has priority I'd suggest we still leave this open to have another maintainer on the USB side of the project? If you can get in touch with @ArnoutD in the meantime so USB has another tester that would be great.
For those new to our repositories, I'm one of the maintainers but unfortunately have no USB hardware to functionally test, if we have someone able to write proper tests this would make the code better maintainable.

I still using the USB stick, if you like I can help you with testing.

@supermarcie highly welcome on behalf of the community
@brefra I've modified the team/codeowners setup as to limit the amount of notifications/emails (saving precious time on your behalf I hope)

I have quite a big plugwise system. And some experience from OpenHab and other development on plugwise. Could help with testing and coding.

FYI, I am planning to look deeper into the memory issues I am facing (see issue tracker) and data being dropped after some time, but realisticly not before November.

I’m also a user of quite some plugwise circles with the usb stick in home assistant. Would love to help testing not much of a help if it comes to coding a’m afraid.

I think part of the problem is that some of timeout are just too tight for a bigger system (that needs to go over multiple hops)

Hi all - I have a big box of Plugwise sticks, plugs, switches and circles that I have inherited. Unfortunately I haven't been able to get it to run on HA - if there's anything I can do to assist I'd be happy to help, including coding and testing. Afraid there might be some hurdles to get over as I'm no HW dev and - as previously noted - not been able to even get it to run... 😬
If someone has the actual documentation for the legacy products and is able to get it online, that would be a start.

Hi all - I have a big box of Plugwise sticks, plugs, switches and circles that I have inherited. Unfortunately I haven't been able to get it to run on HA - if there's anything I can do to assist I'd be happy to help, including coding and testing. Afraid there might be some hurdles to get over as I'm no HW dev and - as previously noted - not been able to even get it to run... 😬 If someone has the actual documentation for the legacy products and is able to get it online, that would be a start.

Probably you need to start with using the original software and check if the sticks and circles have the latest firmware.

In a nutshell, the main issue I am facing is that the stick gets flooded when there are plugs in the network with spotty connectivity. Basically what starts to happen is that the information requests get repeated (retries) as well as new requests are added to those plugs. As a result the outstanding messages start piling up in the sticks memory which slows down the stick communication, and as a result the reply messages back to the controller get so much delayed that the controller already timed out the messages and starts saying those replies unexpected.
By tuning message_time_out and message_retry constants you can see some improvements, but so far I have not been able to get it working stable. At some point the stick is just congested.
For months now it is my intention to dive into it myself but I am a Python novice and this backend is probably not the easiest to start. I am also wondering about the best approach here. Initially I am thinking that
(a) Somehow it is working out well to mark spotty connected plugs as unreachable. I need to investigate why this is not happening
(b) Somehow we need to mark spotty connected plugs and ratelimit the requests to that stick
(c) Create an overall rate limit messages sent to the stick.
Any ideas and thoughts are welcome.

@brefra, @CoMPaTech I am using the usb stick on my (production) homeassistant for a few years now. If you can help me how to setup a dev hass instance for development/testing of this module I can help you test/maintain it.

It would be best to check this with @brefra though @ArnoutD to ensure everything is aligned between maintainers. As an upcoming post will depict, I'm still willing to help out, but not on actual code.
If you want to test the waters, feel free to clone the repository on a machine with (preferably) python 3.12 (or 3.11 for the module, see both issues #107 here and in the module repo (coincidence that the numbers are equal). It 'should work' when you clone the repo, and just run scripts/setup.sh or  python3.12 -m venv venv followed by setup.sh if you have multiple python versions available. From there you should be able to run scripts/core-testing.sh showing 'all green'. The testing script is also ran by pre-commit so if you git commit it should pick up any problems beforehand.#104
(And apologies for the late reply, but as also depicted in the upcoming post, my focus is not on the code as it's lacking maintenance)

To all following this thread
Just interjecting here that the wheels are still on the bus, but they need some TLC soon (before falling off). I've just (as per upstream) removed black from both USB repositories (i.e. this one and the module one), but as the code was due for quality before and definitely is now I also disabled other quality checks to ensure the process for chore maintenance (i.e. through renovate) still keeps running. This took about 2 hours tonight to get everything going again and I'm not sure next time will be quicker or more work with the stale condition of the actual code.
Be aware though that (testable) compatibility with python 3.12 (module remains at 3.11, the component is run against 3.12) and could become an issue for newer versions of HA.
Also this would be one of the final efforts, besides bumping the build-cache every now and then until we have a new (preferably set of) (additional) maintainer(s) besides @brefra.
I'd still be willing to help out on the quality parts and keeping the wheels greased, but won't be coding as I have no hardware to test it against nor does the code have the appropriate testing in place to be able to virtually ensure functionality.

To all following this thread Just interjecting here that the wheels are still on the bus, but they need some TLC soon (before falling off). I've just (as per upstream) removed black from both USB repositories (i.e. this one and the module one), but as the code was due for quality before and definitely is now I also disabled other quality checks to ensure the process for chore maintenance (i.e. through renovate) still keeps running. This took about 2 hours tonight to get everything going again and I'm not sure next time will be quicker or more work with the stale condition of the actual code.
Be aware though that (testable) compatibility with python 3.12 (module remains at 3.11, the component is run against 3.12) and could become an issue for newer versions of HA. Also this would be one of the final efforts, besides bumping the build-cache every now and then until we have a new (preferably set of) (additional) maintainer(s) besides @brefra. I'd still be willing to help out on the quality parts and keeping the wheels greased, but won't be coding as I have no hardware to test it against nor does the code have the appropriate testing in place to be able to virtually ensure functionality.

I'm happy to support this effort, however I'll need some help getting started because I don't think I understand what any of the above means. I'll start with try the contents of your former message.

@dirixmjm and others

I'm happy to support this effort, however I'll need some help getting started because I don't think I understand what any of the above means. I'll start with try the contents of your former message.

If started a very rough (and not intentionally scary, though it might be) write-up at https://github.com/plugwise/plugwise_usb-beta/discussions/109 not to further dilute this issue.

I might dive into it as well. Thanks for the write-up @CoMPaTech

@ArnoutD

@brefra, @CoMPaTech I am using the usb stick on my (production) homeassistant for a few years now. If you can help me how to setup a dev hass instance for development/testing of this module I can help you test/maintain it.

It would be best to check this with @brefra though @ArnoutD to ensure everything is aligned between maintainers. As an upcoming post will depict, I'm still willing to help out, but not on actual code.
If you want to test the waters, feel free to clone the repository on a machine with (preferably) python 3.12 (or 3.11 for the module, see both issues #107 here and in the module repo (coincidence that the numbers are equal). It 'should work' when you clone the repo, and just run scripts/setup.sh or python3.12 -m venv venv followed by setup.sh if you have multiple python versions available. From there you should be able to run scripts/core-testing.sh showing 'all green'. The testing script is also ran by pre-commit so if you git commit it should pick up any problems beforehand.#104
(And apologies for the late reply, but as also depicted in the upcoming post, my focus is not on the code as it's lacking maintenance)
@CoMPaTech ... I contacted @brefra in september but was waiting for him to publish his asyncio branch not to start with ending up in a merge conflict.... will read through your #109 to get a development environment up and running. My HA instance will start failing after 2023.12 then as well as far as I am now suspecting, so I will look on how to at least make it 2024.01 compatible

@ArnoutD well, the python3.12 thingy was (too) ambitious as we just found out on the 'Smile' side, but eventually Core will drop 3.11. So while premature we might indeed still need to catch up at some point. @dirixmjm is trying his first PR now so that is good news for everyone. As per his https://github.com/brefra personal page there is some activity latest mid October but you might want to DM or ping, maybe there is something to share and to pick up from. Unfortunately we do not have more information than you have at this time (i.e. the September response and status).

I've created a test-version of the plugwise-usb backend with the changes proposed by @dirixmjm.
You can switch to using this test-version by updating the plugwise-usb version in the plugwise_usb-beta custom_component by changing the version-number in the manifest-json file from 0.31.0 to 0.31.1b0.
Save the update and then restart HA Core.
In my case the update does not seem to break anything (yet), all devices are up and I can switch the Circles (8, plus a Stealth M+)
I'll create a separate discussion for sharing your results.

Hi, how can I check if I have te right component?
Not all my devices are online now after the change to 0.31.1b0 and a restart.

I can take a while before all devices are back online, inherent to the Zigbee :)
How can you check: look at the contents of the manifest.json-file after the restart.
If the version of plugwise-usb is still 0.31.1b0 then your good.

Please, let's discuss further here: https://github.com/plugwise/plugwise_usb-beta/discussions/110

Just as a heads-up; Warm welcome to @dirixmjm who joined efforts on Plugwise USB projects (both as maintainer and tester. Welcome to the team!
We'll leave the issue open/up for now for other enthusiasts to join in (either just testing or also becoming a maintainer).

@ArnoutD also joined - with that, the USB project is steaming ahead, should we close this issue for now?

Ok for me.

authors: ArnoutD CoMPaTech Laphroaig79 bouwew brefra danmattsson dirixmjm herwinjan joostwestra mvdwetering supermarcie


text:
🛑 Dick Pluim.com is down

In 511adc6, Dick Pluim.com (https://dickpluim.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Dick Pluim.com is back up in 64881ae after 10 minutes.

source: gharchive/issue

license: MIT

license_type: permissive

license_source: github-api


text:
🛑 KCG is down

In 5aa65e7, KCG (https://kunstrijclubgroningen.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: KCG is back up in 3eadc2b after 10 minutes.


text:
🛑 Pierced Arrows is down

In 7b5ac3d, Pierced Arrows (https://www.piercedarrows.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pierced Arrows is back up in 251047c after 9 minutes.


text:
🛑 Pierced Arrows is down

In 72138a4, Pierced Arrows (https://www.piercedarrows.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pierced Arrows is back up in e7998d8 after 14 minutes.


text:
🛑 Pierced Arrows is down

In 5c5dad1, Pierced Arrows (https://www.piercedarrows.nl) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Pierced Arrows is back up in e87e0bd after 18 minutes.


text:
(bug) Conform check operators fail to run

alignment_base_replay(default) and alignment_base_replay fail to run.
I'm not sure that the problem is from my workflow or it's from the operators.
The log is
knime.log
The screenshot is

This is the workflow
alignment_base_replay.zip

Thanks for the report with data, I will have a look at it.

fixed the bugs now.

authors: FrankBGao KFDing


text:
Uncaught TypeError: Cannot read property 'attachEvent' of null in just-the-docs.js

Just happened now. On Chrome, when I run my website using this template, the layout is quite strange and it shows an error in the console of
Uncaught TypeError: Cannot read property 'attachEvent' of null
    at Object.jtd.addEvent (just-the-docs.js:6)
    at initNav (just-the-docs.js:40)
    at HTMLDocument.<anonymous> (just-the-docs.js:439)

You can check the website here https://fmm-wiki.github.io/docs/installation/

Is there some changes just made by the official template?

I change the remote theme back to version 0.2.7, now the layout becomes normal. However, the search field does not work and it still shows the same error caused by just-the-docs.js.

Hi @cyang-kth
You have copied https://github.com/fmm-wiki/fmm-wiki.github.io/blob/master/_layouts/default.html.
This file is provided by the theme, please delete it or incorporate the changes made in just-the-docs.

Thanks for this information.

authors: SgtSilvio cyang-kth

repo: pmarsceill/just-the-docs


text:
🛑 Hacker News is down

In 928f679, Hacker News (https://news.ycombinator.com) was down:

HTTP code: 502
Response time: 246 ms

Resolved: Hacker News is back up in 75c7079 after 8 minutes.


text:
Fail build on score threshold

Allow for the user to set a score failure threshold that will trigger the build to fail if breached.

 Fail build on score threshold

repo: pmckeown/dependency-track-maven-plugin


text:
Thank god for this, you saved me

I can't figure out how to say thank you except to file this and say you just saved me after 2 days of wasted broken installs and deps on an A100.

Thank god for this

Well, you could thank me instead :stuck_out_tongue: Jokes aside, thanks for posting this. It means a lot. I'm glad that this project helped you out.
If you find the time, could you tell me how your envs were broken before? While working on #73, I figured that detecting broken envs would also be good addition for this tools. In the future we might even have ltt fix to fix the env automatically. But all of this depends on correctly detecting broken envs and the reason why they are broken in the first place.
Plus, did you encounter any issues with light-the-torch? Was the usage clear just from the README?

My only request would be to add torchvision (and maybe torchaudio) as extra possible installs along with? I held my breath when I added it but it worked ok.

Most PyTorch distributions, including torchvision and torchaudio are already supported. There is no public list, but I'm periodically monitoring their indices to check if we are missing something.
https://github.com/pmeier/light-the-torch/blob/eda21f3d1398e0551546f6fde0e79f309de0951d/light_the_torch/_patch.py#L38-L50
If something breaks, feel free to reach out.

My nvidia-smi said one thing about cuda (11.6), my nvcc -V said another

That is indeed very confusing and I fell for it myself in the beginning. nvcc reports the version of the CUDA toolkit you have installed, while nvidia-smi reports the version up to which compiled CUDA code is supported on your machine. So in your case, you can use everything with CUDA<=11.7, which I believe is everything PyTorch hosts at the moment.
Plus, unless you actually want to compile CUDA code, e.g. building PyTorch from source, you don't need the CUDA toolkit installed on your system at all. PyTorch ships everything you need at runtime inside the wheels. This is why they are so large. You only need to have the driver installed.
TL;DR if you ever have to install wheels manually again, trust nvidia-smi.

authors: arnicas pmeier

repo: pmeier/light-the-torch


text:
🛑 Fish of Westminister is down

In b524d7a, Fish of Westminister (https://fishofwestminster.org/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Fish of Westminister is back up in 4c0db90 after 5 minutes.

repo: pmjustin/pmuptime


text:
useDrag: Setting bounds breaks swipe behavior

Describe the bug
The swipe parameter in the callback is always [0, 0] if bounds are reached. The problem is conceptual (see Details below) and applies everywhere (it's not a technical/cross-platform issue but a logical issue).
Sandbox or Video
Here's a fork of the cards gallery example, only a bit modified: bounds were added (0 all around).
Result: You can no longer swipe to other cards
Expected result: Swipe should still work, just like on the blue square in the docs (on the swipe section).
Information:

all browsers/devices, see sandbox for versions (same as examples)

Checklist:

[x] I've read the documentation.
[x] If this is an issue with drag, I've tried setting touch-action: none to the draggable element.

Details:
The docs for swipe state:
Here are the conditions for a swipe to be detected on the x axis:

The drag gesture is over.
The drag gesture didn't last more than 220ms.
movement[0] is superior to the swipe.distance[0] option.
velocity[0] is superior to the swipe.velocity[0] option.

The problem is, whenever any bounds are being reached, the movement in that direction will be 0 on subsequent swipes in that direction, thus invalidating any swipe logic. Also, since movement is 0 then so is velocity, which is being used in the sandbox example and also breaks down when bounds are used.
My sandbox which breaks the example is a bit pointless, but it was just the fastest i could do to prove the bug. In my use case i'm implementing a swipe-able photo gallery with pinch zoom on every picture. While zoomed in i can drag the picture around but i need to put bounds so that i can't drag the photo off-screen. Problem is once i set bounds, i can't swipe between pictures any more (unless the photo is zoomed in and in the middle somewhere so that no bound is encountered).
I think the movement/velocity (and swipe!) should be computed before bounds, and then reset afterwards to their current behavior if bounds were met (only reset movement/velocity, but keeping the computed swipe). What do you think?
One workaround is to not set bounds option, but compute and enforce bounds in the drag gesture callback (this is what the docs on swipe do basically, as they ignore the drag offset so it's equivalent to bounds set to 0 all around). Problem is if bounds aren't static then computation quickly adds up and performance may get a hit (didn't actually profile it but that's the direction it's headed).
Another workaround is to raise the swipe behavior to the container element (where there are no bounds but also nothing gets moved so it's like on the docs page with that square), but that might complicate other parts of the code - in my case resetting the zoom on the picture that flies off the screen on navigation.
However, i think the ideal case would be if swipe still works even when bounds are reached. What do you think?

Hi @dbismut , thank you for the quick fix! It works very well, as you can see here: https://codesandbox.io/s/gesture-drag-forked-vycd92?file=/src/App.jsx - btw i like that i could fork the example with code from the branch so i could test it out, really nice touch!
I'll be waiting for the release then :) thanks again, and have a nice day!

Released 10.2.26!

authors: dbismut steodor

repo: pmndrs/use-gesture


text:
fix(react): a workaround for missing named exports

close #572

FWIW, this seems to cause issues when substituting preact/hooks for react, as preact/hooks has no default export:
The requested module 'preact/hooks' does not provide an export named 'default'

That's really unsolvable from the library perspective. We hope React provides ESM, and meanwhile Preact provides CJS with default everything.

source: gharchive/pull-request

authors: dai-shi nornagon

repo: pmndrs/valtio


text:
docs: code miss in react three fiber tutorial

Hi, Thank you for the react three fiber tutorial.
I found one mistake on loading textures page.
https://docs.pmnd.rs/react-three-fiber/getting-started/loading-textures
incorrect: <sphereGeometry args={[1, 100, 100]} map={colorMap} />
correct: <meshStandardMaterial  map={colorMap} />

Thanks for investigating. Fixed with #135.

repo: pmndrs/website


text:
New command: create custom AAD app for use with the CLI

Usage
cli app add
Description
Creates custom Azure AD app for use by CLI for Microsoft 365
Options

Option
Description

-m, --mode <mode>
Determines if CLI will be used by a user (delegated) or as a deamon process (appOnly). Allowed values delegated,appOnly

-p, --permissions [permissions]
List of permissions to assign to the app. If not specified, will assign all permissions currently used by CLI for Microsoft 365. For the actual list see https://pnp.github.io/cli-microsoft365/concepts/authorization-tokens/#azure-ad-application-used-by-the-cli-for-microsoft-365. Use permissions or permissionSet but not both

--permissionSet [permissionSet]
Predefined set of permissions to assign to the app. Allowed values ReadAll, SpoFull, SpoRead. Use permissions or permissionSet but not both

Additional Information

the AAD app will be created in the current directory
the AAD app will be created using the Azure CLI Azure AD app
the created AAD app will be single-tenant
when configuring permissions, CLI automatically chooses the permissions to be granted based on the selected mode
when mode selected to app-only, automatically generates a certificate valid for a year
later, when we support persisting configuration #1945, running this command should update the config with the ID of the newly created app
returns the Azure AD app ID and, if the selected mode was daemon, the thumbprint, password and expiration date of the generated cert

@pnp/cli-for-microsoft-365-maintainers I'd love your feedback. In particular, I'd appreciate if you thought about:

is this spec oversimplified and are we missing some cases?
are user and deamon clear enough or do we use different names to denote the different usage modes
is it correct to assume that in app-only mode folks will be okay with using a secret or should we use a certificate instead? If cert, why and what expiration period should we choose?

Great suggestion! 👏 Some of my thoughts...

is this spec oversimplified and are we missing some cases?

I don't think it needs to be anymore than what it is.

are user and deamon clear enough or do we use different names to denote the different usage modes

I would prefer delegate and app, as this then makes it clear what type of permissions will be added, this is also what the Azure Portal refers to them as.

is it correct to assume that in app-only mode folks will be okay with using a secret or should we use a certificate instead? If cert, why and what expiration period should we choose?

Thinking from a best practice perspective, certificate is more secure than providing a password or secret, so I think we should promote this as such. See below statement on the Certificate & Secrets blade in the Azure Portal.
Credentials enable confidential applications to identify themselves to the authentication service when receiving tokens at a web addressable location (using an HTTPS scheme). For a higher level of assurance, we recommend using a certificate (instead of a client secret) as a credential.

Microsoft have provided some guidance on the validity period of certificates based on length in the past (https://techcommunity.microsoft.com/t5/configuration-manager-archive/recommendations-for-pki-key-lengths-and-validity-periods-with/ba-p/272758).
Key length of 1024:  Validity period = not greater than 6-12 months
Key length of 2048:  Validity period = not greater than 2 years
Key length of 4096:  Validity period = not greater than 16 years

I think that one year would be a good starting point, coincidentally when creating a secret in the Azure Portal the validity period defaults to one year also.

Hi,
agree with @garrytrinder regarding delegated and app mode. I would extend the permissions concept by letting the use specify the service he/she wants to enable.
For example:

ReadWrite.All (enables all permissions of the CLI)
Read.All (enables all permissions of the CLI for read operations
ReadWrite.SPO (enables all read and write SPO permissions)
Read.SPO (enables all read SPO permissions

etc.
Not sure if we should have a separate parameter for this.
As return type I would also return the Azure AD Url to the app.
br,
Patrick

For example:

ReadWrite.All (enables all permissions of the CLI)

Read.All (enables all permissions of the CLI for read operations

ReadWrite.SPO (enables all read and write SPO permissions)

Read.SPO (enables all read SPO permissions

Love this, great idea 👏🏻

Thanks for your thoughts gents! Here are some thoughts:

I would prefer delegate and app, as this then makes it clear what type of permissions will be added, this is also what the Azure Portal refers to them as.

How about delegated and app-only? mode: delegate sounds weird and mode: app isn't quite self-explanatory.
I like the suggestion to use a cert instead of a secret. I thought first of using a secret, because it doesn't expire. Since there is no reminder on expiring certs, admins are often getting surprised when things stop working. If we were to use a cert, then we should return the expiration date of the generated cert.
As for permissions: there is something to say for using permission sets that you mentioned, but I would still allow users to specify their own permissions as listed in AAD. So perhaps these sets could be exposed in a separate option named --permissionSet? To make it clear that these are made up permissions, I'd also suggest using different names like ReadAll, SpoFull, SpoRead. I don't need if we need Full as that's the default setting.

How about delegated and app-only? mode: delegate sounds weird and mode: app isn't quite self-explanatory.

Works for me 👍🏻

If we were to use a cert, then we should return the expiration date of the generated cert.

Agreed.

So perhaps these sets could be exposed in a separate option named --permissionSet? To make it clear that these are made up permissions, I'd also suggest using different names like ReadAll, SpoFull, SpoRead. I don't need if we need Full as that's the default setting.

Agreed, I like the idea of permission sets.

Updated spec

Ship it 😊

Actually, can we change app-only to appOnly, removing the -?
Like you said in another issue, we don't use them in option names so using them in values doesn't seem right.

Spec updated. Is it ready to go?

Ship it (again) :slightly_smiling_face: :rocket:

Hi, if this idea/task is still valid then I would like to take care of it :)

Looks still valid to me, thanks! 👍

One comment from my side which we already talked about internally is that we could reuse a lot of code from the app add command się we may move some to utils methods.
Also we could wait a bit for that improvement
https://github.com/pnp/cli-microsoft365/issues/5870
Pointed out by @martinlingstuyl. Currently this is the last thing not covered yet

Also we could wait a bit for that improvement #5870 Pointed out by @martinlingstuyl. Currently this is the last thing not covered yet
Since we don't call sub-commands anymore, this issue doesn't really matter, does it?

Also we could wait a bit for that improvement #5870 Pointed out by @martinlingstuyl. Currently this is the last thing not covered yet
Since we don't call sub-commands anymore, this issue doesn't really matter, does it?

I think I wrote that one comment above 😉

so if I understand correctly, I should wait for the change until @martinlingstuyl makes his adjustments. Regarding the util comment from @Adam-it, would it be included in Martin's change, or should I move it into my commits?

Hi @mkm17, the other issue is still in help wanted mode, I'm currently not working on it.
Aside from that: you could also just start and build the feature here. We'll need some shared code anyway, and you could include the code to update the public client flows toggle along with what you're building.
Thoughts? @pnp/cli-for-microsoft-365-maintainers

Hi @mkm17, the other issue is still in help wanted mode, I'm currently not working on it.
Aside from that: you could also just start and build the feature here. We'll need some shared code anyway, and you could include the code to update the public client flows toggle along with what you're building.
Thoughts? @pnp/cli-for-microsoft-365-maintainers

Exactly what I was thinking.

yep. I would also not wait for this feature if you are ready to go 🚀. I would:

look for similarities with the app add command and extract that logic to some util methods to be reused in both commands
add handling the public client flows toggle along with implementing this if possible

Maybe a bit late on this, but shouldn't we align this issue with how we add permissions on applications? (using --apisDelegated and --apisApplication options)
@pnp/cli-for-microsoft-365-maintainers  @mkm17

@martinlingstuyl, as I understand, instead of choosing the --mode and assigning --permissions, with your approach, the mode would be chosen by defining the correct parameter --apisDelegated or --apisApplication. But then how to handle the --permissionsSet? By adding more options like: ReadAllDelegated, ReadAllApplication?  What do you think @pnp/cli-for-microsoft-365-maintainers?

Alternate idea: --permissionsDelegated / --permissionsApplication
It would then be an optionset @mkm17, specify either permissionsDelegated / permissionsApplication or permissionSet

Ideas @pnp/cli-for-microsoft-365-maintainers ? Or shall we keep the specs as is?

We could make that two options as well: --permissionsSetDelegated and --permissionsSetApplication....
But maybe this does not make it clearer after all...

I think it's too complicated. We can also drop permissions sets for now and start with just delegated and app-only permissions

In that case: is your suggestion to keep --mode and --permissions? And what values would you expect for permissions? The full resource+scope urls I presume? @waldekmastykarz

Yes, let's stick with --mode and --permissions. For permissions, the safest would be to get resource+scope, although I believe, that Entra defaults to Graph if all you specify is scope. We can follow the same route to make it more convenient for folks to specify their permissions.

Hi, I've paused a bit on this task as I've had some other topics at work. I'll come back to it after Easter. :)

Hello everyone, I've finally created a pull request (PR) for this task. However, I still have some concerns, so I'm eager to hear your opinions on certain aspects described in the PR comment. More information is available here: #5985

authors: Adam-it garrytrinder martinlingstuyl milanholemans mkm17 plamber waldekmastykarz


text:
Get-PnPTenantSite Errors With "File Not Found" When Using a URL for the Identity Parameter

Reporting an Issue or Missing Feature
Please confirm what it is that your reporting
When executing Get-PnPTenantSite with the -Identity parameter as a site URL the action randomly fails with "File Not Found." Continued retries eventually results in the completion of the cmdlet. Using the -Filter parameter with the Url -eq  returns the object. Running Get-PnPTenantSite with only the -Connection parameter returns all sites and included the site which fails with the -Identity parameter.
Expected behavior
The cmdlet should return the site object.

Actual behavior

PnPLog Output:
powershell_ise.exe Error: 0 : 2022-12-13 13:15:55.6186	[PnP.Framework]	[0]	[Error]	ExecuteQuery threw following exception: Microsoft.SharePoint.Client.ServerException: Cannot get site https://???.sharepoint.com/sites/TestCreate5.
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()
at Microsoft.SharePoint.Client.ClientRequest.d__53.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientRequest.d__39.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientRuntimeContext.d__65.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.SharePoint.Client.ClientContext.d__28.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
at Microsoft.SharePoint.Client.ClientContextExtensions.d__6.MoveNext()
ServerErrorCode: -1
ServerErrorTypeName: Microsoft.Online.SharePoint.Common.SpoNoSiteException
ServerErrorTraceCorrelationId: d7dc81a0-30b8-2000-e499-440b63f95009
ServerErrorValue:
ServerErrorDetails:
.	0ms
Steps to reproduce behavior
$HostUrl = "https://???-admin.sharepoint.com/"
$strURL = "https://???.sharepoint.com/sites/TestCreate5"
Connect-PnPOnline -Interactive  -Url $HostUrl | Out-Null
$ConnHost = Get-PnPConnection
Get-PnPTenantSite -Connection $ConnHost -Identity $strURL
What is the version of the Cmdlet module you are running?
1.11.0
Which operating system/environment are you running PnP PowerShell on?

[x] Windows
[ ] Linux
[ ] MacOS
[ ] Azure Cloud Shell
[ ] Azure Functions
[ ] Other : please specify

No. It still happens. More frequently than I'm comfortable with.

@shcrist - does this happen for all sites or just some site collections or maybe just one specific site collection ? Seems like some server side issue. Can you also maybe try on another tenant as well if possible ?

@gautamdsheth It happens for all sites, just not all of the time. I moved the solution to a DoD tenant and I'm seeing the same behavior. It was working fine until about two months ago. If it's the underlying CSOM creating the issue, then I have to wonder if there wasn't an update around that time. It's essentially made this functionality so unreliable that I can't use it.

I ran this line here which effectively will do an -Identity call for each of the site collections in my tenant (OneDrives excluded) and none of them throws an error:
Get-PnPTenantSite | % { Get-PnPTenantSite -Identity $_.Url }

Does this issue still occur for you? There doesn't seem to be anything on the PnP PowerShell side wrong with this one. Perhaps it was a server issue, perhaps there was some corruption in the hidden lists within the SharePoint Online admin center? I believe  they've been doing some changes to those lists around that time. Perhaps those could have temporarily interfered with this?

I'll give it a try tomorrow and see if I'm still seeing it.
Shaun Crist
Senior Consultant
SharePoint
Microsoft Federal
Office: 803 669-0074
@.@.>
@.***  @.*** @.*** @.*** @.*** @.***
From: Koen Zomers @.>
Sent: Tuesday, January 17, 2023 9:49 AM
To: pnp/powershell @.>
Cc: Shaun Crist @.>; Mention @.>
Subject: Re: [pnp/powershell] Get-PnPTenantSite Errors With "File Not Found" When Using a URL for the Identity Parameter (Issue #2647)
I ran this line here which effectively will do an -Identity call for each of the site collections in my tenant (OneDrives excluded) and none of them throws an error:
Get-PnPTenantSite | % { Get-PnPTenantSite -Identity $_.Url }
Does this issue still occur for you? There doesn't seem to be anything on the PnP PowerShell side wrong with this one. Perhaps it was a server issue, perhaps there was some corruption in the hidden lists within the SharePoint Online admin center? I believe they've been doing some changes to those lists around that time. Perhaps those could have temporarily interfered with this?

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fpnp%2Fpowershell%2Fissues%2F2647%23issuecomment-1385541461&data=05|01|Shaun.Crist%40microsoft.com|6f4eb2aa1ade42c79ca108daf899e8d6|72f988bf86f141af91ab2d7cd011db47|1|0|638095637178439948|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=tMs%2Fdit0JNTVyg7qdNXzQ1WMEb%2B7MeSxhwsvArIe5nQ%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAHYJZNRQJPBR7S6MOYYW4QLWS2WMFANCNFSM6AAAAAAS5J6P3Q&data=05|01|Shaun.Crist%40microsoft.com|6f4eb2aa1ade42c79ca108daf899e8d6|72f988bf86f141af91ab2d7cd011db47|1|0|638095637178439948|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=9Fo3lR29a7wIjs6vObFddRb6mgvSglXpAqUaZwzKj0c%3D&reserved=0.
You are receiving this because you were mentioned.Message ID: @.@.>>

It seems to be working as expected again. The only thing I can figure is there was a problem with CSOM in the environment.

authors: KoenZomers gautamdsheth shcrist

repo: pnp/powershell


text:
Update Get-PnPGroupPermissions.md

Added missing description, updated parameter description
Before creating a pull request, make sure that you have read the contribution file located at
https://github.com/pnp/powerShell/blob/dev/CONTRIBUTING.md
Type

[ ] Bug Fix
[ ] New Feature
[ ] Sample
[x] Text for description

Related Issues?
None
What is in this Pull Request ?
Suggested text for missing cmdlet description and a parameter description.

Thanks for your contribution @PowershellScripts !

authors: KoenZomers PowershellScripts


text:
DynamicForm - Custom sorting

Q
A

Bug fix?
[ ]

New feature?
[ X ]

New sample?
[ ]

Related issues?
mentioned in #1416

DynamicForm custom sorting.
Added a new optional prop fieldOrder (string[]), the values are the fields internal names.

Merged manually, thank you!

authors: michaelmaillot srpmtt

repo: pnp/sp-dev-fx-controls-react


text:
New Property Controls (Message, Search and Spinner)

Q
A

Bug fix?
[x]

New feature?
[x]

What's in this Pull Request?
New Property Controls
Message, Search, and Spinner

Thank you very much @joaojmendes for such a great contribution!
The PR has been merged and will be included in the next release.

For me is a pleasure to contribute to this great community !   😊
Thank you for your support @Alex Terentievmailto:notifications@github.com and you amazing work.
Have a nice weekend.
João
From: Alex Terentiev notifications@github.com
Reply to: pnp/sp-dev-fx-property-controls reply@reply.github.com
Date: Saturday, 16 May 2020 at 00:24
To: pnp/sp-dev-fx-property-controls sp-dev-fx-property-controls@noreply.github.com
Cc: João Mendes joao.j.mendes@outlook.com, Mention mention@noreply.github.com
Subject: Re: [pnp/sp-dev-fx-property-controls] New Property Controls (Message, Search and Spinner) (#248)
Thank you very much @joaojmendeshttps://github.com/joaojmendes for such a great contribution!
The PR has been merged and will be included in the next release.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/pnp/sp-dev-fx-property-controls/pull/248#issuecomment-629546421, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AC7YHVJ437VHLOZZNQUMODTRRXFL5ANCNFSM4M5KILBQ.

authors: AJIXuMuK joaojmendes

repo: pnp/sp-dev-fx-property-controls


text:
React recently used documents: Upgraded to 1.16.1

Category

[ ] Bug Fix
[x] New Feature
Related issues: fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
Upgraded to SPFx 1.16.1.

merged to v3 branch, thank you for the contribution.

authors: chandaniprajapati eoverfield

repo: pnp/sp-starter-kit


text:
Feature request: Allow for custom id to be set when you initialize a new row

Title basicly explains everything. I would like to be able to set the id myself. Pocketbase is great but for the things i want to use it it would be greate to be able to set my own id's.

You should be able to do that already if you submit the id field with your create data.
The only limitation at the moment is that it needs to be 15 chars string, but eventually in the future this will be "loosen" and we allow any unique value.
You can also define any id value (without the 15 chars limit) using the OnModelBeforeCreate hook.

repo: pocketbase/pocketbase


text:
Transcoding process updated

Loading bar design. Color and width changed.
Upscaling of transcoded videos is disabled.
Smooth loading bar. Now it is connected to FFmpeg progress report event.
Overall calculation progress function. For handling several transcodings in the future.
Code optimized. Redundant scripts removed.
Handling situation when there is insufficient disk space for transcoding.

Added CSS transition for loading bar. Now it runs more smoothly.


text:
HMS-1832: update domain fixes

A series of commits addressing HMS-1832.  Recommended to review each commit in sequence, rather than the whole PR diff all at once.
Why no tests?  The behavioural changes are mainly at the handler level, and there is no easy way to test that at this time.  Following discussions with @avisiedo , we propose to implement a "smoke test" framework in a (near) future sprint.  It can make it easy to test server behaviour via the service HTTP API, playing out the various scenarios and asserting that response statuses and payloads match expectations.  When this is implemented, it will be straightforward to test the behaviour in this PR - and I shall implement the tests!
commit 0d90e0b0e32c8a1c08d37d84fafde46d16253b26
Author: Fraser Tweedale <ftweedal@redhat.com>
Date:   Tue Oct 31 16:36:53 2023 +1000

    remove unused func

commit 0ef981b34fb8904e51de77234dc4d69d360e6d15
Author: Fraser Tweedale <ftweedal@redhat.com>
Date:   Tue Oct 31 16:40:34 2023 +1000

    refactor: clarify update authorization check

    Rename the function `isSubscriptionManagerIDAuthorizedToUpdate` to
    `ensureSubscriptionManagerIDAuthorizedToUpdate`.  The old name makes
    it seems like it would return a `bool`, when in fact it return `nil`
    on success or an error if there is a problem.

    Also convert it from an object method to a bare function, because
    the `application` was unused.

commit fba23dc54c26d88be90935295585f8a4ba691d89
Author: Fraser Tweedale <ftweedal@redhat.com>
Date:   Tue Oct 31 17:06:08 2023 +1000

    HMS-1832 fix: 403 when server not allowed to update domain

    To update a domain, the server (i.e. its RHSM ID) must already exist
    in the domain being updated.  When a client violates this condition,
    the server currently responds 500 Internal Server Error.  Make it
    return 403 Forbidden instead.

commit 86b71c5f42680415e92fa91c619af6e89155a378
Author: Fraser Tweedale <ftweedal@redhat.com>
Date:   Tue Oct 31 17:06:08 2023 +1000

    HMS-1832 fix: update domain: 404 when not found

    When an agent updates a domain (`PUT /domains/{uuid}`), if the
    domain is not found in the current org, the server currently
    responds 500 Internal Server Error.  Make it return 404 Not Found
    instead.

commit 4a169608cde0dde4ace4e4639ff53ab40d071b2a
Author: Fraser Tweedale <ftweedal@redhat.com>
Date:   Wed Nov 1 16:59:07 2023 +1000

    HMS-1832 fix: prevent changing domain name

    Detect if client is attempting to change the domain name.  Return an
    error if so.

    Also remove processing related to Title, Description and
    AutoEnrollmentEnabled fields.  These fields do not appear in the
    UpdateDomainAgentRequest payload type.

commit 47b252aa1d33788d0989450bab428c0bc4cd3163
Author: Fraser Tweedale <ftweedal@redhat.com>
Date:   Wed Nov 1 16:59:07 2023 +1000

    HMS-1832 refactor: clean up database operations

    Simplify the database operations in the `UpdateAgent` operation.

    First, the handler already "merged" the old and new data, so there
    is no need to query (`FindByID`) the target record again.

    Second, the model object already has the primary key (`id`) set, so
    remove the unnecessary `Where` clause.

    Third, in `updateIpaDomain()`, after the (cascading) deletion of the
    previous associations, simply use `Create` *without*
    `Omit(clause.Associations)`.  This recursively inserts the new or
    updated associations and avoids the manual iteration and insertion
    of the child server, certificate and location objects.

    Unfortunately, I could not find a way to avoid the explicit deletion
    of the existing associations.  I tried many permutations but in each
    case, the old associations were persisting and resulting in
    duplicated and/or obsolete values.\

Hm, I have to work out what's going on with the test failures...

OK, I backed out the refactor after banging my head against the domain_repository DB mock tests.  They were extremely brittle.  After we implement a better integration/smoke test system, I'd like to throw out these mocks.  The testing of the internal details is brittle, and less important than testing that the behaviour of the system from client POV is correct.

repo: podengo-project/idmsvc-backend


text:
Fixup to e3b2201f: prevent open::that from blocking, fix a typo, minor code simplification

open::that can block, for example when firefox is the default browser
on Linux and no instance of firefox is running.

Perhaps tokio::spawn_blocking with open::that would be better in terms of error handling than using that_detached. The latter does not report an error if the browser exits with an error code. OTOH, with open::that, killing the server might kill the browser...

Thanks

authors: attila-lin ilyagr

repo: poem-web/poem


text:
TypeError: Cannot read property 'apply' of undefined [reqOptions.callback.apply(self, m.params) in manager.js]

Hi,
My name is Scott Davis. We are using JSReport in our application, and noticed a show-stopper bug was introduced in node-script-manager on roughly 2015-04-09. This bug was introduced without a corresponding SemVer bump in the version number. (In other words, last week script-manager#0.2.0 was working in production; this week script-manager#0.2.0 fails with this bug.)
The error thrown is this:
/Users/scott/code/local/hdslabs/doorways/node_modules/
jsreport/node_modules/script-manager/lib/manager.js:77

                reqOptions.callback.apply(self, m.params);

                                   ^

TypeError: Cannot read property 'apply' of undefined
    at ChildProcess.<anonymous> (/Users/scott/code/local/hdslabs/doorways/node_modules/
jsreport/node_modules/script-manager/lib/manager.js:77:36)
    at ChildProcess.emit (events.js:129:20)
    at handleMessage (child_process.js:324:10)
    at Pipe.channel.onread (child_process.js:352:11)

[nodemon] app crashed - waiting for file changes before starting...

Doing a bit of console logging, I discovered that the function call should be reqOptions.cb, not reqObject.callback.
m:
{ action: 'callback',
  rid: '636b7d90-e2be-11e4-b367-c77209aa2568',
  pid: 84187,
  params: [ null ] }

reqOptions:
{ execModulePath: '/Users/scott/code/local/hdslabs/doorways/node_modules/jsreport/lib/render/renderExecution.js',
  timeout: undefined,
  rid: '636b7d90-e2be-11e4-b367-c77209aa2568',
  isDone: false,
  cb: [Function] }

Here is the patched code. It is a single line -- the last reqObject.cb.apply call. (I can also send you a pull request if you'd prefer).
self.workersCluster.on("message", function (m) {
    if (m.action === "callback") {
        var reqOptions = _.findWhere(self._runningRequests, { rid: m.rid });
        console.log('m:');
        console.dir(m);
        console.log('reqOptions:');
        console.dir(reqOptions);
        m.params.push(function(){
            var args = Array.prototype.slice.call(arguments);
            if (args.length && args[0]) {
                args[0] = args[0].message;
            }
            self.workersCluster.send({
                action: "callback-response",
                rid: m.rid,
                params: args
            })
        });
        reqOptions.cb.apply(self, m.params);
    }

Hi Scott,
thanks for the bug report, but I think the problem is somewhere else.
I have introduced the new breaking change in script-manager 0.2 which requires following signature of all scripts:
module.exports = function(inputs, callback, done) {
...
}

Where in script-manager 0.1 scripts' signature was
module.exports = function(inputs, done) {
...
}

Unfortunately script-manager was wrongly referenced in the jsreport 0.3 and this breaking change started to bug it. jsreport 0.3 is using the old srcipts signature and undesirably calling new callback feature which throws the exception you describe. So the problem of your code is probably wrong signature of the script.
The reference for script-manager was fixed in 0.4 so hopefully we don't get into such a situation again. I am sorry for the problems it caused.

Hi Jan,
Thanks for your feedback. We’re obviously big fans of your work here at HDS Labs. I work with Scott Fredericksen (cc’d), who you’ve been exchanging emails with on another thread.
We rev’ed to jsreports#0.4.0, and that seemed to fix the issue.
Hopefully you understand our frustration that last week’s deployment to production (using script-manager#0.2.0) worked perfectly, yet this week’s deployment to production failed with exactly the same version of script-manager#0.2.0. Changing method signatures without rev’ing the SemVer made this bug quite tricky to track down, especially since it was in an underlying transitive dependency.
This situation could’ve been avoided completely if:

You referenced the dependency on script-manager in jsreports’s package.json by explicit version number — 0.2.0 — instead of *.
You rev’ed the version of script-manager from 0.2.0 to 0.3.0 when you changed the method signature.

That way jsreport#0.3.0 would’ve been able to pull down the appropriate dependency, and upgrading to jsreport#0.4.0 would’ve upgraded its dependencies accordingly.
Hopefully you don’t feel that I’m lecturing you here — believe me, we’ve all made mistakes like this before, including me! My only goal with this is to turn it into a learning experience so that we don’t get caught by the same issue again in the future. We want to continue using your awesome software for a long time.
Thanks for all of the effort you’ve put into jsreports, including the website, documentation, and examples.
Cheers,
s
Scott Davis
scott@davisworld.org

On Apr 15, 2015, at 2:08 PM, Jan Blaha notifications@github.com wrote:
Hi Scott,
thanks for the bug report, but I think the problem is somewhere else.
I have introduced the new breaking change in script-manager 0.2 which requires following signature of all scripts:
module.exports = function(inputs, callback, done) {
...
}
Where in script-manager 0.1 scripts' signature was
module.exports = function(inputs, done) {
...
}
Unfortunately script-manager was wrongly referenced in the jsreport 0.3 and this breaking change started to bug it. jsreport 0.3 is using the old srcipts signature and undesirably calling new callback feature which throws the exception you describe. So the problem of your code is probably wrong signature of the script.
The reference for script-manager was fixed in 0.4 so hopefully we don't get into such a situation again. I am sorry for the problems it caused.
—
Reply to this email directly or view it on GitHub https://github.com/pofider/node-script-manager/issues/1#issuecomment-93551286.

Thanks for very valuable advises. I really appreciate it.

jsreport is since 0.4 using "~" to reference script-manager and I will change it to match just exact version. I understand the frustration when the same version of jsreport suddenly starts to behave differently

Just to make it clear here. In npm there are versions 0.1.0, 0.1.1 and 0.2.0 of script-manager, where the signature is changed in 0.2.0. That is fine for npm, but unfortunately I didn't make tag in git for 0.1.0 and 0.1.1 what caused  part of the problems.

To summarize:

I will let jsreport to reference dependencies only with explicit versions
Every release will be properly tagged in git

Thanks again, if anything else pops up what could be improved, please let me know.

Jan,
You rock!
Thx,
s
Scott Davis
scott@davisworld.org

On Apr 16, 2015, at 1:44 AM, Jan Blaha notifications@github.com wrote:
Thanks for very valuable advises. I really appreciate it.
jsreport is since 0.4 using "~" to reference script-manager and I will change it to match just exact version. I understand the frustration when the same version of jsreport suddenly starts to behave differently
Just to make it clear here. In npm there are versions 0.1.0, 0.1.1 and 0.2.0 of script-manager, where the signature is changed in 0.2.0. That is fine for npm, but unfortunately I didn't make tag in git for 0.1.0 and 0.1.1 what caused part of the problems.
To summarize:
I will let jsreport to reference dependencies only with explicit versions
Every release will be properly tagged in git
Thanks again, if anything else pops up what could be improved, please let me know.
—
Reply to this email directly or view it on GitHub https://github.com/pofider/node-script-manager/issues/1#issuecomment-93668264.

repo: pofider/node-script-manager

license: mit

license_source: bigquery


text:
Added support for avoiding re-recording snapshots if there're no differences according to the matcher used.

This PR attempts to solve the problem of introducing unneeded changes in the snapshots for the projects that use "imprecise" matching, by avoiding recording a new version of a snapshot, if recording is enforced, and a new version of the snapshot does not differ from the original, according to the imprecise matcher used.
As an additional bonus, recording snapshots does not trigger test failures for versions that match the originals - it's now clearly seen from test results, what snapshots did not match the originals and were changed.

@grigorye Is there anything else that needs to be done in this PR to get it marked as ready for review/merging?

@agurtovoy Well, even though we've been using it for quite some time in "production", I would like to get a confirmation from somebody else, that it's useful and works for them. But, if you believe that it's worth pushing it for review, I don't mind starting the process.

@grigorye We just started using https://github.com/JWStaiert/SnapshotTestingEx and, as you mention in this comment, we need something along the lines of this PR to avoid "drifting" of snapshots that are "fuzzily" compared when you enable shapshot recording for the whole test suite rather than on a test-by-test basis.
Adding SNAPSHOT_RECORDING env variable is an uncontroversial improvement and can probably be a separate (tiny) PR.

@agurtovoy Re: SNAPSHOT_RECORDING - I also thought about a separate PR, but now I think that it's related to another feature "re-implemented" here: being able to delete the obsolete snapshots on "regeneration", without source code modifications.
In upstream, (as far as I know) the only way to delete the obsolete snapshots is erase all the snapshots, execute all the tests, and then regenerate only the actual set. It did not require enforcing the recording by changing that variable, as by default the snapshot is recorded unless the original already exists. What is important is that this does not require any modification of the source code - we just delete files in the file system before running tests.
Here, to get rid of obsolete snapshots, we can not delete all the snapshots, as it would basically make it impossible to fuzzy compare new snapshots vs originals (originals would be gone). Instead, we rely on enforced recording and the file modification date - we touch every snapshot file that would be generated (especially the one that fuzzy matches and that we keep unchanged in terms of content). Then we can search for all the snapshots in the tree, based on the file name or residing Snapshots directory or whatever (yeah, it's a bit of a hack), and erase every snapshot which modification date is not changed. To support this very approach without modification of the source code, we need to enforce from the outside. That's why "SNAPSHOT_RECORDING" is introduced instead of just "false".
I consider being able to erase the obsolete snapshots an existing/required feature, hence introducing this PR without support for that would be a regression from that perspective. That's why I wonder if it makes sense to keep SNAPSHOT_RECORDING inside this very PR.
What's your opinion? I feel like this SNAPSHOT_RECORDING is a hack, as it relies on certain file name structure/file modification dates. That's why I don't feel confident about this whole thing, I personally would not approve it in such a form... :-)

Closed via #867.

authors: agurtovoy grigorye mbrandonw

repo: pointfreeco/swift-snapshot-testing


text:
Silently fails if directory exists

I had problems cloning the repo and the logs gives of something similar to this:
[2017-01-17T14:45:07+00:00] INFO: Processing application_git[a/b] action sync ()
When I enable debug log level I also see this:
[2017-01-17T14:45:08+00:00] DEBUG: application_git[git@github.com:a/b] checkout destination /path/to/dest already exists or is a non-empty directory
Of course the recipe breaks later on but it would be useful if the above step also passed on the cloning error in the logs, would ease troubleshooting.

That is coming from the core git resource: https://github.com/chef/chef/blob/master/lib/chef/provider/git.rb#L85
Not related to this cookbook.

authors: coderanger parhamfh


text:
Docs: add individual component docs

We can port most of the aragonUI docs, gladly, even though they might need some tweaking depending on the props we've removed.

Closed with #11

repo: pokt-foundation/pocket-ui


text:
Polkadot Protocol > Protocol Components > Accounts > Account Balance Types

Migrated https://wiki.polkadot.network/docs/learn-account-balances page

@dawnkelly09 - please check this over to make sure I didn't miss anything 🙂

repo: polkadot-developers/polkadot-docs


text:
[Polkadot Wiki Migration] Using Light Clients

This page is from the Polkadot Wiki, and will be heavily edited, updated, and appropriated as needed.

Page referenced: https://wiki.polkadot.network/docs/build-light-clients

Not really sure what else to add, so I kept it concise.  We can always add more to it later.


text:
feat: add pawel to authors

I added myself to the authors. If everything is ok then please merge.

LGTM. Will be merged in next release. Cycle

authors: Pawel-Gnat polubis

repo: polubis/WebBlog


text:
Use "count" suffix instead of "Num" prefix

https://github.com/polyverse/ropoly/blob/1f6d984c64ff6073222c5ab2f62d7a701527dc1a/lib/types.go#L86

For instance:
OldGadgetCount is more descriptive than NumOldGadgets - can be misinterpreted as whether it's the number of gadgets or the number of a gadget (which can easily be confused with signature.)

repo: polyverse/ropoly


text:
timestamp_16 fields

I'm trying to decode whatever I can from the large "get all my data" zipfiles you can get from Garmin.
In the monitoring_b files you have a monitoring message that contains average heartbeat for that minute and a timestamp, but the timestamp is 16-bit, and a variant of the FIT-file 5-bit timestamp as described on https://developer.garmin.com/fit/protocol/ (search for 5-bit but you probably remember this anyway :) )
I've verified this is the 16-bit version of it, roughly, by comparing against an adjacent full timestamp (from a stress level message right before it):
97. monitoring
 * heart_rate: 54 [bpm]
 * timestamp_16: 50060 [s]
...
99. monitoring
 * activity_type: sedentary
 * current_activity_type_intensity: (8,)
 * intensity: 0
 * timestamp: 2017-06-18 23:41:00

$ printf "%x %x\n" $(($(TZ=0 date -d '2017-06-18 23:41:00' +%s)-631065600)) 50060
33a9c38c c38c

Shouldn't be hard for me to do the conversion but tracking the most recent full time from any recent field in the file will get a little ugly. Could your library do this more cleanly?

Wrote this super simple data processor for now, which may or may not work well (I've not tested it around rollovers yet and it'll probably fail).
class Proc(fitdecode.processors.StandardUnitsDataProcessor):
	def process_type_date_time(self, reader, field_data):
		super().process_type_date_time(reader, field_data)
		last : datetime.datetime = field_data.value
		self.last_date = (int(last.timestamp()) - fitdecode.processors.FIT_UTC_REFERENCE) & ~0xffff

	def process_type_uint16(self, reader, field_data):
		if field_data.name == "timestamp_16":
			field_data.value |= self.last_date
			super().process_type_date_time(reader, field_data)

repo: polyvertex/fitdecode


text:
NTR reduced protein localization to nucleus during mitosis PMID:10523629

standard def
reduced protein localization to nucleus during mitosis

decreased protein localization to nucleus during mitosis FYPO:0005672
edit file: 19ebdbdb0e2cae0d1b90961a57115efd15b9bdf4
release: 3a2745c6a0a452731fd890b1799aca8fb4b94a41

repo: pombase/fypo


text:
typo phopshate

FYPO:0008123
Ontology | fission_yeast_phenotype
Term name | loss of viability in stationary phase upon phopshate starvation

fixed. The ID for this term does not show up in Protege?

Still the ID does not show. I don't know why, this should be automated.
I do locate the term with an ID (FYPO:0008123) search though...

Three could be lots, I only spotted this by chance...
But I don't understand how all of the checks pass
@manulera  @kimrutherford   do you know how to troubleshoot this?

Shouldn't this happen automatically?
There was another change (fairly recently).
Now the obo name space (fission yeast phenotype)  is not automatically  populated , but it used to be ( I am not quite sure when this happened).
I don't know who to ask about issues like this because I don't really know  who  or where which bits happen. Do you think  these would be suitable questions to ask on obo community, or phenotype  ontology Slack channels?

I would say ask in OBO, I am sure @matentzn or @gouttegd know something about this.
It probably has to do with Protege config, or with the OBO annotation plugin.

It looks like FYPO transitioned from the OBO Flat File format (fypo-edit.obo) to the OWL Functional Syntax format (fypo-edit.owl) for its main editing format a few years ago (#4192).
When using OWL Functional Syntax as the edit format, it is normal that the id and the OBO namespace (oboInOwl:id and oboInOwl:has_obo_namespace annotations, respectively) do not appear in Protégé; they only appear when working from an OBO Flat File format.
The terms where those annotations are present in the current version of ontology are most likely terms that were created before the migration to OWL Functional Syntax.

Wow, thanks, @gouttegd - I am embarrassed that I only just spotted that! I had assumed that did not get added until the release pipeline until now.
Do you know how we can configure so that
obo name space "fission_yeast_phenotype" appears automagically? I am sure that it used to. It would be one less typo to make.

Hi @gouttegd thanks for rescuing the original place where this happened!
If I am not mistaken, the reason for this was that using .obo the diffs were always polluted with an incredibly long line that contained the logical definitions. When we transitioned to owl, we could see meaningful diffs that included the logical definitions, and when I had to add a lot of phenotype terms (e.g. for papers with screens) I was able to use scripts that added the logical definition in owl syntax.
Are logical definitions still stored in OBO like that? And is there a way to include those missing annotations easily via protege settings?

Now the obo name space (fission yeast phenotype) is not automatically populated , but it used to be ( I am not quite sure when this happened).

Hi Val.  I'm confused by this.  The OBO files in the release have this at the top:
default-namespace: fission_yeast_phenotype

That seems OK?

Its about the namespace that is needed on every new term:
has_obo_namespace fission_yeast_phenotype
It used to be there automatically, and now I need to add it manually.

authors: ValWood gouttegd kimrutherford manulera


text:
next grant: community data/ colleague information

We need to do something about this at some point, opening an item so I can get this off my to do list:
Steve: Ways of tracking users who move lab, people with the same name etc, perhaps a user ID?
Steve: Capturing users "topics" of interest (can be used to get the community to curate papers other than their own during jamborees etc).
allow community to see their list of Pubs
Original comment by: ValWood

ORCID will manage this

authors: ValWood pombase-admin

repo: pombase/pombase-chado


text:
Update GI documentation once the display is live

For now only the interface for legacy GIs is described.

Sorry, I merged the pull request before I noticed this issue.  I think it's OK to have your new text in the documentation but I can quickly revert it if you think that makes sense.

authors: kimrutherford manulera

repo: pombase/website


text:
orthology annotation display for publication pages

Where a paper is cited as the dbxref for an ortholog, the annotation appears on the publication page (good), but in a too-brief, unhelpful kind of way (bad). To improve the display, make it basically like the display on gene pages, plus the pombe gene name, a la:

S. pombe gene
Ortholog species
Orthologous gene

xlf1
Homo sapiens
NHEJ1 (ENSG00000187736)

xlf1
Saccharomyces cerevisiae
NEJ1 (YLR265C)

Also make the hyperlinks work correctly for genes (i.e. same as on gene pages); the pombe gene link is broken at present.
(inspired by #256)

also, if there's a dbxref for an ortholog, add it to the gene page display
(holler if you want that in a separate ticket)


text:
ordering within "target of" section (GO)

default
if a by gene (i.e  group same gene together) , but the first gene(s) will be those which have
a)
directly activated by
directly inhibited
b)
substate of
c) binds
d) regulated by
Relationships can be considered to be redundant here so the most "specific"
relation is the only one we need to show in summary.
This would collapse to
directly activated by cdc25,
directly inhibited by wee1
substrate of mcs6
substrate of  mik1
substrate of  pyp3
substrate of csk1
regulated by cdc13
regulated by cdc16
binds suc1
binds spd1
regulated by mcs2
regulated by clp1
regulated by srw1
This does not collapse much, it only removes 4  entries from this list, but biologically it makes more sense, because the ones closest to cdc2 biochemically  are listed first.
This is also a curation aid because we can see where annotation is lacking....
For example really cdc13 should be annotated as a direct activator of cdc2.
In fact we can't get the specificity in GO between a  "direct activator"  (cdc13) and a  "direct positive regulator" (wee1). Go decided not to differentiate....(I wonder if this is a good long term plan...)

Yes  please implement, but non- urgent.
Will keep it in the milestone but it really isn't critical for release at all.

I don't think this will bother our users, but it will be a long term improvement...

can remove milestone if  time > a couple of hours

default
if a by gene (i.e group same gene together) , but the first gene(s) will be those which have
a) ...

So sort by the relationships, in the order you listed?

"group same gene together"

Or do you mean sort by gene, then by relationship?  We can't group the genes together if we order by relationships.
Ordering won't take too long.  This will take longer:

Relationships can be considered to be redundant here so the most "specific"
relation is the only one we need to show in summary.

Lets leave this one for a while. I'll remove next. Will mull over....

-by relationship as listed above first.

alphabetical gene name 2nd
(was that the question?)

@kimrutherford did this make sense?

did this make sense?

Yes, except for:

Relationships can be considered to be redundant here so the most "specific"
relation is the only one we need to show in summary.

Which relationships are the most specific?

directly activated by
directly inhibited by
substate of
binds
localized by
regulated by
activity affected by mutation in
affected by mutation in

yes
directly activated by/ directly inhibited by (show both by default although unliekly to occur together?)
substrate_of
binds
localized by/ regulated by (show both by default)
activity affected by mutation in
affected by mutation in

So in summary
Show only the most specific relationship type be default (but show all annotation in 'show details"
Using
directly activated by/ directly inhibited by (show both by default although unliekly to occur together?)
substrate_of
binds
localized by/ regulated by (show both by default)
activity affected by mutation in
affected by mutation in
for the precedence.
Then order within a specific relationship alphabetically by gene name

I did a query to see if any relations aren't covered and found that "transported by" isn't in your list.  Where should that go in the priority order?

binds
transported
localized.
If we ever use a new relationship type that is not  currently used, will we get a log message?

If we ever use a new relationship type that is not currently used, will we get a log message?

Yep, you'll see a complaint in the log.
Currently the list is sorted by the gene column.  Should it be sorted by relation?

Yes, relation first, and then gene.

OK, thanks.  I've got the sorting by priority done.  I'll add sorting by gene and then it should be ready for tonight's load.  I haven't implemented the filtering by priority yet.

I forgot to ask about GO versus FYPO.  Should they be treated separately or an GO annotation take priority over a FYPO annotation in the summary?

GO takes priority over FYPO.

GO takes priority over FYPO.

Great.  That's how implemented it.  The changes are in the main site now, including filtering by priority.  Please let me know if you spot any problems.

Looks great!, much easier to consume ( cdc2 target of is a good eg)
Just to check, do ALL the annotations show in show details? (I think they do)

Just to check, do ALL the annotations show in show details? (I think they do)

Yep, the order has changed but only the summary will have less annotations.

Hi Val.  Where should "phosphorylated by" and "ubiquitinated by" appear in the ordering?  They've popped up in the log file.  Currently the go to the end of the table because they aren't configured.

Before substrate_of I think

Before substrate_of I think

Thanks.  I've changed the config and I'll check Friday night's load.

Thanks. I've changed the config and I'll check Friday night's load.

It's fixed now.

authors: Antonialock ValWood kimrutherford


text:
config: turn on leadership election

Summary
Enable Kubernetes leadership election in all-in-one mode so only a single ingress controller will run at a time.
Related issues
Fixes https://github.com/pomerium/internal/issues/890
Checklist

[x] reference any related issues
[ ] updated docs
[ ] updated unit tests
[ ] updated UPGRADING.md
[ ] add appropriate tag (improvement / bug / etc)
[x] ready for review

there are some complications if we go with the kubernetes based leader election:

with 2 replicas and in-memory databroker, k8s - based leader election acts individually on each controller, meaning there may be a situation that bootstrap controller (that also starts embedded pomerium core) would run on one replica, and settings controller may be elected on another replica and it would be stuck forever waiting for the initial config to be available.
when there is a Postgres/Redis databroker, there should not be any kubernetes leader election for the bootstrap controller, as each replica must run it.

What is the alternative to Kubernetes leadership election?

authors: calebdoxsey wasaga

repo: pomerium/ingress-controller


text:
Localization of default messages.

Would be nice to localize default messages.
It can be done with resources or default .NET messages (they uses resources anyway).

Or another way:
Raise.ArgumentNullException.DefaultMessage = "Something bad happened";

A little weird, but good enough.


text:
"not match" and "not if" causing compiler error

"not match" and "not if"
This is a repost of an issue mentionned on an RFC
Doing not match ... end and not if ... end results in an error:
syntax error: expected expression after not

As the documentation states, if ... end and match ... end are expressions, so this edge case should not return this particular error.
This issue is only minor, as putting parentheses around the match or the if expression fixes the issue.

Fixed by #3449

repo: ponylang/ponyc


text:
Unable to create Fedora releases due to compilation error

Fedora COPR builds changed the warnings they have on or otherwise changed the gcc version and ponyc no longer compiles. We need to fix this to get COPR builds working again.
See: https://copr-be.cloud.fedoraproject.org/results/ponylang/ponylang/fedora-29-x86_64/01042125-ponyc/build.log.
What we need to do:
[] investigate gcc version and flag used
[] setup/modify existing ci to match (not sure which is most applicable)
[] fix the issue
the 2nd 2 steps should be part of the same PR.

I think gcc  8.1 along with the -Werror=stringop-truncation flag should be enough to trigger this.

It's unclear to me whether this is a real bug or not (the compiler thinks it is). I assume from a quick glance that it is, but we'd need to verify that.

@jemc i'm not familiar with what is going on with the AST. Is this an actual error?

I get a 404 error when I click the link to see the build log. Do you have a copy of the error location and message?

Ugh. Apparently the build log gets deleted after a week. It's gone.
Building with gcc 8.1 should do the trick. There's a warning about strncpy at 3 locations in verify.c.
The warning to use to see it is: "-Werror=stringop-truncation"

I have this error on gcc (Debian 8.3.0-6) 8.3.0 i686:
src/libponyc/pass/refer.c: In function ‘generate_multi_dot_name’:
src/libponyc/pass/refer.c:154:3: error: ‘strncpy’ output truncated before terminating nul copying as many bytes from a string as its length [-Werror=stringop-truncation]
   strncpy(buf + offset, name, slen);
   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/libponyc/pass/refer.c:153:17: note: length computed here
   size_t slen = strlen(name);
                 ^~~~~~~~~~~~
src/libponyc/pass/refer.c:165:5: error: ‘strncpy’ output truncated before terminating nul copying as many bytes from a string as its length [-Werror=stringop-truncation]
     strncpy(buf + offset, name, slen);
     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
src/libponyc/pass/refer.c:164:12: note: length computed here
     slen = strlen(name);
            ^~~~~~~~~~~~
cc1: all warnings being treated as errors
make: *** [Makefile:925: build/release/obj-native/libponyc/pass/refer.o] Error 1

An option to fix for now would be:
-Wno-stringop-truncation on Makefile line 134.
It doesn't verify if the warning is real or not (this need to look at that, but it should in theory, put gcc 8+ compilation on the same footing as all the others in that it will build.

N.B. its quite possible that some of these are false positives.

Yeah, these look like false positives.

Using Ubuntu Xenial and Gcc 8.3, I am unable to reproduce this. Very odd.

authors: SeanTAllen jemc stronny


text:
Array.insert allows out of bounds access

Apologies if this behavior is expected, but I was surprised. The documentation for Array.insert says that "An out of bounds index raises an error."
actor Main
  new create(env: Env) =>
    let r = Array[U8].init(0, 1)
    try
      r.update(0, 1)?
      // r.update(1, 2)?, fails with out of bounds
      r.insert(1, 2)? // ok?
    end
    for v in r.values() do
      env.out.print(v.string())
    end

This will print both 1 and 2. Inserting at index 2 will fail. I guess line 343 here:
https://github.com/ponylang/ponyc/blob/7d7a96f6d1246bb12c7e515d7976d30c2365dea2/packages/builtin/array.pony#L337-L350
should be i < _size?
Pony version:
0.33.0 [release]
compiled with: llvm 7.1.0 -- Apple clang version 11.0.0 (clang-1100.0.33.8)
Defaults: pic=false

Since the array is resized by 1 on insertion, it makes sense that you can add a new element to the end. So this is not a bug, but the documentation can be improved to account for this particular case, as "out of bounds index" is inaccurate.

FTR this brhaviour has been introduced in this commit https://github.com/ponylang/ponyc/commit/d97130eaab218b3a3156e99a01e556f242d65a8a

I see, I wonder how to make the documentation clear to distinguish the normal behaviour with the "push" behaviour. It could be tricky to say "if the insert happens at size + 1, it will push the value instead.

Basically, the constraint here is that we cannot insert anywhere that would expand the size by more than one element, because we don't have a value to fill in for the "empty" elements that would need to be created.

I am gonna update the docstring to be up-to-date with the implementation. We agreed during sync that the current behavior is intended and the docs are stale.

authors: EpicEric ergl jemc mfelsche


text:
Garbage collect actors when --ponynoblock is in use

Prior to this commit, actors wouldn't be garbage collected when using
--ponynoblock. With this change, any actors that aren't part of a cycle
will be garbage collected if they can no longer do work.
Before this change, using --ponynoblock with an application that
created transient actors would result in never ending memory growth as
the actors would never be gc'd. You can see an example of this by taking
a Pony program that listens for TCP connections and do a repeating cycle
of open/close. None of the created TCPConnection actors would be
garbage collected.
Closes #2306

One OSX CI build failed on the process/STDIN-WriteBuf test. I've restarted the job.

authors: Praetonus SeanTAllen


text:
Clarify type parameters of TestHelper methods [ci skip]

Following discussion from this Slack thread.
[ci skip]

Guess [ci skip] doesn't work if it's not in the commit... I've cancelled all builds that I could.

CircleCI is blatantly ignoring a skip ci. Dont worry.
Great stuff!

authors: EpicEric mfelsche


text:
Add LogLevel as argument to LogFormatter

RFC text
Closes #3594

Sweet. Thanks @rkallos. Now we can move forward with the Corral change.

authors: SeanTAllen rkallos


text:
Cart Management

@pooranjoyb
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
Add product to cart as well as on Supabase [One to Many relationship] #109
Fixes # 109
Type of change
Please give a X on it which is applicable

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Refactor Code
[ ] A documentation update
[ ] Others(mentioned in the issue number)

How Has This Been Tested?

when user add any item to cart it also display in supabase cart table

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Screenshorts and Vedios:

Checklist:
give a X on it which is applicable

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

@pooranjoyb
please check this and merge it

Hii @dhruv8433 why aren't you using the Cart-Slice we need to store that in store too. Maintain that too.

@pooranjoyb
now you can check it and merge it :

@pooranjoyb
please tell me if you want any kind of modifications...

@pooranjoyb please tell me if you want any kind of modifications...

Can you show me a video demonstration @dhruv8433
It's not working on my end :/

Ok i will share you video

@pooranjoyb
please check this and merge it
if you face any issue then inform me

@pooranjoyb
please check this and merge it if you face any issue then inform me

@pooranjoyb
please check this and merge it if you face any issue then inform me

@pooranjoyb
please check this and merge it if you face any issue then inform me

Dude, why Buy Now adds to cart. The flow is different. User should go to the Product-Details page and Add to Cart button should do that logic. Please update it. @dhruv8433

@pooranjoyb
Ok ok
Got it

@pooranjoyb
now you can check it

check build errors by running npm run build in you local machine.

completed build

@pooranjoyb
now you can check this
i completed my task as you said
please check this and merge it

@pooranjoyb
deployment and build both are completed
please merge it

@pooranjoyb
Please when you become free
Merge it

@pooranjoyb
Please when you become free Merge it

Hii @dhruv8433 really sorry, I was occupied few days. Okay I've seen the deployment. Everything is working fine but just one improvement.

There are static images in the cart.
Make sure that, when Product is added to Cart it is should in the Cart page.
Use the slice or supabase-table to render the items added to cart.

That'll do. I'll merge once this part is done. 🚀

@pooranjoyb
i need help when i try to add product for same user it give me cors error
can you please tell me how to resolve this
can you allow cors from supabase ?

@pooranjoyb
i need help when i try to add product for same user it give me cors error can you please tell me how to resolve this
can you allow cors from supabase ?

please check in supabase. RLS is already disabled. I guess you already have an access. @dhruv8433

@pooranjoyb
i tried many times but i can't find allow origin cors in supabase dashboard
can you please help...

@pooranjoyb
now everything working as expected
please check this and merge it

output:

@pooranjoyb
https://github.com/pooranjoyb/popShop/assets/114583978/7f2a720e-871e-4a1e-9739-5166d3805293

@pooranjoyb
now you can merge it
please check everything working as expected

Awesome work @dhruv8433 🚀
What was the issue with cors tho ?

@pooranjoyb
no i just redisable RLS and try than it worked

please merge it

please merge it

Dude it ain't working, just checked the deployment. :/
screen-recorder-sun-jun-09-2024-18-59-44.webm

Please lmk if I'm missing something, do create a new record if the user doesnot exist in the table. @dhruv8433

@pooranjoyb
just wait i provide you a video

A hell loota work, init @dhruv8433 ? 😆
But yeah at the end its working. So, well done! 💯

Thank you @pooranjoyb
idk why video not downloaded bu thanks again

Thank you @pooranjoyb
idk why video not downloaded bu thanks again

But yeah there is still one issue. I guess that's probably easy to work around.

The functioning is working properly in a single browser but not in other browsers as you are fetching data from redux store.
while rendering the cart items fetch it from db and show.
Although the admin has two items in cart its not showing up in carts page.

@dhruv8433
you can work on this in a separate issue. 👍🏼

@pooranjoyb
Ok i will create separate issue for thay

repo: pooranjoyb/popShop


text:
feat: support projj list command.

close #57

cc @popomore

这个功能有点像 find

find 必须有搜索关键字，这个是可选的。
list 的搜索规则相比 find 更合理一点点，个人感觉。

authors: hotoo popomore

repo: popomore/projj


text:
fix: 試合表生成の修正

試合表の生成がバグる
エラーの内容
https://discord.com/channels/1098782049810259999/1180682418538151976/1293804909241700404

解決済み
理由: マイグレーションが適用されていないことが原因

repo: poporonnet/kcmsx


text:
BCFTools and BATCH_TMPDIR

https://github.com/populationgenomics/production-pipelines/blob/e02782bddc943f1402a7827f781aee0a209af716/cpg_workflows/jobs/vcf.py#L176
Based on @hopedisastro's experiments, bcftools doesn't add a slash here when using as a temp directory
https://batch.hail.populationgenomics.org.au/batches/431549/jobs/1
hail batch env variable:
{
    "name": "BATCH_TMPDIR",
    "value": "/io/batch/bdcc1f"
}

command:
bcftools sort --temp-dir $BATCH_TMPDIR

outputs:
buf_flush] Error: cannot write to /io/batch/bdcc1fWyLxsI/00003.bcf

I'm not sure if this is meaningful, but the temp path used isn't nested inside BATCH_TMPDIR, but is instead created at the same level. If it ain't broke, don't fix it, but I'm just flagging this here.
This would be corrected by using --temp-dir ${BATCH_TMPDIR}/

Closing for now, we can consider re-opening if it creates issues down the track. At the moment we can flag this as a 'known behaviour'.
Unless anyone actually wants the fix
CC @MattWellie

authors: MattWellie vivbak

repo: populationgenomics/production-pipelines


text:
Mirror

Is there a way to mirror parts (especially during/after/for external transform)?

yes, talk to neel he had the same question yesterday.  Use a negative
scaling value in x or y to scale your transformed part.
On Thu, Oct 6, 2016 at 5:12 PM, Kaushik Jayaram notifications@github.com
wrote:

Is there a way to mirror parts (especially during/after/for external
transform)?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/popupcad/popupcad/issues/103, or mute the thread
https://github.com/notifications/unsubscribe-auth/AH0ST4er7LmSCho5W7bYF3GfR7XLe8iTks5qxY5YgaJpZM4KQi91
.

--
Dan Aukes
idealab.asu.edu
Assistant Professor
The Polytechnic School
Fulton Schools of Engineering
Arizona State University

Cool! Thanks
Kaushik Jayaram
Harvard University
Cambridge, MA
Phone: +1 510 499 5164
On Thu, Oct 6, 2016 at 8:20 PM, danaukes notifications@github.com wrote:

yes, talk to neel he had the same question yesterday. Use a negative
scaling value in x or y to scale your transformed part.
On Thu, Oct 6, 2016 at 5:12 PM, Kaushik Jayaram notifications@github.com
wrote:

Is there a way to mirror parts (especially during/after/for external
transform)?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/popupcad/popupcad/issues/103, or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AH0ST4er7LmSCho5W7bYF3GfR7XLe8iTks5qxY5YgaJpZM4KQi91>
.

--
Dan Aukes
idealab.asu.edu
Assistant Professor
The Polytechnic School
Fulton Schools of Engineering
Arizona State University
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/popupcad/popupcad/issues/103#issuecomment-252123898,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACOXiq65dHgywbfSHa70I-bSPZuwFP44ks5qxZBbgaJpZM4KQi91
.

np
On Thu, Oct 6, 2016 at 5:24 PM, Kaushik Jayaram notifications@github.com
wrote:

Cool! Thanks
Kaushik Jayaram
Harvard University
Cambridge, MA
Phone: +1 510 499 5164
On Thu, Oct 6, 2016 at 8:20 PM, danaukes notifications@github.com wrote:

yes, talk to neel he had the same question yesterday. Use a negative
scaling value in x or y to scale your transformed part.
On Thu, Oct 6, 2016 at 5:12 PM, Kaushik Jayaram <
notifications@github.com>
wrote:

Is there a way to mirror parts (especially during/after/for external
transform)?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/popupcad/popupcad/issues/103, or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AH0ST4er7LmSCho5W7bYF3GfR7XLe8iTks5qxY5YgaJpZM4KQi91>
.

--
Dan Aukes
idealab.asu.edu
Assistant Professor
The Polytechnic School
Fulton Schools of Engineering
Arizona State University
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/popupcad/popupcad/issues/103#issuecomment-252123898
,
or mute the thread
<https://github.com/notifications/unsubscribe-
auth/ACOXiq65dHgywbfSHa70I-bSPZuwFP44ks5qxZBbgaJpZM4KQi91>
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/popupcad/popupcad/issues/103#issuecomment-252124425,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AH0ST0EmV3rJ5aA4dJeYSBoRJw7oYI-Tks5qxZFAgaJpZM4KQi91
.

--
Dan Aukes
idealab.asu.edu
Assistant Professor
The Polytechnic School
Fulton Schools of Engineering
Arizona State University

authors: danaukes kjayaram

repo: popupcad/popupcad


text:
Not loading the application

Hi,
I have simply just copied all your files into my local server and tried to launch them. However I got this error:
index.html:86 Uncaught ReferenceError: opc is not defined
    at index.html:86

Can you please fix it or help me point out what to edit?

Hi @zpoll92 thanks for the report, it should be fixed now.

repo: portablemind/grapesjs-code-editor


text:
Unauthorized error after reboot

Before you start please confirm the following.

[X] Yes, I've searched similar issues on GitHub.
[X] Yes, I've checked whether this issue is covered in the Portainer documentation or knowledge base.

Problem Description
Each time after rebooting the host machine, the portainer WebUI shows a Failure notification but does not allow for re-authentication. Assuming the portainer invalidated all the previous sessions but such action resulted in WebUI being completely frozen, the only way is to wait for 8 hours(default session lifetime) for the previous session to expire or to clear the browser cookie.
Expected Behavior
Allow for re-authentication using the regular login page.
Actual Behavior
WebUI froze with repeat Failure notifications.
Steps to Reproduce

log into the WebUI.
Reboot system.
Try to access the WebUI.

Portainer logs or screenshots

Portainer version
2.19.1
Portainer Edition
Business Edition (BE/EE) with 5NF / 3NF license
Platform and Version
Docker 24.0.6
OS and Architecture
Ubuntu 22.04， ARM64
Browser
Chrome Latest
What command did you use to deploy Portainer?
sudo docker run -d -p 9443:9443 --name=portainer \
    --restart=always \
    -v /var/run/docker.sock:/var/run/docker.sock \
    -v portainer_data:/data \
    portainer/portainer-ee:alpine

Additional Information
No response

I can't replicate this issue and reboot my host environments regularly - a simple page refresh is enough for me to get the login UI again. Is there anything special about your setup / browser configuration? Perhaps a browser extension?

I have been having this issue non stop after reboots and how I fixed it was by removing my security exception in the browser. this causes me to have to acknowledge the security risk again and then the login screen shows up.

I have been having this issue non stop after reboots and how I fixed it was by removing my security exception in the browser. this causes me to have to acknowledge the security risk again and then the login screen shows up.

Thanks for your information; it does sound like the problem that I was facing. As I have moved to using port 9000 and run it behind the Cloudflare tunnel, the issue seems to have been resolved.
Previously, I had Portainer running on port 9443 with the default self-signed certificate and Nginx reverse proxy/Cloudflare tunnel for managing incoming traffic and site certificate management.
@jamescarppe, should you find this behavior worth investigating further, I recommend delving deeper into the setup.

authors: jamescarppe kingbigmember sgrtye

repo: portainer/portainer

license: Zlib


text:
Unable to open Stats

hi
pl share OS, n docker version

Hi I tried on ubunto20.04 and docker 20.10 . stats shows for portainer. could u share your environment details.

 @srebala


text:
Recreating a container clears the access control user list

After pressing recreate on a container, if the option Access control is set to restricted, the newly created container would have an empty user list
Expected behavior
The user list to not be cleared
Technical details:

Portainer version: 2.5.1
Docker version (managed by Portainer): 20.10.5
Kubernetes version (managed by Portainer): None
Platform (windows/linux): Linux
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): default on the website
Browser: Chrome
Use Case (delete as appropriate): Using Portainer at Home.
Have you reviewed our technical documentation and knowledge base? Yes

Hi
is it swarm or standalone docker.please share screenshots

standalone

this occurs only when the admin presses recreate on the container, but not when the user does it

This issue is appearing again in 2.11.0

authors: albertoxamin srebala


text:
How can I get stories highlights?

I mean, not the usual stories (24 hours lifetime), but the special ones, like the "eternal stories".

Have you found how to get highlights?

Have you found how to get highlights?

Yes, but I write the solution in another programming language

It still can be helpful. Can you share it?

It still can be helpful. Can you share it?

I don't think it can help you, but here's a piece of code that parses the stories https://gist.github.com/Al-Muhandis/b2bc7550413437442cd1d4911f818cea

authors: AidasK Al-Muhandis

repo: postaddictme/instagram-php-scraper