fuzz: Fix build

The last two builds for rhai have failed on oss-fuzz https://oss-fuzz-build-logs.storage.googleapis.com/index.html#rhai
This is my fault, I didn't properly git add things in my last PR and I also didn't configured the CI correctly, so the CI falsey reported that everything was ok. This should be main instead of master.

I tested all this locally and it's building fine again. I've also (hopefull) fix up the oss-fuzz github action in #811

@silvergasp   For reasons I don't understand, the fuzz build has been failing for months now...  and it seems that all other projects in OSS-Fuzz have been failing.
Can you possibly look into this matter?

Sure I'll take a look now.

Fixed in https://github.com/google/oss-fuzz/pull/12409
Sorry I didn't catch this earlier, I don't receive notifications for failing builds.

Strange that most of the projects have builds that are failing...

@nathaniel-brough   sorry to bother you... but some of the fuzz builds have been failing again...  not sure what it is.
https://oss-fuzz-build-logs.storage.googleapis.com/log-c636c89b-2c30-40a9-910f-3739bae67bdd.txt

Looks like it's related to code-coverage reports. So fuzzing should still be working fine, it's just that code-coverage isn't being collected. Unless you are using the coverage reports you can safely ignore that build failure.
Never the less, I'll see if I can trouble shoot and get back to you.

Great! No wonder it looks like all the builds are ok but then it still keeps telling me something is failing...


chore(deps): update common-dev-assets digest to 81754c2

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
95f6c1e -> 81754c2

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

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


[BUG] Attempt to start recording fails with too many retries

Describe the bug
Using the sample app, I set the ConnectionString in config.properties and tried to start a recording.  It always fails with the error "Retry attempts have been exhausted"
I know the connection string is fine and the passed in serverCallId is valid because if I try to start a recording after the meeting is ended, I get a different error.
I also built 1.0.0-beta.2 from the GitHub as of today and that fails too.
Exception or Stack Trace
2023-01-13 11:40:08.275  INFO 14195 --- [r-http-kqueue-1] com.azure.core.http.policy.RetryPolicy   : {"az.sdk.message":"Retry attempts have been exhausted.","tryCount":3}
com.azure.communication.callautomation.models.CallingServerErrorException: Status code 500, "{"error":{"code":"9999","message":"Unknown internal server error."}}"
	at com.azure.communication.callautomation.models.CallingServerErrorException$1.create(CallingServerErrorException.java:65)
	at com.azure.communication.callautomation.implementation.accesshelpers.ErrorConstructorProxy.create(ErrorConstructorProxy.java:57)
	at com.azure.communication.callautomation.implementation.accesshelpers.ErrorConstructorProxy.create(ErrorConstructorProxy.java:60)

To Reproduce
Invoke http://localhost:8080/startRecording?serverCallId=aHR0c...[SNIP]...OTQ2MTU5MDEyOTQ3 against the sample app
Code Snippet
serverCallLocator = new ServerCallLocator(serverCallId);

StartRecordingOptions recordingOptions = new StartRecordingOptions(serverCallLocator);
recordingOptions.setRecordingContent(RecordingContent.AUDIO_VIDEO);
recordingOptions.setRecordingChannel(RecordingChannel.MIXED);
recordingOptions.setRecordingFormat(RecordingFormat.MP4);

logger.log(Level.INFO, "Getting call recording") ;
CallRecording callRecording = this.callAutomationClient.getCallRecording() ;
logger.log(Level.INFO, "Starting recording") ;
Response<RecordingStateResult> response = callRecording.startRecordingWithResponse(recordingOptions, null);

The last line that invokes startRecordingWithResponse() is what generates the error.  I also tried the startRecording() method and that fails similarly
Expected behavior
The recording should start without an error
Screenshots
N/A
Setup

OS: Max OS X 12.6.2
IDE: Visual Studio Code
Library/Libraries: azure-communication-callautomation:1.0.0-beta.1
Java version: OpenJDK 14.0.2
App Server/Environment: Sample app MS provides using Spring Boot
Frameworks: Spring Boot

Additional context
Add any other context about the problem here.
Information Checklist
Kindly make sure that you have added all the following information above and checkoff the required fields otherwise we will treat the issuer as an incomplete report

[ x] Bug Description Added
[ x] Repro Steps Added
[ x] Setup information Added

I've been testing with just the host in the meeting.  Could this error be due to not having a second person in the meeting?  If so, should the error returned better explain what went wrong?

@juntuchen-msft could you please follow up with @dleewo


Fix xivapi not support language zh

Pull request type

[x] This is a bugfix to existing functionality

Pull request details
if only set language={i18nStore.gameLanguage} it will lead to xivapi language=zh, which is not supported by xivapi.
{"code":400,"message":"invalid request: Failed to deserialize query string: invalid or unsupported language \"zh\""}

Add a redirect to EN when using Chinese Client
const gameLanguage = i18nStore.gameLanguage === Language.CHINESE
	? Language.ENGLISH
	: i18nStore.gameLanguage

Hm, this shouldn't be possible - https://github.com/xivanalysis/xivanalysis/pull/2129/files#diff-7a4265bb108fa9584f8d2efb0b4fc2a373a4504e50bd07378a54673868e9a827R8 prevents the i18n store from exposing CN as a game language. Possibly related to local storage>


Fix memory leak in Graph

This should fix a memory leak in the Graph class.

Looks good to me. Thank you!


Add support for views

To meet complex analytical needs, it can be useful to create views and query them with SquashQL. From then on, it would be nice if squashql-codegen was able to generate definitions for these views.

(The issue was closed since squashql-codegen actually already support views: they are considered as a table like any other)


Custom Form Validation

Environment

Operating System: Darwin
Node Version:     v22.2.0
Nuxt Version:     3.12.4
CLI Version:      3.12.0
Nitro Version:    2.9.7
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      runtimeConfig, site, app, ssr, routeRules, compatibilityDate, future, devtools, extends, ui, modules, plausible, eslint
Runtime Modules<EMAIL_ADDRESS>@nuxt/ui<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>
Version
latest
Reproduction
https://stackblitz.com/edit/nuxt-ui-jnwh5u?file=app.vue
Description
Hi @benjamincanac
Hope you well.
Not sure if this is a bug, but when using an if else in custom form validation even though errors are cleared from errors[] doesnt clear ui until you re-click submit.
Additional context
No response
Logs
No response

@romhml any clues?

Not sure I understand the issue here, errors are updated after interacting with the inputs in the reproduction you provided. Errors are updated on submit or input events. What behaviour are you expecting?

Hey @romhml,
Issue I am facing is that only the single select that was interacted with is being updated on input even though in the validate function if all are equal to zero i want the message to be updated for all of them.
Basically some validation occurs on input, but it only occurs for interacted field - there are case (like when using zod refine or superrefine) that you have a set of 3 inputs that should be considered "as one validation rule" so that user gets correct feedback for those inputs.
Does that make more sense?

This is expected, we only update errors for the input that has been interacted with. If you want to tie the validation for these three inputs you have to group them under the same FormGroup element like so: https://stackblitz.com/edit/nuxt-ui-gbdc1x?file=app.vue

Hey @romhml,
Thanks for this, do get the logic - thought think that it should work even not in the same form group since then you are restricted in a form group definition for all inputs that are part of this validation. How would you set a diffrent label for each input when using this?

It won't be possible to set different label with the example I gave you. Another work around would be to use form.setErrors in the validate function to update the error of related inputs.

Hey @romhml
Yip. That is exactly what I have done @change to custom clear and setErrors.
Don't you think this should be fixed? Think using refine for eg in Zod or or in joi is super common and makes it a pain to use this form component?


use laravel echo server in react native client

I want to use laravel echo server in react native app
but I think something is wrong that I don't know what is it
I get this error in my log

undefined is not an object (evaluating 'this.connector.channel')
channel
D:\react-native\taav\node_modules\laravel-echo\dist\echo.js:750:34
componentDidMount

it is my laravel
class updateStatus implements  ShouldBroadcast
{
use Dispatchable, InteractsWithSockets, SerializesModels;

/**
 * Create a new event instance.
 *
 * @return void
 */

public $activity;
public function __construct( Activity $a)
{
    //

    $this->activity=$a;

}

/**
 * Get the channels the event should broadcast on.
 *
 * @return Channel|array
 */
public function broadcastOn()
{
    return ['channel'];
}

}

that I know my laravel server is correct because I can use correctly my socket in browser
and my react native code:
import React, {Component} from 'react';

 import Echo from "laravel-echo"
  import io from 'socket.io-client/dist/socket.io';

 export default class Activities extends Component {

constructor(props) {
    super(props)
    this.btnadd = this.btnadd.bind(this)
    this.SearchMethod = this.SearchMethod.bind(this)
    this.socket = io('http://'.concat(server).concat(':6001'), {json: false})

}
 componentDidMount() {

    var echo = window.Echo = new Echo({
        broadcaster: 'io',
        host: 'http://'.concat(server).concat(':6001')
    });

    window.Echo.channel('channel')
        .listen('updateStatus', (e) => {
            // this.additem()

        })
}

@facebook-github-bot stack-overflow


Updated tuple type hints to adhere to style guide

Fixed issue with tuples in vision augment.
Fixes: #83

Thanks!


add advanced graphql changes separate from test changes

@RunDevelopment ironically after all the discussion about "integration" tests from #2927, I realized the library I'm using that vendors Prism only uses the .tokenize method so I'm not able to use plugins anyway 😂 😭
Here's the PR for just the advanced graphql changes without any major modifications to the test suite :)
Closes #2927

Sorry for the delay @JaKXz!

the library I'm using that vendors Prism only uses the .tokenize method so I'm not able to use plugins anyway 😂 😭

I'm sorry to hear that. Coincidentally, I just opened an issue for a new hook (#2949) that would solve your problem. But this hook will likely only be added in v2.0.

I just merged a few PRs that changed a bunch of files. Let me quickly resolve the merge conflict.

@JaKXz Also, you should request your vendor to support the before-tokenize and after-tokenize hooks. These hooks are necessary for some languages to work properly. Even the new hook I proposed won't change that.

No worries, thanks for merging! :)


webDriverProxy doesn't work with http proxy and seleniumAddress configured with https

Hello,
When webDriverProxy is configured with a HTTP proxy for both HTTP / HTTPS requests, and the seleniumAddress is configured with HTTPS, protractor returns a protocol error.
Bug report

Node Version: 10
Protractor Version: ^5.4.2
Browser(s): ANY
Operating System and Version ANY
Your protractor configuration file :

exports.config = {
  seleniumAddress: "https://my-personal-grid/wd/hub",
  webDriverProxy: "http://my-proxy:80",
  specs: ["todo-spec.js"]
};

A relevant example test :

describe("angularjs homepage todo list", function() {
  it("should add a todo", function() {
    browser.get("https://angularjs.org");

    element(by.model("todoList.todoText")).sendKeys(
      "write first protractor test"
    );
    element(by.css('[value="add"]')).click();

    var todoList = element.all(by.repeater("todo in todoList.todos"));
    expect(todoList.count()).toEqual(3);
    expect(todoList.get(2).getText()).toEqual("write first protractor test");

    // You wrote your first test, cross it off the list
    todoList
      .get(2)
      .element(by.css("input"))
      .click();
    var completedAmount = element.all(by.css(".done-true"));
    expect(completedAmount.count()).toEqual(2);
  });
});

Output from running the test :

[13:20:55] I/launcher - Running 1 instances of WebDriver
[13:20:55] I/hosted - Using the selenium server at https://my-personal-grid/wd/hub
[13:20:55] E/launcher - EPROTO write EPROTO<PHONE_NUMBER>23936:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

[13:20:55] E/launcher - Error: EPROTO write EPROTO<PHONE_NUMBER>23936:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:

    at ClientRequest.<anonymous> (/protractor-example/protractor/node_modules/selenium-webdriver/http/index.js:238:15)
    at ClientRequest.emit (events.js:198:13)
    at TLSSocket.socketErrorListener (_http_client.js:392:9)
    at TLSSocket.emit (events.js:198:13)
    at errorOrDestroy (internal/streams/destroy.js:107:12)
    at onwriteError (_stream_writable.js:436:5)
    at onwrite (_stream_writable.js:461:5)
    at _destroy (internal/streams/destroy.js:49:7)
    at TLSSocket.Socket._destroy (net.js:613:3)
    at TLSSocket.destroy (internal/streams/destroy.js:37:8)
From: Task: WebDriver.createSession()
    at Function.createSession (/protractor-example/protractor/node_modules/selenium-webdriver/lib/webdriver.js:769:24)
    at Function.createSession (/protractor-example/protractor/node_modules/selenium-webdriver/chrome.js:761:15)
    at createDriver (/protractor-example/protractor/node_modules/selenium-webdriver/index.js:170:33)
    at Builder.build (/protractor-example/protractor/node_modules/selenium-webdriver/index.js:626:16)
    at Hosted.getNewDriver (/protractor-example/protractor/node_modules/protractor/built/driverProviders/driverProvider.js:53:33)
    at Runner.createBrowser (/protractor-example/protractor/node_modules/protractor/built/runner.js:195:43)
    at q.then.then (/protractor-example/protractor/node_modules/protractor/built/runner.js:339:29)
    at _fulfilled (/protractor-example/protractor/node_modules/q/q.js:834:54)
    at /protractor-example/protractor/node_modules/q/q.js:863:30
    at Promise.promise.promiseDispatch (/protractor-example/protractor/node_modules/q/q.js:796:13)
[13:20:55] E/launcher - Process exited with error code 199
npm ERR! code ELIFECYCLE
npm ERR! errno 199

Check that HTTPS protocol isn't available
This command returns an unknown protocol error :
curl --proxy "https://my-proxy:80" "https://www.google.com"

Because the proxy isn't configured with https. And in my case it's not something I can change.
Steps to reproduce the bug
Use nginx as a reverse proxy - by forwarding the http requests we don't care about the domain of the selenium address.
conf.js :
exports.config = {
  seleniumAddress: "http://non-existing-grid-but-important-path/wd/hub",
  webDriverProxy: "http://localhost:80",
  specs: ["todo-spec.js"]
};

Nginx conf file :
worker_processes 1;

events { worker_connections 1024; }

http {
    sendfile on;

    server {
        listen 80;
        server_name localhost;

        location / {
            proxy_pass         https://my-real-selenium-hub-host;
            proxy_redirect     off;
            proxy_set_header   Host $host;
            proxy_set_header   X-Real-IP $remote_addr;
            proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
            proxy_set_header   X-Forwarded-Host $server_name;
        }
    }
}

Nginx Dockerfile:
FROM nginx:alpine

COPY nginx.conf /etc/nginx/nginx.conf

Commands to run :
docker build -t proxy .
docker run -p 80:80 -d proxy
protractor conf.js

Then replace http://non-existing-grid-but-important-path/wd/hub by https://non-existing-grid-but-important-path/wd/hub to notice the bug.

And for those who can't update their proxy configuration, the "steps to reproduce the bug" section can be a workaround. A local reverse proxy and a fake selenium hub endpoint both using http.

It seems related to the selenium-webdriver library so I close this issue. You can find the issue here : https://github.com/SeleniumHQ/selenium/issues/7509


Improve error handling when attempting to upload an already succeeded DataVolume

What this PR does / why we need it:
We had to adjust some of the image-upload behavior with the addition of populators and the PVC Prime logic. This PR improves the handling of a specific error case to better report the status of the PVC.
When searching for the PVC Prime name annotation, if there's a pod succeeded annotation in the target PVC, we can safely assume it was successfully populated, so now we return a PVC already successfully populated message instead of the previous, more generic Unable to get PVC Prime name.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes # https://bugzilla.redhat.com/show_bug.cgi?id=2241658
Special notes for your reviewer:
Release note:

NONE

/lgtm
/approve

/cherry-pick release-1.0


Verify transactions in a block are well formed

Verify that transactions in blocks appear exactly as their marshaled form after unmarshaling.

At least a small PR description would be nice.

At least a small PR description would be nice.

Added a description

LGTM overall. The only thing that isn't clear yet is how we can convince ourselves that we're calling VerifyTransactionsAreWellFormed in all the right places to achieve complete mediation. I see that we call it in 3 places - how can we be sure these are the only three places?

Not only that we can't, but there is a stack of PRs pending to be reviewed that will need to be re-evaluated that we call it in different places.
The right approach would be to change the function that hashes the block to accept an entire block, and not a block data.

LGTM overall. The only thing that isn't clear yet is how we can convince ourselves that we're calling VerifyTransactionsAreWellFormed in all the right places to achieve complete mediation. I see that we call it in 3 places - how can we be sure these are the only three places?

Not only that we can't, but there is a stack of PRs pending to be reviewed that will need to be re-evaluated that we call it in different places.
The right approach would be to change the function that computes the hash of the block, to receive as parameter the entire block, not just the header.

I'll take this commit and incorporate it into my stack of PRs, here:
https://github.com/hyperledger/fabric/issues/4346
https://github.com/hyperledger/fabric/pull/4408

@denyeart we can backport it now


Django 1.7 compatibilty

#51 was my naive attempt to use django-pyodbc with 1.7b1, it seems to be more complicated...
This is what I've found so far:

A ProgrammingError: Attempt to use a closed cursor is raised on select queries.commit comment
If I replace cursor.close() with pass on django/db/models/sql/compiler.sql:820, selecting stuff in the shell works again. But it obviously needs to be fixed at django-pyodbcs side.

The use of TEST_* prefixes in the DATABASES setting is deprecated, but django-pyodbc assumes the keys exist. This makes test database creation fail.

Schema editors. Django 1.7 ships with migrations, so the BaseDatabaseWrapper defines a method schema_editor which raises NotImplementedError.

...
File "/home/jieter/.virtualenvs/pyodbc-test/local/lib/python2.7/site-packages/django/db/backends/init.py", line 546, in schema_editor
raise NotImplementedError('subclasses of BaseDatabaseWrapper may require a schema_editor() method')
NotImplementedError: subclasses of BaseDatabaseWrapper may require a schema_editor() method
    If I add a method returning a simple SchemaEditor like this:
   ```python
    def schema_editor(self, *args, **kwargs):
        "Returns a new instance of this backend's SchemaEditor"
        return DatabaseSchemaEditor(self, *args, **kwargs)

(together with a DatabaseSchemaEditor extending BaseDatabaseSchemaEditor), I get a TransactionManagementError when ./manage.py runserver:
```
...
File "/home/jieter/.virtualenvs/pyodbc-test/local/lib/python2.7/site-packages/django/db/migrations/loader.py", line 148, in build_graph
self.applied_migrations = recorder.applied_migrations()
File "/home/jieter/.virtualenvs/pyodbc-test/local/lib/python2.7/site-packages/django/db/migrations/recorder.py", line 48, in applied_migrations
self.ensure_schema()
File "/home/jieter/.virtualenvs/pyodbc-test/local/lib/python2.7/site-packages/django/db/migrations/recorder.py", line 41, in ensure_schema
with self.connection.schema_editor() as editor:
File "/home/jieter/.virtualenvs/pyodbc-test/local/lib/python2.7/site-packages/django/db/backends/schema.py", line 74, in enter
atomic(self.connection.alias, self.connection.features.can_rollback_ddl).enter()
File "/home/jieter/.virtualenvs/pyodbc-test/local/lib/python2.7/site-packages/django/db/transaction.py", line 274, in enter
"The outermost 'atomic' block cannot use "
django.db.transaction.TransactionManagementError: The outermost 'atomic' block cannot use savepoint = False when autocommit is off.

idea's?

Hi all,
I have the same error,
I use django1.7 and pyobdc on windows 7
when I try to connected to an MS Access DB, I have this error
raise NotImplementedError('subclasses of BaseDatabaseWrapper may require a schema_editor() method')
NotImplementedError: subclasses of BaseDatabaseWrapper may require a schema_editor() method
Thanks

I just got the same error on Windows 7. Which django version can correct this or which patch should I apply whith Django 1.7 ?
I use pyodbc 3.0.7.
Thanks.

Django 1.7 is not yet supported so you might try using django 1.6

I switched to django-pyodbc-azure. Works perfect with Django 1.7 and MS SQL-Server.

same problem here. django 1.7

thank you for your reply.
2015-02-10 17:54 GMT+01:00 Gordon Schultz<EMAIL_ADDRESS>
I switched to django-pyodbc-azure. Works perfect with Django 1.7 and MS
SQL-Server.
—
Reply to this email directly or view it on GitHub
https://github.com/lionheart/django-pyodbc/issues/52#issuecomment-73736447
.

For "Issue 1" - A ProgrammingError: Attempt to use a closed cursor, I believe this is just a behavior difference between pyodbc and other database backends.  If you look at the Django trunk for file django/db/models/sql/compiler.py, it has these two snippets:
849 result = cursor_iter(
850     cursor, self.connection.features.empty_fetchmany_value,
851     self.col_count
852 )
853 if not self.connection.features.can_use_chunked_reads:
854     try:
855         # If we are using non-chunked reads, we return the same data
856         # structure as normally, but ensure it is all read into memory
857         # before going any further.
858         return list(result)
859     finally:
860         # done with the cursor
861         cursor.close()

and the cursor_iter() definition :
1129 def cursor_iter(cursor, sentinel, col_count):
        [...]
1134     try:
1135         for rows in iter((lambda: cursor.fetchmany(GET_ITERATOR_CHUNK_SIZE)),
1136                          sentinel):
1137             yield [r[0:col_count] for r in rows]
1138     finally:
1139         cursor.close()

849 creates an iterator with a built-in close() function.  858 invokes the iterator to completion, calling that close() function, and 861 invokes the close() function a 2nd time.
So I think the solution might be to wrapper the cursor's close() function to silence the ProgrammingError exceptions resulting from closing a pyodbc cursor more than once:
diff --git a/django_pyodbc/base.py b/django_pyodbc/base.py
index 747f36e..47099ae 100644
--- a/django_pyodbc/base.py
+++ b/django_pyodbc/base.py
@@ -367,6 +367,12 @@ class CursorWrapper(object):
         self.last_params = ()
         self.encoding = encoding

+    def close(self):
+        try:
+            self.cursor.close()
+        except Database.ProgrammingError:
+            pass
+
     def format_sql(self, sql, n_params=None):
         if not self.driver_supports_utf8 and isinstance(sql, text_type):
             # Older FreeTDS (and other ODBC drivers?) don't support Unicode yet, so

Let me know if this is the correct path and whether I should create a pull request for it.

@RossRogers this looks like a solid path to pursue. :+1: on a PR.

#78

I don't understand if this problem was solved or not.
I'm upgrading from Djano 1.6 to 1.7.
Python 2.7.6.
pyodbc 3.0.7
django_pyodbc 0.2.5
Ubuntu 12.04
Everything went as planned except for accessing remote database tables (MySQL and Ms-SQL Server).  All of the tables are configured "managed-false".  When I try to access the table I get:
RuntimeError: Conflicting 'bugview_deferred_description_disposition_divisioaf59cb28117de5eb6ddfea0476dab601' models in application 'nvbugsdw': <class 'bug_metrics.models_bugs.BugView_Deferred_Description_Disposition_Divisioaf59cb28117de5eb6ddfea0476dab601'> and <class 'bug_metrics.models_bugs.BugView_Deferred_Description_Disposition_Divisioaf59cb28117de5eb6ddfea0476dab601'>

To fix address that I was instructed to makemigrations on the remote (not managed by Django) DB (see http://stackoverflow.com/questions/34620588/conflicting-models-in-application-with-external-database-tables).  So I tried and got:
NotImplementedError: subclasses of BaseDatabaseWrapper may require a schema_editor() method

Any suggestions?  I've been stuck for a couple of days.
Thanks in advance for any help.

It looks like this class is somehow getting included twice:
bug_metrics.models_bugs.BugView_Deferred_Description_Disposition_Divisioaf59cb28117de5eb6ddfea0476dab601

Do you have the bug_metrics "app" installed twice?

No.  Problem appeared when I upgrade from 1.6 to 1.7.  It happens only on tables that are defined on remote MS-SQL Servers.  The model.py file containing the definition is incldued in multiple other files (views, commands, etc.) but the application is only loaded once.
I have 11 apps.  2 access remote DBs the other 9 access local MySQL DB tables.  Only the two apps that access the remote DB display this problem.

So, the table BugView_Deferred_Description_Disposition_Divisioaf59cb28117de5eb6ddfea0476dab601 has Meta field managed=False like?
class Meta:
    managed = False

Did it transition from managed to un-managed?
I've seen the Django migration system get screwed up before.  If you don't think you'll need to rollback any migrations ( you can always create a forward migration at a later date that undoes the edits), then I would try:

Nuking all files in the bug_metrics/migrations directory

Nuke all rows in table django_migrations

Recreate an initial migration with:
  python manage.py makemigrations bug_metrics

Then fake out the migration, as it is already in a known state:
  python manage.py migrate --fake bug_metrics

One more thought: If you want to root cause this, I'd launch a debugger like winpdb:
Then put this line:
import rpdb2; rpdb2.start_embedded_debugger('foo')

in file django/apps/registry.py right before the RuntimeError is thrown:
raise RuntimeError(
                "Conflicting '%s' models in application '%s': %s and %s." %
                (model_name, app_label, app_models[model_name], model))

Then:

run your command that throws the error
wait for it to hang ( right before that error)
launch winpdb GUI
File->Attach, password 'foo'
Click up the stack and see how it got to that error.

Don't know if this makes any difference or not:
The application bug_metrics has 3 models*.py files.  Two of them define local database tables.  The third one defines classes for managed = False tables that were created by hand (may have used inspectdb tool).  So the bug_metrics applicaiton has a mix of tables.
I migrated bug_metrics (cleared out the migrations directory of everything but init.py, ran makemiragtion and migrate) that created the FAKE migrations.
The "bugview" table ("bug_metrics.models_bugs.BugView_...") has always been manged = False.
class BugView(models.Model):
    BugId            = models.BigIntegerField(primary_key=True)
    Module           = models.CharField(max_length=128, null=False)
    Severity         = models.CharField(max_length=50, null=False)
    Disposition      = models.CharField(max_length=64, null=False)
    Division         = models.CharField(max_length=64, null=False)
. . .
class Meta:
    app_label = 'nvbugsdw'
    managed   = False
    db_table  = 'bugview'

Ok.  And I'll try the debugger approach too.

Is that app_label= 'nvbugsdw' necessary?  If you nuke that line, does this issue disappear?

Same issue with or without it.

Interesting.  I'd definitely go the debugger route then.  If you haven't done that before, it is extremely powerful when root-causing issues.

I did notice one other oddity.  When I run
./manage.py runserver --nothreading <IP_ADDRESS>:8081

With print statements in manage.py, manage.py seems to be run twice.  Is that expected?

manage.py will reload everything anytime a file in any loaded apps is changed.

Thanks for the debug tip.  Found this:
In my view I define:
context_object_name = 'open_bugs'
model = BugView
I override get_queryset() to retrieve the list of record I want:
bv = BugView()
sql = bv.get_open_bugs_for_user_sql(self.filter_username)
bugs = BugView.objects.raw(sql)
I then iterate over the list to cont certain states, etc.
for bug in bugs:
if bug.State == ...
I pass the "bugs" results to context:
get_context_data(self, **kwargs):
    context = super(UserBugsView, self).get_context_data(**kwargs)

Then  in the template I iterate over the passed in "open_bugs" (which I have already iterated over once):
{% for bug in open_bugs %}

{{ bug.BugId }}
...

Looking at dist-packages/django/apps/registry.py, line 210-ish
def register_model(self, app_label, model):
    # Since this method is called when models are imported, it cannot
    # perform imports because of the risk of import loops. It mustn't
    # call get_app_config().
    model_name = model._meta.model_name
    app_models = self.all_models[app_label]
    print "-----> app_label  = "+app_label
    print "-- --> model_name = "+model_name
    print "- - -> app_models = "+str(app_models)
    if model_name in app_models:
        raise RuntimeError(
            "Conflicting '%s' models in application '%s': %s and %s." %
            (model_name, app_label, app_models[model_name], model))

(I added the print lines)
When the views code counts the bugs I see in the trace:
-----> app_label  = nvbugsdw
-- --> model_name = bugview_deferred_description_disposition_divisioaf59cb28117de5eb6ddfea0476dab601
- - -> app_models = OrderedDict([('bugview', <class 'bug_metrics.models_bugs.BugView'>)])

and then when the open_bugs gets to the template I see in the trace:
-----> app_label  = nvbugsdw
-- --> model_name = bugview_deferred_description_disposition_divisioaf59cb28117de5eb6ddfea0476dab601
- - -> app_models = OrderedDict([('bugview', <class 'bug_metrics.models_bugs.BugView'>), ('bugview_deferred_description_disposition_divisioaf59cb28117de5eb6ddfea0476dab601', <class 'bug_metrics.models_bugs.BugView_Deferred_Description_Disposition_Divisioaf59cb28117de5eb6ddfea0476dab601'>)])

which raises the error.
This is the same code I ran under 1.5 and 1.6 Django.
Thoughts?

That code you just pasted is not the latest 1.7 minor release number.  sudo pip install django 1.7.11.  If you do pip install 1.7 it literally installs 1.7, not the highest minor number.  To find the versions, do :
pip install yolk # might need sudo pip ...
yolk -V django

The latest 1.7 minor/bug release number is 1.7.11.

UNBELIEVABLE!!!!
Thank you so much for noticing that.  It works now.

That has bit me before too.  I think pip install django==1.7 should pick the highest bug release as well.  Oh well.
Yay team.

Yes, I just assumed it would.  Didn't some general say something about assumption is the mother of all ..."
Again, thanks.

I believe we have generic 1.7 support on the trunk as I am using it (shame on me).  For specific 1.7 bugs, please file a new ticket.

@RossRogers nope, just tried with 1.7 and ran into the exact same errors commented at the beginning of this thread (dating from 2014)

Connor,
Did you run against 1.7 or the patched up version 1.7.11?  What does pip freeze | egrep '(django|odbc)' give you?

If you can make an S.S.C.C.E and indicate which specific issue of the 4 listed in the first post is still surfacing, that would be helpful.

@RossRogers Looking back on this now, my issues are all related to migrations and the lack of a SchemaEditorClass.  After searching through the repo, I'm assuming migrations are not supported.
inspectdb worked for me (so far, I haven't actually tried retrievals yet).


extract qctstatements

Hi
can this package be used to extract qcstatement from an eidas certificate ?
let me know
thanks
Charandeep

Please don't cross-post without closing the original issue https://github.com/nginx/njs/issues/641

Sorry for the confusion. Closing this as duplicate now


Add Bun as Examples for Package Managers

Existing documentation URL(s)

https://developers.cloudflare.com/pages/get-started/c3/#create-a-new-application
https://developers.cloudflare.com/pages/framework-guides/deploy-a-hono-site/#create-a-new-project

What changes are you suggesting?
I'm suggesting adding bun as an additional example for package managers in the documentation. Currently, the docs provide examples for npm, yarn, and pnpm, but not for bun. Including bun would help users who prefer this package manager to install dependencies more easily.
Additional information
No response

Hi @aninibread @tanushree-sharma — Could you confirm that we should add this? I would need to check with my team, but it looks like bun is supported by the component we use, so it could be pretty straight forward.

We should be consistent across all of docs. Offer npm, yarn, pnpm, and yes, bun, in every example that uses a JS package manager.


[Bug] Ayaneo Pocket S crashing

On android 11
The app loads but when you try to sign in it crashes. works fine on my logitech g cloud

please provide crash info in Logcat


Actor Heartbeat Metric

In what area(s)?

/area runtime

/area operator

/area placement

/area docs

/area test-and-release

Describe the feature
Problem
The lack of visibility into actors' placements, reduces the ability to diagnose resource utilization, hotspot, and other issues in k8s clusters.
Without knowing where actors or specific actor types are running, it's hard to monitor the allocation and manage/tune resources in dynamic environments.
Dapr Placement service holds the placement data where actors are hosted, but the table is not accessible for outside use.
The information in the Host object includes the following:
name: <IP_ADDRESS>:50002
load: 1
entities: "MyActor"
id: "my-actor-server"

While host information may point to the pod, it makes it more complex to map to the pod name when most of the metrics use pod names.
Having a pod name helps to troubleshoot as it can be seen almost anywhere unlike host IP.
Possible use cases

See when and where actors and/or actor types reporting and track if they are alive
Mapping of actor types to pods and resource usage in metric dashboards
Alerts on specific actor types exceeding the resources allowed
Find hotspot issues for actor types and infrastructure bottlenecks hosting these actors
Tracking actor's hearbeat on the timeline and be able to map where actors were running

Additional benefit, aggregating a metric will allow building placement table without complexity of exposing API and doesn't require use of internal gRPC service that requires authentication as was discovered in PR https://github.com/dapr/dapr/pull/6212 which was reverted.
Provides alternative fix for https://github.com/dapr/dapr/issues/6033
Proposed solution
Create the Actor Heartbeat metric when receiving Host in PlacementServer and report for each actor type reported by the actor.
Metric name: dapr_placement_actor_heartbeat_timestamp
Tags: app_id, actor_type, host_name, pod_name
Value: timestamp in seconds since epoch
POC
Example of metric reported by placement service
dapr_placement_actor_heartbeat_timestamp{actor_type="PingPong",app_id="server-ping-pong",host_name="<IP_ADDRESS>:50002",pod_name="server-ping-pong-648f467c5b-6bbm8"}<PHONE_NUMBER>

Example Grafana panel with actor placements

Release Note

RELEASE NOTE: ADD New Actor heartbeat metric dapr_placement_actor_heartbeat_timestamp

Yes. We need this ASAP for better actor visibility.


Aborted (core dumped) error occurs on release mode in Ubuntu 16.04 distribution

I have used the following piece of code
`               ThreadPool  tp(THREAD_POOL_NAME);
TaskManager tm(tp);
            Poco::AutoPtr<MyClass1> ptrA = new MyClass1;
            tm.start(ptrA.duplicate());
            Poco::AutoPtr<MyClass2> ptrB = new MYClass2;
            tm.start(ptrB.duplicate());

            tp.joinAll();
            ptrA->release();
            ptrB->release();

`
When used in Ubuntu 16.04, aborted (core dumped) occurs.
When I run gdb I get the following error :

[New Thread 0x7ffff2022700 (LWP 5437)]
[New Thread 0x7ffff1821700 (LWP 5438)]
[Thread 0x7ffff1821700 (LWP 5438) exited]
[Thread 0x7ffff2022700 (LWP 5437) exited]
Thread 2 "npt" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff405c700 (LWP 5376)]
0x00007ffff5880a40 in _int_free (av=0x7fffe4000020, p=, have_lock=0) at malloc.c:4003
4003       malloc.c: No such file or directory.

The result of core analysis:
gdb -c core

[New LWP 5288]
[New LWP 5286]
[New LWP 5289]
[New LWP 5290]
Core was generated by `./npt'.
Program terminated with signal SIGABRT, Aborted.
#0  0x00007ffad3d26428 in ?? ()
[Current thread is 1 (LWP 5288)]

Which I assume is a segmentation fault due to probable double free/delete.
When I removed the release commnands ptrA->release();, ptrB->release(); the code worked without crashes.
When I tried to debug the code in debug mode and the release commands active the code also worked without crashes.
thanks,
Dimitris

Hi thanks for reporting this. But to make sure, I didn't see the scenario
of how aws cpp sdk related to this code. Can you supply more information?
Such as version of sdk, service you used.
On Wed, Jun 21, 2017 at 1:49 AM dkarantonis<EMAIL_ADDRESS>wrote:

I have used the following piece of code
` ThreadPool tp(THREAD_POOL_NAME);
TaskManager tm(tp);
        Poco::AutoPtr<MyClass1> ptrA = new MyClass1;
        tm.start(ptrA.duplicate());
        Poco::AutoPtr<MyClass2> ptrB = new MYClass2;
        tm.start(ptrB.duplicate());

        tp.joinAll();
        ptrA->release();
        ptrB->release();

`
When used in Ubuntu 16.04, aborted (core dumped) occurs.
When I run gdb I get the following error :
[New Thread 0x7ffff2022700 (LWP 5437)]
[New Thread 0x7ffff1821700 (LWP 5438)]
[Thread 0x7ffff1821700 (LWP 5438) exited]
[Thread 0x7ffff2022700 (LWP 5437) exited]
Thread 2 "npt" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff405c700 (LWP 5376)]
0x00007ffff5880a40 in _int_free (av=0x7fffe4000020, p=, have_lock=0) at
malloc.c:4003
4003 malloc.c: No such file or directory.
The result of core analysis:
gdb -c core
[New LWP 5288]
[New LWP 5286]
[New LWP 5289]
[New LWP 5290]
Core was generated by `./npt'.
Program terminated with signal SIGABRT, Aborted.
#0 0x00007ffad3d26428 in ?? ()
[Current thread is 1 (LWP 5288)]
Which I assume is a segmentation fault due to probable double free/delete.
When I removed the release commnands ptrA->release();, ptrB->release();
the code worked without crashes.
When I tried to debug the code in debug mode and the release commands
active the code also worked without crashes.
thanks,
Dimitris
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/aws/aws-sdk-cpp/issues/581, or mute the thread
https://github.com/notifications/unsubscribe-auth/ADTsCLcAdPNK_fB6FNVUEtlIKsYNTDp7ks5sGNklgaJpZM4OApQJ
.

--
Best Regards!
Liang.
Software Engineer
Game Developer

Hi, sorry for this. It was intended to be sent to Poco c++ library


Added CryptoPhages

Name: CryptoPhages
Description: CryptoPhages are here to infect the Cardano blockchain! This unique pixel art consisting of bacteriophages will brighten your day!
Link:   https://cryptophages.com
Source: null
Tags:

nft

@rcmorano Thanks in advance!

Closing due to not enough approvals for a long time. Please note that showcase projects need to provide a unique value from existing showcase items, feel free to join the discussion here: #243


ENH: Implemented Dirichlet-multinomial distribution (#16810)

Reference issue
Closes gh-16810
What does this implement/fix?
Implements Dirichlet-multinomial distributions. With this class, the user can get the pmf, mean, variance, and co-variance.
Additional information

Thanks for the PR. It would help the review if you were to fill out the templated sections in the description.

Thanks for the PR. It would help the review if you were to fill out the templated sections in the description.

Done.

Hi @MatteoRaso do you plan to finish this? There are some comments waiting for you.

@mdhaber Yes. I'm really sorry that I've been AWOL for the last 2 weeks, but I had some stuff come up that I needed to focus on. I've already made most of the changes suggested by you and @melissawm, but I still need to get it to support broadcasting.

No problem @MatteoRaso - if you need help or want to discuss further feel free to reach out here or on the SciPy slack 😄

I've made the requested changes, but I don't know how to get rid of the "1 change requested" notice.

Just wondering if there's been any updates.

I also replaced the tests with stronger ones. The source of the reference values was not included, and it's important to test against some independent source of information.

There are a few things remaining:

[ ] raise when shape parameters have too many dimensions (since I removed vectorization)
[ ] I need to check some edge cases manually and play around with the distribution
[ ] optional, probably follow-up PR  - add support for n=0
[ ] optional, probably follow-up PR add RVS method (as demonstrated in test_moments)
[ ] optional, follow-up PR - add back vectorization and all associated tests

Lint might fail. IIUC everyone is having trouble checking lint locally right now due to a change in flake8.

Refguide failure would be fixed by suggestion above. Other failures are unrelated.

@MatteoRaso I think this is getting close. Please take a look at the changes to see if this is ready from your perspective. We can add vectorization over shape parameters in a follow-up PR.
@tirthasheshpatel since I've done a lot with this one, would you be able to take a look?

I saw that you removed the broadcasting, but you didn't explain why in the commit message.

I saw that you removed the broadcasting, but you didn't explain why in the commit message.

Vectorization over shape parameters is optional for multivariate distributions, and testing these properly would have required additional work that I did not want to do at this time.
Here's what I'd recommend for this distribution going forward, if it sounds good to you.

@tirthasheshpatel or another maintainer will review and merge
Before continuing with this distribution, I'd suggest that you complete distribution entropy work started in gh-17774. The suggestion to tackle one distribution per PR is a good one because $N$ independent PRs are almost always easier to review/merge than one PR that is $N$ times as big.  I'd also recommend opening only one PR at a time. By working through all the common pitfalls in the first PR and avoiding them in subsequent PRs, we save the work of making similar comments and corrections on several PRs at once.
When that is done, we can continue with the enhancements mentioned in https://github.com/scipy/scipy/pull/17211#issuecomment-1404435894, each in a separate PR, if they have not already been completed. (I might do the vectorization in the meantime.)

The implementation looks good. Although, I'd suggest adding a rvs method. Without that, the distribution is not very interesting.

Yes. I did that in a test and it's one of the suggested enhancements above for a separate PR. The problem is that it will be slow and cumbersome without NumPy 1.22 (vectorization over multinomial shape parameters), but that should be the minimum supported version before the next release.

Thanks @tirthasheshpatel! Do the changes resolve the concerns?
@MatteoRaso Typically we'd squash everything into a single commit when we merge, but we should preserve your original version with the vectorization separately, so I planned to rebase this into two commits. The plan is to squash the original commits up to 903989824a62a2b4569328da5c770cd857619d85 into one with you as author, and squash the remaining commits into one with me as author. That would require a force-push to your branch. After you have a chance to backup whatever you need, may I do the rebase and force-push? Does this look ready to you?

@tylerjereddy according to the support table of NEP 29, the minimum supported version of NumPy should be 1.22 after Jun 23, 2023. Do you think SciPy 1.11 will release after that with 1.22 as the minimum supported version? We need a feature from 1.22 to easily perform random variate sampling.

Don't we normally go a bit slower than NEP29 for that? I think we're at 1.19.5 at the current 1.10.0 stable release. If Ralf thinks it is "ok" I don't have any strong objection, but I do think we tend to bump slowly.

IIRC with the last versions we tried to slowly catch up with the NEP. Maybe we can consider be on par now.

Thanks @tylerjereddy. Good to know. Well, we don't need the feature for this PR, so it's OK for now.
@MatteoRaso also this feature needs an email to the mailing list (e.g. like this) before it can be merged.

The only concern I have is that the name of _check_dirichlet_multinomial_parameters might now be inaccurate, since it checks the support as well now. If everybody else is okay with the name though, then yeah, I'm ready to rebase. That being said, I can't actually access your example email because of spotty internet, so I'll need a day or 2 to send a message to the mailing list.

Only alpha and n are "shape parameters" of the distribution (in the mathematical sense), but alpha, n, and x are parameters of the method of the distribution object (in the programming sense). From the latter perspective, the name seems apt.
I'll go ahead and do the rebase, but I'm open to suggestions for renaming that function in the meantime.

Backed up this branch exactly as it is:
https://github.com/mdhaber/scipy/tree/dir_mul_backup

@MatteoRaso I created mdhaber/scipy#96 to show what the rebase will look like before I force-push to this branch.
The first commit is your commits e39f137f7f591975a174745d277e4fd320026124 - 903989824a62a2b4569328da5c770cd857619d85 squashed into one (with you as the author). The diff of that commit vs main should look like the diff of your commits in this PR.
The second commit is the remaining commits squashed into one (with me as the author). You can verify that the overall diff in that PR should look like the overall diff in this PR.
If it looks to you like the rebase went well, I'll reset the dir_mul branch to the branch in that pr dir_mul_update and force push. Then this PR will be ready to merge. LMK if it looks right.

Okay, I sent an email to the mailing list asking if anybody had any strong opinions about this. If we don't get any negative feedback, it should be good to go.

Okay, I sent an email to the mailing list asking if anybody had any strong opinions about this. If we don't get any negative feedback, it should be good to go.

Yes. I should mention that the last sentence of the email may have given the impression that the merge was imminent and that the request for feedback was made as a formality. I'd suggest that future emails to the mailing list be phrased to appear more welcoming. Also, the conditions under which the PR can be merged should be left to the maintainer who will be merging the PR - the absence of negative feedback about a PR is not always sufficient.
That said, this distribution was requested by a user, and a maintainer welcomed a PR, which indicated that the feature looked like a good fit for SciPy. I, a second maintainer, have worked on the PR and therefore have reviewed it thoroughly. Were I not so involved in writing the code, I would merge it on the basis that the distribution appears to be important, the implementation seems accurate, the tests are sufficient, and the code quality/style is appropriate. A third maintainer, @tirthasheshpatel, has approved the PR. It has been over a week since an email was sent to the mailing list and, admittedly, implicit approval from the mailing list has been sufficient for many other PRs lately, especially when there is so much other support.
Tirth, thanks for your review! After you approved, I rebased on main so that this could be split into two commits, but you can see that there are no substantial differences between the rebased commits and my backup of the original version. How would you like to proceed?

All the changes look good @mdhaber! I think we can merge. Let me know if you have any other changes in mind, otherwise, we can merge.

No other changes from me. Thanks!

Merging. Thanks for the PR @MatteoRaso! This is a really useful addition especially for people doing Bayesian statistics. If you are up for adding another conjugate pair, feel free to add Normal Inverse-Wishart or Normal Inverse-Gamma distribution (see gh-6528). I can help review, feel free to ping me if you create a PR @MatteoRaso!

Thanks for the PR @MatteoRaso!

No problem.

feel free to add Normal Inverse-Wishart or Normal Inverse-Gamma distribution

Sure, I'll take a stab at that in a week's time or so.

@MatteoRaso Thanks for your enthusiasm, but please let's finish the entropy PRs before opening a new PR.

@MatteoRaso Thanks for your enthusiasm, but please let's finish the entropy PRs before opening a new PR.

Of course, that's why I said I'd think about it in a week or so.


[iOS] Mutator clips should not be applied to clipped elements that are scrolled "offscreen"

Run the example from https://github.com/lucalooz/flutter_ads_list_perf , for this one I made sure that I could have one ad on screen that is scrolled off the bottom. The ListView is wrapped in a clip rect, which will apply a mutator if the platform view intersects it partially.
If you scroll the ad slightly off the bottom of the screen, the clip mutator still applies. This could be skipped, as the native view will be clipped by the screen anyway.

I'm working on this one.
cc @hellohuanlin

This was fixed by making the clipping much cheaper!


Restructuring repo

Restructuring folders and simplifying top level.
Removing obsolete folders/files.

The README.md under root/samples needs to be moved to root/samples/DevTestLabs/
Other than that, LGTM.

@ianhays, thank you. I'm doing a subsequent pass for all the documentation. I will catch it there.


Objects are not correctly initialized when using constructor with OuterXml

Description
When creating SDK objects with OuterXml string, properties which should be set may be uninitialized (null).
Information

DocumentFormat.OpenXml Version: 1.10.0

The same code works with version 2.9.1
Repro
var style = new DocumentFormat.OpenXml.Wordprocessing.Style("<w:style w:type=\"paragraph\" w:styleId=\"Heading1\" xmlns:w=\"http://schemas.openxmlformats.org/wordprocessingml/2006/main\">\r\n  <w:name w:val=\"heading 1\" />\r\n  <w:basedOn w:val=\"Normal\" />\r\n  <w:next w:val=\"Normal\" />\r\n  <w:link w:val=\"Heading1Char\" />\r\n  <w:qFormat />\r\n  <w:pPr>\r\n    <w:keepNext />\r\n    <w:keepLines />\r\n    <w:numPr>\r\n      <w:numId w:val=\"3\" />\r\n    </w:numPr>\r\n    <w:spacing w:before=\"320\" />\r\n    <w:jc w:val=\"left\" />\r\n    <w:outlineLvl w:val=\"0\" />\r\n  </w:pPr>\r\n  <w:rPr>\r\n    <w:b />\r\n    <w:color w:val=\"187EC9\" />\r\n    <w:spacing w:val=\"4\" />\r\n    <w:kern w:val=\"32\" />\r\n    <w:sz w:val=\"32\" />\r\n  </w:rPr>\r\n</w:style>");
Assert.NotNull(style.StyleId); // StyleId is null here, until some operation is done which actually parses the XML

Observed
Parsing of the supplied XML is not performed when accessing certain properties.
Expected
All getters should assert that the provided XML has been parsed.

Thanks for the report. I found the issue and have a fix. Apparently, our tests never validate this - good catch!

Great! It was a bit puzzling because this manifested itself as a Heisenbug; the evaluation of the properties by the debugger would trigger the initialization code...

@avonwyss  I've pushed the fix into an updated NuGet package - update to 2.10.1 and it should work now. Thanks for the report!


Allow non-RAII semaphore usage, fix semaphore guard lifetime issue

SemaphoreGuard now borrows Semaphore. This ensures that guard will not outlive the semaphore itself.
Separate methods give and take added to semaphore. There is a use case for task synchronization where first task gives a semaphore while second one takes it.

Looks good to me, thanks!


Unable to execute fHDHR with plugin enabled

[2022-01-17 03:53:01,007] NOOB - Loading  fHDHR v0.9.3-beta, fHDHR_web v0.9.2-beta

Checking and Installing Core Dependencies.

Traceback (most recent call last):

  File "/config/fHDHR/main.py", line 38, in <module>

    sys.exit(run.main(SCRIPT_DIR, fHDHR_web, deps))

  File "/config/fHDHR/fHDHR/cli/run.py", line 175, in main

    returned_code = start(args, script_dir, fHDHR_web, deps)

  File "/config/fHDHR/fHDHR/cli/run.py", line 134, in start

    return run(settings, logger, db, script_dir, fHDHR_web, plugins, versions, web, scheduler, deps)

  File "/config/fHDHR/fHDHR/cli/run.py", line 40, in run

    fhdhr = fHDHR_OBJ(settings, logger, db, plugins, versions, web, scheduler, deps)

  File "/config/fHDHR/fHDHR/__init__.py", line 48, in __init__

    self.fhdhr.origins = Origins(self.fhdhr)

  File "/config/fHDHR/fHDHR/origins/__init__.py", line 34, in __init__

    self.origin_selfadd()

  File "/config/fHDHR/fHDHR/origins/__init__.py", line 66, in origin_selfadd

    self.origins_dict[method] = self.fhdhr.plugins.plugins[plugin_name].Plugin_OBJ(plugin_utils)

  File "/config/fHDHR/plugins/fHDHR_plugin_origin_nextpvr/origin/__init__.py", line 14, in __init__

    self.login()

  File "/config/fHDHR/plugins/fHDHR_plugin_origin_nextpvr/origin/__init__.py", line 50, in login

    sid = self.get_sid()

  File "/config/fHDHR/plugins/fHDHR_plugin_origin_nextpvr/origin/__init__.py", line 61, in get_sid

    initiate_url = '%s/service?method=session.initiate&ver=1.0&device=fhdhr' % self.nextpvr_address

AttributeError: 'Plugin_OBJ' object has no attribute 'nextpvr_address'

Indeed nextpvr_address member doesn't look to be part of the object when get_sid() gets called.
config.ini has the following added in it

[nextpvr]
address = nextpvr
port = 8866
addrssless = false
pin = 1234
sid = none

nextpvr plugin freshly cloned from master

Please look at https://github.com/fHDHR/fHDHR_plugin_origin_NextPVR/pull/6
I haven't been using this specific plugin for a long time (I prefer tvheadend over nextpvr), but this would have been broken for a very long time!
Not even sure how ssl=false became addrssless=false in the readme, but the nextpvr_address property issue is totally my fault, so sorry about that.
give main branch another pull, and let me know if that works for you.

Issue is resolved thank you.
Altough I might still stick to TVHeadend as well. Using NextPVR to handle tuners seems to introduce even more delay when selecting a channel in Plex!


Add ETCC token

项目资料：
白皮书地址：https://came.oss-cn-hongkong.aliyuncs.com/etcc/public/file/ETCC.pdf
项目基本情况：
根据上述阐述，本项目团队基于区块链技术开发了ETCC项目，ETCC是一个基于区块链技术打造的去中心化汽车生态服务平台。ETCC平台通过去中心化的区块链网络链接汽车厂商、后市场服务商和消费者，通过技术手段解决汽车后市场中存在的问题。平台的服务方向包括以下三个方面：
使用区块链技术使汽车服务的价值完全数字化。
提高汽车后市场的透明度，提升用户的体验性。
结合物联网技术实现汽车服务产业链的链接。
ETCC充分应用了区块链的技术思维，让全球的汽车厂商、服务商和消费者都能享受到科技带来的进步，每一个主体都可以在ETCC上快捷方便地进行消费支付，安心地享受汽车产品和服务带来的价值。用户所有的信息传输、资产交易和资金分配等活动，都将受到区块链技术的保护和支持。
转账所需 Gas Limit（对 ERC-20 项目方）：60000

Project background:
Project basic information:
According to the above description, the project team developed the ETCC project based on the blockchain technology, which is a decentralized vehicle ecological service platform based on the blockchain technology. ETCC platform links automobile manufacturers, post market service providers and consumers through decentralized blockchain network, and solves the problems in the automotive post market through technical means. The service direction of the platform includes the following three aspects:
Use blockchain technology to completely digitize the value of automobile service.
Improve the transparency of the automotive aftermarket and enhance the user experience.
Combine Internet of things technology to realize the link of automobile service industry chain.
ETCC makes full use of the technical thinking of blockchain, so that the global automobile manufacturers, service providers and consumers can enjoy the progress brought by science and technology, and each subject can quickly and conveniently pay for consumption on ETCC, and enjoy the value brought by automobile products and services at ease. All information transmission, asset transaction, capital allocation and other activities of users will be protected and supported by blockchain technology.
Recommended Gas Limit (For ERC-20 project teams) for transaction:60000

非常抱歉，请参考教程提交完整的PR，并完善Json中相应的字段内容，


Integration with other build tools

Looks pretty cool :-)
Many of our widgets are react based, or have some other kind of bundler, or build process that does transpilation,  tree shaking, minifying and possibly inlining.  I can't quite see how I could use this package to bootstrap that process.
How would I go about doing that?

You'd want to look at the core bundler project. This is just the initializer. https://github.com/carafe-fm/carafe-bundler

Actually, if you're talking about bundle-specific build process, maybe I was too hasty in pointing over there. The initializer only bootstraps a project structure so that a bundle's sources are split out in a useful way. You should be able to update the package.json file to support any pre-build process, so long as that process ends with the src/ directory containing the bundle source files:

config.json
data.json
meta.json
preview.jpg
template.carafe

As long as you build out those files, either through manual editing, or some other tooling, you can then take advantage of the validator, bundler, etc.

Also, the path and names of the source files are configurable if you need to change them. This is the default package.json
{
  "private": true,
  "name": "carafe-bundle-template",
  "version": "0.0.0",
  "scripts": {
    "validate": "validate-carafe-bundle -b ",
    "import": "extract-carafe-bundle -b ",
    "watch": "render-carafe-source",
    "watch-port": "render-carafe-source -p ",
    "build": "compile-carafe-bundle",
    "push": "compile-carafe-bundle -f"
  },
  "devDependencies": {
    "@carafe-fm/bundler": "^1.0.0"
  },
  "carafe": {
    "templateFilename": "src/template.carafe",
    "configFilename": "src/config.json",
    "dataFilename": "src/data.json",
    "metaFilename": "src/meta.json",
    "previewFilename": "src/preview.jpg"
  }
}

So obviously you can configure the bundle source files to be named whatever you like at the end of your build process.

Another way of thinking about it is for existing bundle projects, you don't need the initializer. You can just add the elements from the package.json file above as needed, and incorporate the bundler into an existing project.

why do I need a template.carafe?  What does that do for me?

is "template.carafe" just your "index.html" loader?

is "template.carafe" just your "index.html" loader?

Right, the reason we didn't use the .html suffix is that it's not valid html yet. It's a template with the bookended merge fields in it. Obviously the bundler could be configured with "templateFilename": "src/template.html", or any file extension and I'm certainly open to the idea of changing the default. We took the idea of using a new file extension from other templating systems. See examples from other templating systems such as .twig, .latte, .mustache

I  would probably not use the template as a template.  I probably would just use WebPack, and the template options it has.  I could build to that file I suppose.
Speaking of webpack, Is there a reason you built your own WebPack Dev Server?  It feels like I can do everything I need with WebPack, WebPack Dev Server and some plugins?

I think I see why you wanted something other than WebPack.  Webpack works ok, but you'd need to restart the server every time just to compile data and config into the HTML.

Yeah, we actually started with WebPack, but it made the whole thing way more complicated.

BTW, the other place custom compiled code can go is into the config, if you want to keep the template clean. E.g.
{
    "$schema" : "https://carafe.fm/schema/draft-01/config.schema.json#",
    "customPackage": {
        "category": "Local JavaScript Packages",
        "help": "Custom React package that is generated by Webpack.",
        "isData": false,
        "label": "My React Package",
        "type": "JS Snippet",
        "value": "<theMinifiedJs>"
    }
}

so how do you deal with transpilation, or other bundling options?

ok I get it now....    I can make it work by using webpack to watch my code, transpile it to the temlate.carafe and the carafe dev server takes over from there.


[BUG]: Test Issue 27

Bug Description
N/A
Logs
N/A
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce
N/A
Expected Behavior
N/A
CSM Driver(s)
N/A
Installation Type
No response
Container Storage Modules Enabled
No response
Container Orchestrator
N/A
Operating System
N/A

/sync


check_parent fix

The signature for check_parent was not updated along with the rest of emails.py. This fixes it.
Tests need to be fixed.

Failed on a google drive issue.


Build is broken due to gwihlidal/ k-mem-rs#54

Won't build because the Ash APi changed.

Published 0.14.1 which removes vk-mem-rs as a dependency


Added py.typed file and modified the setup.py files

Change Description
As the issue #905 wanted to add missing py.typed in published packages in order to support mypy/pyright type checking, I've added py.typed files in all the three libraries presidio-analyzer , presidio-anonymizer and presidio-image-redactor.
Issue reference
This PR fixes issue #905
Checklist

[ ] I have reviewed the contribution guidelines
[ ] I have signed the CLA (if required)
[ ] My code includes unit tests
[ ] All unit tests and lint checks pass locally
[ ] My PR contains documentation updates / additions if required

@microsoft-github-policy-service agree

/azp run

Do I need to make any changes @omri374 in the code?

Hi @Ashhar-24, thanks for this! I don't think so, but we'll check internally. I ran mypy after this change and there are a few issues that it raised. We'll discuss it internally and get back to you. The CI is failing due to a different problem, sorry about that.

@omri374 can you please add a hacktoberfest-accepted label so that this PR gets counted as a successful-PR for me in the hacktoberfest programm.

@omri374 one last thing, how much time will it take to get this PR merged, like in order to merge this PR requires At least 2 approving reviews .


Investigate proposed alternatives to the existing message generation pipeline.

In this months WG meeting, I discussed some painpoints with our current message generation pipeline, and some potential alternatives or changes.
The Problem
Rust does not have a stable ABI, and wants to compile all of the source code and dependencies source code, when compiling a crate. This is fundamentally what pushes us to have such a complex message generation pipeline.
Potential Solutions
I have some ideas that may help alleviate some of this complexity. These ideas are not listed in any order of preference.
Automatically upload ROS 2 messages to crates.io as semver'd packages.
Cargo bakes in semver for crates, but thankfully all ROS 2 message packages have semver versions. Perhaps we could automatically generate and upload crates when new versions of ROS 2 message packages have been published. If we are able to have letters before numbers, then we could in theory have versions like version = "jazzy.*", in our Cargo.toml files. This would alleviate some complexity when it came to upstream message packages, but doesn't change the user story for custom message packages.
Leverage a crate for "plugins"
The abi_stable seems to provide some Rust-to-Rust FFI plugin system. If memory serves this is similar to what we do for rclcpp messages where building the message package, generates a shared library, that downstream packages then dynamically link to.
Restricting a ros2 workspace to have a single cargo workspace
The additional constraints that a cargo workspace provides would potentially allow us to do things like generating message source code on demand from a build script. Of course, this reduces the flexibility of how an end user could organize their source code.
Collecting all upstream ROS 2 messages in a single crate gated with cargo features
This is not my idea, this is from @esteve. Tracking issue for this idea at https://github.com/ros2-rust/ros2_rust/issues/394.

None of these ideas are perfect, and we have still only done a very high level investigation into all of them. While this investigation is on going, we are in parallel working to improve documentation for our existing message generation pipeline https://github.com/ros2-rust/ros2_rust/issues/401.

Automatically upload ROS 2 messages to crates.io as semver'd packages.
I took a look at the semver crate, which is the crate that implement Cargo's interpretation of Semantic Versioning. So the original idea I had proposed is unfortunately not supported.
This sample code will panic
mod tests {
    use semver::Version;

    #[test]
    fn ros_distro_ver() {
        // The rolling branch on common_interfaces uses this specific tag.
        // It may be helpful if users could specify `version = "rolling.*"`
        // This way, if we had the generated ros2_rust messages up in crates.io,
        // end users can just worry about distros. This is similar to what
        // ROS users do today. Track a distro, and occasionally update it with
        // `apt upgrade`.
        let rolling = Version::parse("rolling.5.4.1").unwrap();
    }
}

There is also the added complication of the generated code actually being a combination of two version numbers. One from rosidl_generator_rs and rosidl_runtime_rs, and the other being from upstream ROS, the version numbers associated with the actual .idl files.
I treat rosidl_generator_rs and rosidl_runtime_rs as having the same version because I do not think it is realistic at the moment to have code generated without also knowing the runtime it'll be used with.
We could represent this combination of versions with the semver crate,
let rolling = Version::parse("5.4.1+rust.0.4.1").unwrap();

but now we cannot upload another crate with version 5.4.1+rust.0.5.0.
There are other crates out there that deal with this kind of dual version dilema. For example, take a look at libgit2-sys. This crate maintains many different versions of libgit2 as build metadata.

Crate Version
libgit2 Version

0.17.0
1.8.1

0.16.2
1.7.2

0.15.2
1.6.4

For this reason, I don't think this approach alone, will yield the results we want, unless we are willing to introduce a custom semver schema for ROS distros. This would have to be something like a major version 0 semantically resolves to the rolling distro, etc.
# Gives us the latest rolling (and latest rosidl_*_rs bindings...)
[dependencies.std_msgs]
version = "0.*"

# Gives us the latest jazzy (and latest rosidl_*_rs bindings...)
[dependencies.std_msgs]
version = "1.*"

❌  This is an unintuitive approach for us, as we'd need users to be more aware of the rosidl_*_rs version or our own mapping from a major version to a distro, than the distro name, or the upstream version. ❌

There should still be more discussion around ways to improve the message generation story. There are more avenues to explore. I will continue to deep dive into this


location of pre-built binaries

readme.md says: "The quickest way to get set up is to download the latest binary from https://github.com/itsmewes/gotp/releases"
that url returns 404 error for me.

Hi @gregoryaburk
This is what you should be seeing at the url. I have tried going to https://github.com/itsmewes/gotp/releases in Firefox (Private window) and Chrome (not logged in) and was able to see this page.

What happens when you click on the releases header link? Where does that take you to?

Hi @gregoryaburk
I looked around and I hadn't added the links correctly in markdown. I have updated the links and they should be working now. Thank you for pointing this out.


Added option to install Qemu Guest Agents

Added option to install Qemu Guest Agents:
[custom]
install_qemu_ga=False
If set to True, it will download and install the Qemu Guest
Agents from Fedora website. The base path for the agents is
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-qemu-ga/qemu-ga-win-<IP_ADDRESS>-3.el7ev/
The downloaded MSI will be chosen depending on the architecture of the
image, x86 or x64.
For example, on x64 images, the following MSI installer will be
downloaded and used:
https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-qemu-ga/qemu-ga-win-<IP_ADDRESS>-3.el7ev/qemu-ga-x64.msi
By default, the imaging tools will not install the Qemu Guest
Agents.
The MSI will install two services on the Windows image:

QEMU-GA
QEMU Guest Agent VSS Provider

The Qemu Guest Agents are useful if the Windows instance runs
on OpenStack (KVM hypervisor is required).
If the Windows instance is managed by OpenStack, runs on KVM and
QEMU-GA service is running, the user password can be changed using
the OpenStack Nova command:
nova set-password
Requirement1: if the nova command fails, the instance might enter an error
state and you need to reset the instance state:
nova reset-state  --active
Requirement: the Glance image needs to modified in the following way,
BEFORE the instance gets created:
glance image-update <image_id> --property hw_qemu_guest_agent=True
--property os_admin_user=Admin --property os_type=windows
os_admin_user is the user that will have the password changed.
Defaults to user 'root'. If 'os_type' property is set
to  'windows', the default user is 'Administrator'.
If you modify the required Glance image properties after you created
the instance, the nova set-password will not function.

:white_check_mark: Build windows-openstack-imaging-tools 1.0.213 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/c01388f13c by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.214 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/f9ecb502a5 by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.216 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/7d65d76dff by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.217 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/ce09b8dbdc by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.218 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/edbcea227f by @ader1990)

:x: Build windows-openstack-imaging-tools 1.0.219 failed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/f09fd7ecaa by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.220 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/0824a05f63 by @ader1990)

lgtm

looks good. Just one comment.

@AlekseyChudov I saw that you need the qemu guest agents in https://github.com/AlekseyChudov/windows-kvm-imaging-tools. It would be great if you could review this PR in case you need it.

@AlekseyChudov I saw that you need the qemu guest agents in https://github.com/AlekseyChudov/windows-kvm-imaging-tools. It would be great if you could review this PR in case you need it.

Good feature. I have no additional comments.


Bug: Queries with a negative timespans don't fail

This request has createdAt-start 2017-06-01 and createdAt-end 2017-03-31:
curl -g "https://api.dc01.gamelockerapp.com/shards/eu/matches?filter[playerNames]=shutterfly&filter[gameMode]=casual_aral,blitz_pvp_ranked&sort=createdAt&filter[createdAt-start]=2017-06-01T00:00:00.000Z&filter[createdAt-end]=2017-03-31T23:59:99.999Z" -H "Authorization: Bearer $APIKEY" -H "X-TITLE-ID: semc-vainglory" -H "Accept: application/vnd.api+json"

The date range is more than 28 days, and end < start. It should fail with an error, but instead, it returns data from 2017-06-01 onwards.

Confirmed, this is a bug.  Right now we check that it's < 28 days, but not also >0 days.
Low priority, but great find!

This issue was moved to gamelocker/platform#9


fix pss signing server signing

Description
The signing server adapter always uses the PKCS1-V1_5 Algorithm constant to call the signing server instead of using the configured algorithm.
Please include a summary of the changes and the related issue. Please also include relevant motivation and context. List any dependencies that are required for this change.
What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[ ] 🎇 Restructuring
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents

Related Issue # (issue)
Closes # (issue)
Fixes # (issue)

Remove if not applicable

Screenshots

Added tests?

[ ] 👍 yes
[ ] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help
[ ] Separate ticket for tests # (issue/pr)

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Added to documentation?

[ ] 📜 README.md
[ ] 🙅 no documentation needed

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

tested - works as intended


Launch ManageIQ K8s Operator with images from private Registry

Dear all@ManageIQ,
I was trying to start the Kubernetes Operator for ManageIQ with all pods pulling images from a private Container Registry (for Security reasons and better Version Control). So I tagged all images that originally came from docker.hub/manageiq accordingly and pushed the to my own registry.
But at he end I was not able to customize manageiq.org_v1alpha1_manageiq_cr.yaml in a way that would allow me to use my private registry across all pods.
e.g.:

spec.webserverWorkerImage => enables me to specify fqdn plus namespace of my registry plus image-name. And if I do so, indeed the pod gets started upon the image from my own registry

but ...

spec.orchestratorImageTag => just enables me to specify a tag and it seems to me that pulling from docker.hub is somehow hard-code

Am i right, or is there a way to completely switch to another registry? Did I miss something?
Thanks in advance and best regards, Marcel.

Pretty sure we have a way to do this, because we leverage it elsewhere.  @bdunne ?

Hi @bdunne
do you think there is a way to implement this?

See baseWorkerImage, httpdImage, kafkaImage, memcachedImage, orchestratorImage, postgresqlImage, uiWorkerImage, webserverWorkerImage and zookeeperImage in https://github.com/ManageIQ/manageiq-pods/blob/master/manageiq-operator/deploy/crds/manageiq.org_manageiqs_crd.yaml
You can use the fully qualified Image for each of those, for example: registry.example.com/my_namespace/image_name:tag

Hi all,
I hadn't got the chance to work on that issue on my side for quite a while. But now - finally - I picked up work again and I can state that everything works fine. All images are now pulled from a private registry.
Thanks a lot! Best regards, Marcel.


[Datasets] s3 presigned url fails?

Are we downloading the data from s3 immediately? I am creating presigned URLs that should last long enough, but my model run failed after a while...
2023-07-24 21:34:49,770 INFO [train_llm_engine] [train_llm_engine.py:113] - run_id: ft-civestsdoujg03t1akcg, job_status: RUNNING
...
2023-07-24 22:39:14,368 INFO [train_llm_engine] [train_llm_engine.py:113] - run_id: ft-civestsdoujg03t1akcg, job_status: RUNNING
2023-07-24 22:40:14,750 INFO [train_llm_engine] [train_llm_engine.py:113] - run_id: ft-civestsdoujg03t1akcg, job_status: FAILURE

Get events:
(Pdb) FineTune.get_events('ft-civestsdoujg03t1akcg')
GetFineTuneEventsResponse(events=[LLMFineTuneEvent(timestamp=1690238353.925053, message='Unable to read dataset from s3.', level='error')])

If we're continuously reading from s3 would be better to download up front

Current fine-tune logic downloads the data from s3 immediately. I just attempted a fine-tune with an S3 publicly signed url and it worked. I'd double check that the url used here could be opened in your browser.
In any case, I would now recommend using the Files API to iterate with private CSV data.


Handle the armed status better

Blink allows users to arm/disarm individual cameras. This is pretty useful for inside and outside cameras, for instance.
The armed information in the JSON however, merely indicates whether the system is armed, not whether the camera itself is armed. This value, which is the same as blink.arm, does not indicate whether the camera has motion detection enabled.
In the JSON, the true status information lies in the 'active' key. The value can be 'armed', 'disarmed' or 'disabled'. I believe this field has a lot more value. Therefor I store the active state in self._status and return a boolean based on whether the camera is actually recording when motion is detected. I've also added the status property to obtain the real value.

Great! Any chance you could hack this into the next home assistant release? :)

Cool, I might hack up a custom_component in the meanwhile (although I'm generally lazy) and send some patches.


Reg\Operations - Internal User can see Operation grid

Description:
As an internal user, I can see all of the operations that have been registered
Acceptance Criteria:
Given I am on the BCIERS dashboard
When I click Operations
Then I am brought to the operations grid
Figma
Development Checklist:

[ ] Checklist item
[ ] Checklist item
[ ] Checklist item
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[ ] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:
Dependencies

Blocked by
Blocking

@zoeyli-46  could you please update the Figma link? It's currently linked to an Archived frame

its updated

Based on discussion with the team, this has already been implemented. Closing this ticket.


Non convergence

Even with very high tolerance values, this script does not lead to a convergent M.O. solve:
using SurfaceFluxes
using Thermodynamics
using RootSolvers
using StaticArrays

using CLIMAParameters: AbstractEarthParameterSet
struct EarthParameterSet <: AbstractEarthParameterSet
end
FT = Float64
earth_param_set = EarthParameterSet()
T_atmos = 268.0
u_atmos = 2.0
q_atmos = 0.0
h_atmos = 30.0
ρ_atmos = 1.13
q_sfc = 0.0
T_sfc = 273.0
ts_sfc = Thermodynamics.PhaseEquil_ρTq(earth_param_set, ρ_atmos, T_sfc, q_sfc)
ts_in = Thermodynamics.PhaseEquil_ρTq(earth_param_set, ρ_atmos, T_atmos, q_atmos)

state_sfc = SurfaceFluxes.SurfaceValues(FT(0), SVector{2, FT}(0, 0), ts_sfc)
state_in = SurfaceFluxes.InteriorValues(h_atmos, SVector{2, FT}(u_atmos, 0), ts_in)

# State containers
kwargs = (; state_in, state_sfc, z0m = 1e-2, z0b = 1e-3)
sc = SurfaceFluxes.ValuesOnly{FT}(; kwargs...)
conditions = SurfaceFluxes.surface_conditions(
earth_param_set,
sc,
SurfaceFluxes.UniversalFunctions.Businger(); tol = RootSolvers.SolutionTolerance(1.0))

@yairchn @charleskawczynski we think this is because of the ρ difference here.

These density values should different!
If you need to estimate them we could use the existing T_sfc and T_atmos to get two densities. With h_atmos =30.0 you can use hydrostatic balance to assume one density and estimate the other:
ρ=ρₛexp(-z/H) with H = 7km; z = h_atmos

But what happens when buoyancy is 0? I found a note under Eq. 30 in the SurfaceFluxDesignDoc that this still needs to be addressed 🤔

This is how the FMS deals with it, in case it's useful.

These density values should different! If you need to estimate them we could use the existing T_sfc and T_atmos to get two densities. With h_atmos =30.0 you can use hydrostatic balance to assume one density and estimate the other: ρ=ρₛexp(-z/H) with H = 7km; z = h_atmos

this may be an silly question, but can the density at two different heights in the atmosphere at the same horizontal location not be equal by a physical law? can it ever arise that rho_sfc = rho_atmos, even just for a moment?

These density values should different! If you need to estimate them we could use the existing T_sfc and T_atmos to get two densities. With h_atmos =30.0 you can use hydrostatic balance to assume one density and estimate the other: ρ=ρₛexp(-z/H) with H = 7km; z = h_atmos

this may be an silly question, but can the density at two different heights in the atmosphere at the same horizontal location not be equal by a physical law? can it ever arise that rho_sfc = rho_atmos, even just for a moment?

@kmdeck - yes it could happen that the density is vertically uniform but it is much less likely than a uniform potential temperature.

This is how the FMS deals with it, in case it's useful.

You mean by coding it in fortran 😉
It is not clear to me in this code what is defined as neutral, Δθ ≈ FT(0) or Δρ ≈ FT(0) I am guessing the former but definitely not both. So the same issue might arise there

Haha, there's a time and a place for Fortran 😏 . And yes they use Δθ ≈ FT(0) for bstar. And thanks for the pointers to the docs. I'll check them out!

Note that using SF.jl for variable transfer coefficients still breaks when using SF.ValuesOnly at times of neutral conditions due to the division by zero buoyancy flux during neutral conditions. Options were discussed with Akshay (using a total enthalpy flux, or having a conditional statement like the FMS). We will come back to this issue after the first AMIP, which will use constant transfer coefficients.

Note that using SF.jl for variable transfer coefficients still breaks when using SF.ValuesOnly at times of neutral conditions due to the division by zero buoyancy flux during neutral conditions. Options were discussed with Akshay (using a total enthalpy flux, or having a conditional statement like the FMS). We will come back to this issue after the first AMIP, which will use constant transfer coefficients.

this PR should solve this
https://github.com/CliMA/SurfaceFluxes.jl/pull/36

On a roll, Yair! 🎉

@kmdeck @LenkaNovak Has this been fixed?

I think this has been fixed. I copied the non convergence case to #62 in case there is still a problem.


Updated partners and backers

Preview link:
https://vega-3kaui9pyq-vegaprotocol.vercel.app/community/


Remote server in [Stopped] state after Eclipse restart (issue TOOLS-2736)

Hi,
This pull request addresses issue TOOLS-2736 in OxygenTank
I believe it is SSL issue, so I added empty hostname verifier on SSL context when starting the tread.
Steps to reproduce the issue:

Install Eclipse (eclipse-jee-neon-2 in my case)
Install all plugins from http://product-dist.wso2.com/p2/developer-studio-kernel/4.1.0/esb-tools/releases/5.0.0/
add remote server on localhost (ESB 5.0.0 in my case)
deploy CAR file (with esb proxy)
everything ok so far, but restart the Eclipse
=> remote server is starting for a while, but eventually is in [Stopped] state

Steps to solve the issue:

compile from this fork
Install Remote Carbon plugin from jar wso2-developer-studio-tooling-platform-p2-4.1.0-201702162155.zip
Restart the Eclipse
=> Remote Carbon Servier is in [Started] state

Regards,
David

Current devstudio-tooling-platform master branch supports Eclipse Mars. Hence, closing the PR.


Parameter to MergeFrom() must be instance of same class when building images from docker-build/build.sh

After build images from source using FATE-builder/docker-build/build.sh, building stage can succefully finish, but couln't submit job when starting the fate fluster using custom images. building image step as follow
1、Clone source code and checkout v1.8.0 version
git clone repo-url --recursive-submodule && git checkout v1.8.0  && git submodule update

2、Excuting building process using follow command.
export TAG=1.8.0-release
cd FATE-Builder-ROOT/docker-build/ && sh build.sh all

After build successfully, starting FATE cluster by docker-compose, then submit toy example. Following error will throws.
Fully exception stacks:
Traceback (most recent call last):
  File "/data/projects/fate/fateflow/python/fate_flow/scheduler/federated_scheduler.py", line 278, in federated_command
    federated_mode=federated_mode)
  File "/data/projects/fate/fateflow/python/fate_flow/utils/api_utils.py", line 78, in federated_api
    dest_party_id=dest_party_id, json_body=json_body, api_version=api_version, overall_timeout=overall_timeout)
  File "/data/projects/fate/fateflow/python/fate_flow/utils/api_utils.py", line 162, in federated_coordination_on_grpc
    overall_timeout=overall_timeout)
  File "/data/projects/fate/fateflow/python/fate_flow/utils/grpc_utils.py", line 49, in wrap_grpc_packet
    _src = proxy_pb2.Topic(name=job_id, partyId="{}".format(src_party_id), role=FATE_FLOW_SERVICE_NAME, callback=_src_end_point)
  File "/opt/app-root/lib/python3.6/site-packages/google/protobuf/internal/python_message.py", line 552, in init
    _ReraiseTypeErrorWithFieldName(message_descriptor.name, field_name)
  File "/opt/app-root/lib/python3.6/site-packages/google/protobuf/internal/python_message.py", line 477, in _ReraiseTypeErrorWithFieldName
    raise exc.with_traceback(sys.exc_info()[2])
  File "/opt/app-root/lib/python3.6/site-packages/google/protobuf/internal/python_message.py", line 550, in init
    copy.MergeFrom(new_val)
  File "/opt/app-root/lib/python3.6/site-packages/google/protobuf/internal/python_message.py", line 1314, in MergeFrom
    _FullyQualifiedClassName(msg.__class__)))
TypeError: Parameter to MergeFrom() must be instance of same class: expected basic_meta_pb2.Endpoint got basic_meta_pb2.Endpoint. for field Topic.callback

FATE-Builder does not support building FATE v1.8. Please refer to this to build FATE v1.8.
https://github.com/FederatedAI/FATE/tree/v1.8.0/build/docker-build

FATE-Builder does not support building FATE v1.8. Please refer to this to build FATE v1.8. https://github.com/FederatedAI/FATE/tree/v1.8.0/build/docker-build

Hi @owlet42
Thanks for your very much.
I try to use the doker-build script which mentioned from you. The result is same as the issue described.
I am not sure, should I need to re-genereted all protobuf file before build images?


CM-31904 - Add cycode annotator for all registered languages; fix scan results sharing between projects

it fixes a lot of problems with detection annotation including SCA lock files of all other package systems installed as 3d party plugins; fix data model edge case
so at the end, we have: shared annotator across all app; scan results per project

do not merge. now we should track what psi file was already annotated with the same scan results. because one file could be associated with many languages. it will call the annotator many times

i moved fix to another PR https://github.com/cycodehq/intellij-platform-plugin/pull/42


VNode factory

We could at least provide a VNode.apply(s: String). Furthermore consider AsVNode like AsVDomModifier and a corresponding VNode.apply[T : AsVNode]. This allows for nicer integration of custom vnodes and their creation.

No, actually StringVNode is not a VNode. And I do not see the use case for this typeclass anymore. So, I am closing this one again.
Feel free to reopen if you think this would be beneficial.


Sunstone should permit to select several groups without using All

Description
Today, Sunstone permit to choose only one group or All, it could be very interersting to select several groups
Use case
How are you going to use this new feature? Why do you need it?
I'm part of several groups and having the ressources of all the groups I belong always displayed became annoying.
In our OpenNebula, we have resources available to all users (golden images, shared networks) and resources dedicated per groups:

every user is member of the group users
resources for all users are chgrp users to permit each user to use them

I'm member of 6 groups:

users
dev
stagging
production
projectA
projectB

I want to be able to display only resources of groups users and production (hiding everything else)
Interface Changes
In Sunstone, the Groups selection should became a checkbox with All/None options instead of actual single choice.
Additional Context
I tried to play with labels but:

they are not cumulative, selecting label users and then label production will only display resources labelled production
there are no global labels definition to tag images, network, templates the same way and labels are not restricted to groups

Progress Status

[ ] Branch created
[ ] Code committed to development branch
[ ] Testing - QA
[ ] Documentation
[ ] Release notes - resolved issues, compatibility, known issues
[ ] Code committed to upstream release/hotfix branches
[ ] Documentation committed to upstream release/hotfix branches

Another idea on top of this could be to force a password authentication to enable some groups to make sure users know what they do. And in addition, the possibility to forget some selected groups at logout.
This way, when I select production I'm asked for a password (don't mess with prod) and when I logout + login this group is not automatically selected to avoid the I forgot this group was selected and broke something case.
Thanks.


Workflow features

Features for assigning entries to users, grouping entries in batches etc, marking the status of entries (new, in progress, finished etc.) ...

Some of this is already doable with the flagging feature.
For everything else, we need to start by understading better what kinds of workflow features lexicographic projects actually need.


Add gRPC framework

gRPC is a modern, open source, high-performance remote procedure call (RPC) framework that can run anywhere. gRPC enables client and server applications to communicate transparently, and simplifies the building of connected systems.
Official repository: https://github.com/grpc/grpc
Used by:

Square
Netflix
CoreOS
Cockroach Labs
Cisco
Carbon3D
University of Wisconsin–Madison
Juniper Networks

Thanks!


Missing license

"yarn license ls" shows that package.json is missing a valid license.
Could you please include a valid license? Thanks

#6


Add optional branch to ModuleID

Allow an Ivy branch to be set on the project's module, as well as on dependencies.
This is a work in progress, which for now adds the branch: Option[String] to ModuleID while preserving backwards-compatibility, but the plan is to fix up the whole of sbt so that it's aware of branches where relevant.
Other changes planned:

change the default Ivy patterns to include the ([branch]/) after the module name

Closing in favor of #1994


Single slide

I was just wondering if the fix for a single slide has been included in version 0.4.2. Currently, if i only have a single slide, this is completely hidden on page load. The content is output to html but visually i can't see anything. This relates to the closed issue #4.

Hi there,
had you the to fix this issue? Or do we have some workaround for this?
thank you

Hi the issue still seems to exist. Is there a possibility to fix it or to write a workaround?
Thank you very much

I did have the same issue. I've fixed it adding line 132:
// hack bug inspiration zoom
if (that.size() === 1) {
that.$container.css({
display: 'none',
margin: '0',
padding: '0',
listStyle: 'none',
//position: 'relative',
height: '100%'
});
}
else {
that.$container.css({
display: 'none',
margin: '0',
padding: '0',
listStyle: 'none',
position: 'relative',
height: '100%'
});
}


This is an unnecessary question

Your work is excellent, and I have a question: Will the current reconstruction work develop into generating videos from sparse viewpoints? Or is it more focused on generating videos with physical properties?

Hello, thank you for your interest in our work. I'm not quite sure what you mean, if "generating videos from sparse viewpoints" means generating video with a diffusion model directly from sparse viewpoints, and "generating videos with physical properties" means first reconstructing the underlying 3D scene with a representation such as 3DGS, and then synthesis novel views, then both methods have their own pros and cons. The reconstruction method allows for a better understanding of the 3D world and synthesises more consistent views. However, diffusion methods can better hallucinate unseen parts of the scene, which is great.

Yes, I would like to know: Can reconstruction and video generation be combined? Or can they mutually benefit each other?

Yes, reconstruction may be used to improve the consistency of the diffusion model, [here]](https://drexubery.github.io/ViewCrafter/) is an example. The generated multiview can be utilized for reconstitution, such as the Sora example in our paper.

Thanks for your detailed explanation, which helped me clarify my doubts.


When there are two selects on the one page, they use the options of just one of them

Ionic version:  (check one with "x")
[ ] 1.x
[ x] 2.x
I'm submitting a ...  (check one with "x")
[ x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
When I have a page with two selects, they both show the options of the second select.
Expected behavior:
They should show their own options
Steps to reproduce:
Just have two selects on the one page
See http://plnkr.co/edit/mi0OCw
Related code:
Each of the select below will show B1, B2
     <ion-content padding>
        <ion-select >
           <ion-option >A1</ion-option>
          <ion-option >A2</ion-option>
      </ion-select>

      <ion-select>
           <ion-option >B1</ion-option>
          <ion-option >B2</ion-option>
         </ion-select>
      </ion-content>

Other information:

Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):
Your system information:

 ordova CLI: 6.5.0
Ionic Framework Version: 2.0.1
Ionic CLI Version: 2.2.1
Ionic App Lib Version: 2.2.0
Ionic App Scripts Version: 1.0.0
ios-deploy version: Not installed
ios-sim version: Not installed
OS: Windows 10
Node Version: v6.9.4
Xcode version: Not installed

After also posting for a workaround, there seems to be one as mentioned at this post.. https://forum.ionicframework.com/t/multiple-selects-on-the-same-page-share-the-same-options/80393
So not a big issue at all (as is easily fixed)

Hello, thanks for using Ionic! So as our docs show ion-select should always be wrapped inside an ion-item, which is what that forum post shows too. I am going to close this for now, but if you run into any more issues with this feel free to comment and i will re-open.


Syntax highlight

Having some issues with this branch I hope someone can help lol

it works, but should wait a bit for merge some cleanup needed

added a class to create editors and moved stuff around to make it nice
All I need now is to remove modes and themes not needed


New Feature: add KeysOfType

This PR implements KeysOfType<A extends object, B> which will return all the keys where the value extends a given one.
This can be useful to implement things like Clean<T> which removes from an object the keys where the value is never
type Clean<T> = Pick<T, Exclude<keyof T, KeysOfType<T, never>>>
type TestClean = Clean<{a: string, b: never}> // => {a: string}

another real world usage is to discriminate functions and value properties in objects:
type ObjectFunctions<T> = Pick<T, KeysOfType<T, Function>>
type ObjectProperties<T>= Pick<T, Exclude<keyof T, KeysOfType<T, Function>>>

Thanks @mattiamanzati