/agent/.xml is not Atom like button says

agent.html template for /agent/<identifier>/ displays a button labeled "XML/ATOM" that links to /agent/<identifier>.premis.xml which is not valid Atom. Should that button take the user to /APP/agent/identifier/ similar to the button on an event entry page? If so, should it use a similarly labeled button? Or is that template served as desired and we should change the label on the button?

@vphill can you look at the questions here when you get a chance?

I think we should make it consistent with the behavior of other parts of the app and lead us to /APP/agent/identifier/ and it should return the ATOM wrapped version.

I think this issue still needs some handling. We should change the button on /agent/identifier/ view to look like the "Atompub" button on the /event/identifier/ view  and then link the button to /APP/agent/identifier/ rather than where it goes now.

Should we keep the button that's there now and change its label to XML (in addition to adding the Atompub button)?
Also, should there be a JSON representation of both?

I am not sure what led to the decision to have the premis.xml and JSON formats of agent and not event. The way things are in the app, I am fine with keeping an XML button on agent and not adding a JSON representation to event. Though @vphill may want different, since of any of us, he is the one that might know why we have the different representations.


Workaround: do not use IO::Descriptor to load debug symbols

Fixes #8163. Fixes #13720. Fixes #13792. The underlying codegen issue is not fixed here.
Although this might not have the best performance, Exception::CallStack.load_debug_info is only called at most once for each process. I have not performed any benchmarks.

Is this really a regression, or the regression is in the codegen issue? I'm asking because I don't think we changed anything related to this part in 1.10-dev to justify this being a regression.

IMO the fact #11242 broke the CI in #13720 means this is indeed a regression, even though the codegen issue existed before 1.0.0

ah ok, thanks

Superseded by #13863


Need to create a new landing page

A landing page explaining the idea of the site. Explaining that you can ask for help, or that you are able help somebody.
I'm open to any suggestion!
Some content like:
CollabCity - Collaborate with your City
Need any help or want to help your community?
Say what you need or what you are willing to donate!

Hi,
Are you looking for UI/wireframe ?


Fix decoding of internal narrow-links

Links to narrows containing non-ASCII characters were not being fully decoded.
This should fix an error reported in Sentry: https://sentry.io/organizations/zulip/issues/1200774371/

Thanks!
FTR the linked Sentry error has a stack trace that begins like so:
URIError: URI error
  at decodeURIComponent(app:///[native code]:0:0)
  at getNarrowFromLink(src/utils/internalLinks.js:85:38)
  at next(src/message/messagesActions.js:44:18)

(Sentry items disappear after a pretty short window, I think because of the free plan we're on.)

Haven't yet read this in detail, but one thought I have is: this looks like (a) a pretty fiddly piece of logic, which is (b) self-contained -- naturally a pure, platform-independent function, modulo the addBreadcrumb bit -- and (c) a problem the web frontend also needs to solve. So it seems like a strong candidate for sharing with the webapp.
Want to take a look at the corresponding web-frontend code, and see what it would look like to make that code shared? Who knows, it might even have a bug related to this one :stuck_out_tongue: and then we'd get to fix it in both places at once.
Separately, but at a similar level of detail: I'm not sure what a "dot component" is. Want to add a bit of jsdoc saying what decodeDotComponent is meant to do? Possibly another name would convey more of the meaning, too. (This may be moot, depending on how the sharing prospects look.)

static/js/hash_util.js is the relevant webapp code, which seems like a module that'd make sense to share.

timabbot wrote:

static/js/hash_util.js is the relevant webapp code, which seems like a module that'd make sense to share.

Alas, no. The majority of that file is concerned with constructing links to narrows, which isn't a thing the mobile app presently ever does. Even if it did, it's also the case that the majority of that file is tightly coupled to the types and structures of the webapp (stream_data.id_to_slug(...)), and factoring that out would probably not be worthwhile.

gnprice wrote:

this looks like (a) a pretty fiddly piece of logic,

Yes, but the fiddly parts are all uselessly paranoid error-checking; in the cold light of a new day, it seems clear that it all needs to be set on fire.

Separately, but at a similar level of detail: I'm not sure what a "dot component" is.

I was kind of hoping you'd have a better idea for a name there. :sweat: Renamed to decodeHashComponent, which – while arguably no more informative – is at least the name used by the webapp.

Want to add a bit of jsdoc saying what decodeDotComponent is meant to do?

:+1:

Even if it did, it's also the case that the majority of that file is tightly coupled to the types and structures of the webapp (stream_data.id_to_slug(...)), and factoring that out would probably not be worthwhile.

I specifically was referring to exports.parse_narrow from has_util.js, which is a pure function.

Even if it did, it's also the case that the majority of that file is tightly coupled to the types and structures of the webapp (stream_data.id_to_slug(...)), and factoring that out would probably not be worthwhile.

I specifically was referring to exports.parse_narrow from has_util.js, which is a pure function.

It is pure, but it's still coupled to the webapp's types and capabilities. In particular, it returns values with a negated field, which the mobile app knows nothing about.
(It would make quite a bit of sense, though, to core out getNarrowFromLink and replace its interior  with a thin transformation layer wrapped around parse_narrow.)

Thanks again! Merged.

I specifically was referring to exports.parse_narrow from has_util.js, which is a pure function.

If you follow the call graph in the source, you'll find that a lot of that function's work gets done by decode_operand, and that relies on people.slug_to_emails and stream_data.slug_to_name, which in turn consult the app's data structures. So that will require some refactoring to share: it'll need to take those data structures (perhaps better, getters for them) explicitly.
That's an example of what I had in mind with:

I think the refactoring needed to share more of the hash_util module will be worthwhile to do eventually, but it's tangential to the issue at hand so we might as well pursue other priorities first.

Just so it's not lost in the GitHub thread noise, I'll repeat the followup suggestion I made above, though:

I think actually the main opportunity now is that these newly-written tests are much more thorough and informative than those in the frontend.
For that reason, and to get further experience sharing code, I think it'd be a good followup to... move decodeHashComponent and its inverse encodeHashComponent, say, into a shared module.

Thanks again! Merged.

I specifically was referring to exports.parse_narrow from has_util.js, which is a pure function.

If you follow the call graph in the source, you'll find that a lot of that function's work gets done by decode_operand, and that relies on people.slug_to_emails and stream_data.slug_to_name, which in turn consult the app's data structures. So that will require some refactoring to share: it'll need to take those data structures (perhaps better, getters for them) explicitly.
That's an example of what I had in mind with:

I think the refactoring needed to share more of the hash_util module will be worthwhile to do eventually, but it's tangential to the issue at hand so we might as well pursue other priorities first.

Just so it's not lost in the GitHub thread noise, I'll repeat the followup suggestion I made above, though:

I think actually the main opportunity now [to share code in this area] is that these newly-written tests are much more thorough and informative than those in the frontend.
For that reason, and to get further experience sharing code, I think it'd be a good followup to... move decodeHashComponent and its inverse encodeHashComponent, say, into a shared module.

Ahh, makes sense.  Such a refactoring sounds good.  We could name that module narrow_encoding.js or something.

Filed #3757 for that pair of sharing opportunities.


Automatic parsing of youtube/hulu URLs

YouTube parsing added in https://github.com/JadenGeller/Helium/commit/2d824cea0d77b36c49b8c52803d1eb49f6f4a9d2

Hulu parsing still planned. May require loading the page first and then redirecting


BabylonNative should add initialization logic to correctly propagate the application name to the openxr runtime

Right now we declare an application name of "Open XR Sample" for all xr components:
https://github.com/BabylonJS/BabylonNative/blob/e6ab99276c4bfcb632cedd9ef1905c3448fc8699/Dependencies/xr/Include/XR.h#L350
it feels like this value should be updated to use the actual application name or at least fixed for non openxr platforms.
Note, if we do update the application name, we should also make our application copy name more robust. right now we are not checking that the application name is longer than the allowed application name buffer:
https://github.com/BabylonJS/BabylonNative/blob/e6ab99276c4bfcb632cedd9ef1905c3448fc8699/Dependencies/xr/Source/OpenXR/XR.cpp#L219

Closing for now. Reopen if we want to support this feature.


Numeric column generated as string

Hello, We have Numeric columns that being defined a Generated<Numeric> and when used in queries the datatype of the returned column comes up as string. Should it not be set to number?
export type Numeric = ColumnType<string, string | number, string | number>;

This is correctly implemented, Numeric is possibly string since the value stored cannot be stored in a JS number int.


CB-14728 Enable stopping clusters with ephemeral based hostgroups bas…

…ed on service role whitelist.
See detailed description in the commit message.

also the commit message is not descriptive enough, please make sure it contains detailed information what has changed and why


Add Support for That Midea Remote Everyone Has (RG10F2(D2)/BGEFU1)

I'm not too up on github, but I'm an HVAC tech that watches coding videos on lunch, and spent a weekend pulling and cross-referencing codes using my Broadlink RM4 mini with a half-dozen Midea (and MrCool and Carrier lower-end stuff, all made by midea) remotes and units, and have a unified config that applies to many units.
However, I'm not up on github, and learning how to do a pull request and format it properly would be one thing, and when I was done with everything, I learned of this branch that some people are using.
Reading comments and descriptions, it seems like it would be even more work to translate this over here, and I simply don't have it in the cards for me.  But I do have a json that works with a ton of models of things.  Is it okay to share the working file here?
Remote Models this works for:
Midea RG10F2(D2)/BGEFU1
Midea RG10B(B)/BGEF
Midea/Dreo RG10B(K1)/BGEFU1
Tested climate models this works for:
Dreo TwinCool 12000 BTU Smart Inverter Portable Air Conditioner
Midea  8,000BTU, U-Shaped AC
Midea 12,000 BTU U-Shaped AC
Midea 10,000 BTU U-shaped AC
MRCOOL Versa Pro 30,000 BTU 2.5-Ton 16.5 SEER2 Central Ducted Heat Pump Split System MVP-30-HP-230-25
MRCOOL Versa Pro 30,000 BTU 3-Ton 16.5 SEER2 Central Ducted Heat Pump Split System MVP-36-HP-230-25
MRCOOL EZ Pro Single Zone 24000-BTU 18 SEER Ductless Mini Split EZPRO-24-HP-23016
MRCOOL EZ Pro Single Zone 12000-BTU 18 SEER Ductless Mini Split EZPRO-12-HP-11516
I've confirmed functionality of all commands with all devices.  There were many duplicated or incompatible commands that would cause issues across sub-models (where, say, 24c fan high recorded with one remote would activate auxiliary heat on another unit), but I used a hefty dose of claude, an excel spreadsheet, and a full workday of time to parse out and sanitize these IR commands to not cause any issues.    That said, troubleshooting the format of the yaml/json was almost more difficult for me.
I don't know the numbering scheme of the old or this new fork, but I called it 1832:
1832.json

Hello, thank you fro your contribution. I did slightly modified your file to conform with improved structure of the climate JSON in this  project and merge it as #172


Won't install to VS 2017 on Windows 10

I just installed 2017 Enterprise edition on a Windows 10 machine.  I have previous version of VS 2015 and VS 2013 installed.  I downloaded the AWS Toolkit for Visual Studio 2017 installer.  When I run it, it fails.  I'll attach the log but in short, it fails to find VS 2017 and fails with VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
Expected Behavior
Toolkit should install successfully
Current Behavior
Fails with a VSIXInstaller.NoApplicableSKUsException: This extension is not installable on any currently installed products.
Possible Solution
Unknown
Steps to Reproduce (for bugs)
Install VS 2017 Enterprise.
Download and start AWS Tookit for Visual Studio 2017 installer
Context
I can't create an AWS Serverless Application solution.
Your Environment

Operating System and version: Windows 10
Visual Studio version: 2017 Enterprise

VSIXInstaller_1586156a-0b7c-4397-a866-fee9c9a5dc59.log

Microsoft's vsix installer utility is part of your individual Visual Studio installs and I have a working theory that when you download from the marketplace to your file system and then launch the installer by double-clicking the downloaded file, the wrong version of the installer gets launched and results in the 'cannot find installed products' error. For example, the version of the installer that is distributed with Visual Studio 2015 knows nothing of how to find Visual Studio 2017 editions and if it is launched on a downloaded vsix that is declared (as ours is) to support 2017 only then it will trigger that message.
Instead of downloading the vsix file I recommend installing from within Visual Studio 2017 itself. Launch the IDE and navigate to the Tools menu and select Extensions and Updates. In the resulting dialog select the Online category and then search for 'AWS'. This will bring up the entry for the toolkit. Select it and click the download or install link (I don't immediately recall which button gets shown). This will queue the install to occur when Visual Studio is restarted, so close the IDE and you should see the install process start up. On next load of the IDE, you should find the toolkit to be installed - e.g the View menu will show the AWS Explorer option and if the toolkit cannot find credentials to use it will display it's 'first run' page to guide you.

Thank you.  I totally forgot about Extensions and Updates.   It gave me trouble on the first try but after a reboot it worked.  Thanks for the help.


Fail load the latest post/internal link

6:23:23 PM:   ✖ FAIL load public/chocolate-balls-with-peanut-butter-filling
6:23:23 PM:   | operator: load
6:23:23 PM:   | expected: 200 public/chocolate-balls-with-peanut-butter-filling
6:23:23 PM:   |   actual: ENOENT: no such file or directory, open '/opt/build/repo/public/chocolate-balls-with-peanut-butter-filling'
6:23:23 PM:   |       at: public/chocolate-balls-with-crunchy-peanut-butter-filling/index.html:17:916 <meta data-react-helmet="true" property="og:url" content="https://www.petiteandminimal.com/chocolate-balls-with-peanut-butter-filling">
6:23:23 PM:   3685 tests
6:23:23 PM:      2 skipped
6:23:23 PM:   3684 passed
6:23:23 PM:      1 failed
6:23:23 PM:
6:23:23 PM: ────────────────────────────────────────────────────────────────
6:23:23 PM:   Plugin "netlify-plugin-checklinks" failed
6:23:23 PM: ────────────────────────────────────────────────────────────────
6:23:23 PM:
6:23:23 PM:   Error message
6:23:23 PM:   Error: Links checking failed
6:23:23 PM:
6:23:23 PM:   Plugin details
6:23:23 PM:   Package:        netlify-plugin-checklinks
6:23:23 PM:   Version:        4.1.1
6:23:23 PM:   Repository:     git://github.com/munter/netlify-plugin-checklinks.git
6:23:23 PM:   npm link:       https://www.npmjs.com/package/netlify-plugin-checklinks
6:23:23 PM:   Report issues:  https://github.com/munter/netlify-plugin-checklinks/issues
6:23:23 PM:
6:23:23 PM:   Error location
6:23:23 PM:   In "onPostBuild" event in "netlify-plugin-checklinks" from netlify.toml
6:23:23 PM:       at onPostBuild (/.netlify/plugins/node_modules/netlify-plugin-checklinks/lib/index.js:63:14)
6:23:23 PM:
6:23:23 PM:   Resolved config
6:23:23 PM:   build:
6:23:23 PM:     command: gatsby build
6:23:23 PM:     commandOrigin: ui
6:23:23 PM:     environment:
6:23:23 PM:       - ALGOLIA_ADMIN_KEY
6:23:23 PM:       - GATSBY_ALGOLIA_APP_ID
6:23:23 PM:       - GATSBY_ALGOLIA_SEARCH_KEY
6:23:23 PM:     publish: /opt/build/repo/public
6:23:23 PM:   plugins:
6:23:23 PM:     - inputs: {}
6:23:23 PM:       origin: ui
6:23:23 PM:       package: netlify-plugin-gatsby-cache
6:23:23 PM:     - inputs: {}
6:23:23 PM:       origin: ui
6:23:23 PM:       package: netlify-plugin-no-more-404
6:23:23 PM:     - inputs: {}
6:23:23 PM:       origin: config
6:23:23 PM:       package: netlify-plugin-checklinks

Any idea how to fix it?! I tried clear cache and re-deploy and it gave me the same errors...

Does the /chocolate-balls-with-peanut-butter-filling url exist in your build directory?

Locally yes. I don't know how to check the one on netlify. I've temporarily disabled the plugin now so I can publish my post.

I'm getting the same behaviour. I deploy the site with a new page, netlify-plugin-checklinks then throws an error that the page doesn't exist (it finds the link path of an og tag).
I then comment out the plugin, redeploy, page goes live, re-enable the plugin and the build succeeds.
Using Hugo for static site generation.

I'm puzzled by this. @jpsear Is there a way you can package up your hugo build output, so I can try to recreate this myself locally? I
ll also need your config of the plugin, and the domain this is deployed to, in order to set up the correct resolution of canonical URL's

I think I may understand what the problem is. The checklinks plugin sets the canonicalRoot to the value of the URL environment variable.
const canonicalRoot = process.env.URL;

If the og: meta tags use a different root URL (such as the value of $DEPLOY_PRIME_URL), then checklinks will not remove the root URL and thus fail to resolve the target.
I wonder if it would be possible to allow the canonicalRoot to be overridden. There are two valid root URLs for a Netlify deploy preview (URL and DEPLOY_PRIME_URL), and that's one place where this can come up.

I can't figure out anyway around this problem because Netlify loads the checklinks plugin before the command runs, and thus it's not even possible to hot patch the plugin. I think if the plugin is going to permit modifying the canonicalRoot, it has to be a setting of the plugin itself.

Here's a possible solution: https://github.com/mojavelinux/netlify-plugin-checklinks/commit/ef948ec54b099e78e65c9f9ac5c7e59c68b322f1

@mojavelinux Oh, I didn't know about that environment variable. Must be new, or at least less than 2 years old (time flies).
I could also allow an override in the plugin config, but I doubt that would probably not be compatible with an environment switch.
And if there is no match, as you also deducted, the link resolver will not understand that the asset should be located in the local file system rather than be fetched from the canonical URL.
I'd welcome a PR for this addition if you've been able to test it and verify that is does not regress in the production case


android X show me the empty list

hi,
Searching for nearby available devices keeps returning empty list on Android X
another device on Android 8.1 works well
flutter 1.22.3
flutter_blue 0.7.3
looking forward to your reply

The location service of the device is turned off !


[SPARK-18852][SS]StreamingQuery.lastProgress should be null when recentProgress is empty

What changes were proposed in this pull request?
Right now StreamingQuery.lastProgress throws NoSuchElementException and it's hard to be used in Python since Python user will just see Py4jError.
This PR just makes it return null instead.
How was this patch tested?
test("lastProgress should be null when recentProgress is empty")

Test build #70105 has started for PR 16273 at commit 326d16f.

Test build #70106 has started for PR 16273 at commit f6312d2.

Left one comment on updating docs, otherwise LGTM

Test build #70112 has started for PR 16273 at commit 005204e.

Test build #70106 has finished for PR 16273 at commit f6312d2.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class EventTimeStats(var max: Long, var min: Long, var sum: Long, var count: Long)
class EventTimeStatsAccum(protected var currentStats: EventTimeStats = EventTimeStats.zero)

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

Merged build finished. Test PASSed.

Test build #70105 has finished for PR 16273 at commit 326d16f.

This patch passes all tests.
This patch does not merge cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/70105/
Test PASSed.

Test build #70112 has finished for PR 16273 at commit 005204e.

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

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

Merged build finished. Test FAILed.

retest this please

Test build #70124 has started for PR 16273 at commit 005204e.

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

Merged build finished. Test FAILed.

retest this please

Test build #70138 has started for PR 16273 at commit 005204e.

LGTM!

Test build #70138 has finished for PR 16273 at commit 005204e.

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

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

Merged build finished. Test FAILed.

Test build #70144 has started for PR 16273 at commit 72e6329.

Test build #70144 has finished for PR 16273 at commit 72e6329.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

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/SparkPullRequestBuilder/70144/
Test PASSed.


helm-install: Make helm install failure fatal

Description
Currently, when helm install fails, testsuite still waits for resources and only fails on timeout.
Fix helm behavior and make it exit right after installation failure.

Spec tests need adaptation
https://github.com/cnti-testcatalog/testsuite/actions/runs/10455212865/job/28983108223


Most viewed follow channel dissapear on refresh

Existing Issues

[X] I have searched for existing issues, this is not a duplicate.

Unmodded Twitch

[X] I have checked and this issue only occurs using bttv-android and not with the unmodded Twitch App

What happened?
Open list of followed channels.
Notice the top live streamer you follow.
Swipe down to reload list.
Top streamer dissapears from list.
For a brief second you see the list without the stories at the top, and then the stories appear, along with the dissapearance of top followed streamer.
Workaround: close and reopen app.
bttv-android version
v16.9.1
android version
14
device
Pixel
Anything else?
If you struggle to reproduce I can send a video.

With the followed channels list, do you mean the "Your Live Channels" category ?

https://imgur.com/a/gly2B4X

I just tried to test this myself. I've noticed that the top followed channel consistently disappears and reappears with each refresh. I personally think we should keep rebaselining as this may be a bug in the Twitch version that they have resolved and isn't actually a BTTV issue.


Further improved Initial Compaction (CORE-443)

Further fixes to Initial Compaction logic based on observed Crash Restart loop behaviour in our dev clusters.  There are still two opportunities for compaction but both now happen after the HTTP Server is up to avoid failing readiness probes.

That trivy issue isn't going away. Have replayed the failed job

Yeah I think fixing that will need to become a priority this week once the release cut is done


upgrade to Symfony 6.3

please don't merge this until all service ready for symfony 6.3

we have some specific methods which use in behat-context package which is not exist in macpaw/behat-messenger-context , to remove this package we should adjust and remove using that method in all package which use BehatMessengerContext check this : https://kollex.atlassian.net/browse/DEV-4047


Move to CNCF Slack (slack.cncf.io)

https://github.com/distribution/distribution#communication

opened https://github.com/distribution/distribution/pull/3343

opened https://github.com/distribution/distribution/pull/3343


@Header annotation does not parse @Schema(implementation)

I've added something like this to my JAX-RS-based server:
 @ApiResponse(responseCode = "204",
      description = "Operation was successful",
      headers = @Header(name = Headers.EXAMPLE_HEADER,
          schema = @Schema(implementation = ExampleTypes.ExampleHeader.class))

Expected: To see this header in my openapi generated spec.
Actual: Swagger core ignored a header annotation
Additional details:

io.swagger.v3.oas.annotations.responses.ApiResponse#headers is seemingly only read from io.swagger.v3.jaxrs2.OperationParser#getApiResponses
It calls io.swagger.v3.core.util.AnnotationsUtils#getHeader which in turn does this:

if (header.schema() != null) {
            if (header.schema().implementation().equals(Void.class)) {
                AnnotationsUtils.getSchemaFromAnnotation(

Looks like if schema is specified, but it has implementation, then header is silently discarded

Recommended solutions (one of):

Ignore @Schema annotation entirely, but still add a header even if only a name is specified
Parse "implementation" part of header spec correctly
Throw exception when non-Void implementation is detected
Log when non-Void implementation is detected

Any updates when this bug will be fixed? any workaround?
I would like to see this suggestion from @timothybasanov previous comment:

Parse "implementation" part of header spec correctly

A possible workaround, (it may not look clean 🤷🏻), is to implement the OperationCustomizer interface, intercept/find the header and then patch the schema.

Fixed by #4608


A problem occurred configuring project ':react-native-community_masked-view'.

Bug
After installing '@react-native-community/masked-view' i'm facing this error.
I also installed a bunch of gradle versions and plugins but still the same.
Environment info
Binaries:
Node: 10.13.0
Yarn: 1.17.3
npm: 6.4.1
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-173.4907809
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.5 => 0.61.5
React native info output:
$ npm run android

><EMAIL_ADDRESS>android E:\Projects\ReactNative\Real\Wester
> react-native run-android

info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 964 file(s) to forward-jetify. Using 4 workers...
info JS server already running.
info Installing the app...
<-------------> 0% WAITING
> IDLE

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':react-native-community_masked-view'.
> Could not resolve all artifacts for configuration ':react-native-community_masked-view:classpath'.
   > Could not find gradle.jar (com.android.tools.build:gradle:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/3.3.1/gradle-3.3.1.jar
   > Could not find builder.jar (com.android.tools.build:builder:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/builder/3.3.1/builder-3.3.1.jar
   > Could not find tracker.jar (com.android.tools.analytics-library:tracker:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/analytics-library/tracker/26.3.1/tracker-26.3.1.jar
   > Could not find shared.jar (com.android.tools.analytics-library:shared:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/analytics-library/shared/26.3.1/shared-26.3.1.jar
   > Could not find crash.jar (com.android.tools.analytics-library:crash:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/analytics-library/crash/26.3.1/crash-26.3.1.jar
   > Could not find lint-gradle-api.jar (com.android.tools.lint:lint-gradle-api:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/lint/lint-gradle-api/26.3.1/lint-gradle-api-26.3.1.jar
   > Could not find gradle-api.jar (com.android.tools.build:gradle-api:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle-api/3.3.1/gradle-api-3.3.1.jar
   > Could not find databinding-compiler-common.jar (androidx.databinding:databinding-compiler-common:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/androidx/databinding/databinding-compiler-common/3.3.1/databinding-compiler-common-3.3.1.jar
   > Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/manifest-merger/26.3.1/manifest-merger-26.3.1.jar
   > Could not find sdk-common.jar (com.android.tools:sdk-common:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/sdk-common/26.3.1/sdk-common-26.3.1.jar
   > Could not find builder-test-api.jar (com.android.tools.build:builder-test-api:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/builder-test-api/3.3.1/builder-test-api-3.3.1.jar
   > Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/ddms/ddmlib/26.3.1/ddmlib-26.3.1.jar
   > Could not find sdklib.jar (com.android.tools:sdklib:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/sdklib/26.3.1/sdklib-26.3.1.jar
   > Could not find layoutlib-api.jar (com.android.tools.layoutlib:layoutlib-api:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/layoutlib/layoutlib-api/26.3.1/layoutlib-api-26.3.1.jar
   > Could not find dvlib.jar (com.android.tools:dvlib:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/dvlib/26.3.1/dvlib-26.3.1.jar
   > Could not find repository.jar (com.android.tools:repository:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/repository/26.3.1/repository-26.3.1.jar
   > Could not find common.jar (com.android.tools:common:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/common/26.3.1/common-26.3.1.jar
   > Could not find jetifier-processor.jar (com.android.tools.build.jetifier:jetifier-processor:1.0.0-beta02).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/jetifier/jetifier-processor/1.0.0-beta02/jetifier-processor-1.0.0-beta02.jar
   > Could not find bundletool.jar (com.android.tools.build:bundletool:0.6.0).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/bundletool/0.6.0/bundletool-0.6.0.jar
   > Could not find jetifier-core.jar (com.android.tools.build.jetifier:jetifier-core:1.0.0-beta02).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/jetifier/jetifier-core/1.0.0-beta02/jetifier-core-1.0.0-beta02.jar
   > Could not find builder-model.jar (com.android.tools.build:builder-model:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/builder-model/3.3.1/builder-model-3.3.1.jar
   > Could not find protos.jar (com.android.tools.analytics-library:protos:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/analytics-library/protos/26.3.1/protos-26.3.1.jar
   > Could not find apkzlib.jar (com.android.tools.build:apkzlib:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/apkzlib/3.3.1/apkzlib-3.3.1.jar
   > Could not find apksig.jar (com.android.tools.build:apksig:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/apksig/3.3.1/apksig-3.3.1.jar
   > Could not find annotations.jar (com.android.tools:annotations:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/annotations/26.3.1/annotations-26.3.1.jar
   > Could not find databinding-common.jar (androidx.databinding:databinding-common:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/androidx/databinding/databinding-common/3.3.1/databinding-common-3.3.1.jar
   > Could not find baseLibrary.jar (com.android.databinding:baseLibrary:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/databinding/baseLibrary/3.3.1/baseLibrary-3.3.1.jar

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 6s

error Failed to install the app. Make sure you have the Android development environment set up: https://facebook.github.io/react-native/docs/getting-started.html#android-development-environment. Run CLI with --verbose flag for more details.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':react-native-community_masked-view'.
> Could not resolve all artifacts for configuration ':react-native-community_masked-view:classpath'.
   > Could not find gradle.jar (com.android.tools.build:gradle:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle/3.3.1/gradle-3.3.1.jar
   > Could not find builder.jar (com.android.tools.build:builder:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/builder/3.3.1/builder-3.3.1.jar
   > Could not find tracker.jar (com.android.tools.analytics-library:tracker:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/analytics-library/tracker/26.3.1/tracker-26.3.1.jar
   > Could not find shared.jar (com.android.tools.analytics-library:shared:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/analytics-library/shared/26.3.1/shared-26.3.1.jar
   > Could not find crash.jar (com.android.tools.analytics-library:crash:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/analytics-library/crash/26.3.1/crash-26.3.1.jar
   > Could not find lint-gradle-api.jar (com.android.tools.lint:lint-gradle-api:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/lint/lint-gradle-api/26.3.1/lint-gradle-api-26.3.1.jar
   > Could not find gradle-api.jar (com.android.tools.build:gradle-api:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/gradle-api/3.3.1/gradle-api-3.3.1.jar
   > Could not find databinding-compiler-common.jar (androidx.databinding:databinding-compiler-common:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/androidx/databinding/databinding-compiler-common/3.3.1/databinding-compiler-common-3.3.1.jar
   > Could not find manifest-merger.jar (com.android.tools.build:manifest-merger:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/manifest-merger/26.3.1/manifest-merger-26.3.1.jar
   > Could not find sdk-common.jar (com.android.tools:sdk-common:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/sdk-common/26.3.1/sdk-common-26.3.1.jar
   > Could not find builder-test-api.jar (com.android.tools.build:builder-test-api:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/builder-test-api/3.3.1/builder-test-api-3.3.1.jar
   > Could not find ddmlib.jar (com.android.tools.ddms:ddmlib:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/ddms/ddmlib/26.3.1/ddmlib-26.3.1.jar
   > Could not find sdklib.jar (com.android.tools:sdklib:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/sdklib/26.3.1/sdklib-26.3.1.jar
   > Could not find layoutlib-api.jar (com.android.tools.layoutlib:layoutlib-api:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/layoutlib/layoutlib-api/26.3.1/layoutlib-api-26.3.1.jar
   > Could not find dvlib.jar (com.android.tools:dvlib:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/dvlib/26.3.1/dvlib-26.3.1.jar
   > Could not find repository.jar (com.android.tools:repository:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/repository/26.3.1/repository-26.3.1.jar
   > Could not find common.jar (com.android.tools:common:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/common/26.3.1/common-26.3.1.jar
   > Could not find jetifier-processor.jar (com.android.tools.build.jetifier:jetifier-processor:1.0.0-beta02).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/jetifier/jetifier-processor/1.0.0-beta02/jetifier-processor-1.0.0-beta02.jar
   > Could not find bundletool.jar (com.android.tools.build:bundletool:0.6.0).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/bundletool/0.6.0/bundletool-0.6.0.jar
   > Could not find jetifier-core.jar (com.android.tools.build.jetifier:jetifier-core:1.0.0-beta02).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/jetifier/jetifier-core/1.0.0-beta02/jetifier-core-1.0.0-beta02.jar
   > Could not find builder-model.jar (com.android.tools.build:builder-model:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/builder-model/3.3.1/builder-model-3.3.1.jar
   > Could not find protos.jar (com.android.tools.analytics-library:protos:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/analytics-library/protos/26.3.1/protos-26.3.1.jar
   > Could not find apkzlib.jar (com.android.tools.build:apkzlib:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/apkzlib/3.3.1/apkzlib-3.3.1.jar
   > Could not find apksig.jar (com.android.tools.build:apksig:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/build/apksig/3.3.1/apksig-3.3.1.jar
   > Could not find annotations.jar (com.android.tools:annotations:26.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/tools/annotations/26.3.1/annotations-26.3.1.jar
   > Could not find databinding-common.jar (androidx.databinding:databinding-common:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/androidx/databinding/databinding-common/3.3.1/databinding-common-3.3.1.jar
   > Could not find baseLibrary.jar (com.android.databinding:baseLibrary:3.3.1).
     Searched in the following locations:
         https://dl.google.com/dl/android/maven2/com/android/databinding/baseLibrary/3.3.1/baseLibrary-3.3.1.jar

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 6s

    at checkExecSyncError (child_process.js:611:11)
    at execFileSync (child_process.js:629:13)
    at runOnAllDevices (E:\Projects\ReactNative\Real\Wester\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\runOnAllDevices.js:94:39)
    at buildAndRun (E:\Projects\ReactNative\Real\Wester\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\index.js:179:41)
    at then.result (E:\Projects\ReactNative\Real\Wester\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\index.js:133:12)
    at process._tickCallback (internal/process/next_tick.js:68:7)

Version:
"@react-native-community/masked-view": "^0.1.6"

@hossein-zare
hey, same problem,
did you find out the solution??

i think you should change your gradle version

I fixed the issue days ago but forgot it unfortunately.
I changed the Gradle to 5.6.4 and deleted the build directory.
By the way this maybe caused by the US Sanction as it doesn't let us download the requirements from the source directly. Keep in mind that anytime you're trying to update the dependencies have your VPN on.

I think I'm facing the same problem:

A problem occurred configuring project ':@react-native-community/masked-view'.
The project name '@react-native-community/masked-view' must not contain any of the following characters: [/, , :, <, >, ", ?, *, |]. Set the 'rootProject.name' or adjust the 'include' statement (see https://docs.gradle.org/5.6.4/dsl/org.gradle.api.initialization.Settings.html#org.gradle.api.initialization.Settings:include(java.lang.String[]) for more details).

I have solved this by reinstalling / updating these packages.
npm install --save react-native-gesture-handler react-native-reanimated react-native-screens

Ok, so after a lot of pain and testing, I did the following:

Before ejecting from expo(like in my case), make sure all of your dependencies are the latest version,
if you use yarn, just run: yarn upgrade --latest
Make sure the app still runs normally after this.
Eject.
There won't be any problems after that.

Ok, so after a lot of pain and testing, I did the following:
* Before ejecting from expo(like in my case), make sure all of your dependencies are the latest version,
  if you use yarn, just run: `yarn upgrade --latest`

* Make sure the app still runs normally after this.

* Eject.
  There won't be any problems after that.

Also update your app.json to the same major version installed, something like: "expo": { ...     "sdkVersion": "36.0.0", ... }

hi,
I was not able to resolve my issue with above solution.
Do anyone have another solution to help me?

hi,
I was not able to resolve my issue with above solution.
Do anyone have another solution to help me?

I could solve it :
1- I change my VPN port and server
2- check all link to download gradle 3.3.1 manually
3- run npm install --save-dev jetifier (it is necessary to open node window for react native > 0.60.0)
4- run npm react-native run-android -----> it's OK

because of US sanctions packages and requirements can't get installed correctly, make sure you're using some sort of proxy or vpn

the Build revision tool you would be using might not be compatible with the version of @react-native-community_masked-view , you might be using.
So, if you want to install react-navigation^4.x, then install the navigation dependencies including @react-native-community_masked-view, and make sure that here, you use the Build revision tool version 29.0.3, as others might be incompatible with it.


PyPi package lacks ./tests/conftest.py

Environment information

vvm Version: 0.2.1
vyper Version: any
Python Version: any
OS: osx/linux/win

What was wrong?
If the package was downloaded from PyPi then it cannot pass the tests due to lack of ./tests/conftest.py.
How can it be fixed?
It can be fixed by including ./tests/conftest.py file in  the PyPi tarball. Cound you please include it starting from the next release?

hmm, it's not really common for production tarballs to include the test suite. is it an issue to pull from the github repo to run the tests?

hmm, it's not really common for production tarballs to include the test suite.

I believe it's the other way around. Most of the dependencies of a various crypto-libraries  have test-suite published within their PyPi-tarballs. Even if it were true then perhaps you would remove all the tests from PyPi package since they are not useful. :)

is it an issue to pull from the github repo to run the tests?

No, not a big deal. Right now I am using GitHub tarball and back then I was using PyPi one I've just uploaded the ./tests/conftest.py  file  during my CI-testing.

hmm i see what you are saying. but actually i see that tests/conftest.py is indeed in the source tarball? https://pypi.org/project/vyper/0.4.0/#files

Even if it were true then perhaps you would remove all the tests from PyPi package since they are not useful. :)

hmm i see what you are saying. but actually i see that tests/conftest.py is indeed in the source tarball? https://pypi.org/project/vyper/0.4.0/#files

yea, it's a bit weird that it's not being included. i would think it's an issue with setup.py, but i tinkered with it for a few minutes and was not able to convince it to include conftest.py in the build. @lemenkov if you find a solution to this, please open a PR!

Ok, sure!


option cache: false does not destroy the element

when i set cache: false in the creating options, the popup element does not get destroyed when hidden.
Test-Fiddle: JSFiddle (CSS omitted)
From the code I assume the option is just not completely implemented, because the destroy-method is never called.

The code from cdn is not the lastest versions, is the lastest release witch is alot behind.  :)

Even in the source code the destroy method ist never called. I updated my fiddle so that it loads from dist in master, and the behavior is the same.

I'll fix cache problem in next version, please wait.

This bug is fixed, Thanks.


Azure Activity Log RDP Event Recon

What is the process to see who configured destination and source access to RDP for a given VM or resource?

@jschurman Can you please provide us the URL of the Azure doc that you are having issues with? We look forward to your reply.

@jschurman Since we have not heard back from you we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly reopen the issue and continue the discussion.


Fix ssl context creation

As per https://docs.python.org/3/library/ssl.html#examples and https://docs.python.org/3/library/ssl.html#ssl.Purpose.SERVER_AUTH, the Purpose is supposed to mean the type of target we are connecting to, not the type of client/server we are.

Coverage remained the same at 97.402% when pulling 2117f622b1dd1f0769b7c5c75af4c6e24b4a05f1 on adongy:patch-2 into 61459e5d699ff7b68a924b30c1756798e11c0cd5 on gawel:master.

Coverage remained the same at 97.402% when pulling 2117f622b1dd1f0769b7c5c75af4c6e24b4a05f1 on adongy:patch-2 into 61459e5d699ff7b68a924b30c1756798e11c0cd5 on gawel:master.


Added HAZELnet for Community Creation

After feedback from @katomm , moved HAZELnet to the showcase area and updated the wording slightly.

Name: HAZELnet
Description: A community integration tool that allows stakepool operators and NFT projects to connect and engage with their audience, verify their delegators and holders, create polls, whitelists and more via Discord, Website, and other social media apps.
Link:   HAZELnet.io
Source: Github Repo
Tags:

opensource
nftsupport
token

@nilscodes in #697, we added a new tag 'daotool' to the showcase section. I know a lot of DAOs are also using your bot, so it might be a good idea to add this tag

Hi chairs and I try not to say that but you know how much you love them all
the day you are coming to your home and I am looking forward with your
heart attack you and eyyywiih
On Mon, Jul 18, 2022 at 2:07 AM Nicolas @.***> wrote:

@nilscodes https://github.com/nilscodes in #697
https://github.com/cardano-foundation/developer-portal/pull/697, we
added a new tag 'daotool' to the showcase section. I know a lot of DAOs are
also using your bot, so it might be a good idea to add this tag
—
Reply to this email directly, view it on GitHub
https://github.com/cardano-foundation/developer-portal/pull/679#issuecomment-1186893677,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AGL5MXPJCGXCGSD2KNRWE43VUUGEHANCNFSM52RED2RQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@thenic95 I like the idea, but not sure I'd want to exceed the limit of three tags that was suggested :)


unknown type name double_t on mac os x10.13.2

/System/Library/Frameworks/CoreServices.framework/Frameworks/CarbonCore.framework/Headers/fp.h
error: unknown type name double_t

@ofttryaj
fp.h is a c header file, so I think this error come from c/c++ language server, not bingo.

I use go install command to install gopls, it shows me the error messages

@ofttryaj
I has fixed the issue, please try the latest version gopls: https://github.com/saibing/tools

@saibing Thank you very much! It works

@saibing Can you tell me why I can not install https://github.com/saibing/tools before you fix it

@ofttryaj
I'm has used github.com/fsnotify/fsevents that use some cgo code.


postsubmit-test-docker-staging is failing

Automated tests on the docker staging website is failing for containerd 1.6.7
See https://prow.ppc64le-cloud.org/view/s3/prow-logs/logs/postsubmit-test-docker-staging/1558036211107368960
This looks like a go version issue.

On various distros:

test_centos_7.log:70:gotestsum: /lib64/libc.so.6: version `GLIBC_2.32' not found (required by gotestsum)
test_centos_7.log:71:gotestsum: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by gotestsum)
test_centos_8.log:70:gotestsum: /lib64/glibc-hwcaps/power9/libc-2.28.so: version `GLIBC_2.32' not found (required by gotestsum)
test_centos_8.log:71:gotestsum: /lib64/glibc-hwcaps/power9/libc-2.28.so: version `GLIBC_2.34' not found (required by gotestsum)
test_fedora_34.log:70:gotestsum: /lib64/libc.so.6: version `GLIBC_2.34' not found (required by gotestsum)
test_ubuntu_focal.log:70:gotestsum: /lib/powerpc64le-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by gotestsum)
test_ubuntu_focal.log:71:gotestsum: /lib/powerpc64le-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by gotestsum)

On Debian Bullseye:

test_debian_bullseye.log:85:/usr/local/bin/test-launch.sh: line 28: /workspace/test/bin/gotestsum: Text file busy

This looks similar to this issue https://github.com/containerd/containerd/issues/7255

It looks like we are hitting the buildkit cache issue again, see https://github.com/moby/buildkit/issues/1368
We made a recent changes to run the Docker tests in parallel for checking the packages for the various distro.
To run those tests we first build an image where we install the packages under test. Then we call gotestsum in it.
Adding a touch on the Docker file prior calling docker build fixes this issue.


cloudsmith-cli errors when doing a whoami on a service account

When using a service account with cloudsmith-cli, the whoami fails because it is trying to map fields that don't get returned from the API (name, email).
Stack Trace Snippet:
site-packages/cloudsmith_cli/cli/commands/whoami.py", line 39, in whoami
"email": click.style(email, fg="green"),
File "/usr/lib/python3/dist-packages/click/termui.py", line 449, in style
return ''.join(bits)
TypeError: sequence item 1: expected str instance, NoneType found
I will send a PR where we can explicitly define these as "Null" if they are None, to allow the code to properly complete.

PR in #116


refactored and added some documentation

(1) added a button in ViewHabitActivity that switches the activity to HabitEventsMainActivity
(2) refactored and added some more documentation
(3) implemented 02.03.01 and 02.03.02

Looks good. I think you missed replacing one of the placeholder "John Doe" somewhere though.


NO-ISSUE: Update images

Description

Update image service images
How was this code tested?

No tests
Assignees

/cc @gamli75
/cc @adriengentil
Links

Checklist

[x] Title and description added to both, commit and PR
[x] Relevant issues have been associated
[x] Reviewers have been listed
[x] This change does not require a documentation update (docstring, docs, README, etc)
[ ] Does this change include unit tests (note that code changes require unit tests)

/lgtm
/approve


apns2.credentials: since version 2.0.0 pyJWT encode method return str

PyJWT latest version (2.0.0) introduce the following breaking changes:

encode method now return a str instead of bytes
python 3.5 is no longer supported

see release notes for more informations: https://github.com/jpadilla/pyjwt/releases/tag/2.0.0

@manderj @Pr0Ger Could you please resolve the conflicts and do a release? Dependabot is bumping up the pyjwt to 2.0.0. So I guess that the project compatibility should be fine.

@manderj @Pr0Ger Could you please resolve the conflicts and do a release? Dependabot is bumping up the pyjwt to 2.0.0. So I guess that the project compatibility should be fine.

PyJWT has implemented their own typing in 2.0.0 which is not yet used by default by mypy.
Mypy is still running on old PyJWT stubs (https://github.com/python/typeshed/pull/4854)
To resolve the failed checks mypy can be run directly alongside the latest package probably juste by adding PyJWT in[ drone-pytools requirements file](https://github.com/Pr0Ger/drone-pytools/blob/master/requirements.txt) ?

PyJWT has implemented their own typing in 2.0.0 which is not yet used by default by mypy.
Mypy is still running on old PyJWT stubs (https://github.com/python/typeshed/pull/4854)
To resolve the failed checks mypy can be run directly alongside the latest package probably juste by adding PyJWT in[ drone-pytools requirements file](https://github.com/Pr0Ger/drone-pytools/blob/master/requirements.txt) ?

PyJWT < 2.0.0 is in conflict with some common python packages like python-social-auth.


remove duplicate clousure file

The clousureAlias file was renamed to  closureAlias and this has caused our pod branch to have two copies of the file cause it not to compile.
This pull request removes the extra file.

Have tested an iOS project with this file removed and the KituraKit pod compiles


Main product image does not change according to product variant

main product image does not change according to product option.

This is indeed a needed feature. Anyone working on this?


why ripper crash

why ripper crash  when i rip game

No promises, but you can try my AssetRipper fork.


incorrect function call ?

In https://github.com/erdtman/cose-js/blob/master/lib/encrypt.js#L309
the createContext function is called without a value for the alg parameter.
      keyLength[alg] * 8, // keyDataLength is then evaluated to NaN.
Is that on purpose ?
I found this error while porting the code to typescript.

That seems wrong

Something went wrong

I had a deeper look and it looked like work in progress without tests so I removed that section to not confuse things. The section should likely look very much like the one above since it only supports one recipient as it stands today.


Docs site down cannot access through geist-ui-svelte.dev

Currently there is an issue with the docs sites SSL certificate. This seems to be a problem with the registrar.
If you are here and having trouble accessing our docs try https://geist-ui-svelte.vercel.app

Site is back up


Always returns error "plugin_not_installed"

Trying to use the plugin in a Ionic2 app and following the examples I could find however when I try to run getToken it always returns with an error of plugin_not_installed.
 is added in my config.xml and its in my plugins directory installed. As well as
import { Geolocation, Firebase } from 'ionic-native';
At the top of my file. Have removed my ios and android builds and recreated them and still get the same error.

Hello, which version of Ionic do you use ? Can you please provide some code sample ? config.xml ? ionic info ?
Thank you

Sorry it was an issue on my part. Dumb issue on my part from late night coding. Wasn't waiting to platform was ready.


Add API to remove the static iSCSI configurations from a specified host

Add function Remove-VMHostStaticiSCSITargets to remove static iSCSI configuration.
Motivation: This can be used when adding/removing new hosts to AVS deployment
Testing: We have tested it on local VMware deployments (not in Azure) using PowerShell Pester tests

@hfanan looks like you need to rebase on latest.

@hfanan looks like you need to rebase on latest.

Done


[UNR-2600] Offloading & Authority & Startup actor fixes

Description
TODO
4.22 Engine PR: https://github.com/improbableio/UnrealEngine/pull/337
4.23 Engine PR: https://github.com/improbableio/UnrealEngine/pull/338
Release note
TODO
Tests
Not tested with offloading yet.
Documentation
TODO
Primary reviewers
@mattyoung-improbable

Gonna conflict with my changes for making startup Actors work as desired with zoning, will come find you after lunch to ask questions, I can generally just rebase off you though

Added the discussed changes: https://github.com/spatialos/UnrealGDK/pull/1762/commits/eec686e100baae5d6c21cefccf7ee9ddc43b5c01
@mattyoung-improbable @m-samiec

Updated with the latest suggestions, added changelog notes.

4.24 Engine PR: https://github.com/improbableio/UnrealEngine/pull/391


refactor(traverse)!: TraverseCtx::ancestors do not return Ancestor::None

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

#5295  👈
#5294
main

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

Join @overlookmotel and the rest of your teammates on  Graphite


7-Zip failing to install (0x8a15004a)

After the package was recently updated in the last two days 7-Zip fails to install in the SYSTEM context with the following error:
Found 7-Zip [7zip.7zip] Version 22.01
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Successfully verified installer hash
Starting package install...
An unexpected error occurred while executing the command:
0x8a15004a : Arguments for msiexec are invalid
This was working perfectly fine before the manifest was updated.

Is that MSI application?

Yes, it's MSI:
Installer:
Installer Type: wix
Installer Locale: en-US
Installer Url: https://7-zip.org/a/7z2201-x64.msi
Installer SHA256: f4afba646166999d6090b5beddde546450262dc595dddeb62132da70f70d14ca
Release Date: 2022-07-15

Is that MSI application? Silent Switches are quite differently. Most MSI use /quiet.

I'm using the following command which has worked for over a year: & $wingetPaths install --id Zoom.Zoom --silent --accept-package-agreements --accept-source-agreements

The manifest contains some NullSoft applications but it did not display out on 7zip.7zip instead of MSI 7zip.7zip

So I still get this: PS C:\Windows\system32> winget install --id 7zip.7zip --silent
Found 7-Zip [7zip.7zip] Version 22.01
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Successfully verified installer hash
Starting package install...
An unexpected error occurred while executing the command:
0x8a15004a : Arguments for msiexec are invalid
Are you suggesting that --silent needs to be removed from the command? I'm confused why that is now breaking it.

So I still get this: PS C:\Windows\system32> winget install --id 7zip.7zip --silent Found 7-Zip [7zip.7zip] Version 22.01 This application is licensed to you by its owner. Microsoft is not responsible for, nor does it grant any licenses to, third-party packages. Successfully verified installer hash Starting package install... An unexpected error occurred while executing the command: 0x8a15004a : Arguments for msiexec are invalid
Are you suggesting that --silent needs to be removed from the command? I'm confused why that is now breaking it.

Must have been a delay for my device, it's working perfectly now. Thanks for your help and prompt response :)

Must have been a delay for my device, it's working perfectly now. Thanks for your help and prompt response :)

The delay is waiting for the pull-request to publish.

When I add Installer Slient Switch: /S,  it look like MSI returns an error but only exe works. When I add Installer Silent Switch: /quiet. It look like exe does not work. Most likely, I can try to use custom commands. Also, Azure Pipelines did not report Validation-Installation-Unattended-Failure

It look like Installer Silent Switches is unable to use in the root nodes. It failed on the Validation-Pull-Request

See winget warning.
Manifest validation failed.
Manifest Error: Schema Error. [Schema validation failed.
Error context: [Installers][0][InstallerSwitches] Description: Value type not permitted by 'type' constraint.
Error context: [Installers][0] Description: Failed to validate against schema associated with property name 'InstallerSwitches'.
Error context: [Installers] Description: Failed to validate item #0 in array.
Error context: [Installers][1][InstallerSwitches] Description: Value type not permitted by 'type' constraint.
Error context: [Installers][1] Description: Failed to validate against schema associated with property name 'InstallerSwitches'.
Error context: [Installers] Description: Failed to validate item #1 in array.
Error context: [Installers][2][InstallerSwitches] Description: Value type not permitted by 'type' constraint.
Error context: [Installers][2] Description: Failed to validate against schema associated with property name 'InstallerSwitches'.
Error context: [Installers] Description: Failed to validate item #2 in array.
Error context: [Installers][3][InstallerSwitches] Description: Value type not permitted by 'type' constraint.
Error context: [Installers][3] Description: Failed to validate against schema associated with property name 'InstallerSwitches'.
Error context: [Installers] Description: Failed to validate item #3 in array.
Error context: [Installers][4][InstallerSwitches] Description: Value type not permitted by 'type' constraint.
Error context: [Installers][4] Description: Failed to validate against schema associated with property name 'InstallerSwitches'.
Error context: [Installers] Description: Failed to validate item #4 in array.
Error context:  Description: Failed to validate against schema associated with property name 'Installers'.
] File: 7zip.7zip.installer.yaml
Manifest Warning: Unknown field. [Silent]
Manifest Warning: Unknown field. [Silent]
Manifest Warning: Unknown field. [Silent]
Manifest Warning: Unknown field. [Silent]
Manifest Warning: Unknown field. [Silent]
Manifest Warning: Silent and SilentWithProgress switches are not specified for InstallerType exe. Please make sure the installer can run unattended.
Manifest Warning: Silent and SilentWithProgress switches are not specified for InstallerType exe. Please make sure the installer can run unattended.
Manifest Warning: Silent and SilentWithProgress switches are not specified for InstallerType exe. Please make sure the installer can run unattended.


Rate limit exceeded on search of user followings amount of 40

I see this helper is got activated for search of user followings for result of 40 users I try to debug and see where is the problem, but I didn't spot something maybe someone familiar with the project could take a look from this I see its send parameter for max_results of 40, but I don't know why the rate limit is triggered for that low result as in Postman is working fine. I think it needs to be checked.
i.g.r.t.helpers.AbstractRequestHelper    : Rate limit exceeded, new retry ....
amount = 40;
 public List<UserV2.UserData> getUserFollowing(String userId, int amount) {
        AdditionalParameters parameters = AdditionalParameters.builder()
                .maxResults(amount)
                .build();

        UserList following = twitterClient().getFollowing(userId, parameters);
        List<UserV2.UserData> data = following.getData();

        return data;

If you have a rate limit response, it is because the Twitter API was called too much by your account, there is no relation with the library.
See here : https://developer.twitter.com/en/docs/twitter-api/rate-limits

The future is good I am closing the issue  to not spam.Thank


new shortcut method "get_object_or_none" added.

There exist a method known as get_object_or_404. Same as this method I have added get_object_or_none.
This will reduce the line of code for many users

Closing per ticket-2659.


Multi project build doesn't compile with Gradle 5.x

One of our multi project builds is currently failing to compile.
Expected Behavior
./gradlew assemble should compile as it does in Gradle 4.x
Current Behavior
Fails compilation with:
> Task :views-json-testing-support:compileGroovy FAILED
startup failed:
/Users/graemerocher/dev/grails/views/json-testing-support/src/main/groovy/grails/views/json/test/JsonViewUnitTest.groovy: 6: unable to resolve class grails.plugin.json.view.test.TestRequestConfigurer
 @ line 6, column 1.
   import grails.plugin.json.view.test.TestRequestConfigurer
   ^

/Users/graemerocher/dev/grails/views/json-testing-support/src/main/groovy/grails/views/json/test/JsonViewUnitTest.groovy: 5: unable to resolve class grails.plugin.json.view.test.JsonRenderResult
 @ line 5, column 1.
   import grails.plugin.json.view.test.JsonRenderResult
   ^

Context
This issue is blocking us trying to create the first milestone on Grails 4.x
Steps to Reproduce (for bugs)

git clone git@github.com:grails/grails-views.git
git checkout gradle-5
./gradlew assemble

Your Environment

Gradle 5.0 and 5.1 rc1

Could you please make sure this is not a consequence of Gradle now separating compile and runtime scopes of artifacts with Maven metadata?
See this breaking change note for reference.
An easy way to figure that out would be to compare the output of ./gradlew dependencies --configuration compileClasspath between the current Gradle version used by the project and 5.0

yes I already reviewed that. As far as I can see the views-json-testing-support module has a direct compile dependency on the views-json module:
compile project(":views-json")

The classes that it cannot find during compilation are found in that module. In additional it is possible to compile only the views-json-testing-support if you compile only that project,  the compilation error occurs only if you run ./gradlew assemble from the root project.

@ljacomet It's a project dependency, so this does not apply.
@graemerocher Have a look at the jar that is generated for your views-json project. It's a Spring Boot fat jar, not the normal project jar and thus it cannot be used to be compiled against. Seems like you are replacing the normal jar with the spring boot jar.

Wow, this must be a change in the boot plugin, sorry for the hassle.


when componentDidUpdate data-src is different from src

Describe the bug
The presentation is correct usually, but when I update the parent component,and the props is correct,so the data-src is correct, but I find the src is not updated。
here is :
export class LazyImage extends React.Component {

    static propTypes = {
        alt: PropTypes.string,
        srcset: PropTypes.string,
    }
    componentDidMount() {
        document.lazyLoadInstance.update();
    }

    componentDidUpdate() {
        document.lazyLoadInstance.update();
    }

    render() {
        const { alt, srcset } = this.props;
        return (
            <picture>
                <source type='image/webp' data-srcset={srcset}/>
                <img data-src={srcset} className="lazy" alt={alt} url={srcset}/>
            </picture>
        );
    }
}

export default LazyImage;

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
LazyLoad version
Please report which version of LazyLoad you're using.

Version [12.0.0]

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

Yes that's because, to save memory and CPU time, once an image has been loaded it gets "unwatched" by LazyLoad. If you change the data-src value again, make sure to call LazyLoad's load(element, true) (the second parameter is force) to load it again, as @RaZeR-RBI was suggesting in #361.


Add Kubernetes CLI integration tests

Codecov Report

Merging #101 (d328f2b) into main (10c93c1) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #101   +/-   ##
=======================================
  Coverage   80.24%   80.24%
=======================================
  Files          15       15
  Lines         815      815
=======================================
  Hits          654      654
  Misses        114      114
  Partials       47       47

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 10c93c1...d328f2b. Read the comment docs.


Crash on android 5 Lenovo

I don't have stacktrace but crash reproduced every time when open ScanActivityImpl, lib version is  1.0.5126

Thank you for reporting @Olexiy98 . Do you know what model device the crash occurred on specifically?

Meizu m2 note

Is there any way you can get a stack trace? I am attempting to get ahold of one of these phones, but it's difficult.

Hi @Olexiy98 , we've updated the version of TFLite we use in the app. Please try with the latest release 2.0.0017.
Here is the original bug that was marked fixed in TFLite: https://github.com/tensorflow/tensorflow/issues/31114

I'm closing this issue since I believe it has been fixed. Please feel free to re-open it if it reoccurs.


DOC:stats: Fix levy and levy_l descriptions

Both discriptions incorrectly stated that the PDFs were valid at x == 0, which would imply that it's possible to divide by 0.

Reference issue

None
What does this implement/fix?

The documentation for the levy and levy_l distributions said that the PDF was valid at x == 0, which would imply that it was possible to divide by 0.
Additional information

The limit of the pdf as $x \rightarrow 0$ is 0, so I'm not sure that it's wrong.

I found a paper that also says x must be greater than 0: https://www.researchgate.net/publication/287520272_Some_Inferences_on_the_Levy_distribution

The limit of the pdf as x -> 0 is 0

I'm not sure that matters. Limits only say that a function approaches a value, not that it reaches it. It's like how we get derivatives by taking the limit as h -> 0, even though it wouldn't make sense to actually have h = 0.

I know, but that doesn't mean that the distribution's PDF is not defined to be zero at zero.
I'll merge this based on the citation.


chore(main): release 1.11.1

:robot: I have created a release beep boop
1.11.1 (2023-10-30)
Bug Fixes

🐛 修复 macOS 打包失败的问题 (37e2837)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/viarotel-org/escrcpy/releases/tag/v1.11.1 :sunflower:


Do not repeatedly flush in poll_close.

The current implementation of FramedWrite2::poll_closerequires its inner poll_flush and poll_close to succeed before being ready. This may repeat the inner flush operation because the following poll_close may not be ready.
Especially with bounded futures::channel::mpsc::Senders this may cause a number of flushes if the channel has reached its capacity. Since each Sender has one additional slot, if poll_flush causes a message to be sent, it will occupy this slot. If the subsequent poll_close also results in a send operation it may often not be ready immediately. The next poll_close call will again send the message corresponding to poll_flush and may not be ready to send the close message. With many senders, this may repeat for a substantial number of times.

Then again the current approach is less racy, i.e. it is guaranteed that no concurrent operation can sneak in between the finished flush and the close, so we better leave it as is.


update nina and velux adapter in stable

RE-CHECK!

Automated adapter checker
ioBroker.nina

:thumbsup: No errors found
ioBroker.velux

:thumbsup: No errors found

[ ] :eyes: [W505] setTimeout found in "main.js", but no clearTimeout detected

Add comment "RE-CHECK!" to start check anew

RE-CHECK!

Automated adapter checker
ioBroker.nina

:thumbsup: No errors found
ioBroker.velux

:thumbsup: No errors found
Add comment "RE-CHECK!" to start check anew

Can you also please update the fixed stable version then in the PR for velux
:-)

update the version

Thank you!


Add TriggerContext object

Summary
This introduces the TriggerContext object discussed in this PR comment and resurfaces TriggerContextData via TriggerContext.Data
Testing
Import this TriggerContext object into your trigger file and attempt to use it in replacement of any use of templatized strings (ex. "{{data.interactivity}}")
import { Trigger } from "deno-slack-api/types.ts";
import { TriggerContext, TriggerEventTypes } from "deno-slack-api/mod.ts";
import SubmitIssueWorkflow from "../workflows/submit_issue.ts";

const submitIssue: Trigger<typeof SubmitIssueWorkflow.definition> = {
  type: TriggerTypes.Event,
  name: "Submit an issue",
  description: "Submit an issue to the channel",
  workflow: "#/workflows/submit_issue",
  event: {
    event_type: TriggerEventTypes.ReactionAdded,
    channel_ids: ["C012345T"],
  },
  inputs: {
    channel: {
      value: TriggerContext.Data.Event.ReactionAdded.channel_id,
    },
    team_id: { value: TriggerContext.TeamId },
    enterprise_id: { value: TriggerContext.EnterpriseId },
    event_id: { value: TriggerContext.EventId },
    event_timestamp: { value: TriggerContext.EventTimestamp },
    type: { value: TriggerContext.Type },
  },
};

If you're going to test this end to end, be aware that TriggerContext values may be returned as null and cause runtime failures if being used in a non-nullable field.
Requirements (place an x in each [ ])

[x] I've read and understood the Contributing Guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.

Closing for now as we determine the right way to surface these common properties that don't actually exist for every trigger


Adjust read pool test timeouts

thread ‘server::readpool::tests::test_full’ panicked at ‘assertion failed: rx.recv_timeout(Duration::from_millis(50)).is_err()’, src/server/readpool/mod.rs:292:9

Seems not happen any more.


Support property graph creation over views

What happens?
As highlighted in #158 it is currently not possible to create a property graph containing a view. Internally views are ViewCatalogEntry instead of TableCatalogEntry, which we rely on to figure out whether the PK-FK relationship is correct for the vertex tables and edge tables. Perhaps we can do something to support views as well. Or we should choose to not support this, but it is worth an investigation at least.
To Reproduce

OS:
macOs 13 - Apple M1 Pro
DuckDB Version:
v1.1.2
DuckDB Client:
CLI
Full Name:
Daniel ten Wolde
Affiliation:
CWI
How did you load the extension?
Built from source
Did you include all relevant data sets for reproducing the issue?
Yes
Did you include all code required to reproduce the issue?

[X] Yes, I have

Did you include all relevant configuration (e.g., CPU architecture, Python version, Linux distribution) to reproduce the issue?

[X] Yes, I have

Currently not going to pursue this as we need to know the schema for the property graph. If there is enough request I might reconsider in the future

I'm also encountering this error in NodeJS using duckdb 1.1.3, really don't know how to solve this... Steps to reproduce.
import { createDirectory } from "@yoda-assistant/utils";
import { afterAll, beforeAll, describe, it } from "vitest";

import { Database } from "@/duckdb";

describe("geocoding", () => {
    let db: Database;

    beforeAll(async () => {
        await createDirectory("tmp");

        db = await Database.create("tmp/graph-test-db.db", {
            access_mode: "read_write"
        });

        // Install and load the Arrow extension
        await db.run(`INSTALL arrow; LOAD arrow;`);
        await db.run(`INSTALL fts; LOAD fts;`);
        await db.run(`INSTALL duckpgq FROM community; LOAD duckpgq;`);
        await db.run(`UPDATE EXTENSIONS;`);
    });

    it("duckpgq function should return expected string", async () => {
        const res = await db.all("SELECT extension_name, installed, description FROM duckdb_extensions();");
        console.log(res);
    });

    it("should create a temporary schema", async () => {
        await db.run(`
            CREATE TABLE Person as SELECT * FROM read_json('assets/persons.json');
            CREATE TABLE Person_knows_person as  SELECT * FROM read_json('assets/persons-edges.json');
        `);
    });

    it("should return the number of rows in the Person table", async () => {
        await db.exec(` CREATE PROPERTY GRAPH snb
          VERTEX TABLES (
            Person
          )
          EDGE TABLES (
            Person_knows_person SOURCE KEY (Person1Id) REFERENCES Person (id)
                                DESTINATION KEY (Person2Id) REFERENCES Person (id)
            LABEL Knows
        );`);
    });

    it("should return a graph result", async () => {
        const res = await db.all(`SELECT CAST("element_id(p)" AS "JSON") as test FROM GRAPH_TABLE (snb
                                                                                MATCH p = ANY SHORTEST (a:Person WHERE a.firstName = 'Jan')-[k:knows]-> +(b:Person)
            COLUMNS (element_id(p), vertices(p), edges(p), path_length(p), b.firstName)
                                                                                )
                                  ORDER BY firstName
                                      LIMIT 5;

        `);
        console.log(res);
    });

    afterAll(async () => {
        await db.close();
    });
});

thanks for the repro, but what error are you actually getting?
Just to add to Daniel's remark on not supporting views: DuckPGQ also uses ROWIDs to quickly construct a CSR data structure with dense node and vertex numbers (used in path finding). And VIEWs in DuckDB do not have ROWIDs, as this is coupled to table storage.


Palette command "Open in Notebook Editor" not functional

Environment data

VS Code version: 1.51.1
Extension version (available under the Extensions sidebar): v2020.11.358366026
Jupyter Extension version (available under the Extensions sidebar): v2020.11.358541065
OS (Windows | Mac | Linux distro) and version: Win 10
Python and/or Anaconda version: 3.8.6
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): venv
Jupyter server running: Local

Steps to reproduce:

Create test.ipynb with content

{
 "metadata": {
  "language_info": {
   "codemirror_mode": {
    "name": "ipython",
    "version": 3
   },
   "file_extension": ".py",
   "mimetype": "text/x-python",
   "name": "python",
   "nbconvert_exporter": "python",
   "pygments_lexer": "ipython3",
   "version": "3.8.6-final"
  },
  "orig_nbformat": 2,
  "kernelspec": {
   "name": "python3",
   "display_name": "Python 3.8.6 64-bit",
   "metadata": {
    "interpreter": {
     "hash": "dc33fc19570b4b278fa70787b867f471bafaa41b19b180fd264f469f8e7754ae"
    }
   }
  }
 },
 "nbformat": 4,
 "nbformat_minor": 2,
 "cells": [
  {
   "cell_type": "code",
   "execution_count": null,
   "metadata": {},
   "outputs": [],
   "source": [
    "a = 1"
   ]
  }
 ]
}

and set "jupyter.useNotebookEditor": false, in settings

Right-click on test.ipynb in the File Explorer sidebar and choosing Open in Notebook editor will open it correctly in the notebook editor

Double-click on test.ipynb in the File Explorer sidebar opens it as JSON (as expected due to settings). But now, running the command Jupyter: Open in Notebook Editor from the command palette does nothing.

Expectation: it re-opens the JSON-format test.ipynb in the Notebook editor

Thanks for the bug. I believe exposing this to the palette was not intended. It would never have worked. That command is supposed to only be on the menu.
We should either remove it from the palette or fix it.

The bug is here:
https://github.com/microsoft/vscode-jupyter/blob/922deb2d4793e4d6b0a6883e0d45b861434f0046/src/client/datascience/interactive-ipynb/nativeEditorCommandListener.ts#L118
On a palette command (as opposed to the menu command), the file URI is always undefined. This code could be fixed with another if statement that checks for an empty URI and then uses the active document instead.

Thanks for the feedback! However, we don't have plans on addressing this issue in the near future.


AuthenticatedAgentUserJunctionDAO

Authenticated Agent User Junction DAO

Restrict users from creating a junction object where they are the source user (Agent)
Restrict users from finding and selecting junction objects they are not referenced to. (Agent or Entity)
Restrict users from removing junction objects where they aren't the source user or target user (Agent and Entity)

Tests incl. as AuthenticatedJunctionDAOTest

Troy' comments were handled offline and agreed upon. Here's the summary of our conversation:
patrick [10:54 AM]
The authenticatedUserUserJunctionDAO you created doesn't account for the possiblilty of the agent within the context
It currently exists within nanopay aswell and would need to be ported over
and by making the authenticatedAgentJunctionDAO simpler, I'm not sure what you mean by that

On a different note, I think we need a 4th requirement, which is to prevent the group from being changed by the agent or the entity to one that has permissions the caller doesn't have. It's the same way we prevent users from updating their own group in AuthenticatedUserDAO.

^ I agree
We can address this later on\
Troy [10:59 AM]

The authenticatedUserUserJunctionDAO you created doesn't account for the possiblilty of the agent within the context

I don't think it should be checking the agent. If we check the agent then how are you supposed to act as a business and add someone to your business?

It currently exists within nanopay aswell and would need to be ported over

True, but I don't see why it couldn't be ported over. It doesn't use any nanopay-specific models or code.
patrick [11:00 AM]
We'll need to extend this authenticatedJunctionDAO to account for permissions allowing users to add to the junction
Troy [11:01 AM]

and by making the authenticatedAgentJunctionDAO simpler, I'm not sure what you mean by that

It would be simpler because it wouldn't have to duplicate all of the logic from the generic AuthenticatedUserUserJunctionDAO
patrick [11:01 AM]
This extended authenticatedJunction will be extend within our nanopay platform
AuthenticatedUserUserJunctionDAO was created for something other than the agentJunctionDAO
I believe it satisfies conditions required for the partners functionality

True, but I don't see why it couldn't be ported over. It doesn't use any nanopay-specific models or code.

Troy [11:02 AM]

AuthenticatedUserUserJunctionDAO was created for something other than the agentJunctionDAO

It was written so we wouldn't have to duplicate authentication decorator logic every time we have a junction DAO between two users. This is a perfect use case for it.
patrick [11:03 AM]
^ it'll require alternations already provided by the AuthenticatedAgentJunctionDAO
A verbal conversation continued to conclude that the AuthenticatedAgentJunctionDAO will be extended to include business permissions and prevent groups from being added to the userJunction will be addressed later.

I think this was superseded by https://github.com/nanoPayinc/NANOPAY/pull/5495.

superceded by https://github.com/nanoPayinc/NANOPAY/pull/5495


Aggregate disposes twice in Ix

Related to #93 except not isolated to SelectMany. I can see from that Aggregate_ is calling IAsyncEnumerator<TSource>.MoveNext, which internally is calling Dispose in the case of AsyncEnumerable (and not just in it's catch clause, but also in it's MoveNextCore for the case of some of the internally implemented enumerables. Then Aggregate_ calls Dispose again.
Minimum repro:
        [TestMethod]
        public async Task TestEnumerator()
        {
            int count = 0;
            int disposeCount = 0;
            var enumerator = AsyncEnumerable.CreateEnumerable(
                () => AsyncEnumerable.CreateEnumerator(
                    async (ctx) =>
                    {
                        // Return 2 values
                        return (count++) < 2;
                    },
                    () =>
                    {
                        // All values are 1
                        return new[] { 1 };
                    },
                    () =>
                    {
                        // Dispose
                        disposeCount++;
                    }));

            var unused = await enumerator.Count();

            Assert.AreEqual(1, disposeCount);
        }

This is at least as of the latest in nuget, which is v3.1.1.

Defer till C# 8?


[WIP] Modal keyboard cheatsheet

Created scripts/modal.js, styles/_modal.scss, views/partials/modal.html

Updated scripts/index.js, styles/index.scss, views/layouts/main.html to include modal files

Bonus: corrected minor typo in bower_components/basecoat.readme.md

Looks like the actual tests are passing but CI is failing because of linting issues. Try running standard --fix locally which will automatically fix some of the formatting issues. The rest you may have to fix manually.

@snidelyhazel this is looking great. I am traveling this week but will review it in detail soon.

Thanks for the PR! This was finished up in #2088


HSTS preload list status (HTTP security)

:clipboard: Description
A clear and concise description of the new badge.

Which service is this badge for

Chrome's HTTP Strict Transport Security (HSTS) preload list

What sort of information should this badge show?

HSTS status hsts | status
Status may be preloaded, pending or unknow
Link should points to https://hstspreload.org/?domain=github.com

Examples

Edit: Replace no with unknow
:link: Data
Where can we get the data from?

Is there a public API?

https://hstspreload.org/api/v2/status?domain=github.com

Does the API requires an API key?

No

Link to the API documentation.

https://hstspreload.org/

Edit: Replace no with unknow
:microphone: Motivation
Please explain why this feature should be implemented and how it would be used.

What is the specific use case?

Show HTST approval status.
Track approval and regressions in real time. Alert on potential miss configuration.
Promote security for a safer Internet

Kind of related to #2912 and https://github.com/mozilla/http-observatory/issues/96

I've started work on this in a feature branch.
I noticed that the API returns unknown rather than no for both invalid and non-preload URIs. Should I keep it as no in the badge content?

I noticed that the API returns unknown rather than no for both invalid and non-preload URIs. Should I keep it as no in the badge content?

How about not preloaded?

How about not preloaded?

I'd vote for that as well

@paulmelnikow, that sounds good to me. :+1:
I think that the Firefox HSTS list is based on Chromes list afaik. :thinking: But if mentioning Chrome is more useful, I'm up for that.

Yes Firefox use the same list

Most major browsers (Chrome, Firefox, Opera, Safari, IE 11 and Edge) also have HSTS preload lists based on the Chrome list. (See the HSTS compatibility matrix.)

I've started work on this in a feature branch.
I noticed that the API returns unknown rather than no for both invalid and non-preload URIs. Should I keep it as no in the badge content?

Maybe unknow (red) is more explicit 🤔

How about not preloaded?

I'd vote for that as well

Ok 👍 Will change to unknown again 😋
And yeah, I was just using your examples for the colours 👍

Yeah pending is a good thing but it's still not preloaded.. I was thinking about yellow (less alarmist than orange) 🤔

That sounds great to me. 👍

I'm a little confused how we could go from a message indicative of a definitive "no" to an inconclusive "unknown" state.
I know you'd prefer the hsts label, but if you want to use green|yellow|red badge colors then I'd suggest considering a badge label such as hsts preloaded with statuses such as yes, pending, no.
The concern with using unknow (which I assume should actually be unknown) is that badge colors are all associated with a status, and red is indicative of failure. It looks odd to have a color indicating failure with a conflicting, inconclusive message

I'm a little confused how we could go from a message indicative of a definitive "no" to an inconclusive "unknown" state.

Because when I made the issue I was stupid, and only thinking about myself. I prefer matching the HSTS workflow semantics

I know you'd prefer the hsts label, but if you want to use green|yellow|red badge colors then I'd suggest considering a badge label such as hsts preloaded with statuses such as yes, pending, no.

If you are choosing to add an hsts badge to your readme, of course unknow is a failure, and should be red. Otherwise you don't add an hsts badge at all.

The concern with using unknow (which I assume should actually be unknown) is that badge colors are all associated with a status, and red is indicative of failure. It looks odd to have a color indicating failure with a conflicting, inconclusive message

The thing with hsts and unknown (not unknow 😉 ) is that the API returns the same state whatever you have an hsts HTTP header, set to preload or not, and submitted or not. That's why there only is an unknown I think 🤔
Let's focus on the badge and NOT on the hsts API.. of let's open an issue on their repo 😄
My opinon: Stick to the API, focus on the badge

What we do at Shields is make badges that convey information as clearly as possible. That sometimes means using slightly different semantics or terminology than upstream APIs. We value consistency and clarity in the badges over strict adherence to the upstream terminology. You'll find lots of examples of code in Shields that smooths out the rough edges in APIs. Not that we always do this perfectly! But it's what we strive for. That's the sense in which we focus on the badge.
An argument could be made that unknown makes sense from the context of the API. However in the context of a badge, I agree with @calebcartwright that unknown is completely uninformational. It sounds like a transient error, whereas the intended message is "this host is not in the list." That's not the absence of information, it's a real failure.
I still think not preloaded could work, and to avoid any confusion with pending, that could be changed to preload pending.
Other possible alternatives: unknown host or not listed.
hsts preload is tempting, though since "preload" is more of a state than a noun, it feels nicer to push it into the right text if possible.

I understand that unknown isn't particularly helpful, not preloaded is what is shown when using the hstspreload.org website. @paulmelnikow, so you are suggesting the following? 🙂

And @calebcartwright is suggesting:

Personally I prefer the first, but I think I'll wait until we come to a conclusion before updating to the final look. 😋

@paulmelnikow thanks for your arguments, I agree 👍
@pxgamer I also personally prefer the first 👍

@paulmelnikow thanks for your arguments, I agree 👍
@pxgamer the second proposition from @calebcartwright looks super clean 😮 👍

hsts preload is tempting, though since "preload" is more of a state than a noun, it feels nicer to push it into the right text if possible.

This is my response from above.
Think I still feel that way; that

conveys meaning more elegantly than

in a similar way that

is more elegant than

Yeah but the badge is much more about specific HSTS preaload service than HSTS in general.
The HSTS preload service is not part of the HSTS (HTTP Strict-Transport-Security) specification.
It may be important not to reduce HSTS to HSTS preloading, and to be explicit in the label of that specific badge 🤔

Chromium is a bit restrictive as the list is used by Chrome, Firefox, IE, etc...

Most major browsers (Chrome, Firefox, Opera, Safari, IE 11 and Edge) also have HSTS preload lists based on the Chrome list.

https://hstspreload.org/
Also it's a bit long for nothing..

That seems quite long. But it definitely is informative on which hsts this is.
Thinking about this, should the links stay as /hsts/{uri}.svg, or be something like /hsts/preload/{uri}.svg?

To the best of my knowledge there is only one HSTS preload list 😉

I haven't heard of any others, but it is the Chromium project's list. :yum: I'm not too bothered about whether or not we include Chromium.

 come on 🙄
Some people have to show many badge, on a single table in a readme.. one row of badge per environments. The name "Chromium" adds no relevant informations.. it's quite implicit to the HSTS preload list project.

My concern is about providing enough context to people who are reading this badges, particularly those who haven't heard of this. Let's keep the feedback constructive, please.
After reading some more and marinating for a couple days, I'm think I'm convinced. Let's do this:

Keep the badge label hsts preloaded with yes, pending, no.
Put "Chromium" in the title in the Shields badge listing, e.g. Chromium HSTS preload.
Link to the HSTS preload list and the list submission site in the badge documentation.

@paulmelnikow super cool!
Juste a little thing about the documentation, are you sure you want to link to the HSTS preload list on GitHub https://github.com/chromium/hstspreload instead of the main Chromium project page https://www.chromium.org/hsts ?

Hah, no, I think I must be confusing that repo with some other page I was looking at. I thought the actual list was in that repo, though it's somewhere else entirely: https://cs.chromium.org/chromium/src/net/http/transport_security_state_static.json
Honestly none of these links are very newcomer friendly! Though I guess https://chromium.org/hsts is the closest.

Just pushed points 1 and 2. For number 3, where do I add the links to?

How's this sound?

Strict-Transport-Security is an HTTP response header that signals that browsers should only access the site using HTTPS.
For a higher level of security, it's possible for a domain owner to preload this behavior into participating web browsers. Chromium maintains the HSTS preload list, which is the de facto standard that has been adopted by several browsers. This service checks a domain's status in that list.

@paulmelnikow, here's how it looks:

@paulmelnikow Your intro is nice, but yes we should use https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security#Preloading_Strict_Transport_Security intro as it specify those really important things:

While the service is hosted by Google, all browsers have stated an intent to use (or actually started using) the preload list. However, it is not part of the HSTS specification and should not be treated as official.

Can you add it to the PR? The formatting looks odd. Are you using  tags?
No worries if it doesn’t look perfect. The frontend styling is a work in process.

@paulmelnikow, done. It's using <p> tags, but should it be all one line? Or is there a line-length limit? (I wrapped it a bit.

It’s interpreted as plain HTML which isn’t whitespace sensitive (a space and a newline are treated the same). So line breaks are fine.