Firefox version

This extension is insanely useful. Would love to see a Firefox version, opening this issue to explore the possibility.

I've added the support for Firefox and submitted it as an add-on to https://addons.mozilla.org. Will update the README file when it's accepted.

It's now live on firefox addons 🥳
https://addons.mozilla.org/en-US/firefox/addon/hnrelevant/
Feel free to test it and report any issues


Decouple DAS from celestai-core

Summary
Since we decided to delegate DAS to celestia-node, we should remove this functionality in celestia-core.
Details
Per ADR 007, there have been extensive changes made to incorporate DAS into our fork of tendermint. Most of these changes will need to be reverted, and what remains should either be refactors so that it doesn't import celestia-core, moved to celestia-node, or moved to it's own repo.
Action Items

[x] #508
[x] https://github.com/celestiaorg/celestia-core/pull/514
[x] #523
[x] #518

References
tracking issue #491
ADR #504

While there is still some minor refactoring we could do (see #505), since #523 was merged, we have purged DAS from celestia-core and this issue can be closed.


Fix deprecated Qt usage

Replace obsolete QWheelEvent constructor
Replace obsoleted QWheelEvent functions
Use QMultiMap for maps storing multiple values with the same key

CI:

Linux
Linux-aarch64
macOS
Windows

I don't see any potential API break here.

Yeah, you're right. For some reason I thought I also modified a signature in the header 🙃

This broke CentOS 7 builds, which use Qt 5.9.7:
It isn't likely that we'll see a version bump of Qt5 in CentOS 7 any time soon. If we can't maintain compatibility, I'll need to drop RViz from CentOS packaging.


Couldn't find preset "es2015" relative to directory

I get an error compiling foundation-sites with gulp with the babel-preset-env.
It worked fine with the babel-preset-es2015 before:
The complete error:
> Error: Couldn't find preset "es2015" relative to directory "/Users/peter/Sites/gulp-es6/node_modules/foundation-sites/dist/js" while parsing file: /Users/peter/Sites/gulp-es6/node_modules/foundation-sites/dist/js/npm.js
>     at /Users/peter/Sites/gulp-es6/node_modules/babel-core/lib/transformation/file/options/option-manager.js:293:19
>     at Array.map (<anonymous>)
>     at OptionManager.resolvePresets (/Users/peter/Sites/gulp-es6/node_modules/babel-core/lib/transformation/file/options/option-manager.js:275:20)
>     at OptionManager.mergePresets (/Users/peter/Sites/gulp-es6/node_modules/babel-core/lib/transformation/file/options/option-manager.js:264:10)
>     at OptionManager.mergeOptions (/Users/peter/Sites/gulp-es6/node_modules/babel-core/lib/transformation/file/options/option-manager.js:249:14)
>     at OptionManager.init (/Users/peter/Sites/gulp-es6/node_modules/babel-core/lib/transformation/file/options/option-manager.js:368:12)
>     at File.initOptions (/Users/peter/Sites/gulp-es6/node_modules/babel-core/lib/transformation/file/index.js:212:65)
>     at new File (/Users/peter/Sites/gulp-es6/node_modules/babel-core/lib/transformation/file/index.js:135:24)
>     at Pipeline.transform (/Users/peter/Sites/gulp-es6/node_modules/babel-core/lib/transformation/pipeline.js:46:16)
>     at Babelify._flush (/Users/peter/Sites/gulp-es6/node_modules/babelify/index.js:26:24)

All other packages compile fine, though.

Hi @bonovski
This should be resolved by https://github.com/zurb/foundation-sites/issues/10910: we should now export Foundation as transpiled UMD modules instead of ESM modules.
See also https://github.com/zurb/foundation-sites/pull/10903 and https://github.com/zurb/foundation-sites/pull/10911.
I'm closing this for now. Please reopen if it is not resolved in the next release.

Hi, thanks for the links but that is not the solution with gulp.
I figured it out after some trial and error.
You have to change the preset in "node_modules/foundation-sites/package.json" from es2015 to env.
Hope that helps people with similar problems.


FIFO Matching + Basic User Infrastructure

Implemented a basic first-come first-serve matchmaker. Users are added to a matching queue when they request a match (submit the form) and then another method is called to see if anyone else is in the queue. If there's another user in the queue, and if the two users are not already matched, the users are both removed from the queue and matched. If the users have already been matched, then whoever asked for a match last gets alerted to try again (the method returns a false) and whoever sent in a match request first just stays in the queue. If no one is in the queue, the user remains in the queue until someone else requests a match.
Update: added unit testing and made relevant changes as they came up during testing. Next step is to integrate the unique identification system that Brenda suggested in the design doc.

This PR still has files from the target/ directory. I'd recommend removing them from git tracking to help keep the repo clean. If you don't know how, just ping me and I can help!

@googlebot I signed it!

@googlebot I signed it!


Serialize None to empty string instead of null

Serializing an Option<T> which is None will make it show up as null in yaml.
Since deserializing works without the value in the yaml (no-mention is correctly deserialized to None) it would be nice if one could set the option to serialize None to an empty string in reverse. In my use case, more concise serialization would be very nice.
I could imagine this as different derive or as an option you pass to the serde_yaml::to_string(...) , but any implementation would of course be enough for me.

serde_with::NoneAsEmptyString provides a serialization format agnostic way to translate between None and "".
#[serde_as(as = "serde_with::NoneAsEmptyString")]
tags: Option<String>,

You can also omit the None values from the serialized format, to make it more concise. You can put this attribute on the Option fields #[serde(skip_serializing_if = "Option::is_none")]. If you have many such fields, you might also be interested in the #[serde_with::skip_serializing_none] macro, which automates this.

That's what I was looking for, thanks!


CPMAddPackage does not export variables when finding local packages.

At first, I used CPMFindPackage to add third-party dependencies, because I wanted CPM to first find out if there was a package that needed to be installed locally, and then download and install it if there wasn't.
But then I noticed that CPMFindPackage does not export variables if it finds a locally installed package.
Then I noticed that if I use CPMAddPackage and define CPM_USE_LOCAL_PACKAGES I can also achieve the same function and export the variables after it finds the locally installed packages.
The problem is that I can't use the exported variables even though the logs output using local package.
My CMake code is roughly like this:
CPMAddPackage(
		NAME CURL
		GIT_TAG curl-7_87_0
		GITHUB_REPOSITORY "curl/curl"
		OPTIONS "CURL_USE_OPENSSL"
)

# set(linked_project CURL)
if (${linked_project}_ADDED)
		# downloaded
		message(STATUS "Successfully added [${linked_project}], the source files path is [${${linked_project}_SOURCE_DIR}], the binary files path is [${${linked_project}_BINARY_DIR}]!")
		# add_subdirectory(
		# 		${${linked_project}_SOURCE_DIR}
		# 		${${linked_project}_BINARY_DIR}
		# 		EXCLUDE_FROM_ALL
		# )
else ()
		message(FATAL_ERROR "Library [${linked_project}] not found!")
endif (${linked_project}_ADDED)

Everything works fine on Windows and Linux, but not on MacOS. I don't have a MacOS environment to test in, so I'm relying on GitHub Workflows.

If the local package is found, find_project() set ${linked_project}_FOUND and ${linked_project}_DIR, or not?
IMHO, that is right, because the other variables are related to CPM.cmake if the package was added.


Can't upload a file with camel case metadata (to set Firebase Download Token) using signed URLs on client side

Basically, what I'm trying to do is to have my server send a signed URL to the client and have the client upload the file and generate a Firebase download URL that gives public access to the upload file. The problem is that I cant send my download token as metadata to uploaded file, because it has to be camel case. I read somewhere in the docs that I could send the metadata as a JSON file too, but I couldn't make it work (it didn't gave me an error, just didn't set the metadata).
Environment details

OS: Ubuntu 20.04
Node.js version: v12.16.3
npm version: 6.14.4
@google-cloud/storage version: 5.5.0

Steps to reproduce

Generate a signed URL with the code below

const [url] = await storage.bucket(bucket_name).file(file).getSignedUrl({
    version: 'v4',
    action: 'resumable',
    expires: Date.now() + 24 * 60 * 60 * 1000,
    extensionHeaders: {
        'x-goog-meta-firebaseStorageDownloadTokens': 'a883673-4957-4120-8f52-f383ddddbfb1',
    }
})

Upload a file using this signed URL and sending the x-goog-meta-firebaseStorageDownloadTokens. My code looks something like this:

const chunkSize = 1024 * 1024

async uploadFile(file) {
    let sessionUri = await axios.post(signedUrl, null, {
        headers: {
            'x-goog-resumable': 'start',
            'x-goog-meta-firebaseStorageDownloadTokens': 'a883673-4957-4120-8f52-f383ddddbfb1',
            'content-type': 'image/jpeg'
        }
    }).then(response => {
        return response.headers.location
    })

    const slice = file.mozSlice ? file.mozSlice :
        file.webkitSlice ? file.webkitSlice :
        file.slice ? file.slice : () => {}

    let chunkStart = 0
    while(chunkStart < file.size) {
        let chunkEnd = chunkStart + chunkSize
        if (chunkEnd > file.size) {
            chunkEnd = file.size
        }

        let currentChunk = slice.bind(file)(chunkStart, chunkEnd)
        console.log(chunkStart, chunkEnd, currentChunk)

        await new Promise((resolve, reject) => {
            axios.put(sessionUri, currentChunk, {
                headers: {
                    'Content-Type': file.type,
                    'Content-Lenght': chunkSize,
                    'Content-Range': `bytes ${chunkStart}-${chunkEnd - 1}/${file.size}`
                }
            }).then(response => {
                console.log('[RESPONSE]', response)
                resolve()
            }).catch(error => {
                // RESPONSE WITH 308 ARE TREATED LIKE ERRORS BY AXIOS
                console.log('[ERROR]', error)
                resolve()
            })
        })

        chunkStart = chunkEnd
    }

    console.log('FILE UPLOADED')
}

So, the problem is that, the metadata firebaseStorageDownloadTokens, sent on the headers, become all lower case, which I understand is the way it is supposed to work, but that makes me unable to upload a file and retrieve a firebase download URL, because the file doesn't contain any firebase download token.
This is how it is:

And this is how I need it:

For firebase to read that as an access token it needs to be camel case and I don't know how I could accomplish that without asking for my server to change the metadata after the client uploads a file using the generated signed URL.

Hi @leoalopes,
I was able to confirm this is the case in the underlying GCS XML API, I think this is better as a feature request to the Storage Firebase API to allow both cases.
Hi @abeisgoat,
Where can I forward this FR to Storage for Firebase? In short, the Firebase Download Token metadata key should be case insensitive. When an object is created using the XML API metadata key's are lowercased on insert.
Would this be a reasonable FR for your team?

Moved issue to Firebase team to get more input.


User Onboarding Revamp

Problem solved
Short description of the bug fixed or feature added

PR-Codex overview
This PR focuses on improving user onboarding and account management in the application. It enhances the login flow, modifies team and account retrieval logic, and updates UI components for better user experience.
Detailed summary

Removed skipped state and replaced with complete in onboarding types.
Updated team retrieval logic to handle potential null values.
Introduced loginRedirect function for consistent login handling.
Added getValidAccount to enforce login and onboarding checks.
Refactored onboarding components for clarity and consistency.
Improved error handling and user feedback during email confirmation.
Removed unnecessary imports and cleaned up component structures.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#5471  👈 (View in Graphite)
#5461
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

I see the issue - forgot the call onComplete callback here.

This is fixed now

Fixed now


Update to mypy1.7

[x] Closes #8448
[x] Tests added
[x] User visible changes (including notable bug fixes) are documented in whats-new.rst

I guess we update manually for now?

I guess we update manually for now?

Yeah.
I wish we had something like dependabot for conda — it's very nice in poetry projects where it opens an PR with the upgrade...


Add type path to unneccesary case error

Pain point
When adding elm-review-simplify to a project that is reasonably mature already, it seems very likely to run into Unneccesary case expression errors:
(fix) Simplify: Unnecessary case expression

128| viewCheckoutError findOfferError =
129|     case findOfferError of
         ^^^^
130|         Offer.NotInValidityPeriodError _ _ ->

All the branches of this case expression resolve to the same value. You can
remove the case expression and replace it with the body of one of the branches.

If I don't want to tackle these right now, I might reference these types in an Simplify.ignoreCaseOfForTypes call.
Right now I have to manually go into the codebase and track down the module path leading to this type which is a bit tedious.
possible solution
I think it would be convenient if the rule already did this work for me by adding to the error message:
(fix) Simplify: Unnecessary case expression

128| viewCheckoutError findOfferError =
129|     case findOfferError of
         ^^^^
130|         Offer.NotInValidityPeriodError _ _ ->

All the branches of this case expression resolve to the same value. You can
remove the case expression and replace it with the body of one of the branches.

If this was intentional you can surpress this warning
by adding `Path.To.Type` to the rule configuration through `Simplify.ignoreCaseOfForTypes`.

I personally don't recommend to use this function too much,
because this could be a sign of premature abstraction,
and because I think that often [You Aren't Gonna Need this code](https://jfmengels.net/safe-dead-code-removal/#yagni-you-arent-gonna-need-it).

Hey @stefan-wullems 👋
Yeah, I was thinking of maybe removing this simplification. I can see how it prevents the compiler from helping you out in the future. I am still on the fence on whether to remove it altogether, or only for custom types specific to this project, and keep the simplification if all the referenced custom types come from dependencies.
I know that at least @janiczek put reservations on this simplification back when I added it (I would love your opinion again).
Otherwise, I agree that improving the error message would be nice 👍

If I don't want to tackle these right now

If you want to postpone, you can also use elm-review suppress (https://jfmengels.net/stop-the-bleed/). Not to be abused, but it can be very useful.

I agree that having the full qualified type name in the error would be a nice usability improvement!
@jfmengels After months of usage, this specific check is the only thing in Simplify that I need to go change in ReviewConfig. It comes up reasonably often. I understand that sometimes it will give me warnings I actually care about! It's just that I mostly get the kind-of-false positives.
Here's how it looks currently:
    , Simplify.defaults
        |> Simplify.ignoreCaseOfForTypes
            -- These custom types only have one constructor, but we still want
            -- to pattern-match as we may add more in the future.
            [ "API.Endpoints.ActivationMetrics.ActivationMetricsEndpoint"
            , "API.Endpoints.CohortSize.CohortSizeEndpoint"
            , "Publisher.Activations.Integrations.Empty.Action"
            , "Publisher.Settings.Integrations.WebhooksConfig.Action"
            , "Publisher.ContextualCohorts.Builder.Predicate.PredicateModel"
            , "Publisher.ContextualCohorts.Builder.AST.AffinityType"
            , "Redesign.Store.Action"
            ]
        |> Simplify.rule

Overall I'm fine with the status quo. If this was separated into its own rule / package, I'd probably not use it though.

@Janiczek Do you think your annoyances would be fully solved by only targetting custom types from dependencies? For instance, this means that the following would be simplified
case maybe of
  Just _ -> 1
  Nothing -> 1
--> 1

but not the following
case maybe of
  Just _ -> 1
  Nothing -> 1
--> 1

If we go this route, the previous configuration would become deprecated and unnecessary, and I'd probably remove it. Unless some people would like to ignore it for some custom types from dependencies? :thinking:

Do you think your annoyances would be fully solved by only targetting custom types from dependencies?
Yeah that would absolutely work for me!


Implement Fagin's rank aggregation methods

Efficient similarity search and classification via rank aggregation
R Fagin, R Kumar, D Sivakumar - Proceedings of the 2003 ACM …, 2003 - dl.acm.org
It's also patented:
Efficient similarity search and classification via rank aggregation
United States Patent Application<PHONE_NUMBER>1 Kind Code: A1

úÁÂÁ×ÎÏ. ÷Ó£ ÐÁÔÅÎÔÕÀÔ )
On 19 January 2015 at 01:11, Leonid Boytsov<EMAIL_ADDRESS>wrote:

Efficient similarity search and classification via rank aggregation
R Fagin, R Kumar, D Sivakumar - Proceedings of the 2003 ACM ..., 2003 -
dl.acm.org
It's also patented:
Efficient similarity search and classification via rank aggregation
United States Patent Application<PHONE_NUMBER>1 Kind Code: A1
--
Reply to this email directly or view it on GitHub
https://github.com/searchivarius/NonMetricSpaceLib/issues/32.

Some working version https://github.com/searchivarius/NonMetricSpaceLib/commit/64e6910dfaa6c3b4a398faaac879415a732b79b1

Actually, for L2, I would need to implement LSH-like projections.


replace pushState with replaceState

Fixes: #1301

This doesn't seem to work quite right for me in Firefox - please try the following:

From Devices list view, click on an individual Device to go to the detail view.
Click Back once, it returns to the list view (good!)
Go forward once, returning to the detail view, and click the "Advanced" tab to switch to that tab.
Click Back once, it returns to the list view rather than the base detail view (wrong!)
Go forward once, it returns to the Advanced tab rather than the base detail view (wrong!)
Click on the "Device" tab to switch back to the base detail view.
Click Back once, it returns to the Advanced tab (good!).

This doesn't seem to work quite right for me in Firefox - please try the following:

From Devices list view, click on an individual Device to go to the detail view.
Click Back once, it returns to the list view (good!)
Go forward once, returning to the detail view, and click the "Advanced" tab to switch to that tab.
Click Back once, it returns to the list view rather than the base detail view (wrong!)

Just tested on latest commit (705fa90).
For me on Google Chrome 98 it just stays on the Advanced tab for the first Back click, and then the 2nd returns to list view.

Go forward once, it returns to the Advanced tab rather than the base detail view (wrong!)

I can confirm this behavior on Chrome 98 as well.

Click on the "Device" tab to switch back to the base detail view.
Click Back once, it returns to the Advanced tab (good!).

My bad, I was actually testing Site instead of Device.


Poisson mesh issue with normal estimation

Hi there,
I am using nerf to export mesh using Poisson. However, the result was like this video below.
I predict that the issue due to normal estimation problem when training with normal prediction. I render "normal show" on and off in Meshlab for reference.
Can anyone give me an advice on this to improve mesh generation?
Thanks in advance.
https://user-images.githubusercontent.com/110378166/218024760-55561978-d5d8-494f-bd1e-0197ec9acb91.mp4

The mesh generation method is fairly simplistic at the moment so results like this aren't that unprecedented. If you want a better mesh, consider exporting at a point cloud and using other tools to convert the pointcloud into a mesh. Alternatively look into sdfstudio which is better designed to recover geometry.

The mesh generation method is fairly simplistic at the moment so results like this aren't that unprecedented. If you want a better mesh, consider exporting at a point cloud and using other tools to convert the pointcloud into a mesh. Alternatively look into sdfstudio which is better designed to recover geometry.

Thank you @tancik for helpful advice. The problem as above due to not good colmap estimation, I think. After remove some not good images, I can get reasonable result now. However, when I increased the number of faces, some "noise" faces appear while small number of face did not. Also, when increasing the value std-ratio also reduce these "noise". Please see the video here.
https://user-images.githubusercontent.com/110378166/222665413-66d81f96-fca3-470a-83a2-9d452a23bcd3.mp4
You can see that the "noise" faces have very different color with surrounding while they locate on a similar surface with surrounding. My question is: why the colors of the "noise" faces are very different because I understood that colors are predicted by nerf based on location? Do you have any advice on this?

I'm not really sure what is going on. The colors are predicted by casting small around the surface of the object along the normals. These rays might have poor normals, or they might be cast in an area with bad geometry.


improvement: add docker-compose.yml for tests

@locona thanks!

:tada: This PR is included in version 1.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


add the option to display more of the facet results than the top ten

add the option to display more of the facet results than the top ten

this is a duplicate entry


preprocess different -seq_length for input an output

Sometimes the input length may be much longer than the desired max output length, so there should be two options.

Good point, we will add

Added feature request to our forum http://forum.opennmt.net/t/preprocess-lua-length-options/42/1


Feature improve node loading

Codecov Report

Merging #232 (225a475) into master (f66afcf) will decrease coverage by 0.06%.
The diff coverage is 90.62%.

@@            Coverage Diff             @@
##           master     #232      +/-   ##
==========================================
- Coverage   96.10%   96.04%   -0.07%
==========================================
  Files         151      150       -1
  Lines        3521     3537      +16
==========================================
+ Hits         3384     3397      +13
- Misses        137      140       +3

Impacted Files
Coverage Δ

...l/jamtemplate/common/pathfinder/node_interface.hpp
100.00% <ø> (ø)

impl/jamtemplate/common/pathfinder/node.cpp
95.45% <75.00%> (-4.55%)
:arrow_down:

impl/jamtemplate/common/tilemap/tileson_loader.cpp
98.51% <92.30%> (-1.49%)
:arrow_down:

impl/jamtemplate/common/tilemap/tile_node.cpp
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


colab error code

ValueError: File cannot be fetched: /content/drive/MyDrive/SD/extensions/sd-webui-3d-open-pose-editor/style.css. All files must contained within the Gradio python app working directory, or be a temp file created by the Gradio python app.

tunnel : ngrok

await self.app(scope, receive, send)

File "/usr/local/lib/python3.9/dist-packages/starlette/routing.py", line 66, in app
response = await func(request)
File "/usr/local/lib/python3.9/dist-packages/fastapi/routing.py", line 237, in app
raw_response = await run_endpoint_function(
File "/usr/local/lib/python3.9/dist-packages/fastapi/routing.py", line 163, in run_endpoint_function
return await dependant.call(**values)
File "/usr/local/lib/python3.9/dist-packages/gradio/routes.py", line 337, in file
raise ValueError(
ValueError: File cannot be fetched: /content/drive/MyDrive/SD/extensions/sd-webui-3d-open-pose-editor/style.css. All files must contained within the Gradio python app working directory, or be a temp file created by the Gradio python app.

Due to Gradio limitations, extensions must be placed under webui directory.
See https://github.com/AUTOMATIC1111/stable-diffusion-webui/issues/7684.


feat(ui): add smooth toggle transition for reposity issues list

this PR adds a smooth toggle animation to the repository issues list.
https://github.com/user-attachments/assets/a60fb719-3083-4235-afdf-66560f312a0d

@seanmarcia no worries! glad you think so :)


Update LICENSE.txt to remove "All rights reserved" term

Remove the term All Rights Reserved as Microsoft no longer recommend it.

See also: https://github.com/PowerShell/PowerShell/pull/12729

@SteveL-MSFT @JamesWTruher Can you review?

@iSazonov can you merge in this repo?


Validate Rancher supports k8s 1.22

Due to the dropped APIs, there are significantly more checks needed to validate that k8s 1.22 can be supported.
Supporting installing Rancher onto k8s 1.22 clusters

[x] Validating runtime resources - https://github.com/rancher/rancher/issues/33222
[x] Updating Helm Server chart - https://github.com/rancher/rancher/issues/34058
[x] Ingress support - https://github.com/rancher/rancher/issues/33312 and https://github.com/rancher/rancher/issues/30053
[assigned] Dropping Component Status Support - https://github.com/rancher/rancher/issues/34055

Supporting Downstream k8s 1.22 clusters
[assigned] Supporting k8s 1.22 into Rancher to support 1.22 downstream clusters (client-go for 1.22) - https://github.com/rancher/rancher/issues/34054

[x] Adding k8s 1.22 into KDM/RKE - https://github.com/rancher/rancher/issues/33114
[assigned] Adding k8s 1.22 for RKE2/k3s - https://github.com/rancher/rancher/issues/34056
[x] Validating k8s 1.22 works for EKS - https://github.com/rancher/rancher/issues/33623
[x] Validating k8s 1.22 works for AKS - https://github.com/rancher/rancher/issues/33622
[x] Validating k8s 1.22 works for GKE - https://github.com/rancher/rancher/issues/33621

Supporting Applications in k8s 1.22

[x] Continuous Delivery/Fleet - https://github.com/rancher/rancher/issues/33112
[ ] Apps and Marketplace Apps - https://github.com/rancher/rancher/issues/34057
[x] Legacy Apps - https://github.com/rancher/rancher/issues/34059

unfortunately there is no warning in the official docs noticing people like me that you cannot use the latest version of k3s which is now v1.22.3+k3s1 to run the latest version of rancher until we, ourselves, reach to this ...
[FATAL] the server could not find the requested resource

Just ran into this when upgrading my RKE2 Cluster... It's a bit inconvenient to have latest stable RKE2 not work with latest stable Rancher.

Just to echo the above statements, would have loved a more obvious warning about compatibility before I wasted my night trying to deploy this on the latest stable RKE2

Rancher's support matrix shows which k8s versions are supported for k3s/rke2 - https://www.suse.com/suse-rancher/support-matrix/all-supported-versions/rancher-v2-6-2/
I do agree we can work on making this more obvious.

Just to echo the above statements, would have loved a more obvious warning about compatibility before I wasted my night trying to deploy this on the latest stable RKE2

Yes I feel the same way, it really isn't obvious at all, it should be clearly stated in their deployment docs. This whole thing is a mess and support is getting pushed back realease by release. There isn't even a clear roadmap. At least as far as I can tell.
But if you're willing to run an RC the 2.6.3 version can be deployed on 1.22. clusters.
git clone --depth=1 -b v2.6.3-rc4 https://github.com/rancher/rancher
sed -i "s/%VERSION%/2.6.3-rc4/g" rancher/chart/Chart.yaml
sed -i "s/%APPVERSION%/2.6.3-rc4/g" rancher/chart/Chart.yaml
sed -i "s/%POST_DELETE_IMAGE_NAME%/rancher\/shell/g" rancher/chart/values.yaml
sed -i "s/%POST_DELETE_IMAGE_TAG%/v0.1.10/g" rancher/chart/values.yaml

helm install --create-namespace -n cattle-system rancher/chart/ rancher [-f values.yaml]

Hi,
I see that @sowmyav27 you postponed to v2.6.4 instead of v2.6.3, unfortunately this bug is critical for us as our cluster is down due to this deployment issue: https://github.com/rancher/rancher/issues/35174
Rancher is not installed correctly and the dependencies are also down due to this impact such as Longhorn volumes are down.
The cluster is just unusable at all and it cost money. Could you please push a bit to have this issue fix in the next version?
In my view, as this is critical it should be done via hotfixes, but if not possible then it should be included in the next version.
Thank you a lot and anyway we love your work ;)

@corend We are introducing k8s 1.22 as experimental in 2.6.3 Rancher release and will be GA in 2.6.4 Rancher release.

closing this ticket, as the only remaining issues are tracked for apps & marketplace:
Apps and Marketplace Apps - https://github.com/rancher/rancher/issues/34057


Subject encode problem using templates

Issue Summary
There's a problem with subject encoding while using templates variables.
Steps to Reproduce
$from = new SendGrid\Email("CoffeeBay", "***@coffeebay.cz");
$subject = "Just because it cant be empty";
$to = new SendGrid\Email(null, "***@coffeebay.cz");
$content = new SendGrid\Content("text/html", "Just because it cant be empty");
$mail = new SendGrid\Mail($from, $subject, $to, $content);
$mail->personalization[0]->addSubstitution(":email_year", "***");
// ... a few more substitution
$mail->setTemplateId("***");

Real subject "Přišla nová objednávka z CoffeeBay" is saved in template.
The bottom email is what the wrong subject looks like:

Raw:
Subject: Přišla nová objednávka z CoffeeBay
I tried utf_encode() but doesnt help.  (#162)
When I remove template:
$from = new SendGrid\Email("CoffeeBay", "***@coffeebay.cz");
$subject = "Just because it cant be empty";
$to = new SendGrid\Email(null, "***@coffeebay.cz");
$content = new SendGrid\Content("text/html", "Just because it cant be empty");
$mail = new SendGrid\Mail($from, $subject, $to, $content);

everything works just fine (top email on picture).
Raw:
Subject: =?UTF-8?B?UMWZacWhbGEgbm92w6Egb2JqZWRuw6F2a2EgeiBDb2ZmZWVCYXk=?=
Any ideas? Thank.

Hello @milanzitka,
Have you tried using this sample code? https://github.com/sendgrid/sendgrid-php/blob/master/USE_CASES.md#with-mail-helper-class
When I tried it, both with setting the $subject and storing the subject in the template, I did not see the wrong subject.

Hello @thinkingserious,
thank you for your reply. And yes, i tried it. But i tried again today, and it seems like there's problem only when I add some substitution.
This is okay:

$from = new SendGrid\Email(null, "emailfrom");
$to = new SendGrid\Email(null, "emailto");
$subject = "Something";
$content = new SendGrid\Content("text/html", "Something");
$mail = new SendGrid\Mail($from, $subject, $to, $content);
$mail->setTemplateId("***");

This not:

$from = new SendGrid\Email(null, "emailfrom");
$to = new SendGrid\Email(null, "emailto");
$subject = "Something";
$content = new SendGrid\Content("text/html", "Something");
$mail = new SendGrid\Mail($from, $subject, $to, $content);
$mail->setTemplateId("***");
$mail->personalization[0]->addSubstitution("::email_year", "2016");

Thanks for the follow up @milanzitka,
It looks like we are going to have to dig further on this one. That is strange behavior indeed.

Is this issue still unresolved?
im having the same problems

Hello @Nightzer,
This issue is still on our backlog pending investigation. I've just now added your vote to help move it up the queue.
Thanks!

I have the same Problem. I went with sendgrid Support and exchanged lots of messages but at the end i have up because Support was not able to help me. Thinking about moving from transactional Templates to own stuff because of this. But the Templates was one of the main reasons i wanted to go with sendgrid...

@rh78,
Our engineers are now working on a fix and I'll update this thread when it goes live.
My apologies for the inconvenience and we appreciate your patience.
With Best Regards,
Elmer

Thanks. Can you give us some timeframe when to expect a fix? We want to go live by end of January.

Ps: for me its not PHP but .net API but it seems to be a cross API Problem.

@rh78,
Yes, it's an API level problem.
Unfortunately, I do not have deep insight into the engineering timeline. But the fact that the issue is in development now, leads me to believe it should be pushed live by the end of January, but I can not guarantee that.

Hello @littlewall @Nightzer @rh78,
My apologies for allowing this to fall between the cracks. I should have updated you regarding the fix back in August.
Please let me know if you continue to experience this issue.
With Best Regards,
Elmer


iOS 11

I know iOS 11 is still in beta, but just wanted to let you know that it doesn't work at all on iOS 11. I took at look at some of the methods, like "allInstalledApplications", and they just return an empty array :(
No idea if there is a workaround

Reproduced on the release version of iOS 11. Would love to know if this is feasibly fixable or if this is a dead project.

+1, i really need to know url shemas of an application (For open it by a link)

This private method cannot be used after ios11. How to solve

+1, i really need to know url shemas of an application (For open it by a link)

Sorry, cannot be used after ios11, abandoned by apple.

Only works on Simulator now.


file-templates are not working on ruby mode (rails project)

This template is not beign called on ruby mode.
https://github.com/hlissner/doom-emacs/blob/develop/modules/editor/file-templates/templates/ruby-mode/__module
I think projectile rails is overriding the file-templates.  Another thing is:
This __module is only called on  /lib.  It need to be called on everything on /app/some_folder that is not /app/models /app/controllers /app/views /app/admin /app/jobs /app/serializer /app/

Feel free to PR a change to these lines

projectile-rails comes with its own share of "file templates", defined here: https://github.com/asok/projectile-rails/blob/master/projectile-rails.el#L993. I think the ones below app/ are okay, but you're right that the ruby file template __module is not used. This can be changed with the following advice (there's probably a better way to do so, but it works):
(when (featurep! :editor file-templates)
  (defadvice! +projectile-rails-ignore-snippet-for-module-a (last-part name)
    "Use ruby-mode's __module file template by returning no snippet."
    :override 'projectile-rails--snippet-for-module
    nil))

Together with adding the app/ subdirectory as is to +file-templates-alist, the file-template is used where projectile-rails would apply its own module snippet, while the other app/ snippets come from projectile-rails.
While looking into this, I found a bug in the __module snippet. The first line (file name comment) ignores subdirectories, e.g. it evaluates to # lib/foo.rb in project-root/lib/whatever/foo.rb.


Added link to mbed CLI for Windows Installer

Added a reference to the mbed CLI for Windows Installer in the Installation section. I found this difficult to find without knowing it was also listed in the sidebar.

@dhwalters423 please rebase.
@AnotherButler please review.

@screamerbg @AnotherButler Please reject this PR- I have resubmitted the PR with a new one that has been rebased from the latest commits rather than merged. See PR 542: https://github.com/ARMmbed/mbed-cli/pull/542


seata-spring-boot-starter 注册时，选用redis注册报错

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Ⅰ. Issue Description
采用redis作为注册器的时候，redis.db 类型转换异常
Ⅱ. Describe what happened
If there is an exception, please attach the exception trace:
redis 作为注册中心时发生的
Just paste your stack trace here!

Ⅲ. Describe what you expected to happen
Ⅳ. How to reproduce it (as minimally and precisely as possible)
修改 RegistryRedisProperties 中 db 中类型
Ⅴ. Anything else we need to know?
Ⅵ. Environment:

JDK version : 1.8
OS : win10
Others:

db in RegistryRedisProperties is String
@xingfudeshi add miss param password


Terragrunt v0.12.6 remote state s3 backend

Hi,
First of all thank you for your effort. Today I tried the new patch, downloading Terraform v0.9.3 with Terragrunt v0.12.6 trying to migrate all my templates. Unfortunately, the remote state files are not uploaded to S3 buckets. In particular, this is my terraform.tfvars file:
terragrunt = {
remote_state {
backend = "s3"
config {
bucket     = "my-bucket"
key        = "my-folder/terraform.tfstate"
region     = "eu-west-1"
encrypt    = true
lock_table = "terragrunt_locks"
}
}
terraform {
source = "git::my-source"
}
}
access_key = ""
secret_key = ""
aws_region = ""
Then I run the following commands:

terragrunt plan --terragrunt-source-update
terragrunt apply

The tfstate file is saved in my temp directory instead of s3 bucket. I get this output from CLI:
$ terragrunt apply
[terragrunt] [C:...] 2017/04/24 14:07:18 Running command: terraform --version
[terragrunt] 2017/04/24 14:07:19 Reading Terragrunt config file at C:/.../terraform.tfvars
[terragrunt] 2017/04/24 14:07:19 Terraform files in C:/.../terragrunt-download/xg503kJNvTVMtqN2JAmhZHXKe-4=/UnhX7_f3VZm_gKKqTdGLRsX55eg=/... are up to date. Will not download again.
[terragrunt] 2017/04/24 14:07:19 Copying files from C:/.../test into C:/.../Temp/terragrunt-download/xg503kJNvTVMtqN2JAmhZHXKe-4=/UnhX7_f3VZm_gKKqTdGLRsX55eg=/...
[terragrunt] 2017/04/24 14:07:19 Setting working directory to C:/.../Temp/terragrunt-download/xg503kJNvTVMtqN2JAmhZHXKe-4=/UnhX7_f3VZm_gKKqTdGLRsX55eg=/...
[terragrunt] 2017/04/24 14:07:19 Initializing remote state for the s3 backend
[terragrunt] 2017/04/24 14:07:19 Configuring remote state for the s3 backend
[terragrunt] 2017/04/24 14:07:19 Running command: terraform init -backend-config=bucket=my-bucket -backend-config=key=my-folder/terraform.tfstate -backend-config=region=eu-west-1 -backend-config=encrypt=true -backend-config=lock_table=terragrunt_locks
Downloading modules (if any)...
Get: s3::https://s3-eu-west-1.amazonaws.com/s3-bucket/my-module.tar.gz
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your environment. If you forget, other
commands will detect it and remind you to do so if necessary.
[terragrunt] 2017/04/24 14:07:20 Running command: terraform apply
module.eb_application.aws_elastic_beanstalk_application.eb_application: Creating...
name: "" => "test"
module.eb_application.aws_elastic_beanstalk_application.eb_application: Creation complete (ID: test)
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
The state of your infrastructure has been saved to the path
below. This state is required to modify and destroy your
infrastructure, so keep it safe. To inspect the complete state
use the terraform show command.
State path:
As you can see the state path is null.
Please, let me know if I miss anything.
Regards,
Luca Tartarini

Did you add the backend block to your Terraform configurations (.tf files)?
terraform {
  backend "s3" {}
}

It works great! I think I skipped the section of the README that explains it.
Thank you,
Luca

Great!


two blueprint plugin bug fixes

Description

Bug fix from  @Laganellac to avoid copying connectivity array in inner loop
Adds support for unsigned 64-bit fields

Type of change

[x] Bug fix
[ ] New feature
[ ] Documentation update
[ ] Other

How Has This Been Tested?
Tested by compiling on my mac.
Checklist:

[x] I have followed the style guidelines of this project.~~
[x] I have performed a self-review of my own code.~~
[x] I have commented my code where applicable.~~
[x] I have updated the release notes.~~
[x] I have made corresponding changes to the documentation.~~
[x] I have added debugging support to my changes.~~
- [ ] I have added tests that prove my fix is effective or that my feature works.
[x] I have confirmed new and existing unit tests pass locally with my changes.~~
- [ ] I have added new baselines for any new tests to the repo.
[x] I have NOT made any changes to protocol or public interfaces in an RC branch.~~
[x] I have assigned reviewers (see VisIt's PR procedures for more information).~~

also applied to develop in #17233


Clean up recon_intra.rs, which are ported from libaom

Remove left over libaom code when poring to rav1e
Uncomment some array declarations, which are not used now but required
for PARTITION_VERT_A and _B in the future.

Coverage remained the same at 81.975% when pulling c0cae8e3fc77b9d01812d49f47722f721ee20a10 on ycho:cleanup_recon_intra_rs into 1dddab988f5ee1b5b5e69fb569774bf172444c1a on xiph:master.

Seems fine to me, thank you :)

Thanks!


fix: ping types.

Adds types to the options of the ping function and represents it returning a promise.

Thanks!


Support #page, #track, #group, and pull in user traits from #identify

Based on plenty of feedback and requests, we need to support these other methods. Should be pretty straightforward.
Thanks!

@ryana main question here is around Ramen.version, otherwise lgtm

If there is a standard way to track integration 'versions' let me know. I couldn't find anything, but I did not check exhaustively.

@ryana We don't really have a way to track an integration version right now because we don't provide any way for users to select a given version, which kind of makes exposing a version for an individual integration not very useful.

@ndhoule I understand. This isn't for users to check. It's just so that RamenJS can provide a smooth experience without having to coordinate releases. If you'd prefer, I can remove Ramen.version and make the identity call set window.ramenSettings.partner_version to 0.2.0 instead of messing with the prototype.

Ok .version has been removed. Thx!

Hey guys any word on this? @ndhoule @amillet89 -- I'd like to get this and the new https://segment.com/docs/integrations/ramen page up before next Wednesday.

Ok @ndhoule this is ready to go. Tests are passing. Let me know what you think!

Hey @ndhoule any word here?

looks good @ryana, sorry for the delay, will get this pushed out today!

Thank you sir!


Added support for rocksdb

Added support for packaging rocksdb with cxx-common.

This is older than what is checked in to the vcpkg repo that we use. Is there a reason for using an older version?

There is no reason of using the older version. I didn't check the default version checkout with vcpkg. We can use the same for installing the dependencies.

@ekilmer, I updated the PR. I don't need a specific version and can use the default version with vcpkg.


Fixed non-UTF8 characters.

Summary
Fixed several non-UTF8 characters throughout the source code.
Impact
N/A
Testing
N/A

@fjpanag nice! How did you search for non-UTF8 chars?

@fjpanag nice! How did you search for non-UTF8 chars?

I used cvt2utf to do the conversion.
Is it possible to include this in CI, so non-UTF8 characters are no more introduced in the codebase?

@fjpanag nice! How did you search for non-UTF8 chars?

I used cvt2utf to do the conversion.
Is it possible to include this in CI, so non-UTF8 characters are no more introduced in the codebase?

it's good ideal to add some guard in CI. BTW, should we apply the same change to apps/ folder too.

@fjpanag let's fix the follow style issue?
Warning: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/arch/arm/src/a1x/hardware/a10_memorymap.h:289:1: warning: #include outside of 'Included Files' section
Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/boards/arm/lpc31xx/ea3[13](https://github.com/apache/incubator-nuttx/actions/runs/3135514943/jobs/5091280431#step:3:14)1/src/lpc31_mem.c:106:78: error: Long line found
Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/boards/arm/lpc31xx/ea3152/src/lpc31_mem.c:106:78: error: Long line found
Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/boards/arm/sama5/sama5d3-xplained/src/sam_ethernet.c:169:79: error: Long line found
Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/boards/arm/sama5/sama5d3-xplained/src/sam_sdram.c:[14](https://github.com/apache/incubator-nuttx/actions/runs/3135514943/jobs/5091280431#step:3:15)0:78: error: Long line found
Error: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/boards/arm/sama5/sama5d3x-ek/src/sam_ethernet.c:[16](https://github.com/apache/incubator-nuttx/actions/runs/3135514943/jobs/5091280431#step:3:17)9:79: error: Long line found

@xiaoxiang781216 I will take a look on the style errors.
I will run the tool on apps/ too.
Can you help with the CI script?

BTW the warning Warning: /home/runner/work/incubator-nuttx/incubator-nuttx/nuttx/arch/arm/src/a1x/hardware/a10_memorymap.h:289:1: warning: #include outside of 'Included Files' section is a false alarm.


Chess: Start New Game

one chess please!

@MGBoulware88 Sorry, but you cannot start a new game while the old one is still in progress. Only the repo owner can do that.


Update schema builder UI to make stricter use of types

Using typescript type definitions properly rather than assigning everything to "any" should create more robust code. Warnings and errors should display if the variables are given values that don't match the interface they are given.

Merged into develop.


Interim fix to "chef fails on recent vagrant versions"

See below
https://github.com/swiftstack/vagrant-swift-all-in-one/issues/38

Thanks for this PR. I read the original comments but it's not work for clays. I'm not sure whether this fix is suitable but it works for me. So I merge this until new fix comes. Thanks!


Staking layout

Description
Adds Staking layout with related components
Paths enabled

https://deploy-preview-43--ethereum-org-fork.netlify.app/staking/solo
https://deploy-preview-43--ethereum-org-fork.netlify.app/staking/saas
https://deploy-preview-43--ethereum-org-fork.netlify.app/staking/pools
https://deploy-preview-43--ethereum-org-fork.netlify.app/staking/withdrawals

Marking as ready for review, but given it builds off the other branches, we shouldn't merge until #42 is in.

PR targeting dev again, and merge conflicts have been cleared, ready for review

Addressed all comments, should be ready for another review

@wackerow I've pushed a small fix to use the ImageProps from our custom image component instead of the chakra one.

@pettinarip This appears to just be from the long intl string ID's for the indicators... Once these are filled with sentences it shouldn't happen, though if we want to force some more constraints I'd apply it to the canonical repo.

Got it! yeah, sounds good.


Update quarto preview workflow to include render

From @ateucher:
When freeze: auto is set, if a document contains computations and has been rendered before (i.e., if there is a prior execution result stored in _freeze), quarto preview won’t re-render the document - e.g., demo.qmd has an executable code chunk in it, and the _freeze directory contains those results from prior renderings. You can render the individual file first with quarto render filename. So I think this step should be added to the lesson… The workflow would be then:

Edit demo.qmd
Run quarto render lessons/demo.qmd
Run quarto preview
Add and commit demo.qmd and _freeze content

Closing.
We are removing code from qmd for this iteration of Clinic


Read lines from long-running processes

I just made this work, not sure, how stable it is.
I hope you don't mind the rustfmt formatting :<

Error handling is probably still lacking :)

hmmm, i think there is a memory leak when the process crashes or never returns any stdout or sth


test_deletion_queue_recovery is flaky

Failures on Postgres 16

test_deletion_queue_recovery[validate-keep]: release

The count can be more after a restart than it was before pageserver.shutdown(immediate=True) because of future layers. There is a misused fail::failpoint!("control-plane-client-validate") which will need to become pausable_failpoint!() as well.

Failed 4x in last three days, may not be the same failure mode as this ticket was originally opened for.

https://github.com/neondatabase/neon/pull/7325 should help with the most common failure mode.  We can check in in ~1wk to see how prevalent other failures modes are.

No failures in past 7d


AP-5336: Remove automatic categorisation of benefits

[!WARNING]
Awaiting verification from BA/Case workers as to whether they are sure they want this, plus, if so, then comms need to go out to warn case workers prior to release

What
Remove auto categorisation of state benefit bank transactions
Link to story
The BA has approved the removal of automatic categorisation of state
benefit bank transactions from truelayer.
Note, we will be removing the ability to add disregarded benefits entirely
in the near future - Related story.
Checklist
Before you ask people to review this PR:

Tests and rubocop should be passing: bundle exec rake
Github should not be reporting conflicts; you should have recently run git rebase main.
The standards in the Git Workflow document on Confluence should be followed
There should be no unnecessary whitespace changes. These make diffs harder to read and conflicts more likely.
The PR description should say what you changed and why, with a link to the JIRA story.
You should have looked at the diff against main and ensured that nothing unexpected is included in your changes.
You should have checked that the commit messages say why the change was made.

Removal looks good - pending Caseworker decision! 😄

Caseworker approval received 🚀  - updated on ticket


Removes DNSSec and LOC RData types; fix CERT

A couple DNSSec (TLSA, DS) record types were recently added, but not
tested. Live tests started to fail on these, and since DNSSec is not
something Denominator aims to address, they should be removed.
The LOC record type is desirable, but the implementation isn't ready
to be relied on. This should be reintroduced later, possibly based on
hopper, and cross-checked with DynECT to ensure it actually works. In
the mean time, this removes the LOC record type.
Finally, the CERT record type needed some adjustments before it could
pass tests. These adjustments work on DynECT (so far).
See https://github.com/ultradns/hopper/blob/master/src/main/java/biz/neustar/hopper/record/LOCRecord.java
See https://help.dyn.com/create-loc-record-api
See #256

denominator-pull-requests #423 SUCCESS
This pull request looks good

NetflixOSS » denominator » denominator-pull-requests #48 SUCCESS
This pull request looks good

@wnagele sorry to have to do this, but these record types have absorbed quite a bit of effort. I had to roll them back. I shouldn't have merged the PR earlier without testing it.
I know there's a pretty robust version of LOC in hopper (cc @jdamick @jonbodner). Hopefully, we can get LOC back again soon.
I've serious doubts about adding DNSSEC types. The more code we put into denominator, the more easily we can swamp it. We have to choose very carefully.

denominator-pull-requests #424 SUCCESS
This pull request looks good

NetflixOSS » denominator » denominator-pull-requests #49 SUCCESS
This pull request looks good


Add yii\filters\HostControl::$fallbackHostInfo

Q
A

Is bugfix?
yes

New feature?
yes

Breaks BC?
no

Tests pass?
yes

Fixed issues
https://github.com/yiisoft/yii2/issues/13050#issuecomment-264197674

Done.

Thank you, @rob006


Problem with empty labels

What steps will reproduce the problem?

Define node with an empty label:

node = Node('PROCESS_END', shape='doublecircle', style='filled', label='', width='.15')

What is the expected output?
PROCESS_END [width=".15", style=filled, shape=doublecircle, label=""];

or better:
PROCESS_END [width=".15", style="filled", shape="doublecircle", label=""];

What do you see instead?

I get:

PROCESS_END [width=".15", style=filled, shape=doublecircle, label=];

and the the exception while generating png output:

Error: XXX.gv:17: syntax error near line 17
context: PROCESS_END [width=".15", style=filled, shape=doublecircle, >>>
label=] <<< ;

and the result picture without the requested width of .15, and with a
PROCESS_END label .

What version of the product are you using? On what operating system?
The case is with 1.0.28 release.
Please provide any additional information below.
Release 1.0.25 manages this case properly.
IMO all the attribute values should be quoted.
Original issue reported on code.google.com by<EMAIL_ADDRESS>on 10 Jan 2012 at 9:19

Present as of 3a8ee3d414fbe447af59cce753e71bf2fe050771.
As remarked above, setting a node label=None works because of this check.
Empty labels cause errors with graphviz version 2.39.20160710.1729 (20160710.1729) too.
For example:
Error: /tmp/tmpzhdQqD: syntax error in line 2 near ']'
Fixed by fd356cfe99e1b706239bab6cc71dfcd77e5c86b4.


[jsx-sort-default-props] Bug fix for one case with spread

Closes #2178
I thought an option was needed, but instead it was a bug

@ljharb Done :)


ectd hunter

We should add a hunter looking for etcd access, and for checking whether etcd data is encrypted

etcd access covered by #52


Cannot use import statement outside a module

Issue in using package in nextjs App.
"next": "13.1.6",
"zaman": "^2.0.7"

This error exists yet.
Jus crate a next app, import your package("zaman") in a component, run the project. It raises the error

Hey Thank you for reporting this problem. I need more information, such as how can I reproduce the bug, and if you can provide me with a sandbox, it would help me with the debugging process.

Hi @behzad-ahmadi
I already did this but I didn't get the error. Please create a repository and provide me with the link.

Hi Mr.Khosroshahi
i have this error on Next.js (SyntaxError: Cannot use import statement outside a module)
when one time clear import line and run app and after that again import its work but at all hard reload get the error
i was test  :
const [hydrate, setHydrate] = useState(false)
useEffect(() => {
setHydrate(true)
}, [])
{hydrate && (

<Calendar defaultValue={calendarValue} onChange={day => setCalendarValue(new Date(day))} />

)}
but dosent work

Hi dear.
same error here, seems the library doesn't support SSR yet. I also tried to load it using next/dynamic but still no results, gives me the below error:
is not assignable to type 'ComponentType<{}>'

Hey folks
For now, I don't have a plan for supporting SSR for this package. however, you can use use client in the next apps to use the package.


Update stable channel to v1.18.3+k3s1

This version of k3s addresses two CVEs -- Please reference the release notes

LGTM, waiting on a smoke test of installing 1.18.3 via the 1.18 release channel

We are good to go. Smoke tests pass with using v1.18 channel. Merging.

Endpoint has updated https://update.k3s.io/v1-release/channels now lists v1.18.3+k3s1
Shylaja testing, installing from the "v1.18" channel and it installed v1.18.3+k3s1 as expected. Dave verified as well.


[Benchmarks] Support the display of benchmarks through thresholds

Goal
Show the benchmark icon on the top-right corner based on the configured thresholds

Description
This requires users to

define the thresholds for the metrics as below

For the first step, the absolute threshold is enough
In addition to the screenshot, allow users to choose the emoji for each threshold

Please refer to Grafana's doc for more information: https://grafana.com/docs/grafana/latest/panels-visualizations/configure-thresholds/

Display the emoji at the top-right corner of a panel

Support it in the Cartesian Chart and Stats chart. For the Cartesian chart, the level depends on which threshold/bucket the avg number of metrics falls into.
Provide an option for users to decide whether to show the emoji on the panel.
When hovering on the emoji, show the full thresholds (i.e. benchmarks) in readable language.

After discussion, actual requirements are these
Variable

add Threshold aggregation

Panel Description

add Show Description checkbox
able to use panel variables in panel description
able to customize panel description's trigger icon
able to use current threshold range's icon as panel description's trigger icon

I'll close the issue as there are disputes regarding the solutions. We'll implement a private component and see if it works out.


[Hotfix] Fix ros be status

@rjayroach Opened the PR so we don't forget about this. Is this ready to merge? I've checked out this branch and it seems to be working for me


ADD: Stagenet Support

[ ] For xchain-thorchain create new stagenet init variable, which loads stagenet.thornode.ninerealms.capital as baseURL for posting tx.
[ ] All other chains do not need stagenet support

I have some changes that I'd like to push to a remote branch for this. Is there any way I can get push access to open a PR? Thanks!

Resolved by #456


Remove net451 as a cross-compile target

Will net46 bits work in VS?

Yes. Our VS bits are already net46


Make smoother transition between renderings on data change

Addresses this suggestion on the previous PR: https://github.com/girder/shapeworks-cloud/pull/248#issuecomment-1376590697

I think that is much nicer looking.


Remove authors as action holders after posting a new submission

This addresses ticket 3281, which reported that authors were not being removed as "action holders" when they submitted an updated draft. This left the impression that they still needed to do something to move the submission along.
This adds a call to update_action_holders() in a missed spot in the post_submission() method. This was missed in the original action holders implementation because the document IESG state is not actually changed, only the tags. However, the sub-state "needs ID revision" is encoded as a tag rather than a state, so a check is needed.
The change itself is pretty trivial; the test needed more work than the patch.

Committed to svn as r19122


waifu2x-caffe-cui fail to learn image model

I entered this command in waifu2x-caffe-cui.
waifu2x-caffe-cui -model_dir models/my_model -m noise -noise_level 1 -i learn/test001.jpg -o output.png
But, it is not work, and print error message 変換に失敗したファイルがあります.
All file is exists. What is problem? Is it a feature not originally supported?

waifu2x-caffe does not support training.
If your model(models/my_model) is trained with  my lua implementation, you can use it with info.json, noise1_model.prototxt and noise1_model.json properly configured.

Can you add learning to caffe, or instruction how to do it?
I'm good with photoshop and after increasing images to 7-8x assembling one good picture from mixing of 4 pictures from every red.noise mode of your program (cunet x7-x8 + every of 4 noise reduction levels)
An wanna to use this "merged" in photoshop pictures to increase other results. It's not only for me - it's for all, because if results will be better - program will have more popularity.


Custom Terminal Icon & Color

Add ability to setup custom icon or add custom set of icons to terminal.
Add ability to setup custom color to my icons to terminal.

Deduping with https://github.com/microsoft/vscode/issues/224568. @tolikhalas please use that issue moving forward.


ionic start myapp tabs

I can use angualr4, my ionic is ok, but i can not download. i am very confuse, can you tell me why and how?
here the wrong:
Creating directory .\myapp - done!
Doenloading and extracting tabs starter - failed!
rror: read ECONNRESET
at _errnoException (util.js:1022:11)
at TLSWrap.onread (net,js:615:25)

Closing as a duplicate of https://github.com/ionic-team/ionic-cli/issues/3073
Please post any comments on that issue. Thanks!


Regions will not add

Unique name (sadasdasd) already in use, not able to add new region
When adding a region it does not work.

Same bug's present in V18.  You will need to rewrite the checkUnique function handling this, notably the ADOdb Count statement is insufficient to address filter the boolean issues being presented here.

Would you know which file?

admin/regions.php

Have you made the change? If so can you share?

Yes, but I'm only here to observe bugs and basic comment.  There is a developer associated to this project.

Sorry I cannot.

Hi yeah the changes were actually put into the geocoremax commercial project over at geocoremax.com, it's all fixed.  Is not a trivial fix though, requires complete reworking on function and a handful of other calls in that class.  Just really checking in here for bugs.

lots of ghosts in this project ........

Deleting comments pointing to other projects and helpful resources is not what opensource or github's about.  This geo-community venture birthed on a development forum freely promoting itself without censure, don't play the hypocrite.

@geomodules1 ... #204 I have made the changes but I can't share them sorry, the're for a project elsewhere.

@geomodules1 ... changes have been made, but my comment got deleted for saying where the changes were being made available.  So sorry not available here.

I'm going to point out to the person deleting comments on this thread, that mentioning other projects or helpful resources is not a breach of opensource @ github or a breach of any code of conduct pertaining to this repository.  This geo-community venture exists because of starting itself on a "development" forum with free promotion.

You responded straight with a level 3 - 4 ban !  Do we need to refresh ourselves on the rules?

Temporary Ban

Community Impact: A serious violation of community standards, including sustained inappropriate behavior.
Consequence: A temporary ban from any sort of interaction or public communication with the community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.

Permanent Ban

Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
Consequence: A permanent ban from any sort of public interaction within the community.

I'm going to point out to the person deleting comments on this thread and banning members outright is pathetic.  Mentioning other projects or helpful resources is not a breach of opensource @ github or a breach of any code of conduct pertaining to this repository.  This geo-community venture "exists" from starting itself on a "development" forum with free promotion.   Maybe go check the code of conduct for procedure https://github.com/geodesicsolutions-community/geocore-community/blob/03b6a39b76821863274e4cfdf1ba8e9faf3854e4/CODE_OF_CONDUCT.md

<EMAIL_ADDRESS>email me the changes direct please


Bug: there's no function "edit_message" anywhere in the code

Hi, I was never able to make the "edit_message" function of chat work so tried to debug and I think the issue is simply that base.lua is calling self:edit_message but there is no such function anywhere in the code base, I don't even find a trace of it in the logs. What's going on?

cannot reproduce


Install as plugins in MySQLWorBench

How to install this script as a plugin for mysqlworkbench

I have no idea, sorry.


IssueID:1651: modify uln2003 input from pullup to pushpull.

[Detail]
none
[Verified Cases]
Build Pass:
Test Pass:

感谢提交 Pull Requests！
Thanks for submitting a pull request.

Security Check : c5a412677c6a1965667a330ad9ac0b9d79a265e5

auto build success,number:127

autotest fail,number:1317


SecurityException on missing permission in com.facebook.react.modules.location.LocationModule#getCurrentPosition causes app to crash

Description
I have a situation where an android user opens a page which calls navigator.geolocation.getCurrentPosition. This in turn triggers a SecurityException in the function getCurrentPostion located in com.facebook.react.modules.location.LocationModule
This exception proceeds to crash the app, instead of triggering the error callback of the navigator.geolocation.getCurrentPosition. The issue is twofold:

The app hard-crashes on this exception, without giving me a chance to gracefully recover from the failure.

For some reason the user's install is not detecting the ACCESS_FINE_LOCATION specified in the AndroidManifest.xml file. This appears to be a one off, and we're still following up with the user to see if there are any unusual considerations which might trigger such behavior.

Reproduction Steps and Sample Code
I could not reproduce the issue by disabling the location permission, or making any other user-land modifications that I could imagine.
I had to manually remove <uses-permission android:name="android.permission.ACCESS_FINE_LOCATION"/> from the app AndroidManifest.xml file, and accessed the code that attempts to retrieve the location. The resulting exception crashed my application, despite the fact that navigator.geolocation.getCurrentPosition was called with an error callback.
I could not reproduce this crash with a debugger attached.
Solution
At first glace the most obvious solution is to make the getCurrentPosition function invoke the error handler, instead of re-throwing an exception. I am not sure if there is a good reason why it isn't already doing so.
Note: The same logic applies to the startObserving function in the same class.
Additional Information

React Native version: 0.44
Platform: Android 7.0 (Original User's platform)
Development Operating System: Linux
Dev tools: Android API 25

This issue has been affecting quite a few more users than originally thought. Would it be possible to get some feedback as to the proposed solution from someone more familiar with the topic?

Quick work around is to use PermissionsAndroid. http://facebook.github.io/react-native/releases/0.44/docs/permissionsandroid.html#permissionsandroid

Ah, many thanks.
I'm going to submit a pull request with an update to the docs to reference that.

Hi there! This issue is being closed because {:search=>"repo:facebook/react-native is:open is:issue updated:<2017-05-25 -label:"Good First Task" -label:"Help Wanted" ", :message=>"it has been inactive for a while"}. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!
If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.


can't run simpleCounter example

We bought the video from O'Reilly Media and tried to run example with steps, but we got some problem.
@gwenshap

This was an old issue , but maybe this could be useful to other user.
I think in the last version of code you have to add a new param like this (this is different from what you found in the video lesson)
/run_params.sh  localhost:9092 first old sync 500 10
Note: There is the "old" value (third param) between first and sync


Unable to use OLM tool when the operator is cluster-scoped and has not the role

Error:
$ operator-sdk olm-catalog gen-csv --csv-version 0.1.0 --update-crds
INFO[0000] Generating CSV manifest version 0.1.0
Error: catalog scaffold failed: (open deploy/role.yaml: no such file or directory)

Note
Cluster-scoped ones will not have the role and instead of it will have the cluster_role.
Suggestions
The place which is looking for roles files should be able to also get:

cluster_role.yaml
cluster_role_binding.yaml

If some issue like this one occurs the process should still working for all files in the deploy dir.

Did you mean to make this issue against operator-sdk instead?
If not, I think that I misunderstand what the issue is. Could you explain it in a different way?

@ecordell make sense :-)


Added a stackshare badge

Coverage increased (+0.4%) to 79.798% when pulling 63c392c0c093c0e9aec8728bb4da2704a182950f on stack-badge into c6d022be1f276ea4f84dbc2047248f0beeda3077 on master.


Issues with modified properties when using dotnet-format

I am trying to incorporate dotnet-format (check code style) in our CI builds. However, getting this:
Unhandled exception: System.InvalidOperationException: Cannot modify an evaluated object originating in an imported file "C:\Users\geert\.nuget\packages\msbuild.sdk.extras\2.0.24\Build\Inference.targets".
   at Microsoft.Build.Shared.ErrorUtilities.ThrowInvalidOperation(String resourceName, Object[] args)
   at Microsoft.Build.Shared.ErrorUtilities.VerifyThrowInvalidOperation(Boolean condition, String resourceName, Object arg0)
   at Microsoft.Build.Evaluation.Project.RemoveProperty(ProjectProperty property)
   at Microsoft.CodeAnalysis.MSBuild.ProjectFile.GetProjectFileInfosAsync(CancellationToken cancellationToken)
   at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.Worker.DoOperationAndReportProgressAsync[TResult](ProjectLoadOperation operation, String projectPath, String targetFramework, Func`1 doFunc)
   at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.Worker.LoadProjectFileInfosAsync(String projectPath, DiagnosticReportingOptions reportingOptions, CancellationToken cancellationToken)
   at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.Worker.LoadProjectInfosFromPathAsync(String projectPath, DiagnosticReportingOptions reportingOptions, CancellationToken cancellationToken)
   at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.Worker.LoadAsync(CancellationToken cancellationToken)
   at Microsoft.CodeAnalysis.MSBuild.MSBuildProjectLoader.LoadSolutionInfoAsync(String solutionFilePath, IProgress`1 progress, CancellationToken cancellationToken)
   at Microsoft.CodeAnalysis.MSBuild.MSBuildWorkspace.OpenSolutionAsync(String solutionFilePath, IProgress`1 progress, CancellationToken cancellationToken)
   at Microsoft.CodeAnalysis.Tools.CodeFormatter.FormatWorkspaceAsync(ILogger logger, String solutionOrProjectPath, Boolean isSolution, Boolean logAllWorkspaceWarnings, Boolean saveFormattedFiles, ImmutableHashSet`1 filesToFormat, CancellationToken cancellationToken) in /_/src/CodeFormatter.cs:line 58
   at Microsoft.CodeAnalysis.Tools.Program.Run(String workspace, String verbosity, Boolean dryRun, Boolean check, String files, IConsole console) in /_/src/Program.cs:line 89
   at System.CommandLine.Invocation.CommandHandler.GetResultCodeAsync(Object value, InvocationContext context)
   at System.CommandLine.Invocation.InvocationPipeline.<>c__DisplayClass3_0.<<InvokeAsync>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseParseErrorReporting>b__16_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Builder.CommandLineBuilderExtensions.<>c__DisplayClass3_0.<<UseVersionOption>b__0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseSuggestDirective>b__7_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseDebugDirective>b__4_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseHelp>b__14_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseParseDirective>b__6_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<RegisterWithDotnetSuggest>b__17_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.CommandLine.Invocation.InvocationExtensions.<>c.<<UseExceptionHandler>b__5_0>d.MoveNext()
An error occurred when executing task 'CleanupCode'.
Error: One or more errors occurred.
        .NET Core CLI: Process returned an error (exit code 1).

Will investigate this (no action required from you) and post updates here.

Happens to this property:

This looks like a bug in the MSBuildProjectLoader, I'd open an issue on Roslyn's repo.

Yes, found it, will create a ticket there.

See https://github.com/microsoft/msbuild/issues/4376, will close this ticket since it's out of scope for msbuild sdk extras, but could be a hint for others having the same issue.


Aggregate bonded sent from cosigner from multilevel multi-sig present as Unknown

Steps:

Create multilevel multi-sig. For example:

Multilevel (2 of 2)
 	Multisig cosigner 1 (1 of 1)
 		Cosigner 1
 	Multisig cosigner 2 (1 of 1)
 		Cosigner 2

Send transaction from Cosigner 1.
Go to Cosigner 2 and open transaction details.

Result:
There is a view like for Unknown signer but this signer is from a Known cosigner.
Expected result:
We should not show an "unknown signer warning" and present flow as for a known accounts.

I think we can use this method to determine if an address is in the current multi-sig tree:
https://github.com/symbol/desktop-wallet/blob/8b236aa7191776709a42c1c7bff50ff0a27c832f/src/services/MultisigService.ts#L180

@yilmazbahadir thanks mate!

@OlegMakarenko we are using currently this method: https://discord.com/channels/@me/877119674742087720/945263935664324648
The issue is related to https://github.com/symbol/desktop-wallet/issues/1849. When we call multisig/graph for cosigner not the entire tree is returned. We can use proposed fix here https://github.com/symbol/desktop-wallet/issues/1849 (additional call) to fetch entire tree.

Fixed in https://github.com/symbol/desktop-wallet/pull/1847

Released in 1.0.11


Firestore not playing nice with file_uploader

When one of the widgets is a file_uploader and Firestore is enabled, an error is thrown at stop_tracking complaining about something something not being a string something something.
(sorry, did not save the exact error anymore, I worked around it, see below).
This error does not appear when Firestore is not enabled.
I suspect this is because the return value of a file uploader is sometimes None and sometimes an instance of class UploadedFile, which is not a string. That causes a problem at seralization time into Firestore.
Workaround: I only call start_tracking() after having instanciated my file_uploader widget, meaning I cannot track any widget that comes before it. Sad, but the only way to make it work so far.
Alternative: adding a conditional to automatically convert the value of file_uploader into a string (containing maybe just the filename, not the whole uploaded file).

That's weird, the return value of file uploader is actually never stored in Firestore. I can't test this right now because I don't have an instance of Firestore set up. Maybe this was also fixed with #3. If you see this again, please post the full error message, then I can give it a look!


Docs driveby fix for Memory::data

Reshape the safety warning around mutable aliases instead of threads.

The removed doc is true as well. Can we keep it as well?

Perhaps I'm missing something.  Isn't Memory currently !Send and !Sync?  How would another thread invalidate the underlying pointer by growing the memory?

Also, should data be &mut self since it returns a mutating slice reference?

This appears to conflict with #812 from @alexcrichton which might answer some of my questions above.

How would another thread invalidate the underlying pointer by growing the memory?

The exact problem is here https://www.reddit.com/r/rust/comments/e18jcq/how_to_read_and_write_to_memory_in_wasmtime/ , notice discussion around getrting mem.data_ptr() after the call.

Agreed that storing the slice reference returned by data, invoking a WebAssembly function, and then proceeding to use previously stored reference might result in invalidation from the memory growing during the execution of the WebAssembly.
I was failing to see, however, how data wasn't thread-safe in the current implementation limitations.  We can't send instances between threads (#793), so how could another thread grow the memory?
At any rate, I think this PR might now be superseded by #812.

Yes to clarify there's a large number of reasons that this is an unsafe API, and it doesn't require threads for this to be unsafe. Also sorry yeah I didn't look into this before writing up https://github.com/bytecodealliance/wasmtime/pull/812 which expands on the unsafety reasons here as well.
To answer your questions though @peterhuene:

Perhaps I'm missing something.  Isn't Memory currently !Send and !Sync?

Correct!

How would another thread invalidate the underlying pointer by growing the memory?

While not true that other threads can update this, you could still have something like:
let ptr = memory.data();
instance.call_export("foo"); // invalidates `ptr` by calling `memory.grow`
println!("{:?}", ptr); // reads stale data

(basically this is just a "bland use-after-free")

Also, should data be &mut self since it returns a mutating slice reference?

Due to the aliasing of so many internals here that actually doesn't end up buying us anything. I recently added internal reference counting so you could actually do:
let mut memory = ...;
let mut memory2 = memory.clone();

assert_eq!(memory.data(), memory2.data()); // aliasing mutable pointers!

Even if we didn't have reference counting you still have the above problem:
let mut view = memory.data();
instance.call_export("foo"); // technically referred to by instance, so `view` is still aliased
println!("{:?}", view); // use-after-free

The only way Rust's type system would help here is if we would have something like Instance using no reference counting, Memory using no reference counting, and a fn (&mut Instance) -> &mut Memory method. That way we can guarantee that when you're looking at &mut Memory no one else in the world can possibly be looking at it, so you can safely get &mut.
Even if we did that, however, then you couldn't share memories across threads which is something we'd like to support eventually!
Overall I think we'll need to stick to "all memory access are unsafe" and we'll need to build up safe abstractions (like interface types) which encapsulate the unsafety. Otherwise we can be very very careful to document the various unsafeties.

@pepyakin thanks for putting up this PR!  Given @alexcrichton's incoming changes to the API and subsequent updates to the comments to this method, I'm closing this as superseded by #812.
Please comment on that PR if the updated doc comments are insufficient to convey the changes made in this PR.
Thanks!

@alexcrichton agreed that there is a general aliasing problem, which is why I thought the change here was a more "general purpose" warning than the previous message.
I appreciate the additional detail you've added in #812!


x/pkgsite: package removal request for github.com/terenceodonoghue/golang

What is the path of the package that you would like to have removed?
github.com/terenceodonoghue/golang
Are you the owner of this package?
Yes
What is the reason that you could not retract this package instead?
I have published retractions and made the repo private, would like all packages + docs from terenceodonoghue/golang removed (including for latest version) from pkg.go.dev - packages were published accidentally due to my misunderstandings while learning how Go modules work.
Thank you! 🙏

Related Issues and Documentation

x/pkgsite #48560 (closed)
x/pkgsite: package removal request for [type path here] #52206 (closed)
x/pkgsite: package removal request for [type path here] #52570 (closed)
x/pkgsite: package removal request for [type path here] #50341 (closed)
x/pkgsite: package removal request for [type path here] #50666 (closed)
x/pkgsite: package removal request for [type path here] #53147 (closed)
x/pkgsite: package removal request for [type path here] #52429 (closed)
x/pkgsite: package removal request for [type path here] #58741 (closed)
x/pkgsite: package removal request for [type path here] #54154 (closed)
x/pkgsite: package removal request for [type path here] #54155 (closed)

(Emoji vote if this was helpful or unhelpful; more detailed feedback welcome in this discussion.)

Done. Please allow a few hours to propagate.


Changing entity name not working

Followup of #5

I think it was because of me changing the entity names from mac adres to something human friendly

Can confirm - if you change the MAC to a human-readable value then it stops collecting data.
Re-adding means removing the Homewhiz integration and associated devices, restarting Home Assistant, and then adding back HomeWhiz.
For some reason if I try this without restarting Home Assistant then the HomeWhiz installer just offers me a blank dialogue box that I can only cancel out of.

this isue should get fixed or at least add to the description, so people wont change to human-readable value and wont get disappointed.

This is still behaving odd. When changing the device name, all entities are created again (with "_2" added to the entity name) but starting with the original device name and the old entities are shown as not provided anymore.

Can you check if the issue still persiste again after the recent changes?

I checked and it is working now!


laravel 5.2 AD account can't login

Laravel Version: 5.2
Adldap2-Laravel Version: 3.0
PHP Version: 5.6.21

Description:
1.my project use AD users to login ,so i user bundle adldap2;
2.i follow the steps from quick_start.md in docs;
3.in my code the account from adldap.config admin_username ,admin_password can login but the other account can't login,please help me ,thanks;
Steps To Reproduce:

Hi @syyzw1985, unfortunately I need much more detail to assist you.

Are you using ActiveDirectory or OpenLDAP?
What happens when you try to login? Just a validation error?
Have you performed any troubleshooting steps at all besides just trying to login?

Closing due to inactivity. Will re-open when a response is given.


Something went wrong. Try again in a few minutes.

Encountering two errors in Teams app:

Something went wrong. Try again in a few minutes.
Clicking 'Take a tour' or 'Review introductions' button errors out with "Unable to reach app. Please try again."

Hi @TLS1-2,
Thank you for posting your query, can you please check your application insights and see the exceptions that logged and share it for us to troubleshoot further? It seems the bot is not able to communicate with the app service.

EXCEPTION #1 Microsoft.IdentityModel.Tokens.SecurityTokenSignatureKeyNotFoundException
Message: IDX10501: Signature validation failed. Unable to match key: kid: '[PII is hidden. For more details, see https://aka.ms/IdentityModel/PII.]'. Exceptions caught: '[PII is hidden
Exception Type: Microsoft.IdentityModel.Tokens.SecurityTokenSignatureKeyNotFoundException |
Failed Method: System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateSignature
Formatted Message: Failed to validate the token.
EXCEPTION #2 Microsoft.Graph.ServiceException
Message: Code: Request_ResourceNotFound Message: Resource 'manager' does not exist or one of its queried reference-property objects are not present.
Exception Type: Microsoft.Graph.ServiceException
Formatted Message: Failed to get manager for user: 0e84df5b-cd15-4ade-84f8-b11b7795c8cd. Status Code: NotFound Exception: Code: Request_ResourceNotFound
Message: Resource 'manager' does not exist or one of its queried reference-property objects are not present.
EXCEPTION #3 Microsoft.Rest.HttpOperationException
Message: Operation returned an invalid status code 'BadRequest'
Exception type: Microsoft.Rest.HttpOperationException
Formatted Message: Exception caught : Operation returned an invalid status code 'BadRequest'

Thank you @TLS1-2 for sharing the errors, I'll check the reason for the first exception and get back to you, however the second exception status that the resource doesn't exist, did the deployment succeed for you.

Hi @TLS1-2,
Please share your availability and email id so that we can connect and troubleshoot over the call.

Hi @TLS1-2, do you've any updates on the above ask.

Closing the issue due to inactivity, please create new issue if it still happens.


Change transportation units to MWh

were the values in the data divided by 1000?

were the values in the data divided by 1000?

The value of kWh in this file caused dsgrid to leave the transportation values in kWh rather than convert them to MWh, which is what happens for all other end uses.

thanks that makes perfect sense
so, kWh in datasets/dimensions/enduses.csv and MWh in projects/dimensions/enduses.csv

thanks that makes perfect sense
so, kWh in datasets/dimensions/enduses.csv and MWh in projects/dimensions/enduses.csv

More specifically, the dataset can put its preferred units. All project end uses should use the same unit.


[BUG] arc assay add fails in a large arc

Describe the bug
arc assay add fails in https://git.nfdi4plants.org/kMutagene/arabidopsis_thaliana_transcriptome
creating the assay works, but the register step fails with
ERROR: System.NullReferenceException: Object reference not set to an instance of an object.
   at ISADotNet.XLSX.StudyFile.Study.studyMetaData@65.Invoke(SheetData sheet)
   at ISADotNet.XLSX.StudyFile.Study.fromSpreadsheet(SpreadsheetDocument doc)
   at ISADotNet.XLSX.StudyFile.Study.fromFile(String path)
   at ArcCommander.APIs.AssayAPI.register(ArcConfiguration arcConfiguration, FSharpMap`2 assayArgs)
   at ArcCommander.Program.handleAssaySubCommands@180-1.Invoke(ArcConfiguration arcConfiguration, FSharpMap`2 assayArgs)
   at ArcCommander.Program.processCommand[a,T](ArcConfiguration arcConfiguration, FSharpFunc`2 commandF, ParseResults`1 r)
   at ArcCommander.Program.handleAssaySubCommands(ArcConfiguration arcConfiguration, AssayCommand assayVerb)
   at ArcCommander.Program.handleCommand(ArcConfiguration arcConfiguration, ArcCommand command)
   at ArcCommander.Program.main(String[] argv) Object reference not set to an instance of an object.

To Reproduce

Download the above linked arc
arc add register -s DRP000209 -a Data_aggregation

Expected behavior
assay gets created and registered in target study
OS and framework information (please complete the following information):

OS: Ubuntu
OS Version: 20.04.4 LTS

Additional context
Studies have been created programmatically using ISA.DotNet, and registering them with arc study register worked like a charm.

@HLWeil The bug most likely occurs here: https://github.com/nfdi4plants/ISADotNet/blob/f81431131c9c27ca56222bbfc94a63c6ffb4c73b/src/ISADotNet.XLSX/StudyFile/Study.fs#L72
Trying to investigate this further...

Okay, this bug does not appear anymore in ISADotNet.Xlsx v0.6.0, but the ArcCommander currently uses the buggy version v0.4.0-preview.5. Unfortunately, the new, bug-free version changed some functions so that backward compatibility does not exist anymore. 🤡
Meaning, I will need to figure out how to the now occurring new errors.
This will be part of the upcoming bugfix regarding the bugs around the change in studies due to new ARC-specification version.

Used this as a testcase for checking if IO speed is enough for these huge metadata files. Study parsing speed is totally fine, but parsing the Investigation file takes 15 minutes on my machine.

FsSpreadsheet was the main culprit: https://github.com/fslaborg/FsSpreadsheet/pull/81


Mangling: support mangling of varargs even if it's not the last argument.

Example:
func a(arr: Int..., n: String)
fixes SR-1076

@swift-ci Please smoke test and merge


Skeleton Poser drifts out of alignment

The Skeleton Poser when set up with an object doesn't seem to respect the offset to that object, either changing after a few seconds of run time, or being wrong from the start.
You can see an example of the issue, wherein it changes after a few seconds of run-time here (Please ignore the white hands, that is as intended):
https://media.giphy.com/media/5pYoYOIeyRnQeljuF9/giphy.gif
The Poser preview looks like this:

Then at runtime, when grabbed with the user's actual hand, it looks like this:

The settings on the screw are as follows:

I have tried to following to attempt to isolate the problem;

Trying a different object (Bog standard 3D Cube)
Trying default values for all components
Trying any of the pre-built objects in the provided sample scene
Trying an empty new scene with only the provided Player prefab and a 3D cube with the above settings.
Trying a new project with a freshly imported SteamVR and trying out the 'Happy' ball

All of which exhibit the issue, I can assume that the issue is something to do with the hand tracking or pose behaviour class, but I'm unable to find out what triggers that offset to occur.
Unity Version: 2018.3.0f2
SteamVR Plugin Version: v2.2.0
SteamVR Version: 1.2.7
EDIT: Updating to:
Unity Version: 2018.3.3f1
SteamVR Version: 1.2.10
Still shows the same issues in the following test project (most visible when picking up the Throwable Cubes, you can see that the Index Finger does not align with the edge of the Cube as it does in the Poser):
https://www.dropbox.com/s/t0p09hp8ty7rea7/SVRTest.zip?dl=0

Hi, I got the same problem here, but in my case it's more notorious, when the interaction occurs, the object has a big offset, positioning over the hand pose, I follow the tutorial from youtube, but no resolve my problem, any chance to know what produce this kind of "bug"?, cheers.

How to solve this problem...
@PhantomBadger, In fact it's just related on which transforms your have to move/rotate, this are:

The main hand root (vr_glove...(clone)).
The fingers only.

As I can see, if you move the wrist and the fingers without re-positioning the main hand root, just the fingers are posed as you did it, the wrist ignores the new position.

@3DMagicVR are you sure that's actually the solution? I am having the same problem and even after multiple tests and changes that solution has not solved the problem. Could you please elaborate? Or @PhantomBadger have you found another solution?

I am currently on version v2.3.2 (sdk 1.4.18)  and facing similar problems.
I created a blank Unity project (2019.1.10f1) imported the package and ran the "Interactions_Example" scene.
When grabbing the grande or one of the balls on the "Interesting Interactables" tables using a regular Vive Controller you can see that there is an offset on the object.
When swiping around with the thump on the touch pad of the controller the whole hand begins to move around in a strange way rather than just the thump itself.
This also happens on poses where all fingers are set to static, where nothing is supposed to happen at all.

We were struggling with this issue as well and finally found fix. In the pose assets that are generated there are checkboxes for "Ignore Root Pose Data" and "Ignore Wrist Pose Data" under each hand. Uncheck these boxes and the root/wrist pose of your cloned hand model will be respected.

We were struggling with this issue as well and finally found fix. In the pose assets that are generated there are checkboxes for "Ignore Root Pose Data" and "Ignore Wrist Pose Data" under each hand. Uncheck these boxes and the root/wrist pose of your cloned hand model will be respected.

Thanks, I will check it out when I have a chance, actually I don't have a HTC Vive to see that,, greetings.

We've had difficulty replicating this issue. If the Ignore root/wrist workaround fixes the issue let us know that may give us a better clue as to the underlying issue.

Closing pending feedback.

I've had the same issue using

Unity 2019.3.3f1
SteamVR 2.5.0 (sdk 1.8.19)
Unchecking Ignore root/wrist as suggested by @kimberlysiva fixed it for me.

I've also had the same issue, with a temporary fix using @kimberlysiva 's method.


Unc0ver Crashing After Attempted Jailbreak

Describe the bug
After restarting, my iPhone 11 on 13.5 is not able to jailbreak. The app attempts to jailbreak, and then crashes without completing it. The app continues to crash unless rebooted
To Reproduce
Steps to reproduce the behavior:

Open Unc0ver App
Click on 'Jailbreak'
Wait
It'll get to about the 28th step and then just crash

Screenshots
Before restoring Rootfs: https://youtu.be/bqbA07wN7LM
After restoring Rootfs: https://youtu.be/6WUY6f-MEc8
Device (please complete the following information):

iOS Version: 13.5
iOS Device: iPhone 11
unc0ver Version: Tested on 5.0.1, 5.2.0, 5.2.1

Place an "x" between the brackets if true:

[ ] this is a bug others will be able to reproduce
[x] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[x] this issue is present after a rootfs restore
[x] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.
Present in videos linked

go to settings, general, reset all settings.  When you go to jailbreak, restore root FS first.  then reboot and try again.

You might also want to use a different cord when installing unc0ver.

go to settings, general, reset all settings. When you go to jailbreak, restore root FS first. then reboot and try again.

Restoring settings didn't work unfortunately

You might also want to use a different cord when installing unc0ver.

What do you mean a cord? I went to the website and used the "Open in AltStore" option and for the older releases, I had them in my Files

If you look closely in that video at the 25 second mark.  you can see that you have an unauthenticated package "substituted"   ..   Also you left Gump installed before you did all of this.  That might be whats causing all this.
You need a high level programmer to help you with this.

If you look closely in that video at the 25 second mark. you can see that you have an unauthenticated package "substituted" .. Also you left Gump installed before you did all of this. That might be whats causing all this.
You need a high level programmer to help you with this.

I see, thank you so much for this information. Theoretically, a factory reset should fix this right?

totally. But you will lose your jailbreak.  I think if you just run it normally (unjailbroken) until more information can be found about this.  I'm very confident it can easily be fixed.

just curious.  have you tried jailbreaking with "load tweaks" unchecked?

just curious. have you tried jailbreaking with "load tweaks" unchecked?

Just tried it now and the same thing happened

You tried redownloading unc0ver yet?

You tried redownloading unc0ver yet?

yeah, I've tried redownloading as well as using older versions but with no luck

totally. But you will lose your jailbreak. I think if you just run it normally (unjailbroken) until more information can be found about this. I'm very confident it can easily be fixed.

Update on this. I tried Factory Resetting, and even that didn't work

When you say factory reset,  did you just click reset everything?  or did you actually do a full upgrade with restore?

When you say factory reset,  did you just click reset everything?  or did you actually do a full upgrade with restore?

I actually ended up fixing the issue. I did a factory reset and it continued to do it, but after continuously attempting to jailbreak it wouldn't work. For some reason, it worked almost instantly with the wifi off and Siri off as well

@VMT-Batman thanks, the trick worked for me as well