Implement ES6 object literal identifier reference, method definition, remove dup check

[x] Remove duplicate key check
[x] Add identifier reference property shorthand
[x] Add method definition shorthand
[x] Fix method definition shorthand .prototype, constructability, and .name visibility
[x] Rewrite parts of object literal parsing to reduce duplication and improve structure
[x] Resolve FIXMEs
[x] Make ES6 shorthands conditional to DUK_USE_ES6 for now (no separate config option)
[x] Testcase for duplicate key handling (side effects, overwriting behavior etc)
[x] Testcase for identifier reference shorthand
[x] Testcase for method definition shorthand (cover function .name, name binding)
[x] Testcase for object literal shadowed by a non-writable and non-configurable ancestor
[x] Testcase for computed name in a method definition shorthand
[x] Testcase coverage for string and number in method definition shorthand
[x] Testcase fixes for removal of duplicate key check
[x] Cover "this" binding for getter/setter and method shorthand
[x] Releases entry

@fatcerberus I'll experiment with implementing the method definition shorthand here. That's not yet implemented, but key duplicate check and identifier reference shorthand (in a very hacky way) is implemented. I'll probably rewrite parts of the object literal parsing function: it contains unnecessary duplication and should be possible to simplify a bit now.

Thanks, you didn't have to go to all this trouble but I appreciate it :)

No problem, with these changes ES6 object literal changes should be close to complete. It also reduces footprint (at least at present) because the complicated duplicate key logic can be eliminated. The duplicate key logic in ES5 is a bit complicated because it needs to reject duplicates, but allow a setter and a getter to be paired in separate steps.

The identifier reference shorthand is a bit strange, I actually had to read the testcase to understand it and even then it took a few seconds to sink in what was happening.

I find it a bit difficult to read (though perhaps that's just because I'm not used to it). I guess it could be useful in e.g. this idiom:
var host = 'foo.bar.com'
var port = 8080;
var timeout = typeof timeout === 'number' ? timeout : 60;
net.connect({ host, port, timeout });

@svaarala Let me know when this is stable for testing (no rush), the current branch is causing segfaults for me.

I accidentally deleted a critical line in a rebase which caused all tests to fail. But that's now fixed and repushed. It's not necessarily fully stable now but should work enough to do simple testing. Maybe you pulled that broken version?
The main area of work is to write a proper implementation of the compiler parts. I wanted to create an initial hacky version quickly so that I could add the test coverage etc first.

Reworked the object literal parsing structure a bit. The two level loop structure is now a single level and shared helpers reduce code footprint (and reduce repetition) a bit.

The reworked structure which includes the new syntax is about 100 bytes smaller than previous, which is nice :)

In that case I'll help out with testing :)

@fatcerberus Let me know what happens if you have time to try this out.  The method property syntax is not yet fully correct; the methods have a name binding, .prototype, and they're constructable (they should have none of these).

So to be clear - it'd be good to smoke test this. But detailed testing doesn't yet make much sense because some functionality is still incomplete. It won't be difficult to finish, it's mainly about some annoying plumbing/flags that need to be carried around the compiler.

Interesting, according to MDN computed keys work as method names:
https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Functions/Method_definitions
V8 agrees:
D:\src\duktape\ms>node
> var key = "foo";
undefined
> var obj = { [key]() { console.log("called!"); } }
undefined
> obj
{ foo: [Function: foo] }
> obj.foo()
called!
undefined
>

I mean this:
> obj = { foo() { console.log(typeof foo); } };
{ foo: [Function: foo] }
> obj.foo();
undefined

Re: that key example, that is supported by ES6:

The MethodDefinition case is covered in http://www.ecma-international.org/ecma-262/6.0/#sec-method-definitions
The syntax for it uses PropertyName production for the name slot
PropertyName is defined in http://www.ecma-international.org/ecma-262/6.0/#sec-object-initializer
The definition is LiteralPropertyName or ComputedPropertyName

This isn't implemented in the pull and I probably won't add it here because the name is dynamic and the compiler doesn't handle such cases now.

Added a (failing, known issue) testcase for the computed name in method definition case.

@svaarala I tested this out by changing a few function properties to methods in my game code, seemed to work okay.  I haven't tested the identifier shorthand yet, I'm sure I can find something that will benefit from it though.

Well here's a use case for computed method name:
$ nodejs
> obj = { [Symbol.for('aiee')] (a,b) { console.log(a,b); } };
{}
> obj[Symbol.for('aiee')](2,3)
2 3

That's actually something that would be useful in practice.

Ok, I think I now have the necessary flag plumbing done so this should be functionally complete. I also reworked the code to use a few more helpers. I'll read through the diff before merging but let's see what the tests think.

There are a few test coverage items also still to fix before merging. RELEASES entry also had a typo (fixed but unpushed).

Final footprint tuning: made the ES6 object literals conditional to DUK_USE_ES6 (didn't want to add a specific define for it... maybe later) because they're not needed in ES5-ish low memory targets.

I assume the duplicate property check is removed even in the ES5-ish build?

Right, with the ES5-ish approach it makes no sense to include the check.

Effect on x86 minsize is around -350 bytes which is great :)

Had a bug where number and string wasn't accepted for method definition; now fixed:
duk> var obj = { 1(a,b) { print(a,b); } }; obj['1']('foo', 'bar');
foo bar
= undefined
duk> var obj = { "mystring"(a,b) { print(a,b); } }; obj.mystring('foo', 'bar');
foo bar
= undefined

@svaarala Thanks again for the work on this, this will come in handy. :)

That's good to hear :) This was a nice win-win because the footprint is smaller (also RAM because the duplicate key map isn't needed) and functionality is improved. There's probably a few easy kilobytes in the compiler code waiting to be optimized ;)

Found a bug :-(  It looks like Duktape is mixing up accessors with plain properties in some cases.
	var obj = {
		getMusicFilename: function() {},
		load: function() {},
		fadeIn: function() {},
		fadeOut: function() {},
		update: function() {},
		musicPath: "~/music/",
		play: function() {},
		playSound: function() {},
		forceFinish: function() {},
		setMaxMusicVolume: function() {},
		setMaxSoundVolume: function() {},
		setVolume: function() {},
		stop: function() {},
		save: function() {},
		get done() {},
		get volume() {},
		get svolume() {},
		get mute() {},
		set mute(value) {}
	}
	obj.setMaxSoundVolume();

Result: TypeError: undefined not callable.
What the object looks like to SSJ Blue:

Thanks, I think I can reproduce this. Seems odd how that could happen so I'm sure the cause will be equally interesting :-)

An assert is triggered:
*** FATAL ERROR: assertion failed: comp_ctx->curr_func.is_setget == ((flags & DUK__FUNC_FLAG_GETSET) != 0) (duk_js_compiler.c:7434)

I should be able to fix this with the repro case - thanks!

What's interesting to me is that a data property was interpreted as an accessor before any getter/setter is even encountered.

@svaarala Let me know what you find out, I'm interested in what caused this bug too. ;)

The core issue is seen in this bytecode snippet:
00032 080201b5   MPUTOBJ    r1, r2, 8
00033 00100a02   LDCONST    r10, c16
00034 000d039c   CLOSURE    r3, 13
00035 000201b8   INITGET    r1, r2

A previous run of plain key/value pairs is finished with an MPUTOBJ when a getter is encountered. The getter is loaded with an INITGET opcode. However, the LDCONST for the getter name (c16 here) is loaded to r10 instead of r2 because of a bug in temp reg management.
This should be easy to fix - interesting that it wasn't caught by anything else.

What's interesting to me is that a data property was interpreted as an accessor before any getter/setter is even encountered.

That's caused by the incorrect tempreg number in the bytecode snippet above. The INITGET opcode will be using the right target value (the getter function) but a key left over in r2 from a previous MPUTOBJ. So at first setMaxSoundVolume() is initialized correctly, but it gets overwritten by the getter because of the incorrect key from r2. The leftover key is loaded by:
00024 000c0202   LDCONST    r2, c12

And:
; c12 "setMaxSoundVolume"

So mystery solved :)

Fix is in #1193.

Thanks, that explains why done didn't make it into the object: its getter got assigned to setMaxSoundVolume instead.

@svaarala Thanks for implementing this so quickly, I'm really loving the method shorthand :-)

You're quite welcome. I'm looking forward to the identifier shorthand and destructuring which will allow stuff like:
```js
function connect({ host, port }) {
    // ...
}

var host = 'localhost';
connect({ host, port: 8080 });

which is great for named parameter handling.


CLI for power users

Advantages:

Integration with scripts and other other complex tools such as crontab
Use minimal resources instead of acting as a daemon + GUI
Easier user testing of core features with CLI
Fail-safe in the event of GUI failure (e.g. due to Qt)

Describe the solution you'd like
Ideally, the CLI can be run statelessly with runtime parameters / environment variables / input files. Depending on the current architecture, it might be trivial to adapt existing interfaces to any of your favorite libraries here https://go.dev/solutions/clis
Additional context
This feature would be similar to fluminurs

if anyone’s still interested in a cli solution, i’ve made a canvas cli https://github.com/aidanaden/canvas-sync
it can be installed with brew (mac/linux/wsl) and scoop (windows)
cronjob support will be added soon!


Unable to set page-specific javascript block in forms

Please see the commit in this branch: https://github.com/vraravam/contact_demo/tree/page-specific-javascript-not-rendering
In the 'Groups' resource, for the form object, and using the script block, I am unable to get the script to be rendered.

try this
  form something do
    inputs do
      # ...
    end
    javascript do
      """
      alert('test');
      """
    end
  end

@smpallen99 - thanks, that works!


WidgetsBinding.instance?.addObserver(this); Null pointer exception

Hello,
It seems that supabase package is not supported by having null pointer operator.
Flow:
just installed supabase package in new flutter project start failing regarding this error:
/opt/homebrew/Caskroom/flutter/3.0.4/flutter/.pub-cache/hosted/pub.dartlang.org/supabase_flutter-0.3.3/lib/src/supabase_auth_required_state.dart:43:20: Warning: Operand of null-aware operation '?.' has type 'WidgetsBinding' which excludes null.
- 'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('/opt/homebrew/Caskroom/flutter/3.0.4/flutter/packages/flutter/lib/src/widgets/binding.dart').
package:flutter/…/widgets/binding.dart:1
    WidgetsBinding.instance?.addObserver(this);
                   ^
/opt/homebrew/Caskroom/flutter/3.0.4/flutter/.pub-cache/hosted/pub.dartlang.org/supabase_flutter-0.3.3/lib/src/supabase_auth_required_state.dart:49:20: Warning: Operand of null-aware operation '?.' has type 'WidgetsBinding' which excludes null.
- 'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('/opt/homebrew/Caskroom/flutter/3.0.4/flutter/packages/flutter/lib/src/widgets/binding.dart').
package:flutter/…/widgets/binding.dart:1
    WidgetsBinding.instance?.removeObserver(this);

Flutter SDK: 3.0.5
Supabase version: ^0.3.3
Dart version: 2.17.6
It needs to be updated to remove null pointer operators.

Thanks for opening this issue @musti-91 !
If you read it carefully, the message you are getting is just a warning, but is not anything that prevents the app from launching. The ? is left there intentionally to support Flutter 2.X versions, which requires them.
I would like to close this issue as we have a duplicate one here https://github.com/supabase-community/supabase-flutter/issues/138

I actually it's not. it's an error. I cannot run the app only after using the Supabase.initialize.
the same is happening in the boilerplate
https://github.com/supabase-community/supabase-flutter

@musti-91
Having an extra ? is not an error, and that ? is necessary to support Flutter 2.X versions where WidgetsBinding.instance is a type WidgetsBinding?.
I only see warning, but no error within the message you provided.
It would be great if you could open a new issue with some explanations on how your app fails to launch!

Launching lib/main.dart on iPhone 13 in debug mode...
lib/main.dart:1
Xcode build done.                                            7.4s
Failed to build iOS app
Error output from Xcode build:
↳
    2022-08-15 13:00:17.302 xcodebuild[81643:3628055] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionSentinelHostApplications for extension Xcode.DebuggerFoundation.AppExtensionHosts.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
    2022-08-15 13:00:17.302 xcodebuild[81643:3628055] Requested but did not find extension point with identifier Xcode.IDEKit.ExtensionPointIdentifierToBundleIdentifier for extension Xcode.DebuggerFoundation.AppExtensionToBundleIdentifierMap.watchOS of plug-in com.apple.dt.IDEWatchSupportCore
    ** BUILD FAILED **
Xcode's output:
↳
    Writing result bundle at path:
    	/var/folders/j1/r4jqdj0d1tv9gwy7qgfxz7q80000gn/T/flutter_tools.QZJ93i/flutter_ios_build_temp_dirzKtd06/temporary_xcresult_bundle
/opt/homebrew/Caskroom/flutter/3.0.4/flutter/.pub-cache/hosted/pub.dartlang.org/supabase_flutter-0.3.3/lib/src/supabase_auth_required_state.dart:43:20: Warning: Operand of null-aware operation '?.' has type 'WidgetsBinding' which excludes null.
- 'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('/opt/homebrew/Caskroom/flutter/3.0.4/flutter/packages/flutter/lib/src/widgets/binding.dart').
package:flutter/…/widgets/binding.dart:1
        WidgetsBinding.instance?.addObserver(this);
                       ^
/opt/homebrew/Caskroom/flutter/3.0.4/flutter/.pub-cache/hosted/pub.dartlang.org/supabase_flutter-0.3.3/lib/src/supabase_auth_required_state.dart:49:20: Warning: Operand of null-aware operation '?.' has type 'WidgetsBinding' which excludes null.
- 'WidgetsBinding' is from 'package:flutter/src/widgets/binding.dart' ('/opt/homebrew/Caskroom/flutter/3.0.4/flutter/packages/flutter/lib/src/widgets/binding.dart').
package:flutter/…/widgets/binding.dart:1
        WidgetsBinding.instance?.removeObserver(this);
                       ^
/opt/homebrew/Caskroom/flutter/3.0.4/flutter/.pub-cache/hosted/pub.dartlang.org/supabase_flutter-0.3.3/lib/src/supabase_auth_state.dart:32:5: Error: The method 'onReceivedAuthDeeplink' isn't defined for the class 'SupabaseAuthState<T>'.
- 'SupabaseAuthState' is from 'package:supabase_flutter/src/supabase_auth_state.dart' ('/opt/homebrew/Caskroom/flutter/3.0.4/flutter/.pub-cache/hosted/pub.dartlang.org/supabase_flutter-0.3.3/lib/src/supabase_auth_state.dart').
package:supabase_flutter/src/supabase_auth_state.dart:1
    Try correcting the name to the name of an existing method, or defining a method named 'onReceivedAuthDeeplink'.
        onReceivedAuthDeeplink(uri);
        ^^^^^^^^^^^^^^^^^^^^^^
    Failed to package /Users/alroomi/Developer/youtube/supabase_auth.
    Command PhaseScriptExecution failed with a nonzero exit code
    note: Using new build system
    note: Planning
    note: Build preparation complete
    note: Building targets in dependency order
    Result bundle written to path:
    	/var/folders/j1/r4jqdj0d1tv9gwy7qgfxz7q80000gn/T/flutter_tools.QZJ93i/flutter_ios_build_temp_dirzKtd06/temporary_xcresult_bundle
Could not build the application for the simulator.
Error launching application on iPhone 13.
Exited

I don't mind opening another issue but if you could help here would be great to resolve the issue. the full logs mentioned above.
It's indeed not the issue of optional binding But it seems something to do with
onReceivedAuthDeeplink(uri);
Hope that can helps!!!

commenting this line helps launching the app.
32  // onReceivedAuthDeeplink(uri); // supabase_auth_state.dart

can you try it on the latest version?


[Bug] Workflow and Activity Metrics seem lossy

What are you really trying to do?

We are trying to leverage the Temporal core metrics to build out monitors and dashboards.
Describe the bug

We've noticed that a few metrics are reporting less frequently than they should be. Specific metrics where we've noticed this: temporal_activity_execution_failed (Slack) and temporal_workflow_completed. We've found that metrics incremented from Workflow and Activity interceptors (TS SDK) are showing us roughly expected numbers, but the temporal_ metrics are vastly underreporting them.

Here are screenshots of graphs that subtract interceptor-based metrics from temporal-based ones. Notice how far below 0 the results are.
Activity
temporal_activity_execution_failed

Workflow
temporal_workflow_failed

temporal_workflow_completed

Minimal Reproduction
See Draft PR

Environment/Versions

Temporal Version: TS SDK: 1.4.2, but we experienced the same thing on 1.0.1.

Additional context

Thanks for the detailed info. I'll look into this and see if maybe there's some sampling going on by default that shouldn't be.
It'd help me to know:
What is your export configuration - where are you exporting to, what protocol, are there middlemen, etc?

What is your export configuration - where are you exporting to, what protocol, are there middlemen, etc?

Theoretically we should be exporting to an OTel collector on grpc, which then forwards metrics to our DD Agent (also on grpc). I say theoretically because the docs from OTel were not great at the time we set this up, and there aren't a lot of examples to go off of, but given that we've been seeing metrics come through at all, we assumed that was working fine.
Would it be helpful to share our OTel config?

Yes it would. I believe the collector may do some sampling, but hopefully not by default. Feel free to DM it to me on slack if you don't want to post it here.

DM-ed!

For any observers:
The otel collector config in use had sampling options enabled, which I suspect is the reason. Once Rupali gets a chance to verify the behavior without those options, we'll proceed.

@rupalivohra Did you get a chance to try this out?

Closing this due to staleness. Please open again if you verify it's not b/c of collector settings.


  Move into the new mono repo.  Apply the new config standards.

Added support-notifications via #428 and #455


staging to main

feat: Make service_id a text column

:tada: This PR is included in version 1.6.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


#[derive(Copy, Clone)] on BufferlessDefinition and BufferlessVertices to allow cloning unfinished graphics pipeline builders

[x] Added an entry to CHANGELOG_VULKANO.md or CHANGELOG_VK_SYS.md if knowledge of this change could be valuable to users
[x] Ran cargo fmt on the changes

The title pretty much explains this small PR. This is useful whenever someone needs to define a lot of render passes with similar options but different shaders and vertex types.

@Arc-blroth Thank you for the improvement! Can you fix merging conflicts, please?

@Arc-blroth Sorry for disturbing. Are there any updates? I would like to proceed with merging, but the fix is blocked.

@Eliah-Lakhin Sorry for taking so long to fix merge conflicts 😓 Should be resolved now!

@Arc-blroth Merged. Thanks!


Can't connect to a SQL Server database with a named instance

Bug description
At work, I presented Prisma to my manager, and he liked it, so we want to use it in our next project.
Sometimes we use MySQL, but for this project we are using SQL Server (probably Express).
The problem is trying to connect with a named instance (which is probably going to be a requirement for the project).
At work, we have Windows 10 machines, and this example is from home with a Windows 11 machine. The same error occurs.
So I have 2 servers running:

MSSQL Server
SQL Express

Some picture of my setup:

TCP/IP is enabled for both.
Here I tried connecting using the 'sqlcmd' and it works for both connections.

Here are connection strings I have tried and they didn't work:
// also for every string I also tried using \\ instead of just \  inbetween the HOST and INSTANCE

// this would be the ideal form to have working
DATABASE_URL="sqlserver://DESKTOP-F3USMA8\SQLEXPRESS;database=prisma;integratedSecurity=true;trustServerCertificate=true;"

DATABASE_URL="sqlserver://DESKTOP-F3USMA8\MSSQLSERVER;database=prisma;integratedSecurity=true;trustServerCertificate=true;"

DATABASE_URL="sqlserver://DESKTOP-F3USMA8\SQLEXPRESS:2584;database=prisma;integratedSecurity=true;trustServerCertificate=true;"

DATABASE_URL="sqlserver://localhost\SQLEXPRESS:2584;database=prisma;integratedSecurity=true;trustServerCertificate=true;"

Here are connection strings that worked:
// the ports and instances are in the pictures above

// connects to the SQL Express instance
DATABASE_URL="sqlserver://localhost:2584;database=prisma;integratedSecurity=true;trustServerCertificate=true;"

// connects to the SQL Server instance
DATABASE_URL="sqlserver://localhost:2584;database=prisma;integratedSecurity=true;trustServerCertificate=true;"

// connects to the SQL Server instance
DATABASE_URL="sqlserver://DESKTOP-F3USMA8;database=prisma;integratedSecurity=true;trustServerCertificate=true;"

From this, I can see that the named instance connection string are not working.
I could probably test it on my laptop too, with a fresh installation of windows.
How to reproduce
Using
 npx prisma db push

creates this error:
Error creating a database connection.

Expected behavior
Prisma establishes connection to the SQL Server DB with a named instance.
Prisma information
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "sqlserver"
  url      = env("DATABASE_URL")
}

model Post {
  id        Int      @id @default(autoincrement())
  createdAt DateTime @default(now())
  updatedAt DateTime @updatedAt
  title     String   @db.VarChar(255)
}

Environment & setup

OS: Windows 11/10
Database: SQL Server  (Developer, Express)
Node.js version: 18.7.0

Prisma Version
prisma                  : 4.2.1
@prisma/client          : 4.2.1
Current platform        : windows
Query Engine (Node-API) : libquery-engine 2920a97877e12e055c1333079b8d19cee7f33826 (at<EMAIL_ADDRESS>
Migration Engine        : migration-engine-cli 2920a97877e12e055c1333079b8d19cee7f33826 (at<EMAIL_ADDRESS>
Introspection Engine    : introspection-core 2920a97877e12e055c1333079b8d19cee7f33826 (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt 2920a97877e12e055c1333079b8d19cee7f33826 (at<EMAIL_ADDRESS>Default Engines Hash    : 2920a97877e12e055c1333079b8d19cee7f33826
Studio                  : 0.469.0

Glad to have found this... same issue for me.  So, is it just named instances that have this problem? (I haven't tried installing a default instance yet).  Thanks

As a workaround, you can use the SQL Server Client Network Utility to create an alias for the "server/instance".  I created a server alias "MYSQLSRVR" with port 1433 and it worked for me but now I'm getting this error:
Error: Error in connector: Failed to connect to the database at MYSQLSRVR.
Tried using both Windows authentication and SQL authentication... both "sysadmin"... still isn't working.  It would be sure helpful for troubleshooting purposes to have a clearer indication as to why it failed to connect to the database.

Got it to work!  Try using the preferred IPv4 Address under Wireless LAN adapter Wi-Fi when you do "ipconfig /all".
I do it this way now, but you need the process ID (PID) of the service:

using Task Manager, going to the services tab, and then finding the service name (default ones) under MSSQLSERVER or MSSQL$SQLEXPRESS
using Sql Server Configuration Manager

After you have the PID, open up a terminal and type the following command (replace PID with the one you found, i.e. 4930 ):
netstat -ano | findstr PID

You will see a result that looks something like this "TCP <IP_ADDRESS>:60444 ...", where the port is after the colon.
Then you can replace the port in the '.env' file with the new port.
But this kinda defeats the point of having named instances, if you have to use workarounds to get them to work :\

Hey, we have some support for this in our underlying libraries, so we can definitely start supporting named instances. My biggest problem so far has been that I haven't found a good documentation on how you should define a named pipe in a JDBC connection string. It might not even exist, so this then brings us to implement something outside of the spec. Otherwise this is just adding the support to the connection string, documenting it and having a CI job somewhere that uses this method of connecting.

Hey, we have some support for this in our underlying libraries, so we can definitely start supporting named instances. My biggest problem so far has been that I haven't found a good documentation on how you should define a named pipe in a JDBC connection string. It might not even exist, so this then brings us to implement something outside of the spec. Otherwise this is just adding the support to the connection string, documenting it and having a CI job somewhere that uses this method of connecting.

@pimeys
Hey, thanks for your reply!
Yeah, having a solution that adheres to the spec would be the best option, but it definitely sucks that documentation is missing :\
What about this part of the spec, but I am guessing, it suffers from the same problem?

Currently this doesn't work in prisma, the "instanceName=instance1" is completely ignored, and it connects to the default instance.

Hey, can you confirm do you want named pipes support or just use the SQL Browser together with TCP. If it's the latter, did you try to add the name with two backslashes?
E.g.
sqlserver://localhost\\instance1;integratedSecurity=...

Actually, now when I'm looking at this once more, this is a bug of a feature that should work.

Hey, to clarify I want to use a named instance of a server, to connect through tcp.
I tried your suggestion with these options, and none of them work (find the port with the method from above):
DATABASE_URL="sqlserver://localhost\\SQLEXPRESS;database=taa;integratedSecurity=true;trustServerCertificate=true;"
DATABASE_URL="sqlserver://localhost\\SQLEXPRESS:2584;database=taa;integratedSecurity=true;trustServerCertificate=true;"
DATABASE_URL="sqlserver://DESKTOP-F3USMA8\\SQLEXPRESS;database=taa;integratedSecurity=true;trustServerCertificate=true;"
DATABASE_URL="sqlserver://DESKTOP-F3USMA8\\SQLEXPRESS:2584;database=taa;integratedSecurity=true;trustServerCertificate=true;"

Errors out with:
Error parsing connection string: Conversion error: Invalid instance name in database URL. Please refer to the documentation in
https://www.prisma.io/docs/reference/database-reference/connection-urls for constructing a correct connection string. In some
cases, certain characters must be escaped. Please check the string for any illegal characters."
DATABASE_URL="sqlserver://localhost\SQLEXPRESS;database=taa;integratedSecurity=true;trustServerCertificate=true;"
DATABASE_URL="sqlserver://localhost\SQLEXPRESS:2584;database=taa;integratedSecurity=true;trustServerCertificate=true;"
DATABASE_URL="sqlserver://DESKTOP-F3USMA8\SQLEXPRESS;database=taa;integratedSecurity=true;trustServerCertificate=true;"
DATABASE_URL="sqlserver://DESKTOP-F3USMA8\SQLEXPRESS:2584;database=taa;integratedSecurity=true;trustServerCertificate=true;"

Errors out with:
invocation:\n\n\nError creating a database connection. (Error creating a database connection.)"

Any update on this?

Any update on this?

Some context:

You can run multiple instances of the Database Engine on a computer. One instance can be the default instance. The default instance has no name. If a connection request specifies only the name of the computer, the connection is made to the default instance. A named instance is one where you specify an instance name when installing the instance. A connection request must specify both the computer name and instance name in order to connect to the instance. There is no requirement to install a default instance; all of the instances running on a computer can be named instances.

via https://learn.microsoft.com/en-us/sql/database-engine/configure-windows/database-engine-instances-sql-server?view=sql-server-ver16

Any updates on that one? Looks like it's still not solved...


Cookieless authentication

We aim to integrate the GWA application into the BCDC API Console (which is a custom version of swagger-ui embedded into a CKAN plugin).
The idea is to have a button within swagger-ui called "Get API Key".  Clicking that button will cause swagger-ui (a client-side app) to communicate with the GWA REST endpoint to fetch an API key. To do that GWA must support CORS.  Leo recently enabled CORS by adding the following header to responses from GWA:
Access-Control-Allow-Origin: *
... but the GWA REST endpoint seems to require a session tracking cookie to be passed with any request to the endpoint.  The requirement for a cookie presents a problem because browsers don't allow CORS from the wildcard (*) domain for requests that take cookies.  Browsers give an error like this:
Cannot load http://gwa-t.apps.gov.bc.ca/rest/apiKeys. The value of the 'Access-Control-Allow-Origin' header in the response must not be the wildcard '*' when the request's credentials mode is 'include'.
Do we have any option to modify GWA so cookies don't need to be passed when calling the REST endpoint?  Access tokens in HTTP headers or query string parameters should be fine...

@pauldaustin any suggestion?

fix by using REGEX in CORS

Leo
Please don't mess with the contract of the API outside of the application code. You have just opened a security hole in the application that allows apps to access the users api key without their permission.
At this point that URL is not designed to be used by other applications to access the API key.
The current correct way is that the application redirects the user to the API key page with the callback URL th at will be passed the API key when the user clicks th e approve access button. See the email I sent you.
If an alternate approach is required that will need to be implemented in the next release.
Until then remove the extra headers you added to allow cors.

I've linked this to the original enhancement request for Developer key enhancements


Need more clarity on HA of 99.995 for premium tier

This page doesn't clarify how many instances is required for 99.995 availability. There are many other pages which creates ambiguity in the understanding of High Availability offered.
When I purchase a single instance of this premium tier is 99.995 available to me or just 99.99?
OR I have to buy at least some instances to get these numbers of HA?

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

ID: cab7fc2b-b837-4141-a997-0c70e5a06bf9
Version Independent ID: 9771e71e-4cd1-36c5-8546-31e3dcafb448
Content: Business Critical service tier - Azure SQL Database & Azure SQL Managed Instance
Content Source: articles/azure-sql/database/service-tier-business-critical.md
Service: sql-db-mi
Sub-service: features
GitHub Login: @jovanpop-msft
Microsoft Alias: jovanpop

@arpit9mittal Thank you for the feedback. We are actively investigating and will get back to you soon.

@arpit9mittal Business critical tiers offer availability of 99.995% or 99.99% based on below details. Also we are looking at individual instances that you provision on the Azure.

Azure SQL Database Business Critical or Premium tiers configured as Zone Redundant Deployments have an availability guarantee of at least 99.995%.
Azure SQL Database Business Critical or Premium tiers not configured for Zone Redundant Deployments, General Purpose, Standard, or Basic tiers, or Hyperscale tier with two or more replicas have an availability guarantee of at least 99.99%.

Referenced link:
https://azure.microsoft.com/en-us/support/legal/sla/sql-database/v1_5/

Thanks, but I still have ambiguity please help clarify it .
As per the link -
https://azure.microsoft.com/en-us/support/legal/sla/sql-database/v1_5/

Azure SQL Database Business Critical tier configured with
geo-replication has a guarantee of Recovery point objective (RPO) of 5 sec
for 100% of deployed hours.
Azure SQL Database Business Critical tier configured with
geo-replication has a guarantee of Recovery time objective (RTO) of 30 sec
for 100% of deployed hours.

Question1 : If I have redundant zone replication and not geo-replication
then what will be my RTO & RPO ?
Question2 : For geo-replication, I assume I have to buy more instances
while in zone replication we have default 4 replicas with a purchase of a
single instance. Right ?
On Mon, Dec 28, 2020 at 11:43 PM AnuragSharma-MSFT<EMAIL_ADDRESS>wrote:

@arpit9mittal https://github.com/arpit9mittal Business critical tiers
offer availability of 99.995% or 99.99% based on below details. Also we are
looking at individual instances that you provision on the Azure.

Azure SQL Database Business Critical or Premium tiers configured
as Zone Redundant Deployments have an availability guarantee of at
least 99.995%.
Azure SQL Database Business Critical or Premium tiers not
configured for Zone Redundant Deployments, General Purpose, Standard,
or Basic tiers, or Hyperscale tier with two or more replicas have an
availability guarantee of at least 99.99%.

Referenced link:
https://azure.microsoft.com/en-us/support/legal/sla/sql-database/v1_5/
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/68142#issuecomment-751944288,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADTOFWXLG4QPXBKYSN7ANYLSXFM6JANCNFSM4VLSKZGQ
.

@arpit9mittal For the first query, it is not clearly documented about RTO and RPO when we configure Zone redundancy. Current available information talks only about availability. I am reaching to product group on the same.
For the second query, yes for geo-replication we need to configure/buy the instances based on how many secondary we need. For  zone replication, if possible could you please provide me link where it says creating 4 replicas?

Here is the link -
https://docs.microsoft.com/en-us/azure/azure-sql/database/high-availability-sla#premium-and-business-critical-service-tier-locally-redundant-availability
It says "* High availability is achieved by replicating both compute and
storage to additional nodes creating a three to four-node cluster."*
And it doesn't say that zone redundancy will add to the cost.
Therefore please confirm the following -

A single instance of premium tier will provide 99.99 with default 3-4
replicas without any extra cost.
If I opt for zone redundancy, the cost still remains the same but HA
increased to 99.995
What are the RPO and RTO with zone redundancy.

Regards
-Arpit Mittal
On Wed, Dec 30, 2020 at 4:20 AM AnuragSharma-MSFT<EMAIL_ADDRESS>wrote:

@arpit9mittal https://github.com/arpit9mittal For the first query, it
is not clearly documented about RTO and RPO when we configure Zone
redundancy. Current available information talks only about availability. I
am reaching to product group on the same.
For the second query, yes for geo-replication we need to configure/buy the
instances based on how many secondary we need. For zone replication, if
possible could you please provide me link where it says creating 4 replicas?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/68142#issuecomment-752387066,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADTOFWRQ4OE7Z7G4SJ5GVKLSXLWFFANCNFSM4VLSKZGQ
.

@arpit9mittal Please find my response below:

Yes single instance of premium or business critical tier offers 99.99% availability. (Refer to link):

Rightly said, zone redundancy cost will remain same for premium or business critical tiers but SLA will be increased to 99.995%.
I have reached out to product group on RTO and RPO and shall get back as early as I get the response.

@arpit9mittal Thanks for your patience. Please refer to the verbatim we received from product group "We do not provide an RTO and RPO wrt Zone Redundancy in our SLA. We only provide RTO and RPO wrt geo-replication with Business Critical tier of Azure SQL Database. "
Please let us know if you have any follow up queries.

@arpit9mittal Thanks for your patience. Please refer to the verbatim we received from product group "We do not provide an RTO and RPO wrt Zone Redundancy in our SLA. We only provide RTO and RPO wrt geo-replication with Business Critical tier of Azure SQL Database. "
Please let us know if you have any follow up queries.

Hi,
Yes, this is concerning if we do not know the lag between zone replicas
then we cannot trust to adopt this model. Then it's better to be with just
geo-replication for disaster recovery, instead of achieving HA with zone
replications.
Regards
-Arpit Mittal
On Mon, Jan 4, 2021 at 2:48 AM AnuragSharma-MSFT<EMAIL_ADDRESS>wrote:

@arpit9mittal https://github.com/arpit9mittal Thanks for your patience.
Please refer to the verbatim we received from product group "We do not
provide an RTO and RPO wrt Zone Redundancy in our SLA. We only provide RTO
and RPO wrt geo-replication with Business Critical tier of Azure SQL
Database. "
Please let us know if you have any follow up queries.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/68142#issuecomment-753815663,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADTOFWVQD73SMLMIEOJIDPTSYFXF5ANCNFSM4VLSKZGQ
.

Hi,
Yes, this is concerning if we do not know the lag between zone replicas
then we cannot trust to adopt this model. Then it's better to be with just
geo-replication for disaster recovery, instead of achieving HA with zone
replications.
Regards
-Arpit Mittal
On Mon, Jan 4, 2021 at 2:48 AM AnuragSharma-MSFT<EMAIL_ADDRESS>wrote:

@arpit9mittal https://github.com/arpit9mittal Thanks for your patience.
Please refer to the verbatim we received from product group "We do not
provide an RTO and RPO wrt Zone Redundancy in our SLA. We only provide RTO
and RPO wrt geo-replication with Business Critical tier of Azure SQL
Database. "
Please let us know if you have any follow up queries.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/68142#issuecomment-753815663,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADTOFWVQD73SMLMIEOJIDPTSYFXF5ANCNFSM4VLSKZGQ
.

@arpit9mittal Yes you are right as currently RTO and RPO with zone redundancy are not available but should be available in future. We cannot commit the dates as well. And we do have these available for geo-replication. I will take this feedback to product team.
Please let us know if you have any other queries and we can discuss the same.

@arpit9mittal Yes you are right as currently RTO and RPO with zone redundancy are not available but should be available in future. We cannot commit the dates as well. And we do have these available for geo-replication. I will take this feedback to product team.
Please let us know if you have any other queries and we can discuss the same.

@arpit9mittal We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.

@arpit9mittal We will now proceed to close this thread. If there are further questions regarding this matter, please comment and we will gladly continue the discussion.


How to know the iteration number inside custom eval function

Hi, how to know (in R interface) the iteration number inside a custom eval function?
I have a very intensive custom eval function with a very small learning rate, so I'm only interested in check early stopping each 10 or 20 iterations and save time.
Thanks.

I think you can count the evaluation by a captured variable.

I found using <<- assignment of an iter counter inside custom eval works.
Using CV is necessary adjust the counter as eval is called for each fold.

Yup. Feel free to reopen if there are further questions.


Inside MainViewModel.Export(), exception handling was made using a more specific exception type

This helps us get rid of the awkward variable assignment inside the try block, and we can just assign the variable directly

Sure, we can do that. See if you like the updated version better


Instrument metadata configuration file

Create few examples of instrument metadata configuration file.
They should be in json format, cover the relevant use cases for FAIRness level 1.

This issue has been addressed by PR #46 and #44


Some integration tests still using the production devfile registry

A while back https://github.com/openshift/odo/pull/4752 was merged to move the odo integration tests from using the production devfile registry (https://registry.devfile.io) to staging (https://registry.stage.devfile.io) as we didn't want the telemetry for the devfile registry polluted.
We recently set up telemetry on the devfile registry service and saw a ton of pollution coming back from what appears to be an automated process, for both listing devfiles, and download nodejs & python stacks. Since odo's integration tests primarily test with those stacks (mainly nodejs, but also python for link/unlink tests), we suspected it would be these tests.
I looked through odo's integration tests and saw that the following test files call out to the registry but don't set the registry to staging:

cmd_link_unlink_test.go: odo create without --s2i flag
cmd_pref_config_test.go: odo create without --s2i flag
operatorhub/cmd_link_test.go odo create without --s2i flag
operatorhub/cmd_service_test.go odo create without --s2i flag
component.go: odo create without --s2i flag and odo catalog list components
generic_test.go: odo catalog list components

I wonder if would be more straightforward to call helper.SetDefaultDevfileRegistryAsStaging() from within helper.CommonBeforeEach() so that helper.SetDefaultDevfileRegistryAsStaging() doesn't have to be called from each individual test file?

I wonder if would be more straightforward to call helper.SetDefaultDevfileRegistryAsStaging() from within helper.CommonBeforeEach() so that helper.SetDefaultDevfileRegistryAsStaging() doesn't have to be called from each individual test file?

This made sense to me. I have opened #5057 which could address the issue.

Link to the main telemetry issue: https://github.com/devfile/api/issues/281


External user journey map

Describe the task
Create a Roadmap for the external user facing work. We need to uncover who within CIF would be our ally in doing external user engagement. Need to subsequently decide on communication plan, timeline etc
Acceptance Criteria

[x] Ask CIF team if they have the external User Journey mapped out.
[x] If not, create one with them (Amanda would be a good point of contact for this) Reach out to the CIF Team to narrow down the scope of External User Portal and confirm the user flow
[x] Prepare Miro board for workshop
[x] Prepare Miro board for doing an async review of the workshop
[x] Prepare meeting invites for a synced conversation on the workshop
[x] Send out invites
[ ] Review and revise the CIF Process Miro Board
[ ] Share findings with team in dev/design Sync to brainstorm about the application implementation and high level design ideas

Additional context

This ticket was made after closing #941 work
Or here

Feedback from January 5, 2023 Sprint Review:

There is no existing user journey map

External user journey mapping conducted with CIF team on Jan 16. It was a productive conversation. Some next action items include reaching out to Megan and the Tech team for their input on the journey map, after organizing the information uncovered during the first session.

External user journey mapping conducted with CIF team on Jan 16. It was a productive conversation. Some next action items include reaching out to Megan and the Tech team for their input on the journey map, after organizing the information uncovered during the first session.

External user journey mapping conducted with CIF team on Jan 16. It was a productive conversation. Some next action items include reaching out to Megan and the Tech team for their input on the journey map, after organizing the information uncovered during the first session.

External user journey mapping conducted with CIF team on Jan 16. It was a productive conversation. Some next action items include reaching out to Megan and the Tech team for their input on the journey map, after organizing the information uncovered during the first session.

External user journey mapping conducted with CIF team on Jan 16. It was a productive conversation. Some next action items include reaching out to Megan and the Tech team for their input on the journey map, after organizing the information uncovered during the first session.

External user journey mapping conducted with CIF team on Jan 16. It was a productive conversation. Some next action items include reaching out to Megan and the Tech team for their input on the journey map, after organizing the information uncovered during the first session.

Miro board updated and organized. From our discussion, features have been identified and listed in the board. Findings can be reported for the upcoming dev design sync. @LindsayMacfarlane after your review this issue is good to be closed! c:

Thank you @suhafa ! I had to jump out of the dev/design sync session, so I'm assuming this was discussed? As a side note, I removed the link to the Miro Board above as we are trying not to link out to board that can be public.

@LindsayMacfarlane we discussed the findings from both the sessions Nan and I had over the course of this week, but the Miro board itself was not reviewed by the team in detail since the higher level concerns were discussed already. I check off the last point. Feel free to close this ticket! c:


Ahk+

Hi, something may have gone wrong submitting your issue. We're going to close this one, please open a new issue with details if you have any feedback :)


Add support for double precision.

This allows cgltf_float to be set to double.  Resolves #228.

Adds a define GLTF_DOUBLE_PRECISION that when set sets cgltf_float to double instead of float.
Adds a flag to enable testing with ./test_all.py --double-precision

One subtlety that this is missing from #228 is cgltf_accessor_read_float / cgltf_accessor_unpack_floats. These should continue to use 32-bit float types, one because glTF data contained in accessors can't be double precision, two because these functions have fast paths that directly copy 32-bit floats.
We should also audit uses of cgltf_component_type_r_32f to double check that these don't use cgltf_float.
All of this could probably use cgltf_float32 to be explicit; naked floats are probably not a good idea once we have this configuration define.

Also cgltf_write's CGLTF_DECIMAL_DIG constant probably needs to be updated here.

cgltf_accessor_read_float looks ok to me.  I think you may be right about cgltf_accessor_unpack_floats, all tests are passing now, so I'll create a test that fails it and come up with a patch.
cgltf_float32 is a fine idea, there seemed to already be an assumption that float was 32 bits so I went with it, but this is an easy change.
I need more time to understand CGLTF_DECIMAL_DIG a bit more, but you have a point here.


The .tar.gz distribution isn't installable

@SukeerthiBJ notes here:
https://github.com/Preston-Landers/concurrent-log-handler/pull/67#issuecomment-2337062013
That the .tar.gz release doesn't seem to include the setup.py script, making it difficult to install normally.
On the release page here there's two .tar.gz files - I think one is auto-generated - but neither seems to include setup.py / setup.cfg.

@Preston-Landers , is there a way to get these two files for this tar. For our internal python package creation this step is failing due to absence of these files

Actually I forgot about earlier changes that got rid of the setup.py file.
Instead, you're supposed to use the pyproject.toml file. E.g. with Pip you can download the tar.gz and cd into it and run pip install .


No Response from Host [Bug]

Describe the issue

When adding the integration, it loads for a few seconds and results in an error "No response from Host".
My setup is a bit particular, as Home Assistant runs as HA-OS in a VM inside the TrueNAS Scale system I am trying to monitor. I do not know if there is an issue with the routing of IPs inside of it that could cause the issue? Network configuration is not my forte...
How to reproduce the issue

Expected behavior

Screenshots

Software versions

Home Assistant version: 2024.4.4 (Supervisor 2024.04.4)
TrueNAS integration version: latest
TrueNAS version: TrueNAS-SCALE-23.10.2

Diagnostics data

Traceback/Error logs

2024-05-07 01:36:47.017 WARNING (SyncWorker_6) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "pool" (no_response)
2024-05-07 01:36:47.017 ERROR (MainThread) [custom_components.truenas.config_flow] TrueNAS connection error (no_response)
2024-05-07 01:37:25.267 WARNING (SyncWorker_10) [custom_components.truenas.api] TrueNAS <IP_ADDRESS>/24 unable to fetch data "pool" (no_response)
2024-05-07 01:37:25.268 ERROR (MainThread) [custom_components.truenas.config_flow] TrueNAS connection error (no_response)
Additional context

Your VM most likely cannot access truenas host. Try to access your nas from HA command line.

I created a bridge so that they can communicate from each other, but sadly I am still getting the same error. I can ping my truenas IP just fine from HAOS Terminal now, so this is even weirder now!...
The logs aren't very chatty either...
2024-05-11 00:28:11.496 WARNING (SyncWorker_5) [custom_components.truenas.api] TrueNAS <IP_ADDRESS> unable to fetch data "pool" (no_response)
2024-05-11 00:28:11.497 ERROR (MainThread) [custom_components.truenas.config_flow] TrueNAS connection error (no_response)

Did you use <IP_ADDRESS>:444 ?

are you using standard port for web and do you have valid certificate?

All of this is inside my network, I am using the self-signed certificate from truenas, and nothing special on ports. It's not a truenas instance that's outside of my network that I'm trying to reach, that's why I find it weird that it can't reach, especially since I can ping the nas just fine from inside the HAOS shell.

I somehow fixed it by trying again all the combinations of options above related to SSL (Use SSL on/off, Verify Certificate on/off). But didn't record which one worked, so sorry again for disturbing you and thank you so much for your help !
PS: I did have to create a bridge and assign that br0 to both main truenas and the VM for it to work, but that's a truenas quirk. If anyone has an issue with it ping or PM me I'll be happy to help with that.


[FLINK-26793][documentation] Add recommendations about the write timeout to the javadoc of Cassandra sink and output format

R: @AHeise

R: @zentol I pinged you because we worked together on cassandra. Feel free to ping another reviewer if that makes too many reviews.

@MartijnVisser could we review this one please ? Please don't forget to read the comments in the ticket that contain the details of the experimentation for diagnostic.

@MartijnVisser @zentol friendly ping

@echauchot Sorry, I'll have a look today :)


Scala 2.13 supports by-name implicits

Resubmitting this PR (originally #1879) as requested by the CLA error message in CI. I'm sure I've signed these CLAs before but I did them both again.
I've just copied the relevant tests from the Dotty dialect test suite—I'm happy to expand them if people want.

This time the failure looks definitely spurious instead of just probably spurious.

The CI failure is definitely spurious, I've cleaned the cache and rested the failing job. Let's see

Ok, all ✅ now!


Update sbt-github-actions to 0.13.0

Updates com.codecommit:sbt-github-actions from 0.12.0 to 0.13.0.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Files still referring to the old version number
The following files still refer to the old version number (0.12.0).
You might want to review and update them manually.
CHANGELOG.md
website/yarn.lock

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.codecommit", artifactId = "sbt-github-actions" } ]

labels: sbt-plugin-update, semver-minor, old-version-remains

will do manually


Example does not run

I found two issues, one of which I was able to fix with reference to https://github.com/facebook/react-native/issues/14935 (the location of a critical script has changed from the packager folder to the scripts folder).
The second issue is beyond me. I get a successful build,

** BUILD SUCCEEDED **
Installing build/Build/Products/Debug-iphonesimulator/example.app
Launching org.reactjs.native.example.example

and the packager is running OK, but I get this error in the simulator when launching the app,

Failed to load bundle... index.ios.bundle

because of an

Invalid or unexpected token (While processing preset: ".../example/node_modules/babel-preset-react-native/index.js")

Thanks for question and sorry for delayed reply. Looks like all those issues are related to your local setup and babel configuration. Please, try running example project in clean environment.


remove c-style (incorrect) switch handling

What does this PR do?
We have some c-style code in go.
This PR cleans up that.

👍

+1


Cache not Ready

Hello,
i've build all based on the master branch from today (Fedora 33). All container start, but i can not login.
I've not set admin password, so i can use the default admin:admin.
The console show always this error(?):
autoupdate_1    | 2021/03/18 12:04:02 Cache not ready. Try again in 3 seconds
autoupdate_1    | 2021/03/18 12:04:05 Cache not ready. Try again in 3 seconds
What can i do become the cache ready?
Greetings,
Peter

Hi, I suppose you are using the productive setup as described in the readme? What do the logs for server say? (e.g. docker-compose logs server)

server_1        | ERROR: Django secret key undefined!  Cannot continue.
server_1        | /usr/local/sbin/entrypoint: line 6: /run/secrets/django: Permission denied
server_1        | ERROR: Django secret key undefined!  Cannot continue.
server_1        | /usr/local/sbin/entrypoint: line 6: /run/secrets/django: Permission denied
server_1        | ERROR: Django secret key undefined!  Cannot continue.
server_1        | ERROR: Django secret key undefined!  Cannot continue.
server_1        | /usr/local/sbin/entrypoint: line 6: /run/secrets/django: Permission denied
server_1        | /usr/local/sbin/entrypoint: line 6: /run/secrets/django: Permission denied
server_1        | ERROR: Django secret key undefined!  Cannot continue.
server_1        | /usr/local/sbin/entrypoint: line 6: /run/secrets/django: Permission denied
The file i created based on the install description is secrets/django.env

/run/secrets/django: Permission denied

Secrets are mounted into the containers. Make sure that the docker daemon can access your secret on the host machine.

Hmm.
now i compose as root instead of my docker user.
docker-compose rm
docker-compose up
same problem.
which container is  setting the path to /run/secrets/django to secrets first?
(the  file secrets/adminsecret.env is loaded fine. without this file, there are more errors)

i've connect the container docker_autoupdate_1  and went into the path /run/secrets:
/run/secrets # ls -alt
ls: ./django: Permission denied
total 0
drwxr-xr-x    2 root     root            20 Mar 18 15:01 .
drwxr-xr-x    1 root     root            21 Mar 18 15:01 ..
/run/secrets #

Which user are you inside the docker container?

ah. ok. in this test i was my docker-user not root
now i'will test it also as root.

also as root, permission denied

in my environment, i normaly do anything as docker-user
git, compile startup, create secrets and so on.
the container start as docker-user with the same rights as the files i created.
So i think, the path to secrets in the container is missing or wrong

I assume, that you did create the secrets/django.env in the docker folder, right?

yes (the username is slider)
The full path is /opt/slider/OpenSlides/docker
/opt/slider is the home-directory of user slider
I have set chmod 777 to docker.env, but this does not help
[slider@fc-docker01 ~/OpenSlides/docker]$ ls
build.sh  docker-compose.dev.yml  docker-compose.yml  docker-compose.yml.m4  docker-stack.yml.m4  postgresql.dev.conf  secrets
[slider@fc-docker01 ~/OpenSlides/docker]$ ls -l secrets/
insgesamt 20
-rw-r--r--. 1 slider docker 152 18. Mär 12:22 adminsecret.env
-rw-r--r--. 1 slider docker 152 18. Mär 09:30 adminsecret.env.example
-rwxrwxrwx. 1 slider docker  85 18. Mär 12:24 django.env
-rwxrwxrwx. 1 slider docker 132 18. Mär 09:30 django.env.example
-rw-r--r--. 1 slider docker 198 18. Mär 09:30 usersecret.env.example

I've do another fresh install and pipe the build.sh all output to file.
At step 11/19 an django-File created.
Is it possible that this file has the wrong permission?

Step 8/19 : RUN go build ./cmd/autoupdate
---> Running in 4ff2bfb7b040
Removing intermediate container 4ff2bfb7b040
---> 6f6a05a53f4e
Step 9/19 : FROM builder as development
---> 6f6a05a53f4e
Step 10/19 : RUN mkdir -p /run/secrets
---> Running in 1086a992acfb
Removing intermediate container 1086a992acfb
---> 50427b4fa96a
Step 11/19 : RUN echo "DJANGO_SECRET_KEY='development'" > /run/secrets/django
---> Running in<PHONE_NUMBER>4f

Hello Finn,
this problem is fixed. I've disabled selinux complete.
The bind volumes must mounted with :z flag if selinux is on
https://docs.docker.com/storage/bind-mounts/#configure-the-selinux-label

Ok, glad you found the issue!

Hello Finn,
another fresh install from master this morning (All docker-containers removed --- systemctl stop docker; rm -fr /var/lib/docker/*; systemctl start docker; rm -fr OpenSlides, net git clone..... django.env is set, adminsec.env also set),
all other settings default, without change anything.
New errors:
server-setup_1  | [2021-03-19 08:40:24 +0100] [31] [INFO] openslides.utils.redis_connection_pool [VdfI] CONNECTION_POOL_LIMIT=100
server-setup_1  | [2021-03-19 08:40:24 +0100] [31] [INFO] openslides.utils.redis [VdfI] Redis address redis://redis:6379/0
server-setup_1  | [2021-03-19 08:40:24 +0100] [31] [INFO] openslides.utils.redis [VdfI] Redis read only address redis://redis-slave:6379/0
server-setup_1  | [2021-03-19 08:40:24 +0100] [31] [INFO] openslides.utils.stream [VdfI] Redis stream maxlen None
server-setup_1  | [2021-03-19 08:40:24 +0100] [31] [INFO] openslides.mediafiles.models [VdfI] Using a standalone mediafile database
server-setup_1  | [2021-03-19 08:40:24 +0100] [31] [INFO] openslides.mediafiles.views [VdfI] Using a standalone mediafile database
server-setup_1  | Operations to perform:
server-setup_1  |   Apply all migrations: agenda, assignments, auth, chat, contenttypes, core, mediafiles, motions, sessions, topics, users
server-setup_1  | Running migrations:
server-setup_1  | [2021-03-19 08:40:24 +0100] [31] [WARNING] openslides.utils.redis [VdfI] Redis Exception: . Do not reuse connection...
server-setup_1  | [2021-03-19 08:40:24 +0100] [31] [WARNING] openslides.utils.cache_providers [VdfI] Redis was flushed before method 'get_collection_data'. Ensures cache now.
server-setup_1  | [2021-03-19 08:40:24 +0100] [31] [INFO] openslides.utils.cache [VdfI] Building config data and resetting cache...
server-setup_1  | [2021-03-19 08:40:24 +0100] [31] [INFO] openslides.utils.models [VdfI] Loading core/config
server-setup_1  | [2021-03-19 08:40:24 +0100] [31] [WARNING] openslides.utils.redis [VdfI] Redis Exception: ('MultiExecError errors:', [ValueError('args[0] is empty dict')]). Do not reuse connection...
server-setup_1  | Traceback (most recent call last):
server-setup_1  |   File "/app/openslides/utils/cache_providers.py", line 473, in eval
server-setup_1  |     result = await redis.evalsha(hash, keys, args)
server-setup_1  | aioredis.errors.ReplyError: cache_reset
server-setup_1  | During handling of the above exception, another exception occurred:
server-setup_1  | Traceback (most recent call last):
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/asgiref/sync.py", line 339, in thread_handler
server-setup_1  |     raise exc_info[1]
server-setup_1  |   File "/app/openslides/utils/cache_providers.py", line 101, in wrapped
server-setup_1  |     result = await func(cache_provider, *args, **kwargs)
server-setup_1  |   File "/app/openslides/utils/cache_providers.py", line 358, in get_collection_data
server-setup_1  |     read_only=True,
server-setup_1  |   File "/app/openslides/utils/cache_providers.py", line 478, in eval
server-setup_1  |     raise CacheReset()
server-setup_1  | openslides.utils.cache_providers.CacheReset
server-setup_1  | During handling of the above exception, another exception occurred:
server-setup_1  | Traceback (most recent call last):
server-setup_1  |   File "manage.py", line 11, in
server-setup_1  |     exit(main())
server-setup_1  |   File "/app/openslides/main.py", line 41, in main
server-setup_1  |     execute_from_command_line(sys.argv)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/core/management/init.py", line 381, in execute_from_command_line
server-setup_1  |     utility.execute()
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/core/management/init.py", line 375, in execute
server-setup_1  |     self.fetch_command(subcommand).run_from_argv(self.argv)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 323, in run_from_argv
server-setup_1  |     self.execute(*args, **cmd_options)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 364, in execute
server-setup_1  |     output = self.handle(*args, **options)
server-setup_1  |   File "/app/openslides/core/management/commands/migrate.py", line 25, in handle
server-setup_1  |     super().handle(*args, **options)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/core/management/base.py", line 83, in wrapped
server-setup_1  |     res = handle_func(*args, **kwargs)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/core/management/commands/migrate.py", line 234, in handle
server-setup_1  |     fake_initial=fake_initial,
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 117, in migrate
server-setup_1  |     state = self._migrate_all_forwards(state, plan, full_plan, fake=fake, fake_initial=fake_initial)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 147, in _migrate_all_forwards
server-setup_1  |     state = self.apply_migration(state, migration, fake=fake, fake_initial=fake_initial)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/executor.py", line 245, in apply_migration
server-setup_1  |     state = migration.apply(state, schema_editor)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/migration.py", line 124, in apply
server-setup_1  |     operation.database_forwards(self.app_label, schema_editor, old_state, project_state)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/db/migrations/operations/fields.py", line 249, in database_forwards
server-setup_1  |     schema_editor.alter_field(from_model, from_field, to_field)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 535, in alter_field
server-setup_1  |     old_db_params, new_db_params, strict)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/postgresql/schema.py", line 124, in _alter_field
server-setup_1  |     new_db_params, strict,
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 649, in _alter_field
server-setup_1  |     new_default = self.effective_default(new_field)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 233, in effective_default
server-setup_1  |     return field.get_db_prep_save(self._effective_default(field), self.connection)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/db/backends/base/schema.py", line 212, in _effective_default
server-setup_1  |     default = field.get_default()
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/django/db/models/fields/init.py", line 801, in get_default
server-setup_1  |     return self._get_default()
server-setup_1  |   File "/app/openslides/agenda/models.py", line 364, in list_of_speakers_initially_closed
server-setup_1  |     return config["agenda_list_of_speakers_initially_closed"]
server-setup_1  |   File "/app/openslides/core/config.py", line 54, in getitem
server-setup_1  |     self.get_collection_string(), self.get_key_to_id()[key]
server-setup_1  |   File "/app/openslides/core/config.py", line 62, in get_key_to_id
server-setup_1  |     async_to_sync(self.build_key_to_id)()
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/asgiref/sync.py", line 147, in call
server-setup_1  |     return call_result.result()
server-setup_1  |   File "/usr/local/lib/python3.7/concurrent/futures/_base.py", line 428, in result
server-setup_1  |     return self.__get_result()
server-setup_1  |   File "/usr/local/lib/python3.7/concurrent/futures/_base.py", line 384, in __get_result
server-setup_1  |     raise self._exception
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/asgiref/sync.py", line 212, in main_wrap
server-setup_1  |     result = await self.awaitable(*args, **kwargs)
server-setup_1  |   File "/app/openslides/core/config.py", line 83, in build_key_to_id
server-setup_1  |     self.get_collection_string()
server-setup_1  |   File "/app/openslides/utils/cache.py", line 257, in get_collection_data
server-setup_1  |     collection
server-setup_1  |   File "/app/openslides/utils/cache_providers.py", line 107, in wrapped
server-setup_1  |     await cache_provider.ensure_cache()
server-setup_1  |   File "/app/openslides/utils/cache_providers.py", line 278, in ensure_cache
server-setup_1  |     await self._ensure_cache()
server-setup_1  |   File "/app/openslides/utils/cache.py", line 107, in async_ensure_cache
server-setup_1  |     await self.build_cache(default_change_id)
server-setup_1  |   File "/app/openslides/utils/cache.py", line 131, in build_cache
server-setup_1  |     default_change_id=default_change_id, schema_version=schema_version
server-setup_1  |   File "/app/openslides/utils/cache.py", line 151, in _build_cache
server-setup_1  |     await self.cache_provider.reset_full_cache(config_mapping, change_id)
server-setup_1  |   File "/app/openslides/utils/cache_providers.py", line 301, in reset_full_cache
server-setup_1  |     await tr.execute()
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/aioredis/commands/transaction.py", line 180, in execute
server-setup_1  |     return_exceptions=return_exceptions)
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/aioredis/commands/transaction.py", line 299, in _do_execute
server-setup_1  |     return (await self._gather_result(return_exceptions))
server-setup_1  |   File "/usr/local/lib/python3.7/site-packages/aioredis/commands/transaction.py", line 201, in _gather_result
server-setup_1  |     raise self.error_class(errors)
server-setup_1  | aioredis.errors.MultiExecError: ('MultiExecError errors:', [ValueError('args[0] is empty dict')])

hi, i've got the same error as @pedda4711 on a fresh server with a new untouched docker installation. I would be very interested in a solution too!

Lets keep track in #5974


[BUG] Failed S3 snapshots are able to be restored, causing downstream clusters to be stuck in a Provisioning state  with error message Operation etcd restore failed

Rancher Server Setup

Rancher version: v2.7-head https://github.com/rancher/rancher/commit/1f014b7fcd734e9321555b613cc28b1b12bf8eeb
Installation option (Docker install/Helm Chart): Docker

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc):

Proxy/Cert Details:

Information about the Cluster

Kubernetes version: v1.25.9+rke2r1
Cluster Type (Local/Downstream): Downstream

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider): AWS

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom) Cluster Owner

If custom, define the set of permissions:

Describe the bug

When provisioning a downstream node driver RKE2 cluster, I enabled S3 backups. However, I used a non-existent S3 bucket when provisioning. When attempting to create a backup, I see the following:

I would expect an error, so that part is fine...however, I am able to actually restore this failed backup. When I do that, I see the following error message:

Looking into the logs further, I noted the following:
2023/05/09 19:51:19 [ERROR] [planner] rkecluster fleet-default/mew-rke2-broken-snapshot: error encountered during plan processing was operation etcd restore failed
2023/05/09 19:51:19 [ERROR] error syncing 'fleet-default/mew-rke2-broken-snapshot': handler planner: operation etcd restore failed, requeuing
2023/05/09 19:51:24 [ERROR] error syncing 'c-m-sn6t785b': handler cluster-deploy: Get "https://<IP_ADDRESS>:443/apis/apps/v1/namespaces/cattle-system/daemonsets/cattle-node-agent": cluster agent disconnected, requeuing
2023/05/09 19:52:10 [ERROR] error syncing 'c-m-sn6t785b': handler cluster-deploy: Get "https://<IP_ADDRESS>:443/apis/apps/v1/namespaces/cattle-system/daemonsets/cattle-node-agent": cluster agent disconnected, requeuing
2023/05/09 19:52:54 [ERROR] error syncing 'c-m-sn6t785b': handler cluster-deploy: Get "https://<IP_ADDRESS>:443/apis/apps/v1/namespaces/cattle-system/daemonsets/cattle-node-agent": cluster agent disconnected, requeuing
2023/05/09 19:53:19 [INFO] [planner] rkecluster fleet-default/mew-rke2-broken-snapshot: electing init node for S3 snapshot fleet-default/mew-rke2-broken-snapshot-on-demand-mew-rke2-broken-snapsh-f0d4a restoration
2023/05/09 19:53:19 [ERROR] [planner] rkecluster fleet-default/mew-rke2-broken-snapshot: error encountered during plan processing was operation etcd restore failed

Considering that the backup failed, I would expect to not be able to restore from a failed backup.
To Reproduce

As a standard user, provision a downstream node driver RKE2 cluster with S3 backups enabled and specify a non-existent bucket.
Create an S3 snapshot; validate that the bucket does not get created.
Restore that S3 snapshot and note that the cluster is an error state as mentioned above.

Result
I am able to restore my cluster using a failed S3 snapshot.
Expected Result

I should not able to restore my cluster if a S3 snapshot has failed; the option should not be provided to me at all.

@nwmac @gaktive , FYI - transferred this one to dashboard.

@edenhernandez-suse @kwwii there's also another place where users can trigger restoring a failed snapshot from the list of clusters on Cluster Management page:

it opens a prompt modal:

is it acceptable as a solution if we filter the failed snapshots from the dropdown list?

Ideally the UI should display only valid options. That means filtering out the failed snapshots from the list of possible options.

Ticket #8839 - Test Results - :x: - RE-OPENED
Verified with HA Helm on Rancher v2.7-369c7d37b9e678922297c3811b4329e18da4abdf-head:

Scenario
Test Case
Result

1.
From Cluster Management > Clusters page, attempt a snapshot restore with an invalid snapshot
✅

2.
From Cluster Management > Cluster Details > Snapshots (tab), attempt a snapshot restore with an invalid snapshot
:x:

Scenario 1 - ✅

Fresh install of Rancher v2.7-head
As admin, create a standard user
As standard user, provision a downstream RKE2 cluster w/ s3 etcd backup configured and pointing to a non-existent bucket
Verified - cluster successfully provisions
Take a snapshot
Once active, navigate to Cluster Management > Clusters page, select the three dots next to cluster and then select Snapshot Restore
Verified - invalid snapshot has been filtered out; valid local snap is displayed; as expected

Scenario 2 - :x:

Fresh install of Rancher v2.7-head
As admin, create a standard user
As standard user, provision a downstream RKE2 cluster w/ s3 etcd backup configured and pointing to a non-existent bucket
Verified - cluster successfully provisions
Take a snapshot
Once active, navigate to Cluster Management > Cluster Details > Snapshots (tab), select the three dots next to invalid snapshot, and select restore
Veri-FAILED - Rancher attempts to restore cluster with an invalid snapshot; errored out with operation etcd restore failed

❗NOTE:❗
With scenario 2, after the initial failure, I attempted to reproduce this again on a new cluster, and was unable to do so.  Second attempt results showcased in screenshot below for step 6; which is expected - re-opening due to inconsistencies

re-opening to re-test latest changes.

Ticket #8839 - Test Results - ✅
The following test case was executed 3 times:
With HA Helm on Rancher v2.7-027246f77f03b82660dc2e91df6bf2cd549163f0-head:

Scenario
Test Case
Result

1.
Provision a downstream RKE2 cluster w/ s3 configured + from Cluster Management > Cluster Details > Snapshots (tab), attempt a snapshot restore with an invalid snapshot
✅

Scenario 1 - Executed 3 times - [ ✅ ✅ ✅ ]

Fresh install of Rancher v2.7-head
Provision a downstream RKE2 cluster w/ s3 etcd backups configured to a non-existent s3 bucket
Once active, navigate to Cluster Management > Cluster Details > Snapshots (tab), and take a snapshot
Verified - snapshot captured; s3 snapshot is invalid; as expected
Attempt to restore cluster back to invalid s3 snapshot taken
Verified - Unable to restore to s3 snapshot taken; UI prompts the following message: No actions available; as expected


(fleet) remove existing package entry in the DB on re-install

When installer install <pkg> is called multiple times we can have the following sequence:

Install pkg v1 :ok:
Install pkg v2 :fail:

Before this would lead to v1 still being marked as installed while the failed install of v2 might have broke v1. As such this PR removes the mark that v1 was installed before starting to install v2.

/merge


Fixed #24117 -- Made admin not require context_processors

https://code.djangoproject.com/ticket/24117

I suspect this requires some documentation changes.

Did you see my comment on the ticket -- how about a mention in the release notes? Also, we can update the "Overview" on admin page to remove "django.contrib.messages.context_processors.messages".

Blah. I just wrote up a release and then accidentally cleared them out without properly committing them. Based on the mailing list feedback I think we should defer to 1.9.

What's the way? I'm intrigued. Ticket?

I'd be interested in looking into the possibility of passing "request" to the template and using "request.messages" (a new "feature" I have half implemented in my stash) and "request.user" in the templates. https://code.djangoproject.com/ticket/24117#comment:8


[Low Risk Cleanup] Removes double semicolons

Removes double semicolons since they are not needed.
No specific testing since there are no functional changes. This is low risk.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: kamronbatman sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

@aspnet-hello triage https://dev.azure.com/dnceng/public/_build/results?buildId=414066

This comment was made automatically. If there is a problem contact<EMAIL_ADDRESS>I've triaged the above build. I've created/commented on the following issue(s)
https://github.com/aspnet/AspNetCore-Internal/issues/3295

The triage doesn't exist?

@kamronbatman don't worry about that, it's for our internal tracking!
The change looks good, I'll approve it and we'll merge it hopefully later today.

Thanks @kamronbatman!


Publishing child apps from other authoring resources than dispatch app shows error

Tool
Name: Dispatch
Version: 1.6.8
OS: Win 10 build 18363.720
Describe the bug and reproduction steps
I have 2 LUIS child apps in different authoring resources. I want to create a dispatch app in authoring resource 1 (AR1), using an app from AR1 and using another app from AR2.
The script runs through and I can use the dispatch app afterwars. However I get the following error in the logs and am unsure whether it's any problem that the child apps are not republished (why are they published at all, I wonder?).
[...]
Publishing app1 model...
Publishing app2 model...
Failed adding subscription key/publishing app2 - {
  "error": {
    "code": "Unauthorized",
    "message": "The user is not the owner or a co-owner of this application."
  }
}
Training test-dispatch model...
Publishing test-dispatch model...
[...]

I guess it's internally using the key of AR1 instead of AR2 for this request?
To Reproduce
Steps to reproduce the behavior:
Create a LUIS dispatch application using
dispatch init -n "test-dispatch" --luisAuthoringKey "key1" --luisAuthoringRegion "westeurope"
dispatch add -t luis -i "id1" -k "key1" --intentName "app1"
dispatch add -t luis -i "id2" -k "key2" --intentName "app2"
dispatch create

Expected behavior
No errors should be shown in the output.
[bug]

@sibbl, are AR1/AR2 owned by the same user?  How about subscription key?  Trying to get a repro...

@tsuwandy yes, both ARs were created by me. What could be specific is that the apps were all in AR2 beforehand. App1 created by me, app2 imported by a colleague. I then moved app1 into AR1 and created the dispatch app there.

And Dispatch is created using AR1 (which also has prediction resource)?

@tsuwandy yes, indeed. Dispatch and app1 are in AR2, app1 was kept in AR1.

@sibbl I got a repro. Still investigating, will update this thread as soon I figure out how to fix.

@sibbl , will have to consult with LUIS team what to do in this case.
Is there specific reason they have to be in different apps?

@tsuwandy you mean in different authoring resources? The background is mostly organizational so that we have a better separation of concern.
We have reusable Luis apps (AR2) and project specific Luis apps (AR1). Both kind of apps are combined into dispatch applications which we use for MS bot framework based chatbots for example.

@sibbl, we just published an update to dispatch (version 1.6.9).    Ignore the child publishing error as long as the whole dispatch app is created, trained and published.    We still have to support both apps not yet migrated to Azure and also those already on Azure LUIS resource.   Let me know if you are seeing issues using the newly created Dispatch app.  Please reactivate this issue if you are not able to use the Dispatch app.   Thanks!
P.S. I tried querying the newly created dispatch and i was able to get the child result in the connectedServiceResult, see below.
{
"query": "turn off light",
"topScoringIntent": {
"intent": "l_HomeAutomation",
"score": 1.0
},
"intents": [
{
"intent": "l_HomeAutomation",
"score": 1.0
},
{
"intent": "None",
"score": 6.6E-09
},
{
"intent": "l_Weather",
"score": 1.48148147E-10
}
],
"entities": [
{
"entity": "turn",
"type": "Device_PatternAny",
"startIndex": 0,
"endIndex": 3,
"role": ""
}
],
"connectedServiceResult": {
"query": "turn off light",
"topScoringIntent": {
"intent": "ControlDevice",
"score": 1.0
},
"intents": [
{
"intent": "ControlDevice",
"score": 1.0
},
{
"intent": "None",
"score": 3.9E-09
}
],
"entities": [
{
"entity": "light",
"type": "Device",
"startIndex": 9,
"endIndex": 13,
"score": 0.9847512
},
{
"entity": "turn off",
"type": "Operation",
"startIndex": 0,
"endIndex": 7,
"resolution": {
"values": [
"off"
]
}
},
{
"entity": "off",
"type": "Operation",
"startIndex": 5,
"endIndex": 7,
"resolution": {
"values": [
"off"
]
}
},
{
"entity": "turn",
"type": "Device_PatternAny",
"startIndex": 0,
"endIndex": 3,
"role": ""
}
]
}
}

Let me know if you are seeing issues using the newly created Dispatch app.

The error above is still happening with 1.6.9

Please reactivate this issue if you are not able to use the Dispatch app.

Tricky question as I can obviously use the Dispatch app.
So as far as I understand this issue should be closed, although it's not fixed (even though it's just a UI thing) but I can safely ignore the error for now and should not report any issue again? Well, okay then. 🤷♂

@sibbl , the child publishing error could be safely ignored as long as the dispatch app is created, trained and published.  Make sure you could use it at run time and that you could get back the child result as well.  create command failed for me before v 1.6.9.
The tool still needs to support LUIS apps that have not yet been converted to use Azure LUIS resource, unfortunately there is no way for the tool to know whether LUIS app is using Azure resource or the old authoring model.
Let me know if you are not able to use the Dispatch app at run time.


fn_hadr_backup_is_preferred_replica issue

Backup on AlwaysON without WSFC:
We are testing AlwaysOn without Windows Server Failover Clustering.
The backup return an error because the function fn_hadr_backup_is_preferred_replica is not yet compatible with this mode.
https://feedback.azure.com/forums/908035-sql-server/suggestions/32899291-fn-hadr-backup-is-preferred-replica-fails-for-clus
Issue:
SELECT sys.fn_hadr_backup_is_preferred_replica('XXXXXXXX')
Msg 35222, Level 16, State 0, Line 45
Could not process the operation. Always On Availability Groups does not have permissions to access the Windows Server Failover Clustering (WSFC) cluster.  Disable and re-enable Always On Availability Groups by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online.
To avoid this issue I changed the procedure DatabaseBackup (version 2018-07-16 ) as follow:
135: DECLARE @CurrentIsPreferredBackupReplica bit
--->  DECLARE @CurrentIsPreferredBackupReplica nvarchar(max)
1726: SELECT @CurrentIsPreferredBackupReplica = sys.fn_hadr_backup_is_preferred_replica(@CurrentDatabaseName)
--->    SELECT @CurrentIsPreferredBackupReplica = @CurrentAvailabilityGroupBackupPreference
1852: SET @DatabaseMessage = 'Is preferred backup replica: ' + CASE WHEN @CurrentIsPreferredBackupReplica = 1 THEN 'Yes' WHEN @CurrentIsPreferredBackupReplica = 0  THEN 'No' ELSE 'N/A' END
--->    SET @DatabaseMessage = 'Is preferred backup replica: ' + CASE WHEN @CurrentIsPreferredBackupReplica IS NOT NULL THEN 'Yes' WHEN @CurrentIsPreferredBackupReplica IS NULL  THEN 'No' ELSE 'N/A' END
1906: AND NOT (@CurrentAvailabilityGroup IS NOT NULL AND @CurrentBackupType = 'LOG' AND @CopyOnly = 'N' AND (@CurrentIsPreferredBackupReplica <> 1 OR @CurrentIsPreferredBackupReplica IS NULL) AND @OverrideBackupPreference = 'N')
--->    AND NOT (@CurrentAvailabilityGroup IS NOT NULL AND @CurrentBackupType = 'LOG' AND @CopyOnly = 'N' AND (@CurrentIsPreferredBackupReplica IS NULL) AND @OverrideBackupPreference = 'N')
I opened a Feature instead of Bug because this issue seem to come from Microsoft side but it has been going on for a long time.
So is it possible to have a workaround?

Is this still an issue in the latest CU for SQL Server 2017?
Do you have an open support case with Microsoft?

Heads up: another break related to sys.fn_hadr_backup_is_preferred_replica is in SQL 2017 CU 15. It's now documented in KB4498951:
Availability Group preferred replica backups
IMPORTANT
Consider the following scenario:

You are running an Availability Group on a Windows Server failover cluster.
You are using the  sys.fn_hadr_backup_is_preferred_replica  function within your backup jobs to determine whether to run a backup on the current replica.

In this scenario, the function call fails and generates the following error message:
Msg 41070, Level 16, State 1, Line 1

Configuration data for the availability group with Windows Server Failover Clustering (WSFC) resource ID '<resource ID>' is not found in the WSFC data store. The availability group may have been dropped, or a previous CREATE AVAILABILITY GROUP or DROP AVAILABILITY GROUP operation has failed. Please use DROP AVAILABILITY GROUP command to clean up previously failed operations before retrying the current operation.

This issue does not affect the backup itself. Therefore, you can work around this issue by removing the call to  sys.fn_hadr_backup_is_preferred_replica.
If you have to back up only on the preferred replica, we recommended that you do not apply Cumulative Update 15. This issue will be fixed in a future release.

Thanks for the news.
I tested the 4 options of the Availability Group Backup preferences (without underline cluster):
Primary
Secondary only
Prefer Secondary
Any Replica

[ ] Primary Node

Primary

SELECT Name AS AGname,
       cluster_type,
       cluster_type_desc,
       automated_backup_preference,
       automated_backup_preference_desc
FROM sys.availability_groups
go

AGname           cluster_type cluster_type_desc    automated_backup_preference automated_backup_preference_desc
---------------- ------------ -------------------- --------------------------- ------------------------------------------------------------
PPRADBAG01       1            none                 0                           primary

(1 row affected)

SELECT sys.fn_hadr_backup_is_preferred_replica('TESTADB05')
go

-----
1

(1 row affected)

Secondary only

SELECT Name AS AGname,
       cluster_type,
       cluster_type_desc,
       automated_backup_preference,
       automated_backup_preference_desc
FROM sys.availability_groups
go

AGname           cluster_type cluster_type_desc    automated_backup_preference automated_backup_preference_desc
---------------- ------------ -------------------- --------------------------- ------------------------------------------------------------
PPRADBAG01       1            none                 1                           secondary_only

(1 row affected)

SELECT sys.fn_hadr_backup_is_preferred_replica('TESTADB05')
go

Msg 35222, Level 16, State 0, Line 45
Could not process the operation. Always On Availability Groups does not have permissions to access the Windows Server Failover Clustering (WSFC) cluster.  Disable and re-enable Always On Availability Groups by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online.

Prefer Secondary

SELECT Name AS AGname,
       cluster_type,
       cluster_type_desc,
       automated_backup_preference,
       automated_backup_preference_desc
FROM sys.availability_groups
go

AGname           cluster_type cluster_type_desc    automated_backup_preference automated_backup_preference_desc
---------------- ------------ -------------------- --------------------------- ------------------------------------------------------------
PPRADBAG01       1            none                 2                           secondary

(1 row affected)

SELECT sys.fn_hadr_backup_is_preferred_replica('TESTADB05')
go

Msg 35222, Level 16, State 0, Line 45
Could not process the operation. Always On Availability Groups does not have permissions to access the Windows Server Failover Clustering (WSFC) cluster.  Disable and re-enable Always On Availability Groups by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online.

 Always On Availability Groups does not have permissions to access the Windows Server Failover Clustering (WSFC) cluster.  Disable and re-enable Always On Availability Groups by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online.

Prefer Secondary

SELECT Name AS AGname,
       cluster_type,
       cluster_type_desc,
       automated_backup_preference,
       automated_backup_preference_desc
FROM sys.availability_groups
go

AGname           cluster_type cluster_type_desc    automated_backup_preference automated_backup_preference_desc
---------------- ------------ -------------------- --------------------------- ------------------------------------------------------------
PPRADBAG01       1            none                 2                           secondary

(1 row affected)

SELECT sys.fn_hadr_backup_is_preferred_replica('TESTADB05')
go

Msg 35222, Level 16, State 0, Line 45
Could not process the operation. Always On Availability Groups does not have permissions to access the Windows Server Failover Clustering (WSFC) cluster.  Disable and re-enable Always On Availability Groups by using the SQL Server Configuration Manager. Then, restart the SQL Server service, and retry the currently operation. For information about how to enable and disable Always On Availability Groups, see SQL Server Books Online.

Any Replica

SELECT Name AS AGname,
       cluster_type,
       cluster_type_desc,
       automated_backup_preference,
       automated_backup_preference_desc
FROM sys.availability_groups
go

AGname           cluster_type cluster_type_desc    automated_backup_preference automated_backup_preference_desc
---------------- ------------ -------------------- --------------------------- ------------------------------------------------------------
PPRADBAG01       1            none                 3                           none

(1 row affected)

SELECT sys.fn_hadr_backup_is_preferred_replica('TESTADB05')
go

-----
0

(1 row affected)

It works “fine” on both nodes only for the Primary option.  For the Any Replica choice it seems not allowed to back up on secondary node?

Microsoft is working on a fix for the issue in CU15.
https://support.microsoft.com/en-us/help/4498951/cumulative-update-15-for-sql-server-2017#avail
When it comes to the issue with sys.fn_hadr_backup_is_preferred_replica on clusterless availability groups, is that still an issue in the latest CU?

I installed the CU15 and it works fine, no more error.

@Cedric-Diau, thank you for confirming.
Then we are just waiting for Microsoft to fix the latest issue. Hopefully that will be fixed in the next CU.

@Cedric-Diau, could you also write a comment on the User Voice item.

@olahallengren, Sorry but where is the User Voice item ?

I mean this one:
https://feedback.azure.com/forums/908035-sql-server/suggestions/32899291-fn-hadr-backup-is-preferred-replica-fails-for-clus

The fix in CU15 had a regression and got rolled back in CU16. In CU17 it finally got fixed.
https://support.microsoft.com/en-us/help/4502442/fix-sys-fn-hadr-backup-is-preferred-replica-causes-error-41005-in-sql


Fix deserialization issues in H5PYDataset

Fixes #215.
@rizar correctly identified that this was caused by H5PYDataset accessing self._external_file_handle rather than self.external_file_handle outside H5PYDataset.load.
Git blame points out this is my mistake, sorry about that!
I added this case to the serialization unit test so it's catched the next time.

LGTM!


music_assistant.common.models.errors.LoginFailed: SMB mount failed with error: mount error(115): Operation now in progress Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)

What version of Music Assistant has the issue?
2.0.7
What version of the Home Assistant Integration have you got installed?
2024.6.2
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
when I try to enter my server details i get this error:
Connection failed for the given details: SMB mount failed with error: mount error(115): Operation now in progress
Refer to the mount.cifs(8) manual page (e.g. man mount.cifs) and kernel log messages (dmesg)
How to reproduce
Attempt to mount remote share
Music Providers
Remote Share
Player Providers
n/a
Full log output

Additional information
I can use the same credentials to connect on another device.
Home assistant is using tailscale and I've tried both the tailscale and local IP.
I have removed all special characters from the share.
What version of Home Assistant Core are your running
2024.7.2
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Alternative

Under the advanced settings, mount options, have you tried adding vers=2.0 to the list of options?

just did, i have 'noserverino,file_mode=0775,dir_mode=0775,uid=0,gid=0,vers=2.0 ' but it still is not working - maybe the syntax is wrong?

Any chance you could try with the latest beta? There's a lot of stability fixes gone into it.

just did and unfortunately the issue persists

This is possibly not a MA issue. Have you googled the error?

I have, it seems like a common server mount errors but none of them worked and some diorite replicate well with this issue

Unfortunately we will have to close this soon unless you can provide additional info thtat suggests this is a MA problem as you are the only one reporting it...?

adding version=3.0 did it for me.

Hello , I adding  ,vers=2.0
and it's ok  thank's


Isomorphisms + Profiling

A bit of a weird mutant PR, but:

[x] Isomorphisms
[x] Isomorphism tests (and verification against nx.algorithms.isomorphism)
[x] Profiling infrastructure for performance and optimization

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@04936ff). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master       #7   +/-   ##
=========================================
  Coverage          ?   91.56%
=========================================
  Files             ?        3
  Lines             ?      332
  Branches          ?        0
=========================================
  Hits              ?      304
  Misses            ?       28
  Partials          ?        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 04936ff...097a4c4. Read the comment docs.


fail to build app using ns 8.2.3 and ui-image 4.1.6

demo.tar.gz
When I build android app, I get the following exception.
Gradle build...
         + applying user-defined configuration from /Users/yong/workspace/demo/App_Resources/Android/before-plugins.gradle
         + setting applicationId
         + applying user-defined configuration from /Users/yong/workspace/demo/App_Resources/Android/before-plugins.gradle

Script<EMAIL_ADDRESS>line: 25
A problem occurred evaluating script.
Cannot get property '@akylas/nativescript' on null object

Which platform(s) does your issue occur on?

Android

Please, provide the following version numbers that your issue occurs with:

➜  demo node -v
v14.17.2
➜  demo ns doctor
✔ Getting environment information

No issues were detected.
✔ Your ANDROID_HOME environment variable is set and points to correct directory.
✔ Your adb from the Android SDK is correctly installed.
✔ The Android SDK is installed.
✔ A compatible Android SDK for compilation is found.
✔ Javac is installed and is configured properly.
✔ The Java Development Kit (JDK) is installed and is configured properly.
✔ Xcode is installed and is configured properly.
✔ xcodeproj is installed and is configured properly.
✔ CocoaPods are installed.
✔ CocoaPods update is not required.
✔ CocoaPods are configured properly.
✔ Your current CocoaPods version is newer than 1.0.0.
✔ Python installed and configured correctly.
✔ The Python 'six' package is found.
✔ Xcode version 13.4.0 satisfies minimum required version 10.
✔ Getting NativeScript components versions information...
✔ Component nativescript has 8.2.3 version and is up to date.
✔ Component @nativescript/core has 8.2.4 version and is up to date.
✔ Component @nativescript/ios has 8.2.3 version and is up to date.
✔ Component @nativescript/android has 8.2.3 version and is up to date.

Please, tell us how to recreate the issue in as much detail as possible.
ns build android

@liuy97 thanks for the report and sorry for the trouble. Can you try 4.1.7 and tell me if it fixes it?

@farfromrefug , thanks a lot. I have confirmed that V4.1.7 has fixed this bug.