[BUG] Using defer, Expected a Response to be returned from queryRoute

I hope this method of reporting a bug is correct? This looks related to https://github.com/remix-run/remix/issues/4741 but not identical, and feels like a really basic case, so I'm not sure what's going wrong here
When running the submitted test, I get:
The following error is a bug in Remix; please open an issue! https://github.com/remix-run/remix/issues/new
Error: Expected a Response to be returned from queryRoute
    at Object.invariant [as default] (/home/me/remix/build/node_modules/@remix-run/server-runtime/dist/invariant.js:18:11)
    at handleResourceRequestRR (/home/me/remix/build/node_modules/@remix-run/server-runtime/dist/server.js:297:25)
    at requestHandler (/home/me/remix/build/node_modules/@remix-run/server-runtime/dist/server.js:103:18)
    at file:///home/me/remix/integration/bug-report-test.ts:116:18
    at /home/me/remix/node_modules/@playwright/test/lib/worker/workerMain.js:351:9
    at TestInfoImpl._runAndFailOnError (/home/me/remix/node_modules/@playwright/test/lib/worker/testInfo.js:156:7)
    at /home/me/remix/node_modules/@playwright/test/lib/worker/workerMain.js:347:7
    at TimeoutRunner.run (/home/me/remix/node_modules/playwright-core/lib/utils/timeoutRunner.js:46:14)
    at TimeoutManager.runWithTimeout (/home/me/remix/node_modules/@playwright/test/lib/worker/timeoutManager.js:62:7)
    at TestInfoImpl._runWithTimeout (/home/me/remix/node_modules/@playwright/test/lib/worker/testInfo.js:143:26)
    at WorkerMain._runTest (/home/me/remix/node_modules/@playwright/test/lib/worker/workerMain.js:285:5)
    at WorkerMain.runTestGroup (/home/me/remix/node_modules/@playwright/test/lib/worker/workerMain.js:209:11)
    at process.<anonymous> (/home/me/remix/node_modules/@playwright/test/lib/common/process.js:88:22)

This looks like just a missing default export - with that added the deferred data is working correctly: https://stackblitz.com/edit/remix-run-remix-gkedbv?file=app%2Froutes%2F_index.tsx

This looks like just a missing default export - with that added the deferred data is working correctly: https://stackblitz.com/edit/remix-run-remix-gkedbv?file=app%2Froutes%2F_index.tsx

Ah, thanks for the pointer, figured I'd made a silly mistake somewhere. Might be worth revisiting the error message thpugh?


[INSTALL]: ESMpy in derecho

Package name
esmpy
Package version/tag
8.5.0
Build options
working with ESMF 8.5.0
Installation timeframe
I need esmpy (v8.5.0) library in Derecho for running Hurricane analysis and forecast system (HAFS) model. I use this following library set to run my HAFS simulations. I would really appreciate if you could help me or give me some directions for this if needed.
My module config:
module purge
export MODULEPATH="/glade/work/epicufsrt/contrib/spack-stack/derecho/modulefiles:$MODULEPATH"
export MODULEPATH="/lustre/desc1/scratch/epicufsrt/contrib/modulefiles_extra:$MODULEPATH"
export MODULEPATH="/glade/work/epicufsrt/contrib/spack-stack/derecho/spack-stack-1.5.1/envs/unified-env/install/modulefiles/Core:$MODULEPATH"
module unload ncarcompilers
export stack_intel_ver=${stack_intel_ver:-"2021.10.0"}
module load stack-intel/$stack_intel_ver
export stack_cray_mpich_ver=${stack_cray_mpich_ver:-"8.1.25"}  # Change to "8.1.27" or "8.1.29" if needed
module load stack-cray-mpich/$stack_cray_mpich_ver
export cmake_ver=${cmake_ver:-"3.26.3"}
module load cmake/$cmake_ver
export stack_python_ver=${stack_python_ver:-"3.10.8"}
module load stack-python/$stack_python_ver
export CMAKE_Platform="derecho.intel"
module load ufs-weather-model-env
Other information
No response

We've added esmpy support to spack-stack develop just two weeks ago, it didn't make it into spack-stack-1.8.0. You will need to wait for spack-stack-1.9.0 for it to be available with the blessed ESMF version at that time. It's unlikely that we can (or have the time to) backport the esmfpy update in the latest ESMF package to 8.5.0 (I assume in spack-stack-1.6.0). EPIC has the last word, though.


tags not searchable

I just tried the demo and couldn't find my question by the tag.
Maybe that's by design (I noticed there's a tag cloud on the right hand side), but that still makes it hard to find a question or article that uses a popular tag and has some fairly unique word in the body.
For example if I want to find a python-tagged question that mentions JavaScript, I'd like to be able to find it by searching for python javascript rather than having to browse through all python-tagged Q&A, or search for JavaScript and find many results unrelated to Python.
Maybe "search within results" would be useful (so that one can click on a tag and then search all Q&A or articles that contain the tag.)

Thanks @unsystemizer. Actually I have been thinking about changing the implementation of tags, and perhaps to use Taggit instead. This obviously will fix #73 too. Let work it a little bit more, or, if you have suggestions or perhaps if you submit a PR for this, it will be most appreciated.

Thanks. I would submit a PR if I could but I'm not at that level yet :-)

Solve with 65aabe8e8ffa1ab4ea0ac1441db81fd9d0c4cbc1

Sorry to resurrecting this old issue.
I just installed the latest version and the tags doesn't seem clickable.
All of them points to href="#", and if I try to access the supposed url directly, this gets me a 404 page. Ex: mydomain.com/articles/tag/myTag
Did I missed configuring something? Or is this supposed to happen?
Thank you!


Debugging Failing: Unexpected CLRDBG output from command "-exec-run" on macOS Sierra (10.12.4 Beta)

Environment data
dotnet --info output:
.NET Command Line Tools (1.0.0-rc3-004530)

Product Information:
 Version:            1.0.0-rc3-004530
 Commit SHA-1 hash:  0de3338607

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.12
 OS Platform: Darwin
 RID:         osx.10.12-x64
 Base Path:   /usr/local/share/dotnet/sdk/1.0.0-rc3-004530

VS Code version: Version 1.9.1 (1.9.1)
C# Extension version: 1.7.0
Steps to reproduce

Open dotnet core c# project
Launch the debugger
Wait for project to build

Expected  behavior
The debugger launches and allows me to debug the code
Actual behavior
An error is returned in the output window:
--------------------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (clrdbg) with Visual Studio
Code, Visual Studio or Visual Studio for Mac software to help you develop and
test your applications.
--------------------------------------------------------------------------------
ERROR: Unable to start debugging. Unexpected CLRDBG output from command "-exec-run".
The program '/Users/nicklasdemayo/aaa/projects-git/Service-BAHAdmin/BAH.Admin/bin/Debug/netcoreapp1.1/BAH.Admin.dll' has exited with code 42 (0x0000002a).

I ran the following (suggested from here):
/Users/nicklasdemayo/.vscode/extensions/ms-vscode.csharp-1.7.0/.debugger/clrdbg --interpreter=mi
-gdb-exit

And got no other unexpected output.

@sunmorgus could you enable engineLogging (hopefully the quick way will work) and add the relevant sections around '-exec-run' to this bug?

The quick way appeared to work. I copied everything from the 1011-exec-run line down, let me know if you need more.
1: (686) <-1011-exec-run
1: (11041) ->=telemetry,event-name="VS/Diagnostics/Debugger/clrdbg/LaunchFailed",properties={VS.Diagnostics.Debugger.clrdbg.ErrorCode="0x80070057",VS.Diagnostics.Debugger.clrdbg.Version="15.0.26013.0 built by: PREVIEW.DBG2",VS.Diagnostics.Debugger.clrdbg.OSFamily="Darwin",VS.Diagnostics.Debugger.clrdbg.KernelRelease="16.5.0"}
1: (11042) ->1011^error,msg=""
1: (11042) ->(gdb)
E output: {"category":"telemetry","output":"VS/Diagnostics/Debugger/clrdbg/LaunchFailed","data":{"VS.Diagnostics.Debugger.clrdbg.ErrorCode":-2147024809,"VS.Diagnostics.Debugger.clrdbg.Version":"15.0.26013.0 built by: PREVIEW.DBG2","VS.Diagnostics.Debugger.clrdbg.OSFamily":"Darwin","VS.Diagnostics.Debugger.clrdbg.KernelRelease":"16.5.0"},"type":"output"}
1: (11044) 1011: elapsed time 10358
E output: {"category":"stderr","output":"ERROR: Unable to start debugging. Unexpected CLRDBG output from command \"-exec-run\".\n","data":null,"type":"output"}
ERROR: Unable to start debugging. Unexpected CLRDBG output from command "-exec-run".
1: (11055) <--gdb-exit
1: (11056) ->^exit
1: (11061) <-logout
E output: {"category":"console","output":"The program '/Users/nicklasdemayo/aaa/projects-git/Service-BAHAdmin/BAH.Admin/bin/Debug/netcoreapp1.1/BAH.Admin.dll' has exited with code 42 (0x0000002a).\r\n\n","data":null,"type":"output"}
The program '/Users/nicklasdemayo/aaa/projects-git/Service-BAHAdmin/BAH.Admin/bin/Debug/netcoreapp1.1/BAH.Admin.dll' has exited with code 42 (0x0000002a).
E exited: {"exitCode":42,"type":"exited"}
E terminated: {"type":"terminated"}
E output: {"category":"telemetry","output":"VS/Diagnostics/Debugger/DebugCompleted","data":{"VS.Diagnostics.Debugger.ImplementationName":"Microsoft.MIDebugEngine","VS.Diagnostics.Debugger.EngineVersion":"14.0.31028.1","VS.Diagnostics.Debugger.HostVersion":"1.0.30207.1","VS.Diagnostics.Debugger.AdapterId":"coreclr","VS.Diagnostics.Debugger.DebugCompleted.BreakCounter":0},"type":"output"}
C disconnect: {"restart":false}
 R: {"success":true,"message":null,"request_seq":6,"command":"disconnect","body":null,"running":false,"refs":null,"seq":0,"type":"response"}```

@sunmorgus got it. So it looks like '-exec-run' is failing with E_INVALIDARG (0x80070057), which we don't provide a description for, and that results in this bad error message. Unfortunately that doesn't tell us much about the root cause for where the E_INVALIDARG might be coming from. If you scroll up a little bit where you should see the program path, working directory, and arguments passed, does anything by chance look 'weird'?

@gregg-miskelly I do see this error a little further up:
1: (501) ->(gdb)
1: (501) <-1006-break-insert main
1: (501) ->1006^error,msg="-break-insert currently only supports file/line breakpoints"
1: (501) ->(gdb)
1: (501) 1006: elapsed time 0

However, I took a look at the program path, working directory, and arguments, but nothing sticks out to me as being off...

@sunmorgus that error is actually normal / ignorable. Hmm... I am not quite sure how to troubleshoot this.
Do you get this problem for all projects?

@gregg-miskelly I went and created a new project, and the same issue occurred.
Also, I feel I should mention (and probably should have earlier, sorry)... this issue started occurring after 2 events this morning:

Installing Visual Studio for Mac (and the supporting Mono framework stuff). I tried removing all of that (as well as removing and reinstalling OmniSharp in vscode), but that didn't help.
I also updated this morning to macOS 10.12.4 Public Beta Version 2, but that would be a difficult one to roll back.

It's hard to say whether or not either of those caused the issue I suppose, but they are about the only things I can think of that changed recently.

@sunmorgus Thanks. I will see if I can reproduce this on that OS.

Hoping a solution may be found soon, I am also experiencing this issue when trying to debug.
Both on a simple "Hello, World" project, and more advanced code.
Exact same OS version as @sunmorgus with same environment also.

Same situation here, also with macOS 10.12.4 Beta 2.

Other things I've tried/noticed:

It almost feels like it's having an issue reading the stdin. I had a simple python script I was trying to run recently that was supposed to take input from the stdin, but it wasn't able to for some reason. I didn't dig into it much, but maybe they are related?
I verified that it wasn't an issue with my dotnet core install by reinstalling it, making sure to complete the openssl req as well.
I'm keeping an eye out for a new update to the public beta, and I'm going to submit feedback to Apple as well.

I am getting this same error all of a sudden, worked fine yesterday, but last night my MacOS did update to 10.12.4 Public Beta 2.
Builds fine, but can't debug any longer, any ideas?

Same for me.
Updated to macOS 10.12.4 beta 2.

Also able to repro: On 10.12.4 Beta (16E154a)
Terminal window in vscode:
bash-3.2$ /Users/mshulman/.vscode/extensions/ms-vscode.csharp-1.7.0/.debugger/clrdbg --interpreter=mi =message,text="--------------------------------------------------------------------------------\nYou may only use the Mic rosoft .NET Core Debugger (clrdbg) with Visual Studio\nCode, Visual Studio or Visual Studio for Mac software to help you develop and\ntest your applications.\n--------------------------------------------------------------------------------\n" ,send-to="output-window" (gdb) -gdb-exit ^exit

I thought I'd be able to work around this by launching my app, then attaching the debugger. Unfortunately, I get the same message.

I ended up downloaded the latest stable MacOS version from apple's developer site and it installed back to the pre-beta version without effecting anything that was installed on my MacBook. With that this error was gone, no beta for me till this is resolved...

Error still occurs, 10.12.4 beta 3 release of macOS.

It happens in visual studio for Mac is well.
--
Nick DeMayo
On February 21, 2017 at 8:31:21 AM, Steve Pentland<EMAIL_ADDRESS>wrote:

Error still occurs, 10.12.4 beta 3 release of macOS.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/OmniSharp/omnisharp-vscode/issues/1220#issuecomment-281344718,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACLmcNjUUI_UOFjD-mBxueI1WDqwUOABks5reucpgaJpZM4L9eD1
.

@noahfalk FYI

This issue is caused by an issue with a CoreCLR component. I opened https://github.com/dotnet/coreclr/issues/9730 to track the problem.

I have the same error since upgrading to macOS 10.12.4 beta 2 and 3. Not only Visual Studio for Mac but also VSCode stopped working for me. I'll try reverting to stable 10.12.3 to see if that 'solves' the issue of not being able to debug.

It seems that 1.8.0-beta2 made progress towards a resolution here... I'm now able to at least start the project inside of vscode, but I get a new error message Unable to attach to CoreCLR:
-------------------------------------------------------------------
You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.
-------------------------------------------------------------------
Unable to attach to CoreCLR.
Hosting environment: Development
Content root path: [redacted]
Now listening on: http://localhost:5000
Application started. Press Ctrl+C to shut down.

I can see that the extension is now using vsdbg rather than clrdbg and that is has options for vscode specifically. I tried running the below to see if I'd get any expected output (grasping at straws here... not entirely certain what I'm even doing is correct):
./vsdbg --interpreter=vscode --engineLogging=vsdbg.log --attach --name dotnet

But got no errors or anything in the log file.

@sunmorgus I debugged the issue and we are fairly certain we know what is going wrong. The underlying issue is a problem with CoreCLR (see above CoreCLR bug). We are leaving this issue open as we will need to update the debugger to a new CoreCLR once there is a fix from the CLR team.

I rolled back the osX beta update and that fixed my issue and i was able to run the debugger.

@robvdveer How do I roll it back? Do I have to do a clean install to do that?

I rolled back too, to fix this... go to apple developer portal, download the latest non beta version of Mac OS and install it. It didn't wipe anything for me, I was able to debug in VSCode as soon as it booted back up. MAKE SURE you disable updating back to beta in Mac Settings, otherwise you are back where you started, happened to me once...

Sigh... I'm on the public beta and don't have access to the developer portal :(

Can't you find the nonbeta download in your app store history.

I don't see it in the purchase history... I got the laptop on January 20th (ish), with Sierra already loaded.

If your lapto is not even a month old just do a recovery reset after you make a backup.

@gregg-miskelly: Is this the same problem as issue https://github.com/dotnet/coreclr/issues/9730 (launch fails on Sierra because the vmmap output changed)?

@mikem8361: Yes. The two bugs are linked above.

Similar issue on WIN 10 X64

Error still occurs, 10.12.4 beta 4(16E183b) release of macOS.

@poorboss3 your issue is NOT similar if it is happening on Windows. If you would like help, please open a new bug.

Mac OS Sierra  10.12.4 (non-Beta) was released to the public today and this breaks .NET core from working on anyone's Mac running the latest version of Mac OS...

@LukeStephen :( I hope to have a beta release out later this week with the fix. I will see if I can put a work around together today using unofficial bits.

Thanks!  Even having it work inside visual studio code insiders would be good enough for now...

CC @mikem8361 @lt72

Here is a work around that worked for me:

Download https://dotnet.myget.org/F/dotnet-core/api/v2/package/runtime.osx.10.10-x64.Microsoft.NETCore.Runtime.CoreCLR/1.1.2-servicing-25123-01
Open the resulting file as a zip, and copy out runtimes/osx.10.10-x64/native/libdbgshim.dylib
Open a terminal
cd ~/.vscode/extensions/ms-vscode.csharp-1.8.0/.debugger
cp <path-to-extracted-libdbgshim> .

As I said above, but just to repeat here, I expect to have a real fix out soon. But hopefully this will unblock folks in the mean time.

I can confirm this workaround worked for me. Although my extensions directory was ms-vscode.csharp-1.7.0
Thanks!!

FYI, I ran into this issue today too, but with Mac OS Sierra 10.12.2, using VS Code, both via "Attach"  with one project, and "Launch (web)" with another project.
The project associated with the Attach attempt was a new one I just started exploring today (the MS-birthed, very cool Humanitarian Toolbox AllReady project), and the project associated with the Launch attempt was an existing one that was debuggable just fine as recently as last week.
And I suspect this might be related to a new C# 1.8.0, which VS Code reported needing updating today - so I did. Since I did this in the context of the new project, I initially assumed the problem might be something related to it.
But I can confirm that the problem is fixed now for both projects after following Gregg's instructions above.
Yippee! Thanx much.

I ran into this issue on Mac OS Sierra 10.12.3, but the workaround provided by @gregg-miskelly worked! Thank you! I'm not sure what I did to run into this, because it was working yesterday for me.

I ran into the same problem today it may be linked to any of the following events:

Xcode update
iWork update
macOS update

I'll go for the macOS update, anyway @gregg-miskelly worked perfectly.

I have posted a new release of the C# extension that includes the fix.
To try it -- use the use the Installing Beta Releases instructions to install v1.9.0-beta2.

Thanks, is working now, I was having the same issue today.

macOS 10.12.4 and the beta release has enabled debugging to work as expected for myself as well.   Thank you.

I am happy to see this working for VSCode now. However, will this patch work for Visual Studio for Mac Preview as well?

That is a really good point, I ran into the same issue when trying to debug with VS for Mac preview.

@jorgecotillo yes thanks that workaround fixed it for me! Back to work!

@gregg-miskelly: Should this resolved fixed now?

@gregg-miskelly Version 1.8.1 fixed the issue for me as well.

@DustinCampbell I was going to resolve this as soon as we pushed to the gallery (since hithub makes it harder to find closed issues and this one is popular).

Version 1.8.1 has now been released to the extension gallery, and contains a fix for this issue. Thanks!


fix: pass the correct argument to get_reference_by_email for dbt ingestion

Describe your changes:
This issue fix this error on dbt ingestion
line 173, in get_dbt_owner
    owner = self.metadata.get_reference_by_email(name=dbt_owner)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: OMetaUserMixin.get_reference_by_email() got an unexpected keyword argument 'name'

passing the right named argument, because name is not an arg of get_reference_by_email,

I didn't find any reference to this issue, when searching the issues.

I worked on ... because ...

Type of change:

[x] Bug fix
[ ] Improvement
[ ] New feature
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] My PR title is Fixes <issue-number>: <short explanation>
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

@OnkarVO7 FYI.


SNAP Action: Move each action type hard- and software part into one subdirectory

E.g.
actions/hls_memcopy/hardware
software
shared
Feel free to add more ideas here.
The scattering of the action code was rated not optimal by our HPI and AlphaData partners.

I like this idea very much. Shall we move?

Bruno just told me to proceed with a proposal. The HPI folks wanted it too but I have not seen their proposal yet. Let use try to put something together and discuss it during tryout.

Thanks to all those contributing to this larger effort. I think we did well including this so quickly.


Cannot build App after applying the Android setup. Http POST requests won't work

Your Environment

Plugin version: @transistorsoft/capacitor-background-geolocation": "^4.3.0"
Platform: Android
Device OS version: Android 10
Device manufacturer / model: Samsunsg / Galaxy A71
XCode version: -
Capacitor info (`
💊   Capacitor Doctor  💊

Latest Dependencies:
@capacitor/cli: 3.2.3
@capacitor/core: 3.2.3
@capacitor/android: 3.2.3
@capacitor/ios: 3.2.3
Installed Dependencies:
@capacitor/cli: 3.1.1
@capacitor/core: 3.1.2
@capacitor/android: 3.1.1
@capacitor/ios: 3.1.1
[success] iOS looking great! 👌`)

Plugin config provided to #ready:

//plugin config
  BackgroundGeolocation.ready({
    reset: false,
    debug: false,
    logLevel: BackgroundGeolocation.LOG_LEVEL_VERBOSE,
    disableLocationAuthorizationAlert: true,
    distanceFilter: 10,
    notification: {
      priority: BackgroundGeolocation.NOTIFICATION_PRIORITY_HIGH
    },
    autoSync: true,
    stopOnTerminate: false,
    startOnBoot: true
  }, (state) => {
    if (!state.enabled) {
      BackgroundGeolocation.startGeofences();
      LocalNotifications.requestPermissions().then((permission) => { permission });
    } else {
      console.log("Im having a problem here maybe not ready");
    }
  });

//the post request im trying to execute
 this.httpNative.sendRequest(
       "https://enterurlhere"
      {
        method: 'post',
        data:  {
           //some data
        },
        headers: {
          "Content-Type": "application/json",
          "Accept": "application/json",
          "Access-Control-Allow-Origin": "*",
        },
        responseType: "json",
      }).then(data => {
        data.status = 0;//success
        console.log("success ");
        return data;
      }).catch(error => {
        if (error.status == 401) {
          error.status = -1;
          console.log("validate session")
        } else {
          error.status = 1;//error
          console.log("error");
        }
        return error;
      });

Expected Behavior

The app should be able to communicate with the API and handle the responses in order for the user to login, logout, change password,... in our app
Actual Behavior

The app is unable to execute any POST requests and stucks after applying the Android setup. After the build the app is able to open and execute GET requests. Whenever i try to execute a POST request the app returns the following error in my Console:
ERROR Error: Uncaught (in promise): SyntaxError: Unexpected token U in JSON at position 0

Steps to Reproduce

Install capacitor-background-geolocation plugin
Install HTTP native plugin https://ionicframework.com/docs/native/http
Implement a simple http post request as shown above.
Follow the Android setup
Build the app
Try to run a post request
Check the console tab  for errors

Context

Debug logs

Logs
ERROR Error: Uncaught (in promise): SyntaxError: Unexpected token U in JSON at position 0
SyntaxError: Unexpected token U in JSON at position 0
    at JSON.parse (<anonymous>)
    at GeneralmethodsService.<anonymous> (/main-es2015.js:101)
    at Generator.next (<anonymous>)
    at /vendor-es2015.js:66673
    at new ZoneAwarePromise (/polyfills-es2015.js:1075)
    at __awaiter (/vendor-es2015.js:66669)
    at /main-es2015.js:89
    at ZoneDelegate.invoke (/polyfills-es2015.js:479)
    at Object.onInvoke (/vendor-es2015.js:57245)
    at ZoneDelegate.invoke (/polyfills-es2015.js:478)
    at resolvePromise (/polyfills-es2015.js:913)
    at /polyfills-es2015.js:820
    at rejected (/vendor-es2015.js:66671)
    at ZoneDelegate.invoke (/polyfills-es2015.js:479)
    at Object.onInvoke (/vendor-es2015.js:57245)
    at ZoneDelegate.invoke (/polyfills-es2015.js:478)
    at Zone.run (/polyfills-es2015.js:238)
    at /polyfills-es2015.js:972
    at ZoneDelegate.invokeTask (/polyfills-es2015.js:514)
    at Object.onInvokeTask (/vendor-es2015.js:57233)
defaultErrorLogger @ /vendor-es2015.js:34142

SyntaxError: Unexpected token U in JSON at position 0

Your error is not related to background-geolocation.  You seem to have a JSON error with your data.
I would check the CHANGELOG of that plugin and seek support over there.
Also, why are you even using a 3rd party plugin for HTTP requests?  background-geolocation has a built-in HTTP service.  See API docs for HTTP Guide.

Hi Chris,
Thank you for quick response.
The reason i opened this issue in the first place was that the app with same plugins works just fine on iOS without any json issues.
The problem appears only on android. I will check the HTTP doc you pinted out, but what if i want to use the native http instead of your plugin http?
Do i have an option to choose the plugins i use'
I am i dependend to use the plugins that the plugin uses? 🙂
Im looking forward to you are response on that.
Best regards,
AndreasHi Chris,
Thank you for quick response.
The reason i opened this issue in the first place was that the app with same plugins works just fine on iOS without any json issues.
The problem appears only on android. I will check the HTTP doc you pinted out, but what if i want to use the native http instead of your plugin http?
Do i have an option to choose the plugins i use'
I am i dependend to use the plugins that the plugin uses? 🙂
Im looking forward to you are response on that.
Best regards,
Andreas
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Chris Scott @.>
Sent: Friday, September 24, 2021 4:06:11 PM
To: transistorsoft/capacitor-background-geolocation @.>
Cc: Andreas Apostolou @.>; Author @.>
Subject: Re: [transistorsoft/capacitor-background-geolocation] Cannot build App after applying the Android setup. Http POST requests won't work (#24)
SyntaxError: Unexpected token U in JSON at position 0
Your error is not related to background-geolocation. You seem to have a JSON error with your data.
I would check the CHANGELOGhttps://github.com/silkimen/cordova-plugin-advanced-http/blob/master/CHANGELOG.md of that plugin and seek support over there.
Also, why are you even using a 3rd party plugin for HTTP requests? background-geolocation has a built-in HTTP service. See API docs for HTTP Guide.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/transistorsoft/capacitor-background-geolocation/issues/24#issuecomment-926609605, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATZWYFTEC6WUQ3UP6QL5OHTUDRZUHANCNFSM5EVUVWVQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I wouldn't trust that "native http" plugin.

It's a Cordova plugin.  You're using Capacitor.
Doesn't use the popular okhttp.  background-geolocation uses okhttp for its HTTP requests.

There is a capacitor http plugin (though still doesn't use okhttp).

Can you show me an example or a link to an example on how to use the okhttp to make my POST,PUT,GET... API calls?

Can you show me an example or a link to an example on how to use the okhttp to make my POST,PUT,GET... API calls?

The isn't something you do.  okhttp is a native Android library.  To use okhttp is to write Java code.  That isn't something one does in a Capacitor app.
The plugin contains its own built-in http service.  You just need to provide the plugin an url.  See API docs "HTTP Guide".

Can you please send me a link to the HTTP GUIDE?
It would be very helpful, thanks!
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: Chris Scott @.>
Sent: Monday, September 27, 2021 11:08:11 PM
To: transistorsoft/capacitor-background-geolocation @.>
Cc: Andreas Apostolou @.>; Author @.>
Subject: Re: [transistorsoft/capacitor-background-geolocation] Cannot build App after applying the Android setup. Http POST requests won't work (#24)
Can you show me an example or a link to an example on how to use the okhttp to make my POST,PUT,GET... API calls?
The isn't something you do. okhttp is a native Android library. To use okhttp is to write Java code. That isn't something one does in a Capacitor app.
The plugin contains its own built-in http service. You just need to provide the plugin an url. See API docs "HTTP Guide".
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/transistorsoft/capacitor-background-geolocation/issues/24#issuecomment-928229513, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ATZWYFQ6HVYLVLMCGPM4J43UEDFKXANCNFSM5EVUVWVQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

The README contains a link the the "API docs" in the table of contents.

This one? https://github.com/transistorsoft/capacitor-background-geolocation/blob/master/README.md

???

Is this possible?

No.  The plugin doesn't magically handle all your http requests.

So in order to make it clear.
I was using the ionic-native plugin to make my http requests GET, POST, PUT.
Login, logout user, get user profile data from server...
And on top of that i wanted to use the geolocation plugin, but it wasnt possible and i needed to use the popular okkttp.
Apparently from what i understand i cannot have both. I mean i need to have geolocation plugin and my app functional. Can i?
Correct me if i am wrong.

I mean i need to have geolocation plugin and my app functional. Can i?

Of course you can.

  async ANAPICALL() {     return await BackgroundGeolocation.ready({       url: "https://someurl",       params: {     //some params       },       headers: {       //some headers       },     }, state => {       console.log("[ready] success: ", state);     }).catch(error => {       return error;     });
is this the correct way?

Once the plugin is provided an url, it immediately attempts to POST every recorded location to the provided url.  Adjust params, headers as your server requires.

i didn't manage to make it work. Can you provide me an example with pseudo code just to see how to make a simple post request(without the backgroundgeolocation) and handle the results?
Just the skeleton.
i have followed the HTTP guide, https://transistorsoft.github.io/capacitor-background-geolocation/interfaces/httpevent.html. but the examples are related to BackgroundGeolocation

i didn't manage to make it work

What makes you think it didn't work?

You need to watch the plugin's logs in $ adb logcat.
$ adb logcat *:S TSLocationManager:V

@andreasaphilo I think this is not the right place for your native http plugin related questions.
Try finding an answer on the plugins github issue or through stackoverflow.
I don't want to be mean, but I just think that your bugs are not related to this plugin and you will not find any help here which will show you any solution.

@andreasaphilo I think this is not the right place for your native http plugin related questions. Try finding an answer on the plugins github issue or through stackoverflow. I don't want to be mean, but I just think that your bugs are not related to this plugin and you will not find any help here which will show you any solution.

Im not trying to solve a bug at this stage! I just need an example of a server POST request. Can you provide me with one?

There is no pseudo code for you.
Show me the result of $ adb logcat *:S TSLocationManager:V

I didn't need to use the adb logcat

Yes you do.  This is a very complex plugin and it is logging an immense amount of debugging information to logcat.
If you're not observing the logs, you will fail to use this plugin.

2021-09-28 18:51:48.328 32444-11918/my.app.name V/Capacitor: callback: 1177976, pluginId: BackgroundGeolocation, methodName: ready, methodData: {"options":{"url":"https:\/\/api-dot-smash-eutest.appspot.com\/external\/v2\/smashMember\/login","autoSync":true,"autoSyncThreshold":5,"params":{"username":"35799107978","password":"111111111"},"headers":{"Content-Type":"application\/json","Accept":"application\/json","Access-Control-Allow-Origin":"*","PHILO-OrgId":"628001","PHILO-ClientId":"jumpApp"}}}
2021-09-28 18:51:48.367 32444-11626/my.app.name D/TSLocationManager: [c.t.l.adapter.TSConfig d] ℹ   Persist config, dirty: [autoSyncThreshold, extras, headers, headlessJobService, params, schedule, url]
2021-09-28 18:51:48.372 32444-11626/my.app.name D/TSLocationManager: [c.t.l.adapter.TSConfig d] ℹ   Persist config, dirty: [autoSyncThreshold, headers, headlessJobService, params, url]
2021-09-28 18:51:48.381 32444-32444/my.app.name I/TSLocationManager: [c.t.l.http.HttpService flush]
    ╔═════════════════════════════════════════════
    ║ HTTP Service (count: 0)
    ╠═════════════════════════════════════════════
2021-09-28 18:51:48.386 32444-32444/my.app.name I/TSLocationManager: [c.t.l.http.HttpService flush]
    ╔═════════════════════════════════════════════
    ║ HTTP Service (count: 0)
    ╠═════════════════════════════════════════════
2021-09-28 18:51:48.393 32444-32444/my.app.name I/Capacitor/Console: File: http://localhost/main-es2015.js - Line 3623 - Msg: WOWOWWOWOWO[object Object]
2021-09-28 18:51:48.399 32444-32444/my.app.name I/Dialog: mIsSamsungBasicInteraction = false, isMetaDataInActivity = false
2021-09-28 18:51:48.403 32444-32444/my.app.name I/DecorView: [INFO] isPopOver=false, config=false
2021-09-28 18:51:48.403 32444-32444/my.app.name I/DecorView: updateCaptionType >> DecorView@be2a10e[], isFloating=true, isApplication=true, hasWindowDecorCaption=false, hasWindowControllerCallback=false```

My app, its a loyalty app and  has multiple screen makes multiple api calls.
I am using this plugin for only one screen. The rest of the app is not related to the Background Geolocation.
The users have the option to not enable their location services or not to go to that screen which is using the Background geolocation plugin.
I need to make calls to my server even if the user has not granted permission to GPS, even if the user never enter that screen.
Thats why i was asking you all this time.

I need to make calls to my server even if the user has not granted permission to GPS or even if the user never enter that screen.

This is not related to the plugin.  The plugin Configured with an url is concerned only with posting its own recorded locations.  It has nothing to do with your general application HTTP requests.

I agree what what you are saying, the only issue is that after installing the plugin the general HTTP requests in my app are not working.
This is only happening to the Android version of the app and from our discussion is related to the native okhttp which clashes with my ionic-native cordova plugin and causing my api calls to fail.
I need a solution for this.

I don't have any idea how to help you.  Your error is not from this plugin.

@andreasaphilo You should first ask for a location. HTTP Service (count: 0) that marks as you don't have any position on plugin database. When you have one pending location, the plugin will send to the backend. And also, how you can push locations to someurl?.

@andreasaphilo If you have any conflicts with your http plugin, why don't you just switch to any javascript http/ajax library? For example if you're using Angular, just use the HttpClient from Angular. In general you won't need a native http plugin.

If you are in need to do http requests in the background you will need a native http plugin.
Currently only the Capacitor http plugin is able to do that after 5 minutes in background since Android 10.
But the UI thread is paused, so no JS code is executed after 5 minutes in background. You will need to do background tasks with background fetch then to awaken the app.

@andreasaphilo If you have any conflicts with your http plugin, why don't you just switch to any javascript http/ajax library? For example if you're using Angular, just use the HttpClient from Angular. In general you won't need a native http plugin.

I am using Ionic Angular to build my mobile apps thats why i was using the ionic native plugin in the first place!


StyleGuidelines.md: Style guidance for parameter usage in function and cmdlet calls

Is there any style guidance for how best to pass parameters to functions and cmdlets? If not, is this something that should be added? Things I'm thinking of are:
-Do we allow both single line and multi line passing of parameters? Do we prefer one over the other?
-If multi line is allowed, what are our best practices for formatting the passed parameters?
-Do we care about inline array or hashtable declarations, or do we want them assigned to a variable before passing?

Hi @mhendric,
There are some styleguidelines for this:

There isn't a style guideline on this (there probably should be), but we do allow both single line and
multi-line parameters. But the rule of thumb is that if a line gets beyond 80 chars then it should be split.
This used to be a style guideline but it got removed sometime back.
Multi-line is enabled but there isn't a styleguideline for formatting - although we do tend to apply
[Correct Format for Long Function Calls](Correct Format for Long Function Calls)
We do if there are lots of parameters - but there isn't a hard rule as to how many. I usually apply the line length 80 max - and if the line hits that I'll use a splat or multi-line parameters. See this rule [Correct Format for Long Function Calls](Correct Format for Long Function Calls)

@johlju - sounds like a bit more guidance around this area could be needed.
One final thing, my general rule of thumb if I'm contributing to one of these projects and there isn't a specific style rule is that I'll do my best to copy the existing code.

Personally I tend to use splatting when the lines start to move over ~80 chars. I actually have a ruler in VS Code just for this.
"editor.rulers": [
        80
    ]

The guidelines that I know of.

Use splatting for long calls Correct Format for Long Function Calls
Use named parameters Named Parameters Instead of Positional Parameters

But I have seen these variants.
Suggestion of what I think is good and bad, please comment on that. Also, please add any variants that I missed.
Variant 1 - Good ✔
$superLongVariableName = Get-MyVariablePlease -MyStringParameter '123456789012349012345678901234567890' -Verbose

Variant 2 - Good ✔
$superLongVariableName = Get-MyVariablePlease -MyString1 '1234567890' -MyString2 '1234567890' -MyString3 '1234567890' -Verbose

Variant 3 - Good ✔
The call is long, and will probably wrap when viewing it during the review. But still it should be allowed (?).
$superLongVariableName = Get-MySuperLongVariablePlease -MySuperLongStringParameter '123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890'

Variant 4 - Good ✔
$mySuperLongHashtableParameter  = @{
    MySuperLongKey1 = 'MySuperLongValue1'
    MySuperLongKey2 = 'MySuperLongValue2'
}

$superLongVariableName = Get-MySuperLongVariablePlease -MySuperLongHashtableParameter $mySuperLongHashtableParameter -Verbose

Variant 5 - BAD ❌
The call is very long, and will wrap a lot when viewing it during the review.
$mySuperLongHashtableParameter  = @{
    MySuperLongKey1 = 'MySuperLongValue1'
    MySuperLongKey2 = 'MySuperLongValue2'
}

$superLongVariableName = Get-MySuperLongVariablePlease -MySuperLongHashtableParameter  $mySuperLongHashtableParameter  -MySuperLongStringParameter '123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890' -Verbose

Variant 6 - BAD ❌
Hashtable is not following Correct Format for Hashtables or Objects.
$superLongVariableName = Get-MySuperLongVariablePlease -MySuperLongHashtableParameter @{ MySuperLongKey1 = 'MySuperLongValue1'; MySuperLongKey2 = 'MySuperLongValue2' } -MySuperLongStringParameter '123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890' -Verbose

Variant 7 - Good ✔
Splatting all parameters.
$getMySuperLongVariablePleaseParameters = @{
    MySuperLongHashtableParameter = @{
        MySuperLongKey1 = 'MySuperLongValue1'
        MySuperLongKey2 = 'MySuperLongValue2'
    }
    MySuperLongStringParameter = '123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890'
    Verbose = $true
}

$superLongVariableName = Get-MySuperLongVariablePlease @getMySuperLongVariablePleaseParameters

Variant 8 - BAD ❌
Hashtable is not following Correct Format for Hashtables or Objects.
$superLongVariableName = Get-MySuperLongVariablePlease -MySuperLongHashtableParameter @{ MySuperLongKey1 = 'MySuperLongValue1'; MySuperLongKey2 = 'MySuperLongValue2' } `
                                                       -MySuperLongStringParameter '123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890' `
                                                       -Verbose

Variant 9 - Good ✔
Good, but using auto formatting in VS Code will mess this up (?).
$superLongVariableName = Get-MySuperLongVariablePlease -MySuperLongHashtableParameter @{
                                                            MySuperLongKey1 = 'MySuperLongValue1'
                                                            MySuperLongKey2 = 'MySuperLongValue2'
                                                        } `
                                                       -MySuperLongStringParameter '123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890' `
                                                       -Verbose

Variant 10 - BAD ❌
Hashtable is not following Correct Format for Hashtables or Objects.
$superLongVariableName = Get-MySuperLongVariablePlease `
    -MySuperLongHashtableParameter @{ MySuperLongKey1 = 'MySuperLongValue1'; MySuperLongKey2 = 'MySuperLongValue2' } `
    -MySuperLongStringParameter '123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890' `
    -Verbose

Variant 11 - Good ✔
$superLongVariableName = Get-MySuperLongVariablePlease `
    -MySuperLongHashtableParameter @{
        MySuperLongKey1 = 'MySuperLongValue1'
        MySuperLongKey2 = 'MySuperLongValue2'
    } `
    -MySuperLongStringParameter '123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890' `
    -Verbose

Variant 12 - BAD ❌
Passing parameter (Verbose) outside of the splat.
$getMySuperLongVariablePleaseParameters = @{
    MySuperLongHashtableParameter = @{
        MySuperLongKey1 = 'MySuperLongValue1'
        MySuperLongKey2 = 'MySuperLongValue2'
    }
    MySuperLongStringParameter = '123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890123456789012345678901234567890'
}

$superLongVariableName = Get-MySuperLongVariablePlease @getMySuperLongVariablePleaseParameters -Verbose

Thanks guys. Regarding the 80 character (suggested) limit, is that from the start of the line, or from the first non-whitespace character?

I count from the start of the line, but there are okay to make it longer than 80 chars, there are occasions where I make longer lines too. :) So it’s good you think of it as a suggested limit and not a hard limit.

I make a PR with these changes tomorrow, so you can review it.


Malformed email can lead to warnings

In MailBounceHandler\Handler:
parseDsnFields() can return null for the 'perRecipient' element of the result array.
This ends in a warning in parseBodySectionMachine() on line 877 because 'perRecipient' is not an array.

Thanks for your contrib i will take a look

Solved in latest release (1.13)


add disclaimer for querying large record data

note on records.query() not guaranteeing data over a certain threshold
resolved code snippet

To see the specific tasks where the Asana app for GitHub is being used, see below:

https://app.asana.com/0/0/1205503725311932

checked with @diehuxx and she provided the correct threshold. good to go!


Easy Comms OFF not recognized

Easy communications is OFF in DCS settings. It is OFF in mission settings. VAICOM PTT window still says "Easy Communications ON."
I have master zeroized the entire program, uninstalled VAICOM, deleted all related folders in VoiceAttack, Saved Games, and ensured the export.lua is clean. I made a 100% fresh install via the community 2.8 version .msi installer from Github, no avail.
dcs-05NOC-easycoms.log
VAICOMPRO-05NOV-EasyComs.log

I have seen this on a few people's installs but cannot reproduce.

I can confirm this as an issue in 2.8. I followed the same steps. In fact I completely removed VIACOM Pro and Voice Attack as soon as it was broken in 2.8. I was already starting to use the Jester wheel again! I attached some screen shots of the configuration in VIACOM PRO with DCS 2.8 running and sitting in a hot started Tomcat.

I can confirm this as an issue in 2.8. I followed the same steps. In fact I completely removed VIACOM Pro and Voice Attack as soon as it was broken in 2.8. I was already starting to use the Jester wheel again! I attached some screen shots of the configuration in VIACOM PRO with DCS 2.8 running and sitting in a hot started Tomcat.

The screenshots shown are functioning as attended. This bug is referencing the "Easy Communication: ON" Line at the bottom of their PTT screen.
I have attempted to break mine and also can not reproduce this issue.

I had/have this issue as well. And I believe it has started after I used a SP mission with enforced "easy comms on"(due to mi-24 was not yet supported) after I used VAICOM with this mission, it got stuck at "easy comms on" always. Before that I used vaicom for years with no issues.
Later I found a workaround - If I start VAICOM, start a mission which has "easy comms on" then quit that mission and start a mission with easy comms off, then VAICOM correctly detects easy comms off.
This didn't fix after I changed my PC, altho I have copied back up of DCS and saved games, I have done full DCS repair, delete VAICOM from all related folders I could find and new VA and VAICOM install from github.

How many modules do you all have installed?

Also try deselecting instant select and see if that changes anything when loading.

How many modules do you all have installed?

It depends how we count and what qualify as modules, but all flyable + maps = 40, but if we count mods and other stuff like the GPS add-on, it is way more.
I see it might match the 38 modules bug, will try to test it tomorrow and report further.

Just checked my modules. If we're only counting official aircraft, terrains, and tech (supercarrier, WW2 assets) I have 41.

Sounds like this issue is tied in with #39

I can confirm that after uninstalling a few modules, so far "easy comms off" seems to be working correctly

Bug was fixed in previous release.


[Identity] update fix multiple accounts logic in IBC

Packages impacted by this PR
@azure/identity
Issues associated with this PR
Fixes https://github.com/Azure/azure-sdk-for-js/issues/28896
Describe the problem that is addressed by this PR
What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?
Are there test cases added in this PR? (If not, why?)
Provide a list of related PRs (if any)
Command used to generate this PR:**(Applicable only to SDK release request PRs)
Checklists

[ ] Added impacted package name to the issue description
[ ] Does this PR needs any fixes in the SDK Generator?** (If so, create an Issue in the Autorest/typescript repository and link it here)
[ ] Added a changelog (if necessary)

API change check
API changes are not detected in this pull request.


Add support for ViewPager

It would be great if you could set up the LoopBar with a ViewPager and let it behave like TabLayout from the Support Design Library.
Any doubts of seeing this feature in a later version of LoopBar?

Error:E:\xcode\LeranA\app\src\main\AndroidManifest.xml:8:9-41 Error:
Attribute application@label value=(@string/app_name) from AndroidManifest.xml:8:9-41
is also present at [com.cleveroad:loopbar:1.0.0] AndroidManifest.xml:14:9-46 value=(@string/enls_app_name).
Suggestion: add 'tools:replace="android:label"' to  element at AndroidManifest.xml:5:5-18:19 to override.
E:\xcode\LeranA\app\src\main\AndroidManifest.xml Error:
uses-sdk:minSdkVersion 15 cannot be smaller than version 16 declared in library [com.cleveroad:loopbar:1.0.0] E:\xcode\LeranA\app\build\intermediates\exploded-aar\com.cleveroad\loopbar\1.0.0\AndroidManifest.xml
Suggestion: use tools:overrideLibrary="com.cleveroad.loopbar" to force usage
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:processDebugManifest'.

Manifest merger failed with multiple errors, see logs

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

What went wrong:
Execution failed for task ':app:processDebugManifest'.

@PDDStudio This ability was added in 1.0.1
@woetao, @noblesky  crash was fixed in 1.0.1


Renames seqs to lang (short for language)

Several of us have been confused by the similarity of seq and seqs. In
the regex reexamined paper they call a set of sequences a language in
the context of regular expressions. This shortens to lang.
This is something that came up in the pairing yesterday. Can anyone else think
of a better name? Should we also rename seq to string or str?
NB: PDF have changed because of https://github.com/awalterschulze/regex-reexamined-coq/pull/114/files#diff-2a27707e33c328861511ef9552df2b51R15

I like the lang idea.
We can also rename seq to str and update the paper to say string instead of sequence, but we can do that in a separate step.
I think the markdown has changed before, which resulted in the pdf changing, if you regenerate it.
But this commit doesn't contain the changes to the markdown, so maybe we can update the pdf in a separate commit.

Haha I didn't read your second part of the description, seems we have the same idea about str :)

We can marge this first https://github.com/awalterschulze/regex-reexamined-coq/pull/115
then yours can be a commit that only renames seqs to lang, because this doesn't need to modify the paper.
And then we can have a follow up that renames seq to str, including renaming sequence to string in the paper.
What do you think?

@awalterschulze - good idea let's do that, sorry I misunderstood why the PDF had changed.

No I am sorry, I should have updated the pdf, when I changed the markdown, I was lazy.

Thanks for doing this! I still feel like it was my fault for getting confused, but this new naming seems nice.

We should also split renaming the file Sequences.v and renaming seqs in two separate commits.
Otherwise it will just look like a new file.

@mheiber you were not the first.  You were simply the last, that pushed this over the line and made it obvious that it needed renaming.

@mheiber I was confused by this every time I came back to the repo. I also learned how to do find and replace efficiently in a project with counsel-rg and wgrep in emacs.


Added --dynamic flag to allow dynamic queries

Thank you! Good solutions!
Thank you, good solution. But I want to leave my contribution and how I resolved it.
My problem:
I needed to publicly expose this on the internet with a security / authorization rule
Solution:
It didn't work on a docker at all, due to the release of port 3000 and a problem with the node's express service. I changed the strategy, uploaded a Node.js server (version 14.16.0 LTS) and installed xmysql and changed the xapi.js file according to print
To expose the service on the internet, I initially used ngrok, but with the session expires in 2 hours, I started using the cloudflare argo tunnel https://developers.cloudflare.com/cloudflare-one/connections/connect-apps
Then I added a rule in the Cloudflare Firewall to block and release access (http.host eq "domain.com.br" and not any (http.request.headers ["myheader"] [*] == "hashcode"))
Grateful :)


It is possible to get image width and height using this library?

Hello! I need to limit minimum crop area by 1/2 of the image width and height. It is posiible to get these properties using this library?

You can use this code to get image width and height and divide them by 2:
                        val rectWith = crop.cropRect?.width() ?: MIN_CROP_SIZE_FALLBACK
                        val rectHeight = crop.cropRect?.height() ?: MIN_CROP_SIZE_FALLBACK
                        setImageCropOptions(
                            CropImageOptions(
                                minCropResultHeight = rectHeight / 2,
                                minCropResultWidth = rectWith / 2
                            )
                        )


Added performance benchmarks to background platform channels for iOS.

issue: https://github.com/flutter/flutter/issues/91635
Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

I had to switch the host code from Swift to ObjC because of https://github.com/flutter/flutter/issues/97968.  I think that might be a local problem for my build system but I couldn't seem to resolve it.

Here are the local results for the tests:
flutter: BasicMessageChannel/StandardMessageCodec/Flutter->Host/Small: 55.2 µs
BasicMessageChannel/StandardMessageCodec/Flutter->Host/Large: 757.5 µs
BasicMessageChannel/BinaryCodec/Flutter->Host/Large: 53.9 µs
BasicMessageChannel/BinaryCodec/Flutter->Host/1MB: 314.4 µs
BasicMessageChannel/StandardMessageCodec/Flutter->Host/SmallParallel3: 28.4 µs
BasicMessageChannel/StandardMessageCodec/Flutter->Host (background)/Small: 43.7 µs
BasicMessageChannel/StandardMessageCodec/Flutter->Host (background)/SmallParallel3: 23.6 µs

20% reduction on small payloads serialized, 17% reduction on parallel small payloads.

friendly ping @dnfield

@renyou @angjieli another issue with Google testing missing this PR. Is there a tracking issue for these types of bugs? FRoB says this PR already exists in the database when I tried to trigger it

Since this is just adding a test and the google testing step is hung @CaseyHillers says I can land this without it.


Create problem: Ksusha and Array

The problem is that your code has a time complexity due to the nested loops.
For an array of size 10^5, this would require up to 10^10 operations, which is too many for a program with a 2-second time limit.
My proposed solution would be to check for the minimum element in the array, and then check if all the elements are divisible by that minimum element.
If there is a number in the array that divides all numbers, it must divide the minimum element as well.
Here is one way to implement it:
/*
The problem is that your code has a time complexity due to the nested loops.
For an array of size 10^5, this would require up to 10^10 operations, which is too many for a program with a 2-second time limit.

My proposed solution would be to check for the minimum element in the array, and then check if all the elements are divisible by that minimum element.
If there is a number in the array that divides all numbers, it must divide the minimum element as well.
*/

#include <iostream>
#include <climits> //this is for the INT_MAX constant
using namespace std;

int main()
{
    const int max_capacity = 10e5;
    int arr[max_capacity];
    int min_element = INT_MAX; //we initalize the min_element to the maximum possible value of an integer so that later, we can replace it with the minimum element in the array :)
    bool isDivisible = true; //this is the flag in your interpretation

    int actual_size;
    cin >> actual_size;

    for (int i = 0; i < actual_size; i++) {
        cin >> arr[i];
        if (arr[i] < min_element) {
            min_element = arr[i];
        }
    }

    for (int i = 0; i < actual_size; i++) {
        if (arr[i] % min_element != 0) {
            isDivisible = false;
            break;
        }
    }

    if (isDivisible) {
        cout << min_element;
    }
    else {
        cout << -1;
    }

    return 0;
}

Feel free to ask follow-ups. Good luck coding!

It takes long time to find your comment, thank you shehab for your helping but may you simlify the explanation a little more because i didn't get what you want to do.. if you don't have the time to do so, feel free not to reply... i'll reread it in another time..

I think i begin to understand what you meant to do,
For the division to give integer number the numenerator must be greater than the denomenator, so you get the minimum nuber and chech its condition only, not as i made check for each element, right?
But the last edit for my code was to check this condition before entering the loop of division so i thought cheking the condition is less im time than taking modules of numbers
Thanks a lot for your help

No worries, github can be difficult to navigate. Yep, you're getting there..
Basically your code is flawless as a solution for the problem but in case of CodeForces, the website implements a time limit which is the reason why it doesn't run through all the tests, the reason behind the time limits exceeding is because it checks every possible number in the denominator from the array which takes too long for the program, so a more efficient proposal would be to make the program check only for the minimum number in the denominator since it must divide all other numbers.. Here is a code similar to the one on yours with this simple change:
#include <iostream>
using namespace std;

int main()
{
    const int max_capacity= 10e5;
    int arr[max_capacity];
    int flag=1;
    int actual_size;
    cin >> actual_size;

    // Read the array
    for(int i=0; i<actual_size; i++)
        cin >> arr[i];

    // Find the smallest number
    int min_num = arr[0];
    for(int i=1; i<actual_size; i++)
    {
        if(arr[i] < min_num)
            min_num = arr[i];
    }

    // Check if min_num divides all other numbers
    for(int i=0; i<actual_size; i++)
    {
        if(arr[i] % min_num != 0)
        {
            flag=0;
            break;
        }
    }

    // If min_num divides all numbers, print it, otherwise print -1
    if(flag)
        cout << min_num;
    else
        cout << -1;

    return 0;
}

hope it helps, feel free to ask follow-ups. Good luck!

no problem at all, there is no ideal code in programming, it's all different approaches and they're all great, the best code is the one that can be read by someone who doesn't know anything about coding at all and still manages to understand it :D! (for example, my first approach in this code wasn't rly ideal because it used unneccessary elements)
It won't really take that much time, i recommend the following:

Codecademy: A website that offers free interactive coding courses in different languages
here's the C++ course page: https://www.codecademy.com/courses/learn-c-plus-plus/lessons/cpp-hello-world
it acts as an interactive reference, you read snippets and you apply them into a compiler alongside. so it's a good step-by-step help.
Sololearn: Another great website that offers free courses and helps move at the time pace you choose, they have a mobile app too i believe.
Youtube is loaded with videos explaining different aspects of the languages, a personal favorite is Harvard's CS50

Personally, i think it's best to keep practicing on CodeForces too, they have good, varied problemsets that will surely help. Certainly, it won't be easy to get the answer on first try, but the trials help strengthen your skills. Always, search the web when you face errors and see others with similar issues. Make a folder on your PC, dedicated to programming exercises and always try to challenge yourself with tasks just for fun (ex.: i'd like to make a weather app using c++, is this possible?), you'll automatically find yourself searching the web and using different languages,too! You don't need to always accomplish the task but you'll be learning.
Also, there is no "bad questions", always ask and search for questions online. its how we learn. Good luck!

Very grateful for you.. shokraaan

Anytime, happy to help.. El3afo ^^


Program Freeze if ManualResetEvent is passed into new thread

Describe the bug
When you show a window in a new thread and surround the call with a ManualResetEvent, the window never opens.
Steps to reproduce
I have prepared a sample application here: MahAppsMetroResetEvent
I have a main WPF window that creates a window in a new thread. Just click the button in the sample app.
As soon as you comment out the section Using ready As New ManualResetEvent(False) in file Box.Box the window is shown. So I guess it must have to do something with the reset event.
Expected behavior
I would expect that a new window in a new thread is being created.
Actual behavior
The application freezes and the new window is never shown.
Environment
MahApps.Metro version: v2.2.0
Windows build number: Win10 1809
Visual Studio: 2019 16.7.2
Target Framework: v4.8

@Ksdmg The ShowDialog method of a window opens the window modal, so you should change the order of  these to lines
                                           Box.ShowDialog()
                                           ready.Set()

to
                                           ready.Set()
                                           Box.ShowDialog()

@punker76 thanks for the fast answer.
I need the order like this to pause the main thread until the newly dialog has been closed. If you remove all MahApps.Metro references from the child window and make it a normal window it shows up just fine.

@Ksdmg I tried again your test sample together with the latest v2.3.4 and it seems the issue is gone. I will close this for now. If you still have trouble with this then reopen this one. Thx


Gradle Daemon has large and increasing memory footprint.

The Gradle daemon is ~0.5GB of memory after a single build of the project for Aeron and increases in size with each subsequent build. Over the course of this morning it grew to 1.5GB.
I'm building on Windows 10 with Gradle 3.4.1 and Java 1.8.0_121.
A heapdump shows the process is mostly char[]s and Strings.

Thanks for the note. We are looking at this under #1582. Closing as duplicate.


TF-Lite Micro: Selectively omit data types at compile-time

My application only requires kTfLiteInt8 kernels.
However, kTfLiteFloat32 and kTfLiteUInt8 kernels are also built into the application.
It would save a considerable amount of code space if there was a way to disable building in the unused data types, e.g.:
  switch (input->type) {  // Already know in/out types are same.
#ifndef TFLITE_FLOAT32_DISABLED
    case kTfLiteFloat32:
      return EvalFloat(context, node, params, &data, input, filter, bias,
                       nullptr, nullptr, output);
      break;
#endif
#infdef TFLITE_INT8_DISABLED
    case kTfLiteInt8:
      return EvalQuantizedPerChannel(context, node, params, &data, input,
                                     filter, bias, output, nullptr);
      break;
#endif
#ifndef TFLITE_UINT8_DISABLED
    case kTfLiteUInt8:
      return EvalQuantized(context, node, params, &data, input, filter, bias,
                           nullptr, nullptr, output);
      break;
#endif
    default:
      context->ReportError(context, "Type %s (%d) not supported.",
                           TfLiteTypeGetName(input->type), input->type);
      return kTfLiteError

Or something more elegant ;)

@advaitjain ping :)

Hello @driedler , I'm facing exactly the same issue as you, were you able to select only int8 type ?

Closing this issue in favor of https://github.com/tensorflow/tflite-micro/issues/720


Run App: Prompt user to upgrade labware definitions when uploading a JSON protocol to the robot

User Story
As a PD user, I should be notified of an outdated labware definition when loading my JSON protocol onto a robot via the Run App.
Acceptance Criteria

[ ] User should be prompted with a notification to import their protocol with outdated labware defs back into PD in order to update it.
[ ] TBD - should the user be able to proceed to run the protocol without updating?

UI Design
[Add Zeplin link]

Bug triage determination: MLM


stubbing capybara-webkit

Hello,
i'm trying to intercept and stub https requests from capybara-webkit driver to external site pages, which are resided in internet. I see that currently by default webmock can't intercept them.
So my question is how to intercept calls from capybara-webkit surfing visits.

I got exactly the same question

There is no way to do that with webmock
capybara-webkit runs webkit engine which is an independent headless browser.
WebMock operates on server side only.
You could perhaps load additional js code in test environment which uses https://github.com/node-nock/nock to stub js requests.
or use something like https://github.com/hashrocket/capybara-webmock but that doesn't work with capybara-webkit.
https://github.com/oesmith/puffing-billy seems to support webkit.


run-migration is broken after ESM migration

Current behavior:

Generate migration. It will produce .js file with export default ESM statement
Run run-migration. Error will be thrown, because Node.js didn't expect to see ESM export in .js file

Expected behavior:

Migration is executed without error

Steps to reproduce:
Steps are described in Current behaviour section.
Related code:
Code that broke the functionality - https://github.com/storyblok/storyblok-cli/commit/891af62c7a628286f507299b19128a2193a55550#diff-2c9538c486ae6103ef79ac65657bf841191ae869f4992158328e6739c28e463c
Other information:
To fix the issue, you need to generate .mjs files, not .js.
Current "fix" for me is to use --experimental-detect-module flag, but that's not safe.

I am running into the same issue, but your "fix" using --experimental-detect-module doesn't work for me. It just tells me error: unknown option '--experimental-detect-module'. Which CLI version did you install @privetkuku ?

@OFranke, I have 3.30.0 version installed. '--experimental-detect-module' was introduced in Node 21.1.0` and you need to pass it to the Node itself, not Storyblok.
I use pnpm, for me it looks like this: NODE_OPTIONS='--experimental-detect-module' pnpm storyblok ....
Hope that helps.

@christianzoppi, can you please into it?

Hey there @privetkuku @OFranke I'm currently checking out this issue.
If I understand correctly, the problem comes when trying to run previous generated CJS version of the migrations in the newest versions right? I guess it also depends of the Node version of the project, if it's using >18 or not 🤔.
Would be the ability of choosing the exports via flag like --exports=esm|cjs a good option for you? I would suggest in parallel to migrate to ESM-only in the near future since its more future-proof.

Hello @alvarosabu, thanks for looking into it!
After version bump back then, even newly created migrations were not able to run due to the described reasons in Current behavior section.
I see your fix #116, I think it should do the job🦉


plugin enabled table merge error in version 0.7.0

Hi
I found a bug in kong 0.7.0 when I add some custom plugins to kong.yml.
when I use management api to get the plugins list  (http://localhost:8001/plugins/enabled)
I found the plugin names on the top of the list which should be the exist plugins are overwritten by the custom plugin names.
Perhaps it because the code below (kong/tools/config_loader.lua   row 185)
config.plugins = utils.table_merge(constants.PLUGINS_AVAILABLE, config.custom_plugins)
When merge the two tables (key=index ,value=plugin name) with util.table_merge, the second table will  use the same index key to overwrite the first table's value but not append itself because they have the same key.

@thefosk I overwrite the lua file by the latest code and the bug is fixed.
Thank you very much.


New site: Code of Conduct

Create a "generic" code of conduct page that we can link to from all other locations.
Once this is merged, we can update all groups.io and other links to point to a single, easy to maintain code of conduct.
Should we also update the COC's in various repos to point to this? I think yes.

Where on the site should this be linked from?
If there is a community section, certainly from there. Probably as the intro to the community section.

Markdown for the COC is here:
https://raw.githubusercontent.com/ponylang/ponyc/master/CODE_OF_CONDUCT.md
I've reviewed it and its nice and generic already.

Done. Its in the new website. Will go live when merged. Added COC related tasks to #24.


Use ClusterInfo from streaminfo to get clustername too

Signed-off-by: gargnupur<EMAIL_ADDRESS>Description: Use ClusterInfo from streaminfo to get clustername too
Ref: https://github.com/istio/istio/issues/21566
This will help get name of the blackhole cluster
This depends on PR: https://github.com/envoyproxy/envoy-wasm/pull/460, but separating into a separate PR, so that this is easy to cherry-pick to istio/envoy 1.5 release.

/cc @kyessenov


✨ Adding google services key (protected key)

syncing up the approach used for the RN project, we include the google-services.json while hiding the key as GOOGLE_SERVICES_KEY placeholder

Found an issue with the latest android image, changing from default to a static reference for now until we take a proper look at whats happening there.

(tests are passing locally)

(tests are passing locally)

looks like its that old flakey analytics test 😔 fine to ignore, but wish we could sort that one out.


Sample Source Confirmation

Quick start example in description
It doesn't even build
Error description :
ZUMOAPPNAMEService: The path and / or file name you specified is too long. The fully qualified file name must be less than 260 characters and the directory name must be less than 248 characters. Failed to restore NuGet package for project.

This is a common problem (nothing to do with ZUMO) for Xamarin development.  I find placing the project right off the root drive works. (I place mine in C:\gh\azure-mobile-apps-net-client, for instance)


ToolManager: shortkey_to_tool_map_ not updated when removing tools

I'm part of a DRC team, and we have our own rviz fork. Since we have our own tools that use librviz, we don't use the tools that are initially inserted when you create a new visualization manager. So, we do
manager_ = new rviz::VisualizationManager( render_panel_ );
manager_->getToolManager()->removeAll();

and then we add our own tools. I have just rebased our fork, and found that the following line caused issues:
https://github.com/ros-visualization/rviz/blame/indigo-devel/src/rviz/tool_manager.cpp#L140
It will insert a new uninitialized Tool* into  shortkey_to_tool_map_ if it doesn't have that key in the map already, and causes the application to segfault a few lines after that when trying to set it as the current tool.
I'd suggest changing that line to the following:
Tool* tool = NULL;
  // need to check if it exists in the map, otherwise it will create an uninitialized Tool* with the event->key() inside shortkey_to_tool_map_ and it will segfault later on when trying to access it
  if( shortkey_to_tool_map_.find(event->key()) != shortkey_to_tool_map_.end() )
    tool = shortkey_to_tool_map_[ event->key() ];

Now, that by itself doesn't solve the issue that I'm having: shortkey_to_tool_map_ is never updated outside AddTool. After I remove all tools, shortkey_to_tool_map_ will retain all keys and invalid Tool*, causing it to crash.

@hdeeken do you have time to take a look at this issue?
@fbacim I'll have to dig into this to understand what needs to be changed beyond your suggestion, but I can't say right now when that will be. I'll try to work it in opportunistically.

@ wjwwood  @fbacim RemoveTool obviously needs to alter the map as well. My bad! I'll get to that asap, hopefully within the weekend, otherwise on monday morning. ;)

@hdeeken thanks, sorry I missed that in the review on the first go around.

Bump, does anyone have time to look into this?

@wjwwood the above patch should correctly manage the shortkey map now. i'm sorry for fixing this so late, i completely lost track of that! :(

@hdeeken that's ok, @fbacim do you have any time to try his patch and see if it addresses the issue for you?


Swapping out sprites with Mona

Swapped out main logo, octocat sprites, and arrow sprites (with transparent arrows, because they're lame). Also changed the playback speed of the pacman sprites so its not so frantic with mona, but it hasn't been built/compiled, so no change in the build yet...

Looking great ✨


Dynamic filtering

Allows filtering to be turned on and off, tutorial updated to demonstrate.

Bother, failed unit tests, and I cunningly was using the --fast option, so I didn't see the fails in features.  Closing and will update.


to add qwen-int4 support

I need qwen-int4 support too!

when I run qwen-int . throw a error like this
ValueError: Quantization is not supported for <class 'vllm.model_executor.models.qwen.QWenLMHeadModel'>.

I have a draft PR open in AutoAWQ but the Qwen implementation is buggy compared to other models. Waiting for Qwen to be streamlined a bit more or for someone to help create a workaround.
https://github.com/casper-hansen/AutoAWQ/pull/78

+1

+1


Make sure new cortical areas arent created on top of each other in BM

also ensure no overlap at all (not just position check)

this is a little harder to do efficiently (trying to avoid a linear search type solution)


RFC 2: tBTC liquidation recovery functionality

The outline and required inputs are all clearly listed out, but the juiciest
parts are still stubs, of course; namely, how to compute all the inputs that
require computation.

So far it looks very good, all inputs are very well explained. 👏 As stated in the PR description, the juiciest parts are still stubs, so just adding some early thoughts on those juicy details.
I like the RFC does not require operators to run a BTC node. That would be a significant effort for some of them. Since this is the low-effort mechanism, can we just output the signed transaction to logs (or to some file, if really needed) and let operators do the broadcast on their side? If we document a way of how to do that in the RFC, this should be enough in my opinion.
Regarding the action triggering this whole mechanism, I was first thinking about having a simple CLI command in the client, similar to the signing or key material share decryption action, where the operator would put beneficiaries and keep address as an input. However, this seems wrong for a variety of reasons. First, there is no clear way of how operators should coordinate on when to trigger this action. Secondly, signing requires peer discovery, so this command should send a request to a running client instance instead of triggering some action as a completely separate process. Finally, there is no proven track of inputs operators provided.
Given that we need to get some data from tBTC deposit contract, then get some data from ECDSA keep contract, each operator needs to provide some data, and all of it should be triggerable only for terminated (or also closed if we want to handle misfunds) keeps, we can implement an on-chain contract for coordinating all of it. Operators would submit their beneficiary addresses and as soon as all beneficiaries are known, the contract would emit an event, application-specific actions in the client would react on.
One may argue that implementing a contract adds some work but I do not think it's a significant effort and getting some data on-chain can be easier than computing them in the client. Secondly, we are not implementing any new mechanism for triggering client actions - it is just an event subscription so it's in fact less work on the client-side. Last but not least, operators would have a trustless way to coordinate and track the progress of recovery. Finally, there would be a proven track of BTC beneficiaries provided.

So far it looks very good, all inputs are very well explained. 👏 As stated in the PR description, the juiciest parts are still stubs, so just adding some early thoughts on those juicy details.
I like the RFC does not require operators to run a BTC node. That would be a significant effort for some of them. Since this is the low-effort mechanism, can we just output the signed transaction to logs (or to some file, if really needed) and let operators do the broadcast on their side? If we document a way of how to do that in the RFC, this should be enough in my opinion.
Regarding the action triggering this whole mechanism, I was first thinking about having a simple CLI command in the client, similar to the signing or key material share decryption action, where the operator would put beneficiaries and keep address as an input. However, this seems wrong for a variety of reasons. First, there is no clear way of how operators should coordinate on when to trigger this action. Secondly, signing requires peer discovery, so this command should send a request to a running client instance instead of triggering some action as a completely separate process. Finally, there is no proven track of inputs operators provided.
Given that we need to get some data from tBTC deposit contract, then get some data from ECDSA keep contract, each operator needs to provide some data, and all of it should be triggerable only for terminated (or also closed if we want to handle misfunds) keeps, we can implement an on-chain contract for coordinating all of it. Operators would submit their beneficiary addresses and as soon as all beneficiaries are known, the contract would emit an event, application-specific actions in the client would react on.
One may argue that implementing a contract adds some work but I do not think it's a significant effort and getting some data on-chain can be easier than computing them in the client. Secondly, we are not implementing any new mechanism for triggering client actions - it is just an event subscription so it's in fact less work on the client-side. Last but not least, operators would have a trustless way to coordinate and track the progress of recovery. Finally, there would be a proven track of BTC beneficiaries provided.

Actually just pushed what I had last night. More detail later today, but what I've already added is important to clarify a few edges.

Actually just pushed what I had last night. More detail later today, but what I've already added is important to clarify a few edges.

(Quick note: that last commit is messy and in-flight to make sure it's not sitting on one hard drive ready to be lost. Will be cleaning it up soon.)

(Quick note: that last commit is messy and in-flight to make sure it's not sitting on one hard drive ready to be lost. Will be cleaning it up soon.)

Regarding the action triggering this whole mechanism, I was first thinking about having a simple CLI command in the client, similar to the signing or key material share decryption action, where the operator would put beneficiaries and keep address as an input. However, this seems wrong for a variety of reasons. First, there is no clear way of how operators should coordinate on when to trigger this action. Secondly, signing requires peer discovery, so this command should send a request to a running client instance instead of triggering some action as a completely separate process. Finally, there is no proven track of inputs operators provided.
Given that we need to get some data from tBTC deposit contract, then get some data from ECDSA keep contract, each operator needs to provide some data, and all of it should be triggerable only for terminated (or also closed if we want to handle misfunds) keeps, we can implement an on-chain contract for coordinating all of it. Operators would submit their beneficiary addresses and as soon as all beneficiaries are known, the contract would emit an event, application-specific actions in the client would react on.
One may argue that implementing a contract adds some work but I do not think it's a significant effort and getting some data on-chain can be easier than computing them in the client. Secondly, we are not implementing any new mechanism for triggering client actions - it is just an event subscription so it's in fact less work on the client-side. Last but not least, operators would have a trustless way to coordinate and track the progress of recovery. Finally, there would be a proven track of BTC beneficiaries provided.

Thinking more about it and reading @Shadowfiend's comments I am not longer sure what I proposed is an optimal long-term solution.
An advantage of having a contract and building a UI around it would be to allow stakers (owners) to track the progress. We have some stakers in the network with 10+ liquidated deposits and keeping an eye on them requires communication with the team and having an operator willing to track those deposits and doing this communication.
Another advantage would be that we can probably reuse some tbtc.js parts to construct BTC transactions without having to implement it in the client.
Finally, querying for pending recoveries upon client restart could be simpler. Instead of having to go through all keeps and checking if they are terminated, we could be calling one contract with a function optimized for this purpose.
However...
With application-specific actions in the client, monitoring scripts ran by the community, and the development of external collateralization management services, having a lot of liquidated deposits for a single staker should hopefully no longer be a problem in the future.
Querying keeps one by one needs to be done anyway because we are checking for pending signatures.
This contract would not provide any additional security guarantees as it is not enforcing where tokens are finally transferred.
Finally, what's the most important here IMO: having it all in the client does not require any action to be taken by operators. Ether cost is one thing but more importantly, other signing group members will not suffer from one operator not executing their on-chain part. The fact we eliminate manual actions is a big win.

Ok, open season folks, officially marking this Ready For Review™. The Implementation Details section now includes several mostly-complete functions to do the most important Bitcoin manipulations needed to make this work. The Implementation Behaviors section steps through higher-level bits like key material archiving changes, startup behavior, Bitcoin fee resolution, adjustments to the signing protocol, and the method to submit signed transaction hex.
All sections that could benefit from a connection to a Bitcoin node specify optional behaviors in cases where a Blockstream Electrs fork is available for usage. Usage defaults to Blockstream's public API unless explicitly disabled in configuration*.
Some high-level bits of feedback I'm looking for specifically:

Thoughts on everything under “Implementation Behaviors”.
Thoughts on the optional Bitcoin node functionality.
Anything that feels like it's missing or unclear in the RFC.
Any missing code or other detail in the Implementation Details section.

As always, any other thoughtful feedback is also welcome :)
*- do we want to default this to on, or default it to off and strongly encourage it in the sample config?

On a more meta level, what do you think about putting some description in the filename of the rfc, like rfc-2-liquidation-recovery.adoc, that way when someone is trying to pull up the RFC in the future, they're not having to open the actual files and can scan the /rfc directory

I'm a little confused about how we're collecting the BTC addresses and who is running the command. Is this something that would plug into the ecdsa cli client? If so, does support run the command or would the signer?
The implementation needs to have a btc address for each of the signers, but in the implementation details, we're putting a single btc address in the configuration file. How does each client collect the other addresses?

BTC addresses are provided by each respective client for their own memberships in various deposits, as specified in the section on Specifying an Operator's Bitcoin Recovery Address. The client itself automatically starts the process for a given deposit when its keep transitions to the TERMINATED state, as described in the section on Modification of key material archiving.

Ok, I believe all comments are handled here. I also reworked the whole process of going from ready message -> sighash -> signed transaction. The process now, as suggested by @nkuba, starts by constructing an unsigned transaction. The unsigned transaction has placeholder dummy signature and pubkeyhash data in order to properly estimate the fee, since that data is not used to generate the sighash. Once the signature is available, the witness script is attached to the existing unsigned transaction and then the whole thing is turned into a hex string.
Everything about this approach is better, especially the part where the fee calculation results in a signature that is actually valid :grimacing:

Merged master, believe this one is ready to go.


No protection against divide-by-zero error

In the simple case where a history of length two is specified, and the x parameter stays constant a divide by zero is possible here:
https://github.com/geopm/geopm/blob/dev/src/DerivativeSignal.cpp#L101
Other scenarios may also produce a divide by zero.  A check should be put in place.  Also consider a special branch for the history length 2 case which is just a difference equation.

Related to https://github.com/geopm/geopm/pull/1584

https://github.com/geopm/geopm/blob/dev/service/src/DerivativeSignal.cpp#L102


Font Awesome icons don't render of Safari

The navigation bar relies of the font awesome icons. They provide the image for links such as home or projects, etc... The issue it that on mobile platforms the supporting text is removed in order for the navigation bar to display on the screen at an appropriate size. However, on Safari, the flagship browser for all Apple devices (Ipad, Iphone, MacBook, etc... ) font awesome icons do not render.

There are two options for solutions:

Use a different icon package for the website
Tell people using Safari to open the site in a different browser

We have decided to move to material design icons. These are available across multiple platforms and operating systems.


Modified UaaHttpRequestUtils to build an HTTP client that uses the system proxy settings.

See issue 411

Coverage decreased (-0.2%) to 83.719% when pulling fb1e69e9dac4aa98a6d8cd522d879881501a087b on GESoftware-CF:oidc_proxy_issue into 35a811e3d5033c728c84e0d1f47cbadb2b548df2 on cloudfoundry:develop.

retest this please


Not seeing an upgrade guide mentioning removal of R.__

I like R.__ – what am I meant to use instead?

@flipactual Are you referring to how it isn't showing up in the docs right now?
You will find it here:
https://ramdajs.com/0.25.0/docs/#module.exports
There is an issue with the docs at the moment

Thank you @functionalStoic – I thought it was gone since it isn't showing up where I expected it in the docs

While there has been talk of removing the placeholder, it hasn't actually been removed, nor is there any plan for it in the near future (it would be post 1.0).
The docs are broken, but the placeholder is still there.
To answer your question though, I got a chuckle because the answer is right in your name 😉
R.contains(R.__, arr) === flip(R.contains)(arr)

@Bradcomp 😂 very good!
And what if I would like a placeholder in the middle?

It gets tricky if you want to stay Point Free.
I am personally not on the side of removing the placeholder for that reason, as well as because it helps when using the very controversial comparison functions like gt
R.gt(R.__, 5)    //this makes sense
R.flip(R.gt)(5)  //wat
R.lte(5)         //The same, but now you've lost semantics


fix typo

Coverage remained the same at 80.435% when pulling 2ba8e21c8ff5449a4465ae40c3fefcca70bbf454 on devel into 46740d2c7741bfef5c41751200e99a45294b3018 on master.

Coverage remained the same at 80.435% when pulling 2ba8e21c8ff5449a4465ae40c3fefcca70bbf454 on devel into 46740d2c7741bfef5c41751200e99a45294b3018 on master.


Visualization preprocessor should not catch errors

Pull Request Description

related #6323
Fixes the following scenario:

preprocessor function catches ThreadInterruptedException and returns it as a JSON  {"error":"org.enso.interpreter.runtime.control.ThreadInterruptedException"}

engine thinks that the visualization was computed successfully and just returns it to the user (without doing any fallback logic like retrying the computation)
IDE displays blank visualization

Important Notes

Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.

This scenario can be quite hard to re-create. I was able to reproduce it more or less reliably on one of the last bookclub projects by opening and closing the visualization multiple times.


make check fails with GCC 4.9 on Mac OS 10.10.1

What steps will reproduce the problem?
brew install google-sparsehash --cc=gcc-4.9 --build-from-source

What is the expected output? What do you see instead?
Success.

What version of the product are you using? On what operating system?
sparsehash 2.0.2
Mac OS 10.10.1

Please provide any additional information below.

Running HashtableDeathTest.InsertSizeTypeOverflow
terminate called after throwing an instance of 'std::length_error'
what():  vector::_M_fill_insert
/bin/sh: line 1: 71227 Abort trap: 6           ${dir}$tst
FAIL: hashtable_test

Complete logs:
❯❯❯ brew gist-logs google-sparsehash --cc=gcc-4.9 --build-from-source -v
https://gist.github.com/5a6b10ab7ba0e0f8402f

Original issue reported on code.google.com by sjackman on 26 Jan 2015 at 6:26

Pretty sure this is fixed, trying to track down the commit. I had a problem on OSX until I updated to 2.0.3

Please try with 2.0.3.
Comment if it comes up again.


Updated recursive folder command

Doesn't need echo filename command anymore for the latest version.

Thanks!


respect context timeout in shim binary call

under the efforts of https://github.com/containerd/containerd/pull/3206, https://github.com/containerd/cri/pull/924, https://github.com/containerd/cri/pull/884, containerd works fine in many cases. However, containerd still cannot to recover if there exist some shim which hang forever(start and delete), the timeout here takes no effect https://github.com/containerd/containerd/blob/main/runtime/v2/shim.go#L143
Signed-off-by: jerryzhuang<EMAIL_ADDRESS>

I assume this should be marked for cherrypick to supported releases as a bug fix?

/ok-to-test


Eliah Kagan: Watch curibo.co.uk

Eliah Kagan requests the watch of the watch_keyword curibo\.co\.uk. See the MS search here and the Stack Exchange search here.

curibo\.co\.uk has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Makyen in Charcoal HQ


Release 0.13.0

LGTM, I have tested in our k8s cluster and the ECS demo. Looking beautiful.
I have run again into https://github.com/weaveworks/scope/issues/868 and https://github.com/weaveworks/scope/issues/827 though. Marked them as 0.14

/summon @pidster for lgtm'ing the release.
I still have testing to do, but it's going well so far.
On Friday, 26 February 2016, Alfonso Acosta<EMAIL_ADDRESS>wrote:

LGTM, I have tested in our k8s cluster and the ECS demo. Looking beautiful.
I have run again into #868
https://github.com/weaveworks/scope/issues/868 and #827
https://github.com/weaveworks/scope/issues/827 though. Marked them as
0.14
—
Reply to this email directly or view it on GitHub
https://github.com/weaveworks/scope/pull/1045#issuecomment-189385240.

Probably want to include this in the release https://github.com/weaveworks/scope/pull/1052 (PR is targeting this release branch)

I'm LGTM on this release now

LGTM now

LGTM


Feature/open classes for extension for enum ref

What's this PR do/fix?
It changed some modifiers of 4 classes from private to protected (and extracted one method), so enum type references (as proposed with #1738) could be implemented.
Are there unit tests? If not how should this be manually tested?
I added unit tests with separate commit - testing using reflection that methods have now protected modifier, so subclasses can override or invoke them.
What are the relevant issues?
Issue: #1738

@dilipkrish,
could You review this tiny PR please?

I have reached out about helping with an ultimate solution for this problem, but in the mean time @atsu85 are you willing to share your solution that builds upon this PR?

@robertjamesmccullough,

@atsu85 are you willing to share your solution that builds upon this PR?

Yes, i'll try to prepare a sample project that includes classes that take advantage of this PR to create enum references. However i can't do it right now, so don't expect it in a day or two.
I'll have to note, that enum references are not valid in all places, for example query parameters - my solution doesn't solve that, but otherwise it works well in our project

Thank you @atsu85... I'll try to get your solution or something that accomplishes something similar in the next release. Sorry this has been languishing

As i promised, i tried to add sample code for generating enum-refs into springfox-petstore but stumbled upon couple of problems

There are some test failures that appear to fail only on windows (see #2257 - fixed only couple of them) - would be nice to verify what tests naive enum-ref implementation would break.
Didn't figure out how to start springfox-petstore outside tests - gradlew bootRun -p springfox-petstore doesn't work.
I'm going to deal with it later, right now i'm going to sleep ;)

@atsu85 Trying to validate this PR would you mind making the changes that build on this PR in the the demos project. You should have instructions to start the project/run it etc.
Also when u have a chance you need to resolve the conflicts in this PR and squash the merge commits.


TypeError: msecs must be a number

The SSHAgentClient constructor does not set this.timeout if options is not provided, which results in a TypeError when #_request calls Socket#setTimeout with undefined. (See: jcoglan/vault#29.)

fixed via https://github.com/mcavage/node-ssh-agent/pull/5

Closing this because #5 has been merged.


SPARC-424 Initial work

Fleshed out the README.md and example Dockerfiles and Kubernetes
manifests.

I can't contribute much in terms of the configuration and deployment files. Just cleaned up some typos.

I really appreciated the editing, @aeyates. My eyes had started to gloss over after staring at the text for so long.