encodeURIComponent should accept any value type

TypeScript Version:  2.5.2
Code
encodeURIComponent(true);

Expected behavior:
tsc compiles with no errors.
Actual behavior:
error TS2345: Argument of type 'true' is not assignable to parameter of type 'string'.
Discussion:
encodeURIComponent is currently defined liked this:
declare function encodeURIComponent(uriComponent: string): string;

In reality, encodeURIComponent accepts any value and coerces it to a string if necessary. The first step in its definition in the ES6 spec reads:

Let componentString be ToString(uriComponent).

It’s pretty common to pass true or false or a number like 0 or 10 as a query parameter, for instance. Here are two possible ways to broaden the definition:
declare function encodeURIComponent(uriComponent: any): string;

declare function encodeURIComponent(uriComponent: string | number | boolean): string;

The any option would be technically correct, but passing null or undefined or a non-primitive value is usually a bug (in my experience). You can use your own judgment about how broadly the uriComponent argument should be defined. I’m specifically interested in using number and boolean.

Similar discussion can be found in https://github.com/Microsoft/TypeScript/issues/4002.
We have chosen to be more strict with the standard library and only allow strings, not things that can be coerced into string by the engine.

I think this is different than #4002, since it explicitly/transparently does coercion for the return value, not merely for a comparison value.
I probably never intend to do isFinite(someBoolean), but I could intend to use encodeURIComponent(someBoolean) as a shorthand for encodeURIComponent(someBoolean.toString()) since it has the same effect

Would take a PR for it.

I just ran into this when trying to encode numbers, too.
Doing something like the below code gives a compile-time error, which, as someone more used to plain JavaScript, was unexpected.
getUrl(column: number) {   return 'http://example.com/' + encodeUriComponent(column); }

Is there a way to override the declaration in the mean time?

Figured it out:
declare global {
  function encodeURIComponent(uriComponent: string | number | boolean): string;
}

@jdalrymple Do you have time to submit PR , please ?

Opened PR #31103
From this issue description:

It’s pretty common to pass true or false or a number like 0 or 10 as a query parameter, for instance. Here are two possible ways to broaden the definition:
declare function encodeURIComponent(uriComponent: any): string;
declare function encodeURIComponent(uriComponent: string | number | boolean): string;

The any option would be technically correct, but passing null or undefined or a non-primitive value is usually a bug (in my experience). You can use your own judgment about how broadly the uriComponent argument should be defined. I’m specifically interested in using number and boolean.

I opted for the first solution (using any) because it more closely matches the ES5 spec, but I see merit in @2is10’s second solution as well.


LEDDEVICE ERROR: Unknown/Unimplemented device ws2801

This is my config:
        "device" :
        {
                "name"       : "MyHyperionConfig",
                "type"       : "ws2801",
                "output"     : "/dev/spidev0.0",
                "VID"        : "0x2341",
                "PID"        : "0x8036",
                "rate"       : 1000000,
                "colorOrder" : "rgb"
        },

I do not know why I get this error. I recompiled the source on arch for arm6 on a pi zero, using the master brach. This also happens with the sample config.
But I also get this error:
Unable to load library icui18n "Cannot load library icui18n: (icui18n: cannot open shared object file: No such file or directory)"

With installing icu This error could be solved, but the main issue still exists.
It seems that -DENABLE_DISPMANX=ON -DENABLE_DISPMANX=ON was missing in make. Someone changes the default settings?
I do not know how cmake works, but this causes the error:
https://github.com/hyperion-project/hyperion/blob/master/CMakeLists.txt#L25
I tried to compile with this command as cmake:
cmake -DCMAKE_BUILD_TYPE=Release -DENABLE_DISPMANX=ON -DENABLE_SPIDEV=ON -Wno-dev ..

However I still get:
Failed to open device('/dev/spidev0.0')
I've added dtparam=spi=on to my config.txt though. I had to start hyperion as root. So this is expected I think.

What are you using to attach the LEDs ?
Are they attached to the SPI interface or via some sort of USB device ?
This config has elements of both so I can't tell which you are using.

This message is thrown when you compile without SPI?
My suggestions, please test with raspbian first. If this works, you need to search the errors on your custom build. We will never support these "customized" builds, cause it might be a never ending story for us.
If you compile your own system, deal with it! Might be harsh but what shall we do?

Yes I am using SPI. And no I do not use a customized build. The only difference is that I am using Arch and that the cmake does not recognize that I am compiling for a raspberry pi, so it leaves out the SPI lines. This should get fixed. However I cannot find the reason why this happens. I provided as much information as I could. Please reopen.

you should compile with:
cmake -DCMAKE_BUILD_TYPE=Release -DPLATFORM="rpi" ..
there is no error. You found the right line in code ...

mh, documentation never updated here.

Ah, I see. That makes sense. Ive added it here:
https://github.com/hyperion-project/hyperion/pull/706/files#diff-827d5b5e6ae90ff76f6633a1714d7ac1


Simplyfing Twig Filter and Function setup

Iterating over arrays instead of calling new Twig_SimpleFunction for each
Moving helper functions out to TimberTwigHelper
Using factories for TimberObjects instead of repeating same factory

A couple of years later we arrived at the same conclusion in #2408. Thanks for being ahead of the times!

A couple of years later we arrived at the same conclusion in #2408. Thanks for being ahead of the times!


Compatibility Tips for TensorFlow-1.4.0

I use python2.7,tensorflow==1.4.0.
The error is :
me: GeForce GTX 1080 Ti, pci bus id: 0000:01:00.0, compute capability: 6.1)
Traceback (most recent call last):
File "thumt/bin/trainer.py", line 466, in
main(parse_args())
File "thumt/bin/trainer.py", line 459, in main
sess.run_step_fn(restore_fn)
AttributeError: 'MonitoredSession' object has no attribute 'run_step_fn'
We look forward to your reply.Thank you very much.

2018-04-12 13:10:28.825845: I tensorflow/core/platform/cpu_feature_guard.cc:137] Your CPU supports instructions that this TensorFlow binary was not compiled to use: SSE4.1 SSE4.2 AVX AVX2 FMA
2018-04-12 13:10:29.011996: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1030] Found device 0 with properties:
name: GeForce GTX 1080 major: 6 minor: 1 memoryClockRate(GHz): 1.7335
pciBusID: 0000:03:00.0
totalMemory: 7.92GiB freeMemory: 7.81GiB
2018-04-12 13:10:29.012047: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1120] Creating TensorFlow device (/device:GPU:0) -> (device: 2, name: GeForce GTX 1080, pci bus id: 0000:03:00.0, compute capability: 6.1)
Traceback (most recent call last):
File "thumt/bin/trainer.py", line 468, in
main(parse_args())
File "thumt/bin/trainer.py", line 461, in main
sess.run_step_fn(restore_fn)
AttributeError: 'MonitoredSession' object has no attribute 'run_step_fn'
I have encountered the same error .

@KelleyYin  Have you solved it?

Upgrading TensorFlow to the latest version will eliminates this error.

@Playinf
Thank you for your reply.
1.The latest version of tensorflow needs cuda9.0, and my Ubuntu server is cuda8.0.
2.I saw the branch of github has updated 'Minor changes', so what branch should I use?

@Playinf
Thank you for your reply.
1.The latest version of tensorflow needs cuda9.0, and my Ubuntu server is cuda8.0.
2.I saw the branch of github has updated , so what branch should I use?

You may find commit 2f5c2881220b6f81f864cf045783f062b6022e38 helpful.

Sorry, the commit 7956f2a52aea2b83f5f237d9e496b58dcb8e1626 is the latest one that support TensorFlow 1.4.0.
You can also use the following patch codes with the latest commit:
        # Create session, do not use default CheckpointSaverHook
        with tf.train.MonitoredTrainingSession(
                checkpoint_dir=params.output, hooks=train_hooks,
                save_checkpoint_secs=None, config=config) as sess:

            sess._tf_sess().run(restore_op)

            while not sess.should_stop():
                sess._tf_sess().run([init_op, ops["zero_op"]])
                for i in range(update_cycle - 1):
                    sess._tf_sess().run(ops["collect_op"])

                sess.run(ops["train_op"])

@Playinf Thank you very much. This problem has been solved.

@renhongkai Can you tell me how you solve this problem? I met the same thing 'AttributeError: 'MonitoredSession' object has no attribute 'run_step_fn''. After I use the patch code Playinf describes, it can only run 1 step and then another error ocuured.

@rgwt123 I have tested the patch codes under TensorFlow-1.4.0 and do not found any problems.

We recommend users to use the latest version of TensorFlow. We may drop the compatibility of old TensorFlow versions without notice.


Removed display of schemaVersion field wile still keeping its value u…

Major:

Removed display of schemaVersion field while still keeping its value updated in JS and data.

It was deemed unnecessary to encumber the form with a field the user has no control over and wouldn't mean anything to it anyway.

Minor:

Added comments to empty cases in loops for better consistency in markup.

Plz review & squash+merge


Enhancement: Analog to play Air Hockey games

I think D-Pad is not suitable for playing Air Hockey
Arthur's Absolutely Fun Day! (GBC): Air Hockey Antics LOLFest!!!
Gta 4 Air Hockey minigame

Someone else already suggested this in #54.


im i doing some thng wrong here????

Challenge Link to External Pages with Anchor Elements has an issue.
User Agent is: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36.
Please describe how to reproduce this issue, and include links to screenshots if possible.
 I have the right code, yet when i hit submit nothing happens.

It's simple just rest the challenge and write it again

This didn't work for me.

Had to perform a hard refresh a couple of times.


Application Architecture Design

Pseduo-code:

Create New SQL connection (from a class)
Create New HTML builder class
Load new array of reports (ID 1..32, with corresponding columns to include, SQL command)

Loop (size of array) do

run query defined in array against SQL object
filter based on array parameters
pass result of SQL results to HTML object so it can produce a standard report (it will output a string with the report)
Save the result of the HTML builder to an actual file (e.g. report_16.html)
end loop

Defer this until after coursework is submitted for ideas and input.

New application structure discussed and implemented. Closed out.


Added more properties to PaginatedDataTable2 and AsyncPaginatedDataTable2, fixed tests

Added dividerThickness
Added renderEmptyRowsInTheEnd (It won't render empty rows in the end of the Table when set to false)
Fixed cross platform goldens images comparison for tests, by adding custom fonts based on this

@maxim-saplin It seems that adding custom fonts while running tests it doesn't help a lot, matchesGoldenFile keeps failing.

Uploaded new Goldens, PR should work. Here's side-by-side comparison, macOS renders fonts bold

Codecov Report
Base: 96.51% // Head: 96.52% // Increases project coverage by +0.00% :tada:

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

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #159   +/-   ##
=======================================
  Coverage   96.51%   96.52%
=======================================
  Files           3        3
  Lines        1062     1065    +3
=======================================
+ Hits         1025     1028    +3
  Misses         37       37

Impacted Files
Coverage Δ

lib/src/async_paginated_data_table_2.dart
85.51% <ø> (ø)

lib/src/paginated_data_table_2.dart
97.86% <100.00%> (+0.02%)
:arrow_up:

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.

There's a minor bug with renderEmptyRowsInTheEnd, pagination shows incorrect number of rows on the page when page size is greater than available number of rows:

@maxim-saplin I just made a small change that will take into consideration renderEmptyRowsInTheEnd when showing the footer info title. By the way I've been testing renderEmptyRowsInTheEnd with different properties combinations and had no issues so far.

@maxim-saplin You know that you closed it instead of merged it?

Oops.. Thanks for noticing. Though I've already pushed the new version to pub.dev)


⚠ Bofrost.be has degraded performance

In c8f0730, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 863 ms

Resolved: Bofrost.be performance has improved in 98350e4.


BUG2-1182-fix: hide non functional attribute update

Some blind drivers have exposed unnecessary information to history. (bug2-1182)
modify the aqara and hansem blind drivers not to show some events
(for supportedWindowShadeCommands, supportedInitializedState)

Could you fix https://github.com/SmartThingsCommunity/SmartThingsEdgeDrivers/blob/8639f88e40e9245cbca67a8e21a82cff0d7488f7/drivers/SmartThings/matter-window-covering/src/init.lua#L77 as well which has the same issue?

Could you fix
https://github.com/SmartThingsCommunity/SmartThingsEdgeDrivers/blob/8639f88e40e9245cbca67a8e21a82cff0d7488f7/drivers/SmartThings/matter-window-covering/src/init.lua#L77
as well which has the same issue?

@tpmanley I added an additional commit for matter window covering. Please review it again


Error when running generate with --steps

fixes #109

Can the warning also cause issues? If yes, I will just remove the else entirely.

I think it's better to release a patch as soon as possible as KPOps is supposed to be stable now.

I don't think anything is really broken. Just the behavior was different some time ago. But if people are just starting to use it now, all is fine

I don't think a quick fix is needed. Just #110 :-)

@sujuka99 I agree with @philipp94831. The fix for this bug is implementing #110. As far as I know. None of the projects are facing this bug now. You can go ahead and merge this because I still think that throwing an exception is unnecessary.


fix: protobuf version not always getting set in headers

In order to maximize amount of times protobuf version is logged we have updated logic as follows:

First try to use protbuf RuntimeVersion which is available in protobuf 4.x
if not available try to read using manifest file
if manifest file doesn't not exist then default to "3" as we know runtime < 4

Tested:

maven build using client library directly and overriding protobuf
spring boot started project + google cloud storage client client lib, validated that protobuf header was sent

LGTM. Blake for approval.


Push main to live

Docs Build status updates of commit 99f9596:
:warning: Validation status: warnings

File
Status
Preview URL
Details

BingMaps/coverage/transit-coverage/europe.md
:warning:Warning
View
Details

BingMaps/coverage/transit-coverage/africa.md
:bulb:Suggestion
View
Details

BingMaps/coverage/transit-coverage/asia-australia-pacific-islands.md
:bulb:Suggestion
View
Details

BingMaps/coverage/transit-coverage/index.md
:bulb:Suggestion
View
Details

BingMaps/coverage/transit-coverage/north-america.md
:bulb:Suggestion
View
Details

BingMaps/coverage/transit-coverage/south-america.md
:bulb:Suggestion
View
Details

BingMaps/getting-started/bing-maps-dev-center-help/understanding-bing-maps-transactions.md
:bulb:Suggestion
View
Details

BingMaps/rest-services/traffic/index.md
:bulb:Suggestion
View
Details

BingMaps/coverage/geographic-coverage.md
:white_check_mark:Succeeded
View

BingMaps/getting-started/bing-maps-api-best-practices.md
:white_check_mark:Succeeded
View

BingMaps/v8-web-control/developer-resources.md
:white_check_mark:Succeeded
View

BingMaps/coverage/transit-coverage/europe.md

Line 608, Column 14: [Warning: file-not-found - See documentation] Invalid file link: 'http://www.Autocars_S.A.S.A.I.B..com'.
Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

BingMaps/coverage/transit-coverage/africa.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

BingMaps/coverage/transit-coverage/asia-australia-pacific-islands.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

BingMaps/coverage/transit-coverage/index.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

BingMaps/coverage/transit-coverage/north-america.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

BingMaps/coverage/transit-coverage/south-america.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

BingMaps/getting-started/bing-maps-dev-center-help/understanding-bing-maps-transactions.md

Line 2, Column 1: [Suggestion: description-missing - See documentation] Missing required attribute: 'description'.

BingMaps/rest-services/traffic/index.md

Line 18, Column 2: [Suggestion: column-header-missing - See documentation] Column headers are required for tables. Add appropriate header text, or remove any extra table cells that cause an extra column.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Develop a DSL for specifying DyNet networks

The strength of Racket is its support for advanced DSL design. This should be used to develop a facility to easily specify network architectures.

Yes.


Sidewise regulary miss tabs and focuses url-bar

Regulary, after long time use and complex browsing, Sidewise loses tabs and sets every second focus on Chrome-url-bar. I have 200 tabs.
Only reopen Chrome helps to restart Sidewise and remove problems.
Sometimes tabs not opening on mouse click, however they exists and can be clicked from Chrome tabs.
Sometimes Chrome urlbar is focused every second, so its imposible even to use other applications in Windows.

Chrome urlbar is focused every second?  To regain missing tabs click on the "emergency restore" in the advanced options.


Make all h2s on "What is Health Equity" page Taviraj Light

Closes #830
Pinged Chi for more details on how far this should be applied (to lower level headers, site wide, etc.)  Will update accordingly.

For some reason there were two FAQ sections in the previous version of this
file, I consolidated them back into one.
On Sat, May 15, 2021, 10:29 AM vanshkumar @.***> wrote:

@.**** commented on this pull request.
In
frontend/src/pages/WhatIsHealthEquity/WhatIsHealthEquityPage.module.scss
https://github.com/SatcherInstitute/health-equity-tracker/pull/864#discussion_r632985537
:

@@ -385,58 +438,3 @@
text-decoration: underline !important;
}
}

-/** ------------- FAQ ------------- **/
-.FaqGrid {
I don't think you actually changed any of these FAQ styles, right? What's
the reason for moving them?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/SatcherInstitute/health-equity-tracker/pull/864#pullrequestreview-660375998,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEULCIB5OOCG4U3ZVJLNLKLTN2VO5ANCNFSM445ON3XQ
.


Add HelixUser#getFollowers method

There is no way to get followers from HelixUser class, but, I think, it's a great case of use

This pull request doesn't meet any of the requirements shown in the pull request template or contributing guidelines.


Brackets 1.8 - Brackets Git failed to connect to NodeJS

Description

[Description of the bug or feature]
Steps to Reproduce

Just open Brackets 1.8 with Brackets-git plugin

Versions
Windows 10
Brackets 1.8

Fix this trough reinstall brackets and brackets-git

Happy to hear you were able to fix it.
Closing as extension problem.


Downmerge main to dev after script updates

Scripts were updated directly to Main. Downmerge changes to dev.

Remove SwiftFormat from project.
As SwiftFormat is not automatically installed like SwiftLint is, customers can get build failures.

Add required 'getHistoricalEvents' method to TestableExtensionRuntime

Remove leading whitespace from run script.

Update CircleCI Xcode image to 12.0.1

Remove SwiftFormat

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

@kevinlind do you know why the coverage dropped to 55%?

@kevinlind do you know why the coverage dropped to 55%?

No, I haven't figured this out yet. From the percentage, it looks like it's only counting the unit test coverage and ignoring the functional test coverage. I did notice the Xcode project did not have coverage enabled for the AEPAnalytics or AEPAnalyticsFunctionalTests schemes, but that didn't make a difference when enabling coverage in Xcode and kicking a build.
I don't see any errors in the build for the Codecov step. The Codecov logs do state it found and uploaded the coverage reports for AEPAnalytics, AEPAnalyticsUnitTests, and AEPAnalyticsFunctionalTests. However, in Codecov, the build logs show the source files from the functional tests all with line coverage of 0.
https://codecov.io/api/gh/adobe/aepsdk-analytics-ios/download/build?path=v4/raw/2022-02-15/4D7DD0C282C336E085570C6546B826B8/3b4fe70f862c62db9da5129626359d7535173191/7743c041-b260-4dca-9225-79130977d96f.txt

Coverage to be fixed in https://github.com/adobe/aepsdk-analytics-ios/pull/63, merging.


Update README.md

Grammar mistake in the documentation

Thank you very much for your contribution, although I feel the previous wording looked fine as well.


Split the proposal into two separate sections: one for the API and one for JAX-RS transport

To ensure that the spec has broader applicability the JAX-RS specific aspects of the API need to be pulled out into a separate section.
This change would also enable a cleaner definition of the wire protocol with the main option being JAX-RS and in particular would provide a natural place to document how participants running against one implementation of this specification can register with other implementations (see #17).

Hi Michael,
Current in ServiceComb-Saga implementation, we just use GRPC to send events coordinator, here are our design document for it.  I think we can work together to polish the specification.

We discussed this issue at the last hangout and the consensus (Emily and myself) was that we should start with smaller steps and target the initial proposal towards the baseline JAX-RS. I therefore would like to close this issue as will not fix.
Support for other protocols such as gRPC can be supported using vendor adaptors.

@zhfeng I withdrew PR jbosstm#5 since the plan is to keep the dependency on JAX-RS in the initial MP LRA proposal. We can still interoperate with other models by providing an adaptor component to proxy the two models. Tom came up with a technique for doing this on issue #17 which I think would make sense to include in the SmallRye implementation.


Delete button turns white after first touch

Hello,
I noticed an issue where the back button changes to white when I tap it. This is problematic because I'd like to have a white background. I'm attaching three screenshots that show the keypad before I enter anything, after I've entered three numbers, and after I've pressed the delete button one time. I turned the background color blue to show what I mean.
Before

During

After deleting one

Any ideas? Thanks!

how to fix this?

Create ic_delete.xml in drawable.
<vector xmlns:android="http://schemas.android.com/apk/res/android"      android:width="55dp"      android:height="45dp"      android:viewportWidth="55.0"      android:viewportHeight="45.0">  <path      android:pathData="M53.42,2L18.27,2C16.67,2 15.29,2.68 14.38,4.05L2,22.5L14.38,40.95C15.29,42.09 16.67,43 18.27,43L53.42,43L53.42,2Z"      android:strokeColor="#000000"      android:fillColor="#00000000"      android:strokeWidth="3"/>  <path      android:pathData="M37.95,16L25,28.5"      android:strokeLineCap="square"      android:strokeColor="#000000"      android:fillColor="#00000000"      android:strokeWidth="3"/>  <path      android:pathData="M37.5,28.95L25,16"      android:strokeLineCap="square"      android:strokeColor="#000000"      android:fillColor="#00000000"      android:strokeWidth="3"/> </vector>

Set keypadDeleteButtonDrawable to PinLockView
 app:keypadDeleteButtonDrawable="@drawable/ic_delete"

I think this issue needs to be looked for @aritraroy

A quick fix to this problem is mPinLockView.setDeleteButtonDrawable(getResources().getDrawable(R.drawable.ic_backspace_pin)); //delete button drawable
Be sure to import a backspace icon which has the color you want for the backspace button.


Version compatibility broken

From git blame I can see that 4 months ago the perform method has changed signature.
It's an API change of a public method, so the major version of pac4j should be increased because of that.
Especially important due to the fact that it is used in bujio project.
reference:
https://github.com/pac4j/pac4j/blob/da8a9c258a75f3faff813005f312bbbfbe370a20/pac4j-core/src/main/java/org/pac4j/core/engine/CallbackLogic.java#L29

The 2.x version API has remained stable, only the master (v3.x) has been changed. I'm not sure to see the issue here.


Orwellian Lawset

About the PR
Added Orwellian Lawset to the game.
Why / Balance
Allows for additional roleplay interactions with the AI as well as a tool admemes and admins can use to further gimmicks in a round. Can be used by security for crackdowns on crime in a dystopian manner. Also a nice nod to 1984. I noticed there was not a proper 1984 lawset in the game already, and decided it would be fun to make one myself.
Technical details
-Added Orwellian law board item to silicon.yml
-Added Orwellian law order and ID to silicon-laws.yml
-Added Orwellian laws to laws.ftl
Media

(It's impossible to display the AI's law list on singleplayer as AI's laws cannot update until the AI has been activated, and the AI's laws cannot be updated after being activated as taking control of the AI breaks after switching control.
Requirements

[X ] I have read and am following the Pull Request and Changelog Guidelines.
[X ] I have added media to this PR or it does not require an ingame showcase.

Breaking changes
No breaking changes.
Changelog
:cl:

add: Added Orwellian Lawset!

Note that there is also an AI lawset freeze as of the moment, #31924. This PR (and a bunch of others) will stay closed until the specifics in the linked issue are worked out.


Fix typo in MainMenu.xib

"Select an Enahancement" -> "Select an Enhancement"

I'm not that familiar with Xcode project structure, so I'm not sure if this needs to be changed in another place.


PlantUML Preview

Preview window has no scrollbars. Large diagrams have to be rendered to image before being able to preview.

hmm...
I couldn't resolve this issue.
My implementation is VS Code extensions sample code.
Do you have idea what resolve this issue?

Occasionally the scrollbars appear. Mostly not, I can however use the middle mouse button to pan left and right so its not unusable. Great plugin though...

Hi,
I have installe dthe extension on my VScode.
I got "command 'extension.previewplantuml' not found" when I run "PlantUML preview".

Extension Installed
JAVA_HOME created
PLANTUML_JAR created
GRAPHVIZ_DOT created

@llagit please create new issue.

I improved scroll experience.
You can scroll use the wheel and middle mouse button.
But, doesn't show scroll bar...


Do we need to support async requests?

We have async request functionality here. Not having worked with async much, I have questions:

what is the main use case?
can we do without it?

My guess at the first is: it helps when making many requests in parallel. My guess at the second is: yes, we don't have that functionality in epidatr and that client works well enough.
Removing async support would reduce maintenance work and would allow us to switch completely to delphi-epidata.py as the backend (see #29).
There is an async smoke test here and a regular one here. Those could provide some good examples to get started in testing.

Found some discussion from a while ago.

Also this issue.

TL;DR of above issues:

async calls were originally intended to get around row limits and pagination in the old PHP server
current row limits are much larger and we don't do pagination, thus this feature is no longer necessary
async it will be deprecated in covidcast client and eventually downstream code will stop using it
we can therefore remove this functionality here and simplify the code, this work will happen here #28

Closed by #28


dotnet test publish results - duplicates previous tasks' results

Create two test projects
Create build task dotnet test proj1.tests.csproj with publish enabled
Create build task dotnet test proj2.tests.csproj with publish enabled
Run build
Results from proj1.tests.csproj are published twice

Log for step 2 looks like this:
2018-02-21T14:51:44.4918390Z Results File: D:\a\_temp\VssAdministrator_factoryvm-az265_2018-02-21_14_51_43.trx
2018-02-21T14:51:44.9541003Z ##[section]Async Command Start: Publish test results
2018-02-21T14:51:45.0399232Z Publishing test results to test run '258'
2018-02-21T14:51:45.0399456Z Test results remaining: 202. Test run id: 258
2018-02-21T14:51:45.6759084Z Published Test Run : xxxxxxxxxxxxxx
2018-02-21T14:51:45.6759464Z ##[section]Async Command End: Publish test results

Log for step 3 looks like this:
2018-02-21T14:52:03.4059924Z Results File: D:\a\_temp\VssAdministrator_factoryvm-az265_2018-02-21_14_52_02.trx
2018-02-21T14:52:03.5848043Z ##[section]Async Command Start: Publish test results
2018-02-21T14:52:03.6071384Z Publishing test results to test run '259'
2018-02-21T14:52:03.6071535Z Test results remaining: 202. Test run id: 259
2018-02-21T14:52:03.9313838Z Published Test Run : xxxxxxxxxxxxxx
2018-02-21T14:52:08.1417901Z Publishing test results to test run '260'
2018-02-21T14:52:08.1418097Z Test results remaining: 83. Test run id: 260
2018-02-21T14:52:08.5283796Z Published Test Run : xxxxxxxxxxxxxx
2018-02-21T14:52:08.5284410Z ##[section]Async Command End: Publish test results

Seems that when the task is flagged to publish the results, it publishes D:\a\_temp\*.trx instead of just the trx's from the task? Just a guess.

Looks like a likely candidate!
https://github.com/Microsoft/vsts-tasks/blob/1bde6b9a7d857112f84c89b5dd4357a88022ab0b/Tasks/DotNetCoreCLI/dotnetcore.ts#L141

Workaround:
Disable publish test results for all but last dotnet test command.

Just realised...
That workaround doesn't work..
https://github.com/Microsoft/vsts-tasks/blob/59fe6dd129d8e1462dcd6361a417acbaccb8b1f0/Tasks/DotNetCoreCLI/dotnetcore.ts#L103
The .trx file will only get generated if the Publish test results option is ticked!

I guess simplest fix would be to just remove line 103. This would make it create the report regardless.
However I suppose creating the report is a somewhat expensive operation?
Or I guess you could change https://github.com/Microsoft/vsts-tasks/blob/59fe6dd129d8e1462dcd6361a417acbaccb8b1f0/Tasks/DotNetCoreCLI/dotnetcore.ts#L101
so it appended a random directory then you call tp.mkDirP() or whatever.

Just seen this issue is like 100 years old.
Come on guys. https://github.com/Microsoft/vsts-tasks/issues/5924

@Mardoxx Sorry for the trouble. We are acknowledging that it's a bug. We couldn't prioritize it.
We welcome your contributions :)
Ideal fix is to delete ***.trx files before running the test command - https://github.com/Microsoft/vsts-tasks/blob/1bde6b9a7d857112f84c89b5dd4357a88022ab0b/Tasks/DotNetCoreCLI/dotnetcore.ts#L103

Does rmRF() support minmatch?

Creating a bug to track internally and will be fixed soon. Closing this thread


feat: use DISPATCH action type instead of overloaded TEXT action

depends on UI generating these actions since they can't be manually created or edited.
Updates the GetHistory function to return the card placeholders similar to the SET_ENTITY actions.
ActionDetailsList

ActionCreatorEditor

Card Placeholder in Train Dialogs:

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

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add: tsconfig.json

This configures TypeScript and tells it to look at JS files as well, so that IDEs like VSCode can provide better edit-time checks.
This works especially well in VSCode with the ErrorLens extension which shows problems inline.
Problems with typings can be resolved by adding JSDoc comments (for which homer0 has an excellent Prettier plugin) or straight-up *.d.ts files, which will be used by the editor but otherwise don't impact the build at all.
This is a stepping stone towards TypeScript support, allowing a gradual conversion. Personally I use TS very sparingly, rely extensively on JSDoc and have great expectations for the types proposal.

Cool thanks!


Fix readme

README is in a bad state. There is redundant content.  Please clean up.

Thanks for the heads up, we'll get this cleaned up.  This likely happened in with the merge conflict in a3dfa3d.

This looks fixed as of commit 95c655b?

Done & tested.


docs(version): update CDN references and Angular docs

Updated repo README.md to include reference to correct CDN location of ngOfficeUIFabric & Office UI Fabric CSS files.
Also updated README.md to include details about the state of the project (ng1, ng2, ng4, etc).
Fixes #489. Fixes $494.

Coverage remained the same at 97.771% when pulling d1dbab8e7a5200f08176bbc5683370600a831ab2 on andrewconnell:issue489-docVersionUpdate into 868a9d7f240cc5b3f3d44296eed21f0f5e3f339d on ngOfficeUIFabric:master.

Coverage increased (+0.7%) to 98.498% when pulling d97d1b0f8c3170f14c3a228401dd2ae76af00d87 on andrewconnell:issue489-docVersionUpdate into 868a9d7f240cc5b3f3d44296eed21f0f5e3f339d on ngOfficeUIFabric:master.

Coverage increased (+0.7%) to 98.498% when pulling 0219e422097f02a3f7ed5e5244836600f3565606 on andrewconnell:issue489-docVersionUpdate into 868a9d7f240cc5b3f3d44296eed21f0f5e3f339d on ngOfficeUIFabric:master.

Coverage increased (+0.7%) to 98.498% when pulling 806b5d9251f80c2d9a506f0a758304c2a460b720 on andrewconnell:issue489-docVersionUpdate into 868a9d7f240cc5b3f3d44296eed21f0f5e3f339d on ngOfficeUIFabric:master.


how to use the DeployAVDSessionHostReplacer.bicep for deployment

I'm trying to use the bicep for deployment, since i need to add some custom code for running custom scripts, as well as deploying other vm extensions on the host.
there isn't much documentation on this, other than the readme, which i tried, but got errors:
 |  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 | 12:34:24 - Error: Code=InvalidTemplate; Message=Deployment template
 | validation failed: 'The template resource 'deployFunctionApp' at line
 | '390' and column '9' is not valid: The language expression property
 | array index '2' is out of bounds.. Please see
 | https://aka.ms/arm-functions for usage details.'.

in the deploy/bicep/DeployAVDSessionHostReplacer.bicep
it calls
module deploySessionHosts 'modules/AVDStandardSessionHost.bicep' = [for vm in VMNames: {
which references
deployStandardTemplateSpec.bicep
../../../StandardSessionHostTemplate/DeploySessionHosts.json
What steps am i missing to deploy the bicep, instead of the arm?

Any updates on this?  i need to customize the solution, and after i do, and run the Build deployAVDSessionHostReplacer bicep file into ARM action, and attempt to deploy, i get the error in the previous post

Hey! I am working on a new version (Currently in beta but not quiet ready yet) that will allow you to easily use your own template. Would you like to be the first one to test it?


Fix double escaping of dttm expressions

If ddtm_expr is an expression with special characters then timestamp_grain escapes
the special characters already escaped.
Solution discussed with sqlalchemy upstream:
https://bitbucket.org/zzzeek/sqlalchemy/issues/3737/literal_column-given-a-specific-sql
Fix #617

LGTM


Corrupt save games

Everything worked fine until for some reason loading any save game made after what seems to be a loadable file. The next save game made with it will crash after a few seconds when loading it.
https://pastebin.com/5UAmfhUR - Crash log
https://pastebin.com/tpBcXj7n - JContainers64.log
Hopefully the file "__delete_if_empty" made by Vortex mod manager inside JCData folder isn't causing issues, as everything worked fine before.
I'm using the version that came with mod VioLens, it has version 4.0.1b of JContainers64. I tried re-installing but that did not help. It is the only mod that is actively using it.
If I save indoors where I saved already, the save game is fine. If I go outside to save, that save game refuses to load.
Edit: I did those steps in order and the log is different and comes with some garbled text when the save is loaded.
https://pastebin.com/RkmuvaMJ
Completely deleting all folders associated and installing JContainers64 outside of the mod manager seems to be working fine. Those spare files inside the working directory for the plugin seem to be the cause, but what is strange the issue only appeared after a number of saves, rather than immediately.
Regardless, I have sent a bug report to the Vortex team.

Hi @Forgemaster thanks for your report. If I'm getting it right, issue is fixed by installing JC outside of this Vortex manager? I didn't understand well the situation with these "spare" files - which ones? You removed them or left them? One thing which comes to mind to be likely pecular is that JC includes one dummy file inside an otherwise empty folders - this is to force Nexus Mod Manager installing that folder and avoid issues/crashes.

Are these Vortex files empty? At best I can see whether JC can ignore empty or not well formatted domains...

Hi @Forgemaster, I have added small workaround. JC will ignore any files with two leading underscores. This looks safe enough. So it may do. Better solution would be to add real JSON validation, but this may introduce some resource usage which in general I would like to avoid. After I do #18 I'm going to release new version, so you may compile as it is now from the develop banch or wait a bit.

P.S. You can try now the release with workaround at https://github.com/ryobg/JContainers/releases/tag/v4.1.0

Hi! I have uploaded here a build with more elaborated procedure for domain population. I believe it should work, but you can try throw at it whatever junk you may find.

So I think this should be solved now. JC should consider only folders. Let hope that sombody does not decide to put and  junk folders inside. In any case, if this issue persist, feel free to reopen.


fix spelling of 'iff' and 'idenifier'

@hikerpig,
Thanks for your contribution.
To ensure that the project team has proper rights to use your work, please complete the Contribution License Agreement at https://cla.microsoft.com.
It will cover your contributions to all Microsoft-managed open source projects.
Thanks,
Microsoft Pull Request Bot

@hikerpig, thanks for signing the contribution license agreement. We will now validate the agreement and then the pull request.
Thanks, Microsoft Pull Request Bot

Sometimes we use "iff" in the meaning of "if and only if"
(see https://en.wikipedia.org/wiki/If_and_only_if)
But some of the comments looks bogus to me.

@weinand  Thanks for your note. So I check again and see many of them looks just like typos, then I got the meaningful comments back in the next commit


buildPythonPackage , buildPythonApplication: take installCheck-related attributes directly

Description of changes
This PR enables buildPythonPackage and buildPythonApplicaiton to directly take the installCheck- related attribute instead of specifying it using check- associated arguments.
This is the first and backward-compatible step toward simplifying the installCheck-related attribute specification for Python packages and applications.
In the long run, we should deprecate the use of checkPhase to specify installCheckPhase, and use installCheckPhase directly, as stated in the mk-python-derivation comment four years ago.
Cc: @FRidh
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[X] Fits CONTRIBUTING.md.

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

I believe to understand the distinction between checkPhase and installCheckPhase in the meaning of the stdenv chapter in the manual. What I don't understand is why Python adopted one over the other, and what the motivation and benefit of rolling that decision back is.

@mweinelt The issue is that we are

specifying the installCherkPhase attributes using the checkPhase arguments of buildPython* and
pretending that we are using checkPhase in the corresponding section of Nixpkgs Manual.

It is not about the choice between chcekPhase and installCheckPhase, but to inform the choice to users of the bud helpers.

Why then not move us into checkPhase if it is all the same? I don't see the value in adopting another lingo when a whole bunch of packages have already adopted it.

That's indeed another way to go.
The decision to implement doCheck with  doInstallCheck dates back to 2016, in commit 3e05cce97ca3ea9eee42a17c8bc0b89345b5d0b6 made by @FRidh in #18143. The comment mentioning the long-term goal to move to installCheckPhase was added in 2019 in commit f7e28bf5d8181926e600a222cb70180519d09726.

The issue is that we are

specifying the installCherkPhase attributes using the checkPhase arguments of buildPython* and
pretending that we are using checkPhase in the corresponding section of the Nixpkgs Manual.

It is not about choosing between chcekPhase and installCheckPhase but about informing users of the build helpers about this choice.

The manual notes that checkPhase is used instead of installCheckPhase.
However, I do not know why we adopted checkPhase and not installCheckPhase as it was.
Perhaps because installCheckPhase was rarely used and unfamiliar to most people?

The checkPhase for python maps to the installCheckPhase on a normal derivation. This is due to many python packages not behaving well to the pre-installed version of the package. Version info, and natively compiled extensions generally only exist in the install directory, and thus can cause issues when a test suite asserts on that behavior.

https://github.com/NixOS/nixpkgs/blob/master/doc/languages-frameworks/python.section.md#testing-python-packages-testing-python-packages

I get that installCheckPhase runs post-install and is more useful for the reasons mentioned.
The frustrating thing here is, that we simplified the lingo to build-system and dependencies, only to move from checkInputs to nativeCheckInputs, and now to nativeInstallCheckInputs. I get that all of these bits and pieces have meaning, but we'll be dealing with the resulting churn for the next two releases at least.
And then there is the matter of nix-community/nix-init#419 🫠

Build system and dependencies are essentially another layer on top. The underlying stdenv atttributes will always be needed for all other cases.
I think motivation at the time was consistency. Probably it was not given much thought.

After some thought, I'm personally against the migration to installCheckPhase for now.
It has been over six months since we started the switch to build-system/dependencies, and this migration is painful.
Indeed, this change is correct and should be done to ensure consistency with the phase definition.
However, it will be more difficult to encourage contributors to migrate just for that reason, even if it is backwards compatible.
Regarding installCheckPhase, I feel that many of its functions have delegated passthru.tests, such as tester.testVersion.
It is no exception in python, where https://github.com/NixOS/nixpkgs/pull/272177 tries to separate build and test.
I don't know how it will finally be implemented, but it seems that it would be less burdensome if this PR change were adopted at the same time as the separation.

After some thought, I'm personally against the migration to installCheckPhase for now.
It has been over six months since we started the switch to build-system/dependencies, and this migration is painful.
Indeed, this change is correct and should be done to ensure consistency with the phase definition.
However, it will be more difficult to encourage contributors to migrate just for that reason, even if it is backwards compatible.

Thank you for sharing your precious experiences about attribute renaming.
Your right. The change wouldn't be helpful to the community if the pain caused by the mass renaming outweighs the benefits of the name correctness.

Regarding installCheckPhase, I feel that many of its functions have delegated passthru.tests, such as tester.testVersion.
It is no exception in python, where #272177 tries to separate build and test.
I don't know how it will finally be implemented, but it would be less burdensome if this PR change were adopted at the same time as the separation.

Delegating checks to passthru.test (as package tests) sounds like the right way to go. Let's push that one first.
If this is not the change we want to make now, should we close this pull request or mark it as a draft?


[Bug]: rustdesk binary is downloaded and put in the path, but it isn't installed

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
rustdesk
Expected/Current Behaviour
Hi everyone,
I'm going to install rustdesk via puppet to all my colleagues using windows.
After installing rustdesk with the --global option, the binary is downloaded and available for execution, but if you'd look in the bottom left corner, there is a message which tells you the program isn't installed. This restricts the options for proper remote control rather badly. For instance, you can't do anything as administrator.
Steps to Reproduce
It's the default behaviour

Possible Solution
According to the manual, you can install it by executing it with the --silent-install option.
I hope that helps.
Scoop and Buckets Version
Sorry, can't tell since I don't have that system available at the moment. But it's a fresh installation from Friday the 12th.

Scoop Config
I didn't configure anything.

PowerShell Version
Up-to-date Windows 11 version.

I don't expect this to be very relevant in this case.

Additional Softwares
No response

Thanks! Awesome!

Thanks! Awesome!

There are nothing was fixed, just a note for the issue.

According to the manual, you can install it by executing it with the --silent-install option.

Scoop install apps as portable as possible, so you should refer to https://rustdesk.com/docs/en/client/windows-portable-elevation/ OR requests it at https://github.com/ScoopInstaller/nonportable for silent install of RustDesk.
According to their documentation, even if you run it as admin, that prompt will still appear on UI, but the restricted(UAC interaction, etc.) should be gone. I don't use it, this needs your confirmation.

For the controlled end, It is recommended to use their official installers instead of installing via Scoop, whether it is RustDesk or VNC Server, etc.


🎨 style(electron): prettier format all code in electron

In this purely reformat PR, I ran npx prettier "src/electron/**/*.{cjs,mjs,html,js,json,md,ts}" --write to format all code under src/electron/**, so in the future the feature code won't be distracted by the format change.

To confirm @fortuna - this says strings are supposed to be single quoted (go/js-style#features-strings-use-single-quotes) - are we ignoring that?

To confirm @fortuna - this says strings are supposed to be single quoted (go/js-style#features-strings-use-single-quotes) - are we ignoring that?

Updated the prettier config file to reflect that.


Message.respond doesn't work for block actions

This is jumping the gun since Slapp doesn't officially yet support block actions (though in a PR it has some support for it) but block actions no longer accept message bodies in response to a block action interaction.
In previous attachment based action interactions, the payload passed in msg.respond() are sent as a response to the open POST request from Slack, provided that it's called before the responseTimeout. Otherwise, msg.respond falls back to response_url in POSTing the message body.
Workarounds for this are setting a private property msg._respond = null prior to calling msg.respond in order to trick Slapp into thinking there's no open response attached, or calling msg.respond({}) with an empty body and then subsequently calling with the msg.respond(yourMessageBodyHere).
Since v4 of Slapp is incoming, highlighting this issue as something that msg.respond should handle in that new version.

message.respond() should work for block actions now 😄 Bolt v1 included default support for Block Kit. If you have any problems with it, feel free to open another issue.


Add in more Python virtual environment information

Description
We've been asked how Kedro works with venv and pipenv and have prepared documents that have never landed up in our core documentation.
Context
This would help users with their queries about venv and pipenv.
Possible Implementation

We follow this documentation style guide: https://github.com/quantumblacklabs/kedro/blob/develop/docs/README.md
We have the documentation specified in our kedro-examples repository here
You could just copy the docs in, or if you want you could create new docs for us

Taking this one

Addressed in #260


OpenGL 4 additions to OpenGLExtensions.cs

Modifies OpenGLExtensions.cs by adding the ability to call glPatchParametri and adding constants related to tessellation shaders and patches: GL_TESS_EVALUATION_SHADER, GL_TESS_CONTROL_SHADER, GL_PATCH_VERTICES, GL_PATCH_DEFAULT_INNER_LEVEL, GL_PATCH_DEFAULT_OUTER_LEVEL

This is great thanks @ftlPhysicsGuy !


[Feature]: Font Size Setting

Feature description
There currently isn't an option to change the text size on specific windows, only to zoom in or out on the whole program.
The ability to customize the font size, specially in the terminal, will make using the program much more comfortable.
If possible, maintain the option to zoom in/out on the GUI (side bar, top menu...).
Thanks!
Implementation Suggestion
No response
Anything else?
No response

#What font sizes specifically are you thinking of updating? We have different font sizes for different elements and not all of them are easy to update... terminal font sizes already can be updated using term:fontsize

Oh, right, I didn't realize there was a setting for that. I looked inside .config and couldn't find a waveterm folder, so I thought the config file just wasn't accessible (I've also seen this has been pointed out by another user, but that's a different topic).
I guess it would be nice to have a button in the GUI, either to directly open the config file, or better, to change term:fontsize.
Either way, I guess this is now solved, since the feature exists.
Thanks for your time.


two options for your consideration. int if decmila == 0 and decimal only if >= n (1000)

hi,
I have two thoughts...
*would you consider and option to not show the decimal if the decimal is 0 so 1.0 becomes 1

would you also consider an option to only show decimals if >= 1000 i.e has an abreviated metric like K,M etc.

thanks.

Hello,

*would you consider and option to not show the decimal if the decimal is 0 so 1.0 becomes 1

You can use ReadableDecInt function.

would you also consider an option to only show decimals if >= 1000 i.e has an abbreviated metric like K,M etc.

Do you mean something like ReadableHumanNumber function but for decimals?  Is >= 1000 decimals == >= 0.1 ?
If not just give me an example please.

Hello,

*would you consider and option to not show the decimal if the decimal is 0 so 1.0 becomes 1

You can use ReadableDecInt function.

would you also consider an option to only show decimals if >= 1000 i.e has an abbreviated metric like K,M etc.

Do you mean something like ReadableHumanNumber function but for decimals?  Is >= 1000 decimals == >= 0.1 ?
If not just give me an example please.

That's it. No decimals for >0.0 && <1000.0


feat: added operators for postgres array column type

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Document the rest of pathfinder_content

@bors-servo: r+

:pushpin: Commit 4060baa has been approved by pcwalton

:hourglass: Testing commit 4060baa80c0686a5ad9b220f4fe5f079628e8706 with merge 2b5c6682d75a3f79b5a5e02af51650754a7f190d...

:sunny: Test successful - checks-travis
Approved by: pcwalton
Pushing 2b5c6682d75a3f79b5a5e02af51650754a7f190d to master...


error when install with docker

<EMAIL_ADDRESS>install /usr/local/lib/node_modules/angular-cli/node_modules/execSync
node install.js

The command '/bin/sh -c npm install --global angular-cli' returned a non-zero code: 1

I just updated the angular-cli version. Could you pull and try again? If you get the error again, could you run ng --version and paste the output?

I am getting same error ?

I'll need some more information to help.
What is your operating system?
What version of docker are you using?
When the build fails what are the last ~100 lines of console output (npm will usually give some more detail than the final docker error)?

Closing this issue from lack of response.


netcoredbg: 3.0.0-1018 -> 3.1.0-1031

Description of changes

updated netcoredbg to 3.1.0-1031 (https://github.com/Samsung/netcoredbg/releases)
updated dotnet to 8.0.7
updated deps.nix

closes #329620
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Result of nixpkgs-review pr 329845 run on x86_64-darwin 1

1 package built:

netcoredbg

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

1 package built:

netcoredbg

see also #326335

@YoshiRulz thanks, commented there. This PR switches from dotnet 7 to dotnet 8

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

1 package built:

netcoredbg


The retry /backoff code may not be timezone aware

First of all a great useful action... been using it for multiple projects. For the first time I tried using it on a self hostet runner and faced this rare issue hence reporting. This is also the first time that I have faced the rate limiting response form GHA and I get a feeling that the code for retry backoff reset may not be timezone aware... see the attached log. Note the very last line shows that that next attempt will happen 5Hr 30 mins and 59 seconds later. though the authors intention is to try 1 minute later
Since this self hosted runner is running in India time which 5.5 hrs ahead of UTC.. it is clearly a bug that instead of retrying after 1 minute it is adding the time zone offset as well.
  2022-02-24 21:15:38 +0530 - publish -  INFO - created check https://github.com/Apra-Labs/ApraPipes/runs/5321272796
  2022-02-24 21:15:38 +0530 - publish-unit-test-results - WARNING - Request GET /search/issues?q=type%3Apr+repo%3A%22Apra-Labs%2FApraPipes%22+e10e0c3b16257b9be2a05ed3df65554798615562&per_page=100 failed: Forbidden
  2022-02-24 21:15:38 +0530 - publish - WARNING - Request GET /search/issues?q=type%3Apr+repo%3A%22Apra-Labs%2FApraPipes%22+e10e0c3b16257b9be2a05ed3df65554798615562&per_page=100 failed with 403: Forbidden
  2022-02-24 21:15:38 +0530 - publish-unit-test-results -  INFO - There is no Retry-After given in the response header
  2022-02-24 21:15:38 +0530 - publish-unit-test-results -  INFO - Response body indicates retry-able error: you have exceeded a secondary rate limit. please wait a few minutes before you try again.
  2022-02-24 21:15:38 +0530 - publish-unit-test-results -  INFO - Reset occurs in 5:30:59.330597 (2022-02-24 21:16:38), setting next backoff to 19859.330597s

https://github.com/EnricoMi/publish-unit-test-result-action/blob/d0787a9f068cd772424d68efbaad91e6171da8c6/python/publish_unit_test_results.py#L117
it apears that above line may be the root cause of this issue.
defer = max(next - datetime.utcnow().timestamp(), 0)
if next is in IST the above will always be 5:30 hrs more than required

Thanks for reporting, this is valuable. I will look into this.

Can you please test the fix?
uses: EnricoMi/publish-unit-test-result-action/composite@branch-fix-reset-timestamp-utc

The problem is the non-UTC timestamp here (#223):
https://github.com/EnricoMi/publish-unit-test-result-action/blob/2c33be40c34e7dc3b7d798cb0e8e64ce56755c4c/python/publish/retry.py#L76

trying

So my build passed but I wasnt challenged by GHApi rate limiter so I can not vouch if the fix really worked. I can conitnue to stay in the fix branch for report if I observe any retries... unless you suggest a way to force the rate limiter to challenge me

Sure, run this job before the publish action:
    - name: exhaust limit
      env:
        GITHUB_TOKEN: ${{secrets.GITHUB_TOKEN}}
      run: |
        gh api "https://api.github.com/rate_limit" -q '.resources.search'
        for i in $(seq 1 40); do
          gh api "https://api.github.com/search/issues?q=type%3Apr+repo%3A%22EnricoMi%2Fpublish-unit-test-result-action%22+ea2392a7b3ea985a4ed8c3cf084b3776e4a957b0&per_page=100"
          gh api "https://api.github.com/rate_limit" -q '.resources.search'
        done
        gh api "https://api.github.com/rate_limit" -q '.resources.search'

The limit is 30 calls per minute, so this exhausts these calls. Make sure the publish action has this line:
if: always()

I could replicate this and show that the fix works. Thanks a lot!

This has been released as v1.30, available through v1.

I also tested 1.30 using exhaust limit approach you suggested... thanks a ton for quick turn arround.


Challenge Task [WIP]

This is a PR (still WIP) for localtunnel to support connection on demand to overcome the 10 connection limit

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

hi @svavassori. what is the status of this PR?

On 5 March 2018 at 00:58, Jan Kuri<EMAIL_ADDRESS>wrote:

hi @svavassori https://github.com/svavassori. what is the status of
this PR?

The functionality is there, thus you can use it to evaluate; it could be
that there are minor fixes to do though.
Regards,
Sergio

this doesn't work for me, did you even try to run this?

On 5 March 2018 at 10:12, Jan Kuri<EMAIL_ADDRESS>wrote:

this doesn't work for me, did you even try to run this?

I didn't run it, it was to give you an idea of how I implemented the
changes at an architectural level.
Did you have any problem compiling it?

Not working, thanks for trying it out.


chore(deps): update common-dev-assets digest to d165a27

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
c785f20 -> d165a27

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline


Add hints to nucleotide-count exercise

#220 add HINTS.md to nucleotide-count exercise.
Among other things the formatting with all the code snippets might be improved.

LGTM


Refactor: Change any type usage and refactor the code

@rakku-ms

@bganapa

@sijuman

Please re-open this or submit a new PR once you're ready to be out of "draft"


Implement minos.networks.WrappedRequest

┆Issue is synchronized with this ClickUp task by Unito

Closing this issue as it will be resolved by https://github.com/Clariteia/minos_microservice_networks/issues/298


CODEOWNERS: IPsec owns pkg/common/ipsec

This directory was introduced in commit<PHONE_NUMBER>de ("cmd, common: Move countUniqueIPsecKeys to common/ipsec pkg"), but the CODEOWNERS were not updated.
Fixes:<PHONE_NUMBER>de ("cmd, common: Move countUniqueIPsecKeys to common/ipsec pkg")

/test

Changes are fine, but I'll just note that https://google.github.io/styleguide/go/best-practices.html#util-packages common is a bit of a red-flag in terms of package naming.
EDIT: or to be more clear, common/ipsec is specifically fine just not happy we have a common pkg with logic in it)

Feel free to rename. I don't have a dog in this fight.

Changes are fine, but I'll just note that https://google.github.io/styleguide/go/best-practices.html#util-packages common is a bit of a red-flag in terms of package naming.
EDIT: or to be more clear, common/ipsec is specifically fine just not happy we have a common pkg with logic in it)

Feel free to rename. I don't have a dog in this fight.

Yep, it's now on the list :innocent:


Provide a way to clear variable and name scope

This is a follow-up of https://github.com/tensorflow/tensorflow/issues/6189
It would be nice to be able to create a variable or name scope that does not obey all currently open scopes.
As an example:
with tf.variable_scope('foo'):
    with tf.variable_scope('bar'):
        x = tf.constant(1.0, name='x')     # foo/bar/x

with tf.variable_scope('foo'):
    with tf.variable_scope('bar', fresh=True):
        x = tf.constant(1.0, name='x')    # bar/x

This would be useful for using scopes with object oriented TensorFlow graphs.
Consider a slightly modified version of the example from #6189 . Assume each method pushes a scope for the instance (with the class name) and for the method.
class Foo(object):
    def __init__(self):
        self.x = tf.get_variable('x', [], initializer=tf.constant(0.0))

    def meth(self, foo):
        z = tf.multiply(foo, 3.14, name='z')
        return self.x.assign(z)

    def boom(self, foo):
        return tf.multiple(2.0, self.meth(foo), name='baz')

f0 = Foo()      # Foo/__init__/x
f1 = Foo()      # Foo_1/__init__/x
f0.meth(1.0)    # Foo/meth/*
f0.boom(2.0)  # Foo/boom/baz, Foo/boom/Foo/meth/z

I'd like the variables in boom's call to meth to be prefixed with only Foo/meth rather than Foo/boom/Foo/meth. This requires either releasing the variable scope within boom before calling out (hard) or providing a way for meth to clear the existing variable scope.

@ebrevdo Any opinion as to whether this is desirable feature request?

I am interested in the answer to this same question. Thanks.

+1 Need this feature.

+1 Need this as well.

You can access and pass around a scope object:
with variable_scope("a") as vs:
with variable_scope("b"):
with variable_scope(vs):
# back in "a"

Why is this not already a top priority?

+1 Need this feature.

Yeah, build that ~wall~ feature!

+1 would like this feature. Using with variable_scope(""): resulted in the prefix still being affixed to layer weight names. I went around this in my subclassed layer by assigning self._name = '' like so:
class SomeConvs(keras.layers.Layer):
    def __init__(self):
        super(SomeConvs, self).__init__()
        self._name = ''
        layer_name = "name_i'm_forced_to_use_because_i'm_loading_weights_via_name"
        self._conv2d = keras.layers.Conv2D(filters=(2, 2),
                                           name=layer_name)

    def call(self, x):
        x = self._conv2d(x)
        return x

Asking Francois to take a look since the example is Keras specific, and in tf2 name and variable scopes are kinda the same thing now.


In integration test output, print test path relative to workspace root rather than crate root

Problem
If I have a workspace with crates foo and bar, and they both have integration tests, then running cargo test or cargo test --workspace produces output that looks like:
     Running tests/integration.rs (target/debug/deps/integration-90c5d22d758aa08c)

[...]

     Running tests/integration.rs (target/debug/deps/integration-71f1b5c00acba212)

Notable, nowhere in either of these lines (or in anywhere else in any of the integration test output) does Cargo associate which integration test output belongs to which crate.
Proposed Solution
It would be easier for users to visually parse the output here if Cargo would include some indication as to which crate each integration test belongs to, for example by using the path to the workspace root rather than the path to the crate root:
     Running bar/tests/integration.rs (target/debug/deps/integration-90c5d22d758aa08c)

[...]

     Running foo/tests/integration.rs (target/debug/deps/integration-71f1b5c00acba212)

Notes
No response

This came from a zulip thread
When in a workspace, cargo generally shows everything relative to the workspace root, so this change makes sense to me though I have no idea the work required to do it or the side effects it may have.


fix #1852, update sbt to 0.13.9

The packaging and cross-build looks good in local test.

Downloading sbt launcher for 0.13.9:
  From  http://typesafe.artifactoryonline.com/typesafe/ivy-releases/org.scala-sbt/sbt-launch/0.13.9/sbt-launch.jar
    To  /home/travis/.sbt/launchers/0.13.9/sbt-launch.jar
Download failed. Obtain the jar manually and place it at /home/travis/.sbt/launchers/0.13.9/sbt-launch.jar

+1


Update YouTube iframe props to include autoplay

Check out the youtube player options here: https://developers.google.com/youtube/youtube_player_demo

#483 has already added pip but still need to expand this one


fix: alice arg ordering

PR-Codex overview
This PR focuses on fixing the argument ordering in the Alice.ts file within the Portfolio/Integrations directory.
Detailed summary

Fixed the argument ordering for placeOrderDecode function in Alice.ts to correctly decode ABI parameters.
Updated the order of arguments in the function signature to match the decoding process.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

/snapshot

/snapshot


Make it possible to use pod name in cloudinit defs

This is a change I had to make so as to enable StatefulSets of VMs.

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

pkg/libvirttools/virtualization.go, line 425 at r1 (raw file):

	config := in.Config
	name := config.Metadata.Name

Are you sure that always Metadata will be non-nil?

pkg/libvirttools/virtualization.go, line 477 at r1 (raw file):

	virtletVolsDesc, _ := sandBoxAnnotations[VirtletVolumesAnnotationKeyName]
	domXML, err = v.addAttachedVolumesXML(in.PodSandboxId, in.SandboxConfig.Metadata.Name, uuid, virtletVolsDesc, domXML)

Earlier in this func we have that set as name.

Comments from Reviewable

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, 4 unresolved discussions.

pkg/libvirttools/virtualization.go, line 420 at r1 (raw file):

	}

	if in.Config == nil || in.Config.Metadata == nil || in.Config.Image == nil || in.SandboxConfig == nil || in.SandboxConfig.Metadata == nil {

But why you don't use provideed by API Get* here and in other places? You can use them in cascade as they all have check pointer on nil and return nil for complex structure, i.e. other than string, integer...

pkg/libvirttools/virtualization.go, line 454 at r1 (raw file):

	}

	metadataStore.SetContainer(name, uuid, in.PodSandboxId, config.Image.Image, snapshotName, config.Labels, config.Annotations)

I would say we need to replace it with config.GetImage().GetImage() otherwise, as it provided by api?

Comments from Reviewable

Review status: all files reviewed at latest revision, 4 unresolved discussions.

pkg/libvirttools/virtualization.go, line 425 at r1 (raw file):
Previously, jellonek (Piotr Skamruk) wrote…
Are you sure that always Metadata will be non-nil?

yep, it should be replaced with config.GetMetadata().GetName()

pkg/libvirttools/virtualization.go, line 477 at r1 (raw file):
Previously, jellonek (Piotr Skamruk) wrote…
Earlier in this func we have that set as name.

No, we actially have  container/VM name inname, and here we get pod's name. But I think it should be get as in.GetSandboxConfig().GetMetadata().GetName().

Comments from Reviewable

Review status: all files reviewed at latest revision, 4 unresolved discussions.

pkg/libvirttools/virtualization.go, line 477 at r1 (raw file):
Previously, vefimova (Victoria Efimova) wrote…
No, we actially have  container/VM name inname, and here we get pod's name. But I think it should be get as in.GetSandboxConfig().GetMetadata().GetName().

ough, once this was Config, and once SandboxConfig - yeah, my mistake.

Comments from Reviewable

Review status: all files reviewed at latest revision, 4 unresolved discussions.

pkg/libvirttools/virtualization.go, line 425 at r1 (raw file):
Previously, vefimova (Victoria Efimova) wrote…
yep, it should be replaced with config.GetMetadata().GetName()

but if above will catch it - so it's ok there.

Comments from Reviewable

Review status: all files reviewed at latest revision, 4 unresolved discussions.

Comments from Reviewable


Preact Support?

hey folks!
is there any interest in having support for Preact with this builder?
I guess in order to support it is to include the vite-preact plugin into the config?
I'm willing to help if I can get some guidance!
thanks in advance

If you want to make it, then you could try stealing the code from the React plugin, and work from there! You will have to be the primary maintainer, though!

you mean I become the primary maintainer of that part right? just to clarify!
Either way, we are dropping Preact for now because other core libraries we depend on does not support Preact either. when we tackle that again I'm more than happy to jump as a primary maintainer of the preact version of this plugin!


Liveness probes needed for K8s/OpenShift

It would be nice to have out-of-the-box endpoints for k8s/Openshift Livenessprobes which is an essential mechanism  for Pod/container health.
We are currently workarounding it using fluentd-mechanisms

https://docs.fluentd.org/monitoring-fluentd/monitoring-prometheus
https://docs.fluentd.org/monitoring-fluentd/monitoring-rest-api

https://docs.fluentd.org/input/monitor_agent

The simplest form is to activate the monitor_agent in fluent.conf (this is already done for logging, also see Enhancement Request https://github.com/splunk/splunk-connect-for-kubernetes/issues/609) and add an simple HTTP GET to the  endpoint. Once this endpoint stops
being available the pod will be restarted.
This is still better than login into the container and executing an arbitrary command; but it will not give us the certainty that the process itself is still working, just that the endpoint is available.
We used this to mitigate problems with the objects pod where process threads setting up an event watch threw an exception every time a load balancer would kill the connection after 10min. (it would still work afterwards but leave some hundreds defunct processes behind until nothing could be forked and the container was dead)
In a second iteration we used output from the the endpoint to see if somethings changes.
We hope that "emit_count" is a useful metrics for this purpose:
plugin_id:object:c954   plugin_category:input   type:monitor_agent      output_plugin:false     retry_count:
plugin_id:object:c968   plugin_category:input   type:kubernetes_metrics output_plugin:false     retry_count:
plugin_id:object:11e4   plugin_category:output  type:splunk_hec output_plugin:true      buffer_queue_length:0   buffer_timekeys:        buffer_total_queued_size:763465 retry_count:0   emit_records:322709     emit_count:322709       write_count:216 rollback_count:0   slow_flush_count:0      flush_time_count:13662  buffer_stage_length:1   buffer_stage_byte_size:763465   buffer_queue_byte_size:0        buffer_available_buffer_space_ratios:99.8
plugin_id:object:c97c   plugin_category:filter  type:record_modifier    output_plugin:false     retry_count:
plugin_id:object:c990   plugin_category:filter  type:record_modifier    output_plugin:false     retry_count:
plugin_id:object:c9a4   plugin_category:filter  type:record_modifier    output_plugin:false     retry_count:
plugin_id:object:c9b8   plugin_category:filter  type:record_modifier    output_plugin:false     retry_count:
plugin_id:object:c9cc   plugin_category:filter  type:record_modifier    output_plugin:false     retry_count:

So if we use emit_count or one those returned metrics we could create a Liveness probe based on a container command (a script oneliner) to save the metrics and compare it with a later one.
Once it stopped changing the probe fails after n times and the pod will be killed.
We used this to mitigate https://github.com/splunk/splunk-connect-for-kubernetes/issues/493.
Since this is a workaround and we do not know if this endpoint will work until all eternity, it would be nice to have something more official and reliable.
Wishlist:

Provide endpoints which guarantees the functionality of the given service (metrics, logging, objects)
Provide the option to enable/disable it using the umbrella values.yaml file
at least a statement in the docs, that this is a valid way to go for now.

Hi @gnarc, thank you for reporting this issue. We have added this feature request to our backlog and the team will decide when to work on this in the future. We also welcome anyone to create a pull request if they are so inclined.

Cool. Thanks.

it was added in 1.4.9


SiteMap Enhancement

The site map of  the project is not so good looking . Even the arrows are not merging properly and in some places arrows defining the map are not present .
@harikesh409 , I want to fix this issue , please assign me this issue , so that I can proceed.

Go ahead @tier3guy


cli,deps: bump go-libedit to fix bugs

PR: https://github.com/cockroachdb/cockroach/pull/28233
From release notes:

The commands are now properly able to customize the prompt with ~/.editrc on Linux. [#28233][#28233] {% comment %}doc{% endcomment %}
The commands once again support copy-pasting special unicode character from other documents. [#28233][#28233] {% comment %}doc{% endcomment %}

These are bug fixes and do not expose new functionality to users.


⚠ Nebulance has degraded performance

In fe06efa, Nebulance ($NBL) experienced degraded performance:

HTTP code: 502
Response time: 1131 ms

Resolved: Nebulance performance has improved in de81b77 after 9 minutes.


Fail to create a new folder under one SAS attached ADLS Gen2 blob container with full permissions

Storage Explorer Version: 1.17.0
Build Number: 20201216.1
Branch: main
Platform/OS: Windows 10/ Linux Ubuntu 16.04/ MacOS Catalina
Architecture: ia32/x64
Regression From: Not a regression
Steps to Reproduce

Expand one ADLS Gen2 storage account -> Blob Containers.
Create a blob container -> Attach it with SAS by selecting full permissions.
Open the attached blob container -> Try to create a new folder.
Check whether the folder is created successfully.

Expected Experience
The folder is created successfully.
Actual Experience
Fail to create the folder.

Error details:
 "name": "Error",   "message": "Server failed to authenticate the request. Please refer to the information in the www-authenticate header.\nRequestId:c650681a-701f-0045-3a90-d3a43e000000\nTime:2020-12-16T09:50:09.5987038Z",

Verified this issue on build 20210113.4. Fixed.

Verified this issue on build 20210113.4. Fixed.


v1.5.0 release

Coverage remained the same at 86.129% when pulling eeedb7faabccc0aa869c8492425b4db38a39cf55 on rel-v1.5.0 into 2de5819fd32f8ab588f667ba1be35e5fa3737565 on master.


Getting namespace error

What means that??
[ERROR] TiExceptionHandler: Error: Could not lookup constructor for namespace: "AvImageview.ImageView"
I just used it this way:
<ImageView image="$.args.image" ns="AvImageview" class="w-screen h-auto rounded-lg" loadingIndicator="true" contentMode="Alloy.Globals.CONTENT_MODE_FILL" brokenLinkImage="/images/placeholder.jpg"/>

iOS works as expected

using  module="av.imageview" solves it.


Thunderbid Beta cannot be installed on Android 5.1.1

Checklist

[X] I have used the search function to see if someone else has already submitted the same bug report.
[X] I will describe the problem with as much detail as possible.

App version
8.0b1
Where did you get the app from?
Google Play
Android version
5.1.1
Device model
Galaxy Tab A(2016)
Steps to reproduce

Search Thunderbird Beta on Google Play
Install it.

Expected behavior
2.Thunderbird successfully installed.
Actual behavior

Your device is not compatible with this version message is displayed, even if Thunderbird app should support Android 5.0 and up.

Logs
No response
Notes
Tried to install K-9 mail on the same device and it worked.

The version from here installs on my Fifth Generation Kindle Fire running Android 5.1.1.

Installed the new version 8.0b2 on Galaxy tab  A, Android 5.1.1 and it was successfully installed.

I'm suspecting this is due to old architectures not supported anymore, possibly mips. I think we'll just have to live with this, the architecture has been deprecated since 2018 or so. Thank you for reporting though, and @ThePillenwerfer for confirming it works on other Android 5 devices!


scons: update to 4.7.0, drop all the old versions

Description of changes
This techinically removes the man pages, but that's probably fine?
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

Are the older versions not needed anymore? Yay!

Same for openvino

Next will be how to fix the dreadful lack of manpages

Hmm I wonder how come CI was green. A quick git grep scons.override reveals a few more evaluations fixes missing...

Those were probably merged into master later.

I'll do another pass of these after the next staging cycle, probably.

I already opened https://github.com/NixOS/nixpkgs/pull/326478 to help other PRs that target currently staging.


All done except Grammar Structure

I will figure Grammar part out this week and will also finish Markup 2.

Will request when the code is finished.


Why is it realtime on the lovelace card but not when casting a RTSP stream using dash cast

If i use a camera entity or a direct RTSP url there is a lag of 15 seconds or so. If i use the webrtc card instead it's near realtime.

Webrtc is designed for video calls so they fixed the 15 second delay thing that many other protocols have. The actual delay depends on the encoding and also how close to the next I-frame you join the stream

Maybe you casting not webrtc card with dashcast


Add Enumerable#to_h

Should probably overwrite in Hash, just not sure whether to retun dup or self there.

Hash doesn't include Enumerable AFAIK :/
Also, the "requirement" for including Enumerable is to implement an #each method. With your Enumerable#to_h, a class including it would have to implement #[] too.

Well, then not overwrite but define ;)

Thanks! I'll add Hash#to_h to return self, like in Ruby :-)


Rules don't rotate properly in 3-Way split cells

Some rules don't rotate properly if they are applied across 3x3 split cells.
The horizontal rule here does only rotate once to the right and the diagonal only gets applied in the normal way.

other rules do work better:

also to the top / left its different:

also also the top / left works differently if the squares get filled in procedurally and not with the brush like i did above

here is the file to try it out:
bug1.json

got it to work when i scaled the grid up by 3 because when it splits in 3 it wont get rounded. But don't think it can be fixed by scaling it up because you would need to scale it up by all the numbers then.


Infinite recursion between deprecated API's

Expected behavior
Print log to debugger
Actual behavior

Steps to reproduce
import Logging

struct Hello: LogHandler {

    var metadata: Logging.Logger.Metadata = [:]

    var logLevel: Logging.Logger.Level = .error

    init(_ label: String) {
    }

    subscript(metadataKey metadataKey: String) -> Logger.Metadata.Value? {
        get {
            return self.metadata[metadataKey]
        }
        set(newValue) {
            self.metadata[metadataKey] = newValue
        }
    }
}

import Logging

final class Client {

    static let shared = Client()

    private init() {
        LoggingSystem.bootstrap(Hello.init)
    }
}

@main
struct TestApp: App {

    init() {
        _ = Client.shared
    }

    var body: some Scene {
        WindowGroup {
            ContentView()
        }
    }
}

import Logging

struct ContentView: View {

    init() {
        var log = Logger(label: "unique.value")
        log[metadataKey: "mykey"] = "jelly"
        log.error("hi")
    }

    var body: some View {
        Text("Hello, World!")
    }
}

The init for SwiftUI view's may be called multiple times, but this doesn't seem to be the issue.
SwiftLog version/commit hash
Latest release as of (9th Jan 2023) - v1.4.4
Swift & OS version (output of swift --version && uname -a)
swift-driver version: 1.62.15 Apple Swift version 5.7.1 (swiftlang-<IP_ADDRESS>.3 clang-14<IP_ADDRESS>)
Target: arm64-apple-macosx13.0
Darwin Roberts-Personal-MacBook-Pro.local 22.1.0 Darwin Kernel Version 22.1.0: Sun Oct  9 20:14:30 PDT 2022; root:xnu-8792.41.9~2/RELEASE_ARM64_T8103 arm64
Xcode Version 14.1 (14B47b)

You didn't finish implementing your log handler, in the screenshot you paste the solution is included:
    @available(*, deprecated, message: "You should implement this method instead of using the default implementation")
    public func log(level: Logger.Level,
                    message: Logger.Message,
                    metadata: Logger.Metadata?,
                    source: String,
                    file: String,
                    function: String,
                    line: UInt) {
// ...
    }

you have to implement this method. It delegates to old methods for compatibility with existing LogHandler implementations which used the "old" API. This way we did not break source compat when adding the new handler APIs.
Please implement the above method and things will work as expected.

Double checked, yeah this works correctly:
import Logging

@main
public struct untitled4 {

    public static func main() {
        LoggingSystem.bootstrap(Hello.init)

        var log = Logger(label: "unique.value")
        log[metadataKey: "mykey"] = "jelly"
        log.error("hi")
    }
}

struct Hello: LogHandler {

    var metadata: Logging.Logger.Metadata = [:]

    var logLevel: Logging.Logger.Level = .error

    init(_ label: String) {
    }

    subscript(metadataKey metadataKey: String) -> Logger.Metadata.Value? {
        get {
            return self.metadata[metadataKey]
        }
        set(newValue) {
            self.metadata[metadataKey] = newValue
        }
    }

    // REQUIRED
     func log(level: Logger.Level,
                    message: Logger.Message,
                    metadata: Logger.Metadata?,
                    source: String,
                    file: String,
                    function: String,
                    line: UInt) {
        print("message: \(message)")
    }
}

Please complete your LogHandler implementation and it'll work fine.
If there's anything else here please feel free to comment or reopen the issue

Please re-open this ticket :) I will submit a PR to fix.

Commented more in the PR: https://github.com/apple/swift-log/pull/249
We can't do source breaking changes like this for quite a while.


Fetch all available application

How fetch all available application for a specific google developer account with the lib?

Can you be a bit more specific? Which API are you using?
In general, issues on this project are against the API client itself and not the APIs that it talks to. Support for those APIs are typically handled on StackOverflow.

Google Play API. I would like to fetch all the app for a specific client. I have checked the samples in github. I don't see anything relating to my issue

Unfortunately there's no one who works on this project that will be able to answer any questions about that specific API. I'd recommend asking your question on stackoverflow with the Google Play API tag.


Child component doesn't re-render when its props change

Qwik Version
0.10.0
Operating System (or Browser)
Chrome / Ubuntu 22.04
Node Version (if applicable)
16.17.1
Which component is affected?
Qwik Runtime
Expected Behaviour
As per the example in documentation the child component should re-render when its props change.
const Child = component$((props: { count: number }) => {
  return <span>{props.count}</span>;
});

const MyApp = component$(() => {
  const store = useStore({ a: 0, b: 0, c: 0 });

  return (
    <>
      <button onClick$={() => store.a++}>a++</button>
      <button onClick$={() => store.b++}>b++</button>
      <button onClick$={() => store.c++}>c++</button>

      <Child count={store.a} />
      <Child count={store.b} />
    </>
  );
});

Actual Behaviour
The child component doesn't re-render on prop change.
Child only re-renders only if the value passed as the prop is read somewhere in the parent component.
This could be due to the store subscription not getting activated.
Additional Information
Please remove {JSON.stringify(store)} in the code to reproduce the bug

The code reports an error, no?

I cant reproduce the issue in 0.10.0


Publish content: extra pages

TODO

[ ] Terms and conditions
[ ] Privacy policy
[ ] home/landing

Deliverables

Published content on extra pages

Estimated Effort

[ ] XS: 1 to 2 hours
[ ] S: half a day
[ ] M: 1-2 day
[ ] L: 1 week
[ ] XL: Move to an epic

Out of scope

Are we using CDS or DTO existing terms and policies?


Hexes don't seem to line up with grids

I don't fully remember if this was created in v9 or v10. I believe it has been ported from a v9 game and duplicated.
This map has a 177 grid; tried to scale up to 200 but problem persisted.

fvtt-Scene-stolen-lands-(copy).json.txt

Should now be fixed in 2.0.1!


tutorial update str interpolation syntax

The tutorial was still using the deprecated string interpolation syntax.

If $(...) is the new string interpolation syntax, then I guess this part under the 'Friendly' page should be removed/changed?
https://www.roc-lang.org/friendly

"Name: \(Str.trim name)" uses string interpolation syntax: a backslash inside a string literal, followed by an expression in parentheses. This code is the same as combining the string "Name: " with the string returned by the function call Str.trim name.

Because Roc's string interpolation syntax begins with a backslash (just like other backlash-escapes such as \n and "), you can always tell which parts of a string involve special handling: the parts that begin with backslashes. Everything else works as normal.


manifests: Return UNSUPPORTED when deleting manifests by tag

The OCI distribution spec allows implementations to support deleting manifests by tag, but also permits returning the UNSUPPORTED error code for such requests. docker/distribution has never supported deleting manifests by tag, but previously returned DIGEST_INVALID.
The Tag and Digest fields of the manifestHandler are already correctly populated based on which kind of reference was given in the request URL. Return UNSUPPORTED if the Tag field is populated.
Signed-off-by: Adam Wolfe Gordon<EMAIL_ADDRESS>

This PR fixes the conformance error seen here: https://oci-conformance.s3.amazonaws.com/distribution-spec/distribution/content-management/report.html


Show command to download results for bacalhau job run

bacalhau docker run prints a command on how users can download the results, but not for bacalhau job run. We should print a similar command if the job type is ops or `batch.
Example outputs:
→ /usr/local/bin/bacalhau docker run ubuntu echo helloUsing default tag: latest. Please specify a tag/digest for better reproducibility.
Job successfully submitted. Job ID: 477670e9-69b6-43b2-81a0-21ba44079189
Checking job status... (Enter Ctrl+C to exit at any time, your job will continue running):

	Communicating with the network  ................  done ✅  0.2s
	   Creating job for submission  ................  done ✅  0.0s
	               Job in progress  ................  done ✅  0.7s

To download the results, execute:
	bacalhau get 477670e9-69b6-43b2-81a0-21ba44079189

To get more details about the run, execute:
	bacalhau describe 477670e9-69b6-43b2-81a0-21ba44079189

→ /usr/local/bin/bacalhau job run hello.yaml
Job successfully submitted. Job ID: j-c0daa560-2445-4f20-9b3c-3cdca5cc6be8
Checking job status... (Enter Ctrl+C to exit at any time, your job will continue running):

	Communicating with the network  ................  done ✅  0.1s
	               Job in progress  ................  done ✅  0.6s

To get more details about the run, execute:
	bacalhau job describe j-c0daa560-2445-4f20-9b3c-3cdca5cc6be8

To get more details about the run executions, execute:
	bacalhau job executions j-c0daa560-2445-4f20-9b3c-3cdca5cc6be8

Pre-requirement #3971


Zixu jin

Sure, already pushed it

That's not possible, you wouldn't get this diff otherwise. Please  pull upstream (not main) and push, and show me the output of these commands

You are on the wrong branch. You are on main, but the pr is from the ZIXU-JIN branch. Use git switch to go on this branch, then pull upstream main and push.


what should be the maximum duration of the sound?

what should be the maximum duration of the sound?

There isn't any limitation on the duration of audio, whatever fits in your GPU is the upper bound.

Hopefully, your question have been answered, I am closing this issue for now, feel free to reopen it incase you have further questions.


[Bug] When nan is used as the min argument to mindspore.ops.clamp, the wrong result is printed

Environment
Hardware Environment(Ascend/GPU/CPU):

/device cpu

Software Environment:

MindSpore version (source or binary): 2.2.13
Python version (e.g., Python 3.7.5): 3.8.10
OS platform and distribution (e.g., Linux Ubuntu 16.04): Linux Ubuntu 22.04
GCC/Compiler version (if compiled from source):  7.5.0

Describe the current behavior
When nan is used as the min argument to mindspore.ops.clamp, the wrong result is printed. While when nan is used as the max argument, the result is same as pytorch.
Describe the expected behavior
tensor([[nan, nan, nan],
[nan, nan, nan],
[nan, nan, nan]])
Steps to reproduce the issue
import mindspore.ops as ops
import mindspore as mind
import numpy as numpy

input_tensor = mind.tensor(np.array([[1, 2, 3], [4, 5, 6], [7, 8, 9]], dtype=np.float32))
min=float('nan')
max=2
output_tensor = ops.clamp(input_tensor,min,max)

# Print the output tensor
print(output_tensor)

#pytorch 2.0.0+cu117
import torch
import numpy as np

input_tensor = torch.tensor(np.array([[1, 2, 3], [4, 5, 6], [7, 8, 9]]))
min=float('nan')
max=2
output_tensor = torch.clamp(input_tensor,min,max)

print(output_tensor)

the same bug should exist in mindspore.ops.clip too


Old-style search layout

[x] Google, Google Images, and Google Video could all have their search boxes on homepages and results pages be made a bit squarer, and the padding between results could probably be condensed a bit.
[x] Green website link text would also be nice.
[x] "People also ask" can be removed thanks.
[x] It'd probably be quite hard to reorganise the little thumbnail thing above the result title, but padding could be slimmed and a regex replacement of / › /\//g could be done to transform URLs to a more normal format.

All of this functionality has been added as of right now; scheduled to be added in the upcoming v2.2 update.