Cannot register a request that uses a string body

Expected Behavior
To be able to register a request that uses a form-encoded body.
Actual Behavior
Any request that uses a string body silently fails to register.
Steps to Reproduce the Problem
const authHeaders = {
  'Content-Type': 'application/x-www-form-urlencoded',
};

await mock.register(
  { method: 'POST', endpoint: '/auth', body: ' username=username&password=password', headers: authHeaders },
  { status: 200, body: { access_token: 'string' } },
);

// sending a matching request will 404

// Or list the mappings
const mappings = await mock.getAllMappings();
console.log(mappings); // empty array that shows the register silently failed

Specifications

Version: 1.6.0
Platform: Windows
Subsystem: WSL2

Hi, thanks for raising this up. I will try to look at this later today.
Meanwhile, if you have any more findings about the issue, do share them

Have you tried using BodyType feature as specifying BodyType.Body?

Looks like this is something wiremock does not have a good way to support which might limit our support too. SO thread: https://stackoverflow.com/questions/48627656/wiremock-match-request-post-by-params

@Rigellute if there is a JSON equivalent that you can come up with that will solve your case, I am happy to look at possible implementations of that in the library
to see some examples of wiremock JSON requests: http://wiremock.org/docs/stubbing/

@satvik-s thanks for looking into this. I've not looked into a JSON equivalent workaround.
Although the non-JSON Basic Stubbing example from the wiremock docs should work for my usecase too (since the body is just a string).
The main issue was that the plain string body was not being registered with wiremock server itself. I've not tried v2 of this lib, which may have fixed that?

@Rigellute that might work. i would suggest trying BodyType.Body for that. here is an example of doing something similar: https://github.com/HBOCodeLabs/wiremock-captain/tree/main/docs/examples#return-binary-data-eg-api-with-protobuf-support

@Rigellute  were you able to figure this out? if yes, would like to close this out

Hi @satvik-s, I've not yet tried using BodyType.Body.
I've pivoted away from using wiremock for the time being, so feel free to close. If I come back and this is still an issue, I'll reopen.


color scales ranges

Actual Behavior:
Roni:

Case colors are too heavily in the dark range, most extremely in (Cumulative, Ratios) mode – does the color scale need to be adjusted?

How about a color scale that has more variance at both the high end and low end, like an S-curve?    Doesn't help with animation, however, since the low variance middle area will have to be crossed at some point.
Having consistency over time conflicts with rescaling to better show differences at each time.  But how about showing both a global scale (across all time) and a local scale (for the current time), so the user could select which scale they want to use.  Also, the local scale could be resized to show how it relates to the size of the global scale.  Something like this:
all time scale:  [0 ...                     |                             |       max over all time]
current scale:                              [1K...   10K... 100K]
You'll have to imagine the gradient of colors inside the [brackets...].

As hard as this problem is, here is making it harder:
Beyond the need to highlight relative differences between different locations (and to some extent also across time), for many signals it is important to show the absolute significance of the current levels:  North Dakota may have the highest number of tests each day, but is it really that high?  Or, Iowa may have the lowest, but is it really very low?  For many of our indicators, there are some a priori reference points, expectations, desiderata, or red lines whose crossing is significant.  Arguably, we should not use "hot red" to indicate a level that is not disconcerting, or green to indicate a level that it totally fine, regardless of the levels at other locations.  For some signals, it's not about the boundary between "good" and "bad", but about comparison to familiar markers (like, e.g. pre-pandemic levels).
Suggested solutions are hereby solicited.
In a time plot context, one or more horizontal lines may convey that reference information.

We could visualize a quantifiable measure of significance itself, perhaps with another attribute such as line thickness, or opacity, or with a separate indicator analogous to confidence bands.  Or we could flag significant events with annotations, if they have a discrete time or place to flag.  Annotations can highlight ranges or areas as well as points.
Letting the user infer significance, particularly if it is subjective, means we have to show enough so they can do that inference, such as showing a values relative to a total, or relative to arbitrary thresholds.    We can show both absolute values and relative values (e.g. per-capita) in the same chart if we avoid the confusion of multiple scales.   We can show both values and change of values (1st derivative, 2nd derivative...) in the same chart more easily since they have the same scale, but again, we have to be careful when showing the rate of change (which is relative).

If we start to use colors more consistently to represent "good" or "bad" things, then we should be careful to be comprehensive so that we don't leave out a few cases that accidentally imply the opposite of what we intend.
Also we ought to be careful of cultural assumptions about color.  "Red" is not bad everywhere, nor is "green" always good.

If we start to use colors more consistently to represent "good" or "bad" things, then we should be careful to be comprehensive so that we don't leave out a few cases that accidentally imply the opposite of what we intend.
Can you explain or give an example?

Also we ought to be careful of cultural assumptions about color. "Red" is not bad everywhere, nor is "green" always good.
Fair point, although we are optimizing for U.S. consumption.

If we start to use colors more consistently to represent "good" or "bad" things, then we should be careful to be comprehensive so that we don't leave out a few cases that accidentally imply the opposite of what we intend.

Can you explain or give an example?

I just mean that "starting to be consistent" is not the same as "being consistent everywhere".  But there are also probably cases where we are not sure whether to consider a high value for some indicator either good or bad.  Maybe more visits to hospitals correlates with more infections, for example.

The "define thresholds for good or bad and map that way" strategy is what sites like COVID Exit Strategy do. It makes sense for their mission and target audience: their audience wants to know "How bad is my state?" and they can answer "Bad", supplementing that with the tables showing each metric color-coded by some standard.
On the other hand, our approach right now seems more designed for people who want to compare specific metrics in ways we don't anticipate. Since they're sophisticated and we don't know their exact criteria, we instead present all the data in ways that facilitate the user drawing their own conclusions.
I think both approaches have merit for their audience. But we need to decide who our audience is so we can understand which approach better serves their needs; and if we decide on setting good/bad thresholds, we'll have to talk to the audience to figure out what is good and what is bad.

I very much agree that the specifics should depend on who the users are and what they want.
But for now, we continue to develop for an ill-defined, general, user, which appears to be at least moderately data savvy.
My suggestion was not to switch to the CAN style, but rather to add some absolute grounding to some of the signals.
The main goal continues to be geo-wise and time-wise comparisons.  But for the same relative comparison of locations, there is a significant difference between, say, most of them being "not-too-bad", and all of them being in pretty bad state.  I was suggesting that we try to convey that sense.
Here is one concrete suggestion, not necessarily the best one:  add one or more reference points to the color legend.  E.g. ads a small tick on the color legend itself and indicate that it corresponds to the 'pre-pandemic level', or to the 'threshold for opening the economy', or some such thing.

I think I'm also going to close this because this is a very static issue at this point. For example, we recently redesigned/extended the color scales during Omicron first wave, so at least this is out of date with what we presently have. We can always bring it back to life if somebody tells me I'm wrong.


pkg/trace/obfuscate: add a filter to extract table names from queries

Description
This change introduces a new tag called sql.tables which contains the tables that a query addresses as list of comma-separated values. To enable it, the feature flag table_names needs to be set using DD_APM_FEATURES=table_names. For example, given the query:
SELECT * FROM users JOIN friends

Will result in the tag sql.tables to contain the values users,friends
Limitations
The current algorithm works agnostic of SQL engine. It simply takes the first word that follows any of the following keywords: FROM, UPDATE, INTO and JOIN.

Different SQL engines may have different syntax and could contain further keywords (example) after these ones which are not table names. This case is not covered by the current implementation.

If we later on decide to have the tracing clients mark the SQL engine as a tag, we could use it to further improve the processing.

This looks good to me. My only comment is that table names can be case-insensitive, and we may want to recognize two instances of the same table name with different cases as the same table name. I suppose it's a product question though - perhaps a customer would want to see that they are using different casing in their queries.

@pkalmakis I see some articles online (although no personal experience) saying that some database engines have table names that are case sensitive. I'd say to leave it like this for now and address it later if it's a problem. I hope that's ok with you. The impact is minimal because this is a "feature-flag" only feature, not even mentioned in the change log, so there is time to improve.


Crashes & out of memory

I'm trying to debug crashes and out memory indications.

The crash reports from Apple are around the time of database access.
E.g., see https://github.com/stephencelis/SQLite.swift/issues/1042

Crash reports from BugSnag are indicating out of memory. (WIth no traces).

Dany gave me logs. "No errors or pop ups,but after returning from a chrome rendered link, Neebla looked like it restarted,landed me back to album list."
He was wondering about memory usage in the app. I'm wondering if this is when BugSnag is reporting out of memory crashes.

Running connected to the Xcode debugger, I tapped on a URL. Coming back, the app restarted. The debugger said "Message from debugger: Terminated due to signal 9".

Results of showing open files when going into the background-- and get signal 9 in this case too:
2021-03-18T19:37:20-0600 debug  : openFilePaths: ["/dev/null", "/dev/ttys000", "/dev/ttys000", "/private/var/mobile/Containers/Data/Application/BC706923-AC8B-426B-8B0E-98BC27B1BA5F/Library/Application Support/com.bugsnag.Bugsnag/biz.SpasticMuffin.SharedImages/v1/kvstore", "?", "/private/var/mobile/Containers/Shared/AppGroup/2A899802-F51E-4921-BD14-71E7F3CE6582/Documents/Neebla.SQLite.db", "?", "", "/private/var/mobile/Containers/Shared/AppGroup/2A899802-F51E-4921-BD14-71E7F3CE6582/Documents/SyncServer.SQLite.db", "/private/var/mobile/Containers/Shared/AppGroup/2A899802-F51E-4921-BD14-71E7F3CE6582/Documents/logging/LogFile.txt", "/private/var/mobile/Containers/Data/Application/BC706923-AC8B-426B-8B0E-98BC27B1BA5F/Library/Caches/biz.SpasticMuffin.SharedImages/Cache.db", "/private/var/mobile/Containers/Data/Application/BC706923-AC8B-426B-8B0E-98BC27B1BA5F/Library/Caches/biz.SpasticMuffin.SharedImages/Cache.db-wal", "/private/var/mobile/Containers/Data/Application/BC706923-AC8B-426B-8B0E-98BC27B1BA5F/Library/Caches/biz.SpasticMuffin.SharedImages/Cache.db-shm", "/private/var/mobile/Containers/Data/Application/BC706923-AC8B-426B-8B0E-98BC27B1BA5F/Library/Caches/biz.SpasticMuffin.SharedImages/Cache.db", "", "/private/var/mobile/Containers/Data/Application/BC706923-AC8B-426B-8B0E-98BC27B1BA5F/Library/Caches/biz.SpasticMuffin.SharedImages/Cache.db-wal", "/private/var/containers/Shared/SystemGroup/systemgroup.com.apple.nsurlstoragedresources/Library/dafsaData.bin", "",

This was one just before going into the background and getting the signal 9:
openFilePaths: ["/dev/null", "/dev/ttys000", "/dev/ttys000", "/private/var/mobile/Containers/Data/Application/F4FA2CCC-447D-41B7-866A-4BB047D3FDBF/Library/Application Support/com.bugsnag.Bugsnag/biz.SpasticMuffin.SharedImages/v1/kvstore", "?", "?", "/private/var/mobile/Containers/Shared/AppGroup/2A899802-F51E-4921-BD14-71E7F3CE6582/Documents/Neebla.SQLite.db", "/private/var/mobile/Containers/Shared/AppGroup/2A899802-F51E-4921-BD14-71E7F3CE6582/Documents/SyncServer.SQLite.db", "/private/var/mobile/Containers/Shared/AppGroup/2A899802-F51E-4921-BD14-71E7F3CE6582/Documents/logging/LogFile.txt", "/private/var/mobile/Containers/Data/Application/F4FA2CCC-447D-41B7-866A-4BB047D3FDBF/Library/Caches/biz.SpasticMuffin.SharedImages/Cache.db", "/private/var/mobile/Containers/Data/Application/F4FA2CCC-447D-41B7-866A-4BB047D3FDBF/Library/Caches/biz.SpasticMuffin.SharedImages/Cache.db-wal", "/private/var/mobile/Containers/Data/Application/F4FA2CCC-447D-41B7-866A-4BB047D3FDBF/Library/Caches/biz.SpasticMuffin.SharedImages/Cache.db-shm", "/private/var/mobile/Containers/Data/Application/F4FA2CCC-447D-41B7-866A-4BB047D3FDBF/Library/Caches/biz.SpasticMuffin.SharedImages/Cache.db", "/private/var/mobile/Containers/Data/Application/F4FA2CCC-447D-41B7-866A-4BB047D3FDBF/Library/Caches/biz.SpasticMuffin.SharedImages/Cache.db-wal", "/private/var/containers/Shared/SystemGroup/systemgroup.com.apple.nsurlstoragedresources/Library/dafsaData.bin"]

Here's what I'm using to get this:
    // From https://developer.apple.com/forums/thread/655225
    func openFilePaths() -> [String] {
        let result = (0..<getdtablesize()).map { fd -> (String?) in
            var flags: CInt = 0
            guard fcntl(fd, F_GETFL, &flags) >= 0 else {
                return nil
            }
            // Return "?" for file descriptors not associated with a path, for
            // example, a socket.
            var path = [CChar](repeating: 0, count: Int(MAXPATHLEN))
            guard fcntl(fd, F_GETPATH, &path) >= 0 else {
                return "?"
            }

            // https://stackoverflow.com/questions/11737819
            var flockValue:flock = flock()
            if fcntl(fd, F_GETLK, &flockValue) >= 0 &&
                flockValue.l_type == F_WRLCK {
                return String(cString: path) + "; flock.l_type: F_WRLCK (exclusive or write lock)"
            }

            return String(cString: path)
        }

        return result.compactMap {$0}
    }

So it seems this specific issue-- of tapping on a link and coming back to Neebla is not a file lock issue.
This is also evidence that SQLite is not holding a file lock when the app goes into the background.

A possibility for the overt crashes coming from Apple is that the SQLite db is in the shared container.
https://inessential.com/2020/02/13/how_we_fixed_the_dreaded_0xdead10cc_cras
“The moral of the story ended up being: just don’t keep your SQLite database in the shared group container.”
https://github.com/stephencelis/SQLite.swift/issues/1042
https://stackoverflow.com/questions/30156107/share-sqlite-database-between-app-and-extension
https://rbranson.medium.com/sharing-sqlite-databases-across-containers-is-surprisingly-brilliant-bacb8d753054
https://github.com/andpor/react-native-sqlite-storage/issues/308
https://developer.apple.com/library/archive/technotes/tn2408/_index.html
“When you create a shared container for use by an app extension and its containing app in iOS 8.0 or later, you are obliged to write to that container in a coordinated manner to avoid data corruption.”
https://www.avanderlee.com/swift/core-data-app-extension-data-sharing/
https://github.com/sqlcipher/sqlcipher/issues/156
https://stackoverflow.com/questions/41599261/crash-when-opening-fmdb-in-background-mode
https://sqlite.org/docs.html
https://github.com/ccgus/fmdb/issues/262
https://developer.apple.com/forums/thread/655225
https://stackoverflow.com/questions/21473162/database-is-locked-crash-in-sqlite3-database-in-ios
https://github.com/sqlcipher/sqlcipher/issues/255
https://developer.apple.com/documentation/uikit/uiapplication/1623031-beginbackgroundtask
https://developer.apple.com/forums/thread/126438

https://developer.apple.com/documentation/uikit/uiapplication/1623031-beginbackgroundtask
You can call this method at any point in your app’s execution. You may also call this method multiple times to mark the beginning of several background tasks that run in parallel. However, each task must be ended separately. You identify a given task using the value returned by this method.
To assist with debugging, this method generates a name for the task, based on the name of the calling method or function. If you want to specify a custom name, use the beginBackgroundTask(withName:expirationHandler:) method instead.
This method can be safely called on a non-main thread. To extend the execution time of an app extension, use the performExpiringActivity(withReason:using:) method of ProcessInfo instead.

My next planned action is to do this:
"the containing app (and all applications) should properly use background task assertions around file operations they require completed in a shared container (with or without extensions). This includes all writes or deletions. Such a process might still be killed by jetsam but at a much lower frequency."
(from https://developer.apple.com/library/archive/technotes/tn2408/_index.html)
This should be relatively straight forward for iOSBasics as there are pretty well-defined entry points to this API.
It will be tricker in the Neebla app itself, which uses a separate SQLite db.

We'll, I've wrapped the main entry points for iOSBasics in a new BackgroundAsssertable from iOSShared. And that doesn't appear to be changing the crash rate for Neebla. At least now I've got a "good" repro path: If you remove the app, get an album downloading, put app in the background and turn of the screen. That gets me lots 'o crashes.

https://developer.apple.com/documentation/xcode/diagnosing_issues_using_crash_reports_and_device_logs/identifying_high-memory_use_with_jetsam_event_reports
"Discover why the operating system terminated your app when available memory was low."
https://developer.apple.com/forums/thread/73192
https://stackoverflow.com/questions/15122986/what-does-jetsam-really-do
https://programmer.ink/think/learn-more-about-oom-low-memory-crash-in-ios.html

In bug reports from Apple, where do the crashes originate? Am I on the right track with the background assertions?

20120317.0:

a)

Next:

Replacing Bugsnag with Firebase Crashlytics: Bugsnag doesn't catch lots of crashes. And Apple crash reporting only seems to work for TestFlight builds/builds you upload to them. And has some big latencies.
https://github.com/firebase/firebase-ios-sdk/blob/master/SwiftPackageManager.md

Wrap Timer usage in the new background assertions.

In TestFlight build 20210319.1 I've added some more usage of backgroundAsssertable in iOSBasics-- this time in the network delegate calls. The crashes above (https://github.com/SyncServerII/Neebla/issues/7#issuecomment-802978539) I was getting stem from network delegate callbacks, but I'm not sure this change will quite enough. I'd like to proceed gradually, adding more code to deal with crashes only as needed. When I'm certain it's needed.

Result: Still crashes. In same manner. Get an album started downloading, put into the background, and fairly reliably get a crash.

May want to add more backgroundAssertable's in NotificationCenter.default.addObserver's.

I have moved to using a single SQLite db (from one in the main app in one in iOSBasics). This is to:
a) simplify things
b) because it seemed like I wasn't seeing 2x WAL and SHM files open (which I would expect), and
c) Admittedly not very extensive looking on stackoverflow seemed to indicate that multiple SQLIte dbs was inadvisable.
The main possible problem with this is conflicting names of databases tables across Neebla and iOSBasics.

That db didn't help the crash issue.
My next change is to not send local notifications in Neebla when the app is in the background. These drive the code in https://github.com/SyncServerII/Neebla/issues/7#issuecomment-802978539. My hypothesis is that when the network delegate methods get called in the backgound, the amount of work that can be done by the app is limited. And if you go over that, the system kills the app.

Testing criteria: Getting all albums downloaded without a single crash reported from Apple-- using a TestFlight build. (Yes, this is a moving criteria, as it depends on the number of albums and their specific size and data parameters).

All of these crashes I see so far in Apple crash reporting are still coming from unreadCountFor-- haven't dealt with all of these yet.

TestFlight 20210320.1 testing: Got through a full round of downloads of all albums from scratch with no crashes!


Report name

Add host, start time and scenario name to report filename (should be easier to find and sort)
Add human friendly duration in html report
Add some doc about dev and debugging

Close #2931

Can you do this without adding the humanfriendly dependency? Seems a bit much to add an entire package just to format one date...
There's already some info about debugging in running-in-debugger.rst, can you maybe add your info there instead (and link to it from developing-locust.rst)
@andrewbaldwin44 Any opinions on the TS stuff?

@obriat Could you also check that this works with the --html flag?

Can you do this without adding the humanfriendly dependency? Seems a bit much to add an entire package just to format one date...
There's already some info about debugging in running-in-debugger.rst, can you maybe add your info there instead (and link to it from developing-locust.rst)
@andrewbaldwin44 Any opinions on the TS stuff?
I'm not a Python expert, but does this package adds a overhead to the runners or just the report part?
I'll move my doc to this page

I'm not a Python expert, but does this package adds a overhead to the runners or just the report part?

Hey there! Not a maintaner, but, I don't think the issues is adding a overhead, it's having to add a full package (that hasn't been updated since 2020) just to format a date for a report, I'd say that adding your own implementation would be better :)
You can always check how humanfriendly does it!
https://github.com/xolox/python-humanfriendly/blob/6758ac61f906cd8528682003070a57febe4ad3cf/humanfriendly/__init__.py#L402
It really isn't hard nor long!

@obriat Could you also check that this works with the --html flag?
Hi,
I think that I response to every suggestions and fix failed tests.

About the --html flag, this option needs a filename as input (not mandatory but throw an exception on writing file). So what should we do ?

Keep the current behaviour?
Use the default generated filename if no input is given (but detects if the input is a dir and not a full filename+path)?

Hey @obriat, for the --html <filename> flag, I just meant to double-check it's still working as expected, since it also uses the get_html_report function, but looks fine so no need to change anything :+1:

I tested --html just for fun :) It doesn't seem to have the duration?

Maybe add a search for ' seconds' here to ensure it works https://github.com/locustio/locust/blob/eba774c8db030a103fd82bcdf26cef0d5376415e/locust/test/test_main.py#L1183

Btw, resolve the conflicts in launch.json whatever way you like, dont worry about my changes :)

I’ll fix the conflict, a bit strange about the —html I’m pretty sure I tested it :(
Is there a way to make a automated test about it?

I tested --html just for fun :) It doesn't seem to have the duration?

"It works on my PC":
git branch --show-current
report-name
poetry run locust -f examples/basic.py  -u 1 -H http://<IP_ADDRESS>:8089 --headless -u 1 -t 30s --html ~/headless-locust-report.html
grep -Eo '"duration": "[^"]*"'  ~/headless-locust-report.html
"duration": "29.067671298980713 seconds"

The rendered html is also correct  "During: 03/11/2024 23:01:02 - 03/11/2024 23:01:31 (29.067671298980713 seconds)"
(Yes, I know, I got a round problem 😄 )

Yea sorry, missing the seconds was my bad, I must have messed up rebuilding the UI.
Test looks good, but we dont have pytest as a dependency so looks like it is failing. I think we'll be going in the pytest direction in not too long a while, so feel free to add it to the dev dependencies (something like poetry add --group dev pytest)

Done,  pyproject.toml changes are readable, but I don't know about the poetry.lock ones.

Sorry, it was the wrong group, it was supposed to be added to "test", not "dev". I'll fix it in master. Thanks!


Gamepad stopped working

Hi,
Gamepad used to work but suddenly it stopped working. I'm not sure if the issue is with Photino or with the native WebView itself (maybe something updated there that needs an update from Photino side as well) but here's a super simple demo to illustrate the issue:
wwwroot/index.html:
<!DOCTYPE html>

<html lang="en" xmlns="http://www.w3.org/1999/xhtml">
<head>
    <meta charset="utf-8" />
    <title></title>
</head>
<body>
    <script>
        window.addEventListener("gamepadconnected", (e) => {
            alert("CONNECTED!");
            console.log("Gamepad connected at index %d: %s. %d buttons, %d axes.",
                e.gamepad.index, e.gamepad.id,
                e.gamepad.buttons.length, e.gamepad.axes.length);
        });
    </script>
</body>
</html>

Program.cs
using PhotinoNET;
using System.Drawing;

namespace HelloPhotino.ThreeD
{
    class Program
    {
        [STAThread]
        static void Main(string[] args)
        {
            string windowTitle = "Gamepad Test";
            var window = new PhotinoWindow()
                .SetTitle(windowTitle)
                .SetUseOsDefaultSize(false)
                .SetSize(new Size(700, 525))
                .Center()
                .SetResizable(false)
                .Load("wwwroot/index.html");
            window.WaitForClose();
        }
    }
}

If you run this in Photino, connect a gamepad, and try to use it, nothing happens.
If you start the exact same HTML either with a static files server or by serving it from filesystem (ie with 'file:///'), you'll see that once you use a gamepad, you see an alert saying "CONNECTED!" and details in the console log.
Now to clarify, its not just the gamepad event not firing, using navigator.getGamePads() or anything gamepad-related don't work either. As if it is no longer recognized (and it used to work perfectly in the past).
Can you please check?
Thanks :)

Seems to be issue with WebView in general and not Photino:
https://github.com/MicrosoftEdge/WebView2Feedback/issues/3025

Correct, as @RonenNess  mentioned this seems to be an issue with WebView2. Please follow the thread he linked above to see if/when it gets resolved. There's an explicit mention of Photino in the discussion thread already as well, as far as I have seen.


Level 20 scale values are not displayed on Species advancement

When creating a new Species any updates to scale values at level 20 are not displayed within the advancement UI. Tested in v4.1, Foundry 12.331

Happens for Backgrounds also.


chore(deps): update tubenhirn/semantic-release-github docker tag to v4.0.1

This PR contains the following updates:

Package
Update
Change

tubenhirn/semantic-release-github
patch
v4.0.0 -> v4.0.1

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.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

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

This PR has been generated by Renovate Bot.

:tada: This PR is included in version 4.4.4 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Closes #1248 fix broken readme links

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[ ] Code is formatted according to the tidyverse style guide
[ ] Updated relevant unit tests or have written new unit tests - See Unit Test Guide
[ ] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[ ] Update to all relevant roxygen headers and examples
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[ ] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[ ] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[ ] Address or fix all lintr warnings and errors - lintr::lint_package()
[ ] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue in the Development Section on the right hand side.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

@dinakar29 it looks to me like there is an issue with doing main/evel versions and our links now.  Any thoughts on how we can avoid these broken links?

This shouldn't be needed anymore, I've reverted the website configuration to its original state. Thanks for looking into this and proposing a fix, @shahronak47!


maestro: update from 1.36.0 to 1.37.9

Description of changes

https://github.com/mobile-dev-inc/maestro/blob/main/CHANGELOG.md
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.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.

Could you please update the commit message to maestro: 1.36.0 -> 1.37.9


ViewEncapsulation.Native Prevents Global Styles From Being Applied

Mac OS X 10.11.6
Chrome 53.0.2785.101
ng v1.0.0-beta.11-webpack.8

Using ViewEncapsulation.Native prevents global styles from being applied. Using ViewEncapsulation.Emulated or ViewEncapsulation.None works as expected.
Can the cli prepend something like /deep/ to global styles?

/deep/ is deprecated with native shadow dom

We won't automatically change global styles, no. This is a discussion best had in https://github.com/angular/angular though, since it's a general issue.


AttributeError: 'int' object has no attribute 'replace'

I'm trying to convert the following API:
https://start.camunda.com/openapi.json
However, I'm getting the error AttributeError: 'int' object has no attribute 'replace',
Stacktrace:
Traceback (most recent call last):
  File "/usr/local/bin/openapi-python-client", line 8, in <module>
    sys.exit(app())
  File "/usr/local/lib/python3.9/site-packages/typer/main.py", line 214, in __call__
    return get_command(self)(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/typer/main.py", line 497, in wrapper
    return callback(**use_params)  # type: ignore
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/cli.py", line 140, in generate
    errors = create_new_client(
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/__init__.py", line 296, in create_new_client
    project = _get_project_for_url_or_path(
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/__init__.py", line 269, in _get_project_for_url_or_path
    openapi = GeneratorData.from_dict(data_dict, config=config)
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/parser/openapi.py", line 333, in from_dict
    endpoint_collections_by_tag, schemas = EndpointCollection.from_data(
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/parser/openapi.py", line 45, in from_data
    endpoint, schemas = Endpoint.from_data(
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/parser/openapi.py", line 283, in from_data
    result, schemas = Endpoint._add_parameters(endpoint=endpoint, data=data, schemas=schemas, config=config)
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/parser/openapi.py", line 217, in _add_parameters
    prop, schemas = property_from_data(
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/parser/properties/__init__.py", line 539, in property_from_data
    return _property_from_data(
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/parser/properties/__init__.py", line 462, in _property_from_data
    return _string_based_property(name=name, required=required, data=data), schemas
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/parser/properties/__init__.py", line 266, in _string_based_property
    default=convert("str", data.default),
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/parser/properties/converter.py", line 33, in convert
    return _CONVERTERS[type_string](value)
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/parser/properties/converter.py", line 62, in _convert_string
    return f"{utils.remove_string_escapes(value)!r}"
  File "/usr/local/lib/python3.9/site-packages/openapi_python_client/utils.py", line 55, in remove_string_escapes
    return value.replace('"', r"\"")
AttributeError: 'int' object has no attribute 'replace'

Hey @adrianschneider94 thanks for reporting the issue! Looks like that exception is happening because there is a value of type "string" with a default that is a JSON number. I'll fix that so it doesn't crash anymore 😅. Unfortunately after fixing it locally there is a lot of your schema that doesn't get generated, looks like that's mostly because we don't support recursive models yet (see #338). Guess we'll keep bumping that one up in priority 😁


Can't build on Windows: syntax error near unexpected token `('

I did cargo build in curl-sys.
I wonder if it may be because I'm using sh.exe from Git.
running: make '-j4'
CDPATH="${ZSH_VERSION+.}:" && cd /c/dev/curl-rust/curl-sys/curl && C:/Program Files (x86)/Git/bin/sh.exe "/c/dev/curl-ru
st/curl-sys/curl/missing" --run autoconf
Makefile:738: recipe for target '/c/dev/curl-rust/curl-sys/curl/Makefile.in' failed
Makefile:766: recipe for target '/c/dev/curl-rust/curl-sys/curl/configure' failed

--- stderr
configure: WARNING: disabling built-in manual
"C:/Program Files (x86)/Git/bin/sh.exe": -c: line 4: syntax error near unexpected token `('
"C:/Program Files (x86)/Git/bin/sh.exe": -c: line 4: `      CDPATH="${ZSH_VERSION+.}:" && cd /c/dev/curl-rust/curl-sys/curl && C:/Program Files (x86)/Git/bin/sh.exe "/c/dev/curl-rust/curl-sys/curl/missing" --run automake-1.14 --foreign \'
"C:/Program Files (x86)/Git/bin/sh.exe": -c: line 0: syntax error near unexpected token `('
"C:/Program Files (x86)/Git/bin/sh.exe": -c: line 0: `CDPATH="${ZSH_VERSION+.}:" && cd /c/dev/curl-rust/curl-sys/curl &&
 C:/Program Files (x86)/Git/bin/sh.exe "/c/dev/curl-rust/curl-sys/curl/missing" --run autoconf'
make: *** [/c/dev/curl-rust/curl-sys/curl/Makefile.in] Error 258
make: *** Waiting for unfinished jobs....
make: *** [/c/dev/curl-rust/curl-sys/curl/configure] Error 258
task '<main>' panicked at 'assertion failed: cmd.stdout(InheritFd(1)).stderr(InheritFd(2)).status().unwrap().success()',
 build.rs:122

I'm going to close this for now as we haven't been able to reproduce. If there is more information and / or steps to fix, please open the ticket again. Thanks.


Add support for tvfplay.com

youtube-dl http://tvfplay.com/video/detail/477/TVF-Pitchers-S01E05-Where-Magic-Happens --verbose
[debug] System config: []
[debug] User config: []
[debug] Command-line args: ['http://tvfplay.com/video/detail/477/TVF-Pitchers-S01E05-Where-Magic-Happens', '--verbose']
[debug] Encodings: locale 'UTF-8', fs 'UTF-8', out 'UTF-8', pref: 'UTF-8'
[debug] youtube-dl version 2014.02.17
[debug] Python version 2.7.6 - Linux-3.16.0-50-generic-x86_64-with-Ubuntu-14.04-trusty
[debug] Proxy map: {}
[generic] TVF-Pitchers-S01E05-Where-Magic-Happens: Requesting header
WARNING: Falling back on generic information extractor.
[generic] TVF-Pitchers-S01E05-Where-Magic-Happens: Downloading webpage
[generic] TVF-Pitchers-S01E05-Where-Magic-Happens: Extracting information
ERROR: Unsupported URL: http://tvfplay.com/video/detail/477/TVF-Pitchers-S01E05-Where-Magic-Happens; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.
Traceback (most recent call last):
File "/usr/lib/python2.7/dist-packages/youtube_dl/YoutubeDL.py", line 493, in extract_info
ie_result = ie.extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/common.py", line 158, in extract
return self._real_extract(url)
File "/usr/lib/python2.7/dist-packages/youtube_dl/extractor/generic.py", line 380, in _real_extract
raise ExtractorError('Unsupported URL: %s' % url)
ExtractorError: Unsupported URL: http://tvfplay.com/video/detail/477/TVF-Pitchers-S01E05-Where-Magic-Happens; please report this issue on https://yt-dl.org/bug . Be sure to call youtube-dl with the --verbose flag and include its complete output. Make sure you are using the latest version; type  youtube-dl -U  to update.

@remitamine  Any google account would work.

9xbuddy.com is a site that can provide direct mp4 links to videos on TVFPlay.

I am working on adding support tvfplay.com. Can someone assign me this issue?

Any update? U just need to login with any google account

Any update? U just need to login with any google account

The 'need-account' tag means one needs to pay for the subscription (after logging into an account). Can't view anything with just an account.


Difference in Memory Budget

I’m currently utilizing the Memory Budget extension on my system. However, I’ve noticed a significant discrepancy between the usage displayed in the output and the actual value indicated by the Task Manager. Could this be an error, or is there another explanation for this difference?

Don't use the task manager for GPU statistics. It's often wrong or misleading. Compare with a proper tool, e.g. nvidia's overlay.

Okay Thanks @SaschaWillems . Got it.


fix: exposed credential

Harness Developer Pull Request
There seems to be a valid api key included in this page. @charanya-j
I have DMd the owner of the key and am looking up the API to revoke it using the key itself.
curl -s -X GET \
  'https://app.harness.io/gateway/ng/api/accounts/<redacted>?accountIdentifier=<redacted>' \
  -H 'x-api-key: <redacted>' | jq .

{
  "status": "SUCCESS",
  "data": {
    "identifier": "wFHXHD0RRQWoO8tIZT5YVw",
    "name": "Harness.io",
    "companyName": "Harness.io",
    "cluster": "prod-1",
    "defaultExperience": "CG",
    "authenticationMechanism": "USER_PASSWORD",
    "nextGenEnabled": true,
    "productLed": true,
    "twoFactorAdminEnforced": false
  },
  "metaData": null,
  "correlationId": "ca1aa2af-7b16-406b-b8bb-f34d0cde8393"
}

What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Preview environment: https://ci.pr.harness.io/pr-670


Exclude the issue owner's own comment from first response

I think the comments of the owner of the issue themselves should be excluded from Time to first response.
Because they will add something that they forgot to write in the body of the Issue, or make additional comments to supplement the body of the Issue(like #26).
We could modify it as the default behavior, but if we are more cautious, we might add an option like IGNORE_OWNER_COMMENT.

I think that changing default behavior is okay in this case. Great catch on this situation. I normally modify my issue descriptions rather than comment to add more information so I wouldn't have thought of this one. I'm sure lots of people comment like described.


Footer section is buggy

Description
Hey @SauravMukherjee44 One of the animation in footer section is buggy. I have attached video for the same. Can you please assign me this issue to fix it. Anyway the animation doesn't look great! Thank you!
Screenshots
screen-capture.webm

hey @sumitkr2000 you can assign this issue to me I can work on it.

@HoneyTyagii No I will work on it as as asked it first! but they are not assigning it to me :(

@SauravMukherjee44 Hoping to get a reply!

Hello @sumitkr2000 , someone else is working on this at #548
If they are unable to make all changes, you can make an issue after that.
For now, closing the issue.


Used short license and bumped deps

Used short license and bumped asto and http

@g4s8 please, check/merge

@rultor release, tag=0.4.2

@olenagerasimova OK, I will release it now. Please check the progress here

@rultor release, tag=0.4.2

@olenagerasimova Done! FYI, the full log is here (took me 8min)


Error

Traceback (most recent call last):
File "C:\Users\Dylan\Downloads\selfbot-master\selfbot-master\zeenode\launch.py", line 2, in
from zeenode.load import load
File "C:\Users\Dylan\Downloads\selfbot-master\selfbot-master\zeenode\zeenode\load.py", line 3, in
from discord.ext import commands as zeenode
ImportError: cannot import name 'commands' from 'discord.ext' (unknown location)

download discord bro


⚠ Bofrost.de has degraded performance

In 7e6359c, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 947 ms

Resolved: Bofrost.de performance has improved in 9dc2e0b after 11 minutes.


Add Nested Types List and Map for Python UDF support

This pull request adds list and map support for UDF
There are two ways to denote nested types in our signatures:

Annotation
eg: def f(x : list) -> list[int]
Only the returned type must be fully annotated (ie. its child type(s) are declared)
Explicit declaration
eg: conn.create_function("myfunction", f, [Type.LIST], "INT64[]")
As with the above example, only the return type must be fully annotated. Full annotation does not make use of the kuzu.Type enumeration. Instead, it must be given as a complete string.

i tried the following script:
import sys

sys.path.append('/Users/z473chen/Desktop/code/kuzu/tools/python_api/build')

import kuzu
from kuzu import Type

db = kuzu.Database("./test")
conn = kuzu.Connection(db)

def add5(x: int) -> int:
    return x + 5

conn.create_function("add6", add5)
print(conn.execute("return add5(2)").get_as_df())

But i got the following error:
Traceback (most recent call last):
  File "/Users/z473chen/PycharmProjects/pythonProject9/3.py", line 15, in <module>
    conn.create_function("add6", add5)
  File "/Users/z473chen/Desktop/code/kuzu/tools/python_api/build/kuzu/connection.py", line 260, in create_function
    self._connection.create_function(name, udf, parsed_params_type, return_type)
TypeError: signature() got an unexpected keyword argument 'eval_str'

We should give meaning error message in this case.
BTW: Can you add docs about how to use python UDF? Looks like our usage is different from duckdb

This seems to be a result of older python versions (<3.10), but I can fix this. The error message I get is Catalog exception: function ADD5 does not exist.

i tried the following script:
import sys

sys.path.append('/Users/z473chen/Desktop/code/kuzu/tools/python_api/build')

import kuzu
from kuzu import Type

db = kuzu.Database("./test")
conn = kuzu.Connection(db)

def add5(x: int) -> int:
    return x + 5

conn.create_function("add6", add5)
print(conn.execute("return add5(2)").get_as_df())

But i got the following error:
Traceback (most recent call last):
  File "/Users/z473chen/PycharmProjects/pythonProject9/3.py", line 15, in <module>
    conn.create_function("add6", add5)
  File "/Users/z473chen/Desktop/code/kuzu/tools/python_api/build/kuzu/connection.py", line 260, in create_function
    self._connection.create_function(name, udf, parsed_params_type, return_type)
TypeError: signature() got an unexpected keyword argument 'eval_str'

We should give meaning error message in this case.
BTW: Can you add docs about how to use python UDF? Looks like our usage is different from duckdb

This seems to be a result of older python versions (<3.10), but I can fix this. The error message I get is Catalog exception: function ADD5 does not exist.

My python version is:
➜  duckdb git:(v0.10.1) ✗ python3 --version
Python 3.9.6

3.9.6 is still a mainstream python version.

@mxwli You could look at adding preliminary docs in Markdown in this file and sending a PR - I'll test out what I can in the code and make any updates to the PR as needed.
https://github.com/kuzudb/kuzu-docs/blob/main/src/content/docs/client-apis/python.mdx

def add5(x: str) -> int:
    return x + 5

conn.create_function("add6", add5)
print(conn.execute("return add6(2)").get_as_df())

Is this the expected behaviour? The python type Annotation suggests that the input parameter should be a string but the given parameter is 2. The function still returns correct result.

This isn't expected, but it's a side effect of an intentional change I made in this PR. I'll have to make more changes to the API here.


Adds minor changes(license year and clean-up step) to Sdk automl video action recognition batch notebook

checklist for opening a PR for Official Notebooks under the notebooks/official folder :

[x] Use the notebook template as a starting point.
[x] Follow the style and grammar rules outlined in the above notebook template.
[x] Verify the notebook runs successfully in Colab since the automated tests cannot guarantee this even when it passes.
[x] Passes all the required automated checks. You can locally test for formatting and linting with these instructions.
[ ] You have consulted with a tech writer to see if tech writer review is necessary. If so, the notebook has been reviewed by a tech writer, and they have approved it.
[x] This notebook has been added to the CODEOWNERS file under # Official Notebooks section, pointing to the author or the author's team.
[x] The Jupyter notebook cleans up any artifacts it has created (datasets, ML models, endpoints, etc) so as not to eat up unnecessary resources.

/gcbrun


Fix Subscribe RPC to correctly distinguish bids and asks.

Found by Mickey!
See here:
https://github.com/ripple/rippled/commit/6014b132348bc51af658285cf2d385bc504deb6d#diff-e33c82fefe08b47268c75bbbd4bd054cL311
Note that there are apparently no tests for Subscribe - I filed a JIRA for this: https://ripplelabs.atlassian.net/browse/RIPD-740

Reviewers: @miguelportilla @ximinez

Nice fix to this problem, Tom. LGTM +1

Clever fix. :+1:
Builds, and unit and JS tests pass in Windows. Not that that helps much in this case.

Pushed a new version with Vinnie's reversed suggestion.

I cherry picked your fix,Tom.

Closing this in favor of Mickey's branch.


Setting MJ-container color prevents components from being dropped in view

The issue occurs on the demo as well. If you set the container color, it appears like you can't drop any section blocks on the canvas. Content blocks like image and text are working. After further inspection in the mjml code, it's clear the components are being added to the template.
Steps to reproduce

Any template works
set the container color
Add new blocks
Check code. The blocks will be there but they will not appear in editor.

@masfi
Fixed in v0.1.5 ab4f042


Use local copy of Intel AVS topology build instead of fetching from GitHub

Archive with built topology files was removed from releases at https://github.com/thesofproject/avs-topology-xml/ after merging them into linux-firmware repo. This commit adds a local copy of the tarball and uses it while installing AVS support.
Proper fix would be to install newer version of linux-firmware package (>= 20240811), but on Debian-based system this package was split into smaller ones, requiring additional work to include these new blobs.
Fixes #159 and #168.

For additional context, this change was tested on SNAPPY with Debian 12.6 installed.


Spec error "There aren't targets available" on Windows 7

Hi, I'm using Ferrum 0.2.1 on Windows 7 Professional SP1.  I tried running the first "save a screenshot" example from README.md, and I get the error "There aren't targets available (Ferrum::EmptyTargetsError)"
I get the same error running the specs:
C:\ferrum-master>bundle exec rake
C:/Ruby/Ruby255-x64/bin/ruby.exe -I'C:/Ruby/Ruby255-x64/lib/ruby/gems/2.5.0/gems/rspec-core-3.8.2/lib';'C:/Ruby/Ruby255-x64/lib/ruby/g
ems/2.5.0/gems/rspec-support-3.8.2/lib' 'C:/Ruby/Ruby255-x64/lib/ruby/gems/2.5.0/gems/rspec-core-3.8.2/exe/rspec' --pattern 'spec/**{,/*/*
*}/*_spec.rb'
Starting Puma
* Version 4.1.0 , codename: Fourth and One
* Min threads: 0, max threads: 4
* Listening on tcp://<IP_ADDRESS>:60259

basic http authentication
  denies without credentials (FAILED - 1)

Failures:

  1) basic http authentication denies without credentials
     Got 0 failures and 2 other errors:

     1.1) Failure/Error: raise EmptyTargetsError if targets.empty?

          Ferrum::EmptyTargetsError:
            There aren't targets available
          # ./lib/ferrum/targets.rb:110:in `block in targets'
          # ./lib/ferrum.rb:95:in `with_attempts'
          # ./lib/ferrum/targets.rb:105:in `targets'
          # ./lib/ferrum/targets.rb:12:in `initialize'
          # ./lib/ferrum/browser.rb:109:in `new'
          # ./lib/ferrum/browser.rb:109:in `targets'
          # ./spec/browser/basic_auth_spec.rb:8:in `block (2 levels) in <module:Ferrum>'

     1.2) Failure/Error: raise EmptyTargetsError if targets.empty?

          Ferrum::EmptyTargetsError:
            There aren't targets available
          # ./lib/ferrum/targets.rb:110:in `block in targets'
          # ./lib/ferrum.rb:95:in `with_attempts'
          # ./lib/ferrum/targets.rb:105:in `targets'
          # ./lib/ferrum/targets.rb:12:in `initialize'
          # ./lib/ferrum/browser.rb:109:in `new'
          # ./lib/ferrum/browser.rb:109:in `targets'
          # ./lib/ferrum/browser.rb:94:in `reset'
          # ./spec/spec_helper.rb:58:in `block (2 levels) in <top (required)>'

Finished in 1.8 seconds (files took 2.23 seconds to load)
1 example, 1 failure

Failed examples:

rspec ./spec/browser/basic_auth_spec.rb:7 # basic http authentication denies without credentials

C:/Ruby/Ruby255-x64/bin/ruby.exe -I'C:/Ruby/Ruby255-x64/lib/ruby/gems/2.5.0/gems/rspec-core-3.8.2/lib';'C:/Ruby/Ruby255-x64/lib/ruby/g
ems/2.5.0/gems/rspec-support-3.8.2/lib' 'C:/Ruby/Ruby255-x64/lib/ruby/gems/2.5.0/gems/rspec-core-3.8.2/exe/rspec' --pattern 'spec/**{,/*/*
*}/*_spec.rb' failed

C:\ferrum-master>ruby -v
ruby 2.5.5p157 (2019-03-15 revision 67260) [x64-mingw32]

Thanks for any assistance!

What Chrome version are you using by the way?

Version 76.0.3809.132 (Official Build) (64-bit)  (the current version)
I checked, and exactly the same 2 spec failures occur on Windows 10 Pro version 1803 (current fully patched Windows 10 version), same version of Chrome.

Confirming that for some reason Chrome doesn't start properly on Windows 10, but looks like even if I skip this check for targets and we create page it crashes nevertheless, though interesting thing is that when I pass headless: false flag Chrome starts...

Thanks!  As you pointed out, puppeteer has some similar-sounding issues on Windows.  I'll look into running ferrum on a different OS.

@hyperlexie using branch gem "ferrum, github:"route/ferrum", branch: "add-contexts" and this code seems to be fixed the issue:
require "ferrum"

browser = Ferrum::Browser.new(browser_path: "C:\\Program Files (x86)\\Google\\Chrome\\Application\\chrome.exe", logger: STDOUT, browser_options: { 'no-sandbox': nil })
browser.goto("https://google.com")
browser.screenshot(path: "google.png")
browser.quit

I'm going to merge it soon, it's not windows fix, it's added API for contexts.

@route WOW!  I tried running your 0.4 gem with the code you provided.
On Windows 7, the first 4 times I got a timeout.  I set timeout: 10, and the next 4 times it ran successfully, producing the google.png file.
I was a little surprised to get the timeouts, as this is a 3 year old laptop that's reasonably fast: Core i7 2.6GHz, 64 GB RAM, 2 SSDs in RAID 0, high speed internet connection.
On Windows 10 (without the :timeout parameter) the first time I got the timeout.  The next time I got "There aren't targets available" (see below), and the next 2 times it ran successfully and produced google.png.  (I never did set the timeout).  Nothing changed between the runs, just run, run, run, run.  I'm guessing the first timeout got resolved by caching somewhere. This is on a 7 year old laptop that's getting pretty sluggish.
I'm very glad to see this basically working.  Thank you!!!
▶ 0.9767789228353649 {"method":"Target.getTargets","params":{},"id":2}
    ◀ 0.9909544929396361 {"id":2,"result":{"targetInfos":[]}}

▶ 1.0229625208303332 {"method":"Target.getTargets","params":{},"id":3}
    ◀ 1.1605821179691702 {"id":3,"result":{"targetInfos":[]}}
 (most recent call last):
        8: from C:/Users/hyperlexie/RubymineProjects/ferrum_test_2/main.rb:4:in `<main>'

        7: from C:/Ruby/Ruby250-2-x64/lib/ruby/2.5.0/forwardable.rb:223:in `goto'

        6: from C:/Ruby/Ruby250-2-x64/lib/ruby/2.5.0/forwardable.rb:223:in `page'

        5: from C:/Ruby/Ruby250-2-x64/lib/ruby/gems/2.5.0/gems/ferrum-0.4/lib/ferrum/browser.rb:100:in `targets'
        4: from C:/Ruby/Ruby250-2-x64/lib/ruby/gems/2.5.0/gems/ferrum-0.4/lib/ferrum/browser.rb:100:in `new'
        3: from C:/Ruby/Ruby250-2-x64/lib/ruby/gems/2.5.0/gems/ferrum-0.4/lib/ferrum/targets.rb:12:in `initialize'
        2: from C:/Ruby/Ruby250-2-x64/lib/ruby/gems/2.5.0/gems/ferrum-0.4/lib/ferrum/targets.rb:105:in `targets'
        1: from C:/Ruby/Ruby250-2-x64/lib/ruby/gems/2.5.0/gems/ferrum-0.4/lib/ferrum.rb:110:in `with_attempts'
C:/Ruby/Ruby250-2-x64/lib/ruby/gems/2.5.0/gems/ferrum-0.4/lib/ferrum/targets.rb:110:in `block in targets': There aren't targets available (Ferrum::EmptyTargetsError)

Process finished with exit code 1

@hyperlexie I'll release new version soon, it works with targets slightly different so there shouldn't be EmptyTargetsError anymore.
The key is no-sandbox, I guess timeout option is not needed.
I added it because first time I also got timeout but next run it was fine. From the log I noticed that when Ferrum called goto it stuck because it never got response back. Dunno but it is something Chrome + Windows related and doesn't depend on CPU. I have very powerful 8700K but it bit me either.


A draft for supporting multiple search paths

Currently, wetzel offers an option for additional search paths:

The -s option lets you specify the path string that should be used when loading the schema reference paths.

This could be extended in order to support multiple search paths.
This PR is a DRAFT, for discussing whether (and how) this should be implemented.
The change might raise questions:

Is there backward compatibility on the command line level?
Callers might already use the -s/-searchPath parameter, and this should probably still work (for single paths) in the future. I introduced a -S/-searchPaths parameter (uppercase/plural), for the case that an array of search paths should be given. Alternatively, the original -s parameter could be removed or replaced by the -S parameter, or it could try to either accept a single string or an array as the value for -s, or print a warning or error...
Is there backward compatibility on the API level?
The options object contained a searchPath field. This was passed to downstream functions with the name seachPath. But it actually already stored an array, and therefore, should be renamed to searchPaths (plural).
Should this be covered with unit tests?
The functionality of the -s parameter is not tested right now. Iff the functionality of the searchPath/searchPaths parameter should be tested, then it will be necessary to create a test schema, split into multiple directories. (It's not yet clear how well this could be covered with the current testing code...)

Regarding the question

Should this be covered with unit tests?

I added an additionalOptions property in the test setup, for specifying ... well, additional options (like a single search path, or multiple search paths).
But ... more work will be necessary in order to handle these search paths properly - regardless of whether it's a single one, or multiple: The output usually contains a link to the schema file, as in
* **JSON schema**: [searchPathsExternalA.schema.json](schema/searchPathsExternalA.schema.json)
And the schema/ directory always is the schemaRelativeBasePath that was given as the -p command line option. So when a $ref is only found via the search path, this link will be wrong...

This is obsolete due to a larger refactoring at https://github.com/javagl/wetzel/tree/generate-3dtiles


proposal syntax else ... then for else keyword in conditional branchs

examples in tutorial
if a == b then
  env.out.print("they are the same")
else
  if a > b then
    env.out.print("a is bigger")
  else
    env.out.print("b bigger")
  end
end

limited by set pattern in old school
if a == b then
  env.out.print("they are the same")
elseif a > b then
  env.out.print("a is bigger")
else
  env.out.print("b bigger")
end

just use "else ... then" instead of "elseif ... then"
if a == b then
  env.out.print("they are the same")
else a > b then
  env.out.print("a is bigger")
else
  env.out.print("b bigger")
end

And it is ok in expressions
x = 1 + if lots then 100 else afew then 10 else 2 end

And there is almost no additional cost for parsing.

This should be opened using the rfc process.
https://github.com/ponylang/rfcs

moved to rfcs#207


[Open source] Exchangis1.0 field mapping is not refreshed.

After changing the library table of the data source, the field mapping has not changed dynamically, and the back-end has returned the new field mapping value normally.
更换数据源的库表之后，字段映射并没有相应的动态改动，此时后端已经正常返回了新的字段映射值

https://github.com/WeBankFinTech/Exchangis/pull/282，这个pr解决了


feat: remove lodash

Pull Request Test Coverage Report for Build 29ed7a1f0f9973e6c7fa738659d7a75777ea944d-PR-8
Details

11 of 11 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.2%) to 94.251%

Totals

Change from base Build 8b8113ef039bce9e2d10bcc00a2b9f3bf02921c7:
0.2%

Covered Lines:
353

Relevant Lines:
367

💛  - Coveralls


Topic Model API Refactor

This should address #164 and provide a cleaner API for dealing with the results of a topic model. The lda-topics tool has been updated to use this new API.

Lots of conflicts here; not sure what happened. Can you rebase your changes on top of the latest develop branch?
This is what i would do: take your fork, switch to the develop branch and do a pull against this repository to update it. Then make a new branch for your commits from there, and then use git cherry-pick to add your commits to that new branch. Then you should be able to make a clean PR against develop here without conflicts so the CI can test things.


Unable to get automatically generated tickValues on axis

If we set the number of required ticks on fc.svg.axs() we can't get the actual tickValues returned.
The behaviour is demonstrated [here.] (http://codepen.io/rjmcneill/pen/aNoLKY?editors=0011)
I have 4 solutions, and I'm happy to submit a PR if you think any are along the right lines.

[One] (https://github.com/rjmcneill/d3fc/tree/bug/tick-values-1)
[Two] (https://github.com/rjmcneill/d3fc/tree/bug/tick-values-2)
[Three] (https://github.com/rjmcneill/d3fc/tree/bug/tick-values-3)
[Four] (https://github.com/rjmcneill/d3fc/tree/bug/tick-values-4)

The existing behavior seems consistent with d3 -
https://github.com/mbostock/d3/wiki/SVG-Axes#tickValues
On Thu, 25 Feb 2016 at 16:16 Robert James McNeill<EMAIL_ADDRESS>wrote:

If we set the number of required ticks on fc.svg.axs() we can't get the
actual tickValues returned.
The behaviour is demonstrated here.
http://codepen.io/rjmcneill/pen/aNoLKY?editors=0011
I have 4 solutions, and I'm happy to submit a PR if you think any are
along the right lines.

One https://github.com/rjmcneill/d3fc/tree/bug/tick-values-1
Two https://github.com/rjmcneill/d3fc/tree/bug/tick-values-2
Three https://github.com/rjmcneill/d3fc/tree/bug/tick-values-3
Four https://github.com/rjmcneill/d3fc/tree/bug/tick-values-4

—
Reply to this email directly or view it on GitHub
https://github.com/ScottLogic/d3fc/issues/914.

The axis delegates to the scale to determine the ticks - so how about obtaining them as follows:
dateAxis.scale().ticks()

Thanks for the feedback @chrisprice and @ColinEberhardt.
Obtaining them through scale seems like a good solution.
Cheers!

No problem :-)


ignore a (potentially) unused import in generated code

ignore a (potentially) unused import in generated code

When using plugins, a flutter packages get will generate lib/generated_plugin_registrant.dart in the project. This file can potentially contain analysis warnings; specifically, about unused imports:
Unused import: 'dart:ui'.

This PR ensures that the generated file does not introduce new analysis warnings to the project.

I'll try updating to the latest -


Adds EditorConfig file which should be supported by all editor around

http://editorconfig.org/ for editor plugin list to install

Notes:

disabled for js until grunt lintspaces fixed https://github.com/schorfES/grunt-lintspaces/issues/21 (better we make a PR on their github so that it's fixed faster)
Didn't add it to check as there is currently glsl error . Do I fix them in this PR ?

unning "lintspaces:external" (lintspaces) task
☓ examples/earlyz/fragment.glsl
  L55: Expected an indentation at 24 instead of at 23.
☓ sources/osgShader/node/functions.glsl
  L98: Expected an indentation at 6 instead of at 5.
☓ sources/osgShader/node/lights.glsl
  L45: Expected an indentation at 30 instead of at 29.
  L46: Expected an indentation at 30 instead of at 29.
  L48: Expected an indentation at 30 instead of at 29.
  L49: Expected an indentation at 30 instead of at 29.
  L50: Expected an indentation at 30 instead of at 29.
  L51: Expected an indentation at 30 instead of at 29.
  L53: Expected an indentation at 30 instead of at 29.
  L54: Expected an indentation at 30 instead of at 29.
  L55: Expected an indentation at 30 instead of at 29.
  L57: Expected an indentation at 30 instead of at 29.
  L58: Expected an indentation at 30 instead of at 29.
  L59: Expected an indentation at 30 instead of at 29.
  L60: Expected an indentation at 30 instead of at 29.
  L61: Expected an indentation at 30 instead of at 29.
  L63: Expected an indentation at 30 instead of at 29.
  L64: Expected an indentation at 30 instead of at 29.
  L66: Expected an indentation at 30 instead of at 29.
  L67: Expected an indentation at 30 instead of at 29.
  L68: Expected an indentation at 30 instead of at 29.
  L69: Expected an indentation at 30 instead of at 29.

if it fails just disable grunt check

is it still useful if we use eslint ?

needs a rebase


Allow the s3Key (AWS_LAMBDA_S3_KEY) to be specified

This case is a bit different than the rest because the fallback value is actually already in sbt's task graph (the jar name).
Also I opted for using the ? operator on SettingKey instead of defining the key to be Option[String]. Just because I think it's a more pleasant user-experience, but it doesn't have to stay this way. I can either revert to Option, leave it as is, or change all of them to not be option (massive breaking change, but would make all the keys consistent). I'm happy to do either, just presenting this way as my preference.

Hold on jar is already there.

Ok, I've re-done the feature to be for s3KeyPrefix / AWS_LAMBDA_S3_KEY_PREFIX.
It's still using String and .?, which I can change if you prefer. Let me know, and also it would be lovely (for me) if, following this being accepted and merged, a release could be cut and published :)

Once more, with more of that "it can actually compile" property.

👍


How to add labels to the next/previous month buttons for TalkBack?

When using the TalkBack screen reader the buttons that indicate the next or previous month read as unlabelled (e.g. Button 69 unlabeleed, Button 47 unlabelled).
Is there a way to assign the values Next Month and Previous Month to these buttons?
The screenshot shows the calendar with TalkBack enabled and focussed on the previous button, and the overlay shows the text TB reads out.

This issue has been fixed and is available in the 1.3 snapshot. Stay tuned for the next release.You can try the 1.3 snapshot with the instructions in README. Enjoy and report issues!

Public APIs were added: setContentDescriptionArrowPast, setContentDescriptionArrowFuture, setContentDescriptionCalendar with 1.3


A problem in urgent need of repair

Whenever there is an icon increase or decrease in the notification area, the centered icon will return to the beginning, and then center again, which greatly affects the experience. I hope it can be repaired as soon as possible. Thank you

I had that fixed a long time ago. Any other applications installed that alter the taskbar?
I also can't reproduce it on any of my testing systems.

I don't have this issue either.

could it be the cpu monitor task bar object that could be interfering here?


Add an option to set the revision for local analysis. [phab:D1379]

Created by fromberger at 2017-02-25 00:40:40:
In the queue implementation for kindex files, add an option to allow the
revision marker to be set. This is done as a variadic argument to the
constructor to avoid needing to change existing call sites.

craigbarber wrote at 2017-02-27 21:23:18:
Does this work with the changes schroederc introduced in #1784?

fromberger wrote at 2017-02-27 22:11:54:

! In (earlier comment), craigbarber wrote:
Does this work with the changes schroederc introduced in #1784?

Yes, in the sense that they're orthogonal (the presence or absence of the field doesn't affect this change).

craigbarber accepted this revision at 2017-02-27 22:44:02

fromberger closed via commit 641e584bea12b61730c9bc30a32746af4b9bebda at 2017-02-27 22:57:14


Update User.php

Reset guarded fields, because we use $fillable instead.
related to https://github.com/rainlab/userplus-plugin/pull/35#issuecomment-622323509
related to:
https://github.com/rainlab/user-plugin/pull/33
https://github.com/rainlab/userplus-plugin/pull/35
https://github.com/rainlab/location-plugin/issues/52
fixes:
https://github.com/rainlab/userplus-plugin/issues/34

@TimFoerster can you confirm that this fix does in fact resolve the issue you had with the UserPlus plugin not allowing the Location plugin fields to be fillable?

@TimFoerster can you confirm that this fix does in fact resolve the issue you had with the UserPlus plugin not allowing the Location plugin fields to be fillable?

I confirm.

@bennothommo LGTM!


Remove unused restricted sun import package

There was an import (unused) for a restricted sun package. This request removes that and other unused imports from the class.
My contributions are licensed under the Apache 2.0 License as required for contributions to this project

Pulled, pending sync.


Exclude qps_test from tsan runs

The TSAN deadlock detector has some problems that prevents this test
from running successfully.
Issue #2994 has been filed to re-enable these in the future.

tsan is still failing for c: https://grpc-testing.appspot.com/job/gRPC_pull_requests/2205/config=tsan,language=c,platform=linux/console

One bug at a time
On Wed, Aug 19, 2015, 8:36 PM David G. Quintas<EMAIL_ADDRESS>wrote:

tsan is still failing for c:
https://grpc-testing.appspot.com/job/gRPC_pull_requests/2205/config=tsan,language=c,platform=linux/console
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/pull/2995#issuecomment-132875050.


Make Keylime easily deployable on Kubernetes/Openshift

After several discussions with @mpeters @ansasaki Lukas Vrabec @galmasi and Marcus Hesse, we collectively decided that the time to have Keylime easily deployed on Kubernetes/Openshift has come. I propose we use this issue to concentrate all the relevant discussion on this topic.
I will start by listing some common relevant points, and I do thank Marcus Hesse for starting the discussion on the keylime-operator on CNCF's Slack. I believe I have addressed most of your questions on this writeup.
The main goal is to end with an "Attestation Operator", which can not only automatically add nodes (i.e., agents) to specific verifiers but can also properly react to administrative activities such as node reboots or cordoning off.
I am not an Kubernetes/Openshift expert by any means, and therefore my proposal here is bound to be incomplete/incorrect, and therefore additions/corrects are welcome. That being said, I see  the following set of intermediate steps, in increasing order of complexity, as a good way to achieve our goal.

Ensure that all keylime components can be fully executed in an containerized manner. For this the following requirements should be satisfied.
a. Unmodified public images. I suggest we expand https://quay.io/organization/keylime (under Red Hat's control), already offering the "latest"  verifier, registrar and tenant to also include the rust agent image (@ansasaki is pursing this)
b. Carefully determine the least amount of (container) privileges will be required to run the agent
c. Provide some tool to perform containerized keylime deployments (@maugustosilva and @galmasi have a tool, which is about to be released into open-source, to perform this task).

Create a simple Kubernetes application for keylime. At this point, we should be able to start by writing progressively more yaml files
a. The idea is to start with very simple Deployment with the following objects:
* AStatefulSet (initially of 1) for the Registrar
* AStatefulSet (initially of 1) for the Verifier
* A DaemonSet for the Agents
* Both exposed as Service (type=NodePort)
* mTLS certificates stored as Secrets
* Given the fact keylime can be fully configured via environment variables, we shall use environment dependent variables on our yaml.
b. Initially, I propose we make the following simplifying boundary conditions
* Given the use of the sqlite we could start without any DB deployment
* mTLS certificates are pre-generated (with keyime_ca commands) and added to the Kubernetes cluster
* Environment variables will be also set and maintained by some external tool
* The tenant will NOT be part of the initial deployment.
* Make use of the "Node Feature Discovery" to mark all the nodes with tpm devices (and make it part of the DaemonSet node selector)
c. From this point we should expand for an "scale-out" deployment.
* Multiple Registrars and Verifiers
* A pre-packaged helm deployment of some SQL database server will be used.
* A Service (type=LoadBalancer)
d. At this point, the following technical considerations should be made.
* I am hoping we can "get away" with a pre-packaged n-way replicated SQL DB server.
* Verifiers are identified by a "verifier ID", which I assume can be take from the "persistent identifier within a StatefulSet"
* The load balancing algorithm will have to use the URI (which contains the agent UUID) for the selection of the backend (i.e., we cannot use round-robin or source IP, given that presently a single tenant will add all the agents to the set of verifiers)
* Tenant is still considered as a component outside of the whole deployment

Create an Operator for keylime. My experience writing operators is fairly limited, but I will point out some of the desirable characteristics:

Ability to automatically generate all pertinent certificates
Ability to deal with environment variables
Ability to automatically add agents to verifiers
Ability to react to administrative tasks on node, such as reboot, drainage, cordoning off.

Make the Operator more "production-ready"

How to deal with (measured boot and runtime/IMA) policies?
How to deal with "scale-out" operations (i.e., if the number of verifier pods increase, should we perform "rebalancing")?
How to integrate "durable attestation" on this scenario?

The majority of the aforementioned stakeholders (@maugustosilva @mpeters @ansasaki Lukas Vrabec @galmasi and Marcus Hesse) voted for having this worked developed on a new repository within the keylime project. I will create such repository.

Copied this issue, as is, to https://github.com/keylime/attestation-operator/issues/1

We reach a point where we have an actually functional "base" Keylime deployment (via helm) at https://github.com/keylime/attestation-operator . This issue can be closed.


scrollbar in ios10 is not showing but works in ios 11

setting scrollbars: true in options shows the scrollbar in iOS 11 (iPhone 7)
But iOS 10 (iPhone 5s) is not having any scrollbar but it scrolls.
Observed that the scroll related element having class ".iScrollVerticalScrollbar .iScrollLoneScrollbar" is not added in the dom.

It works prefectly fine. I missed scrollbar flag in one scenario.
Thanks.


Issue-91: Added Jupyter, image and readme files for hole detection

Issue-91: Added Jupyter, image and readme files for hole detection.
Hole detection is done through OpenCV, grayscaling, Gaussian blur, blob detection.

#91

Hey @srimontidutta, which Image Processing technique have you used here?


Added 'files' api methods

Codecov Report

Merging #185 (16e1c84) into master (bbc4586) will decrease coverage by 0.13%.
The diff coverage is 13.15%.

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


New version: GPUCompiler v0.9.1

Registering package: GPUCompiler
Repository: https://github.com/JuliaGPU/GPUCompiler.jl
Created by: @jpsamaroo
Version: v0.9.1
Commit: b8dba94c14957cd6aab41c50d3afb43f1d52dc73
Reviewed by: @jpsamaroo
Reference: https://github.com/JuliaGPU/GPUCompiler.jl/commit/b8dba94c14957cd6aab41c50d3afb43f1d52dc73#commitcomment-45213833

[noblock]
Package is 1.6 only.

Could I get a manual merge? Tests are passing on master with 1.6, and I need this for #26429


Create logic for price calculator

We have the average prices for all the options (except direct cremation #2 ) based on a basic regional breakdown.

closing issue as was done in last sprint


Allow to scrape views and present them in tables

In addition to graphs and single metrics, it would be good if this datasource also offers the possibility to retrieve views and display them in a table.
Example: To show services with issues on a dashboard, I would like to create specific views with filters in Check_MK and present them in Grafana via the table visualization panel. We are currently implementing this using iFrames, which are unfortunately very inflexible.

Hi Fabian,
at the current state and looking at our internal projects, it is not very likely that this enhancement will find his way into the connector. Even though it would be useful. So, I'm sorry to say, that I need to close this issue.


Adds request ID to archive download request.

Fixes #16.

Coverage remained the same at 100.0% when pulling 53261c5e380fdec04b4ba479b9e55700e4ea093d on AndreLouisCaron:download-request-id into 2ca4062859f9a95861fcc3867c6d3e7b3f3164f8 on smartmob-project:master.


Adapt swyxkit page with Windi CSS

References:

https://github.com/sw-yx/swyxkit
https://swyxkit.netlify.app/foo
https://windicss.org/integrations/vite.html
https://stackoverflow.com/questions/69601626/windi-css-hmr-not-working-for-svelte-vite-app

https://github.com/sw-yx/swyxkit/blob/main/src/routes/[slug].svelte#L41


Remove 'unsafe-eval' in CSP guidance

Fixes #29293
Mackinnon ... I see that Pavel is still working on runtime bits, but it is ok to knock this out for preview coverage now?
It's not easy to see from the diff because it's adding versioned content. The changes here are to ...

Remove the following line ...

* Specify `unsafe-eval` to permit the Blazor WebAssembly Mono runtime to function.

Change part of the WASM policy from ...

script-src 'self'
           'unsafe-eval';

... to ...

script-src 'self';

Internal previews

📄 File
🔗 Preview link

aspnetcore/blazor/security/content-security-policy.md
Enforce a Content Security Policy for ASP.NET Core Blazor

@guardrex While 'unsafe-eval' is no longer required, 'wasm-unsafe-eval' is required instead (because WebAssembly execution is disabled without it). See https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy/script-src#unsafe_webassembly_execution.

@MackinnonBuck ... Ok ... I put that on the last commit.

@MackinnonBuck  unsafe-eval is still required due to the blazor js script. I get errors when I test this with the latest preview
Did I miss something?
Greetings Damien

@damienbod ... I recommend posting the rendered meta tags built by Lock's API and to show the errors.

Here's the error
Error:

browserLink:153 Refused to apply inline style because it violates the following Content Security Policy directive: "style-src 'self'". Either the 'unsafe-inline' keyword, a hash ('sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU='), or a nonce ('nonce-...') is required to enable inline execution.

I can't see any difference in the CSP which is strange.

Error:
blazor.webassembly.js:1 EvalError: Refused to evaluate a string as JavaScript because 'unsafe-eval' is not an allowed source of script in the following Content Security Policy directive: "script-src 'self' 'sha256-v8v3RKRPmN4odZ1CWM5gw80QKPCCWMcpNeOmimNL2AA=' 'wasm-unsafe-eval'".
at Function (<anonymous>)
at dotnet.8.0.0-preview.3.23174.8.b7g991eq1o.js:3:165575
at sc (dotnet.8.0.0-preview.3.23174.8.b7g991eq1o.js:3:165596)
at dotnet.8.0.0-preview.3.23174.8.b7g991eq1o.js:3:168598
at ic (dotnet.8.0.0-preview.3.23174.8.b7g991eq1o.js:3:169205)
at dotnet.8.0.0-preview.3.23174.8.b7g991eq1o.js:3:164662
at Object.ec [as call_assembly_entry_point] (dotnet.8.0.0-preview.3.23174.8.b7g991eq1o.js:3:165046)
at Object.callEntryPoint (blazor.webassembly.js:1:42926)
at qt (blazor.webassembly.js:1:59086)

When we used to have hashes in the topic (6.0 or earlier), I would update them on release day because they're potentially being churned by the PU all the way up to final release. That wasn't a problem at 7.0 because no hashes were required for the CSP.

@guardrex  The one which fails uses the 'wasm-unsafe-eval' and the error is about the missing 'unsafe-eval'

the error is about the missing 'unsafe-eval'

... but perhaps that's only because it needs the hash for the script that the error mentions.
What happens if you use the one from the error message ...
builder.AddScriptSrc()
    .Self()
    .WithHash256("sha256-47DEQpj8HBSa+/TImW+5JCeuQeRkm5NMpJWZG3hSuFU=")
    .WasmUnsafeEval();

... and btw ... looks like you aren't on latest ...

preview.3

Update to Pre4.

@guardrex  latest version does not start
https://github.com/dotnet/aspnetcore/issues/48298
yes, this is probably just a WIP problem and will probably be fixed in the next preview release. I just wanted to mention it so that it's visible. Released version works without problem. I will test with the other hash as well.
Greetings Damien

Was doing some testing again and this does not work in .NET 7 either, the 'unsafe-eval' is still required

@damienbod The 'unsafe-eval' requirement will still be required for .NET 7 and earlier. Also, please note that the updates enabling improved CSP compliance aren't available in a public preview release yet. You could try installing a nightly build from https://github.com/dotnet/installer to test this new improvement. Thanks!


Add health checks

Add health checks, in particular the GROBID container. So that it will automatically be restarted.

issue was raised in the wrong repo


Spherical coordinates

I would hope that we choose theta to be co-latitude (z = cos(theta)) and varphi to be longitude. Seems there is a different choice here?
https://github.com/JuliaApproximation/SphericalHarmonics.jl/blob/7028d27ba92bb289a7d8bd4f241ed4314eb8f2e9/src/SphericalHarmonics.jl#L30-L37

@dlfivefifty (Ping, looks like no one is watching this repository so far.)

You mean swap phi and theta?

Yeah https://juliaapproximation.github.io/FastTransforms.jl/latest/#FastTransforms.sphevaluate

z = cos(θ):

Wikipedia
DLMF

z = cos(φ):

Wolfram

I suppose that's a 2-to-1 vote in favour of @MikaelSlevinsky

We could add our upcoming Acta Numerica paper to the first list

FYI, I think i'll be adding spin-weighted spherical harmonic transforms within the next couple months, as well as methods for complex data.

We could add our upcoming Acta Numerica

Not too late to change it 🤣

@jagot do you agree with Mikael?

Yes, I prefer to have z = r cos(θ), I think that is the "physicists convention".

Done.


SqlServerNetwork: Refactored to not load assembly from GAC

Pull Request (PR) description

Changes to SqlServerDsc

Updated helper function Restart-SqlService to have to new optional parameters
SkipClusterCheck and SkipWaitForOnline. This was to support more aspectes
of the resource SqlServerNetwork.

Changes to SqlServerNetwork

Refactor SqlServerNetwork to not load assembly from GAC (issue #1151).
The resource now supports restarting the SQL Server service when both
enabling and disabling the protocol.
Added integration tests for this resource
(issue #751).

This Pull Request (PR) fixes the following issues
Helps with issue #1151
Fixes #1051 (closing this since the issue is around code that has been removed).
Fixes #751
Fixes #581 (closing this since the issue is around code that has been removed).
Task list

[x] Added an entry under the Unreleased section in the CHANGELOG.md? Entry
should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md?
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help?
[x] Comment-based help added/updated?
[x] Localization strings added/updated in all localization files as appropriate?
[ ] Examples appropriately added/updated?
[x] Unit tests added/updated?
See DSC Resource Testing Guidelines.
[x] Integration tests added/updated (where possible)?
See DSC Resource Testing Guidelines.
[x] New/changed code adheres to
DSC Resource Style Guidelines
and Best Practices?

This change is

Codecov Report

Merging #1172 into dev will increase coverage by <1%.
The diff coverage is 100%.

@@          Coverage Diff          @@
##            dev   #1172    +/-   ##
=====================================
+ Coverage    97%     97%   +<1%
=====================================
  Files        33      33
  Lines      4005    3993    -12
=====================================
- Hits       3916    3906    -10
+ Misses       89      87     -2


mungegithub: SQ is trying to assign issues to people not in k8s org

Which is invalid
E0617 01:22:08.601896       1 github.go:1228] Error assigning issue# 22485 to pstauffer: PATCH https://api.github.com/repos/kubernetes/kubernetes/issues/22485: 422 Validation Failed [{Resource:Issue Field:assignee Code:invalid}]
E0617 01:25:55.248509       1 github.go:1228] Error assigning issue# 24568 to screeley44: PATCH https://api.github.com/repos/kubernetes/kubernetes/issues/24568: 422 Validation Failed [{Resource:Issue Field:assignee Code:invalid}]
E0617 01:26:36.620666       1 github.go:1228] Error assigning issue# 24877 to paralin: PATCH https://api.github.com/repos/kubernetes/kubernetes/issues/24877: 422 Validation Failed [{Resource:Issue Field:assignee Code:invalid}]
E0617 01:28:24.151443       1 github.go:1228] Error assigning issue# 25383 to asalkeld: PATCH https://api.github.com/repos/kubernetes/kubernetes/issues/25383: 422 Validation Failed [{Resource:Issue Field:assignee Code:invalid}]
E0617 01:29:33.465465       1 github.go:1228] Error assigning issue# 20627 to asalkeld: PATCH https://api.github.com/repos/kubernetes/kubernetes/issues/20627: 422 Validation Failed [{Resource:Issue Field:assignee Code:invalid}]
E0617 01:29:33.591463       1 github.go:1228] Error assigning issue# 26927 to asalkeld: PATCH https://api.github.com/repos/kubernetes/kubernetes/issues/26927: 422 Validation Failed [{Resource:Issue Field:assignee Code:invalid}]
E0617 01:29:59.404684       1 github.go:1228] Error assigning issue# 25807 to andreykurilin: PATCH https://api.github.com/repos/kubernetes/kubernetes/issues/25807: 422 Validation Failed [{Resource:Issue Field:assignee Code:invalid}]
E0617 01:30:11.698570       1 github.go:1228] Error assigning issue# 19636 to tnachen: PATCH https://api.github.com/repos/kubernetes/kubernetes/issues/19636: 422 Validation Failed [{Resource:Issue Field:assignee Code:invalid}]
E0617 01:30:19.824485       1 github.go:1228] Error assigning issue# 25858 to keontang: PATCH https://api.github.com/repos/kubernetes/kubernetes/issues/25858: 422 Validation Failed [{Resource:Issue Field:assignee Code:invalid}]
E0617 01:30:21.011350       1 github.go:1228] Error assigning issue# 22436 to simonswine: PATCH https://api.github.com/repos/kubernetes/kubernetes/issues/22436: 422 Validation Failed [{Resource:Issue Field:assignee Code:invalid}]

@eparis @lavalamp

Yeah, we should probably turn off the munger that is doing this.

Reply to this email directly, view it on GitHub
https://github.com/kubernetes/contrib/issues/1230, or mute the thread
https://github.com/notifications/unsubscribe/AAnglr4zBHWnNRPXejz4JeW2Zvl7NMQtks5qMuVrgaJpZM4I4nBr
.

It's known, he's working on it. I think we can turn it off for now...
https://github.com/kubernetes/contrib/pull/1179

I made #1234, we can turn it back on when it's fixed.


In a remote window, folder picker shows the contents of the parent directory rather than the current directory

Does this issue occur when all extensions are disabled?: Yes/No

VS Code Version: 1.66.2
OS Version: Win 11 Enterprise

Steps to Reproduce:

Open a remote connection in Folder A/B/C
Click File -> Open Folder
The folder picker opens up and shows all the directories in parent folder B and not inside C

Is this by design ? Is there a way to override this ?

@shsuman this should be how "Open Folder" works in all cases, remote or not. I have folder c:\users\alros\repos\microsoft\vscode open in VS Code, then I run "Open Folder", the starting dir will be c:\users\alros\repos\microsoft. This is different from "Open File", which starts in c:\users\alros\repos\microsoft\vscode


Ensure -PipelineVariable is set for all output from script cmdlets

PR Summary
Previously, -PipelineVariable was only set for the first occurence of output from a script cmdlet. This change borrows some code from the handling for compiled commands to ensure -PipelineVariable is always set correctly and should behave as expected even for script cmdlets.
PR Context
This PR resolves #10932, see this issue for further discussion.
We will need to document the bugged behaviour for downlevel versions of PowerShell in docs so that users are aware. Most folks probably won't have noticed it, but people may still run into it from time to time on downlevel versions.
@SteveL-MSFT I'm not 100% sure, but this feels like the kind of fix y'all might want in a servicing release for 7.0. 🙂
PR Checklist

[x] PR has a meaningful title

Use the present tense and imperative mood when describing your changes

[x] Summarized changes
[x] Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
[x] This PR is ready to merge and is not Work in Progress.

If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.

Breaking changes

[x] None
OR
[ ] Experimental feature(s) needed

[ ] Experimental feature name(s):

User-facing changes

[ ] Not Applicable
OR
[x] Documentation needed

[ ] Issue filed:

Testing - New and feature

[ ] N/A or can only be tested interactively
OR
[x] Make sure you've added a new test if existing tests do not effectively test the code changed

Tooling

[x] I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
OR
[ ] I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:

Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

Codefactor issue is an existing issue in this test file in an area I've not touched; not going to mess with that for now. 🙂

I think this falls into a bucket 3 breaking change and I think we should take the change.
@PowerShell/powershell-committee  Please review

@PowerShell/powershell-committee reviewed this, we agree that the previous behavior was broken and falls under bucket 3 as a breaking change, so approve the intended new behavior

@JamesWTruher  can you respond to @vexx32

@JamesWTruher please update your review / let me know if you have additional cases to cover with tests. Thanks! 💖

@TravisEz13 is there anything left pending here? 🙂

Merged this so we can include it in the next preview in order to validate it better


perf: bypass duplexify

Bypasses duplexify and pipes encode, socket, decode directly without any intermediate proxy.

Would be nice if multileveldown provided a less hacky way to do this...

The goal here is to skip this line, if I understand it correctly? https://github.com/Level/multileveldown/blob/52f4861fc37500bfed167114f007bfce3104fc77/leveldown.js#L79.

The goal here is to skip this line, if I understand it correctly? https://github.com/Level/multileveldown/blob/52f4861fc37500bfed167114f007bfce3104fc77/leveldown.js#L79.

Yep and avoid the overhead/complexity of an intermediate stream.

The less hacky way would be to support a second argument here, defaulting to null:
https://github.com/Level/multileveldown/blob/52f4861fc37500bfed167114f007bfce3104fc77/client.js#L21-L23

The less hacky way would be to support a second argument here, defaulting to null:

Yep. But that would require updating multileveldown.

I worry this will have a side effects, because:

duplexify handles a bunch of edge cases
the close event on a net socket has a hadError argument that we may need to ignore here

I worry this will have a side effects, because:

duplexify handles a bunch of edge cases

I'm more worried about having duplexify than not having it.

the close event on a net socket has a hadError argument that we may need to ignore here

Yes.

This makes no difference in my benchmarks, at least not after removing much bigger bottlenecks. In many-level (the WIP replacement for level-party) I doubled the throughput by batching reads, among other things.

This makes no difference in my benchmarks, at least not after removing much bigger bottlenecks. In many-level (the WIP replacement for level-party) I doubled the throughput by batching reads, among other things.

Can I follow many-level somewhere?

I'll post something in https://github.com/Level/abstract-level/issues/14 once I've pushed the repo


Archive API Requests Returning Partial Responses

Hello, and happy 4th of July 🎆🇺🇸🎆
I'm hacking on the Archive API, and am running into some behavior I wasn't expecting.
In my node script, I send two requests for two different month's worth of data, three seconds apart. I'm using the request-promise library to issue the requests. Sometimes these will complete successfully, but often they will not.
Specifically, the response will come back with a 200 status code, but the JSON body will be incomplete.
I was able to replicate this behavior using Charles, making back-to-back queries for February 1985, over 30 seconds apart.
Here are gists representing the first complete response, and the second partial response.
My main questions are:

Is there a problem with the format of the requests I'm sending to the API?
Is there a best practice I should follow to both format the requests and process the response, so that I could either stop getting partial responses or limit the chances that a partial response would be returned?

Thanks and please let me know if there are additional details I can provide.

The responses from the Archive API can be pretty big (~20mb).  Does your request have a timeout?
The Archive API is meant so you can build up your own database locally of NYT article metadata.
https://developer.nytimes.com/archive_api.json#/README

Hi and thanks for the quick response. My request doesn't have a timeout associated with it.
My workaround was basically to check if the response was a valid JSON object, and retry if not. Seems to be working fine.


Add ?: debugging support to work like .?

Currently you can do:
x =: foo.bar().?.baz().?

Where .? is sugar for .WWW() which prints and returns its input.
Next we want
foo ?: bar baz

to be like
WWW:
  foo: bar baz

for quick print debugging.

Needed to #137

Can be done with function tags instead


Correction of spellings, grammatical and punctuation errors in the README.md

Hello mentors , I would like to correct some of the spellings, grammatical and punctuation errors in the README.md. Looking forward to working on this issue as a GSSOC 21 participant. Thank you:)

@sarala-2210 can you show the errors? Screenshots may be!

@gauravdas014 and some more minor changes like,
bugfixes->bug fixes
bugs which have ->bugs that have
voices from -> voices of
diversity centric -> diversity-centric
To Add: DEI means Diversity Equity & Inclusion

@sarala-2210 Go Ahead


Add adapter-middleware.coffee

Did NOT delete middlewares.coffee

@billbliss,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

We don't need this PR anymore. Do we?