Outputs differ from Targets

@sooftware Can you kindly explain to me why the output lengths and targets are so different? :/ (also in outputs I get negative floats). Example shown below
The outputs are of shape [32,490,16121] (where 16121 is the len of my vocab) What is the 490 dimensions
Also the outputs are probabilities right?
(outputs)
tensor([[[-9.7001, -9.6490, -9.6463,  ..., -9.6936, -9.6430, -9.7431],
         [-9.6997, -9.6487, -9.6470,  ..., -9.6903, -9.6450, -9.7416],
         [-9.6999, -9.6477, -9.6479,  ..., -9.6898, -9.6453, -9.7417],
         ...,
         [-9.7006, -9.6449, -9.6513,  ..., -9.6889, -9.6477, -9.7405],
         [-9.7003, -9.6448, -9.6512,  ..., -9.6893, -9.6477, -9.7410],
         [-9.7007, -9.6453, -9.6513,  ..., -9.6892, -9.6466, -9.7403]],

        [[-9.6844, -9.6316, -9.6387,  ..., -9.6880, -9.6269, -9.7657],
         [-9.6834, -9.6299, -9.6404,  ..., -9.6872, -9.6283, -9.7642],
         [-9.6834, -9.6334, -9.6387,  ..., -9.6864, -9.6290, -9.7616],
         ...,
         [-9.6840, -9.6299, -9.6431,  ..., -9.6830, -9.6304, -9.7608],
         [-9.6838, -9.6297, -9.6428,  ..., -9.6834, -9.6303, -9.7609],
         [-9.6842, -9.6300, -9.6428,  ..., -9.6837, -9.6292, -9.7599]],

        [[-9.6966, -9.6386, -9.6458,  ..., -9.6896, -9.6375, -9.7521],
         [-9.6974, -9.6374, -9.6462,  ..., -9.6890, -9.6369, -9.7516],
         [-9.6974, -9.6405, -9.6456,  ..., -9.6876, -9.6378, -9.7491],
         ...,
         [-9.6978, -9.6336, -9.6493,  ..., -9.6851, -9.6419, -9.7490],
         [-9.6971, -9.6334, -9.6487,  ..., -9.6863, -9.6411, -9.7501],
         [-9.6972, -9.6338, -9.6489,  ..., -9.6867, -9.6396, -9.7497]],

        ...,

        [[-9.7005, -9.6249, -9.6588,  ..., -9.6762, -9.6557, -9.7555],
         [-9.7028, -9.6266, -9.6597,  ..., -9.6765, -9.6574, -9.7542],
         [-9.7016, -9.6240, -9.6605,  ..., -9.6761, -9.6576, -9.7553],
         ...,
         [-9.7036, -9.6237, -9.6624,  ..., -9.6728, -9.6590, -9.7524],
         [-9.7034, -9.6235, -9.6620,  ..., -9.6735, -9.6589, -9.7530],
         [-9.7038, -9.6240, -9.6622,  ..., -9.6738, -9.6582, -9.7524]],

        [[-9.7058, -9.6305, -9.6566,  ..., -9.6739, -9.6557, -9.7466],
         [-9.7061, -9.6273, -9.6569,  ..., -9.6774, -9.6564, -9.7499],
         [-9.7046, -9.6280, -9.6576,  ..., -9.6772, -9.6575, -9.7498],
         ...,
         [-9.7060, -9.6263, -9.6609,  ..., -9.6714, -9.6561, -9.7461],
         [-9.7055, -9.6262, -9.6605,  ..., -9.6723, -9.6558, -9.7469],
         [-9.7058, -9.6270, -9.6606,  ..., -9.6725, -9.6552, -9.7460]],

        [[-9.7101, -9.6312, -9.6570,  ..., -9.6736, -9.6551, -9.7420],
         [-9.7102, -9.6307, -9.6579,  ..., -9.6733, -9.6576, -9.7418],
         [-9.7078, -9.6281, -9.6598,  ..., -9.6704, -9.6596, -9.7418],
         ...,
         [-9.7084, -9.6288, -9.6605,  ..., -9.6706, -9.6588, -9.7399],
         [-9.7081, -9.6286, -9.6600,  ..., -9.6714, -9.6584, -9.7406],
         [-9.7085, -9.6291, -9.6601,  ..., -9.6717, -9.6577, -9.7398]]],
       device='cuda:0', grad_fn=<LogSoftmaxBackward0>)

(output_lengths)
tensor([312, 260, 315, 320, 317, 275, 308, 291, 272, 300, 262, 227, 303, 252,
        298, 256, 303, 251, 284, 259, 263, 286, 209, 262, 166, 194, 149, 212,
        121, 114, 110,  57], device='cuda:0', dtype=torch.int32)

(target_lengths)
tensor([57, 55, 54, 50, 49, 49, 49, 48, 48, 47, 43, 42, 41, 40, 40, 39, 37, 37,
        36, 36, 36, 35, 34, 33, 29, 27, 26, 24, 20, 19, 17,  9])

I am using the following code for training and evaluation
import torch
import time
import sys
from google.colab import output
import torch.nn as nn
from conformer import Conformer
import torchmetrics
import random

cuda = torch.cuda.is_available()
device = torch.device('cuda' if cuda else 'cpu')
print('Device:', device)

################################################################################

def train_model(model, optimizer, criterion, loader, metric):
  running_loss = 0.0
  for i, (audio,audio_len, translations, translation_len) in enumerate(loader):
    # with output.use_tags('some_outputs'):
    #   sys.stdout.write('Batch: '+ str(i+1)+'/290')
    #   sys.stdout.flush();

    #sorting inputs and targets to have targets in descending order based on len
    sorted_list,sorted_indices=torch.sort(translation_len,descending=True)

    sorted_audio=torch.zeros((32,201,1963),dtype=torch.float)
    sorted_audio_len=torch.zeros(32,dtype=torch.int)
    sorted_translations=torch.zeros((32,78),dtype=torch.int)
    sorted_translation_len=sorted_list

    for index, contentof in enumerate(translation_len):
      sorted_audio[index]=audio[sorted_indices[index]]
      sorted_audio_len[index]=audio_len[sorted_indices[index]]
      sorted_translations[index]=translations[sorted_indices[index]]

    #transpose inputs from (batch, dim, seq_len) to (batch, seq_len, dim)
    inputs=sorted_audio.to(device)
    inputs=torch.transpose(inputs, 1, 2)
    input_lengths=sorted_audio_len
    targets=sorted_translations.to(device)
    target_lengths=sorted_translation_len

    optimizer.zero_grad()

    # Forward propagate
    outputs, output_lengths = model(inputs, input_lengths)
    # print(outputs)

    # Calculate CTC Loss
    loss = criterion(outputs.transpose(0, 1), targets, output_lengths, target_lengths)

    loss.backward()
    optimizer.step()

    # print statistics
    running_loss += loss.item()

    output.clear(output_tags='some_outputs')

  loss_per_epoch=running_loss/(i+1)
  # print(f'Loss: {loss_per_epoch:.3f}')

  return loss_per_epoch

################################################################################

def eval_model(model, optimizer, criterion, loader, metric):
  running_loss = 0.0
  wer_calc=0.0
  random_index_per_epoch= random.randint(0, 178)

  for i, (audio,audio_len, translations, translation_len) in enumerate(loader):
    # with output.use_tags('some_outputs'):
    #   sys.stdout.write('Batch: '+ str(i+1)+'/72')
    #   sys.stdout.flush();

    #sorting inputs and targets to have targets in descending order based on len
    sorted_list,sorted_indices=torch.sort(translation_len,descending=True)

    sorted_audio=torch.zeros((32,201,1963),dtype=torch.float)
    sorted_audio_len=torch.zeros(32,dtype=torch.int)
    sorted_translations=torch.zeros((32,78),dtype=torch.int)
    sorted_translation_len=sorted_list

    for index, contentof in enumerate(translation_len):
      sorted_audio[index]=audio[sorted_indices[index]]
      sorted_audio_len[index]=audio_len[sorted_indices[index]]
      sorted_translations[index]=translations[sorted_indices[index]]

    #transpose inputs from (batch, dim, seq_len) to (batch, seq_len, dim)
    inputs=sorted_audio.to(device)
    inputs=torch.transpose(inputs, 1, 2)
    input_lengths=sorted_audio_len
    targets=sorted_translations.to(device)
    target_lengths=sorted_translation_len

    # Forward propagate
    outputs, output_lengths = model(inputs, input_lengths)
    # print(outputs)

    # Calculate CTC Loss
    loss = criterion(outputs.transpose(0, 1), targets, output_lengths, target_lengths)

    print(output_lengths)
    print(target_lengths)
    # outputs_in_words=words_vocab.convert_pred_to_words(outputs.transpose(0, 1))
    # targets_in_words=words_vocab.convert_pred_to_words(targets)
    # wer=metrics_calculation(metric, outputs_in_words,targets_in_words)

    break

    if (i==random_index_per_epoch):
        print(outputs_in_words,targets_in_words)

    running_loss += loss.item()
    # wer_calc += wer

    output.clear(output_tags='some_outputs')

  loss_per_epoch=running_loss/(i+1)
  wer_per_epoch=wer_calc/(i+1)

  return loss_per_epoch, wer_per_epoch

################################################################################

def train_eval_model(epochs):
  #conformer model init
  model = nn.DataParallel(Conformer(num_classes=16121, input_dim=201, encoder_dim=32, num_encoder_layers=1)).to(device)

  # Optimizers specified in the torch.optim package
  optimizer = torch.optim.Adam(model.parameters(), lr=0.0001, betas=(0.9, 0.98), eps=1e-9)

  #loss function
  criterion = nn.CTCLoss().to(device)

  #metrics init
  metric=torchmetrics.WordErrorRate()

  for epoch in range(epochs):
    print("Epoch", epoch+1)

    ############################################################################
    #TRAINING
    model.train()
    print("Training")

    # epoch_loss=train_model(model=model,optimizer=optimizer, criterion=criterion, loader=train_loader, metric=metric)

    # print(f'Loss: {epoch_loss:.3f}')
    # print(f'WER: {epoch_wer:.3f}')

    ############################################################################
    #EVALUATION
    model.train(False)
    print("Validation")

    epoch_val_loss, epoch_val_wer=eval_model(model=model,optimizer=optimizer, criterion=criterion, loader=test_loader, metric=metric)

    print(f'Loss: {epoch_val_loss:.3f}')
    print(f'WER: {epoch_val_wer:.3f}')

################################################################################

def metrics_calculation(metric, predictions, targets):
    print(predictions)
    print(targets)
    wer=metric(predictions, targets)

    return wer

train_eval_model(1)

Output length means the speech signal's length. (It became 1/4 by the conv module.)
The target length is the length of the character uttered in this speech signal. These two are different things.
Taking the CTC below as an example, the length of the voice is very long, but the hello spoken here is five letters.
This can be processed in a sequence tagging method like CTC, or a decoder can be attached separately to predict one by one.

Try converting the actual audio signal into spectrogram and input it. Is "loss" negative?

Output length means the speech signal's length. (It became 1/4 by the conv module.) The target length is the length of the character uttered in this speech signal. These two are different things. Taking the CTC below as an example, the length of the voice is very long, but the hello spoken here is five letters. This can be processed in a sequence tagging method like CTC, or a decoder can be attached separately to predict one by one.

so I either use the CTC loss either a single layer LSTM Decoder (as proposed in the paper)? What if I want to check the accuracy? e.g take the predicted word sequence vs the target

Try converting the actual audio signal into spectrogram and input it. Is "loss" negative?

I am converting the audio files in MelSpec before adding them to my dataloaders

CTC Loss was not used in the Conformer paper.
If you have a decoder separately, you can use Cross Entry Loss instead of CTC Loss.
If you want to check the accuracy, it would be nice to study speech recognition model training.

@sooftware in the paper they are using a single layer LSTM Decoder
so i need to construct one to feed the outputs of the encoder to produce results?

Yes, but as far as I remember, in Conformer paper, they used LSTM transducer decoder.

yes, do you have any source i can find more about it?

Check https://github.com/openspeech-team/openspeech


Expect test fail for mysql-simple, too - no server

You'll need to exclude the mysql-simple test too - sorry, I forgot about this problem.

This is not necessary as mysql-simple doesn't have a test-suite

OK, I'm jumping the gun just a little.  It will have one as soon as it is released.  By all means hold this patch for a day or so until I've had a chance to check and release the latest version.

As long as you are aware of it!


CODE block breaks in MS Edge

I referenced the following on MS Edge:
https://themes.gohugo.io//theme/indigo/post/markdown-syntax/
As a result, one line space is left in CODE block:

Chrome and Firefox don't have this, but some Windows users will care.

found this solution:
code {
    display: block;
}

CSS may need additional tweaking, but it is a separate issue.

Thanks for opening this! Code blocks in general could be improved, as they don't play very nicely with Hugo's highlight shortcodes either.

I think this was fixed at some point, maybe with the new Markdown renderer? I don't see this extra-linebreak issue in Edge anymore (the syntax highlighting in #89 is still a problem, though, and I'm fixing it now).
Closing as wontfix, but please don't hesitate to re-open if you continue to see an issue!


695: Add --format Flag to "zally rules" Command

Closes #695

Codecov Report

Merging #707 into master will decrease coverage by 0.07%.
The diff coverage is 84.61%.

@@             Coverage Diff              @@
##             master     #707      +/-   ##
============================================
- Coverage     83.86%   83.78%   -0.08%
  Complexity      883      883
============================================
  Files           158      159       +1
  Lines          2380     2387       +7
  Branches        339      339
============================================
+ Hits           1996     2000       +4
- Misses          232      234       +2
- Partials        152      153       +1

Impacted Files
Coverage Δ
Complexity Δ

cli/zally/commands/lint.go
81.33% <100%> (-2.76%)
0 <0> (ø)

cli/zally/app.go
100% <100%> (ø)
0 <0> (ø)
:arrow_down:

cli/zally/utils/formatters/factories.go
100% <100%> (ø)
0 <0> (?)

cli/zally/commands/supported_rules.go
84.09% <42.85%> (-6.39%)
0 <0> (ø)

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 7494e3d...f4ed08c. Read the comment docs.

:+1:

@maxim-tschumak could you please check it again?

:+1:

:+1:


Rename roi_align_2d to roi_average_align_2d

This is a tentative fix (should be removed in #5198) to keep compatibility between betas.

@toslunar Can you check?

Jenkins CI test (for commit ae7d6ad97228074960532c8d29c40bfa956d662b, target branch master) succeeded!


The fsc node approver and iou process memory leak, the memory grows to 16G in about 10 minutes under 50-60TPS and exits abnormally

@yaofeiliang , this is very interesting. Can you give us more information? Do you have profile data that you can share for us to analyze? Do you know where the memory is leaked?

Hi @yaofeiliang
can you please provide additional information which let me reproduce this issue. I was wondering how you invoke the 50k transactions? How did you measure the memory consumption?
Could you also try to enable monitoring in the IOU topology and share the Grafana logs.
	// Monitoring
	monitoringTopology := monitoring.NewTopology()
	//monitoringTopology.EnableHyperledgerExplorer()
	monitoringTopology.EnablePrometheusGrafana()

	return []api.Topology{
		fabricTopology,
		fscTopology,
		monitoringTopology,
	}

Once the network is up and running using ./iou network start --path ./testdata, you can log into Grafana via your browser on localhost:3000 as admin with the default password admin.
The Fabric Backend Dashboard will show you the memory consumption of the FSC nodes and Fabric peers.
To run some workload over time I was testing with the following script but I did not observe any abnormal memory consumption.
#!/usr/bin/env bash

outFile="out.txt"

for i in {1..1000}; do
  echo "run: $i"
  ./iou view -c ./testdata/fsc/nodes/borrower/client-config.yaml -f create -i "{\"Amount\":10}" > $outFile
  id=$(head -n 1 $outFile | tr -d '"'s)
  ./iou view -c ./testdata/fsc/nodes/borrower/client-config.yaml -f query -i "{\"LinearID\":\"$id\"}"
  ./iou view -c ./testdata/fsc/nodes/lender/client-config.yaml -f query -i "{\"LinearID\":\"$id\"}"
  ./iou view -c ./testdata/fsc/nodes/borrower/client-config.yaml -f update -i "{\"LinearID\":\"$id\",\"Amount\":8}"
done

@adecaro @mbrandenburger

After executing the script concurrently
number of transactions 2307;
Memory usage:
iou 1.98G;
approver 1.13G;
borrower 1.08G;
lender 609.2M;
and increasing as transactions grow

Hi @yaofeiliang , fantastic data. Thanks a lot for this feedback.
Please, could you check the folder where the FSC node configuration is (core.yaml)? There you should be able to find the cpu, memory, and locks profile that are automatically generated when you shut down an FSC node.
I think this can give us additional information :)

@yaofeiliang it seems that the current way of logging the FSC nodes and processes causes this heavy memory usage. Since the IOU sample builds on top of the integration test suite, all logging is kept in memory to allow anaylizing the output of the processes. However, this is not the right way to do that when you have a long running setup with many transactions. We will look into that.

@mbrandenburger Loyal fans look forward to memory problem solved.


Uncaught TypeError: Cannot read property 'mainModule' of undefined

[Enter steps to reproduce below:]

...
...

 I'll look into the matter. Thanks for your feedback @57ar7up

I'm sorry @57ar7up I am unable to reproduce the problem. Can you please tell me steps to reproduce the problem?

It's appears when I press Escape

@57ar7up Does the bug appear every time u press Escape or only at some instances. And if later is the case, the can you please elaborate it?

I do have the same bug and it appears every time I press Escape.

I think the error comes when you press escape before activating the find-and-replace atleast once. Correct me if I am wrong

Yes

I got the problem. I'll be working on it. Thanks for the feedback :)

Scroll searcher has been updated. Due to recent shadow dom update, this new version will only work with Atom >= v1.13.0.
https://atom.io/packages/scroll-searcher

I am closing the issue. Please reopen the issue if required.


Assertion Error when training

I run the code as GetStarted_Standalone(but deleted the --master, just use the default value). Then finally the terminal shows me that
zipping images and labels
2018-04-07 05:54:19 INFO  FileInputFormat:249 - Total input paths to process : 10
2018-04-07 05:54:19 INFO  FileInputFormat:249 - Total input paths to process : 10
2018-04-07 05:54:19,721 INFO (MainThread-1843) Reserving TFSparkNodes
Traceback (most recent call last):
  File "/mnt/aruyuna/TensorflowOnSpark/TensorFlowOnSpark/examples/mnist/spark/mnist_spark.py", line 68, in <module>
    cluster = TFCluster.run(sc, mnist_dist.map_fun, args, args.cluster_size, num_ps, args.tensorboard, TFCluster.InputMode.SPARK, log_dir=args.model)
  File "build/bdist.linux-x86_64/egg/tensorflowonspark/TFCluster.py", line 221, in run
AssertionError

When we set --master yarn there's also these messages.
Then I try the Hadoop Cluster, it's also failed:
2018-04-07 06:27:08 INFO  Client:54 -
	 client token: N/A
	 diagnostics: N/A
	 ApplicationMaster host: <IP_ADDRESS>
	 ApplicationMaster RPC port: 0
	 queue: default
	 start time:<PHONE_NUMBER>814
	 final status: FAILED
	 tracking URL: http://aruyuna:8088/proxy/application_1523030059313_0006/
	 user: hduser
Exception in thread "main" org.apache.spark.SparkException: Application application_1523030059313_0006 finished with failed status

When I check the tracking log, I can also find that "AssertionError".
How can I solve this problem? Thanks very much.
Tensorflow Type=gpu version=1.4
cuda version=7.5
TensorflowOnSpark version=1.2.1
Hadoop version=2.7.4
Spark version=2.3.0
Python version=2.7.6

Solved.

Could you please tell me how to solve this problem

@SeanNew you can take a look at the source to see what the assert is, e.g. TFCluster.py:221.  I'll add debug/error msgs for these asserts in the near future.


Routing HTTP Exceptions through Controller

Background
the framework currently allows you to easily define views for specific HTTP status code responses.  For example, an HTTP status code of 404 will display the resources/views/errors/404.blade.php view automatically if it exists.  it works the same for other codes like 500 errors.
Problem
All of the routes on my site are processed through controllers, all of which extend a base Controller.  This base controller sometimes initializes the user, sets the current timezone, and other random stuff. The master template often relies on these variables. For example, if a user is logged in, the Controller figures that out and passes that user to the view. My master template looks for that user, and shows certain functionality if present. When a 404 is hit, I want to still be able to show the user specific menus, and continue using that 404 view.
Proposal
IMHO it would be ideal if the framework would still catch those exceptions, but instead of immediately rendering the view, send them to a specific route. Then we could create an ErrorController with specific methods for each status code.
class ErrorController extends Controller
{
    public function e404() //method names cannot start with numbers
    {
        return view('errors.404');
    }
}

Before I start on a PR, I am looking for some feedback on this, to see if other people are running into a similar issue as me, and if they've come up with different (maybe better) solutions to it.
Thanks!

Deal with this in your exception handler.

It is technically possible for you to get this to work with custom code.

i'm sure it is, but i was curious if it was a problem for other people as well. And if so, that we could make an internal change to make it easier for everyone.
Is there a use case where immediately rendering the view is preferential, and routing through a controller would be undesired?

I'd say we definitely shouldn't change the current behaviour, but it is absolutely possible for you to get this behaviour if you want it. Just be careful though, because current if an exception is handled by the exception handler, the middleware system has already been broken out of, so anything that would have wrapped the response is no longer executed (ie, headers, cookies never get attached to the response).


fix pointer cursor in column headers

This ensures that the pointer cursor is only in use for the menu buttons and not the whole column headers.

I just realized that for collapsed columns, it does make sense to have the whole column area with this pointer, since clicking anywhere on the column header uncollapses the column. Worth opening a follow-up issue about this?


Z-index conflict with Magnific-Popup

Hi there!
After updating from 4 to 5, when sweetalert2 is fired inside a Magnific-Popup, it loses the z-index battle to it. Magnific-Popup has a wrapper under the body tag, called mfp-wrap, with a z-index of 1043 (magic number).
Sweetalert2 also has a wrapper under the body tag, called swal2-container, with a z-index of 1000. So it is fired bellow the magnific-popup, which is a problem.
This is easily solved by overwriting sweetalert2 z-index to a number above 1043, but would be possible, in order to enhance this plugin, to programmatically detected the needed z-index to ensure that sweetalert2 will fire up above everything? For example, detected which tag bellow body has the biggest z-index, then set the sweetalert2 z-index to that number + 1.
Best regards,
Rafael Pacheco.

Maybe we should just assign the max z-index value for .swal2-container? It's<PHONE_NUMBER>.

As sweetalert2 represents a popup that must be the top most frame, I think it's okay to max it up. But this number must be compatible with all browsers. Maybe a little less aggressive number, like 10000? I don't recall seeing any modal plugin which uses big z-indexes.

I'd probably say something around 1060. That would also put it above bootstrap modals. I wouldn't set it to the max because some plugins such as jquery datepicker attach to the body by default and would need to be above sweetalert for use in the modal.

nice point with a datepicker, I'll make it 1060.

Fixed in v5.0.5.
Thank you both @rafael-renan-pacheco for reporting and @samturrell for pointing out possible datepicker inside the swal2 modal.

I'm using MagnificPopUp 1.1.0 (latest) and sweetalert 7.0.5 (latest). The sweetalert modal is properly displayed and the buttons are clickable, but if I add a "password" field, I won't gain focus. I've increased the z-index, but it didn't seem to make any difference.  Is this the same issue as bootstrap?
CASE USE: I'm using MagnificPopUp to display product details (via Ajax) on a web-based POS. Any buttons with a specific class trigger sweetalert to display prompt to require an administrative passcode to override before continuing. It works, until the buttons are clicked within a MagnificPopUp modal.

@JamoCA I'm having the exact same issue right now. Any solution yet?

I think I've found my solution, just in case anyone wondering. Simplifying this: https://github.com/dimsemenov/Magnific-Popup/issues/897
I just add that line on magnific open callback. E.g:
$('.listing').magnificPopup({
    ....
    callbacks: {
        open: function() {
            // Disabling focus enforcement by magnific
            $.magnificPopup.instance._onFocusIn = function(e) {};
         }
    }
});


python: use built-in venv instead of virtualenv when installing formulae

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[ ] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?
[ ] Have you successfully run brew man locally and committed any changes?

This PR uses python's built-in venv to install formulae instead of the external virtualenv, which has dependencies and needs to be bootstrapped. The dependencies could also theoretically differ based on Python version.
Current caveat: venv uses ensurepip to install pip and setuptools using the wheels that are bundled with cpython, even if a newer one is installed, which is 20.2.3 for pip and 49.2.1 for setuptools in Python 3.9.1: https://github.com/python/cpython/blob/1e5d33e9b9b8631b36f061103a30208b206fd03a/Lib/ensurepip/init.py#L16-L18, https://github.com/python/cpython/tree/1e5d33e9b9b8631b36f061103a30208b206fd03a/Lib/ensurepip/_bundled
Other downstream package managers patch ensurepip to point to their locally managed pip and setuptools: https://src.fedoraproject.org/rpms/python3.9/blob/2084e749c71fe494a9a4ed76ce9c2d149b76868c/f/00189-use-rpm-wheels.patch, so that's a possible solution to ensure the temporary installation venv is using the latest versions that Homebrew knows about vs either using a known outdated version or blindly using the latest available in PyPI.
Marking as a draft for now and can look into writing new tests if it's decided to go in this direction.
Follow-up to #9435.

Review period will end on 2020-12-17 at 17:41:06 UTC.

Review period will end on 2020-12-17 at 17:41:06 UTC.

Review period ended.

Nice work, thanks @dtrodrigues!

Nice work, thanks @dtrodrigues!


linuxserver wireguard

hello.
I have wireguard with linuxserverio
I would like to connect ngoduykhanh/wireguard-ui with linuxserver/wireguard
but my config is wrong. when i had a user, nothing happen.
I write my docker-compose at the end of my post.
Thank you in advance for your reply.

version: "2.1"
services:
  wireguard:
    image: ghcr.io/linuxserver/wireguard
    container_name: wireguard
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Paris
      - SERVERURL=XXXXXXXXXXXX #optional
      - SERVERPORT=51820 #optional
      - PEERS=5 #optional
      - PEERDNS=auto #optional
      - INTERNAL_SUBNET=<IP_ADDRESS> #optional
      - ALLOWEDIPS=<IP_ADDRESS>/0 #optional
    volumes:
      - ./config:/config
      - ./modules:/lib/modules
    ports:
      - 51820:51820/udp
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
    restart: unless-stopped

  wireguard-ui:
    image: ngoduykhanh/wireguard-ui
    container_name: wireguard-ui
    ports:
      - 5000:5000
    logging:
      driver: json-file
      options:
        max-size: 50m
    volumes:
      - ./db:/app/db
      - /wireguard:/etc/wireguard
    links:
      - wireguard:wireguard

hi,
you have to point - /wireguard:/etc/wireguard to the wg0.conf file from wireguard.
I think in you're case it is - ./config:/etc/wireguard.
kind regards

Did you ever get this working? I was not able to. I did notice that the PUID and PGID in wireguard-ui are different than in the linuxserver wireguard container. I changed them and the permissions seem to line up but the client list doesn't change in wg0.conf.
original permissions:
/app # ls -lac /etc/wireguard
total 32
drwxr-xr-x    6 1000     1000          4096 May 31 23:44 .
drwxr-xr-x    1 root     root          4096 May 31 23:44 ..
-rw-------    1 1000     1000           156 May 31 23:44 .donoteditthisfile
drwxr-xr-x    2 1000     1000          4096 May 31 23:44 coredns
drwx------    2 1000     1000          4096 May 31 23:44 peer1
drwxr-xr-x    2 1000     1000          4096 May 31 23:44 server
drwxr-xr-x    2 1000     1000          4096 May 31 23:44 templates
-rw-------    1 1000     1000           485 May 31 23:44 wg0.conf

permissions with changed PUID/PGID:
/app # ls -lac /etc/wireguard
total 32
drwxr-xr-x    6 wgui     wgui          4096 May 31 23:30 .
drwxr-xr-x    1 root     root          4096 May 31 23:30 ..
-rw-------    1 wgui     wgui           156 May 31 23:30 .donoteditthisfile
drwxr-xr-x    2 wgui     wgui          4096 May 31 23:30 coredns
drwx------    2 wgui     wgui          4096 May 31 23:30 peer1
drwxr-xr-x    2 wgui     wgui          4096 May 31 23:30 server
drwxr-xr-x    2 wgui     wgui          4096 May 31 23:30 templates
-rw-------    1 wgui     wgui           485 May 31 23:30 wg0.conf

docker-compose.yaml
version: "2.1"
services:
  wireguard:
    image: ghcr.io/linuxserver/wireguard
    container_name: wireguard
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - PUID=100
      - PGID=101
      - TZ=America/New_York
      - PEERS=1
    volumes:
      - wg-conf:/config
      - wg-modules:/lib/modules
    ports:
      - 51820:51820/udp
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
    restart: always

  wgui:
    image: ngoduykhanh/wireguard-ui:latest
    container_name: wireguard-ui
    ports:
      - 5000:5000
    volumes:
      - wgui-db:/app/db
      - wg-conf:/etc/wireguard
    depends_on:
      - "wireguard"
    restart: always

volumes:
  wg-conf:
    external: false
  wg-modules:
    external: false
  wgui-db:
    external: false

web ui:

wg output from wireguard container after adding a user
root@6f274d01e75c:/# wg
interface: wg0
  public key: XXXXX
  private key: (hidden)
  listening port: 51820

peer: XXXXX
  allowed ips: <IP_ADDRESS>/32

You need to do 2 things to make wireguard see the changes:

Apply the changes to the config file
restart the wireguard container

To apply the changes, hit the button in the top right:

You can either restart the container manually docker restart <container> or add another container to your docker compose to monitor the server's wg0.conf and auto-restart the container. You'd have to expose your container management API to that monitoring container for that to work.
before:
wireguard@wireguard:~/wg$ sudo docker exec -it wireguard cat /config/wg0.conf
[Interface]
Address = <IP_ADDRESS>
ListenPort = 51820
PrivateKey = XXXXX
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE

[Peer]
# peer1
PublicKey = XXXXX
AllowedIPs = <IP_ADDRESS>/32

after:
[Interface]
Address = <IP_ADDRESS>/32
ListenPort = 51820
PrivateKey = YYYYY
MTU = 1450
PostUp = iptables -A FORWARD -i %i -j ACCEPT; iptables -A FORWARD -o %i -j ACCEPT; iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
PostDown = iptables -D FORWARD -i %i -j ACCEPT; iptables -D FORWARD -o %i -j ACCEPT; iptables -t nat -D POSTROUTING -o eth0 -j MASQUERADE

# ID:           c2qrful24nqq2s4q5ddg
# Name:         test
# Email<EMAIL_ADDRESS># Created at:   2021-06-01 04:30:50.940846174 +0000 UTC
# Update at:    2021-06-01 04:30:50.940846174 +0000 UTC
[Peer]
PublicKey = XXXXX
PresharedKey = XXXXX
AllowedIPs = <IP_ADDRESS>/32

Note: this does not update your wg0.conf, it completely replaces it. Your private key and all the peers generated from linuxserver/wireguard will be lost
FWIW, here's my updated docker-compose.yaml, but I don't think the permissions changes were the issue.
version: "2.1"
services:
  wireguard:
    image: ghcr.io/linuxserver/wireguard
    container_name: wireguard
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=America/New_York
      - PEERS=0
    volumes:
      - wg-conf:/config
      - wg-modules:/lib/modules
    ports:
      - 51820:51820/udp
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
    restart: always

  wgui:
    image: ngoduykhanh/wireguard-ui:latest
    container_name: wireguard-ui
    ports:
      - 5000:5000
    volumes:
      - wgui-db:/app/db
      - wg-conf:/etc/wireguard
    depends_on:
      - "wireguard"
    restart: always

volumes:
  wg-conf:
    external: false
  wg-modules:
    external: false
  wgui-db:
    external: false

Hi, I'm trying to do the same exact thing discussed in here but so far have no luck.
I'm on Synology DSM and running linuxserver/wireguard successfully, just need the UI to work.
Unfortunately, it doesn't.
I've mapped wg0.conf file but when I save through the UI, that file wasn't even touched.
version: '3.7'
services:
  wireguard:
    image: ghcr.io/linuxserver/wireguard
    container_name: wireguard
    cap_add:
      - NET_ADMIN
      - SYS_MODULE
    environment:
      - PUID=1053
      - PGID=65538
      - TZ=Asia/Kuala_Lumpur
      - SERVERURL=redacted #optional
      - SERVERPORT=51820 #optional
      - PEERS=5 #optional
      - PEERDNS=auto #optional
      - INTERNAL_SUBNET=<IP_ADDRESS> #optional
      - ALLOWEDIPS=<IP_ADDRESS>/0 #optional
    volumes:
      - /volume1/docker/wireguard/config:/config
      - /lib/modules:/lib/modules
    ports:
      - 51820:51820/udp
    sysctls:
      - net.ipv4.conf.all.src_valid_mark=1
    restart: always

  wgui:
    image: ngoduykhanh/wireguard-ui:latest
    container_name: wireguard-ui
    ports:
      - 5155:5155
    volumes:
      - wgui-db:/app/db
      - wg-conf:/volume1/docker/wireguard/config
    environment:
      - SENDGRID_API_KEY=redacted
      - EMAIL_FROM_ADDRESS=redacted
      - EMAIL_FROM_NAME=redacted
      - SESSION_SECRET=redacted
      - WGUI_USERNAME=redacted
      - WGUI_PASSWORD=redacted
      - BIND_ADDRESS=<IP_ADDRESS>:5155
    depends_on:
      - "wireguard"
    restart: always

volumes:
  wg-conf:
    external: false
  wg-modules:
    external: false
  wgui-db:
    external: false

This is what I'm using now and it works perfect. The only thing I need to figure out is to install the monitor (https://hub.docker.com/r/kking124/wireguard-monitor) so it could restart wireguard when I change the setup.

Can you jump over to (https://github.com/kking124/wireguard-monitor) and submit an issue if you haven't gotten it working yet?


Allow react 17 as a peer dependency

Hey there,
We are using react 17 and I believe the library should also work in this version, therefore I'd like to update the peer dependency requirement

Thanks @DanielMSchmidt , published to<EMAIL_ADDRESS>

Wow that was quick 🤯  Thanks a ton @fraserxu 🙇


feat(doc): "Update the document of the roadmap to improve readability and include features that are in preparation but not yet scheduled.

Modifications

Update the document of Roadmap to enhance readability and include potential job responsibilities

Types of changes

[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Bugfix (non-breaking change which fixes an issue)
[x] Documentation Update (if none of the other choices apply)
[ ] So on...

Verifying this change

[x] Make sure that the change passes the testing checks.

This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

This can be verified in development debugging
This can be realized in a mocked environment, like a test cluster consisting in docker

(or)
This change MUST reappear in online clusters, or occur in that specific scenarios.
Does this pull request potentially affect one of the following parts:

[ ] Master
[ ] MetaNode
[ ] DataNode
[ ] ObjectNode
[ ] AuthNode
[ ] LcNode
[ ] Blobstore
[ ] Client
[ ] Cli
[ ] SDK
[ ] Other Tools
[ ] Common Packages
[ ] Dependencies
[ ] Anything that affects deployment

Documentation

[x] doc
[ ] doc-required
[ ] doc-not-needed
[ ] doc-complete

Review Expection

[ ] in-two-days
[x] weekly
[ ] free-time
[ ] whenever

Matching PR in forked repository

PR in forked repository:

+1

+1

+1

+1

+1

+1

+1


[Inky] Buttons doubling the button class

Not seeing this in the tests, I'll update foundation-docs with the latest version of Inky and see if it's still happening.

Updated foundation-docs and everything looks chill. Run npm update inside the foundation-emails repo to pull a newer version.


keyd-application-mapper fails when system startup

Sometimes the keyd-application-mapper fails when system startup.
log message
keyd-application-mapper fails when system startup
Mostly started successfully, but if it fails, I must turn on Keyd Extention on GNOME Extentions to start KAM.

What is the output of ~/.config/keyd/app.conf? Where are you seeing the log
message you posted? It doesn't look like anything produced by the script.
On Sat, Apr 2, 2022 at 10:17 AM shungo27 @.***> wrote:

Sometimes the keyd-application-mapper fails when system startup.
log message
keyd-application-mapper fails when system startup
Mostly started successfully, but if it fails, I must turn on Keyd
Extention on GNOME Extentions to start KAM.
—
Reply to this email directly, view it on GitHub
https://github.com/rvaiya/keyd/issues/173, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAOP7GNZCSKMQZ7REJQIGIDVDBJIRANCNFSM5SK73KWQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I'm sorry. I copied a completely different text 😰
Correct error message
Apr  2 18:19:29 raspberrypi gnome-shell[13252]: ERROR: could not connect to keyd instance, make sure it is running and you are a member of `keyd`

For me it was the following
Traceback (most recent call last):   File "/usr/bin/keyd-application-mapper", line 336, in <module>     lock()   File "/usr/bin/keyd-application-mapper", line 303, in lock     lockfh = open(LOCKFILE, 'w') PermissionError: [Errno 13] Permission denied: '/home/$USER/.config/keyd/app.lock'
When running as sudo
ERROR: could not find app.conf, make sure it is in ~/.config/keyd/app.conf

I'm assuming this is happening because keyd-application-mapper is somehow getting started before keyd. I've allowed the initialization order to be reversed in the latest commit. Can you see if this solves your problem?

I tested the reboot 5 times with keyd 2.3.1-rc (ed7991d). There seems to be no problem so far👍

Thanks for the confirmation. Feel free to reopen if the issue resurfaces.


Capture And Process mTLS TCPDUMP

I think it will great to see how the HTTPS traffic can be captured via tcpdump and processed via wireshark or similar tool. I could not find much info about this.

Hey @infinitydon 👋, thanks for opening the issue!
Our current opinion is that the capturing and processing of TCP data should be left to tools that are designed for that use case (e.g., Wireshark, as you mentioned). Autocert is purpose built for making certificates available to pods. Anything else, we consider to be out of scope at this time.
That said, we're open to having our minds changed by folks from the community. I'll leave the issue open as wontfix and if we see more support we can revisit.


Add cross join

I am finding this useful for aggregate joins where the native and imported data each have one row.

Would you be happy to merge this?


Weak type detection doesn't consider generic types

TypeScript Version:  2.4.1
Code
interface BaseInterface {
  baseMethod?: () => void;
}

interface DerivedInterface extends BaseInterface {
  derivedMethod?: () => void;
}

class Impl implements DerivedInterface {
  derivedMethod(): void { }
}

class Helper {
  runCore<T extends BaseInterface>(o: T): void  { }

  run(): void {
    this.runCore(new Impl());
  }
}

Expected behavior:
TS2559 is not reported, since Impl shares a property DerivedInterface, an interface which extends BaseInterface.
Actual behavior:
TS2559 is reported.
Workaround:
If the following call is used, TS2559 is not reported:
this.runCore<DerivedInterface>(new Impl());

The problem is that BaseInterface doesn't share a property with Impl(). This fix works too
class Helper {
  runCore<T extends BaseInterface>(o: T): void  { }

  run(): void {
    this.runCore(new Impl() as BaseInterface);
  }
}
`

The problem is that BaseInterface doesn't share a property with Impl().

It's not supposed to. The weak types implementation currently works well for certain algorithms, but is quite problematic for others. It could be substantially improved by avoiding the warning report when the object passed in shares a property with an interface that extends a weak type.

This fix works too

The use of an unchecked cast precludes the approach from being considered a fix.

   It sounds like a fix to me, just not a clean fix.

The problem is the structurally typed nature of typescript. @sylvanaar is right, from the compilers perspective, BaseInterface and Impl don't share any properties. This limitation is not limited to weak types; notice that you can't say new Impl().baseMethod() because the compiler doesn't even know it's there. The canonical workaround for this is interface merging:
interface Impl extends BaseInterface {}
class Impl implements DerivedInterface ...

This tells the compiler to add the base methods to Impl even if they aren't actually defined in the body of Impl. implements doesn't actually add anything to your type, it just checks that what is present conforms to the implemented interface. Afterward, the compiler has no idea that the class and the base interface are related.
I think the concept BaseInterface really needs is "must implement at least one". Unfortunately, I don't think the OO concepts in typescript allow that. Maybe some clever union type would do it, though.


(1.9) Custom Themes overhaul

Changes:

Custom themes v2, removes orangedark and orangelight.
More detailed reset button, also added reset to saved theme

This should not happen. v1 already supports not including orangeLight and orangeDark. If you want to make it simpler, orangeLight and orangeDark should not be included by default in the theme JSON.

I like the idea of the reset buttons though.

they should just be simplified, instead of teh orange stuff, use terms like primary, secondary, etc

This should not happen. v1 already supports not including orangeLight and orangeDark. If you want to make it simpler, orangeLight and orangeDark should not be included by default in the theme JSON.

so do i scrap v2 and just edit v1 to not care about orangelight and dark?

This should not happen. v1 already supports not including orangeLight and orangeDark. If you want to make it simpler, orangeLight and orangeDark should not be included by default in the theme JSON.

so do i scrap v2 and just edit v1 to not care about orangelight and dark?

v1 already doesn't care about orangeLight and orangeDark. But yes, you should scrap v2, it's a pointless change.

another PR is using v2 rn too.


[BUG] broken source links in the documentation

Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Clicking on the list_models page redirects to
Broken link page → https://huggingface.co/docs/timm/reference/models

https://github.com/rwightman/pytorch-image-models/blob/main/src/timm/models/_registry.py#L94

Expected behavior
Instead, it should redirect to
https://github.com/rwightman/pytorch-image-models/blob/main/timm/models/_registry.py#L94
I believe due to this other links in the docs are also broken.

@rwightman thanks for the prompt reply. I will try to submit a PR tonight. I saw some instructions in the hfdocs folder on how to get started. On that same note, I think since the project is so popular, it should also have a CONTRIBUTING.md encouraging people to submit PRs and fix bugs.

@deven367 still want to do that, or would you like me to?

On second thought, it looks like it's already working, eh? Maybe I missed a PR or some update?
If so, @deven367 can you pls close?

Yeah, its working again. I'll close it. Thanks @nateraw


Some attributes are not available in response objects

I see that sms.list_hosted_service_properties(service_name, True) also return virtual_ips
<HostedService>
....
 <Deployments>
   <Deployment xmlns=”http://schemas.microsoft.com/windowsazure”>
      ......
      <VirtualIPs>
        <VirtualIP>
          <Address>virtual-ip-address-of-deployment</Address>
        </VirtualIP>
      </VirtualIPs>
   </Deployment>
  </Deployments>
</HostedService>

But these properties like virtual_ips are not being returned in the response from the sdk.

This property should now be available, could you check that you get it correctly now?
Thank you,

Closing due to inactivity. Please feel free to re-open the bug if you still see the issue.


Simplified nav colors + removed highlight on mobile

:no_entry: Error rendering the commits bac952c68888...a1aa1a614b2b on linux. :mag_right: 23 errored, 1 new, 50 changed

Error in a1aa1a614b2b: Chat_List-Normal-ERROR

Error in bac952c68888: Devices_Devices_List-Devices-ERROR

Error in a1aa1a614b2b: Devices_Devices_List-Devices-ERROR

Error in bac952c68888: Chat_No_Conversation-normal-ERROR

Error in bac952c68888: Chat_Input-Normal-ERROR

Error in a1aa1a614b2b: Chat_Input-Normal-ERROR

Error in bac952c68888: Chat_Inbox-You_Rekey_Selected-ERROR

Error in a1aa1a614b2b: Chat_Inbox-You_Rekey_Selected-ERROR (view)
Error in bac952c68888: Chat_Inbox-You_Rekey-ERROR (view)
Error in a1aa1a614b2b: Chat_Inbox-You_Rekey-ERROR (view)
Error in bac952c68888: Chat_Inbox-Selected_Normal-ERROR (view)
Error in bac952c68888: Chat_Inbox-Selected_Muted-ERROR (view)
Error in bac952c68888: Chat_Inbox-Part_Rekey_Selected-ERROR (view)
Error in a1aa1a614b2b: Chat_Inbox-Part_Rekey_Selected-ERROR (view)
Error in bac952c68888: Chat_Inbox-Part_Rekey-ERROR (view)
Error in a1aa1a614b2b: Chat_Inbox-Part_Rekey-ERROR (view)
Error in bac952c68888: Chat_Inbox-Normal-ERROR (view)
Error in bac952c68888: Chat_Inbox-Long_Top-ERROR (view)
Error in a1aa1a614b2b: Chat_Inbox-Long_Top-ERROR (view)
Error in bac952c68888: Chat_Inbox-Long_Bottom-ERROR (view)
Error in a1aa1a614b2b: Chat_Inbox-Long_Bottom-ERROR (view)
Error in bac952c68888: Chat_Inbox-Empty-ERROR (view)
Error in a1aa1a614b2b: Chat_Inbox-Empty-ERROR (view)
Added: Chat_No_Conversation-normal (view)
Changed: You_Rekey-Normal (before) (after) (diff)
Changed: Text-Terminal_Empty_Information (before) (after) (diff)
Changed: Text-Terminal_Comment_Information (before) (after) (diff)
Changed: Text-Body_Wrap_Information (before) (after) (diff)
Changed: Text-Body_Small_Semibold_Italic_Information (before) (after) (diff)
Changed: Text-Body_Small_Semibold_Italic_Documentation (before) (after) (diff)
Changed: Text-Body_Small_Secondary_Link_Information (before) (after) (diff)
Changed: Text-Body_Small_Primary_Link_Information (before) (after) (diff)
Changed: Text-Body_Small_Italic_High_Risk (before) (after) (diff)
Changed: Text-Body_Small_Inline_Link_High_Risk (before) (after) (diff)
Changed: Text-Body_Semibold_Italic_High_Risk (before) (after) (diff)
Changed: Text-Body_Information (before) (after) (diff)
Changed: Text-Body_Big_Link_Information (before) (after) (diff)
Changed: Text-Body_Big_Information (before) (after) (diff)
Changed: Text-Body_Big_Documentation (before) (after) (diff)
Changed: Colors-white_20_rgba_255_255_255_0_20 (before) (after) (diff)
Changed: Colors-white_0_rgba_255_255_255_0 (before) (after) (diff)
Changed: Colors-transparent_rgba_0_0_0_0 (before) (after) (diff)
Changed: Colors-grey_cccccc (before) (after) (diff)
Changed: Colors-green_3_dcc_8_e (before) (after) (diff)
Changed: Colors-green_3_E_8_FAF_3 (before) (after) (diff)
Changed: Colors-blue_5_F_8_FAFD (before) (after) (diff)
Changed: Colors-blue_4_ebf_5_fc (before) (after) (diff)
Changed: Colors-blue_3_40_rgba_168_215_255_0_4 (before) (after) (diff)
Changed: Colors-black_10_rgba_0_0_0_0_10 (before) (after) (diff)
Changed: Colors-black_05_rgba_0_0_0_0_05 (before) (after) (diff)
Changed: Colors-beige_f_7_f_1_eb (before) (after) (diff)
Changed: Buttons-Secondary_waiting (before) (after) (diff)
Changed: Buttons-Secondary_full_Width_waiting (before) (after) (diff)
Changed: Buttons-Secondary (before) (after) (diff)
Changed: Buttons-Primary_small_waiting (before) (after) (diff)
Changed: Buttons-Primary_full_Width_waiting (before) (after) (diff)
Changed: Buttons-Follow_small_waiting (before) (after) (diff)
Changed: Buttons-Danger_small_waiting (before) (after) (diff)
Changed: Buttons-Danger_full_Width (before) (after) (diff)
Changed: Buttons-Danger (before) (after) (diff)
Changed: Avatar-Normal_x_48 (before) (after) (diff)
Changed: Avatar-Normal_x_32 (before) (after) (diff)
Changed: Avatar-Normal_x_24 (before) (after) (diff)
Changed: Avatar-Mutual_Follow_x_64 (before) (after) (diff)
Changed: Avatar-Mutual_Follow_x_48 (before) (after) (diff)
Changed: Avatar-Mutual_Follow_x_112 (before) (after) (diff)
Changed: Avatar-Follows_You_x_80 (before) (after) (diff)
Changed: Avatar-Follows_You_x_112 (before) (after) (diff)
Changed: Avatar-Following_x_176 (before) (after) (diff)
Changed: Avatar-Following_x_16 (before) (after) (diff)
Changed: Avatar-Fallback_x_32 (before) (after) (diff)
Changed: Avatar-Fallback_x_16 (before) (after) (diff)
Changed: App_Tab_Bar-Search_Active (before) (after) (diff)
Changed: App_Tab_Bar-Normal (before) (after) (diff)


High CPU consumption when idle

Does this issue occur when all extensions are disabled?: No (it does not happen when running VSCode in Windows, does happen in WSL) - no other extension than Remote - WSL is enabled/installed

VS Code Version:
Version: 1.61.0-insider (system setup)
Commit: f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78
Date: 2021-09-14T05:15:56.612Z
Electron: 13.1.8
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.19043

OS Version: using WSL1 on Win 10 x64 Enterprise Edition and running VSCode remotely in WSL
OS: Ubuntu 18.04.2 LTS on Windows 10 x86_64
Kernel: 4.4.0-19041-Microsoft

Steps to Reproduce:

start VSCode Insiders and wait until everything is up
run ps -eo pcpu,pid,user,args
observe high CPU usage:

eip@LAPTOP-O4GG982K:~$ ps -eo pcpu,pid,user,args
%CPU   PID USER     COMMAND
 0.0     1 root     /init
 0.0  1547 root     /init
 0.0  1548 eip      -bash
 0.0 14916 root     /init
 0.0 14917 eip      sh -c "$VSCODE_WSL_EXT_LOCATION/scripts/wslServer.sh" f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78 insider .vscode-server-insiders 0
 0.0 14918 eip      sh /c/Users/PeterKrokavec/.vscode-insiders/extensions/ms-vscode-remote.remote-wsl-0.58.2/scripts/wslServer.sh f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78 insider .vscode-server-insiders 0
 0.0 14924 eip      sh /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/server.sh  --port=0 --use-host-proxy --without-browser-env-var --disable-websocket-compression --print-ip-address --enable-remote-auto-shutdown
13.3 14926 eip      /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/node /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/out/vs/server/main.js  --port=0 --use-host-proxy --without-browser-env-var --disable-websocket-compression --print-ip-address --enable-remote-auto-shutdown
 0.0 14937 eip      /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/node /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/out/bootstrap-fork --type=ptyHost
 0.7 14974 eip      /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/node /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/out/bootstrap-fork --type=watcherService
52.5 15197 eip      /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/node /home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/out/bootstrap-fork --type=extensionHost --uriTransformerPath=/home/eip/.vscode-server-insiders/bin/f66a3e06bcb9f000e5dc0ad0040ff9b32fc75c78/out/vs/server/uriTransformer.js --useHostProxy=
 0.0 25235 eip      ps -eo pcpu,pid,user,args

I haven't noticed this last week, but today I upgraded VSCode to latest version (I was prompted that there was a new version to install so I did although I was already on 1.61.0-insiders since the last week)
Is there a possibility to downgrade my insiders build to an older one?

I am seeing this on a native Linux machine, the load is constantly around 100% for me


not available on the chrome store anymore

not sure if this is dead (seems like it), but please remove the link to the store then

Thanks! Removed.


read and write in little endian order

Before patch (queryRuns=2)
hdf5/nytimes-256-angular.hdf5: 289761 base and 9991 query vectors loaded, dimensions 256
PQ@128 build 18.09s,
PQ encode 1.93s,
Build M=8 ef=128 in 15.05s with 0.92 short edges
  Query PQ=true top 100/2 recall 0.7115 in 3.55s after 43910864 nodes visited
  Query PQ=true top 100/4 recall 0.7621 in 6.26s after 79406058 nodes visited
Build M=16 ef=128 in 29.56s with 0.80 short edges
  Query PQ=true top 100/2 recall 0.7853 in 5.68s after 79359556 nodes visited
  Query PQ=true top 100/4 recall 0.8369 in 10.99s after 149524964 nodes visited
Build M=32 ef=128 in 67.65s with 0.59 short edges
  Query PQ=true top 100/2 recall 0.8444 in 10.02s after 140328630 nodes visited
  Query PQ=true top 100/4 recall 0.8969 in 19.18s after 269563424 nodes visited

After patch:
hdf5/nytimes-256-angular.hdf5: 289761 base and 9991 query vectors loaded, dimensions 256
PQ@128 build 22.73s,
PQ encode 2.15s,
Build M=8 ef=128 in 15.60s with 0.92 short edges
  Query PQ=true top 100/2 recall 0.7113 in 3.34s after 44005096 nodes visited
  Query PQ=true top 100/4 recall 0.7625 in 6.41s after 79669490 nodes visited
Build M=16 ef=128 in 29.95s with 0.80 short edges
  Query PQ=true top 100/2 recall 0.7856 in 5.55s after 79299732 nodes visited
  Query PQ=true top 100/4 recall 0.8368 in 11.04s after 148996964 nodes visited
Build M=32 ef=128 in 66.47s with 0.59 short edges
  Query PQ=true top 100/2 recall 0.8442 in 9.58s after 139674146 nodes visited
  Query PQ=true top 100/4 recall 0.8967 in 19.29s after 268166768 nodes visited

Doesn't seem to make a difference really

@tjake did you get a chance to look at this?  do you agree that it's a nothingburger?

How you’re using it yeah. If we ever used mmap buffers directly then we
would want it.  But fine to close it out
On Fri, Sep 29, 2023 at 1:45 PM Jonathan Ellis @.***>
wrote:

@tjake https://github.com/tjake did you get a chance to look at this?
do you agree that it's a nothingburger?
—
Reply to this email directly, view it on GitHub
https://github.com/jbellis/jvector/pull/67#issuecomment-1741273839, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAK3KAVTEDY3Q2YK5ZGZTLX44CKRANCNFSM6AAAAAA4YHEEJU
.
You are receiving this because you were mentioned.Message ID:
@.***>


Create project from WCQS SPARQL query (special case: requires Wikimedia authentication)

This is a feature request for a specific subcase of OpenRefine/OpenRefine#1212. This will be helpful for users who want to edit structured data of existing Wikimedia Commons files with the help of OpenRefine.
Through the SDC project for OpenRefine, users will be able to edit and upload files with structured data on Wikimedia Commons. See more info about this project on meta.wikimedia.org.
In some cases, it may be very handy for users to start an OpenRefine project with a SPARQL query from the Wikimedia Commons Query Service (WCQS). However, this specific SPARQL endpoint requires Wikimedia OAuth authentication.
It would be great if the work done on OpenRefine/OpenRefine#1212 also includes this use case, or alternatively we add support for WCQS after that general task has been completed.
Proposed solution
I have no idea at all about the technical difficulties re: this request. Curious to hear considerations around this!
Additional context

General info about WCQS, including some pointers re: dealing with authentication from external tools https://commons.wikimedia.org/wiki/Commons:SPARQL_query_service
The authentication for WCQS is controversial in the Wikimedia community, see https://phabricator.wikimedia.org/T297995. However, it is very unlikely that authentication is removed anytime soon (think in the upcoming years)

We discussed that it may be useful if I'd collect some typical example queries. Here are a few that will be useful for people who want to batch edit SDC with OpenRefine, and who would like to start from a SPARQL query:

An advanced query which is very useful for SDC batch editing; it uses the Commons API to retrieve files from a specific Wikimedia Commons category. https://w.wiki/5JiK
From the example queries, and very useful for SDC editing as well (cleanup tasks): a query that shows files that depict both a specific church and the generic 'church building' (which would be good to remove). It would be great if OpenRefine could load more than 500 (ie not use the LIMIT if the query doesn't time out) https://w.wiki/5JiR
This one shows files by a specific username, with Depicts statements: https://w.wiki/5Jiu


add gp-pages readme

Signed-off-by: laminar<EMAIL_ADDRESS>
(If this PR fixes a github issue, please add Fixes #<xyz>.)
Fixes #
(or if this PR is one task of a github issue, please add Master Issue: #<xyz> to link to the master issue.)
Master Issue: #384
Motivation
add readme for https://charts.functionmesh.io/
Modifications
add readme for https://charts.functionmesh.io/
Verifying this change

[x] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Documentation
Check the box below.
Need to update docs?

[ ] doc-required
(If you need help on updating docs, create a doc issue)

[ ] no-need-doc
(Please explain why)

[x] doc
(If this PR contains doc changes)

leave some minor comments. PTAL

done


[WIP]Data convertor code refine with more types support

@jikunshang @Intel-bigdata/bdf-cider-engine open another PR for further changes.

can we merge this PR? if so please change your title(remove WIP).

Change the title for now, still some known issues for bool type to be fix

Change the title for now, still some known issues for bool type to be fix

update these info in description?

@yyang52 are we in right sharp? I am preferring to merge it timely.


[Bug]: OAuth - Post query to dropbox fails.

Is there an existing issue for this?

[X] I have searched the existing issues

Description
On establishing a connection to dropbox using OAuth2.0, and running a post query - the query fails with the following errors -
[PE-RST-5000]
An error occurred during the execution of your API. Please check the error logs for more details.
[400 BAD_REQUEST]
Error in call to API function "files/list_folder": request body: could not decode input as JSON
Steps To Reproduce

Create an OAuth connection to dropbox.

The connection goes through fine

Now create a new POST api entering the Body in JSON format as below -
{
--
"include_deleted": false,
"include_has_explicit_shared_members": false,
"include_media_info": false,
"include_mounted_folders": true,
"include_non_downloadable_files": true,
"path": "",
"recursive": false
}

Note that the query fails with the errors -
[PE-RST-5000]
An error occurred during the execution of your API. Please check the error logs for more details.
[400 BAD_REQUEST]
Error in call to API function "files/list_folder": request body: could not decode input as JSON

This same query passes on Production.
Note: Details of credentials as below -
URL - https://api.dropboxapi.com/2/files/list_folder
Authentication Type - OAuth2.0
Grant Type - Authorisation Code
Access Token URL - https://api.dropboxapi.com/oauth2/token
Client ID - 2lwiwmnrsektqim
Client Secret - s16uo7jhe1o971i
Scope - files.metadata.write
Authorisation URL - https://www.dropbox.com/oauth2/authorize
Redirect URL - https://release.app.appsmith.com/api/v1/datasources/authorize
Custom Authentication Parameters -
response_type = code
token_access_type = offline
Ensure your redirect URL is a part of the dropbox setup.
Public Sample App
No response
Environment
Release
Issue video log
No response
Version
Release Branched out

Looks like a FE issue. Posted my analysis here: https://theappsmith.slack.com/archives/CTHN8GX5Y/p1677598620592509?thread_ts=1677567532.832279&cid=CTHN8GX5Y

Fixed as part of PR: https://github.com/appsmithorg/appsmith/pull/21057


Generated connect or create classes get too many suffices

I have the schema set to configure both:
dtoSuffix                     = "DtoAttributes"
entitySuffix                  = "Attributes"

However, when I annotate something with @DtoRelationCanCreateOnCreate or @DtoRelationCanConnectOnCreate then the interface for the connect or create generates with the dtoSuffix but the property itself receives both suffices:
interface CreateOfferAttachmentsRelationInputDtoAttributes {
  create: CreateOfferAttachmentDtoAttributes[];
}

export interface CreateOfferDtoAttributes {
  candidateName: string;
  candidatePosition: string;
  attachments?: CreateOfferAttachmentsRelationInputDtoAttributesAttributes;
}

This fails compile because the type does not exist.
I tried to look into this and traced that the second suffix is being added some time after helpers.ts returns the value, since type there is correct. I can't figure out where this is happening, though, or what the potential follow-on risks would be to changing this.

Thanks! There is a small check if the dto or entity class name should be generated and it only checked if the provided name ends with dto. So if the dtoSuffix ends with dto everything went fine. Now, this check considers the whole dtoSuffix (see commit).
I just released version 1.17.4


Transaction Hashes are Computed Incorrectly

ganache-core uses EIP-155 hashes to identify transactions. This causes JSON-RPC calls like eth_sendRawTransaction to return unexpected values. The EIP-155 hash should be used to generate a signature. It should not be used to identify the transaction in the RPC mechanism.
Expected Behavior
$ curl -X POST --data '{"jsonrpc":"2.0","method":"eth_sendRawTransaction","params":["0xf86b808504e3b2920082520894a3bd45f7b000a6d3d2359b0577ed34adbdfc25eb87038d7ea4c68000802aa0dec7e8ff13c93cdc9a75432f01730bdc3a20fc0eaf820a7234c1aabdbf6ccb64a0601845af5cbd02e9c443f870bdbee61c93a5533c4c3f84931a0e1dfab30d39ab"],"id":1}' https://ropsten.infura.io
{"jsonrpc":"2.0","id":1,"result":"0xe1ba8a320f9fc6846127b244faf9825028d7298c4d34c4aa0fc57d48b85a7ab3"}

Current Behavior
$ curl -X POST --data '{"jsonrpc":"2.0","method":"eth_sendRawTransaction","params":["0xf86b808504e3b2920082520894a3bd45f7b000a6d3d2359b0577ed34adbdfc25eb87038d7ea4c68000802aa0dec7e8ff13c93cdc9a75432f01730bdc3a20fc0eaf820a7234c1aabdbf6ccb64a0601845af5cbd02e9c443f870bdbee61c93a5533c4c3f84931a0e1dfab30d39ab"],"id":1}' localhost:8545
{"id":1,"jsonrpc":"2.0","result":"0x56860ff2721668edd33f5f86abdbd44fe1a8e8f3efba1a12dc76f2c9da53b836"}

Notice that the hash is 0x56860ff2721668edd33f5f86abdbd44fe1a8e8f3efba1a12dc76f2c9da53b836 instead of sha3(data) = 0xe1ba8a320f9fc6846127b244faf9825028d7298c4d34c4aa0fc57d48b85a7ab3
Possible Solution
Always use sha3(rawData) to identify signed transactions, including over json rpc.
Steps to Reproduce (for bugs)
Run gananche-cli in the background using this:
const secretKey = Buffer.from('8874F01D72E7BE5D5417B55E0F21698692704F408C1AFF382641DB0423F1B2E1', "hex");
const config = {
  "accounts": [
    { "balance": 1000000 *<PHONE_NUMBER>000000000,
      "secretKey": secretKey
    }, ], };

require("ganache-cli").server(config).listen(8545);

Then run curl as above.
Context
Transaction hashes computed outside of ganache-core/ganache-cli do not match those expected or returned by ganache-X. This makes it difficult to use ganache-X for testing applications that interact with other Ethereum nodes.
Your Environment

Version used: Ganache CLI v7.0.0-beta.0 (ganache-core: 3.0.0-beta.0)
Operating System and version: macOS 10.13.2

I met with hash inconsistency issues too. May I know if it is relevant ? I am didn't use EIP155 signature and my test is as follows. Thanks for your help !
From Ganache Cli

version: Ganache CLI v6.2.3 (ganache-core: 2.3.1)

eth_getTransactionByHash
   > {
   >   "jsonrpc": "2.0",
   >   "method": "eth_getTransactionByHash",
   >   "params": [
   >     "0xbed7a8d01e51b7bd38d5850c889c3ff7c77187096d65759563a3af6948aa14dd"
   >   ],
   >   "id": 0
   > }
 <   {
 <     "id": 0,
 <     "jsonrpc": "2.0",
 <     "result": {
 <       "hash": "0xbed7a8d01e51b7bd38d5850c889c3ff7c77187096d65759563a3af6948aa14dd",
 <       "nonce": "0x0",
 <       "blockHash": "0xa6fae628979e440a3aec283b59bd700903adc4ddc46d5d4bb316d7d688b2cd14",
 <       "blockNumber": "0x2",
 <       "transactionIndex": "0x0",
 <       "from": "0x9e0b01422022d36c49e9e7367bb913a21971f31d",
 <       "to": "0xb5e64298c11ae039a26a9bd337a08e0a16ff8f7c",
 <       "value": "0xde0b6b3a7640000",
 <       "gas": "0x5208",
 <       "gasPrice": "0x10642ac00",
 <       "input": "0x",
 <       "v": "0x1c",
 <       "r": "0x4d27429c02ae442b1a7fed7e97b02d9ac6ac943f9a2aead49cc4d4bc8ef49a86",
 <       "s": "0x33e11db734724dcdb1f5988ea4fcbf9dd992ba74e14288f3801f9cc954c82e7b"
 <     }
 <   }

From Geth

the transaction is signed without chainId

curl \
  -H "Content-Type: application/json" \
  -X POST \
  --data '{"jsonrpc":"2.0","method":"eth_getTransactionByHash","params":["0x201c35a2b4e65289100b7c06e4ea3f00037f4f8ad57ee6a627611993becebabd"],"id":67}' \
http://localhost:8545 | jq

geth version

Geth
Version: 1.8.19-stable
Architecture: amd64
Protocol Versions: [63 62]
Network Id: 1
Go Version: go1.11.2
Operating System: darwin
GOPATH=
GOROOT=/usr/local/Cellar/go/1.11.2/libexec

result

{
  "jsonrpc": "2.0",
  "id": 67,
  "result": {
    "blockHash": "0xcfdb376a115ac00c171c1b0adcbe76d59e2d2476988236b356b770c21ed07344",
    "blockNumber": "0x1",
    "from": "0x9e0b01422022d36c49e9e7367bb913a21971f31d",
    "gas": "0x5208",
    "gasPrice": "0x10642ac00",
    "hash": "0x201c35a2b4e65289100b7c06e4ea3f00037f4f8ad57ee6a627611993becebabd",
    "input": "0x",
    "nonce": "0x0",
    "to": "0xb5e64298c11ae039a26a9bd337a08e0a16ff8f7c",
    "transactionIndex": "0x0",
    "value": "0xde0b6b3a7640000",
    "v": "0x1c",
    "r": "0x4d27429c02ae442b1a7fed7e97b02d9ac6ac943f9a2aead49cc4d4bc8ef49a86",
    "s": "0x33e11db734724dcdb1f5988ea4fcbf9dd992ba74e14288f3801f9cc954c82e7b"
  }
}

@Ykid We just released new ganache-core and ganache-cli betas with a fix for transaction hash issues.
You can install the beta via npm install ganache-core@beta or npm install ganache-cli@beta -g for the CLI.
Please let me know if these hash miss matches are still an issue!


document usage of --- to create log groups

Don't see this behaviour documented anywhere. Using --- in the output of a command starts a log group you can fold on the frontend.

@lox Does this not work if we put this in a script that is executed from the main command?
# main pipeline

- label: 'some step'
- command: 'some-script.bat'

:: some-script.bat

echo "--- Group 1"
npm i

It should work! 🤔 Wanna drop us an email at<EMAIL_ADDRESS>@harryi3t


Documentation for installing AdaptiveCpp on macbook Pro M1

Documentation for installing AdaptiveCpp on macbook Pro M1 with reference to  https://github.com/AdaptiveCpp/AdaptiveCpp/issues/1433

Thank you. Perhaps some of our users with Mac experience (@normallytangent ?) can comment on the documented steps.
It might be a good idea to also enable the SSCP compiler and document how to set things up with LLVM. The SSCP JIT compiler for host CPU I think should work on Mac.
At a higher level, I think the most important question is how this content would fit into the existing documentation. This PR just provides a text file that is referenced from nowhere, which makes it questionable whether it would be found by users. We could add some structure to cover different OS. Or, we do the same what we do currently with Windows and document the steps for Mac in a Wiki-page (https://github.com/AdaptiveCpp/AdaptiveCpp/wiki/Using-AdaptiveCpp-on-Windows).

@illuhad  Thank you for the reply  .
I think its better if documentation related to macOS  can be replicated for how its done with windows as you suggested , because installing and running the application should not be cumbersome . Also the documentation related to macOS that's already existing was not complete enough . I will push the changes soon and keep you posted .

why do you suggest the idea "it might be a good idea to also enable the SSCP compiler " ?

Because the SSCP JIT compiler (--acpp-targets=generic) is our default and most powerful compiler. It can also target the host CPU and in principle it should be able to run on Mac. So ideally, we can verify that it works and then also recommend people to use it on Mac. We are already heavily pushing Linux users towards using the SSCP compiler.
We should first enable it in Ma CI though; @fodinabor recently tried this and discovered some hiccups.

I still would hope that somehow we could get CI running... On a local MacOS install, I was able to use SSCP with this branch: https://github.com/AdaptiveCpp/AdaptiveCpp/tree/feature/enable-sscp-macos However, I had to make really sure that I used the correct libc++ (i.e. the one from brew, I think).
However, as the relatively long line of attempts to debug CI on https://github.com/AdaptiveCpp/AdaptiveCpp/tree/macos-ci-dbg2 shows, I'm not so sure how to make this right..
The issue is: recent brew LLVM is built against its own libc++, therefore, we should also build AdaptiveCpp (runtime & tests) against that libc++. However, the current failure in the CI was that tests that test if a certain exception is thrown fail, as the exception is not captured by boost - my intuition is, that this is because boost & AdaptiveCpp are built against other libc++(-abi) versions, therefore not being able to capture each other's exceptions...
I'm not entirely sure how to deal with this...


Add Simplify.DI

IoC / Simplify.DI - https://github.com/i4004/Simplify/wiki/Simplify.DI
A common interface for IOC containers. Decouples users and frameworks (that are based on Simplify.DI) from dependency on IOC containers.
Decouples users and frameworks (that are based on Simplify.DI) from dependency on IOC containers. Instead of that, they will only depend on Simplify.DI interface.
Provides DIContainer.Current ambient context as centralized IOC container. Provides unified Interface for creation IOC container providers (wrappers) for IOC container frameworks.

Repo is achieved


isort

Isn't this already fixed by using black?

No. See https://github.com/psf/black/issues/333.

I had already added isort — I just forgot.


merged Student Visit Data branch and onboarding data branch

mergedStudentVisitData branch along with some onboarding data

For this merge to dev, just want to add that AddingAdditionalData in path documentation/RunningStudentSurveyLocally/AddingAdditionalData was added by mistake and is an empty file. Just a fyi


Issue on page /tutorials/W1D3_ModelFitting/W1D3_Intro.html

Your issue content here.

Can you clarify the issue by giving more details? Thank you.

Not enough info provided.


style the pop up for the detail of a schema

Signed-off-by: steve-237<EMAIL_ADDRESS>

Why did you build a new component only for this schema pop-up? We have the information pop-up, which worked fine for more than one use case.

Why did you build a new component only for this schema pop-up? We have the information pop-up, which worked fine for more than one use case.

The component l created is supposed to be used for this issue but so far it has not been implemented yet. and that solves the problem with the view. The information pop up that I styled should be used to deliver error messages or success of operations as on the mockup. But if you have other modifications that you can make to improve the view please add them

Why did you build a new component only for this schema pop-up? We have the information pop-up, which worked fine for more than one use case.

The component l created is supposed to be used for this issue but so far it has not been implemented yet. and that solves the problem with the view. The information pop up that I styled should be used to deliver error messages or success of operations as on the mockup. But if you have other modifications that you can make to improve the view please add them

Yes, but we shouldn't duplicate code just for one use case. You could still use the information pop up and edit and extend it. There is always the possibility to use "ngIf" in html, if that helps you.

Why did you build a new component only for this schema pop-up? We have the information pop-up, which worked fine for more than one use case.

The component l created is supposed to be used for this issue but so far it has not been implemented yet. and that solves the problem with the view. The information pop up that I styled should be used to deliver error messages or success of operations as on the mockup. But if you have other modifications that you can make to improve the view please add them

You are right. We have a lot of smaller dialogs which could be refactored if needed in the future. Although I do not like the it, i can stay for now.

There is a small problem at this level, we cannot fully read what is written on the image. Is it supposed to be like this?


ONEDNN - Layer Normalization error

System information.

Have I written custom code (as opposed to using a stock example script provided in Keras):
OS Platform and Distribution : ubuntu 18, ubuntu 20,redhat 7
TensorFlow installed from (source or binary): binary
TensorFlow version (use command below): 2.9.
Python version: 3.8.11
Bazel version (if compiling from source):
GPU model and memory:
Exact command to reproduce: see code below

Describe the problem.
Describe the problem clearly here. Be sure to convey here why it's a bug in Keras or why the requested feature is needed.
Describe the current behavior.
the code fail here
but I am assuming the source in another place
Describe the expected behavior.
code pass without fail like if TF_ENABLE_ONEDNN_OPTS set to 0

Do you want to contribute a PR? (yes/no):no
If yes, please read this page for instructions
Briefly describe your candidate solution(if contributing):

Standalone code to reproduce the issue.
run on computer with intel dl booster (without GPU)
import os
os.environ['TF_ENABLE_ONEDNN_OPTS'] = '1'
import tensorflow as tf
import numpy as np

input_layer = tf.keras.layers.Input(shape=(3,24), dtype=np.float32)
data = tf.quantization.fake_quant_with_min_max_vars(inputs=input_layer, min=0, max=3.5, num_bits=8)
data = tf.keras.layers.LayerNormalization(axis=[-2,-1], center=True,scale=True)(data)
data = tf.quantization.fake_quant_with_min_max_vars(inputs=data, min=0, max=3.5, num_bits=8)
model = tf.keras.Model(inputs=input_layer, outputs=data)
model.compile()
model.summary()

data = np.random.rand(1,3,24)
res = model.predict(data)

Source code / logs.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/path/to/python/python3.8/site-packages/keras/utils/traceback_utils.py", line 67, in error_handler
    raise e.with_traceback(filtered_tb) from None
  File "/path/to/python/python3.8/site-packages/tensorflow/python/eager/execute.py", line 54, in quick_execute
    tensors = pywrap_tfe.TFE_Py_Execute(ctx._handle, device_name, op_name,
tensorflow.python.framework.errors_impl.InvalidArgumentError: Graph execution error:

Detected at node 'model/layer_normalization/add' defined at (most recent call last):
    File "<stdin>", line 1, in <module>
    File "/path/to/python/python3.8/site-packages/keras/utils/traceback_utils.py", line 64, in error_handler
      return fn(*args, **kwargs)
    File "/path/to/python/python3.8/site-packages/keras/engine/training.py", line 2033, in predict
      tmp_batch_outputs = self.predict_function(iterator)
    File "/path/to/python/python3.8/site-packages/keras/engine/training.py", line 1845, in predict_function
      return step_function(self, iterator)
    File "/path/to/python/python3.8/site-packages/keras/engine/training.py", line 1834, in step_function
      outputs = model.distribute_strategy.run(run_step, args=(data,))
    File "/path/to/python/python3.8/site-packages/keras/engine/training.py", line 1823, in run_step
      outputs = model.predict_step(data)
    File "/path/to/python/python3.8/site-packages/keras/engine/training.py", line 1791, in predict_step
      return self(x, training=False)
    File "/path/to/python/python3.8/site-packages/keras/utils/traceback_utils.py", line 64, in error_handler
      return fn(*args, **kwargs)
    File "/path/to/python/python3.8/site-packages/keras/engine/training.py", line 490, in __call__
      return super().__call__(*args, **kwargs)
    File "/path/to/python/python3.8/site-packages/keras/utils/traceback_utils.py", line 64, in error_handler
      return fn(*args, **kwargs)
    File "/path/to/python/python3.8/site-packages/keras/engine/base_layer.py", line 1014, in __call__
      outputs = call_fn(inputs, *args, **kwargs)
    File "/path/to/python/python3.8/site-packages/keras/utils/traceback_utils.py", line 92, in error_handler
      return fn(*args, **kwargs)
    File "/path/to/python/python3.8/site-packages/keras/engine/functional.py", line 458, in call
      return self._run_internal_graph(
    File "/path/to/python/python3.8/site-packages/keras/engine/functional.py", line 596, in _run_internal_graph
      outputs = node.layer(*args, **kwargs)
    File "/path/to/python/python3.8/site-packages/keras/utils/traceback_utils.py", line 64, in error_handler
      return fn(*args, **kwargs)
    File "/path/to/python/python3.8/site-packages/keras/engine/base_layer.py", line 1014, in __call__
      outputs = call_fn(inputs, *args, **kwargs)
    File "/path/to/python/python3.8/site-packages/keras/utils/traceback_utils.py", line 92, in error_handler
      return fn(*args, **kwargs)
    File "/path/to/python/python3.8/site-packages/keras/layers/normalization/layer_normalization.py", line 324, in call
      outputs = outputs + tf.cast(offset, outputs.dtype)
Node: 'model/layer_normalization/add'
scale must be 1D tensor[1,3,24]
	 [[{{node model/layer_normalization/add}}]] [Op:__inference_predict_function_217]

@gowthamkpr,
I was able to reproduce the issue in tensorflow v2.9 and nightly. Kindly find the gist of it here.

I run my code in the GitHub action
and I set the
TF_ENABLE_ONEDNN_OPTS=0
TF_DISABLE_MKL=1

and sometimes I get the error
any idea how I can debug this?
or any other env to set to disable intel dl booster?


Fixed marked tiles not disappearing

https://github.com/i-yam-jeremy/bog-runelite-plugin/issues/1#issue-462762772
Also simplified code

Any chance this can be merged and the plugin added to the plugin hub?


Update functionality of date picker on charts

The charts should adjust their range based on the selected period.
Signed-off-by: johnsonw<EMAIL_ADDRESS>

This change is


Move video/jobs to redux

[x] finish job board move (in progress)
[x] update react-router
[x] update history
[x] update react-router-redux
[x] Fix hikes issues
[x] Update eslint/gulp-eslint

@BerkeleyTrue updated the pull request.

@BerkeleyTrue updated the pull request.

@ltegman Good idea, I'll do that.

Now live beta!

Great stuff! Can't wait to look over the redux code more when I have more time. Tested out videos and jobs and didn't run into problems with either :+1:


Add timestamps alignment; Smartphone data extraction; Depth image extraction

Closes #4
Closes #3

Smartphone video frames are extracted with ffmpeg
Depth images (32-bit float img) are saved in tiff format, as suggested in imwrite() documentation

Smartphone video frames are extracted with ffmpeg
Depth images (32-bit float img) are saved in tiff format, as suggested in imwrite() documentation

Closes #7

Closes #7


flutter_compass deprecation warning

Each time I run flutter pub get or run my application which depends on flutter_compass only through this plugin, I get the following warning:
"The plugin flutter_compass uses a deprecated version of the Android embedding.
To avoid unexpected runtime failures, or future build failures, try to see if this plugin supports the Android V2 embedding. Otherwise, consider removing it since a future release of Flutter will remove these deprecated APIs.
If you are plugin author, take a look at the docs for migrating the plugin to the V2 embedding: https://flutter.dev/go/android-plugin-migration."

flutter_compass has published version 0.7.0 which solves the issue. So need to update the dependency

Thanks you for reminder! Updated dependencies.


Bug report: Braille in version 10

Describe the bug
Braille in the Output field comes up as â â â â â â â
To Reproduce
Steps to reproduce the behaviour or a link to the recipe / input used to cause the bug:

Using the To Braille Operator and observing the text in the output

Expected behaviour
Expected text to be  ⠃⠗⠁⠊⠇⠇⠑
Screenshots
If applicable, add screenshots to help explain your problem.

Desktop:

OS: Attempted and found on IPhone, Ubuntu and Windows
Browser: Using Safari, Firefox and Edge
CyberChef version: 10.0.1

Additional context
Pressing the Replace Input with Output button displays correct braille in the input field.

This can be fixed by changing the Output character encoding to UTF-8, however I will work on a better solution as this should work out of the box.


Settings Page with Light/Dark Mode Switch

To implement the dark and lightmode switch look here :moon: : https://github.com/Malte2036/react-social/blob/main/lib/database/backendService.ts#L53

Please Assign this issue to me
I would love to work upon this.

Please Assign this issue to me I would love to work upon this.

@indiehjaerta is working on this one.


How to end greedy-consume arguments?

Given:
type flags struct {
   Something []string `names:"-s" usage:"pass in something(s)"`
   Rest      []string `args:"true"`
}

how does the user end the greedy consumption of -s and provide non-flag arguments?  E.g., a common pattern in flag parsing libraries requires multi-value argument flags to be specified once for each argument:
cmd -s A -s B -s C XYZ

would produce len(a.Something) == 3 and a.Rest == []string{"XYZ"}.  If multi-value arguments are greedy, len(a.Something) == 4 and a.Rest == []string{}.
How does a user pass in arguments to Rest with greedy consumption?

@serussell There is no builtin support like '-' and '--' currently,  but you can just define a '-nop' flag and place it after last value of '-s', it will works. Glad to see the better way, thanks.

Maybe it's not so clear, what i means is:
type flags struct {
   Something []string `names:"-s" usage:"pass in something(s)"`
   Nop      bool
   Rest      []string `args:"true"`
}

And then cmd -s A -s B -s C -nop XYZ will works.

One solution would be to have multi-value arguments be non-greedy.  That is:
cmd -s A B C

would not assign A, B, and C to s.  To pass multiple values to one argument, require specifying the argument multiple times.  This is the behavior of most POSIX commands (e.g., tar) and even the go command itself.  Right now, with this library, the following are equivalent:
cmd -s A -s B
cmd -s A B

but only the latter breaks the ability of the library to differentiate between multi-value and non-flag arguments.  A solution would be to simply remove the latter behavior.

That looks a bit wordy if the flag name is -something instead of simple -s, actually i'd prefer long flag name instead of short so i don't need to remember what the flag means, especially for those not frequently used application.
Maybe it's better to make it an parsing option.


[BUG] expanding user

Hi,
I think expanding the user this way (line 14) could lead to some bugs:
https://github.com/raspberrypi/picamera2/blob/dd984341d3fda13f1c08c41dc93e25625853bcfe/picamera2/__init__.py#L13-L22
In this SO answer, the author explains that the user directory is not always /home/<user>. Also, dir is a built-in function in Python. I would rewrite the code like so:
def _set_configuration_file(filename):
    user_directory = os.path.expanduser("~")
    dirs = [
        os.path.join(
            user_directory,
            "libcamera/src/libcamera/pipeline/rpi/vc4/data"
        ),
        "/usr/local/share/libcamera/pipeline/rpi/vc4",
        "/usr/share/libcamera/pipeline/rpi/vc4"]

    for directory in dirs:
        file = os.path.join(directory, filename)

        if os.path.isfile(file):
            os.environ['LIBCAMERA_RPI_CONFIG_FILE'] = file
            break

Regards,
Vincent

Hi, thanks for the suggestion. That might be a good candidate for a PR, if you'd like to submit one? Please read our contribution guidelines so that we can get through the process easily and quickly. Thanks!
(Just a minor warning that I think this is the new 3.10 release... but which we aren't "officially" distributing without some extra libcamera updates. Hopefully it will only be a few days at most for this, but just to let you know that things are not quite perfect at the minute.)


Readme files for Win7 and Win7SP1 are swapped.

It seems that readme files and possibly the image reflecting the kernel version information for Prefetch samples are swapped entirely.

fixed: https://github.com/AndrewRathbun/DFIRArtifactMuseum/commit/44a163a45956dea188938bcc80f5dda04d321722


Refactor docs cellTypes to cell_types

Signed-off-by: Jason T. Brown<EMAIL_ADDRESS>

Not sure why the CI tests failed.

@metasim can you force the travis build to try again?


Individual Theme per Language not working

When trying to set the theme(s) for a specific language only hugo does not seem to apply the theme at all.
I verified that for the following configuration hugo only resolves theme layouts when the theme-common is enabled for all languages but not if it's only enabled for specific languages.
baseURL = "http://example.org/"
title = "My New Hugo Site"

defaultContentLanguage = "en"
defaultContentLanguageInSubdir = true
#theme = ["theme-common"]

[languages]
    [languages.en]
        languageCode = "en"
        weight = 1
        contentDir = "content/en"
        theme = ["theme-common"]

I prepared a small test repository that demonstrates the problem.
https://github.com/hanneskuettner/hugo-theme-for-language
I would expect hugo to render the index.html with the content "Single Common" from the theme-common layouts single.html file but instead I get the warning found no layout file for "HTML" for kind "page": and an empty page.
This works as expected if you uncomment line 6 in the config.toml.
I've had a look in the globalOnlySettings variable and could not find theme in the as such I would expect this to work.
https://github.com/gohugoio/hugo/blob/5914f91b6c980e42693661d5fd5640e237691df6/langs/language.go#L33
What version of Hugo are you using (hugo version)?

$ hugo version
Hugo Static Site Generator v0.76.5/extended darwin/amd64 BuildDate: unknown

Does this issue reproduce with the latest release?
Yes

That is not a feature/supported in Hugo.

That's a shame! I guess I will close this issue then.
Maybe we should start documenting which settings are supported per language and which aren't because so far I've found information all over the place, e.g. your own quote from two years ago.

Is this something that can be added to the feature roadmap?

Is this something that can be added to the feature roadmap?


fix: add tailwindcss types

Currently importing the resolved config from #tailwind-config throws an error using TypeScript since the config file is not being written. This PR adds @types/tailwindcss and writes a simple .d.ts to the .nuxt folder to provide config types.
Before

After

@types/tailwindcss is now deprecated because tailwindcss provides its own type definitions
I think this PR could be safely reversed?

Create a PR that removes the dependency #514


[Identity] tried exclusive union for Identity types

Packages impacted by this PR
@azure/identity
Issues associated with this PR
None
Describe the problem that is addressed by this PR
The client Id and resource Id to be passed in the managed identity credential should be mutually exclusive. The user shouldn't be able to pass both. The | union operator for types in TS somehow allows both parameters to be passed.

We are already following the same approach for these types -

export declare type ClientCertificateCredentialPEMConfiguration = {
 certificate: string;
certificatePath?: never;
} | {
 certificate?: never;
 certificatePath: string;
 };

What are the possible designs available to address the problem? If there are more than one possible design, why was the one in this PR chosen?

Yet to discuss.
TODO:
[ ] Add for these types too - DefaultAzureCredentialClientIdOptions and DefaultAzureCredentialResourceIdOptions

Collaborator - @sadasant

I was talking with @bterlson and he came up with a solution that looks like this:
export declare type Certificate = {
    name: string;
}

export declare type ClientCertificate = Certificate & {
    certificate: string;
}
export declare type ClientCertificatePath = Certificate & {
    certificatePath: string;
};

declare function foo1(prop: ClientCertificate | ClientCertificatePath): void;
foo1({ name: "foo", certificate: "1", certificatePath: "2" }) // this isn't A or B but both

declare function foo2(...args: [o: ClientCertificate] | [o: ClientCertificatePath]): void;
foo2({ name: "foo", certificate: "1", certificatePath: "2" }) // good error but intellisense still suggests the other prop after you give one

The only problem with this is that IntelliSense still suggests that you can have both properties. @witemple-msft do you know any Typescript magic that can be used to get a better IntelliSense here?

@joheredi I believe that what you’re suggesting is what we had before. This PR is about suggesting an approach that fixes the IntelliSense issue.

@sadasant, the key is in how the function parameter is defined.
declare function foo2(...args: [o: ClientCertificate] | [o: ClientCertificatePath]): void;
foo2({ name: "foo", certificate: "1", certificatePath: "2" }) // good error but intellisense still suggests the other prop after you give one

That makes TS give you an error, but IntelliSense still suggests both properties. The original change in this PR suggests both as well. I believe that Brian's suggestion gives a better error.

...args: [o: ClientCertificate] | [o: ClientCertificatePath] is really weird though 🤔 having to spread parameters, and then expanding the underlying types with the array syntax… I’m not a fan 😅.

@joheredi @KarishmaGhiya @sadasant  I would typically use an overload for this situation.
The issue here is that omitting a field from an interface in TypeScript does not mean "this field is not present," but means "this field is not constrained" which is a subtle distinction with an important difference. In addition, there are rules about what fields may be included in object literals that open up a bit for union types compared to interface types.
So, what I'd do is have two constructor overloads, one for each options variant. Note that you can't actually stop someone from passing both fields at runtime, so you will have to pick which one takes precedence.
See this TS playground for a demo and a bit more explanation: https://www.typescriptlang.org/play?#code/JYOwLgpgTgZghgYwgAgMIHsC2n0mQbwChkTk4AuZAZzClAHMBuQgX0MNElkRQCFkIAD0ggAJlTRYceIqWQAjSjTogmrdp2jwkaAcIhiJGbLgLFSCSiACumedGZtCMayARhgpmOnQAKeZbI-AA+aACUBE4ubh6m8nBQ-pS8YZQAbujAoszR7p548YmBqKnIGVk5rnlxCf6BIeGR7AD0zcgA8ugADlQAdM4+vrKkFMgARJA0YwA05iSK48oMM3PIgQCMAAysYS1tALLWCAAWChBgXP2FQ6ujExBTs3ILY0uqK3Ib2yy7hK3IAHVjgZkGAAJ5dB4IOhdMBkKhUYD0EAScGQ1HoZC5WJ4LoJOCYc7QCQAd2AYFO6DS0AANug4OJpshyWtgQgANZUP5tClwOEUlAJei2Az8iEoTB8k4PZAAfVwEFlyCptPpomoSJAfOsUAgTJA6H5wOQrnyypgZBpNO5yupUDpDI1yO1uqoTLgYg68gAVhB3MgADLk6BwGkSBIoaUciDqnC66i0YDuGlgsj0OCgGg2xGqGkoTTcHRomW8vCm3B9ZAAQTw6B9frhNODUFDoOOfOZ4YRmpjoMxcGzkIQwBgSdB4uQmGsNDWuDAGdrIBTWOAEBp4jbHYjyFEEFHIF7oE3YshTPk1jhcBNIHyNrJVtn4AXctDNKV6AtApXa43H+ZYAkBAsC6BVwHHdFemQABVHN6DbFAVXtNUbTgcoNy-cs8GLJlCQ9Bhj3g5V639JsuFbKcZyoIcR1TXBly-Ucfy5f4-1lKgsEVW1VUdPEW0JLhwL1MhPQNOFWNfd87QddVeIJIkoEEvogA

@witemple-msft I love it! @KarishmaGhiya let’s do that ^

API changes have been detected in @azure/identity. You can review API changes here
API changes
-     constructor(options?: ManagedIdentityCredentialOptions);
+     constructor(options?: ManagedIdentityCredentialClientIdOptions);
+     constructor(options?: ManagedIdentityCredentialResourceIdOptions);
+     constructor(options?: TokenCredentialOptions);

API changes have been detected in @azure/identity. You can review API changes here

API changes have been detected in @azure/identity. You can review API changes here

API changes have been detected in @azure/identity. You can review API changes here

API changes have been detected in @azure/identity. You can review API changes here

API changes have been detected in @azure/identity. You can review API changes here

API changes have been detected in @azure/identity. You can review API changes here

API changes have been detected in @azure/identity. You can review API changes here

API changes have been detected in @azure/identity. You can review API changes here

API changes have been detected in @azure/identity. You can review API changes here