Clipping generation data

Pull Request
Description
This change in code makes sure that when getting negative generation data from the clients, the data is clipped at 0 and does not go lower.
If your changes affect data processing, have you plotted any changes? i.e. have you done a quick sanity check?

[x ] Yes

Checklist:

[x] My code follows OCF's coding style guidelines
[x] I have performed a self-review of my own code
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] I have checked my code and corrected any misspellings

see #218


Update virus total connector handle breaking change

Please check the following conditions for your PR.

[ ] apiDefinition.swagger.json is validated using paconn validate command.
[ ] apiProperties.json has a valid brand color. Invalid brand colors are #007ee5 and #ffffff.

@amirkeren It appears that you are updating some aspects of your connector update that will introduce breaking changes to your users. Could you please confirm us that there will be no external users affected for this connector.
##[error]The type format has been changed for the output field. Existing flows may be broken if they are using this field and actual payload has been changed. ValuePath: operation/VirusTotalGetIpScanV3/responses/200/schema/data/attributes/last_analysis_stats/harmless/format Source: NewSwagger ##[error]The type format has been changed for the output field. Existing flows may be broken if they are using this field and actual payload has been changed. ValuePath: operation/VirusTotalGetIpScanV3/responses/200/schema/data/attributes/last_analysis_stats/malicious/format Source: NewSwagger ##[error]The type format has been changed for the output field. Existing flows may be broken if they are using this field and actual payload has been changed. ValuePath: operation/VirusTotalGetIpScanV3/responses/200/schema/data/attributes/last_analysis_stats/suspicious/format Source: NewSwagger ##[error]The type format has been changed for the output field. Existing flows may be broken if they are using this field and actual payload has been changed. ValuePath: operation/VirusTotalGetIpScanV3/responses/200/schema/data/attributes/last_analysis_stats/timeout/format Source: NewSwagger ##[error]The type format has been changed for the output field. Existing flows may be broken if they are using this field and actual payload has been changed. ValuePath: operation/VirusTotalGetIpScanV3/responses/200/schema/data/attributes/last_analysis_stats/undetected/format Source: NewSwagger ##[error]The type format has been changed for the output field. Existing flows may be broken if they are using this field and actual payload has been changed. ValuePath: operation/VirusTotalGetIpScanV3/responses/200/schema/data/attributes/total_votes/harmless/format Source: NewSwagger ##[error]The type format has been changed for the output field. Existing flows may be broken if they are using this field and actual payload has been changed. ValuePath: operation/VirusTotalGetIpScanV3/responses/200/schema/data/attributes/total_votes/malicious/format Source: NewSwagger ##[error]The output field has been deleted. Existing flows may be broken if they are using this field and actual payload has been changed. ValuePath: operation/VirusTotalRetrieveInfo/responses/200/schema/date Source: NewSwagger ##[error]The output field has been deleted. Existing flows may be broken if they are using this field and actual payload has been changed. ValuePath: operation/VirusTotalRetrieveInfo/responses/200/schema/results Source: NewSwagger ##[error]The output field has been deleted. Existing flows may be broken if they are using this field and actual payload has been changed. ValuePath: operation/VirusTotalRetrieveInfo/responses/200/schema/stats Source: NewSwagger ##[error]The output field has been deleted. Existing flows may be broken if they are using this field and actual payload has been changed. ValuePath: operation/VirusTotalRetrieveInfo/responses/200/schema/status Source: NewSwagger

@sriyen-msft it is my understanding that the changes we made in the properties file regarding policyTemplateInstances should replace the values in run time and prevent the breaking changes. Is that not the case?

@sriyen-msft it is my understanding that the changes we made in the properties file regarding policyTemplateInstances should replace the values in run time and prevent the breaking changes. Is that not the case?

Adding @mamurshe for review the breaking changes

As Amir said and as we spoke in email, we used policies to replace in run time the path of the new actions.
For each action from the previous breaking changes list (VirusTotalGetIpScanV3, VirusTotalRetrieveInfo, VirusTotalRetrieveInfoaboutFile) we now have:

The old code of this action + the old response definition object.
A new code for this action with new dummy path + new Json response definition object.
Both have a versioning paragraph after it (to show only the new version in portal)
Policies in the end of the code will replace dummy path with original path.

@mamurshe Could you please review the new breaking changes and let us know if they versioning would affect the existing flows

Are the breaking changes compared to what happend after PR 729?
If so, it is not the actual code presented to users in portal.
This PR didn't change anything for the old versions of the actions. They still refer to the same response definition.
For example:
In PR 807 the deprecated version of VirusTotalGetIPScanV3 points to ipResult.
Going to ipResult definition, gives the exact definition prior to PR 729 as seen here.
Same applies to analysesResponse (VirusTotalRetrieveInfo).

@mamurshe Can you please approve this PR to let this go


[BUG] : logic falis in few edge cases

✏ Describe the bug
the code doesn't handel these edge cases 👇🏻
📸 Screenshots
screen-recorder-sun-oct-23-2022-17-14-30.webm
screen-recorder-sun-oct-23-2022-17-16-03.webm

i can work on this..

go for it :star_struck:


Network: Updates NICType() to retrieve type from database

Readies NICType() function for the introduction of additional network types by loading the type from the database.
Includes https://github.com/lxc/lxd/pull/7675 so should not be merged until it has been and rebased.

Readies NICType() function for the introduction of additional network types by loading the type from the database.
Includes #7675 so should not be merged until it has been and rebased.

So we'll merge #7675 first.

@brauner yep, I'll rebase once the other has merged to make review clearer, but I wanted to get a head start on the combined test run. Thanks.

Testsuite passed

@brauner rebased

Testsuite passed


\varphi displayed as \phi in code but not in comment

Hi,
When I would like to use the \varphi greek symbol for example in a variable's name in the autocomplete list the \phi greek symbol appears and it gets completed to it as well. See image 1.
It also happens when I would like to use \phi in a variable's name but it gets completed to \varphi.
However when I do the same thing in a comment, the autocomplete list remains to be the same but the result of the completion is the good greek character. See image 2 and 3.

In the julia documentation it looks good. unicode-input
Interestingly if I use the REPL, \varphi gets completed to \phi no matter if I am writing code or a comment.
My debug info if needed:
Atom:
Version: 1.44.0
Dev Mode: false
Official Release: true
{
"http_parser": "2.8.0",
"node": "10.11.0",
"v8": "6.9.427.31-electron.0",
"uv": "1.23.0",
"zlib": "1.2.11",
"ares": "1.14.0",
"modules": "69",
"nghttp2": "1.33.0",
"napi": "3",
"openssl": "1.1.0",
"electron": "4.2.7",
"chrome": "69.0.3497.128",
"icu": "62.2",
"unicode": "11.0",
"cldr": "33.1",
"tz": "2019a"
}
julia-client:
Version: 0.12.2
Config:
{
"consoleOptions": {},
"firstBoot": false,
"juliaOptions": {},
"juliaPath": "C:\Users\PoloskeiTamasHunor\AppData\Local\Julia-1.3.1\bin\julia.exe",
"uiOptions": {
"enableMenu": true,
"enableToolBar": true,
"errorInRepl": true,
"usePlotPane": false
}
}
ink:
Version: 0.12.2
Config:
undefined
uber-juno:
Version: 0.3.0
Config:
{
"disable": true
}
language-julia:
Version: 0.19.2
Config:
undefined
language-weave:not installed
indent-detective:
Version: 0.4.0
Config:
undefined
latex-completions:
Version: 0.3.6
Config:
undefined
versioninfo():
Julia Version 1.3.1
Commit 2d5741174c (2019-12-30 21:36 UTC)
Platform Info:
OS: Windows (x86_64-w64-mingw32)
CPU: Intel(R) Core(TM) i7-5500U CPU @ 2.40GHz
WORD_SIZE: 64
LIBM: libopenlibm
LLVM: libLLVM-6.0.1 (ORCJIT, broadwell)
Environment:
JULIA_EDITOR = "C:\Users\PoloskeiTamasHunor\AppData\Local\atom\app-1.44.0\atom.exe"  -a
JULIA_NUM_THREADS = 2
Status `C:\Users\PoloskeiTamasHunor\.julia\environments\v1.3\Project.toml`

[7d9fca2a] Arpack v0.4.0
[c52e3926] Atom v0.12.7
[6e4b80f9] BenchmarkTools v0.5.0
[336ed68f] CSV v0.5.25
[861a8166] Combinatorics v1.0.0
[7a1cc6ca] FFTW v1.2.0
[5789e2e9] FileIO v1.2.2
[59287772] Formatting v0.4.1
[033835bb] JLD2 v0.1.12
[e5e0dc1b] Juno v0.8.0
[dd61e66b] MDBM v0.1.4
[6fe1bfb0] OffsetArrays v1.0.2
[5fb14364] OhMyREPL v0.5.4
[14b8a8f1] PkgTemplates v0.6.4
[c46f51b8] ProfileView v0.6.3
[d330b81b] PyPlot v2.8.2
[93e0c654] Reduce v1.2.5
[295af30f] Revise v2.5.3
[123dc426] SymEngine v0.7.1
[37b6cedf] Traceur v0.3.0
[de0858da] Printf
[9abbd945] Profile

This is just an "issue" with your font, which displays \varphi differently in italics. Looks fine with e.g. Source Code Pro:


chore: flutter v3.22

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Checklist:

[x]  I have read freeCodeCamp's contribution guidelines.
[x]  My pull request has a descriptive title (not a vague title like Update index.md)


drivers: display: st7789v: add rotation feature

Adds rotation function for st7789v display driver
Opened issue #32286
Signed-off-by: Vitaliy Nimych<EMAIL_ADDRESS>

Tested with PineTime with 240x240 display. It worked after correcting the offset (see other comment).

You should squash the two commits into one.

You should rebase the branch to the latest main, as some changes are made to the st7789v driver.

Hi!
Yes, I received yesterday one display 240x240 for test
I want to finish my work, on New Year's Eve and start testing driver for 240x240 resolution.
Thanks for answer and help with testing.

Tested with PineTime with 240x240 display. It worked after correcting the offset (see other comment).

You should squash the two commits into one.
You should rebase the branch to the latest main, as some changes are made to the st7789v driver.

Hi! Yes, I received yesterday one display 240x240 for test
I want to finish my work, on New Year's Eve and start testing driver for 240x240 resolution.
Thanks for answer and help with testing.

Hello @cvetaevvitaliy. Can you perform the tests with this generic 240x240 display? I'm trying to test on the same display version (https://www.aliexpress.com/item/32915085705.html) and it doesn't work.

@cvetaevvitaliy please check my comments, and I tried and it is ok for my 240x240 lcd, it is ok!

@cvetaevvitaliy If you still want to continue this PR, please

resolve the review issue
squash the two commits into one
rebase the branch to the latest main, as some changes are made to the st7789v driver

If you still want to continue this PR, please
resolve the review issue
squash the two commits into one
rebase the branch to the latest main, as some changes are made to the st7789v drive

I will try to do it soon.  I am in Ukraine, it was hot for a couple of months


follows parent project changes

Codecov Report

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

@@            Coverage Diff            @@
##             master     #106   +/-   ##
=========================================
  Coverage     95.68%   95.68%
  Complexity      206      206
=========================================
  Files            28       28
  Lines           463      463
  Branches         87       87
=========================================
  Hits            443      443
  Misses            9        9
  Partials         11       11

Impacted Files
Coverage Δ
Complexity Δ

...ckson/datatype/serialize/JavaslangSerializers.java
81.81% <100%> (ø)
13 <0> (ø)
:x:

...n/datatype/deserialize/JavaslangDeserializers.java
81.81% <100%> (ø)
13 <0> (ø)
:x:

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 bff4792...878495e. Read the comment docs.


Add support for fetching descendant names for non-place entities.

API results:
non-place-descendants.webm
With this change, we can now do scatter plots for non-place entities:

Thanks Bo.


Corrections in README file

Hi there,
There were some corrections needed in README file.
For the Operate Client, at some places TaskList Client details were provided.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Parth, Shah seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Hi @parth-99,
Thanks for your contribution! Well apreciated :)


AccessLevel.UNSUPPORTED

A common pattern when implementing interfaces is to just throw an UnsupportedOperationException from some implementation methods.  In the case of setters, particularly, it would be nice to be able to do that this way:
@Getter @Setter(AccessLevel.UNSUPPORTED) final String value;

The generated setter would then look like this:
public void setValue(String value) { throw new UnsupportedOperationException(); }

If you have to throw an exception from a method you're implementing it means your class shouldn't implement that interface or you should split your interface into multiple ones.

What if you wanted the setter to be protected and yet throw UnsupportedOperationException? I think a new annotation, let's say @SetterUnsupported, or an additional parameter to @Setter would be better for this case.

A fair point.  Also, the same additional parameter could also be added to other annotations, like @Getter, @*Constructor, etc., to likewise generate a stub that always throws an exception.  Furthermore, the exception to be thrown could be specified as the value of the parameter.  Something like:
  @Getter @Setter(stub=UnsupportedOperationException.class) final String value;


Add DjangoShip to readme

Found another one.
https://www.djangoship.com

@nitverse wanna take this one?


[Utility] Local Proof of Stake CLI - CLI and RPC client [part 1/2] - Issue #112

Description
This PR updates the CLI so that it provides access to the Utility module commands via RPC calls
Issue
Part of Issue https://github.com/pokt-network/pocket/issues/112 but we decided to split the work in 2 separate PRs
Type of change
Please mark the options that are relevant.

[x] New feature, functionality or library

List of changes

Updated CLI
Refactored the previous implementation of the "debug" utility into it's own subcommand

Testing

[x] make test_all
[x] LocalNet w/ all of the steps outlined in the README

Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have tested my changes using the available tooling
[x] If applicable, I have made corresponding changes to related local or global README
[x] If applicable, I have added new diagrams using mermaid.js
[x] If applicable, I have added tests that prove my fix is effective or that my feature works

@deblasis

I want a simple README in the CLI package laying out the CLI structure

We will also need user usage and specification documents - but that can be done in a separate issue (please open followup)

To double down on what @andrewnguyen22 said, please do create a separate issue for instructions/docs for large changes like these.

I want a simple README in the CLI package laying out the CLI structure

We will also need user usage and specification documents - but that can be done in a separate issue (please open followup)

To double down on what @andrewnguyen22 said, please do create a separate issue for instructions/docs for large changes like these.

I agree with you both, will do shortly

Guys, I believe that when #163 is ready, there are gonna be lots of conflicts. Normally I would just squash and merge at this point but let's coordinate when we are all online. 🙂

Holding off on another review for this until we merge in #235 and rebase this on top of main.

All the comments should be addressed via commits or answers now.

With the exclusion of this one comment (https://github.com/pokt-network/pocket/pull/177#discussion_r998944555) which is pretty big, I'm happy to approve its PR. @deblasis can you create a follow up ticket for us to discuss how to implement it and do so?
@andrewnguyen22 PTAL if you see any other potential issues or blockers.

@deblasis Please re-request the review when this is ready

I think I need an answer from @andrewnguyen22 here: https://github.com/pokt-network/pocket/pull/177#discussion_r1003222441 but apart from that it's ready I believe.

@deblasis Please re-request the review when this is ready

I think I need an answer from @andrewnguyen22 here: #177 (comment) but apart from that it's ready I believe.

https://github.com/pokt-network/pocket/pull/177/files/27e36c2e94150e8cec43e9c5caa383b2d9940a60#r1009984269

Approving with a few minor comments, but otherwise approving because it's past the point of "good enough" and we'll iterate on main.
@deblasis I know we talked bout a Makefile or utility with examples of how to curl and such. Is that in a followup PR?

https://github.com/pokt-network/pocket/pull/169#issue-1346412216
scroll down a bit, under "demo". Obviously that's just markdown that we can package the way we want. Just let me know how and I'll do it.

@deblasis Noted that the demo is there. Will review #169 after we merge in 1/2 and 2/2 to make the conflict resolution easier.


Reading the project/deployment context from the current dir

$ cd ./my-app
$ now
...
> Deployed to https://my-app.nkzawa-zeit.now.sh

$ now logs
# logs of the latest deployment for the current dir when no URL is specified

$ now inspect
# ditto

It might be great if it could work since it's annoying to copy-paste/type/remember urls.

Thank you for creating this issue!
Please note that – in order for us to be able to handle each feature request with care – we have to consume all of them through a unified pipeline that makes it easier for us to prioritize, track and progress on the features our user base is interested in.
In turn, the Issues tab on this repository is best only be used for reporting bugs, which we can immediately act on.
For well-explained feature requests (like the one you just posted), please contact us at<EMAIL_ADDRESS>so that we can consider adding it to our roadmap.


Stats After Curse,Weaken etc.. (Feature request ??)

Hi, we found another problem, on our live server 0.56c-nightly we are used to stats workign like that:
100str = 100hits, when someone cast Weaken on me, stats are fe. 88str = 100 hits (hits without connection to str in this case)
Now it is work that after weaken your stats are 88str = 88 hits instantly, (connection)
Please can you make some feature for it ?
We found the code for it, when i comment it as bellow, it works as we need.
https://pastebin.com/TaZ4NS7A
https://pastebin.com/m5chry2a
It is in CCharStat.cpp

we are told about it in #185

it is not the same mate. One is lowering stats on Maxhits, the Weaken spell is lowering stats on Maxhits too after the change.
Nolok send me fix for first problem, but its not fixing the second. Thank why im mentioning this aswell.

ahh, ok
i hate that stats spells unequip all items if it's required str is more

done. Working perfectly.


LuCI Wifi not updated to reflect new options

daemon.notice netifd: radio0 (2539): Usage:    iw [options] dev  set channel  [NOHT|HT20|HT40+|HT40-|5MHz|10MHz|80MHz]
daemon.notice netifd: radio0 (2539): Options:
daemon.notice netifd: radio0 (2539):   --debug         enable netlink debugging
user.notice mac80211: Failed command: iw dev wlan0 set channel 40 HT40

I think iw as been updated to use new HT options but LuCI still save the options using the old HT options
I have to manually edit /etc/config/wireless and change the HT40 to HT40+ or HT40-

This is a bug of https://github.com/openwrt/openwrt/blob/master/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh. HT40 is a legal UCI value which is supposed to get translated to either HT40+ or HT40-. I believe the code at https://github.com/openwrt/openwrt/blob/master/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh#L514 is simply superfluous since the channel setting already happens in https://github.com/openwrt/openwrt/blob/master/package/kernel/mac80211/files/lib/netifd/wireless/mac80211.sh#L623


Does data control and responsibility by the customer or Microsoft?

Because I found different 3 sources of Microsoft, some o365 control by customer. Some control by Microsoft. I confuse.
Does data control and responsibility by the customer or Microsoft?
https://docs.microsoft.com/en-us/microsoft-365/enterprise/ebcm-customer-and-cloud-partner-ebcm-responsibilities?view=o365-worldwide
https://www.microsoft.com/security/blog/2018/06/19/driving-data-security-is-a-shared-responsibility-heres-how-you-can-protect-yourself/

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

ID: f4ec59b4-502b-1a20-cde0-ab08647fc86a
Version Independent ID: 8cb55ad6-b271-a597-aff7-47d4c0f3ec5f
Content: Shared responsibility in the cloud - Microsoft Azure
Content Source: articles/security/fundamentals/shared-responsibility.md
Service: security
Sub-service: security-fundamentals
GitHub Login: @TerryLanfear
Microsoft Alias: terrylan

@OrawanO Thank you for your feedback . We will investigate and update the thread .

@OrawanO The customer is always in control of the data .  Microsoft engineers do not have access to customer data. Only the support teams have a very limited level of read-only access to customer data only when any customer opens a support case. This is done just to make sure that troubleshooting the issue for the customer takes less time.
Hence data control (who has rights to data and who doesn't) is something which is totally with the customer. Microsoft stores the data for the customer on our side and its availability and is guaranteed by Microsoft . We provide tools for governance and rights management to the customers.
The three article that you have mentioned provide the same details about the customer data. We call it a shared responsibility because the security of the datacenter level , security at the hardware level and security at the platform level is managed by us but data security within the customer's instance of the Microsoft product like Microsoft 365/PowerBi is managed by the customer. So this is a joint effort .
Hope the above explanation helps. We will now close this issue. Should you have any further queries , feel free to let us know and we will be happy to help you.

#please-close


[ceph-osd][main] Fix key when retrieving osdmap

For the nautilus version of ceph, osdmap is a nested dict with another
osdmap dict inside:
root@mon1:~# ceph --cluster ceph -s -f json | jq '.osdmap'
{
  "osdmap": {
    "epoch": 13,
    "num_osds": 3,
    "num_up_osds": 3,
    "num_in_osds": 3,
    "num_remapped_pgs": 0
  }
}
root@mon1:~# ceph --version
ceph version 14.2.11 (f7fdb2f52131f54b891a2ec99d8205561242cdaf) nautilus (stable)

We were only extracting the first one and ended up failing to check
the number of registered osds when setting them up.
Before the fix:
TASK [ceph-osd : wait for all osd to be up] *************************************************************
Tuesday 11 August 2020  22:20:29 +0000 (0:00:00.558)       0:01:39.088 ********
skipping: [osd1]
skipping: [osd2]
fatal: [osd3]: FAILED! =>
  msg: 'The conditional check ''(wait_for_all_osds_up.stdout | from_json)["osdmap"]["num_osds"] | int > 0'' failed. The error was: error while evaluating conditional ((wait_for_all_osds_up.stdout | from_json)["osdmap"]["num_osds"] | int > 0): ''dict object'' has no attribute ''num_osds'''

After:
TASK [ceph-osd : wait for all osd to be up] *************************************************************
Tuesday 11 August 2020  22:24:21 +0000 (0:00:00.672)       0:01:38.898 ********
skipping: [osd1]
skipping: [osd2]
ok: [osd3 -> mon1]

@david-caro are you well deploying nautilus with stable-4.0 ?

@david-caro are you well deploying nautilus with stable-4.0 ?

I was using stable-4.0.25 at the start, but changed to latest master as I had issues with some of the parameters missing and such.
But yep, you are right, I might have messed something up as 4.0.25 has the correct key path:
david@magnum$ git diff origin/stable-4.0.25 origin/master -- roles/ceph-osd/tasks/main.yml
diff --git a/roles/ceph-osd/tasks/main.yml b/roles/ceph-osd/tasks/main.yml
index 7a9f8052..3bc8489d 100644
--- a/roles/ceph-osd/tasks/main.yml
+++ b/roles/ceph-osd/tasks/main.yml
@@ -83,8 +83,8 @@
   changed_when: false
   delegate_to: "{{ groups[mon_group_name][0] }}"
   until:
-    - (wait_for_all_osds_up.stdout | from_json)["osdmap"]["osdmap"]["num_osds"] | int > 0
-    - (wait_for_all_osds_up.stdout | from_json)["osdmap"]["osdmap"]["num_osds"] == (wait_for_all_osds_up.stdout | from_json)["osdmap"]["osdmap"]["num_up_osds"]
+    - (wait_for_all_osds_up.stdout | from_json)["osdmap"]["num_osds"] | int > 0
+    - (wait_for_all_osds_up.stdout | from_json)["osdmap"]["num_osds"] == (wait_for_all_osds_up.stdout | from_json)["osdmap"]["num_up_osds"]
   when:
     - inventory_hostname == ansible_play_hosts_all | last

Closing this, thanks!


community: Added timestamp for messages in Firestore Chat Message History

Description: Added Firestore server timestamp to know the date when the messages was stored there.
Issue: N/A
Dependencies: N/A
Twitter handle: @Solaucas99

@efriis


Add files via upload

updated version of EBeam_heaters_snewman_RMA1.gds
Removed heater section that was intended to be electrical routing.
Added (2) new designs.

Please check the verification report. It is now working.

you have multiple top cells. please fix.

You have many maufacturing DRC errors in the metal.  See screenshot.

Closing pull request.  I'll submit the update for EBeam_heaters_snewman_RMA1.gds, which is DRC clean.  I'll work to address the issues with the new designs separately.


Make generated Junior blocks always connect to each other

Previously, we would sometimes put them in separate stacks, and if they were inside another block, that would also involve adding a newline block.
I don't remember exactly why we did this, but I think it had something to do with CodeCombat and newlines and comments and such things being important.
In any case, we don't seem to need it in CodeCombat Junior, and this code change seems to do the trick, while not having any effect outside of Junior.
Able to remove a long function that was counteracting these newline blocks for maxBlocks counting in CCJ as well. (That I just added today.)
Fixes CCJ-285. Fixes CCJ-293. Fixes CCJ-284.
Before: example of auto-generated blocks having gaps and (newline) blocks:

After: everything's snug:

Summary by CodeRabbit

New Features

Enhanced error handling and session management in the LevelLoader, improving stability during loading processes.
Streamlined block linking and conversion for junior users, optimizing their experience with code-to-blocks functionality.

Bug Fixes

Simplified logic in SpellView for determining maximum block counts, eliminating unnecessary complexity.

Refactor

Removed outdated methods and language-specific logic in SpellView, focusing on a more generalized approach to block counting.

Ah, right, I had just added countSameLevelBlocks for counting how many (newline) blocks would be added in Python and adding that to the maxBlocks limit, but now we don't need the (newline) blocks in CCJ any more because of this change.


add 3 missing fields to CratesResponse

add fields: versions, keywords & categories

These are ready to be merged too.

Why are they optional?
Does the API return null if they are empty?

Let's make then not Option but instead default for serde.
#[serde(default)]
field: Vec<_>

Yeah. This field is used in at least 2 API responses, one of which doesn't include them, but another does.
I just made the requested change.

@joseluis thanks!


How to hide labels and charts fill that position?

I am trying to hide my eyes and make the chart fill the width of the screen. Is there any way to do that?

This is my code

hideLegend={true}

I don't believe this works for anything other than progress charts. i'd like to implement this on a bar or line graph

Oh sorry didn't know

https://www.youtube.com/watch?v=m8gyy7JItmU https://www.youtube.com/watch?v=1WZjeESH4a0


performance: apparts should preallocate typical borrow errors

Motivation
go tool pprof -http :8088 -focus "Borrow" cpu.prof

Analize
(*partitionRT).init
Definition
Decision
### Tasks
- [ ] func `(*partitionRT).init()` should return preformated errors

Results
Was

Now


Use inExpression in a nullsafe way

peekLast is a JDK method using platform types for the return value.

@hick209

Is this fixing an issue that you have seem or just a precaution?

I mostly care because our internal build has some additional null checking for JDK classes, which is triggering on this code. However, this version will also crash on unbalanced use of the stack, which is nice.

Ran into merge conflicts while trying to land this. @nreid260 would you mind rebasing it?

Nevermind, it was simple enough. I've rebased it


Slow Count Query with Relation Filter PostgreSQL

Bug description
query count with relation getting slower after 5 times request, this issues persist with more than 400k++ rows data being counted

I manage to forcing disconnect client by calling await prisma.$disconnect() after calling query count to temporary fix this issue, but this method will decrease performance of prisma at all, since this function await prisma.$disconnect() will take some time to reconnect all of clients.
i have tried to using raw query, and transaction query but the issues still persist. i have tried to manually query with pgadmin4 to see its server related issues, but the query running well with pgadmin4
Notes:
i have same method with different table (smaller rows data) and its working properly without forcing client to disconnect
How to reproduce
i have create some project to reproduce the issues you can clone from this repo https://github.com/BagasNS/prisma-reproduce-slow-query then follow readme
Expected behavior
query count not getting slow without disconnecting the client (calling await prisma.$disconnect())
Prisma information

// This is your Prisma schema file,
// learn more about it in the docs: https://pris.ly/d/prisma-schema

generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model accounts {
  id_account        String           @id @default(uuid())
  full_name         String
  calon             calon?
  surveyor          surveyor?
  pemilih           pemilih?
}

model calon {
  id_calon                 String                     @id @default(uuid())
  id_account               String                     @unique
  account                  accounts                   @relation(fields: [id_account], references: [id_account])
  dukungan                 dukungan[]
}

model pemilih {
  id_pemilih        String            @id @default(uuid())
  id_account        String            @unique
  account           accounts          @relation(fields: [id_account], references: [id_account])
  dukungan          dukungan[]
}

model surveyor {
  id_surveyor        String           @id @default(uuid())
  id_account        String           @unique
  account           accounts         @relation(fields: [id_account], references: [id_account])
  dukungan          dukungan[]
}

model dukungan {
  id_dukungan    String     @id @default(uuid())
  id_pemilih     String
  pemilih        pemilih    @relation(fields: [id_pemilih], references: [id_pemilih])
  id_surveyor    String
  surveyor       surveyor    @relation(fields: [id_surveyor], references: [id_surveyor])
  level_dukungan LevelDukungan // enum
  id_calon       String
  calon          calon      @relation(fields: [id_calon], references: [id_calon])
  created_at     DateTime   @default(now()) @db.Timestamptz(3)
  updated_at     DateTime   @default(now()) @db.Timestamptz(3)

  @@unique([id_pemilih, level_dukungan, id_calon])
}

enum LevelDukungan {
  A
  B
  C
  D
} // Real Enum Has Been Replaced

let nama = req.query.nama || "";
let limit = parseInt(req.query.limit) || 10; // Default Limit
let page = parseInt(req.query.page) || 1;

console.time('GET PAGINATED DATA')
let dukungan = await prisma.dukungan.findMany({
  where: {
    pemilih: {
      account: {
        full_name: {
          contains: nama,
          mode: 'insensitive'
        }
      }
    },
    id_calon: calon.id_calon,
  },
  select: {
    pemilih: {
      select: {
        id_pemilih: true,
        account: {
          select: {
            full_name: true
          }
        }
      }
    },
    surveyor: {
      select: {
        id_surveyor: true,
        account: {
          select: {
            full_name: true
          }
        }
      }
    },
    created_at: true
  },
  skip: limit * (page - 1),
  take: limit
});
console.timeEnd('GET PAGINATED DATA')

console.time('GET COUNT ALL DATA')
let total_data = await prisma.dukungan.count({
    where: {
        pemilih: {
            account: {
                full_name: {
                    contains: nama,
                    mode: 'insensitive'
                }
            }
        },
        id_calon: calon.id_calon,
    }
})
console.timeEnd('GET COUNT ALL DATA')

Environment & setup

OS: Windows 10, MacOS Big Sur (11.7.X), MacOS Venture (13.1), Google App Engine (Not sure what google using)
Database: PostgreSQL 14
Node.js version: 18

Prisma Version
prisma                  : 4.9.0
@prisma/client          : 4.9.0
Current platform        : windows
Query Engine (Node-API) : libquery-engine ceb5c99003b99c9ee2c1d2e618e359c14aef2ea5 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli ceb5c99003b99c9ee2c1d2e618e359c14aef2ea5 (at<EMAIL_ADDRESS>Introspection Engine    : introspection-core ceb5c99003b99c9ee2c1d2e618e359c14aef2ea5 (at<EMAIL_ADDRESS>Format Binary           : prisma-fmt ceb5c99003b99c9ee2c1d2e618e359c14aef2ea5 (at<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.9.0-42.ceb5c99003b99c9ee2c1d2e618e359c14aef2ea5
Default Engines Hash    : ceb5c99003b99c9ee2c1d2e618e359c14aef2ea5
Studio                  : 0.479.0
Preview Features        : filteredRelationCount

That looks ... weird. We will try to reproduce.
To maybe help us in understanding: 1 dukungan can have n pemilih which then has 1 accounts - is that correct? And your search wants to show all dukungan that are connected to an accounts where full_name contains a certain string?

1 dukungan can only have 1 pemilih then 1 pemilih can only have 1 accounts
1 pemilih can have n dukungan

and i want to show all dukungan that connected to pemilih then connected to accounts where accounts.full_name contains some string.
anyway thanks for the response!

Ah right, I was reading the wrong direction again.
While it is still generating the seed data for me right now, maybe a (somewhat offtopic but still related) question:
Wouldn't it be easier to write the query starting with account with its where condition, and then include the pemilih and dukungan for the results it finds?

I can confirm the fundamental problem you are reporting:
PS C:\Users\Jan\Documents\throwaway\17406> node .

Query: SELECT COUNT(*) FROM (SELECT "public"."dukungan"."id_dukungan" FROM "public"."dukungan" WHERE ("public"."dukungan"."id_dukungan") IN (SELECT "t0"."id_dukungan" FROM "public"."dukungan" AS "t0" INNER JOIN "public"."pemilih" AS "j0" ON ("j0"."id_pemilih") = ("t0"."id_pemilih") WHERE (("j0"."id_pemilih") IN (SELECT "t1"."id_pemilih" FROM "public"."pemilih" AS "t1" INNER JOIN "public"."accounts" AS "j1" ON ("j1"."id_account") = ("t1"."id_account") WHERE ("j1"."full_name" ILIKE $1 AND "t1"."id_pemilih" IS NOT NULL)) AND "t0"."id_dukungan" IS NOT NULL)) OFFSET $2) AS "sub"
Params: ["%%",0]
Duration: 7898ms
GET COUNT ALL DATA: 7.904s
PROCESS TIME: 7.921s
=== ITERATION 6 END ===

Next step: Get actual query duration from database to see if this is on the database or Prisma Client/Engine side.

here some interesting info. it seems count by ORM are the problem, when i try using raw query using this project https://github.com/BagasNS/prisma-reproduce-slow-query it working properly.

but the wierd things is, if query count by ORM are the problem, why counting by ORM always start slowing down from iteration 6?
FYI: when query is slowing down at iteration 6, its not affecting another query, only counting at same method are affected, no matter how much connection pooling are. For Example in my real project using express js, there are some middlewares then some input validations that using prisma query, then request forward to getDataPagination. middleware and input validation are ok when prisma slowing down at method getDataPagination


kdeconnect is broken in 20.09

Describe the bug
The kdeconnect widget in the KDE panel shows:
Error loading QML file: file:///nix/store/78r8ihcgk25cj91d5bk8l5z6xcvxqli9-kdeconnect-1.3.5/share/plasma/plasmoids/org.kde.kdeconnect/contents/ui/main.qml:25:1: module "org.kde.kdeconnect" is not installed

Also, going to the "KDE Connect" panel in the KDE System Settings shows the error message The shared library was not found.
Notify maintainers
@FRidh
Metadata
$ nixos-version
20.09.20201006.7badbf1 (Nightingale)

It's possible we should update it: https://invent.kde.org/network/kdeconnect-kde/-/tags thought it's not clear whether we should choose 20.08.1 or 1.4.0. I pushed some new dependencies we'll need in order to update it in https://github.com/NixOS/nixpkgs/pull/99956 . Here's a diff for the kdeconnect update, which doesn't work, hence I didn't push it to https://github.com/NixOS/nixpkgs/pull/99956 :
:100644 100644 c3d2feb2fed 1860b66c09e M	pkgs/applications/misc/kdeconnect/default.nix
:100644 100644 eaa37e1fe2a 752c5c50cd5 M	pkgs/top-level/all-packages.nix

diff --git a/pkgs/applications/misc/kdeconnect/default.nix b/pkgs/applications/misc/kdeconnect/default.nix
index c3d2feb2fed..1860b66c09e 100644
--- a/pkgs/applications/misc/kdeconnect/default.nix
+++ b/pkgs/applications/misc/kdeconnect/default.nix
@@ -13,25 +13,45 @@
 , libfakekey
 , libXtst
 , qtx11extras
+, qtmultimedia
 , sshfs
 , makeWrapper
 , kwayland
 , kio
+, kpeoplevcard
+, kpeople
+, kirigami2
+, pulseaudio-qt
 }:

 mkDerivation rec {
   pname = "kdeconnect";
-  version = "1.3.5";
+  version = "20.08.1";

   src = fetchurl {
-    url = "mirror://kde/stable/${pname}/${version}/${pname}-kde-${version}.tar.xz";
-    sha256 = "02lr3xx5s2mgddac4n3lkgr7ppf1z5m6ajs90rjix0vs8a271kp5";
+    url = "https://download.kde.org/stable/release-service/${version}/src/${pname}-kde-${version}.tar.xz";
+    sha256 = "0s76djgpx08jfmh99c7kx18mnr3w7bv4hdra120nicq89mmy7gwf";
   };

   buildInputs = [
-    libfakekey libXtst
-    ki18n kiconthemes kcmutils kconfigwidgets kdbusaddons knotifications
-    qca-qt5 qtx11extras makeWrapper kwayland kio
+    libfakekey
+    libXtst
+    qtmultimedia
+    pulseaudio-qt
+    kpeoplevcard
+    kpeople
+    kirigami2
+    ki18n
+    kiconthemes
+    kcmutils
+    kconfigwidgets
+    kdbusaddons
+    knotifications
+    qca-qt5
+    qtx11extras
+    makeWrapper
+    kwayland
+    kio
   ];

   nativeBuildInputs = [ extra-cmake-modules kdoctools ];
diff --git a/pkgs/top-level/all-packages.nix b/pkgs/top-level/all-packages.nix
index eaa37e1fe2a..752c5c50cd5 100644
--- a/pkgs/top-level/all-packages.nix
+++ b/pkgs/top-level/all-packages.nix
@@ -21555,7 +21555,7 @@ in

   k4dirstat = libsForQt5.callPackage ../applications/misc/k4dirstat { };

-  kdeconnect = libsForQt514.callPackage ../applications/misc/kdeconnect { };
+  kdeconnect = libsForQt5.callPackage ../applications/misc/kdeconnect { };

   inherit (kdeFrameworks) kdesu;

Applying this patch causes ld errors. Using the same patch but libsForQt514.callPackage for kdeconnect is closest I got, but it fails with an unfound kcmutils_version.h include.

we indeed should use 20.08.1.

Fixed in https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/328

Updating kdeconnect is inseparable from https://github.com/NixOS/nixpkgs/pull/99956 so I'm pushing it there.

This issue still exists on master and release-20.09.

I noticed a similar problem with the printer widget in the KDE panel:
Error loading QML file: file:///nix/store/4mqinkdaq1r00hqicrzwk8a3i86hyw8b-print-manager-20.08.1/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/printmanager.qml:64:34: Type PopupDialog unavailable
file:///nix/store/4mqinkdaq1r00hqicrzwk8a3i86hyw8b-print-manager-20.08.1/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PopupDialog.qml:81:23: Type PrinterItem unavailable
file:///nix/store/4mqinkdaq1r00hqicrzwk8a3i86hyw8b-print-manager-20.08.1/share/plasma/plasmoids/org.kde.plasma.printmanager/contents/ui/PrinterItem.qml:28:1: Type PlasmaExtras.ExpandableListItem unavailable
file:///nix/store/a9q5wr6ygfkdb85lz0n37508y12a1pgn-plasma-framework-5.73.0-bin/lib/qt-5.12.7/qml/org/kde/plasma/extras/ExpandableListItem.qml:20:1: module "QtQuick" version 2.14 is not installed

Yeah, mixing 3 different versions of Qt in one system really isn't ideal...

A similar issue we had fixed in https://github.com/NixOS/nixpkgs/pull/99956 appears with the set kdeApplications. See https://github.com/NixOS/nixpkgs/issues/100707 .

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/what-should-stable-nixos-prioritize/9646/1


Hide Cells in the Notebook History Viewer

Right now the history viewer does not reflect which cells are hidden in the notebook. We should be able to run the same code we use in the main notebook to create "placeholders" for hidden cells, and even enable hidden cell preview using a detailed tooltip, but I don't think we want users to be able to click these placeholders to open the cells in an embedded sidebar.

The last thing to fix is getting a name for the hidden cell markers. For now we default everything to "Hidden Cells". Fixing this would involve tracking changes to hidden cell names over time, which is a larger feature, so closing this issue for now.


Fix error Ts(2742) Update vue-query.ts

The inferred type of 'client ' cannot be named without a reference to '@ts-rest/vue-query/src/lib/use-mutation'. This is likely not portable. A type annotation is necessary.

You need to manually annotate your exported client
const options = {
  baseUrl: 'http://localhost:3000',
} satisfies Parameters<typeof initQueryClient>[1];

export const client: InitClientReturn<typeof contract, typeof options> = initQueryClient(contract, options);


Add ES6 template strings and/or template-functions for SELECT

The idea is to mix SQL and JavaScript variables in one string, like ES6 does:
    var filename = 'myfile.xlsx';
    alasql('SELECT * FROM XLSX("${filename}")',[],function(res){ ... });

instead of:
    alasql('SELECT * FROM XLSX("'+filename'+'")',[],function(res){ ... });

In this case Alasql will make this conversion at the parsing time, but not execution. In future versions will allow to have execution time JavaScript variables (with double backquotes):
    alasql('SELECT * FROM XLSX("``filename``"',[],function(res){ ... });

Another idea - to have internal templater for SELECT output, like:
    alasql.tmpl.mytmpl = '<div>{%= o.id %}</div>';
    var res = alasql('SELECT * TEMPLATE tmpl() FROM one');

This template function will be useful for XLSX export function.

Negative. Closed.

(Agree on not implementing. This is an issue with the user and the "string creating" javascript engine used - hopefully ES6 will be the norm soon :) )

Multiline strings are already in Chrome, but not in Node...

Seams like io.js and node.js is merging - so think multiline string are not far in the node world :)

Ok. I still think about templater, but probably we will keep it for plugins. I thnik that ORM is more in priority, that template-base SQL genereation


mod hola

@yu-sasaki0 - I'm glad to see you're trying out the examples! This PR is for the main branch of the actual demo repo from your fork, so I'm not going to merge it in, but let me know if you have any questions. Best of luck and thanks for trying out the demo!


Blog app: Add devise

Implemented features:

Remove current_user method in ApplicationController
Install and setup devise.

Can register a new user
User logs in with a combination of email and password
Hashed password should be stored in the database
Ask for confirmation of email
Can reset password
modify the views in devise](https://github.com/heartcombo/devise#configuring-views) for registration and login to match the wireframes from the Sneak Peek

Thank you for the approval


Design Kit

Do you have any design kits or components available for Lightweight Charts?
When building the high-fidelity wireframes, we use component libraries to reflect what the live product will look like.
For example, Material UI is Google's component library. They publish a design kit for designers to use for their high-fidelity wireframes. The design kit includes buttons, text fields, and other parts of a web app.
A design kit would be helpful.

Do you have any design kits or components available for Lightweight Charts?

There aren't any design kits available for the library at the moment.
I agree that a design kit would be useful when building high-fidelity wireframes, however I don't think we can justify the creation and ongoing maintenance effort required to provide this at the moment.
Leaving the issue open to gauge interest from the community.


optimize integration testing in CI

This adds a new option, integration which is used to list platforms to use in integration testing (CI) and avoids whitelisting platforms. This will enable running those tests on real hardware if the --integration option is omitted.
--integration option is now not default, in the future this will be the default and will build/test a minimal set, running sanitycheck with more coverage will be possible use another option.
oh, one more thing in this PR: use native_posix exclusively where it makes sense and avoid massive build/running trivial stuff that is being tested elsewhere anyways..

stats:
current master:
i9:zephyr(master): sanitycheck -y
Renaming output directory to /home/nashif/Work/zephyrproject/zephyr/sanity-out.5
INFO    - JOBS: 20
INFO    - Selecting default platforms per test case
INFO    - Building initial testcase list...
INFO    - 4206 test configurations selected, 202630 configurations discarded due to filters.
INFO    - Completed in 3 seconds

this PR with no options:
i9:zephyr(sanitycheck/optimize_tests): sanitycheck -y
Renaming output directory to /home/nashif/Work/zephyrproject/zephyr/sanity-out.3
INFO    - JOBS: 20
INFO    - Selecting default platforms per test case
INFO    - Building initial testcase list...
INFO    - 4444 test configurations selected, 202392 configurations discarded due to filters.
INFO    - Completed in 3 seconds

this PR with -G
i9:zephyr(sanitycheck/optimize_tests): sanitycheck -y -G
Renaming output directory to /home/nashif/Work/zephyrproject/zephyr/sanity-out.4
INFO    - JOBS: 20
INFO    - Selecting default platforms per test case
INFO    - Building initial testcase list...
INFO    - 4033 test configurations selected, 202803 configurations discarded due to filters.
INFO    - Completed in 3 seconds

@nashif do you think it would be feasible to override integration boards locally ? (I'm thinking about a new prop in map.yaml)

@nashif do you think it would be feasible to override integration boards locally ? (I'm thinking about a new prop in map.yaml)

why would you want to do that? you can still run on any boards with full coverage by specifying the boards directly.

why would you want to do that? you can still run on any boards with full coverage by specifying the boards directly.

Maybe I'm not quite clear with the new option. And reading again the description, I'm actually more confused. I understand the interest of removing the withelisting, but I'm not clear why the integration makes things better.
Can you provide more details on the problematic you're tackling here ?

Can you provide more details on the problematic you're tackling here ?

--integration helps optimize the coverage for CI runs, everything else is kept the same or is improved by relying on up2date information from dts re hardware availability and support.
The goal is not to randomly build and run tests and instead do this in the most optimal way balance coverage with run-time required in CI when someone submits a PR.

The goal is not to randomly build and run tests and instead do this in the most optimal way balance coverage with run-time required in CI when someone submits a PR.

Get it better, txs

Did I understand this patch well: apart form what listed under integration, qemu_x86 will be always one of  CI target as well (if filters mach?).
Currently settings, storage and FS are tested in CI on either qemu and posix (which is great, and i really like as extensive testing are problematic for flash endurance). I wan't to avoid disabling these test in CI accidentally.
BTW: some of commits here are helpers patches, but not strongly connected and can go to the master independently, even right now.

superseded with #28435


KioskPlugin.exitKiosk() does not seem to work

This issue is occurring using Genymotion v2.12.0 Android emulator with S7 Android 6.0.0 API 23 image.
The app has a button, 'Exit Kiosk Mode' when it is clicked I can see the KioskPlugin.exitKiosk(); firing but still cannot switch app or access settings to change default launcher.
If the command KioskPlugin.exitKiosk(); is run directly in the console it returns undefined.
Any suggestions?
Thanks.

Does KioskPlugin.isInKiosk(function(isInKiosk){ alert(isInKiosk); }); returns true for you? (=is activity from this plugin running?)
Does KioskPlugin.isSetAsLauncher(function(isLauncher){ alert(isLauncher); }); returns true for you? (=is that activity set as launcher?)

Thanks for clarification.
I went into that menu to manually set the launcher to the app initially. When exitKiosk is fired through there is no menu displayed to choose the launcher.
This Android image provide the choice of two launchers by default, Pixel Launcher and Google Launcher.
I cannot get back into settings or anything so I have to delete the image.
Have you tried on Genymotion android image? Perhaps the root cause of this behavior has to do with the android image that is supplied by the emulator.
If you test with Genymotion, probably a good idea to clone the test image you use test the plugin to avoid having to recreate the image from scratch.

Hi, I can rule out that this issue is not caused by using a Genymotion android image.
I have tried with POP7 Alcatel Tablet. I can confirm no launch selector menu is displayed when using this function on this device.
KioskPlugin.exitKiosk();

Can you obtain list of installed launchers (activities for using in intent) on your testing device/emulator?

Yes, launchers on Genymotion Android S7 image are 'Google Now Launcher' and 'Pixel Launcher'.
I did some more testing today and was able to get the Select launcher dialog to display using this plugin (https://github.com/guatedude2/cordova-plugin-kiosk-launcher) which is a based on your plugin.
In your codebase the function is exitKiosk and guatedude2 it is switchLauncher.
Comparing the two native Android calls they seem nearly identical except for one line.
KioskActivity.kioskModeEnabled = false;
guatedude2
       } else if (SWITCH_LAUNCHER.equals(action)) {
                KioskActivity.kioskModeEnabled = false;
                Intent intent = new Intent(Intent.ACTION_MAIN);
                intent.addCategory(Intent.CATEGORY_HOME);
                intent.setFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP);

                Intent chooser = Intent.createChooser(intent, "Select destination...");
                if (intent.resolveActivity(cordova.getActivity().getPackageManager()) != null) {
                    cordova.getActivity().startActivity(chooser);
                }

                callbackContext.success();
                return true;
            }

hkalina
           } else if (EXIT_KIOSK.equals(action)) {

                Intent intent = new Intent(Intent.ACTION_MAIN);
                intent.addCategory(Intent.CATEGORY_HOME);
                intent.setFlags(Intent.FLAG_ACTIVITY_CLEAR_TOP);

                Intent chooser = Intent.createChooser(intent, "Select destination...");
                if (intent.resolveActivity(cordova.getActivity().getPackageManager()) != null) {
                    cordova.getActivity().startActivity(chooser);
                }

                callbackContext.success();
                return true;

That is weird - both projects use identical code for existKiosk...
Can you record and provide log from adb logcat ?
If you can, try to add following additional debug output:
                if (intent.resolveActivity(cordova.getActivity().getPackageManager()) != null) {
                    cordova.getActivity().startActivity(chooser);
                    System.out.println("Kiosk: activity chooser started"); // this
                } else {
                    System.out.println("Kiosk: unable to resolve launcher activity"); // and this
                }

Unable to reproduce - closing - feel free to reopen if will find steps to reproduce the issue.

Haven't had a chance to test yet. I will test again with screen recording and share results here. Thanks.

No screen recording needed - I need way to reproduce the issue on my machine or more info at least.
Please, try to compile and run the demo app: https://github.com/hkalina/cordova-kiosk-demo
If there WILL be the same problem, check your build environment/downloaded Android image - it is working for me on image you mentioned.
If there WILL NOT be the same problem, try to find what is different in your project - send source of minimal failing project here.

I will be using Meteor sample Todo application (https://github.com/meteor/todos) to replicate. Actual project which  would not display Launch screen is also Meteor-based application. I'll commit code to a new repo so that it can be reproduced on your end.
The Meteor app is built with same HTML/CSS/Javascript so very similar the sample kiosk-demo you created for this plugin.
I'm as puzzled as your are as to why this issue is occurring. I'll do a screen record just so we're completely on the same page as to what might be the root cause.

Hello, similar proplem, exitKiosk does nothing.
But if I read correctly, in my case I wuld need a real exit kiosk: Some way to disable kiosk, or prevent it from starting, actually I can only exit the application and no send it in background, how could I achieve it?

@LucaColombi the exitKiosk() should show launcher selection - which allows to switch to regular lanuncher and the current task is sent to background. Can you provide steps to reproducing?

@hkalina @LucaColombi  I'm developing an Ionic application and had the same issue where the exitKiosk does nothing (isInKiosk returns true, isSetAsLauncher returns true).
Tested on a Samsung Note 8
My workaround for now is this.platform.exitApp(); which closes the application and gives me the opportunity to switch launchers


fix: add check script in README.md example

Thanks for this @tincho70 ! I fix this in the last commit before see your PR.


kbfsedits: includes at least 3 self-clusters in the overall user history

(Depends on #1631.)
This is the first attempt at making sure your own recent write history appears in the overall edit history, even if they were a long time ago.  The desired behavior, for now:

Make sure there are always 3 TLF-writer clusters for yourself in the list.
Sort them into the list according to the regular algorithm -- i.e., if they happened a long time ago, they will still appear at the bottom.
Don't do anything special for the public folder -- if it happens to be one of the top-3 self-clusters, it will make the list; if not, it won't.

To make this happen, this PR:

Creates a special "#self" kbfs-edits notification channel in the logged-in user's private conversation.
On every "normal" notification, it writes the name and type of the TLF into this "#self" channel.

But as a best-effort optimization, it tries to make sure that whatever it writes is different from the last write to the "#self" channel, so we don't build up a bunch of useless duplicate entries.

When loading the inbox, it makes sure the last 3 unique TLFs from the "#self" channel are included.
TlfHistory never trims the logged-in user's writes from the history.
UserHistory always includes at least 3 clusters by the logged-in user in the overall history.

Issue: KBFS-3080

Appveyor is being fixed separately.


Review API Surface area in Steeltoe.Security

See https://github.com/SteeltoeOSS/Steeltoe/issues/897#issuecomment-1198088843.

@TimHess Do we still need to do anything here, or can it be closed?


Failed parsing JSON input

I am getting an error when using the code exactly as given in the Interactive Chart js. It yields:
(function () { /* illegal callback name */ })({"ExceptionType":"Exception","Message":"Failed parsing JSON input","Details":"Internal.MODApis","InnerException":null})
Is there something I am missing?

Hi there @mjdguyler , sorry to hear you are encountering issues with the provided code. Would you be able to provide some more information? Here are a couple of different options that would make it much easier for us to help get you up and running:

The full api url that is being hit along with the parameters (you should be able to find this in chrome debug tools under the network tab)
A hosted url to your project so that we can debug ourselves
An exported .har file from chrome for the API request (see attached screenshot)

Hopefully we can help you get you back up and running!

Parameters:
parameters:
"{"Normalized":false,"NumberOfDays":3650,"DataPeriod":"Day","Elements":[{"Symbol":"APPL","Type":"price","Params":["ohlc"]},{"Symbol":"APPL","Type":"volume"}]}"
URL:
url: "http://dev.markitondemand.com/Api/v2/InteractiveChart/jsonp",
Attached is the HAR.
The website cannot be attached as it is running on localhost. I downloaded
the code as you had it on GitHub and added inside my .js file a call to
give parameters and make the new Markit.InteractiveChartApi like in the
demo.
Thanks for the quick response.
Mark
On Wed, May 20, 2015 at 11:00 AM, Ali Khatami<EMAIL_ADDRESS>wrote:

Hi there @mjdguyler https://github.com/mjdguyler , sorry to hear you
are encountering issues with the provided code. Would you be able to
provide some more information? Here are a couple of different options that
would make it much easier for us to help get you up and running:

The full api url that is being hit along with the parameters (you
should be able to find this in chrome debug tools under the network tab)
A hosted url to your project so that we can debug ourselves
An exported .har file from chrome for the API request (see attached
screenshot) [image: image]
https://cloud.githubusercontent.com/assets/1418016/7732750/3e696292-fee7-11e4-925b-4892bd1512d6.png

Hopefully we can help you get you back up and running!
—
Reply to this email directly or view it on GitHub
https://github.com/markitondemand/DataApis/issues/18#issuecomment-103975319
.

@mjdguyler It doesn't look like the entire har was attached can you instead try copying the full url using google chrome. I'm using http://markitondemand.github.io/DataApis/InteractiveChartSample/ as an example:
The full url should look like this...
Escaped
http://dev.markitondemand.com/Api/v2/InteractiveChart/jsonp?callback=jQuery110209236548591870815_1432147464499&parameters={"Normalized"%3Afalse%2C"NumberOfDays"%3A3650%2C"DataPeriod"%3A"Day"%2C"Elements"%3A[{"Symbol"%3A"AAPL"%2C"Type"%3A"price"%2C"Params"%3A["ohlc"]}%2C{"Symbol"%3A"AAPL"%2C"Type"%3A"volume"}]}&_=1432147464500
Unescaped
"http://dev.markitondemand.com/Api/v2/InteractiveChart/jsonp?callback=jQuery110209236548591870815_1432147464499&parameters={"Normalized":false,"NumberOfDays":3650,"DataPeriod":"Day","Elements":[{"Symbol":"AAPL","Type":"price","Params":["ohlc"]},{"Symbol":"AAPL","Type":"volume"}]}&_=1432147464500

Here is what you asked for:
http://dev.markitondemand.com/Api/v2/InteractiveChart/jsonp?callback=jQuery1102006651935772970319_1432145887816&parameters={"Normalized"%3Afalse%2C"NumberOfDays"%3A3650%2C"DataPeriod"%3A"Day"%2C"Elements"%3A[{"Symbol"%3A"APPL"%2C"Type"%3A"price"%2C"Params"%3A["ohlc"]}%2C{"Symbol"%3A"APPL"%2C"Type"%3A"volume"}]}&_=1432145887817
Thanks,
Mark Guyler
On Wed, May 20, 2015 at 11:47 AM, Ali Khatami<EMAIL_ADDRESS>wrote:

@mjdguyler https://github.com/mjdguyler It doesn't look like the entire
har was attached can you instead try copying the full url using google
chrome. I'm using
http://markitondemand.github.io/DataApis/InteractiveChartSample/ as an
example:
The full url should look like this...
Escaped
http://dev.markitondemand.com/Api/v2/InteractiveChart/jsonp?callback=jQuery110209236548591870815_1432147464499&parameters={"Normalized"%3Afalse%2C"NumberOfDays"%3A3650%2C"DataPeriod"%3A"Day"%2C"Elements"%3A[{"Symbol"%3A"AAPL"%2C"Type"%3A"price"%2C"Params"%3A["ohlc"]}%2C{"Symbol"%3A"AAPL"%2C"Type"%3A"volume"}]}&_=1432147464500
Unescaped
"
http://dev.markitondemand.com/Api/v2/InteractiveChart/jsonp?callback=jQuery110209236548591870815_1432147464499&parameters={"Normalized":false,"NumberOfDays":3650,"DataPeriod":"Day","Elements":[{"Symbol":"AAPL","Type":"price","Params":["ohlc"]},{"Symbol":"AAPL","Type":"volume"}]}&_=1432147464500
[image: image]
https://cloud.githubusercontent.com/assets/1418016/7733704/1e2d5252-feee-11e4-8d08-db8af118f805.png
—
Reply to this email directly or view it on GitHub
https://github.com/markitondemand/DataApis/issues/18#issuecomment-103991921
.

@mjdguyler I am almost at a loss. I checked the API code and nothing seems to be out of the ordinary, but your URL does return an error. What's stranger still is that I took the parameters from my url, replaced the parameters in yours for reference, and it works! They look the same, but I'm wondering if there is some weird encoding in the string somewhere. Even after changing your callback value to my callback value yours still failed. I've gotten to the point where I think it might be some type of encoding issue with your page. Is your page in UTF8?
Check out these example urls for reference:
Works
http://dev.markitondemand.com/Api/v2/InteractiveChart/jsonp?callback=jQuery1102006651935772970319_1432145887816&parameters={"Normalized":false,"NumberOfDays":3650,"DataPeriod":"Day","Elements":[{"Symbol":"AAPL","Type":"price","Params":["ohlc"]},{"Symbol":"AAPL","Type":"volume"}]}
Doesn't Work
http://dev.markitondemand.com/Api/v2/InteractiveChart/jsonp?callback=jQuery1102006651935772970319_1432145887816&parameters={"Normalized":false,"NumberOfDays":3650,"DataPeriod":"Day","Elements":[{"Symbol":"APPL","Type":"price","Params":["ohlc"]},{"Symbol":"APPL","Type":"volume"}]}
As you can see the urls appear to be identical, but the second url was constructed using your url example.
@brianbaker , @timburcham can someone sanity check me here?

The working example uses AAPL, which is Apple.  The non-working example uses APPL, which is Pete Appel Corp, a delisted OTC stock.  http://finance.yahoo.com/q?uhb=uh3_finance_vert&fr=&type=2button&s=appl
If you switch your example to AAPL, in both places, it should work.
Nice brainteaser, by the way.  :)

@mjdguyler , if you can drop some line numbers to where you found this originally, we will work to correct any error in the documentation.

Thanks for your help, I had thought I typed that in correctly.
On Wed, May 20, 2015 at 12:41 PM, Tim Burcham<EMAIL_ADDRESS>wrote:

@mjdguyler https://github.com/mjdguyler , if you can drop some line
numbers to where you found this originally, we will work to correct any
error in the documentation.
—
Reply to this email directly or view it on GitHub
https://github.com/markitondemand/DataApis/issues/18#issuecomment-104010403
.

@timburcham I, no joke, had three developers look at that before I added that reply. Now that you pointeed it out its so obvious it hurts. Good spot Tim!


Audio file format to download

Pick the file format and quality of the audio to convert from youtube video. ( mp3, webm, wave..etc )

I commence with all these issues within two weeks to enhance the audio to convert from Youtube video(mp3, webm).

:+1:


Add random feature selection to tree building in forest.

At the moment we consider all features for the tree building process.
Goal:

Use parameter ratio_features_at_split to determine the ratio of features to consider at each splitting point in a tree. -> rewrite _fit method in causaltree.py.
Check if number of features is below a threshold (< 3) then do not use the ratio but use all variables and print a warning message.

Issue was solved/added by a7939d7fe07a0a.


CAMEL-12966: camel-netty4-http use relative path by default

Make useRelativePath to true, to get the relative path by default.

@oscerd , @davsclaus , changes done. Can you pls review ?

     * An example with relative path:
     * GET /foo HTTP/1.1
     * Host: myserver.com
     *
     * And with absolute path:
     * GET http://myserver.com/foo HTTP/1.1
     * Host: myserver.com

eg we do today as the bottom, but we want to use the upper as the new default when using netty4-http producer

You can turn on DEBUG logging and netty will log the actual HTTP request and responses so you can see the HTTP headers

Well, the earlier approach i used, making the default 'useRelativePath' to true had quite a few tests failing. These were tests with non GET requests. So, there are quite a few tests that need to be changed and code be refactored. In addition, we are restricting this for GET only.
For example, we have this test, NettyHttpBindingUseRelativePathInPostTest,
@Test
    public void testSendToNetty() throws Exception {
        Exchange exchange = template.request("netty4-http:http://localhost:{{port}}/myapp/myservice?query1=a&query2=b&useRelativePath=true", new Processor() {

            public void process(Exchange exchange) throws Exception {
                exchange.getIn().setBody("b1=x&b2=y");
                exchange.getIn().setHeader("content-type", "application/x-www-form-urlencoded");
                exchange.getIn().setHeader(Exchange.HTTP_METHOD, HttpMethods.POST);
            }

        });
        // convert the response to a String
        String body = exchange.getOut().getBody(String.class);
        assertEquals("Request message is OK", body);
    }

and if we change the default value to 'true', i guess we probably then lose the objective this unit test class has for relative address in POST requests. We need to showcase the flip side of the test, by turn the value to 'false' in the unit test.
I understand we have specified the hard code for GET request, but if the change is going to use relative paths for only GET, i find this approach to be more simpler.
Thank you Claus for taking a look here. I will check with the earlier approach and modifying the tests.

On the other hand I would find it too magic if GET is doing it this way, and all the other HTTP verbs are doing it another way.
To my knowledge the HTTP protocol and other http clients are more often using the relative syntax where the hostname is provided in the Host header and the top header with the request uri is the relative path from the Host.

Any news on this?

I'm closing this.


Revert 204 endpoint changes

Reverts changes from https://github.com/mxenabled/openapi/pull/57

:shipit:


LLVM package missing targets which are supposed to be enabled by default

#52031 broke the LLVM package. Previously all the LLVM default targets were built, now we have only these targets built (on my machine):
    amdgcn - AMD GCN GPUs
    r600   - AMD GPUs HD2XXX-HD6XXX
    wasm32 - WebAssembly 32-bit
    wasm64 - WebAssembly 64-bit
    x86    - 32-bit X86: Pentium-Pro and above
    x86-64 - 64-bit X86: EM64T and AMD64

LLVM is a general purpose library for compiler frontends, you can't just delete target backends from it.

This was fixed in d6f401e132ebc9083c64dc2d7a7574344c49a9c9.

Ahh really happy to hear that. Thanks! I was worried that I was going to get push back on this.

Nope! Conceivably a platform's bootstrap and base compiler (when clang or llvm-based) might eventually elide these but for anything using 'llvm' as a dependency (like zig) wouldn't be impacted, for he reasons you say. :).
And this isn't currently part of anyone's plans AFAIK anyway :). Glad it works now!


CDPSDX-3926 Database backup should continue with salt update fail

JIRA: CDPSDX-3926
Database backup chain includes two flows: 1. SALT_UPDATE 2. DATABASE_BACKUP Now when SALT_UPDATE fails the chain will not continue to DATABASE_BACKUP. However, we want to make DATABASE_BACKUP continue even if SALT_UPDATE fails because SALT_UPDATE should not impact database backup. The way we handle this is in SALT_UPDATE_FAILED_STATE, we will check if the flowchain is BackupDatalakeDatabaseFlowEventChainFactory. If it is we will continue otherwise we will keep the old way (for all other cases that use SALT_UPDATE) - not move to the next flow.
Before
(DB failed when salt update fails. Hardcoded to force a salt update failure):

(Not moving to next flow):

After:
(DB succeeds even if salt update fails. Hardcoded to force a salt update failure):

(Moved to next flow even if having a failed status in one of the states):

*Test with datalake upgrade which also uses SALT_UPDATE. We can tell it's NOT moving to the cluster upgrade flow and done with SALT_UPDATE. So this change is not impacting  DL backup.

in general I do not think this is the right approach to handle the issue here.
if failure of salt update does not matter in case backup then why do we do it for backup? if salt update is needed for backup then we just can't ignore if it fails. if salt update is not needed for backup, then you can just simply remove the salt update flow from backup flowchain.

I understand your concerns Adam, but the main idea behind this is not that we don't care about Salt update, just that a failure does not necessarily mean that backup cannot be done. The primary reason we run the Salt update at the beginning of the backup process is to ensure that the most up-to-date versions of the backup Salt state files are present on the cluster. Files which are not changed often and, are not changed in drastic ways.
With this in mind, if a Salt update fails that just means that the backup Salt state files may not be up to date, but that backup can still proceed and function correctly.
The main reason we are even doing this is because we have observed a lot of issues with the Salt update process, resulting in backups failing when they could have been successful by just ignoring the update. We are currently working on some logic to avoid the Salt update altogether (instead updating the files we need directly), but until then we need this change to ensure backup is functioning as successfully as possible.

in general I do not think this is the right approach to handle the issue here.
if failure of salt update does not matter in case backup then why do we do it for backup? if salt update is needed for backup then we just can't ignore if it fails. if salt update is not needed for backup, then you can just simply remove the salt update flow from backup flowchain.

I understand your concerns Adam, but the main idea behind this is not that we don't care about Salt update, just that a failure does not necessarily mean that backup cannot be done. The primary reason we run the Salt update at the beginning of the backup process is to ensure that the most up-to-date versions of the backup Salt state files are present on the cluster. Files which are not changed often and, are not changed in drastic ways. With this in mind, if a Salt update fails that just means that the backup Salt state files may not be up to date, but that backup can still proceed and function correctly.
The main reason we are even doing this is because we have observed a lot of issues with the Salt update process, resulting in backups failing when they could have been successful by just ignoring the update. We are currently working on some logic to avoid the Salt update altogether (instead updating the files we need directly), but until then we need this change to ensure backup is functioning as successfully as possible.

I see, unfortunately we need to do as much as possible to avoid bugs, so we cannot rely on something such:
Files which are not changed often and, are not changed in drastic ways
What if the final fix will be ready only 3 releases later and in the meantime someone changes a backup related state? It is possible that he/she won't be aware of this behaviour.
But if you are confident with this, I am fine with it.
Although what I would really like to avoid is to "pollute" SaltUpdateActions with feature dependent conditions and logics which requires expensive calls (StackDtoService, FlowLogDBService, FlowChainLogService). These calls will affect all flowchains which using this flow, thus I do not recommend it.

Closed this PR because some of our new changes have decreased the impact of salt update.


Lot of unnecessary white space around cell output

When we have text output, we seem to have a lot of unnecessary white space above and below the cell output!
Sample

There's only one line in the output
However the output panel seems to be 4 lines in height...

Here we have both native editor and interactive window together. As we can see there's a lot of white space in native editor. Lot of real-estate wasted.

Closing due to lack of customer enthusiasm. Designs are being churned as we speak so we'll likely address things like this when those changes make their way to engineering.


[token site] Note on missing proposals

https://github.com/vegaprotocol/frontend-monorepo/pull/1222 formerly had a callout that it's possible that a market proposal may not exist due to checkpoints not containing old, enacted proposals. @barnabee & me voted to remove that from the console, but there should be a comment on the token site if a proposal is not found, that it might be for that reason

Is this the same as https://github.com/vegaprotocol/frontend-monorepo/issues/1076 @edd ?


rpath/runpath setting does not show in pkg-config files

I'm trying to build OpenSSL 3.4.0 with the -Wl,-rpath,'$(LIBRPATH)' option so I can install libraries at a non-default location.  Both libraries and the openssl binary seems to be built properly with the desired rpath, but the rpath setting does not appear in pkg-config files.

the rpath linker directive has no impact on the pkg-config files.
If you want to install to a non-default path, you should use the --prefix and --openssldir configuration options when configuring your build.
You can also choose to use --rpath if you want to specify where the libraries are searched for (depending on how you are loading openssl), but you need to use the former options to properly lay out your pkg-config files


'Their' underline

The 'Their' on the homepage's jumbotron could use some adjusting of its underline. Currently you are just using the default text-decoration: underline;, but it's a bit chunky, so you're probably better off overriding it with a pseudo element:
.pn-frontpage-feature-their {
   /* text-decoration: underline; */
   &:after {
      left: 0;
      right: 0;
      content: '';
      height: 3px;
      bottom: .3em;
      background: #fff;
      position: absolute;
   }
}

It's probably also best to change that 3px underline to a 2 px underline for the smaller breakpoints.
Before:

After:

done. pushing.
--
Bryant Smith
630.430.5328
On Tue, Nov 17, 2015 at 1:19 PM, Matt Soria<EMAIL_ADDRESS>wrote:

The 'Their' on the homepage's jumbotron could use some adjusting of its
underline. Currently you are just using the default text-decoration:
underline;, but it's a bit chunky, so you're probably better off
overriding it with a pseudo element:
.pn-frontpage-feature-their {
/* text-decoration: underline; */
&:after {
left: 0;
right: 0;
content: '';
height: 3px;
bottom: .3em;
background: #fff;
position: absolute;
}
}
It's probably also best to change that 3px underline to a 2 px underline
for the smaller breakpoints.
Before:
[image: screen shot 2015-11-17 at 1 09 56 pm]
https://cloud.githubusercontent.com/assets/2831517/11221786/8b47b86a-8d2c-11e5-86a1-5189c3f85bd4.png
After:
[image: screen shot 2015-11-17 at 1 11 02 pm]
https://cloud.githubusercontent.com/assets/2831517/11221815/bb494132-8d2c-11e5-9ffc-2755a0b45f5a.png
—
Reply to this email directly or view it on GitHub
https://github.com/billybobjobo/public_narrative/issues/3.


⚠ SpeakUpConference.com has degraded performance

In 341fbcd, SpeakUpConference.com (https://www.speakupconference.com) experienced degraded performance:

HTTP code: 200
Response time: 11854 ms

Resolved: SpeakUpConference.com performance has improved in ccedad4 after 11 minutes.


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_7apxlrofjs/clone/recipe/meta.yaml:15: pip_install_args: pip install should be run with --no-deps.
ERROR: /tmp/abs_7apxlrofjs/clone/recipe/meta.yaml:20: missing_wheel: For pypi packages, wheel should be present in the host section
ERROR: /tmp/abs_7apxlrofjs/clone/recipe/meta.yaml:47: http_url: http://whitenoise.evans.io/en/stable/ is not https
Errors were found


feat: Add IToastService, IMesssageService, IDialogService to a new library Microsoft.FluentUI.AspNetCore.Components.Abstractions

🙋 Feature Request
I would like to use the following services: IToastService, IMesssageService, IDialogService without having to have a reference to the full Microsoft.FluentUI.AspNetCore.Components package, instead I would like to use something like Microsoft.FluentUI.AspNetCore.Components.Abstractions.
This would allows me to e.g.  inject these services view models that are not in the same project as my Blazor UI code.
💁 Possible Solution
Microsoft.FluentUI.AspNetCore.Components package is separated into

Microsoft.FluentUI.AspNetCore.Components
Microsoft.FluentUI.AspNetCore.Components.Abstractions.

🔦 Context
If doing MVVM together with fluent-ui blazor, the simplest workaround is to put all view models inside razor.class lib or wherever the UI blazor components exists, however idealy I would prefer a finer level on granularity and separation between my view models and UI code.

This is indeed an improvement that could be useful in certain cases, like the one you're presenting.
It's not currently planned, but we can analyze it and put it in the backlog of a future major release.


Support multipart configuration in ServletContextHandlerFactory component

The multipart configuration should be supported via the ServletContextHandlerFactory component on the Servlet or on the context component side

We will not use the Servlet 3.1 multipart request feature as it is crap


isaaclevin.presencelight version 5.4.11

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.1 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

@ItzLevvie if I have a similar schema going forward (basically replacing version and hash) I should be able to automate this correct?


Support Special Placeholders in Mach-O library paths

As requested for bookkeeping in https://github.com/NationalSecurityAgency/ghidra/issues/5937#issuecomment-1803670481
@rpath is one of the simpler ones, but if I recall correctly the overall mechanism around this is more complicated and also includes other variables, and maybe even some mechanism to set those arbitrarily

Some info: https://blog.krzyzanowskim.com/2018/12/05/rpath-what/


implement countDocuments()

What this PR does:
Noticed that countDocuments() implementation was missing, but already supported in jsonapi.
Which issue(s) this PR fixes:
Fixes #
Checklist

[ ] Changes manually tested
[ ] Automated Tests added/updated
[ ] Documentation added/updated
[ ] CLA Signed: DataStax CLA

Thanks for this PR @vkarpov15. I noticed this too, and was about to add this week.


Support posix_spawn on Android and Emscripten

Emscripten uses the musl implementation. Android exposes the same functions and constants as the other linux_like platforms, but its posix_spawnattr_t and posix_spawn_file_actions_t are opaque. See:
https://github.com/emscripten-core/emscripten/blob/e25fa53069665c1f6c3be4ba5ed1d6ae82339849/system/lib/libc/musl/include/spawn.h https://github.com/aosp-mirror/platform_bionic/blob/2215ad406b253f12e270cdd0876e19e9df2aa6d4/libc/include/spawn.h
Since the fields in the linux implementation are private, let's make it opaque on all linux_like platforms.

Hmm, I think https://github.com/emscripten-core/emscripten/blob/cbb7a11e2b0ffec34b59c0a7417a1bd2a61e02d9/tools/system_libs.py#L1076 means that Emscripten doesn't actually support posix_spawn (though it does ship the header). I'll make this Android-only then.
@sbc100 FYI -- you might want to stop shipping spawn.h in Emscripten.

This was revered in https://github.com/rust-lang/libc/pull/3678 because exposing the fields was important to get the correct size, see https://github.com/rust-lang/libc/issues/3608.
@pcc I'd suggest you file a new PR that doesn't have this problem.


[ABC Templates] Proposal on Implementation Details

Is your feature request related to a problem? Please describe
Github RFC: https://github.com/opensearch-project/OpenSearch/issues/12683
Overview
The proposed templates in RFC  https://github.com/opensearch-project/OpenSearch/issues/12683 aim to provide a pre-defined set of system templates (made available as part of the distribution), which can allow users to create indices/index-templates for specific use cases without worrying about the granular tuning that are required for those use cases. This document covers certain decisions being proposed to come up with a final proposal around how these templates can be implemented.
Requirements

Application Based Configuration (ABC) templates should provide a sensible set of defaults for use-cases to tune their performance (compute, storage) and usability (index state management)
Suggest Schema based on standards so that different types of integrations can leverage the default settings.
Changes to core settings should be taken care of in the ABC templates as part of new version releases.
New features applicable to the use cases catered by these templates should reflect on these, and apply to the index/index-template as well.
ABC templates should be validated and made available for use as part of the bootstrap process. Any plugin dependent settings should be inferred and validated along with fallback options.

Proposed Implementation Details
Reusing Composable Index/Component Templates Resource
Background: Component Templates allow to declare settings and mappings which can be then used to create composable index templates. Composable Index Templates are defined using a schema which allows a template definition, along with multiple component templates which it can be composed of. These are applied to an index which matches the pattern defined the index template definition. In case of multiple composable index templates matching the index name pattern, the one with the highest priority is used. Some of the properties of index templates today are:

Component Templates today don’t allow to parameterization at all. The settings/mappings can be declared, but there is no way to ensure that users provide certain settings during index creation. Since these are used by index templates today through a composed_of mechanism, we cannot parametrize them without breaking compatibility
Index Templates are used only prior to index creation, and any changes to the index templates are not used once the index has been created.
Only the latest version of these templates is stored in the cluster state.

Proposal: Use component template as the building block (storage model) and filter these templates from being used in composed_of declaration of composable index templates.

Component Templates can be used as the building block for ABC templates.
ABC Templates can be referred to from an index template or an index [We can start with index templates].
ABC Templates will not be tied to any index pattern directly but will need to come from the context definition while creating an index template/index.
We can also create specific templates (e.g. OTEL Schema indices) using ABC Templates through a context definition

If we go ahead with this modeling, we can reuse the existing component template storage model, but we will need to add support to parameterize setting values in case to the template definition within the application logic.
We can’t add paramterization support in compsable index templates directly as of today as they break the auto create index flow during rollovers due to which this new internal template layer is needed. Hence, any index template tied with an ABC template will need to declare concrete values for parameters provided in the ABC templates.
e.g.
logs-basic.json // ABC Template

{
  "template": {
    "settings": {
      "codec": "best_compression",
      "merge.policy": "log_byte_size",
      "refresh_interval": "60s"
    }
  },
  "_meta": {
    "__abc_template": true,
    "_version": "1.0.0"
  },
  "version": 1
}

# Users can do the following. Order of application is component template followed by declared template followed by context definition (Context definition supersedes all declarations)
PUT _index_template/my-logs
{
    "pattern": "my-logs-*"
    "template": {
        "settings: {
            "refresh_interval": "60s"
        }
    },
    "context": {
        "name": "logs-basic",
        "version": "_latest" # Version is optional, default is latest with upgrades enabled,
        "params": {} # Required if params are present in ABC template
    }
}

Storage Model

We can reuse the cluster state component for component templates to store the ABC templates
ABC templates will have different application logic to ensure:

They are marked as distribution provided templates through a metadata field.
They will not be allowed to updated via APIs (i.e. only changes in the repository can allow the templates to be updated)
Validation logic for ABC templates will differ to account for support of parameterized settings.

Any unused template version can be purged over time (except for latest) if they remain unused in snapshots, indices, etc.

Applying Template Upgrades
Based on the entity referencing the context for ABC template, we will allow to have the context of the entity to be updated when templates are upgraded to a new version.
Any updates to component templates are applied on the index templates referring them today as well. With ABC templates, we will extend this to be applicable for indices as well. By default, the template upgrades will apply to the entity using them in the context.
Template hosting

We start with a code based config repository can be created which holds the basic ABC templates
These templates will be exposed through an interface which allows for custom dynamic repository along with loading logic applicable for each of them (this allows extension to support loading of generic resources)
The repository will support versioning on top of the templates it provides.

Overrides through other Templates/Index Settings

Creation: Ordering in index templates and indices will follow as:

First component templates are applied [Applicable to index templates only]
Declared settings/mappings in index templates are applied thereafter

Any settings which coincide with ones declared in ABC templates — Use ABC template settings

This is followed by applying ABC templates [i.e. ABC templates supersede any setting coming through component template]. If there is a conflict between what is declared through an index template and through ABC templates, we can either fail during simulation or handle gracefully.

Setting Updates:

Any settings which have been applied through the context should not be changed during the index lifecycle if the index continues to be associated with the context. We will need to add validation for this in index settings flows.
Context can be removed as a whole from the index/index templates if users want to not be tied with the constraints which come with these. This can be implemented at a later point of time.

Handling Cluster upgrades

Whenever a new cluster manager gets elected, it can query the repository in which templates are hosted, and apply any differences from the last known version into the applicable resource (i.e. cluster state). With version checks in place, we can limit the additional work and only traverse, and apply the actual changes.

Initial Template Repository
Proposed Defaults
Template Repository will be focused on 2 things:

Applying performance optimizations
Adding default applications

Performance Optimization Settings [In Progress]
Request Logs
refresh_interval: "60s"
index.codec: "zstd_no_dict || best_compression"
merge_policy: "LOG_BYTE_SIZE"

Metrics
refresh_interval: "60s"
index.codec: "zstd_no_dict || best_compression"
merge_policy: "LOG_BYTE_SIZE"

Events
index.optimize_doc_id_lookup.fuzzy_set.enabled: true
index.optimize_doc_id_lookup.fuzzy_set.false_positive_probability: 0.10
index.merge.policy.deletes_pct_allowed: 5.0
merge_policy: "LOG_BYTE_SIZE",
index.codec: "zstd_no_dict || best_compression"

Related component
Indexing:Performance

@mgodwan Do we need to update the label as 2.17?


Return email address on login

Implements https://github.com/ooni/backend/issues/709

1.0.73~pr732-160 deployed on -test


Multiple charge controllers, complication with dbus-serialbattery

Hello,
we already had contact in the victron forum.
I would like to use the driver to integrate three charge controllers.
In addition, there seem to be problems when dbus-serialbattery runs in parallel.

The BMS driver does not start. Your driver only starts when I plug in the USB adapter for the DalyBMS. Apparently he has now set this for the application?

Adapter:

How can I support you, do you need more information?
I would also be interested in how I can cleanly remove the driver from the system again.
I'd be happy to hear back from you.

Really useful project. I have Raspberry Pi Venus, with Victron 100-50 plus 2x Epever Tracer 6415AN. So hoping to get this working. Im using dbus-serial battery, Jk BMS which is good with DVCC, to control the output of the Victron SCC, when the battery is high. Being able to limit or turn off the Epever's would be great too. The 6415's have a problem with Lifepo4 BMS, if it disconnects Charging; they then put a high voltage, sometimes near solar panel voltage onto the 24v system. Im using a Victron Battery Protect on the loads, but its HVD is fixed at 32v, and a bit slow operating, so a few small items have been blown, that cannot tolerate over 32v. Now on 7S (310Ah cells) where over voltage is lower, often around 30v, and panels now in parallel 40v. With 8S overvoltage was higher. Maybe need a second Victron Battery Protect between the Epever's and the 24v system.  i am setting the chargers to 23.6v max = Bulk & Absorption for Victron = Boost & Equalisation for Epever. Epever recommend using both those, at the same voltage.


none of the file resources are getting recognized

i used below code to replace the file names with absolute file path, still it is giving me protocol is unknown, i have font files, image files to include in pdf
var dirName = path.join('file://', __dirname);
dirName = dirName + '/';

html = html.replace(/src="/g, 'src="'+dirName).replace(/src: url(/g,'src: url('+dirName);

sorry, i had to set the flag as true for allowLocalFilesAccess, it resolved the issue
conversion({ html: html, phantomPath: require("phantomjs-prebuilt").path,allowLocalFilesAccess: true }, function(err, pdf) {


Exit with an error code if failed to parse

I am using Scenery with Atlantis and if scenery fails to parse the output of a plan or apply it still returns an exit code of 0. This results in the Github checks passing instead of failing as one would expect them to if something went wrong.

I agree, this should be the default behavior, but maybe make it optional? We also use Atlantis. We currently have several projects that scenery can't parse, and we can't figure out why. Right now we're still able to apply the plan, and it would be pretty annoying to have to enable/disable scenery on a per project basis.

@kenske I've heard about some plans that Scenery is unable to parse. I'll try to dig into why this is happening, chances are that there's something missing from the parser.
I have some free time in the coming days so I'll making some updates to scenery and I can introduce a --no-exit-on-fail flag, it makes sense.
Out of curiosity, what version of Terraform are you using? With Hashicorp deprecating Terraform 0.11 I'm considering only supporting Terraform 0.12+ as it means I could use the JSON output and forego parsing in effort only displaying a pretty-print output.

@dmlittle We're in the process of upgrading to 0.12, so right now we have a mix of both 0.11 and 0.12 projects. Adding that flag would be great, it would at least let us keep using scenery on 0.11 until we upgrade fully to 0.12.
This is a great tool, thanks for your work.


Allow smart speakers to perform next and previous

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 67.53%. Comparing base (d4515d5) to head (3010d03).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #12   +/-   ##
=======================================
  Coverage   67.53%   67.53%
=======================================
  Files           4        4
  Lines         231      231
=======================================
  Hits          156      156
  Misses         75       75

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


rebase and send again

Please follow the pattern of FluentAssertions for the TestFormatable and the because class in the assertion too keep a live documentation, use existing tests for inspiration

Modified


More example with hooks

Enhance documentation
Enhance the documentation with more examples that use hooks

PRs welcome (:

My first time contributing. I'd like to help with this. I think that reformatting the current ones to have two versions of the same example, one with classes and the other with functions+hooks, could help enhance the documentation. Could I try it?

PRs welcome (:

I've created this PR, I've added some example with functional + hooks #2608


 Depending on the details of the cause and the fix, this might be 1.8.1 material. Tentatively marking it as such.

dup of #19734 ?

Adding another data point here - all my cgo stuff broke when upgrading to XCode 8.3. I was able to get around this by building binaries with -ldflags -s.

Yes, dup of #19734. Apparently my search-fu was weak.
@repustate, knowing that -ldflags=-s is a workaround seems useful. Will you duplicate that comment at #19734? Thanks.

Removing milestone because this is a dup of another bug that is already correctly milestoned.


Change Tracking and Inventory (CT&I) with MMA/OMS has retired

Module/Lab: 02
Exercise: 01
Task: 02
Step: 04
Description of issue:
A Change Tracking and Inventory (CT&I) with MMA/OMS has retired on 31st August 2024. New VM onboarding is no longer supported. For retirement details, refer here.
Repro steps:

Create an automation account
Open Configuration Management
Open Inventory

Relevant screenshots

Is there any update on the issue reported above?

Hi @TJGitHubUser , can u please provide an update for this issue

Labs are currently being rewritten to account for MMA retirement. While I can't give an exact date they will be republished, I think we're probably looking at weeks at the most. The labs are required to go through a security compliance/testing phase with our ALH provider. We will post a heads-up when we have a better idea of when the updated labs will be available.
Thanks.

Hi @TJGitHubUser , any latest update on this. When can we expect the latest changes ?

Both lab2 and lab9 are being significantly rewritten and retested. We're hoping to submit both labs to the ALH providers for verification within the next couple of weeks, but I can't give an exact estimate of release. I hate to say by end of year but given testing, security, accounting for holiday timeframes and then working through our release teams I'd say we're working to have new updates as quickly as possible. Thanks for your understanding.