Search Management Service ID missing

The search service returns the following response object:
type ServiceResource struct {
	autorest.Response `json:"-"`
	Name              *string                    `json:"name,omitempty"`
	Location          *string                    `json:"location,omitempty"`
	Tags              *map[string]*string        `json:"tags,omitempty"`
	Properties        *ServiceReadableProperties `json:"properties,omitempty"`
}

This doesn't follow the normal convention of having the ID as part of the response. The documentation suggests the ID will be part of the return:
{
   "id": "/subscriptions/[subscriptionId]/resourceGroups/[resourceGroupName]/providers/Microsoft.Search/searchServices/[serviceName]",
      "name": "service name",
      "location": "service geo region",
      "type": " Microsoft.Search/searchServices",
      "tags": {
         "key": "value",
         . . .
         },
       "sku": {
            "name": "free | standard | standard2"
         },
      "properties": {
		           	"replicaCount": 1 - 12,
			           "partitionCount": 1 | 2 | 3 | 4 | 6 | 12
              "status": "running | provisioning | deleting | degraded | disabled | error",
              "statusDetails": "details of the status",
              "provisioningState": "succeeded | provisioning | failed"
       }
}

I believe this may be due to the missing ID in this part of the Swagger definition:
https://github.com/Azure/azure-rest-api-specs/blob/master/arm-search/2015-02-28/swagger/search.json#L380
IF this is the case, then I will open a PR to add it

@stack72 Yup, that'd be the reason. Opening a PR would help. Thanks.

@brendandixon I will open a PR as soon as I find an example of a swagger doc with an ID :)

@stack72 Look at this line https://github.com/Azure/azure-rest-api-specs/blob/master/arm-search/2015-02-28/swagger/search.json#L421. I believe that is what's missing.

@brendandixon thanks :) https://github.com/Azure/azure-rest-api-specs/pull/120

@stack72 -- Very cool that you're working on a Go client for Azure Search. However, please keep the change in your own fork for now. We are using this Swagger spec for generating a C# pseudo-client that we use for testing the Azure Search .NET SDK, and as you can see, it's not ready for prime time. Changing this spec will likely break our tests.

@brjohnstmsft I'm confused. If the API returns this field, why are you not interested in taking this change? The Swagger specs are used by other Azure teams as well - it's important that they reflect the actual live service.
Either the REST documents should be updated, or the Swagger spec should be, No?

@colemickens It depends. Is the purpose of these Swagger specs to exactly capture Azure APIs, or is it to provide a model from which to generate high-quality client libraries? Sometimes these goals are in conflict. In this case, we (the Azure Search team) chose to omit ID since it didn't seem like it would serve a useful purpose in the client library (name is used as a unique identifier for resources everywhere in ARM, not ID). This decision was completely academic at the time we made it, because we didn't (and still don't) ship a management client library for Azure Search. Right now we use this spec to generate some C# stubs that we use to test our data plane .NET SDK.
@stack72 Can you tell me a bit more about your scenario? What are you using this spec for, and in what situations do you need the ID?
If we decide that adding ID is the right thing to do, I'd be happy to take the change, as long as we make sure that re-generating the code in this project doesn't break the Azure Search SDK tests.

The Swagger spec intentionally doesn't describe the service accurately because you're using the Swagger spec to generate some test code? I'm not sure I understand how making the Swagger spec accurate could have any impact on tests, or rather, why tests would rely on something so fragile as "whether or not a field named id is surfaced in the object that is created".
An API that doesn't return an id field doesn't feel much like a REST API, to me. Azure already differs from what I perceive as mainstream REST, in that we don't have any sort of "link" fields on our resources or lists. Going further and removing what we do have (virtually the same thing in the id field), makes me feel we're even further from REST conventions.
In a more general sense, I just don't see why we would intentionally drop data from the response that was deemed necessary information when the API was created -- the ARM endpoints don't return it for no reason. As far as I can tell from looking at azure-sdk-for-go, the search service would be the one of only  specs to not surface the id field. And including this value doesn't make the generated client any harder to use.

(name is used as a unique identifier for resources everywhere in ARM, not ID).

I also am very confused by this statement. In ARM, the information in the id field is a superset of the information in the name field. This is an identifier in the ARM world.: /subscriptions/[subscriptionId]/resourceGroups/[resourceGroupName]/providers/Microsoft.Search/searchServices/[serviceName]" while [serviceName] is not. Imagine if the user wants to take the "SearchService" object returned and persist it and restore it later. They'll never be able to get back to that resource with only the data returned by the code-gen'd client. But if it were the actual response from the service, the resource's full identity would be included.
Another reason: I don't know that much about SearchService, but in the networking stack, you have to create links between resources to create logical relationship. When creating those relationships, the ARM APIs require the full qualified ID... because it's the only way to unique identify the resource. This is another place where I should be able to just use the ID that was returned from my prior POST.
Finaly, I can't speak for @stack72, but at the very least, a number of other Azure SDKs are generated from the Swagger specs, which is why I'm interested in seeing them as accurate as possible. I would argue that any unfriendliness that results from an accurate Swagger specification indicates an unfriendliness in the API call itself, not the client. And I would like to see those fixed on the API side, rather than on the caller since not everyone is lucky enough to be using a generated, supported client. We already give outsiders to the Azure/ARM/AD ecosystem enough pain points.

Let's unpack this, because we're starting to cover a lot of ground.
First off, thanks for the examples of practical usage of the ID field in the networking stack. I also buy the consistency argument, so in this case I agree we should add ID. My bad for having the PR closed before we had a chance to have this discussion. @stack72 , I'll have it re-opened and merged tomorrow (can't do it myself because I don't have write access to azure-rest-api-specs).
That said, there are many more problems with this particular Swagger spec than the missing ID field. I left it in a half-finished state many months ago because it was good enough for my purposes at the time. This is actually the first I've heard of anyone taking a dependency on this spec outside of the Azure Search team. I hadn't intended to revisit this particular spec for a while because shipping a management client is pretty low on our priority list (not many customers ask for it because most get by with ARM templates and our data plane client is way more important to our customers).
If other contributors want to finish adding all the missing features and fixing the idiosyncrasies of the arm-search spec, I'm happy to take those changes, but there are a couple things I think we need to figure out first:

Who is responsible for making sure that all downstream dependencies on the spec don't break? In the case of this PR there is likely no impact, but someone still has to re-run AutoRest to regenerate the C# code in azure-sdk-for-net and make sure everything still works. It's not a lot of work for this change, so to make things simple I'll do that this time. But in general, who takes this work? A contributor changing the spec won't necessarily be familiar with all the other languages and SDK projects.
If the service team (Azure Search) isn't responsible for creating a particular client like the Go client, then who is going to support it? Document it (not just references, but how-to articles on azure.com)? Keep it up-to-date as the REST API changes? AutoRest only gives you code and reference docs, not a complete product, so what exactly is the endgame for this client?

thanks @brjohnstmsft and @colemickens - FWIW, not having the ID actually breaks the convention so it's good to have this agreed on :)
Look forward to the merge coming!
P.

@brjohnstmsft I believe these is a misunderstanding regarding the Swagger. It must define the public API correctly, including all accepted and returned data. It cannot arbitrarily omit fields since that will, by definition, create code that breaks the API.

@stack72, your PR has been merged. Sorry for the delay while we sorted this out.
@brendandixon Let's follow up offline on the question of the role of service teams in this spec work.

One final comment: In the future, let's try to keep issues related to Swagger specs filed in the azure-rest-api-specs repo. I missed this thread because I wasn't watching this repo (I am now). Thanks.

@brjohnstmsft Agreed. Simple oversight this time.

Closing this - have written our own implementation to allow us to proceed


records: introduce unified wayback URL argument

After previous ticket #1990 to expose historical versions of records is
implemented, one can expose historical versions of records easily via:
/record/18/export/xm?revision=REVID
/record/18?of=xm&revision=REVID

The historical versions of records' documents are exposed differently,
via version argument:
/record/18/files/thesis.pdf?version=2

It would be useful to have a unique way of referring to past versions
of resources handled by the digital library, be they records or
documents (or other related information like discussion).
This could be done by introducing a new wayback URL argument that
would bring, as best as possible, the past version of a resource:
/record/18/export/xm?wayback=YYYYMMDDhhmmss
/record/18/files/thesis.pdf?wayback=YYYYMMDDhhmmss

The URLs would be internally translated to ones using revision (for
record metadata) and version (for file) and corresponding functions
would be called before serving the results.  So the wayback layer
could be relatively thin.
However, it may be suitable to extend this to other resources, such as
HTML detailed formats or XML reference list or even discussion
threads:
/record/18/?wayback=YYYYMMDDhhmmss
/record/18/references?wayback=YYYYMMDDhhmmss
/record/18/discussion?wayback=YYYYMMDDhhmmss

One possibility would be to create a new wayback module with a
waybackify daemon that would run in the background and go through
resources decorated with @waybackify (or defined in some
configuration variable) and take historical snapshots of results into
history store.  The serving part would then look in this wayback store
and serve what is available for given time snapshot.
(This would be useful for future Memento RFC 7089 support.)

Memento protocol has been implemented in Invenio-Records-REST.


Add end-to-end test for alerts_gcs

Goal
end-to-end test for alerts_gcs script
Toward #9
What I changed

The test uses the a GCS emulator that runs in a Docker container. Thus I:

install tox-docker and configure the emulator in tox.ini
refactor to create a _main() method that allows injecting an already instantiated GCS Client.

New pytest.fixture mock_alerts_storage_client that pre-populates the emulated storage with files (binary and text) of mock alerts.  These files are stored in f/frizzle/alerts/tests/assets/

As with all frizzle data flows' tests, I've added it as a new tox.ini "environment"

I will need to take a deeper look why CircleCI is failing this.  Tests pass locally, but I could imagine the new tox-docker addition is not what CI is expecting.


Tests: add tests for pkg/envoy/ads stream aggregated resources.

Please describe the Improvement and/or Feature Request

Add test cases for pkg/envoy/ads Server.StreamAggregatedResources(). It is completely not covered.

Scope (please mark with X where applicable)

New Functionality          [ ]
Install                    [ ]
SMI Traffic Access Policy  [ ]
SMI Traffic Specs Policy   [ ]
SMI Traffic Split Policy   [ ]
Permissive Traffic Policy  [ ]
Ingress                    [ ]
Egress                     [ ]
Envoy Control Plane        [ ]
CLI Tool                   [ ]
Metrics                    [ ]
Certificate Management     [ ]
Sidecar Injection          [ ]
Logging                    [ ]
Debugging                  [ ]
Tests                      [x]
CI System                  [ ]
Demo                       [ ]
Project Release            [ ]

Possible use cases

Ref #1489

Reference to my comment here: https://github.com/openservicemesh/osm/pull/3515#issuecomment-875058594


[fix][sec] Go Functions security updates

Fixes #21819 #21820 #21821 #21822 #21823 #21824

Main Issue: #xyz

PIP: #xyz

Motivation

Modifications
Updating Go dependencies for Pulsar functions
Verifying this change

[ ] Make sure that the change passes the CI checks.

(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (10MB)
Extended integration test for recovery after broker failure

Does this pull request potentially affect one of the following parts:

If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] The metrics
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Matching PR in forked repository
PR in forked repository:

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

Comparison is base (1a4a9d9) 73.66% compared to head (4a6e71b) 73.61%.
Report is 3 commits behind head on master.

Additional details and impacted files

@@             Coverage Diff              @@
##             master   #21844      +/-   ##
============================================
- Coverage     73.66%   73.61%   -0.05%
+ Complexity    32343    32309      -34
============================================
  Files          1858     1858
  Lines        138146   138141       -5
  Branches      15141    15141
============================================
- Hits         101763   101697      -66
- Misses        28544    28575      +31
- Partials       7839     7869      +30

Flag
Coverage Δ

inttests
24.18% <86.66%> (-0.01%)
:arrow_down:

systests
23.74% <73.33%> (-0.13%)
:arrow_down:

unittests
72.89% <100.00%> (-0.06%)
:arrow_down:

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

Files
Coverage Δ

...er/loadbalance/impl/ModularLoadManagerWrapper.java
91.30% <100.00%> (ø)

...rg/apache/pulsar/broker/service/AbstractTopic.java
87.92% <ø> (ø)

...rg/apache/pulsar/broker/service/BrokerService.java
80.99% <100.00%> (-0.16%)
:arrow_down:

...oker/service/nonpersistent/NonPersistentTopic.java
69.91% <100.00%> (ø)

...sar/broker/service/persistent/PersistentTopic.java
78.37% <100.00%> (-0.42%)
:arrow_down:

...java/org/apache/pulsar/common/util/FutureUtil.java
74.54% <100.00%> (+0.47%)
:arrow_up:

... and 75 files with indirect coverage changes


Update styles.css

What is the change?
Update the styles.css by adding the .btnFrame class to their corresponding btns and remove the inconsistency behaviour of button in home.ejs page.
Related issue?
close: #576
How was it tested?
I have tested it by running the home.ejs page in localhost:3000 and inspecting through google developer tools.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelines while contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[x] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.
[x] Have you tested the code before submission?

Screenshots or Video:
Add a screenshot or demo video if appropriate.
https://user-images.githubusercontent.com/72553479/113655356-42460a00-96b7-11eb-98c2-66a9b44ebd5c.mp4

Please review it.

/gssoc/

/level2/


[BUG] display of segmentation masks with dype uint8 is broken

System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Linux, Ubuntu 21.04 and 18.04.5
FiftyOne installed from (pip or source): pip
FiftyOne version (run fiftyone --version): fiftyone v0.12.0, Voxel51, Inc.
Python version: Python 3.8.10 (fresh conda environment)

Commands to reproduce
Example data
fiftyone datasets create --name uint_mask --dataset-dir $TEST_DIR --type fiftyone.types.ImageSegmentationDirectory
fiftyone app launch uint_mask

Describe the problem
Segmentation masks that are added with dtype unit8 appear broken in the app. This is the case when importing a dataset using ImageSegmentationDirectory as above, as well as when manually adding such a sample to a dataset (c.f. example code below). When changing the dtype to int everything works as expected as seen in the code example below.
The behavior is easiest to observe with the code example below. If you look at the segmentation mask in the app, int_mask shows as expected, while uint8_mask is completely broken. There are a few pixels visible in a the upper left part of the image, but the label values are completely off. Probably something in the serialization/deserealization logic goes wrong and the data is unpacked incorrectly.
A quick fix is changing https://github.com/voxel51/fiftyone/blob/7c061ea22030ea355357df78a8c61598d784ea02/fiftyone/utils/data/importers.py#L2717 to
    mask = etai.read(mask_path, cv2.IMREAD_UNCHANGED).astype(int)

Code to reproduce issue
# generate test data
import cv2
import numpy as np

img = np.zeros((400, 400, 3), np.uint8)
img = cv2.circle(img, (200, 200), 100, (255, 255, 255), -1)

mask = img[..., 0]

EXAMPLE_PATH = "/tmp/test_img.png"
cv2.imwrite(EXAMPLE_PATH, img)

# minimal example
import fiftyone as fo

ds = fo.Dataset()

ds.add_sample(
    fo.Sample(
        EXAMPLE_PATH,
        uint8_mask=fo.core.labels.Segmentation(mask=mask),
        int_mask=fo.core.labels.Segmentation(mask=mask.astype(int)),
    )
)

session = fo.launch_app(ds)

input("any key")

Other info / logs
❯ pip list
Package                     Version
--------------------------- ---------
anyio                       3.3.0
appdirs                     1.4.4
argcomplete                 1.12.3
backports.zoneinfo          0.2.1
black                       21.7b0
boto3                       1.18.24
botocore                    1.21.24
certifi                     2021.5.30
charset-normalizer          2.0.4
click                       8.0.1
cycler                      0.10.0
dataclasses                 0.8
Deprecated                  1.2.12
dill                        0.3.4
dnspython                   1.16.0
eventlet                    0.31.1
fiftyone                    0.12.0
fiftyone-brain              0.6.2
fiftyone-db                 0.2.1
future                      0.18.2
glob2                       0.7
greenlet                    1.1.1
h11                         0.12.0
httpcore                    0.13.6
httpx                       0.18.2
idna                        3.2
imageio                     2.9.0
Jinja2                      3.0.1
jmespath                    0.10.0
joblib                      1.0.1
kaleido                     0.2.1
kiwisolver                  1.3.1
MarkupSafe                  2.0.1
matplotlib                  3.4.3
mongoengine                 0.20.0
motor                       2.5.0
mypy-extensions             0.4.3
ndjson                      0.3.1
networkx                    2.6.2
numpy                       1.21.2
opencv-python-headless      <IP_ADDRESS>
packaging                   21.0
pandas                      1.3.2
pathspec                    0.9.0
patool                      1.12
Pillow                      8.3.1
pip                         21.2.4
plotly                      4.14.3
pprintpp                    0.4.0
psutil                      5.8.0
pymongo                     3.12.0
pyparsing                   2.4.7
python-dateutil             2.8.2
pytz                        2021.1
PyWavelets                  1.1.1
PyYAML                      5.4.1
regex                       2021.8.3
requests                    2.26.0
retrying                    1.3.3
rfc3986                     1.5.0
s3transfer                  0.5.0
scikit-image                0.18.2
scikit-learn                0.24.2
scipy                       1.7.1
setuptools                  57.4.0
six                         1.16.0
sniffio                     1.2.0
sortedcontainers            2.4.0
tabulate                    0.8.9
threadpoolctl               2.2.0
tifffile                    2021.8.8
tomli                       1.2.1
tornado                     6.1
typed-ast                   1.4.3
typing-extensions           <IP_ADDRESS>
tzlocal                     3.0
universal-analytics-python3 1.1.1
urllib3                     1.26.6
voxel51-eta                 0.5.2
wheel                       0.37.0
wrapt                       1.12.1
xmltodict                   0.12.0

What areas of FiftyOne does this bug affect?

[x] App: FiftyOne application issue
[x] Core: Core fiftyone Python library issue
[ ] Server: Fiftyone server issue

Willingness to contribute
The FiftyOne Community encourages bug fix contributions. Would you or another
member of your organization be willing to contribute a fix for this bug to the
FiftyOne codebase?

[ ] Yes. I can contribute a fix for this bug independently.
[ ] Yes. I would be willing to contribute a fix for this bug with guidance
from the FiftyOne community.
[ ] No. I cannot contribute a bug fix at this time.
[x] Maybe, depends on complexity.

Hey @falckt thanks for reporting this. We'll tweak the App-side code to handle segmentation masks with any integer-type, so that users can store and work with masks in any integer type they prefer.


Add a WIT to track it like a task

Great documentation! I noticed that in the "Add a WIT to track it like a task" section, the left and right columns in the table are sometimes mismatched.

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

ID: 1c3f9f74-172b-bcf9-cde8-3eca80bd9f66
Version Independent ID: 25af456b-0268-95e9-8c51-4dfcac78d3af
Content: Add work item types to backlogs and boards - VSTS & TFS
Content Source: docs/work/customize/add-wits-to-backlogs-and-boards.md
Service: unspecified
GitHub Login: @KathrynEE
Microsoft Alias: kaelli

Thank you for your response @KathrynEE. For instance on the first row, left column says "Backlog priority field (Agile, CMMI)" but the code on the right column is about the stack rank field. The second row says "Stack rank field (Scrum)" but the code is about backlog priority etc.


UI/UX: Gradient background on companies, contact and FAQ page

The following pages need a gradient background so it looks a bit more fun.

[ ] Companies
[ ] Contact
[ ] FAQ

No speakers page? @TimKardol

No speakers page? @TimKardol

I forgot that one. Yes the speakers page as well

Closed in #329


[Request] Provide official sha256sum for releases

We consume the releases published at https://github.com/regclient/regclient/releases/  such as https://github.com/regclient/regclient/releases/download/v0.4.7/regsync-windows-amd64.exe
Currently, there is no way to validate the integrity of the downloads as there is no checksum information attached to the release. We can calculate and store the checksum for subsequent integrity checks of the downloads, but that does not help with the initial validation as we can only use the provided binary as the source of truth
Ideally, each published artifact should attach a .sha256  file with the calculated hash of the release
Would it be possible to consider this?
Read more : https://www.apache.org/info/verification.html

Hi @yeikel. Since checksums only verify the file has not been tampered in transit, and https also provides that guarantee, they aren't provided for this project. Notably since checksums and the artifacts are stored in the same location, an attacker changing the artifact could also change the checksum.
Instead, regclient uses signing of the binaries and images using cosign to verify the artifact was generated by the GitHub Action build. Details on how to verify those signatures are included in the installation docs: https://github.com/regclient/regclient/blob/main/docs/install.md

Just my two cents, checksum file still provides value if you are fetching regclient through an Artifactory, using tools such as Bazel.

Just my two cents, checksum file still provides value if you are fetching regclient through an Artifactory, using tools such as Bazel.

What is the checksum doing in that scenario? My hesitation is to avoid a false sense of security.

Under bazel, it used for caching, and immutability guarantee when the artifact is fetched through an read-through proxy. It does what the sigstore does but more primitive.

Under bazel, it used for caching, and immutability guarantee when the artifact is fetched through an read-through proxy. It does what the sigstore does but more primitive.

For caching, you want to use the ETag HTTP header.
Using the sha256 would tell you proxy didn't modify the content, but only if you pulled the sha256sum without using the proxy. And it doesn't guarantee that the original registry didn't modify the content, which is why signing is preferred. Attacks like the xz vulnerability would be more difficult to hide if artifact consumers verified the signature was from GitHub Actions on public commits.

For caching, you want to use the ETag HTTP header.

Oh i mean on the client side, some build tools cache artfiacts from internet by their content checksum.

And it doesn't guarantee that the original registry didn't modify the content, which is why signing is preferred. Attacks like the xz vulnerability would be more difficult to hide if artifact consumers verified the signature was from GitHub Actions on public commits.

No arguments here, i agree.


Fix the "adding new overrides to PanelObjectConfig" problem.

This shouldn't be a breaking change moving forward and existing subclasses of PanelObjectConfig should automatically get the new functionality.

PanelObjectConfig now takes in an PanelObjectConfig.InitObject in its constructor instead of a mess of arguments. This is essentially creating a shadow PanelObjectConfig, which isn't ideal (parameters need to be added in three places now), but all three are fairly obvious and will be caught if the person adding parameters actually tests.
PanelObjectConfig.Builder subclasses will call BuildInitObject() in their subclass, and take in a PanelObjectConfig.InitObject in their constructor, which they'll dutifully pass on to the base implementation.
This is a breaking change, but should be the last one.


Common command link for web applications is broken

Link currently goes to: https://docs.microsoft.com/en-us/azure/ap-service I am assuming you want it to go: https://docs.microsoft.com/en-us/azure/app-service

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

ID: 1c268a98-afcb-d2c2-87c7-880d52900533
Version Independent ID: 4c835da4-38bc-22a8-67b4-dd522adcc0e3
Content: Get started with Azure CLI 2.0
Content Source: docs-ref-conceptual/get-started-with-azure-cli.md
Product: azure
GitHub Login: @sptramer
Microsoft Alias: sttramer

Thank you for the report. This link should be fixed during tomorrow's site publish.


Loading rewarded video throws CLIENT_UNSUPPORTED_OPERATION

Rewarded video does not loading. Request throws:
code: "CLIENT_UNSUPPORTED_OPERATION"
message: "Client does not support the message: getrewardedvideoasync"

Are you testing this on mobile?

Yes. Nothing happens. Loading request returns false

get_purchases also return null. But i have iap products on Facebook

I recall that there were quite a few things I needed to setup before I could get both IAP and ads to work. Have you signed up for Audience Network? Do you have a Payment Account set up?

Yes. Yes. Do we need to review our app for test ads and IAP?

Ok, so for IAP:
What does fbinstant.on_payments_ready() return?
And fbinstant.get_product_catalog(callback)?
Have you followed these steps: https://developers.facebook.com/docs/games/instant-games/guides/in-app-purchases ?
For ads:
Where do you see the "CLIENT_UNSUPPORTED_OPERATION"? In the console? When calling fbinstant.load_rewarded_video(placement, callback)?

Ok, good to hear that rewarded videos work!
For IAP it's probably some setting that is missing somewhere for your project. This is how it looks in the example project where IAP purchases are working:

Good news: administrators can see IAPs. Bad news developers cant. I dont know why.

Ok, hmm, that might be something to ask Facebook about. You should ask this in the Instant Games group on Facebook.

Closing. Rewarded video was confirmed to work.


Update Build

Update various versions
Add Scala3
Add Scalafix/Scalafmt

Also add liancheng's ogranize imports scalafix tool

Remove Main/MainSpec
Switch to sbt-typelevel plugin

@rossabaker

@armanbilge Are you hanging around to help with the project, or just here for the build? :smile:

Oops.  I did not look carefully at the build status before merging.


LG local scoped generators get clobbered with nested dialogs

We need to maintain the Generator properly to the dialog scope.

Changed to cache and restore the generator as adaptive dialogs come in and out of scope on BeginDialog(), ContinueDialog(), And REsumDialog() boundaries
changed EndDialog to restore the parent, in case the parent doesn't cache correctly.
Added unit test to verify that nested dialogs with local generators have the correct generator for the dialog scope.

Pull Request Test Coverage Report for Build 85061

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

Totals

Change from base Build 85048:
0.0%

Covered Lines:
6006

Relevant Lines:
7753

💛  - Coveralls

Pull Request Test Coverage Report for Build 85061

0 of 0   changed or added relevant lines in 0 files are covered.
893 unchanged lines in 109 files lost coverage.
Overall coverage decreased (-1.3%) to 76.2%

Files with Coverage Reduction
New Missed Lines
%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Facebook/FacebookAdapter.cs
1
96.67%

/libraries/Adapters/Microsoft.Bot.Builder.Adapters.Facebook/FacebookClientWrapper.cs
1
93.24%

/libraries/integration/Microsoft.Bot.Builder.Integration.ApplicationInsights.Core/ApplicationBuilderExtensions.cs
1
71.43%

/libraries/Microsoft.Bot.Builder.AI.LUIS/LuisApplication.cs
1
95.45%

/libraries/Microsoft.Bot.Builder.AI.LUIS/V3/LuisApplication.cs
1
96.43%

/libraries/Microsoft.Bot.Builder.AI.LUIS/V3/LuisUtil.cs
1
96.5%

/libraries/Microsoft.Bot.Builder/BotStateSet.cs
1
85.0%

/libraries/Microsoft.Bot.Builder.Dialogs/Debugging/SourceRange.cs
1
46.15%

/libraries/Microsoft.Bot.Builder.Dialogs/Memory/Scopes/MemoryScope.cs
1
88.37%

/libraries/Microsoft.Bot.Builder.Dialogs/PersistedStateKeys.cs
1
60.0%

Totals

Change from base Build 85048:
-1.3%

Covered Lines:
8427

Relevant Lines:
11059

💛  - Coveralls

:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.Luis.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.AI.QnA.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.ApplicationInsights.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Azure.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.Dialogs.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Builder.TemplateManager.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Configuration.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Connector.dll compared against version 4.5.3
:heavy_check_mark: No Binary Compatibility issues for Microsoft.Bot.Schema.dll compared against version 4.5.3


Fix API profile endpoint

Hello and thanks for the crate! I will be using it for a project soon hopefully.
Quick PR fixing the endpoint for profiles: it is /api/account, as specified here: https://lichess.org/api#tag/Account/operation/accountMe

Hi there!
Apologies for responding so late to this PR, I've been inactive for quite a while.
Thanks for the fix :)

No problem :) I fixed more stuff, I'll open other PRs eventually. Cheers!


Hard coded path separator for 'created new dat' string

https://github.com/datproject/dat/blob/9a7150a10a7b312d408e2c223608eaea6d21f213/src/ui/archive.js#L23
Forward slash is not a path separator on Windows. Need to use some Node module to get the current platforms path sep char.

Hi, am I overqualified for this?  I just found this project and I'm thinking what an awesome project I would love to contribute but this issue looks like its been set aside as an easy entry for someone.
It could be easily solved by adding a package but maybe you don't want an extra dependency and since its a small task it could be solved without the package in a line or two of code.

Go for it if you'd like =). Yes, should be able to accomplish with the core path module afaik.

OK, I've just had a look at it and it's done but then it occured to me to look around to see if there was anywhere else it was needed and I noticed that there is a lot of linux style line endings.  It is a different package but that should probably be changed as well.

Thanks!
Ya, we did not have windows support for a long time and I was not great at thinking about that =/.


Update dependencies

I think peerDependencies is correct if the original.

Thanks for this @sugarshin. Not quite generic enough to meet all needs, unfortunately.
Ref #43


Keyed Loops

Loops need an option to be keyed in order to reorder components and preserve state.

Closing because there is no local state in Moon v1.

The reason for a library to implement keyed loops is to preserve DOM state rather than library state.

Actually, Moon aimed to have mechanisms for storing DOM state directly within vnodes, moving the responsibility of maintaining DOM state to the developer (e.g. a focus prop). I realized that it wasn't exactly practical, so a keyed algorithm is back on the roadmap.


Install-AndriodSDK.ps1 causes Windows2019/2022 build failure

Description
Update: I ran Windows 2019 this morning and found this same issue.
Starting January 21, 2023 around 1 pm EST, I have had three Windows2022 builds fail on Install-AndriodSDK with the error that -AndroidPackages $platformList is null. I had three builds run in the morning without issue.
I have been running builds back to back while working on modifying the image-generation.yml for my requirements. I have kept all the build files the same, and I didn't update the repo between any of the above builds.
As a test, I fetched the latest upstream this morning and hit the same error. Please let me know what information I should provide, and I am happy to assist! Thanks all for the work that you put into this!
Platforms affected

[X] Azure DevOps
[ ] GitHub Actions - Standard Runners
[ ] GitHub Actions - Larger Runners

Runner images affected

[ ] Ubuntu 18.04
[ ] Ubuntu 20.04
[ ] Ubuntu 22.04
[ ] macOS 11
[ ] macOS 12
[x] Windows Server 2019
[X] Windows Server 2022

Image version and build link
I think I need some help understanding why I am not seeing a "Version" field under my "Initialize Job". If someone can provide me with some direction here I am happy to provide the required information:
Starting: Initialize job
Agent name: 'SelfHosted000026'
Agent machine name: 'SelfHosted000026'
Current agent version: '2.214.1'
Current image version: 'dev'
Agent running as: 'AzDevOps'
Prepare build directory.

Is it regression?
I am seeing this as above.
Expected behavior
Attached are logs from where the build was successful:
expected.txt
Actual behavior
Attached are what I am currently seeing:
failure.txt
Repro steps
Compile this packer build for Windows2022. For me the failure happens at the 2h 9-10m mark.

Hello @PapaDers, we are working on it, thank you.

fixed.

This did fix it for me! Thank you all 💯

Howdy - has the new MacOS release of this fix rolled out yet? I'm still seeing this failure in my Android builds on MacOS-12 images unfortunately.


Information regarding the consumer being able to read messages

When creating integration tests using kafkajs, I ran into some issues were I did awaited for the connection to send a message from my producer. However, I was not aware that the consumer would only be able to actually read messages from a topic, after the consumer event GROUP_JOIN. I'm sending a PR that might help people with the same issue :)
Here's a PR with the information: https://github.com/tulios/kafkajs/pull/521

I ran into some issues were I did awaited for the connection to send a message from my producer.

Could you maybe explain the issue a bit more? A producer should be able to produce messages completely independently from a consumer being ready or not. Kafka logs being persistent, a consumer can connect and read messages from the log at any time after they were produced (or until they are garbage collected through time-based retention or key-based compaction).

I think this was in an integration test, right @capucho?

Yes, sorry for the lack of context.
Imagine I have the following test to see if I consume a single message in my consumer.
test('should be able to read published messages', async done => {
        await kafkaConsumer.subscribe(myInternalTopic, consumerFn(done))
        // if I don't have this waitForConsumerToJoinGroup here, what will happen is that
        //I will send the message but my consumer couldn't yet be available to listen to the message
        await waitForConsumerToJoinGroup(kafkaConsumer.consumer)
        await kafkaProducer.send(topic, [
          {
               value: 'test'
          },
        ])
      }

If I don't have the waitForConsumerToJoinGroup, what would happen is that I could end up in a situation where the kafkaConsumer.subscribe() would return the result, even though it didn't actually join the consumer group yet. Then my producer would run, send the message. However, since my consumer didn't join yet the consumer group yet, what will happen is that I will never see the message since I don't have the fromBeginning flag as true.
I was just trying to clarify that being connected doesn't actually mean that you'll consume the produced messages at that point.


My allsky is overexposed during the day

Hello
My allsky during the day it will have a few normally exposed photos, then one will be overexposed.
I checked the allsky log and it got the following error:
Dec  6 11:14:42 allsky allsky.sh[11232]: WARNING: ASISetControlCaps() for control 1, value=18605 failed: ASI_ERROR_GENERAL_ERROR (16)
Dec  6 11:14:47 allsky allsky.sh[11232]:   > ERROR: Failed getting image: ASI_ERROR_TIMEOUT #1 (with 0.8 exposure = NO) (11)
Dec  6 11:14:59 allsky allsky.sh[11232]: STARTING EXPOSURE at: 2021-12-06 11:14:59   @ 18.61 ms (0.02 sec)
I don't get this error at night. It only happens during the day.
This is my allsky website: http://vtobs.com
During the day that error happens very often
Sorry my english is not good.

Dec  6 11:12:25 allsky allsky.sh[10884]: STARTING EXPOSURE at: 2021-12-06 11:12:25   @ 120 us
Dec  6 11:12:25 allsky allsky.sh[10884]: === next exposure: old way=215, new way=206 (multiply by 1.721) [last_exposure_us=120, minAcceptable=122, mean=78]
Dec  6 11:12:26 allsky allsky.sh[10884]: === next exposure: old way=370, new way=352 (multiply by 1.721) [last_exposure_us=205, minAcceptable=122, mean=78]
Dec  6 11:12:28 allsky allsky.sh[10884]: === next exposure: old way=245, new way=197 (multiply by 0.564) [last_exposure_us=350, maxAcceptable=134, mean=216]
Dec  6 11:12:28 allsky allsky.sh[10884]:  >xxx mean was 78 and went from 44 below min of 122 to 82 above max of 134, is now at 216; OK to set temp max to current_exposure_us of 350
Dec  6 11:12:29 allsky allsky.sh[10884]: === next exposure: old way=370, new way=331 (multiply by 1.617) [last_exposure_us=205, minAcceptable=122, mean=83]
Dec  6 11:12:29 allsky allsky.sh[10884]:  >xxx mean was 216 and went from 82 above max of 134 to 39 below min of 122, is now at 83; should NOT set temp min to current_exposure_us of 205
Dec  6 11:12:30 allsky allsky.sh[10884]: === next exposure: old way=595, new way=533 (multiply by 1.617) [last_exposure_us=330, minAcceptable=122, mean=83]
Dec  6 11:12:30 allsky allsky.sh[10884]: WARNING: ASISetControlCaps() for control 1, value=350 failed: ASI_ERROR_GENERAL_ERROR (16)
Dec  6 11:12:35 allsky allsky.sh[10884]:   > ERROR: Failed getting image: ASI_ERROR_TIMEOUT #1 (with 0.8 exposure = NO) (11)
Dec  6 11:12:47 allsky allsky.sh[10884]: STARTING EXPOSURE at: 2021-12-06 11:12:47   @ 350 us
Dec  6 11:12:52 allsky allsky.sh[10884]:   > ERROR: Failed getting image: ASI_ERROR_TIMEOUT #2 (with 0.8 exposure = NO) (11)
Dec  6 11:12:54 allsky allsky.sh[10884]: STARTING EXPOSURE at: 2021-12-06 11:12:54   @ 350 us
Dec  6 11:12:59 allsky allsky.sh[10884]:   > ERROR: Failed getting image: ASI_ERROR_TIMEOUT #3 (with 0.8 exposure = NO) (11)
Dec  6 11:13:01 allsky allsky.sh[10884]: STARTING EXPOSURE at: 2021-12-06 11:13:01   @ 350 us
Dec  6 11:13:06 allsky allsky.sh[10884]:   > ERROR: Failed getting image: ASI_ERROR_TIMEOUT #4 (with 0.8 exposure = NO) (11)
Dec  6 11:13:08 allsky allsky.sh[10884]: STARTING EXPOSURE at: 2021-12-06 11:13:08   @ 350 us
Dec  6 11:13:13 allsky allsky.sh[10884]:   > ERROR: Failed getting image: ASI_ERROR_TIMEOUT #5 (with 0.8 exposure = NO) (11)
Dec  6 11:13:15 allsky allsky.sh[10884]: *** ERROR: Maximum number of consecutive errors of 5 reached; exiting...
Dec  6 11:13:16 allsky allsky.sh[10884]: copy_notification_image.sh: Uploading NotRunning.jpg
Dec  6 11:13:19 allsky allsky.sh[10884]:      ***** Stopping AllSky *****
Dec  6 11:13:19 allsky allsky.sh[10884]: 'capture' exited with RETCODE=99
Dec  6 11:13:19 allsky allsky.sh[10884]: copy_notification_image.sh: Uploading NotRunning.jpg
Dec  6 11:13:25 allsky allsky.sh[11057]:      ***** Starting AllSky *****
Dec  6 11:13:25 allsky allsky.sh[11057]: CAMERA: ZWO
Dec  6 11:13:25 allsky allsky.sh[11057]: Starting allsky camera...
Dec  6 11:13:25 allsky allsky.sh[11057]: copy_notification_image.sh: Uploading StartingUp.jpg
Dec  6 11:13:34 allsky allsky.sh[11057]: **********************************************
Dec  6 11:13:34 allsky allsky.sh[11057]: *** Allsky Camera Software v0.8.2c |  2021 ***
Dec  6 11:13:34 allsky allsky.sh[11057]: **********************************************
Dec  6 11:13:34 allsky allsky.sh[11057]: Capture images of the sky with a Raspberry Pi and an ASI Camera

@ptson92, please make sure you havr the lasted files from GitHub.  We just updated several a few days ago.
Also see the Wiki page for reporting Issues and follow those instructions.
Your English is great.  I would not have known it wasn’t your native language if you didn't mention it.
Thanks

Thank you very much.
I just updated yesterday.
Before that, I had a problem when switching from night to day the exposure time was locked at 15s.

is there a command to check the allsky version?

@Bra1nsen look in /var/log/allsky.log for the word "Software".

thanks Eric.
maybe not the right place, but youre definitely the right person to ask:
in addition to the skycam, i also connected a couple of weather sensors (temp, wind, radiation) to my raspi. I wrote a simple python script in which I send the data to my server via mqtt. apparently this interferes with the allsky software, since both apparently don't run at the same time. can that be so? And if so, what would you advise me to do?

There's really no reason your sensor python and the allsky code shouldn't coexist.  The allsky capture app doesn't use any ports itself, and the WebUI is on port 80 ( via lighttpd, could be changed in /etc/lighttpd/lighttpd.conf if desired ).
The only potential issue would be resource exhaustion... memory or processor.. but as long as your sensor python code isn't doing anything crazy.. you should be more than fine.  You could have both running, and then use top to monitor the CPU/Memory just in case.  You can also use iostat (part of the sysstat package) to check for disk IO issues -- but I highly doubt there will be any.
fwiw, you could modify your Python code to dump the sensor data to a text file, then add it as a text overlay for capture.  Then you'd have your sensor data under the date/time, sensor temp, gain, etc... at the top left of your allsky image.

ok i will check that. in any case, after activating my python script, the allsky service no longer worked. but your answer calms me down. Thank you Sir

@Bra1nsen can you be more specific when you say "the allsky service no longer worked"?
Did you get any messages in /var/log/allsky.log?

Yep, something is wrong. and it is definitely due to the prallel running python script.
the log show immediately after I run my script:  "***** Stopping AllSky *****"

I mean I could share the script, but it's an absolutely basic program that publishes simple strings

@Bra1nsen let's create a 'new issue' for this... then, please do share the name of your script, as well as the code, and the /var/log/allsky.log file.
Thanks!

@ptson92 Any update?

I have updated to the latest version. It still has the same error.  I tried turning the 0.8 exposure on and off, but still the same error. Now that I'm using manual exposure, I don't get the error anymore.

@ptson92 Please see the Wiki page for reporting Issues and follow those instructions.  I will take a look at your log file.

Thanks
This is my log file.
allsky.log

@ptson92 Try setting your USB Bandwith to 40 with auto exposure on and see if it helps.  If not, try 60 and 100.
Also see if your Pi is having undervoltage issues.  In the WebUI, click on the "System" link.

Thank you @EricClaeys
I'm going to change the power supply to the Pi this weekend and try again.

@ptson92 Changing the USB bandwidth is super easy in the WebUI and is a g[d debugging step.

Eric i did the update as suggested, but now iam not able to set exposure time during the day? What can i do?

would it work if i adjust here?

/etc/raspap/camera_options_RPiHQ.json

@Bra1nsen In the WebUI's "Daytime settings" section there should be an "Exposure" setting.  It is an "advanced" option since people usually have auto-exposure on during the day.  Go to the end of the page and click on the "Show advanced options" button.
Do NOT edit the "camera_options_RPiHQ.json" file manually, since the WebUI overwrites it.  That file is meant to be updated only via the WebUI.

@ptson92 Did changing the power supply and/or USB bandwidth help?
You log file showed that you got a couple pictures that were fairly dark, then a super bright one, then a couple fairly dark, then the ASI_ERROR_TIMEOUTs.  There wasn't anything with a 15-second lock.
Since the first picture was dark, the software increased the exposure time but the second picture was just as dark so the software increased the exposure time again, and the 3rd picture jumped significantly in brightness.
It's like there's stiction in the camera exposure - the exposure time keeps increasing but the brightness doesn't change, then all of a sudden another change in exposure time causes a big change in brightness.  I don't know why that is.

@EricClaeys
I have tried changing the power supply, trying to change the usb bandwidth. Still nothing changed, I still get the same error. That problem only shows up during the day. Everything is fine at night.
I tried it on ASI 120MC and it doesn't have the same problem. Maybe the problem is because the 178MC is faulty or the firmware is not good.
Thanks

@ptson92 You are only getting the ASI_ERROR_TIMEOUT errors during the day?
Please follow the instructions here and upload your `/var/log
As a test, set your daytime exposure to 10000 (same as night), your day brightness to 50 (which is the default), and night max auto-exposure to 60000 (which is the max amount the camera supports). and run during the day.
If that still fails, set the "Version 0.8 Exposure" option to "Yes" and try again.

Closing issue - no response from user in 5 months.


run oref0-set-system-clock after oref0-set-device-clocks in case rig is offline

When a rig is offline, it is using this code path and running oref0-set-device-clocks (which fails), but never getting to the part of oref0-pump-loop that runs oref0-set-system-clock. In order to make sure that the rig sets its time from the pump when NTP is unavailable, this simply adds a oref0-set-system-clock run after the attempt to oref0-set-device-clocks.

It looks like one of our unit tests may have a midnight-UTC boundary condition:
not ok 189 IOB should calculate IOB without counting time pump suspended in middle of basal
  AssertionError: expected -0.01 to be 0.235
      at Assertion.fail (node_modules/should/cjs/should.js:275:17)
      at Assertion.value (node_modules/should/cjs/should.js:356:19)
      at Context.<anonymous> (tests/iob.test.js:973:38)

Just did some whitespace cleanup to prompt another travis-ci run.

I tested it several times during the week on my PI+HAT rig. Works very well! 👍 for merge :)


 Delete the others, including these Instructions.
{{cask_file}} represents the cask file you’re submitting/editing (if applicable).
If there’s a checkbox you can’t complete for any reason, that’s OK. Just explain in detail why you weren’t able to do so.

Changes to a cask
Editing an existing cask

[ ] Commit message includes cask’s name (and new version, if applicable).
[ ] brew cask audit --download {{cask_file}} is error-free.
[ ] brew cask style --fix {{cask_file}} left no offenses.

Adding a new cask

[ ] Checked there aren’t open pull requests for the same cask.
[ ] Checked there aren’t closed issues where that cask was already refused.
[ ] When naming the cask, followed the token reference.
[ ] Commit message includes cask’s name.
[ ] brew cask audit --download {{cask_file}} is error-free.
[ ] brew cask style --fix {{cask_file}} left no offenses.
[ ] brew cask install {{cask_file}} worked successfully.
[ ] brew cask uninstall {{cask_file}} worked successfully.

Changes to the core

[ ] Followed hacking.md.

Please delete the parts of the pull request template that are not relevant and fill out the rest.

The download link is walled, couldn't verify.

The download link is walled, couldn't verify.

Yep. https://github.com/caskroom/homebrew-cask/pull/16503 and https://github.com/caskroom/homebrew-cask/pull/17319.


[BUG]InvalidArgument desc = There is no block device frontend for volume vi01

I used longhorn UI create volumn and  Create PV/PVC,then used https://longhorn.io/docs/1.0.1/references/examples/#simple-pod to create pod .
Pod status :  ContainerCreating
Block type volume no this issue
[root@master220 home]# kubectl  get pvc
NAME   STATUS   VOLUME   CAPACITY   ACCESS MODES   STORAGECLASS      AGE
vb01   Bound    vb01     2Gi        RWO            longhorn-static   53m
vi01   Bound    vi01     3Gi        RWO            longhorn-static   53m
[root@master220 home]# kubectl  describe  pod  longhorn-simple-pod-iscsi
Name:         longhorn-simple-pod-iscsi
...
Volumes:
volv:
Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName:  vi01
ReadOnly:   false
default-token-qkflr:
Type:        Secret (a volume populated by a Secret)
SecretName:  default-token-qkflr
Optional:    false
QoS Class:       BestEffort
Node-Selectors:
Tolerations:     node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type     Reason                  Age                  From                         Message

Normal   Scheduled                           default-scheduler            Successfully assigned default/longhorn-simple-pod-iscsi to node222.bocloud.cn
Normal   SuccessfulAttachVolume  43m                  attachdetach-controller      AttachVolume.Attach succeeded for volume "vi01"
Warning  FailedMount             12m (x23 over 43m)   kubelet, node222.bocloud.cn  MountVolume.SetUp failed for volume "vi01" : kubernetes.io/csi: mounter.SetupAt failed: rpc error: code = InvalidArgument desc = There is no block device frontend for volume vi01
Warning  FailedMount             7m35s (x3 over 30m)  kubelet, node222.bocloud.cn  Unable to attach or mount volumes: unmounted volumes=[volv], unattached volumes=[default-token-qkflr volv]: timed out waiting for the condition
Warning  FailedMount             3m1s (x15 over 41m)  kubelet, node222.bocloud.cn  Unable to attach or mount volumes: unmounted volumes=[volv], unattached volumes=[volv default-token-qkflr]: timed out waiting for the condition
UI status
State: Attached
Health: Healthy
Ready for workload:Ready
Conditions:
restore
scheduled
Frontend:iSCSI
Attached Node & Endpoint:
node222.bocloud.cn
iscsi://<IP_ADDRESS>:3260/iqn.2019-10.io.longhorn:vi01/1
Size:
3 Gi
Actual Size:0 Bi
Base Image:
Engine Image:abcsys.cn:5000/longhornio/longhorn-engine:v1.0.1
Created:an hour ago
Node Tags:
Disk Tags:
Last Backup:
Last Backup At:
Instance Manager:
instance-manager-e-2b8f0fb4
Namespace:default
PVC Name:vi01
PV Name:vi01
PV Status:Bound
Pod Name:longhorn-simple-pod-iscsi
Pod Status:Pending
Workload Name:
Workload Type:
[root@node221 /]# service iscsid status
Redirecting to /bin/systemctl status iscsid.service
● iscsid.service - Open-iSCSI
Loaded: loaded (/usr/lib/systemd/system/iscsid.service; disabled; vendor preset: disabled)
Active: active (running) since 五 2020-08-14 10:04:08 CST; 29min ago
Docs: man:iscsid(8)
man:iscsiuio(8)
man:iscsiadm(8)

Notice that you are using the frontend iSCSI, hence the pod cannot find a block device file then mount it automatically after the attachment.
You can check this doc to see how to use Longhorn volume with frontend iSCSI.

thx
The Longhorn CSI driver doesn’t support iSCSI mode.
Attached Node & Endpoint:
node222.bocloud.cn
iscsi://<IP_ADDRESS>:3260/iqn.2019-10.io.longhorn:vi01/1
The above information can be used to connect to the iSCSI target provided by Longhorn using an iSCSI client.


Moving Focus after disabling an input

For consideration to fix the Issue listed. From discussion and further digging isDisabled wasn't being passed to useFocus and probably wouldn't be the right place to fix it anyways because disabled elements shouldn't fire any events, even blur.
Instead, isDisabled was added as a prop to FocusRing which prevents the rendering of those classes if the FocusRing is disabled. Wrote a demo that shows how FocusRings should be moved when it gets disabled out from under a user.
Closes https://github.com/adobe/react-spectrum/issues/1164
✅ Pull Request Checklist:

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

📝 Test Instructions:

🧢 Your Project:

closing this one, explanation in Issue this was hoping to close


[Feature] 不能正确刮削湾湾的视频

Description
能不能增加下湾湾产的小姐姐视频刮削
Is this feature related to a specific bug?
No response
Do you have a specific solution in mind?
No response

本身就不支持的


Add warning detection for "namemaybein"

"namemaybein" should check whether the referenced compartment exists. If not, there should be a warning.

Implemented in https://github.com/sys-bio/vscode-antimony/commit/760e28068b3d810c02b3e7cfb4c60dff7f1d4746


Add networking support

Networking Todo:

[x] Put all containers into a takeout network
[x] Test (somehow?) that this network means other Docker containers can be accessed by their full name (e.g. TO--mailhog--v1.0.1) in the target Docker-based Laravel apps
[x] Figure out how to make it so my MySQL Docker container is accessible as mysql--alias
[x] How do we make it so people with only one container get mysql easily, but people with multiple MySQL containers also have something usable
[x] Tag all new containers with serviceVersion (e.g. mysql80)
[x] Tag the first container with the short version (e.g. mysql)
[x] Clean up the version number?
[x] Extract Docker Networking methods to a separate class
[x] Test the things with @test on them

Brainstorm on the naming situation:

By default, each service aliases itself to just its service name (e.g. mysql)

Every container gets tagged with mysql80:
@josecanhelp gave his blessing to Option 1 🙌

Option 1:

All MySQL instances (e.g.) are tagged with their name and version (e.g. mysql80) and the first instance of that type that I spin up also gets the short version (mysql), with the intention of later making it so we can allow them to repoint the shortcut

Option 2:

If I spin up a second MySQL instance, it spins down my first, and then names them all as mysql57, mysql80, etc. and points the short name (mysql) to the latest of those I have open

Every container doesn't necessarily get tagged with the version:

Option 3:

If I spin up a second MySQL instance, it spins down my first, and then names them all as mysql57, mysql80, etc.

Option 4: (not prefered)

We require a nickname for every new container spun up, and that's used for its alias

Option 5: (not prefered)

Number them. mysql1, mysql2 ,
etc

Not sure why WIndows is erroring but it has nothing to do with this code.

Crap. One fix needed:

This thing is way too long.


Darwin builds for MacOS should be macOS

Problem
macOS is the proper name, let's fix that 👍

fix this where?  in GN?


Improvements to the french localization to make it more idiomatic :

As requested on https://github.com/chriskiehl/Gooey/pull/347, I rebased the changes on the release-1.0.3 branch.

Corrected small typos in the french localization file.
Added articles where necessary in the french localization.
Added spaces and dots to comply with french typographic rules.
Added accentuated capitals in the french localization where required.
Improvements to the french localization to make it more idiomatic.

Awesome. Thanks! 👍


chiwa.getAllTags(phoneNumber) not success

I installed your module and succeeded running ypur example: chiwa.authenticateWithToken(token) and chiwa.getNumberTag(phoneNumber, countryCode), but when I ran chiwa.getAllTags(phoneNumber) it returned:

{ status: 'error', message: 'No result found.' }

Please help.

Hi soulhd, thanks for taking the time to report this issue and helping improve the project!
Could I confirm that you’ve followed the documentation to provide the full phone number, including the country code, as shown in the example?
const chiwa = require('@akane_chiwa/getcontact-web-js');

(async () => {
  try {
    // You MUST provide the complete number along with the country code.
    const phoneNumber = '+6285701203115';
    const tags = await chiwa.getAllTags(phoneNumber);
    console.log(tags);
  } catch (error) {
    console.error('Error fetching tags:', error);
  }
})();

If you’ve already done this and are still experiencing the error, it could be due to our limit on GetContact searches being reached. Please let me know if this helps or if you’re seeing something different on your end. Thanks again for bringing this up!

Ok, I did anything right and I just double checked. I'll restart my project from beginning maybe tonight.
Oh and I even studied your module briefly, the getAllTags seems to be posting request using header like you'd have when you call it from the web app by chrome browser, right? I did copying the request as curl from chrome's inspect panel and pasted it into terminal changing phoneNumber data, turned out that if you never query any phone number through the web app before, you'll never get the tags from requesting that way. CMIIW. I don't know how, IMHO I think the code should use selenium or anything to mimick real chrome browser


[plex] Added values to choose init container image

Special notes for your reviewer:
This is to close Issue #258
Checklist

[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [radarr])

Thanks for this change, @RickCoxDev!


Create ankushtripathii.json

My personal profile

Fixes Issue

Changes proposed

Check List (Check all the applicable boxes)

[ ] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.
[ ] This PR does not contain plagiarized content.
[ ] The title of my pull request is a short description of the requested changes.

Screenshots

Note to reviewers

Please move your file to public/data.
Also, update your Twitter link!

Let us know if you need any help! __        Summary: 🛠 This code needs a fix  |  Tags: Not maintainable

Please move your file to public/data.
Also, update your Twitter link!

Let us know if you need any help! __        Summary: 🛠 This code needs a fix  |  Tags: Not maintainable

how to move file to public/data .


document directory layout

It will be easier to make decisions about where new components write data if we have a common place where the directory layout is documented.

@crosbymichael Was this done in the ops guide?

Naw, i'm going to work on something today.  Or maybe add this as an update to the ops guide


Trigger helm release

Re creating approved PR, deleted by cleaning my fork.
cc: @platinummonkey

@platinummonkey  I don't have merge permissions in this repo, I leave it for you guys.


167-Wrong-Currency-Symbol-In-QuickSearch

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

You need to sign the CLA for me to be able to merge this

Now signed

#168

#167


[now-cli] Remove deprecated @now/php builder from bundled builders tarball

@now/php has been deprecated in favor of community-maintained now-php, so don't bundle the deprecated builder with Now CLI.

Codecov Report

Merging #2907 into canary will decrease coverage by 0.09%.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           canary   #2907     +/-   ##
========================================
- Coverage    13.2%   13.1%   -0.1%
========================================
  Files         265     265
  Lines       10338   10317     -21
  Branches     1163    1168      +5
========================================
- Hits         1365    1352     -13
+ Misses       8912    8904      -8
  Partials       61      61

Impacted Files
Coverage Δ

src/util/prefer-v2-deployment.ts
56.25% <0%> (-5.66%)
:arrow_down:

src/util/projects/get-project-by-id-or-name.ts
25% <0%> (-3.58%)
:arrow_down:

src/util/metrics.ts
70.58% <0%> (+2.4%)
:arrow_up:

Continue to review full report at Codecov.

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

👍


get_weighted_triads_number

For consistency with other methods, this should be named
get_number_of_weighted_triads()

In the current Ensmallen master branch, this already appears as get_number_of_weighted_triads, which version are you using?

I was searching in the online documentation, here
https://anacletolab.github.io/grape/grape/ensmallen.html#Graph.get_weighted_triads_number
I did not wind up using this particular method, I found something better!

That documentation is a tad outdated, we have to update it. @zommiommy could you take a look at that, when you have time?


E10: \ should be followed by /, ? or & line 1242:

After installation of hashivim/vim-terraform and juliosueiras/vim-terraform-completion, Vim throws list of errors at startup:
E10: \ should be followed by /, ? or &
line 1243:
E10: \ should be followed by /, ? or &
line 1244:
E10: \ should be followed by /, ? or &
line 1245:
E10: \ should be followed by /, ? or &
line 1246:
E10: \ should be followed by /, ? or &
line 1247:
E10: \ should be followed by /, ? or &
line 1248:
E10: \ should be followed by /, ? or &
line 1249:
E10: \ should be followed by /, ? or &

It repeats up to number 1270, next occurences are 1281, 1283, 1287 and 1289.
hashivim/vim-terraform is at<PHONE_NUMBER>3db362b13a56f26cd34f668e9e17a4
vim-terraform-completion is at b451f39c1ad5649bf277cc7a366e2fdf2afcb987
vim 8.0.1542
It doesn't happen when only one of these two is enabled. Any idea what's going on or how to make this report more useful?

Never mind, looks like I made a mistake – it happens only when vim-terraform is loaded. I will report it there.
Sorry for the noise.

no problem


Update ip-addresses.md

Added the South Africa North (JNB) ip

@v-vedara : Thanks for your contribution! The author, @mrbullwinkle, has been notified to review your proposed change.

@v-vedara : Thanks for your contribution! The author, @mrbullwinkle, has been notified to review your proposed change.

#sign-off


IncrementVersionNumber - the new version number is less than the old version number

Hi,
I have the following problem with the "IncrementVersionNumber" workflow:
[IncrementVersionNumber] Unexpected error when running action. Error Message: The new version number (1.10) is less than the old version number (1.9). The version number must be incremented., StackTrace: at Set-VersionInSettingsFile, D:\a\_actions\microsoft\AL-Go-Actions\v5.0\IncrementVersionNumber\IncrementVersionNumber.psm1: line 108 <- at <ScriptBlock>, D:\a\_actions\microsoft\AL-Go-Actions\v5.0\IncrementVersionNumber\IncrementVersionNumber.ps1: line 46 <- at <ScriptBlock>, D:\a\_temp\989f38ee-08d1-4139-9f8b-28d0b976b3b7.ps1: line 4 <- at <ScriptBlock>, <No file>: line 1
I couldn't find the exact reason in the code, but it seems the System.Version cast is not applied correctly to variables before ($newValue -lt $oldValue) comparison.
These are the steps to recreate the issue:

Create new repo from AL-Go-PTE template
Wait until Initial Build is done
Run "Create new app" workflow with sample code parameter
Run "Increment Version Number" workflow with Updated Version Number parameter: 1.9
Run "Increment Version Number" workflow with Updated Version Number parameter: +0.1

Here is my public repo with the issue recreated: https://github.com/akoniecki/versionincrement-debugging/actions/runs/8718133126/job/23914709863#step:7:60

We just got the exact same issue.
Error: Unexpected error when running action. Error Message: The new version number (2.10) is less than the old version number (2.9). The version number must be incremented., StackTrace: at Set-VersionInSettingsFile, /home/runner/work/_actions/microsoft/AL-Go/f2f452940bc16f36a4c59f1fd1982c566f16c03c/Actions/IncrementVersionNumber/IncrementVersionNumber.psm1: line 108 <- at <ScriptBlock>, /home/runner/work/_actions/microsoft/AL-Go/f2f452940bc16f36a4c59f1fd1982c566f16c03c/Actions/IncrementVersionNumber/IncrementVersionNumber.ps1: line 46 <- at <ScriptBlock>, /home/runner/work/_temp/a3b6a4b4-9bc3-4c1d-ab35-7258a178aaaf.ps1: line 4 <- at <ScriptBlock>, <No file>: line 1

After updating AL-GO, we encountered the same error during the ‘Create Release’ process. We’re also using AL-Go-PTE.

Unexpected error when running action. Error Message: The new version number (<IP_ADDRESS>) is less than the old version number (<IP_ADDRESS>).
The version number must be incremented., StackTrace: at Set-VersionInSettingsFile,
D:\a\_actions\microsoft\AL-Go-Actions\v5.0\IncrementVersionNumber\IncrementVersionNumber.psm1: line 108 <- at <ScriptBlock>,
D:\a\_actions\microsoft\AL-Go-Actions\v5.0\IncrementVersionNumber\IncrementVersionNumber.psm1: line 154 <- at Set-VersionInAppManifests,
D:\a\_actions\microsoft\AL-Go-Actions\v5.0\IncrementVersionNumber\IncrementVersionNumber.psm1: line 150 <- at <ScriptBlock>,
D:\a\_actions\microsoft\AL-Go-Actions\v5.0\IncrementVersionNumber\IncrementVersionNumber.ps1: line 53 <- at <ScriptBlock>,
D:\a\_temp\d26634c8-a3cc-4341-991e-cf830077b236.ps1: line 4 <- at <ScriptBlock>, <No file>: line 1


task29

Task on Exceptions(Try catch Finally, Retry, Throw) - Read the excel and write the data into another Sheet

SourceCode/2023/Oct2023/Basics/karunakar/Task29/project.json
Scoring:
Code Completion: 1.5/2
Execution: 1.5/2
Annotations and Comments: 0.5/1
Issues and Solutions:

No Automation Hub URL is defined in project: Go to "Project Settings", fill in the required information including the "Automation Hub URL".

Unused dependency packages: UiPath.Mail.Activities, UiPath.Testing.Activities, and UiPath.UIAutomation.Activities are found in your project. If they're not in use, delete them. Your process execution will speed up.

"Log Message" is not used in the Main workflow: Log Messages are crucial in and after development. They make it easy to trace your program execution and find errors. Add them.

"abcd" variable is unused: Delete variables which are not doing anything in the program.

Unnecessary use of "Task on Exceptions" (Try catch finally) using system exception SYSTEM.IO.IOEXCEPTION: Remove unnecessary sequences. It will make your code cleaner and more readable.

"Read Range Workbook" is defined more than once: Assign activities unique names. It reduces chances of errors and increases code readability.

DataTable variable "exception_dtt" does not have DataTable prefix

@karunakar7668
Task -29
Code verified.
Complete a pending tasks.


Blocking for collaborators

Collaborator blocking is available to all users with full access. I would like there to be an option for editing access rights, but without all the other features. For example, without blocking editing for co-authors.
And yet - no one can understand - who exactly blocked the file for the co-authors? When unlocking, the information is written, but when it is blocked, it is not.

Hello @ChupakabraMSK, thank you for report. At your request, two enhancements were created in our private issue tracker - 52815, 52816.


[vulkan-sdk-*] Update to 1.3.290.0

Fix #39172
The following 13 ports have been updated:

port
new version

glslang
14.3.0

lunarg-vulkantools
1.3.290.0

robin-hood-hashing
1.3.290.0

spirv-cross
1.3.290.0

spirv-headers
1.3.290.0

spirv-reflect
1.3.290.0

spirv-tools
1.3.290.0

volk
1.3.290.0

vulkan-headers
1.3.290.0

vulkan-loader
1.3.290.0

vulkan-tools
1.3.290.0

vulkan-utility-libraries
1.3.290.0

vulkan-validationlayers
1.3.290.0

Checklist

[x] Changes comply with the maintainer guide.
[x] SHA512s are updated for each updated download.
[ ] ~The "supports" clause reflects platforms that may be fixed by this new version.`~
[ ] ~Any fixed CI baseline entries are removed from that file.~
[ ] ~Any patches that are no longer applied are deleted from the port's directory.~
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is added to each modified port's versions file.

Test
The port installation tests pass with the following triplets:

x64-windows

To be clear, no change requested. Just want to make sure I understand how a thing is intended to be used to do a good job reviewing it before signing off. Thanks for the updates!

Can you explain what this script is doing and add ...

and

To be clear, no change requested. ...
...

Sorry for my late reply. The intention of the script is acquisitioning the port glslang version 14.3.0 that it is releasing two version for the same revision (fa9c3de released with 14.3.0 and vulkan-sdk-1.3.290.0), different with port vulkan-sd-components version 1.3.290.0
I plan to streamline the script and add instructions. I will reopen this PR after modification.


Expose Remarketing Tags In API

Hi All,
In v201809 of the AdWords API we could query the CustomerService for the RemarketingSettings in order to get the Remarketing Tags ( called snippet in the API object model ) for the account:
https://developers.google.com/adwords/api/docs/reference/v201809/CustomerService.RemarketingSettings

As of V6 of the Ads API I'm still not sure where to find that data via the API. I brought it up with the AdWords API forum back in January and they said they put in the feature request:
https://groups.google.com/g/adwords-api/c/BD3cC-Ht4_o

Are the remarketing tags currently exposed via the Ads API? If not, is there a roadmap for them? It's one of the last hurdles for our complete migration from AdWords API to Ads API.
Thanks
Pete

This is available from ConversionAction.tag_snippets.

Nick,
It's not the same data.
AdWords API v201809 customer.getRemarketingSettings().getSnippet() gives a JS snippet that looks like this:

The ConversionAction TagSnippets for the same customer through the Ads API does not contain the above data.
Pete

I'll chime in here, as I was involved in some of the changes made in the Google Ads API around this feature. The AdWords API blurred the line between "conversion action" and "remarketing action", so we decided to officially make them separate concepts in the Google Ads API, as they are in the UI.
I'll look through our notes to see if I can shed more light on this.

I'm guessing that this is the correct resource? remarketing_action.tag_snippets

Right, but @PeterLavetsky mentioned in the forum post that tag_snippets was empty in responses. I'm looking into the example provided there.

@PeterLavetsky , I'm not seeing any remarketing actions on the account you mentioned on the forum. Could you try with another account and let us know if you get back snippets? The response:
Body: field_mask {
  paths: "remarketing_action.id"
  paths: "remarketing_action.name"
  paths: "remarketing_action.resource_name"
  paths: "remarketing_action.tag_snippets"
}

Means that no rows were returned.

Full disclosure: I'm working with a different customer today than the customer from the forum post in January but the two customers are in the same boat: no remarketing actions exist but they do both get a remarketing snippet back from the AdWords API.
My current thought process is to construct the remarketing tag manually since the only piece of dynamic data in the JS snippet appears to be the google_conversion_id and I do get that value back from the Customer resource:
customer.getConversionTrackingSetting().getConversionTrackingId()

However it seems a little loose and prone to errors if Google changes that JS code in the future.
In the meantime I'll look for another account that does have remarketing actions and see if the snippets come back there.

I looked through a couple dozen accounts and didn't find any remarketing actions.
However I did move forward with manually constructing the remarketing tag using the conversionTrackingId found on Customer and I've been able to achieve parity that way.
Assuming that JS snippet doesn't change much ( hardly ever? ) I should be able to make this solution work.

Thanks for the update. I'm checking in with some folks on our side to try to get more info on why this changed.

I filed a feature request to have this added to the API, but I don't have a timeline at this point. One of the challenges is that unlike the conversion event snippet, the remarketing event snippet requires further customization after you retrieve it (there are some placeholders in there for values you need to update), so the snippet is not ready for use "out of the box".
I'll close this library issue, but if and when we add this to the API, we'll be sure to include it in the appropriate version's release notes.
Thanks,
Josh

I filed a feature request to have this added to the API, but I don't have a timeline at this point. One of the challenges is that unlike the conversion event snippet, the remarketing event snippet requires further customization after you retrieve it (there are some placeholders in there for values you need to update), so the snippet is not ready for use "out of the box".
I'll close this library issue, but if and when we add this to the API, we'll be sure to include it in the appropriate version's release notes.
Thanks,
Josh

Cool ... thanks @jradcliff

Cool ... thanks @jradcliff


Create maskduck.localplayer.dev.json

Requirements

[x] You have completed your website.
[x] The website is reachable.
[x] The CNAME record doesn't contain https:// or /.
[x] There is sufficient information at the owner field.
[x] Your website is not hosting on the following due to SSL issues: Vercel, Netlify

Description

weird purposes idk what to describe
Link to Website

https://maskduck.github.io
NOTE: the CNAME is pointed to maskduckos.github.io which means that this won't cause any problem with any one-custom-domain rule

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request


Whether to support yolov4-tiny,and outputing of the target box

Thanks for your work, I noticed that the final detection result does not seem to output the coordinates of the target frame (like x, y, w, h), is my understanding correct? Can you add the function of outputting the coordinate boxing to the code?

Whether to support yolov4-tiny

Yes.  Please refer to Demo #5: YOLOv4 for details.

I noticed that the final detection result does not seem to output the coordinates of the target frame (like x, y, w, h), is my understanding correct? Can you add the function of outputting the coordinate boxing to the code?

Please refer to utils/yolo_with_plugins.py.  The TensorRT yolov4/yolov3 engine would output x, y, w, h (in the range of 0.0~1.0).  And the _postprocess_yolo() function would convert them into x1, y1, x2, y2 (or xmin, ymin, xmax, ymax) in "pixels".  Also refer to this line of code.
        boxes = np.concatenate([xx, yy, xx+ww, yy+hh], axis=1) + 0.5
        boxes = boxes.astype(np.int)

cool!Thank you for such a quick response, I will try your code.


Unit_Converter

This is the project  where I have made a basic unit converter(feet-inches) with the help of HTML , CSS & JS

I know how to make an interactive Unit Converter and have worked with the same previously. Please assign me this issue in GSSoC'23.

I can easily make an interactive unit converter using HTML, CSS, JS.
Could you assign it to me?

Sir/Ma'am please assign me the issue.


Added International Electronic Business College

School Name
Added International Electronic Business College
Official Site
https://www.kbc.ac.jp/
IT Engineering
https://www.kbc.ac.jp/course/it-engineer/

@Yuta26462 Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Fabric leaks the default device on exception

Bug description
See reproduction below
What version are you seeing the problem on?
master
How to reproduce the bug
import pytest
import torch

import lightning as L
from lightning.fabric.plugins import HalfPrecision

class MyPlugin(HalfPrecision):
    def init_context(self):
        # arbitrary error
        raise NotImplementedError

fabric = L.Fabric(devices=1, accelerator="cuda", plugins=MyPlugin("16-true"))

with pytest.raises(NotImplementedError):
    with fabric.init_module():
        pass

default_device = torch.tensor(0).device
assert default_device.type == "cpu", default_device

Error messages and logs
The assertion fails
Environment
Current master
More info
This blocks https://github.com/Lightning-AI/lightning/pull/18704

Could this be resolved by resetting the device in a finally-block?

I thought torch.device implemented __exit__. If not, then we would need to write our own context manager that does it

Your example should be
from contextlib import ExitStack
import pytest
import torch

ctx = ExitStack()
ctx.enter_context(torch.device("cuda:0"))

with pytest.raises(NotImplementedError):
    with ctx:
        raise NotImplementedError()

default_device = torch.tensor(0).device
assert default_device.type == "cpu", default_device

which does work as expected.
I found the cause of this issue. I'll open a PR


 IF YOU DO NOT FOLLOW THE FORMAT OR MAKE A GENERIC TOKEN REQUEST YOUR ISSUE WILL BE DELETED WITHOUT COMMENT
YOUR JUSTLIST MUST FOLLOW THE JSON SPECIFICATION
{
"name": "QuotesToken",
"logoURI": "https://quotestoken.com/img/quotestoken.png",
"timestamp":<PHONE_NUMBER>000,
"tokens": [{
"chainId": 1,
"address": "TTjxdJA5fH6DF3YXEYBgSBwg9S7hqRfo6r",
"name": "QuotesToken",
"symbol": "QTN",
"decimals": 18,
"logoURI": "https://quotestoken.com/img/quotestoken.png"
}
],
"version": {
"major": 1,
"minor": 0,
"patch": 0
}
}
Checklist

[x] I understand that this is not the place to request a token listing.
[x] I have tested that my JustList is compatible by pasting the URL into the add a list UI at justswap.org.
[x] I understand that filing an issue or adding liquidity does not guarantee addition to the justlists website.

Please provide the following information for your token.
JustList URL must be HTTPS.
JustList URL: https://tronscan.org/#/contract/TTjxdJA5fH6DF3YXEYBgSBwg9S7hqRfo6r
JustList Name: Quotes Token
Link to the official homepage of the JustList manager: https://quotestoken.com

Hi, mmirabi,thanks for reaching out. We are currently very tight on development resources and adding new lists, If timing is a key issue for you, we recommend you join the existing community SUNSWAP list, for example: Tron Alliance List: https://github.com/listtronalliance/tronalliance.
Thanks
Note:
If the token satisfies the following four conditions, it will be automatically added to the "Tron Alliance List" :
1.The token page on Transcan has a official website
2.The token page on Transcan needs at least 1 social profile
3.In order of liquidity from most to least, select the top 10 tokens with 24-hour trading volume greater than $10,000.
4.If the tokens move back in the liquidity rankings or 24 hours trading volume less than $10,000 , the token will be removed


test(toberemoved):jenkins merge pr with right branch

just a test for jenkins, will be removed

Pull request test result: failure :x:

Pull request test result: failure :x:

Pull request test result: failure :x:

Pull request test result: failure :x:

Pull request test result: failure :x:

Pull request test result: failure :x:

Pull request test result: success :star:


Enhancing the timepicker

Hey, thanks for the library.
I was wondering if there is a way how to extend the functionality in order to achieve something like this:

Thanks!

Hi @chmln
Thanks for your reply. Sure, I think this currently comes from http://amsul.ca/pickadate.js/time/
Would be nice to have a similar enhancement. I'm currently working on a project, migrating from jQuery to Vue.js and your library is great to use along Vue.js and I'm currently using your library as a date picker and I would love to use it also for the time picker too.

Hi @chmln
Thank you for this awesome library.
Are there any plans to add this feature? Many of my users are craving for a timepicker in dropdown format :)
Cheers


The specified module was not loaded because no valid module file was found in any module directory.

Just installed the module through the Powershell ISE.
Import-Module Autotask
$securepassword = ConvertTo-SecureString -string "PASSWORD" -AsPlainText -Force
$Credential = new-object System.Management.Automation.PSCredential ("USERNAME", $securepassword)
$ApiKey = "APIKEY"
Connect-AutotaskWebAPI -Credential $Credential -ApiTrackingIdentifier $ApiKey  -Verbose

Lots of verbose output...
VERBOSE: Removing the imported "Set-AtwsUserDefinedFieldDefinition" function.
VERBOSE: Removing the imported "Set-AtwsWorkTypeModifier" function.
VERBOSE: Removing the imported "Connect-AutotaskWebAPI" alias.
VERBOSE: Populating RepositorySourceLocation property for module Autotask.
VERBOSE: Loading module from path 'C:\Program Files\WindowsPowerShell\Modules\Autotask\<IP_ADDRESS>\Autotask.psm1'.
Import-Module : The specified module 'C:\Program Files\WindowsPowerShell\Modules\Autotask\<IP_ADDRESS>' was not loaded because no valid module file was
found in any module directory.
At C:\Program Files\WindowsPowerShell\Modules\Autotask\<IP_ADDRESS>\Public\Connect-AtwsWebAPI.ps1:80 char:7
+       Import-Module -Name $ModulePath -Global -Prefix $Prefix -Force
+       ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (C:\Program File...utotask\<IP_ADDRESS>:String) [Import-Module], FileNotFoundException
    + FullyQualifiedErrorId : Modules_ModuleNotFound,Microsoft.PowerShell.Commands.ImportModuleCommand

The files are there, not sure what the problem is.
Also tried loading the module directly with the parameters, but getting an authentication error. User is setup with the API key, credentials and user is set to API user. Also tried full access.

Thanks! This is so awesome. The fact that you auto-generated these methods from the API is AMAZING.
Where would I look to find out how you did that? Seems like something I could use in other projects and programming languages.

Sorry, I didn't see this comment before now since you closed the issue - I have a bit of backlog in my mailbox... 😊
All the code is included in the module. Most of what you would want to look at are in the Private subdirectory. The convoluted part is the caching. The functions are generated from templates (*-AtwsDefinition.ps1). I use .EntityInfo() to determine which methods are supported (get, set, new, remove) and I use .FieldInfo() to determine which parameters to include and how to validate them. The core of the module is an inner and outer foreach loop:
Foreach ($Entity in $Entities) {
  $Fields = $Atws.GetFieldInfo($Entity.name)
  Foreach ($Field in $Fields) {
    # a lot of stuff
  }
}

The challenge is that looking up fieldinfo is slow. To look up fieldinfo for 134 entities every time you load the module was annoyingly slow. So I started caching it. That became complicated rather quickly. But it feels like it is almost there now :)