Make the websocket in the middleware just send json

The middleware package now communicates purely through a generic event interface with the handler. I thus removed a TODO that was created for this task. The event is then sent through a websocket connection to connected clients.

I added a TODO to move to more restrictive event interfaces as we add actual functionality.


[BUG] TypeError when using sample code in Lambda

Environment

chrome-aws-lambda Version: 3.0.4
puppeteer / puppeteer-core Version: 3.0.4
OS: Mac
Node.js Version: 12.x
Lambda / GCF Runtime: nodejs12.x

Expected Behavior
Should fetch github.com home page
Current Behavior
TypeError: r.close is not a function
I'm not sure where to start with this one. I'm using Serverless with Webpack,  and I'm using the layer from chrome-aws-lambda-layer for my Chromium.
I have not yet attempted to run this locally as I'm not currently setup for it on this project. I did notice that the path coming back from chromium.getExecutablePath is /tmp/chromium - not sure if that's correct (or relevant to the issue).
Steps to Reproduce
const chromium = require('chrome-aws-lambda');

exports.handler = async (event, context, callback) => {
  let result = null;
  let browser = null;

  try {
    browser = await chromium.puppeteer.launch({
      args: chromium.args,
      defaultViewport: chromium.defaultViewport,
      executablePath: await chromium.executablePath,
      headless: chromium.headless,
      ignoreHTTPSErrors: true,
    });

    let page = await browser.newPage();

    await page.goto(event.url || 'https://www.github.com');

    result = await page.title();
  } catch (error) {
    console.log(error);
  } finally {
    if (browser !== null) {
      await browser.close();
    }
  }

  return {
    statusCode: 200,
    message: result
  }
};

Possible Solution
I'm wondering if there are any extra params specific to Serverless to get proper files included in the build? Unsure where to start debugging this one.

This was a Webpack issue, my apologies.


CAPSTONE_DIET

Capstone has a diet compile time flag, described here: http://www.capstone-engine.org/diet.html
This reduces the library size. It would be quite useful to provide builds with this flag, considering that capstone-x86.min.js is 2MB, which is prohibitively large for some JavaScript projects.

My main concern is that the build matrix will get insanely large with too many builds to choose from, and not obvious for developers which one to pick (diet mode sacrifices information that is useful for some). Plus, it's just a 40% reduction. If 2 MB is too large, chances are 1.2 MB will be too large as well.
Providing precompiled builds was meant for popular combinations (e.g. single arch, multi arch) and more complex combinations (e.g. using CAPSTONE_DIET) can always pass the appropriate flags to build.py.
That said, if more people think diet-mode precompiled builds is absolutely necessary I will add that.


Add rest of leaderboard features

[ ] Timer bar
[x] Textboxes where missing
[x] Fix flickering modal/enlarged memes
[x] If not working: Fix final leaderboard display of "Best Meme of the Game" and "Best Meme of the Round" which might always show the same at the moment.
[x] Restyle leaderboard table same as lobbylist

Not sure whether to add timer bar since it's not important for the leaderboard
Added/Fixed Textboxes:
https://github.com/sopra-fs23-group-13/meme-it-client/commit/9396470509755fb5521d03efec8cab16ccfa089f
and https://github.com/sopra-fs23-group-13/meme-it-client/commit/4f21ee78c2b414e141018ded1818672e41951bb1
Fixed Flickering Modal/Leaderboard:
https://github.com/sopra-fs23-group-13/meme-it-client/commit/4f21ee78c2b414e141018ded1818672e41951bb1
Fixed Best Meme display:
https://github.com/sopra-fs23-group-13/meme-it-client/commit/4f21ee78c2b414e141018ded1818672e41951bb1
Restyled leaderboard table:
https://github.com/sopra-fs23-group-13/meme-it-client/commit/a2f11b021f201d6c7d673026326cbf025b52b582

https://github.com/sopra-fs23-group-13/meme-it-client/pull/157 contains all these changes plus the (probably) final textboxes


Wording in default_dtypes does not leave room for unsupported data types

The documentation of default_dtypes reads as of today:
Returns a dictionary containing default data types.

The dictionary must have the following keys:

  - "real floating": default real floating-point data type.

  - "complex floating": default complex floating-point data type.

  - "integral": default integral data type.

  - "indexing": default array index data type.

The "must" poses an issue for implementations that don't implement all data types, yet, such as ndonnx (related discussion). Maybe wording this as "...may at most contain the following keys..." is more appropriate?

So far the standard has required all data types. There was some discussion about loosening this, but I don't remember if there was a resolution on it, or if we actually have an issue for it already.

Oh, I see! Thanks for the clarification! I was under the impression that a subset may be allowed, but it clearly isn't: https://data-apis.org/array-api/2023.12/API_specification/data_types.html. I believe it does indeed make sense to require all data types so I'm closing this issue.


[Feature request] Support CohereForCausalLM

Would it be possible you add support for CohereForCausalLM?
Here is the model:
https://huggingface.co/CohereForAI/c4ai-command-r-v01
It's a very capable model that supports many languages (including some not supported by many other models like Vietnamese and Persian) so I think it will be quite widely used by the non-English AI community.
Thanks!

Ya right now even for trust_remote_code with registration of the methods, which works for transformers, this fails for vllm
(vllm2) fsuser@e2e-77-235:~$ python
Python 3.8.18 (default, Sep 11 2023, 13:40:15)
[GCC 11.2.0] :: Anaconda, Inc. on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> from vllm import LLM, SamplingParams
>>> llm = LLM(model="CohereForAI/c4ai-command-r-v01", trust_remote_code=True)
INFO 03-12 11:27:50 llm_engine.py:87] Initializing an LLM engine with config: model='CohereForAI/c4ai-command-r-v01', tokenizer='CohereForAI/c4ai-command-r-v01', tokenizer_mode=auto, revision=None, tokenizer_revision=None, trust_remote_code=True, dtype=torch.float16, max_seq_len=8192, download_dir=None, load_format=auto, tensor_parallel_size=1, disable_custom_all_reduce=False, quantization=None, enforce_eager=False, kv_cache_dtype=auto, device_config=cuda, seed=0)
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/fsuser/miniconda3/envs/vllm2/lib/python3.8/site-packages/vllm/entrypoints/llm.py", line 109, in __init__
    self.llm_engine = LLMEngine.from_engine_args(engine_args)
  File "/home/fsuser/miniconda3/envs/vllm2/lib/python3.8/site-packages/vllm/engine/llm_engine.py", line 391, in from_engine_args
    engine = cls(*engine_configs,
  File "/home/fsuser/miniconda3/envs/vllm2/lib/python3.8/site-packages/vllm/engine/llm_engine.py", line 128, in __init__
    self._init_workers()
  File "/home/fsuser/miniconda3/envs/vllm2/lib/python3.8/site-packages/vllm/engine/llm_engine.py", line 181, in _init_workers
    self._run_workers("load_model")
  File "/home/fsuser/miniconda3/envs/vllm2/lib/python3.8/site-packages/vllm/engine/llm_engine.py", line 1041, in _run_workers
    driver_worker_output = getattr(self.driver_worker,
  File "/home/fsuser/miniconda3/envs/vllm2/lib/python3.8/site-packages/vllm/worker/worker.py", line 100, in load_model
    self.model_runner.load_model()
  File "/home/fsuser/miniconda3/envs/vllm2/lib/python3.8/site-packages/vllm/worker/model_runner.py", line 88, in load_model
    self.model = get_model(self.model_config,
  File "/home/fsuser/miniconda3/envs/vllm2/lib/python3.8/site-packages/vllm/model_executor/utils.py", line 52, in get_model
    return get_model_fn(model_config, device_config, **kwargs)
  File "/home/fsuser/miniconda3/envs/vllm2/lib/python3.8/site-packages/vllm/model_executor/model_loader.py", line 43, in get_model
    model_class = _get_model_architecture(model_config)
  File "/home/fsuser/miniconda3/envs/vllm2/lib/python3.8/site-packages/vllm/model_executor/model_loader.py", line 35, in _get_model_architecture
    raise ValueError(
ValueError: Model architectures ['CohereForCausalLM'] are not supported for now. Supported architectures: ['AquilaModel', 'AquilaForCausalLM', 'BaiChuanForCausalLM', 'BaichuanForCausalLM', 'BloomForCausalLM', 'ChatGLMModel', 'ChatGLMForConditionalGeneration', 'DeciLMForCausalLM', 'DeepseekForCausalLM', 'FalconForCausalLM', 'GemmaForCausalLM', 'GPT2LMHeadModel', 'GPTBigCodeForCausalLM', 'GPTJForCausalLM', 'GPTNeoXForCausalLM', 'InternLMForCausalLM', 'InternLM2ForCausalLM', 'LlamaForCausalLM', 'LLaMAForCausalLM', 'MistralForCausalLM', 'MixtralForCausalLM', 'QuantMixtralForCausalLM', 'MptForCausalLM', 'MPTForCausalLM', 'OLMoForCausalLM', 'OPTForCausalLM', 'OrionForCausalLM', 'PhiForCausalLM', 'QWenLMHeadModel', 'Qwen2ForCausalLM', 'RWForCausalLM', 'StableLMEpochForCausalLM', 'StableLmForCausalLM', 'Starcoder2ForCausalLM']
>>>

Dup of #3330, vLLM does require custom model implementation. See https://docs.vllm.ai/en/latest/models/adding_model.html.


Duplicating js

Hi,
I have an AssetBundle (AB) on Head position (3 css and 1 js) and another one on End position (0 css and 15 js) in certain page. Whe using this extension, all the js files from both AB are mixed up in only one file and placed in the both html positions. I mean that in Head i have 1 file minified (1 + 15 = 16 js) and in the End i have the same file.
What should be the result?
One js file in the head with just 1 minified js file and a different file in the end with 15 minified js files.
My relevant config:
'js_position' => [\yii\web\View::POS_HEAD, \yii\web\View::POS_END], // positions of js files to be minified

My relevant resulting html:
<head>
...
<script src="/clientes/sg2/public_html/frontend/web/minify/da39a3ee5e6b4b0d3255bfef95601890afd80709.js">
...
</head>
<body>
.....
....
<script src="/clientes/sg2/public_html/frontend/web/minify/da39a3ee5e6b4b0d3255bfef95601890afd80709.js">
</body>
...

What is wrong? And what could I do to help?

Show the bundles and how you connect. Just checked in version 1.9.1 everything works correctly.
p.s. I'm sorry for the long answer. Missed notice.


[K12] Test and Test Score Objects K12 Additions

Critical Changes
Changes
New List Views and Quick Actions
In version 1.8, we made the following changes. If you installed an earlier version or installed on top of an existing org, consider making them to your org.

We introduced a K-12 All Tests list view on Test. If you choose to create a K-12 All Tests list view, we recommend this configuration:

Sharing Settings: All users can see this list view-
Filter by Owner: All tests
Display order: Test Name, Contact, Test Type, Test Date
See Create or Clone a List View.
Create a K12 Test Compact Layout with fields in this order: Test Name, Contact, Test Type, Test Date

We introduced a K-12 All Test Scores list view on Test Scores. If you choose to create a K-12 All Tests Scores list view, we recommend this configuration:

Sharing Settings: All users can see this list view
Filter by Owner: All test scores
Display order: Test Score Name, Test Type, Test, Subject Area, Score, Percentile
See Create or Clone a List View.
Add K-12 All Test Scores as a related list on Test.
For more information, see Display a New Custom Object After a Product Release.
Create a K12 Test Compact Layout with fields in this order: Test Name, Contact, Test Type, Test Date

We introduced new quick actions for Edit, New Note, Printable View, Change Owner, Clone, and Delete. If you want the New Case quick action to appear, you'll need to update the global quick action for New Case and change the record type as described in Quick Action Considerations.

Issues Closed
Closes #177
New Metadata
Page Layouts:

K12 Kit Test Layout
K12 Kit Test Score Layout

List View:

K12 All Tests
K12 All Test Score

Deleted Metadata
Testing Notes

Trial Org: this should be tested only after the PR has been merged to master

Dev_Namespaced Shape + dev_org_namespaced flow:
Pre-requisite: Go to Setup || User Interface || Global Actions || New Case

Click Edit on "New Case"
Update "RecordType" value from "Master" to "Incident"
Click save

Steps for testing:

Create Test and Test Score records
Test and Test Score page layout should match the screenshots on this quip doc https://salesforce.quip.com/5YeEArOU11bn#XSOACAgOHRH and https://salesforce.quip.com/5YeEArOU11bn#XSOACAVFf4P
Test and Test Score list view should match the screenshots on this quip doc
https://salesforce.quip.com/5YeEArOU11bn#XSOACAjlpPk and
https://salesforce.quip.com/5YeEArOU11bn#XSOACAg0xPp

Dev_Namespaced Shape + qa_org flow:
Pre-requisite: Go to Setup || User Interface || Global Actions || New Case

Click Edit on "New Case"
Update "RecordType" value from "Master" to "Incident"
Click save

Steps for testing:

Create Test and Test Score records
Test and Test Score page layout should match the screenshots on this quip doc https://salesforce.quip.com/5YeEArOU11bn#XSOACAgOHRH and https://salesforce.quip.com/5YeEArOU11bn#XSOACAVFf4P
Test and Test Score list view should match the screenshots on this quip doc
https://salesforce.quip.com/5YeEArOU11bn#XSOACAjlpPk and
https://salesforce.quip.com/5YeEArOU11bn#XSOACAg0xPp

@kdy618 looks like the build is failing compilation here, just wanted to give a heads up  in case you didn't see it.

Tested / Passes QE.

For the last bullet (for case quick action) printable is spelled wrong)

After testing in a K12 beta SO using the install_beta flow I would like to recommend adding some notes to the last bullet for New Case quick action:  In Global Actions you will see two options for New Case: 1 specific to the K12 managed package and 1 that is standard to Case. Edit the Global Action for the standard Case. Here you will update the record type to "Incident" and save. Once that is done, go to Publisher Layouts (under Global Actions), click edit, and drag the standard New Case quick action into the Global Publisher and save.

@kdy618 The changes look good, approving the PR. Can you remind me if we are going forward with this PR by documenting the steps to enable 'New Case' or are we doing a SPEC ? Also, do we want to update that we are adding new page layouts and flexi pages? Thanks

@skosgi1 , yep we are documenting it but I think we're providing a link on how to change the record type for the global quick action documentation that sfdc has. Good point on the page layout.
@juliesnow , is it too late to add that we have new page layout for Test and Test Score?

@kdy618 + @jacebryan - will PM you re these updates.

@kdy618 - Is there a reason K12 created a custom New Case global action that has the same name as the standard New Case global action? Is there any possible issues associated with this?

@kdy618 - Is there a reason K12 created a custom New Case global action that has the same name as the standard New Case global action? Is there any possible issues associated with this?

@jacebryan , we're leveraging the standard out of the box new case global action. We did not create a new one.

@kdy618  - Unless I'm mistaken I am seeing a K12 specific managed New Case global action that uses the same api name as the standard New Case global action.

@kdy618 - Unless I'm mistaken I am seeing a K12 specific managed New Case global action that uses the same api name as the standard New Case global action.

@jacebryan , I created beta shape org + ran beta_install and I only saw 1 New case global action. Am I running the wrong flow/shape?

Can we confirm a few things here?

We've leveraged standard Quick Actions and made them available for use in the Salesforce Mobile and Lightning Experience Actions bar for the Test and Test Score page layouts: Edit, New Note, New Case, Printable View, Change Owner, Clone and Delete.

What about existing customers? Will they need to make any changes?

In order to use the standard New Case Quick Action on Test and Test Score page layouts you will need to update the record type on the New Case Global Action to "Incident". You will see two options in Global Actions for New Case: 1 specific to the K12 managed package and 1 that is managed. Edit the Global Action for the non-managed New Case. Here you will update the record type to "Incident" and save.

This change will only need to be made by customers who have not already updated the New Case Global Action to "Incident".

The New Case Quick Action that SHOULD be showing on the Salesforce Mobile and Lightning Experience Actions bar on Test and Test Score page layouts should be the standard New Case Quick Action and not the custom K12 New Case Quick Action?

@juliesnow - here is language for use in the updated release notes. Feel free to do your magic :)
With the release of K12 1.8 we've leveraged standard Quick Actions and made them available for use in the Salesforce Mobile and Lightning Experience Actions bar for the Test and Test Score page layouts. Those Quick Actions include: Edit, New Note, New Case, Printable View, Change Owner, Clone and Delete.
Note:

You will need to edit the Page Layouts for both Test and Test Score and remove the New Case quick action that is set by default. You will need to add the other New Case Quick Action in its place.
In order to use the standard New Case Quick Action on Test and Test Score page layouts you will need to update the record type on the New Case Global Action to "Incident". You will see two options in Global Actions for New Case: 1 specific to the K12 managed package and 1 that is non-managed. Edit the Global Action for the non-managed New Case. Here you will update the record type to "Incident" and save. This change will only need to be made by customers who have not already updated the New Case Global Action to "Incident".


Request for Model Weights for PeptideBERT

Thank you for making PeptideBERT accessible through this repository. I’m currently working on a project related to peptide property prediction and I believe using the pre-trained model from PeptideBERT would be very helpful.
I was wondering if you could kindly provide the model weights mentioned in the paper, or guide me on how to obtain them if they are available elsewhere?
Thank you!

Hello Karththigan, you can find the model weights in the releases section of the repository.

Thank you!


Try to choose the right properties for SVC

Hi folks,
I develop tool that sample every 2 min with cron job with the next classes\observations:

Day (1-7)
Hour (00-23)
Minute (00-59)
Factor: Some Value (1-1000) (0 for < 800, else 1)

I have VARY large dataset available to train the ML algo (more than 1M samples)
I'm using SVC for classification and prediction (4 features right?).
I want to predict  the next sample: [2, 16, 2, 1] (Monday, 16:02, more than 800).

From your expereince, which SVM proparties should I need to choose? i.e.: $kernel, $cost, $degree, $gamma, $coef0, $tolerance, $cacheSize, $shrinking?
Should I choose other Multiclass classification? like kNN?

Thanks!

Hi @shaikezam, sorry for delay:
Your problem may sounds like linear problem, but with 3 features (day, hour, minute) i will try to use Kernel::RBF.
As for other parameters

gamma - more higher gamma value tries to exactly fit the training data set (so leads to overfitting)
cost - controls the trade off between smooth decision boundary and classifying the training points correctly (same as gamma, to much can lead to overfitting)
degree - only for Kernel::POLYNOMIAL, so you can skip it
coef0 - same as degree
tolerance - tolerance of termination criterion, it's much more complicated, you can go ahead with the default value: 0.001
cacheSize - size of the kernel cache, it has a strong impact on run times for larger problems. If you have enough RAM available, it is recommended to set it to a higher value than the default of 100(MB)
shrinking - whether to use the shrinking heuristic, you should leave this true, as it should greatly improve your performance, for very little loss in terms of accuracy in most cases

For such a large collection kNN will be less performance effective.

:thinking: this should be in documentation ...

Thanks for answer!
I tried run with kNN (k=3, 5) and get pretty much good prediction.
I will also try with SVM and comapre the result.
Shai

How much time does the prediction take for this amount of data? I am asking because there can be a lot of room for improvement, it may be optimized (I assume that).

The total prediction (which is get the dataset from DB, create labels and target and run prediction) take about 10 seconds for 200k samples.
I run it in AWS EC2 (micro).
I was able to run it parallel while K=3 & 5, but when trying to add 7 and 9, the VM will collapse :)

Hi,
Some remarks:
There is 210K samples in the traning set

KNN - the VM has 1 GB memory, that not enough (memory exception) - 40 seconds runing, but the most accurate algorithm
SVM\SVC - Traning never stoped (I stoped the program after 10 minutes)
NaiveBayes - Assume this is the fastest algorithm - 20 seconds but predictions not right, A all.

This can be improved, also there is possibility to introduce features that can limit memory usage (at the expense of losing performance).
In my opinion, it's short. For example training the MNIST database (with SVM and 60k samples) took 30-60 minustes.
NaiveBayes is to naive in this scenario.


[ja] Update concepts/cluster-administration/addons.md

fixes #32999
Restore "Contiv" entry, and apply other en updates.
List of updates (History)

https://github.com/kubernetes/website/pull/29719
https://github.com/kubernetes/website/pull/31760

https://github.com/kubernetes/website/pull/32938

https://github.com/kubernetes/website/pull/32834

https://github.com/kubernetes/website/pull/32937

https://github.com/kubernetes/website/pull/34171

https://github.com/kubernetes/website/pull/34126

en:
https://kubernetes.io/docs/concepts/cluster-administration/addons/
https://github.com/kubernetes/website/blob/main/content/en/docs/concepts/cluster-administration/addons.md
ja:
https://kubernetes.io/ja/docs/concepts/cluster-administration/addons/
https://github.com/kubernetes/website/blob/main/content/ja/docs/concepts/cluster-administration/addons.md
/assign @nasa9084

Thanks for the update. It is so good.
/lgtm


Network Management Using CDP and LLDP Layer 2 Protocols

Proposed title of article
Understanding how to manage networks using Layer 2 Protocols (CDP and LLDP)
Introduction paragraph (2-3 paragraphs):
One of the basic steps in network management and troubleshooting is to ensure the network connectivity between the devices is perfect and up running. To achieve this, one must understand how devices are interconnected between the network topology and have a proper documentation of the network.
To do this, in this article will show the reader how to use the Layer 2 discovery protocols to help the network administrator gather hardware and protocol information about neighbouring devices, which is useful information for troubleshooting, management and
Documenting the network. It will also equip the reader with the knowledge of how to configure the protocols on the network devices.
Key takeaways:
The reader should be able to:

Understand the Layer 2 protocols, both Cisco Discovery Protocol (CDP) and Link Layer Discovery Protocol (LLDP).
Be able to configure both the two protocols on networking devices.
Be able to troubleshoot and manage networks using the two protocols.

References:
N/A
Templates to use as guides
N/A

cc @hectorkambow

cc @hectorkambow

seems like a helpful topic - lets please be sure it add value beyond what is in the official docs and that it does not overlap with any existing EngEd articles (if you haven't already). - approved @dentonya


Availability options (YES/NO) overlap the box where they should be (Only on FF)

Version
2.0.15
File / Feature
Availability (Only  on Firefox)
Expected behaviour
The options YES and NO should be inside the box meant for them, or the box should be removed as it is in the Chrome version.
Actual behaviour
The  dial button for the YES option is overlapping the box where it's supposed to be.
Stacktrace / Error message
{paste here}

Other info
If the user clicks on the Options icon and waits for the options to appear, he can click again on the Vialer icon and then the bug is gone, since the box disappears. However, once the Availability menu collapses, if the user opens it again, the bug is back in place.
Steps to reproduce

Log into Vialer
2 Click on Availability
Notice the overlap

Screenshot

Fixed in develop (Firefox branch still not fully functional though)


pyprep.utils._filter_design throws error for large sampling rates

A minimal reproducible example for version 0.4.0, meant to mimic the usage in pyprep.find_noisy_channels._get_filtered_data, is as follows:
import numpy as np
from pyprep.utils import _filter_design

sample_rate = 8000.
bandpass_filter = _filter_design(
    N_order = 100,
    amp = np.array([1, 1, 0, 0]),
    freq = np.array([0, 90 / sample_rate, 100 / sample_rate, 1]),
)

This code chunk throws the following error:
ValueError                                Traceback (most recent call last)
/tmp/ipykernel_18594/550440648.py in <module>
      3 sample_rate = 8000.
      4
----> 5 bandpass_filter = _filter_design(
      6     N_order = 100,
      7     amp = np.array([1, 1, 0, 0]),

~/anaconda3/envs/glottis/lib/python3.9/site-packages/pyprep/utils.py in _filter_design(N_order, amp, freq)
    524         ),
    525     )
--> 526     pchip_interpolate = scipy.interpolate.PchipInterpolator(
    527         np.round(np.multiply(nfft, freq)), amp
    528     )

~/anaconda3/envs/glottis/lib/python3.9/site-packages/scipy/interpolate/_cubic.py in __init__(self, x, y, axis, extrapolate)
    230     """
    231     def __init__(self, x, y, axis=0, extrapolate=None):
--> 232         x, _, y, axis, _ = prepare_input(x, y, axis)
    233         xp = x.reshape((x.shape[0],) + (1,)*(y.ndim-1))
    234         dk = self._find_derivatives(xp, y)

~/anaconda3/envs/glottis/lib/python3.9/site-packages/scipy/interpolate/_cubic.py in prepare_input(x, y, axis, dydx)
     59     dx = np.diff(x)
     60     if np.any(dx <= 0):
---> 61         raise ValueError("`x` must be strictly increasing sequence.")
     62
     63     y = np.rollaxis(y, axis)

ValueError: `x` must be strictly increasing sequence.

Clearly the input to PchipInterpolator is the problem, so let's see what that looks like.
import numpy as np
import math

sample_rate = 8000
nfft = np.maximum(512, 2 ** (np.ceil(math.log(100) / math.log(2))))
freq = np.array([0, 90 / sample_rate, 100 / sample_rate, 1])
x = np.round(np.multiply(nfft, freq))

The output is x == array([  0.,   6.,   6., 512.]), which becomes the x argument to  PchipInterpolator Once sample rates are sufficiently large, the np.round operation causes consecutive values of x to be equal, which causes the error.
It would be nice to find a more robust way to filter, no? This isn't a problem until very large sampling rates (somewhere between 6 and 7 kHz), but nonetheless frustrating for those who don't want to downsample until after they've epoched their data (e.g. to minimize jitter vs. their event markers for very precise latency measurements).
I'm sure there's been some discussion on filter design in the past that lead to the use of a custom filter here instead of just using MNE's bandpass, so maybe it's not worth changing if it causes too much of a departure from the Matlab implementation -- but from this user's perspective, this would be a helpful change.

Hmm indeed I would think is possible to automatically use another bandpass implementation if it fails with the default one (as in put a try clause); then if it uses that other bandpass print something to the user as a warning.

I think that'd be okay :+1: I actually think this might be related to #107 - maybe @a-hurst can weigh in.

Hi all, apologies for the slow reply! @sappelhoff, re-reading the docs it looks like PyPREP already defaults to using MNE's filtering re: #107 unless MATLAB equivalence is requested. The filter throwing the exception here is the custom filter used for  creating the 1-50 Hz bandpass-filtered EEG copy used by the HF noise, correlation, and RANSAC bad channel detectors, which existed in PyPREP before I joined and is used regardless of MATLAB-equivalence.
We can certainly make this filter code another matlab_strict thing and swap in MNE filtering code in its place. If we do, we should also try adding a more informative exception in case someone does try matlab_strict mode with high sample-rate data.

We can certainly make this filter code another matlab_strict thing and swap in MNE filtering code in its place. If we do, we should also try adding a more informative exception in case someone does try matlab_strict mode with high sample-rate data.

:+1: agreed, I would go that route


[api] Fix handling of const objects in Callback class

Before, the following results in a compilation error:
const struct Object *obj;
void obj_doit(const Object *obj);

Callback<void()> cb(obj, obj_doit);

This is especially noticable when migrating from the old Thread
constructor, which previously required const.
Fixed by adding an additional const_cast:
void *_obj = const_cast<void*>(static_cast<const void*>(obj));

Could alternatively be fixed with C cast, not idiomatic C++ but cleaner:
void *_obj = (void*)obj;

cc @bridadan, @c1728p9

@mbed-bot: TEST
HOST_OSES=windows
BUILD_TOOLCHAINS=GCC_ARM,ARM,IAR
TARGETS=K64F,LPC1768

This is just straight undefined behavior and therefore illegal c++.
With this hack, it also totally mess with the overload resolution rules and failed at compilation time or worse execute the wrong function.
struct Foo {

    int value() const {
        return _ value;
    }

    void value(int new_value) {
        _value = value;
    }

private:
   int _value;
};

const Foo foo;

// this callback should wrap int Foo::value() const
// instead the compiler will try to wrap void Foo::value(int)
// because the const has been cast away
Callback<int()> cb(&foo, Foo::value);

The solution is simple: instead of wrapping everything in
    struct _class;
    union {
        void (*_staticfunc)();
        void (*_boundfunc)(_class *);
        void (_class::*_methodfunc)();
    } _func;

    void *_obj;

    // Thunk registered on attach to dispatch calls
    R (*_thunk)(void*, void*, A0, A1, A2, A3, A4);

And loose all type information when it is still needed, encapsulate everything into a  generic function object which handle the call and preserve all type information. Store this object in an "byte storage" in the callback class and generate a function to call the function object, the equivalent of your thunk.
By using this approach, you can handle every kind of CV qualifier, not just const.
In the process you can also make the function call and the call operator const it is the same approach that is used by every serious function abstraction implementation.

This is just straight undefined behavior and therefore illegal c++.

Which part is undefined behavior? Casting away constness is perfectly valid as long as the no write operation through the pointer (standard, see section 5.2.11).

With this hack, it also totally mess with the overload resolution rules and failed at compilation time or worse execute the wrong function.

This changes no function prototypes and can only impacts overload resolution where templates fail to expand. Your example fails to compile for reasons unrelated to this pr since Callback (and FunctionPointer before it) weren't designed to handle cv qualifiers.

Store this object in an "byte storage" in the callback class and generate a function to call the function object, the equivalent of your thunk.

Correct me if I'm wrong, but is the only difference between your suggestion and the current implementation the use of a byte array over a void * to store the _obj? Wouldn't you still need to lose the type information to store it in the byte array? The current implementation at least takes care of size/alignment concerns for the pointer.

By using this approach, you can handle every kind of CV qualifier, not just const.

You're right, this pr doesn't fix all of the cv qualifiers. I can look into adding this support through more specialized overloads. I may just be missing the bigger picture, but I'm not sure how the byte array with cv qualifiers more than void * casts.

In the process you can also make the function call and the call operator const

This is a good idea.
I was hoping to avoid expanding the Callback class too much, but it sounds like it may be necessary to properly handle cv qualifiers.

@geky

Which part is undefined behavior? Casting away constness is perfectly valid as long as the no write operation through the pointer (standard, see section 5.2.11).

This changes no function prototypes and can only impacts overload resolution where templates fail to expand. Your example fails to compile for reasons unrelated to this pr since Callback (and FunctionPointer before it) weren't designed to handle cv qualifiers.

I was under the impression that for member functions, the function pointer was converted to the non const version and I was wrong, it just generate a compilation error.
In that case there is no reasons to keep the const_cast for Callback with member function constructors (like (here)[https://github.com/geky/mbed/blob/6a551898378dfeaef5c68cb01e54b785f6b37b56/hal/api/Callback.h#L94]).
And without them I would support that PR.

Correct me if I'm wrong, but is the only difference between your suggestion and the current implementation the use of a byte array over a void * to store the _obj? Wouldn't you still need to lose the type information to store it in the byte array? The current implementation at least takes care of size/alignment concerns for the pointer.

The important operation of a function call is the function call.
If this function call is generated from a function like object then all types information are still available when the function like object is generated. Only the call is type erased (easy) and the object is hidden into the storage.
It would be possible to do it with the current implementation but it would require:

const
*volatile
*const volatile
Overloads for each constructors and attach function (function and member function).

With a function like object as intermediate wrapper I think it is easy to generate the right code without tricky casts and it can greatly reduce the number of overloads needed.
It would be interesting to investigate how a the second parameter of the constructor and the attach function can be replaced by a template parameter type template<typename T, typename F>.
In that case, F will map automatically to the overload  needed by T.
Yes, the storage should be properly aligned.

In that case there is no reasons to keep the const_cast for Callback with member function constructors

Good point, at the very least what I'm trying to do there seems completely broken because of member function pointer shenanigans. I'll remove them next chance I get.

The important operation of a function call is the function call.
If this function call is generated from a function like object then all types information are still available when the function like object is generated. Only the call is type erased (easy) and the object is hidden into the storage.

It'd be interesting to see what this would look like. I'd just get worried if it became more obscure how the class operated, but maybe it wouldn't be that bad.

It would be interesting to investigate how a the second parameter of the constructor and the attach function can be replaced by a template parameter type template<typename T, typename F>.
In that case, F will map automatically to the overload needed by T if their is no conflict.

That would be very cool, hopefully errors don't get too bad. It looks like gcc's implementation just has an overload for each combination of cv:
https://gcc.gnu.org/onlinedocs/gcc-4.7.0/libstdc++/api/a01173_source.html#l01150

Good point, at the very least what I'm trying to do there seems completely broken because of member function pointer shenanigans. I'll remove them next chance I get.

Separate PR for this?
Ready for merging? to fix the above use case (https://github.com/mbedmicro/mbed/pull/2190#issue-166192420)

@0xc0170, sorry, I meant I would remove it from this pr once I had access to a computer. Give me just a bit.

@mbed-bot: TEST
HOST_OSES=windows
BUILD_TOOLCHAINS=GCC_ARM,ARM,IAR
TARGETS=K64F,LPC1768

I updated the pr to not change the constructors for member functions.
note: I changed the casts to C-style casts to completely strip out cv-qualifiers (without access to std::remove_cv). It's a bit of a hack that takes care of the current issue, although still type-safe since cv-qualifiers are carried over in the T type.
@pan- is right that we should adopt a set of overloaded constructors in the future.


The files in experiments folder are all generated by running the code?

Hi, thank you for the excellent job!
The files in experiments folder are all generated by running the code? Are there some stuff that are prior knowledge to help with the training. I feel confusion about this problem: "FileNotFoundError: [Errno 2] No such file or directory: 'experiment/VOC/cls/infer/final/affx2,at_score,att2affx1/ann,affed/seed/2009_004108.png'". But it didn't generate these files last step.
Thank you for your explain!
Best

I solved this issue, see issue15

Nicely done 👍👍👍👍👍👍! This has solved a problem that has been bothering me for a while.

同样的问题

Fixed. Thanks @ChunmengLiu1


CA server logs

I am trying to do local setup for Fabric
So to start my CA server and VP0, I made a docker.compose.yml file as per the documentation given on link: http://hyperledger-fabric.readthedocs.io/en/latest/Setup/Network-setup/
My docker.compose.yml file is as follows:
membersrvc:
image: hyperledger/fabric-membersrvc
command: membersrvc
vp0:
image: hyperledger/fabric-peer
environment:
- CORE_PEER_ADDRESSAUTODETECT=true
- CORE_VM_ENDPOINT=http://<IP_ADDRESS>:2375
- CORE_LOGGING_LEVEL=DEBUG
- CORE_PEER_ID=vp0
- CORE_SECURITY_ENROLLID=test_vp0
- CORE_SECURITY_ENROLLSECRET=MwYpmSRjupbT
links:
- membersrvc
command: sh -c "sleep 5; peer node start"
This is the terminal output when i run docker compose up command:
Starting 0b17352fc95e_0b17352fc95e_0b17352fc95e_shambhavi_membersrvc_1
Starting shambhavi_vp0_1
Attaching to 0b17352fc95e_0b17352fc95e_0b17352fc95e_shambhavi_membersrvc_1, shambhavi_vp0_1
vp0_1         | 05:53:01.659 [logging] LoggingInit -> DEBU 001 Setting default logging level to DEBUG for command 'node'
vp0_1         | 05:53:01.661 [peer] func1 -> INFO 002 Auto detected peer address: <IP_ADDRESS>:7051
vp0_1         | 05:53:01.664 [peer] func1 -> INFO 003 Auto detected peer address: <IP_ADDRESS>:7051
vp0_1         | 05:53:01.665 [eventhub_producer] AddEventType -> DEBU 004 registering BLOCK
vp0_1         | 05:53:01.665 [eventhub_producer] AddEventType -> DEBU 005 registering CHAINCODE
vp0_1         | 05:53:01.665 [eventhub_producer] AddEventType -> DEBU 006 registering REJECTION
vp0_1         | 05:53:01.665 [eventhub_producer] AddEventType -> DEBU 007 registering REGISTER
vp0_1         | 05:53:01.665 [nodeCmd] serve -> INFO 008 Security enabled status: false
vp0_1         | 05:53:01.665 [nodeCmd] serve -> INFO 009 Privacy enabled status: false
vp0_1         | 05:53:01.667 [eventhub_producer] start -> INFO 00a event processor started
vp0_1         | 05:53:01.667 [db] open -> DEBU 00b Is db path [/var/hyperledger/production/db] empty [false]
vp0_1         | 05:53:01.852 [chaincode] NewChaincodeSupport -> INFO 00c Chaincode support using peerAddress: <IP_ADDRESS>:7051
vp0_1         | 05:53:01.852 [chaincode] NewChaincodeSupport -> DEBU 00d Turn off keepalive(value 0)
vp0_1         | 05:53:01.852 [sysccapi] RegisterSysCC -> INFO 00e system chaincode (noop,github.com/hyperledger/fabric/bddtests/syschaincode/noop) disabled
vp0_1         | 05:53:01.853 [nodeCmd] serve -> DEBU 00f Running as validating peer - making genesis block if needed
vp0_1         | 05:53:01.855 [state] loadConfig -> INFO 010 Loading configurations...
vp0_1         | 05:53:01.856 [state] loadConfig -> INFO 011 Configurations loaded. stateImplName=[buckettree], stateImplConfigs=map[numBuckets:%!s(int=1000003) maxGroupingAtEachLevel:%!s(int=5) bucketCacheSize:%!s(int=100)], deltaHistorySize=[500]
vp0_1         | 05:53:01.856 [state] NewState -> INFO 012 Initializing state implementation [buckettree]
vp0_1         | 05:53:01.856 [buckettree] initConfig -> INFO 013 configs passed during initialization = map[string]interface {}{"numBuckets":1000003, "maxGroupingAtEachLevel":5, "bucketCacheSize":100}
vp0_1         | 05:53:01.857 [buckettree] initConfig -> INFO 014 Initializing bucket tree state implemetation with configurations &{maxGroupingAtEachLevel:5 lowestLevel:9 levelToNumBucketsMap:map[3:65 8:200001 7:40001 5:1601 0:1 9:1000003 4:321 2:13 1:3 6:8001] hashFunc:0xab4560}
vp0_1         | 05:53:01.857 [buckettree] newBucketCache -> INFO 015 Constructing bucket-cache with max bucket cache size = [100] MBs
vp0_1         | 05:53:01.859 [buckettree] loadAllBucketNodesFromDB -> INFO 016 Loaded buckets data in cache. Total buckets in DB = [0]. Total cache size:=0
vp0_1         | 05:53:01.859 [nodeCmd] serve -> DEBU 017 Running as validating peer - installing consensus
vp0_1         | 05:53:01.860 [peer] initDiscovery -> DEBU 018 Retrieved discovery list from disk: [<IP_ADDRESS>:7051]
vp0_1         | 05:53:01.861 [consensus/controller] NewConsenter -> INFO 019 Creating default consensus plugin (noops)
vp0_1         | 05:53:01.861 [consensus/noops] newNoops -> DEBU 01a Creating a NOOPS object
vp0_1         | 05:53:01.862 [consensus/noops] newNoops -> INFO 01b NOOPS consensus type = *noops.Noops
vp0_1         | 05:53:01.863 [consensus/noops] newNoops -> INFO 01c NOOPS block size = 500
vp0_1         | 05:53:01.863 [consensus/noops] newNoops -> INFO 01d NOOPS block wait = 1s
vp0_1         | 05:53:01.863 [nodeCmd] serve -> INFO 01e Starting peer with ID=name:"vp0" , network ID=dev, address=<IP_ADDRESS>:7051, rootnodes=, validator=true
vp0_1         | 05:53:01.872 [consensus/statetransfer] verifyAndRecoverBlockchain -> DEBU 01f Validating existing blockchain, highest validated block is 0, valid through 0
vp0_1         | 05:53:01.872 [consensus/statetransfer] blockThread -> INFO 020 Validated blockchain to the genesis block
vp0_1         | 05:53:01.872 [consensus/handler] 1 -> DEBU 021 Starting up message thread for consenter
vp0_1         | 05:53:01.874 [peer] ensureConnected -> DEBU 022 Starting Peer reconnect service (touch service), with period = 6s
vp0_1         | 05:53:01.874 [peer] chatWithPeer -> DEBU 023 Initiating Chat with peer address: <IP_ADDRESS>:7051
vp0_1         | 05:53:01.875 [rest] StartOpenchainRESTServer -> INFO 024 Initializing the REST service on <IP_ADDRESS>:7050, TLS is disabled.
vp0_1         | 05:53:04.874 [peer] chatWithPeer -> ERRO 025 Error creating connection to peer address <IP_ADDRESS>:7051: grpc: timed out when dialing
vp0_1         | 05:53:07.874 [peer] ensureConnected -> WARN 026 Touch service indicates dropped connections, attempting to reconnect...
vp0_1         | 05:53:07.874 [peer] ensureConnected -> DEBU 027 Connected to: []
vp0_1         | 05:53:07.874 [peer] ensureConnected -> DEBU 028 Discovery knows about: [<IP_ADDRESS>:7051]
vp0_1         | 05:53:07.875 [peer] chatWithPeer -> DEBU 029 Initiating Chat with peer address: <IP_ADDRESS>:7051
vp0_1         | 05:53:10.875 [peer] chatWithPeer -> ERRO 02a Error creating connection to peer address <IP_ADDRESS>:7051: grpc: timed out when dialing
vp0_1         | 05:53:13.874 [peer] ensureConnected -> WARN 02b Touch service indicates dropped connections, attempting to reconnect...
vp0_1         | 05:53:13.874 [peer] ensureConnected -> DEBU 02c Connected to: []
vp0_1         | 05:53:13.874 [peer] ensureConnected -> DEBU 02d Discovery knows about: [<IP_ADDRESS>:7051]
vp0_1         | 05:53:13.874 [peer] chatWithPeer -> DEBU 02e Initiating Chat with peer address: <IP_ADDRESS>:7051
vp0_1         | 05:53:14.875 [peer] chatWithPeer -> DEBU 02f Established Chat with peer address: <IP_ADDRESS>:7051
vp0_1         | 05:53:14.875 [peer] handleChat -> DEBU 030 Current context deadline = 0001-01-01 00:00:00 +0000 UTC, ok = false
vp0_1         | 05:53:14.876 [peer] SendMessage -> DEBU 031 Sending message to stream of type: DISC_HELLO
vp0_1         | 05:53:14.889 [consensus/handler] HandleMessage -> DEBU 032 Did not handle message of type DISC_HELLO, passing on to next MessageHandler
vp0_1         | 05:53:14.889 [peer] HandleMessage -> DEBU 033 Handling Message of type: DISC_HELLO
vp0_1         | 05:53:14.889 [peer] beforeHello -> DEBU 034 Received DISC_HELLO, parsing out Peer identification
vp0_1         | 05:53:14.889 [peer] beforeHello -> DEBU 035 Received DISC_HELLO from endpoint=peerEndpoint:<ID:<name:"vp1" > address:"<IP_ADDRESS>:7051" type:VALIDATOR > blockchainInfo:<height:1 currentBlockHash:"F\271\335+\013\250\215\023#;?\353t>\353$?\315R\352b\270\033\202\265\014'dn\325v/\327]\304\335\330\300\362\000\313\005\001\235g\265\222\366\374\202\034IG\232\264\206@).\254\263\267\304\276" >
vp0_1         | 05:53:49.888 [peer] beforeGetPeers -> DEBU 08b Sending back DISC_PEERS
vp0_1         | 05:53:49.888 [peer] SendMessage -> DEBU 08c Sending message to stream of type: DISC_PEERS
vp0_1         | 05:53:49.889 [peer] SendMessage -> DEBU 08d Sending message to stream of type: DISC_GET_PEERS
vp0_1         | 05:53:49.889 [consensus/handler] HandleMessage -> DEBU 08e Did not handle message of type DISC_PEERS, passing on to next MessageHandler
vp0_1         | 05:53:49.889 [peer] HandleMessage -> DEBU 08f Handling Message of type: DISC_PEERS
vp0_1         | 05:53:49.889 [peer] beforePeers -> DEBU 090 Received DISC_PEERS, grabbing peers message
vp0_1         | 05:53:49.890 [peer] beforePeers -> DEBU 091 Received PeersMessage with Peers: peers:<ID:<name:"vp0" > address:"<IP_ADDRESS>:7051" type:VALIDATOR >
vp0_1         | 05:53:54.888 [consensus/handler] HandleMessage -> DEBU 092 Did not handle message of type DISC_GET_PEERS, passing on to next MessageHandler
vp0_1         | 05:53:54.888 [peer] HandleMessage -> DEBU 093 Handling Message of type: DISC_GET_PEERS
vp0_1         | 05:53:54.888 [peer] beforeGetPeers -> DEBU 094 Sending back DISC_PEERS
vp0_1         | 05:53:54.888 [peer] SendMessage -> DEBU 095 Sending message to stream of type: DISC_PEERS
vp0_1         | 05:53:54.890 [peer] SendMessage -> DEBU 096 Sending message to stream of type: DISC_GET_PEERS
vp0_1         | 05:53:54.890 [consensus/handler] HandleMessage -> DEBU 097 Did not handle message of type DISC_PEERS, passing on to next MessageHandler
vp0_1         | 05:53:54.891 [peer] HandleMessage -> DEBU 098 Handling Message of type: DISC_PEERS
vp0_1         | 05:53:54.891 [peer] beforePeers -> DEBU 099 Received DISC_PEERS, grabbing peers message
vp0_1         | 05:53:54.891 [peer] beforePeers -> DEBU 09a Received PeersMessage with Peers: peers:<ID:<name:"vp0" > address:"<IP_ADDRESS>:7051" type:VALIDATOR >
vp0_1         | 05:53:55.874 [peer] ensureConnected -> DEBU 09b Touch service indicates no dropped connections
vp0_1         | 05:53:55.874 [peer] ensureConnected -> DEBU 09c Connected to: [<IP_ADDRESS>:7051]
vp0_1         | 05:53:55.874 [peer] ensureConnected -> DEBU 09d Discovery knows about: [<IP_ADDRESS>:7051]
vp0_1         | 05:53:59.888 [consensus/handler] HandleMessage -> DEBU 09e Did not handle message of type DISC_GET_PEERS, passing on to next MessageHandler
vp0_1         | 05:53:59.889 [peer] HandleMessage -> DEBU 09f Handling Message of type: DISC_GET_PEERS
vp0_1         | 05:53:59.889 [peer] beforeGetPeers -> DEBU 0a0 Sending back DISC_PEERS
vp0_1         | 05:53:59.889 [peer] SendMessage -> DEBU 0a1 Sending message to stream of type: DISC_PEERS
vp0_1         | 05:53:59.890 [peer] SendMessage -> DEBU 0a2 Sending message to stream of type: DISC_GET_PEERS
vp0_1         | 05:53:59.890 [consensus/handler] HandleMessage -> DEBU 0a3 Did not handle message of type DISC_PEERS, passing on to next MessageHandler
vp0_1         | 05:53:59.890 [peer] HandleMessage -> DEBU 0a4 Handling Message of type: DISC_PEERS
vp0_1         | 05:53:59.890 [peer] beforePeers -> DEBU 0a5 Received DISC_PEERS, grabbing peers message
vp0_1         | 05:53:59.890 [peer] beforePeers -> DEBU 0a6 Received PeersMessage with Peers: peers:<ID:<name:"vp0" > address:"<IP_ADDRESS>:7051" type:VALIDATOR >
vp0_1         | 05:54:01.874 [peer] ensureConnected -> DEBU 0a7 Touch service indicates no dropped connections
vp0_1         | 05:54:01.874 [peer] ensureConnected -> DEBU 0a8 Connected to: [<IP_ADDRESS>:7051]
vp0_1         | 05:54:01.874 [peer] ensureConnected -> DEBU 0a9 Discovery knows about: [<IP_ADDRESS>:7051]
vp0_1         | 05:54:04.887 [consensus/handler] HandleMessage -> DEBU 0aa Did not handle message of type DISC_GET_PEERS, passing on to next MessageHandler
vp0_1         | 05:54:04.888 [peer] HandleMessage -> DEBU 0ab Handling Message of type: DISC_GET_PEERS
vp0_1         | 05:54:04.888 [peer] beforeGetPeers -> DEBU 0ac Sending back DISC_PEERS
vp0_1         | 05:54:04.888 [peer] SendMessage -> DEBU 0ad Sending message to stream of type: DISC_PEERS
vp0_1         | 05:54:04.889 [peer] SendMessage -> DEBU 0ae Sending message to stream of type: DISC_GET_PEERS
vp0_1         | 05:54:04.890 [consensus/handler] HandleMessage -> DEBU 0af Did not handle message of type DISC_PEERS, passing on to next MessageHandler
vp0_1         | 05:54:04.890 [peer] HandleMessage -> DEBU 0b0 Handling Message of type: DISC_PEERS
vp0_1         | 05:54:04.890 [peer] beforePeers -> DEBU 0b1 Received DISC_PEERS, grabbing peers message
On another terminal, i run the following command to start my VP1:
docker run --rm -it -e CORE_VM_ENDPOINT=http://<IP_ADDRESS>:2375 -e CORE_PEER_ID=vp1 -e CORE_PEER_ADDRESSAUTODETECT=true -e CORE_PEER_DISCOVERY_ROOTNODE=<IP_ADDRESS>:7051 hyperledger/fabric-peer peer node start
and give my VP0 IP as CORE_PEER_DISCOVERY_ROOTNODE in the above command
So my query is that VP0 and VP1 are communicating, but how to verify that CA server has  also started as there is no specifc log for CA coming
Please help!!!!

any solution?


NIFI-2032 fixed 'enableControllerServices' logic

added getRequiredControllerServices() operation to ControllerServiceNode

Thanks @olegz . I will build locally and merge.

Getting a compilation failure missing import org.apache.nifi.reporting.BulletinFactory. Did this get missed in the second commit?

I see, it appears that I have to reference different org.apache.nifi.events.BulletinFactory, building now

@alopresto so I just fixed it and squashed it with the last commit. No compilation error on my end. LMK

I merged into master but I've had to rebase and resolve conflicts 3 times on 0.x branch and still have tests failing. Will continue working on that part in the morning.

@alopresto let me look at what's going on with 0.x and I'll issue a separate PR. Thanks!


Reproducing the issue in the tests

Description
EDIT: Sorry folks. New to open source dev and didn't realize I was making a PR against vite and not my fork 😳
For those interested, here's my draft reproduction: https://github.com/GeordiD/vite/pull/1
Closing this

My bad, didn't realize where I was pointing this PR.
For those interested, here's my draft reproduction: https://github.com/GeordiD/vite/pull/1
Closing this


Switch opticks submodule to bitbucket repository

opticks is actively developed using a Git repo hosted on bitbucket.org

#1 0.274 Submodule 'opticks' (git@bitbucket.org:simoncblyth/opticks.git) registered for path 'opticks'
#1 0.275 Cloning into '/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/2/fs/opticks'...
#1 0.364 Warning: Permanently added 'bitbucket.org' (ED25519) to the list of known hosts.
#1 0.395<EMAIL_ADDRESS>Permission denied (publickey).
#1 0.395 fatal: Could not read from remote repository.
#1 0.395
#1 0.395 Please make sure you have the correct access rights
#1 0.395 and the repository exists.
#1 0.395 fatal: clone of 'git@bitbucket.org:simoncblyth/opticks.git' into submodule path '/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/2/fs/opticks' failed
#1 0.395 Failed to clone 'opticks'. Retry scheduled
#1 0.397 Cloning into '/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/2/fs/opticks'...
#1 0.474<EMAIL_ADDRESS>Permission denied (publickey).
#1 0.474 fatal: Could not read from remote repository.
#1 0.474
#1 0.474 Please make sure you have the correct access rights
#1 0.474 and the repository exists.
#1 0.474 fatal: clone of 'git@bitbucket.org:simoncblyth/opticks.git' into submodule path '/var/lib/buildkit/runc-overlayfs/snapshots/snapshots/2/fs/opticks' failed
#1 0.474 Failed to clone 'opticks' a second time, aborting
#1 ERROR: failed to update submodules for https://github.com/BNLNPPS/esi-opticks.git: git error: exit status 1

Resolved in #39


Add support for Apache CXF Client calls

Is your feature request related to a problem? Please describe.
When observing a service that calls a SOAP Service using an Apache CXF generated Client, there is no span showing up for the HTTP Call.
Describe the solution you'd like
HTTP SOAP Calls created by an Apache CXF Client should generate a new span in the current transaction. The called URL should also be reported.
Describe alternatives you've considered
Since Apache CXF uses a simple URLConnection (https://github.com/apache/cxf/blob/master/rt/transports/http/src/main/java/org/apache/cxf/transport/https/HttpsURLConnectionFactory.java#L90) i expected that a new span would be created by the url-connection-plugin.

Since Apache CXF uses a simple URLConnection [...] i expected that a new span would be created by the url-connection-plugin.

That's what I would expect too. Which version if the agent are you using? Could you send me the debug logs from startup to the first request where you would expect the client span?

Okay, so I tried to reproduce this locally against a cloud hosted elastic cluster and the call shows up. So this seems to be an issue with our setup and not with the agent. Feel free to close this issue :-)

I’m happy to hear that. If you need help with the setup don’t hesitate to comment on this closed issue.

Updating the agent to version 1.5 (from whatever we had before?) also fixed this issue, so all is good now. :-)

Probably you used a version pre 1.4.0, which did not have support for HttpUrlConnection yet. See also https://www.elastic.co/guide/en/apm/agent/java/current/supported-technologies-details.html#supported-networking-frameworks


add browsers field

This is a real fix for #117 to prevent webpack build warnings. Webpack will automatically use the browser build (see https://webpack.github.io/docs/configuration.html#resolve-packagemains).

I am not sure why adding "browser" field breaks the tests. I thought it was some dependency update, but then the following PR passed... Does it pass when you run them locally? Is it maybe breaking browserify?

It seems like it breaks the bundle creation indeed:
Works: https://travis-ci.org/epoberezkin/ajv/jobs/155026726#L2271
Breaks: https://travis-ci.org/epoberezkin/ajv/jobs/154730115#L2275
See https://github.com/substack/node-browserify#browser-field

It correct that browserify uses the browser field just like webpack. But it should be the correct way to deploy the browser build. If the CI task breaks it probably means that dist/ajv.bundle.js would break in the same CI task, too.
I'll try to run the tests locally.
I could use a webpack field instead of browser. That also works for webpack users and probably wouldn't break your CI job. I'm not a browserify user, but as far as I understand browserify they would want a browser field, too?

Tests run locally when using webpack. It fixes the warnings with #117. We can definitely start with the webpack field and if any browserify user needs a browser field we can switch to it later and fix the CI tasks.

I'm not a browserify user, but as far as I understand browserify they would want a browser field, too?

If you want to use the bundle it can be just loaded separately. You can either use browserify to create this bundle (that's what is used here) or you can bundle Ajv as part of your application, in which case you just use var Ajv = require('ajv').
I am not sure I understand what would be your code to use Ajv if you include the bundle rather than the index file - the bundle doesn't return the Ajv constructor as far as I understand. Would you just use global that the bundle exposes? In which case I don't think I understand why you need webpack at all if you use the bundle. And if you are going to use as above I don't think it would work.

Isnt the bundle a UMD file? Than it would return the constructor. It must be that way as I can use Ajv just fine with the bundled file.
"why you need webpack at all if you use the bundle" Well, I use the bundled file of Ajv, but my application has a lot of other dependencies and my own source code which wants to be bundled, too. Right? ;) And why would I want a prebundled file of one my dependencies? Well, to get rid of all the warnings from requires in try/catch-blocks for optional dependencies :)

Got it. Thank you!

Thank you!

In 4.6.0

Webpack still complains
WARNING in ./~/ajv/dist/ajv.bundle.js
Critical dependencies:
1:476-483 This seems to be a pre-built javascript file. Though this is possible, it's not recommended. Try to require the original source to get better results.
 @ ./~/ajv/dist/ajv.bundle.js 1:476-483

Seems like the best way to solve this is just to pass these dependencies in via the options.

Interesting. I don't get this warning. But it is a different warning and it is just one, not three. Hmm...

Wouldn't the better solution be to simply add to docs the instruction to use IgnorePlugin (see https://github.com/epoberezkin/ajv/issues/117#issuecomment-198328830)?

In which case users who use any of those packages could also have them included by changing the regexp?

I think that at least for now there should be some documentation. I am not using the async features in my app so my workaround is to import Ajv from 'ajv/lib/ajv'; and to use the following in my webpack config:
new webpack.IgnorePlugin(/^regenerator|nodent|js\-beautify$/, /ajv/),

I think that the choice of whether to include nodent or regenerator on the frontend is not one that should be hidden to the user because they are pretty large.  I almost abandoned using Ajv on the frontend (after using it on my backend) because I thought I need to add another ~300kb (uncompressed) to my bundle. I would propose the following to sidestep this problem all together:
import Ajv from 'ajv';
import regenerator from 'regenerator';

const ajv = new Ajv({ regenerator });

This would simplify the configuration over using transform: 'regenerator' and async: 'es7' and make it more explicit about what you are actually adding to your bundle when you use Ajv. Either way you still need to add it to package.json. Bundled dependencies only seem useful if you managing your dependencies with script tags.
Anyway that's my 2 cents. Sorry if this is off topic to this pull request.

I'd like to not include framework specific configuration to my webpack configuration. I share between a lot of (compex) projects and so far it works without specific configurations. I thought the browsers field would be the idomatic way to load a browser specific build from a framework both for webpack and browserify. (I also thought This seems to be a pre-built javascript file. is mostly about minified files.)
@sokra Is there a way to rewrite this line so it is ignored by webpack, but usable by browserify?

Use the browser field it you want different modules for browser and server.

So what is the correct configuration to avoid This seems to be a pre-built javascript file. webpack warning?

In our case we did:
module: {
    // Without this webpack will log a warning.
    noParse: /node_modules\/ajv\/dist\/ajv.bundle.js/
}

And it seems to be working fine. From my understanding, ajv wants us to use dist/ajv.bundle.js when we're building for the browser and dist/ajv.bundle.js is built using webpack/browserify/whatever so using noParse seems appropriate. I guess.


Chapter user progress component

Motivations
Implement the view which represents the progress of a user on a chapter. (design)
Subtasks
Display, in the chapter user progress tab of items, a table with:

as row, all
as columns:

Content: the item name (with a link)
Latest activity: in "YY-MM-DD HH:MM"
Time spent: displayed with | duration
# subm. : submissions (a number)
score: score/validated as a score ring

Waiting for https://github.com/France-ioi/AlgoreaBackend/issues/780 to be implemented/deployed.


Can't install: tensorflow-gpu library not found?

As per the given instructions I'm running pip install -r requirements.txt but after installing a bunch of stuff I'm getting this fatal error:

Collecting tensorflow-gpu==1.4.0 (from -r requirements.txt (line 21))
Could not find a version that satisfies the requirement tensorflow-gpu==1.4.0 (from -r requirements.txt (line 21)) (from versions: 0.12.0rc1, 0.12.0, 0.12.1, 1.0.0, 1.0.1, 1.1.0rc0, 1.1.0rc1, 1.1.0rc2, 1.1.0)
No matching distribution found for tensorflow-gpu==1.4.0 (from -r requirements.txt (line 21))

Unfortunately I have zero experience with tensorflow (or pip, for that matter). Is there an easy way to work around this?

Operating system: macOS High Sierra (10.13.4)
Running python --version says: Python 2.7.15.
Running python3 --version says: Python 3.7.0.

When trying to run my code, does it work if you use pip3 and python3 instead of pip and python?

I tried pip3 install -r requirements.txt, at first I got an error about some library being outdated and having to run pip install --upgrade pip.
I assumed I had to run pip3 install --upgrade pip instead, which seemed to get rid of the first error.
When running pip3 install -r requirements.txt again I now got a rather long error log, which I uploaded here in case it explains anything, I hope this is of any help?

So I was looking into tensorflow 1.4.0 on mac and apparently as of tensorflow 1.2.0, gpu is not supported on mac. That makes things interesting.
That leaves a few possible options:

Try using just tensorflow instead of tensorflow-gpu in requirements.txt. This will greatly lower speed but should be functional, especially if you just want to play the best model.
Try using tensorflow-gpu version1.1.0. I have no idea if this will function correctly, but it may be worth trying.
Try using a different computer that isn't mac.

Thanks for the suggestions and feedback, much appreciated. Unfortunately with 1 and 2 I'm still getting the same long list of error output, and 3 is not an option (I only have a mac).
Note however that I see a lot of compile errors that seem to be related to numpy. Now that I think of it, that was also the module that caused the initial error, warning me to upgrade pip3. In particular I see a bunch of errors related to numpy/random/mtrand/mtrand.c which I assume is a mersenne prime twister based random generator (I know because that's what it's also called in php). Either way some part of the numpy library, not related to tensorflow.
If I just do this: pip3 install numpy==1.14.0 I am also getting that same bunch of errors.
Could there be something else wrong or missing, or is there anything else I can check or update about my code environment, which may help resolve the errors from building/installing numpy?

You might want to try installing libraries one by one and not restricting the versions. I would start with trying to get Tensorflow and Keras to work because they are the most important. I think it might be possible that some of the versions I have specified do not work well with mac.
I wish I had more knowledge about your issue, but it is an issue with the C in numpy compiling on your mac.

Potentially you could try using Anaconda with my environment.yml file(or manual install in conda) to see if that will allow you to properly install the libraries.


Fixed directories in GH pages links

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
0

Relevant Lines:
0

💛  - Coveralls


TTNN eltwise_acosh - fail when input tensor has ROW_MAJOR layout (GS and WH)

ttnn.acosh fails in cases when layout of an input tensor is ROW_MAJOR. During sweep test, for every combination of parameters with layout = ROW_MAJOR, an error occurs in this format:

Always | FATAL    | For valid non-interleaved buffers page size 2048 must equal buffer size 19008. For interleaved-buffers page size should be divisible by buffer size

Sweep test crashes with Fatal Python error: Floating point exception.
To Reproduce
Steps to reproduce the behavior:

Checkout branch amalbasaTT/opsets4and5-unit-tests
Run command:pytest tests/ttnn/python_api_testing/non_working_unit_tests/grayskull/test_eltwise_acosh.py

Expected behavior
Test case should fail with the error:

RuntimeError: TT_FATAL @ ../ttnn/cpp/ttnn/operations/eltwise/binary/device/binary_device_operation.cpp:194:                               (input_tensor_a.get_layout() == Layout::TILE && input_tensor_b.get_layout() == Layout::TILE)
info:
Inputs to eltwise binary must be tilized

Getting Additional info for the operation under test and its behavior:
To get additional information and results for different combinations of input shapes, types, layouts and memory configs for which this operation was tested you can also run locally sweep test:
pytest tests/ttnn/python_api_testing/sweep_tests/run_sweep_test.py --input-path tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_working/grayskull/ttnn_eltwise_acosh_test.yaml --input-method cli --cli-input results_ttnn_eltwise_acosh

To do this, you should:

Follow the Getting Started page to setup the repo, environment variables and python-env
Activate source build/python_env/bin/activate
Checkout amalbasaTT/opsets4and5-unit-tests
Run sweeps by using pytest tests/ttnn/python_api_testing/sweep_tests/run_sweep_test.py --input-path tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_working/grayskull/ttnn_eltwise_acosh_test.yaml --input-method cli --cli-input results_ttnn_eltwise_acosh
After the run is completed all test sweeps results should be available inside specified output directory (in this case ./results_ttnn_eltwise_acosh). There you will find .csv which holds all executed sweeps, among which you can also find the ones that failed and were recreated by the unit test, which you can get by searching unique data_seed field.

Test file gives the appropriate error


Logged-in as Page is not working properly.

Not trying to duplicate the issue from #772
I've left a comment there but doesn't seem to get any response.
Does it work yet? I've tried but couldn't get it to work.
I tried using both api.listenMqtt  and api.listen and callback function just return undefined.

(Same picture from #772)

@7osCraft

Everything is working fine for me. Please make sure the page id is valid and the account you use in the api has the permission to view page messages.

@7osCraft May I know which method did you use? listenMqtt or  listen? I haven't tested again since checkpoint happened frequently

listen is now depecrated. I tested with listenMqtt which is the working method.

@7osCraft
Login is not working for me.
const login = require('facebook-chat-api');

// Create simple echo bot
login({email: 'email', password: 'password'}, (err, api) => {
  if (err) return console.error(err);

  api.listen((err, message) => {
    api.sendMessage(message.body, message.threadID);
  });
});

info login Logging in...
info login Logged in
info login Request to reconnect
info login Request to pull 1
ERR! login Error inside first pull request. Received HTML instead of JSON. Logging in inside a browser might help fix this.
{ error:
   'Error inside first pull request. Received HTML instead of JSON. Logging in inside a browser might help fix this.' }

Please use the latest bleeding edge version. It has the fix for this.


XMLDOC translated to English

Besides the translation of the XMLDOC there is also a .gitignore file and the *.local files have been removed. The comments inside the implementation part are still untranslated.

Merged your pull request. Thanks for creating it!


[The Office Quotes] ... Failed to load quotes getaddrinfo ENOTFOUND www.officeapi.dev

Extension
https://www.raycast.com/braydoncoyer/office-quotes
Description
First time install... can't use it. Says: Failed to load quotes getaddrinfo ENOTFOUND www.officeapi.dev
Steps To Reproduce
Just install and open in raycast.
Current Behaviour
Says: Failed to load quotes getaddrinfo ENOTFOUND www.officeapi.dev
Expected Behaviour
See office quotes

Plus one, still failing


Local run_gui.ps1 OSError: [WinError 127]

Traceback (most recent call last):
File "C:\layerdivider\layerdivider\demo.py", line 8, in
from ldivider.ld_segment import get_mask_generator, get_masks, show_anns
File "C:\layerdivider\layerdivider\ldivider\ld_segment.py", line 1, in
from segment_anything import sam_model_registry, SamAutomaticMaskGenerator, SamPredictor
File "C:\layerdivider\layerdivider\venv\lib\site-packages\segment_anything_init_.py", line 7, in
from .build_sam import (
File "C:\layerdivider\layerdivider\venv\lib\site-packages\segment_anything\build_sam.py", line 7, in
import torch
File "C:\layerdivider\layerdivider\venv\lib\site-packages\torch_init_.py", line 122, in
raise err
OSError: [WinError 127] 指定されたプロシージャが見つかりません。 Error loading "C:\layerdivider\layerdivider\venv\lib\site-packages\torch\lib\cublas64_11.dll" or one of its dependencies.
続行するには、Enter キーを押してください...:
I've reinstalled it many times, but no improvement.

I have the exact same problem, I installed the CUDA and CUDNN and all the requirements and I still get that error

I have the exact same problem, I installed the CUDA and CUDNN and all the requirements and I still get that error

My friend has found a fix for this, I have listed the steps in another page: https://github.com/mattyamonaca/layerdivider/issues/48


Fix buffer metrics issue on Python 3

Currently I am encounter the following issue on python 3:
    def flush(self, send_partial = True):
        '''Sends as much data as possible to CloudWatch. If send_partial is set to False,
            this only sends full pages. This way, it minimizes the API usage at the cost of
            delaying data.
            '''
        for namespace, buffer in self.buffers.items():
            full_pages = len(buffer) / PAGE_SIZE
>           for i in range(full_pages):
E           TypeError: 'float' object cannot be interpreted as an integer

Having the same issue.
Looks like current release of cloudwatch-fluent-metrics==0.3.0 does not have this change yet?


Feat/add logo data in cms footer collection

Description
Add footer logos to cms footer collection.
minor

Footer logos are generated from the cms.

Let's set the logo size is fixed as 170 * 34. consider to stretch the image if the image is smaller than this dimension.

I standardized the size of logos to 163x45, ensuring a uniform and complete presentation for all logos.


[ gtest ] Update port to include fix for C++20 compliance

Is your feature request related to a problem? Please describe.
GTest in vcpkg uses std::result_of which was removed in C++20.
Proposed solution
The port should be updated/patched to include this fix from this commit https://github.com/google/googletest/commit/61f010d703b32de9bfb20ab90ece38ab2f25977f

After gtest releases the latest version, we will update the problem to the latest version


Add condition for service clusterIP

Signed-off-by: Hariharan Subramanian<EMAIL_ADDRESS>
What this PR does / why we need it:
Add condition on the service clusterIP so it didn't set the clusterIP if one wasn't defined.
Why we need it:
First time when the service is created without clusterIP defined a clusterIP is set. The next time we run the yaml file it will fail as the clusterIP is empty and it tries to set a clusterIP
Which issue this PR fixes
(optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged)

fixes #

Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped

@davidkarlsen @prydonius Can you please review when you get a chance? Thanks!

/ok-to-test

Thanks for the contrib @hariharan16s

/approve

/lgtm

Thanks for the contrib @hariharan16s

Thanks for the review @lachie83

I didn't change anything to my values and after update I got: Error: UPGRADE FAILED: Service "cluster-autoscaler-aws-cluster-autoscaler" is invalid: spec.clusterIP: Invalid value: "": field is immutable
@hariharan16s
The patch doesn't seem backward compatible.

@mbelang : This was the same error I got before making the change.
Are you defining a ClusterIP in values? Not sure in your case how in the previous versions the clusterIP is being tracked as we had to define the clusterIP in values to get rid of the error.
Basically first time when the service is created without clusterIP defined, a clusterIP was set. The next time we run the yaml file it will fail as the clusterIP is empty and it tries to set a clusterIP which it should not.

@hariharan16s

Are you defining a ClusterIP in values? Not sure in your case how in the previous versions the clusterIP is being tracked as we had to define the clusterIP in values to get rid of the error.
No

I do understand the purpose of the fix but it is odd that I do not have the problem on 0.12.0 and I have it on 0.12.1.
here is my value file:
autoDiscovery:
  clusterName: my-cluster-name

cloudProvider: aws
awsRegion: us-east-1

extraArgs:
  v: 1

podAnnotations:
  iam.amazonaws.com/role: cluster-autoscaler
  scheduler.alpha.kubernetes.io/critical-pod: ''

rbac:
  create: true

sslCertPath: "/etc/ssl/certs/bundle.crt"
sslCertHostPath: "/etc/ssl/certs/bundle.crt"

@mbelang : Looks like this just appears to be issue with an upgrade with clusterIP not defined and not a fresh install. Let me try to replicate this and get back to you.

Seeing a similar issue:
Service "cluster-autoscaler-aws-cluster-autoscaler" is invalid: spec.clusterIP: Invalid value: "": field is immutable
I did alter my values file to contain a service section to try and get around this based on the requirements that were added to the chart for the service manifest in the last update:
service:
  clusterIP: ""

This doesn't really change anything. If I helm get the release, I see this for the service yaml:
# Source: cluster-autoscaler/templates/service.yaml
apiVersion: v1
kind: Service
metadata:
  labels:
    app: aws-cluster-autoscaler
    chart: cluster-autoscaler-0.12.1
    heritage: Tiller
    release: cluster-autoscaler
  name: cluster-autoscaler-aws-cluster-autoscaler
spec:
  ports:
    - port: 8085
      protocol: TCP
      targetPort: 8085
      name: http
  selector:
    app: aws-cluster-autoscaler
    release: cluster-autoscaler
  type: "ClusterIP"

You can see in this case there's just no spec.clusterIP entry at all even though the default values file seems to include clusterIP: "" and my local values file explicitly adds it anyway.

@hariharan16s is the solution for now just to delete the release and redeploy?

Was there ever any movement on this? I'd like to get this working properly.

@echoboomer : For now try to delete the service and the next time you apply the yaml with clusterIP: "" it should work as expected.

This is a long standing issue in other charts and still has no resolution https://github.com/helm/charts/issues/9227
It was reverted from nginx-ingress because the conditional creates a deployment that cannot be upgraded: https://github.com/helm/charts/pull/10993
This change should be reverted because it prevents upgrades.


fix:[OTHER] Use main tag instead of div tag #103

Fixes Issue
Closes #103
Changes proposed

replaced div tag with the main tag around issues listing from src/routes/index.svelte

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[x] All new and existing tests passed.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

Screenshots
before:

After:

Thank you Tom.


feat(QTREES-363): useFeedbackData hook

This PR add the hook useFeedbackData, which provides the list of issue types that can be reported and also manages saving those in the local storage. It provides a handler to report an issue as well.

:tada: This PR is included in version 1.0.0-staging.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


To gather in a group in V-Sekai, organize a meetup

Group experience!

[x] Flat
[x] Virtual Reality

Postponed.


Rename Azure AD /1

Fixes #30200
Fixes #30242
Fixes #30244
Fixes #30246
Fixes #30245

Internal previews

📄 File
🔗 Preview link

aspnetcore/host-and-deploy/linux-apache.md
Host ASP.NET Core on Linux with Apache

aspnetcore/host-and-deploy/linux-nginx.md
[Ubuntu](https://review.learn.microsoft.com/en-us/aspnet/core/host-and-deploy/linux-nginx?branch=pr-en-us-30247)

aspnetcore/security/authentication/social/additional-claims.md
Persist additional claims and tokens from external providers in ASP.NET Core

aspnetcore/security/authentication/ws-federation.md
Authenticate users with WS-Federation in ASP.NET Core

aspnetcore/security/authorization/policies.md
Policy-based authorization in ASP.NET Core

@tdykstra I took all your suggestions


Update pair.sharing.io to use Cluster-API v1.1.3

Cluster-API is stable now and Cluster-API v1 support is out for Equinix Metal.
Depends on #140

Complete!


[FAB-16846] Fix OU validation

Type of change

Bug fix

Description
WIP,

when OU enforcement is disabled validate specified identities
when OU enforcement is enabled validate identity to ensure only one special OU exists

Related issues
FAB-16846

I don't see why the problem that the user reported in the JIRA is really a bug:
He laments:

consider I have define my own ou, the array msp.ouIdentifiers are not empty （only contain the OrganizationalUnits I've defined and not contain node ou).So 'admin' ou will not be found.

However if he defines an OU (or several), then it means (by definition) that every certificate the MSP recognizes should be among these OUs.
He defined the node OUs as "client", "admin", etc. which obviously contradicts the MSP definition of:
OrganizationalUnitIdentifiers:
  - Certificate: "cacerts/cacert1.pem"
    OrganizationalUnitIdentifier: "zc"

I think what we may want to do, is to change our tooling such that it won't be possible to create a channel creation transaction (or a genesis block) with such a contradiction.
Opinions? @adecaro  @ale-linux

Just to repeat things here as well, @adecaro has looked into the jira and left some questions there - let's figure those out first before we proceed with this CR

For now, closing this draft as user error.


Add note about deploying dev environment to Heroku

According to the #398

👍

Thanks @bocharsky-bw

Thanks for tweaking the message!


Docs: Update support referencing support package tool

Proposed changes
Troubleshooting in Kubernetes requires collecting data from various sources of the kubernetes API.
The nginx-supportpkg-for-k8s is such a tool that NGINX has created to make this data collection as easy as possible.

This PR updates the support page of NGF docs referencing this tool in a similar manner to what was added to NIC docs

Checklist
Before creating a PR, run through this checklist and mark each as complete.

[x] I have read the CONTRIBUTING doc
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have checked that all unit tests pass after adding my changes
[x] I have updated necessary documentation
[x] I have rebased my branch onto main
[x] I will ensure my PR is targeting the main branch and pulling from my branch from my own fork

Hi @ADubhlaoich , thanks for reviewing the material.
I have accepted your suggestions.
Please, let me know of any others.
Otherwise, please update branch and merge as I don't have permissions for this.

If we want to publish this right away, then once this is merged into main, we'll need to create a cherry-pick commit and pull request to the release-1.5 branch.

Thanks for the suggestion @sjberman, yes please, if possible.


8none1/effectsspeedcheck

Fixes: https://github.com/raulgbcr/lednetwf_ble/issues/12

Looks good, I ordered one of this LEDs to test too! Maybe in the future if someone really needs that we can implements effects per device and separate them, the main code should support that easily enough since it was thought to support various models.
Thanks again for the work! Feel free to merge 😄


[Bug] Incorrect Vertica datatype parsing

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
We have fields in Vertica with datatypes interval hour to second, interval day to second. In generated dbt docs we see datatypes interval hour, interval day
Expected Behavior
Correct datatypes in generated docs
Steps To Reproduce
Create model
{{
    config(
        materialized='view'
    )
}}
select cast('25 sec' as INTERVAL hour TO SECOND(6)) as duration;

Run dbt docs generate, dbt docs serve
Relevant log output
No response
Environment
- OS: Mac 14.2.1
- Python: 3.9
- dbt: 1.6.3

Which database adapter are you using with dbt?
No response
Additional Context
No response

Thanks for reaching out @igor-kramer !
This looks like it is behavior that is specific to the dbt-vertica adapter (rather than dbt-core), so I'm going to close this in favor of you opening an issue within dbt-vertica instead:
https://github.com/vertica/dbt-vertica/issues


NullPointerException could be Thrown at line 124 of org.apache.dubbo.rpc.cluster.loadbalance.RoundRobinLoadBalance

[ ] I have searched the issues of this repository and believe that this is not a duplicate.

Environment

Dubbo version: 3.0
Operating System version: Any
Java version: 1.8

Steps to reproduce this issue
An NPE could be thrown at line 124 of org.apache.dubbo.rpc.cluster.loadbalance.RoundRobinLoadBalance. selectedWRR could be null because the condition cur > maxCurrent may not be true.
    protected <T> Invoker<T> doSelect(List<Invoker<T>> invokers, URL url, Invocation invocation) {
        WeightedRoundRobin selectedWRR = null;
        // other codes
        for (Invoker<T> invoker : invokers) {
            // other codes
            if (cur > maxCurrent) {
                selectedWRR = weightedRoundRobin;
            }
        }
        if (selectedInvoker != null) {
            selectedWRR.sel(totalWeight); // selectedWRR could be null.
            return selectedInvoker;
        }

Actual Behavior
An NPE could be thrown at line 124 because no defensive null check is provided.

selectedWRR and selectedInvoker are being set in the same time. It is impossible that selectedWRR is null and selectedInvoker is not null.


montserrat: 7.210 -> 7.222

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/montserrat/versions.
meta.description for montserrat is: "A geometric sans serif font with extended latin support (Regular, Alternates, Subrayada)"
meta.homepage for montserrat is: "https://www.fontspace.com/julieta-ulanovsky/montserrat"
meta.changelog for montserrat is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 7.222 with grep in /nix/store/0pvj73k47x0j17afscw5ypayxdyvq46y-montserrat-7.222

found 7.222 in filename of file in /nix/store/0pvj73k47x0j17afscw5ypayxdyvq46y-montserrat-7.222

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

2 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 x86_64-darwin rebuild(s)

First fifty rebuilds by attrpath
montserrat

Instructions to test this update (click to expand)

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

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

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

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

1 package built:

montserrat

Maintainer pings
cc @scolobb @06kellyjac for testing.

@ofborg eval


Fix the function formats for /microsoft.graph.#

Linked to: https://github.com/microsoftgraph/msgraph-sdk-powershell/issues/151


Wget/Curl Download and Bash Execution: Changing logic for search terms, to make searches comply with title and intention

Details
The logic in the queries here has an OR between the matching on quiet/stdout and the match for pipe and "bash".
This causes the query to hit when wget/curl is either silenced or piped to bash.
From the title i would maybe assume that an AND between the quiet/stdout check and pipe+bash check would be the correct queries?
Searches modified:

Wget Download and Bash Execution
Curl Download and Bash Execution

Checklist

[ ] Validate name matches <platform>_<mitre att&ck technique>_<short description> nomenclature
[ ] CI/CD jobs passed ✔
[ ] Validated SPL logic.
[ ] Validated tags, description, and how to implement.
[ ] Verified references match analytic.

Hey @DipsyTipsy , we are working to fix this up. I agree with your fixes. We're in the midst of ensuring we can generate new data that we can test against. We appreciate the feedback and apologize for the long delay in getting this resolved.

Hey @DipsyTipsy , we got the updates updated. Apologies for the delay! This will go out next release along with a reference to you for your awesome help! Really appreciate the feedback and your patience!

Hello @DipsyTipsy - sorry this took a bit for us to test, there are currently some TA limitations with the test data set but after testing this with @MHaggis , its evident that the detection needs to be fixed. We have added a note at the bottom of the yaml mentioning this limitation. Thank you for updating this detection !!


Revert "Resolve a number of bugs resulting in corrupt dependency graphs"

Reverts gradle/gradle#29853 as it currently causes failures when trying to upgrade the Gradle wrapper to the latest nightly.

@bot-gradle test QF

I've triggered the following builds for you. Click here to see all build failures.

QuickFeedback build

@bot-gradle test

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build


Durability QoS

Related:

https://github.com/eProsima/Micro-XRCE-DDS-Agent/pull/248
https://github.com/eProsima/Micro-XRCE-DDS/pull/90
https://github.com/micro-ROS/rmw-microxrcedds/pull/133

Build status:

Linux
Windows

Build status:

Linux
Windows