return app name, version and description at root path when opened in browser

closes #253

👋 @gr2m Thanks for opening this up. I took a look and I don't think these changes allow the user to overwrite the / path if they want to. I added a test case to document this here --> https://github.com/probot/probot/pull/255

Hmm good catch :/ ... I wonder if there would be a solid way to find out if a custom route is defined for the root path. If it’s not, maybe instead of showing the info page we should redirect to /probot and show the info page there? That would have the benefit that all probot apps would have that info page available ...

🤔 Ya I'm not sure I have a good answer. That's why I only opened a PR for the test case 😉 We might be able to add a middleware at after all the plugins& their routers have been loaded. By default express middlewares are used in the order in which they are registered. Here's an example of adding an app.use after all the other routes have been registered.

Feels a little hacky but I think we could register it right before server.listen gets called. https://github.com/probot/probot/blob/60558f92b647807a8e9fe0d023715e69879007ba/index.js#L70

I did this and wrote some tests around it, it seems to work..? Let me know what y'all think:
app.get('/', (req, res, next) => {
  // Get list of routes using '/'
  const pathsToIndex = app._router.stack.filter(path => path.route && path.route.path === '/')

  // If there is more than one route using '/', it means there is a custom
  // handler somewhere. Move on to that handler instead of this one.
  if (pathsToIndex.length > 1) {
    next()
  } else {
    res.redirect('/probot')
  }
})

Closing this out in favour of #279


include,test,sunos: Oracle Developer Studio support.

Oracle Solaris linker visibility support.  Option "-fvisibility=hidden"
requires public functions to be defined as "__global".
fs_utime_round test failed as timespec.tv_nsec conversion to double
resulted in negative number.  Skipped this test.
Note that it was necessary to compile with C99 language features.

The C99 option was necessary because of other changes in v1.42.0 and not due to changes provided here.
Compiler version used:
$ /opt/developerstudio12.6/bin/cc -V
cc: Studio 12.6 Sun C 5.15 SunOS_i386 152882-05 2019/10/30

Hi there!  This breaks libuv on illumos systems.  Can we revert this please?
@alls0rts Where does __global come from?

@jclulow https://github.com/libuv/libuv/pull/3371

Thanks @cjihrig !
As an aside, in future, I'm totally around to be CCed on anything that affects the sunos/illumos bits.  I recognise we're a somewhat boutique platform, but I can help with builds and tests and whatever.

We have a @libuv/smartos team that currently has no members. Would you (or anyone else) like to be added there?

Yes I think so!  Can we rename it @libuv/illumos ?

Done and done. Thanks for volunteering.

We have a @libuv/smartos team that currently has no members. Would you (or anyone else) like to be added there?

Please feel free to add me too. I mostly work on OmniOS which an illumos distribution shipping libuv. Thanks.

@citrus-it Invite sent.


Inlining and variable capture

When Boogie inlines the spec of b inside foo, the bound variable "a" in ensures clause conflicts with the parameter "a" of foo. Is this a known bug/feature, and how to people get around it (e.g. obscure names of bound variables in quantifiers)?
For the following program foo.bpl
type ref;
var arr:[int]int;

procedure {:inline 1} b()
modifies arr;
ensures (forall a:int  :: {arr[a]} a < 10 ==> arr[a] == 0);
{
}
procedure foo(a:ref)
modifies arr;
{
   call b();
}

When I generate the inlined version:
boogie /noVerify foo.bpl /printInstrumented > foo_1.bpl
and remove the first/last lines (Boogie verifier ...), then I get the following type checking error:
boogie /noVerify foo_1.bpl
Boogie program verifier version <IP_ADDRESS>016, Copyright (c) 2003-2014, Microsoft.
foo_1.bpl(40,19): Error: more than one declaration of variable name: a
foo_1.bpl(40,29): Error: trigger must mention all quantified variables, but does not mention: a
2 name resolution errors detected in foo_1.bpl

That is a bug. Boogie should rename the "a" in the quantifier (both in the "ensures" clause as in the example, and also if there was a quantifier over "a" somewhere in the body of the inlined procedure), just like it currently renames any local variables of the inlined procedure.
Rustan


ComfyUI desktop install error

I tried installing this through comfyUI desktop but got error saying:
ComfyUI-3D-Pack install failed: Bad Request

I just went through the trouble of installing this yesterday, sharing my experience:

To solve the Bad Request error in the manager UI, change bypass_ssl = False to bypass_ssl = True in ComfyUI_windows_portable\ComfyUI\custom_nodes\ComfyUI-Manager\config.ini (pointed out here)
Even after this, the package will fail to load because of missing dependencies. You will have to look at the terminal output for missing packages and install them manually using python shipped with ComfyUI (e.g. C:\ComfyUI_windows_portable\python_embeded\python.exe -s -m pip install [missing-package]). Some of the packages off the top of my head that need to be installed manually: omegaconf, kiui, nvdiffrast (must be installed by cloning their repository and building it locally), ninja, torch_scatter (see next), pytorch3d (must be installed by cloning their repository and building it locally), onnxruntime/onnxruntime-gpu, diffusers==0.29.0, xformers==0.0.28.post3.
Installing torch-scatter requires copying include and libs folders from a full python installation to the portable one ComfyUI ships with (check which version ComfyUI is using, install the same version of python locally and copy these folders from python installation to ComfyUI_windows_portable\python_embeded\).
Some workflows seem to have missing custom nodes that don't get detected by the manager, though I've only run into "IMG_padder" node in CharacterGen_to_Unique3D.json workflow so far. This is an outdated node from Eden.art_nodesuite package where it has been renamed to "Eden_IMG_padder" in recent versions (hence why it doesn't get detected by the manager's resolver), so if you're going to use that workflow you'll have edit it by manually replacing all occurrences of "type":"IMG_padder" with "type":"Eden_IMG_padder" in that file with a text editor.

Hope this helps.


Delta Component Text doesn't match LiveSplit

Looks like it can show just "Delta", which is not what LiveSplit does.

https://github.com/CryZe/livesplit-core/blob/624b8ff398fc4ccd76438fc518ca3846aded93c3/src/component/delta.rs#L82-L91
Doesn't account for if the comparison_override isn't selected so just defaults to "Delta". Will fix today when I have a place to plug in my laptop 😬

Keep in mind, that text is also used for the name in the layout editor, which apparently doesn't match the text shown on the component for this component, which is the actual reason for this bug (most other components do). So if you fix this, make sure that both of them are correct. Maybe we want a test to ensure this stays correct. I'm not sure, you decide.

That commit works, however A) I'm not sure it's the prettiest/cleanest way and B) rustfmt-nightly refuses to install on my computer for some reason (I probably need to update rust itself) so formatting


Fix use of memoize

Description
The typescript-memoize library does not work for generators. Only the first call was yielding results. Therefore, I converted all the functions that utilize the @Memoize annotation to return normal lists.
Type of change

[x] Bug fix
[ ] New feature
[ ] Breaking change

Related issues

Fix #1

Migration notes

Describe migration notes if any

Extra info

Add any additional information

Each stream is tested independently so there were no cases yet where the memoized function was called more than once.

Can we add a test an check that it's being called exactly once? so we could test for memoize being used

I'll try to check. As I understand we need to check that function called exactly only and this function is in AsyncGenerator func?


Fix failure to start game on invite of other player

To test, start the activity and invite another player,
when they join they will get an 'failed to launch' error.
This was happening since a function was not found.

We should port to the new framework from Sam P.


Allow external TLS termination with rancherd

Allow rancherd helm chart to set the -tls external to allow a Rancher installation with an external L7 Load Balancer with SSL termination.
gzrancher/rancher#13002

@davidnuzik - This is an important feature for any customer using AWS, Azure, etc.


how to import cell h:mm with maatwebsite/excel 3.1

Closing due to inactivity. Please feel free to re-open if needed.


Blocks in Attachment

Hey,
Can you add Blocks in SlackAttachment, please ?
ref : https://api.slack.com/messaging/composing/layouts#adding-blocks
Thanks
You're doing an amazing job

Updated package available on nuget...


[dv/chip] change condition order in resolve_sw_image_paths

Hi,
This PR changes the condition order in the resolve_sw_image_path method in the chip_env_cfg file to check for silicon_creator before checking for new_rules.
This required specifically for tests that defined with both new_rules and silicon creator like the following test, in which the flash image created with _silicon_creator as its suffix.
https://github.com/lowRISC/opentitan/blob/13e9917aca2db743554ec8f3e9a55128c115c78c/hw/top_earlgrey/dv/chip_rom_tests.hjson#L805-L810
This PR comes with PR #24284

#24306 cherry-picks this commit to the earlgrey_1.0.0 branch.


when a single result is searched it does not show in the list ?

🐛 Describe the bug

In a local deployment I am getting this result for a search:

The API search request is:
http://localhost:8080/PDS_APIs/pds_doi_api/0.2/dois?ids=*insight_cameras%3A%3A5.0*
gives the following result:
[
  {
    "doi": "10.13143/a2t9-za69",
    "identifier": "urn:nasa:pds:insight_cameras::5.0",
    "node": "eng",
    "status": "draft",
    "submitter"<EMAIL_ADDRESS>    "title": "Laboratory Shocked Feldspars Collection #1",
    "update_date": "2022-03-11T00:38:48+00:00"
  }
]

📜 To Reproduce
Steps to reproduce the behavior:

Go to 'ui' search
Search for a string which returns a single result
See error saying 1 result is found but not showing it in the table

🕵 Expected behavior

The result should show in the table.
📚 Version of Software Used

latest version on main branch
🩺 Test Data / Additional context

🏞Screenshots

🖥 System Info

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

🦄 Related requirements
⚙ Engineering Details

Actually it is not because of the single result because now I can see a single result, see screenshot

The cause might be the status a this single result which was only reserved when I first made the search.
I am thinking the bug might be a discrepancy between the way the number of rows is counted and the rows which are actually displayed.

@tloubrieu-jpl I wasn't able to reproduce this one. The value that you pointed out will return an empty array. When I try to to get a different single value it will show. Also to test I hard coded the response:
[  {    "doi": "10.13143/a2t9-za69",    "identifier": "urn:nasa:pds:insight_cameras::5.0",    "node": "eng",    "status": "draft",    "submitter"<EMAIL_ADDRESS>   "title": "Laboratory Shocked Feldspars Collection #1",    "update_date": "2022-03-11T00:38:48+00:00"  }]
And it will still show that single value.
Maybe there was a different kind of error that occured for you in that image?

@tloubrieu-jpl l did a lot more testing but I still can't reproduce this one. Are you still getting this? If not maybe we can close this one?

We are closing this ticket because we are not able to reproduce


IS-15622: Adding $original_source to share pipes

Just a comment, the "defaults" template will add the "$original_source" property automatically if it is not already there. I'll roll out a PR for that asap, but this is good as a temporary workaround.


WARNING: An illegal reflective access operation has occurred

Even though the program works, I get this warning every time:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by com.sun.xml.bind.v2.runtime.reflect.opt.Injector (file:/usr/local/bin/ia-rcade) to method java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int)
WARNING: Please consider reporting this to the maintainers of com.sun.xml.bind.v2.runtime.reflect.opt.Injector
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release

Java version:
openjdk version "11.0.2" 2019-01-15
OpenJDK Runtime Environment 18.9 (build 11.0.2+9)
OpenJDK 64-Bit Server VM 18.9 (build 11.0.2+9, mixed mode)

My system: Macbook Pro 2017, Macos Mojave

OK, this is confirmed, I have the same issue with JDK 11 on Linux. Java is in a deprecation process of some parts of its API. Pretty annoying. I'll take a look and fix this asap.
Thanks for reporting me this issue.

Fixed by da82ad4


Protocol: ethernet

Return active interfaces, error if none.

So, you mean to define a new interface called NetworkInterface that will check the stats?  and create implementation for each one ?
type NetworkInterface interface {
Name() string
IsActive() (bool, error)
Stats() (map[string]interface{}, error)
Type() string
Scan() ([]string, error)
}

The idea is to print information about active interfaces to confirm that at least one is connected. It is a common check when troubleshooting this kind of problems.


Chatlog mode for observers

The chatlog mode when the obs are talking between them is incorrectly parsed, returning 33554432 instead of 0x02 (so obviously, the formatter isn't working either).

Fixed in #13


[Feature Request]: Plan for Integration with Google Cloud Services

Feature Description
This feature aims to enhance the functionality of the Terminal by enabling its integration with a variety of cloud-based services. By doing so, the Terminal will become a more versatile tool that can be utilized in numerous beneficial ways by users. Whether it's data storage, machine learning, or other computational services, this integration feature will allow the Terminal to tap into the vast resources available in the cloud, thereby significantly expanding its capabilities and usefulness.
Motivation
This feature is crucial because it leverages the power of Go, a statically typed, compiled language known for its efficiency and scalability. The Terminal's AI chat interface, being developed in Go, is not only independent but also virtually limitless in its capabilities. The only constraints it may encounter are runtime errors, which are well-handled within the Go environment. This feature, therefore, addresses the challenges of scalability and efficiency in AI chat interfaces, providing a robust and reliable solution.
Possible Implementation
Any cloud-based service that can be useful for humans
Alternatives Considered
Alternatives will be considered once the version reaches 1.0 or higher.
Additional Context
No response

📢 Updated


feat(index.html): add dialogs/texts to index. changed table to tables

ref #276.
Description
This PR adds Texts and Dialogs to index.html (docs).
Compatibility
N/A
Caveats
For now I think it's better to just add some CSS to the Dialog, because I was thinking if we put a button that opens a dialog in the demo, without any overlay, it will look weird.
And if we add an overlay just for the demo, people will open bug issues because they're using dialogs and it will not show any overlay, it's going to be confusing.

I've also changed from Table to Tables (just the word at the demo, and ids), because other components are pluralized and this one wasn't.
Also found one bug regarding the Dialog component, but I will open another issues for that.

I think the following demo is good 👍
Because it's a dialog including the style of backdrop.

<button type="button" class="nes-btn" onclick="document.getElementById('default-dialog').showModal();">Open dialog</button>
<dialog class="nes-dialog" id="default-dialog">
  <form method="dialog">

Dialog

Alert: this is a dialog.

    <menu class="modal-menu">
      <button class="nes-btn">Cancel</button>
      <button class="nes-btn is-primary">Confirm</button>
    </menu>
  </form>
</dialog>

.modal-menu {
  padding: 0;
  text-align: right;
}

And if we add an overlay just for the demo, people will open bug issues because they're using dialogs and it will not show any overlay, it's going to be confusing.

Could you let me know more about this? 🙏

Could you let me know more about this?

My mistake, for some reason the overlay wasn't showing up in my very old notebook, maybe with the browser version or OS.
But I've tested your demo code in my PC and your demo looks better :+1:
What should I do?

Close this PR and you make a new one using the demo code you've provided;
Change the code in this PR to the demo you've provided.

Also, should we add 4 buttons (or 4 checkboxes) to show the diversity of the dialogs (is-dark, is-rounded) or just one is fine?

I'll fix it and push it to this branch🛠

should we add 4 buttons (or 4 checkboxes) to show the diversity of the dialogs (is-dark, is-rounded) or just one is fine?

It's better to have 4 buttons.
*

@guastallaigor I fixed it 🛠
Could you review this changes? 🙏

@guastallaigor I fixed it
Could you review this changes?

Thank you for changing it @BcRikko.
LGTM, but if I may give a suggestion, adding this would save more "screen space".
#dialogs > section {
  display: inline-block;
}

Also, we can check this is another issue/PR, but there isn't a white border in the dialog (ref #281) when it's opened:
index.html

storybook

But it is showing up right in the storybook. I'm checking it but I haven't found the cause of this.
Anyway, this is great and good to merge, thank you.

Oh my gosh 😇
Browsers other than Chrome cannot use dialog element. 😭
https://caniuse.com/#feat=dialog

@guastallaigor  I fixed bug of dark dialog border. 🛠
and I added dialog polyfill for other than Chrome 😇

Oh my gosh
Browsers other than Chrome cannot use dialog element.
https://caniuse.com/#feat=dialog
The first suggestion you made is good.

Make sense then, I didn't thought about that. Because when I first test it, I used firefox on my notebook.

I think everything is good to merge for now, since it's a demo :+1:
You can merge it when you can.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Winget can't find installed package to uninstall

Brief description of your issue
I installed FreeCAD via winget and now I'm unable to uninstall it.

Steps to reproduce
Install FreeCAD with winget install FreeCAD.FreeCAD
Attempt to uninstall with winget uninstall FreeCAD.FreeCAD
Expected behavior
program should be found an uninstalled.
Actual behavior
Winget cannot find installed package
Environment
Windows Package Manager v1.2.10271
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.22000.613
Package: Microsoft.DesktopAppInstaller v1.17.10271.0

Install 0.19.3
Upgrade to 0.19.4
Uninstall doesn't work because it installed FreeCAD side-by-side:

This will be fixed by a winget-pkgs PR: https://github.com/microsoft/winget-pkgs/pull/58902
cc @cbc02009: You will need to make sure to uninstall the old version of FreeCAD from your PC so that upgrades will continue to work or otherwise WinGet will get confused and won't know which version of FreeCAD to upgrade.

I tried it out and repro the same experience.  1 version uninstalls fine, but with two it gets muddled.  I created #2129 for this, although I feel like I've done so in the past but couldn't find it.

We've been working on the side-by-side scenarios. You could try the latest release and enable the experimental feature on:

https://github.com/microsoft/winget-cli/releases/tag/v1.8.924-preview

Please provide feedback at:

https://github.com/microsoft/winget-cli/discussions/4281

Is this still a problem with WinGet 1.8?


Let the Android embedding adopt OnPreDrawListener

Internal bugs: http://b/190767277, http://b/185423816
Using https://developer.android.com/reference/android/view/ViewTreeObserver.OnPreDrawListener to delay when Flutter's activity first draws can help solve

getting more accurate https://developer.android.com/topic/performance/vitals/launch-time measurements
not require a custom Flutter splash screen transition on top of the Android OS's splash screen and the subsequent Android S splash screen breaking change (b/185423816)

Things this might involve:

Update https://flutter.dev/docs/development/ui/advanced/splash-screen#android-launch-screen
Support a compatibility mode with the old way. Likely by letting this be configurable via FlutterView constructor argument and letting there be intent builder flags defaulting to yes on FlutterActivity/FlutterFragment/FlutterFragmentActivity

@jiahaog any updates on this issue? Let me know if you want me to take a look, and go ahead with the PR.

One consideration to make though wrt https://github.com/flutter/flutter/issues/85139 is that it still can't make Android's first frame a correct measurement of Flutter's first frame, since Android's first frame will still be
[Flutter's first frame] + [time needed to jump from raster to main thread and get a next Android vsync] = [Android's first frame].

Yes, I've started looking at it, will follow up with a PR soon

Support a compatibility mode with the old way. Likely by letting this be configurable via FlutterView constructor argument and letting there be intent builder flags defaulting to yes on FlutterActivity/FlutterFragment/FlutterFragmentActivity

What about if we check if the user has supplied a io.flutter.embedding.android.SplashScreenDrawable by calling https://github.com/flutter/engine/blob/40edba381e758e4abaaa4e59192748f12eb97895/shell/platform/android/io/flutter/app/FlutterActivityDelegate.java#L432, if true, then we don't add OnPreDrawListener. Otherwise, we opt into this new mode?
Also, is there a valid use case for this custom splash screen API? could we deprecate it, and document that it's not longer needed?
@xster any thoughts?

@blasten we may still need a flag - users may still want to provide io.flutter.embedding.android.SplashScreenDrawable / provideSplashScreen for APIs < 31, while at the same time using the Android S splash screen. (unless we do option 2 below)
There are a few approaches I can think of:
Option 1: Support the Flutter-specific splash screen for APIs >= 31
There may be a jarring transition here depending on how users set up their Flutter splash screen. But in this case, we continue to show the provided drawable.
This will require a flag roughly named useLegacySplashScreenAboveAPI31 for this discussion, which will probably be read from the users' AndroidManifest.xml. The following table tries to enumerate possible use cases of how users may configure their app, and the behavior on the API versions.

Android S APIs used to configure the Android splash screen
Users who do not provide io.flutter.embedding.android.SplashScreenDrawable or provideSplashScreen
Users who provide io.flutter.embedding.android.SplashScreenDrawable or provideSplashScreen

API <31
Not supported
Use preDraw; the Android embedding will not show any Flutter-specific splash screen
Don't use preDraw; the Android embedding should use the provided drawable as the splash screen

API >=31
Android S default behavior
Use preDraw; the Android embedding will not show any Flutter-specific splash screen
Introduce a new flag useLegacySplashScreenAboveAPI31 defaulting to true.  - When enabled: preDraw will be disabled, the user provided drawable will be shown as the Flutter splash screen (possible jarring transition).  - When disabled (ideal state): predraw will be enabled, the user provided drawable will not be shown|Use preDraw; the Android embedding will not show any Flutter-specific splash screen

The guidance here is for users who want to show a splash screen to do the following, which are not mutually exclusive

To target API < 31, continue to use io.flutter.embedding.android.SplashScreenDrawable or provideSplashScreen
To target API >=31, set useLegacySplashScreenAboveAPI31 to false and use the Android S splash screen APIs

Option 2: Don't support the Flutter-specific splash screen for APIs >= 31
Another approach is to use preDraw unconditionally for APIs >= 31. This is probably breaking, since the provided splash screens through io.flutter.embedding.android.SplashScreenDrawable / provideSplashScreen will not be shown.

Do we need to worry about the V1 embedding? I also noticed the existence of the io.flutter.app.android.SplashScreenUntilFirstFrame option, but this appears to only be used for V1.

Jotting down my findings as well about how it works today on cold start.
API < 31

android:theme on activity is shown
show io.flutter.embedding.android.SplashScreenDrawable / provideSplashScreen if present
Crossfade to Flutter

API 31

Android S splash is shown
<possible jarring transition because Android S splash is not nessarily aligned with 2 or 3>
show io.flutter.embedding.android.SplashScreenDrawable / provideSplashScreen if present
Crossfade to flutter

Thanks Jia.
I was under the impression that the custom Flutter splash screen was added because we didn’t know that we could delay showing the Android view hierarchy until Flutter painted the first frame.  If this is true, then this feature is not longer necessary.
I’d like to see a real world use case where a secondary splash screen is needed because the oficial Android splash screen isn’t sufficient. have you seen this case internally?

Note that onPreDraw() has been available since API level 1.

From what I can see, most use cases internally point their io.flutter.embedding.android.SplashScreenDrawable to @drawable/launch_background.xml. The same @drawable/launch_background.xml is also referenced by the android:theme of the Activity, as the android:windowBackground. There is one instance where the app uses provideSplashScreen to offset the same @drawable/launch_background.xml by the status bar height. I'm not really sure why, but I reached out to the author.

Thanks Jia.  Do we still need the flag useLegacySplashScreenAboveAPI31 or could we still use the same check from https://github.com/flutter/engine/blob/40edba381e758e4abaaa4e59192748f12eb97895/shell/platform/android/io/flutter/app/FlutterActivityDelegate.java#L432?

Not sure if we should reuse it - the linked check comes from the io.flutter.app.android.SplashScreenUntilFirstFrame option which users can set in their manifest, but it appears to be deprecated since it's only part of the V1 embedding. The naming also doesn't really match the semantics of what we're trying to do here as well.
I do like the simplicity of not having a flag though as you've mentioned. Do you know if there are other valid external use cases of manually providing a splash screen?

There's also the equivalent in the V2 embedding: https://github.com/flutter/engine/blob/138c91c614d742c52aa5432b4cb921f0ff9fdee2/shell/platform/android/io/flutter/embedding/android/FlutterActivityLaunchConfigs.java#L16

Right, I think we were both referring to that flag (io.flutter.embedding.android.SplashScreenDrawable) above. I set up a meeting to align on our approach to this offline 🙂

We synced up, next steps:

Verify if using preDraw and not using io.flutter.embedding.android.SplashScreenDrawable / provideSplashScreen causes a white flash on pre-Android S
If the white flash isn't an issue, make using preDraw the default, and add a manifest flag that controls the behavior on all API versions to allow users to opt-out

if users use io.flutter.embedding.android.SplashScreenDrawable / provideSplashScreen, print logs to direct them to documentation / migration guide
Then deprecate the io.flutter.embedding.android.SplashScreenDrawable / provideSplashScreen APIs

Verify that the proposed behavior doesn't do anything weird on add-to-app

Verify if using preDraw and not using io.flutter.embedding.android.SplashScreenDrawable / provideSplashScreen causes a white flash on pre-Android S

@jiahaog I just tested it on Android 30/ Moto G7.  No white splash. However, I do see the fade-out transition.
I changed the custom drawable bg color to purple, and I see a fade-out purple background that gets blended with the color I set in the initial Android splash screen.

Here's the code I added to FlutterView.java:
private void init() {
    // ... current code ... //
    this.getViewTreeObserver().addOnPreDrawListener(new ViewTreeObserver.OnPreDrawListener() {
      @Override
      public boolean onPreDraw() {
        return isFlutterUiDisplayed;
      }
    });
}

Yeah, I can reproduce that as well. I must have remembered something wrongly, apologies for the confusion. As discussed, I'll work on a PR for the following then:

if the white flash isn't an issue, make using preDraw the default, and add a manifest flag that controls the behavior on all API versions to allow users to opt-out

if users use io.flutter.embedding.android.SplashScreenDrawable / provideSplashScreen, print logs to direct them to documentation / migration guide
Then deprecate the io.flutter.embedding.android.SplashScreenDrawable / provideSplashScreen APIs

Update: Working on a PR for what was discussed above

https://github.com/flutter/engine/pull/27645 was rolled back in https://github.com/flutter/engine/pull/27788 because it broke some devicelab tests.

https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android hybrid_android_views_integration_test/2047/overview
https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_android embedded_android_views_integration_test/2044/overview

Will investigate and try to reland

@jiahaog https://github.com/flutter/engine/pull/27811 seems to have landed. Can we close this issue?

I think so


Refactor Job._execute (resolves #972)

resolves #972
refactored Job._execute into Job._executor and Job._runner and modified worker.py to use the new
context manager syntax of Job._executor.

Jenkins, test this please.

Jenkins, test this please.

Can we change the commit message to
Don't report job as success until caching cleaned up (fixes #972)

… by turning Job._execute() into a context manager that wraps the caching context manager.

Also, cacheInfo.jobState is now a defaultdict of dicts and not ints

Build seems to hang. Gonna kill it. Check out
AttributeError: '_JobState' object has no attribute 'jobSpecificFiles'

in the build log.

 Pushed a new one

@hannes-ucsc this is ready!

@hannes-ucsc this is ready! The only failure is a stats and logging error

Build failure tracked as #978.
Jenkins, test this please.

Jenkins, test this please.

Jenkins, test this please.

Build failure tracked as #978 for which a fix was merged into master since then.

Jenkins, test this please.

Build failure tracked as #760.

Jenkins, test this please.

This also resolved #963


Type parameter bounds can be marked "exact nullable" if upcast.

class B<T extends Object> {
  void f(T t) {
    // Create an edge from the bound to some type
    List<dynamic> x = [t];
    // and make that type exact nullable
    x[0] = null;
  }
}

This migration should produce no source edits.
Currently, the assignment from List<T> to List<dynamic> results in an edge from the bound of T to the dynamic type argument in List<dynamic>. This is correct.
But it has an unfortunate consequence, it means that when dynamic is marked exact nullable (by assigning null to the list index), that exact nullability is propagated upstream, and that is currently not stopped in any way from marking the bound of T as exact nullable.
We therefore get T extends Object? whis is unnecessary.
This occurs in package:async.

Related to https://github.com/dart-lang/sdk/issues/40552

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


schedule between hours

In schedulable I see you can create a schedule with a set time, but in ice_cube you can do something like
s=IceCube::Schedule.new(Time.now, duration: IceCube::ONE_HOUR)
which will set up a schedule (singular) between now and 1h
after which you can also do
s.add_recurrence_rule IceCube::Rule.daily
which will make it daily recurring in the interval of that hour
Is this possible in schedulable ?

Hours is currently not implemented yet. I'm aware of this and plan to do it.


UDP stream for raw radio signal

UDP stream for raw radio signal, once #4 is done. What about security/bandwidth? Configurable port number (default 50077?)

Or just stream the cooked bit values, see ideas-timepi.txt (not yet public).


Failed to inject profiler into

Hello there!
I have a problem to run async-profiler on Java within Kubernetes pod.
Docker image based on Alpine Linux and Java 17 and i send you a part of it related to async-profiler.
RUN mkdir /usr/local/async-profiler && wget -O /usr/local/async-profiler/async-profiler.tar.gz https://github.com/async-profiler/async-profiler/releases/download/v2.9/async-profiler-2.9-linux-musl-x64.tar.gz &&\
 cd /usr/local/async-profiler &&\
 tar -xzvf async-profiler.tar.gz &&\
 rm -f /usr/local/async-profiler/async-profiler.tar.gz &&\
 cp -R async-profiler-2.9-linux-musl-x64/ /opt/async-profiler

RUN apk add libgcc libstdc++ libstdc++6

Under container file system, async-profiler stored at /opt/async-profiler directory.
In the same issues on this repository, i found that i will need to manually attach profiler to Java as agent with this command  java -agentpath:/opt/async-profiler/build/libasyncProfiler.so=start,summary,flat -version. I try this and get this error:

Error occurred during initialization of VM
Could not find agent library /opt/async-profiler/build/libasyncProfiler.so in absolute path, with error: /usr/glibc/lib/libgcc_s.so.1: version `GLIBC_2.0' not found (required by /opt/async-profiler/build/libasyncProfiler.so)

How can i fix this?

Please use version 3.0.
async-profiler 2.9 is no longer supported.

Does async-profiler 3.0 have musl build?
Or default build successfully works with Alpine Linux on Kubernetes?

async-profiler-3.0-linux-x64 should work on Alpine, too.


PatternFly v6

Note: Current PF v6 package versions generate test failures
DO NOT MERGE

/ok-to-test


Support multiple carets/multiple selection

Example

Editor is no longer being worked on, and has been removed from the repo. Closing.


Run test suite (stestr) during release builds instead of stochastic_swap.py

Summary
I changed the test-command in [tool.cibuildwheel] to run the test suite stestr instead of running the old stochastic_swap.py script. I should work linux, macosx, and windows because the test command is not overriden
Details and comments
As it is a safecheck only I added the --abbreviate command to produce a shorter output and didn't activate the QISKIT_TEST_CAPTURE_STREAMS=1
Closes: https://github.com/Qiskit/qiskit/issues/12202
[Unitary Hack 2024]

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
4 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.03%) to 89.604%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
4
93.13%

Totals

Change from base Build<PHONE_NUMBER>:
0.03%

Covered Lines:
62524

Relevant Lines:
69778

💛  - Coveralls

Hi @ljcamargo,
While this effort looks like starting in the right direction, it seems that it wont make it before tomorrow's deadline. Of course, you are more than welcome to continue working on it and @mtreinish will continue reviewing it. However, it wont be eligible for the unitaryHack bounty.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
18 unchanged lines in 3 files lost coverage.
Overall coverage decreased (-0.02%) to 89.761%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/expr.rs
1
94.02%

crates/qasm2/src/lex.rs
5
92.88%

crates/qasm2/src/parse.rs
12
96.69%

Totals

Change from base Build<PHONE_NUMBER>:
-0.02%

Covered Lines:
63654

Relevant Lines:
70915

💛  - Coveralls


[Spaceship Tunes] Modification of app version's build is possible even when the version is waiting for review, in review, or pending developer release

New Issue Checklist

[ ] Updated fastlane to the latest version
[X] I have read the Contribution Guidelines

Issue Description
Complete output when running fastlane, including the stack trace and command used

You can use: --capture_output as the last commandline argument to get that collected for you

I have found that it is possible to change selected build in app edit version even though the version is waiting for review, in review, or pending developer release. Build cannot be changed in the iTunes Connect UI in either of the mentioned states. This is definitely an iTunes API bug and I have filed it in Apple bug reporter. Spaceship could also be enhanced to place these checks so that app versions are not left in undesirable state.
Environment
Please run fastlane env and copy the output below. This will help us help you :+1:
If you used --capture_output option please remove this block - as it is already included there.
🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.12.5

Ruby
2.3.1

Bundler?
false

Git
git version 2.11.0

Installation Source
~/.rvm/gems/ruby-2.3.1/bin/fastlane

Host
Mac OS X 10.12.5 (16F73)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.3.1/lib

OpenSSL Version
OpenSSL 1.0.2h  3 May 2016

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
8.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL

LANGUAGE

fastlane files:
No Fastfile found
No Appfile found
fastlane gems

Gem
Version
Update-Status

fastlane
2.43.0
🚫 Update available

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.0.0

executable-hooks
1.3.2

bundler-unload
1.0.2

rubygems-bundler
1.4.4

bundler
1.15.1

io-console
0.4.5

slack-notifier
1.5.1

claide
1.0.1

colored2
3.1.2

nanaimo
0.2.3

xcodeproj
1.4.4

rouge
1.11.1

xcpretty
0.2.4

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.5.0

babosa
1.0.2

colored
1.2

highline
1.7.8

commander-fastlane
4.4.5

faraday-cookie_jar
0.0.6

uber
0.0.15

declarative
0.0.9

declarative-option
0.1.0

representable
3.0.4

retriable
2.1.0

public_suffix
2.0.5

addressable
2.5.1

mime-types-data
3.2016.0521

mime-types
3.1

little-plugger
1.1.4

multi_json
1.12.1

logging
2.1.0

memoist
0.15.0

os
0.9.6

signet
0.7.3

googleauth
0.5.1

google-api-client
0.12.0

mini_magick
4.5.1

security
0.1.3

xcpretty-travis-formatter
0.0.4

json
1.8.6

excon
0.55.0

rubyzip
1.2.1

plist
3.2.0

faraday
0.11.0

faraday_middleware
<IP_ADDRESS>

http-cookie
1.0.3

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20161129

fastimage
2.0.1

unicode-display_width
1.1.3

terminal-table
1.7.3

generated on: 2017-08-02

Hey @PragyaTripathi ! Thanks for raising this issue. That is definitely something that we would love to have in spaceship. We would be more than happy to review a PR adding those checks! Is there any chance you would want to submit a PR with that change? If not, no worries and we will try to get to that as soon as we can, but we love first-time contributors to fastlane and can help anywhere that we can! 🚀  🐙

Will do, @ohayon!


建议增加支持postgresql 协程客户端

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

https://github.com/hyperf/db-pgsql-incubator


Question: Will all EventHandler events be replaced with TypedEventHandler?

Currently there are a lot of places with mixing two types of events like below from FlyoutBase.cs:
public event EventHandler<object> Closed;
public event EventHandler<object> Opened;
public event EventHandler<object> Opening;
public event TypedEventHandler<FlyoutBase, FlyoutBaseClosingEventArgs> Closing;

Is it planned to move all events to TypedEventHandler in WinUI 3?
It shouldn't be a breaking change, since (object sender, object _) event handler can work with both types of event.

Also I would love to see TypedEventHandler in .net core too, but there is another issue for that.
https://github.com/dotnet/runtime/issues/28289

@StephenLPeters
I am not sure, if I see relation between args and sender type.
There are already events with typed args in EventHandler.
TypedEventHandler is useful for typed sender, so we don't need to cast it in every handler method.

EventHandler<T> and TypedEventHandler<object,T> are functionally equivalent. But changing from the former to the latter for consistency would be a breaking change, and we're putting a high priority on avoiding breaking changes.


update

Hello to all,
I have done the update with pip3 (pip3 install GramAddict -U), but when I start the bot it always found a new version 3.2.1 and the actual version is 3.1.5.
How could I fix it?

Git pull
Or
gramaddict run --config yourconfigpath.yml

Git pull Or gramaddict run --config yourconfigpath.yml

I have done togheter with pull or gramaddict run and I obtain "Requirement already satisfied"
but when I start the bot I see the new version avaiable and actual version 3.1.5

You are doing something wrong.
Anyway create a new venv, activate and start the bot from there.
You can read the Readme or follow https://packaging.python.org/en/latest/guides/installing-using-pip-and-virtual-environments/

You are doing something wrong. Anyway create a new venv, activate and start the bot from there. You can read the Readme or follow https://packaging.python.org/en/latest/guides/installing-using-pip-and-virtual-environments/

thank you
solved


The Curse of Kelly (TCoK)

So, I currently trying to renaming the default branch (kellyos_main) into nckos_main. But whatever I trying, the kellyos_main would return back after I commiting a change. Currently I gonna find how to properly changing the branch. Discuss below for the solutions.
The title is a joke actually

It's over.


Refactored igemm kernel and solver for xdlops wrw fp32

Dedicated wrw solver with reduced tuning parameters
Dedicated wrw kernel instead of reusing fwd kernel
Changed loading dimension of matrix B from GemmN (CYX) to GemmM (NHW) for enabling vector load (up to 15% improvement)
Do not support group conv. in this PR

@zjing14 Does this retuning? If so, what needs retuning?

@zjing14 Does this retuning? If so, what needs retuning?

Yes, we need to retune wrw fp32.

@zjing14 Am I right that this new solver is factored out from some other "universal" solver? If it is expected to be always better with the subset of problem-configs it covers (the non-group WrW convolutions, I guess), then I recommend excluding this subset from that "universal" solver.

@zjing14 Sorry, I am raising comment after comment as I discover while making fp16/bfp16 specific wrw solver.

@zjing14 Merge conflicts

@daniellowell Merged.

This is a blocker for #203 due to this. It MUST be reverted and reworked to invokers.
Since #145 we should NOT use RunAndMeasure() in the new Solvers. The only reason that this PR has passed the tests is that #203 is not yet merged.
@daniellowell @DrizztDoUrden @alexandraBara @JehandadKhan @zjing14

The most recent comment is wrong.


How to correctly set up internal ip for django-debug-toolbar

First time i am editing setting.py file in google cloud computing please forgive me for this silly Question ...
i wanted to run django-debug-toolbar and followed every step in that tutorial. and the thing is i want the tool bar to be visible in our office only. So i just put our public address into INTERNAL_IPS like INTERNAL_IPS = ('182.74.xx.xx',) and i did restart run server. but the tool bar not visible. if changed back to <IP_ADDRESS> then tool bar also coming ...
Just open stackoverflow question also please answer that too .. thanks

Your question was anwsered on Stack Overflow.


how to pretrain model on

https://github.com/darrenjkt/MS3D/blob/f206aeb32095dcb805c51a963791f15724db6e9b/tools/cfgs/waymo_models/uda_secondiou.yaml#L5-L8
Hi authors!
Does it means we pretrain on waymo domain with only 5% of waymo data?

https://github.com/darrenjkt/MS3D/blob/f206aeb32095dcb805c51a963791f15724db6e9b/docs/GETTING_STARTED.md?plain=1#L36-L41
But GETTING_STARTED tell me that I should train it on 5Hz.
Is there something wrong with my understanding?


Set up the repository and move stuff from apify-sdk and apify-client here

I separated the PR into 3 commits. At first, I just copied the apify-client-python repository, and in the next commits, I did the changes to be able to see the changes I made.
Basically regarding the project setup I just removed the docs & test stuff.
The content of src/ was discussed on Slack with @fnesveda .
Closes #1.

Thanks, @fnesveda. I fixed the minor issues you mentioned, added unit tests, and also a few lines into README.

Thanks, @fnesveda, it should be fixed now.


Support binary and hexadecimal number encodings

For compatibility we want to support hexadecimal and binary number encodings, at least for input facts.
This requires the new syntax of prefixes  0x and 0b for integers.
It should also work during conversion of datatypes e.g. INT("0xF")

Probably worth it to also implement 0o for octal encoding, which comes up when, e.g., reasoning about unix file permissions.


Zoom Clone

Description 📜
It's a Zoom Clone with React JS using WebRTC
Fixes #918

Type of change 📝
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x] Add a new project

Domain of Contribution 📊
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x] Project using ReactJs

Checklist ✅
Please delete options that are not relevant. And in order to tick the check box just put x inside them for example [x] like this

[x] I have performed a self-review of my own code or work.
[x] My changes generates no new warnings.
[x] I'm GSSoC'22 contributor

Screenshots / Gif (Recommended) 📸

Review @khushi-purwar


v5 can break due to subpath imports - node+deno unable to resolve core modules re imports map

I reported this: https://github.com/nodejs/node/issues/51009
initially reported to tsx here: https://github.com/privatenumber/tsx/issues/425
The minimal repro from the tsx issue (on StackBlitz) uses p-limit for the demo.
I encountered the issue when bumping packages in a TypeScript cli project to current (including bumping p-limit v4 to v5) that runs via tsx (with module "ESNext" in the tsconfig).
The trigger of the issue in p-limit is right here:
https://github.com/sindresorhus/p-limit/compare/v4.0.0...v5.0.0#diff-e727e4bdf3657fd1d798edcd6b099d6e092f8573cba266154583a746bba0f346R2
Given the circumstances I'm not sure if you want to do anything differently, however I figured I'd create an issue here to put it on your radar, in case you want to accommodate on account of the popularity of this package. Thanks!

Someone else reported a similar issue with esbuild

@JonathonRP gotcha, thanks for the tip
Note tsx uses esbuild under the hood and is what I was using that led to me encountering + reporting this issue in the first place.
For future note if you comment with the issue link (or link direct to the specific comment), or if you reference the issue id, GitHub will take care of adding the mention to the issue feeds. Its fewer keystrokes than typing out "someone else reported..." and has the benefit of linking things up and tying them together :)
I'm going to comment over on #76 now how this is related

To be clear, Deno is not affected because of the subpath imports. The issue is async_hooks is experimental API that Node recommends migrating away from (https://nodejs.org/api/async_hooks.html) and Deno does not support it.
The following change to the package.json makes it "work" in Deno:
    "imports": {
		"#async_hooks": {
			"deno": "./async-hooks-stub.js",
			"node": "async_hooks",
			"default": "./async-hooks-stub.js"
		}
	}

Seems to also fail in tsup with:
ESM Build failed
Error: Build failed with 1 error:
../../node_modules/.pnpm/p-limit@5.0.0/node_modules/p-limit/index.js:2:28: ERROR: Could not resolve "#async_hooks"
    at failureErrorWithLog (/Users/segevfiner/prj/swimm/node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:1649:15)
    at /Users/segevfiner/prj/swimm/node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:1058:25
    at runOnEndCallbacks (/Users/segevfiner/prj/swimm/node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:1484:45)
    at buildResponseToResult (/Users/segevfiner/prj/swimm/node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:1056:7)
    at /Users/segevfiner/prj/swimm/node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:1085:16
    at responseCallbacks.<computed> (/Users/segevfiner/prj/swimm/node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:703:9)
    at handleIncomingPacket (/Users/segevfiner/prj/swimm/node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:762:9)
    at Socket.readFromStdout (/Users/segevfiner/prj/swimm/node_modules/.pnpm/esbuild@0.18.20/node_modules/esbuild/lib/main.js:679:7)
    at Socket.emit (node:events:517:28)
    at addChunk (node:internal/streams/readable:368:12)
CJS Build failed

@segevfiner for sure thanks for the explicit confirmation.
tsup uses esbuild, the same as tsx (which is what I was using when I first hit and reported this issue) so unfortunately this can be expected. You can downgrade p-limit to v 4.x and it should work for you.

I had a similar issue using tsx with p-limit v5. Downgrading to v4 fixed the issue (thanks @firxworx!)
Here's the error I had to help other people searching:
node:internal/url:1393
    throw new ERR_INVALID_URL_SCHEME('file');
          ^

TypeError [ERR_INVALID_URL_SCHEME]: The URL must be of scheme file
    at fileURLToPath (node:internal/url:1393:11)
    at finalizeEsmResolution (node:internal/modules/cjs/loader:1164:20)
    at Module._resolveFilename (node:internal/modules/cjs/loader:1106:16)
    at a._resolveFilename (/Users/work/ProgrammingProjects/[...]/node_modules/.pnpm/tsx@4.7.0/node_modules/tsx/dist/cjs/index.cjs:1:1729)
    at Module._load (node:internal/modules/cjs/loader:985:27)
    at Module.require (node:internal/modules/cjs/loader:1235:19)
    at require (node:internal/modules/helpers:176:18)
    at Queue (/Users/work/ProgrammingProjects/[...]/node_modules/.pnpm/p-limit@5.0.0/node_modules/p-limit/index.js:2:29)
    at Object.<anonymous> (/Users/work/ProgrammingProjects/[...]/node_modules/.pnpm/p-limit@5.0.0/node_modules/p-limit/index.js:4:25)
    at Module._compile (node:internal/modules/cjs/loader:1376:14) {
  code: 'ERR_INVALID_URL_SCHEME'
}

Node.js v20.11.0

Seems like it is an issue in Node.js itself: https://github.com/nodejs/node/issues/49257

hello, using patch-package you can do the following:
diff --git a/node_modules/p-limit/index.js b/node_modules/p-limit/index.js
-import {AsyncResource} from '#async_hooks';
+import {AsyncResource} from './async-hooks-stub';

hope that helps someone until the issue is resolved.

hello, using patch-package you can do the following:
diff --git a/node_modules/p-limit/index.js b/node_modules/p-limit/index.js
-import {AsyncResource} from '#async_hooks';
+import {AsyncResource} from './async-hooks-stub';

hope that helps someone until the issue is resolved.

Thanks, it helped me.
For clarity, I manually edited the node_modules/p-limit/index.js file and changed this part to import {AsyncResource} from './async-hooks-stub';

The latest version no longer uses subpath exports: https://github.com/sindresorhus/p-limit/releases/tag/v6.0.0


Implement filterBestKeypoints

test: add ID card crops for FM
chore: unignore scripts
test: start general FM test
fix: bug in checkBorderDistance
test: write general FM test
test: keypoints and descriptors should have same length
fix(getBriefDescriptors): add minBorderDistance option
fix: debug borderDistance
fix(orientedFastFeature): distance to border
refactor: move getRadius to own file
fix: remove keypoints too close to border
fix(getOrientedFastKeypoints): remove descriptorsPatchSize option
fix: keypoints and descriptors have same size
test(getFastKeypoints): star image from matlab
refactor: move getCirclePoints
feat: implement getDistanceMatrix
feat: implement getKeypointsInRadius
test: work on global FM test
feat: implement filterBestKeypoints
test(filterBestKeypoints): add more tests

This PR can be merged once #214 has been merged.


Make multithreading and fork helper functions separately configurable

Our feature, openenclave, uses the openssl library.
https://github.com/openenclave/openenclave
The openenclave environment supports pthread, but does not support getpid. These APIs are used by multithreading and openssl_get_fork_id private implementations (respectively) in threads_*.c files. (e.g. threads_pthread.c)
We would like it if it was possible to configure OpenSSL to use pthreads for multithreading, but not to use getpid. Possible solutions could be:

Define openssl_init_fork_handlers() and openssl_get_fork_id() in a source file outside of threads_*.c. Then our system could compile threads_pthread.c as we are now, but compile the new fork .c file with OPENSSL_SYS_WINDOWS defined.
Have multithreading and fork helper functions managed by separate macros/configuration options instead of just OPENSSL_SYS_WINDOWS

The openenclave environment supports pthread, but does not support getpid.

Does it support forking at all?

Does it support forking at all?

Openenclave does not support forking.

Maybe a "no-fork" option to disable fork protection features.


tft.py Reduce allocation when using transparency

Hi Robert, when using transparency this patch avoids allocating a buffer each time a string is output. The drawback is that the buffer remains in place, potentially after the need for it has passed. However in typical GUI applications strings are drawn repeatedly and it saves a lot of allocs which can eventually fail if the heap becomes fragmented.

Hi Peter, thanks for the PR. Preallocating the buffer is surely an efficiency improvement. Did you keep the row-by-row pixel structure I use in the fonts? Otherwise the displaySCR_charbitmap() function in TFT_io.py wouldn't work. I must say I lost that project a little bit out of sight, and hardly remember all the little details. The age, you know ...

Hi Robert, I think age has got the better of me this time.
When I created the branch I'd forgotten that my fork has diverged significantly from yours, so the PR includes a heap of changes I hadn't intended to include. If you look at the last commit you'll see that the change is very simple. It radically reduced OOM errors when running my GUI on a very fragmented Pyboard where it tried to allocate ~2K each time a screen was refreshed. However I can envisage applications where it could actually make things worse. It is, of course, entirely up to you whether to make the change.
These display boards seem harder to find these days so I don't know how many new users we're likely to get.

Hi Peter, I noticed the change to tft.py, and it looks good to me.
The TFT's are still available at buydisplay.com. They deliver pretty fast. Another source is www.eckstein-shop.de. I thought a while of rebuilding the lib using SPI and thge ILI3941 controller. But there is not need at the moment, especially since there are already libs offering that. They seem however lack a good font handling.

I have included the preallocation of the buffer required for transparency into my branch. Including the other changes is a little bit too much at the moment.

Fair enough - it was my error to include them in the PR.


test hyde theme

Following the steps from https://damien.co/blog/2020-05-26-hugo-tips-themes-config/ I created this trial. @mjang-cobalt please take a look.

Closing. Thank you for your work on this, @duroiucorina .


Missing basic cluster implementation

Problem
Missing basic cluster implementation
Proposed Solution
implement it

Not needed given import issues filed


Using app extension only API

Using the library not only in the "main" app but also in a Share extension, I am getting a warning
linking against a dylib which is not safe for use in application extensions: Carthage/Build/iOS/Connectivity.framework/Connectivity

The code probably only uses APIs that are "extension-safe", so it would be nice to check the box in the project settings to make the warning disappear.

Thanks


Strings that can be decoded / cracked in 2 crackers / decoders

ciphey -t "IkknbSBnb2luZyB0byBtdXJkZXIgdW5jbGUgYm9iIGF0IDZwbSB0b21vcnJvdw=="┏━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━┓
┃ Name of Cipher ┃ Probability ┃
┡━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━┩
│ Base           │      99.99% │
└────────────────┴─────────────┘

This is a base 64 string, but it returns as SHA256.
Returning {'lc': None, 'IsPlaintext?': True, 'Plaintext': 'CODE ERREUR : 005', 'Cipher': 'sha256', 'Extra Information': None}

This is because:

The string is the exact right size for SHA256
It just so happens, on one of our hash APIs, that the string has been calculated to be that.

This is a difficult situation.
Luckily, there are some things we can do with the (almost finished) cipher-iface branch!
Since a hash is binary data, AuSearch will decode the base64, and first check for further decodings. The chance of a SHA256 hash successfully decoding as UTF-8 is roughly 1 in 2^32 (4 billion). Even if someone really is that unlucky, that just means that we will waste time with that string, before cracking the hash.
Conversely, if it really is a UTF-8 string, any reasonably accurate AuSearch heuristic will leave the intensive sha256 cracking until later in the search.
One suggestion would be to add a tag system for the crackers, so that a user could disable/single out hash cracking, without having to rewrite large portions of the code base.
I would be interested to see people's feedback after Orwell is released, so that we can see whether this is worth implementing.

SHA256 is not cracked, it is searched up in an API - thus it is much faster than everything apart from the decoders. :disappointed:
I'm hoping this fixes it:

Since a hash is binary data, AuSearch will decode the base64, and first check for further decodings. The chance of a SHA256 hash successfully decoding as UTF-8 is roughly 1 in 2^32 (4 billion). Even if someone really is that unlucky, that just means that we will waste time with that string, before cracking the hash.

Ausearch is now reasonably accurate, so this should not be a problem anymore


How to connection in expressjs with cratedb??

Below mention connection trick apply but not connected
file:-typings.ts
declare module 'node-crate'{
var crate : any;
export default crate;
}
file:- app.js
import crate from "node-crate";
crate.connect('localhost', 4200);
Any body know how to connected  to cratdb in Expressjs
error accrued like this:--
[Node] TypeError: Cannot read property 'connect' of undefined
Thanks!!!............

This seems to be a client related question/problem. Could you please open that up in node-crate? (assuming that's the client you're using)
The repo and issue tracker here is mainly for server side related issues or feature requests. See also other support options


Inconsistency in enforcing mutability of claims

Describe the issue:
Currently, when the SCIM2 schemas endpoint (https://localhost:9443/scim2/Schemas) is called, the properties of the claims in urn:ietf:params:scim:schemas:extension:enterprise:2.0:User dialect are formed using the properties of the corresponding mapped local claim instead of the properties defined in <IS_HOME>/repository/conf/scim2-schema-extension.config file.
For an example even though the urn:ietf:params:scim:schemas:extension:enterprise:2.0:User:lockedReason claim's mutability is defined as read-only in scim2-schema-extension.config, the SCIM2 schema endpoint returns the below attributes which correspondent to the mapped identity claim - http://wso2.org/claims/identity/lockedReason which states the claim's mutability is read-write.
            {
                "uniqueness": "NONE",
                "displayName": "Locked Reason",
                "name": "lockedReason",
                "displayOrder": "0",
                "description": "Locked Reason",
                "mutability": "READ_WRITE",
                "type": "STRING",
                "multiValued": false,
                "caseExact": false,
                "returned": "DEFAULT",
                "required": false
            },

In the Console/MyAccount applications, the schema endpoint is used to manage the user profile attributes. Hence, the user profile attributes returned as read-write by the schema endpoint are allowed to be edited in the Console/MyAccount. However, Charon component validates whether the updated enterprise schema attributes are read-only against the configuration defined in scim2-schema-extension.config [1]. If the claims are defined as read-only in the scim2-schema-extension.config, Charon throws an error and resulting in a error.
[1] https://github.com/wso2/charon/blob/139c9170e1df0d56ce0e5db74bbf692eae915b6c/modules/charon-core/src/main/java/org/wso2/charon3/core/utils/PatchOperationUtil.java#L3564
How to reproduce:

Go to 'Attribute Dialects' in Console app.
Check 'Show this attribute on user profile and user registration page' in 'Locked Reason' claim and update. Do not tick 'Make this attribute read-only'.
Go to a user's profile in Console and try to update any detail (ex: Update mobile number).
When clicked on the update button following an error occurs as Charon throes an exception since 'Locked Reason' claim in the SCIM2 enterprise schema dialect is read only.

Expected behavior:
The mutability(or any other property) of the claims should be enforced using either the properties of the local claim or the properties of the corresponding enterprise schema claim, and that should be consistent in all the places.
i.e. If Schema endpoint returns the properties of the mapped local claims, the validations done by Charon when updating the claims should be done using the same properties.

On a side note, a claim can generally be one of the below types.

claims which can be viewed and edited by the end user
claims which can be viewed and edited by the admin
claims which can be edited by the server only

For the first two types of the above claims, the admin should be able to define the properties of the claims such as the mutability. Hence, it is preferred if we can use the properties of the claims in local dialect to enforce the behaviour of the claims.

We can change the http://wso2.org/claims/identity/lockedReason claim attribute through claim-config.xml file [1] as readonly so that we can avoid the issue. Likewise we can do this for all the claims which are having different values in claim-config and scim2-schema-extension.config file.
[1] https://github.com/wso2/carbon-identity-framework/blob/master/features/claim-mgt/org.wso2.carbon.claim.mgt.server.feature/resources/conf/claim-config.xml#L462

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


SIL: Use the right generic signature for computing SIL function type for coroutine accessors

The function type's generic signature will have already been dropped at this point if all generic parameters were fully concrete, so use the original generic signature to compute the reduced type of the yield type.
Fixes https://github.com/apple/swift/issues/61040.

@swift-ci Please smoke test

@swift-ci Please smoke test

@swift-ci Please smoke test macOS


sequence invoked with "error" parameter automatically fails

when i pass an "error" parameter to a sequence, it fails with that parameter as a return value. note that the sequence fails, without even invoking any of the components. also note that this only affects sequences, not individual actions.
this breaks slack oauth flows: when the user clicks Cancel in an oauth flow, slack calls my redirect_uri with an error parameter. but the issue seems to be unrelated to web-export. the undesirable behavior occurs even with conventional invocations.
here is an example:
echo 'function main(params) { return { code: 302, headers: { location: "https://google.com" }}}' > /tmp/foo.js

wsk action update foo /tmp/foo.js
wsk action update --sequence fooseq foo,foo

wsk action invoke fooseq -p error weird -br
{
    "error": "weird"
}
wsk action invoke fooseq -p error weird -b 2>&1 | grep status
        "status": "application error",
        "statusCode": 0,

wsk action invoke fooseq -p error_nope weird -br
{
    "code": 302,
    "headers": {
        "location": "https://google.com"
    }
}```

So we currently have a convention, obviously, that any action that returns a result with an "error" attribute is considered an error.
Seems clear that reserving the keyword "error" is a mistake.   Easy fix: use something like __OPENWHISK_ABNORMAL_EXIT instead.

the problem here is that none of my actions were even invoked... the sequence just prematurely fails without even invoking any of the components

Not to mention the action isn't returning an error property.

Can I bet of the fold?

@ioana-blue assigned to you speculatively.

ok ... so the check to abort a sequence based on "error" arguably should not apply to the first method in the outermost sequence .... although I could argue the other way and claim this is working as designed.
I still propose changing the keyword as a better fix.

Should not apply to the incoming invoke parameters - they are not the result of an action. Why do we need to change the convention to abort the sequence? This strikes me as completely orthogonal.

it's orthogonal, ok -- but the current convention sucks so let's fix it as long as we're touching that code?

Well if we change it it seems quite a change. Now actions might return error or some other property if they are stand alone vs composed in a sequence?

Also we should consider this https://github.com/openwhisk/openwhisk/issues/995#issuecomment-265589172.

of minor note: if we had a catch mechanism #1793, then i could have protected myself from this situation, by redirecting the user back to the origin page of my app.

This works as designed. There is even a test for it @rabbah see this:
https://github.com/openwhisk/openwhisk/blob/master/tests/src/system/basic/WskSequenceTests.scala#L107
Note zero actions being executed in the sequence is tested in this line (so works as designed) @starpit
https://github.com/openwhisk/openwhisk/blob/master/tests/src/system/basic/WskSequenceTests.scala#L113
I understand we need to change this. Some of the options discussed in this thread:

simply not apply the 'error' convention to the params of the topmost/outtermost action in the sequence
change the reserved keyword (while keeping the current behavior of checking whether the keyword is part of the incoming params)
change the reserved keyword and also do 1 above

Changing the name of the error property really is a different point. As in if the invoke parameters contained the property, whatever it is called, should the sequence really not run?
I think this behavior is wrong - thanks for pointing out the test.

Thanks for pointing out the test.
Changing the name of the error property really is a different point. As in if the (initial) invoke parameters contained the property, whatever it is called, should the sequence really not run?
I think this behavior is wrong or at the very least surprising - since it applies only to sequences. We should consider the two points separately (behavior if invoke time parameters specify the property for error, and name of the error property). Changing the name of the property to something less common is just hiding the behavior/making it less likely to happen in practice. It doesn't address the sequence vs non-sequence invocation semantic difference. I suppose we could disallow incoming parameters from specifying this property, as option 4... maybe?
Option 5 as alluded to by @starpit: provide catch and leave the rest as is - but also doesn't address semantic gap vs non-sequences.

I vaguely remember why we settled on this behavior/convention. I think we didn't want to treat sequences differently depending on where they appear wrt to other sequences/actions
E.g., s -> a, x , where a is an atomic action and x is a sequence. Under the current behavior, if the error property is received by s or x, no actions from those sequences get executed.
In the new behavior under discussion, it makes a difference whether the error property is received by initial parameter payload or is received as payload from a return from a previous action in a sequence.

in the new behavior under discussion, it makes a difference whether the error property is received by initial parameter payload or is received as payload from a return from a previous action in a sequence.

Or to put it differently, if the invoke time parameters are received by a sequence vs non-sequence (atomic) action. Since sequences are actions, should the semantics apply to all actions?

I can understand some kind of retval interpretation, but why would we ever have an inval squasher? In AX if A returns error then fine kill the sequence at that point.

@starpit I can imagine scenarios where the incoming params come from triggers through rules and then you can think of inval as retval.

Triggers don't have return values so I think I'm OK with that. If we insist they do, I persist: any retval of a trigger is just it's inval. And so we are back to squashing. Added on input, which we cannot do, because inputs may come from a world that does not obey our conventions.
And why isn't rejecting a promise sufficient for indication of error and thus shirt circuiting. Why would we ever need to invent a convention for this.

any retval of a trigger is just it's inval

That's how I think of triggers.

And why isn't rejecting a promise sufficient for indication of error and thus shirt circuiting. Why would we ever need to invent a convention for this.

Not sure I get this part. It may hold in a js only world, but how does it generalize to polyglot world?

We are agreed at least to fix this, so that failures no longer occur as a function of input values?

After all this discussion, I think I agree with @rabbah 's point of view, i.e., 1. the name of the error property is orthogonal to the way the error property is treated when received as parameter - by either topmost sequences or actions; and 2. the semantics for sequences should be the same as for actions since sequences are actions.
As such, I suggest for now I change the way the params with an error property received by a topmost sequence behave (i.e., the sequence will start execution and the error property short-circuit applies only to returned values).
I perceive the renaming of the error property a much more intrusive change because, to keep semantics the same for actions and sequences, we would need to rename the error property for atomic/simple actions as well. This could potentially cause headaches for active users and right now I don't see any benefit.
Any comments/opinions/etc? @rabbah @starpit @sjfink

I think Nick's example shows that it is likely that external services may use "error" property -- and so we will run into this again, when someone wants to use such a service in a sequence.
So, it seems to me we will have to change the convention sooner or later ... sooner seems better than later.

@sjfink what's your take on actions and sequences behaving the same? do you mean to change the error property name for atomic actions as well to stay consistent across all types of actions?

Yes, I think actions and sequences should behave the same, so I propose changing the name for atomic actions as well.
Nick has an example of an external service producing a value with an "error" property.    It seems reasonable to me that someday, someone will wrap a REST call to a similar service and use it in a sequence.
If you want a concrete example, let's suppose tomorrow Watson conversation changes their API so that one of their API calls has an "error" property.     All of a sudden, with no notice, all sequences using this will just break.
I think it's not a question of if this will happen, but when.

After some more thinking, the treatment of error property is different for the very first action in a sequence, irrespective of whether that action is a sequence or not (nothing to do with topmost sequence).
Consider the following example (assume s, x are sequences and a, b are atomic actions and none of the actions return error):
   s-> a, x
   s -> a
   s -> x   (*)
   x -> b

Assume all these sequences get a payload that contains an error field, they will all execute fine under the new behavior.
(*) note x executes even when not topmost

Seems like we are agreed to rename error to something else like whiskError?   How hard is it?  I imagine the code change itself is easy but we have to update docs too?

I'm opposed. Will expand this afternoon.

@ioana-blue  In your proposed fixed, you said
As such, I suggest for now I change the way the params with an error property received by a topmost sequence behave (i.e., the sequence will start execution and the error property short-circuit applies only to returned values).
The error property should apply also based on whether some status code indicates a whisk error.

@perryibm I think that happens automatically by current design; whenever there is a status code that indicates an error, the activation response that is constructed contains the error property. We have a test for such a case
https://github.com/openwhisk/openwhisk/blob/master/tests/src/system/basic/WskSequenceTests.scala#L304

@rabbah curious about your take on this.
If I were to play devil's advocate, in this example
https://github.com/openwhisk/openwhisk/issues/1822#issuecomment-278355909
if a service changes anything in its API, I'd rather know about it than everything in the OW world behave as if nothing happened. Also, you'd think any API breaking changes would be advertised in advance, so the REST wrapper action could be updated to properly handle the new field addition. If any service provider adds an error field, I'd like to know and have control over it.
Not to add that if I were a current OW user and something that was naturally used so far (the error field to signify error) would be changed to something cryptic like OW**** and I would have to change all the code in my actions to deal with this change, I would be annoyed.
This being said, I can argue both ways. It's fuzzy. (That's one reason why I liked Nick's inval/retval distinction. The REST api wrapper example is not an inval (at least not in my mind).)

We tend to state that invoking an action is Dictionary → Dictionary but more formally it is Dictionary → Try[Dictionary]. The Dictionary must be treated opaquely and if so, then there are no grounds to squash/not invoke an action that receives a dictionary because it defines an error property, regardless of the property name. Such is the case of an argument received from the REST API to activate an action whether directly or via a trigger.
Once running inside of the openwhisk runtime, the semantics are such that an action may return a Success[Dictionary] or Failure[Dictionary], and under composition, if the result of an action is the former, the dictionary is unboxed and passed to the next action in the sequence. If it's the latter, the execution terminates.
The runtime encodes Failure[Dictionary] with the presence of an error property in the dictionary - while within the openwhisk runtime, it is fair to apply this uniformly since any action must adhere to this protocol and the runtime enforces this.
(To relate this to the catch handler, when an action result is Failure[Dictionary] and there is a catch handler in scope for the action, then the action is invoked and receives the unboxed Dictionary.)

i think that's a good summary. the general flow is then:
given Seq(X,Y,Z), where X resolves to Success(D1), and Y resolves to Failure(D2), and Y.catch is W such that W(D2)=Success(D3), the result is the following data flow
D0 -> X => Success(D1) -> D1 => Y => Failure(D2) -> D2 -> W => Success(D3) => D3
where -> flows are managed by openwhisk, and => flows are managed by the application/actions

Closed by https://github.com/openwhisk/openwhisk/commit/a1dfc1dc449348533cfcfc76b1a89944730c716e.


popup wallet

make a pop up on the web when the pop up of the plugin is on, then close it when it is closed


Beaconbot 2.1

Many changes in this. Essentially updated from Discordjs v12 to Discordjs v13 which called for many changes to the code, mostly naming convention changes and method changes.
Along with a version update, there are small tweaks to existing features such as the roleinfo and userinfo command.
This is bumped up to v2.1 instead of v2.0 because I have added a fairly large new feature, Experience. Users will now level up by being active within the Discord Server and helping others with problems they may have.
Also, a few bug fixes as well.
For more info on the changes please review each commit individually.

Manually handled.


crash on start up if host port is used

if the host port is used by something else it instant crashes without telling why

Fixed in latest bleeding edge release 😊
Please lmk if it still crashes

Tested it and can confirm that it dosent crash anymore just red error messege telling me what the issue is like its suppose to


[Introspection] Error: [libs\sql-schema-describer\src\postgres.rs:125:23] could not get columns

Command: prisma introspect
Version: 2.6.2
Binary Version: 6a8054bb549e4cc23f157b0010cb2e95cb2637fb
Report: https://prisma-errors.netlify.app/report/11176
OS: x64 win32 10.0.19041
JS Stacktrace:
Error: [libs\sql-schema-describer\src\postgres.rs:125:23] could not get columns
    at IntrospectionEngine.<anonymous> (C:\Users\...\...\node_modules\@prisma\cli\build\index.js:2:1828886)
    at Generator.throw (<anonymous>)
    at rejected (C:\Users\...\...\node_modules\@prisma\cli\build\index.js:2:1825889)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Rust Stacktrace:
   0: <unknown>
   1: <unknown>
   2: <unknown>
   3: <unknown>
   4: <unknown>
   5: <unknown>
   6: <unknown>
   7: <unknown>
   8: <unknown>
   9: <unknown>
  10: <unknown>
  11: <unknown>
  12: <unknown>
  13: <unknown>
  14: <unknown>
  15: <unknown>
  16: <unknown>
  17: <unknown>
  18: <unknown>
  19: <unknown>
  20: <unknown>
  21: <unknown>
  22: <unknown>
  23: <unknown>
  24: <unknown>
  25: <unknown>
  26: <unknown>
  27: <unknown>
  28: <unknown>
  29: <unknown>
  30: <unknown>
  31: <unknown>
  32: <unknown>
  33: BaseThreadInitThunk
  34: RtlUserThreadStart

No recent reports.


gvm-libs: 22.6.3 -> 22.7.0

Diff: https://github.com/greenbone/gvm-libs/compare/refs/tags/v22.6.3...v22.7.0
Changelog: https://github.com/greenbone/gvm-libs/releases/tag/v22.7.0
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 247302 run on x86_64-linux 1

1 package built:

gvm-libs


Added first set of tests for drill-4783

Chun,
I verified drill4783 and added some tests around it. I am adding more tests, but it take a while before I complete all of them. So can you review this change?
Rahul

+1

Thanks Abhishek!


Compilation: Program type already present: android.support.v4.app.INotificationSideChannel$Stub$Proxy

I get error when i want build android app with this plugin:
 Task :app:compileDebugShaders UP-TO-DATE
> Task :app:generateDebugAssets UP-TO-DATE
> Task :CordovaLib:mergeDebugShaders UP-TO-DATE
> Task :CordovaLib:compileDebugShaders UP-TO-DATE
> Task :CordovaLib:generateDebugAssets UP-TO-DATE
> Task :CordovaLib:packageDebugAssets UP-TO-DATE
> Task :app:mergeDebugAssets UP-TO-DATE
> Task :app:validateSigningDebug UP-TO-DATE
> Task :app:signingConfigWriterDebug UP-TO-DATE
> Task :app:transformClassesWithDexBuilderForDebug

D8: Program type already present: android.support.v4.app.INotificationSideChannel$Stub$Proxy

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.
> com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
  Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
  Program type already present: android.support.v4.app.INotificationSideChannel$Stub$Proxy

* 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 9s
> Task :app:transformDexArchiveWithExternalLibsDexMergerForDebug FAILED
35 actionable tasks: 8 executed, 27 up-to-date
E:\Ampps\www\agrochest_web\cordova\platforms\android\gradlew: Command failed with exit code 1 Error output:
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: E:\Ampps\www\agrochest_web\cordova\platforms\android\app\src\main\java\org\apache\cordova\file\AssetFilesystem.java uses unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
D8: Program type already present: android.support.v4.app.INotificationSideChannel$Stub$Proxy

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.
> com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives:
  Learn how to resolve the issue at https://developer.android.com/studio/build/dependencies#duplicate_classes.
  Program type already present: android.support.v4.app.INotificationSideChannel$Stub$Proxy

* 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 9s
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>run-android: `cd cordova && cordova run android`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>run-android script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!       Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>cordova-android script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\Pawel\AppData\Roaming\npm-cache\_logs\2020-05-25T08_40_38_701Z-debug.log

It seems to me that some conflict with dependencies here
https://github.com/pwlin/cordova-plugin-file-opener2/issues/256
What i can do with this?

I understand, but, [insert current year argument], relying on "android.support.v4" should not be case.
What I recommend, and have worked for others in a similar position, is to have it upgraded to androix on build, by adding the plugins:
cordova plugin add cordova-plugin-androidx
cordova plugin add cordova-plugin-androidx-adapter

More info can be found in the issue: https://github.com/andrehtissot/cordova-plugin-fcm-with-dependecy-updated/issues/72
If it doesn't work, let me know.


Sentry Relay: Network Outage

Both the staging and the production Sentry relay repeat the warning in their Docker logs (sudo docker logs -f relay):
2023-05-05T23:00:26Z [relay_server::actors::upstream] WARN: Network outage, scheduling another check in 60s

I identified the root cause for this issue: The (unavailability of the) DNS servers provided. In our current setup, we have multiple DNS servers, one on the public interface and others on the internal one. For a yet unknown reason, the public-facing DNS servers are preferred but cannot be reached. For some name resolution, this "just" causes a delay, whereas the Relay obvious fails.
I deployed a Docker-specific solution (valid until the next deployment; keeping the current global configuration for debugging) and will continue investigating.

I completed my investigation and submitted a PR to fix this issue.

The PR has been merged, and we were able to confirm that this resolves our issue. Therefore, we are closing this issue as well.


Create Privacy Policy and Terms

I'll create privacy policy and terms

Under login forms in login there's a Link which's go /privacy page and it's empty


python3Packages.discordpy: 1.6.0 -> 1.7.0

Motivation for this change
Noticed an update was pushed upstream, so i decided to update the package.
Things done

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

[X] NixOS
[ ] macOS
[ ] other Linux distributions

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

/marvin opt-in
/status needs_reviewer

Result of nixpkgs-review pr 118466 at 58876f23 run on x86_64-linux 1

2 packages built successfully:

python38Packages.discordpy
python39Packages.discordpy

2 suggestions:

warning: stale-substitute
Stale substituteInPlace detected.
substituteStream(): WARNING: pattern 'aiohttp>=3.6.0,<3.7.0' doesn't match anything in file 'requirements.txt'
Near pkgs/development/python-modules/discordpy/default.nix:48:0:
   |
48 |     description = "A python wrapper for the Discord API";
   | ^

warning: stale-substitute
Stale substituteInPlace detected.
substituteStream(): WARNING: pattern 'websockets>=6.0,!=7.0,!=8.0,!=8.0.1,<9.0' doesn't match anything in file 'requirements.txt'
Near pkgs/development/python-modules/discordpy/default.nix:48:0:
   |
48 |     description = "A python wrapper for the Discord API";
   | ^

Result of nixpkgs-review pr 118466 at 58876f2 run on x86_64-linux 1
2 packages built successfully:
2 suggestions:

warning: stale-substitute
Stale substituteInPlace detected.
substituteStream(): WARNING: pattern 'aiohttp>=3.6.0,<3.7.0' doesn't match anything in file 'requirements.txt'
Near pkgs/development/python-modules/discordpy/default.nix:48:0:   |
48 |     description = "A python wrapper for the Discord API";
   | ^

warning: stale-substitute
Stale substituteInPlace detected.
substituteStream(): WARNING: pattern 'websockets>=6.0,!=7.0,!=8.0,!=8.0.1,<9.0' doesn't match anything in file 'requirements.txt'
Near pkgs/development/python-modules/discordpy/default.nix:48:0:   |
48 |     description = "A python wrapper for the Discord API";
   | ^

Result of nixpkgs-review pr 118466 at 58876f2 run on aarch64-linux 1
2 packages built successfully:
2 suggestions:

I must say, I am a really big fan of this bot. Fixed these suggestions :)


Is the C++ version of Succinct Open?

No its not open sourced since it isn't completely stable/well documented; but I can provide access if you're interested. What's your use-case?

Thank for your reply.
My use-case is text search and approximate search.

The C++ version can now be found here: http://github.com/amplab/succinct-cpp


Session status connected/disconnected

Is there a way to have a permanent state of the session to show connected or disconnected?
In order to check this state to determine whether or not we need to reconnect to the broker.

As of Ver2.0.0, there is no property on MQTTSession to identify whether the session is active or not.
PRs are welcome 😀


error when use .net 8 template with interactive render auto

Steps to reproduce error:

install template with the command: dotnet new mudblazor --interactivity Auto
run the proyect
go to counter page
click on counter button
refresh the page
get the error

I did ask for them to be updated :-(
But thats not the problem in this case cause I updated them to 8.0.1 and the problem remains

@ScarletKuro You are right.  After a clean and rebuild with 8.0.1 the issue is resolved

I had to also clean obj and bin folders

https://github.com/MudBlazor/Templates/issues/453#issuecomment-1901309111
This worked for me.

I am seeing the same error as initially described. Cleaning and rebuilding does not fix it for me. Also, I see it in every single, freshly created MudBlazor project. Here's what I did:

In Visual Studio, I create a new project using the template "MudBlazor Web App (MudBlazor)", with .NET 8.0, no authentication and interactive render mode "Auto (Server and WebAssembly)", globally set:

Once it's created, I change nothing at all and start debugging (F5):

After the first loading, it works: hiding/showing the sidebar, switching over to the counter page, increasing count by clicking the button.
As soon as I reload or start the second debugging session (or each time after that), there's no interactivity any more (clicking the three-bars-symbol to hide the sidebar does nothing, neither does clicking the counter button), and a JSON error appears in the console:

(Also, the CSS file gets a 404 now).

Clicking the sidebar link "Counter" shows a lot of errors in the console:

This happens across all the browsers I've tried: Firefox, Brave, Edge. I've tried this in Visual Studio 2022 (17.8.6) as well as VS Code 1.86.0 - it's exactly same everywhere: First run after creating the project is okay, second and every after that fails.

My installed .NET SDK is 8.0.101.

MudBlazor templates installed are the lastest (0.6.5).

I'm using Windows 11 Pro (23H2).

To rule out a configuration problem, I have uninstalled .NET entirely and made a clean install. I did the same with Visual Studio (removed completely and did a clean install). It changed nothing. I've used MudBlazor with .NET 6 and never experienced any problems like this.
Also, when using the "original" Blazor Web App template that comes with Visual Studio, applying the same settings as above, it works without a problem, no matter how often I reload / restart. The same goes for the Fluent UI template: It works both server side as well as after the switch to client side - so clearly, there's an issue with MudBlazor somehow...
My impression is that something goes/is wrong with the way WebAssembly render mode is configured/hooked in (since the problem occurs after the first reload, i.e. after the switch from server side to client side. Sadly, I cound't figure out what "the other" templates (the "original" one or Fluent UI) do differently regarding this...
I do think that MudBlazor is fantastic, and I'd really, really love to use this rather than Bootstrap (oiriginal template) or Fluent UI.  So - how could this problem best be tackled?
Thanks to everybody investing tehir time to work on MudBlazor and to help other people!

@philipp-koch have you updated the underlying libraries (Microsoft.AspNetCore.Components.WebAssembly.Server, Microsoft.AspNetCore.Components.WebAssembly and all other MS libraries) to 8.0.1 as the issue suggests? Then clear obj / bin / .vs(hidden), clean browser cache etc?

@ScarletKuro Thank you for pointing this out so clearly - I was mistaken, thinking "8.0.1" referred to the installed .NET SDK! So, I've taken a look at the NuGet package manager, and indeed the mentioned packages were still the RC versions, not 8.0.1. I have updated them, performed clean and rebuild for the solution, cleared the browser cache - and voilà, it works now! So, in other words: "Amazing, just do it right and all of a sudden it works!" 🤣
I'm a little emberassed now, but more importantly, I'm really happy this could be solved (so easily)...hanks again!
Thanks for your quick and helpful reply!

Hopefully https://github.com/MudBlazor/Templates/pull/454 will be merged soon, so it will work out of the box.


Handling XML Response

I can connect the web service with the code which is below:
Alamofire.request(.GET, "http://httpbin.org/get", parameters: ["foo": "bar"])
         .response { (request, response, data, error) in
                     println(request)
                     println(response)
                     println(error)
                   }

The service return to me XML. How can I get the result to an array from this XML output?

Instead of creating a support issue in Github, please open a question on Stack Overflow and tag Alamofire. The Alamofire community is very helpful and supportive. Stack Overflow is the best place to get your question answered quickly and correctly.

From our Contribution Guidelines
Asking Questions
We don't use GitHub as a support forum. For any usage questions that are not specific to the project itself, please ask on Stack Overflow instead. By doing so, you'll be more likely to quickly solve your problem, and you'll allow anyone else with the same question to find the answer. This also allows maintainers to focus on improving the project for others.


According to the cvxpy.org (http://www.cvxpy.org/versions/index.html), the latest stable release is version 1.0, and previous versions are not supported.
However, I strictly followed the installation steps (http://www.cvxpy.org/install/index.html) and anaconda installed cvxpy version 0.4.9 (cvxpy.__version__ is 0.4.9).
I installed the latest version of Anaconda (5.1.0) on Linux, if that helps.
Unless I screwed up somehow (very possible), it means the officially recommended installation steps result in an officially unsupported version of cvxpy.
Side note: I also notice that "multiply" is not documented: http://www.cvxpy.org/api_reference/cvxpy.atoms.affine.html#multiply

I am getting a similar issue. When I attempt conda install -c cvxgrp cvxpy=1.0.1 I get
Fetching package metadata .............
Solving package specifications:

PackageNotFoundError: Packages missing in current channels:

  - cvxpy 1.0.1* -> lapack

We have searched for the packages in the following channels:

  - https://conda.anaconda.org/cvxgrp/linux-64
  - https://conda.anaconda.org/cvxgrp/noarch
  - https://repo.continuum.io/pkgs/main/linux-64
  - https://repo.continuum.io/pkgs/main/noarch
  - https://repo.continuum.io/pkgs/free/linux-64
  - https://repo.continuum.io/pkgs/free/noarch
  - https://repo.continuum.io/pkgs/r/linux-64
  - https://repo.continuum.io/pkgs/r/noarch
  - https://repo.continuum.io/pkgs/pro/linux-64
  - https://repo.continuum.io/pkgs/pro/noarch

This was resolved for me by borrowing from the cvxpy/continuous_integration/install.sh script
conda install -q -n test-environment -c conda-forge lapack

Woah @matthewgilbert that worked for me too. Thanks!
So
conda install -c conda-forge lapack
should be added to the official install steps

The install instructions have been updated.

all this is very bad, the installation instructions of cvxpy should be update!!! they are not!

Currently the CVXPY 1.0.2 version document is not updated. Installation by conda is still some ancient version....

@ericwbzhang , can you explain what you mean?
@SteveDiamond , @rileyjmurray , do you know anything about this issue? (I use pip+virtualenv instead of conda, so I never see any of these issues personally ...)

@akshayka I don't know why they would get old anaconda versions. I updated the install instructions to require lapack and cvxpy=1.0.21 (version number will be updated by bumpversion). That should stop these old installs.

is it possible to have the install instructions of the correct version without conda?

I tried
conda install -c cvxgrp cvxpy= 1.0.21 (or 1.0.1)
but it returns package not found. I have lapack installed.

Update:
I did some search and it seems to be a problem only for Anaconda user on Windows.
https://github.com/cvxgrp/cvxpy/issues/701

I am no expert on conda packaging, but it may be worthwhile putting cvxpy on the conda-forge channel instead of maintaining your own cvxpy channel on https://anaconda.org/.
In my experience getting all the continuous integration working for linux/mac/windows is quite painful. One of the advantages of using conda-forge is they have a pretty straightforward framework for getting builds across all three platforms and pretty solid support via their gitter channel. This would also simplify the user experience to just running conda install -c conda-forge cvxpy

@matthewgilbert thanks for the suggestion. I'm considering simply removing the instructions for installation with Anaconda. We switched to suggesting installation with pip a few months ago. We'll still put out conda versions with each new release, but people can find them on their own perhaps.

Alternatively, if we can get conda forge working, we can just tell conda users to install cvxpy via conda forge instead of cvxgrp. But it looks like cvxpy on conda forge is several versions behind the current version. The pull requests for updates were never merged in, because they failed the CI tests: https://github.com/conda-forge/cvxpy-feedstock/pulls. I don't have the time right now to fix this, and Steven probably doesn't either.
If someone wants to look into this and help us get the conda-forge recipe working, that would be really great! I know conda is important for windows users in particular.

Weirdly, I'm trying to install cvxpy on a new macbook pro, and I'm also getting this issue.

The discussion on this thread is now a duplicate of #937 (planned conda-forge integration).