Intermittent Error "The connection does not support MultipleActiveResultSets."

Describe what is not working as expected.

I have an ASP.Net Core application that uses EF Core.
I use ASP.Net Identity and share the same DBContext for my app's entities.
I have set my connection string to an Azure SQL database to have MultipleActiveResultSet=True.
It works for a day or two, but eventually it fails with the error:
The connection does not support MultipleActiveResultSets.

If you are seeing an exception, include the full exceptions details (message and stack trace).
2017-08-31 00:00:37.095 +00:00 [Error] An exception occurred in the database while iterating the results of a query.

System.InvalidOperationException: The connection does not support MultipleActiveResultSets.
   at System.Data.SqlClient.SqlCommand.<>c.<ExecuteDbDataReaderAsync>b__107_0(Task`1 result)
   at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.EntityFrameworkCore.Storage.Internal.RelationalCommand.<ExecuteAsync>d__26.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.EntityFrameworkCore.Query.Internal.AsyncQueryingEnumerable.AsyncEnumerator.<BufferlessMoveNext>d__9.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.EntityFrameworkCore.Query.Internal.AsyncQueryingEnumerable.AsyncEnumerator.<MoveNext>d__8.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Microsoft.EntityFrameworkCore.Query.Internal.AsyncLinqOperatorProvider.SelectAsyncEnumerable`2.SelectAsyncEnumerator.<MoveNext>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.EntityFrameworkCore.Query.Internal.AsyncLinqOperatorProvider.SelectAsyncEnumerable`2.SelectAsyncEnumerator.<MoveNext>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.EntityFrameworkCore.Query.Internal.AsyncLinqOperatorProvider.ExceptionInterceptor`1.EnumeratorExceptionInterceptor.<MoveNext>d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.EntityFrameworkCore.EntityFrameworkQueryableExtensions.<ToListAsync>d__129`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Banico.Data.ItemRepository.<GetAllByTypeAndSections>d__8.MoveNext() in /Users/jasebanico/Banico/src/Banico.Data/Repositories/ItemRepository.cs:line 72
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Banico.Plugins.Directory.DirectoryController.<GetAllBySections>d__9.MoveNext() in /Users/jasebanico/Banico/src/Plugins/Banico.Plugins.Directory/DirectoryController.cs:line 52
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.AspNetCore.Mvc.Internal.ObjectMethodExecutor.<CastToObject>d__40`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeActionMethodAsync>d__27.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextActionFilterAsync>d__25.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ActionExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeNextResourceFilter>d__22.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Rethrow(ResourceExecutedContext context)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)
   at Microsoft.AspNetCore.Mvc.Internal.ControllerActionInvoker.<InvokeAsync>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Builder.RouterMiddleware.<Invoke>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware`1.<Invoke>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.<Invoke>d__6.MoveNext()

Steps to reproduce
Include a complete code listing (or project/solution) that we can run to reproduce the issue.
Partial code listings, or multiple fragments of code, will slow down our response or cause us to push the issue back to you to provide code to reproduce the issue.

I am not able to reproduce it consistently. I can provide the repository and controller code location. The complete solution is here in Github.

Startup:
services.AddDbContext<AppDbContext>(options => options.UseSqlServer(appDbContextConnectionString));

Repository:
https://github.com/jasebanico/banico/blob/master/src/Banico.Data/Repositories/ItemRepository.cs

Controller:
https://github.com/jasebanico/banico/blob/master/src/Plugins/Banico.Plugins.Directory/DirectoryController.cs

Further technical details
EF Core version: 1.1.1
Database Provider: 1.0.2
Operating system:
IDE: VS Code

@jasebanico The repositories are being registered as singletons in Startup.cs. This means that there is one shared DbContext instance even though the DbContext itself is registered as scoped. This can mean that the same context instance (and hence the same connection) can be accessed by multiple threads (due to multiple requests) at the same time. Since both DbContext and DbConnection/SqlConnection are not thread safe this is likely the root cause of the intermittent failures. The repositories should probably be registered as scoped.


[AVM Module Issue]: virtualNetworkSubnetId and GatewayTimeout error

Check for previous/existing GitHub issues

[X] I have checked for previous/existing GitHub issues

Issue Type?
I'm not sure
Module Name
avm/res/web/site
(Optional) Module Version
0.3.2
Description
We're employing the function app module, where the basic function app, along with the private endpoint, deploys successfully. However, we're now attempting VNET integration, for which we're configuring the 'virtualnetworksubnetid' parameter.
We've observed that the value must adhere to a specific format to correctly represent the subnet, and we've ensured its proper formatting. However, during deployment, we encounter the following error: 'The gateway did not receive a response from 'Microsoft.Web' within the specified time period.'
Has anyone else encountered this issue, or could it possibly indicate a bug?
(Optional) Correlation Id
30742872-6519-453b-8149-ef5fb71869bb

Hey @bgawale - thanks for submitting the issue. We can take a look for you to try a reproduce the issue to determine if its a bug. I will aim to triage next week but it is a short week for us in NZ. I'll keep the issue posted.

Thanks for the response @tsc-buddy . We were able to resolve it but only after explicitly adding a few settings, not sure which one of them fixed it but did not work unless these were added (was not hoping it since these are not even mandatory properties.) Sharing the working version for your reference, if it helps.
var vnet_res_id = '/subscriptions/${subscription().subscriptionId}/resourceGroups/${mod_vnet_gen0.outputs.resourceGroupName}/providers/Microsoft.Network/virtualNetworks/${rs_vnet_name}'

module mod_fnapp_mydata_0 'br/public:avm/res/web/site:0.3.2' = {
  name: 'mod_fnapp_mydata'
  params: {
    kind: 'functionapp'
    name: rs_fn_mydata_name
    serverFarmResourceId:mod_asp_mydata_0.outputs.resourceId
      managedIdentities: {
      systemAssigned: true
    }
    siteConfig: {
      numberOfWorkers: 1
      acrUseManagedIdentityCreds: false
      alwaysOn: true
      http20Enabled: false
      functionAppScaleLimit: 0
      minimumElasticInstanceCount: 0
      use32BitWorkerProcess: false
    }
    basicPublishingCredentialsPolicies: [
      { allow: true
        name: 'ftp'
      }
      {  allow: true
        name: 'scm'
      }
    ]
    httpsOnly: true
    privateEndpoints: [
      {
        privateDnsZoneResourceIds: [
          mod_dnszone_web_0.outputs.resourceId
        ]
        subnetResourceId: mod_vnet_gen_0.outputs.subnetResourceIds[0]
      }
    ]
   virtualNetworkSubnetId: '${vnet_res_id}/subnets/functionapp-subnet'
   vnetContentShareEnabled: true
   vnetImagePullEnabled: true
   vnetRouteAllEnabled: true
   scmSiteAlsoStopped: true
   publicNetworkAccess: 'Disabled'
   appSettingsKeyValuePairs: {
    FUNCTIONS_EXTENSION_VERSION: '~4'
    FUNCTIONS_WORKER_RUNTIME: 'dotnet'
   }
  }
}

Thanks for this @bgawale i will test it next week and if they turn out to be mandatory, we may look to add an additional sample for people to reference on the readme. Thanks again for raising this.


The port on the backend VM is mentioned incorrectly, I think.

The port on the backend VM is mentioned incorrectly in case there are more than 1 SQL Servers, I think. The Fronend port is 1434 but the backend port should still be 1433 in the pink Note section.
I would suggest the frontend ports to be 14331, 14332, and so on.. and the backend is still 1433 or the configured port for the db.

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

ID: 0ad13676-0e4b-6e1d-bd9c-e7b6e6698da9
Version Independent ID: 37f5f9b3-c78e-78ff-7d94-ea70c2958ed7
Content: Access on-premises SQL Server from Data Factory Managed VNet using Private Endpoint - Azure Data Factory
Content Source: articles/data-factory/tutorial-managed-virtual-network-on-premise-sql-server.md
Service: data-factory
GitHub Login: @lrtoyou1223
Microsoft Alias: lle

Thanks for the question! We are looking into this and will get back to you soon.

Hello Peeyush-Now
I am assuming that you are talking about the below note section.

As per the documentation here ,

If you look at the below command for SQL Sever 2 :
sudo ./ip_fwd.sh -i eth0 -f 1434 -a <FQDN/IP> -b 1433
The requests/packets received are being forwarded to the destination SQL Server of IP at Port 1433.

Consider a scenario where Azure Data Factory is being configured to collect data from 2 or more on premise SQL Servers, each of them running on the default port 1433. The load balancer knows by FQDN/IP which sql server to route to, but needs a different port for routing to the backend pool VMs. The backend VMs use the routing table port to then decide which FQDN to forward the request to. Have I undersood this right?
So may be your documentation is correct, and for clarity, it can
ADF request (sql server 1:1433) --> load balancer:443 --> backend vm<1.. n>:14331 -->sql server1:1433
ADF request (sql server 2:1433) --> load balancer:443--> backend vm<1.. n>:14332-->sql server2:1433
..
ADF request (sql server X:1433) --> load balancer:443--> backend vm<1.. n>:1433X-->sql serverX:1433
If you agree, please close the issue else let me know.

Yes, That's right.  The backend VM forwards the request to the respective SQL Server on port 1433 based on the routing table port of the VM.
We will close this out, but if you feel you need more information please just let us know.


(MODULES-1420) Add yaml_fact_cron_path_env and facts_package_ensure parameters

The yaml_fact_cron_path_env parameter can be used to override the value of PATH for the cron
and exec resources managing the yaml factsource.
The facts_package_ensure parameter can override the package_ensure value used when
defining Mcollective::Plugin[facter]

Hi @treydock sorry this has been overlooked for so long. In fact, I think we recently merged some PRs that dabble in that same context.
Would you check recent history and see whether this might now be obsolete? Belated thanks for the PR in any case!

@treydock from what i gather, this is being addressed in #190, #193, #218 … it would be really awesome if we just had one fix ;)

For me personally, this is obsoleted as I'm no longer using the facter source for mcollective.  The hosts where I had been using the facter fact source plugin are now just using YAML and have the cron refresh disabled in favor of calling the fact refresh script when they run puppet apply.

Alright, thanks for the feedback.
Still, I believe we do want this functionality. Will have to carefully look and see where we are right now.

Can you rebase if this is still needed?

Closing due to age, and apparently solutions in other PRs.


prettier-standard linting errors

Due to the project's title (Prettier and standard brought together! <3) I assumed we didn't need to install and run standard for its linting functionality. I did some testing and it seems like prettier-standard does not output any linting errors.
Are we supposed to run standard alongside prettier-standard?

It's duplicate of #17

Thanks for the link! I'm still not sure what would be the best way to also get Standard's linting functionality. Maybe some more clarification can be added to the readme file? It looks like I'm not the only one who misunderstood what prettier-standard actually does (and doesn't).

I thought it was pretty clear with "While standard is a linter, prettier-standard is a formatter"? #17 is not about misunderstanding but adding extra functionality

@sheerun prettier-standard seems deps eslint when I use --lint ?
package.json
{
    "scripts": {
        "prettier": "prettier-standard --lint"
    },
    "dependencies": {
        // no eslint
    },
    "devDependencies": {
        // no eslint yet
        "babel-eslint": "^10.0.3",
        "prettier-standard": "^16.3.0",
    },
}

npm run prettier
output:
✖ prettier-standard --lint found some errors. Please fix them and try committing again.
helpers/remix.js 560ms

/Users/xx/coding/helpers/remix.js
  0:0  error  Parsing error: Cannot find module 'eslint'
Require stack:
- /Users/xx/coding/node_modules/babel-eslint/lib/require-from-eslint.js
- /Users/xx/coding/node_modules/babel-eslint/lib/analyze-scope.js
- /Users/xx/coding/node_modules/babel-eslint/lib/parse-with-scope.js
- /Users/xx/coding/node_modules/babel-eslint/lib/index.js
- /Users/xx/coding/node_modules/prettier-standard/node_modules/eslint/lib/cli-engine/config-array-factory.js
- /Users/xx/coding/node_modules/prettier-standard/node_modules/eslint/lib/cli-engine/cascading-config-array-factory.js
- /Users/xx/coding/node_modules/prettier-standard/node_modules/eslint/lib/cli-engine/cli-engine.js
- /Users/xx/coding/node_modules/prettier-standard/node_modules/eslint/lib/cli-engine/index.js
- /Users/xx/coding/node_modules/prettier-standard/node_modules/eslint/lib/api.js
- /Users/xx/coding/node_modules/prettier-standard/src/index.js
- /Users/xx/coding/node_modules/prettier-standard/src/cli.js

✖ 1 problem (1 error, 0 warnings)


add compressed image messages

Addresses https://github.com/Kukanani/vision_msgs/issues/20

The messages also need to be added to the CMakeLists.txt . Otherwise looks good. :)

Not sure something can be done about it, but to me (non-native speaker) it sounds like the detections are compressed, not just the source image data.

As a native speaker I agree. The alternative is to roll it into the existing message, as the image is optional in any case? Then there's the issue of not knowing which image message to use. I don't have a strong opinion either way though.

Thanks for the PR!
I'd prefer multiple message types for clarity. As far as naming goes, I agree that CompressedDetection is slightly ambiguous. The only suggestion I have is something like Detection2DWithCompression, which is perhaps more explicit, but certainly more clunky. Instead of renaming the message, can you simply make a note in the header comments for the new message that the difference between this and the standard Detection2D is that the source image is compressed?
Also note #19, which I hope to merge tomorrow, would mean that we should include tracking information in this new message type as well.

I renamed the compression messages and added a comment in their headers about how they differ from the non-compression versions. Let me know if you feel the names are too clunky, otherwise I'll merge in a week or so.

Still missing the tracking fields.

Rebased and added tracking fields

Closing - we've removed the data sources entirely so this is no longer required

Closing - we've removed the data sources entirely so this is no longer required


Pull request diff has no text

Gogs Version: <IP_ADDRESS>1
When creating a pull request I don't see any text in the diff at the bottom of the page. The diff colouring appears correct however, were the text to be there.

Whereas the actual commit diff shows:

In my local gogs installation, the same problem happens after the pull request has been created and you view the Files Changed tab for the pull request. I've just tested this on https://try.gogs.io (which is slightly later version (<IP_ADDRESS>6) to my local install) and that shows the diff correctly after the pull request is created, but I can still reproduce the problem on https://try.gogs.io for the initial pull request create/Compare Changes.

Confirmed after local upgrade that <IP_ADDRESS>6 fixes this for the diff in Files Changed tab, but is still a problem in the initial pull request create (Compare Changes) page.

Duplicate of #2462 and fixed in #2480

ping @chrisbrookes

Appears to be same issue as #2462, assuming it uses same page/template (/.../compare/branch...owner:branch)? Agree, looks like it'll be fixed with #2480.

@chrisbrookes

looks like it'll be fixed with #2480

Have you tried? If it isn't working @andreynering has more stuff to fix :laughing:

I'm struggling to test if it's currently fixed in develop because I'm using the docker image, and it seems to be that develop == latest == Version: <IP_ADDRESS>6. Something not right with the docker builds?

@chrisbrookes
I tested it myself and the problem exists.
I already submited a PR with (another) fix: https://github.com/gogits/gogs/pull/2493

Ok, thanks!

This is claimed to be fixed by merging #2491


Remove the #[interrupt] macro

Thank you for your contribution!
We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:
Submission Checklist 📝

[x] I have updated existing examples or added new ones (if applicable).
[ ] My changes were added to the CHANGELOG.md in the proper section.

Extra:

[x] I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖
Description
See #1407
Testing
Builds fine

Fixes #1407

Suggestion for the release notes (migration guide)
<EMAIL_ADDRESS>Migration Guide
This release changes interrupt handler binding from link-time binding to runtime-binding. This increases flexibility a lot especially in regards to mixing async an non-async drivers but needs some changes in user code.
The most obvious thing is the removal of the #[interrupt] macro. It's replaced by the #[handler] macro which works in a different way.
Now you have to explicitly bind the interrupt handler. The supported peripheral drivers either take a new optional paramter to their constructor or the offer a set_interrupt_handler function.
Example
Before
static BUTTON: Mutex<RefCell<Option<gpio::Gpio9<Input<PullDown>>>>> =
    Mutex::new(RefCell::new(None));

#[entry]
fn main() -> ! {
    let peripherals = Peripherals::take();
    let system = peripherals.SYSTEM.split();
    let clocks = ClockControl::boot_defaults(system.clock_control).freeze();

    let io = IO::new(peripherals.GPIO, peripherals.IO_MUX);
    let mut button = io.pins.gpio9.into_pull_down_input();
    button.listen(Event::FallingEdge);

    critical_section::with(|cs| BUTTON.borrow_ref_mut(cs).replace(button));

    interrupt::enable(Interrupt::GPIO, Priority::Priority2).unwrap();

    led.set_high().unwrap();

    loop {
    }
}

#[ram]
#[interrupt]
fn GPIO() {
    esp_println::println!("GPIO Interrupt");

    critical_section::with(|cs| {
        BUTTON
            .borrow_ref_mut(cs)
            .as_mut()
            .unwrap()
            .clear_interrupt()
    });
}

Now
static BUTTON: Mutex<RefCell<Option<gpio::Gpio9<Input<PullDown>>>>> =
    Mutex::new(RefCell::new(None));

#[entry]
fn main() -> ! {
    let peripherals = Peripherals::take();
    let system = peripherals.SYSTEM.split();
    let clocks = ClockControl::boot_defaults(system.clock_control).freeze();

    let mut io = IO::new(peripherals.GPIO, peripherals.IO_MUX);
    io.set_interrupt_handler(handler);
    let mut button = io.pins.gpio9.into_pull_down_input();

    critical_section::with(|cs| {
        button.listen(Event::FallingEdge);
        BUTTON.borrow_ref_mut(cs).replace(button)
    });

    loop {
    }
}

#[handler]
#[ram]
fn handler() {
    esp_println::println!("GPIO Interrupt");

    critical_section::with(|cs| {
        BUTTON
            .borrow_ref_mut(cs)
            .as_mut()
            .unwrap()
            .clear_interrupt()
    });
}

You can see the interrupt is enabled automatically for you now.
All existing examples are adapted to the new mechanism. Have a look at them for peripheral specific differences.

#1410 was merged


cmd/golint: introduce auto fix option (--fix)

This patch introduces an option to fix pointed out warnings automatically.
This one provides such function partially; actually it has the only naming auto-correction.
~To be honest, I'm not confident about how to test this feature, this patch contains a simple shell-script based test as you can see. Could you please tell me if there is a good way?~
Update: I wrote a test case to check the behavior of auto-fix mode at 86ac9149668b2514f199ad5a0126a94c5176d0d8
It can fix like so:
https://github.com/golang/lint/blob/9ceeaa38f1710f96dd9f0dc840a44b4e0de0c390/testdata/names.go
=>
https://github.com/golang/lint/blob/9ceeaa38f1710f96dd9f0dc840a44b4e0de0c390/testdata/auto_fix/expected.go
Ref #214

Any plans to land this PR?


TTI polyfill head script

Is the TTI polyfill head script required? I was noticing that events weren't firing every page load. Once I added the head script from the TTI readme it seemed to be firing 100% of the time. If this is required should it be added to the docs somewhere?
This is the script I'm referring to from https://github.com/GoogleChromeLabs/tti-polyfill
<script>
!function(){if('PerformanceLongTaskTiming' in window){var g=window.__tti={e:[]};
g.o=new PerformanceObserver(function(l){g.e=g.e.concat(l.getEntries())});
g.o.observe({entryTypes:['longtask']})}}();
</script>

Oh Boy, it is interesting that I never noticed this bug! Thank you for pointing this out.
Can you please share with me more info on how big is your app (kb/mb), how you load the resources in your index.html and how you use Perfume. This information would be beneficial to me to understand better your case.
And I will also double test it, and see to introduce back the code inside Perfume.

@a-axton v1.0.0 is out 🔥 🚀 with your fix


fix concurrent_ruby gem install error

This hits all code out there that uses puppet as a gem. I'd much rather have them release an updated gem with a stricter dependency or compatibility with 1.2.0.

Puppet 6.29.0 and 7.22.0 got released which pin the concurrent-ruby version, so this change shouldn't be required anymore.


Knife solo fails with "ERROR: ArgumentError: wrong number of arguments (1 for 0)"

Trying to build a Cloudfoundry setup, but the inception server predictably fails to build in my environment (this reoccurs even after an inception delete):
∵ temujin9@takni:~/Projects/Bazaarvoice/project/DaaS ∴ inception deploy

Confirming: Using AWS/us-west-2

Preparing deployment settings

Using your git user.name (Nathaniel Eliot)
Acquiring a public IP address... <IP_ADDRESS>

Provision inception server

Reusing security group ssh
Booting m1.small inception server... i-b36435be
Confirming ssh access to server... done
Provisioning 16Gb persistent disk for inception server... i-b36435be

Prepare inception server

knife solo prepare<EMAIL_ADDRESS>-i /home/temujin9/.inception_server/ssh/inception -j '{"disk":{"mounted":true,"device":"/dev/xvdf"},"git":{"name":"Nathaniel Eliot","email":"temujin9@t9productions.com"},"user":{"username":"ubuntu"},"fog":{"aws_access_key_id":"REDACTED","aws_secret_access_key":"REDACTED"}}' -r 'bosh_inception'
WARNING: No knife configuration file found
Bootstrapping Chef...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 16519  100 16519    0     0  48230      0 --:--:-- --:--:-- --:--:-- 50057
Downloading Chef 11.14.6 for ubuntu...
downloading https://www.opscode.com/chef/metadata?v=11.14.6&prerelease=false&nightlies=false&p=ubuntu&pv=13.04&m=x86_64
  to file /tmp/install.sh.2064/metadata.txt
trying wget...
url     https://opscode-omnibus-packages.s3.amazonaws.com/ubuntu/13.04/x86_64/chef_11.14.6-1_amd64.deb
md5     8f6735d01eeeb37e979aa2443ecee8c8
sha256  a0a53055f77baafd8ad254a391557618c3af7367a2b69b703d2ef06de41699be
downloaded metadata file looks valid...
downloading https://opscode-omnibus-packages.s3.amazonaws.com/ubuntu/13.04/x86_64/chef_11.14.6-1_amd64.deb
  to file /tmp/install.sh.2064/chef_11.14.6-1_amd64.deb
trying wget...
Comparing checksum with sha256sum...
Installing Chef 11.14.6
installing with dpkg...
Selecting previously unselected package chef.
(Reading database ... 52215 files and directories currently installed.)
Unpacking chef (from .../chef_11.14.6-1_amd64.deb) ...
Setting up chef (11.14.6-1) ...
Thank you for installing Chef!
Generating node config 'nodes/ec2-50-112-52-174.us-west-2.compute.amazonaws.com.json'...
knife solo cook<EMAIL_ADDRESS>-i /home/temujin9/.inception_server/ssh/inception -j '{"disk":{"mounted":true,"device":"/dev/xvdf"},"git":{"name":"Nathaniel Eliot","email":"temujin9@t9productions.com"},"user":{"username":"ubuntu"},"fog":{"aws_access_key_id":"REDACTED","aws_secret_access_key":"REDACTED"}}' -r 'bosh_inception'
WARNING: No knife configuration file found
Running Chef on ec2-50-112-52-174.us-west-2.compute.amazonaws.com...
Checking Chef version...
Installing Berkshelf cookbooks to '/home/temujin9/.berkshelf/knife-solo/0c041c64b878b586438f82e0dd637de0f435861c'...
DEPRECATED: Your Berksfile contains a site location pointing to the Opscode Community Site (site :opscode). Site locations have been replaced by the source location. Change this to: 'source "https://supermarket.getchef.com"' to remove this warning. For more information visit https://github.com/berkshelf/berkshelf/wiki/deprecated-locations
ERROR: ArgumentError: wrong number of arguments (1 for 0)
/usr/lib/ruby/vendor_ruby/rake/file_utils.rb:53:in `block in create_shell_runner': Command failed with status (100): [knife solo cook<EMAIL_ADDRESS>(RuntimeError)
        from /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:45:in `call'
        from /usr/lib/ruby/vendor_ruby/rake/file_utils.rb:45:in `sh'
        from /var/lib/gems/1.9.1/gems/inception-server-0.3.0/lib/inception/inception_server_cookbook.rb:39:in `knife_solo'
        from /var/lib/gems/1.9.1/gems/inception-server-0.3.0/lib/inception/inception_server_cookbook.rb:26:in `block in converge'
        from /usr/lib/ruby/1.9.1/fileutils.rb:125:in `chdir'
        from /usr/lib/ruby/1.9.1/fileutils.rb:125:in `cd'
        from /var/lib/gems/1.9.1/gems/inception-server-0.3.0/lib/inception/inception_server_cookbook.rb:25:in `converge'
        from /var/lib/gems/1.9.1/gems/inception-server-0.3.0/lib/inception/cli.rb:143:in `converge_cookbooks'
        from /var/lib/gems/1.9.1/gems/inception-server-0.3.0/lib/inception/cli.rb:35:in `deploy'
        from /var/lib/gems/1.9.1/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
        from /var/lib/gems/1.9.1/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
        from /var/lib/gems/1.9.1/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
        from /var/lib/gems/1.9.1/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
        from /var/lib/gems/1.9.1/gems/inception-server-0.3.0/bin/inception:8:in `<top (required)>'
        from /usr/local/bin/inception:23:in `load'
        from /usr/local/bin/inception:23:in `<main>'

Retrying after this failure results in:
 ∵ temujin9@takni:~/Projects/Bazaarvoice/project/DaaS ∴ inception deploy

Confirming: Using AWS/us-west-2

Preparing deployment settings

Using your git user.name (Nathaniel Eliot)

Provision inception server

Reusing security group ssh
Confirming ssh access to server... /var/lib/gems/1.9.1/gems/fog-core-1.24.0/lib/fog/core/wait_for.rb:11:in `wait_for': The specified wait_for timeout (60 seconds) was exceeded (Fog::Errors::TimeoutError)
        from /var/lib/gems/1.9.1/gems/inception-server-0.3.0/lib/inception/inception_server.rb:271:in `attach_persistent_disk'
        from /var/lib/gems/1.9.1/gems/inception-server-0.3.0/lib/inception/inception_server.rb:67:in `create'
        from /var/lib/gems/1.9.1/gems/inception-server-0.3.0/lib/inception/cli.rb:119:in `perform_deploy'
        from /var/lib/gems/1.9.1/gems/inception-server-0.3.0/lib/inception/cli.rb:34:in `deploy'
        from /var/lib/gems/1.9.1/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
        from /var/lib/gems/1.9.1/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
        from /var/lib/gems/1.9.1/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
        from /var/lib/gems/1.9.1/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
        from /var/lib/gems/1.9.1/gems/inception-server-0.3.0/bin/inception:8:in `<top (required)>'
        from /usr/local/bin/inception:23:in `load'
        from /usr/local/bin/inception:23:in `<main>'

However, inception ssh works just fine, after the initial deploy failure.

in what file did you put these values? @temujin9

I tried it on mac os:
echo '
Host "ec2*.amazonaws.com"
  User ubuntu
  UserKnownHostsFile /dev/null
  StrictHostKeyChecking no' >> ~/.ssh/config

It didn't solve the issue however.

on ubuntu trusty32 this workaround seems to be working

I've tried it on ubuntu/trusty32 as well, no luck.

Unfortunately, this was months ago, and I've not touched this particular project since then. I can't provide any more help here than I already have. Sorry!

sure, no harm taken :)


Don't overwrite config on shutdown

changes in the config on velocity (3.1.1) are only possible while the server is offline. I would like to change the config while server is running, so the changes will apply on next restart

Hey, thanks for the report, we'll look into it (cc @arrayofc)

Hey, has been fixed in https://github.com/BadlionClient/BadlionClientModAPI/releases/tag/2.0.1 😃


Support instantiating TypeScript classes with new

These three commits add support for instantiating TypeScript classes with the new operator. See individual commit messages for details.
Note: I’m on a mostly-CLI environment (no IDE), and haven’t had to write JavaDoc in a while (yay!), so I might’ve gotten the syntax wrong. It would be great if you could check that.

Can one of the admins verify this patch? (see README)

@ceylonbuildbot OK to test

@chochos @quintesse @jvasileff any comments?

It remains my view that if we are going to do this for TypeScript anyway, then we should probably do it consistently everywhere.

I think we should have a way to differentiate backend specific keys and flags, at least in the Java code. Perhaps just a prefix, e.g. KEY_JS_NEW and isJsNew.
This makes code much easier to read and understand, even for just one backend. And more so for multiple backends (if we ever consolidate with similar changes I've made for Dart.)
This is something I've been thinking about for Dart, but I haven't adopted a convention yet.

@gavinking sure, but that’s going to be a lot more work, and in the meantime this allows me to continue working on the TypeScript loader.
@jvasileff good idea. (Only tangentially related, but if we’re going to introduce more backend-specific flags, we’ll probably reach the limit of the current 32-bit flags :) ) I can amend and force-push – but we should probably decide on a naming scheme. This sounds good to me:

Accessors: isJs*, setJs*
Flag: JS_*
Key: KEY_JS_*

Actually, KEY_JS_* makes no sense at all. The model-js file is already specific to the JS backend :D

Actually, KEY_JS_* makes no sense at all

I strongly disagree.

the typechecker specific metadata is of a much cleaner and different nature than backend specific metadata. Distinguishing between the two makes code much, much easier to read and understand, and
there's no reason for this file format to be JS specific. There have even been musings of using it for the JVM backend, as an optimization.

Note that I'm taking about the Java code. I'm guessing it's not worth the storage cost to prefix the actual keys.

Alright, I pushed new commits with prefixed names. (Also rebased on master.)

cool :+1:

Rebased again. Any chance on getting this merged? The constant rebasing is a bit inconvenient.

Thanks Enrique!


401: Validator that caused the failed validation: com.sap.cloud.security.token.validation.validators.XsuaaJwtSignatureValidator

We are migrating our apps from spring-xsuaa to spring-security by following the guides published here:
Spring Security guide: https://github.com/SAP/cloud-security-services-integration-library/tree/main/spring-security
Migration guide: https://github.com/SAP/cloud-security-services-integration-library/blob/main/spring-security/Migration_SpringXsuaaProjects.md
Feature branch: https://github.tools.sap/LBN/lbn-freightOrdersForSettlement/tree/Spring3Java17_V2/lbn-freightOrdersForSettlement-service
2024-02-09 09:16:57,691 WARN  [http-nio-8086-exec-7] - [com.sap.cloud.security.token.validation.ValidationResults] [] - Signature of Jwt Token is not valid: the identity provided by the JSON Web Token Key can not be trusted (Signature: nPvLTCww8MDwn5wFoCEwC264tMyMzbnsPO8o8AvOmzXbRxRj75AUkQpzI2a6wzZHgqpyvCmEnzfdQYZDRVYBylwqEX5sX0AaCB4vDPpWWliKlyeyCaIx401R00VuNyqegp_UWfImY4NJDVhKVCOPr2ZuAa8ZxGz1rKbizkEaIsEdxEFHNTdq7NTNUAxLh6tR_g5wDn_NNozeIvtB_BTX_P83sZABw3TD6h26pG52KnYgwzqsUUxH8ycSpkaC0MSKb0gSKKXNSmrGesGjNciaTNYy5to-C6r8j9KWsmr3xvYtlR0XvMLpiOMaMh0JrngoDu-PbrBW2pwEIWNquRyHWQ).
2024-02-09 09:16:57,691 DEBUG [http-nio-8086-exec-7] - [com.sap.cloud.security.token.validation.CombiningValidator] [] - Validator that caused the failed validation: com.sap.cloud.security.token.validation.validators.XsuaaJwtSignatureValidator
2024-02-09 09:16:57,691 DEBUG [http-nio-8086-exec-7] - [com.sap.cloud.security.token.validation.CombiningValidator] [] - Object of type com.sap.cloud.security.token.XsuaaToken that caused the failed validation:
Jwt header
    {"alg":"RS256","jku":"https://lbn-e2e-carrier01.authentication.sap.hana.ondemand.com/token_keys","kid":"key-id-1","typ":"JWT","jid": "LMXa0ZyqMstuE0fgC0toT0IPlPy9HyBvoLXc84CiTcs="}

===========
We got some lead, the issue was occurring due to the size of the JWT token.
JwtSignatureValidator => Base64.getUrlDecoder().decode(signature)
sun.security.jca.JCAUtil.RSAPadding => BadPaddingException was coming
Please let us know how to resolve this??

Hi, how did you get to this lead?
Did you see this error message in your logs?
I assume if Base64.getUrlDecoder().decode(signature) throws a BadPaddingException, this would be the case.
Did you try to validate the signature of the token in a different tool, e.g. https://jwt.io/?
How did you get this token? Is it a real XSUAA token issued when logging in?
Do you see this message when you enable debug logging for our library?

Closing this as Github Issue section is no longer maintained.


error message not present when there is syntax error

when there is a syntax error, not style (error/warning). The error message is not present at reporter output. for example:
jscs --reporter json test.js --no-colors
{"test.js":[{"line":11,"column":20}]}

which actually there is a syntax error:
SyntaxError: Unexpected token ILLEGAL

Is it an expect behavior or a bug?

I have the same problem, I'm using syntastic with jscs and it expects message from jscs...

It was actually fixed in https://github.com/jscs-dev/node-jscs/commit/b47f765546cfca93c0aa93a5e9c12d1d731d6e75
But it's only in 2.x release, so install via npm install jscs won't get that fix.
@xavierchow

@ruanyl thanks for reminding, I think the fix is in 3.0 branch, no sure when there'll be a release for it tho.


runtime(ruby): Update syntax, indent and ftplugin files

thanks, included as of da16a1b471aa717f58909cc6531cb6dbbff14d22 (I also squashed in @tpope s  #12994 )


Shared Global State

Hello, searched documentation but i did not find a way to share state globally, meaning between two or more van-elements. Sorta like in an island architecture. Now, when it comes to island architecture, astro we can use nanostores. I'm curious to know if there is a recommended way / sollution for van-element. I mean i could use custom events, maybe pubSub to subscribe to events with data and that would be the easiest possible way, but those would work if both van-elements are present.

Hi! Thank you for your interest in the project.

The most straight forward way to share state between components is simply to put the state in a global-scoped van.state. If you need more complex state, you can even use VanX.reactive to build a store. Things will work automatically because VanJS is awesome :)

Here is a simple example on CodePen: https://codepen.io/atmos4/pen/RNbozMV.

A more complex approach would be to use a context (think React Context), so that the state is only shared to a part of the DOM. This approach is slower in terms of performance and more complex to implement, and would make use of the WebComponent context specification.

I actually have some draft code for option 2. If you are interested I can polish it and make it into a small package. However I would always recommend option 1, as it is simpler, more performant and sufficient in most cases.
None of the information I gave here is available in the docs, so I will work on fixing that asap

I added shared state in the docs, under an "Advanced section". I feel like this is a topic that often deters people from using custom elements/web components so thank you for bringing it up.
Let me know if you would want me to publish a "Van Context" package too!
I am going to close the issue for now. Thank you for your feedback and interest!

Wow, thanks a lot. I appreciate it! 🥳 🎄 🎅


app doesn't show errror message when attempting to create impossible universal links

Every occurrence of
TODO: Display appropriate error to user
should be fixed (search the source code for it)
Situations: creating an order of higher value than 4,300Eth, creating orders with indices higher than 32768.
I noticed this in the pull request but decided to approve it anyway and put the issues aside.

Believe this was done a long time ago.


Check #691bug

From vNext_yarong_780
Added test file that fires setup and teardown failures

Hi @artemjackson, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla.microsoft.com.

TTYL, MSBOT;

@artemjackson, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

Please submit this as a PR to 780 and not to vNext so I can just review your changes.

Should be submitted to vNext_yarong_780. Closed.


Clarification: RemoteID and/or DroneID?

Hey,
does this project also spoof/broadcast DJI's DroneID data (Aeroscope detectable) or (FAA style) Remote ID only?
Source indicates opendroneid is used, yet I'm unsure if DJI's DroneID is using the same protocol?
A sample project claiming to spoof Aeroscope detectable DroneID data:
https://github.com/DJISDKUser/ESP8266_DJI_DroneID_Throwie
Kindly asking for clarification.

Hey,
does this project also spoof/broadcast DJI's DroneID data (Aeroscope detectable) or (FAA style) Remote ID only?
Source indicates opendroneid is used, yet I'm unsure if DJI's DroneID is using the same protocol?
A sample project claiming to spoof Aeroscope detectable DroneID data: https://github.com/DJISDKUser/ESP8266_DJI_DroneID_Throwie
Kindly asking for clarification.

It replicates RemoteID broadcasts only. RemoteID is similar to DJI's Drone ID but not the same transmission or protocol. Hope this helps!

Yep! Whatever @sethmnone mentioned is correct. You can probably modify the code to also broadcast DroneID data if you want, given the linked repo.

Anybody willing to implement DJI Drone ID?


Update README

I was in the same situation as #89.

Hi @fukayatsu thank you for your commit, could you please squash the commits?

sure :)


Make fed resolver always apply configured exception handler

Pull request checklist

[x] Please read our contributor guide
[x] Consider creating a discussion on the discussion forum first
[x] Make sure the PR doesn't introduce backward compatibility issues
[x] Make sure to have sufficient test cases

Pull Request type

[x] Bugfix

Changes in this PR
Issue #966
Ensures that a configured exception handler will be applied to exceptions that occurred within eg a Mono or CompleteableFuture execution.
The tests specifically for exception handling did not previously verify that the custom handler was called in all cases; added a check to verify it was called.
Had to make all of the tests in that suite provide a more fully configured DFE in order to get them to pass - there was an NPE in DefaultDataFetcherExceptionHandler when the ExecutionStepInfo wasn't present.
Alternatives considered
Considered trying to detect and special-case a not-fully configured DFE, but determined that the problem was the tests.
Considered not extracting causes from additional exception types, but after checking that CompletableFuture does wrap exceptions (and Mono does not), decided to add the extra extraction.

Thanks for the PR contribution!

tyvm. I see that the checks have passed - what's the cycle for when yall merge things?

We have a couple PRs coming up, so likely end of this week or early next week we'll do a release.

Thank you!


Azure ExecutionContext not registered in Spring Application Context

Contrary to what https://cloud.spring.io/spring-cloud-static/spring-cloud-function/3.0.0.M1/azure.html#_accessing_azure_executioncontext  states, the ExecutionContext is not registered into the spring application context. It can neither be retrieved via dependency injection into any bean or component (or the Function<>), nor is it registered under the bean name targetExecutionContext in the application context / bean factory.
Using version 3.1.4

FYI: I ended up registering the Execution Context into a InheritableThreadLocal with a WeakReference upon function start and removed it on end, and used @CustomLog from Lombok to call into a logger that reads the Execution Context and thus the target logger from there.
That was the only viable solution to get logging done in Azure Functions with Spring

Sorry, i just pushed and backported doc updates so should be fine from now one.
But basically the execution context available as Message header - https://github.com/spring-cloud/spring-cloud-function/blob/main/spring-cloud-function-samples/function-sample-azure/src/main/java/example/Config.java#L48

The whole thing goes a bit deeper anyway, as with Azure Functions the ExecutionContext is only valid for that single call. We solved it by saving it to a InheritingThreadLocal static variable in a central logging system, and redirecting all logs to that instance, if it is present.
Otherwise you end up dragging the ExecutionContext and the logger through the whole system.
It is a pitty this is not abstracted away by Azure, and a function can simply use a Sl4j2 logger.

I understand, but at hat was actually fixed a while back, but we forgot to update the docs. So the point if having ExecutionContext as Message Header implies that you'll have a new one or the most current one on every invocation.

I do undestand, but your example only works "okay" if you assume an Azure function's work is done in a couple of lines of code in a single class, in a single method, while often it is split out into multiple methods, components, services, etc. Each invocation of a service, each method call, will have the Message or ExecutionContext be passed around. It is super impractical.
That is why we chose to capture the ExecutionContext in a InheritingThreadLocal when the function is called, and use our own custom logger that wraps around it with lombok accross the whole application.


allow to set HTTP headers

allow to set headers officially on expressjs which powers the ghost application
Why?
In the world of microservices, it is best to set response headers right from the source(application)
will be great to be able to set HTTP headers right from running ghost container which is powered by expressjs so one can troubleshoot at the microservices layer.
How?
http://expressjs.com/en/4x/api.html#setHeaders

We provide a pretty stock installation of Ghost -- if Ghost itself allows this, our image should expose that behavior in the standard way.  I'd recommend checking the Ghost documentation for more information (and possibly joining their Slack channel via http://slack.ghost.org/ for additional help). :+1:


timedelta serialization->de-serialization precision error

Bug
For bugs/questions:

OS: Windows/Linux
Python version import sys; print(sys.version): 3.6.7
Pydantic version import pydantic; print(pydantic.VERSION): 0.23

Where possible please include a self contained code snippet describing your
bug, question, or where applicable feature request:
from pydantic import BaseModel
from datetime import timedelta
from typing import Optional

class Foo(BaseModel):
    name: str
    time_delta: Optional[timedelta]

Foo.parse_raw(Foo(name="Bar", time_delta=timedelta(seconds=0.767607)).json())

What is going on is the float value that represents the timedelta deserializes with some precision error and the regex (pydantic.datetime_parse.standard_duration_re) does not allow for float values that are longer than 6 digits.

I agree int and float should both be accepted by timedelta and interpreted as seconds.
PR welcome.
Better not to convert them to strings, but rather just pass them to timedelta(seconds=value).

After some further investigation, I was only able to reproduce the issue when using ujson as the json serializer (I was unable to repoduce it using the builtin json module).  Either way, there is still a possible issue if the BaseModel constructor is passed a high precision float value.
@samuelcolvin is there a reason why the standard_duration_re was implemented, but then on serialization the timedelta was serialized using timedelta.total_seconds()?
My thinking is to utilize the standard_duration_re for validation and to switch timedelta's json encoder to just output the strings representation of a timedelta (timedeltas.str output) as the standard_duration_re seems to parse the results just fine. A change like this will not break back comparability in-theory, as the validator will not change and it will handle float input still.

sorry for the delay in responding to this.
I don't really want to change the standard serialization for timedelta:

for me total seconds a as a float makes the most sense as a default
it would break lots of peoples code.

Most people aren't serializing pydantic models to re-load them into pydantic (if you want to do that you'd be better off using pickle), but to use in other systems/languages eg. databases or js - in both of these situations using str(delta) would break things for them a lot.

This issue doesn't seem to be relevant anymore. Closing the issue.


Problem running contextive

Hello team,
I installed Contextive and when trying to hover over a term in the definition file I get:
Request textDocument/hover failed.
VSCode: July 2023 (version 1.81)
Contextive: v1.9.3
macOS: 13.4 (22F66)
Output and sample definition.yml
https://gist.github.com/pdjota/3a41ba0e484babac0d60228979791823

Hi @pdjota, while I assume that the empty terms list is a temporary state, I have pushed v1.9.4 today that improves the resilience so that one context having an empty terms list doesn't break it for terms defined in other contexts.
Thanks again, and please feel free to raise another issue if you have any further problems!


Add Kintsugi and Kiln testnets

Target branch: bellatrix

Add Kintsugi and Kiln configs
Make it feasible on Metamask
Disable Fortmatic and Portis for now

TODOs:

[x] make deposit on kintsugi
[ ] test top-up
[x] test Kiln

note that beaconchain explorer doesn't support APIs before genesis. some beaconcha.in-API calls fail now

Merging this PR now to see the demo website. Post-merge feedback is still appreciated!

Hi @samajammin @wackerow
Could you help review this PR? Especially the security check of https://github.com/ethereum/staking-launchpad/blob/bellatrix/src/pages/ConnectWallet/Chains.ts?

Hey @hwwhww! I'm OOO for the rest of the week. Perhaps @wackerow can help take a look. Otherwise I'll check this out next week when I'm back.


SIGINT instead of SIGKILL on unix systems

Codecov Report

Merging #295 into master will decrease coverage by 0.15%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master     #295      +/-   ##
==========================================
- Coverage   74.28%   74.13%   -0.16%
==========================================
  Files           8        9       +1
  Lines         976      978       +2
==========================================
  Hits          725      725
- Misses        205      207       +2
  Partials       46       46

Flag
Coverage Δ

#unittests
74.13% <0%> (-0.16%)
:arrow_down:

Impacted Files
Coverage Δ

service/driver.go
0% <0%> (ø)
:arrow_up:

service/driver_unix.go
0% <0%> (ø)

Continue to review full report at Codecov.

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


OpenSearch client v1.0.2 release NPM request

Need NPM release for opensearch-js v1.0.2
Describe the solution you'd like
Use previous release template for v1.0.2 release

Any ETA on this @peterzhuamazon

@peternied since you are oncall for the week can you follow up with @ananzh and @kavilla thanks.

FYI - we are working this request offline, but will use this to track overall work.

v1.0.2 is released<EMAIL_ADDRESS>closing this issue. Thanks!


MRG: Add projection of EEG electrodes

This allows visualizing the EEG electrodes projected onto the scalp.
Also gets the machinery in place for #3700.
Ready for review/merge from my end.

CircleCI output:
https://2923-1301584-gh.circle-artifacts.com/0/home/ubuntu/mne-python/doc/_build/html/auto_examples/visualization/plot_eeg_on_scalp.html

Current coverage is 87.37% (diff: 68.81%)

Merging #3707 into master will decrease coverage by <.01%

@@             master      #3707   diff @@
==========================================
  Files           343        343
  Lines         60923      60957    +34
  Methods           0          0
  Messages          0          0
  Branches       9312       9325    +13
==========================================
+ Hits          53238      53262    +24
- Misses         4928       4933     +5
- Partials       2757       2762     +5

Powered by Codecov. Last update 930106e...e0b50c1

Thanks for the look @jaeilepp, comments addressed

the fact that projected sensors have the same red color makes it really had to see.
2 options:

use a different color for projected sensors
only allow one way for plotting. Eventually showing the two ways in the example?

thoughts?

I think it's nice to be able to see both. Are they all hard for you to see? For me they are hard to see in the case that they overlap, which is precisely when I don't need to see them both...
If you'd prefer I can change the colors to be more different, but they should be somewhat similar to differentiate them from, say, dig points, or any other type of points.
Another option would be to draw a line from the original to the spot on the scalp, but not sure how easy this is in Mayavi or how good it would look.

whatever works. It's just maybe in static view in web page that it's not
really visible :(

Can you try it locally? That way you could see if it's better interactively, and easily make changes to see if you like something better. Might be faster than iterating over GitHub comments

thanks @Eric89GXL


Failed generate rust code with proto-grpcio

sorry,my English isnt well,so I try to descript the problem I had
Describe the bug
After read the Readme, I can generate throuth the first way Manual Generation with command
protoc --rust_out=. --grpc_out=. --plugin=protoc-gen-grpc=which grpc_rust_plugin example.proto.
bug when I try to generate proto file by protoc-grpcio.cargo build fail
failed to execute command: Permission denied (os error 13).
and the trace show that it panic at
        if self.always_configure || !build.join("CMakeCache.txt").exists() {
            run(cmd.env("CMAKE_PREFIX_PATH", cmake_prefix_path), "cmake");
        } else {
            println!("CMake project was already configured. Skipping configuration step.");
        }

fn run(cmd: &mut Command, program: &str) {
    println!("running: {:?}", cmd);
    let status = match cmd.status() {
        Ok(status) => status,
        Err(ref e) if e.kind() == ErrorKind::NotFound => {
            fail(&format!("failed to execute command: {}\nis `{}` not installed?",
                          e, program));
        }
        Err(e) => fail(&format!("failed to execute command: {}", e)),
    };
    if !status.success() {
        fail(&format!("command did not execute successfully, got: {}", status));
    }
}

To Reproduce
Steps to reproduce the behavior:

clone the project protoc-grpcio
run the command cargo run --manifest-path example/Cargo.toml --bin server

Expected behavior
build fail and panic
thread 'main' panicked at ' failed to execute command: Permission denied (os error 13)
System information

Ubuntu18.04
libprotoc version 3.7.0
cmake version 3.12.2
rust 1.35-nightly
go 1.11.5
GNU ld (GNU Binutils) 2.32
gcc 7.3.0

Additional context

. - @mtp401

Could you please provide your example.proto file?

Could you please provide your example.proto file?

syntax = "proto3";

package example;

service Diner {
  rpc Eat(Order) returns (Check) {}
}

enum Item {
  SPAM = 0;
  EGGS = 1;
  HAM = 2;
}

message Order {
  repeated Item items = 1;
}

message Check {
  double total = 1;
}

It is the example proto of the project proto-grpcio . ice juju...

事实上让我很困惑的是,一开始用的是命令行,是能够生成对应的文件的.后来下了protoc-grpcio后,他的demo无法运行-. - .后面还试了试grpc-rust.也是可以自动生成相关文件的.
下面这是完整的报错信息
running: "/home/lynss/softwares/envs/cmake" "/home/lynss/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/grpcio-sys-0.4.2/grpc" "-DgRPC_INSTALL=false" "-DgRPC_BUILD_CSHARP_EXT=false" "-DgRPC_BUILD_CODEGEN=false" "-DCMAKE_INSTALL_PREFIX=/home/lynss/projects/rust/protoc-grpcio/example/target/debug/build/grpcio-sys-47cecebc29b1342c/out" "-DCMAKE_C_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_C_COMPILER=/usr/bin/cc" "-DCMAKE_CXX_FLAGS= -ffunction-sections -fdata-sections -fPIC -m64" "-DCMAKE_CXX_COMPILER=/usr/bin/c++" "-DCMAKE_BUILD_TYPE=Debug"

build script failed, must exit now', /home/lynss/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/cmake-0.1.35/src/lib.rs:778:5
stack backtrace:
   0: std::sys::unix::backtrace::tracing::imp::unwind_backtrace
             at src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:39
   1: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:71
   2: std::panicking::default_hook::{{closure}}
             at src/libstd/sys_common/backtrace.rs:59
             at src/libstd/panicking.rs:197
   3: std::panicking::default_hook
             at src/libstd/panicking.rs:211
   4: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:474
   5: std::panicking::continue_panic_fmt
             at src/libstd/panicking.rs:381
   6: std::panicking::begin_panic_fmt
             at src/libstd/panicking.rs:336
   7: cmake::fail
             at /home/lynss/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/cmake-0.1.35/src/lib.rs:778
   8: cmake::run
             at /home/lynss/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/cmake-0.1.35/src/lib.rs:756
   9: cmake::Config::build
             at /home/lynss/.cargo/registry/src/mirrors.ustc.edu.cn-61ef6e0cd06fb9b8/cmake-0.1.35/src/lib.rs:611
  10: build_script_build::build_grpc
             at ./build.rs:98
  11: build_script_build::main
             at ./build.rs:187
  12: std::rt::lang_start::{{closure}}
             at /rustc/33ef0bad21d6bb646c7c3ab0dbf381ca96c324bf/src/libstd/rt.rs:64
  13: std::panicking::try::do_call
             at src/libstd/rt.rs:49
             at src/libstd/panicking.rs:293
  14: __rust_maybe_catch_panic
             at src/libpanic_unwind/lib.rs:87
  15: std::rt::lang_start_internal
             at src/libstd/panicking.rs:272
             at src/libstd/panic.rs:388
             at src/libstd/rt.rs:48
  16: std::rt::lang_start
             at /rustc/33ef0bad21d6bb646c7c3ab0dbf381ca96c324bf/src/libstd/rt.rs:64
  17: main
  18: __libc_start_main
  19: _start

It is the example proto of the project proto-grpcio

I can't find this file. Which version of proto-grpcio are you using?

I cannot reproduce the error under this environment:

Ubuntu 18.04
GNU ld (GNU Binutils for Ubuntu) 2.30
gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
libprotoc 3.1.0 (yes, I guess this is the cause, could you please try downgrading your protoc version?)
cmake version 3.10.2

When I run the example I get:
~/git-repos/protoc-grpcio|master λ> cargo run --manifest-path example/Cargo.toml --bin server
   Compiling grpcio-sys v0.4.2
   Compiling example v0.0.1 (/home/yqz5714/git-repos/protoc-grpcio/example)
   Compiling grpcio v0.4.3
    Finished dev [unoptimized + debuginfo] target(s) in 8.44s
     Running `example/target/debug/server`
listening on <IP_ADDRESS>:43353
Press ENTER to exit...

When I run the example I get:
~/git-repos/protoc-grpcio|master λ> cargo run --manifest-path example/Cargo.toml --bin server
   Compiling grpcio-sys v0.4.2
   Compiling example v0.0.1 (/home/QAQ/git-repos/protoc-grpcio/example)
   Compiling grpcio v0.4.3
    Finished dev [unoptimized + debuginfo] target(s) in 8.44s
     Running `example/target/debug/server`
listening on <IP_ADDRESS>:43353
Press ENTER to exit...

好的,我试试换个版本的proto=. =

When I run the example I get:
~/git-repos/protoc-grpcio|master λ> cargo run --manifest-path example/Cargo.toml --bin server
   Compiling grpcio-sys v0.4.2
   Compiling example v0.0.1 (/home/QAQ/git-repos/protoc-grpcio/example)
   Compiling grpcio v0.4.3
    Finished dev [unoptimized + debuginfo] target(s) in 8.44s
     Running `example/target/debug/server`
listening on <IP_ADDRESS>:43353
Press ENTER to exit...

When I run the example I get:
~/git-repos/protoc-grpcio|master λ> cargo run --manifest-path example/Cargo.toml --bin server
   Compiling grpcio-sys v0.4.2
   Compiling example v0.0.1 (/home/QAQ/git-repos/protoc-grpcio/example)
   Compiling grpcio v0.4.3
    Finished dev [unoptimized + debuginfo] target(s) in 8.44s
     Running `example/target/debug/server`
listening on <IP_ADDRESS>:43353
Press ENTER to exit...

I cannot reproduce the error under this environment:

Ubuntu 18.04
GNU ld (GNU Binutils for Ubuntu) 2.30
gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
libprotoc 3.1.0 (yes, I guess this is the cause, could you please try downgrading your protoc version?)
cmake version 3.10.2

it dosent work yet.. now libprotoc version is 3.1.0

bysides , the module build failed is ' failed to run custom build command for grpcio-sys v0.4.2
'.and when i google it , i found a problem likes mine ,and grpc-rs is mentioned. https://github.com/pantsbuild/pants/issues/4984

The panicking code is actually:
https://github.com/pingcap/grpc-rs/blob/f1216de3605e14d47067f8e1a2a74878240b7339/grpc-sys/build.rs#L98
which is a cmake error.

@Lynss Could you please provide your full log of cargo clean && cargo build? And please do enable verbose output, thanks.

it seems my fault... cause when I had to try to use the tower-grpc,the same error happened with 'permission denied'.

Clion's teminal had been set into oh_my_zsh...


I can't to custome json decode error handler.

when I call request.get_json(), I found that request.json has been set.
If I post a http request with content-type:application/json with empty body or incomplete json string, this will abort in 400,
I want to custom my json decode error handler, what should I do?

This is not a support forum. Please ask questions on stackoverflow or similar places.


Bug: Problem when trying to select text in text field when editing node text

A "bug" occured when I was trying to select text from the input when editing node text, it triggered the drag.

Fixed.


[synapse] Migrate to Samples Workflow V2

This issue is part of the Azure SDK for JavaScript sample quality effort.
The new sample tool (dev-tool samples publish) has been made available to all package maintainers, and we would like to migrate all packages to the new system.
What do I need to do?
This issue is to track migrating all packages within the synapse folder to the new layout. However, it does not appear that there are any sample packages in this folder. If this is expected, this issue can be closed.
There are a few things to do to resolve this issue:

Attempt to follow the steps in the migration guide for each of the packages. Any problems can be reported to me, and I'll be available to assist in getting everything moved over.
Look at https://github.com/Azure/azure-sdk-for-js/issues/14180, the main tracking issue for this work, and see if your package has any problems listed in the issue description. We would like to fix all of these issues that we are able to fix as we are migrating samples to the new system.

If for any reason you think that this issue should not apply to this service/package, please get in touch with me so that we can discuss the package's needs.
Thank you!

Synapse doesnt have samples. Closing the issue


BufNMF: add example where basesMode = 2 and actMode = 2

Add an example to the example code that does decomposition with actMode set to 2 and also basesMode set to 2. This will require pre-computed bases and activations to be supplied.
This is an added functionality since the example code was initially made.

Doesn't necessarily need something pre computed. You could do a decomposition, then process the results in some way before re-synthesis, e.g. smoothing the activations.

yes - I think that I'll do that in the learn ticket. so only the vocoder is missing from the help

Smoothing activations is a good one.

that was my plan :) with assymetric smoothing, like gerard and i experimented with 4 years ago. it should be fun, but deffo advanced so I plan to put that in learn, as per https://github.com/flucoma/learn-website/issues/324


Bitcoin repeating in message

You have received a Bitcoin gift from Anant. Click on the link and follow the steps to receive bitcoin in your Bitcoin Tribe bitcoin wallet

can't test because gift creation fails


Consider adding support for combined I/O like write-(poll)-read with a single completion

Hi,
I was playing around with io_uring, trying to use it in Wine to implement more efficient internal communication, and I think it could be useful if io_uring implemented some sort of combined I/O, returning a single CQE for a group of IOSQE_IO_LINK-ed operations (for instance, as it is how I'm currently combining the operations together).
The use case I have is a simple server, with multiple clients, communicating through pipes. The server processes requests one at a time, writes its reply and immediately queues the read for the next one. Using IOSQE_IO_LINK I can already link the write and read operations together, making sure it only starts reading for the next request on a pipe after finishing writing the reply, and it is already more efficient that queue-ing the read when the write CQE is received.
However, even doing this, the write SQE still creates a CQE, and pointlessly waking up the server just to acknowledge them. I think it could be even more efficient if this combined I/O created a single CQE only when the linked read completes.
This use case is pretty simple but I'm sure it could also be useful to have such feature for more complex linked operations.
Cheers,

Ha I just found IOSQE_CQE_SKIP_SUCCESS which looks exactly like what I need. Going to try it.

About particularly write-(poll)-read, if the purpose of the poll is to POLLIN before read, it's not needed since some version where io_uring got IORING_FEAT_FAST_POLL. It will be polled internally if needed.
But yeah, IOSQE_CQE_SKIP_SUCCESS, queued for not yet released 5.17. Just to note if you use it, your app should not use IOSQE_DRAIN.

Thanks, I guess I'll have to wait a bit then but it's nice to see that it's going to be supported. I don't think I've got any use for IOSQE_IO_DRAIN anyway.
I figured already that the poll wasn't needed, it was the pattern when using epoll for instance, I've also tried adding IOSQE_ASYNC on the read sqes, but I'm not sure if it made any difference either.


Desks missing description

Desks missing description what this is for.

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

ID: 7af332a3-efc1-49aa-24c2-64b5031a2420
Version Independent ID: f47bc209-aa9e-f337-1cfa-b8a727a9f780
Content: Set-Place (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Set-Place.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@Kazzan, empty parameter descriptions are a known commodity. Availability vs. functionality are two different things.
Are you being directed to use that parameter from other content, or are you just pointing out that the description is empty.

Hi @chrisda, got it. There are even parameters for Microsoft Places (in Private Preview currently) documented, so just wondering why not the Desks parameter. If it is a similar story and even not described by Product Group or just missing the description for production one. In overall, the blog post about Set-Place in Exchange blog is old now, and missing the description of most of parameters, so some real examples (like from Room Finder) will be nice addition to these (or at least link to same in EAC). Just a thought.

@Kazzan Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.


RouteAlreadyExists AWS 'up' error

I have not touched any of the route tables on an existing stack. But when I try to deploy a redis instance within the stack the update fails, because of
aws:ec2:RouteTable (axiom-private-subnet-3-routetable-cloud-development):
    error: 1 error occurred:
    	* updating urn:pulumi:axiom-cloud::Development::aws:ec2/routeTable:RouteTable::axiom-private-subnet-3-routetable-cloud-development: 1 error occurred:
    	* error creating route: RouteAlreadyExists: The route identified by <IP_ADDRESS>/0 already exists.
    	status code: 400, request id: 6c24f1c6-ca0d-48aa-a340-54a5e99a2cb5

This happened before previously,  when I did an update that was even adding anything to the stack.

Could you please provide more diff information along with the code that creates your route tables/network to help debug?

Hi,
As there has been no further details added here, I am going to close this out as a stale issue. If this is still a problem, please let us know and we can try and help
Paul


Fixed typo in docstring

@joe2far have you signed the CLA?

@jsternberg - I have signed the CLA

Thanks!


Reenable Interop4.5 sample

As part of migrations to VS 2017, I temporarily disabled building the app which targets 4.5.1. Once we can build this sample again, we need to add it back to the solution and start building it again. https://github.com/aspnet/Identity/blob/a5ca720ff1bb361bdc4e4cb92652be26eae4b1ee/samples/Interop4.5/Interop4.5.csproj.aspnet45

This was a point in time sample, the official interop sample will be done somewhere else (most likely docs)

So should we remove the sample from this repo altogether?

Its already gone :)


No changes reaction on grid_settings

Hello!
When y trying change column or gutter or more settings on grid_settings, it doesn't react to it in any way, but when i change grid-columns or max width - it's work! What do I do not so?
$column: 211px !default;
$gutter: 20px !default;
$grid-columns: 6;
$max-width: em(1366);
Thank you!

I have the same issue (node-neat package: 1.7.1beta), and I can't figure out why. I have tried to change the default values directly at the source, but nothing happens.

@DryamDryam @ksesong What’s the structure of your project (Sass imports, etc) and where are you defining these grid settings?

Here is the content of the main stylesheet:
// == Importing modules
@import 'bourbon';
@import 'neat';

// == Helpers
@import 'helpers/_normalize';
@import 'helpers/_reset';
@import 'helpers/_variables';  // <== Grid settings are set here
@import 'helpers/_mixins';
@import 'helpers/_media-queries';

// == Layout, components...

With grid settings as such:
$column: em(40);
$gutter: em(20);
$grid-columns: 14;
$max-width: em(1100);
$visual-grid: true;

This is especially strange as both the $grid-columns and $max-width variables are operational. My libsass version is 3.1.0, which shouldn't be an issue with this version.

@ksesong As described in Neat’s readme, you need to import your grid setting changes before neat. So, something like this:
@import 'bourbon';
@import 'grid-settings';
@import 'neat';


Throw Errors instead of Strings

It seems that this addon is currently throwing plain strings instead of Error instances. I've noticed this because using it with mocha warned me like this:
Error: the string "You're trying to create a sensor, but no factory for this type was found" was thrown, throw an Error :)
    at Runner.fail (assets/test-support.js:6477:11)
    at assets/test-support.js:6751:18
    at done (assets/test-support.js:6205:5)
    at Test.Runnable.run (assets/test-support.js:6228:7)
    at Runner.runTest (assets/test-support.js:6661:10)
    at assets/test-support.js:6744:12
    at next (assets/test-support.js:6586:14)
    at assets/test-support.js:6596:7
    at next (assets/test-support.js:6531:23)
    at assets/test-support.js:6558:7

Is there a reason for throwing strings over proper errors?

note that this was with the current stable version (v0.1.11) and from the source code it looks like the master branch is throwing proper errors now.


[Bug]: unable to import images using an account with whitespace in its home directory path

Describe the bug
Hello,
When I try to run Distrod on a User which has a white space in its home directory (e.g. C:\Users\My Account), the import of the downloaded archive breaks.
[Distrod][ERROR] Failed to register the distribution.
Caused by:
Failed: cmd.exe /C wsl --import Distrod %LocalAppData%\Distrod "C:\Users\MYACCO~1\AppData\Local\Temp\.tmpJmcTKu\install.tar.gz"
Steps to reproduce

Create a new local user with a name separated by a whitespace, it is mandatory the user has its home directory with the same name format (C:\Users\My Account)
Run distrod and choose to download a container image from linuxcontainers.org
Choose Rocky Linux (21)
Choose version 8
Wait for the download and then the error should appear during the import

Expected behavior
Successful import of the downloaded distro image into WSL
Windows version
Windows 11 21H2 (Build SO 22000.856)
Linux kernel version
No distro installed
Distro
Rocky Linux 8
How did you install that distro?
Installed by Distrod wizard
Logs
C:\Users\My Account\Desktop\distrod_wsl_launcher-x86_64>distrod_wsl_launcher.exe

        ██████╗ ██╗███████╗████████╗██████╗  ██████╗ ██████╗
        ██╔══██╗██║██╔════╝╚══██╔══╝██╔══██╗██╔═══██╗██╔══██╗
        ██║  ██║██║███████╗   ██║   ██████╔╝██║   ██║██║  ██║
        ██║  ██║██║╚════██║   ██║   ██╔══██╗██║   ██║██║  ██║
        ██████╔╝██║███████║   ██║   ██║  ██║╚██████╔╝██████╔╝
        ╚═════╝ ╚═╝╚══════╝   ╚═╝   ╚═╝  ╚═╝ ╚═════╝ ╚═════╝
=================================================================================
Thanks for trying Distrod! Choose your distribution to install.
You can install a local .tar.xz, or download an image from linuxcontainers.org.

* linuxcontainers.org is a vendor-neutral project that offers distro images for
  containers, which is not related to Distrod. LXC/LXD is one of its projects.
  BTW, you can run Systemd with distrod, so you can try LXC/LXD with distrod!
=================================================================================
[1] Use a local tar.xz file
[2] Download an image from linuxcontainers.org
[Distrod] Choose the way to get a distro image from the list above.
[Distrod] Type the name or the index of your choice.
[Default: Download an image from linuxcontainers.org]: 2
[Distrod] Fetching from linuxcontainers.org...
[1] almalinux
[2] alpine
[3] alt
[4] amazonlinux
[5] apertis
[6] archlinux
[7] busybox
[8] centos
[9] debian
[10] devuan
[11] fedora
[12] funtoo
[13] gentoo
[14] kali
[15] mint
[16] opensuse
[17] openwrt
[18] oracle
[19] plamo
[20] pld
[21] rockylinux
[22] springdalelinux
[23] ubuntu
[24] voidlinux
[Distrod] Choose a linuxcontainers.org image from the list above.
[Distrod] Type the name or the index of your choice.
[Default: ubuntu]: 21
[Distrod] Fetching from linuxcontainers.org...
[1] 8
[2] 9
[Distrod] Choose a version from the list above.
[Distrod] Type the name or the index of your choice.
[Default: 9]: 8
[Distrod] Fetching from linuxcontainers.org...
[Distrod] Downloading 'https://images.linuxcontainers.org/images/rockylinux/8/amd64/default/20220914_02:35/rootfs.tar.xz'...
  [00:00:15] [##################################################] 107.93MiB/107.93MiB (7.17MiB/s, 0s)
[Distrod] Download done.
[Distrod] Unpacking and merging the given rootfs to the distrod rootfs. This may take a while...
[Distrod] Now Windows is installing the new distribution. This may take a while...
Copyright (c) Microsoft Corporation. All rights reserved.

Usage: wsl.exe [Argument] [Options...] [CommandLine]
...
_<output of wsl --help>_
...

[Distrod][ERROR] Failed to register the distribution.

Caused by:
    Failed: cmd.exe /C wsl --import Distrod %LocalAppData%\Distrod "C:\\Users\\MYACCO~1\\AppData\\Local\\Temp\\.tmpJmcTKu\\install.tar.gz"

additional comment
No response

Same issue. Had to work around it by installing the distro manually and then enabling it with option 2 to get systemd started up


[stable/grafana-agent] Support existing ConfigMap.

Signed-off-by: Aaron Layfield<EMAIL_ADDRESS>What this PR does / why we need it:
This enabled an option for using an existing ConfigMap
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #164

Special notes for your reviewer:
@davosian does this fit your requirements?
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

Merging.


Add linux kernel lts2021

cactus finished building and testing your changes
It was requested for merge by "Badrappan, Jeevaka"<EMAIL_ADDRESS>so we merge it. Thanks for your contribution.
more details, logs, and binaries: /absp/builders/celadon-mergerequest/builds/3112


Integrate warnings and rank zero utilities

🚀 Feature
Integrate https://github.com/Lightning-AI/lightning/blob/master/src/pytorch_lightning/utilities/rank_zero.py and https://github.com/Lightning-AI/lightning/blob/master/src/pytorch_lightning/utilities/warnings.py

These rank_zero utilities shouldn't go here. They rely on PL/Lite specific mechanics to set the rank and and parse it from env variables. It would not be very practical to have them in a different library.

The only specific thing is the rank extraction, so we can just make that an argument to the utilities here.


Exception occured when running inverted_pendulum_mpc_control.py

$ python3 inverted_pendulum_mpc_control.py

Exception has occurred: exceptions.TypeError
Variable name 31 must be a string.
  File "/home/***/code/mpc_inv/inverted_pendulum_mpc_control.py", line 67, in mpc_control
  File "/home/***/code/mpc_inv/inverted_pendulum_mpc_control.py", line 43, in main
  File "/home/***/code/mpc_inv/inverted_pendulum_mpc_control.py", line 188, in <module>

I had the same problem with you and I fixed it out. The code has some errors: you have to revise the line 64-65 to this:
x = cvxpy.Variable((nx, T + 1))
u = cvxpy.Variable((nu, T))

@HTLife @WatsonZhouAnda Hi. Is it possible for you to make a PR to solve this issue?

I fixed it.


WebpackError at /en/

What I'm trying to achieve
Trying to build-assets
Steps to reproduce the problem

What I expected to happen
…
Screenshots

WebpackError at /en/
ModuleBuildError in
Module build failed (from ./node_modules/mini-css-extract-plugin/dist/loader.js):
ModuleBuildError: Module build failed (from ./node_modules/sass-loader/lib/loader.js):
Error: Cannot find module 'node-sass'
at Function.Module._resolveFilename (internal/modules/cjs/loader.js:582:15)
at Function.Module._load (internal/modules/cjs/loader.js:508:25)
at Module.require (internal/modules/cjs/loader.js:637:17)
at require (/home/b12/work/saleor/node_modules/v8-compile-cache/v8-compile-cache.js:159:20)
at Object.sassLoader (/home/b12/work/saleor/node_modules/sass-loader/lib/loader.js:46:72)
at runLoaders (/home/b12/work/saleor/node_modules/webpack/lib/NormalModule.js:301:20)
at /home/b12/work/saleor/node_modules/loader-runner/lib/LoaderRunner.js:364:11
at /home/b12/work/saleor/node_modules/loader-runner/lib/LoaderRunner.js:230:18
at runSyncOrAsync (/home/b12/work/saleor/node_modules/loader-runner/lib/LoaderRunner.js:143:3)
at iterateNormalLoaders (/home/b12/work/saleor/node_modules/loader-runner/lib/LoaderRunner.js:229:2)
at Array. (/home/b12/work/saleor/node_modules/loader-runner/lib/LoaderRunner.js:202:4)
at Storage.finished (/home/b12/work/saleor/node_modules/webpack/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:43:16)
at provider (/home/b12/work/saleor/node_modules/webpack/node_modules/enhanced-resolve/lib/CachedInputFileSystem.js:79:9)
at /home/b12/work/saleor/node_modules/graceful-fs/graceful-fs.js:78:16
at FSReqWrap.readFileAfterClose [as oncomplete] (internal/fs/read_file_context.js:53:3)
System information
Operating system: Ubuntu 18.04
Browser: Chrome

Hi, can you provide the steps to reproduce your issue?
Also, did you install the dependencies? Try running npm i as node-sass should have been installed from there.

Hi, can you provide the steps to reproduce your issue?
Also, did you install the dependencies? Try running npm i as node-sass should have been installed from there.

yes i checked there are some issues with node-sass package which not get installed in a normal way so there is a way to install it sudo npm install --save-dev  --unsafe-perm node-sass

it's resolved you can close this issue. @NyanKiyoshi


TractableConsumerType does not have all default parameters needed to solve()

Related to #844
Trying to write this automated simple automated test of basic solve and simulate functionality for TractableConsumerType:
https://gist.github.com/sbenthall/771121ec30afeaefdf24a9b7ac109997
This test fails on the solve() step with the following error:
        # Define some useful constants from model primitives
>       self.PermGroFacCmp = self.PermGroFac / (
            1.0 - self.UnempPrb
        )  # "uncertainty compensated" wage growth factor
E       AttributeError: 'TractableConsumerType' object has no attribute 'PermGroFac'

TractableBufferStockModel.py:362: AttributeError

The problem seems to be that there is no value of PermGroFac passed through to the constructor upon initialization by default.

There is no startup dictionary for TractableConsumerType available.


Shelly TRV (thermostat over valve) - no change in valve position when opening window

Discussed in https://github.com/jmcollin78/versatile_thermostat/discussions/340

Originally posted by nurunet January 14, 2024
Hi, I have bought a Shelly TRV because it was recommended here for use with VT. I set it up as a Thermostat over Valve. I also created an automation to push the temperature value of an external sensor to the thermostat.
Heating seems to work well, I just have some oscillation above the set heat point - I guess I still have to tweak the TPI settings.
However, I realized I didn't hear the valve move when opening the window. I checked, and - as expected - the Versatile Thermostat UI card shows the open window with little to no delay. The detail page of the VT entity in Home Assistant also shows the valve position to be 0%.
The details of the Shelly TRV entity however show the valve to be still open (at x%), and so does the web UI of the Shelly TRV itself.
Confusingly, the valve then normally moves to 0% when I close the window again - at least for a while.
Is this behavior known? Did I misconfigure something? Should I open an issue?

Looks like I'm running version 5.2.1.
My VTherm attributes are the following:
hvac_modes: heat, off
min_temp: 7
max_temp: 23
target_temp_step: 0.1
preset_modes: none, frost, eco, comfort, boost
current_temperature: 19
temperature: 18
hvac_action: idle
preset_mode: eco
is_on: true
hvac_mode: heat
type: null
is_controlled_by_central_mode: true
last_central_mode: null
frost_temp: 5
eco_temp: 18
boost_temp: 21
comfort_temp: 19
frost_away_temp: 5
eco_away_temp: 18
boost_away_temp: 18
comfort_away_temp: 18
power_temp: null
target_temperature_step: 0.1
ext_current_temperature: 1.9
ac_mode: false
current_power: null
current_power_max: null
saved_preset_mode: eco
saved_target_temp: 19
saved_hvac_mode: heat
window_state: off
motion_state: null
overpowering_state: null
presence_state: on
window_auto_state: off
window_bypass_state: false
security_delay_min: 60
security_min_on_percent: 0.5
security_default_on_percent: 0.1
last_temperature_datetime: 2024-01-14T22:26:47.799397+01:00
last_ext_temperature_datetime: 2024-01-14T21:34:59.615481+01:00
security_state: false
minimal_activation_delay_sec: 10
device_power: 1
mean_cycle_power: 0
total_energy: 0
last_update_datetime: 2024-01-14T22:33:22.809760+01:00
timezone: Europe/Berlin
window_sensor_entity_id: binary_sensor.bathroom_window_contact
window_delay_sec: 1
window_auto_enabled: false
window_auto_open_threshold: null
window_auto_close_threshold: null
window_auto_max_duration: null
motion_sensor_entity_id: null
presence_sensor_entity_id: binary_sensor.anyone_home
power_sensor_entity_id: null
max_power_sensor_entity_id: null
temperature_unit: °C
is_device_active: false
ema_temp: 19.1
valve_open_percent: 0
is_over_valve: true
underlying_valve_0: number.bathroom_shelly_trv_valve_position
underlying_valve_1: null
underlying_valve_2: null
underlying_valve_3: null
on_percent: 0
on_time_sec: 0
off_time_sec: 300
cycle_min: 5
function: tpi
tpi_coef_int: 0.5
tpi_coef_ext: 0.01
friendly_name: Bathroom Versatile Thermostat
supported_features: 17

This was earlier today.
I had opened the window, and VTherm showed that correctly:

But, at the same time, the valve remained open at 15%:

I'll try to provide logs tomorrow.

Try to reproduce in my test env (I have no valve in my house):
before opening:

After opening the window:

The thermostat turns off. The valve percent goes to 10 (which is the lower limit in my test env, else it will be 0).
The thermostat valve open percent is 0 (but I send the minimum value which is 10) :

I close the window:

The thermostat turns on, the thermostat valve wants 100% and the real valve is programmed to 90% (which is the max possible for this test valve).
For me all is working as expected.
Try to find logs, there should be an explanation.

Oh, the second try I do and I've got the issue:

That is not normal to have 90% with the window open and thermostat turned off.

Hello, the fix have been pushed into the release https://github.com/jmcollin78/versatile_thermostat/releases/tag/5.3.3.beta2
This is beta because there is the central boiler new feature in it. But you can install if you want and not to wait for the official release.
I don't know if it is relevant for you but can also participate to the test of the central boiler feature. See: https://github.com/jmcollin78/versatile_thermostat/discussions/339

Hi, and thank you. It is awesome how much time and effort you put into this project - and how responsive you are.
I'll see tonight if I can install the beta.
Until then, I am still wondering why (at least sometimes) the valve position does go to 0%... upon closing the window again. Do you have any idea?

Until then, I am still wondering why (at least sometimes) the valve position does go to 0%... upon closing the window again. Do you have any idea?

Yes it was badly coded. I have recoded this part and add some unit tests.

https://github.com/jmcollin78/versatile_thermostat/releases/tag/5.3.3

I confirm, 5.3.3 seems to have fixed the issue. Merci beaucoup !


Problem handling response in a 'string'

Hi,
Here's an example of a 'raw' response I get from a .NET WebAPI :
"[
   {
       \"Title\": Item title
       \"Lead\": Item lead
   }
   { item },
   { item 2 }
   { ... }
]"

As you can see, it is wrapped in a string. If I use a regular $http get, the response gets deserialized using the JSON parser.
If I do the same using Restangular, I get an error saying Response for getList SHOULD be an array and not an object or something else
Here's an example call I use (using decoupled service) :
News.getList({ param: $scope.param }).then(function (data) {
    console.log('success');
}, function (response) {
    console.log('error');
});

How can I do this using Restangular? Isn't it supposed to pass through $http?

The way you've made the getList call seems correct, but can you post a screenshot of the request and request body? It might not be deserializing the array correctly, but as Restangular uses $http under the hood, I'm not sure why the deserialization isn't taking place.


Adds SecretService Demo with some fixes.

Adds SecretService Demo with some fixes  to SercretService.

Secret service credential is now persisted -- see comments toward end of #1346 page.
Convenience method IsSecretExistsForKey() is added to SecretHelper.cs
Nuget package as Template10.Services.SecretService v1.0.2 already live.

Want to change to Template10.Services.Secrets and include SecretService but also include CrytoService in the same namespace. Take a look at what we did with Template10.Services.Serialization if you want to know what I mean.

Oh! somehow missed this message. Will have a look at this.


JS / TS crashed

Type: Bug
while updating dynamic styling to normal styling inside  tag it crashed
VS Code version: Code - Insiders 1.90.0-insider (5f78b58b57b7cf84d28d801fed6bb4a48f908601, 2024-05-09T05:49:43.696Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

System Info

Item
Value

CPUs
11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 2304)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: enabled_ondirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_graphite: disabled_offvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: enabled

Load (avg)
undefined

Memory (System)
15.71GB (5.49GB free)

Process Argv
--crash-reporter-id 1bd23bf2-7f56-4d16-87fc-3b7411cce352

Screen Reader
no

VM
40%

Item
Value

Remote
WSL: Ubuntu-20.04

OS
Linux x64 <IP_ADDRESS>-microsoft-standard-WSL2

CPUs
11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 x 2304)

Memory (System)
3.83GB (0.89GB free)

VM
0%

Extensions (21)

Extension
Author (truncated)
Version

es7-react-js-snippets
dsz
4.4.3

auto-close-tag
for
0.5.15

auto-rename-tag
for
0.1.10

remotehub
Git
0.62.0

remote-containers
ms-
0.365.0

remote-ssh
ms-
0.112.2024050815

remote-ssh-edit
ms-
0.86.0

remote-wsl
ms-
0.88.2

azure-repos
ms-
0.38.0

remote-explorer
ms-
0.4.3

remote-repositories
ms-
0.40.0

remote-server
ms-
1.5.1

vscode-github-actions
git
0.26.2

rest-client
hum
0.25.1

mongodb-vscode
mon
1.6.0

vscode-docker
ms-
1.29.1

cmake-tools
ms-
1.17.17

cpptools
ms-
1.20.5

cpptools-extension-pack
ms-
1.3.0

postman-for-vscode
Pos
1.0.1

cmake
twx
0.0.17

(3 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
tftest:31042121
vscod805:30301674
vsaa593cf:30376535
py29gd2263:31024238
c4g48928:30535728
vscrpc:30624061
a9j8j154:30646983
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30926734
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
h48ei257:31000450
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
cppperfnew:30980852
pythonait:30973460
showvideot:31016890
chatpanelt:31014475
0ee40948:31013168
a69g1124:31018687
dvdeprecation:31040973
pythonprt:31036556
dwnewjupytercf:31039676

Please try collecting the TS Server log from the crashed instance:

Set "typescript.tsserver.log": "verbose"

Restart VS Code and reproduce the problem

Open the TypeScript section of the output panel

At the very top, find the first line that prints to path to the semantic error log file. It should look something like:
[Info  - 19:54:59.247] <semantic> Log file: /Users/matb/Library/Application Support/Code - Insiders/logs/20200213T104930/exthost55/vscode.typescript-language-features/tsserver-log-ZT2zau/tsserver.log

That file contains the typescript logs.

Look through that log file for the first error or stack trace you see. If you can share the log, I can also take a look to see if anything stands out

⚠Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!