Updated broken method when getting source array for a Grouped Dropdown.

Hi Andrew,
Looks like getSourceAsArray() is no longer a method on the SelectField class. getSource() returns an assc. array that can be used to get a category key from. Tested on SS 4.8
Cheers,
Kris

Looks good! 👍
I think the original reason for this was to account for sources of different types (Map/SS_List), it looks like SS4 now has a system in place for sanitizing source values  so getSource should always give us a value we could work with.
This has been released in 2.2.4
Thanks,
Andrew


Bugfix - Fix for incorrectly referenced recognizer in analysis_explanation using PhoneRecognizer

Change Description
Changed how the recognizer parameter for the AnalysisExplanation is populated for the PhoneRecognizer so that it get's referenced correctly
Issue reference
This PR fixes issue #1330
Checklist

[x] I have reviewed the contribution guidelines
[x] I have signed the CLA (if required)
[x] My code includes unit tests
[x] All unit tests and lint checks pass locally
[x] My PR contains documentation updates / additions if required

@microsoft-github-policy-service agree

/azp run


Edited upload.php example in README file

I changed the example for the upload.php file because in my opinion could be confusing: it uses the getIdentifier() method to give a name to the uploaded file, which produces a file without an extension and which is not intended for naming files, as suggested to me here.

Coverage remained the same at 100.0% when pulling c716bbbc15596f61ba6f3aad4256f1a588b0d13e on roibeart:roibeart-readme-edit into 340ed5b947173ec4bc790dd8b512b2820e5dfab4 on flowjs:master.

Thanks


Re-factor the loading-icons used in the viewer toolbars

Currently the SVG images for the loading-icons exist in two versions, for the light- respectively dark-theme, which nowadays are the only "duplicated" icons left.
The reason for this is that these icons are being used in input-elements, where the regular mask-image approach used for all buttons don't work.
To address this we add containers for the input-elements, such that we have a "regular" DOM-element where we can use mask-image.
Edit: This reduces the size of the gulp mozcentral output by 1.5 kilo-bytes, which isn't a lot but still cannot hurt.

/botio-linux preview


Failed to run xamarin build command, error MSB4057

The Xamarin script has trouble building our app.
Archiving and signing from within Visual Studio for Mac works just fine, however.
The error seems to be MSB4057, given that that is basically the entire content of the generated log. However, I'm not sure how to debug this further.
The log is full of that error as follows (paths truncated):
"/Toggl.sln" (Toggl_Daneel target) (1) ->
"/Toggl.Ultrawave/Toggl.Ultrawave.csproj" (Toggl_Daneel target) (2) ->
  /Toggl.Ultrawave/Toggl.Ultrawave.csproj : error MSB4057: The target "Toggl_Daneel" does not exist in the project.

You can see the app's repo here: https://github.com/toggl/mobileapp
I also attached the full log and output of the script.
xamarin-build-output.log
terminal.log

Hi, thanks for reporting the issue, we will look into it as soon as possible.

Hi @amulware ,
we released a new version of codesigndoc, please try it out and reopen the issue, if you still see the issue.

I'm still getting the same errors as detailed above I'm afraid. Let me know if there is something different/more specific I can try to make it work or get more information.

@godrei I don't think I have the right to reopen issues. The button is missing for me.

Reopened, we'll check this ASAP!


SearchBackPressure Service Collector added

Signed-off-by: Jeffrey Liu<EMAIL_ADDRESS>Is your feature request related to a problem? Please provide an existing Issue # , or describe.
Add the functionality to gather the SearchBackPressure Service.
Describe the solution you are proposing
Add SearchBackPressureStatsCollector.java to collect SearchBackPressure related metrics, and added Unit Testing for SearchBackPressureStatsCollector.java.
Describe alternatives you've considered
N/A
Additional context

Changes in licenses/ are auto-created after running ./build gradlew

In order to access the Constants field in this collector, another pull & request for performance-analyzer-commons package has been made.
Example:
@JsonProperty(SearchBackPressureStatsValue.Constants.SEARCHBP_NODEID) public String getSearchBackPressureStats_NodeId() { return this.nodeId; }
Parallel Pull & Request link: https://github.com/opensearch-project/performance-analyzer-commons/pull/33
Approving this pull & request will be needed in order for the collector to access the Performance-Analyzer-Commons Constants fields. Or else, error would occur.

Can verify the extracted search_back_pressure metrics in /dev/shm/performanceanalyzer directory, open any log file, and search for "search_back_pressure"

Check List

[X] New functionality includes testing.
[X] All tests pass
[X] New functionality has been documented.
[X] New functionality has javadoc added
[X] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Can we cleanup the bunch of jars which got along with the commit making the file changes as 37?

Can we cleanup the bunch of jars which got along with the commit making the file changes as 37?

Just cleaned up all jars.


Convert CLI configuration to Rust

Our CLI is currently set from a YAML file which makes refactoring harder because we're forced to use string values to get options.

I'll take this up.


use liboverdrop crate

Use the API provided by https://github.com/overdrop/liboverdrop-rs/pull/1.

Accidentally pushed https://github.com/rfairley/fedora-coreos-metrics-client/commit/63f903631d3a68cf0ac70fcdfbff1b69a51f55aa to master, closing this PR. This was a simple change to adapt to the changes in the liboverdrop master - so I think it is OK not to revert it. A follow-up can be done soon to use the liboverdrop crate once published.

I guess this means we now need to release and fedora-package liboverdrop before being able to release and package this. Timewise, do you think it's fine?

Right, yes this does make packaging liboverdrop a blocker. The packaging for liboverdrop should be straightforward, but I don't want to rush work there for this. I'll revert this now - less harm done.
I did build an RPM ready go here for FCOS, but we may still want to add changes upstream (in this repo) before packaging this. Shouldn't block more changes being added based on my accidental push.

Superseded by: #10


Using search will only search open directory, no sub-directories.

Description
When in a folder and using search, it will not show any results for sub-directories.
Steps To Reproduce
Just use search in a directory.
Requirements
Recursive searching.
Files Version
<IP_ADDRESS>
Windows Version
Windows 11 Pro 22631.3810
Log File
debug.log

Thanks for the report, you have to press enter to do a full search, as just typing will search the current folder using a quicker method.

@rivahere typing without pressing enter will filter the current directory (as Josh mentioned), can you confirm if pressing enter starts a regular search?


Rename src/SourceBuild/tarball directory in dotnet/installer

The src/SourceBuild/tarball directory name no longer makes sense with the introduction of the VMR (Virtual Mono Repo).  This directory should be renamed.
A couple suggestions that I have heard are:
src/VirtualMonoRepo/
src/SourceBuild/
Within this folder there would be content/, patches/ and readme.md
This issue was also discussed in https://github.com/dotnet/source-build/issues/2867#issuecomment-1350697418.

[Triage] We discussed this and feel that src/SourceBuild is the better name.

I found this reference that might be worth fixing: https://github.com/dotnet/source-build/blob/466a89576b148ea5d540c5ccfafbf9ffbe2d76c3/eng/submit-source-build-release-pr.sh#L36

@premun - is this work done?  Can this be closed?


Add query_opts option

resolves #213

Coverage increased (+0.01%) to 93.978% when pulling 4983afc6ed274118101544a0f9558a6f55bf8a40 on elridion:main into d21341348b71a159a7e4f23e2320ed1c9fcf5723 on woylie:main.

Thank you!

Happy to help!


FALCON-1985: Disable FeedExportIT and FeedImportIT temporarily

These tests started to fail since may due to some infrastructure changes on the jenkins servers. debugging that will require access to those servers. until then disabling these tests to unblock 0.10 release branch creation.

Build failed, you might have to set enable to false for each individual test.

+1 checks passed. Will commit shortly


🌱  Uplift to github.com/docker/docker v20.10.11

This PR keeps up with https://github.com/kubernetes-sigs/cluster-api/pull/5886/

/test-v1b1-integration

@kashifest would you like to backport this to the release-0.5 branch as well since it is a security vulnerability and we are using the affected version in that branch? Also, cherry-pick bot would not be an option to do it IMO, since it does not run 'go mod tidy' for you.

/lgtm


Chinese

ChineseSimplified.zip

Added the attached ZIP to the dev branch. Will close the PR itself though,
Thanks :)


Request coherent memory for model staging buffer

There is no guarantee in the spec on the order of the following memory types:
VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT | VK_MEMORY_PROPERTY_HOST_CACHED_BIT,
VK_MEMORY_PROPERTY_HOST_VISIBLE_BIT | VK_MEMORY_PROPERTY_HOST_COHERENT_BIT,

which means we can't assume that the first memory type that is host visible is going to be coherent.

Thx for your PR!


Fixed some typos and grammatical errors

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #18307

@freeCodeCamp/spanish-language-editors Please review this

@thecodingaviator looks good, although "requisitos de aprobación" would be better than "requerimientos aprobatorios"
I will look forward to build a doc to standardize those phrases which are common in several files.
You can merge this, and I will start making some of those standardizations later next week.

Thank you for your contribution to the page! 👍
We're happy to accept these changes, and look forward to future contributions. 📝


Add service plan model

https://projects.engineering.redhat.com/browse/SSP-831
This PR is to start the work for custom dialogs. This adds the ServicePlan model and associated migration and associations.
After the migration runs one needs to run rake db:migrate:service_plans<EMAIL_ADDRESS>it will reach out to Topology and get the service plan for each portfolio_item and create a new ServicePlan record.

@miq-bot add_reviewer syncrou
@miq-bot add_reviewer mkanoor

@lindgrenj6 Can we fix the description of the PR to not talk about migration


Default GTK 3 theme folder

There is no default folder for a GTK 3 theme. All GTK 3 folders are targeting a specific version. Would be great to have a gtk-3.0 folder that can be applied whatever version is in use.

I second this. As it stands, it won't work in the GNOME desktop. It requires a gtk-3.0 folder.

Actually, just renaming the gtk-3.20 to gtk-3.0 makes it appear for GNOME, but it does not render properly.

Please rename the gtk-3.14 to gtk-3.0, it should work. Please confirm. Thanks.

That works, thanks.

Just so you know, with this fix I now added support for Typewriter to install-gnome-themes.


[Merge] MONDO_0015989 'congenital valvular dysplasia'

Mondo term (ID and Label)
MONDO:0015989 'congenital valvular dysplasia'
Reason for deprecation
Obsolete in Orphanet
Term to be merged with
MONDO:0034937 FLNA-related x-linked myxomatous valvular dysplasia
(this term is from the pending orphanet ingest): https://github.com/monarch-initiative/mondo/issues/3038
[Term]
id: MONDO:0034937
name: FLNA-related x-linked myxomatous valvular dysplasia
definition: A rare genetic cardiac malformation characterized by progressive myxomatous degeneration predominantly of the mitral valve (but not uncommonly with multivalvular involvement), presenting as valve thickening and dysfunction with variable stenosis, prolapse, and/or regurgitation, and potentially resulting in lethal heart failure. Hyperextensible skin and joint hypermobility have been reported in some patients. Hemizygous males display a more severe phenotype than heterozygous females. [Orphanet:555877]
subset: ordo_morphological_anomaly
synonym: "Dystrophie valvulaire associée à FLNA" EXACT  [Orphanet:555877]
synonym: "Filamin A-related X-linked myxomatous valvular dysplasia" EXACT  [Orphanet:555877]
synonym: "FLNA-related valvular dystrophy" EXACT  [Orphanet:555877]
xref: ICD10:Q22 {source="Orphanet:555877"} {source="Attributed (The ICD10 code is attributed by Orphanet)"}
xref: ICD10:Q22 {source="Orphanet:555877"} {source="NTBT (ORPHA code's Narrower Term maps to a Broader Term)"}
xref: OMIM:314400 {source="Orphanet:555877"} {source="BTNT (ORPHA code's Broader Term maps to a Narrower Term)"}
is_a: MONDO:0020288 {source="Orphanet:555877"} ! atrioventricular valve anomaly
relationship: has_modifier HP:0001419 {source="Orphanet:555877"} ! X-linked recessive inheritance
relationship: disease_has_basis_in_dysfunction_of http://identifiers.org/hgnc/3754 {source="Orphanet:555877"} ! FLNA
xref: Orphanet:555877 {source="MONDO:equivalentTo"} ! flna-related x-linked myxomatous valvular dysplasia
related to:
https://github.com/monarch-initiative/mondo/issues/2912

Isn't https://www.omim.org/entry/314400?search=myxomatous&highlight=myxomatous an exact match?
How is this different from MONDO:0010753, given that OMIM uses MYXOMATOUS VALVULAR DYSTROPHY, X-LINKED; XMVD as an alternate term for CARDIAC VALVULAR DYSPLASIA, X-LINKED; CVD1

@maglott I think you are correct. I think these two terms can be merged with: MONDO:0034937 FLNA-related X-linked myxomatous valvular dysplasia

MONDO:0015989 'congenital valvular dysplasia'
MONDO:0010753 'cardiac valvular dysplasia, X-linked'


Add support for thrift_binary protocol in jaeger receiver

Description

 Fixes #
How Has This Been Tested?

Checklist:

[ ] I have updated the relevant Helm chart(s) version(s)
[ ] I have updated the relevant component changelog(s)
[ ] This change does not affect any particular component (e.g. it's CI or docs change)

test


Add list API support.

I did not add tests in this pull request.

Coverage decreased (-5.8%) to 85.061% when pulling a7fb8018e14d092980370fa8a387023d5583b586 on BenLubar-PR:lists into e804ee7eb264c7bbd58ad9c80291e4d9e2c131a5 on mattn:master.

Thank you. Please add tests

The tests seem to just be testing the encoding/json package. Is this correct, or am I missing something?

Yes, this is guard for not breaking current behavior.

@BenLubar Nice, I was just looking into adding support for lists myself! Looking forward to this PR getting merged!

@muesli I've been a bit busy recently, so if you want to take ownership of this PR and write the tests, feel free

@BenLubar Ok, will do! I'll just open a separate pull request in that case, unless you want to give me permissions to push to your fork. But I guess that's not worth it.

Closed by #93


Device detection / driver issues with raspberrypi0-wifi with systemd images newer than rocko

Description
I have an older, working, image that I wanted to update to the newer branches. Checked all the changelogs, updated things as necessary, built my image, and it didn't work the way it used to. So I stopped trying to use my image and have been building core-image-base.
With systemd, core-image-base boots with barely any device modules loaded, and none of the peripherials work. I do not (ever) see a splash screen.
Steps to reproduce the issue:
When building core-image-base, targeting raspberrypi0-wifi, with the following in my local.conf:
DISTRO = "poky"

DISTRO_FEATURES += " systemd usbhost wifi zeroconf"
DISTRO_FEATURES_BACKFILL_CONSIDERED += "sysvinit"

VIRTUAL-RUNTIME_init_manager = "systemd"
VIRTUAL-RUNTIME_initscripts = "systemd-compat-units"
EXTRA_IMAGE_FEATURES = "debug-tweaks"

I end up with a system that boots to a console, but has no splash screen.
When I run lsmod, I get only the following modules loaded:
ipv6
overlay
sch_fq_code

This is clearly not detecting the hardware properly.
** When rebuilding the same image without systemd **
Everything works as expected from a device / boot perspective.
lsmod returns all driver modules properly loaded, and the system works / boots as expected.
Current layers / branches:
meta-yocto-bsp       = "warrior:38d5c8ea98cfa49825c473eba8984c12edf062be"
meta-oe
meta-python
meta-networking      = "warrior:8d5dcd6522e9d15e68637b6d7dda0401f9bb91d0"
meta-raspberrypi     = "warrior:6c73694912c73187560f657bec24893f184f9b14"

** systemd-udevd reports errors **
Running journalctl | grep 'udev'  reports...
Jul 15 20:28:37 raspberrypi0-wifi systemd[1]: Listening on udev Control Socket.
Jul 15 20:28:38 raspberrypi0-wifi systemd[1]: Starting udev Kernel Device Manager...

Jul 15 20:28:38 raspberrypi0-wifi systemd[1]: Started udev Coldplug all Devices.
Jul 15 20:28:40 raspberrypi0-wifi kernel[98]: [    3.329952] systemd[1]: Listening on udev Control Socket.
Jul 15 20:28:42 raspberrypi0-wifi systemd-udevd[80]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.

This is also occurring on master for these layers.

Nevermind... Issue was that another layer was removing all manner of packageconfigs from systemd.


Perform API changes and import clean-up

This request proposes the following changes:
API

firebase.ts

Add methods for the admin claim
Methods should wait for the Firebase Auth-state to settle before calling its methods
Refactor lines of code to perform nullish coalescing and optional chaining where appropriate
Remove references to the un-verified claim

firebase-admin.ts

Add getDonations() which returns all donation documents
Clean up imports
setClaimsForNewUser(..) should only add the donor claim
addEvent(..) add events to the Events collection
setClaimForAdmin(...) should add or remove admin privileges to a user

firebase-events.ts

Add converter

firebase-donations.ts

activeDonations(...) should log an event if a user id is undefined

firebase-images.ts

Should await for the availability of an user's id

firebase-organizations.ts

Add Firestore converter
Add getOrganizations()
Add setOrganization(...)

firebase-storage.ts

Add Firestore converter
Add addStorage(...)
Add getAllStorage()

firebase-users.ts

Make changes to imports
Add getAllUserAccounts()
Make changes to internal methods for retrieving account information
Add addNote(...) to add a note on a user account
Refactor addUsers.js and listUsers.js within firebase-users.ts. Adding users are managed by calls to Firebase Auth. Retrieving users are handled with calls to Firebase Auth and Firestore.

Components

Browse

Resolve imports with the root alias

DonationCard

Import shared style for all card types Card.module.css (AccountCard.module.css should simply be renamed to Card.module.css)

Header

Resolve imports with the root alias

ProtectedRoute

Define ProtectedRoute as a client component. This addition would enable a ProtectedRoute to be declared within a server component

Models

Event

Add class/collection that will store user initiated events and system events. Events may also be used for standardizing notes sub-collections present in other top-level collections.

Organization

Make changes to imports

Storage

Make changes to imports

User

Make changes to imports

Pages

Join (the user creation) page

Make changes to imports

Login page

Make changes to imports

Site landing page

Make changes to imports
Update the unit test file to resolve an import with the root alias

Types

Add the placeholder Note type
Add the placeholder OrganizationForm type
Add the placeholder Storage type

Thanks, @NathanWEdwards. Quick note on this: looking at Wendy's latest input, it sounds like we might want to keep the default un-verified claim for new users if its not too much of a pain. Might not be mission critical, but sounds like she does do some basic vetting so it could be useful to assume all new users are unverified until she can confirm they are a part of the organizations they've affiliated themselves with.


Content Writing for Home, About page with decoration

Presently, our home page is empty. Do write about the forum & some cool features that helps the user to visit more on the website. Do the same for About Page in which you have to write about the platform as a summary .

Assign this to me

is this issue already assigned? Or can I work on this?

@ronitsingh1405 it is already assigned. You can work on the existing issues as backend developer.
Thanks!


WebAuthn support requirements

Support new public_key type to be variable length and add the supporting serialization and deserialization needed.
Related to
https://github.com/EOSIO/eos/issues/7012
https://github.com/EOSIO/eosjs/issues/537

#659 and #677 addressed WebAuthn support.


FIXED:CHINA EASTERN A320neo

Winglet had some deviations and I fixed it

maybe i will fix it again i should see it in game .


amateuer  question about FastRTPS compilation

I am working on a data distribution service protocol using eProsima FastRTPS in Linux (Ubuntu), but I am not able to make it run because FastRTPS has file "makefile_x64Linux2.6gcc" which i need to compile but i dont know the commands to do it . I have tried make option, too, but still having the same problem. Is there any command for compiling .6cc file ?

i was able to compile by simply using the following command
$ make -f makefile_x64Linux2.6gcc


Fixed slave id access

fixes: https://rollbar.com/thomas-mesosphere/dcos/items/1543/occurrences/6961996376/

Mind giving me a brief explanation of what went wrong here?

I wrote slave.id when it should have been slave['id'].  This code only gets run when a node query matches multiple nodes, so it doesn't get run much

Ah, okay. Thanks!


powerplatform_user support environment without dataverse

This pull request includes significant changes to the powerplatform_user resource, focusing on adding support for environments without Dataverse and updating the user management workflow. The most important changes include adding support for non-Dataverse environments, modifying test workflows, and updating documentation.
Support for Non-Dataverse Environments:

Added support for adding users to environments without Dataverse created. (.changes/unreleased/added-20241118-091212.yaml)
Updated the powerplatform_user resource to handle non-Dataverse environments, specifying that only 'Environment Admin' and 'Environment Maker' roles are allowed in such cases. (docs/resources/user.md) [1] [2]

Workflow Updates:

Modified the test workflow to focus on the TestAccUserResource_Validate_Create_Environment_User test. (.github/workflows/run_tests.yml)

Documentation Enhancements:

Updated the powerplatform_user documentation to include a note about role compatibility when transitioning from non-Dataverse to Dataverse environments. (docs/resources/user.md)

Example Configuration Adjustments:

Commented out the Azure AD and random provider configurations in example files to reflect the focus on non-Dataverse environments. (examples/resources/powerplatform_user/resource.tf, examples/resources/powerplatform_user/outputs.tf) [1] [2]

Internal Code Refactoring:

Added a new Find function to the array helper to facilitate searching within arrays. (internal/helpers/array/array.go)
Refactored the authorization service to distinguish between Dataverse and non-Dataverse user management, including methods for creating, updating, and deleting users in both contexts. (internal/services/authorization/api_user.go) [1] [2] [3] [4] [5] [6] [7] [8]
[Copilot is generating a summary...]

Codecov Report
Attention: Patch coverage is 52.57453% with 175 lines in your changes missing coverage. Please review.

Project coverage is 3.29%. Comparing base (7d15a3d) to head (c6f2a46).

Files with missing lines
Patch %
Lines

internal/services/authorization/resource_user.go
32.82%
118 Missing and 13 partials :warning:

internal/services/authorization/api_user.go
77.16%
31 Missing and 6 partials :warning:

internal/api/lifecycle.go
0.00%
3 Missing :warning:

internal/helpers/array/array.go
57.14%
2 Missing and 1 partial :warning:

...services/authorization/datasource_securityroles.go
0.00%
1 Missing :warning:

:exclamation:  There is a different number of reports uploaded between BASE (7d15a3d) and HEAD (c6f2a46). Click for more details.
HEAD has 1 upload less than BASE

Flag
BASE (7d15a3d)
HEAD (c6f2a46)

2
1

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #529       +/-   ##
==========================================
- Coverage   73.35%   3.29%   -70.06%
==========================================
  Files         105     105
  Lines       14957   15250      +293
==========================================
- Hits        10972     503    -10469
- Misses       3306   14716    +11410
+ Partials      679      31      -648

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests


Fix "Sticky UI Panel" Bug in Create App View

This commit fixes a bug, where the Create App view would "stick"
when there were no Kubes present in the user's configuration.
In order to fix the bug, many NPM package dependancies and README
files were updated.
This commit closes supergiant/supergiant#430

Coverage decreased (-0.02%) to 55.282% when pulling a47c5edf111cc39b8aa0afbdf1246eb73e7ec49c on briansage:onedotoh_issue430 into 11392475f81d5cd3142b02c26682bc31b1a4a4f5 on supergiant:master.


Dockerfile for controller should not need golang as base

The way the current k8s collector (https://github.com/intuit/katlas/blob/master/controller/Dockerfile) runs in the image is not ideal, it should be compiled in prior and put in the alpine base image.
ref: https://github.com/intuit/katlas/blob/master/service/Dockerfile

Created Makefile and modified Dockerfile with alpine base image.
Need to test the changes on Kubenetes minikube.

Testing is done. PR submitted.

Done


Add note in Syslog docs on scenario when UDS is used

@guywi-ms

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Add WordPress database fields to env file

Targets #918

Description

Moved WordPress database configurations to .env file.
Corrected Spelling of prefix.
Updated installation document.

Checklist:

[x] I have performed a self-review of my own code.

@kuldeep3 Can you alos review this once.


I do not see how to run xray here

I went through the readme and I did not see how to run xray along with Fatgate here. Maybe I am missing something?

I got it to work using this gist:
https://gist.github.com/surjikal/7f7cb8db96fb2f1ce21dddb10ec244d0


add randStrSeed to support   read after write massive data cases

feat #44

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.weixiaotong seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Environment variables not detected when used in config file from an imported source

Versions

nuxt: v2.15.7
node: v16.7.0

Reproduction
https://github.com/dvlden/nuxt-generate-bug
Steps to reproduce

clone reproduction repository
install dependencies
yarn run generate
check dist/index.html, the custom meta tag will contain value of APP_SPECIAL env. variable, which is holy.sh
edit contents of .env file by changing APP_SPECIAL to something else
yarn run generate
check dist/index.html, the custom meta tag will remain untouched, the meta content will be what it was initially
rm -rf dist .nuxt
yarn run generate
still old value, it doesn't detect the change

What is Expected?
All process.env variables should exist so that their change can be tracked. This isn't the case when something is imported inside nuxt.config.js and used for configuration.
What is actually happening?
It seems that nuxt doesn't pick up env. variables that appear to be unused?
If you inspect @nuxt/cli/dist/cli-generate.js and log the currentBuild, you'll notice that process.env only contains APP_SOMETHING which is used in nuxt.config.js directly, through the constant.
However, APP_SPECIAL is non-existent within process.env, but it's being imported from a file and used in example to create contents of a meta tag. I assume we could've use the imported constant for some other purpose too and it wouldn't detect a change.
This problem is happening for all nuxt scripts, not just generate.

@danielpost That's works, but slows down the repeated process, as it doesn't cache anything.
"To avoid rebuilding when an unimportant env variable changes, Nuxt checks your nuxt.config for usage."
Yes I noticed that, but how come it doesn't check for env variables that were used in other files and were imported in config and used for some part of config? That bit kind of makes no sense. I just used a single file to cleanup nuxt config file and extract some utilities there, that happen to use env variables... Is there a way to at least tell it Nuxt, to also check some other files for important env variable changes?

A new ignoreEnv option is coming with 2.16 (https://github.com/nuxt/nuxt.js/pull/8955) which you can try by using nuxt-edge or using the workaround mentioned by @danielroe to explicitly add used envs.
/note: For nuxi/nuxt3 we should try a proxy-based implementation to track process.env accessing

Perfect!
Thank you @danielpost for that workaround and thank you @pi0 for useful information about a new upcoming feature.


getrandom(2) is missing from the bindings

We have getentropy, but not getrandom

This can't be implemented until glibc in CI becomes 2.25, adding this binding will break the crate for < 2.25.

Hi @marmistrz  ! I am trying to clean-up issues: is this still an issue for you?
(btw, I would recommend lib rand or other cryptographic libraries instead of relying on getrandom(2))

@kristate I'm not currently working on the project which needed that, but I still consider this an issue. I should be able use getrandom if my libc is new enough. Otherwise, it defies the purpose of this crate.
IIRC the project did something pretty low-level and thus I wanted to use the syscall directly, but I don't remember the details.
maybe you should do a feature build, just like gtk-rs does - e.g. I can explicitly demand glibc >= 2.25 in my cargo.toml - or just say that I demand that the libc supports getrandom, and then the bindings are generated.

The version of glibc being targeted on CI (and therefore, the minimum version of glibc supported), has been updated. Please feel free to submit a PR implementing these.

The version of glibc being targeted on CI (and therefore, the minimum version of glibc supported), has been updated. Please feel free to submit a PR implementing these.

My understanding from https://lwn.net/Articles/711013/ is that glibc does NOT implement a fallback in the case that the getrandom() syscall is unavailable. Is that correct, or have things changed? If so, I agree it is a really good idea to expose libc::getrandom() so that no Rust code needs to use the vararg syscall function. (varargs are a bad idea, in general.)


Comment out "checkOwners" since it doesn't work expectedly now

WHAT
This pull request comments out (disable) "checkOwners" since it doesn't work expectedly now.
WHY
It's possible to override "image" with any docker images with violation because now the validation admission webhook for Deployment doesn't check "UPDATE" operation, then Kritis allows any docker images in ReplicaSet and Pod creation because of the checkOwners.
If we add "UPDATE" operation to the webhook for Deployment, the webhook can get AdmissionReview for Deployment update but it cause another issue which we can't know the admission comes from "UPDATE" or "DELETE" operation. (Both sends "UPDATE" admission)
It's probably because the admission's Kind is "extensions/v1beta1" and it doesn't support "DELETE" operation.
So for now it's better to disable the checkOwners so that we can reject docker images when Deployment updated.

Adding some supplement information. The current issue is, it is possible to change docker image of a pod using kubectl edit pod command to any docker image. Validation webhook will skip new image validation check because it will first try to check its owner (Deployment) image. When a pod image is edited to a different image, it does not change Deployment image. So, Deployment image is still same (old one) which is already passed by validation webhook. And validation webhook will let it go.
For now it make sense to just diable owner check functionality. It does save some time when there are many pods of same deployment. In that case it will only check once instead of checking for each pod. It is good for optimization but there is a security loophole. So, lets just diable it.

Thank you for the review and clarifying.
I'm going to merge it 💪


Avoid minor version dependencies in gemspec

Dependencies like ~> x.y.z are not recommended to use in gemspec because they cause version conflicts like in screenshot. Use ~> x.y instead. Due to semantic versioning this won't break the gem because new features aren't released in patch versions of gems.

You'll notice that many of the dependencies are in the 0.x range, where semver is explicitly not honored. For these I explicitly want x.y.z style specification as API breakage can occur any moment.
As unparser does something "tricky" (reproducing ruby syntax) even smaller differencies in the parser version (fixing bugs) can have a big impact on unparser correctness. So its better to keep unparser close to the latest supported parser via x.y.z style dependency.
In the past I had more opensource time, so I could track parser development more closely. These days I do not have the time to stay in close sync. But I prefer unparser does not bundle against very new parser, instead allowing incorrect combinations.
For example your PR whitelists parser 2.3.x that brings new nodes unparser does currently not support.


Basic styles for web UI

Changes
Fixes #10

Why Are Changes Being Made
The styles are minimal but go a long way to making the list of ACH files and each file (along with any errors) easier to grok. Screenshots above are in dark mode, though light mode was added as well and is honored from system preferences. Works on just about anything with a browser.

Awesome, thanks Josh!!


[Question] Build Static Libraries

The README.md states the following:

It can also produce standalone dynamic or static libraries that can be consumed by applications written in other programming languages.

But I can't find information about how to do it. Can sombody give me more information?

@deinok I have polished the WIP docs in https://github.com/dotnet/corert/pull/6645. Please take a look and give us feedback on the instructions worked for you.

@jkotas Really nice work. Probably I'm missing something, but why is NativeCallableAttribute attribute not included in source?

Also, does the generated files have some runtime dependencies other than the OS itself?

Probably I'm missing something, but why is NativeCallableAttribute attribute not included in source?

CoreRT shares the public API definition with .NET Core. NativeCallableAttribute was not added as public .NET Core (yet), so this workaround it necessary for now.

Also, does the generated files have some runtime dependencies other than the OS itself?

The runtime dependencies are fully self-contained. The binary has same OS dependencies as .NET Core.  (It only really matters on Linux - there is a list of OS packages that it needs.)

CoreRT shares the public API definition with .NET Core. NativeCallableAttribute was not added as public .NET Core (yet), so this workaround it necessary for now.

Thanks for the change on the docs.

The runtime dependencies are fully self-contained. The binary has same OS dependencies as .NET Core. (It only really matters on Linux - there is a list of OS packages that it needs.)

So, for what I understand a *.so generated via CoreRT will just require the same *.so that .NETCore
Runtime requires (the same a common publish -r  will need), not the .NETCore Runtime itself

Right

@jkotas Thanks for the info :)


Feature to view and download value of property from UI

Fix https://github.com/apache/skywalking/issues/11974
Large amount of text to display in property value

[ ] Add a unit test to verify that the fix works.

[X] Explain briefly why the bug exists and how to fix it.
The issue was caused due to the use of property value being very long in some cases resulting in bad UX. The fix ellipsizes the content of the value beyond 20 characters and provides a new popup to view and download the value of a property.

[ ] If this is non-trivial feature, paste the links/URLs to the design doc.

[ ] Update the documentation to include this new feature.

[ ] Tests(including UT, IT, E2E) are added to verify the new feature.

[X] If it's UI related, attach the screenshots below.

https://github.com/apache/skywalking-banyandb/assets/53624363/dff66b02-b8a6-4c93-95b9-3f794a028601

@hanahmily I noticed, the approval is not dismissed when new changes are applied.
You should update .asf.yaml

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

Project coverage is 47.79%.  Consider uploading reports for the commit 00daa83 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #414      +/-   ##
==========================================
- Coverage   47.80%   47.79%   -0.02%
==========================================
  Files         173      173
  Lines       21562    21562
==========================================
- Hits        10308    10305       -3
- Misses      10380    10382       +2
- Partials      874      875       +1

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


Expand list of extensions of known binary types

I thought it would be a good idea to:

Start keeping a list of known binary types.
When files with those extensions are found, is_binary() returns True and the code that checks the file's starting chunk is bypassed.

This list just includes .pyc to start, but perhaps it should be expanded.
The code: https://github.com/audreyr/binaryornot/commit/b748fc18824d3de586ff75ec4cea3fd5a7fc212c
Thoughts or feedback? What about the use case where a file might need to be checked despite its extension?

I'm not sure if that's a good idea in the first place as you might get false positives. I think you still need to perform the check.


Redirect to server after creation

We want to give the user a smooth experience, this can be improved by
redirecting to the server object after it has been created. That way the user
gets a better feeling of the Server creation flow.
Fixes #13
/cc @brambokdam

:shipit:


v3 - updateLayers issue

Double-call
https://github.com/uber/deck.gl/blob/dev/src/react/deckgl.js#L100
Calls updateLayers on the layer manager, then this._updateLayers which calls updateLayers again on the layer manager with the same arguments.
Synchronous setState
Also noticed that this._updateLayers is called immediately after setState. setState is asynchronous, so https://github.com/uber/deck.gl/blob/dev/src/react/deckgl.js#L83 will evaluate to false. The end result is the context not being set, which leads to:

Could solve both by removing L100 and moving L101 to be the callback on the setState. LMK if you want a PR.

closed by #129, not sure why it didn't autoclose it


Unable to use jwt-decode with typescript project

Description
I am trying to use jwt-decode in a typescript project i.e. Stencil Project & it is throwing following error:
import * as jwt_decode from 'jwt-decode';
.
.
.
let token = "........";
let decoded = jwt_decode(token);

This expression is not callable.Type '{ default: (token: string, options?: Options) => TTokenDto;
}' has no call signatures.

Reproduction

install jwt-decode in any typescript project

npm install --save @types/jwt-decode
npm install --save jwt-decode

import it in your code & use

import * as jwt_decode from 'jwt-decode';
.
.
.
let token = "........";
let decoded = jwt_decode(token);

build project

Please provide the following:

Version of this library used: ^2.2.0
Version of the platform or framework used, if applicable: stencil - ^1.3.3 , typescript - 3.7.2

You can import the jwt_decode directly
import jwt_decode from 'jwt-decode';

let token = "........";
let decoded = jwt_decode(token);

Hi @rahulbhooteshwar, here's an example Typescript project with jwt-decode.

I tried this but vscode gave me an error saying 'This expression is not callable'

I tried this but vscode gave me an error saying 'This expression is not callable'

@showduhtung I'm getting the same error 'This expression is not callable', so I use it like this and it's working for me. I don't get why I have to pass the payload myself though.
import jwt_decode, { JwtPayload } from 'jwt-decode'

const decodedToken = jwt_decode<JwtPayload>(token)

I resolved this issue as follows:
import jwt_decode, { JwtPayload } from 'jwt-decode';
const decoded = jwt_decode(token || '') || null;
console.log(decoded); // {id: "601872b3eee5d0001c1cdcb2", iat:<PHONE_NUMBER>, exp:<PHONE_NUMBER>}

Hi @fabramosdev  Thanks , it really works but could not fetch that value from this object and get the separate value. Could you tell me how to do that. Thanks in advance.

Hi @fabramosdev Thanks , it really works but could not fetch that value from this object and get the separate value. Could you tell me how to do that. Thanks in advance.

Hi, in case you want to get each value separately inside the object?
If I understand your question correctly, because of the typescript you can call "decoded.iat", "decoded.exp" or even in this case shown the "decoded.id".
Hope this helps

Hi @fabramosdev  , yes I tried that, but it is not working in .ts file but in .js . Is there any way to fetch the values in typescript. I am getting compile time error while fetching the value using {decoded.iat}.

Oh, I have the same problem as @RituparnaA2Z-CM!
My code is
import jwt_decode, {JwtPayload} from 'jwt-decode'; getCustomerId(){     let token =  this.getToken();     let decoded = jwt_decode<JwtPayload>(token ||'') || null;     console.log('Token aus getCustomerId: ' + decoded)   }
But in the console I just get an object
console.log from Browser: Token aus getCustomerId: [object Object]

@vskowronsky hey I have solved the issue. Just type cast it with your object model. Let say,
export class Model {
field1: string;
field2:string;
field3:string;
}
import the model from package path;
import jwt_decode, { JwtPayload } from 'jwt-decode';
const decoded = jwt_decode(token || '') || null;
console.log(" fetching field 1 -----", decoded.field1);
console.log(" fetching field 2 -----", decoded.field2);
console.log(" fetching field 3 -----", decoded.field3);

Thank you very much for answering :-)
I did try your approach but it did not work for me.
This is my code, that worked for me in the end:
getCustomerId(){
let decoded = jwt_decode<JwtPayload>(this.getToken());
    console.log('Token aus getCustomerId: ' + decoded['data'].id)
return decoded['data'].id
 }
data is the name of the payload field in my token. I had to reference it in square brackets and then look for the id.
Hope that is helpfull for any one else as well. It is always good to have alternatives.

@vskowronsky  thank you so much for another option. Yes, it is very much true to have second options in case but sad to know that my approach did not work for you :(. Anyways happy to know that you fixed it.

I came across the same "This expression is not callable" problem, and specifying the type did not solve the issue.
I was however able to fix it by calling jwtDecode.default<JwtPayload>(...) instead. Not sure why that's a thing, but I thought I'd share in case anyone has the same problem!

I came across the same "This expression is not callable" problem, and specifying the type did not solve the issue. I was however able to fix it by calling jwtDecode.default<JwtPayload>(...) instead. Not sure why that's a thing, but I thought I'd share in case anyone has the same problem!

When in a standard ESM module it's not a problem:

However from TypeScript:

TypeScript sees it as module import not a function per se, and this happens whenever moduleResolution is set to NodeNext. I think this a bug per se with TypeScript since Node ESM resolution is inferring types correctly.
However a middleground approach until fixed could be to change the exports to e.g.:
export function decode(token, options) {
}

export default decode;

The in the TypeScript defintions defined the following:
...
export function decode<T = unknown>(
  token: string,
  options?: JwtDecodeOptions
): T

export default decode;

Then TS would resolve the module correctly.

And it would still be backwards compatible.

Hi I am having this issue.
"moduleresolution": "nodenext"

If some of you are still trying to figure it out try "import {jwtDecode} from 'jwt-decode'

⚠ It's a named export so it must be imported this way:
import { jwtDecode } from "jwt-decode"


Add SUSD Token

Please check the following to ensure a successful verification of Token Profile
.json and .png document checklists
logo dimensions: Link to download a 28X28 png icon logo: https://starsc.io/branding.php
Token Symbol: SUSD
Token Contract Address: ( need it Assistance)
Supported Exchanges:Nil
Suggested Gas limit setting (default is 60,000):60,000
Social Media :
Facebook : https://www.facebook.com/STAR-Secure-Tangible-Asset-Reserve-107270137533909/?tn-str=k*F
LinkedIn :https://www.linkedin.com/company/starsc/
Telegram: https://t.me/Starsecure
Project Team background
Chew Lih Ren, Chief Executive Officer
Linkedin Profile:
https://www.linkedin.com/in/chew-lih-ren-ab25ab84/
Lynn Heng, Chief Technology Officer
Linkedin Profile:
https://www.linkedin.com/in/lynn-heng
En Shen, Chief Finance Officer
Linkedin Profile:
https://www.linkedin.com/in/en-shen-lew-13512419b/
Project basic information: Star Stable Coins (STAR) endorsed by World Digital Central Bank (WDCB), is a 1-1 asset backed stablecoins that is fully collaterized, legally protected and transparently verified by 3rd party attestations.

{
"symbol": "SUSD",
"address": "0xe8dE351d8F949B2FFb8068a84a3bC8034874fd32",
"overview":{
"en": "Star Stable Coins (STAR) endorsed by World Digital Central Bank (WDCB), is a 1-1 asset backed stablecoins that is fully collaterized, legally protected and transparently verified by 3rd party attestations."
},
"website": "https://starsc.io/",
"whitepaper": "https://starsc.io/download/StarStableCoinsWhitepaper-English.pdf"
}

非常抱歉，该PR的Json格式不正确，请参考其他PR或教程重新提交，这个PR关掉了。

为确保 Token Profile 的顺利通过，务必逐一确保以下检查项并补充项目资料：
.json 及 .png 文件检查项
logo 尺寸：120*120 px
logo 背景：透明
代币有至少一笔成功的转账记录
此项对于 ERC-20 项目方：合约地址有大小写（做 checksum）
.json 和 .png 文件名一致（包括大小写）
项目资料：
官方公告：
团队背景：
项目基本情况：
媒体报道：
收录的交易所：
转账所需 Gas Limit（对 ERC-20 项目方）：（默认为 60000）
Please check the following to ensure a successful verification of Token Profile
.json and .png document checklists
logo dimensions: 120*120 px
logo background: Transparent
At least one transaction on the token contract
For ERC-20 project teams: Upper and lower capitalized alphabets in token address (For checksum purposes)
Same document name for both .json and .png (Including capitalization)
Project background:
Official announcement: https://t.me/Starsecure
Project team background:
Project basic information: Star Stable Coins (STAR) endorsed by World Digital Central Bank (WDCB), is a 1-1 asset backed stablecoins that is fully collaterized, legally protected and transparently verified by 3rd party attestations.
Media publications:
Tradeable exchanges:
Recommended Gas Limit (For ERC-20 project teams) for transaction: 60,000


move deis workflow minio to deployments

fixed in https://github.com/TheNewNormal/kube-solo-osx/releases/tag/v0.9.7


inlining carry propagate

name          old time/op  new time/op  delta
Add-10        5.05ns ± 2%  4.63ns ± 1%   -8.44%  (p=0.000 n=10+10)
Sub-10        5.36ns ± 0%  4.93ns ± 1%   -8.06%  (p=0.000 n=8+10)
Negate-10     5.49ns ± 0%  4.00ns ± 0%  -27.03%  (p=0.000 n=9+9)
SetBytes-10   6.77ns ± 0%  6.81ns ± 1%   +0.69%  (p=0.041 n=9+10)
Equal1-10     20.0ns ± 0%  20.1ns ± 0%   +0.62%  (p=0.000 n=10+8)
Equal2-10     20.0ns ± 0%  20.1ns ± 0%   +0.71%  (p=0.000 n=9+10)
Mul32-10      5.57ns ± 0%  5.56ns ± 0%   -0.03%  (p=0.049 n=10+9)
Mul-10        42.6ns ± 0%  42.3ns ± 1%   -0.87%  (p=0.002 n=9+10)
Square-10     31.4ns ± 0%  30.8ns ± 0%   -1.81%  (p=0.000 n=10+10)
Inv-10        14.5µs ± 0%  14.5µs ± 2%     ~     (p=0.897 n=10+10)
SqrtRatio-10  14.6µs ± 1%  14.4µs ± 1%   -1.33%  (p=0.000 n=10+10)

name               old time/op  new time/op  delta
KeyGeneration-10    273µs ± 2%   265µs ± 1%  -2.95%  (p=0.000 n=10+9)
NewKeyFromSeed-10   268µs ± 1%   263µs ± 0%  -1.83%  (p=0.000 n=10+9)
Sign-10             288µs ± 1%   283µs ± 1%  -1.67%  (p=0.000 n=9+10)
Verify-10           536µs ± 1%   523µs ± 1%  -2.48%  (p=0.000 n=10+9)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

125 of 125 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.7%) to 56.893%

Totals

Change from base Build<PHONE_NUMBER>:
0.7%

Covered Lines:
4329

Relevant Lines:
7609

💛  - Coveralls


Integer out of range on startup

Expected Behavior
Bot to start up and walk around as intended
Actual Behavior
Starts scanning area for objects then crashes
Steps to Reproduce
Other Information
Error: [2016-07-26 21:59:30] [#] Scanning area for objects (1 / 25) Traceback (most recent call last):   File "pokecli.py", line 220, in <module>     main()   File "pokecli.py", line 211, in main     bot.take_step()   File "/home/PokemonGo-Bot/pokemongo_bot/__init__.py", line 36, in take_step     self.stepper.take_step()   File "/home/PokemonGo-Bot/pokemongo_bot/stepper.py", line 53, in take_step     self._walk_to(self.config.walk, *position)   File "/home/PokemonGo-Bot/pokemongo_bot/stepper.py", line 67, in _walk_to     i2f(self.api._position_lat), i2f(self.api._position_lng), lat, lng)   File "/home/PokemonGo-Bot/pokemongo_bot/cell_workers/utils.py", line 98, in i2f     return struct.unpack('<d', struct.pack('<Q', int))[0] struct.error: integer out of range for 'Q' format code
OS: Ubuntu 16.04
Git Commit: 3aca6d798f8a3e173dce0beb7b13c9505cc5b251
EDIT:
Happens in both master and dev branch

Same here...
Traceback (most recent call last):
  File "pokecli.py", line 250, in <module>
    main()
  File "pokecli.py", line 236, in main
    bot.start()
  File "/Users/me/Development/Personal/PokemonGo-Bot/pokemongo_bot/__init__.py", line 36, in start
    self._setup_api()
  File "/Users/me/Development/Personal/PokemonGo-Bot/pokemongo_bot/__init__.py", line 275, in _setup_api
    self.login()
  File "/Users/me/Development/Personal/PokemonGo-Bot/pokemongo_bot/__init__.py", line 255, in login
    lat, lng = self.position[0:2]
  File "/Users/me/Development/Personal/PokemonGo-Bot/pokemongo_bot/__init__.py", line 27, in position
    return (i2f(self.api._position_lat), i2f(self.api._position_lng), 0)
  File "/Users/me/Development/Personal/PokemonGo-Bot/pokemongo_bot/cell_workers/utils.py", line 118, in i2f
    return struct.unpack('<d', struct.pack('<Q', int))[0]
struct.error: integer out of range for 'Q' format code

Same issue here as well.
No modifications to source made, just straight out of the box with only a setup config.json.
My config:
{
    "auth_service": "ptc",
    "username": "xxx",
    "password": "xxx",
    "location": "40.783003,-73.965902",
    "gmapkey": "xxx",
    "max_steps": 5,
    "mode": "all",
    "walk": 4.16,
    "debug": false,
    "test": false,
    "initial_transfer": 0,
    "location_cache": true,
    "distance_unit": "km",
    "item_filter": "101,102,103,104",
    "evolve_all": "NONE"
}

ideas? it worked for me a second ago

Same error for me. Was working 30 minutes ago, I changed the location in the config.json file, and bam, now it's not working. I went and changed the loc again, still not working.
[2016-07-26 15:14:29] [x] Initial Transfer.
[2016-07-26 15:14:29] [x] Preparing to transfer all duplicate Pokemon, keeping the highest CP of each type.
[2016-07-26 15:14:29] [x] Will NOT transfer anything above CP 400
[2016-07-26 15:14:29] [x] Transferring Done.
[2016-07-26 15:14:29] [#]
[2016-07-26 15:14:29] [x] Starting PokemonGo Bot....
[2016-07-26 15:14:29] [#] Scanning area for objects (1 / 25)
Traceback (most recent call last):
File "pokecli.py", line 220, in
main()
File "pokecli.py", line 211, in main
bot.take_step()
File "C:\Users\jring_000\Downloads\Pokemon\PokemonGo-Bot-master\PokemonGo-Bot-master\pokemongo_bot_init_.py", line 36, in take_step
self.stepper.take_step()
File "C:\Users\jring_000\Downloads\Pokemon\PokemonGo-Bot-master\PokemonGo-Bot-master\pokemongo_bot\stepper.py", line 53, in take_step
self._walk_to(self.config.walk, *position)
File "C:\Users\jring_000\Downloads\Pokemon\PokemonGo-Bot-master\PokemonGo-Bot-master\pokemongo_bot\stepper.py", line 67, in _walk_to
i2f(self.api._position_lat), i2f(self.api._position_lng), lat, lng)
File "C:\Users\jring_000\Downloads\Pokemon\PokemonGo-Bot-master\PokemonGo-Bot-master\pokemongo_bot\cell_workers\utils.py", line 98, in i2f
return struct.unpack('<d', struct.pack('<Q', int))[0]
struct.error: integer out of range for 'Q' format code

same here...

Ok so its working on my ubuntu but failes in my win 10...

In mine, the "int" parameter being passed in is actualy a float.

I have same error, it was working fine couple hours ago, is it new bug?

The history shows that the last update was 19 hours ago and that was only to the readme, so it seems that people who it was working with earlier today and now it's not.. Maybe the server was updated and is responding with a different value than the script expects?

Can we confirm that #1046 solves? I cannot seem to implement it

The latest dev branch works for me now havent tried the master

Commit has been reverted, please repull. #1065


dockerTools: add support for ARM variants

Description of changes

Things done

Add support for ARM architectures that require a variant field with the ARM version (e.g. "v8", "v7"...)
This PR is a successor to https://github.com/NixOS/nixpkgs/pull/119683 that is marked as stale since Oct 22, 2021

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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/)
22.11 Release Notes (or backporting 22.05 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

@ofborg test docker-tools

There's an evaluation error in nixosTests.docker-tools on x86_64-linux and it seems we should run those tests on all system types:
nixos/tests/all-tests.nix:
-  docker-tools = handleTestOn ["x86_64-linux"] ./docker-tools.nix {};
+  docker-tools = handleTest ./docker-tools.nix {};

For some unknown reason, cross-compiling cannot be done on aarch64-darwin and x86_64-darwin. Nix sends me the following error message:
error: infinite recursion encountered

Should we restrict the supported OS to Linux only, or is this just a common problem when attempting to cross-build a Mac application from Linux?

Custom file used for testing

{ pkgs, ... }:

pkgs.pkgsCross.x86_64-darwin.dockerTools.buildLayeredImage {
  name = "test";
  tag = "0.0.1";
  contents = [ pkgs.pkgsCross.x86_64-darwin.hello ];

  created = "now";

  fromImage = pkgs.pkgsCross.x86_64-darwin.dockerTools.pullImage {
    imageName = "docker.io/library/busybox";
    imageDigest = "sha256:ef320ff10026a50cf5f0213d35537ce0041ac1d96e9b7800bafd8bc9eff6c693";
    sha256 = "sha256-9T6tP/xnZwaTH+qkbkVuXhCk+qZGE3WBY8T+Ug4qCmc=";
    finalImageName = "docker.io/library/busybox";
    finalImageTag = "stable-uclibc";
    #os = "linux";
    #arch ="arm";
    #variant = "v7";
  };

  config = {
    Env = [
      "DEBUG=false"
    ];

    WorkingDir = "/";

    Entrypoint = [ "/bin/hello" ];
  };
}

cannot be done on aarch64-darwin and

Can't find a release where pkgsCross.x86_64-darwin.stdenv evaluated, so that does seem pretty broken, but macOS doesn't run containers anyway. We can restrict it to linux afaic.

darwin as a build platform should work though.

Shouldn't I make an entry in the release notes since we are making breaking change?

A note in the release notes nixos/doc/manual/from_md/release-notes/rl-2211.section.xml would indeed be appreciated. Don't forget to run ./nixos/doc/manual/md-to-db.sh.

You could reuse much of the corrected deprecation error for that.


Json schemas fix

deleted "items" in not array objects

Changes Unknown when pulling f658e30648100a232bf94f9b4a18c0082b1d0567 on json_schemas_fix into ** on master**.

Changes Unknown when pulling 92ecc47352cb55ac1f8c50bb04a5152ce38d14a6 on json_schemas_fix into ** on master**.


HotReload breaks components rendering when 'component' has 'key' property set inside keep-alive

Version
3.3.0
Environment info
Environment Info:

  System:
    OS: Linux 4.9 Debian GNU/Linux
9 (stretch) 9 (stretch)
    CPU: (2) x64 Intel(R) Core(TM) i7-5650U CPU @ 2.20GHz
  Binaries:
    Node: 10.15.0 - /usr/local/bin/node
    Yarn: 1.12.3 - /usr/local/bin/yarn
    npm: 6.4.1 - /usr/local/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce

See the Demo video
Download the attached archive Bug.zip and extract it
npm install
./node_modules/.bin/vue-cli-service serve
Edit the file src/ui/project-editor-view.vue changing the JavaScript portion in any way and see HMR failing

See src/ui/main-view.vue which contains additional note.
What is expected?
Hot Reload should work as expected
or
the usage of
<keep-alive>
    <component :key="key" :is="component"/>
</keep-alive>

should be forbidden at all.
What is actually happening?
Components get unmounted without any error or reason, resulting in a lot of struggles looking for the reason of the mysterious vanishing.
I don't know if this is an intended behavior, but the result is misleading.

Any developments on this? It ruins hmr..

I'll close this since this is tracked in the mentioned issues. Please look up progress there.


UofT-DSI | Visualization - Assignment 4

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
I have uploaded my final files for visualization assignment 4. I have included my 2 visuals, supporting documentation, the answered md for the assignment and links to the dataset.
What did you learn from the changes you have made?
Building visuals is time consuming. There is a lot of effort on your end to reshape the data, design the visual, write the code and ensure you apply design/accessibility principles
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
APproach was to use the skills I am familiar with. What we learned in class, and using some of my previous experience in Tableau. For my tableau map, it could have been completed in Power BI but preferred the accessibility of online experience with tableau.
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
Ensuring the data is shaped appropriately, such that the df columns are named the same, same format and can be used for my design purpose
How were these changes tested?
the python file would be run to ensure the plot is interactive and the tableau image, to ensure I can find the image online
A reference to a related issue in your repository (if applicable)
n/a
Checklist

[ ] I can confirm that my changes are working as intended

Good job!
A4 complete


install issue: Nix does not find rimraf, tsc etc.

On a fresh Ubuntu 22.10 instance, I tried install via cloning and running "nix run". This yielded:
error: builder for '/nix/store/7izay7wmrs2cdcggjafylvlk2577mj72-blockfrost-backend-ryo.drv' failed with exit code 127;
       last 10 log lines:
       > ➤ YN0000: └ Completed in 0s 409ms
       > ➤ YN0000: ┌ Fetch step
       > ➤ YN0013: │ 915 packages were already cached
       > ➤ YN0000: └ Completed in 0s 664ms
       > ➤ YN0000: ┌ Link step
       > ➤ YN0007: │ esbuild@npm:0.16.17 must be built because it never has been before or the last one failed
       > ➤ YN0000: └ Completed in 15s 747ms
       > ➤ YN0000: Done with warnings in 17s 158ms
       > building
       > command not found: rimraf  (note: or tsc, see below)

I tried various combinations of yarn install, npm install, lock file deleting, and removing rimraf from the package.json - which then resulted in the same error for tsc instead; as I've tried installing rimraf globally before, I suspect this is a nix issue, which I am unable to figure out myself.
another one I arrived at is:
error: builder for '/nix/store/l8i7zas8hzsn7hhgasd5bdj2c4n8bhvk-blockfrost-backend-ryo.drv' failed with exit code 1;
       last 10 log lines:
       > ➤ YN0056: │ tapable@npm:2.2.1: Cache entry required but missing for tapable@npm:2.2.1
       > ➤ YN0056: │ terser-webpack-plugin@npm:5.3.8: Cache entry required but missing for terser-webpack-plugin@npm:5.3.8
       > ➤ YN0056: │ terser@npm:5.17.3: Cache entry required but missing for terser@npm:5.17.3
       > ➤ YN0056: │ update-browserslist-db@npm:1.0.11: Cache entry required but missing for update-browserslist-db@npm:1.0.11
       > ➤ YN0056: │ watchpack@npm:2.4.0: Cache entry required but missing for watchpack@npm:2.4.0
       > ➤ YN0056: │ webpack-sources@npm:3.2.3: Cache entry required but missing for webpack-sources@npm:3.2.3
       > ➤ YN0056: │ webpack@npm:5.82.1: Cache entry required but missing for webpack@npm:5.82.1
       > ➤ YN0013: │ 936 packages were already cached, 55 had to be fetched
       > ➤ YN0000: └ Completed in 0s 865ms
       > ➤ YN0000: Failed with errors in 1s 500ms
       For full logs, run 'nix log /nix/store/l8i7zas8hzsn7hhgasd5bdj2c4n8bhvk-blockfrost-backend-ryo.drv'.

... and also failed at installing those manually with yarn. Npm install yields
npm ERR! 404 Not Found - GET https://registry.npmjs.org/0.16.17 - Not found

Update: local docker build appears to be working, so I'll roll with that.

A simple nix run in a fresh nixos/nix docker instance also does the trick.

To reproduce the issue?
I've tried different machines and Ubuntu 20.04 VM with freshly installed Nix and cannot seem to be able to reproduce - both master and custom-network work for me with nix run. Are you possibly on Darwin? (I'm testing on x86)

To reproduce the issue?
Are you possibly on Darwin?

No, to get it to work as intended. Current setup is Ubuntu 22.10, running a vanilla nix/nixos docker, in which I am following the instructions of this repo successfully.
It appears that with mere Ubuntu 22.10 & nix the yarn setup fails somehow. Manually running yarn/node install didn't work as well, and I would not expect them to do the trick either, as I assume nix wants to have the stuff in the nix system anyways, not the ubuntu one.

I want to note that running the dockers - both from hub and built within the nixos-docker, then exported to ubuntu - works.

Cool! Regarding the shell troubles - nix-shell (or more recent nix develop  alternative) should put you in a shell where all the dependencies are available and you should be able to just run for example yarn run dev to start the server which uses config/development.yaml.

Right, so the mistake was that I did not parse "Nix" to mean "either Nixos or nix shell" but only as "either Nixos or Unix with Nix installed". However it still does not work that way - nix develop installs a bunch of stuff, then, without error, just gives me back the regular shell; nix-shell gives some warnings, then the same rimraf-error when running nix run. Note that this is tested on the custom-network branch.
I am as I said before working with the docker anyways now, so I don't have a need to be able to build it myself. Leaving the issue open since technically etc., but from my side it can be closed for now. Thank you for the assistance.

a simple docker build without touching anything nix works as well (need to build the custom-network branch docker, hence). I don't know why it failed before, this time I did a fresh clone & checkout custom-network".

Update: nix-shell, yarn install and yarn start appear to be working. Leaving the issue open as it's not the approach in the readme.

Found out we have this in CONTRIBUTING.md, so closing this.


Bumped GitHub spellcheck action to latest version: 0.35.0

Hello
As the maintainer of the spellcheck GitHub action I am sunsetting version 0.23.0 as by the proposed sunset policy
I have updated the action to version 0.35.0, so this PR offers an update to the latest version.
Let me know if you have any issues with the proposed PR and I will do my best to accommodate.
I can recommend Dependabot for keeping your GitHub actions up to date, alternatively there are Renovate, if you want a PR proposing a basic configuration for Dependabot, please let me know.
jonasbn

Hi @sarroutbi
Do note version 0.40.0 of the Spellchecker action was released this morning.

Hi @sarroutbi
I will be removing the Docker image for version 0.23.0 from DockerHub soon, so please consider getting this merged or your action updated.
Do note version 0.32.0 was a recommended security update.
REF:

https://github.com/rojopolis/spellcheck-github-actions/blob/master/CHANGELOG.md#0320-2023-05-18-security-patch-release-update-recommended


Remove obsolete sed command

Due to the fix committed in 041d232, these commands are no longer necessary, and can be removed safely.

Thanks for your attention to detail.


Added my profile

I have added my github profile

@jindalabhishek1  thnx for contributing, try this year, and make sure you follow me and star this repo for updates about special swags I will be giving.
Contribute in October for Hacktoberfest 2020


Having trouble making the plugin work

Hello there. I'm having trouble making the plugin work.
I'm getting this error on the terminal:
TemplateWriterWriteError was thrown

ENOENT: no such file or directory, stat '/images/uploads/meBio.png'

The path exists and it's correct, so I don't get the error. I'm a self taught programmer and sometimes is very hard to understand why things don't work. (the project does not have a "src" folder)
Thank you for your time.
The code:
const img2picture = require("eleventy-plugin-img2picture");
module.exports:
cfg.addPlugin(img2picture, {

  eleventyInputDir: "//",
  imagesOutputDir: "_site",
  urlPath: "_site/images/",
  extensions: ["jpg", "png", "jpeg"],
  formats: ["webp", "jpeg"],
  sizes: "100vw",
  minWidth: 150, // Minimum width to resize an image to
  maxWidth: 700, // Maximum width to resize an image to
  widthStep: 150, // Width difference between each resized image
  fetchRemote: false, // When true, remote images are fetched, cached and optimized.
  dryRun: false, // When true, the optimized images are not generated. Only HTMLs are processed.

  // Function used by eleventy-img to generate image filenames
  filenameFormat: function (id, src, width, format) {
    const extension = path.extname(src);
    const name = path.basename(src, extension);

    return `${name}-${id}-${width}w.${format}`;
  },

  cacheOptions: {},
  sharpOptions: {},
  sharpWebpOptions: {},
  sharpPngOptions: {},
  sharpJpegOptions: {},
  sharpAvifOptions: {},

});

The problem you are facing looks similar to #7.

Also, you might want to start with mandatory options: eleventyInputDir, imageOutputDir, and urlPath. Once, you make it working you can customise using optional parameters.

It really looks like a folder structure problem.  I'm lost here.
I don't have a "src" folder.
eleventyInputDir: "//", ----> stays empty?
imagesOutputDir: "_site", ----> "_site"
urlPath: "_site/images/", ----> "_site/images/"

Can you try with eleventyInputDir: ".", and remove all options other than  eleventyInputDir, imageOutputDir, and urlPath?

Tried this. Still does not work.
eleventyInputDir: ".",
imagesOutputDir: "",
urlPath: "",

console:
TemplateWriterWriteError was thrown

path is not defined

If you wish I can provide you all the code. If we are able to make this work it could help other people that have the same issue. This plugin seems really good. Not having to use short codes is the best way to go.

I've uploaded the code and opened the git repo.
https://github.com/ornelasnarciso/artornelasnarciso

The problem you are facing looks similar to #7.

@ornelasnarciso Please go through the thread, #7. Both path and eleventyInputDir errors were addressed in that tread. Based on these common problem I have update the Readme.

#7 only shows the text: "No description provided." Nothing else.
Followed the instructions on readme, and the plugin still does no work.
The (Quick Start) will provide empty spaces and no images. For some reason the plugin only applies changes to images on markdown files. All the others are not affected.
const img2picture = require("eleventy-plugin-img2picture");
module.exports = function (eleventyConfig) {
eleventyConfig.addPlugin(img2picture, {
eleventyInputDir: ".",
imagesOutputDir: "_site",
urlPath: "",
});
};
The advanced option makes no changes and provides no errors on the console. Is it correct to write  "development" ( if (process.env.ELEVENTY_ENV === "development") {)? I assumed it has to be this way since there's no instructions about it.
const img2picture = require("eleventy-plugin-img2picture");
const path = require("path");
const img2pictureOptions = {
eleventyInputDir: ".",
imagesOutputDir: "_site",
urlPath: "",
extensions: ["jpg", "png", "jpeg"],
formats: ["avif", "webp", "jpeg"],
sizes: "100vw",
minWidth: 150,
maxWidth: 1500,
widthStep: 150,
fetchRemote: false,
dryRun: false,
filenameFormat: function (id, src, width, format) {
const extension = path.extname(src);
const name = path.basename(src, extension);
return ${name}-${id}-${width}w.${format};
},
cacheOptions: {},
sharpOptions: {},
sharpWebpOptions: {},
sharpPngOptions: {},
sharpJpegOptions: {},
sharpAvifOptions: {},
};
/============== module.exports
if (process.env.ELEVENTY_ENV === "development") {
cfg.addPlugin(img2picture,);
} else {
cfg.addPassthroughCopy("./images");
}

With quick start example, try with these settings:
{
  eleventyInputDir: ".",
  imagesOutputDir: "_site/images/",
  urlPath: "/images/"
}

imagesOutputDir tells where to copy the optimised images, and urlPath will be used to generate src in <img> tag. So, urlPath should match the path used in imagesOutDir when serving. Example, with  urlPath: "/images/", within <picture> you will have <img src="/images/<filename>.jgp" />

Now it's working with that quick start. :)
And how should i proceed to use the advanced? I want to control de image sizes.
And sorry for taking your time.
Thank you for the help.

Great! Glad to know it worked. You should be able to use all options other than dryRun and filenameFormat without any issues.

dryRun only for testing, it don't generate any image files.
filenameFormat, you need to write a function to generated filenames

This is the best plugin for images on eleventy.
Thank you very much for your time and help. :)

Me again.
Everything is working fine but i totally forgot about the images that are passed on the css something like => background-image: url("imageFile.png");.
It's obvious they don't have the "img" attribute so the plugin doesn't know they exist. Is there any way to make the plugin work with images called from the css?
Thank you.

No. This plugin only optimises images in HTML files referenced with <img> tags.

OK. Thank you. :)


Question: Release strategy

Hi everyone,
I'm just wondering what is an release strategy for this project? Is there any cycle set, or it's kind of free? :)
Seems like there are some merges to master alraedy, plenty of PRs approved, some even merged.
Thank you.

I wonder about that too. Is there a plan for PHP 8.2?

Seems like maintainers are gone. What about to pick some new ones? Or do we have to create another fork? @Shardj ?
Too many forks will kill the initiative and seems, that here is plenty of contributors.

@develart-projects sure, I'm happy to give people repo permissions if anyone wants to volunteer as a maintainer. I haven't worked on a project that uses this codebase in almost 2 years now so it fell out of interest for me.
Do tag me in replies, that way I actually get a notification. I don't really look at my GitHub very much currently.

@Shardj we still have plenty of projects active, so I'm happy to spent some time on this. At least we have already some work done in the PRs waiting just for acceptance and new release, thanks.

@develart-projects alright, added you as a contributor. There are three other contributors as well but it seems they've all stopped looking at this repo too. However I know @kaktusas2598 still works on a project that uses this repo so if you aren't sure on a PR maybe check in with him, or tag me and I'll hopefully see it
To answer the original question, release strat was just whenever. Feel free to make one yourself, here's the most recent release commit if you want to see the files I change. I started the changelog.md because it was requested but it's pretty much just copied and pasted PR titles. After changing the files I just make a new tag for the new versions semvar in the format of "version-#.#.#" and then release on that tag.

Thanks for the continuous support. Releasing new versions please update also \library\Zend\Version.php content.

@krzyko thanks for the reminder, will try to not forget :)

Good work guys. I am also using this in a big project and I'm happy this is maintained.
Will try to contribute once we start working to get this running on PHP 8.2


Un-terminated markup codes like  cause issues

This markup was copied from an EEx template into a ~H one.

The problem is the
. The compiler error is:
** (Surface.Translator.Parser.ParseError) /my_app/views/editor/placeholder.ex:14: expected end of string
    (surface) lib/surface/translator/parser.ex:222: Surface.Translator.Parser.parse/3
    (surface) lib/surface/translator.ex:23: Surface.Translator.run/4
    (surface) expanding macro: Surface.sigil_H/2
    (fe_web) lib/fe_web/views/editor/placeholder.ex:13: FeWeb.Editor.Placeholder.render/1
    (elixir) lib/kernel/parallel_compiler.ex:229: anonymous fn/4 in Kernel.ParallelCompiler.spawn_workers/7

After trial and error I realized it was the
. When I changed it to
 then it worked fine.
The solution is either support markup like the non-xml valid
 or improve the error message to help identify what the problem is.

Improving the error message is the way to go. There's a new parser that still has to be merged that address this by giving the following message:
.../placeholder.ex:18: expected closing tag for "
"

Perfect!

@brainlid the new parser on master accepts HTML void elements like
 or
. No need to self-close them anymore. You can copy and paste them freely now ;)

@brainlid BTW, with the new parser you'll have to make a small change in you <Form> component. Please use:
<#Raw></form></#Raw>

instead of:
{{ raw("</form>") }}


Device Timestamp is always Center of Exposure

Fixes https://github.com/microsoft/Azure-Kinect-Sensor-SDK/issues/1107
Remove comments about device timestamp being start of exposure

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

#sign-off

#sign-off


Don't lint .go files below /testdata/ [phab:D1218]

Created by shahms at 2017-01-05 16:55:16:

fromberger wrote at 2017-01-05 17:10:40:
Thanks! I had made a note to look into this, but you beat me to it. :)

fromberger accepted this revision at 2017-01-05 17:10:40

shahms closed via commit 171b8c3f9e2c12a56e8d845ea6da6caf2b76e37c at 2017-01-05 17:19:23


Update Hue Bridge blocks use

 is a comment.
You will see these throughout the issue template. Make sure you do not type your comments
between these characters or we will not be able to see what you wrote!

4. Links
To create a hyperlink, type the [text you want to link](followed by the url in parenthesis)
-->
Describe the bug
After a fresh install of Emulated Hue on Home Assistant (2022.4.7) I tried to connect the Hue app on the iPhone - app v4.16.1 (10083)-
It finds the Home Assistant emulated bridge, the bridge connects but the Hue iOS app then shows an update screen.
"There is a mandatory update available for your Hue Bridge.  You can use your system again after the update"
The only option is to switch back to the hardware Hue Bridge.
Steps to Reproduce

Install Emulated HUE on Home Assistant
On HUE app, search for bridge
On HomeAssistant enable link mode
Return to HUE app, shows "Connected to your Hue Bridge" - click continue
At this point it shows the blocking "Update Hue Bridge" screen

Tried uninstalling both Emulated Hue and the Hue app on iOS and reinstalling.  There's no getting round the update screen.
Expected behavior
Not to prompt me on the phone to update the bridge.  There's no way to use the bridge until the update is done, which of course can't happen.
Logs
[13:52:14] INFO: Starting Emulated Hue...
2022-04-28 13:52:15,786 INFO  emulated_hue.config -- Auto detected listen IP address is <IP_ADDRESS>
2022-04-28 13:52:15,875 INFO  hass_client -- Connected to Home Assistant ws (version 2022.4.7)
2022-04-28 13:52:16,050 INFO  emulated_hue.api -- Started HTTP webserver on port 80
2022-04-28 13:52:16,098 INFO  emulated_hue.api -- Started HTTPS webserver on port 443
2022-04-28 13:52:37,150 INFO  emulated_hue.config -- Link request detected - Use the Homeassistant frontend to confirm this link request.
2022-04-28 13:52:42,447 INFO  emulated_hue.config -- Link mode is enabled for the next 5 minutes.
2022-04-28 13:52:43,248 INFO  emulated_hue.api -- Client Hue#My iPhone registered

Hardware Info:

Architecture (Ex: x86, ARM): x86
Addon version (Ex: stable or dev): 0.2.13 stable

Value of "tag_commit_or_branch" if using dev:

OS (Ex: Windows 10, Ubuntu Buster): HAOS
Hardware (Ex: PC, Raspberry Pi 1/2/3/Zero): HP T630 Thin Client

Additional context

Ah I saw the other replies on other issues about the v2 Api after I posted this.

Can I get a link to the fix for this?


Postgres SKIP LOCKED

Is your feature request related to a problem? Please describe.
Skip locked is super useful for things like job queues. Looks like you can use it with Knex directly, but I don't want to lose the ability to use other mikro-orm features.
Describe the solution you'd like
Either a new lock mode, similar to TypeORM pessimistic_partial_write. AFAIK it should just need to set skipLocked on the Knex query builder along with the forUpdate
Or another option for skip locked.
Describe alternatives you've considered
Get the knex instance and use transactions manually (this is what I'm doing now, but I lose quite a bit of type safety)
Additional context
Add any other context about the feature request here.

I'd also cover other cases too, looks like there are 4 (combination of for share/update and skip lock/nowait). Not sure about the naming, it looks like typeorm uses pessimistic_partial_write and pessimistic_write_or_fail, but I haven't seen other ORMs or tools with similar naming. Do you think it makes sense to call the for share variants as partial_read and read_or_fail? Do you know other tools that are abstracting this? What naming do they use?
We can also allow passing the table names via query builder.

I think adding them to the current lock modes makes sense since you can't use skip locked or nowait without for share/update. I think knex actually throws an error if you add .skipLocked() without first doing .forUpdate() or .forShare(). So that should reduce the number of errors someone could get. It would just need to be documented well what each option does to the query, that's the only issue I had with TypeORM doing that. It was hard to tell what each option did.
Being able to specify the locked tables though is super important, especially for joins, otherwise you are locking every table that get's joined (even if you don't plan to update the other tables). So the query builder could have a second optional parameter for an array of tables/aliases to provide. And it would be great if it could be added to the Find/FindOne options as well, maybe as lockTables.

Do you think we should allow this also for em.find()? Currently EM supports lock modes only on em.findOne(), but it feels like really artificial limitation, I guess I forgot to add it to the right place in the early days and nobody complaint :]

If there's no reason it can't be, then yeah. I'm currently having to use query builder because find doesn't support lock modes. Would there need to be two enums then to not allow optimistic on find()? Or would the type just be a union of the supported types for each?
Also I went ahead and made a patch for my project's use case to avoid having to use knex directly. Not sure if this will help implement it, but it's working for me currently. I had to add a check for the method because I noticed that the lock modes were being called when update queries take place and skip locked throws errors with update.
@mikro-orm+core+4.5.4.patch
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index c4ede3d..f97a83a 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -78,7 +78,8 @@ export declare enum LockMode {
     NONE = 0,
     OPTIMISTIC = 1,
     PESSIMISTIC_READ = 2,
-    PESSIMISTIC_WRITE = 3
+    PESSIMISTIC_WRITE = 3,
+    PESSIMISTIC_PARTIAL_WRITE = 4
 }
 export declare enum EventType {
     onInit = "onInit",
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index 89eb4a1..574d98d 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -83,6 +83,7 @@ var LockMode;
     LockMode[LockMode["OPTIMISTIC"] = 1] = "OPTIMISTIC";
     LockMode[LockMode["PESSIMISTIC_READ"] = 2] = "PESSIMISTIC_READ";
     LockMode[LockMode["PESSIMISTIC_WRITE"] = 3] = "PESSIMISTIC_WRITE";
+    LockMode[LockMode["PESSIMISTIC_WRITE"] = 4] = "PESSIMISTIC_PARTIAL_WRITE";
 })(LockMode = exports.LockMode || (exports.LockMode = {}));
 var EventType;
 (function (EventType) {

@mikro-orm+knex+4.5.4.patch
diff --git<EMAIL_ADDRESS><EMAIL_ADDRESS>index f22bf10..5fc9afb 100644
---<EMAIL_ADDRESS>+++<EMAIL_ADDRESS>@@ -373,6 +373,9 @@ class QueryBuilderHelper {
         if (lockMode === core_1.LockMode.PESSIMISTIC_WRITE) {
             return void qb.forUpdate();
         }
+        if (qb._method === 'select' && lockMode === core_1.LockMode.PESSIMISTIC_PARTIAL_WRITE) {
+            return void qb.forUpdate().skipLocked();
+        }
         const meta = this.metadata.find(this.entityName);
         if (lockMode === core_1.LockMode.OPTIMISTIC && meta && !meta.versionProperty) {
             throw core_1.OptimisticLockError.lockFailed(this.entityName);

Also I'm willing to open a PR for this, I just won't be able to start on it until next week

No worries, I am already 90% there, just making some adjustments in the EM API as described above :]

Would there need to be two enums then to not allow optimistic on find()? Or would the type just be a union of the supported types for each?

We can do lockMode: Exclude<LockMode, LockMode.OPTIMISTIC>.

Awesome, looking forward to it 🎉  Thanks!

There is one gotcha with the lockTables, as you need to specify aliases, not table names. Will try to swap the table names if there is an alias automatically, I guess it should be safe.

Right, would that work if someone overrides the alias in the query builder?

Mmmm maybe it will be better to keep it up to the user, as the inference based on table/entity names wouldn't be really precise. There can be multiple joins to the same table, and we might want to lock only the root entity (and root entity always has alias e0).

That sounds good, could add a small warning to the docs about that so users are aware that they should probably add an alias for the table and then use that in the option (or use e0 for the table). Should the option be called lockAliases then?


Fixing pattern configuration mistakes?

How would you edit/remove mistakes made when configuring a pattern?
For example:

Edit/remove CodeTemplate
Edit/remove attribute
Edit/remove element/collection
Change element to collection and visa versa
Edit/remove Command
Edit/remove LaunchPoint

Edit/remove attribute - edit update-attribute Name (same options as edit add-attribute) and edit delete-attribute Name
Edit/remove element/collection  - edit update-element Name (same options as edit add-element) and edit delete-element Name

Other cases in similar vein


Doesn't work with alternative language keyboards.

Expected behavior
I would expect combos to activate automatically and correctly.
Actual behavior
I type my keyword, instead of replacing the keyword with my snippet text the keyword dissapears and my keyboard "locks up". I can't type anything. To "unlock" the keyboard I need to press ALT and CTRL both once individually.
Steps to reproduce the behavior
Set keyboard language to French and try to use a combo.
Operating system
Windows 10 1909

Hi.
I have a VM of Windows 10 in French, w/ French keyboard layout, and it works just fine. However It's an older release. I will update it to 1909 and retry.

I am using a german keyboard layout without problems. (except https://github.com/xmichelo/Beeftext/issues/223)
And I rarely use Beeftext. But it is running in the background all the time and worked fine for the last year or two.
WIndows 10 64bit 1909

This looks like #300. @pifiuk is the last character of your combo keyword using AltGr (like one of #{[|\@]}) ?


python311Packages.google-cloud-container: 2.21.0 -> 2.22.0

Changelog: https://github.com/googleapis/python-container/blob/v2.22.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 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

[ ] Fits CONTRIBUTING.md.

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

4 packages built:

python310Packages.google-cloud-container
python310Packages.google-cloud-container.dist
python311Packages.google-cloud-container
python311Packages.google-cloud-container.dist


[WFLY-17107] Upgrade Undertow legacy to 2.2.20.Final

Signed-off-by: Flavia Rainone<EMAIL_ADDRESS>Jira: https://issues.redhat.com/browse/WFLY-17107
    Release Notes - Undertow - Version 2.2.20.Final

        Bug

[UNDERTOW-2109] -         The large file is in unexpected location on JDK17

[UNDERTOW-2140] -         SSLSessionInfo.calculateKeySize(String cipherSuite) doesn't account for all cipher suits

[UNDERTOW-2142] -         ChunkedStreamSinkConduit write with a buffer array writes too few buffers

[UNDERTOW-2147] -         race condition between session invalidate and  changeSessionId leads to UT000010

[UNDERTOW-2159] -         InMemorySessionManager#getSession - null check inconsistency

        Enhancement

[UNDERTOW-2145] -         UndertowOutputStream and ServletOutputStreamImpl awaitWritable unnecessarily

Thanks @fl4via


completion: use separate kind for Cody completions

Sorry, for some reason it wasn't allowing me to push updates on the original PR in #144
(you should still get the credit for your commit though!)

Thanks @Pandoks ! Good call on creating separate kind


Need a warning message in UI when upgrade GKE k8s version

Version: Master 2.2 (3/18/19)
Related: #18976
What kind of request is this (question/bug/enhancement/feature request):
Bug
Steps to reproduce (least amount of steps as possible):

Upgrade GKE k8s version
Notice this only affects the master k8s version, and does not upgrade the nodes

Result:
We should add a warning message in the UI in this case when editing to upgrade k8s version.
(And if it's not too difficult could we make the warning only show when we specifically choose newer version of K8s from dropdown? (UI compares current versus picked to make this determination? if is different then show message?)) otherwise if its not easy always show it.
I would like to suggest something like this in typical yellow warning box in the approximate area of k8s version drop down:

When you upgrade the Kubernetes version with GKE only the master version will be upgraded. If you would like to upgrade the nodes as well you will need to do this manually via the Google Cloud Platform.

Other details that may be helpful:
Related: #18976 and #18966

Version: Master 2.2 (3/19/19) ImageID:
Confirmed issue. If and only if you are upgrading to a newer K8s version (cluster is older version, and then you manually pick a newer version from drop-down on edit) THEN you will get this message:

I tested with several versions and smoke tested this area. Happens regardless if upgraded from older rancher or on a fresh install of latest master, as expected.


The last GitHub Actions build failed

https://github.com/Hagb/docker-easyconnect/runs/7820173979?check_suite_focus=true
Would you pls rerun this action? Thx!

Also, local build failed. A workaround would be download manually the deb file.

Thanks for reminding! I have successfully rerun the action. The problem seems temporary.


Try to define buttons backgroundImage to gradient, but failed

@coloredBakcgroundImage: none;
@primaryBackgroundImage: @coloredBackgroundImage;
@secondaryBackgroundImage: @coloredBakcgroundImage;
@positiveBackgroundImage: @coloredBackgroundImage;
This is in the button.variables.
When I try to define:
@primaryBackgroundImage: linear-gradient(lighten(@primaryColor, 30%), @primaryColor 60%, darken(@primaryColor, 40%));
It does nothing,
I have to change the @coloredBackgroundImage to change the button's background. But if I do that, all different buttons have the same backgroundImage.
What's the problem here? Can anyone help?

What files are you declaring this in?

src/themes/default/elements/button.variables
Thanks for response!
I have found the problem, I need to write some button.overrides to redefine the buttons CSS, otherwise any definitions in the button.variables would not take effect.


Proper model directory structure

I found no mention in the docs about the proper way to structure models in a Flask app. Right now I have this:
# app.py
db = SQLAlchemy(app)

and:
# models.py
from app import db
class MyModel(db.Model):
# ...

But this means I have a circular dependency once I try to do:
# app.py
from models import MyModel

It's worth mentioning how this should be done in the docs.

This isn't a Flask-SQLAlchemy issue per se, it largely depends of the structure of your app.
There's plenty of guides which outline various different ways of structuring a Flask app which includes Flask-SQLAlchemy.


await generates invalid state machine that never completes for System.Net.Http.HttpClient

Tested versions
v4.2.1.stable.mono.official [b09f793f5], v4.2.2.stable.mono.official [15073afe3]
System information
Godot v4.2.2.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4090 (NVIDIA; <IP_ADDRESS>61) - AMD Ryzen 9 5950X 16-Core Processor (32 Threads)
Issue description
await generates an invalid state machine that never completes for System.Net.Http.HttpClient
awaiting using .Wait() works as intended.
This is an issue with third-party libraries that use System HttpClient instead of Godot's HttpClient.
Steps to reproduce
Create a new C# project
Import the code below and run with debugger on (see gif below for execution results)
using System.Threading.Tasks;
using Godot;

public partial class TestScript : Node
{
    private System.Net.Http.HttpClient _httpClient = new System.Net.Http.HttpClient();

    public override void _Ready()
    {
        Works();
        Hangs().Wait();
        base._Ready();
    }

    public void Works()
    {
        var task = _httpClient.GetAsync("https://www.google.com");
        task.Wait();
        var google = task.Result;
        var contentTask = google.Content.ReadAsStringAsync();
        contentTask.Wait();
        var googleContent = contentTask.Result;
        GD.Print(googleContent);
    }

    public async Task Hangs()
    {
        var google = await _httpClient.GetAsync("https://www.google.com");
        var googleContent = await google.Content.ReadAsStringAsync();
        GD.Print(googleContent);
    }
}

Minimal reproduction project (MRP)
demo.zip

Task.Wait blocks the calling thread which will cause a deadlock here because await expressions in Godot use a custom GodotSynchronizationContext that queues the continuation on Godot's main thread. This means that await continuations are waiting in a queue until Godot invokes them, but Godot is blocked because you called Task.Wait.
In general, you have to be careful when using Task.Wait or Task.Result. It's preferable to use await instead. And try to avoid blocking on engine callbacks (such as _Ready or _Process).
A possible solution to your deadlock could be to avoid GodotSynchronizationContext or using Task.ConfigureAwait(false). That way you avoid blocking the Godot main thread and the queued continuations can be invoked.
// Use Task.Run to avoid using GodotSynchronizationContext.
Task.Run(() => Hang()).Wait();

// Alternatively, use Task.ConfigureAwait(false) to indicate that
// the continuation doesn't go back to the original context.
var google = await _httpClient.GetAsync("https://www.google.com").ConfigureAwait(false);

Hard to say what to do about it, but it's definitely a noob trap.
In my case, the _Ready blocking call was okay because I had a lot of processing to do at that step. But it would be nice to have some more information on the deadlock.
pseudo code solution?
if in DEBUG
register this new task at GodotSynchronizationContext
see that `_Process` is hung for some time and we didn't update for some time (5-10seconds?)
throw an exception and abort the Task/Thread
configurable via settings `GD.GodotSynchronizationContextDebugTimeout(Timespan.Infinity);`

Maybe it's more a matter of adding this to docs, rather then fixing the underlying issue as I guess it might be though.


[Feature Request] Local playlists through m3u

Right now, the only way to get Nadeko to play local files in succession is to play a whole folder.
Would it be possible to add support for the m3u format so people can make playlists instead of moving files around for different playlists?
Thanks so much for your fantastic work!

make a m3u, then upload it somewhere and get a direct link to it, then use !!ra link-to-m3u to queue it.


read openai key from standard environment variable

~> $env.OPENAI_API_KEY                                                                                01/30/24 23:44:06 PM

Dup https://github.com/dustinblackman/oatmeal/issues/8


Help Implementing FIPS Level 1 Requirements #4

I was looking at the Level 1 Specific Requirements in README_FIPS.md and was stuck on how #4: Run integrity selftest at power on for SW component would be implemented. I was wondering if there were any good resources on implementing this? (Would it be just as simple as flashing a UEFI on my board, what I/O and components should be checked in the self-test, etc) Thanks a lot!

In the Intel Cryptography Library, integrity self-test is an important step to ensure that the cryptographic module has not been tampered with or damaged at startup. This self-test is often used to comply with the requirements of the FIPS (Federal Information Processing Standards) 140 series1.
When implementing this self-test, a specific API function is usually called at system startup to perform the self-test. For example, the Intel® Cryptography Primitives Library provides the fips_selftest_ippcp API to run the self-test1. The user's application should call these self-test functions before using the algorithm for the first time. see Example


Meetups

What's up with the Travis checks? I see that this actually passed, but it shows as failed.