works in debug but throws Unhandled in release build

Nice work - much appreciated however..
Compiling in release mode throws this:
Unhandled Exception: LateInitializationError: Local 'result' has not been initialized.
it seems to be related to the following line in builders/widget.dart
WidgetsBinding.instance!.addPostFrameCallback(_captureImage);
Symptom: perfect in debug, blank screen in release
Fixing it is beyond my skill as I'm just learning.
E/flutter (18180): #2      _PageTurnWidgetState._captureImage (package:ssv1/book_screen/builders/widget.dart:40)
E/flutter (18180): #3      SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1144)
E/flutter (18180): #4      SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1090)
E/flutter (18180): #5      SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:998)
E/flutter (18180): #6      _rootRun (dart:async/zone.dart:1354)
E/flutter (18180): #7      _CustomZone.run (dart:async/zone.dart:1258)
E/flutter (18180): #8      _CustomZone.runGuarded (dart:async/zone.dart:1162)
E/flutter (18180): #9      _invoke (dart:ui/hooks.dart:167)
E/flutter (18180): #10     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:259)
E/flutter (18180): #11     _drawFrame (dart:ui/hooks.dart:126)
E/flutter (18180):
E/flutter (18180): [ERROR:flutter/lib/ui/ui_dart_state.cc(186)] Unhandled Exception: LateInitializationError: Local 'result' has not been initialized.
E/flutter (18180): #0      LateError._throwLocalNotInitialized (dart:_internal-patch/internal_patch.dart:208)
E/flutter (18180): #1      RenderObject.debugNeedsPaint (package:flutter/src/rendering/object.dart:2112)
E/flutter (18180): #2      _PageTurnWidgetState._captureImage (package:ssv1/book_screen/builders/widget.dart:40)
E/flutter (18180): #3      SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1144)
E/flutter (18180): #4      SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1090)
E/flutter (18180): #5      SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:998)
E/flutter (18180): #6      _rootRun (dart:async/zone.dart:1354)
E/flutter (18180): #7      _CustomZone.run (dart:async/zone.dart:1258)
E/flutter (18180): #8      _CustomZone.runGuarded (dart:async/zone.dart:1162)
E/flutter (18180): #9      _invoke (dart:ui/hooks.dart:167)
E/flutter (18180): #10     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:259)
E/flutter (18180): #11     _drawFrame (dart:ui/hooks.dart:126)
E/flutter (18180):
E/flutter (18180): [ERROR:flutter/lib/ui/ui_dart_state.cc(186)] Unhandled Exception: LateInitializationError: Local 'result' has not been initialized.
E/flutter (18180): #0      LateError._throwLocalNotInitialized (dart:_internal-patch/internal_patch.dart:208)
E/flutter (18180): #1      RenderObject.debugNeedsPaint (package:flutter/src/rendering/object.dart:2112)
E/flutter (18180): #2      _PageTurnWidgetState._captureImage (package:ssv1/book_screen/builders/widget.dart:40)
E/flutter (18180): #3      SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1144)
E/flutter (18180): #4      SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1090)
E/flutter (18180): #5      SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:998)
E/flutter (18180): #6      _rootRun (dart:async/zone.dart:1354)
E/flutter (18180): #7      _CustomZone.run (dart:async/zone.dart:1258)
E/flutter (18180): #8      _CustomZone.runGuarded (dart:async/zone.dart:1162)
E/flutter (18180): #9      _invoke (dart:ui/hooks.dart:167)
E/flutter (18180): #10     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:259)
E/flutter (18180): #11     _drawFrame (dart:ui/hooks.dart:126)
E/flutter (18180):
E/flutter (18180): [ERROR:flutter/lib/ui/ui_dart_state.cc(186)] Unhandled Exception: LateInitializationError: Local 'result' has not been initialized.
E/flutter (18180): #0      LateError._throwLocalNotInitialized (dart:_internal-patch/internal_patch.dart:208)
E/flutter (18180): #1      RenderObject.debugNeedsPaint (package:flutter/src/rendering/object.dart:2112)
E/flutter (18180): #2      _PageTurnWidgetState._captureImage (package:ssv1/book_screen/builders/widget.dart:40)
E/flutter (18180): #3      SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1144)
E/flutter (18180): #4      SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1090)
E/flutter (18180): #5      SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:998)
E/flutter (18180): #6      _rootRun (dart:async/zone.dart:1354)
E/flutter (18180): #7      _CustomZone.run (dart:async/zone.dart:1258)
E/flutter (18180): #8      _CustomZone.runGuarded (dart:async/zone.dart:1162)
E/flutter (18180): #9      _invoke (dart:ui/hooks.dart:167)
E/flutter (18180): #10     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:259)
E/flutter (18180): #11     _drawFrame (dart:ui/hooks.dart:126)
E/flutter (18180):
E/flutter (18180): [ERROR:flutter/lib/ui/ui_dart_state.cc(186)] Unhandled Exception: LateInitializationError: Local 'result' has not been initialized.
E/flutter (18180): #0      LateError._throwLocalNotInitialized (dart:_internal-patch/internal_patch.dart:208)
E/flutter (18180): #1      RenderObject.debugNeedsPaint (package:flutter/src/rendering/object.dart:2112)
E/flutter (18180): #2      _PageTurnWidgetState._captureImage (package:ssv1/book_screen/builders/widget.dart:40)
E/flutter (18180): #3      SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1144)
E/flutter (18180): #4      SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1090)
E/flutter (18180): #5      SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:998)
E/flutter (18180): #6      _rootRun (dart:async/zone.dart:1354)
E/flutter (18180): #7      _CustomZone.run (dart:async/zone.dart:1258)
E/flutter (18180): #8      _CustomZone.runGuarded (dart:async/zone.dart:1162)
E/flutter (18180): #9      _invoke (dart:ui/hooks.dart:167)
E/flutter (18180): #10     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:259)
E/flutter (18180): #11     _drawFrame (dart:ui/hooks.dart:126)
E/flutter (18180):
E/flutter (18180): [ERROR:flutter/lib/ui/ui_dart_state.cc(186)] Unhandled Exception: LateInitializationError: Local 'result' has not been initialized.
E/flutter (18180): #0      LateError._throwLocalNotInitialized (dart:_internal-patch/internal_patch.dart:208)
E/flutter (18180): #1      RenderObject.debugNeedsPaint (package:flutter/src/rendering/object.dart:2112)
E/flutter (18180): #2      _PageTurnWidgetState._captureImage (package:ssv1/book_screen/builders/widget.dart:40)
E/flutter (18180): #3      SchedulerBinding._invokeFrameCallback (package:flutter/src/scheduler/binding.dart:1144)
E/flutter (18180): #4      SchedulerBinding.handleDrawFrame (package:flutter/src/scheduler/binding.dart:1090)
E/flutter (18180): #5      SchedulerBinding._handleDrawFrame (package:flutter/src/scheduler/binding.dart:998)
E/flutter (18180): #6      _rootRun (dart:async/zone.dart:1354)
E/flutter (18180): #7      _CustomZone.run (dart:async/zone.dart:1258)
E/flutter (18180): #8      _CustomZone.runGuarded (dart:async/zone.dart:1162)
E/flutter (18180): #9      _invoke (dart:ui/hooks.dart:167)
E/flutter (18180): #10     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:259)
E/flutter (18180): #11     _drawFrame (dart:ui/hooks.dart:126)

(The following has failed to resolve)
Downgrade to stable, cleanup, cache etc etc, copy to new project, compile with --no-shrink... all failed,

Debug works perfectly with zero output problems reported on real phone, emulator, windows and chrome builds.
Release compile fails on all platforms in exactly the same way.

After a while of edit and test, I have found a quick fix about this problem, you could change the function _captureImage to like this and it will work on release build, (You 'll need to copy this library to your own directory to edit PageTurnWidget file)
void _captureImage(Duration timeStamp) async {
await Future.delayed(const Duration(milliseconds: 20));
final pixelRatio = MediaQuery.of(context).devicePixelRatio;
final boundary =
_boundaryKey.currentContext?.findRenderObject() as RenderRepaintBoundary;
// if (boundary.debugNeedsPaint) {
//   await Future.delayed(const Duration(milliseconds: 20));
//   return _captureImage(timeStamp);
// }
final image = await boundary.toImage(pixelRatio: pixelRatio);
setState(() => _image = image);
}

Thanks mate - it works. I was hoping for better performance once I could get it to work in release mode but unfortunately its still unusably slow . I might look into how to make the performance better. If you find anything please make sure you post it.

Hi there! I'm writing 1 year later, but who knows, this can be interesting to someone: the original code snippet was probably this Gist. And it's very, very smooth.
I haven't found any relevant difference that might cause this huge difference, but I'll share if I find it.


JSON-based schema-building formats

Hi,
Sorry for the long post, but I thought this may interest you.
I'm planning on submitting a PR to add support in db.js for additional JSON-based schema-building formats in addition to the type supported now.
I was wondering whether you were interested in seeing the proposals below added into idb-schema. An advantage of this is that we could allow users to more easily mix and match formats, e.g., if they built the first two versions programmatically using idb-schema's current approach but then moved to a simpler JSON-based format or vice versa. Or multiple formats could perhaps even be combined within a single version. Each has its advantages and disadvantages.
The programmatic approach is unique in offering the full expressivity of addCallback, while the JSON formats can benefit from being declarative and potentially more succinct.
The first JSON type is already available in db.js (though I want to see it keyed to version so that an extended migration path is possible, e.g., if the user was on version 1 but needed to be brought through versions 2 and 3 as supported in idb-schema).
{
    store1: {
        key: {keyPath: 'id', autoIncrement: true},
        indexes: {
            firstName: {},
            answer: {unique: true}
        }
    }
}

To expand this for supporting versions would be a simple matter of allowing:
{
    1: {
        store1: {
        // ...
    },
    2: {
        store2: {}
    }
}

For each new version, we can compare the stores on the supplied object with the existing stores in the database, and if not in use, we can (optionally) delete them, whereas if there is a change, we can delete unused or changed indexes and create new ones, or rebuild any keyPath/autoIncrement changes. (This is mostly how it works now.)
The advantage of this approach over the other approaches is that it will show the whole schema in code exactly as it will be built upon each version. The disadvantage is the same (that it will become unwieldy with many versions) and also that it doesn't have a means of indicating that a store should be renamed or copied (though I guess it could be expanded to add movedFrom or copiedFrom properties). It might also be enhanced to act similarly to JSON Merge Patch (see below) to allow use of null to explicitly indicate that a given store, store feature, or index was to be deleted, and otherwise not delete. If we supported both of these changes, then I think the third type below would also automatically be supported as a subset of this (modified) first type.
Maybe we could even allow callbacks here too to get all the capabilities in one (though it would no longer by JSON):
{
    1: [function myCallback (upgradeneededEvent, librarySpecificObject) {}, {
        store1: {
        }
    ]

And/or we might allow add/put/delete/clear (with optional keys (including MongoDB-style) where relevant) (as well as an equivalent JSON for our query syntax) within the syntax to avoid the need for callbacks (similar to your idb-batch format).
The second type is one I wish to add based on JSON Patch though it is based on the first type.
3: [
     { "op": "remove", "path": "store2" },
     { "op": "add", "path": "store1/indexes", "value": { "lastName": { } } },
     { "op": "replace", "path": "store1/indexes/answer/unique", "value": false },
     { "op": "move", "from": "storeOldName", "path": "storeNewName" },
     { "op": "copy", "from": "people/indexes", "path": "otherPeople/indexes" }
]

The advantage here is that besides being declarative, a standard, and only needing to express changes, is that it can indicate the renaming of a store (i.e., move) so as to indicate that the original content should be preserved (though under a different name). It can also allow declarative copying (e.g., to replicate indexes on another store).
The third type is JSON Merge Patch (Note that this spec doesn't work well if the null value is needed in the altered JSON, but for our schema purposes, there are no current arguments which act in a special manner with null).
This approach would also be declarative, a standard, and only need to express changes (including being explicit about whether it was deleting or altering), but it would not allow renaming (or copying) of stores. Its advantage over JSON Patch would be that it is more succinct. Here is the equivalent (minus the move/copy)
3: {
    "store2": null,
    "store1": {
        "indexes": {
            "lastName": { }
        },
        "answer": {
            "unique": false
        }
}

What do you think?

Btw, regardless of the choice(s) of schema format, it would be convenient if your schema.stores() format could also be supplied for import and possibly for diffs also.

This is a long post!
I think support of JSON schema is out of scope for this library. If you're willing to implement it, you can create idb-json-schema which consumes programmatic approach of idb-schema.
But I definitely want to improve format of schema.stores() in 4.0 and make it the same as treo's idb-descriptor.


Update

But I'm curious, why did you make this PR on my personal website?

I don't quite get your question?

But I'm curious, why did you make this PR on my personal website?

I don't quite get your question?

You've suggested some changes and a German translation, thanks for that, but this is my personal site, no one else is getting any benefit from it. So why suggest these changes?

...no one else is getting any benefit from it.
Isn't that the case with all OpenSource projects?

So why suggest these changes?
So that even Germans can do something with the page (who can not speak English) 🤣! And to keep all node modules up to date

...no one else is getting any benefit from it.

Isn't that the case with all OpenSource projects?

So why suggest these changes?

So that even Germans can do something with the page (who can not speak English) 🤣! And to keep all node modules up to date

Yeah yeah that's cool, it just seemed unusual to me


Allow arbitrary metadata on refs

it's not part of the changes, but the update ref part should really just update the existing ref object in elastic and remove any parent* keys so it won't contradict the the existing ref (or reject the update if the parent* keys aren't the same)

Ok, sounds good. I'll create a new PR for that.


[BUG] Ollama AIX Configuration Issue

Description
Setup Ollama + bigAGI fresh install. I have followed the basic steps. Ollama has been verified to work with other apps. I added Ollama to the bigAGI as a service provider and can see the models. I am on v2-dev
When in chat mode, I try to start a chat it gives me this error in the chat UI:
[AIX Configuration Issue] Ollama: Ollama is not supported in this context

and this error in the server:
Aix.Ollama (dispatch-prepare): **[AIX Configuration Issue] Ollama**: Ollama is not supported in this context

Ollama service notes the requets but shows no error.
Would appreciate any help
Device and browser
Linux Local deployment with npm
Screenshots and more

Willingness to Contribute

[X] 🙋♂ Yes, I would like to contribute a fix.

True, Ollama has not been ported to AIX (big agi 2 new AI engine) yet.
Model listing is working, but ollama has some non standard protocol that needs to be implemented.
AIX has new native support for OpenAI-compatible, Anthropic, and Google protocols, but not Ollama yet.
It's likely not much work to do it, so if anyone wants to contribute it, I'd welcome a PR. I'm working on the official 2.0 release which will likely come without Ollama support at launch unless someone steps in and puts the day of work that's required to make and this.

@matrix303 try now ;) simple fix, seems to work very well, including images (PNG only) with Vision.

@matrix303 correct - that was the first out of 4 commits to fix ollama; it only updated the models. It was actually the next commit that brought in the bulk of the fixes.
Go with the current head of v2-dev, or 1811e31ea5c8a79bf5cc3641289b57655154cbf5 to be safe.

@enricoros, got it working! for some reason I had to reclone the git repo but its very likely due to my own "explorations" into trying to get it working.
Cheers

Great, let me know how it is, the integration should be solid @matrix303


Optimising input bar for mobile

Beware, changes to the input bar.

Only CSS changes
Optimisation for mobile sizes

We have problems on mobile that are not related to the new input bar:
Scrolling is sorta broken: On iOS when virtual keyboard comes out, it does weird stuff to the viewport. As a result, people can scroll the page up and down, including higher than they should because a zone is created under the screen.
Fullscreen is also broken because the viewport size is actually bigger than the screen and therefor the fullscreen is more than full.
As a result, I'm hidding the fullscreen option on mobile as it makes things worse.


Changed order of operations in init, so that context set before NUMA mods.

This pull request is to fix issue #89

Looks ok, Yep. let run a test and I'll do the merge

The error comes from PR #17, which added NUMA for debian upstart init script (other init scripts already had the feature, correctly implemented it seems (sysconfig_file loaded before NUMA).
:+1:


CARDS-1783: Make email scheduling more flexible

The PR removes the InitialNotificationsTask and ReminderNotificationsTask scheduled tasks and provides, as a replacement, an OSGi component that can be configured and instantiated to provide emails for upcoming appointments. The functionality of the InitialNotificationsTask and ReminderNotificationsTask scheduled tasks is preserved by the InitialNotificationsTask and ReminderNotificationsTask configurations for io.uhndata.cards.proms.emailnotifications.UpcomingNotificationsFactory that is loaded upon repository initialization.
To test:

Build this PR with mvn clean install
Follow the instructions in https://github.com/data-team-uhn/cards/blob/dev/Utilities/Development/EmailServer/README.md to setup a testing mail server and client to see the emails sent by CARDS. Follow the Using (with ./start_cards.sh) instructions as opposed to the Using (with Docker Compose) instructions.
Open a new terminal in Utilities/Development and start the mock Torch server by running nodejs mock_torch.js --appointment-time-hours-from-now=24.
Open a new terminal in Utilities/Development and start the mock Slack server by running nodejs mock_slack.js
Start CARDS in Cards4Proms mode with the command<EMAIL_ADDRESS>PATIENT_NOTIFICATION_FROM_NAME=DATAPRO NIGHTLY_NOTIFICATIONS_SCHEDULE="0 * * * * ? *" CARDS_HOST_AND_PORT='localhost:8080' NIGHTLY_SLACK_NOTIFICATIONS_SCHEDULE="0 * * * * ? *" SLACK_PERFORMANCE_URL="http://localhost:8000/" ./start_cards.sh --dev --project cards4proms -V emailnotifications.smtps.checkserveridentity=false.
Visit http://localhost:8080 and login as admin:admin.
Visit http://localhost:8080/system/console/configMgr and add a new PROMs Import configuration with the following values:

Name: LocalNodeJS
Import schedule: 0 0 0 * * ? *
days to query: 3
Endpoint URL: http://localhost:8011/
Authentication URL: (leave blank)
Vault token: (leave blank)
Clinic names: 6012-HC-Congenital Cardiac
Provider names: SomeParticipantEID
Allowed provider roles: ATND
Vault role name: (leave blank)
Dates to query: (leave blank)

Trigger the import by visiting http://localhost:8080/Subjects.importTorch?config=LocalNodeJS
Verify that the 12345 / AppointmentOneFhirID-Cardio appointment was created.
You should now receive an email with the subject "Reminder: You have 24 hours left to complete your pre-appointment questions" once every minute.
Visit http://localhost:8080/system/console/configMgr once again and create a new Upcoming appointment notification with the following values:

Name: TestNotifications
Metric Name: Test Notification emails sent
Clinic Mapping Path: /Proms/ClinicMapping/853703519
Email Subject Line: Email Notification System Test
Plaintext Email Template JCR Path: /apps/cards/proms/clinics/Cardio/mailTemplates/24h.txt
HTML Email Template JCR Path: /apps/cards/proms/clinics/Cardio/mailTemplates/24h.html
Days before upcoming visit: 1

Every minute you should receive an upcoming appointment notification email with the subject line Email Notification System Test.
On the mock Slack server, you should also be receiving, once every minute, performance notifications that include an incrementing count of Test Notification emails sent and Reminder Emails Sent. It should also display 1 for the Total number of Imported Appointments.
Repeat the above steps but, this time, specify an appointment 72 hours from now instead of 24 hours when starting the mock Torch server (ie. nodejs mock_torch.js --appointment-time-hours-from-now=72). Verify that you are receiving an email with the subject line "Welcome to DATAPRO: Answer your Pre-Appointment Questions" once every minute. Also verify that the Initial Emails Sent count in the Slack notifications is auto-incrementing.

Code reviewed, not tested

@IntegralProgrammer @acrowthe does this generalization allow sending notification emails AFTER the visit time? For prems, the notifications to fill out experience surveys must be sent a couple of days after the patient is discharged.

Looks like sending notification emails to past visits might actually work if daysBeforeVisit in GeneralNotificationsTask is negative (via @IntegralProgrammer; to be confirmed by testing), which means the PREMs use case might be covered functionality-wise.
That being said, since we want to generalize this code for both proms and prems, some more minor refactoring might make the code easier to digest:
* [ ]  Rename `AbstractPromsNotification` to `AbstractEmailNotification` (or `AbstractPatientNotification`?)

* [ ]  `In Abstract****Notification`, rename `daysInTheFuture` to `differenceInDays` and document that a negative value sends emails for past events, while a positive value sends emails for future events

* [ ]  Similarly in GeneralNotificationTask rename `daysBeforeVisit` to `daysToVisit` and document the meaning of positive and negative values.

* [ ]  In `UpcomingNotificationFactory`, rename `daysBeforUpcomingVisit` to `daysToVisit`, change the name and description and document the meaning of positive and negative values.
  Can we assume that in the name of this class `Upcoming` refers to the notification about to be sent, not to the visit in the future? if not, this class also needs to be renamed.

I have done these refactorings and can confirm that tasks can be created that send emails both for appointments in the future (PROMS) as well as appointments in the past (PREMS).
To test:

Follow the original testing instructions in the description of this PR and ensure that the default 72 hour initial notification and 24 hour reminder notification tasks still work as expected.
Visit http://localhost:8080/system/console/configMgr and create a new Appointment email notification with the following parameters:

name: PastAppointmentFollowUp
metricName: Follow-up Emails Sent
clinicId: /Proms/ClinicMapping/853703519
emailSubject: How was your appointment?
plainTextEmailTemplatePath: /apps/cards/proms/clinics/Cardio/mailTemplates/24h.txt
htmlEmailTemplatePath: /apps/cards/proms/clinics/Cardio/mailTemplates/24h.html
daysToVisit: -7

Visit http://localhost:8080/bin/browser.html and edit a Visit information Form so that the visit date is 1 week ago from today (you'll need to check-out the Form node before doing this and check it back in after)
Ensure that you are receiving emails with the subject How was your appointment? once every minute.


runs seems a typo

In the README.md -> Usage -> Basic section, there is a field runs. But the VSCode reports an error:
There's not enough info to determine what you meant. Add one of these properties: run, shell, uses, with, working-directory
Expected uses or run to be defined

I think it should be run?

You're right it should be run. PR would be welcome if you have the time


New modules and Java versions

Set GWT version to 2.8.1, GWTP to 1.6 and GwtBootstrap3 to 0.9.4
In every *.gwt.xml file added property gssDefaultInUiBinder to true,
so the GSS is used as default.
Added string constants in Select widget.
Java version 1.8

@zlamalp I have updated the Bootstrap and JQuery versions and it seemed all OK. Also, I have replaced the spaces with tabs.

@zlamalp I have just added a sha512 hash wherever it was missing. I believe it should be all ok now.


Adding file extension to interface imports

Adding the file extension will allow the interface imports to work for typescript packages using both moduleResolution bundler as well as nodenext. This is also more closely aligned with the node spec for imports so should be better supported. Closes #223

LGTM

Thanks for the follow-up here.


Solving environment: / Killed

Hello there! While attempting to install using the environment.yml file, I encountered the error message "Solving environment: / Killed". Trying to understand what was causing this issue, I found that fitsio and pyccl dependencies in the .yml  file were necessary. After adding these dependencies, the installation proceeded successfully.

Hi @gabygga ! Thanks for pointing this out!
A fix is being merged by #34


Drop the useless '(s = strlen(ofname)) > 8' conditions

Fixes: #12

this PR didn't clean up unused variables.  i pushed commit dff43a5 to the same thing.
thanks for pointing out the obsolete logic.


Add ampersandia.net

42.5KB according to https://tools.pingdom.com/#5ff73d78c5000000

This website is already a member.


Write a C program to find average of digits of a number

Description
Write a C program to find average of digits of a number
Average of digits of a number is the sum of all digits divided by the number of digits.
Input  : 123
Output : 2

How to contribute

Save the solution in program/FindAverageOfDigitsOfANumber.c file
Add FindAverageOfDigitsOfANumber.c file in find-average-of-digits-of-a-number folder

!assign

Hey @astitva0011,
This issue has been assigned to you for more than 15 days.
We are unassigning you from this issue.
If you are still interested in contributing to this issue, please get auto-assigned on the issue by commenting !assign again.
Thanks for your contributions :)

!assign

Can Output be in decimal?

It should be, thanks for noticing 👍🏻

!assign


Allow loading data to webviews

Use case
Developers sometimes wants a webview to render a page from a string.
For example this is done in the webview_flutter example app for the navigation delegate example.
While this can currently be done using data URIs that approach has a few drawbacks:

A base url cannot be specified which means scripts are unable to access content loaded using any scheme other than 'data'.
Converting the data to base64 is required even if the backing webview doesn't require it.
It requires some boilerplate.

Proposal
Add a loadData method to WebViewController:
Future<void> loadData({@required String data, @required String mimeType, String baseUrl});

This will use [loadHtmlString:baseUrl] on iOS and loadWithBaseUrl on Android.
Note that https://github.com/flutter/plugins/pull/1312 and https://github.com/flutter/plugins/pull/1137 are both trying to solve the same problem but need some more work (we can resolve this issue either with a new PR or by iterating on one of those PRs)

This was fixed in 2.4.0


Allow images to be used as column headers

Prework

[x] Read and abide by the great_tables code of conduct and contributing guidelines.
[x] Search for duplicates among the existing issues (both open and closed).

Proposal
This can be achieved in a couple of ways already, although they both are very hacky. One is by using placeholder column names and replacing them appropriately in the HTML output created by as_raw_html with base64 encoded <img> tags (essentially the approach that is used in fmt_image).
A couple of approaches that might work for a proper implementation this:

A .fmt_column_header_image method that mimicks fmt_image and reuses FmtImage if possible.

df = pl.DataFrame([
    {"column_name": 1.0}
])

GT(df).fmt_column_header_image(
     column_name=<path to image>,
     # fmt_image kwargs
     height=...
)

Allow option in .col_labels to enable use of an image instead of a renaming label, or infer from argument type

df = pl.DataFrame([
    {"regular_name": 1.0, "image_column": "something"}
])

GT(df).col_labels(
    regular_name="some other name",
    # infer from Path type?
    image_column=Path(...),
)

I would be happy to try implementing something like this. Thank you 😄

Thank you for bringing this issue to our attention. I'll close it now, as the vals.fmt_image() function is available to achieve the desired result.


Address case in ETH tx verification on BitBox02 and tx verification on simulator

See commit messages for detailed explanation.

Okay, I implemented the changes you have pointed out.

Oh also please add a CHANGELOG entry

Did my last push now, according to your requests

Okay, I also added an entry to CHANGELOG of Python API


Bad tooltips on matches for player

When I select matches page for a player and then paginate it once or twice, I keep getting the followin tooltip issue:

Google chrome, Windows 10. Also, Safari on Mac.

This may be fixed in https://github.com/odota/ui/pull/389/commits/50689655bbed57cc764bba5afe6c14bd488a4bec #389

Can we get a confirmation if this is fixed?

Yes


Which copyright license does this project have (or - if at all - to which do you plan to change it)?

It's Apache 2, you can see the license file. No plans to change it.


ESP01 8266 doesn't connect with MQTT local server

Hi guys, I keep having problems with my ESP01. Even if i read about a lot of problem like this one none of the solutions worked form me.
I have mosquitto running locally on my mac (so in Node red MQTT server is set to "localhost:1833"). Then I try to send data from my ESP01 using the pubsub library. Initially the ESP01 connect to my WiFi, but then it can not connect to the mosquitto server. What am I missing? Should I change the mosquitto ip address from "localhost:1833" to something else?
This is the code
#include <ESP8266WiFi.h>
#include <PubSubClient.h>

const char* ssid         = "WifiNetworkname";
const char* password     = "password";
const char* mqttServer   = "localhost:1833";
const int   mqttPort     = 1883;

#define PUB_GPIO2_STATUS "state"
#define SUB_GPIO2_ACTION "state"

#define GPIO2_LED 2

WiFiClient wifiClient;
PubSubClient mqttClient(wifiClient);

void loop() {
    mqttClient.loop();
}

void initWifiStation() {

    WiFi.mode(WIFI_AP_STA);
    WiFi.begin(ssid, password);
    Serial.print("\nConnecting to WiFi");
    while (WiFi.status() != WL_CONNECTED) {
       delay(1000);
       Serial.print(".");
    }
    Serial.println(String("\nConnected to the WiFi network (") + ssid + ")" );
}

void initMQTTClient() {

    // Connecting to MQTT server
    mqttClient.setServer(mqttServer, mqttPort);

    while (!mqttClient.connected()) {
        Serial.println(String("Connecting to MQTT (") + mqttServer + ")...");
        if (mqttClient.connect("ESP8266Client")) {
            Serial.println("MQTT client connected");
        } else {
            Serial.print("\nFailed with state ");
            Serial.println(mqttClient.state());

            if (WiFi.status() != WL_CONNECTED) {
               initWifiStation();
            }
            delay(2000);
        }
    }

    // Declare Pub/Sub topics
    mqttClient.publish(PUB_GPIO2_STATUS, "Hello");
    mqttClient.subscribe(SUB_GPIO2_ACTION);
}

void setup() {

    Serial.begin(115200);

  // GPIO2 is set OUTPUT
    pinMode(GPIO2_LED, OUTPUT);

    initWifiStation();
    initMQTTClient();

}

Not sure what you mean with

I have mosquitto running locally on my mac (so in Node red MQTT server is set to "localhost:1833").

mqttServer in your ESP01 code should be the IP address of the computer where Mosquitto is running

Not sure what you mean with

I have mosquitto running locally on my mac (so in Node red MQTT server is set to "localhost:1833").

mqttServer in your ESP01 code should be the IP address of the computer where Mosquitto is running

@absalom-muc I mean that I installed mosquitto on my computer and then started it with the command "brew services start mosquitto"

@absalom-muc I mean that I installed mosquitto on my computer and then started it with the command "brew services start mosquitto"

mqttServer in your ESP01 code should be the IP address of the computer where Mosquitto is running

I know but I think the syntax is wrong

mqttServer in your ESP01 code should be the IP address of the computer where Mosquitto is running

I know but I think the syntax is wrong

The syntax is
const char* mqttServer   = "Name_of_the_computer_where_Mosquitto_is_running";
It is not localhost and the mqtt port is not part of this name.
Maybe you try it first with a public available broker to find out if the problem is on ESP side or with your computer where Mosquitto is running

The syntax is
const char* mqttServer   = "Name_of_the_computer_where_Mosquitto_is_running";
It is not localhost and the mqtt port is not part of this name.
Maybe you try it first with a public available broker to find out if the problem is on ESP side or with your computer where Mosquitto is running

How can I find my IP address if I'm on a mac?

How can I find my IP address if I'm on a mac?

I tested a public broker and everything works fine. The esp-01 just can't connect when I'm using local broker mosquitto

I tested a public broker and everything works fine. The esp-01 just can't connect when I'm using local broker mosquitto

How can I find my IP address if I'm on a mac?

I've no mac, but when I enter your question in a search machine I get many hits. Maybe you try it ...

How can I find my IP address if I'm on a mac?

I've no mac, but when I enter your question in a search machine I get many hits. Maybe you try it ...


Fix doc/code mismatch on FINISH case 9.4

The doc expects UnexpectedRequest, before KEY_EXCHANGE. But the code only send VC without ALGORITHM.
However, if VCA is used, then the error is SessionRequired. That also makes sense, because without KEY_EXCHANGE there is no session.
As such, just fix the doc to match the code.

Fix https://github.com/DMTF/SPDM-Responder-Validator/issues/97


get_child doesn't have onready warning

Godot version:
3.2
Issue description:
When you declare a field variable using get_node(), you get a warning that it won't work and use onready. The same is true for get_child() (and maybe get_parent() and similar), but the warning doesn't appear.

for my fix: does the get_parent() method needs the warning ??
@KoBeWi

It does.


fix(plugin-local-electron): Make the plugin compatible on Windows, and can live with other plugins

[x] I have read the contribution documentation for this project.
[x] I agree to follow the code of conduct that this project follows, as appropriate.
[x] The changes are appropriately documented (if applicable).
[x] The changes have sufficient test coverage (if applicable).
[x] The testsuite passes successfully on my local machine (if applicable).

Summarize your changes:
The plugin-local-electron currently cannot work with plugin-vite (or any other plugin) because it claims startLogic, which is unnecessary because it just merely set the ELECTRON_OVERRIDE_DIST_PATH env var.
This PR:

Moved this logic to init function instead of startLogic
Changed function locateElectronExecutable to detect this ELECTRON_OVERRIDE_DIST_PATH env var to make the project directly starts the binary in the wanted path. (Because on Windows this env variable makes no effect and still launch the binary under node_modules...)

@caoxiemeihao Can I bother you review this?

@VerteDinde Can you review this PR?😘

@reitowo please can you resolve conflicts?


add new creative tabs wand gui

I suggest adding a creative tabs wand gui. For every type of magic (eg. Utility, Firebending, etc). Also a search feature would be nice

Creative mode is a hack. It's all client-side, there's nothing I can do with it, and it screws up wands and inventories in general by giving the client control over all of it. Sorry!


Switch no-loop-func eslint rule from warning to error (in .eslintrc)

The one error that needed to be fixed was in static/js/echo.js.
The function in the loop was being used by _.each(). This has been
replaced by iterating through the array using a while loop instead.

Automated message from Dropbox CLA bot
@arpith, it looks like you've already signed the Dropbox CLA. Thanks!

This looks great.  Merged, thanks @arpith!


Modify modulation property names

Fixes #398
Fixes #397
Renames rate to code_rate
Fixes #366

Codecov Report
Attention: Patch coverage is 84.89209% with 21 lines in your changes missing coverage. Please review.

Project coverage is 79.51%. Comparing base (05bee3d) to head (c1a7242).

Files
Patch %
Lines

src/sdr/_modulation/_linear.py
76.47%
8 Missing :warning:

src/sdr/_modulation/_cpm.py
76.66%
7 Missing :warning:

src/sdr/_modulation/_psk.py
50.00%
5 Missing :warning:

src/sdr/_modulation/_msk.py
66.66%
1 Missing :warning:

Additional details and impacted files
@@                Coverage Diff                @@
##           release/0.0.x     #401      +/-   ##
=================================================
- Coverage          79.59%   79.51%   -0.09%
=================================================
  Files                 63       63
  Lines               3931     3963      +32
=================================================
+ Hits                3129     3151      +22
- Misses               802      812      +10

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


add brotli support

This adds brotli header support since Preact-cli now supports brotli compression.

Thank you @hassanbazzi


[FE] Filter for communities

Codecov Report

Merging #42 into master will increase coverage by 0.18%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #42      +/-   ##
==========================================
+ Coverage    70.7%   70.88%   +0.18%
==========================================
  Files          56       57       +1
  Lines        1280     1288       +8
  Branches       75       76       +1
==========================================
+ Hits          905      913       +8
  Misses        358      358
  Partials       17       17

Impacted Files
Coverage Δ

src/app/communities/communities-filter.pipe.ts
100% <100%> (ø)

src/app/communities/communities.component.ts
57.57% <100%> (+1.32%)
:arrow_up:

Continue to review full report at Codecov.

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


fix: use gcs in gateway

Fixes https://github.com/prefix-dev/pixi/issues/1922

@clement-chaneching Would you be able to verify if this works for you using something like?
rattler create --dry-run -c gcs://... <some package>


(V2) Warning or error for orphan docs

🚀 Feature
When the site is built, show a warning or an error about orphaned docs page. An orphaned doc would be the one that has no links from any other docs or in the sidebar navigation. As a result, that doc may never be discovered.
Have you read the Contributing Guidelines on issues?
Yes
Motivation
This is one of the ways to improve seo for a technical docs site. All docs pages should be navigateable through internal links in the site. In this case, it can be either through links from another doc or through sidebar navigation.
Sphinx based site has an option to be able to detect this kind of orphaned docs. It'd be great if we could catch similar issues in Docusaurus.
https://docs.readthedocs.io/en/stable/guides/technical-docs-seo-guide.html
Pitch
I think the easiest way to implement is to check if each docs listed in one of the sidebar.
Whether each docs have at least one link from another doc, might be tricky to implement because every docs have to parsed and keep track of links. It's probably also safe to assume that every docs should be in the sidebar. So, maybe only checking sidebars for orphaned docs is enough.
This should be configurable so that it'll be either an error or warning. Making it an error will be helpful for CI process.
A similar warning for orphaned assets can be helpful. There's no point in having an image file included in the site if it's not used anywhere in the docs. Perhaps orphaned docs asset should be a separate feature request.

Hi,
This is something I actually noticed and wanted to work on some day :)
I think we should also allow a frontmatter like secret: true, so that if it's not linked from anywhere, it does not work. Sometimes people want a page with no link and no sitemap to it on purpose.

I think we should also allow a frontmatter or config like secret: true, so that if it's not linked from anywhere, it does not warn/error. Sometimes people want a page with no link and no sitemap on purpose, until they are ready to publish.

I'm not so sure about that. It may give some people an incorrect impression of the content of that page being "secured".
Even if there are no links to that "secret" page from other docs, it does not make that page secured in anyway. Search engine crawlers might still locate it or someone can still find that page (manually or accidentally). Someone from the inside might even post a link to it if they're upset for any reason.
The only way contents should be secured is if there are authentication in place; this brings up a completely separate topic. Or, the site should not be published publicly; i.e. publish internally that is only accessible through VPN.
Bottom line is, "secrets" should be handled veeeery carefully 😄

@amimas this is an option that would be documented. The user should understand that the link is still accessible, just without any link.
I use this feature extensively on my own blog, based on a gatsby theme: https://github.com/narative/gatsby-theme-novela#post

This is useful because it permits me to share an actual link for blog post reviews before final publish, without requiring to create PR deployments.
Some sites only use Github pages, not all are on Netlify, yet they may want a doc review from community folks before including it in the sidebar. Having an actual link to share is more convenient than asking them to review the MD on Github (particularly if it's interactive MDX)

Isn't this already doable right now? Even if the warning/error message about orphaned docs feature is implemented, in this case you'd just set that option to be a warning. Not sure what the value of the metadata in front matter. In your case, it needs to be an orphaned page. Maybe I'm getting tripped over the term "secret" as metadata.

We can see later if having an error/warning is a problem.
I'm ok to check for unreferenced docs. I probably wouldn't mind if the build show a few warnings in case I have private docs anyway, so we'll figure later if that is annoying for some users.

Hi, is this currently being worked on? If not, I'd like to take a stab at it if its still a desired issue

Thanks, you can work on it
Le jeu. 12 nov. 2020 à 21:14, vthirupathi<EMAIL_ADDRESS>a
écrit :

Hi, is this currently being worked on? If not, I'd like to take a stab at
it if its still a desired feature
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/facebook/docusaurus/issues/2875#issuecomment-726315586,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFW6PWYJ4JWNMXHJ7RXIQ3SPQ6ZPANCNFSM4NSHGYBQ
.

Hi, me and @cindygu4 have constructed a plan for this. We're having trouble figuring out which file in the source would be responsible for displaying the warning?
Also, in website/sidebars.js, how is docs-introduction resolved. As in, how does it know this refers to docs.md?

Hi @vikhramt007
I don't know what is the best place to handle this in the code.
Sidebars use doc ids, that are generated from the FS location or by frontmatter.

It's probably better to discuss first what you plan to build exactly, and its API, before rushing on implementing it, or you'll likely end up coding something we couldn't merge due to a bad design decision

Hi @vikhramt007
I don't know what is the best place to handle this in the code.

We were just unsure of if the warning is displayed on the website's home page or when the user clicks on the docs page?

Sidebars use doc ids, that are generated from the FS location or by frontmatter.

Thanks, this really clears that up!

It's probably better to discuss first what you plan to build exactly, and its API, before rushing on implementing it, or you'll likely end up coding something we couldn't merge due to a bad design decision

Our current plan is as follows:

In sidebar.js create a set of doc ids from the items key of each dictionary with type: 'category', as well as any standalone strings.
look through the .md or .mdx files for each doc id and add any linked docs not yet added to the set, and repeat this process until no new docs are added
using this complete set of non-orphan docs, create a list of all  docs not in this set (orphan docs)
Display all these orphan docs either in the home page or docs page

Would this be a valid approach?
Thanks for the input

Hi,
The type DocMetadata already contains the sidebarName attribute if the doc is associated with any sidebar, so you don't need to work on finding docs that are not in any sidebar, it's already done for you.
The concept of "orphan doc" is not "does not appear in any sidebar", but rather "has no incoming link". If a doc is not in any  sidebar, but the homepage links to it, it should not be considered as orphan.

Display all these orphan docs either in the home page or docs page

This feature  is about warning/error, not displaying those docs in the UI.  You can reuse the reporting code used by onBrokenLinks when you detect an orphan doc, and  offer a configurable option for this logging (some users may want an orphan doc on purpose for some reasons, and should be able to disable such warning)

I wonder if this should not be handled more generically. @amimas it make sense to also report orphan pages no? Or do we explicitly want to restrict this to docs?
There's already a method here:
export async function handleBrokenLinks({
  allCollectedLinks,
  onBrokenLinks,
  routes,
  baseUrl,
  outDir,
}: {
  allCollectedLinks: Record<string, string[]>;
  onBrokenLinks: ReportingSeverity;
  routes: RouteConfig[];
  baseUrl: string;
  outDir: string;
})

In which we have all the page paths and their outgoing links, it should be doable to detect which pages have no incoming links based on these datas.

This would be very easy to implement given all links collected (and also the solution that IMO makes the most sense). The only problem is the number of false positives. Should we allow users to declare a list of routes to be ignored? If we do it in the core, we can't rely on any metadata and have to hard-code the ignored routes.


Add region override

Is your feature request related to a problem? Please describe.
It's not possible to override the region without changing the source code.
See https://github.com/theurichde/go-aws-sso/blob/6d35a950f02ba9b193c3ef2c36075669792ee326/main.go#L28
Describe the solution you'd like
It'd be nice to be able to specify a region some other way (i.e. flag).
Describe alternatives you've considered
N/A
Additional context
When using the incorrect region, authorization returnsinvalid_grant provided.

Thanks for reporting!

[X] Fixed right now with version v0.2.0

You can either set the region now via e.g. --region ca-central-1, -r ca-central-1 or in the config file via region: ca-central-1


Toasts for live channel notifications

#678
This feature request is mainly for those users who only use the chatterino browser extension as well as those who only have 1 channel open at a time. The idea is that chatterino will fetch the live-status of channels that are not in splits if you have them added to receive notifications from them. This way the user can open the channel that the user has selected a notification for when the channel goes live.

Fixed by @apa420 in #678


[DPE-2317] Small upgrade fixes

While testing upgrades on Kafka/Zookeeper VM, I found a couple of small fixes/improvements on UX.
The most relevant one should be setting failed the unit if the upgrade_stack is not present. This used to create a sense of false expectation that upgrade run, even if the pre_upgrade action was not run and the upgrade_stack was not determined.

Closing as stable


Fix: Portal level layer strikeout

ATM there is no 'Portal-Level-Limit-By-Zoom'..so the old 'strike-out-portal-level-layer-if-not-visible' is obsolete.
While removing the old code (commit 2b545a2) I stumbled upon some depending and also obsolete stuff (commit 54916a8 - commit hash in comment in wrong)

closed because stale project


moving list removing inside the CS

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


azure keyvault is not working with Ubuntu 20.04 (WLS)

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az keyvault secret list
Errors:
No module named 'azure.keyvault.v7_0'
Traceback (most recent call last):
python3/dist-packages/knack/cli.py, ln 206, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 528, in execute
    self.commands_loader.load_arguments(command)
azure/cli/core/__init__.py, ln 299, in load_arguments
    self.command_table[command].load_arguments()  # this loads the arguments via reflection
cli/core/commands/__init__.py, ln 291, in load_arguments
    super(AzCliCommand, self).load_arguments()
...
<frozen importlib._bootstrap>, ln 961, in _find_and_load_unlocked
<frozen importlib._bootstrap>, ln 219, in _call_with_frames_removed
<frozen importlib._bootstrap>, ln 1014, in _gcd_import
<frozen importlib._bootstrap>, ln 991, in _find_and_load
<frozen importlib._bootstrap>, ln 973, in _find_and_load_unlocked
ModuleNotFoundError: No module named 'azure.keyvault.v7_0'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az keyvault secret list --vault-name {}

Expected Behavior
Environment Summary
Linux-4.4.0-19041-Microsoft-x86_64-with-glibc2.29
Python 3.8.5
Shell: bash

azure-cli 2.0.81

Extensions:
azure-devops 0.17.0

Additional Context

hi @houk-ms could you pls help to have a look? thanks

hi @cosmospuglisi could you pls install latest Azure CLI to see if the issue still there? 2.0.81 has some issue detail pls see https://github.com/Azure/azure-cli/issues/14011

Latest update is ok
On Mon, Mar 8, 2021, 07:07 Yunge Zhu<EMAIL_ADDRESS>wrote:

hi @cosmospuglisi https://github.com/cosmospuglisi could you pls
install latest Azure CLI to see if the issue still there? 2.0.81 has some
issue detail pls see #14011
https://github.com/Azure/azure-cli/issues/14011
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-cli/issues/16268#issuecomment-792493892,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABCK5V3TZSWRLCDEEDXDU3TCRSSTANCNFSM4U3OV5IQ
.

Please see https://github.com/Azure/azure-cli/issues/19640#issuecomment-1148202854


Polygon entity blinking when updating its color on mouseover

Here is a sandcastle of my problem.
Expected behaviour: I have three groups of polygons, and I want to add each group to the viewer as a CustomDataSource, and instanciate each polygon as entities in these dataSources. When hovering a polygon, I want to change the polygon color and reset the color of the previous hovered polygon (if there was one).
Actual behaviour: In the provided example, as mouse moves inside the polygon on the right side, it starts flickering, while it works fine on other polygons. I then noticed that if I add another polygon entity in the same dataSource (uncomment line 15 to do so), it doesn't bug anymore. It seems like it bugs out only when having a single entity in the dataSource. I've logged the pickedObject in the console and when moving the mouse over the "bugged" polygon, undefined value is sometimes returned by viewer.scene.pick method instead of the expected entity.
Have I messed something up in this code ?
Browser: Tested on Chrome/Firefox
Operating System: Tested on Linux/Windows
Thank you in advance for your help ;)
NB: In case the following information is relevant : I've seen posts suggesting that color changing on hover events like this example can be done using a CallbackProperty, but I can not do it this way because I've got a use case where I have up to 2320 polygons and the scene won't even load when instanciating each entity with a CallbackProperty for the color.

The picking is actually working correctly - the problem is that when you update an entity, this update happens asynchronously. When the entity disappears for a few frames, the picking result becomes undefined (because there's nothing rendered).
Ideally you could just say "I want this entity to be update synchronously" for cases when it won't update every frame, but when it does update it'll be on user interaction and you'd want it to be synchronous. You can read a bit more on this here: https://github.com/AnalyticalGraphicsInc/cesium/issues/7934#issuecomment-501304278

Hello @OmarShehata and thank you for your answer.
My bad for incriminating the picking, I misunderstood the problem !
I've read #7934 and I understand the following available solutions:

using a CallbackProperty to make the entity dynamic but it would result in poor perfs for my use case of thousands of polygons
or use the primitives directly with geometryInstances as said in this comment

Nevertheless, I can't help wondering how come there isn't any blinking when I have several entities in the EntityCollection of the CustomDataSource, but there is blinking only when having a single polygon entity.
See in this simpler sandcastle how it blinks on hover when I declared only one array of coordinates to be translated as an entity, but if you uncomment line 5 and add another polygon with [0,0] coordinates, it doesn't blink anymore.

I edited the title so it matches the actual problem and so it doesn't incriminate the picking !
If you have any hint on why this behaviour is happening when the entity is declared alone, but not happening if I declare several entities in the dataSource ?
Maybe some collection is dropped in first case when removing/recreating the entity and not in the second case or something like that.

@jeremiebailleul I'm closing this since the blinking is expected behavior as explained in my earlier comment. The fact it doesn't happen in all situations is a good question, but I think what would really solve this problem for you is being able to control when entities are sync/async, which is the feature request here: https://github.com/AnalyticalGraphicsInc/cesium/issues/5127
Feel free to 👍 that to express your interest in seeing that feature in the engine.

I think that I found why the blinking happen only on some situations.
When we are updating a polygon, we are removing it from the batch before inserting it again.
GeometryVisualizer.js:
            //If in a single update, an entity gets removed and a new instance
            //re-added with the same id, the updater no longer tracks the
            //correct entity, we need to both remove the old one and
            //add the new one, which is done by pushing the entity
            //onto the removed/added lists.
            if (updaterSet.entity === entity) {
                updaterSet.forEach(function(updater) {
                    that._removeUpdater(updater);
                    that._insertUpdaterIntoBatch(time, updater);
                });
            } else {

If the polygon is alone in a batch, the batch is destroyed when removing the updater. The function _insertUpdaterIntoBatch will have to create a new batch.
StaticGroundGeometryPerMaterialBatch.js:
    StaticGroundGeometryPerMaterialBatch.prototype.remove = function(updater) {
        var items = this._items;
        var length = items.length;
        for (var i = length - 1; i >= 0; i--) {
            var item = items[i];
            if (item.remove(updater)) {
                if (item.updaters.length === 0) {
                    items.splice(i, 1);
                    item.destroy();
                }
                break;
            }
        }
    };

Not destroying the batch when are updating an entity seems to solve the issue.
The color update is still a bit slow but the polygon doesn't disappear before being displayed with its new color.

Here is the recommended way of changing a polygon's color on mouse over that avoids any flickering. You need to use a ColorMaterialProperty, that has a CallbackProperty for its color value.
This will not mark the entity as dynamic, so it should be efficient to have this on thousands of entities.  This will simply change the color attribute of the underlying primitive. Here's a version of this implemented in the primitive API to make it clear what's happening under the head. I'd be happy to review a new Sandcastle example that adds this to the list of examples since it's not obvious this is the right way to do it.

Thank you for your help.
The solution using entities and a CallbackProperty is too slow to be used when there are 100 polygons. We were able to display a lot more entities without the CallbackProperty.
The solution with the primitive API seems to work fast enough for about 2000 polygons.

@OmarShehata FYI, the primitive/Entity versions you link to above are not doing the same thing.  The primitive one does not confirm the Polygon to terrain, while the Entity one does.  You need to use GroundPrimitive to have the polygon on terrain. That is most likely the main reason for the performance difference.  I'm pretty sure there is also a performance bug in the Entity API that I'm looking into as well but may be something different.

Just opened #8630 which greatly improves performance in the Entity API for this use case and should scale to thousands of polygons.


Fix example project

Summary
Update java SDK to 3.5.2
Update the corresponding functions to use the new API
Downgrade targetSdkVersion to 22, since the example project didn't handle runtime permission yet

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

fix #17 #18 #19

Current coverage is 0.00% (diff: 0.00%)

Merging #20 into master will not change coverage

@@           master   #20   diff @@
===================================
  Files           1     1
  Lines         148   148
  Methods         0     0
  Messages        0     0
  Branches       10    10
===================================
  Hits            0     0
  Misses        148   148
  Partials        0     0

Powered by Codecov. Last update 8bf24cd...8720d22

Although camera runtime permission is already implemented from #15 , but for record audio still not implemented

@hendrawd Thanks for taking the time to fix this! Have a good Christmas break


Docker hub image for version 12.4 contains cryptominer

After ~3 days of uptime postgres process spawns 8 processes with autogenerated names like "0DJbp5eh" which eat up all CPU cores and RAM. Also this processes open connection to Hetzner (<IP_ADDRESS>) with some sort of "empty" http server which listens on 80 and 8080 ports.

Yes, the "official" one.

related: https://github.com/docker-library/postgres/issues/664#issuecomment-579871694

Indeed, this is most likely due to having your instance exposed on the public internet (or you have an attacker within your network, such as another previously compromised machine), and you've suffered a compromise.

I don't think that's the case: this problem manifest by the schedule on 4 different unrelated machines in different networks (3 dev workstations and CI) and only after delay. Delay is always the same, approximately 3 days. Our company is switching to another image, so if issue is resolved, then your "official" image is definitely compromised.

BTW, one of workstations has ufw rules that block all traffic except for incoming ssh, and postgres container isn't permanently up, but cryptominer still starts if I forget to shut down this container for the weekends.

When you forward a port on a Docker container, Docker uses iptables directly to expose that port externally, so it is very likely bypassing all ufw rules unless you've gone to extra effort to ensure the Docker chain happens after the ufw one (and then maintain/verify that ordering periodically).

Additionally, the source code for our image is completely open and available for review here -- you should be able to trivially build it locally as well, if you suspect that our builds are the culprit.  I think you'll find that Docker has bypassed your firewall.
Alternatively, you could try adding a more complex password for any/all users on the database instances, which should also be a deterrent.

Can you, please, recomend a way to sandbox docker build process, so I can ensure it isn't downloading anything malicious? Your build script while being opensource looks obfuscated.

It's not "obfuscated" as such, but it is a little bit complicated because it needs to build from source for architectures that the PostgreSQL project doesn't publish official release binaries for.
Doing docker build already does some amount of sandboxing, but if you want to also sandbox the network accesses you'll have to pre-download all the files it needs (local Debian mirror, local PostgreSQL APT repo mirror, etc).
For help with these things (and with mitigating your other issues), I would recommend a dedicated support forum such as the Docker Community Forums, the Docker Community Slack, or Stack Overflow.


Integrate ChatBot structure

Ref:

https://dev.to/novu/building-a-real-time-chat-with-websockets-novel-and-clerk-40ac

Need to first find a way to convert Resume / LinkedIn data into embeddings
Then perform to search on the embeddings created above for answers


InvalidArgumentError of run_CIL.py

Hi @felipecode
I suffer from an issue when running run_CIL.py of invalid argument error as:
InvalidArgumentError (see above for traceback): Cannot assign a device for operation input_image: node input_image (defined at /home/XXXXX/imitation-learning/agents/imitation/imitation_learning.py:42) was explicitly assigned to /device:GPU:0 but available devices are [ /job:localhost/replica:0/task:0/device:CPU:0, /job:localhost/replica:0/task:0/device:XLA_CPU:0 ]. Make sure the device specification refers to a valid device. The requested device appears to be a GPU, but CUDA is not enabled.
[[node input_image (defined at /home/XXXXX/imitation-learning/agents/imitation/imitation_learning.py:42) ]]
Thanks in advance.

Problem fixed by upgrade CUDA to 9.0 and uninstall and install tensorflow-gpu.
Issue close!


Fix LicenseInfoInSnippet property name

In the Python tools (including the examples in the repo), the https://spdx.github.io/spdx-spec/v2.3/snippet-information/#96-license-information-in-snippet-field property is named licenseInfoFromSnippet. However, as can be seen in the spec, it should be called licenseInfoInSnippet.
edit: This also applies to files. The property should be called licenseInfoInFile

fixed by #289


CommonsChunkPlugin has been removed

Error: webpack.optimize.CommonsChunkPlugin has been removed, please use config.optimization.splitChunks
describe your changes...

[ ] Read and sign the CLA. PRs that haven't signed it won't be accepted.
[ ] Make sure your PR complies with the writer's guide.
[ ] Review the diff carefully as sometimes this can reveal issues.
Remove these instructions from your PR as they are for your eyes only.

#444
https://webpack.js.org/guides/code-splitting/#prevent-duplication
英文网站并没有这些内容，这是你自己添加的吧，可以向上游英文仓库提交 pr，英文仓库接收 pr 后，中文仓库再合并更新和进行翻译。


Sanitise meta title and description

Oops. Fixes the left tab to look like the right tab:

I also removed the title link from pipeline pages. I'm not sure why that was there, it's inconsistent with the rest of the site and doesn't really add anything.

Possible to have nf-core >> sarek instead?

Possible to have nf-core » sarek instead?

Possible to have that, yes. But it's considered bad practice in web design circles. Imagine you have a bunch of different nf-core tabs open in a browser window and they're all squished: if it says nf-core first, then all you can see is nf-core repeated over and over. If it comes last, then you have useful information in the limited characters that you can see..

This is why you are developing the website and I am not!


VAAPI can't use other rate control profiles of GPU

When deploying in Openshift, only one rate control profile Is available:

We have installed the gpu driver from 1.1.0 (with firmware)
version: intel-data-center-gpu-driver-container:2.0.0-5.14.0-284.28.1.el9_2.x86_64  and can access the GPU with OpenCL and other utilities with no issue.
It seems that one possible cause of the limitation may listed here: https://github.com/intel/media-driver?tab=readme-ov-file#known-issues-and-limitations
The GPU configuration sets the mode of enable_guc to 3 (see attached doc syskerneldebugdri1i915_.txt), but according to
https://wiki.archlinux.org/title/intel_graphics#Enable_GuC_/_HuC_firmware_loading we should see the message i915 0000:00:02.0: [drm] HuC firmware i915/icl_huc_9.0.0.bin version 9.0 authenticated:yes
but instead,

It may be possible that HuC fw is not loaded correctly, and the rate control isn't available

Test Dockerfile to see VAAPI through vainfo command:
vainfo.zip

Note: This happens on Openshift 4.12.7, as well as OpenShift 4.13.11

Thanks for submitting the issue @brgavino. We have not support media driver so far. Without the media driver, the driver container you have used works with no issues right? @uMartinXu any thoughts here?

Thanks, @brgavino @vbedida79, The Flex GPU media features are in plan but have not been supported yet.
We can create a feature request github issue and address this feature request. And partners like @brgavino can give more clear requirments there.

That's fine, let's create the feature request - it would be helpful to add a note to documentation that media driver support isn't available in OpenShift yet. The dependency (GPU Plugin) does support it on other platforms, otherwise - so it is unclear.

looks like there is some issue with "mei_gsc" kernel module in the backport driver.
[  155.993631] mei_gsc i915.mei-gscfi.19712: FW not ready: resetting: dev_state = 2 pxp = 0
Any idea to fix it quickly?


Fix gateway injection when using SPIRE

Please provide a description of this PR:
When using SPIRE, it’s necessary to define an injection template and to indicate to use it by default for sidecars, using the following Helm values:
  sidecarInjectorWebhook:
    templates:
      spire: |
        spec:
          volumes:
            - name: workload-socket
              csi:
                driver: "csi.spiffe.io"
                readOnly: true

This works as intended.
Then, to use it for a gateway, it’s necessary to add an annotation on the gateway pods, using the following Helm values:
  podAnnotations:
    inject.istio.io/templates: "gateway,spire"

However, it doesn’t work, the following error is shown in Kubernetes events:
Error creating: Pod "gateway-q68cn" is invalid: [spec.volumes[0].csi: Forbidden: may not specify more than 1 volume type, spec.containers[0].volumeMounts[0].name: Not found: "workload-socket", spec.containers[0].volumeMounts[1].name: Not found: "workload-socket"]

This PR fixes the issue by copying what is done in the sidecar injection template to the gateway injection template.

Hi @yann-soubeyrand. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

/ok-to-test

please add release notes

@yann-soubeyrand: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
313bcf9fb85959ced760555f8831c6db512074fb
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@yann-soubeyrand: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
313bcf9fb85959ced760555f8831c6db512074fb
link
true
/test release-notes

gencheck_istio
313bcf9fb85959ced760555f8831c6db512074fb
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@yann-soubeyrand: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
313bcf9fb85959ced760555f8831c6db512074fb
link
true
/test gencheck

release-notes_istio
4c8529d5f3c6f2671e3781bbe13a146c980258b3
link
true
/test release-notes

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@yann-soubeyrand: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
4c8529d5f3c6f2671e3781bbe13a146c980258b3
link
true
/test release-notes

gencheck_istio
4c8529d5f3c6f2671e3781bbe13a146c980258b3
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@yann-soubeyrand: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

gencheck_istio
4c8529d5f3c6f2671e3781bbe13a146c980258b3
link
true
/test gencheck

unit-tests-arm64_istio
63646a06e73736ca62ddb5a5cf1d8778bd4019d3
link
true
/test unit-tests-arm64

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@yann-soubeyrand: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
63646a06e73736ca62ddb5a5cf1d8778bd4019d3
link
true
/test unit-tests-arm64

gencheck_istio
63646a06e73736ca62ddb5a5cf1d8778bd4019d3
link
true
/test gencheck

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

Yopu can see a lot of similar tests in pkg/kube/inject/testdata/inject used in this function:
pkg/kube/inject/inject_test.go
54:// TestInjection tests both the mutating webhook and kube-inject. It does this by sharing the same input and output
56:func TestInjection(t *testing.T) {

We may or may not want to actually do this still but fwiw it can also be accomplished today like:
  sidecarInjectorWebhook:
    templates:
      spire: |
        spec:
          volumes:
            - name: workload-socket
              emptyDir:
              csi:
                driver: "csi.spiffe.io"
                readOnly: true


Updated Bucks County ESRI token

Not sure how often this changes.

Hm, for Tennessee we set up a script to do the token out of band. Might be necessary here.

I used https://gisweb.co.bucks.pa.us/apps/floodplainviewer/ and then looked at the network requests to find the token.

Makes sense! I verified that I could find the token and get the data. Would you mind making two changes to this PR?

Update the data URL to https://s3.amazonaws.com/data.openaddresses.io/cache/us/pa/bucks.zip, a GeoJSON cache of the live server.
Add a website tag pointing to https://gisweb.co.bucks.pa.us/apps/floodplainviewer/

Thanks @migurski  for the help. I think I got it now.


Update cloudknox-howto-recommendations-rule.md

Minor updates to make the doc consistent to the current UX.

@marcelodiiorio : Thanks for your contribution! The author(s) have been notified to review your proposed change.


error during demo using video

Hi, Great work!
I tried doing inference using images and it worked well, but during the inference using video, I got this error.

Any thoughts on how to get through it?

Thanks for your interest.
Currently, we do not have support for video input. The original visualizer in demo.py (from AdelaiDet) would require some modifications before it can be used with videos. We recommend you try the image visualizer only.


chore(deps): update elliptic to fix CVE-2024-48949

Description
Please explain the changes you made here.
Which issue(s) does this PR fix

Fixes #?
https://issues.redhat.com/browse/RHIDP-4417

PR acceptance criteria
Please make sure that the following steps are complete:

[ ] GitHub Actions are completed and successful
[ ] Unit Tests are updated and passing
[ ] E2E Tests are updated and passing
[ ] Documentation is updated if necessary (requirement for new features)
[ ] Add a screenshot if the change is UX/UI related

How to test changes / Special notes to the reviewer

/cherry-pick release-1.3


chore: add strict-boolean-expressions rule

Description
Add @typescript-eslint/strict-boolean-expressions eslint rule for packages.

/ok-to-test

/ok-to-test

https://github.com/appsmithorg/appsmith/actions/runs/6429347315

@KelvinOm - Please always merge with latest release & then start run. AutoHeight_Form_spec.ts is fixed & merged now.

/ok-to-test

@KelvinOm - Please always merge with latest release & then start run. AutoHeight_Form_spec.ts is fixed & merged now.

@Aishwarya-U-R Yeah, I'm practicing it. The previous launch was yesterday.

/ok-to-test

/ok-to-test


Proper handling of list fields

Moved field handling to a separate function and added logic to correctly process nested lists.
Code diff looks way more complex than it actually is. Copied everything that originally was under else if ($field['type'] !== 'ignore') { into a new function, so that it can be called from multiple places.
Fixes https://github.com/getgrav/grav-plugin-admin/issues/273

Thanks!


Please add Nashville local broadcast channels

Guide
https://iptv-org.github.io/epg/guides/en/tvpassport.com.xml
Channels
abcwkrn.us
cbswtvf.us
foxwztv.us
nbcwsmw.us
Notes
Thank You

The EPG for ABC Nashville, TN can be found in https://iptv-org.github.io/epg/guides/en/tvpassport.com.xml under WKRNDT1.us


whether it need a spectrogram of each audio during training？

I found that the style image (style_img) needs to be used in training, but I looked at your data processing code. I found that there was no part about how the image came from, only the code to determine the image path according to the voice path.Does this mean that it is necessary to generate a Mel spectrogram for each audio.

Oh sorry...
I will update soon

Looking forward to your update.I wonder if you can give me an email address to communicate.Thanks.

Hi @freshwindy.
I update code. See make_mel_style.py.
I also update model, see /MIST_tacotron and delete /tacotron2 and then change directory name /MIST_tacotron -> /tacotron2
It is make you easy to train.

Hi,Thank you for sharing.I have checked your updated code, but I still have a question, that is, I found your updated make_ mel_ Style.py also adds the image style migration model. Is this necessary for image processing? Because I saw this in your model also have style_encoder,which will lead to re-use of image style migration.

Hi, @freshwindy .
I use mel-spectrogram feature like image. So we need image precessing.
GST tacotron uses token extracted from mel-spectrogram as feature. But MIST tacotron uses image style transfered mel-spectrogram extracted from mel-spectrogram(make_mel_style.py) as feature

Close due to inactivity.


Delete hidapi recipe

This recipe was not used in the builds, instead recipe from meta-openembedded is
being used. Surplus metadata should be deleted.
Refs:
https://github.com/Dasharo/dasharo-issues/issues/770
https://github.com/Dasharo/dasharo-issues/issues/769

Thanks


Long Seed

You can add 'long' seed for generate noise ?

Adding support for 64 bit seeds would lower performance, and has very little benefit to the usefulness of the library. What do you want 64 bit seeds for?


React Native - Hermes Android path wrong for react-native 0.69.0

Description
As of 0.69 of react native, Hermes is managed by React Native and as a result the hermes path is different to what AppCenter Expects.
Repro Steps
Please list the steps used to reproduce your issue.

Run appcenter codepush release-react on a react-native 0.69 project on android

Expected behavior
It distributes the app.
Details

It attempts to get hermes from node_modules/hermesvm/linux64-bin/hermes resulting in

Error: spawn node_modules/hermesvm/linux64-bin/hermes ENOENT

I'm pretty certain that the problem is here https://github.com/microsoft/appcenter-cli/blob/master/src/commands/codepush/lib/react-native-utils.ts#L521
I think we basically need
  return path.join("node_modules", "react-native", "node_modules", "hermes-engine", getHermesOSBin(), "hermesc");

Duplicate my mistake


Filter translations by key and value

Allows translations to be filtered by both key and value as per screenshots below:

Thanks :)


Removing global variable to improve unit testing

Proposed changes
This Pull Request resolves #4217. It focuses on removing a global variable thereby improving unit testing.
Types of changes
What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

[ ] New feature (non-breaking change which adds functionality)
[x] Bugfix (non-breaking change which fixes an issue)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices applies)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the commit for DCO to be passed.
[x] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[ ] I have added necessary documentation (if appropriate)

Dependency
None
Special notes for your reviewer: None

Okay, checking for any potential errors

@Ratul-Saha-003 are you working on this anymore?


[Core] Use make_shared in make factory functions

What
In our various make factory functions, use std::make_shared rather than constructing a std::shared_ptr directly.
Why
make_shared is best practice, not least because it co-locates shared_ptr metadata with the allocated type, so that an additional pointer hop is removed.
However, it's not trivial for types with a private constructor.  There are a few possible workarounds however.
Notes
A particular pattern (from the above linked post) that works well in our case is to have an inline struct that inherits from the parent and makes its constructor public, e.g.
ManagerPtr Manager::make(managerApi::ManagerInterfacePtr managerInterface,
                         managerApi::HostSessionPtr hostSession) {
  struct EnableMakeShared : Manager {
    EnableMakeShared(managerApi::ManagerInterfacePtr managerInterface,
                     managerApi::HostSessionPtr hostSession)
        : Manager(std::move(managerInterface), std::move(hostSession)) {}
  };

  return std::make_shared<EnableMakeShared>(std::move(managerInterface), std::move(hostSession));
}

Other possible solutions:

friend a custom allocator and use std::allocate_shared instead of make_shared.  This requires copy-pasting from the STL implementation, yucky.
Have a public move constructor, then in create we can use private constructor to construct on the stack, then use the public move constructor for make_shared.

Another possible solution:

A public constructor that takes a private tag type as an argument - see https://stackoverflow.com/questions/54454620/why-cant-i-access-the-private-constructor-in-my-static-function-as-below/54456533#54456533

Closing as we previously backed-out of using this change in a real PR for readability reasons.


Added WebCodecs API

https://www.w3.org/TR/webcodecs/

Hi! Thanks for your contribution.
I've tried to use this API but I've noticed that the new() function is missing for the VideoEncoder and VideoDecoder (and probably more structs).
Am I missing something? Is there an alternative way to construct these?

I've tried to use this API but I've noticed that the new() function is missing for the VideoEncoder and VideoDecoder (and probably more structs).
It's a long problem in wasm-bindgen - most of the newer standards use the new syntax for constructors, and the Rust code generator doesn't support it, The support was added in #2842, but it's not merged yet. If you really need to test it right now, you can fork the branch and generate the bindings yourself.

Thanks a lot for the explanation!

@Sixshaman how did you go about generating the feature flags for this? I tried to add the share API a few weeks back, but was unable to figure out how to auto generate the proper feature flags.

@Sixshaman how did you go about generating the feature flags for this? I tried to add the share API a few weeks back, but was unable to figure out how to auto generate the proper feature flags.

When you run cargo run --release --package wasm-bindgen-webidl -- webidls src/features, the flags get written to the "src/features" file. Simply copy them to Cargo.toml afterwards.


prepare release 2.0.3

please build

please build

@jmini Thanks for spotting this! just released 2.0.4 correcting the issue.


Setting OperatorPipelinesRelease does not fetch the version

Bug Description
When setting the OperatorPipelinesRelease for OperatorPipeline like this:
operatorCertification.OperatorPipeline{
		ObjectMeta: metav1.ObjectMeta{
			Name:      PipelineName,
			Namespace: testingNamespace,
		},
		Spec: operatorCertification.OperatorPipelineSpec{
			ApplyCIPipeline:          true,
			ApplyHostedPipeline:      false,
			ApplyReleasePipeline:     false,
			GitHubSecretName:         githubSecretName,
			KubeconfigSecretName:     kubeconfigSecretName,
			OperatorPipelinesRelease: "v1.0.98",
			PyxisSecretName:          pyxisSecretName,
		},
	}

When running this I get this error:
status:
  conditions:
  - lastTransitionTime: "2023-10-25T14:05:35Z"
    message: Local repo unavailable
    observedGeneration: 1
    reason: NotFound
    status: "False"
    type: GitRepoReady
  observedGeneration: 1

Looks like everything is related to this part of the code https://github.com/redhat-openshift-ecosystem/operator-certification-operator/blob/main/internal/reconcilers/pipeline_git_repo.go#L59 where we only get a branch and not the tag, so we don't get a Release but rather we only get a branch.
This is kind of difficult when there's a small change like the one reported here https://github.com/redhat-openshift-ecosystem/operator-pipelines/issues/530 because we should be getting a version to run the certification pipeline

hi @sxd thanks for reporting this issue. We'll take a look at the best way to be able to use a branch or a tag.

Hi @acornett21
We hit this issue again because of this commit https://github.com/redhat-openshift-ecosystem/operator-pipelines/commit/1651f69c9e2a6df14e15a82d3167ec34501ab487 now we can't run anything because we can only use main and not the release version.
There's a way I can test your patch? like a development version of the operator I can deploy ?
Regards!

@sxd version 1.1.3 has been released and should be in your clusters catalog to use. Let us know if you have any issues.

@acornett21 thank you so much!! I'm going to test it and try it


[TACHYON-1516] Clean up WorkerContext config after tests

https://tachyon.atlassian.net/browse/TACHYON-1516

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/7699/
Test PASSed.

Thanks for the clean up. LGTM


fix: When the trailing slash option is the default, don't remove it on the error page.

For example, when hosting with AWS Amplify (S3), if index.html does not exist, it will be redirected to the path with the trailing slash, resulting in a redirect loop.
The following settings will remove the trailing slash when a non-existent page is accessed, which should not be removed since the default Trailing Slash option does not redirect.
Nuxt configuration

target : static
router.trailingSlash : undefined (default)

Nuxt-i18n configuration
i18n: {
    strategy: 'prefix_and_default',
    lazy: true,
    ...
}

I ran into a similar problem with this one when using the function localePath with default nuxt trailingSlash option (undefined).
In my case I have to use both the path with trailing slash and without trailing slash which is seems impossible with current localePath.
Example:
<nuxt-link to='/a'>...</nuxt-link>                 // => href=/a
<nuxt-link to='/b/'>...</nuxt-link>                // => href=/b/
<nuxt-link :to='localePath("/a")'>...</nuxt-link>  // => href=/en/a
<nuxt-link :to='localePath("/b/")'>...</nuxt-link> // => href=/en/b

I'm not sure how to fix this but I think we should respect the behavior of this trailingSlash option in the same way as nuxt do. To have a way that isn't just always append trailing slash or always remove it.

I ran into a similar problem with this one when using the function localePath with default nuxt trailingSlash option (undefined).
In my case I have to use both the path with trailing slash and without trailing slash which is seems impossible with current localePath.
Example:
<nuxt-link to='/a'>...</nuxt-link>                 // => href=/a
<nuxt-link to='/b/'>...</nuxt-link>                // => href=/b/
<nuxt-link :to='localePath("/a")'>...</nuxt-link>  // => href=/en/a
<nuxt-link :to='localePath("/b/")'>...</nuxt-link> // => href=/en/b

I'm not sure how to fix this but I think we should respect the behavior of this trailingSlash option in the same way as nuxt do. To have a way that isn't just always append trailing slash or always remove it.

I'm starting to realize that for static hosting setting route.trailingSlash to true might be required and the module should either enforce that or strongly recommend it at least (see also #1037).

In my case I have to use both the path with trailing slash and without trailing slash which is seems impossible with current localePath.

I'm curious why do you need to use paths with trailing slash and whether that's because you are statically hosting your generated code?

I'm starting to realize that for static hosting setting route.trailingSlash to true might be required and the module should either enforce that or strongly recommend it at least (see also #1037).

In my case I have to use both the path with trailing slash and without trailing slash which is seems impossible with current localePath.

I'm curious why do you need to use paths with trailing slash and whether that's because you are statically hosting your generated code?

No, In my case it's a bit messy. I use universal mode run behind reverse proxy server which serve multiple applications. Some route that created by CMS may have a trailing slash. So I am concerned about this.
Go to another application

I think we should at least have an option that can preserve trailing slash.

No, In my case it's a bit messy. I use universal mode run behind reverse proxy server which serve multiple applications. Some route that created by CMS may have a trailing slash. So I am concerned about this.
Go to another application

I think we should at least have an option that can preserve trailing slash.


What is a "zone" in this API, and how does it relate to Lutron app rooms?

Background:  I've been programming with the old telnet-style Integration Protocol for years (large RRa2 install), but am just now looking at LEAP.
I got a Caseta starter kit (hub, pico, plug-in module) and have started writing code using this library.  My intent is use it for RRa3 eventually, but the Caseta starter kit was cheap.
I'm trying to figure out how to group the devices discovered by the room assigned in the Lutron app.  Questions:

What is the "zone" field in the device data returned by the API?
What is the "area" field?
If one of the above represents the room assigned in the app, is there a way to map that field to the room name (other than parsing it from the "name" field?
Why no get_occupancy_groups() method?  There are methods for scenes, devices, buttons, etc.

Ok, the area field links back to the name using the bridge.areas dict.
Still not sure what the zone represents.  Also, seems like those dicts should have cover methods.


Add rule names back to rules

Please describe the feature or suggestion.
Rules used to have a "Name" that uniquely identified it.  That was changed a while ago to an opaque "Id" field.  SARIF supports both of these, and ideally, the rule names should come back and live alongside the rule ids.
Additional context
No response

Duplicate of #198.


[Outlook] (add-ins) Update instructions for accessing add-ins

Docs Build status updates of commit af95e0b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/concepts/privacy-and-security.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 8154923:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/concepts/privacy-and-security.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Add option in SCons to clone env variables

This allows custom environment variables to be used during the build, which is useful when using alternative compilation tools such as caches and distributed build systems.
I've been using this locally for a while and it would be nice to have it upstream.

Renamed the option to import_env_vars.

Thanks!


Part 1-4 of AboutMe path, with only the core critical files

This is a new pull request without the extraneous files that the older pr had.

second commit is for steps 5-8 for the second part of the project, everything works functionally and is ready to be developed after the PR is approved


Specify custom Vitest config

Hi! Thanks for your work on this package @nickbreaton!
I'm using this package with my vitest.config.js but I have existent configuration here:
{
  plugins: [svelte({ hot: !process.env.VITEST }), Icons({ compiler: 'svelte' })],
  test: {
    watch: false,
    clearMocks: true,
    environment: 'jsdom',
    include: ['test/**/*.ts'],
    exclude: [
      'node_modules',
      'dist',
      '.idea',
      '.git',
      '.cache',
      'test/__mock__/**/*.ts',
      '.coverage',
      '.svelte-kit',
    ],
    deps: {
      inline: ['@splidejs/svelte-splide', 'msw', /@sentry/],
    },
    coverage: { reporter: ['lcovonly'], reportsDirectory: '.coverage' },
  },
}

I would like to be able to provide this config along with the one provided by the package to Vitest. Would this be possible? Thanks in advance!

I would recommend putting it inside your svelte.config.js's vite section like this:
https://github.com/nickbreaton/vitest-svelte-kit/blob/ef2dfd132f378ced89bdfc350df80fa57486bf56/tests/vite-plugins/svelte.config.js#L12-L14
You don't need the svelte plugin in there though, since it will already be included.
If you need to conditionally include something in your vite config just for test, you can use the VITEST environment variable as mentioned in your docs within the svelte.config.js file as well:
https://github.com/nickbreaton/vitest-svelte-kit/blob/ef2dfd132f378ced89bdfc350df80fa57486bf56/tests/process-env-vitest/svelte.config.js#L13


Update aws-java-sdk-core to 1.12.753

About this PR
📦 Updates com.amazonaws:aws-java-sdk-core from 1.12.459 to 1.12.753
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.amazonaws", artifactId = "aws-java-sdk-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #786.


Fix get_typed_fund extra param in benchmark

Commit b0939f662 recently removed extra param which breaks building benchmark

@alexcrichton PTAL


Support Circle CI

Coverage remained the same at 69.004% when pulling 4d0c9c4fdcd005439ce2aae9f1754df71afa9b3c on circle-ci into b65ec63cd1334b92d0ed8a9d0bbd4f73776ab94c on master.

Coverage remained the same at 69.004% when pulling 0bd42d42cd1e37f0d0abd97d4fb30c4d202e6938 on circle-ci into b65ec63cd1334b92d0ed8a9d0bbd4f73776ab94c on master.

Coverage remained the same at 69.004% when pulling 7e3386d333df6ae4d66b2a4a2aee65a61df84af8 on circle-ci into b65ec63cd1334b92d0ed8a9d0bbd4f73776ab94c on master.

Coverage remained the same at 69.004% when pulling 7e3386d333df6ae4d66b2a4a2aee65a61df84af8 on circle-ci into b65ec63cd1334b92d0ed8a9d0bbd4f73776ab94c on master.


Error: path could not be found

Hello there!
I have installed Pythonia succesfully using npm and when i'm trying to import it in my code. Its shows following error

error: Error: Unable to resolve module path from F:\RNProjects\InnoVital_Project1\InnoVital\node_modules\pythonia\src\pythonia\index.js: path could not be found within the project or in these directories:
node_modules\pythonia\node_modules
node_modules
7 | const { StdioCom } = process.platform === 'win32' ? require('./StdioCom') : require('./IpcPipeCom')
8 |
9 | const { dirname, join, resolve } = require('path')
|                                             ^
10 | const { PyClass, Bridge } = require('./Bridge')
11 | const getCaller = require('caller')
12 |
can you help me why i'm getting this error? and how to resolve it?

Please update your Node.js version and npm from https://nodejs.org/, then install the package to a new project after running npm init. This seems like an broken environment issue.


Make the delay in between temperature and hydration renders configurable

A user requested this from me after you said you were tight on time.
Tested to work on 1.15.2.

Awesome thanks for doing that, I'll  merge this into the project. I've got planned to add another option for how this can work that I'll add on top of this at a later date.