added logic for handling slices rreturn empty arrays

The first issue is having trim_audio handle cases where it may return an empty array on output.
offset_bytes == offset_bytes + duration_bytes) is True checks when the indices are the same, which would return a slice of [x:x+y] which is empty.
len(audio_buffer) <= self.transcriber_config.sampling_rate checks when the length of the audio_buffer is less than the sampling rate.
The length of the audio_buffer counts the number of bytes.
For the cases where we have either 0 or 1 chunks, this is less than or equal to one second of sample rate.
This handles the edge cases and returns the audio_buffer as is.
Otherwise, if both of these cases fail, then we proceed with trimming the audio_buffer.

The trim_audio method relies on offset_s and duration_s converting from float to int, where they represent the index of a bytearray.
This wasn't totally obvious at first glance for me:
offset_bytes -= total_bytes - len(audio_buffer)
As I read the whole function:
The indices based on  offset_s and duration_s cast to offset_bytes and duration_bytes.
By definition, offset_bytes grows less slowly than (offset_bytes + duration_bytes)
At (offset_bytes + duration_bytes > total_bytes), which is roughly in the middle, duration_bytes starts to go negative.
So the whole picture looks something like this:

The indexes tend to zero out for small inputs close to zero, and also for inputs with a small difference between them.
This is especially the case for samples where the audio_buffer is small and total_bytes is small.

Bug reproduction:
{session_id}.json}:
{"messages": [{"text": "test", "sender": "human", "timestamp":<PHONE_NUMBER>.747542, "metadata": {"confidence": 1.0, "is_interrupt": true, "path": "cache/transcript_0.wav", "duration": 0}}], "start_time":<PHONE_NUMBER>.746528}
transcript_0.wav: 44 bytes
Here is what we can get from the metadata for a zero-length transcript.
The actual file is 44 bytes, since this is the length of a header.
From session logs and transcripts, the actual message does get processed, transcripts with a non-zero message count still return an empty transcript. In all of these cases, the message was 1-2 words.

Here was the problem:
offset_bytes -= (total_bytes - len(audio_buffer))
Here is the basic setup of the problem.
We have a transcript being uploaded with a length of zero frames.
This would be a transcript file that contains only 44 bytes, the length of a header and zero frames, which is what we see here:
44 Aug 29 21:13 transcript_2.wav
Now we reference the metadata associated with it and the message prior.
106924 Aug 29 21:13 transcript_1.wav


awscli - add range-get and multipart sse-c tests

travis build failure is unconnected to this PR. docker build -f Dockerfile.dev -t play.minio.io/mint:travis-$TRAVIS_PULL_REQUEST_SHA . ran successfully locally whereas on travis RUN build/mc/install.sh command fails

nvm, it passed @deekoder  this can be merged.


Update CaptureWindow position after filtering

We had the issue that after filtering sometimes the capture windows
doesn't show anything because as we are not showing some tracks anymore,
the old position doesn't have any track. In this PR we ask for an update
after updating tracks position, so the view y-position is clamped for the
new top-y and bottom-y coordinates.
Something to consider:

I don't like TrackManager asking CaptureWindows to update position.
We should have a better way to do this (CaptureWindows updating its
position after drawing, but as it wasn't that simple) I left as it is
now.

I overloaded the method UpdateWorldTopLeftY because I feel that it is
nicer (can be convinced about the opposite)

This solution came from the idea in
https://github.com/google/orbit/pull/2089 (almost copy-paste) but without splitting
UpdateTrackPosition and UpdateTrackPrimitives

Solve http://b/182978978.
Test: Load a capture, move the screen, filter.

Do you have an idea how to address this outside of trackmanager?

Quickly looked into the code. TimeGraph is the only caller of TackManager::UpdateTracks. Shouldn't we just move the call to GetCanvas()->UpdateWorldTopLeftY() right after this call in TimeGraph?

Do you have an idea how to address this outside of trackmanager?

Quickly looked into the code. TimeGraph is the only caller of TackManager::UpdateTracks. Shouldn't we just move the call to GetCanvas()->UpdateWorldTopLeftY() right after this call in TimeGraph?

Yes, thanks for catching this. I only was thinking on solving this inside CaptureWindows and I forget this quick-win. I still think this should to be manage with CaptureWindows itself, but we are one step ahead xD


feat: enable matplotlib and plotly in examples

This pull-request fixes #301 by ensuring plotly is supported in our theme. Matplotlib support is explored too.

Plotly and matplotlib are supported. Main issue here is that the different extensions are getting in conflict because "sphinx-gallery" generates a bunch of files. Still working on it.


Get alerts via icinga API?

Proposal: Allow to pass icinga URL and host/service for alerts. Kured will query icinga API and if there is an active alert on the specific host/service - the node will not be rebooted.
Useful for users (like us) who use icinga/nagios for monitoring.

I suppose this could be implemented in a similar fashion as https://github.com/weaveworks/kured/blob/834e7d191d029c733930eb561e3f40ace470d8a3/cmd/kured/main.go#L153-L167 .

Though I am afraid people will just come with different solutions... Does someone have an idea on how to make this generic? Webhooks?


error

logs
https://gist.github.com/mat41997/32cf3b2d9dc5ac464258e0120df76dd7
timings
https://timings.aikar.co/?id=0570cf120a004f89847ad9adab1a9b9a
torch
https://github.com/TorchSpigot/Torch
https://yivesmirror.com/downloads/torch

Hey, this plugin doesn't work on 1.11 or older versions of the spigot.
Thank you for the report anyway. 😄


store_baseline_file_branch flag overwrites the README.md file

Issue Description
When store_baseline_file_branch is set to 'true', the action will update the results.json file within in that specified branch. However, along side results.json the Veracode pipeline scanner's README.md file is also committed to the repository.
Screenshots

Issue Source
I suspect the issue is stemmed from pipeline-scan.ts file, where everything within pipeline-scan-LATEST.zip is unzipped in the current directory.
Since README.md is tracked file within our repository, it will be overwritten with this method in commit.ts.
Possible fix
Restrict git stash command to individual file. Example: git stash push -- ${baselineFileName}. This will only stash one file and similarly when checking out the stash we can restrict that baseline file as well: git checkout stash -- ${baselineFileName}

Hi @mouradzadegun, we have completely overlooked your request from last year! We are very sorry for not answering on time. The required updates are now implemented with the latest version of the action v1.0.11. Please give it a try and let us know if it works as expected now.

Hi @julz0815, I can confirm I tested the new version it does work as expected. Thank you for resolving this issue.


Mobile App Support Form

Time Tracking: MA-42
This is done when:

[x] Feedback link text in Profile tab changed to Mobile App Support
[x] Feedback link url in Profile tab changed to new Mobile App Support form url

[ ] Testing PASS in QA

End-to-end testing failed in QA.
Issue: Support ticket assigned incorrectly (email address derivation err)
Next Step: Fix in progress (ETA 1-2d)


preParseHandler vs. postParseHandler

Hi,
Sorry to open an issue for this simple question.
I've searched the web but could not find a clear answer: what is the difference between preParseHandler vs. postParseHandler? What are the assumptions for each one? When should I use one rather than the other?
Is it simply that one (post) is run after the other (pre)? What occurs betwwen the 2 (i.e. what is the "parsing" exactly)?
Thanks in advance

"Parsing" in this context means extracting the raw text and metadata from a document, regardless of its content type.
That is, the text is extracted from binaries such as PDFs, MS Word, etc., or in the case of markup-based documents such as HTML, tags are stripped so you get only the content.  Extracted Metadata depends on each document.  They range from document properties to <meta> tags in HTML pages.
So preParseHandler takes place before text and metadata are extracted while postParseHandler executes after.
So if you need to deal with documents in their original form (e.g., you want to reference HTML tags using DOMTagger or else), you would use pre....  Otherwise, if you want to act on obtained metadata or the text only (without formatting or else), use ``post...```.
Using a handler that is meant to work on text only as a pre-parse handler can produce errors since many documents could be binaries.  You can use the restrictTo configuration that is available to all handlers to make sure your handler only applies to a specific content type.
Does that answer?

Perfectly, Thanks!


CosmosDb Collection Properties and Owned - Blocking Issues

While I realize that this isn't fully enabled and CosmosDb provider is very much a work in progress I'm not confident that the current solution here: 8172 really addresses the issue because Owned classes are exclusive from what I can tell and you need to be able to create collections and lists.
So in a document store it is entirely normal to do this:
public class Contact {
       public ICollection<string> SomeList {get; set;}
       public ICollection<Relationship> Relationships {get; set;
}

public class Relationshp  {
      public RelationshipTypes Type {get; set;}
      public ShortContact OtherContact {get; set;}

In this case EVERYTHING above is stored in the Contact document including a list of ['somevalue1', 'somevalue2'] for the string collection AND the array.
ShortContact is SHARED all over the place. Any time I have a reference that would otherwise be a JOIN in a relational database to the Contact table I use ShortContact that contains a minimum set of properties that describe the contact but not everything in the document.
ShortContact needs to be updated every time the actual contact is updated because the properties like Name in ShortContact need to be updated with the new values.

So the issues are.

It is my understanding (from the error telling me so) that if you put [Owned] on ShortContact and use Fluent on Relationship .HasOneOwned(t => t.OtherContact) as an example that you can't do the same anywhere else in your model because it's now exclusive.
There is no handling for ICollection as far as I can tell. Nor IDictionary.
Owned Collections don't seem to be properly supported because EnsureCreated still tries to create DbContext collection in your database even though the actual Entities all have ToContainer() specified and create their own containers (we use Database level throughput)
Migrations, while not changing the model itself, are vital because you need to be able to update the database with triggers that update things like all ShortContact in the database with new values based on what is being updated/deleted from the root entity.  Migrations don't have to track the model and update it, but they do need to create an empty migration that allows you to add linq commands to update data based on model changes AND update triggers etc. and then gen that into an executable script against your database to be run as part of your ci/cd.

These issues (minus #4) completely defeat the NoSQL/DocumentDb model and make a non-starter for the CosmosDb provider if they're not addressed before release of Ef Core 3.0. (i.e. it's essentially useless for any complex project that is properly using CosmosDb)
While I see references to some of these things in other closed tickets they're all dismissed. They shouldn't be because the CosmosDb provider can't be used in any real-world scenario until such time as these things are properly implemented as intended in the NoSQL world and generate a model that makes sense.
To me, all sub collections should be assumed to be sub collections of the parent document unless there is a DbSet in the DbContext or they are explicitly referenced in the modelBuilder somewhere as entities.
And primitive type lists and dictionaries need to be supported as first class citizens.
Thanks.

@divega @AndriySvyryd to follow up.

It is my understanding (from the error telling me so) that if you put [Owned] on ShortContact and use Fluent on Relationship .HasOneOwned(t => t.OtherContact) as an example that you can't do the same anywhere else in your model because it's now exclusive.

I don't understand the issue that you are experiencing. Can you provide the model that you want to configure and the exception that EF throws?

There is no handling for ICollection as far as I can tell. Nor IDictionary.

I filed https://github.com/aspnet/EntityFrameworkCore/issues/14762

Owned Collections don't seem to be properly supported because EnsureCreated still tries to create DbContext collection in your database even though the actual Entities all have ToContainer() specified and create their own containers (we use Database level throughput)

Could you provide a model that has this issue?

Migrations, while not changing the model itself, are vital because you need to be able to update the database with triggers that update things like all ShortContact in the database with new values based on what is being updated/deleted from the root entity.  Migrations don't have to track the model and update it, but they do need to create an empty migration that allows you to add linq commands to update data based on model changes AND update triggers etc. and then gen that into an executable script against your database to be run as part of your ci/cd.

EF Core doesn't support data migration in general (except some very limited cases with seed data), implementing something as flexible as you are describing is currently out of scope.

Hi @AndriySvyryd

It's really any case where a class is owned by multiple parents.

So if you create a "ShortContact" and you use it on a Relationship which causes it to be owned by the relationship AND you use it on say Account which has a Contact on it, which is also owned based on the methodology being used, EF Core freaks out and says that it's already owned and dies.
The primary issue with this and #3 is that Owned doesn't really solve the problem of NoSQL. You will, because you have no joins, have reference objects that are used everywhere you would have had a join in the database and they will be exactly the same everywhere VERY likely.  In this scenario EF Core falls over. (which is also why it starts generating stuff in a collection under the name of the context.
#4  Sure EF Core does. You can easily create a blank migration right now and execute up/downs with data any time you want with migrationBuilder.Sql.  This is largely what's needed for CosmosDb to start.
However, if done properly there would be a concept of a "Reference" that would be an object per #1 and 2 above and when that reference was created, it would automatically create cosmosdb server side triggers that update the values in the reference everywhere they are in the database automatically when any of the fields changed in the parent document.  AND EF Core would automatically use these triggers without having the specify them.  That would be how I would see migrations working best. The rest is just SQL commands or upsert/delete documents.
Of course at a minimum EF Core needs to support enumerating the triggers that will run on a given collection. As it stands right now you basically can't use triggers because there is no way to specify them and CosmosDb doesn't run triggers unless explicitly told to.
This is all basic stuff in Cosmos that EF Core has to support or you'll have a useless provider that doesn't work in any real-world scenario.  References are a fact of life in Document Databases so Triggers are also not-optional at the very least and then embedded lists of the same type as other embedded lists are also non-optional.
The only part that is slightly optional is Migrations and automatic creation of triggers to clean up references.  And even that, at least it should allow creation of those migrations and then execution of them manually.

@JohnGalt1717 EF Core already supports what you describe in 1 and 3, however you might be running into a bug. Unfortunately unless you provide a repro project there is no practical way for us to find it and fix it.

It's really simple to repro:
Class1 {
public Subclass SubObj {get; set;}
}
Class 2 {
public Subclass SubObj {get; set;}
}
[Owned]
public class Subclass {
……..
}
Write .HasOwned for Class1 and Class2 for their SubObj.
Volia, will crash on EnsureCreated.

@JohnGalt1717 It works fine for me. What version of Microsoft.EntityFrameworkCore.Cosmos are you using?

Preview 2

You mean 3.0.0-preview.19074.3 ? It works, see https://github.com/AndriySvyryd/CosmosRepro
I was able to repro 3 and filed https://github.com/aspnet/EntityFrameworkCore/issues/14841

@divega @smitpatel to follow up.

All: Maybe I'm missing something. Need an explicit sample that uses the same class in multiple parents with owned that shows this standard reference methodology for NoSQL.
Also need to know how to force cosmos to execute triggers in EF Core otherwise that's a show stopper for obvious reasons.

All: Maybe I'm missing something. Need an explicit sample that uses the same class in multiple parents with owned that shows this standard reference methodology for NoSQL.

@JohnGalt1717 https://github.com/AndriySvyryd/CosmosRepro is exactly this

So if you create a "ShortContact" and you use it on a Relationship which causes it to be owned by the relationship AND you use it on say Account which has a Contact on it, which is also owned based on the methodology being used, EF Core freaks out and says that it's already owned and dies.

ShortContact needs to be updated every time the actual contact is updated because the properties like Name in ShortContact need to be updated with the new values.

EF Core does not support triggers, you can define them and run them yourself for now as a work-around. While triggers are useful, at the same time, requiring to update multiple documents like that goes against principal of data embedding inside a document. Because you update Contact, you need to update all the relationships which has short contacts. Ideally, your document which has relationship with other document should not store anything which requires frequent updates. In most cases that comes down to the Id/Pk of the related document. Which once you create the document, you would not change. Lack of join on document database is cons of them (and then there pros to counter certain limitations). You need to figure out what to do on client side in order to get-around the lack of join. Having minified version of document which requires frequent updates is certainly not the ideal way.

@divega Can this be closed now, or is there anything else that needs following up on?

@ajcvickers My issue is that because CosmosDB doesn't support enforcing triggers by default, if EF Core is released without the ability to define triggers per collection, this is a major issue for any significant deployment.
Further the assertion that my method of providing reference data in documents that have associations because of no joins is non-standard is completely incorrect. Mongo, Raven, and many other NoSQL DocumentDbs actually explicitly state that this is how you do it. The even explicitly state that you then should update those associated information whenever the originating document's values are updated.
Thus the entire premise of what and how the cosmosdb provider for EF Core is being written on is incorrect and going to result, as I started this thread with, in a useless provider that can't be used in the real world.
(And that's assuming that you can have multiple owners of the same child class, which you couldn't the last time I checked in Preview 2)

Notes from triage: Added "escape hatches" to the list in #12086 (@AndriySvyryd feel free to move to the correct section and check the box if this is fully done) so that it is easy to drop down to the Cosmos SDK and do things directly there if EF Core does not (yet) have any appropriate abstraction.


fix for mqtt keepalive

Previous code would set keepalive interval to 1 second if a keepalive value was provided (or just not explicitly set to None).
One issue I've noticed with Mosquitto, if you explicitly set keep_alive_interval in MqttClientConfiguration to None, the esp32 will fail to connect. I'm not sure of the cause of this issue (I'm new to MQTT).

You are completely right - thanks for the fix!


model misidentification

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
I have a 2024 Model 3 (highland) but teslamate thinks it's a model 3+ instead.
Expected Behavior
Correctly identify the kind of model 3.
Steps To Reproduce

Have a model 3 highland
setup teslamate for it

Relevant log output
No relevant log.

Screenshots
No response
Additional data
No response
Type of installation
Docker
Version
v1.28.2

What is stored in your cars table, removing the VIN?
What shows on the TeslaMate home page?

Are you referring to the trim badge displayed in the TeslaMate UI?

Are you referring to the trim badge displayed in the TeslaMate UI?

Yes. As well as what is in the database.

Are you referring to the trim badge displayed in the TeslaMate UI?

Yes. As well as what is in the database.

Understood. Since the trim badge data is sourced from the Tesla API, it's possible that Tesla labels this model in that particular way. We can investigate further to see if there's a discrepancy between Tesla's API data and the actual model specifics.

This is my "cars" table, including the VIN. Sorry for the bad formatting.
id |       eid       |       vid        | model | efficiency |     inserted_at     |     updated_at      |        vin        |     name     | trim_badging | set
tings_id | exterior_color | spoiler_type | wheel_type | display_priority | marketing_name
----+-----------------+------------------+-------+------------+---------------------+---------------------+-------------------+--------------+--------------+----
---------+----------------+--------------+------------+------------------+----------------
1 |<PHONE_NUMBER>27749 |<PHONE_NUMBER>517060 | 3     |      0.143 | 2023-12-12 19:02:18 | 2023-12-17 12:35:58 | LRW3E7FS7RC963406 | 10.000 Gauss | 50           |
1 | PearlWhite     | None         | Glider18   |                1 | SR+

50 & SR+

Those two attributes are the reason TeslaMate is displaying Model 3 SR+. You can see that in the marketing_name.
Current code looks at the model and marketing_name. Anyone with a non-Model 3 Highland share their cars table? My guess is it will be the same (looking at TeslaMate code), thus not able to differentiate between a Highland and non-Highland.

I see. I didn't know if that was directly read from my car or somehow decoded from VIN. Well, thanks for taking a look, maybe I have a SR+ after all!

I see. I didn't know if that was directly read from my car or somehow decoded from VIN. Well, thanks for taking a look, maybe I have a SR+ after all!

It is pulled directly from the API. If you are comfortable making API calls, you could pull your vehicle_data from the API and confirm what comes from Tesla.
https://www.teslaapi.io/vehicles/state-and-settings

Definitely beyond my skills. Already took a while to learn enough to understand what a "cars" table is, and how to retrieve it:)

Here i have the 'cars' table with a model 3 highland and a model y.

id
eid
vid
model
efficiency
inserted_at
updated_at
vin
name
trim_badging
settings_id
exterior_color
spoiler_type
wheel_type
display_priority
marketing_name

2
9297092945XXXXX
1689XXXXXXXXXX
Y

1702902957000
1702902958000
LRWYXXXXXXXXXXX

74D
2
MidnightSilver
None
Induction20Black
1
LR AWD

1
9298844120XXXXX
1689XXXXXXXXXX
3

1702902957000
1702904712000
LRW3XXXXXXXXXXX

74D
1
StealthGrey
None
Glider18
1
LR AWD

Here i have the 'cars' table with a model 3 highland and a model y.
id	eid	vid	model	efficiency	inserted_at	updated_at	vin	name	trim_badging	settings_id	exterior_color	spoiler_type	wheel_type	display_priority	marketing_name
2<PHONE_NUMBER>XXXXX	1689XXXXXXXXXX	Y<PHONE_NUMBER>000<PHONE_NUMBER>000	LRWYXXXXXXXXXXX		74D	2	MidnightSilver	None	Induction20Black	1	LR AWD
1<PHONE_NUMBER>XXXXX	1689XXXXXXXXXX	3<PHONE_NUMBER>000<PHONE_NUMBER>000	LRW3XXXXXXXXXXX		74D	1	StealthGrey	None	Glider18	1	LR AWD

This adds more confusion in that yours is referenced as a LR AWD Model 3 Highland. Based upon this, there is not yet a way to designate a Highland Model 3 from the API.
Still interested if either of you could pull your vehicle_data to see what the API returns.


Remove inaccessible diagrams

As part of the 2020 accessibility work, we should remove the following two diagrams from the tech docs as they are not accessible (use colour to denote meaning, not an svg format, alt text, not clear, not necessary):

https://docs.payments.service.gov.uk/api_reference/#payment-status-lifecycle
https://docs.payments.service.gov.uk/payment_flow/#overview

The payment flow overview diagram is already described in the body text so does not need any further changes.
The payment status lifecycle diagram needs to be described in the body text so this ticket will encompass that work.

@miriamalice I've incorporated Krishna's latest information into this PR. Are you happy with the content?


vagrant-goodhosts not updating hosts file on windows

After running vagrant up vagrant reports that goodhosts is "Checking for host entries" and doesn't say anything more about it.
When I attempt to reach the URL (in this case vvv.test) it can't be found.
Looking at my hosts file (C:\Windows\System32\drivers\etc\hosts) there are no entries for vvv.test, one.wordpress.test, or two.wordpress.test.
I can add these manually to the hosts file and that works.
Are there logs somewhere I can look at to see the issue goodhosts is running into?

The log is printed in the console.
Can I have an example of the vagrant output?
Also what version of the plugin are you using?

Below is the log for vagrant up
C:\vvv>vagrant up                                                                                __ __ __ __
\ V\ V\ V / Varying Vagrant Vagrants
 \_/\_/\_/  v3.6.2-git::stable(62c5796)

Platform: platform-mingw32 windows  HyperV-Admin  HasWinAdminPriv  vagrant-goodhosts vagrant-vbguest monochrome-terminal shared_db_folder_disabled, VVV Path: "C:/vvv"
Vagrant: v2.2.15, VirtualBox: vN/A

Docs:       https://varyingvagrantvagrants.org/
Contribute: https://github.com/varying-vagrant-vagrants/vvv
Dashboard:  http://vvv.test

Bringing machine 'default' up with 'hyperv' provider...
==> default: Verifying Hyper-V is enabled...
==> default: Verifying Hyper-V is accessible...
==> default: [vagrant-goodhosts] Checking for host entries
    default: Configuring the VM...
    default: Setting VM Enhanced session transport type to disabled/default (VMBus)

Vagrant requires administrator access for pruning SMB shares and
may request access to complete removal of stale shares.
==> default: Starting the machine...
==> default: Waiting for the machine to report its IP address...
    default: Timeout: 120 seconds
    default: IP: <IP_ADDRESS>
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: <IP_ADDRESS>:22
    default: SSH username: vagrant
    default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Preparing SMB shared folders...
    default: You will be asked for the username and password to use for the SMB
    default: folders shortly. Please use the proper username/password of your
    default: account.
    default:
    default: Username (user[@domain]<EMAIL_ADDRESS>    default: Password (will be hidden):

Vagrant requires administrator access to create SMB shares and
may request access to complete setup of configured shares.
==> default: Setting hostname...
==> default: Mounting SMB shared folders...
    default: C:/vvv/database/sql => /srv/database
    default: C:/vvv/config => /srv/config
    default: C:/vvv/provision => /srv/provision
    default: C:/vvv/certificates => /srv/certificates
    default: C:/vvv/log/memcached => /var/log/memcached
    default: C:/vvv/log/nginx => /var/log/nginx
    default: C:/vvv/log/php => /var/log/php
    default: C:/vvv/log/provisioners => /var/log/provisioners
    default: C:/vvv/www => /srv/www
==> default: Machine already provisioned. Run `vagrant provision` or use the `--provision`
==> default: flag to force provisioning. Provisioners marked to run always will still run.
==> default: Running action triggers after up ...
==> default: Running trigger: VVV Post-Up...
    default: Running: inline script
    default:  * Restarting Nginx
    default:  * Restarting MariaDB
    default:  * Syncing clocks
    default: 24 Apr 22:09:43 ntpdate[3481]: adjust time server <IP_ADDRESS> offset -0.006679 sec
    default:
    default:   ✧ ▄▀▀▀▄▄▄▄▄▄▄▀▀▀▄ ✧  Thanks for  __ __ __ __
    default:    ✧█▒▒░░░░░░░░░▒▒█    using       \ V\ V\ V /
    default:  ✧   █░░█░░░░░█░░█ ✧                \_/\_/\_/
    default:   ▄▄  █░░░▀█▀░░░█  ▄▄✧
    default:  █░░█ ▀▄░░░░░░░▄▀ █░░█ Vagrant Up has finished! Visit http://vvv.test
    default: ──────────────────────────────────────────────────────────────────────

Thanks looking at the code https://github.com/goodhosts/vagrant/blob/65edd1fd1450504cd610e0d34ff146951b6da4a9/lib/vagrant-goodhosts/GoodHosts.rb#L95 seems that the plugin didn't find any ip address to parse. Maybe I can add an alert for this case.
Maybe it is something in the settings of VVV?

Have you did some changes to the vvv config file?

I'm wondering if it has to do with Hyper-V. I've run into a few different issues using VVV with Hyper-V over the last few days. Maybe Hyper-V picks up the IP at a different point than goodhosts is expecting?

I don't know, I have no idea about the VVV settings as example. Maybe there is something wrong there and the plugin get wrong data.

@davidshq
for hyper-v has limitations on how vagrant works. you can't set a static IP. so whatever when you do a vagrant up, it will detect an IP and may have to edit the hosts file manually with that IP address.


add thai translation

I would like to add Thai translation to justdelete.me. Please review my PR. :)

Fixed as you suggest. Please have a look. 😄

Looks fine to me nw @wattachai , thanks!


Intended way to set_figure_params for a single figure

I was wondering, what is the intended way to temporarily set plotting parameters, e.g. figsize?
Say I want to increase the figsize just for a single UMAP plot.
I could either temporarily set_figure_params and reset it manually afterwards
sc.set_figure_params(figsize=(8, 8))
sc.pl.umap(adata, color="cell_type")
sc.set_figure_params(figsize=(4, 4)) # or whatever it was before...

Or create the figure separately:
_, ax = plt.subplots(figsize=(8, 8))
sc.pl.umap(adata, color="cell_type", ax=ax)

Would it make sense to extend set_figure_params to act as a context manager?
with sc.set_figure_params(figsize=(8, 8), frameon=False):
    sc.pl.umap(adata, color="cell_type")

But maybe there's a comparable way already?

You can use matplotlib's rc_context. E.g.:
with plt.rc_context({"figure.figsize": (8, 8), "figure.dpi": (300)}:
    sc.pl.umap(adata, ...)

cool, thanks!


half letters of Hindi Words are not not rendering correctly in TextField Flutter web.

on Left Side, the highlighted word is in the database (or desired result) while the right side word is in TextField. I want both the word to be the same Any solution around it this is occurring in Flutter web.

[√] Flutter (Channel stable, 2.0.6, on Microsoft Windows [Version
10.0.19042.804], locale en-US)
• Flutter version 2.0.6 at C:\Users\ASUS\flutter2
• Framework revision 1d9032c7e1 (5 weeks ago), 2021-04-29
17:37:58 -0700
• Engine revision 05e680e202
• Dart version 2.12.3
[√] Android toolchain - develop for Android devices (Android SDK
version 30.0.0-rc3)
• Android SDK at C:\Users\ASUS\AppData\Local\Android\Sdk
• Platform android-30, build-tools 30.0.0-rc3
• ANDROID_HOME = C:\Users\ASUS\AppData\Local\Android\Sdk
• Java binary at: C:\Program Files\Android\Android
Studio\jre\bin\java
• Java version OpenJDK Runtime Environment (build
1.8.0_242-release-1644-b01)
• All Android licenses accepted.
[√] Chrome - develop for the web
• Chrome at C:\Program Files
(x86)\Google\Chrome\Application\chrome.exe
[!] Visual Studio - develop for Windows (Visual Studio Community
2019 16.6.2)
• Visual Studio at C:\Program Files (x86)\Microsoft Visual
Studio\2019\Community
• Visual Studio Community 2019 version 16.6.30204.135
X The current Visual Studio installation is incomplete. Please
reinstall Visual Studio.
[√] Android Studio (version 4.1.0)
• Android Studio at C:\Program Files\Android\Android Studio
• Flutter plugin can be installed from:
https://plugins.jetbrains.com/plugin/9212-flutter
• Dart plugin can be installed from:
https://plugins.jetbrains.com/plugin/6351-dart
• Java version OpenJDK Runtime Environment (build
1.8.0_242-release-1644-b01)
[√] VS Code (version 1.56.2)
• VS Code at C:\Users\ASUS\AppData\Local\Programs\Microsoft VS
Code
• Flutter extension version 3.12.2
[√] Connected device (3 available)
• Windows (desktop) • windows • windows-x64    • Microsoft
Windows [Version 10.0.19042.804]
• Chrome (web)      • chrome  • web-javascript • Google Chrome
91.0.4472.77
• Edge (web)        • edge    • web-javascript • Microsoft Edge
89.0.774.75
! Doctor found issues in 1 category.

@a1111198
Are you using any 3rd party keyboard to type in Hindi or using the language option of your machine ?

Basically using on Flutter web. I am using google translator API which is translating the text and autofill (means a translate button translates it and fill using a controller). But If I copy Text from google translator and paste it still gets the same result.

@a1111198
Np, forget about flutter localizations. Can you provide more details / steps as how you are implementing below alongwith a complete minimal code sample, that we can use to verify.

I am using google translator API which is translating the text and autofill (means a translate button translates it and fill using a controller). But If I copy Text from google translator and paste it still gets the same result.

I just created a new project for verification purposes. Just create a new project and replace the code of the main file with the following code:
import 'package:flutter/material.dart';
void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  // This widget is the root of your application.
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key key, this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  TextEditingController _controller;
  @override
  void initState() {
    _controller = TextEditingController();
    super.initState();
  }

  @override
  void dispose() {
    _controller.dispose();
    super.dispose();
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text(widget.title),
      ),
      body: Center(
        child: Column(
          mainAxisAlignment: MainAxisAlignment.center,
          children: <Widget>[
            Container(
              width: 200,
              child: TextField(
                controller: _controller,
              ),
            )
          ],
        ),
      ),
    );
  }
}

Now run this code in Chrome (web) now copy आत्मसंतुष्ट and paste there.  you may check the results.

@a1111198
Before verifying if this is a Flutter web issue or not, can you confirm if the Hindi word renders properly in non-flutter web app ?

This code sample is working fine for Android i.e Hindi word renders properly in the android app.
I don't have a mac so can't say anything about IOS and MACOS. also don't have Linux as my operating system so not sure about it. and for Windows, the desktop app is not running due to some other reasons so could not check for windows.

Thanks for the code sample and details around it.
This seems to be a canvaskit rendering issue, as, with html rendering, the word is rendered properly as shown below:

With flutter run -d chrome --web-renderer html:

With flutter run -d chrome:

 flutter doctor -v
[✓] Flutter (Channel stable, 2.2.1, on Mac OS X 10.15.4 19E2269 darwin-x64,
    locale en-GB)
    • Flutter version 2.2.1 at /Users/dhs/documents/fluttersdk/flutter
    • Framework revision 02c026b03c (4 days ago), 2021-05-27 12:24:44 -0700
    • Engine revision 0fdb562ac8
    • Dart version 2.13.1

[✓] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    • CocoaPods version 1.10.1

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.55.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (4 available)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 91.0.4472.77

• No issues found!

the issue has been solved.
others can read more about Web renderers from  here
solution for this issue   is also same.
Thanks for taking interest in this issue.

Not sure why you said it's solved, but looks a clear case of canvaskit rendering issue. You although have an option to continue using html rendering, but would like to keep this open for tracking.

Deduplicating with https://github.com/flutter/flutter/issues/81166, but feel free to reopen if I'm mistaken.


[libpq] Update to 12.2 and some feature fixes

should fix some issues mentioned in #10875 + and update to 12.2

Hi @Neumann-A
Thanks for this PR.
Could you look into the regression on arm64-windows?
Unable to determine OpenSSL version: The openssl.exe command wasn't found. at C:\vsts\_work\4\s\buildtrees\libpq\arm64-windows-rel\src\tools\msvc/Mkvcbuild.pm line 147.

Related issue #9866

/azp run

@Neumann-A
Could you please help confirm if the test results are as intended in current state?
On Windows:

Error: Cannot find definition for package python, perl, pam, libedit, kerberos, openbsd.

Feature readline, bonjour, systemd, llvm, not supported by configure script on the target platform.

Feature tcl, uuid  is not yet implement on the target platform.

When I run .\vcpkg.exe install libpq[openssl,zlib,nls,ldap,icu,xml,xslt,client]:x64-windows, I met the error:
F:\10915\vcpkg\buildtrees\libpq\x64-windows-rel\src\backend\utils\adt\pg_locale.c(995,51): error C2037: left of 'locale_name' specifies undefined struct/union '__crt_locale_data' [F:\10915\vcpkg\buildtrees\libpq\x64-windows-rel\postgres.vcxproj]
         F:\10915\vcpkg\buildtrees\libpq\x64-windows-rel\src\backend\utils\adt\pg_locale.c(996,36): error C2198: 'wchar2char': too few arguments for call [F:\10915\vcpkg\buildtrees\libpq\x64-windows-rel\postgres.vcxproj]

But if I remove client from the list, other features can build successfully.
After then, I rebuild client, there is no error.
It's so weird. On Visual Studio 2019, client still cannot be built successfully. I don't know why.
On Linux:

Error: Cannot find definition for package python, perl, pam, libedit, kerberos, openbsd, openldp.

Feature readline, bonjour, systemd, not supported by configure script on the target platform.

Feature tcl, uuid , llvm is not yet implement on the target platform.

Current;y, feature openssl,zlib,nls,ldap,icu,xml,xslt,client  have passed with the following triplets:

x86-winodows
x64-windows
x64-linux

Note: client  seems to be conflict with other features on Windows. So it needs to be built
separately.
On x64-windows-static

For client feature, some errors like this:

64>libpq.lib(fe-connect.obj) : error LNK2019: unresolved external symbol __imp_FreeCredentialsHandle referenced in function pqDropConnection [F:\10915\vcpkg\buildtrees\libpq\x64-windows-static-rel\reindexdb.vcxproj]
    64>libpq.lib(fe-connect.obj) : error LNK2019: unresolved external symbol __imp_DeleteSecurityContext referenced in function pqDropConnection [F:\10915\vcpkg\buildtrees\libpq\x64-windows-static-rel\reindexdb.vcxproj]
    64>libpq.lib(fe-auth.obj) : error LNK2019: unresolved external symbol AcquireCredentialsHandleA referenced in function pg_SSPI_startup [F:\10915\vcpkg\buildtrees\libpq\x64-windows-static-rel\reindexdb.vcxproj]
    64>libpq.lib(fe-auth.obj) : error LNK2019: unresolved external symbol InitializeSecurityContextA referenced in function pg_SSPI_continue [F:\10915\vcpkg\buildtrees\libpq\x64-windows-static-rel\reindexdb.vcxproj]
    64>libpq.lib(fe-auth.obj) : error LNK2019: unresolved external symbol FreeContextBuffer referenced in function pg_SSPI_continue [F:\10915\vcpkg\buildtrees\libpq\x64-windows-static-rel\reindexdb.vcxproj]
    64>libcrypto.lib(e_capi.obj) : error LNK2019: unresolved external symbol __imp_CertOpenStore referenced in function capi_open_store [F:\10915\vcpkg\buildtrees\libpq\x64-windows-static-rel\reindexdb.vcxproj]

For openssl,zlib,nls,ldap,icu,xml,xslt features, there are no any errors.

Personally, it might be better to remove these features that are not supported or implemented currently. What do you think about this? @Neumann-A
I also have a question about the first kind of error:
Error: Cannot find definition for package python, perl, pam, libedit, kerberos, openbsd, openldp
When building these features, why do they show that these features cannot be defined?

perl, pam, libedit, kerberos, openbsd

Missing vcpkg ports. Need to be added to make those work. Especially kerberos enables gssapi in libpq which should be added to get everything included into libpq. The other features mainly influence details or include other contributions.

Feature readline, bonjour, systemd, llvm, not supported by configure script on the target platform.

intentionally. Those features are not supported on Windows. Give me a Supports:-Field for features ;)

Feature tcl, uuid is not yet implement on the target platform.

means if somebody wants/needs to use these feature they need to implement it in the portfile.

When I run .\vcpkg.exe install libpq[openssl,zlib,nls,ldap,icu,xml,xslt,client]:x64-windows, I met the error:

Needs to be fixed upstream.
error C2037: left of 'locale_name' specifies undefined struct/union '__crt_locale_data'
postgres seems to have accessed a private (implementation detail) of a certain CRT struct which it cannot access any longer due to a change within the headers of the CRT runtime.
https://postgrespro.com/list/thread-id/1555397 seems like they still haven't fixed this.

Personally, it might be better to remove these features that are not supported or implemented currently. What do you think about this?

I personally don't like to remove work already done. Extracting the possible features of a port is always kind of a headache and that is why I personally always add all features which I can see even if they might not yet be supported by VCPKG. One way to deal with something like that would be to allow comments in the CONTROL file

For client feature, some errors like this: (x64-windows-static)

Looking through the perl scripts feature client is currently not supported on x64-windows-static. Requires a lot of changes to make it work

When building these features, why do they show that these features cannot be defined?

The ports do not exists. So they need to be added to vcpkg. python was just missing the version.

@Neumann-A Since vcpkg currently does not support the Supports field for features, I think we should add error information based on the selected feature and triplet in portfile.cmake.

@Neumann-A
Could you please resolve the conflict?

Alright, this looks good to me! Thanks @Neumann-A :D


vimPlugins: add neotest and neotest-rust

Description of changes
https://github.com/nvim-neotest/neotest
https://github.com/rouge8/neotest-rust

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Please rebase

I'm not sure why CI is failing 🤔


npm run build fails when using in a docker container

Strapi version: 3.0.0-beta.6
Node: 12
Locally works ok, but inside a docker container, it cannot build an admin panel.
Dockerfile contents:
FROM node:11.5.0-alpine

COPY . /var/www/cms

WORKDIR /var/www/cms

RUN apk add --no-cache \
  autoconf \
  automake \
  gcc \
  libc-dev \
  libtool \
  make \
  nasm \
  zlib-dev \
  && chmod +x ./strapi.sh

RUN npm install

EXPOSE 1337

CMD ["./strapi.sh"]

strapi.sh contents:
#!/bin/sh
set -ea

_stopStrapi() {
  echo "Stopping strapi"
  kill -SIGINT "$strapiPID"
  wait "$strapiPID"
}

trap _stopStrapi SIGTERM SIGINT

cd /var/www/cms

APP_NAME=${APP_NAME}
DATABASE_HOST=${DATABASE_HOST}
DATABASE_PORT=${DATABASE_PORT}
DATABASE_NAME=${DATABASE_NAME}
DATABASE_USERNAME=${DATABASE_USERNAME}
DATABASE_PASSWORD=${DATABASE_PASSWORD}

NODE_ENV=production npm run build
NODE_ENV=production npm run start &

strapiPID=$!
wait "$strapiPID"

On the step - NODE_ENV=production npm run build - it's failing with following errors:
cms    | Building your admin UI with production configuration ...
cms    | ℹ Compiling Webpack
cms    | (node:17) UnhandledPromiseRejectionWarning: Error: spawn Unknown system error -8
cms    |     at ChildProcess.spawn (internal/child_process.js:372:11)
cms    |     at Object.spawn (child_process.js:543:9)
cms    |     at module.exports (/var/www/cms/node_modules/imagemin-pngquant/node_modules/execa/index.js:204:26)
cms    |     at input (/var/www/cms/node_modules/imagemin-pngquant/index.js:52:13)

Same issue here, exact same configs, however, i even tried adding in a few alpine packages;
RUN apk update
&& apk add --no-cache
bash
build-base
gcc
libtool
autoconf
automake
pkgconfig
nasm
lcms2-dev
libpng-dev libjpeg-turbo-dev giflib-dev tiff-dev
zlib-dev
&& rm -rf /var/cache/apk/*
Seems like alpine will not run pngquant.. see; https://github.com/imagemin/pngquant-bin/issues/65

@dvanblaricom i switched to node:11.5.0 normal, and build is sometimes work and sometimes doesn't, seems like some kind of timeout is happening, could you try a default node:11.5.0 image without installing any additional packages?

Agree with the Vue statement! I am currently attempting the build with node:latest and I still get the same error. i did have it working with ubuntu:bionic and strapi beta 5 with installing gnupg and curl, but when i just went back to using that and strapi beta 7, i am still getting the error. I think it might be strapi beta 7

Have you tried beta6? I had these issues with 5, 6 beta's for now.

I have not, it might be node 11 as well as https://github.com/strapi/strapi/issues/3506

Can you try node:10 image?

yes, trying Node:10 with beta.7 now

same error for me

I'm building mine, meanwhile, how many cores/ram you allocated for docker?

2 cores, 2GB memory and 1GB swap currently on my local machine

Have you tried to clean npm caches? The link you provided, a guy mentioned this.

There's my docker settings:

trying with beta.7, node:10 and added
RUN npm cache clean --force
RUN npm cache verify
RUN npm install

Just found: https://github.com/strapi/strapi/issues/3383, it's related to ram i guess.

I am running into getting strapi-docker started. I have added two providers in the strapi.sh
cd $APP_NAME
npm i -S strapi-provider-upload-google-cloud-storage
npm i -S strapi-provider-upload-aws-s3
strapi dev &

And when I start docker-compose up, I get lodash not found, and I believe this is still something to do with not able to install the modules. I have bumped up the docker daemon memory 3 GB, CPU - 4s, SWAP 1 GB
❯ docker-compose up
Creating network "strapi-docker_default" with the default driver
Creating strapi-docker_db_1 ... done
Creating strapi-docker_api_1 ... done
Attaching to strapi-docker_db_1, strapi-docker_api_1
db_1   | 2019-07-02T03:01:20.129+0000 I CONTROL  [main] Automatically disabling TLS 1.0, to force-enable TLS 1.0 specify --sslDisabledProtocols 'none'
db_1   | 2019-07-02T03:01:20.146+0000 I CONTROL  [initandlisten] MongoDB starting : pid=1 port=27017 dbpath=/data/db 64-bit host=60c92a1e8a07
db_1   | 2019-07-02T03:01:20.146+0000 I CONTROL  [initandlisten] db version v4.0.10
db_1   | 2019-07-02T03:01:20.146+0000 I CONTROL  [initandlisten] git version: c389e7f69f637f7a1ac3cc9fae843b635f20b766
db_1   | 2019-07-02T03:01:20.146+0000 I CONTROL  [initandlisten] OpenSSL version: OpenSSL 1.0.2g  1 Mar 2016
db_1   | 2019-07-02T03:01:20.146+0000 I CONTROL  [initandlisten] allocator: tcmalloc
db_1   | 2019-07-02T03:01:20.146+0000 I CONTROL  [initandlisten] modules: none
db_1   | 2019-07-02T03:01:20.146+0000 I CONTROL  [initandlisten] build environment:
db_1   | 2019-07-02T03:01:20.146+0000 I CONTROL  [initandlisten]     distmod: ubuntu1604
db_1   | 2019-07-02T03:01:20.146+0000 I CONTROL  [initandlisten]     distarch: x86_64
db_1   | 2019-07-02T03:01:20.146+0000 I CONTROL  [initandlisten]     target_arch: x86_64
db_1   | 2019-07-02T03:01:20.146+0000 I CONTROL  [initandlisten] options: { net: { bindIpAll: true } }
db_1   | 2019-07-02T03:01:20.156+0000 I STORAGE  [initandlisten] Detected data files in /data/db created by the 'wiredTiger' storage engine, so setting the active storage engine to 'wiredTiger'.
db_1   | 2019-07-02T03:01:20.160+0000 I STORAGE  [initandlisten] wiredtiger_open config: create,cache_size=989M,session_max=20000,eviction=(threads_min=4,threads_max=4),config_base=false,statistics=(fast),log=(enabled=true,archive=true,path=journal,compressor=snappy),file_manager=(close_idle_time=100000),statistics_log=(wait=0),verbose=(recovery_progress),
db_1   | 2019-07-02T03:01:32.977+0000 I STORAGE  [initandlisten] WiredTiger message [1562036492:977804][1:0x7fee07f14a80], txn-recover: Main recovery loop: starting at 20/11392 to 21/256
db_1   | 2019-07-02T03:01:33.509+0000 I STORAGE  [initandlisten] WiredTiger message [1562036493:509438][1:0x7fee07f14a80], txn-recover: Recovering log 20 through 21
db_1   | 2019-07-02T03:01:33.968+0000 I STORAGE  [initandlisten] WiredTiger message [1562036493:968430][1:0x7fee07f14a80], txn-recover: Recovering log 21 through 21
db_1   | 2019-07-02T03:01:34.036+0000 I STORAGE  [initandlisten] WiredTiger message [1562036494:36173][1:0x7fee07f14a80], txn-recover: Set global recovery timestamp: 0
db_1   | 2019-07-02T03:01:34.057+0000 I RECOVERY [initandlisten] WiredTiger recoveryTimestamp. Ts: Timestamp(0, 0)
db_1   | 2019-07-02T03:01:34.103+0000 I CONTROL  [initandlisten]
db_1   | 2019-07-02T03:01:34.103+0000 I CONTROL  [initandlisten] ** WARNING: Access control is not enabled for the database.
db_1   | 2019-07-02T03:01:34.103+0000 I CONTROL  [initandlisten] **          Read and write access to data and configuration is unrestricted.
db_1   | 2019-07-02T03:01:34.103+0000 I CONTROL  [initandlisten]
db_1   | 2019-07-02T03:01:34.163+0000 I FTDC     [initandlisten] Initializing full-time diagnostic data capture with directory '/data/db/diagnostic.data'
db_1   | 2019-07-02T03:01:34.166+0000 I NETWORK  [initandlisten] waiting for connections on port 27017
api_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>- 3 but none is installed. You must install peer dependencies yourself.
api_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
api_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
api_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
api_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
api_1  | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
api_1  | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
api_1  |
api_1  | +<EMAIL_ADDRESS>api_1  | removed 1 package, updated 1 package and audited 27989 packages in 29.339s
api_1  | found 10 vulnerabilities (1 low, 6 moderate, 2 high, 1 critical)
api_1  |   run `npm audit fix` to fix them, or `npm audit` for details
api_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>- 3 but none is installed. You must install peer dependencies yourself.
api_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
api_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
api_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
api_1  | npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
api_1  | npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules/fsevents):
api_1  | npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"x64"})
api_1  |
api_1  | +<EMAIL_ADDRESS>api_1  | updated 1 package and audited 27989 packages in 23.838s
api_1  | found 10 vulnerabilities (1 low, 6 moderate, 2 high, 1 critical)
api_1  |   run `npm audit fix` to fix them, or `npm audit` for details
db_1   | 2019-07-02T03:02:30.088+0000 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:39266 #1 (1 connection now open)
db_1   | 2019-07-02T03:02:30.091+0000 I NETWORK  [conn1] received client metadata from <IP_ADDRESS>:39266 conn1: { driver: { name: "nodejs", version: "3.2.7" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.9.125-linuxkit" }, platform: "Node.js v10.16.0, LE, mongodb-core: 3.2.7" }
api_1  | (node:85) UnhandledPromiseRejectionWarning: Error: Cannot find module 'lodash'
api_1  |     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
api_1  |     at Function.Module._load (internal/modules/cjs/loader.js:562:25)
api_1  |     at Module.require (internal/modules/cjs/loader.js:690:17)
api_1  |     at require (internal/modules/cjs/helpers.js:25:18)
api_1  |     at Object.<anonymous> (/usr/src/api/strapi-app/node_modules/strapi-provider-email-sendmail/lib/index.js:8:11)
api_1  |     at Module._compile (internal/modules/cjs/loader.js:776:30)
api_1  |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
api_1  |     at Module.load (internal/modules/cjs/loader.js:653:32)
api_1  |     at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
api_1  |     at Function.Module._load (internal/modules/cjs/loader.js:585:3)
api_1  |     at Module.require (internal/modules/cjs/loader.js:690:17)
api_1  |     at require (internal/modules/cjs/helpers.js:25:18)
api_1  |     at module.exports (/usr/src/api/strapi-app/node_modules/strapi-plugin-email/config/functions/bootstrap.js:27:48)
api_1  |     at Promise (/usr/src/api/strapi-app/node_modules/strapi/lib/Strapi.js:358:11)
api_1  |     at new Promise (<anonymous>)
api_1  |     at execBootstrap (/usr/src/api/strapi-app/node_modules/strapi/lib/Strapi.js:346:14)
api_1  |     at Promise.all.Object.values.map.plugin (/usr/src/api/strapi-app/node_modules/strapi/lib/Strapi.js:391:9)
api_1  |     at Array.map (<anonymous>)
api_1  |     at Strapi.runBootstrapFunctions (/usr/src/api/strapi-app/node_modules/strapi/lib/Strapi.js:390:35)
api_1  |     at Strapi.start (/usr/src/api/strapi-app/node_modules/strapi/lib/Strapi.js:125:18)
api_1  |     at process._tickCallback (internal/process/next_tick.js:68:7)
api_1  | (node:85) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
api_1  | (node:85) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
api_1  | (node:85) UnhandledPromiseRejectionWarning: Error: Cannot find module 'lodash'
api_1  |     at Function.Module._resolveFilename (internal/modules/cjs/loader.js:636:15)
api_1  |     at Function.Module._load (internal/modules/cjs/loader.js:562:25)
api_1  |     at Module.require (internal/modules/cjs/loader.js:690:17)
api_1  |     at require (internal/modules/cjs/helpers.js:25:18)
api_1  |     at Object.<anonymous> (/usr/src/api/strapi-app/node_modules/strapi-provider-upload-aws-s3/lib/index.js:10:11)
api_1  |     at Module._compile (internal/modules/cjs/loader.js:776:30)
api_1  |     at Object.Module._extensions..js (internal/modules/cjs/loader.js:787:10)
api_1  |     at Module.load (internal/modules/cjs/loader.js:653:32)
api_1  |     at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
api_1  |     at Function.Module._load (internal/modules/cjs/loader.js:585:3)
api_1  |     at Module.require (internal/modules/cjs/loader.js:690:17)
api_1  |     at require (internal/modules/cjs/helpers.js:25:18)
api_1  |     at module.exports (/usr/src/api/strapi-app/node_modules/strapi-plugin-upload/config/functions/bootstrap.js:27:49)
api_1  |     at Promise (/usr/src/api/strapi-app/node_modules/strapi/lib/Strapi.js:358:11)
api_1  |     at new Promise (<anonymous>)
api_1  |     at execBootstrap (/usr/src/api/strapi-app/node_modules/strapi/lib/Strapi.js:346:14)
api_1  |     at Promise.all.Object.values.map.plugin (/usr/src/api/strapi-app/node_modules/strapi/lib/Strapi.js:391:9)
api_1  |     at Array.map (<anonymous>)
api_1  |     at Strapi.runBootstrapFunctions (/usr/src/api/strapi-app/node_modules/strapi/lib/Strapi.js:390:35)
api_1  |     at Strapi.start (/usr/src/api/strapi-app/node_modules/strapi/lib/Strapi.js:125:18)
api_1  |     at process._tickCallback (internal/process/next_tick.js:68:7)
api_1  | (node:85) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
db_1   | 2019-07-02T03:02:30.182+0000 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:39268 #2 (2 connections now open)
db_1   | 2019-07-02T03:02:30.182+0000 I NETWORK  [conn2] received client metadata from <IP_ADDRESS>:39268 conn2: { driver: { name: "nodejs", version: "3.2.7" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.9.125-linuxkit" }, platform: "Node.js v10.16.0, LE, mongodb-core: 3.2.7" }
db_1   | 2019-07-02T03:02:30.185+0000 I NETWORK  [listener] connection accepted from <IP_ADDRESS>:39270 #3 (3 connections now open)
db_1   | 2019-07-02T03:02:30.186+0000 I NETWORK  [conn3] received client metadata from <IP_ADDRESS>:39270 conn3: { driver: { name: "nodejs", version: "3.2.7" }, os: { type: "Linux", name: "linux", architecture: "x64", version: "4.9.125-linuxkit" }, platform: "Node.js v10.16.0, LE, mongodb-core: 3.2.7" }
api_1  | [2019-07-02T03:02:33.649Z] warn The bootstrap function is taking unusually long to execute (3500 miliseconds).
api_1  | [2019-07-02T03:02:33.650Z] warn Make sure you call it?
api_1  | [2019-07-02T03:02:33.656Z] warn The bootstrap function is taking unusually long to execute (3500 miliseconds).
api_1  | [2019-07-02T03:02:33.656Z] warn Make sure you call it?

On GKE (Kubernetes) when I run the same docker image, I get the error message
Error loading the local develop command. Strapi might not be installed in your "node_modules". You may need to run "npm install"

I changed the strapi-sh to the following and now I am able to run it in docker/kubernetes.
#!/bin/sh
set -ea

_stopStrapi() {
  echo "Stopping strapi"
  kill -SIGINT "$strapiPID"
  wait "$strapiPID"
}

trap _stopStrapi SIGTERM SIGINT

cd /usr/src/api

APP_NAME=${APP_NAME:-strapi-app}
DATABASE_CLIENT=${DATABASE_CLIENT:-mongo}
DATABASE_HOST=${DATABASE_HOST:-localhost}
DATABASE_PORT=${DATABASE_PORT:-27017}
DATABASE_NAME=${DATABASE_NAME:-strapi}
DATABASE_SRV=${DATABASE_SRV:-false}
EXTRA_ARGS=${EXTRA_ARGS:-}

if [ ! -f "$APP_NAME/package.json" ]
then
    strapi new ${APP_NAME} --dbclient=$DATABASE_CLIENT --dbhost=$DATABASE_HOST --dbport=$DATABASE_PORT --dbsrv=$DATABASE_SRV --dbname=$DATABASE_NAME --dbusername=$DATABASE_USERNAME --dbpassword=$DATABASE_PASSWORD --dbssl=$DATABASE_SSL --dbauth=$DATABASE_AUTHENTICATION_DATABASE $EXTRA_ARGS
    cd $APP_NAME
    npm i -S lodash
    npm i -S strapi-provider-upload-google-cloud-storage
    npm i -S strapi-provider-upload-aws-s3
    npm run setup
    cd ..
fi

cd $APP_NAME
NODE_ENV=production npm start

strapiPID=$!
wait "$strapiPID"

Can someone summarize what the current issue was/is so that the admin panel can not be built? In general I assume it's still an issue with the current beta (beta.11), right?
I've tried several configurations and now I'm down to beta.7, with node-10 and I had to delete my application to have it created with the aforementioned beta. THIS WORKS.
Does anyone have an idea why this issue is occuring?
Greetz,
Sascha

Ok, I tried to add few plugins and recreate the admin panel if I run strapi dev. It works when you are running production. Not sure if you have tried using dev or production?

This would be a lot simpler if it wasn't using image minification for production, or didn't use alpine.
I swapped to node-slim and it worked fine. I had to copy over the healthcheck and strapi.sh to my project, and setup the Dockerfile myself.

HI,
We just released a full rebuild of our docker image 🎉
We are closing the issues and open PRs to start fresh.
If you feel like something is missing or want to add things feel free to open new PRs ! 💯

@alexandrebodin please, share a link?

Just read the updated readme ;)

I just had this issue running strapi/strapi:latest with docker-compose, following this guideline, but using mysql instead of Mongo DB: https://strapi.io/blog/how-to-run-a-strapi-dev-stack-with-docker-compose

Error loading the local develop command. Strapi might not be installed in your "node_modules". You may need to run "npm install"

The container won't stay up, so I cannot bash into it and run npm install manually.

@boxedcode Getting the same error with Mongo DB. Have you solved this issue by any chance?

Also here

Hi @idimlab @rogoit @boxedcode  I see you are not all using the same DB. Would you mind onpening new issues with your specific errors so we can triage them and help you out :)

Hi @alexandrebodin ,
how can i help. I just do the installation guide and run in the same isse as the rest here. What can i do now?
See you
Roland

@rogoit You can start by opening a new issue with some informations so we can review it with context of recent changes.
We need to know the OS / version / docker-compose or dockerfile you have created

@alexandrebodin I am sorry to say this but it is a lame strategy to close an unsolved issue just because there's a rebuild of the images. It seems like people are still having the same issues that was first reported a year back. So, it is evident that "rebuilding" images didn't fix anything.

For anyone else having the same issue, here's a dirty fix:

Start the container. This will create the necessary files for a new project.
Stop the container.
cd into the project directory (from host machine).
npm install, assuming almost all distros come with npm preinstalled.
Start the container.

For anyone else having the same issue, here's a dirty fix:

Start the container. This will create the necessary files for a new project.
Stop the container.
cd into the project directory (from host machine).
npm install, assuming almost all distros come with npm preinstalled.
Start the container.

I'm was having the same issue (on MacOS), and this worked for me 👍

but.. it was expected that we would have to instal the node dependencies even working with Docker... ??

I am working on Linux Ubuntu ;)

I just released a new version of the image that fixing an error with the node_modules not being installed if the project doesn't have a package-lock or yarn.lock file. can you test this @rogoit ?

@alexandrebodin I just  got a build that failed for the first time with issue
[3/5] Fetching packages...
warning<EMAIL_ADDRESS>Invalid bin field for "url-loader".
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[4/5] Linking dependencies...
warning "strapi-admin ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>- 3".
warning "strapi-admin ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "strapi-plugin-graphql ><EMAIL_ADDRESS>has unmet peer dependency "koa@^2".
warning "strapi-plugin-graphql ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>|| ^0.10.0 || ^0.12.0 || ^0.13.0".
warning "strapi-plugin-users-permissions ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>[5/5] Building fresh packages...
Done in 49.77s.
Removing intermediate container c09f4541deb0
 ---> 93bbb505f85f
Step 7/10 : COPY . .
 ---> 94d02a7cbc97
Step 8/10 : RUN yarn build --clean
 ---> Running in 106569bbbdd1
yarn run v1.22.4
$ strapi build --clean
Error loading the local build command. Strapi might not be installed in your "node_modules". You may need to run "npm install"
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
The command '/bin/sh -c yarn build --clean' returned a non-zero code: 1
##[error]Process completed with exit code 1.

FROM strapi/strapi:3.1.1-node12

WORKDIR /srv/app

COPY ./package.json ./
COPY ./yarn.lock ./

ENV NODE_ENV staging

RUN yarn install --prod

COPY . .

RUN yarn build --clean

EXPOSE 1337

CMD ["yarn", "start"]

I just released a new version of the image that fixing an error with the node_modules not being installed if the project doesn't have a package-lock or yarn.lock file. can you test this @rogoit ?

It worked for me. thanks ;)

For anyone else having the same issue, here's a dirty fix:

Start the container. This will create the necessary files for a new project.
Stop the container.
cd into the project directory (from host machine).
npm install, assuming almost all distros come with npm preinstalled.
Start the container.

I'm having the same issue (on MacOS), and I will try this here..

but.. it was expected that we would have to install the node dependencies even working with Docker... ??

I have a combo of Azure Web App and mounted Azure Storage volume.  I have SSHed to the container  but can't find the project directory  to run npm install.  I can see the repo already created on the fileshare. My Potsgres db is a hosted service.
version: '3.3'
services:
api:
image: strapi/strapi
init: true
restart: always
environment:
- DATABASE_CLIENT=postgres
- DATABASE_HOST=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
- DATABASE_PORT=5432
- DATABASE_NAME=xxxxxxxxxxxxxxxxxx
- DATABASE_USERNAME=xxxxxxxxxxxxxxxxxxxxxxxxxx
- DATABASE_PASSWORD=xxxxxxxxxxxxxxxxxxxxxxxxxxxx
- DATABASE_SSL=true
ports:
- 80:1337
volumes:
- StrapiMount:/srv/app
- /srv/app/node_modules
Note: "StrapiMount" = ${WEBAPP_STORAGE_HOME} ... docker won't accept ${WEBAPP_STORAGE_HOME}.  Though StrapiMount was defined with a Path, Strapi dumped the app on the root folder.
Can you please point me to how to reach the project directory?   THANK YOU.

Starting your app...

Error loading the local develop command. Strapi might not be installed in your "node_modules". You may need to run "npm install"

NODE_ENV

Same issue for me, but if I start FROM node:14-alpine the node_modules directory is right there, where is supposed to be. 🤔


Compulsory addition of title and description

How to make title and description optional?

Hi, @princemofo
This project assumes that each post contains title and description. Displaying the posts and uploading post is based on this rule.
You can modify the logic of creating, editing and displaying the posts for creating post without title and description.


Update Dart.java

add support android.support.v4.app.Fragment

@f2prateek can we reconsider this feature?

How difficult would that be to create a dart for support artifact ? @dlemures

:+1: for me you can reopen and merge the PR. I agree with @dlemures after a private chat. Feature is powerful and few lines long. Worth it !
This should be released as 2.1.0

Are you OK with it @fprateek ?

@stephanenicolas  I need to re-initiate a merger request?

Yeah I'm fine with it if needed. I think You'll need a rebase + add the dependencies.

Well, I quickly finish it


Geo Gazetteer as a REST API service

This PR provides service mode to geo gazeteer.
The service mode is best to use when doing large number of name to GPS lookups.
(The real delay in CLI mode are from the JVM intialization and Lucene index warmup.
Service mode requires only one JVM init and also keeps the Lucene index warm with all the cache optimizations for subsequent calls!)
Benchmark
CLI Mode

Service mode in embedded Jetty:
EDIT : this benchmark is no longer applicable. See UPDATE 1

UPDATE 1: Service Mode in Embedded Tomcat and JAX-RS with Apache CXF

On a side note, the above screenshots show Tomcat + CXF is twice slower than embedded Jetty for minimal REST services!

@thammegowda +1
Hi Thamme, Thanks for suggesting this. I had a discussion with Chris today on it and he agrees that it's a great idea. Given it's integrated with tika i t should improve time for geo tagging of whole index. I am planning to put a fix in tika regarding algorithm changes I made recently and I can incorporate a client in tika for lucene-geo-gazetter after your changes.
Both of us propose below enhancement in your PR.

Instead of making changes in GeoNameResolver.java it would be better if we create a new class rest/api/GeoNameResolverServer.java and call existing functions to host an endpoint.
It will be nice if we can keep name of query params same as CLI options. Like ?s=Pasadena & c=5 etc..
Can you please use embedded tomcat instead of jetty?

@smadha
Glad to hear. The speed improvement is huge and I am sure Tika's GeoPraser will be faster. Here is my story to support that claim : I had to map about 200,000 location names(detected by NER parser) in one row (for my CSCI-572 coursework) and found that in the first two hours my program was able to map only 20,000 by using the CLI mode. After converting to rest API, the whole 200,000 mappings happened in less than 10 minutes!
I will send another push after making the proposed changes.

The GeoNameHanlder has been modified to cache the index reader.  My changes include an inner static class SearchHandler which neeeds to be refactored as rest/api/GeoNameResolverServer.java.
Yes, it makes sense to keep it consistent.
I double checked the Licence. Jetty is licenced under Apache Licence 2.0.

Jetty is alv2 but I'd prefer tomcat of possible @thammegowda it also has an embedded mode this is an amazing pr!! @smadha thanks for the summary

@chrismattmann :+1:  Will swap embedded jetty with tomcat.

Thanks @thammegowda embedded Tomcat is just as simple really check out the Tomcat7 maven plugin

@chrismattmann Done with the changes, ready to merge!

love @thammegowda @smadha you both are awesome!


Want to store Secrets on PCF for Dotnet Core

I've .Net core services to be deployed on PCF and I'm able to do this.
We have a requirement where we need to store DB Connection strings, Passwords on PCF and should be accessible thru Environment Variables(values should be encrypted).
Looking for suggestions.

This seems like a general question about Cloud Foundry that's not specific to PCF Dev.
PCF ships with CredHub for this use case: https://docs.pivotal.io/pivotalcf/2-3/credhub/index.html
If you're a PCF customer in need of support, please reach out via<EMAIL_ADDRESS>


cmake: kvs-embedded-c target fix

Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>Issue #, if available:
Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This PR will fix possible build error with t31 toolchain by adding "-fPIC" flag:
[ 92%] Linking C shared library ../../lib/libsamplescommon.so
/mips-gcc472-glibc216-64bit/bin/../lib/gcc/mips-linux-gnu/4.7.2/../../../../mips-linux-gnu/bin/ld: ../../lib/libkvs-embedded-c.a(mkv_generator.c.o): relocation R_MIPS_26 against `getRandomNumber' can not be used when making a shared object; recompile with -fPIC
../../lib/libkvs-embedded-c.a: error adding symbols: Bad value


Cannot find module 'webpack/lib/container/ModuleFederationPlugin'

Hello @manfredsteyer
I have an issue when I add module-federation-plugin using ng add @angular-architects/module-federation
with nx projects it add webpack.config.js for each project

but when I run npm start I get this issue :

any idea about this plz ?

Hey
It looks you are using webpack 4, not 5.

@hmaidithamer
please add this to package.json
  "resolutions": {
    "webpack": "5.27.2"
  }

you have to install the deps with yarn.

Beginning with version 12 you can also use npm and you don't need this resolutions section anymore.

you can add the module by using:
const { ModuleFederationPlugin } = require('webpack').container;

you can structure your webpac.config.js as this:
const HtmlWebpackPlugin = require('html-webpack-plugin');
const { ModuleFederationPlugin } = require('webpack').container;
//const ModuleFederationPlugin = require('webpack/lib/container/ModuleFederaionPlugin')
module.exports = {
mode: 'development',
devServer: {
port: 8081,
},
plugins: [
new ModuleFederationPlugin({
name: '....',
filename: '.....',
exposes: {
' ......'
},
}),
new HtmlWebpackPlugin({
template: './public/index.html',
}),
],
};

..... tends to means your code structure

you have to install the deps with yarn.

Beginning with version 12 you can also use npm and you don't need this resolutions section anymore.

@manfredsteyer I'm using nx/cli (nx v12) -> empty preset then generated an angular (v12) host app with the mfe option

I tried updating the code structure with
// const ModuleFederationPlugin = require("webpack/lib/container/ModuleFederationPlugin");
const { ModuleFederationPlugin } = require('webpack').container;
-- not working
Also "resolutions": {
"webpack": "^5.0.0"
},  -- not working
@manfredsteyer -- I am working on  https://github.com/manfredsteyer/module-federation-plugin-example and have same error

I tried updating the code structure with // const ModuleFederationPlugin = require("webpack/lib/container/ModuleFederationPlugin"); const { ModuleFederationPlugin } = require('webpack').container;
-- not working
Also "resolutions": { "webpack": "^5.0.0" }, -- not working
@manfredsteyer -- I am working on https://github.com/manfredsteyer/module-federation-plugin-example and have same error

It looks like you can specify resolution on the root level package. Then it worked for me.


Release v3

It's finally time to release the v3 version, which has been been developed in the develop branch.
For this task we should finally merge develop into main. Merge should be easy, but we should pay attention to conflicts to ensure we keep dependency bumps that have been merged into main.

https://github.com/newrelic/nri-kubernetes/pull/316


feat: use JS SDK's Client for "invoke contract"

This page contained a very complicated, old-school example of how to invoke a smart contract. I've updated it with how to use contract.Client.
I made this somewhat more complicated than it needs to be, showing how to also deploy a new contract from an already-uploaded Wasm hash. I wanted to do this for a few reasons:

The part where we actually call increment has become so simple that
the page feels almost unnecessary, if that's all we show. (Although
maybe that would be good?)
The example contract ID is almost certainly invalid. If people want to
walk through the whole thing, it would be nice to show them how to
walk through the whole thing.
It's actually fairly straightforward! It allows us to show off more of
Client's features.

That said, I would love to add the ability to deploy directly from a file:
Client.deploy({ wasm: "path/to/some/file.wasm" })

If the JS SDK gains this ability, then we can clean up this example even more, removing the stellar contract install CLI step.
Should we keep the old example?
Maybe it's nice to see a side-by-side of low-level JS SDK logic next to higher-level Client logic? Sort of a "peek under the hood", to show how much Client is doing. This seems most useful to SDK/client authors, since I can't imagine most app developers caring to dive into that logic. Unless they encounter some problem, and need to understand these lower-level details? Not sure if this is the document where we should do that, though. Honestly, it might be fine to refer them to the source code of Client.

Preview is available here:http://developers-pr1101.previews.kube001.services.stellar-ops.com

@chadoh and @willemneal, howdy! Are we still working on this one? Waiting on anything? Thanks! :)

Preview is available here:http://developers-pr1101.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr1101.previews.kube001.services.stellar-ops.com

Preview is available here:http://developers-pr1101.previews.kube001.services.stellar-ops.com


Senate votes are indexed by lisID

I have a use case where I am looking for votes on a Senate bill in the 112th Congress and didn't have any data showing up.  It turns out that the source data consistently indexes Legislator votes by bioguideID for the House, but by lisID for the Senate for the 112th-114th Congresses.
parse_votes.py is expecting this to always be bioguideID, so we're not registering any Senate votes in the database:

This source data sure is unnecessarily obfuscated!  I'm going to work on a fix.

Fixed in PR #22.


Allocation output file

Fixes https://github.com/Deltares/Ribasim/issues/659.
notes:

Allocation not done  t = 0 as no flows for sources are available yet.
The saved abstraction is now the last abstraction before the allocation update, should be the average abstraction since the last allocation solve

Here is an example of the behavior of allocation:

The 2 users are completely equivalent, only the demand on one of them is increasing over time. Currently the goal is to maximize the sum of the flows to the users, so the optimization does not care about the composition of that sum. Fair distribution is next (https://github.com/Deltares/Ribasim/issues/726).

@visr we have to decide what users should do when they are not in a subnetwork or allocation is not activated in the TOML. Should they default to demand = allocated?

Should they default to demand = allocated?

Yes I think that makes sense here.

Now I'm actually done with this PR 😋.


Browse project vs browse engagement

To do: Consider whether there are further filters on project page for whether a project is FRO initiated or community initiated


[Large datasets] Speed up download and processing

Various improvements to speed-up creation and processing of large scale datasets.
Currently:

distributed downloads
remove etag from datafiles hashes to spare a request when restarting a failed download

Looks all good :)
I rebased from master and added a test for parallel map_nested

you're da best


remove init container from connector deployment.

Description:
remove init container from connector deployment.

Testing done:
Done

Affected area:

Functional Area

New Functionality
[ ]

CI System
[ ]

CLI Tool
[ ]

Certificate Management
[ ]

Control Plane
[ ]

Demo
[ ]

Documentation
[ ]

Egress
[ ]

Ingress
[ ]

Install
[ ]

Networking
[ ]

Observability
[ ]

Performance
[ ]

SMI Policy
[ ]

Security
[ ]

Sidecar Injection
[ ]

Tests
[ ]

Upgrade
[ ]

Other
[X]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? no

Is this a breaking change? no

Has documentation corresponding to this change been updated in the fsm-docs repo (if applicable)? no

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Please upload report for BASE (release/v1.4@338708b). Learn more about missing BASE report.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@               Coverage Diff               @@
##             release/v1.4     #415   +/-   ##
===============================================
  Coverage                ?   14.25%
===============================================
  Files                   ?      819
  Lines                   ?    64825
  Branches                ?        0
===============================================
  Hits                    ?     9241
  Misses                  ?    55411
  Partials                ?      173

Flag
Coverage Δ

unittests
14.25% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

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


[3pt] Add unit tests for all implemented methods.

Description to be added

All data should be preserved by saving collections in .json files.

Create a schema.sql file with tables that will be analogical to the structure of the classes that you created: games table (add all properties and associations from the parent Item class as table columns)
authors table


upgrade avalonia pkg to 0.10.0

fix avalonia high cpu usage on linux ( https://github.com/AvaloniaUI/Avalonia/issues/5192 )

Not totally clear why build is failed. I'll take a look tomorrow if you don't fix it before.

I tried to revert the change just to verify if build process work but it seems it doesn't depend on the avalonia pkg upgrade.
Actually I'm using CSharpMath lib through direct source ref from my project using latest avalonia without issues:
Directory.Build.props
<Project>
    <PropertyGroup>
        <!-- <AvaloniaVersion>0.10.0-preview5</AvaloniaVersion> -->
        <AvaloniaVersion>0.10.0-rc1</AvaloniaVersion>
        <CSharpMathVersion>0.5.0-beta</CSharpMathVersion>
    </PropertyGroup>
</Project>

csproj
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>net5.0</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="AngouriMath" Version="1.2.0-preview.5" />
    <PackageReference Include="Avalonia.Desktop" Version="$(AvaloniaVersion)" />
    <!-- <PackageReference Include="CSharpMath.Avalonia" Version="$(CSharpMathVersion)" /> -->
  </ItemGroup>

  <ItemGroup>
    <ProjectReference Include="..\..\CSharpMath\CSharpMath.Avalonia\CSharpMath.Avalonia.csproj" />
  </ItemGroup>

</Project>

Yep, it is something else. Can you revert back?

Yep, it is something else. Can you revert back?

I did it

Can you also update the sample project to make it runnable? (i.e. use new style of defining theme etc)

sry I didn't notice of that change, theme uri, because I not used in my example, now updated so avalonia example is runnable
cd CSharpMath.Avalonia.Example
dotnet run

I tried to fix build in #187 and while one was easy to fix the rest isn't obvious. But I think this PR can be merged in before.

Yep, I seen with #187 now Build/Everything works, still pb with test about missing refrence of Color, that's strange because if I run the same cmd of ( https://github.com/verybadcat/CSharpMath/pull/187/checks?check_run_id=1610656618 )
dotnet test CSharpMath.CrossPlatform.slnf -c Release -l GitHubActions --blame --collect:"XPlat Code Coverage" -r .testcoverage -p:PackageReleaseNotes="$RELEASE_NOTES" -p:PackageVersion=187-pr-ci-d97230fd6070d60c60175129ab3dc8cb85228437 -- DataCollectionRunSettings.DataCollectors.DataCollector.Configuration.IncludeTestAssembly=true

it finishes without errors.
I gotten that type of errors sometimes when a project reference an avalonia version while another uses another one, but may also because there is the need to add some ref like https://www.nuget.org/packages/System.Drawing.Common/ or https://www.nuget.org/packages/Microsoft.Windows.Compatibility/
It may useful to change avalonia ref in this file, may using $(AvaloniaVersion) from Directory.Build.props to keep that in sync but unsure if this could help.
Another suggestion is to upgrade entire library from from netcoreapp3.1 to net5.0 ; it may a courageous choice but net5.0 solve many problems about the cross platform in my opinion and actually the recommended one ( https://dotnet.microsoft.com/download )

It may useful to change avalonia ref in this file, may using $(AvaloniaVersion) from Directory.Build.props to keep that in sync but unsure if this could help.

That tests released packages and should use the Avalonia version currently referenced on NuGet.

@devel0 Would you like to accept changes suggested above or better to merge it to the master as is and then open a separate PR for them?

@devel0 Would you like to accept changes suggested above or better to merge it to the master as is and then open a separate PR for them?

@devel0 Would you like to accept changes suggested above or better to merge it to the master as is and then open a separate PR for them?

did it for all suggestions apart for FluentTheme constructor argument-less from code because seems there aren't such construction mode from code ( it may work using dependency injection but for the example could enough using uri spec )

@devel0 Would you like to accept changes suggested above or better to merge it to the master as is and then open a separate PR for them?

did it for all suggestions apart for FluentTheme constructor argument-less from code because seems there aren't such construction mode from code ( it may work using dependency injection but for the example could enough using uri spec )

@FoggyFinder I am busy on other projects right now, you can have the say on this one.

@FoggyFinder I am busy on other projects right now, you can have the say on this one.

@FoggyFinder I am busy on other projects right now, you can have the say on this one.

I've read your mind :-) Done it one minute before the comment was posted

@FoggyFinder I am busy on other projects right now, you can have the say on this one.

I've read your mind :-) Done it one minute before the comment was posted

@FoggyFinder I am busy on other projects right now, you can have the say on this one.

I've read your mind :-) Done it one minute before the comment was posted

@FoggyFinder I am busy on other projects right now, you can have the say on this one.

I've read your mind :-) Done it one minute before the comment was posted


Apply fixes to same error occurrences in current document.

Added the functionality which allows user to apply the all fixes from sarif Log, which belongs to same error, to current document.

    public void Dispose()

Try to unhook the events here.
try something like:
foreach var x in ApplyFixesInDocument.GetInvocationList()
ApplyFixesInDocumentt -= x

Refers to: src/Sarif.Viewer.VisualStudio/Fixes/DisposableDifferenceViewerControl.xaml.cs:67 in 5e9fd32. [](commit_id = 5e9fd320a68804bbac7a0138db12211a0b40e9d6, deletion_comment = False)

    public void Dispose()

Try to unhook the events here.
try something like:
foreach var x in ApplyFixesInDocument.GetInvocationList()
ApplyFixesInDocumentt -= x
Refers to: src/Sarif.Viewer.VisualStudio/Fixes/DisposableDifferenceViewerControl.xaml.cs:67 in 5e9fd32. [](commit_id = 5e9fd32, deletion_comment = False)

great solution! verified it works fine. lesson learned :)


Missing file in unpkg for g2plot, incompatible g2plot version

There is a problem after recent releases in https://unpkg.com/@antv/g2plot@latest/dist/.
The file "g2plot.js" is no longer available there and the file "g2plot.min.js" is not working.
It is also causing problems on yours documentation website - https://ant-design-blazor.github.io/en-US/charts/bullet.

is there a solution for this?

@NPadrutt Some time ago I checked on their documentation and it was working - however I did not see any update on github. So I do not know actually - what I did so it would work I took specific version of the file from https://unpkg.com/browse/<EMAIL_ADDRESS>here and it helped for me. Maybe the current version works well

aah, so you just added the missing file manually?


autoDispose even if there is a listener next screen

Describe the bug
I'm setting the counterState = 10 and next page the counterState = 0 Due to autoDispose it cause the stateProvider dispose. Even tho you switch page directly after you set the state. Which seems weird if you ask me, since we listen to the stateProvider at next screen, so why dispose it even before checking if there is still a listener.
To Reproduce
final counterProvider = StateProvider.autoDispose<int>((_) => 0);

class Screen1 extends ConsumerWidget {
  const Screen1({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    return Center(
      child: ElevatedButton(
        child: const Text("Press me"),
        onPressed: () {
          ref.read(counterProvider.state).state = 10;
          Navigator.push(context, MaterialPageRoute(builder: (context) => const Screen2()));
        },
      ),
    );
  }
}

class Screen2 extends ConsumerWidget {
  const Screen2({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context, WidgetRef ref) {
    final counter = ref.watch(counterProvider);
    return Center(
      child: Text(counter.toString()),
    );
  }
}

Expected behavior
Counter should be 10 and not dispoed so Quick when there is still a listener on the other screen

What happens if the route does not load in e.g 5 seconds and if you fetch data from website and you would like it to dispose immediately after it's unused. But set it before you switch route, what can you do then?

I do not understand the case you're referring to. Can you make an example?
But I'd suggest trying cacheTime. You should be able to see for yourself if it solves your issue

We had the discussion about this on Discord, cacheTime solve the issue, but you told me it was not meant for this and you had something else on mind to fix this.
This is a simple example, but there is cases where i would like to fetch things from an API on one screen through initState and pass the value to the stateProvider then switch screen immediately after to the new screen with that value being used. But autoDispose clear the value, even tho screen2 is listening for the provider

We had the discussion about this on Discord, cacheTime solve the issue, but you told me it was not meant for this and you had something else on mind to fix this.

The scenario we discussed before was different.
This one is solved by cacheTime.

Ah okay, but i opened issue, just to have it as a reminder for you. What should i write, so i can remind you about this situationen we talked about in discord

There's no need for a reminder. It's part of my 2.0.0 todo-list, so it'll come.

Oh okay, sorry for wasting your time here. I really appreciate your work


Consistently called async functions do not work well with fake timers

🐛 Bug Report
Consistently called async functions do not work well with fake timers.
To Reproduce
beforeEach(() => {
  jest.useFakeTimers();
});

const fn = async () => {
  console.log(1);
  await new Promise(resolve => setTimeout(() => resolve(), 10));
  console.log(2);
  await new Promise(resolve => setTimeout(() => resolve(), 10));
  console.log(3);
};

it('test', (done) => {
  fn().then(() => done());
  console.log(4);
  jest.advanceTimersByTime(10);
  console.log(5);
  jest.advanceTimersByTime(10);
});

Here is a result of execution:
yarn run v1.7.0
$ jest --env=node --verbose --resetMocks --resetModules --testMatch=**\\test.test.js
  console.log tests/unit/test.test.js:6
    1

  console.log tests/unit/test.test.js:15
    4

  console.log tests/unit/test.test.js:17
    5

  console.log tests/unit/test.test.js:8
    2

 FAIL  tests/unit/test.test.js (6.749s)
  × test (5052ms)

  ● test

    Timeout - Async callback was not invoked within the 5000ms timeout specified by jest.setTimeout.

Expected behavior
The second promise should be resolved after the second timer advance. Also both of them should be resolved if I call the advanceTimersByTime function once with 20 ms param.
Run npx envinfo --preset jest
Paste the results here:
System:
    OS: Windows 10
    CPU: x64 Intel(R) Core(TM) i7-4790 CPU @ 3.60GHz
  Binaries:
    Yarn: 1.7.0 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
    npm: 5.4.2 - C:\Program Files\nodejs\npm.CMD

Jest version: 23.5.0

I think you should make your test async:
https://jestjs.io/docs/en/asynchronous.html#async-await

I know the reason why it happens. That's right that it is necessary to make a time advance function async and I hope that it will be done and it'll fix the problem. In my test case there is no way not to use fake timers because here was an example. In my real test case there are minutes and even hours of waiting. That's why I need to use it.
P.S. I already solved this problem by rethinking of the app architecture. Now I have config that replaces minutes by seconds in test environment. Also I use integration tests to check time dependent logic and use unit tests to check pure functions execution. So I don't need to fake timers anymore.

this is still an issue and a workaround is discussed on stackoverflow. I think it would still be great if jest can support this usecase with fake timers