Base table or view already exists

When I run
php artisan voyager:install --with-dummy
I get this error:
Base table or view already exists
C:\project\Doctrine\DBAL\Driver\PDOException::("SQLSTATE[42S01]: Base table or view already exists: 1050 La table 'users' existe déjà")
I guess that "users" table is already reserved by laravel !

@already already done!

Voyager doesn't provide a migration to create a users table.  It simply relies on the default Laravel one to run.  Once you figure out where the extra users table creation is coming from, you should be able to re-run the voyager:install command.
If you have further questions or need help getting past this, please ask in our Slack group.


whois <IP_ADDRESS> reveals a russian server

Hi
In the DNSchoices of install.sh, the address <IP_ADDRESS> ("::: Using DNS.WATCH servers.") points to:
netname:        ZSTTK-NET
descr:          JSC "Zap-SibTranstelecom"
descr:          Komsomolqskijj Avenue, 1/4
descr:          630004, Novosibirsk
whereas the dns.watch services are provided by the german company IAMONSYS GMBH.
I do not feel comfortable with that!

Well, then don't use that DNS service I guess? You are able to choose what DNS server you want to use. (unless you mean we got the IP wrong, in which case you can submit a PR or leave a comment)

It is their server, it is not wrong.
https://dns.watch/index#ips
You should not feel uncomfortable with it, but if you are, that is why there are a ton of choices there.

@0-kaladin : Sorry but in your link https://dns.watch/index#ips the server address is <IP_ADDRESS> and not <IP_ADDRESS>. You may have a mistype error in install.sh.

Since this is a security issue, I thought it had higher priority and immediately fixed it. I also checked the other IPs of the DNS servers, and the seem to be correct.

Thanks @redfast00


Remove unused errors

Part of #43
Remove values from Errors enum which are no longer required, and move QueryViewOperation to using .HTTP error.
reviewer: @brynh

+1


Seaport 1.3

This PR highlights changes from Seaport 1.2 to Seaport 1.3 and is meant to facilitate review and discussion of those changes.

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (2560c03) compared to base (001a347).
Patch coverage: 100.00% of modified lines in pull request are covered.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@              Coverage Diff              @@
##           seaport-1.2      #990   +/-   ##
=============================================
  Coverage       100.00%   100.00%
=============================================
  Files               47        46    -1
  Lines             2661      2649   -12
  Branches           393       394    +1
=============================================
- Hits              2661      2649   -12

Flag
Coverage Δ

foundry
77.91% <81.25%> (+0.10%)
:arrow_up:

production
100.00% <100.00%> (ø)

reference
100.00% <100.00%> (ø)

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

Impacted Files
Coverage Δ

contracts/Seaport.sol
100.00% <ø> (ø)

contracts/lib/Consideration.sol
100.00% <ø> (ø)

contracts/lib/ConsiderationDecoder.sol
100.00% <ø> (ø)

contracts/lib/LowLevelHelpers.sol
100.00% <ø> (ø)

reference/ReferenceConsideration.sol
100.00% <ø> (ø)

contracts/lib/ConsiderationBase.sol
100.00% <100.00%> (ø)

contracts/lib/FulfillmentApplier.sol
100.00% <100.00%> (ø)

contracts/lib/OrderCombiner.sol
100.00% <100.00%> (ø)

contracts/lib/Verifiers.sol
100.00% <100.00%> (ø)

reference/lib/ReferenceConsiderationBase.sol
100.00% <100.00%> (ø)

... and 3 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


order: container with max-width priority

windicss

tailwind

Then I think I will take out the container separately and not merge it with the following. The container is indeed a bit special.

but medias overwrite max-w

and tw example https://play.tailwindcss.com/FN8mw3RU4F

сс @voorjaar

It happens to me with all responsive styles:
e.g.
flex justify-between sm:justify-end
I would expect, that sm:justify-end is active from sm upwards, but justify-between somehow has a higher priority

Can you test again? just tested it. It's seem right...


Fix partial inquiry overview

All links are overwritten in each Listing-page pointing to inquiry (e.g. Contact, Delete, etc. point to Inquiry action with Id).

Fixed in PR #128. Closing issue.


[wip] feat: update Radio component to Diete v5

You're right, I will update the design. Standalon radio makes no sense :)

OK so we wait for the new design.

The design is done, ready in diete05

One side effect in the current store design is, that changing focus also changes the value. If this ever is a problem, we can change it similarly to how this is done in select.


Add map.shouldHaveSize assertion

I don't believe we have this currently.

Should not we close it yet? :)

Sure thing!
I suggest closing issues when commiting https://help.github.com/en/articles/closing-issues-using-keywords

Sure thing!
I suggest closing issues when commiting https://help.github.com/en/articles/closing-issues-using-keywords

Ok. Did not know. Thank you!


Add missing anchor bracket in README.md

thanks

Coverage remained the same at 100.0% when pulling b71c61ba71fdc819e8a6fd79f1871a5aee89a98c on matiassingers:patch-1 into 6fac3967aa6f0d16620c44a3043daf113e900d74 on jonathanong:master.


The representation of simple expressions was surrounded by redundant parenthesis eg. (1=1)

This commit removes the outer most parenthesis of expressions.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@863997c). Click here to learn what that means.
The diff coverage is 81.25%.

@@            Coverage Diff            @@
##             master    #6168   +/-   ##
=========================================
  Coverage          ?   83.17%
  Complexity        ?    12528
=========================================
  Files             ?     1452
  Lines             ?    47441
  Branches          ?     5826
=========================================
  Hits              ?    39459
  Misses            ?     5276
  Partials          ?     2706

Impacted Files
Coverage Δ
Complexity Δ

...analyze/expressions/ExpressionToStringVisitor.java
68.75% <0%> (ø)
10 <0> (?)

.../crate/analyze/expressions/ExpressionAnalyzer.java
91.52% <100%> (ø)
27 <0> (?)

...er/src/main/java/io/crate/sql/tree/Expression.java
66.66% <100%> (ø)
2 <1> (?)

...arser/src/main/java/io/crate/sql/SqlFormatter.java
87.75% <100%> (ø)
7 <0> (?)

...rc/main/java/io/crate/sql/ExpressionFormatter.java
80.52% <75%> (ø)
4 <2> (?)

Continue to review full report at Codecov.

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


Error "mocha.run() was called with no tests" (under Windows)

Can not run tests via npm test:
PS C:\inetpub\wwwroot\ol3> npm test

><EMAIL_ADDRESS>pretest C:\inetpub\wwwroot\ol3
> eslint tasks test test_rendering src examples

C:\inetpub\wwwroot\ol3\test_rendering\test.js
  26:6  error  Missing semicolon  semi

? 1 problem (1 error, 0 warnings)

npm ERR! Test failed.  See above for more details.

Ok. Inserted necessary semicolon.
And...
PS C:\inetpub\wwwroot\ol3> npm test

><EMAIL_ADDRESS>pretest C:\inetpub\wwwroot\ol3
> eslint tasks test test_rendering src examples

><EMAIL_ADDRESS>test C:\inetpub\wwwroot\ol3
> node tasks/test.js

mocha.run() was called with no tests
npm ERR! Test failed.  See above for more details.

How can I run tests ? Please help.

Can you try with make test?

I have windows machine and this command was not recognized as an internal or external. Shoud I install something in addition to npm install ?

Building on Windows might help.

install Cygwin (make + nano)

edit Cygwin's /etc/fstab file to disable ACLs like this none /cygdrive cygdrive binary,noacl,posix=0,user 0 0

run make

PS C:\inetpub\wwwroot\ol3> make test
Не найден файл: *.glsl
Не найден файл: *.js
Не найден файл: *.js
Не найден файл: *.js
FIND: Неправильный формат параметра
Не найден файл: *.html
Не найден файл: *.js
FIND: Неправильный формат параметра
npm install
\
><EMAIL_ADDRESS>install C:\inetpub\wwwroot\ol3
> node tasks/install.js

><EMAIL_ADDRESS>postinstall C:\inetpub\wwwroot\ol3
> closure-util update

<EMAIL_ADDRESS>node_modules\coveralls
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>└──<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>cas
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>1<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>http-
<EMAIL_ADDRESS><EMAIL_ADDRESS>node tasks/test.js
mocha.run() was called with no tests
make: *** [Makefile:136: test] Error 1

Second attempt:
$ cd C:/inetpub/wwwroot/ol3

T1nK@megaubivashka /cygdrive/c/inetpub/wwwroot/ol3
$ make test
node tasks/test.js
mocha.run() was called with no tests
make: *** [Makefile:136: test] Ошибка 1

Sorry, I am not using Windows myself. Maybe someone else has an idea.

It was possible to run the test 3.17.1 under ubuntu. Head does not start.

@cpsTinK have you figured out how to solve this? I got the similar issue under Windows. can't use "make" command. maybe there should be a way for Windows environment.

Closing due to lack of activity.


Fix root calculation for quadratic polys without linear term

An unchecked signum multiplication in analysis.function.polynomial.root.QuadraticRoot causes the solver to always report a double root at 0 whenever the linear coefficient of a quadratic polynomial is 0. This PR adds a guard to ensure that the correct roots are returned.

Thanks for the submission.  I took this PR and made a fix that is more simple for the next dev reading this to understand.
https://github.com/deephaven/SuanShu/pull/7


Mod changelogs are unavailable until the mod is updated

Geode Issue

[X] I confirm that this bug is NOT related to a mod but directly to Geode Loader itself.

Platform
Android64
SDK commit
No response
Geode Version
v3.7.1
Mods Installed
Irrelevant
Expected Behavior
The purpose of changelogs are to see the changes associated with updating mods. Forcing the player to update before the changelogs can be viewed makes this complicated and makes determining whether you want to update a mod difficult.
I would expect the changelogs for all released versions, including those ahead of the installed version, of the installed mod to be available in the GUI, and perhaps an icon indicating which version you are currently on.
Actual Behavior
Only the changelog up until the installed version is available
Steps to Reproduce

Install any mod
Wait for an update to be available (or install a version of the mod that is not the latest version)
Check the changelogs and notice the changelog for the update is unavailable.

Additional Information
Sorry if this is incorrectly labelled as a bug report; it feels like a bug to me.

Yeah that's very annoying
You could've posted this in the discussions section so it doesn't appear in the issues section

Yeah that's very annoying You could've posted this in the discussions section so it doesn't appear in the issues section

this is an issue.

I always found this annoying but thought it was intentional. New I'm thinking why would it be intentional in the first place

I agree. I never remember what mods I've updated after restarting so I never check the changelog.

I always check where the my mods will appear in the Newest tab with the latest updated filter toggled. But would be more helpful to have this or have the filters also available in tab with the mods we have


WIP: fetchThreadImages or feature request

Description
I wanted to create a way of downloading all images posted sent in given thread.
Research
I stareted by watching network traffic on messenger.com while scrolling down the image history.
First query looked like this:
https://www.messenger.com/webgraphql/query/?query_id=515216185516880&variables={"id":"<uid>","first":"<number>"}.Where uid is specified user and number is how many to download, default is 12. Facebook will do more, but I am kinda scared.
If you scroll down further, it shows more and more history.
Query now looks like this:
https://www.messenger.com/webgraphql/query/?query_id=515216185516880&variables={"id":"<uid>","after":"<image_id>","first":<number>}. Previous variables are the same, but there is new thing called after, after digging around some more I found out that image_id is special variable for starting query after given image. It is called coursor in JSON.
After POST'ing it, it returns almost readable JSON, it begins with "for (;;);".
My development
I forked it and created my own crude function to handle it. I'll keep working on it.

Hi there @krzesu0, thanks for the research!
I've previously investigated Facebook's GraphQL endpoints quite extensively, and i know that the endpoint at /webgraphql/query works similarly to the one at /api/graphqlbatch/, which we've previously implemented support for, see Client.graphql_request. So I'd suggest using that, something like this should get you far:
data = {"id": <thread_id>, "first": 12}
j = self.graphql_request(_graphql.from_query_id("515216185516880", data))

Note: This internal API was changed recently in #439, so remember to update from master before implementing this!
When you want to parse the result, please make a helper @classmethod on the _file.ImageAttachment class, and convert the result to ImageAttachment objects.
Regarding the cursors, then I think it'd be nice if we could hide them as an implementation detail, and just return an iterable, then the user can choose how many results they want from there?

When you want to parse the result, please make a helper @classmethod on the _file.ImageAttachment class, and convert the result to ImageAttachment objects.
Regarding the cursors, then I think it'd be nice if we could hide them as an implementation detail, and just return an iterable, then the user can choose how many results they want from there?

I rewrote this as @madsmtm suggested. I decided to hide cursor from user . Both _fetchImages (helper) and fetchThreadImages are now generator objects.

I don't think this feature will work for thread videos, It returns only the preview URL and ID's. It uses these ID's to download it from /mercury/attachments/video/?video_id=.... This could be another feature I'll work on.


[RFC ] Backward compatibility discussion for Parquet format support

Background
We are currently working on merging parquet support to release-3-1-0 branch. The origin PR is #874 (based on v2) which has been reworked in #1115 and based on release-3-1-0 branch. The discussion here will  be focus on PR #1115.
During the testing in staging environment, I realize that we should have backward compatibility to support both JSON and Parquet data format. Because an Athena table will only be able to load one type of data, either JSON and Parquet. Once we flip the switch to change the data to Parquet format, the existing data in JSON format will have to either move to another database/tables, or to  be converted to parquet format. I would like to dump my brain here and share with all contributors. Would love to hear your ideas as well.
Description
Backward Compatibility

A new setting data_format will be added to conf/lambda.json under athena_partition_refresh_config. Support format will be json and parquet, default to json. The reason to set json as default value is to minimize the disruption to existing users. I am open to discuss the change of default setting. https://github.com/airbnb/streamalert/blob/2162c64f269afa47710b8adb4d922b2865e179be/conf/lambda.json#L53-L55
So the new configure will look like  "athena_partition_refresh_config": {
    "concurrency_limit": 10,
    "data_format": "json",
    "log_level": "info"
  },

Or  "athena_partition_refresh_config": {
    "concurrency_limit": 10,
    "data_format": "parquet",
    "log_level": "info"
  },

Migrate existing JSON data
If the user choose and upgrade to Parquet format for historical searching, all Athena tables need to be recreated and set data format to parquet. It means the existing JSON data won't be searching from the new tables. We can provide proper approach to migrate existing JSON data.

Option 1: Migrate to new location but still in JSON format
It is possible to provide a script or integrate with StreamAlert cli to create tables in a new database and add partitions by enumerating S3 data buckets.

pros

Cost efficient: it will generate cost related to S3 List, Get and Athena create database, tables and Alter Tables API calls
Fast: It should be fast, because it will only enumerate S3 data bucket and add partitions to Athena tables in new database.

cons

Data is still in JSON format, so the historical searching against these data will be still slow
Increase maintenance burden because we will maintain another database.

Option 2: Convert JSON format to Parquet
Provide a one time script to convert all existing JSON data to parquet and integrate with new data in the same tables.

pros

We will have all historical data in consistent format, Parquet.
All historical data will be searchable in godspeed.
It is possible to use MSCK REPAIR TABLE to load all new partitioned parquet data.

cons

It may cost lots of $$$$ to convert years of historical data if some one have StreamAlert historical searching feature enabled for years. We are not only List and Get objects from S3, but also Put objects to S3 and it is more expensive action.
It will take longer time to finish the conversion.

Not saying this is best but as SA has no official Python3 release yet and the hope is users will do a fresh deploy so this should be considered as a less engineering time option.

Option 3: Drop JSON Support & have users provision a new s3 location for  historic search.
For users who wish to migrate existing data to parquet provide a one time script to convert selected  SON data to parquet and integrate with new data in the same tables.
For users who wish to retain their existing Athena table in JSON no action outside of providing a new bucket is required (We could add a bucket & table suffix to make this automatic & non breaking) so users who do upgrade would just have a second DB table and bucket and then can choose at a later stage to migrate or retain

pros

removes needs to support JSON in the future
Users who wish to migrate historical data to benefit from fast search can opt to if they wish
Users would have two athena DB's one in JSON on in Parquet so they would retain historical search without spending $$$$
This allows users to migrate specific tables of interest vs all.

cons

This is a breaking change.
This would result in an extra S3 bucket being provisioned for the new format.
Historical Data would be split so SQL knowledge would be required for complex queries.

This is done in #1115


added initial content for sites

https://github.com/cloudflare/workers-docs-engine/issues/70

resolved these comments

Lots of progress, thanks.
Still need to address the double spaces after some of the ordered list numbers e.g.2.__ => 2._ (_ means space).

Also some of the indentation is messed up inside the the nested content / code blocks inside the ordered list.
Some places are 3/6, some are 2/4. Please standardize to 2-spaces for tabs.


Balance default mod values

[x] Organ weights
[x] Vat maintenance interval
[x] Vat power consumption
[x] Organ ingredients per organ type
[x] Clone ingredients
[x] Clone growing time

Fixed in the commits below.
Overhaul ingredients and recipe costs: 7a502d7e8dd5be5f1e4b0335918cb52973032fc1
Adjust clone growth time formula: 6c9e92071817b5365af0da1759c6b72a45239132
Increase power consumption for both vats: 81d2e512dfc6382bf09bea862a73cb8fc554b421
Reduce vat maintenance decay rate: c2c370364ec404392da2344616560423d4b39c8f
Balance organ weights: 66844d08a6d70cccb46cda58619d639cbf8fec0d


Lint files

How can we ensure we stay linted and don't have to do a big catch-up again later?

How can we ensure we stay linted and don't have to do a big catch-up again later?

Ah, seeing https://github.com/getsentry/eng-pipes/issues/497 now. 👍


Add the ability to automatically launch the app when the user logs in to the computer

It would be awesome if the app can launch automatically when the user logs in to the computer.
Additionally, adding a preference so the user can choose to enable/disable this feature would be great.

Great article I found to help with this: https://jogendra.dev/implementing-launch-at-login-feature-in-macos-apps
I'm currently reading about it.

@alobaili  I use (MeetingBar)[https://github.com/leits/MeetingBar] everyday at work and I believe we can get cool stuff from it

I tried following the instructions in the article but for some reason it's not working. I tried creating the AutoLauncher target but I don't have a team so maybe it's a problem with code signing when creating the archive. No matter what I do the app won't launch on login.
This package may also be helpful and provide a ready made solution we can use directly: https://github.com/sindresorhus/LaunchAtLogin

@alobaili I believe we can go ahead with ready made solution as the developer is well known also

@alobaili how is things going with you? do u need any help?

I scrapped the first attempt (implement it myself) and didn't have the time to try the LaunchAtLogin package.
I've turned my attention to the issue of fixing dragging an image with watermark included. I'm almost done with it. I'll probably finish tomorrow or the day after.
Feel free to take this one if you have the time.

@alobaili  ok, I will pick this task

I'm done with this task, also tested it and it's working as expected 👍
Thanks for sharing the above package!
Also, I created a signed version so you can install it and try it out! (QRCodeHere)[https://we.tl/t-FH4vsMPIKF]


Re-add @private, undocumented .identifier method that was only me…

…ant for internal framework use but was used by some downstream consumers. This method will be removed in a coming minor release.

@jcoyne @rickychilcott @navidemad mind reviewing this change?


Add support for setting POSIX capabilities on the binary generated by Go

To prevent an application from being swapped to disk, we use mlock (prevents writing private keys to disk).
However, this requires the POSIX CAP_IPC_LOCK capability to be set on the binary file.
This PR adds the option to specify what capabilities to set on the binary file.
NOTE for reviewer:
Would it be possible to get some feedback on whether this feature would be accepted in ko (regardless of the implementation)?

@cpanato Do you have an initial opinion on this PR?

This change looks good! Sorry it's taken so long to review it.
We'll want to regenerate the CLI docs to pass CI, and probably add docs to the website to describe how/why you'd use this. An e2e test that builds and runs ./test with some capability would also help guard against future regressions, but I'll defer to you about how best to test that.
Thanks for this contribution, and sorry again for taking so long to get to it.

Codecov Report

Merging #1098 (603c08c) into main (495411a) will decrease coverage by 1.65%.
The diff coverage is 5.10%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main    #1098      +/-   ##
==========================================
- Coverage   49.19%   47.54%   -1.65%
==========================================
  Files          44       45       +1
  Lines        3653     3786     +133
==========================================
+ Hits         1797     1800       +3
- Misses       1624     1752     +128
- Partials      232      234       +2

Files Changed
Coverage Δ

pkg/build/options.go
61.11% <0.00%> (-3.60%)
:arrow_down:

pkg/build/posixcapability.go
0.00% <0.00%> (ø)

pkg/commands/resolver.go
35.48% <0.00%> (-0.97%)
:arrow_down:

pkg/build/gobuild.go
55.06% <12.19%> (-2.23%)
:arrow_down:

pkg/commands/options/build.go
68.80% <100.00%> (+0.50%)
:arrow_up:

NOTE for reviewer:
Would it be possible to get some feedback on whether this feature would be accepted in ko (regardless of the implementation)?

Definitely a feature I'm interested in. Is there any prior art here re: the UX of this flag?

Is there any prior art here re: the UX of this flag?

Answering my own question: I see that docker has a --cap-add and --cap-drop flag for docker run. Using that might be reasonable? I'm not sure if it's even possible to drop capabilities using xattrs, so maybe that doesn't make any sense.

@imjasonh @jonjohnsonjr WDYT about the latest changes? Is this ready to be merged?

@inteon FYI similar feature landed in https://github.com/ko-build/ko/pull/1271


feat(validator): has the error message per rule

In this PR, the validator will have multiple result objects, so it will have an error message per rule.
For example, one error message will become more friendly.
'Invalid Value: the request body "title" is invalid - abcdefg'

will be:
'Invalid Value [abcdef]: the request body "title" is invalid - isLength'

Internally, it has error objects as follows:
[
  {
      "isValid": true,
      "target": "body",
      "key": "title",
      "value": "abcdefg",
      "ruleName": "should be \"string\"",
      "ruleType": "type"
  },
  {
      "isValid": false,
      "message": "Invalid Value [abcdefg]: the request body \"title\" is invalid - isLength",
      "target": "body",
      "key": "title",
      "value": "abcdefg",
      "ruleName": "isLength",
      "ruleType": "value"
  }
]

If you want to do more complex error handling, you can refer to this result objects in the done option.
const vHandler = validator(
  (v) => ({
    title: v.body('title').isLength({ max: 5 }),
  }),
  {
    done: (res, c) => {
      if (res.hasError) {
        // ... do something
        // console.log(res.results)
      }
    },
  }
)

This PR is related to #561

Hi @ThatOneBro !
Could you see this PR?

Hi @yusukebe , sorry it took so long! I meant to already review this PR, I'll look at it right now! 😄

I did some testing and I think this PR is good.
I added a test in #609 in case you want to merge the test in too.


Realm creation form doesn't properly handle long domain names

On /create_realm with a moderately long hostname, It'd be better to shrink the text box than do this line-wrapping.

@zulipbot claim


Building Kong from source fail because of wrong submodules versions

When building kong from source in version 3.1.0, thekong-build-tools/openresty-build-tools/kong-ngx-build command fail with this error:
error: unknown type name 'mdb_size_t'

kong-ngx-build run with --resty-lmdb 1.0.0 as requested for this version of Kong, but the issue is that kong-ngx-build do not checkout correct version of submodule lmdb in the lua-resty-lmdb repository.
I opened a PR to fix this issue: https://github.com/Kong/kong-build-tools/pull/644

We are no longer maintaining this repository as Kong is now build by Bazel: https://github.com/Kong/kong/tree/master/build


Remove fail-fast for Ginkgo

Parallel tests cause parallel processes to get interrupted on a failure, creating too much noise (and it's unnecessary now that the tests complete in a reasonable time).
The -p flag is also redundant since --procs is already specifying parallelism since its default is 1.

There was one flake that showed up which I've added some additional logging for if it shows up again, but the fail fast flag removal was also working as expected, so this is ready for review.


ESP32-H2: Add support for ESP-IDF v5.0

Problem
The tag v5.0-beta1 of ESP-IDF is released now, so update the support for ESP32-H2 based on IDF-v5.0-beta1.
Change overview
Update the support for ESP32-H2 based on idf tag v5.0-beta1.
Testing
Tested on ESP32-H2, the commissioning and controlling work well.

/rebase


Fix error in README.md

Thank you for releasing this! It will be very useful for developer starting out with Craft. I just made a fix to the readme

Thanks for the fix!


Can't seem to get tabs correct

Description
Thank you for making this wonderful tool. I've been very pleased with it's functionalities. However, I'm struggling with getting the auto-tab complete to work right. When copy and pasting the before and after beautify I noticed the tabs pasted normal (i.e. the desired/correct spacing/tab). This might be a hint that it's just how it's being rendered. I've tried playing with the files in the "uncrustify" folder, the editor settings, and go through restarting/unistalling the package with no success. I've also attached a screen shot of my editor showing what appears to be double tabbing. I'm not great with Atom so I've likely missed a setting.
Thank you for any help,
Best,
Zev
https://gist.github.com/zeeev/95a45bec2f723ad777298bbfb5ea78ff

I have:

[x] Tried uninstalling and reinstalling Atom Beautify to ensure it installed properly
[x] Reloaded (or restarted) Atom to ensure it is not a caching issue
[x] Searched through existing Atom Beautify Issues at https://github.com/Glavin001/atom-beautify/issues
so I know this is not a duplicate issue
[x] Filled out the Input, Expected, and Actual sections above or have edited/removed them in a way that fully describes the issue.
[x] Generated debugging information by executing Atom Beautify: Help Debug Editor command in Atom and added link for debug.md Gist to this issue

The link to the gist is in the debug.md was already in the issue. I'm not sure why the bot is not seeing it.

It's the checkboxes in the issue template.  I'll fix the message to say that.

@szeck87 Thanks. I've updated the checkboxes. I missed one.

Yea it doesn't use the default.cfg unless you put it in the settings.  We only send input_tab_size, output_tab_size, and indent_with_tabs, none of those seem to do anything.  I'll need to do some playing around and fix what we send by default.
Meanwhile, can you try putting the path to the default.cfg file in Atom Beautify's settings under C?  Also comment out align_number_left in that same file.

Thank you for the suggestion, @szeck87. By simply providing the path to the default config, and commenting out the align_number_left the issues was resolved.
Thank you again for building and supporting high-quality open source software.

No problem.  Let's leave this open as a defect with spacing using Uncrustify. I'll look into it more later this week.


Add slide threshold

When sliding horizontally even the tiniest bit, remotely close to none, it changes to the next or previous slide. With this update, you need to scroll at least 10% of the carousel width so it takes the action. Otherwise, the current slide is retained.

_this.data.shouldSlide nothing about this instance. need details about this

Does it work well now?


Fixing dll method reference

Fixed dll method reference for Storage FQDN resolution
Added traces for connectivity summary

@Azure/microsoft-azure-workload-backup-scripts-maintainers please review the changes


Prefix Pronto ENV config variables

@mmozuras this PR prefixes all of the Pronto configuration variable ENVs.  Let me know your thoughts.
Examples:

CONSOLIDATE_COMMENTS -> PRONTO_CONSOLIDATE_COMMENTS
GITHUB_SLUG -> PRONTO_GITHUB_SLUG
MAX_WARNINGS  -> PRONTO_MAX_WARNINGS
VERBOSE -> PRONTO_VERBOSE

@doomspork 👏
I think that it makes a lot of sense, helps avoid possible conflicts, bugs.
Thanks mknapik for the idea 👍

Thanks @mmozuras!  Do you want me to submit a PR to update the README or will you handle that later?

@doomspork sure, go ahead and make a PR. Will merge it after releasing this change to not confuse users of Pronto 😄


Add a small note about indexes ignoring SemVer build metadata.

This adds some clarification to the documentation on how registries need to handle SemVer build metadata, and the uniqueness constraint around version entries. IIRC, some issues in cargo have been fixed, but some still linger (like #7180). crates.io just fixed it so that new duplicates will be rejected.

Looks good. Thanks!
@bors r+

:pushpin: Commit 0ab423dfe98c47b8bd03e8aa3c9c3adf597e6b53 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 0ab423dfe98c47b8bd03e8aa3c9c3adf597e6b53 with merge 9b85e1171313be86a834099ba013c3deb0540170...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing 9b85e1171313be86a834099ba013c3deb0540170 to master...


[NumPy] Fix np flip when axis input contains negative number

Description
As title.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at https://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Fix and extra error message
[x] Extra test case

Comments
@xidulu

@mxnet-bot run ci [centos-cpu, windows-gpu]

@mxnet-bot run ci [windows-gpu]


Keep track of paid course runs

We should not delete PaidCourseRun on unenrolling the student. This model was created for tracking purposes and was meant to keep track of the payment status of the enrollment.
It was first introduced and described in this issue https://github.com/mitodl/mitxonline/issues/738
The deletion of the model was introduced in this PR https://github.com/mitodl/mitxonline/pull/1474.

@annagav is there a reason why this came up?

Here https://github.com/mitodl/hq/issues/3929.
When we defer a user the PaidCourseRun gets deleted.
I think we need to add states to paidCourseRun instead of deleting.


Docker's agent response in chat streams code as if it was raw markdown

Testing #217639
Using the docker agent, you can see how it renders the code weirdly as it's being streamed:

Same as https://github.com/microsoft/vscode/issues/217915 I think, although I can't get this kind of response out of @docker, it just returns an error for me :)


bug: Address asset view not available in sidebar

Provide environment information
MacOs
Brave
Describe the bug

It says we could access address asset viewer in the sidebar but I don't see how? clicking on my wallets doesn't do it.

I can get to the address viewer by clicking on token owner addresses but not in sidebar. If it's not meant to be that's fine maybe I misunderstood.
Link to reproduction
https://realms.world/collection/goldenToken
To reproduce
There is no page I see where I can access my own address or others in the sidebar.
Additional information
No response

Fixed in #58 3bdbc91


No way to tell that a given form is submitted

Related to at least #119, #242, #267, #280, #291, #355, #401
We do if formdata is not None before calling process_formdata on each field in a form. This broke the rather common case where users were passing request.form to a form even if the method wasn't POST because request.form isn't None. Previously we checked bool(formdata), which handled this case but caused processing to behave inconsistently depending on what was submitted.
Flask-WTF somewhat handles this by only passing request.form if the method is actually a submit method (POST, PUT, DELETE).
None of the approaches are really correct. Maybe you have a client that always sends some extra data (for example, an auth key). Or you have two forms on the same page, whichever was not submitted will still see the same non-empty form data as the one that was submitted.
f1 = FormA(request.form)  # was submitted, sees data
f2 = FormB(request.form)  # was not submitted, sees same data

Most built-in fields mask this issue because they only change data (which is set from the default / object data first) if formdata.getlist('name') is not empty. However, StringField will set data = '' if nothing was submitted (which #355 changes). And SelectMultipleField and MultipleFileField will overwrite with an empty list because there's no way to distinguish "selected zero values" with "didn't send data" (BooleanField has a similar problem.)
This can also cause weird issues during validation with InputRequired. If there are two forms, and you do something like if f1.validate(): ... elif f2.validate(): ..., and f1 was not submitted, it will show a "input required" error even if a default value was being displayed, which is confusing.
I'm not sure what the solution is here, but am open to discussion. We can break things, I don't care about backwards compatibility for 3.0.
CC @lepture @alanhamlett

This is more broadly important if we want to validate other data sources such as JSON, or PATCH requests, which do not have the same constraints and behaviors as HTML forms.

We could check if any of the form keys match any of the field names before processing. But this is expensive and unnecessary for the most common case of a single form. It's also incorrect for validation, where "no form data" might legitimately be a validation issue.
Alternatively, we could have a Form.is_submitted(formdata) method which just returns True by default, or True if any keys match submit field names and values. Flask-WTF already has this concept, although it's not implemented the way I just described, and it only applies to validation right now, not processing.

The most radical change would be to stop considering different data sources differently. Remove process_formdata and only use process_data. Combine data in layers, like form (incoming) data > keyword args > data dict > object > field defaults and process it once. However, I want to fully understand why it's not done this way (there's an FAQ entries about it and multiple issues have been closed because of it) before we do this.

It is logical error. Doc https://wtforms.readthedocs.io/en/stable/forms.html The Form class -> class wtforms.form.Form -> Construction init(formdata=None, obj=None, prefix='', data=None, meta=None, **kwargs):
formdata – Used to pass data coming from the enduser, usually request.POST or equivalent. formdata should be some sort of request-data wrapper which can get multiple parameters from the form input, and values are unicode strings, e.g. a Werkzeug/Django/WebOb MultiDict
MultiDict is not None. MultiDict can be empty dict. Flask used Werkzeug as wrappers standart function.
Example:
@app.route('/url', methods=['GET', 'POST'])
def url_func():
    form = UserForm(request.form, data={'var': 'val'})
    if request.method=='POST':
        ...
        return 'POST request'
    request 'GET request. var={}'.format(form.var.data)

And GET request.form is type MultiDict (or ImmutableMultiDict) and equal empty list (is not None)

See the rest of my post, I address why truth testing instead of none doesn't solve the issue.

My english is bad. Do I need to suggest a solution? Or the solution is already found and will be in the next version?

It sounds like this issue should be tackled for 3.0. What do you think?

I would like to get something into 3.0, but as I've said above I don't know what that would look like. I don't think there's going to be a 100% satisfying solution to this.

We need to come up with a policy for data processing and apply it consistently. We need to keep in mind that WTForms is intended first for processing HTML form data, and account for the fact that HTML form data is ambiguous in some cases such as boolean, multi-select, and file fields.
There are multiple types of data:

No data (formdata is None) - #280 started using this instead of bool(formdata) to decide to process data, since it's more accurate in indicating that form data wasn't submitted.
Empty data (bool(formdata)) - This is unreliable if other form data is submitted such as API tokens, or if one form is submitted on a page with multiple forms. Technically this is true of formdata is None too, but I think None is a better indication that this isn't a post request.
Partial data - This isn't supported right now, but would be useful for patch requests or API requests, where only changed data might be submitted. Could do something similar to Marshmallow, where a partial=True flag on the form uses default values if the key is missing. This can come later, but should be kept in mind at least.
Implict defaults - #280 and #355 dealt with this for StringField, where the value might be '' or None depending on what was passed in. I think 3.0 should consistently set values to None unless a value was actually given (for all fields, not just string).
Provided defaults - There is constant confusion that defaults passed in as default= for fields, or obj, data, and kwargs for forms, is only used when no form data at all is provided. If this wasn't the case, there would be no way to submit an empty value for a field if it also had a default. It's also confusing which of obj, data, and kwargs takes precedence. I think the way forward here is better documentation, no behavior changes.

There are multiple places where processing happens:

Form processing - Called automatically when a form instance is created, decides what default data to pass along with form data to each field's processing.
Field processing, default data - This should be better about accepting string or Python data consistently.
Field processing, form data - This should also be better about accepting string or Python data consistently; HTML form data will always be strings, but people keep trying to pass JSON or Python in. Some default filtering to strip surrounding space should probably be added (except for strings, where that should be an option).
Field filters - Seems to be very underdocumented. It's common to modify data in a validator instead, since that API is more well known.
Form validation - Recently formalized form-level validation errors. Other than that just calls out to each validator, collecting validator methods from the form.

Field validation - Some fields implement pre validation. Post validation is also available but not used by any built-in fields. In charge of accounting for errors that were caught during processing. Errors here can either stop validation or just append an error message and keep going.

This post initially started as me collecting all the discussions once again, but turned into a big dump of my current thoughts on behavior of the entire processing stack. The amount of information here might make the situation look worse than it is. WTForms is already fairly consistent and works, but there's a lot of little inconsistencies and ambiguities that can be addressed.

Further down the line, a solution to ambiguous fields could be to render a hidden input with some sentinel value in order to force a submitted form to send a value for the field. For example a boolean field could render a hidden input with "value=unchecked" and then a checkbox with "value=true". If the list of values only contains the sentinel, it is false, otherwise it is true. If the name is not in the form data at all, we now know it was not sent and can safely assume the default. Similar schemes can be used for other field types. I'm not sure exactly how this would work, fields right now only render one input, and hidden fields are usually rendered in one block with form.hidden_field().

@tomchristie Any insight from TypeSystem on handling the ambiguity of missing HTML form data? I couldn't find a discussion of that in its docs.

Erm, I guess useful points are...

If you're going to have more than one POST form action associated with the same URL, you really want to be using something like a submit button to populate an action="<some action name"> field, to determine which form is being submitted.
Fields are always required, unless they have a default. Tho "required" just means some value must be included, even if it is None or "". We run validation for all values, including "" and None - it's the responsibility of the field to handle validating those cases, rather than the responsibility of the containing schema/form/thingumy.
All fields have an optional allow_null. If it is set to True, then we also set default=null. Fields coerce "" values to None if set.
For CharFields, we have both allow_null or allow_blank and options, and coerce inputs one way or the other. If allow_blank is set then we also set default="".
For booleans, we force users to explicitly add a default=False.

Don't know if that's any help. 🤷♂

Haha, sorry to drag you into this without warning, I just remembered you had worked on a form library recently, thanks for answering 😅

(I'm unsure this is useful, but, as WTForms user, this is the way I expect WTForms would behave:

Currently, it's possible to instanciate a Form without filling the formadata or obj parameters. I don't understand what's the point: if none of them are not provided, what is the goal of Form().validate() method? I wonder if it would help to change these optional parameters to force one of them to be filled. If both are None, an Exception would be raised.

Missing parameter should be accepted only if the Field accepts it. I think there could be a new parameter to define if it's ok to not post it. By default, it would be forbidden (like Tom Christie does with allow_null=False parameter), except for RadioField and CheckBoxField because the browsers don't send the value if unchecked. In case of not send, the value should be set to the default parameter. (allow_missing or missing_ok are better parameter names IMO.) However there would be a problem with PATCH: a missing field is ok but the default value is not what we want, it need to be known that the value was not filled. Using an boolean attribute on Field could be a solution (field.sent?).

Default parameter should provide a compatible type to the formatted data: for example, an IntegerField should provide a default value like 0, an UUIDField should provide a UUID instance (or an equivalent object according to duck typing), etc.


Why Job doesn't fail when terraform show errors

All jobs are completed and successful even though something went wrong with "init", "plan" or "apply".
Why? Wouldn't it be better to fail so we can collect metrics and do something about it without having to check pod logs?

@francardoso93 I agree that it's odd that the pod completes and is marked as successful when something goes wrong. I personally haven't had an issue checking logs when I see something didn't occur that I expected to occur, but I think you're right that a failure metric is way more useful than waiting for other errors to happen if tf didn't run.
The script that powers the tfo runner (in v0.3.x) is https://github.com/isaaguilar/terraform-operator/blob/master/docker/terraform/run.sh. I think it'd be pretty easy to inject an exit flag that gets updated on init, plan, or apply events, then exit with that exit code. My problem with updating this script is actually a big flaw in TFO's design which is that the runners aren't version-able.  (NOTE I'm fixing the runner-versioning flaw in v0.4.0+ releases).
So what I'll do is test out updating the script with an exit code flag and see if that works to get a pod to fail without any repercussions.

PS In v0.4.0+ versions, init, plan, and apply are all executed in different pods and do fail upon error. This stops the terraform workflow and even updates the terraform resource's Status. I'm still working on docs and testing for this design change.

I'd also like to mention that users can create their own runner. It's very poorly documented, but hopefully this doc can help someone get started if they themselves wanted to changes the behaviour of init, plan, and apply: https://github.com/isaaguilar/terraform-operator/blob/master/docs/architecture.md#custom-terraform-runner


fix(seed): Add tests, solution, and image for Project Euler problem 15

Pre-Submission Checklist

[x] Your pull request targets the staging branch of freeCodeCamp.
[x] Branch starts with either fix/, feature/, or translate/ (e.g. fix/signin-issue)
[x] You have only one commit (if not, squash them into one commit).
[x] All new and existing tests pass the command npm test. Use git commit --amend to amend any fixes.

Type of Change

[x] Small bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds new functionality)
[ ] Breaking change (fix or feature that would change existing functionality)
[ ] Add new translation (feature adding new translations)

Checklist:

[x] Tested changes locally.
[ ] Addressed currently open issue (replace XXXXX with an issue no in next line)

Closes #XXXXX
Description

Added more tests, a solution, and an image to make the description more clear.
The image is from Project Euler but is re-hosted on imgur. Should be fine to use the image under the Creative Commons Licence, but if not, I could recreate it and update this PR.
BREAKING CHANGE: None
Here's the solution for QA:
function latticePaths(gridSize) {
  let paths = 1;

  for (let i = 0; i < gridSize; i++) {
    paths *= (2 * gridSize) - i;
    paths /= i + 1;
  }
  return paths;
}

Thanks @scissorsneedfoodtoo 👍

@Bouncey, thank you for taking the time to QA and merge this!


Any way to make phone audio go to headphones of pc?

Hello, so i have this problem where audio comes from the android phone and not the headphones, i really would like for it to go to headphones, any way to do so?

https://github.com/Genymobile/scrcpy#audio-forwarding

Most desktop motherboards have Line In, I use that myself.
You need to plug 3.5mm audio plug to Line In and the headphone jack of your smartphone (It still has one, right?) then set Line In to Listen To your Playback Device of choice.

Most desktop motherboards have Line In, I use that myself.
You need to plug 3.5mm audio plug to Line In and the headphone jack of your smartphone (It still has one, right?) then set Line In to Listen To your Playback Device of choice.

i have a laptop oof

Most desktop motherboards have Line In, I use that myself.
You need to plug 3.5mm audio plug to Line In and the headphone jack of your smartphone (It still has one, right?) then set Line In to Listen To your Playback Device of choice.

i have a laptop oof

I'm sure there's some USB soundcards or something if you want wired and no latency audio, but not sure if it's worth the money over rom1vs audio forwarding solution.


Update current master with code from upstream

The list of changes:

pytest instead of nose
test fixes/new tests from upstream
code is now formatted with black
all tests that fail (permanently or not) - are marked with pytest.mark.skip(reason='Potential Bug') or pytest.mark.skip(reason='Not Implemented')
'sanity' flag was removed (there is no sense in it right now) - amount of stable tests is 194 and they run for 8min30secs. Tests that we are currently interested in are located here s3tests_boto3/functional/test_s3.py and s3tests_boto3/functional/test_s3_neofs.py

One thing about commits - I can squash everything into the one big commit or leave it as is - with a history of commits from the upstream. I prefer squashing, but perhaps history will be useful in the future - during test failures investigation.
Further plan:

Improve allure reporting (even with the latest changes it is not friendly enough), should be more like in testcases repo.
Investigate everything in s3tests_boto3/functional/test_s3_neofs.py, open corresponding bugs; since these tests were specifically written for neofs - they should pass + there are not so many of them.
Move to s3tests_boto3/functional/test_s3.py - investigate everything that is not marked with fails_on_aws or fails_on_dbstore - this is a huge effort, so we will need to prioritise skipped tests.
Investigate tests marked withfails_on_aws or fails_on_dbstore

I'd expect to see some clear merge that solves #31 and then any additional things as a set of commits on top of it, looks like at the moment they're all mixed into the merge commit itself. Squashing is not an option.

Maybe they can't be separated though, I've not tried merging them to judge what number of conflicts there is and is there any possibility to solve them without a lot of changes in the merge commit itself.

It is too painful to separate commits or to do smth with these commits structure (except just squashing), so I'd prefer not to do anything with it. At first I thought it be much easier just to refork the repo. Conflicts are almost everywhere, test_s3.py (16337 lines) is just a one big conflict that very hard to process.


Update UI

I deleted unneeded or duplicated files
I moved the application logic outside the UI. The UI is now responsible only for changing settings (and manual change), after the application closes the thread is started.
I gave the centralWidget a layout, so that every widget is now positioned and scaled automatically
depending on the desktop in the config, some plugins get disabled and you can not enable them (for example, I use KDE and therefore Gnome is disabled). It would also be possible to make the widget invisible :thinking:

I tested if every setting in the UI changes the config properly, if I missed something let me know :sweat_smile:
Fixes #48

Here is how it looks now:

An alternative  design for the main window

unselected options are hidden, I could even put the buttons in an additional option "manual"
the selected mode could be set directly in the config, possibly with an enum containing all the options rather than using boolean for every option
the times for sunrise and sunset are not visible anymore, but I could add a label for that

Hey this is looking really good!

Hello,
I think this version (https://github.com/daehruoydeef/Yin-Yang/pull/68#issuecomment-711203843) works better from a UX perspective as it doesn't hide the options behind a drop-down. I would also recommend to align the check-boxes to the left instead of having them centred. Finally what about a toggle instead of a check box for the different desktop options?
Cheers,

I think this version (#68 (comment)) works better from a UX perspective as it doesn't hide the options behind a drop-down

I agree, if sunrise and sunset are used as the time, the user should see which time has been set. Same for the position if there's a feature in the future which sets the location based on the current position.

I would also recommend to align the check-boxes to the left instead of having them centred

I'm using title and checkable properties of QGroupBox. The title is actually set to be left, hover it seems like not every theme supports it. The windows and fusion theme seem to align it properly.
A workaround would be to add a checkbox manually, but this would make things more complicated.

Finally what about a toggle instead of a check box for the different desktop options?

As far as I know there is no toggle in Qt.

I'm also thinking about adding a small icon in the notification center which can be used to toggle the theme manually. Depending on the theme in use, the icon would switch to a dark or bright version. With a right click, the user could open the settings menu.
Also, an option to send a notification about theme changes would be nice.

Hello,
I found these resources about toggle button in Qt:
https://stackoverflow.com/questions/14780517/toggle-switch-in-qt
https://doc.qt.io/qt-5/qmlexampletoggleswitch.html
I don't know if it's helpful but in the stackoverflow there is even a python implementation example ;-)
As for the small icon I think that it would be a nice addition. In KDE they do have one for Night Color that you can probably check as example.
Cheers,

I would not let the user fill in there own lat / long. You should be able to switch between time and sunrise/ sunset. Both options exposing the  fields to adjust the time. The difference is that with the lat / long the fields are locked and the values are pre filled.
Also it should be sunrise to sunset.
I will come up with a variation of this Design, I will hide the Play Sound behind the Settings leaving the main interface as clean as possible. Also the Settings Button will get a actual Settings Icon.
I am happy to announce that I can continue working on this project now and dedicate more time. Thank you for your help, I really appreciate that!

Also I see that the new UI features a tab called applications, with the current implementation this is not possible it would need to alter the windows rules. Right now the best effort would be to enhance stability, come up with a real installation process and enhance the GTK Support.
I did a V2 branch, there is a slightly new GUI that is conditional based on the desktop environment you are using. Gnome is exposing different fields than on KDE. I would like to keep this tool as much cross platform as possible. Using a notification icon would be a really great idea for KDE but would need to be disabled on Gnome or other. Also lets keep the checkbox as a toggle switch. We would need to do our own implementation for this which is not worth it I think


NDArray common API

cumulativeSum output type MutablePrimtiveNDArray

erf output type PrimitiveNDArray

copyIfNotMutable output type

pad function in ndarray-core contains mode: String, change it on Enum or something other pls

tile output type

copyIfNotMutable output type

Same thing in Mutable version

scalar in companion object in MutablePrimitiveNDArray have incorrect type

slice at BooleanNDArray return type

invoke(vararg shape: Int, init: (Int) -> Boolean) in MutableBooleanNDArray have incorrect return type


DB2 for IBM i (also known as AS/400 - iSeries - ...) support

Original author<EMAIL_ADDRESS>(March 08, 2012 20:53:53)
Purpose of code changes on this branch:
I provided an additional database flavor: in fact "DB2 for IBM i" is a member of the DB2 family, but there are some adaptations, mostly related to the catalog...
Regards
Luc
Original issue: http://code.google.com/p/flyway/issues/detail?id=229

Hi Axel,
What can i do to help? What's missing to include this in flyway?
Thanks

We have decided not to implement this as it is very unlikely we will never have access to such a system for testing.

@axelfontaine It would be a shame if Flyway couldn't support the best relational database out there. Is there a way we can add support for DB2 on i by just adding an existing jar to the classpath? Then someone else could support DB2 on IBM i in Flyway and you don't need to have it in you source.


Can't debug runIde task because of duplicate jdwp options

Describe the bug
runIde task cannot be launched under debugger in IDEA. Gradle shows the following error
ERROR: Cannot load this JVM TI agent twice, check your java command line for duplicate jdwp options.

It seems this commit introduced duplication of jdwp option
To Reproduce
Just launch runIde task under debug in IDEA
Expected behavior
Debugging of runIde works as previously
Environment:

OS: macOS 12.5.1
Gradle IntelliJ Plugin Version: 1.10.0-SNAPSHOT
Gradle Version: 7.5

Thanks for reporting. The fix is now available in the 1.10.0-SNAPSHOT.


Document CNI nodename configuration

If a kubelet uses a name to register that is not its hostname, the associated CNI plugin on that node has to be configured with this same name.   If the kubelet name and the CNI nodename do not match, felix will not create routes for pods created on that node.  Update the CNI configs for Kubernetes to reflect this.

I'll take a humble shot at documenting this.


Raw mode improvement

Currently, there are somethings what could be done better according to raw mode.
I can't explain what it is because there are playing a lot of factors a role and that story will be longer than me fixing it.
However, this is just a tracking issue.

This will likely be improved in 0.8.3 - refactor

Fixed in #115


Multiple RST_STREAM sent while receiving DATA frames in flight after cancel.

Looking at frame logging after a cancellation
<< 0x00000003 16384 DATA
>> 0x00000003     4 RST_STREAM
<< 0x00000003 16384 DATA
>> 0x00000003     4 RST_STREAM
<< 0x00000003 16384 DATA
>> 0x00000003     4 RST_STREAM
<< 0x00000003 16384 DATA
>> 0x00000003     4 RST_STREAM
<< 0x00000003 16384 DATA
>> 0x00000003     4 RST_STREAM
<< 0x00000003 16384 DATA
>> 0x00000003     4 RST_STREAM
<< 0x00000003 16384 DATA
>> 0x00000003     4 RST_STREAM

My reading of the spec is that only the first RST_STREAM should be sent
https://datatracker.ietf.org/doc/html/rfc7540#section-6.4

However, after sending the
RST_STREAM, the sending endpoint MUST be prepared to receive and
process additional frames sent on the stream that might have been
sent by the peer prior to the arrival of the RST_STREAM.

Dupe of https://github.com/square/okhttp/issues/6171


Add PSR-4 support to tests

I've added PSR-4 support to the tests.
This partially closes #109.

@jenssegers I've removed hhvm tests and the tests now works fine.

@jenssegers I've added a service provider test and dropped PHP 5.3 support.

Coverage increased (+0.01%) to 99.77% when pulling de5e5b7ffa679c50247ff0307d09ed756ede012b on vinkla:tests into 9410bcf69c1eb8063a062c6135af648738f187ad on jenssegers:master.

I'm still not completely sure about the PSR4 support for tests, it just feels so unnecessary. Not even Laravel uses PSR4 in their tests.

Why not? In this way we'll code the package source and the tests in the same way. The The League of Extraordinary Packages, Graham Campbell (who is one of Laravel's maintainers) and many more does this already. Why shouldn't we? This update gives us better coverage tests :)

@jenssegers have you had any time to think this through?

@jenssegers have you had any time to think this through?

@jenssegers have you decided? If you don't want it I understand. Please let me know!

Currently I don't really see the point in keeping tests PSR-4, sorry. I might come back to this later but will close it for now.


Add Custom Echo Binder to catch not-allowed fields during POST requests

There isn't a ticket for this yet - but this is somethign I've been wanting to do for a while so I took a bit of time this hackathon to do it.
Basically we need to return 400 when extra fields are returned in a request, this was all handled via metaprogramming (and via the openapi spec) on the ruby side, but thankfully there is an easier way here on the Go side.
The "allowed" fields are all codified on the *CreateRequest structs - those struct are the control of what we allow in on POST calls. So if we can just validate the JSON bodies against the tagged fields in those structs we basically have codified field validation.

Basically we can use a custom echo.Binder instance to decode the json bodies, and in doing so we have control of the decoder which has a setting to disallow unknown fields.
The default behavior is just to discard them and not error out, which is what we do not want. Luckily we can limit this only to the context#Bind(interface{}) calls as well - so we don't have to change any other code.
Here is what the response looks like now with an "extra" field passed into POST /sources:

I'm debating setting the test echo instance's binder to our custom one but am not having luck there. Some tests fail if it is set, I will look at it more next week.

/retest


feat: lemmas analogous to fderiv_within_of_open

from the project towards Sard's theorem

I have not compared FDeriv.lean and MFDeriv.lean to check if there are other lemmas only stated in one context.

Thanks; all addressed.
I was mirroring the lemma fderiv_within_of_open - I take it should be renamed; I've pushed a commit accordingly.

bors r+
maintainer merge
Thanks!


Mermaid flowchart is not completely supported

graph TD
ShortArrow --> WorksInDevOps
LongArrow ----> DontWorkInDevOps
The long arrow is supported in Mermaids live editor, but not in DevOps:
Image from DevOps:

Graph from mermaid Live editor:

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

ID: 29f1e43f-a069-dd88-7fc7-9cc497fb94f0
Version Independent ID: c261afa7-6eb7-b3f0-9f92-6d2f3c5ac336
Content: Markdown syntax for wikis in Azure DevOps - Azure DevOps
Content Source: docs/project/wiki/wiki-markdown-guidance.md
Product: devops
Technology: devops-collab
GitHub Login: @chcomley
Microsoft Alias: chcomley

Thanks for the heads up, @mkrsbl, I'll make the update. Once published, this issue will automatically close. Thanks again.


Update new content

Note that the practice code is not uploaded fully.

とりあえず, upload the current progress code.


BUG:Pay with debit card - Doesn't auto-complete the zip and state correctly

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Go to ND and login
Go to settings > payment > Debit card

Expected Result:
Zip code and password should not auto filled in correctly
Actual Result:
Zipcode auto filled with some portion of the email and password of that email
Workaround:
Unknown
Platform:

Where is this issue occurring?

Web

Version Number: 1.2.12-1
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos:

https://user-images.githubusercontent.com/43996225/194431077-0349df27-0441-45de-b041-fdc1a8994873.mp4
Expensify/Expensify Issue URL:
Issue reported by:  @quinthar
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1665001946509239
View all open jobs on GitHub

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

Sorry, it is reproducible in production too

Having trouble reproducing in web, discussing here.

Looking into this further today.

Clarifying a few questions about this here.

@alex-mechler unassigning you as the bug that caused this is reported as being fixed by the above PR.

Asking clarifying question here to understand a bit better the relationship between this bug and the above linked PR.

Still discussing in Slack thread.

Discussed with @rushatgabhane in Slack to understand a bit more about how the above linked PR fixed this bug.
Since this bug is being fixed by a PR that's already merged, we're all set to close here. Payment will be handled in the original issue that led to the above linked PR.


feat: cache the Nagware overdue response form IDs

Summary
Update the Nagware function so that it caches the overdue response form IDs in Redis.
This is being done to reduce strain on the DynamoDB table when loading a user's /forms page.
Related

https://github.com/cds-snc/platform-forms-client/issues/4234

Noting if we want to test the front-end
Can flip  checkForOverdue to true
https://github.com/cds-snc/platform-forms-client/pull/4221/files#diff-f46d88023f6b538e47c703d64cfc3e12a8247db7c705ce8fd7888f2322cd779dR75


Feature - announce autoplaylist songs

Would like to see some config option etc to enable spamming channel with current autoplaylist song being played :) like the normal playlist one does
Cheers

Duplicate of #526


Documentation: cds.load für .json

Hi
See https://cap.cloud.sap/docs/node.js/api#cds-load
There, an order of file loading depending on file extensions is listed. What about the good old .json-extension? My tests show that this is still considered, right after .csn. Is this just missing in the docu, or is json-loading deprecated?
Regards

Thank you. We will have a look at it and get to you back here asap.
Best regards,
Iwona

Hi @wattnu, you are right .json is still supported, but sort of silently deprectated (as it never was publicly documented) → you should prefer .csn as that has less risks of accidentally picking wrong .json files.


Optimize Block Level Code Input Experience

Is your feature request related to a problem? Please describe.
The user experience of block level code input is not very good. Can you optimize it?
Describe the solution you'd like
I hope block level code input can have a complete background, and the code can highlight in input mode
Describe alternatives you've considered
I think codemirror gfm mode is awesome https://codemirror.net/mode/gfm/
Additional context

Would be awesome to have suchfeature, was looking for something similar as current block level code looks weird and I do rather prefer a fully background.


DateTime(...).toUtc() and DateTime.utc(…) give different results

Dart VM version: 2.1.1-dev.1.0 (Wed Jan 9 14:55:46 2019 +0100) on "macos_x64"
Using Flutter

The issue is rather straightforward. I would expect DateTime(...).toUtc() to give the same output as DateTime.utc(…) but they don't.
Given the following example:
DateTime now = DateTime.now();
DateTime toUtc = DateTime(now.year, now.month, now.day).toUtc();
DateTime utc = DateTime.utc(now.year, now.month, now.day);
print("now $now");
print("toUtc $toUtc");
print("utc $utc");

the output will be:
now 2019-04-02 16:28:23.223
toUtc 2019-04-01 22:00:00.000Z
utc 2019-04-02 00:00:00.000Z

whereas I would expect it to be:
now 2019-04-02 16:28:23.223
toUtc 2019-04-02 00:00:00.000Z
utc 2019-04-02 00:00:00.000Z

I think this behavior makes sense.
The following creates a new DateTime object when the current timestamp are in you own timezone and converts it to a new datetime object where the time is represented as UTC:
DateTime toUtc = DateTime(now.year, now.month, now.day).toUtc();
And here you create a DateTime object where you tell Dart that the input are already UTC.
DateTime utc = DateTime.utc(now.year, now.month, now.day);
Please see the documentation for the two constructors:
https://api.dartlang.org/stable/2.2.0/dart-core/DateTime/DateTime.html
https://api.dartlang.org/stable/2.2.0/dart-core/DateTime/DateTime.utc.html
And the toUtc() method:
https://api.dartlang.org/stable/2.2.0/dart-core/DateTime/toUtc.html

CC @lrhn

This is working as intended.
DateTime(y, m, d).toUtc() finds the y-m-d time in the local time-zone and then creates a UTC date at the same point in time. So, if I'm in the UTC+2 time zone, and I do DateTime(2019, 04, 02).toUtc(), I start with the local time 2019-04-02T00:00:00+02:00, and then find that the corresponding UTC-time is 2019-04-01T22:00:00Z. That's the same point in time in a different time zone, it answers the question "when the local time is 2019-04-02T00:00:00, what is the time in the UTC time zone".
When you do DateTime.utc(2019, 04, 02), you get the point in time where the UTC clock showed 2019-04-02T00:00:00Z. If I do toLocal() on that, I'd get the local time 2019-04-02T02:00:00+02:00.


CX Priority Selection

https://github.com/Jacudibu/PRUNner/projects/1#card-62816375
Where would  this CX Selection be?
There is no selection on the planner currently.

Yeah, right now you'll need to edit the UserData/empire.json file manually – right at the top there should be this field:
  "GlobalSettings": {
    "PriceDataPreferenceOrder": [
      "PlanetOverrides",
      "EmpireOverrides",
      "NC1Bid",
      "NC1Average",
      "MMBuy",
      "NC1Ask",
      "MMSell"
    ]
  },

Just change the order or change NC1 with any other CX and then reload your Data :)

Implemented in v0.4


Massive interaction improvement when it comes to the current load graph

Just throwing in a wild idea here. Is it possible to just always show the user the coloured dots (under the 'View default topology' button). And whenever he clicks on the green one - a tiny loader will appear and the loadGraph will add the green line for storage.
This way we don't need to deal with those rather ugly radio buttons and just throw those out of the window.
@ChaelKruip what do you think?

After discussing this @grdw and I decided that this idea is going to confuse the user because different strategies will show up as the same (green) effective load curve. So, there is no one-on-one relation between the suggested buttons and the curves in the chart. Closing.


Add ValidataclassMixin class

This PR adds a mixin class ValidataclassMixin with two methods:

to_dict() returns the data of the dataclass object as a dict (wraps dataclasses.asdict())
create_with_defaults() is a class method that creates an object of the dataclass using default values (from the field metadata), providing an alternative to the regular constructor which does not support validataclass default values

This PR more or less is a solution for #9.


Wyzywyg public section needs to have a media field added to be able link the media added to the content

[ ] We need to add the below media field to the wyzywyg public section this to be able link the media added to the content:
Name : wysiwygMedia
Type: Image

Acceptance testing

[ ] Wyzywig public section have the media field below added:
Name : wysiwygMedia
Type: Image

There is a discussion in issue https://gl.eweev.com/eweev/geeks/geeks_front/-/issues/208 about it


WIP: Rate mode 3d attitude control

change attitude setpoint from Euler angles to full rotation matrix to facilitate specification of arbitrary orientations
looks like a new mixer will be required to handle inverted orientations

I'm closing this for now because we have the issue of acceleration artefacts in attitude mode without GPS, and racers often have sketchy GPS (which is why we need to stop gyro bias estimation). I'm not generally rejecting the idea, but it seems like a tight tuning of the rate loop is the more robust approach.

This would be interesting to test by flying an autopilot-controlled path defined by maintaining constant roll/pitch angles and constant yaw rate (with no input from GPS). One would expect to observe changing roll/pitch angles as the attitude estimation error builds.
This is another case in which it would be nice to have mocap data to quantify actual estimation error. So far, I haven't observed significant attitude errors when flying non-GPS quads around in stabilized mode.

@LorenzMeier

sketchy GPS (which is why we need to stop gyro bias estimation)

I had no GPS installed on the S250AQ that I was using to test ACRO mode.

replaced by https://github.com/PX4/Firmware/pull/5372


Updated version

@nithinkdb If we remove -beta tag in this PR - consider also removing corresponding note in readme


Wizard/Sorcerer not using casting modifier on True Strike when first loading game

Whenever I load the game for the first time, and apparently before I take a short/long rest, both my Sorcerer and Wizard are not using their casting ability score when using True Strike.  After a rest or any sort, it seems like it works as it's supposed to.
UB Bug reports.zip

Are settings in zip? If not can you please share as well?

It is now.  At least, I THINK I did it right
UB Bug reports.zip


lovr.filechanged only gives filenames, not full paths

If you change a file a/b/c.lua in your project, lovr.filechanged only gives you c.lua as the path.
dmon file events have a dir and a path.  We need to concatenate the two and strip off the source directory.  Be careful about Windows slashes.

False alarm, this was an issue with my test code


Tests run twice

Not that it's slow, but when I make a simple change, it runs the tests twice. How does software even work?

My tests run three times currently from vim (lucky me) on OSX whenever I save a change.  Would it be worth ignoring a small window of file notification activity when receiving a change event to avoid this? (like 50/100 ms?)

That might work. Hugo has something like that in place.
I'm not a vim user, but besides modifying Spotlight Privacy settings (mentioned above), you could also try tweaking your .vimrc file. These settings are from thoughtbot's config
set nobackup
set nowritebackup
set noswapfile

Thx @nathany.  Modifying the vim config dropped one of the three.  Adding the project folder to Spotify Privacy didn't seem to have any effect.

Progress.
This is Hugo's code to batch up notifications. Not sure when I'll get a chance to implement it, but I'd welcome a pull request. :smile:
https://github.com/spf13/hugo/blob/master/watcher/batcher.go


Implemented Reflect for all the ranges

Objective
Fixes #5763
Solution
Implemented as reflect value like the current Range. Is there a benefit to changing everything to a reflect struct?

Eh actually I'll just follow up. No sense waiting around

bors r+


ANSI ESC[30m invisible in certain Terminal setups

Problems summary
If the user set terminal's background color and black color to be really similar, \x1B[30m will be hardly visible
(Example dark terminal color setup : Gruvbox Dark on Windows Terminal)
Expected
To have visible terminal outputs
Environment Information (Required!)

dein.vim version(SHA1):
33a475f
OS:
Windows (WSL)
neovim/Vim :version output:
Irrelevant. This is more related to user's terminal setup. I know we can't customize terminal colorschemes for every user, but this color collision can be avoided by simply using a color other than black for certain text. It's okay if we don't "fix" this. It's more of a user customization issue.

Provide a minimal init.vim/vimrc without plugin managers (Required!)
Irrelevant
How to reproduce the problem from neovim/Vim startup (Required!)
When installing using the installation script using
sh -c "$(curl -fsSL https://raw.githubusercontent.com/Shougo/dein.vim/master/bin/installer.sh)"

Equivalently, executing
echo -e "\x1b[30m test"

in the terminal would give the same invisible result.
Screen shot (if possible)

Upload the log messages by :redir and :message (if errored)

I've changed it to magenta to follow the color of the selection numbers, I'll be opening a PR soon.
Preview


Upgrade converter package to v3.2

Description
Upgrade converter package to version 3.2 and fix test cases to adapt to future template changes.
Related issues
Addresses [issue #].
Testing
Run unit tests and E2E tests
FHIR Team Checklist

[x] Update the title of the PR to be succinct and less than 50 characters
[x] Add a milestone to the PR for the sprint that it is merged (i.e. add S47)
[x] Tag the PR with the type of update: Bug, Dependencies, Enhancement, or New-Feature
[x] Tag the PR with Azure API for FHIR if this will release to the managed service
Review squash-merge requirements

Semver Change (docs)
Skip

@LTA-Thinking  This pull request removes unstable test results assertion from different template versions such as Id. So that future template updates will not break the tests.

@LTA-Thinking  This pull request removes unstable test results assertion from different template versions such as Id. So that future template updates will not break the tests.


fix change password in admin

I found this bug when I change password for an account, so I just fix it by changing r'^(.+)/password/$' to r'^(.+)/change/password/$'.

What is the bug?

Oh, I am sorry, I just use https://github.com/mishbahr/django-users2, and this will fail when changing password, I will close this.


adjust images' dimention

After upgrading to V2, Here is some CSS that needs to be changed：

The default font color of the navigation is #fff
the image width needs to be deleted~

Thanks~

After upgrading to V2, Here is some CSS that needs to be changed：

The default font color of the navigation is #fff
the image width needs to be deleted~

Thanks~

Hi,
[1]: The default font color of the navigation is #fff(mentioned here)
I think [1] is  a work in progress in docusaurus V2 (https://github.com/facebook/docusaurus/issues/3937)
Thanks.

After upgrading to V2, Here is some CSS that needs to be changed：

The default font color of the navigation is #fff
the image width needs to be deleted~

Thanks~

Hi,
[1]: The default font color of the navigation is #fff(mentioned here)
I think [1] is  a work in progress in docusaurus V2 (https://github.com/facebook/docusaurus/issues/3937)
Thanks.

Yes, it's related to V2.

Yes, it's related to V2.


Ensure rustc-echo-wrapper works with an overridden build.target-dir

Without this when running with an overridden target-dir there are about a dozen test failures like
> CARGO_BUILD_TARGET_DIR=not-target cargo test -- fix::does_not_crash
---- fix::does_not_crash_with_rustc_wrapper stdout ----
running `/home/nemo157/sources/cargo/not-target/debug/cargo build`
running `/home/nemo157/sources/cargo/not-target/debug/cargo fix --allow-no-vcs`
thread 'fix::does_not_crash_with_rustc_wrapper' panicked at '
test failed running `/home/nemo157/sources/cargo/not-target/debug/cargo fix --allow-no-vcs`
error: process exited with code 101 (expected 0)
--- stdout

--- stderr
error: failed to run `rustc` to learn about target-specific information

Caused by:
  could not execute process `/home/nemo157/sources/cargo/not-target/tmp/cit/rustc-echo-wrapper/target/debug/rustc-echo-wrapper rustc - --crate-name ___ --print=file-names --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=cfg` (never executed)

Caused by:
  No such file or directory (os error 2)
', tests/testsuite/fix.rs:1228:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

If the overridden target-dir is absolute this also results in rustc-echo-wrapper artifacts going into the developers main target-dir rather than under <target-dir>/tmp as intended.
Both issues are resolved by forcing the target-dir to be a manifest-relative one for this specific build.

r? @ehuss
(rust-highfive has picked a reviewer for you, use r? to override)

Thanks!  I think the issue here is that the sandbox limits aren't getting set correctly. I think something like this would be a more correct fix:
diff --git a/crates/cargo-test-support/src/lib.rs b/crates/cargo-test-support/src/lib.rs
index 1ed9bd54e..ed9e50f33 100644
--- a/crates/cargo-test-support/src/lib.rs
+++ b/crates/cargo-test-support/src/lib.rs
@@ -1209,7 +1209,7 @@ pub trait TestEnv: Sized {
             .current_dir(&paths::root())
             .env("HOME", paths::home())
             .env("CARGO_HOME", paths::home().join(".cargo"))
-            .env("__CARGO_TEST_ROOT", paths::root())
+            .env("__CARGO_TEST_ROOT", paths::global_root())
             // Force Cargo to think it's on the stable channel for all tests, this
             // should hopefully not surprise us as we add cargo features over time and
             // cargo rides the trains.

That will ensure that things like echo-wrapper don't read any configuration settings from above the cit directory.

Yep, that seems to work and makes a lot more sense.

Thanks!
@bors r+

:pushpin: Commit 61c4b11eae2223ae5efd2c09d541c0a543960f95 has been approved by ehuss
It is now in the queue for this repository.

:hourglass: Testing commit 61c4b11eae2223ae5efd2c09d541c0a543960f95 with merge a120cfe08ee826d64a5cd99ef2c1e5b52a6fefd2...

:sunny: Test successful - checks-actions
Approved by: ehuss
Pushing a120cfe08ee826d64a5cd99ef2c1e5b52a6fefd2 to master...


The Asking Questions Sample - a few questions

Here are a few questions Steve (@WashingtonKayaker) and I have about the AskingQuestions Sample.
1. About Always prompt
Does Max turn count overwrite Always prompt? Testing the Always prompt functionality in the sample and no difference found in bot's behavior b/w when it is checked or unchecked.

2. About Confirm Options
The Confirm Options section in the ConfirmInput prompt is confusing. Does ConfirmInput prompt needs Confirm Options as ChoiceInput does? Testing adding the following options and found selecting the first option will always return "confirmation: True" and the rest all return "confirmation: False".

Testing in the Emulator:

3. About Append choices
What does Append choice do in ChoiceInput prompt? What impacts will this option have when checked and unchecked? what other fields it depends on or is related to?

4. About OAuth login
The OAuth login prompt under the Ask a quesiton action. Is there any difference b/w the  OAuth login prompt under the Ask a quesiton action and the OAuth login action under the Access external resources action menu?

Thanks for the feedbacks.

InputsDialog has a feature that if you configure the Value property, for example, user.age. The InputDialog will check whether user.age has a value, if it has, then it will not prompt.
AlwaysPrompt is used to prompt an input whenever the Value property has a value.

Maxcount is not related AlwaysPrompt, it is used with defaultValue, if the user's input didn't pass the validation, it will reprompt. and if the reprompt times reaches maxcount, it will returns default value.

The choiceOptions in Confirm Input is just a way to provide alternative way to tweak the choices rendered to the user. In most cases, it is not needed to confirm that.

It looks like a schema bug, the appendChoices didn't map to any logic in the code, I will follow up on the sdk side.

the two OAuthInput are exactly the same, we may need to consider to just keep one of them.

@mareekuh @sangwoohaan  we may need UI updates for item 2 and minor change for item 4 of the duplicated fly-out menu. @luhan2017 will evaluate item 3 .

Closing this issue for now and will probably reopen it later when necessary.


RTSP Stream Grabbing?

Is there a way to grab or passthrough the rtsp streams? I see the ports are exposed on all these units from door to wall cams and the web apps have to be grabbing them somehow. It would be nice to pull those streams in and have them available.

I don't think this would be trivially possible and part of this project. From what I can tell, the firmware on these devices opens an OpenVPN connection to ADC and uses that to maintain a connection. They also randomly generate a root password and do not make it available to the end user. All of this is good from a security standpoint but makes it hard for owners to MiTM the cams :P
Breaking into your own equipment is outside of the scope of this project (we need to stay on the up and up with ADC!), but it would be in scope to set up a relay using the ADC proxy.

Notes: the web viewer makes a call to https://www.alarm.com/web/api/video/videoSources/liveVideoHighestResSources/<CAM-ID> and receives a response which includes proxyUrl under it's attributes. This proxy url can be used to view the camera live through ADC's servers.


Udemy Says : 403 Forbidden retry after few minutes

Issue number 298 is closed but this is still an issue for so many members. Pls see the comments from users. I too am facing the same issue. Updated everything and even for the first download I get the error.
[*] : Trying to login as (gopal.nayak@*****.com)...
[-] : Udemy Says : 403 Forbidden retry after few minutes ...

It works with latest update. So closing it.

it's occurring again

I use the way to solve the 400 problem,but this problem I can`t solve it


Prepare v0.11.0

Description
Prepare next release {version}
TODOs

[x] Create branch release/{version-number} from latest develop
[x] Bump version number in package.json
[x] Update CHANGELOG.md
[x] Create DRAFT release page at GH linked to release/{version-number} branch
[x] ADD release notes to DRAFT release page
[x] Sign binaries as described here and add signed message to DRAFT release page
[x] Check binaries by running on macOS, Windows and Linux
[x] Publish release

Resolved by #2151


Value is read out

Testing #107610

ubuntu20 w/ orca
navigate to "Editor: Format on Save"
:bug: it doesn't read the "value" if the setting is check or not. It reads the whole description and only when pressing enter it reads "checked" or "unchecked"

I don't know whether it should or not. Not all values can easily be read in that context (objects, arrays), some may be long, or confusing outside of the context of focus inside the control. I think it makes sense to interact with the control to get the value. @isidorn ?

For a boolean setting what Joh is suggesting makes sense, but for consistency if we do it for boolean settings we should do for all.
I suggest that for now leave this as it is. And if we also get feedback from the community that mathces this we can append the value to the top aria label.

I agree with that. Will listen for more feedback.


im pretty sure its me but im recieving this error

Traceback (most recent call last):
File "day_bot.py", line 145, in
bot.run()
File "day_bot.py", line 108, in run
count=likes_for_this_tag)
File "/usr/local/lib/python2.7/dist-packages/instagram/bind.py", line 196, in _call
return method.execute()
File "/usr/local/lib/python2.7/dist-packages/instagram/bind.py", line 182, in execute
include_secret=self.include_secret)
File "/usr/local/lib/python2.7/dist-packages/instagram/oauth2.py", line 224, in prepare_request
url = self._full_url_with_params(path, params, include_secret)
File "/usr/local/lib/python2.7/dist-packages/instagram/oauth2.py", line 148, in _full_url_with_params
self._full_query_with_params(params) +
File "/usr/local/lib/python2.7/dist-packages/instagram/oauth2.py", line 144, in _full_url
self._signed_request(path, {}, include_signed_request, include_secret))
File "/usr/local/lib/python2.7/dist-packages/instagram/oauth2.py", line 172, in _signed_request
return "&sig=%s" % self._generate_sig(path, params, self.api.client_secret)
File "/usr/local/lib/python2.7/dist-packages/instagram/oauth2.py", line 127, in _generate_sig
return  hmac.new(secret, sig, sha256).hexdigest()
File "/usr/lib/python2.7/hmac.py", line 136, in new
return HMAC(key, msg, digestmod)
File "/usr/lib/python2.7/hmac.py", line 75, in init
self.outer.update(key.translate(trans_5C))
TypeError: character mapping must return integer, None or unicode

https://help.instagram.com/contact/185819881608116


Add TokenPocket wallet support

Is your feature request related to a problem? Please describe.
No
Describe the solution you'd like
Add TokenPocket wallet into the login panel
Describe alternatives you've considered
Additional context
TokenPocket wallet injected ethereum object as metamask do. which also have  ethereum.isTokenPocket to detect with in a TokenPocket dapp browser.

@chendatony31 Thanks it should be available on our next release.

We can use this logo https://s2.coinmarketcap.com/static/img/coins/200x200/5947.png

Hi @bonustrack , please use these instead:
https://tp-statics.tokenpocket.pro/tokenpocket.png
https://tp-statics.tokenpocket.pro/tokenpocket-200-200.png

@chendatony31 Thanks do you have one with transparent background? It should fit better

How about this one?
https://tp-statics.tokenpocket.pro/tokenpocket-380.png

@chendatony31 We did the change here: https://github.com/snapshot-labs/lock/pull/22 we've used the image from the website favicon here https://www.tokenpocket.pro/favicon.png hope that works well

Ok, thanks


Expokit 32 - pendingNotification experienceId is null.

Hi,
I know this is not an issue with react-native-onesignal but I was wondering if you could offer some advice.
When opening push notifications on iOS, Expo (detached) throws an error on
- (void)userNotificationCenter:(UNUserNotificationCenter *)center didReceiveNotificationResponse:(UNNotificationResponse *)response withCompletionHandler:(void (^)(void))completionHandler {   EXPendingNotification *pendingNotification = [[EXPendingNotification alloc] initWithNotificationResponse:response identifiersManager:self];   if (![[EXKernel sharedInstance] sendNotification:pendingNotification] && [EXEnvironment sharedEnvironment].isDetached) {     _pendingNotifications[pendingNotification.experienceId] = pendingNotification;   }   completionHandler(); }
The issue is
_pendingNotifications[pendingNotification.experienceId] = pendingNotification;
pendingNotification.experienceId is null.
I have tried to pass in the data in the push notification as
curl --include \      --request POST \      --header "Content-Type: application/json; charset=utf-8" \      --header "Authorization: Basic REST_ID" \      --data-binary "{\"app_id\": \"APP_ID\", \"contents\": {\"en\": \"There are 10 games today\"}, \"headings\": {\"en\": \"Matchups are ready\"}, \"data\": {\"experienceId\": \"@login/expo-slug\"}, \"included_segments\": [\"Subscribed Users\"]}" \      https://onesignal.com/api/v1/notifications
Any idea how I can pass this data to fix this issue?

@owenhope expo push notifications and OneSignal notifications are different things and have different structures. This is more of an issue with Expo being incompatible with non-Expo push notifications.


Adding private Docker repo option for SolrCloud images

Signed-off-by: Zane Williamson<EMAIL_ADDRESS>*Issue number of the reported bug or feature request: https://github.com/bloomberg/solr-operator/issues/28
Describe your changes
Add optional ability to use a private Docker repo to store and pull SolrCloud images. Requires a predefined K8s secret to reference that is leveraged for accessing private docker repo.
Testing performed
Deployed changes to local development environment and validated image pulls from private Artifactory Docker repository.
Tested using type: kubernetes.io/dockerconfigjson Secret.
Additional context
With this change you can now publish to a private repo SolrCloud images that may contain additional plugins / Jars that your team may be using to extend SolrCloud.

Oy, Github does some automatic merge syncs. I am submitting PRs to a fork we have. Going to clean this up.


unexpected character in file names after python 3

i.e., viewer/pressure-latitude/bmodel_vs_model/bu-global/bann.html
According to @zshaheen: in Python 3, when you have a string, you need to specially convert it to a str. It’s usually a bytestring.

To be specific, the link somehow added extra characters as it should be:
i.e., viewer/pressure-latitude/### bmodel_vs_model/### bu-global/### bann.html

Fixed in https://github.com/ESGF/output_viewer/pull/13


[BUG] build_meta: prepare_metadata_for_build_wheel hook does not honor --build-option

setuptools version
setuptools==69.2.0 and wheel==0.43.0
Python version
Python 3.12
OS
Fedora Linux
Additional environment information
No response
Description
I am trying to run the prepare_metadata_for_build_wheel hook for the https://github.com/Rogdham/pyzstd project as part of the Fedora Linux build process. The project requires passing --dynamic-link-zstd when building without the in-tree zstd copy or else it fails with FileNotFoundError: [Errno 2] No such file or directory: 'zstd/lib/common/'.
I ran
python -c 'from setuptools.build_meta import *; prepare_metadata_for_build_wheel("dist", {"--build-option": "--dynamic-link-zstd"})'

and expected the build backend to pass --dynamic-link-zstd through to the internal setup.py dist_info subcommand that it calls to generate the metadata. Instead, it only passes ['dist_info', '--output-dir', 'dist', '--keep-egg-info'].
Should pyzstd be changed to allow setting this option through a different mechanism (e.g., an environment variable) or can setuptools start honoring --build-option for the prepare_metadata_for_build_wheel hook?
Relates: https://github.com/pypa/setuptools/issues/3896
CC: @Rogdham
Expected behavior
See above
How to Reproduce
Checkout https://github.com/Rogdham/pyzstd without the zstd submodule and run the command mentioned above.
Output
n/a

I will go ahead and close this issue now, since this is not a planed feature in setuptools.
If the solution mentioned in https://github.com/pypa/setuptools/issues/4293#issuecomment-2041579801 does not suit the use case, please consider contributing towards https://github.com/pypa/setuptools/discussions/4083.


Fixed compatibility with PHPStan 0.11.13

This is about: https://github.com/phpstan/phpstan/issues/2361
Please release this change. Thank you.
Closes #296

Should we raise the phpstan dependency version to 0.11.13?

Not necessary.

@nunomaduro Can you please tag a new 0.3.19 release with this change? People are reporting this error a lot :) Thank you!

Waiting for #295

No, that doesn't make sense :( Nuno said "After this feature we need to release a major version."
So if you tagged dev-master now, it would get to all users, no need to wait for additional blocking work. I'd realliy appreciate this.

I am just a janitor here, I don't even have a release checklist.

@ondrejmirtes Thanks for heads up, the version v0.3.19 is out.


Future old god unit?

https://www.hiveworkshop.com/threads/the-black-templar.239873/

https://www.hiveworkshop.com/threads/orange-centaurion.336996/