POL-165 - Update AWS policies for credential Service 1

Description
Modified AWS policies to support credential service
Issues Resolved
Modified AWS policies to support credential service
Contribution Check List

[ ] All tests pass.
[ ] New functionality includes testing.
[ ] New functionality has been documented in the README if applicable
[ ] New functionality has been documented in CHANGELOG.MD

Running Template links and screenshots
AWS Disallowed Regions
https://governance.rightscale.com/org/1105/projects/60073/applied-policies/5e1874b3513cd00001eaecae

AWS Idle Compute Instances
https://governance.rightscale.com/org/1105/projects/60073/applied-policies/5e186ed9828e5b00011722dd

AWS Long Stopped Instances
https://governance.rightscale.com/org/1105/projects/60073/applied-policies/5e18703a828e5b00011722e1

AWS Publicly Accessible RDS Instances
https://governance.rightscale.com/org/1105/projects/60073/applied-policies/5e186e51828e5b00011722dc

Out of 6 policies which were selected for end to end testing, pasted the links of applied policies and screenshots for 4 policies.
As discussed, AWS Internet facing ELBs policy syntax has been reviewed internally.
AWS object storage optimization policy changes have not been committed as testing the same has given 501 error for which ticket has been raised to resolve the issue(PHX-1971).

          22 Errors

:no_entry_sign:
The URL is not valid: https://github.com/flexera/policy_templates/tree/POL-165-update_aws_policies_for_credential_service/aws/disallowed_regions in compliance/aws/disallowed_regions/aws_disallowed_regions.pt Status: 404

:no_entry_sign:
The URL is not valid: https://docs.rightscale.com/credentials/ in compliance/aws/long_stopped_instances/README.md Status: 404

:no_entry_sign:
The URL is not valid: https://docs.rightscale.com/credentials/ in cost/aws/burstable_instance_cloudwatch_credit_utilization/README.md Status: 404

:no_entry_sign:
The URL is not valid: https://docs.rightscale.com/credentials/ in cost/aws/elb/clb_unused/README.md Status: 404

:no_entry_sign:
The URL is not valid: https://docs.rightscale.com/credentials/ in cost/aws/idle_compute_instances/README.md Status: 404

:no_entry_sign:
The URL is not valid: https://docs.rightscale.com/credentials/ in cost/aws/reserved_instances/coverage/README.md Status: 404

:no_entry_sign:
The URL is not valid: https://docs.rightscale.com/credentials/ in cost/aws/reserved_instances/recommendations/README.md Status: 404

:no_entry_sign:
The URL is not valid: https://docs.rightscale.com/credentials/ in cost/aws/s3_bucket_size/README.md Status: 404

:no_entry_sign:
The URL is not valid: https://docs.rightscale.com/credentials/ in operational/dbaas/aws/rds_backup/README.md Status: 404

:no_entry_sign:
The URL is not valid: https://docs.rightscale.com/credentials/ in security/aws/loadbalancer_internet_facing/README.md Status: 404

:no_entry_sign:
The URL is not valid: https://github.com/rightscale/policy_templates/tree/master/security/aws/rds_publicly_accessible/AWS_Publicly_Accessible_RDS_Instances.pt in security/aws/rds_publicly_accessible/README.md Status: 301

:no_entry_sign:
The URL is not valid: https://docs.rightscale.com/credentials/ in security/aws/rds_publicly_accessible/README.md Status: 404

:no_entry_sign:
compliance/aws/disallowed_regions/README.md:13: MD009 Trailing spaces
compliance/aws/disallowed_regions/README.md:17: MD009 Trailing spaces
compliance/aws/disallowed_regions/README.md:25: MD009 Trailing spaces
compliance/aws/disallowed_regions/README.md:53: MD009 Trailing spaces
compliance/aws/disallowed_regions/README.md:1: MD019 Multiple spaces after hash on atx style header
compliance/aws/disallowed_regions/README.md:12: MD022 Headers should be surrounded by blank lines
compliance/aws/disallowed_regions/README.md:24: MD022 Headers should be surrounded by blank lines
compliance/aws/disallowed_regions/README.md:52: MD022 Headers should be surrounded by blank lines
compliance/aws/disallowed_regions/README.md:16: MD032 Lists should be surrounded by blank lines
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
cost/aws/burstable_instance_cloudwatch_credit_utilization/README.md:11: MD009 Trailing spaces
cost/aws/burstable_instance_cloudwatch_credit_utilization/README.md:20: MD009 Trailing spaces
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
cost/aws/elb/clb_unused/README.md:1: MD009 Trailing spaces
cost/aws/elb/clb_unused/README.md:2: MD009 Trailing spaces
cost/aws/elb/clb_unused/README.md:9: MD009 Trailing spaces
cost/aws/elb/clb_unused/README.md:11: MD009 Trailing spaces
cost/aws/elb/clb_unused/README.md:13: MD009 Trailing spaces
cost/aws/elb/clb_unused/README.md:15: MD009 Trailing spaces
cost/aws/elb/clb_unused/README.md:17: MD009 Trailing spaces
cost/aws/elb/clb_unused/README.md:53: MD009 Trailing spaces
cost/aws/elb/clb_unused/README.md:55: MD009 Trailing spaces
cost/aws/elb/clb_unused/README.md:57: MD009 Trailing spaces
cost/aws/elb/clb_unused/README.md:44: MD010 Hard tabs
cost/aws/elb/clb_unused/README.md:45: MD010 Hard tabs
cost/aws/elb/clb_unused/README.md:1: MD022 Headers should be surrounded by blank lines
cost/aws/elb/clb_unused/README.md:3: MD022 Headers should be surrounded by blank lines
cost/aws/elb/clb_unused/README.md:8: MD022 Headers should be surrounded by blank lines
cost/aws/elb/clb_unused/README.md:14: MD022 Headers should be surrounded by blank lines
cost/aws/elb/clb_unused/README.md:52: MD022 Headers should be surrounded by blank lines
cost/aws/elb/clb_unused/README.md:56: MD022 Headers should be surrounded by blank lines
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
cost/aws/reserved_instances/coverage/CHANGELOG.md:11: MD024 Multiple headers with the same content
cost/aws/reserved_instances/coverage/CHANGELOG.md:19: MD026 Trailing punctuation in header
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
cost/aws/reserved_instances/recommendations/README.md:5: MD022 Headers should be surrounded by blank lines
cost/aws/reserved_instances/recommendations/README.md:3: MD026 Trailing punctuation in header
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
security/aws/loadbalancer_internet_facing/README.md:1: MD009 Trailing spaces
security/aws/loadbalancer_internet_facing/README.md:2: MD009 Trailing spaces
security/aws/loadbalancer_internet_facing/README.md:7: MD009 Trailing spaces
security/aws/loadbalancer_internet_facing/README.md:8: MD009 Trailing spaces
security/aws/loadbalancer_internet_facing/README.md:11: MD009 Trailing spaces
security/aws/loadbalancer_internet_facing/README.md:13: MD009 Trailing spaces
security/aws/loadbalancer_internet_facing/README.md:62: MD009 Trailing spaces
security/aws/loadbalancer_internet_facing/README.md:64: MD009 Trailing spaces
security/aws/loadbalancer_internet_facing/README.md:66: MD009 Trailing spaces
security/aws/loadbalancer_internet_facing/README.md:41: MD010 Hard tabs
security/aws/loadbalancer_internet_facing/README.md:42: MD010 Hard tabs
security/aws/loadbalancer_internet_facing/README.md:53: MD010 Hard tabs
security/aws/loadbalancer_internet_facing/README.md:54: MD010 Hard tabs
security/aws/loadbalancer_internet_facing/README.md:1: MD022 Headers should be surrounded by blank lines
security/aws/loadbalancer_internet_facing/README.md:3: MD022 Headers should be surrounded by blank lines
security/aws/loadbalancer_internet_facing/README.md:6: MD022 Headers should be surrounded by blank lines
security/aws/loadbalancer_internet_facing/README.md:12: MD022 Headers should be surrounded by blank lines
security/aws/loadbalancer_internet_facing/README.md:61: MD022 Headers should be surrounded by blank lines
security/aws/loadbalancer_internet_facing/README.md:65: MD022 Headers should be surrounded by blank lines
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
security/aws/rds_publicly_accessible/README.md:2: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:5: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:7: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:8: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:10: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:12: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:14: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:32: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:36: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:64: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:73: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:75: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:77: MD009 Trailing spaces
security/aws/rds_publicly_accessible/README.md:28: MD010 Hard tabs
security/aws/rds_publicly_accessible/README.md:32: MD010 Hard tabs
security/aws/rds_publicly_accessible/README.md:64: MD010 Hard tabs
security/aws/rds_publicly_accessible/README.md:1: MD022 Headers should be surrounded by blank lines
security/aws/rds_publicly_accessible/README.md:3: MD022 Headers should be surrounded by blank lines
security/aws/rds_publicly_accessible/README.md:6: MD022 Headers should be surrounded by blank lines
security/aws/rds_publicly_accessible/README.md:11: MD022 Headers should be surrounded by blank lines
security/aws/rds_publicly_accessible/README.md:72: MD022 Headers should be surrounded by blank lines
security/aws/rds_publicly_accessible/README.md:76: MD022 Headers should be surrounded by blank lines
security/aws/rds_publicly_accessible/README.md:26: MD031 Fenced code blocks should be surrounded by blank lines
security/aws/rds_publicly_accessible/README.md:32: MD031 Fenced code blocks should be surrounded by blank lines
security/aws/rds_publicly_accessible/README.md:9: MD032 Lists should be surrounded by blank lines
security/aws/rds_publicly_accessible/README.md:25: MD032 Lists should be surrounded by blank lines
security/aws/rds_publicly_accessible/README.md:33: MD032 Lists should be surrounded by blank lines
security/aws/rds_publicly_accessible/README.md:37: MD032 Lists should be surrounded by blank lines
A detailed description of the rules is available at https://github.com/markdownlint/markdownlint/blob/master/docs/RULES.md

:no_entry_sign:
Policy Template path should be lowercase. cost/aws/elb/clb_unused/AWS_Delete_Unused_CLB.pt

:no_entry_sign:
Policy Template path should be lowercase. security/aws/loadbalancer_internet_facing/AWS_Internet-facing_ELBs.pt

:no_entry_sign:
Policy Template path should be lowercase. security/aws/rds_publicly_accessible/AWS_Publicly_Accessible_RDS_Instances.pt

  Generated by :no_entry_sign: Danger

@praut1   also please see the Danger errors.


Git folder weighting more than 99.3% of the repo size

Hi all,
I recently wondered why the repo size was so big.
First, let me say that the repo size is 3.6GB which is huge for waht we have in it (mainly text files).
I ran WinDirStat to get some statistics on the repo and I found this:

Is there any reason to keep the .git folder so big?
After running the following command:
git repack -a -d --depth=250 --window=250
git prune
git gc --aggressive

I got the following stat:

It saved 0.8GB which is better but not perfect...
Well at the end, I guess I just wanted to raise the question of the size of the repo which I find quite big ^^ , and maybe come up with a solution.
System
operating system Windows 10

@edumur it is indeed unfortunate that the repo is as big as it is. I did some stats at some point and it is mainly due to ipy notebooks and the images therein. However, the .git folder contains all the revisions of the code that has ever been created so it is expected to be big compared to the checkout code. It is not really possible to shrink the repository without rewriting the history and chancing every single git commit since the start. In the future we will be more strict about the number of notebooks and their revisions to try to stop the growth

Thanks for this reply.
Do you think it is possible to have some files, maybe notebook, which do not exist today that we can erase from the git history to save some space?

Not really, you cannot remove a file from the git history unless you are willing to rewrite the entire history changing every single commit hash and that is a very destructive thing to do

I see...
Well, as you said, this is unfortunate ^^" .
You can close the issue or leave it opened, as you wish.
Thanks again for you reply and the work you do on this lib ;) .

After some investigation it turns out that this was largely due to the git history being retained in the gh-pages branch that holds the docs. After deleting that a fresh clone of qcodes is ~140 MB for me.
To get the saving locally you will probably have to:

Fetch the origin.
If your own fork or any other fork that you have added as a remove contains a gh-pages branch you may also have to delete the branch from that fork
Run the above commands to perform gc etc

Or alternatively checkout from a fresh clone

~140MB, that's so cool.
I will try right away, thanks!

closing since the size is now down to a more reasonable level. Let me know if there are other issues


Add new app build repo connection via AppCenter Github App instead of Github webhook.

Describe the solution you'd like
As of now, adding a new app via App Center and connecting a build to a specific Github repository creates only a webhook instead of connecting it via the installed AppCenter GitHub App (connected to the organisation).
This results in general repository slowness using git when multiple App Center apps are connected to the same repository (due to many webhooks). Also Github repositories are bound to only 20 webhooks, not allowing scale of more connections to apps.
Describe alternatives you've considered
We are currently using a GitHub dance of adding the same repo, saving and then using the save link to add a new App Center app via Github so the app build will be connected via the Github Marketplace app and not via a Github webhook.
Additional context
We are concerned this dance is not safe or will break in the future and seek for a solid solution that will use the GitHub app connection only and not a webhook.
Worth nothing current workaround can only be done by a Github admin and not by lower permission users.

We are currently using a GitHub dance of adding the same repo, saving and then using the save link to add a new App Center app via Github

Worth nothing current workaround can only be done by a Github admin and not by lower permission users.

@zarko-via do you mind help me understand more about this? What steps are taken when you onboard a new App Center app and connect with GitHub marketplace app?

I've been also struggling with this. Finally I was able to connect an app with the following dance steps:

Uninstall App Center app in GitHub
Find App Center app in Marketplace and select "grant this app access"
Select repository, and use the wizard to create a new app based on the repository

Funny thing to note is, that you could choose multiple operating systems (for example Android and iOS), which is not possible while creating an app via the dashboard.
Now that I have my alpha Android app connected to my repository, I'm wondering how would it be possible to build a beta Android from the same repository...

you could choose multiple operating systems (for example Android and iOS), which is not possible while creating an app via the dashboard.

This is a bit tricky. We've been meaning to improve this flow, but haven't been able to. If you go to GitHub, find your account setting or organization setting, you should be able to find the installed App Center app, and edit the repository list granted access. Each time you edit the list, it triggers the flow, during which you can create new apps with same repository again

Ah, awesome! This works - just not too obvious 😄Thanks for the tip!

You shall not close bot!


Handle spaces in StringList

Useful for things with spaces (such as Partner A)

Handle cases where the python value is None. -> set that to ''

Do you think this makes sense to add?

We should have to handle None, since this is a StringList, not a StringOrNoneList.
That's a good point though - this will break with empty strings too.


[Addition]:

Hotspot b58 Addresses
11fm1XUqkSK4USukxxnmk62eT968s6MJn4wwurzyj6usmBgy3ws
112PtgjMaxEzS8iLidwZqkS3xFF6ESheG8KgY6pnTh7qexGkRx2j
112Vy2CvxLZUE3zMrbxjyC12CfyYr1HSm5QKaTCZQAjYGjRVUUX5
112op34XaAQTnB8C9wZLDKurGpLVe2GNJn2P3L9zKcoLEZx6PW1B
112LeZtYAoN9T7mNxfCXxyk7BjZDFxivKRscu6T7AL8x8td8519h
11eyQf8ds6ekU1sxiycuV3KDcZek5E8Uw26p1y7sqwNatonXNmT
11WpmoZ825acNeSpKox2QJ6VzhyjpJm1vVYY3HSdnTzTdQH2DwJ
Discord Handle
Hayden#2530
Reason(s)
These hotspots recently popped up in my area and I have notifications setup for my region via Helium Vision. I have a fleet of 100 hotspots in relatively rural Alabama and all of my installations are exclusively exterior installations with extremely good coverage and redundancy.
I have personally mapped my area and have never picked up a single one of these hotspots I have listed. They are all running Sequential Static IP addresses and EXCLUSIVELY communicate with hotspots in their own wallet. That is nearly impossible due to the level of coverage that I have in my area and the very flat topography that we are located in. They are also all at impossible heights but that really isn't a determining factor for spoofing locations but it is strange that they put all of them at 50M+ in height. The SNR values are very odd as well so it could be a simple MITM exploit.
Feel free to reach out to me on Discord for any proof of my fleet and the coverage I am providing for my area.

Some of these were added to the denylist but others are still communicating and earning rewards from the same units that are included in the denylist.
11eyQf8ds6ekU1sxiycuV3KDcZek5E8Uw26p1y7sqwNatonXNmT
112PtgjMaxEzS8iLidwZqkS3xFF6ESheG8KgY6pnTh7qexGkRx2j


Pages order info

Changes
What has been done

I have added parameters to the query and backend so that we can ask for specific parts of the Orders-data
Updated front-end to support pagination
Adjusted some CSS on the front-end

The E2E tests are a bit flaky. If it fails try to run it again bu pressing details then rerun jobs. It I higly doubt the fail on E2E1 is acutally your doing. That said if rerunning does not fix it you shouldn't merge.


Recreate default AppSets in argocd namespace on change

fixes https://github.com/stolostron/cluster-templates-operator/issues/147

/retest

/retest


[Discussion] Keeping or removing the check on index existence in list_splits method

Currently, in list_splits, we return filtered splits notably with a filter on index UIDs.
In cases where an index does not exist, we have a different behavior between the file-backed metastore and the PostgreSQL metastore.

file-backed metastore: as soon as an index is not found, it returns an error IndexesDoNotExist.
PostgreSQL metastore: we check only indexes' existence if no splits are returned. See the convoluted code.

(note that the PR on the multi-indexes #3734 introduced this discrepancy).
Also, with the multi indexes features, querying splits while a user deletes some indexes will more likely happen (scenario such as "a user makes a search query on a list of indexes, an admin user deletes one of the indexes, the user gets an error").
One pro for returning an error when an index does not exist is that the caller gets the right error immediately. This is useful in Quickwit's code base as we can react to this error and stop getting splits from the metastore for a given index.
This is why I'm currently reluctant to drop the existence check.

A left outer join can make the code less complex and more accurate. I hope the performance penalty will be negligible with indexes on the index_uid columns in the indexes and splits tables.

In #4109, I replaced the list splits method by a stream splits method.
So now I see two options:

strict mode: check index existence before the select (I think it should be possible to avoid 2 calls to the db)
lenient mode: no check on the index existence


[boringssl] x64-osx build failure

Host Environment

OS: MacOS 10.5
Compiler: Xcode 11.6

To Reproduce
Steps to reproduce the behavior:
./vcpkg install boringssl --triplet x64-osx
Failure logs
clang: error: no such file or directory : '/wd4065'
Additional context

Looks like there is no judgment there. Needs add if (MSVC) ... endif().


Play Presets from rundown JSON

I added an API to SPX-GC to get the current Rundown JSON.
With this code there will be presets that are generated from the Rundown
This will make it easier to use for users because they don't need to manually read the JSON file to get the Item ID's.
I added some Tests to make sure I don't break existing Presets.
In this Version, it will only get the Rundown on first connect/reconnect.
I hope I can change that to a polling approach later, or even use the socket.io used in SPX-CG internally.

What happens when no presets are the (no connection but active module for example) will it hold the rest?

What happens when no presets are the (no connection but active module for example) will it hold the rest?

In this function, it will return an empty list if the Rundown is not returned by the HTTP GET.
This could be because the Version of SPX-GC has not the rundown/get endpoint, or because the SPX-GC is not running at all.
But the Module will still behave like before, only if the Feature is there the User has an easy way  to Play Manual Rundown Items.
https://github.com/marcnnn/companion-module-spx-gc/blob/c6b2b0727c2da32a478738639485fc0fef731576/presets.js#L141
This test checks if the presets that are not Rundown Specific are still in the return of initPresets.
https://github.com/marcnnn/companion-module-spx-gc/blob/c6b2b0727c2da32a478738639485fc0fef731576/test/presets.js#L20
And writing about it more I found a Problem when no Rundown is selected, jet SPX-GC return an empty Object.
This test checks that the Code can handle that now.
https://github.com/marcnnn/companion-module-spx-gc/blob/c6b2b0727c2da32a478738639485fc0fef731576/test/presets.js#L79


buttons on the top right on the menu do not show up on linux.

title.
also, the alert button is missing.

ah, I know what the issue is with the top right buttons; will post again when that's fixed.
as far as the alert button goes, it appears within the TV when you have a new alert; if it's not appearing there, try clicking on the tv to see if it opens up (TF2 alerts are sometimes glitchy and don't show the icon)

ah, I know what the issue is with the top right buttons; will post again when that's fixed.
as far as the alert button goes, it appears within the TV when you have a new alert; if it's not appearing there, try clicking on the tv to see if it opens up (TF2 alerts are sometimes glitchy and don't show the icon)

sweet.
also, i thought the tv was the twitch stream thingy, so that's just me being dumb.
thanks!

haha, nah that's not dumb at all; quite a few people have mentioned it. I may look at better ways to handle that in the future.
I just pushed a commit that might fix your issues; if you could download the hud and give it another go to see if it works, that'd be great :) https://github.com/rbjaxter/budhud/archive/master.zip

Going to mark this as complete; let me know if you're still having issues!


No FileSystem for scheme: s3a

It seems that Presto doesn't support the s3a schema.
I created an external table on Amazon S3 and used the location "s3a://xxx", then I could run all kinds of queries based on this table in Hive, but none of them could run in Presto, all returned the following error message:
Query 20150413_000647_00004_pnfam failed: No FileSystem for scheme: s3a

According to the Hadoop official document, Hadoop Wiki Amazon S3, S3A is a successor to the S3 Native, s3n.
So is there any plan  to support s3a filesystem?

@soulmachine no support for s3a yet. s3 and s3n are supported. We do not have s3a use case yet. Maybe I could simply patch and send you a PR to try?

@soulmachine I take a try at https://github.com/facebook/presto/pull/2682, maybe you could try building Presto with my PR and see whether it is working. Your comments and suggestions are appreciated.

I just merged @zhenxiao's patch, so this will be supported in the next release. Thanks for letting us know about this.
You might also be able to make this work with the current release by adding hive.config.resource=/path/to/config.xml to your Hive catalog properties file where config.xml contains the following:
<?xml version="1.0"?>
<configuration>
<property>
    <name>fs.s3a.impl</name>
    <value>com.facebook.presto.hive.PrestoS3FileSystem</value>
</property>
</configuration>

Thanks @zhenxiao @electrum !

@soulmachine, I am trying to create an external table on Amazon EMR AMI Version (3.7.0) that uses Hadoop 2.4.0 and Hive 0.13.1 using Amazon S3 bucket and s3a scheme. But I am getting error below:-

FAILED: Execution Error, return code 1 from org.apache.hadoop.hive.ql.exec.DDLTask. MetaException(message:Got exception: java.io.IOException No FileSystem for scheme: s3a)

Can you please enlighten me on how you were able to create external table using s3a scheme? Did you use the current versions available in Amazon AMI?


DOC: spatial: Fix some docstrings.

The docstrings for 'geometric_slerp', 'minkowski_distance', 'minkowski_distance_p' and 'tsearch' are updated:

Add a few missing 'Returns' sections, and move some sections around to comply with the NumPy docstring standard.
Copy-edit the 'minkowski_distance' and 'minkowski_distance_p' docstrings to reflect what they actually do.

Also fixed a few really long lines (PEP 8).

If this is squash-merged, only the first commit message is needed.


feat(interface): expose the interface struct

Expose the methods of the interface struct so we can access them outside the SDK.

LGTM even though clippy beta fails in CI


Editable installs now respect the value of wheel.install-dir

Attempting to fix: https://github.com/scikit-build/scikit-build-core/issues/866
I'm passing down wheel.install-dir to the editable redirect script and appending it to DIR so that rebuilds happen in the correct path. This worked for me in a local testing environment, but I'm not familiar with this codebase, so I don't know if this is an optimal solution.

FYI, https://github.com/scikit-build/scikit-build-core/blob/8cbd92f430c20ad5e0d9725198a1397ab599437d/src/scikit_build_core/settings/skbuild_model.py#L170 can't be None, I think you are introducing a None with the or.

Thanks for the help in adding that error check and a test!

Thanks for working on this! After I finish debugging https://github.com/pypa/cibuildwheel/issues/1975, I'll probably try to make a release.


Feature request: make beep.sh customization survive upgrades

Hello dear devs!
Is it possible to make the customized content of "beep.sh" part of the core config, so it is not overwritten by the next firmware update?

Hi @soder10,
Since the script hasn't changed over the years and I don't see work happening there I'd suggest a simpler approach: exchanging the script at boot start / stop time via our https://docs.opnsense.org/development/backend/autorun.html rc.syshook facility so you can move your beep.sh copy back to be the actual script that's going to be executed.
Cheers,
Franco

Hi @fichtner,
you mean, if I create my own custom beep.sh (e.g. modified parameters inside the script) and  copy it to both to /usr/local/etc/rc.syshook.d/start/ and /usr/local/etc/rc.syshook.d/stop/  --> give it some custom name, then the original boot.sh will be bypassed and only my custom beep.sh will be executed only?

almost, the start and stop script will have to overwrite the original beep.sh before it is used

Sorry for my ignorance, but closing this issue means your recommendation to copy beep.sh into the autorun rc.syshook is the solution for the future?

I took the lack of further response as a sign that the proposed solution works? I really don’t want a ticket around for a feature request that will not be worked on by the core team. It would be nicer if the Pull Request would be opened, reviewed and merged for a more portable solution when it was prepared by a submitter.

You arw right, I did not provide feedback. Actually I got stuck reading the dev docs about this syshook architecture, and what needs to be done where. Maybe its too high for me :-) I am not a Linux/BSD dev at all.

I'm more than happy to walk you through it. You have your modified beep.sh, right?

Thanks for the support! Yes, I have a custom "beep.sh" in /usr/local/sbin, with some custom values inside. I made a backup of the original and called it as beep.sh.original in the same dir, just in case.
I checked /usr/local/etc/rc.syshook.d/start, and it has the following file: "95-beep", its content is:
#!/bin/sh
/usr/local/sbin/beep.sh start
Similarly, /usr/local/etc/rc.syshook.d/stop, and it has "05-beep", its content is:
#!/bin/sh
/usr/local/sbin/beep.sh stop
So if /usr/local/sbin/beep.sh is edited, the change will be in effect until the beep.sh is restored to Opnsense default during a possible upgrade.
To avoid such overwrite, I would need to create a new file "beep.sh.custom", and modify the startup rc.syshook.d/start to add a new sequence before 95:
"94-copy-beep" with such content:
cp /usr/local/sbin/beep.sh.custom /usr/local/sbin/beep.sh
Similarly for rc.syshook.d/stop
"04-copy-beep" with such content:
cp /usr/local/sbin/beep.sh.custom /usr/local/sbin/beep.sh
Would that be the future-proof solution? Or am I missing the whole point here?

This is exactly right. But use the following content:
#!/bin/sh
cp /usr/local/sbin/beep.sh.custom /usr/local/sbin/beep.sh

And do this:
# chmod 755 /usr/local/etc/rc.syshook.d/start/94-copy-beep /usr/local/etc/rc.syshook.d/stop/04-copy-beep

You could even build a single file installable plugin for this in case you need to install it on different machines, but that's for later if needed.

Cool, thanks!


Updated Roadmap

I'm very interested in the actual Ionic Roadmap and Vision of you guys. This one seems to be outdated: https://docs.google.com/document/d/1Qlc5X2eJyOB0izkFlH7KJ5BmMi0MeXUZRHJHt3hS6Wo/edit

Hey @tmvnk, you are correct that it is outdated. I've updated that document to include some high level goals, but we probably won't be updating it with individual issues for a bit. The best place to see current bugs / features that we are working on are the milestones: https://github.com/driftyco/ionic/milestones
Currently our main goals include making app's faster and improving routing. All of our work on this can be found on the 3.0 branch: https://github.com/driftyco/ionic/tree/3.0
To see exactly what we are working on every week, please take a look at our framework meeting notes which we update (nearly) every Monday: https://docs.google.com/document/d/1LrPDUkfXpqPIsghaSCxHyN1GIZ0TK2bwFxOZx2GKWtI/view
I hope this helps! Thanks for the issue. 🙂


ERROR: Forbidden when s init xinwuyun/start-fg

Describe the bug
A clear and concise description of what the bug is.
Screenshots

Desktop (please complete the following information):

OS: darwin-x64
Version: @serverless-devs/s: 2.1.1,node-v12.15.0

Additional context
s init xinwuyun/start-fg

已完成优化


#737 Add a temporary "advanced projection" section in the documentation

@pauldendulk I'll try to make your requested changes as soon as possible but for now i propose some minor changes to document our discution. Do not hesitate to tell me if  it's not appropriate.
Greetings

 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.LOOS Antoine 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.

@antoineloos why was this closed?


How to store and query array of key value pairs?

My data format is like:
{
  timestamp string,
  name string,
  kind int,
  status_code int,
  ...
  tags: {
    key1: value1,
    key2: value2,
    ...
  }

}

The list of keys in tags is varying in size for each row and the keys are also not defined (it can be anything string).
I want to query dataset by tags, i.e., return all rows which have given key: value pair.
In Pinot, we can achieve this by storing all keys in a multi-value dimension TAGS__KEYS and all values in another multi-value dimension TAGS__VALUES and then query using MAP_VALUE function.
Sample query:
SELECT * FROM xyzView WHERE ( tags__KEYS = 'key1' AND tags__VALUES = 'value1' AND mapValue(tags__KEYS,'key1',tags__VALUES) = 'value1' )
How can we achieve the same in Druid? Druid also has a multi-value dimension but does not have mapValue functionality. Or can we achieve this using any other way in Druid?

you can store tags as an array of concatenated KEY__VALUE and use an extraction function ( https://druid.apache.org/docs/latest/querying/dimensionspecs.html#extraction-functions ) in your query filter

@chrisociepa Can you please detail down? I have TAGS__KEYS and TAGS__VALUES as multi-value dimension. Extraction functions, as I saw mostly used regex to match data. Regex won't work in this case Eg, multiple keys can have value true but we then won't know which one really did. Or am I missing something?

you can use the js exctraction function to extract keys and values from concatenated pairs ( https://druid.apache.org/docs/latest/querying/dimensionspecs.html#javascript-extraction-function ). So either in filters or in grouping you can use the exctraction function

you can use the js exctraction function to extract keys and values from concatenated pairs ( https://druid.apache.org/docs/latest/querying/dimensionspecs.html#javascript-extraction-function ). So either in filters or in grouping you can use the exctraction function

most common approach to handle that in Druid is to flatten the schema during/before ingestion so that in the end Druid datasource columns are [timestamp, name, kind, status_code, key1, key2,..] .
Then there are no problems on query side.

@himanshug But the number of keys and the keys themselves are not fixed. It varies for every event.

@himanshug But the number of keys and the keys themselves are not fixed. It varies for every event.

that is fine, Druid ingestion has a mode where it "discovers" the dimensions and that would be appropriate for this use case. In the end, when segment is built it will have list-of-dimensions = union-of(dimensions in all events)
quoting from  https://druid.apache.org/docs/latest/ingestion/index.html#dimensionsspec
"If this and spatialDimensions are both null or empty arrays, Druid will treat all non-timestamp, non-metric columns that do not appear in dimensionExclusions as String-typed dimension columns. See inclusions and exclusions below for details."

This seems interesting. So, it will keep updating the schema as it ingests events with new keys? Let me give it a try


Migrate Image Training Endpoint to Django

Migrate Image Training Endpoint to Django
Github Issue Number Here: Feature#993
What user problem are we solving?
With the ongoing migration from Flask Blueprint to Django for better scalability and maintainability, we need to ensure that the training endpoints for image datasets continue to function as expected. Users need a reliable endpoint to submit image training requests and this migration aims to improve the overall infrastructure.
What solution does this PR provide?
This PR introduces the /image route within the Django framework, replacing the old Flask Blueprint route. The new route handles image training requests, particularly focusing on classification tasks as regression is not supported. The structure of this endpoint is mirrored from the specified reference, with adjustments made to fit the Django framework. The old image train code served as inspiration for ensuring that the necessary features and behaviors are retained.
Testing Methodology
Testing yet to be done but to verify the functionality and integrity of the new /image route, but when testing begins, we can submit training requests using torch built-in datasets (MNIST, FashionMNIST) to ensure that models train as expected and the endpoint returns accurate results.
Also use postman for testing .
Any other considerations

@karkir0003 @dwu359
took a stab at this. a couple questions i had was.

What should the correct path be in ImageDefaultDatasetCreator constructor (dataset.py)? Here is the code I am referring to:

   self.train_set = datasets.__dict__[dataset_name](root='./backend/image_data_uploads', train=True, download=True, transform=self.train_transform)   self.test_set = datasets.__dict__[dataset_name](root='./backend/image_data_uploads', train=False, download=True, transform=self.test_transform)
With transition to django, is the path for data uploads still gonna be in backend/data_uploads?

Does my image.py look good in /routes/image? Is there any particular i have to add for image training?

Any additional schemas for image classification? I think i got the right ones.

for image data uploads, please dont use backend/ dir.

for image data uploads, please dont use backend/ dir.

sure, then what directory do i use? I dont see a similar directory in /training

i think u can test the endpoint out @codingwithsurya

for image data uploads, please dont use backend/ dir.

sure, then what directory do i use? I dont see a similar directory in /training

should be clarified

for image data uploads, please dont use backend/ dir.

sure, then what directory do i use? I dont see a similar directory in /training

should be clarified

yea looks good. i just commited what we talked about. and i'll test on colab as well soon when i get a chance.

added minor comments on static typing python

addressed all these

TO-DO: find viable nnSequential PyTorch MNIST Architecture

TODO: Cross-Entropy Loss not computing correctly. Figure out correct param for FLATTEN in current architecture.
Otherwise, we can make our own

TODO: Train/test transforms as parameter to endpoint. CIFAR10 Testing.


⚠ ClamAV has degraded performance

In 88d704a, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 76 ms

Resolved: ClamAV performance has improved in f0c023e after 11 minutes.


scp name

other players can see the name of the scp 600 ,
even if he kills a class d the name of scp 600 won't disappear ,
is there a way to hide the name from other players so he can't be spotted so easily ,
ty.

custom_info: 'SCP-600V' -> custom_info: ''
try it


Add bevy_entropy plugin and include it in the default set

Objective

Bevy games / applications often need to use random number generators, but they make execution non-deterministic. Currently there is no official way to introduce determinism in a bevy-supported way.

Solution

Include a source of entropy to (optionally) enable deterministic random number generators. The plugin can be completely disabled if no source of entropy is required, the default entropy from the OS can be used if randomness is needed but deterministic execution is not, or a world seed can be specified for deterministic random number generation.

Note that I put up a PR previously to add default rngs. While most other engines (godot, unity, etc) provide built-in rngs, this is a lower-level (and more general?) building block we likely want to start with first.
Open items

[x] Is the naming ok? Entropy or EntropySource? get()? Naming is ok
[x] Should this be a plugin or in core? One can make the argument that entropy is as core as time and thus should always be there. Plugin is better and time might move out of core.
[x] Tests
[ ] Docs (did I miss these in the repo?)
[ ] Changelog item

I don't think this is deterministic where there is system ordering ambiguity - afaik I we don't make a promise about execution order in that case
However, I hadn't realised that a mutable resource would be deterministic if ordering is well defined - although obviously that does have the cost of making all entropy access serial.
One potentially neat thing would be for the rng to be a custom system parameter, which gets a 'system level' rng seed, without blocking the global entropy. We would probably need a pre-run hook which could hold resources for only a short amount of time (alternatively, chained systems could support something similar and those could be used instead)

Preface: I think that standardizing on a solution here is extremely important. Without it, each crate in the ecosystem will use their own PRNG solution, bloating dependencies and making a unified approach to determinism pretty much impossible.

I don't think this is deterministic where there is system ordering ambiguity - afaik I we don't make a promise about execution order in that case

We can currently use the single-threaded executor when we want drop-in determinism. There's space in the future for more sophisticated parallel executors as well.

One potentially neat thing would be for the rng to be a custom system parameter, which gets a 'system level' rng seed, without blocking the global entropy

Agreed, this would be extremely useful, and worth baking into Bevy as a whole. RNG use will be quite prevalent in some games, and it would be nice to have a non-blocking solution.

We would probably need a pre-run hook which could hold resources for only a short amount of time (alternatively, chained systems could support something similar and those could be used instead)

I prefer the former solution; I would probably build it using a simple exclusive system that runs at the start of the schedule and initializes the Local data of each RNG dependent system. Could you expand a little on how you think system chaining could work @DJMcNab?

The basic idea of how the system chaining would work is that the first system in the chain would only block the resources that it uses.
E.g. a system with a resmut parameter could be chained after a relatively long running system without blocking other system's access to that value, such as to update it at the end of the frame, say
Basically change chaining into dependencies with 'message passing'
Also our single threaded executor also doesn't guarantee ordering afaik, it's just a way to run the parallel system graph but only using one thread

Also our single threaded executor also doesn't guarantee ordering afaik, it's just a way to run the parallel system graph but only using one thread

Right... it runs it in topographic order, but that topographic order may vary freely within the constraints between runs.

Is the naming ok? Entropy or EntropySource? get()?

I much prefer Entropy. It's perfectly clear and we're going to need to type this a lot.

Should this be a plugin or in core? One can make the argument that entropy is as core as time and thus should always be there

Hmm. It would force a dependency on rand for every Bevy app, which is not great. I see your point though.

Docs (did I miss these in the repo?)

The doc strings and examples here are quite good so far. You could add module level documentation, but what probably makes more sense is to add a page on RNG as part of chapter 3 of the new book in the bevy-website repo. See https://github.com/bevyengine/rfcs/blob/main/rfcs/23-quick_start_book.md for an overview of the plan there.

@LegNeato we're currently undergoing relicensing to add Apache in addition to MIT. Could you please agree to this relicense over in https://github.com/bevyengine/bevy/issues/2373?

Commented. Will try to clean this up in the next day or so.

Not sure why the ci job is failing with something related to jni, I didn't touch anything there. Any pointers would be appreciated.
I'll look into automatically making rngs or entropy per-system if this lands.

Ah, the same CI issue exists on master:
https://github.com/bevyengine/bevy/runs/3326099396

This is now a part of an RFC: https://github.com/bevyengine/rfcs/pull/55

What are the pros/cons of this versus bevy_rand, besides this being intended to be built-in? Are there any design ideas to merge in or anything like that?

This predates bevy_rand and inspired a bit of it (and the verbage of much of the bevy_rand explanation is reused from the RFC associated with this).

Closing in favor of https://github.com/bevyengine/bevy/pull/7871 and/or bevy_rand. I still think this needs to be built into bevy.


Allow to hide the icon in the editor's title

Currently it shows up when any editor is open. In most of the time it's not relevant.

Will be fixed in next release!

Thanks!
FYI, you can close the issue with the commit that solves it: https://help.github.com/en/enterprise/2.16/user/github/managing-your-work-on-github/closing-issues-using-keywords


[PREPARES FOR JENKINS-36871] Fix findbug errors and jelly files

@reviewbybees

This pull request originates from a CloudBees employee. At CloudBees, we require that all pull requests be reviewed by other CloudBees employees before we seek to have the change accepted. If you want to learn more about our process please see this explanation.


Create SECURITY.md

@jklein24 Let me know how you like this, and if you're okay with it, I'll make for our other projects as well.


Support OTP in XMonad.Prompt.Pass

Description
Support OTP type password in XMonad.Prompt.Pass. This require pass-otp (https://github.com/tadfisher/pass-otp) has been setup in the running machine.
Checklist

[x] I've read CONTRIBUTING.md

[x] I tested my changes with xmonad-testing

[x] I updated the CHANGES.md file

Thanks!


Update to latest buildkit

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 11 committers have signed the CLA.:x: thaJeztah:x: tiborvass:x: alexcb:x: tonistiigi:x: AkihiroSuda:x: crazy-max:x: ktock:x: chang-andrew:x: andreabolognani:x: hinshun:x: vladaionescuYou have signed the CLA already but the status is still pending? Let us recheck it.

0 out of 11 committers have signed the CLA.

I've removed CLA bot from this repo as it's not necessary.


Golang support for tf.Variable

System information

TensorFlow version (you are using): unsure
Are you willing to contribute it (Yes/No): yes

Describe the feature and the current behavior/state.
I don't see any equivalent of "tf.Variable" in the Go API:
https://pkg.go.dev/github.com/tensorflow/tensorflow/tensorflow/go#section-readme
and
https://pkg.go.dev/github.com/tensorflow/tensorflow/tensorflow/go/op
Will this change the current api? How?
It will change the Go API.
Who will benefit with this feature?
Golang users who want to train models.
I have a model I am creating in Golang and then sending to Python to use the optimization API. I need tf.Variable objects to pass to the minimize function.
Any Other info.
I mistakenly filed this FR in an unofficial repo: https://github.com/galeone/tfgo/issues/62

@gonzojive Please take a look at this explanation, where its clearly explained why there is no support to tf.variable in Golang.

But it's not worth it IMO since the support for static-graph + session execution is enough for every application: just write the graph in Python (a function decorated with @tf.function) and export it as a SavedModel - the graph can contain any layer, with variables and so on. The exported graph can be loaded into tfgo and used, being the state (the value of the variables) managed by the TensorFlow runtime (the C library) and not by the bindings.

Thank you @galeone for the explanation. The feature request would allow building the graph with Go, not Python. Perhaps it is infeasible.
Is there an RPC API for graph building? Go could use that.

Is there an RPC API for graph building? Go could use that.

Not at the moment, but we may consider it - although it will be some time out.

@gonzojive: You might be interested in my experimental fork, which focusses on reviving the golang binding also for training. It already supports op.Variable, tf.Func, op.While and many more ops than upstream. See some examples here.

Hi,
Thank you for opening this issue. Since this issue has been open for a long time, the code/debug information for this issue may not be relevant with the current state of the code base.
The Tensorflow team is constantly improving the framework by fixing bugs and adding new features. We suggest you try the latest TensorFlow version with the latest compatible hardware configuration which could potentially resolve the issue. If you are still facing the issue, please create a new GitHub issue with your latest findings, with all the debugging information which could help us investigate.
Please follow the release notes to stay up to date with the latest developments which are happening in the Tensorflow space.


Translate into Arabic

files require translation:

[ ] def/ar/about.cson
[ ] def/ar/context.cson
[ ] def/ar/menu_darwin.cson
[ ] def/ar/menu_linux.cson
[ ] def/ar/menu_win32.cson
[ ] def/ar/settings.cson

for more info please checkout CONTRIBUTING.md

Are there any work left to be done on this issue? Shouldn't this issue be closed after the merge?

Translation reviewed https://github.com/liuderchi/atom-i18n/pull/279


Began Work on Fixing Nested Syntax

NOTE: This PR is not ready to merge!
I have begun working on fixing #519, but I have reached a bit of a stumbling block. I have gotten shift-reader.js to accept files with nested syntax, but something is getting garbled in between (details below), leading me to believe that I'm missing some step in the expander pipeline.
To explain where I'm at, here's what I know:

The reading of syntax templates (and, well, everything else) is done in src/shift-reader.js.
Syntax objects begin when src/shift-reader.js's advance function (master) returns a token of type LSYNTAX.
The contents of syntax objects are read like normal syntax; the only thing that makes them special
is that the handler for LSYNTAX bundles all of the read pieces together into an immutable list.
The reason for the error that is mentioned in the bug report is because advance in src/shift-reader.js does not handle the "`" character (or it's escaped variant), so it delegates to the superclass (which also does not handle it).

Thus, I figured that fixing the error would just be a matter of adding the proper escapes to advance, allowing nested syntax objects to be read correctly. As far as reading the syntax goes, this all seems to work correctly. Note: This change is what the first commit of this PR reflects.
So, what happened? I tried to run this modified version on the following code:
syntax makeSayer = function(ctx) {
  let x = ctx.next().value;
  return #`syntax ${x} = function(ctx) { return \`console.log('hello world')\`; }`;
}

makeSayer hi

The result was the following error messsage:
/home/belph/git-belph/sweet.js/dist/syntax.js:174
        return s_701.addScope(scope_696, bindings_697, options_698);
                    ^

TypeError: Cannot read property 'addScope' of null
    at /home/belph/git-belph/sweet.js/dist/syntax.js:174:21
    at /home/belph/git-belph/sweet.js/node_modules/immutable/dist/immutable.js:3018:46
    at List.__iterate (/home/belph/git-belph/sweet.js/node_modules/immutable/dist/immutable.js:2208:13)
    at IndexedIterable.mappedSequence.__iterateUncached (/home/belph/git-belph/sweet.js/node_modules/immutable/dist/immutable.js:3017:23)
    at seqIterate (/home/belph/git-belph/sweet.js/node_modules/immutable/dist/immutable.js:606:16)
    at IndexedIterable.IndexedSeq.__iterate (/home/belph/git-belph/sweet.js/node_modules/immutable/dist/immutable.js:322:14)
    at IndexedIterable.mixin.toArray (/home/belph/git-belph/sweet.js/node_modules/immutable/dist/immutable.js:4260:23)
    at new List (/home/belph/git-belph/sweet.js/node_modules/immutable/dist/immutable.js:2067:62)
    at reify (/home/belph/git-belph/sweet.js/node_modules/immutable/dist/immutable.js:3572:37)
    at List.mixin.map (/home/belph/git-belph/sweet.js/node_modules/immutable/dist/immutable.js:4403:14)

Let's first dissect the syntax object in question as follows:
<ret> = #`syntax ${x} = function(ctx) { \`console.log('hello, world')\`; }`
                                        |------- <ret_nested> --------|

Now, here's what I can tell happens:

read (my fork's copy) will tokenize <ret> and <ret_nested> just fine; <ret> is an immutable list with an entry at index-whatever that is another immutable list corresponding to <ret_nested>
Sometime between then and the return value of the call to deserializer.read(str) in loadForCompileTime (my fork's copy), the location of <ret_nested> in <ret> is set to null. Why? Not a clue.

And that is where I'm at. Am I missing some step here? I feel like this is, if nothing else a step in the right direction; nested syntax is a powerful feature to have, so I'd love to get this fixed!

So I just had a crazy idea. Syntax template are already syntactically special so what if we just don't escape them? Beginning (#`) and ending (`) delimiters are always distinguished so there is no syntactic reason to escape them. Just start a recursive read when you get to a #` inside a read of an outer syntax template.
Normal templates still need to be escaped of course.
syntax m = ctx => {
  return #`
    syntax n = ctx => {
      let s = \`foo\`;
      return #`
        syntax o = ctx => {
          return #`1`
        }
      `
    }
  `
}

This avoids the need to count backslashes and all that.
This approach confuses existing syntax highlighters a little but since all the backticks must be balanced the confusion is localized to the syntax templates themselves.
Does this seem reasonable or am I missing something?

@disnet That seems perfectly reasonable (it's the same approach Racket takes!)

Oh! The trick is nested interpolations:
let s = #`
  let ss = #`foo \${42}`
`;

You'll need to count escapes for those I think.

Okay, so a double escape look like \\${42}, but what would a triple escape look like? \\\${42} or \\\\${42}? If it's the latter, what about using something like Racket's unquote-syntax shorthand (#,) to avoid an exponential blowup of escapes?

How would #, help?

Using the standard escaping for \, one can see that #, quickly becomes considerably less typing (and is much more descriptive of the unescaping depth)

Depth
Escape sequence with \
Escape Sequence with #,

0
${42}
${42}

1
\${42}
#,${42}

2
\\\${42}
#,#,${42}

3
\\\\\\\${42}
#,#,#,${42}

4
\\\\\\\\\\\\\\\${42}
#,#,#,#,${42}

Ah! I see what you meant. Yeah do that 😄

@disnet if we took care of syntax templates with a combination of reader macros and syntactic extensions, we could do this:
syntax m = ctx => {
  return #`
    syntax n = ctx => {
      let s = \`foo\`;
      return ${ #`
        syntax o = ctx => {
          return ${ #`1` }
        }
      ` }
    }
  `
}

This way a syntaxTemplate macro could take care of converting nested term objects back into escaped syntax template strings and would be transformed to:
syntax m = ctx => {
  return syntaxTemplate`
    syntax n = ctx => {
      let s = \`foo\`;
      return ${ syntaxTemplate`
        syntax o = ctx => {
          return ${ syntaxTemplate`1` }
        }
      ` }
    }
  `
}

Thus m gets transformed to:
syntax n = ctx => {
  let s = \`foo\`;
  return ${ #`
    syntax o = ctx => {
      return ${ #`1` }
    }
  ` }
}

@gabejohnson humm...I'm not following. Could you expand (ha!) on what you meant?

My point is that if you just require interpolating if you're nesting syntax templates you can avoid any special syntax and just parallel the syntax used by template literals already:
syntax m = ctx => {
  return #`
    syntax n = ctx => {
      let s = \`foo\`;
      return ${ #`
        syntax o = ctx => {
          return ${ #`${ ctx.next().value }` }
        }
      ` }
    }
  `
}

vs.
syntax m = ctx => {
  return #`
    syntax n = ctx => {
      let s = \`foo\`;
      return #\`
        syntax o = ctx => {
          return #\`\\${ ctx.next().value }\`
        }
      \`
    }
  `
}

or
syntax m = ctx => {
  return #`
    syntax n = ctx => {
      let s = \`foo\`;
      return #`
        syntax o = ctx => {
          return #`\\${ ctx.next().value }`
        }
      `
    }
  `
}

While there are more characters at shallow nesting depths, you don't have to count slashes as you nest.

@gabejohnson I like that, I think it feels the most natural.

Something I just thought of. Which context does the innermost ctx refer to?


Defining dispatcher.utter_message() in action_session_start causing issue in interactive learning

Rasa Open Source version
3.0
Rasa SDK version
3.0
Rasa X version
No response
Python version
3.8
What operating system are you using?
Linux
What happened?
Using dispatcher.utter_message in action_session_start results in an error when running interactive learning
class ActionSessionStart(Action): """Executes at start of session"""
def name(self) -> Text: """Unique identifier of the action""" return "action_session_start"
async def run( self, dispatcher: CollectingDispatcher, tracker: Tracker, domain: Dict[Text, Any], ) -> List[EventType]: """Executes the custom action"""

the session should begin with a session_started event events = [SessionStarted()]

add action_listen at the end events.append(ActionExecuted("action_listen"))

dispatcher.utter_message(text="Hello there!")
return events
Command / Request
rasa interactive
Relevant log output
2022-01-21 11:45:03 INFO root - Rasa server is up and running.
 Processed story blocks: 100%|███████████████████████████████████████████████████████████████| 6/6 [00:00<00:00, 4054.43it/s, # trackers=1](#trackers=1)(#trackers=1)
 Processed rules: 100%|██████████████████████████████████████████████████████████████████████| 6/6 [00:00<00:00, 7043.33it/s, # trackers=1](#trackers=1)(#trackers=1)
 [2022-01-21 11:45:03 -0500] [56064] [ERROR] Exception occurred while handling uri: 'http://localhost:5005/conversations/7107bd6567054e92812e7eec81c0a591/tracker?include_events=ALL'
 Traceback (most recent call last):
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/sanic/app.py", line 770, in handle_request
 response = await response
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/rasa/server.py", line 254, in decorated
 return await result if isawaitable(result) else result
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/rasa/server.py", line 703, in retrieve_tracker
 tracker = await app.agent.processor.fetch_tracker_with_initial_session(
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/rasa/core/processor.py", line 322, in fetch_tracker_with_initial_session
 await self._update_tracker_session(tracker, output_channel, metadata)
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/rasa/core/processor.py", line 267, in _update_tracker_session
 await self._run_action(
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/rasa/core/processor.py", line 894, in _run_action
 await self.execute_side_effects(events, tracker, output_channel)
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/rasa/core/processor.py", line 795, in execute_side_effects
 await self._send_bot_messages(events, tracker, output_channel)
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/rasa/core/processor.py", line 811, in _send_bot_messages
 await output_channel.send_response(tracker.sender_id, e.message())
 AttributeError: 'NoneType' object has no attribute 'send_response'
 2022-01-21 11:45:03 ERROR rasa.core.training.interactive - An exception occurred while recording messages.
 Traceback (most recent call last):
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/rasa/core/training/interactive.py", line 1486, in record_messages
 await _plot_trackers(events_including_current_user_id, plot_file, endpoint)
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/rasa/core/training/interactive.py", line 1422, in _plot_trackers
 event_sequences = await _fetch_events(conversation_ids, endpoint)
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/rasa/core/training/interactive.py", line 1393, in _fetch_events
 tracker = await retrieve_tracker(endpoint, conversation_id)
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/rasa/core/training/interactive.py", line 196, in retrieve_tracker
 result = await endpoint.request(
 File "/Users/chris/miniforge3/envs/rasa/lib/python3.8/site-packages/rasa/utils/endpoints.py", line 173, in request
 raise ClientResponseError(

Hi everyone, hello @b-quachtran,
I have a similar issue. Is there any developent on this? or any workaround that you found?
This issue also happens when using "Talk to your bot" on RASA X. My error message is:
Encountered an exception while running action 'action_session_start'.Bot will continue, but the actions events are lost. Please check the logs of your action server for more information.
Traceback (most recent call last):
  File "/opt/venv/lib/python3.8/site-packages/rasa/core/processor.py", line 869, in _run_action
    events = await action.run(
  File "/opt/venv/lib/python3.8/site-packages/rasa/core/actions/action.py", line 750, in run
    bot_messages: List[Event] = await self._utter_responses(
  File "/opt/venv/lib/python3.8/site-packages/rasa/core/actions/action.py", line 699, in _utter_responses
    generated_response, tracker, output_channel.name(), **response
AttributeError: 'NoneType' object has no attribute 'name'

Using rasa open-source 3.1.0 and rasa x 1.1.0
Thank you in advance,
Sören

Is there any update on this? What is exactly the cause of the error? If you help me, I could also try to contribute.


composer install does not work (error)

composer install does not work (error)

What kind of error do you have?


Support DynamicList templates as part of standard schema

LUIS recognizers support the ability to define dynamic lists that are passed in at runtime.  To do this your LUIS model needs to have a place holder entity which is statically populated at training time and dynamically populated at runtime.  The LUIS recognizer would look like:
"recognizer": {
"$kind": "Microsoft.LuisRecognizer",
"applicationId": "=settings.luis.DynamicLists_test_en_us_lu.appId",
"endpoint": "=settings.luis.endpoint",
"endpointKey": "=settings.luis.endpointKey",
"dynamicLists": "=[dialog.PersonValue, dialog.RoomNumberValue]"
}
Then we would have an action template to fill in the runtime definition of dialog.person and hang that off of beginDialog.  It would have a SetProperty(dialog.person, LISTSTRUCTURE).  The default definition would be the same one generated for the training time, but this would give people a place to dynamically calculate the list to pass in.
Inside of BeginDialog is an action which looks like:
{$kind: Microsoft.SetProperty, property: "dialog.PersonValue", value: "{
                    "entity": "PersonValue",
                    "list": [
                        {
                            "canonicalForm": "Chris McConnell",
                            "synonyms": [
                                     "Chris",
                                     "McConnell"
                            ]
                        },
                        {
                            "canonicalForm": "Zongyang",
                            "synonyms": [
                            ]
                        }
                    ]
                },

To actually make this dynamic someone could call the graph API and compute this structure to set in memory that would then be passed into the LUIS recognizers.
This schema should be of type string with $examples that look like enum $examples.
Person: {$ref: "dynamiclist.schema", $examples: {"": {PersonValue: { "Christopher McConnell": ["Chris", "Christopher"]}}}.  Then from this you generate a PersonValue LUIS list with the $examples and you use the same name when passing in a dynamic list.
You can view this as an open-ended enum (which is why its type is just string) where you can statically define training data and at runtime supply dynamically defined definitions.

Define dynamiclist.schema.   Type is string and may be able to reuse enum templates.
Extend recognizer template to add dynamiclists and the list is empty if there are no dynamic templates.
For each dynamic property add a SetProperty action to the begin dialog for setting the dynamic list in memory.

Examples from tests: botbuilder-dotnet-main\tests\Microsoft.Bot.Builder.AI.LUIS.Tests\tests\LuisAdaptiveRecognizerTests\DynamicLists.test.dialog

I go through all the codes related to dynamiclist in botbuilder-dotnet. I think the logic as follows:
If options.dynamiclist is not null, it will be added in the query content. The query content with uri will be sent to LUIS server (implemented in the function of RecognizeInternalAsync). Based on my understanding, the data in the dynamiclist will be trained when LUIS server receiving it. When LUIS trains data in dynamiclist, does it need the corresponding lu file with example utterances? In that case, why do we need to set property in begin dialog, since dynamiclist already includes all information needed?
I think the usage of dynamiclist.schema is similar to that of form-global.en-us.data, we have some templates and use functions like substitutions to replace some parameters with $example of PropertyValue. Then the dynamiclist of the PropertyValue is generated. Is my understanding correct?


Enable rails/delegate on .rubocup.yml

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew typecheck with your changes locally?
[x] Have you successfully run brew tests with your changes locally?

enable  rails/delegate on .rubocup.yml because of # TODO and change some methods to  delegator

I suggest not using Rail's delegate method and using Forwardable's ones instead (you might need to use def_delegator instead of delegate to satisfy Sorbet in some cases). The less unnecessary dependency on activesupport the better.


fn routes create generates broken reference to existing image

When issuing:
fn routes create myapp /hello -i shaunsmith/hello-node:0.0.8
The result is:
/hello created with shaunsmith/:0.0.1

The image name is missing and the tag is incorrect.
fn routes list myapp confirms the route is setup wrong:
path		image				endpoint
/hello		shaunsmith/:0.0.1		localhost:8080/r/myapp/hello

Took a look at this - fn routes create is still loading the func file and --image doesn't seem to do anything
adding
name: to the func file allows this to work

closed by #75


Add definitions validation with GA

Add questionnaire validation script (run by Github Actions)
This validation has 2 parts:

1. Questionnaire Schema Validation

Added questionnaire definition schema with required properties and so definitions can be validated against those
This also includes input type validation so only supported input types can be added
This also includes text input type validation so only supported text input types (text, date, time, etc) can be added

2. Branching Logic Validation

This also checks whether the branching logic (key in definitions: branching_logic) is valid
This has 2 parts: first, it checks whether the logic identifiers/keys are actual field names in the questionnaire
Second, this checks whether or not the values in the logic are correctly wrapped in quotes.

I was also thinking we had this GSoC project this also might be an opportunity to build this validation process into any future questionnaire-building interface.
https://github.com/RADAR-base/GSoC/tree/main/project-ideas_2023 project "1A. aRMT Questionnaire Generator"
Though in lieu of that running this as part of the GH Actions is good

LGMT, nice bit of fixes already with the action failing relieved

Proof the system works! :+1:


Base control plane Docker images on scratch instead of base.

The control plane is proxied through the Conduit proxy. The Conduit
proxy is based on the base image, and the control plane containers
and the proxy share a networking namespace. This means we don't
need the extra base utilities in the controller images since we can
use the utilties in the proxy image.
This is a step towards building the initial no-networking Conduit CA
pod. Since the Conduit CA will not do any networking of its own, we
networking debugging utilties are not helpful for it. They are
actually an unnecessary risk because they could facilitate the
exfiltration of the private key of the CA. (The Conduit CA pod won't
have the Conduit Proxy injected into it either.)
This also simplifies & slightly speeds up the building of the
controller images. This is a stepping stone towards being able to
build the controller images without docker build to improve build
times.
Signed-off-by: Brian Smith<EMAIL_ADDRESS>

This shouldn't be merged until after #347 is merged, since #347 is what adds the proxy to the control plane.

This sounds like a generally fine thing to me. You might consider adding an ARG RUNTIME_IMAGE-scratch at the top and using FROM $RUNTIME_IMAGE so that it's possible to build these images i.e. with the Go toolchain/gdb/whatever?

This is a stepping stone towards being able to build the controller images without docker build to improve build times.

Is this described in another issue? I really value that docker provides a repeatable build environment where we don't have to worry about my local GOPATH, etc... but I'm open to anything faster if it's as reproducible as what we have today.

This is a stepping stone towards being able to build the controller images without docker build to improve build times.

Is this described in another issue? I really value that docker provides a repeatable build environment where we don't have to worry about my local GOPATH, etc... but I'm open to anything faster if it's as reproducible as what we have today.

Yes, it is described in PR #341. I agree that we need to provide a repeatedable build environment.


Test update of toolchain.

TODO:

Update wasmtime and remove final reference to github.com/egrimley-arm

Draft log message for this PR:
Update Rust toolchain for Icecap and use stable compiler for rest.
Icecap now uses nightly-2021-08-25 and the rest uses stable 1.56.1.
In the new submodule icecap/sysroot/rust:

Updates for internal API changes.
A HACK: some locks are disabled.
The submodule src/llvm-project is removed to save disc space.

In this repo changes include:

Various features are removed to enable use of stable compiler.
Crate versions updated, including: hex, lexical-core, x509-parser
HACK to save disc space in icecap/Makefile: rm -rf ../sdk

Will this PR eventually turn into the one that we use to merge recent Rust support into Veracruz?

Will this PR eventually turn into the one that we use to merge recent Rust support into Veracruz?

Yes, I hope. Lots of tidying to be done, and can we avoid checking out all of rust plus llvm?

https://github.com/veracruz-project/veracruz/runs/4533192689:
LLVM ERROR: IO failure on output stream: No space left on device
error: could not compile `serde`
warning: build failed, waiting for other jobs to finish...
error: couldn't create a temp dir: No space left on device (os error 28) at path "/tmp/nix-build-rustc-nightly.drv-0/source/build/x86_64-unknown-linux-gnu/stage0-rustc/x86_64-unknown-linux-gnu/release/deps/rmetaq91uih"

The issue here is that the Docker image that the CI for IceCap is running on is not primed with the right Nix store paths, so Nix is having to build a lot from scratch, ultimately exhausting disk space. The solution is to build and push a new IceCap CI Docker image, and refer to it in .github/.
See veracruz/icecap/docker/Makefile for details, or we can discuss 1-1.

make ci-build fails for me. That might be because I've had to point icecap/icecap at my own fork.

@egrimley-arm: what is the status of this PR?  Is it ready for review?

@egrimley-arm the PR removing the proper dependency from wasi-types has now been merged.

There is still one reference to egrimley-arm, for wasmtime. The required change in wasmtime is to delete four lines of the form #![feature(...)]. If I remember correctly, with those lines the code works with any "nightly" compiler (though you get a warning with more recent compilers), and without them the code works with any recent compiler, "nightly" or stable. Should we just make the change to wasmtime immediately before this PR is merged? (We already have veracruz-v1 branch of wasmtime.)

Yes, I think we should merge the changes into our fork of wasmtime.  All forked dependencies need to be under the veracruz-project organization, rather than personal accounts.
Is there an existing PR for that?

Yes, I think we should merge the changes into our fork of wasmtime. All forked dependencies need to be under the veracruz-project organization, rather than personal accounts.
Is there an existing PR for that?

https://github.com/veracruz-project/wasmtime/pull/9, which should be merged immediately before this PR
(updated to refer to veracruz-project instead of egrimley-arm).

I think we're now in a position to proceed. I've approved the wasmtime changes and modulo the change in the wasmtime dependency in this changeset, pointing it away from your repository and toward the project's, this is also now in a position where it is ready to be merged.

OK, let's do it then!


Remove unneeded Configurators.

We now have roseEditorConfigurator to configure Publisher and Author
and ScientistConfigurator to configure the top level Scientist component.

https://github.com/substance/substance/pull/743 must be merged first.


If PromptLoginBehavior is null then the TranslateToFreshPasswordAuth …

…behavior is applied.
#signoff

@billmath Please confirm if this text is okay to merge. Thanks!!

#sign-off


Indicate that the type pattern supports generic arguments

Fixes #10334
Relies on dotnet/samples#803
In addition, review and update modified topics.

closing and re-opening for a fresh build.


integrate socketcan-io4edge and ttynvt-runner

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


Nginx: Improve tracing

Add possibility to use HTTP OTLP exporter.
Improve tracing so that module creates internal or client span depending if the request is handled by Nginx directly or passed upstream.
Set span status depending on result. If status code is between 400 - 599 set status as error.
Catch internal processing failures in log phase.
Rewrite tests in JS

Because of how Nginx works we can't determine what module will serve the actual request before its served. For what purpose I have implemented ProxyRecordable which makes it possible to change the span kind after processing in log phase.

@esigo any plans with this one?

Just wanted to add an upvote on this one, I reached out to the nginx team and they were resistent to adding client spans to the instrumentation itself, so this seems like the best path forward:
https://github.com/nginxinc/nginx-otel/issues/17

I've got mixed feelings regarding span status. For example, it isn't always clear whether 4xx status codes are "errors". Does OTEL specification have clear stance on these?
Perhaps configuration flag for defining which status codes are viewed as span errors would be enough?

I wouldn't consider 4xx's errors either, every time we did it in our other instrumentation it lead to a lot of false positives / noise.

@esigo / @seemk what would be required to move this forward?


updated css logo to the latest version

Updated CSS Icon(s)
Introduced a new official logo for CSS, replacing the outdated CSS3 shield logo. The updated logo, designed by Javi Aguilar in collaboration with the CSS-Next Community Group, represents CSS as a whole rather than a specific version. It aligns visually with other web language logos like JS, TS, and WA, featuring modern design elements and the iconic "rebeccapurple" color.
Icon Details

Icon ID
Icon

css-light

css-dark

Notes

There's also a light version out there, solid white background color, but I think the primary color will be better in auto mode.
https://github.com/CSS-Next/logo.css

Checklist

[x] Added icon(s) to the appropriate directory
[x] Verified the icon(s) display correctly
[x] Updated documentation with the new icon(s)
[x] If the icon has light and dark, verified the auto switch works correctly
[x] The Svg does not contain any sort of strokes

I would love to, but that the logo has one corner with no radius... I don't know how it should be implemented :/
I don't think it should be a problem to have an icon that doesn't respect this.

I understand your concern, but I believe it would be more authentic to leave one side unrounded. This way, at least one icon can visually convey its connection to the style, even if it doesn’t strictly follow the radius rule. That said, I’ve adjusted it to align with your feedback nonetheless.

I might have misunderstood the purpose of the auto mode, so I left it in just in case. However, it can be removed if you think it’s unnecessary — what do you think?

I might have misunderstood the purpose of the auto mode, so I left it in just in case. However, it can be removed if you think it’s unnecessary — what do you think?

I think making it rebecca purple would be better :) then it will be all good I guess

@Jeesson which one do you prefer ?
1:

2:

The first option is definitely better — it adds uniqueness to the icon, just like with wasm. There’s nothing wrong with that, right?

The first option is definitely better — it adds uniqueness to the icon, just like with wasm. There’s nothing wrong with that, right?

I completly agree with you :)


C++ WPILib Deploy sometimes does not show up

When in the Java perspective, the deploy command does not show up for C++. The reverse is not true: Java programs do not have this problem in the C++ perspective.

Fairly certain this was done on purpose. I think because the C++ plugin crashes if that menu is (loaded? run?) in the Java perspective and prevents the C++ Deploy menu items from showing up in either perspective until you restart Eclipse. I recall not being able to figure out how to fix that actual problem, so the workaround was to not show them outside the C++ perspective.

Found a different fix for this that allows it to show up in the Java perspective


docs: Update content under the heading "Claiming an issue" in the contributing guidelines.

Fixes Issue #20865
Testing plan:
Updated content under "Claiming an issue". The second line in the first paragraph now reads "Before making your first pull request, you can only claim issues with the good first issue or help wanted labels."

@raghupalash how does this look?

Let's change it to the following, which is more accurate:

Until your first pull request is merged, you can only claim issues with the...

Let's change it to the following, which is more accurate:

Until your first pull request is merged, you can only claim issues with the...

My first pull request was only merged yesterday, yet I was able to claim issues without those 2 labels before that... Am I missing something here?

Yeah I saw that Raghav claimed the issue without those labels when he had no commits merged, that's why I thought that one would need just a PR to claim those issues.

@zulipbot remove "area: settings (user)"

I guess this issue has been resolved with https://github.com/zulip/zulip/commit/30fec0c7012ae42495e966c76512aa44c49d5963, so I am closing this pull request.


Update module docstring

Coverage remained the same at 97.426% when pulling b87913aa5a1f4f0f6ec1adf78c9ba7a2c437e56c on arcondello:vartype_docupdate into d20653ea7ee01a1a405f4c7ff5ba2ea9ad2c69d2 on dwavesystems:1.0.0.


Reformatted code quality in example is quite poor

From the example:
With the above configuration, this code:

def f(x):
    '''
    Something about `f`. And an example:

    .. code-block:: python

        foo, bar, quux = this_is_a_long_line(lion, hippo, lemur, bear)
    '''
    pass
... will be reformatted (assuming the rest of the options are set to their defaults) as:

def f(x):
    """
    Something about `f`. And an example:

    .. code-block:: python

        (
            foo,
            bar,
            quux,
        ) = this_is_a_long_line(
            lion,
            hippo,
            lemur,
            bear,
        )
    """
    pass

I fail to see a circumstance where the second form is more pleasant and readable than the first. Is it possible to prevent such reorganisation configuration-wise?

Hey -- it's hard to really take action on this issue, but the purpose of that example is to demonstrate the line-length rules for formatting code within docstrings, rather than provide any commentary on the style of the reformatted code. The style, though, is consistent with Black, and so within the formatter's goals.

(The short answer is no, apart from increasing the line length to prevent Ruff from wrapping lines in those cases.)


New feature request: Nested menu entries

I am finding out if there is any way to make sidebar items nested, to make it tidier with a huge number of sidebar items.
It seems like currently no plugin have ever implemented this feature, but I found a discussion, and a PR to the Home Assistant Core repository: https://github.com/home-assistant/frontend/pull/17943. But it seems like the HA is not ready to merge it (for nearly 1 year).
So I think, is there any possibility to implement this feature in this plugin?

Hi @Eyre-S,
Please, check my comment here.
I'll close this one and if you need to discuss something else, please doing it in the discussions that are already open.
Regrads


[Deploy] Notion

Service
This recipe is for Notion, a great webapp to collaborate on wikis, todos, docs.
Link to your repository
https://gitlab.com/lonestone/open-source/franz-notion

Duplication of https://github.com/meetfranz/plugins/issues/99


Error encountered using client.Insert() - Organization ID: id value of incorrect type

Hi Michael,
Thank you for making this amazing library available.  I've installed the nuget package and have had great success with the GetSession(), Count() and Query() methods against my Salesforce sandbox.
I've run into an error though, when I try and insert a new record. Salesforce is complaining about the Organization ID being of the wrong type, although I am inserting an Account record which doesn't seem to have an Organization Id in it.
Could you provide some pointers on how to fix this error?
Here's some screenshots of what I'm seeing and the code I'm using...
Error message

Code encountering the error

Definition of the Account Dto

The following code using the Microsoft types generated from the WSDL works

Kind regards,
Craig.

Thank you for update. I will check in to this ASAP and let you know what I find.

Thanks.

On 24 Mar 2015, at 5:29 am, Michael Shattuck<EMAIL_ADDRESS>wrote:
Thank you for update. I will check in to this ASAP and let you know what I find.
—
Reply to this email directly or view it on GitHub https://github.com/clamidity/SalesforceMagic/issues/16#issuecomment-85134664.

@donners77 I don't believe that the source of this error is this library. I think its coming from salesforce because the data you send is not 100% correctly correlated to what is already in salesforce. See if this thread helps - https://success.salesforce.com/answers?id=90630000000glwVAAQ

Closing for now


Fix RN 0.47 breaking change

Remove Override to enable compiling with RN 0.47. Change is backwards compatible

Thanks! 👍


Move code for closing sidebar to a function

In assets/js/index.js we have repeated code that closes the sidebar. We need to put it in one function and call it each time. The code is being used for 3 or 4 events, so it should be put in a separate function and then the function should be called from these events

I'm familiar with the code, I can take care of this!

Great @JLambertazzo I'll assign you

Hi, I would like to attempt this.


Roll out to all repositories

Currently, only PostgreSQL uses this repo. We should however roll it out to all vs dialects.

I've created individual tickets in each repository. Closing this one.


Update Settings “general”

Automatically generated by Netlify CMS

👷 Deploy Preview for quiet-chimera-c1d66f processing.

Name
Link

🔨 Latest commit
f9b2d31cc57d7058cc12737f59472b1b866d4f76

🔍 Latest deploy log
https://app.netlify.com/sites/quiet-chimera-c1d66f/deploys/64e28e97e36e3000084d7642


Feature/154-log in register token

In this PR the changes for creating the log in as an authenticated user have been implement it. In order to be able to check its performance you have to following steps:

Create a new user using the register (you have to use a real email for it) and activate the account by following the link from the mail and pressing the post button. After this the account will be active.
Go to the admin screen of django and check that the user has a role assign (not family becuase the screens are not implemented yet)
Once you checked it has a role assign then try to log in and the corresponding screen should appear.
Keep in mind that right now after doing the register for family or volunteer you will be redirect to their register form pages (which are not yet done). When this part it is functional then the part of checking the role from the admin screen would not be neccesary

Do we have to register in the register screen or on the api?

Using the register form
El 27 mar 2024 17:54, samrodman @.***> escribió:
Do we have to register in the register screen or on the api?
—
Reply to this email directly, view it on GitHubhttps://github.com/ISPP-G5/NexONG_Frontend/pull/159#issuecomment-2023305558, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AX2LS7H3VISA4VOOUY2FON3Y2LTS5AVCNFSM6AAAAABFLHVCFCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRTGMYDKNJVHA.
You are receiving this because you were assigned.Message ID: @.***>

At first I have troubles trying to register bt after fixing some self problems I manage to do the register and log in totally fine. I get the email and I manage to activate the account and can be seen clearly on the /api/user in the is_enabled attribute. Just to point out, I created a volunteer profile and in the api appears FAMILY as a role and null in volunteers. Guess that's a backend problem. When log in, the volunteers profile appears. Great job!

I noticed that but I think it is related with somenthing with the backend. I will have a look and see why it could be. Thanks!


Consider reducing delay for indexing of libraries

This is especially important for my library (https://github.com/RobertCraigie/prisma-client-py) as it is auto-generated it will be modified a lot.
Currently whenever a change is made to the schema and the package is re-generated, any new type errors are not reported and new autocomplete suggestions are not shown either for 10 minutes or until the language server is restarted. This makes it difficult to rapidly prototype schema changes.
I tried going through the Pylance settings and didn't find anything that worked for me. I could've missed the setting but even if there is a setting I can change to get the desired behaviour ideally this would be possible by default as it can be confusing for users as they don't know that they will have to either wait 10 minutes or restart the language server for their schema changes to propagate.
I understand that delaying the indexing of libraries is for performance reasons. Is there any way indexing could be optimised for my use case?

Thanks for the report @RobertCraigie, One way you could trigger is to the Language  Server restart from the command palette with Python: Restart Language Server. That would be faster than the restarting the process. Please reopen the issue if that approach is not satisfactory. Thanks

Hi @judej, sorry I wasn't clear enough in the original comment. I was making use of the command palette Python: Restart Language Server which works well but it can still be confusing if a user forgets that they have to run it or doesn't know that they have to run it in the first place.
I would like to provide the best possible experience for users of my library and having the editor automatically recheck their code and update suggestions as soon as they make any schema changes without them having to think about it would be an amazing QOL feature. Ideally this would be possible with default settings but I understand that this brings performance concerns.

@RobertCraigie, are you saying that users of your library will experience frequent regeneration of code? Or is this just an issue for you as you develop the library? I had previously assumed that it was the latter, but based on your most recent comment, I'm wondering if I misunderstood. If users of your library will see frequent code regeneration, can you explain more about the intended workflow for your library?

@erictraut Yes users will experience frequent code regeneration in certain workflows.

can you explain more about the intended workflow for your library?

Of course. The library deviates from other ORMs as the data models are defined outside of a python file, instead they are defined in a Prisma Schema file, the way this works isn't important but it does mean that the library code has to be regenerated every time a change is made to the schema.
So when users are prototyping features in their app they'll likely be making lots of changes to their schema which results in a lot of code regeneration. However, any workflow that does not require changes to the schema will not result in code regeneration.
It also should be noted that code generation is a hard requirement for the library as it is fundamental to its ability to provide type safe queries and is an underlying requirement by Prisma as well.
Sample Prisma Schema in case that helps clear things up:
datasource db {
  url      = env("DATABASE_URL")
  provider = "postgresql"
}

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

model User {
  id         Int      @id @default(autoincrement())
  created_at DateTime @default(now())
  email      String   @unique
  name       String?
  role       Role     @default(USER)
}

enum Role {
  USER
  ADMIN
}

Thanks for the details. Am I correct in assuming that the generated code files are located within the user's project file, as opposed to in the installed library location (in site-packages)? If these generated files are project-local code files, then regenerating them should be no different than any other edit, and "library indexing" concerns shouldn't apply.

Yeah that is a good point. I was under the impression that the vast majority (if not all) modern python projects use some form of environment isolation whether that's venv, poetry, virtualenv etc. Although I do not know what the actual usage stats are for these environment managers.
Generating to a local directory also comes with the disadvantage of having to deal with Python's potentially confusing import system for relative modules. For example it would then be difficult to run scripts in other directories:
prisma/
├─ <generated library code>
foo/
├─ script.py
schema.prisma

# script.py
from prisma import Prisma

Running the script with python foo/script.py will result in an ImportError as the local package cannot be resolved properly. As far as I'm aware the fix for this is sys.path manipulation which the user would then need to include in every script they want to run.
For what it's worth it is very clear to the user where the code is being generated to:
$ prisma generate
Prisma schema loaded from schema.prisma

✔ Generated Prisma Client Python to ./.venv/lib/python3.9/site-packages/prisma in 265ms

It may be clear, but if I found that a library was dynamically generating new code files into my Python environment (virtual or otherwise), I'd be pretty surprised and a bit miffed.

I see, I think most people come into the library with the knowledge that it does this but I acknowledge that it might be surprising.
I do think I want to keep the current behaviour due to the difficulties with importing local modules and I haven't received complaints from users that the default behaviour is not what they want.
If you do want to use local modules then it's a one line change:
generator client {
  provider = "prisma-client-py"
  output = "prisma"
}

For users of your library who want to use Pylance, I would recommend the approach of generating local modules. Perhaps you could document that as an alternate workflow?

For users of your library who want to use Pylance, I would recommend the approach of generating local modules. Perhaps you could document that as an alternate workflow?

Yes that is a good suggestion, I'll document that as an alternative workflow.
However I still want to be able to provide a good experience for users who want to generate to site-packages, would it be possible to add an option to disable or reduce the 10 minute delay?

We generally don't add new configuration knobs unless/until we have signal that there is a broad need. This use case still strikes me as atypical and rather esoteric. We could reconsider in the future if we get sufficient signal from our user base.

Yeah that is a good point. I was under the impression that the vast majority (if not all) modern python projects use some form of environment isolation whether that's venv, poetry, virtualenv etc. Although I do not know what the actual usage stats are for these environment managers.
Generating to a local directory also comes with the disadvantage of having to deal with Python's potentially confusing import system for relative modules. For example it would then be difficult to run scripts in other directories:
prisma/
├─ <generated library code>
foo/
├─ script.py
schema.prisma

# script.py
from prisma import Prisma

Running the script with python foo/script.py will result in an ImportError as the local package cannot be resolved properly. As far as I'm aware the fix for this is sys.path manipulation which the user would then need to include in every script they want to run.
For what it's worth it is very clear to the user where the code is being generated to:
$ prisma generate
Prisma schema loaded from schema.prisma

✔ Generated Prisma Client Python to ./.venv/lib/python3.9/site-packages/prisma in 265ms

This is also the behavior from the Javascript/Typescript implementation of Prisma, so it'd make sense for the implementations to be functionally identical. I came across this refresh issue myself and had no idea why I could import everything properly in runtime but vscode presented errors. I had no idea to restart the language server. I think having this setting be user-adjustable, wouldn't hurt.

+1 on the above behavior being expected from a module side. If it did it otherwise, it would be pretty unexpected.


Ability to make all windows go full screen via a hotkey?

weord idea. can be done via applescript anyway

I'm not talking about Apple native full screen, I'm talking yabai -m window --toggle zoom-fullscreen for all applications. I need this when I'm using my 13' screen where tiling squishes everything.

You can use the following command to toggle zoom-fullscreen for all windows on the currently active space: yabai -m query --windows --space | jq '.[].id' | xargs -I{} yabai -m window {} --toggle zoom-fullscreen
If you always want windows to be fullscreen you can just use the stack layout instead of bsp though.

thank you @koekeishiya, I was looking for this.


Failure to render WebP images inside a page

PhantomJS version: 2.1..1
I was just trying to render a page where there are Webp images. for example: https://developers.google.com/speed/webp/gallery1
using Mac
binary

when running this code:
var webPage = require('webpage');
var page = webPage.create();

page.viewportSize = { width: 1920, height: 1080 };
page.open("https://developers.google.com/speed/webp/gallery1", function start(status) {
  page.render('test.jpeg', {format: 'jpeg', quality: '100'});
  phantom.exit();
});

i got this image:

any idea if this going to be fixed?

Support for WebP images will be in 2.5 release

Could you please try again with 2.5 binary? Thank!


fix: correct scrollable element check condition

Changed the logical operator from && to || because an element cannot be both document.documentElement and document.body at the same time.
✅ Pull Request Checklist:

[ ] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

Was anything breaking with this? It'd be good to be able to verify the behavior update. This is a line from 4 years ago, so curious how you found it.

No no, you misunderstand. I haven't seen it adversely affect anything. I'm curious how you noticed it.

I’ve always been a fan of the React Spectrum library, so I like to dig into its source code whenever I have some free time. Recently, while debugging, I noticed that a specific if condition (on line 113) wasn’t being triggered, which got me curious. I started looking into it more, but now that I think about it, I might’ve messed something up in the process. I’m really sorry about that.


Trying [tsml-react] - not working

Greetings -
I am wanting to take advantage of this feature and because i am already using the plugin, I tried simply typing in [tsml-react] on a page as suggested.
Are there other steps I need to take to utilize this?  Thank you!
Jodie/Northern Michigan Central Office
nmcentraloffice.org

Pinging @tech2serve for a WordPress question - should we open this up as a ticket in the TSML repository since it concerns shortcodes?

First of all, @jackieoh1, I apologize for not having caught this issue earlier. I need to do a better job of seeing new issues in some of our other repositories.
Please tell me more about you experienced, including what you did see, how you added the short code, and the theme you're using. I will try to duplicate on my site.
Thanks!
@FlipperPA I will try to transfer the issue to TSML.