react-test-renderer should be a dependency

Having documentation say to add react-test-renderer dependency in addition to enzyme defeats the purpose of npm dependencies.
Couldn't this package be a dependency of enzyme so that you just install enzyme and get what it needs as well?
Alternatively, if there is some reason why this is bad, why not have a peer dependency so that at a minimum you get an install warning rather than a mysterious build error about react-test-renderer missing?

Because the dependency only applies when you're using React 15.5+.
Using any of npm's dependency features would force everyone using any version of React to have the dependencies for all of them.
Eventually we'll be reworking enzyme to use an adapter pattern, so you'd include the adapter for the React version you needed, and it would just have normal dependencies/peerDependencies.
This is mentioned in the readme.

@ljharb but would it hurt react 15.4 users if the dependency was included? Basically you could avoid the consumers doing the extra unexpected step...

Because of the multiple conditional version ranges (that would easily become incompatible), I think it would cause far more problems than it solved.


adjust/fix some log and error messages

Some where just incorrect, some were too spammy. Also added few to log additional info (e.g on CGovernanceManager::UpdateCachesAndClean and CInstantSend::CheckAndRemove).

utACK


Trying to upload

Hey,
I've tried everything to make the filemanager work, and o boi it work.
Well, it ... show off which is nice but I can't upload anything.
I've made a screen capture to show it better :
https://www.youtube.com/watch?v=wauOX1Foqdw
I really don't know why it won't upload, chmod 777 is set to the folder and subfolders  ...

@Epistol The same... any ideas?

@Epistol in my case I found, I have this error after multiple uploading images. I created a new issue for this - #330

@Epistol I solved my problem - #330 . So, check your .htaccess and other url settings. Hope, it will be helpful for you too.

@Epistol I had the same problem but after enabling the extension EXIF it worked like a charm.

If this problem still occurs, please reopen this issue.


material_select('destroy') doesn't work on a child of a cloned element.

When trying to destroy a select that is a child of a cloned element, the generated elements don't go away.
Here's a link to an example.
And here's the code in case the link doesn't work:
<div class='wrapper-div'>
  <select>
    <option value=1>Option 1</option>
    <option value=2>Option 2</option>
  </select>
</div>

<button class='btn' id='copy'>
  Copy this
</button>

$(function() {
  $('select').material_select();

  $('#copy').click(function() {
    var $newSelect = $('.wrapper-div').clone();
    $('body').append($newSelect);
    $newSelect.find('select').material_select('destroy');
  });
});

It looks like this after material_select('destroy') is run on the second element:

Also had the same issue trying to dynamically add selects with a "+" button and letting jquery using a select tag as a template (which actually got material_selected() on body ready). What I had to do is move the template into a very long javascript string variable.

You have two problems, 1 when you call $('select').material_select();  materialize destroys the select and creates an input instead, so you cannot simply clone the result.
Also newSelect.find('select').material_select('destroy'); simply didn't found the select.


Allow for SMTP TLS / SSL transport security to be configured

Right now SMTP communication between NS and the mail relay hard coded.  Update the runtime configuration to allow for TLS and SMTPS.

See Mailer bean definition in SpringBootNotificationConfig

We will, most likely, need to use SMTPS/TLS for sending mail through AWS SES.


error: NetavarkError use Into Trait

Instead of using two function for types String and str we can just use a generic which implements Into. This allows us to only use one function for both.

@mheon @flouthoc PTAL

/lgtm
/approve


Experiencing compatibility issues with at least one Pleroma server

See thread, need to dig into this:
https://friend.camp/@darius/101633836271141997

<EMAIL_ADDRESS>working for me from https://social.wake.st (mastodon) but just tried to follow from https://cathoderay.tube (pleroma) and get I get the hourglass of with "Awaiting approval. Click to cancel follow request"

Thanks, that tracks with what I'm hearing. I probably won't get to this until March 1 (I'm traveling) but I do have a test pleroma server up and running so I can track this down.

Okay I've done some testing. This is using Pleroma v0.9.99. Here is my best documentation of what is going on:

From my test pleroma server, I search an account like<EMAIL_ADDRESS>the search works fine and the account appears with the option to follow

when I hit the "Follow" button it flashes Requesting..., Unfollow, and then Follow in rapid succession

Behind the scenes, this is logged on my Pleroma server:
Mar 11 02:38:33 li1081-165 mix[5322]: 02:38:33.180 request_id=2m5ce55bt8u4ffduuc0048oh [info] POST /api/friendships/create.json
Mar 11 02:38:33 li1081-165 mix[5322]: 02:38:33.187 [info] Relaying https://pl.tinysubversions.com/activities/5a85de32-daa3-4485-8632-25b2cc21284a out
Mar 11 02:38:33 li1081-165 mix[5322]: 02:38:33.187 [info] Sending https://pl.tinysubversions.com/activities/5a85de32-daa3-4485-8632-25b2cc21284a out via AP
Mar 11 02:38:33 li1081-165 mix[5322]: 02:38:33.188 [info] Federating https://pl.tinysubversions.com/activities/5a85de32-daa3-4485-8632-25b2cc21284a to https://bots.tinysubversions.com/api/inbox
Mar 11 02:38:33 li1081-165 mix[5322]: 02:38:33.288 request_id=2m5ce55icl6ob144dc0048p1 [info] POST /users/darius/inbox
Mar 11 02:38:33 li1081-165 mix[5322]: 02:38:33.291 request_id=2m5ce55icl6ob144dc0048p1 [info] Fetching object https://bots.tinysubversions.com/u/pleroma_develop_branch via AP
Mar 11 02:38:33 li1081-165 mix[5322]: 02:38:33.298 request_id=2m5ce55icl6ob144dc0048p1 [info] Sent 200 in 9ms
Mar 11 02:38:33 li1081-165 mix[5322]: 02:38:33.298 [info] Handling incoming AP activity
Mar 11 02:38:33 li1081-165 mix[5322]: 02:38:33.689 request_id=2m5ce55bt8u4ffduuc0048oh [info] Sent 200 in 509ms
Mar 11 02:38:34 li1081-165 mix[5322]: 02:38:34.230 request_id=2m5ce57ag00j4dhvvc0048ph [info] GET /api/users/show.json
Mar 11 02:38:34 li1081-165 mix[5322]: 02:38:34.232 request_id=2m5ce57ag00j4dhvvc0048ph [info] Sent 200 in 2ms
Mar 11 02:38:34 li1081-165 mix[5322]: 02:38:34.717 request_id=2m5ce587hkbvns99gk0048q1 [info] GET /api/qvitter/statuses/notifications.json
Mar 11 02:38:34 li1081-165 mix[5322]: 02:38:34.719 request_id=2m5ce587hkbvns99gk0048q1 [info] Sent 200 in 2ms

You can see I sent out what is presumably the Follow to the inbox of the RSS bot, and shortly thereafter received a POST to /users/darius/inbox, which is indeed the inbox of my user on my test instance. I presume this is the Accept event being sent back by my RSS-to-AP server. If I go take a look there, what was sent is:
{ '@context': 'https://www.w3.org/ns/activitystreams',
id:
 'https://bots.tinysubversions.com/28d2d0afe817fa6fed275e8cce3421fe',
type: 'Accept',
actor: 'https://bots.tinysubversions.com/u/pleroma_develop_branch',
object:
 { '@context':
    [ 'https://www.w3.org/ns/activitystreams',
      'https://pl.tinysubversions.com/schemas/litepub-0.1.jsonld' ],
   actor: 'https://pl.tinysubversions.com/users/darius',
   cc: [ 'https://www.w3.org/ns/activitystreams#Public' ],
   context:
    'https://pl.tinysubversions.com/contexts/13023db2-98ed-4d3b-9982-744f6cd868b8',
   context_id: 41,
   id:
    'https://pl.tinysubversions.com/activities/f186ba1e-a5b3-4a87-b6b3-07f13657818c',
   object: 'https://bots.tinysubversions.com/u/pleroma_develop_branch',
   published: '2019-03-11T02:43:59.841940Z',
   state: 'pending',
   to: [ 'https://bots.tinysubversions.com/u/pleroma_develop_branch' ],
   type: 'Follow' } }

Per the AP spec this seems about right to me (the contents of object is literally just the object the RSS server received from Pleroma on the Follow).
I would assume the Follow request from Pleroma would resolve at this point, but it's not. The account is not added to the FollowersCollection on Pleroma:

And strangely, if I reload the search page it gives me the "unfollow" option for all the bots I've been testing with, even though they are not followed by my user as far as I can tell.

Any thoughts on what is going on here?

Pleroma does not like your actors because they do not declare a followers collection.  This is, presumably, allowed per AP, but Pleroma requires the declaration because we need to know what URIs need special handling (such as the followers collection URI).


SPARTA-623 Error trace is not giving enought information

Given a policy with a KafkaDirect input
When Kafka service is not up
Then it should throw an exception giving the croncrete cause
Given a policy with a KafkaDirect input
When Kafka service is not up
Then it should not give following trace:

LocalSparkStreamingContextActor:63 - null
scala.MatchError: null ....

Fixed also scalastyle. Headers were giving errors

LGTM!

:shipit:

Comment accepted. Will treat it ASAP


Separate mozillians.org urls from DinoPark.

We are going to use a middleware to redirect everything to dino-park. closing this.


Performance issues

I noticed serious performance issue related to using Stream.ReadAsync method which has huge overhead in Simple.MailServer.Mime.StringReaderStream.ReadLineAsync method
for (var i = 0; i < _buffer.Length; i++)
{
   var read = await BaseStream.ReadAsync(_singleBuf, 0, 1, cancellationToken); // <-- this is the issue
   if (read <= 0)

I believe the following articles are related to the issue:
https://ayende.com/blog/173345/the-cost-of-async-i-o-false-assumptions-and-pride
https://nbsoftsolutions.com/blog/await-async-in-c-and-why-synchrony-is-here-to-stay

Hi,
Thank you for the comment. In that case this line should be replaced with custom made function described in the link.
But the purpose of this GitHub project is not in speed or code quality. This is more like show case or proof of concept thing. In description I explicitly stated that this code is not production ready.
So because of this, I will not implement this improvement, which would blur the main purpose of clean and easy understandable code.
Nevertheless, thank you for this valuable info.
Matjaž


Stricter indexing column assignment

There needs to be a "global", consistent indexing scheme downstream from the BDR. This means that the BDR must always assign indices in a consistent pattern. For instance, the UNIT index might be last index, while preceding indices are always TIME indices. In addition, time indices must be arrange in descending order (YEAR > MONTH > DAY), to make it possible to get a proper time-series using sort_index. Naming conventions are another possible way of handling this.

Not relevant since using old indexing scheme


Added functionality to check Updated Environment's Health

Added functionality to check Updated Environment's Health (Green) and Status (Ready) post Update Action. If Healthy, return Success
else Return job as Failure.

I am not sure when any changes will get into this plugin.  I created a fork of this plugin with some fixes if you would like to contribute there. jenkinsci/aws-beanstalk-publisher-plugin


Remove _count vars

what

Remove var.unauthenticated_listener_arns_count and var.authenticated_listener_arns_count variables

why

These variables were a workaround for limitations in old versions of terraform from two years ago. The newer versions in 0.14.x no longer require these variables.

references
N/A

/test all


this isnt an issue but add this pls

like add a thing where u can make it survival, so like if u have noteblocks setup, it will tell u what notes u need

also can u update 1.19.4

I added this feature in my fork of songplayer if u want to give it a try

Added a "survival only" mode that requires you to place the required instruments for a song within reach distance manually, then tunes them automatically when you play the song.


Diff Run Framework

Summary:
This PR adds the framework to selectively run sections based on changes to the model data.  This significantly speeds up the run time when there are no changes and provides incremental improvements when only a subset of data changes are applied across the various sections.
The main logic driving these changes consist of two main parts:

A run_map that keeps track of which sections are completed as part of each run.
A diff action plugin that checks for differences in the files that are generated under roles/dtc/common/files between the current and previous runs.

These changes introduce three new action plugins:

plugins/action/common/read_run_map.py - Reads changes to the run_map.yaml file under roles/validate/files which keeps track of each section that completed during the previous run.
plugins/action/common/run_map.py - Writes changes to the run_map.yaml file under roles/validate/files which records each section that completes during the current run.
plugins/action/dtc/diff_model_changes.py - Calculates the difference between files under roles/dtc/common/files from the previous run and current run.

This PR also introduces a new control parameter called force_run_all to force all sections to run and can be set under group_vars
Sections will be selectively run based on changes to the data model when the following is true:

The force_run_all flag is set to false
All sections in the run_map are set to true from the previous run

Resolve this issue (https://github.com/netascode/ansible-dc-vxlan/issues/177) as part of this PR.


Incorrect error message with unauthorized AD users

Rancher versions:
rancher/server: master at March 15th
Steps to reproduce:

Enable AD authentication
select  Allow members of Projects, plus Authorized Users and Organizations
Login with unauthorized user

results:
UI show error username or password is incorrect instead of getting unauthorized error, the api responds with 401 error though

We can tweak the message I suppose to say "or maybe they're fine, but you're not allowed in" but this is standard practice.  There is only one message and (should be) only one error response for "the server said you can't come in".  It doesn't (shouldn't) expose why you can't come in.
Returning multiple errors like "that username does not exist"*,  "that username is valid but not on the allowed list", or "that username is valid and that's the wrong password" are all unnecessarily leaking information about the underlying auth system.
*: Except in a system with public registration (like most SaaSes), where you can find that out by trying to register the name anyway.

Changed to one of:
Logging in failed: Check credentials, or your account may not be authorized to log in.
Logging in failed: Your account may not be authorized to log in.
depending on the auth provider.

Version - 2.0 master 3/29
Verified fixed


[SPARK-48055][PYTHON][CONNECT][TESTS] Enable PandasUDFScalarParityTests.{test_vectorized_udf_empty_partition, test_vectorized_udf_struct_with_empty_partition}

What changes were proposed in this pull request?
enable two test in PandasUDFScalarParityTests
Why are the changes needed?
test coverage
Does this PR introduce any user-facing change?
no, test only
How was this patch tested?
ci
Was this patch authored or co-authored using generative AI tooling?
no

thanks @HyukjinKwon
merged to master


System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateSignature throws unexpected ArgumentException

Hello Team,
Recently started seeing unexpected ArgumentException exception during token validation. The documented contract doesn't suggest such behavior. A preceding call to JwtSecurityTokenHandler.CanReadToken returned true.
Microsoft.IdentityModel.Clients.ActiveDirectory, Version=5.2.2
Call stack:
System.ArgumentException: IDX12729: Unable to decode the header 'System' as Base64Url encoded string. jwtEncodedString: 'System.Security.SecureString'. ---> Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: K. Path '', line 0, position 0.
at Newtonsoft.Json.JsonTextReader.ParseValue()
at Newtonsoft.Json.JsonTextReader.Read()
at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type)
at System.IdentityModel.Tokens.Jwt.JsonExtensions.DeserializeJwtHeader(String jsonString)
at System.IdentityModel.Tokens.Jwt.JwtSecurityToken.Decode(String[] tokenParts, String rawData)
--- End of inner exception stack trace ---
at System.IdentityModel.Tokens.Jwt.JwtSecurityToken.Decode(String[] tokenParts, String rawData)
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ReadJwtToken(String token)
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateSignature(String token, TokenValidationParameters validationParameters)
at System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken(String token, TokenValidationParameters validationParameters, SecurityToken& validatedToken)

Hi @drago-draganov, it seems like you passed a secure string ('System.Security.SecureString') to JwtSecurityTokenHandler. The reason why CanReadToken returns true is because the method only counts dots and recognizes 'System.Security.SecureString' as a JWS (2 dots).
JwtSecurityTokenHandler doesn't support SecureStrings.

Hi @GeoK,
I don't think I follow. JwtSecurityTokenHandler.ValidateToken accept string as token value. I certainly don't explicitly pass SecureString. The JWT token is provided over the wire as a string. The first step is to validate it, therefore the call to JwtSecurityTokenHandler.ValidateToken.

@drago-draganov Check if you can verify that you are not passing SecureString. Looking at the stack trace you posted, it looks like the string you passed is a SecureString.
Unable to decode the header 'System' as Base64Url encoded string. jwtEncodedString: 'System.Security.SecureString'.

@GeoK I'm not passing SecureString to JwtSecurityTokenHandler.ValidateToken for sure. How can one compile with SecureString argument, since the JwtSecurityTokenHandler.ValidateToken API signature accepts only String? Am I missing something?
The JWT token content itself is coming over the wire and I don't have control how and what is serialized. The error looks to me related to the deserialization of the token.

Any chance that you can capture the token and reproduce? Looking at the stack trace, value of the token that you are passing to ValidateToken is 'System.Security.SecureString'.

To clarify a bit. The issue is not that parsing the token fails due to bad payload, but the way it fails. The current ArgumentException is not expected. Perhaps should be manifested via SecurityTokenException?

@drago-draganov we can't change the exception as we could break users.
We are moving towards JsonWebTokenHandler and I don't think this meets the bar.


Support node development on Apple M1

This is currently blocked by the grpc tools not having precompiled grpc binaries for M1: https://github.com/grpc/grpc-node/issues/1405
Once this issue is complete, we can verify functionality.

Digging into this further, the only real issue is the lack of precompiled binaries for protoc. If we simply require the developer to install protoc on their machine (via brew install protoc), the problem goes away. This is a precompile step that can be run under Rosetta2 if needed, the actual grpc layer works on M1.


[e2e]: container push main default slsa3

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/4070921065
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Thu Feb  2 03:18:10 UTC 2023

Repo: https://github.com/slsa-framework/example-package/tree/main
Run: https://github.com/slsa-framework/example-package/actions/runs/4080782489
Workflow file: https://github.com/slsa-framework/example-package/tree/main/.github/workflows/e2e.container.push.main.default.slsa3.yml
Workflow runs: https://github.com/slsa-framework/example-package/actions/workflows/e2e.container.push.main.default.slsa3.yml
Trigger: push
Branch: main
Date: Fri Feb  3 03:23:01 UTC 2023
Tests are passing now. Closing this issue.


Modify XboxOneDevice to extend MediaPlayerEntity

Simple change here to modify XboxOneDevice class to extend MediaPlayerEntity instead of MediaPlayerDevice. No change in functionality, just following upstream class naming changes in 0.109 to avoid receiving the warning in the log.

Thanks!


switch to Icons8 for icons

Requires a subscription
https://icons8.com/

Do this once you've got funding for DLx.


Fix: ItemList selection bug && navigation bug

Fix: #37277
Fix: ItemList navigation with disabled items

As far I know items[i].selectable and !items[i].disabled are interchangeable here. I think we should use disabled only for rendering stuff and selected for selection.
https://github.com/godotengine/godot/blob/e9ecb06cf36fbf1f9174a3c4727416194d60d7aa/scene/gui/item_list.cpp#L266

I think we should use disabled only for rendering stuff and selected for selection.

If that is the solution, then please update the class reference, so that it does not suggest otherwise. The issue you are linking is about signals getting triggered in cases that the docs suggest they shouldn't.

Is that correct? If so, this PR does not fix #37277.

In my fix it check whether the item can be selected or not, by it's not disabled and selectable (the property of an item) and it solves #37277
but I think we don't have to check if it's disabled or not for selection.
@pycbouh

Sorry for the late review. The fix looks good but the PR needs a rebase.

Superseded by #60123


Seba/ci beauty

This is a rebase of https://github.com/dcSpark/cddl-codegen/pull/115 with the formatting reapplied to master

Will this make it very difficult for #129 to get merged now with the run rustfmt commit at the end? Or will it be fine if #129 runs rustfmt before merging?

Yes, somebody will have to rebase. If their PR can be merged as-is, we can rebase my PR here


Icons not showing

Icons are not visible at Shapes menu:

Installed via Manage collections...->Install From Repository...

I'm not sure what's causing this. The icons show fine when installing via "Install From File..." but not when installing from the repository, so I'm fairly certain it's not a bug with the collection but rather a bug with Pencil. If you could report a bug over in the Pencil repo, that'd be good :smiley:


Area2D Reports Incorrect Collision Information Immediate After Calling set_pos()

In a function if you move an Area2D via set_pos() then call get_overlapping_areas(), Godot will report the collision iteration from the previous iteration, not the current information.
I've created an example that demonstrates this behavior at http://home.comcast.net/~hammerbro/CollisionExample.zip
If you press Left, the two Area2Ds will move to the opposite ends of the screen. If you press Right, they will move to an overlapping position in the center. If you press Space Bar, the current collision information will be printed.
When you first press Right, the Area2Ds will overlap, but within that same function call they will report that they are not overlapping. If you press Space after that they will then report that they do overlap, even though they haven't moved. When you next press Left, they will report that they do overlap, even though they're no longer close to each other. Again, Space will report accurate information, but only because some number of game loops have passed since they were moved.

yes, this is not immediate. All the physics/collision logic is computed in
a separate thread so this information is updated after fixed_process .
Do you really need to check this manually though? Area has signals to let
you know when something entered/exited overlap, it's rare and generally not
needed that you want to check colisions manually, as it's a lot less
efficient
On Wed, Jul 1, 2015 at 1:04 AM, Gastronok<EMAIL_ADDRESS>wrote:

In a function if you move an Area2D via set_pos() then call
get_overlapping_areas(), Godot will report the collision iteration from the
previous iteration, not the current information.
I've created an example that demonstrates this behavior at
http://home.comcast.net/~hammerbro/CollisionExample.zip
If you press Left, the two Area2Ds will move to the opposite ends of the
screen. If you press Right, they will move to an overlapping position in
the center. If you press Space Bar, the current collision information will
be printed.
When you first press Right, the Area2Ds will overlap, but within that same
function call they will report that they are not overlapping. If you press
Space after that they will then report that they do overlap, even though
they haven't moved. When you next press Left, they will report that they do
overlap, even though they're no longer close to each other. Again, Space
will report accurate information, but only because some number of game
loops have passed since they were moved.
—
Reply to this email directly or view it on GitHub
https://github.com/okamstudio/godot/issues/2222.

I do want the ability to create my own physics engine in GDScript -- too many game engines these days are tightly coupled with their physics engines, and it introduces a subtle homogeneity that I find distasteful. To do so, I need the ability to detect and handle collisions myself. Plus the more general-purpose functionality Godot has, the more varied the games people can create.
That being said, it does seem like signals do what I'd expect them to do in this little demo, so it's possible that my immediate plans can be accomplished that way. I'd still consider this a minor bug, though perhaps it's only noticed by people with unusual inclinations (do the physics themselves). I can also understand if it's inextricably linked to the physics engine; I've been messing around with the source code trying to create some kind of force_physics_update() function, but with little success so far.
I'd say if it's not reasonable to adjust this behavior, that at least some kind of footnote should be added warning others that certain function calls may be an iteration behind.

You could set physicsJustChanged = false at the start of _fixed_process(), and then each time you move around something that would impact physics, set it to true and do not try to use physics-dependent features while it's true. It will then be set to false in the following frame and you can then check for collisions...
I'm not sure if you could get something better without completly changing the way the collision logic works.

if you want to handle your own collisions, check the Shape2D API, it has a lot of useful methods for dealing with collision detection yourself


menu item blade Undefined Variable $item

i know , we should'nt edit a vendor script ,
_https://adminlte.io/docs/2.4/main-header_
i have trying to add code in the page.blade.php

 tes
//Main Header code From Document Admin LTE
//this line
after i have been add, i got ...
"Undefined variable: item (View: /var/www/html/laravel/laraveladmin/vendor/jeroennoten/laravel-adminlte/resources/views/partials/menu-item.blade.php) (View: /var/www/html/laravel/laraveladmin/vendor/jeroennoten/laravel-adminlte/resources/views/partials/menu-item.blade.php) (View: /var/www/html/laravel/laraveladmin/vendor/jeroennoten/laravel-adminlte/resources/views/partials/menu-item.blade.php) ◀"
when i ctrl + z
same , still got that .
should i add some code in config/adminlte.php ?
Thanks In Advance

it was fixed and come with version 1.26.x


_ in alertmanager.url gives 'ERRO[0000] invalid Alertmanager URL'

What did you do?
Try to start prometheus with a - in alertmanager.url hostname.
What did you expect to see?
Prometheus startup
What did you see instead? Under which circumstances?
Prometheus fails to start with ERRO[0000] invalid Alertmanager URL
Environment

System information:

root@aio1-prometheus-container-1ce4332a:~# uname -srm
Linux 4.4.0-77-generic x86_64

Prometheus version:

root@aio1-prometheus-container-1ce4332a:~# prometheus -version
prometheus, version 1.6.2 (branch: master, revision: b38e977fd8cc2a0d13f47e7f0e17b82d1a908a9a)
  build user:       root@c99d9d650cf4
  build date:       20170511-12:59:13
  go version:       go1.8.1

Prometheus configuration file:

insert configuration here

Alertmanager configuration file:

---
global:
  scrape_interval:     15s
  evaluation_interval: 15s
rule_files:
  - /etc/prometheus/alarm.rules
scrape_configs:
  - job_name: 'prometheus'
    scrape_interval: 5s
    static_configs:
      - targets: ['aio1_prometheus_container-1ce4332a:9090']
      - targets: ['aio1_prometheus_container-80fbb462:9090']
      - targets: ['aio1_prometheus_container-c162b818:9090']
  - job_name: 'node'
    static_configs:
      - targets: ['aio1:9100']
      - targets: ['aio1_cinder_scheduler_container-dd28c03d:9100']
      - targets: ['aio1_swift_proxy_container-93e91eb6:9100']
      - targets: ['aio1_neutron_server_container-ca547b0f:9100']
      - targets: ['aio1_neutron_agents_container-a7bc08a8:9100']
      - targets: ['aio1_nova_api_os_compute_container-50c11b60:9100']
      - targets: ['aio1_galera_container-d62f36fb:9100']
      - targets: ['aio1_memcached_container-00d6d829:9100']
      - targets: ['aio1_rabbit_mq_container-1fc0866b:9100']
      - targets: ['aio1_designate_container-16f22f3b:9100']
      - targets: ['aio1_nova_console_container-4f609da5:9100']
      - targets: ['aio1_cinder_api_container-67a9eee0:9100']
      - targets: ['aio1_blackbox_container-1b3e1133:9100']
      - targets: ['aio1_blackbox_container-ef36ca7d:9100']
      - targets: ['aio1_blackbox_container-93936ea5:9100']
      - targets: ['aio1_nova_conductor_container-19089b7d:9100']
      - targets: ['aio1_horizon_container-1b6daf91:9100']
      - targets: ['aio1_keystone_container-0be3c486:9100']
      - targets: ['aio1_grafana_container-00075ed0:9100']
      - targets: ['aio1_grafana_container-8ec960f9:9100']
      - targets: ['aio1_grafana_container-fe2142ca:9100']
      - targets: ['aio1_glance_container-b0220d11:9100']
      - targets: ['aio1_nova_api_metadata_container-2bb03f2c:9100']
      - targets: ['aio1_prometheus_container-c162b818:9100']
      - targets: ['aio1_prometheus_container-1ce4332a:9100']
      - targets: ['aio1_prometheus_container-80fbb462:9100']
      - targets: ['aio1_nova_scheduler_container-b51f7087:9100']
      - targets: ['aio1_rsyslog_container-973c250b:9100']
      - targets: ['aio1_nova_api_placement_container-1c03ea59:9100']
      - targets: ['aio1_heat_apis_container-7d40935f:9100']
      - targets: ['aio1_heat_engine_container-ee0e94fc:9100']
      - targets: ['aio1_alertmanager_container-10c18cc4:9100']
      - targets: ['aio1_alertmanager_container-63376c45:9100']
      - targets: ['aio1_alertmanager_container-639c8482:9100']
  - job_name: 'haproxy'
    static_configs:
      - targets: ['aio1:9101']
  - job_name: 'mysql'
    static_configs:
      - targets: ['aio1_galera_container-d62f36fb:9104']
  - job_name: 'alertmanager'
    static_configs:
      - targets: ['aio1_alertmanager_container-63376c45:9093']
      - targets: ['aio1_alertmanager_container-639c8482:9093']
      - targets: ['aio1_alertmanager_container-10c18cc4:9093']

Logs:

root@aio1-prometheus-container-1ce4332a:~# /usr/bin/prometheus -config.file=/etc/prometheus/prometheus.yml -storage.local.path=/var/lib/prometheus/data -alertmanager.url http://aio1_alertmanager_container-63376c45:9093,http://aio1_alertmanager_container-639c8482:9093,http://aio1_alertmanager_container-10c18cc4:9093 -web.console.templates=/etc/prometheus/consoles -web.console.libraries=/etc/prometheus/console_libraries
ERRO[0000] invalid Alertmanager URL: http://aio1_alertmanager_container-63376c45:9093  source=main.go:75

After changing _ in alertmanager.url to -
root@aio1-prometheus-container-1ce4332a:~# /usr/bin/prometheus -config.file=/etc/prometheus/prometheus.yml -storage.local.path=/var/lib/prometheus/data -alertmanager.url http://aio1-alertmanager-container-63376c45:9093,http://aio1-alertmanager-container-639c8482:9093,http://aio1-alertmanager-container-10c18cc4:9093 -web.console.templates=/etc/prometheus/consoles -web.console.libraries=/etc/prometheus/console_libraries
INFO[0000] Starting prometheus (version=1.6.2, branch=master, revision=b38e977fd8cc2a0d13f47e7f0e17b82d1a908a9a)  source=main.go:88
INFO[0000] Build context (go=go1.8.1, user=root@c99d9d650cf4, date=20170511-12:59:13)  source=main.go:89
INFO[0000] Loading configuration file /etc/prometheus/prometheus.yml  source=main.go:251
INFO[0000] Loading series map and head chunks...         source=storage.go:421
INFO[0001] 40498 series loaded.                          source=storage.go:432
INFO[0001] Starting target manager...                    source=targetmanager.go:61
INFO[0001] Listening on :9090                            source=web.go:259

RFC 952 says that:
1. A "name" (Net, Host, Gateway, or Domain name) is a text string up
   to 24 characters drawn from the alphabet (A-Z), digits (0-9), minus
   sign (-), and period (.)

But the rule apparently isn't strictly followed by DNS servers and names in an /etc/hosts file can contain underscores.
Just pointing out that there's a little inconsistency in hostname handling, and we possibly need a better error for special characters? Something like:
Invalid characters, only A-Z,0-9 and . allowed

The library we use for checking urls probably needs updating again.

We use govalidator to do it here: https://github.com/prometheus/prometheus/blob/master/cmd/prometheus/config.go#L354-L369
I verified in the latest master of govalidator that the URL specified above: aio1_alertmanager_container-63376c45:9093 is returning false.
Opened https://github.com/asaskevich/govalidator/issues/212 upstream but not sure it will be fixed there soon. One thing we could do is just pull out the IsURL logic out into prometheus itself and add support for _ as IsURL is the only thing we are using.

I'm against adding support for underscores, it's clearly forbidden by the DNS spec. That there is no validation for entries in /etc/hosts does not change that.

We relaxed the validation criteria after all.


[tem-1856] Introduces schema create command

This PR introduces the schema create command. Very similar to the db create command. Both commands are now added to the README. Both commands were required to introduce the extension enable command.
cr -- db create -n my_database -i test
16:08:35 [INFO] trying to create database 'my_database' on instance 'test'
16:08:35 [INFO] finding config for instance test
16:08:36 [INFO] database created

cr -- schema create -n my_schema -d my_database -i test
16:08:54 [INFO] trying to create schema 'my_schema' for database 'my_database' on instance 'test'
16:08:54 [INFO] finding config for instance test
16:08:55 [INFO] schema created

psql -h localhost -U postgres

postgres=# \l
                                    List of databases
       Name       |  Owner   | Encoding |  Collate   |   Ctype    |   Access privileges
------------------+----------+----------+------------+------------+-----------------------
 my_database      | postgres | UTF8     | en_US.utf8 | en_US.utf8 |
 postgres         | postgres | UTF8     | en_US.utf8 | en_US.utf8 |

postgres=# \dn+
                                         List of schemas
   Name    |       Owner       |           Access privileges            |      Description
-----------+-------------------+----------------------------------------+------------------------
 addons    | postgres          |                                        |
 my_schema | postgres          |                                        |
 pgmq      | postgres          |                                        |
 public    | pg_database_owner | pg_database_owner=UC/pg_database_owner+| standard public schema
           |                   | =U/pg_database_owner                   |

@ChuckHend I updated those attributes (name and created_at) to be required for both schema and database, no longer options.

@ChuckHend you had on db create before I had a chance to update the attributes, so I did them on this PR. Thanks!


database is no longer valid and must be remigrated

What platforms are affected?
linux
What architectures are affected?
amd64
What SpiceDB version are you using?
v1.37.0
Steps to Reproduce
apiVersion: authzed.com/v1alpha1
kind: SpiceDBCluster
metadata:
  name: shortlink
  annotations:
    argocd.argoproj.io/sync-wave: "1"
spec:
  config:
    replicas: 1
    datastoreEngine: postgres
  secretName: shortlink-spicedb-config
  patches:
    - kind: Deployment
      patch:
        spec:
          template:
            metadata:
              annotations:
                sidecar.istio.io/inject: "false"
            spec:
              containers:
                - name: spicedb
                  image: 'ghcr.io/authzed/spicedb:v1.37.0'
                  resources:
                    requests:
                      memory: "128Mi"
                      cpu: "50m"
                    limits:
                      memory: "512Mi"
                      cpu: "200m"
                  env:
                    - name: SPICEDB_DATASTORE_CONN_URI
                      valueFrom:
                        secretKeyRef:
                          name: spicedb-postgres-pguser-spicedb
                          key: uri
                    - name: SPICEDB_DISPATCH_CACHE_METRICS
                      value: "true"
                    - name: SPICEDB_DISPATCH_CLUSTER_METRICS
                      value: "true"
                    - name: SPICEDB_NS_CACHE_METRICS
                      value: "true"
                    - name: SPICEDB_METRICS_ENABLED
                      value: "true"
                    - name: SPICEDB_OTEL_PROVIDER
                      value: otlpgrpc
                    - name: SPICEDB_OTEL_SAMPLE_RATIO
                      value: "1"
                    - name: OTEL_EXPORTER_OTLP_ENDPOINT
                      value: "http://grafana-tempo.grafana:4317"
    - kind: Job
      patch:
        spec:
          template:
            metadata:
              annotations:
                sidecar.istio.io/inject: "false"
            spec:
              containers:
                - name: migrate
                  image: 'ghcr.io/authzed/spicedb:v1.37.0'
                  env:
                    - name: SPICEDB_DATASTORE_CONN_URI
                      valueFrom:
                        secretKeyRef:
                          name: spicedb-postgres-pguser-spicedb
                          key: uri

Expected Result
correct install
Actual Result
{"level":"warn","datastoreReady":false,"time":"2024-10-12T22:17:04Z","message":"datastore failed readiness checks: datastore is not migrated: currently at revision `add-rel-by-alive-resource-relation-subject`, but requires `create-relationships-counters-table`. Please run `spicedb migrate`. If you have previously run `TRUNCATE`, this database is no longer valid and must be remigrated. See: https://spicedb.dev/d/truncate-unsupported"}

spicedb and spicedb-migrate have the identical version, with spicedb saying that the migration is of the wrong version

Very strange. After the next restart, the service started working


Issue 1:	[ 1669644 ] Crash in letter_is_okay() with trigger

https://code.google.com/p/tesseract-ocr/issues/detail?id=1
Reported by tmbdev, Mar 7, 2007
Filip Gieszczykiewicz - filipg(sf)
recognizing attached tif with v1.03 crashes as follows:
pppppspppppppppspppppppppsppppppppppppppppppppppppppp
Program received signal SIGSEGV, Segmentation fault.
0x080fb8a8 in letter_is_okay (dawg=0xb7f09008, node=0xbf815a04,
char_index=7, prevchar=0 '\0',
word=0xbf815bff "proto-ft", word_end=0) at dawg.cpp:49
49 if (edge_occupied (dawg, edge)) {
(gdb) bt
#0 0x080fb8a8 in letter_is_okay (dawg=0xb7f09008, node=0xbf815a04,
char_index=7, prevchar=0 '\0',
word=0xbf815bff "proto-ft", word_end=0) at dawg.cpp:49
#1 0x080f3b26 in append_next_choice (dawg=0xb7f09008, node=108107,
permuter=5 '\005',
word=0xbf815bff "proto-ft", choices=0x82e7ad0, char_index=7,
this_choice=0x8260df0,
prevchar=0 '\0', limit=0xbf815c28, rating=0, certainty=-1.15637732,
rating_array=0xbf815ab4,
certainty_array=0xbf815b58, word_ending=0, last_word=0,
result=0xbf815a58) at permdawg.cpp:202
#2 0x080f3f03 in dawg_permute (dawg=0xb7f09008, node=108107, permuter=5
'\005',
choices=0x82e7ad0, char_index=7, limit=0xbf815c28, word=0xbf815bff
"proto-ft", rating=0,
certainty=0, rating_array=0xbf815ab4, certainty_array=0xbf815b58,
last_word=0)
at permdawg.cpp:273
#3 0x080f40b3 in dawg_permute_and_select (string=0x814f9fc "system
words:", dawg=0xb7f09008,
permuter=5 '\005', character_choices=0x82e7ad0, best_choice=0x8260d40,
system_words=1)
at permdawg.cpp:334
#4 0x080f5640 in permute_words (char_choices=0x82e7ad0, rating_limit=1000)
at permute.cpp:1611
#5 0x080f6549 in permute_all (char_choices=0x82e7ad0, rating_limit=1000,
raw_choice=0xbf815dc8)
at permute.cpp:1092
#6 0x080f6952 in permute_characters (char_choices=0x82e7ad0, limit=1000,
best_choice=0xbf815dd8,
raw_choice=0xbf815dc8) at permute.cpp:1146
#7 0x080d1ef6 in chop_word_main (word=0x826f830, fx=1,
best_choice=0xbf815dd8,
raw_choice=0xbf815dc8, tester=0 '\0', trainer=0 '\0') at
chopper.cpp:476
#8 0x080cf426 in cc_recog (tessword=0x826f830, best_choice=0xbf815dd8,
best_raw_choice=0xbf815dc8, tester=0 '\0', trainer=0 '\0') at
tface.cpp:247
#9 0x08069a94 in recog_word_recursive (word=0x826e9f0, denorm=0x826be54,
matcher=0x80684a0 <tess_default_matcher(PBLOB*, PBLOB*, PBLOB*, WERD*,
DENORM*, BLOB_CHOICE_LIST&)>, tester=0, trainer=,
testing=0 '\0', raw_choice=@0x826be7c,
blob_choices=0xbf8162b8, outword=@0x826be50) at tfacepp.cpp:191
#10 0x0806a380 in recog_word (word=0x826e9f0, denorm=0x826be54,
matcher=0x80684a0 <tess_default_matcher(PBLOB*, PBLOB*, PBLOB*, WERD*,
DENORM*, BLOB_CHOICE_LIST&)>, tester=0, trainer=0, testing=0 '\0',
raw_choice=@0x826be7c, blob_choices=0xbf8162b8,
outword=@0x826be50) at tfacepp.cpp:90
I don't think it's related to issue 1546972
It is dependent on the specific image - recreating a new TIF with pbmtext
of the contained text does not crash. Also, scaling image -2.0 or +2.0 does
not crash - just this one does.
Argh, image too big for sf.net - see
http://tesseract-ocr.repairfaq.org/downloads/b37by2.tif

2007-03-07T22:23:34.000Z
Mar 7, 2007 Project Member #1 tmbdev
(No comment was entered for this change.)
Owner: ---

2007-03-07T22:24:44.000Z
Mar 7, 2007 Project Member #2 tmbdev
(No comment was entered for this change.)
Owner: theraysmith

2007-03-07T22:47:04.000Z
Mar 7, 2007 Project Member #3 tmbdev
(No comment was entered for this change.)
Summary: [ 1669644 ] Crash in letter_is_okay() with trigger

2008-11-14T03:24:22.000Z
Nov 13, 2008 Project Member #4 theraysmith
I found the cause of this, and it will be fixed in 2.04.
Status: Started

2008-12-24T01:04:46.000Z
Dec 23, 2008 Project Member #5 theraysmith
(No comment was entered for this change.)
Status: Duplicate
Mergedinto: 128


FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory

Issue description
One of my nodes is stuck in a reboot loop, as soon as it is up and running it gets a Javascript heap out of memory error and crashes
Expected behavior
Steps to reproduce the problem

Fresh install of the node and it started

Specifications

Node version: OriginTrail Node v8.1.1+beta.3
Platform: Ubuntu 22
Node wallet:0xdA2DE0AD0731Ea28e1d71586798C23701F5375a9
Node libp2p identity: 28

Error logs
Nov 03 05:54:03 ottest3 node[210159]: [2024-11-03 05:54:03] USERLVL: [getCleanerCommand]  level-change Nov 03 05:54:03 ottest3 node[210159]: [2024-11-03 05:54:03] USERLVL: [commandsCleanerCommand]  level-change Nov 03 05:54:03 ottest3 node[210159]: [2024-11-03 05:54:03] USERLVL: [publishResponseCleanerCommand]  level-change Nov 03 05:54:03 ottest3 node[210159]: [2024-11-03 05:54:03] USERLVL: [getResponseCleanerCommand]  level-change Nov 03 05:54:03 ottest3 node[210159]: [2024-11-03 05:54:03] INFO:  Replay pending/started commands from the database... Nov 03 05:54:03 ottest3 node[210159]: [2024-11-03 05:54:03] INFO:  Sharding Table Service initialized successfully Nov 03 05:54:03 ottest3 node[210159]: [2024-11-03 05:54:03] INFO:  Initializing blockchain event listener for blockchain base:84532, handling missed events Nov 03 05:54:06 ottest3 node[210159]: [2024-11-03 05:54:06] INFO:  Event listener initialized for blockchain: 'base:84532'. Nov 03 05:54:06 ottest3 node[210159]: [2024-11-03 05:54:06] INFO:  Event Listener Service initialized successfully Nov 03 05:54:06 ottest3 node[210159]: [2024-11-03 05:54:06] INFO:  Initializing http api and rpc router Nov 03 05:54:06 ottest3 node[210159]: [2024-11-03 05:54:06] INFO:  Enabling network protocol: /store/1.0.0 Nov 03 05:54:06 ottest3 node[210159]: [2024-11-03 05:54:06] INFO:  Enabling network protocol: /update/1.0.0 Nov 03 05:54:06 ottest3 node[210159]: [2024-11-03 05:54:06] INFO:  Enabling network protocol: /get/1.0.0 Nov 03 05:54:06 ottest3 node[210159]: [2024-11-03 05:54:06] INFO:  Node listening on port: 8900 Nov 03 05:54:06 ottest3 node[210159]: [2024-11-03 05:54:06] INFO:  Routers initialized successfully Nov 03 05:54:06 ottest3 node[210159]: [2024-11-03 05:54:06] INFO:  Network ID is QmWtC2g85qP7UuukZPonZrjS7TpZ8APyibRzAD3eU3hywa, connection port is 9000 Nov 03 05:54:06 ottest3 node[210159]: [2024-11-03 05:54:06] INFO:  Node is up and running! Nov 03 05:54:08 ottest3 node[210159]: [2024-11-03 05:54:08] TRACE: [dialPeersCommand]  Node connected to QmNcjL4P5Dzq5hn6fkncYEsTcRU2g7g4N5rE2KCvHSPDav, updating sharding table last seen and last dialed. Nov 03 05:54:27 ottest3 node[210159]: <--- Last few GCs ---> Nov 03 05:54:27 ottest3 node[210159]: [210159:0x69b5f70]    84435 ms: Scavenge (reduce) 2046.0 (2082.8) -> 2045.4 (2082.8) MB, 7.90 / 0.00 ms  (average mu = 0.304, current mu = 0.262) allocation failure; Nov 03 05:54:27 ottest3 node[210159]: [210159:0x69b5f70]    84502 ms: Scavenge (reduce) 2046.3 (2082.8) -> 2045.7 (2083.0) MB, 6.91 / 0.00 ms  (average mu = 0.304, current mu = 0.262) allocation failure; Nov 03 05:54:27 ottest3 node[210159]: [210159:0x69b5f70]    84571 ms: Scavenge (reduce) 2046.5 (2083.0) -> 2045.9 (2083.3) MB, 6.30 / 0.00 ms  (average mu = 0.304, current mu = 0.262) allocation failure; Nov 03 05:54:27 ottest3 node[210159]: <--- JS stacktrace ---> Nov 03 05:54:27 ottest3 node[210159]: FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed - JavaScript heap out of memory Nov 03 05:54:27 ottest3 node[210159]: ----- Native stack trace ----- Nov 03 05:54:27 ottest3 node[210159]:  1: 0xb8ced1 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [/usr/bin/node] Nov 03 05:54:27 ottest3 node[210159]:  2: 0xf06460 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node] Nov 03 05:54:27 ottest3 node[210159]:  3: 0xf06747 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [/usr/bin/node] Nov 03 05:54:27 ottest3 node[210159]:  4: 0x11182e5  [/usr/bin/node] Nov 03 05:54:27 ottest3 node[210159]:  5: 0x1118874 v8::internal::Heap::RecomputeLimits(v8::internal::GarbageCollector) [/usr/bin/node] Nov 03 05:54:27 ottest3 node[210159]:  6: 0x112f764 v8::internal::Heap::PerformGarbageCollection(v8::internal::GarbageCollector, v8::internal::GarbageCollectionReason, char const*) [/usr/bin/node] Nov 03 05:54:27 ottest3 node[210159]:  7: 0x112ff7c v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [/usr/bin/node] Nov 03 05:54:27 ottest3 node[210159]:  8: 0x11320da v8::internal::Heap::HandleGCRequest() [/usr/bin/node] Nov 03 05:54:27 ottest3 node[210159]:  9: 0x109d747 v8::internal::StackGuard::HandleInterrupts() [/usr/bin/node] Nov 03 05:54:27 ottest3 node[210159]: 10: 0x1540042 v8::internal::Runtime_StackGuardWithGap(int, unsigned long*, v8::internal::Isolate*) [/usr/bin/node] Nov 03 05:54:27 ottest3 node[210159]: 11: 0x7fe71e699ef6 Nov 03 05:54:27 ottest3 systemd[1]: otnode.service: Main process exited, code=dumped, status=6/ABRT Nov 03 05:54:27 ottest3 systemd[1]: otnode.service: Failed with result 'core-dump'. Nov 03 05:54:27 ottest3 systemd[1]: otnode.service: Consumed 58.114s CPU time. Nov 03 05:54:28 ottest3 systemd[1]: otnode.service: Scheduled restart job, restart counter is at 528. Nov 03 05:54:28 ottest3 systemd[1]: Stopped OriginTrail V8 Node. Nov 03 05:54:28 ottest3 systemd[1]: otnode.service: Consumed 58.114s CPU time.
Disclaimer
Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to<EMAIL_ADDRESS>

I have the same issue on my main node. I have given ot-node up to 4-5 gb of ram to work with, rather than the default 2gb.
<--- Last few GCs --->
[1327991:0x59233a0]    68273 ms: Mark-Compact (reduce) 2046.6 (2083.9) -> 2045.9 (2084.2) MB, 1548.60 / 0.00 ms  (avera>
[1327991:0x59233a0]    69680 ms: Mark-Compact (reduce) 2046.9 (2084.2) -> 2046.2 (2084.7) MB, 1402.67 / 0.00 ms  (avera>
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
----- Native stack trace -----
 1: 0xb8ced1 node::OOMErrorHandler(char const*, v8::OOMDetails const&) [node]
 2: 0xf06460 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [node]
 3: 0xf06747 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, v8::OOMDetails const&) [nod>
 4: 0x11182e5  [node]
 5: 0x1130168 v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, >
 6: 0x1106281 v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::int>
 7: 0x1107415 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::in>
 8: 0x10e4a66 v8::internal::Factory::NewFillerObject(int, v8::internal::AllocationAlignment, v8::internal::AllocationTy>
 9: 0x1540896 v8::internal::Runtime_AllocateInYoungGeneration(int, unsigned long*, v8::internal::Isolate*) [node]
10: 0x7210b28d9ef6
otnode.service: Main process exited, code=dumped, status=6/ABRT
otnode.service: Failed with result 'core-dump'.
otnode.service: Consumed 2min 6.141s CPU time.
otnode.service: Scheduled restart job, restart counter is at 1566.
Started otnode.service - OriginTrail V6 Node.

Mine has 8GB and still does this

starting beta.3 i don't see it anymore if I allocate 4GB, it does not work well with lower values
@haroldboom try to reduce number of paranets you are syncing

starting beta.3 i don't see it anymore if I allocate 4GB, it does not work well with lower values
@haroldboom try to reduce number of paranets you are syncing

I have allocated 5GB to the node struggling with this.

starting beta.3 i don't see it anymore if I allocate 4GB, it does not work well with lower values
@haroldboom try to reduce number of paranets you are syncing

I see it with 5GB across my nodes. 8 paranets


Not blocking suggested posts

When Facebook first opens the add-on works, and as I scroll through the first few posts I can see it blocking posts from the feed. However, after Facebook loads the second batch of posts it stops blocking unwanted content. Also, if I have the "Hide all Blocks" setting turned off the elements that are blocked are not reduced in size like they were previously, so I still have to scroll through them.

Hey,
If you see that again, please could you inspect element on the Follow link and send it's html here?
I have not seen it yet from my side, so it's new, and will have to add it.

Hey,
If you see that again, please could you inspect element on the Follow link and send it's html here?
I have not seen it yet from my side, so it's new, and will have to add it.

Yup!
Here is the HTML for the follow button:
Follow
And here is the HTML on a join button that shows on similar posts:
Join

Next version will have a match on >Follow< and >Join<  and that should sort this out - thanks!


Remove tabbed content from GitHub README file.

Fix #506

:tada: This PR is included in version 2.0.0 :tada:
The release is available on:

2.0.0
GitHub release

Your semantic-release bot :package::rocket:


Layout issue on add new item with compactType:null

Something wrong with y: Infinity in non-compact mode. All new items float and stack at the top of layout.
This issue sandbox: https://codesandbox.io/s/zen-carson-mkvz2

Having same Issue when compactType is null.


Makefile: Move kind targets to dedicated Makefile.kind

Makefile: Move kind targets to a separate Makefile.kind
Makefile.kind: Add missing .PHONY targets

/test


pull request for e2e test at 12/17/2016 00:15:19

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


console and keyboard layout

when using the vfkit console (started on my case by podman machine start --log-level DEBUG) the keyboard is using english keyboard layout (but keyboard is using for example a french layout)
when using qemu console started by podman machine start as well, it was able to find/use my local keyboard layout
I would expect to have vfkit behaving the same way
vfkit console if I enter azerty on a french keyboard, it displays qwerty

qemu console, it displays azerty as expected

The vfkit console used by podman is displaying the VM graphical framebuffer, and this behaves as if your keyboard was physically plugged into the VM. This means it honors the keyboard settings configured in the guest, which will be QWERTY by default.
I don't know what the qemu console is, but I'd guess this is using -display curses, the keyboard mapping would be done using the host configuration, and thus would be right in your case.
Once https://github.com/crc-org/vfkit/issues/48 is implemented and podman-desktop supports it, this should give you the behaviour you want.
There is not much vfkit can do for the --gui keyboard behaviour.


feat(web): implement multiple users per workspace

Invite users by email
We do not validate emails for password logins
Hard reload page if workspace changes to avoid reactivity issues

bors merge


Fixes ENYO-1140

Issue
Path to less script is fixed relative to an assumed location of enyo
Fix
Determine path to LESS based on src of LESS loader script tag
Enyo-DCO-1.1-Signed-off-by: Ryan Duffy<EMAIL_ADDRESS>

Closing out as jira associated with this PR has been closed.


Fix the problem that output labels of switch node sometimes disappear

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)

Proposed changes
#1663
As a switch node named the element of output port labels with mixing number and alphabet, I changed it to use only numbers.
Checklist

[x] I have read the contribution guidelines
[ ] For non-bugfix PRs, I have discussed this change on the mailing list/slack team.
[x] I have run grunt to verify the unit tests pass
[ ] I have added suitable unit tests to cover the new/changed functionality

Coverage remained the same at 87.755% when pulling 0822bf5eb3ef535e6b107200b4b8f488cfe8e5fa on node-red-hitachi:switch-labels-disappear into 3b12076d4bc8f42c3f824ef0be466649f1b4de39 on node-red:master.


ENH: Allow advanced users to build only necessary applications.

Exposing all applications in CMake would be too much considering that there are more
than 80 applications built as part of ANTS. This commit introduces advanced options
that are not visible in CMake's user interface, that allow to pick only the
tools that ones wants to build when BUILD_ALL_ANTS_APPS is set to OFF.
If one wants to build 'StackSlices', they need to pass an extra variable called
ANTS_BUILD_StackSlices to CMake and set it to ON.
e.g: cmake -DANTS_SUPERBUILD:BOOL=OFF -DBUILD_ALL_ANTS_APPS:BOOL=OFF
-DANTS_BUILD_StackSlices=ON ../ANTs
More generally, one needs to use the variable 'ANTS_BUILD_${ANTS_APP}' to build
${ANTS_APP}.

what is status of this?  read to commit?   will it affect ANTsR compilation?

The default behavior stays the same, so it should not create any problem in tools depending from ANTs that do not explicitly use the new options.

thanks - will try it out


String Comparison Kernels Non-Monotonic Offset Panic

Describe the bug
The string comparison kernels panic if they encounter non-monotonic offsets, even if the values for which they are encountered are null. Currently ArrayDataBuilder's validation catches such arrays, however, I think this is actually a bug (#1071) as I don't think the arrow specification forbids nulls from having arbitrary offsets. I encountered this whilst working on a parquet StringArray decoder where I was hoping to leave the offsets for null values default zero-initialized and save some cycles.
To Reproduce
// Test handling of nulls with arbitrary offsets
let offsets = vec![2, 0, 2, 2];
let validity = vec![false, true, false];
let values = "ab";

let mut offsets_buffer = MutableBuffer::new(offsets.len() * 4);
offsets_buffer.extend_from_slice(&offsets);

let validity_buffer = MutableBuffer::from_iter(validity.iter().cloned());

let mut values_buffer = MutableBuffer::new(values.len());
values_buffer.extend_from_slice(values.as_bytes());

let builder = ArrayDataBuilder::new(DataType::Utf8)
    .len(validity.len())
    .add_buffer(offsets_buffer.into())
    .add_buffer(values_buffer.into())
    .null_bit_buffer(validity_buffer.into());

// Validation prevents non-monotonic offsets (#1071)
let data = unsafe { builder.build_unchecked() };

let string = StringArray::from(data);
let eq = eq_utf8(&string, &string).unwrap();
assert!(min_boolean(&eq).unwrap())

Expected behavior
I would expect the above to pass, all non-null values have valid offsets. Instead it panics with
called `Option::unwrap()` on a `None` value
thread 'compute::kernels::comparison::tests::test_utf8_array_nulls' panicked at 'called `Option::unwrap()` on a `None` value', arrow/src/array/array_string.rs:101:40
stack backtrace:
   0: rust_begin_unwind
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/std/src/panicking.rs:517:5
   1: core::panicking::panic_fmt
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/panicking.rs:100:14
   2: core::panicking::panic
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/panicking.rs:50:5
   3: core::option::Option<T>::unwrap
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/option.rs:746:21
   4: arrow::array::array_string::GenericStringArray<OffsetSize>::value_unchecked
             at ./src/array/array_string.rs:101:13
   5: arrow::compute::kernels::comparison::eq_utf8::{{closure}}
             at ./src/compute/kernels/comparison.rs:56:35
   6: core::ops::function::impls::<impl core::ops::function::FnOnce<A> for &mut F>::call_once
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/ops/function.rs:280:13
   7: core::option::Option<T>::map
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/option.rs:848:29
   8: <core::iter::adapters::map::Map<I,F> as core::iter::traits::iterator::Iterator>::next
             at /rustc/f1edd0429582dd29cccacaf50fd134b05593bd9c/library/core/src/iter/adapters/map.rs:103:9
   9: arrow::buffer::mutable::MutableBuffer::from_trusted_len_iter_bool
             at ./src/buffer/mutable.rs:489:38
  10: arrow::compute::kernels::comparison::eq_utf8
             at ./src/compute/kernels/comparison.rs:685:5
  11: arrow::compute::kernels::comparison::tests::test_utf8_array_nulls
             at ./src/compute/kernels/comparison.rs:2305:18
  12: arrow::compute::kernels::comparison::tests::test_utf8_array_nulls::{{closure}}

I don't think we necessarily want to support non monotonic offsets -- but the string comparison kernel shouldn't be checking the values of array slots that are not valid (aka are null)

The consensus on #1071 is that offsets should be monotonically increasing, so closing this


oil: 0.1.0 -> 0.3.0

Motivation for this change
https://www.oilshell.org/blog/2017/12/22.html
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

cc @lheckemann


Trigger is broken or different in current version of logic apps

Hello! I am unable to find the trigger mentioned in this article with all the nice additional options for recurrence. It does not have the "Show advanced options" drop-down. Please help!

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

ID: a3a74141-d842-b9fe-2b09-a355c32aa4df
Version Independent ID: 5b3c4677-37ab-cc7b-c7e1-5dacee7a5cea
Content: Build schedule-based automated workflows - Azure Logic Apps
Content Source: articles/logic-apps/tutorial-build-schedule-recurring-logic-app-workflow.md
Service: logic-apps
GitHub Login: @ecfan
Microsoft Alias: estfan

Hi @KonTheCat  Thanks for your feedback. We will review and update as appropriate.

@KonTheCat Couple of month back , parameters UI have been changed and we added the support for adding additional parameters through the dropdown "Add new parameter"and the UI no longer have the link to toggle the ‘Show advanced option’.

Hello! It seems to me that the functionality is different, the add new parameter options do not replace the functionality that the article shows. Is there a reference for accomplishing the same functionality with functions or some other approach?

@KonTheCat  You can achieve this functionality with timer triggers in Azure Functions.  For this the attribute's constructor takes a CRON `expression.
'[FunctionName("TimerTriggerCSharp")]
public static void Run([TimerTrigger("0 */5 * * * *")]TimerInfo myTimer, ILogger log)
{
if (myTimer.IsPastDue)
{
log.LogInformation("Timer is running late!");
}
log.LogInformation($"C# Timer trigger function executed at: {DateTime.Now}");
}'
For more information, you can follow the doc https://docs.microsoft.com/en-us/azure/azure-functions/functions-create-scheduled-function

Ok, so I would need an Azure Function, and then that would start the Logic App? Or can I add this function to Logic Apps directly?
I created the below UserVoice for reference, and for anyone who agrees that the previous functionality should just be brought back.
https://feedback.azure.com/forums/287593-logic-apps/suggestions/38567398-restore-logic-app-scheduling-flexibility

@KonTheCat: Hi Konstantin, thanks for raising the UX issue in this topic. The content is updated to show the current UX.


ChoreRemove the Committer-related description in the contribution guide

Only PMC members can subscribe to the mailing list, including this in the contributor guide would create ambiguity and unnecessary subscriptions.
Gitbox is also limited to Committer members.
We'd better create new Committer/PMC wizard docs if we can, but anyway, the description here is always inappropriate.

run buildall


separate example from udibo base code

This will make easy to clone, run and understand

There are 3 examples in different repositories that can easily be forked. They are linked to in the README.md. One is a very basic example, another shows how you can use tailwindcss v3 in your project and another shows how you can use react query. Are you looking for anything other types of examples?
https://github.com/udibo/react_app#examples
The one example in this repository's example folder is mainly there for manually testing that various features for this framework are working correctly while developing it. It can also be used as a reference.
I plan on adding more detailed documentation to udibo.com. But until then, all there is available is the README.md and examples. If anything is unclear or not documented well, I can try updating them to be better.
https://github.com/udibo/react_app/issues/13


🐛 [cloud_firestore] Vague exception report - PlatformException(firebase_firestore, length=11; index=11, {}, null)

Bug report
Describe the bug
I have a hundreds of occurrences of the following error in our sentry.io:
PlatformException: PlatformException(firebase_firestore, length=11; index=11, {}, null)
  File "message_codecs.dart", line 582, in StandardMethodCodec.decodeEnvelope
  File "platform_channel.dart", line 159, in MethodChannel._invokeMethod
  File "<asynchronous suspension>"
  File "method_channel_query.dart", line 139, in MethodChannelQuery.snapshots.<fn>
  File "<asynchronous suspension>"
  File "unparsed"

Also this one:
PlatformException(firebase_firestore, length=95; index=95, {}, null)
From VSCode:
I/flutter (26225): Caught error: PlatformException(firebase_firestore, src.length=95 srcPos=92 dst.length=95 dstPos=93 length=-37, {}, null)
I/flutter (26225): #0      StandardMethodCodec.decodeEnvelope
package:flutter/…/services/message_codecs.dart:582
I/flutter (26225): #1      MethodChannel._invokeMethod
package:flutter/…/services/platform_channel.dart:159
I/flutter (26225): <asynchronous suspension>
I/flutter (26225): #2      MethodChannel.invokeMethod
package:flutter/…/services/platform_channel.dart:332
I/flutter (26225): #3      MethodChannelDocumentReference.snapshots.<anonymous closure>
package:cloud_firestore_platform_interface/…/method_channel/method_channel_document_reference.dart:110
I/flutter (26225): #4      _runGuarded (dart:async/stream_controller.dart:847:24)
I/flutter (26225): #5      _BroadcastStreamController._subscribe (dart:async/broadcast_stream_controller.dart:213:7)
I/flutter (26225): #6      _ControllerStream._createSubscription (dart:async/stream_controller.dart:860:19)
I/flutter (26225): #7      _StreamImpl.listen (dart:async/stream_impl.dart:493:9)
I/flutter (26225): #8      new _ForwardingStreamSubscription (dart:async/stream_pipe.dart:118:10)
I/flutter (26225): #9      _ForwardingStream._createSubscription (dart:async/stream_pipe.dart:88:16)
I/flutter (26225): #10     _ForwardingStream.listen (dart:async/stream_p <cuts off>

I have no idea what it means as the error description is vague.
It only comes from Android devices.
I'm not sure this causes any problems, as we've had no stability complaints.
EDIT
I have run into this one personally, see the reproduction section
Steps to reproduce
Steps to reproduce the behavior:
It's periodic and very rare but I've hit it once myself running the following code:
Stream<MyUser> read() {
    return _auth.authStateChanges().switchMap((myUser) {
      if (myUser != null) {
        return _fs.doc('users/${myUser.uid}').snapshots().map((userSnapshot) {
          if (userSnapshot.exists) return MyUser.fromSnapshot(userSnapshot);

          return null;
        });
      }

      return Stream.value(null);
    }).handleError((_) => null); // Handles logout events
  }

  /// Returns a list of the businesses the logged in user has access to.
  Stream<BuiltList<Business>> listMyBusinesses() {
    return _myUserRepo.read().switchMap((user) {
      if (user?.businesses?.isEmpty ?? true) return Stream.value(BuiltList<Business>([]));

      final businesses = <Stream<Business>>[];
      for (final busId in user.businesses.keys) {
        businesses.add(_busRepo.read(busId));
      }

      return Rx.combineLatest(
          businesses,
          (List<Business> list) =>
              BuiltList<Business>(list.where((business) => !business.deleted).toList()..sort((a, b) => a.name.compareTo(b.name))));
    });
  }

  listMyBusinesses().listen((_) {});

Whats suspicious about the above code is that it adds a lot of listeners rapidly.
So maybe that hits a race condition in an internal list of subscriptions internally in the cloud_firestore plugin (which could make sense since the error hints at "indexes"). I'm just speculating.
Expected behavior

Additional context

Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[✓] Flutter (Channel stable, 1.22.3, on Mac OS X 10.13.6 17G14033, locale en-DK)
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
[!] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
        sudo xcodebuild -runFirstLaunch
[✓] Android Studio (version 4.0)
[✓] VS Code (version 1.51.0)
[✓] Connected device (2 available)

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 2.10.3
Flutter SDK 1.22.3
tillty 5.16.7+51607

dependencies:
- animated_text_kit 2.5.4 [flutter characters]
- audioplayers 0.16.2 [uuid path_provider flutter flutter_web_plugins]
- bloc 6.1.0 [meta]
- built_collection 4.3.2 [collection quiver]
- built_value 7.1.0 [built_collection collection fixnum quiver]
- cached_network_image 2.3.3 [flutter flutter_cache_manager octo_image]
- charts_flutter 0.9.0 [charts_common collection flutter intl logging meta]
- cloud_firestore 0.14.3 [flutter meta quiver firebase_core firebase_core_platform_interface cloud_firestore_platform_interface cloud_firestore_web]
- country_code_picker 1.6.2 [flutter modal_bottom_sheet]
- country_pickers 1.3.0 [flutter]
- crypto 2.1.5 [collection convert typed_data]
- cupertino_icons 1.0.0
- dart_date 1.0.7 [intl timeago]
- data_connection_checker 0.3.4
- device_info 1.0.0 [flutter device_info_platform_interface]
- drag_and_drop_gridview 1.0.8 [flutter]
- firebase_auth 0.18.3 [meta firebase_core firebase_core_platform_interface firebase_auth_platform_interface firebase_auth_web flutter]
- firebase_core 0.5.2 [firebase_core_platform_interface flutter quiver meta firebase_core_web]
- firebase_crashlytics 0.2.3 [flutter stack_trace firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface]
- firebase_dynamic_links 0.6.2 [flutter firebase_core]
- firebase_storage 4.0.1 [flutter firebase_core]
- flutter 0.0.0 [characters collection meta typed_data vector_math sky_engine]
- flutter_bloc 6.1.0 [flutter bloc provider]
- flutter_dotenv 2.1.0 [flutter meta]
- flutter_localizations 0.0.0 [flutter intl characters collection meta path typed_data vector_math]
- flutter_material_color_picker 1.0.5 [flutter]
- flutter_nfc_acs 0.1.6 [flutter flutter_plugin_android_lifecycle]
- flutter_slidable 0.5.7 [flutter]
- flutter_vibrate 1.0.0 [flutter]
- http 0.12.2 [http_parser path pedantic]
- image 2.1.18 [archive xml meta]
- image_picker 0.6.7+12 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- intl 0.16.1 [path]
- nfc_in_flutter 2.0.5 [flutter]
- package_info 0.4.3+2 [flutter]
- phone_number 0.8.1 [meta flutter]
- positioned_tap_detector 1.0.3 [flutter]
- provider 4.3.2+2 [flutter nested collection]
- qr_flutter 3.2.0 [flutter qr]
- random_string 2.1.0
- reorderables 0.3.2 [flutter]
- rxdart 0.24.1
- sentry 3.0.1 [http meta stack_trace usage pedantic]
- shared_preferences 0.5.12+4 [meta flutter shared_preferences_platform_interface shared_preferences_linux shared_preferences_macos shared_preferences_web shared_preferences_windows]
- sprintf 5.0.0
- strings 0.1.4 [characters unicode]
- time 1.3.0
- url_launcher 5.7.10 [flutter url_launcher_platform_interface url_launcher_web url_launcher_linux url_launcher_macos url_launcher_windows]
- uuid 2.2.2 [crypto convert]
- validators 2.0.1 [vin_decoder]

dev dependencies:
- build_runner 1.10.4 [args async build build_config build_daemon build_resolvers build_runner_core code_builder collection crypto dart_style glob graphs http_multi_server io js logging meta mime path pedantic pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- built_value_generator 7.1.0 [analyzer build build_config built_collection built_value source_gen quiver]
- intl_translation 0.17.10+1 [analyzer args dart_style intl path petitparser]

dependency overrides:
- analyzer 0.40.6 [_fe_analyzer_shared args cli_util collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]

transitive dependencies:
- _fe_analyzer_shared 12.0.0 [meta]
- archive 2.0.13 [crypto args path]
- args 1.6.0
- async 2.4.2 [collection]
- basic_utils 2.7.0-rc.1 [http logging json_annotation pointycastle convert crypto]
- build 1.5.0 [analyzer async convert crypto logging meta path glob]
- build_config 0.4.2 [checked_yaml json_annotation meta path pubspec_parse yaml]
- build_daemon 2.1.4 [built_collection built_value http_multi_server logging pedantic path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 1.4.3 [analyzer build crypto graphs logging meta path package_config pool pub_semver]
- build_runner_core 6.0.3 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta path package_config pedantic pool timing watcher yaml]
- characters 1.1.0-nullsafety.3
- charcode 1.1.3
- charts_common 0.9.0 [collection intl logging meta vector_math]
- checked_yaml 1.0.2 [json_annotation source_span yaml]
- cli_util 0.2.0 [path]
- clock 1.0.1 [meta]
- cloud_firestore_platform_interface 2.2.0 [flutter meta collection firebase_core plugin_platform_interface]
- cloud_firestore_web 0.2.1 [flutter flutter_web_plugins http_parser meta firebase_core firebase_core_web cloud_firestore_platform_interface js]
- code_builder 3.5.0 [built_collection built_value collection matcher meta]
- collection 1.15.0-nullsafety.3
- convert 2.1.1 [charcode typed_data]
- dart_style 1.3.9 [analyzer args path source_span]
- device_info_platform_interface 1.0.1 [flutter meta plugin_platform_interface]
- ffi 0.1.3
- file 5.2.1 [intl meta path]
- firebase_auth_platform_interface 2.1.3 [flutter meta firebase_core plugin_platform_interface]
- firebase_auth_web 0.3.2 [flutter flutter_web_plugins meta http_parser intl firebase_core firebase_core_web firebase_auth_platform_interface js]
- firebase_core_platform_interface 2.0.0 [flutter meta plugin_platform_interface quiver]
- firebase_core_web 0.2.1 [firebase_core_platform_interface flutter flutter_web_plugins meta js]
- firebase_crashlytics_platform_interface 1.1.3 [flutter meta collection firebase_core plugin_platform_interface]
- fixnum 0.10.11
- flutter_blurhash 0.5.0 [flutter meta]
- flutter_cache_manager 2.0.0 [flutter path_provider uuid http path sqflite pedantic clock file rxdart]
- flutter_plugin_android_lifecycle 1.0.11 [flutter]
- flutter_web_plugins 0.0.0 [flutter characters collection meta typed_data vector_math]
- glob 1.2.0 [async collection node_io path pedantic string_scanner]
- graphs 0.2.0
- http_multi_server 2.2.0 [async]
- http_parser 3.1.4 [charcode collection source_span string_scanner typed_data]
- image_picker_platform_interface 1.1.1 [flutter meta http plugin_platform_interface]
- io 0.3.4 [charcode meta path string_scanner]
- js 0.6.2
- json_annotation 3.1.0
- lists 0.1.6
- logging 0.11.4
- matcher 0.12.9 [stack_trace]
- meta 1.3.0-nullsafety.3
- mime 0.9.7
- modal_bottom_sheet 1.0.1-dev [flutter]
- nested 0.0.4 [flutter]
- node_interop 1.2.0 [js]
- node_io 1.1.1 [node_interop path]
- octo_image 0.3.0 [flutter flutter_blurhash]
- package_config 1.9.3 [path charcode]
- path 1.8.0-nullsafety.1
- path_provider 1.6.24 [flutter path_provider_platform_interface path_provider_macos path_provider_linux path_provider_windows]
- path_provider_linux 0.0.1+2 [path xdg_directories path_provider_platform_interface flutter]
- path_provider_macos 0.0.4+6 [flutter]
- path_provider_platform_interface 1.0.4 [flutter meta platform plugin_platform_interface]
- path_provider_windows 0.0.4+3 [path_provider_platform_interface meta path flutter ffi win32]
- pedantic 1.9.2 [meta]
- petitparser 3.1.0 [meta]
- platform 2.2.1
- plugin_platform_interface 1.0.3 [meta]
- pointycastle 2.0.0
- pool 1.4.0 [async stack_trace]
- process 3.0.13 [file intl meta path platform]
- pub_semver 1.4.4 [collection]
- pubspec_parse 0.1.5 [checked_yaml json_annotation pub_semver yaml]
- qr 1.3.0 [meta]
- quiver 2.1.5 [matcher meta]
- shared_preferences_linux 0.0.2+4 [file flutter meta path path_provider_linux shared_preferences_platform_interface]
- shared_preferences_macos 0.0.1+11 [shared_preferences_platform_interface flutter]
- shared_preferences_platform_interface 1.0.4 [meta flutter]
- shared_preferences_web 0.1.2+7 [shared_preferences_platform_interface flutter flutter_web_plugins meta]
- shared_preferences_windows 0.0.1+3 [shared_preferences_platform_interface flutter ffi file meta path path_provider_platform_interface path_provider_windows]
- shelf 0.7.9 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 0.2.3 [shelf web_socket_channel stream_channel]
- sky_engine 0.0.99
- source_gen 0.9.8 [analyzer async build dart_style glob meta path pedantic source_span]
- source_span 1.7.0 [charcode collection meta path term_glyph]
- sqflite 1.3.2+1 [flutter sqflite_common path]
- sqflite_common 1.0.2+1 [synchronized path meta]
- stack_trace 1.9.6 [path]
- stream_channel 2.0.0 [async]
- stream_transform 1.2.0
- string_scanner 1.0.5 [charcode meta source_span]
- synchronized 2.2.0+2
- term_glyph 1.1.0
- timeago 2.0.28
- timing 0.1.1+2 [json_annotation]
- typed_data 1.3.0-nullsafety.3 [collection]
- unicode 0.2.4 [lists]
- url_launcher_linux 0.0.1+4 [flutter]
- url_launcher_macos 0.0.1+9 [flutter]
- url_launcher_platform_interface 1.0.9 [flutter meta plugin_platform_interface]
- url_launcher_web 0.1.5+1 [url_launcher_platform_interface flutter flutter_web_plugins meta]
- url_launcher_windows 0.0.1+3 [flutter]
- usage 3.4.2 [path]
- vector_math 2.1.0-nullsafety.3
- vin_decoder 0.1.2 [meta basic_utils http random_string]
- watcher 0.9.7+15 [async path pedantic]
- web_socket_channel 1.1.0 [async crypto stream_channel]
- win32 1.7.3 [ffi]
- xdg_directories 0.1.2 [meta path process]
- xml 4.5.1 [collection convert meta petitparser]
- yaml 2.2.1 [charcode collection string_scanner source_span]

I am just seeing the same error, with same lack of context and with a very uncommunicative Crashlytics log.
Non-fatal Exception: io.flutter.plugins.firebase.crashlytics.FlutterError
PlatformException(firebase_firestore, length=11; index=11, {})
StandardMethodCodec.decodeEnvelope (message_codecs.dart:572)
MethodChannel._invokeMethod (platform_channel.dart:161)
MethodChannelDocumentReference.<fn> (method_channel_document_reference.dart:94)
.suspension> (<asynchronous)

Same here.
E/flutter (24950): [ERROR:flutter/lib/ui/ui_dart_state.cc(177)] Unhandled Exception: PlatformException(firebase_core, java.util.concurrent.ExecutionException: java.lang.ArrayIndexOutOfBoundsException: length=11; index=11, null, null)
E/flutter (24950): #0      StandardMethodCodec.decodeEnvelope
package:flutter/…/services/message_codecs.dart:582
E/flutter (24950): #1      MethodChannel._invokeMethod
package:flutter/…/services/platform_channel.dart:159
E/flutter (24950):
E/flutter (24950): #2      MethodChannel.invokeMethod
package:flutter/…/services/platform_channel.dart:332
E/flutter (24950): #3      MethodChannel.invokeListMethod
package:flutter/…/services/platform_channel.dart:345
E/flutter (24950): #4      MethodChannelFirebase._initializeCore
package:firebase_core_platform_interface/…/method_channel/method_channel_firebase.dart:30
E/flutter (24950): #5      MethodChannelFirebase.initializeApp
package:firebase_core_platform_interface/…/method_channel/method_channel_firebase.dart:75
E/flutter (24950): #6      Firebase.initializeApp

We've seen the same error a few times with firebase_storage: ^5.0.1 on ios.

me too with one only user... 375 events on Android 10

me too with one only user... 375 events on Android 10

I'm having the same issue. Although when I build and run a release version, it acts normally. But, in the debug mode I get this error unlimited times and after a while, it shows Platform exception.

Hey @larssn,  we updated the way we handle snapshot event listeners back in January which may have fixed your problem. Can you confirm if you're still seeing the same issue crop up?

I think it did! Can't find it in our error logging service anymore.


WRKLDS-705: Bump openshift/api to enable DynamicResourceAllocation through TechPreviewNoUpgrade

Part of making https://kubernetes.io/docs/concepts/scheduling-eviction/dynamic-resource-allocation available for early adoption.

/retest-required

/retest-required

/lgtm
/approve


Where does uv land on PEP 517 backend-path out-of-tree?

👋 Ok, you caught me doing some weird things...
In a Python monorepo, with your own PEP 517/660 build backend, it's really convenient to define your build-backend as:
[build-system]
requires = []
build-backend = "super_cool_custom_thing"
backend-path = [".."]

Unfortunately pip gets really angry when you do this.
But uv doesn't! 🎉
So, I'm wondering if this is on purpose or on accident.

FWIW According to PEP 517:

Directories in backend-path are interpreted as relative to the project root, and MUST refer to a location within the source tree (after relative paths and symbolic links have been resolved).

So I'm defintely violating it. But also:

Frontends SHOULD check this condition

So you aren't required by spec to error here. Hows about we slip uv a fiver to keep looking the other way? 😛
(Or if you are planning on erroring, maybe allowing an opt-out flag? UV_IM_VIOLATING_PEP_517_BACKEND_PATH_AND_I_HAVE_NO_SHAME=1?)

Reasons doing this is actually a good idea ™ :

You don't need to have your own cheeseshop for your build backend
Alternatively, you don't bring in all the issues with --no-build-backend on your 1p packages (e.g. you have to install your build backend first, and you can't install deps at the same time as your packages because you might not have installed your dependencies' build backends)
You can feel safe knowing everyone is using your build backend (including the right version)

(I have opened a discussion related to this on Discourse, but more generally)

I'm ok not to enforce this.

If you're willing to write down what led you to this decision, for posterity, be my guest 😁

Mostly just that it costs us nothing and users are using it so it'd be breaking for us to remove :)

I'll take it! If you give me a pointer, I'll file myself a task to add a test here to avoid backsliding.


Upgrade io.netty:netty-codec-http

Patches sec vuln.

@ALRubinger we pull this dependency in through io.grpc:grpc-core, which it appears we're already on the latest version of. we could depend explicitly on a later version of io.netty:netty-codec-http but it seems like diverging these dependencies introduces other risks - do you have a perspective/preference here?

@worstell Yep typically in these instances I'll force an upgrade of the transitive dependency and run it through the testsuite. If ✅, I assume all is good - but of course this depends on a testsuite w/ sufficient coverage.

Note that in this instance I'd expect the risk of upgrade to be small; it's a patch update which shouldn't remove any deprecated API calls and it should be designed to be forward-compatible. Testsuites at runtime are the only way to know for sure :)

Can you link to the CVE for this?

This seems like it might be relevant issue, and the maintainers state that gRPC is not impacted.

Can you link to the CVE for this?

https://nvd.nist.gov/vuln/detail/CVE-2024-29025

Ah different to the one above.

Yup and I follow where you're going with this - determining if you're using any vulnerable code paths. My recommendation is to try the upgrade regardless, because any consumers of FTL are going to have their vuln scanners light up even if we legitimately "ignore" this for us. Ideally io.grpc:grpc-core would address this (you can even file an issue with them requesting it!) so that us and every other downstream consumer of it gets this fixed at the root where it was introduced.

Ha, Sonatype does threat scanning too and sent this report:

So ideally our fixing it up or getting the root to do it helps. We can ignore in FOSSA but it'd still flag in Sonatype :)

No longer relevant after the JVM rewrite.


Add IESTP - Argentina

Official website of the institute: http://www.istpargentina.edu.pe/
Official Facebook: https://www.facebook.com/instituto.argentina

@leonelhv First stage of verification passed, official domain is istpargentina.edu.pe as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@leonelhv Please provide us with

the school street address, including city and country
an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course

Thank you!

@philipto Thank you for your response. Here is the information you requested:
Address: Av. Alfonso Ugarte Cdra. 9 S/N
City: Lima
Country: Peru
Computing and Information Technology career curriculum (3 years):  http://www.istpargentina.edu.pe/wp-content/uploads/2018/01/Computacion.pdf

@leonelhv Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Question on clustering

I'm having a slightly bizarre issue; and its entirely possible i'm not using Kafka correctly here, i'm using the sarama-cluster consumer to load balance two consumers (same consumer group name, different machines).
I've placed tracking on the metrics of how much each instance is receiving, and almost always I turn up both instances and both will begin receiving data, and our metrics indicate, but after one minute, all of the data will begin being handled by only once instance, no matter the situation, i've let it run for days and stressed the load on it to see if theres a change in behaviour but nothing..
Do you have any recommendations, heres some sample code that illustrates the problem, just change the topic/consumer group name to whatever you'd like (that has data on it) and set KAFKA_HOSTS in your env, if you fire up 2 one will only receive messages, the other will not:
package main

import (
    "strings"
    "log"
    "os"
    "time"
    cluster "github.com/bsm/sarama-cluster"
)

var messagesReceived = 0;

func Start(kafkaAddrs []string) {
    config := cluster.NewConfig()
    config.Net.TLS.Enable = false
    config.ClientID = "logstream"
    config.Consumer.Return.Errors = true

    client, err := cluster.NewClient(kafkaAddrs, config)
    if err != nil {
        log.Fatal(err)
    }

    err_v := config.Validate()
    if err_v != nil {
        log.Fatal(err_v)
    }
    var topics = []string{"alamoweblogs"}
    consumer, err_c := cluster.NewConsumerFromClient(client, "logstream", topics)
    if err_c != nil {
        log.Fatal(err_c)
    }
   defer consumer.Close()
   for {
        select {
            case message := <- consumer.Messages():
                messagesReceived++
		_ = message
        }
   }
}

func main() {
  go Start(strings.Split(os.Getenv("KAFKA_HOSTS"),","))
  t := time.NewTicker( time.Second * 60 )
  for {
            log.Printf("received#count=%d\n", messagesReceived)
            messagesReceived = 0
            <-t.C
  }
}

nevermind, we only had one partition open. duhm-de-duhm...


[✨] Support to RequestEvent from useResource$ hook as an optional parameter.

Is your feature request related to a problem?
Yes, I'm facing a problem where I've two different API URLs for the same API Service, one URL is public-network facing and the other one is local-network facing.
And now when I use the useResource$ hook which runs on both server (within local-network) and client (within public-network) If the hook runs on the server then I need to access the following to do conditional fetch request: req.env.get('API_URL').
SSR Mode: req.env.get('API_URL')
CSR Mode: import.meta.env.PUBLIC_API_URL
But because I can't RequestEvent object in the useResource$ hook I can't do those conditionals API URL choosing based on SSR and CSR mode.
Describe the solution you'd like
I would like to have access to the RequestEvent or RequestEventBase object instance optionally as useResource$'s callback parameter.
Use Case 1:
const user = useResource$((ctx, req) => {
    const apiUrl = req?.env.get('API_URL') || import.meta.env.PUBLIC_API_URL;
    // Notice: I'm using the `?` null coleasing operator. I hope it also works with undefined.
    return fetch(`${apiUrl}/v1/user`).then(res => res.json());
});

Use Case 2:
const token = useResource$((ctx, req) => {
    return req?.cookie.get('token') || jsCookie.get('token');
});

Describe alternatives you've considered
routeLoader might be an option but that is currently inefficient for this kind of task in my opinion.
For example for Use Case 1:
I might get the LOCAL API URL (from req.env.get('API_URL') using routeLoader which is kinda weird because in SPA navigation the routeLoader will called but that value no use in CSR Mode / SPA mode. and also kinda exposes the LOCAL API URL to the public source code.
For example for Use Case 2:
I might get the token (from req.cookie) using routeLoader which is okay, but when navigation is happening in SPA mode with CSR rendering I already have access to document.cookie which is enough for me to have cookie in place for me to use. So in SPA navigation, the routeLoader network call is wasted.
Additional context
No response

Ohh, that is an interesting idea. So we have this in server$ as well.  I think we could do something like this.
const token = useResource$(function(this: nul | RequestEvent, ctx, req) {
    console.log(this ? 'Server': 'Client');
    return req?.cookie.get('token') || jsCookie.get('token');
});

Would you be interested in creating a PR fix for this? See server$ for inspiration as it already has this argument. I would be happy to guide you through it.

Thanks for the hint about server$, I wonder if server$ can be combined with useResource$ to achieve what I wanted.
Use Case 1:
// Top-level function
const getApiUrlSsr = server$(async function() {
  return this.env.get('API_URL');
});

// Component-level hook
const user = useResource$(async ctx => {
    const apiUrl = isServer ? await getApiUrlSsr() : import.meta.env.PUBLIC_API_URL;
    return fetch(`${apiUrl}/v1/user`).then(res => res.json());
});

Use Case 2:
// Top-level function
const getTokenSsr = server$(async function() {
  return this.cookie.get('token');
});

// Component-level hook
const token = useResource$(async ctx => {
    return isServer ? await getTokenSsr() : jsCookie.get('token');
});

Does this work? I'll try soon to test it out.
If this solution works, then I think we don't need to necessarily change the API of useResource$.
And also if the solution works then we need to point it in the documentation to make easier for new users to adapt easily.
Thanks.

Also, I think just passing this: null | RequestEvent doesn't hurt any user-facing API really!
Having this: null | RequestEvent with useResource$ and useTask$ is a great plus without having to complicate simple use cases!
For example, who need access to RequestEvent | null they just need change their arrow function to full function! that just it without much changes!.
What's what your opinion?

Qwik AI is awesome for clarifying simple questions.

I like your idea. I think all tasks functions could have this and it would not break anything.
Let me know if you are up for doing the work. Happy to guide you along.

I would be happy to contribute, but will be able to start next month.
Any guides would be helpful of course.

Wondering one thing, how can we make the import the same, as currently useResource$, useTask$ imports from @builder.io/qwik but when need to integrate some server things that can only be done inside @builder.io/qwik-city

Hmm! That is a good point. Qwik cant depend on qwikcity. Maybe there is a simpler request interface which is not Qwik city specific but only platform specific?

We moved this issue to qwik-evolution repo to create a RFC discussion for this.
Here is our Qwik RFC process thanks.


Update eslint package for typescript

What is the motivation for adding / enhancing this feature?

The current version is only 100% compatible unit version <3.5.0 and with @typescript-eslint/eslint-plugin Version 2.* it is valid until version <3.8 (3.8 is currently in beta). This should be updated to have 100% support from the plugin and a maybe 100% support as they say there could be some cases where there could be problems.
This is the warning that the current typescript eslint plugin throws when you use it on a typescript version that is not officially supported.
=============

WARNING: You are currently running a version of TypeScript which is not officially supported by typescript-estree.

You may find that it works just fine, or you may not.

SUPPORTED TYPESCRIPT VERSIONS: >=3.2.1 <3.5.0

YOUR TYPESCRIPT VERSION: 3.7.5

Please only submit bug reports when using the officially supported version.

=============

What are the acceptance criteria

[ ] Update @typescript-eslint/eslint-plugin and @typescript-eslint/parser to the lastest 2.* version

Can you complete this feature request by yourself?

[ ] YES
[ ] NO

Which Release Cycle state this refers to? Info for developer.
Pick one option.

[x] This is a normal feature request. This should be available on https://test.storefrontcloud.io and then after tests this can be added to next Vue Storefront version. In this case Developer should create branch from develop branch and create Pull Request 2. Feature / Improvement back to develop.
[ ] (Pick this option only if you're sure) This is an important improvement request for current Release Candidate version on https://next.storefrontcloud.io and should be placed in next RC version. In this case Developer should create branch from release branch and create Pull Request 3. Stabilisation fix back to release.
[ ] (Pick this option only if you're sure) This is a critical improvement request for current Stable version on https://demo.storefrontcloud.io and should be placed in next stable version. In this case Developer should create branch from hotfix or master branch and create Pull Request 4. Hotfix back to hotfix.

Additional information

These are the rules that are added/changed which are all errors:

'prefer-const'
'@typescript-eslint/ban-ts-ignore'
'no-var'
'@typescript-eslint/no-empty-function'
'@typescript-eslint/no-this-alias'
'@typescript-eslint/no-inferrable-types'
'prefer-rest-params'

About these there should be some discussion on how to handle it if there should be moved to warning, be disabled or stay the same as the default and just fix them in the code?

@pkarw i can take this - guess related to https://github.com/DivanteLtd/vue-storefront/issues/4126

Cool! Go on @simonmaass

this is an absolute nightmare :) there are so many rules that need decision making... i believe this should be done by core team!


TRACE: Unable to dial peer. Error: connect ECONNREFUSED <IP_ADDRESS>:9000

Issue description
After updating test node to V3.0.0, the node has trouble connecting to peer
TRACE: Unable to dial peer xxxx. Error:
Error: connect ECONNREFUSED <IP_ADDRESS>:9000
Expected behavior
Able to dial peer
Actual behavior
Connection to peer failed with ECONNREFUSED
Steps to reproduce the problem

Let the node auto-update to V3.0.0
Error shows in the log while trying to dial peer

Specifications

Node version: 3.0.0
Platform: Ubuntu 20.04 LTS
Node wallet: "0xf19da42c2fa6070d197c53a95cd5d8999696cabf"
Node libp2p identity: QmTaS2Cv2HASsSREaQDvijVryXDuXjTCLjwMptfyPViCQ8

Contact details

Email<EMAIL_ADDRESS>
Error logs
[2022-11-03 16:36:44] TRACE: Unable to dial peer QmbSEhJtmdAa4QBXUsGb7xh7DBRuM1ms3g4sXAvQ6pTxQ3. Error:
Error: connect ECONNREFUSED <IP_ADDRESS>:9000
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1247:16)
Error: The operation was aborted
at AbortSignal.onAbort (/root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p-tcp/src/index.js:93:14)
at AbortSignal.[nodejs.internal.kHybridDispatch] (node:internal/event_target:694:20)
at AbortSignal.dispatchEvent (node:internal/event_target:636:26)
at abortSignal (node:internal/abort_controller:292:10)
at AbortController.abort (node:internal/abort_controller:323:5)
at AbortSignal.onAbort (/root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p/node_modules/any-signal/index.js:13:16)
at AbortSignal.[nodejs.internal.kHybridDispatch] (node:internal/event_target:694:20)
at AbortSignal.dispatchEvent (node:internal/event_target:636:26)
at abortSignal (node:internal/abort_controller:292:10)
at AbortController.abort (node:internal/abort_controller:323:5)
at AbortSignal.onAbort (/root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p/node_modules/any-signal/index.js:13:16)
at AbortSignal.dispatchEvent (/root/ot-node/6.0.0-beta.3.0.0/node_modules/event-target-shim/dist/event-target-shim.js:818:35)
at abortSignal (/root/ot-node/6.0.0-beta.3.0.0/node_modules/abort-controller/dist/abort-controller.js:52:12)
at AbortController.abort (/root/ot-node/6.0.0-beta.3.0.0/node_modules/abort-controller/dist/abort-controller.js:91:9)
at AbortController.abort (/root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p/node_modules/timeout-abort-controller/index.js:30:18)
at /root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p/node_modules/timeout-abort-controller/index.js:20:38
at Timeout.timerWrapper (/root/ot-node/6.0.0-beta.3.0.0/node_modules/libp2p/node_modules/timeout-abort-controller/node_modules/retimer/retimer.js:21:16)
at listOnTimeout (node:internal/timers:559:17)
at processTimers (node:internal/timers:502:7)
Disclaimer
Please be aware that the issue reported on a public repository allows everyone to see your node logs, node details, and contact details. If you have any sensitive information, feel free to share it by sending an email to<EMAIL_ADDRESS>

UPDATE:
This error persists on mainnet V6.0.1 and happens when I change the port on the config file:
"network": {
"implementation": {
"libp2p-service": {
"config": {
"port": "9001"
}
}
}
}
If I change the port back to default 9000, I get the error described in #2178.

Closing this as it is duplicate of #2178