Consider working with fwupd?

Hi Andrew!
Thanks for reaching out on Twitter, this looks exactly like the thing I'm trying to do. I'm really in awe of what you've done in Culvert so far, and I have a feeling I'll have a lot more questions in the future! Some background:

fwupd is a system daemon focussed on firmware updates and platform security, and gets metadata and new firmware from the LVFS, another one of the connected projects I maintain. fwupd is installed by default on basically every Linux distro, and also included in ChromeOS -- and the LVFS has supplied over 77 million updates -- so we're doing okay. :)
HSI is shorthand for the Host Security ID, which is a set of tests we run on the machine. We're checking for UEFI Secure Boot, the IOMMU being set up correctly, things like various BootGuard straps being configured correctly, and dozens of things more. It's essentially what you've done with Culvert but instead focussing on mainly-consumer Intel/AMD UEFI and some aarch64 bits and getting buy-in from vendors about actually fixing the issues and dragging up the level of security for the platform. It's all documented here: https://fwupd.github.io/libfwupdplugin/hsi.html and it's being expanded all the time with new tests.
The fwupd HSI tests are being run at scale with deep integration with the desktop done, Red Hat insights done, and also openSCAP planned as well. We're working with various large, ahem, companies making HSI compliance a bit part of commercial purchasing agreements.
A mega vendor want to run fwupd on the BMC itself, initially targetting AST2500 and AST2600 -- and are concerned that OpenBMC/uboot might not doing all it should do. This is why I'm now poking around with the datasheet working out if anything needs to be verified (it does) and if anything exists already (it seems it does!). Several other vendors are using AST2X00 devices and want to verify the BMC security from the host, as the server proprietary BMC stacks are somewhat fragile.

Anyway, this issue is too long already, and is probably actually a discussion -- so if you'd like to move this to email or even a quick zoom call let me know. I'm working for Red Hat in the UK if that helps. Thanks for any ideas or feedback.

Hello!
Thanks for the interest. I'll share a bit of background too:

I started culvert internally at IBM as a demonstration of the issues outlined in CVE-2019-6260 prior to publication of the CVE, and to push for us (IBM) to mitigate them for Power systems firmware. Its existence lead to @shenki's LCA talk about server security and featured in Eclypsium's write-up of Quanta's BMC firmware woes
I've continued to maintain it as it's helped us with BMC and platform bring-up, development and recovery (especially around the OTP strapping in the AST2600), and I expect it will be useful for the same in future generations of BMC SoCs.

I've got some patches in-flight for the AST2600 that might also interest you: https://github.com/amboar/culvert/compare/master...ast2600 - expect iterations on that series in the days to come :)
Anyway, I'm keen on the idea of integrating culvert's functionality into fwupd. I'll take a look at how fwupd currently implements these tests and have a bit of a think about what the integration path might look like. I'd certainly like your thoughts on that too.
Feel free to email me directly and we can chat that way, and maybe use that to bootstrap a zoom session.
Thanks for getting in touch!

Quite a bit to work through there :)
I took a look at the fwupd codebase after you opened the issue and I tend to agree the way forward is one of two extremes:

Your "steal ideas" approach - re-implement the functionality in fwupd and lean on the abstractions I've put together in culvert as a guide
Ship culvert as a binary and fork/exec it, and e.g. parsing results from stdout

I'm not sure how 2 plays into your "each additional dep means the number of people using the feature goes down two orders of magnitude" issue - arguably it would be a dependency, but not in a library sense. I'm not sure if the distinction matters. Shipping culvert as a separate binary avoids us having to actually resolve the licensing question, and we could add meson options to trim functionality down to meet the requirements of fwupd. Adding a HSI reporting mode to culvert would be pretty neat, though from what I've seen JSON documents you have are more about enumerating and describing the attributes rather than measuring? Do you have a schema for measurement results? Regardless, I think we could cook up some descriptions based on the text in CVE-2019-6260.
1 is obviously more work, but gives a much tighter integration into fwupd and restricts the scope of behaviour to at most fill fwupd's requirements. Was flashing a new BMC image ever a goal (asking due to some of the discussion on Mastodon)? There's obviously tension there between measuring the bridge state to assess security posture and requiring the bridges be available for flashing purposes, bypassing any authentication/authorisation on the BMC's part.
As for playing with stuff, I think the other thread on Mastodon is going to be the most help there. Aspeed are also quite responsive on the OpenBMC Discord and might be able to give you some pointers (maybe it's possible to rig up an EVB in a useful configuration - I don't have one at hand).
Anyway, I'm happy to help out either way where I can!

I'm less keen on this; various vendors have tried to convince us to exec random binaries for enumeration, firmware writing and security validation, and I think in all honesty this would be horrific from a "keeping it all working in CI" point of view, and greatly complicates things like project maintenance, device lifecycle, caching and resource locking. It also makes progress reporting almost impossible and also selinux policy much harder to satisfy. I think it would be a bad precedent and would open the floodgates tbh.

Yeah, many good concerns there. Let's concentrate on getting the bits we need implemented directly in fwupd.

More interesting for stuff like Red Hat Insights is the JSON output, which culvert could certainly copy, e.g.

Right, that's the output that I was asking about. From the brief look I took at the JSON documents in fwupd.git it wasn't obvious that e.g. HsiResult was specified.

I'd appreciate your edits and comments on https://docs.google.com/document/d/1Ib_1hwxCnfe-H0d7jeBOi38NYyTHIzEi66OcU61xLY4/edit?usp=sharing -- I think it makes a lot of sense to agree on the failures and the severities. Maybe some of those don't make sense as HSI attrs, ideas welcome.

Yep, let me have a read through and provide some feedback.

Okay, I've left a bunch of comments on the google doc. Let me know what you think.

Yeah, many good concerns there. Let's concentrate on getting the bits we need implemented directly in fwupd.

I think a good starting point would be to add the checks for the devmem bridge, e.g. Read DWORD HICRB (0x100h) and check that bit 6 is set -- I've added these sections to the doc -- any help there most welcome. If I understand the culvert code correctly the devmem bridge isn't doing any of the report checks either -- i.e. we need the functionality there too.
I'm somewhat sceptical that server OSs are going to let us use all the bridges -- i.e. with kernel lockdown enabled the iopl() and outb_p() code is going to fail. I don't know if remapping the MMIO BARs is going to work, but I guess it's more likely than the SIO method. I also think matching the AST_PCI_VID&AST_PCI_DID_VGA PCI device is going to be a lot safer than just doing SIO writes on unknown hardware -- I don't know if 0xA5A5 is a common or unique unlock code. Wisdom is certainly appreciated.

I think a good starting point would be to add the checks for the devmem bridge, e.g. Read DWORD HICRB (0x100h) and check that bit 6 is set -- I've added these sections to the doc -- any help there most welcome.

Right, let me fill those out. It made me think about whether there's a better way to describe all the bits so that you could dump them out as reference. That would make your job here a bit easier. However, I think it would require a bit of rearchitecting as I've encoded this info in the code rather than defining it statically.

If I understand the culvert code correctly the devmem bridge isn't doing any of the report checks either -- i.e. we need the functionality there too.

Can you clarify what you mean here? Is it that you'd like to see a report of whether the /dev/mem interface is available in e.g. the output of probe? There are limitations there...

I'm somewhat sceptical that server OSs are going to let us use all the bridges -- i.e. with kernel lockdown enabled the iopl() and outb_p() code is going to fail. I don't know if remapping the MMIO BARs is going to work, but I guess it's more likely than the SIO method. I also think matching the AST_PCI_VID&AST_PCI_DID_VGA PCI device is going to be a lot safer than just doing SIO writes on unknown hardware -- I don't know if 0xA5A5 is a common or unique unlock code. Wisdom is certainly appreciated.

Yeah, all valid concerns. The latter concern is the reason for the warning in caps at the top of the README :)
Getting back to iopl() and outb_p(), you'll be pleased to know that the SoCs implement a PCI-to-LPC bridge :) However, whether it's enabled is under control of the BMC, so it may not be enabled in all circumstances and is documented to be disabled by default. But if it is enabled, we can use the PCIe BAR mapping to drive LPC accesses rather than inb/outb.
Stepping back for a moment, I guess we need to be explicit about what we're trying to establish. Are we trying to establish whether the BMC is vulnerable with no assumptions about the access method on the host side (e.g. bare-metal hosting or host kernel compromise are in-scope), or are we trying to establish vulnerability from userspace (assuming root)? I presume the former. If the host kernel is locking down userspace access then I can't see how we can escape having help from the kernel to establish the presence of the vulnerabilities.

I've added a table describing all the bits in each SoC's physical address space for org.fwupd.hsi.Aspeed.iLPC2AHB.ReadWrite. Let me know what you think. If it's helpful we can discuss how we go about adding the table for the remaining sections.

Is it that you'd like to see a report of whether the /dev/mem interface is available

Nah, I mean if you do culvert probe when running on the SoC device it should show the user what the problems are.

we can use the PCIe BAR mapping to drive LPC device accesses

Can you remap the BAR when the kernel is locked down?

Are we trying to establish whether the BMC is vulnerable

For the first cut, I want to run fwupd on the BMC as part of OpenBMC and then output a report on what problems there are. I think working on the PCI-to-LPC bit so we can scan from the host OS is probably phase 2.

I've added a table describing all the bits in each SoC's physical address space

I think that's a really good start, more certainly welcome! I've got some test code that should be ready for some rough review next week -- i.e. mmap /dev/mem, read 0x1e6e2070 and look for the bit etc. i.e. a really simple first cut.

Nah, I mean if you do culvert probe when running on the SoC device it should show the user what the problems are.

This should work. Is it not working for you? I just checked on an AST2600 and it provides this output:
root@ast2600:~# ./culvert -v probe
[*] Found 5 registered bridge drivers
[*] Trying bridge driver Debug UART
[*] Unrecognised argument list for debug interface (0)
[*] Trying bridge driver devmem
[*] Probing devmem
[*] Probing for SoC revision registers
[*] Found revision 0x5030303
[*] Trying bridge driver iLPC2AHB
[*] Failed to initialise iLPC bridge: -95
[*] Trying bridge driver LPC2AHB
[*] Failed to initialise L2A bridge: -95
[*] Trying bridge driver P2A
[*] Failed to initialise P2A bridge: -2
[*] Probing for SoC revision registers
[*] Found revision 0x5030303
[*] Selected devicetree for SoC 'aspeed,ast2600'
[*] Found 14 registered drivers
[*] Bound trace driver to /ahb/bus-controller@1e600000
[*] Bound sdmc driver to /ahb/apb/memory-controller@1e6e0000
[*] Bound strap driver to /ahb/apb/syscon@1e6e2000/strapping
[*] Bound sioctl driver to /ahb/apb/syscon@1e6e2000/superio
[*] Bound bridge-controller driver to /ahb/apb/syscon@1e6e2000/bridge-controller
[*] Bound pciectl driver to /ahb/apb/syscon@1e6e2000/pcie-bridge-controller
[*] Bound otp driver to /ahb/apb/secure-boot-controller@1e6f2000
[*] Bound debugctl driver to /ahb/apb/uart@1e783000
[*] Bound debugctl driver to /ahb/apb/uart@1e784000
[*] Bound vuart driver to /ahb/apb/serial@1e787000
[*] Bound vuart driver to /ahb/apb/serial@1e788000
[*] Bound ilpcctl driver to /ahb/apb/lpc@1e789000/bridge-controller
[*] Initialised strap driver
[*] Initialised sioctl driver
[*] Initialised bridge-controller driver
[*] iLPC bridge gate ID: 5
[*] Initialised ilpcctl driver
[*] Initialised ilpcctl AHB bridge controller
[*] Initialised debugctl driver
[*] Initialised debugctl AHB bridge controller
[*] Initialised debugctl driver
[*] Initialised debugctl AHB bridge controller
[*] fdt: Searching devicetree for type 'memory'
[*] Initialised sdmc driver
[*] Initialised pciectl driver
[*] Initialised pciectl AHB bridge controller
xdma:   Restricted
        BMC: Enabled
        XDMA on BMC: Enabled
        VGA: Disabled
        XDMA is constrained: Yes
p2a:    Disabled
debug:  Permissive
        Debug UART port: UART1
debug:  Permissive
        Debug UART port: UART5
ilpc:   Disabled
[*] Unbound instance of driver ilpcctl
[*] Unbound instance of driver vuart
[*] Unbound instance of driver vuart
[*] Unbound instance of driver debugctl
[*] Unbound instance of driver debugctl
[*] Unbound instance of driver otp
[*] Unbound instance of driver pciectl
[*] Unbound instance of driver bridge-controller
[*] Unbound instance of driver sioctl
[*] Unbound instance of driver strap
[*] Unbound instance of driver sdmc
[*] Unbound instance of driver trace

Can you remap the BAR when the kernel is locked down?

I haven't poked much at lockdown tbh so I went looking. It seems you can't map the BAR into userspace when lockdown is sufficiently enforced:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/pci/pci-sysfs.c?h=v6.1#n1028

For the first cut, I want to run fwupd on the BMC as part of OpenBMC and then output a report on what problems there are. I think working on the PCI-to-LPC bit so we can scan from the host OS is probably phase 2.

Sounds good.

I think that's a really good start, more certainly welcome! I've got some test code that should be ready for some rough review next week -- i.e. mmap /dev/mem, read 0x1e6e2070 and look for the bit etc. i.e. a really simple first cut.

Okay. Given you listed BMC and host access separate I wasn't quite sure whether that table was exactly what you were after. Since it's at least useful, we can work to add that table for the remaining HSIs.
As a point of reference, anything that calls soc_bridge_controller_register() is a driver that controls the state of a bridge. The bits we need to touch are (in)directly referenced from the enforce() callback implementation. This might end up calling into other areas of the codebase. From there it's a bit of a maze of mapping the compatibles back to the devicetrees to derive the absolute register addresses. The list isn't terribly long (though eventually needs to account for the eSPI and LPC2AHB bridges):
$ git grep soc_bridge_controller_register
src/soc.c:soc_bridge_controller_register(struct soc *ctx, struct bridgectl *bridge, const struct bridgectl_ops *ops)
src/soc.h:int soc_bridge_controller_register(struct soc *soc, struct bridgectl *bridge,
src/soc/debugctl.c:    if ((rc = soc_bridge_controller_register(soc, debugctl_as_bridgectl(ctx), ops)) < 0) {
src/soc/ilpcctl.c:    if ((rc = soc_bridge_controller_register(soc, ilpcctl_as_bridgectl(ctx), ops)) < 0) {
src/soc/pciectl.c:    if ((rc = soc_bridge_controller_register(soc, p2actl_as_bridgectl(ctx), &p2actl_ops)) < 0) {
src/soc/pciectl.c:    if ((rc = soc_bridge_controller_register(soc, xdmactl_as_bridgectl(ctx), &xdmactl_ops)) < 0) {

So if you want to get a head-start you can dig in that way, otherwise I'll plug away at adding the tables when I have a moment.

[*] Initialised pciectl AHB bridge controller

Aha, I didn't know that would work when local. Isn't devmem going to work in all cases, and possibly be a more reliable way to retrieve the information? Or do you think we should always be using pciectl in fwupd when running on the BMC rather than devmem?

Ah, I think we're running up against two things here:

Naming things is hard
My absolute lack of any design or usage documentation

Let me try to fix 2 properly, however as a brief explanation the codebase is split into approximately three parts:
a. The stuff under src/bridge
b. The stuff under src/soc
c. Everything else (logging, host bits that are dependencies of the stuff under src/bridge, etc)
Considering a. above, the source under src/bridge contains all the host-side drivers for the bridges ("host" is used a bit loosely here, as it also contains the /dev/mem driver for use on the BMC - I consider the machine on which culvert is running to be called the "host" rather than the processor that's attached to the BMC):
$ git ls-files src/bridge
src/bridge/debug.c
src/bridge/debug.h
src/bridge/devmem.c
src/bridge/devmem.h
src/bridge/ilpc.c
src/bridge/ilpc.h
src/bridge/l2a.c
src/bridge/l2a.h
src/bridge/meson.build
src/bridge/p2a.c
src/bridge/p2a.h

Host bridge drivers are registered in the code via the REGISTER_BRIDGE_DRIVER() macro. Their role on initialisation is to produce an AHB object (struct ahb) on which we can perform {read,write}{,l}() operations. This gives us an abstraction that we exploit through the rest of the codebase, where we don't care which bridge we're using, only that we can perform reads and writes on the AHB.
Reads and writes on the AHB are handy, however, what's even more handy is pairing this capability with the knowledge of how the AHB address space is laid out. A constructed SOC object (struct soc) emerges from (effectively) the soc_from_rev(..., rev_probe(ahb)) sequence in soc_probe() once we have our struct ahb, and from there we can start binding drivers to devices in the AHB address space and doing interesting things.
The drivers for the devices in the SoC's address space live in src/soc and are registered with the REGISTER_SOC_DRIVER() macro. They are all implemented in terms of struct soc, which gives them an abstract mechanism to drive reads and writes on the AHB (via struct soc's struct ahb instance). Returning to the bridges for a moment, it's the case that the SoC exposes control bits for them on the APB address space (mapped into the AHB). Given that a lot of the interest here is about inspecting and controlling the state of these bridges, there are drivers that do just that in src/soc:
$ git grep soc_bridge_controller_register
src/soc.c:soc_bridge_controller_register(struct soc *ctx, struct bridgectl *bridge, const struct bridgectl_ops *ops)
src/soc.h:int soc_bridge_controller_register(struct soc *soc, struct bridgectl *bridge,
src/soc/debugctl.c:    if ((rc = soc_bridge_controller_register(soc, debugctl_as_bridgectl(ctx), ops)) < 0) {
src/soc/ilpcctl.c:    if ((rc = soc_bridge_controller_register(soc, ilpcctl_as_bridgectl(ctx), ops)) < 0) {
src/soc/pciectl.c:    if ((rc = soc_bridge_controller_register(soc, p2actl_as_bridgectl(ctx), &p2actl_ops)) < 0) {
src/soc/pciectl.c:    if ((rc = soc_bridge_controller_register(soc, xdmactl_as_bridgectl(ctx), &xdmactl_ops)) < 0) {

Enter the naming problem :) I needed some way to differentiate between e.g. ilpc as a host bridge driver and ilpc as a SoC bridge driver. I probably could have chosen a better scheme, but in terms of the symbols in the code the SoC-side bridge drivers are suffixed with ctl.
Rounding it out, soc_bridge_controller_register() gathers all instances of SoC-side bridge drivers into a list for us to work with later on in the execution of culvert.
With this structure it's the case that however we drive accesses on the BMC AHB we can easily inspect the configuration of all the bridges, and hence culvert probe works over /dev/mem, the P2A, the iLPC bridge, and the debug UART equally.
Finally, returning to your comment:

[*] Initialised pciectl AHB bridge controller
Aha, I didn't know that would work when local. Isn't devmem going to work in all cases, and possibly be a more reliable way to retrieve the information? Or do you think we should always be using pciectl in fwupd when running on the BMC rather than devmem?

From the above the output [*] Initialised pciectl AHB bridge controller comes from the driver for the SoC-side PCIe device controller (src/soc/pciectl.c), i.e. the driver that encodes which bits to inspect to determine how the various PCIe devices and bridges are configured (VGA and BMC devices, P2A and XDMA bridges) rather than the host-side P2A bridge driver (src/bridge/p2a.c). Earlier on in the output we can see the host-side P2A bridge driver (src/bridge/p2a.c) fail to initialise:
...
[*] Trying bridge driver P2A
[*] Failed to initialise P2A bridge: -2
...

Does that help?

Okay, I've added the rest of the tables and covered the interesting configuration bits for all of the AST2400, AST2500 and AST2600 in the shared google doc. That should be a decent start.


ID Court type choice:
User feedback: something
(court_type_selection)

Question ID
Court type choice

Details
test fee waiver feedback form 1

Variable being sought
court_type_selection

Package version
playground

Filename
docassemble.playground5FeeWaiverRequest:fee_waiver_request.yml

Test issue created for custom tester feedback form


Resharding

Fix the tabletserver RPC interface and tests.

@sougou @guoliang100

@aaijazi changed the worker tests a bit, to use the gorpc stubs. That way when we switch to grpc, less work to do.

worker tests lgtm


SplitView placement right + displayMode CompactOverlay doesn't work

in the Xaml Controls Gallery Split View page set the placement to right and the display mode to CompactOverlay and notice that the content is clipped.  Its possible this is a XCG bug, since changing the OpenPaneLength and CompactPaneLength can reveal the content if the correct settings are chosen.

#2392

#2392 looks related but this could be another similar issue in the style.

I think this is an issue with the XAML Controls Gallery. The content inside the pane has a lot of right padding. Since the content gets positioned to the left of the right border, by "coincidence" we show essentially nothing. If we have content in there that has no right padding, and instead content, there won't be this lack of content.

@StephenLPeters @stmoy Should we close this issue since this is an issue with the XCG SplitView sample which is also being tracked by https://github.com/microsoft/Xaml-Controls-Gallery/issues/322?

Sure, sounds good.


sha256.hmac return garbled hash value

I was trying to use the sha256.hmac function to generate hmac sha256 hash, but I got some garbled code.
//convert String to Uint8Array
var msg = new TextEncoder("utf-8").encode("/v2/radios?page=1&size=10&catalog=all:7690d85d-7777-2930-040c-9241b52682ab");
var key  = new TextEncoder("utf-8").encode("q23IN6hB7p");
var hash = sha256.hmac(key, msg);
//convert Uint8Array to String
console.log(new TextDecoder("utf-8").decode(hash));  // result is garbled code： gUm7_�������)���V�Ύ����kb�l�T

version: v1.0.0
browser: Chrome 62

What did you expect it to return?

I expected it to return a hash string like: "eac1jklqa0c9f4e700ccab992dfb36a6d2e30e34sd01c8476f3cio27633f187"

The returned value is a binary (0-255) hash, so if you want a hex representation convert it to hex. You never want to convert binary values from utf-8 unless you know they represent text encoded as utf-8 in the first place.

Thanks @dchest. for clarification.
For someone running into the same problem, I post my solution here:
//convert String to Uint8Array
var msg = new TextEncoder("utf-8").encode("/v2/radios?page=1&size=10&catalog=all:7690d85d-7777-2930-040c-9241b52682ab");
var key  = new TextEncoder("utf-8").encode("q23IN6hB7p");
var hash = sha256.hmac(key, msg);
//convert Uint8Array to hex string
var hashStr = Array.from(hash, function(byte) {
    return ('0' + (byte & 0xFF).toString(16)).slice(-2);
  }).join('');

You're welcome! If you already use TextEncoder, it's easier to use it for hex too as in my edited comment.

@dchest I tried few other heavyweight libraries, for the same API I am using here, they accept and return both string value instead of Uint8Array.

What is your consideration to use Uint8Array when design this API?
Is it possible to update the user guide to include code example on conversion between Uint8Array to String?

It was popular in JavaScript libraries to create many methods, like hexDigest(), base64Digest(), etc — there are many different representations of hashes — and also accept strings instead of Uint8Arrays. This made libraries include hex, base64, utf8, etc. encoders/decoders. So imaging you're using AES, SHA256, ZIP, PNG, etc. and all of them include their own, perhaps buggy, encoders/decoders, inflating code size. This was mostly an artifact of JavaScript not having typed arrays, so bytes were represented either as strings or as Arrays. Now that we have typed arrays and TextEncoder/TextDecoder (or Buffer in Node.js), it's time to put an end to this practice.
There's a small note about it in the docs ("Functions accept and return Uint8Arrays. To convert strings, use external library (for example, nacl.util)"), but I'd welcome a pull request to add something like this to examples:

const result = hasher.digest();
// or if you need a hex representation:
const hexResult = new TextEncoder("hex").encode(result);

@dchest I will try to improve this part of doc a little bit, going to do a pull request.
But I think const hexResult = new TextEncoder("hex").encode(result); returns Uint8Array not a String, what method do you recommend for String conversion?

Or, right, sorry, it indeed returns Uint8Array and "hex" is not supported in some browsers. Not sure then, maybe Node.js's Buffer.from(result).toString('hex')?


[whois] IP Addresses are returning blank

Extension
https://www.raycast.com/zavbala/whois
Description
Hello, thank you for this awesome extension!
Unfortunately, it doesn't seem to return anything when you enter an IP address, though who.is works fine with IPs.
Is this something that you think could be fixed, please? 🙏
Steps To Reproduce
Enter an IP in the field
Current Behaviour

Expected Behaviour
No response

closing as I have implemented it myself in #8853
@raycastbot close this issue

@raycastbot close this issue


Upload failing on current development branch

One of the changes to the develop branch over the last few days appears to have broken uploading.  I haven't narrowed it down to an exact commit, but I reverted back to commit 86260a48ba5a154649800146aefe7d503e6cc059 and the problem went away.
This is on MacOS, attempting to upload to arduino nanos.
amp@AMP-MBP-home:~/Dropbox/Arduino/ObjectLights/platformio/CubeLights [master]$ platformio run -e light_cube -t upload --upload-port /dev/cu.usbserial-AM01SK3R
[Sun Feb 22 14:37:13 2015] Processing light_cube (build_flags: -DPLATFORMIO -Wall -DCUBE_LIGHT_BASIC_CONTROL, platform: atmelavr, board: nanoatmega328, framework: arduino, global_buildflags: -DPLATFORMIO -Wall, upload_port: /dev/cu.usbserial-AM01SK3R)
-----------------------------------------------------------------------------------------------------------------------------------------------
before_upload(["upload"], [".pioenvs/light_cube/firmware.hex"])
"/Users/amp/.platformio/packages/tool-avrdude/avrdude" -q -D -p atmega328p -C "/Users/amp/.platformio/packages/tool-avrdude/avrdude.conf" -c arduino -U flash:w:.pioenvs/light_cube/firmware.hex:i
avrdude: ser_open(): can't open device "unknown": No such file or directory
ioctl("TIOCMGET"): Inappropriate ioctl for device

avrdude done.  Thank you.

scons: *** [upload] Error 1

@aphelps sorry :( It was huge refactoring with build scripts. I've just fixed it. I will re-test uploading for all platforms (which I have) tomorrow.

No problem, these things happen.  I love all the tests I've been watching going in ;)

Which tests do you mean? From avrdude ? :smile:


JavaScript heap out of memory (minecraft.js)

Hi ! I have a strange error when I ask this server with minecraftping: Freebuild.mine.bz:25565

The problem is that this server crashes my script ...
Is there a solution to prevent this crash ?
This problem occur in local and on my web server...
I use gamedig to query thousands of different game servers and I have never had this problem before, only with this Minecraft server.
Thank you in advance.
David

I cannot reproduce this problem on my computer.
Windows 10 1809
<EMAIL_ADDRESS>
> node -v
v10.13.0
> npm -v
6.8.0

> gamedig --type minecraft --host freebuild.mine.bz --port 25565 --pretty
{
  "name": "",
  "map": "",
  "password": false,
  "raw": {
    "description": {
      "text": "Freebuild"
    },
    "players": {
      "max":<PHONE_NUMBER>,
      "online": 423685411,
      "sample": [
        {
          "id": "cc8ba061-e894-472b-bbc0-20945286ec3b",
          "name": "§8§O|Mortal|§fBauerPower06§r"
        },
        {
          "id": "9e2fe3aa-c341-470e-aaf1-6d44e369cf98",
          "name": "§6|Royal|§f Zombie_Assassin5§6|$$$|§r"
        },
        {
          "id": "302297a0-2e3f-4f03-bd94-18009a6dfc12",
          "name": "§9|Prophet|§f shaggyolsen§6|§4LavaKing§6|§r"
        },
        {
          "id": "6f1a4e8d-84eb-4fd1-bb5e-726001b6925d",
          "name": "§8§O|Mortal|§fIbbycoolkid§r"
        },
        {
          "id": "18ea979c-9e76-4e19-a5cb-a1ebdb945bca",
          "name": "§l§7§kOU§b§nSiddiet§l§7§kOU§r"
        }
      ]
    },
    "version": {
      "name": "Spigot 1.13.2",
      "protocol": 404
    },
    "rcvNumPlayers": 423685411
  },
  "maxplayers":<PHONE_NUMBER>,
  "players": [],
  "bots": [],
  "connect": "freebuild.mine.bz:25565",
  "ping": 210
}

Are you using a version of gamedig below 2.0.12?
This server is returning 423685411 as online player number, that would cause gamedig to create a array with 543685411 element before 2.0.12.
see https://github.com/sonicsnes/node-gamedig/commit/2ffeda6098c19af66bedaa47a9de4eec64481b54

@Genteure is exactly correct. Versions before 2.0.12 would attempt to allocate 423 million player objects, because the server is lying about how many players are online. After 2.0.12, these servers will simply get an empty player array.


GPL Licensed code in superset

I am not a licensing expert but it seems following file has GPL license -
https://github.com/airbnb/superset/blob/master/superset/assets/vendor/select2.sortable.js
its not good to ship it as part of superset which has apache license.

Dup of #1270


Update active-directory-devhowto-appsource-certified.md

Broken link

@dstrockis : Thanks for your contribution to the Azure documentation! The author, @skwan, has been notified to review your proposed change.

#sign-off


Use UTC timestamps in all the ci/kokoro/* scripts.

Usually the Kokoro VMs are running on Google Standard Time, but the containers are running in UTC, which makes comparing timestamps annoying (not hard, just annoying).

[ ] -common
[ ] -cpp
[ ] -spanner
[ ] -pubsub
[ ] -bigquery

Done in https://github.com/googleapis/google-cloud-cpp/pull/3704 for -cpp, which will be our only repo.


Add documentation to readthedocs

Docs are now on RTD:
https://qgrad-docs.readthedocs.io/en/latest/index.html

I still have to set up webhooks such that docs automatically build on each commit. But I don't have the owner
privilege to do that
"Edit on GitHub" links point to the rest files instead of the code. This needs to be fixed


test: Disable mysql_server_test on Travis CI.

It is currently always failing and will be fixed once we switch Travis CI to run the tests within Docker.
I'll merge this right away. No need for review here.
@demmer suggested this temporary measure in https://github.com/youtube/vitess/issues/3203.

I think you will need to disable local.unit as well. When I was looking at this, the mysql_server_test hides this failure. But once you remove that one, this one also fails .

You're right :(
It's already failing: https://travis-ci.org/youtube/vitess/jobs/277522775
I'll create another PR.


SearchBox doesn't have icons in Safari

Bug: What is the current behavior?
In Safari the icons of the search box don't show up
Visible in for example: https://community.algolia.com/instantsearch.js/react/storybook/?selectedKind=SearchBox&selectedStory=default&full=0&down=1&left=1&panelRight=1&downPanel=kadirahq%2Fstorybook-addon-knobs

Bug: What is the expected behavior?
The search box has buttons with icons like in Chrome

Bug: What browsers are impacted? Which versions?
All current Safari versions can't display svg inside a <button>, mve:
http://codepen.io/anon/pen/mRQMzW
What project are you opening an issue for?

react-instantsearch

What is the version you are using? Always use the latest one before opening a bug issue.
3.1.0

All current Safari versions can't display svg inside a , mve:

Thanks a lot you are the new safari detective! It's perfect :)
What about we use an <img src=svg instead?

I was missing the actual error and assuming svg was the problem, opening PR with the fix in a few minutes


Debugging Crashing/Restarting InfluxDb Being run Windows Service

I have a situation where InfluxDb sometimes will crash/restart and the entries in the Windows Event Log is not enought to debug the issue.
I have problems enabling logging of InfluxDb when running InfluxDb on Windows as a service (through nssm). I have succeded in enabling HTTP request logging by setting [access-log-path = “/test/access.log”] in influxdb.conf. However I cannot get the general InfluxDb logging to be written to file.
Do any of you have any advise on how to achieve this?

Hi @JLorch we need a lot more information to triage this issue. If you're unable to get that information, e.g., logs and so on, then possibly asking on the InfluxData community site: https://community.influxdata.com might get you the help you need.
Thanks.


Tome of transmutation Issue 'xpOverride'

Hello when i tried to open the book in server play nothing happens but in server console this message appears :
https://pastebin.com/HA1ZiEzB
i've tested it on single play and it works but not in server play.
version used : build 53

this is odd... the server shouldn't even care about that field hence it is marked as client-side only. and it used to work. whatever, i'm fixing it and a patch should be up soon.

Thank you for reporting it. It should be fixed in the next version which will be available here as soon as it is approved.


Support for signing and verifying items in IPFS

Description
IPFS (InterPlanetary FileSystem, https://ipfs.tech/) provides a public, content-addressable filesystem.
IPFS files can be address via ipfs://[hashcode] where hashcode is the immutable hash of the file (technically, it's a Merkle tree of hashes where hashcode is the root).
Thus, the bytes at a given hashcode will either not exist or will be the same everywhere, to everyone, for all time.
Signing an IPFS url/contents will provide a mechanism for signing and verifying the signature of an immutable item.
So... what can be immutable? An SBOM. Other build artifacts (e.g., OmniBOR receipts.)
Adding IPFS signing and verification capabilities to cosign will allow for signing public SBOMs and other artifacts
stored in IPFS.

I have a patch that I'd be pleased to offer.


externalConsole: true does not open terminal, just hangs

VSCode Version: 1.0.0
OS Version: osx 10.11.4

Steps to Reproduce:

Create launch.json

{
  "version": "0.2.0",
  "configurations": [
  	{
  		"name": "Launch",
  		"type": "node",
  		"request": "launch",
  		"program": "${workspaceRoot}/dist/index.js",
  		"stopOnEntry": false,
  		"args": [],
  		"cwd": "${workspaceRoot}/dist/",
  		"preLaunchTask": null,
  		"runtimeExecutable": null,
  		"runtimeArgs": [
  			"--nolazy"
  		],
  		"env": {
  			"NODE_ENV": "development"
  		},
  		"externalConsole": true,
  		"sourceMaps": false,
  		"outDir": null
  	},
  	{
  		"name": "Attach",
  		"type": "node",
  		"request": "attach",
  		"port": 5858,
  		"address": "localhost",
  		"restart": false,
  		"sourceMaps": false,
  		"outDir": null,
  		"localRoot": "${workspaceRoot}",
  		"remoteRoot": null
  	}
  ]
}

Press F5.

What happens: Debug-bar shows. If one goes to debug view, a small dot moves left to right, above VARIABLES.
Expected: A terminal should open.
If I change externalConsole to false, I can debug as normal inside vscode, but without any stdin.

@arve0 does it make a difference if you open the Terminal application first and then try to launch the debugging session?

No, it's the same with Terminal open or closed.

@arve0 if the Terminal application is not running, does VS Code make the Terminal application start when launching a debug session?

Not at the PC now, I'll have to check that later today.

if the Terminal application is not running, does VS Code make the Terminal application start

No.
I've created a screen cast: https://youtu.be/xpZOi9hqT4M
Should also mention that I have a case sensitive file system. (You may notice that I'm using typescript 1.9.0-dev, ref #5161.)

@arve0 mentioning the case sensitive file system might have helped to find the problem: the node-debug extension references an AppleScript helper through a path with the wrong character case.
Could you please change the name of the Apple Script helper from TerminalHelper.scpt to terminalHelper.scpt. You can find the helper inside the VS Code application bundle:
/Applications/Visual\ Studio\ Code.app/Contents/Resources/app/extensions/node-debug/out/node/TerminalHelper.scpt

Sweet! That worked 🎉 Thanks.


Index patterns are set for all tenants in Kibana Multitenancy 6.1.1

Hi,
I am running search guard 20.1 on elasticsearch/kibana 6.1.1
I want to set up an index pattern A  for tenant A and an index pattern B for tenant B.
But then i can find index pattern A and B in both tenants. When i set up index pattern A in A, i find it in all other tenant.
Any idea on the issue here ?
Thanks

This is a bug in the MT / KI module and will be fixed with the next release, scheduled for next week.

This has been fixed with the Search Guard and Kibana plugin releases today. You need to upgrade to:

Search Guard 6.x-21.0
Kibana Plugin 6.x-10

For me it still doesn't work with the new upgrade. I have upgraded to kibana 6.1.2 with searcg guard 21.0 and kibana plugin 6.1.2-10.

Hm, somehow this can't be ;) since the complete code that was responsible for copying values between tenants has been removed. How can I reproduce this?

I don't know...I'm using this docker that i have cloned for elasticsearch :
And this docker for Kibana :
I have just changed the version numbers in the dockerfiles.

elasticsearch version : 6.1.2
searchguard version : 21.0
kibana version : 6.1.2
searchguard version (for kibana): 6.1.2-10

Maybe i am missing another config change ? Can I check somewhere the actual version of searchguard launched ? I can see in the logs of elasticsearch or kibana that it is really 6.1.2, but i don't see the version of searchguard

You can visit this endpoint:
/_searchguard/license
Besides license infos this will also print the version numbers of the installed modules. Can you post it here please?
Also, if I understand correctly, steps to reproduce are:

log in to Kibana
switch to a tenant
create index pattern
switch to another tenant

Result: index pattern is present also in second tenant
Correct?

sg_license |
-- | --
uid | "00000000-0000-0000-0000-000000000000"
type | "TRIAL"
issue_date | "2018-01-26"
expiry_date | "2018-03-29"
issued_to | "The world"
issuer | "floragunn GmbH"
start_date | "2018-01-26"
major_version | 6
cluster_name | "*"
msgs | []
expiry_in_days | 47
is_expired | false
is_valid | true
action | ""
prod_usage | "Yes, one cluster with all commercial features and unlimited nodes per cluster."
license_required | true
allowed_node_count_per_cluster | "unlimited"
modules |
AUDITLOG |
default_implementation | "com.floragunn.searchguard.auditlog.impl.AuditLogImpl"
gitsha1 | "4c2d5d34976510c70c82ffbbaeec79f8d64ebf43"
buildTime | "2018-02-05T12:37:00Z"
is_enterprise | "true"
actual_implementation | "com.floragunn.searchguard.auditlog.impl.AuditLogImpl"
description | "Audit Logging"
type | "AUDITLOG"
version | "6.1.2-20.1"
INTERNAL_USERS_AUTHENTICATION_BACKEND |
default_implementation | "com.floragunn.searchguard.auth.internal.InternalAuthenticationBackend"
gitsha1 | "a66a990971337f625e7ac99deeda5fcca32299a6"
buildTime | "2018-02-06T13:10:52Z"
is_enterprise | "false"
actual_implementation | "com.floragunn.searchguard.auth.internal.InternalAuthenticationBackend"
description | "Internal users authorization backend"
type | "INTERNAL_USERS_AUTHENTICATION_BACKEND"
version | "6.1.2-21.0"
REST_MANAGEMENT_API |
default_implementation | "com.floragunn.searchguard.dlic.rest.api.SearchGuardRestApiActions"
gitsha1 | "a0709cbd1e1d61107682162cf5ec3840553dcb4c"
buildTime | "2017-12-22T15:49:45Z"
is_enterprise | "true"
actual_implementation | "com.floragunn.searchguard.dlic.rest.api.SearchGuardRestApiActions"
description | "REST Management API"
type | "REST_MANAGEMENT_API"
version | "6.0-20.0"
HTTP_BASIC_AUTHENTICATOR |
default_implementation | "com.floragunn.searchguard.http.HTTPBasicAuthenticator"
gitsha1 | "a66a990971337f625e7ac99deeda5fcca32299a6"
buildTime | "2018-02-06T13:10:52Z"
is_enterprise | "false"
actual_implementation | "com.floragunn.searchguard.http.HTTPBasicAuthenticator"
description | "HTTP Basic Authenticator"
type | "HTTP_BASIC_AUTHENTICATOR"
version | "6.1.2-21.0"
DLSFLS |
default_implementation | "com.floragunn.searchguard.configuration.SearchGuardFlsDlsIndexSearcherWrapper"
gitsha1 | "b58d834423501292df9d6b976a168d5047607675"
buildTime | "2018-02-05T13:34:50Z"
is_enterprise | "true"
actual_implementation | "com.floragunn.searchguard.configuration.SearchGuardFlsDlsIndexSearcherWrapper"
description | "Document- and Field-Level Security"
type | "DLSFLS"
version | "6.0-20.1"
MULTITENANCY |
default_implementation | "com.floragunn.searchguard.configuration.PrivilegesInterceptorImpl"
gitsha1 | "d9dae44e7d25f475792f553bdeeb4d125492d6cf"
buildTime | "2018-02-05T13:50:27Z"
is_enterprise | "true"
actual_implementation | "com.floragunn.searchguard.configuration.PrivilegesInterceptorImpl"
description | "Kibana Multitenancy"
type | "MULTITENANCY"
version | "6.0-21.0"
compatibility |
modules_mismatch | false

Yes the step to reproduce are correct

This is not an error in Search Guard. We used the the original repos you mentioned above and after configuring multi tenancy everything works as expected.
However, the Dockerfiles and the especially the SG configuration in this repo is not correct:

Multi tenancy is not enabled in sg_config
The Kibana server user that is configured in kibana.yml is not configured in sg_config
There is only one Kibana role, usually you should use two, one for the Kibana serve user, one for regular Kibana users
The permissions for the Kibana server user are not correct. They especially lack the  indices:admin/template* permission
the "sgtenant" HTTP header is  not whitelisted in kibana.yml

After fixing all these configuration errors in the Dockerfile everything works as expected. If you need further assistance in settup up MT, please ask on the Google Groups: https://groups.google.com/forum/#!forum/search-guard
Closing, not a bug.


Whenever run I get this

https://i.imgur.com/Ge8nz8m.png

incorrect version of discum you are running 1.1
while 1.3+ is the latest discum version

incorrect version of discum you are running 1.1
while 1.3+ is the latest discum version

https://i.imgur.com/slbMLxN.png what about this one?

it was unable to find a settings so it used default

havent heard back will be closing


fix offchain-worker std features

Just a minor fix.
Fix the missing std in Cargo.toml

We don't disable the default features, aka std. So, this is not required.


consolidated adapter api module

Implement the consolidated adapter API proposal in which the juttle runtime exports a single module containing the full adapter API as a global, thereby making it so that adapters should not need to require('juttle').
Detailed changes are described in the commits, but a high-level summary includes:

Add a consolidated adapter API module that exports all core juttle functionality needed to implement the adapters.
Export this API as a global as part of loading the adapters and remove the now unneeded Module.load hijacking that was added in #134.
Load the adapter's package.json and check for a `juttleAdapterAPI' entry that contains the version of juttle with which the adapter should be compatible.
Add a reducerDefaultValue utility function to avoid exposing all the reducer implementation to the adapters just to get the empty value.
Add a facade around juttle-test-utils so adapters can simply require('juttle/test').utils instead of the gory path down into runtime/specs.
Add an adapterDescribe hook that functions just like mocha.describe but after setting the JuttleAdapterAPI global. This way adapter unit tests can still pull in portions of the implementation.

Resolves #367

@davidvgalbraith @dmajda @bkutil @mstemm @VladVega

+1

The rest of the changes look good. I think by time of 0.5.0 release we should document the versioning in a readme but it doesn't have to be this pr.

+1 with comments addressed

Addressed all of @dmajda's comments and rebased on top of master. Will merge on green.


More reusable and less effort template / API packaging

As @kakkoyun said:

However, I have long term concerns.
First of all these reviews are getting challenging. We need to define clear ownership of this component and what we would like to achieve. We need to build context and knowledge.
Second, jsonnet files for optional attributes are getting out of control. They are cumbersome and not easy to digest. We should come up with a better pattern.
And last we are getting reckless with the API, we just keep adding things to CRD. The existing API already seems archaic comparing our recent configuration. Moreover, we don't think about the future that we plan, we might need to rewrite the whole CRD to support other signals.

AC:

ACM is able to use more from RHOBS templates
We use Locutus (we can do GitOps + Operator job)
Any user can easily reuse the configuration

One comment I heard was to make things opinionable, otherwise, you can make it work for everyone. Maybe we should be more opinionated but also allow experimenting. E.g a very strict and simple API, but has some extra fields that allow injecting Jsonnet or so.
Another idea is to split functionalities.
We want to represent the deployment topology of components, then their configuration then the Kubernetes specific options. Why we cannot have 3 abstractions instead of one combined. E.g If someone has special Kubernetes it should allow this person to use our templates while swapping Kubernetes logic around. Thinking loudly (:

Thanks @kakkoyun @bwplotka to bring this topic and collect the comments.
You know that ACM is using operator to deploy observatorium ecosystem. as a product or mature solution, it may need to expose more properties in CRD to allow the user to do tuning in large scale environment. for example: more retention and duration parameters, etc.
I have concerns about the operator depends on deployments. Actually, I think the deployments should be generated by operator with pre-defined configurations. the user can use operator to deploy the observatorium or use deployment to deploy.  in this way, we can

Maintain only one repo without inconsistent issues.
Promote operator to be adopt

Yes, that's the plan more or less!
The key part is the API part. If we want to reuse it, we need to find a good way to iterate over the API without too much boilerplate.


[BUG] Can't delete Storage disk

Describe the bug
Deleting a Storage device from the UI doesn't work. I had to go into Longhorn and delete the disk after eviction/scheduling is disabled
To Reproduce
Hosts -> Edit Config -> Storage -> X on the Disk to remove -> Save
Hosts -> Edit Config -> Storage - Disk is still there.
Refer to https://suse.slack.com/archives/C02CN3TT61M/p1714679403477409
Expected behavior
Disk should be removed. Instead one has to go into Longhorn and remove the disk.
Environment

Harvester ISO version: 1.3.0
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630): R620

@Vicente-Cheng  -thanks for this :smile: :+1:  - this looks good on Harvester Version: master-9c0a3a1-head
On a bare-metal HP DL160, 3 Node Cluster, the disk can be removed physically from the node and then cleaned up appropriately on Harvester & Longhorn UI

Disk was provisioned and schedulable, prior - via extra storage class etc.


Make score_amount comparison stricter

score_amount could potentially be 0 causing the validator to fail
We not explicitly check if score_amount is not None.
Fixes #1277
Signed-off-by: Colin Schoen<EMAIL_ADDRESS>

Thanks


Feat/upload aritfacts

I haven't finished with all commands.

CI is still failing

You have to move from target dir instead of dist

target/bundle

It's still failing, pls check the path

it's still failing


What font did you use?

Hello,
I am currently working on a project of mine, which is an textboard (like an imageboard, but without images) and I wanted to make a remix of your logo with the text NostrChan, may I ask what font you used? I can easily find the color palette myself, so that's not needed. Looks very good by the way, nicely done!
Cheers in advance

Hi,
I'm the designer of the nostr logo.
For the logotype I started using a Montserrat which I enlarged and rounded at the corners.
To create your logo I would like to suggest you to put side by side another font in order to suggest a relationship between the two elements but with differences.
nostr(original font a little bit bold) chan (Montserrat regular or a more squared font)
However I used the Montserrat font.
Thank you for appreciation.

Thanks for responding
After doing a little bit of experimenting, I came up with the following logos:

I'll just re-use your icons, as I really like them and I don't want to waste more time on designing (I suck at it, but you gotta do what you gotta do). Thanks again, I'll add your name (and mbaruli's) to the credits section of the README of my project.
Have a good one!

Very nice indeed!
Thanks for sharing it and for the credits.
Best of luck for your project!
--
Marco Barulli
https://marco.barulli.it
On Fri, Oct 27, 2023 at 7:30 PM c6c534e825f4a3d41ede3e67473187d1 <
@.***> wrote:

Thanks for responding
After doing a little bit of experimenting, I came up with the following
logos:
[image: nostrchan-white-on-purple]
https://user-images.githubusercontent.com/125209101/278713593-fb4af69a-bb0f-4480-9bf5-ef01ae36b330.png
[image: nostrchan-purple-on-white]
https://user-images.githubusercontent.com/125209101/278713597-0a9f1c1f-3870-46d4-a542-d01f2dcd0695.png
I'll just re-use your icons, as I really like them and I don't want to
waste more time on designing (I suck at it, but you gotta do what you gotta
do). Thanks again, I'll add your name (and mbaruli's) to the credits
section of the README of my project.
Have a good one!
—
Reply to this email directly, view it on GitHub
https://github.com/mbarulli/nostr-logo/issues/1#issuecomment-1783270172,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAILWGXYJSDHKMYOSBGN7UTYBPVU7AVCNFSM6AAAAAA6P6EAKCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTOOBTGI3TAMJXGI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hi, nice result, it works perfectly.
Thanks for adding us on the credits.


Update RNImgToBase64Module.java

fixed a bug when pass a remote uri rather than local uri in getBase64String method.

Sorry for the late reply ! Thank you for this


(GLES3) Default Material matches clear color

Godot version:
3.2 Beta 1 Mono
OS/device including version:
Ubuntu 19.04
Issue description:
Cube mesh without material (or default) is very difficult to see as it always matches the clear color

Red Clear Color:

Steps to reproduce:

Open the reproduction project
Modify Project Settings->Rendering->Environment->Default Clear Color

Minimal reproduction project:
GodotTestProject.zip

What is the bug here?
You have a white object in an environment with a single color. Of course it takes its color from the environment. This is a consequence of PBR rendering.

The problem is usability. It is impossible to see an object without using the Gismos.
The problem goes away instantly when I add the default environment. How about when no environment is set, it uses the default environment (To be consistent with Material)

The problem is usability. It is impossible to see an object without using the Gismos.

I think showing what the object will actually look like in the final rendered scene is much more important than highlighting the object in the Viewport.

The problem goes away instantly when I add the default environment.

This is expected. The default environment isn't a flat color so you don't get the same effect.
In 4.0 you will be able to specify a background color and a different color to use for radiance. So we will not have this problem the same way.

I think showing what the object will actually look like in the final rendered scene is much more important than highlighting the object in the Viewport.

The object should be visible in both the viewport and the rendered scene. One could argue that the bug is even more prominent in the rendered game because the object is literally invisible if there are no lights.

The default environment isn't a flat color so you don't get the same effect.

This problem can be easily fixed by making a null environment behave as the default environment. This way it would at least be consistent with other rendering elements such as materials.

Apologies for this issue, no change is directly needed right now. Godot projects automatically come with a default environment in default_env.tres which I have mistakingly deleted.


Russian language and notification fix

Hey @mamonth not sure if you can close this PR (as, oddly the way it is setup I cannot), but if you can, please do!


Optionally show homepage from CONTROL in vcpkg search

Is your feature request related to a problem? Please describe.
I wanted google benchmark. If I search "benchmark", I get "benchmark            1.5              A library to support the benchmarking of functions, similar to unit-tests."   It would be nice to know more details, like perhaps author, to understand it's really what i want.
Proposed solution
Show the homepage when running search if --homepage is specified.
Describe alternatives you've considered
Alternatively, if available, there could be a --details, --author etc. switch which provides better origin information.

We recently added the "Homepage" tag to the Control files with something like this as an end goal, we just haven't gotten around to designing and implementing the final step yet.  Would you be interested in implementing the final piece?  If you don't have time to do it then that is okay, we can make it up for grabs to anyone.

I think I can get it done...what is the design you were expecting?

I have not put too much thought into the design.  As a starting point I like the --details switch you suggested.  It would probably work best in a multi-line format, that way it can also show long descriptions.
I have been busy with some new responsibilities so I am going to hand you off to @vicroms.  Good luck!


Asynchronous Support in Scrapegraph-ai

Hello Scrapegraph-ai developers,
I'm currently using Scrapegraph-ai within a FastAPI application and have encountered some issues with asynchronous operations. I'm unable to utilize the asynchronous capabilities effectively, and I'm seeking guidance on how to resolve this.
I've tried to implement asynchronous patterns, but I'm facing challenges.

Look at #694

@jasonshenj you can consider starting a thread to execute like use asyncio.to_thread or loop.run_in_executor

Hi @goasleep do you have idea to how modify asyncloader to make it a sync?

@jasonshenj could you provide an example? would help with reproducibility and help us better track down the root cause of your issues

Hi @goasleep do you have idea to how modify asyncloader to make it a sync?

Why does this need to change? If do that you need to support both async and sync method

@goasleep  I would like to have support for both

@goasleep I would like to have support for both

I'm not sure what you want to ? could you help to give me an example?

Thank you very much for your support and assistance. I have managed to resolve the issue I was facing. Initially, I encountered challenges with Playwright, as it was too time-consuming and unable to capture the desired content. To address this, I separated the data retrieval process, incorporated some anti-detection features, and optimized the speed. However, this led to some asynchronous issues.
After carefully reviewing your source code, I made adjustments by switching from the synchronous interfaces of LangChain that you were using to their asynchronous ones. This change has proven to be quite effective.
Once again, thank you for your help. Your project is truly impressive and has been a great learning experience for me.

such as:
answer = chain.invoke({"question": PROMPT_STR}) To
answer = await chain.ainvoke({"question": PROMPT_STR})

Thank you, I've seen that we still use chain.invoke and I'm going to switch to the async one,
have a nice day


Schema property is ignored

Hi, I have setup a GuestModel that I defined like this:
class Guest extends Typegoose {
  @prop() name: string
  @prop() searchesCount: number
  @prop() profilesCount: number
  @prop() lastCountResetDate: number
}

const GuestModel = new Guest().getModelForClass(Guest, {
  existingMongoose: mongoose,
  schemaOptions: { collection: 'guests' }
})

But I'm having trouble with the name property. When I try to use GuestModel.create, the name value is ignored. And when I try to set it via findOneAndUpdate and selecting by name, I get the following error: Path "name" is not in schema, strict mode is true, and upsert is true.
Setting @prop({ required: true }) on name made no difference.
Edit: the bug only happens when NODE_ENV is production, even though the database is the same.
What am I missing here?

can it be that typegoose just dosnt fully work with the mongoose strict option?


travis master branch build errors

the build errors because it tries to clone the repos over ssh without a key -- switch to https

closed via #91


Add wiki link to readme

Description

Adds wiki tutorial link to readme. closes #10
Checklist for success

[x] This change isn't already implemented by a pending pull request
[x] This change is a child commit of a reasonably recent commit in the master branch

Requests need not be a single commit, but should be a linear sequence of commits (i.e. no merge commits in your PR)

[x] All tests pass locally (see the testing section for more info)
[x] All New behaviors or major functional changes have tests

Updated :+1:


Operations Engineering Design Principles

As an Operations Engineering Team
We want a set of documented and agreed design principles
so that we can be consistent with our approach to designing services, and aid our decision making process.
Functional Requirements:

Whoever picks up this story should define some design principles. We will use this list for further discussion as a Team.

As an example we discussed Opt-in Feature Control for Teams. This is based on user research and that we should enable services so that Service Teams can opt-in to the services and tools that we offer rather than mandating that Teams use our products. This is one design principle that we have already discussed and agreed (freebie!)
This can include technical choices e.g We will user GH Actions, we will write code in language.
Non-Functional Requirements:

Put the initial ideas in a Google Doc or a shared board. This doesn't need to be polished. It is just to facilitate to discussion so that a set of principles can be agreed.

Acceptance Criteria:

[ ] We have a list of design principles that can be discussed as a team.
[ ] Meeting scheduled or offline discussion to present and agree as a team on some principles.
[ ] We will have a set of agreed principles what we can then publish at the end of the discussion.

Notes
Separate user stories will be created for documentation.

I've had some thoughts about other principles this team could consider and document:
User-Centric Design: Always prioritize the needs and experiences of the users. Ensure the design is intuitive and easy to understand, with user feedback at the core of development.
Sustainability: Consider the long-term impact of decisions on the environment and community. Aim for designs that are environmentally friendly and socially responsible.
Transparency: Keep users informed about changes, updates, and how their data is used. Honesty builds trust and loyalty.
Agility: Foster a culture of continuous improvement. Embrace an iterative design process that allows for quick adaptation to feedback and changing requirements.
Inclusivity: Embrace diversity in both the design process and the final product. Consider the needs of different cultural, age, and gender demographics.
Ethical Consideration: Ensure all design and development practices adhere to ethical guidelines. This includes fair treatment of all stakeholders, including employees, users, and the broader community.
Collaboration and Communication: Promote open communication and collaboration across different teams and stakeholders. A collaborative environment fosters creativity and efficiency.
Quality over Quantity: Focus on delivering a quality product rather than rushing to add numerous features. A well-thought-out, high-quality feature will generally be more appreciated by users than many poorly executed ones.
Alignment with Organisational Goals: Ensure the design aligns with the organisation's mission, vision, and strategic goals. This creates cohesion across different areas of the business.
Embrace Failure as Learning: Encourage a culture where failure is seen as an opportunity to learn and grow rather than something to be avoided. This fosters innovation and resilience.

Story warrants further Jamboard session

Not for now


Time zone offset being subtracted from utc timestamp when inserting into column while using prepared statements

rails <IP_ADDRESS>
activerecord-jdbcpostgresql-adapter (61.1-java)
activerecord-jdbc-adapter (61.1-java)
jdbc-postgres (42.2.14)

jruby <IP_ADDRESS> on openjdk8
application.rb

config.time_zone = "UTC"

Table "public.foobars"
 Column            |            Type             | Collation | Nullable |                     Default
--------------------------------------------------------+-----------------------------+-----------+----------+--------------------------------------------------
 id                | integer                     |           | not null | nextval('foobars_id_seq'::regclass)
 created_at        | timestamp without time zone |           |          |
 updated_at        | timestamp without time zone |           |          |

When prepared statements are turned on and a record is inserted into the database, the active record debug log shows the correct UTC timestamp with an offset of +00:00.
[DEBUG] [2021-10-08 13:13:20 -0600] Foobar Create (31.2ms)  INSERT INTO "foobars" ("created_at", "updated_at") VALUES (?, ?)  [["created_at", Fri, 08 Oct 2021 19:13:20.573182000 UTC +00:00], ["updated_at", Fri, 08 Oct 2021 19:13:20.573363000 UTC +00:00], ]

However the inserted record takes my current offset (MDT -6:00) and applies it to the record, saving the incorrect time.
app_development=# select * from foobars;
-[ RECORD 1 ]------------------------------------------+-----------------------------------------

created_at                                             | 2021-10-08 13:13:14.411114
updated_at                                             | 2021-10-08 13:13:14.411256

Turning off prepared statements solves this problem.

Looking into this more, the current timezone in my postgres instance is America/Denver. But once again, MRI does not have this issue using the pg adapter but JRuby does.
psql (13.4)
Type "help" for help.

testdb=# show timezone;
    TimeZone
----------------
 America/Denver
(1 row)

Maybe not common, but does happen.  We have been hit.  It results in a big mess :(

Hi, we are also affected by this issue. As a workaround, we disabled prepared statements; but a fix for this would be great.


Interactive Future Forecast

Although I made it a bit interactive by hover functions but still I am not able to make a detailed display of the future forecast due to some html tag things.
In the html, I have added view-more class which is intended to give a detailed display but whenever it is getting on browser, the edited html code went missing. Adding it again and again by inspect option helped me a bit to shape it properly.
Also please let me know if there were any changes to be made in the contribution I have done.

can you please add the ss

The view more option in this photo is done by the inspect option coz the edited html code is not getting reflected in the page.

The blue color ss is of hover on view more


Cluster creation fails on WSL2

Hi,
I'm trying nvkind on WSL2, in which the nvidia driver is installed in Windows and exposed to the Linux VM automagically.
I followed all steps listed in the requirements section and they all succeed.
However, when I create a cluster using ./nvkind cluster create, the cluster is created and post-processing steps installs packages. During this process, I encounter the following error:
<log truncated for readability>
Setting up nvidia-container-toolkit-base (1.16.0~rc.2-1) ...
Setting up libnvidia-container1:amd64 (1.16.0~rc.2-1) ...
Setting up libnvidia-container-tools (1.16.0~rc.2-1) ...
Setting up nvidia-container-toolkit (1.16.0~rc.2-1) ...
Processing triggers for libc-bin (2.36-9+deb12u4) ...
time="2024-08-02T10:58:37Z" level=info msg="Loading config from /etc/containerd/config.toml"
time="2024-08-02T10:58:37Z" level=info msg="Wrote updated config to /etc/containerd/config.toml"
time="2024-08-02T10:58:37Z" level=info msg="It is recommended that containerd daemon be restarted."
umount: /proc/driver/nvidia: not found
F0802 12:58:38.097622   29676 main.go:45] Error: patching /proc/driver/nvidia on node 'nvkind-mz6kz-worker': running script on nvkind-mz6kz-worker: executing command: exit status 1

I guess the nvidia driver works differently on WSL2 than on a regular Linux host, and therefore /proc/driver/nvidia may not be present. How would I work around this issue?

@jdonkervliet on WSL2 the system-level interface for the VM running docker containers is different from standard linux systems. There is only a single device node (/dev/dxg) that is injected into the system and there is no /proc/driver/nvidia path. Note that because of this there is currently no selective device injection under WSL2 and as such only some of the examples in the nvkind repo are relevant.
Could you describe your hardware setup a bit further so that we can see whether WSL2 support -- or a sane workaround -- is something that we can provide in the short term?


⚠ WIP – Documentation overhaul

See #421

Warnings

:warning:
This pull request may need a CHANGELOG entry.

:warning:

Source/dom/models/Selection.js changed, but not:

📚 its docs
🧪 its tests

That's OK as long as you're refactoring.

  Generated by :no_entry_sign: dangerJS

I find the main page quite dry. There is no context whatsoever about what it is, what you can do, etc. For contrast, https://www.figma.com/developers eases you nicely into it.

Is it intentional for the Actions Page to have the sidebar filled with all the links? Seems like on the deployed branch it is different.

Warnings

:warning:

Source/dom/Factory.js changed, but not:

🧪 its tests

That's OK as long as you're refactoring.

:warning:

Source/dom/layers/Group.js changed, but not:

📚 its docs
🧪 its tests

That's OK as long as you're refactoring.

:warning:

Source/dom/layers/SymbolMaster.js changed, but not:

🧪 its tests

That's OK as long as you're refactoring.

:warning:

Source/dom/models/CurvePoint.js changed, but not:

📚 its docs

That's OK as long as you're refactoring.

:warning:

Source/ui/UI.js changed, but not:

🧪 its tests

That's OK as long as you're refactoring.

  Generated by :no_entry_sign: dangerJS against 7cca6de26cc5621223cb2f7a2a2131030ae5fe09

Closing for #498 that tidies up the git history


Enable seeding in test apps

Move test data to YAML files in db/seeds
Ticket and context
Ticket: HFEYP-622
The automatic seeding of data was removed for TEST app, as QA managed the data there manually.  With the introduction of Review apps, we need seeds to return.
Need to revert https://github.com/DFE-Digital/early-years-foundation-reform/pull/241 and also update the seeds data.  I started to replace the existing .rb files with a seed based on .yml but we did not come to an agreement on whether that was the best way.  Happy to let Rob and Tunde discuss and decide the best plan while I’m away, but the ultimate goal is make seed data easily maintainable.
The previous seeds were developed without content_assets being embedded in the markdown.  In addition articles and users are new and need seed data.

[ ] Review apps and Dev need seed data
[ ] Make seed data maintainable
[ ] Articles (with images) seed data
[ ] User seed data

Tech review
Is there anything that the code reviewer should know?
The existing files in db/seeds we not used in the seeding process. I've moved them to an archive folder as they contain useful data that I believe will be used later to increase the number and content of pages being seeded.
Code quality checks

[ ] All commit messages are meaningful and true

Product review
If this is configured correctly, the review app should be populated with data without additional intervention.
How can someone see it in review app?

Click the link to review app (posted by a github-actions bot below)

QA
The review app is displaying content pages using data from the seed apps


Transfer ownership of this repo?

I'm no longer maintaining this project so it seems kinda silly to have it in my name. @jdf , do you want to take over this repo?

Sure. Do you know how?

https://help.github.com/en/articles/transferring-a-repository
Once that happens, need to add a commit to replace "kazimuth" in all the links to issues.

Ready when you are, @kazimuth!

Alright, transferring now :)

Hmm. WHen I click on the link, I get "this transfer has expired".

Looks like it went through?


Update video reading process

What?

Update video reading process

Why?

To reduce the number of frames to read and improve efficiency

@inuzukam
Thank you for your contribution!
Could you check the comment so that all tests pass.

@kan-bayashi
In my one sample, by specifying start_timestamp and end_timestamp, the reading video that used to take about 1 hour now takes about 2 minute!

Really COOL!


Fix for Sodium 0.6.0-beta.1

The folder structure for sodium was changed to net.caffeinemc from me.jellysquid which caused this mod to break when pressing the button.

Could this get merged?

I was planning to merge when the release came out, do you think I should merge before then?

I was planning to merge when the release came out, do you think I should merge before then?

i think yes, because it is the most used on 1.21 yet

Does this break compatibility with below 1.6? If so, maybe it's worth waiting, if not, def merge.

It would break the mod however I think a simple if statement would fix it, I will look into it.

Neoforge is a bit broken at the moment but when I get it working I can release it.

NeoForge works in an actual instance however I couldn't get it to open in dev for some reason? If you have an idea as to why that is I would love to hear.


datasets

Hello! I am always looking at your beneficial repository.
I'm wondering what difference between the dataset used in the pretrain process and finetuning process.
One uses full and one uses clean, what is the difference between this two datasets?

how can i prepare the dataset?

I have same problem

Figure 4 in parer, reference: https://arxiv.org/pdf/1612.06321.pdf


Specify URL from service to open by default

What should we add or change to make your life better?
Something I thought of when I got off the call.  Maybe an option in the tye.yaml to open a particular URL on a particular service by default when you do tye run.  So if I have a UI or API service that fronts the other services, it just auto opens in my browser if I have that option specified.  So like below it would open http://localhost:whateverport/dashboard in the yaml below
services:
- name: frontend
  startUrl: /dashboard
   # other settings
- name: backend

I realize this could potentially be awkward if someone is just hosting an executable though.
Why is this important to you?
Saves a step of trying to find the URL from the terminal or from the dashboard.

There's a new option in the in the command line in ci builds --dashboard then will open up the dashboard on tye run --dashboard

We could add a commandline argument for this, with the intention of this being used by an IDE like VS or VS Code. We don't really want to put this in tye.yaml because it seems pretty non-portable.
We're going to close this right now based on how long it might be before we're every going to think about tooling integration. Please give us feedback if you can think of a way to make this useful today (a command line switch).


Updates to pre-requisites documentation

Describe the bug
The pre-requisites in documentation need to be updated for the 3rd pointer Steps on how to connect to MySQL database in your PHPMyAdmin. The correct path should be localhost/phpMyAdmin.

The correct path  localhost/phpMyAdmin is updated in pre-requisites document
Refer screenshot

This issue is completed. Closing it.


Add multiple extra config option

Add bash traceback if an error occured
Also fix some unbound variables

Looks good and tests pass. I like the use of mktemp and cleaning up on the error and exit signals.  Also didn't know about bash tracebacks until, now. :sunglasses:
Have one request: could you write a simple unit test to ensure that the fragments are appended to the openvpn config file?  Would be nice to verify that the mktemp files are clean-up too, but kind of hard to test from the outside.
With the config unit test this looks good to merge.

I'll try to figure out how to do that and update the PR

Take a look at the conf_options test.  I'd guess it's a matter of making some config files and grepping them for expected contents.
Could either append that test or add another one using conf_options for reference.
You can run the test locally with test/run.sh "$image" where image is the name of your local docker build -t $image.

I figured out how to add the tests following your instructions. I've added 2 more extra config and validated that they got appended to the config.
I wanted to see if there could be a better way to do those tests, as there is a lot of similar lines. I was wondering if Bats (https://github.com/sstephenson/bats) could be a good replacement or if generating a function that use bash arrays or something could help.
I did not push this idea further though as I don't want to disrupt this too much :)

Thanks for updating this.  The new test looks good.  My main motivation for unit tests is to make sure that other's contributions don't break as has happened in the past and in some extreme cases never worked to begin with.  By this measure, we're doing better then the majority of software projects.
As far as what it could be, you're right.  The current unit test "framework" is hijacked from the upstream docker people as they use it at a massive scale.  However, it seems to be quite limiting and repetitive.
For now, I think this is good.  When something easy to maintain comes along we'll move along to that.


Creating go path is unclear.

When trying to make a gopath, nothing that I do works. Its confusing for me. I would like a more simple way on how to make a go path, I cant find it on the "wiki" ethier.
Please just explain here

I am running Windows 10 not Linux.

http://www.wadewegner.com/2014/12/easy-go-programming-setup-for-windows/
Define in environment variables and run command prompt with admin privileges.

This is beyond the scope of kahoot-hack. Talk to the Go developers if you have a beef with them, lol.


Update Keywords Volume Data is error

Hi there, wanna tell you that Update Keywords Volume Data for all Tracked Keywords is error. All other function of Google ads integrations are normal

Research is error too

@dangson92 Can you please pull the latest release and see if that resolves your issue?

@towfiqi I'm on v2.0.5 and getting this error.

i have the same error, after update on the new version.

@Coysh Can you please check the log and share what error message you got?

After full Restart, and Docker Restart, it works now!


Table is sorted on enter key when it should only be filtered

When adding a filter to a column, if I am using enter key instead of "Apply" button, it filters the column AND sorts (as column header is focused, so table takes that the enter key means sorting as well)

Would expect that when filter is active, sorting would not be triggered as well.
itwinui-react version: 2.12.6

Hi!
Thanks for reporting this issue.
We are currently working on our next major release so won't have time for this.
The fastest way to have this fixes is contributing to our repo! Our contributing guide

Should be fixed in 3.0.7


Removed some mentions about deccomissioned freddy.

This pr fixes #407 in Fredrikam/fredboat Link:https://github.com/Frederikam/FredBoat/issues/407
@napstr you can now close it safely.
Greets from Greece!
-Player 1

This doesn't look right. Instead of removing the mentions this adds even more.

Can you explain your decision to leave the invite link to a decommissioned bot in there, when the task is to remove it?

did I? where?

dammit, lemme review this

is there smth more I forgot? doesnt seem like it


Factor out auth and forms. Fixes #12950

This adds two new packages, both of which are part of the shared framework and ship as NuGet packages for client-side Blazor:

Microsoft.AspNetCore.Components.Authorization
Microsoft.AspNetCore.Components.Forms

Questions
For the authorization classes, should we use the namespace Microsoft.AspNetCore.Components.Authorization?
Currently this retains their existing namespaces, so they are all in M.A.Components. This differs from all the forms classes, which already have the namespaces M.A.Components.Forms. Since the separation of packages is a user-visible feature (in client-side Blazor at least, since there's no shared framework), it now feels more justified to emphasise the seam by having a distinct namespace for .Authorization.
Should .Web reference .Authorization?
Initially that's what I did, as it's what we discussed before. But I think this change achieves more if we don't have that reference. I'm not sure why we'd want .Web to be an uber-package that bundles all the things, especially considering that client-side Blazor projects have to reference .Web and you want to minimize unused dependencies (even when using the linker). This PR currently does not have a reference from .Web to .Authorization, and it works perfectly well.
Should .Web reference .Forms?
Currently in this PR it does, because .Web contains InputText etc. that depend on Forms APIs such as EditContext. If we want to take this a step further, we could also create a M.A.Components.Forms.Web package so that .Web itself doesn't have to reference .Forms. This means that transitively, default client-side Blazor projects wouldn't have to reference System.ComponentModel.Annotations. I haven't gone that far because I think this warrants more discussion about how far is too far when it comes to decoupling packages. Even if we do this, we might still want the default client-side template to reference .Forms.Web otherwise it's hard to discover how to do data editing, which is such a core scenario.

Update We discussed offline, and the answer to all the questions above is "keep it as it is in this PR".

Actually we do want to put Authorization classes in their own namespace.

Rebased on https://github.com/aspnet/AspNetCore/pull/12936 since there are conflicts.

@JunTaoLuo How do you want to go about merging this? The components parts of this PR are done and ready to merge, but I don't know if the multitargeting change you rebased it onto is ready to go in.
If your parts of this are done, do you want to merge it?

I rebased after merging the multitargeting PR, this is ready to go in.

Hmm the test failure looks like it might be related to the change:
 Templates.Test.BlazorServerTemplateTest.BlazorServerTemplateWorks_IndividualAuth(useLocalDB: False)
Project new blazorserver  --auth Individual failed to publish.\r\nProcess exited with code 1\nStdErr: \nStdOut: Microsoft (R) Build Engine version 16.3.0-preview-19329-01+d31fdbf01 for .NET Core\r\nCopyright (C) Microsoft Corporation. All rights reserved.\r\n\r\n  Restore completed in 19.99 ms for F:\\workspace\\_work\\1\\s\\src\\ProjectTemplates\\test\\bin\\Release\\netcoreapp3.0\\TestTemplates\\AspNet.blazorserverindividual.ekm3gq2pvfa\\AspNet.blazorserverindividual.ekm3gq2pvfa.csproj.\r\n  You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview\r\nStartup.cs(40,32): error CS0246: The type or namespace name 'AuthenticationStateProvider' could not be found (are you missing a using directive or an assembly reference?) [F:\\workspace\\_work\\1\\s\\src\\ProjectTemplates\\test\\bin\\Release\\netcoreapp3.0\\TestTemplates\\AspNet.blazorserverindividual.ekm3gq2pvfa\\AspNet.blazorserverindividual.ekm3gq2pvfa.csproj]\r\nStartup.cs(40,22): error CS0311: The type 'AspNet.blazorserverindividual.ekm3gq2pvfa.Areas.Identity.RevalidatingIdentityAuthenticationStateProvider<Microsoft.AspNetCore.Identity.IdentityUser>' cannot be used as type parameter 'TImplementation' in the generic type or method 'ServiceCollectionServiceExtensions.AddScoped<TService, TImplementation>(IServiceCollection)'. There is no implicit reference conversion from 'AspNet.blazorserverindividual.ekm3gq2pvfa.Areas.Identity.RevalidatingIdentityAuthenticationStateProvider<Microsoft.AspNetCore.Identity.IdentityUser>' to 'AuthenticationStateProvider'. [F:\\workspace\\_work\\1\\s\\src\\ProjectTemplates\\test\\bin\\Release\\netcoreapp3.0\\TestTemplates\\AspNet.blazorserverindividual.ekm3gq2pvfa\\AspNet.blazorserverindividual.ekm3gq2pvfa.csproj]\r\n\r\nExpected: True\r\nActual:   False
   at Templates.Test.BlazorServerTemplateTest.BlazorServerTemplateWorks_IndividualAuth(Boolean useLocalDB) in /_/src/ProjectTemplates/test/BlazorServerTemplateTest.cs:line 100
--- End of stack trace from previous location where exception was thrown ---
Output:
==> F:\workspace\_work\1\s\.dotnet\dotnet.exe new blazorserver --debug:custom-hive "F:\workspace\_work\1\s\src\ProjectTemplates\test\bin\Release\netcoreapp3.0\TestTemplates\\Hives\f2ac4a6d-31e5-4642-bcbb-8bb14b4078bf\.templateengine" --auth Individual -o F:\workspace\_work\1\s\src\ProjectTemplates\test\bin\Release\netcoreapp3.0\TestTemplates\AspNet.blazorserverindividual.ekm3gq2pvfa [F:\workspace\_work\1\s\src\ProjectTemplates\test\bin\Release\netcoreapp3.0\]
The template "Blazor Server App" was created successfully.
This template contains technologies from parties other than Microsoft, see https://aka.ms/aspnetcore/3.0-third-party-notices for details.

Processing post-creation actions...
Running 'dotnet restore' on F:\workspace\_work\1\s\src\ProjectTemplates\test\bin\Release\netcoreapp3.0\TestTemplates\AspNet.blazorserverindividual.ekm3gq2pvfa\AspNet.blazorserverindividual.ekm3gq2pvfa.csproj...
  Restore completed in 218.71 ms for F:\workspace\_work\1\s\src\ProjectTemplates\test\bin\Release\netcoreapp3.0\TestTemplates\AspNet.blazorserverindividual.ekm3gq2pvfa\AspNet.blazorserverindividual.ekm3gq2pvfa.csproj.

Restore succeeded.

Publishing ASP.NET application...
==> F:\workspace\_work\1\s\.dotnet\dotnet.exe publish -c Release -p:PublishWithAspNetCoreTargetManifest=false [F:\workspace\_work\1\s\src\ProjectTemplates\test\bin\Release\netcoreapp3.0\TestTemplates\AspNet.blazorserverindividual.ekm3gq2pvfa]
Microsoft (R) Build Engine version 16.3.0-preview-19329-01+d31fdbf01 for .NET Core
Copyright (C) Microsoft Corporation. All rights reserved.

  Restore completed in 19.99 ms for F:\workspace\_work\1\s\src\ProjectTemplates\test\bin\Release\netcoreapp3.0\TestTemplates\AspNet.blazorserverindividual.ekm3gq2pvfa\AspNet.blazorserverindividual.ekm3gq2pvfa.csproj.
  You are using a preview version of .NET Core. See: https://aka.ms/dotnet-core-preview
Startup.cs(40,32): error CS0246: The type or namespace name 'AuthenticationStateProvider' could not be found (are you missing a using directive or an assembly reference?) [F:\workspace\_work\1\s\src\ProjectTemplates\test\bin\Release\netcoreapp3.0\TestTemplates\AspNet.blazorserverindividual.ekm3gq2pvfa\AspNet.blazorserverindividual.ekm3gq2pvfa.csproj]
Startup.cs(40,22): error CS0311: The type 'AspNet.blazorserverindividual.ekm3gq2pvfa.Areas.Identity.RevalidatingIdentityAuthenticationStateProvider<Microsoft.AspNetCore.Identity.IdentityUser>' cannot be used as type parameter 'TImplementation' in the generic type or method 'ServiceCollectionServiceExtensions.AddScoped<TService, TImplementation>(IServiceCollection)'. There is no implicit reference conversion from 'AspNet.blazorserverindividual.ekm3gq2pvfa.Areas.Identity.RevalidatingIdentityAuthenticationStateProvider<Microsoft.AspNetCore.Identity.IdentityUser>' to 'AuthenticationStateProvider'. [F:\workspace\_work\1\s\src\ProjectTemplates\test\bin\Release\netcoreapp3.0\TestTemplates\AspNet.blazorserverindividual.ekm3gq2pvfa\AspNet.blazorserverindividual.ekm3gq2pvfa.csproj]

Care to take a look @SteveSandersonMS

Yes, thanks. Pushed an update. Will check the results now.


song: Banshee and Pogo not detected

Description
Banshee and Pogo are not detected with the new player-detection. Maybe others too, did not test with all..
    printf -v players "|%s" "${players[@]}"
    player="$(ps -e | awk -v pattern="(${players:1})$" '$0 ~ pattern {print $NF; exit}')"

Changing ps -e to ps -x works for Pogo but not Banshee.
For both ps -e output does not contain the player name.
ps -x
ps -x | grep banshee
24447 pts/1    Sl+    0:01 banshee /usr/lib/banshee/Banshee.exe
24468 pts/0    S+     0:00 grep banshee

ps -x | grep pogo
24480 pts/1    Sl+    0:00 python3 /usr/bin/pogo
24492 pts/0    S+     0:00 grep pogo

Neofetch version
git-master

I’ll fix this 👍

Fixed. https://github.com/dylanaraps/neofetch/commit/01bd13a3b555f0e8b4eb201c1a68423a1bd7bcf7
Let me know if the issue still occurs, I couldn't get banshee or pogo working on my machine.

Both working now. :+1:

Cheers :+1:


android_defines_test passing even when no devices are found

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8756889553112536529/+/u/run_android_defines_test/stdout

@zanderso FYI

At the bottom of the logs I'm seeing this:
Task result:
{
  "success": false,
  "reason": "Task failed: DeviceException: No Android devices detected"
}

════════════════╡ ••• Finished task "android_defines_test" ••• ╞════════════════

══════════════╡ ••• Flaky status for "android_defines_test" ••• ╞═══════════════

Consistently failed across all 3 executions.
flaky: false

Does that not mean that the task failed?

That's correct but I'd expect the test step to be red

Not sure if the test_util.test is not propagating the exit code or the test itself is not reporting the proper exit code.
@keyonghan would you mind taking a look the test_util method?

Maybe related to our recent retry wrapper change. Taking a look.

It's not. It should be related to the exit code.
Another example where the step failed but shown as green: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux_pixel_7pro complex_layout_scroll_perf_impeller_gles__timeline_summary/98/overview
Another issue here is: the task is marked as failed in dashboard though the build is marked as success.

The most recent tree red on Linux analyzer_benchmark has same issue. The test step fails but the build is Succeed.
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux analyzer_benchmark/7177/overview

Wondering if the sh/ps1 wrapper somehow hides the exit code in some corner cases.
https://flutter-review.googlesource.com/c/recipes/+/54763/7/recipe_modules/test_utils/api.py#137

This seems to be a bit more widespread. I added @godofredoc and @keyonghan to a chat thread. Is there a recent change that should be reverted?

A fix is landing: https://flutter-review.googlesource.com/c/recipes/+/54925

This probably needs a PSA to discord and<EMAIL_ADDRESS>

Fix landed. Marking as resolved.
Correct status is now surfaced: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux technical_debt__cost/16684/overview

@keyonghan Is this happening again?
https://ci.chromium.org/ui/p/flutter/builders/prod/Windows_arm64 run_release_test_windows/1586/overview
Test shows as passed but logs indicate it failed and the tree is saying it failed:
Task result:
 {
   "success": false,
   "reason": "Task failed: Did not find expected line\n\nBuilt build\\windows\\x64\\runner\\Release\\app.exe\n\nin flutter run --release stdout\n\n[√ Built build\\windows\\x64\\runner\\Release\\ui.exe, , Flutter run key commands., h List all available interactive commands., c Clear the screen, q Quit (terminate the application on the device)., , Application finished.]\n"
 }
 Finished task "run_release_test_windows"
 Flaky status for "run_release_test_windows"
 Consistently failed across all 3 executions.
 flaky: false

We should add similar logic to windows (.ps1) file as well.

https://flutter-review.googlesource.com/c/recipes/+/54932 fixes the windows case. Please reopen if you see this again.


Use pytest mechanism to drop files inserted to make test more robust

Fixes #364

Codecov Report

Merging #367 (3afcee2) into master (2003db7) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #367      +/-   ##
==========================================
+ Coverage   76.94%   76.95%   +0.01%
==========================================
  Files          67       67
  Lines        6455     6458       +3
==========================================
+ Hits         4967     4970       +3
  Misses       1488     1488

Impacted Files
Coverage Δ

tests/unit_tests/test_db_handler.py
95.00% <100.00%> (+0.10%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Introduce sensitive tag in web scan configuration parts

Situation
DAST Reports shall not contain sensitive/secret information like headers etc. currently the DAST report shows the given headers which can contain sensitive information.
Wanted
It shall be possible to add something like "annotation" to the corresponding JSON parts, so its programmatically possible to identify sensitive information .
Also this sensivie information shall not be inside the DAST reports (OWASP ZAP)
Solution

TBD: Find the best location to filter the sensitive information and replace it with **************

Update after discussion
We want to introduce the sensitive tag, but it will be set to true on default. This way if nothing is configured the content of the header will not be inside the report.
If the user wants the header data inside the report "sensitive" : false must be set explicitly.
Example
After a scan with the config below a finding which contains the header Authorization: Basic abc will only contain Authorization: ******** inside the report.
{
    "apiVersion": "1.0",
    "webScan": {
        "url": "https://productfailure.demo.example.org",
        "headers" : [ {
	   "name" : "Authorization",
	   "value" : "Basic abc",
	   "onlyForUrls" : [...],
	   "sensitive" : true // true on default, means will be masked
	} ]
    }
}


fix: unexcepted stop because https://github.com/yuin/goldmark/commit/…

ast.WalkStop will stop rendering after https://github.com/yuin/goldmark/commit/0b4973017794ac7f7d89593ad92542fed5c6dc54
https://github.com/yuin/goldmark/blob/21437947a30d8568d1fc1c4244da555c4576c6e3/ast/ast.go#L481-L485

Thanks!


Trigger an action on tap and on dismissed

Hi ! Yeah, you can do that with a controller now.
Here's some code:
@override
void initState() {
  // Programatically display tooltip after two seconds
  Future.delayed(const Duration(seconds: 2), () {
    tooltipController.showTooltip(immediately: false);
  });

  tooltipController.addListener(() {
    // Prints the enum value of [TooltipStatus.isShowing] or [TooltipStatus.isHiding]
    if (tooltipController.value == TooltipStatus.isShowing) {
      // my logic
    }
  });
}

You'll just need to create a controller as you would any other and pass it through the JustTheTooltip constructor.

If you mean it'd be cool to have callbacks on the actual constructor:
JustTheTooltip(
  onClose: () {},
  onOpen: () {}
)

that's another thing and I'd gladly look at a PR

JustTheTooltip(
onClose: () {},
onOpen: () {}
)
Yeah, that's what I meant
I hope to be added soon, Thank you

Thank you the suggestion. 0.0.11 now has these callbacks. For any issues with them, please raise a new issue. Thank you !
JustTheTooltip(
  onDismiss: () {
    // do something
  },
  onShow: () {
    // something else
  }
),


CTK API documentation (doxygen) is dead

https://commontk.org/docs/html/classes.html is dead

It is still dead.

@jcfr would it be possible to set up a github action to generate and publish the doxygen doc on github pages?

@jcfr do you have any ide how to solve this?

how to solve this?

Indeed, I will address this.

@jcfr Users keep asking for this.

The given file won't open because the whole /docs path is dead