if all properties in a struct are readOnly, do not serialize this struct when sending request

Feature Request

track1 go sdk
bug encountered: if a resource enable user assigned identity, it's common that we get the resource first, then modify the fields and fire the update api request.  The backend service will report error:
Invalid value for the identities '/subscriptions/sub-id/resourceGroups/resource-group-name/providers/Microsoft.ManagedIdentity/userAssignedIdentities/identity-name'. The 'UserAssignedIdentities' property keys should only be empty json objects, null or the resource exisiting property."

this cause a lot of trouble for users
https://github.com/terraform-providers/terraform-provider-azurerm/issues/10406

Hi @ArcturusZhang , any progress on this issue?


Update navan-tutorial.md

I am including updated information and URLs as we (the Navan team) have updated our SSO integrations and have rebranded from TripActions to Navan. Thank you!

@jeevansd
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#please-close


feat: support WOFF2 to SVG

Use woff2-rs to decompress woff2 fonts.
Add a comparison between TTF and WOFF2 after converting to SVG on the test page.

Very cool, ty.


Expose System.Console.KeyAvailable to the SystemConsole implementation

oh, that'd be a good idea - do you think you could add KeyAvailable all the way up the chain? eg. add it to the IConsole interface and implement the property in every class that implements it?

Yeah no worries, will commit it when done

Commit also fixed some formatting to comply with your code style

it appears every implementation only checks System.Console.KeyAvailable - if I were to create my own class that implements IConsole and modify the implementation of KeyAvailable and use one of the existing console interfaces to wrap around it, it wouldn't properly fall back to my implementation - it would rely on System.Console. Can you make it so that every KeyAvailable relies on the backing IConsole it gets passed (except for SystemConsole of course)?

that looks good, thank you :+1:


updating rust deps and repairing CI with deps

Update rust pnet dependency to move past a release with potential vulnerabilities.
Update CI to install dependencies before golang-ci lint job (fixing broken CI job)
Remove now unused rust crate

The missing file for pebbe/zmq4 is no longer missing and the golangci-lint job now works. It does show that there are some lint issues, however those should probably be addresses in a separate PR.


Update welcome message from OSPR bot with info and checklist for authors

Story
"As an author of an OSPR (open source pull request), I want to get a useful welcome message after posting my PR so that:

I know where to look for relevant information about the OSPR process if/when I need it.
I know which steps I need to complete to get my PR ready for engineering review.
(maintained repos only) I know who to ping for engineering review."

Full description
One important aspect of reducing time-to-merge for OSPRs is to empower PR authors to manage more parts of the OSPR process themselves.
For that, they'll need:

Easy access to information about the OSPR process as a whole that they can reference as necessary.
A clear list of expectations that maintainers have of them, i.e., a checklist of steps/requirements that they must complete before their PRs can be considered ready for engineering review (including creating  product proposals and feature tickets retroactively if their PRs include user-facing changes).

For maintained repositories, they should also get information about who to ping when they're done completing prerequisites for engineering review (e.g. @2u-aurora).

Note: As determined by the maintenance working group, the OSPR bot should not ping maintainers of a repository directly in the welcome message. Instead, it should enclose mentions of maintainers in backticks: `@2u-aurora`.

Information about the maintainers of a repository can be extracted from its catalog-info.yml (example).
Completion criteria

[x] Draft new welcome message.
[x] Have the bot post the new welcome message instead of the existing one.
[x] Implement support for retrieving maintainer info and adding it to the welcome message (if available).

Behavioral specifications
N/A (doesn't change current behavior of OSPR bot, just its messaging)
Documentation updates & improvements criteria
Left to the assignee’s appreciation
Relevant repositories

https://github.com/openedx/openedx-webhooks, and in particular:

https://github.com/openedx/openedx-webhooks/tree/master/openedx_webhooks/templates
https://github.com/openedx/openedx-webhooks/blob/master/openedx*webhooks/templates/github_community_pr*comment.md.j2

Review timeline
Flexible.
Notes
According to Feanil:

openedx-webhooks code is gnarly, feel free to ping #openedx-webhooks  for help

@feanil @mphilbrick211 @sarina @jmakowski1123 FYI, this is a copy of the OpenCraft ticket that I scheduled for next sprint (starting Tue Apr 16).

Draft of new welcome message is available here.

Hi @itsjeyd - I'm concerned about this line:

This repository is currently maintained by @{{ maintainers }}. Tag them in a comment and let them know that your changes are ready for review.

I don't think we'll know who the maintainers are in a standard pattern. Could you reword this to explain how to find the maintainers (either by using Backstage or viewing catalog-info.yaml within the repo? (I think it would be better to direct to Backstage, personally)

@sarina FYI, the code is looking at the catalog-info.yaml files on the repo to determine the maintainer so it should be up-to-date.  It might get cached for a bit so could be out of date temporarily but not on any large time scale.

 I guess I don't know anything about the bot these days. Are you going to be able to add in the new message?

@sarina Sorry for the delay in getting back, I was out sick for two weeks and working through my e-mail backlog has been taking some time.

Are you going to be able to add in the new message?

The PR for that is here: https://github.com/openedx/openedx-webhooks/pull/288

@itsjeyd great. Seems like you have a good set of reviewers over there, so I'll let that team finish it up.

Sounds good, thanks @sarina.

https://github.com/openedx/openedx-webhooks/pull/288 has been merged so we're done here 🎉

https://github.com/openedx/openedx-webhooks/pull/288 has been merged so we're done here 🎉


PREPARE BASE MODEL

[ ] Adding Config yaml
[ ] Adding config_entity for dataclass config
[ ] configuration created
[ ] component created
[ ] pipeline builded
[ ] prepare base model finished


Migrate and write up procedure for staging.dockstore.org migration to cloudfront

Feature Request
Desired behaviour
Come up with a plan to migrate staging.dockstore.org
Record length of / minimize outage
Write up docs to use as a model for a similar migration for dockstore.org
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Sprint: Seabright Sprint 16 Pram
┆Issue Number: DOCK-862
┆Epic: Serve UI from s3/CloudFront

➤ Denis Yuen commented:
https://wiki.oicr.on.ca/display/DOC/Cloudfront ( https://wiki.oicr.on.ca/display/DOC/Cloudfront ) will need updates due to our latest approach
(i.e. no edge lambda, no cname)
Should also clean up old cloudfront distro, lambda, etc. if confirmed


There is no repository for ubuntu yakkety

I am trying to install freerdp-nightly on ubuntu yakkety, from xenial
deb http://pub.freerdp.com/repositories/deb/xenial/ freerdp-nightly main
But it not work, i have following errors:
sudo apt-get install freerdp-nightly
Reading package lists... Done
Building dependency tree
Reading state information... Done
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 freerdp-nightly : Depends: libavcodec-ffmpeg56 (>= 7:2.4) but it is not installable or
                            libavcodec-ffmpeg-extra56 (>= 7:2.4) but it is not installable
                   Depends: libavutil-ffmpeg54 (>= 7:2.4) but it is not installable
E: Unable to correct problems, you have held broken packages.

@dementro5 ubuntu 1610 isn't supported  as our build machines aren't upgraded yet. I have it on my todo and have a look once there is a calm minute.

bmiklauz, thank you!

yakkety is EOL, closing


Problem with Logistic Pipes

OpenPeripheral break the original functionality of the Logistic Pipe's pipes.
Example with a Request Pipe;
Instead of being able to do .makeRequest() to request an item to pass through it,
the pipe returns functions related to MJ such as .getMaxMJReceived() and .getTankInfo(), which is completely unrelated to the pipe's original purpose, not only that but all these MJ functions doesn't even return something.
Is there a way/config to disable OpenP from overriding methods from other mods peripherals?

The modid is not LogisticsPipes|Main
it is just LogisticsPipes
I looked in the code itself, under the @Mod annotation:
modid = "LogisticsPipes"

Uhmm, This issue is 3 years old. While mechanism of blacklisting TEs remains unchanged, target mod was probably rebuild multiple times.

Hey,
i have the same problem with Logistic Pipes and OpenMod. Where and how i input the Blacklist? Pls write a little manual, what we have to do. The comments are not helpful enough :/
A fixed version of the mod will be the best solution i think.

Uh, this issue is not related to OpenPeripheral - just Logistic Pipes ignoring getSubItems on one of the OpenBlocks items. Also, is completely harmless.
Besides, 1.7.10 is unsupported.


refactor operator-framework-e2e

Description

Adds a script called setup.sh to perform all the setup logic for the coast-to-coast e2e test

This makes it easier to read and modify the setup logic in the future

Removes obsolete Go code and updates the Ginkgo tests as necessary
Removes obsolete Makefile targets and updates the Makefile as necessary

The combination of the changes here makes the test still generally do the same things of:

Create a temp directory for building operators
Use the operator-sdk to:

create two operators and build their images, one for the registry+v1 and one for the plain+v0 bundle formats
generate and build the bundle image for the registry+v1 bundle format

For the plain+v0 operator, create and build the plain+v0 bundle image
Creates a File-Based Catalog (FBC) image that contains both the operators
Load the operator, bundle, and catalog images onto a KinD cluster
Clean up the temp directories
Run the Ginkgo test suite that:

Creates a Catalog that references a catalog image, either the one with the plain+v0 bundle or the one with the registry+v1 bundle
Creates an Operator that references a package, either the one with the plain+v0 bundle or the one with the registry+v1 bundle
Verifies that the Operator eventually has the condition Installed with a status of True and a reason of Success

Motivation

Makes it easier to read and modify the operator-framework-e2e test. Particularly it will help with making the e2e changes needed for #475 easier
resolves #482

Open Questions

The previous implementation included "upgrading" an operator by changing its .spec.version to be the "new" version. This implementation does not have that and instead focuses on the coast-to-coast of build, package, deploy. Is it necessary to include the "upgrading" of an operator as part of this e2e test?

Reviewer Checklist

[ ] API Go Documentation
[ ] Tests: Unit Tests (and E2E Tests, if appropriate)
[ ] Comprehensive Commit Messages
[ ] Links to related GitHub Issue(s)

Correct me if I'm wrong, but it seems that both #349 and #350 are resolved by this since we no longer use local-registry.

#350

Looks like it. I looked through the issues to try and find the ones this resolved and missed these. Will add them as resolved to the PR description, thanks!

Re: go-apidiff - we removed a bunch of e2e helper functions which were exported. I think we can ignore this.


Tower lab license

We need to document and/or automate licenses to run Tower in a lab environments.

Currently uploading to S3 (a day or so prior to the workshop) and have the students reference it during the workshop.

Each student should apply for a 5-day 5-node trial license here: https://www.ansible.com/workshop-license. License files is delivered to their inbox usually in 1 to 2 minutes.


Automate releases

Currently, releases are manual. We could automate this with something like rever and github actions

Needs further discussion, specifically to specify what problems this solves and the cost of implementing it.

I think @danlester was working on something related to this, no?

Yes, I think we have a more streamlined release process now, so let's let this issue close.

Oh except it won't be closed now because we've commented on it! (That makes it un-stale)


Review Aligment uses and definitions

BEGIN_COMMIT_OVERRIDE
docs: Update definition of Alignment and json files.
fix(BCard): Set correct align types.
fix(BNav): Set correct align types.
fix(BNavbarNav): Set correct align types.
feat(BPagination): Extend justify content types for between, around and evenly
fix(BPagination): Set correct align types.
fix(BTabs): Set correct align types.
fix(BRow): Set correct align types.
END_COMMIT_OVERRIDE
Describe the PR
In external projects, using an IDE like IntelliJ is taking problems to go directly to each definition of the Alignment namespaces, because we have a conflict naming for the type "Alignment" and the namespace "Alignment".
During the check also I see another problems like: definining a namespace as a type in props. No correct type definitions for text alignment, no correct definitions for justify content aligment, mixing "fill" type from Navigation as a justifify content alignment.
PR checklist

What kind of change does this PR introduce? (check at least one)

[x] Bugfix :bug: - fix(...)
[x] Feature - feat(...)
[ ] ARIA accessibility - fix(...)
[x] Documentation update - docs(...)
[ ] Other (please describe)

The PR fulfills these requirements:

[x] Pull request title and all commits follow the Conventional Commits convention or have an override in this pull request body This is very important, as the CHANGELOG is generated from these messages, and determines the next version type. Pull requests that do not follow conventional commits or do not have an override will be denied

How about instead we refactor this to remove the namespace. Essentially, just remove the namespace and append Alignment to the keys. VerticalAlignment, HorizontalAlignment, etc.

While we were trying to use the newest version, we saw that we have a problem using the directive tooltip (bad configuration with who is the root element with the assigned directive like v-b-tooltip.top.hover and the title is missing.
So, no value defined for the directive and no title, and we are trying to use an undefined value with the method "toString". Maybe we can create a warning in that case, that allows the developers to review when we try to use the directive, but it wasn't possible to retrieve the title.
With this change the error is silent, a warning is good, but no generating an error. what do you think?

Not sure what you mean

While we were trying to use the newest version, we saw that we have a problem using the directive tooltip (bad configuration with who is the root element with the assigned directive like v-b-tooltip.top.hover and the title is missing.
So, no value defined for the directive and no title, and we are trying to use an undefined value with the method "toString". Maybe we can create a warning in that case, that allows the developers to review when we try to use the directive, but it wasn't possible to retrieve the title.
With this change the error is silent, a warning is good, but no generating an error. what do you think?

Not sure what you mean

I mean, since this PR https://github.com/cdmoro/bootstrap-vue-3/pull/647/files the directive related for Tooltip is error prune to having this error:

So, the code is not taking care of the possibility of a bad configuration, and it's going to break other projects. With this PR the error is gone, because I'm taking care of the possibility of returning an undefined value, but...
I guess to help other developers is good to display a warning message to say something like: "Please, review tooltip directive usage. Some uses are not defining a title in root component or a value like "v-b-tooltip=xxx"  to define a title".
And also, I guess there is a lack of documentation about using this directive.

Ultimately I don't think it's a good use of time since eventually I would like to go through and rebuild the directives. But you're free to implement that change if you want. An error message, and perhaps a doc update if you'd like.

Why did the tests need to change?

Why did the tests need to change? Specifically im referring to card.spec.ts

Because "fill" type wasn't a valid type for text horizontal alignment.
https://github.com/cdmoro/bootstrap-vue-3/pull/794/commits/14d0f1ea31edb11ebc8cef728f045e4da942b605
In Bootstrap 5 doesn't exist "text-fill" as a type alginment.
https://getbootstrap.com/docs/5.2/utilities/text/#text-alignment
https://getbootstrap.com/docs/5.2/components/card/#text-alignment
So, the text was trying to validate that we generate a string with the prefix "text-" with the given value, but "fill" in this MR is not a valid one.
Also, in bootstrap-vue (2) you can find the same:
https://bootstrap-vue.org/docs/components/card#horizontal-card-layout


iOS: MPA functionality proof-of-concept

Have a hard-coded square overlaying some of the map area to represent a Marine Protected Area. This should show up in the map screens, so the officer can see if they are within the borders of the MPA. There is no additional functionality associated with this (e.g. they are still allowed to board a vessel outside the MPA)

Here's example of a polygon to overlay:
{ name: Galapagos,
points: [
[-0.534202465, -88.03310394],
[-2.811371193, -88.28613281],
[-2.635788574, -93.12011719],
[-0.790990498, -95.14160156],
[2.372368709, -96.28417969],
[4.302591077, -94.26269531],
[3.250208562, -91.01074219],
[-0.534202465, -88.03310394]
] }

The data will be stored in the MenuData table.

Design - https://mongodb.invisionapp.com/console/share/8XXUAUP2YZS/587697149

from the ui for the MenuData table:


Return certificate chain for export cert

Signed-off-by: Alexander Wels<EMAIL_ADDRESS>
What this PR does / why we need it:
Before we returned just the found certificate and not the entire chain. To properly verify the certificate you must have the entire chain. This commit looks up the chain until either we find the root CA or we can't find anything else in the config map.
Also checking the OnBefore and OnAfter times, to figure out which cert is most valid in case of a cert rotation and the bundle containing multiple valid certificates.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Release note:

NONE

/test pull-kubevirt-unit-test

/lgtm
/approve

/cherrypick release-v0.58


fix: Consume digest from step output

Description

Part of https://github.com/kubewarden/kubewarden-controller/issues/938

Test

release job test:
https://github.com/viccuad/audit-scanner/actions/runs/12318153026

Additional Information
Tradeoff

Potential improvement

testing job passed (besides triggering the helm-charts repo), merging.


Change module and jsnext:main to provider.esm.js

When running Snowpack, when installing @bootstrap-styled/provider, it was looking for<EMAIL_ADDRESS>when it didn't exist.

Thanks !

@seendsouza , released failed : https://travis-ci.org/github/bootstrap-styled/provider/jobs/750616644
Would you mind fixing the error and redo a MR? You can test it first locally with npm run test. I'll repass your PR asap.

:tada: This PR is included in version 2.0.3 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Android Flick

Description
When rendering a LottieView component, we want to change the animation between the animated and the idle. When it comes to state changing (which, in consequence, will render the other animation), an ugly flick can be seen (ONLY in Android) until the next animation is fully rendered.
According to one of the contributors, this is a common bug know by them but they have no solution for the moment. It might be related to an old version on 'lottie-android' used in the last version of 'lottie-react-native'. Updating it leads to compilation errors which we could not solve.
Steps to Reproduce

Create app with Lottie React Native installed
Drop a Lottie View with a JSON animation on the render
When the animation finishes, change the state in order to render another animation.
A flick will be seen in between that animation change

Snack Expo test app: https://snack.expo.io/@jescandarani/lottie-test (only reproducible on real Android device)
Expected behavior: A normal transition between the animated and the idle animation.
Actual behavior: A flick can be seen in the transition between the animated and the idle animation.
Versions
You can get this information from executing npm version.
"lottie-react-native": "2.5.9",
"react-native":"0.57"

I did some investigation myself and this is indeed an issue with the old lottie-android used in lottie-react-native. We would need to update the dependency and make sure it compiles correctly.


CustomSHA256 doesn't seem to be used when uploading object

Hi,
I'm trying to use a custom implementation for computing SHA256 checksums (I want to use the AVX512 version of sha256-simd) but my custom function is never called. In which circumstances the CustomSHA256 function provided when creating minio.Client is used?

Described here: https://github.com/minio/minio-go/blob/cb21d7dd9e4faec51eb6125f008ae0e7d8414960/api.go#L312


upscayl: resolve hash mismatch for 2.9.9

Description of changes
Somehow when building upscayl v2.9.9 now we are greeted with a rather strange hash mismatch error that had not been encountered during the review phase of #287665.
Fixes #291914.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 292017 run on x86_64-linux 1

1 package built:

upscayl


Adds 'config' option to specify location for a PostCSS config file

Resolves #40.

Coverage remained the same at 100.0% when pulling 1eb40c24d7410515d7d118d81f34be9d9df8d4d4 on chrisngobanh:master into 0ed60b097025dba3105dc326737a8384e0e430d9 on wbyoung:master.

Coverage remained the same at 100.0% when pulling b3f357956ebffbb305cd1bfc40cdd1832d593bea on chrisngobanh:master into 0ed60b097025dba3105dc326737a8384e0e430d9 on wbyoung:master.

Can we do a 0.3.0 release after this is merged?

@chrisngobanh published. Thanks for the PR!


Further gradle build improvements

Further updates to the gradle build as per #3370

Initial attempt at enabling one FVT (asset-consumer) within the gradle build

By ensuring the gradle build has the existing FVTs we can be more confident it is generating a good build/package,
and we can then use this as a base for more, longer tests - such as for docker, UI, with confidence.
The gradle build is also much quicker and more flexible so an ideal place to add further testing
Note: Interim update - the fvt platform is launched, servers configured, but actual tests not run (yet)

still in progress.

still in progress.

Gradle build currently failing with:
Error: Unable to access jarfile ../../../../../open-metadata-distribution/open-metadata-assemblies/build/unpacked/egeria-2.8-SNAPSHOT-distribution.tar.gz/server/server-chassis-spring-2.8-SNAPSHOT.jar

Since the FVTs use the packaged jar for testing, and it's not present, the tests fail.
This is a good test and was as intended.
Investigating root cause (typically works second-time, so timing related)

The server launch was failing as the FVT server start task was depending on the zipped distribution archive, rather than the unpacked tar.
So sometimes the server existed (as the untar occurs immediately once the zipped archive is created), but often it did not...
Should be an accurate task dependency now


timestamps support in embedded_schema

I wasn't able to get timestamps support in embedded_schema. In result timestamp fields are nil for all embedded documents but it works fine for regular documents. Do i miss something, is there a way to get timestamps support for embedded_schema?

I realize this issue is really old, but it is still an issue which I assume is why it's still open. Since mongoldb_ecto 1.0 is in beta, I assume this is a bug that would need to be fixed before the final release.
When using the timestamps macro from Ecto.Schema in an embedded schema, the inserted_at and updated_at field values are always nil/null.

@bdtomlin This is a good question! I'm not quite sure how that would be implemented, but my guess is it wouldn't be straightforward conceptually or technically and possibly impossible. Timestamps can be set on the root document whenever it's created/updated, but embedded documents don't have quite as clean of a lifecycle. For instance, I could insert a bunch of comments into a post document and then create the post -- what timestamp do the comments get? Is it the timestamp of when they were added to the post struct or when the post was inserted into the DB? In terms of implementation, my guess is the implementation of timestamps on the root document is straight forward (e.g. add a $set on all the insert* or update*` functions) but how do you implement it on embedded documents that might be embedded deep in a tree?
I'm going to close this for now as I don't see a path forward for this feature. However, if anyone has any ideas on how to implement this, I would welcome the PR and would love to hear ideas on how to make it happen!

@scottmessinger,
Mongoid handles this with what it calls cascading callbacks. That name gives a pretty decent hint of a way to handle it. https://docs.mongodb.com/mongoid/current/tutorials/mongoid-relations/#cascading-callbacks
I will try to come back to this in the future, but I think it would help to leave it open so it still has visibility for me or anyone else who may need this feature and has some time to work on it.


"(sw *StreamWatcher) receive()" receive io.EOF  every 30~50 minittues?

I use client-go to watch k8s service and endpoints like this:
clientset.CoreV1().Services("").Watch(metav1.ListOptions{})
But every 30~50 minittues，the StreamWatcher will receive the io.EOF.
"(sw *StreamWatcher) receive()" receive io.EOF and stop.
And I have to watch again.

It is normal for the apiserver to timeout watch requests and for clients to have to reestablish them

@liggitt
Thanks!
So I have to re-watch when apiserver timeout?

yes. the helpers built on top of StreamWatcher (cache.Informer, which uses ListerWatcher) do this for you, and call add/update/delete handlers you specify
see https://github.com/kubernetes/kubernetes/blob/master/staging/src/k8s.io/client-go/examples/workqueue/main.go#L164-L195 as an example

/close


Bad results

I am getting some very poor results. I am using the single_image script and resizing images to 512,512

Can some of the images + masks from the showed resuts can be shared? This way I could verify if I did something weird

Hi~
I have testes your image, and the result is as follow:

Besides, I also upload our test images to directory "test_imgs".

Thanks a lot, I will check whats happening. Just to make completely sure, the mask you send to the network is the 3rd image, not the second, correct?

Yes, you are right. We send the 3rd image as our mask.

Hi,
For the test images it does indeed work well. However, for single_image_test, the image needs to be 2^k. How did you do the resizing of the image for my example?

Removing center cropping fixed it for me


Support ServiceLoader loading of typesafe config

Part 1 - the easiest.

Nice, thanks. I will merge it once I figure out why the build fails on travis.


Use fsPath instead of path for config file

The problem was that a config file path like
'/c:/something' was being used instead of the
correct path 'c:\something'.
This is the solution suggested by @fluxium.
Unfortunately a number of other changes were
necessary to make the extension build again
with the latest packages on Windows. Then there
were a number of new lint messages checked, and
new messages because of a newer typescript.
I think I got them all fixed except the cypress test
is failing due to some missing monaco element.
This is likely caused by a dom change in a new version
that needs to be accomodated in the test case.
Closes #???
Description

For contributor use:

[x] Targeted PR against master branch
[x] Linked to Github issue with discussion and accepted design OR link to spec that describes this work
[x] Code follows the standards mentioned here
[x] Updated relevant documentation
[x] Re-reviewed Files changed in the Github PR explorer
[ ] Added appropriate labels

Sorry I forgot to mention:
Fixes https://github.com/onflow/vscode-cadence/issues/57

How do I fix this synk error:
`snyk` requires an authenticated account. Please run `snyk auth` and try again.

How do I fix this synk error:
`snyk` requires an authenticated account. Please run `snyk auth` and try again.

Upon further investigation, it looks like "snyk test" requires an auth token, but "snyk protect" does not. The auth token requirement was added at some point, and the package.json was using an old version. When I updated it, I ran into this problem. I will revert to the old version of snyk, but really, the best solution is to provide the auth token.

Yes, that can be resolved, but maybe it's better to revert now and not be blocked by it and resolve that as part of later PR

Yes, that can be resolved, but maybe it's better to revert now and not be blocked by it and resolve that as part of later PR

It's done, how do I make it re-run the CI action?

Yes, that can be resolved, but maybe it's better to revert now and not be blocked by it and resolve that as part of later PR

It's done, how do I make it re-run the CI action?

The CI actions won't be run anymore since I've changed the base branch to be a non-master branch. You can run tests, linting and synk check locally. CI will be run after this is merged into base (submissions/issue-3/koala) branch.

I ran tests, lint, and sync check locally. Do you need me to do anything else?

I ran tests, lint, and sync check locally. Do you need me to do anything else?

No, no feel free to merge this, and for future reference I think it will be easier that you go and merge this PRs yourself (be sure to target same base branch as this PR) and then only open a PR after the milestone is complete, so we don't block each other.

I don't have permission to merge pull requests here.

Ok I must be going about this wrong. My intent was to submit a pull request to get a change into the master branch so that people can develop the extension on windows.

Are you trying to make this part of the FLIP fest? In case you are, this should stay out of master until the work is complete, because else anyone else working on this will conflict with your work. The idea is that after all milestones are completed this potentially is merged into master.

No this is not a flip-fest problem, I just needed it to be done in order to do one of the flip-fest problems. Thanks.

The bug this fixes also blocks me from working with VSCode on windows. Merging this and getting a new build of the VSCode plugin would be super helpful.

@eburnette Ok, I see, I will test the changes and merge them as soon as possible. You can continue your work by basing the branch on top of this one.


Data Catalog emtpy

First, awesome work here, really appreciate you sharing this.
When connecting to snowflake via:

$ harlequin company.region.snowflakecomputing.com:443/database?account=account&authenticator=externalbrowser

i can execute queries as expected, but the Data Catalog tab on the left remains empty. This expected?

Actually now looking at the README I bet these are related

Snowflake adbc driver seems to be the only driver that returns the xdbc_data_type from adbc_get_objects()
Snowflake adbc driver has a bug with adbc_get_table_schema() that returns adbc_driver_manager.OperationalError: IO: sql: expected 12 destination arguments in Scan, not 11

Thanks for raising this issue, those issues you pointed out shouldn't effect the data catalog. Let me try to reproduce the error on my end and see what's going on.

@paw-lu do you know if authenticator=externalbrowser requires to have SSO on your snowflake account? I am trying to use the same URI format as the one you provided but for me nothing happens and the data catalog is in a continuously loading state. The URI format I tested with is was<EMAIL_ADDRESS>so I am wondering if there is something going on with this auth method that's causing things to break.

sorry missed this comment!
i don't know if it's required, but yes, I am using SSO here


Luftdaten sensor reports unknown value for one out of two conditions

Home Assistant release (hass --version):
0.60.0
Python release (python3 --version):
Python 3.6.3
Component/platform:
luftdaten
Description of problem:
The sensor only reports one out of two conditions (humidity and P2 is reported as unknown). The api data from luftdaten seems to be fine in the same timeframe.
It might be that sensor 5637 is not providing measurements for humidity
20:28 components/sensor/luftdaten.py (WARNING)
It might be that sensor 5636 is not providing measurements for P2
20:28 components/sensor/luftdaten.py (WARNING)
Expected:
Home assistant should display P1, P2, temperature and humidity.
Problem-relevant configuration.yaml entries and steps to reproduce:
- platform: luftdaten
  sensorid: 5636
  monitored_conditions:
    - P1
    - P2
- platform: luftdaten
  sensorid: 5637
  monitored_conditions:
    - temperature
    - humidity

Additional info:
curl https://api.luftdaten.info/v1/sensor/5637/
[{"sensordatavalues":[{"value":"9.30","id":1320348971,"value_type":"temperature"},{"value":"99.90","id":1320348972,"value_type":"humidity"}],"location":{"country":"DE","latitude":"51.541","id":2840,"longitude":"7.912"},"timestamp":"2017-12-23 19:31:53","sensor":{"sensor_type":{"manufacturer":"various","name":"DHT22","id":9},"pin":"7","id":5637},"sampling_rate":null,"id":604177852},{"sensordatavalues":[{"value":"9.20","id":1320360405,"value_type":"temperature"},{"value":"99.90","id":1320360406,"value_type":"humidity"}],"location":{"country":"DE","latitude":"51.541","id":2840,"longitude":"7.912"},"timestamp":"2017-12-23 19:34:20","sensor":{"sensor_type":{"manufacturer":"various","name":"DHT22","id":9},"pin":"7","id":5637},"sampling_rate":null,"id":604183274}

curl https://api.luftdaten.info/v1/sensor/5636/
[{"sensordatavalues":[{"value":"31.73","id":1320348947,"value_type":"P1"},{"value":"15.40","id":1320348948,"value_type":"P2"}],"location":{"country":"DE","latitude":"51.541","id":2840,"longitude":"7.912"},"timestamp":"2017-12-23 19:31:53","sensor":{"sensor_type":{"manufacturer":"Nova Fitness","name":"SDS011","id":14},"pin":"1","id":5636},"sampling_rate":null,"id":604177840},{"sensordatavalues":[{"value":"36.53","id":1320360378,"value_type":"P1"},{"value":"17.42","id":1320360379,"value_type":"P2"}],"location":{"country":"DE","latitude":"51.541","id":2840,"longitude":"7.912"},"timestamp":"2017-12-23 19:34:20","sensor":{"sensor_type":{"manufacturer":"Nova Fitness","name":"SDS011","id":14},"pin":"1","id":5636},"sampling_rate":null,"id":604183262}]

I've taked a look on this and from my perspective it is a bug in python-luftdaten 0.1.1
I've created an PR to hopefully fix the issue. (https://github.com/fabaff/python-luftdaten/pull/1)
BR
Rene


feat: update android ui automator to stable 2.3.0

@axelniklasson is there an eta on when this will be released?

@DavidREntwistle Axel is on PTO right now, but I can tell you that it's coming very soon! :)

Still facing this issue after the library update PR is merged.
Waiting for flows to complete...
[Passed] app_info (1m 38s)
[Passed] nifmo (2m 2s)
Error: Exception in thread "pool-4-thread-1" java.io.IOException: Command failed (host:transport:emulator-5556): device 'emulator-5556' not found
	at dadb.adbserver.AdbServer.send$dadb(AdbServer.kt:99)
	at dadb.adbserver.AdbServerDadb.open(AdbServer.kt:137)
	at dadb.forwarding.TcpForwarder.handleForwarding$lambda-1(TcpForwarder.kt:64)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:840)


Added myself

I have added myself in the respected community of Open Source

Thnx for contributing @Devansh2005  make sure you follow me and star this repo so that you don't miss the updates and contribute during Hacktoberfest 2020.
Also resolve the conflicts.


djb2CaseInsensitiveHash may cause excessive probing with Abseil hash tables

Title: djb2CaseInsensitiveHash may cause excessive probing with Abseil hash tables
Description: My colleagues who implemented the Abseil containers (@fowles and @sbenzaquen) mentioned that djb2CaseInsensitiveHash will likely cause excessive probing with absl::{flat,node}_hash_{set,map}. StringUtil uses this hash [1] in an absl::flat_hash_set [2]. Ideally this would be built on top of the absl::Hash framework [3] instead.
Relevant Links:
[1] https://github.com/envoyproxy/envoy/blob/02a526257a013e80bc508399446aac0234c3ec4e/source/common/common/utility.cc#L472
[2] https://github.com/envoyproxy/envoy/blob/02a526257a013e80bc508399446aac0234c3ec4e/source/common/common/utility.h#L170
[3] https://abseil.io/docs/cpp/guides/hash

The only real use of this function seems to be at source/common/network/transport_socket_options_impl.cc, where it seems to be used to compute some kind of fingerprint.  It may make sense to call djb2CaseInsensitiveHash directly and delete CaseInsensitiveHash to avoid use in containers.

This use also doesn't require stability across restarts, so we could just outright migrate to absl::Hash at the same time if that makes more sense.

The absl::Hash functor adds hashing support for a type which is controlled by us and hashing implies the type needs to be instantiated. I added hashing support to Envoy::Http::LowerCaseString and added benchmarks to compare absl::Hash-based hahsing and the existing djb2-based functor in https://github.com/rojkov/envoy/pull/2.
The results for djb2-based functor:
BM_RemoveTokensLong/8                                500 ns          499 ns      1398876
BM_RemoveTokensLong/64                              3394 ns         3388 ns       206346
BM_RemoveTokensLong/512                            30048 ns        29996 ns        22904
BM_RemoveTokensLong/4096                          292963 ns       292404 ns         2328
BM_RemoveTokensLong/8192                          728479 ns       727128 ns          964
BM_CreateCaseUnorderedSet/8                          258 ns          258 ns      2707808
BM_CreateCaseUnorderedSet/64                        2160 ns         2156 ns       325820
BM_CreateCaseUnorderedSet/512                      27457 ns        27404 ns        25302
BM_CreateCaseUnorderedSet/4096                    430956 ns       430180 ns         1620
BM_CreateCaseUnorderedSet/8192                   1100068 ns      1097241 ns          642

For absl::Hash
BM_RemoveTokensLong/8                     568 ns          567 ns      1091066
BM_RemoveTokensLong/64                   3991 ns         3986 ns       176470
BM_RemoveTokensLong/512                 32421 ns        32369 ns        21365
BM_RemoveTokensLong/4096               278556 ns       278081 ns         2534
BM_RemoveTokensLong/8192               563884 ns       562856 ns         1256
BM_CreateCaseUnorderedSet/8               317 ns          316 ns      2210124
BM_CreateCaseUnorderedSet/64             2600 ns         2596 ns       275066
BM_CreateCaseUnorderedSet/512           21555 ns        21517 ns        32737
BM_CreateCaseUnorderedSet/4096         231011 ns       230574 ns         3021
BM_CreateCaseUnorderedSet/8192         486659 ns       485269 ns         1443

The current implementation works faster if the number of elements is less than 600-1000 (as it doesn't need instantiation allegedly). When the number of elements is greater than that excessive probing starts to manifest.


Bug: extra space in wrap mode of text object

This Issue is about (delete as applicable)

A bug in the API (v3.6.0)

Here is a live demo of this bug. There are 2 text objects.

The first one has wordWrap.width = 200, which has an extra space in each line end.
The second one does not have wordWrap, which works well.

Thanks for opening this issue, and for submitting a PR to fix it. We have merged your PR into the master branch and attributed the work to you in the Change Log. If you need to tweak the code for whatever reason please submit a new PR.


[SPARK-17084][SQL] Rename ParserUtils.assert to require

What changes were proposed in this pull request?
This PR renames ParserUtils.assert to ParserUtils.require. This is done because this method is used to check requirements, and not to check if the program is in an invalid state.
How was this patch tested?
Simple rename. Compilation should do.

cc @rxin

Test build #63846 has started for PR 14665 at commit e611071.

Test build #63846 has finished for PR 14665 at commit e611071.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63846/
Test PASSed.

Merged build finished. Test PASSed.

Test build #63862 has started for PR 14665 at commit d9b4bb1.

LGTM pending Jenkins.

Test build #63862 has finished for PR 14665 at commit d9b4bb1.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/63862/
Test PASSed.

Merged build finished. Test PASSed.

Merging in master/2.0.


Adding switch support

Simple new device type being added.

Doesn't seem like he's done anything with this repo since his last release at 1.3.0. Can you publish your source with homebridge so other can use it until he updates?

I'd be happy to!  This is the first time I've done this (I needed to add
the wall switch) so I'm not entirely sure how to go about publishing the
source with homebridge.  Are you wanting it to be verified with Homebridge
or something else?
On Sat, Oct 21, 2023 at 8:04 PM Blaine Huff @.***>
wrote:

Doesn't seem like he's done anything with this repo since his last release
at 1.3.0. Can you publish your source with homebridge so other can use it
until he updates?
—
Reply to this email directly, view it on GitHub
https://github.com/sajmonr/homebridge-hubspace/pull/34#issuecomment-1773949794,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AADHF4ZYSNYWWXXFNIIONTLYARPJJAVCNFSM6AAAAAA5XUL4G2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZTHE2DSNZZGQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Bugfix for VerifyXml

Method VerifyXml doesn't work correctly with empty xml tags as described in #935. Here is a fix for this problem.

@callmekoo can u accept the cla

@dotnet-policy-service agree


CIS - Provide ability to support custom profile (user skips)

Provide ability to support custom profile (user skips)

Ability to skip / unskip tests
Need ability to see the "skip" status before running the scan
Clear distinguish user skipped and Rancher skipped

This has been fixed using the cis-operator and ClusterScanProfile CRD. The user skipped tests can be added to the ClusterScanProfile CR and Rancher skipped are marked as "Not Applicable" tests in the report.
Seems duplicate of https://github.com/rancher/cis-operator/issues/18

On master-head - commit id: 343b8e19c

User is able to specify tests to be skipped in a customScan profile by adding this under spec

spec:
  benchmarkVersion: cis-1.5
  skipTests:
    - "1.1.20"
    - "1.1.21"

Permissive scan has no rancher skipped tests. Only tests marked N/A and Passed


How to inject dependencies into hooks?

Your Question

A hook is a method on a model that receives a DB object (and a pointer to itself). This limits possible hook dependencies to:

Fields/state on the model: this breaks away from using models as PODs.
DB context: this is fine for tracing, but not intended for dependencies.
Using some global singleton variables: this is problematic for tests, needs mutex for threads etc.

In my actual use case, I have some request-id tracing stuff which works fine as context, but I also have an eventbus instance that I'm trying to move away from global singleton (3.) with context, but this is also being quite problematic.
Is there a "proper" way to inject dependencies into hooks, or some recommendation?
The document you expected this should be explained
https://gorm.io/docs/hooks.html

Expected answer
Preferred choice, another option that I didn't know, or reframing the problem itself. Thank you!

Do you need db.Statement.Settings?
https://gorm.io/docs/settings.html#content-inner

@a631807682 yes exactly something like that. Do Settings get propagated into new .Sessions and transactions?

It depends on how you use it
	tx1 := DB.Set("test", 123)
	v, _ := DB.Get("test") // nil
	v1, _ := tx1.Get("test") // 123

Aha, it looks like it copies the settings then. Great, thanks a lot!


Is this working for you?

Seems incompatible with updated Guzzle... especially with the class names.
Error after error trying to shove a request through shopify.php
Can you add a bit of documentation, or at least a note that this no longer works with recent Laravel and Guzzle versions?

UPDATE:
Got it working by:

Adjusting the guzzle namespaces from Guzzle\Http to GuzzleHttp (to match what is in the autoload_classmap.php)
Updating the new Client parameters to match what the updated guzzle expects to receive (array, not string)
Removing a null parameter in the makeRequest function (expects an array there, not null)
Fixing the response mechanism to a valid function

Below is my working code for shopify.php. I have tested with GET requests only so far. Have a feeling POST/PUT/DELETE will take some doing.
public function __construct($domain, $key, $password)
        {
            $url          = "https://" . $key . ":" . $password . "@" . $domain . "/admin/";
            $this->client = new Client([
                'base_url' => $url,
                'defaults' => ['headers' => ['Content-Type' => 'application/json']]
            ]);
        }

        /**
         * send off the request to Shopify, encoding the data as JSON
         *
         * @param  string $method
         * @param  string $page
         * @param  array  $data
         *
         * @return array
         */
        private function makeRequest($method, $page, $data = [])
        {

            $r = $this->client->createRequest($method, $page, $data);

            if ($data && $method != 'GET') {
                $r->setBody(json_encode($data), 'application/json');
            }

            if ($method == 'GET' && !empty($data)) {
            }

            try {
                $response = $this->client->send($r);
                return $response->json();
            } catch (ClientErrorResponseException $e) {
                return [
                    'error'    => $e->getMessage(),
                    'url'      => $e->getRequest()
                                    ->getUrl(),
                    'request'  => $e->getRequest(),
                    'status'   => $e->getResponse()
                                    ->getStatusCode(),
                    'response' => $e->getResponse()
                ];

            } catch (BadResponseException $e) {
                return [
                    'error'    => $e->getMessage(),
                    'url'      => $e->getRequest()
                                    ->getUrl(),
                    'request'  => $e->getRequest(),
                    'status'   => $e->getResponse()
                                    ->getStatusCode(),
                    'response' => $e->getResponse()
                ];
            }

        }

To access in a controller, I use:
	public function index()
	{
		$data = ['query'=>['limit'=>'250']];
		return Shopify::getProducts($data);
	}

Maybe this will help someone down the line—

Sorry about that, it sems like i don't get emails from GitHub when someone comments on my repo.
I see you fixed it up in your own fork, did you want to send a pull request?


Create StaticMDCBinder using BasicMDCAdapter as implementation

This allows projects using this library to avoid the following error (and basically having no implementation of MDCAdapter:
SLF4J: Failed to load class "org.slf4j.impl.StaticMDCBinder".
SLF4J: Defaulting to no-operation MDCAdapter implementation.s
SLF4J: See http://www.slf4j.org/codes.html#no_static_mdc_binder for further details.

hey @alejandrohdezma, I have just run into this issue. Did you find a different workaround?


Improve performance of decoding table row

Currently we are heavily depends of HashSet and HashMap while decoding a row(cut_row), which do some unnecessary allocation and hash computing. Since the key is always i64/u64, and the element count is small. we can implement a highly optimize/customize a HashSet/HashMap with a internal vector.

It depends on the number of columns. After changing from fnv to fx hash, the cost of hash can be negligible.


EventEmitter is not working in Release apk

Description
I'm using the react native's event emitter to send events from native to JS. This thing is working absolutely fine on my DEBUG version. I'm able to send events with data from native side to JS, but this is not working in the final RELEASE APK!
To further test out things, I changed my build variant to "release" version. To my surprise it works fine even in release variant. The problem is I'm unable to receive native events in the final release build APK! (gradlew assmbleRelease)
React Native version:
System:
OS: Windows 10 10.0.19041
CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
Memory: 450.34 MB / 7.86 GB
Binaries:
Node: 10.16.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.4 - C:\Program Files (x86)\Yarn\bin\yarn.CMD
npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: Version  <IP_ADDRESS> AI-193.69<IP_ADDRESS>26763
Languages:
Java: 13.0.2
Python: 3.8.0
npmPackages:
@react-native-community/cli: Not Found
react: 16.11.0 => 16.11.0
react-native: 0.62.2 => 0.62.2
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

Send an event with some data from the native side using event emitter.
Add listener in JS side and try to fetch the results from this native event.
Works fine in DEBUG and RELEASE build variants, but now try generating an APK(RELEASE)

We don't get events data in release APK!
Expected Results
I'm expecting that my listener at the JS side should listen to the event and get data!
Snack, code example, screenshot, or link to a repository:
In Java (Native) side:
SomeActivity.java (onCreate Method)
Basically, I'm trying to send a JSON object from the native side to JS which I've already converted to a NativeMap.
Also, the reactContext was coming as null in onCreate method, so I added this check to make sure it's not null.
if(getIntent().hasExtra("pendingNoonReportDoc")) {
            ReactInstanceManager reactInstanceManager = getReactNativeHost().getReactInstanceManager();
            ReactContext reactContext = reactInstanceManager.getCurrentReactContext();
            if (reactContext != null) {
                reactContext.getJSModule(DeviceEventManagerModule.RCTDeviceEventEmitter.class)
                        .emit("hasPendingDoc", pendingNoonReportWritableMap);

            } else {
                reactInstanceManager.addReactInstanceEventListener(new ReactInstanceManager.ReactInstanceEventListener() {
                    @Override
                    public void onReactContextInitialized(ReactContext context) {
                        context.getJSModule(DeviceEventManagerModule.RCTDeviceEventEmitter.class)
                                .emit("hasPendingDoc", pendingNoonReportWritableMap);
                        reactInstanceManager.removeReactInstanceEventListener(this);
                    }
                });
            }
        }

In JS-Side
const eventEmitter = new NativeEventEmitter(NativeModules.ClickNativeEg);

const MyApp = () => {
....
	useEffect(() => {
		eventEmitter.addListener("hasPendingDoc", (event) => {
			console.log(event);
			console.log("hasPendingDoc receved event!");
		});
	}, [eventEmitter]);
....
}

Thanks for the issue @abdulghanitech! Could you provide a repo so I can build the production app? I want to make sure it happens on a clean template.

did anyone manage to find the problem and how to solve it?

Is there a solution to this? I'm stuck on this issue.

Anything yet? Stuck here as well

If you're on fire, a desperate solution is to add some delay somewhere before you access context, with TimeUnit.SECONDS.sleep(1);. Adding 1 second delay works for me.

We're also seeing this.


Remove unnecessary requirements on success()

The Clone + Slice<RangeTo<usize>> requirement on I is unnecessary, since the success() combinator just moves input. I also removed the braces to keep the style in line with value().

Coverage increased (+0.02%) to 87.632% when pulling 9156d967c8527f8f81e0fc12ea1b27072f84b841 on calebsander:master into 1c34db743864455568ca9d30b2a90b26d94cca93 on Geal:master.


Previous and Next Month

Hai @deviprsd21
I like to push my code into a branch. I think that would be better.
Could please create a new branch for it and let me know the name?
Best,
Real Infotech Services
<EMAIL_ADDRESS>

name of the branch - test-branch

Hai @deviprsd21!
The new build has the functionality. You have done it.
You can check the old and new new for proof.

Thanks.
Best,
Real Infotech Services,
<EMAIL_ADDRESS>

So you won't be pushing your code?

It is my pleasure to push it. I will do and let you know asap.
Best,
Real Infotech Services,
<EMAIL_ADDRESS>

Hai @deviprsd21
I get the following error on push command

Best,
Real Infotech Services,
<EMAIL_ADDRESS>


Way to query the state of all workers and queues and whatever else we need to monitor

As a sysadmin tasked with keeping binstar up, I need a way to monitor binstar to proactively fix things.
This should be a simple text page with little to no markup.
"OK" when happy, and something other than "OK" when not.
A second page which can easily give me why things are not "OK" would be helpful, but we wouldn't want it on the initial page. (We could do this with query params as well. Just don't put JS or markup in the page)
If you feel there are things other than workers that should be monitored, pages for them should be made too.
If you are determining worker health by something other than queue size, a page which gives me maximum queue size of the longest queue would be good, so we can set a monitor for "if any queue is longer than 10, warn".
This all also needs a way to disable items from being monitored, for example if you have a new worker which you're debugging but is not in the generally available queue.
Monitoring should also be able to check things like DB health, if backups are happening and are good, etc.

closing - updated build UI being released in the next couple of weeks may address.


Add link to Greach talk about the project

Noam Tenne did a great talk at Greach 2017 about the project... let's add a link to it in the documentation.
https://www.youtube.com/watch?v=HoPSS5TEqS8&feature=youtu.be

Done in the development branch.


CLEAN:  Resolve Axis and AxisType

In _typing.pyi, we have:
Axis = Union[str, int]
SeriesAxisType = Literal["index", 0]  # Restricted subset of _AxisType for series
AxisType = Literal["columns", "index", 0, 1]

There are 23 places (assuming I did grep correctly) where we use Axis, but can probably change this to AxisType in many (if not all) of them.

Now I think there is only a single place where Axis is used which is this Axis: TypeAlias = str | int

Now I think there is only a single place where Axis is used which is this Axis: TypeAlias = str | int

The issue is that within the stubs themselves we have many places where we use Axis, so that is the reconciliation that needs to be done, especially with the introduction of AxisInt

yeah i'll do it

Actually i am not able to understand what is to be done with Axis in stubs because there are not many places where we can resolve Axis as it is declared it is mostly in inside funcs, but what is to be done I am not able to understand

Actually i am not able to understand what is to be done with Axis in stubs because there are not many places where we can resolve Axis as it is declared it is mostly in inside funcs, but what is to be done I am not able to understand

In _typing.pyi, we have the following:
AxisInt: TypeAlias = Literal[0, 1]
Axis: TypeAlias = AxisInt | Literal["index", "columns", "rows"]
SeriesAxisType: TypeAlias = Literal[
    "index", 0
]  # Restricted subset of _AxisType for series
AxisTypeIndex: TypeAlias = Literal["index", 0]
AxisTypeColumn: TypeAlias = Literal["columns", 1]
AxisType: TypeAlias = AxisTypeIndex | AxisTypeColumn

In the pandas source, we use Axis as an argument type, while in pandas-stubs, we use AxisType.  We should decide to go one way or the other, maybe by changing pandas.
Based on a discussion in https://github.com/pandas-dev/pandas/pull/48612 ,  I'd like @twoertwein to comment on which way he thinks we should go within pandas-stubs.

I like the idea of separating Series-only/DataFrame axis values! Making that change in pandas will probably take some effort (especially for the integer indexing).
I'm slightly shocked how many Axus-related types we have, can we simplify it a bit. Maybe:
AxisInt: TypeAlias = Literal[0, 1]  # might not even be needed for the public API, typically used in private functions
AxisIndex: TypeAlias = Literal["index", 0]
AxisColumn: TypeAlias = Literal["columns", 1]
Axis: TypeAlias = AxisTypeIndex | AxisTypeColumn

I like the idea of separating Series-only/DataFrame axis values! Making that change in pandas will probably take some effort (especially for the integer indexing).
I'm slightly shocked how many Axis-related types we have, can we simplify it a bit. Maybe:
AxisInt: TypeAlias = Literal[0, 1]  # might not even be needed for the public API, typically used in private functions
AxisIndex: TypeAlias = Literal["index", 0]
AxisColumn: TypeAlias = Literal["columns", 1]
Axis: TypeAlias = AxisTypeIndex | AxisTypeColumn

What about including "row" in AxisIndex ?

What about including "rows" in AxisIndex ?

the pandas PR added it only because it is technically possible and to avoid a mypy error (but I think it is not very well documented/used). I'd be fine adding/excluding it.

@ramvikrams
So the goal would be to use these:
AxisInt: TypeAlias = Literal[0, 1]  # might not even be needed for the public API, typically used in private functions
AxisIndex: TypeAlias = Literal["index", 0]
AxisColumn: TypeAlias = Literal["columns", 1]
Axis: TypeAlias = AxisTypeIndex | AxisTypeColumn

and remove AxisType, SeriesAxisType and AxisType (changing where we have AxisType to the "new" Axis)
We can remove AxisInt - it is only used in algorithms.take(), and just use a Literal[0, 1] there.
So that would mean we would only see AxisIndex, AxisColumn and Axis throughout the stubs.

@ramvikrams So the goal would be to use these:
AxisInt: TypeAlias = Literal[0, 1]  # might not even be needed for the public API, typically used in private functions
AxisIndex: TypeAlias = Literal["index", 0]
AxisColumn: TypeAlias = Literal["columns", 1]
Axis: TypeAlias = AxisTypeIndex | AxisTypeColumn

and remove AxisType, SeriesAxisType and AxisType (changing where we have AxisType to the "new" Axis)
We can remove AxisInt - it is only used in algorithms.take(), and just use a Literal[0, 1] there.
So that would mean we would only see AxisIndex, AxisColumn and Axis throughout the stubs.

thanks, i'll get started now

We don't have AxisInt but we have Axis: TypeAlias = str | int so should we remove this Axis to move forward with the orignal plan

We don't have AxisInt but we have Axis: TypeAlias = str | int so should we remove this Axis to move forward with the orignal plan

Yes, the goal is to use what is now AxisType and make that Axis


Data Export Problem for Classroom.Zooniverse.org Galaxy Zoo 101

@srallen I just got an email from Rose Finn using classroom.zooniverse in her Astro101 course. She used it last year as well.
She's run into a data export error.
Here's her info:
my username is Rose_Finn (rfinn@siena.edu).  My class for this spring is
https://classroom.zooniverse.org/#/astro-101-with-galaxy-zoo/students/classrooms/2673/join?token=7b9a17456a3f1962
and this is the project page for galaxy zoo
https://www.zooniverse.org/projects/zooniverse/galaxy-zoo-in-astronomy-101/classify?group=1749049&_ga=2.195639468.1877613624.1553048722-149825245.1553048722
If I go to https://www.zooniverse.org/lab/2308/data-exports - is there a workflow I can choose to export data and maybe manually pull out her classrooms data? Or other way that I can try to help her (without imposing on your time this week)?

Here's the error she gets:

These are caesar exports, so this indicates and issue with those. We can follow up in those logs looking for reductions exports for that user group id and those project's workflows that failed.

Fwiw, we can't really use Panoptes classification exports without doing manually the aggregation caesar does for those to make them usable.

Thanks! (And good reminder that caesar manipulates the data to make it more useable - so not that helpful to get the panoptes raw classification export)
I can ask Amy to check on caesar -- but to be sure I know what to ask for (also so I know for future cases) - are these the right numbers to share with Amy?:
workflow = 2673
group ID = 1749049
?

(I'll share the full URLs w/ her, but it's for my knowledge as well).

The workflow ids are:
Galaxy Zoo 101: 5521
Hubble's Law: 5522
And user group id is correct, 1749049
(id 2673 is the classroom id which is only used by edu api, not by panoptes or caesar)

@srallen See https://github.com/zooniverse/caesar/issues/721
Looking like the classroom.zooniverse button for 'data exports' isn't acting as expected. No caesar calls were made by Rose's request (nor mine, that I tried today), as far as Amy was able to see.

But don't follow up at this time - for Rose, I'll just use example data exports that Tommy/Cody created previously. We'll address this problem this summer when Molly joins in June and we kick off the next round of classroom.zooniverse effort.

Closed by #158


E2M2 displays Red Keycard as requiring Red Keycard

Logic is operating correctly - it shows as inaccessible when I have R, Y, but not B - but the displayed message on the tooltip is incorrect.

This is now fixed in v<IP_ADDRESS>. Thanks for letting me know!


CI needs updating

Various CI checks have recently started failing. I'm not sure of this but I wonder if these are triggered by the recent release of Go 1.22.
The build container check also detects that we're no longer using a supported version of go the Dockerfile

As noticed in a different project this seems more likely due to latest revive(v1.3.7) release where it adds support to detect unused parameters for anonymous functions.

The build container check also detects that we're no longer using a supported version of go the Dockerfile

As noted in https://github.com/samba-in-kubernetes/samba-operator/pull/315
The downside of this approach is that PRs & other work unrelated to Golang may periodically break when Go issues a new major release.

first occurrence 😆


Remove duplicated section in "annotating-function-parameters-and-return-values" document

Remove 3 sections in document that were duplicated. The following sections are repeated in the block directly above the removed lines:

_Inout_updates_z_(s)
_Out_writes_to_(s,c) + 3 variants
`Inout_updates_to(s,c) + 1 variant

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


Custom Hierarchical Permissions

goal is to leverage hierarchical permissions in eos
specifically, want to create a new custom permission level in the following structure
owner < active < newpermission
where newpermission can sign a subset of action types e.g. eosio::buyram, but cannot auth any other action type
this way the moderately valuable private key associated with newpermission could be used in a dapp vs the invaluable active / owner keys
does this functionality exist as of right now? it seems that this functionality exists already, specifically i was able to run:
./cleos create key
then take the public key EOS[...] and run:
./cleos set account permission myaccountname newpermission EOS[...] active -p myaccountname@active
this seems to work, meaning it successfully creates a new permission level in the desired hierarchy in that:
./cleos get accounts myaccountname returns new key in hierarchy
permissions:
⋅⋅⋅⋅⋅⋅owner     1:    1 EOS[...]
⋅⋅⋅⋅⋅⋅⋅⋅⋅active     1:    1 EOS[...]
⋅⋅⋅⋅⋅⋅⋅⋅⋅⋅⋅⋅newpermission     1:    1 EOS[...]
now let's say i want the newpermission to only be able to sign action = eosio::buyram:
./cleos set action permission myaccountname eosio buyram newpermission -p myaccountname
i see a linkauth transaction go through without complaint. linkauth is visible in chain explorers
then, however, i create a new wallet and import the private key of newpermission then try to run:
./cleos -system buyram myaccountname myaccountname "0.10 EOS" -p myaccountname@newpermission
and get an error:
Error 3090003: provided keys, permissions, and delays do not satisfy declared authorizations
Ensure that you have the related private keys inside your wallet and your wallet is unlocked.
wallet is def unlocked, so now i'm back to: is this functionality enabled as of now? lol
if not, what needs to be done, i'm game to help this seems like a big one.
if functionality does exist, what have i missed / done wrong in the workflow above?

The default permission for a buyram operation is hard-coded to active. (line 1222 in cleos' main.cpp). Cleos would need to read the -p passed on instead of using the hard-coded one.
I'm rolling out changes to eosc (which is similar to cleos, but cross-platform) that implement that properly for voteproducer and buyram and other actions.  It's not as fully-fledged as cleos right now, but already has a few advantages. Take a look http://github.com/eoscanada/eosc
My concern is not being able to see the auth links created through the eosio::linkauth operation.. /v1/chain/get_account doesn't report any such data.. I'd love to see that added. @wanderingbort ?

thanks for pointing out the hard-coded permission level in cleos! i'm tearing my hair out (whats left that is) with this custom permission so i'm def interested in checking out eosc if it sorts out this custom permission flow business. i think that it would be a major boon for development on eos if there was a real push to have a majority of users create less valuable sub-keys that linkauth to various subsets of actions
e.g. could have the following custom permission to action mapping:
voter -> voteproducer + setproxy
ramtrader -> buyram + sellram
delegator -> delegatebw + undelegatebw
each sub-key offers a more modular way to secure each action, or group of logically related actions. it also lowers the barrier to marginal user adoption if developers can use named permissions the user has already created to use another dapp
+1 for the comment about /v1/chain/get_account not returning link data, i'd very much like to see that information returned. i've already had it happen where i forgot a linkauth i had pushed already, so this would be great to see it all together.
in the meantime i'm gonna try to get the custom permission to work bypassing cleos and just making POST requests directly to /v1/chain/push_transaction, unless u think there's a better kludge at the moment?

@marketstack I'm a bit late to answer this but I think you could try pushing the transaction manually in cleos:
cleos push action eosio buyram '["myaccountname", "myaccountname", "0.1000 EOS"]' -p myaccountname@newpermission

That way you should be able to bypass the hardcoded active permission that was getting injected.

Any update on this issue ? It would be great if we can see existing linkauth directly from cleos get account. Also, is it possible to view linkauth table directly from cleos ?


change 'starting activity' layout

Description
Fixes #947
Notes (out of scope, known issues, hints for reviewing code, ...)  (optional)
...
Test cases

[ ] Case 1:

Given I am the usual user
When I go to [this page](branch link)
And I click on ...
Then I see ...
And

[ ] Case 2:

Given I am the usual user
When ...

Let's start with the expected UI. Does this fit?

For the UI. That looks ok. For the first message, just keep "Starting the activity", and for the second one "Loading the task".


Persistent error notice

I'm running 1.0
I have the following error message: /mnt/hdd/raspiblitz.conf: -: line 5
This shows periodically on the raspi LCD.

line 5 could be the name of the RaspiBlitz ... it could be that you set an invalid string there.
First try to SSH in and in main menu choose NAME - change name/alias and enter one without any special chars.
If you still have a problem ... please SSH in, go to terminal and check the config file with:
sudo cat /mnt/hdd/raspiblitz.conf
and post the content here.

please close this.


Command to refresh spacebar

It would be nice to have a command like spacebar -m refresh to rerender spacebar.
For example, when I create a new space with yabai -m space --create spacebar won't show it for a few seconds, so I have to use this workaround to force it to rerender spaces immediately spacebar -m config spaces on but I think a native option to do so would be a better solution

Just run your spacebarrc
yabai -m space --create && ~.config/spacebar/spacebarrc

works for me at least


Add Slack archive and dependency for viewing

Problem
Being on Slack's free plan means that we lack access to threads and messages that are more than 3 months old.
Solution
This adds two possible solutions to dev: 1) an exported zip archive from Slack with a dependency, slack-export-viewer, to enable viewing the archive in a browser. If the community likes this approach, the entire history of public channels could be added to dev and updated on a regular basis. Instructions for using the package are in the readme; 2) the HTML generated by an alternative tool, slack-archive.
The slack-archive tool is more fully-featured and its UI handles threads well, but using it requires elevated permissions in Slack and the HTML its UI requires is voluminous (only one month's worth of Slack data is included here, and it amounts to close to 90k lines). Also, a user could accidentally share DMs and messages in private channels. By contrast, the slack-export-viewer tool does not require any permissions -- only an exported archive that those with admin privileges in the Slack workspace can generate -- and collects/displays only public channels. It doesn't handle threads very well. A screenshot of each is included below in the comments.

Note: All schema changes require discussion. Please link the issue for context.

[ ] Your change modifies the core OpenLineage model
[ ] Your change modifies one or more OpenLineage facets

If you're contributing a new integration, please specify the scope of the integration and how/where it has been tested (e.g., Apache Spark integration supports S3 and GCS filesystem operations, tested with AWS EMR).
One-line summary: adds a slack archive and tool for viewing
Checklist

[ ] You've signed-off your work
[x] Your pull request title follows our guidelines
[ ] Your changes are accompanied by tests (if relevant)
[x] Your change contains a small diff and is self-contained
[x] You've updated any relevant documentation (if relevant)
[ ] Your comment includes a one-liner for the changelog about the specific purpose of the change (if necessary)
[ ] You've versioned the core OpenLineage model or facets according to SchemaVer (if relevant)
[ ] You've added a header to source files (if relevant)

SPDX-License-Identifier: Apache-2.0
Copyright 2018-2023 contributors to the OpenLineage project

HTML generated by slack-archive:

Update: I contributed a change to slack-export-viewer that improves the way it displays threads. It's been merged but not yet released.

should we close this in favor of https://github.com/OpenLineage/slack-archives?


firebase_messaging event handlers in example app never trigger with --preview-dart-2

Problem
The example app for the firebase_messaging plugin has event handlers for onMessage, onLaunch, and onResume that should print the received message to debug and also trigger an action within the app. However, none of these event handlers actually run when a notification is received.
I know messaging is working because I can receive notifications through the app from Firebase Console and tap them and they'll open the app, but nothing prints to debug and the associated action does not occur.
Flutter Doctor
flutter doctor -v
[√] Flutter (Channel beta, v0.1.5, on Microsoft Windows [Version 10.0.16299.309], locale en-US)
    • Flutter version 0.1.5 at C:\Users\Caleb\Google Drive\Android\flutter
    • Framework revision 3ea4d06340 (3 weeks ago), 2018-02-22 11:12:39 -0800
    • Engine revision ead227f118
    • Dart version 2.0.0-dev.28.0.flutter-0b4f01f759

[√] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at C:\Users\Caleb\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)

[√] Android Studio (version 3.0)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-915-b01)

[√] VS Code (version 1.21.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Dart Code extension version 2.10.0

[√] Connected devices (1 available)
    • Pixel 2 XL • 709KPNY0046767 • android-arm64 • Android 8.1.0 (API 27)

• No issues found!

As far as I remember onMessage is only called for data messages, not for notifications
and when the app is active.

Yes, onMessage only gets called when the app is in the foreground, but as far as I can tell the docs don't specify that it requires a data message. However, it also requires additional configuration to work, which is not set up in the example app.
The other two are supposed to be called when you tap a notification, and again there is no listed requirement of it being a data message, so I expect it to work. Though if it does require data messages then that would explain why they don't get called, since the data messaging is not enabled.

What am I supposed to see there? The only thing it says is that you have to set a custom key-value pair of click_action: FLUTTER_NOTIFICATION_CLICK in order for onResume or onLaunch to be called when the notification is tapped on Android. It's set, but still not calling anything when the notification is tapped.

I did some debugging to try and figure out what was going on, but I'm confused by what I'm seeing... I put a breakpoint inside the function that I'm assigning to onMessage in the configure() call, and also put one inside the onMessage case of the FirebaseMessaging _handleMethod function. The debugger will break at the correct line in _handleMethod as expected:
Future<Null> _handleMethod(MethodCall call) async {
  switch (call.method) {
    case "onToken":
      final String token = call.arguments;
      if (_token != token) {
        _token = token;
        _tokenStreamController.add(_token);
      }
      return null;
    case "onIosSettingsRegistered":
      _iosSettingsStreamController
          .add(new IosNotificationSettings._fromMap(call.arguments));
      return null;
    case "onMessage":
      return _onMessage(call.arguments); // <-- Breakpoint here, hit as expected
    case "onLaunch":
      return _onLaunch(call.arguments);
    case "onResume":
      return _onResume(call.arguments);
    default:
      throw new UnsupportedError("Unrecognized JSON message");
  }
}

I verified that call.arguments contains the key/value pairs that I'm setting in the message from the Firebase Console; however, when I continue, the breakpoint in my handler never happens, and the code there doesn't run. The debugger only shows the value of _onMessage as _Closure so I can't tell what is happening there.

Okay, so after a lot of dead ends, I had a random idea and tried running the project with just flutter run, as I had previously been running everything with flutter run --preview-dart-2... and everything works. So the problem is actually something with Dart 2.

@Herohtar no exceptions in the log output?
flutter clean might be worth a try.

No exceptions at all. I've been stopping the app and doing flutter clean every time I made a change specifically to avoid any potential issues there.
In any case, this may have been fixed by https://github.com/flutter/plugins/pull/434, but I won't be able to check until this evening.

I can also confirm this - I'm having the same problem and it's gone when I add --no-preview-dart-2 (Dart 2 seems to be the default for 0.2.4)

Is this still an issue?
It is working in my project since quite a while.

Sorry, I forgot about testing this. I checked just now and it seems to be working with Flutter 0.5.1.

@Herohtar glad to hear and thanks for the feedback!

@Herohtar
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/889. Any further collaboration will be done there.


Uncaught TypeError: Cannot read property 'attributes' of undefined

Hi,
I have this issue each time smoothState triger my code on link active
Uncaught TypeError: Cannot read property 'attributes' of undefined
My script is normaly ok, all is whithin the div main id, he show properly the first attributes on laoding but lost himself after..
any advice for me ?
thanks a lot :)

Hey @loximoz,
We might be able to help, but we'll need a lot more information about what you're working on so that we can re-create the issue. Here's a quick list of what we'll need: https://github.com/miguel-perez/smoothState.js#how-to-ask-for-help

Hi,
Thanks for your fast response.i fixed it since few , was my fault with my header who broked the smoothstate attributes copy, cause i declare wrong some.
Thanks a lot again, and great plugin by the way !
Regards
Sylvain
Sur 27 avr. 2015 20:02, à 20:02, "Miguel Ángel Pérez"<EMAIL_ADDRESS>a écrit:

Hey @loximoz,
We might be able to help, but we'll need a lot more information about
what you're working on so that we can re-create the issue. Here's a
quick list of what we'll need:
https://github.com/miguel-perez/smoothState.js#how-to-ask-for-help

Reply to this email directly or view it on GitHub:
https://github.com/miguel-perez/smoothState.js/issues/159#issuecomment-96761462


GNU/Linux: "Failed to clear temp storage" error after elevation

When I hit flash it asks for root password then it doesn't do anything. The button becomes "flash" again. Just that.

Etcher version: v1.0.0-beta.15
Operating system and architecture: Ubuntu 14.04 64bit
DevTools:

    tracker.js:10 Tue Sep 27 2016 15:01:01 GMT+0200 (EET) Application start
    tracker.js:10 Tue Sep 27 2016 15:01:01 GMT+0200 (EET) Checking for updates
    tracker.js:10 Tue Sep 27 2016 15:01:54 GMT+0200 (EET) Select image ({"size":1513308160,"path":"/blablabla/ubuntu-16.04.1-desktop-amd64.iso","logo":false,"bmap":false})
    tracker.js:10 Tue Sep 27 2016 15:02:06 GMT+0200 (EET) Flash ({"image":"/blablablabla/ubuntu-16.04.1-desktop-amd64.iso","device":"/dev/sdc"})
    tracker.js:10 WRITER: Tailing /tmp/etcher-569253li5orq6Mys.log

    tracker.js:10 WRITER: Tail starting:

    tracker.js:10 WRITER: filename: /tmp/etcher-569253li5orq6Mys.log

    tracker.js:10 WRITER: options: {}

    tracker.js:10 WRITER: Attempting to elevate

    Failed to clear temp storage: An operation that depends on state cached in an interface object was made but the state had changed since it was read from disk. InvalidStateError

I found empty log files in /tmp/

I'm pretty sure this bug will be fixed with the following patch: https://github.com/resin-io/etcher/pull/774.
I'll publish a custom build here so you can test it if you can.

Here's the custom build: https://www.dropbox.com/s/ao1vmhhv7775mc5/Etcher-linux-x64.zip?dl=0

I'll close this issue as resolved, but please re-open if you can still reproduce with the custom built I sent, or with the next published Etcher version.


[prim/lint] Move AscentLint waiver rules for prim_gf_mult into own file

prim_gf_mult is a primitive with it's own core file. Having the waiver rules inside the shared prim.waiver file may cause Flow warnings.

Thanks guys, with this commit we're now completely lint clean:
|                                           Name                                            |  Flow Warnings  |  Flow Errors  |  Lint Warnings  |  Lint Errors  |
|:-----------------------------------------------------------------------------------------:|:---------------:|:-------------:|:---------------:|:-------------:|
|              [AES](../../../../../ip/aes/lint/ascentlint/latest/report.html)              |       0 W       |      0 E      |       0 W       |      0 E      |
| [ALERT_HANDLER](../../../../ip_autogen/alert_handler/lint/ascentlint/latest/report.html)  |       0 W       |      0 E      |       0 W       |      0 E      |
|        [AON_TIMER](../../../../../ip/aon_timer/lint/ascentlint/latest/report.html)        |       0 W       |      0 E      |       0 W       |      0 E      |
|            [ASCON](../../../../../ip/ascon/lint/ascentlint/latest/report.html)            |       0 W       |      0 E      |       0 W       |      0 E      |
|               [AST](../../../../ip/ast/lint/ascentlint/latest/report.html)                |       0 W       |      0 E      |       0 W       |      0 E      |
|      [ENTROPY_SRC](../../../../../ip/entropy_src/lint/ascentlint/latest/report.html)      |       0 W       |      0 E      |       0 W       |      0 E      |
|        [CLKMGR](../../../../ip_autogen/clkmgr/lint/ascentlint/latest/report.html)         |       0 W       |      0 E      |       0 W       |      0 E      |
|            [CSRNG](../../../../../ip/csrng/lint/ascentlint/latest/report.html)            |       0 W       |      0 E      |       0 W       |      0 E      |
|         [ADC_CTRL](../../../../../ip/adc_ctrl/lint/ascentlint/latest/report.html)         |       0 W       |      0 E      |       0 W       |      0 E      |
|              [EDN](../../../../../ip/edn/lint/ascentlint/latest/report.html)              |       0 W       |      0 E      |       0 W       |      0 E      |
|    [FLASH_CTRL](../../../../ip_autogen/flash_ctrl/lint/ascentlint/latest/report.html)     |       0 W       |      0 E      |       0 W       |      0 E      |
|             [GPIO](../../../../../ip/gpio/lint/ascentlint/latest/report.html)             |       0 W       |      0 E      |       0 W       |      0 E      |
|             [HMAC](../../../../../ip/hmac/lint/ascentlint/latest/report.html)             |       0 W       |      0 E      |       0 W       |      0 E      |
|             [KMAC](../../../../../ip/kmac/lint/ascentlint/latest/report.html)             |       0 W       |      0 E      |       0 W       |      0 E      |
|              [I2C](../../../../../ip/i2c/lint/ascentlint/latest/report.html)              |       0 W       |      0 E      |       0 W       |      0 E      |
|          [LC_CTRL](../../../../../ip/lc_ctrl/lint/ascentlint/latest/report.html)          |       0 W       |      0 E      |       0 W       |      0 E      |
|          [PATTGEN](../../../../../ip/pattgen/lint/ascentlint/latest/report.html)          |       0 W       |      0 E      |       0 W       |      0 E      |
|           [KEYMGR](../../../../../ip/keymgr/lint/ascentlint/latest/report.html)           |       0 W       |      0 E      |       0 W       |      0 E      |
|             [OTBN](../../../../../ip/otbn/lint/ascentlint/latest/report.html)             |       0 W       |      0 E      |       0 W       |      0 E      |
|         [OTP_CTRL](../../../../../ip/otp_ctrl/lint/ascentlint/latest/report.html)         |       0 W       |      0 E      |       0 W       |      0 E      |
|           [PINMUX](../../../../../ip/pinmux/lint/ascentlint/latest/report.html)           |       0 W       |      0 E      |       0 W       |      0 E      |
|              [PWM](../../../../../ip/pwm/lint/ascentlint/latest/report.html)              |       0 W       |      0 E      |       0 W       |      0 E      |
|        [PWRMGR](../../../../ip_autogen/pwrmgr/lint/ascentlint/latest/report.html)         |       0 W       |      0 E      |       0 W       |      0 E      |
|         [ROM_CTRL](../../../../../ip/rom_ctrl/lint/ascentlint/latest/report.html)         |       0 W       |      0 E      |       0 W       |      0 E      |
|        [RSTMGR](../../../../ip_autogen/rstmgr/lint/ascentlint/latest/report.html)         |       0 W       |      0 E      |       0 W       |      0 E      |
|     [RV_CORE_IBEX](../../../../../ip/rv_core_ibex/lint/ascentlint/latest/report.html)     |       0 W       |      0 E      |       0 W       |      0 E      |
|            [RV_DM](../../../../../ip/rv_dm/lint/ascentlint/latest/report.html)            |       0 W       |      0 E      |       0 W       |      0 E      |
| [TOP_EARLGREY_RV_PLIC](../../../../ip_autogen/rv_plic/lint/ascentlint/latest/report.html) |       0 W       |      0 E      |       0 W       |      0 E      |
|         [RV_TIMER](../../../../../ip/rv_timer/lint/ascentlint/latest/report.html)         |       0 W       |      0 E      |       0 W       |      0 E      |
|       [SPI_DEVICE](../../../../../ip/spi_device/lint/ascentlint/latest/report.html)       |       0 W       |      0 E      |       0 W       |      0 E      |
|         [SPI_HOST](../../../../../ip/spi_host/lint/ascentlint/latest/report.html)         |       0 W       |      0 E      |       0 W       |      0 E      |
|        [SRAM_CTRL](../../../../../ip/sram_ctrl/lint/ascentlint/latest/report.html)        |       0 W       |      0 E      |       0 W       |      0 E      |
|      [SYSRST_CTRL](../../../../../ip/sysrst_ctrl/lint/ascentlint/latest/report.html)      |       0 W       |      0 E      |       0 W       |      0 E      |
|             [UART](../../../../../ip/uart/lint/ascentlint/latest/report.html)             |       0 W       |      0 E      |       0 W       |      0 E      |
|           [USBDEV](../../../../../ip/usbdev/lint/ascentlint/latest/report.html)           |       0 W       |      0 E      |       0 W       |      0 E      |
|     [SOCKET_1N](../../../../../ip/tlul/socket_1n/lint/ascentlint/latest/report.html)      |       0 W       |      0 E      |       0 W       |      0 E      |
|     [SOCKET_M1](../../../../../ip/tlul/socket_m1/lint/ascentlint/latest/report.html)      |       0 W       |      0 E      |       0 W       |      0 E      |
|   [ADAPTER_REG](../../../../../ip/tlul/adapter_reg/lint/ascentlint/latest/report.html)    |       0 W       |      0 E      |       0 W       |      0 E      |
|  [ADAPTER_SRAM](../../../../../ip/tlul/adapter_sram/lint/ascentlint/latest/report.html)   |       0 W       |      0 E      |       0 W       |      0 E      |
|       [SENSOR_CTRL](../../../../ip/sensor_ctrl/lint/ascentlint/latest/report.html)        |       0 W       |      0 E      |       0 W       |      0 E      |
|     [SRAM2TLUL](../../../../../ip/tlul/sram2tlul/lint/ascentlint/latest/report.html)      |       0 W       |      0 E      |       0 W       |      0 E      |
|                      [CHIP_EARLGREY_ASIC](../../latest/report.html)                       |       0 W       |      0 E      |       0 W       |      0 E      |


upgrade base image for fluent-bit

Description
Changes proposed in this pull request:

...
...
...

Related issue(s)

Wanted to see what dependencies are updated. As the impact is not relevant, will close the PR instead


I cannot even zoom out

VSCode Version: Code 1.14.2 (cb82febafda0c8c199b9201ad274e25d9a76874e, 2017-07-19T23:34:09.706Z)
OS Version: Windows_NT ia32 10.0.15063
Extensions:

Extension
Author (truncated)
Version

python
don
0.6.9

Steps to Reproduce:

Reproduces without extensions: Yes/No

@thisistrash
First - Expletives in issues are completely inappropriate and unnecessary
Second - Your issue lacks any useful information other than the version of code
Third - I have been using Code on Windows 7 with no problems in this regard
Finally - I suggest changing your ID

This could be that zoom doesn't work when you pinch a mouse pad on a laptop - this behaviour is present in Chrome / Edge / Visual Studio etc.  Thus, the report may assumed this feature should be in VsCode.  One also assumes a mouse when turned should zoom in/out ,but, I am unable to test to no being on laptop.  I can confirmed Ctrl+, Ctrl+ and Ctrl+Numpad0 work.


ARROW-15619: [C++] Temporal component extraction function for extracting is_leap_year indicator

This is to resolve ARROW-15619

And now the merge conflict is here :)

@lidavidm rebased.

Is there a test for a timestamp with timezone where it would give a different result if the timezone was ignored? (to catch that the timezone is properly applied) Such as "2012-01-01 00:00:00+02:00" (which is "2011-12-31 22:00:00" in the underlying UTC value, and then not a leap year)
(didn't check the exact values in the tests, so there might already be a case like this)

@jorisvandenbossche good point, I'm not sure either. Will add.

@jorisvandenbossche added Pacific/Pago_Pago test to show results are different than in Australia/Broken_Hill. Also added a Pandas test and noticed I forgot to add one when adding is_dst kernel, so I added one for that as well.


Migrate imp to importlib

Fixes: #111 and #114
Summary/Motivation:
This fixes the code with Python 3.12, where the imp module does not exist.
Changes proposed in this PR:
Migrate imp to importlib
Legal Acknowledgement
By contributing to this software project, I agree to the following terms and conditions for my contribution:

I agree my contributions are submitted under the BSD license.
I represent I am authorized to make the contributions and grant the license. If my employer has rights to intellectual property that includes these contributions, I represent that I have received permission to make contributions and grant the required license on behalf of that employer.

Sorry, there is an error in this PR. I will make another one.


Encountered an error while persisting cache

Awesome package by the looks of it. When I tried to get it working, I ran into this error:

[node-haste] Encountered an error while persisting cache:

SyntaxError: /Users/AlexMac/Projects/PalateCleanser/node_modules/react-native-spinkit/scripts/rnpm-prelink.js: 'return' outside of function (42:0)
// etc, can post if full log is helpful

I install via npm, linked up with rnpm, and my test code is very simple:

import Spinner from 'react-native-spinkit';
// (in render)
<Spinner isVisible={true} size={24} type={"Circle"} color="#000000"/>

On screen, the loading spinner does not show up and a thin red box of the appropriate size appears instead.
Thanks much for any help!

Thanks for the feedback @alexjhannan.
Looks like an issue with the rnpm autolinking script, I pushed a potential fix in the new version (0.1.2).
Could you please try and let me know ? Thanks

Works perfectly now. Thanks so much! Great support and a great package.


feat: switch to sha256sum

I should have pushed this to https://github.com/ublue-os/isogenerator/pull/8 .. sorry about that!


Updating landing page

-Add new images (animated-logo.gif and background.png) into the static folder
-Adding new "get started" button that leads to the explore page (the old one was just a picture )
-remove the old picture that was displayed on the landing page from
static folder
related to #54
Please merge this PR after merging PR #80 first

I think you should label this PR as status/in-progress

@ifireball @AviadP
This PR is ready for review

Since this depends on another PR, I cannot review this yet.

@ifireball @AviadP
This PR is ready for review

@ifireball @ AviadP
This PR is ready for review

LGTM


Issue with k8s.io/docs/tasks/configure-pod-container/assign-cpu-resource/

This is a...

[ X] Bug Report

Problem:
kubectl top pod memory-demo
Proposed Solution:
kubectl top pod cpu-demo
Page to Update:
https://kubernetes.io/...
1.11

Hi svennela,
The v1.11 Doc (https://v1-11.docs.kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/) shows:

Documentation for Kubernetes v1.11 is no longer actively maintained. The version you are currently viewing is a static snapshot. For up-to-date documentation, see the latest version.

The current v1.12 Doc (https://kubernetes.io/docs/tasks/configure-pod-container/assign-cpu-resource/) doesnt have the issue?
Has been fixed with PR #9376

@sluetze is correct. Closing.


Loss of Connections after upgrading to dalli 3.2.3

Hello team! Thank you for all the work you do maintaining this gem. Our service is experiencing sudden drops in connections to our memcached instance after upgrading to dalli 3.2.3 from 2.7 and changing from DalliStore to MemCacheStore. I've uploaded a screenshot of the CloudFront dashboard that shows these drops in active memcached connections. The drops happen randomly at times (seemingly) and other times, we observe this right after a deployment of new k8s pods. When it does happen it takes hours to recover, but it does eventually recover.
The service is on Rails 6.1, Ruby 2.7.6 (in the process of upgrading) and memcached 1.6.6, the puma server is in cluster mode (2 workers). Not sure if this is relevant, but when we were using DalliStore we did have a block in the puma configuration (puma.rb) that explicitly reset the connections on worker boot like so:
on_worker_boot do

  Rails.cache.reset

end

But that method is no longer available on MemCacheStore so that block was commented out. When we began seeing the dropped connection behavior we automatically attributed it to this commented code so I tried creating a custom cache store that extended MemCacheStore to give access to the underlying Dalli Client like DalliStore used to do by exposing @data through the dalli method. I called the reset method directly on it like this:
on_worker_boot do

  Rails.cache.dalli.reset

end

but continued to see the drops. At this point was just throwing spaghetti on the walls to see what sticks.
Was just wondering if anyone else saw something similar after upgrading. Apologies in advance if this is totally unrelated to the gem upgrade and inappropriate for this forum but this behavior was seen right after upgrading. Hoping for some guidance here if anyone knows what may be happenning.

Hi @phnx311
I'm not sure why this is a concern.  I don't have any data on your application, but this looks like typical connection pool behavior.
When you do a deploy, the connections from the pool in the old pod disappear, and the active connection count drops to zero.  Connections will start to be created based on load and contention on the pool.  Over time, there may be more contention on the pool driving the creation of more connections.
Because connection_pool doesn't reclaim idle connections, these connections will stay open over time.  That's why the total number of connections eventually levels out at a maximum.  You can configure the maximum size of the pool with the size parameter if you're seeing performance problems.
Random drops may occur if the connections in the pool become invalid (usually for a network related reason) and some connections are dropped from the pool.

Closing based on response.