[SPARK-28621][SQL] Fix CheckCartesianProducts mismatch actual physical plan

What changes were proposed in this pull request?
Fix CheckCartesianProducts.isCartesianProduct so that

when left or right side table can broadcast, then do not raise Detected implicit cartesian product... exception. (because we will use broadcast nested loop join)
when left or right side table both cannot broadcast and join conditions do not include equi-condition, then raise Detected implicit cartesian product... exception.

How was this patch tested?
Unit test added.
Manual test by:
Providing
spark.range(2).createOrReplaceTempView("sm1") // can be broadcast
spark.range(50000000).createOrReplaceTempView("bg1") // cannot be broadcast
spark.range(60000000).createOrReplaceTempView("bg2") // cannot be broadcast

and suppose spark.sql.crossJoin.enabled=false
Test1
Run
spark.sql("select sm1.id, bg1.id from bg1 join sm1 where sm1.id < bg1.id").explain

Before:
Detected implicit cartesian product... exception raised.

Please review https://spark.apache.org/contributing.html before opening a pull request.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13741/
Test PASSed.

Test build #108655 has started for PR 25359 at commit c8f274d.

Test build #108655 has finished for PR 25359 at commit c8f274d.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108655/
Test FAILed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/13752/
Test PASSed.

Test build #108667 has started for PR 25359 at commit c48cc22.

Test build #108667 has finished for PR 25359 at commit c48cc22.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/108667/
Test FAILed.

See new PR https://github.com/apache/spark/pull/25520


[Server] Not available and not accessible

It seems your service is not available and not accessible.
C:\Users\Max\resend-php-example>php index.php
Error: cURL error 28: Failed to connect to api.resend.com port 443: Timed out (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for https://api.resend.com/emails

It seems your service is not available and not accessible inside Iran even with VPN.
Maybe this is because of AWS because AWS service is blocked here.
I tested the script on another server our of Iran and everything worked as expected.
Thanks.


Expo support

what about an implementation with nativewind for expo

We are using tailwindest on expo without any problems

We are using tailwindest on expo without any problems

great to know

We are using tailwindest on expo without any problems

any example of the code?

Sure.
Just follow the doc.
https://tailwindest.vercel.app/1-start/setup
Setup is same like in "normal web project".
Maybe you can share your problems.

I've been busy lately and hadn't checked it, but it's good to hear it's working! I'll test expo + nativewind today😀

nativewind and tailwindest work very well! Check out the example code and a screenshot of the execution results.
import { useState } from "react"
import { Text, TouchableOpacity, View } from "react-native"
import { wind, wind$ } from "tailwindest"

const container = wind({
    flex: "flex-1",
    display: "flex",
    flexDirection: "flex-col",
    gap: "gap-1",
    alignItems: "items-center",
    justifyContent: "justify-center",
    backgroundColor: "bg-teal-50",
}).class()

const button = wind$("success", "fail")(
    {
        display: "flex",
        alignItems: "items-center",
        justifyContent: "justify-center",
        padding: "p-3",
        borderRadius: "rounded-lg",
        border: "border-transparent border-solid",
        borderWidth: "border-2",
        ":active": {
            opacity: "active:opacity-70",
        },
    },
    {
        fail: {
            backgroundColor: "bg-red-500",
            borderColor: "border-red-100",
        },
        success: {
            backgroundColor: "bg-blue-500",
            borderColor: "border-blue-100",
        },
    }
)

export default function App() {
    const [count, setCount] = useState(0)
    return (
        <View className={container}>
            <Text className="font-bold text-2xl">Count is {count}</Text>
            <View className="flex flex-row gap-4">
                <TouchableOpacity
                    className={button.class("fail")}
                    onPress={() => setCount((c) => c + 1)}
                >
                    <Text className="text-white">Plus</Text>
                </TouchableOpacity>
                <TouchableOpacity
                    className={button.class("success")}
                    onPress={() => setCount((c) => c - 1)}
                >
                    <Text className="text-white">Minus</Text>
                </TouchableOpacity>
            </View>
        </View>
    )
}

Result of example code


Protect against https://www.drupal.org/project/drupal/issues/3013802

I have seen this issue quite a few times in custom code: $url->getRouteName() is called to check whether it's a certain entity route -- but if the url points to a since deleted entity then this bombs. It's nowhere evident you want to run $url->isRouted() && $url->getRouteName(). This should be a mild warning nothing like the world is burning if it's not there but it'd be nice to warn.

I think we need to add a few object types for PHPStan's type system. When we encounter Url::fromRoute we can call it a UrlRouted otherwise UrlUnrouted. Then whenever getRouteName is called, we can check the object type. If it's not UrlRouted via no or maybe trinary logic, we can return the error if isRouted hasn't been called. I think.

Problem is, you will likely hit something like $link_uri = Url::fromUri($paragraph->field_link->uri); -- the very problem is that you can't tell what that becomes...


Add an example of graceful shutdown when SIGINT (GPIO)

I’m new to Rust, and I’m really struggling to implement code that properly drops GPIO pins when Ctrl + C (SIGINT) is pressed. The documentation states that Rust doesn’t automatically call the drop method when a SIGINT signal is received. However, I would greatly appreciate an example of how to handle this situation.

Welcome to Rust @Eduardo-RFarias 😁 . There's an example in the examples folder that shows you how to handle signals using the simple-signals crate. Check out gpio_blinkled_signals.rs.
Hope that helps!


Looks great, lot's of potential, Chrome, Opera, Vivaldi?

Looks great, lot's of potential, Chrome, Opera, Vivaldi?
Any plans?

Because It's depending on Sidebar API of Firefox, There's no plan for now. :/

Wait, Opera has API for it...

Todo: check with https://github.com/mozilla/webextension-polyfill/
(after rewriting this addin #11 finishes)


Unable to fetch dashboard!

We were using apigility in our project before and it was working fine, after few composer update's , apigilty admin ui was showing a blank page.  After searching on github and so, we came to know that there were issues of zf-hal version, which got updated by composer update Anyways, we almost tired everything but we can not make it work, so I just removed all my packages and did a fresh, composer install , now I can see the apigilty ui but it is showing Unable to fetch dashboard!
Any help in this regard will be much appreciated.
Here is my composer.json
  "require": {
    "php": ">=5.5",
    "zendframework/zendframework": "~2.5",
    "zfcampus/zf-apigility": "~1.0",
    "doctrine/doctrine-orm-module": "~0.9.2",
    "radnan/rdn-upload": "2.*",
    "hybridauth/hybridauth": "dev-master as 2.5.1",
    "mobiledetect/mobiledetectlib": "^2.8",
    "zendframework/zendservice-twitter": "^2.1",
    "bjyoungblood/bjy-authorize": "1.4.*"

},
"require-dev": {
    "zfcampus/zf-apigility-admin": "~1.0",
    "zfcampus/zf-development-mode": "~2.0"
},

This repository has been closed and moved to laminas-api-tools/api-tools; a new issue has been opened at https://github.com/laminas-api-tools/api-tools/issues/16.


Testing panel can't run test files that contain doctests

Environment

Elixir & Erlang versions (elixir --version): Elixir 1.14.0 (compiled with Erlang/OTP 25)
Elixir Language Server version: Started ElixirLS v0.12.0 // ElixirLS built with elixir "1.11.4" on OTP "22"
Operating system: MacOS Ventura
Editor or IDE name (e.g. Emacs/VSCode): VSCode
Editor Plugin/LSP Client name and version: ??

Current behavior
I just today noticed that VSCode has a Testing panel in the sidebar, that seems to integrate with ElixirLS to be able to run my tests.

However, clicking the "run" triangle (or running the tests from the panel) hangs, with "tests in progress" icon.
The ElixirLS logs show an error -
[Trace - 6:30:13 PM] Received response 'workspace/executeCommand - (50)' in 16ms. Request failed: %MatchError{term: "doctest Y2015.Day01.part2/3 (6)"} (-32000).

(The doctests don't seem anything out of the ordinary - https://github.com/sevenseacat/advent_of_code/blob/main/lib/y2015/day01.ex )
This error happens even if I fully quantify the doctest line (ie. don't use the aliased form).
If I comment out the doctest line in the test file, then the "run" triangle appears for individual tests as well as the whole file, and the tests can be run successfully.

(I do have test lenses enabled, but these errors occur even when disabled - seems this testing panel is separate from that functionality)
Expected behavior
With the doctest line uncommented, individual tests from the file (or the whole file) should be able  to be run without error. Ideally there should be a "run" icon next to the doctest line too, to be able to run the doctests, but that might be too hard!

Fixed in https://github.com/elixir-lsp/elixir-ls/pull/800 and https://github.com/elixir-lsp/vscode-elixir-ls/pull/293


”Pardina” is listed in the drop-down menu

Description:
"Pardina" is listed in the drop-down menu alongside its corresponding county and commune, according to the law.
Precondition:
The website is up an running.

Step 1
Type "Pardina" in the search bar.

Expected results
The location is listed in the drop-down menu as "Comuna Pardina, TULCEA".


Cleanup metrics and logging for client lib

Add missing metrics
Remove un-necessary metrics

We need to do additional log cleanup, the debug logs that we emit can confuse the user. we need to hide all these logs.

This is done by:
https://github.com/uber-go/cadence-client/pull/197
https://github.com/uber-go/cadence-client/pull/200


Updates to legend tests

this PR building upon @kysolvik existing pr .
also doing a bit of function and readme cleanup as i go to clarify process!

letting CI build but if all builds well, this can be merged! all legend asserts are tested via this PR.


[0.5pt] Set up the project with Webpack and Jest- group task

Set up Gitflow
Set up webpack
Set up a JavaScript testing library (Jest)

This task is complete


CryptographicException when calling SignInManager.PasswordSiginAsync

Any idea why I get this error?
An unhandled exception occurred while processing the request.
CryptographicException: Key not valid for use in specified state.

Microsoft.AspNet.Security.DataProtection.Cng.DpapiSecretSerializerHelper.UnprotectWithDpapiImpl(Byte* pbProtectedData, UInt32 cbProtectedData, Byte* pbOptionalEntropy, UInt32 cbOptionalEntropy)

Stack
Query
Cookies
400 Headers
Environment
CryptographicException: Key not valid for use in specified state.

Variable 400  Value
Accept application/json, text/plain, */*
Accept-Encoding gzip, deflate
Accept-Language en-US,en;q=0.8
Connection keep-alive
400  Content-Length 387
Content-Type application/json;charset=UTF-8
Host localhost:8080
Origin http://localhost:8080
Referer http://localhost:8080/ 400
User-Agent Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.111 Safari/537.36

0

Dupe of https://github.com/aspnet/DataProtection/issues/51.


Update tailwindcss

Update tailwindcss, postcss, autoprefixer
Added tailwindcss/forms
removed default option from svelte-preprocessor as it's deprecated.

Thank you @Ak4zh for the PR 👍


the only third party applications can be used ?

thanks for the tool but we can use only the third party applications in the tool ? or we can use any application ?

@pretech86 You can use any APK that decompiles/recompiles successfully.


feat: add nusa:stat command for local development uses

This command mainly use while in development, to print the current stat of the whole data.
composer testbench nusa:stat

+------+----------------------------+-----------+-----------+----------+
| Code | Name                       | Regencies | Districts | Villages |
+------+----------------------------+-----------+-----------+----------+
| 11   | Aceh                       | 23        | 290       | 6500     |
| 12   | Sumatera Utara             | 33        | 455       | 6110     |
| 13   | Sumatera Barat             | 19        | 179       | 1265     |
| 14   | Riau                       | 12        | 172       | 1862     |
| 15   | Jambi                      | 11        | 144       | 1585     |
| 16   | Sumatera Selatan           | 17        | 241       | 3258     |
| 17   | Bengkulu                   | 10        | 129       | 1513     |
| 18   | Lampung                    | 15        | 229       | 2651     |
| 19   | Kepulauan Bangka Belitung  | 7         | 47        | 393      |
| 21   | Kepulauan Riau             | 7         | 80        | 418      |
| 31   | Dki Jakarta                | 6         | 44        | 267      |
| 32   | Jawa Barat                 | 27        | 627       | 5957     |
| 33   | Jawa Tengah                | 35        | 576       | 8563     |
| 34   | Daerah Istimewa Yogyakarta | 5         | 78        | 438      |
| 35   | Jawa Timur                 | 38        | 666       | 8494     |
| 36   | Banten                     | 8         | 155       | 1552     |
| 51   | Bali                       | 9         | 57        | 716      |
| 52   | Nusa Tenggara Barat        | 10        | 117       | 1166     |
| 53   | Nusa Tenggara Timur        | 22        | 315       | 3442     |
| 61   | Kalimantan Barat           | 14        | 174       | 2145     |
| 62   | Kalimantan Tengah          | 14        | 136       | 1571     |
| 63   | Kalimantan Selatan         | 13        | 156       | 2016     |
| 64   | Kalimantan Timur           | 10        | 105       | 1038     |
| 65   | Kalimantan Utara           | 5         | 55        | 482      |
| 71   | Sulawesi Utara             | 15        | 171       | 1839     |
| 72   | Sulawesi Tengah            | 13        | 175       | 2017     |
| 73   | Sulawesi Selatan           | 24        | 313       | 3058     |
| 74   | Sulawesi Tenggara          | 17        | 221       | 2287     |
| 75   | Gorontalo                  | 6         | 77        | 729      |
| 76   | Sulawesi Barat             | 6         | 69        | 648      |
| 81   | Maluku                     | 11        | 118       | 1235     |
| 82   | Maluku Utara               | 10        | 118       | 1185     |
| 91   | Papua                      | 9         | 105       | 999      |
| 92   | Papua Barat                | 13        | 218       | 1837     |
| 93   | Papua Selatan              | 4         | 82        | 690      |
| 94   | Papua Tengah               | 8         | 131       | 1208     |
| 95   | Papua Pegunungan           | 8         | 252       | 2627     |
+------+----------------------------+-----------+-----------+----------+

The command will give you the current number of regencies, districts and villages on each province. Optionally you can pass --diff option whether any changes in the main database after tests ran. The --diff option should look like these.
composer testbench nusa:stat -- --diff

Changes
+------+----------------------------+-----------+-----------+----------+
| Code | Name                       | Regencies | Districts | Villages |
+------+----------------------------+-----------+-----------+----------+
| 81   | Maluku                     | 11        | 119       | 1245     |
| 82   | Maluku Utara               | 10        | 129       | 1195     |
+------+----------------------------+-----------+-----------+----------+

The main goals is to provide summary and reports whether there's a changes on the main nusa' database in every pull request or not. Even better if we could enable auto comment on every changes made by a pull request.
Notable changes

[x] There's indeed some changes in regencies from upstream
[x] Show current province code on its attribute test
[x] Add pint.json config to exclude submodules directory

This is odd,
I was expecting the tests should be failed due to there's some issue in the upstream https://github.com/cahyadsn/wilayah/pull/49 🤔


Take Bugreport does not with without modifications

The current Take Bugreport script bundled with the app is as follows:
#!/bin/bash
declare -a arr
thisdir=$1 # $1 is the bundle resources path directly from the calling script file
serial=$2 #
adb=$thisdir/adb

# --------------------
#
# Add your script below. When sending adb commands to the user-selected device, use "$adb -s $serial"
#
# --------------------

TakeBugReport(){
	ldap=$(whoami)
	now=$(date +"%m-%d-%Y-%H-%M-%S")
	devicename=$($adb -s $serial shell getprop ro.product.name)
	finalFilename=$devicename-$ldap-$now.png
	finalFilename="${finalFilename//[$'\t\r\n ']}"

	$adb -s $serial bugreport > $finalFilename".txt"
	}

mkdir -p ~/Desktop/bugreport
cd ~/Desktop/AndroidTool
TakeBugReport
open . #opens the Android Tool folder in Finder after executing. Could be annoying

Out of the box, this does not work for any device. One of the following two modifications has to be made, either:

Manually create ~/Desktop/AndroidTool so the script has a destination to enter
Change cd ~/Desktop/AndroidTool to cd ~/Desktop/bugreport so the output is placed in the created directory.

I believe option 2 was probably the intended purpose, but it's not clear why the script assumes that ~/Desktop/AndroidTool/ exists on the machine (it is is not created, nor part of the setup instructions).

ah - thanks, good catch. "Bugreport" was an early code name for the app

Committed for next release


Can I train roBERTa on my dataset of sentences in order to find out the most similar sentences compared to a custom sentence?

Can I train roBERTa on my dataset of sentences in order to find out the most similar sentences compared to a custom sentence?
If so then how can I approach that?
10x in advance.

@chamecall RoBERTa is basically a sentence encoder that you can use to get good vector representation for any sentence.
Please look at STS-B task from GLUE and released roberta glue section. That task is about predicitng sentence similarity. So you can use the same loss and setup as that task for finetuning RoBERTa on your task.


non ASCII character

It's not directly a bug in HUE.
I'm using a tool that read the file as ASCII, not UTF8, in order to modify the config file for deployment automation.
It fails because of non ASCII character at that line:
https://github.com/cloudera/hue/blob/f30e9f75011f777458873fbc4c807bd2d100a4cb/desktop/conf/pseudo-distributed.ini.tmpl#L109
"Double quotes" are not standard.
Since other "double quotes" are standard in the file, I suggest to avoid non ASCII character in that file.

Thanks!
It's gonna be pushed to master soon: https://review.cloudera.org/r/11385/bugs/HUE-7139/


Warning: NaN is an invalid value for the width css style property.

Issue Type

[x] Bug report
[ ] Feature request
[ ] Question / support request
[ ] Other

Description
Hi. I have a Docusaurus website that is using this project with ThemedImage. When switching themes (dark - lite), we get the following error:
react-dom.development.js?ac89:67 Warning: `NaN` is an invalid value for the `width` css style property.
    at img
    at div
    at dialog
    at div
    at ControlledBase (webpack-internal:///./node_modules/react-medium-image-zoom/dist/index.js:350:9)
    at Controlled
    at Uncontrolled (webpack-internal:///./node_modules/react-medium-image-zoom/dist/index.js:649:84)
...

I have seen #357, and indeed it seems like ThemedImage is using display: none (source)., but upgrading to the latest version does not seem to help. This is tested using v5.1.1.
Maybe worth noting that it was working fine on v4.4.3.
Appreciate your help.

Here is a code sample from my project:
Usage:
import ThemedImage from '@theme/ThemedImage';
import useBaseUrl from '@docusaurus/useBaseUrl';
import Zoom from "react-medium-image-zoom";

...

<Zoom>
	<ThemedImage sources={{
	  light: useBaseUrl('/img/architecture-light.svg'),
	  dark: useBaseUrl('/img/architecture-dark.svg'),
	}} alt="architecture"/>
</Zoom>

Hi, @nirhaas! I'm sorry you're having trouble. I should be able to address this tonight or tomorrow night given I have enough information here. Stay tuned!

Okay, I've been able to reproduce this, and I think it directly has to do with SVGs.
I'll need some time to figure it out. Thanks for reporting this!

Have any solution been found yet? I am getting the same error right now in my app.

@arthureberle I haven't fixed it yet. I'll think about it some more

I am having this issue as well. It seems to only happen on some of our pages that use <Zoom> https://preview.pousette-dartfoundation.org/works/head-of-a-woman/

Is it possible that the file size of some of the images is too large?
Should I try to wait until the image is fully loaded using onLoadingComplete before attempting to apply the Zoom?

I'll try to fix this over the weekend; I know it's annoying, y'all. @jeremyzilar It looks like you're using a .webp image (good on ya), so I'll use that one and an SVG without dimensions in my testing.

I've found that for me it crashes when in the same page I have this component + a react-bootstrap Modal component. Once I open the latter - I see the same error in the console.
Is there a temporary workaround for this?

Could fix it now by myself. The error occurred in my project because i had image components which are rendered differently on desktop and mobile. On Desktop i have used this zoom package and on mobile it was displayed as a slider. Even though the zoom component was not rendered into the DOM, it somehow was looking for a width value.
My previous way to hide the components was with media queries through tailwindcss:

            <SliderGallery images={product.images} /> // Mobile

            <ZoomGallery images={product.images} /> // Desktop

This led to the error above. I have now switched to a use-hook called useWindowSize (which can be found on the usehooks-ts page) and a simple if then and the error dissappeared.

I know I still need to fix this. We were dealing with floods and a cyclone in New Zealand, and I have other open source projects, too.

This warning is happening in 5.1.3 release for png files too:
<Zoom zoomMargin={8}>
  <Image
    src="https://picsum.photos/600/800"
    alt="Sample billing statement"
    width="200"
  />
</Zoom>

Alright, nobody has submitted a PR, so this one's time has come: I'm not doing other OSS work until y'all are taken care of with this issue. TBD on a fix timeline, but here we go...

Ok, I think I got it. Can y'all test this potential fix by installing<EMAIL_ADDRESS>and seeing if that resolves your issue? If so, I can bundle this and another issue and cut a release for v5.1.4 tomorrow.
Here's the PR: https://github.com/rpearce/react-medium-image-zoom/pull/404

Can y'all please 🙏 try this fix out? npm i<EMAIL_ADDRESS>


Instructions and examples of randomized questionnaires

Under the questionnaires modules, there could be a new chapter that describes randomized questionnaires in detail with examples.
There are two different types of randomization for questionnaires:

the pick-randomly option of the questionnaire RST directive, and
the randomized option of the pick-any RST directive used under questionnaires.

A-plus-rst-tools README desribes the options and the additional related options too.
https://github.com/apluslms/a-plus-rst-tools/blob/master/README.md#2-graded-questionnaire
In the new Aplus manual chapter, it would be important to also explain how the system makes random sampling and what affects it. Teachers may break the sampling for existing student submissions if they modify the question after releasing it. This may be particularly problematic if the existing submissions are automatically regraded after the question has been changed.

Concerning the random sampling and how it changes when the teacher modifies the question afterwards, here are comments adapted from an email to a teacher. The teacher had modified the correct choices in a randomized pick-any question after some students had already submitted. This led to confusion when the old submissions were automatically regraded and some of them were moved to the "rejected" status.
In a randomized checkbox question, the random sampling is affected by the number of choices (checkboxes) and also by the correct checkboxes. If you change the set of correct checkboxes after releasing the questionnaire to the students, it is possible that the sampling changes for the existing submissions (that were submitted before the correct choices were changed). Thus, the student answered the question with one sampling (a set of the choices) and when the submission is regraded after modifying the correct choices, the grading uses a different sampling than what the student was originally given. Therefore, the grading results after regrading may look very confusing. After regrading, the rendered feedback will show choices that match the new sampling, but that is not what the student originally saw.
Regrading (after modifying the question) may set the submission to the "rejected" status if the submitted answer contains choices that are not included in the new sample. The submission becomes rejected because the input is considered invalid against the new sample.
In the submission details in the inspect submission page, you can see the original sample used when the student answered the questionnaire.
If you set "preserve-questions-between-attempts" in the RST questionnaire, the sampling does not change after submissions. But the sampling may still change if you modify the question choices and correct choices.
At any rate, if the student reloads the assignment page after the teacher has made the changes in the question, then the student sees the new version of the assignment and can answer normally. In randomized questionnaires, the questionnaire is always loaded "fresh". You may have seen that in normal questionnaires, the feedback of the previous submission is shown in the place of the questionnaire for students, but in randomized questionnaires, the assignment page always loads the "clean, fresh" assignment without signs of what was previously submitted. This is good since the student gets a questionnaire with the new choice sampling. (Randomized questionnaires include hidden checksums, which is why the previous rendered feedback HTML may not be used as a form for the new submissions; a new, "clean" form is needed.)
Internal ticket from the teacher:
https://rt.cs.aalto.fi/Ticket/Display.html?id=24616

This function in the MOOC-Grader takes care of the random sampling for questionnaires.
https://github.com/apluslms/mooc-grader/blob/10051cd7f9c021e2b5b05ef541891eb7e851ad66/access/types/forms.py#L386


[AKS] Add Etags in AKS CLI

Related command

Description

Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

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

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Thank you for your contribution! We will review the pull request and get back to you soon.

Queued live test to validate the change.

test_aks_nodepool_create_scale_delete
test_aks_upgrade_upgrade_settings

Requeued live test

Queued live test to validate the change.

test_aks_nodepool_create_scale_delete
test_aks_upgrade_upgrade_settings

Requeued live test

case test_aks_nodepool_create_scale_delete failed with following error

E           azure.core.exceptions.HttpResponseError: (PreconditionFailed) Resource not found but ETag header is provided. If this is a request to create, please do not provide ETag.
E           Code: PreconditionFailed
E           Message: Resource not found but ETag header is provided. If this is a request to create, please do not provide ETag.

@InduSridhar please resolve the conflicts and update the PR title according to the guidance https://github.com/Azure/azure-cli/tree/dev/doc/authoring_command_modules#format-pr-title

/azp run

/azp run

/azp run

/azp run

https://dev.azure.com/azclitools/public/_build/results?buildId=210053&view=logs&j=4e4d232d-230a-55c9-0730-4c1a9c36b9e5&t=6d1bdb99-245b-5117-da18-01d8df6f72c0&l=1868

FAILED src/azure-cli/azure/cli/command_modules/acs/tests/hybrid_2020_09_01/test_aks_commands.py::AzureKubernetesServiceScenarioTest::test_aks_create_default_setting
FAILED src/azure-cli/azure/cli/command_modules/acs/tests/hybrid_2020_09_01/test_aks_commands.py::AzureKubernetesServiceScenarioTest::test_aks_nodepool_create_scale_delete
FAILED src/azure-cli/azure/cli/command_modules/acs/tests/hybrid_2020_09_01/test_aks_commands.py::AzureKubernetesServiceScenarioTest::test_aks_upgrade_node_image_only_cluster
FAILED src/azure-cli/azure/cli/command_modules/acs/tests/hybrid_2020_09_01/test_aks_commands.py::AzureKubernetesServiceScenarioTest::test_aks_upgrade_node_image_only_nodepool

https://dev.azure.com/azclitools/public/_build/results?buildId=210053&view=logs&j=c4905e22-e505-5bfe-aa0a-49d3f9325fa2&t=cf247c3b-aad8-52b9-12ca-ceb3e5942fcf&l=3571

FAILED src/azure-cli/azure/cli/command_modules/acs/tests/latest/test_agentpool_decorator.py::AKSAgentPoolContextCommonTestCase::test_get_if_match
FAILED src/azure-cli/azure/cli/command_modules/acs/tests/latest/test_agentpool_decorator.py::AKSAgentPoolContextCommonTestCase::test_get_if_none_match
FAILED src/azure-cli/azure/cli/command_modules/acs/tests/latest/test_agentpool_decorator.py::AKSAgentPoolContextStandaloneModeTestCase::test_get_if_match
FAILED src/azure-cli/azure/cli/command_modules/acs/tests/latest/test_agentpool_decorator.py::AKSAgentPoolContextStandaloneModeTestCase::test_get_if_none_match
FAILED src/azure-cli/azure/cli/command_modules/acs/tests/latest/test_agentpool_decorator.py::AKSAgentPoolContextManagedClusterModeTestCase::test_get_if_match
FAILED src/azure-cli/azure/cli/command_modules/acs/tests/latest/test_agentpool_decorator.py::AKSAgentPoolContextManagedClusterModeTestCase::test_get_if_none_match
FAILED src/azure-cli/azure/cli/command_modules/acs/tests/latest/test_agentpool_decorator.py::AKSAgentPoolAddDecoratorStandaloneModeTestCase::test_add_agentpool
FAILED src/azure-cli/azure/cli/command_modules/acs/tests/latest/test_agentpool_decorator.py::AKSAgentPoolUpdateDecoratorStandaloneModeTestCase::test_update_agentpool

/azp run

/azp run

/azp run

/azp run

/azp run

/azp run

/azp run

please add the changelog to History Notes section with impacted command/parameter, i.e.,
[AKS] az aks xxx: Add parameters --if-match and --if-none-match to support {xxx function}
...


Fix native lazyloading detection

Currently the Native Lazyloading detection is broken (at least on 84.0.4147.125).
When running previous implementation of
typeof HTMLImageElement === "object" && HTMLImageElement.prototype.loading;

It results in false. This is at least in part due to typeof HTMLImageElement resulting in "function".
I have copied the implementation from the polyfill for loading attribute, here: https://github.com/mfranzke/loading-attribute-polyfill/blob/master/loading-attribute-polyfill.js

Is anyone able to review this PR? It would be great to have native lazyloading working as intended with this library

Hey @taijuten , your PR hasn't gone unnoticed, we are however in the process of taking a closer at this area, to make it a better fit for our future plans.
We appreciate the importance of this feature to you, and your patience.

@taijuten Please see the comment of your original issue - at this point we will not add new functionality to the this project.


Sometimes, clicking on the map selects a seemingly random province

"Sometimes province selection selects a province even though you clearly clicked outside of any province. I think it might have something to do with zooming in/out"

When you zoom out in a way that would normally make the camera out of bounds (but then the camera's built-in limit properties prevent it),
I think the code that checks inputs for province selection has incorrect information on the camera's position


v0.3.2

Added features, updated tests and docs.
New Features

view_crystal : use Blink, Pluto, or Jupyter to render a crystal in an interactive GUI
calculate_bond_vectors! : determines Cartesian vectors between bonded atoms (included in infer_bonds!)
get_bond_vector : retrieves the vector between two atoms
clear_vectors! : removes all vector annotations (included in remove_bonds!)
bond_angle : calculates the angle between two adjacent bonds
bond_distance : retrieves the distance annotation for an edge (without requiring using MetaGraphs)

Codecov Report

Merging #87 (33000db) into master (f2992d1) will increase coverage by 0.15%.
The diff coverage is 93.22%.

@@            Coverage Diff             @@
##           master      #87      +/-   ##
==========================================
+ Coverage   95.76%   95.91%   +0.15%
==========================================
  Files           9        9
  Lines         920      979      +59
==========================================
+ Hits          881      939      +58
- Misses         39       40       +1

Impacted Files
Coverage Δ

src/Xtals.jl
100.00% <ø> (ø)

src/misc.jl
97.64% <81.81%> (-2.36%)
:arrow_down:

src/bonds.jl
96.63% <95.83%> (+1.63%)
: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 f2992d1...33000db. Read the comment docs.


Gatsby fails in headless folder with various errors

Description
Running gatsby develop in the headless-front-end/gatsby folder fails with a bunch of errors, starting with this:
Cannot query field "allCraftBlogBlogEntry" on type "Query".

This is followed by these errors:
Unknown type "Craft_bodyContent_richText_BlockType".
Unknown type "Craft_bodyContent_quote_BlockType".
Unknown type "Craft_uploads_Asset".
Unknown type "Craft_bodyContent_imageCarousel_BlockType".
Unknown type "Craft_uploads_Asset".
Unknown type "Craft_bodyContent_embed_BlockType".

This is running Gatsby in Windows 10, with Craft running in Homestead.
Steps to reproduce

Follow steps to install the Starter Blog in the README
cd to headless-front-end/gatsby folder and type gatsby develop

Additional info

OS: Windows 10

Craft version: <IP_ADDRESS>

PHP version: 7.4

Database driver & version: MySQL driver (MariaDB 10.4.12)

Plugins & versions:
Craft plugins:
Asset Rev: 6.0.2
Gatsby Helper: dev-master
Redactor: 2.8.3
Typogrify: 1.1.18
oEmbed: 1.3.6
npm packages:
gatsby: ^2.25.3,
gatsby-image: ^2.4.21,
gatsby-plugin-manifest: ^2.5.2,
gatsby-plugin-offline: ^2.2.7,
gatsby-plugin-react-helmet: ^3.3.13,
gatsby-plugin-sass: ^2.4.2,
gatsby-plugin-sharp: ^2.7.1,
gatsby-source-craft: ^1.0.0-beta.1,
gatsby-source-filesystem: ^2.4.1,
gatsby-transformer-sharp: ^2.5.17,
nuka-carousel: ^4.7.1,
prop-types: ^15.7.2,
react: ^16.13.1,
react-dom: ^16.13.1,
react-helmet: ^5.2.1,
snyk: ^1.424.4

Sorry @sijones-uk, looks like this project’s Gatsby readme needs updating.
The configuration is slightly different using the just-released plugins: https://github.com/craftcms/gatsby-source-craft#quick-start
Guessing the tl;dr is update your environment variable names...
CRAFTGQL_TOKEN=your-graphql-token
CRAFTGQL_URL=https://your-craftcms-site.test/api

...and enable Allow discovery of sourcing data for Gatsby for your schema after the Gatsby Helper is installed if you’ve not already done that.
Can you let me know if that does it?

Unfortunately, I'm still getting the same errors. I'd already create a .env with the CRAFTGQL_TOKEN and CRAFTGQL_URL variables in (I also tried changing the filename to .env.development as per the Gatsby documentation, without any success). I tried regenerating the token to be certain it wasn't that, and it didn't make any difference. (I set the CRAFTGQL_TOKEN env value to the token from Craft minus the Authorization: Bearer part.). I'd already enabled Allow discovery of sourcing data for Gatsby for my schema.
Could it be anything to do with the version of Gatsby? I'm using version 2.25.3.

Could it be anything to do with the version of Gatsby? I'm using version 2.25.3.

Shouldn’t be; that’s what this project is using and I’m running it locally just fine.

Can you successfully query Craft’s GraphQL API directly using GraphQL Playground or Insomnia or a third-party client?
If so, have you also added homepage content and a few test blog posts?

The errors you listed are what I’m used to seeing when the GraphQL connection is busted and nothing is sourced from the Craft site—are those preceded by anything else revealing?

Yes, I've got home page content and two blog posts. I've tested the Craft Blog API endpoint using Postman with the following simple query:
query MyQuery {
  entries {
    id
    title
  }
}

This produced the expected output:
{
    "data": {
        "entries": [
            {
                "id": "53",
                "title": "Another blog entry"
            },
            {
                "id": "39",
                "title": "My new blog post"
            },
            {
                "id": "1",
                "title": "About"
            },
            {
                "id": "3",
                "title": "Home"
            }
        ]
    }
}

The output from gatsby develop starts like this:
error There was an error in your GraphQL query:

Cannot query field "allCraftBlogBlogEntry" on type "Query".

If you don't expect "allCraftBlogBlogEntry" to exist on the type "Query" it is most likely a typo.
However, if you expect "allCraftBlogBlogEntry" to exist there are a couple of solutions to common problems:

- If you added a new data source and/or changed something inside gatsby-node.js/gatsby-config.js, please try a restart of your development server
- The field might be accessible in another subfield, please try your query in GraphiQL and use the GraphiQL explorer to see which fields you can query and what shape they have
- You want to optionally use your field "allCraftBlogBlogEntry" and right now it is not used anywhere. Therefore Gatsby can't infer the type and add it to the GraphQL schema. A quick fix is to add at least one entry with that field ("dummy content")

It is recommended to explicitly type your GraphQL schema if you want to use optional fields. This way you don't have to add the mentioned "dummy content". Visit our docs to learn how you can define the schema for "Query":
https://www.gatsbyjs.org/docs/schema-customization/#creating-type-definitions
error "gatsby-node.js" threw an error while running the createPages lifecycle:

Cannot query field "allCraftBlogBlogEntry" on type "Query".

[...]

It looks like everything’s right. If you haven’t already, be sure to run gatsby clean and try building again to rule out a cache problem. (I’m reaching here, but that could also be it 🤞.)

I've found the cause of this issue: Gatsby wasn't liking my self-signed certificate. When I changed the CRAFTGQL_URL to use http instead, the above errors stopped. I'm now getting a different error, essentially the same as the issue reported here (but unlike that issue, I've already got content in the site, so that wasn't the cause):
error "gatsby-source-craft" threw an error while running the sourceNodes lifecycle:

Variable "$id" is not defined

  379 |     if (remoteConfigVersion !== localConfigVersion || !localContentUpdateTime) {
  380 |         reporter.info("Cached content is unavailable or outdated, sourcing _all_ nodes.");
> 381 |         await sourceAllNodes(config);
      |         ^
  382 |     }
  383 |     else {
  384 |         reporter.info(`Craft config version has not changed since last sourcing. Checking for content changes since "${localContentUpdateTime}".`);

Make sure that you don't have a typo somewhere and use valid arguments in sourceNodes lifecycle.
Learn more about sourceNodes here: https://www.gatsbyjs.org/docs/node-apis/#sourceNodes

I'm assuming this isn't related to the Starter Blog specifically, so will need to open a new issue in the Gatsby source plugin repo?

That looks like the error you’d get when your GraphQL schema isn’t configured correctly on the Craft end. With the Starter Blog it can happen if you’ve not added entries or content, and I saw the same thing testing earlier when I forgot to enable Users for said schema.
Make sure your schema’s sufficiently permissive, has that Allow discovery of sourcing data for Gatsby option enabled, and that you’ve run gatsby clean before trying gatsby develop again. I apologize if I sound like a broken record, but it seems as though some environmental setting or configuration is not right.

I saw the same thing testing earlier when I forgot to enable Users for said schema

That was it - thank you! I hadn't checked the "View all users" box in my schema because the Gatsby components and pages aren't outputting any user info. Do you know why it fails when that box is unchecked?

Aha! I’m glad you’ve got it working. Every entry has an author, which is of course a user. I’ll let @andris-sevcenko decide what to do with this information.

Actually nevermind—that bug’s been fixed for the next upcoming Gatsby Helper release. Closing this out!


update googleapis

googleapis: 699616e026ae26a00c20adecbdf08c40d92bd1fe
protobuf: v3.4.0

cla/google seems to be blocking this merge. Do we know what's going on here...? :cry:


HTML5 platform doesn't work after 0.76.1

Home Assistant release with the issue:

0.76.1
Last working Home Assistant release (if known):
0.75.1
Operating environment (Hass.io/Docker/Windows/etc.):

Component/platform:

Description of problem:
the trigger that fixed in issue #16063 doesn't do anything , it only switch to on , i have tried with PC and Android
also tried to delete the old html5 file and the HA didn't create a new file when i turned the switch to ON.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

Are there any errors in the logs about this?  Does it work if you revert to 0.76 or 0.75.3?

there is no error in the logs , in the 0.76 there was a different problem when the toggle didn't work.
i didn't tried to revert to 0.75.3

Personally I always revert to ensure the issue is not related to anything else.

I can agree on that, but i am not the only one with the same issue

There was an issue when we move this page to profile, @balloob said he fixed, but looks like not.

Ok so this issue is related to auth then.  Good to know for those of us that are not using auth.

It looks like I have a similar problem - seeing 404 on HA webpage after updating to 0.76.1 See full comments at https://community.home-assistant.io/t/error-during-setup-of-component-auth/63393 (sorry - I put it there first)

@Mikeinnc your problem is totally different, home-assistant needs aiohttp==3.3.2, you cannot downgrade it. If you really installed home-assistant in its own virtual environment, it should not affect other application, you need double check it.
Please do not piggy-back, use forum or chat channel for support.

Yes, sorry about that. I had already written my comments in the other area - thought it might have been easier to link to them than write again! Obviously not.... :-(
I'm definitely installed in a virtual environment - that is the recommended approach, I understand, for my Pi environment, and it has been working flawlessly for - well, a very long time! This is the first time I have seen an upgrade 'break' it. I suppose the good news is that I have downgraded back to 0.75.3 and that appears to be working perfectly. Hope that gives a clue as to what is broken in 0.76.x?


add length in the datapack to support masking

#445

Codecov Report

Merging #462 into 2.0 will not change coverage.
The diff coverage is 100%.

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


docs: RHIDP-1472 Adding GitLab OAuth as an authentication provider

Fixes #RHIDP-1472
Content borrowed from:

https://backstage.io/docs/auth/gitlab/provider
https://backstage.io/docs/auth/#sign-in-configuration

The assembly that will integrate the content into the complete documentation will be available in a further pull request

Is enabling GitLab auth specific to deploying RHDH on OCP with the Operator? If not, we should consider a different location for this content. What about creating an Enabling Authentication Providers chapter / assembly that contains the sub-sections for each provider (GitHub, GitLab, etc.)?

@linfraze I haven't tested with a Helm chart deployment. I believe the scenario is always the same, on Kubernetes as on OpenShift: you configure the app via a config map, and optionally, secrets. Using Kubernetes/OpenShift Secrets for secrets is a good practice that we should promote.
The difference between Helm-based and Operator-based deployments, is the options at hand to configure the config map and the secrets.
With an Operator-based installation, we already have this: https://access.redhat.com/documentation/en-us/red_hat_developer_hub/1.1/html/administration_guide_for_red_hat_developer_hub/proc-install-rhdh-operator_admin-rhdh#configuring-the-developer-hub-custom-resource
With a Helm-based installation, we are not convered yet. One option is to configure the Helm charts before deploying them. I believe you can also edit the config map.

@riginoommen @kadel I updated the procedure to  1. add secrets. 2. center more around the config map. I tested on an OpenShift Local Operator-based deployment. Is it OK now?

@themr0c the current location of this content pigeon-holes it to a specific platform and method, which might not be necessary or accurate. As previously discussed, I think the best structure for this content is to create an Enabling Authentication Providers section (assembly) and nest each of the individual auth provider sections (GitHub, GitLab, etc.) in that assembly. This structure also follows modularity best practices, which will allow us to easily convert the Enabling Authentication Providers section into its own title in the future, if we want to.
Another issue is that the GitHub auth section is already published as its own section in the Getting Started guide (intentionally for modularity) and all authentication provider sections should be in the same place. Ideally in the Enabling Authentication Providers section, which is already planned and may be in progress.
What are your thoughts on structuring the authentication content that way?

My take on this is that we have started all of this in parallel:

To organize the assembly: https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/81. We might want to finalize this first for clarity. The current content that we know is going in each procedure helps us to mature this.

A PR for each procedure module: https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/78, https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/82, https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/83, https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/85.

Current PR used to develop the structure for the content that should go for each provider.
Currently added the modules in a temporary place, to render the module in the preview. Add the modules in the final place once https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/81 is merged.
TODO: Clarity on the helm vs. operator configuration method. We might need a new Jira for this, and finalize this Jira first.

Content of the page (configuration steps) looks good. As @linfraze pointed out the placement of this page is wrong. It should not be under Operator installation. Better would be to have a separate section for all auth providers, something like "Enabling Authentication Providers"
If you want to handle that separately that is your call.
/lgtm

If you want to handle that separately, that is your call.

and I guess there is https://github.com/redhat-developer/red-hat-developers-documentation-rhdh/pull/81 for that :-)

@kadel Indeed, let's follow the official syntax: <1>. See https://docs.asciidoctor.org/asciidoc/latest/verbatim/callouts/

Ready for QE and peer review.


Cannot select launch target in quick pick

I have the following launch configurations

When I try to switch to the tslint-server launch configuration from the picker that is shown when clicking the debug status bar item

Then quick pick is shown, but selecting the Attach to Server launch config has no effect

I can reproduce this with latest insiders. Not with stable -> November


Failed to show Schema Registry

Describe the bug

When I click to Schema Registry, I got the error as below:

Maybe I have a subject with name "google/protobuf/any.proto" in my schema registry and that is causes of error
Set up

I used Helm chart to install Kafka-UI

Hi, thanks for reporting the issue!
This is a known issue (#1995), unfortunately we haven't fixed it yet. Feel free to subscribe/upvote the original issue. Stay tuned!


Adding batch image processing to Vision API

The amount of data that Vision can return can be pretty deep and processing more than one image at a time adds another level to that.
Here's my proposed approach to work with multiple images with multiple feature types.
        >>> images = client.batch()
        >>> for i in range(10):
        ...     images.add_image(client.image(source_uri='gs://%s.jpg' % (i,)))
        >>> images.detect_faces()
        {'0.jpg': [], '1.jpg': [],}
        >>>
        >>> # With multiple feature types.
        >>> features = [Feature(FeatureTypes.FACE_DETECTION, 5),
        ...             Feature(FeatureTypes.LOGO_DETECTION, 3)]
        >>> for i in range(10):
        ...     image = client.image(source_uri='gs://%s.jpg' % (i,))
        ...     images.add_image(image=image, features=features)
        >>> images.detect()

With a context manager it could look something like this...
        >>> features = [Feature(FeatureTypes.FACE_DETECTION, 5),
        ...             Feature(FeatureTypes.LOGO_DETECTION, 3)]
        >>> with client.images() as images:
        ...     for i in range(10):
        ...         image = client.image(source_uri='gs://%s.jpg' % (i,))
        ...         images.add_image(image=image, features=features)
        ...     results = images.detect()

So client.images() is like a batch? Why not name it as such? What is the equivalent backend method that you'd be using? (Or would you just be sending N requests?)

It will actually be one request with N vision requests so I could change it to batch().
The GAPIC method is called batch_annotate_images.

SGTM. As for the interface of the batch, you should check out the datastore batch / accompanying docs. It commits on __exit__, but we also document an explicit public interface people can use to add mutations to the batch and to manually commit or rollback the batch (rollback is datastore transaction specific).

I definitely like having the context manager be "sugar" over an explicit imperative surface.

Is there a benefit to running batch if we are asking for the same feature. Would I expect performance increase by running batch versus looping through N requests?

@bw4sz yes, batching only makes one large request rather than multiple smaller requests, so it should be faster.
See: https://cloud.google.com/vision/docs/reference/rpc/google.cloud.vision.v1#google.cloud.vision.v1.ImageAnnotator.BatchAnnotateImages

Is there a limit to the batch size, I was batching 600 images and i got a
timeout error, no problem sending them individually. Optimal chunking size?
On Fri, Jun 16, 2017 at 11:46 AM, Thomas Schultz<EMAIL_ADDRESS>wrote:

@bw4sz https://github.com/bw4sz yes, batching only makes one large
request rather than multiple smaller requests, so it should be faster.
See: https://cloud.google.com/vision/docs/reference/rpc/
google.cloud.vision.v1#google.cloud.vision.v1.ImageAnnotator.
BatchAnnotateImages
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/google-cloud-python/issues/2897#issuecomment-309105086,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABJwrOUCgnD9relVnJ-bWmFmRXaWgSjtks5sEs2YgaJpZM4LTYWA
.

--
Ben Weinstein, Ph.D.
Postdoctoral Fellow
Oregon State University
http://benweinstein.weebly.com/

It looks like the max number of images per request(which may be a soft limit?) is 16.
@lukesneeringer could probably confirm this for you though.

the limit is 100 per request.


Issue reading some imzML files

I am trying to read an imzML file using this fuction:
def getspectrum(self, index):
mz_bytes, intensity_bytes = self.get_spectrum_as_string(index)
mz_array = np.frombuffer(mz_bytes, dtype=self.mzPrecision)
intensity_array = np.frombuffer(intensity_bytes, dtype=self.intensityPrecision)
return mz_array, intensity_array
I get this error:
ValueError: buffer size must be a multiple of element size
The pixel that is not able to read has different lengths for mz and intensities, i.e.  len(mz_bytes) > len(intensity_bytes)

Hi @aryre, it seems like you described the problem correctly and our error message was informative, that your .ibd file is corrupted, and that the spectrum has more intensity values than m/z values.

@aryre before you try fixing the issue I'd suggest to look into the problem and narrow it down, why do you have the different numbers of the m/z values and intensities?


Support for Go To Definition, Rename Symbol and other IDE features

Thanks for your amazing work on this library! I'm a big fan of the approach you have taken with Zod of defining a type's schema only once rather than duplicatively for each type and its parser.
The one major downside I have found with using Zod for declaring types is that Visual Studio Code (and I assume the TypeScript language server more generally) does not seem to be able to connect usages of object properties back to their declaration in z.object.
For example, consider the following code:
const Example = z.object({ property: z.string() });

type Example = z.infer<typeof Example>;

const instance: Example = { property: "value" };

Using any language server action like Go To Definition, Find Usages or Rename Symbol on Example["property"] does not work. This is a particular pain point for Rename Symbol, which is incredibly useful when working on a large code base.
I assume this is a limitation of the Typescript language server given the specific type-level programming that Zod is using. However, these features do appear to work with io-ts (a library that takes a similar approach), which makes me think it may be possible to implement Zod's type mappings in a way that preserves these IDE features, at least for some scenarios.
Is this a valuable goal to pursue, or have I misunderstood how most people are using Zod?
Digging a little deeper, TypeScript does not appear to be able to connect the properties in an object to those same properties in its associated mapped type if the keys are changed.  This appears to be what is causing the IDE features to not work. For example, consider a simplified version of the return type of objectType in Zod:
type optionalKeys<T extends object> = {
    [k in keyof T]: k;
}[keyof T];

type requiredKeys<T extends object> = {
    [k in keyof T]: undefined extends T[k] ? never : k;
}[keyof T];

export type addQuestionMarks<T extends object> = {
    [k in optionalKeys<T>]?: T[k];
} & {
    [k in requiredKeys<T>]: T[k];
};

export type mergeIntersections<T extends object> = { [K in keyof T]: T[K] };

type Example2 = { property: string; optionalProperty: string | undefined };

const instance2: mergeIntersections<addQuestionMarks<Example2>> = { property: "" };

// type Instance2 = {
//    property: string;
//    optionalProperty?: string | undefined;
// }
type Instance2 = typeof instance2;

This code is responsible for making schemas marked with .optional() optional (rather than just undefined) in the final object type. The addQuestionMarks type is transforming the keys in T using optionalKeys and requiredKeys. Due to these transformations of the keys of T, TypeScript can no longer connect the original type's keys to the mapped type's keys. As a result, using Go To Definition on property on the line starting with const instance2 does not work.
However, I believe we can get the same outcome in a way that preserves the IDE features:
export type addQuestionMarksPreserve<T extends object> = {
    [k in keyof T]?: T[k];
} & {
    [k in requiredKeys<T>]: T[k];
};

type Example3 = { property: string; optionalProperty: string | undefined };

const instance3: mergeIntersections<addQuestionMarksPreserve<Example3>> = { property: "" };

// type Instance3 = {
//    property: string;
//    optionalProperty?: string | undefined;
// }
type Instance3 = typeof instance3;

All I have done is changed [k in optionalKeys<T>]?: T[k]; to [k in keyof T]?: T[k];. Using Go To Definition and Rename Symbol on property on the line starting with const instance3 now works as you would expect.
I believe this works because { [k in keyof T]?: T[k]; } directly passes on the keys of T without transforming them. This allows TypeScript to connect the original type with the mapped type. We then rely on the fact that { a?: A | undefined } & { a: A } merges to { a: A }, giving us the original type mapping behaviour.
What do you think? Is it worth seeing whether these sorts of changes can improve the IDE experience when using Zod?

I don't have any first hand knowledge of what might be going on here, but I think if we can make a backwards compatible change that preserves our existing behavior and doesn't add much maintenance or cognitive overhead, I'm absolutely thrilled to help get a PR merged that improves editor ergonomics.
I think the one thing I would want to see in a PR that updates this type is some additional type-level tests to ensure we're not breaking anything in the ecosystem, so feel free to open a PR with these changes and we can get that going together.

Thanks @scotttrinh, I've opened a PR: https://github.com/colinhacks/zod/pull/1117

Merged! This is fantastic stuff, thank you 👏


[Bug] [Web] Display "-1" in DataStudio Job Config's SavePointStrategy after creating a flinksql job

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
Env:  Dinky 1.0-rc1 20231215，Firefox 121

What you expected to happen
Display "Disabled".
How to reproduce
DataStudio > Project > Create a flinksql job > Open the new created job > Seeing right pannel's SavePointStrategy.
Anything else
No response
Version
dev
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Problems caused by historical data, please execute
update dinky_task set save_point_strategy = 0 where save_point_strategy is not null and save_point_strategy = -1;

i will be fix it


make the navbar smooth and attractive

@mrbhatt2348 I want to work on this issue under JWOC

I want to work on this issue under JWOC

I want to work on this issue under JWOC

Go on

@mrbhatt2348 please add jwoc and the corresponding difficulty tags

Hey @mrbhatt2348  I want to work on this issue under JWOC.


Animation restarts on window resize

The animation restarts when the window is resized, which is confusing.

Fixed by 44c47d8d226e7cd88ec3f3a80d914de3a61a1112


Add enum for zeCommandListAppendMemAdvise to preferred location to system memory

Currently we have the following ze_memory_advice_t enum values available to control preferred memory location:

ZE_MEMORY_ADVICE_SET_PREFERRED_LOCATION = 2,    ///< hint that the preferred memory location is the specified device
ZE_MEMORY_ADVICE_CLEAR_PREFERRED_LOCATION = 3,  ///< removes the affect of
ref.: https://spec.oneapi.io/level-zero/latest/core/api.html?highlight=zecommandlistappendmemadvise#_CPPv418ze_memory_advice_t

The Set option is aimed to set preferred location to the specified device only,
which is default for KMD-migrated shared allocation for performance reasons.
As a result, currently we are unable to remove its affect other than by calling clear.
But the Clear option without calling the set option is not expected to do anything.
So we need a hint to set preferred location to system memory to change the default.

Note: The KMD has already uAPI for VM ADVISE to specify preferred location
to both system or device memory, and clear the current preferred location:
{code}
struct prelim_drm_i915_gem_vm_advise {
...
/**
* Attributes to apply to address range or buffer object
*
* PREFERRED_LOCATION
*	sets the preferred memory class and instance for this object's
*	backing store.  This is a hint only and not guaranteed to be
*	honored.  It is an error to choose a memory region that was not
*	part of the original set of placements for the GEM object.
*	If choosing a preferred location that is in conflict with the
*	use of ATOMIC_SYSTEM or ATOMIC_DEVICE, the atomic hint will
*	always be honored first.
*	To clear the current preferred location, specify memory class
*	as I915_MEMORY_CLASS_NONE.
/
__u32 attribute;
..
#define PRELIM_I915_VM_ADVISE_PREFERRED_LOCATION	(PRELIM_I915_VM_ADVISE | 3)
/* Preferred location (memory region) for object backing */
struct prelim_drm_i915_gem_memory_class_instance region;
{code}
{code}
enum prelim_drm_i915_gem_memory_class {
PRELIM_I915_MEMORY_CLASS_SYSTEM = 0,
PRELIM_I915_MEMORY_CLASS_DEVICE,
PRELIM_I915_MEMORY_CLASS_NONE = -1
};
{code}

Looks like a spec omission, there is not option to set preferred location to host.
We should have set/clear for host preferred location, right now it is not possible to do it via API.

Thanks @MichalMrozek , @smilczar . Yes, I think we need to add it.

Note: alternatively, we can have a generic Get/Set MemAccessAttribute for programmer to specify ATOMIC and SYSTEM settings as well (already discussed with Ankur).


KAFKA-10804 add more subsets and exclude performance tests

This PR is a part of https://issues.apache.org/jira/browse/KAFKA-10804
The following tasks are included by this PR.

add more subsets
not to run all system tests - exclude performance

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

@hachikuji It seems the free plan of Travis CI can't support Kafka system tests totally. Not sure whether we can get more free resources from Travis CI? If not, maybe we should remove (or disable) Travis CI build :(

the timeout StreamsEosTest is traced by #9706

@hachikuji @junrao Could you take a look at following fixes? I'd like to make system tests work ASAP on travis.
streams_eos_test.py -> #9706
connect_distributed_test.py -> #9673
downgrade_test.py and upgrade_test.py -> #9712


Create SuggestionItemImpl class

To create a SuggestionItemImpl concrete class which implements SuggestionItem interface.
model --> suggestion --> SuggestionItemImpl

Hey @johannagwan ! Just nitpicking here, but I feel like the model --> suggestion --> SuggestionItemImpl is not that descriptive.


webkitgtk: 2.24.3 -> 2.24.4 (security!)

Motivation for this change
https://webkitgtk.org/2019/08/28/webkitgtk2.24.4-released.html
https://webkitgtk.org/security/WSA-2019-0004.html
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nix-review --run "nix-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Notify maintainers
cc @

cc @NixOS/backports, :heart:

609fe21661d3998a6d6aff5a2e51609d4fb19d05
Not enough rebuilds to warrant a staging push for stable.


FC alignment

Hi @pgarbacki,
Thanks for contributing!
Would you mind adding some description regarding what this PR is about?

Hey @pgarbacki, any updates on this?


global.json documentation

From @jaredpar on July 17, 2017 21:19
Where can I find documentation on global.json? This is the only public documentation I could find:
https://docs.microsoft.com/en-us/dotnet/core/tools/global-json
Unfortunately it doesn't answer the questions I have about the sdk.versions property. In particular:

What are the matching rules? Say I put 1.0 but 2.0 is available. Will 2.0 be chosen or will an error occur?
Can I put in version ranges?
Is there globbing support?

Also of interest is the version of the SDK that comes installed with Visual Studio. Does that version change on every update, preview, etc ... of VS? Worried about how updates to VS will interact with restrictions that I add in this file.
Copied from original issue: dotnet/sdk#1421

From @livarcocc on July 18, 2017 23:40
@mairaw can we work on documentation for this? We changed the policy in 2.0, it would be good to do an all up write up on this file.

From @jaredpar on July 18, 2017 18:35
CC @rainersigwald, @nguerrera, @dsplaisted

From @mairaw on August 12, 2017 7:21
Sorry, I missed this mention earlier. Yes, we can improve the docs. Doc issues can be filed at https://github.com/dotnet/docs/issues. Can I have more info on what needs to be done @livarcocc @nguerrera? I don't know what the change was or the answer to @jaredpar's questions, unfortunately. Should we move this to our repo?

From @jaredpar on July 19, 2017 15:7
@livarcocc can we get the details posted here while waiting for doc? Need to understand how this works before we can adopt in our repos.

What are the matching rules? Say I put 1.0 but 2.0 is available. Will 2.0 be chosen or will an error occur?

Prior to dotnet 2.0, the matching rule was that if no exact match was found, then latest would be used. https://github.com/dotnet/core-setup/issues/2334
In 2.0, the rules are described in this PR's description: https://github.com/dotnet/core-setup/pull/2621. However, in the desktop msbuild/VS case, the error cases listed there are actually currently fallbacks to the 1.1 SDK in the MSBuild folder due to the problem described in https://github.com/dotnet/sdk/issues/1470#issuecomment-322310484

Can I put in version ranges?

No

Is there globbing support?

No

Also of interest is the version of the SDK that comes installed with Visual Studio. Does that version change on every update, preview, etc ... of VS? Worried about how updates to VS will interact with restrictions that I add in this file.

Yes, it does change.

Tagging @johnbeisner.

I'm working on this right now. One behavior I've observed is that if I specify a patch version that is greater than the latest installed version, latest is used.
e.g. if I specify 2.1.4 and the latest version I have is 2.1.300-preview1-008174, latest is used (something like roll backward along patch). By design?
/cc @KathleenDollard

@mairaw That sounds like this issue: https://github.com/dotnet/core-setup/issues/3805

That's correct @dsplaisted!

I've read the info @nguerrera about the VS/MSBuild case and it's not super clear to me what happens when with the multiple possible combinations (VS versions earlier than 15.3 and later, SDK 1.1, SDK 2.0, etc.)
Can someone please summarize that please?


Missing rpm binaries in the release

Current implementation of GH workflows do not produce rpm binaries.

Closing, as this is duplication of #325


Adding the cli to be published to Docker hub

@bradrydzewski Let me know if this works for you or if I should find another way to publish to docker hub :)

This will be extremely useful for me (currently using a similar image that I roll). When will this be merged?

@bradrydzewski didn't know if you decided to include this or not :)

This is a very useful feature for me. I'd love to just run
$ docker run -it --env-file=drone.env drone/cli drone repo ls

Instead of downloading the binaries from github. Drone is container-centric after all!
Seems simple and ready to merge. Are you planning to add this? Ping @bradrydzewski.

@tboerger I think this should have all your comments covered. I also parallelized the builds.

I think the scope of this was a bit too large. I use slightly different conventions in the drone organization, and this pull request broke with the conventions we're using in the drone/drone project.
I pushed d7b19e6f6f581880352f232ba3453e0b769a9dca which we can use as a baseline going forward.


Pandas

Pre-merge request checklist:

[x] I have performed a full review of this code myself.

For Python code in PySpark specific sections, all code should have been run in Jupyter notebooks.
For code in sections of the book containing both Python and R code, the page of the book should be constructed as described in the contributing guide and converted to a markdown file.

[x] I have formatted the outputs of code blocks correctly (to match other outputs in the book and in line with the style guide [coming soon])
[x] I have built the book as outlined in the contributing guide and confirmed that any additional/modified content is displaying as expected.

Details of this request (such as):

I have updated the examples given for Pandas UDFs in the Book to use Easting and Northing coordinates for calculating distances.

Things to note about this request (such as):

The aim was to make the examples less arbitrary

Hi Nathan,
I have made corrections as per your comments, these have been pushed as seen in the most recent commit. Thank you.


Install / docker instructions

For those with no java experience, it would be very useful to have build/install directions  or a docker image
This looks like a great tool.

Sorry, I'm not very experienced with using Docker and can only provide a Windows version of my software as I don't have access to a Mac computer.


Refactoring has lead to slight performance drop and needs repair

Refactoring somewhere around 75fa509c7eab9c33a52de4276507e56279d9ccfd leads to performance drop. Find it and correct it.

Performance loss has been corrected in d6386be24845b61459b07a07835b362286488b52 and might have been a misguided refactor of Knuth long division. Now try for the other non-lossy refactoring.

Correction cycling in #379. Note to self: Stop fumbling around with long division.


Problem: tier-2 testing does not include a straightforward load test

@jhult Would it be possible to easily construct a load test by invoking all of the HURL tests, but in parallel all at once?


Use erlef/setup-beam for GitHub Action

Pull Request Test Coverage Report for Build ffcdc07e94e81aca28ce03d1f1d02cc4d32d712f-PR-60

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.074%

Totals

Change from base Build 05a07644f9158b8bb7466c5ce02fa9f11c5c1ef1:
0.0%

Covered Lines:
107

Relevant Lines:
108

💛  - Coveralls

Thanks @kianmeng! 💟


refactor: move website examples into data files

The examples showcased on the website were previously all defined in the the YAML front matter of _index.md. This commit moves them to separate data files1, which are easier to edit and test.

Thank you for the contribution!
Do you think that it is worth splitting the new .yaml files into separate .prql and .sql files, so we get syntax highlighting when editing them? We do something similar with integration tests and book tests.

Currently the example metadata also includes a label, so I think it makes sense to have everything together (i.e. label, prql and sql) in one file.

Could we put the label into _index.md?

Yeah we could but then the data for one example would be split up across three different files, which I think would make editing examples more cumbersome.

I'm -0.5 on merging this, as the examples equality accessible as before as since they are still in YAML, but spread over multiple file.
@max-sixty I'll defer this one to you.

I want to note that the refactor did enable the test code to be simplified since it no longer has to extract the tests from _index.md or special case the hero example.

Oh I'm +1 on this, test code is much simpler.
I would be even keener if they were .prql files we could snapshot; then we get the benefits of editing PRQL files directly, and zero test code. But that requires running the compilation as part of building the website (unless we instead extract from the snapshot files https://github.com/mitsuhiko/insta/issues/353)


ARROW-5727: [Python] [CI] Install pytest-faulthandler before running tests

I'm regenerating the manylinux build images...

Images uploaded to quay.io now.

Travis-CI build: https://travis-ci.org/pitrou/arrow/builds/550347796
AppVeyor build: https://ci.appveyor.com/project/pitrou/arrow/builds/25531096


♻ refactor for using StatLoggerBase

Based on https://github.com/vllm-project/vllm/pull/5925 (should be merged after the upstream code is released)

CI will fail until 0.5.1 is released

CI will fail until 0.5.1 is released

Yes but the bug is not related to the ci right

See #28: this will immediately stop the adapter if one of the tasks fails

Regarding this PR: I included this in #30 (https://github.com/opendatahub-io/vllm-tgis-adapter/pull/30/commits/474cb80799651f8c65520f43b77b1ab2951b56d5), while modifying it to make sure this works with the current (and previous) vLLM version


Request for documentation: desktop client changelog incomplete (v5.8.1)

The changelog for the desktop app is incomplete ( https://docs.mattermost.com/about/desktop-app-changelog.html ). It only contains v5.8.0, not v5.8.1, which has been cut 2-3 weeks ago.
I am very sure, that I already saw the changelog for v5.8.1 on the page in the past, but it seems to have disappeared/been overwritten.
Could this please be fixed?
Best regards!

This will be fixed via https://github.com/mattermost/docs/pull/7249.


docker dbpedianif: fix rights of created files

The files created by docker are owned by root, but should be owned by the user executing docker.

Check out https://github.com/docker/compose/issues/3270

implemented:
set permissions for /root in docker image and use set-user-with-folder.sh to execute as owner of the mounted folder.


documentation: Add code comments to auth pathway.

There are a few functions that are confusing to new developers trying to understand or modify the login code.

maybe_send_to_registration, in the remote_user pathway
How django's authenticate chooses which auth backend to use

@gnprice fyi / feel free to edit.

@HarshitOnGitHub I just wrote pretty extensive documentation for how our authentication systems work internally in the comments in 873aca4a8243e3187fc00c38ae4da80ccf0cd88a; since you've been reading this code recently, I'd love it if you gave that a read and commented on anything that could be improved, either in terms of details that were really important for your understanding the code that aren't mentioned here or any confusing/inaccurate language (feel free to either list things or submit a PR).


GenIso for empty case classes

Closes #222

Hm build seems to fail with an issue pulling 2.11.6 ?

That's nice you managed to handle the object and empty case classes in the same method :)
what do you think about apply0, one or single instead of unit? In fact, Unit is by definition the type with a single value, so maybe that's the most accurate name.


Excuse me, how is this tilt effect achieved?

Yes, at the moment the perspective effect was disabled by a flutter bug. In the new version, for some reason if you add ClipRRect inside something that will be transformed into perspective a bug occurs (the screen disappears)

Oh, thank you.


Code of Conduct  Update README.md

@Rockyspade #6

I think we can close this PR.

@bartekpacia I think we can report this account.


[Off-chain] Simplify TxClient with EventsQueryClient

Summary
Human Summary

Simplifies TxClient implementation by replacing EventsQueryClient usage with an EventsReplayClient.
Simplifies EventsReplayClient to take a single generic type parameter.

Issue

#256

Type of change
Select one or more:

[ ] New feature, functionality or library
[ ] Bug fix
[x] Code health or cleanup
[ ] Documentation
[ ] Other (specify)

Testing

[ ] Run all unit tests: make go_develop_and_test
[ ] Run E2E tests locally: make test_e2e
[ ] Run E2E tests on DevNet: Add the devnet-test-e2e label to the PR. This is VERY expensive, only do it after all the reviews are complete.

Sanity Checklist

[x] I have tested my changes using the available tooling
[ ] I have performed a self-review of my own code
[x] I have commented my code, updated documentation and left TODOs throughout the codebase

I'm not sure why the E2E tests are failing in CI. :thinking:
(cc  @okdas, if you have bandwidth, I would be grateful for an explanation at least :sweat_smile: :shrug:)

I'm not sure why the E2E tests are failing in CI. 🤔
(cc @okdas, if you have bandwidth, I would be grateful for an explanation at least 😅 🤷)

Interesting! RelayMiner is down with the following error:
{"level":"info","message":"Starting relay miner..."}
{"level":"info","message":"starting relayer sessions manager"}
{"level":"info","message":"starting relayer proxy"}
{"level":"info","proxy host":"<IP_ADDRESS>:8545","message":"starting relay proxy server"}
{"level":"info","message":"starting ring cache"}
panic: unexpected error deserialising event: {"jsonrpc":"2.0","result":{},"id":"XU72jMrpfPM="}
: attempted to deserialize non-tx event bytes [/go/pkg/mod/cosmossdk.io/errors@v1.0.0-beta.7/errors.go:153]; eventBz: {"jsonrpc":"2.0","result":{},"id":"XU72jMrpfPM="}

goroutine 208 [running]:
github.com/pokt-network/poktroll/pkg/client/events.(*replayClient[...]).newMapEventsBytesToTFn.func1({{0xc00038b800?, 0x32?, 0x200}, {0x0, 0x0}})
    /poktroll/pkg/client/events/replay_client.go:295 +0x1b4
github.com/pokt-network/poktroll/pkg/observable/channel.goMapTransformNotification[...]({0x40c4408?, 0xc000a09590}, {0x40bc750, 0xc000ff0ea0?}, 0xc001234460?, 0xc00120e618)
    /poktroll/pkg/observable/channel/map.go:117 +0xff
created by github.com/pokt-network/poktroll/pkg/observable/channel.MapReplay[...]
    /poktroll/pkg/observable/channel/map.go:76 +0x1da
Stream closed EOF for devnet-issue-330/devnet-issue-330-relayminer-59fc47499f-l54xl (relayminer)

Does that look familiar? I'll see how to better provide this kind of information to you and other developers!


Add properties of a question all at once?

Are you requesting a feature, reporting a bug or ask a question?
Asking a question: Is there a way to add all the properties of a question at once?
const page = editor.survey.pages[0];

// How I've seen the tests do it
page.addNewQuestion('radiogroup');
q.title='Gender'
q.isRequired=true;
q.choices=['Male', 'Female', 'Non-Binary', 'Rather Not Say']

// How I'd like to do it
page.addNewQuestion({
  type: 'radiogroup',
  title: 'Gender',
  isRequired: true,
  choices: ['Male', 'Female', 'Non-Binary', 'Rather Not Say']
});

Sure
    var json = {
     name: "question1",
     type: "radiogroup",
     title: "Gender",
     isRequired: true,
     choices: ["Male", "Female", "Non-Binary", "Rather Not Say"]
    };
    var newElement = Survey.JsonObject.metaData.createClass(json["type"]);
    new Survey.JsonObject().toObject(json, newElement); // or just use this string to fill the object with json

Thanks for the quick response


Add Cross-Platform Support for File Watching and Command Execution(Windows OS🪟)

This pull request introduces several enhancements to ensure cross-platform compatibility for the file watching and command execution functionality of the project. The primary changes include:
Cross-Platform Command Execution:
Modified the ExecuteCommand function to support both Unix-like systems and Windows🪟.
Path Handling Adjustments:
Ensured that file paths are formatted correctly for the operating system by using filepath.FromSlash().
Also:
Delete redundant break statement (switch mode)
Update go.mod file go 1.23.0 -> go 1.23.1

Thanks for your contribution.


Highlight symbolic links in different color

Is it possible to have symlinks highlighted in a different color than regular files?
I tried changing NeoTreeSymbolicLinkTarget highlight group but that seems to have no effect.

How can I detect when an object is a symlink? I tried node.type == "symlink" as a guess based on file_type_map in filter_external.lua but it's not working.

How can I detect when an object is a symlink? I tried node.type == "symlink" as a guess based on file_type_map in filter_external.lua but it's not working.

Use node.is_link. Also, node.link_to will give you the target of the link if you need it.


No Robot Appears When Running python test.py -r uid

Hello,
In the tutorial found at (https://maniskill.readthedocs.io/en/latest/user_guide/tutorials/custom_robots.html#testing-the-loaded-urdf-mjcf，Testing The Loaded URDF/MJCF), I encountered an issue when running the command python test.py -r uid. The SAPIEN window does pop up during execution, but no robot appears in the simulation.
To verify that this issue is not related to my URDF file, I used the provided panda_v2.urdf file included in the project. However, the result is the same: the robot does not appear.
Could you please help me understand why this is happening? Thank you!

Solved, but keyframes must be set. However, this was not mentioned in the tutorials.

Thanks for the bug spot, I have reopened it so that we can address this in the docs.


aksv2 add inline cloud cred test check

Right now there is no credential check when adding a cloud cred for aksv2. We need to add it back in so the cred doesn't get created if the credentials are invalid.
Waiting on endpoint: https://github.com/rancher/rancher/issues/33861

I had made this for 2.6.1, but we can close and use primary backend issue also.

LGTM
on v2.6-ba95a58481e6fe693e3e4d45931a055e67a97af7-head:

Same results on master-61339fb7f8ff0b7833a80cbb3913f152477871b7-head


Indicate if all required metrics were fetched

ARUHA-2103: Fix metric endpoint to indicate missing metrics
Description
Previously, metric endpoint doesn't state if it was able to fetch all metrics for all brokers.

lgtm 👍


This code is not working

TelemetryConfiguration configuration = TelemetryConfiguration.CreateFromConfiguration("ApplicationInsights.config");
The argument to CreateFromConfiguration method is to receive XML content, not the path of config file.
Source Code: TelemetryConfiguration.cs#L289

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

ID: b189efce-ce4e-f8f8-ecf8-8803a18f9b65
Version Independent ID: aec54012-dae3-ce18-0f8c-30749c46a79c
Content: Azure Application Insights for Console Applications
Content Source: articles/application-insights/application-insights-console.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@poychang ty,,

@poychang Thank you for bringing this to our attention. You are absolutely right the code would need a little modification to be able to work:
using System.IO;
TelemetryConfiguration configuration = TelemetryConfiguration.CreateFromConfiguration(File.ReadAllText("C:\\ApplicationInsights.config"));
var telemetryClient = new TelemetryClient(configuration);

An update to the doc has been merged internally it will go-live in for the en-us docs at 10 AM (UTC-7) tomorrow.

@MicrosoftDocs/azure-cxp-triage #please-close


Platform - look into adding testing for cloud functions

Description
Currently, we do not have any tests set up for the cloud functions. Now that the scraper is finalized, we can begin writing some tests for it to increase confidence. We can follow this guide https://cloud.google.com/functions/docs/testing/test-http#functions-testing-http-unit-nodejs
TODO

[ ] follow this guide to implement test structure https://cloud.google.com/functions/docs/testing/test-http#functions-testing-http-unit-nodejs
[ ] add some unit tests

Additional context
N/A

after investing and doing a lot of research, the best way to be able to test for cloud functions and firestore is to use the firebase emulator. Some alternatives are deploying the tests to production and then running the tests that way on the prod database which would not be ideal. We could also create another firebase to deploy tests there (similar to a staging environment) but we don't have the funding or manpower to maintain a staging environment. So as a solution, we will run our cloud functions on the local emulator and test it that way.


SQS client.receive_messages hangs when WaitTimeSeconds is not set

Using version 1.0.0
I've found that with SQS client, calling client.receive_message() without WaitTimeSeconds param causes the statement to hang for a 5-10 mins before returning None. If I supply any WaitTimeSeconds param such as "20" it works fine.
Seems to related to this block https://github.com/spulec/moto/blob/master/moto/sqs/models.py#L346-L352

Perhaps changing linee 346 to:
if result or (unix_time() > polling_end):

Fixed by @Brett55 in #969

@JackDanger Wanted to contact you direct but this will have to suffice, I noticed that when I upgraded to version 1.0.0 of Moto, that tests are hitting AWS direct (SQS and SNS). I confirmed this by rolling back to 0.4.31 and master branch from github. I will look into this further, but I'd imagine this is not expected

@Brett55 That's a known but under-publicized change of Moto 1.0. What you need to do is replace @mock_sqs with @mock_sqs_deprecated (and same for other service) everywhere that Boto is used. @mock_sqs is now only for Boto3 support.

Thanks for response, okay, that makes sense. It seems that moto 0.4.31
works with both boto 2 and 3 and moto 1.0.0 you must be explicit on
@mock_sqs vs @mock_sqs_deprecated?
On Fri, Jun 2, 2017 at 4:12 PM, Jack Danger<EMAIL_ADDRESS>wrote:

@Brett55 https://github.com/brett55 That's a known but under-publicized
change of Moto 1.0. What you need to do is replace @mock_sqs with
@mock_sqs_deprecated (and same for other service) everywhere that Boto is
used. @mock_sqs is now only for Boto3 support.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/spulec/moto/issues/968#issuecomment-305921079, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AGsE2T3-IpR8wrtKaryq9ZO3CN5ho8I8ks5sAIjUgaJpZM4NsVic
.

@Brett55 That's correct.


statSTR error when specifying samples on the command line

The statSTR documentation says it accepts a comma-separated list of samples OR a file with a list of samples. But if I do:
statSTR --vcf NC_051357.vcf --samples BN,WN --acount --out stdout

It is attempting to read from a file rather than accepting those sample IDs as strings:
FileNotFoundError: [Errno 2] No such file or directory: 'BN'

Update: I misread the usage info. We say comma-separated list of files, not sample names. This would be a nice feature in the future, but closing for now since we actually do what is advertised.