Install specific Symfony version

How can I install Symfony 4.0?
If I specific the 4.0 version it installs Symfony 4.1.1 ....

Any help please?

If you really want to stick to one minor version (why would you do so?), you need to change the version requirements in the composer.json file (e.g. using ~4.0.0 instead of ~4.0).
I'm closing here since we use github for bug fixes only. Cheers.


Update sql-database-metrics-diag-logging.md

Submitted a minor change to the sample code for clarity

#sign-off

@danimir : Thanks for your contribution to the Azure documentation! The author, @veljko-msft, has been notified to review your proposed change.

#sign-off


only test test pipelineX without insert

Proposed changes
this pr https://github.com/apache/doris/pull/24910 in pipelineX

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall

run buildall

run buildall

now test partition sort fix

run buildall

run p0

run buildall


Mini Smart Plug

Device found as mini smart plug - seems to work ok - I am using Tuya Local as well
but it does this
https://user-images.githubusercontent.com/11158209/126865666-ea564d72-cb9a-4501-9ff2-821357bb6be1.mp4
You switch it on, after a second or 2 the switch changes to off - plug is still on

I have the same issue with all my switches.

Check it out: https://youtu.be/P-vOwHB83JE?t=585
This fix worked for me :)

Check it out: https://youtu.be/P-vOwHB83JE?t=585
This fix worked for me :)

This fixed mine as well. Thank you! :)


Wrong path join

Hello guys, I think you should not use '' in path.join.
<script src="static\manager.bundle.js"></script>

Firefox does not like this
GET
http://localhost:9001/static%5Cmanager.bundle.js [HTTP/1.1 404 Not Found 1ms]

I think I just found the issue. Just to make sure, are you using Windows?

@avin can you try v1.29.2
It should work now

@mnmtanish, yes i'm windows user and 1.29.2 works fine! Thank you very much for fast reply!

I'm using Mac and I have the same issue. I'm also using the latest version of storybook.

I am also a Mac use and I am having this same problem. I am using version 3.1.7. @mnmtanish Any suggestions?


Objects and functions should be documented

In the correct Pythonic format

When you say correct Pythonic format, do you mean something like this?
def some_function(arg1, arg2, optional_arg='Some String'):
    '''Runs some stuff on some things and then spits out the end result
    depending on the stuff you put into it.
    Args:
        arg1 (list): List of things (str) that you want to run the
        function on.

        arg2 (integer): The number of times you want to perform this
        function.

        optional_arg (string): A flag to change the way the function does
        stuff.

    Returns:
        result_list (list): A list results generated by the function.
    '''

That's it yes!
On Mon, 1 Feb 2021, 21:20 Chris Cummings<EMAIL_ADDRESS>wrote:

When you say correct Pythonic format, do you mean something like this?
def some_function(arg1, arg2, optional_arg='Some String'):
'''Runs some stuff on some things and then spits out the end result    depending on the stuff you put into it.     Args:        arg1 (list): List of things (str) that you want to run the        function on.                arg2 (integer): The number of times you want to perform this        function.        optional_arg (string): A flag to change the way the function does        stuff.    Returns:        result_list (list): A list results generated by the function.    '''
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mellowdrifter/python-bgpstuff.net/issues/3#issuecomment-771299995,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABQFHWA6EMF6VVZMIFTPMD3S45OQNANCNFSM4W5X7NVA
.

Cool, I'm gonna poke at this!

Added a first stab at things


fix(sharing-ng): Fix setPassword call for spaceroot

Requests to /raph/v1beta1/drives/{driveid}/root/permissions/{permissionid}setPassword were rooted to the wrong method.

We don't need a changelog?

Hm, I guess it's ok here. This has not been part of a release yet.


Differentiate UDP and TCP Protocols in Services

Saving protocol information in the lb(x)_key in bpf, as well as
adding protocol information to service maps creation in the
lbmap package ensures that translation, receiving, and forwarding
will always take the protocol into proper account.
Refactor cilium to always assume a protocol with a service.
Refactor tests to account for service protocols.
Update Documentation for kubeproxy-free nodeport example
Since the output of cilium service list has changed
the documentation should reflect the change.
Fixes: #9207
Signed-off-by: Nate Sweet<EMAIL_ADDRESS>Please ensure your pull request adheres to the following guidelines:
cilium: eBPF code and daemon take L4 protocol into account for services, allowing for host level port overlap.

@nathanjsweet Thanks for working on this. To make reviewing easier, could you give some hints how this approach differ from #12628?

@brb sorry, I should have opened this as a draft.  Here is the approach I'm going to take (but haven't yet):

On start up the service cache will get a snapshot of the state of the conn track table.
The service cache will consistently add a duplicate lb_map entry into the service maps with protocol "0", while it is in "legacy mode".
Periodically the service cache will check the conn track table against its initial snapshot. Once the initial snapshot shows that all initial connections on start up are gone, then the service cache will switch out of "legacy mode"
Out of legacy mode the service cache will evict all duplicate lb_map entries where the protocol is "0" and no longer add such duplicate entries.

The service cache will consistently add a duplicate lb_map entry into the service maps with protocol "0", while it is in "legacy mode".

@nathanjsweet That's a neat idea. I think that the scanning of the CT tables is not needed, as both placeholder entries will have the same rev_nat_id, so it won't be possible to distinguish between them from a CT entry. Instead, I'd suggest to introduce a flag --support-no-proto-svc-foobar which would default to true (for existing deployments), and in Helm it'd be set to false (for new deployments). The flag would control whether "0" entries should be created during the initial service sync (happens before the datapath reload). When set to false, it would also try to remove "0" entries. This would also make downgrades possible.

test-missed-k8s

@nathanjsweet Do you plan still to work on it?

@nathanjsweet Do you plan still to work on it?


cloudprovider: add instance id to NodeSpec

Sometimes for external applications it is important to identify the cloud instance of the nodes. Until this patch there was no contract that the node name returned by List was also the unique identifier of the cloud instance. This new API ensures that an external application can reliably retrieve the relevant instance id of the nodes.

@bgrant0607 for API thoughts.
This seems reasonable to me, but I'd prefer to land it with implementations for AWS and GCE (if not OpenStack and Vagrant)

Re. API:

This is the Node API. "Instance" is cloud jargon. As @brendandburns pointed out, we run on bare metal, too, so I don't want to couple the API too closely to cloud providers. I'd be happier with externalID, which would better match the description.

Status information should be reconstructable. We can rediscover container IDs from Docker. Do we expect all externalIDs to be similarly discoverable? It seems like that might not be true, in general, esp. for bare metal. Given that the external ID will be provided when the node is created and shouldn't change so long as the node exists, I think it makes more sense to be in the NodeSpec.

@bgrant0607 I implemented all the cloud providers but I guess I'll need other people's help to test them. I could verify just the ovirt one.

I'm punting at Brendan - I am out the second half of this week and crazy slammed the first half.

I'll test on vagrant after #4468 merges.

@bgrant0607 I'd prefer to keep ExternalID in Status vs Spec because I assume that a node can change ExternalID (e.g. vm cloned / decommissioned, etc.).

@simon3z A node shouldn't be able to change ExternalID. That would be a new node object. That said, Spec is updatable. Status must be 100% automatically reconstructable from other sources, and shouldn't be provided by the cluster administrator. Does ExternalID meet that requirement?

@bgrant0607 I moved it to Spec

API LGTM. Thanks.
What happens for providers for which this is not implemented?
FYI, maintainers are here:
https://github.com/GoogleCloudPlatform/kubernetes/blob/master/MAINTAINERS.md
https://github.com/GoogleCloudPlatform/kubernetes/tree/master/docs/getting-started-guides
@derekwaynecarr for Vagrant
@doublerr for Rackspace
@justinsb for AWS
@jeffmendoza for Azure

@bgrant0607 if it's not implemented the error message (if any) is logged and the externalId won't be reported. Returning an empty string (and nil error) would be OK for providers that don't intend to expose the id.

So it looks like we're heading for a pattern where we add lots of methods to the cloud provider, where each method extracts one piece of information.  My inclination would have been a pattern where we have a "GetInfo" call, which just gathers all the information.  This seems like it would be more efficient (particularly as we start to collect more and more information) and simpler.
The AWS code looks fine, though I haven't tested it.

I think I generally agree with @justinsb on the GetInfo call, but the whole cloud provider stuff needs a refactor anyway, so I'm not going to block the PR on that.  Merging.

if it's not implemented the error message (if any) is logged and the externalId won't be reported.
Returning an empty string (and nil error) would be OK for providers that don't intend to expose the id.

Sounds good.

@brendandburns if you agree with the GetInfo call refactoring I can start to work on that tomorrow (my final goal is to add another information and it seems that having separate class is not sustainable anymore). Thanks!

@brendandburns can you check my last question? do you have an answer for that?


Update docs with operator manifests extraction

No release notes added. Docs changes to feature already documented in release notes


EC/DSA nonce generation fixes for 3.1 and 3.0 branches

This is backport of #24265 to 3.1 and 3.0 branches.

@nhorman ping for second review

This pull request is ready to merge

@nhorman @paulidale please reconfirm - there was discrepancy in the prototypes of ossl_bn_is_word_fixed_top(). IMO no need to restart the timer.

Merged to the 3.1 and 3.0 branches. Thank you for the reviews.


How to convert BBBC010 to zarr format?

consolidate_data.py: This code does not work.
Can you provide more details on dataset preparation?

hello，did you solved this problem？

the convert BBBC010 to zarr format problem

Hi Arya, can you please provide more information on the error you encountered?


Handle unknown accounts and split transfers

This PR addresses two issues:

#94
#95

Split Transfers
Issue #95 is fairly straightforward. We just need to detect and handle transfers in split transactions. This means that when a split transaction category is in brackets (e.g. [Savings]), this value should be assigned to Split.to_account rather than Split.category. See the associated issue for more detail.
Unknown Account Types
Issue #94 is a bit more tricky. I think this situation relates to the !Option:AutoSwitch section of the QIF file that isn't well defined. The associated issue has more detail, but in summary: sometimes accounts have types that aren't defined in the AccountType enum. To handle this situation, a fallback mechanism is implemented that assigns these accounts an 'unknown' type, ensuring the parser remains functional when this situation is encountered. It doesn't seem ideal, and perhaps we'll find a better solution in the future. But this addresses pydantic failures when reading files with these unknown account types. It is left to the user to detect and fix the unknown types on their end if they desire.

@isaacharrisholt I'm not sure what happened with the tests on this one. Everything passes in my 3.12 environment, and I'm pretty sure the failures in 3.11 aren't related to the changes in this PR. Do you have any more insight?

@isaacharrisholt Apologies, those failures were on me. I think I got it sorted. We're still getting the virtualenv failure in the windows 3.9 test discussed in a comment on a previous PR. But otherwise I think we're good to go now.

No worries, thanks for accepting it!


sizeColumnsToFit not working if we call that api from column moved event

i call the api from onColumnMoved event, but nothing will happen.(still i got horizontal scrollbar)
iam calling api like this, in grid options
onColumnMoved: function (event) {
event.api.sizeColumnsToFit();
}
is it right or wrong?

i hv tried $scope.gridOptions.api.sizeColumnsToFit(); this also not working in that place of event call

sizeColumnsToFit does not work when forPrint=true

i didnt enabled it.so, default it is set to false i think.

sizeColumnsToFit does not work when forPrint=true -> it is not supported. forPrint doesn't use scrollbars so it doesn't make sense.
$scope.gridOptions.api.sizeColumnsToFit(); should work
please provide a plunker.
ps closing - this is not a problem with ag-grid, issues are for items that need fixing in ag-grid


Added support for SOCKS4 and SOCKS4a proxy servers

This looks fantastic! Thanks for the massive contribution!

Released!
https://www.nuget.org/packages/FluentFTP/37.1.0


The relative link rewrite on github links is lacking.

On github, the relative link requires a blob/master path part.
Example: https://pub.dartlang.org/packages/leveldb/versions/5.0.0 look for the example/main.dart reference.

More details in https://github.com/dart-lang/pub-dartlang-dart/issues/850


PriorityFreeze in Singularity deploy/request

Hey
We're currently looking into adding priorotyFreeze into our pipeline, but struggle to find the proper key and wrapping for our request.
Can you please share the knowledge -- how to add the priority level to the deployment yaml?
Thanks.

priority is a request level setting. taskPriorityLevel field on the request json (not deploy json). Then in Singulairty UI you can freeze launches of all tasks below priority level X if you need to. It also influences scheduling order with higher priorities coming first


Extension Lifecycle (spawn and kill processes, caching of items, optimized loading)

Description of the new feature / enhancement
We need to conduct a deep dive into how we manage extensions over the course of their lifetime.
Extension processes should not remain around for the entire lifecycle of the palette itself. As part of this investigation, we should consider:

How do we properly spawn and kill extensions?
How do we ensure speedy UI/UX if extension processes are not constantly lying around
How can we potentially cache top level commands from extensions so we don't have to always have them around.

Scenario when this would be used?
This will be abstracted away from extension developers, but will become core to the command palette
Supporting information
No response

Here's a weird wacky thing today:
Every time we come back to the main page, we call IExtension.GetProvider. And in the sample, we always instantiate a new one on the call to that. So every extension we have? Instantiates a new object each time we get to the main page.
Twofold fixes:

Best practice: Extensions should probably have a single static ICommandProvider instance that they return out.
We probably shouldn't call that every time we come back? Like, we can call TopLevelCommands, but GetProvider? We should already have that!


Update circe-core, circe-generic, ... to 0.14.4

Updates

io.circe:circe-core
io.circe:circe-generic
io.circe:circe-testing

from 0.14.1 to 0.14.4.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.circe" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.circe" }
}]

labels: library-update, early-semver-minor, semver-spec-patch, version-scheme:early-semver, commit-count:1

Superseded by #307.


Redesign offer slider

Fixes #5
Describe the changes you've made
A clear and concise description of what you have done to successfully close your assigned issue. Any new files? or anything you feel to let us know!
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
A clear and concise description of it.
Additional context (OPTIONAL)
Add any other context or screenshots about the feature request here.
Test plan (OPTIONAL)
A good test plan should give instructions that someone else can easily follow.
How someone can test your code?
Checklist

[x] I have mentioned related issue number in PR description.
[x] I have added screenshots and related demo links of my changes..
[x] The title of my pull request is a short description of the requested changes.
[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] Open Source Program names(OPTIONAL: If you participated in any open-source program then please mention the program name here)

Share website link so I can review your changes.

Share website link so I can review your changes.

https://tjanhvi.github.io/Apni-Dukaan/


sladi4kodivane

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[x] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[x] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[x] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[x] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

@Adi2007 Thanks for reaching out, but could you please elaborate on the issue you're facing along with the URL of the MS Doc that you were following, if any?

@Adi2007 since this issue is not actionable I am closing it out. Please feel free to make a new issue describing your exact problem with a specific article and giving clear suggestions for improvements.


Add PureScript to list of programming languages

see https://twitter.com/james_santucci/status/1374711136910770176

Implemented.


gist update fails on Mac OS X El Capitan 10.11.6

Hi! Please, allow me to post a link to Sublime Text forum to avoid duplicated information!
https://forum.sublimetext.com/t/sublime-github-on-mac-os-x-el-capitan-10-11-6/28494
Thanks for any insight! Cheers!

It works today. I'm not able to figure out why. Sorry for the noise! Thanks for your work!


Boolean tests (like $a -eq 1) are not recognized

It now has a rudimentary level of support, it no longer generates an exception.

Now supported


Container component isn't available through reapp-kit

I'm trying to render a container component by importing it through the reapp-kit but when I try to render there is a Uncaught TypeError: Cannot read property 'toUpperCase' of undefined. I looked through the reapp-ui code and it lists Container as an available component so not too sure why it's not working with reapp-kit. Is there any way to use the Container component and the grid system with reapp?
my code:
import {
  React,
  View,
  Button,
  Container
} from 'reapp-kit';

export default class extends React.Component {
  render() {
    return (
      <View
        {...this.props}
        title="Container">

        <Container>
          <Button>some button</Button>
        </Container>
      </View>
    );
  }
}

Sorry, the docs are out of date. I'm going to work on updating them soon. It's been moved into Grid. Grid.Container

On Apr 18, 2015, at 2:23 PM, Ken Miyamoto<EMAIL_ADDRESS>wrote:
I'm trying to render a container component by importing it through the reapp-kit but when I try to render there is a Uncaught TypeError: Cannot read property 'toUpperCase' of undefined. I looked through the reapp-ui code and it lists Container as an available component so not too sure why it's not working with reapp-kit. Is there any way to use the Container component and the grid system with reapp?
my code:
import {
React,
View,
Button,
Container
} from 'reapp-kit';
export default class extends React.Component {
render() {
return (
<View
{...this.props}
title="Container">
    <Container>
      <Button>some button</Button>
    </Container>
  </View>
);

}
}
—
Reply to this email directly or view it on GitHub.

Ok thanks! The Grid.Container works now, I have two buttons in a container but they aren't spread out evenly. I'm excited for the updated docs but in the meantime I'll just use custom styles with flexbox on some divs to spread elements out the way I want. Let me know if I can help you out with the docs in any way. We were using React-Native but got interested in Reapp since it works for android too.

Added this to the latest reapp-ui, if you reinstall reapp-kit just plain Container should work as well.


Image segmentation training script

Hello,
Will you be releasing the training scripts for efficientvit training on cityscapes dataset?

Thanks for your interest in our work. Releasing the training code and scripts on segmentation is on the schedule. Please stay tuned.
Best regards,
Han

Hi @han-cai , do you have any update on the schedule when image segmentation training script can be released?  Thanks very much!


No longer override projectDirs.

No longer override projectDirs now that the gradle subproject names match the directory names.

Codecov Report

Merging #311 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #311   +/-   ##
=========================================
  Coverage     90.55%   90.55%
  Complexity      495      495
=========================================
  Files            80       80
  Lines          1959     1959
  Branches        143      143
=========================================
  Hits           1774     1774
  Misses          149      149
  Partials         36       36

Continue to review full report at Codecov.

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

/cc @bogdandrutu

I don't have write access. May I ask you to merge this PL?

@ubschmidt2  Sorry for the delay.  I'll merge it now.

Thanks!


Parameter '-SkipImportSession' doesn't exist

This page lists '-SkipImportSession' as a parameter from 2.0.4-Preview2, but this parameter isn't available in 2.0.4 (release version). Looks like the parameter has been removed from one of the previews...

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

ID: 13d88f18-3cc8-5f18-8d61-ff7f5fa4e314
Version Independent ID: 60f9a029-69f3-e65c-6816-fbd414790ce3
Content: Connect-ExchangeOnline (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Connect-ExchangeOnline.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@hairyken, confirmed. The parameter was in Preview2 and Preview6, but not in Preview9 and not in the public release of 2.0.4. I removed it from the topic.
Thanks for the feedback.
Closing


T07.06 Remove guests - Illegal cursor error

java.lang.IllegalStateException: Couldn't read row 0, col -1 from CursorWindow.  Make sure the Cursor is initialized correctly before accessing data from it.

@dafm96  I know its a little late but would you submit some sample code so I can see the error

Closing.
Not enough information provided.


Update dependencies and workflows

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

Project coverage is 100.00%. Comparing base (2ba96fc) to head (ecd7171).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #101   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines           39        39
  Branches         4         4
=========================================
  Hits            39        39

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


item.links() shouldn't be an dictionary instead of method?

Hi, I am new to sat-search and quite new to python
I was following the definitions in http://sat-utils.github.io/sat-api/?python#tocslinks
Based on that, on the bellow script, shouldn't "items.links" be accessed as dictionary containing "href, rel, type and title"? If I try access based on ['href'] I receive

TypeError: 'method' object is not subscriptable

The only way i could access was using items.links()
def sat_search(wlon,nlat,elon,slat,startdate,enddate,cloud,limit, collection):
	search = Search(bbox=[wlon, slat, elon, nlat],
                    time ='{}/{}'.format(startdate, enddate),
				    query={'eo:cloud_cover': {'lt': cloud},
						   'collection': { 'eq': collection}})

	items = search.items( limit = limit )
	print('%s items found' % len(items))
	print(items.summary( ['date', 'id', 'eo:cloud_cover', 'landsat:product_id']) )
	# print( items.calendar() )
	# items.save('test.json')

	scenes = {}
	for item in items:
		identifier = item.properties['landsat:product_id']
		scenes[identifier] = {}
		scenes[identifier]['sceneid'] = identifier
		scenes[identifier]['scene_id'] = item.id
		scenes[identifier]['cloud'] = int(item.properties['eo:cloud_cover'])
		scenes[identifier]['date'] = item.properties['datetime'][:10]
		scenes[identifier]['wlon'] = float(item.bbox[0])
		scenes[identifier]['elon'] = float(item.bbox[2])
		scenes[identifier]['slat'] = float(item.bbox[1])
		scenes[identifier]['nlat'] = float(item.bbox[3])
		scenes[identifier]['path'] = int(item.properties['eo:column'])
		scenes[identifier]['row'] = int(item.properties['eo:row'])
		scenes[identifier]['resolution'] = item.properties['eo:bands'][3]['gsd']
		scenes[identifier]['icon'] = item.assets['thumbnail']['href']
		scenes[identifier]['link'] = item.links()[0]
	return scenes

collection='landsat-8-l1'
wlon = -45.97
elon = -45.80
slat = -12.95
nlat = -12.89

startdate = '2018-01-01'
enddate = '2018-12-31'
cloud = 100#20
limit = 299
b = sat_search(wlon,nlat,elon,slat,startdate,enddate,cloud,limit, collection)

Other observation, the search I performed also returned scenes that shouldn't overlap with my study area (my area is 220|069 and in search I also got from 074|069 a pacific ocean scene). I noticed that their bounding box are wrong (-179.11958 to 178.78202). I am using an if statement to eliminate them from my search. But this is a catalogation problem right?
    if ( (item.bbox[0] - item.bbox[2]) > -3 ):

Almost 1 year since this opened!  Closing since it's so stale, but to answer your questions:

item.links is a method that can be used to return all links with a certain rel type, e.g.,  item.links('derived_from')
the issue with the catalog is from the DevSeed sat-api deployment, which is outdated now but this issue can be raised there: https://github.com/sat-utils/sat-api/issues

I would recommend using https://earth-search.aws.element84.com/v0 as a STAC API which has Sentinel-2 (L1C, L2A, and L2A COGs), and Landsat will be added in the next couple weeks.


Define sourceDescription in response

This PR defines a struct for sourceDescription JSON response to support DESCRIBE query execution response defined in https://docs.ksqldb.io/en/latest/developer-guide/ksqldb-rest-api/ksql-endpoint/

Tested out manually by connecting to a local ksqldb instance.

@thmeitz thank you!


CSS

CSS
User Story
As a bootcamp student
I want prework notes to be organized on a webpage
So that I look back and reference it
Acceptance Criteria
GIVEN a study guide website
WHEN I view the study guide
THEN
I see a Dark Blue Header and footer, and four boxes with a shadow

Added CSS to index.html
Added CSS notes


Making sure to open modal automatically for cropping the image being uploaded

While creating a listing, we need to open the modal automatically for cropping it.

Lgtm


Ta graded option

Added an option to include an additional csv with the assignment scores (as input by grader). This option would allow grading easier when a TA or instructor ALSO grades a peer review assignment.

Tested on my machine - behaved as expected both when there are no grades, and some grades


Add mocha and eslint to test for bugs

You can now run npm test to check for bugs, could also use a CI tool to run for pull requests.
As of now the only files that don't work as expected are in src/constants/, I'm not sure why the function is broken into two files but it's really weird IMO.  Nice work!!

Also it is broken up into two files because the way our build process works. It just concats all the files together. It's dirty but it works.

@Rabrennie we should exclude those files then so the tests will pass. Now I understand what was happening but at first I didn't know why they were split.


Update met to 11.1.0 once released and adjust date range for patch

Describe the bug
This is just a reminder that until<EMAIL_ADDRESS>is released, we can't build met@11 (and therefore metplus@5 and global-workflow-env) on macOS. I previously thought this was only the case for the M1 (aarch64) architecture, but it is the same on Intel (x86-64).
UPDATE - see https://github.com/JCSDA/spack-stack/issues/646#issuecomment-1636282170
To Reproduce
Try it.
Expected behavior
The error is expected. This issue will be closed by a PR that adds<EMAIL_ADDRESS>once released.
System:
macOS (version and architecture don't matter)
Additional context
n/a

This is actually on a problem on release-1.4.x, because develop has a patch:
https://github.com/JCSDA/spack/blob/01d6aa5239a8f46862d0f35a9f3533afdb9151a2/var/spack/repos/builtin/packages/met/package.py#L63
When<EMAIL_ADDRESS>or whatever the tag is comes out, then this patch will no longer be needed and likely fail. We should then update the when statement accordingly - keeping this issue open until that is done.

The expected release date for<EMAIL_ADDRESS>which will contain the fixes we need to remove the patches is targeted for July 31, 2023.

It's been released, I will work on the update next week.


doc: net: Add doc how to test Ethernet bridging with native-sim

Add instructions how to test Ethernet bridging when using native-sim board.
Fixed also couple of minor error prints noticed during testing.

Updated according to comments
Rebased to latest main


Adapt bisect script to new openqa-clone-job output

Use --json-output instead of trying to parse the human readable output
See https://progress.opensuse.org/issues/131486

Ok, a real love example on openQA would be nice

I wanted to write "live example" but I love "love example" anyway :)


issues and assign bug still not fixed

Thanks your feedback but it is duplicated to #1116

Just a note: work is in progress, improving pages one by one right now, so it should be fixed when we rewrite the new issue and issue view pages. :grinning:


When I color black transition to either color, arrow head disappears

Steps to reproduce the behavior:

Create diagram Start-Task-End

Color transitions

Arrow heads disappeared.

Expected Behavior
Arrow heads do not disappear.
Environment

OS: Windows 10, x64
Camunda Modeler Version: 3.1.2 x64

Fixed on master, pending release.

Cf. https://github.com/camunda/camunda-modeler/commit/eb95b0b5e26e9a44142ab4d9f29014d0d76b0f65.

When it will be released?

Should be working in nightly.

Duplicate of https://github.com/camunda/camunda-modeler/issues/1342.


feature request: Debug facility, show full command call

Did you check existing requests?

[X] I have searched the existing issues

Describe the feature
There doesn't seem to be a straightforward way to render resulting formatter command to stdout, etc.
I have tried `log_level = vim.log.levels.TRACE, but to no avail.
Could it be implemented?
Provide background
Related to https://github.com/stevearc/conform.nvim/issues/386. I would like to debug the issue further, but there is not enough data to narrow-down the problem.
What is the significance of this feature?
strongly desired
Additional details
Will help user users, maybe even @stevearc himself :)

Not sure what you mean by

render resulting formatter command to stdout

If you set log_level = vim.log.levels.TRACE then you should get everything you need in the log file. TRACE should actually have more than you need; if all you want is the command that should show up at DEBUG. The path to the log file is shown in :ConformInfo


자동 줄바꿈 옵션이 자꾸 초기화 됩니다.

Type: Bug
프로그램을 새로 시작할 때마다 자동 줄바꿈 옵션이 해제되는 문제가 있습니다. 이미 발생한지 좀 되었는데 참고 쓰다가 도저히 못참겠어서 제보합니다.

그러나 설명이 영어가 아니기 때문에 작업하기가 어렵습니다. 가능하다면 이 문제를 영어로 편집하십시오. 새 댓글을 추가하거나 새 문제를 만들지 말고 기존 문제를 편집하십시오.
안타깝게도 자동 번역 서비스는 소프트웨어 문제에 대해 효과적으로 의사 소통하는 데 필요한 기술 언어를 처리 할 수 없으므로 번역을 도와 줄 기술에 익숙한 인간 번역가를 찾는 것이 좋습니다.
그렇지 않으면 이 문제는 번역이 필요한 것으로 표시되었으며 커뮤니티 회원이 번역을 도울 수 있습니다.

Thanks for creating this issue!
Unfortunately, as the description is not in English, it's hard for us to work on. If possible, please edit the original issue to be in English.
In our experience, automatic translation services are not able to handle the technical language needed to effectively communicate about software issues, so we recommend finding a human translator who is familiar with our technology to help.
Otherwise, we have marked this as needing translation and a community member may be able to help out.

There is a problem with the automatic rewinding option being turned off each time you start a new program. It's been a while since it happened, now I'm reporting it because I can't stand it more.

Please give more details about what the problem is- I don't follow the explanation. Screenshots or a screen recording might help.

I mean the basic editor view option '자동 줄 바꿈' (I don't know what's the English name of it) which is making text field automatically wrapping the long text line into the next line. You can toggle it by pushing "Alt + Z".
Most of the text editors keep this setting when you restart them, but VS Code recently changed this to put this option always off every single time I open the editor.

Ok, it sounds like you toggle word wrap, but it doesn't remember the setting next time you open the editor.

I think this is intentionally.

Ok, it sounds like you toggle word wrap, but it doesn't remember the setting next time you open the editor.

exactly.

There is a setting btw.! It is just that the "toggle" only changes that setting temporarily.


build linting to warn on unused settings during reload

Fixes #3183
This implements an input task lintBuild that checks for unused settings/tasks. Because most settings are on the intermediary to other settings/tasks, they are included into the linting by default. The notable exceptions are settings used exclusively by a command. To opt-out, you can either append it to Global / excludeLintKeys or set the rank to invisible.
On the other hand, many tasks are on the leaf (called by human), so task keys are excluded from linting by default. However there are notable tasks that trip up users, so they are opted-in using Global / includeLintKeys.
lintBuild is also implemented as a function that takes a State, and I'm calling that during reload now.

credits
The core of the idea is straight from the snippet proposed by @havocp in 2011 unused settings thread that identified 58 unused settings. This filters the candidates down to locally defines settings only (also an idea discussed in the thread).

Wouldn't it be better to opt-in to such linting?  Either by opting into linting on load or by just running a task (or command).

Great work :+1: I like that such linting is enabled by default and it doesn't require an opt-in. IMO build users should not opt-in to get some checks that are most likely always on point: if their task/setting implementation isn't used anywhere, either they have dead code, sbt has a bug in its build linting logic or they messed it up. Hopefully the first and third possibilities are the most likely.

If there's high confidence then instead of warning (and going ignored, for instance in CI) let it fail the build load.

To be honest, I am not quite sure what the signal/noise ratio would be until people start using them, so this PR keeps the option somewhat open. Initially there might be some adjustment period needed, if there's a popular plugin that uses settings from a command. (Exclusion doesn't introduce new type, so plugins should be able to exclude without adding dependencies on sbt 1.4.x).
Once the dust settles during Mx or RC, and if it's mostly good suggestions, then we can keep it on as part of reload. Otherwise, we can just let users run lintUnused task or let ppl opt-in globally.
I think it would also be interesting to have a mode for plugin authors to self-check if their plugin wiring is kosher. (Currently only keys from local files are checked)


ROS 1.0.4 shutdown command not working.

RancherOS Version: (ros os version)
[root@rancher ~]# ros os list
rancher/os:v1.0.4 local latest running
Where are you running RancherOS? (docker-machine, AWS, GCE, baremetal, etc.)
vmware fusion on High Sierra Beta 5.
[root@rancher ~]# uname -a
Linux rancher 4.9.40-rancher #1 SMP Fri Jul 28 04:17:20 UTC 2017 x86_64 GNU/Linux
[root@rancher ~]# docker -v
Docker version 17.06.0-ce, build 02c1d87
[root@rancher ~]# id
uid=0(root) gid=0(root) groups=0(root),10(wheel)
[root@rancher ~]# shutdown now -h
> ERRO[0000] EOF
[root@rancher ~]# date
Wed Aug 16 15:22:48 UTC 2017

halt works.

@clemenko it looks like the arg parsing and error output isn't good.
however - the command needs to be the other way around :/
sudo shutdown -h now
sven@y260:~$ machine ssh sven2050
[rancher@sven2050 ~]$ shutdown --help
Incorrect Usage.

NAME:
   shutdown - shutdown RancherOS
built: '2017-08-08T00:05:15Z'

USAGE:
   shutdown [global options] [arguments...]

VERSION:
   v1.0.4

AUTHOR(S):
   Rancher Labs, Inc.

GLOBAL OPTIONS:
   -r value, -R value  reboot after shutdown
   -h value            halt the system
   --version, -v       print the version

[rancher@sven2050 ~]$ shutdown -h now
FATA[0000] shutdown: Need to be root
[rancher@sven2050 ~]$ sudo shutdown -h now
t> time="2017-08-17T16:47:49Z" level=info msg="Setting shutdown timeout to 60 (rancher.shutdown_timeout set to 60)"
P> time="2017-08-17T16:47:49Z" level=info msg="Stopping /docker : f7bcf762d3bb"
X...........> time="2017-08-17T16:47:50Z" level=info msg="Stopping /ntp : 186e8a30d8d3"
R.> time="2017-08-17T16:47:50Z" level=info msg="Stopping /network : c0f4219fa466"
O.> time="2017-08-17T16:47:50Z" level=info msg="Stopping /udev : b68d9637d5ae"
O> time="2017-08-17T16:47:50Z" level=info msg="Stopping /acpid : e8152fecb4f3"
Q.> time="2017-08-17T16:47:50Z" level=info msg="Stopping /syslog : 634c4a80d7af"
\.> time="2017-08-17T16:47:50Z" level=info msg="Console Stopping [/console] : 6ea4855239a9"
Connection to <IP_ADDRESS> closed by remote host.
exit status 255

Confirmed that shutdown -h now works.


Remove call to /v2/info when getting bearer token

DO NOT MERGE !!!
THIS IS JUST A PROPOSAL !!!

Coverage increased (+0.02%) to 90.916% when pulling 8f180be5e565521b70c57bab64704ce64479914d on SAP:simple_oauth into 7ccdcfed31d95a576e74c1aea05f2e72dad20773 on cloudfoundry-incubator:master.

@rajkiranrbala @KRuelY Any reason for keeping the additional roundtrip to API endpoint around?

PR #664 takes a slightly different approach, so closing this one


Debugging app in Safari

Hi,
I'm using the sample Ionic 2 app from (http://ionicframework.com/docs/v2/getting-started/installation/)
Following the instruction I was able to run the app. However, I'm unable to debug the app in Safari with source maps. In Chrome it works perfectly. I'm using OS X with Safari 9.
Adding screenshots of Chrome and Safari.
In Chrome we can see source maps files:

In safari we don't se source maps files only the bundled files:

Can we debug ionic apps with source maps in Safari or we must use Chrome? In my iOS Apps I must debug with Safari, so it's really important to have this ability.
Thanks

Per our offline discussion, I'm re-assigning this to @jthoms1.

Hello all, this should be fixed with the latest version of the Ionic cli. To install the latest version of the ionic cli simply run sudo npm install -g ionic@beta. Thanks for using Ionic!

Hi jgw96.
I have sudo npm install -g ionic@beta however still in Chrome Sourceampping works and in Safari we still have problm.
Attaching screenshot of Safari after the updating to the latest version of Ionic CLI:

Pay attention to the console errors. In addition we don't see the TypeScript files as I saw in Chrome.

Hello @galsch would you mind giving this another try with a fresh starter app? Thanks!

@jgw96 seems like the source mapping finally works - nice job.
What was the problem and how did you make it finally work in Safari?
Also, do you have support for Webpack (I see that you're using Gulp)?
Thanks!

@galsch I am actually not sure of the exact problem as I was not the one that fixed it, but if i remember right it was related to just making sure the .map files were in the proper place for safari to be able to pick them up. Also, right now we are using Browserify, but we are currently hard at work on a brand new build process that will be using Webpack 2 and will include tree shaking, minification, offline template compilation and more so that the average Ionic 2 app bundle will be tiny and get to first render extremely fast. Thanks for using Ionic!

@jgw96 I'm looking forward the transition to Webpack 2.
Good luck & Great job.
Thanks

@galsch Thanks, I am too haha! 😃


Add infrastructure for creating diagnostics for general API usage

This adds an analyzer (without code fix provider) for identifying and flagging usage of configured namespaces, types, or members and creating diagnostics with associated messages.
This will allow easily notifying users if they're using namespace, types, or members that are known to require manual changes.
Fixes #621
Fixes #502
Fixes #65
Fixes #69
Fixes #75

@twsouthwick, I've updated the PR based on your feedback (thanks!). Can you take another look?
Also, I removed launchSettings.json which it looks like you added last week but I think is unnecessary since I don't want to have a git change (or, worse, conflict) every time I f5 UA against a different project locally. Let me know if there's a reason you prefer committing the file.

The launchsettings.json change was so it would get launched with "development" enviornment so it won't send telemetry on dev work. Happy to explore other options there

Yea, I see why you changed launchsettings.json. I'll change it back to how you had it. I don't like having that file be always modified (and never committed) on my dev machine, but I can't think of a better alternative.


Fix Sumo Vehicle Height

Fix #620.
That is still not perfect as our way to add 3D information in SUMO is a bit artificial, but at least it fixes the bug introduced when we did update the SUMO version.

:+1:

:+1:


Checks if screen is retina or superior, in which case adds @2x

Ref. #276
@rochoa

Will add a test so don't merge just yet, just CR ;)

the way to do this is to have a retina flag for our layers so if it's enabled we use @2x for tiles we generate (mainly torque, png and grid)
We never can do that replacement on layers because is not standard.
@rochoa solution is a good compromise I think, we do right now something like that for https:
https://github.com/CartoDB/cartodb.js/blob/develop/src/vis/layers.js#L11

bump!


As a CIF user, I want to see which forms I updated when I edited on the summary of a revision, so that I get confirmation of which changes I made

Description:
Allowing users to review which forms they modified when creating a revision / amendment
Prototype: https://www.figma.com/proto/PzOY8RyQnVXnjZJdSv2AqQ/Wireframing_Figma?page-id=2289%3A2663&node-id=3169%3A2715&viewport=-573%2C1082%2C0.31&scaling=scale-down&starting-point-node-id=3169%3A2715&show-proto-sidebar=1 (FYI the mocks are interactive)

Acceptance Criteria:
As a CIF user
When I submit any type of project revision
Then I can see a 'Forms Updated' section
As a CIF user
When I submit any type of project revision
Then I can see a list of forms with checkboxes
Where only the updated forms are checked
As a CIF user
When I submit any type of project revision
The updated forms in the list can be expanded
And expanding them displays the diff with the previous version
As a CIF user
When I submit any type of project revision
The updated forms in the list are expanded by default
Development Checklist:

[x] Reusing what was designed in #633 to access the list of forms would be ideal, but we might want to start with a static list of forms (which will evolve as we refactor)
[x] Pattern similar to CollapsibleReport to hide / show the changed forms
[ ] Meets the DOD

Definition of Ready (Note: If any of these points are not applicable, mark N/A)

[x] User story is included
[ ] User role and type are identified
[ ] Acceptance criteria are included
[ ] Wireframes are included (if required)
[ ] Design / Solution is accepted by Product Owner
[ ] Dependencies are identified (technical, business, regulatory/policy)
[ ] Story has been estimated (under 13 pts)

·Definition of Done (Note: If any of these points are not applicable, mark N/A)

[ ] Acceptance criteria are tested by the CI pipeline
[ ] UI meets accessibility requirements
[ ] Configuration changes are documented, documentation and designs are updated
[ ] Passes code peer-review
[ ] Passes QA of Acceptance Criteria with verification in Dev and Test
[ ] Ticket is ready to be merged to main branch
[ ] Can be demoed in Sprint Review
[ ] Bugs or future work cards are identified and created
[ ] Reviewed and approved by Product Owner

Notes:

@nanyangpro @LindsayMacfarlane leaving this card in 'new issues' since we're unsure about

the benefit of collecting this data at this point in the process
how to provide feedback to the users on what was selected on this page

Thanks for the note, @pbastia!
You indicated that "the mocks are inactive" in the description above. I just checked, it should be fine. Would you mind checking it again and let me know if there are any issues accessing it from your end?

It says "interactive" :D

Hi @nanyangpro and @pbastia - taking a look at the labels assigned to this ticket - do we still require additional UX/UI or is this ready for backlog refinement? (It already has acceptance criteria). Also, given that it is related to the amendment/revisions my assumption is that this is a high priority item for implementation.

@LindsayMacfarlane @nanyangpro I am still a little confused about which data we are collecting with this list of forms, given that we don't constrain the user on which forms are to be modified.

If the purpose is only to redirect the user to the first form, I am not sure how much value this represents
The list of forms modified in an amendment can be computed on the Summary page

^ I agree with Pierre here, I don't see a lot of value in defining the forms to be updated beforehand. Maybe we can re-work this ticket to be something like: "When viewing an amendment/revision, I can see a generated list of which forms were updated"

@nanyangpro I wanted to get your confirmation about this AC:

As a CIF user
When I submit any type of project revision
The updated forms in the list are expanded by default

Hey team! Please add your planning poker estimate with Zenhub @BCerki @dleard @gurjmatharu @matthieu-foucault @mikevespi @Sepehr-Sobhani

Thanks for confirming, @pbastia! - The AC looks good.
Just a quick question, if the amended field is one that cause changes on other fields, would we check the forms/fields that's been impacted under this section as well? We can also confirm CIF Ops expectations with Taylor and Amanda tmr.

I think we should reflect those changes. Otherwise the state of the application changes - without any feedback to the user

Good call, @pbastia. - On that note, shall we visually distinguish the amended fields and the impacted fields, e.g. different colours, indicators, tooltips explaining why, etc., so that the user won't be confused?

@nanyangpro, the figma link doesn't seem to have a wireframe labelled #994. Is it one of the other ones? Also the link to #633 doesn't have a wireframe or seem particularly related to this ticket?

Thanks for the question, @BCerki - The Figma link is a prototype. You can see the part for #994 at the last step. A screen capture of the section was also provided in @pbastia's ticket description.

@nanyangpro How should we distinguish between fields a user directly updated, and fields that changed as a result?

And a follow up: the section titles line up with the tasklist sections, and some of the sections in the tasklist have more than one subsection (i.e. project details has contacts and managers). For those sections, if there are changes to both forms, should we indicate which fields are from which, or just put all of the changes in a row?

As discussed with @mikevespi on Dec 9th:

For now (before we have Tooltip component), we'll use text indicator (instead of different colours or icons) for distinguishing fields a user directly updated, and fields that changed as a result. Suggested text indicator for the latter: "This field is updated as a result of the changes you made."
Yes, let's display the hierarchy.

Based on the discussion with @nanyangpro here is the way we want to show added fields:

and here is the way we want to show removed field:

I think I need someone to walk me through the workflow for this ticket. I could see the 'forms updated' section, but could never get any data changes to display. It's also still confusing having the amendments/revisions section, but then we can still go in the "old way" to edit.

I think I need someone to walk me through the workflow for this ticket. I could see the 'forms updated' section, but could never get any data changes to display. It's also still confusing having the amendments/revisions section, but then we can still go in the "old way" to edit.

@LindsayMacfarlane I can walk you through the workflow.

Thank you @Sepehr-Sobhani - looks good!
Based on your demo at Sprint Review I was able to play around with this feature. I still struggle with the overall workflow of amendments and revisions, but that will hopefully be made more clear with @nanyangpro workflow mapping this sprint. Nan - let me know if you want me to walk you through from a user perspective on what is working and/or confusing from a potential users perspective.

Thanks for suggesting that, @LindsayMacfarlane! Appreciate it!
I share your confusion walking through the partially implemented workflow too. Hopefully it's more intuitive for the users once we have unclearness clarified for the team and the full envisioned workflows are in place.


table.rows to CSV converter fails on LifeMapper data

A multicolumn table with some complex cell contents (URLS, parenthetical lists), fails for me.  The failure is during the encoding process.      To recreate this, run "LifeMapper occurrences from Experiment Number" in the Arbor collection and enter experiment number 1530489.  Browser console shows:
POST https://arbor.kitware.com/girder/api/v1/item/romanesco/table/rows.json/csv 500 (Internal Server Error) d3.js:1919
{"message": "Exception: 'ascii' codec can't encode character u'\xed' in position 22: ordinal not in range(128)\n

It has been observed that LifeMapper sometimes returning non-vallid JSON. Closing.


Update readme description

Improves README.md to reflect the project.

cc @ameukam @BenTheElder

Is it possible to also update the current project description on the side

This project exists to explore the creation of a proxy for OCI images. This project is experimental and may change drastically or be cancelled with little or no public notice.

via a PR?
I'd like to change it to

This project is the repo for registry.k8s.io, the production domain redirect service for Kubernetes container image artifacts.

/lgtm
/approve
Thanks!

/lgtm /approve
Thanks!

@ameukam, thank you!

/label good first issue


Unable to get terraform validate to work

I'm getting the following error
terraform.validate: Failed:

Error: No Terraform configuration files found in directory: /Users/tony/Code/afedulov/terraform-fargate/terraform/templates

My workspace directory is here - https://github.com/afedulov/terraform-fargate/tree/master/terraform
Running terraform validate on the command line seems to work just fine. So i'm not sure why this is giving me issues.

the default configuration assumes that the terraform templates are stored in a folder called templates (see https://github.com/mauve/vscode-terraform/blob/master/package.json#L108-L112) relative to the workspace root.
In your case you probably want to change that configuration to terraform (you can do it in a per-workspace configuration if you want to)


Loading from byte[] broken

I am on the latest release and trying to open a PDF with a byte array:
<script>
var pdfjsframe = document.getElementById('pdfjsframe');
// At the very least, wait until the frame is ready, e.g via onload.
pdfjsframe.onload = function() {
    var data = ... data here or elsewhere ... ;
    pdfjsframe.contentWindow.PDFViewerApplication.open(data);
};
</script>````

This will just not show anything, for what I saw is that the function isArrayBuffer is checking for byteLength, but when sending a byte array the property byteLength is set in data.

what data in your case? please provide a link to your code.

Closing as incomplete until the requested information is provided. See also https://github.com/mozilla/pdf.js/blob/master/CONTRIBUTING.md.


some artificial objects are subclasses of network node right now

Description of the issue
updated on April 15th, 2020
The following classes are subclasses of NetworkNode right now:

bus: A node in an electrical network
shunt impendance (with very long def)
transformer (with very long def)

At least shunt impedance and transformer are rather artificial objects, right?
Ideas of solution
reclassify:

ShuntImpendance: ArtificialObject
Transformer: ArtificialObject

new defs?
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[x] I already read the latest version of the workflow for this repository
[x] The goal of this ontology is clear to me

I am aware that

[x] every entry in the ontology should have an annotation
[x] classes should arise from concepts rather than from words
[x] class or property names should follow the UpperCamelCase

I think, all of them should be subclasses of electricity grid component. We should do this together with #18
And electricity grid component should be an artificial object itself.

ok #18 wants to include:

Powerline

DC above ground and underground
AC by voltage (?)

switchyard

I'll close #18 then and we discuss them here

"AC by voltage": I think it is meant that there different voltage levels in AC power lines, e.g.

AC line with 380 kV
AC line with 220 kV
AC line with 110 kV

So the nominal voltages are properties of the power lines.

ok, AC, DC and Powerline also have defs already and are implemented as fiat object parts:
power line: "An uninterrupted transmission system between two nodes in the electric grid."

subclass of link

AC-Line: "Alternating current high voltage transmission line. Can comprise multiple cables and multiple circuits.
Generally, flows in the model can not be controlled but are a function of the resitance and electrochemical potential difference."

subclass of power line

HVDC-Line: Transmission system usind high voltage direct current.
Genreally, flows in the model can be controlled/optimized.

subclass of power line

any ideas for switchyard?

this should probably wait for #36

Definition proposals for current subclasses of link: (it would be easiest to update the defs directly in PR #385)

Powerline:  an electricity grid component that is an uninterrupted transmission system between two nodes in an electricity grid.

AC Powerline: A powerline for transferring high voltage alternating current.
HVDC Power line: A powerline for transferring high voltage direct current.

undirected edge: I'd suggest to delete this class. It lacks a def but seems to be related to modelling.

current subclasses of (grid)node:

network node: delete this class, since grid node will get the new def: part of a supply grid where two or more links meet

transformer: an electricity grid component that passively transfers electrical energy from one electrical circuit to another (wikipedia)
switchyard (substation): an electricity grid component that connects different levels of voltage, has_part some transformer
bus and shunt impedance: delete temporarily

Sounds good, then we make grid component classes for all types of grids? (Your pull request reads as if there will be just the general "grid component" class)

True, I corrected it in the PR.
After restructuring this, we can discuss whether some of the power generating units/ energy converting devices should also be seen as grid components. This might need further adjustment of the grid components class...


The lesson explaining the bit length for smtp is 8 bytes, but when deciphered only generates 4 bytes when entered into calculator

unsigned char stmp[8] = {0, 1, 2, 3, 4, 5, 6, 7};
This is 8 bytes, so why is the calculation only 4 bytes?Can you give me some examples?
Thanks.

If you feel you need to continue the discussion, you can reopen the issues.


Accerleration with asynchronous MCTS is unstable

Hi! When running your code, I monitored the size of prediction_queue. I find that every time the prediction_worker carries out its computation, the size of the queue is different. And the size can never reach the prediction_queue_size I set, which means the parallelism is far from enough. The queue size is usually very small. Do you have any ideas how to increase the parallelism so that every time the worker computes the result, the queue size is large enough to better utilize the GPU?

solved!


Move Ambassador's Envoy to a more upstream commit

We've gotten a big chunk of the ext_authz stuff upstreamed into Envoy, so it's time to update the version of Envoy we use to build Ambassador.

This is done as of 0.53.1.


Can't install .net7.0 version

after i use the code
islocalizer install auto -m net7.0 -l zh-cn -cc LocaleFirst
to try to install the .net7 IntelliSenseLocalizer, this tool will install .net8 version by default

There has a small error here. Now fixed in version 1.1.2. Please use command 'dotnet tool update -g islocalizer' to update and try it again.


SetState does not rerender NavigatorIOS component (w/ example repo)

Here is a repo showing the bug https://github.com/the4dpatrick/react-native-bug-example
I am trying to toggle NavigatorIOS on and off based on the prop navigationBarHidden set to a state value.
    return (
      <NavigatorIOS
        style={styles.container}
        initialRoute={initialRoute}
        navigationBarHidden={this.state.hideNavbar}
        configureScene={() => Navigator.SceneConfigs.PushFromRight}/>
    );

I pass along a method to child components that passes the parent's context and toggle the state value.
  toggleNavigation() {
    this.setState({
      hideNavbar: !this.state.hideNavbar
    });
  }

     initialRoute = {
        component: ScreenWithMenu,
        title: 'Screen',
        passProps: {
          toggleNavigation: this.toggleNavigation.bind(this)
        }
      };

Inside the sidemenu, I am calling this.props.toggleNavigation() onPress. This correctly toggles the navbar when initially hidden, but when you press onLeftButtonPress, the navbar does not toggle off.
  navigateToThemes() {
    var Themes = require('../Screens/Themes');

    this.props.menuActions.close();
    this.props.toggleNavigation();
    this.props.navigator.push({
      component: Themes,
      title: 'Themes',
      leftButtonTitle: 'Back',
      onLeftButtonPress: () => {
        this.props.navigator.pop();
        this.props.toggleNavigation();
      },
      passProps: { navigator: this.props.navigator }
    })
  }

Here is the start of the IRC chat on this bug https://botbot.me/freenode/reactnative/2015-05-26/?msg=40122019&page=1

I suspect you're running into the same issue I did (though I wanted to change the initial routes). https://github.com/facebook/react-native/pull/1300
I believe re-rendering the navigator is a no-go for the time being.
@ericvicenti thoughts?

NavigatorIOS is not currently owned by anyone on the React Native team because it is not used internally at Facebook, so this one is up to us to figure out.
The reason this isn't happening is that this property is only applied on viewDidAppear - so you will see it work when you change routes, but not when you trigger it within the same route. If you'd like to submit a patch, you're welcome to!

@the4dpatrick - this commit on your project fixes the problem, but I think it's a little hacky. If you want to clean it up into a nicer solution that would be great. Feel free to clone that repo and try it - I included the node_modules directory in it because I made changes directly to the React Native source

This is a dup of #846


fix: ssrExternal should not skip nested dependencies

Description
ssrExternal is skipping nested dependencies causing breakages during SSR
Additional context
Before digging into this, I suspected it was an issue in vite-plugin-svelte and filed an issue there: https://github.com/sveltejs/vite-plugin-svelte/issues/281. It turned out to be an issue in Vite instead

What is the purpose of this pull request?

[X] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[X] Read the Contributing Guidelines.
[X] Read the Pull Request Guidelines and follow the Commit Convention.
[X] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[X] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[X] Ideally, include relevant tests that fail without this PR but pass with it.

I just realized something. When vite-plugin-svelte starts providing support to prebundle svelte libraries, this wouldn't really be useful anymore since we don't add optimizeDeps.include with the > syntax. That means we'd still need https://github.com/sveltejs/vite-plugin-svelte/pull/289, but I wonder if we need this PR now. This PR would be useful if the parent is added to ssr.noExternal, but since the > comes from optimizeDeps.include, they aren't quite related.

Even if Svelte doesn't use the > syntax, it's still a documented feature of Vite and the bug would still exist, so I think it's probably a good change to make either way

I don't think there's a bug since Vite currently ignores these sort of syntax as expected. We can still merge this though, but it leads to extra valid ssr.external specifiers in the logic, which could be fine in most normal usecase, but we should also have vite-plugin-svelte not rely on this behaviour (and other plugins if there is)

Is it expected that Vite ignores dependencies with the > syntax? I don't think it's expected, which is why I said there's a bug. I don't think they're "extra", but rather are expected to be there, but maybe I'm mistaken?

Yeah I think it is expected that Vite ignores > right now. The reason Vite uses metadata.optimized now is to retrieved a list of known imports or dependencies after scanning. So it only cares about imports without the > syntax, as in JS there's no imports with the > syntax. The > syntax is only used in user configs or plugins, and inadvertently enters the SSR externalization logic.
But putting it another way, if we have optimizeDeps.include: ["foo > bar"] and ssr.noExternal: ["foo"], where foo is an ESM dep, and bar a CJS dep. I shouldn't expect removing optimizeDeps.include to have an impact on ssrLoadModule. Right now, if regardless of optimizeDeps.include it would always error out as expected. But with this PR, keeping the optimizeDeps.include lets ssrLoadModule work, while removing it would cause an error, which I feel is a bit inconsistent.

Hmm. The plugins are adding the > dependencies because import scanning can't find them due to unsupported file types. I suppose that might be addressed by running the Svelte plugin inside esbuild.

, if we have optimizeDeps.include: ["foo > bar"] and ssr.noExternal: ["foo"], where foo is an ESM dep, and bar a CJS dep. I shouldn't expect removing optimizeDeps.include to have an impact on ssrLoadModule. Right now, if regardless of optimizeDeps.include it would always error out as expected. But with this PR, keeping the optimizeDeps.include lets ssrLoadModule work, while removing it would cause an error, which I feel is a bit inconsistent.

I'm not sure I would expect this to error out regardless of what optimizeDeps contains. I would expect the import scanning to find both packages and externalize them both. Is that wrong?

Hmm. The plugins are adding the > dependencies because import scanning can't find them due to unsupported file types. I suppose that might be addressed by running the Svelte plugin inside esbuild.

We're currently adding > as we have to optimizeDeps.exclude Svelte libraries, but re-optimizeDeps.include the non-ESM deps of the Svelte library. Vite is able to scan Svelte files but it doesn't scan into libraries in node_modules.

I'm not sure I would expect this to error out regardless of what optimizeDeps contains. I would expect the import scanning to find both packages and externalize them both. Is that wrong?

The import scanning currently only does a shallow scan (it doesn't scan the bar transitive dependency), so it will only find foo. In most cases this is fine, as foo will be loaded by Node. But if we do ssr.noExternal: ['foo'], foo will not be loaded by Node, but goes through Vite's plugin system to "process" the package, and this is needed because Node doesn't understand how to import Svelte files.
However, in doing so the dependencies of foo, e.g. bar will be imported. Vite handles this part interestingly. Because bar is not in ssr.external, Vite will modify the import as import bla from '/path/.../bar/index.js'. In cases like this, Node will import it directly without making sure it's ESM. Only when the dep is in ssr.external, the import will be kept as import bla from 'bar', where Vite will ensure it's ESM. (Code)
This is my observation so far though. Maybe Vite should be auto-externalizing transitive deps by default, but I'm not sure how to fix this yet.

Only when the dep is in ssr.external, the import will be kept as import bla from 'bar', where Vite will ensure it's ESM.

Vite can and should import both CJS and ESM code. You linked to a line of code calling nodeImport in your last comment. If you read the jsdoc for that method it says it that it works with CJS as well.

Maybe Vite should be auto-externalizing transitive deps by default, but I'm not sure how to fix this yet.

Yes, I think Vite should externalize everything by default. I took a stab at that earlier (https://github.com/vitejs/vite/pull/6698), but one of the tests was failing and I didn't have time to investigate.


[WIP] Explorative PR for a merge of opal's fork

eregontp: @opalrb Nice! I would be interested to know how you guys use RubySpec :) Definitely open an issue if we can make it easier for you.

– https://twitter.com/eregontp/status/604710586300133376
I don't expect this PR to be merged right away, rather I'm opening it to check & fix all the little things that will make it ok for a merge.
cc @eregon @opal/core

Hello!
I see you use a custom file instead of a MSpec config to list specs to run.
And a custom set of excludes/filters instead of MSpec tags.
Is there any particular reason? Would it be because filesystem interactions are difficult or executing some parts of MSpec would require additional efforts?
I made a few comments on the diff, but for the rest I see it is mainly not_supported_on guards.
In general we try to have less guards like these as it impacts readability, makes it harder to maintain and in the end makes some parts of the spec just ignored under some implementations, which is not the goal of RubySpec.
Ideally, tags would be enough for excluding specs which are not supported, but of course that excludes a whole example (it). One solution would be to break the assertions so there is only a few should per examples. This might be good for some cases (like for equal? with strings) but might also be very cumbersome for some other cases (like Regexp options).

What features are unsupported by Opal?
I see http://opalrb.org/docs/unsupported_features/ and from the specs here also some Regexp options and Bignum?

@eregon yes 😓 docs need some love
The real list is made of the unsupported filters
https://github.com/opal/opal/tree/master/spec/filters/unsupported
plus the stuff commented in the specs list
https://github.com/opal/opal/blob/master/spec/rubyspecs
that is not part of the bug list
https://github.com/opal/opal/tree/master/spec/filters/bugs
hope it makes sense…

bugs and unsupported are combined together as an example filter and the specs list filters files, right?

Yes the difference is just to help us track what we intend to fix and what we can't do anything about (e.g. threads/encoding/tainting)

I think I addressed all comments, removing the WIP mark, let me know if there's anything else that needs to be done for the PR to be merged.
I left the date_spec update out on purpose as I'd like to prepare a proper PR for it keeping @adambeynon as the spec author.

One last note,

You are right, the spec is just about the existence of #hash.
A should respond_to(:hash) would make a lot more sense then.

I've updated the spec to use respond_to but I noticed that this way it's not calling the method anymore. Not necessarily a problem, but still worth being aware of the change.

The last commit causes failures, so it's probably better to leave it as:
lambda { obj.hash }.should_not raise_error

(The send should not be needed, right?)

ha :) just force pushed with
    obj.respond_to?(:hash).should == true

@eregon I can revert it if you want

@elia That's good too, thank you for your work!
I am still looking for a better solution than all these guards.
I think some examples can be split easily and the other are mostly compile-time issues, right?
For the compile-time problems, would it be possible to accept the syntax and compile unsupported things to something that would just raise a "NotImplementedError" or "NotSupportedError"? There is something similar in JRuby+Truffle for instance.
If you want to keep a hard error at compile-time for normal usage, maybe it would make sense to have an extra flag when running RubySpec meaning "do not fail hard with unsupported syntax and compiler stuff".
But this delayed error might actually prove useful to load third-party code and only error out on usage of unsupported stuff.

@eregon yes for some stuff we have that and I think it's the way to go long term, that being said I don't think I'll be able to tackle this change any time soon.
cc @vais

@elia Right, fair enough. Given the number of exclusions is not too big I think this is OK to merge.
Do you mind if I rebase the commits on top of master to avoid multiple merges?

All changes are merged as of 388a4adbe1b05b283b85dea048f8319ccc2b0b54.
I cherry-picked the commits on top of master, removed the ones that reverted each other and adapted a few commit messages.
Thank you for your fixes and let's use ruby/rubyspec for Opal!

@eregon @elia :+1: Good work

Great! Thanks @eregon!


add tests for views

Is your feature request related to a problem? Please describe.
For view.py create tests

I am interested to work on this issue. @harsh-9in Can you add the labels for hacktoberfest and assign it to me.

go ahead @ManishShah120 :+1:


Substring(string startString, string endString, StringInclusionOptions stringInclusionOptions) method throws an exception when "startString" and "endString" are the same.

Describe the bug
When calling the Substring(string startString, string endString, StringInclusionOptions stringInclusionOptions) method with "startString" and "endString" that are equal, the exception System.ArgumentOutOfRangeException: 'Length cannot be less than zero. (Parameter 'length')' is thrown.
To Reproduce
Steps to reproduce the behavior:

Write the following code:
"a.s.d".Substring(".", ".", StringInclusionOptions.IncludeNone);
See the error.

Expected behavior
Either select the substring, located between the equal strings, or display a more informative exception.

/cib

/cib

Issue name too long, abridging...

Let's try again: /cib

/cib


Corrections to recommendations for user consent

@psignoret : Thanks for your contribution! The author(s) have been notified to review your proposed change.


mouse wheel behavior different on left/right pane.

Im operating matternost via bluetooth mouse and awared the left pane and right pane behaves opposite movement with the same mouse wheel input.

Device Name: nova3
OS Version:android 8
Mattermost App Version:2.1.0
Mattermost Server Version:7.8.0

Expected behavior is...
Left and right pane behave same with the same mouse wheel input.

Sorry to hear, but this won't change as the list on the "right pane" is an inverted list and expected to behave as inverted. I underdtand that with the mouse wheel feels strange, but it definitely feels natural with the hands

Thank you for your reply. Does that mean that the operating specification of the mouse wheel is different between the Windows version and the Android version ...?
The Windows version (touch panel) and Android version are exactly the same when touch -scrolling.
In Windows, the left and right Panel scrolls in the same direction with mouse wheels. In the Android version, the left Panel and the right Panel scroll in the opposite direction.


[Feature Request][Documentation] Example on how to use the HTTP probe with TLS/HTTPS/443

I've searched quite a while on how to use HTTP probe when you want to probe 443 instead of 80. I managed to do so by specifying the 443 port, but then I get issues from the backend servers such as HTTP 400: the plain http request was sent to https port
If there is such documentation, can you point me to the right place? Even if it exists, is should be perhaps more prominent somewhere in the examples.
P.S. I've also found out that the cloudprober follows the redirect, so currently what we do is we probe the port 80, we get the 3xx redirect and then the 443 is probed, but I would like to prevent the extra redirect request on every probe...

Sorry for the insufficient (not so user-friendly) documentation.
Probe config options can be derived from the protobuf fields. For example here is the config protobuf for the HTTP probe type:
https://github.com/google/cloudprober/blob/master/probes/http/proto/config.proto
There are also some examples in the examples directory, though they are not easy to find too.
We'll try to improve the documentation, but for your particular use case, you need to configure 'protocol' as HTTPS:
probe {
  type: HTTP
  http_probe {
    protocol: HTTPS
    url: ...
    port: ..
  }
}

Hope this helps for now.

thx! that was exactly what we were looking for :)


Support for OPENAI_BASE_URL environment variable

In actual prompt engineering, I hope to use OpenAI's model through our own API service. I tried using the OPENAI_BASE_URL environment variable, but it seems not to work.
OpenAI's API clients support environment variables for specifying the base URL, typically used to connect to OpenAI's servers through a proxy server.
In their Python API, the name of the environment variable is OPENAI_BASE_URL: Python API reference
Can ChainForge be updated to support the same variable?

Yeah, I’ll add it this weekend or early next week.

Awesome, it's finished so quickly!
However, it seems like there are still some small issues.
I tested it, and setting the OpenAI Base URL in "ChainForge Settings" works fine.
But, if I set the OPEN_BASE_URL through an environment variable, it seems to still not take effect.
It looks like only the OPENAI_API_KEY environment variable is working, Configuring OPEN_BASE_URL via environment variables does not work.

Thanks @huangyafei , OPENAI_BASE_URL should now work in <IP_ADDRESS>.


fix ics20 ibc withdrawals

references https://github.com/penumbra-zone/web/issues/1375

@grod220 can you approve? I don't have enough context on this problem (or on ICS 20 withdrawals) to know whether this change should work

(also, a test for the ICS 20 withdrawals should be added to the extractAltFee tests, no?)

Todo for tests later plz


Resolve Clippy warnings

Resolve a ton of clippy warnings within ferrumc.
So therefore, stuff like:
!section.block_states.is_some()

are now like
section.block_states.is_none()

and etc.

oh yeah also ran cargo fmt too

Alright, thanks mate!


refactor(sso-auth-modal-plugin): convert translations to json

refactor(sso-auth-modal-plugin): convert translations to json
Description of the Change
882cc796a — refactor(sso-auth-modal-plugin): convert translations to json

Done.


cranelift-isle: Helpers to get type/term by name

This is a common pattern in sema, so factor it out.
Since this version uses intern instead of intern_mut, it might be a tiny bit faster when errors occur due to not writing names into maps then. When no error occurs, ISLE should do exactly the same work with or without this commit.

As a datapoint, this PR has passed about ten million executions of the ISLE fuzzer.


Added a default UserFactory

This adds factories.py to the common app, which abstracts loading either:

A custom UserFactory, as specified by MITOL_COMMON_USER_FACTORY
Or, a default Userfactory, defined in mitol.common.factories.default

To test this, open a shell poetry run python manage.py shell and:
from mitol.common.factories import *
UserFactory.create()

It should create the user as expected.

Codecov Report

Merging #16 into main will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              main       #16    +/-   ##
==========================================
  Coverage   100.00%   100.00%
==========================================
  Files           16        10     -6
  Lines          382       181   -201
  Branches        42        15    -27
==========================================
- Hits           382       181   -201

Flag
Coverage Δ

#mitol-django-common
?

#mitol-django-mail
100.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

mitol-django-mail/mitol/mail/test_utils.py
100.00% <0.00%> (ø)

mitol-django-common/mitol/common/__init__.py

mitol-django-common/testapp/models.py

mitol-django-common/mitol/common/utils.py

mitol-django-common/mitol/common/apps.py

mitol-django-common/mitol/common/test_utils.py

mitol-django-common/mitol/common/models.py

Continue to review full report at Codecov.

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


[WIP]Fix double render error when displaying an error flash message on edit or add provider

When an error occurs during editing or adding a configuration manager provider, a double render error occurs instead of a flash message being displayed
Will add specs

@miq-bot add_label ui, wip, bug

Closing - fixed by  #7015


Added sportid to mlb class

Why
As a developer or user I would want to be able to get players from AAA or teams from AAA
What
Updated get_teams and get_people to default to sportid 1 if no sportid is passed
Tests
four tests added and pytest ran
Risk and impact
What is the risk level of the change and why?

Minimal

Test is fixed in new branch


Best practice for delaying say() function?

Hello! I was wondering if anyone in this community has tried delaying the say() function for days after an event occurs. If so, would you mind sharing your code or any takeaways from the experience?
My project is a drip campaign that's sparked from a "team_join" event. I want a DM to go out to the Slack member immediately (already implemented this) and then send a DM every few days with follow-up information (not implemented). I'm thinking of using time.sleep() or event.wait(), but would love to hear from other folks.
Thank you!

Hi @sheafallick thanks for writing in!
This is a good question for this use case, there are a few ways I can think of to implement this.
One that stands out, if you know exactly what the messages should be, takes advantage of scheduledMessages. In short once the app receives an event it creates a series of ScheduledMessages then uses the say() function to reply to the user.
The code could look something like this
from logging import Logger

from slack_bolt import BoltContext, Say
from slack_sdk import WebClient

def sample_message_callback(context: BoltContext, say: Say, client: WebClient, logger: Logger):
    try:
        client.chat_scheduleMessage(
            channel = "C1234567890",
            post_at = "299876400",
            text = "hello in the future"
        )
        greeting = context["matches"][0]
        say(f"{greeting}, how are you?")
    except Exception as e:
        logger.error(e)

Here is more info on scheduledMessages Let me know if this is helpful!

Ah amazing, thank you @WilliamBergamin! For the "post_at" field, could I make it dynamic by saving the timestamp of the event_join and adding a set amount of time after (i.e. team_join timestamp for user x + 5 days)? We don't have a database currently so I'm particularly interested in solutions where we can save those variables locally.
If you don't know, I can do some more research here. Thank you for your help!

Absolutely, you could fetch the event time from the payload and add 5 days with something like this
def sample_message_callback(event, context: BoltContext, say: Say, client: WebClient, logger: Logger):
    try:
        next_message_time = event["event_time"] + 432000
        client.chat_scheduleMessage(
            channel = context.channel_id,
            post_at =next_message_time,
            text = "hello in the future"
        )
    except Exception as e:
        logger.error(e)

I would also tend to stay away from a database, since it introduces complexity, instead it is possible to perform the following operations on scheduledMessages

create
list
delete

Amazing, thank you so much @WilliamBergamin! I'm going to build this next week assuming Marketing gets the copy to me, I'll follow up and let you know how the effort goes.

@WilliamBergamin, thanks so much for your help! I was able to go off your advice & figure it out from there. A couple of notes from my implementation:

I needed to convert the ts in the event data to a float and then round it to the nearest second to get the time logic to work (the input for the client.chat_scheduleMessage post_at parameter needs to be an integer).
Using the "say" function w/ the greeting variable broke the code for me. I found just writing the client.chat_scheduleMessage sections of the code for each message within the function associated with the listener worked fine.

I'll close this now, I think it's working. If there are any bugs I encounter that I can't figure out I'd love to pick your brain about them. Thanks again for your time 😄


General documentation improvements

I went through most of the major structs and threw some comments in, especially in relation to odd things present in the API which aren't fully reflected in the library. I tried my best to scan for typos, but if I ended up letting one through, oops.

LGTM

After looking at it again I went through and fixed a few nits, as well as squashing the commits into one.

@sn0w thanks for the heads up; don't really know how I missed that. Hey, at least I'm finally learning how to squash commits today. :D

This is fantastic! Thanks for putting work into documentation, I love it.


Add podSecurityStandards.enforsed

Sets policy.giantswarm.io/psp-status: disabled on the Cluster CR
What does this PR do?
(Please set a descriptive PR title. Use this space for additional explanations.)
What is the effect of this change to users?
How does it look like?
(Please add anything that represents the change visually. Screenshots, output, logs, ...)
Any background context you can provide?
(Please link public issues or summarize if not public.)
What is needed from the reviewers?
Do the docs need to be updated?
Should this change be mentioned in the release notes?

[ ] CHANGELOG.md has been updated (if it exists)

@mnitchev we'll need this only during the v1.24 -> v1.25 transition phase, right?

Yeah that's what this is for. I'm currently testing it in cluster-aws here https://github.com/giantswarm/cluster-aws/pull/481


Document change.select2 on event list

Added as time to time is need it to avoid confusion between events. Base on https://github.com/select2/select2/issues/3620#issuecomment-181600117
and commit https://github.com/select2/select2/commit/7f8e9dc62a847ef63d38b8cd8f6e13f31bbb2115
Note: should an example be added?

Thanks!  It's actually documented here: https://select2.org/programmatic-control/add-select-clear-items#limiting-the-scope-of-the-change-event.
I'm actually not sure if we should add it directly to the list of events, because those are all events that Select2 triggers.  change.select2, on the other hand, is an event that the consumer triggers on Select2.

Hi, @alexweissman but the thing is that be itself is an "event", somehow because as you said it's triggered by the user, but it'll be useful to have it on the list as an event to which select react, and of course could be used as a "refresh" sometimes to avoid unwanted behavior.
Of course this will be left at your discretion :)

Let's break it into two sections then:

Events triggered by Select2
Events that can be triggered on Select2

Seems good to me, so I'll be closing as has been decided, have a nice day :)

Ok, I have updated and reorganized the events docs a bit, as inspired by your comments: https://select2.org/programmatic-control/events


workflows: Fixup typo in comment

(I'm waiting on another PR to merge this with to avoid a full CI trigger and push for a typo in the comments).


progwrp <IP_ADDRESS>18 causes an issue when writing comments in github

"Supermium 124.0.6367.245 pre-release" x86 tested on Windows XPSP3 x86 german.
I used the new progwrp.dll v1.1.5018 from this comment https://github.com/win32ss/supermium/issues/686#issuecomment-2189324440
and started the browser with the following command line (I think the cmdline does not matter):
C:\Programme\Supermium124test\chrome.exe  --disable-remote-fonts --disable-alternate-ds --safebrowsing-disable-download-protection --in-process-gpu --compact-ui --disable-features=DownloadBubble --ungoogled-supermium
Problem:
When I reply to github discussion and start each sentence with a minus-sign (doing an enumeration)
- blabla
- blabla
- blabla

Whie doing that the github website is expected to automatically suggest the next bullet-point for each line.
With progwrp.dll v1.1.5018 this doesn't work properly on the very last line of the edit field, instead it writes a whole line of minuses erroneously for me,
I do think the bug is in progwrp.dll v1.1.5018, because the bug does not happen for me in the alternative chrome-xpapi-adapter_x86.b5065-wD3D9accel by ida-re-things.

For the record this is not just a font rendering bug. The too many minuses are really there, and I have to edit them away individually by using the cursor on each character.

Finally looking at some other issues, and unfortunately I cannot reproduce this bug on XP or 2003. But I could bring out a special binary that would track any '-' key input.

yeah sure, if you can link such a binary here, I would test with it and attach some logs, that it would produce. Let me know if/how I could help.


Fix AndroidManifest merge

Need to get the correct manifest setup in the platforms/android for the plugin merge.

You might want to add it in a .aar according to this

fixed now


Update README.md

Updated to Include Azure DevOps in places of Visual Studio Team Services

@elbatk - Can you have a look at this?


Reworked generate

Implementation
A swing at addressing #70 though rather than getting any smarter about how we actually generate sentences (that can surely be improved someday), the changes in this PR implement checks that generation can succeed. Aside from the tests, and a couple little things cargo fmt threw in there, the actual implementation is relatively short, thanks to the proposal from @notDhruv, that served me well ❤
That proposal was for implementation that effectively lets us decide if generation can succeed lives here https://github.com/shnewto/bnf/issues/70#issuecomment-1356299131
I was happy to follow it to the letter, though one note if you're looking at the code, in my implementation "marking" non-terminals means adding them to a Vec called terminating_rules
Heads Up
This represents a breaking change! (though a great one imo) It removes the RecursionLimit error, and previously, you could generate from grammars that didn't hit a terminal state, they'd just print what they had, including the string representation of non-terminals if that's all there was. Now, that's not the case :)

Coverage: 91.737% (+0.7%) from 91.063% when pulling fc688cb045780d1573a3b453847e225015b3e544 on reworked-generate into 9db5aaafb99c7101340ebe180a7c7ef7c966068f on main.

Another couple notes. First, this opens the door to being able to better set some "min" and "max" for generated output but that seems to me better served by another PR. as it stands, if you generate with this grammar from the docs:
<dna> ::= <base> | <base> <dna>
<base> ::= 'A' | 'C' | 'G' | 'T'

you're going to get the same, pretty random, non-deterministic output, i.e.
Ok("AAGGC")
Ok("GCGT")
Ok("TTTC")
Ok("C")
Second! I'm still kind of toying with the idea of changing the signature on generate to take an optional starting rule, i.e. the LHS of the prod you want to "start" generating from. On one hand, it means maybe if you want to generate from different parts of a large grammar, you can more readily. On the other, it clutters the invocation with a parameter that if you don't want to use it, have to deal with passing None to opt out. It also adds another fail case / place the API can break on ya, i.e. if you pass in a starting rule that doesn't look like the starting rules we know about...
Maybe... that could be another PR and instead of adding an Option to the generate signature, we could add a non-breaking, generate_from or something if we learn there's an interest.

woah that clippy action is great, will address those fixes a bit later but also, TIL that default cargo clippy I guess ignores tests and you need one of --all-features --all-targets to get these lints locally?

Yeah since cfg(test) is technically a "feature", compilation and clippy don't include any test (or other features/targets) without those flags.
I personally think test should at least be a default clippy feature enabled, but w/e