Cross-Site Scripting (XSS) vulnerability - CVE-2024-6484

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
A vulnerability has been identified in Bootstrap that exposes users to Cross-Site Scripting (XSS) attacks. The issue is present in the carousel component, where the data-slide and data-slide-to attributes can be exploited through the href attribute of a tag due to inadequate sanitization. This vulnerability could enable attackers to execute arbitrary JavaScript within the victim's browser.
Found a medium-level vulnerability issue in the Fortify scan for all 5.x series versions also
References
https://github.com/advisories/GHSA-9mvj-f7w8-pvh2
Reduced test cases
vulnerability issue
What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?
Chrome
What version of Bootstrap are you using?
5.3.3

Is there a plan to fix this vulnerability?


Does #3067 corrected valus < min too?

Issue # 3067 corrected values > Max (pointer doesn't stop), but we see values < min that makes pointer overpass min value.

Latest echarts version don't have this problem. https://ecomfe.github.io/echarts-examples/public/editor.html?c=gauge


Fix #4634: unite processing of allOf, anyOf, oneOf relation so it wil…

…l work same in OpenAPI 3.1 and OpenAPI 3.0

Fixes #4634
Thank you @GooDer for your work and provided fix


[Avatar] Fix TypeScript error on imgProps

[x] I have followed (at least) the PR section of the contributing guide.
This pr will close #30238

uhh sorry, i was using github.dev, i will work on this once i'm at home

So, I've tried running yarn prettier as suggested in the CI but nothing changed, so I confused about what to do at this point

So, I've tried running yarn prettier as suggested in the CI but nothing changed, so I confused about what to do at this point

Not sure why you didn't see any changes. I've run and committed them. Should be good to go now. Thanks!

Ok thanks 😄


Installation failed on the on prem devops server 2022

We are trying to install the build tools in on-prem devops server 2022. downloaded the latest 2.0.71 vsix and tried to upload, but getting the error message "Authentication schemes ms.vss-endpoint.endpoint-auth-scheme-workload-identity-federation, are not valid".
Looks like we need to enable workload identity federation authentication scheme, but not sure where. Can someone please help how to resolve this?

Hi !
We are using AzureDevOps Server (on-Prem 2022), it's not the last version (2022.0.1). I will try the last update 2 in PreProd.
Getting the same error ""Authentication schemes ms.vss-endpoint.endpoint-auth-scheme-workload-identity-federation, are not valid".
I tried to install the extension manually without success (with gallery admin page).
Please, Help :).
Flo

Hi !
Bad news, I tried with AzureDevOps 2022.2 (07/09/2024) and the latest extension of PowerPlatform 2.0.74 and it failed with the same error.
Flo

Hi !
I change my answer !
Just Install the Update 2 (RTW), it adds the necessary to install the last version of the extension !


Basic roaster functionality

Summary by CodeRabbit
Release Notes

New Features

Introduced a web-based interface for controlling coffee roasting processes with real-time updates.
Implemented a FastAPI application for managing both simulated and real coffee roasting hardware.
Added functionality for managing roast profiles, including saving, loading, and deleting profiles.
Enabled real-time data visualization for temperature and control metrics using charts.
Integrated servo motor control through the Maestro controller for enhanced roasting automation.

Bug Fixes

Improved error handling for WebSocket connections and file operations.

Documentation

Added structured representation for coffee roasting profiles in JSON format.

Going to merge this just to keep momentum, but need to do some serious auditing of the code soon


Used is_callable instead of method_exists

Since a Serializer class might use __call(..) to resolve relations it might be better to use is_callable([$this, $method]) instead of method_exists($this, $method).

Thanks for the PR! Please see the resolution of the similar PR: https://github.com/tobscure/json-api/pull/107#issuecomment-278274417

Thanks!


adding my school

los angeles cartagena colombia

@waruiaoshi First stage of verification passed, official domain is losangelescartagena.edu.co as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@waruiaoshi Pull request merged. Thank you!

@waruiaoshi I am sorry, the pull request appeared to have signs of fraud. The merge will be reverted in a minute. If you are a student of this school, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


KAFKA-3093: Add Connect status tracking API

@ewencp, @Ishiihara: Ping for review. I'm still improving the testing, but I've removed the WIP tag.

@hachikuji One last thing -- we require a new config for distributed mode now (status.storage.topic) and that doesn't exist in the configs for the system tests. I checked some tests (after merging with https://github.com/apache/kafka/pull/949 to fix current brokenness) and the standalone tests seem ok but the distributed ones fail to start up connect because of the missing config. Should be a trivial fix.

@ewencp Sure, no problem. The other thing I wanted to ask about is whether surfacing the exception message in the FAILED case was sufficient, or if we should include any information from the stack trace. What do you think?

@hachikuji Good question. It'd be nice to get stack trace info as well. Often that is enough to diagnose the problem and avoids the user having to dig through logs to pick out the original source of the issue.

@ewencp Ready for another look. I've added code to include the trace of the root cause in the output. Do you think we should just capture the entire stack trace?

@hachikuji What were you thinking this would look like? A list of FailureCauses or something? The full stack trace requires intermediate exception types + messages to make much sense, right?
I agree that as it is now, different types of errors could be difficult to diagnose. Since we only keep the root cause, the source of some exceptions may nor may not be clear (e.g. if a JDBC gets a SQLException that is too generic, it might be difficult to figure out what triggered it). In contrast, only reporting the top-level exception without including any messages from causes may leave things too generic (e.g. ConnectException with a generic message).

Summary of offline discussion: we agreed that it probably makes more sense to include the full formatted stack trace as a string rather than trying to pick out the useful parts. We do not think there are any use cases which could actually take advantage of more structure from this API and UIs would annoyingly have to implement their own stack trace formatting.

@ewencp Updated as discussed. The distributed system tests now pass (after fixing a bug from this patch).

@hachikuji Thanks, I only got as far as figuring out the tests were breaking!
Left some thoughts re: managing these changes long term and avoiding breakage, but LGTM and looks like this addresses the JIRA while keeping system tests passing. Thanks!


Update renv and lockfile

This PR fixes #50 as follows:

Updates renv to v1.0.7
Updates the renv lockfile with R v4.4.0 and new package versions.

I'm not really sure why there's an issue with installing {StanHeaders}, will look into it.

I'm not really sure why there's an issue with installing {StanHeaders}, will look into it.

thank you for setting this up. should we wait for {StanHeaders} to update dependencies to let this PR pass all checks and merge before merging #57 or #60 right? Is it possible to estimate this update to should we re-run the workflow?

Hi @avallecam, this PR is failing checks because one or more of the workflows uses the function epiparameter::epiparam(), which has been removed in more recent version of {epiparameter}. I'll file a separate issue for replacing this usage with epiparameter::epidist_db(). I would also suggest putting the render workflow on a monthly CRON job so that we know of breaking changes in packages under development.

@pratikunterwegs epiparameter::epiparam() was replaced in #63 I needed to update some other packages (R.utils, arm, matrix) in order to pass all checks. Are you able to rebase and solve conflicts in this PR?

I'm pushing changes to this PR after rebasing on main so will wait for checks to run.


[Storage] STG 83

This PR aims to prepare the various files for API View generation. This includes bumping the service versions, filling out the changelogs, and squashing various merge conflicts.

API change check
API changes are not detected in this pull request.

/azp run python - storage - tests

/check-enforcer override


OpenVBX-Directory errors out if nobody answers...

Everything works as expected until the user does not answer the phone...  Then the system says: 'Sorry, an error occurred.'...
I believe that it works correctly if the user picks up in time (or their voicemail picks up in time); however, it doesn't seem to work otherwise...

So sorry this took me this long to fix for you. It should work now.

No problem, I'll hopefully be able to give it a try later this week when
things settle down a little :-)
Thanks,
Nicholas Henry
<EMAIL_ADDRESS>(720) 675-9086
On Sat, Jan 14, 2012 at 7:20 PM, Tim Lytle <
<EMAIL_ADDRESS>
wrote:

So sorry this took me this long to fix for you. It should work now.

Reply to this email directly or view it on GitHub:
https://github.com/tjlytle/OpenVBX-Directory/issues/1#issuecomment-3496604


Drag and Drop with long click and Contextual Action Bar

Is it possible with this library? I'll explain:
I have a list with some items that you can click on it (radio buttons) (so onItemClickListener and all that stuff will not work). When I long click any element inside my list row, I launch a Contextual Action Bar (when item selected).
My idea is to launch a drag action too (like startDraging(position). Something like:
    holder.radioButton.setOnLongClickListener(new View.OnLongClickListener() {
        @Override
        public boolean onLongClick(View view) {

            if (!isCAB()) { //No Contextual Action Bar
               getListView().setItemChecked(position, true); //Launch ActionMode
               getListView().startDrag(position); //HERE (launch drag too)
            }else {
                selectCABitem(checkedItems, position);
            }
            return true;
        }
    });

What I would do then is have a drag listener, if we drag an item to another position (even if we don't drop it yet), the contextual action bar will disappear, on the other hand, if we drop the element in the same position, then the CAB stays and you can continue selecting items. This is the default behaviour of Google Keep for example.
I think what is really needed is the ability to say "startDrag(position)" and having that listener... I was not really lucky for now with that libraries out there.
Looking at this library, the only way for launching a drag action is to give a id handler (like imageview)?
Thanks for your time!

Hi,
OK I think I know what you want, a way to progmatically start the drag operation?
This should be possible, but won't you need to take your finger off the list item before the drag has finished?
What is the overall functionally you're trying to achieve? Long press on the item then...
Thanks


is-it-possible-to-add-border-image-of-first-arc-rotation-of-doughnut-with-angula

I have created a doughnut in with chart js in angular4. Here i have to add starting point and ending point in the first rotation of doughnut chart arc. In the image you have seen start and end point image, can we able to achieve it in chart js library with angular 4. kindly update it in below plunker ,better solution or suggestion be appreciated.
Arc configuartion in the doc:

o/p

More details : https://stackoverflow.com/questions/47607604/is-it-possible-to-add-border-image-of-first-arc-rotation-of-doughnut-with-angula
Plunker: https://plnkr.co/edit/vHlmFY8ahSYXqvnwb5I3?p=preview if its possible update it here.

possible.
but, you shouldn't be posting questions/requirements here. this section is only for 'issues' that you're currently having with the library itself.

@pundoo  in any where of the doc, shows border-image related docs, so i have thought to ask a question here and i dont have idea to extend the plugin for add border images. Ok thanks  for answer..

@MohamedSahir this is definitely possible, but you would need to write either a new arc implementation or a plugin that hooks into the chart to draw afterwards.
In general you'll get a better answer to these kinds of questions on StackOverflow.


Fix for updating colors from Fonts & Colors

Some how I missed this pull request. Thanks for this. I've sinced released a beta 2 version. Check it out.


Plugin.BLE.Abstractions.Exceptions.CharacteristicReadException: Gatt write characteristic FAILED.

I'm working on an app and I need to develop a feature whose goal is to CANCEL an ongoing operation.
But every time I write a new command and send it to the device, I get 'Gatt write characteristic FAILED'.
Is it possible to cancel an ongoing operation?

Hi @gadsaldanha,
I'm the friendly issue checker.
It seems like (100.00 %) you haven't used our issue template :cry: I think it is very frustrating for the repository owners, if you ignore them.
If you think it's fine to make an exception, just ignore this message.
But if you think it was a mistake to delete the template, please close the issue and create a new one.
Thanks!

But every time I write a new command and send it to the device, I get 'Gatt write characteristic FAILED'.

You're not giving us much information to work with, but this error message tells me you're working on Android.

Is it possible to cancel an ongoing operation?

In principle yes. Most methods of ICharacteristic have a cancellationToken argument. This was even extended further recently, see #549. Is this sufficient for you, or do you need something else?


fix: stale time with huge value

In Javascript, setTimeout has a limit. If the ms exceeds that, the setTimeout callback will be executed after 1 ms.
This is not an expected behavior. For example, I would like to pass in Infinity to have that value stale for a very long time. Currently, passing Infinity will have no effect.
ref: https://stackoverflow.com/questions/3468607/why-does-settimeout-break-for-large-millisecond-delay-values
Fixed #26

TIL. Thanks! Released as 1.0.9


Add C API for GuestProfiler

Sorry for the noise with #7853, I messed up with Git.

I think I addressed everything for now.


Tristan170117

Step 1: Describe your environment

Android device: _____
Android OS version: _____
Google Play Services version: _____
Firebase/Play Services SDK version: _____

Step 2: Describe the problem:
Steps to reproduce:

Observed Results:

What happened?  This could be a description, logcat output, etc.

Expected Results:

What did you expect to happen?

Relevant Code:
// TODO(you): code here to reproduce the problem

@Noel97martin Please fill the issue template if you're having an issue.


NoMethodError (undefined method `sign' for #<String:

my code here
        tx = Eth::Tx.new({
                gas_limit: 200000,
                gas_price: 1,
                nonce: 1,
                to: address_to,
                value: amount,
                data: ''
            })

        tx.sign(privateKey_hex)

trace log
           "Framework Trace": [
            {
                "id": 0,
                "trace": "eth (0.4.6) lib/eth/tx.rb:56:in `sign'"
            },

i've resolved with code additional
        key = Eth::Key.new priv: privateKey_hex
        tx.sign(key)


Support JNI

[Enhancement]
Problem
cmake -DWITH_JNI=ON
Solution
fix some compile problem in JNI mode


configMap for default.d directory

Plugin version used: v2.0.0
On the latest release, only two configMaps are allowed, for defining default.local file, and config.d directory files.
I'm trying to setup the plugin with the need of using the parameter CVMFS_CONFIG_REPOSITORY.
I tried to define it on the default.local file, but running cvmfs_config chksetup, I'm facing this error:
Error: CVMFS_CONFIG_REPOSITORY can only be set in /etc/cvmfs/default.conf and /etc/cvmfs/default.d/*.conf (not in /etc/cvmfs/default.local)
In previous versions, there is a configMap to define files inside the default.d directory.

Why is it the default.d configMap deprecated?
Is there an alternative or workaround to define the parameter CVMFS_CONFIG_REPOSITORY using the default.local and config.d configMaps?
Can be added again a configMap to map the file inside the default.d directory?

Hi @gman0, thanks for your reply and your work.
I'm currently mapping the configuration using configMaps and I find this mechanism enough simple and intuitive to "store" the proper configuration on the values.yml file, having also the capacity to track it easily on a control version such as Git/GH/GL, etc, and using it "transparently" on integrations without involving "existent" files on storage support to mount it later.
About the proposal on issue #54,  If I can decide, I would probably choose to stay on configMaps but adding some others like /etc/cvmfs/defaul.d/*, for example. Anyway, I'm conscient that keeping this mechanism requires additional work on the code to add extra configMaps if required, modifying different files.
If you are considering the volume mount approach because is more flexible, please, go ahead, you probably have a better understanding of what is better to improve the usability of the plugin, the only point that I consider that is mandatory if you decide to change to this approach, is to have a good section docu/guide explaining on how to use it properly.
Thanks again for your work, if I can help you with whatever you consider, please don't hesitate on mentioning me.
Regards!

Hi @jtorrex, you can check https://github.com/cvmfs-contrib/cvmfs-csi/pull/56 if that would work for you. Thanks!

Checked #56. For my particular use case, I think that we can close this issue as the new patch provides a better flexible way for mapping the desired configuration. Thanks for your work again @gman0.


As developers we want to make load- and stress-tests

It is important for the developers to know the limits of their website. Therefore the website should have load- and stress-tests, which would give an overview of the websites capabilities.
** CRITERIA OF ACCEPTANCE **

The project include a load test
The project include a stress test

Won't be addressing this issue


Adding docs tag to README.md

Adding ReadTheDocs badge to README.md

Trivial change self-approving


Change Wercker badge to check only master branch

This badge looks to all PR. Its too much:

We can change to only check master branch:

Pull request #274


.NET 7 support

Is there a way to run this from a project that is not .NET Framework? I'm currently getting the following exception when trying to get an instance from the WrapperProxyFactory:
System.TypeLoadException: Could not load type 'System.Runtime.Remoting.RemotingServices' from assembly 'mscorlib, Version=<IP_ADDRESS>

Unfortunately not. Feel free to submit a pull request, though!


Add CI

Short term goal

Run tests with the virtual TEE environment.

Long term goal

Run tests with actual SGX or SEV-SNP

Tool
GitHub Actions should be enough.

CI with virtual TEE was addressed in #19

@takuro-sato - do you think we should close this one as we have CI in a virtual and CD in a SGX?

Agree. Thank you for pointing it out


New tool to add, KitOps

Check out KitOps, we just launched it to help ease model handoffs between data scientists and app devs or devops folk.
https://github.com/jozu-ai/kitops

Created a PR for this to make it easier: https://github.com/aporia-ai/mlops.toys/pull/109

@SnirShechter any thoughts on this issue and #109

Hey, I no longer work at Aporia so I don't have write access to this repo any more.
Tagging the VP R&D and chief architect, They'll be able to merge this.
@yanivzoh @yonbek


Feat/extend unicode ranges

Coverage increased (+0.01%) to 99.66% when pulling 4bf617810884dd4ca45ce39692c06fc3879c4900 on feat/extend-unicode-ranges into 7a4d6a815565e22db2b6f5321f926e38c17e962b on master.


ARROW-2657: [C++] Undo export pthread_once related symbols.

This seems to fix https://issues.apache.org/jira/browse/ARROW-2657, but I don't fully understand this code so it may introduce other issues.
This code was introduced in #1953.
cc @wesm @pitrou

I don't fully understand this code so it may introduce other issues.

As you can see on Travis-CI (look at the manylinux1 build).

If, as @wesm suggests, "TensorFlow is not respecting the manylinux1 standard and is using newer compilers", I'm not sure how we can reconcile TensorFlow and Arrow :-/

The original problem is that libarrow.so and libplasma.so both link with libstdc++ and, when the RH devtoolset is used (i.e. when building wheels), some parts of the libstdc++ are linked statically (the parts that aren't available at runtime with an old libstdc++). Then, when loading libplasma.so which also loads libarrow.so, those static symbols end up instantiated twice in the process (because they are made library-local by the visibility script).
The fix for that was to ensure that those symbols stay process-global, so they that all resolve to a single location.

This is a bit of a mess -- I'm reading through the original comments to understand what's happening better. Would this not be a problem in any setting where devtoolset was used to build multiple .so files?

Where is the call_once call happening? I searched in the codebase and didn't find that anywhere

call_once is apparently used under the hood for lazily-initialized static singletons (i.e. when a static object is defined inside a function).

Would this not be a problem in any setting where devtoolset was used to build multiple .so files?

I think it's ok as long as you don't try to hide the "once" symbols using a visibility script.

@xhochy is there a problem if we allow these pthread symbols to be visible in the .so? We might have to set up some kind of exclusions file for the visibility check script

We actually hide these symbols to be compatible with other libs. In this case it sadly produces the opposite, so it's fine to exclude them.

@xhochy, where does check_arrow_visibility.sh live?

That's the one, let me know if you need help. I think that may need to be turned into a Python script that can read from an exclusions file

Is -pthread being passed when linking libplasma?
This gcc thread suggests that may fix the problem https://gcc.gnu.org/bugzilla/show_bug.cgi?id=58104. Try adding ${PTHREAD_LIBRARY} to https://github.com/apache/arrow/blob/master/cpp/src/plasma/CMakeLists.txt#L66?

Although I'm not sure why that particular test would fail =( I can try to tinker with this tomorrow possibly, I don't know where to turn for help

Another thing we could try is to not use the global thread pool in Plasma, in case there is some issue with using the global thread pool in libarrow in libplasma (and we can resolve the shared-library-crossing issue at some later time)

We could also try replacing the global thread pool initialization with an explicit use of std::call_once in case the issue relates to something having to do with gcc-4.8's implementation of threadsafe static initialization

I also think we should get the TensorFlow team involved in this. They bear some responsibility for their choice of a non-conforming compiler toolchain when building their wheels

Rebased. Taking a look at this; I am curious if replacing the atomic initialization of the threadpool with a mutex will make the problem go away

Looks like PyTorch and TensorFlow trampled each other over this issue also https://github.com/pytorch/pytorch/issues/3059#issuecomment-335668027. Digging some more into this

Been banging my head against this for a few hours now. I've been looking at PyTorch's equivalent symbols.map file
https://github.com/pytorch/pytorch/blob/master/tools/pytorch.version
I tried to make it look more like theirs:
{
    global:
        extern "C++" {
          *arrow::*;
        };

    local:
        *;
  };

But then this causes errors like
$ python -c "import pyarrow"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/wesm/code/arrow/python/pyarrow/__init__.py", line 47, in <module>
    from pyarrow.lib import cpu_count, set_cpu_count
ImportError: /home/wesm/local/lib/libarrow.so.10: undefined symbol: _ZNK6google8protobuf7Message11GetTypeNameEv

Intuitively, all of the symbols except for the arrow:: symbols (and other C++-related symbols like typeinfo, etc.) should be hidden. I'm going to have to take a break from this for a day or two before I'll be able to work on it again as it's too frustrating

@wesm thanks for looking into this. I'm out of ideas at the moment about the "right" way to solve this. If we can't figure something out then it will likely be possible to workaround by not using the global thread pool in plasma.

After looking at this, I'm not sure that will help; we would have to find some other way to have a global thread pool without having a static global in libarrow.so. We should try to better understand the conflict with TensorFlow -- the fact that PyTorch was able to solve the problem by hiding the symbol is promising.
I'm concerned that devtoolset-2 (which is based on gcc 4.8.x) is on the very edge of C++11 support and so there may be something idiosyncratic that's going wrong. I wonder how much trouble we'd be getting ourselves into if we built our wheels with devtoolset-3 (gcc 4.9.x-based)

Do we already have other static singletons in Arrow?
I suppose it could be possible to use our own mutex-backed implementation if that helps (I don't think the GetCpuThreadPool performance is that critical - if you're planning to offload tasks to a thread pool, you're obviously ok with enduring the cost of thread synchronization). But I'm curious why TensorFlow is using a different toolchain - obviously that should conflict with the manylinux1 requirements?

I tried using mutexes to sychronize -- the issue is having any global variable that is a C++ object it seems -- this causes the compiler to emit the std::once_call instructions resulting in the pthread symbols being statically linked. I don't yet understand why these symbols are a conflict. From the PyTorch solution, it seems that getting our symbol exports right should solve the problem

Answering to myself: yes, we already have static singletons in the Arrow codebase. For example in the type factories in type.cc.

You're right; I'm pretty mystified why this problem only started coming up now
TensorFlow needs a newer version of clang for all the LLVM-stuff they are using I guess

I tried using mutexes to sychronize

Which idiom did you try exactly?
I'm thinking something like:

static std::mutex cputhreadpool_mutex;
static CPUThreadPool* cputhreadpool = nullptr;

GetCPUThreadPool() {
  lock_guard lock(cputhreadpool_mutex);
  if (cputhreadpool == nullptr) {
    cputhreadpool = ...;
  }
  return cputhreadpool;
}

By putting all static variables outside of the function we would ideally remove the call_once usage.

That's what I tried. I suspect the call_once symbols are getting pulled in from something else (maybe from the condition_variable use?) -- we may be looking at a red herring.

Disassembling the libarrow.so that's part of the generated wheel would probably tell us where call_once is used exactly.

I was just looking at https://google.github.io/styleguide/cppguide.html#Static_and_Global_Variables. I will have another go at trying to fix this, but I think we might consider following Google's advice and not having any static globals with non-trivial destructors (i.e. shared_ptr has a non-trivial dtor). I suspect that's what caused these symbols to bubble up in the first place

Thanks @wesm! Let us know what you find. I think following that style guide point makes a lot of sense.

The main problem with that is that it would probably require explicit initialization of the thread pool, and applications would need to shut down the thread pool explicitly to avoid valgrind warnings. Will let you know what I find

Codecov Report

Merging #2096 into master will increase coverage by 0.04%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2096      +/-   ##
==========================================
+ Coverage   86.47%   86.52%   +0.04%
==========================================
  Files         244      244
  Lines       41808    41892      +84
==========================================
+ Hits        36155    36246      +91
+ Misses       5653     5646       -7

Impacted Files
Coverage Δ

cpp/src/arrow/python/helpers.cc
79.87% <0%> (-3.23%)
:arrow_down:

python/pyarrow/parquet.py
90.46% <0%> (-0.08%)
:arrow_down:

cpp/src/arrow/python/common.h
100% <0%> (ø)
:arrow_up:

cpp/src/arrow/python/python_to_arrow.cc
88.29% <0%> (+0.12%)
:arrow_up:

cpp/src/arrow/python/arrow_to_python.cc
91.71% <0%> (+0.2%)
:arrow_up:

cpp/src/arrow/python/builtin_convert.cc
92.1% <0%> (+0.47%)
:arrow_up:

cpp/src/arrow/util/thread-pool-test.cc
99.45% <0%> (+0.54%)
:arrow_up:

cpp/src/arrow/python/helpers.h
90% <0%> (+1.11%)
:arrow_up:

python/pyarrow/tests/test_parquet.py
96.96% <0%> (+1.4%)
:arrow_up:

Continue to review full report at Codecov.

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

I'm getting closer on this. So I'm able to load the various libraries and then load tensorflow:
$ python
Python 3.6.5 | packaged by conda-forge | (default, Apr  6 2018, 13:39:56)
[GCC 4.8.2 20140120 (Red Hat 4.8.2-15)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import ctypes
>>> ctypes.CDLL('/home/wesm/miniconda/envs/wheel-test-2/lib/python3.6/site-packages/pyarrow/libarrow.so')
<CDLL '/home/wesm/miniconda/envs/wheel-test-2/lib/python3.6/site-packages/pyarrow/libarrow.so', handle 1948b50 at 0x7fa407a9ff98>
>>> ctypes.CDLL('/home/wesm/miniconda/envs/wheel-test-2/lib/python3.6/site-packages/pyarrow/libarrow_python.so')
<CDLL '/home/wesm/miniconda/envs/wheel-test-2/lib/python3.6/site-packages/pyarrow/libarrow_python.so', handle 196a9a0 at 0x7fa407a9ffd0>
>>> ctypes.CDLL('/home/wesm/miniconda/envs/wheel-test-2/lib/python3.6/site-packages/pyarrow/libarrow_boost_regex.so.1.65.1')
<CDLL '/home/wesm/miniconda/envs/wheel-test-2/lib/python3.6/site-packages/pyarrow/libarrow_boost_regex.so.1.65.1', handle 196c8d0 at 0x7fa407a9ff98>
>>> ctypes.CDLL('/home/wesm/miniconda/envs/wheel-test-2/lib/python3.6/site-packages/pyarrow/libarrow_boost_filesystem.so.1.65.1')
<CDLL '/home/wesm/miniconda/envs/wheel-test-2/lib/python3.6/site-packages/pyarrow/libarrow_boost_filesystem.so.1.65.1', handle 19526b0 at 0x7fa407a9ffd0>
>>> ctypes.CDLL('/home/wesm/miniconda/envs/wheel-test-2/lib/python3.6/site-packages/pyarrow/libarrow_boost_system.so')
<CDLL '/home/wesm/miniconda/envs/wheel-test-2/lib/python3.6/site-packages/pyarrow/libarrow_boost_system.so', handle 196d070 at 0x7fa407a9ff98>
>>> ctypes.CDLL('/home/wesm/miniconda/envs/wheel-test-2/lib/python3.6/site-packages/pyarrow/libparquet.so')
<CDLL '/home/wesm/miniconda/envs/wheel-test-2/lib/python3.6/site-packages/pyarrow/libparquet.so', handle 196d920 at 0x7fa407a9ffd0>
>>> import tensorflow

But
$ python
Python 3.6.5 | packaged by conda-forge | (default, Apr  6 2018, 13:39:56)
[GCC 4.8.2 20140120 (Red Hat 4.8.2-15)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import pyarrow
>>> import tensorflow
Segmentation fault (core dumped)

You can see from gdb that importing pyarrow fires up the thread pool:
>>> import pyarrow
im[New Thread 0x7fffecc4d700 (LWP 7962)]
[New Thread 0x7fffec44c700 (LWP 7963)]
[New Thread 0x7fffe7c4b700 (LWP 7964)]
[New Thread 0x7fffe544a700 (LWP 7965)]
[New Thread 0x7fffe2c49700 (LWP 7966)]
[New Thread 0x7fffe0448700 (LWP 7967)]
[New Thread 0x7fffddc47700 (LWP 7968)]
p>>> import tensorflow

Thread 1 "python" received signal SIGSEGV, Segmentation fault.
0x0000000000000000 in ?? ()
(gdb)

So seemingly things are okay until  the pthread_once machinery to initialize the thread pool is triggered.
I'm a bit at a loss here on this, folks. I've spent about 4 hours now working on this and I don't know enough about what's going on inside to solve this.
One solution we can try is to get rid of the global thread pool, and instead explicitly pass a thread pool into functions where one is supported. This means we could set up a thread pool that we can use for the lifetime of a pyarrow session and manage things in the Python bindings. This will definitely get rid of the issue.
Another option is that we figure out where the thread pool is being initialized at import time and fix that so all of the imports, including tensorflow, can succeed. The downside is that if the user imports pyarrow, does something that uses threads, then later imports tensorflow, they will segfault.

FWIW, I'm +1 on offering more public thread control on functions that support it. In some applications you could imagine having separate thread pools for IO and computation

Getting rid of the global thread pool may be the simplest option.
Unfortunately I think "importing pyarrow, doing something that uses threads, then later importing tensorflow" will be pretty common.

Can someone try the workaround I mentioned in https://github.com/apache/arrow/pull/2198#issuecomment-401632426 ?

By the way, I'm a bit surprised that import pyarrow would initialize the global thread pool. Do we know on which code path that happens?

@pitrou I will try the work around and also try to figure out where the thread pool is getting initialized. After thinking about this overnight, I think we should manage the global thread pool on the Python side. Then we are not relying on non-trivial global variables in the shared library

The global thread pool is intended for C++ use as well. The prior situation was that we could launch local thread pools in several places (e.g. Plasma or memcpy) without regard for machine occupancy.

Right, I understand that. What I'm proposing is to expose ThreadPool* as a parameter instead of a flag bool use_threads anywhere where we have the global pool now. So the application can decide whether or not to use threads

I agree that this does expose some complexity to the developer-user; I see both sides of the argument, but I think it may be a good thing to offer more control/flexibility in the API in this way

I don't know, I would tend to wait for user requests to come up :-)

OK, so I found out the mystery of the threads being spawned. They're being spawned by openblas when NumPy imports:
(gdb) break pthread_create
Function "pthread_create" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (pthread_create) pending.
(gdb) r
...
>>> import pyarrow
#0  __pthread_create_2_1 (newthread=0x7fffeedcd280 <blas_threads>, attr=0x0,
    start_routine=0x7fffecbc08e0 <blas_thread_server>, arg=0x0) at pthread_create.c:610
#1  0x00007fffecbc0c08 in blas_thread_init ()
   from /home/wesm/miniconda/envs/wheel-test-3/lib/python3.6/site-packages/numpy/core/../.libs/libopenblasp-r0-39a31c03.2.18.so
#2  0x00007fffec9a0085 in gotoblas_init ()
   from /home/wesm/miniconda/envs/wheel-test-3/lib/python3.6/site-packages/numpy/core/../.libs/libopenblasp-r0-39a31c03.2.18.so
#3  0x00007ffff7de5733 in call_init (env=0x962b20, argv=0x7fffffffc4b8, argc=1, l=<optimized out>) at dl-init.c:72
#4  _dl_init (main_map=main_map@entry=0x963080, argc=1, argv=0x7fffffffc4b8, env=0x962b20) at dl-init.c:119
#5  0x00007ffff7dea1ff in dl_open_worker (a=a@entry=0x7fffffff1310) at dl-open.c:522
#6  0x00007ffff6a422df in __GI__dl_catch_exception (exception=0x7fffffff12f0,
    operate=0x7ffff7de9dc0 <dl_open_worker>, args=0x7fffffff1310) at dl-error-skeleton.c:196
#7  0x00007ffff7de97ca in _dl_open (
    file=0x7fffef759b90 "/home/wesm/miniconda/envs/wheel-test-3/lib/python3.6/site-packages/numpy/core/multiarray.cpython-36m-x86_64-linux-gnu.so", mode=-2147483646, caller_dlopen=0x7ffff7a51161 <_PyImport_FindSharedFuncptr+417>,
    nsid=<optimized out>, argc=1, argv=<optimized out>, env=0x962b20) at dl-open.c:605
#8  0x00007ffff7475f96 in dlopen_doit (a=a@entry=0x7fffffff1540) at dlopen.c:66
#9  0x00007ffff6a422df in __GI__dl_catch_exception (exception=exception@entry=0x7fffffff14e0,
    operate=0x7ffff7475f40 <dlopen_doit>, args=0x7fffffff1540) at dl-error-skeleton.c:196
#10 0x00007ffff6a4236f in __GI__dl_catch_error (objname=0x69a350, errstring=0x69a358, mallocedp=0x69a348,
    operate=<optimized out>, args=<optimized out>) at dl-error-skeleton.c:215
#11 0x00007ffff7476735 in _dlerror_run (operate=operate@entry=0x7ffff7475f40 <dlopen_doit>,
    args=args@entry=0x7fffffff1540) at dlerror.c:162
#12 0x00007ffff7476051 in __dlopen (
<SNIP>

@pitrou I tried your workaround and it didn't work unfortunately. I'm going to take a crack at adding options to pass in a thread pool in the various places where we use it so we can unblock ourselves on this; not sure what else to do

Changing our API just so that TensorFlow's non-compliant wheels don't crash sounds a bit over the board to me. I'd rather redirect user complaints to the TensorFlow project. We shouldn't feel responsible for this issue.

Thanks @wesm! @pitrou I agree it'd be best to fix the issue on the TF side, but that's most likely a long-termer item. Not supporting TF at this point would be like being incompatible with numpy or pandas.

Here's the backtrace
#0  0x0000000000000000 in ?? ()
#1  0x00007ffff7688827 in __pthread_once_slow (
    once_control=0x7fffd4cd51c8 <tensorflow::port::(anonymous namespace)::cpuid_once_flag>,
    init_routine=0x7ffff088bfe1 <std::__once_proxy()>) at pthread_once.c:116
#2  0x00007fffd4575faa in void std::call_once<void (&)()>(std::once_flag&, void (&)()) ()
   from /home/wesm/miniconda/envs/wheel-test-3/lib/python3.6/site-packages/tensorflow/python/../libtensorflow_framework.so
#3  0x00007fffd4575fde in tensorflow::port::TestCPUFeature(tensorflow::port::CPUFeature) ()
   from /home/wesm/miniconda/envs/wheel-test-3/lib/python3.6/site-packages/tensorflow/python/../libtensorflow_framework.so
#4  0x00007fffd4575f11 in tensorflow::port::(anonymous namespace)::CheckFeatureOrDie(tensorflow::port::CPUFeature, std::string const&) ()
   from /home/wesm/miniconda/envs/wheel-test-3/lib/python3.6/site-packages/tensorflow/python/../libtensorflow_framework.so
#5  0x00007fffd43b7394 in _GLOBAL__sub_I_cpu_feature_guard.cc ()
   from /home/wesm/miniconda/envs/wheel-test-3/lib/python3.6/site-packages/tensorflow/python/../libtensorflow_framework.so
#6  0x00007ffff7de5733 in call_init (env=0x944d20, argv=0x7fffffffc4a8, argc=1, l=<optimized out>) at dl-init.c:72
#7  _dl_init (main_map=main_map@entry=0xc29300, argc=1, argv=0x7fffffffc4a8, env=0x944d20) at dl-init.c:119
#8  0x00007ffff7dea1ff in dl_open_worker (a=a@entry=0x7fffffff57b0) at dl-open.c:522
#9  0x00007ffff6a422df in __GI__dl_catch_exception (exception=0x7fffffff5790,
    operate=0x7ffff7de9dc0 <dl_open_worker>, args=0x7fffffff57b0) at dl-error-skeleton.c:196
#10 0x00007ffff7de97ca in _dl_open (
    file=0x7fffd9bcf640 "/home/wesm/miniconda/envs/wheel-test-3/lib/python3.6/site-packages/tensorflow/python/_pywrap_tensorflow_internal.so", mode=-2147483646, caller_dlopen=0x7ffff7a51161 <_PyImport_FindSharedFuncptr+417>,
    nsid=<optimized out>, argc=1, argv=<optimized out>, env=0x944d20) at dl-open.c:605

I'm pushing the branch as it stands now. I'll try a few more things

I agree that fixing this in some way is extremely important. I can investigate the solution to try to import tensorflow before pyarrow if it is available. Any thoughts?

This is the cheapest thing I can think of:
$ python
Python 3.6.5 | packaged by conda-forge | (default, Apr  6 2018, 13:39:56)
[GCC 4.8.2 20140120 (Red Hat 4.8.2-15)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import ctypes
>>> import tensorflow
>>> tensorflow
<module 'tensorflow' from '/home/wesm/miniconda/envs/wheel-test-3/lib/python3.6/site-packages/tensorflow/__init__.py'>
>>> ctypes.CDLL('/home/wesm/miniconda/envs/wheel-test-3/lib/python3.6/site-packages/tensorflow/libtensorflow_framework.so')
<CDLL '/home/wesm/miniconda/envs/wheel-test-3/lib/python3.6/site-packages/tensorflow/libtensorflow_framework.so', handle 23d7f40 at 0x7f3834cc6080>
>>> import pyarrow
>>> import tensorflow
WORKS

Loading the tensorflow shared library is fast, whereas import tensorflow takes about as long as importing numpy

Yep, that's the way to do it. Let me see if I can get the path without importing tensorflow ;)

Probably have to look in site-packages
>>> import site
>>> site.getsitepackages()
['/home/wesm/miniconda/envs/wheel-test-3/lib/python3.6/site-packages']

suffice to say this workaround should only be needed on Linux

OK @pcmoritz I will leave this branch to you.
@pitrou I changed the various ThreadPool variable to use unique_ptr instead of shared_ptr; I can change it back, but I wonder if you feel strongly about one vs. the other?

Roger, reverted

Closing because hopefully this is worked around by #2210.


Use __construct instead of class name for constructor

Future versions of PHP will not allow use of class name as constructor.

#59 looks like the most complete PR for this request

can be closed due to the merging of #59


Need to increase the timeout for TypingAnimation

Feature request
I need to increase the timeout of the typing animation shown by the bot. Currently, the bot typing animation disappears after 2 sec or so. I need to increase to 6 sec. I tried following the approach of setting SendTimeout explicitly but it doesn't seem to work.
window.WebChat.renderWebChat({
directLine: window.WebChat.createDirectLine({
token: params['s'],
userID: params['username'],
user: {id: params['userid']},
}),
store, username: params['username'],
userID: params['userid'], sendTimeout: 60000,
styleSet,
sendTypingIndicator: true,
},
document.getElementById("webchat")
);
Any idea of how can I Increase the timeout for typing Animation.

Hi @mathurvarun84, the typing indicator is not currently customizable. After speaking with the team, we are interested in enabling users to modify the duration. This has been added to our backlog. Thank you!

Hi!
We need this feature too.
Thanks for your work on it.

Hi,
This would be very nice feature to have. Looking forward to it.

Hi
i changed this value (3e3) => (6e5)
search this  text :  ofType("Show_Typing").delay(3e3)
in this file
https://cdn.botframework.com/botframework-webchat/latest/botchat-es5.js
works for me

How to fix
Implementation

Today, we use saga to control how long to show typing

"How long" is a question on UI, not back end. Thus, the better design is to move it away from saga

Tomorrow

Use debounce in UI to control how long to show typing
Move typing indicator into send box

This will greatly reduce code complexity

Add typingIndicatorTimeout to styleOptions

Tests

Basic test

Default value
Non-default value
New activity from bot come in and it should immediately remove typing indicator

Corner cases

After the typing indicator "faded away", setting styleOptions.typingIndicatorTimeout to a bigger value should bring it back

https://github.com/microsoft/BotFramework-WebChat/pull/2321 Added a typingAnimationDuration option to the default style options - default is 5000 milliseconds.


Date/TIme is not acurrate on file save

If you modify a file ( spreas, document, etc ) the file is saved correctly in nextcloud, but ther time/date are not updated.
If you use desktop client do no receive update for this file, time/date is not changed.
Regards
Cayetano

The application uses the official method of saving the file putContent. Inside the method, the data is updated, including time/date.
In the list of files, the time is updated only after the page reloads. Is the file being saved after editing? If the file is downloaded, will it contain changes?

I'm make some test.

make modification... download immediately the file... changes are not in
the file
make modification... reload page download immediately the file...
changes are not in the file
make modification .. wait 10 minutes... reload page, the files are
changes in.

Any ideas ?
Regards
Cayetano
2017-06-06 15:21 GMT+02:00 Sergey Linnik<EMAIL_ADDRESS>
The application uses
https://github.com/ONLYOFFICE/onlyoffice-owncloud/blob/master/controller/callbackcontroller.php#L319
the official
https://doc.owncloud.org/api/classes/OCP.Files.File.html#method_putContent
method of saving the file putContent. Inside the method, the data is
updated, including time/date.
In the list of files, the time is updated only after the page reloads. Is
the file being saved after editing? If the file is downloaded, will it
contain changes?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ONLYOFFICE/onlyoffice-owncloud/issues/73#issuecomment-306484004,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAz_pNIsZdsb-7mZhE3qT6iGBlgeBPA9ks5sBVJJgaJpZM4NmRJ2
.

Hello @cayetano
This is a peculiarity of working NextCloud with OnlyOffice - time of last editing updates only after page refreshing. But the fact that changes appear only after 10 minutes since the last editing is strange.
You may follow this instruction to set logs level to 0. Then post logs here or send at<EMAIL_ADDRESS>

Could you please specify if the problem recurs or we can close the topic.

The current behavior is:

Edit with "OnlyOffice"
Date / Time is not updated on the web until you refresh manually. Even if you go out and enter the folder. It is probably an effect of memcached.
File system level is not updated until after about 30 seconds you have left the editor.
The synchronization client detects in the next iteration.

I think the incidence can be solved.
Thank you very much. This tool has become essential to my daily work.
regards
Cayetano

Is there a change in the file from the editors, if you download it from nextcloud?


Applying extension via migrations not working for 0.3.1

The statements introduced in 0.3.1 prevent the extension to be automatically added via migrations.
With 0.3.0 I could just create a migration file and add the extensions that way, now with0.3.1 it fails with the error:
Error: ERROR: pg_extension_config_dump() can only be called from an SQL script executed by CREATE EXTENSION (SQLSTATE 0A000)
At statement 4: select
    pg_catalog.pg_extension_config_dump ('audit.record_version_id_seq','')
Try rerunning the command with --debug to troubleshoot the error.

I checked the pg docs but couldn't really make sense of it. Any idea if there is a way to make this work?

if you're attempting to install by copy/pasting the SQL, you can omit any function calls to
pg_catalog.pg_extension_*

as they're not applicable


how to use api

hello there, I want to know how to use the available zenzapi, is there any guide how to use?

do u use termux or heroku?
if u use termux, u should register to zenzapi first and then u got the apikey. Copy the apikey. Then open your termux, type pkg install mc. and then cd Killua-Zoldyck and then type mc. The output should be file of the bot. search for 'config.json', and press edit button. It should be open the config.json file. Then edit the "apikey" in
"APIs": {
"zenz": "https://zenzapis.xyz",
"apikey": "YOURAPIKEY"
just delete the 'YOURAPIKEY' and paste your apikey

do u use termux or heroku? if u use termux, u should register to zenzapi first and then u got the apikey. Copy the apikey. Then open your termux, type pkg install mc. and then cd Killua-Zoldyck and then type mc. The output should be file of the bot. search for 'config.json', and press edit button. It should be open the config.json file. Then edit the "apikey" in "APIs": { "zenz": "https://zenzapis.xyz", "apikey": "YOURAPIKEY" just delete the 'YOURAPIKEY' and paste your apikey

ahh, alright. Thanks for the info!!


will it work for unbalanced data for classifier?

will it work for unbalanced data for classifier?
for one hot data: only 0s and 1s in data
is it possible to set class weights like
https://scikit-learn.org/stable/modules/generated/sklearn.linear_model.LogisticRegression.html
class_weight dict or ‘balanced’, default=None
Weights associated with classes in the form {class_label: weight}. If not given, all classes are supposed to have weight one

It depends on how unbalanced the data is but it should work.
Currently we don't have class_weight implemented but it is definitely something that we will look into adding in the next versions of the model.


added micrometer prometheus registry

@brian-brazil can you please merge this PR? Thanks!

Thanks for your PR. We only list one client library per language/runtime, and there's already a Java client which follows our best practices.

Micrometer is the default metrics library for all Spring Boot projects, I would suggest it makes sense to mention it in the documentation.
Furthermore there are currently already 3 JVM libs listed...?

Those are collectors, not client libraries.

I quite the introduction to that section:

They are not Prometheus client libraries themselves but make use of
one of the normal Prometheus client libraries under the hood.

That is exactly what Micrometer is. A generic metrics library for the JVM that collects data and offers a Prometheus endpoint.
Please instruct me if you want me to change the wording in my change or proceed and close the PR.
Thanks for considering it.

If it goes anywhere, it'd be in the section above.

it'd be in the section above.

You're referring to "Software exposing Prometheus metrics"? That's where I as a reader would certainly not expect it.
Micrometer is a library, not a software.
You could argue that Spring Boot could be mentioned in that section as it can export Prometheus metrics using Micrometer. But Micrometer is also an independent library that has nothing to do with Spring. I've just migrated a large enterprise application to export Prometheus metrics using Micrometer and we're not using Spring.
Again, thanks for maintaining this documentation. I find it very helpful and would like to contribute where I see a need. But you'll need to give me clearer advice.

You're referring to "Software exposing Prometheus metrics"?

Yes.

If Micrometer belongs in the Software exposing Prometheus metrics, doesn't that imply that go-metrics belongs in the Software exposing Prometheus metrics section as well?
Micrometer and go-metrics perform the same function, they are libraries that you can use to instrument your code and export metrics to different metrics backends.

I think this makes sense where it is, it's in the same class as go-metrics.


pythran in Debian

Currently pythran does not seem to be packaged for Debian. Would you mind me trying to package it for Debian?

I 100% don't mind! I used to maintain a private debian repo but lack time, so go ahead :-)
I'd be curious of the package rules, do no hesitate to share them!

Neither am I. But it is still a hard dependency and there is no short
term workaround...

So my guess is that you should probably bundle boost.simd within pythran
and not as an external dependency?

standard boost would do for all but boost/simd, right?
yes
It's going to be hard to get something into Debian if it's already abandoned by upstream
agreed. I could remove that dependency and use xsimd instead from @quantstack, but that would delay the packaging 'tll the end of year.

My boost.simd version is patched, why cannot you consider it as an implementation detail of pythran?

My boost.simd version is patched, why cannot you consider it as an implementation detail of pythran?

I don't think Debian is going to accept this. From https://wiki.debian.org/UpstreamGuide#No_inclusion_of_third_party_code

Please do not include other code (like libraries) or data that are also shipped separately inside your source archive, or if you do, please make sure they can be reliably ignored. Instead of shipping third party libraries you should rather make sure your program will be link nicely against recent versions of these libraries. If a security issue is found in one of the bundled packages, it is far easier for the package maintainers or the Security Team to patch and rebuild one package than to scan the entire archive for all copies of this code and patch them individually (this happened for zlib, for example). It's also preferable for the end users to receive an update for just one package (e.g. OpenSSL) rather than a large number of applications.
It is even worse if you maintain your private forks of third party libraries. This is not only troublesome for distributors but in the long run also to your own project. You should always make sure that the patches you might need for your specific application will be backported to the library upstream - that's simply how Free Software works.

Is there a chance to disable boost.simd or would that render pythran virtually pointless?

Out of curiosity, @serge-sans-paille are you now actually planning on migrating
to xsimd? (Which, apart from the work involved, seems like a great idea.)

And the answer is... yes :-)

@saraedum xsimd is now vendrored with pythran, and we dropped the boost.simd dependency. It's now possible to install pythran without extra deps if boost.math and boost.format and xsimd are already installed, using the appropriate setup.py flags. (master version only, requires the latest version of xsimd)

As a RFP was recently filled, I'm volunteering to retake the debian packaging effort (including the packaging of gast and beniget). :crossed_fingers:
Hopefully thanks to the migration to xsimd (which also entered debian unstable recently) and the good work since the original effort things will be a bit smoother!

@diego-plan9 : That's great news!, thanks for sharing it :-)
I'm going to do a release by the end of the week, so that's probably too short to sneak some distrib-specific patches in, but feel free to propose any updates / ask questions etc.

Thanks Serge for the heads up on the new version - and for being so open to potential discussions, questions and patches!
The "real" packaging work is likely still some time away, as it needs the dependencies to be packaged first, but I'll make use of your invitation of sharing my findings and asking questions as soon as I have progressed a bit more :+1:

As a brief status update: gast is in the NEW queue, a RFS for beniget will be issued after gast is accepted, and pythran 0.10 keeps being polished - work in progress can be checked at salsa.
Taking advantage of the previous invitation, some questions/notes:

Is there a subset of the test suite that be used as a "proxy" for ensuring the package works as expected?
Predictably, I have been running into some practical issues trying to run the full test suite (impressive coverage!). It is still in my TODO list to find out how to best handle long-running processes at the Debian packaging/CI side, but if there were a subset of tests that could run in reasonable time and still have enough confidence about the package being working, that would be very handy. I have been preliminary using test_base.py for that purpose - but any other recommendations would be welcome!

Usage of -Wno-absolute-value - is it safe to remove?
When running the test suite with the PYTHRAN_CXX_FLAGS flags defined in TestEnv, I ran into the following (using gcc-11):
error: command-line option '-Wno-absolute-value' is valid for C/ObjC but not for C++ [-Werror]

I'm not sure if this points towards a C++ compiler being used instead of a C compiler in my setup, or if it might point to an an issue with the versions of the compilers involved / supported.

Support for /etc/pythran.cfg (or a similar system-wide configuration dir)
Related to how to best deal with the .cfg files - does the current version look for pythran.cfg in the /etc/ folder? It's far from required - mostly a wishlist/question item.

Packaging the headers as a separate pythran-dev package
This one is basically a question out of curiosity - has it been considered to distribute the .hpp files as a separate package? The thinking would be to take advantage of them ending up installed in a standard location, and keep the Python package a bit more "pure" (and biased towards a packaging perspective). I have not looked into the implications fully, but I'm wondering if you would be open to me attempting to tackle it at the debian-packaging level (which might end up being causing more issues than solving, as I don't want to deviate too much from the original sources!), either at this stage or eventually.


Add best python crash course, Please merge this

What does this PR do?
Add resource
For resources
Python Crash course
Why is this valuable (or not)?
This is valuable because it's a crash course
How do we know it's really free?
It's completely free because it's a YouTube video, and you can check the same if have any confusions
For book lists, is it a book? For course lists, is it a course? etc.
Checklist:

[x] Read our contributing guidelines.
[x] Search for duplicates.
[x] Include author(s) and platform where appropriate.
[x] Put lists in alphabetical order, correct spacing.
[x] Add needed indications (PDF, access notes, under construction).
[x] Used an informative name for this pull request.

Follow-up

Check the status of GitHub Actions and resolve any reported warnings!

@eshellman have a look here and please merge it

ok so i did changes that were requested, please check and merge it

I have done the changes and removed those gdrive links

@davorpa check-urls lasted more than 6 hours

i'm closing this pr and will make a new one instead


type='RepeatDataset' in faster-rcnn r18 How to close it

i try to set  the time 0，but dont work

It optionally wraps a dataset to repeat it.  Remove the RepeatDataset and use the inner dataset definition to achieve the times=0 equivalent.


fiber framework

Description [describe your advice]
Solution [if any solutions, describe here]
Others [screenshots and other info]

now support in master branch.


SCRAM-SHA-1(-PLUS) + SCRAM-SHA-256(-PLUS) + SCRAM-SHA-512(-PLUS) + SCRAM-SHA3-512(-PLUS) supports

Dear @petergoldstein,
In first, I wish you a Happy New Year!
Can you add supports of :

SCRAM-SHA-1
SCRAM-SHA-1-PLUS
SCRAM-SHA-256
SCRAM-SHA-256-PLUS
SCRAM-SHA-512
SCRAM-SHA-512-PLUS
SCRAM-SHA3-512
SCRAM-SHA3-512-PLUS

You can add too:

SCRAM-SHA-224
SCRAM-SHA-224-PLUS
SCRAM-SHA-384
SCRAM-SHA-384-PLUS

"When using the SASL SCRAM mechanism, the SCRAM-SHA-256-PLUS variant SHOULD be preferred over the SCRAM-SHA-256 variant, and SHA-256 variants [RFC7677] SHOULD be preferred over SHA-1 variants [RFC5802]".

SCRAM-SHA-1(-PLUS):
-- https://tools.ietf.org/html/rfc5802
-- https://tools.ietf.org/html/rfc6120

SCRAM-SHA-256(-PLUS):
-- https://tools.ietf.org/html/rfc7677 since 2015-11-02
-- https://tools.ietf.org/html/rfc8600 since 2019-06-21: https://mailarchive.ietf.org/arch/msg/ietf-announce/suJMmeMhuAOmGn_PJYgX5Vm8lNA

SCRAM-SHA-512(-PLUS):
-- https://tools.ietf.org/html/draft-melnikov-scram-sha-512

SCRAM-SHA3-512(-PLUS):
-- https://tools.ietf.org/html/draft-melnikov-scram-sha3-512

https://xmpp.org/extensions/inbox/hash-recommendations.html
-PLUS variants:

RFC5056: On the Use of Channel Bindings to Secure Channels: https://tools.ietf.org/html/rfc5056
RFC5929: Channel Bindings for TLS: https://tools.ietf.org/html/rfc5929
Channel-Binding Types: https://www.iana.org/assignments/channel-binding-types/channel-binding-types.xhtml
Channel Bindings for SCRAM over TLS 1.3: https://tools.ietf.org/html/draft-whited-tls-channel-bindings-for-tls13 -> https://tools.ietf.org/html/draft-ietf-kitten-tls-channel-bindings-for-tls13

LDAP:

RFC5803: Lightweight Directory Access Protocol (LDAP) Schema for Storing Salted: Challenge Response Authentication Mechanism (SCRAM) Secrets: https://tools.ietf.org/html/rfc5803

HTTP:

RFC7804: Salted Challenge Response HTTP Authentication Mechanism: https://tools.ietf.org/html/rfc7804

2FA:

Extensions to Salted Challenge Response (SCRAM) for 2 factor authentication: https://tools.ietf.org/html/draft-melnikov-scram-2fa

IANA:

Simple Authentication and Security Layer (SASL) Mechanisms: https://www.iana.org/assignments/sasl-mechanisms/sasl-mechanisms.xhtml

Linked to:

https://github.com/scram-xmpp/info/issues/1

Happy new year.
So most of this doesn't seem very relevant to Dalli.  It's basically just a listing of hash function references with some stuff at the end about HTTP, 2FA and SASL mechanisms.
As far as the hash functions go, that's already supported.  Just create a digest_class and pass it into the client.  The hash functions in Dalli have nothing to do with authentication, encryption, or any other security concern.  I'm happy to write up a brief wiki page explaining how you can wrap any hash algorithm in a digest class, suitable for consumption by Dalli.
As far as HTTP security goes, that's irrelevant to Dalli.  Dalli doesn't use HTTP(S).
In terms of SASL (and 2FA), Dalli is first and foremost dependent on what's supported by memcached.  There's a relatively limited set of mechanisms supported there and not much usage in the community.  Pretty much everyone uses the "plain" mechanism, which is basically just passing the username/password to memcached over the channel.  This channel may or may not be encrypted with TLS/SSL.  Using a TLS encrypted channel is supported by Dalli.
Using more sophisticated non-challenge mechanisms would be fairly straightforward.  Adding a challenge mechanism, like 2FA, would not.  That's because Dalli is not really intended for use by an interactive user - it's intended for use by persistent servers that may need to reconnect at any time.
Given memcached's typically use case as a cache of data, this both makes sense and is an appropriate level of security.

@petergoldstein: Thanks again for your quickly answer and for your wishes.
I know, I have published all links about SCRAM, not specified to Dalli but it is to inform you.
The goal is to use SCRAM-SHA-* and SCRAM-SHA-*-PLUS instead of DIGEST-MD5:

https://github.com/petergoldstein/dalli/search?q=md5

I have published a ticket in important Ruby libs liked to pop/imap/smtp/ldap and memcached, you are the first to reply ^^
Like you have said, SCRAM is really good for security and it is not new, you can see an important list here:

https://github.com/scram-xmpp/info/issues/1

Note: SCRAM-SHA-1 / SCRAM-SHA-256 / SCRAM-SHA-512 are here (but not in official memcached):

https://github.com/couchbase/memcached/tree/master/cbsasl
https://github.com/couchbase/memcached/search?o=asc&q=scram&s=committer-date&type=commits

So I don't think you understand my points above.  You don't seem to understand the use cases within Dalli.
Using SCRAM-SHA-* or SCRAM-SHA-*-PLUS as a replacement for MD5 as it comes up in the search link you provided makes no sense.  MD5 is used in Dalli for key compression, not for any form of authentication or encryption.  There is no user involvement whatsoever.  So "SCRAM" algorithms, whose entire point is to add challenges to authentication requests, are totally inapplicable.
On the SASL front,  SCRAM makes no sense for the typical Dalli use case.  As I noted above:
Dalli is not really intended for use by an interactive user - it's intended for use by persistent servers that
may need to reconnect at any time.

That is completely not a fit for SCRAM, which requires user involvement to authenticate a connection.
So none of this appears to be relevant to Dalli.  Please review my comments here and above, and if you have any questions that are not just a bunch of links I'm happy to try and address.  But at this point I'm going to plan to close this issue and the other you opened sometime in the next couple of days.

Closing based on https://github.com/petergoldstein/dalli/issues/895#issuecomment-1008598618


Only parse headers

No point parsing the entire message since only some of the headers are used

I'd like @Humbedooh to review this, I'm not well versed in the code.

Ping

PING


add win_arm64 to allowed platforms

This patch enables uploading win_arm64 binary wheels to the PyPI repository.
CPython and key packages have been already ported to win/arm64 platforms. Python upstream CI is running for win/arm64 and Python official support is expected from Python 3.11. There are many package maintainers keen to start pushing win_arm64 binary wheels and would be helpful if win_arm64 is added to the permitted platform list.

Thanks, @di, and @ewdurbin for the quick review.
Do you know when the changes would be deployed on the production and test PyPI server?

@nsait-linaro It was live as of ~2 minutes ago!

@nsait-linaro It was live as of ~2 minutes ago!

Thanks, it works. I can upload wheels now 🎉


chore: update renovate to use best practices

This PR

enables renovate best practices

Notes
The current configuration seems to be invalid. This PR updates Renovate to use best practices recommended by the Renovate team.
https://docs.renovatebot.com/presets-config/#configbest-practices

Does this pin shas of actions? That's my only concern, I hate that mode.

Does this pin shas of actions? That's my only concern, I hate that mode.

Yes, it does. Perhaps we should use config-js-lib or https://docs.renovatebot.com/presets-config/#configjs-app instead.

Ya, or maybe we can override it. I'm sure the rest is fine, but I can't stand the breaking changes the action sha pinning introduces.


Add processor type in card while selecting node

Blocked till it's added and deployed on Grid Proxy.

WIP:
https://github.com/threefoldtech/tfgrid-sdk-ts/issues/2057#issuecomment-2021510752

Work completed:

Verified, Devnet 5c12959.
The CPU model and version are now displayed on each node.
on the node finder page.

And load the nodes tab on the deployments pages.

And for the node with unknown CPU, it doesn't show anything.

TC2653 - CPU type is showing on node details

Verified:

Devnet
5c12959


[Outlook] (on send) Describe workaround to prevent editing the item

Related to issue https://github.com/OfficeDev/office-js/issues/1249.

Docs Build status updates of commit e912ac5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/outlook/outlook-on-send-addins.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Purpose of Default vs DefaultSelectedItems and Selected vs SelectedItems

Its unclear and confusing what the difference is between them. I'm assuming that Selected is simply First(SelectedItems), and DefaultSelectedItems is {Value: Default} depending on the SelectMultiple property.
Edit:
Found existing closed issue #285

Default isn't mentioned because it shouldn't be used.

Then it should not be there.

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

ID: bb8bf3d3-12e3-5b55-8713-221cf5f5a30c
Version Independent ID: 5a050d01-6ef6-97d6-07de-d5cac82dea06
Content: Combo box control: reference - Power Apps
Content Source: powerapps-docs/maker/canvas-apps/controls/control-combo-box.md
Service: powerapps
GitHub Login: @chmoncay
Microsoft Alias: chmoncay

Thank you for reaching out. For help with updating feature experience (including removal of any existing properties not in use), please reach out to Power Apps Ideas Forum, or support teams with a ticket to help you out further.


Remove even more errors that I did not see in first round due to caching

As described, this pull request removes even more build errors. There are actually still a few missing, but I need help from others to fix them, as the concern missing links that I don't know.
I also removed the Schrödinger workshop 2017 and the short announcement of moving to Slurm from the news.

Thanks!


Unrecognized environment: equation

\begin{equation}
  L(Y, f(X))=\left\{
  	\begin{aligned}
  	1, \quad Y \neq f(X)\\
  	0, \quad Y = f(X)\\
  	\end{aligned}
  	\right
  	.
  \end{equation}

expect:

actual:

Currently, the equation environment is not supported. The equation requires to show its number, but for this project, it is impossible (because these equations are separated in context).
Anyway, I'll make a PR to support the equation environment but will not show its number.


[OPALSUP-257]Add team member error

on the Company/Team page, error happens when adding apps on the team and save, BEFORE adding members to this team. the API call to mno-enterprise Teams controller gets correct response, error happens at render html partial because instance.app could be nil

Closing in favor of https://github.com/maestrano/mno-enterprise/pull/757


When the OTBR is rebooted after the Matter enddevice is paired with the OTBR, the chip tool command is not transmitted.

Hi
I am currently working on a Matter project.
I configured OTBR with Raspberry Pi, completed pairing with nRF52840 board (Light bulb), and confirmed that Light on/off works (use to chiptool command).
However, after rebooting the OTBR, the Chip tool light on/off command is not delivered to the Enddevice.

Successful commissioning of endevice and otbr for the first time (node id is 300)
./chip-tool-release onoff on 300 1 When sending command, node id 300 Fabric id 0x1A1EF49FC643541D

[1661490979.941199][1352:1352] CHIP:DIS: Verifying the received credentials
[1661490979.948676][1352:1352] CHIP:DIS: Added new fabric at index: 0x3, Initialized: 1
[1661490979.948805][1352:1352] CHIP:DIS: Assigned compressed fabric ID: 0x783E482064712CE1, node ID: 0x000000000001B669
[1661490979.972146][1352:1352] CHIP:DIS: Fabric (3) persisted to storage. Calling OnFabricPersistedToStorage
[1661490979.972271][1352:1352] CHIP:CTL: Joined the fabric at index 3. Compressed fabric ID is: 0x783E482064712CE1
[1661490980.130537][1352:1357] CHIP:TOO: Sending command to node 0x12c
[1661490980.131397][1352:1357] CHIP:DIS: Resolving 1A1EF49FC643541D:000000000000012C ...
[1661490980.137856][1352:1357] CHIP:DL: Avahi resolve found
[1661490980.138696][1352:1357] CHIP:DIS: Node ID resolved for 1A1EF49FC643541D:000000000000012C
[1661490980.140833][1352:1357] CHIP:DIS: UDP:[fd99:bf05:bbe9:1:1ed7:af3:6efd:a15c%wlan0]:5540: new best score: 6
[1661490980.140986][1352:1357] CHIP:DIS: Checking node lookup status after 10 ms
[1661490980.141612][1352:1357] CHIP:DIS: Keeping DNSSD lookup active
[1661490980.331406][1352:1357] CHIP:DIS: Checking node lookup status after 200 ms
[1661490980.332571][1352:1357] CHIP:SC: Initiating session on local FabricIndex 1 from 0x000000000001B669 -> 0x000000000000012C
[1661490980.335867][1352:1357] CHIP:IN: Prepared unauthenticated message 0x5585e74768 to 0x0000000000000000 (0) of type 0x30 and protocolId (0, 0) on exchange 4525i with MessageCounter:2314344470.
[1661490980.336651][1352:1357] CHIP:IN: Sending unauthenticated msg 0x5585e74768 with MessageCounter:2314344470 to 0x0000000000000000 at monotonic time:<PHONE_NUMBER>3D4264 msec
[1661490980.337620][1352:1357] CHIP:SC: Sent Sigma1 msg

Retransmit the following command after OTBT reboot
./chip-tool-release onoff on 300 1

Fabric id is different from fabric id before otbr reboot.
[1661491207.821921][789:789] CHIP:DIS: Added new fabric at index: 0x2, Initialized: 1
[1661491207.822056][789:789] CHIP:DIS: Assigned compressed fabric ID: 0x46C385D8286F4C18, node ID: 0x000000000001B669
[1661491207.845347][789:789] CHIP:DIS: Fabric (2) persisted to storage. Calling OnFabricPersistedToStorage
[1661491207.847646][789:789] CHIP:CTL: Joined the fabric at index 2. Compressed fabric ID is: 0x46C385D8286F4C18
[1661491207.848014][789:789] CHIP:CTL: Setting attestation nonce to random value
[1661491207.848207][789:789] CHIP:CTL: Setting CSR nonce to random value
[1661491207.852583][789:789] CHIP:CTL: Generating NOC
[1661491207.855649][789:789] CHIP:DIS: Verifying the received credentials
[1661491207.863075][789:789] CHIP:DIS: Added new fabric at index: 0x3, Initialized: 1
[1661491207.863209][789:789] CHIP:DIS: Assigned compressed fabric ID: 0x55F242389EDE75B3, node ID: 0x000000000001B669
[1661491207.874940][789:789] CHIP:DIS: Fabric (3) persisted to storage. Calling OnFabricPersistedToStorage
[1661491207.877534][789:789] CHIP:CTL: Joined the fabric at index 3. Compressed fabric ID is: 0x55F242389EDE75B3
[1661491208.155696][789:794] CHIP:TOO: Sending command to node 0x12c
[1661491208.155948][789:794] CHIP:DIS: Resolving D6D4D6EF92695544:000000000000012C ...
[1661491208.356344][789:794] CHIP:DIS: Checking node lookup status after 200 ms
[1661491213.160018][789:794] CHIP:DL: Re-trying resolve
[1661491218.156018][789:789] CHIP:DIS: Cancelling incomplete address resolution as device is being deleted.
[1661491218.156171][789:789] CHIP:DIS: Discovery does not require any more timeouts
[1661491218.158868][789:789] CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented.
I checked the topology of Otbr web and found it was still connecting.

When Otbr is rebooted, the n52840 board log is also output as shown below.
D: 4171091 [DL]OpenThread State Changed (Flags: 0x00000200)
I: 4171101 [DL]SRP Client was stopped, because current server is no longer detected.
D: 4171109 [DL]OpenThread State Changed (Flags: 0x00000200)
D: 4171116 [DL]OpenThread State Changed (Flags: 0x00000002)
D: 4171121 [DL]   Thread Unicast Addresses:
D: 4171125 [DL]        fd15:f73b:9669:466a:0:ff:fe00:0/64 valid rloc
D: 4171131 [DL]        fd15:f73b:9669:466a:5d79:1733:146f:bf/64 valid
D: 4171138 [DL]        fe80::90b7:f629:a2c8:a8a9/64 valid preferred
D: 4171733 [DL]OpenThread State Changed (Flags: 0x00000200)
D: 4171740 [DL]OpenThread State Changed (Flags: 0x00000001)
D: 4171745 [DL]   Thread Unicast Addresses:
D: 4171749 [DL]        fdfa:abe6:eb46:1:bbd8:7c9:d4cd:5521/64 valid preferred
D: 4171756 [DL]        fd15:f73b:9669:466a:0:ff:fe00:0/64 valid rloc
D: 4171763 [DL]        fd15:f73b:9669:466a:5d79:1733:146f:bf/64 valid
D: 4171769 [DL]        fe80::90b7:f629:a2c8:a8a9/64 valid preferred
D: 4172039 [DL]OpenThread State Changed (Flags: 0x00000200)
I: 4172062 [DL]SRP Client was started, detected server: fd15:f73b:9669:466a:34a3:c700:bb6a:851f
D: 4172071 [DL]OpenThread State Changed (Flags: 0x00000200)
D: 4172383 [DL]OpenThread State Changed (Flags: 0x00000200)
D: 4173224 [DL]OnSrpClientNotification: Last requested operation completed successfully
D: 4174363 [DL]OpenThread State Changed (Flags: 0x00000200)
3.However, as a result of checking whether the Fabric ID exists before otbr boot, it exists.
./chip-tool-release discover resolve 300 0x1A1EF49FC643541D
coway@raspberrypi:~/Matter-aws-iot-device-sdk-python-v2/samples $ ./chip-tool-release discover resolve 300 0x1A1EF49FC643541D
[1661491291.639196][800:800] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-tTJHpF)
[1661491291.641279][800:800] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1661491291.641601][800:800] CHIP:DL: NVS set: chip-counters/reboot-count = 2 (0x2)
[1661491295.155690][800:800] CHIP:DL: Got Ethernet interface: eth0
[1661491295.156464][800:800] CHIP:DL: Found the primary Ethernet interface:eth0
[1661491295.157121][800:800] CHIP:DL: Got WiFi interface: wlan0
[1661491295.162824][800:800] CHIP:DL: Found the primary WiFi interface:wlan0
[1661491295.163624][800:800] CHIP:IN: Loading from storage for fabric index 0x1
[1661491295.168682][800:800] CHIP:IN: Loading from storage for fabric index 0x2
[1661491295.170002][800:800] CHIP:IN: Loading from storage for fabric index 0x3
[1661491295.176423][800:800] CHIP:ZCL: Using ZAP configuration...
[1661491295.182938][800:800] CHIP:DL: Avahi client registered
[1661491295.184990][800:800] CHIP:CTL: Setting attestation nonce to random value
[1661491295.185101][800:800] CHIP:CTL: Setting CSR nonce to random value
[1661491295.185264][800:800] CHIP:CTL: Setting attestation nonce to random value
[1661491295.185368][800:800] CHIP:CTL: Setting CSR nonce to random value
[1661491295.187229][800:800] CHIP:CTL: Generating NOC
[1661491295.188771][800:800] CHIP:DIS: Verifying the received credentials
[1661491295.192756][800:800] CHIP:DIS: Added new fabric at index: 0x1, Initialized: 1
[1661491295.192863][800:800] CHIP:DIS: Assigned compressed fabric ID: 0xD6D4D6EF92695544, node ID: 0x000000000001B669
[1661491295.203104][800:800] CHIP:DIS: Fabric (1) persisted to storage. Calling OnFabricPersistedToStorage
[1661491295.203187][800:800] CHIP:CTL: Joined the fabric at index 1. Compressed fabric ID is: 0xD6D4D6EF92695544
[1661491295.203372][800:800] CHIP:CTL: Setting attestation nonce to random value
[1661491295.203527][800:800] CHIP:CTL: Setting CSR nonce to random value
[1661491295.205319][800:800] CHIP:CTL: Generating NOC
[1661491295.206827][800:800] CHIP:DIS: Verifying the received credentials
[1661491295.210647][800:800] CHIP:DIS: Added new fabric at index: 0x2, Initialized: 1
[1661491295.210730][800:800] CHIP:DIS: Assigned compressed fabric ID: 0x46C385D8286F4C18, node ID: 0x000000000001B669
[1661491295.228607][800:800] CHIP:DIS: Fabric (2) persisted to storage. Calling OnFabricPersistedToStorage
[1661491295.228688][800:800] CHIP:CTL: Joined the fabric at index 2. Compressed fabric ID is: 0x46C385D8286F4C18
[1661491295.228877][800:800] CHIP:CTL: Setting attestation nonce to random value
[1661491295.228986][800:800] CHIP:CTL: Setting CSR nonce to random value
[1661491295.230832][800:800] CHIP:CTL: Generating NOC
[1661491295.232539][800:800] CHIP:DIS: Verifying the received credentials
[1661491295.237266][800:800] CHIP:DIS: Added new fabric at index: 0x3, Initialized: 1
[1661491295.237401][800:800] CHIP:DIS: Assigned compressed fabric ID: 0x55F242389EDE75B3, node ID: 0x000000000001B669
[1661491295.259592][800:800] CHIP:DIS: Fabric (3) persisted to storage. Calling OnFabricPersistedToStorage
[1661491295.259727][800:800] CHIP:CTL: Joined the fabric at index 3. Compressed fabric ID is: 0x55F242389EDE75B3
[1661491295.447558][800:805] CHIP:DIS: Resolving 1A1EF49FC643541D:000000000000012C ...
[1661491295.556267][800:805] CHIP:DL: Avahi resolve found
[1661491295.556467][800:805] CHIP:DIS: Node ID resolved for 1A1EF49FC643541D:000000000000012C
[1661491295.558047][800:805] CHIP:DIS: UDP:[fd99:bf05:bbe9:1:1ed7:af3:6efd:a15c%wlan0]:5540: new best score: 6
[1661491295.558151][800:805] CHIP:DIS: Checking node lookup status after 110 ms
[1661491295.558220][800:805] CHIP:DIS: Keeping DNSSD lookup active
[1661491295.648033][800:805] CHIP:DIS: Checking node lookup status after 200 ms
[1661491295.648186][800:805] CHIP:TOO: NodeId Resolution: 300 at UDP:[fd99:bf05:bbe9:1:1ed7:af3:6efd:a15c]:5540
[1661491295.648255][800:805] CHIP:TOO: MRP retry interval (idle): 5000ms
[1661491295.648320][800:805] CHIP:TOO: MRP retry interval (active): 300ms
[1661491295.648382][800:805] CHIP:TOO: Supports TCP: no
[1661491295.648600][800:805] CHIP:DIS: Discovery does not require any more timeouts
[1661491295.653085][800:800] CHIP:BLE: BleConnectionDelegate::CancelConnection is not implemented.
[1661491295.653735][800:800] CHIP:DL: writing settings to file (/tmp/chip_counters.ini-suUJsH)
[1661491295.656470][800:800] CHIP:DL: renamed tmp file to file (/tmp/chip_counters.ini)
[1661491295.656650][800:800] CHIP:DL: NVS set: chip-counters/total-operational-hours = 0 (0x0)
[1661491295.656772][800:800] CHIP:DL: Inet Layer shutdown
[1661491295.656840][800:800] CHIP:DL: BLE shutdown
[1661491295.656920][800:800] CHIP:DL: System Layer shutdown
I think Enddevice and otbr can send and receive cluster commands successfully even if Otbr is rebooted if Fabric ID does not change after Otbr reboots
Please guide.
Thank you

@cw-20021349 Is "OTBR" in this case the same device that chip-tool is running on?   Or a different device?

@bzbarsky-apple hi It's the same device.

Hi
When pairing with Chip-tool for the first time, config and pairing information are saved in /tmp.
When the Raspberry Pi reboots, the files in /tmp are deleted.
Chip-tool config files in /tmp after pairing with enddevice

After rebooting the raspberry, check the files in the /tmp path (all erased)

I think that the chip tool config and information when paired with Enddevcie for the first time should be saved in a path other than /tmp. Can you give me a guide?

@bzbarsky-apple hi It's the same device.

In that case the issue is that chip-tool stores its state in /tmp, as you discovered.  That's not particularly configurable right now, without code changes.

I faced the same issue at Matter v1.0.0.
I want to know how to fix or prevent this issue.

I found out how to prevent this issue.
content:
A quick solution could be to modify the setting of /tmp:
sudo vim /usr/lib/tmpfiles.d/tmp.conf
Change the line "D /tmp 1777 root root -" to "d /tmp 1777 root root -"
Then the content of /tmp will not be removed on every reboot.
reference:
https://devzone.nordicsemi.com/f/nordic-q-a/91280/when-the-otbr-is-rebooted-after-the-matter-enddevice-is-paired-with-the-otbr-the-chip-tool-command-is-not-transmitted


Remove solution from StarWars template

For me there's no clear reason, why the StarWars example needs a solution file.
This is just something I wouldn't expect from dotnet new and it introduces a new subfolder nobody really needs.
This PR aligns the StarWars example with the Server Template.

Yes... let's remove it. Having just a project also aligns it with the empty template.


added tests for noUnusedVariables

I noticed noUnusedVariables didn't have any tests and I added some.
While doing so, I found a bug - I think.
The following block statement doesn't throw any error:
function foo(myVar) {
  console.log("foo");
}
foo();

I should expect to have an error for myVar, am I right? I could fix it in this PR but I'd need some help. :)

Not sure off the top of my head what could be causing that bug. There are these lines that we have to mark parameters as used since the last one is the only one that could theoretically be handled. You can console.log(usedBindings); and see if it's related.

@sebmck So I did some debugging inside the code and it turns out that for this particular piece of code, the program doesn't go inside the loop that you highlighted.
The scope of that program returns only foo as own binding

@sebmck So I did some debugging inside the code and it turns out that for this particular piece of code, the program doesn't go inside the loop that you highlighted.
The scope of that program returns only foo as own binding. myVar is not there.

Ah. I think it has something to do with some weirdness because when we go into a JSBlockStatement we inherit from the parent functionshead scope.

@bitpshr done! PR updated!
Here is the issue https://github.com/romejs/rome/issues/539

In the lint rule, I think that
if (rest === undefined) {
  ignoreLast = false;
}

should be
if (rest !== undefined) {
  ignoreLast = false;
}

That passes the test case you have commented out.

@bitpshr @yassere PR updated!

Thank you! Snapshots are failing but I'll fix it in trunk.


Cannot Update Campaign Collections

While https://www.dosomething.org/volunteer/old-school-impact has campaigns as part of the collection, the edit tab (https://www.dosomething.org/node/4953/edit) shows no campaigns, so leads cannot edit the collection.

@sergii-tkachenko could this be related to https://github.com/DoSomething/phoenix/issues/5195 -- both have campaign field reference? if so, will it be fixed when https://github.com/DoSomething/phoenix/pull/5315 is deployed? Thanks!!

@mikefantini @sergii-tkachenko Adam needs to show this to AARP the week of the 19th, so would be great to have this all fixed by the 15th (a Thursday) if possible!

Looking at this.

Looks like it's related to #5195
Not sure if Home page was fixed manually or programmatically #5315 cc @mikefantini
Investigating the reason behind this

I just confirmed that executing script from #5315 fixed the issue on staging: http://staging.beta.dosomething.org/node/1194/edit.
I think we should run in on prod. Will coordinate this with @sheyd.

Fixed in https://github.com/DoSomething/phoenix/issues/5276#issuecomment-147792473.


Improved proxy header support

add zuul.add-host-header property to add Host header
add port to X-Forwarded-Host as defined in RFC 7239
extract PreDecorationFilter.filterOrder() into a public constant

fixes #1108

Closed with tests added via beb84dbe07e1be3bd6cb5db9df4241af55c702fb


docker swarm init error

When I executed " sh startDatabox.sh",the following process and error occurs
Error response from daemon: This node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again.
More than one IP found please select from the list.

<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
#? <IP_ADDRESS>
flag needs an argument: --advertise-addr
See 'docker swarm init --help'.
Ignoring unsupported options: build

this node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again
[seeding manifest] waiting for appstore
[seeding manifest] waiting for appstore
[seeding manifest] waiting for appstore

Hi,
Can you provide some more information?
What branch, OS, docker version?
Also, how did you select the IP address?  Did you type the full address?

hello!
I cloned the latest source code form me/databox repos and I built the virtual machine OS(centos7) using vagrant and then installed requirements(docker,pip,docker-compose,etc;) that are also latest version  and then I executed 'sh startDatabox.sh' comment.
In Command promant,asking IP like as following
More than one IP found please select from the list.

<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
#?
And then I type <IP_ADDRESS> and press enter
And Finally error occurs ,
flag needs an argument: --advertise-addr
See 'docker swarm init --help'.
Creating certs
./certs/arbiter.json arbiter
./certs/export-service.json export-service
./certs/syslog.json syslog
Done!
Ignoring unsupported options: build

this node is not a swarm manager. Use "docker swarm init" or "docker swarm join" to connect this node to swarm and try again
[seeding manifest] waiting for appstore
[seeding manifest] waiting for appstore

"then I type <IP_ADDRESS> and press enter"
Just use 1,2 or 3 to select the IP do not type the address.

oh!
why i don't think about it , Thanks you.
error is clear :)

Glad it's fixed.
Cheers
Tosh

Cheers!
Could I inquire about Databox?
Is it work the export service in Databox?
Is Databox possible to connect with external server[example; PPM server]?
Thanks,


Compilation error when using Simulink co-simulation

Describe the bug
Unable to run Simulink S-function co-simulation due to compilation error. A solution is proposed under the headline Additional information.
To Reproduce

Export an arbritary model to Simulink S-function
Run HopsanSimulinkCompile.m in Matlab

Expected behavior
The following error appears:
Compiling S-function from Hopsan model...
Building with 'Microsoft Visual C++ 2017'.
Error using mex
indexingcsvparser.cpp
C:\Users\samka91\Desktop\review\cosim\HopsanCore\dependencies\indexingcsvparser\src\indexingcsvparser.cpp(292): error C2039: 'min': is not a member of 'std'
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\include\vector(20): note: see declaration of 'std'
C:\Users\samka91\Desktop\review\cosim\HopsanCore\dependencies\indexingcsvparser\src\indexingcsvparser.cpp(292): error C3861: 'min': identifier not found
C:\Users\samka91\Desktop\review\cosim\HopsanCore\dependencies\indexingcsvparser\src\indexingcsvparser.cpp(293): error C2039: 'max': is not a member of 'std'
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.15.26726\include\vector(20): note: see declaration of 'std'
C:\Users\samka91\Desktop\review\cosim\HopsanCore\dependencies\indexingcsvparser\src\indexingcsvparser.cpp(293): error C3861: 'max': identifier not found
C:\Users\samka91\Desktop\review\cosim\HopsanCore\dependencies\indexingcsvparser\src\indexingcsvparser.cpp(327): warning C4267: 'argument': conversion from 'size_t' to 'long',
possible loss of data
C:\Users\samka91\Desktop\review\cosim\HopsanCore\dependencies\indexingcsvparser\src\indexingcsvparser.cpp(331): warning C4267: 'argument': conversion from 'size_t' to 'int',
possible loss of data
C:\Users\samka91\Desktop\review\cosim\HopsanCore\dependencies\indexingcsvparser\src\indexingcsvparser.cpp(363): warning C4267: 'argument': conversion from 'size_t' to 'long',
possible loss of data
C:\Users\samka91\Desktop\review\cosim\HopsanCore\dependencies\indexingcsvparser\src\indexingcsvparser.cpp(372): warning C4267: 'argument': conversion from 'size_t' to 'int',
possible loss of data
C:\Users\samka91\Desktop\review\cosim\HopsanCore\dependencies\indexingcsvparser\src\indexingcsvparser.cpp(406): warning C4267: 'argument': conversion from 'size_t' to 'long',
possible loss of data
C:\Users\samka91\Desktop\review\cosim\HopsanCore\dependencies\indexingcsvparser\src\indexingcsvparser.cpp(409): warning C4267: 'argument': conversion from 'size_t' to 'int',
possible loss of data

Error in HopsanSimulinkCompile (line 2)
mex -DHOPSAN_INTERNALDEFAULTCOMPONENTS -DHOPSAN_INTERNAL_EXTRACOMPONENTS -D_USE_MATH_DEFINES -DWIN32 -I"HopsanCore/include" -I"componentLibraries/defaultLibrary"
-I"HopsanCore/dependencies/rapidxml" -I"HopsanCore/dependencies/indexingcsvparser/include" -I"HopsanCore/dependencies/libnumhop/include" HopsanCore/src/Component.cpp
HopsanCore/src/ComponentSystem.cpp HopsanCore/src/ComponentUtilities/AuxiliarySimulationFunctions.cpp HopsanCore/src/ComponentUtilities/CSVParser.cpp
HopsanCore/src/ComponentUtilities/DoubleIntegratorWithDamping.cpp HopsanCore/src/ComponentUtilities/DoubleIntegratorWithDampingAndCoulumbFriction.cpp
HopsanCore/src/ComponentUtilities/EquationSystemSolver.cpp HopsanCore/src/ComponentUtilities/FirstOrderTransferFunction.cpp HopsanCore/src/ComponentUtilities/HopsanPowerUser.cpp
HopsanCore/src/ComponentUtilities/IntegratorLimited.cpp HopsanCore/src/ComponentUtilities/LookupTable.cpp HopsanCore/src/ComponentUtilities/ludcmp.cpp
HopsanCore/src/ComponentUtilities/matrix.cpp HopsanCore/src/ComponentUtilities/PLOParser.cpp HopsanCore/src/ComponentUtilities/SecondOrderTransferFunction.cpp
HopsanCore/src/ComponentUtilities/WhiteGaussianNoise.cpp HopsanCore/src/CoreUtilities/AliasHandler.cpp HopsanCore/src/CoreUtilities/ConnectionAssistant.cpp
HopsanCore/src/CoreUtilities/HmfLoader.cpp HopsanCore/src/CoreUtilities/HopsanCoreMessageHandler.cpp HopsanCore/src/CoreUtilities/LoadExternal.cpp
HopsanCore/src/CoreUtilities/MultiThreadingUtilities.cpp HopsanCore/src/CoreUtilities/NumHopHelper.cpp HopsanCore/src/CoreUtilities/SaveRestoreSimulationPoint.cpp
HopsanCore/src/CoreUtilities/SimulationHandler.cpp HopsanCore/src/CoreUtilities/StringUtilities.cpp HopsanCore/src/HopsanEssentials.cpp HopsanCore/src/HopsanTypes.cpp
HopsanCore/src/Node.cpp HopsanCore/src/Nodes.cpp HopsanCore/src/Parameters.cpp HopsanCore/src/Port.cpp HopsanCore/src/Quantities.cpp
HopsanCore/dependencies/libnumhop/src/Expression.cpp HopsanCore/dependencies/libnumhop/src/Helpfunctions.cpp HopsanCore/dependencies/libnumhop/src/VariableStorage.cpp
HopsanCore/dependencies/indexingcsvparser/src/indexingcsvparser.cpp componentLibraries/defaultLibrary/defaultComponentLibraryInternal.cpp componentLibraries/extra-components.cpp
testModel.cpp  -output testModel

Hopsan version (please complete the following information):

Windows 10
HopsanGUI 64-bit, Version: <IP_ADDRESS>80912.0739
Matlab 2019a
Microsoft Visual Studio 2017

Additional information
After adding #include <algorithm>  in \Hopsan\HopsanCore\dependencies\indexingcsvparser\src\indexingcsvparser.cpp, everything works fine.

This problem belongs to the IndexingCSVParser, which is actually a separate GitHub project. I have reported it there and linked to this issue.

@samuelkarnell I have been trying to add CI support for MSVC to ensure that hopsancore will work with this compiler. I found two other issues that you may run into, one stack overflow if parameters refer to the selves, and a bug in the lookuptable parser when temporary files are used.
See https://github.com/Hopsan/hopsan/pull/1875/commits/b1f63bea603e7455508a9295e9a3a2414e5d0234 and https://github.com/Hopsan/hopsan/pull/1875/commits/e23a880fbecc80ab6bd0819e2a240ef165ad19ce for details if you run into these problems.


Documentation missing for SPI and ADC async operations

None of the user-visible SPI or ADC operations that end in _async appear in the generated documentation although there are references to their existence.
(Also: in the second link above documentation comment for spi_api_io_async erroneously overrides its target with an incorrect @typedef annotation.)

This is fixed now, since the funcitons appear in the generated doc


Can it work when the dev pane is not open?

Now the rule only work when I have opened the dev pane.

It works after I restart the chrome. Sorry for the noise.


ClearableFileInput and "required" attritube at the Edit time

The ClearableFileInput at the edition time  (when a file has already been uploaded), for files required , let the "required" attribute in the input. The consequence of this, the browser (like Chrome)  didn't know a file has already been uploaded, a tooltip appears and the submission of the form is blocked.
The standard Django widget does not show the "required" attribute at any time
Django widget rendering at the creation time
<input id="id_file" name="file" type="file">

Django widget redering at the edit time, (with file in it)
   Currently: RICE.pdf
Change: <input id="id_file" name="file" type="file">

Floppyform widget rendering at the creation time
<input type="file" name="file" required="" id="id_file" class="form-control">

Floppyform widget rendering at the edition time, with file already uploaded

  RICE.pdf

<Change:

<input type="file" name="file" required="" id="id_file" class="form-control">

In the floppyform widget rendering, we clearly see the "required" attribute which does not appear on the Django widget rendering.
Workaround
To avoid this, I rewrite the widget, get_context method actually
     def get_context(self, name, value, attrs):
            ctx = super(MyClearableFileInput, self).get_context(name, value, attrs)
            if value:
                ctx['required'] = False
           return ctx

I have simular issue with ImageField
#199
Do you think your "def get_context()" code can help me?
I've been thinking maybe to solve it using a jquery hack onload


Mark smoke-catalina not flaky

This reverts commit 99bc4de73c8422e21b7d65764af506ef21ec75ea.
Working theory was a transient device issue?  Hasn't flaked in awhile.
Fixes https://github.com/flutter/flutter/issues/71178

cool?

🤷♀
computers, man.

cool?

🤷♀
computers, man.

i approved it, btw

i approved it, btw


staticpod installer: set the manifests directory permissions to 0600

To conform to CIS benchmarks
Testing PR: https://github.com/openshift/cluster-kube-scheduler-operator/pull/485

/retest-required

/lgtm


Align operationIds to comply with guidelines

Changed operationIds to reflect Guidelines + updated guideline

@MassimoC 	@MisterKite 	what's the status here?

Can you also provide an example of the Swagger spec that is generated please @MisterKite?


Move Dependency on OMGHTTPURLRQ to Subspec

I wanted to clean up dependencies, because more frameworks slow app start down. The dynamic loader takes longer the more there are.
The subspec DietFoundation does not offer any support for NSURLSession because it shouldn't have external dependencies.
PromiseKit.Foundation depends on OMGHTTPURLRQ. That dependency really isn't needed. It could be extracted to a different file and moved to its own subspec.
So the dependency on OMGHTTPURLRQ either should

be moved to its own subspec PromiseKit.OMGHTTPURLRQ, so that DietFoundation and Foundation can be merged.
stay in PromiseKit.Foundation, but add the NSURL* extensions like the one below on NSURLSession to DietFoundation.

extension NSURLSession {
    public func promise(request: NSURLRequest) -> URLDataPromise {
        return start(request, session: self)
    }
}

private func start(@autoclosure body: () throws -> NSURLRequest, session: NSURLSession = NSURLSession.sharedSession()) -> URLDataPromise {
    do {
        let request = try body()
        return URLDataPromise.go(request) { completionHandler in
            let task = session.dataTaskWithRequest(request, completionHandler: completionHandler)
            task.resume()
        }
    } catch {
        return URLDataPromise(error: error)
    }
}

This is already done in PromiseKit 4, to be released with Xcode 8.

Though we have no plans to do it for 1.x or 2.3-minimal-changes, but we could if desired.

Thanks. I hadn't checked PromiseKit 4, sorry.