max-provisioned-writes AND enable-writes-up-scaling can be ignored

I was experimenting with this on a development environment and had a situation where these configuration options were not sufficient to stop the tool from updating the write throughput.
under [default_options] I have both
max-provisioned-writes:  2
enable-writes-up-scaling: false
And yet, the following occurred in the logs:
[ec2-user@ip-192-168-11-111 ~]$ dynamic-dynamodb --config test.conf
2016-04-25 17:18:48,623 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Consumed read units: 20.53%
2016-04-25 17:18:48,648 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Consumed write units: 0.00%
2016-04-25 17:18:48,677 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Consumed read units: 20.53%
2016-04-25 17:18:48,686 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Read throttle count: 10
2016-04-25 17:18:48,702 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Throttled read percent by provision: 0.33%
2016-04-25 17:18:48,726 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Throttled read percent by consumption: 1.62%
2016-04-25 17:18:48,727 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Consecutive read checks 1/1
2016-04-25 17:18:48,756 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Consumed write units: 0.00%
2016-04-25 17:18:48,771 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Write throttle count: 0
2016-04-25 17:18:48,795 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Throttled write percent by provision: 0.00%
2016-04-25 17:18:48,823 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Throttled write percent by consumption: 0.00%
2016-04-25 17:18:48,824 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Scaling down writes is not done when usage is at 0%
2016-04-25 17:18:48,824 - dynamic-dynamodb - INFO - Will not increase writes over max-provisioned-writes limit (2 writes)
2016-04-25 17:18:48,824 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Consecutive write checks 0/1
2016-04-25 17:18:48,824 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Changing provisioning to 5 read units and 2 write units
2016-04-25 17:18:48,863 - dynamic-dynamodb - INFO - Dev.PlayerInventory - Updating provisioning to 5 reads and 10 writes
You'll notice that it indicates it will not increase writes over max-provisioned-writes, but it does update it anyway. Furthermore, the consumed write units was 0.00%. at the time, so there was no need to increase it.
This happened while I was experimenting with lookback-window-start value. I tried setting the value to 1-2 minutes, which seems to be too small and caused inaccurate measurement of the Consumed Read Units. I can reproduce this behavior with dry-runs at will by setting this value to 2 or 1. At 3, the behavior goes away.

As a side note, you might consider updating the documentation on lookback-window-start. It appears unstable below a value of 3, which would also match with my Cloudwatch experience. Realistically dynamo cloudwatch values don't seem to be reliably available prior to that and the edge case doesn't appear to be handled.


Load Transaction (no body)

loadTransactions() => [transaction1, transaction2...]

Eventually will need filtering but this will do for now

sort by date

@allanfang1 close this issue if your satisfied with the endpoint... leave ur comments here


Don't show hide files magic in Dockerfile inside image in /root/build…

…info/

OSBS-7865

Signed-off-by: Robert Cerven<EMAIL_ADDRESS>

rn updated

Don't show hide files magic in Dockerfile inside image in /root/buildinfo/


DevSite Import: Authentication Overview

Notice: This DevSite page will soon be deleted per b/133171590. Please add this sample to GitHub if it is relevant still:
https://developers.google.com/api-client-library/python/guide/aaa_overview

Authentication Overview

    This document is an overview of how authentication, authorization, and accounting are accomplished.
    For all API calls, your application needs to be authenticated.
    When an API accesses a user's private data, your application must also be authorized by the user to access the data.
    For example, accessing a public Google+ post would not require user authorization,
    but accessing a user's private calendar would.
    Also, for quota and billing purposes, all API calls involve accounting.
    This document summarizes the protocols used by Google APIs and provides links to more information.

Access types

  It is important to understand the basics of how API authentication and authorization are handled.
  All API calls must use either simple or authorized access (defined below).
  Many API methods require authorized access, but some can use either.
  Some API methods that can use either behave differently,
  depending on whether you use simple or authorized access.
  See the API's method documentation to determine the appropriate access type.

1. Simple API access (API keys)

  These API calls do not access any private user data.
  Your application must authenticate itself as an application belonging
  to your Google API Console project.
  This is needed to measure project usage for accounting purposes.

API key:
  To authenticate your application, use an
  API key
  for your API Console project.
  Every simple access call your application makes must include this key.

Warning:
    Keep your API key private.
    If someone obtains your key,
    they could use it to consume your quota or incur charges
    against your API Console project.

2. Authorized API access (OAuth 2.0)

  These API calls access private user data.
  Before you can call them,
  the user that has access to the private data must grant your application access.
  Therefore, your application must be authenticated,
  the user must grant access for your application,
  and the user must be authenticated in order to grant that access.
  All of this is accomplished with
  OAuth 2.0 and libraries written for it.

Scope:
  Each API defines one or more scopes that declare a set of operations permitted.
  For example, an API might have read-only and read-write scopes.
  When your application requests access to user data,
  the request must include one or more scopes.
  The user needs to approve the scope of access your application is requesting.

Refresh and access tokens:
  When a user grants your application access, the OAuth 2.0 authorization server
  provides your application with refresh and access tokens.
  These tokens are only valid for the scope requested.
  Your application uses access tokens to authorize API calls.
  Access tokens expire, but refresh tokens do not.
  Your application can use a refresh token to acquire a new access token.

Warning:
    Keep refresh and access tokens private.
    If someone obtains your tokens,
    they could use them to access private user data.

Client ID and client secret:
  These strings uniquely identify your application and are used to acquire tokens.
  They are created for your project on the API Console.
  There are three types of client IDs,
  so be sure to get the correct type for your application:

Web application client IDs
Installed application client IDs
Service Account client IDs

Warning:
    Keep your client secret private.
    If someone obtains your client secret,
    they could use it to consume your quota,
    incur charges against your Console project,
    and request access to user data.

Using API keys

    More information and examples for API keys are provided on the
    API Keys
    page.

Using OAuth 2.0

    More information and examples for OAuth 2.0 are provided on the
    OAuth 2.0
    page.

The docs are now added to the docs/ folder.
Fixed with #706.


Make sure CSS box-sizing: border-box has -moz version too

In testing Moonstone on Firefox, I noticed a lot of buttons with the
wrong size.  This turned out to be a problem where Firefox hasn't yet
implemented a non-prefixed version of the CSS box-sizing rule.
We had some places where we had the -moz version, but the usage wasn't
consistent in Moonstone. I noticed that we had a .box-sizing CSS
selector, so I used Less's mixin support to replace all the explicit
border-box uses with that rule.
Enyo-DCO-1.1-Signed-Off-By: Ben Combee<EMAIL_ADDRESS>

Thanks for the work, sadly, so out of date we can't merge easily!


Added started log message used in Selenium 4.0.0

I updated Selenium to 4.0.0 on my project and the BrowserWebDriverContainer failed to start because non of the current messages are logged by the container anymore. After manully adding waitingFor(Wait.forLogMessage(".*Started Selenium Standalone.*", 1)) the container are starting again and the tests are also working.
Example of container logs for docker run selenium/standalone-chrome:4.0.0:
2021-10-14 08:34:48,824 INFO Included extra file "/etc/supervisor/conf.d/selenium.conf" during parsing
2021-10-14 08:34:48,826 INFO supervisord started with pid 8
2021-10-14 08:34:49,829 INFO spawned: 'xvfb' with pid 10
2021-10-14 08:34:49,832 INFO spawned: 'vnc' with pid 11
2021-10-14 08:34:49,835 INFO spawned: 'novnc' with pid 12
2021-10-14 08:34:49,837 INFO spawned: 'selenium-standalone' with pid 13
Setting up SE_NODE_GRID_URL...
2021-10-14 08:34:49,844 INFO success: xvfb entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-10-14 08:34:49,845 INFO success: vnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-10-14 08:34:49,845 INFO success: novnc entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2021-10-14 08:34:49,845 INFO success: selenium-standalone entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
Selenium Grid Standalone configuration:
[network]
relax-checks = true

[node]
session-timeout = "300"
override-max-sessions = false
detect-drivers = false
max-sessions = 1

[[node.driver-configuration]]
display-name = "chrome"
stereotype = '{"browserName": "chrome", "browserVersion": "94.0", "platformName": "Linux"}'
max-sessions = 1

Starting Selenium Grid Standalone...
08:34:50.241 INFO [LoggingOptions.configureLogEncoding] - Using the system default encoding
08:34:50.246 INFO [OpenTelemetryTracer.createTracer] - Using OpenTelemetry for tracing
08:34:50.795 INFO [NodeOptions.getSessionFactories] - Detected 6 available processors
08:34:50.843 INFO [NodeOptions.report] - Adding chrome for {"browserVersion": "94.0","browserName": "chrome","platformName": "Linux","se:vncEnabled": true} 1 times
08:34:50.858 INFO [Node.<init>] - Binding additional locator mechanisms: name, id, relative
08:34:50.879 INFO [LocalDistributor.add] - Added node 1b12f5e0-f89f-4ddd-8dd5-227a735853c0 at http://<IP_ADDRESS>:4444. Health check every 120s
08:34:50.884 INFO [GridModel.setAvailability] - Switching node 1b12f5e0-f89f-4ddd-8dd5-227a735853c0 (uri: http://<IP_ADDRESS>:4444) from DOWN to UP
08:34:51.008 INFO [Standalone.execute] - Started Selenium Standalone 4.0.0 (revision 3a21814679): http://<IP_ADDRESS>:4444


Client Allocation Request for: LandSatFile

Client Allocation Questions
Core Information

Name: LandSatFile
Website / Social Media: https://slingshot.filecoin.io/project/5fc274a7bb7b32dc2a0841d2
DataCap Requested: 5TiB
Addresses to be Notarized: f3wtftfpyxqyc4geuvca72k6o7ctkn4b7urbavnlizujtrow3qtdjzzpbc4mp7z4327mkzzqnfykzm333fk6sa
Notary Requested: ann-shin

Thank you for your application. Because of our account problem, you need to login plus.fil.org to apply again.


To add a Media property for comments_disabled/interactive

Currently, there's an option to get  comment_count, but there's no way to know whether the comments are closed or not.
This always returns 0 even if the comments are closed.
Is it possible to add this functionality?

with media_info you can get that details.

Hey kingbotss, thanks for your reply. The thing is media_info returns a Media object. Below, you can see the declaration of this class. There's no such property there. The only thing close enough is comment_count, which is 0 for both posts with 0 comments and for posts with comments disabled. There's no way to differentiate those. There's no other attribute like comments_disabled: bool or something like that. Hence, my request to add this feature.
class Media(BaseModel):
pk: str
id: str
code: str
taken_at: datetime
media_type: int
product_type: Optional[str] = ""  # igtv or feed
thumbnail_url: Optional[HttpUrl]
location: Optional[Location] = None
user: UserShort
comment_count: Optional[int] = 0 #-----------------------< This
like_count: int
has_liked: Optional[bool]
caption_text: str
accessibility_caption: Optional[str]
usertags: List[Usertag]
video_url: Optional[HttpUrl]  # for Video and IGTV
view_count: Optional[int] = 0  # for Video and IGTV
video_duration: Optional[float] = 0.0  # for Video and IGTV
title: Optional[str] = ""
resources: List[Resource] = []
clips_metadata: dict = {}

The media info endpoint returns more details, You can check.

Here's the output of the media_info function for this random post with comments turned off https://www.instagram.com/p/BzKYwnpi712/
I'm not sure where to look for the attribute you refer to.
media_info():
pk='2074579472581639542'
id='2074579472581639542_11578752162'
code='BzKYwnpi712'
taken_at=datetime.datetime(2019, 6, 26, 6, 6, 6, tzinfo=datetime.timezone.utc)
media_type=1
product_type=''
thumbnail_url=HttpUrl('https://instagram.fifo4-1.fna.fbcdn.net/v/t51.2885-15/64613952_883010682035863_9110585929113117144_n.jpg?stp=dst-jpg_e35&_nc_ht=instagram.fifo4-1.fna.fbcdn.net&_nc_cat=107&_nc_ohc=w6vMd5ByxJMAX9O2HBg&edm=AP_V10EBAAAA&ccb=7-5&oh=00_AT-1RFYV7rNtvTP06JQpRoTuJz9GfOnZW8eAM7Tdt69WIg&oe=62AC7960&_nc_sid=4f375e',
scheme='https',
host='instagram.fifo4-1.fna.fbcdn.net',
tld='net',
host_type='domain',
port='443',
path='/v/t51.2885-15/64613952_883010682035863_9110585929113117144_n.jpg',
query='stp=dst-jpg_e35&_nc_ht=instagram.fifo4-1.fna.fbcdn.net&_nc_cat=107&_nc_ohc=w6vMd5ByxJMAX9O2HBg&edm=AP_V10EBAAAA&ccb=7-5&oh=00_AT-1RFYV7rNtvTP06JQpRoTuJz9GfOnZW8eAM7Tdt69WIg&oe=62AC7960&_nc_sid=4f375e')
location=None
user=UserShort(pk='11578752162', username='sensodyne_latvia', full_name='Sensodyne_latvia', profile_pic_url=HttpUrl('https://instagram.fifo4-1.fna.fbcdn.net/v/t51.2885-19/51600999_358922564721327_7029198993380868096_n.jpg?stp=dst-jpg_s150x150&_nc_ht=instagram.fifo4-1.fna.fbcdn.net&_nc_cat=103&_nc_ohc=TRwsGkaSgZkAX9q8WYh&edm=AP_V10EBAAAA&ccb=7-5&oh=00_AT9MMz2OPgjCAV3PEt86CKhGPNddiQYQSyFz4hQVI1hy4A&oe=62AC0F3F&_nc_sid=4f375e', scheme='https', host='instagram.fifo4-1.fna.fbcdn.net', tld='net', host_type='domain', port='443', path='/v/t51.2885-19/51600999_358922564721327_7029198993380868096_n.jpg', query='stp=dst-jpg_s150x150&_nc_ht=instagram.fifo4-1.fna.fbcdn.net&_nc_cat=103&_nc_ohc=TRwsGkaSgZkAX9q8WYh&edm=AP_V10EBAAAA&ccb=7-5&oh=00_AT9MMz2OPgjCAV3PEt86CKhGPNddiQYQSyFz4hQVI1hy4A&oe=62AC0F3F&_nc_sid=4f375e'), profile_pic_url_hd=None, is_private=False, stories=[])
comment_count=0
like_count=30
has_liked=None
caption_text='Vai Tu zināji, ka ieteicams skalot muti 30 sekundes līdz 1 minūtei ar tam paredzēto līdzekli, pirms to izspļaut? Pārliecinies, ka lieto mutes dobuma kopšanas produktus pareizi, lai varētu saskatīt vēlamos rezultātus 😊\n.\n.\n.\n#sensodyne #latvia #smile #healthcare #enjoylife #sensitivity #sensitiveteeth #smile #smilewide #springsmile #beautifulsmile'
accessibility_caption=None
usertags=[]
video_url=None
view_count=0
video_duration=0.0
title=''
resources=[]
clips_metadata={}

Thanks for the clue, kingbots. Indeed, the media_info function calls a number of functions, the final one of which is extract_media_gql.  All you have to do is to extend the Media class and add a property for comments_possible. I consider this issue resolved.


VSO refered me wrongly to this page, should be to a subpage

Hi,
My build: (id:8525995, account:mseng) failed which a promise of documentation on why shallow-cone might fail:
##[warning]Git checkout failed on shallow repository, this might because of git fetch with depth '1' doesn't include the checkout commit <anonymized>'. Please reference documentation (http://go.microsoft.com/fwlink/?LinkId=829603)
4121

But this page doesn't seem to have this information. It seems the content moved to a sub-page (Pipeline options for git). It would be nice if either the parent doc can mention that the shallow-clone docs are in the sub-page or ideally the fwlink would be updated to shallow-fetch section in 'Pipeline options for Git' page

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

ID: e59bebc3-fe8a-ad9e-7c55-884a8c7b4bac
Version Independent ID: 7db3d604-b118-2f7b-85f4-1bd52244b279
Content: Build source repositories - Azure Pipelines
Content Source: docs/pipelines/repos/index.md
Product: devops
GitHub Login: @steved0x
Microsoft Alias: sdanie

I was also linked here from the DevOps pipelines Build edit screen for the "Get Sources" task.

The link should provide more information whether or not you want to "tag sources" but there is nothing on this page about "tagging".

I was also linked here from the DevOps pipelines Build edit screen for the "Get Sources" task.

The link should provide more information whether or not you want to "tag sources" but there is nothing on this page about "tagging".

Azure Devops link is https://aka.ms/ci-tagsources but redirects to this page currently titled "Build source repositories"


Add ability to add team members to itinerary

We need to be able to select from potential team members and add them to an itinerary. The following rules must apply.
They must be assigned (and accepted) to a task from the same event. That task must occur on the same date as the itinerary is scheduled for. Only users who are not part of an itinerary for that day already should be shown.
@tonysurma I'm working on this currently.

Update - Worked on this in the morning. Getting close so hope to have something I can check in soon.


Export improvements

It is currently not possible to export table properties in JSON – it should be enough to add the appropriate processor.
Export should be also documented better and properly tested for all the datasets (cf. #29).

Also add a checkbox "Export with properties". This can be integrated for both HTML and XLSX (although not CSV because the number of columns would not fit).


Release v1.2.1 of Ceph-CSI driver

[x] Define release process

Release doc would be a good start

[x] Define release deadlines

Code Freeze : 25-Sep-2019
RC : 30-Sep -2019
GA : 05-Oct-2019

[x] Define/list roadmap for v1.2.1

Proposed contents for v1.2.1 release

[x] Release Team:

@Madhu-1

@humblec

The release blockers (issues/PRs) are labelled with release-1.2.1.
https://github.com/ceph/ceph-csi/labels/release-1.2.1

[x] Document features and announce the release.

The plan here is to make a bug fix release, either we can call it as 1.2.1 or 1.3.0. Any preference?

I would stick semver as the defined in the releases.md file, IOW move this to 1.2.1 not 1.3.0.

@humblec, as we are doing bug fixes, will go with 1.2.1

yeah. lets stick to 1.2.1.

https://github.com/ceph/ceph-csi/issues/609

I would prefer the following format.
VERSION.RELEASE.BUGFIX
Where VERSION.RELEASE should follow the CSI standard's current specification version as much as possible. That makes it easy to understand the capabilities of each release.

The v1.2.1 release is out
https://github.com/ceph/ceph-csi/releases/tag/v1.2.1
I am closing this issue !!


[BUG] config-data.yaml uses different formats for cluster names

connectedhome/src/app/common/templates/config-data.yaml has a few top-level tags.
The format used by CommandHandlerInterfaceOnlyClusters, DefineBitmaps, WeakEnums seems to be the cluster name with no spaces, converted to CamelCase.
The format used by ClustersWithInitFunctions, ClustersWithAttributeChangedFunctions, ClustersWithShutdownFunctions, and ClustersWithPreAttributeChangeFunctions is the cluster name with spaces and no case conversion: as defined in the cluster XML file.
It's a quite confusing, and formats should converge
Context: https://github.com/project-chip/connectedhomeip/pull/29162

Note a ZAP issue.  On the ZAP side, this is just doing "look up a string you provide in the list you name".  The strings and list names are all provided in Matter templates.

While CommandHandlerInterfaceOnlyClusters is indeed processed by the templates connectedhome/src/app/zap-templates/templates/app/im-cluster-command-handler.zapt and connectedhome/src/app/zap-templates/templates/app/callback.zapt, ClustersWithInitFunctions and others are populated by zap/src-electron/generator/matter/app/zap-templates/templates/app/helper.js, thus the ticket was opened here.
Happy to open the issue on the matter side of things


[Question] Resizeable models

Hi.
The openvino support resizable models. You can change input shape and outputs shape will change too.
Is it possible convert such models?

The tool is designed to optimize the model to the limit for low-spec edge devices, so there are no plans to support variable resolution or variable batches at this time. This may be implemented in the future.

Hi! Is it still impossible to convert model with variable batch size from OV to TF?

OpenVINO -> ONNX
https://github.com/PINTO0309/openvino2tensorflow

ONNX ->sbi4onnx -> N batch ONNX
https://github.com/PINTO0309/simple-onnx-processing-tools

N batch ONNX -> TF

$ onnx-tf convert -i mobileone_s0_Nx3xHxW.onnx -o saved_model

/usr/local/lib/python3.8/dist-packages/tensorflow_addons/utils/ensure_tf_install.py:53: UserWarning: Tensorflow Addons supports using Python ops for all Tensorflow versions above or equal to 2.3.0 and strictly below 2.5.0 (nightly versions are not supported).
 The versions of TensorFlow you are currently using is 2.9.0 and is not supported.
Some things might work, some things might not.
If you were to encounter a bug, do not file an issue.
If you want to make sure you're using a tested and supported configuration, either change the TensorFlow version or the TensorFlow Addons's version.
You can find the compatibility matrix in TensorFlow Addon's readme:
https://github.com/tensorflow/addons
  warnings.warn(
2022-07-29 20:04:51,012 - onnx-tf - INFO - Start converting onnx pb to tf saved model
WARNING:absl:Found untraced functions such as gen_tensor_dict while saving (showing 1 of 1). These functions will not be directly callable after loading.
2022-07-29 20:05:07,449 - onnx-tf - INFO - Converting completes successfully.
INFO:onnx-tf:Converting completes successfully.

$ saved_model_cli show --dir saved_model/ --all

MetaGraphDef with tag-set: 'serve' contains the following SignatureDefs:

signature_def['__saved_model_init_op']:
  The given SavedModel SignatureDef contains the following input(s):
  The given SavedModel SignatureDef contains the following output(s):
    outputs['__saved_model_init_op'] tensor_info:
        dtype: DT_INVALID
        shape: unknown_rank
        name: NoOp
  Method name is:

signature_def['serving_default']:
  The given SavedModel SignatureDef contains the following input(s):
    inputs['input'] tensor_info:
        dtype: DT_FLOAT
        shape: (-1, 3, -1, -1)
        name: serving_default_input:0
  The given SavedModel SignatureDef contains the following output(s):
    outputs['184'] tensor_info:
        dtype: DT_FLOAT
        shape: (-1, 1000)
        name: StatefulPartitionedCall:0
  Method name is: tensorflow/serving/predict

Concrete Functions:
  Function Name: '__call__'
        Named Argument #1
          input

  Function Name: 'gen_tensor_dict'


Issue with detect script

I am having trouble running the detect.py script. When I run it after training and loading weights from that training, I get this error:
Traceback (most recent call last):
File "detect.py", line 65, in
app.run(main)
File "C:\Users\venkav1\AppData\Local\Continuum\anaconda3\envs\tf-n\lib\site-packages\absl\app.py", line 300, in run
_run_main(main, args)
File "C:\Users\venkav1\AppData\Local\Continuum\anaconda3\envs\tf-n\lib\site-packages\absl\app.py", line 251, in _run_main
sys.exit(main(argv))
File "detect.py", line 53, in main
for i in range(nums[0]):
TypeError: 'Tensor' object cannot be interpreted as an integer
When I print out nums, it gives this <tf.Tensor 'yolov3/yolo_nms/combined_non_max_suppression/CombinedNonMaxSuppression:3' shape=(1,) dtype=int32>)
Any idea on how to fix this?

thats weird the output shape of NMS shoudln't be (1,).
does detect.py work with default pretrained weights? how did you train and load weights.

It produces the same result and error when i load the pre-trained darknet weights. I trained using the train.py script and loaded the checkpoint file yolov3_train_2.tf that was produced by the training script in this line.
flags.DEFINE_string('weights', './checkpoints/yolov3_train_2.tf',
'path to weights file')
For loading the pretrained weights, I just used the yolov3.tf file that is produced from the convert.py script.

I am getting the same error. The nums varaible is a tensorflow varaible and not an integer. I am getting boxes,  scores and everything as 0s from yolov3(img). Any clue why this is happening?

I am getting the same error as @varunvbsci, did you figure out the solution to it?

can you update to the latest version and try again?


yoink ignores total_freeleech_size

My config:
total_freeleech_size: "50GB" # Max space to use for downloads. If 0, no limit is applied
category: "FreeLeech" # Category to use for downloads.
paused: false # Whether to pause torrents after adding them to qBittorrentf
qbittorrent: # Connection details for qBittorrent
  host: "http://localhost:22222"
  username: ""
  password: ""
prowlarr: # Connection details for Prowlarr
  host: "http://localhost:9696"
  api_key: ""
indexers: # List of indexers to use. Filters out any indexers not in this list
  - id: 27 # ID of the indexer in Prowlarr
    max_seeders: 20 # Maximum number of seeders to allow. 0 = no limit
    max_size: "25GB" # Maximum file size to allow. 0 = no limit
    min_leechers: 0 # Minimum number of leechers to allow. 0 = no limit
  - id: 36 # ID of the indexer in Prowlarr
    max_seeders: 20 # Maximum number of seeders to allow. 0 = no limit
    max_size: "25GB" # Maximum file size to allow. 0 = no limit
    min_leechers: 0 # Minimum number of leechers to allow. 0 = no limit
  - id: 39 # ID of the indexer in Prowlarr
    max_seeders: 20 # Maximum number of seeders to allow. 0 = no limit
    max_size: "25GB" # Maximum file size to allow. 0 = no limit
    min_leechers: 0 # Minimum number of leechers to allow. 0 = no limit

Dry-run log:
❯ yoink --dry-run --config yoink.yaml

██╗   ██╗ ██████╗ ██╗███╗   ██╗██╗  ██╗
╚██╗ ██╔╝██╔═══██╗██║████╗  ██║██║ ██╔╝
 ╚████╔╝ ██║   ██║██║██╔██╗ ██║█████╔╝
  ╚██╔╝  ██║   ██║██║██║╚██╗██║██╔═██╗
   ██║   ╚██████╔╝██║██║ ╚████║██║  ██╗
   ╚═╝    ╚═════╝ ╚═╝╚═╝  ╚═══╝╚═╝  ╚═╝
           0.5.0 - MrMarble

┌───────────────────────────────────────┐
│       Running in dry-run mode.        │
│    No torrents will be downloaded.    │
└───────────────────────────────────────┘

Total download size: 50GB
Checking qbt connection... OK
Found 5 torrents in qBittorrent:
  [257 kB] The Loneliness Companion_ A Pra - Shrein H....
  [319 MB] The Art And Science Of Modern Hacking
  [1.0 GB] The Complete ChatGPT Guide From Zero to Hero 2023
  [219 kB] Friends with Benefits Goals by Barbi Cox.epub
  [237 kB] John C. Maxwell - How Successful People Think.epub
Used space: 1.4 GB, Left: 49 GB
Checking prowlarr connection... OK
Searching for freeleech torrents...
Found 186 freeleech torrents:
Uploading 186 torrents (1.3 TB) to qBittorrent...

paused: false setting is ingored too it seems

+1 on paused: false being ignored.


Fix issue with mmdc executable path on Windows

To run the Mermaid engine on Windows, you need to use mmdc.cmd instead of mmdc.

Thanks for the PR and apologies for the late reply.
Could you test if something like this would work as well?
self.execpath or (pandoc.system.os:match 'windows' and 'mmdc.cmd' or 'mmdc'),

I think I'd prefer the built-in OS field over querying an env-var.

Hi @tarleb, I found that the issue might have been caused by my installation environment. After reinstalling mermaid-cli, I can now run mmdc smoothly without having to use mmdc.cmd. So please ignore and close this PR, thank you.

Good to know, and thanks again!


Openshift route is added 🎉

Summary
Add Openshift route template and update values file accordingly.
Fix imageTag variable for MySQL version which was misnamed from the subchart.

Thanks @ckavili for the pull request!
Per the CONTRIBUTING.md file displayed when you created this pull request, we need to add you to the list of approved contributors for the Mattermost project.
Please help complete the Mattermost contribution license agreement?
This is a standard procedure for many open source projects. Your form should be processed within 24 hours and reviewers for your pull request will be able to proceed.
Please let us know if you have any questions.
We are very happy to have you join our growing community! If you're not yet a member, please consider joining our Contributors community channel to meet other contributors and discuss new opportunities with the core team.

/check-cla

Hi @cpanato Thanks for the review! Just updated the files based on your comments.


The Properties of one blob snapshot are editable

Storage Explorer Version: 1.12.0
Build: 20200322.2
Branch: master
Platform/OS: Windows 10/ Linux Ubuntu 18.04/ macOS High Sierra
Architecture: ia32/x64
Regression From: Previous release(1.12.0)
Steps to reproduce:

Expand one Non-ADLS Gen2 storage account -> Blob Containers.
Create a new blob container -> Upload one blob to it -> Create snapshot for the blob -> Manage Snapshots.
Select a snapshot -> Right click it -> Click 'Properties..'.
Check the Properties dialog.

Expect Experience:
The properties are not editable.
Actual Experience:
The properties are editable.

Need to update se-blob-extension

This issue has been fixed on build 20200329.1. Close it.


rpm: Use /usr/bin/atom with desktop file

Requirements
Description of the Change
Multiple people over multiple releases have had issues starting atom
noting scl errors. The fix was noted to be running /usr/bin/atom and has
been verified by multiple users. This change updates the desktop file to
use /usr/bin/atom instead of /usr/share/atom/atom.
Alternate Designs
The current alternate designs are:

Tell rpm users to not use the desktop file and instead run atom from the terminal.
Have all terminal based packages work around the issue

Why Should This Be In Core?
So people who install via rpm can click the desktop icon and use atom without errors 😄
Benefits
Same as "Why should this be in core?"
Possible Drawbacks
I don't think there are any but I created this quickly based on the issue.
Applicable Issues
See: https://github.com/atom/atom/issues/13451

@ashcrow change the line to Exec=<%= installDir %>/bin/<%= appFileName %> %F

Closing in favor of https://github.com/atom/atom/pull/17508


[PT Run] Option for system commands localization

Summary of the Pull Request
What is this about:
Adding option to system commands plugin for localization.
By default commands are localized (current PT behaviour).
What is include in the PR:

Settings

Localize: true

Localize: false
How does someone test / validate:

In order to see the new option in the settings https://github.com/microsoft/PowerToys/pull/12920 is needed, but additional option {"Key":"LocalizeSystemCommands","DisplayLabel":"Use localized system commands instead of english ones","Value":true} can be added manually to %LOCALAPPDATA%\Microsoft\PowerToys\PowerToys Run\settings.json.
Since resources are localized in build farm you need to manually add to build output localized resources, eg: PowerToys\x64\Debug\modules\launcher\Plugins\System\it\Microsoft.PowerToys.Run.Plugin.System.resources.dll.

Quality Checklist

[x] Linked issue: #12063
[ ] Communication: I've discussed this with core contributors in the issue.
[ ] Tests: Added/updated and all pass
[ ] Installer: Added/updated and all pass
[x] Localization: All end user facing strings can be localized
[ ] Docs: Added/ updated
[x] Binaries: Any new files are added to WXS / YML

[x] No new binaries
[ ] YML for signing for new binaries
[ ] WXS for installer for new binaries

Contributor License Agreement (CLA)
A CLA must be signed. If not, go over here and sign the CLA.

@davidegiacometti
I think it would be better to allow searching for both if a setting is set to true. Something like show localized results too.

@htcfreek search by subtitle isn't possible, that's why subtitle isn't affected by the option.
I'll mark this PR as draft. Let's discuss on the issue how to implement this feature: https://github.com/microsoft/PowerToys/issues/12063

PR and screenshot in the first post updated.

Now both title and subtitle follow the option (english/localized)
Changed the option label

@mykhailopylyp can you confirm that if merged now will be released in 0.47?
Considering that https://github.com/microsoft/PowerToys/issues/12483 is needed, and there is also https://github.com/microsoft/PowerToys/issues/12293 would be nice to release these together.

@mykhailopylyp can you confirm that if merged now will be released in 0.47?

Don't see a reason why it wouldn't be released in 0.47. It will not be released in 0.45 though.

Hi @davidegiacometti ,
Do you still want to make any changes or can I go ahead and merge it?

Hi @davidegiacometti ,
Do you still want to make any changes or can I go ahead and merge it?

You can merge it.
Thanks 😃

Thank you for the contribution!


Allow to write multiline configs in form

Have no idea how to deal with it with our press Enter to submit. Maybe we should add auto-submit during the input?

Yes, I suggest making a demo. And add a little 300ms denounce for typing.
We need to see if users get annoyed by the error messages.

I think we can do this:

Enter to add a newline
Cmd+Enter to submit
Add gray-ish note like "Press ⌘+Enter" after "Display compatible browsers"

And Ctrl+Enter for non-Mac users

Copy-pasting of multi-line config doesn’t work too


Fix appveyor config to check for node module cache dir before creation

check for path first

Now it fails because it's taking too long to run.  I think the limit is 40 minutes.

Oh good grief.  We really need to clean up the tests, that's ridiculous.  Should we just merge it?

I'd say merge it. At least it make's the run less broken.  The longer term fix is to make the tests faster, and that means reducing the number of files that it's writing to disk.  The way the tests are spawning child processes is not a very good design, and they should be grouped under a "slow" flag.  Any tests that don't write files to disk should be considered "fast" and suitable for running on any CI.

Agreed.  Thank you.


input-group custom-file-input browse button border-radius

The following markup, as viewed on the documentation, keeps a border-radius on the "browse" button when we have a second button (Bootstrap 4.0.0):

    <input type="file" class="custom-file-input" id="inputGroupFile02">
    Choose file

    Upload

Sample at JSFiddle
Screenshot:

Seen on:

Linux Mint 17.3 Cinnamon (64-bit)
Firefox Quantum 57.0.4 (64-bit)
Google Chrome 63.0.3239.132 (Official Build) (64-bit)
Opera 50.0.2762.58

[ ]

Duplicate of #27002


Modify the link

Change the link of IsDigest to https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.social.socialthreadattributes.aspx
Category

[ x ] Content fix
[ ] New article
Related issues: fixes #2706

What's in this Pull Request?
Change the link of IsDigest to https://msdn.microsoft.com/en-us/library/microsoft.sharepoint.client.social.socialthreadattributes.aspx

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/general-development/reference-threads-and-digest-threads-in-sharepoint-server-social-feeds.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

thx @KingKangMSFT, appreciated.


operator [CI] flux (0.31.3)

Signed-off-by: paulofrazao<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.

Hi @J0zi @mvalarh
We now added @paulofrazao as a maintainer of the Flux operators for OpenShift.

/hold

/unhold

/merge possible

/merge possible

/merge possible


The endpoint used by get_usage_status can only be used from the browser

The usage.jl test is broken:
{
    "error": {
      "message": "Your request to GET /v1/dashboard/billing/subscription must be made with a session key (that is, it can only be made from the browser). You made it with the following key type: secret.",
      "type": "server_error",
      "param": null,
      "code": null
    }
  }

I'm not sure if there's a way to fix this without ripping out get_usage_status

Closing because this issue is sidestepped in 0.8.7: https://github.com/JuliaML/OpenAI.jl/releases/tag/v0.8.7


[IA-3516] Add runtime and storage cost to Analyses tab

Description
Add runtime and storage cost to the CloudEnvironmentModal, Galaxy modal, and as tooltips for the context bar.
Testing
Tested an environment with only a jupyter runtime and persistent disk
Tested an environment with Juptyter and Galaxy runtimes
Tested an environment with Galaxy runtime
Note - the current dev instability makes things a little more difficult. Once the requests succeed, all information appears to be correct.

@tiffanytuffany @n8landolt Is it communicated to users somewhere that the cost rates are estimates and therefore should not be taken as bills?

Might I suggest adding estimate in the tooltip text like so:
This rate reflects the estimated aggregate hourly cost..."

UX approved

few nits, looks good overall

General conversation - do we know that by using the colors object that we'll be compliant for different UIs?

General conversation - do we know that by using the colors object that we'll be compliant for different UIs?

It won't be guaranteed, but your odds will be better. When I've been doing the colors for a white label site, I do check color contrast and adjust as necessary. That being said, I don't know all the places every color is used, so it's possible there are usages that are problematic.

@n8landolt can you let me know when you have addressed @jdcanas's comments so I know when to review? If there are specific things you want me to look at earlier, just tag me on them.

I seem to get into some inconsistent states, especially when switching between tabs and reloading.

Note that when "Azure environment" is showing, I'm actually in a GCP workspace, not an Azure one.

With the latest commit, the information shown in the total cost more accurately represents what is shown in the tooltip for the individual app. Note that it is possible for the disk cost to not return, or the app cost to not return (in which case the app isn't shown at all).

Jupyter creation isn't working at all well, so it's hard to say what is going on in that case. All of these things will hopefully be improved/fixed in future iterations or dev environment fixes.


After creating a new game, return to Save Tool

If a new game is created from the New Project Tool, the Save Tool should be loaded when hitting escape. Right now it loads the New Project Tool since that was the last tool used before creating the game.

This has been fixed.


Env render in CMD

FROM kubernetes:v1.19.8
CMD kubectl apply -f mongo-{{ .version }}.yaml

Then:
sealer run -e version=v1.0 ....

I prefer a way like the ARG command in dockerfile

FROM kubernetes:v1.19.8

ARG MY_ENV="a"
CMD echo $MY_ENV

Then:
sealer run -e MY_ENV=b ....

What if the env is part of a string, like mongo-$VERSION.yaml.  mongo-${VERSION}.yaml is better?

you can support both format


sidecar: Skip reset slave all when initialization.

What type of PR is this?
/bug
Which issue(s) this PR fixes?
Fixes #450
What this PR does?
Summary: Skip reset slave all when initialization.
Special notes for your reviewer?

This PR and Issue are inconsistent.

LGTM.


[Windows] Set application user model ID to prevent editor / running project and different versions of editor taskbar icon stacking.

Set application ID for the editor and project windows to prevent unnecessary taskbar icon stacking.

Thanks!


Added a check to make sure username starts with a letter

Closes: #1
Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py.
Fixes #<issue_number_goes_here>

It's a good idea to open an issue first for discussion.

[x] Tests pass
[ ] Appropriate changes to README are included in PR

@googlebot I signed it!


How to disallow unknown query parameter?

The operation object allows folks to specify parameters, but how can I express that no unnamed parameters may be accepted?
We've had issues where clients are passing in query parameters thinking that they're accepted when actually they are not.
How do folks feel about introducing something like additionalQueryParameters for parameters?
/foo:
  get:
    parameters:
      limit:
        in: query
      offset:
        in: query
    additionalQueryParameters: false
    ...

Then when folks do GET /foo?start=xxx-xxx-xxx they'll get an error instead of a silent failure.
Other links on the web:

https://stackoverflow.com/questions/58187233/is-it-possible-to-disallow-unknown-query-parameters-in-an-openapi-v3-spec
https://github.com/cdimascio/express-openapi-validator/issues/133
https://github.com/opengeospatial/ogcapi-features/issues/128
https://softwareengineering.stackexchange.com/a/311489

This is an excellent question!
Inside a schema the additionalProperties defaults to true as it (loosely in 3.0) based on JSON schema which will unless specified accept additional properties.
Re query params it is an interesting question and seems to vary per implementation. As these are explicitly defined and documented a client should be following the API definition to ensure the type, range, format etc of their request matches what the OAS definition aka "contract" prescribes. You would be well within your rights to return a 400 detailing the unsupported parameter in the same way you would report an out of range.
Where it gets a bit nuanced is interpretations of postels law on being conservative what you send and liberal in what you accept. Its not unusual to see APIs that would accept but disregard anything that is not in the definition silently and this is also acceptable.
Is it something you could cover in the descriptions and overall behaviour of your APIs stating your position and in your level of error verboseness?

Possibly related: #568

This would be a very useful feature to have, as an added help to security. It also helps with the conditions mentioned above, especially where you would consider sending the wrong query variables concerning and you have a large number of paths.

If we moved to representing all in:query parameters as an object described by a single JSON schema, then we would get this functionality 'for free' with the existing additionalProperties keyword.

In my APIs I always default to disallow additional query parameters but I think it would be nice to have this option to explicitly say we do it.
I also made a proposal for the order of the query parameters here: https://github.com/OAI/OpenAPI-Specification/issues/883

This would be very useful. I was looking for this just now.

So where does this put us today.
@savage-alex you make a good point about what we actually should and shouldn't document in our specifications.
Perhaps we should ask, "when would it be desirable to permit undocumented query parameters?"  If we have no good use cases for it, maybe we should by default specify that implementations should reject unknown query parameters in general.

Did someone found a workaround in the meantime that the feature might be integrated ?
Or there is no way to catch unknown query parameter as an error currently ?

Reposting my comments from #3738 here for visibility:
I am wondering how this feature will be used in practice.
I don't think users of the API get any benefit from it. It does not "describe" any useful behavior of the API, unlike additionalProperties which can include a description that explains the meaning of additional properties. It specifies when the operation is required to fail but not when it actually will fail, since undefined query parameters can still cause failures when undefinedQueryParameters is true, the default. So users must be prepared for failures either way.
I suppose this clarifies to implementers how they should treat undefined query parameters, but this assumes that the API description is written by someone other than the team that implements the API, which in my experience is rather rare.
I do understand that, from an API governance perspective, rejecting undefined query parameters is a best practice and failures to do so should be rooted out and corrected. But I don't think adding undefinedQueryParameters helps much on this front -- and could actually hinder it, since it gives implementers an excuse for not following this best practice -- "Well, we didn't document that undefined query parameters must fail, so we don't need to fix our service".
In short, I don't see much practical value in this new keyword and would not recommend it's use in any of the APIs I work with, but if others feel strongly that it is needed I wouldn't oppose it.

I'll note that I've talked to several folks who specifically recommend allowing undefined query parameters due to 3rd-party entities appending them for various purposes (e.g. tracking).  There was a brief discussion about it on the APIs You Won't Hate slack recently.
So that's a use case for allowing, and multiple people have spoken up here over the past two years saying that they would use the disallow.
I'm generally very skeptical of one person saying "I wouldn't use this" and making that an argument for not adding something.  Particularly when multiple people over time have said they would use it.  Why should someone's lack of interest in a feature invalidate the use cases of others?  No one is forced ot use the keyword.

If we moved to representing all in:query parameters as an object described by https://github.com/OAI/OpenAPI-Specification/issues/256#issuecomment-780989715, then we would get this functionality 'for free' with the existing additionalProperties keyword.

This is already possible: with style=query, explode=true, type=object, a single parameter will consume all values in the query string.
This functionality should be documented as an example in the specification, as it is quite useful but not immediately obvious to those unfamiliar with json schema (or those who have written an openapi validator ;) ).
I can see that it may still be useful to have an explicit config for what OP requested, however.

@OAI/tsc review request:  As I've already submitted a PR for this, could we get a decision on whether to support it or not?  If not, I'll drop the PR, if so, we can discuss in the PR whether it is the right way to solve this.

I already weighed in above, but I've been mulling this a bit more and it reminds me of the "Open World vs Closed World" discussion from way back.
https://github.com/OAI/OpenAPI-Specification/issues/568
I thought I'd post that here in case it helps inform the discussion.

@mikekistler yes, very relevant, thanks!
For those who don't want to slog through it (although it's interesting), the resolution of that issue is basically "yes, it's a contract, but it's an open-world contract."  So if an API contradicts something that the description says (or is documented to mean as a default in the absence of a field), then that's an error on the part of either the description or the API.  But if an API does something that is just not addressed by the description, then that's fine.
In this case, additional query parameters are not addressed by the specification, just like (in that linked open world/closed world issue), most API descriptions do not address all possible response codes.  We would not want a "disallow unknown response codes" field, because entities outside of "the API"'s control (e.g. intermediaries) can produce unanticipated response codes.
But the syntax and semantics of the query string are the responsibility of the resource identified by the scheme + authority + path (possibly restricted by scheme-specific rules).  So whether or not additional query parameters can be accepted is within the scope of API design.  It may or may not be a good idea to forbid them (and it poses problems for API evolution), but there may be good reasons to do so.

Like @mikekistler , I also was reminded of the open vs closed world. OpenAPI generally prefers to describe what you can do rather than what you cannot do. If you want to prevent additional parameters, that's a choice you can make in its implementation. Does a consumer need to know that such a thing is expressly disallowed? (They'll find out pretty fast if they just try it.)
So I think the potential benefit here may be for generating backend code or for configuring a gateway to enforce such restrictions? Is adding support in the OAS the best way to accomplish that? [This reminds me of how swagger-node (nee apigee-127) originally had a configuration option for strict validation that would reject requests that contained patterns not described in the description document, IIRC.]

Anyway, I'll typically argue a point for as long as it seems like I might win it.  If the TSC comes to a collective decision to not do this, please just go ahead and close it, no need to convince me first.

@earth2marsh

Does a consumer need to know that such a thing is expressly disallowed? (They'll find out pretty fast if they just try it.)

Isn't the point of documenting our APIs so that the consumer doesn't have to blindly try stuff to understand how the API will respond?
It's useful to the end consumer for constructing valid requests. It's useful for automated testing to ensure the API is behaving as expected.
@mikekistler

It does not "describe" any useful behavior of the API ... It specifies when the operation is required to fail but not when it actually will fail, since undefined query parameters can still cause failures when undefinedQueryParameters is true, the default. So users must be prepared for failures either way.

A condition where the operation is expected to fail is behavior that is useful to describe. I don't think that is contradicted by there being other conditions where failure is possible.
@handrews

I'm generally very skeptical of one person saying "I wouldn't use this" and making that an argument for not adding something. Particularly when multiple people over time have said they would use it.

Agreed.
@karenetheridge

This is already possible: with style=form, explode=true, type=object, a single parameter will consume all values in the query string.
(and then additionalProperties: true or additionalProperties: false can be used).

This is interesting, and may obviate the philosophical questions above. It's been too long since I read RFC6570 to recall for my own understanding if this encompasses the effect of an allowUndefinedQueryParameters, but it looks like it ought to.

I already said above that I won't oppose adding this if others feel there is value in it.
But I wonder ... what does it mean to have additionalQueryParameters: true? What useful information does that give to users? Note that this is very different from additionalProperties: true, which (I think) means that additional properties are strictly allowed and cannot cause a failure.
Also, I don't find this argument convincing:

Isn't the point of documenting our APIs so that the consumer doesn't have to blindly try stuff to understand how the API will respond?

If I documented all the stuff the consumer should need to understand to use the API, do I really need to tell them "Oh and don't try anything else"? Only test programs and hackers try to pass things that are undocumented in hopes of triggering some extra behavior.
But again, if you and others think it adds value in some way, I'm happy to let you do it.

@notEthan I agree with you that documentation potential is one great value of the spec! Today parameter descriptions could be used to handle some of that lifting. For example, if a pair of coordinates is expected to always have both lat and lon; then the description for lat could explain that it:

"Must be accompanied by a lon."

I'm not hard-against this, btw, I am just considering the implications. Inter-dependency implies a bunch of logic checks in tooling that would require work before tooling authors could claim full-support. For example, what would we expect from tools like Swagger UI or Postman when consumers are crafting a request? [I think inter-dependency would at least show some sort of warning if you've created a malformed request (like an onblur check that the other inter-dependent input field had a value).]
If this complexity is worth that investment, we should do it--I'd just prefer it to be obvious that this creates much more value in the world than it costs. It does seem like there is enthusiasm in this thread for such a feature.
This is one of the reasons why we introduced the x-extensions mechanism as a way for the community to demonstrate the idea in practice with tooling. For instance, this could be used to demonstrate the test automation in action.

I posted above about the Open World vs Closed World discussion in this repo. But I just realized that even more relevant is @handrews blog post "JSON Schema is a constraint system" (yes Henry I read it):
https://modern-json-schema.com/json-schema-is-a-constraint-system
The point of that blog post (I think) is that you must approach JSON Schema not as a "definition/description" system but as a "constraint system" -- starting from "anything is possible", JSON schema adds constraints to what is possible. By contrast, definition/descriptions are additive: "You start from nothing and the more you specify, the more you can do."
I have always thought of OpenAPI as a "definition/description" of an API, though admittedly part of it is specified with JSON schema with is the opposite.
But I think the crux of this discussion is: Should OpenAPI be a "definition/description" or a "constraint system"? If we decide that it should be constraint system, then I think we need to acknowledge that it is woefully inadequate.  In addition to constraints on query parameters as this topic is considering, I think we'd also need constraints for:

no additional paths allowed
no additional methods on a path allowed
no additional media types on request or response bodies allowed
no additional response headers
no additional security schemes
no additional OAuth scopes

and there are probably others. Is this really the road we want to start down?

I think you've framed it nicely, and I think this is not the road we want to head down, myself.

I think that the point of that additionalQueryParameters: true proposition is to keep both possible and tell users : 'I designed that API in a closed/open worl point of view.
About that point :

Does a consumer need to know that such a thing is expressly disallowed? (They'll find out pretty fast if they just try it.)

APIs ain't only designed for users but also bots and they may not work at all until a programmer actually fix it.

@mikekistler

But I wonder ... what does it mean to have additionalQueryParameters: true? What useful information does that give to users?

It means exactly what we have now, so I don't understand the question.
Per #3529, minor releases MUST be backwards-compatible, and additionalQueryParameters: true is the default value, so a 3.2 Parameter Object with additionalQueryParamters: true is the same as a 3.2 Parameter Object without additionalQueryParamters at all, which by definition MUST have the same meaning as it does in 3.1.

Note that this is very different from additionalProperties: true, which (I think) means that additional properties are strictly allowed and cannot cause a failure.

That's not really correct.  additionalProperties just takes a schema and applies it to all properties that are not otherwise accounted-for in the same Schema Object.  true and false are just shorthand schemas (for {} and {"not": {}} or any other unsatisfiable schema, respectively.
Within a single Schema Object, there is no difference whatsoever between additionalProperties: true, additionalProperties: {}, and not having additionalProperties at all.  It's still possible for those properties to cause a failure by contradicting other constraints (There is a complex interaction with unevaluatedProperties but that's not relevant here because there is no analogue with the Parameter Object).

@mikekistler

I suppose this clarifies to implementers how they should treat undefined query parameters, but this assumes that the API description is written by someone other than the team that implements the API, which in my experience is rather rare.

I was doing this at IBM for the entire time we worked together... I consider it fundamental to a healthy software engineering organization that this workflow is possible. You also seem to assume that APIs have exactly one implementation, which I find to be an exceedingly strange (and wrong) assumption.
Mike, it seems like you're mostly arguing that we don't need these things because it's incorrect for a service implementation to support things like undefined query parameters, and it's incorrect for client implementations to send extraneous information. But in practice, what you are arguing for is that ambiguity in an API definition is a good thing. I just think that is completely indefensible. Ambiguity is the mortal enemy of quality and robustness.
The reason I think this matters so much is that I think it is exceedingly common for implementations to ignore extraneous/undefined information in a request and exceedingly common for client implementations to depend on this. This is very bad!

But I think the crux of this discussion is: Should OpenAPI be a "definition/description" or a "constraint system"? If we decide that it should be constraint system, then I think we need to acknowledge that it is woefully inadequate.

YES!

@hudlow I've often been the person that writes the description while others (sometimes in a different country/time zone) implement it.  I'd say that's a critically important software style:  Using an OpenAPI Description as a contract with a more junior remote team.

I'm going to bow out of this discussion now. I concede that there is value in having a "constraint system" for HTTP APIs and I'm fine to let OpenAPI be that as long as it does not impede using it for describing APIs, which is my primary use case.

Just to close the loop for those that were not on this week's Moonwalk call, related to @mikekistler constraint system vs description comment:
I emphatically made the point that this is not an either-or thing.  It is a context-specific both-and.
We have JSON Schema as a constraint system, for better or worse, and that's not changing in 3.x.  However, it is only used for request/response bodies and query parameters.  And this particular issue is only about URL query string parameters, which is an important distinction.  In particular, this is not about header parameters.
Headers and response codes (and methods, although we restrict those far beyond what the HTTP spec allows) are defined as open-ended spaces.  The RFCs require that implementations MUST allow unknown values, and specifies how to treat them.  Constraining those spaces with a "no undefined values" would be objectively incorrect.  This is because the API designer does not control what all parties might do with headers and status codes.
Request and response bodies, as well as URLs, are owned by the resource.  It is entirely within the right of the resource to put whatever constraints they want on these things.  Some users think that's a good thing to do, some users think that's a bad thing to do.  We should not care.  It has use cases and more demand (shown by the 7 or so people who have asked for it here) than many other features.
The RFCs grant full control of bodies and URLs to resource owners (who are, in this case, the API description authtors), and our spec should reflect that.

There's a lot I agree with in your post, Henry, but there is still one thing that concerns me. We identified a principle of supporting mechanical upgrades for Moonwalk, so if we continue down this path, mightn't we violate that? (Or else perhaps it means providing some affordance for a constraint system on top of the descriptive/open-world layer?)

@earth2marsh that's a good question, but if we take my solution of implementing #1502, the only thing we are "adding" is an exact analogue of what we already support for request bodies.  It's the exact same syntax, and the exact same process, you just put it in the query string instead of in a single-line request body.
So how could that make Moonwalk upgrades any more difficult?  That is not a rhetorical question, I just don't see where there would be a problem that doesn't already exist.  The upgrade for describing application/x-ww-form-urlencoded should be the same no matter where it goes.  In fact, Moonwalk should be an opportunity to make that more consistent, both philosophically and syntactically.

Actually, I'm pretty sure it makes upgrades easier, because you can already do @karenetheridge 's trick in many situations, so we'd have to upgrade that already.  But we can migrate that trick to the #1502 solution, which then reduces it to a problem we have to solve anyway (form-urlencoded for request bodies).  So it actually provides us with a smoother migration path.  That's another reason to use the #1502 solution instead of the allowUnknownQueryStringParams boolean (which I'm increasingly against).

In today's TDC call, we decided to consider a proposal for #1502, which would solve this without adding new fields.  @earth2marsh keep an eye out for the proposal and we can continue the discussion there - I have already closed the PR I opened specifically for this issue.


Multi-gpu training for YOLO

It's very cool code for chainercv. By the way, are you going to extend multi-gpu training code for YOLO?

#596

Alright, I am still waiting for training script for YOLO....  Well, it's so sad that chainercv do not support any training of YOLO. This issue is for multi-gpu but actually we even can't do single GPU training of YOLO in chained cv (maybe that it's in progress here #596 ).


Remove empty internal constructor

As VortoValue is public, having the constructor as internal means that new VortoValue can't be created.

It's already been made public in this commit 3f61725b51e573047623a025b0aac2944c6da0e9. You'll have to use the build on MyGet though as it's not been released yet.


no need to maintain a gh-pages branch anymore

you can host pages directly from master now.
https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/

@jgravois that's really good to know, thanks! I have tried hosting from master with mixed results. Perhaps the github universe is still churning on some of the files required for the "main" demo in this repo?  It won't (yet) load the src js file for the custom layer nor the data demo csv file.

Update: so for now, I've set it back to work with gh-pages branch.  Feel free to experiment with it if you feel so inclined.

Feel free to experiment with it if you feel so inclined.

i don't have sufficient privileges to change those settings (unless an organization is used, only one owner/admin can be designated).
this isn't crucial.

✋- 5

Follow up: serving from master now seemingly without any problems.


Bug: Circular field dependency results in maximum call stack

This code:
import {
	Schema,
	Query,
	ObjectType,
	Field,
	schemaFactory
} from 'graphql-schema-decorator'

@ObjectType()
class QueryType {
	@Field()
	other(): QueryType {
		return null
	}
}

@Schema()
class SchemaType {
	@Query() query: QueryType
}

schemaFactory(SchemaType)

Results in:
RangeError: Maximum call stack size exceeded

@Cactucs Yap, circular references are still not being handled, sorry about that.
I will this open so that we can tackle after 1.0 is released.

@Cactucs Oh, meanwhile please feel free to send us a PR with a fix suggestion 😉

I've created PR that solves this: https://github.com/indigotech/graphql-schema-decorator/pull/72


How to search column with func.group_concat?

I have a cloumn such as:
ColumnDT(func.group_concat(distinct(Role.name)), global_search=False, mData='roles'),

And search in DataTables not working for this column.
I found while I using having everything is okey.

Is there a way to solve it?

No, that is not supported directly, search input is translated to a where clause. Probably you can work around this by doing a subquery first and then filtering (using where) in the outer query


fix: discrepancy between eth_getTransactionCount RPC values post-Testnet reset

Description
What

Using the same set of EVM accounts (generated from BIP-39 seed phrase) before and after the reset

Why
Dropping down into RPC requests, appears to yields some clues as to why this might be happening:

eth_getTransactionCount(address, 'latest') returns a low number (0 before sending my first transaction after the reset)
eth_getTransactionCount(address, 'pending') returns a high number (140 in my case, which probably was the nonce prior to the reset)

So it is apparent that metamask (correctly) uses the pending value instead of the latest value... but the question is why the pending value seems to be stuck at this value, even after the reset. unknown what the underlying reason it being stuck is - is it caching within Metamask, or caching within RPC relay, or is the value being returned from Hedera nodes?
Steps to reproduce
Before Testnet reset:

in Metamask settings, enable the option for custom nonce
in a DApp client connect using an EVM account (ECDSA with simple key) in MetaMask
trigger something in the DApp that would ask you to sign and submit a transaction
nonce appears correctly
submitting the transaction with the pre-filled nonce value works

After Testnet reset:

in Metamask settings, enable the option for custom nonce
in a DApp client connect using the same EVM account  as before in MetaMask
trigger something in the DApp that would ask you to sign and submit a transaction
nonce appears incorrectly
submitting the transaction with the pre-filled none value does not work, RPC errors saying that the nonce is incorrect
submitting the transaction after overriding the pre-filled nonce value with the known-to-be-correct value (obtain this using eth_getTransactionCount(address, 'latest') works

Additional context
No response
Hedera network
testnet
Version
0.41.0-SNAPSHOT c288615a33e08dfa172df7754aa764bad12eeb71
Operating system
macOS

I was able to experience the issue with MM, but indeed is the nonce you had previous to the reset, seems  like MM is using a cache out of its history.
You need to clear your data, go to:
Settings --> Advanced --> Clear activity tab data.

I have done many combinations of tests and I haven't been able to replicate the issue afterward
This will solve your issue

thanks - that worked!


Autowithdrawl to lightning address

Basically allow lightning addressed people to autowithdrawl their account balance from SN.
This could work a number of ways, but we probably want it to leave some sats in wallet. Options:
A. conditionally, e.g. withdrawal anything over 12k sats, leaving 10k sats, and paying a max fee of 50 sats
B. unconditionally, e.g. always attempt to withdrawal any balance, even if it's just 1 sat, paying a max fee of 10 sats
C? direct funding, e.g. don't hold my sats at all and zap me directly
C is probably a little wacky to do if we want to take our zap sybil fee, but we might be able to cook up something with hold invoices. It's also unclear what to do on failure.

C? direct funding, e.g. don't hold my sats at all and zap me directly
C is probably a little wacky to do if we want to take our zap sybil fee

Maybe we could use routing hints? As if the user uses a private channel with us. Then we could take our zap synbil fee as a routing fee

If routing hints can specify a fee explicitly then that would work.

The elements contained in the field r are commonly referred to as routing hints. They allow the receiver to communicate an extra set of edges that may help the sender complete their payment. The hints are usually used when the receiver has some/all private channels, and they wish to guide the sender into this "unmapped" portion of the channel graph. A routing hint encodes effectively the same information that a normal channel_update message does. The update is itself packed into a single value with the following fields:
The pubkey of the outgoing node in the edge (264 bits)
The short_channel_id of the "virtual" edge (64 bits)
The base fee (fee_base_msat) of the edge (32 bits)
The proportional fee (fee_proportional_millionths) (32 bits)
The CLTV expiry delta (cltv_expiry_delta) (16 bits)
The final portion of the data segment is the set of feature bits that communicate to the sender the functionality needed to complete a payment. As an example, if a new payment type is added in the future that isn’t backward compatible with the original payment type, then the receiver can set a required feature bit to communicate that the payer needs to understand that feature to complete the payment.

-- Mastering the Lightning Network, Chapter 15
So I believe this could work.
However, there is one problem:
The receiver has to add the routing hints since they create the invoice. Since I am not aware of any wallet that supports configuring routing hints - that's also how wallet companies like Muun and ACINQ make their money afaik so it's probably actually against their interests -, this autowithdrawal feature would only work with routing hints if the stackers have full control over their nodes and good knowledge to use "advanced" features like configuring routing hints.
But assuming they added the routing hints with the appropriate proportional fee, the payment would route through us and, we could take the sybil fee as a routing fee.
The flow could be like this:

A wants to zap B 1 sat on SN for a good meme
SN requests invoice from B's node
SN verifies invoice includes routing hints including fees
we show that invoice to A
A pays
Payment routes through us and we take the sybil fee
B receives payment
We can show the payment on SN (since we were paid our fee)

Another downside may be that B needs to have a channel open with us. But I am not 100% sure on that. Maybe routing hints can just be used as a pit stop? So A would need  to find a route to SN and we would need to find a route to B. Which is naturally way easier if B has a channel with us.

This would require us setting these fees statically on some number of channels right?
What if we wrapped the receivers invoice in a hold invoice with our own hints that go through our node?

This would require us setting these fees statically on some number of channels right?

Mhh, I believed the fee in the routing hint is independent of fees configured per channel. As I understood it, the routing hint is like announcing a channel just for this invoice so you can set any fee.
But yes, the existing static channel fees may make things more complicated.

What if we wrapped the receivers invoice in a hold invoice with our own hints that go through our node?

So A would pay us and then we would pay B? Settling the invoice with A when the payment to B was successful and else cancelling it?
That sounds really promising, I like that!

I guess we'd need to determine if a hint is just a hint or a requirement.

So A would pay us and then we would pay B? Settling the invoice with A when the payment to B was successful and else cancelling it?

What I'm thinking is something exactly like https://lnproxy.org/ which manages to take an arbitrary fee by "wrapping" the original invoice in a hold invoice to itself.

The route hints won't force the sender to route through you. It's just including additional hops that might not be on the graph.
The wrapped invoice method would work, but you have to be absolutely sure you won't lose money doing it.

The route hints won't force the sender to route through you. It's just including additional hops that might not be on the graph.
The wrapped invoice method would work, but you have to be absolutely sure you won't lose money doing it.

The route hints won't force the sender to route through you. It's just including additional hops that might not be on the graph.
The wrapped invoice method would work, but you have to be absolutely sure you won't lose money doing it.

Ahh, makes sense. Thanks for clarifying it!

The wrapped invoice method would work, but you have to be absolutely sure you won't lose money doing it.

I suspect the concern here is outgoing route to the receiver could fee-jack you. We'd probably want the receiver to tell us how much they're willing to pay in fees upfront and take those fees unconditionally and failing the payment if a route can't be found <= the set fee.

Aside from failure UX (which is definitely tractable), the only other hard part to the hold invoice method is we now have to get really serious about managing liquidity and connectedness.

The concern is you're glueing multiple payments together. I'd highly advise not doing this if you're unsure of how you'd lose money by doing such a thing.

You're right, I haven't studied the money losing scenarios when "gluing multiple payments together." I'm top of dome discussing this.
afaik money loss would happen on the route outgoing to the final receiver. If you're implying there are other, less obvious ways, then we'll do our best to find them before implementing.

Yes, the money being received by the final recipient but you being unable to redeem the payment made to you. But I guess it also depends on if you actually want to implement the same payment hash in the wrapped invoice, that would make it trustless. However, naively you can implement it without invoice wrapping and just normal invoices that you always have the preimage to so you can redeem at any time if needed.
The problems mostly come with making sure your program can always settle the payment under these scenarios and more:

Restarts (service or lnd)
Internet disconnections
Stuck payments on the 2nd part
Make sure the 2nd timelock is always longer than the first, long enough for you to manually settle issues

You never want one side to settle without the other, and you're not in control of when the final recipient settles it, only the max amount of time when they can settle it.

That's very helpful thank you! (I wish there were zaps on github.)
It sounds like the problems are a near 1-to-1 map of all the problems lightning nodes solve on a normal route and because we're getting in-between that we'll have to re-solve all those issues.


Bump Node Version and Increase Timeout

Task linked: FRI-416 Update Create Frigg App Template: Bump Node Version and Increase Timeout


feat(disploy): message components (#53)

Support message components within Disploy.

This is a collaborative pull request, we would love to see you contribute to the feat/message-components branch!

Todo

[ ] Modal structure
[ ] Action-row structure
[ ] Button structure
[ ] Select-menu structure
[ ] Handle modals in the router
[ ] Handle buttons in the router

The more suggestions; the more todo items that will be added.

The buttons pull request https://github.com/Disploy/disploy/pull/68 implemented message component handlers, routing and more. However, it doesn't include Button structures or action rows, only supporting raw JSON.
This pull request implemented this, but it's now too stale and outdated for the new changes. We should look at the goals of  this pull request and implement them separately later.


Began detailing README

Created images directory in /docs and added the SSPINN_Logo.png.
Logo is still too big, but I will resize that in the next commit
There is still a lot missing from main README - mostly looking for feedback on what else is important to add and what is incorrect in this version.
Will remove the jup. notebook used for drafting in the next commit.

Pull Request Test Coverage Report for Build 105

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 56.642%

Totals

Change from base Build 104:
0.0%

Covered Lines:
226

Relevant Lines:
399

💛  - Coveralls


Add development environment notes recommending rbenv

This came up helping Ben with his setup at Code for Boston.

Thanks @bw120!


Unable to connect using ssh to a function app locally using az cli

This is autogenerated. Please review and update as needed.
Describe the bug
Unable to connect using ssh to a function app locally using az cli
Command Name
az webapp ssh
Errors:
The command failed with an unexpected error. Here is the traceback:
'str' object has no attribute 'value'
Traceback (most recent call last):
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/knack/cli.py", line 231, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 657, in execute
    raise ex
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 712, in _run_job
    return cmd_copy.exception_handler(ex)
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/azure/cli/command_modules/appservice/commands.py", line 37, in _ex_handler
    raise ex
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 691, in _run_job
    result = cmd_copy(params)
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/__init__.py", line 328, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/azure/cli/core/commands/command_operation.py", line 121, in handler
    return op(**command_args)
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/azure/cli/command_modules/appservice/custom.py", line 4321, in ssh_webapp
    create_tunnel_and_session(
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/azure/cli/command_modules/appservice/custom.py", line 4035, in create_tunnel_and_session
    tunnel_server = get_tunnel(cmd, resource_group_name, name, port, slot, instance)
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/azure/cli/command_modules/appservice/custom.py", line 3977, in get_tunnel
    webapp = show_webapp(cmd, resource_group_name, name, slot)
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/azure/cli/command_modules/appservice/custom.py", line 605, in show_webapp
    return _show_app(cmd, resource_group_name, name, "webapp", slot)
  File "/usr/local/Cellar/azure-cli/2.30.0/libexec/lib/python3.9/site-packages/azure/cli/command_modules/appservice/custom.py", line 734, in _show_app
    "Unable to find {} '{}', in RG '{}'".format(cmd_app_type.value, name, resource_group_name),
AttributeError: 'str' object has no attribute 'value'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

az login
az webapp ssh -n {} -g {} --subscription {} where the name and group is for a function app

Expected Behavior
setup local ssh gateway to remote function app
Environment Summary
macOS-12.0.1-x86_64-i386-64bit, Darwin 21.1.0
Python 3.9.7
Installer: HOMEBREW

azure-cli 2.30.0

Additional Context

route to service team

Could be related to #19903.

I can confirm this is fixed now.


Incorporated S grade and Additional Courses

Both S grade courses and Additional courses are displayed in the course list, and counted towards total credits completed, but aren't considered in the CGPA calculation

Also, more of a general note. The indentation seems to have been affected by whatever formatter you're using, so this PR will have to be put on hold until #18 is solved.

@dark-trojan, your formatter seems to have changed the indentation all over the place. This usually causes problems with git blame and causes headaches with merge conflicts when we try to merge other PRs.

@dark-trojan, we have formatted our code. Could you redo this PR as discussed whenever you are free? Sorry for the inconvenience.
PS. Take care about the formatting this time.


Add NixOS to WSL Linux distros

Hey,
would like to see NixOS provided as a distribution for WSL.
It is already working fine by using https://github.com/nix-community/NixOS-WSL
If it's possible to publish it on Microsoft Store, I'm willing to help out.
Downstream issue: https://github.com/nix-community/NixOS-WSL/issues/63
Best regards
Jonas

Commented on the upstream issue, but I'm happy to help.


Configs for import are greyed out

Preparation

[X] I tested the latest release
[X] I looked at other issues (even the closed ones)
[X] I read the Troubleshooting Guide

FGO server
NA
FGA build number
1856
Describe the bug
All configs are gray and unselectable, select all is not working too. File manager have the permissions, FGA does not ask for them.
Tried on LDPlayer 9.0.27 and LDPLayer 4.0.83, same story

Video
https://user-images.githubusercontent.com/9951646/199855538-b85e8e25-0f75-4731-aae7-65ca28d3ecbd.mp4
Device model
LDPlayer
Android version
9
Screen size
1920x1080
RAM
4

I believe you have to rename the file extension to .json

I believe you have to rename the file extension to .json
JSON are greyed out too

https://github.com/Fate-Grand-Automata/FGA/issues/1338#issuecomment-1263982570
Guess you have to manually input them again

Try .fga.json file extensions. Works on my phone.

Try .fga.json file extensions. Works on my phone.

Nah, they're still greyed out

It's also grayed out for me on both emulator and my phone. Renaming doesn't fix it on either.

Was able to reproduce it on an emulator, working on it.

Should work with build 1888.


Repo sync for protected CLA branch

The pull request is created from master637732873677613429 to master to fix git push error for protected CLA branch

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


The future of botogram

Don't worry, botogram is not going to go away, this is about extending it!
Currently, botogram is strictly tied to the Telegram bots API. There is no problem with that, I started botogram with Telegram as the only target and I'm not going to leave it anytime soon. The thing is, the bots landscape is rapidly mutating, and more and more platform are adopting some kinds of API. Other than that, I want to avoid to lock everything into one single platform, because in the remote eventuality Telegram turns evil I don't want to see all this work wasted.
The thing I'm thinking about now is turning botogram into a more generic framework for bots, while keeping the same API. Fortunately, most of the logic of botogram is actually detached from the Telegram API, so it's simple to call an abstraction layer instead of the API directly.
I think this is the way to go, in order to embrace more platforms and guarantee a future for botogram even if Telegram slows down. But any opinion is highly appreciated!

Hi Pietro.
Making botogram a generic framework makes sense. What other available platforms do you have in mind? Are you aware of any others that are more open than Telegram's at this time?
In the near term, I see new platforms being targeted toward business, with their APIs being at least somewhat subscription driven and more 'locked down'. This is of course not a reason not to support them via botogram, though I cannot see moving from Telegram unless some key component critical to a bot's working/purpose is only available via another platform. In this case, the only things I can think of would be some kind of business intelligence agent (think IBM Watson, Cortana, etc), better/easier integration with other 'wares owned by another platform, or simply the platform reach is greater (more people utilize it). The open API landscape already greatly helps with the first two, and allows you to stay with Telegram.
In any case, I am happy there are more platforms arriving. They will force each other to add more and better features, and hopefully keep each other honest. That said, it's simply good software development to abstract away Telegram's API, and I think you've done a nice job with that already.
If it were me, I would continue on to 1.0 and make a solid Telegram framework that's already in good shape to be generalized and supportive of multiple frameworks.
Brad

Making botogram a generic framework makes sense. What other available platforms do you have in mind? Are you aware of any others that are more open than Telegram's at this time?

I'm looking around at the other APIs out there, but I want to abstract the framework even if Telegram is the only decent one, because I don't want to be locked in a platform.

This is of course not a reason not to support them via botogram, though I cannot see moving from Telegram unless some key component critical to a bot's working/purpose is only available via another platform.

But the thing this will allow you to do is something like:
bot.add_provider("telegram", "122324:slkdnlflkzsbdflkblkfakbjkas")
bot.add_provider("slack", "their_api_key")

The botogram structure allows right now to have multiple processes fetching updates from the upstream server, and having them connecting to different providers isn't that difficult. So, you will be able to have support to multiple platforms in the same instance of your bot (if you're not using APIs available only in one of the platforms).

If it were me, I would continue on to 1.0 and make a solid Telegram framework that's already in good shape to be generalized and supportive of multiple frameworks.

I don't plan to add other drivers right away (I prefer implement the Telegram API in a good way), but doing that post-1.0 will be much harder than currently.

I don't think I will ever do this.


autoreset should work without mode "one-shot"

Hello there,
I am new to rive.
Currently, I am having an issue when running the program. Can you please guide me.
[Attached the screenshot]


fix(versions): update Activiti/activiti-cloud-full-chart-security versions

UpdateBot pushed helm dependency: activiti-cloud-full-example to: 7.1.149

UpdateBot commands:
updatebot push-version --kind helm activiti-cloud-full-example 7.1.149


update.sh: improve verbose output and readability.

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

Would have made it easier to debug https://github.com/Homebrew/homebrew-core/issues/2804 where wasn't clear which directory was causing the issue.

While I'm generally in favor of this PR, I think in its current state it might contribute to the confusion when output related to <repo2> will appear under a heading that suggests it's still operating on <repo1>. It would be really nice if all verbose Git output related to a given directory/repository was grouped under a common heading that indicates this directory/repository.
To address this, I'd suggest to either move the added verbose output to the very top of the pull function or to add additional verbose output there. (Something like Updating $DIR ... will probably do.)
(I once proposed something similar in Homebrew/legacy-homebrew#49905 but I guess it had a bad start as it was originally disabling parallelization—for the sake of clearer debug output—and then was blocked by discussion about the structure of the output and implementation details of ohai et al. in Bash, that I also made part of the PR. Just wanted to mention this for some context and prior discussion.)

@UniqMartin Take a look now; have changed the approach somewhat.

Thanks for making this change; I'm a lot happier with the output! In fact I'm :+1: on the change as-is. (There's one suggestion in a code comment you might want to integrate beforehand.)


How to run the matlab code mainTeX.m (lacking of data?)

Hi: Fanglin When I was running the code  mainTeX.m to myTeX.loadHSI() to load hyperspectral imaging heatcube, there were something wrong that is lacking the data '._wn.mat'. This file is not provided in the dataset. How can I get the '_wn.mat' data? Thanks.

Hi jackygsb,
The 'wn.mat' file was given outside the code package folder and was given in the HADAR database, see the 'wavenumber*.mat' files.
Please copy and paste one of them into your working directory and rename it as needed.
Thanks


Latest change 2.4.14 causes following code to stop working with res pet

/cast [nopet,nodead] Call Pet 2; [@pet,dead] Revive Pet

Duplicate of #574


How can i draw a marker in the earth

Need same

I wrote a plugin which can solve your problem: https://pub.dev/packages/scenekit_plugin

No description provided.

I wrote a plugin which can solve your problem: https://pub.dev/packages/scenekit_plugin


Adding a back to top button as a feature

I wanted to add button for back to top as the webpage can be little too long to scroll again and again

@maitri-vv yeah,Sure

Fixed


Trusted Senders

"Microsoft subscribes to third-party sources of trusted senders."
Can we get visibility on the trusted senders and third parties so we know if this is applicable to our tenant?

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

ID: 3094559e-4d03-8f6d-a620-a3f61ec33184
Version Independent ID: d352d9b3-3d96-402b-c20e-df677b3e9d60
Content: Configure the connection filter policy, Allow list, Block list - Office 365
Content Source: microsoft-365/security/office-365-security/configure-the-connection-filter-policy.md
Service: o365-seccomp
GitHub Login: @MSFTTracyP
Microsoft Alias: tracyp

@sysadmin-scs - Thank you for engaging with the community here for the docs.
I know the product teams are always looking for user feedback and feature requests on how to make Microsoft 365 better. They keep a close tab on user feedback and it would be awesome if you could add your voice in UserVoice.
You might find others have made a similar request that you can add to, or you can open a new one. Let us know here if you do so we can up-vote your request.
Thank you for your contribution to make the docs better! Much appreciated!


CI: Harfbuzz doesn't work on CI

It seems the version is too old for the bindings.

On CI, version is 2.6.4. On my Ubuntu 22.04 it's 2.7.4.

On Windows I had same issue, and worked when replaced dlls in pharo-vm by the ones in this zip:
https://github.com/harfbuzz/harfbuzz/releases/download/5.2.0/harfbuzz-win64-5.2.0.zip

We were working with Pablo to create new Pharo VMs with the required libs

Now it works (with the new VM)! tested on ubuntu but should be the same on other platforms.
thanks @tesonep !!
Reported in the log:
Main graphic library versions
-----------------------------
Cairo: 		1.17.4 	/home/runner/.smalltalkCI/_cache/vms/Pharo64-11/pharo-vm/lib/libcairo.so.2
Freetype: 	2.12.1 	/home/runner/.smalltalkCI/_cache/vms/Pharo64-11/pharo-vm/lib/libfreetype.so.6
Harfbuzz: 	5.3.1 	/home/runner/.smalltalkCI/_cache/vms/Pharo64-11/pharo-vm/lib/libharfbuzz.so.0
SDL: 		2.24.1 	SDL2


fix: token ID in the query higher than the number of tokens in the index

When I used a customized tokenizer, the vocab is saved by retriever into vocab.index.json under the format of, for example:
{"0": 0, "1": 1, "2": 2, "3": 3, "4": 4, "5": 5, "6": 6, "7": 7, "8": 8, "9": 9, "10": 10, "11": 11}

when i retrieve by ids of query tokens like results, scores = reloaded_retriever.retrieve(query_tokens, corpus=titles, k=2) it led to an error when we query in a different corpus
File "env\Lib\site-packages\bm25s_init_.py", line 486, in get_scores_from_ids
raise ValueError(
ValueError: The maximum token ID in the query (12) is higher than the number of tokens in the index.This likely means that the query contains tokens that are not in the index.

In function retrieve of class BM25 in bm25s_init_.py, the retriever load the vocab this way:
# if it's a list of list of tokens ids (int), we remove any integer not in the vocab_dict
if is_list_of_list_of_type(query_tokens, type_=int):
    query_tokens_filtered = []
    for query in query_tokens:
        query_filtered = [
            token_id for token_id in query if token_id in self.vocab_dict
        ]
        if len(query_filtered) == 0:
            if "" not in self.vocab_dict:
                self.vocab_dict[""] = max(self.vocab_dict.values()) + 1
            query_filtered = [self.vocab_dict[""]]

        query_tokens_filtered.append(query_filtered)

    query_tokens = query_tokens_filtered

I think a quick fix is add .values in the query_filtered and it work:
query_filtered = [
    token_id for token_id in query if token_id in self.vocab_dict.values()
]

Thanks for the PR.
See my comment here: https://github.com/xhluca/bm25s/issues/91#issuecomment-2546236988
Could you also add a test file with the following scenarios?
default tokenizer -> no error
default tokenizer -> error
custom tokenizer -> error
custom tokenizer -> no error


Mapping of Google "address components" to "address format"

Hey,
do you have further data on how to map the single address_components coming from the Google Geocoding API to the address formats?
The pretty simple example question would be which comes first in the address line 1, [Street] [Number] or [Number] [Street], the former i.e. US, the latter in Germany.
I cannot find any useful mapping data for this.

Their API should also return the address formatted with micro-format
markup, no? That will have the street name and number in the right order,
and can be easily extracted to the street number field as is from the
relevant span if you want to use it to populate the widget.

jan. 2017 2.44 p.m. skrev "Christian Adamski"<EMAIL_ADDRESS>

:

Hey,
do you have further data on how to map the single address_components
coming from the Google Geocoding API to the address formats?
The pretty simple example question would be which comes first in the
address line 1, [Street] [Number] or [Number] [Street], the former i.e. US,
the latter in Germany.
I cannot find any useful mapping data for this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/googlei18n/libaddressinput/issues/119, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AIjis96KdueVkC6LW4fMZLNc0otSFBt0ks5rV1HUgaJpZM4Ltf79
.

The issue might more complex than that. I'm maintaining the geolocation Drupal module, which allows to interact with the address Drupal module, which in turn is based on this data.
And now people come and tell me that in NYC the locality is not the city, but the neighborhood field, or that in Argentina the adminstrative area must be filled with something else etc.
Google in all these cases gives the correct formatted string, but I cannot find any mapping data from the single components to that formatted string.

I will look at your idea.later though, maybe it works out. Thanks so far

@lararennie I just checked: no micro-format from Google Geocoding. It's a plain string.

https://developers.google.com/places/web-service/details shows adr_address
with:
48 Pirrama Rd,
Pyrmont
NSW
2009,
Australia
2017-01-26 16:24 GMT+01:00 Christian Adamski<EMAIL_ADDRESS>
@lararennie https://github.com/lararennie I just checked: no
micro-format from Google Geocoding. It's a plain string.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/googlei18n/libaddressinput/issues/119#issuecomment-275416048,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIjisxJjNqsM3_8ZXbh2f_SEuMuztnI9ks5rWLqsgaJpZM4Ltf79
.

@lararennie thanks for your replay. That is the places API though, which is distinct from the basic geocoding API

I'm also thinking about related issues How to know which component corresponds to

i am facing a similar issue, i would also like to use the adr_address, but it is not available in the geocoding API @ChristianAdamski or @crazyshakalaka have you guys found a solution

I started to map this out manually :(
https://git.drupalcode.org/project/geolocation/-/tree/8.x-3.x/modules/geolocation_google_maps/src/Plugin/geolocation/GeocoderCountryFormatting
Similarly for OSM / Nominatim & Photon:
https://git.drupalcode.org/project/geolocation/-/tree/8.x-3.x/modules/geolocation_leaflet/src/Plugin/geolocation/GeocoderCountryFormatting


[Abort Controller] Investigate the role of arguments

Investigate the issue raised here: https://github.com/Azure/azure-sdk-for-js/pull/11269/files#r489043950.

I believe the related code has been removed in abort-controller v2.