No repositories from Gogs

I've setup Drone using the Gogs driver and logins work perfectly fine. However, none of my repositories are shown in Drone, not even in the search box as suggested in another issue. I just get "No Matches Found".
Gogs' API shows both repositories on Gogs.
Drone's API shows nothing but "[]".
What am I missing?

there is a known issue in Drone where we cache the repository list for 24 hours which means newly created repositories aren't displayed immediately. You can directly navigate to the page (ie mydrone.com/foo/bar or to restart Drone to flush the cache.
we have an open issue for this and are planning a fix to refresh the cache manually, which will land in the 0.4.1 release.

Thank you for the quick response. Navigating direct worked perfectly.


let re-admit button show up when it should

little typo. r? @keybase/react-hackers

oh!

We should get this in the release


Use gravatar cache

If gravatar.com isn't available or doesn't perform well, a ghost blog stumbles. At least until the 2000 ms timeout is reached.
Wouldn't it be good to cache the gravatar images in a local cache folder and check for the lastModified before sending out a new request to gravatar.com? It could save from a lot of external requests and speed up the blog.

It should be async as far as I know, anything beyond that is up to Gravatar to optimise - or for blog owners to upload a photo to Ghost rather than relying on Gravatar

Sry, you're right. Gravatar loads async and won't slow down the blog.
Thx for clearing up the issue!


New lint failures from the proposed 0.3.0 code

I just ran my project through the new linter based off the current state of the master branch before the proposed bump to 0.3.0 (as of 4cb6db8187c30ee1be5b4f04c6c1227ec27c427a) and I'm getting a few new lint failures that I wasn't getting with 0.2.0.
Specifically the following selectors are all producing new failures where they weren't before,
.AuthCodeControl-input[type=number]
.Button[disabled]
.CheckControl-input[disabled] ~ .CheckControl-label
.TextControl-inner--password .TextControl-input[type="password"]

Are these selectors actually non-compliant and the new linting code properly picking them up, or is something going awry?
I'm just calling the linter with no additional options, like so,
postcss()
  .use(require('postcss-bem-linter')())
  .process(css);

The errors make sense to me, because those chained attribute selectors are not accounted for in the SUIT regular expression.
I believe that before the recent changes the regular expressions were not checking that the whole sequence matched the whole regexp. Instead, I think they were looking to see if the regexp had a match anywhere within the selector sequence. I switched it to the current more strict form (whole match) because otherwise you could actually attach anything arbitrarily after or before a matching string.
(I hope that statement is accurate --- I'd have to take a look at the old code to verify. Please correct me if I'm wrong @necolas.)
Anyway, @necolas do you want the SUIT componentSelector pattern to allow for attribute selectors? If so, you or I could update the regexp.

Also getting new errors on these two selectors as well,
.ActivityLog-detailQuote ::before
.ListItem-media--double *:nth-child(2)

Again, I think the regexps are performing as expected. Those will probably work in 'loose mode', though. I think it's up to @necolas whether to allow that kind of stuff with the SUIT pattern.

we should support the chained attributes
this should be an error though, because it could impact every element in the sub-tree
.ActivityLog-detailQuote ::before {}
.ListItem-media--double *:nth-child(2) {}

#30 is there for adding chained attributes to SUIT pattern, which will solve this problem.

Fixed by #35

:+1: Thanks so much guys, looking forward to the new release.


Problems encountered when converting tensorflow models to rknn models

The following is my code, and the issue occurred in the loading model section：
from rknn.api import RKNN
if name == 'main':
# 确定目标设备target
target = 'rv1126'
# 创建RKNN对象
rknn = RKNN()

# 配置RKNN模型
print('--> config model')
rknn.config(mean_values=[[127.5, 127.5, 127.5]],
            std_values=[[127.5, 127.5, 127.5]],
            reorder_channel='0 1 2',
            target_platform=[target])
print('done')

# 加载TF模型
print('--> loading model')
ret = rknn.load_tensorflow(tf_pb='/home/alientek/ssd_inception_v2_coco_2018_01_28/frozen_inference_graph.pb',
                           inputs=['FeatureExtractor/MobilenetV1/MobilenetV1/Conv2d_0/BatchNorm/batchnorm/mul_1'],
                           outputs=['concat', 'concat_1'],
                           input_size_list=[[300, 300, 3]])
if ret != 0:
    print('load model failed!')
    rknn.release()
    exit(ret)
print('done')

When loading the model, an error will be reported as follows：
W:tensorflow:From /home/alientek/anaconda3/envs/py3.8-rknn-1.7.5/lib/python3.8/site-packages/rknn/api/rknn.py:107: extract_sub_graph (from tensorflow.python.framework.graph_util_impl) is deprecated and will be removed in a future version.
Instructions for updating:
Use tf.compat.v1.graph_util.extract_sub_graph
E Catch exception when loading tensorflow model: /home/alientek/ssd_inception_v2_coco_2018_01_28/frozen_inference_graph.pb!
E Traceback (most recent call last):
E   File "rknn/api/rknn_base.py", line 253, in rknn.api.rknn_base.RKNNBase.load_tensorflow
E   File "rknn/base/RKNNlib/RK_nn.py", line 52, in rknn.base.RKNNlib.RK_nn.RKnn.load_tensorflow
E   File "rknn/base/RKNNlib/app/importer/import_tensorflow.py", line 110, in rknn.base.RKNNlib.app.importer.import_tensorflow.Importensorflow.run
E   File "rknn/base/RKNNlib/converter/convert_tf.py", line 103, in rknn.base.RKNNlib.converter.convert_tf.convert_tf.init
E   File "rknn/base/RKNNlib/converter/tensorflowloader.py", line 45, in rknn.base.RKNNlib.converter.tensorflowloader.TF_Graph_Preprocess.init
E AttributeError: 'NoneType' object has no attribute 'op'
E Please feedback the detailed log file <log_feedback_to_the_rknn_toolkit_dev_team.log> to the RKNN Toolkit development team.
E You can also check github issues: https://github.com/rockchip-linux/rknn-toolkit/issues
load model failed!
I don't know how to solve it! >_< Please help me! Thanks for everyone!

Got same problem, did you solve it?

It seems that the problem is at
ret = rknn.load_tensorflow(tf_pb='/home/alientek/ssd_inception_v2_coco_2018_01_28/frozen_inference_graph.pb',                            inputs=['FeatureExtractor/MobilenetV1/MobilenetV1/Conv2d_0/BatchNorm/batchnorm/mul_1'],                            outputs=['concat', 'concat_1'],                            input_size_list=[[300, 300, 3]]), the parameter "input" doesn't match model's input node.
I changed it to inputs=['FeatureExtractor/MobilenetV1/MobilenetV1/Conv2d_0/Conv2D'] and solved the problem for me.


Syntax error on valid code.

> mocha --require babel-register --require test/unit/setup.js "test/**/*.spec.js"

---/node_modules/babel-core/lib/transformation/file/index.js:558
      throw err;
      ^

SyntaxError: ---/src/views/Accommodation.vue: Unexpected token, expected , (14:85)
  12 |

  13 |                Total Cost of Accommodation
> 14 |                {{ formatPrice(accommodationSpend.totalCostOfAccommodation) }}
     |                                                                                ^
  15 |

  16 |

  17 |                Number of Room Nights
    at Parser.pp$5.raise (---/node_modules/babylon/lib/index.js:4454:13)

For some reason it doesn't believe I can have a '.' in an argument?

It is valid vue template syntax but not valid jsx.

Yeah, I was mislead by your description on npms.io as "Babel preset for all Vue plugins."


Ability to edit demands

Right now, you can't go back and edit a demand. The user who originally created (and thus owns) a demand should be able to edit the demand, likely from the show page.
For MVP just the owner of the demand will suffice. In the future, we may want to have permissions set on demands so that teams/groups of people can edit, or the entire public may.

Addressed in #31


translate define interdependent environment variables into Chinese

translate define interdependent environment variables into Chinese

/approve

@fancc This one needs a rebase.

@fancc

This page has been localized in another PR.
/close


Faild to resovled

when I gradlew build the BasicSample, i got error
logs:
A problem occurred configuring project ':app'.

Could not resolve all dependencies for configuration ':app:_debugApkCopy'.
Could not resolve android.arch.persistence.room:support-db:1.0.0-alpha1.
Required by:
project :app > android.arch.persistence.room:runtime:1.0.0-alpha1
project :app > android.arch.persistence.room:runtime:1.0.0-alpha1 > android.arch.persistence.room:support-db-impl:1.0.0-alpha1
Could not resolve android.arch.persistence.room:support-db:1.0.0-alpha1.
Could not get resource 'https://dl.google.com/dl/android/maven2/android/arch/persistence/room/support-db/1.0.0-alpha1/support-db-1.0.0-alpha1.pom'.
Could not HEAD 'https://dl.google.com/dl/android/maven2/android/arch/persistence/room/support-db/1.0.0-alpha1/support-db-1.0.0-alpha1.pom'.
dl.google.com`

i don't think this is network error. because i has set proxy. who knows why

Dup of #25 ?

perhaps not same @JoseAlcerreca .
that error occur when i follow the solution that they said.

经发现https://dl.google.com/dl/android/maven2/android/arch/persistence/room/support-db/1.0.0-alpha1/support-db-1.0.0-alpha1.pom下载后的目录.gradle\caches\modules-2\files-2.1\android.arch.persistence.room\support-db\1.0.0-alpha1\1db084aa6b150b4b7059ec92cba2f9ca7011bfa6的support-db-1.0.0-alpha1.pom文件竟然是乱码，导致无法解析，以及无法下载对应的jar和aar.所以直接通过浏览器下载后，覆盖这个文件即解决问题了。
另外工程需要android studio 3.0才能运行


Ability to specify stack arguments layout

What is the feature you'd like to have?
To be able to specify layout of function arguments on stack, using function signature. Currently it's only possible with adding custom calling convention, but would be handy to make it same way as it can be done for registers.
Additional Information:
For example in IDA you can use syntax:
@<^offset:size>

Yes additionally the UI needs to be updated so it can display these types of parameters as well.

Closing in favor of this: https://github.com/Vector35/binaryninja-api/issues/3340


Slider doesn't work properly on mobile

The ui looks sexy, for some reason the transparency looks better now BUT there's a problem:
The slide won't slide correctly on mobile, i struggle to move the slider on mobile, it's a problem i've had with fluent before (i solved by modifying the slider circle size, not recommended, it may break the slider border limit, its a temporary workaround)

I'll check that out

Do u think making the display text a text box fix the issue?


(iOS) crash when trying to save image from Share

When I try to save the shared screenshot, the iOS crash.
Any ideas?

You haven't set the privacy key for photo library in the plist
On Tue, 28 Feb 2017 at 6:51 am, DenilsonUFV<EMAIL_ADDRESS>wrote:

When I try to save the shared screenshot, the iOS crash.
Any ideas?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/ChrisMaire/unity-native-sharing/issues/23, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAytHNqk5TsZUrnL9ukS_L4Iw2s4MX04ks5rgyQCgaJpZM4MNhcP
.

@danoli3 is right!
you have to add a NSPhotoLibraryAddUsageDescription tag to your Plist
<key>NSPhotoLibraryAddUsageDescription</key>
<string>Can I use your Camera Roll please? :)</string>

and then works!

To prevent this from happening again if you rebuild your Xcode project completely, add this script to a folder named Editor which will allow the script to run. It will be called automatically by the build system.
using UnityEngine;
using UnityEditor;
using UnityEditor.Callbacks;
using System.Collections;
using UnityEditor.iOS.Xcode;
using System.IO;

public class PostBuildScripts {

[PostProcessBuild]
    public static void AddPhotoLibraryUsageKey(BuildTarget buildTarget, string pathToBuiltProject) {

        if (buildTarget == BuildTarget.iOS) {

            // Get plist
            string plistPath = pathToBuiltProject + "/Info.plist";
            PlistDocument plist = new PlistDocument();
            plist.ReadFromString(File.ReadAllText(plistPath));

            // Get root
            PlistElementDict rootDict = plist.root;

            // Ensure that photo usage description is always added
            var buildKey = "NSPhotoLibraryUsageDescription";
            rootDict.SetString(buildKey, "Photo library access needed to save screenshots");

            // Write to file
            File.WriteAllText(plistPath, plist.WriteToString());
        }
    }
}

This could probably be integrated into the plugin itself.

This key is for ios 10+
How to fix this problem on IOS 9?
(for sure i added this key to plist but application still crashing when i click "save image".

@BaalEvan it is only required for iOS 10+

Important: To protect user privacy, an iOS app linked on or after iOS 10.0, and that accesses the user’s photo library, must statically declare the intent to do so. Include the NSPhotoLibraryUsageDescription key in your app’s Info.plist file and provide a purpose string for this key. If your app attempts to access the user’s photo library without a corresponding purpose string, your app exits.

Post your stack trace/console log so we can see what is the problem.

It works on first time but when i click share button once again there is "Lost Connection" error and the app closes. There is no more output.

@BaalEvan looks like you're game is being killed because of a memory warning. Not directly related to this plugin.

Thanks, i will check this, but how do you know that the problem is related to memory?
There is no warning on output except information about unloading unused assets on scene load.
(i'm not experienced with iOS and this could be valuable information ;) )

You can see in the console that it is "unloading x unused Assets to reduce memory usage.". On the last attempt it failed to unload any assets and was killed by the system. Since the app is killed the debugger loses the connection. This is most likely triggered when this plugin captures a screenshot and increases memory usage. Use Unity's tools to profile memory usage.
I don't want to further derail comments on this issue.

@MrNickBarker, Thank you for the C# code. I added your script to my Editor folder and I still got a crash. I am running on ios 11.2.

@artfail can you post your crash log?

Is there someway to call the callback method if image is saved or not on iphone?

Hi, I've taken over this repository, due to the age of the issue I'll be closing this issue
I've rewritten most of the plugin to be easier to use, and there is a high possibility that your issue has been fixed
Please download and see if your issue is still present. If it is please create a new issue and I'll get to it as soon as I can


Redirect bug

https://openeo.eodc.eu/credentials/oidc redirects to https://openeo.eodc.eu/bouncer.eodc.eu/realms/EODC/.well-known/openid-configuration instead of https://bouncer.eodc.eu/auth/realms/EODC/.well-known/openid-configuration.
Tried to reproduce locally but I couldn't manage to do it.

Solved. Problem was in configuration files.


Fix new RDS instance tagging

Without these changes, RDS instance creation breaks on tagging the new
instance. This saves the response from RDS instance creation so the generated
ARN can be used to tag the RDS instance. It removes use of tags_for_resource
since that expects the tags property to be named tags instead of rds_tags.

Rebased for tests.

Closing in favor of #442 .


Extension - Remove the logic that differentiates between Native tokens and Local tokens in case show sub-logo

Describe the task
Remove the logic that differentiates between Native tokens and Local tokens
Actual : Don't show sub-logo on Native token

Expect : Add sub-logo on Native token

Version test : http://file.cdmteck.com/s/xQicESpii8txNi8

[ ] Re-check style sub-logo

Version test: http://file.cdmteck.com/s/xQicESpii8txNi8

[ ] Do not show sub-logo on Select token on search token screen

Version test : http://<IP_ADDRESS>:8900/s/Z9LGs87rGYwoPCK
Validation passed in case :

Show sub-logo on Select token on search token screen


General housekeeping

Sweep contributed code for:

[ ] Correctly capitalized titles (Sentence case)
[ ] Strings marked for translation
[ ] Translator notes
[ ] Default output for null variables (example: Profile or Add Object: Profile, not : Profile for new objects, or objects without names)
[ ] Remove/replace code placeholders
[ ] Remove BS special-purpose layout selectors, e.g. col-sm-12; also make responsive!

@axoplasm I think issue #1343 may be a result of these changes, based on looking at the code. But I may be wrong - I'm gonna continue poking around the pages affected

@axoplasm I've been through pretty much the entire site while executing the test cases for PA - I did not see anything stand out other than what we've already reported as styling issues and other things that may have been a cause of changes in this ticket. I think this is probably safe to move to deploy ready? Unless there is anything you can point out I can directly focus on

Let's move this one on


More flexible S3 configuration

This pull request changes the way the S3 client is configured.
The user can now set any option for the S3 client they want. The code is working great with the Ceph RGW S3 implementation and should also work with minio (https://github.com/jdxcode/npm-register/issues/59), though I have not tested this.

This dependency was already required by something and caused failing docker image builds.
Am 17. Juli 2018 17:43:11 MESZ schrieb Dan Gautsch<EMAIL_ADDRESS>
dgautsch commented on this pull request.

@@ -19,6 +19,7 @@
"klaw": "^2.1.1",
"lodash": "^4.17.5",
"metric-log": "^1.0.1",

"node-pre-gyp": "^0.10.3",

What is node-pre-gyp being used for? Or is this a semver upgrade?
--
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
https://github.com/jdxcode/npm-register/pull/116#pullrequestreview-137893727

--
Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.

@dgautsch seems to be it's good to go :)?


Running multiple ios builds in parallel using gym fails

Issue Description
As part of our CI pipelines apps with slightly different configuration are built in parallel on the same machine. Sometimes they are all built correctly, but often we get the following error for some of them:

The file “App_2023-09-15_12-40-24.982.xcdistributionlogs” couldn’t be saved in the folder “T” because a file with the same name already exists.

As it turns out all the builds try to write the same .xcdistributionlogs file.
How is the path of that determined? Can a truly temporary directory used instead, e.g. the export path? Note that xcdistributionlogs is placed in the parent directory of the export path which is not unique anymore.
Tried to configure all possible paths to a dedicated value for each build that were documented for build_ios_app, i.e.:

output_directory
buildlog_path
build_path
derived_data_path
archive_path

But apparently that does not affect the passed parameters of xcodebuild itself.
Complete output when running fastlane, including the stack trace and command used
xcodebuild -exportArchive -exportOptionsPlist /var/folders/_8/mxv5z_855rd3t39vn2r_2vf40000gp/T/gym_config20230915-5701-lj94lt.plist -archivePath build/ios/archive/.xcarchive.xcarchive -exportPath /var/folders/_8/mxv5z_855rd3t39vn2r_2vf40000gp/T/gym_output20230915-5701-5z62lf
xcodebuild[9712:1186757] [MT] IDEDistribution: -[IDEDistributionLogging _createLoggingBundleAtPath:]: Error creating logging bundle at path "/var/folders/_8/mxv5z_855rd3t39vn2r_2vf40000gp/T/App_2023-09-15_12-40-24.982.xcdistributionlogs". Error = Error Domain=NSCocoaErrorDomain Code=516 "The file “App_2023-09-15_12-40-24.982.xcdistributionlogs” couldn’t be saved in the folder “T” because a file with the same name already exists." UserInfo={NSFilePath=/var/folders/_8/mxv5z_855rd3t39vn2r_2vf40000gp/T/App_2023-09-15_12-40-24.982.xcdistributionlogs, NSUnderlyingError=0x600002e77420 {Error Domain=NSPOSIXErrorDomain Code=17 "File exists"}}
xcodebuild[9712:1186757] *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSURL initFileURLWithPath:]: nil string parameter'

I am not using Fastlane, but using xcode 14.3 and came across this exact same error, in a similar situation of multiple builds going.
Given that the log filename contains the millisecond and app name, it should be unlikely that the files overlap. However it does happen when 2 builds are triggered simultaneously. Both of them use the same distribution filename, despite being 2 separate processes, so even though the millisecond is included in the filename, and the filename is a temporary one, it still collides.
My best guess is that it's a bug in Xcode 14.3, not Fastlane. And I agree, it does not seem like there is a way to change that temporary path. In other words: Try upgrading to Xcode 15 (at the moment it's an RC) and see if it fixes it.

A lot of things you have shared in this post.

As far as I know "parallelism" is not really supported by fastlane. Fastlane is also not thread safe and information from different builds could get mixed up.

Hi
Did you find a solution for this? Or do I have to target different build machines for each configuration? We just got new fancy hardware and would be sweet to be able to run multiple builds in parallell if possible :)
ping hunhejj

Unfortunately we didn't really find a nice solution.

Unfortunately we didn't really find a nice solution.

okey, thank you for the response :)


ENH: stats.xi_correlation: add xi correlation function

Reference issue
Closes gh-21453
What does this implement/fix?
This adds a function that computes the $\xi$ correlation coefficient and performs an (asymptotic or permutation) test of independence.
Additional information

alternative could be added, but two-sided and alternative='less' test seem unlikely to be useful
It's arguable that ties should be automatically detected by using _rankdata, and this should inform the choice of statistic calculation method.  However, the p-value calculation is supposed to be based on whether the distribution underlying y is continuous or not - not whether there actually are ties. So it seems like we should be able to use y_continuous for both. Perhaps automatic detection (and maybe a metod='auto') can be added in a follow -up.
When there are ties in x, they are broken at random (an option suggested by the paper). Perhaps we can do something smarter in a follow-up, but let's leave it alone for now.
too_small=1 doesn't seem to be working for multidimensional arrays
Should we document this as the $\xi$ statistic (using the Greek letter)?

@matbmeijer here is a PR for the xi correlation statistic and corresponding hypothesis test. If you're still interested, please take a look and send an email to the forum about it. If there is no longer interest, let us know if we should close the PR and issue.

I think this is a very interesting addition and I can’t wait to try it out once it’s added!

In that case, would you like to make a post on the mailing list and help find a maintainer to review? It looks like the OP does not intend to do that.

Thanks for posting @fancidev. I suppose chatterjeexi would be most consistent with existing names kendalltau, pearsonr, and spearmanr for the correlation coefficients.

In that case, would you like to make a post on the mailing list and help find a maintainer to review? It looks like the OP does not intend to do that.

Done. https://discuss.scientific-python.org/t/new-function-scipy-stats-xi-correlation/1498/1

I suppose chatterjeexi would be most consistent with existing names kendalltau, pearsonr, and spearmanr for the correlation coefficients/tests.

Sounds good to me!

One additional extension is adding confidence intervals. This can be added as a method of the result object as usual.

Good point!

Thanks @tupui. If you'd reply to or resolve the open comments, I'd appreciate it. Some of those comments were left open for the reviewing maintainer to decide.
Also, it looks like we had converged on renaming to chatterjeexi to be consistent with the names of all the existing correlation functions: kendalltau, pearsonr, and spearmanr. Should I push that change?

It's a bit ugly but yeah I suppose we should do this 👍😅

Getting this in. It went on the forum and we left that long enough up there. Thanks again Matt!


[Collapse] Collapse to height specified?

It would be a nice feature to not collapse a Collapse component all the way, but instead to collapse it to a height specified. This would allow for a small preview of the collapsable content.
There could be other ways to implement the same functionality.
Thanks for the consideration!

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

I have been looking to contribute. This looks like a decent first issue. I would like to give this one a go.


install.sh (exec file) fails

After launching
line 1: version: command not found
line 2: oid: command not found
size: '122964664': No such file

cb659ee9cf460d4fa30660adf0e67982dbd68f4d
87baca18550582cf2b95de2b6284240a85026f04
Resolved.


Skip existing copyright lines

Fixes #309
Draft for review; still need to write tests

keep open.


Feature/aqi 3742

Are there any unit tests for this body of work? @KentMiller

@joezhou-aqi  - there are no unit tests in this solution. I created automated tests in the test fixture. There's a crucible review for this.

I see that the package was created (https://www.nuget.org/packages/Aquarius.ONE.ClientSDK/13.14.0), which I think makes sense. I'd like to merge this to keep Master in sync with our package creation. Any push back?


Not compatible with the version of your running IDE

Describe the bug
Plugin is Incompatible with Webstorm 2024.3
Incompatible: requires IDE build 241.* or earlier
Steps to reproduce the behavior
No response
Expected behavior
No response
Screenshots

Additional context
No response

I've had this twice now, first when WebStorm 2024.2 was released, and it took ages to "Solve some minor issues and update dependencies" and release 1.2.2, which worked with 2024.2. then shortly after that WebStorm updated to 2024.3, and this plugin has yet to catch up to the bus.
to be completely honest, this plugin has spent more time "disabled" than "enabled" in my IDE, simply because it's been incompatible for the vast majority of the time.

just for the sake of understanding this better... is there any real benefit in locking down the version compatibility so tightly? could it perhaps work better to mark this plugin as compatible with 2024.* (or whatever pattern would cover 2024.4, 2024.5, etc.)?
best case scenario, IDE updates would change things that don't relate to this plugin.. moderate case, it changes things so one or two plugin features don't work.. worst case, it causes the IDE to crash, in which case we would just disable it until there is an update. right now, our only option is to disable it and wait for dependencies to be updated and a new release with a new compatibility check, even if the plugin code requires no major changes.
please keep in mind: I have no experience building JetBrains plugins, I'm honestly just curious as to why it takes so long each time before this gets any updates..

Incompatibility with IDE 2024.3 has been fixed by release/1.2.4.
Thanks @nekofar


Get Stuck at Building Wheel

Hi, anyone faces the problem of installation gets stuck at building wheel?

Can you share more information on your configuration, especially which DL framework you're building with? Passing the --verbose flag to pip install would also provide more useful build logs. A hang makes me suspect your system is over-parallelizing the build process:

If the hang happens while building Flash Attention or transformer_engine_torch, then it's a failure while building a PyTorch extension. Try setting MAX_JOBS=1 in the environment (see this note). Note that building Flash Attention is especially resource-intensive and can experience problems even on relatively powerful systems.
If the hang happens in CMake, then it's a failure in a Ninja build. We currently don't have a way to reduce the number of parallel Ninja jobs, but it is something we should prioritize if it is causing a problem (pinging @phu0ngng).

With https://github.com/NVIDIA/TransformerEngine/pull/987, you can control the number of parallel build jobs with the MAX_JOBS environment variable.

Same problem.
Especially, got stuck in Running command /usr/lib/cmake-3.22.6-linux-x86_64/bin/cmake --build /opt/tiger/TransformerEngine/build/cmake --parallel 1

Hm, I'd expect most systems could handle building with MAX_JOBS=1. I wonder if we could get more clues if you build with verbose output (pip install -v -v .).

I have a similar problem. With MAX_JOBS=1 it gets stuck after 6/24 and otherwise it gets stuck after 8/24 building transpose_fusion.cu.o. I use Cuda 12.5 and I have a rtx 3060.
I also tried to limitate the number of threads with export MAKEFLAGS="-j2" but without success.
(sorry for the picture but my whole computer gets frozen and I have to reboot manually)


[HOLD for payment 2023-02-24] New message green line appears after a brief moment when opening the app from background

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to any chat
Mark as read first message then swipe from bottom then open the app again.
Notice that mark as read line disappears then appears again.

Expected Result:
Mark as read line should consistently.
Actual Result:
Mark as read line disappears then appears again.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] iOS / native

Version Number: 1.2.58-3
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:
https://user-images.githubusercontent.com/43996225/214428001-1d3d6c53-f276-4e5f-a1a6-a61a1f129c5b.MP4
https://user-images.githubusercontent.com/43996225/214428016-58faba86-83d0-47cf-8c9e-9d3c0ac42358.MP4
Expensify/Expensify Issue URL:
Issue reported by: @hungvu193
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1674552168801719
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01ecfec059338b828f
Upwork Job ID:<PHONE_NUMBER>954881536
Last Price Increase: 2023-02-08

@puneetlath this issue was created 2 weeks ago. Are we close to a solution? Let's make sure we're treating this as a top priority. Don't hesitate to create a thread in #expensify-open-source to align faster in real time. Thanks!

@puneetlath 12 days overdue now... This issue's end is nigh!

I think this likely needs to be Internal.

Job added to Upwork: https://www.upwork.com/jobs/~01ecfec059338b828f

Triggered auto assignment to Contributor Plus for review of internal employee PR - @eVoloshchak (Internal)

Hi, Eduardo from Callstack, can I take this one?

@gedu as mentioned in Slack feel free to give this a try but there is a chance it requires backend changes, nevertheless post your findings!

Proposal
Please re-state the problem that we are trying to solve in this issue.
After marking a chat message as unread, when you put the app into the background and open it again, the new green line hide and shows up again
What is the root cause of that problem?
In ReportsActionView we are subscribing to Visibility.onVisibilityChange and as soon the app becomes visible we are cleaning the newMarkerReportActionID, when that happens the new green line disappears, and later when the list is fully visible, it checks if was manually marked didManuallyMarkReportAsUnread and it shows up the green line again
What changes do you think we should make in order to solve the problem?
In ReportsActionView we are subscribing to Visibility.onVisibilityChange check if still unread before clearing the newMarkerReportActionID instead of assuming that the user already read the message

https://user-images.githubusercontent.com/1676818/218082628-0c2f2ab6-db42-4ff2-882f-25ce620466bb.mp4
https://user-images.githubusercontent.com/1676818/218082665-d7de7732-7bc0-4fcd-ac49-d28fd4804c18.mp4
What alternative solutions did you explore? (Optional)
Maybe instead of using a ReportActionID using the lastReadTime, so we avoid to use kind of 2 properties to mark a message as unread, this will require a lot of code changes and testing to avoid regression bugs or breaking the working features

Ah yes that is interesting. The comment says "If the app user becomes active and they have no unread actions" but then we don't actually check whether or not the chat is unread before clearing the marker. That solution sounds good to me. @eVoloshchak what do you think?

@puneetlath, @gedu, @eVoloshchak Whoops! This issue is 2 days overdue. Let's get this updated quick!

Not overdue, PR was deployed to production 3 days ago

Updated the title to reflect this.

@eVoloshchak sent you a contract offer.

Offer accepted👌

All done. Thanks everyone!

@puneetlath please invite me, I'm the reporter

@puneetlath, the PR was merged within 2 business days. I didn't review proposals, only the PR, but it looks like contributor might be eligible for the bonus

Just gonna reopen this so we dont forget to handle the reporting bonus

@puneetlath, the PR was merged within 2 business days. I didn't review proposals, only the PR, but it looks like @gedu might be eligible for the bonus

@eVoloshchak in this case, this was handled by a vendor contributor from Callstack, so the process is more similar to our Internal PR process.
@hungvu193 sorry for forgetting about you! Can you apply here: https://www.upwork.com/jobs/~01ecfec059338b828f

@puneetlath, the PR was merged within 2 business days. I didn't review proposals, only the PR, but it looks like @gedu might be eligible for the bonus

@eVoloshchak in this case, this was handled by a vendor contributor from Callstack, so the process is more similar to our Internal PR process.
@hungvu193 sorry for forgetting about you! Can you apply here: https://www.upwork.com/jobs/~01ecfec059338b828f
For me: https://www.upwork.com/ab/applicants/1623441417954881536/applicants

Thank you, I've just applied!

Paid! Should actually be done now. Thanks everyone!


dm: fix MariaDB up down test

What problem does this PR solve?

Issue Number: close #4287
What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Questions
Will it cause performance regression or break compatibility?
Do you need to update user documentation, design documentation or monitoring documentation?
Release note
None

/hold
waiting https://github.com/pingcap/tiflow/pull/11743

/unhold

/rest

/retest

/retest


register the diskFileSystemProviderOnMain

This PR fixes #141176

@bpasero This does not fix the issue. This enables watching and listening of files on the main, but the changed files are transported from main using file scheme which is not the scheme that diskFileSystemProviderOnMain is registered with. Seems like the main/shared process channel shall use the right scheme for these files coming from main.

https://github.com/microsoft/vscode/commit/8756f0969c505ef24e9577afd2167487a03152ce


Dependency resolution doesn't take platform into account.

Poetry version: 1.5.1
Python version:  3.10.12
OS version and name: (docker: ubuntu, linux 6.4.6)
pyproject.toml: So minimal I include it inline:

[tool.poetry]
name = "tmp"
version = "0.1.0"
description = ""
authors = []

[build-system]
requires = ["poetry-core"]
build-backend = "poetry.core.masonry.api"

[tool.poetry.dependencies]
python = ">=3.10,<3.11"
torchvision = [
   {platform="linux", url="https://download.pytorch.org/whl/cu118/torchvision-0.15.2%2Bcu118-cp310-cp310-linux_x86_64.whl"},
   {platform="windows", url="https://download.pytorch.org/whl/cu118/torchvision-0.15.2%2Bcu118-cp310-cp310-win_amd64.whl"},
]
sentence-transformers = "^2.2.2"

[x] I am on the latest stable Poetry version, installed using a recommended method.
[x] I have searched the issues of this repo and believe that this is not a duplicate.
[x] I have consulted the FAQ and blog for any relevant entries or release notes.
[x] If an exception occurs when executing a command, I executed it again in debug mode (-vvv option) and have included the output below.
Attempting to export the above pyproject.toml throws an error, since walker.py thinks there are overlapping

Issue
Attempting to export the above pyproject.toml throws a runtime error.  sentence-transformers declares that it depends on torchvision.  Currently walker.py doesn't take the platform into account, so it thinks that these dependencies are overlapping and fails.  Setting a breakpoint on walker.py::get_locked_package confirms that the explicit passes for torchvision are fine: it's the pass for sentence-transformers which can't work out which to pick.
Looking at the lockfile I can't see where (if anywhere) the platform information is actually stored in it.  Should it be?  Or should the exporter consult pyproject.toml?
Traceback
(cli-py3.10) app@31552c26b59e ~/c/tmp (ci/folder-vendor)> poetry export -vvv
Loading configuration file /home/app/.config/pypoetry/config.toml
Source (poetry-lockfile): 2 packages found for torchvision *
Source (poetry-lockfile): 2 packages found for torchvision *
Source (poetry-lockfile): 1 packages found for sentence-transformers >=2.2.2,<3.0.0

  Stack trace:

  12  ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/cleo/application.py:327 in run
       325│
       326│             try:
     → 327│                 exit_code = self._run(io)
       328│             except BrokenPipeError:
       329│                 # If we are piped to another process, it may close early and send a

  11  ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/poetry/console/application.py:190 in _run
       188│         self._load_plugins(io)
       189│
     → 190│         exit_code: int = super()._run(io)
       191│         return exit_code
       192│

  10  ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/cleo/application.py:431 in _run
       429│             io.input.interactive(interactive)
       430│
     → 431│         exit_code = self._run_command(command, io)
       432│         self._running_command = None
       433│

   9  ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/cleo/application.py:473 in _run_command
       471│
       472│         if error is not None:
     → 473│             raise error
       474│
       475│         return terminate_event.exit_code

   8  ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/cleo/application.py:457 in _run_command
       455│
       456│             if command_event.command_should_run():
     → 457│                 exit_code = command.run(io)
       458│             else:
       459│                 exit_code = ConsoleCommandEvent.RETURN_CODE_DISABLED

   7  ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/cleo/commands/base_command.py:119 in run
       117│         io.input.validate()
       118│
     → 119│         status_code = self.execute(io)
       120│
       121│         if status_code is None:

   6  ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/cleo/commands/command.py:62 in execute
        60│
        61│         try:
     →  62│             return self.handle()
        63│         except KeyboardInterrupt:
        64│             return 1

   5  ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/poetry_plugin_export/command.py:109 in handle
       107│         exporter.with_credentials(self.option("with-credentials"))
       108│         exporter.with_urls(not self.option("without-urls"))
     → 109│         exporter.export(fmt, Path.cwd(), output or self.io)
       110│
       111│         return 0

   4  ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/poetry_plugin_export/exporter.py:80 in export
        78│             raise ValueError(f"Invalid export format: {fmt}")
        79│
     →  80│         getattr(self, self.EXPORT_METHODS[fmt])(cwd, output)
        81│
        82│     def _export_generic_txt(

   3  ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/poetry_plugin_export/exporter.py:95 in _export_generic_txt
        93│         )
        94│
     →  95│         for dependency_package in get_project_dependency_packages(
        96│             self._poetry.locker,
        97│             project_requires=root.all_requires,

   2  ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/poetry_plugin_export/walker.py:93 in get_project_dependency_packages
        91│         selected.append(dependency)
        92│
     →  93│     for package, dependency in get_project_dependencies(
        94│         project_requires=selected,
        95│         locked_packages=repository.packages,

   1  ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/poetry_plugin_export/walker.py:121 in get_project_dependencies
       119│         )
       120│
     → 121│     nested_dependencies = walk_dependencies(
       122│         dependencies=project_requires,
       123│         packages_by_name=packages_by_name,

  RuntimeError

  Dependency walk failed at torchvision

  at ~/code/.dockerdev-data/cli-pHEz0X_z-py3.10/lib/python3.10/site-packages/poetry_plugin_export/walker.py:151 in walk_dependencies
      147│             requirement, packages_by_name, nested_dependencies
      148│         )
      149│
      150│         if not locked_package:
    → 151│             raise RuntimeError(f"Dependency walk failed at {requirement}")
      152│
      153│         if requirement.extras:
      154│             locked_package = locked_package.with_features(requirement.extras)

Did you really search for duplicates?!
This is duplicate of at least #163, #168, #173, #176, #183, #186, #187

Did you really search for duplicates?!

Yes.  Seems I wasn't as intelligent as I could have been though.

This is duplicate of at least #163, #168, #173, #176, #183, #186, #187

#186 actually has the same setup, albeit with markers= rather than the shorthand.  Ergo this really is a dupe.  I don't have multiple versions of the same package in the pyproject.toml.  The code path is different: 181 filters out the right version, whereas this is the inverse bug: we can't select between as decided isn't being populated correctly.
I don't want to clutter up the issue tracker with noise: feel free to close this as a dupe.


Pointing shellscript shebang to env-bash instead of hardcoding bash

…this partially solves compatibility with osx (doesn't fix everything, but is a step in the right direction)
The -v operation, used in etc/to-be-installed/qemu_cmd.sh, was added in bash version 4
OSX has bash 3 by default because of licensing. This can be fixed on the user's end by
installing the new bash and updating the login shell. (This is a reasonable thing to say
the end user is responsible for on their own, and not that of this project.)
brew install bash
sudo vim /etc/shells
# while in vim add the listing: /usr/local/bin/bash
chsh -s /usr/local/bin/bash

However, on our end, many shell scripts hard-code the osx version of bash in the shebang.
Ergo "#! /bin/bash" needs to be changed in a number of places to "#! /usr/bin/env bash"
which will respect the user's preferred bash.
 Will reopen later.


Countries listed by name in timeseries-byLocation.json

I've noticed there are several instances where the timeseries data has a country keyed both by its ISO-3166 country code and its common name:

key
code

US
USA

Bahamas, The
BHS

Cape Verde
CPV

East Timor
TLS

The Gambia
GMB

Republic of the Congo
COG

Also, a couple countries are present only by their full names, not their country codes:

key
code

Syria
SYR

Laos
LAO

Thanks, @NickSto! I bet you'll find JHU is providing the ones that are keyed off something other than the ISO-3166 alpha 3 code... Can you confirm the sources for each item you noted above?
Note that the US issue should be fixed already.

@lazd Yep, JHU is the source for everything I mentioned except USA, which is from https://covidtracking.com/api/states.

Wow that was quick, thanks!

Okay looks like we got a regression. I just checked and there's a Burma key now.

@NickSto ok that doesn't sound like a regression, more like another case we didn't handle. I'll take a look.

So should Burma be MMR? It's it called Myanmar now? https://www.iso.org/obp/ui/#iso:code:3166:MM

Yeah, MMR seems to be the ISO code for that country, whatever you prefer to call it. Thanks for taking a look.


https://mrousavy.com cannot be reached 🐛

What were you trying to do?
I am trying to read the docs on https://mrousavy.com/react-native-vision-camera/docs/guides/ but the site is down
Reproduceable Code
No response
What happened instead?

Relevant log output
No response
Device
desktop browser
VisionCamera Version
latest
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

It works for me, even after clearing cache

It works for me now with cloudflare warp. I m not sure of the root cause but m glad its not a widespread problem


Improve Build Process

Discuss and implement a solid and failure tolerant build process.
Build process will be triggered for each release notification.
Here are some of the broad steps.

Clone the Repo :white_check_mark:
Compare activity.info and decide whether to continue build :ballot_box_with_check:
Build the sugar activity to .xo archive. Better approach would be to spawn docker container for this. (Yet To Implement) :ballot_box_with_check:

Fixed in #3
Commit e1924d862cab0632eb5f64c7af7183d1bdd8c6ed


fix(deps): Update prettier and associated dependencies

Some files in the project use a mix of tabs and spaces for formatting making code more difficult to read (for example, layout.svelte). Prettier could fix the inconsistent formatting but currently fails to run due to some outdated dependencies/configuration (see below).
Fixing prettier configuration/dependencies to be able to run it on the project.

npx prettier . --check
Checking formatting...
[warn] Ignored unknown option { pluginSearchDirs: ["."] }.
...
src/routes/+error.svelte
[error] Couldn't resolve parser "svelte".

Hi @r0manarmy. I just published an update with some changes that were in your PR. Also moved the eslint config to ESM.
I think everything you proposed is in my update (and then some). Please let me know if you think I missed anything.

@nstuyvesant Yeah, looks good. This PR is safe to close.

Thanks for confirming!


fix job traces spaming logfiles folder

This was observed when investigating issues with webjobs.  We traces to logfiles folder when starting trigger and continuous job executables.  This could generate a flood of traces (if those come up/down multiple time such as continuous job that stops frequently).    The side effect is the more important traces will be purged out.   The fix is to migrate those traces to ETW instead.  User can still view jog.log file to see if any issue.

That's already in.


Unknown format 6?

python WavSteg.py -r -s /testing.wav -o wave.txt -n 1 -b 1000
Ran into an error during execution. Check input and try again.
unknown format: 6

I'm using Python's wave module which only supports a few types of WAV files.
In particular, your file seems to be of type WAVE_FORMAT_ALAW which would need to be converted first (e.g. with ffmpeg).


Markdown mode

italic
bold
bold italic
headers (3 levels)
unordered lists (one level only, bullet sprite customisable)
ordered lists (one level only)
links (coverted to Scribble regions)
images
quotes (no nesting)

Implemented the parser. Customisation and testing comes next.


Transmitter should hold strong ref to Receiver

If this is not the case, then a consumer needs to hold the reference to the receiver, which might be slightly awkward. Using the approach ReactiveSwift with Signal+Observer.

Codecov Report

Merging #5 into master will increase coverage by 0.09%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master      #5      +/-   ##
=========================================
+ Coverage   98.71%   98.8%   +0.09%
=========================================
  Files           3       3
  Lines         156     168      +12
=========================================
+ Hits          154     166      +12
  Misses          2       2

Impacted Files
Coverage Δ

ReceiverTests/ReceiverTests.swift
98.26% <100%> (+0.2%)
:arrow_up:

Receiver/Sources/Receiver.swift
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


When external volume names are reused after a volume with driver_opts onRemove=retain, volumes would get purged on volume delete.

Rancher server version - Build from v1.6 branch
rancher/storage-nfs:v0.8.4
Steps to reproduce the problem:

Create Volume - "abc" (using "Add Volumes" option from Infrastructure Storage) with driver_opt onRemove=retain

Create a service - S1with this volume - "abc" using UI . Write some contents.

Delete service S1.

Delete volume - "abc"  — Volume gets deleted from rancher-server. But it continues to be in nfs server as expected.

Create another service - S2  using the same volume name - "abc" using UI.

This results in a new volume getting created in rancher-server with no driver_opt set.
Existing volume from rancher-nfs gets used for this service as expected.
Delete service S2.
Delete volume "abc".
Volume gets deleted from rancher-server. Volume also gets deleted in nfs server.

@sangeethah This is not a bug, this is the intended and expected behavior. We don't propagate driver opts when a volume is deleted and another with the same name is created.

Makes sense to me.. you created and deleted a volume, and it was retained.  That life cycle ends at 4.  5 is a new volume that happens to have the same name; it doesn't have retain, so when you delete it the underlying data should be deleted.  The directory doesn't "remember" that it was supposed to be retained for a different volume long gone.
If anything, the problem to solve is that at step 5 it is unknown and unknowable (without direct access to the NFS server) if creating "abc" is going to give me a fresh new empty volume or a recycled pre-owned one that's already got someone's stuff in it.  Seems like you should have to explicitly say reusing is ok and it should error if you don't and the directory already exists.

The other issue is the automatic creation of volumes ( which happens on creation of service with a volume that does not exist in rancher-server) not having the ability to set any driver_opts.

The explicit "reusing is ok" flag, defaulted to false, would be really helpful in testing. I've run into strange test results more than once because I was reusing a host/export in different environments and the volume names happened to collide.


Draft: Add backfilling to search backed by GORM

Search will need to backfill regularly when rebuilding indexes.
I've adopted a backfill pattern I created a few weeks ago into indigo and updated Search's firehose consuming to adopt the backfilling pattern.

I haven't reviewed in depth, but i'm pretty darn excited about having a generic backfill mechanism like this! Great work.


Reorder steps in build_universe.yaml

This PR should make merge conflicts less likely in workflows that pull and push back to https://github.com/r-releases/r-releases.r-universe.dev.

The explicit specification of r-releases in build_universe() is because r-releases refers to a fixed local folder and not a GitHub org. That's minor.
The main thing is checking out the repo after we install R and package. Otherwise the following merge conflict scenario is more risky:

job: check out repo
job: install packages
someone/something else: push to GitHub
job: merge conflict trying to push packages.json


Document ttAdapter and integration between typeahead and bloodhound

Cross-posting this from https://github.com/twitter/typeahead.js
The docs are split in two with no page explaining how the two fit together, which is how they will be used most of the time.
More importantly, there's no mention whatsoever in either page of the ttAdapter method, even though most users specify engine.ttAdapter() as their source in the typeahead, as is done here. This is a key function as it runs the engine's search:
            __ttAdapter: function ttAdapter() {
                var that = this;
                return this.remote ? withAsync : withoutAsync;
                function withAsync(query, sync, async) {
                    return that.search(query, sync, async);
                }
                function withoutAsync(query, sync) {
                    return that.search(query, sync);
                }
            },

This was needed in v0.10.x and it WAS in the docs, but the author removed it. Seems to be deprecated in v0.11.x.
The typeahead manual states:  source can also be a Bloodhound instance.
So in your example:  source: movies


Dragging Control nodes is super slow

Godot version
a76db34
System information
Windows 10 x64
Issue description
This is more prominent in debug builds, but when you drag a Control node, the movement is extremely lagging:

I debugged a bit and seems like the inspector is refreshed twice with each movement.
Steps to reproduce

Create a new User Interface scene
Add any Control child
Drag it around

Minimal reproduction project
No response

I can confirm this on 4.0.alpha 992317957 (Linux, NVIDIA 510.68.02).

Dragging a control node makes a call to Control::_edit_set_state() (in control.cpp) which in turn calls Control::_set_layout_mode() which seems to be the culprit. I commented out this call to _set_layout_mode() which eliminated the performance issues entirely for me.
For an actual solution I have this in mind. Within Control::_set_layout_mode() there is currently a check for whether or not the mode is actually being changed. It looks like this:
...
if ((int)get_meta("_edit_layout_mode", p_mode) != (int)p_mode) {
	list_changed = true;
}
...

If this if-statement fails the method still proceeds, although without the list_changed flag set to true. Assuming that this method's only purpose is to set the mode, it is safe to return from the function if the current layout mode is the same as the new mode. Adding an else-block with a simple return solves the performance issues for me.
I'm very new to the godot code base so I might be missing something. But if this sounds like a reasonable approach I can issue a pull request with this change to Control::_set_layout_mode()

I investigated this a bit and seems like it's a regression from #59185

I notice the method is adding the "_edit_layout_mode" meta regardless of whether or not the mode is LAYOUT_MODE_POSITION or LAYOUT_MODE_ANCHORS, then proceeds to remove this meta if the mode is LAYOUT_MODE_POSITION (which I guess is the default value, thus redundant):
...
set_meta("_edit_layout_mode", (int)p_mode);

if (p_mode == LayoutMode::LAYOUT_MODE_POSITION) {
    remove_meta("_edit_layout_mode");
...

Only adding the "_edit_layout_mode" meta if the mode is LAYOUT_MODE_ANCHORS also fixes the performance issue. To me this seems like the most straightforward solution. I'll create a pull request with this fix.


WIP: Update CONTRIBUTING.md

Remove CLA reference

Maybe it would make sense for this PR just to remove the CLA, and then to make another issue / PR for designing the process.


[BUG]: cert-csi documentation clarity

Bug Description
The driver specific examples in the documentation are great
https://dell.github.io/csm-docs/docs/support/cert-csi/
For PowerStore, as an example, the values (true/false) are setup properly for valid use cases.
in contrast,
https://github.com/dell/cert-csi/example-certify-config.yaml seems incomplete
example-certify-config.yaml
requests:

include driver specific example in the github repository
remove the example-certify-config.yaml from the github repository
include critical comments in the driver specific tests yaml for any test requirements.  For example, the "waitforfirstconsumer" requirement for the CapacityTracking test, and in OpenShift, any labels that need to be applied to the CSI driver

Logs
n/a
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
n/a
Expected Behavior
n/a
CSM Driver(s)
powerstore 2.10.1
Installation Type
No response
Container Storage Modules Enabled
No response
Container Orchestrator
OpenShift 4.14
Operating System
OpenShift 4.14

Hi Rajendra, please do triage and create internal ticket for tracking of this issue.

/sync


⚠ Bofrost.de has degraded performance

In dfacfe5, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1293 ms

Resolved: Bofrost.de performance has improved in ed826b7 after 8 minutes.


Editor locks up after about 1 hour of usage

Issue Type: Bug
After updating from the previous version of vscode, after about an hour the editor starts locking up for 30-60 seconds, then starts working for about 5 seoncds and the cycle repeats over and over.
To fix the issue I need to reload the window (F1 -> Reload Window), and then an hour or so later it starts happening again.
I have been working on TypeScript files, so for all I know it is TypeScript that is causing this, but there is nothing in the developer tools or output console. I have no information as to what is causing this, all I know is that it is happening, and it was after I upgraded VSCode versions.
I have both Windows and Ubuntu, and it happens on both.
When working with the project, I have 2 terminals open, one that is running pm2 log and one that is running gulp build (from a task.json task). I don't know if maybe one of these are causing the editor to lock up?
Let me know if you need more information, however at the moment this is all I have...
VS Code version: Code 1.26.1 (493869ee8e8a846b0855873886fc79d480d342de, 2018-08-16T18:34:20.517Z)
OS version: Linux x64 4.15.0-33-generic

System Info

Item
Value

CPUs
AMD Phenom(tm) II X6 1090T Processor (6 x 1499)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: disabled_softwarevideo_decode: unavailable_softwarevideo_encode: unavailable_softwarewebgl: enabledwebgl2: enabled

Load (avg)
2, 1, 1

Memory (System)
7.79GB (0.46GB free)

Process Argv
/usr/share/code/code /home/ryan/Documents/vscode/projects/website-builder/

Screen Reader
no

VM
0%

This is likely https://github.com/Microsoft/vscode/issues/56628, can you try the insiders build and see if it happens there? https://code.visualstudio.com/insiders/

@Tyriar looks like that might be the issue, with the insiders build, I have yet to have any issues.

@TheColorRed thanks for letting me know 😃


since update i cant activate consol

Hi since the latest update when i click the start activation button no page pops up as per the message meaning im unable to link my consol

May be popup blocked, what is displayed in the Authorization Manager?

same for me wait....

No any bug, was popup window blocked in my safari web browser, for some unknown reason after yesterday system update.
Nów is open as excepted.

thanks it was the pop up blocker issue, all fixed now, thanks for your help


Ensure that the time zone in the provenance section has the correct time zone offset

Change the time zone from UTC to local

Duplicate issue


Bad error messages when server response isn't a GraphQL error

These kinds of error messages are pretty useless and should contain as much helpful information as possible.
Maybe there generally should be a way to expose HTTP response headers?

Seems like dumping the entire HTTP response (including the response body) when this happen could be helpful. This could be done if the JSON.parse fails or if there is missing both data and errors key.


Recursive updates

Describe the bug
This issue is not present in 0.14.x and affects both Chrome and Firefox.
Any page with multiple BModal components (and others, but I've only tested with modals) results in the following warning in console:

Maximum recursive updates exceeded in component <RouterView>. This means you have a reactive effect that is mutating its own dependencies and thus recursively triggering itself. Possible sources include component template, render function, updated hook or watcher source function.

Where <RouterView> is any top-level component, e.g., this would be called <Inertia> in a default layout Inertia app.
If the modals are not present in a nested component the issue will not appear.
This issue breaks the functionality of complex pages.
Reproduction
https://stackblitz.com/edit/github-jfyohs?file=src%2FPages%2FIndex.vue
Used Package Manager
npm
Validations

[X] Have tested with the latest version. This is still alpha version and sometime things change rapidly.
[X] Follow our Code of Conduct
[X] Read the Contributing Guide.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A, please open a GitHub Discussion instead.
[X] The provided reproduction is a minimal reproducible of the bug.

The contained reproduction doesn't contain any warning or errors

This seems to be a bug in hmr and/or vue-router with modal.

It is not a problem with the router, here is a reproduction repo that might illustrate the issue a bit better: https://stackblitz.com/edit/github-3pqadn?file=src%2FChildComponent.vue
Before making a change in ChildComponent.vue please open console and see the interval ticking normally. Make any change and see it attempt to instantiate itself infinitely before being caught by Vue.
It is a major problem: it completely kills development until the page is fully reloaded, so every change breaks the page. Versions prior to 0.15 do not have this issue.
I am not sure if this is something that can also be triggered in production, but I have not looked into it.

Any info helps.

I checked out the 0.14.10 and 0.15.5 tags and can confirm this has nothing to do with the BModal component, I am able to recreate the issue on the latest release but not on 0.14.10, even after cherry picking the latest version of the component into the older branch, so it seems some other utility or lib change is causing this, but I am unable to investigate further at this time.

0.14.10 is fine but 0.15.0 is not.
This break since commits made on Oct, 30

Same problem here. Using BModal component produce the warning message mentioned by @benjivm.
I am not sure if this can be a problem in production because, in my case, the problem appears when you're making changes to the page. So in development mode, when the page reload, the warning message is displayed.
The error is not present in 0.14.10.

After upgrade Vue 3.3.13 to 3.4.15 using bootstrap-vue-next 0.14.10:
Uncaught (in promise) Maximum recursive updates exceeded. This means you have a reactive effect that is mutating its own dependencies and thus recursively triggering itself. Possible sources include component template, render function, updated hook or watcher source function.
Problem persists if using bootstrap-vue-next 0.16.0.

There is also an error in the browser and a large memory leak. If there is more than one BModal on one pure component.
vue: 3.4.26
bootstrap-vue-next: 0.17.4
vite: 5.2.10
[Vue warn]: Unhandled error during execution of app errorHandler
warn$1 @ chunk-KRQ7UQDJ.js?v=e2aa7cc5:1512
logError @ chunk-KRQ7UQDJ.js?v=e2aa7cc5:1724
handleError @ chunk-KRQ7UQDJ.js?v=e2aa7cc5:1716
checkRecursiveUpdates @ chunk-KRQ7UQDJ.js?v=e2aa7cc5:1895
check @ chunk-KRQ7UQDJ.js?v=e2aa7cc5:1865
flushJobs @ chunk-KRQ7UQDJ.js?v=e2aa7cc5:1870
Promise.then (async)
queueFlush @ chunk-KRQ7UQDJ.js?v=e2aa7cc5:1782
queueJob @ chunk-KRQ7UQDJ.js?v=e2aa7cc5:1776
reload @ chunk-KRQ7UQDJ.js?v=e2aa7cc5:1983
(anonymous) @ chunk-KRQ7UQDJ.js?v=e2aa7cc5:2013
(anonymous) @ journal-index.vue:351
(anonymous) @ hmr.ts:77
(anonymous) @ hmr.ts:311
(anonymous) @ hmr.ts:277
queueUpdate @ hmr.ts:277
await in queueUpdate (async)
(anonymous) @ client.ts:205
handleMessage @ client.ts:203
(anonymous) @ client.ts:91
Show 17 more frames
Show less
123432:1 Uncaught (in promise) Maximum recursive updates exceeded in component <RouterView>. This means you have a reactive effect that is mutating its own dependencies and thus recursively triggering itself. Possible sources include component template, render function, updated hook or watcher source function.

There is also an error in the browser and a large memory leak. If there is more than one BModal on one pure component.  This means you have a reactive effect that is mutating its own dependencies and thus recursively triggering itself. Possible sources include component template, render function, updated hook or watcher source function.

I'll add a comment - this happens when vue-router is installed

I have
vue: 3.4.26
bootstrap-vue-next: 0.17.5
vite: 5.2.11
no vue-router installed but it's almost the same


Update README.md

Changing from relative path to absolute path so that the link in https://kubeapps.com/charts/stable/consul is not broken.

@prydonius Should this be an issue against monocular?

I'm closing as this should be fixed in monocular. See kubernetes-helm/monocular#180

@mattfarina agreed, thanks for moving it there.


GDScript: Load global classes when running debug tests

So when running compiler debug tests it works with dependencies within a project.

I tested it. This works under the following conditions:

It's bin/<godot executable> --test gdscript-compiler <path/to/script.gd> command (test_gdscript.cpp).
There is project.godot file.
There is correct .godot/global_script_class_cache.cfg file.

It doesn't work for regular tests (gdscript_test_runner.cpp). Is it intentional?

Interesting! So this only works because it's done within the context of a project. Is there any situation in which this might be run but there is no ProjectSettings singleton, which might cause a crash?
I was working on something similar to try to add a unit test to #79205, but there we cannot rely on ProjectSettings, I believe. My attempted solution was to add global class names found in .gd test scripts, as well as .notest.gd test scripts. Unfortunately that wasn't enough to make the class loadable and I didn't investigate further.

It doesn't work for regular tests bin/<godot executable> --test (gdscript_test_runner.cpp). Is it intentional?

Yes, the test runner does not use a project nor the global classes config. It generates the index on the fly from all the test files:
https://github.com/godotengine/godot/blob/f6187014ec1d7a47b7201f64f3a8376a5da2f42d/modules/gdscript/tests/gdscript_test_runner.cpp#L321-L337

Interesting! So this only works because it's done within the context of a project. Is there any situation in which this might be run but there is no ProjectSettings singleton, which might cause a crash?

I don't think there's such case. This code is really only run from one code path AFAIK.


Missing Symbol

Where can I find the symbols for nt! TRIAGE_9F_POWER. I get
Symbol nt!TRIAGE_9F_POWER is not found when I run this program. Please help.

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

ID: 28a05e45-339b-d94e-f337-e802afd56b79
Version Independent ID: 8db6253e-eb0c-e88b-bf1e-7270a56096ca
Content: Bug Check 0x9F DRIVER_POWER_STATE_FAILURE - Windows drivers
Content Source: windows-driver-docs-pr/debugger/bug-check-0x9f--driver-power-state-failure.md
Product: windows-hardware
Technology: debugger
GitHub Login: @DOMARS
Microsoft Alias: domars

This symbol should aready be included in the publicly available symbol for ntoskrnl  on https://msdl.microsoft.com/download/symbols
One thing to try, add an underscore to the beginning of the type name. many NT symbols use a typedef and you may need to use the original struct name which begins with an underscore.
dt nt!_TRIAGE_9F_POWER
0:000> lm
start             end                 module name
0000000140000000<PHONE_NUMBER>046000   ntoskrnl   (pdb symbols)          C:\ProgramData\Dbg\sym\ntkrnlmp.pdb\5D6312DA6921E3A4E7F938B88330B0771\ntkrnlmp.pdb
0:000> dt TRIAGE_9F_POWER
Symbol TRIAGE_9F_POWER not found.
0:000> dt _TRIAGE_9F_POWER
ntoskrnl!_TRIAGE_9F_POWER
+0x000 Signature        : Uint2B
+0x002 Revision         : Uint2B
+0x008 IrpList          : Ptr64 _LIST_ENTRY
+0x010 ThreadList       : Ptr64 _LIST_ENTRY
+0x018 DelayedWorkQueue : Ptr64 _TRIAGE_EX_WORK_QUEUE
+0x020 DelayedIoWorkQueue : Ptr64 _TRIAGE_EX_WORK_QUEUE

@Jacksole - Thanks for filing this issue. And @grahamm78 - thanks for seeing the fix here. I updated the doc to use the _TRIAGE_9F_POWER. Good luck with your debugging and thanks again for calling out this error in the docs.


Model 3d always top view different and LoadingNode tags are too blurry

hi @ThomasGorisse @grassydragon, when scroll model 3d alway top view different, how to set model 3d equal view different?

I using LoadingNode loading tag but too blurry. How to improve quality view?
Can you help me resolve it? thank so much

Hi.
Sorry about that but I totally don't get your question. Can you precise it?

hi @ThomasGorisse when I set sceneView.setZOrderOnTop(false) -> background black. How to set background transparent? (I set  sceneView.setBackgroundDrawable(transparent) but not working!)

How to fix this issue?


Add desktop modeler release notes 7.14.0

Please review.

@jandevriesmendix Does this set of release notes need a link to your video? (Could find Fiona on GitHub, or I would have asked her)

@tao-zhang : Looks good. I've made a couple of changes for typos and where I felt that we could be a bit clearer. I've also added a few comments which may, or may not, need action.
Can you have a look and make sure my changes are OK, and let me know if you want any changes relating to the comments.

@MarkvanMents That's correct. We will have a link to the video on Monday. The release notes can be published if they don't contain a link to the video yet. I will add the link when it's available.


[QUERY] End to end tracing via Azure.Messaging.ServiceBus

Query/Question
Should Azure.Messaging.ServiceBus support correlation between pub and sub?  Specifically, when viewing the end-to-end transaction details in Application Insights, should I be able to view the complete code path from sending the message to a topic continuing through processing the messages by subscribers?
I built a simple .NET 5 web application that sends and receives topic/subscription messages using Microsoft.Azure.ServiceBus on one code path and Azure.Messaging.ServiceBus on another.
Messages processed via Microsoft.Azure.ServiceBus show both pub and sub

Messages processed via Azure.Messaging.ServiceBus show as two different transactions.
one for pub:

one for sub

Environment:

Azure.Messaging.ServiceBus 7.0.1
.NET SDK (reflecting any global.json):
Version:   5.0.101
Commit:    d05174dc5a

Runtime Environment:
OS Name:     Windows
OS Version:  10.0.19041
OS Platform: Windows
RID:         win10-x64
Base Path:   C:\Program Files\dotnet\sdk\5.0.101\
Host (useful for support):
Version: 5.0.1
Commit:  b02e13abab

Visual Studio 16.8.3

Quick update based on some additional research.
If I start an activity in my ProcessMessage callback and set the parent id to the Diagnostic-Id I get end to end tracing.
`
var activity = new Activity("ProcessMessage");
if (arg.Message.ApplicationProperties.TryGetValue("Diagnostic-Id", out var parentId))
{
activity.SetParentId(parentId.ToString());
}
        activity.Start();

        DoWork();

        activity.Stop();

`
Take this with a grain of salt.  I've only just started poking around the Azure.Messaging.ServiceBus solution.  The parent context appears to be added as a linked diagnostic activity.  The Links property on DiagnosticActivity does not override the Links inherited from Activity and instead creates a "new" Links.  Given that DiagnosticActivity is private it can't easily be referenced directly as a DiagnosticActivity by app insights or other libraries.  I'm assuming it would be referenced as Activity in most situations;, this would result in Links resolving to Activity.Links, not DiagnosticActivity.Links.  The "new" keyword appears to be relatively recent.  Could this have broken the correlation?
`
private class DiagnosticActivity : Activity
{
private List? _links;
        public new IEnumerable<Activity> Links => (IEnumerable<Activity>?)_links ?? Array.Empty<Activity>();
    }

`

Quick update based on some additional research.
If I start an activity in my ProcessMessage callback and set the parent id to the Diagnostic-Id I get end to end tracing.
`
var activity = new Activity("ProcessMessage");
if (arg.Message.ApplicationProperties.TryGetValue("Diagnostic-Id", out var parentId))
{
activity.SetParentId(parentId.ToString());
}
        activity.Start();

        DoWork();

        activity.Stop();

`
Take this with a grain of salt.  I've only just started poking around the Azure.Messaging.ServiceBus solution.  The parent context appears to be added as a linked diagnostic activity.  The Links property on DiagnosticActivity does not override the Links inherited from Activity and instead creates a "new" Links.  Given that DiagnosticActivity is private it can't easily be referenced directly as a DiagnosticActivity by app insights or other libraries.  I'm assuming it would be referenced as Activity in most situations;, this would result in Links resolving to Activity.Links, not DiagnosticActivity.Links.  The "new" keyword appears to be relatively recent.  Could this have broken the correlation?
`
private class DiagnosticActivity : Activity
{
private List? _links;
        public new IEnumerable<Activity> Links => (IEnumerable<Activity>?)_links ?? Array.Empty<Activity>();
    }

`

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

@psiservices-dbrink thanks for creating this issue. There appears to be work that needs to happen within App Insights to get the end to end tracing to work with the new library. I've created an issue in their repo that links back to this one -

@psiservices-dbrink thanks for creating this issue. There appears to be work that needs to happen within App Insights to get the end to end tracing to work with the new library. I've created an issue in their repo that links back to this one -

Any update on this? This works very nicely already with EventHubs. Just switched to ServiceBus and somewhat disappointed that end-to-end tracing doesn't seem to work here OOTP. I can see the Diagnostics-Id message property is getting correctly set by the sender but the processor does not seem to use it at all.

Hi @sebader,
That PR updates the processor so that the diagnostics-Id from the message is included as the correlation information in the ServiceBusProcessor.ProcessMessage.Start event. Before this PR, the linked activity would not be available as part of the Start event but only as part of the End event as mentioned in https://github.com/Azure/azure-sdk-for-net/issues/20349.
We will plan to release a patch with this in the next week or so.

ok thanks @JoshLove-msft ! Will watch out for the new version and will give it a try

@JoshLove-msft , does #20349 actually correct end to end tracing with app insights/service bus or does this issue still need to be fixed?
If the latter, is there any way to get the app insights team engaged?

Hi @psiservices-dbrink, we would still need the app insights work. I've pinged on that issue to try to get an update.

@JoshLove-msft If this is a valid feature request or a bug, can you please add the appropriate label and milestone?

This is a feature request and it is waiting on work by the App Insights team. https://github.com/microsoft/ApplicationInsights-dotnet/issues/2151

Hi everyone
I'm using Azure.Messaging.ServiceBus version 7.5.1 and end-to-end tracing seems to work out-of-the box. I even checked that a "Diagnostic-Id" property is available in ApplicationProperties Property of the message on receiver side. (Side note, it seems it's not working for sheduled messages. is that expected ?)
For additional tracing, I wanted to use Correlation-Context header to carry some very specific properties to be attached to the message as well. As explained in this page of the documentation, the end-to-end tracing implementation is based on HTTP Correlation protocol, which can leverage Correlation-Context header to store additional context data. Unfortunately, I don't see this data being carried to ApplicationProperties in the message on the service bus receiver side. Am I doing it wrong ? Or is it part of things still not implemented in Azure.Messaging.ServiceBus SDK ?

@ncoussemacq, if you set a header in the application properties it should still be there when the message is received, regardless of what the header is. We don't have special handling for correlation-context, but I'd expect it to still be on the received message. Are you sure you are looking at the same message?

Regarding the tracing not working for scheduled messages, this is not expected. Can you share a code snippet?

I wanted to use Correlation-Context header to carry some very specific properties to be attached to the message as well.
Unfortunately, Correlation-Context (and  HTTP Correlation protocol) are not supported in any Azure SDK. We use W3C trace-context for Diagnostic-Id format but the formal W3C standard for Baggage (aka Correlation-Context) is still in draft.

The docs seem to be out of date and I'll update them to reflect it.
As @JoshLove-msft mentioned, you can pass anything you want through application properties, but you'd have to populate those properties manually on the telemtery depending on your tracing solution.

Thanks for these answers.
I didn't plan to manually set any additional property and was expecting it to be done automagically. I'll check if it's possible to do it on my side. Do you plan to support Baggage header propagation when the standard will be approved ?
About correlation not working on scheduled message, I just figured out why while trying to write a sample to reproduce it. Sorry for that false report.

@ncoussemacq  thanks a lot for the update!
Once the Baggage is approved, we'll gradually adopt it.

Hi everyone
I'm using Azure.Messaging.ServiceBus version 7.5.1 and end-to-end tracing seems to work out-of-the box. I even checked that a "Diagnostic-Id" property is available in ApplicationProperties Property of the message on receiver side. (Side note, it seems it's not working for sheduled messages. Is it expected ?)
For additional tracing, I wanted to use Correlation-Context header to carry some very specific properties to be attached to the message as well. As explained in this page of the documentation, the end-to-end tracing implementation is based on HTTP Correlation protocol, which can leverage Correlation-Context header to store additional context data. Unfortunately, I don't see this data being carried to ApplicationProperties in the message on the service bus receiver side. Am I doing it wrong ? Or is it part of things still not implemented in Azure.Messaging.ServiceBus SDK ?

It works out of the box, one issue I noticed is that the library makes use of the old System.Diagnostic.DiagnostiSources and if any projects references the new diagnostic versions it breaks down see.
https://github.com/dlebee/corrolation-function-servicebus

@dlebee Unfortunately Azure Functions doesn't allow to use DiagnosticSource version that's ahead of the host version, Azure SDK are compatible with Function runtime v2+ and can't update DiagnosticSource.

@dlebee Unfortunately Azure Functions doesn't allow to use DiagnosticSource version that's ahead of the host version, Azure SDK are compatible with Function runtime v2+ and can't update DiagnosticSource.

I actually found a way to fix Activity Tags and have a potential hotfix to support it if you are interested using OperationLinks just cleaning it up a bit.
It involves activating the experimental flag of supporting Activity of the library ServiceBus Messaging and a bit of Telemetry Initializers.

Looks like this was fixed in ApplicationInsights 2.21.0: https://github.com/microsoft/ApplicationInsights-dotnet/pull/2593 🙂

Yes, this is now available in https://www.nuget.org/packages/Microsoft.ApplicationInsights/2.21.0


Seeing warning Several alternatives for attribute name '{key}'

My script runs fine on a small version of my XML file but using a larger version, fails with the warning:
parse_biosample_into_DB.py in Entry.handle_email(self, node)
    @xml_handle_element("Owner","Contacts","Contact")
        def handle_email(self, node):
--->     if node.attributes['email']:
                 self.email = node.attributes['email']

File /usr/local/lib/python3.9/site-packages/bigxml/nodes.py:26, in XMLElementAttributes.__getitem__(self, key)
 def __getitem__(self, key):
     alternatives, value = self._items[key]
     if alternatives > 1:
         warnings.warn(
             (
                 f"Several alternatives for attribute name '{key}'."
   (...)
             RuntimeWarning,
         )

KeyError: 'email'

The offending handler (inside a dataclass):
    @xml_handle_element("Owner","Contacts","Contact")
    def handle_email(self, node):
        if node.attributes['email']:
            self.email = node.attributes['email']

The data looks like:
<Contact<EMAIL_ADDRESS>
but there are a few instances of
<Contact<EMAIL_ADDRESS>lab="ACME Labs">
    <Name>
        <First>Jane</First>
        <Last>Doe</Last>
    </Name>
</Contact>

I can't see any other elements with the attribute email in my XML file, so I'm lost as to why this is occurring.

Disregard - I discovered some nodes do not have the email attribute, so I solved the issue with:
    if node.attributes.get('email'):

About the Several alternatives for attribute name warning
This warning occurs that there are several attributes with different namespaces, so we don't know which value to get. More info in the docs.
I don't think that's the case here however, since you don't get the warning but only sees it in the stacktrace to provide context.
The KeyError exception
The exception you are having is KeyError: 'email'.
Maybe there are some Contact tag without the email attribute?
In which case, you could do for example:
if 'email' in node.attributes:
    self.email = node.attributes['email']

or with a walrus operator:
if email := node.attributes.get('email'):
    self.email = email


Data for next 24 hrs

Hi!
Thanks for creating this module.
I'm currently pulling the data via Awattar API using Node-Red but am not able to get the prices for all upcoming next 24 hours.
From my knowledge, Awattar only publishes the data something about 14:00 UTC+1.
Did you find a way to receive the prices for the upcoming 24hrs, no matter at which time you pull them?
In the sensor data, I can only see the prices for today.
Thanks

duplicate #1


Railway data field loss problem

I have A problem with railway data. I can't get the railway network by setting network_type, so I download the railway data by setting custom_filter='["railway"~"rail|subway|light_rail|tram|narrow_gauge"]'.  However, there is no railway field in the data after downloading, so I can no longer distinguish rail or TRAM in the network.  How can we solve this problem?
thanks a lot !

And this is my code:
import osmnx as ox
city=ox.graph_from_place('Taiwan',which_result=2,simplify=False,custom_filter='["railway"~"rail|light_rail|narrow_gauge|subway"]')
ox.save_graph_shapefile(city,'T_rail')

See https://osmnx.readthedocs.io/en/latest/osmnx.html#osmnx.utils.config and https://stackoverflow.com/a/62106557/7321942

See https://osmnx.readthedocs.io/en/latest/osmnx.html#osmnx.utils.config and https://stackoverflow.com/a/62106557/7321942

That seems to solve my problem. I'll give it a try. Thank you very much!


Included Application Guard

Application Guard is an upgraded experience (using SafeDocs as well) from Protected View when tenant has enabled the feature and set the policy.

@JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks

@ekarafezov Please implement the feedback. Thanks


can't type on my code editor

I can't type or code on my editor , I would love to restore to default mode

please try running with extensions disable, F1 > Reload with Extensions Disabled


Update README.md

FedRec-woLDP-1.json是什么文件呢

It is used to save model performance during model training period. You can change the file name as you like.


JWT token expiration

JWT tokens supports a withExpiresAt options see here
Is it possible to add support for this in as an extension or a similar method to https://github.com/GetStream/stream-java/blob/6645fce4d648c8c4e3ec97b5f38543a8f28d312f/src/main/java/io/getstream/core/utils/Auth.java#L115-L114 ?
I've also seen this option is available in stream clients in other lang (e.g. ruby)
We want to leverage this so that if a malicious user were to access the token, they won't always have access to notification data. The default of a never expiring token seems too lax.

Added overloads for frontend token generation methods in new 3.1.7 release:
See https://getstream.github.io/stream-java/io/getstream/core/utils/Auth.html#buildFrontendToken-java.lang.String-java.lang.String-java.util.Date- and https://getstream.github.io/stream-java/io/getstream/client/Client.html#frontendToken-java.lang.String-java.util.Date-

Awesome tyvm!


Convert Javascript to Typescript

Which feature you want to improve?
Convert implementation in Javascript to Typescript to:

Better type checking
Convert repository to be classified as Typescript project

What and why you want to improve that feature

[ ] cli
[x] docs-e2e-testing
[ ] setupTests.js in ts projects

@nvh95 yooo 👋
cool project, sad i didnt hear about this from the very beginning, wish i could've hacked on it a ton haha 😆
can i help here? can i take over something?


Add ability to use cursor pagination with beanie

@uriyyo I also added a backwards pass with testing, but I can't figure out why it works for Document and doesn't work for Document.find()


Tasks-Vision Image Segmentation Selfie Landscape GPU Output Misaligned and Poor Quality

Have I written custom code (as opposed to using a stock example script provided in MediaPipe)
None
OS Platform and Distribution
Windows 11
Mobile device if the issue happens on mobile device
No response
Browser and version if the issue happens on browser
No response
Programming Language and version
Javascript (Chrome Version 121.0.6167.161 (Official Build) (64-bit))
MediaPipe version
0.10.9
Bazel version
No response
Solution
Tasks Vision Image Segmentation - Selfie Segmentation
Android Studio, NDK, SDK versions (if issue is related to building in Android environment)
No response
Xcode & Tulsi version (if issue is related to building for iOS)
No response
Describe the actual behavior
Output is vertically offset by about one texel (1/144) in common scenarios
Describe the expected behaviour
Output should be correctly positioned
Standalone code/steps you may have used to try to get what you need
You can see this behavior in the demo itself:
https://mediapipe-studio.webapps.google.com/demo/image_segmenter

This seems to primarily effect the landscape model, as this one has the output about one texel below where it should be.  For me this happens only when GPU inference is turned on.  Interestingly, if I am using my Intel iGPU instead of my 3090, the GPU inference option does yield correctly positioned output. Even if I shift the output back up one pixel, the quality is better but still rough, so it might not be as simple as a one texel shift.  The legacy solution does not have this problem regardless of CPU/GPU, and on a side note, the new solution has significantly higher CPU, GPU, and RAM consumption also.

Other info / Complete Logs
No response

For the side-note: MediaPipe Studio is a complicated environment (there's a bunch of extra stuff going on there), so I believe that if you try profiling a standalone demo like the CodePen instead (https://mediapipe-studio.webapps.google.com/demo/image_segmenter), you will get much better measurements on CPU/GPU/RAM consumption.
Also, even the CodePen demos can be made quite a bit faster and more efficient if the visualization rendering is performed on GPU as well-- more information can be found on #4630, and it looks like there's at least one sample which now uses this more efficient path: https://github.com/googlesamples/mediapipe/pull/212.
Please let us know if trying either/both of the above doesn't improve things!
I'd also be curious to hear if the output mis-positioning you're experiencing is also fixed by changing demo environment (that would tell us if the issue is just visualization in Studio, or if the problem is possibly something else).

Because there is an overlay rather than a background swap, the misalignment is a lot easier to see in the main demo (https://mediapipe-studio.webapps.google.com/demo/image_segmenter), but it appears to still be present in the tutorial background segmenter (https://github.com/googlesamples/mediapipe/tree/main/tutorials/background_segmenter).  The general way to tell is to get your arm/hand just right so that it is being detected as foreground, and you can see that the top gets cut off a bit and the bottom includes a bit extra.  Once again, I only get this on my 3090 and not when I am using CPU or when I have my iGPU selected as my GPU.
Tutorial Segmenter GPU Enabled (RTX 3090):

Tutorial Segmenter CPU Enabled:

With a green screen, the misalignment in the GPU version becomes much more clear, but it is really easy to miss the difference in most situations, where it is just a slight appearance of the image segmentation being worse.
With regards to the performance, even in the tutorial demo, I am seeing about 2x more CPU and GPU consumption than the legacy implementation, and the memory consumption is closer but still worse.  I am curious about how it works under the covers and why it needs so much CPU, as my naive thought process is that a 255x144 image would just be sent to the GPU and then go through several neural network layers and then output as the mask, which should barely use the CPU at all.

The misalignment is interesting-- since it's GPU-specific, makes me wonder which operations on your GPU are resulting in these differences (like whether the issue is model-specific as well, or if it only occurs for confidence mask versus category mask, etc.).  Narrowing that down as much as possible sounds like a good next step.
As for the performance, if everything is being done GPU-side, then the new API should be at least as efficient, if not even more so.  However, the new API does have a lot of additional options that the previous one didn't have.  So it would be good to verify between old and new API tests that everything else being tested for is the same.  In particular, that:
(a) the model being used is the same
(b) only the confidence mask is being produced (the old API didn't have category masks-- those are a more complicated optional feature)
(c) the ML inference is using GPU for both
(d) there is no CPU postprocessing accidentally occurring when using the new API when the results are being drawn to screen, or when the mask is being handled
(e) the demo itself is comparable (the "background_segmenter" demo performs a blur and does a bunch of imageBitmap conversions, for example).
I suspect that at least one if not more of these cases (a)-(e) is causing the difference in work, since otherwise the pipeline should be almost entirely GPU, and it should be very efficient, and there should be very almost no CPU processing being performed (except waiting for GPU processing to finish, which would likely show up in a profile as "readPixels" calls taking a long time).
At the very least, looking at the code makes me think that (e) would certainly cause some large performance differences.  In particular, I see that the "background_segmenter" demo doesn't check if video.currentTime has increased when processing video frames (in order to prevent duplicate frame rendering), so it will very likely literally just be doing 2x or 3x the amount of work for no reason by processing the same frame 2 or 3 times in a row!  So that's the first thing I'd try to fix.
To make things simpler and more direct for comparison, if the video.currentTime fix isn't enough, I think I'd then personally just scrap all the existing demos and make a much simpler and more direct test-- where I force everything to be the same (resolution, model, only confidence masks, GPU only, etc.), and then I'd take the mask texture (as a WebGLTexture) and render it directly myself using some same shader code into the canvas for final output.  Otherwise, there's just too many differences between all these different demos/examples, and I think trying to hunt down deltas one-by-one would take a lot longer than just making a simple comparison from scratch that can compare the two APIs in an apples-to-apples way.
Also, if you capture screenshots of the performance profiling traces when running these demos, that can sometimes be enough to see where things are taking too long (or using CPU unexpectedly).  So that's always a good thing to share for reference, since it's quick to capture, just in case anything noticeably off can be found in those.

I did some testing on different hardware for the texel offset:
RTX 3090 (Original Test Case): Afflicted
RTX 3080: Afflicted
GTX 1070: Afflicted
AMD R9 Fury X: Correct Behavior
So it seems to effect NVidia specifically, even across generations.
As for the performance, I made some bare minimum tests locally where I just loop the segmentation on a fixed image without touching the output so as to try and get as close to an apples to apples comparison as possible rather than comparing two differently constructed demos.
Legacy solution had the browser consuming 3.6% of the CPU and 33.3% of the GPU yielding about 180FPS.
The tasks vision solution used 1.9% of the CPU and 33.4% of the GPU yielding about 190FPS.
The new solution is showing clear benefits for CPU consumption.  The GPU usage is pretty close, though task manager doesn't seem to be great with giving exact GPU consumption.  I guess the performance of the new solution is fine.  I'm not sure if there are any optimizations that would invalidate a fixed image test, but I did provide an incrementing number for the time stamp.

Hi @Singulariteehee,
Could you please confirm whether you are still seeking a resolution to this issue, or if the matter has been resolved from your end?
Thank you!!

I tried again in the current latest version 0.10.12, and the problem is still there. I forced the task to allow regionOfInterest and then offset it by 1/144 vertically when detecting NVidia for the GPU, which partially solves the problem, but it further reveals a pattern of janky lines, about 1/8 horizontal lines are messed up creating jagged shapes in the results. When I remove the regionOfInterest hack, I can still see the 1/8 horizontal line pattern, but it is just less noticeable because the whole thing is off. I am limited in how much I can investigate because the WASM source and unobfuscated javascript are both still unavailable.