Experiment Settings

Hello, author:
I would like to ask other methods (JOAO, etc.) are pre-trained on ZINC15 and then fine-tuned on eight datasets?

Hi @DuanhaoranCC , all the baselines (JOAO, etc) are pretrained on the GEOM dataset (only 2D topology is considered).


Create a layer of indirection for service and plan names

#802 explains that service and plan names can change across broker catalog refreshes. Since we need a stable reference, that issue suggests using the service and plan GUID to reference services and plans in the catalog. In the SIG call on 5/8/2017, many of us agreed that there is no other option.
I agree that using GUIDs to reference services and plans on the broker is the best and most reliable. I do, however, believe that doing so is:

A poor user experience for the person creating new Instances
Not portable across clusters, each of which may provide the same logical service with the same API (i.e. MySQL databases or S3-compatible object storage), but uses brokers that specify different service & plan GUIDs

To solve these two problems, I propose adding a layer of indirection (i.e. the solution to all problems in CS 😄 ) to map service-catalog service and plan names to the GUIDs.
This layer of indirection could be represented as two new resources: ServiceName and PlanName. These resources would be namespace-less (just like ServiceClasses and Brokers are right now), and look something like the following:
ServiceName
apiVersion: servicecatalog.k8s.io/v1alpha1
kind: ServiceName
metadata:
    name: CoolService
spec:
    serviceGUID: fab569db-2d06-4522-b4f6-4ff06f179e5e

PlanName
apiVersion: servicecatalog.k8s.io/v1alpha1
kind: PlanName
metadata:
    name: CoolPlan
spec:
    serviceName: CoolService # which service this is a plan of
    planGUID: 9220f523-7635-4361-86e9-f4af6a606d4f

Here are some considerations for these resources:

Either the operator can manually create these or the controller can automatically create them from the original (i.e. on the first catalog fetch) names of each service & plan name.
When a controller re-fetches a catalog from a broker, it's responsible for doing the following:

If the service is removed, then the corresponding ServiceName and all its PlanName resources should be "soft-deleted" (similar to the soft delete discussed in #801)
If the plan is removed, then the corresponding PlanName should be soft-deleted
If the service or plan GUID changed, then the corresponding GUID on the ServiceName or PlanName resource should be updated accordingly, and a new condition should be added to that ServiceName or PlanName to indicate that the update happened

A poor user experience for the person creating new Instances

Absolutely no disagreement there.  My gut says that I would rather solve that problem with porcelain commands (kubectl service-catalog provision <service display name> <plan display name>) than a new type of naming indirection.  See #704

Not portable across clusters, each of which may provide the same logical service with the same API (i.e. MySQL databases or S3-compatible object storage), but uses brokers that specify different service & plan GUIDs

I do not dispute that this is a valid problem, but I hesitate to introduce a new type of naming indirection to deal with it.  I think of this as being similar to StorageClass and label selectors on PVCs.  I know that this is something the you and Gabe have been talking about for a while.  Is that your primary interest?  If so it might pay to reframe the discussion around that.  I have called this problem 'trait-based provisioning' in the past and people seem to have thought that was a decent name for it.

A couple more thoughts on the 'trait-based provisioning' thing:

This seems to be the actual purpose of 'tags' in the OSB API, see https://github.com/kubernetes-incubator/service-catalog/issues/497 and https://github.com/openservicebrokerapi/servicebroker/blob/master/spec.md#service-objects
Since tags are not really a thing in k8s, I have discussed with @jwforres and a couple others at RH the idea of having a convention for brokers to communicate in service metadata about the k8s labels their services should have -- we could use label selectors for this concern if we did this
I do not actually know how CF uses (1), just for the record
I realized the other day that I have no idea how plans would work with a feature like this - since plans do not themselves have 'tags' in the OSB spec - have you had any thoughts in that area?

I know that this is something the you and Gabe have been talking about for a while. Is that your primary interest?

Good eye 😄  - I did have that problem in mind. I suggested this particular solution because I believe that it's more directly suited to solve the GUID problem, while still leaving open the possibility to later implement the trait-based system that we've spoken about before.
If "trait based provisioning" via a label-selector and StorageClass-like solution is what the group prefers to solve this specific problem, then I am ok with that as well.
I do, however, want to remove GUIDs from most standard workflows as soon as possible

You said:

If the service or plan GUID changed, then the corresponding GUID on the ServiceName or PlanName resource should be updated accordingly, and a new condition should be added to that ServiceName or PlanName to indicate that the update happened

can you elaborate on this? GUIDs never change.  If you mean, a service as deleted and a new service was created that "looks the same", can you elaborate on how we determine they "look the same" ?

Is this something that can be done client side with kubectl extensions?

@MHBauer check out: https://github.com/kubernetes-incubator/service-catalog/issues/837#issuecomment-300925516

@arschles can we store those mappings inside ServiceClass (or Broker, not sure which one is more appropriate) instead of having separate resources?

/remove-lifecycle rotten
/lifecycle frozen

This project is being archived, closing open issues and PRs.
Please see this PR for more information: https://github.com/kubernetes/community/pull/6632


Full-Stack Reactive Website in Django (no JavaScript)

Article checklist
Pre-submission checks

Please ensure that you have only one open topic suggestion (issue) + in-review article (linked pull request) at a time. This will ensure that we complete the review process in a timely manner from inception to publishing

If you have not already, please go over our Resources Page for more tips and tricks on how to improve your overall technical writing so reviews are swifter, increase the chance of a payout and provide more value to our readers.

For first-time contributors and for more details on our submission guidelines, see our Contributing Guidelines.

Formatting and structure checks

[x] Have you used the correct folder and file structure? - see Contribution Guidelines

[x] Is your article properly formatted in Markdown? - see Github Markdown guide

[x] Have you used our preferred heading structure? - H3 (###) and up

[x] Does your article follow any of the suggested structure formats? - see example formats

[x] Is your article over 750 words? - Tool: Wordcounter.net

[x] Is the article you are submitting an in-depth and unique article? Does it go beyond what is in the official docs and what is covered in other blog sites. See these articles as examples.

[x] Does your article provide enough value and detail about your topic? - Articles should be clear, accurate, and fully explained.

[x] Can your article be understood by beginners? - Assume the audience is smart but has no prior exposure to the common terminology in your article.

[x] Have you included a hero image that is 600x400 pixels and have the copyright to use it? - Tools: Pixlr Image Editor for resizing and Unsplash for Creative Commons images

Grammar & plagiarism checks

[x] Have you spellchecked and grammar checked your article? - Tools: Write&Improve - ProWritingAid - Grammarly
[ ] Please place your article through a 3rd party plagiarism checker. We suggest using Quetext, this tool is free and has a daily limit. We typically accept articles with 10% or less.
[ ] Have you checked your article for readability? - Tool: Hemmingway
[x] Have you added sources for quotes and images that aren't yours?

Technical checks

[x] Are your code snippets properly formatted for syntax highlighting - see Syntax guide
[ ] Have you checked your code runs correctly and you've highlighted all necessary dependencies for installation?
[x] Are the software programs and packages you're highlighting in your article up to date, using current versions and not deprecated?

Topic suggestion this closes

Remove the backticks and add the issue number below to link and close your Topic Suggestion (issue) when your article has been published (PR has been merged). See this video for more details.

This closes #3658

Finally, delete the article checklist notes in blockquotes and submit your PR. We look forward to reviewing your article.

@ahmadmardeni1 requesting to review this article

You are NOT a test peer reviewer. @Samuel-2626
cc @hectorkambow

👋  Good afternoon everyone - my mistake @ahmadmardeni1
Samuel - did in fact reach out to do a test review back in August.
Samuel - as an FYI - we have filled up most if not all peer reviewer positions - but we are currently working on growing the entire EngEd program and this will expand the peer reviewer team.
As mentioned - I'll be sure to add your name to our list of interested community members - and we can use any test review (you may had already performed as an indicator ) for next time.
If I recall correctly - we were going to keep a keen eye on your next published article to better gauge the incoming correct?
@Samuel-2626
cc @ahmadmardeni1

Good afternoon everyone - my mistake @ahmadmardeni1
Samuel - did in fact reach out to do a test review back in August.
Samuel - as an FYI - we have filled up most if not all peer reviewer positions - but we are currently working on growing the entire EngEd program and this will expand the peer reviewer team.
As mentioned - I'll be sure to add your name to our list of interested community members - and we can use any test review (you may had already performed as an indicator ) for next time.
If I recall correctly - we were going to keep a keen eye on your next published article to better gauge the incoming correct?
I do not recall if you performed any test reviews.
@Samuel-2626
cc @ahmadmardeni1

Hello @hectorkambow, I think @Samuel-2626 is the author of the article not the test reviewer.

Am the one who had requested to review the article

@dentonya 👍
Similar to my message via DM on slack - we can not (at the moment) process or train any more peer reviewers as most positions have been filled or in the process of being filled.
We will be looking to add more to the team in the near future as we grow the EngEd program 🚀
👍

Sorry, we are not talking about Samuel. He is the author. @hectorkambow @mercymeave
The student who asked for a test review deleted his comment.

Upon running your article through our 3rd party plagiarism checker it seemed to raise a few flags and the % was higher than we typically accept.
Please see attached PDF - and revisit the article to ensure we are contributing wholly unique and original content.
Be sure to see our resources page to see more info on plagiarism and what is considered as such.
Full-Stack Reactive Website in Django (no JavaScript)

@ahmadmardeni1 Most of this red flags are from the docs of unicorn and I did make reference to them in the article.
Thoughts?

@mercymeave any update

Hi, @mercymeave any update

Hi, @mercymeave any update

Working on it.

Plagiarism check done ✅


update inscribers and add unavailable cases

Codecov Report
Patch and project coverage have no change.

Comparison is base (366caa9) 100.00% compared to head (d21a346) 100.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##               1.5     #1104     +/-   ##
===========================================
  Coverage   100.00%   100.00%
===========================================
  Files           46        21     -25
  Lines         2414      1230   -1184
  Branches       354       220    -134
===========================================
- Hits          2414      1230   -1184

Flag
Coverage Δ

production
?

reference
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 25 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


More Test Cases

[x] Update Favourite Command Test Cases
[x] Update UnFavourite Command Test Cases

Codecov Report

Merging #255 (a99e315) into master (efcde33) will increase coverage by 1.20%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##             master     #255      +/-   ##
============================================
+ Coverage     65.39%   66.60%   +1.20%
- Complexity      746      764      +18
============================================
  Files           111      111
  Lines          3534     3536       +2
  Branches        320      322       +2
============================================
+ Hits           2311     2355      +44
+ Misses         1109     1063      -46
- Partials        114      118       +4

Impacted Files
Coverage Δ

...seedu/address/logic/commands/FavouriteCommand.java
88.88% <0.00%> (+59.47%)
:arrow_up:

...edu/address/logic/commands/UnfavouriteCommand.java
88.88% <0.00%> (+59.47%)
:arrow_up:

...rc/main/java/seedu/address/model/ModelManager.java
84.28% <0.00%> (+8.57%)
:arrow_up:

src/main/java/seedu/address/model/AddressBook.java
83.87% <0.00%> (+12.90%)
:arrow_up:

...a/seedu/address/model/person/UniquePersonList.java
86.88% <0.00%> (+19.67%)
:arrow_up:

Continue to review full report at Codecov.

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


Handtracking Support, Parent a 3D Cube to the index finger

Plugin Version or Commit ID
v0.12.0
Unity Version
2022.3
Your Host OS
MacOS
Target Platform
UnityEditor, iOS
Description
I'm trying to parent a cube and have it track to the position of a finger and match the joint position and rotation, I'm a little confused on how to extract that position and make a simple 3D model be a child of it and be parented to it.
I looked at the MultiHandLandmarkListAnnotation class, and tried placing it in the draw function:

I see the cube start to follow my finger but it doesn't look like it's matching one to one:

Code to Reproduce the issue
No response
Additional Context
No response

You don't need to modify *Annotation classes since you can access the value without them.
synchronously
https://github.com/homuler/MediaPipeUnityPlugin/blob/01cdd567ac5939b81114e27e8c13a92bde8275f4/Assets/MediaPipeUnity/Samples/Scenes/Hand Tracking/HandTrackingSolution.cs#L79
or asynchronously (callback)
https://github.com/homuler/MediaPipeUnityPlugin/blob/01cdd567ac5939b81114e27e8c13a92bde8275f4/Assets/MediaPipeUnity/Samples/Scenes/Hand Tracking/HandTrackingSolution.cs#L103-L106

Sorry still a little confused, how would I be able to get the landmarks transform properties from them?

To get the local position, please read https://github.com/homuler/MediaPipeUnityPlugin/wiki/Getting-Started#get-landmarks.
If you want to get the rotation, which is not returned by MediaPipe, you need to calculate it by yourself.

Plugin Version or Commit ID
v0.12.0
Unity Version
2022.3
Your Host OS
MacOS
Target Platform
UnityEditor, iOS
Description
I'm trying to parent a cube and have it track to the position of a finger and match the joint position and rotation, I'm a little confused on how to extract that position and make a simple 3D model be a child of it and be parented to it.
I looked at the MultiHandLandmarkListAnnotation class, and tried placing it in the draw function:
I see the cube start to follow my finger but it doesn't look like it's matching one to one:

### Code to Reproduce the issue
_No response_
Additional Context
No response

Thanks for you logic, i very long find in others resourse how i can move objects with detection and u help me bro, you cool

To get the local position, please read https://github.com/homuler/MediaPipeUnityPlugin/wiki/Getting-Started#get-landmarks.
If you want to get the rotation, which is not returned by MediaPipe, you need to calculate it by yourself.

you are right, this does not work synchronously, in the case when you edit the annotation, but I do not understand how exactly you propose to do this, I must call these functions from another created class
or contact handtrakingsolution, in the handtraking scene example, how to achieve this?


Add vue-devtools export support

As a developer I want to send the current state to a colleague.

[ ] Add query location parser
[ ] Add option to paste the current state to the console
[ ] Add option to import the current state from the clipboard

Will focus on shadow dom tools and deprecate the vue-devtools


How to use this without updating? Every time Auto1111 updates something breaks.

I want to use without updating. anybody know how to do it?

Warning: Taming Transformers not found at path /content/gdrive/MyDrive/sd/stablediffusion/src/taming-transformers/taming
Warning: CodeFormer not found at path /content/gdrive/MyDrive/sd/stablediffusion/src/codeformer/inference_codeformer.py
Traceback (most recent call last):
  File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 15, in <module>
    from modules import shared, devices, sd_samplers, upscaler, extensions, localization, ui_tempdir
  File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_samplers.py", line 12, in <module>
    from modules import prompt_parser, devices, processing, images
  File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/processing.py", line 30, in <module>
    from blendmodes.blend import blendLayers, BlendType
ModuleNotFoundError: No module named 'blendmodes'

me error

fixed

fixed

thanks! I uninstalled everything from gdrive and reinstalled. same problem. model version 1.5
Traceback (most recent call last):   File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 15, in <module>     from modules import shared, devices, sd_samplers, upscaler, extensions, localization, ui_tempdir   File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_samplers.py", line 12, in <module>     from modules import prompt_parser, devices, processing, images   File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/processing.py", line 30, in <module>     from blendmodes.blend import blendLayers, BlendType ModuleNotFoundError: No module named 'blendmodes'

same here
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 15, in
from modules import shared, devices, sd_samplers, upscaler, extensions, localization, ui_tempdir
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_samplers.py", line 12, in
from modules import prompt_parser, devices, processing, images
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/processing.py", line 30, in
from blendmodes.blend import blendLayers, BlendType
ModuleNotFoundError: No module named 'blendmodes'

https://colab.research.google.com/github/TheLastBen/fast-stable-diffusion/blob/main/fast_stable_diffusion_AUTOMATIC1111.ipynb

https://colab.research.google.com/github/TheLastBen/fast-stable-diffusion/blob/main/fast_stable_diffusion_AUTOMATIC1111.ipynb

Ben Thanks I will test it now. Is there anyway to use without updating? I do not want to update and redo all of my settings every time.

now I get this error:
/usr/local/lib/python3.8/dist-packages/scipy/__init__.py:146: UserWarning: A NumPy version >=1.16.5 and <1.23.0 is required for this version of SciPy (detected version 1.24.0   warnings.warn(f"A NumPy version >={np_minversion} and <{np_maxversion}" Traceback (most recent call last):   File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 195, in <module>     webui()   File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 133, in webui     initialize()   File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 63, in initialize     modules.sd_models.load_model()   File "/content/gdrive/.shortcut-targets-by-id/1s72GKp1yYc5oo43L_IfY9bA5zjP3mUIu/sd/stable-diffusion-webui/modules/sd_models.py", line 284, in load_model     checkpoint_info = checkpoint_info or select_checkpoint()   File "/content/gdrive/.shortcut-targets-by-id/1s72GKp1yYc5oo43L_IfY9bA5zjP3mUIu/sd/stable-diffusion-webui/modules/sd_models.py", line 115, in select_checkpoint     if len(model_checkpoint) == 0: TypeError: object of type 'NoneType' has no len()

@tamal777 create a copy of one from history
you may need to mod the files to revert to specific version with
git revert <oldercommitversionofwebui>

https://github.com/TheLastBen/fast-stable-diffusion/commits/main/fast_stable_diffusion_AUTOMATIC1111.ipynb
@tamal777 create a copy of one from history
you may need to mod the files to revert to specific version with
git revert <oldercommitversionofwebui>

thanks

/usr/local/lib/python3.8/dist-packages/scipy/init.py:146: UserWarning: A NumPy version >=1.16.5 and <1.23.0 is required for this version of SciPy (detected version 1.24.0
warnings.warn(f"A NumPy version >={np_minversion} and <{np_maxversion}"
Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 195, in
webui()
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 133, in webui
initialize()
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 63, in initialize
modules.sd_models.load_model()
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_models.py", line 284, in load_model
checkpoint_info = checkpoint_info or select_checkpoint()
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_models.py", line 115, in select_checkpoint
if len(model_checkpoint) == 0:
TypeError: object of type 'NoneType' has no len()

now I get this error, deleted all previous folders before, so it can start fresh:

same here

/usr/local/lib/python3.8/dist-packages/scipy/init.py:146: UserWarning: A NumPy version >=1.16.5 and <1.23.0 is required for this version of SciPy (detected version 1.24.0 warnings.warn(f"A NumPy version >={np_minversion} and <{np_maxversion}" Traceback (most recent call last): File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 195, in webui() File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 133, in webui initialize() File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 63, in initialize modules.sd_models.load_model() File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_models.py", line 284, in load_model checkpoint_info = checkpoint_info or select_checkpoint() File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/sd_models.py", line 115, in select_checkpoint if len(model_checkpoint) == 0: TypeError: object of type 'NoneType' has no len()

now I get this error, deleted all previous folders before, so it can start fresh:

same here

I also get this error after a SD delete and rerun

Same.

Same

same

My python is very bad and pardon me but my git is too because i only do sall hobbyist projects.
It looks like v2 checkpoint specific issue? I was able to get around this by going into stable-diffusion-webui/sd_models.py
at line 112 "def select_checkpoint()"...
replacing with:
`model_checkpoint = {}  # initialize model_checkpoint as an empty dictionary
def select_checkpoint():
global model_checkpoint
model_checkpoint = model_checkpoint or {}  # assign default value if model_checkpoint is None
if len(model_checkpoint) == 0:
# code to handle empty model_checkpoint
model_checkpoint = shared.default_sd_model_file`

https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/5974

AUTOMATIC1111/stable-diffusion-webui#5974

pardon

this is actually the issue in A1111 : https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/5971

sorry for asking, where do i insert this ?
git revert

you don't have to, just do a clean run with the latest colab

you don't have to, just do a clean run with the latest colab

I don't want to reinstall SD for each update. how to stay on the working version?

A1111 merged a dozen pull requests today, it doesn't happen everyday

Could you teach me how to use an old version?

https://github.com/TheLastBen/fast-stable-diffusion/commits/main/fast_stable_diffusion_AUTOMATIC1111.ipynb
@tamal777criar uma cópia de um da história
você pode precisar modificar os arquivos para reverter para uma versão específica com
git revert <oldercommitversionofwebui>

could you teach me how to use this command to use an old version?


Error while processing kite#events

User reported that he's seeing an error on every keystroke:

Problem still persists
My copilot version: 2.20190509.1
Nvim v0.3.4
I reinstall vim-plugin by copilot
Error message appears on every movement

This is a weird error and not a part of the code that I'd expect to cause problems.
The problem is occurring when the plugin tries to send an event to Kite asynchronously.
In this case neovim is unable to start a background job because, evidently, the argument list is too long.  The event payload contains the buffer contents, but only if it's less than 1MB.  This seems to suggest that the user's sh shell (or OS?) limits the size on argument (or the whole list?) to less than 1MB, but I'm guessing here.
Please could you ask the user what OS they use and what sh --version gives?

Same issue over here. Happens on Ubuntu 18.04 while sh points to dash 0.5.8-2.10. Changing to bash would make no difference, because we run into some kernel level limitations here.
One of the files affected by this issue has a size of 178904 bytes.
The limiting factor in this case is not the whole argument list, but the limit for a single argument (MAX_ARG_STRLEN). Have a look at https://serverfault.com/questions/163371/linux-command-line-character-limit for further information. Seems to be 131072 bytes per argument.
Enabling debug logging gives me the following line in kite-vim.log:
> /home/lm/.config/nvim/pack/kite/start/vim-plugin/lib/linux/kite-http --timeout 120ms --post --data '{"selections": [{"end": 57931, "start": 57931}], "source": "vim", "action": "selection", "editor_version": "NVIM v0.4.0-dev", "plugin_version": "1.0.32", "text": "(...)", "filename": "(..)"}' 'http://<IP_ADDRESS>:46624/clientapi/editor/event'

Pretty clear: The issue here is that the data is handed over to kite-http via command line arguments.
To really solve the problem the whole post data should be handed over via stdin to kite-http instead.

@LarsMichelsen Thanks for the useful info.

To really solve the problem the whole post data should be handed over via stdin to kite-http instead.

I agree.
@jansorg This would be an easy change for the plugin – are you happy for me to go ahead?  Who would you like to update kite-http?

@airblade Yes, this sounds like a good way to fix this. Please go ahead. If you're happy with Go then feel free to do the change as you could immediately test your change. If you preferred not to fix things in Go then I'd be happy to implement this.

Done in #185.


RqHref should pay attention to X-Forwarded-Proto

X-Forwarded-Proto header should be taken into account.

The job #815 assigned to @yegor256/z, here is why. The budget is 30 minutes, see §4. Please, read §8 and §9. If the task is not clear, read this and this.

Bug was reported, see §29: +15 points just awarded to @yegor256/z

@rultor release, tag is 1.8.3

Manual assignment of issues is discouraged, see §19: -5 points just awarded to @yegor256/z

It is strongly discouraged to assign jobs to their creators, see §19: -15 points just awarded to @yegor256/z

@rultor release, tag is 1.8.3

@yegor256 OK, I will release it now. Please check the progress here

@rultor release, tag is 1.8.3

@yegor256 Done! FYI, the full log is here (took me 12min)

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

@yegor256 According to QA Rules:

Problem reporter and problem solver are two different persons

In this ticket you were the reporter and solver.

Some of ticket messages must mention all pull requests where the problem was actually fixed.

There was no PR created for this issue, so the link is not included.
Please, try to avoid such issues in future.

@0crat quality acceptable

The job #815 is now out of scope

Order was finished: +30 points just awarded to @yegor256/z


Mechanism to override body replace

This commit keeps the default behaviour but lets you override the default behaviour of replacing the body tag.
Here's an example of me overriding the default behaviour.
$ ->
  $(document).on 'page:replace', (e) ->
    turboElement = document.getElementById 'turbolinks-replace'
    newTurboElement = $(e.originalEvent.data.html).find('#turbolinks-replace')[0]
    turboElement.parentElement.replaceChild newTurboElement, turboElement
    false #cancel default turbo link replace

I've got a long running video background I don't want reloaded every page replace.
https://github.com/rails/turbolinks/pull/204, I also ran into the page caching issue described here when overriding the default behaviour

Closing in favor of the partial page replacement feature introduced in v3.0.  Should give you the functionality you need.


Vulnerability roundup 108: mysql-8.0.26: 38 advisories [7.1]

search, files

[ ] CVE-2021-35610 CVSSv3=7.1 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35597 CVSSv3=6.5 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35607 CVSSv3=6.5 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35612 CVSSv3=5.5 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35608 CVSSv3=5.3 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35602 CVSSv3=5.0 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-2478 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-2479 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35546 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35575 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35577 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35591 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35596 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35622 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35624 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35626 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35627 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35628 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35630 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35631 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35634 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35635 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35636 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35637 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35638 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35641 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35642 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35643 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35644 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35645 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35646 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35647 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35648 CVSSv3=4.9 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35632 CVSSv3=4.4 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35623 CVSSv3=2.7 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35625 CVSSv3=2.7 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35633 CVSSv3=2.7 (nixos-21.05, nixos-unstable)
[ ] CVE-2021-35640 CVSSv3=2.7 (nixos-21.05, nixos-unstable)

CVE details
CVE-2021-35610
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 7.1 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H).
CVE-2021-35597
Vulnerability in the MySQL Client product of Oracle MySQL (component: C API). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Client. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Client. CVSS 3.1 Base Score 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35607
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 6.5 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35612
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.5 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:H).
CVE-2021-35608
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Group Replication Plugin). Supported versions that are affected are 8.0.26 and prior. Difficult to exploit vulnerability allows low privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 5.3 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35602
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Options). Supported versions that are affected are 8.0.26 and prior. Difficult to exploit vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server as well as unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 5.0 (Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:N/I:L/A:H).
CVE-2021-2478
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-2479
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35546
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Replication). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35575
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35577
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via MySQL Protcol to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35591
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DML). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35596
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Error Handling). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35622
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Encryption). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35624
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges). Supported versions that are affected are 5.7.35 and prior and 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL Server accessible data. CVSS 3.1 Base Score 4.9 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N).
CVE-2021-35626
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35627
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35628
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35630
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Options). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized creation, deletion or modification access to critical data or all MySQL Server accessible data. CVSS 3.1 Base Score 4.9 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N).
CVE-2021-35631
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: GIS). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35634
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35635
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35636
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35637
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: PS). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35638
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35641
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35642
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35643
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35644
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35645
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35646
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35647
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Optimizer). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35648
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: FTS). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.9 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35632
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Data Dictionary). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with logon to the infrastructure where MySQL Server executes to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a hang or frequently repeatable crash (complete DOS) of MySQL Server. CVSS 3.1 Base Score 4.4 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:H).
CVE-2021-35623
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Roles). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Server accessible data. CVSS 3.1 Base Score 2.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N).
CVE-2021-35625
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Security: Privileges). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized read access to a subset of MySQL Server accessible data. CVSS 3.1 Base Score 2.7 (Confidentiality impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N).
CVE-2021-35633
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: Logging). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized ability to cause a partial denial of service (partial DOS) of MySQL Server. CVSS 3.1 Base Score 2.7 (Availability impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:N/A:L).
CVE-2021-35640
Vulnerability in the MySQL Server product of Oracle MySQL (component: Server: DDL). Supported versions that are affected are 8.0.26 and prior. Easily exploitable vulnerability allows high privileged attacker with network access via multiple protocols to compromise MySQL Server. Successful attacks of this vulnerability can result in unauthorized update, insert or delete access to some of MySQL Server accessible data. CVSS 3.1 Base Score 2.7 (Integrity impacts). CVSS Vector: (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N).

Scanned versions: nixos-21.05: 4f37689c8a2; nixos-unstable: 942eb9a335b.
Cc @orivej

We no longer support nixos-21.05, but this has been fixed in the currently supported NixOS versions:

nixos-22.05: mysql-8.0.29, mysql-5.7.39
nixos-unstable: mysql-5.7.39, mysql-8.0.30


Fix the Mongo expireAt field for RememberMe TGTs

The Mongo Ticket Registry applies a Mongo expire index on the expireAt field.  Currently the expireAt field is based on the expiration policy's TTL.  In the case of a Remember Me policy TTL the active TTL depends on the TicketState whereas the existing code will only ever retrieve the default TTL.  Consequently, mongo will now delete Remember Me tickets based on this default TTL expireAt index before the Remember Me time period has expired.  This change allows the Mongo Registry to query the Ticket TTL based on the ticket attributes and therefore set the correct expireAt value.

Could you please update the PR with:

A summarized issue description.
A brief overview of how the solution manages to fix the problem.

Thank you.

@mmoayyed done

Wonderful. Looks like one last remaining issue before the final merge:
> Task :core:cas-server-core-tickets-api:checkstyleMain
[ant:checkstyle] [ERROR] /home/travis/build/apereo/cas/core/cas-server-core-tickets-api/src/main/java/org/apereo/cas/ticket/support/BaseDelegatingExpirationPolicy.java:91:5: Missing a Javadoc comment. [JavadocMethod]
> Task :core:cas-server-core-tickets-api:checkstyleMain FAILED
> Task :core:cas-server-core-util:checkstyleMain
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':core:cas-server-core-tickets-api:checkstyleMain'.
> Checkstyle rule violations were found. See the report at: file:///home/travis/build/apereo/cas/core/cas-server-core-tickets-api/build/reports/checkstyle/main.html
  Checkstyle files with violations: 1
  Checkstyle violations by severity: [error:1]


Added Complete NodeJS + ExpressJS + MongoDB Course by Complete Coding by Prashant Sir to free-courses-hi.md

What does this PR do?
Add Complete NodeJS + ExpressJS + MongoDB  🚀🔥 Course ❤ in Hindi | Notes | Certification by Complete Coding by Prashant Sir to free-courses-hi.md
For resources
Description
Why is this valuable (or not)?
How do we know it's really free?
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

@eshellman I've removed the emojis. Could you please check if it's ready to be merged?


[SECURITY CONCERN] mixpanel autotracking password field

We received an email from the Mixpanel Security Team informing us that the auto-track feature was tracking the password field. They suggested updating to the latest version of but I can't find any record of that being addressed in this repository. Can anyone confirm if this vulnerability affected the javascript library as well as the mobile SDKs?

Thanks for reaching out. We're in the process of releasing that change now, sorry for the delay.

We've just released version 2.16.0, which contains the fix. Thanks for your patience.

Also, to clarify: the issue only affects the JS SDK, and not the mobile SDKs.

Any word when this will be available on npm?

@joealcorn Available on NPM now.

Excellent, thank you


How do we have different formatting on tags

I read a similar request to format the entire line, but all I care about is different colors for different tags.  In Plaintasks, I use red, orange, yellow and green for the states @critical, @high, @low, @today - respectively.
I tried adding the following style like you posted in another issue:
atom-text-editor::shadow, atom-text-editor {
  .source.todo {
    .attribute.urgent &{
      color: red;
    }
  }
}

However, they are still blue....

I don't think you need the extra & there. It should work if you do:
atom-text-editor::shadow, atom-text-editor {
  .source.todo {
    .attribute.urgent {
      color: red;
    }
  }
}

That was it.  Thank-you!!
Where can I find a list of the attributes I can style or have over-ride my theme settings?

The structure of the grammar means that the class is actually set to whatever the attribute is! So if you can make it an attribute, you can style it directly. In your example, @high would have a class of .attribute.high. If you aren't sure, you can open the dev tools (cmd-option-i) and inspect the tag itself to see what the class is.


breaking(linux) Update debian images to bookworm

Fixes https://github.com/jenkinsci/docker/issues/1686
Testing done
Built one of the images locally and checked it was using bookworm

### Submitter checklist
- [ ] Make sure you are opening from a **topic/feature/bugfix branch** (right side) and not your main branch!
- [ ] Ensure that the pull request title represents the desired changelog entry
- [ ] Please describe what you did
- [ ] Link to relevant issues in GitHub or Jira
- [ ] Link to relevant pull requests, esp. upstream and downstream changes
- [ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

@timja I'll let you merge once you're happy with the change / approval


Support pull request target

Adding new PR against 1.3 - follows: https://github.com/Madrapps/jacoco-report/pull/6
pull_request_target allows you to run GHA across forks - which is insecure for public repositories but useful for enterprise or private repos.
This PR adds support for this GHA event.
I'm not entirely sure how to verify that this event supports the same payload as pull_request

Thanks @chrsr . Will go through and merge this, sometime this weekend.


Outdated instructions

Screenshots and instructions are slightly outdated for the "Connect a bot to Facebook Messenger" part

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

ID: 0199d414-87e1-e32d-b528-ee9d2e03c54e
Version Independent ID: f88f4b08-0977-baee-5226-844695828b95
Content: Connect a bot to Facebook Messenger - Bot Service
Content Source: articles/bot-service-channel-connect-facebook.md
Service: bot-service
GitHub Login: @Kaiqb
Microsoft Alias: kamrani

Hi @turbozapekanka Thanks for reporting the issue. If you are looking for information about using Facebook adapter, please check here. Also, docs for Facebook adapter will be available soon.

FYI. Docs for custom sdk adapters (Facebook / Twilio) are WIP in PR #1923

PR 1923 was merged and closing the issue.


⚠ Bofrost.at has degraded performance

In 52d2949, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1931 ms

Resolved: Bofrost.at performance has improved in 4e26ef9.


Feature Request: Specify snapshot directory

I'm working on a project that needs to snapshot multiple things for each test. I'd like to build some thin utility functions around the snapshots, but this results in them being placed within a utility folder.
I'm not sure what the mechanism might be, but I'd like to be able to specify where my snapshots are stored.

is there any way to get current test context from Rust test runner?
i would expect snapshots to be stored in some nested directory that is also namespaced by target
e.g.
snapshots/wasm/my_test.snap
snapshots/darwin/my_test.snap

Under what circumstances would you expect the snapshots to be different by target?

i was thinking about testing default configuration based on the target.
e.g. if you're running a binary, grab that thing from the file system, if it's a wasm module, grab it from an ajax request etc.
although that might be better handled on a case by case basis manually to avoid extra complexity

Right - I with many libraries you'd want the same behavior on all targets. Where you want different behavior, you could supply different snapshot names.
Maybe there's an abstraction that would make this case easier, but I wouldn't think we'd want a different path for each target by default...

I started work on thread local settings support. This could be used to move the snapshots elsewhere.


[lc_ctrl/dv] Enable CDC instrumentation

The lc_ctrl block-level DV environment has been cleaned up and should now tolerate skew introduced as part of the CDC instrumentation.
Refer to #16689 for context.

Hm... I just ran this with multiple seeds locally (Xcelium). Looks like there are still some mismatches:
ERROR: [Scheduler] [00:02:32]: [run]: [status] [lc_ctrl:3.lc_ctrl_jtag_csr_aliasing.231037738: F]
ERROR: [Scheduler] [00:05:19]: [run]: [status] [lc_ctrl:5.lc_ctrl_sec_mubi.2086755826: F]
ERROR: [Scheduler] [00:08:07]: [run]: [status] [lc_ctrl:7.lc_ctrl_jtag_csr_aliasing.1269372366: F

Especially the lc_ctrl_jtag_csr_aliasing sounds interesting.
I will give this a closer look tomorrow.

Hm... I just ran this with multiple seeds locally (Xcelium). Looks like there are still some mismatches:
ERROR: [Scheduler] [00:02:32]: [run]: [status] [lc_ctrl:3.lc_ctrl_jtag_csr_aliasing.231037738: F]
ERROR: [Scheduler] [00:05:19]: [run]: [status] [lc_ctrl:5.lc_ctrl_sec_mubi.2086755826: F]
ERROR: [Scheduler] [00:08:07]: [run]: [status] [lc_ctrl:7.lc_ctrl_jtag_csr_aliasing.1269372366: F

Especially the lc_ctrl_jtag_csr_aliasing sounds interesting. I will give this a closer look tomorrow.

Thank you for looking into this @msfschaffner, if it is not design issue, maybe we can fix the dv tb post M2.5?

Hm... I just ran this with multiple seeds locally (Xcelium). Looks like there are still some mismatches:
ERROR: [Scheduler] [00:02:32]: [run]: [status] [lc_ctrl:3.lc_ctrl_jtag_csr_aliasing.231037738: F]
ERROR: [Scheduler] [00:05:19]: [run]: [status] [lc_ctrl:5.lc_ctrl_sec_mubi.2086755826: F]
ERROR: [Scheduler] [00:08:07]: [run]: [status] [lc_ctrl:7.lc_ctrl_jtag_csr_aliasing.1269372366: F

Especially the lc_ctrl_jtag_csr_aliasing sounds interesting. I will give this a closer look tomorrow.

Thank you for looking into this @msfschaffner, if it is not design issue, maybe we can fix the dv tb post M2.5?

I am not sure whether it is a DV or design issue - need to take another look tomorrow.

Hm... I just ran this with multiple seeds locally (Xcelium). Looks like there are still some mismatches:
ERROR: [Scheduler] [00:02:32]: [run]: [status] [lc_ctrl:3.lc_ctrl_jtag_csr_aliasing.231037738: F]
ERROR: [Scheduler] [00:05:19]: [run]: [status] [lc_ctrl:5.lc_ctrl_sec_mubi.2086755826: F]
ERROR: [Scheduler] [00:08:07]: [run]: [status] [lc_ctrl:7.lc_ctrl_jtag_csr_aliasing.1269372366: F

Especially the lc_ctrl_jtag_csr_aliasing sounds interesting. I will give this a closer look tomorrow.

Thank you for looking into this @msfschaffner, if it is not design issue, maybe we can fix the dv tb post M2.5?

I am not sure whether it is a DV or design issue - need to take another look tomorrow.

@msfschaffner I looked at errors. Can you wait for me? I will let you know sometime tomorrow.

@msfschaffner I looked at errors. Can you wait for me? I will let you know sometime tomorrow.
Sure no problem :)

Closing, since this will be superseded by #18873


Internal Server Error for release downloads hosted on pivotal.io

Downloads from the https://github.com/cloudfoundry/cli/releases page are broken - Internal Server Error is displayed.

I'm not able to reproduce this.  Are you downloading a binary or installer file?  Which OS?

All installers & binaries from here:
https://github.com/cloudfoundry/cli/releases/tag/v6.10.0
On Wed, Mar 25, 2015 at 10:49 PM, greg oehmen<EMAIL_ADDRESS>wrote:

I'm not able to reproduce this. Are you downloading a binary or installer
file? Which OS?
—
Reply to this email directly or view it on GitHub
https://github.com/cloudfoundry/cli/issues/392#issuecomment-86228878.

--
Balázs
[image: View my profile on LinkedIn]View Balázs Orbán's profile
http://www.linkedin.com/in/orbanbalage
<EMAIL_ADDRESS>+421 908 457 183

A warning should be put on the download page to use another browser than Chrome until something is fixed.

This seems to be resolved now. Closing this.

I'm on Chrome Version 43.0.2357.124 m
and the issue still persists.

I confirm the issue. Only in Chrome, Firefox working fine.

It works for me on Chrome on the Mac. Still need to re-test on Windows.


Client don't close connection if tasks are lost during sending process

Infinite client connection when mongoDB pod is killed during the sending of session
Step to reroduce:

Start a session with 1000 task
Kill mongoDB pod or Node where mongoDB is located
Look on armonikGUI to see if some tasks as been lost during process (Should be writed for exemple "total task = 997")
Wait for the task to end
When it's done server side. The client should not end session and wait for the "3" remaining lost task indefinetely

Expected behavior:
Should end the session after session ended server side and notify the client that some tasks as been lost
GUI screenshot :

Task lost log during process:
SuccessNotAllTask.txt

Hi, which version of ArmoniK.Extension.Csharp are you using ?
From the logs you sent it looks like an old version. Can you check if the issue is present with the 0.8.2 version ?
I also need a few more information:

Do you kill MongoDB near the start of the send ? Near the end ?
Your typical payload size
Which api are you using ? Unified or Symphony


Undefined variable: dataTypeContent (View: C:\wamp\www.....\edit-add.blade.php) when adding new record in a newly created table/bread.

Voyager version: 0.10.9
Laravel Version: 5.3
When adding new record in a newly created table/bread.

Please remember to add version of Voyager and Laravel when creating an issue.

@marktopper Sorry, I missed it, Done.

Can you try get version dev-master and test it there?

I tried it now but the problem still exists.
"require": {
  "php": ">=5.6.4",
  "laravel/framework": "5.3.*",
  "tcg/voyager": "dev-master"
},

In addition to that there still some updates not added yet to the system for example the parent_id of the category is still text input not a dropdown select element.

Just created a branch with a possible fix for your issue, can you try dev-fix/567?

And in order to get that to show as a dropdown, you must set some additional JSON options for that BREAD field.
Try this json
{
    "default": "__null__",
    "null": "__null__",
    "options": {
        "__null__": "NULL"
    },
    "relationship": {
        "key": "id",
        "label": "name"
    }
}

or create a fresh installation
or remove all voyager database migration and run voyager:install again. (the migrations are copied from vendor folder to database folder)

Thanks @marktopper
I used that branch dev-fix/567 and tried again but nothing changed.

@peacemoon
I'm already using the package with a fresh laravel installation.
Anyway I'll rerun the migrations and let you know if it solved the problem.

Can you please send the content of the cached view that you can see in the exception?

Here it is:
Cached view contents

Seems like it could be an issue that is specific when using the datetime type.
<input type="datetime" class="form-control datepicker" name="<?php echo e($row->field); ?>" value="<?php echo e(gmdate('m/d/Y g:i A', strtotime($dataTypeContent->{$row->field}))); ?>">

Will try it out later, just on my way out for a birthday.

@marktopper
It is related to the deleted_at column, when I unchecked its browse/edit/create/delete checkboxes, the problem has gone.
Enjoy ur time.

Pull #590 should have done the trick.
Tagging a new release later today.


Map with picture file color image with opacity

Hi,
I would like to know if it's possible to add above the map a png file containing colors with opacity (atmospheric index). And to be able to zoom together ?
How I can to do that ?
Thks

zoom together? what is that?
So, the png file is really outside of the map. You click somewhere on the png and then something should happen in the map? What should happen?

This is what is happening when using WMS. You have to create a Raster geometry which has a boundingbox in world coordinates.

https://github.com/Mapsui/Mapsui/blob/master/Mapsui.Geometries/Raster.cs
The constructor takes a MemoryStream, which is the data of you image, and a BoudingBox, which is the extent of the image. Add the raster to a MemoryLayer. Not too hard.

If your map is in SphericalMercator make sure you transform the coordinates of the BoundingBox to SphericalMercator.

Ok thank you for your feed back. We will try that !

@pauldendulk We try this code :
var image = new MemoryStream(await DownloadImageAsync(_url));
var raster = new Raster(image, new BoundingBox(230000, 5510000, 800000, 5866000));
var layer = new MemoryLayer() { DataSource = new MemoryProvider(raster)/, Opacity = 0.75/ };
_map.NativeMap.Layers.Add(layer); [
That works well but when we add Opacity the map it's very very slow.
What do you think ?

Probably because the image is too big. This means you need a more advanced solution where you use the image layer and cut out of part of the image when you fetch the data. I think you will need to write your own Provider (DataSource). Something like the WmsProvider. It will have the image in memory. On the GetFeaturesInView of the provider you will need to do some re-sampling of the image. Not very easy (but fun to do). You could use SkiaSharp there.

ok thank you. See you later.


When will you release the code?

Thank you for your concerns about our work. I am really sorry that we may delay one or two weeks to publish our code. After we making our code available, we will inform you through this issue.

Thank you for your concerns about our work. Code has been released.


Extension issue

Issue Type: Bug
Extension Name: LiveServer
Extension Version: 5.6.1
OS Version: Windows_NT x64 10.0.18363
VSCode version: 1.54.3

:warning: We have written the needed data into your clipboard. Please paste! :warning:

Is there a way to fix this?


hs.getResourceFileList() OAuth 2 error

@selimnairb I am getting a InsecureTransportError: (insecure_transport) OAuth 2 MUST utilize https error that stems from for resource in hs.getResourceList(types=types): (see the Traceback below). The funny thing is, if I do not authenticate my instance of the HydroShare object at all (i.e. hs = HydroShare()) it works fine. Also, the OAuth version is working fine on other hs_restclient calls, such as hs.getSystemMetadata(res_id). Do you know what's going on here?
I already tried passing use_https=True to the HydroShare() instantiation, just to be sure. Still no change.
[Thu Mar 31 22:11:03 2016] [error] Traceback (most recent call last):
[Thu Mar 31 22:11:03 2016] [error]   File "/usr/lib/tethys/lib/python2.7/site-packages/django/core/handlers/base.py", line 149, in get_response
[Thu Mar 31 22:11:03 2016] [error]     response = self.process_exception_by_middleware(e, request)
[Thu Mar 31 22:11:03 2016] [error]   File "/usr/lib/tethys/lib/python2.7/site-packages/django/core/handlers/base.py", line 147, in get_response
[Thu Mar 31 22:11:03 2016] [error]     response = wrapped_callback(request, *callback_args, **callback_kwargs)
[Thu Mar 31 22:11:03 2016] [error]   File "/usr/lib/tethys/src/tethys_apps/tethysapp/hydroshare_gis/controllers.py", line 228, in get_hs_res_list
[Thu Mar 31 22:11:03 2016] [error]     for resource in hs.getResourceList():
[Thu Mar 31 22:11:03 2016] [error]   File "/usr/lib/tethys/lib/python2.7/site-packages/hs_restclient/__init__.py", line 262, in _getResultsListGenerator
[Thu Mar 31 22:11:03 2016] [error]     r = self._request('GET', res['next'], params=params)
[Thu Mar 31 22:11:03 2016] [error]   File "/usr/lib/tethys/lib/python2.7/site-packages/hs_restclient/__init__.py", line 208, in _request
[Thu Mar 31 22:11:03 2016] [error]     verify=self.verify)
[Thu Mar 31 22:11:03 2016] [error]   File "/usr/lib/tethys/lib/python2.7/site-packages/requests_oauthlib/oauth2_session.py", line 310, in request
[Thu Mar 31 22:11:03 2016] [error]     raise InsecureTransportError()
[Thu Mar 31 22:11:03 2016] [error] InsecureTransportError: (insecure_transport) OAuth 2 MUST utilize https.

@shawncrawley Can you supply a minimal example that triggers the error (omitting of course any client IDs or secrets)?  Thanks.

from hs_restclient import HydroShare, HydroShareAuthOAuth2

client_id = 'whatever_it_is'
client_secret = 'whatever_it_is'
token = {
u'access_token': u'whatever_it_is',
u'expires_in': 2592000,
'expires_at':<PHONE_NUMBER>,
u'token_type': u'Bearer',
u'scope': u'read write',
u'refresh_token': u'whatever_it_is'
}

auth = HydroShareAuthOAuth2(client_id, client_secret, token=token)
hs = HydroShare(auth=auth, hostname='www.hydroshare.org', use_https=True)

i = 1
for res in hs.getResourceList():
    print 'resource%s' % i
    i += 1

This seems to fail when processing the 6th resource in the list, because this is my output:
/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:315: SNIMissingWarning: An HTTPS request has been made, but the SNI (Subject Name Indication) extension to TLS is not available on this platform. This may cause the server to present an incorrect TLS certificate, which can cause validation failures. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#snimissingwarning.
  SNIMissingWarning
/usr/local/lib/python2.7/dist-packages/requests/packages/urllib3/util/ssl_.py:120: InsecurePlatformWarning: A true SSLContext object is not available. This prevents urllib3 from configuring SSL appropriately and may cause certain SSL connections to fail. For more information, see https://urllib3.readthedocs.org/en/latest/security.html#insecureplatformwarning.
  InsecurePlatformWarning
resource1
resource2
resource3
resource4
resource5
Traceback (most recent call last):
  File "test.py", line 21, in <module>
    for res in hs.getResourceList():
  File "/usr/local/lib/python2.7/dist-packages/hs_restclient/__init__.py", line 262, in _getResultsListGenerator
    r = self._request('GET', res['next'], params=params)
  File "/usr/local/lib/python2.7/dist-packages/hs_restclient/__init__.py", line 208, in _request
    verify=self.verify)
  File "/usr/local/lib/python2.7/dist-packages/requests_oauthlib/oauth2_session.py", line 310, in request
    raise InsecureTransportError()
oauthlib.oauth2.rfc6749.errors.InsecureTransportError: (insecure_transport) OAuth 2 MUST utilize https.

@shawncrawley Thanks.  I'll look at this later today or tomorrow and get back to you.

@shawncrawley The problem is that for whatever reason Django REST framework has decided to put HTTP links in for result pagination, rather than HTTPS.  We need to review our django/Django REST framework configuration to change this.  For now, I posted hs_restclient version 1.2.2, which patches the URL each next page when HTTPS is being used (e.g. when using OAuth).  Let me know how that goes.

@selimnairb Thanks, with version 1.2.2 it is now working. Am I good to close this issue then?


[4.2] handleViewException in PHP7

This PR fixes that issue: https://github.com/laravel/framework/issues/16123
Exceptions thrown from blade files are currently not being handled correctly for PHP7.

@taylorotwell I have been using it for a week. No problem at all. I think you can release a new version now.

@bcalik new release was just tagged https://github.com/laravel/framework/releases/tag/v4.2.21


Cannot browse media (albums) from within Home Assistant

What version of Music Assistant has the issue?
2.0.0b103
What version of the Home Assistant Integration have you got installed?
2024.1.0
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
Browsing media from a media player device on home assistant works fine, except when browsing albums which results in an unknown error.
How to reproduce
Select a media player device in Home Assistant (eg Sonos).
Click on "browse media"
Click on "albums"
Click on an album
Result:
Media Browsing Error
Unknown error
Music Providers
smb files system (remote share)
Player Providers
Sonos, not grouped.
Relevant log output
2024-02-22 18:21:08.155 ERROR (MainThread) [homeassistant.components.websocket_api.http.connection] [281470290935616] Error handling message: Unknown error (unknown_error) XXXXXXXXX  from <IP_ADDRESS> (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36)
Traceback (most recent call last):
File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 26, in _handle_async_response
await func(hass, connection, msg)
File "/usr/src/homeassistant/homeassistant/components/media_player/init.py", line 1310, in websocket_browse_media
payload = await player.async_browse_media(media_content_type, media_content_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/mass/media_player.py", line 496, in async_browse_media
return await async_browse_media(self.hass, self.mass, media_content_id, media_content_type)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/mass/media_browser.py", line 103, in async_browse_media
return await build_album_items_listing(mass, media_content_id)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/config/custom_components/mass/media_browser.py", line 254, in build_album_items_listing
tracks = await mass.music.get_album_tracks(album.item_id, album.provider)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/music_assistant/client/music.py", line 155, in get_album_tracks
for item in await self.client.send_command(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.12/site-packages/music_assistant/client/client.py", line 168, in send_command
return await future
^^^^^^^^^^^^
music_assistant.common.models.errors.InvalidCommand: Invalid command: music/album/album_tracks
Additional information
No response
What version of Home Assistant Core are your running
2024.2.0
What type of installation are you running?
Home Assistant Container
On what type of hardware are you running?
Raspberry Pi

Have you other players to try? I just tried with a chromecast and a slimproto device and both worked fine.

Try removing the integration from HA, then remove it from HACS, restart HA then reinstall

Try removing the integration from HA, then remove it from HACS, restart HA then reinstall

Unfortunately still the same

OK this sill get looked at in due course

This is fixed in the 2024.2.x version of the HA integration.

Just updated and yes looks like it's ok, thank you!

This has been fixed in b110

Hi all,
I'm suffering from the same issue when attempting to create an automation using media player media picker. When a music assistant player is selected, the options for Tracks/Playlist appear, but when selected, the
Media Browsing Error
Unknown error
Appears.
HA versions:
Core
2024.10.4
Supervisor
2024.10.3
Operating System
13.2
Frontend
20241002.4
MA version:
Music Assistant Server
Current version: 2.3.2
Thanks!

@hazzapatcher you have asked a question in a closed issue from six months ago. You can ask your question in the discussions area. I would attach a screenshot or two as I am not sure what you are trying to do (not surprising though asI do all my automations in yaml)


Change SOURC3 logo  SOURC3 Alpha

Change logo for all pages
https://www.figma.com/file/3UUMChv0qaOOkHoddpEFgA/SOURC3?node-id=3295%3A672

Checked


fromJS doesn't sanitize

What happened
Am not sure if this is a bug or an intended behavoir. But it happened to us, as where where using<EMAIL_ADDRESS>It happened that the user entered data with a   "
   }
}

Immutable.fromJS(xxx)

or go to: http://codepen.io/marsch/pen/gMYWMM

update: found out that this might relate to babel :/ closing now


[Question]¸ Upgrade to 0.1.11 / websockets, any breaking changes?

Hi,
Sorry for the title, I don't really understand what is happening. I just updated pynecone to 0.1.11, deleted .web and re-ran 'pc init' then ' pc run' but my app doesn't work anymore, no error, no console log, no network event (maybe that's normal using websocket) just doing nothing when clicking on my buttons.
Is there anything I should change compared to the previous version?
Still trying to find out what is happening but not that easy...

So, I found the cause but no the reason. On a button click event I change the value of the app state (and in the logs, it went from False to True) but in the frontend when I display the state variable value, it is still False:
class QuestionnaireState(pc.State):

    questions: List = []
    started: bool = False

...

class SubmitButtonState(QuestionnaireState):
    def start(self):
            QuestionnaireState.started = True

            logger.debug(f"Questionnaire started? {QuestionnaireState.started}")

2023-01-03 14:20:54.069 | DEBUG    | app.pages.questionnaire:start:196 - Questionnaire started? True

 pc.vstack(
            pc.heading("Questionnaire for " + QuestionnaireState.methodology),
            pc.text("started: " + QuestionnaireState.started),
            pc.divider(),
...

And not the case with 0.1.10.
Any idea

I'll look into this. One thing you could try is run
pc run --loglevel debug

to get more detailed logs (we just added this flag).
The other thing is after the websockets change, in the Network tab of the browser you should now see a single /event connection, which is the WS.

Ah, I think the issue is you need to have
self.started = True

in the event handler (rather than setting the class variable). The class fields should only be used in the render methods, within the event handlers the vars should be referred to as fields of the local state instance.
Not sure how it worked in the previous version.

ok!
In the meantime, I coded a little PoC to show the issue.
I think I'm doing something wrong but...
from typing import List, Dict
import pynecone as pc

class ButtonModel(pc.Model, table=False):

    title: str

class AppState(pc.State):
    """The app state."""

    default_field: str
    test: int = 0

class LocalState(AppState):

    button_state: List[bool] = [False for i in range(10)]

    @pc.var
    def get_buttonmodel(self) -> List[ButtonModel]:
        self.default_field = "break me"
        return [ButtonModel(id=0, title="this is a button which breaks pynecone"), ButtonModel(id=1, title=self.default_field)]

class SubState(LocalState):
    def trigger_fault(self) -> None:
        print(self.test, AppState.test)
        self.test = 1
        AppState.test = 1
        print(self.test, AppState.test)

def index():
    return pc.center(
        pc.vstack(
            pc.text("test" + LocalState.test),
            pc.foreach(LocalState.get_buttonmodel, lambda a_model: display_form(a_model)),
            spacing="1.5em",
            font_size="2em",
        ),
        padding_top="10%",
    )

def display_form(model: ButtonModel):

    return pc.button(model.title, size="lg", on_click=SubState.trigger_fault)

# Add state and page to the app.
app = pc.App(state=AppState)
app.add_page(index)
app.compile()

yeah it was self in the working version, I thought it could create a local variable but without modifying the parent variable. But not better,

Actually, my fault - you are correct. We did have a breaking change and haven't updated the docs yet.
For performance reasons, the child state cannot directly set the parent state vars like this anymore. You now have to reference the parent state using the self.parent_state field. I updated your code, lmk if this works (we will update the docs for this ASAP)
from typing import List, Dict
import pynecone as pc

class ButtonModel(pc.Model, table=False):

    title: str

class AppState(pc.State):
    """The app state."""

    default_field: str
    test: int = 0

class LocalState(AppState):

    button_state: List[bool] = [False for i in range(10)]

    @pc.var
    def get_buttonmodel(self) -> List[ButtonModel]:
        self.default_field = "break me"
        return [ButtonModel(id=0, title="this is a button which breaks pynecone"), ButtonModel(id=1, title=self.default_field)]

class SubState(LocalState):
    def trigger_fault(self) -> None:
        print(self.test, AppState.test)
        self.parent_state.parent_state.test += 1
        print(self.test, AppState.test)

def index():
    return pc.center(
        pc.vstack(
            pc.text("test" + LocalState.test),
            pc.foreach(LocalState.get_buttonmodel, lambda a_model: display_form(a_model)),
            spacing="1.5em",
            font_size="2em",
        ),
        padding_top="10%",
    )

def display_form(model: ButtonModel):

    return pc.button(model.title, size="lg", on_click=SubState.trigger_fault)

# Add state and page to the app.
app = pc.App(state=AppState)
app.add_page(index)
app.compile()

ah ah ok this is what I thought :D I was trying some super().super().test.... :D
Thanks!

So changing to parent_state works but makes the code pretty weird (I have a lot self.parent_state.parent_state.parent_state...) and hard to maintain as I need to remember in which subclass the attribute is. So if you can find a way to  make it transparent or something more recursive like a recursive thing. That would be great!

Yes we can bring back the original way it was working (where you can just inherit the parent state vars). I think the code cleanliness is worth it, we'll have this in the next version.

@picklelo, can you explain now the overall network architecture? On which port the WS server is listening to? is the FastAPI server on port 8000 still needed an so on...
It works fine on localhost but when I tried to deploy the app to Azure nothing works.
Thanks!

Hi its should be 8000 still are you using the right protocol for web sockets may need to use tcp. Also are you using a load balancer, what does your overall hosting architecture look like

Like Alek said we use the FastAPI server for websockets, which is at the endpoint localhost:8000/event. All events  and state updates are sent through the websocket connection. Maybe something you need to configure in Azure to allow sockets?

I found a way to generate the static website and deployed to Azure Static Website and it works with wss. Good!

Hi
Could you let me know how you successfully deployed the backend to Azure WebApps ?


PropagateClassVars to sub-models

Change Summary
Currently, if a ClassVar is defined on a model and re-defined
on a sub-model omitting the ClassVar annotation, Pydantic produces an
unrelated error:
NameError: Field name "..." shadows a BaseModel attribute ...

This check was introduced to prevent shadowing Pydantic's own methods
and attributes defined on the BaseModel class.  Following this change,
class variables (that is, variables annotated with ClassVar)
defined on parent models will be inherited by sub-models and
will be overwritable without having to reapply the annotation.

Related issue number
fix #2061
Checklist

[x] Unit tests for the changes exist
[x] Tests pass on CI and coverage remains at 100%
[x] Documentation reflects the changes where applicable
[x] changes/<pull request or issue id>-<github username>.md file added describing change
(see changes/README.md for details)

I've also updated the documentation to explain what PrivateAttr is for, which I thought was unclear.

Humm, I'm not sure about this, I think not using the ClassVar annotation on the sub-class is a recipe for enormous confusion. Even for those who understand how pydantic works, let alone those who are new to it.
Personally I would argue that developers should be forced to always use ClassVar[]even if they're overwriting an attribute which is a class var on the parent model.
But if many people feel otherwise I'm happy to be overruled, also I think a more descriptive error message would be good.

Humm, I'm not sure about this, I think not using the ClassVar annotation on the sub-class is a recipe for enormous confusion. Even for those who understand how pydantic works, let alone those who are new to it.
Personally I would argue that developers should be forced to always use ClassVar[]even if they're overwriting an attribute which is a class var on the parent model.
But if many people feel otherwise I'm happy to be overruled, also I think a more descriptive error message would be good.

If I were to re-annotate subclasses, I would have to parametrise the ClassVar for type completeness - type checkers cannot perform 'partial' inference - annotations must be complete.  This results in a whole lot of repetition, even if I were to use a type alias, for what my type checker is able to infer statically via inheritence.  That Pydantic would not honour the class variable is more surprising to me, but YMMV :)

If I were to re-annotate subclasses, I would have to parametrise the ClassVar for type completeness - type checkers cannot perform 'partial' inference - annotations must be complete.  This results in a whole lot of repetition, even if I were to use a type alias, for what my type checker is able to infer statically via inheritence.  That Pydantic would not honour the class variable is more surprising to me, but YMMV :)

Okay, I'll trust you on this one 😄 .

Thanks a lot.

Question on this in https://github.com/pydantic/pydantic/discussions/4518.