The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.

Hi team,
I have spent a lot of time to solve the problem and also spent a lot of time to search the solution on net but every time I failed. The scenario is that
I am using @google-cloud/storage to upload my image on google cloud storage. Everything is fine. Images successfully uploaded on cloud. Now I want to show these images to my users but I didn't want to give public permission to images. So I created a signed url and trying to download them but everytime I am facing the following problem
<Error>
SignatureDoesNotMatch
<Message>
The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.
</Message>
<StringToSign>GET<PHONE_NUMBER> /<my bucket name>/<my image name></StringToSign>
</Error>

here is my code
//get signed url
    action: 'read',
        expires: Date.now() + 76000000,
        contentType: 'image/jpeg'
    };
    var file = bucket.file('TestingImage.jpg').getSignedUrl(options, function (error, signedUrl) {
        console.log('signed url...');
        console.log(signedUrl);
    });

But when I put this signed url in browser it give me the error.
I am following the url for uploading image
https://googlecloudplatform.github.io/google-cloud-node/#/docs/storage/0.6.0/storage
How ever I can download these image in nodejs using file.download() but I want to view this image on browser
Please guide me when am I wrong.

The browser will need to set the matching Content Type on the request headers.

As needed. If you provide a content-type, the client (browser) must provide this HTTP header set to the same value.
- https://cloud.google.com/storage/docs/access-control/signed-urls

If you remove the content type while creating the signed URL, it should work in the browser.

Thanks a lot

Hi ,
I am using latest 'aws-java-sdk-s3', version: '1.11.158'.  I am getting below error when uploading the files. I am able to list the buckets.  Is there any signature setting I have do.?
The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method.
com.amazonaws.services.s3.model.AmazonS3Exception: The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method. (Service: Amazon S3; Status Code: 403; Error Code: SignatureDoesNotMatch; Request ID: null), S3 Extended Request ID: null

Hi, there!
I'm facing the same problem but I've already removed the content type while creating the signed URL.
The interesting fact is that this problem only happens suddenly a few days after the signed URL is created..
The code I'm following is the one below:
https://github.com/firebase/functions-samples/blob/master/generate-thumbnail/functions/index.js
Thanks in advance!

I notice the example code sets the expiration date for 482 years from now, so that's probably not the issue :) (Unless-- did you change it?)
Assuming that's not the case, I'm not sure what it could be. Could you open a new issue on the https://github.com/firebase/functions-samples repo? If it turns out to be a problem with our library, we can continue to look at it and see what we can do.

I'm getting the same error. I do not pass content-type to signer method. Do I need to set some special permissions on the bucket maybe, have an ACL or something? Service Account that is used to sign urls has Storage Admin role.

Same as @jayarjo here.
Also, the file I'm trying to access have a name like Customers/{id}/kitten.jpeg. I use all this name to get my signedUrl, and not only kitten.jpeg (makes sense to me).
Is there any further explanations here ?

Can someone provide solution for this. URL worked for few days after geenration now suddenly my android app is not able to download image and it fails with "HttpException: Invalid statusCode: 403,".  From browser it gives  below error
This XML file does not appear to have any style information associated with it. The document tree is shown below. <Error> SignatureDoesNotMatch <Message> The request signature we calculated does not match the signature you provided. Check your Google secret key and signing method. </Message> <StringToSign> GET<PHONE_NUMBER>0 /wmiefy-577a4.appspot.com/images/thumb_5e83f485-656d-45b5-8c40-47b11453e1965771333569762950312.jpg </StringToSign> </Error>

Have the same problem :)
`export async function storeFileInStorage(filename: string, objectId: string, fileType: FileType, base64Content: Buffer, objectType: string): Promise {
const folderName = objectType === "PROFILE" ? profiles : agreements;
const bucket = admin.storage().bucket();
const fileAsByteArray = new Uint8Array(base64Content);
const bucketFilename = folderName + '/' + objectId + '/' + fileType + "_" + filename;
const file = bucket.file(bucketFilename);
let publicUrl;
await file.save(fileAsByteArray)
.then(async stuff => {
publicUrl = await file.getSignedUrl({
action: 'read',
expires: '05-09-2999'
});
}).catch(err => {
throw Error(Could not store file for objectId: ${objectId} with to ${bucketFilename} error: ${err});
});
return {publicUrl: publicUrl ?? "", storagePath: bucketFilename, type: fileType};
}`
For example url

Greetings folks!  If you're having issues, please open a new issue here:
https://github.com/googleapis/nodejs-storage/

For me it was because I was using POST instead of PUT, it's not just about the ContentType header, the http method has has to match, in golang:
	         	method := "PUT"   // THIS MUST MATCH
			expires := time.Now().Add(time.Minute * 10)

			url, err := storage.SignedURL(bucket, filename, &storage.SignedURLOptions{
				GoogleAccessID: cfg.Email,
				PrivateKey:     cfg.PrivateKey,
				Method:         method,
				Expires:        expires,
				ContentType:    "binary/octet-stream",   // NOTE
			})

			if err != nil {
			      // ...
			}

			var client = http.DefaultClient
			request, err := http.NewRequest("PUT", url, req.Body)  // we use PUT not POST

			if err != nil {
				// ....
			}

			request.Header.Set("Content-Type", "binary/octet-stream")  // this must match
			response, err := client.Do(request)

If anyone ever encounters this error again, in my case the key had an expiry date and it had expired. Generating a new key worked

I am having the same issue today: we're the 9th of August 2023, and here are the parameters: X-Goog-Date=20230803T154108Z&X-Goog-Expires=604800
The link should be valid until the 10th, but somehow I am getting Access Denied with SignatureDoesNotMatch.
For some reasons this link was working for a few days and now stopped working before expiration date.
I am generating the link using firebase admin in a Cloud run environment:
        const thumbnailUrlExpiresAt = new Date(Date.now() + 604800000); // 7 days
        const [signedUrl] = await firebase
          .storage()
          .bucket(process.env.BUCKET_VIDEO_THUMBNAILS)
          .file(lastExport.thumbnailData?.thumbnailPath)
          .getSignedUrl({
            version: 'v4',
            action: 'read',
            expires: thumbnailUrlExpiresAt
          });

What is actually going on here?

@jayarjo @JustinBeckwith @stephenplusplus @schankam
I have the same issue
index.js
const { onRequest } = require('firebase-functions/v2/https');
const webhookHandler = require('./webhook');
const getTransactionDetails = require('./getTransactionDetails');

exports.webhookHandler = onRequest(webhookHandler);
exports.getTransactionDetails = onRequest(getTransactionDetails);

webhook.js
const getFirebaseApp = require('./firebaseConfig');
const { getFirestore } = require('firebase-admin/firestore');
const { onRequest } = require('firebase-functions/v2/https');

const firebaseApp = getFirebaseApp();

exports.saveTransactionDetails = onRequest(async (req, res) => {
  try {
    console.log(req);
    console.log('req body is', req.body);
    const total = parseFloat(req.body.total) || 0;
    const counter = parseInt(req.body.counter) || 0;

    const db = getFirestore();
    const totalsRef = db.collection('totals').doc('total');
    const totalsDoc = await totalsRef.get();

    if (totalsDoc.exists) {
      const totalsData = totalsDoc.data();
      const newTotal = totalsData.total + total;
      const newCounter = totalsData.counter + counter;

      await totalsRef.update({
        total: newTotal,
        counter: newCounter
      });
    } else {
      await totalsRef.set({
        total,
        counter
      });
    }

    res.status(200).json({ message: 'Transaction details saved successfully' });
  } catch (error) {
    res.status(500).json({ message: 'Failed to save transaction details' });
  }
});

getTransactionDetails.js
const getFirebaseApp = require('./firebaseConfig');
const { getFirestore } = require('firebase-admin/firestore');
const { onRequest } = require('firebase-functions/v2/https');

const firebaseApp = getFirebaseApp();

exports.getTransactionDetails = onRequest(async (req, res) => {
  try {
    const db = getFirestore();
    const totalsRef = db.collection('totals').doc('total');
    const totalsDoc = await totalsRef.get();

    if (totalsDoc.exists) {
      const totalsData = totalsDoc.data();
      res.status(200).json({ total: totalsData.total, counter: totalsData.counter });
    } else {
      res.status(404).json({ message: 'Transaction details not found' });
    }
  } catch (error) {
    res.status(500).json({ message: 'Failed to retrieve transaction details' });
  }
});

Firebaseconfig.js
const { initializeApp } = require('firebase-admin/app');

let firebaseApp;

function getFirebaseApp() {
  if (!firebaseApp) {
    firebaseApp = initializeApp();
  }
  return firebaseApp;
}

module.exports = getFirebaseApp;


Playback of cdng coming from MLV files

Tested on Mac OS Monterey 12.2.1
Files seems to play in correct order and in realtime. However preview is completely green.
Since we are at it. Eos m and other digic V canon cameras can manipulate pixels to achieve a better output. For instance 1x3 pixel modification which creates a very anamorphic output needs to be corrected. This could be done by addressing the default scale tag in cdng metadata. Only program I know atm using this tag is adobe camera raw.
Anyway. Not sure how deep you are willing to go around these files but a good looking preview would be nice to have to start with. I´ll provide a few sequences here.
M10-0942_1_2022-11-10_0001_C0000.zip
M10-0941_1_2022-11-10_0001_C0000.zip
M10-0938_1_2022-11-10_0001_C0000.zip

Thanks for sharing those. We've fixed the green issue - a colour maths bug with DNGs with forward matrices. It should make it into the next minor release which will be next week.
Implementing the scale tag looks like not a massive task - we'll try to schedule it in.

Nice one 👌

Green MLV fixed and default scale tag implemented for 1.0.3 release

Sounds good. I´ll await the release.


IMDB experiments preference pair generation

In the controlled sentiment generation part, it is mentioned that you generate preference pairs over generation with a pre-trained sentiment classifier. I see an earlier issue earlier where the sentiment classifier is mentioned, however, what model is actually used to perform the text completion for generating the preference pairs?
Thank you very much in advance!

This is a fine-tuned GPT-2-large model; you can find the weights here.


"Tasks" panel displays multiple instances of the same FrostingTask if it uses a "partial" definition.

The "Tasks" panel for the Cake Build extension will display the same task multiple times in the list if the FrostingTask definition uses partial.
The amount of times that it displays the same task in the "Tasks" panel depends on how many separate .cs files are in the project that define partial for the same class.

@nils-a thank you for the fix! I'm sorry that I didn't get around to trying it from your feature branch.


Error: cutlassF: no kernel found to launch

Encounter an error while trying to run Vicuna model:
`
:~/workspace/lit-gpt$ python chat/base.py --checkpoint_dir checkpoints/lmsys/vicuna-7b-v1.3
Loading model 'checkpoints/lmsys/vicuna-7b-v1.3/lit_model.pth' with {'org': 'lmsys', 'name': 'vicuna-7b-v1.3', 'block_size': 2048, 'vocab_size': 32000, 'padding_multiple': 64, 'padded_vocab_size': 32000, 'n_layer': 32, 'n_head': 32, 'n_embd': 4096, 'rotary_percentage': 1.0, 'parallel_residual': False, 'bias': False, 'n_query_groups': 32, 'shared_attention_norm': False, '_norm_class': 'RMSNorm', 'norm_eps': 1e-06, '_mlp_class': 'LLaMAMLP', 'intermediate_size': 11008, 'condense_ratio': 1}

Prompt: how is the weather?
Reply: Traceback (most recent call last):
File "/home/jovyan/workspace/lit-gpt/chat/base.py", line 302, in
CLI(main)
File "/opt/saturncloud/envs/saturn/lib/python3.9/site-packages/jsonargparse/_cli.py", line 85, in CLI
return _run_component(component, cfg_init)
File "/opt/saturncloud/envs/saturn/lib/python3.9/site-packages/jsonargparse/_cli.py", line 147, in _run_component
return component(**cfg)
File "/home/jovyan/workspace/lit-gpt/chat/base.py", line 190, in main
tokens_generated = decode(fabric, tokenizer, y)
File "/home/jovyan/workspace/lit-gpt/chat/base.py", line 109, in decode
for token in token_stream:
File "/opt/saturncloud/envs/saturn/lib/python3.9/site-packages/torch/utils/_contextlib.py", line 35, in generator_context
response = gen.send(None)
File "/home/jovyan/workspace/lit-gpt/chat/base.py", line 61, in generate
logits = model(idx.view(1, -1), max_seq_length, input_pos)
File "/opt/saturncloud/envs/saturn/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/opt/saturncloud/envs/saturn/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/opt/saturncloud/envs/saturn/lib/python3.9/site-packages/lightning/fabric/wrappers.py", line 116, in forward
output = self._forward_module(*args, **kwargs)
File "/opt/saturncloud/envs/saturn/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/opt/saturncloud/envs/saturn/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/home/jovyan/workspace/lit-gpt/lit_gpt/model.py", line 107, in forward
x, self.kv_caches[i] = block(x, (cos, sin), max_seq_length, mask, input_pos, self.kv_caches[i])
File "/opt/saturncloud/envs/saturn/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/opt/saturncloud/envs/saturn/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/home/jovyan/workspace/lit-gpt/lit_gpt/model.py", line 168, in forward
h, new_kv_cache = self.attn(n_1, rope, max_seq_length, mask, input_pos, kv_cache)
File "/opt/saturncloud/envs/saturn/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1518, in _wrapped_call_impl
return self._call_impl(*args, **kwargs)
File "/opt/saturncloud/envs/saturn/lib/python3.9/site-packages/torch/nn/modules/module.py", line 1527, in _call_impl
return forward_call(*args, **kwargs)
File "/home/jovyan/workspace/lit-gpt/lit_gpt/model.py", line 247, in forward
y = self.scaled_dot_product_attention(q, k, v, mask=mask)
File "/home/jovyan/workspace/lit-gpt/lit_gpt/model.py", line 273, in scaled_dot_product_attention
return torch.nn.functional.scaled_dot_product_attention(
RuntimeError: cutlassF: no kernel found to launch!`

Maybe is related to some installation issue?
ERROR: pip's dependency resolver does not currently take into account all the packages that are installed. This behaviour is the source of the following dependency conflicts. s3fs 2022.3.0 requires fsspec==2022.3.0, but you have fsspec 2023.6.0 which is incompatible.

Same problem here. Strictly followed the installation steps in a fresh conda env with Python 3.10. The error occurs in chat/base.py aswell as generate/base.py and across models.
 I think it's an issue in PyTorch itself as we are installing the latest nightly version.
We need a nightly because torch 2.1 (which is not yet out) contains desired functionality (like flash attention if I'm not mistaken).
As a quick fix try to install previous versions of PyTorch nightly:
pip install --index-url https://download.pytorch.org/whl/nightly/cu118 --pre 'torch==2.1.0.dev20230703'

This is the version that is installed on my machine. Or you can try a different one (as you can see the version is a date).
@carmocca @awaelchli  I think it should be addressed. Blindly relying on a nightly version is not a good thing in my opinion.

Do we have a solution for this?
Had this error today with the Llama 2 model: https://github.com/Lightning-AI/lit-gpt/issues/354

In my environment, set
torch.backends.cuda.enable_mem_efficient_sdp(False)
in addition to
torch.backends.cuda.enable_flash_sdp(False)
improved situation.

https://github.com/pytorch/pytorch/issues/102029#issuecomment-1560071148 suggests that it is related to using bf16 precision. Can somebody try precision 32?

With bf16 it works without raising that error. The problem is that the code tries to use bf16 even with Nvidia T4 which doesn't support it.
On A10G chat works without errors, but the quality of the generated text has dropped significantly:
main ~/repos/lit-gpt python chat/base.py --checkpoint_dir checkpoints/EleutherAI/pythia-410m --precision bf16-true
Loading model 'checkpoints/EleutherAI/pythia-410m/lit_model.pth' with {'org': 'EleutherAI', 'name': 'pythia-410m', 'block_size': 2048, 'vocab_size': 50254, 'padding_multiple': 128, 'padded_vocab_size': 50304, 'n_layer': 24, 'n_head': 16, 'n_embd': 1024, 'rotary_percentage': 0.25, 'parallel_residual': True, 'bias': True, 'n_query_groups': 16, 'shared_attention_norm': False, '_norm_class': 'LayerNorm', 'norm_eps': 1e-05, '_mlp_class': 'GptNeoxMLP', 'intermediate_size': 4096, 'condense_ratio': 1}
>> Prompt: hello
>> Reply: ": :mock_request,
                        "json_errors": "Error response from server: 500 (Internal Server Error)",
                        "error_messages": [
                          "Upgrade: JWT issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk issuer: jwk: jwk issuer:jwk: jwk issuerwk:jwk:jwkjwk:jjkjwkjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjjj^C

The above text was generated on A10G with torch==2.1.0.dev20230810+cu118.
And this what I get with the older version torch==2.1.0.dev20230703+cu118:
main ~/repos/lit-gpt python chat/base.py --checkpoint_dir checkpoints/EleutherAI/pythia-410m --precision bf16-true
Loading model 'checkpoints/EleutherAI/pythia-410m/lit_model.pth' with {'org': 'EleutherAI', 'name': 'pythia-410m', 'block_size': 2048, 'vocab_size': 50254, 'padding_multiple': 128, 'padded_vocab_size': 50304, 'n_layer': 24, 'n_head': 16, 'n_embd': 1024, 'rotary_percentage': 0.25, 'parallel_residual': True, 'bias': True, 'n_query_groups': 16, 'shared_attention_norm': False, '_norm_class': 'LayerNorm', 'norm_eps': 1e-05, '_mlp_class': 'GptNeoxMLP', 'intermediate_size': 4096, 'condense_ratio': 1}
>> Prompt: hello
>> Reply: ," I thought, although my breath was short and shallow, I was suddenly in a world of pain and adrenaline.
 I was a do not touch kind of girl who often left my father in the drivers seat.
She was a nice girl when she was a little girl, but she is now a very happy woman because she no longer is afraid of the dark and wants to be near a light.
I can't take her out with me. . . .

I turned on the TV to watch a show about small pets, and watched the screen to my embarrassment. There was a moment of shame in my heart, but I pushed away the words, and pulled the covers up to my chin. My eyes drooped. I felt sick.

"It's okay, I'll be right back." The strange feeling that I got when she was with me was gone. In a way, it made me feel happy to hear her voice, but it made me realize that I didn't want to see her again.

"Mom, you're getting better. And I have a feeling it can only help you."

"You're not the first one."

 You have your mother, and we have your Dad. You're going to be okay."

@Andrei-Aksionov Can you try a larger (3B+) instruction finetuned model? I don't trust the output of the smaller pretrained pythia models, they often output garbage. I recommend using a simple testing prompt like "The letters of the alphabet in order are:" instead of a prompt like "hello", especially with pretrained models

Model: Pythia-2.8b
Seed: fixed
Precision: bf16-true

Pytorch: 20230811 (the newest one)
⚡ main ~/repos/lit-gpt python chat/base.py --checkpoint_dir checkpoints/EleutherAI/pythia-2.8b --precision bf16-true
Global seed set to 1337
Loading model 'checkpoints/EleutherAI/pythia-2.8b/lit_model.pth' with {'org': 'EleutherAI', 'name': 'pythia-2.8b', 'block_size': 2048, 'vocab_size': 50254, 'padding_multiple': 128, 'padded_vocab_size': 50304, 'n_layer': 32, 'n_head': 32, 'n_embd': 2560, 'rotary_percentage': 0.25, 'parallel_residual': True, 'bias': True, 'n_query_groups': 32, 'shared_attention_norm': False, '_norm_class': 'LayerNorm', 'norm_eps': 1e-05, '_mlp_class': 'GptNeoxMLP', 'intermediate_size': 10240, 'condense_ratio': 1}
>> Prompt: The letters of the alphabet in order are:
>> Reply:

A B C D E F G H I J K L M N O P Q R S T U V W X Y Z

The years of the Zodiac are:

Aries: April 20 - May 20

Taurus: May 21 - June 21

Gemini: June 22 - July 22

Cancer: July 23 - August 22

Leo: August 23 - September 22

Virgo: September 23 - October 22

Libra: October 23 - November 21

Scorpio: November 22 - December 21

Sagittarius: December 22 - January 20

Capricorn: January 21 - February 18

Aquarius: February 19 - March 20

Pisces: March 21 - April 20

Each year has twelve months, each of which is divided into the number of days it contains (for instance, one year is divided into 12 months, and 12 of these are divided into the number of days in each month).

Sometimes in everyday life we use "year" to mean a whole number, rather than using the word "day" to mean the amount of time in a day. For example, "This is the year three hundred and seven."

Pytorch: 20230703
⚡ main ~/repos/lit-gpt python chat/base.py --checkpoint_dir checkpoints/EleutherAI/pythia-2.8b --precision bf16-true
Global seed set to 1337
Loading model 'checkpoints/EleutherAI/pythia-2.8b/lit_model.pth' with {'org': 'EleutherAI', 'name': 'pythia-2.8b', 'block_size': 2048, 'vocab_size': 50254, 'padding_multiple': 128, 'padded_vocab_size': 50304, 'n_layer': 32, 'n_head': 32, 'n_embd': 2560, 'rotary_percentage': 0.25, 'parallel_residual': True, 'bias': True, 'n_query_groups': 32, 'shared_attention_norm': False, '_norm_class': 'LayerNorm', 'norm_eps': 1e-05, '_mlp_class': 'GptNeoxMLP', 'intermediate_size': 10240, 'condense_ratio': 1}
>> Prompt: The letters of the alphabet in order are:
>> Reply:

A.

B.

C.

D.

E.

F.

G.

H.

I.

J.

K.

L.

M.

N.

O.

P.

Q.

R.

S.

T.

U.

V.

W.

X.

Y.

Z.

ADDITIONAL NOTES:

As a sign of good luck, a well-placed "C" will make it easier for you to find what you're looking for.

For the same reason, a well-placed "Q" is better than a "W" or "J."

According to some people, the "U" represents the number 7, and it's good luck when you find it on a mail box, or in a newspaper, book, or certificate.

Often there's more than one "Q" symbol on a letter or word.

When you know what letter it is and what it means, call it by its name:

A.

B.

C.

D.

E.

F.

G.

H.

I.

J.
K.
L
M
N.
O.
P.
Q.
R.
S.T.U
V.W.X.Y.
Z.

ADDITIONAL NOTES:

As a sign of good luck, a well-placed "C" will make it easier for you to find what you're looking for.

For the same reason, a well-placed "Q" is better than a "W" or "J."

According to some people, the "U" represents the number 7, and it's good luck when you find it on a mail box, or in a newspaper, book, certificate.

Often there's more than one "Q" symbol on a letter or word.

When you know what letter it is and what it means, call it by its name:
A.
B.

C.

D.

E.

F.

G.
H
I.
J.K.
L
M.N.O
P.
Q.R.R.S.T.U
V.WX.Y.Z.

ADDITIONALSO

So as you can see the response with the newest version to my eye looks even better.
The only question: why with previous (a month old) version of PyTorch generation with bf16-true on a Nvidia T4 (that doesn't support this precision) is possible, while with the newest one - not?

(Copy pasting @Andrei-Aksionov's answere from #408 here)
Actually it seems like the problem is in the precision (it's bf16-true by default) which is not supported by many popular graphics cards like T4 or V100.
And previous versions of PyTorch-nightly for some reason didn't care about wrongly provided precision at all.
So try to solve it in that order:

Use the proper precision for your graphics card. Here you can find what precisions are supported.
Hint: use --precision CLI argument in order to use it:python generate/base.py --prompt "Hello, my name is" --checkpoint_dir ./stablelm-base-alpha-3b --precision 32-true

If the above didn't help try to install the previous version of PyTorch-nightly (perhaps try with a clean venv):pip install --index-url https://download.pytorch.org/whl/nightly/cu118 --pre 'torch==2.1.0.dev20230703'

However, there is still the following error:
RuntimeError: Expected x1.dtype() == cos.dtype() to be true, but got false.  (Could this error message be improved?  If so, please report an enhancement request to PyTorch.)
who can help me?

.1.0.dev20230728+cu118

I had the same issue even with torch nightly v2.1.3.
Fixed by adding the above lines.

pip install --index-url https://download.pytorch.org/whl/nightly/cu118 --pre 'torch==2.1.0.dev20230703'

but cuda oom


Please consider fixing issues detected by repository checker

Notification from ioBroker Check and Service Bot
Dear adapter developer,
I'm the ioBroker Check and Service Bot. I'm an automated tool processing routine tasks for the ioBroker infrastructure. I have recently checked the repository for your adapter traccar for common errors and appropiate suggestions to keep this adapter up to date.
This check is based the current head revisions (master / main  branch) of the adapter repository
Please see the result of the check below.
ioBroker.traccar
   -
ERRORS:

[ ] :heavy_exclamation_mark: [E033] @iobroker/adapter-core 3.1.3 specified. 3.1.4 is required as minimum, 3.1.6 is recommended. Please update dependencies at package.json
[ ] :heavy_exclamation_mark: [E036] @iobroker/testing 4.1.0 specified. 4.1.3 is required as minimum,  4.1.3 is recommended. Please update devDependencies at package.json
[ ] :heavy_exclamation_mark: [E162] js-controller 3.1.0 listed as dependency but 4.0.24 is required as minimum, 5.0.19 is recommended. Please update dependency at io-package.json.
[ ] :heavy_exclamation_mark: [E204] Version "1.0.0" listed at common.news at io-package.json does not exist at NPM. Please remove from news section.

WARNINGS:

[ ] :eyes: [W028] Minimum node.js version 18 recommended. Please adapt "{'engines' : { 'node' >= '16' } }" at package.json.
[ ] :eyes: [W040] "keywords" within package.json should contain "ioBroker"
[ ] :eyes: [W115] "common.tier" is required in io-package.json. Please check https://github.com/ioBroker/ioBroker.docs/blob/master/docs/en/dev/objectsschema.md#adapter.
[ ] :eyes: [W181] "common.license" in io-package.json is deprecated. Please define object "common.licenseInformation"
[ ] :eyes: [W184] "common.main" is deprecated and ignored. Please remove from io-package.json. Use "main" at package.json instead.
[ ] :eyes: [W521] "gulp" found at devDependencies at package.json but no "gulpfile.js" found. Is this dependency really required?
[ ] :eyes: [W853] .npmignore found - consider using package.json object "files" instead.

:thumbsup: No suggestions found
Please review issues reported and consider fixing them as soon as appropiate.
Errors reported by repository checker should be fixed as soon as possible. Some of them require a new release to be considered as fixed. Please note that errors reported by checker might be considered as blocking point for future updates at stable repository.
Warnings reported by repository checker should be reviewed. While some warnings can be ignored due to good reasons or a dedicated decision of the developer, most warnings should be fixed as soon as appropiate.
You may start a new check at any time by adding the following comment to this issue:
@iobroker-bot recheck
Please note that I (and the server at GitHub) have always plenty of work to do. So it may last up to 30 minutes until you see a reaction. I will drop a comment here as soon as I start processing.
Feel free to contact me (@iobroker-bot) if you have any questions or feel that an issue is incorrectly flagged.
And THANKS A LOT for maintaining this adapter from me and all users.
Let's work together for the best user experience.
your
ioBroker Check and Service Bot
@mcm1957 for evidence
Last update at Fri, 06 Sep 2024 10:57:15 GMT

Issue outdated due to RECREATE request. Follow up issue #673 has been created.
This issue will be closed.
your
ioBroker Check and Service Bot


Docker CI

Added a docker compose for dev
Dockerfile updates to make a smaller image under nginx
Github ci to build/push docker image to docker hub

LGTM !

@Pipazoul the main branch is commented on the build.yml , so it won't start ? right ?


HI JT

Thank you for this calendar!
I have the new issue. I want to user swipe in range year from 2014 to 2015.
I could modify what method?
Thank!

For now you can't, but soon I will release a new version of the calendar, more customizable.

Thank JT,
I hope new version have my feature :)

I just release a new version.
Check the Example project.


feat(issue): avoid closing issues on dry-run mode

PR Checklist
Please check if your PR fulfils the following requirements:

[x] The commit message follows our guidelines
[x] Tests for the changes have been added/updated (for bugfix/feature)
[ ] Docs have been added/updated (for bugfix/feature)
[ ] Contributing implementation have been added/updated (for bugfix/feature)

PR Type
What kind of change does this PR introduce?

[x] Feature (a new feature)
[ ] Bugfix (a bug fix)
[ ] Style (changes that do not affect the meaning of the code (white-space, formatting, missing semi-colons, etc))
[ ] Refactor (a code change that neither fixes a bug nor adds a feature)
[ ] Perf (a code change that improves performance)
[ ] Test (adding missing tests or correcting existing tests)
[ ] Build (changes that affect the build system, CI configuration or external dependencies)
[ ] Docs (changes that affect the documentation)
[ ] Chore (anything else), please describe:

What is the current behaviour?

What is the new behaviour?
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Codecov Report

Merging #121 (b93d952) into develop (1e0c39b) will decrease coverage by 12.75%.
The diff coverage is 100.00%.

:exclamation: Current head b93d952 differs from pull request most recent head 01f8231. Consider uploading reports for the commit 01f8231 to get more accurate results

@@             Coverage Diff              @@
##           develop     #121       +/-   ##
============================================
- Coverage    99.46%   86.71%   -12.76%
============================================
  Files           43       43
  Lines          743      745        +2
  Branches        68       69        +1
============================================
- Hits           739      646       -93
- Misses           4       99       +95

Flag
Coverage Δ

integration
86.71% <100.00%> (+0.03%)
:arrow_up:

unit
?

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

Impacted Files
Coverage Δ

src/core/issues/issue-close-stale-processor.ts
100.00% <100.00%> (ø)

src/utils/links/create-input-link.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

src/utils/loggers/mock-date-format.ts
0.00% <0.00%> (-100.00%)
:arrow_down:

src/github/api/labels/github-api-labels.service.ts
54.90% <0.00%> (-45.10%)
:arrow_down:

src/utils/loggers/logger-format.service.ts
66.66% <0.00%> (-33.34%)
:arrow_down:

src/core/stale.service.ts
68.96% <0.00%> (-31.04%)
:arrow_down:

...imeline-items/github-api-timeline-items.service.ts
72.00% <0.00%> (-28.00%)
:arrow_down:

src/core/issues/issue-logger.ts
73.33% <0.00%> (-26.67%)
:arrow_down:

src/utils/loggers/logger.service.ts
78.94% <0.00%> (-21.06%)
:arrow_down:

src/utils/maps/map-filter.ts
80.00% <0.00%> (-20.00%)
:arrow_down:

... and 7 more


[ENH] provide helpers to allow cythonizing variants of custom declarative tools

In the Zokusei project im currently exploring a alternative to data-classes/attrs
for optimization purposes, i'd like to explore enabling cython to create constructors/helper methods tailored to the specific classes instead of just using loops over field objects
instead of having something like https://github.com/RonnyPfannschmidt/Zokusei/blob/d4114c1266b740e421ee07368be55e6f0cc7e415/src/zokusei/init.py#L29-L44
i'd like to be able to have cython act,
as if for a
# point.py
class Point(...)
    x: int = field()
    y: int = field()

there also was a
def __init__(self, x, y):
   self.x = x
   self.y = y

and in case there was a
# point.pyx

cpdef class Point(...)::
   cpdef int x
   cpdef int y

i would like to be able to have cython act,
as of the ctor was also declared with additional data types as well
as next steps im exploring good ways to write the generic ctors in a way cython speeds them up a little, but i'd like to be able to use the  full power of cython from "metaprogramming"

Right now we don't have a lot of metaprogramming support (because it's a bit more complicated than regular Python - "runtime" no longer really works for code generation).
I think there's been a number of proposals in the past, but none have been really convincing (and none have been implemented).
Our own (proposed) implementation of dataclasses relies mostly on code-generation (which your project is aiming to avoid) but it also has access to a lot of internal Cython details to help it. And it isn't hugely pretty.
So I don't have any great suggestions - I can see why it'd be nice but I can also see why it hasn't been done

for my particular use-case - it would probably be enough if there was a way to make cython inline loops of known values
alternatively, if there was any way to generate/alter a "Ast" that cython is supposed to use it would also be a big help
if there was any way to tell cython more about the building blocks its allowed to use in some places instead of the roundabout code,
that would help
also - i don't mind generating code for the cythonize my datatypes route
after all thats a compilers step to make class loading and execution cheaper and faster
what i want to avoid however is runtime codegen (so if  its cythonize its fine to use a codegen , if its not cythonize, its bad to use a codegen


style up more admonition types

full list in the RTD docs

trying to get this working. currently blocked on #47


Work with 'yarn hot'

I am using yarn watch to work with frontend because i couldn't get the yarn hot.
It says compiled successfully but when i reload the page, the changes are not there.

Fixed, I liked your Naruto profile picture hahaha

@alefesouza Thanks man


graphia: 3.1 -> 3.2

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/graphia-app/graphia/releases.
meta.description for graphia is: "A visualisation tool for the creation and analysis of graphs."
meta.homepage for graphia is: "https://graphia.app"
meta.changelog for graphia is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.2 with grep in /nix/store/m6fjx74qsgx038hcxyx5pxzx8jf588jz-graphia-3.2
found 3.2 in filename of file in /nix/store/m6fjx74qsgx038hcxyx5pxzx8jf588jz-graphia-3.2

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
graphia

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/m6fjx74qsgx038hcxyx5pxzx8jf588jz-graphia-3.2 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A graphia https://github.com/r-ryantm/nixpkgs/archive/24703a94e5d17cb52f8a379a9342f5517e82d0f5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/m6fjx74qsgx038hcxyx5pxzx8jf588jz-graphia-3.2
ls -la /nix/store/m6fjx74qsgx038hcxyx5pxzx8jf588jz-graphia-3.2/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

graphia

Maintainer pings
cc @bgamari for testing.

@GrahamcOfBorg eval


Google Maps MarkerClusterer should be configurable

As a user I should be able to enable/disable marker clustering and configure grid size, e.g.:
maps:
  google:
    marker_clusterer:
      enabled: true
      grid_size: 25

Implemented.


Bot gets stuck after applying to jobs for awhile. Always same error.

: Waiting for selector .jobs-search-results-list li.jobs-search-results__list-item:nth-child(7) failed: Waiting failed: 5000ms exceeded
at Timeout.

This could be as a result of a slow connection or device.. basically the DOM content doesn't get loaded in time so the element is not found before the time threshold is exceeded.

Alright I increased the timeout to 9000 gonna test to see if I still run into this problem. Ill report back


Update Integration Docs for Vendor Neutrality

Please remove this paragraph from the Diagrid Conductor Integration page to ensure vendor neutrality:

Try out Conductor Free, ideal for individual developers building and testing Dapr applications on Kubernetes.

Paragraph removed via https://github.com/dapr/docs/pull/4344


Improve support for purging older job info

If a user is running many push jobs they can accumulate quite a few old jobs that are no longer interesting. This slows the server down, consumes storage, and makes the listing commands less useful.
While jobs can be deleted individually, this is painful to do in bulk and should be automated.
A couple of options suggest themselves:
add a configurable expiry date for older jobs
add bulk delete based on filters
The first is probably the simplest to do.

https://github.com/chef/chef-push/issues/4


Event hooks for plugins: Change from function-hooks to an observer

Currently it's not possible to have multiple plugins installed which use the same event hook.
For distributing core events to the core view, we already use an observer and it works pretty well.
So we need to change that as soon as possible because at the moment there aren't that much plugins yet which have to be changed the way they register for an event.

Since you are using jQuery you could create your own events like this...
to Register events:
$(Candy.View.Event.Message).bind('beforeShow', function (e, message) { /* do stuff ... / });
$(Candy.View.Event.Message).bind('beforeShow', function (e, message) { / some other stuff... */ });
to trigger the event and call all registered handlers:
$(Candy.View.Event.Message).triggerHandler('beforeShow',[message]);
I would like to contribute to this project... what are the steps for me to get involved?

+1 for using jQuery's event bus

@patforg: Sounds nice! Didn't know that.
To contribute you could first fork the project and make a branch for e.g. this feature. Then you make the necessary changes and submit a pull request to our "dev"-Branch. We can then review your changes and apply them if everything's good.
As soon as you contributed some stuff, we could give you commit rights.
@pstadler: What do you think about doing it this way?

Works for me, I already had a fork going will get a feature branch going.

Cool patforg, we'll be glad to receive your pull requests!

I'm closing this issue in favor of #51


Fix specs according changes in sshkit 1.11

SSHkit 1.11 adds a :known_hosts option to ssh_options,
which breaks one spec in the current master.

Thanks, good catch!


CDK install via DevSuite Installer fails if minishift previously installed in /usr/local/bin

I had previously installed minishift on my Mac using https://github.com/chouseknecht/minishift-up-role. This Ansible role installs Minishift with OpenShift Origin into /usr/local/bin. This breaks the DevSuite Installer, as it constructs its search path to prioritize /usr/local/bin before /Applications/DeveloperSuite.

Perhaps the installer should check for the presence of /usr/local/bin/minishift first.

That can be fixed, but there still would be conflict between CDK and minishift (there is issue for that in CDK JIRA https://issues.jboss.org/browse/CDK-210).


S&R : Total amount  are displayed in satoshis (sats) but are not labeled

[x] Issue Identified:

The total amount and total fees are displayed in satoshis (sats) but are not labeled, leading to potential confusion. It may appear as if the amounts are in Bitcoin (BTC) rather than sats.

Completed


do in diff mode does not remove manually created folds in replaced area

Steps to reproduce

Run vim --clean
Source the following file:

call setline(1, ['a', 'b', 'g', 'h', 'i', 'j', 'k'])
vnew
call setline(1, ['a', 'b', 'c', 'd', 'e', 'f', 'j', 'k'])
windo diffthis
set foldmethod=manual
3,4fold
5
call feedkeys('do', 'tx')

The fold in now on lines 4,5

Expected behaviour
The fold is removed
Version of Vim
9.0.135
Environment
Operating system: Arch Linux
Terminal: kitty
Value of $TERM: xterm-kitty
Shell: fish
Logs and stack traces
No response

It probably does not make sense to use foldmethod=manual in diff mode?

Commands like "do" and ":diffget" rely on the foldmethod to be "diff".
When you set it to "manual" you'll have to adjust folds manually.


Events for signing and verifying signatures

Signed-off-by: Matej Pavlovic<EMAIL_ADDRESS>

Summary of changes: squash and rebase


UI - platform web ci / cd stuff

Issue:

bcgov/entity/issues/

Description of changes:
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the namex license (Apache 2.0).

Temporary Url for review: https://strr-platform-dev--pr-194-rgaaaigh.web.app

Temporary Url for review: https://strr-platform-dev--pr-194-rgaaaigh.web.app

Temporary Url for review: https://strr-platform-dev--pr-194-rgaaaigh.web.app

Temporary Url for review: https://strr-platform-dev--pr-194-rgaaaigh.web.app

Temporary Url for review: https://strr-platform-dev--pr-194-rgaaaigh.web.app

Temporary Url for review: https://strr-platform-dev--pr-194-rgaaaigh.web.app

Temporary Url for review: https://strr-platform-dev--pr-194-rgaaaigh.web.app


[BUG] Ammunition calculating incorrectly

Module Version: v0.31.1

Describe the bug
Ammunition is not calculating correctly, instead of using the weight 0.075, it is using 1.5. I looked through the settings and could not find anything that could be causing this (using default settings)
To Reproduce
Steps to reproduce the behavior:
Add ammunition with quantity 20 and weight 0.075 to a characters inventory. Observe total weight
Expected behavior
Weight should be 20 * 0.075, which is 1.5
Screenshots

Browser:

Foundry client

Foundry Version:
11.306
Game System:
DnD5e: 2.2.2

Sorry @txm3278 cannot replicate the issue on my actors can you pass to me the actor json data ?

I ran Find the Culprit and this is only an issue with the item containers module installed. I can't upload a json here, can I dm it to you over discord?

Should be fixed with 0.13.3 let me know it

Ammunition now calculates correctly, but I am having the same issue described here.

Fixed, Thanks!

This bug is back,

Looking through the code, for ammo, it is calculating the weight with itemQuantity * itemWeight. Then it is again multiplying by itemQuantity

I was sure it was  solved...  can you export the actor data json (rename the json with .txt for upload on github)

Tested in the latest update, this is working again! The debug messages do look a bit odd though, mainly the last one,

i'll fix that


InventoryCollection Builder improvements

Issue: https://github.com/ManageIQ/manageiq/issues/17396

[ ] dependent :  https://github.com/ManageIQ/manageiq-providers-amazon/pull/456
[ ] dependent : https://github.com/ManageIQ/manageiq-providers-azure/pull/271
[ ] dependent : https://github.com/ManageIQ/manageiq-providers-openstack/pull/307
[ ] dependent: https://github.com/ManageIQ/manageiq-providers-ovirt/pull/268
[ ] dependent: https://github.com/ManageIQ/manageiq-providers-redfish/pull/14
[ ] dependent: https://github.com/ManageIQ/manageiq-providers-kubevirt/pull/104
[ ] dependent: https://github.com/ManageIQ/manageiq-providers-kubernetes/pull/265
[ ] dependent: https://github.com/ManageIQ/manageiq-providers-openshift/pull/100

Renaming builder_params => default_values (partially)
Merged common definitions from provider specific

cc @agrare

Cc @Ladas

@slemrmartin this looks good to me, I assume we'll need to merge this and the rest of the provider PRs together since at least the builder_params change is breaking?
Can you run the refresher specs for all of the providers locally before I merge this to make sure we don't run into any surprises when we kick the rest of the PRs?

@agrare I added an alias to add_builder_params so providers specs will work before and after merge of providers PRs.
:builder_params symbol will be refactored later, it influences more than builder and definitions.
All providers tested locally without problems

@slemrmartin ah you're right I totally missed that alias, :+1:


Update: JetBrains.PHPStorm.EarlyAccess version 212.4746.69

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[x] Does your manifest conform to the 1.0 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

JetBrains PHPStorm failed last time also?


Regarding algorithm IDs like ranger(15)

[ ] wait until Jakob has an answer
[ ] maybe change API from algo_id to algo_name

Maybe we can have both. Algo by id and algo by name? The latter then uses all ids that fits the name? More important is the last one.
The new ids are introduced when a learner gets a new version. This usually should not affect the outcome.

This should be working by now.

If the algo parameter is non-numeric, it just assumes its the algorithm name.


[BUG] Advanced grpahics quality not changing when enabled

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[X] I have thoroughly looked through the available Wiki articles and could not find a solution to my problem.
[X] I am using the latest version of Bloxstrap.
[ ] I did not answer truthfully to all the above checkboxes.

What problem did you encounter?
i tried to change my settings beacuse arsenal was laggy and noticed that i have 1-10 graphics and my adavanced ones are enabled. please fix this*
Bloxstrap Log

This bug happens to me aswell, should be fixed

FFlag that made the setting work got removed by Roblox. We can't do anything about it, since we're not Roblox Technicians.


Search on a mobile browser

Glad to see the search plugin! 👍
But there is a bug when I test it on a mobile browser (at least on Firefox for Android). When I click on the search bar, the sidebar will hide itself...
Another problem is that data-auto2top has no effect on a mobile browser.

auto2top  is work in iPhone Safari/Chrome. I don't have Android devices to test...

No problem on Chrome for Android too. Try Firefox for iOS, maybe?


Fix space between popover's arrow and triggering element

This PR is a proposal to:

Fix the space between the popover's arrow and the triggering element.
Add --bs-popover-inner-border-radius as it is done for the dropdowns with --bs-dropdown-inner-border-radius

(Note: I can split the commits if needed)
Regarding the fix proposed here.
In https://github.com/twbs/bootstrap/commit/2e75ec3c41a54865caa48f46485a1c90b12b0de6 (and so in the main branch) we can observe this kind of modifications:
- bottom: subtract(-$popover-arrow-height, $popover-border-width);
+ bottom: calc((var(--#{$variable-prefix}popover-arrow-height)) * -1); // stylelint-disable-line function-disallowed-list

The substraction does not appear in the new calculation. So the rendering is slightly different:
Before
Preview: https://getbootstrap.com/docs/5.1/components/popovers/#four-directions

With the error (main branch)
Preview: https://twbs-bootstrap.netlify.app/docs/5.1/components/popovers/#four-directions
There is an extra spacing between the button and the arrow:

With the fix proposed in this PR
Preview: https://deploy-preview-35976--twbs-bootstrap.netlify.app/docs/5.1/components/popovers/#four-directions

I always used .25 increments but I don't think everyone else has been following that.

I always used .25 increments but I don't think everyone else has been following that.

Thanks for the rule, I've updated my .66 :smile: to .75 via https://github.com/twbs/bootstrap/pull/35976/commits/9b3407a59874b964099410b1c24364210c41077f


[INLONG-2349][inlong-dataproxy ]modify dataproxy log name

modify dataproxy log name
Fixes #2349

Codecov Report

Merging #2350 (31b4b2b) into master (256ebf9) will increase coverage by 0.01%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master    #2350      +/-   ##
============================================
+ Coverage     12.53%   12.54%   +0.01%
- Complexity     1215     1218       +3
============================================
  Files           420      420
  Lines         36240    36240
  Branches       5670     5670
============================================
+ Hits           4541     4546       +5
+ Misses        30893    30886       -7
- Partials        806      808       +2

Impacted Files
Coverage Δ

...ong/tubemq/manager/service/ClusterServiceImpl.java
52.94% <0.00%> (+2.94%)
:arrow_up:

...inlong/tubemq/manager/service/TaskServiceImpl.java
8.53% <0.00%> (+4.87%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 256ebf9...31b4b2b. Read the comment docs.


Scenes

I have a intermittent problem with scenes.
I define a scene with 3 light bulbs, to switch them all on.
I play the scene and most times only the first bulb is switch on.
The debug log shows, that all on characteristics fired and the platform did set on.
Any idea ?

I am also having a problem with scenes. I have a scene that I use to control multiple Nest thermostats at the same time. It worked great for months then about 3 weeks ago it only worked 50% of the time. Now the scene doesn't work at all. I can still control each thermostat separately with Siri.

You can close this issue from my side. Homebridge did send the correct commands in the correct sequence. The problem was net.Socket handling in the platform.
Sorry for the issue.


fix: users' lsp.root_dir config not respected when starting lsp

Previously custom root_dor is not used when starting otter language server. This patch fixes this issue by requiring the config module on starting the language server (after it merges with user's custom config).

thanks!


Data with an axis of length of 0 infinite loops

Seems that if you gives the function an array where one of the axes lengths is 0 then the program goes into an infinite loop. The simple test case I found is:
dwtn([[]], 'haar')

But it is likely true about others as well, just haven't tested other situations.

Thanks for reporting this. It looks like we need to add some kind of sensible error in this case.
I don't believe we currently have any length 0 test cases.

I accidentally did it while writing in an IPython notebook. It was an incomplete line and then I lost my session when I killed the process (not really much of a loss).

Okay, this should be addressed by #506.  There was a guard against this in the 1D case, but it was not being applied for >=2D data.

Great!


Make GKE configuration and context setup optional

As discussed.
We could extend Fy to be able to login to EKS but in this particular case it's unclear whether we'll need to do that or use another agent (and then would arguably need to consider other forms of K8s login which may not be linked to cloud providers). For now the best escape hatch is just to make the GKE login optional.

Forked to update variable name and merged: https://github.com/Inshur/fy/pull/24


Icon Deslection

User Story
As a user, I would like to have an easy way to deselect an icon corresponding to a group member, so that I can correct myself easily in case I miss-clicked one.
Detailed Description
Provide additional details and context.
Acceptance Criteria

[ ] Given [Condition], then [Expected Result]
[ ] Given [Condition], then [Expected Result]
[ ] Given [Condition], then [Expected Result]

Closed.

Closed.


InputFileCache and "Issue is not linked to a file" problem

Hi, I have a problem - issues in my project are not reported into BitBucket PR despite they are detected correctly. I only see  "No new issues detected" comment in BB, and in the log many errors "Issue xxx is not linked to a file". I examined source codes of Sonar Stash plugin and found the place where this error is raised. There is the FileInputCache in place and the error is thrown when cache miss, but I was unable to recognize where and how this cache is build. Can somebody please explain me how this works, and why I'm getting this error?

The cache is built in the InputFileCacheSensor.
Can you describe the setup of your project?

Which runner?
In which directory do you execute the runner?
In which directory is your git root?
Is it a multi-module project?
Which version of the plugin are you using?

The plugin version is 1.2.0.

What is the project base dir in term of sonar?

I see this issue with a Java/Maven project. It appears that the plugin is properly finding a couple of issues with the PR, but the only comment on the PR is "No new issues detected" - even though near the end of the debug logs, there is a message "New SonarQube issues have been reported to Stash."

Multi-module Maven project
Jenkins 2.53
SonarQube 6.3
sonar-stash plugin version 1.2.0
sonar-maven-plugin 3.2

Here's the Maven command being executed by Jenkins:
-B -Dsonar.analysis.mode=preview
-Dsonar.branch=myAppBranch -Dsonar.stash.notification=true
-Dsonar.stash.repository.root=${JENKINS_HOME}/workspace/myapp-pull-request
-Dsonar.stash.project=PROJ -Dsonar.stash.repository=myapp
-Dsonar.stash.pullrequest.id=1 '-Dsonar.stash.password=****'
-X -Dsonar.verbose=true

I don't see the sonar.stash.repository.root property in the documentation for plugin version 1.2.0, only in the unreleased 1.3-SNAPSHOT. Figured it couldn't hurt to try it, but it doesn't seem to have an effect.
Here is some debug output (I used the variable JENKINS_HOME for brevity and to obscure actual dir structure, but that is fully expanded in my logs):
12:25:11 [DEBUG] 12:25:11.612 Initializers :
12:25:11 [INFO] 12:25:11.612 Base dir:${JENKINS_HOME}/workspace/myapp-pull-request
12:25:11 [INFO] 12:25:11.612 Working dir: ${JENKINS_HOME}/workspace/myapp-pull-request/target/sonar
12:25:11 [INFO] 12:25:11.612 Source encoding: UTF-8, default locale: en_US
.... snip stuff about other plugins ...

12:25:11 [DEBUG] 12:25:11.650 Sensors : org.sonar.plugins.clover.CloverSensor@52ac965f -> Stash Plugin InputFile Cache -> Embedded CSS Analyzer Sensor -> XmlFileSensor -> Analyzer for "php.ini" files
.... snip stuff about other plugins ...

12:25:11 [INFO] 12:25:11.651 Sensor Stash Plugin InputFile Cache [stash]
12:25:11 [INFO] 12:25:11.651 Sensor Stash Plugin InputFile Cache [stash] (done) | time=0ms
.... snip stuff about other plugins ...

12:25:12 [INFO] 12:25:12.025 99/99 components tracked
12:25:12 [INFO] 12:25:12.025 ANALYSIS SUCCESSFUL
12:25:12 [DEBUG] 12:25:12.028 Post-jobs : org.sonar.plugins.stash.StashIssueReportingPostJob@76813d96
12:25:12 [INFO] 12:25:12.028 Executing post-job org.sonar.plugins.stash.StashIssueReportingPostJob
12:25:12 [DEBUG] 12:25:12.049 Issue AVuSJRxDW5zjNhC4tWNV is not a new issue and so, not added to the report
.... snip many more log msgs like the above ....

12:25:12 [DEBUG] 12:25:12.051 Issue 015BA0C7FA330DE4D6 is not linked to a file, not added to the report
12:25:12 [DEBUG] 12:25:12.051 Issue 015BA0C7FA330DE4D7 is not linked to a file, not added to the report
.... snip more "not a new issue" log msgs ....
... snip detailed HTTP resquest/response logging ....

12:25:12 [DEBUG] 12:25:12.466 SonarQube reviewer sonar identified in Stash
... snip detailed HTTP resquest/response logging ....

12:25:12.829 Stash differential report retrieved from pull request myapp #1
12:25:13 [INFO] 12:25:12.829 New SonarQube issues have been reported to Stash.
... snip detailed HTTP resquest/response logging ....

12:25:13 [INFO] 12:25:13.069 SonarQube analysis overview has been reported to Stash.
12:25:13 [INFO] 12:25:13.093 Task total time: 11.956 s

@lllewellyn Did you use the 1.3.0-SNAPSHOT version or 1.2.0?
The new setting only has an effect in 1.3.

1.2.0. I guessed that the new setting only affected the snapshot but tried it anyway. I wasn't surprised that it didn't help.

More troubleshooting information - I modified my copy of the 1.3.0-SNAPSHOT code to add debug logging to the InputFileCacheSensor class. I also added logging to the StashRequestFacade.getIssuePath() method, to log the name of any file not found, and have the StashRequestFacade constructor logging the repository root and project base dir. Here are some sample results. Again, ${JENKINS_HOME} resolves to a correct absolute path on my system, I use the variable for brevity and to redact the real content.
Here's logging added to the InputFileCacheSensor.
    @Override
    public void analyse(Project module, SensorContext context) {
        LOGGER.debug("******* Building InputFileCache");
        for (InputFile inputfile : filesystem.inputFiles(filesystem.predicates().all())) {
            LOGGER.debug("******* Added file {} with key {}", inputfile, context.getResource(inputfile).getEffectiveKey());
            inputFileCache.putInputFile(context.getResource(inputfile).getEffectiveKey(), inputfile);
        }
    }

Here's assocated debug output from the InputFileCacheSensor. Note the 'key' values are all null. This explains why the files can't be found.
09:45:02 [DEBUG] 09:45:02.733 ******* Building InputFileCache
09:45:02 [DEBUG] 09:45:02.733 ******* Added file [moduleKey=com.company.myapp:module1, relative=application.properties, basedir=${JENKINS_HOME}/workspace/myapp-pull-request/module1] with key null
09:45:02 [DEBUG] 09:45:02.733 ******* Added file [moduleKey=com.company.myapp:module1, relative=pom.xml, basedir=${JENKINS_HOME}/workspace/myapp-pull-request/module1] with key null
09:45:02 [DEBUG] 09:45:02.733 ******* Added file [moduleKey=com.company.myapp:module1, relative=src/main/java/com/company/myapp/batch/BrokenCode.java, basedir=${JENKINS_HOME}/workspace/myapp-pull-request/module1] with key null

The facade prints the following from the constructor:
09:45:07 [DEBUG] 09:45:07.494 ******** repository root: 'Optional[${JENKINS_HOME}/workspace/myapp-pull-request]'
09:45:07 [DEBUG] 09:45:07.494 ******** projectBaseDir: '${JENKINS_HOME}/workspace/myapp-pull-request'

so it looks like in my case, setting the repository root is redundant.
When trying to locate file paths, the enhanced logging confirms that the plugin is planning to add comments for the right file:
09:45:08 [DEBUG] 09:45:07.779 ****** Could not find path for componentKey com.company.myapp:module:src/main/java/com/company/myapp/batch/BrokenCode.java in file cache
09:45:08 [DEBUG] 09:45:07.779 Issue 015BA55BC8855A4336 is not linked to a file, not added to the report
09:45:08 [DEBUG] 09:45:07.779 ****** Could not find path for componentKey com.company.myapp:module1:src/main/java/com/company/myapp/batch/BrokenCode.java in file cache

Do you have suggestions for what to try next? I'm not familiar with the internal workings of SonarQube. Looks like we might be able to fix this by correcting the file cache keys.

Looking at the SonarQube API, the Resource.effectiveKey property is commented with "internal use only'. Maybe SonarQube 6.3 is no longer setting the value. The entire class is actually marked Deprecated.
https://github.com/SonarSource/sonarqube/blob/master/sonar-plugin-api/src/main/java/org/sonar/api/resources/Resource.java
...
public String getEffectiveKey() {
    return effectiveKey;
  }

  /**
   * Internal use only
   */
  public final Resource setEffectiveKey(String effectiveKey) {
    this.effectiveKey = effectiveKey;
    return this;
  }
...

@lllewellyn I can confirm that the effective key is null for me on 6.3.
The internal use only applies to the setter, as the user is not supposed to modify the object.
I assume this is a regression in SonarQube and will investigate this.

Can we somehow trigger initialization of the effectiveKey from Sonar Stash plugin? I know the error is probably in the Sonar API part, but it will be faster to fix it in our code than waiting for authors of Sonar to fix it..

@lllewellyn @michalmikee  Can you test #127?

Hooray, the fix in PR 127 worked for me!
Thank you for being so responsive and providing a fix so quickly, I appreciate it. I can demonstrate an integration between Jenkins, SonarQube, and Bitbucket now and this plugin helps a lot. I'd love to have an officially blessed release before using the plugin in production. Any idea when we might expect 1.3.0 release including this fix?

Hello, any update on getting the fixed merged and into an official release? Thanks!

#127 Is now in 1.3.0-rc1, please test.


setActiveEventTool

the tool should not be set as active when installing the extension.
setActiveEventTool is handy for debugging but not for release versions
https://github.com/LettError/LightMeter/blob/master/LightMeter.roboFontExt/lib/lightMeterTool.py#L366
tjanks

Thanks, fixed.


blogViewModel and openSourceViewModel VS ViewModelProviderFactory

hi i checked both previous and new code and i have a question. as i see, you move all viewmodels to ViewModelProviderFactory and remove them from modules. Although you mention new OpenSourceViewModel(dataManager,schedulerProvider); and  new BlogViewModel(dataManager,schedulerProvider); in ViewModelProviderFactory, you also provide them in OpenSourceFragmentModule and BlogFragmentModule. why did you do this ?
thanks

hey,
Thanks for pointing it out.
This looks like a mistake and we have rectified it and it will be available soon in the master branch.
Reason being , now all the VM creation is delegated to VMFactory and hence there should not be any VM creation from any of the modules.

Thanks for answering me. you can close this issue


can't install this plugin

android studio 2.2.2
when i install this plugin from browse repositories, it can't download.
so i use install plugin from disk, this can install but when i restart android studio, it warn this plugin has some problems.
please help me!

Do your Android Studio install Kotlin plugin?

Thanks! It works.

Your welcome. Thanks for installing this plugin!


fail use jwt_parser:base64_decode to decode when upgrade kong 3.4.2 to 3.6.0

Is there an existing issue for this?

[X] I have searched the existing issues

Kong version ($ kong version)
kong 3.6
Current Behavior
In Kong 3.6.0
When I use kong.plugins.jwt.jwt_parser:base64_decode, it will meet exception : nil,invalid input.
2024/03/01 16:14:10 [debug] 1277#0: *1286 [lua] sso.lua:119: jwt_decoder:base64_decode(key) = nilinvalid input
Expected Behavior
In Kong 3.4.2
When I use kong.plugins.jwt.jwt_parser:base64_decode, it will decode successfully.
☺☺☺♣♥�☺0�☺H��:18:34 [debug] 1259#0: *150 [lua] sso.lua:119: jwt_decoder:base64_decode(key) = 0�☺"0
☻�☺☺�y¶@�K♠��%/{���▲(�Ԕ��/�♥[�73Ql9�I� H���♣��I‼1       �o��:��g�߹�ZU�'2�d`��J�H3�)
�▲ؿ
鷂rO��L������ ��g▲��P���Ô�#�����v!���6TL�z26^��xq��     �v4����M∟4:{♣���tξ(����↕�[܋�t����[e�r�d��g�e=♠y��T�hs▼�6I�yN7�����→}‼^����↔¶�ǽx��s1���4��f�E�→,F��.��►e1���n���r_☻♥☺☺

Steps To Reproduce

Require jwt_parser

local jwt_decoder = require "kong.plugins.jwt.jwt_parser"
local DEBUG, ERR, INFO, log = ngx.DEBUG, ngx.ERR, ngx.INFO, ngx.log

use jwt_parser:base64_decode

local test_key = "MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAsbxk6rmBw/+8b2qwQnxKcK8VRRJcSQGCHjwzCzYmMa+XuRL0iaDmOIpXvXmqSMDGM/CdjoQhGfyotnnw3fROjBnOpnNeiX6UPYsJSLzozx1pv7gvRkyfv6hpp9pMn6UWt4IkFsHpeM/V1Spxvgbr+S9clXn+0saM529fK9BFPxjyHk2Jv+SHy9fnjre/5sFVyGxeAM36RVcw3u/D7v7gKigCjhR1Qc3FMJKDrZE5AQQOJELYMrWvaBUxVYjRwQpuEGt/OHbvJZEpABhIYd2lbby1BNtq96loup/SBxJ3jam0MUsf8aB87+vB4QiaX5gwTTLRw2IcnEal+DuZgnNaQQIDAQAB"
log(DEBUG, "jwt_decoder:base64_decode(key) = ", jwt_decoder:base64_decode(test_key))

check the log, you can see:
2024/03/01 16:14:10 [debug] 1277#0: *1286 [lua] sso.lua:119: jwt_decoder:base64_decode(key) = nilinvalid input

Anything else?
https://github.com/Kong/kong/pull/11569 refactor the code about jwt_parser:base64_decode, so is it expected that such an error will occur?

Not sure whether if https://github.com/Kong/kong/pull/11569 affectted it, we need to check

We have created a ticket to track this issue (KAG-3952), thanks for your report.

jwt token should be encoded with Base64URL algorithm, which means that we should replace '+' to '-' and '/' to '-'.
The variable test_key includes invalid char /, so kong think it is a wrong base64url string.

You can change the code like this:
local input = "..."
input = input:gsub("+", "-"):gsub("/", "_")
print(jwt_decoder:base64_decode(input))

jwt token should be encoded with Base64URL algorithm, which means that we should replace '+' to '-' and '/' to '-'.
The variable test_key includes invalid char /, so kong think it is a wrong base64url string.

Thanks, the problem has already been solved.

You can change the code like this:
local input = "..."
input = input:gsub("+", "-"):gsub("/", "_")
print(jwt_decoder:base64_decode(input))

@chronolaw Will this change be added to the source code？

You can change the code like this:
local input = "..."
input = input:gsub("+", "-"):gsub("/", "_")
print(jwt_decoder:base64_decode(input))


Twig function evaluate has no direct access to page object

This code doesn't work:
{{ evaluate('page.header.title') }}

This code works correctly:
{{ evaluate('grav.page.header.title') }}

This is actually expected.  evaluate() is a custom function that utilizes the Twig::processString() function, and that can be called at any time whether or not a page has been initialized or not.  It only has access to Twig variables that are setup in the Twig::init() function:
            // Set some standard variables for twig
            $this->twig_vars = $this->twig_vars + [
                    'config'            => $config,
                    'system'            => $config->get('system'),
                    'theme'             => $config->get('theme'),
                    'site'              => $config->get('site'),
                    'uri'               => $this->grav['uri'],
                    'assets'            => $this->grav['assets'],
                    'taxonomy'          => $this->grav['taxonomy'],
                    'browser'           => $this->grav['browser'],
                    'base_dir'          => rtrim(ROOT_DIR, '/'),
                    'base_url'          => $base_url,
                    'base_url_simple'   => $this->grav['base_url'],
                    'base_url_absolute' => $this->grav['base_url_absolute'] . $path_append,
                    'base_url_relative' => $this->grav['base_url_relative'] . $path_append,
                    'home_url'          => $base_url == '' ?  '/' : $base_url,
                    'theme_dir'         => $locator->findResource('theme://'),
                    'theme_url'         => $this->grav['base_url'] . '/' . $locator->findResource('theme://', false),
                    'html_lang'         => $this->grav['language']->getActive() ?: $config->get('site.default_lang', 'en'),

                ];
        }

The fact that you are using it in a Twig template, means that Page is almost certainly available (via the Grav container), but not via page directly which is only added via Twig::processPage() and Twig::processSite()


Code refinements, better error handling

Description
Some code prettification, better error handling in some places

Note 2 code reviewer approval needed. Approach in twitter group & discord channel.

@Mira-Alf @tolgaerdonmez are you guys fine with this changes?

@Mira-Alf is it working? If not breaking any thing I will merge it

More additions. The code works now. Issues were with putting await at the wrong place


pytest-check-hook.sh: delete pytest bytecode after install

In https://github.com/NixOS/nixpkgs/issues/139292 we found out that
pytest leaves pytest-generated bytecode in install directory
(as tests are ran after install). That bytecode is:

non-deterministic (was copied from cpython before cpython got
support for deterministic bytecode)
unneeded after test run

The change cleans bytecode up and provides a hook variable to avoid it
if needed.
Tested on python39Packages.pytest-xdist as:
$ nix build -f. python39Packages.pytest-xdist
$ nix build -f. python39Packages.pytest-xdist --rebuild

Closes: https://github.com/NixOS/nixpkgs/issues/139292

Why not create an entirely new hook that's always run and removes those files, i.e. not only if pytestCheckHook is used?

Why not create an entirely new hook that's always run and removes those files, i.e. not only if pytestCheckHook is used?

I'm not very familiar with nixpkgs hooks stacking. How the hook you propose should it be activated?
One of caveats is that hook needs to know exact pytest version (or hook should be tweaked slightly to delete all files that look remotely like pytest files).

One of caveats is that hook needs to know exact pytest version (or hook should be tweaked slightly to delete all files that look remotely like pytest files).

I think it makes sense to remove the files regardless of version.

How should packages opt into such hook?

How should packages opt into such hook?

Sandro suggested running along with rest of python hooks. Converted it to a new hook and placed it to postPhases. While at it added python2 cleanup as well.

This is better added as setupHook to pytest itself. It already has one for removing the cache it creates.

Switched to pytest-provided setupHook.

Right, I forgot that case!


Fixing percentage change for more accurate representations of changes

Problem
Previously we floored the percentage change ie if its 12.65%, this was displayed as 12%.
However, for smaller changes, ie below 1%, this can be deceptive as this will show up as 0% changes.
Solution
This PR updates the createDetailedReport function to display all percentage changes with two decimal places, regardless of their value.
This ensures that all percentage changes are displayed consistently with two decimal places, and allows for accurate checks on the percentage change value.

Thank you :)


(GH-2323)(Docs) Finalize module docs

Closes #2323
Major changes:

Restructured the modules section to emphasize "Modules overview" to
readers. These parent pages can get a bit lost in the nav.
Turned modules.md into "Modules overview" and added some high-level
explanation of modules (in Bolt) and dependency management.
Edits to Module structure doc. This doc lacked direction. I've tried
to narrow the focus down to modules that you're using with Bolt -
where you should put the code and how you can load it with Bolt.
Removed the Managing modules page and added most of the content from
that page to "Installing modules".
Moved the "What's changed" section to the relevant developer update.
Moved the packaged modules section to "Modules overview."
Moved the compatibility stuff to "Modules overview."
Removed/Deprecated most references to the old Puppetfile workflows.
Moved the "Migrate a Bolt project" info to the projects page.
Added a section on modules to Troubleshooting.

For an exhaustive list of changes, see #2323
!no-release-note

Okay so I removed the alt forge and proxy bits, and added the project init command to the GS. The GS needs more updates, but I have a separate ticket for that on the Kanban, so I'll get back to it after Thanksgiving :)


upload old data cache folder to recover data?

Can a cached folder be uploaded to recover lost data?
The cache folder before the computer crashed is about 200 GB.
The computer is gone.
The data was never uploaded for 3 months.
Is the data recoverable from the cache folder?
Thanks

That's a question for our support team at<EMAIL_ADDRESS>Be sure to write from the email address associated with your account and mention the name of the device that uploaded the files you are trying to recover. Also describe the cache you are asking about.
If I understand you correctly (and I might not be), no. The way to recover data is selecting it in the Manage tab of the application and downloading from there. The desktop application is better suited than the mobile client for this, by the way.

So data that is ready to be uploaded is not stored in the cache file?
Support wasn't helpful.
I know the official way to recover is through the management tab.  I am wondering how the information is stored and how I can decrypt it myself or perform the upload only so I can then go into the management tab and download the information normally since it never uploaded for 3 months, which the software didn't warn me about by the way which in my humble opinion is an epic fail.  The software offered ZERO notifications about anything actually.


Mark alpha.kubernetes.io/provided-node-ip as alpha

The annotation is alpha, so record that detail.

LGTM
Thanks @sftim
/lgtm

/approve


Adjust a test for error URL added in Pydantic 2.7.0

One test, tests/test_tutorial/test_path_params/test_tutorial005.py::test_get_enums_invalid, has started failing with Pydantic 2.7.0
The failure is easily reproduced by checking out the current master, 3425c834cc113060d00b8a295d3456eb306a109d, and running the tests as described in https://fastapi.tiangolo.com/contributing/#tests.
This PR adapts that test for the new error URL included in the response to the validation failure.

It seems like the lint failure is not related to this PR:
fastapi/openapi/utils.py:126: error: Incompatible types in assignment (expression has type "deprecated | str | Literal[True]", target has type "dict[str, Any] | bool | str")  [assignment]

Thank you! I just updated those tests and also how these things work. Including the removal of the URL from errors. So this is now handled. But thanks for the work! :coffee:

Thank you! I just updated those tests and also how these things work. Including the removal of the URL from errors. So this is now handled. But thanks for the work! ☕

Wonderful; that is much better. Thank you for the update!


strange fuzzy results, deletes what should be preserved

Well can't get the point why, but it's happening.
[root@db4 galera_backup]# cat /etc/rotate-backups.ini
[/galera_backup]
hourly = 3
daily = 1
weekly = 0
monthly = 0
yearly = 0
ionice = idle

Mind the "Deleting directory" in the second example. The only change is in "hour" in "timestamp".
[root@db4 galera_backup]# /bin/rotate-backups -nv -x '*'$(date  --date="1 days ago" "+%Y-%m-%d")'*'
2016-03-17 12:54:35 db4.sl.example.lab rotate_backups.cli[36454] INFO Performing a dry run (because of -n option) ..
2016-03-17 12:54:35 db4.sl.example.lab rotate_backups[36454] DEBUG Using configuration file /etc/rotate-backups.ini ..
2016-03-17 12:54:35 db4.sl.example.lab rotate_backups[36454] DEBUG Using configuration file /etc/rotate-backups.ini ..
2016-03-17 12:54:35 db4.sl.example.lab rotate_backups[36454] INFO Scanning directory for backups: /galera_backup
2016-03-17 12:54:35 db4.sl.example.lab rotate_backups[36454] DEBUG Excluded 'galera_backup_db4.sl.example.lab_2016-03-16_12-00' (it matched the exclude list).
2016-03-17 12:54:35 db4.sl.example.lab rotate_backups[36454] DEBUG Excluded 'galera_backup_db4.sl.example.lab_2016-03-16_22-00' (it matched the exclude list).
2016-03-17 12:54:35 db4.sl.example.lab rotate_backups[36454] INFO Found 3 timestamped backups in /galera_backup.
2016-03-17 12:54:35 db4.sl.example.lab rotate_backups[36454] INFO Preserving /galera_backup/galera_backup_db4.sl.example.lab_2016-03-17_12-00 (matches 'daily' retention period) ..
2016-03-17 12:54:35 db4.sl.example.lab rotate_backups[36454] INFO Preserving /galera_backup/galera_backup_db4.sl.example.lab_2016-03-17_16-00 (matches 'hourly' retention period) ..
2016-03-17 12:54:35 db4.sl.example.lab rotate_backups[36454] INFO Preserving /galera_backup/galera_backup_db4.sl.example.lab_2016-03-17_18-00 (matches 'hourly' retention period) ..
2016-03-17 12:54:35 db4.sl.example.lab rotate_backups[36454] INFO Nothing to do! (all backups preserved)
[root@db4 galera_backup]#

[root@db4 galera_backup]# date
Thu Mar 17 12:57:34 CET 2016

[root@db4 galera_backup]# mv /galera_backup/galera_backup_db4.sl.example.lab_2016-03-17_18-00 /galera_backup/galera_backup_db4.sl.example.lab_2016-03-17_10-00

[root@db4 galera_backup]# /bin/rotate-backups -nv -x '*'$(date  --date="1 days ago" "+%Y-%m-%d")'*'
2016-03-17 12:58:01 db4.sl.example.lab rotate_backups.cli[37843] INFO Performing a dry run (because of -n option) ..
2016-03-17 12:58:01 db4.sl.example.lab rotate_backups[37843] DEBUG Using configuration file /etc/rotate-backups.ini ..
2016-03-17 12:58:01 db4.sl.example.lab rotate_backups[37843] DEBUG Using configuration file /etc/rotate-backups.ini ..
2016-03-17 12:58:01 db4.sl.example.lab rotate_backups[37843] INFO Scanning directory for backups: /galera_backup
2016-03-17 12:58:01 db4.sl.example.lab rotate_backups[37843] DEBUG Excluded 'galera_backup_db4.sl.example.lab_2016-03-16_12-00' (it matched the exclude list).
2016-03-17 12:58:01 db4.sl.example.lab rotate_backups[37843] DEBUG Excluded 'galera_backup_db4.sl.example.lab_2016-03-16_22-00' (it matched the exclude list).
2016-03-17 12:58:01 db4.sl.example.lab rotate_backups[37843] INFO Found 3 timestamped backups in /galera_backup.
2016-03-17 12:58:01 db4.sl.example.lab rotate_backups[37843] INFO Preserving /galera_backup/galera_backup_db4.sl.example.lab_2016-03-17_10-00 (matches 'daily' retention period) ..
2016-03-17 12:58:01 db4.sl.example.lab rotate_backups[37843] INFO Deleting directory /galera_backup/galera_backup_db4.sl.example.lab_2016-03-17_12-00 ..
2016-03-17 12:58:01 db4.sl.example.lab rotate_backups[37843] INFO Preserving /galera_backup/galera_backup_db4.sl.example.lab_2016-03-17_16-00 (matches 'hourly' retention period) ..

# root owned are created manually, for testing
# the 11-00-00 was added later
#
[root@db4 galera_backup]# ll
total 12
drwxr-xr-x 6 mysql mysql 4096 Mar 16 00:08 galera_backup_db4.sl.example.lab_2016-03-16_12-00
drwxr-xr-x 6 mysql mysql 4096 Mar 16 20:33 galera_backup_db4.sl.example.lab_2016-03-16_22-00
drwxr-xr-x 2 root  root     6 Mar 17 12:54 galera_backup_db4.sl.example.lab_2016-03-17_10-00
drwxr-xr-x 2 root  root     6 Mar 17 12:59 galera_backup_db4.sl.example.lab_2016-03-17_11-00-00
drwxr-xr-x 6 mysql mysql 4096 Mar 16 20:33 galera_backup_db4.sl.example.lab_2016-03-17_12-00
drwxr-xr-x 2 root  root     6 Mar 17 12:54 galera_backup_db4.sl.example.lab_2016-03-17_16-00

Hi Petr, thanks for the feedback and sorry if rotate-backups unexpectedly rotated away more backups than you expected it to. This behavior can be explained (given the current algorithm for deciding which backups remain and which are rotated away) but that doesn't necessarily mean the behavior is satisfactory for you and/or other users.
Conceptual explanation
When you configure hourly=3 it means that the first backup in each of the past three hours (relative to the most recent backup) is preserved. Backups that are more than three hours old will be deleted unless they are matched by another rotation frequency.
Applied to the first example
In your first example the following three timestamps are used:

2016-03-17 12:00
2016-03-17 16:00
2016-03-17 18:00

18:00 minus three hours is 15:00 which matches backups 2 and 3 but not 1, however backup 1 fits in the slot for the daily backup and so is preserved as well.
Applied to the second example
In your second example the following three timestamps are used:

2016-03-17 10:00
2016-03-17 12:00
2016-03-17 16:00

16:00 minus three hours is 13:00 which matches only backup 3, however backup 1 fits in the slot for the daily backup and so is preserved as well.

I only just realized that you came to the same conclusion when you opened issue #3. I'll see if I can add an option to change this behavior as suggested there.

Exactly but anyway, thanks for explanation. Your code is rock solid. I understood the documentation wrong way. I vote for make the example above a part of the documentation.
The major difference is that I do not create backups "hourly" or so.. but at specified timers. Thus it doesn't do what expected - (as you wrote) the "default algorithm" do not match all user needs. #3 address that to make your piece of code even more usable. Thanks.


API call /flow_manager/v2/flows on POST is returning misleading response status

@hdiogenes @italovalcy @ajoaoff @rmotitsuki

If the payload items field is empty, it returns 200 when it should be 400.
reflected on end-to-end test:
tests/test_e2e_20_flow_manager.py::TestE2EFlowManager::test_016_install_flows_should_fail

Code:
def test_016_install_flows_should_fail(self):

        payload = {}

        api_url = KYTOS_API + '/flow_manager/v2/flows'
        response = requests.post(api_url, data=json.dumps(payload),
                                 headers={'Content-type': 'application/json'})
        assert response.status_code == 400

The same happens with these cases:
payload = {
            "flows": [
            ]
        }

and
payload = {
            "flows": [
                {

                }
            ]
        }

A not serializable JSON broke the application and it should return a 400 error.
case:

payload = {
            "flows": [
                {
                    "priority"
                }
            ]
        }

The issue mentioned above should be verified for any  not serializable JSON

Hi @ArturoQuintana, I think maybe have a misconception in the third case of the error you have reported.
The error: not serializable JSON, occurs because of the test itself. The json.dumps cannot make this data serializable. In addition, I am working to solve the other cases in the PR https://github.com/kytos/flow_manager/pull/137

Hi @cmagnobarbosa, thanks for getting back to me about this.
I am sorry about the misconception on this report from my side.
Kytos documentation specifies that 400 response code belong to all the cases that the JSON flow is not valid (https://napps.kytos.io/kytos/flow_manager)
A not serializable JSON match to that class, or not?
If not, we should not take care of this, but how will the Napp behave if it receives a not serializable JSON? is the code caring about this possibility? How do we guarantee the Napp will always receive a serializable JSON?

Hi, @ArturoQuintana thanks for the reply.
A JSON that is not well-formed, including all data that is not in the expected format, will be handled. If NApp receives data such as that reported in the not-serializable case, the error will be handled to avoid this error from interrupting NApp.


Create screen test with ocr

Added more selftest using cursor aptitude

Looks like the package-lock was massively changed in this PR, can you undo the changes to that? You may need to use node v16, it looks like you may be on an earlier version and it's changing the file.


doc: add docs for dealing with special characters in ref names

Why:
There are a few places in the UI where we provide instructions for how to do things on the command-line. We can provide shell-friendly escaped versions of most branch names, but there will always be some edge-casey ones (eg. names containing single quotes) for which the escaping rules vary subtly by shell. Rather than try to cram a dozen variants of the commands into the UI, we want to direct people to the docs for such problematic names.
What's being changed:
The intent here is not to document every shell's rules (doomed to be incomplete and become stale over time), but rather provide a flavour of what users should be aware of, and some helpful links to jumping off to official upstream docs for commonly-used shells.
Closes: https://github.com/github/coding/issues/2388

Check off the following:

[x] I have reviewed my changes in staging (look for the latest deployment event in your pull request's timeline, then click View deployment).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

cc @codeminator and @georgebrock

@wincent
Thanks so much for opening a PR! I'll get this triaged for review :zap:

@ramyaparimi any thoughts on when this PR will be reviewed?

@codeminator Thanks for reaching out.
We have a limited set of resources to pull from in order to get work done in the open source repository. We do our best to get things addressed as quickly as possible. Unfortunately, we can’t promise exactly when this will be handled, but rest assured that it is in the hands of the proper team and we’ll get to it as rapidly as we can with resources and other priorities in mind.
Thanks for your patience and your contributions to the GitHub docs.

👋 Thanks a lot for providing the content for this article, @wincent! 🙇♂ I'm sorry that it's taken us a while to get to reviewing this.
I've push up an edit in https://github.com/github/docs/pull/9577/commits/1b903fcff36197e524c9283b39f0a3dab0986e1f, which breaks the content up into digestible sections, and also made some wording/formatting edits for it to align with our style guides and language recommendations.
Please let me know if I've unintentionally changed the meaning of anything that makes it incorrect.
Because I've made significant changes, I'll get someone else on the team to give it a quick review of my changes.

Thanks, @martin389! 🙇♂
@wincent Let me know if you're happy to get this merged in 🙂

Let me know if you're happy to get this merged in

@lucascosti, thanks for the edits and @martin389, thanks for the review! This looks great to me.


,"hash or mismatch file has been modified or corrupted?" Help.

Description
Yesterday, I updated to tModLoader v<IP_ADDRESS> and got the update, I tested multiplayer with my friend, then a few hours later, I got this:
Hash mismatch, data blob has been modified or corrupted
at Terraria.ModLoader.IO.TmodFile.Read(LoadedState desiredState, ReadStreamingAsset streamingHandler)
at Terraria.ModLoader.ModLoader.FindMods()
Whats going on? I checked the Tmod loader discord and supposedly, the latest version fixed this problem but I still got the problem that was supposedly fixed. I must of redownloaded TmodLoader at least 10 times...
Steps to Reproduce

Redownload TmodLoader
Extract with Winrar
Replace Terraria Files with TmodLoader Files in their destination.
Launch Game and Enjoy.

Expected behavior
Everything works properly and enjoy the game.
Actual behavior
I get the same message shown above making me non-accessible to my mods in-game.
Reproduction frequency
Every, Single, Time I redo the process.
Version
TmodLoader v<IP_ADDRESS>
Mods

Calamity Mod v<IP_ADDRESS>: on
Fargos Mutant Mod: on
Shorter Respawn Time: on
AlchemistNPC: on
HEROs Mod: off
Another Boss Healthbar: on
Joost Mod v0.6.4: on
Auto Trash: on
Crystilium v<IP_ADDRESS>: on
Recipe browser v0.6: on
Spirit mod v<IP_ADDRESS>: on
Tremor Mod Remastered v<IP_ADDRESS>: on
Thorium mod v<IP_ADDRESS>: on
Boss checklist v<IP_ADDRESS>: on
Yet another boss health bar 1.2.1: on

(Oh yeah, I cant change the off/on Because I can't access my mods folder In-game or else i'll get the above...)
Additional Information
This just happened when I Installed the latest version of TmodLoader. This never happened when I started with the old version v<IP_ADDRESS> til I updated to the new TmodLoader v<IP_ADDRESS>. Please Help, and thanks.

Duplicate of #315

oh, i didn't that, thanks


Weird output if a contracted function references instance methods via self.anything

I already reported a similar issue in #6, but it turned out that this was not because of the return type, but because of something else, the use of self.anything!
Documentation for the following is generated fine:
class User
  def foo
    self.username
  end
end

While the following has the "two method" problem as descroibed above:
class User
  include Contracts

  Contract None => String
  def foo
    self.username
  end
end

So as soon I have an occurence of self.anything in the function the problem occurs. Even if I could circumvent the usage of self by renaming the parameter, I prefer to always use self for calling methods of the current object.
It does not matter if I define the method username with a contract or without or leaving it undefined/implicitely created by ActiveRecord.
edit
Because I forgot to mention so far: I am using yard-contracts and contracts from rubygems.

Just tried with both gems from git master, problem is there too.

Aah thank you. Now I see what's happening.
yard-contracts registers a hook to be called on Contract method call. It then looks ahead to find the next method def call and documents it. Unfortunately YARD doesn't provide much info about the def call—it doesn't say whether it's a class or instance method. So currently I'm using match(/ self\./) to work out if it's a class method or not, I realise now that it's looking at the whole source of the method, not just the first line. Should be an easy fix with a stricter regex, but I don't want to make it too strict in case anyone formats their method definitions weirdly.
I'll try to fix it later today.

This sounds also as if you would not catch up Classmethods defined like this:
class Foo
  include Contracts
  class << self
    Contract None => String
    def bar
      'class method!'
    end
  end
end

Since I'm on my mobile right now, I can't test it by myself.
When I'm able to test this I will do and file a new issue if necessary (or someone else does faster than me).

Yep it wouldn't. It also won't work for define_method. If you can think of a better way feel free to make a pull request, but YARD + Ripper don't make it easy.

My knowledge about yard is only on how to use it, not on how to enhence it. But maybe the Yard-developers would be open for suggestions, so you can work together with them to enhence their interface.

I would go here with /def self./ - will not support singleton classes,
but will fix current bug.
On Apr 2, 2015 3:02 PM, "Norbert Melzer"<EMAIL_ADDRESS>wrote:

My knowledge about yard is only on how to use it, not on how to enhence
it. But maybe the Yard-developers would be open for suggestions, so you can
work together with them to enhence their interface.
—
Reply to this email directly or view it on GitHub
https://github.com/sfcgeorge/yard-contracts/issues/8#issuecomment-88888916
.

Yeah that's what I'm thinking. It also won't work if one uses the class name instead of self, but I don't know why you'd want to do that and it's against the style guide.
I think fixing singleton classes and define_method would require substantial AST parsing and I'm not sure it's worth it. I'll fix this first then suggestions welcome :)

This is now fixed with /def +self\./ and I've pushed a patch release to Rubygems. I'll close this issue as it's now fixed and maybe think about the more complex cases later.


Support to nativescript projects with angular

I see on an official nativescript angular project example, a nice .gitignore
I'm going to test it and then make a pull request.

This issue was moved to dvcs/gitignore#1


deploy ERC20PiptSwap

Codecov Report

Merging #76 (aae0e07) into master (eee739d) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #76   +/-   ##
=======================================
  Coverage   86.51%   86.51%
=======================================
  Files          35       35
  Lines        2129     2129
  Branches      313      313
=======================================
  Hits         1842     1842
  Misses        287      287

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update eee739d...aae0e07. Read the comment docs.


Update install instructions to include Jira 9 hint

Summary
Ticket Link
Fixes https://github.com/mattermost/mattermost-plugin-jira/issues/907

@mickmister If it's super quick - can we do a line wrap and the word Note in bold here to make it obvious instructions have changed?
If it crates formatting complications I'm fine with it as is.

Merged and cherry-picked into release-3.2.3


handlebars

We started on these templates, I am planning to work more on these tomorrow. Main, Login, and Dashboard templates have been created to where they will render with routes. I have added a public folder with the images and css. We will begin working on the js tomorrow.


refactor!: Split Logs

Split logs into firstMonth, lastMonth - both in query and mutation
Preserve all existing data
Test it

@RickiJay-WMDE This seems to need a rebase :(


Add ability to show task disk resource if configured to do so

Exactly what it says on the tin.
If config.showTaskDiskResource is true, the disk resource will be shown on the tasks table and as an option on the New Deploy form.
cc @tpetr @kwm4385 @wolfd

LGTM


see what happens if we migrate a library

Replace this paragraph with a description of what this PR is changing or adding, and why. Consider including before/after screenshots.
List which issues are fixed by this PR. You must list at least one issue.
If you had to change anything in the flutter/tests repo, include a link to the migration guide as per the breaking change policy.
Pre-launch Checklist

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I signed the CLA.
[ ] I listed at least one issue that this PR fixes in the description above.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] I added new tests to check the change I am making or feature I am adding, or Hixie said the PR is test-exempt.
[ ] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Approving for science

Science!
ERROR: third_party/dart/flutter_tools/lib/src/base/async_guard.dart

83: Function? onError, Null safety is not enabled for this file. http://go/dart-null-safety-not-enabled #experiment_not_enabled

/third_party/dart/flutter_tools/lib/src/base/async_guard.dart:83:11: Error: Null safety features are disabled for this library.
Try removing the package language version or setting the language version to 2.12 or higher.
  Function? onError,
          ^