Change output file extension to mp3

Change output file extension to be consistent with code snippet that shows pipe to an mp3 file instead of wav.

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

#label:"aq-pr-triaged"

#sign-off

@nitinme: I'm sorry - only the author of this article, @v-jaswel, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.


Can I make number below each circle?

Hello, I want to move the number 1,2,3 below each circle.
How can I make it?

The wheel items are just drawables - this is the downside to if they were views it would be much easier to achieve what you want. I think it's possible but not straight forward. You would have to look at the code to see how it renders the wheel items and how the bounds are determined


Configure the control to allow transparency

Issue 59
Changing the frame buffer format to A8R8G8B8, the alpha channel of the color passed to the function GL.ClearColor will determine now the level of transparency of the control.

I'm still slightly suspicious of the gamma thing, hopefully varon can answer what that was about.
But otherwise I think this is a good addition.
Really appreciate the PR, hopefully I'll have some time soon to make a new release of this package with this PR in it.

This is a fantastic addition! Could we hope to see this merged soon? Thanks to you both.

I will merge this, and if this results in gamma issues I hope that people will open an issue here so we can fix it in that case.


Issue9 throttling

Fixes #9
Adds throttling method to base consumer class. Throttling can be used to limit the rate that the consumer application processes messages. Limiting the process rate helps to prevent overloading of applications that the consumer accesses.

@mshmsh5000 As requested ^^ The image processing consumer can be "throttled" to protect against overloading the Drupal site.


Figure out how to determine a 'Linger Rate' indicator

"how long you stared at a graphic while scrolling through a story"

Aly suggests displaying just a histogram at first, not to bucket anything.


Build and dockerize the project under windows

using ./gradlew dockerize under windows will lead to a confusion inside the Dockerfile
because how paths are handled in windows
for example running the current command in windows
./gradlew.bat :edc-controlplane:edc-controlplane-memory-hashicorp-vault:dockerize
will lead into this error

> Task :edc-controlplane:edc-controlplane-memory-hashicorp-vault:dockerize FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':edc-controlplane:edc-controlplane-memory-hashicorp-vault:dockerize'.
> Could not build image: COPY failed: file not found in build context or excluded by .dockerignore: stat build\opentelemetry-javaagent.jar: file does not exist

Expected behavior
to successfuly build the code
Screenshots/Error Messages

Add any other context or information about the problem here.

Used version: release/0.5.1
OS: Windows
Docker Version: 24.0.5

Possible Implementation
replace the (windows slashes) in the build.gradle.kts for OTEL_JAR to make it work inside the Dockerfile

The dockerfile is intended for our build process, which runs on Linux.  The official deliverable of tx-edc is a helm chart plus the prebuilt images. Why do you need to build your own connector image, and why do you need the dockerfile for that to be hosted in the tx-edc repository (as opposed to: your own infrastructure)?


hackernoon article images broken

Hi,
The article describing your work seems broken.
https://hackernoon.com/diy-redux-with-rxjs-rxdx-23163a87ade1
Your face is displayed instead of code snippets. Ego ? ;)

@heticeric Sorry but I didn't receive any notification about your issue, therefore, I was not aware of your message. Thanks for letting me know. I think while hackernoon migrating the articles they messed up. :( I'll ask them about it.


Remove Configuration from Evaluator Prompty

Description
This PR removes the default configuration from the evaluator prompty files so that the model config the user passes in is the single source of truth.
All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

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

/check-enforcer override


Build GC for nix development environment.

Overrides the boehmgc package to apply patch needed for mt support.
Quick followup to discussion in crystal-lang/crystal#9727. A little simpler to submit changes here rather than inline on that thread. I noticed that you already have the patch in the distribution-scripts repo. This applies that, then feeds in the result for the dev environment uses.
There still looks to be an issue with llvm_ext under musl, but hopefully this pushes things in the right general direction.
Note: SHA’s have changed on the binaries too as switched them over to fetchTarball to keep the extracted version in the nix store as opposed to the archive.

Cool! Thanks. I iterated a little more to match how the gc is build in distribution-scripts. A couple of flags and including libatomic.
Do these changes look good to you?

Nice. The nixpkgs that this is pinned against already has boehmgc-8.0.4 and libatomic_ops-7.6.10 so you can just lay on these changes there.
The only flag it looks to have trouble with is --disable-shared, as that drops some expected build outputs. I haven’t been able to dig into that, but not sure if this is an issue?

bdw-gc's readme and distribution-scripts use the nested checkout structure to build bdw-gc with atomic operations capabilities. Maybe that scheme no longer applies since I think it depends on the C compiler version support for atomic operations. But I would rather build things as similar as they are build for now to avoid changing too much.
Building the gc does not involve too much time and the cache is already setup for darwin.
I am including 91378a68d5473ede0589088230e9b9a1808914db in the upstream PR :-)
On another stories, are you aware of some documentation for using binaries and libraries  in non-nix environment that were build with nix. Maybe nix's patchelf can be used in that direction. But I was unable to find information of that scenario. This would allow us to get rid of omninus in our build process.

Ah, I missed that in the readme completely! Definitely makes sense to take your approach, or if you want a minor cache bump symlink to it in the nix store from that location.
I've not had to go the other way (building a dynamically linked binary for use outside of a nix environment), but patchELF does look like it would be capable up updating those paths in either direction. This would defeat the purpose of a deterministic build environment though as you're back linking to unknown deps. I'm unfamiliar with your exact needs here though so this could satisfy them.
I'll close this PR so that conversation isn't fragmented between here and the core repo. Hopefully one of the other nix / crystal intersectee's may be able help out with some more advice there too.

FYI, I aim to see if I can use nix as a build environment for the .tar.gz packages that currently use docker & omnibus and they are not fully reproducible. But they aim to work in non nix environment, so that is one of the mid-term goals in mind.
Thanks for all the input! 🙇♂


FEAT: Support for Individual PDF (requires sphinxcontrib-jupyter=0.5.0)

This PR adds support for individual page PDF construction.

[ ] requires sphinxcontrib-jupyter=0.5.0 https://github.com/QuantEcon/sphinxcontrib-jupyter/pull/211

hey @AakashGfude if we are going to keep anju_pdf in the Makefile -- lets update the name to constructor_pdf otherwise let's delete and just keep it local.

[ ] update aws.admin tools when this is merged


Remove call to nonexistent member seekpos() of std::fpos

Boost-iostreams failed with error C2039: 'seekpos': is not  a member of 'std::fpos<_Mbstatet>'.
See http://eel.is/c++draft/fpos -- to get to an offset you can convert to int; now there is no seekpos member.

@alexkaratarakis , please help review this, thanks!.

Thanks! This should be upstreamed https://github.com/boostorg/iostreams


As a user, I want challenge documentation to be available so that I can learn about the topics before I apply them in a challenge.

Acceptance Criteria

[ ] Users can access readily available documentation that is concise and well-written.
[ ] Users can have the documentation open at any point, even with a challenge running.

...

The best documentation I could find was from https://www.w3schools.com/ for html specifically. Planning on summarizing in our documentation but providing hyperlinks to docs.

Waiting for our documentation to end up on the site before we can complete this issue.

Marking this as complete since @DungLe2911 was able to get it working.


Git commit throws error when no user.name/user.email is known in Git repo

When committing pages to the Git repo (PushyRepo::commit()) , the Git library complains that user.name and user.email are unknown. They are however available at the global level.

Removing --author from execute command does not solve the issue
Adding a name <email> hardcoded in the commit statement does not help
shell: Executing commit without --author works fine.

A side effect of this is that changes have been staged and will no longer be visible in the list of pages in Admin. Manual unstaging is needed.
Suggestion:

When commit throws an exception, all staged items should be unstaged.

Interesting. Yes there is great potential for git errors and they should be handled better. I don't know if it's best to wait for #11 though.
I thought I had coded the commit wrapper to use the logged in email/name as fallback, or perhaps I just thought it or added a TODO comment.

* When commit throws an exception, all staged items should be unstaged.

Agree, or is there some equivalent of database rollback available in PHP? That is, encapsulating statements into a "transaction".

Agree, or is there some equivalent of database rollback available in PHP? That is, encapsulating statements into a "transaction".

I'm afraid that as long as Git doesn't provide it, it would be impossible for any language to implement a language construct for it...
I'm also afraid that another library will not provide such action. It will probably remain a manual action inside the catch. Does the current lib provide a method to remove staged items?

I'm not seeing the original problem reported here. My client made a commit through Pushy that was correctly attributed to her name and email, even though git is configured to use something else on that server.

I thought I had coded the commit wrapper to use the logged in email/name as fallback

Actually it uses it first with a TODO to "add a fallback".

The username/email will have to be added to the config of the local Git first. Can the current lib do that?

I don't know and the library needs replacing anyway. Perhaps I will add the author configured for the repo as a further setup requirement to the docs. I am unsure about the plugin going too far into repository metadata. I guess because I don't want it to be going into dangerous territory, or being perceived that way. It's kind of about building trust (I don't know).

I'm also afraid that another library will not provide such action

That's probably right. I hoped one might emulate a rollback using some magic with PHP.

I'm not seeing the original problem reported here.

Replying to myself, I thought just earlier that I really should be setting up a test site for working on this plugin so I can properly try to reproduce issues and generally work in safety. I have been working very carefully in a real repo which is sure to bite me one day :/


Support for Postgres citext datatype

Great work on these beam nuggets!
I successfully used the RelationalDB read to connect to my PostgreSQL DB and save the table contents to a JSON file.
One thing I noticed, however, is that this doesn't support the Postgres citext datatype. I found a workaround by using this: https://github.com/mahmoudimus/sqlalchemy-citext
I wanted to bring to your attention in case you can incorporate into the nugget. I would attempt a contribution / pull request but I am new to Python.

Happy it worked for you!
You can submit a PR as you suggested.


MargarineBot v2.0 Development

It's official! MargarineBot v2.0 is in development!
MargarineBot has outgrown some of its systems and has become a bit constricted in what it can support. Not to mention, the feature backlog is split 50:50 for these features and features that can still be added to v1. So, it is the perfect time to upgrade Margarine's systems!
With this update, I am hoping that the changes will bring a lot more flexibility and freedom when it comes to adding new features that need a bit of change. Nearly every aspect from databases to speech to user commands is on the table for change. But, hopefully, not too much change to alienate v1 from v2 and make v2 migrations difficult.
Planned Changes
I have a lot of ideas and work planned to happen for this release. Some items may come in future releases of v2 but this is a list of what to expect from v2.
Database management is getting a lot of updates in this update. A major priority with this update is to allow hosters to use a database provider of their choice via official plugin or self-made. Official support will include SQLite and Postgres but MongoDB & MySQL may also be included. On top of this, guild and client settings will be merged into the same database as MargarineUser profiles instead of a hybrid JSON/SQLite setup with v1.
MargarineUser profiles and capabilities are also getting a fair amount of priority. MargarineUsers can expect to have more 3rd-party services to connect to similar to AniList and MyAnimeList. The economy commands, one of the lesser developed modules in recent updates, will also be expanded to have more purpose and allow MargarineUsers to do more with their inventories and credits.
A new framework, Miyuu, is also in development specifically for Margarine to replace Klasa. Miyuu's repository is made public as of this announcement which you can view here: https://github.com/Butterstroke/Miyuu
Finally, here's a list of miscellaneous things I still wanted to highlight:

Restructure the speechHelper function to be more readable and more efficient.
Utilize TypeScript for development as opposed to JavaScript.

Roadmap
The current roadmap is planned to take a few months of development. So while dates are nice, it's too far into the future to give an accurate timeline of events. However, these are some of the things users can expect to see in the following months:

MargarineBot v1 will still be supported at least until the release of v2.
Development changes may get ported into v1 with no major changes (ie: bug fixes, standalone features)
v1 will continue to migrate out of Klasa as much as possible to make it less dependent on it. v1 will not port over to Miyuu.
Updates for deprecation and ending support for v1 will be made closer to v2 release
A guide and tools to update from v1 to v2 will be made and released for self-hosters

Updates will be distributed by comments on this post and on my Discord support server.
Questions?
Any questions about these changes? Questions can be asked in the following places:
Discord Server: https://discord.gg/qKfqsjW (In the margarine-bot channel)
Email<EMAIL_ADDRESS>

As stated on the Discord server earlier this month, v2.0 development will be shifting directions a bit.
Miyuu is taking longer than expected to develop and with the pace of Discord's changes, would be worse off for a 2.0 release. So instead, the changes will happen directly in MargarineBot for v2.0. When Miyuu is ready, MargarineBot will transition into a v3.0 release with Miyuu. Likewise, MargarineBot v2.0 will require Node versions v16.6.0+ to run as it will be using Discord.js v13 as opposed to Node v12 and Discord.js v12.
Klasa will also be completely removed from MargarineBot in v2.0. Due to Discord changing how messages work with bots, most commands and features will transition into slash commands for it. This means that Klasa will be no longer needed and thus removed. Some features like starboards will be modified for guild settings but will need the new intent to run.
For everything else, development is going fairly well. I know there hasn't been a lot of news since the initial comment, but I have been working on porting things over and working on more of the underground parts. It's not the most exciting or interesting pieces of development to report on hence the silence.
As always, questions can be asked either in the Discord server or via my email. I'm always happy to respond so feel free to reach out.
I will also leave you all with a screenshot of the first successful test of dynamically loading slash commands and handling them.

Closed as the project will be going into End-of-Life support instead.


Improved note about webhint extension

Docs Build status updates of commit 97ed19a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

microsoft-edge/test-and-automation/webhint.md
:white_check_mark:Succeeded
View

microsoft-edge/visual-studio-code/index.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


feat(x/marketmap): refactor all market map consumer code

Think we should close this since the refactoring im working on directly conflicts

i'll leave open - but as a draft


Create .gitignore

Noticed config.py is in the repo. Also added some other files/folders to gitignore.

I think I got them all!


fix: fix binding tests for Gee-0.8

See #90
TODO: needs support for callback types nested in classes/interfaces before this can be merged.

Implemented in 1f769bcfaf2cf09da6b2b60c8321ec50c9f69e40.


⚠ Bofrost.es has degraded performance

In 6f83040, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1629 ms

Resolved: Bofrost.es performance has improved in d85b60a after 10 minutes.


Point the tinydtls submodule at the new location.

The old location https://git.eclipse.org/r/tinydtls/org.eclipse.tinydtls
is no longer accessable. It has been moved to
https://github.com/eclipse/tinydtls.git.
Signed-off-by: Scott Bertin<EMAIL_ADDRESS>

@rettichschnidi the "Install Ninja" step is now failing. Do you know how to fix that?

@sbertin-telular I will take care of it

@sbertin-telular Please cherry-pick this one commit: https://github.com/rettichschnidi/wakaama/commit/3f4ae1167925f3088387e9d732fd392d0b438717
Unfortunately, I can make a separate PR because that would fail due to the TinyDTLS issue... :/

@sbernard31 this is ready to merge.

:robot: : Done !
:grin:


Geometrycollection

Hi, i am using your WKTParser Library in one of my project. Everything was working great. However, i having issue with 'Geometrycollection' and only then i realised it is not included in the library. Is there any workaround to it?

hi @nanaberry . Sorry for hearing this because i didn't notice about this issue until now. I don't know if there is any problem with my notifications...
Well, GeometryCollection is included on this library but i can say that i am not using it from some time ago (i didn't test it on the latest Xcode or iOS SDK), so can you put here the WKT that you are trying to parse ? or something that can be help for me to resolve this issue ?

Closed issue due to inactivity.


Move dill to pickle

This pull request fixed #405

Standard file extension for pickle is .pkl. May be renaming the files?

Also remove dill from requirements.txt

Also remove dill from requirements.txt

Done

Coverage remained the same at 91.017% when pulling 36532dded723a5f27f54034da6b63c1509bfb481 on move-dill2pickle into 7cfa4012f4f0e2ec9d950255c06e5cf0c478f459 on dev.

Does the tagger still working correctly / similar to when it was using dill?

Does the tagger still working correctly / similar to when it was using dill?
Looks like at least it pass one test at
https://github.com/PyThaiNLP/pythainlp/blob/a4bbac97958c1d00b379862118a4a38021a5753c/tests/test_tag.py#L49
But just to confirm.

It's working correctly.


compileStringLiteral: support wide int32 string

support L"" wide string to int32 array
C code
L"\\\a\b\f\n\r\t\v\e\x1\x0104中A+-@\"\'123abcABC";

Go code
(*int32)(unsafe.Pointer(&[26]int32{'\\', '\a', '\b', '\f', '\n', '\r', '\t', '\v', '\x1b', '\x01', 'Ą', '中', 'A', '+', '-', '@', '"', '\'', '1', '2', '3', 'a', 'b', 'c', 'A', '\x00'}))

Codecov Report
Base: 88.80% // Head: 88.76% // Decreases project coverage by -0.04% :warning:

Coverage data is based on head (90ef581) compared to base (df06408).
Patch coverage: 87.35% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #155      +/-   ##
==========================================
- Coverage   88.80%   88.76%   -0.05%
==========================================
  Files          10       10
  Lines        3341     3427      +86
==========================================
+ Hits         2967     3042      +75
- Misses        293      301       +8
- Partials       81       84       +3

Impacted Files
Coverage Δ

cl/codebuild.go
86.62% <64.70%> (-0.80%)
:arrow_down:

cl/expr.go
91.40% <92.85%> (+0.19%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


No link to github.io page here

It is present in the readme under Website:

Sorry... not sure how i missed that.


we hit the channel limit

Bot needs to handle more categories for classes because Discord imposes a limit on how many channels can be within a category

ref #102


crd changes for velero konveyor-dev update pre-1.9

/retest

/retest

MySQL application NoDefaultBackupStorageLocation was removed from master. Rebase to test without this entry.


Suggestion Page for Feedback Module

The Suggestion Page for Feedback Module provides users with the ability to make suggestions to the individual parts of the service detail (i.e. service name, description, address, etc..). Here is the updated mock: https://zpl.io/VDwj8kw
Acceptance Criteria

[ ]  Checking the individual checkbox will expand and reveal the input field for the user to type in their suggestion for individual parts.
[ ]  Individual labels (both customized or existing labels) have identical appearances (same font style, same font size)
[ ]  Clear divider (grey, extends full width) to section off different parts of the service detail.

Steps for QA:

Notes from talk from Aron:

The light grey divider now replaces the existing tan one, this is a universal change and should appear full width everywhere
The labels in the designs are only in edit mode
We really need to be able to render these fields as consistently as possible which means dropping styling (ie H1s) and making it look as close to the designs as possible
The entire "Suggest an update" with checkbox section should be clickable

Both issues outlined here have their own tickets now: #1016 & #1017


[question] Missing endpoints with version 5.x

I have qubino ZMNHCD shutter switches. These normally has only Endpoint 0. Whenever i plug in its optional temperature sensor, then it has Endpoint 0.1 and 2. This was working fine with zwavejs2mqtt 4.x. But in 5.x, as i see from "Migrating to v8" notes of node-zwave-js; it has "Ignore unnecessary endpoints" feature now. (Migrating to v8) I need to add:
"preserveEndpoints": [0, 1, 2]

but i do not know where to put it. I am using a docker container for zwavejs2mqtt. 3 of 12 Qubino ZMNHCD i have temp sensors connected; so 3 of them are multi endpoints and the remaining 9 are single endpoint.
Can anyone tell me how i can use this preserveEndpoints flag for the multiple endpoint issue in these 3 nodes? Thanks a lot...

Please share a driver log (level debug) of a re-interview.
Also, do you know which endpoint the sensor will appear on? Did you re-include your devices after adding the temperature sensor?

In zwavejs2mqtt 4.x, i had 2 endpoints; Endpoint 0 lifeline and Endpoint 2 Temperature Sensor. Now, in 5.4.2, as default it comes as Endpoint 0 lifeline and Endpoint 0 Temperature Sensor. Funny thing is, when i delete Endpoint 0 Temperature Sensor From Groups, everything works perfectly fine even the temperature sensor sensor readings. So, you can simply disregard this problem; it works fine... Thanks...

Now, in 5.4.2, as default it comes as Endpoint 0 lifeline and Endpoint 0 Temperature Sensor.

Yep, that's the intention. If there is no duplicate functionality between endpoints, they are not really necessary.

Funny thing is, when i delete Endpoint 0 Temperature Sensor From Groups, everything works perfectly fine even the temperature sensor sensor readings.

What do you mean by this? I'd like to make sure that we don't have to edit a configuration to make this work.

I think there is no configuration change necessary. The way you did was right but as i understand the way Qubino does it is weird. In any case leaving it as it is better IMHO, cause it may create disturbance in other people's qubino usage. Thank you for the great work; my zwave network was never this stable...


Removed Boost and ported to C++11. Added support for Android and iOS

This PR replaces Boost with C++11 counterparts. And where they are not available, I either reimplemented them or used an alternative, namely:

There aren't semaphores in C++11, and it seemed to me that the interprocess features are not used, so I implemented a simple semaphore with condition variables (which are lighter, especially on Windows).
Instead of Boost.Asio, I added the standalone Asio distribution as a thirdparty submodule.
Instead of Boost.PropertyTree, I've used Tinyxml2, which is lighter and very portable.

I also added support for Android, including:

Added Michal Srb (@michalsrb)'s fork of Ken MacKay (@kmackay)'s implementation of ifaddrs for Android.
Tinyxml2, which works on Android.

Notes:

I couldn't find an example of the EDP XML format, so I don't know if the code I added with Tinyxml2 works fine. Could you add an example file so I can test it?
I had to use std::strftime instead of std::put_time because the latter is not implemented in GCC 4.8, which is the one that Ubuntu Trusty ships.

This work is completely independent and not officially endorsed or supported by OSRF, I did it in my spare time.

Also, I put the semaphore under the LGPL3 license, as the rest of the project. I tried my best to keep the same code style (tabs, naming, etc.) in the changes I made, let me know if they need reworking.

I just rebased against master and fixed the conflicts, I haven't had time to test the latest changes thoroughly, but they should work fine on Android.

Rebased this PR again against master. Changes since the last rebase:

I removed Boost from the examples and replaced it with C++11
Reorganized the files for the new FlowController and ThroughputController classes a bit so that they no longer expose <asio.hpp>
Added support for Universal Windows Platform apps (e.g. Windows IoT, Windows Phone, Windows 10)

Hi Esteve,
Impressive! Thanks a lot for all this effort (again). We will test everything.
After our change to Apache License 2.0,Any contribution that you make to this repository (including this pull request) will be under the Apache 2 License, as dictated by that
license:
5. Submission of Contributions. Unless You explicitly state otherwise,
   any Contribution intentionally submitted for inclusion in the Work
   by You to the Licensor shall be under the terms and conditions of
   this License, without any additional terms or conditions.
   Notwithstanding the above, nothing herein shall supersede or modify
   the terms of any separate license agreement you may have executed
   with Licensor regarding such Contributions.

I note you published the semaphore as LGPL, could you change that? I will contact you directly.

@JaimeMartin I had the license header removed from the semaphore in a previous rebase. What the clause 5 of the Apache license says is that, given a contributed piece of code that doesn't have an explicit license, it'll default to the Apache 2.0 license. In any case, pushed an update ot the branch where I added a header to the sempahore code with the Apache 2.0 license, just to avoid any confusion.
Also, I've split the UWP code into a separate commit, in case you'd rather cherry pick only the C++11 and Android changes.

I've rebased this PR once again against master, no major changes this time.

@JaimeMartin is there any word on when/if this will be merged into master?

Here's yet another periodic rebase. I second @scott-eddy , is there any actual plan to merge or test this? It's been 7 months since I first submitted this for review and updating this PR every time there's a conflict with master consumes a fair amount of time.
It's ok if it takes a lot of time to test all the changes (though you already use certain parts of C++11, namely std::mutex, std::unique_lock, etc.), but it'd be great to get some feedback.

Hi Esteve,
During the last months we have been working in several features to support properly ROS2 and our customers, so it is a matter of bandwidth.
We are very interested on this, and our plan is to prepare an experimental branch to test this PR properly.  I think we will be able to start the first tests in less than one month as we are incorporating a new engineer to the project.
Thanks for your patience, and your contribution.

@JaimeMartin that's fantastic, thanks for the update, I just wanted a bit of feedback. Let me know if there's anything I can help with to get this merged.

I just updated the description to mention that I added support for iOS to this branch.

I would like to suggest that it might be helpful to split up the unrelated parts of this PR. I would really like to see the boost to c++11 changes to get merged. @JaimeMartin Can you comment if the chances to integrate these changes individually would speed things up?

@dirk-thomas good idea. I've split the first commit and moved the Android-specific changes to https://github.com/eProsima/Fast-RTPS/pull/26/commits/53fc231ed75a40712f2c25ce5c3e91031a6066ff

@JaimeMartin @richiprosima Can you we please get a comment from you on this?

Hi @dirk-thomas, @esteve ,
We will be releasing resources  to test & merge this very soon.

@JaimeMartin thanks for the update. I just rebased this PR against master, @JavierIH @VicenteEprosima feel free to ask me any questions here about the changes.

@JaimeMartin When you review the changes I would suggest to consider not to introduce custom options like EPROSIMA_HONOR_BUILD_SHARED_LIBS. CMake already has an option for that purpose: BUILD_SHARED_LIBS. If the CMake default (FALSE) doesn't match your needs you can override as we do it for ROS (see https://github.com/ros2/ament_cmake_ros/blob/master/ament_cmake_ros/cmake/build_shared_libs.cmake).

@dirk-thomas Fast-CDR already uses EPROSIMA_HONOR_BUILD_SHARED_LIBS (https://github.com/eProsima/Fast-CDR/pull/8) to choose whether to use BUILD_SHARED_LIBS to let CMake build Fast-CDR as a shared library. However, feel free to submit any patches to use your approach, I'm sure the folks at eProsima will appreciate your effort.

I will leave it up to eProsima to pick their strategy. I only wanted to provide my 2 cent that adding a custom option for something CMake already provides seems counterproductive. Users familiar with CMake won't know about it and will certainly not expect it. Even worse if the developer uses the CMake option to override the behavior they can affect the add_library() calls which don't use SHARED but not the ones which do (so actually asymmetric behavior - one value works the other just doesn't because it conflict with the custom option unknown to the user).

@dirk-thomas I'm not arguing with you, you raise many valid points, so if you feel so strongly about this, it'd be great you could submit a patch that addresses it, that's the beauty of opensource. I don't have much time to work on this PR, so anyone who can contribute, the more the merrier.

@esteve changes are good for me because Fast-CDR and Fast-RTPS repositories didn't offer the alternative to build static libraries on Linux. I wasn't aware of the existence of BUILD_SHARED_LIBS. If this option is available on CMake, better not duplicate as you said. Changes have been already done on eProsima/Fast-CDR@56778bdc1f5506cee341d580bd785792ae5fee20. In the process of merging this PR we will apply the change on Fast-RTPS. Thanks to both.

I've rebased this PR and applied the same commit that @richiprosima made for Fast-CDR so that both projects use the same approach to building static libraries. I only applied the patch on non-Windows platforms, since the libraries already built both static and shared on Windows.

I've merged @JavierIH 's PR and reordered and squashed some of the commits, but both two branches are equivalent.
I just realized that this PR is one day away from turning a year old since I first submitted it for review, whoa!

We are very interested in using FastRTPS on Android and would love to see this land. Curious to know if this is a near-term target for eProsima? Would it be safe to start working from this PR's branch?
@esteve Thanks in general for your efforts both here and in your efforts towards ROS2 support on Android!

@richiprosima @esteve
Also, out of curiosity, do you have available the methods you use to build FastRTPS for Android? Using @esteve's ros2_java README as a baseline, I was able to successfully build using the following commands, but they could probably use a lookover to see if I missed anything:
mkdir build
cd build

$HOME/Android/Sdk/cmake/3.6.3155560/bin/cmake \
-DCMAKE_TOOLCHAIN_FILE=$HOME/android/android-ndk-r14/build/cmake/android.toolchain.cmake \
-DANDROID_ABI=armeabi-v7a \
-DANDROID_NDK=$HOME/Android/Sdk/ndk-bundle \
-DCMAKE_BUILD_TYPE=Release \
-DANDROID_NATIVE_API_LEVEL=android-21 \
-DANDROID_PLATFORM=android-21 \
-DANDROID_FUNCTION_LEVEL_LINKING=OFF \
-DANDROID_TOOLCHAIN_NAME=arm-linux-androideabi-clang \
-DANDROID_STL=gnustl_shared \
-DTHIRDPARTY=ON \
-DCOMPILE_EXAMPLES=OFF \
-DCMAKE_CXX_FLAGS=-std=c++11 -frtti -fexceptions \
..

@spiderkeys thanks for trying out this branch! That CMake incantation is perfect, the only thing I might change is that you don't have to pass any extra flags to the C++ compiler. Starting with NDK r14, RTTI and exceptions are enabled by default (see https://github.com/pombredanne/android.googlesource.com-platform-ndk/commit/9b3fff0a117ab7c49eb97c1bc441b4bb8c3464fc) Additionally, -std=c++11 is not necessary since it's already in FastRTPS' CMakeLists.txt
Also, according to the FastRTPS README, you should pass -DEPROSIMA_BUILD=ON, instead of -DTHIRDPARTY=ON, I need update the ros2_java docs.
Let me know if you find any other issue, I've been using this code in conjunction with ros2_java, but haven't really used it standalone.


Maximum call stack size exceeded with "maxNativeZoom"

Hello!
I found out that if "maxNativeZoom" is used and it is exactly 2 less then "maxZoom" when maximum zoom reached - " Maximum call stack size exceeded " is thrown.

 L.tileLayer('http://{s}.tile.osm.org/{z}/{x}/{y}.png', {
            attribution: '© OpenStreetMap contributors',
            maxNativeZoom: 14,
            maxZoom: 16,
            minZoom: 11,
        }).addTo(map);

It should be exactly "maxZoom" - "maxNativeZoom" === 2 to get the error. I have tested it with your example.
   "leaflet": "^1.4.0",     "leaflet-active-area": "^1.1.0"

we're seeing something similar in our project with leaflet 1.5.1
@paulgreg do you have any advice on this or possible a chance to look at it?

hey @webmatrixxxl - @dopeters got a PR merged in that helped fix this issue for us. it's not on NPM yet, however we installed the package via the git repo like so:
"leaflet-active-area": "https://github.com/Mappy/Leaflet-active-area.git"

hope it helps :)

Hello,
Yes, sorry for the delay.
Could you confirm that @dopeters’s PR fixes your issue ?
If so, I would generate the npm package.

@colbyfayock @paulgreg
Hello. Any updates? We would not like to use the link to the repository in package.json

"leaflet-active-area": "https://github.com/Mappy/Leaflet-active-area.git"
did not fix it for me

@webmatrixxxl does this resolve the issue for you as well?

Just published release 1.1.1 with the fix.


wrong date or day of week

08 October 2024 is Tuesday but showing wednesday

That was a timezone issue, and has been fixed.
Thanks for this.

Thanks for fixing, I'm update component, but still see error, 10 Oct is Tuesday, not Friday. How could I fix that? And one more, could you tell me, how to change start week since monday?

Everything seems okay here. Did you update the npm package?

I will make an update to the package and expose props so week can start from either Monday or Sunday

Everything seems okay here. Did you update the npm package?

yep, package updated, after update i saw new png files in directory

reinstall and still got wrong date((. We are in N. Central Asia Standard Time +7 timezone, how can i fix that ussue? And patiently wait new update to change start a week)))

Alright.
Would jump on it to make update so you can pass a timezone prop, as well as "Monday" as first day of the week

After package update  cannot build project, got this:
build started...
✓ 10 modules transformed.
[commonjs--resolver] Failed to resolve entry for package "v3-events-calendar". The package may have incorrect main/module/exports specified in its package.json.

Let me check  and see if i can reproduce

@azaharov88
A new update has been published and patched.
Thank you!

Works fine! You're great! Realy thanks!

If you want to make greater component, would be nice to make a locale file with names of months, days etc.

Can you show your code?
parts of it related to the calendar so i can see if you're doing anything incorrectly.
Popups works just fine on my end.

If you want to make greater component, would be nice to make a locale file with names of months, days etc.

I don't understand what you mean

If you want to make greater component, would be nice to make a locale file with names of months, days etc.

I don't understand what you mean

I mean, make locale files so you can changing language just by changing locale

Can you show your code? parts of it related to the calendar so i can see if you're doing anything incorrectly.
Popups works just fine on my end.

Sorry, forget it, it's not part of calendar code)


Meet with the community champion for LEAP to better understand how they would actually use the unlisted_choice feature

Email requesting a meet sent out.

@jmunroe, can you capture the main ideas/follow-ups from the above content in independent new issues, and then we close this one? Thanks!

Here are three actions that follow from this meeting:

https://github.com/2i2c-org/infrastructure/issues/2955 (suggestion for next sprint)
https://github.com/2i2c-org/infrastructure/issues/2956 (backlog)
https://github.com/2i2c-org/infrastructure/issues/2957 (backlog)


Dynamic Map step size

Feature request: Set stepsize for every dimension in a DynamicMap.
The default of 0.00001 is rather small.

I believe this would relate to the proposal in #843 - the idea is that stepsize in an example of a dimension preference.

Now that #1245 is merged, I see no reason not to allow this as a dimension parameter.

Implemented in PR #1257. Closing.


Get "Error: conn busy" when running db remote set with 0.13.0

Bug report
When running supabase db remote set <url> it prints the following error:
Error: conn busy

Describe the bug
See above.
To Reproduce
Steps to reproduce the behavior, please provide code snippets or a repository:

cd <existing project created with supabase 0.12.4>
Run supabase start
Run supabase db remote set postgresql://...
Should see error message

Expected behavior
The local database should be linked to the remote database
System information

OS: macOS
Version of supabase-js: 1.28.2
Version of Node.js: 14.16.0

I am experiencing the same behavior. Thank you for reporting.

I have the same problem, thanks for reporting too.
Version information:
➜  opinionshift git:(feat-devcontainer) ✗ supabase --version
0.15.1

Thanks for reporting! Turns out this happens irrespective of which CLI version the project was initialized with. Let me know if the issue persists.


[Investigate] Add support for GraphQL modules

https://graphql-modules.com/

GraphQL Modules is a toolset of libraries and guidelines dedicated to create reusable, maintainable, testable and extendable modules out of your GraphQL server.

We should leverage this to improve generated projects.
See https://github.com/aerogear/graphback/pull/335

Here's an idea:
In the model folder where developers define the input schema there can be two options.

For each subfolder defined Graphback would create a module, keeping schema files separate and preserving desired structure.

- model
  - note
    - model.graphql
    - queries.graphql
    - mutations.graphql
  - comment
    - model.graphql
    - queries.graphql
    - mutations.graphql

The output would look something like this:
- modules
  - note
    - model.graphql
    - queries.graphql
    - mutations.graphql
    - resolvers
      ..
    - providers
      ..
    - index.ts

If the schema files are defined in the folder root then Graphback would just generate one large module.

- model
  - note.graphql
  - comment.graphql

Here's an idea:
In the model folder where developers define the input schema there can be two options.
1. For each subfolder defined Graphback would create a module, keeping schema files separate and preserving desired structure.

- model
  - note
    - model.graphql
    - queries.graphql
    - mutations.graphql
  - comment
    - model.graphql
    - queries.graphql
    - mutations.graphql

The output would look something like this:
- modules
  - note
    - model.graphql
    - queries.graphql
    - mutations.graphql
    - resolvers
      ..
    - providers
      ..
    - index.ts

1. If the schema files are defined in the folder root then Graphback would just generate one large module.

- modules
  - app
  	- note.graphql
  	- comment.graphql
	..


Update MD file on new branch 2017-30-10_23-12-38

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Eager loading of CUDNN sub-libraries.

Improves accuracy of TF autotuning by ensuring first calls to cudnn kernels run at full speed.
Attention @sanjoy

cudnn_8_0.inc is auto-generated, is it still fine to make changes to it manually?

Yes, that's fine. There aren't that many additions that this would get out of hand.


Reserved Instance valid EA Key

Could you let me know if it's normal that the tables for RICharges / RIRecommendations_Single / RIRecommendations_Shared / RIUsage / Budget are in error if the EA API Key is not at the enrollment-level?
If yes, could you add this information in the documentation ?

Thanks for posting – note that we can only answer feedback related to the documentation, and can’t provide direct support or respond feature requests.
Your best venue for getting an answer or feedback on your question is from the community (https://community.powerbi.com) or from support at https://support.powerbi.com. You can also provide feedback using the Give Product Feedback button at the bottom of the article page.


Sidenav on esc close menu

Describe the bug
Sidenav is closing when you press ESC key. The state of sidenav_open is not change instead only css class .mat-drawer transform: translate3d(-100%, 0, 0);
To Reproduce
Click on Sidenav then press ESC key
Expected behavior
Sidenav should have option to not close sidenav or to change state with ESC.
Desktop System Info

OS: Mac, Ubuntu 24.04
Browser Chrome, Firefox
Version latest

Good catch. Thanks for bringing this to our attention. Seems like it should be a quick fix, so I'll see if I can look at it this week.

I looked at the sidenav API. Seems it should be easy to add both options. And I think API-wise it seems fairly clear.
We can use the openChanged event to notify the Mesop app when the state of the side nav has changed. In this case it would be up to user to update the closed state accordingly.
We can also use the disableClose to make it so that pressing ESC and clicking the background will not close the sidenav.


module federation remoteType

remoteType: "umd" error

Bug report

What is the current behavior?
error
If the current behavior is a bug, please provide the steps to reproduce.
https://stackblitz.com/edit/github-faw5we-nztzyp?file=app1%2Fwebpack.config.js

// app1
ModuleFederationPlugin({
remoteType: "umd",
remotes: {
"app2": "app2@http://localhost:3002/remoteEntry.js"
}
})
// app2
ModuleFederationPlugin({
name: "app2",
library: { type: "umd", name: "app2" }
})
What is the expected behavior?

Other relevant information:
webpack version:  5.74.0
Node.js version: 16.13.0
Operating System:
Additional tools:

Remote seems to lose its global scope or not inject container at all when umd

UMD is just not supported by module federation, so if you want it feel free to send a PR, sorry, it is not high priority, because developers mostly don't use this format for module federation

UMD is just not supported by module federation, so if you want it feel free to send a PR, sorry, it is not high priority, because developers mostly don't use this format for module federation

ok, I'm implementing "webpack-4 module consumption". I just want to compare the appearance of "webpack-5" during implementation. In fact, I don't need "module consumption" output as "umd"


add windows support

This replaces the os.Rename call with two separate implementations depending
on target OS.  On windows it uses the movefileex syscall to make the move
atomic, unlike the implementation of os.Rename.
Needs tests, for sure.

Fixes #1

https://github.com/golang/go/issues/32188#issuecomment-497873904 says MoveFileEx is not atomic under windows, and ReplaceFile should instead be used.

https://github.com/golang/go/issues/22397#issuecomment-498856679 says nothing is atomic under windows. Closing this until someone comes up with new evidence.


Add How to Setup a Domain Whitelabel and How to View Email Statistics to USE_CASES.md

Please see this for an example.

#475


Fixed #30183 -- Added parsing of inline SQLite constraints.

Sorry for delay, I hope to look comments to end of week

It's difficult to review since so much code has moved. Is it feasible to separate this into a commit that moves the existing code and then make the changes after that?

@timgraham , split to several commits with code extracting

Tests crash on Oracle with "ORA-02261: such unique or primary key already exists in the table". I guess it's because Comment has unique=True for the ref field as well as models.UniqueConstraint(fields=['ref'], name='ref_uniq'),.

Tests crash on Oracle with "ORA-02261: such unique or primary key already exists in the table". I guess it's because Comment has unique=True for the ref field as well as models.UniqueConstraint(fields=['ref'], name='ref_uniq'),.

yep, removed duplicated constraints, hope it should fix model creation

buildbot, test on oracle.

There's at least one failure on Oracle:
======================================================================
FAIL: test_get_constraints (introspection.tests.IntrospectionTests)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/tim/code/django/tests/introspection/tests.py", line 266, in test_get_constraints
    self.assertEqual(constraints.keys() ^ (custom_constraints | field_constraints), set())
AssertionError: Items in the first set but not the second:
'sys_c001487308'
'sys_c001487309'
'sys_c001487310'
'sys_c001487307'

Running the full suite now.

Here are details of the extra Oracle constraints:
 'sys_c001487413': {'check': 1,
                    'columns': ['id'],
                    'foreign_key': None,
                    'index': 0,
                    'primary_key': 0,
                    'unique': 0},
 'sys_c001487414': {'check': 1,
                    'columns': ['ref'],
                    'foreign_key': None,
                    'index': 0,
                    'primary_key': 0,
                    'unique': 0},
 'sys_c001487415': {'check': 1,
                    'columns': ['article_id'],
                    'foreign_key': None,
                    'index': 0,
                    'primary_key': 0,
                    'unique': 0},
 'sys_c001487416': {'check': 1,
                    'columns': ['pub_date'],
                    'foreign_key': None,
                    'index': 0,
                    'primary_key': 0,
                    'unique': 0},

I guess the test should expect those constraints.


Auth0 log says "Success Login" but the dashboard login Error

Describe the problem
I have set the .local-config.json file as well as the auth0 setting. However, the local dev always stuck in the page just after log in, saying
"Oops, something went wrong
There was an error logging you in.
Error: Unauthenticated" (See the image).
When I go to the auth0 page to see the log, the log says I logged in successfully.
So confused. Where is the problem?
Screenshots

Anyone has developed locally please? How to solve it

Hey @Chauban ,
see the reply to your other issue here: https://github.com/netbirdio/dashboard/issues/382
Best,
Eduard


app_test failing, possibly due to fee changes

app_test is failing.  I suspect the changes implemented for #66 are the cause.  So I am assigning this to @nathanhourt
$ tests/app_test
Running 1 test case...
1640058ms th_a       application.cpp:171           startup              ] Allocating all stake to 5KQwrPbwdL6PhXujxW37FSSQZ1JiwsST4cqQzDeyXtP79zkvFD3
1640067ms th_a       main.cpp:96                   test_method          ] e.to_detail_string(): 10 assert_exception: Assert Exception
core_fee_paid >= op.calculate_fee(db().current_fee_schedule()):
{}
th_a  evaluator.hpp:198 evaluate

{"genesis_state":{"initial_parameters":{"current_fees":{"key_create_fee":270300,"account_create_fee":666666,"account_update_fee":150000,"account_transfer_fee":300000,"account_len8up_fee":1500000,"account_len7_fee":7000000,"account_len6_fee":14000000,"account_len5_fee":70000000,"account_len4_fee":280000000,"account_len3_fee":680000000,"account_len2_fee":1000000000,"asset_len3_fee":"7000000000","asset_len4_fee":2700000000,"asset_len5_fee":1350000000,"asset_len6_fee":675000000,"asset_len7up_fee":140000000,"account_whitelist_fee":300000,"delegate_create_fee":680000000,"witness_create_fee":680000000,"witness_withdraw_pay_fee":1500000,"transfer_fee":2700000,"limit_order_create_fee":666666,"limit_order_cancel_fee":150000,"call_order_fee":800000,"publish_feed_fee":666666,"asset_create_fee":680000000,"asset_update_fee":150000,"asset_issue_fee":700000,"asset_burn_fee":1500000,"asset_fund_fee_pool_fee":150000,"asset_settle_fee":7000000,"data_fee":13500000,"global_parameters_update_fee":1350000,"membership_annual_fee":270000000,"membership_lifetime_fee":1350000000,"withdraw_permission_create_fee":2700000,"withdraw_permission_update_fee":150000,"withdraw_permission_claim_fee":700000,"withdraw_permission_delete_fee":150000,"vesting_balance_create_fee":7000000,"vesting_balance_withdraw_fee":2700000,"asset_global_settle_fee":140000000,"worker_create_fee":680000000,"assert_op_fee":150000,"proposal_create_fee":7000000,"proposal_update_fee":1500000,"proposal_delete_fee":150000},"block_interval":5,"maintenance_interval":86400,"maximum_transaction_size":2048,"maximum_block_size":2048000000,"maximum_undo_history":1024,"maximum_time_until_expiration":86400,"maximum_proposal_lifetime":2419200,"maximum_asset_whitelist_authorities":10,"maximum_asset_feed_publishers":10,"maximum_authority_membership":10,"burn_percent_of_fee":2000,"network_percent_of_fee":2000,"lifetime_referrer_percent_of_fee":3000,"max_bulk_discount_percent_of_fee":5000,"cashback_vesting_period_seconds":31536000,"cashback_vesting_threshold":10000000,"bulk_discount_threshold_min":100000000,"bulk_discount_threshold_max":"10000000000","count_non_member_votes":true,"allow_non_member_whitelists":false,"witness_pay_per_block":1000000,"worker_budget_per_day":"50000000000","max_predicate_opcode":1},"allocation_targets":[{"name":"init0","addr":"GPHFAbAx7yuxt725qSZvfwWqkdCwp9ZnUama","weight":0},{"name":"init1","addr":"GPHFAbAx7yuxt725qSZvfwWqkdCwp9ZnUama","weight":0},{"name":"init2","addr":"GPHFAbAx7yuxt725qSZvfwWqkdCwp9ZnUama","weight":0},{"name":"init3","addr":"GPHFAbAx7yuxt725qSZvfwWqkdCwp9ZnUama","weight":0},{"name":"init4","addr":"GPHFAbAx7yuxt725qSZvfwWqkdCwp9ZnUama","weight":0},{"name":"init5","addr":"GPHFAbAx7yuxt725qSZvfwWqkdCwp9ZnUama","weight":0},{"name":"init6","addr":"GPHFAbAx7yuxt725qSZvfwWqkdCwp9ZnUama","weight":0},{"name":"init7","addr":"GPHFAbAx7yuxt725qSZvfwWqkdCwp9ZnUama","weight":0},{"name":"init8","addr":"GPHFAbAx7yuxt725qSZvfwWqkdCwp9ZnUama","weight":0},{"name":"init9","addr":"GPHFAbAx7yuxt725qSZvfwWqkdCwp9ZnUama","weight":0},{"name":"nathan","addr":"GPHFAbAx7yuxt725qSZvfwWqkdCwp9ZnUama","weight":1}],"initial_witnesses":[{"owner_name":"init0","block_signing_key":"GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","initial_secret":"8fafdc1d8c46392cc7a6d1c7a925450fe43f0c23822e1053611f0e81"},{"owner_name":"init1","block_signing_key":"GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","initial_secret":"8fafdc1d8c46392cc7a6d1c7a925450fe43f0c23822e1053611f0e81"},{"owner_name":"init2","block_signing_key":"GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","initial_secret":"8fafdc1d8c46392cc7a6d1c7a925450fe43f0c23822e1053611f0e81"},{"owner_name":"init3","block_signing_key":"GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","initial_secret":"8fafdc1d8c46392cc7a6d1c7a925450fe43f0c23822e1053611f0e81"},{"owner_name":"init4","block_signing_key":"GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","initial_secret":"8fafdc1d8c46392cc7a6d1c7a925450fe43f0c23822e1053611f0e81"},{"owner_name":"init5","block_signing_key":"GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","initial_secret":"8fafdc1d8c46392cc7a6d1c7a925450fe43f0c23822e1053611f0e81"},{"owner_name":"init6","block_signing_key":"GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","initial_secret":"8fafdc1d8c46392cc7a6d1c7a925450fe43f0c23822e1053611f0e81"},{"owner_name":"init7","block_signing_key":"GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","initial_secret":"8fafdc1d8c46392cc7a6d1c7a925450fe43f0c23822e1053611f0e81"},{"owner_name":"init8","block_signing_key":"GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","initial_secret":"8fafdc1d8c46392cc7a6d1c7a925450fe43f0c23822e1053611f0e81"},{"owner_name":"init9","block_signing_key":"GPH6MRyAjQq8ud7hVNYcfnVPJqcVpscN5So8BhtHuGYqET5GDW5CV","initial_secret":"8fafdc1d8c46392cc7a6d1c7a925450fe43f0c23822e1053611f0e81"}],"initial_committee":[{"owner_name":"init0"},{"owner_name":"init1"},{"owner_name":"init2"},{"owner_name":"init3"},{"owner_name":"init4"},{"owner_name":"init5"},{"owner_name":"init6"},{"owner_name":"init7"},{"owner_name":"init8"},{"owner_name":"init9"}]}}
th_a  db_init.cpp:358 init_genesis

{"data_dir":"/tmp/bb1e-90a3-983c-cf70/blockchain"}
th_a  db_management.cpp:55 open

{}
th_a  application.cpp:190 startup

Yep. This one's my fault.  :P

@theoreticalbts Can you check if this is fixed? #55 happens every time I run today, so I can't tell if it's fixed or not.

Looks like it's fixed.


Noah-OM gridded namelist.input refactor

PURPOSE
This PR refactors namelist.input and the module responsible for reading that file. This PR adds required NetCDF variable, dimension, and attribute names to namelist.input that were previously hardcoded.
ADDITIONS
None
CHANGES
namelist.input
The following variables were added to namelist.input:

netcdfin_filename, which is the directory/name of NetCDF file holding gridded model inputs
name_var_vegtyp, which is the name of NetCDF variable for vegtyp (land use)
name_var_isltyp, which is the name of NetCDF variable for isltyp (soils)
name_var_soilcolor, which is the name of NetCDF variable for soilcolor
name_var_slope, which is the name of NetCDF variable for slope
name_var_azimuth, which is the name of NetCDF variable for azimuth
name_dim_x, which is the name of NetCDF 'x' dimension (longitude dimension)
name_dim_y, which is the name of NetCDF 'y' dimension (latitude dimension)
name_att_dx, which is the name of NetCDF 'x' dimension resolution (spacing)
name_att_dy, which is the name of NetCDF 'y' dimension resolution (spacing)

The following variable were removed from namelist.input (because they are now read-in via NetCDF file or derived from NetCDF inputs):

terrain_slope
azimuth
sfctyp
soilcolor

Note that the vegtyp and isltyp variables were previously removed in PRs #74 and #80, respectively.
NamelistRead.f90
The NamelistRead module was refactored to facilitate reading the refactored namelist.input file.
DomainGridType.f90
domaingrid_type%IST (i.e., the soil vs. lake indicator variable) was removed from the domaingrid_type%InitTransfer procedure.
This PR uses the NetCDF-provided input variable vegtyp (land use) and the variable parameter_type%ISWATER (from /parameters/MPTABLE.TBL) to derive domaingrid_type%IST rather than require sfctyp as an additional gridded input variable. However, we cannot set domaingrid_type%IST here because parameters_type%ISWATER has not yet been set -- and won't be until parametersgrid_type%paramRead is called. Thus, IST was removed from domaingrid_type%InitTransfer.
RunModule.f90
This PR initializes domaingrid_type%IST in initialize_from_file as:
      domaingrid%IST(:,:) = 1
      where (domaingrid%vegtyp == parametersgrid%ISWATER) domaingrid%IST = 2

TESTING
I re-compiled the model, re-executed the model, and re-executed /test/analysis/compare_outputnc.py and got expected resutls: grid cell (1,1) passed all tests while all other cells did not.
I also did a crude test to verify that the PR correctly initializes domaingrid_type%IST by adding a print statement immediately after IST's initialization, i.e.:

I then modifyed /data/netcdf_input.nc such that all grid cells had a vegtyp value of 1 except for cell (1,1). Cell (1,1) was assigned a vegtyp value of 17, which equals ISWATER if veg_class_name = "MODIFIED_IGBP_MODIS_NOAH". I then re-compiled the model with the included print statement and re-executed with the modified /data/netcdf_input.nc file and got the following (correct) output:

@SnowHydrology: @nmizukami was kind enough to volunteer to review this. However, I wanted to call your attention to this PR because (1) it refactors namelist.input, which seems important, and (2) it does not require that the IST variable (i.e., soil vs lake indicator variable) be read-in via NetCDF -- the PR instead initializes IST via vegtyp (land use). Let me know if you have thoughts on this.

I appreciate you all taking the time to look at this, @SnowHydrology, @andywood, and @nmizukami.
I'll revise this PR to rename the netcdfin_filename to attrib_nc_file or something similar. I'll also hardcode the NetCDF variable, attribute, and dimension names and make sure that we have sufficient checks and error messages in case the user provides unexpected names/values. I'll additionally make sure to address anything else that you've identified in the comments above.
@andywood: regarding that SUMMA-style code, whomever wrote the NamelistRead subroutine gave us that gift. That's where I lifted it from!
Thanks again, all! Appreciate it.

I appreciate you all taking the time to look at this, @SnowHydrology, @andywood, and @nmizukami.
I'll revise this PR to rename the netcdfin_filename to attrib_nc_file or something similar. I'll also hardcode the NetCDF variable, attribute, and dimension names and make sure that we have sufficient checks and error messages in case the user provides unexpected names/values. I'll additionally make sure to address anything else that you've identified in the comments above.
@andywood: regarding that SUMMA-style code, whomever wrote the NamelistRead subroutine gave us that gift. That's where I lifted it from!
Thanks again, all! Appreciate it.

Could have been me pulling that in -- a sad part of fractured attention to too many projects is that I don't remember!

This all looks good to me, Grey :)
On Mon, Oct 16, 2023 at 2:13 PM GreyEvenson-NOAA @.***>
wrote:

@.**** commented on this pull request.
In run/namelist.input
https://github.com/NOAA-OWP/noah-owp-modular/pull/87#discussion_r1361218481
:

@@ -51,8 +45,19 @@
nsnow            = 3               ! number of snow levels
nveg             = 20              ! number of vegetation types
croptype         = 0               ! crop type (0 = no crops; this option is currently inactive)

sfctyp           = 1               ! land surface type, 1:soil, 2:lake
soilcolor        = 4               ! soil color code
+/

+&netcdf_input

netcdfin_filename  = "../data/netcdf_input.nc"  ! directory/name of NetCDF file holding gridded model inputs

I changed lots of names in revising the PR:
NetCDFVarsType.f90 -> AttributesType.f90
netcdfvars_type -> attributes_type
netcdfin_filename -> attributes_filename
However, I'm not married to these. I'd be happy to change them again if
folks think it would be helpful.
—
Reply to this email directly, view it on GitHub
https://github.com/NOAA-OWP/noah-owp-modular/pull/87#discussion_r1361218481,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABIKARI7N5UAY34ASBS474TX7WIONAVCNFSM6AAAAAA5BXC2T2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTMOBQHA4DENZSHE
.
You are receiving this because you were mentioned.Message ID:
@.***>

@SnowHydrology, I believe we're ready for you to have another look. @andywood seemed to approve of the changes. @nmizukami, let me know if you see anything else we can improve upon.
Thanks again for all your time in reviewing this!


Fix: PDF Options, Allow General PDF Format Configuration

The code allowing customisation of the PDF invoices does not match what is available in the version of dompdf required by cashier.  These changes allow users to optionally use Laravel style configuration file that can be shared with any part of the application that uses the dompdf/dompdf library to generate PDF files.
Benefits:
Developers can set important options like the paper size or orientation for invoices.  Unknown or unused settings will be discarded if they are not recognised between versions.  This has been a major requirement for projects that leverage Cashier directly or indirectly through Spark.
Usage:
A developer who wants to change the PDF formatting can create a dompdf.php file in thier config directory and those options will be passed to the renderer when an invoice is created.
Example:
This would be a simple file, /config/dompdf.php with default settings.
<?php

return [

    /*
    |--------------------------------------------------------------------------
    | Default Paper Size
    |--------------------------------------------------------------------------
    |
    | This option determines the default paper size for invoices.  Expand your
    | market by billions* by using using 'a4', be bespoke by choosing 'legal'.
    |
    */

    'default_paper_size' => env('DOMPDF_PAPER_SIZE', 'letter'),

    /*
    |--------------------------------------------------------------------------
    | Default Paper Orientation
    |--------------------------------------------------------------------------
    |
    | This option determines the default paper orientation for invoices. Use
    | 'landscape' for something more exotic.
    |
    */

    'default_paper_orientation' => env('DOMPDF_PAPER_SIZE', 'portrait'),

    /*
    |--------------------------------------------------------------------------
    | Default HTML Processor
    |--------------------------------------------------------------------------
    |
    | This option determines the parsing engine for invoices. Why party like
    | it's 1999 when you already have to write a restrictive subset of HTML
    | for email and invoice templates? You know what to do... you savage.
    |
    */

    'enable_html5_parser' => env('DOMPDF_USE_HTML5_PARSER', false),

];

Documentation Updates:
Detailed PDF formatting options can be set by creating a dompdf.php file in the project's config directory, specifying the options to be passed to the PDF renderer. See the following for details.
https://github.com/dompdf/dompdf/blob/master/src/Options.php
I'm not good at writing copy.
Implementation Notes:
Creating and initialising an Dompdf\Options object from an array of values first appears to be a better code path.  While there is an interface for supplying an Dompdf\Options object after the Dompdf\Dompdf object is created ( see Dompdf::set_options() ), it does not work reliably for all option values.  I may submit another pull request to that project to address this.
I have not added a publishable configuration file because Laravel/Cashier could change its dependencies.  I feel it is outside of scope.
Everything I know, I learned from @JeffreyWay

Prefer to just stick to a convention.

Thank you for taking the time to review this.  I don't see how else I can get a hook to change the paper size on invoices that has a chance to survive updates.
I see this line but, I cant figure out how it might be used to set any configuration options.
https://github.com/laravel/cashier/blob/36436c0d9fb07516dbf7e052dd38ca57ed9cbb68/src/Invoice.php#L255
I'd be greatful for any guidance.

If you have a convention in mind, I'd be happy work on implementing it.  At the moment, there's no way to pass any settings with the version of dompdf/dompdf cashier has in its dependencies.

Oh... I should have mentioned it at the top to be clear.  You have quite a number of projects on the go and I'm referencing something very specific.  My bad.
Cashier has a dependency of dompdf 0.8, but is using the configuration mechanism that is for 0.6 and below.  If we could, we would use the  convention of 0.6 but they shifted this.
They outline it here:
https://github.com/dompdf/dompdf/wiki/DOMPDF-and-Composer-Quick-start-guide
Good news is that we can use a very laravel configuration style now.  That's what this pull request was about.

Please look into this. @epreston is right. This is a very annoying bug/incompatibility!


Installing not working

Hi there, ive installed over 9 plugins in hoobs and no issues at all, but when I try to install this one, it makes the bridge but it doesn't install the plugin.
https://github.com/user-attachments/assets/7a0a3633-e6fe-4b80-9e33-35335530f34e

Seems you might have a similar issues as here, please check the solution there
https://github.com/merdok/homebridge-webos-tv/issues/512#issuecomment-1899898042 also here https://github.com/merdok/homebridge-webos-tv/issues/529#issuecomment-2076696650

I don’t understand, I’ve tried with a fresh installation of Hoobs and I still can’t download the plugin, it just makes the bridge and that’s all. I really don’t know what to do.

This is not an issue with the plugin but with your local environment. You are missing required packages or your node.js version might be incorrect. Please follow the provided links and try to apply the solution provided there.


Add count prop to OuiTreeView #934

Description
Added count prop to display the number of children components in TreeView with an OuiFacetButton
Issues Resolved
Fixes #934
Check List

[ ] New functionality includes testing.
[ ] New functionality has been documented.
[ ] All tests pass

[ ] yarn lint
[ ] yarn test-unit

[ ] Update CHANGELOG.md
[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Could you add a before and after screenshot for this change?

sure!

@keskami  According to the issue description: "Count prop should reflect the number of OuiTreeNode children, and should be optional to include". It seems like you need to modify the props that sent into the OuiTreeView component. For example:
<OuiTreeView items={items} showCount={true} aria-label="Sample Folder Tree" />

Some suggestions:

Add some unit tests for this new functionality
(Maybe?) Add a toggle for the Tree view demo to demonstrate that this is an optional feature


Drop one-var rule

The Rule: http://eslint.org/docs/rules/one-var
The Current WPCS JS Docs: https://make.wordpress.org/core/handbook/best-practices/coding-standards/javascript/#declaring-variables-with-var
Decisions & Discussions:

https://wordpress.slack.com/archives/C5UNMSU4R/p1499174610645102
https://wordpress.slack.com/archives/C5UNMSU4R/p1499174819719992

Closed via #109


Reloading a page adds a duplicate entry to the history

If you visit a page, and then click the reload button, when you push the back button, it appears to the user that nothing happens. You must press the back button again to return the original page.
Steps to reproduce:

Start on Page A
Click a navigate to Page B
Reload Page B
Click the back button

Expected: you are on Page A
Actual: you are on Page B
It gets worse because if you click reload on Page B multiple times, the user must click the back button that many times before they return back to Page A. This is very jarring.
I suppose this could be considered expected behavior, since you are going "back" to what Page B looked like at a previous time. However no other Web browser or gemini browser works this way.
I suspect that a list is is being used to track history, and clicking reload adds another entry to the list. I suggest that reloading a page should not add a new entry to the history list

@acidus99 Should be fixed in https://github.com/jfoucher/Jimmy/commit/d1a5c50ec81285a999fbe035bc0e73ed7297b1d5

Thank you!


LUCENE-10499: reduce unnecessary copy data overhead when growing array size

ArrayUtil#grow will copy origin array data to the new array after growing size in default, but in many places, the new array needn't the origin data. This PR reduces the extra copy data overhead.
Checklist
Please review the following and check all that apply:

[x] I have reviewed the guidelines for How to Contribute and my code conforms to the standards described there to the best of my ability.
[x] I have created a Jira issue and added the issue ID to my pull request title.
[x] I have given Lucene maintainers access to contribute to my PR branch. (optional but recommended)
[x] I have developed this patch against the main branch.
[x] I have run ./gradlew check.
[ ] I have added tests for my changes.

Can we instead add a new method to ArrayUtil, with a different name than grow, that doesn't copy data?
I don't think we should add a boolean parameter to grow that gives it radically different behavior.

Can we instead add a new method to ArrayUtil, with a different name than grow, that doesn't copy data?
I don't think we should add a boolean parameter to grow that gives it radically different behavior.

@rmuir Hi, I add ArrayUtil#growSizeOnly method that only grow size and not copy array data, please review again, thanks.

@jpountz Hi, can you help to take some time to review this PR, thanks a lot

I don't much like the name either. I wouldn't block, but perhaps growWithoutCopying? or growNoCopy? The whole idea that we are growing the existing array is deceptive though because really we are just creating a new array (maybe), but I can't improve on the name much either,

@msokolov @jpountz Thank you for your comments, I refactored method name as ArrayUtil#growNoCopy.

Thanks, the change looks correct to me. I'm not a fan of the new method's name, but I don't have a better suggestion. I'll merge this change in a few days unless someone objects.

@jpountz Hi, there are no more reviews for a few days, can you help to merge this pr? thanks.

@rmuir @jpountz Hi, this pr is ready to be merged, thanks.


Add an option to automatically sync the current locale with the system locale

Add an option to automatically sync the current locale with the system locale.
So when the system locale is changed, the current/app locale will be reloaded as well (if supported).
Reference: https://github.com/bratan/flutter_translate/issues/20

Can you detect the language change in localeResolutionCallback then rebuild the LocalizationProvider ?

There are some issues preventing this from working currently but yes, I think this will be the way to go.

Thanks for the great package, we may be using it in our app. Is this enhancement still planned?

@doc-rj-celltrak - Yes

@bratan Can you elaborate on why the flutter_device_locale package is needed. The same functionality and the syncing is available in plain Flutter via WidgetsBinding.instance.addObserver(...) or am I missing something?

@kuhnroyal - Because of some iOS issues where different values for the current/selected locale are returned depending on the environment (debug/release) and device type simulator/real device.
So by using flutter_device_locale the real locale is always used regardless of the environment.
More info:
https://github.com/flutter/flutter/issues/14128
https://github.com/bratan/flutter_translate/pull/15

@bratan Thanks, Right I now remember this issue. I though this is solved by adding the correct plist entries tho.

@bratan what about doing this
    final currentLocale = WidgetsBinding.instance.window.locale;
    final locale = currentLocale != null && currentLocale.countryCode != null
        ? currentLocale
        : Localizations.localeOf(context);

to avoid using flutter_device_locale    , btw any progress on this issue? thanks for this great package!

Hi @bratan is there any update on this issue? Thanks.

Hi, there is no update currently as I`m quite busy these days, probably in the near future.

If anyone wants to implement this themselves, you can use a WidgetsBindingObserver and override didChangeLocales(). Do this with a StatefulWidget above MaterialApp.
When a system locale change is detected, you can do something like this:
    Future<void> _didChangeLocales(
    BuildContext context,
    List<Locale>? locales,
  ) async {
    if (locales != null && locales.isNotEmpty &&
        locales[0] != LocalizedApp.of(context).delegate.currentLocale) {
      if (Platform.isAndroid) {
        Restart.restartApp();
      }
    }
  }

In my case, I'm restarting the app natively for Android, due to problems trying to force-rebuild the entire widget tree. I'm using the restart_app package to do that.


chore: cleanup old packages

@kmdrGroch you want to take a look here?

as soon as i finish mine :D


Handles null result results from Reactive stream. [Do Not Merge]

This is an indicator that the Scheduler Service is not available.
Awaiting findings from Paul.
resolves #22

Codecov Report

Merging #26 into master will decrease coverage by 1.1%.
The diff coverage is 80%.

@@             Coverage Diff              @@
##             master      #26      +/-   ##
============================================
- Coverage     98.14%   97.04%   -1.11%
- Complexity       52       54       +2
============================================
  Files             3        3
  Lines           162      169       +7
  Branches          5        8       +3
============================================
+ Hits            159      164       +5
- Misses            3        4       +1
- Partials          0        1       +1

Impacted Files
Coverage Δ
Complexity Δ

...ler/spi/cloudfoundry/CloudFoundryAppScheduler.java
96.55% <80%> (-1.28%)
41 <0> (+2)

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 d63c983...08b3c8a. Read the comment docs.

squashed and merged as 0c49d279838d9e7c377f2a40db16cb77e2f08345


Css font path using relative build path

Ive changed assetsPublicPath to a relative path.
    assetsPublicPath: './',

All works fine except links to font files from css are broken. I've added fonts to my project under
/src/assets/fonts/myfont.woff
I've added them to app.vue like so
@font-face {
    font-family: 'HelveticaNeue';
    src: url('assets/fonts/HelveticaNeue.woff') format('woff');
    font-weight: 400;
    font-style: normal;
  }

All works fine in dev. In production the font files are emitted to dist/static/fonts/ however within the css file the path is
@font-face {
    font-family: HelveticaNeue;
    src: url(static/fonts/HelveticaNeue.6f58d34.woff) format("woff");
    font-weight: 400;
    font-style: normal
}

Which causes the following path error in in the browser
Request URL:http://localhost/dist/static/css/static/fonts/HelveticaNeue.6f58d34.woff
Request Method:GET
Status Code:404 Not Found
The path in the css should be url(../fonts/
Is there a way to resolve this?
Something to do with postcss-url perhaps?

I'm using // Template version: 1.3.1

Please try this: https://github.com/vuejs-templates/webpack/issues/1266#issuecomment-361201523

Hi @LinusBorg thanks your help that does fix the path within the Css file, however now the files are emitted to the wrong folder. They are outputted to one level below /dist/ :(

Damnit. This seems to be really tricky. Relative paths are of he devil :D

yep, its a pain. Pretty sure postcss-url can solve this issue. I see you've added it to the project, maybe it just needs some additional config?

postcss-url is a fairly recent addition to the template (#1115), removing this from .postcssrc.js restores existing functionality.
In regards to adding postcss-url to fix #1199 and #1106, why not just use @import "~leaflet/dist/leaflet.css"; instead of trying to resolve a relative URL? Surely that's the whole point of using a bundler.
But removing postcss-url from .postcssrc.js does actually allow access to node_modules with a relative URL and also access to other relative assets, so there's no real downside here if postcss-url was only added to fix this one issue.

Having the same issue here.
The only thing I've changed from the default config is changing the assetsPublicPath in index.js. I have to do this because my files are not on a webserver but used on an embedded Chrome instance.
    assetsPublicPath: './',

I include the fonts in the style tag of App.vue like this:
@font-face {
  font-family: "Noto Sans SemCond";
  src: local("Noto Sans SemiCondensed"), local("NotoSans-SemiCondensed"),
    url("assets/fonts/subset-NotoSans-SemiCondensed.woff2") format("woff2");
  font-weight: normal;
  font-style: normal;
}

The suggested fix by @LinusBorg from here does not work as well. Is there any way to include fonts in the production build? This seems like a pretty common use case.

I had the exact same issue using the material-design-icons in this template.  My dev configuration worked, but I had set prod to use relative paths.  A valid workaround is described in issue 200 which has been open since July, 2016. The code for your webpack base font rule should be:
{
  test: /\.(woff2?|eot|ttf|otf)(\?.*)?$/,
  loader: 'url-loader',
  options: {
    limit: 10000,
    name: utils.assetsPath('fonts/[name].[hash:7].[ext]'),
    // workaround for vuejs-templates webpack issue 1266
    publicPath: process.env.NODE_ENV === 'production' ? '../../' : '/'
  }
}

Incidentally, all I had to do the get material-design-icons working was npm i material-design-icons, add import 'material-design-icons/iconfont/material-icons.css' to the main.js file, and then use the above workaround.

Same here, need relative path for electron.js, some news about that ?

I had the same issue. My development config worked, but my production build did not. Kept getting the wrong path for fonts. In my case, the dir structure was as below
src
    assets
        fonts
.
.
www
    dist
        static
            fonts

I added the following line to the webpack base config file where it checks for font files.
publicPath: process.env.NODE_ENV === 'production' ? '../../' : '/'

I'm just posting to mention this seems to be an actual issue with the webpack url-loader. While I do not use vuejs-templates (but certainly will in the future), I found this exact issue with one of my older React/Electron projects, then finding myself trying to figure out why my production builds were trying to access fonts using an exact development path.
At the time of this writing I'm using Webpack 4.10.0, and url-loader 0.6.2. While I haven't tried 1.1.1 just yet, it's probably safe to say it doesn't change anything considering the last post was made 27 days ago in the referenced issue.
Anyways, I thought I would mention this before anyone spent too much time trying to find the source of this issue in this particular project.

Just in case somebody is trying to this with an Vuej + Vuetify + Cordova (or Phonegap), I confirm the same work around worked for me. Thanks @johnellinwood  !!

https://cloud.githubusercontent.com/assets/15955272/25930239/b9ea5924-3637-11e7-99ad-9cb88c7f6054.png

https://cloud.githubusercontent.com/assets/15955272/25930239/b9ea5924-3637-11e7-99ad-9cb88c7f6054.png


Uncaught SyntaxError: The requested module 'wink-eng-lite-web-model' does not provide an export named 'default'

Is it possible to use in Deno somehow?
Getting error 'Uncaught SyntaxError: The requested module 'wink-eng-lite-web-model' does not provide an export named 'default' when importing as import model from<EMAIL_ADDRESS>

Hello @joonaskaustel
We have not tested it on deno yet.
Can you try using it with https://cdn.skypack.dev/wink-eng-lite-web-model?
Best,
Sanjaya

Hello @joonaskaustel
We tested it on deno at replit using the following code:

Here is the output:

Here is the URL for the same<EMAIL_ADDRESS>Best,
Sanjaya


Vite + React encountered Uncaught TypeError: Super expression must either be null or a function

Hi, i’m encountered this error when using Vite + React Moralis. This error is not happening when using webpack (npx create-react-app) and only occured when using vite.
main.jsx:

Error:

We have seen several issues with Vite apps. It might be because of the way they handle EsModules.
It might be solvable by configuring the app, but my knowledge of Vite is limiting unfortunately.
We will look into better out-of-the-box support for Vite apps, or provide boilerplate for it in the future

Hi, i’m encountered this error when using Vite + React Moralis. This error is not happening when using webpack (npx create-react-app) and only occured when using vite.
main.jsx:
Error:

A simple fix you can use to overcome this is adding events as a devDependency by running yarn add -D events or npm i --save-dev events and that should get that fixed.

@Qudusayo Thanks mate! I had the same issue and your solution magically solved it.

A quick way to fix this is by adding events as a dev dependency by running yarn add -D events or npm i --save-dev events and that should get that fixed.

Thank you @Qudusayo, this issue made me scratch my head a bit😂, and hopefully they could fix this issue soon


Added Separation behavior

Added seperation feature, check it!
Recording :
https://user-images.githubusercontent.com/96647299/195695451-bffcef73-4d95-463e-a67c-a42bcb23cc1a.mp4
Thank you.
Closes #18

So, that's a good starting point, but now we need to actually implement the Separation behavior. This is a standard term in the literature, described in https://www.red3d.com/cwr/steer/gdc99/ as

Separation steering behavior gives a character the ability to maintain a certain separation distance from others nearby. This can be used to prevent characters from crowding together. To compute steering for separation, first a search is made to find other characters within the specified neighborhood. This might be an exhaustive search of all characters in the simulated world, or might use some sort of spatial partitioning or caching scheme to limit the search to local characters. For each nearby character, a repulsive force is computed by subtracting the positions of our character and the nearby character, normalizing, and then applying a 1/r weighting. (That is, the position offset vector is scaled by 1/r 2.) Note that 1/r is just a setting that has worked well, not a fundamental value. These repulsive forces for each nearby character are summed together to produce the overall steering force. See Figure 14:

So it doesn't mean you want to get away from other agents as far as possible (that would be Flee behavior), but rather avoid getting too much into other people's personal space.
In the README of this project there are links to other game libraries which have implementations of those behaviors -- you can check those for inspiration!


How to I can query return all field in table, don't need defined?

I wanna get all data in table, how to I can do that?
I think it look like query:
const query = gql`
  query getBooks {
    books @rtdbQuery(ref: "/books", type: "Books") @array {
      id @key
      @all
    }
  }
`;

Can you help me?

@minhchienwikipedia
The query-all-in-array example at wiki (https://github.com/Canner/apollo-link-firebase/wiki/Simple-Query-Example#query-all-in-array) should solve your problem.
const query = gql`
  query getUsers {
    users @rtdbQuery(ref: "/users", type: "Users") @array {
      id @key
      name
      birth
    }
  }
`;

@wwwy3y3 I think you don't know what i say, i mean i want get all data in one item not all item in array.
Example:
user: { name: "ABC", birthday: "10-10-2010", country: "Viet Nam", .... (many fields) }
So how to i can query many fields if i don't defined in query string?
If i query like your query is:
 const query = gql
query getUsers {
users @rtdbQuery(ref: "/users", type: "Users") @array {
id @key
name
birth
}
}
;
I can't get many fields i don't defined, i just have "id, name, birthday", i have so many fields, i can't write all in query.

The certainty of the returning fields is one of the most important feature graphQL provides, thus it's impossible to query data without defining fields,
If you want to save time writing fields, you should use fragment (http://graphql.org/learn/queries/#fragments)


配合unocss

会不会发生unocss样式没有生成，预热找不到

Tested the plugin with a Vite + unocss project. It's working fine for me. Are you hitting any issues with it?


Moving the time step in the scene constructor to the "Step" function

It's quite an inconvenience to have to specify it in the constructor rather than the Step function, especially if Step is not called on a seperate thread. Granted, you can use timers, but what if the user doesnt reach 60 fps or the specified time step?
It seems like a simple "fix" that ill probably contribute myself.

Yeah this is a good call. Overall I think constructors can be quite cumbersome. A good strategy could be to move the constructor code into an Init function. The constuctor can just call this Init function and perhaps allocate instance memory on the heap (as opposed to right now, will attempt to on the stack which could easily overflow the stack). Then if users do not want initialization upon construction, the Init() call can be commented out of the constructor and called manually by the user.

Feel free to re-open this if you get a contribution going. Closing for now :)


Python dependency checking, installation

scipy dependency now imported at module load, and checked for during pre-compilation
added quick_setup.jl for easy installation of Xtals + scipy into fresh environments (fixes lurking dependency error)
updated docs to explain use of quick_setup.jl

Closes #40

Codecov Report

Merging #70 (5e659b8) into master (b7820f0) will increase coverage by 0.40%.
The diff coverage is 97.14%.

@@            Coverage Diff             @@
##           master      #70      +/-   ##
==========================================
+ Coverage   92.67%   93.08%   +0.40%
==========================================
  Files          11       11
  Lines         887      925      +38
==========================================
+ Hits          822      861      +39
+ Misses         65       64       -1

Impacted Files
Coverage Δ

src/matter.jl
90.56% <ø> (+7.58%)
:arrow_up:

src/bonds.jl
94.90% <91.66%> (+0.63%)
:arrow_up:

src/Xtals.jl
100.00% <100.00%> (ø)

src/atomic_masses.jl
100.00% <100.00%> (ø)

src/covalent_radii.jl
100.00% <100.00%> (ø)

src/cpk_colors.jl
100.00% <100.00%> (ø)

src/crystal.jl
90.34% <100.00%> (-0.37%)
:arrow_down:

src/distance.jl
93.67% <100.00%> (+2.59%)
:arrow_up:

src/misc.jl
98.48% <100.00%> (+0.15%)
:arrow_up:

... and 7 more

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 b7820f0...5e659b8. Read the comment docs.


[#29] Add parallel core test runner (main)

The usage for run_core_tests.py has not changed, just added a new option and parallel-ized all the innards

Puttin it in. Thanks!


Added "hcp-prepare-aws-account"

 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.