Remove dependency on fmt

fmt isn't adding much value, and can be mildly annoying, e.g. by default it builds only a static library but tuber now doesn't like linking with that. It's simpler to just stop using it.

Wow, I don't understand why this particular change is breaking the wheel builds.  Nothing you've done should have affected the other dependencies.  Super weird!  I'll try to reproduce / fix on my fork.

My only guess is that the include search path wasn't actually being set correctly for libhttpserver, but that it happened to be in the same place as fmt and so was working as a result of adding the search path entry for that?
This does remind me, however, to also clean fmt out of the workflow and install_deps scripts.

My only guess is that the include search path wasn't actually being set correctly for libhttpserver, but that it happened to be in the same place as fmt and so was working as a result of adding the search path entry for that?

Oh yeah, that's certainly possible.  I'll investigate.

Ah, yep, this is the fix:
diff --git a/CMakeLists.txt b/CMakeLists.txt
index 7e4d971..af0fe1d 100644
--- a/CMakeLists.txt
+++ b/CMakeLists.txt
@@ -35,6 +35,7 @@ find_package(Threads REQUIRED)
 include(CTest)

 pybind11_add_module(_tuber_runtime MODULE src/server.cpp)
+target_include_directories(_tuber_runtime PUBLIC ${LIBHTTPSERVER_INCLUDE_DIRS})
 target_link_libraries(_tuber_runtime PUBLIC ${LIBHTTPSERVER_LIBRARIES} Threads::Threads)

 pybind11_add_module(test_module MODULE tests/test_module.cpp)

Out of interest - what do you think about -DFMT_HEADER_ONLY?
As I understand it, libfmt is a preview of std::format or std::print, so this shifting (at c++ committee pace) from an external dependency to the new, non-iostream-based way to do string formatting.

That would fix the specific linking issue I had, but it still seems simpler to remove it, since it was called in a total of five remaining places and wasn't doing anything that couldn't be trivially be done even in C++98. Even if something equivalent were in the standard today, I wouldn't see any point in using it; in my opinion the iostreams style is clearer than the old-fashioned printf-style, anyway.

I was about to pull rank and leave libfmt in place (personal preference - I am allergic to iostreams). But I love red diffs more than anything else in the world.


Updates dependencies on the observe package

This issue was originally filed by @vicb

I'm trying to add some support for Observable in Angular.Dart but I have the following problem: code_transformers depends on "analyzer: '>=0.13.2 <0.14.0'"
The current observable depends on "analyzer: '>=0.15.6 <0.16.0'" (and this is the same for intl).
It would be great that when a core package is updated all the packages that depends on it are also updated.
May be this is the case but only for stable release ?
Meanwhile it would really help to show dependencies on pub.dartlang.org, see https://code.google.com/p/dart/issues/detail?id=19436

This issue has been moved to dart-lang/observe#64.


GitHub releases do not include dist bundled files

I think it would be useful to also include the bundled d3fc files in GitHub releases (assuming GitHub releases is still relevant?).
Currently, only the following files are including:

GitHub releases are certainly relevant, although I don't know whether people use them to obtain the library (as we already have CDN, npm, etc .,.). Anyhow, it is pretty easy to provide our library via this release mechanism.


Trying to get TypeScript color coding to work correctly

Issue Type: Bug
Running into the error even though I have the correct @types/react version installed.
"JSX element implicitly has type 'any' because no interface 'JSX.IntrinsicElements' exists.ts"
VS Code version: Code 1.43.0 (78a4c91400152c0f27ba4d363eb56d2835f9903a, 2020-03-09T19:34:44.548Z)
OS version: Darwin x64 21.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
3, 3, 4

Memory (System)
32.00GB (0.51GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (19)

Extension
Author (truncated)
Version

vscode-nginx-conf
ahm
0.1.3

vscode-java-entities-converter
alb
0.0.1

vscode-erb-beautify
ali
0.2.0

vscode-zipfs
arc
1.0.1

vscode-eslint
dba
2.1.8

docs-markdown
doc
0.2.76

gitlens
eam
10.2.3

prettier-vscode
esb
5.5.0

code-runner
for
0.11.2

terraform
has
2.3.0

npm-dependency-check
jan
1.3.0

vscode-docker
ms-
1.1.0

vscode-typescript-next
ms-
5.0.20221116

vscode-groovy-lint
Nic
1.4.0

nginx-formatter
ray
0.0.13

ruby
reb
0.28.1

bash-beautify
sha
0.1.1

vscode-ruby
win
0.28.0

markdown-all-in-one
yzh
3.4.0

Thanks for creating this issue! It looks like you may be using an old version of VS Code, the latest stable release is 1.73.1. Please try upgrading to the latest version and checking whether this issue remains.
Happy Coding!

I disabled the other extensions one by one and fixed the issue by trial and error :-)


Static code analysis _036 (Null Pointer Dereference)

Short summary (details in attached file):
LinuxGPTPPersistFile::triggerWriteStorage()
.../linux/src/linux_hal_persist_file.cpp

    bool triggerWriteStorage(void)
    {
            if (!writeCB) {

event Event 2:  Considering the case where writeCB must have been equal to 0.
                    GPTP_LOG_ERROR("Persistent write callback not registered");
            }
            bool result = false;
            if (memoryDataLength > storedDataLength) {
            ...
            }
            writeCB((char *)restoredata, storedDataLength);

Null Pointer Dereference: writeCB is dereferenced here, but it is NULL.

gptp_036.txt

Fix was merged.


[FEAT] Add Athena Datediff function

Is your proposal related to a problem?

Datediff comparison is not currently available for athena. There appears to be an athena datediff function so should (hopefully) be able to add this functionality.
Describe the solution you'd like

Define cll.datediff_level and cl.datediff_at_thresholds for athena, similar to spark and duckdb.
Describe alternatives you've considered

Additional context

Linked to #881


The 'latest' folder can contain multiple versions of data

Issue
Because there are several possible output file formats, it is possible to re-upload data without overwriting it.
For example:

A csv of a given dataset gets upload as version 2021-01-29 and latest.
A shapefile of the same dataset gets uploaded as version 2021-02-28 and latest, but no csv gets uploaded as latest.
The directory 'latest' now contains data from both 2021-01-29 and 2021-02-28.

How can we enforce version consistency within "latest?"
Ideas for solutions

Only use the latest directory for one file format, either consistent across datasets or saved as a "default" in config
Create subdirectories for file type (not ideal)
If the latest option gets called, remove and recreate the latest directory entirely (or keep it and delete everything in it before uploading the new data -- the effect would be the same). In the above example, the 2021-01-29 csv in the latest directory would get deleted when the 2021-02-28 version would get uploaded. The resulting latest directory would only contain shapefile data, and only from 2021-02-28. This approach has the downside that only a single file can exist in latest using our given code, since each output file format is a separate command.
If upload as latest gets called, remove all files within the latest directory that do not have the same version as the one getting uploaded. We can back-track versions from s3 metadata to do this. This allows us to keep the uploading code as it is, rather than building a "bulk upload" option that iterates through file types.

separate the latest tagging process into a separate function <class>.tag_latest(version='20210127', ...)
this function should do the following:

copy files from .../20210127/ folder into .../latest/
store files copied into files.txt
or ideally we can store that list of latest files config.yml and config.json

separate the latest tagging process into a separate function <class>.tag_latest(version='20210127', ...)
this function should do the following:

copy files from .../20210127/ folder into .../latest/
store files copied into files.txt
or ideally we can store that list of latest files config.yml and config.json

A csv of a given dataset gets upload as version 2021-01-29 and tagged as latest
in latest folder,  file.txt will specify the latest files

/ 2021-01-29 /data.csv

A shapefile of the same dataset gets uploaded as version 2021-02-28 and tagged as latest, but no csv gets uploaded as latest.
in latest folder,  file.txt will specify the latest files

/ 2021-02-28 /data.shp

A csv of a given dataset gets upload as version 2021-01-29 and tagged as latest
in latest folder,  file.txt will specify the latest files

/ 2021-01-29 /data.csv

A shapefile of the same dataset gets uploaded as version 2021-02-28 and tagged as latest, but no csv gets uploaded as latest.
in latest folder,  file.txt will specify the latest files

/ 2021-02-28 /data.shp


support non-cached (correlated) distributed subquery, which requires parameters from parent query

When a correlated subquery is not expandable to join, we have to keep the subQueryExpr to evalute it. In this case, subQueryExpr requires a parameter to evaluate it every time (see plan with a ? mark). This is supported in non-distributed execution by passing the parameter around with ExecContext.GetParam/AddParam(). However, this mechanism is missing in Distributed execution, we shall patch it.

@zhouqingqing @arzuschen This requirement is processing.


usm: http2: Increment request_seen and response_seen if method/status are literal headers

What does this PR do?
Increment request_seen and response_seen if method/status are literal headers

Motivation
A miss by 2 previous PRs.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided. Except if the qa/skip-qa label, with required either qa/done or qa/no-code-change labels, are applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

will be covered in #22778


Bug report:  m365 spo listitem add - multi-choice field

Description
Hello
I cannot create an item trying to supply an array for multiple choice with Fill-ins enabled. The array gets truncated to a single-line.
Input:
m365 spo listitem add --listTitle "ListTitle" --webUrl $u --Title $_."Title" --MultiChoiceField '["ValueA","ValueB"]'
Output:
(...)
"MultiChoiceField": [
"['ValueA','ValueB']"
],
(...)
The output truncated the array (note I tried handful of different combinations of passing in an array, couldn't find a proper one).
Expected output:
"MultiChoiceField": [
"ValueA",
"ValueB"
]
Which is the result of m365 spo listitem get after correcting the listitem manually.
Can you please advise the proper format or address with fix?
Steps to reproduce
Create multichoice column with fillins enabled.
m365 spo listitem add --listTitle "ListTitle" --webUrl $u --Title $_."Title" --MultiChoiceField '["ValueA","ValueB"]'
Expected results
"MultiChoiceField": [
"ValueA",
"ValueB"
]
Actual results
(...)
"MultiChoiceField": [
"['ValueA','ValueB']"
],
(...)
Diagnostics
Executing command spo listitem add with options {"options":{"listTitle":"MyList","webUrl":"https://mysite.sharepoint.com/sites/MySite","MultiChoiceColumn":"['ValueA','ValueB']","debug":true,"output":"json"}}
Getting content types for list...
Existing access token eyJ0eXAiOi still valid. Returning...
Request:
{
"url": "https://mysite.sharepoint.com/sites/MySite/_api/web/lists/getByTitle('MyList')/contenttypes?$select=Name,Id",
"method": "get",
"headers": {
"common": {
"Accept": "application/json, text/plain, /"
},
"delete": {},
"get": {},
"head": {},
"post": {
"Content-Type": "application/x-www-form-urlencoded"
},
"put": {
"Content-Type": "application/x-www-form-urlencoded"
},
"patch": {
"Content-Type": "application/x-www-form-urlencoded"
},
"user-agent": "NONISV|SharePointPnP|CLIMicrosoft365/5.8.0",
"accept-encoding": "gzip, deflate",
"accept": "application/json;odata=nometadata",
"authorization": "Bearer eyJ0eXA"
},
"responseType": "json",
"decompress": true
}
Response:
{
"url": "https://mysite.sharepoint.com/sites/MySite/_api/web/lists/getByTitle('MyList')/contenttypes?$select=Name,Id",
"status": 200,
"statusText": "OK",
"headers": {
"cache-control": "private, max-age=0",
"transfer-encoding": "chunked",
"content-type": "application/json;odata=nometadata;streaming=true;charset=utf-8",
"expires": "Sat, 29 Oct 2022 19:34:28 GMT",
"last-modified": "Sun, 13 Nov 2022 20:34:28 GMT",
"vary": "Origin,Accept-Encoding",
"p3p": "CP="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI"",
"x-networkstatistics": "0,525568,0,58,357517,0,525568",
"x-sharepointhealthscore": "2",
"x-sp-serverstate": "ReadOnly=0",
"dataserviceversion": "3.0",
"spclientservicerequestduration": "25",
"x-aspnet-version": "4.0.30319",
"x-databoundary": "None",
"x-1dscollectorurl": "https://eu-mobile.events.data.microsoft.com/OneCollector/1.0/",
"x-ariacollectorurl": "https://eu-mobile.events.data.microsoft.com/Collector/3.0",
"sprequestguid": "034e78a0-d045-5000-5c7a-c17a24b21a91",
"request-id": "034e78a0-d045-5000-5c7a-c17a24b21a91",
"ms-cv": "oHhOA0XQAFBcesF6JLIakQ.0",
"strict-transport-security": "max-age=31536000",
"x-frame-options": "SAMEORIGIN",
"content-security-policy": "frame-ancestors 'self' teams.microsoft.com *.teams.microsoft.com *.skype.com *.teams.microsoft.us local.teams.office.com *.powerapps.com *.yammer.com *.officeapps.live.com *.office.com *.stream.azure-test.net *.microsoftstream.com *.dynamics.com *.microsoft.com securebroker.sharepointonline.com;",
"x-powered-by": "ASP.NET",
"microsoftsharepointteamservices": "<IP_ADDRESS>26",
"x-content-type-options": "nosniff",
"x-ms-invokeapp": "1; RequireReadOnly",
"x-cache": "CONFIG_NOCACHE",
"x-msedge-ref": "Ref A: CFEC0496DF484F3E8AC64274E580F97D Ref B: BER30EDGE0819 Ref C: 2022-11-13T20:34:28Z",
"date": "Sun, 13 Nov 2022 20:34:27 GMT",
"connection": "close"
},
"data": {
"value": [
{
"Id": {
"StringValue": "0x0100F693387DE588C84A9A0259B7C22F6E5A000FCCF5C9E50EE6468B6051FE5C02E290"
},
"Name": "Element"
},
{
"Id": {
"StringValue": "0x012000CDA987B01F47B447BD2322C67052AF66"
},
"Name": "Folder"
}
]
}
}
Creating item in list MyList in site https://mysite.sharepoint.com/sites/MySite...
Existing access token eyJ0eXAiOiJKV1QiL still valid. Returning...
Request:
{
"url": "https://mysite.sharepoint.com/sites/MySite/_api/web/lists/getByTitle('MyList')/AddValidateUpdateItemUsingPath()",
"method": "post",
"headers": {
"common": {
"Accept": "application/json, text/plain, /"
},
"delete": {},
"get": {},
"head": {},
"post": {
"Content-Type": "application/x-www-form-urlencoded"
},
"put": {
"Content-Type": "application/x-www-form-urlencoded"
},
"patch": {
"Content-Type": "application/x-www-form-urlencoded"
},
"user-agent": "NONISV|SharePointPnP|CLIMicrosoft365/5.8.0",
"accept-encoding": "gzip, deflate",
"accept": "application/json;odata=nometadata",
"authorization": "Bearer eyJ0eXAi"
},
"responseType": "json",
"decompress": true,
"data": {
"formValues": [
{
"FieldName": "MultiChoiceColumn",
"FieldValue": "['ValueA','ValueB']"
}
]
}
}
Response:
{
"url": "https://mysite.sharepoint.com/sites/MySite/_api/web/lists/getByTitle('MyList')/AddValidateUpdateItemUsingPath()",
"status": 200,
"statusText": "OK",
"headers": {
"cache-control": "private, max-age=0",
"transfer-encoding": "chunked",
"content-type": "application/json;odata=nometadata;streaming=true;charset=utf-8",
"expires": "Sat, 29 Oct 2022 19:34:28 GMT",
"last-modified": "Sun, 13 Nov 2022 20:34:28 GMT",
"vary": "Origin,Accept-Encoding",
"p3p": "CP="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI"",
"x-networkstatistics": "0,525568,0,0,2245,0,28941",
"x-sharepointhealthscore": "1",
"x-sp-serverstate": "ReadOnly=0",
"dataserviceversion": "3.0",
"spclientservicerequestduration": "65",
"x-aspnet-version": "4.0.30319",
"x-databoundary": "None",
"x-1dscollectorurl": "https://eu-mobile.events.data.microsoft.com/OneCollector/1.0/",
"x-ariacollectorurl": "https://eu-mobile.events.data.microsoft.com/Collector/3.0",
"sprequestguid": "034e78a0-9052-5000-8558-53f08cb26c52",
"request-id": "034e78a0-9052-5000-8558-53f08cb26c52",
"ms-cv": "oHhOA1KQAFCFWFPwjLJsUg.0",
"strict-transport-security": "max-age=31536000",
"x-frame-options": "SAMEORIGIN",
"content-security-policy": "frame-ancestors 'self' teams.microsoft.com *.teams.microsoft.com *.skype.com *.teams.microsoft.us local.teams.office.com *.powerapps.com *.yammer.com *.officeapps.live.com *.office.com *.stream.azure-test.net *.microsoftstream.com *.dynamics.com *.microsoft.com securebroker.sharepointonline.com;",
"x-powered-by": "ASP.NET",
"microsoftsharepointteamservices": "<IP_ADDRESS>26",
"x-content-type-options": "nosniff",
"x-ms-invokeapp": "1; RequireReadOnly",
"x-cache": "CONFIG_NOCACHE",
"x-msedge-ref": "Ref A: 144CFBEC6A2140E38CF86C75D839BD71 Ref B: BER30EDGE0508 Ref C: 2022-11-13T20:34:28Z",
"date": "Sun, 13 Nov 2022 20:34:28 GMT",
"connection": "close"
},
"data": {
"value": [
{
"ErrorCode": 0,
"ErrorMessage": null,
"FieldName": "MultiChoiceColumn",
"FieldValue": "['ValueA','ValueB']",
"HasException": false,
"ItemId": 0
},
{
"ErrorCode": 0,
"ErrorMessage": null,
"FieldName": "Id",
"FieldValue": "38",
"HasException": false,
"ItemId": 0
}
]
}
}
field values returned:
[
{
ErrorCode: 0,
ErrorMessage: null,
FieldName: 'MultiChoiceColumn',
FieldValue: "['ValueA','ValueB']",
HasException: false,
ItemId: 0
},
{
ErrorCode: 0,
ErrorMessage: null,
FieldName: 'Id',
FieldValue: '38',
HasException: false,
ItemId: 0
}
]
Id returned by AddValidateUpdateItemUsingPath: [object Object]
Existing access token eyJ0eXAiOiJKV1Q Returning...
Request:
{
"url": "https://mysite.sharepoint.com/sites/MySite/_api/web/lists/getByTitle('MyList')/items(38)",
"method": "get",
"headers": {
"common": {
"Accept": "application/json, text/plain, /"
},
"delete": {},
"get": {},
"head": {},
"post": {
"Content-Type": "application/x-www-form-urlencoded"
},
"put": {
"Content-Type": "application/x-www-form-urlencoded"
},
"patch": {
"Content-Type": "application/x-www-form-urlencoded"
},
"user-agent": "NONISV|SharePointPnP|CLIMicrosoft365/5.8.0",
"accept-encoding": "gzip, deflate",
"accept": "application/json;odata=nometadata",
"authorization": "Bearer eyJ0eXAiO"
},
"responseType": "json",
"decompress": true
}
Response:
{
"url": "https://mysite.sharepoint.com/sites/MySite/_api/web/lists/getByTitle('MyList')/items(38)",
"status": 200,
"statusText": "OK",
"headers": {
"cache-control": "private, max-age=0",
"transfer-encoding": "chunked",
"content-type": "application/json;odata=nometadata;streaming=true;charset=utf-8",
"expires": "Sat, 29 Oct 2022 19:34:28 GMT",
"last-modified": "Sun, 13 Nov 2022 20:34:28 GMT",
"etag": ""08032b92-ce24-48a8-badd-8d5ccf9a0f5a,1"",
"vary": "Origin,Accept-Encoding",
"p3p": "CP="ALL IND DSP COR ADM CONo CUR CUSo IVAo IVDo PSA PSD TAI TELo OUR SAMo CNT COM INT NAV ONL PHY PRE PUR UNI"",
"x-networkstatistics": "0,525568,0,0,347096,0,286440",
"x-sharepointhealthscore": "2",
"x-sp-serverstate": "ReadOnly=0",
"dataserviceversion": "3.0",
"spclientservicerequestduration": "48",
"x-aspnet-version": "4.0.30319",
"x-databoundary": "None",
"x-1dscollectorurl": "https://eu-mobile.events.data.microsoft.com/OneCollector/1.0/",
"x-ariacollectorurl": "https://eu-mobile.events.data.microsoft.com/Collector/3.0",
"sprequestguid": "034e78a0-e05d-5000-5c7a-c87114a1b32b",
"request-id": "034e78a0-e05d-5000-5c7a-c87114a1b32b",
"ms-cv": "oHhOA13gAFBceshxFKGzKw.0",
"strict-transport-security": "max-age=31536000",
"x-frame-options": "SAMEORIGIN",
"content-security-policy": "frame-ancestors 'self' teams.microsoft.com *.teams.microsoft.com *.skype.com *.teams.microsoft.us local.teams.office.com *.powerapps.com *.yammer.com *.officeapps.live.com *.office.com *.stream.azure-test.net *.microsoftstream.com *.dynamics.com *.microsoft.com securebroker.sharepointonline.com;",
"x-powered-by": "ASP.NET",
"microsoftsharepointteamservices": "<IP_ADDRESS>26",
"x-content-type-options": "nosniff",
"x-ms-invokeapp": "1; RequireReadOnly",
"x-cache": "CONFIG_NOCACHE",
"x-msedge-ref": "Ref A: 7DE0D3DDFB0A4690B9E275B8B2D330A7 Ref B: BER30EDGE0519 Ref C: 2022-11-13T20:34:28Z",
"date": "Sun, 13 Nov 2022 20:34:27 GMT",
"connection": "close"
},
"data": {
"FileSystemObjectType": 0,
"Id": 38,
"ServerRedirectedEmbedUri": null,
"ServerRedirectedEmbedUrl": "",
"ID": 38,
"ContentTypeId": "0x0100F693387DE588C84A9A0259B7C22F6E5A000FCCF5C9E50EE6468B6051FE5C02E290",
"Title": null,
"Modified": "2022-11-13T20:34:28Z",
"Created": "2022-11-13T20:34:28Z",
"AuthorId": 10,
"EditorId": 10,
"OData__UIVersionString": "1.0",
"Attachments": false,
"GUID": "67820435-6824-4eb4-83b1-3e2df4e4576d",
"ComplianceAssetId": null,
"MultiChoiceColumn": [
"['ValueA','ValueB']"
],
}
}
CLI for Microsoft 365 version
v5.8.0
nodejs version
v18.11.0
Operating system (environment)
Windows
Shell
PowerShell
cli doctor
{
"os": {
"platform": "win32",
"version": "Windows 10 Enterprise",
"release": "10.0.22621"
},
"cliVersion": "5.8.0",
"nodeVersion": "v18.11.0",
"cliAadAppId": "31359c7f-bd7e-475c-86db-fdb8c937548e",
"cliAadAppTenant": "common",
"authMode": "DeviceCode",
"cliEnvironment": "",
"cliConfig": {},
"roles": [],
"scopes": [
"AllSites.FullControl",
"AppCatalog.ReadWrite.All",
"AuditLog.Read.All",
"Bookings.Read.All",
"ChannelMember.ReadWrite.All",
"ChannelMessage.Read.All",
"ChannelMessage.Send",
"ChannelSettings.ReadWrite.All",
"Chat.Read",
"Chat.ReadWrite",
"Directory.AccessAsUser.All",
"Directory.ReadWrite.All",
"ExternalConnection.ReadWrite.All",
"Group.ReadWrite.All",
"IdentityProvider.ReadWrite.All",
"Mail.ReadWrite",
"Mail.Send",
"Notes.Read.All",
"Place.Read.All",
"Policy.Read.All",
"Reports.Read.All",
"SecurityEvents.Read.All",
"ServiceHealth.Read.All",
"ServiceMessage.Read.All",
"ServiceMessageViewpoint.Write",
"Tasks.ReadWrite",
"Team.Create",
"TeamMember.ReadWrite.All",
"TeamsAppInstallation.ReadWriteForUser",
"TeamSettings.ReadWrite.All",
"TeamsTab.ReadWrite.All",
"TermStore.ReadWrite.All",
"User.Invite.All",
"User.ReadWrite.All",
"profile",
"openid",
"email",
"AllSites.FullControl",
"AppCatalog.ReadWrite.All",
"AuditLog.Read.All",
"Bookings.Read.All",
"ChannelMember.ReadWrite.All",
"ChannelMessage.Read.All",
"ChannelMessage.Send",
"ChannelSettings.ReadWrite.All",
"Chat.Read",
"Chat.ReadWrite",
"Directory.AccessAsUser.All",
"Directory.ReadWrite.All",
"ExternalConnection.ReadWrite.All",
"Group.ReadWrite.All",
"IdentityProvider.ReadWrite.All",
"Mail.ReadWrite",
"Mail.Send",
"Notes.Read.All",
"Place.Read.All",
"Policy.Read.All",
"Reports.Read.All",
"SecurityEvents.Read.All",
"ServiceHealth.Read.All",
"ServiceMessage.Read.All",
"ServiceMessageViewpoint.Write",
"Tasks.ReadWrite",
"Team.Create",
"TeamMember.ReadWrite.All",
"TeamsAppInstallation.ReadWriteForUser",
"TeamSettings.ReadWrite.All",
"TeamsTab.ReadWrite.All",
"TermStore.ReadWrite.All",
"User.Invite.All",
"User.ReadWrite.All"
]
}
Additional Info
No response

Hi @AlexJPawlak thank you for reporting this issue.
We'll have a look at it.

Hi @AlexJPawlak I just checked it. Apparently this is by design by the API we are using. The way you should add multi choice fields is by passing a value like this: Choice 1;#Choice 2;#Choice 3.
Can you check if this works for you? Maybe it's a good idea to add this to our documentation file. Therefore I shall add it.

Hey thanks!
That seems to have helped. Sharepoint API seems not so straightforward, I think it's the easiest to look up browser payloads in future
Best regards

I think it's the easiest to look up browser payloads in future.

Indeed, that's what I did 😊.
However we can't expect our users to do that, so a better way is us adding an example to the docs for every field type.

Yep. Thanks, it seems all resolved then :-)


Adding touch icons

Fixes #14

Doesn't seem to be loading the icon when I save the webpage to homescreen on my IPhone 6. Is it working on yours?

Hmm, I just tested the "Add to Home Screen" and it worked for me. I also see it in the Safari address bar drop-down and on my desktop Safari "Favorites" screen.
I did find that the icon (or lack of one) seems to stay cached for quite some time, so wait for a while and see.


Actually release v0.7.0

Things are a bit stuck at the moment. I've locked the embedded-hal library to exactly 0.2.2 to avoid warnings about using deprecated functions until the Linux Embedded HAL catches up (I hit some problems with passing a None:: into the constructor there.
I'm also stuck due to a library problem between nix and libc that may require me to either backport/freeze some libraries or to wait until every dependency that requires the three different versions of the nix crate are satisfied.
The big change that embedded folks will depend on is in #16. For now, I think they'll have to rely on using this Git repository directly instead of Crates.io.

Nix has been updated! I just need to run some tests to make sure everything is looking good and the ball can get rolling.


ATSAML21E18B fails to generate

When I try to compile the code generated from this SVD file: ATSAML21E18B.zip
With this procedure:

cargo init --lib
cargo add bare-metal vcell cortex-m
echo "max_width = 10000" >> rustfmt.toml to prevent the line length errors
svd2rust -i ATSAML21E18B.svd | rustfmt | tee src/lib.rs
cargo build

I get the following errors:
error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66240:21
      |
66240 |     register_block: sercom0::RegisterBlock,
      |                     ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66243:19
      |
66243 |     type Target = sercom0::RegisterBlock;
      |                   ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66244:25
      |
66244 |     fn deref(&self) -> &sercom0::RegisterBlock {
      |                         ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66252:21
      |
66252 |     register_block: sercom0::RegisterBlock,
      |                     ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66255:19
      |
66255 |     type Target = sercom0::RegisterBlock;
      |                   ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66256:25
      |
66256 |     fn deref(&self) -> &sercom0::RegisterBlock {
      |                         ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66264:21
      |
66264 |     register_block: sercom0::RegisterBlock,
      |                     ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66267:19
      |
66267 |     type Target = sercom0::RegisterBlock;
      |                   ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66268:25
      |
66268 |     fn deref(&self) -> &sercom0::RegisterBlock {
      |                         ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66276:21
      |
66276 |     register_block: sercom0::RegisterBlock,
      |                     ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66279:19
      |
66279 |     type Target = sercom0::RegisterBlock;
      |                   ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66280:25
      |
66280 |     fn deref(&self) -> &sercom0::RegisterBlock {
      |                         ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66288:21
      |
66288 |     register_block: sercom0::RegisterBlock,
      |                     ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66291:19
      |
66291 |     type Target = sercom0::RegisterBlock;
      |                   ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `sercom0`
     --> src/lib.rs:66292:25
      |
66292 |     fn deref(&self) -> &sercom0::RegisterBlock {
      |                         ^^^^^^^ Use of undeclared type or module `sercom0`

error[E0433]: failed to resolve. Use of undeclared type or module `tc0`
     --> src/lib.rs:79227:21
      |
79227 |     register_block: tc0::RegisterBlock,
      |                     ^^^ Use of undeclared type or module `tc0`

error[E0433]: failed to resolve. Use of undeclared type or module `tc0`
     --> src/lib.rs:79230:19
      |
79230 |     type Target = tc0::RegisterBlock;
      |                   ^^^ Use of undeclared type or module `tc0`

error[E0433]: failed to resolve. Use of undeclared type or module `tc0`
     --> src/lib.rs:79231:25
      |
79231 |     fn deref(&self) -> &tc0::RegisterBlock {
      |                         ^^^ Use of undeclared type or module `tc0`

error[E0433]: failed to resolve. Use of undeclared type or module `tc0`
     --> src/lib.rs:79239:21
      |
79239 |     register_block: tc0::RegisterBlock,
      |                     ^^^ Use of undeclared type or module `tc0`

error[E0433]: failed to resolve. Use of undeclared type or module `tc0`
     --> src/lib.rs:79242:19
      |
79242 |     type Target = tc0::RegisterBlock;
      |                   ^^^ Use of undeclared type or module `tc0`

error[E0433]: failed to resolve. Use of undeclared type or module `tc0`
     --> src/lib.rs:79243:25
      |
79243 |     fn deref(&self) -> &tc0::RegisterBlock {
      |                         ^^^ Use of undeclared type or module `tc0`

error: aborting due to 21 previous errors

I have tested the same procedure with this SVD file without issue.

That sounds like #107: missing <cluster> support.

Yep, sure does?

@nigelb Could you please try this with the current master? Cluster support was added, but I know some ATSAMD chips still have issued due to other problems.
If so, lets figure out which other reported issues are blocking you.

Hi @jamesmunns I have the same issue as #191 :
$ svd2rust.exe -V
svd2rust 0.12.0 (631ab3e 2018-03-09)

$ svd2rust -i ATSAML21E18B.svd
WARNING Some(Ident("mode1")) overlaps with another register block at offset 0. Ignoring.
WARNING Some(Ident("mode2")) overlaps with another register block at offset 0. Ignoring.
error: Cluster USART has no determinable `size` field
caused by: Warning! overlap while calculating Register Size within a Cluster! Cluster contents may be incorrectly aligned!
note: run with `RUST_BACKTRACE=1` for a backtrace

Thanks,
Nigel

Thanks for confirming @nigelb, I'd say follow that issue as @wez is working on a fix for it. We can keep this open to track your specific chip. I will update the title to represent this

should be fixed


QtAndroidExtras : Call Java from Qt/QML

http://doc.qt.io/qt-5/qtandroidextras-index.html
http://stackoverflow.com/a/27762416
http://stackoverflow.com/questions/33407883/how-to-build-cmake-based-project-for-android-ios-using-qtcreator
#include <QtAndroidExtras>

TOOD: Find working CMake example of QtAndroidExtras
Adding Java to a CMake based Qt project seems non trivial.
@ruslo: Have you come across any CMake use of QtAndroidExtras?

Closing old issue.


Improved UI of the form in patient portal

#210 issue resolved
This PR improves the UI of Patient Portal
I have improved the UI of the form also added hover effects.
Screenshots of updated UI:

I declare that:

The content I am submitting is original and has not been plagiarized.
No portion of the work has been copied from any other source without proper attribution.
The work has been checked for plagiarism, and I assure its authenticity.

[ ] I have updated my branch and synced it with project main branch before making this PR
[ ] Is this a bug fix/enhancement/documentation changes
[ ] Part of GSSOC
[ ] Tested for any breaking changes
[ ] Other relevant checks completed

I understand that any violation of this undertaking may have legal consequences that I will bear and could result in the withdrawal of any recognition associated with the work.

[ ] I Agree

Kindly add this box below the heading

Ok

I have made the changes suggested

Resolve conflicts

@Wafmulla any updates on this? LGTM with incorporating the @Anishkagupta004 's suggestions

No activity


@imports marked as unused

🔎 Search Terms
@import noUnused
🕗 Version & Regression Information

I was unable to test this on prior versions because it uses @import

⏯ Playground Link
No response
💻 Code
This requires multiple files, so the TS playground won't work. Sorry.
// bar.js
/** @import {foo} from "foo"; */

/**
 * @param baz {foo}
 */
function bar(baz) {}

With this in the TSConfig
"noUnusedLocals": true,
"noUnusedParameters": true,

🙁 Actual behavior
Foo is marked as unused.
It's being used in a JSDoc
🙂 Expected behavior
It shouldn't be marked as unused.
Additional information about the issue
This doesn't appear all the time, usually when there's multiple imports.
The example doesn't actually error, the code erroring got force-pushed away. However, it's the general issue.
I thought it might need a type qualifier, but that doesn't seem to be valid.

Oh, I didn't look at PR comments. I think this still needs an issue though: https://github.com/microsoft/TypeScript/pull/57207#issuecomment-2148552262

Duplicate of #58368.


B4 - Application authority config

When configuring the Application authority, could we use aadAppOAuthAuthority instead of aadAppOAuthAuthority so that we don't need to manually concatenate the tenantId to get the full authority (authority: ${config.aadAppOauthAuthorityHost}/${config.aadAppTenantId}``)?

Good catch :) thank you!


feat: enable debug apis by default

Motivation

https://github.com/ChainSafe/lodestar/issues/6822

Description
Enable debug apis by default, see referenced issue for rationale.
Closes https://github.com/ChainSafe/lodestar/issues/6822

Consensus on today's standup is that we would feel a lot more comfortable to enable by default only if we had DOS protection measures in place. Something like #6838 where we have protection measures and adding a CLI flag disabling certain endpoints/functionality.
It was also suggested that we should make our documentation note more prominent about having to manually turn on debug API. Argument is that experienced power users of Lodestar will be able to enable it via flag rather than burdening inexperienced users with exposing this risk by default.

Consensus on today's standup is that we would feel a lot more comfortable to enable by default only if we had DOS protection measures in place

After watching the recording and what was discussed there, it feels to me more like a misunderstanding of the current situation. Enabling debug routes by default does not introduce any new DoS vector as the same can already be achieved by calling getStateValidators api which is part of beacon namespace.

Something like https://github.com/ChainSafe/lodestar/issues/6838 where we have protection measures and adding a CLI flag disabling certain endpoints/functionality.

Whether or not we implement a solution for #6838 is not relevant for this PR. The issue is meant to address protecting public beacon nodes which have debug namespace enabled explicitly already.

rather than burdening inexperienced users with exposing this risk by default.

If operators / stakers expose their beacon api publicly due to misconfiguration, having their node go down due to oom is the least of their worries. Please see  https://github.com/ChainSafe/lodestar/issues/6822#issuecomment-2135504604. and just in general, enabling debug endpoints by default doesn't introduce any new risks, as mentioned multiple times (happy to be proven otherwise)

It was also suggested that we should make our documentation note more prominent about having to manually turn on debug API. Argument is that experienced power users of Lodestar will be able to enable it via flag

Our client should just work by default, people trying to use ethdo or other tooling that requires debug routes might not be advanced users that know about these different api namespaces. I've seen plenty of users facing this issue with Lodestar specifically because all other clients enable the debug namespace by default already. There was even discussion on the beacon-api repo to move it out of debug namespace (https://github.com/ethereum/beacon-APIs/pull/357) but it was closed due to friction this would create changing the path, not because it would introduce a risk.
As a side note, a lot of tooling (e.g. eth-docker) already enables debug by default (ref) because of the UX degradation mentioned above of having the user figure this out themselves.

Consensus on today's standup is that we would feel a lot more comfortable to enable by default only if we had DOS protection measures in place

After watching the recording and what was discussed there, it feels to me more like a misunderstanding of the current situation. Enabling debug routes by default does not introduce any new DoS vector as the same can already be achieved by calling getStateValidators api which is part of beacon namespace.

Makes sense.  I thought getting the state was the only route that causes an issue.

Something like #6838 where we have protection measures and adding a CLI flag disabling certain endpoints/functionality.

Whether or not we implement a solution for #6838 is not relevant for this PR. The issue is meant to address protecting public beacon nodes which have debug namespace enabled explicitly already.

Also makes sense.

rather than burdening inexperienced users with exposing this risk by default.

If operators / stakers expose their beacon api publicly due to misconfiguration, having their node go down due to oom is the least of their worries. Please see #6822 (comment). and just in general, enabling debug endpoints by default doesn't introduce any new risks, as mentioned multiple times (happy to be proven otherwise)

I tend to lean towards this as an issue but truth be told, it can be solved with documentation.  I also tend to think that the single-threaded nature of JS causes more risk than just OOM.  Large api requests halt the world for everything else so its also worth noting this in the docs if we turn this on by default.

It was also suggested that we should make our documentation note more prominent about having to manually turn on debug API. Argument is that experienced power users of Lodestar will be able to enable it via flag

Our client should just work by default, people trying to use ethdo or other tooling that requires debug routes might not be advanced users that know about these different api namespaces. I've seen plenty of users facing this issue with Lodestar specifically because all other clients enable the debug namespace by default already.

Agreed.  I have noticed a lot of issues related to this and I suppose the UX of having it on by default may sway my opinion considering the discussion above.

There was even discussion on the beacon-api repo to move it out of debug namespace (ethereum/beacon-APIs#357) but it was closed due to friction this would create changing the path, not because it would introduce a risk.

Yes, but this was what lighthouse mentioned and this is very much not the case for us....  The node stops with a 400mb api response.  https://github.com/ethereum/beacon-APIs/pull/357#issuecomment-1742634965

As a side note, a lot of tooling (e.g. eth-docker) already enables debug by default (ref) because of the UX degradation mentioned above of having the user figure this out themselves.

I tend to see this in a new light but would like to put this thought forward, if the consumers are not seeing the note in the docs about turning on the debug namespace will they also miss the note about protecting one's node from attacks.
If we ensure that idea is front-and-center (even more prominently displayed in getting-started, on the readme, etc), that open apis are risky (should be common sense but that is definitely not so common) I suppose this will be a good change from a DX perspective...

getStateValidators

Ah yes, forgot about that terrible endpoint.
Are there any efforts to deprecate the worst offenders?
Noting that an exposed API is already a DoS vector, it seems ok to add the debug namespace by default.
I guess the hope would be that we could disable the worst endpoints / variants by default.
The hope is that an exposed API would go from terrible DoS vector (where on the order of 1 bad request blows up a node) to less-terrible DoS vector (where on the order of 1000 requests blow up the node).

Are there any efforts to deprecate the worst offenders?

There are efforts but since this api is required by a lot of infrastructure / tooling around the CL (and the VC itself) it is required to provide an alternative, if all offenders support ssz, we could at least disable JSON on those, see https://github.com/ethereum/beacon-APIs/pull/449 for potential solution.

The hope is that an exposed API would go from terrible DoS vector (where on the order of 1 bad request blows up a node) to less-terrible DoS vector (where on the order of 1000 requests blow up the node).

yeah that would the best outcome we can get if people wanna expose the beacon api directly. It will still be quite easy to DoS, if people wanna run a infrastructure provider like Infura for the CL, they will have to implement a caching layer and other protections either way.

:tada: This PR is included in v1.20.0 :tada:


Prevent webpack.DefinePlugin from overriding process.env object

Currently when production app is running, in the main process just one environment variable exists  - NODE_ENV. This change should prevent process.env object from being reset.

Can you explain why this code ensures that the env variable won't be changed?

It follows from the code of DefinePlugin. When some object passed there it will be transformed to JSON string which will be evaluated further. And original value will be replaced with the result of this evaluation. https://github.com/webpack/webpack/blob/master/lib/DefinePlugin.js#L27
At the same time, when you define some value of primitive type it will be added to existing object (or this parent object will be created).


Rust cross compile won't build

I am on Ubuntu trying to cross compile to x86_64-unknown-linux-musl so I can use Rust for an AWS Lambda runtime.
I am using reqwest, which depends on openssl, but I can't for the life of me get this thing to build. I have tried adding openssl as a dependency in Cargo.toml, as well as openssl-sys. I do have  libssl-dev installed.
I have tried setting env variables like this:
export OPENSSL_DIR="/usr/lib/x86_64-linux-gnu"
export OPENSSL_INCLUDE_DIR="/usr/include/openssl"
but still no luck :/ I have tried Googling and reading through all these issues for hours and I can't seem to find any different ideas.
My current error is this:
error: failed to run custom build command for 'openssl-sys v0.9.80'

Caused by:
  process didn't exit successfully: '/home/dmbluesmith/DevWork/Check-Author-Associations-Service/check-author-associations-service-app/lib/lambdas/checkAssociations/target/release/build/openssl-sys-7b966edf89eb27d4/build-script-main' (exit status: 101)
  --- stdout
  cargo:rustc-cfg=const_fn
  cargo:rustc-cfg=openssl
  cargo:rerun-if-env-changed=X86_64_UNKNOWN_LINUX_MUSL_OPENSSL_NO_VENDOR
  X86_64_UNKNOWN_LINUX_MUSL_OPENSSL_NO_VENDOR unset
  cargo:rerun-if-env-changed=OPENSSL_NO_VENDOR
  OPENSSL_NO_VENDOR unset
  cargo:rerun-if-env-changed=CC_x86_64-unknown-linux-musl
  CC_x86_64-unknown-linux-musl = None
  cargo:rerun-if-env-changed=CC_x86_64_unknown_linux_musl
  CC_x86_64_unknown_linux_musl = None
  cargo:rerun-if-env-changed=TARGET_CC
  TARGET_CC = None
  cargo:rerun-if-env-changed=CC
  CC = None
  RUSTC_LINKER = None
  cargo:rerun-if-env-changed=CROSS_COMPILE
  CROSS_COMPILE = None
  cargo:rerun-if-env-changed=CFLAGS_x86_64-unknown-linux-musl
  CFLAGS_x86_64-unknown-linux-musl = None
  cargo:rerun-if-env-changed=CFLAGS_x86_64_unknown_linux_musl
  CFLAGS_x86_64_unknown_linux_musl = None
  cargo:rerun-if-env-changed=TARGET_CFLAGS
  TARGET_CFLAGS = None
  cargo:rerun-if-env-changed=CFLAGS
  CFLAGS = None
  cargo:rerun-if-env-changed=CRATE_CC_NO_DEFAULTS
  CRATE_CC_NO_DEFAULTS = None
  DEBUG = Some("false")
  CARGO_CFG_TARGET_FEATURE = Some("fxsr,sse,sse2")
  running "perl" "./Configure" "--prefix=/home/dmbluesmith/DevWork/Check-Author-Associations-Service/check-author-associations-service-app/lib/lambdas/checkAssociations/target/x86_64-unknown-linux-musl/release/build/openssl-sys-edd1020990764309/out/openssl-build/install" "--openssldir=/usr/local/ssl" "no-dso" "no-shared" "no-ssl3" "no-unit-test" "no-comp" "no-zlib" "no-zlib-dynamic" "no-md2" "no-rc5" "no-weak-ssl-ciphers" "no-camellia" "no-idea" "no-seed" "no-engine" "no-async" "linux-x86_64" "-O2" "-ffunction-sections" "-fdata-sections" "-fPIC" "-m64" "-DOPENSSL_NO_SECURE_MEMORY"
  Configuring OpenSSL version 1.1.1t (0x1010114fL) for linux-x86_64
  Using os-specific seed configuration
  Creating configdata.pm
  Creating Makefile

  **********************************************************************
  ***                                                                ***
  ***   OpenSSL has been successfully configured                     ***
  ***                                                                ***
  ***   If you encounter a problem while building, please open an    ***
  ***   issue on GitHub <https://github.com/openssl/openssl/issues>  ***
  ***   and include the output from the following command:           ***
  ***                                                                ***
  ***       perl configdata.pm --dump                                ***
  ***                                                                ***
  ***   (If you are new to OpenSSL, you might want to consult the    ***
  ***   'Troubleshooting' section in the INSTALL file first)         ***
  ***                                                                ***
  **********************************************************************
  running "make" "depend"
  running "make" "build_libs"
  /usr/bin/perl "-I." -Mconfigdata "util/dofile.pl" \
      "-oMakefile" include/crypto/bn_conf.h.in > include/crypto/bn_conf.h
  /usr/bin/perl "-I." -Mconfigdata "util/dofile.pl" \
      "-oMakefile" include/crypto/dso_conf.h.in > include/crypto/dso_conf.h
  /usr/bin/perl "-I." -Mconfigdata "util/dofile.pl" \
      "-oMakefile" include/openssl/opensslconf.h.in > include/openssl/opensslconf.h
  make depend && make _build_libs
  make[1]: Entering directory '/home/dmbluesmith/DevWork/Check-Author-Associations-Service/check-author-associations-service-app/lib/lambdas/checkAssociations/target/x86_64-unknown-linux-musl/release/build/openssl-sys-edd1020990764309/out/openssl-build/build/src'
  make[1]: Leaving directory '/home/dmbluesmith/DevWork/Check-Author-Associations-Service/check-author-associations-service-app/lib/lambdas/checkAssociations/target/x86_64-unknown-linux-musl/release/build/openssl-sys-edd1020990764309/out/openssl-build/build/src'
  make[1]: Entering directory '/home/dmbluesmith/DevWork/Check-Author-Associations-Service/check-author-associations-service-app/lib/lambdas/checkAssociations/target/x86_64-unknown-linux-musl/release/build/openssl-sys-edd1020990764309/out/openssl-build/build/src'
  musl-gcc  -I. -Iinclude -fPIC -pthread -m64 -Wall -O3 -O2 -ffunction-sections -fdata-sections -fPIC -m64 -DOPENSSL_USE_NODELETE -DL_ENDIAN -DOPENSSL_PIC -DOPENSSL_CPUID_OBJ -DOPENSSL_IA32_SSE2 -DOPENSSL_BN_ASM_MONT -DOPENSSL_BN_ASM_MONT5 -DOPENSSL_BN_ASM_GF2m -DSHA1_ASM -DSHA256_ASM -DSHA512_ASM -DKECCAK1600_ASM -DRC4_ASM -DMD5_ASM -DAESNI_ASM -DVPAES_ASM -DGHASH_ASM -DECP_NISTZ256_ASM -DX25519_ASM -DPOLY1305_ASM -DOPENSSLDIR="\"/usr/local/ssl\"" -DENGINESDIR="\"/home/dmbluesmith/DevWork/Check-Author-Associations-Service/check-author-associations-service-app/lib/lambdas/checkAssociations/target/x86_64-unknown-linux-musl/release/build/openssl-sys-edd1020990764309/out/openssl-build/install/lib/engines-1.1\"" -DNDEBUG -DOPENSSL_NO_SECURE_MEMORY  -c -o apps/app_rand.o apps/app_rand.c
  make[1]: Leaving directory '/home/dmbluesmith/DevWork/Check-Author-Associations-Service/check-author-associations-service-app/lib/lambdas/checkAssociations/target/x86_64-unknown-linux-musl/release/build/openssl-sys-edd1020990764309/out/openssl-build/build/src'

  --- stderr
  /bin/sh: 1: musl-gcc: not found
  make[1]: *** [Makefile:671: apps/app_rand.o] Error 127
  make: *** [Makefile:175: build_libs] Error 2
  thread 'main' panicked at '

  Error building OpenSSL:
      Command: "make" "build_libs"
      Exit status: exit status: 2

The stderr message says it all, you haven't installed musl-gcc.  On Debian and derivatives, you need to install the package musl-tools.

Well, I definitely feel silly, but that fixed it! Thanks!


adding firebase-ios-sdk to Xcode Swift Packages, as well as depending on it in a local Swift Package causes packages to fail to resolve consistently.

[REQUIRED] Step 1: Describe your environment

Xcode version: 12.3
Firebase SDK version: 7.4.0 (also affects at least 7.3.x)
Installation method: Swift Package Manager
Firebase Component: Analytics, FirebaseCrashlytics, perhaps all.

[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
(See example project linked at the bottom)
adding firebase-ios-sdk to Xcode Swift Packages, as well as depending on it in a local Swift Package causes packages to fail to resolve consistently.
The Results:

artifact of binary target 'FirebaseAnalytics' failed extraction: The operation couldn’t be completed. (TSCBasic.StringError error 1.)
artifact of binary target 'GoogleAppMeasurement' failed extraction: The operation couldn’t be completed. (TSCBasic.StringError error 1.)

The (Workaround) Solution:
Some combination of closing Xcode, Resetting Package Cache, and Updating Package Dependencies can resolve it temporarily.
Relevant Code:
https://github.com/jondwillis/FirebaseSPMBug

Thanks for the report.
It's almost certainly a Swift Package Manager bug and I recommend reporting there also. It looks similar to https://forums.swift.org/t/problem-in-xcode-project-to-get-all-dependencies/42287.

Thanks for the report.
It's almost certainly a Swift Package Manager bug and I recommend reporting there also. It looks similar to https://forums.swift.org/t/problem-in-xcode-project-to-get-all-dependencies/42287.

@paulb777 Thanks, I agree. I added to the thread that you linked to. Overall the SPM<>Xcode integration seems quite buggy.

@paulb777 Thanks, I agree. I added to the thread that you linked to. Overall the SPM<>Xcode integration seems quite buggy.

Thanks @jondwillis. I would add the distinction about SPM <> Xcode integration bugginess specifically for binary packages.  The source package integration has been more stable.

Thanks @jondwillis. I would add the distinction about SPM <> Xcode integration bugginess specifically for binary packages.  The source package integration has been more stable.

@jondwillis Does Xcode 12.5 address this?

@paulb777 ...sort of! ... with some changes, thanks to improved Xcode-SPM error messaging.
For context, this was my local swift package's Package.swift:
    dependencies: [
        .package(url: "https://github.com/Quick/Quick.git", from: "3.0.0"),
        .package(url: "https://github.com/Quick/Nimble.git", from: "9.0.0"),
        .package(url: "https://github.com/firebase/firebase-ios-sdk", from: "7.4.0"),
    ],
    targets: [
        .target(
            name: "Analytics",
            dependencies: [
                .product(name: "FirebaseAnalytics", package: "Firebase"),
                .product(name: "FirebaseCrashlytics", package: "Firebase"),
            ]),
            ...

Without any changes to my example project in Xcode 12.5 beta, I received the following error when resolving packages:
unknown package 'Firebase' in dependencies of target 'Analytics'; valid packages are: 'Quick', 'Nimble', 'firebase-ios-sdk'

I decided to bump to version to 7.6.0 at this time, and remove the firebase dependency from my project's Swift packages. Then I tried changing the local dependency's dependencies package name to firebase-ios-sdk, e.g.:
..product(name: "FirebaseCrashlytics", package: "firebase-ios-sdk"),

Which allowed the dependency's dependency to resolve. However, when re-adding Firebase to my project's Swift package, I got another error:
product dependency 'FirebaseAnalytics' in package 'firebase-ios-sdk' not found

Seems circular! That then led me to the solution, removing the project's Firebase dependency again, then adding an explicit name to my local dependency's product dependencies, and re-adding my projects Firebase dependency (including in case the order here matters):
dependencies: [
        .package(url: "https://github.com/Quick/Quick.git", from: "3.0.0"),
        .package(url: "https://github.com/Quick/Nimble.git", from: "9.0.0"),
        .package(name: "Firebase", url: "https://github.com/firebase/firebase-ios-sdk", from: "7.6.0"),
    ],
    targets: [
        .target(
            name: "Analytics",
            dependencies: [
                .product(name: "FirebaseAnalytics", package: "Firebase"),
                .product(name: "FirebaseCrashlytics", package: "Firebase"),
            ]),

I updated my test project repo  with the working solution.
⚠ for future people, I did notice while going back and replaying these steps, the previous broken behavior appeared again unexpectedly, so maybe this needs to all happen in a really specific order, or can still occur transiently.

@jondwillis Thanks for sharing your journey and solution. I'm going to close since the sporadic functionality is almost certainly a Swift Package Manager and not specifically the Firebase implementation.


Olimex STM32-E407 board hangs after some time - ping_pong and int32_publisher app with UDP transport (ros:galactic)

Issue template

Hardware description: Olimex STM32-F407
RTOS: FreeRTOS
Installation type: micro_ros_setup
Version or commit hash: Galactic

Steps to reproduce the issue
Follow this tutorial:
docker run -it --net=host -v /dev:/dev --privileged ros:galactic
source /opt/ros/$ROS_DISTRO/setup.bash
mkdir microros_ws
cd microros_ws
git clone -b $ROS_DISTRO https://github.com/micro-ROS/micro_ros_setup.git src/micro_ros_setup
sudo apt update && rosdep update
rosdep install --from-path src --ignore-src -y
sudo apt-get install python3-pip
colcon build
source install/local_setup.bash
ros2 run micro_ros_setup create_firmware_ws.sh freertos olimex-stm32-e407
ros2 run micro_ros_setup configure_firmware.sh ping_pong -t udp -i <IP_ADDRESS> -p 8888
ros2 run micro_ros_setup build_firmware.sh
ros2 run micro_ros_setup flash_firmware.sh

Expected behaviour
Messages must be published without interruption.
Actual behavior

Messages are published but after a while, the board seems to hang (LEDs stop blinking), and no messages published.
This happens at random and is worsened when the timer timeout is set lower, i.e, at high publisher rates. We eventually want to run an application that publishes at at least 100Hz.
In my tests so far, the ping_pong example app (that publishes every 2 seconds) has stopped after around 1200s (based on the message timestamps on /microROS/ping). It is very hard to make this reproducable as it may or may not stop at all.
I also have this issue with the int32_publisher example when it is set to run at 100Hz.

Additional information
The last seen lines of log seen at the agent (ping_pong example) :
1646736973.873109] debug    | DataReader.cpp     | read_fn                  | [==>> DDS <<==]        | client_key: 0x00000000, len: 34, data:
0000: 50 03 00 00 40 9F 36 2B 16 00 00 00 31 38 35 34 37 37 34 36 38 30 5F 31 38 39 35 31 33 30 37 39
0020: 30 00
[1646736973.873148] debug    | DataWriter.cpp     | write                    | [** <<DDS>> **]        | client_key: 0x00000000, len: 34, data:
0000: 50 03 00 00 40 9F 36 2B 16 00 00 00 31 38 35 34 37 37 34 36 38 30 5F 31 38 39 35 31 33 30 37 39
0020: 30 00
[1646736973.873259] debug    | UDPv4AgentLinux.cpp | send_message             | [** <<UDP>> **]        | client_key: 0x2693D1FA, len: 46, data:
0000: 81 01 A5 01 09 01 26 00 00 14 00 06 50 03 00 00 40 9F 36 2B 16 00 00 00 31 38 35 34 37 37 34 36
0020: 38 30 5F 31 38 39 35 31 33 30 37 39 30 00
[1646736973.873331] debug    | UDPv4AgentLinux.cpp | send_message             | [** <<UDP>> **]        | client_key: 0x2693D1FA, len: 13, data:
0000: 81 00 00 00 0A 01 05 00 B4 01 00 00 80
[1646736975.854734] debug    | UDPv4AgentLinux.cpp | recv_message             | [==>> UDP <<==]        | client_key: 0x2693D1FA, len: 48, data:
0000: 81 80 B4 01 07 01 26 00 01 BF 00 05 52 03 00 00 40 9F 36 2B 16 00 00 00 31 36 34 38 39 32 37 33
0020: 38 33 5F 31 38 39 35 31 33 30 37 39 30 00 00 00
[1646736975.855176] debug    | DataReader.cpp     | read_fn                  | [==>> DDS <<==]        | client_key: 0x00000000, len: 34, data:
0000: 52 03 00 00 40 9F 36 2B 16 00 00 00 31 36 34 38 39 32 37 33 38 33 5F 31 38 39 35 31 33 30 37 39
0020: 30 00
[1646736975.855242] debug    | DataWriter.cpp     | write                    | [** <<DDS>> **]        | client_key: 0x00000000, len: 34, data:
0000: 52 03 00 00 40 9F 36 2B 16 00 00 00 31 36 34 38 39 32 37 33 38 33 5F 31 38 39 35 31 33 30 37 39
0020: 30 00
[1646736975.855295] debug    | UDPv4AgentLinux.cpp | send_message             | [** <<UDP>> **]        | client_key: 0x2693D1FA, len: 46, data:
0000: 81 01 A6 01 09 01 26 00 00 14 00 06 52 03 00 00 40 9F 36 2B 16 00 00 00 31 36 34 38 39 32 37 33
0020: 38 33 5F 31 38 39 35 31 33 30 37 39 30 00
[1646736975.855333] debug    | UDPv4AgentLinux.cpp | send_message             | [** <<UDP>> **]        | client_key: 0x2693D1FA, len: 13, data:
0000: 81 00 00 00 0A 01 05 00 B5 01 00 00 80

Hello @TanmayDeshmukh, is it possible for you to debug the application and check in which line is the code stopped? Is this a FreeRTOS assert or it is a hard fault?

@pablogs9 Is there maybe a tutorial for debugging through JTAG you could point me to?

No, we do not have any. It should be straightforward using opencd and marus25.cortex-debug

@TanmayDeshmukh
to debug with vscode as gdb frontend, add launch.json like the follow
{
            "name": "custom_stm32f767zi-stlink-dbg",
            "type": "cortex-debug",
            "request": "launch",
            "servertype": "stutil",
            "cwd": "${workspaceRoot}",
            "executable": "${workspaceRoot}/libs/custom_stm32f767zi/build/micro-ROS.elf",
            "runToEntryPoint": "appMain",
            "armToolchainPath": "${workspaceRoot}/toolchain/gcc-arm-none-eabi-8-2019-q3-update/bin",
            "svdFile": "${workspaceRoot}/.vscode/svd/STM32F767.svd",
        },

We managed to debug the app, and we found out that multiple threads died after some time, including initTask, ethernetif_set_link and the appMain. This is why the board stopped blinking and the publisher stopped. We were then stuck looping through the ethernetif_input function from ethernetif.c.
We looked into the bug/issue that @ZhenshengLee mentioned in this issue, and we increased the stack size value INTERFACE_THREAD_STACK_SIZE to 500, which seems to solve the issue for now. We will continue to test this.
We wanted to ask if there is a way to see stack overflow through the debugger?

@LiWeiAn  accoding to https://github.com/micro-ROS/freertos_apps/issues/96#issuecomment-1065019133
This can be closed.


Add support for TLSH?

Recently it has been suggested to remove ssdeep from Debian. According to the former ssdeep Debian package maintainer ssdeep has been superseded by TLSH. Would you be willing to add support for TLSH in dnstwist?

I've been considering switching to TLSH since it's been made public. Considering the fact it's now widely adopted I think it's about time. Let me look into that.

At first glance I find TLSH a bit more sensitive compared to ssdeep, but it's too soon to compare them in terms of accuracy.
Anyway, I added support for TLSH. For the time being, ssdeep will still be preferred, and TLSH used as a fallback in case the former is unavailable. This way it should be transparent for the end user and should avoid potential hiccups from introducing new or renaming existing command line arguments.

@elceef Thanks for adding support for TLSH. I've tried it and it seems to work smoothly. I have not done any detailed comparison but judging by looking at a few examples, it seems that TLSH provides systematically larger values than ssdeep.

TLSH support was added by commit 17d6fe7. Thus closing this issue. Thanks again for adding this feature.


Laravel 5.4 compatibility

Laravel 5.4 removed the Session::set() method as it was not intended for public use. This PR replaces the calls to Session::set() with calls to Session::put() to restore compatibility with current versions of Laravel.

Codecov Report

Merging #18 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##             master    #18   +/-   ##
=======================================
  Coverage       100%   100%
- Complexity        0     14   +14
=======================================
  Files             3      3
  Lines            38     38
=======================================
  Hits             38     38

Impacted Files
Coverage Δ
Complexity Δ

src/Middleware/Reauthenticate.php
100% <100%> (ø)
3 <0> (+3)
:arrow_up:

src/ReauthLimiter.php
100% <100%> (ø)
6 <0> (+6)
: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 6c14d0d...8a775d1. Read the comment docs.

@mpociot Hey there, It seem the latest tag is not available on Packagist.

@crynobone whoops, looks like the package was not automatically linked to packagist. Fixed it 👍


hostname predicate is not port agnostic

Hello SCGW team,
As a first time user of spring cloud gateway, I struggle for a bit of time not understanding why my basic route using hostname predicate wasn't working.
Its only after putting a break point in HostRoutePredicateFactory I start realising that the hostname predicate is not removing the port of the Host header, before doing the match condition.
I understand gateway would be expose on port 443 most of the time but as dev testing the gateway, I was exposing it under a different port.
I also understand now that the host predicate is just a 'host' header filtering and I was personally not aware that the port would be in there. Is there any value of not excluding the port from the match? Extending the javadoc maybe?
I won't be the only one I guess, doing this rookie mistake when exploring Spring cloud gateway.
Thanks!
Quentin

Not at the moment.  When specifying the URL of the route you need to specify the port if it is different than the one the gateway is running on.

"When specifying the URL of the route you need to specify the port if it is different than the one the gateway is running on."
In my case, the port wasn't different than the one the gateway is running on but still, I had to specify the port.

What was the port of the gateway and what port was it forwarded to?  Maybe you can provide a sample that demonstrates what you saw.

ok forget what I just said, I miss understood your previous statement. Was indeed my case

@qcastel FWIW here is what I am using
 - Header=Host, restapi\.test\.ultradns\.net(:\d+)?
basically making a port part optional and irrelevant


Select2 - Breaks onBlur validation

Using with Select2 means that changes to select2 objects aren't properly validated

A couple of hacks are required to make select2 and bootstrap work with this plugin:

Make sure to include select2-boostrap-css in your project.
Add the following styles:

.form-group.has-error .select2-selection {
    border-color:#a94442;
}

Add the following binding on select change event:

$('select').on('change',function() {
    $(this).valid();
})


Update safari extension

Description
Added fuse.js for fuzzy search
https://github.com/raycast/extensions/issues/13621
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@iwex Great addition!


Move 'join' SQL implementation to warehouse

Fix for the https://github.com/iterative/studio/issues/10602
In this PR:

do not generate multiple join SQL queries as it could be quite heavy for some warehouse implementations (e.g. ClickHouse, see related PR), if there is join (or union) found in chain, save results in temporary table and run chain from there. See implementation here.
move join implementation to warehouse to be able to tweak join (e.g. in ClickHouse, see related PR)
remove tqdm from save method as it was added in previous PR as an experimental and not really needed here. Questionable.

do not generate multiple join SQL queries as it could be quite heavy for some warehouse implementations (e.g. ClickHouse, see related PR), if there is join (or union) found in chain, save results in temporary table and run chain from there. See implementation here.

can we avoid this for now if we use partial join and such? (I'm worried that let's say next time we add BigQuery or something - we are replacing optimizer with our own engine - kinda replicating what DB should be doing) ? it's also not needed for SQLite, right?

can we avoid this for now if we use partial join and such? (I'm worried that let's say next time we add BigQuery or something - we are replacing optimizer with our own engine - kinda replicating what DB should be doing) ?

Good point! Let me update the PR.

it's also not needed for SQLite, right?

Yes... I was thinking how to make it warehouse-dependent but can not find a good way to do this easily. Let me think a bit more.

can we avoid this for now if we use partial join and such?

it's also not needed for SQLite, right?

Did some tests in SQLite.
Python script:
from datachain import DataChain, Column, ModelStore
from datachain.lib.webdataset_laion import WDSLaion, LaionMeta

ModelStore.register(LaionMeta)
ModelStore.register(WDSLaion)

images = DataChain.from_dataset("laion_wds")
meta_pq = DataChain.from_dataset("laion_pq")
meta_emd = DataChain.from_dataset("laion_emb")

images_with_meta = images.merge(
    meta_pq,
    on="laion.json.uid",
    right_on="uid",
    inner=True
)

result = images_with_meta.merge(
    meta_emd,
    on=["stem", "source.index"],
    right_on=["stem", "emd.index"],
    inner=True
).save("laion")

Existing datasets:
$ datachain dataset-stats laion_wds
Number of objects: 447567
Total objects size:   13.4G
$ datachain dataset-stats laion_pq
Number of objects: 2
Total objects size:  230.5M
$ datachain dataset-stats laion_emb
Number of objects: 1009874
Total objects size:    2.8P
$

Execution on main branch (without changes in this PR), one merge on three tables:
$ time python wds_merge.py
python wds_merge.py  53.56s user 79.61s system 39% cpu 5:34.64 total
$

Execution in current branch, two merges:
$ time python wds_merge.py
python wds_merge.py  7.78s user 41.17s system 36% cpu 2:12.94 total
$

It is 2,5 times faster than one merge on three tables in SQLite.

I'm worried that let's say next time we add BigQuery or something - we are replacing optimizer with our own engine - kinda replicating what DB should be doing

This is my main concern right now. Still looking for a proper solution to implement multiple joins separation based on warehouse type.
Also wanted to mention changes in Studio PR with join tables reorder will not works without this fix with separating joins 👀


Improvement: method overriding

Hi guys,
I often override methods because Django :rofl: I was wondering if Code can help me override methods which whispers me. Like if I hit let's say SHIFT + Enter onto whispered row it would paste the original method definition.
Example:
I type:
def get_a

I get whispered:

I hit SHIFT + Enter and I get

Thank you and I'm sorry if this is duplicated task. I've looked around but found nothing.

I think this very much depends on the language you are using to provide this kind of information. I know for example that in TS we now have a quick fix to implement an interface but I would also love to get this into IntelliSense when I type in the body of the class.

@bpasero On the TypeScript side, https://github.com/Microsoft/TypeScript/issues/7158 tracks returning inherited methods in the suggestion list. This suggestion itself would not fill in the full signature , but we could leverage typescript.useCodeSnippetsOnMethodSuggest to do this

For start (and I guess for 80% of cases) it would be cool enough just to make Code to write in the line it's whispering (just like in my screens).
Thank you wery much, please keep Code making better and better ;)

@grafa I think the best in this specific case is to create an issue in the Python extension you are using.

So I should create the issue for every possible language that can override methods?
There is really no way to implement feature in Code itself to be able to write in the current file when a keyboard shortcut is pressed on highlighted whispered item just like I've described in my first post?
It seems to me like a pretty much easy solution that solves the problem and is good enough for 99% cases.

@grafa Yes, I please open issues against the language where you would like to see this functionality. For Python, please file an issue against the Python extension: https://github.com/DonJayamanne/pythonVSCode/issues/new
Thanks


[suggestion] Add route to the build output

$ git push production master
Counting objects: 54, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (50/50), done.
Writing objects: 100% (54/54), 200.77 KiB | 0 bytes/s, done.
Total 54 (delta 22), reused 0 (delta 0)
-----> Building bemtfc...
-----> Ruby app detected
-----> Compiling Ruby/Rack
-----> Using Ruby version: ruby-2.2.0
-----> Installing dependencies using 1.7.12
       Running: bundle install --without development:test --path vendor/bundle --binstubs vendor/bundle/bin -j4 --deployment
       Fetching gem metadata from https://rubygems.org/..........

       Gems in the groups development and test were not installed.
       It was installed into ./vendor/bundle
       Bundle completed (11.13s)
       Cleaning up the bundler cache.

-----> Discovering process types
       Procfile declares types -> web
       Default process types for Ruby -> rake, console, web
-----> Compiled slug size is 18M
-----> Creating release...
=====> Application deployed
=====> Added default web=1 formation
To ssh://git@demo.localflynn.com:2222/bemtfc.git
 * [new branch]      master -> master

It would be nice to add something like
Visit your application at:
http://bemtfc.demo.localflynn.com

To the bottom of the output =)

:sparkles:

+1: I do this in my wrapper scripts, it'd be nice if the tool itself did it.

Flynn is unmaintained and our infrastructure will shut down on June 1, 2021. See the README for details.


RuntimeError: Could not run 'aten::normal_' with arguments from the 'DML' backend.

Environment

hardware & software
version

gpu: amd 6650XT
driver: 22.10.3

wsl2 ubuntu20.04
<IP_ADDRESS>-microsoft-standard-WSL2

python
3.8.10

pytorch-directml
1.8.0a0.dev220506

code
>>> import torch
>>> t1 = torch.Tensor([[1., 2.], [3., 4.]]).to("dml") # works well
>>> t2 = torch.randn_like(t1) # raise RuntimeError

ErrorMessage:
RuntimeError: Could not run 'aten::normal_' with arguments from the 'DML' backend. This could be because the operator doesn't exist for this backend, or was omitted during the selective/custom build process (if using custom build). If you are a Facebook employee using PyTorch on mobile, please visit https://fburl.com/ptmfixes for possible resolutions. 'aten::normal_' is only available for these backends: [CPU, BackendSelect, Named, AutogradOther, AutogradCPU, AutogradCUDA, AutogradXLA, AutogradNestedTensor, UNKNOWN_TENSOR_TYPE_ID, AutogradPrivateUse1, AutogradPrivateUse2, AutogradPrivateUse3, Tracer, Autocast, Batched, VmapMode].

CPU: registered at /home/vsts/work/1/s/build/aten/src/ATen/RegisterCPU.cpp:5926 [kernel]
BackendSelect: fallthrough registered at /home/vsts/work/1/s/aten/src/ATen/core/BackendSelectFallbackKernel.cpp:3 [backend fallback]
Named: fallthrough registered at /home/vsts/work/1/s/aten/src/ATen/core/NamedRegistrations.cpp:11 [kernel]
AutogradOther: registered at /home/vsts/work/1/s/torch/csrc/autograd/generated/VariableType_4.cpp:8795 [autograd kernel]
AutogradCPU: registered at /home/vsts/work/1/s/torch/csrc/autograd/generated/VariableType_4.cpp:8795 [autograd kernel]
AutogradCUDA: registered at /home/vsts/work/1/s/torch/csrc/autograd/generated/VariableType_4.cpp:8795 [autograd kernel]
AutogradXLA: registered at /home/vsts/work/1/s/torch/csrc/autograd/generated/VariableType_4.cpp:8795 [autograd kernel]
AutogradNestedTensor: registered at /home/vsts/work/1/s/torch/csrc/autograd/generated/VariableType_4.cpp:8795 [autograd kernel]
UNKNOWN_TENSOR_TYPE_ID: registered at /home/vsts/work/1/s/torch/csrc/autograd/generated/VariableType_4.cpp:8795 [autograd kernel]
AutogradPrivateUse1: registered at /home/vsts/work/1/s/torch/csrc/autograd/generated/VariableType_4.cpp:8795 [autograd kernel]
AutogradPrivateUse2: registered at /home/vsts/work/1/s/torch/csrc/autograd/generated/VariableType_4.cpp:8795 [autograd kernel]
AutogradPrivateUse3: registered at /home/vsts/work/1/s/torch/csrc/autograd/generated/VariableType_4.cpp:8795 [autograd kernel]
Tracer: registered at /home/vsts/work/1/s/torch/csrc/autograd/generated/TraceType_4.cpp:10651 [kernel]
Autocast: fallthrough registered at /home/vsts/work/1/s/aten/src/ATen/autocast_mode.cpp:250 [backend fallback]
Batched: registered at /home/vsts/work/1/s/aten/src/ATen/BatchingRegistrations.cpp:1016 [backend fallback]
VmapMode: registered at /home/vsts/work/1/s/aten/src/ATen/VmapModeRegistrations.cpp:37 [kernel]

And torch.gather meet the same question.
Expectation
if i try like this:
>>> import torch
>>> t1 = torch.Tensor([[1, 2], [3, 4]]).to("cpu")
>>> t2 = torch.randn_like(t1).to("dml")

it doesn't raise error.

Hi, please try with the latest released torch-directml. uninstall pytorch-directml and install torch-directml instead.


feat: allow not setting the spec.replicas when creating a deployment

Fixes #184
Signed-off-by: Matthias Riegler<EMAIL_ADDRESS>

It's a patch we have in an internal code-base since a while, non breaking and reduces a bit of the overhead


Support nodejs10.x

AWS lambda supports nodejs10.x; please support that option also in this plugin.

There's already a PR for this #78

This issue can be closed! This works great already.


Functional style binding for multiple input topics only creates one consumer group

Dear developers,
I have a working application that uses spring-cloud-stream functional style for input and output topics binding.
After deployed the application to dev environment I discovered some weird behaviour which I found to be best clarified in this thread.
Currently I have 2 bindings settings: one for spring.cloud.stream.kafka and the other one for spring.clould.stream.kafka.streams
For the spring.cloud.stream.kafka bindings the config looks like the following:
spring.cloud.stream:
  kafka.binder:
    brokers: localhost:9092
    autoCreateTopics: false
  bindings:
    processor-in-0:
      group: group.topic.0
      destination: input_topic_0
      consumer:
        concurrency: 12
    processor-in-1:
      group: group.topic.1
      destination: input_topic_1
      consumer:
        concurrency: 12
    processor-in-2:
      group: group.topic.2
      destination: input_topic_2
      consumer:
        concurrency: 12
    processor-out-0:
        destination: output_topic_0

For the spring.clould.stream.kafka.streams the config looks like the following:
spring.cloud.stream.kafka.streams:
  binder:
    brokers: localhost:9092
    autoCreateTopics: false
    configuration:
      schema.registry.url: mock://
      num.stream.threads: 12
  bindings:
    processor-in-0:
      consumer:
        applicationId: processor-app-0
    processor-in-1:
      consumer:
        applicationId: processor-app-1
    processor-in-2:
      consumer:
        applicationId: processor-app-2

Then the function as the spring bean that binds to these input topics:
@Bean
public Function<KStream<String, String>,
	Function<KStream<String, String>,
		Function<KStream<String, String>,
			KStream<String, String>>>> processor() {
    return stream0 -> stream1 -> stream2 {
        return ....
    };
}

As you can see that I've created a binding function "processor" that binds to 3 input topics and produce to 1 output topic.
After the application is started, I saw that 12 stream threads were created, this is the correct behaviour since I set the number of stream threads to be 12.
However in terms of the group creation, I only see "processor-app-0" being created and all 12 consumers have been assigned under this one group. Also this single group appears to have subscribed to all 3 input topics where I was intentionally wanting one consumer group per input topic.
So there are 2 issues:
The first issue is that the spring.cloud.stream.kafka.streams applicationId appears to have overridden the group name I set from the spring.cloud.stream.kafka bindings.
The second issue is that I do not see consumer group for "processor-app-1" and "processor-app-2" even though I've specifically defined them inside the spring.cloud.stream.kafka.streams bindings. After the application is deployed, there is only one consumer group created "processor-app-0" which appeared to be the applicationId from the kafka.streams binding for the first parameter. All the group.id I defined earlier inside the kafka bindings seem to be gone or overridden.
I'm wondering if this is the correct behaviour, if it is then did I do something wrong?

Hi @AttitudeL, First of all, when we are talking about Kafka Streams binder-based applications, properties prefixed with spring.cloud.stream.kafka.binder/bindings.* are completely irrelevant and the binder only takes into account spring.cloud.stream.kafka.streams.binder/bindings.*  with the exceptions mentioned here. With that, the group name set through spring.cloud.stream.kafka.bindings will not have any effect at all.
In Kafka Streams binder, each function gets a unique applicaiton.id and behind the scenes, this id is delegated to that function's StreamsConfig.  Kafka Streams require that each config is provided with its own applicaiton.id. In the binder, there is a one to one mapping between a function and the corresponding Kafka Streams StreamsConfig.  Therefore, it is by design, that you are seeing that the first application.id set through spring.cloud.stream.kafka.streams.bindings.processor-in-0.consumer.applicaitonId always takes effect and the others are ignored. You might as well use spring.cloud.stream.kafka.streams.binder.functions.processor.applicationId or if you only have a single function use spring.cloud.streams.kafka.streams.binder.applicationId. See the refdocs for more details on that.
This same function level application.id is used as the group.id for the consumer as well. Thus, what you are seeing is the expected behavior, i.e. the same consumer group is subscribed to all the input topics. If you want each input topic to be consumed by a different consumer group, then you have to split your function into 3 separate functions. This is the same behavior of how it works in the legacy StreamListener based processors as well.

Hi @sobychacko
I sincerely appreciate your fast reply. So as I suspected that it's expected behaviour.
However I still have a few questions that I'd like to clarify, hope you don't mind.
You mentioned that with kafka streams binding, spring.cloud.stream.kafka.binder are ignored. My question is that would destination and consumer.concurrency also be ignored in this case?
Since I was looking at the log I saw 12 consumers were created as per num.stream.threads: 12 property. I wonder if consumer.concurrency is ignored then is there a way to assign 12 threads per input topic for the kafka-streams binding?

@sobychacko sorry I think the yml format probably confused you.
The group is coming from spring.cloud.stream.bindings.processor-in-0.group instead of spring.cloud.stream.kafka.bindings. I wonder would this also be ignored?
Also I defined spring.cloud.stream.bindings.processor-in-0.destination and it seems to work. But I don't know if spring.cloud.stream.bindings.processor-in-0.consumer.concurrency will be ignored since I would like 12 threads for that specific topic.

@AttitudeL no problem. Anything defined at spring.cloud.stream.bindings.* will be honored, except for the group when it comes to Kafka Streams binder. There, we expect applicationId settings as I mentioned above which take precedence. It is recommended to not setting the group property on the same binding when you are using Kafka Streams binder and rely on providing the applicationId. You might get some inconsistent behavior if you set group and applicationId on the same binding.

@sobychacko thank you so much for the clarification! I really wish these types of info can be easily found. Regardless it’s all good now.
Please allow me to thank you again for all the efforts. All the best!


Do not wait for SSH keys if there is an external controller

After stop reconciling KubevirtCluster with external controller, the machine reconcile function is waiting for an SSH keys that are not set anymore, because the cluster reconcile is never called.
To release this block, this PR does two things:
First, it add condition to the machine reconcile, to not wait for SSH keys if there is an external controller.
Then, the implementation of the KubevirtMachineReconciler.reconcileDelete function requires an SSH key to build a new machine instance, while the key is not actually used in the deletion process. To ease that, this PR introduces a new version of the NewMachine function: the NewBasicMachine function. This function creates a new machine instance only with the fields needed for deletion. Then this new function is used in the NewMachine function to populate the common fileds, and in the KubevirtMachineReconciler.reconcileDelete function to return an instance with fields needed in the deletion process.
Signed-off-by: Alex Gradouski<EMAIL_ADDRESS>
What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release notes:

None

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

27 of 35 (77.14%)  changed or added relevant lines in 3 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage increased (+0.6%) to 42.267%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/kubevirt/machine.go
20
22
90.91%

controllers/kubevirtmachine_controller.go
6
12
50.0%

Files with Coverage Reduction
New Missed Lines
%

controllers/kubevirtmachine_controller.go
1
33.41%

Totals

Change from base Build<PHONE_NUMBER>:
0.6%

Covered Lines:
593

Relevant Lines:
1403

💛  - Coveralls

/ok-to-test

/retest

I'm working on a e2e test for external cluster usage right now. To exercise my test, i had to handle this ssh key logic already, which I posted in #83 which shows how i would approach it.
Whatever we do, i want to make sure the unit test from #83 is merged that we eventually get e2e logic covering this use case. I'm working on the e2e test case now.

Closing in favor of #83


Stick to resource controllers when possible

:warning: The following controllers contain actions outside of the 7 resource actions (index, create, store, show, edit, update, destroy).

[ ] app/Http/Controllers/AttendanceController.php

[ ] app/Http/Controllers/CommentController.php

[ ] app/Http/Controllers/CourseSkillController.php

[ ] app/Http/Controllers/EnrollmentController.php

[ ] app/Http/Controllers/EventController.php

[ ] app/Http/Controllers/LeadStatusController.php

Most controllers have already been reorganized to stay closer to resourceful structure.
The remaining classes are referenced in other issues and will be reworked along with other improvements.


Add E2E test suite

Add a ginkgo[1] based E2E test suite its dependencies.
Test checkup Job successful execution.
The E2E test is currently separated from the Makefile, and is executaed by:
cd tests
ginkgo

The test suite respects the following environment variables:
TEST_NAMESPACE - set the namespace on which to perform the tests
TEST_IMAGE - sets the image name and tag, on which to perform the tests
[1] https://onsi.github.io/ginkgo/

Change: Limit the linter to cmd and tests directories.
Change: Add a timeout to the linter.

Change:
Answered @EdDev's comments.
Aligned K8s dependencies to v0.25.5

Could you add a makefile target for e2e tests? suggestions:
make functest
make test/e2e

In the PR description I've mentioned that the E2E tests are currently separated from the Makefile.
I don't mind adding a target, but at the moment there won't be a github actions workflow for it.

Change: Add test-e2e target to Makefile.

Change:

Rebase
Create ServiceAccount, Role, RoleBinding and ConfigMap.
Point the checkup to the ConfigMap.
Test the ConfigMap data at checkup completion.

Change:

Move the permission setup to a dedicated function.
Add a DeferCleanup() after each object's successful creation.
Replaced two string literals with constants from the rbacv1 package.

Change: Answered @EdDev's comment.


bluesky-kafka v0.2.0

It is very likely that the current package version for this feedstock is out of date.
Notes for merging this PR:

Feel free to push to the bot's branch to update this PR if needed.
The bot will almost always only open one PR per version.
Checklist before merging this PR:

[ ] Dependencies have been updated if changed: see upstream
[ ] Tests have passed
[ ] Updated license if changed and license_file is packaged

Note that the bot will stop issuing PRs if more than 3 Version bump PRs generated by the bot are open. If you don't want to package a particular version please close the PR.
Here is a list of all the pending dependencies (and their versions) for this repo. The first package is the current feedstock package. Please double check all dependencies before merging.
Feedstock Packages Build Status

Repo
Build  Health
nsls2forge  PyPI  defaults  conda-forge  GitHub  Versions
Downloads

bluesky-kafka

This is a duplicate of #7 for some reason. @thomashopkins32 has ideas how to fix it. Closing this PR.


Integration missing more than 4 smart-plugs - recognises/displays 4 smartplugs, yet 8 are in DHCP and the Meross_lan config entry

Version of the custom_component
"meross_lan": {
"version": "5.0.4",
"requirements": []
}
Configuration
config_entry.yaml attached.  Note there are 8 x MSS310 smart-plug devices detected in the "store" section (and 1 lamp, which it correctly detects) which I presume is downloaded from the meross app/server
Screenshot of HA Ubiquiti DHCP table showing 8 Meross smartplugs - 4 recognised by Meross integration, and 4 which are not
Screenshot of HA  device list, showing 4 plus recgnisd by Ubiquiti and Meross, and 4 others only recognised by Uniquiti.
Describe the bug
I have 8 MSS310 smart-plugs on the network, but no matter how many times I power off or clear and re-pair the last 4, the integration only recognises the first 4.
When I cleared all data in the integration, deleted all the devices, deleted the hub and started again, it also auto-recognised the first four from the LAN, and stopped after 4. Seems there is a problem recognising more then 4 MSS310 devices.
Debug log
Attached debug log - includes turning one of the missing devices off, then on again 10 - 15 seconds later, to see if there are any events detected from the missing devices
[config_entry-meross_lan-1f051c2453a2b73c991d83679129b2ec.json.txt](https://github.com/krahabb/meross_lan/files/15156211/config_entry-meross_lan-1f051c2453a2b73c991d83679129b2ec.json.txt)
![HA devices table - 4 recognised, 4 not recognised by Meross integration](https://github.com/krahabb/meross_lan/assets/151645043/24fb8d59-a0bf-4456-8e63-528ba0c57d71)
![Meross 4smartplugs](https://github.com/krahabb/meross_lan/assets/151645043/df7d5ec7-b566-4ecb-9986-b834ce68052b)
[home-assistant_meross_lan_2024-04-30T00-21-45.849Z.log](https://github.com/krahabb/meross_lan/files/15156566/home-assistant_meross_lan_2024-04-30T00-21-45.849Z.log)

It could be the unrecognized entries are due to the devices mac addresses being out of the address ranges configured in meross_lan.
You can check (and eventually edit) the manifest.json file in meross_lan folder and see that it filters dhcp discoveries by mac address mask(s):
  "dhcp": [
    {"hostname": "*", "macaddress": "48E1E9*"},
    {"hostname": "*", "macaddress": "34298F1*"},
    {"registered_devices": true}
  ],

I've checked a bit of internet and seen that there's a new address range registered to Meross: C4:E7:AE* so I guess I should add that to the manifest too....
You could rightly check if this is the case by adding the relative entry in manifest.json and reload (restart HA)

I did consider the MAC thing - and checked that all devices have the same MAC prefix (which is one of the prefixes in that table). They are also connected to the same VLAN with IP addresses in the same range.
Screenshot from Ubiquiti showing all the MACs and connection parameters to the LAN.
Looks like the 4 that are recognised and the 4 that are not are all identical as far as LAN connectivity and MAC ranges are concerned - so I think that isn't the issue.

I have the same problem.
I had to setup my homeassistant from scratch and now only four devices (out of about 20) are recognized. I have about 16 mss710 in the network, and they do work perfectly in Homekit or Alexa.
They also worked in Homeassistant before. The system drive failed, so I replaced the drive ans stated from scratch.
Four different devices where detected right away, but that's it, nothing else.
(Two of them are 710, one 120b and one 110)
I will try to setup manually.

Seems like I am able to add the devices manually by IP address.
This is ok so I can ho on with the HA setup, but would be interesting to see, why the auto discovery failes.
Maybe too many devices :-)

Additional Hint: After adding a few plugs manually, some devices where discovered automatically.
I have now all the devices setup, a little bumpy road, but it works, so many thnks for the integration and the work behind it.

This is very hard to track down...I know HA DHCP component has a lot of caching/optimizations so it might get fooled somehow, meross_lan too might be buggy for the matter but, if it receives a DHCP discovery from HA core it should:

log a warning in case of any failure
either show you a device needing to be identified/configured (since the device key is unknown)
or show you a device needing final acknowledge since meross_lan already knew the key


WAQI Sensor not updating

Home Assistant release (hass --version):
0.37
Python release (python3 --version):
3.4.2
Component/platform:
WAQI (World Air Quality Information) sensor
Description of problem:
Sensor displays information from a week ago and is not updating.
Others reporting the same issue in forum:
https://community.home-assistant.io/t/waqi-not-updating-system/7473/4
Direct tests of API via https://wind.waqi.info/nsearch/station/Rahway always returns current results in JSON:
{"dt":"2.945028ms","term":"rahway","results":[{"s":{"a":"17","t":["2017-02-08 12:00:00","-0500"],"n":["Rahway PM, NewJersey"],"u":"usa/newjersey/rahway-pm"},"n":["Rahway PM, NewJersey, USA"],"x":3564,"c":"US","z":0}]}
But sensor shows results from 1/26/17 and hasn't changed since I implemented it on 2/4/17

Expected:
Sensor should update appropriately.
Problem-relevant configuration.yaml entries and steps to reproduce:
#
#
#  Air Quality Index
#
#

- platform: waqi
  locations:
    - Rahway

Traceback (if applicable):
No errors seen in log
**Additional info:**

I confirm there is an issue. I also just have set up this sensor and the collection date is January 28th...
No errors logged and direct test of API with url (as described above) gives the correct and up to date information.
Hope it can be solved....

Stopped updating here as well....

https://github.com/valentinalexeev/pwaqi/issues/4

Confirmed update in PR https://github.com/home-assistant/home-assistant/pull/5944 fixes this.


When the selected paths (endpoints) of the OpenAPI doesn't require authentication, Kiota should create plugins with auth object as none

Today Kiota creates all API plugins with auth "None".
We should validate whether the selected paths (endpoints) of the OpenAPI doesn't require authentication and if that's the case, create the auth object as "None".
If the OpenAPI description includes security scheme and the endpoints need authentication:
1 - We should validate the authentication type: https://github.com/microsoft/kiota/issues/5071 and
2 - Create the right auth object: https://github.com/microsoft/kiota/issues/5070
Auth object are required in the plugin manifest. So probably we need to implement those 3 together.

@maisarissi This is already the case by default since we always set type none today by default (placeholder from the early internal preview).
See the following example. Since there are already other issues capturing the work for when the auth is not anonymous, what other changes do you expect here?
{
  "$schema": "https://aka.ms/json-schemas/copilot-extensions/v2.1/plugin.schema.json",
  "schema_version": "v2.1",
  "name_for_human": "Repair Service",
  "description_for_human": "A simple service to manage repairs for various items",
  "description_for_model": "A simple service to manage repairs for various items",
  "contact_email"<EMAIL_ADDRESS>  "namespace": "Repairs",
  "capabilities": {
    "localization": {}
  },
  "functions": [
    {
      "name": "listRepairs",
      "description": "List all repairs"
    }
  ],
  "runtimes": [
    {
      "type": "OpenApi",
      "auth": {
        "type": "None"
      },
      "spec": {
        "url": "repairs-openapi.yml"
      },
      "run_for_functions": [
        "listRepairs"
      ]
    }
  ]
}

I do only expect that Kiota will validate the auth needed for calling all selected endpoints and generate the right thing.
I know we are already creating the auth as "None" as default. I just didn't know if we needed to add new validations/logic to create the "None" only when it makes sense.
If that's not the case, feel free to close this.

Here is my reflection, None being the default (especially when no information is provided), I believe we already have everything we need here.
The other authentication types are the "special cases" that need to update the code.
I'll go ahead and close this.


Build of 5.6.0 fails due to missing file.

Describe the issue
Can you reliably reproduce the issue?
Yes
If so, please list the steps to reproduce below:

Build dependencies.
Run autogen.sh

Expected behavior
autogen.sh to complete without errors and allow configure to be completed without errors and then make.
Actual behavior
Receive these error lines and autogen stops:
configure.ac:1559: error: required file 'params/Makefile.in' not found
Makefile.am:10: error: required directory ./params does not exist
src/Makefile.am: installing 'build-aux/depcomp'
autoreconf: automake failed with exit status: 1
What version of NEBULAPROJECT Core are you using?
Compiling 5.6.0
Machine specs:

OS: Ubuntu 20.04
CPU: 6 vcore VirtualBox vcpu
RAM: 12 GB
Disk size: 30GB
Disk Type (HD/SDD): NVMe SSD.

Thank you for looking into this.

5.6.1 has fixed the issue.  Thanks. :-)


Raw githack for GitLab is down today?

I just found that raw.githack.com for gitlab is down today...
Please check, my url is
https://glcdn.githack.com/imgfo/example/-/raw/master/imgfo/example-api-1.17.1.json

Thanks for the report and sorry for inconvenience. It has been fixed.