Please specify whether it is CANFD in the Message

Below is the CANFD dbc generated by CANdb++, with the canfd flag added to the last line
Although custom attributes can be parsed, I need to determine whether it is CANFD. Can the IsExtID field in the Message be changed to an enumeration, or IsCANFD be added?

VERSION ""

NS_ :
	NS_DESC_
	CM_
	BA_DEF_
	BA_
	VAL_
	CAT_DEF_
	CAT_
	FILTER
	BA_DEF_DEF_
	EV_DATA_
	ENVVAR_DATA_
	SGTYPE_
	SGTYPE_VAL_
	BA_DEF_SGTYPE_
	BA_SGTYPE_
	SIG_TYPE_REF_
	VAL_TABLE_
	SIG_GROUP_
	SIG_VALTYPE_
	SIGTYPE_VALTYPE_
	BO_TX_BU_
	BA_DEF_REL_
	BA_REL_
	BA_DEF_DEF_REL_
	BU_SG_REL_
	BU_EV_REL_
	BU_BO_REL_
	SG_MUL_VAL_

BS_:

BU_:

BO_<PHONE_NUMBER> New_Message_1: 8 Vector__XXX
 SG_ New_Signal_2 : 8|8@1- (1,0) [0|0] "" Vector__XXX
 SG_ New_Signal_1 : 0|8@1- (1,0) [0|0] "" Vector__XXX

BA_DEF_  "MultiplexExtEnabled" ENUM  "No","Yes";
BA_DEF_ BO_  "CANFD_BRS" ENUM  "0","1";
BA_DEF_  "DBName" STRING ;
BA_DEF_  "BusType" STRING ;
BA_DEF_ BU_  "NodeLayerModules" STRING ;
BA_DEF_ BU_  "ECU" STRING ;
BA_DEF_ BU_  "CANoeJitterMax" INT 0 0;
BA_DEF_ BU_  "CANoeJitterMin" INT 0 0;
BA_DEF_ BU_  "CANoeDrift" INT 0 0;
BA_DEF_ BU_  "CANoeStartDelay" INT 0 0;
BA_DEF_ BO_  "VFrameFormat" ENUM  "StandardCAN","ExtendedCAN","reserved","reserved","reserved","reserved","reserved","reserved","reserved","reserved","reserved","reserved","reserved","reserved","StandardCAN_FD","ExtendedCAN_FD";
BA_DEF_DEF_  "MultiplexExtEnabled" "No";
BA_DEF_DEF_  "CANFD_BRS" "1";
BA_DEF_DEF_  "DBName" "";
BA_DEF_DEF_  "BusType" "";
BA_DEF_DEF_  "NodeLayerModules" "";
BA_DEF_DEF_  "ECU" "";
BA_DEF_DEF_  "CANoeJitterMax" 0;
BA_DEF_DEF_  "CANoeJitterMin" 0;
BA_DEF_DEF_  "CANoeDrift" 0;
BA_DEF_DEF_  "CANoeStartDelay" 0;
BA_DEF_DEF_  "VFrameFormat" "StandardCAN";
BA_ "BusType" "CAN FD";
BA_ "DBName" "canfd";
BA_ "VFrameFormat" BO_<PHONE_NUMBER> 15;

Hi,
VFrameFormat is not standard stuff, I mean this is quite Vector specific. I am a bit reluctant to add specific properties in the object based on non standard custom properties.
What if the  VFrameFormat definition (BA_DEF_ BO_) and /or value (BA_DEF_DEF_ and BA_ )  is missing? What is default?
Moreover, the list is quite open
ENUM  "StandardCAN","ExtendedCAN","reserved","reserved","reserved","reserved","reserved","reserved","reserved","reserved","reserved","reserved","reserved","reserved","StandardCAN_FD","ExtendedCAN_FD"

What about all those reserved?
We could eventually add an extension method for convenience, something like
public static string VFrameFormat(this Message message)
{
  // Checks for the VFrameFormat property and returns null if no property is found of the value if found
}

I would prefer keeping the string but let's say we go go for an enum then the values should be
public enum VFrameFormat
{
  NotSet = 0,
  Unknown, // Property set but value not recognized
  StandardCAN,
  ExtendedCAN,
  StandardCAN_FD,
  ExtendedCAN_FD
}

A

Adding extension methods is fine.

Hi,
the good thing about extension method is that you can write it yourself in your code extending current functionality, at least until we relese the new version.
public static VFrameFormat FrameFormat(this Message message)
{
    if (message.CustomProperties.TryGetValue("VFrameFormat", out var frameFormat) == false)
        return VFrameFormat.NotSet;

    switch (frameFormat.StringCustomProperty.Value)
    {
        case "StandardCAN":
            return VFrameFormat.StandardCan;
        case "ExtendedCAN" :
            return VFrameFormat.ExtendedCan;
        case "StandardCAN_FD" :
            return VFrameFormat.StandardCanFd;
        case "ExtendedCAN_FD":
            return VFrameFormat.ExtendedCanFd;
        default:
            return VFrameFormat.Unknown;
    }
}

public enum VFrameFormat
{
    NotSet = 0,
    Unknown, // Property set but value not recognized
    StandardCan,
    ExtendedCan,
    StandardCanFd,
    ExtendedCanFd
}

Cheers
A

That's awesome, thanks!


One more credential error.

I am getting an error while uploading the image "Missing credentials in config".
May you please explain that step:
Paste the contents into a file named ~/.bluemix/cos_credentials.
First of all I do not have that file, so I create it.
Is it .txt .js ?
What should I put in it, node.js string like
{
"api-key":"XXXX",
....}
I just copied credentials and put it and got a mistake I mentioned before.

Hello again @r4sk01 - please reopen this issue if you are still having problems...

Hi @loafyloaf , sorry for a late reply. It took some time to test it, I confirm it works now. I did not really change anything, just did all the order from the scratch. Thank you for help!

I did as you described, but still...
I installed into D:\www\cos-web-gallery, so the file .bluemix/cos_credentials resides there, the content of which is taken from the clipboard. Is that location correct?
D:\www\cos-web-gallery>npm start
><EMAIL_ADDRESS>start D:\www\cos-web-gallery
> node app.js

To view your app, open this link in your browser: http://localhost:3000

That address works. Using the browser, I tried to upload a file, resulting in:
  fieldname: 'img-file',
  originalname: 'P1000589.JPG',
  encoding: '7bit',
  mimetype: 'image/jpeg'
}
CredentialsError: Missing credentials in config
    at Object.openSync (fs.js:458:3)
    at Object.readFileSync (fs.js:360:35)
    at Object.readFileSync (D:\www\cos-web-gallery\node_modules\ibm-cos-sdk\lib\util.js:96:26)
    at SharedIniFileCredentials.refresh (D:\www\cos-web-gallery\node_modules\ibm-cos-sdk\lib\credentials\shared_ini_file_credentials.js:73:47)
    at SharedIniFileCredentials.get (D:\www\cos-web-gallery\node_modules\ibm-cos-sdk\lib\credentials.js:140:18)
    at resolveNext (D:\www\cos-web-gallery\node_modules\ibm-cos-sdk\lib\credentials\credential_provider_chain.js:119:15)
    at D:\www\cos-web-gallery\node_modules\ibm-cos-sdk\lib\credentials\credential_provider_chain.js:120:11
    at D:\www\cos-web-gallery\node_modules\ibm-cos-sdk\lib\credentials.js:142:31
    at SharedJSONFileCredentials.refresh (D:\www\cos-web-gallery\node_modules\ibm-cos-sdk\lib\credentials\shared_json_file_credentials.js:90:13)
    at SharedJSONFileCredentials.get (D:\www\cos-web-gallery\node_modules\ibm-cos-sdk\lib\credentials.js:140:18)

What am I doing wrong?
My galleryController.js reads like this:
    var ep = new aws.Endpoint('https://s3.private.fra.eu.cloud-object-storage.appdomain.cloud');
    var s3 = new aws.S3({endpoint: ep, region: 'eu-geo'});
    var myBucket = 'k48k-mybucketname-1';

Using https://cloud.ibm.com/objectstorage/..., I could upload files to this bucket without problem.


Visit Cross Project Skills in Inception is never used

While the skill is defined, no route ever reports it.  Further, the description references navigating from Project to Cross Projects, but there is not currently a tab or section called Cross Projects.

It was moved under Dependencies tab

PR: https://github.com/NationalSecurityAgency/skills-service/pull/1829


🐛 [BUG] -

Description
I encountered the following error when using tvm.relay.frontend.onnx to load an onnx model generated by nnsmith.

Installation
pip install "git+https://github.com/ise-uiuc/nnsmith@main#egg=nnsmith[torch,onnx]" --upgrade
Reproduction
# Paste the commands or python script for reproducing the issue.

Screenshots
![DESCRIPTION](LINK.png)

Logs
No response
Front-end framework
onnx
Version of the front-end framework
No response
Back-end engine
tvm
Version of the front-end engine
onnx-1.14.0
Other context
No response

Another error occurred while loading another model


test(client): overhaul e2e testing story to use cypress

TODOS:

[ ] - Figure out environment story (e.g. everyone should be able to run e2e against local server)

Is this still a WIP or ready for review?

I personally treat any WIP PR as ready for review.
In this case we could certainly provide more e2e tests and CI integration is also still in flux. But please feel free to leave feedback already.

@cburgdorf In our last discussion about this I think we've decided to let the e2e tests simply run against our staging system. That's fine by me. However we'll have cases where we run into chicken and egg problems. For example, to have the current e2e test suite pass, I needed to make some changes in our app's template.
Those changes are part of this PR but not yet deployed to staging, making our e2e tests naturally fail. I guess we regularly need to keep an eye on this, when a PR requires a deployment to staging first.
That being said, would you mind putting this branch on staging so I can work on the CI integration?

Here's another thing we need to agree on: Environment variables.
Basically what we want is:

Everyone should be able to run e2e tests locally on a local server (most likely localhost:4200)
e2e tests should be executed against staging.machinelabs.ai on CI
Maybe, in the future we want to be able to run e2e tests against different environments

Cypress offers a few ways to deal with this:
Using cypress.json
This would be a general environment configuration that would also be part of version control. Ideally, here we would configure default settings that should be the same for everyone. E.g. baseUrl = localhost:4200, no screenshots, no video recording.
Creating a cypress.env.json
This file would not be part of version control and everyone would basically be able to create their own custom environment settings. Also, conflicting values between cypress.env.json and cypress.json will be overridden. You can see the env file as a preferred setting with cypress.json being the fallback.
Using CYPRESS_* environment variables
Basically environment variables that can be quickly set/overridden. Those will also override values in cypress.env.json and cypress.json. Good for CI environments.
Using CLI's --env option
Similar to Angular CLI's env option, there's an --env flag that takes a comma separated list of values for environment variables. Those have the highest priority over all other options.
More on all those options here: https://docs.cypress.io/guides/guides/environment-variables.html
Proposal
In order let everyone run with his/her own config, but at the same time sharing the same for e.g. CI, I'd suggest we do the following:

We keep the already introduced cypress.json which sets baseUrl: localhost:4200 and turns off screenshots and video

Anyone who'd like to override any default settings can introduce their own cypress.env.json file (which we'll ignore in the project), or use any of the other options respectively.

Anything else that needs change for CI can be set in environment variables. However, right now, I think the provided defaults in cypress.json would do the trick.

Quick summary of our video call:

The e2e tests should run against a local webserver serving the client as it is in this PR. In other words, the e2e tests should not run against http://staging.machinelabs.ai because otherwise any PR that contains a new e2e test will fail in CI by definition as it just doesn't exist on the staging system yet.

However, the client that will run on a local webserver will run against the rest of the staging system (server, firebase). That's a bit of a compromise so that we don't have to have a system where each PR deploys it's own atomic universe (something that isn't trivial to achieve) at the cost of being dependent against the version of the server and the firebase that is currently deployed on staging.

@PascalPrecht mentined that running cypress on top of a ng serve is problematic so we try out a different approach where we first generated a dist and serve that manually without using the angular-cli.

Regarding the environment variables. I'm not sure yet how many environment variables we need. I'm fine to go with any of the proposed options.

Thanks for the write-up @cburgdorf !

@PascalPrecht mentined that running cypress on top of a ng serve is problematic so we try out a different approach where we first generated a dist and serve that manually without using the angular-cli.

Here's the related issue: https://github.com/bahmutov/start-server-and-test/issues/4#issuecomment-376971830

Alright, updated the PR to now run cypress on CI as well. Let's see what travis says.


Simulator Update

Update simulator to work with Firebase 3.0
Currently the REST protocol does not work with Firebase 3.0 . This thread is to discuss the way forward for the given simulator and what can be done.

Hi Guys,
So just some background about the new Firebase 3.0 API's.

The NodeJS API doesn't support the "signInWithCustomToken" call. This is only supported on the client side.
There appears to be a reserved "nonce" value in the JWT token. This alludes to the api requiring a nonce on every request. For the un-initiated this is a unique value  that can't be repeated per scope (Request, Session....). Given that we already have a unique DateTime which provides this per session I would suggest that the API is now implementing a Unique Nonce per request pattern. Saying this the REST API is probably going to be dumped for anything other than anonymous requests, a similar pattern can however still be implemented but the authentication needs to be respected.

So from the findings over the past couple of days I would suggest that the RestAPI needs to be obsoleted for Node based applications.
Luckily there is a pattern to work around the issue. Specifically we can run the "InitializeApplication" with a second parameter to include a namespace specific to the username and run requests against that specific instance. I'm currently in the process of working through this upgrade process in the background and should have something in the next couple of days.

From a security point of view I kind of agree that the Bearer Token authentication mechanism and most SPA architectures are broken. A nonce value would make sense so that stolen tokens can't be used to access resources. In the browser security model this usually means a Secure cookie that is tied to the bearer token as well. In a REST only world this secure cookie mechanism doesn't exists hence this is what makes me believe that they are trying to remove the reliance on it...
Comments welcome. I thought that given the lack of explanation over why the API has changed it might be worthwhile dragging this out from anyone closer to the API team at google...
Cheers

Hi guys, updated Simulator tied to the 3.0 API. I will merge this on my private repo for the time being but waiting for the main build to be updated for now...

Note that you can use the Bolt simulator with the 3.0 SDK - you just need to install the database secret to get the appropriate admin access via the REST interface.  I've updated the 'configure-project' command to point to the new location.


Support: adding sourceMaps when not built for production

First off thanks for creating a great start theme that lets more design focused guys like me use features I would have trouble setting up on my own.
I was wondering how I can add source maps to the theme when its running in watch mode, but have them disabled when I build for production. There is a lot going on with webpack and yarn I don't understand, which is great using what you already have. I just have trouble knowing how to extend it. I have used things like grunt or gulp but web-pack seems to go at it a bit differently.

👋 Hey @guategeek!
This is possible by adding mix.sourceMaps() to webpack.mix.js.
By looking at the original source code it seems mix.sourceMaps() accepts a parameter for if in production or not, would look something like this:
mix.js('resources/js/app.js', 'js/app.js')
   .sass('resources/sass/app.sass', 'css/app.css')
   .sourceMaps(false);

mix.sourceMaps() also accepts a second parameter type where you can specify the sourcemap type as stated here.
Couldn't find much more information about this in the laravel mix docs, but it's mentioned in Laravel docs with a basic example:
https://laravel.com/docs/5.6/mix#css-source-maps

On a sidenote, it's possible to check for production for other api references as well by using mix.inProduction(), for example:
mix.js('resources/assets/js/app.js', 'public/js');

if (mix.inProduction()) {
    mix.version();
}

Let me know if you're still having troubles setting up sourcemaps and I'll help!

Thanks so much for the help. Still took a lot of playing around to get things to work.
With help from this post and your comments, I was able to get source maps working as .map files in dev and watch, and not referenced when in production. Here is my webpack.mix.js setup if it can help anyone else
mix.setPublicPath('dist')
  .webpackConfig({devtool:'source-map'})
  .sourceMaps(false)
  .js('resources/js/app.js', 'js/app.js')
  .sass('resources/sass/app.sass', 'css/app.css')
  .options({
    processCssUrls: false
  })
  .version();

Great, I'm glad it's solved! Happy coding and thanks for using this theme! 🙌
Closing this issue as it's resolved.


Add darkmode to other projects page.

Fixes #131

Doesn't seem to be working

I think, I know why its not working. @aliraza944 Called out some stuff in the css, but here the css is main.css

Still aren't working

Added in commit f54ba48, #172


feat(blockquotes): add blockquotes plugin

Hi everyone! First of all, thanks for your time publishing this work here on GH.
I'd love to use this plugin and if there's anything that is blocking it from being published, maybe I can help with it. Thanks!

Hey @slig, I haven't had time to iron out the bugs here yet, but I'm happy to merge this and release as an alpha version if you want to play around with it. Just a warning that it's probably not quite production ready, and we're not using it in production yet.

Thank you very much!

Published as<EMAIL_ADDRESS>Feel free to file issues as you run into them. Thanks for checking it out!


dotnet_host_path

Version 4.3.1 rendered the following errors:

Errors occurred while analyzing dependencies for some of your projects. Are you sure you can connect to all your configured NuGet servers?

Unable to find DOTNET_HOST_PATH environment variable. If you use credential providers for your NuGet sources you need to have this set to the path to the dotnet executable.

After setting the environment variable (why do I need to do that..!), the first error still remains.
This worked flawlessly yesterday (no problem if I use  CLI or VS).

Version 4.3.2 should fix this @doterik

👍🏼

This is happening to me to with version 4.6.4+3bad9cacfd8752a5d0a98fad47493c26bd8f5a88
We use private Nuget feeds that are configured in a repo level nuget.config file.
Is there any useful information that I can provide?
Errors occurred while analyzing dependencies for some of your projects. Are you sure you can connect to all your configured NuGet servers?

Unable to find DOTNET_HOST_PATH environment variable. If you use credential providers for your NuGet sources you need to have this set to the path to the `dotnet` executable.


please help to clarify the behavior of "default

[Enter feedback here]

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

ID: b57420a5-e3d6-5b81-4f22-1257df5c3743
Version Independent ID: 602cb979-ec58-7bee-3d02-5667cd422c33
Content: Autoscale with multiple profiles - Azure Monitor
Content Source: articles/azure-monitor/autoscale/autoscale-multiprofile.md
Service: azure-monitor
Sub-service: autoscale
GitHub Login: @EdB-MSFT
Microsoft Alias: edbaynash

#Duplicate as https://github.com/MicrosoftDocs/azure-docs/issues/105481


[BUG] No handler found for URI /_plugins/_security/api/nodesdn

The API for the security plugin does not seem to be able to handle the API for the nodes_dn data.
From the Dev Console inside dashboards or externally using curl and the admin keys, this request:
 GET _plugins/_security/api/nodesdn

results in
 {
   "error" : "no handler found for uri [/_plugins/_security/api/nodesdn] and method [GET]"
 }

This is a new install of RPM-based OpenSearch 2.1.0 running on RHEL8
I use the plugins.security.nodes_dn parameter in the opensearch.yml file to implement host validation, but would like to move to the nodes_dn.yml file -- but the documentation on that is lacking at the moment.

@dredwilliams I see that this was closed shortly after it was opened, Is there an issue around this feature or its documentation?


Unnecessary Resampling leading to poor pixel positioning

Dear Hongfaqiou,
there seems to be an issue with how TIFFImageryProvider maps the tiff values to the canvas. This occurs even when re-projection is not needed, e.g. for cogs in EPSG:4326 and EPSG:3857.
Using this Climate Data cog as an example (it is in EPSG:4326): https://nex-gddp-cmip6-cog.s3-us-west-2.amazonaws.com/daily/GFDL-CM4/ssp585/r1i1p1f1/pr/pr_day_GFDL-CM4_ssp585_r1i1p1f1_gr1_2015_01_25.tif
The data should look like this:

But TIFFImageryProvider renders it like this:

Note the following:

The pixels are no longer square and appear to be resampled
It does not retain the data integrity - we need users to be able to see the value of this scientific data at a single point on the globe.

Note in a more zoomed in example, how the pixels are clearly not square. This is TIFFImageryProvider in TerriaJS:

This is TIFFImageryProvider in your online demo:

Whereas the tru data is square pixels (shown in QGIS):

Please note, to be able to see what is happening at the pixel level we have changed the Cesium settings for _defaultMagnificationFilter and  _defaultMinificationFilter to remove the blurring:
https://github.com/TerriaJS/terriajs/blob/13fa4cfaabecdc82dff749836a1dcef602b0a1ae/lib/Models/Catalog/CatalogItems/CogCatalogItem.ts#L140-L141
If you like, we have put more details on the perceived error in out PR here: https://github.com/TerriaJS/terriajs/pull/7209

@staffordsmith83 I'm glad to see you continue to support TIFF in terrainjs. This issue is the same as #18, and I've been quite busy lately. I'll try to fix this issue next week, which seems to be related to resampling

Thats great, thanks @hangfaqiu, @nf-s watch this ticket

@staffordsmith83 I spent a day solving this problem, and now:

Scaling no longer causes distortion
The values are accurately represented from the original TIFF

I will submit the improved code in the next two days.

@staffordsmith83
I have released the corrected version v2.11.0.
The reason for this issue is as follows:

For tiles exceeding the maximum level of the COG (Cloud Optimized GeoTIFF), the accuracy is lost when calculating the sampling window using latitude and longitude.
The default resampling method of GeoTIFF changes the width and height structure of the acquired TIFF grid.
When rendering the data resampled with a small window using GeoTIFF, the grid boundaries of the original TIFF cannot be aligned.

The implementation approach is as follows:

No longer set the maximum level to maximumLevel by default for COG.
Use the tiles of the last level of the COG at higher levels.
Calculate the window size of the current tile on the clipped tiles.
Resample to the target resolution.

The current issues are:

Although WebWorker is used to accelerate, the speed seems to be average.
When fetching TIFF data at higher levels, there are cases of repeated calculations, especially poor performance when using reprojection.

The optimization plan is:

Use WebGL for resampling, pass the original data as a texture, and resample to the target width and height.

@Staffordsmith83 @nf-s, a huge thanks to the wonderful new contributor @TheMrCam for offering the resampling method for bilinear.
Thank you so much for your hard work, and the functionality of this library has become even more splendid. How delightful it is!
But there are still some problems

I found that when zooming to a larger level, the position of the grid is shifted overall
Bilinear interpolation produces unnecessary segmentation rather than sharpening when scaling to larger levels

@staffordsmith83 I have released the corrected version v2.11.0. The reason for this issue is as follows:

For tiles exceeding the maximum level of the COG (Cloud Optimized GeoTIFF), the accuracy is lost when calculating the sampling window using latitude and longitude.
The default resampling method of GeoTIFF changes the width and height structure of the acquired TIFF grid.
When rendering the data resampled with a small window using GeoTIFF, the grid boundaries of the original TIFF cannot be aligned.

The implementation approach is as follows:

No longer set the maximum level to maximumLevel by default for COG.
Use the tiles of the last level of the COG at higher levels.
Calculate the window size of the current tile on the clipped tiles.
Resample to the target resolution.

The current issues are:

Although WebWorker is used to accelerate, the speed seems to be average.
When fetching TIFF data at higher levels, there are cases of repeated calculations, especially poor performance when using reprojection.

The optimization plan is:

Use WebGL for resampling, pass the original data as a texture, and resample to the target width and height.

GPU based resampling supported, please check the latest version @staffordsmith83

Thanks @hongfaqiu this is great work! Just to let you know, the latest terria release incorporates your TIFFImageryProvider, we had to fork the code to make some modifications to suit our custom fork of cesium, but it is essentially your code that powers our COG support. Ive now left the project, but want to thank you very much for your contribution! I will alert the existing team to this new version

@staffordsmith83 I have noticed that terriajs seems to have opened a rather different branch. The main branch fixed some obvious bugs some time ago. Therefore, I would like to remind you.


Add ignore fake player configuration

I did a test run yesterday on my heavily modded server, after 2hours I had collected about 2 million events.
This adds an option to ignore Fake players for events that currently log them.
I wasn't sure where to put the configuration node, let me know if you have any concerns!

This will be helpful, especially since Sponge works so well on modded servers. It might be necessary in the future to find a way to filter these, because there might be cases where some TileEntities should be tracked while others not.

So with this will things such as quarry's not log their block changes? That is my only worry, as we probably should provide a way to undo those and other similar actions.

The whole purpose of this for me is not logging quarries, they produce insane amounts of data. I'm not opposed to a whitelist/blacklist, but for now I just disabled this by default.

For a temporary fix this seems great then as that is a lot of data. For the future, do we think a blacklist or a whitelist would be better @viveleroi?I am thinking a blacklist as for some servers with a lot of mods would have to come up with quite a long list of items to add to a whitelist. In @phit's case, he could simply blacklist the problematic blocks such as quarries.

A blacklist is probably best, or even allow toggling one or the other.

Oh, looks like it doesn't like the underscore, what would be a good name for this? IGNOREFAKEPLAYERS also seems kinda long.

The IGNORE_FAKEPLAYERS variable name is against the check style :P. I think changing the name to IGNOREFAKEPLAYERS works fine.


What is the reason of deprecaiting iter methods?

Greetings! Thank you for continuing to maintain this project and creating the repository.
I updated my project to the new version dotenv and saw that iter methods were deprecated. As for me, I found them quite useful in my project, because they allowed me to read dotenv files, preprocess variables and then to decide which of them and how I store in the environment. With deprecating those my only option is to iterate though vars() (which is basically just env::var()) and I don't have any way to detect whether those come from the system or from the dotenv file.
Could we consider un-deprecating those methods? Thank you

The reason was that all the cases I could find of people using the iter methods was to use the dotenv crate for config files instead of actually merging them with the environment. dotenv is not intended for managing config files per-se, it's for managing environment variables. If you have a legitimate usecase for inspecting the variables before sending them into the environment I'd love to hear it! If there are compelling reasons to do the inspection I will consider un-deprecating these methods.

Not sure if it's a valid usecase, but: I manage my infra via rust binary and this binary reads env files and runs various of tasks. One of the examples is it starts development environment + specs in watch mode. Running processes use different env files. For such case, I prefer not to load anything in parent environment but read appropriate file and pipe result to environment of appropriate child process. TBH I'm not sure if this change might actually cause issues but global state makes me worry by default and I would prefer not to have it when it's not required and potentially might cause problems.

I think I can imagine issues here. E.g. if I forgot to pipe env vars to one of the child, with clean parent environment it would crash due to absence of the data. But when parent environment is populated with the wrong set of vars, then it would inherit it and hello debugging fun.

@alexfedoseev just to make sure I understand, you launch a child process and then modify its environment with the contents of a .env file? If this is the case, why doesn't the child process run the .env file itself?

@dgriffen I abstracted it away so process uses provided env vars, e.g.:
pub struct Cmd {
  pub bin: &'static str,
  pub args: Args,
  pub env: EnvVars,
  pub cd: Dir,
  pub msg: &'static str,
}

pub fn up() -> Cmd {
  Cmd {
    bin: "cargo",
    args: Args::new(vec!["watch", "-x", "run"]),
    env: DEV_ENV.all(),
    cd: Dir::CoreServer,
    msg: "Running reloadable Core development server",
  }
}

Then returned Cmd is used by the executor. This allows me to use same abstraction for processes that need all vars from the .env file as well as processes that need only few (or don't need env at all).

If this is the case, why doesn't the child process run the .env file itself?
I can answer this question for my use case. Because dotenv::dotenv() doesn't actually override already set environment variables. This is apparently by design, but I actually want the opposite. I'm not sure why this is not an option, but I have to use dotenv_iter() hack like
Command::new("env").envs(dotenv::dotenv_iter()?.collect::<Result<Vec<_>,_>>()?).status()?;

in order to achieve what I want at least for subprocesses.

Hey @dgriffen! Sorry it took me so long to answer..
In my project in order to set environment variables for the application I require to use APP_NAME_ prefix for all the variables keys. At the same time in .env I allow users to omit that prefix, because people can be confident that the variables are applied exactly to the application. This way I can reduce some boilerplate, especially if the prefix is quite long.
So the thing I do with preprocessing is prepending APP_NAME_ prefix to every key that is specified in .env (if the prefix is not used already).
With deprecating iter methods I'll loose that convenience and I'll have to either bring prefix boilerplate back to .env or to resort to some hacks, that I'd really prefer to avoid, like iterating through a whole list of environment variables and mutating a subset of them.

@mvlabat okay, I can definitely see that as a use-case! I'll go ahead and undeprecate thse methods in 0.14.2. I will probably change their return type signature slightly though since I don't like that they expose an internal iterator type.

It doesn't seem like those methods were undepricated. Even though it's mentioned in CHANGELOG.

@alexfedoseev thanks for reporting, I forgot to actually undeprecate them.

That PR has all but wrapped this up. I'm pretty sure this issue can be closed


Revamp response serialization performance

Reference: https://github.com/tiangolo/fastapi/discussions/5669

@tiangolo Do you have time reviewing this?

Thanks @kigawas! As this could hit corner cases not covered, I would rather not do it and instead do the current official way to convert dataclasses to dicts.
If you want to squeeze performance, you could serialize directly and return a response directly. Also, a future version of FastAPI will use Pydantic's own serialization, which is equivalent to orjson (Rust's SerDe), so that will probably help a lot. You would probably also get performance improvements by using Pydantic v2 with FastAPI in most places instead of dataclasses.
Given that, I'll pass on this one, but thanks for the interest! ☕


Android TV Support

Can APKs and AABs created run on Android TV. A friend asked me because he owns Android TV and therefore wanted the right answer for him.

Unfortunately, Android TV doesn't devices usually don't have a browser, so Trusted Web Activity won't work there. A common solution is using a WebView to wrap the web experience.
Closing the issue, as this is currently outside the scope of Bubblewrap (due to the lack of a browser in Android TV devices).


Research tooltip accessibility

Description
read this article and research tooltip accessibility
modify component if necessary
Problem Statement/Justification
none
Proposed Solution or API
No response
Alternatives
No response
Are you willing to participate in implementing this feature and create a pull request include the implementation?
None
Additional Information
No response

@yamada-ui/tooltip is applicable to this issue

@yamada-ui/tooltip probably does not satisfy all the checkmarks.

@taroj1205
please double check

@taroj1205 please double check

Yes, it does seems to not satisfy WAI-ARIA Roles, States, and Properties.

created issue
https://github.com/yamada-ui/yamada-ui/issues/1634


Mobile browser support

In order to work on a stock mobile browser, audio and video elements need to be created beforehand, and during a ui event handler only is javascript allowed to start an audio or video playing.

Closing as this issue has been opened at https://github.com/soap-bubble


Added OWS-ArcGIS pro doc

Added the instructions to connecting to the DE Africa Web Services for GIS using ArcGIS Pro. For each web service, the ArcGIS instructions were added after the relevant QGIS instructions.


Grafana roundtrip json export/import bug

Unfortunately I can reproduce this issue reliably: https://github.com/grafana/grafana/issues/2816

Create dashboard in Grafana 3
Export json file

Import json file manually (via Grafana web UI) works.
Import via API does not despite making the exact same API calls.
In other words, there's some additional json munging required, can't submit dashboard file as-is.
This is an inconvenience because now a hackish post processing step is necessary for demo outputs.
Note: the really odd thing is that backwards compatibility with Grafana 2 is good so dashboards exported from that are imported correctly both ways.

This is the dashboard json baked into current kube-grafana container:
https://github.com/cncf/demo/blob/master/Docker/grafana/dashboards/cncfdemo.json
This is how it roundtrips back out if you export it from the UI:
https://gist.github.com/zilman/4fde89c1d07d370e709559bb44274ffa
The diff:
"dashboard" : {
...
    "overwrite" : true,
    "inputs" : [ {
        "name" : "DS_PROMETHEUS",
        "type" : "datasource",
        "pluginId" : "prometheus",
        "value" : "Prometheus"
    } ]

Without injecting this blob it just fails to import programatically.

What would be the final solution for this problem. I tried that containerized grafana with baked json in
https://github.com/cncf/demo/blob/master/Docker/grafana/dashboards/cncfdemo.json
That still failed.


feat: create comdex testnet config

Description
Closes: #XXXX

Run npm run dev --chaintype=testnet --chainname=comdex and check testnet.localhost:3000/comdex to test

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] ran linting
[ ] wrote tests where necessary
[x] included the correct type prefix in the PR title
[x] targeted the correct branch
[ ] provided a link to the relevant issue or specification
[x] reviewed "Files changed" and left comments if necessary
[x] confirmed all CI checks have passed
[ ] added an entry to the CHANGELOG.md file

close PR and add config to monorepo


Grav admin add account appears to fail.

This is regarding a fresh install of Grav v1.7.0-rc.8 - Admin v1.10.0-rc.8:
When a new account is added in admin and it’s fields populated, trying to save it generates a 404 error. Then an attempt to log in using the new account’s username and password fails with “Login failed…”. The initial admin account works correctly. This is the case on both my local development server and on the production server.
In user/accounts a new yaml file is created with what looks like a 32 digit hex number as its name (e.g. ‘b5ec29f160ca2a63e70f08d39f6792bb.yaml’). If this file name is used as the username or if the yaml file name is changed to intended username, everything works correctly. I assume the 404 is because admin is looking for a yaml file with the correct username and but at login it expects the numeric name.

I also encounter this:
After creating an account

when you access the username you entered

This one has actually been fixed already.


Add assistant to microtask-renderer

This is a temporary fix to introduce assistant. Will move to BaseFragment when we implement ViewModel for Microtask renderer

Please use the visible() extension method wherever possible.


Add method for getting all entries

Fixes #45
Fixes #9
From instrument/contentful_middleman

@dlitvakb Awesome!  Thanks for pulling this into the contentful-labs repo.  Any chance you can do a release with this fix in there?

@nijotz Yes! It will be released during this week, can't confirm exact date yet.


Clarification: EnderIO and Flan's mod dual wielding

I'm experiencing an issue where EnderIO seems to be preventing Flan's mod dual-wielding. I've seen this posted on here twice already. I'm not clear on whether this a solved issue or not yet.

I don't see how it could possibly be the fault of EIO. Flan has yet to weigh in on the issue. We have no interaction with Flan's mod so it must be a problem on his end.

Perfect, works for me. I'll resume nagging him.
Incidentally, awesome mod. Keep up the good work!


Add support for importKey for P-521 public key on Deno.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (5cdfa76) 97.43% compared to head (47b26b1) 97.43%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #294   +/-   ##
=======================================
  Coverage   97.43%   97.43%
=======================================
  Files          35       35
  Lines        2265     2265
  Branches      233      234    +1
=======================================
  Hits         2207     2207
  Misses         57       57
  Partials        1        1

Flag
Coverage Δ

unittests
97.43% <ø> (ø)

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

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


Finalize UX documentation regarding text field

### Accepotance criteria
- [ ] Images for the documentation
- [ ] Take a look to the texts of the documentation, and update this with the Jeroen's changes.
- [ ] A11y tab section of the documentation isn't complete.

duplicate see #597


Editor should be initialized outside angular ngZone

If I'm not mistaken the editor is initialized inside the current angular ngZone.
This means that each event listener that the editor create will be linked to angular change detection.
Thus a lot of action on the editor could trigger an angular change detection cycle.
This could be a source of bad performance in certain cases.
Would it be possible to add a flag on the editor to enable or disable ngZone on the editor ?

This is a big issue, because Internet Explorer 11 (which is unfortunately used by our customer) has big problems with that. it get extremly slow

i have a possible working solution in my fork and need to test it on my mac to send a pull request.

I am running into issues when running e2e tests with Protractor. I run into script timeouts.
I know that another editor fixed a similar problem by running outside of the Angular zone.


Dynamic routes using the wrong locale in Next 13.4.13

What version of this package are you using? 2.5.3
What operating system, Node.js, and npm version? Windows, Node 20, pnpm
What happened?
I have an app with the two locales en (base) and de. Some of my routes are dynamic, like /[channel] and /video/[id].
After updating to Next 13.4.13, I am encountering this behavior in my app: When navigating to a dynamic route like /[channel], it switches to the base locale even though the URL locale doesn't change. So it would navigate from /de to /de/test, but loads the en locale. When navigating back to a non-dynamic route it uses the correct locale again. This only happens with Next 13.4.13, dynamic routes and when navigating using a router Link or router.push.
Here's the dev server logs:
next-translate - compiled page: / - locale: de - namespaces: common, navbar, home, channel - used loader: getServerSideProps
next-translate - compiled page: /[channelName] - locale: en - namespaces: common, navbar - used loader: getServerSideProps

I experience something similar while using pages folder.
When navigating through <Link> to a dynamic route or page with getServerSideProps, translations are not loaded. Instead, it shows translation keys i.e. about_us.some.key. After page refresh or when the page opened directly translations show OK.
next-translate and the plugin of v2.5.3, next.js v13.4.13

Downgrading next to 13.3.x did not help
legacyBehavior on  did not help

Any idea?

I can confirm what @shelooks16 has found. When removing my middleware.ts, which does not handle anything locale-related, this issues does not occur.


Empty Negotiation Response from Service/SyntaxError: Unexpected end of JSON input

I have a standard-tier SignalR service in Default mode which has been working, but this morning when I try to connect I get the following back from the /negotiate request forwarded by my app:

Request (app):

POST https://localhost:44368/chat/negotiate?...&negotiateVersion=1
Response:
200
Body: {"negotiateVersion":0,"url":"https://....service.signalr.net/client/?hub=chathub\u0026asrs.op=%2Fchat...\u0026negotiateVersion=1\u0026asrs_request_id=ftgdb1cBAAA%3D","accessToken":"...","availableTransports":[]}

Request (service):

POST https://....service.signalr.net/client/negotiate?hub=chathub&asrs.op=%2Fchat&...&negotiateVersion=1&asrs_request_id=ftgdb1cBAAA%3D
Response:
200
Body:

The following error comes back when I call HubConnection.start() in the JavaScript client:
SyntaxError: Unexpected end of JSON input
at JSON.parse ()
at HttpConnection. (signalr.min.js:16)
at step (signalr.min.js:16)
at Object.next (signalr.min.js:16)
at fulfilled (signalr.min.js:16)

We also started experiencing this issue with all our Azure SignalR Instances this morning. We logged a Sev-A Ticket with Azure support

We also started experiencing this with a c# based client that has been in production since last December. All systems, even running local, have started to fail which leads me to think that either something changed with the signalr service itself, or something changed in the token validation or generation that is making the negotiation fail. We get a token using the ADAL library based on the client if the app service hosting the the hub. I've verified the token exists, and this exact code is used throughout our systems for rest calls and works everywhere else.
Please any suggestions would be greatly appreciated. We've also started a ticket, but it is through a vendor and takes forever to escalate.

I'm having this issue as well with Azure SignalR standard tier it started this morning around 4am.
I did notice that specifying the transport type manually skipping the negotiation does seem to fix it, but I'm sure this is a terrible solution, not recommending it.
.withUrl("/chathub", {
  skipNegotiation: true,
  transport: signalR.HttpTransportType.WebSockets
})

@PaitoAnderson doesn't seem so bad. Thanks for the info; glad we haven't gone to production with this yet.

Interesting that the documentation clearly states that skipNegotiation: true isn't supported for Azure SignalR... so that is confusing

Yeah, just noticed that. Could it be that clients are just connecting to the app itself and not the service in that case?

Yea, when running locally, my socket is connected to localhost instead of Azure SignalR now

The way we are setup, the Hub<IMessageHub> does the negotiation based on the credentials passed in, convenient because this app supports openid connect, cookies and jwt for various clients. That negotiation call returns the url of the signalr server in azure along with an access token for that service and hub name. Then the client calls the azure service to negotiate, it returns a new token and the list of transports allowed. To send messages, the messages are coming from azure regardless of running local or in azure as I understand it.
I duplicated all these calls with postman. I have two different hubs in the same instance of azure signalr. One works, and returns the token and transports. The other returns 200 OK, and no data whatsoever. Hoping a call from MS signalr team is coming soon

This is what we received so far via our support ticket. Seems like there was a new release of Azure SignalR to US-East that broke all of us.

Confirmed this also appears to be broke on new signalR instances in the west coast as well.

I was having the same issue with a new service I spun up on Monday. :shrug:
I'm just glad it doesn't seem like an issue with the SDK. I was going crazy
trying to figure out what I was doing wrong.
On Wed, Aug 26, 2020, 18:24 Mike Stephens<EMAIL_ADDRESS>wrote:

Confirmed this also appears to be broke on new signalR instances in the
west coast as well.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Azure/azure-signalr/issues/1000#issuecomment-681154965,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQTITVH27HKT3AU3V6OUOLSCWDTFANCNFSM4QL6Y3VA
.

We've identified the root cause and are hot fixing all the influenced instances. It might take ~30mins to have all the influnced instances fixed. An RCA will be provided shortly after.

This is working for me now, thanks!

RCA
Impact:

Cannot create client connection (negotiation failed)

Only if the customer's app server used AAD to authorize their requests.

For resources created recently (resources created within the mentioned range will be impacted)

WestUS2

From 8/21 08:06 To 08/27 03:01 (UTC)

EastUS

From 8/24 07:29 To 08/27 03:01 (UTC)

Southeast Asia, Canada East, West Europe, Central US, UK South, South Central US

From 8/25 07:20 To 08/27 03:01 (UTC)

Australia East, North Europe, Japan East, East US 2, West US, Brazil South, France Central, Korea  Central

From 8/26 08:00 To 08/27 03:01 (UTC)

For existing resources (all resources will be impacted within the time range)

WestUS2

From 8/24 07:12 To 8/27 03:25 (UTC)

EastUS

From 8/26 08:01 To 8/27 03:30 (UTC)

Root Cause
We deployed a new feature to encourage our customers to use AAD Token to access our service instead of using AccessKey. However, if our customer had already used AAD Token to authenticate requests to their server, our SignalR SDK will forward all the claims in that token to the ASRS, including the Issuer. In this scenario, our ASRS will falsely enter a different authorization process and decline the negotiation request with status code 200 and an empty response body.
Mitigation
We rollbacked all the resources in WestUS2 / EastUS and newly created resources in other regions.
Repairs

Check both Audience and Issuer field for identifying if a given Token is an AAD Token.
Return 401 Unauthorized if the authorization process failed.

Customer workarounds
Set a customized claim provider to overwrite the Issuer field, any value except for "https://sts.windows.net/" is acceptable
services.AddSignalR()
    .AddAzureSignalR(s => s.ClaimsProvider = (c) =>
    {
        var claims = c.User.Claims;
        return claims.Concat(new Claim[] { new Claim("iss", "") });
    });

This issue took our production environment down for an entire day. I am curious why the status page was not updated to reflect at least a partial degradation of your managed service? What about impact to SLAs?

We apologize for the downtime this issue caused to your production environment. If you believe your production workload has been affected by this issue with SLA impact, please open a customer support ticket to have it processed based on our promised SLA.
Regarding Azure status page, a general guideline from Azure (a good article can be found here) is it is mainly for outages that all customers and major scenarios are impacted. Since this issue only impacts customers who use AAD, we ended up using Azure service health to inform each customer in the impacted regions. If you go to service health in Azure portal you should be able to see an alert regarding this outage.


make it a choice to load move_group capabilities

Description
I encountered this error [ERROR] [launch]: Caught exception in launch (see debug for traceback): 'capabilities' mentioned in #2734
Now I can launch my robot_moveit_config with the choice of adding those capabilities or not. I don't need them for now but it might come in handy if I'm going to use MTC as explained in the PR comment that passed those capabilities to launches.py
from moveit_configs_utils import MoveItConfigsBuilder
from moveit_configs_utils.launches import generate_move_group_launch

def generate_launch_description():
    moveit_config = MoveItConfigsBuilder("thermoplast_abb_irb4600_camera_cell", package_name="abb_irb4600_webcam_moveit_config").to_moveit_configs()
    return generate_move_group_launch(moveit_config, load_capabilities=True)

Could you please update the description here?

Could you please update the description here?

done

thanks @gavanderhoorn


When working with Conda, there are no checks on the environment packages

Describe the bug or the issue that you are facing
When creating the environments with conda, there are no checks performed when creating the environment to see if the packages exist or if the pip dependencies are also correctly installed.
Steps/Code to Reproduce
When creating the environments with conda, there are no checks performed when creating the environment to see if the packages exist or if the pip dependencies are also correctly installed.
az ml environment create --file .\train-conda.yml
train-conda.yml
$schema: https://azuremlschemas.azureedge.net/latest/environment.schema.json
name: docker-image-plus-conda-example
image: mcr.microsoft.com/azureml/openmpi4.1.0-ubuntu20.04
conda_file: environment.yml
description: Environment created from a Docker image plus Conda environment.

environment.yml
channels:
  - defaults
  - anaconda
  - conda-forge
dependencies:
  - python=3.7.5
  - pip
  - pip:
      - azureml-mlflow==1.38.0
      - azureml-sdk==1.38.0
      - sklearn==0.24.1

Expected Output
No error is thrown even though there is no such package like sklearn.
There should be a check to make sure that the environment has been successfully created before moving on to the next steps.
Versions
running az -v
azure-cli                         2.43.0
core                              2.43.0
telemetry                          1.0.8
Extensions:
account                            0.2.5
ml                                2.12.1
Dependencies:
msal                              1.20.0
azure-mgmt-resource             21.1.0b1
Which platform are you using for deploying your infrastrucutre?
Azure DevOps (ADO)
If you mentioned Others, please mention which platformm are you using?
No response
What are you using for deploying your infrastrucutre?
Bicep
Are you using Azure ML CLI v2 or Azure ML Python SDK v2
Azure ML CLI v2
Describe the example that you are trying to run?
Tabular. but this affects all the environments.

There is also an open issue with this https://github.com/Azure/azure-cli/issues/23381


Add support for mlint, a MATLAB linter

I had to redirect stderr to stdout, so this probably doesn't work in Windows. Let  me know if I should do it a different way. I looked some and didn't see current support for any other linters that output to stderr.

Thanks for pointing out the right way to handle stderr. I think I addressed all your changes @w0rp.

Looks good to me. Cheers! :beers:


playLayout: an option similar to smallHide, but starting with the normal layout

essentially, give the option to click on the game icon and toggle the left side

Implemented in v2.3.70


LockingIterator should use fopen mode c

	$this->lockFp = fopen("{$this->dir}/$name", 'w+');
	flock($this->lockFp, LOCK_EX);

This is not atomic. Probably
	$this->lockFp = @fopen("{$this->dir}/$name", 'x');

would be better. On unlock, just delete the file.

No this would be a really bad way of dealing with locks. If the program crashes, the flock call wil automatically release its lock.
If you use fopen with 'x' modifier and the program crashes the file remains and no new processes can start.
the current code is atomic. you can easily test it by running the following code twice concurrently:
<?php

var_dump("opening");
$lockFp = fopen("lock", 'w+');
sleep(2);
var_dump("locking");
flock($lockFp, LOCK_EX);
var_dump("locked");
sleep(5);
fclose($lockFp);
var_dump("ready");

with the extra sleep functions the race conditons can be tested and in no circumstances can the locked parted by executed twice concurrently.

Sure! While we are chatting (hi!) mind chiming in on itertools vs nikic/iter in https://www.drupal.org/node/2757489 ? Thanks much!


How to set ip for hoverfly?

Hi!
How do I set hoverfly to listen on something other than loopback like <IP_ADDRESS>/8? The only config I can find concerns hoverctl and it's remotes.

Hi @karlpokus, you can set hoverfly to listen on a single address only, for example hoverfly -listen-on-host <IP_ADDRESS> , or listen to all interfaces: hoverfly -listen-on-host <IP_ADDRESS>. I don't think it works with a CIDR block.

@tommysitu Wonderful! Thank you. I'm gonna try this.

@tommysitu
$ hoverfly -listen-on-host <IP_ADDRESS>/8
INFO[2018-02-07T13:44:24+01:00] Listen on specific interface                  host=<IP_ADDRESS>/8
INFO[2018-02-07T13:44:24+01:00] Using memory backend
INFO[2018-02-07T13:44:24+01:00] Proxy prepared...                             Destination=. Mode=simulate ProxyPort=8500
INFO[2018-02-07T13:44:24+01:00] current proxy configuration                   destination=. mode=simulate port=8500
FATA[2018-02-07T13:44:24+01:00] Failed to start proxy                         error=listen tcp: lookup <IP_ADDRESS>/8: no such host

<IP_ADDRESS> works though.

You are not the first one asking the question. I have added the answer to the "Troubleshooting" section in the docs now.

@tommysitu Yeah documenting this sounds good. btw: any chance of adding the flag to hoverctl in the future?

Yes, inconsistent flags between hoverctl and hoverfly is an issue. If you want to do some Go, feel free to send us a PR.

@tommysitu I'd be happy to contribute. Let me see if I can find a spot. Regardless - thanks for the swift reply. Really like working with hoverfly.

The inclusion of the listen-on-host flag has been merged in via #705 and is now awaiting release.

@benjih Excellent news! Thank you 😃


Rust library: Optimize Vec of certain types

It seems that Candid serialization/deserialization in Rust can get quite expensive, especially if Vec<u8> is involved. Users can avoid that by using serde::ByteBuf instead, which allows Candid to copy the whole blob in and out, but it’s inconvenient if Vec<u8> is idiomatic.
The obvious solution, i.e. impl Deserialize for Vec<u8> in addition to impl Deserialize for Vec<T>, doesn't work (unless we get https://github.com/rust-lang/rust/issues/31844).
But we could do what Haskell does to handle a very similar problem with the same constraints (there the pretty-printing of [Char]).
This would require extending CandidType to have, in addition to the existing method
    fn idl_serialize<S>(&self, serializer: S) -> Result<(), S::Error>

a new method (rought syntax)
    fn idl_serialize_vec<S>(xs : &[Self], serializer: S) -> Result<(), S::Error>

Vec[t]’s implementation of idl_serialize calls idl_serialize_vec on the conatined type
Most impls define idl_serialize_vec by calling the usual, polymorphic, encoding function for Vec (i.e. what idl_serialize does for Vec[t] now)
But some, like impl CandidType for u8, can now do optimized stuff, e.g. use serialize_blob.

For encoding we can do that, since we have a custom trait. For decoding this might require introducing a CandidDeserialize instead of using Serde’s, not sure.

I see. So the trick comes from &[Self] which side-stepped the specialization restriction. Instead of impl for Vec<u8> and Vec<T>, we impl for u8, and other types.
For decoding, that means we cannot use serde's framework, or we need to convince serde to adopt this trick.


Publish Prospero documentation on https://docs.wildfly.org

To publish Prospero docs on https://docs.wildfly.org, we would need:

Automatically generate docs whenever we do a release of Prospero

-> The prospero-build-1.2.3.Final.zip contains an empty docs dir. This looks to be a bug as I was expected to get the generated content from https://github.com/wildfly-extras/prospero/tree/main/dist/docs

Open a PR in https://github.com/wildfly/wildfly.github.io that would add this doc in a prospero subdirectory

-> this would make the doc available at https://docs.wildfly.org/prospero

@jmesnil thanks, I'll take a look at the first point.
As to the publication - does it mean that's a manual process to update the documentation, i.e. every time new version has to be pushed to wildfly/wildfly.github.io?

yes, whenever you release, you'd have to update https://github.com/wildfly/wildfly.github.io and merge the updated doc.


[Device Support Request] Tuya TS0121 (new device_type?) Not getting quirks applied

Problem description
I've recently bougt two new Connecte power sockets (rebranded tuya) which doesn't report power usage correctly, not firmware either.
From before I have 3 other working perfectly fine. The two new ones are sold as the same socket.
Current measurements are having spikes at almost 3000A, and measure around 130-140A while the power measurement is around 40W (seems about correct for a small fridge)
Summation delivered is also increasing too quickly showing about 35kWh in a day.
Voltage seems to be reported correctly.
Solution description
I don't know how to write or adjust quirks, but I imagine it is the same quirk as before, it just needs to apply to the new identifier as well.
Screenshots/Video
Screenshots/Video
[Paste/upload your media here]

Device signature
Device signature
{
  "node_descriptor": {
    "logical_type": 1,
    "complex_descriptor_available": 0,
    "user_descriptor_available": 0,
    "reserved": 0,
    "aps_flags": 0,
    "frequency_band": 8,
    "mac_capability_flags": 142,
    "manufacturer_code": 4098,
    "maximum_buffer_size": 82,
    "maximum_incoming_transfer_size": 82,
    "server_mask": 11264,
    "maximum_outgoing_transfer_size": 82,
    "descriptor_capability_field": 0
  },
  "endpoints": {
    "1": {
      "profile_id": "0x0104",
      "device_type": "0x0051",
      "input_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0702",
        "0x0b04",
        "0xef00"
      ],
      "output_clusters": [
        "0x000a",
        "0x0019"
      ]
    }
  },
  "manufacturer": "_TZ3000_5ity3zyu",
  "model": "TS0121",
  "class": "zigpy.device.Device"
}

Diagnostic information
Diagnostic information
The log file was too long to paste, so it's attatched as a file.
zha-7de48d8e8d99ebff82bd942e0e2db63a-_TZ3000_5ity3zyu TS0121-6162eb5fd75c2a402a425d4a6e8da4d2.json

Logs
Logs
[Paste the logs here]

Custom quirk
Custom quirk
[Paste your custom quirk here]

Additional information
I'll gladly help testing out a new quirk to get this working for as many people as possible.

What is the manufacturer and model for the other switches that work?

They're all the same manufacturer and model.
Manufacturer is Connecte (now part of Futurehome)
Product nr.: Co017
It's registered in the norwegian "EFO database" with El.nr.: 4500993
Here is the signature of a working device:
{
  "node_descriptor": {
    "logical_type": 1,
    "complex_descriptor_available": 0,
    "user_descriptor_available": 0,
    "reserved": 0,
    "aps_flags": 0,
    "frequency_band": 8,
    "mac_capability_flags": 142,
    "manufacturer_code": 4098,
    "maximum_buffer_size": 82,
    "maximum_incoming_transfer_size": 82,
    "server_mask": 11264,
    "maximum_outgoing_transfer_size": 82,
    "descriptor_capability_field": 0
  },
  "endpoints": {
    "1": {
      "profile_id": "0x0104",
      "device_type": "0x0009",
      "input_clusters": [
        "0x0000",
        "0x0003",
        "0x0004",
        "0x0005",
        "0x0006",
        "0x0702",
        "0x0b04",
        "0xef00"
      ],
      "output_clusters": [
        "0x000a",
        "0x0019"
      ]
    },
    "242": {
      "profile_id": "0xa1e0",
      "device_type": "0x0061",
      "input_clusters": [],
      "output_clusters": [
        "0x0021"
      ]
    }
  },
  "manufacturer": "_TZ3000_5ity3zyu",
  "model": "TS0121",
  "class": "zhaquirks.tuya.ts0121_plug.TS0121_Var03"
}

If you get a chance, try this one and see if it works for you.
from zigpy.quirks import DEVICE_REGISTRY

try:
    del DEVICE_REGISTRY._registry_v2[("_TZ3000_5ity3zyu", "TS0121")]
except KeyError:
    pass

from zigpy.quirks.v2 import QuirkBuilder

from zhaquirks.tuya import (
    TuyaNewManufCluster,
    TuyaZBElectricalMeasurement,
    TuyaZBMeteringCluster,
    TuyaZBOnOffAttributeCluster,
)

(
    QuirkBuilder("_TZ3000_5ity3zyu", "TS0121")
    .replaces(TuyaZBOnOffAttributeCluster)
    .replaces(TuyaZBMeteringCluster)
    .replaces(TuyaZBElectricalMeasurement)
    .replaces(TuyaNewManufCluster)
    .add_to_registry()
)

Thanks a lot! I need to read up on how to apply a custom quirk.
Next week will be hectic, but after that I'll definetly have time.
I'll get back to you with results.

Okay, so I found time to figure out and try this new custom quirk, and it WORKS! 😁
Thank you so much for the help. Will it get merged in ZHA?

firmware is still reported as unknown, I will report if it shows up in a while.

Firmware is very hit and miss, I think out of my 80 devices only 2 are showing a firmware other than unknown. So, it may never show.
On the merging, the exiting quirks are odd, since they only match on the model and not the manufacturer. I have to discuss with @TheJulianJES on how we can proceed with this, since v2 quirks require both and I don't have a list of all possible manufacturers.


extension: Add Span::setTag for setting attributes in OTLP Tracer

Signed-off-by: Alex Ellis<EMAIL_ADDRESS>
Commit Message:  Add Span::setTag for setting attributes in OTLP Tracer
Additional Description: Adding attributes to the OTLP traces generated in the OTLP tracer (see https://github.com/envoyproxy/envoy/issues/9958).
Here's a sampling of the attributes Envoy creates in a basic test setup (Envoy making a child span for its call to the Nighthawk test server) by just adding this method:

Risk Level: low
Testing: Added a unit test (with fleshed out proto expectations)
Docs Changes: N/A
Part of #9958

/retest

/retest

Hi @htuch! When this auto-added you for review, I realized I added you for this extension under CODEOWNERS in the last PR without checking with you — happy to update that if you'd like, as I'm sure you get plenty of review requests already :)

@AlexanderEllis initial testing and it looks like this is working well. Fantastic! And thanks for working on this

Awesome, glad to hear it, and thanks for testing it out!

One thing I'm stuck on is the health check filter. I have a cluster health check on my front Envoy
                "health_checks": [
                    {
                        "always_log_health_check_failures": true,
                        "healthy_threshold": 2,
                        "http_health_check": {
                            "path": "/z/",
                            "codec_client_type": "HTTP2",
                            "service_name_matcher": {
                                "exact": "sync_service"
                            }
                        },
                        "interval": "5s",
                        "interval_jitter": "0.5s",
                        "timeout": "1s",
                        "unhealthy_threshold": 2
                    }
                ],

and then a health check filter on the upstream Envoy
                                        {
                                            "name": "envoy.filters.http.health_check",
                                            "typed_config": {
                                                "@type": "type.googleapis.com/envoy.extensions.filters.http.health_check.v3.HealthCheck",
                                                "headers": [
                                                    {
                                                        "name": ":path",
                                                        "string_match": {
                                                            "exact": "/z/"
                                                        }
                                                    }
                                                ],
                                                "pass_through_mode": false
                                            }
                                        },

But the OpenTelemetry Collector is still seeing and sending health checks with user_agent Envoy/HC.
Feels like this should be handled in the HCM. I'm pretty sure the filter worked when using the Lightstep tracer previously.
Any ideas?

LGTM, but we probably should have a non-Googler maintainer consistently reviewing these as well, @mattklein123 can you take a look at this short PR as you also reviewed the main OT extension?
I'm happy to remain CODEOWNERS, but it's possible @yanavlasov or someone else in our Envoy Platform team might take it if they have cycles.

@moderation Thanks for calling that out! Just to make sure I'm on the same page, you have your front Envoy health checking your upstream Envoy, and the OTel collector is not seeing the traces from that check with the right user agent? I'm going to be afk this week, but I should be able to dig in and try that setup out myself after the 4th 👍
@htuch Sounds great to me, thanks!

@moderation Should be all set with https://github.com/envoyproxy/envoy/pull/22047 merged in 👍 Thanks again for trying this out!


[Observer] Add VeChain support for BlockAPI

Added in https://github.com/trustwallet/blockatlas/pull/254


Computer Science Resource

I want to add some YouTube channels which will help Computer Science Students to gain knowledge and understand their topics easily.

Sure. You can go ahead


[RFC] Introduce a new ownership design for libtock_unittest.

Previously, libtock_unittest made use of thread local storage (as well as plentiful use of Rc) to support libtock_platform's asynchronous API traits smoothly. However, those traits were removed, allowing us to simplify libtock_unittest's design.
This PR deletes the previous design doc titled "Fake Kernel Ownership" and replaces it with a new document that presents a simpler, more-efficient design. I would like to refactor libtock_unittest to use this new design, as I believe it will decrease the maintenance burden. As a side benefit, it will improve the effectiveness of fuzzing (by making the tests execute faster) if we add fuzzing in the future.
Rendered

bors r+


Virtual IP (VIP) support for service

Feature flow:

Every service/loadBalancer service gets a VIP (Virtual IP) from the Link Local ip range (configurable)
On DNS update, we check if the host provides VIP service (internally we look up the VIP provider on the host). If there is not, DNS is configured the usual way. If there is, DNS is configured with the  :  A record.
In order for container to be registered as VIP service provider in cattle, it has to be configured with the label:

"io.rancher.network.services=vipService"
For services instances, the label has to be put on the service defined in *compose.yml file.
Each VIP provider can have its own way of implementing VIP service; the implementation details are unknown to Rancher.
@ibuildthecloud label supports specifying list of services. So in the future we can specify more than just a VIP if we decide to delegate more services to the external provider.

https://github.com/rancher/rancher/issues/1740

169.254.0.* and 169.254.255.* are reserved in the link-local RFC and should probably not be used. And we use <IP_ADDRESS>{0,4} ourselves.

@vincent99 thank you, Vince, will blacklist those

@ibuildthecloud schema file will get renamed after I address all the comments and make a final rebase with master


Missing flipper features for a brand new install

Some behaviour like subject uploading relies on flipper being setup and enabled Panoptes.flipper[:subject_uploading].enabled?. These features need to be pre-seeded or 'flipped' around to allow missing features to work.
This was initially reported in contact@ email from a user running their own system.

closed by #2962


Ideas from discussion

Something about modifying Docker so it uses ipfs instead of the layers.
Permissions

On Fri, Apr 17, 2015 at 03:03:06PM -0700, Ho-Sheng Hsiao wrote:

Permissions

Permissions are mostly in ipfs/go-ipfs#846, although that issue is
also getting deeper into trust issues that I don't think we need to
resolve yet.  We do need at least an executable mode in IPFS if we
want to run #22 directly from a FUSE mount.
Having a statically linked ipfs binary would also be nice 1.
@jbenet just pointed me at https://gobuilder.me/, so I'll see what it
spits out…

Get performance better so we can demo things without having pre-pinned assets.

Longer term down the nsinit path, it would be good to be able to use
Docker's bridging with nsinit.  I'm not sure how that's handled in
Docker, but the default nsinit config just sets up the loopback
interface.  If it's another stand-alone-ish library like libcontainer,
it could be pretty easy to recycle here.  If it's baked into
docker/docker, it will likely be harder to tease out.

On Fri, Apr 17, 2015 at 03:41:43PM -0700, Ho-Sheng Hsiao wrote:

Get performance better so we can demo things without having
pre-pinned assets.

Heh, yes ;).  And fix whatever reliability issues we were having
around @jbenet's VM :p.  Although towards the end I think most of the
issues where that my local IPFS daemon was serving assets over a slow
DSL link.

And symlink-support would be nice, it's a pain (for me anyway) to get
a statically linked ipfs, and Linux distros like to use symlinks like:
libc.so.6 -> libc-2.20.so
It's not hard to unwind those links, but it is an extra step if you're
going from a vanilla distro tarball to something you can store in
IPFS.

@wking I'm planning on having symlinks. Its on my todo heap

Let's use checkboxes for tracking todos.

[ ] symlinks (easy)
[ ] permissions on unixfs (metadata?) (easy)
[ ] getting exec to work from ipns inside a container (easy)
[ ] docker storage driver (medium)
[ ] docker with a different image format -- straight ipfs (hard)
[ ] perf issues
[ ] mounting on osx problems?
[ ] prepared built nsinit, etc. (may need multiple archs)

On Fri, Apr 17, 2015 at 05:39:48PM -0700, Juan Batiz-Benet wrote:

Let's use checkboxes for tracking todos.

I think it's easier (epecially for those of us following by mail, who
don't get updates when comments are updated) to use a separate issue
for each entry in your list, with a "demo" label (allows cross-repo
grouping [1]) or milestone (only inside one repo, but gives %
complete) to group them together.
Mechanics aside, the list looks good to me, except I think “perf
issues” and “docker with a different image format” are pretty fuzzy
;).
I'll ping the libcontainer folks about their build issues.

On Fri, Apr 17, 2015 at 07:10:26PM -0700, W. Trevor King wrote:

… (allows cross-repo grouping 1)…

Oops, forgot the reference:

@wking hm-- we use checkboxes a lot in various other repos. They're really useful to capture independent items to ensure are handled without yet having to do the work of making individual issues. Also, sometimes i edit my comments for correctness/clarity if i notice an error within a few min-- will this mess up your flow (happy to avoid it)?

On Sat, Apr 18, 2015 at 05:06:56AM -0700, Juan Batiz-Benet wrote:

we use checkboxes a lot in various other repos. They're really
useful to capture independent items to ensure are handled without
yet having to do the work of making individual issues.

New issues aren't that hard to make ;).  If you like the command
line, you can use ghi 1 and do:
$ ghi open -m 'Support symlinks'
Although I just installed ghi via:
$ gem install ghi
$ ghi config --auth wking
and bumped into 2, which I worked around by adding:
require 'socket'
to the top of my gem-installed
~/.gem/ruby/2.0.0/gems/ghi-0.9.3/lib/ghi/authorization.rb (after the
encoding comment).

Also, sometimes i edit my comments for correctness/clarity if i
notice an error within a few min--

Usually errors that you miss with the first version aren't terribly
serious, so I'm fine missing out on them.

… will this mess up your flow (happy to avoid it)?

If checkboxes are easier for you, I'll handle working with them.  But
my personal preference for anything distinct enough for a checkbox is
to open a new issue.


[PDCL-6220] - Single identity:result handle retured on consent update

Description

A bug which caused to have two identity:result handles returned was fixed in the Edge Gateway.
Related Issue

Motivation and Context

Updated tests to expect a single identity:result handle and further validate its content.
Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (non-breaking change which does not add functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA or I'm an Adobe employee.
[x] I have made any necessary test changes and all tests pass.
[x] I have run the Sandbox successfully.

@jfkhoury , @shammowla This PR fixes tests, which started to fail once a bug was fixed in EE Gateway.
Looking through history, I see that test expectations were changed to match the returned response when the bug was first introduced -- not sure if we talked about this at that time, but we should definitely discuss such problems going forward.


belindas-closet-nextjs-99-fix-nestjs-templates

resolves #99
This PR addresses the following:

Deletes pull_request.md in .github/ISSUE_TEMPLATE folder.
Creates pull_request_template.md in .github folder.
Adds user story and issue titles to front matter for user story and issue templates.

I modified this existing PR to instead achieve the goal of deleting all templates. They've all been added to the .github repo where they can be centrally managed for all repos.


Tachiyomi

Source information
https://raw.githubusercontent.com/keiyoushi/extensions/repo/index.min.json
Source language
All
Source new URL
https://raw.githubusercontent.com/keiyoushi/extensions/repo/index.min.json
Other details
https://github.com/Elbia00/Elbia.git
Acknowledgements

[X] I have updated all installed extensions.
[X] I have opened WebView and checked that the source URL has not changed yet.
[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have admitted that I am a clown by having checked this box, as I have not read these acknowledgements.
[X] I will fill out all of the requested information in this form.

You're asking us to change the link to the same link and give you credit?


[1.21] Crash when attempting to encode fluid recipes in AE2

Version: emi-1.1.7+1.21+neoforge
Crash logs and more relevant information in the link below.
https://github.com/AppliedEnergistics/Applied-Energistics-2/issues/7956

Seems to be specific to ae2's implementation in that issue.


@zeit/next-css: Remove minimize option

The minimize option has been removed in css-loader 1.0.0 which is now used ( 91bf70af7d9e042aafc3c2824665c01e76078abe).
To avoid confusion (there is currently no minification) we should remove the line in https://github.com/zeit/next-plugins/blob/2db666d9adf96bb16532caf5048b7b44e115222d/packages/next-css/css-loader-config.js#L76

Feel free to send a pull-request.

I found it very convenient that next-css automatically minified the CSS. Can we get that back?

Looking for some clarification, does a postcss.config.js need to be present for postcss-loader to be included? Or can we just config it in next.config's postcssLoaderOptions?
The readme says You can also pass a list of options to the postcss-loader by passing an object called postcssLoaderOptions.
But lines 49-68 in css-loader-config.js only handles the case when postcss.config.js file is present.

#327 solves the automatically minimizing

Hey guys,
the minimize option is still on the npm version of this plugin which causes build error on pnpm

The file on the repo is different

Invalid options seems to be ignored by npm and yarn because project builds fine. Any input on this would be appreciated.

Next.js has built-in support for css and sass: https://nextjs.org/docs/basic-features/built-in-css-support we recommend using the built-in support which solves numerous edge cases and adds additional optimizations

Next.js has built-in support for css and sass: https://nextjs.org/docs/basic-features/built-in-css-support we recommend using the built-in support which solves numerous edge cases and adds additional optimizations

when i removed @zeit/next-css from next.config.js and package.json, thereby moving to the built-in CSS support upon upgrading to 9.2.0
I started getting this loader error.

1:0\nModule parse failed: Unexpected character '@' (1:0)\nYou may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders\n> @font-face{font-family:"sofia-pro";src:url("https://use.typekit.net/af/5855b2/00000000000000003b9b1a98/27/l?subset_id=2&fvd=n4&v=3") format("woff2"),url("https://use.typekit.net/af/5855b2/00000000000000003b9b1a98/27/d?subset_id=2&fvd=n4&v=3") format("woff"),url("https://use.typekit.net/af/5855b2/00000000000000003b9b1a98/27/a?subset_id=2&fvd=n4&v=3") format("opentype");font-style:normal;font-weight:400;font-display:swap}@font-face{font-family:'FontAwesome';src:url('https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts//fontawesome-webfont.eot?v=4.7.0\');src:url(\'https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts//fontawesome-webfont.eot?#iefix&v=4.7.0\') format('embedded-opentype'),url('https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts//fontawesome-webfont.woff2?v=4.7.0\') format('woff2'),url('https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts//fontawesome-webfont.woff?v=4.7.0\') format('woff'),url('https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts//fontawesome-webfont.ttf?v=4.7.0\') format('truetype'),url('https://cdnjs.cloudflare.com/ajax/libs/font-awesome/4.7.0/fonts//fontawesome-webfont.svg?v=4.7.0#fontawesomeregular\') ...


chore: replaced virgin inspect.iscoroutinefunction with chad asyncio.iscoroutinefunction

Summary
Replaced all occurrences of inspect.iscoroutinefunction with the slightly more truthy asyncio.iscoroutinefunction.
Checklist

[x] If code changes were made, then they have been tested

[ ] I have updated the documentation to reflect the changes
[x] I have formatted the code properly by running task lint
[x] I have type-checked the code by running task pyright

[ ] This PR fixes an issue
[ ] This PR adds something new (e.g. new method or parameters)
[ ] This PR is a breaking change (e.g. methods or parameters removed/renamed)
[ ] This PR is not a code change (e.g. documentation, README, ...)

🗿


In appendix A, add | as alternative for disjunction ("or")

Please modify Appendix A to add "|"
as an alternative symbol for disjunction ("or"), both in the discussion about "or" and in
the following summary table.
This is used. For example, prover9 uses "|" for "or", "&" for "and", and so on,
as documented here:
https://www.cs.unm.edu/~mccune/prover9/manual/2009-11A/syntax.html
Thanks so much!

Fixed in 33bdea908cbc772a1f18d2814c1200b8cb44cf4b, thanks!


Termination for SCPI commands

When I executed VXI11 example, and connected over some VXI11 client codes, we get to know that the commands only work with the termination \n\r. So, is there any simple way to avoid this, and work without this termination characters?
Without termination, on the server code, it is showing the below error.
double free or corruption (out)
Aborted

I suggest to check the parameter:  SCPI_LINE_ENDING  and file scpi_user_config.h.
for compile the file scpi_user_config.h, you need to add:
add_definitions(-DSCPI_USER_CONFIG=1)
on CMakelists.txt
Warning: I'm just a user of the scpi parser software and not a devellopper

+1 for scpi_user_config.h, which is included in config.h to supersede:
https://github.com/j123b567/scpi-parser/blob/224f7cee7c2c5592081e1dec640862f029323782/libscpi/inc/scpi/config.h#L57

You might consider using a flexible/dynamic definition of SCPI_LINE_ENDING similar to how Keysight is handling it in their Keysight B2980B Series Femto/Picoammeter Electrometer/High Resistance Meter:
When parsing commands:

Message Terminator
A terminator informs SCPI that it has reached the end of a message. The following
message terminators are permitted.

newline , expressed in ASCII as decimal 10 or hex 0A
end or identify  (EOI with ATN false)
both of the above
also

... although I would recommend ignoring <END>, leaving <NL> and <CR><NL>, only.
When returning results:

Data Output Format
A terminator  (0x0a, 1 byte) is attached to the end of each data.


setcdr: Symbol's value as variable is void: stack

You have a typo at the end of history-add-history-internal.

Hehe, just fixed it. Thanks~
https://github.com/boyw165/history/commit/fff501f68768a613b3dcfb48ade24a707f78407e

Thank you.


Update validateBpayCRN

Hey,
Good work with a simple CRN generator. I see your validation function forces 10 digits, but the spec allows 2-20. This PR fixes that.
Fix from forcing 10 digit length to accepting 2-20 digit length.
Thanks,
Lucas.

Thanks for this Lucas! I'll push a new version out with this update now.


fix: duplicate names of tables handling

Duplicate name handling - https://github.com/open-contracting/spoonbill/issues/43

moved to https://github.com/open-contracting/spoonbill/pull/93


Resizeable support for multiple images

This will allow us to pass any image path and generate the thumbnail using get_thumbnail. This is useful when using it inside of multiple images array / input type. For example:
@foreach($posts as $post)
    @foreach($post->images as $image)
        <img src="{{Voyager::image($post->get_thumbnail($image, 'small'))}}" />
    @endforeach
@endforeach

If you are using multiple images input type, you can optional cast your images attribute
use TCG\Voyager\Traits\Resizable;

class Post extends Model
{
    use Resizable;

    protected $casts = [
        'images' => 'array',
    ];
}

I made new PR #3288. Close this one


Remove needless scriptElement.async = true

See https://mathiasbynens.be/notes/async-analytics-snippet#async.

@ebidel - can you take a peek? If it looks good, please approve and assign to me.

Yea not needed but I always do it for good measure. Lgtm


Firebase crash: RejectedExecutionException Compose

Hello, we saw a couple of crashes on Firebase related with DevCycle code.
We suppose that the method that is crashing is: dvcClient.variable(...) bc its the only method we use
We are using:

devCycle = 1.4.2
compose = 1.2.1

Fatal Exception: java.util.concurrent.RejectedExecutionException: Task androidx.activity.d@52492b rejected from java.util.concurrent.ThreadPoolExecutor@7967188[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 0]        at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2085)        at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:848)        at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1394)        at java.util.concurrent.Executors$DelegatedExecutorService.execute(Executors.java:624)        at com.devcycle.sdk.android.eventsource.EventSource.start(EventSource.java:52)        at com.devcycle.sdk.android.api.DVCClient.initEventSource(DVCClient.java:66)        at com.devcycle.sdk.android.api.DVCClient.access$initEventSource(DVCClient.java)        at com.devcycle.sdk.android.api.DVCClient$onResumeApplication$1$1$1.invokeSuspend(:31)        at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(BaseContinuationImpl.java:8)        at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.java:86)        at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.java:12)        at kotlinx.coroutines.scheduling.TaskImpl.run(TaskImpl.java:2)        at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.java:9)        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.java:9)        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.java:9)        at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.java:9)

Hey @emi-net21, thanks for creating this issue!
Couple of additional questions I have for you / your team:

Do you use realtime updates on the DevCycle Android SDK?
Does your app use coroutines / threads?

We'll start investigating on our end to see if we can reproduce this issue. Looking forward to hearing from you!

1-2: Yes, coroutines = "1.6.4"
Example we use:
override suspend fun checkVariable(): Flow<Boolean> {         return withContext(ioDispatcher) {             val variable =                 dvcClient.variable(KEY, false)             callbackFlow {                 trySend(                     variable                 )                 variable {                     trySend(it.value)                 }                 awaitClose()             }         }     }
Just to mentioned, we could not reproduce the crash, but saw a couple of them on Firebase Crashalitycs

Awesome, thanks for the info! We're looking at adding some checks to make sure that an Executor is available before we establish our Realtime updates connection. Aiming to have that published sometime next week that should mitigate this issue.

Hello @kaushalkapasi I also saw a lot of crashes on Firebase related to DevCycle code with above mention Exception.
Any update?

Hey @vinodkumarsagitla, we have a PR ready! Just doing some internal testing before we publish a release! Are you able to share any more information about the crashes that you are seeing?

@kaushalkapasi We are unable to reproduce this crash but saw lots of crashes on Firebase Crashalitycs.
We are using:
devCycle = 1.4.2
coroutines = 1.6.4

@emi-net21 & @vinodkumarsagitla we've released a new version of the Android SDK (1.4.4) that has a fix for this issue.
If you could test it out and let us know if it eliminates / reduces the number of crashes you are seeing then we can go ahead and resolve this issue!
Sorry for the delay on getting this out, appreciate your patience!

Hey @vinodkumarsagitla, just wanted to check in to ensure we can close this issue

Hello @VicV, I am still waiting because my client have not release build yet after version update of DevCycle. I will inform you as soon as when my app is live.

Hello @VicV  After new release we are unable to reproduce this crash but saw lots of crashes on Firebase Crashalitycs.
See below screen shot:
https://www.dropbox.com/s/lsh3crqyl2bxtyh/1.png?dl=0
https://www.dropbox.com/s/vjkv8p5fpw47o6v/2.png?dl=0

HI @vinodkumarsagitla apologies, your follow-up went under our radar. Last you ran this, were you still seeing crashes on Firebase Crashlytics?

Closing this issue due to being unreproducible, please feel free to reopen with any further information if it's still happening


Adding links to Java samples

Added links to the java samples repository as part of the developer guide page

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

#label:"aq-pr-triaged"

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

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

#sign-off


Squiggly not working with @JsonProperty

I am trying to serialize a bean with fields having @JsonProperty, but it is not coming in response.
Example:
Model:
    @Data
    class MyModel {
        private String data;
        @JsonProperty("errors")
        private String error;
    }

Response:
     {
         "data":"MyData"
     }

Expected response:
    {
        "data":"MyData",
        "errors": "My errors"
    }

On digging through squiggly code, I found SquigglyPropertyFilter.getPropertyName is using beanIntrospector to get the property names and comparing it with the element name which is constructed through BeanPropertyWriter which respects the @JsonProperty.

Seems to work for me.  I noticed that you are using Lombock, so maybe it has something to do with that?
import com.fasterxml.jackson.annotation.JsonProperty;
import com.fasterxml.jackson.databind.ObjectMapper;
import com.github.bohnman.squiggly.Squiggly;

import java.io.IOException;

public class Test {

    public static void main(String[] args) throws IOException {
        ObjectMapper mapper = Squiggly.init(new ObjectMapper(), "data,errors");
        mapper.writeValue(System.out, new MyModel());

    }

    public static class MyModel {
        private String data =  "My Data";

        @JsonProperty("errors")
        private String error = "My errors";

        public String getData() {
            return data;
        }

        public void setData(String data) {
            this.data = data;
        }

        public String getError() {
            return error;
        }

        public void setError(String error) {
            this.error = error;
        }
    }
}

@bohnman Thanks for your reply. Lombok doesn't seem to be a problem here. It is working with Lombok as well.
I missed to specify some of the configurations. I am using spring boot with following properties:
squiggly.properties:
filter.implicitlyIncludeBaseFields=true
filter.propagateViewToNestedFilters=true
property.addNonAnnotatedFieldsToBaseView=true

Squiggly configuration
@Bean
	public FilterRegistrationBean squiggyRequestFilter() {
		FilterRegistrationBean filter = new FilterRegistrationBean();
		filter.setFilter(new SquigglyRequestFilter());
		filter.setOrder(1);
		return filter;
	}

	@PostConstruct
	public void init() {
		Squiggly.init(objectMapper, new RequestSquigglyContextProvider("fields", "base") {

			@Override
			protected String customizeFilter(String filter, HttpServletRequest request, Class beanClass) {
				if (filter != null && MyModel.class.isAssignableFrom(beanClass)) {
					filter = "data." + filter + "";
				}

				return filter;
			}

		});
	}

I have not specified any filter or fields in url.
I will debug this further.
Also, there was another nested field where this was not working on debugging, it turned out that @JsonProperty specified in constructor property is not being used. The model looks like this:
public final class Form {
    @NotNull
    private final FormInput myForm;
    @NotNull
    private final String actionUrl;

    @NotNull
    public final FormInput getmyForm() {
       return this.myForm;
    }

    @NotNull   public Form(@JsonProperty("form") @NotNull FormInput myForm, @NotNull String actionUrl) {      Intrinsics.checkParameterIsNotNull(myForm, "myForm");      Intrinsics.checkParameterIsNotNull(actionUrl, "actionUrl");      super();   public final String getActionUrl() {
       this.myForm = myForm;      this.actionUrl = actionUrl;   }
       return this.actionUrl;
    }

    @NotNull
    public final FormInput component1() {
       return this.myForm;
    }

    @NotNull
    public final String component2() {
       return this.actionUrl;
    }

    @NotNull
    public final Form copy(@JsonProperty("form") @NotNull FormInput myForm, @NotNull String actionUrl) {
       Intrinsics.checkParameterIsNotNull(myForm, "myForm");
       Intrinsics.checkParameterIsNotNull(actionUrl, "actionUrl");
       return new myForm(myForm, actionUrl);
    }

    public String toString() {
       return "Form(myForm=" + this.myForm + ", actionUrl=" + this.actionUrl + ")";
    }

    public int hashCode() {
       return (this.myForm != null?this.myForm.hashCode():0) * 31 + (this.actionUrl != null?this.actionUrl.hashCode():0);
    }

    public boolean equals(Object arg0) {
       if(this != arg0) {
          if(arg0 instanceof myForm) {
             Form arg1 = (Form)arg0;
             if(Intrinsics.areEqual(this.myForm, arg1.myForm) && Intrinsics.areEqual(this.actionUrl, arg1.actionUrl)) {
                return true;
             }
          }

          return false;
       } else {
          return true;
       }
    }
 }

Here, myForm/form field is not coming in json output.

@sahebpreet
Here's the problem line in your code:
if (filter != null && MyModel.class.isAssignableFrom(beanClass)) {
    filter = "data." + filter + "";
}

Here you are prefixing the filter with "data.", which means you would only every be including the data field.  If you want to include other fields you, can do something like the following:
if (filter != null && MyModel.class.isAssignableFrom(beanClass)) {
    filter = "**,data." + filter + "";
}

Squiggly currently doesn't support JsonProperty in the constructor.  I'll will add a separate issue to track this.

Thanks a lot @bohnman it is working now.


sketching out a community & patch-based approach for adding extra features

I think it would be beneficial to have some kind of official and documented way of adding "extensions" or "patches" to startingpoint-based images / repos.
Having the scripts functionality, it would be entirely possible to boostrap that for such a feature. The scripts already have access to the recipe (where they could read their configuration, maybe from under a separate namespace like unofficial:).
It would be pretty easy to have a system where; Oh you want libvirt and virt-manager? Well this guy maintains a set of packages for that that you can just pull in like this.
The question is, what is the mechanism for pulling it in. There could be an extra option, like extrarepos: that just downloads scripts for you, or the scripts could just be added manually.

We have ublue-os/bling now, where extra "bling" should be added and maintained, then pulled in here. Possible community endeavours would probably go via a similar route, COPYing stuff between containerfiles, RPMs, and so forth. Scripts can easily add new sections to recipe.yml, and scripts can be easily COPYed around.


sqlite3 support added

Note that MySQL and SQLite are completely different systems.

Good point. I didn't notice the naming discrepancy. We should probably change MySQLLoader to SQLiteLoader.

Great catch. I had started adding a MySQL loader, but later realized a SQLite was the better fit. This must've been stuck from then. Thanks


About permission lacking of config's parent dir

> rathole -V
rathole 0.4.7

Describe the bug
This occurs when I try to start rathole with systemd, It failed to start unexpectedly and has no valid debug information about it:
> journalctl -f -u rathole.service
Mar 16 14:34:09 host systemd[1]: Stopped rathole Daemon.
Mar 16 14:34:09 host systemd[1]: rathole.service: Consumed 12ms CPU time, received 960B IP traffic, sent 9.7K IP traffic.
Mar 16 14:34:09 host systemd[1]: Started rathole Daemon.
Mar 16 14:34:09 host rathole[99122]: Mar 16 14:34:09.370  INFO handle{service=example}: rathole::client: Starting <omitted>
Mar 16 14:34:09 host systemd[1]: rathole.service: Deactivated successfully.

To Reproduce
Steps to reproduce the behavior:

Create config dir config, with permission 751 owned by user B.
Start rathole with config file which with full permission and owned by user A, in config dir.

Run rathole by user A:
> RUST_LOG=trace rathole --client config/test.toml
...
Mar 16 14:41:59.500 TRACE config_watcher{path="config/test.toml"}: mio::poll: registering event source with poller: token=Token(0), interests=READABLE
Mar 16 14:41:59.501  INFO handle{service=ssh_tcp}: rathole::client: Starting <omitted>
Mar 16 14:41:59.501 TRACE mio::poll: deregistering event source from poller

It exits directly, without reporting any available information related to permission lacking.
Bcz I found this, seems rathole needs read permission of the parent directory?
https://github.com/rapiz1/rathole/blob/9479b9a3a9c426a9ee04175cbd747b49a520d497/src/config_watcher.rs#L165
Is there a way to implement hot-reload without this permission? Or at least report some error messages about the permission lacking...
Environment:
> uname -srm
Linux 6.2.5 x86_64

This is introduced by https://github.com/rapiz1/rathole/pull/122
In short, if only the file is watched, then sometimes vim does not trigger a inotify event.
Can you make a directory seperately for rathole config and set the corresponding permission?