[TODO] Logout in User Menu changes

This user icon dropdown menu, currently under the (R) when you click on it,  needs some change.
Logout icon (import LogoutIcon from '@mui/icons-material/Logout';) and label needs to change state to the MUI Login using this depending on the state of login/logout.
import LoginIcon from '@mui/icons-material/Login';

Note: There is no current login or logout functionality.

@LOGESH-B can we do this with useState, useEffect?

@gbowne1  I am not clearly getting you
with my understanding we can store the login details in local storage along with cookie so we can fetch from there to verify the login/logout state of a user

The icon and its label "Logout" as I showed above should change state between when user is logged in or logged out.  I believe its possible to change this in the view depending on state.

Yeah we can chage it by state using this

@gbowne1 I am not clearly getting you
with my understanding we can store the login details in local storage along with cookie so we can fetch from there to verify the login/logout state of a user

Ok.  We will need to both authorize and authenticate as well.  Are we storing auth stuff in the db for validation?  I would like to make use of what the browser gives us too like localStorage, indexedDB, session, cookies, etc so as long as it can be done securely.

@gbowne1
Yeah we can use localstorage or cookie but I am suggesting to use the JWT tokens....during login we can geneate the JWT token and store it in local storage for each req we can send it as header for the validation of the user

yeah we can definitely use JWT's, get the tokens and save it to storage with maybe a utility.
I made a PR with changes to implement the Login UI and also the icon changing in this issue.

I think it would be better to use Session storage as it is a better option than local storage for storing sensitive information as it is cleared when the session ends and perhaps some cookies.

I think it would be better to use Session storage as it is a better option than local storage for storing sensitive information as it is cleared when the session ends and perhaps some cookies.

Ok it is also a good idea✌

I mean not that its a good or bad idea to use local and we can test it for development purposes, but yeah, if someone happens to catch the xss, xhr, etc. when in production, not gonna be that good.


System Management Admin - Responsive Alerts

The alert colors/icons render perfectly when the page is loaded. However, if user changes status of any of the instances via the buttons on the UI, the status is not ever updated. There is currently an implementation in the instance pop-up menu "start/stop instance" that gets the updated instance status and returns it to the menu item. However, the information does not filter up to the other Alerts, and it seems to not trigger React to update the view in a timely fashion. Figure out a way to make this feature work better and not just on page load/refresh. And don't forget it should work for if the system > start/stop all buttons are pressed as well

Going to do the following

[ ] Fix the bug in #182 so that the Stop Instance dropdown button on the System Admin Card works
[ ] Update the useSystems hook to refetch when there is an INSTANCE_UPDATED event occurs


broken vertical line char

Your Windows build number:  Microsoft Windows [Versione 10.0.17677.1000]

What you're doing and what's happening: make menuconfig command

What's wrong / what should be happening instead: as you can see from the screen, the vertical line char is broken and not displayed.  Trying to paste it to a nano editor doesn't show anything, trying with other works... For example this is displayed ├ but this not ─

What font is that?
This certainly smells like a dupe of #189 to me.

any news for this?

Nope, I'll post an update when I make progress on this.

Oh, this is another case of #240. Marking duplicated!

As a workaround, you can set your TERM to vt100 or putty (if your distribution provides a putty termcap.) The putty terminal definition is almost exactly xterm-256color but it doesn't offer "repeat graphic character", the behavior dialog is using.

sorry but where should i set the TERM variable?


build(package.json): bumped semantic-release to v24.0.0

:tada: This PR is included in version 9.0.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Advancing 0.19.0-rc3 release to status: admiral

What happened to the PR description? It’s supposed to have links to the relevant commits.

What happened to the PR description? It’s supposed to have links to the relevant commits.

Not sure, it never worked for me.


fix(ui): improved footer links contrast

Checklist:

[x] I have read and followed the contribution guidelines.
[x] I have read and followed the how to open a pull request guide.
[x] My pull request targets the main branch of freeCodeCamp.
[x] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

I updated the UI of the footer to add more contrast between the trending articles links and the footer description. In some views, the original color did not cause a sharp change between the description text and the trending articles links which caused me some confusion. I also added a top border for the grid.
Tested on GitPod.

This isn't going to work. You've made the trending guides link text too light now so it doesn't meet minimum accessibility contrast requirements (which are 4.5:1).
Color alone is usually not the best way to try and distinguish things. Maybe you can explain a little more what your confusion was? Actually, that is what opening an issue is for, which is probably what should have been done.

As a new contributor, we encourage you to read our contributing guidelines.
We expect our contributors to be aware of the process specific to this project. Following the guidelines religiously earns you the respect of fellow maintainers and saves everyone time.
Some examples of this are:

Do not edit files directly through GitHub – while you can, it's not a good idea.
Make sure you follow the PR checklist and not just tick things off; otherwise, we won't take you seriously.
Use the correct way to link issues in the description of the PR by updating the XXXXXX. Do not just add issue numbers everywhere and anywhere you feel like.
Keep mentions and review requests to a minimum. We understand you are excited about contributing, and our maintainers will get back to you as soon as they get a chance.
Do not work directly off your main branch - create a new branch for the changes you are working on.

We appreciate you taking the time to help us, and we hope to see more contributions from you.
Happy Contributing.


Page.goto should raise an error if the target URL is invalid

This is handled as an error from the Playwright browser server.


[MM-18952/GH-16740] - Migrate 'components/authorize' module and associated tests to TypeScript

Summary

Migrated all files inside components/authorize to TypeScript
Renamed files to have TypeScript extensions and updated incorrect imports
Check-types resulted in no errors inside this component (there were other type errors elsewhere in the repo which you might already be aware of)

Ticket Link
Fixes #16740
https://mattermost.atlassian.net/browse/MM-18952

Hello @lucievr,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

Hello @lucievr,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

/update-branch


Azure Firewall Packet Capture moving missed change from 2023-11-01 private branch to public api

ARM (Control Plane) API Specification Update Pull Request

[!TIP]
Overwhelmed by all this guidance? See the Getting help section at the bottom of this PR description.

PR review workflow diagram
Please understand this diagram before proceeding. It explains how to get your PR approved & merged.

Purpose of this PR
This PR was merged to the private 2023-11-01 private branch but was missed in moving to current api.
This is a public preview feature and requires to be checked into this api-version.
PR: https://github.com/Azure/azure-rest-api-specs-pr/pull/17364/files#diff-4a6b9e5d2f8d4996c120a1b47ef68bac4439c06897a536cbe99e022f7f705b01
What's the purpose of this PR? Check the specific option that applies. This is mandatory!

[ ] New resource provider.
[ ] New API version for an existing resource provider. (If API spec is not defined in TypeSpec, the PR should have been created in adherence to OpenAPI specs PR creation guidance).
[X] Update existing version for a new feature. (This is applicable only when you are revising a private preview API version.)
[ ] Update existing version to fix OpenAPI spec quality issues in S360.
[X] Other, please clarify:

This is a private preview feature looking to go to public preview feature and requires this fix for powershell to work as expected and is expected to be checked into this api-version.
PR: https://github.com/Azure/azure-rest-api-specs-pr/pull/17364/files#diff-4a6b9e5d2f8d4996c120a1b47ef68bac4439c06897a536cbe99e022f7f705b01

Due diligence checklist
To merge this PR, you must go through the following checklist and confirm you understood
and followed the instructions by checking all the boxes:

[X] I confirm this PR is modifying Azure Resource Manager (ARM) related specifications, and not data plane related specifications.
[X] I have reviewed following Resource Provider guidelines, including
ARM resource provider contract and
REST guidelines (estimated time: 4 hours).
I understand this is required before I can proceed to the diagram Step 2, "ARM API changes review", for this PR.

Additional information

 Viewing API changes
For convenient view of the API changes made by this PR, refer to the URLs provided in the table
in the Generated ApiView comment added to this PR. You can use ApiView to show API versions diff.

Suppressing failures
If one or multiple validation error/warning suppression(s) is detected in your PR, please follow the
suppressions guide to get approval.

Getting help

First, please carefully read through this PR description, from top to bottom. Please fill out the Purpose of this PR and Due diligence checklist.
If you don't have permissions to remove or add labels to the PR, request write access per aka.ms/azsdk/access#request-access-to-rest-api-or-sdk-repositories
To understand what you must do next to merge this PR, see the Next Steps to Merge comment. It will appear within few minutes of submitting this PR and will continue to be up-to-date with current PR state.
For guidance on fixing this PR CI check failures, see the hyperlinks provided in given failure
and https://aka.ms/ci-fix.
For help with ARM review (PR workflow diagram Step 2), see https://aka.ms/azsdk/pr-arm-review.
If the PR CI checks appear to be stuck in queued state, please add a comment with contents /azp run.
This should result in a new comment denoting a PR validation pipeline has started and the checks should be updated after few minutes.
If the help provided by the previous points is not enough, post to https://aka.ms/azsdk/support/specreview-channel and link to this PR.

@nikhilpadhye1 - Need the breaking change approval label. It was applied by @JeffreyRichter on the PR in private repo: https://github.com/Azure/azure-rest-api-specs-pr/pull/17364, and presumably applies here as well.


Error in source selection found

When selecting a source, the following error is occurring.
'wrapped_class_ListItem' object has no attribute 'setCast'
Test environment
Elementum 0.1.64
kodi 16.1
Android 5.1.1
Brazilian Portuguese language
https://paste.kodi.tv/ehovoxobaf.kodi
Note: This problem did not occur in version 0.1.62
Regards

@veniciusgp Please, try with 0.1.65.

@veniciusgp Please, try with 0.1.65.

@veniciusgp Please, try with 0.1.65.

Hi @elgatito
In version 0.1.65 no source is found

Note: I did not update version 0.1.64 to version 0.1.65. I uninstalled version 0.1.64 and installed version 0.1.65
Elementum Burst update to version 0.0.55
https://paste.kodi.tv/pecisajise.kodi
Regards

@veniciusgp Please, try with 0.1.65.

Hi @elgatito
In version 0.1.65 no source is found

Note: I did not update version 0.1.64 to version 0.1.65. I uninstalled version 0.1.64 and installed version 0.1.65
Elementum Burst update to version 0.0.55
https://paste.kodi.tv/pecisajise.kodi
Regards

@veniciusgp your burst configuration cannot find any results for requested item. There is no error with Elementum.

@veniciusgp your burst configuration cannot find any results for requested item. There is no error with Elementum.

@veniciusgp your burst configuration cannot find any results for requested item. There is no error with Elementum.

Hi @elgatito
Why doesn't this problem happen with version 0.1.62 without changing any settings in Burst?

@veniciusgp your burst configuration cannot find any results for requested item. There is no error with Elementum.

Hi @elgatito
Why doesn't this problem happen with version 0.1.62 without changing any settings in Burst?

@veniciusgp It can be because in last versions language detection was fixed, so previously, Burst probably used english names, now it uses spanish/portuguese names.
Enable setting to use original names for searching.

@veniciusgp It can be because in last versions language detection was fixed, so previously, Burst probably used english names, now it uses spanish/portuguese names.
Enable setting to use original names for searching.

@veniciusgp It can be because in last versions language detection was fixed, so previously, Burst probably used english names, now it uses spanish/portuguese names.
Enable setting to use original names for searching.

Hi @elgatito
I changed the setting in elementum to use the original names in the search according to your tip
Now several sources are being found but when selecting one the following error is occurring
Failed to convert to input type to either a std::string or a std::vector<(XBMCAddon::xbmcgui::InfoLabelStringOrTuple)>
https://paste.kodi.tv/puqevecafi.kodi
Regards

@veniciusgp It can be because in last versions language detection was fixed, so previously, Burst probably used english names, now it uses spanish/portuguese names.
Enable setting to use original names for searching.

Hi @elgatito
I changed the setting in elementum to use the original names in the search according to your tip
Now several sources are being found but when selecting one the following error is occurring
Failed to convert to input type to either a std::string or a std::vector<(XBMCAddon::xbmcgui::InfoLabelStringOrTuple)>
https://paste.kodi.tv/puqevecafi.kodi
Regards


Added include for the generated xtensor-pythonTargets.cmake.

The previous version of xtensor-pythonConfig.cmake.in didn't properly include the generated xtensor-pythonTargets.cmake file. Thus users were not able to use the imported target xtensor-python.

Thanks!


Linting shaders

Can naga be used as a cli tool to lint shader files? Or are there other tools that can be used?

naga-cli can validate and translate shaders. This will give you errors (sometimes panics without an error) but not necessarily give you feedback about style or unused names etc.
I have seen some "glsl lint" extensions for VSCode, but no experience with how they work or what they provide.

I'm thinking this would mean building a separate CLI tool that uses naga-cli to validate .wgsl and .glsl files.

wgpu uses naga already to validate shaders. And errors do get passed all the way to Python. I use a simple try/except for my project. And this does work, apart from edge cases where the called process panics (it doesn't have any exit code). Some of these are already addressed and next wgpu-core release is targeting 17th January, which I hope includes all the naga fixes of the past 2 months.
So using naga-cli seems redundant. I wanted to parse the error message into a Python Exception with corrected span etc later on, since the shadertoy code isn't a valid fragment shader on it's own. You always have to add the compatibility code before it.
perhaps introducing a .validate_shadertoy method directly to the Shadertoy class might be a good idea.

I'm mostly thinking about having a CLI tool available that can be run on CI to validate all .glsl and .wgsl files. I think with what you're saying, it means we could build something like that on wgpu-py instead of on naga-cli.

https://github.com/PolyMeilex/vscode-wgsl
Looks like this has both syntax highlighting and a CLI linting functionality


Fail to load on dedicated server

crash-2024-09-06_00.11.17-fml.txt

Seems to be caused by EntityJS, closing now.


Support for Authentication Key?

Hi,
Does this project support, or is planning on supporting, networks that have an authentication key configured to connect to the network?

I have not used authentication keys in any of my setups, so I don't really have any plans there. I'm happy to integrate a pull if someone wants to put one up, but I don't really have any plans to add anything that I don't personally use.


For testing latency install and run other GPTree like software as "Chat Toolkit"

For testing ChatGPT response time, install
Chat Toolkit
https://github.com/danb27/chat-toolkit, they also use Whisper for STT, and for TTS pyttsx3 (https://pypi.org/project/pyttsx3/)
and test how quickly ChatGPT answers.

I have tested only the chat / "input text via keyboard" variant, no STT, no TTS. just the ChatGPT API call and it was very fast, not longer than 2 seconds rather less, what confirms the numbers from https://github.com/ClemensGruber/climart_gptree/issues/24#issuecomment-1950323929 so same conclusion:
We have 20 to 40 seconds waiting time with GPTree so it seems as a bigger problemm in our implementation!


Updated GoogleVoice.php to work with new split login and different PO…

…ST URLs.
Updated login POST URL.
Added DOM parsing to avoid issues with name/value being moved in login source.
Added additional features to capture other message type
Added function to capture all inputs from captured pages to prevent breaking on changes.
Made GALX and _rnr_se use DOM input captures and updated errors to capture more data.
Changed some comments and removed trailing space and added returns between functions for ease of use.

Awesome, thanks! Works for me as well.


Wire up DERIVATIVE aggregate

If the query is like this:
SELECT DERIVATIVE(value)
FROM cpu
WHERE time > now() - 4h

It will compute the rate of change between each data point.
If the query is like this:
SELECT DERIVATIVE(MEAN(value))
FROM cpu
WHERE time > now() - 4h
GROUP BY time(5m)

It will take the rate of change of the mean of 5 minute buckets of time.

so where is derivative?

+1 or is there another way to access to derivative/speed on data ?

I am using rc25 and I don't see the derivative function. Get the following error:
ERROR: {"results":[{"error":"function not found: "DERIVATIVE""}]}
Here is my query:
SELECT DERIVATIVE(value) FROM "my.series" WHERE time > now() - 15m GROUP BY time(10s) ORDER BY asc
Any ideas please?

@anandmani-lab49 -- keep an eye on this ticket. Once the functions are implemented, this ticket will be closed.


Text links in the markdown files as images

You're linking files as images e.g.:
* ![TSSBase.py](TSSBase.py): This is the basic class for all OAISYS components.

For Firefox it's fine:

but for other browsers like Safari it isn't:

which looks ugly.
The solution is to remove the exclamation marks:
-* ![TSSBase.py](TSSBase.py): This is the basic class for all OAISYS components.
+* [TSSBase.py](TSSBase.py): This is the basic class for all OAISYS components.

I find these files:
./README.md
./src/README.md
./src/assets/stages/README.md
./src/environment_effects/README.md


Normalization for DM in utils.createfourierdesignmatrix_dm

Hi All,
I have recently started to use Enterprise, and while resolving a discrepancy of my results with other person results (from PAL2) noticed the following. In utils.createfourierdesignmatrix_dm we create a Fourier design matrix for DM variation noise. But it looks like there is a to-do item: # TODO: should we use a different normalization.
Here are my suggestions:

Replace line 134 with the following:
Dm = 4.15e3/(freqs**2)
Add a comment:
# 4.15e3 = K^(-1), where K is from Eq. 23 in L. Lentati paper: https://academic.oup.com/mnras/article/437/3/3004/2907742

Do you think these are worth implementing?
I would be happy to git-push these changes.

I would rather keep the current normalization which makes the basis functions dimensionless. There are several reasons for this.

Much easier to gauge "strength" of DM signal as with this normalization it is simply the deviation (in seconds) at 1.4 MHz.
Allows the exact same parameterization and priors as we use for red noise.
Keeps code uniform in that all basis functions are dimensionless and all gaussian priors are variances in units of seconds^2.
Allows for easy extension to other exponents on radio frequency (i.e. scattering, or varying, etc) without having to figure out what other constant to use for normalization

Of course this is up to the other developers as well but I strongly prefer the dimensionless normalizations.

I also prefer to keep them dimensionless, but it would be pretty easy to allow the create designmatrix functions to take a normalization option.  The hardcoding of numbers always bothers me, even if I would choose 1400 MHz too.

@jellis18 @paulthebaker then we could just add "fref" argument in utils.createfourierdesignmatrix_dm, with a default of 1400, and mention that it has MHz units in the comment. It shouldn't affect existing users

@bvgoncharov, that sounds good. Do you want to implement this and make a PR?

Hi @jellis18 , sure, I created a PR: https://github.com/nanograv/enterprise/pull/165
Sorry for late reply. This was my first pull request, so I had to find some time to look through documentation and make sure I am doing it right :)


inconsistent prediction results using HinSage

getting inconsistent prediction results after fitting a HinSage model
I am using the HinSage-link-prediction demo script.
After model fitting, I ran model.predict(test_gen) and got results
array([[3.9639022],
       [3.1461685],
       [3.5686603],
       ...,
       [4.0026994],
       [3.790706 ],
       [3.9910824]], dtype=float32)

ran model.predict(test_gen) again, this time got results
array([[4.011217 ],
       [3.3255208],
       [3.701041 ],
       ...,
       [4.098828 ],
       [3.6664836],
       [3.870615 ]], dtype=float32)

I have also set random seeds as
import os
import tensorflow as tf
import random as python_random

seed_value= 0
np.random.seed(123)
tf.random.set_seed(1234)
python_random.seed(123)
os.environ['PYTHONHASHSEED']="3"

I am using Stellagraph 1.2.1.
Please advise how to fix this issue. Thank you!

@huonw any suggestions?

Hi @enjieli thanks for waiting!
Unfortunately, I don't think HinSAGE is fully reproducible at the moment: https://github.com/stellargraph/stellargraph/pull/926 is a (very old) work-in-progress pull request that fixes this.
In any case, from your description I'm slightly unclear: are you setting the random seeds before each predict call, or just once at the start of the script? I think you should be able to slightly more reproducible behaviour using https://stellargraph.readthedocs.io/en/stable/api.html#module-stellargraph.random too:
sg.random.set_seed(123)
tf.random.set_seed(123)
first = model.predict(test_gen)

sg.random.set_seed(123)
tf.random.set_seed(123)
second = model.predict(test_gen)

However, this won't be completely consistent 😦

@huonw thanks for your response. I was setting the random seeds just once at the start of the script.
Another quick question on HinSage, I have one node type that has 5000+  features, is it better to do feature dimension reduction first before building the graph? I have 4430 nodes and 2569835 edges in the graph;  each mode fit epoch takes a while to run. What's the best practice for my case? Thank you so so much!

You're right that large feature vectors may be suboptimal, because it does force copying a lot of data for every data point. HinSAGE samples a neighbourhood of each requested head node for training and prediction, and then has to collect the features of every node in the neighbourhood. The sizes of these neighbours can quickly become very large because the node types and edge types and number of samples multiply, rather than add.
That is to say, reducing feature size may improve performance significantly.

@huonw thank you for your input!
Are there ways to get node feature importance in the HinSage Link Prediction model? like the GCN saliency_maps .

I found that a possible workaround is to set batch_size to 1 in HinSAGENodeGenerator, which is used to call model.predict() method.  Other seed parameters need to be set as well.
The results become deterministic across different runs, however, this hurts prediction performance.


After an update configurator does not open

See below:
> streamdeckui
panic: runtime error: index out of range [0] with length 0

goroutine 1 [running, locked to thread]:
main.newEditor({0x0, 0x0, 0x0}, {0x7f7700, 0xc0000c0000})
        streamdeckui/ui.go:39 +0x30d
main.main()
        streamdeckui/main.go:28 +0x195

Worked before update/reboot. Daemon seems to start up fine, though the service status does not mention anything about finding a device and my previous config is not loaded onto the device.
Using Arch, installed streamdeckd and streamdeckui via the AUR packages.

hey, sorry it's taken so long, I believe this can sometimes be the result of the connection to the streamdeck not being closed correctly, has it worked since you opened this issue/does it work if you replug the device while the daemon is running

This is actually probably a streamdeckd error - restarting streamdeckd, replugging the device, rebooting the computer etc did not help, but something that did actually help was installing the Python based streamdeck-ui (https://timothycrosley.github.io/streamdeck-ui/) and trying to use that. It worked, and when i closed that and opened streamdeckd again, it started working just fine.


Device not supported: Oneplus Nord CE4

Please resolve this issue ASAP

@Ajmaljazz Please read the info at https://github.com/cyb3rko/flashdim/issues/2.
Device is now excluded from PlayStore


static willTransitionTo is lost

i'm not sure if this is the fault of babel-plugin-react-transform. After integrating react-transform-boilerplate into our setup, static willTransitionTo is gone on components. i guess it gets lost in the process of wrapping the component with a HOC?

Please provide a reproducible example. Babel plugin doesn't add any HOCs.

Ok, i investigated some more.
The problem is the following:
We use fluxible, which provides the provideContext helper, which wraps your root component by returning a HOC that injects context into its its wrapped component. it copies over statics by using hoist-non-react-statics, which in turn uses     var keys = Object.getOwnPropertyNames(sourceComponent) to get the relevant statics. When console.logging those keys without using this plugin, this returns an array that contains "willTransitionTo". When using with this plugin, the array doesn't contain "willTransitionTo" (just ["length", "name", "arguments", "caller", "prototype", "displayName", "__reactPatchProxy", "contextTypes"]).
I am not sure if this is expected behaviour, as I do not entirely understand the limitations section of your react-proxy README:

Does not replace ES7 instance properties
Does not replace bound static methods
Replacing a method using autobind-decorator causes its identity to change

(I don't find google results for "ES7 instance properties" and "bound static methods" -- excuse my ignorance :))

Closing as duplicate of https://github.com/gaearon/react-proxy/issues/23.

Ok thanks for confirming, will watch there!

Just to clarify—this is not related to limitations in README, those are only talking about what's hot reloaded. The problem is a side effect of the way static properties are currently being proxied.

Thank you for reporting this.
It should be fixed in<EMAIL_ADDRESS>via<EMAIL_ADDRESS>(https://github.com/gaearon/react-proxy/pull/29).
Please verify.

Awesome. Works! Thank you so much. :) deploying react-transform to all of
our projects now. Yey :)
Dan Abramov<EMAIL_ADDRESS>schrieb am Fr., 25. Sep. 2015 22:17:

Thank you for reporting this.
It should be fixed in<EMAIL_ADDRESS>via<EMAIL_ADDRESS>(
gaearon/react-proxy#29 https://github.com/gaearon/react-proxy/pull/29).
Please verify.
—
Reply to this email directly or view it on GitHub
https://github.com/gaearon/babel-plugin-react-transform/issues/25#issuecomment-143343292
.


Error message when using moved libraries

Description
If you move your user folder directory from the standard C: partition and try to open a library through the "libraries"-group in your left sidebar it shows an error message which says:
"Have you deleted this folder? The folder you are trying to access could have been moved or deleted."
However, there is no problem if you access the library from your start page rather than from the "Libraries" section in your left sidebar.
The path that's being accessed is not at all the library's path:
It accesses "C:\Users\justi\AppData\Roaming\Microsoft\Windows\Libraries\Pictures.library-ms"
when it should access "D:\justi\Pictures"
Steps To Reproduce

Move one of your libraries to a different partition than C:
Show the libraries section in your sidebar.
Click on the library you moved.
Get the error.

Expected behavior
There should be no error whatsoever and you should just get to the newly defined path of your library.
Files Version
Versão: <IP_ADDRESS>
Windows Version
Windows 11 21H2 22000.258
Relevant Assets
The log doesn't mention anything on the error. The last occurrence was at 20:28 when it says "show context menu".

Assets
[debug.log](https://github.com/files-community/Files/files/7492961/debug.log

)

@justinbernard-dev is this happening after deleting/renaming the cache.db file too?

@nvi9 could you tell me where I can find this cache file? Searching my PC with Search Everything doesn't give me a result that could correspond to Files Application.

It should be located in the same directory as your log file: %localappdata%\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\LocalState

@nvi9 there sadly is no such file. Even if I search the whole %localappdata%\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\ folder using explorer.

Is this still an issue?

In case it helps, I'm having the same issue with different steps. All I did was delete a file or two in my Documents and Pictures libraries, and now when I click on the shortcuts for them I get this same notification once if not twice. Difference is I haven't moved these libraries to another drive, they're still on my C drive. Latest version, 22H2 Win10. Actually, my Videos library is on another drive, but that doesn't have the issue. I figure it's a problem with the shortcuts themselves, Microsoft code being screwy.

Are you sure that all path link in libraires properties are going to valid folders.

Yes...? If it weren't so, wouldn't it just not have anything to display and error?


Add compiled python files to .gitignore

This is a very tiny change but I like my git status reports clean. And python tends to mess that up by creating untracked files like src/etc/download.pyc.

r? @alexcrichton
(rust_highfive has picked a reviewer for you, use r? to override)

Thanks! I tend to prefer these sorts of files to be added in the global gitignore, however, instead of each project individually.

Oh, OK. I've used Rust's .gitignore as the precedent. (Makes the project more "self-contained", but that's just my two pennies.)


Add support for S3 compatible storage providers

New configuration settings are added for the S3 storage. The extension will support any S3-compatible storage provider. Tested with Backblaze B2 and Wasabi. I couldn't check with Amazon due to the non-availability of a free tier account.
It fixes #88

Cool ! Thanks your PR !


Add release, contribution and code of conduct

Add release, contribution and code of conduct guidelines
As per the ODA Code Governance meeting on 6 June 2024, we need to add guidance on Release management, contributing and a code of conduct.
The proposal is:

Release management based on SemVer 2.0.0 and Trunk Based Development
Contributor guidelines depending on how we want to encourage contributions
A code of conduct based on existing templates like the Contributor Covenant

Some thoughts about building/versioning/releasing of Dockerfiles.
Releases from the master branch have a fixed version number "..".
Prereleases from the feature branches have a prerelease number "..-".
Following SemVer 2.0.0 the ordering of a number with prerelease is before the version number without prerelease. E.g. "1.0.0-odaa26" < "1.0.0"
The versions for all dockerfiles should be stored only once at one central place.
We can use the values.yaml file to store the current version number of a dockerfile.
To make it better accessible, the image value ("ocfork/secretsmanagement-operator:0.1.0/odaa-26") can be split into three parts:
secretsmanagement-operator:
  image: ocfork/secretsmanagement-operator
  version: 0.1.0
  prereleaseSuffix: odaa-26

In the feature branches the prereleaseSuffix has to be set to a value, while in the master branch it has to be unset.
There can be an automation, if in the project settings, the "Workflow permissions" are set to "Read and write permissions".
So, when merging a PR, the prereleaseSuffix could be automatically removed.
For the SecretsManagement-Operator and -Sidecar I added workflows for building the dockerimages based on the values.yaml and also check, whether the branch type matches the configured version number:
https://github.com/ODA-CANVAS-FORK/oda-canvas-component-vault/blob/odaa-26-ghactions/.github/workflows/build-prerelease-secretsmanagement-operator.yml
name: Build SecretsManagement-Operator Prerelease Dockerimage
on:
  push:
    branches:
    - feature/*
    paths:
    - source/operators/secretsmanagementOperator-hc/docker/**/*
jobs:
  build-secrets-management-operator-prerelease-dockerfile-job:
    runs-on: ubuntu-latest
    steps:
      - name: Checkout
        uses: actions/checkout@v4
      - name: read image of secretsmanagement-operator from values.yaml
        id: get_smanop_image
        uses: mikefarah/yq@master
        with:
          cmd: yq '.secretsmanagement-operator.image' charts/canvas-oda/values.yaml
      - name: read versionnumber of secretsmanagement-operator from values.yaml
        id: get_smanop_version
        uses: mikefarah/yq@master
        with:
          cmd: yq '[.secretsmanagement-operator.version, .secretsmanagement-operator.prereleaseSuffix] | filter(.!=null and .!="") | join("-")' charts/canvas-oda/values.yaml
      - name: Check Version
        id: check-tag
        run: |
          echo
          if [[ ${{ steps.get_smanop_version.outputs.result }} =~ ^[0-9]+\.[0-9]+\.[0-9]+-.*$ ]]; then
              echo "Version ${{ steps.get_smanop_version.outputs.result }} matches featurebranch format <n>.<n>.<n>-<prerelease>"
          else
              echo "::error::Version ${{ steps.get_smanop_version.outputs.result }} does not matche featurebranch format <n>.<n>.<n>-<prerelease>" && exit 1
          fi
      - name: Set up Docker Buildx
        uses: docker/setup-buildx-action@v3
      - name: Login to Docker Hub
        uses: docker/login-action@v3
        with:
          username: ${{ secrets.DOCKERHUB_USERNAME }}
          password: ${{ secrets.DOCKERHUB_TOKEN }}
      - name: Build and push
        uses: docker/build-push-action@v5
        with:
          context: source/operators/secretsmanagementOperator-hc/docker
          platforms: linux/amd64
          push: true
          tags: |
            ${{ steps.get_smanop_image.outputs.result }}:${{ steps.get_smanop_version.outputs.result }}

So, the process could look like the following:

Create a Branch feature/odaa-123
Edit the values.yaml for each Dockerfile xxx, which should be modified in the branch
2.1. increment xxx.version
2.2. set xxx.prereleaseSuffix to odaa-123
Modify the sources
4.1. If sources are modified, without having the prereleaseSuffix set, the Action will raise an error
create a PR
TBD: unset the xxx.prereleaseSuffix in values.yaml. Either via Action or manually
Merge PR
7.1. If xxx.prereleaseSuffix was not unset, the GitHub Action will raise an error

This way, deploying the charts from the branches allways contains runnable images and never can overwrite a release version.

About Trunk-Base development:
We are already using feature based development, either with branches or forks.
So our development process is feature based.
But we can use release branches for creating releases (mainly of the helm-chart).
So, it would be a mixture of feature-based development and release branches.


Submission invitation readers should be values-copied

For double-blind venues, the submission invitation must have values-copied for the readers field. Otherwise, the readers of the original submission will not be updated with revisions.

How to reproduce this error:

Use the test_neurips_conference.py test
After the first deadline, the author can edit the submission using the Revision invitation and can add another author.
The added author should try to access the submission and the Revision button.

Step 3 should fail now.

I was able to reproduce the error. The readers value is set using submission_stage.get_invitation_readers which uses submission_stage.due_date to identify whether the conference is under submission or not. I should change that to use the second due date, right @melisabok?

I think for double blind venues the submissions readers should always be values-copied.
For single blind venues the submission readers should be values-copied until the first deadline. Between the first and second deadline they may want to choose another readers, for example add the ACs are readers so they can bid on papers.


Don't build messages without a format

This doesn't fix #2188 but it will prevent bad messages from being sent and should give a stack trace for why we are not setting the MIME Version (which we do by calling MimeMessageHelper.setBody(message, body);
(I'm currently looking at why exactly it happens).

I don't think this is actually possible to hit and it didn't catch the issue.


Problems appearing cells before the animation starts.

Hello! Thanks for the wonderful framework! I ran into the problem that UICollectionView cells appear before the animation starts, at this point the cells are loading photos and the user names are already visible. Please tell me how can this be avoided?
                self?.collectionView.refreshControl?.endRefreshing()
                let offset = UIScreen.main.bounds.width
                let fromAnimation = AnimationType.from(direction: .left, offset: offset)
                let animationInterval = 0.1
                self?.collectionView.animateViews(animations: [fromAnimation], initialAlpha: 1, finalAlpha: 1, delay: 0, duration: 0.4, animationInterval: animationInterval, completion: {

                })
                self?.collectionView.reloadData()

https://monosnap.com/file/MgYyNwEbBqeMdyI4jedYBPMf0uIKOQ

If you're animating from outside the view I recommend you hide the views then reload the data and then apply the animation.
self?.collectionView.refreshControl?.endRefreshing()
let offset = UIScreen.main.bounds.width
self?.collectionView.prepareViews()
self?.collectionView.reloadData()
let fromAnimation = AnimationType.from(direction: .left, offset: offset)
let animationInterval = 0.1
self?.collectionView.animateViews(animations: [fromAnimation], initialAlpha: 1, finalAlpha: 1, delay: 0, duration: 0.4, animationInterval: animationInterval, completion: {

})

Hello @marcosgriselli ! I tried to do so it did not help me.
Also I did so, but it did not help me
self?.collectionView.prepareViews(initialAlpha: 0)
self?.collectionView.reloadData()

@alexanderkhitev prepareViews will not work if there are no cells to prepare 😕. You'll have to do some workaround. The shortest path to get it could be
self?.collectionView.alpha = 0
self?.collectionView.reloadData()
self?.collectionView.prepareViews(initialAlpha: 0)
self?.collectionView.alpha = 1

Or setting te cell alpha to 0 on cellForItem() only for the first load.

@marcosgriselli Yes I tried doing the same method only with isHidden and it also works, thanks!


[postfix] expose logs by linking to STDOUT

Hi - this is my 1st pull request.  I was unable to see any logs using your tail -F /var/log/mail.log method so I've removed that and instead linked the /var/log/mail.log to /dev/stdout which seems to work better.
I've also added a supervise folder to each service as when attemptiong to debug, this prevented proper service query via the 'sv' command.

thanks!


[Feature Request] add toggle+to+top and toggle+to+bottom actions

Checklist

[X] I have read through the manual page (man fzf)
[X] I have searched through the existing issues

Output of fzf --version
0.46.1 (brew)
Problem / Steps to reproduce
It would be great to have "toogle to top" and "toggle to bottom" actions.
Current workaround is to keep the tab key pressed to toggle+down to the bottom, but the problem is that the last item will keep toggling very quickly and there's a 50% chance for the last item to be selected upon releasing the tab key.
Having a toggle+to+bottom action would allow users to bind a key (say shift-end) and toggle all the items from the current cursor position to the last item:
1/  Move the cursor to a specific location.
[ ] one
[ ] two
[ ] three  <-- cursor
[ ] four
[ ] five

2/ Press the key binding for toggle+to+bottom.
3/ Desired result:
[ ] one
[ ] two
[x] three
[x] four
[x] five  <-- cursor

See<PHONE_NUMBER>ba1c408016d2b542af9a4229e627ad
I figured adding $FZF_POS variable and using transform action to implement the desired behavior would be much more flexible and versatile than adding dedicated actions.
# Toggle selection to the top or to the bottom
seq 30 | fzf --multi --bind 'load:pos(10)' \
  --bind 'shift-up:transform:for _ in $(seq $FZF_POS $FZF_MATCH_COUNT); do echo -n +toggle+up; done' \
  --bind 'shift-down:transform:for _ in $(seq 1 $FZF_POS); do echo -n +toggle+down; done'

You can replace toggle+up with select+up or deselect+up, etc.

Nice, also TIL about transform. Cool stuff, thanks!


Upgrade to Mockito-Kotlin 2

See https://github.com/jaredsburrows/android-gif-example/blob/master/gradle/dependencies.gradle.kts#L73
Update to testImplementation "com.nhaarman.mockitokotlin2:mockito-kotlin:x.x.x"
From https://github.com/nhaarman/mockito-kotlin

Closed by https://github.com/jaredsburrows/android-gif-example/commit/b6eacf818d8e27468a01fea04dc47715324ac4c7.


Passing cupy functions into cupyx.scipy.ndimage.filters.generic_filter causes a TypeError

It looks like you can't pass cupy functions (like cupy.mean) into cupyx.scipy.ndimage.filters.generic_filter(). This is at odds with what I'd expected, based on how it works with numpy.
I have  minimal working example here and it's obvious I need to replace cupy.mean, I'm just not sure what I should replace it with. Does anyone have suggestions?

Conditions (you can just paste the output of python -c 'import cupy; cupy.show_config()')

CuPy Version          : 8.0.0rc1
CUDA Root             : C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v10.2
CUDA Build Version    : 10020
CUDA Driver Version   : 10020
CUDA Runtime Version  : 10020
cuBLAS Version        : 10202
cuFFT Version         : 10102
cuRAND Version        : 10102
cuSOLVER Version      : (10, 3, 0)
cuSPARSE Version      : 10301
NVRTC Version         : (10, 2)
Thrust Version        : 100907
CUB Build Version     : 100800
cuDNN Build Version   : None
cuDNN Version         : None
NCCL Build Version    : None
NCCL Runtime Version  : None
cuTENSOR Version      : None

Code to reproduce

import numpy as np
import scipy.ndimage.filters

# this works
numpy_array = np.random.random((20, 20))
numpy_result = scipy.ndimage.filters.generic_filter(numpy_array, np.mean, 3, mode="reflect", cval=0)

import cupy
import cupyx.scipy.ndimage.filters

# this doesn't work, because cupy.mean is neither
cupy_array = cupy.random.random((20, 20))
cupy_result = cupyx.scipy.ndimage.filters.generic_filter(cupy_array, cupy.mean, 3, mode="reflect", cval=0)

Error messages, stack traces, or logs

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-4-8789e403f984> in <module>
      3
      4 cupy_array = cupy.random.random((20, 20))
----> 5 cupy_result = cupyx.scipy.ndimage.filters.generic_filter(cupy_array, cupy.mean, 3, mode="reflect", cval=0)

c:\users\genevieve\anaconda3\envs\cupy-dask-image\lib\site-packages\cupyx\scipy\ndimage\filters.py in generic_filter(input, function, size, footprint, output, mode, cval, origin)
   1075                                                      mode, origin, 'footprint')
   1076     in_dtype = input.dtype
-> 1077     sub = _filters_generic._get_sub_kernel(function)
   1078     if footprint.size == 0:
   1079         return cupy.zeros_like(input)

c:\users\genevieve\anaconda3\envs\cupy-dask-image\lib\site-packages\cupyx\scipy\ndimage\_filters_generic.py in _get_sub_kernel(f)
     26         raise TypeError('only ReductionKernel allowed (not ElementwiseKernel)')
     27     else:
---> 28         raise TypeError('bad function type')
     29
     30

TypeError: bad function type

I did try this, but it's not the answer either:
import cupy
import cupyx.scipy.ndimage.filters

my_mean = cupy.ReductionKernel('T x', 'T out', 'x', 'cupy.mean', 'out = a', '0', 'my_mean')

cupy_array = cupy.random.random((20, 20))
cupy_result = cupyx.scipy.ndimage.filters.generic_filter(cupy_array, my_mean, 3, mode="reflect", cval=0)
# produces a compilation error

cc/ @emcastillo @coderforlife

The functions that are passed to generic_filter will be called inside the GPU, so they need to be actual CUDA kernels, there is no easy way that we can call python code or regular host code from the GPU. You will need to create your own custom RawKernels or ReductionKernels, inside a ReductionKernel you can't call a regular cupy function as you are trying now, so you need to implement the mean yourself.
This is a snippet that does what you want. Hope you find it useful.

import cupy
import cupyx.scipy.ndimage.filters

my_mean = cupy.ReductionKernel(
    'T x',  # input params
    'T y',  # output params
    'x',  # map
    'a + b',  # reduce
    'y = a / _in_ind.size()',  # This is an undocumented variable and a hack
    '0',  # identity value
    'mean'  # kernel name
)

cupy_array = cupy.random.random((20, 20))
cupy_result = cupyx.scipy.ndimage.filters.generic_filter(cupy_array, my_mean, 3, mode="reflect", cval=0)

Thank you @emcastillo, that does indeed solve my problem 😄
Thanks for helping me get my feet wet with CUDA kernels!

We are planning to support these eventually through fusion kernels (automatically create CUDA kernels from Python code), however those are significantly more tricky to implement so are currently not supported.

The functions that are passed to generic_filter will be called inside the GPU, so they need to be actual CUDA kernels, there is no easy way that we can call python code or regular host code from the GPU. You will need to create your own custom RawKernel or ReductionKernel.
Inside a ReductionKernel you can't call a regular cupy function as you are trying now, so you need to implement the mean yourself 😞.
This is a snippet that does what you want. Hope you find it useful.
import cupy
import cupyx.scipy.ndimage.filters

my_mean = cupy.ReductionKernel(
    'T x',  # input params
    'T y',  # output params
    'x',  # map
    'a + b',  # reduce
    'y = a / _in_ind.size()',  # This is an undocumented variable and a hack
    '0',  # identity value
    'mean'  # kernel name
)

cupy_array = cupy.random.random((20, 20))
cupy_result = cupyx.scipy.ndimage.filters.generic_filter(cupy_array, my_mean, 3, mode="reflect", cval=0)

Hello
I need to use nanmean along with the cupyx scipy generic_filter
But I don't know how to make the custom function (how to count the nan present and ignore them )
I am making this filter to fill gaps in the images with the mean of the neighboring pixels ignoring the empty neighbors
After this step, I will use boolean indexing to extract the new values of the previously empty cells leaving the original pixels as they were.
I'll attach my numpy code for illustration
#input:
array= np.array([[[13, 21, 13,  np.nan],
                 [ 5, np.nan, 22, 14],
                 [15, 33,  np.nan,  np.nan],
                 [ 0,  0, np.nan,  np.nan]],
                [[13, 17, 13,  np.nan],
                 [ 5, np.nan, 33, 14],
                 [21, 33,  np.nan,  np.nan],
                 [ 0,  0, np.nan,  np.nan]],
                [[13, 21, 13,  np.nan],
                 [ 5, np.nan, 70, 14],
                 [21,  np.nan,  np.nan,  np.nan],
                  [ 0,  0, np.nan,  np.nan]]]
                , dtype=np.float32)

#footprint
mask = np.zeros((3,3,3))
mask[1,:]=1
mask[1,1, 1] = 0
result= ndimage.generic_filter(array, np.nanmean, footprint=mask, mode='constant', cval=np.nan)

Thanks for your time


Usage of dangerouslySetInnerHTML throws when using with Trusted Types

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
Some code in Material UI uses dangerouslySetInnerHTML. It will throw when using Trusted Types.
https://github.com/mui-org/material-ui/blob/0d94283959a3aa016881b9644767b937c34d2807/packages/mui-system/src/cssVars/getInitColorSchemeScript.tsx
https://github.com/mui-org/material-ui/blob/4a67b3ce32a1a6e89d1c36b2781db460159c9f57/packages/mui-material/src/OutlinedInput/NotchedOutline.js#L80
https://github.com/mui-org/material-ui/blob/ba2fce43a735f6085e68c2d76ab746a098488862/packages/mui-material/src/FormHelperText/FormHelperText.js#L115
https://github.com/mui-org/material-ui/blob/ba2fce43a735f6085e68c2d76ab746a098488862/packages/mui-material/src/InputAdornment/InputAdornment.js#L131
https://github.com/mui-org/material-ui/blob/01bd5a026bc0c4184a9774e64554f5a10cbeeda7/packages/mui-material/src/Select/SelectInput.js#L503
Expected behavior 🤔
Not using dangerouslySetInnerHTML.
Steps to reproduce 🕹
Cannot provide it in the sandbox.
Context 🔦
I'm using Trusted Types to secure our execution environment.
Your environment 🌎

`npx @mui/envinfo`
  System:
    OS: Windows 10 10.0.19044
  Binaries:
    Node: 17.3.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.17 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 8.3.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.19041.1266.0), Chromium (97.0.1072.69)
  npmPackages:
    @emotion/react: ^11.7.1 => 11.7.1
    @emotion/styled: ^11.6.0 => 11.6.0
    @mui/icons-material: 5.2.5 => 5.2.5
    @mui/lab: 5.0.0-alpha.61 => 5.0.0-alpha.61
    @mui/material: 5.2.5 => 5.2.5
    @mui/system: 5.2.5 => 5.2.5
    @mui/types:  7.1.0
    @types/react: ^17.0.38 => 17.0.38
    react: 18.0.0-rc.0 => 18.0.0-rc.0
    react-dom: 18.0.0-rc.0 => 18.0.0-rc.0
    typescript: 4.6.0-dev.20211202 => 4.6.0-dev.20211202

Fair enough, I don't see why we cannot add the unicode character as a child directly. Would you like to create a PR?

Cool, of course!

I had a bit a look at why we used the dangerous API in the first place. I could find https://github.com/mui-org/material-ui/pull/10380. I might have blindly copied a StackOverflow answer without realizing I was doing it wrong. All good.


Update CloudFront-TLS-1-2-2020 security policy to support TLS 1.3

Description of changes:
Cipher Suites

TLS_AES_128_GCM_SHA256
TLS_AES_256_GCM_SHA384
TLS_CHACHA20_POLY1305_SHA256
ECDHE-RSA-AES128-GCM-SHA256
ECDHE-RSA-AES256-GCM-SHA384
ECDHE-RSA-CHACHA20-POLY1305

Elliptical Curves

X25519
P-256
P-384

Signature Scheme/Algorithms (for both TLS 1.2 and TLS 1.3)

TLS_SIGNATURE_SCHEME_RSA_PSS_RSAE_SHA256
TLS_SIGNATURE_SCHEME_RSA_PSS_RSAE_SHA384
TLS_SIGNATURE_SCHEME_RSA_PSS_RSAE_SHA512
TLS_SIGNATURE_SCHEME_RSA_PKCS1_SHA256
TLS_SIGNATURE_SCHEME_RSA_PKCS1_SHA384
TLS_SIGNATURE_SCHEME_RSA_PKCS1_SHA512
TLS_SIGNATURE_SCHEME_RSA_PKCS1_SHA224
TLS_SIGNATURE_SCHEME_RSA_PKCS1_SHA1

Minimum Version

TLS12

Maximum Version

TLS13

Describe s2n’s current behavior and how your code changes that behavior. If there are no issues this pr is resolving, explain why this change is necessary.
Call-outs:
Update CloudFront-TLS-1-2-2020 to support TLS 1.3. It is currently not being used.
Testing:
Unit tests.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #1903 into master will decrease coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1903      +/-   ##
==========================================
- Coverage   81.52%   81.50%   -0.03%
==========================================
  Files         229      229
  Lines       17109    17109
==========================================
- Hits        13948    13944       -4
- Misses       3161     3165       +4

:heart_eyes: Any update on this?

Codecov Report

Merging #1903 into master will increase coverage by 0.50%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1903      +/-   ##
==========================================
+ Coverage   80.99%   81.50%   +0.50%
==========================================
  Files         247      229      -18
  Lines       18421    17109    -1312
==========================================
- Hits        14921    13944     -977
+ Misses       3500     3165     -335


Fixes for issue https://github.com/redis/hiredis/issues/827

See the issue for a repro. This fix also adds the ability for sdsrange to return an error in the unlikely event that the write buffer is larger than ssize_t.

Oh, I'm sorry. I see the SSL checks have failed. I will fix those as soon as I can.

I merged in your changes and just added a couple of tiny tweaks to get all the tests passing.
As usual, Windows is special :smile:
https://github.com/michael-grunder/hiredis/pull/new/blewis-master

Thanks!
On Tue, Jun 2, 2020 at 3:06 PM Michael Grunder<EMAIL_ADDRESS>wrote:

I merged in your changes and just added a couple of tiny tweaks to get all
the tests passing.
As usual, Windows is special 😄
https://github.com/michael-grunder/hiredis/pull/new/blewis-master
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/redis/hiredis/pull/828#issuecomment-637748429, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AABCZHXZ6CO7M5ZE42JQ34DRUVEUDANCNFSM4NQIK2VA
.

Sorry, I wasn't sure if you wanted me to close this one. Please close it as you see fit!
Best,
Bryan

Closing in favor of #830


Add FKs from synchronization_oauths

[ ] user_id
[ ] service ?

There has been no activity on this issue for more several months. We are closing it. If you think this still needs to be addressed please open a new issue.


allow for hyperlinks in view-result

I.e., the relevant documentation would link to https://docs.openshift.com/container-platform/4.7/networking/enable-cluster-wide-proxy.html like it would in the report
./oc-compliance view-result ocp4-moderate-cluster-wide-proxy-set
+----------------------+--------------------------------------+
|         KEY          |                VALUE                 |
+----------------------+--------------------------------------+
| Title                | Ensure that cluster-wide proxy       |
|                      | is set                               |
+----------------------+--------------------------------------+
| Status               | FAIL                                 |
+----------------------+--------------------------------------+
| Severity             | medium                               |
+----------------------+--------------------------------------+
| Description          | Production environments can          |
|                      | deny direct access to the            |
|                      | Internet and instead have an         |
|                      | HTTP or HTTPS proxy available.       |
|                      |                                      |
|                      |                                      |
|                      |                                      |
|                      | The Proxy object is used to          |
|                      | manage the cluster-wide egress       |
|                      | proxy. Setting this will             |
|                      | ensure that containers get           |
|                      | the appropriate environment          |
|                      | variables set to ensure              |
|                      | traffic goes to the proxy per        |
|                      | organizational requirements.         |
|                      |                                      |
|                      |                                      |
|                      |                                      |
|                      | For more information, see the        |
|                      | _relevant documentation_.              |
+----------------------+--------------------------------------+
| Rationale            | External networks tend to            |
...

/remove-lifecycle rotten


Support plugin prefixes

Plugins such as i18n include their own content types such as locale that can be queried via the api as well.
Those are exposed on sub paths of the form /api/{plugin}/{pluralName}.
When trying to fetch e.g. the locale type, currently the request is made to /api/locales as it is resolved through the fetched schema but the plugin prefix is not used although it can be derived from the plugin field in the schema.
Why is this useful?
Especially in the example case with locales, it can be used to query a list of all locales and their names in order to build e.g. a language switcher component.

@mwoelk I agree this would be an awesome feature, I tried to add such logic to the plugin but I faced a wall at some point with endpoints that does not respect the new API format which is the case for i18n.
I guess since the i18n plugin is a core feature we could make an exception for it in order to be able to query it.
cc @remidej  @markkaylor


added Username and profile pic at nav bar

   {{Auth::user()->name}}

                    </li>

do some changes to make to add path to profile pic

Ok i will work on it.
Thanks for your response
On Fri, 13 Sep 2019, 1:50 am Anderson Carpi<EMAIL_ADDRESS>wrote:

I think that's a good idea, but you should make it in a way that people
can customize it and at least enable/disable it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jeroennoten/Laravel-AdminLTE/pull/368?email_source=notifications&email_token=AKSKHWWHXOQXITGMXIU27ZTQJKP7NA5CNFSM4IWCNYMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6TEEZI#issuecomment-530989669,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKSKHWTMWKZI5Y5ZJKKHFR3QJKP7NANCNFSM4IWCNYMA
.


Utilize 3D cameras I no longer use for home automation

I have multiple Microsoft Kinect and Xtion that I no longer use. Although it requires to be plugged into a computer, they should be very functional as a security camera. Why can't I make use of them instead of buying even more cameras for home usage?

Found the request is already out there community.home-assistant.io#107067, 10 votes so far.

HoA integration https://www.home-assistant.io/integrations/camera/ I/F that seems to be widely used. So aim to connect to it.

HoA camera component src may help? https://github.com/home-assistant/core/tree/dev/homeassistant/components/camera

RPi + Kinect (+ ROS) https://www.hackster.io/dmitrywat/rgb-d-slam-with-kinect-on-raspberry-pi-4-ros-melodic-ace795#=


Break out long case-block into its own function.

The TreeUnwrapper::ReshapeTokenPartitions() is getting pretty big.

Codecov Report
Attention: 2 lines in your changes are missing coverage. Please review.

Comparison is base (4f5d869) 92.95% compared to head (fb769ae) 92.95%.

Files
Patch %
Lines

verilog/formatting/tree_unwrapper.cc
96.36%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master    #2057   +/-   ##
=======================================
  Coverage   92.95%   92.95%
=======================================
  Files         357      357
  Lines       26411    26411
=======================================
  Hits        24550    24550
  Misses       1861     1861

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


One-time binding

Due to its dynamic nature, formly necessarily adds a lot of watchers.  By my count, there's about 5 watchers added whenever a <formly-form> is used and anywhere from 9 to ~25 watchers added for each <formly-field>.  9 would be for just a field like { template: '<hr/>' } and I've seen around 25 for a typical formlyBootstrap field (and maybe some ng-messages stuff added in).
While number of watchers isn't the only performance metric to look at, I think it's fairly directly related in this case.  And while there should definitely be a tradeoff assumed when using something dynamic like formly, I wonder if we could get that number down at all by leveraging one-time binding.  Though I have to imagine there probably wouldn't be that many things that we could globally one-time bind since there's so many different options and use cases and some need some parts "live" while others need other parts "live."
I wonder if we could at least provide a master one-time-binding opt-in setting for folks who don't need very dynamic forms (maybe just leave ng-model-type stuff two-way bound and one-time-bind everything else?).  Or perhaps let users configure which parts of the <formly-form> and <formly-field> they want one-time bound?
I really don't even know what this would look like and I understand this might not be possible for people using formly with Angular 1.2, but perhaps others could give thoughts or feedback on whether and/or how this might work.

Feel free to makeapullrequest.com


use glob pattern instead of listing files for BUILD

fixes #781

This change is

I think it is better to be explicit and consistent.

If we're going to go for explicit lists of files then we need a pre-commit hook that verifies all new files are mentioned in a BUILD file.

@ZackButcher agreed. Let's get a pre-commit hook for gazelle working. It'd be awesome to couple that with codecov checks too (which currently are enforced for 3?? packages).

Closing this pull request create issue #784


Some icons truncated under kitty terminal

Under the kitty terminal most of the icons are truncated, basically losing the start of them. See https://sw.kovidgoyal.net/kitty/faq/#some-special-symbols-are-rendered-small-truncated-in-kitty.
This is not a minor fix though, since the author sees this as a 'feature' more than an issue. I'll look at it but i see that many other similar tools have the same issue in kitty.
Works perfectly in alacritty, and with ghostty coming public release in December, I'm not giving this much priority.

meh. The icons look fine under Ghostty, and indeed every other terminal so i'm going to assume this is a kitty issue and close as he has already stated (despite many reports) that this is not a bug


WIP - [ACS][AKS][OSA] Convert module to use multi-API

#8267

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[ ] I adhere to the Command Guidelines.

This PR hasn't been modified since January. I will close it for now. Please reopen when it is ready to be reviewed.


Integration of new fleet api

From now on, new vehicles do not support the old Tesla owner's API. From 2024 onward, no cars will support the current API.
Detailed plan here:
https://developer.tesla.com/docs/fleet-api#2023-11-17-rest-api-vehicle-commands-endpoint-deprecation-timeline-action-required

Ah nice catch, there is a discussion on that as well in #254 and @LelandSindt might already have taken a look too.

@pkuehnel  -- are you seeing failures? --- what commands are you using?

I got rid of Teslamateapi and implemented the new fleet api by myself (at least what I need), see here
I created a Dev Account at Tesla as well and am hosting a service so everyone using TeslaSolarCharger can create a Token from the application. All requests for cars that require the FleetAPI proxy as well are auto transmitted to my self hosted FleetAPI proxy.

For a few days now, my attempts to start/stop charging and change charge current started returning 403. TeslaMate is still able to pull data, but it appears commands are being rejected with 403 status.

Just tested, it looks like the wake command worked, but the /api/v1/cars/1/command/auto_conditioning_start command failed with a 403... I figured it was just a matter of time... I usually only use this automation in the winter time, so it may have been broken for some time.
@tobiasehlert  --- it might be time to pull the command portion of this service out... I don't anticipate having time or reason to migrate it to the new supported methods any time soon.

The commands are not working longer. I'm using teslamatapi to adjust charging speed, 403 response

Apparently the wake command via the HTTP API will likely remain working, as it requires no authentication. All other commands will require authentication from now on, so 403 should mean that we should be using the FleetAPI
As I was using TeslaMateAPI to control charging, I'm now looking into controlling charging via BLE, as it will likely be faster to adjust charging amps.

It would be great to have this working in teslamateapi! I had excess solar charging working use the tesla binding in OpenHAB and that worked well, but my car now also needs the Fleet API as of a few months.
I have Teslamate and teslamateapi running and was just about to migrate over to reading that via MQTT and sending commands for my charging rules over to using teslamateapi, but alas the error is "Tesla Vehicle Command Protocol required, please refer to the documentation here: https://developer.tesla.com/docs/fleet-api#2023-10-09-rest-api-vehicle-commands-endpoint-deprecation-warning"
Did someone look at the proxy that Tesla is offering yet?
Or can I poke Teslamate more directly to send these commands for me? I don't think it can do things like start_charging out of the box, can it?


Solution

great tests!

Hi @random-hummingbird ;)
Thanks for try our challenge. My team mates will contact you shortly.
Thanks!


Strict Mode Bug

There is a bug with the strict mode.
If you zoom in and make the box really big, then zoom out the crop box can go over the image.

Thank you!


Recreating Docker swarm leads to Err: listen tcp <IP_ADDRESS>:7946: bind: address already in use

Description
Recreating a Docker swarm with docker swarm leave -f and docker swarm init a couple of times leads to the following error in docker.log: Err: listen tcp <IP_ADDRESS>:7946: bind: address already in use
Joining workers to such a swarm manager then leads to Mar 16 11:16:52 secondblue dockerd[758]: time="2017-03-16T11:16:52.145876195Z" level=warning msg="memberlist: failed to receive: No installed keys could decrypt the message from=<IP_ADDRESS>:53924"
I came across this problem while writing a helper script to reset a (real hardwar) demo environment again and again. But it can be reproduced with Docker Machine.

Steps to reproduce the issue:

docker-machine create -d virtualbox tst
eval $(docker-machine env tst)
docker swarm init --advertise-addr <IP_ADDRESS>
docker swarm leave -f
docker swarm init --advertise-addr <IP_ADDRESS>
docker swarm leave -f
docker swarm init --advertise-addr <IP_ADDRESS>
docker swarm leave -f
docker-machine ssh tst
cat /var/log/docker.log

In parallel looking on the ports listening in the machine, the port 7946 is still listening after leaving the swarm:
$ docker-machine ssh tst
docker@tst:~$ netstat -an | grep 7946
tcp        0      0 :::7946                 :::*                    LISTEN
udp        0      0 :::7946                 :::*

Describe the results you received:
time="2017-03-17T07:37:17.975482519Z" level=info msg="Gossip cluster hostname tst-00b488f70cfd"
time="2017-03-17T07:37:17.975500395Z" level=debug msg="Encryption key 1: 6fc7c"
time="2017-03-17T07:37:17.975528348Z" level=debug msg="Encryption key 2: d51b0"
time="2017-03-17T07:37:17.975533599Z" level=debug msg="Encryption key 3: 8681a"
time="2017-03-17T07:37:17.975608225Z" level=error msg="Error in agentInit : failed to create memberlist: Failed to start TCP listener. Err: listen tcp <IP_ADDRESS>:7946: bind: address already in use"
time="2017-03-17T07:37:17.976687877Z" level=debug msg="Root CA updated successfully" cluster.id=i1q2pbhbd31n02a39oo1ovuj6 method="(*Server).updateCluster" module=ca
time="2017-03-17T07:37:17.977759203Z" level=debug msg="Calling GET /v1.26/swarm"
time="2017-03-17T07:37:17.978666940Z" level=debug msg="Calling GET /v1.26/nodes/jl5321ooxdhr5kths3f1ai904"
time="2017-03-17T07:37:21.224266845Z" level=error msg="failed to send node leave: timed out broadcasting node event"
time="2017-03-17T07:37:21.342478674Z" level=debug msg="checkEncryption(8jlu4ma, <nil>, 0, true)"
time="2017-03-17T07:37:21.372807365Z" level=debug msg="Revoking external connectivity on endpoint gateway_ingress-sbox (8d8be82e3a664e223b320217070052bf21cfc08e9997f5cb1e96671a16d926b3)"
time="2017-03-17T07:37:21.443056711Z" level=debug msg="Releasing addresses for endpoint gateway_ingress-sbox's interface on network docker_gwbridge"
time="2017-03-17T07:37:21.443085904Z" level=debug msg="ReleaseAddress(LocalDefault/<IP_ADDRESS>/16, <IP_ADDRESS>)"
time="2017-03-17T07:37:21.472006338Z" level=debug msg="Releasing addresses for endpoint ingress-endpoint's interface on network ingress"
time="2017-03-17T07:37:21.472074337Z" level=debug msg="ReleaseAddress(LocalDefault/<IP_ADDRESS>/16, <IP_ADDRESS>)"
time="2017-03-17T07:37:21.473235690Z" level=debug msg="releasing IPv4 pools from network ingress (8jlu4majgdvqiercuqqqhatgw)"
time="2017-03-17T07:37:21.473255783Z" level=debug msg="ReleaseAddress(LocalDefault/<IP_ADDRESS>/16, <IP_ADDRESS>)"
time="2017-03-17T07:37:21.473269962Z" level=debug msg="ReleasePool(LocalDefault/<IP_ADDRESS>/16)"

Describe the results you expected:
Should work multiple times.
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Client:
 Version:      17.03.0-ce
 API version:  1.26
 Go version:   go1.7.5
 Git commit:   60ccb22
 Built:        Thu Feb 23 10:40:59 2017
 OS/Arch:      darwin/amd64

Server:
 Version:      17.03.0-ce
 API version:  1.26 (minimum version 1.12)
 Go version:   go1.7.5
 Git commit:   3a232c8
 Built:        Tue Feb 28 07:52:04 2017
 OS/Arch:      linux/amd64
 Experimental: false

Output of docker info:
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 17.03.0-ce
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 0
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: active
 NodeID: jl5321ooxdhr5kths3f1ai904
 Is Manager: true
 ClusterID: i1q2pbhbd31n02a39oo1ovuj6
 Managers: 1
 Nodes: 1
 Orchestration:
  Task History Retention Limit: 5
 Raft:
  Snapshot Interval: 10000
  Number of Old Snapshots to Retain: 0
  Heartbeat Tick: 1
  Election Tick: 3
 Dispatcher:
  Heartbeat Period: 5 seconds
 CA Configuration:
  Expiry Duration: 3 months
 Node Address: <IP_ADDRESS>
 Manager Addresses:
  <IP_ADDRESS>:2377
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 977c511eda0925a723debdc94d09459af49d082a
runc version: a01dafd48bc1c7cc12bdb01206f9fea7dd6feb70
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.4.52-boot2docker
Operating System: Boot2Docker 17.03.0-ce (TCL 7.2); HEAD : f11a204 - Thu Mar  2 00:14:47 UTC 2017
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 995.8 MiB
Name: tst
ID: DI4T:HKXV:ZQJE:UGL4:EWIC:LQE3:72NV:YSTO:T5DU:6JAC:H5R3:6JLF
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 25
 Goroutines: 125
 System Time: 2017-03-17T07:54:40.549954175Z
 EventsListeners: 0
Username: stefanschererseal
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

Additional environment details (AWS, VirtualBox, physical, etc.):
VirtualBox, Raspberry Pi

ping @aboch @docker/core-swarmkit-maintainers

The sockets should be released when the network DB is shutdown.
I tried to reproduce this multiple times on a linux host but did not hit the issue yet.
It would be interesting to see in the docker logs if any warn/error from the swarm leave path are present.

Here is the docker.log https://gist.github.com/StefanScherer/86a03582bc0d5f3a9cf2d8cc59dae1bf
I repeated it in a fresh VirtualBox Docker Machine. I found out that after a docker swarm leave -f port 7946 is listening for some seconds after the command has finished. So if you wait for say 10 seconds the listening port disappears and then the docker swarm init works again.
Maybe on Raspberry Pi's it takes longer than 10 seconds, I can check that next week.

/cc @dongluochen

This issue should be fixed in 17.05 because of #32283 because now the swarm init/join will be processed only after the swarm leave is complete, after the networking agent has closed the network DB (control plane and its socket). Same after graceful daemon stop/start sequence, stop will wait for the graceful stop of network DB.

Fixed by #32283
But feel free to reopen if you are able to reproduce with 17.05


Issue with k8s.io/docs/tasks/access-application-cluster/access-cluster/

This is a...

[x] Bug Report

Problem:
The documentation says that kubectl needs to know the location of the cluster and credentials to access it, but doesn't explain how to get these params out of existing cluster and how to save them in kubectl. I suppose that there could be even some login command that authenticates and stores these details automatically.
Proposed Solution:
Explain the procedure in detail how to access existing cluster with kubectl.
Page to Update:
https://kubernetes.io/docs/tasks/access-application-cluster/access-cluster/#accessing-for-the-first-time-with-kubectl

@mengqiy 👋

We can add a section saying something like:
By default kubectl use the config file in ~/.kube/config.
You can view it by using kubectl config view.
And also link the following doc
https://kubernetes.io/docs/tasks/access-application-cluster/configure-access-multiple-clusters/

Linked doc still doesn't explain:

What is context?
What is certificate-authority and why it is important?
How to get that certificate-authority from the server?
How to generate client certificate and add it to server?
What for is client.key?

If that info is specific to cluster provider, then documentation could try to define common layout and link those docs.
For #4548 the journey is try minikube through ssh -> setup kubectl access to remote minikube through ssh tunnel (fails because of https://github.com/kubernetes/minikube/issues/1974).

@abitrolly There are another 2 docs:
https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/
https://lukemarsden.github.io/docs/user-guide/sharing-clusters/
@zacharysarah Maybe we want to do something e.g. reorg to make our doc more easier for user to understand.

@mengqiy Agreed! I'm giving this the Actionable label so that it stands a better chance of receiving work.

https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/

@mengqiy I don't remember seeing this link. At least there should be a link to it. Still it was not explained what context is for. so I edited the explanation https://github.com/kubernetes/kubernetes.github.io/pull/5611

/remove-lifecycle frozen

/remove-lifecycle stale


[Bug] Spurious issue with subgraph deployments

Bug report
We have an end to end test suite which does many subgraph deployments. We're find that our tests spuriously fail with subgraph validation error: [the specified block must exist on the Ethereum network]. In our test suite, we always deploy subgraphs with against mainnet with start blocks in the range of 0-100.
We can't reliably reproduce the issue but do find it happens often on different tests. Our API calls the subgraph_deploy on graph node and this is the full message that's returned: subgraph validation error: [the specified block must exist on the Ethereum network].
We're running graph node v0.31.0.
Relevant log output
No response
IPFS hash
No response
Subgraph name or link to explorer
No response
Some information to help us out

[ ] Tick this box if this bug is caused by a regression found in the latest release.
[ ] Tick this box if this bug is specific to the hosted service.
[X] I have searched the issue tracker to make sure this issue is not a duplicate.

OS information
None

Found some relevant logs from our e2e tests:
e2e-tests-graph-node-1   | Jul 07 07:50:18.580 INFO Received subgraph_create request, params: SubgraphCreateParams { name: SubgraphName("cljsa19l3001jc6joh17r1gq4") }, component: JsonRpcServer
e2e-tests-graph-node-1   | Jul 07 07:50:18.588 DEBG Created subgraph, subgraph_name: cljsa19l3001jc6joh17r1gq4, component: SubgraphRegistrar
e2e-tests-graph-node-1   | Jul 07 07:50:18.590 INFO Received subgraph_deploy request, params: SubgraphDeployParams { name: SubgraphName("cljsa19l3001jc6joh17r1gq4"), ipfs_hash: DeploymentHash("QmX2wBD6mB5CcqXkp9XP1HfF9LrdKwFSA5eddXVj8sYSTB"), node_id: None, debug_fork: None, history_blocks: None }, component: JsonRpcServer
e2e-tests-graph-node-1   | Jul 07 07:50:19.164 ERRO subgraph_deploy failed, params: SubgraphDeployParams { name: SubgraphName("cljsa19l3001jc6joh17r1gq4"), ipfs_hash: DeploymentHash("QmX2wBD6mB5CcqXkp9XP1HfF9LrdKwFSA5eddXVj8sYSTB"), node_id: None, debug_fork: None, history_blocks: None }, error: ManifestValidationError([BlockNotFound("100")]), component: JsonRpcServer

Which is very unusual because block 100 definitely exists on mainnet which is the network that this subgraph is being deployed against. We also see that this test often succeeds.

hey @paymog could you possibly run with TRACE logging in case there is more info on where this is failing?

hey @paymog could you possibly run with TRACE logging in case there is more info on where this is failing?

Totally, how do I do that? I searched for TRACE in MD files and don't see mentions of an env var which controls that.

The error from firehose is eaten up and there is no retry mechanism.
https://github.com/graphprotocol/graph-node/blob/27cbcdd0cc21bd9a22e604bf18fd0f6b6c8dc37e/graph/src/firehose/endpoints.rs#L387
Error could be one of:

network connection issue
TooManyRequests (backoff mechanism when getting a burst of connections)
server shutting down between the request and the response (ex: due to autoscaling)

IMHO, the IPFS call is made with a retry, I don't see why the "get_block" from firehose shouldn't also be done with a retry mechanism.

This is where the (legitimate?) error gets replaced by "Block Not Found":
https://github.com/graphprotocol/graph-node/blob/27cbcdd0cc21bd9a22e604bf18fd0f6b6c8dc37e/core/src/subgraph/registrar.rs#L527
The fetch block should be 1) retried (2 or 3 times is more than enough) and the error should bubble up (ex: connection error...) instead of being replaced by a BlockNotFound.

good catch @sduchesneau!


Replicate victory-bar docs change

/cc @david-davidson @boygirl

@exogen Huh, some weird call stack errors in CI--we can debug this one later.

This same error happens when I run on master, I think due to the eslint version (and related packages). victory-axis hasn't done a builder port yet, but it's in a PR.

@exogen I think this pr is safe to merge since we know what's failing CI now.

@boygirl @exogen Rebased on top of master (w/ builder port) => happy CI! Merging. :+1:


[Q] How to track a hard-coded config?

Sometimes there are so many configuration options and I know an option would always be set to the same value after comparison. I don't want to complicate the global configuration parser anymore. So I prefer to copy the code and hard code the option in different copies. Such an option still needs to be tracked for comparison. What's the easiest way to do this? Is there anything like a wrapper which I can add to the hard-coded option line and track it?

Hey @bfs18
By hard-coded config do you mean the configurations that are used to run the python script like 👇
python train.py -a a -b b -c c?

So I prefer to copy the code and hard code the option in different copies

What do you mean by copying the code to different copies?

For example, I might use different dropout rates or different activation functions.
dropout = 0.5
act_layer = nn.ELU()

These 2 values are passed to  other functions. These 2 assignment expressions are hard coded configurations. How to track assignment expressions with wandb.Config?

You could do something like
wandb.config.dropout = 0.5
wandb.config.act_layer = "elu"

And that will update the config for your run.


Support local volumes

Add support for locally mapped volumes. This could be implemented by building a sidecar image from the mapped files.
version: '3'
services:
  nextjs:
    restart: always
    image: caddy:2.7.6
    command: ["caddy", "file-server", "--root", "/static", "--listen", ":80"]
    #x-defang-static-files: /static
    volumes:
      - ./:/static
    ports:
      - target: 80
        published: 8000
        mode: ingress

Currently this emits a warning.

See also #490

This requires volume support, before we're able to copy the local files into the created volume.

I'm going to flag that this issue seems to be about mounting files from a local build context into a volume, as opposed to #818 which is about creating a volume that should be populated by the image at runtime/and persisted.

Though... depending on implementation, I guess these could work similarly:

When defang compose up is run, we create a cloud volume (EBS or something)

If they're using the ./localdir:/containerdir syntax, we create it based on the ./localdir name
If they're using the volumename:/containerdir syntax we create it based on the volumename

If they're using the ./localdir:/containerdir syntax, we check if there is anything in the volume

If there is, we copy that to the cloud volume, but only if we just created the volume (i.e. future defang compose up runs shouldn't overwrite the cloud volume)

I suspect we'll need a bunch of warnings to make this usable and safe at the same time.


Error in generate_report: 'content'

Describe the bug
Since updating to version 0.10.9 (same with 0.10.10) I get an error "Error in generate_report: 'content'" after successful web scraping. This only happens when I use a custom log handler - the moment I comment out the custom logs handler the report gets generated as usual
This happens irrespective of LLM used (OpenAI default, ollama various ...) and regardless of type of research.
How can the log handler afect report generation that way?
To Reproduce
this is the relevant part of my python app:
class CustomLogsHandler:
    """A custom Logs handler class to handle JSON data."""
    def __init__(self):
        self.logs = []  # Initialize logs to store data

    def set_widget(self, widget):
        self.widget = widget

    async def send_json(self, data: Dict[str, Any]) -> None:
        """Send JSON data and log it."""

        self.logs.append(data)  # Append data to logs
        output = data['output']
        if starts_with_emoji(output):
            output = f"\n{output}"
        self.widget.stream(output)
        if data['metadata']:
            for item in data['metadata']:
                self.widget.stream(item)

async def do_research(query: str, report_type: str = "research_report", widget=None) -> str:
    research_settings()
    custom_logs_handler = CustomLogsHandler()
    researcher = GPTResearcher(query=query,
                                report_type=report_type,
                                config_path=None,
                                websocket=custom_logs_handler,
                                )
    researcher.set_verbose(True)

    # Initialize the researcher
    with widget.add_step(status="running", running_title="Researching ...", success_title="job done!") as chatstep:
        custom_logs_handler.set_widget(chatstep)
        await researcher.conduct_research()
    report = await researcher.write_report()
    return(report)

Log excerpt:
INFO:     [07:42:51] ✍ Writing report for 'aspartame consumption and diabetes risk'...
{'content': 'writing_report',
'metadata': None,
'output': "✍ Writing report for 'aspartame consumption and diabetes risk'...",
'type': 'logs'}
{'output': '# Aspartame Consumption and Diabetes Risk: A Comprehensive '
'Analysis\n'
'\n',
'type': 'report'}
Error in generate_report: 'content'
INFO:     [07:42:53] 📝 Report written for 'aspartame consumption and diabetes risk'
{'content': 'report_written',
'metadata': None,
'output': "📝 Report written for 'aspartame consumption and diabetes risk'",
'type': 'logs'}
Expected behavior
Previously, the report would be generated without problems

@kga245 any chance you can help with this?

I am trying already… hopefully will have found the problem in the next
couple of days
Horst
On Mon, 30 Dec 2024 at 17:03, Assaf Elovic @.***> wrote:

@kga245 https://github.com/kga245 any chance you can help with this?
—
Reply to this email directly, view it on GitHub
https://github.com/assafelovic/gpt-researcher/issues/1052#issuecomment-2565100683,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADZYZTXIDY7ZDGDBQDFPXGD2IDV4XAVCNFSM6AAAAABULFJUZSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNRVGEYDANRYGM
.
You are receiving this because you authored the thread.Message ID:
@.***>


ValueError: 'a' cannot be empty unless no samples are taken

When run this line 'aug = PIL.Image.open(np.random.choice(self.anomaly_source_paths)).convert("RGB")', I encountered this error. By the way,  how to debug in 'bash run-wfdd.sh' mode?

Maybe this image path was null, but I don't know why?

Similar to #2 , please download the texture dataset DTD (Describable Textures Dataset), and configure --augpath with its absolute path.
Similar to #19 , you can use the command-line arguments to debug.

Similar to What does the augpath path hold? #2 , please download the texture dataset DTD (Describable Textures Dataset), and configure --augpath with its absolute path.
Similar to Impossible to train custom datasets... #19 , you can use the command-line arguments to debug.

Thanks, but how to debug the code with so many parameters?

For example, in PyCharm, you can input the command-line arguments into the Script Parameters box for debugging.


Model loading and weights for a few nodes

Hi,
During the first generation on my workflow some of the model weights and nodes seem to be downloading which adds a lot of overhead on the generation time. Is there a reason why it's doing this or a way I can bypass this issue?

This is the most efficient way for the model to handle many possible different weights.


Reduce artifact transforms logging from info to debug

Backport of 8da456e6dae0add9116ef7bc250fc3cb4a7372e6
Context
Logging this at info makes info logging very noisy, and there's nothing between default and info.
Contributor Checklist

[X] Review Contribution Guidelines.
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[X] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[X] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team.
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective.
[ ] Provide unit tests (under <subproject>/src/test) to verify logic.
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes.
[X] Ensure that tests pass sanity check: ./gradlew sanityCheck.
[X] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest.

Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

Master branch, but it's already merged to master, so it will be included in 8.12. You can try it with 8.12 nightlies (see https://gradle.org/nightly/).


Parallel tests

First step towards parallel tests
https://jira.hyperledger.org/browse/IS-1135
With the PR now many tests use their own wallet to test something and delete it afterwards.
Some global things remain for now. Marked some with FIXME.
This PR changes many file. Should you approve please merge soon because I fear a ton of merge conflicts otherwise.

@Artemkaaas @mattraffel I suggest to merge this PR as soon as https://github.com/hyperledger/indy-sdk/pull/1518#discussion_r266491335 will be resolved


Fix try/catch to choose the more specific exception handler

Fix #2293
Idea behind the Fix
After selecting a handler, for both try/catch and trap{}, we set $_ with new ErrorRecord(rte.ErrorRecord, exceptionToPass). The exceptionToPass will be adopted only if (rte.ErrorRecord.Exception is ParentContainsErrorRecordException) == true. So basically $_.Exception will always be rte.ErrorRecord.Exception unless it's a ParentContainsErrorRecordException instance. So we should just select the handler based on rte.ErrorRecord.Exception if it's not ParentContainsErrorRecordException. When it is ParentContainsErrorRecordException, then we go through the original code path to determine what exception to pass to user.
The old fix would cause unacceptable breaking changes (see the discussion below). The following is the new fix:
First rank the given exception types -- a smaller rank indicates a more specific exception type, for example, rank == 0 means the corresponding exception type is not derived by another other given exception types, while rank == 1 means the corresponding exception type is derived by another exception type in the given types. CatchAll is considered to be derived by any other exception type.
Then during the search, we try all existing searching methods in the same existing order, as long as we haven't found a handler whose exception type's rank is 0.
When a new handler is found, we use the following algorithm to decide whether to replace the current handler (the handler that was found before the new handler):

If new-rank is less than current-rank -- meaning the new handler is more specific, then we update the current result with it.
If new-rank is more than current-rank -- meaning the new handler is less specific, then we do NOT change the current result.
If new-rank is equal to current-rank, we do NOT change the current result UNLESS the current handler is catch-all. (This is to keep the original behavior -- prefer to use the later found exception as the exception-to-pass-in if all exceptions result in the catch-all handler.

With the Fix
PS D:\> try {
>>     Get-ChildItem c:\xyzzy -ea Stop
>> } catch [System.Management.Automation.ItemNotFoundException] {
>>     "ItemNotFoundException caught"
>> } catch [System.Exception] {
>>     "System.Exception caught"
>> }
ItemNotFoundException caught
PS D:\>
PS D:\> try {
>>     Get-ChildItem c:\xyzzy -ea Stop
>> } catch [System.Management.Automation.ItemNotFoundException] {
>>     "ItemNotFoundException caught"
>> } catch [System.Management.Automation.RuntimeException] {
>>     "RuntimeException caught"
>> }
ItemNotFoundException caught

Task

[x] Refine the fix
[x] Run our legacy tests to find potential regressions (ran the Github nightly build tests)
[x] Add tests

Hi @daxian-dbw, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Dongbo Wang). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

The potential breaking changes comes from trying to catch ParentContainsErrorRecordException?
If that's it, it seems safe. Most people just catch everything anyway.
I'd like some investigation to know for sure that ActionPreferenceStopException and CmdletInvocationException are always wrapped in a ParentContainsErrorRecordException.

I will investigate ActionPreferenceStopException and CmdletInvocationException further.

@lzybkr it turns out it causes quite a few regressions ☹ for example:
Before the change
PS:20> try { dir c:\xyzz -ea Stop }
>>     catch [System.Management.Automation.ActionPreferenceStopException] {
>>        "ActionPreferenceStopException Caught" }
ActionPreferenceStopException Caught

PS:22> try { Invoke-Expression "gcm -Name" }
>>     catch [System.Management.Automation.CmdletInvocationException] {
>>        "CmdletInvocationException Caught" }
CmdletInvocationException Caught

After the change
PS C:\> try { dir c:\xyzz -ea Stop }
>>      catch [System.Management.Automation.ActionPreferenceStopException] {
>>         "ActionPreferenceStopException Caught" }
dir : Cannot find path 'C:\xyzz' because it does not exist.
At line:1 char:7
+ try { dir c:\xyzz -ea Stop }
+       ~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ObjectNotFound: (C:\xyzz:String) [Get-ChildItem], ItemNotFoundException
    + FullyQualifiedErrorId : PathNotFound,Microsoft.PowerShell.Commands.GetChildItemCommand

PS C:\> try { Invoke-Expression "gcm -Name" }
>>      catch [System.Management.Automation.CmdletInvocationException] {
>>         "CmdletInvocationException Caught" }
Invoke-Expression : Missing an argument for parameter 'Name'. Specify a parameter of type 'System.String[]' and try again.
At line:1 char:7
+ try { Invoke-Expression "gcm -Name" }
+       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidArgument: (:) [Invoke-Expression], ParameterBindingException
    + FullyQualifiedErrorId : MissingArgument,Microsoft.PowerShell.Commands.InvokeExpressionCommand

And the awkward part of the current behavior is that sometimes $_.Exception in the catch block is not the same kind of exception that the catch block is supposed to capture, take the same commands as examples:
PS:24> try { dir c:\xyzz -ea Stop }
>>     catch [System.Management.Automation.ActionPreferenceStopException] {
>>        $_.Exception.GetType().FullName }
System.Management.Automation.ItemNotFoundException

PS:25> try { Invoke-Expression "gcm -Name" }
>>     catch [System.Management.Automation.CmdletInvocationException] {
>>        $_.Exception.GetType().FullName }
System.Management.Automation.ParameterBindingException

You can see that $_.Exception caught by catch [ActionPreferenceStopException] and catch [CmdletInvocationException] are ItemNotFoundException and ParameterBindingException respectively.

The root problem is we don't have a specific exception to search for handler. Instead, we have multiple candidate exceptions from which we pick up to suit the given handlers.
The fix needs to be re-worked, and I think we need to change new ErrorRecord(ErrorRecord, Exception) to allow forceful replacement of the exception.

@lzybkr I think this try/catch fix is ready. Can you please review this PR?


Window closes when I place a large amount of text in the clipboard

Issue Type: Bug
I'm switching from Sublime Text and evaluating how Visual Code compares. Dealing with unreasonably large text files is something most of text editors struggle with, but VS Code seems to do worse than just struggle. I made a .sql file with a million lines, weighing about 70 MB. Opening the file in VSC is okay, but noticeably slower than a regular file. However, when I hit CMD+A and CMD+C to copy the whole content, the app seems to crash and a standard windows error window pops up, saying "The window has crashed" with options to "Reopen" and "close".
VS Code version: Code 1.28.2 (7f3ce96ff4729c91352ae6def877e59c561f4850, 2018-10-17T00:23:51.859Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz (8 x 2195)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
7.76GB (2.84GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

vscode-eslint
dba
1.6.1

php-debug
fel
1.12.6

php-intellisense
fel
2.3.5

php-pack
fel
1.0.2

file-icons
fil
1.0.16

vs-color-picker
lih
0.7.0

vscode-scss
mrm
0.6.2

sublime-keybindings
ms-
4.0.0

vscode-css-peek
pra
2.1.0

magento-snippets
raf
0.1.3

@ananaszjoe it's very likely we run into OOM on v8, can you help try code --max-memory=4096 (first close all vscode instances) and see if it helps?