[CAE Workbook] Added new query widget and resolved minor parsing bugs

PR Checklist
Added new widget/query to show CAE support status filterable bby App and Resource
Minor query updates to existing template

Incorrect parsing over AuthenticationProcessingDetails logs leading to wrong data being shown in the workbook. Regex fixed
Typo change in column name
As per new PM guidance, only showing CAE data if IpSeenByRp is different and not empty

If adding or updating templates:

[X] post a screenshot of templates and/or gallery changes
[X] ensure your template has a corresponding gallery entry in the gallery folder
[ ] If you are adding a new template, add your team and template/gallery file(s) to the CODEOWNERS file. CODEOWNERS entries should be teams, not individuals
[X] ensure all steps have meaningful names
[X] ensure all parameters and grid columns have display names set so they can be localized
[X] ensure that parameters id values are unique or they will fail PR validation (parameter ids are used for localization)
[X] ensure that steps names are unique or they will fail PR validation (step names are used for localization)
[X] grep /subscription/ and ensure that your parameters don't have any hardcoded resourceIds or they will fail PR validation
[X] remove fallbackResourceIds and fromTemplateId fields from your template workbook or they will fail PR validation

Screenshots of Workbook:

@microsoft/azure-ad-workbooks : Could anyone from the team please review/approve this workbook? It has been approved by the logsAnalytics team already.

@karanb22 : Would be able to approve this PR?

@SarahBar : Thanks for the review. I appreciate all of the callouts. I definitely missed a few things that you did catch.

Change "IP Address mismatch seen by AAD and RP" section to Full
Updated Default range to 24 hours
Removed Users param since it would have created issues where we wouldn;t be able to spot IP mismatches. Thanks for explaining how the query works internally.
Set the default to All apps


Fix more highlighting bugs

Fixes #66682
Fixes #66486

Changed to:

Made [ not stop type-expecting:

Left for later:
Something else I found that hasn't been reported: Characters like + think they are unary when in a situation like if A+B because prev_text is if at that point in the logic, not A, and if is not a value keyword. There are other situations where this causes wrong highlighting, like the - thinks it's unary in func foo(f: float) -> void because prev_text is float at that point, which is a non-value keyword.
I still haven't figured out how to fix it, so I've left it out of this PR for now (although I did make ->'s - not get highlighted like a number). In general, the chain of checks if prev_text is a value keyword – null / INF  / NAN / self / true / false / PI / TAU – is very scuffed and should be revisited.
Would appreciate some suggestions on how to figure out whether the last thing was actually the keyword.
The strikethrough stuff has been fixed too.

This has been like the cartoon trope where a character is trying to block a leakage, but as soon as he blocks it, new leakages appear.

Thanks!


[Task] WeWorkApp message  is sent in groups

Description
now WeWorkApp can only send  to ALL , However, most scenarios need to be pushed to specific people at a fixed point。
Task List
The WeWorkApp now supports all pushes, and cannot be specified to push to the specified person.
Task 1: Add new types of tags, such as asset tags and alarm push tags.
Task 2: Add a specific tag for the message notification to push the specified person.
企微应用现在支持全部推送，无法指定推送给指定的人。
任务一：标签新增类型，如资产标签，告警推送标签。
任务二：消息通知新增推送指定标签，实现推送指定人员。

Description
now WeWorkApp can only send to ALL , However, most scenarios need to be pushed to specific people at a fixed point。
Task List
The WeWorkApp now supports all pushes, and cannot be specified to push to the specified person. Task 1: Add new types of tags, such as asset tags and alarm push tags. Task 2: Add a specific tag for the message notification to push the specified person.
企微应用现在支持全部推送，无法指定推送给指定的人。 任务一：标签新增类型，如资产标签，告警推送标签。 任务二：消息通知新增推送指定标签，实现推送指定人员。

Can you provide a case study?

Description
now WeWorkApp can only send to ALL , However, most scenarios need to be pushed to specific people at a fixed point。
Task List
The WeWorkApp now supports all pushes, and cannot be specified to push to the specified person. Task 1: Add new types of tags, such as asset tags and alarm push tags. Task 2: Add a specific tag for the message notification to push the specified person.
企微应用现在支持全部推送，无法指定推送给指定的人。 任务一：标签新增类型，如资产标签，告警推送标签。 任务二：消息通知新增推送指定标签，实现推送指定人员。

Can you provide a case study?
For example, there are three servers hosting 1, 2, and 3, and there are three administrators, users A, B, and C.
Host 1 alarms are pushed to user A,
host 2 alarms are pushed to users A and B,
and host 3 alarms are pushed to A, B, and C, like this。
Refer： https://developer.work.weixin.qq.com/document/path/90236
{
"touser" : "UserID1|UserID2|UserID3",
"toparty" : "PartyID1|PartyID2",
"totag" : "TagID1 | TagID2",
"msgtype" : "text",
"agentid" : 1,
"text" : {
"content" : "你的快递已到，请携带工卡前往邮件中心领取。\n出发前可查看<a href="http://work.weixin.qq.com">邮件中心视频实况，聪明避开排队。"
},
"safe":0,
"enable_id_trans": 0,
"enable_duplicate_check": 0,
"duplicate_check_interval": 1800
}


Additional UAT stability improvements (tower mutex, array bounds checks)

This is a rollup of stability improvements tested in conjunction with #420. Includes:

Mutex protection for an unprotected map[string]ADSBTower
Removes a currently unused products_last_minute map type
Array bounds checking on uatdecode.go DecodeUplink() function
Array bounds checking on the (now disabled) decodeAirmet() function

ADSBTowerMutex missed in parseInput().
Will just remove the products_last_minute code if we don't need it, otherwise we'll have the code cluttered with a bunch of commented code.

Thanks!

What do you think about showing products breakdown in recent UAT messages?
https://github.com/cyoung/stratux/blob/master/web/plates/status.html#L51-L61
MsgLog.Products isn't used, either. It was displaying at one point. Not all EFBs show this breakdown and there have been a few questions "am I receiving NEXRAD frames?" etc.

I'm all in favor of adding the product count. I regularly get reports from
users claiming that they're not getting any NEXRAD data. It would be great
if there was a status item that showed what had come in.
On Tue, May 31, 2016 at 7:32 AM, cyoung<EMAIL_ADDRESS>wrote:

What do you think about showing products breakdown in recent UAT messages?
https://github.com/cyoung/stratux/blob/master/web/plates/status.html#L51-L61
MsgLog.Products isn't used, either. It was displaying at one point. Not
all EFBs show this breakdown and there have been a few questions "am I
receiving NEXRAD frames?" etc.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/cyoung/stratux/pull/428#issuecomment-222674512, or mute
the thread
https://github.com/notifications/unsubscribe/AAVYPHob24tlcvi5YRA5WyCi7v5VDxPbks5qHCpagaJpZM4Io6yG
.

--
Steven Sokol
408 Camelot Drive
Liberty, MO 64068
mobile: +1<PHONE_NUMBER>
fax: +1<PHONE_NUMBER>


CURL output URL

in order to get the URL, use (curl https://aka.ms/downloadazcopy-v10-windows -MaximumRedirection 0 -ErrorAction silentlycontinue).headers.location
instead of
(curl https://aka.ms/downloadazcopy-v10-windows -MaximumRedirection 0 -ErrorAction silentlycontinue).RawContent

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

ID: 15911160-5ba2-fb0a-0b24-16b3857e20ce
Version Independent ID: d925bc9f-f825-2f82-168c-6c30d716b9ce
Content: Copy or move data to Azure Storage by using AzCopy v10
Content Source: articles/storage/common/storage-use-azcopy-v10.md
Service: storage
Sub-service: common
GitHub Login: @normesta
Microsoft Alias: normesta

@BakkerJan
Thanks for the feedback! We are currently investigating and will get back on this.

@BakkerJan thank you for the update!

I've updated the article and that change should appear live this afternoon. Thx again.

#please-close


Add a BuildSystemDelegate which supports notifications for build settings changes

Introduce a BuildSystemDelegate to handle notifications from the build system

SourceKitServer is the main delegate to process these notifications
Currently limited to changes in FileBuildSettings
Delegate informs the BuildSystem of files to watch via registerChangeWatching(for: URL) and unregisterChangeWatching(for: URL)
In the future we could have more integration for handling changes in dependencies

Handling changes in FileBuildSettings

SourceKitServer sends notifications to the internal LSPs informing them of any opened documents that have changes in their compiler flags

For clangd, we send a notification to update the compilation database
For SourceKit/sourcekitd we must close and reopen the file to force a new AST with the new compiler flags

Could you please squash this so we don't have a merge in the middle (or at least squash the changes up to and including the merge commit)?

We don't need to nail all of this down right away, but I'm wondering about the split of responsibilities between notification and settings method.

What is the expectation for the performance of calling settings(for:_:) after you get a notification? Can it ever still be slow? What about before getting a notification, such as on initial query?
Would it be reasonable to provide the settings right in the notification instead so you don't need to make another call?
Should that be the primary way to get settings, and you just always get an initial notification when you register?  That ways the standalone settings(for:_:) method is only intended for one-off requests, not to be mixed with notifications.
On the other hand, when you open a new document, it's nice to call settings(for:_:) and get initial settings before e.g. talking to sourcekitd, but maybe the real thing you want is to get the initial settings with a timeout so that if it's going to take a few seconds to load settings you just open the sourcekitd document without settings and update it when they're available.

Squashed, let me know if it looks OK.

We don't need to nail all of this down right away, but I'm wondering about the split of responsibilities between notification and settings method.

What is the expectation for the performance of calling settings(for:_:) after you get a notification? Can it ever still be slow? What about before getting a notification, such as on initial query?

That's a good point. What do you think? One option is for the  BuildSystem to return some placeholder flags and then fix them up later (by sending a notification). Alternatively the BuildSystem could block trying to resolve these, but who knows how long it could take.
I would assume that after a notification, the BuildSystem likely has the flags cached (unless they were invalidated - e.g. the BuildSystem no longer has a record of a file).

Would it be reasonable to provide the settings right in the notification instead so you don't need to make another call?

Yeah, this seems reasonable. Potentially an optional, where null means the BuildSystem no longer has a record of the file?

Should that be the primary way to get settings, and you just always get an initial notification when you register?  That ways the standalone settings(for:_:) method is only intended for one-off requests, not to be mixed with notifications.
On the other hand, when you open a new document, it's nice to call settings(for:_:) and get initial settings before e.g. talking to sourcekitd, but maybe the real thing you want is to get the initial settings with a timeout so that if it's going to take a few seconds to load settings you just open the sourcekitd document without settings and update it when they're available.

Yeah, it's unclear what to do here if the BuildSystem might take some time to load it. Maybe  settings(for:_:) can be shifted to be async (with a callback) to allow for this type of timeout?

One option is for the BuildSystem to return some placeholder flags and then fix them up later (by sending a notification).

I'm wary of using fallback settings in the interim, because it would cause us to create a semantic AST in sourcekitd that is almost certain to have errors. So you're wasting resources typechecking an AST, and you end up with bad diagnostics like failing to import every module.  I think you only want to use fallback settings when the build system doesn't know about the file.  You could instead open the document with no settings so that you get syntactic support right away.

Potentially an optional, where null means the BuildSystem no longer has a record of the file?

Seems reasonable.

Yeah, it's unclear what to do here if the BuildSystem might take some time to load it. Maybe settings(for:_:) can be shifted to be async (with a callback) to allow for this type of timeout?

Yeah, for settings(for:_:) it would be straightforward to timeout; I guess it's less obvious to me how we would coordinate that for a hypothetical design where we rely on getting an initial notification with settings from the delegate, since the delegate is more isolated from the query than a callback closure would be.

One option is for the BuildSystem to return some placeholder flags and then fix them up later (by sending a notification).

I'm wary of using fallback settings in the interim, because it would cause us to create a semantic AST in sourcekitd that is almost certain to have errors. So you're wasting resources typechecking an AST, and you end up with bad diagnostics like failing to import every module. I think you only want to use fallback settings when the build system doesn't know about the file. You could instead open the document with no settings so that you get syntactic support right away.

Potentially an optional, where null means the BuildSystem no longer has a record of the file?

Seems reasonable.

Yeah, it's unclear what to do here if the BuildSystem might take some time to load it. Maybe settings(for:_:) can be shifted to be async (with a callback) to allow for this type of timeout?

Yeah, for settings(for:_:) it would be straightforward to timeout; I guess it's less obvious to me how we would coordinate that for a hypothetical design where we rely on getting an initial notification with settings from the delegate, since the delegate is more isolated from the query than a callback closure would be.

As an alternative then, we could remove the settings(for:_:) and then let the build system notify the delegate when it has build settings for the request files. In the meantime the LSP would likely ignore requests in a given file and defer opening until settings are known? Or default to empty settings (would likely have errors in both Objective-C and Swift)
It's also worth noting that at the moment the BuildSystemList always gives fallback build settings if they may not be correct.

Or default to empty settings (would likely have errors in both Objective-C and Swift)

Empty settings for swift means it will be syntax-only, so no semantic errors like module import failures.  For clang I'm guessing clangd itself is going to choose fallback settings, but that's pretty hard to avoid.

Or default to empty settings (would likely have errors in both Objective-C and Swift)

Empty settings for swift means it will be syntax-only, so no semantic errors like module import failures. For clang I'm guessing clangd itself is going to choose fallback settings, but that's pretty hard to avoid.

So how does removing the settings(for:_:) and then letting the build system notify the delegate when it has build settings for the requested files sound? This will allow us to use empty arguments for Swift (but presumably have errors for C/C++/Objective-C), but I'm not sure how well it will work with the BuildSystemList due to the FallbackBuildSystem. If we want to support the BuildSystemList here we will probably have to modify things a bit.

So how does removing the settings(for:_:) and then letting the build system notify the delegate when it has build settings for the requested files sound?

This is my preference, provide the settings along with the notification, which may or may not ever come, and let the LSP service deal with lack of settings however it wants.
If the build system can offer temporary or fallback settings, that is nice but not a requirement and it can do it by sending separate notifications.

@swift-ci please test

So how does removing the settings(for:_:) and then letting the build system notify the delegate when it has build settings for the requested files sound?

This is my preference, provide the settings along with the notification, which may or may not ever come, and let the LSP service deal with lack of settings however it wants.

That seems fine for now, although I think we'll want to bring back a way to do a one-off request for settings for things like background indexing in the future.  But we can deal with it then.

That seems fine for now, although I think we'll want to bring back a way to do a one-off request for settings for things like background indexing in the future. But we can deal with it then.

If we make background indexing an operation supported by the build server then we don't need to get settings, we'll just request the build server to produce index data for certain files.

Good point.

So how does removing the settings(for:_:) and then letting the build system notify the delegate when it has build settings for the requested files sound?

This is my preference, provide the settings along with the notification, which may or may not ever come, and let the LSP service deal with lack of settings however it wants.
If the build system can offer temporary or fallback settings, that is nice but not a requirement and it can do it by sending separate notifications.

Do you think it would make sense for the registerFor... call to return a FileBuildSettings?? e.g. so the BuildSystem can easily return FileBuildSettings if it has them for the initial openDocument call? Otherwise I guess the BuildSystem could immediately trigger a notification if it has the flags and the LSP could still use them for the initial open call.

Do you think it would make sense for the registerFor... call to return a FileBuildSettings??

It's not clear to me there's particular benefit, it makes the interaction model a bit more complicated since the LSP will wait for both the register call to respond and for a possible notification. Since the LSP will wait for a response asynchronously anyway, we might as well make it so that it only waits for a notification,  so the usage model will be a bit more straightforward.

Do you think it would make sense for the registerFor... call to return a FileBuildSettings??

It's not clear to me there's particular benefit, it makes the interaction model a bit more complicated since the LSP will wait for both the register call to respond and for a possible notification. Since the LSP will wait for a response asynchronously anyway, we might as well make it so that it only waits for a notification, so the usage model will be a bit more straightforward.

Ah, that makes sense if there's some sort of async communication protocol that we'd need to wait for. But if the BuildSystem is inside SourceKit-LSP / there's a synchronous channel to get them, you could potentially wait for the register call to return something and then trigger the open.
e.g.
No placeholder args
openDocument(/foo/main.c)
registerForChangeNotifications(/foo/main.c) --> settings
send clangd flags and then open
Placeholder/temp args
openDocument(/foo/main.c)
registerForChangeNotifications(/foo/main.c)
Send open to the clangd (uses temp flags causing errors)
fileBuildSettingsChanged([/foo/main.c])
Send clangd proper flags --> now is accurate
But I agree, we can always change this later on

Initial fixes, still need to:

Remove settings(for:_:)
Fix up the Swift BuildSystem test
Add clangd BuildSystem test

@swift-ci please test

Tests added, is it ok if I remove the settings(for:_:) in a follow up PR? Think that one will require modifying the behavior of the BuildSystemList a bit.

@swift-ci please test

@swift-ci please test

@swift-ci please test

Ah looks like I need to merge with upstream to add support for the new BuildSystemBuildSystem from #151. Will do that tomorrow

OK, added support, tests should be good now

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test

@swift-ci please test


Poseidon v2.5

Here I collect the necessary changes for Poseidon v2.5. This is work in progress.
See https://github.com/poseidon-framework/poseidon2-schema/pull/42 for the discussion surrounding this upcoming release.

Codecov Report

Merging #25 (3e052be) into master (68b6543) will decrease coverage by 9.36%.
The diff coverage is 8.21%.

@@            Coverage Diff             @@
##           master      #25      +/-   ##
==========================================
- Coverage   77.43%   68.06%   -9.37%
==========================================
  Files           8        9       +1
  Lines         421      476      +55
==========================================
- Hits          326      324       -2
- Misses         95      152      +57

Impacted Files
Coverage Δ

R/janno_basic.R
34.61% <0.00%> (ø)

R/janno_upgrade.R
0.00% <0.00%> (ø)

R/janno_validate.R
83.76% <0.00%> (-4.67%)
:arrow_down:

R/janno_read.R
81.81% <50.00%> (+29.18%)
:arrow_up:

R/janno_process_age.R
95.65% <83.33%> (ø)

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 68b6543...3e052be. Read the comment docs.


FeatureDB - QC_transition_group_pass, QC_transition_pass are empty when component fails

Describe the bug
QC_transition_group_pass and QC_transition_pass columns in FeatureDB.csv either have a value of 1 or none. In the PivotTable report, these values are either 0 or 1. I believe the FeatureDB "pass" columns should be consistent and fill these entries with 0 as well, instead of leaving the entry blank.
Expected behavior
Passed components contain a value of 1, and failed components contain a value of 0.
data
You can view the QC_transition_group_pass and QC_transition_pass columns from the FeatureDB report from the LCMS_MRM_Unknowns example dataset: FeatureDB.csv
Version information

OS: Windows 10
Version: 1.15.0

I believe this should have been taken care of in one of our last releases.  Please get back to us if the problem still persists.


SCARD_E_INVALID_PARAMETER

The bug should be solved but still appears.
Downloaded the master branch, because i saw that the fix was merged and builded with cmake.
Just to be sure i also checked the modified date of smartcard_operations.c
which was 26-01-21 12;33 (3 hours ago) so that seems to be correct.
i clicked the check card button a few times resulting in the same error as far as i can see
Here's the log again:
log_freerdp.txt

@ShiZNizZLe tricky one. From the log I found a remaining issue, could you try https://github.com/akallabeth/FreeRDP/tree/smart_e_invalid ?

@ShiZNizZLe tricky one. From the log I found a remaining issue, could you try https://github.com/akallabeth/FreeRDP/tree/smart_e_invalid ?

build it with these steps again:
unzip FreeRDP-smart_e_invalid.zip
cd FreeRDP-smart_e_invalid/
ln -s packaging/deb/freerdp-nightly debian
sudo dpkg-buildpackage
log_freerdp.txt
btw this is the button i need to press to check if the card is inserted:

As you can see, it says:
card in reader = false
This is a self made program used wether to check a dll that we're using can read the card.
through windows it all works fine but when using the raspberry workstations we have this problem right here.

build it with these steps again:
unzip FreeRDP-smart_e_invalid.zip
cd FreeRDP-smart_e_invalid/
ln -s packaging/deb/freerdp-nightly debian
sudo dpkg-buildpackage
log_freerdp.txt
btw this is the button i need to press to check if the card is inserted:

As you can see, it says:
card in reader = false
This is a self made program used wether to check a dll that we're using can read the card.
through windows it all works fine but when using the raspberry workstations we have this problem right here.

are you sure you´re using the correct branch?

are you sure you´re using the correct branch?

uhm, well i downloaded the zip of the link you sent: https://github.com/akallabeth/FreeRDP/tree/smart_e_invalid
and then followed the steps i mentioned earlier. Don't know if  sudo dpkg-buildpackage gets files from another branch or something?
in other words: are the steps i took correct?

uhm, well i downloaded the zip of the link you sent: https://github.com/akallabeth/FreeRDP/tree/smart_e_invalid
and then followed the steps i mentioned earlier. Don't know if  sudo dpkg-buildpackage gets files from another branch or something?
in other words: are the steps i took correct?

this is what the folder looks like after i installed everything;

this is what the folder looks like after i installed everything;

@ShiZNizZLe ok, I´ve added a very prominent log message in https://github.com/akallabeth/FreeRDP/tree/smart_e_invalid2
could you retry with that one?
the steps you describe are fine (dpkg-buildpackage uses the sources you have locally) but I fail to see how you end up in that specific code path, so this might help

@ShiZNizZLe ok, I´ve added a very prominent log message in https://github.com/akallabeth/FreeRDP/tree/smart_e_invalid2
could you retry with that one?
the steps you describe are fine (dpkg-buildpackage uses the sources you have locally) but I fail to see how you end up in that specific code path, so this might help

ah okay i get you.
Well i don't know exactly how the programming of the button works, as a collegue of mine designed that program.
That button is the trigger for the invalid parameter error i think. i can see if i can get you the functionality of the button if you need that.
But i'll try the the new branch first.
Although what i don't get:
why do the nightly files in the 1st screenshot appear after excecuting dpkg-buildpackage if it should only use the local files?

ah okay i get you.
Well i don't know exactly how the programming of the button works, as a collegue of mine designed that program.
That button is the trigger for the invalid parameter error i think. i can see if i can get you the functionality of the button if you need that.
But i'll try the the new branch first.
Although what i don't get:
why do the nightly files in the 1st screenshot appear after excecuting dpkg-buildpackage if it should only use the local files?

it even says building nightly, which i don't understand then

it even says building nightly, which i don't understand then

@ShiZNizZLe because you´re building the nightly package ;)
that is the same we do on our build machines.
You installed the .deb files created, yes? (sorry, have to ask)

@ShiZNizZLe because you´re building the nightly package ;)
that is the same we do on our build machines.
You installed the .deb files created, yes? (sorry, have to ask)

and yes, a small sample app that triggers the issue could help a lot as I then can reproduce locally and do not require your help for checking.

and yes, a small sample app that triggers the issue could help a lot as I then can reproduce locally and do not require your help for checking.

yes i see the deb files, i'm now gonna generate a log for you.
Now i understand :)
Uhm well the problem is that you would also need the uzi smartcard (which we use) to test it yourself. I can ask if i can send you the important parts of the code, i think that comes in handy too or not?

yes i see the deb files, i'm now gonna generate a log for you.
Now i understand :)
Uhm well the problem is that you would also need the uzi smartcard (which we use) to test it yourself. I can ask if i can send you the important parts of the code, i think that comes in handy too or not?

log_freerdp.txt
here you go

log_freerdp.txt
here you go

@ShiZNizZLe as expected, the log message is missing.
how do you run the installed binary? nightly installs to /opt/freerdp-nightly/bin/xfreerdp

@ShiZNizZLe as expected, the log message is missing.
how do you run the installed binary? nightly installs to /opt/freerdp-nightly/bin/xfreerdp

i think that link makes it complicated?
i ran it from the folder in screenshot 2 because i thought that was were it would build.
i now think i have to go to
/home/pi/freerdpnightly/FreeRDP-smart_e_invalid2
then to the linked debian folder and then to the opt folder, which is here:
/home/pi/freerdpnightly/FreeRDP-smart_e_invalid2/debian/freerdp-nightly/opt/freerdp-nightly/bin
why is it in such a weird place?

i think that link makes it complicated?
i ran it from the folder in screenshot 2 because i thought that was were it would build.
i now think i have to go to
/home/pi/freerdpnightly/FreeRDP-smart_e_invalid2
then to the linked debian folder and then to the opt folder, which is here:
/home/pi/freerdpnightly/FreeRDP-smart_e_invalid2/debian/freerdp-nightly/opt/freerdp-nightly/bin
why is it in such a weird place?

@ShiZNizZLe I think you do it a bit weiredly.

Build the debian packages with dpkg-buildpackage
Install the .deb files generated with dpkg -i <name>.deb
Run /opt/freerdp-nightly/bin/xfreerdp

as for why we install in /opt, because the nightly should not override stable versions shipped with your distro.

@ShiZNizZLe I think you do it a bit weiredly.

Build the debian packages with dpkg-buildpackage
Install the .deb files generated with dpkg -i <name>.deb
Run /opt/freerdp-nightly/bin/xfreerdp

as for why we install in /opt, because the nightly should not override stable versions shipped with your distro.

well i just followed the instructions right here:
https://github.com/FreeRDP/FreeRDP/wiki/Compilation
so i just have to
-cd to the extracted zip and then
-dpkg-buildpackage
-install all debs
-run
?

well i just followed the instructions right here:
https://github.com/FreeRDP/FreeRDP/wiki/Compilation
so i just have to
-cd to the extracted zip and then
-dpkg-buildpackage
-install all debs
-run
?

@ShiZNizZLe yes.
please also paste the command line you use (strip passwords etc)

@ShiZNizZLe yes.
please also paste the command line you use (strip passwords etc)

okay, i'll do that tomorrow morning!

okay, i'll do that tomorrow morning!

well when i try it your way i get this?
haven't found a solution how to solve it

here are the extracted files where im trying to do dpkg-buildpackage

well when i try it your way i get this?
haven't found a solution how to solve it

here are the extracted files where im trying to do dpkg-buildpackage

@ShiZNizZLe of course you need the ln -s step, I was just checking if you were calling the correct binary, because I´ve debugged the stuff yesterday and you were really using the wrong binary as the required log messages were missing.
I´ve created https://github.com/FreeRDP/FreeRDP/pull/6757 to address this now as I was able to create a test code that exposed the issue.
Please build that source:

Follow the steps from the dpkg-buildpackage in the wiki
install the resulting .deb packages
test with /opt/freerdp-nightly/bin/xfreerdp

@ShiZNizZLe of course you need the ln -s step, I was just checking if you were calling the correct binary, because I´ve debugged the stuff yesterday and you were really using the wrong binary as the required log messages were missing.
I´ve created https://github.com/FreeRDP/FreeRDP/pull/6757 to address this now as I was able to create a test code that exposed the issue.
Please build that source:

Follow the steps from the dpkg-buildpackage in the wiki
install the resulting .deb packages
test with /opt/freerdp-nightly/bin/xfreerdp

do i also have to do this one then? because i didn't do that before or do i need to do the rest of the steps from your extracted branch like in the screenshot above?:
sudo apt build-dep freerdp2-x11
Sorry it isn't all that logical to me

do i also have to do this one then? because i didn't do that before or do i need to do the rest of the steps from your extracted branch like in the screenshot above?:
sudo apt build-dep freerdp2-x11
Sorry it isn't all that logical to me

finally,
did it without sudo apt build-dep freerdp2-x11
then unpacked freerdp-nightly_3.0.0_armhf.deb
then  freerdp-nightly-dbg_3.0.0_armhf.deb
and then freerdp-nightly-dev_3.0.0_armhf.deb
now i can run it from opt...
maybe handy to add the steps to the compilation wiki?
because i've always missed that i should depackage the debs

finally,
did it without sudo apt build-dep freerdp2-x11
then unpacked freerdp-nightly_3.0.0_armhf.deb
then  freerdp-nightly-dbg_3.0.0_armhf.deb
and then freerdp-nightly-dev_3.0.0_armhf.deb
now i can run it from opt...
maybe handy to add the steps to the compilation wiki?
because i've always missed that i should depackage the debs

everything succeeded, only now the log seems nowhere to be found

everything succeeded, only now the log seems nowhere to be found

ah i could'nt write to the folder apparently, but here it is
log.txt

ah i could'nt write to the folder apparently, but here it is
log.txt

@ShiZNizZLe ok, good. then we finally have a fix.

@ShiZNizZLe ok, now I see the error. you call the wrong xfreerdp binary!
calling without path (like xfreerdp ) will call the binary that is found in your PATH
either start with /opt/freerdp-nightly/bin/xfreerdp or (in your case from the same folder) with ./xfreerdp

@ShiZNizZLe ok, now I see the error. you call the wrong xfreerdp binary!
calling without path (like xfreerdp ) will call the binary that is found in your PATH
either start with /opt/freerdp-nightly/bin/xfreerdp or (in your case from the same folder) with ./xfreerdp

huh why do i have to put ./ before it even though i'm already in that folder, funny :')
gimme a sec

huh why do i have to put ./ before it even though i'm already in that folder, funny :')
gimme a sec

then i get this message:

then i get this message:

then i get this message

then i get this message

@ShiZNizZLe we are getting there.
check where your libasan.so is located (run find /usr/lib -name "*asan*so*" to get a list of files matching) and start with LD_PRELOAD=<path_to_libasan>/libasan.so ./xfreerdp <yourargs>
I´ve got 2 installed on my machine, so I get
/usr/lib/x86_64-linux-gnu/libasan.so.6
/usr/lib/x86_64-linux-gnu/libasan.so.6.0.0
/usr/lib/x86_64-linux-gnu/libasan.so.5.0.0
/usr/lib/x86_64-linux-gnu/libasan.so.5

and you need to check which one works on your machine.
obviously you will have different paths as you are on arm.
something similar to /usr/lib/aarch64-linux-gnu/libasan.so.5

@ShiZNizZLe we are getting there.
check where your libasan.so is located (run find /usr/lib -name "*asan*so*" to get a list of files matching) and start with LD_PRELOAD=<path_to_libasan>/libasan.so ./xfreerdp <yourargs>
I´ve got 2 installed on my machine, so I get
/usr/lib/x86_64-linux-gnu/libasan.so.6
/usr/lib/x86_64-linux-gnu/libasan.so.6.0.0
/usr/lib/x86_64-linux-gnu/libasan.so.5.0.0
/usr/lib/x86_64-linux-gnu/libasan.so.5

and you need to check which one works on your machine.
obviously you will have different paths as you are on arm.
something similar to /usr/lib/aarch64-linux-gnu/libasan.so.5

i guess i have to pick the middle one then

i guess i have to pick the middle one then

i get this when i opened up the connection. i see the desktop very shortly and closes immediately after

i get this when i opened up the connection. i see the desktop very shortly and closes immediately after

@ShiZNizZLe ok, good, the application is now finally running (and the correct version too, yea!)

So, first, you can ignore the ASAN warnings that have something with X11 in it (these are from the way X11 cleans up resources)
There seems to be an issue with your RDP server, try running with /log-level:debug to get some more information why this happens.
You might skip the last step and just add /network:auto /gfx:avc444 and check if the connection works then. (RDP has some very very strange settings, so best try to set them to automatic detection whenever possible)

@ShiZNizZLe ok, good, the application is now finally running (and the correct version too, yea!)

So, first, you can ignore the ASAN warnings that have something with X11 in it (these are from the way X11 cleans up resources)
There seems to be an issue with your RDP server, try running with /log-level:debug to get some more information why this happens.
You might skip the last step and just add /network:auto /gfx:avc444 and check if the connection works then. (RDP has some very very strange settings, so best try to set them to automatic detection whenever possible)

@ShiZNizZLe ok, there is an issue on current master, I´ve pushed a fix for that to the pull request branch

@ShiZNizZLe ok, there is an issue on current master, I´ve pushed a fix for that to the pull request branch

with option 3 it quits again
i'll get you a log file

with option 3 it quits again
i'll get you a log file

log_freerdp(1).txt

log_freerdp(1).txt

@ShiZNizZLe I´ve already written it, I´ve pushed a fix for the thing you see to the branch, please redownload

@ShiZNizZLe I´ve already written it, I´ve pushed a fix for the thing you see to the branch, please redownload

this one right? https://github.com/akallabeth/FreeRDP/tree/smart_e_invalid2 (because i don't see a recent file change)

this one right? https://github.com/akallabeth/FreeRDP/tree/smart_e_invalid2 (because i don't see a recent file change)

@ShiZNizZLe no, #6757 , the pull request

@ShiZNizZLe no, #6757 , the pull request

should i do something like this to do that? git fetch origin pull/6757/head:something
never pulled a request before either

should i do something like this to do that? git fetch origin pull/6757/head:something
never pulled a request before either

sorry i really don't know how to get the files from there, could you guide me through it, this is all a bit new for me...

sorry i really don't know how to get the files from there, could you guide me through it, this is all a bit new for me...

i think i got it gimme a sec

i think i got it gimme a sec

@ShiZNizZLe on the top there is a link to the source branch, wher you can download the zip, on the bottom there are instructions on how to check it out.

@ShiZNizZLe on the top there is a link to the source branch, wher you can download the zip, on the bottom there are instructions on how to check it out.

this one you mean right?

its a bit frustrating why i cant seem  to use git tho...

this one you mean right?

its a bit frustrating why i cant seem  to use git tho...

works

works

lol now it does this again, i'm pretty sure i didn't miss anything right?

lol now it does this again, i'm pretty sure i didn't miss anything right?

@ShiZNizZLe

you forgot ln -s
why sudo dpkg-buildpackage? building never requires root

@ShiZNizZLe

you forgot ln -s
why sudo dpkg-buildpackage? building never requires root

oops sorry
because just to be sure i guess
i only see a link to the community guidelines on the pull request page

oops sorry
because just to be sure i guess
i only see a link to the community guidelines on the pull request page

Ok, might be collapsed, but here:

Ok, might be collapsed, but here:

ah, didn't trust clicking anywhere near merging, thanks!

ah, didn't trust clicking anywhere near merging, thanks!

@ShiZNizZLe no worries, you don´t have the permissions ;)

@ShiZNizZLe no worries, you don´t have the permissions ;)

oh well thats the problem, can't click it :')

oh well thats the problem, can't click it :')

also can't check out apparently

also can't check out apparently

building now,
hopefully this is fine

building now,
hopefully this is fine

got a new log for you :)
log_freerdp(2).txt

got a new log for you :)
log_freerdp(2).txt

i can give you a zip with the solution and excecutable if you want?
the dll's are made by aet europe https://www.aeteurope.com/
the problem is that we can't see what we're doing wrong with these dll's, because we can't see the code.
I don't know if this will help you in any way?
The only problem is that you don't have the 'uzi' smartcard that we have to use.

In log_freerdp(2).txt we see a strange message.
at .... SCardGetAttrib for dwAttrId: SCARD_ATTR_ATR_STRING is requested which is handled correctly. We don't see any problem in our own logs anymore.
but at ...  there is a SCardDisconnectS with  dwDisposition: SCARD_LEAVE_CARD.
We did not remove the card...
at ... there is message  SCardGetStatusChangeA failed with error SCARD_E_TIMEOUT [-2146435062]


Cross compiling for arm with 'c' plugin fails at linker 'cpp' plugin does nothing

Expected Behavior
"Hello world!" application cross compiles to arm.
Current Behavior
With the 'c' plugin applied, building the component after calling the linker at /usr/bin/ld.
Compiling directly with arm-linux-gnueabi-gcc <mysrc> works. I also tried changing to 'cpp' plugin, but that seems to do nothing at all.
Context
Gradle version 4.9. I tried to get a working example of cross-compiling with the below build configuration
apply plugin: 'c'

model {
    toolChains {
        gcc(Gcc) {
            target('arm'){
                cppCompiler.withArguments { args ->
                    args << "-m32"
                }
                linker.withArguments { args ->
                    args << "-m32"
                }
            }
        }
    }
    platforms {
        x64 {
            architecture 'x86_64'
        }
        arm {
            architecture 'arm'
        }
    }
    components {
        app(NativeExecutableSpec) {
            targetPlatform 'x64'
            targetPlatform 'arm'
        }
    }
}

with the code for helloworld in src/app/c.
Steps to Reproduce (for bugs)
The above should be sufficient, I think.
Your Environment
Ubuntu 16.04, I installed packages gcc-arm-linux-gnueabi binutils-arm-linux-gnueabi according to
https://askubuntu.com/a/250721/62612

Thanks @eaaltonen for this question. Cross-compilation is possible with both the software model plugins (your case) and the new native plugins. You will most likely have to replace -m32 or -m64 by -mthumb for cCompiler, cppCompiler, linker, and compilerProbeArgs so Gradle discover the right headers.
Then, you need to change the cCompiler, cppCompiler, linker and staticLibArchiver executable to use the one from the cross-compilation tool chains. To do so, you would use something like cCompiler.executable = 'gcc-arm-linux-gnueabi-gcc' for the C compiler. You need to do the same for the other one as well. You should also use gcc-arm-linux-gnueabi-gcc (if building only C) or gcc-arm-linux-gnueabi-g++ (if building C and C++) as the linker. By default, Gradle will find the default GCC for the current host and will fail in presence of any cross-compilation directive.
Putting it all together should look like this (disclaimer, I don't have cross-compilers on my machine so I can verify if the code is accurate, but it should give you a good idea on how to solve your issue):
apply plugin: 'c'

model {
    toolChains {
        gcc(Gcc) {
            path '/path/to/cross/toolchain/bin'
            target('arm'){
                compilerProbeArgs.removeAll(['-m32', '-m64'])
                compilerProbeArgs << '-mthumb'
                cCompiler.withArguments { args ->
                    args.removeAll(['-m32', '-m64'])
                    args << "-mthumb"
                }
                cppCompiler.withArguments { args ->
                    args.removeAll(['-m32', '-m64'])
                    args << "-mthumb"
                }
                linker.withArguments { args ->
                    args.removeAll(['-m32', '-m64'])
                    args << "-mthumb"
                }
                cCompiler.executable = 'gcc-arm-linux-gnueabi-gcc'
                cppCompiler.executable = 'gcc-arm-linux-gnueabi-g++'
                linker.executable = 'gcc-arm-linux-gnueabi-g++'
                staticLibArchiver = 'gcc-arm-linux-gnueabi-ar'
            }
        }
    }
    platforms {
        x64 {
            architecture 'x86_64'
        }
        arm {
            architecture 'arm'
        }
    }
    components {
        app(NativeExecutableSpec) {
            targetPlatform 'x64'
            targetPlatform 'arm'
        }
    }
}

Thanks @lacasseio for your reply.
I tried your suggestions with the following build configuration. I have mostly set the paths and names to match the locations of the GCC arm cross compiler packages on Ubuntu.
apply plugin: 'c'

model {
    platforms {
        x64 {
            architecture 'x86_64'
        }
        armel {
            architecture 'armel'
        }
    }
    toolChains {
        gcc(Gcc) {
            path '/usr/bin'
            target('armel'){
                compilerProbeArgs.removeAll(['-m32', '-m64'])
                compilerProbeArgs << '-mthumb'
                cCompiler.withArguments { args ->
                    args.removeAll(['-m32', '-m64'])
                    args << "-mthumb"
                }
                cppCompiler.withArguments { args ->
                    args.removeAll(['-m32', '-m64'])
                    args << "-mthumb"
                }
                linker.withArguments { args ->
                    args.removeAll(['-m32', '-m64'])
                    //args << "-mthumb"
                }
                cCompiler.executable = 'arm-linux-gnueabi-gcc'
                cppCompiler.executable = 'arm-linux-gnueabi-g++'
                linker.executable = 'arm-none-eabi-ld'
                //staticLibArchiver = 'arm-none-eabi-ar'
            }
        }
    }
    components {
        app(NativeExecutableSpec) {
            targetPlatform 'x64'
            targetPlatform 'armel'
        }
    }
}

Some observations from trying this build:

Trying to set the staticLibArchiver will fail the build , as it is a read-only property for "object of type org.gradle.nativeplatform.toolchain.internal.gcc.DefaultGccPlatformToolChain"

Compiling to an object file works, however linking fails (does not fail build). Linker output below.

/usr/bin/ld: cannot find crt1.o: No such file or directory
/usr/bin/ld: cannot find crti.o: No such file or directory
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/5/libstdc++.so when searching for -lstdc++
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/5/libstdc++.a when searching for -lstdc++
/usr/bin/ld: cannot find -lstdc++
/usr/bin/ld: cannot find -lm
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/5/libgcc_s.so when searching for -lgcc_s
/usr/bin/ld: cannot find -lgcc_s
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/5/libgcc.a when searching for -lgcc
/usr/bin/ld: cannot find -lgcc
/usr/bin/ld: cannot find -lc
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/5/libgcc_s.so when searching for -lgcc_s
/usr/bin/ld: cannot find -lgcc_s
/usr/bin/ld: skipping incompatible /usr/lib/gcc/x86_64-linux-gnu/5/libgcc.a when searching for -lgcc
/usr/bin/ld: cannot find -lgcc
/usr/bin/ld: cannot find crtn.o: No such file or directory
collect2: error: ld returned 1 exit status

I tried linking manually by calling arm-linux-gnueabi-ld -o output <objectfile built by Gradle> /usr/arm-linux-gnueabi/lib/crt1.o /usr/arm-linux-gnueabi/lib/libc.so /usr/arm-linux-gnueabi/lib/crti.o
This worked, except for the paths in the binary containing /usr/arm-linux-gnueabi/lib/crt1.o etc. which should probably have been /lib/crt1.o. These files are provided by the package libc6-armel-cross. The paths would need fixing, but I gave up at this point due to my lack of experience in cross compiling. It would be great if the new native plugins had improved support for cross compiling.

Use arm-none-eabi-g++ or arm-none-eabi-gcc as the linker instead.


memory leak in shi_insert

void *scfg_key = strdup(SERVER_SCFG_KEY);
shi->shi_insert(shi_ctx, scfg_key, SERVER_SCFG_KEY_SIZE,
        s_server_config.lsc_scfg, server_config_sz, t + settings->es_sttl);

ret = shi->shi_lookup(shi_ctx, scfg_key, SERVER_SCFG_KEY_SIZE,
                      &scfg_ptr, &real_len);

It seems memory leak in scfg_key, scfg_key is a duplicate string, but will not be released.
As an api, scfg_key should not be released in application code. If  application code released it in shi_insert function， it will crashed in shi_lookup because shi_lookup will use it later.
The same is ture in lsquic_tokgen.c
@dtikhonov

The shared hash interface is somewhat unusual -- and perhaps it could be documented better, but there is no leak.  The ownership of the second argument to shi_insert() is transferred to the shi implementation; it is to be freed when the element is deleted.
A sample implementation of this is in lsquic_stock_shi.c.  It is tested in test_shi.c.  You can see that there is no leak.


The MetaQA dataset

when I read the train.txt, valid.txt and test.txt in data/MetaQA, I found the triples in test.txt are included in train.txt, could you explain why should this happen?

Hi LinxiCai, thanks for your interest.
We studied MetaQA for the QA task, not KG completion task. We want to pretrain on the whole KG (or 50% KG depending on setting) and then finetune for QA. test.txt and valid.txt triples exist just for compatibility with KGE implementations, which require separate validation and test triples. So we simply copied triples from train.txt to test.txt to maintain compatibility.

OK,thanks a lot !! I understand. By the way, I had another question, when I train embedding for metaQA triples, if I don't use dropout or batch_normalization, will there be overfitting? or can you share your training arguments when you get your MetaQA embedding?


Run administration without hot reload mode ends in a JavaScript error

I download the latest tag and install / activate the plugin. After that, I access http://localhost:8000/admin and went in the following error:

If I run the hot reload mode all is fine. Some idea or do you know the issue?

Have you ran the build for the administration javascript? bin/build.sh?
The committed files are not always in the git. If you want a 'upload and run' situation, you should download the zip release.

Yes, I tried to rebuild administration. In my case I take the files from GitHub, unzip them, copy them to the plugin folder. Add the required Composer packages and install the plugin on command line. After that I executed the build script of the  administration assets.
Now I tried to figure out the bug. After I commented out the line:
// import './override/sw-settings-user/page/sw-settings-user-detail';
the login works.

I had the same error.
After commented out the line there is no error at the login page, but also no settting-fields in the backend to enable 2FA.
Shopware Version: <IP_ADDRESS>

I've been looking into this tonight, but I can't seem to reproduce this. I'm getting the same (good) result for the latest tagged version, as well as for the master, both in HRM as with a normal build.

I get this error with the download the zip release.


wip - adding ordered collections

@dgeb this is still a work in progress, I've made the updates to orbit.js and the tests look good. I had a quick go at integrating it with ember-orbit in an app I'm working on but it looks like I'll need to spend some time looking at how ember-orbit and orbit.js integrate tomorrow. I've put this up in case you get a chance to review.

We may want to change the flag from ordered to actsAsOrderedSet, since it's mutually exclusive from actsAsSet, and yet both are modeling set behavior. This will also clarify that any such relationships must be PUT as a whole data set for JSON API (and other sources, I imagine).

@dgeb yeah, that does seem more accurate. I'm hoping to get this tied up this weekend (need to do ember-orbit and check everything against an app).
Could you give me an overview of how actsAsSet actually works with ember-orbit? I can see that orbit.js only allows updateLink to be used by actsAsSet hasManys but I can't see how ember-orbit would switch between using addLink and updateLink (I'd expect https://github.com/orbitjs/ember-orbit/blob/master/lib/ember-orbit/links/has-many-array.js to use updateLink for actsAsSet).

Is there any reason to not use an array for all hasMany and default to always being ordered - things that don't care about order can feel free to ignore the index?

@gnarf it's a good question, we'd need to add some more explicit handling of dupes (using a hash avoids having to worry about this but I'll have to add it anyway for actsAsOrderedSet). You'll see in this PR I've added the index as an additional optional arg to addLink and removeLink. All in all though, always using an orderedSet does seem simpler.

The point about dupes is an important one...

Been looking at firebase and they make a great point about arrays being difficult to update in a distributed environment, it's a case of last write wins when really you want to merge the changes together. I'm now considering switching to using a priority field on each of the items in the list. This has it's own problems, i.e. you can end up with multiple items in the list with the same priority but at least you don't lose items in the list. It is resolvable however because you can stretch the list out and give the overlapping items unique priorities at a later time.

they make a great point about arrays being difficult to update in a distributed environment, it's a case of last write wins when really you want to merge the changes together.

That's why I think this is only acceptable if the entire array is updated as a set, and why I wanted this flag to be actsAsOrderedSet. If you really want merging instead of replacement, then I agree that some sort of priority system on a normal collection makes sense (although it is non-trivial too).

@opsb are you still pursuing actsAsOrderedSet in this branch or have you abandoned it in favor of your Firebase source? Fine to keep this open for now if everything's still a WIP - just asking.

@dgeb I'm circling back round to it after I've done the integration with Firebase. Because I'm integrating two unfamiliar techs (orbit.js and firebase) I wanted to see the big picture before I finished off with that branch. I'm still undecided about the best way to manage arrays for my app but I will finish it off this PR either way.

@opsb makes sense - thanks :+1:

@dgeb this PR is ready to go now. Let me know if there's anything you want me to amend.

The corresponding PR for ember-orbit is at https://github.com/orbitjs/ember-orbit/pull/56

Rebased against master

It's kinda sad that we never got this in.... It needs a rebase again :frowning:
I thought we had and was all telling @mzgoddard about it as if it were a real thing :smile:

I'm a little reticent now. I came across issues with old operations overwriting newer ones when using memory-source with a remote source. Currently there isn't any mechanism in orbit to establish which operation is newer so there's no way to know which one to prefer. This is a fairly thorny topic so I think we'll have to park it for now.

Should we close this PR @opsb , will you update it / rebase it / work on it?

I've been giving this some thought lately actually. The original problem was that there was no way to tell if an operation had been applied to an array or not. The operation relies on the index positioning so if an array is modified after the original operation has been applied then if the operation arrives at the source again (which is relatively common) then you can easily get stuck in infinite loops with two operations churning on the arrays. Now there's a transaction log however it's possible to check if a transaction has been applied already and this stops the bad sequence. That said, there's obviously been a fair few changes since this PR was put together and it's probably better to put it together again from scratch using this one as inspiration.

Alrighty - going to close this then!


Custom event title

Hi!
First of all, very nice script! My problem is, that events that are created get the title from one cell, but I would like to set a custom title like so: var title = sheetName+" no."+row[1]+" inspection";
How would I achieve this in your script? Another problem I'm having is that I'm not able to set how many header rows I have, my spreadsheet has 7 header row and on the 7th row there are the id, title, starttime and so on...
Also, is it possible to remove all the script used for calendar-to-spreadsheet sync? I only need to sync events from spreadsheet to calendar and don't want to have someone accidentally doing it the other way around!
Thanks again!
Cheers!

Here is an example sheet with realistic data: https://docs.google.com/spreadsheets/d/12oW-OoxGCk1rgpgGkzp2aGFf9Ryhw9FpovlfDQMvvLE/edit?usp=sharing
What I'm trying to do is add all rows to the calendar and if the date changes remove the previous event and create a new one, every event should be an All Day event, so I don't need to use the endtime. Right now I did minimal changes to the script but it gives me an error :/
[18-02-20 06:29:15:563 PST] Starting execution
[18-02-20 06:29:15:794 PST]<EMAIL_ADDRESS>[0.222 seconds]
[18-02-20 06:29:15:894 PST] Calendar.getEvents([Wed Dec 31 14:00:00 PST 1969, Thu Dec 31 14:00:00 PST 2499]) [0.099 seconds]
[18-02-20 06:29:15:895 PST] CalendarEvent.getId() [0 seconds]
[18-02-20 06:29:15:896 PST] CalendarEvent.getId() [0 seconds]
[18-02-20 06:29:15:896 PST] CalendarEvent.getId() [0 seconds]
[18-02-20 06:29:15:896 PST] CalendarEvent.getId() [0 seconds]
[18-02-20 06:29:15:897 PST] CalendarEvent.getId() [0 seconds]
[18-02-20 06:29:15:897 PST] CalendarEvent.getId() [0 seconds]
[18-02-20 06:29:15:898 PST] SpreadsheetApp.getActiveSpreadsheet() [0 seconds]
[18-02-20 06:29:15:899 PST] Spreadsheet.getActiveSheet() [0 seconds]
[18-02-20 06:29:16:007 PST] Sheet.getDataRange() [0.107 seconds]
[18-02-20 06:29:16:067 PST] Range.getValues() [0.06 seconds]
[18-02-20 06:29:16:069 PST] Range.offset([0, -1, 19, 1]) [0 seconds]
[18-02-20 06:29:16:123 PST] Execution failed: The coordinates or dimensions of the range are invalid. (line 326, file "Code") [0.498 seconds total runtime]

Any help would be greatly appreciated :)


Get tests passing again

This PR makes rustfmt to pass tests again 😄
Closes #1665.
A few changes are suspicious and I am not sure if they are correctly formatted (e.g. please take a look at comment.rs). Others look harmless to me.

Added a commit to run travis and appveyor only against nightly.

Awesome, thank you so much!


Attiny85 and tone

the tone function is not working on Attiny85
using an arduino works
the test with attiny85
https://wokwi.com/projects/380875729611174913
the same code on an arduino
https://wokwi.com/projects/380875832702983169
using only digitalWrite and delay the buzzer works

Thanks for reporting!
tone() does not work on the default ATTiny85 core - it is not a simulation problem, it also doesn't on the actual ATtiny85 device. See here: https://forum.arduino.cc/t/attiny-and-tone/430648/37
Using digitalWrite is actually a good way to overcome this - here's an example implementation of beep() that uses the same method: https://wokwi.com/projects/285525640477671948


Add port to host header if it is not the default one for the scheme (HTTP1)

I basically did the same thing as jmmk did here: #200 but for HTTP1.

@ericmj I fixed some things myself, ready for another review.

Thanks @sergiodottori! 💟

Thank you!


BigInt does not have a parseInt method, use BigInt() instead

There is a proposal for BigInt.fromString but it's only stage 1 and nothing implements it yet.

Thanks, I overlooked that one!


Display performance is slow

Please note, this depends on computer / browser / luck when running. I haven't rebooted my computer for some time so it's slower than usual. However, it's not THAT slow.

similar to
https://github.com/source-academy/js-slang/issues/371

The particular benchmark mentioned in the screenshot should not be js-slang's fault, as displaying a single number should still take a really short amount of time on the js-slang end.
I looked into it and this is what gets called for every display call in cadet-frontend
https://github.com/source-academy/cadet-frontend/blob/d0fb4e6e87f4ec6e08f7d0055d4a6a338c8e7e45/src/commons/utils/JsSlangHelper.ts#L46-L53
It's possible that display is slow in this benchmark not because js-slang is slow but because of the overhead incurred by redux. Since there's a "TODO in 2019: fix this hack" in there anyway, I think this might need additional investigation by someone from the frontend team.

Just tested by disabling the "fix this hack" code, and I can run 10k iterations with no issue.

So the bad performance of display in this benchmark is likely contributed by cadet-frontend. Reopening.

My intuition is that react is trying to re-render the entire page every time we put something in there asynchronously.

Ah, @thomastanck sorry for barking up the wrong tree.

My intuition is that react is trying to re-render the entire page every time we put something in there asynchronously.

I see. Sounds fixable.

Much better :D


list index out of range error

Hi, when I attempt to run basic gym envs from the example script, there is a list index out of range error. Screenshots are from an attempt to run Pendulum-v1.

Hi, thanks for opening an issue about this. Curious what caused it and how you fixed it?

I had the same problem when trying to reuse example.py with a non-image custom env. It went away after commenting out the following lines:
  #'encoder.mlp_keys': '$^',
  #'decoder.mlp_keys': '$^',
  #'encoder.cnn_keys': 'image',
  #'decoder.cnn_keys': 'image',


Make createAppendStream actually work

Actually, considering that lack of this commit makes Showdown unusuable, may as well merge it without waiting.


[Shadowrun5thA] add sustained spell tracker

Changes / Comments
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.
[ ] Is this a bug fix?
[ ] Does this add functional enhancements (new features or extending existing features) ?
[ ] Does this add or change functional aesthetics (such as layout or color scheme) ?
[ ] If changing or removing attributes, what steps have you taken, if any, to preserve player data ?
[ ] If this is a new sheet, did you follow Building Character Sheets standards ?

If you do not know English. Please leave a comment in your native language.

Character Sheet Info Roll20 Internal Use only.

Hey @Stexinator there are some conflicts within this one, can you fix those and update your pr? Thanks for all the work you do, mate!


Forking the prediction API (backend)

Blocked by #25

Fork API
switch the front end to use the locally API
Test that it works

https://github.com/projecthorus/tawhiri
https://github.com/projecthorus/tawhiri-downloader-container/

@DarylDohner @David-Rey The prediction backend can run without the frontend, does this need to be blocked by #25 ?

Yes b/c one of the requirements is switching the frontend to pull from the local API and another is to test them together


catkin build problem

Hi @margaritaG  Thanks for your great works!
I have a strange problem, when I run catkin build -j12,  the package can not build success! The build process hang long time! the runtime is 7 hours 42 minutes and 50.9 seconds total. no error log In process.
17 of 24 packages succeeded.
any suggestion?
Thanks!

@wolf943134497 it could be that compilation of pcl_catkin (namely, its pcl_ros package) it running low on RAM, see here.
How many CPU cores does your machine have? Try limiting the number of parallel jobs via the -j flag to something that is way lower that your total number of cores.

@margaritaG  Thank you for your feedback!
my machine have 16 cores. I try  to use 4,6,8,12  parallel jobs,but the problem still can not be solved! I have the same problem when I use pcl_catkin in other project.

@wolf943134497 Did you try catkin build mask_rcnn_ros depth_segmentation gsm_node -j1 -l1?

@wolf943134497 Did you try catkin build mask_rcnn_ros depth_segmentation gsm_node -j1 -l1?

@margaritaG  Thanks your suggestions! It works after trying -j1 - 11


[Uno] Maps crashes the app when used inside ContentDialog on Android

Mapsui Version
5.0.0-beta.4
Mapsui Platform
Uno
Device
Android
Describe the bug
When you open a ContentDialog with a map control in it, as per https://github.com/Mapsui/Mapsui/issues/2778, CenterOn() has no effect and the map stays on the default location over the ocean somewhere, but unlike on desktop, once you touch the map the whole app just crashes (does not seem to throw any exception that I can catch while debugging).
https://github.com/user-attachments/assets/498086fc-160f-48d9-b5a2-9e09088ff201

Note: 4.0.8 works fine in the content dialog.


Trello securityDefinitions etc

Moving issue to relevant repo.
@bobby-brennan wrote

Would suggest moving the Trello spec to unofficial-api-specs as the original doesn't seem to be maintained. If you do I'll submit a PR there.
OAuth2 definition should be removed as Trello only supports OAuth1
api_key name should be key
should also have api_token as both key and token are needed
Correct secDefs:

{
  "securityDefinitions": {
    "api_key": {
      "in": "header",
      "name": "key",
      "type": "apiKey"
    },
    "api_token": {
      "type": "apiKey",
      "in": "query",
      "name": "token"
    }
  }
}

Thanks @bobby-brennan after PR #13 can we close this?

@bobby-brennan it looks like each occurrence of trello_auth needs patching to use one or both of the new apiKey securityDefinitions. Is that something you can do with a search and replace?

A little vim-fu:
%s/trello_auth:\n\(\s\+- '.*'\n\)\+/api_key: []\r        - api_token: []\r/g

https://github.com/APIs-guru/unofficial_openapi_specs/pull/14

Trello updated in the main repo.

Thanks!

No, thank you. Are we ok to close this issue now?

Looks good to me


Add lean.current_search_paths for finding the current library paths

Demo (of using it with telescope):
https://github.com/Julian/lean.nvim/wiki/Configuring-&-Extending#live-grep

The implementation here is really trivial for someone to do themselves, it's one line with telescope.

In that case, I think it would be more helpful to advertise an example configuration for telescope in the readme.  Live grep is also super useful outside of lean projects.
The lean.finder module doesn't seem to provide much convenience either.  The configuration you have in your init.vim seems to be longer than the equivalent telescope configuration.

We may extend functionality here at some point.

What might make this functionality more interesting is if it picked up the directories automatically.  For lean 3, we can parse the output of lean -p.  In lean 4, this is unfortunately a bit more complicated.

That's fair feedback, and likely a good idea. Will have a look at what's involved for the Lean 4 case.
(Though I apparently pushed this to main inadvertently, so will have to back it out).

Will have a look at what's involved for the Lean 4 case.

IIRC there's no nice way to get the paths.  You can get the paths to the source directories for the current package with leanpkg print-paths (the second lines is a :-separated list of directories).  This does not include the source directory for the core library.  The server does something like the following to figure it out:
echo 'def main : IO UInt32 := do IO.println <| <- IO.FS.realPath <| (<- IO.appDir) / ".." / "lib" / "lean" / "src"; pure 0' | lean --stdin --run

The server does something like the following to figure it out

lean --print-libdir looks like it's roughly that now. It doesn't restrict to just the src directory but including the rest of the implementation seems possibly nice anyhow to me.
Will rewire to use that and see what you think.

OK, this is ready for rereview!

@gebner why is it that for Lean 3, lean --path also returns a path to a nonexistent ../library directory (see recent failure)?
$ lean --path
{
  "is_user_leanpkg_path": false,
  "leanpkg_path_file": "/home/rishhvaishnav/.vim/pack/bundle/start/lean.nvim/lua/tests/fixtures/example-lean3-project/l
eanpkg.path",
  "path": [
    "/home/rishhvaishnav/.elan/toolchains/leanprover-community--lean---3.31.0/bin/../library",
    "/home/rishhvaishnav/.elan/toolchains/leanprover-community--lean---3.31.0/bin/../lib/lean/library",
    "/home/rishhvaishnav/.vim/pack/bundle/start/lean.nvim/lua/tests/fixtures/example-lean3-project/./."
  ]
}

why is it that for Lean 3, lean --path also returns a path to a nonexistent ../library directory (see recent failure)?

Because if you use lean directly from the build directory, you only have ~/lean/bin/../library (and not ~/lean/bin/../lib/lean/library).

@Julian see recent few changes and let me know if you have any comments, otherwise LGTM at this point.

Nice, thank you!


feat: lib1 as gradle project and license check

This makes VideoGenerator/library to a proper gradle project again by adding gradle scripts.
Following, the license check plugin that is used in the other subprojects can be applied

I added the license check plugin into lib1. Currently, the license check fails for all subprojects though, since there is some weird error with some junit license file not being found by the plugin. Feel free to investigate. Will try to do so later too

The license creation is now fixed for all subprojects. ./gradlew generateLicenseReport will work in ./DifferenceGenerator, ./VideoGenerator/library and ./GUI.
NOTE: Currently, ./gradlew checkLicense fails due to some packages (junit, compose, etc.) not being resolved properly by the plugin. We'll need to sort that out at some point (before putting the check into the CI at least)

Closes #100


[9.x] WFLY-4812 Upgrade Infinispan to 7.2.3.Final

https://issues.jboss.org/browse/WFLY-4812

Linux with security manager Build 134 is now running using a merge of 1308e48e7a4f327427de71d9c6dca53350a7a9a9

Windows Build 141 is now running using a merge of 1308e48e7a4f327427de71d9c6dca53350a7a9a9

Linux Build 140 is now running using a merge of 1308e48e7a4f327427de71d9c6dca53350a7a9a9

Linux with security manager Build 134 outcome was SUCCESS using a merge of 1308e48e7a4f327427de71d9c6dca53350a7a9a9
Summary: Tests passed: 828, ignored: 319 Build time: 0:06:58

Linux Build 140 outcome was SUCCESS using a merge of 8efd346e95f3104f2ff7e96ecac0b7f2d88948c5
Summary: Tests passed: 2870, ignored: 374 Build time: 0:47:51

Windows Build 141 outcome was SUCCESS using a merge of 8efd346e95f3104f2ff7e96ecac0b7f2d88948c5
Summary: Tests passed: 2870, ignored: 374 Build time: 0:48:12

Linux Build 141 is now running using a merge of 8efd346e95f3104f2ff7e96ecac0b7f2d88948c5

Linux with security manager Build 135 is now running using a merge of 8efd346e95f3104f2ff7e96ecac0b7f2d88948c5

Windows Build 142 is now running using a merge of 8efd346e95f3104f2ff7e96ecac0b7f2d88948c5

Linux with security manager Build 135 outcome was SUCCESS using a merge of 8efd346e95f3104f2ff7e96ecac0b7f2d88948c5
Summary: Tests passed: 828, ignored: 319 Build time: 0:05:39

Windows Build 142 outcome was SUCCESS using a merge of 8efd346e95f3104f2ff7e96ecac0b7f2d88948c5
Summary: Tests passed: 2870, ignored: 374 Build time: 0:47:54

Linux Build 141 outcome was SUCCESS using a merge of 8efd346e95f3104f2ff7e96ecac0b7f2d88948c5
Summary: Tests passed: 2869, ignored: 374, muted: 1 Build time: 0:48:25

Does this remove the need for https://github.com/wildfly/wildfly/pull/7629 ?

@stuartwdouglas It does not remove the need for #7629.  This only changes the isolation of the ejb cache.

I thought the isolation of the cache was the problem (at least the problem started appearing after it was changed). If you have REPEATABLE_READ does this mean that web requests will wait until the previous request has finished and the changes are commited to the cache? If so then this should be all that is required to fix the test.

Linux with security manager Build 137 is now running using a merge of d8867fd34ae9d209e22d3f9b9030a26fecd59430

Linux Build 143 is now running using a merge of d8867fd34ae9d209e22d3f9b9030a26fecd59430

Windows Build 144 is now running using a merge of d8867fd34ae9d209e22d3f9b9030a26fecd59430

Linux with security manager Build 137 outcome was SUCCESS using a merge of d8867fd34ae9d209e22d3f9b9030a26fecd59430
Summary: Tests passed: 828, ignored: 319 Build time: 0:05:30

Windows Build 144 outcome was SUCCESS using a merge of d8867fd34ae9d209e22d3f9b9030a26fecd59430
Summary: Tests passed: 2870, ignored: 374 Build time: 0:46:26

Linux Build 143 outcome was SUCCESS using a merge of d8867fd34ae9d209e22d3f9b9030a26fecd59430
Summary: Tests passed: 2869, ignored: 374, muted: 1 Build time: 0:46:51

I had initially widened the isolation to improve concurrent read access a session.  Let me revert that until I find a better solution.

Windows Build 145 is now running using a merge of 8dcc79dbccf54195a83d87d8e656d0d54b658aee

Linux Build 144 is now running using a merge of 8dcc79dbccf54195a83d87d8e656d0d54b658aee

Linux with security manager Build 138 is now running using a merge of 8dcc79dbccf54195a83d87d8e656d0d54b658aee

Linux with security manager Build 138 outcome was SUCCESS using a merge of 8dcc79dbccf54195a83d87d8e656d0d54b658aee
Summary: Tests passed: 828, ignored: 319 Build time: 0:05:42

Windows Build 145 outcome was SUCCESS using a merge of 8dcc79dbccf54195a83d87d8e656d0d54b658aee
Summary: Tests passed: 2870, ignored: 374 Build time: 0:47:49

Linux Build 144 outcome was SUCCESS using a merge of 8dcc79dbccf54195a83d87d8e656d0d54b658aee
Summary: Tests passed: 2870, ignored: 374 Build time: 0:48:16


[secp256r1] Use the p256 crate's implementation of recoverable signatures

Since v0.13.0, the p256 crate supports recoverable signatures. There's as of v0.13.0 a todo in their code about handling reduced x's which is not handled yet, but when that's done, we should consider using their implementation instead of our own.

This is no longer relevant after #566


Automated PR: Standardising Files

This PR will standardise the files we have with out agreed spec in sous-chefs/repo-management.
This repo has been identified by topic(s) of chef-cookbook

they DO have Debian 11 and Ubuntu 22.04, which was my whole point.
lrosenman@ossec:~$ cat /etc/apt/sources.list.d/ossec.list
deb  [trusted=yes]     https://updates.atomicorp.com/channels/atomic/ubuntu jammy/amd64/
lrosenman@ossec:~$

Same for Debian with bullseye/amd64/ and bullseye/arm64

Released as: 2.0.0


adds Amazon Sagemaker actions

@phillipperalez I've added the tests, so I think this is ready for another review.


CryptoConfig.EncodeOID Bug - "Value was either too large or too small for an Int32."

Multiple places in the code and its dependent libraries end up calling .NET's CryptoConfig.EncodeOID:

https://github.com/PKISolutions/pkix.net/blob/a6847f693edf5970836d1595a0edb5c0e709df51/PKI/Cryptography/Oid2.cs#L402
https://github.com/PKISolutions/pkix.net/blob/a6847f693edf5970836d1595a0edb5c0e709df51/PKI/Cryptography/Oid2.cs#L464

SysadminsLV.Asn1Parser.Asn1Utils.EncodeObjectIdentifier uses it as well and it is used extensively throughout the code base:

There appears to be an integer parsing bug in CryptoConfig.EncodeOID. The following PowerShell demonstrates this bug.
PS C:\> [System.Security.Cryptography.CryptoConfig]::EncodeOID('<IP_ADDRESS>.4.1.3<IP_ADDRESS>3183039')

Exception calling "EncodeOID" with "1" argument(s): "Value was either too large or too small for an Int32."
At line:1 char:1
+ [System.Security.Cryptography.CryptoConfig]::EncodeOID('<IP_ADDRESS>.4.1.3 ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
    + FullyQualifiedErrorId : OverflowException

The bug is due to the following code in .NET's CryptoConfig.EncodeOID function:
public static byte[] EncodeOID(string str)
{
	if (str == null)
	{
		throw new ArgumentNullException("str");
	}
	char[] separator = new char[]
	{
		'.'
	};
	string[] array = str.Split(separator);
	uint[] array2 = new uint[array.Length];
	for (int i = 0; i < array.Length; i++)
	{
		array2[i] = (uint)int.Parse(array[i], CultureInfo.InvariantCulture);
	}

Note that the code use splits the OID string by periods, and then attempts to parse each numeric value using int.Parse. The bug is<PHONE_NUMBER> is a valid OID value, but it is too large for int.Parse to handle. As such, the Value was either too large or too small for an Int32. exception gets thrown.
We originally encountered bug when using PSPKI's Get-CATemplate cmdlet in an environment where AD CS assigned a template OID that caused the exception. In that case, pkix.net appears to use CryptoConfig.EncodeOID primarly for OID input validation (just making sure it's a well-formed OID). I'd suggest implementing your own function to do the validation until .NET can fix the bug upstream. Other places in the code, however, appear to use SysadminsLV.Asn1Parser.Asn1Utils.EncodeObjectIdentifier to get the OID bytes, so a replacement for CryptoConfig.EncodeOID  may be needed in those instances.

Thanks for report, I will take a look into it. Stuff in SysadminsLV.Asn1Parser.Asn1Utils is mostly obsolete. There is more proper ASN.1 OBJECT_IDENTIFIER handler: https://github.com/PKISolutions/Asn1DerParser.NET/blob/master/Asn1Parser/Universal/Asn1ObjectIdentifier.cs
it treats tokens as unsigned 64-bit QWORDs. But it may be reasonable to use BigInts for safety just in case if someone gets really mad and use enormous values. Either way, this needs to be reviewed and addressed.

A follow-up. I've updated Asn1Parser library to address mentioned issues as follows:

I've updated Asn1ObjectIdentifier to handle really big numbers, which are larger than unsigned QWORDs
Updated Asn1Utils.EncodeObjectIdentifier and Asn1Utils.DecodeObjectIdentifier to use Asn1ObjectIdentifier class for encoding and decoding and which doesn't use .NET shortcuts (like CryptoConfig or X509EnhancedKeyUsageExtension classes). Instead, it relies on a pure math and BigInteger to represent OID arcs.

Awesome! I appreciate the really fast response!

fixed in v4.0.1


fs__WEBPACK_IMPORTED_MODULE_1___default.a.realpathSync is not a function

I am using graphql.macro to import .graphql file in a create-react-app app. It works well.
However, when I try to run a Cypress test, I got error

The following error originated from your test code, not from Cypress.

fs__WEBPACK_IMPORTED_MODULE_1___default.a.realpathSync is not a function

When Cypress detects uncaught errors originating from your test code it will automatically fail the current test.
Cypress could not associate this error to any specific test.
We dynamically generated a new test to display this failure.
Check your console for the stack trace or click this message to see where it originated from.
client/node_modules/graphql.macro/es/utils/resolveImportPath.js:3:13
  1 | import path from 'path';
  2 | import fs from 'fs';
> 3 | var CMD = fs.realpathSync(process.cwd());
    |             ^
  4 | var jsconfigPath = path.resolve(CMD, 'jsconfig.json');
  5 | var jsconfigInclude;
  6 |

I know Cypress is using Mocha internally.
Any help will be great. Thanks

I found https://github.com/apollographql/graphql-tag#testing

Testing environments that don't support Webpack require additional configuration. For Jest use jest-transform-graphql.

Hmm, what about Cypress which built on Mocha...

Same problem, except on production :( Can't get this plugin to work at all, and have no way to load my gql files in my CRA.


Refactoring Recording

Done some documenting over Commands and Recording.
engine.rs is now called recording.rs
Id is now ResourceId and uses NonZeroU64::new_unchecked as mentioned in the comment
Some structs/variants with Buf got replaced with Buffer because Image is also not shortened as Img.

There are some comments and functions left in Recording where I don't know what they do in detail yet so they're left out.


Required option in addSPLookupFieldXml/ CAML bloc does not work.

Hi i have tried many ways to add the required option for the column but nothing seems to be working. i have tried adding the IsRequired option  like this
schemaXml": "<Field Type="Lookup" DisplayName="Customer" Required="TRUE" ShowField="Title" Name ="CreaOppClient"/>",
"addToDefaultView": true,
"isRequired": true,
"verb": "addSPLookupFieldXml",
"targetListName":"Custom Library"
But that did not work, I delete the entire column and recreate, not working either. Any help would be appreciate.

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

ID: 68267476-ee8d-7b95-446b-711ddb683da2
Version Independent ID: aa099b9d-48db-5513-11c7-32c49a27e5be
Content: Site design JSON schema
Content Source: docs/declarative-customization/site-design-json-schema.md
Product: sharepoint
GitHub Login: @spdevdocs
Microsoft Alias: spdevdocs

@umaknow-alain -
Do you get this issue while creating site from new site design or when you use an update site design?
Please share the scripts. I'll try to run in my Dev tenant.

It was an update site design. When we were trying to invoke the site design via powershell, the required filed was never updated. I finally decided to delete the list and recreate it, then required icon appear. Also one thing important to mention is that when you are using the verb addSPLookupFieldXml, only the caml bloc is taken in consideration.
Thanks you can close the case.


Caught up changes from typescript-github-action-template

#3651  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @CatChen and the rest of your teammates on  Graphite


feat: update sub key http header name to support api catalog SDKCF-1248

Codecov Report

Merging #76 into master will decrease coverage by 0.13%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #76      +/-   ##
==========================================
- Coverage   89.38%   89.25%   -0.14%
==========================================
  Files          25       25
  Lines        1508     1508
==========================================
- Hits         1348     1346       -2
- Misses        160      162       +2

Impacted Files
Coverage Δ

RPerformanceTracking/Private/_RPTConfiguration.m
90% <100%> (ø)
:arrow_up:

...ng/Private/_RPTClassManipulator+UIViewController.m
98.38% <0%> (-1.62%)
:arrow_down:

RPerformanceTracking/Private/_RPTTrackingManager.m
92.65% <0%> (-0.57%)
:arrow_down:

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 875d626...fa77d1d. Read the comment docs.


Third-party matching trial token loaded in top level site is still not allowing 3P cookies access

Our usecase(http://b/332975135) to access third party cookies for the origin https://pay.google.com is recently approved.
We could successfully inject the trial token with third party matching in the top level site when it loads our script. Although developer tool shows the token is valid in the application tab, when the top level site loads the iframe with the origin pay.google.com is still unable to access the top level site cookies.
Here are the screenshots:
Top level site shows the trial token is injected:

Developer tool shows the trial token is valid:

Iframe with the origin pay.google.com still unable to access 3P cookies:

Same Iframe when we enable the option to access 3P cookies manually can access 3P cookies:

Can you confirm that you have the following flag configuration?
chrome://flags/#third-party-cookie-deprecation-trial → enabled
chrome://flags/#tracking-protection-3pcd → enabled
chrome://flags/#tpcd-metadata-grants → disabled
chrome://flags/#tpcd-heuristics-grants → disabled

After taking a closer look at your demo page, the issue appears to be that after the script runs and injects the pay.google.com trial token, there is a pay.google.com iframe loaded without the trial token.
The trial is persistent, so loading an iframe from the token origin without the trial token will disable the trial. This is noted under the graphic here.

You are right about the trial was not persistent as soon as the first iframe loaded without the token.
However after loading the iframe with the same token (By setting the origin-trial response header), still the trial seems to be disabled. Should we need to inject third party token in the top level site and load the iframe by setting its response header with another token (without third party matching)?

Should we need to use two tokens? One for top level site with third party matching and another when loading the iframe?

You will need a different token for the iframe. The "third-party matching" tokens are only for use by scripts that inject the token on other origins. The tokens that can be used by iframes are provided for trial registrations where the "third-party matching" box is not checked.


Target java 8 for agent.

Issue #, if available:
Description of changes: Upstream switched to Java 8 so no point in our bytecode targeting 7
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Codecov Report

Merging #20 (3b26222) into main (7232e67) will increase coverage by 50.00%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main      #20       +/-   ##
===========================================
+ Coverage        0   50.00%   +50.00%
- Complexity      0        3        +3
===========================================
  Files           0        2        +2
  Lines           0       10       +10
  Branches        0        1        +1
===========================================
+ Hits            0        5        +5
- Misses          0        3        +3
- Partials        0        2        +2

Impacted Files
Coverage Δ
Complexity Δ

...y/javaagent/providers/AwsOpenTelemetryFactory.java
62.50% <0.00%> (ø)
3.00% <0.00%> (?%)

...emetry/javaagent/providers/AwsAgentProperties.java
0.00% <0.00%> (ø)
0.00% <0.00%> (?%)

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 7232e67...3b26222. Read the comment docs.


Use new Java signing key

Fixes #5259.

Suggested CHANGELOG text:

Upgrade Java signing key to F638279A7281EE8EAE58C4B98D3CFE7E7D0262DA.

"Test metastore client commands using trino and dbt" is stuck and not  relevant to these changes.  Pulling by administrative force rather than re-doing them (they are on an almost-longest path to success in the actions graph).


Dead lock when PBXObjects.delete

Call xcodeProj.pbxproj.delete(object: ) lead to dead lock.
solve:
add
defer {
    lock.unlock()
}

to PBXObjects.swift in func delete(reference: ) after lock.lock().

Thanks for reporting this @antscript. Feel free to open a PR with the fix that you suggested. Otherwise, we can look into it.


Another Little Typo

diff --git a/src/doc/languagespec.tex b/src/doc/languagespec.tex
index 08e302f..f5dd483 100644
--- a/src/doc/languagespec.tex
+++ b/src/doc/languagespec.tex
@@ -3417,7 +3417,7 @@ derivatives.  Gabor noise allows several optional parameters to the
 "direction", <vector>}
 \vspace{12pt}
 If {\cf anisotropic} is 0 (the default), Gabor noise
-will be isotropic.  If {\cf anisotripic} is 1, the Gabor noise will
+will be isotropic.  If {\cf anisotropic} is 1, the Gabor noise will
 be anisotropic with the 3D frequency given by the {\cf direction}
 vector (which defaults to {\cf (1,0,0)}).  If {\cf anisotropic} is
 2, a hybrid mode will be used which is anisotropic along the

And another:
diff --git a/src/doc/languagespec.tex b/src/doc/languagespec.tex
index 1599a85..7ce8082 100644
--- a/src/doc/languagespec.tex
+++ b/src/doc/languagespec.tex
@@ -4526,7 +4526,7 @@ the previous function.
\apiend
-\apiitem{\colorclosure\ \colorclosure\ {\ce reflection} (normal N, float eta)}
+\apiitem{\colorclosure\ {\ce reflection} (normal N, float eta)}
 \indexapi{reflection()}

 Returns a \colorclosure that represents sharp mirror-like reflection

Thanks!
I've incorporated these fixes into the docs.


Add AWS::DynamoDB::Table to AllowedValues on AWS::CloudTrail::Trail.DataResourceType

Issue #, if available:
fix #2133
Description of changes:
-Add AWS::DynamoDB::Table to AllowedValues on AWS::CloudTrail::Trail.DataResourceType
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I would want to make sure the advanced selectors are available.  The documentation for the CloudTrail resource type doesn't seem to mention it so it looks like I'll have to test it out.


Add a PR comment w/ the alpha version

@codecademy/gamut-templates v2.2.29-alpha.81aeab.10+81aeab35 packages/gamut-templates
@codecademy/gamut            v2.4.5-alpha.81aeab.10+81aeab35 packages/gamut

Published Alpha Packages:@codecademy/gamut-icons      v2.1.5 packages/gamut-icons@codecademy/gamut-styles    v2.2.11 packages/gamut-styles@codecademy/gamut-templates v2.2.30 packages/gamut-templates@codecademy/gamut            v2.4.6 packages/gamut

Published Alpha Packages:@codecademy/gamut-icons      v2.1.5 packages/gamut-icons@codecademy/gamut-styles    v2.2.11 packages/gamut-styles@codecademy/gamut-templates v2.2.30 packages/gamut-templates@codecademy/gamut            v2.4.6 packages/gamut

Published Alpha Packages:%!s():
%!s():
%!s():
%!s():

Published Alpha Packages:@codecademy/gamut-icons:2.1.5
@codecademy/gamut-styles:2.2.11
@codecademy/gamut-templates:2.2.30
@codecademy/gamut:2.4.6

Published Alpha Packages:@codecademy/gamut-icons:2.1.5@codecademy/gamut-styles:2.2.11@codecademy/gamut-templates:2.2.30@codecademy/gamut:2.4.6

Published Alpha Packages:@codecademy/gamut-icons:2.1.5@codecademy/gamut-styles:2.2.11@codecademy/gamut-templates:2.2.30@codecademy/gamut:2.4.6

Published Alpha Packages:@codecademy/gamut-icons@2.1.5@codecademy/gamut-styles@2.2.11@codecademy/gamut-templates@2.2.30@codecademy/gamut@2.4.6


nixos/klipper: Tweaks

Motivation for this change
Building a new printer, and this time it's powered by NixOS and not Yocto :stuck_out_tongue:
Anyways, this PR extends services.klipper to facilitate the use of alternative integrations (e.g., Moonraker). New options are added to allow the configuration of --input-tty, --api-server, as well as the user/group Klipper will run as.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 130616 at f8658c81 run on x86_64-linux 1

2 packages built successfully:

klipper
nixos-install-tools

1 suggestion:

warning: name-and-version
Did you mean to pass pname instead of name to mkDerivation?
Near pkgs/servers/klipper/default.nix:8:3:
  |
8 |   name = "klipper";
  |   ^

Near pkgs/servers/klipper/default.nix:9:3:
  |
9 |   version = "unstable-2021-07-15";
  |   ^

Ah, I now see you made PR's for that too.
Can you add me as a reviewer in this series of changes? Definitely interested in improving the Klipper experience in NixOS :)

Ah, I now see you made PR's for that too.
Can you add me as a reviewer in this series of changes? Definitely interested in improving the Klipper experience in NixOS :)

Sure thing! I wanted to add you to both PRs but I forgot.


customize kibana.index ,console log is not reasonable

version: odfe 1.6.0
make config in kibana
server.name: kibana
server.host: "0"
elasticsearch.hosts: https://localhost:9200
elasticsearch.ssl.verificationMode: none
elasticsearch.username: admin
elasticsearch.password: admin
elasticsearch.requestHeadersWhitelist: ["securitytenant","Authorization"]
kibana.index: ".kibanayg"
opendistro_security.multitenancy.enabled: true
opendistro_security.multitenancy.tenants.preferred: ["Private", "Global"]
opendistro_security.readonly_mode.roles: ["kibana_read_only"]
newsfeed.enabled: false
telemetry.optIn: false
telemetry.enabled: false
console log:
{"type":"error","@timestamp":"2020-04-09T07:14:58Z","tags":["error","migration"],"pid":1,"level":"error","error":{"message":"Authorization Exception: Authorization Exception","name":"Error","stack":"Error: Authorization Exception: Authorization Exception\n    at respond (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:349:15)\n    at checkRespForFailure (/usr/share/kibana/node_modules/elasticsearch/src/lib/transport.js:306:7)\n    at HttpConnector. (/usr/share/kibana/node_modules/elasticsearch/src/lib/connectors/http.js:173:7)\n    at IncomingMessage.wrapper (/usr/share/kibana/node_modules/elasticsearch/node_modules/lodash/lodash.js:4929:19)\n    at IncomingMessage.emit (events.js:203:15)\n    at endReadableNT (_stream_readable.js:1145:12)\n    at process._tickCallback (internal/process/next_tick.js:63:19)"},"message":"Authorization Exception: Authorization Exception"}
{"type":"log","@timestamp":"2020-04-09T07:14:58Z","tags":["status","plugin:opendistro_security@<IP_ADDRESS>","info"],"pid":1,"state":"yellow","message":"Status changed from yellow to yellow - Tenant indices migration failed","prevState":"yellow","prevMsg":"Setting up index template."}

The console message is not clear.
Can you turn on the verbose and provide the information here.
Not sure, but it seems like this is the issue with kibana username.
https://github.com/opendistro-for-elasticsearch/security/blob/825863b5f617c7a191e5ee8d25b88bf1df6d9bbc/src/main/java/com/amazon/opendistroforelasticsearch/security/rest/TenantInfoAction.java#L94
Can you check if the kibana username in elasticsearch is same as configured in kibana.yml?
If not the issue is expected.
You can use this API to find the kibana username in elasticsearch -
curl https://localhost:9200/_opendistro/_security/api/securityconfig?pretty
part of output
 "kibana" : {         "multitenancy_enabled" : true,         "server_username" : "kibanaserver",         "index" : ".kibana"       },
Please let me know if helps.

Closing unable to reproduce given the information above. Please feel free to re-open if this is still an issue in current versions of OpenSearch. Thanks!


Selfhosting for free

Can be this hosted on some free hosting?

If you use a VPS provider and use Docker on it, sure.
Though Feedbacky is best hosted on your own hardware for instance with Docker on a Linux machine. You can use Windows or Mac OS but it is not officially supported by the developer and you'll have to do some workaround for it to work.

I dont have VPS, so I will use the hosted version. It will be free forever for 5 boards?

As of right now, yes.


[Moonbeam] [Astar EVM] Add support for RMRK token

If you want to integrate an asset (fungible token/ NFT), you would need to provide

Name of the asset: RMRK
Blockchains:
Moonbeam
Astar EVM (As soon as Axelar integrates Astar, the token will be available.)
Metadata of the asset (symbol, decimals, smart contract address, on-chain metadata like assetId,...)
Moonbeam: 0x524d524B4c9366be706D3A90dcf70076ca037aE3
Astar: 0x524d524B4c9366be706D3A90dcf70076ca037aE3
Logo of the token: https://www.figma.com/file/PxPvXw5woBernBu3BtwxkX/SubWallet-Project-Logo?type=design&node-id=897-212&mode=design&t=WJ53Qo6C5ASj9mKu-4
Is your asset transferable? Yes

Documents and references:

https://www.rmrk.app/blog/official-announcement-from-rmrk-introducing-the-new-rmrk-token-contract
https://www.rmrk.app/blog/rmrk-tokens

Account has RMRK on moonbeam: 0x4b9D84e1395CEdD43e13271435abAB940AFFD142
Account has RMRK on AstarEVM:


Solid Web additions

Add a JSON-LD to all speaker pages (http://schema.org/Person) and to the podcast episodes.
Enable CORS (https://enable-cors.org)

I'll split this into two issues, given how it concerns two different enhancement ideas.


Consider settlement with recent orders if they are part of "mature" settlements

Fixes #1310
See linked issue to read the motivation.
Implementation:
We get a Vec<Settlement> and iterate over it. If a settlement includes a mature order (older than passed time) or a recent order which has been considered valid at one point, all orders within the current settlement (including recent orders) are considered valid and we look at the next settlement.
We keep looping over all settlements until we reach a point where no new orders have been added to the valid set. Now we know all of the valid orders.
Because this can get computationally expensive for many settlements with many orders, validated settlements get stored in a HashSet in order to quickly determine on each iteration whether we can skip looking at the current settlement.
Test Plan
Added unit test for 3 scenarios:

No settlement includes any "mature" orders => No settlements should be considered
2 disjoint settlements (one including mature order, one including no mature orders) => only the settlement with the mature order is considered
Multiple settlements (1 including mature order) arranged like a linked list => Because 1 settlement includes mature order the other settlements "linked" to it are also considered valid

On second thought the operations we can skip because we have the settlements HashSet are very cheap. So having this set is maybe not worth the additional code complexity. Feedback is welcome.