Tag Helper is generating the empty link

I am trying creating link using tag helper but that is creating the empty link. I have included Tag helper reference as well. PFA the code file:
TagHelper.txt

Hi @Sourabh721992 could you please specify in more detail what you're doing and what you're trying to achieve? Could you share a minimal reproduction (source code) of the problem so we can help.

Hi,
I am using a tag anchor link to go from view, Index.cshtml to view, Details.cshtml. Both views are linked to HomeController in the solution. But what is happening is tag helper is creating empty link for me. I am attaching all the files.
Index.txt
Details.txt
_ViewImports.txt
HomeController.txt

Are you following any example or documentation?
https://docs.microsoft.com/en-us/aspnet/core/mvc/views/tag-helpers/intro?view=aspnetcore-5.0 might help you, there are also some samples here: https://github.com/dpaquette/TagHelperSamples
Unfortunately, this is beyond my knowledge. @Pilchie is this something you can help with?

Yes I have followed the documentation but I am not sure why the link is href is not getting generated.


Integrate with go-leak library and fix leaks

Summary

PR Status
Type
Impact level

Ready
Bug
Medium

Description

Integrates with a Goleak detection library.
Fixed ~26 identified leaks in tests

Why is this not merged?

I guess I'm still awaiting a review here.


[Suggestion] Only allow setting the username for social links in params.toml file

Right now the whole URL is being passed in the param.toml file.
This has a side effect: The theme wouldn't be able to make use of using the username right away.
For instance in the twitter share button, the link loads up the author name instead of the twitter username in the via part.

My username for twitter is @nisrulz.
One can work around this by extracting the username from the path string. However, if we just take in username then it becomes simpler for other usecases too related to social media actions.
Hard coding the base URL also means that the theme works for people out of the box. They just need to fill in their usernames.
Thoughts?

I changed the share data structure
Now, you can do like this.
params.toml file
...
[[share]]
  name = "facebook"
  username = "zzossig"

[[share]]
  name = "twitter"
  username = "zzossig"

I added 3 sharing platforms but it's giving me error all the time here is the link Live site  I just added username but everytime it's shows error


Client observe does not work for large message

On the client side, I want to observe a resource with a large message and I'm getting a bad request as a status code.
I would like to intensify that for small and medium messages(size until 1K), it works well.
 ...   const setup = {     host: 'CLOUD_IP',     observe: true,     port: 5683,     pathname: '/middlewareToCloud',     method: 'GET' }     const req = coap.request(setup)
I had added the option Block2, but it did not work:
     req.setOption('Block2', Buffer.of(0x2))
What do I need to do to get the payload for the large message?
Am I doing something wrong or is it an issue for a large message?

I don't know if it can help, but it's the current response.
ObserveReadStream {   _readableState: ReadableState {     objectMode: true,     highWaterMark: 16,     buffer: BufferList { head: null, tail: null, length: 0 },     length: 0,     pipes: null,     pipesCount: 0,     flowing: null,     ended: false,     endEmitted: false,     reading: false,     sync: true,     needReadable: false,     emittedReadable: false,     readableListening: false,     resumeScheduled: false,     paused: true,     emitClose: true,     autoDestroy: false,     destroyed: false,     defaultEncoding: 'utf8',     awaitDrain: 0,     readingMore: false,     decoder: null,     encoding: null   },   readable: true,   _events: [Object: null prototype] {     close: [Function],     deregister: [Function]   },   _eventsCount: 2,   _maxListeners: undefined,   payload: <Buffer >,   options: [],   code: '4.00',   method: undefined,   headers: {},   url: '/',   rsinfo: { address: 'CLOUD_IP', family: 'IPv4', port: 5683, size: 12 },   outSocket: { address: '<IP_ADDRESS>', family: 'IPv4', port: 56920 },   _packet: {     code: '4.00',     confirmable: false,     reset: false,     ack: true,     messageId: 60029,     token: <Buffer 89 fb ce 8a d6 ce 64 a8>,     options: [],     payload: <Buffer >   },   _payloadIndex: 0,   _lastId: undefined,   _lastTime: 0,   _disableFiltering: false,   [Symbol(kCapture)]: false

Hi! Thanks for reporting the issue :) Could you try out a bigger block size? You can increase argument in the buffer up to 0x06 (for the maximum blocksize of 1024 bytes), maybe this could help?

I changed the block2 toreq.setOption('Block2', Buffer.of(0x6))

Hmm, that is strange :/ I found no indication in the specification both for blockwise and observe that could hint why this is interpreted as a bad request. Does sending the observe request without the block2 option set also lead to an error?
Perhaps it could also be an issue with the server implementation? Is the server also using node-coap or using another library?

Good point @JKRhb!
From server-side is another library(libcoap).
I'll will change from libcoap to node-coap to check!
Currently, I use the Copper plugin to execute some tests and I can get large messages using this plugin.


Question ⁉: How to permenately uncap, run at startup

I managed to swap my CAPS and ESC using these commands
uncap
uncap 0x1b:0x14

But when I restart Windows they aren't swapped anymore. How can I permanently swap these two keys? You may put this in the REAME.md. If it is already explained in the readme file I think you should make it more clear.

Uncap does not swap keys permanently. This is by design. You can however make Uncap part of Windows startup, so that whenever the system starts, Uncap runs automatically. See issue #15 for a discussion about this.

Ok, I will close this issue. I hope to add these instruction in the README file
https://github.com/susam/uncap/issues/15#issuecomment-727639874


ACL host option support

In traditional ACL client (embedded kafka-acls.sh) it is possible to define host parameter (ip address) that ACL will affect to.
ACL for resource options:

principal
host
operation
permissionType

Example for ACL with host option:
kafka-acls.sh --bootstrap-server=broker.example.com:9092 --add --allow-principal User:* --allow-host <IP_ADDRESS> --operation ALL --topic bar1
list ACL:
Current ACLs for resource `ResourcePattern(resourceType=TOPIC, name=bar1, patternType=LITERAL)`:
 	(principal=User:*, host=<IP_ADDRESS>, operation=ALL, permissionType=ALLOW)

More than that I see host option in the julie ACL execution log and it has wildcard value "host" : "*".
Example for principal "User:Alice" with consumer access to topic bar1:
{
  "Operation" : "com.purbon.kafka.topology.actions.access.CreateBindings",
  "Bindings" : [ {
    "resourceType" : "GROUP",
    "resourceName" : "*",
    "host" : "*",
    "operation" : "READ",
    "principal" : "User:Alice",
    "pattern" : "LITERAL",
    "scope" : null
  }, {
    "resourceType" : "TOPIC",
    "resourceName" : "bar1",
    "host" : "*",
    "operation" : "READ",
    "principal" : "User:Alice",
    "pattern" : "LITERAL",
    "scope" : null
  }, {
    "resourceType" : "TOPIC",
    "resourceName" : "bar1",
    "host" : "*",
    "operation" : "DESCRIBE",
    "principal" : "User:Alice",
    "pattern" : "LITERAL",
    "scope" : null
  } ]
}

Is it possible to use option "host" in topology ACL configuration, like this?
context: "example"
projects:
  - name: "kafka"
    topics:
      - name: "bar1"
        config:
          retention.ms: "604800000"
        consumers:
          - principal: "User:Alice"
            host: "<IP_ADDRESS>"

Or maybe there is any other way to do it?

I found the solution. It can be done via Custom JulieRoles - https://julieops.readthedocs.io/en/latest/futures/define-custom-roles.html
Steps:

describe custom ACL in roles.yml

roles:
  - name: "custom_acl"
    acls:
      - resourceType: "Topic"
        resourceName: "bar1"
        patternType: "LITERAL"
        host: "<IP_ADDRESS>"
        operation: "READ"
        permissionType: "ALLOW"
      - resourceType: "Topic"
        resourceName: "bar1"
        patternType: "LITERAL"
        host: "<IP_ADDRESS>"
        operation: "DESCRIBE"
    - resourceType: "Group"
        resourceName: "*"
        patternType: "LITERAL"
        host: "<IP_ADDRESS>"
        operation: "READ"

set custom role to topology config

context: "example"
projects:
  - name: "kafka"
    custom_acl:
      - principal: "User:Alice"
    topics:
      - name: "bar1"
        config:
          retention.ms: "604800000"

set custom acl path in config
julie.roles=/roles.yml

yes, this is "the way" for now. but somehow I agree with you that introducing this to the other abstractions is a good idea.


Issue 948 utf8 import

Closes #948 by encoding UTF-8 characters in the import prior to base64 encoding.

Decided to leave in decode code commented out in case future need for decoding arises.


[BUG] Failed to load extension (.NET)

does loading extension still work?
because it seems that its prefixing google chrome path from the actual extension path which makes it fail.
Im getting this error when launching playwright.
---------------------------
Error Loading Extension
---------------------------
Failed to load extension from: C:\Program Files (x86)\Google\Chrome\Application\108.0.5359.125\"D:\Projects\.NET Shared Codes\scraptest2playwrite\scraptest2playwrite\bin\Debug\chrome-extensions\ublock-origin-lite-chrome". Manifest file is missing or unreadable
---------------------------
OK
---------------------------

heres the command line;
--disable-extensions-except="D:\Projects\.NET Shared Codes\scraptest2playwrite\scraptest2playwrite\bin\Debug\chrome-extensions\ublock-origin-lite-chrome"
--load-extension="D:\Projects\.NET Shared Codes\scraptest2playwrite\scraptest2playwrite\bin\Debug\chrome-extensions\ublock-origin-lite-chrome"

' lstArgs here contains the command line above;

        Dim config As New BrowserTypeLaunchPersistentContextOptions
        With config
            .Channel = "chrome"
            .Locale = "en-US"
            .Headless = False
            .Devtools = True
            .DownloadsPath = Path.GetFullPath(".\chrome-downloads")
            .Args = lstArgs
            .IgnoreDefaultArgs = {"--disable-extensions"}
            .JavaScriptEnabled = True
        End With

        Dim browser = PL.Chromium.LaunchPersistentContextAsync(Path.GetFullPath(".\chrome-data"), config).Result

Im using .net 4.6.1, and 1.28.0 version of playwright nugget,
anyone?

Yes it should work, did you see the error? Manifest file is missing or unreadable

Yes it should work, did you see the error? Manifest file is missing or unreadable

yes. i can see the error thats why i posted it.
you can also see it was showing an additional path from the extension which i did not even set.
and yes, manifest file exist and extension path i set is true and correct.

Looks like its caused by the quotes which are used and that your path contains spaces. I recommend to use single quotes or no quotes at all, then it should work.
Closing since this is more a Chromium related issue rather than Playwright.

i dont think this is an issue with chromium since im using the same extension path and same argument list when using puppeteer and it works using installed google chrome or using a vanilla chromium.
even the provided sample from this full repo causes the same error if extension path is added.
using Microsoft.Playwright;

using var playwright = await Playwright.CreateAsync();

// Failed to load extension from: C:\Program Files(x86)\Google\Chrome\Application\109.0.5414.74\ ...... Manifest file is missing or unreadable
string[] lstArgs = { @"--disable-extensions-except=""D:\Projects\.NET Shared Codes\scraptest2playwrite\scraptest2playwrite\bin\Debug\chrome-extensions\ublock-origin-lite-chrome""",
@"--load-extension=""D:\Projects\.NET Shared Codes\scraptest2playwrite\scraptest2playwrite\bin\Debug\chrome-extensions\ublock-origin-lite-chrome"""};

// Failed to load extension from: C:\Program Files(x86)\Google\Chrome\Application\109.0.5414.74\ ...... Manifest file is missing or unreadable
//string[] lstArgs = { @"--disable-extensions-except='D:\Projects\.NET Shared Codes\scraptest2playwrite\scraptest2playwrite\bin\Debug\chrome-extensions\ublock-origin-lite-chrome'",
//@"--load-extension='D:\Projects\.NET Shared Codes\scraptest2playwrite\scraptest2playwrite\bin\Debug\chrome-extensions\ublock-origin-lite-chrome'"};

// will error and will not work because path needs to be inside a single or double quote
//string[] lstArgs = { @"--disable-extensions-except=D:\Projects\.NET Shared Codes\scraptest2playwrite\scraptest2playwrite\bin\Debug\chrome-extensions\ublock-origin-lite-chrome",
//@"--load-extension=D:\Projects\.NET Shared Codes\scraptest2playwrite\scraptest2playwrite\bin\Debug\chrome-extensions\ublock-origin-lite-chrome"};

// even if you put your extension folder on drive c: (testing with single/double quote)
// Failed to load extension from: C:\Program Files(x86)\Google\Chrome\Application\109.0.5414.74\"C:\chrome-extensions\ublock-origin-lite-chrome".Manifest file is missing or unreadable
//string[] lstArgs = { @"--disable-extensions-except=""C:\chrome-extensions\ublock-origin-lite-chrome""",
//@"--load-extension=""C:\chrome-extensions\ublock-origin-lite-chrome"""};

string[] ignoreArgs = { "--disable-extensions", "--enable-automation" };

await using var browser = await playwright.Chromium.LaunchPersistentContextAsync(Path.GetFullPath($".\\chrome-data-dir"),
    new BrowserTypeLaunchPersistentContextOptions() {  Channel = "chrome", Headless = false,
        IgnoreDefaultArgs = ignoreArgs, Args = lstArgs, ExecutablePath = @"C:\Program Files (x86)\Google\Chrome\Application\chrome.exe" });

var page = await browser.NewPageAsync();
await page.GotoAsync("https://playwright.dev/dotnet");
await page.ScreenshotAsync(new PageScreenshotOptions { Path = "screenshot.png" });

The following works for me, it contains spaces and brackets:

using Microsoft.Playwright;

using var playwright = await Playwright.CreateAsync();
var extensionPath = "C:\\Users\\maxschmitt\\development\\playwright-dotnet\\src\\Playwright.Tests.TestServer\\assets\\simple-extension (81)";
await using var context = await playwright.Chromium.LaunchPersistentContextAsync("", new(){
    Headless = false,
    Args = new[] {
        $"--disable-extensions-except={extensionPath}",
        $"--load-extension={extensionPath}"
    },
});
await context.Pages[0].PauseAsync();

Looks like in your case the issue is that you did not escape the slashes.

The following works for me, it contains spaces and brackets:
using Microsoft.Playwright;

using var playwright = await Playwright.CreateAsync();
var extensionPath = "C:\\Users\\maxschmitt\\development\\playwright-dotnet\\src\\Playwright.Tests.TestServer\\assets\\simple-extension (81)";
await using var context = await playwright.Chromium.LaunchPersistentContextAsync("", new(){
    Headless = false,
    Args = new[] {
        $"--disable-extensions-except={extensionPath}",
        $"--load-extension={extensionPath}"
    },
});
await context.Pages[0].PauseAsync();

Looks like in your case the issue is that you did not escape the slashes.

FINALLY it works.. lol
case solved. thanks...


Maestral.app opens with "Welcome" window despite having been configured

So, today when the Maestral.app launched at login it presented us with the "Welcome to Maestral ... Link Dropbox Account" window.  This feels odd since we did configure Maestral several months ago in the macOS gui and have been using it without much difficulty ever since...
This is on macOS 10.13.6 with Maestral.app 1.5.2
Should I just go ahead and follow the prompts to link the dropbox account again?
Maybe my maestral.plist or Application Support files just became corrupted?

Apologies for not getting back to this earlier. It does appear like the config file getting lost or moved somehow. Relinking should do the job, and hopefully it should not occur again.
Actual corruption of the config file, or Dropbox access being revoked, should result in an explicit error message instead.


Refine and prove pf3, comment on issue with defining il3

@cwjnkins. I made progress by refining and proving pf3, but I did not prove its requirements.  These can presumably be proved, but I couldn't quickly/easily do it.  I think the way I defined ( bt₃ and) il₃ has caused a lot of unnecessary pain, so I am stopping here.  I think this provides good motivation for the weakest precondition infrastructure you have suggested for the Error monad :smile:.  Feedback/input welcome.

I agree -- it definitely provides good motivation for changing how we handle proofs running in the error monad. See PR #128 for an example of how things might change.


OCM-6106 | node drain grace period for hosted control planes

Support node drain grace period for NodePools of HyperShift-enabled clusters. The node drain grace period is supported for these operations:

Create machinepool (nodepool)
Update machinepool
Describe machinepool

https://issues.redhat.com/browse/OCM-6106

@robpblake Thanks for the review. I think I've addressed all the comments, but please let me know if I've missed something.

/test test
/test commits

/hold API changes have not merged yet.

/unhold

/approve


Support for more options

Hey there,
I'd love to see some support for more options (and maybe even custom ones) like systemctl hybrid-sleep - Hibernate and Suspend both have been acting up lately, but together they work fine - as well as support for customisations (Disabling modules, adding custom ones, ...)
Is this viable?
Thanks!

Hi, thanks for opening an issue. This extension currently supports custom configurations (see here) to add or modify entries and desktops (currently can't disable entries but I'll work on that). If you think any of the desktops or entries should be upstreamed I am always open to pull requests or feature requests.
I will leave this issue open for now in case the instructions need clarification and / or until disabling entries is do-able.

Hi, thanks for opening an issue. This extension currently supports custom configurations (see here) to add or modify entries and desktops (currently can't disable entries but I'll work on that). If you think any of the desktops or entries should be upstreamed I am always open to pull requests or feature requests.
I will leave this issue open for now in case the instructions need clarification and / or until disabling entries is do-able.

Oh XDG_CONFIG_HOME is unset for me, that's probably why there's no config to be found

When  XDG_CONFIG_HOME is undefined it defaults to $HOME/.config according to the XDG Base Directory Specification

When  XDG_CONFIG_HOME is undefined it defaults to $HOME/.config according to the XDG Base Directory Specification
Also you can now disable entries which I have documented in the configuration section

yeah I completely overread that.
I also just now discovered, that there are no config files in .config/ulauncher-system, but rather in .local/share/ulauncher/extensions.
Thanks for your help!

Hi, I would not recommend changing configurations in the extensions folder as this could possibly affect updating the extension in the future (from my understanding ulauncher just pulls the repository to update). To modify configs I would instead recommend copying files from .local/share/ulauncher/extensions/ulauncher-system to $HOME/.config/ulauncher-system and then modifying them with the info in configuration


Fix a potential bug in TestControllerBurstReplicas

Fix a potential bug in TestControllerBurstReplicas: manager.podStore.Store.Add(&pod) actually adds a pointer to a local copy of pod

I signed it!
On Fri, May 15, 2015 at 1:46 PM, googlebot<EMAIL_ADDRESS>wrote:

Thanks for your pull request. It looks like this may be your first
contribution to a Google open source project, in which case you'll need to
sign a Contributor License Agreement (CLA).
[image: :memo:] Please visit https://cla.developers.google.com/
https://cla.developers.google.com/ to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll
verify. Thanks.

If you've already signed a CLA, it's possible we don't have your
GitHub username or you're using a different email address. Check your
existing CLA data https://cla.developers.google.com/clas and verify
that your email is set on your git commits
https://help.github.com/articles/setting-your-email-in-git/.
If you signed the CLA as a corporation, please let us know the
company's name.

—
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/kubernetes/pull/8306#issuecomment-102268493
.

No point in waiting for Travis


resolve problems with unit test workflow

close #316
close #318

Caught up with #314

The remaining problems do not happen with databroker 1.2.  The CI uses databroker v2.0.0b31 (at this time).  All of these problems are related to storing the UB matrix (and other information) in the run as a detector.
FAILED hkl/tests/test_save_restore_UB.py::test_fourc_orientation_save - assert 0 == 1
FAILED hkl/tests/test_save_restore_UB.py::test_fourc_run_orientation_info - AssertionError: assert 'fourc' in {}
FAILED hkl/tests/test_save_restore_UB.py::test_list_orientation_runs - AttributeError: 'DataFrame' object has no attribute 'scan_id'
FAILED hkl/tests/test_save_restore_UB.py::test_no_primary_stream - AttributeError: 'DataFrame' object has no attribute 'scan_id'
FAILED hkl/tests/test_save_restore_UB.py::test_missing_energy_key - assert 0 == 1
FAILED hkl/tests/test_save_restore_UB.py::test_restore_orientation - KeyError: 'fourc'
FAILED hkl/tests/test_save_restore_UB.py::test_restore_sample - KeyError: 'fourc'
FAILED hkl/tests/test_util.py::test_issue215 - assert 0 == 1

It's clear that the hkl.util.restore_orientation_info() function needs some serious attention before it can find the information known to be available from a run that was saved before this branch was started.  That's a new problem with databroker v2+.  Reverting the workflow to databroker 1.2.5 and tiled 0.1.0a96.

ALL CI passes.  Next, move the new pins from test settings to packaging requirements.

With databroker 2.0.0b31 (and tiled 0.1.0a110), this line fails with a KeyError: https://github.com/bluesky/hklpy/blob/aa1e0c59bdda8013fc5a50a55fc2aff189686160/hkl/util.py#L348
and that is very suspicious since the key was just offered on the previous line: https://github.com/bluesky/hklpy/blob/aa1e0c59bdda8013fc5a50a55fc2aff189686160/hkl/util.py#L347

An alternative to pinning databroker and tiled is to raise an exception (?ValueError?) in run_orientation_info() when type(run).__name__ != "Catalog" (an intake catalog).

As an upgrade, the configuration could be saved using the newer DiffractometerConfiguration class.  Still, that would not resolve the problem reported in #318 when using run_configuration_info() torecover previously-saved configurations.

Using local command: sphinx-build -M html "source" "build" -v 2>&1 | tee /tmp/log.txt, sphinx complained that the chardet package could not be imported.  Adding that to env-dev.yml next.

Still:
2023-12-23T21:48:26.2424512Z [autodoc] from hkl.configuration import DCConfiguration.canonical_axes
2023-12-23T21:48:26.2427010Z [autodoc] import hkl.configuration => <module 'hkl.configuration' from '/home/runner/work/hklpy/hklpy/hkl/configuration.py'>
2023-12-23T21:48:26.2428908Z [autodoc] getattr(_, 'DCConfiguration')
2023-12-23T21:48:26.2430174Z [autodoc] => <class 'hkl.configuration.DCConfiguration'>
2023-12-23T21:48:26.2431422Z [autodoc] getattr(_, 'canonical_axes')
2023-12-23T21:48:26.2433439Z [app] emitting event: 'build-finished'(TypeError("traceback_exception_init() got an unexpected keyword argument 'max_group_width'"),)

Switch to Py311 for this build

Locally, docs fail 30 times on lines such as these examples:
autodoc: failed to import attribute 'DCConfiguration.canonical_axes' from module 'hkl.configuration'; the following exception was raised:
autodoc: failed to import attribute 'DCConfiguration.constraints' from module 'hkl.configuration'; the following exception was raised:
autodoc: failed to import attribute 'DCConfiguration.energy_keV' from module 'hkl.configuration'; the following exception was raised:
autodoc: failed to import attribute 'DCConfiguration.engine' from module 'hkl.configuration'; the following exception was raised:

All are classes using the @dataclass property.

This SO post is helpful.  When using type annotations and @dataclass property, need to help Sphinx out by being more explicit about how to describe the docs.

Issue in trio repository related to this persistent error.  This is trio 0.19.0.
2023-12-23T22:42:31.9288016Z [autodoc] => <class 'hkl.configuration.DCConfiguration'>
2023-12-23T22:42:31.9289251Z [autodoc] getattr(_, 'geometry')
2023-12-23T22:42:31.9298270Z [app] emitting event: 'build-finished'(TypeError("traceback_exception_init() got an unexpected keyword argument 'max_group_width'"),)
2023-12-23T22:42:31.9300360Z
2023-12-23T22:42:31.9338927Z Error in sys.excepthook:
2023-12-23T22:42:31.9339203Z Traceback (most recent call last):
2023-12-23T22:42:31.9340648Z   File "/home/runner/micromamba/envs/documentation/lib/python3.11/site-packages/dask/base.py", line 71, in wrapper
2023-12-23T22:42:31.9341217Z     return func(exc_type, exc.with_traceback(tb), tb)
2023-12-23T22:42:31.9342102Z            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2023-12-23T22:42:31.9343323Z   File "/home/runner/micromamba/envs/documentation/lib/python3.11/site-packages/trio/_core/_multierror.py", line 447, in trio_excepthook
2023-12-23T22:42:31.9344046Z     for chunk in traceback.format_exception(etype, value, tb):
2023-12-23T22:42:31.9346975Z                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2023-12-23T22:42:31.9348181Z   File "/home/runner/micromamba/envs/documentation/lib/python3.11/traceback.py", line 139, in format_exception
2023-12-23T22:42:31.9348894Z     te = TracebackException(type(value), value, tb, limit=limit, compact=True)
2023-12-23T22:42:31.9351416Z          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2023-12-23T22:42:31.9353171Z   File "/home/runner/micromamba/envs/documentation/lib/python3.11/site-packages/trio/_core/_multierror.py", line 393, in traceback_exception_init

Locally, trio 0.23.2, which is latest release.

@padraic-shafer @mrakitin This is ready now.

@mrakitin @padraic-shafer - Anything else?

Absent additional comments to be addressed, I plan to merge this PR by the end of 2024-01-10.

@padraic-shafer @mrakitin : added the pipefail to the CI -- all tests pass at this time


add coverage configuration to cover interface instead of tests

see https://stackoverflow.com/questions/48505458/coverage-of-cython-module-using-py-test-and-coverage-py for details on the new configuration


added API V3 support to youtube

This requires a valid API Key from google apis console. Slap it in your config
config {
"youtube": { "key" KEY }
}

fine work :+1:

can you make this take the 'google' api key and squash the commits?

merge this sucker in nerd

thanks!

https://www.youtube.com/watch?v=0GidDVaM9xY


Add Subplot support for matplotlib

If a user defines an operation with subplots, only one of the the subplots is shown in the UI, we should add support to subplots from matplotlib.
#1218 is a close related issue.

For rich feature transformation from matplotlib to deepforge graphs, meta-model needs to be updated to incorporate more properties backend(Which needs update) to transfer properties like style and color of the matplotlib.lines.Line2D object. This is logical since we want to replicate the properties from matplotlib as closely as possible.

Closing this issue in favor of #1308 .

#1308 Takes this and tries to implement a new visualizer


questions about CanPotentiallyCoerceTo

what does DateTimeNoTimeZone type mean? I didn't find related data value type
what does Any type mean? It seems non of the types could be coerce to it
will we support Number type to Time type? It looks like Number could be converted to DateTime.
Perhaps a bug here https://github.com/microsoft/Power-Fx/blob/76c3cade7d5a95cd083edabeb9d582e6a84192d9/src/libraries/Microsoft.PowerFx.Interpreter/Marshal/TypeCoercionProvider.cs#L371C9-L371C9
It should be:

if (target == xx)
{
    return xx.AllowedListConvertToXx(source);
}

Check https://github.com/microsoft/Power-Fx/blob/76c3cade7d5a95cd083edabeb9d582e6a84192d9/src/libraries/Microsoft.PowerFx.Interpreter/Marshal/TypeCoercionProvider.cs#L99
One of them must be wrong

Thanks for pointing out the issues.
1: DateTimeNoTimeZone is type that does not use local timezone for datetime.
2: we only can coerce from specific type to the list of types that it allows, we don't allow coerce from one to Any.
3: Number to Time is not supported.
4: We fix it in PR: https://github.com/microsoft/Power-Fx/pull/1656

Fixed in PR https://github.com/microsoft/Power-Fx/pull/1656


Can't get this to work correctly in Windows

Hi, when i run this in windows it just runs and then doesn't have an output. I would like to work on this code, but I am not sure what branch to work on once I fork this?

Hey Guido,
Hmm, odd - no error or anything? Though I haven't tested on Windows, so unclear whether it'd work - there are a few instances in which it isn't doing path joins, but just forward-slashes, which might be pwning win.
Master of this fork is the canonical version. Looking at the network, seems like people are hacking in other stuff ¯\_(ツ)_/¯, though no big changes elsewhere.

I will work on it this week and let you know what I find


Update version for new release

Following https://github.com/WebBluetoothCG/ble-test-peripheral-android/pull/70, here's the patch that needs to be applied to update the app to the Play Store.
R:@g-ortuno

Will push to play store later today.

Thank you @g-ortuno!

It looks like https://play.google.com/store/apps/details?id=io.github.webbluetoothcg.bletestperipheral version is still 7.0.
cc @g-ortuno


kafka io attack: add username and password flags

Signed-off-by: cwen0<EMAIL_ADDRESS>add username and password flags to fix this

Chaosd will access Kafka server to get partitions when to exec io attack. So username, password, host, and port should be supported.
https://github.com/chaos-mesh/chaosd/blob/a9c05406d24511bc692253508950aa93fb9d0394/pkg/server/chaosd/kafka.go#L385-L387

/merge


Feature request: Support for non-Dire Bear Form (level 10-39)

Had someone ping me on Github for this. If anyone wanna implement this it'd be awesome. I don't have gametime currently. Probably wanna use either UnitLevel("player") or IsSpellKnown() and possibly add eventhandling for when someone learns Dire Bear Form mid session.

Can you (or someone else) test the latest build? I don't have a druid in that range and am too lazy to do the 10 levels xD

@ForsakenNGS I confirmed this worked, level 35 bear. I'll try to remember to confirm if the auto update works when learning Dire Bear Form.

I had to reload to once I learned dire bear form.

Should be close enough ;) Closing.


Fix optional fields in Pydantic models

Problem
Pylance is flagging initialization of some Pydantic objects (ie. objects of classes extending BaseModel) as having missing arguments when optional arguments are not provided. Although the code still runs as it should, this type of error is a potential source of frustration for VS Code users.
Example
For example, according to the doc string for the GoogleGenerativeAIEmbeddings class, it can be used in the following way:
from langchain_google_genai import GoogleGenerativeAIEmbeddings

embeddings = GoogleGenerativeAIEmbeddings(model="models/embedding-001")
embeddings.embed_query("What's our Q1 revenue?")

When editing the same code in Visual Studio Code with the Pylance extension enabled, following error is encountered.

In this case, the parameters task_type, google_api_key, client_options, transport, and request_options are clearly optional, as indicated by the None type. client does not have the None type, but is also optional since it is not provided in the example code snippet.
Note that Pylance does not flag the absence of the credentials field, even though it is also optional, and that the only field with a recognized default value (= None) is credentials.
Causes
Upon closer examination of the code, it becomes evident that some definitions for Pydantic fields are not handled by Pylance as intended. Examining the definition of GoogleGenerativeAIEmbeddings from the previous example (some methods, field descriptions and doc string for class are redacted for the sake of brevity):
class GoogleGenerativeAIEmbeddings(BaseModel, Embeddings):
    # <doc string>

    client: Any  #: :meta private:
    model: str = Field(
        ...,
        description="...",
    )
    task_type: Optional[str] = Field(
        None,
        description="...",
    )
    google_api_key: Optional[SecretStr] = Field(
        None,
        description="...",
    )
    credentials: Any = Field(
        default=None,  # <- notice the default keyword
        exclude=True,
        description="...",
    )
    client_options: Optional[Dict] = Field(
        None,
        description="...",
    )
    transport: Optional[str] = Field(
        None,
        description="...",
    )
    request_options: Optional[Dict] = Field(
        None,
        description="...",
    )

    @root_validator()
    def validate_environment(cls, values: Dict) -> Dict:
        """Validates params and passes them to google-generativeai package."""
        google_api_key = get_from_dict_or_env(
            values, "google_api_key", "GOOGLE_API_KEY"
        )
        client_info = get_client_info("GoogleGenerativeAIEmbeddings")

        values["client"] = build_generative_service(
            credentials=values.get("credentials"),
            api_key=google_api_key,
            client_info=client_info,
            client_options=values.get("client_options"),
        )
        return values

    # <other methods>

we can see that except for client and model all other fields are given a default value by Field. However, the only default value recognized by Pylance is the one for credentials. And it is no coincidence that credentials is also the only field where the default value is defined using the default keyword argument.
It is safe to say that the errors related to task_type, google_api_key, client_options, transport, and request_options are caused by the default value for them not being provided with the keyword arguments. (Unfortunately, I am not sure why this is the case.)
For the client case, we can assume that it's default value is None, since it's set within the validate_environment method. This case is not explicitly declared, which makes Pylance angry.
TL;DR
The problem seems to be caused by two different cases:

The default value for an optional field is not provided (such as client in GoogleGenerativeAIEmbeddings).
The default value for an optional field is provided without the default keyword using Field.

Solution
Find all the field definitions that are causing problems and fix them.
To find the examples for the first case, I searched for field definitions of type Any without a default value, similar to client in GoogleGenerativeAIEmbeddings. For the second case, I searched for optional fields using the Optional[.*] = Field( regex and manually checked for definitions without the default keyword.
It was trivial to apply the fix after finding the faulty lines.

@orkhank thanks for your contribution! could fix the remaining linter issues, please?


test: ante tests

Description
Adds tests for our custom ante handler

Author Checklist
All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.
I have...

[ ] included the correct type prefix in the PR title
[ ] added appropriate labels to the PR
[ ] added ! to the type prefix if API or client breaking change
[ ] targeted the correct branch (see PR Targeting)
[ ] provided a link to the relevant issue or specification
[ ] added a changelog entry to CHANGELOG.md
[ ] included comments for documenting Go code
[ ] updated the relevant documentation or specification
[ ] reviewed "Files changed" and left comments if necessary
[ ] confirmed all CI checks have passed

Reviewers Checklist
All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.
I have...

[ ] confirmed the correct type prefix in the PR title
[ ] confirmed ! in the type prefix if API or client breaking change
[ ] confirmed all author checklist items have been addressed
[ ] reviewed state machine logic
[ ] reviewed API design and naming
[ ] reviewed documentation is accurate
[ ] reviewed tests and test coverage
[ ] manually tested (if applicable)

Codecov Report

Merging #337 (1d50e18) into main (2e75689) will increase coverage by 0.18%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #337      +/-   ##
==========================================
+ Coverage   32.06%   32.25%   +0.18%
==========================================
  Files          74       77       +3
  Lines        9919    10066     +147
==========================================
+ Hits         3181     3247      +66
- Misses       6445     6515      +70
- Partials      293      304      +11

Impacted Files
Coverage Δ

ante/spam_prevention.go
66.17% <ø> (ø)

ante/fee.go
4.44% <0.00%> (ø)

ante/ante.go
55.88% <0.00%> (ø)


test(client): fix the name conflict in create tag and order in list tags

Pull Request Test Coverage Report for Build 905073671

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.42%

Totals

Change from base Build 905050750:
0.0%

Covered Lines:
4379

Relevant Lines:
5313

💛  - Coveralls


[FEATURE] Styling improvement

Styling of the list itself can be improved. It's very basic as of right now. Can I be assigned this for HacktoberFest 2022?

Styling of the list itself can be improved. It's very basic as of right now. Can I be assigned this for HacktoberFest 2022?

Good Luck 👍🏻
Here is a design from which you can take idea:

I've made a PR for the enhancement of this.

I've made a PR for the enhancement of this.

You have made a seperate grid for this but I want it intside the company swag card.

Oh I thought it was supposed to be a filter-by-tag implementation. So I've added it at the top. Can do the separate one, but will that count as spam if I made a PR of that?


Nitant-DG find sequence

Feature implementation explained in Developer Guide.
UML Sequence Diagram rendered.

Codecov Report

Merging #84 (179bb13) into master (6785dcd) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #84   +/-   ##
=========================================
  Coverage     59.22%   59.22%
  Complexity      547      547
=========================================
  Files            95       95
  Lines          2391     2391
  Branches        336      336
=========================================
  Hits           1416     1416
  Misses          759      759
  Partials        216      216

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


recipient related discussion labels are not shown

If I load the forum from a discussion page and then navigate to the index, the private discussion icons and member lists are not shown. If I load the forum on a PD discussion and navigate to the index, only this discussion has icon and member list
The other PDs are displayed as normal discussions

duplicate of #7 but the issue is that if you come from a non pd discussion, the labels are not shown, if you do they are.


Migrate sensor functions

Most of our sensor functions have already been migrated by myself and @BruceTee23 -- we still have one to migrate!

Working on it

awesome -- thanks!


Ambiguity/No Examples on docs re S3 on Google Storage and lack of support for workflow identity

I'm using Moon on GKE (Helm install) and want to upload video from the tests onto GS. However, the docs (https://aerokube.com/moon/latest/#s3) are vague about what I need to configure for Google Storage.
I have a Google Storage bucket created in my account, and configured the service.json as described (displayed via Helm):
  service.json: |
    {
      "kernelCaps": ["SYS_ADMIN"],
      "s3": {
        "endpoint": "https://storage.googleapis.com",
        "bucketName": "my-moon-bucket",
        "version": "S3v2",
        "keyPattern": "$sessionId"
      }
    }

But when attempting to upload the logs or video, I get this:
mc: <ERROR> Unable to write to one or more targets. Insufficient permissions to access this file `https://storage.googleapis.com/my-moon-bucket/chrome-89-0-61f0e62a-10b1-445f-8a36-40a8876e9492/session.log`.

This may be because the default service account used by the cluster doesn't have access to storage (which is intentional)
This leads me to the next question. What if I have a credentials.json file used by GCP service accounts and want to use that? (This would likely be the method if you were running in a non-google cluster and wanted to use GS and not S3)
Or, what we use Workflow Identity which requires us to use a specific Kubernetes service account? I don't see a way to (easily) specify which service account to use on the browser pods?
Happy to test or provide more information if needed.

Okay, figured out the setup.
Going through the minio site, this page pointed me to this page, which then let me figure out how to create an access/secret key which I then use in the config, without needing a credentials json.
Might be worthwhile to put this on the docs or make them clearer

@huang-jy stuff related to service account is described here: https://aerokube.com/moon/latest/#service-account

@huang-jy stuff related to service account is described here: https://aerokube.com/moon/latest/#service-account

That would work for installations where you're installing directly into the cluster, but if I'm installing via Helm I can't do that unless I extract and patch the chart, then install from that?

Let's then add service account support to chart.

Thanks very much :)

@huang-jy btw, here is the definition of our service account in chart: https://github.com/aerokube/charts/blob/master/moon/templates/moon.yaml#L2-L42 Probably it would be simpler to add permissions to this one.

Is it okay if try to patch and make a PR?

@huang-jy you could, but let's discuss first suggested changes. You could send an example here first.

Perfect. I will work on my changes, then post them here before raising a PR

Here are my changes.
For workflow identity to work, the service account must be tagged with a specific annotation:
<EMAIL_ADDRESS>
So if the GCP service account is "moon-sa" in project "test-project", the annotation would be
<EMAIL_ADDRESS>
The GCP sa also requires configuring to indicate which Kubernetes service account to expect, but that's not in scope for this change.
The change I propose is simple: allow the user to optionally add annotations to the serviceaccount created by the Helm install:
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: {{ .Release.Name }}
  namespace: {{ .Release.Namespace }}
  {{- if .Values.moon.serviceaccount.annotations }}
  annotations:
  {{- range $key, $value := .Values.moon.service.annotations }}
    {{ $key }}: {{ $value | quote }}
  {{- end }}
  {{- end }}

Then in values.yaml:
moon:

  ....

  serviceaccount:
    annotations: {}

  ....

Users can override the values.yaml in the usual way
moon:

  ....

  serviceaccount:
    annotations:
<EMAIL_ADDRESS>
  ....

And verify it shows up on the service account itself:
$ kubectl get serviceaccount -n moon moon -o yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    iam.gke.io/gcp-service-account<EMAIL_ADDRESS>
    meta.helm.sh/release-name: moon
    meta.helm.sh/release-namespace: moon

It can also be tested using gcloud builders:
(Using no annotation)
$ kubectl run -n moon --rm --serviceaccount=moon -it test --image gcr.io/cloud-builders/gsutil ls
kubectl run --generator=deployment/apps.v1 is DEPRECATED and will be removed in a future version. Use kubectl run --generator=run-pod/v1 or kubectl create instead.
If you don't see a command prompt, try pressing enter.
AccessDeniedException: 403 Caller does not have storage.buckets.list access to the Google Cloud project.
Session ended, resume using 'kubectl attach test-5b87dbc985-dhnjw -c test -i -t' command when the pod is running
deployment.apps "test" deleted

(Using an annotation)
$ kubectl run -n moon --rm --serviceaccount=moon -it test --image gcr.io/cloud-builders/gsutil ls
kubectl run --generator=deployment/apps.v1 is DEPRECATED and will be removed in a future version. Use kubectl run --generator=run-pod/v1 or kubectl create instead.
If you don't see a command prompt, try pressing enter.
gs://bf-moon-assets/
gs://backups/
gs://wp-assets/
gs://wp-backups
Session ended, resume using 'kubectl attach test-5b87dbc985-kgggm -c test -i -t' command when the pod is running
deployment.apps "test" deleted

@huang-jy please go ahead and create a PR. Don't forget to add a comment on top of your key in values.yaml.

PR raised https://github.com/aerokube/charts/pull/50
One note: The current chart version available on the helm repo is 1.1.4, but the Chart.yaml in the git repo shows 1.0.7, I bumped the version to 1.1.5 for this change. If that is wrong, let me know and I'll put it down to 1.0.8

@huang-jy see my comments in your PR.

Thanks @vania-pooh I've made the changes requested

@huang-jy merged.

@huang-jy tagged as https://github.com/aerokube/charts/releases/tag/1.1.5.

Thank you very much. I will close this issue


Fix exception related with the action type definition on PostgreSql.

The raised exception is:
 UniqueViolation('duplicate key value violates unique constraint "pg_type_typname_nsp_index"\nDETAIL:  Key (typname, typnamespace)=(producer_queue_id_seq, 2200) already exists.\n')

Closing this issue as the correct repo is https://github.com/Clariteia/minos_microservice_networks and there is already an issue there: https://github.com/Clariteia/minos_microservice_networks/issues/229


default_device no longer sets to overridden default_device method

Importing the fastai_xla_extensions.core module overrides the fastai.torch_core.default_device but
the next line importing from fastai.vision.all import * still uses the old fastai.torch_core.default_device for some reason.
This wasn't the behavior in the past but something changed recently.

No longer requires setting of default_device in latest version (0.04)


Player left after 5-10 seconds with no input...

After 5 seconds Player left, no heartbeat work :-( How can I fix this?
This project is very cool, I would like to use in 3D Project :-)

I'm not sure if you were using the accompanying server project or not, but I noticed in its codebase that the heartbeat rate was at 10 seconds, while in the client code it was only sending the heartbeat every 30 seconds. This meant that if the player did not do any actions (movement), the server would never receive any messages and then kick that player for inactivity.
I've updated the server project to have a longer timeout rate, but you can also adjust the heartbeat setting in the client project to send more often.
I hope this helps solve your issue.

Thank you for your note. Yes, I am using python server project. Do you think is possible tu use it in 3D VR worlds ?


Add account autocomplete input for admin configuration

Admins can visit the admin page
When you enter the account ID, we should have the suggestion roll, for better UX

Instances to check

[x]  Devhub proposals
[x]  Infrastructure committee
[ ]  Events committee

@Megha-Dev-19 Is this ticket not complete?


hints and dist regeneration

Since master is protected and requires two reviews to push, there seems to be only two solutions to merge hints and dist:
-use a bot with admin permissions on the repo to override the protection
-automatically generate and manually merge PRs
This implements the second solution, and updates hints and dist weekly instead of daily to reduce the inconvenience.
Following the suggestion from @polubelova I also added a check to avoid trivial updates.

Can you confirm somewhere in the build someone runs rm -rf dist// ? This is the important bit in case some change results in a file being deleted

@msprotz this is done in the Nix build


Rebooting on switch power off

I've been messing around with an NSPanel on my entryway but only for the use of widgets through mqtt, now I placed another one in the bathroom where I'm using the 2 line outputs: one for the main lights and the other for extractor fan.
Randomly (but very often) when I turn off a switch the device reboots itself. I tried with 11.0.5 and 11.0.03 versions, same behaviour. Very strange it may have something to do with my wiring?

Well it keeps happening... randomly when I turn on or off one of the two relays it reboots itself...

{"Time":"2022-04-06T08:23:35","Uptime":"0T00:04:59","UptimeSec":299,"Heap":165,"SleepMode":"Dynamic","Sleep":50,"LoadAvg":40,"MqttCount":1,"Berry":{"HeapUsed":19,"Objects":396},"POWER1":"ON","POWER2":"OFF","Wifi":{"AP":1,"SSId":"Apple Network","BSSId":"58:EF:68:6D:57:77","Channel":5,"Mode":"11n","RSSI":100,"Signal":-50,"LinkCount":1,"Downtime":"0T00:00:04"}}

Hey,
this looks more like an hardware issue than something releated to tasmota or the berry driver, get in touch with sonoff and ask for a replacement.

I thought of that so I swapped the screens with my other nspanel and the config too. Same problem. I'll test swapping the back panel too it may be something wrong with the power unit

Si I've switched the power back plates to and got the exact same behavior... I'm guessing not a hardware issue

The only log that stands out is:
22:19:01.806 MQT: tele/nspanel2/RESULT = {"NSPanel":{"error":2}}


first_setup.py: ask for the admin user's full name

Hey @christianp ,
Can you please describe the issue. I would like to work on it.

#721 is a duplicate of this, and is resolved.


[homestead] vagrant box 0.5.0 will not finish provisioning: invalid network interface

Vagrant informed me of an upgrade to the homestead box, version 0.5.0, but when I try to use this version, I get the following error:
==> default: Configuring and enabling network interfaces...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

/sbin/ifdown eth1 2> /dev/null

Stdout from the command:

Stderr from the command:

(no output shown)
I was able to ssh into the box (using vagrant as the default password, since the ssh key was not yet transmitted), and discovered the names of the network interfaces have changed:
vagrant@homestead:~$ ifconfig -a
enp0s3    Link encap:Ethernet  HWaddr 08:00:27:46:f3:a1
          inet addr:<IP_ADDRESS>  Bcast:<IP_ADDRESS>  Mask:<IP_ADDRESS>
          inet6 addr: fe80::a00:27ff:fe46:f3a1/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:487 errors:0 dropped:0 overruns:0 frame:0
          TX packets:305 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:57159 (57.1 KB)  TX bytes:46276 (46.2 KB)

enp0s8    Link encap:Ethernet  HWaddr 08:00:27:bb:88:05
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

I have never seen this before, but it looks like it's a result of Ubuntu 16.04 using systemd which implemented this: https://www.freedesktop.org/wiki/Software/systemd/PredictableNetworkInterfaceNames/
There are various techniques to disable this behaviour, but probably the scripts should just be updated since this seems to be the way of the future.

Thanks, but we only process laravel/framework issues here.

Where do you process homestead issues, then?  This is the only open issue tracker in the laravel project.

I'd also like to know where we can report issues with Homestead.

If anyone else encounters this issue, /u/utotwel on Reddit claims that installing vagrant 1.8.4 (instead of the 1.8.1 package that comes with Ubuntu) solves the problem.  It's not an ideal solution, since the vagrant package is extremely poor and puts everything in the wrong place, but it's a nice work-around!  Hopefully the Debian/Ubuntu-maintained package will be updated soon.

If installing vagrant 1.8.4 is not an option... what can I do?

@ndlbass The easiest way is to simply stick with Homestead 0.4.4.  Just set version = "0.4.4" in your Homestead.yaml
I got it working on 0.5.0 by logging into the running VM through the VirtualBox console (after provisioning failed), adding the net.ifnames=0 kernel parameter to /etc/default/grub, update-grub, then running vagrant reload --provision. I think I also had to fiddle with the device names in /etc/network/interfaces a bit to make everything work right.  Not sure exactly what I did, but now it's working fine.

If anyone wants to know about how to get rid of the 0.5.0 version:
vagrant box remove laravel/homestead --provider virtualbox --box-version 0.5.0

Thanks @d3rd4v1d. It works!

Thanks @d3rd4v1d , you save my life 👍


SS3.2: Bug in Locale menu

Fatal error: Call to a member function Link() on a non-object in /vagrant/www/fluent/code/extensions/FluentExtension.php on line 320
Somehow
DataObject::get($class)->byID($id)->Link();
crashes, when re-publishing the page it works. Dunno why.
when debugging i see that
Page::get()->byID(3) => null
Page::get()->filter('ID', 3) => DataList....
Maybe related to https://github.com/silverstripe/silverstripe-framework/issues/4700  and hopefully resolved in 3.2.1 ?

Ah, maybe. In which case, have you tested it with 3.2 dev branch?

not yet, just with the 3.2.0 release

I think it is possibly fixed.
I recently added full tests for 3.2 branch recently so it should be working.

Fixed?

No idea... maybe @wernerkrauss could confirm?


ERROR Sensor DHT Adafruit-DHT to 1.3.4 on 0.78.0b0 (beta)

Home Assistant release with the issue:

0.78.0b0
Last working Home Assistant release (if known):
NO
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io
Component/platform:

DHT Sensor
Description of problem:
error install DHT  sensor Adafruit-DHT to 1.3.4
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
sensor:
  - platform: dht
    sensor: DHT11
    pin: 24
    monitored_conditions:
      - temperature
      - humidity

Traceback (if applicable):
2018-09-11 18:46:35 ERROR (SyncWorker_17) [homeassistant.util.package] Unable to install package Adafruit-DHT==1.3.4: Failed building wheel for Adafruit-DHT
wirelesstagpy 0.3.0 has requirement colorlog==3.0.1, but you'll have colorlog 3.1.4 which is incompatible.
waterfurnace 0.7.0 has requirement websocket-client>=0.47, but you'll have websocket-client 0.37.0 which is incompatible.
upsmychoice 1.0.6 has requirement beautifulsoup4==4.5.1, but you'll have beautifulsoup4 4.6.3 which is incompatible.
upsmychoice 1.0.6 has requirement python-dateutil==2.6.0, but you'll have python-dateutil 2.7.3 which is incompatible.
upsmychoice 1.0.6 has requirement requests==2.12.4, but you'll have requests 2.19.1 which is incompatible.
toonlib 1.0.2 has requirement cachetools==2.0.0, but you'll have cachetools 2.0.1 which is incompatible.
toonlib 1.0.2 has requirement requests==2.13.0, but you'll have requests 2.19.1 which is incompatible.
temperusb 1.5.3 has requirement pyusb>=1.0.0rc1, but you'll have pyusb 1.0.0b1 which is incompatible.
spotcrime 1.0.3 has requirement requests==2.12.4, but you'll have requests 2.19.1 which is incompatible.
skybellpy 0.1.2 has requirement colorlog==3.0.1, but you'll have colorlog 3.1.4 which is incompatible.
python-velbus 2.0.19 has requirement pyserial==3.3, but you'll have pyserial 3.1.1 which is incompatible.
python-jose-cryptodome 1.3.2 has requirement pycryptodome<3.4.0,>=3.3.1, but you'll have pycryptodome 3.6.6 which is incompatible.
pysma 0.2.0 has requirement aiohttp<3,>2, but you'll have aiohttp 3.4.4 which is incompatible.
pysma 0.2.0 has requirement async-timeout<3,>2, but you'll have async-timeout 3.0.0 which is incompatible.
pymysensors 0.17.0 has requirement pyserial>=3.4, but you'll have pyserial 3.1.1 which is incompatible.
pymonoprice 0.3 has requirement pyserial>=3.4, but you'll have pyserial 3.1.1 which is incompatible.
pymata 2.14 has requirement pyserial==2.7, but you'll have pyserial 3.1.1 which is incompatible.
pyicloud 0.9.1 has requirement keyring<9.0,>=8.0, but you'll have keyring 15.0.0 which is incompatible.
pyicloud 0.9.1 has requirement keyrings.alt<2.0,>=1.0, but you'll have keyrings-alt 3.1 which is incompatible.
pyblackbird 0.5 has requirement pyserial>=3.4, but you'll have pyserial 3.1.1 which is incompatible.
nad-receiver 0.0.9 has requirement pyserial==3.2.1, but you'll have pyserial 3.1.1 which is incompatible.
myusps 1.3.2 has requirement beautifulsoup4==4.6.0, but you'll have beautifulsoup4 4.6.3 which is incompatible.
myusps 1.3.2 has requirement python-dateutil==2.6.0, but you'll have python-dateutil 2.7.3 which is incompatible.
myusps 1.3.2 has requirement requests==2.12.4, but you'll have requests 2.19.1 which is incompatible.
myusps 1.3.2 has requirement selenium==2.53.6, but you'll have selenium 3.14.0 which is incompatible.
mycroftapi 2.0 has requirement websocket-client==0.44.0, but you'll have websocket-client 0.37.0 which is incompatible.
motorparts 1.0.2 has requirement beautifulsoup4==4.5.1, but you'll have beautifulsoup4 4.6.3 which is incompatible.
motorparts 1.0.2 has requirement requests==2.12.4, but you'll have requests 2.19.1 which is incompatible.
magicseaweed 1.0.0 has requirement requests==2.12.4, but you'll have requests 2.19.1 which is incompatible.
locationsharinglib 2.0.11 has requirement beautifulsoup4==4.6.0, but you'll have beautifulsoup4 4.6.3 which is incompatible.
libsoundtouch 0.7.2 has requirement websocket-client>=0.40.0, but you'll have websocket-client 0.37.0 which is incompatible.
insteonplm 0.13.1 has requirement pyserial==3.2.0, but you'll have pyserial 3.1.1 which is incompatible.
hipnotify 1.0.8 has requirement requests==2.9.1, but you'll have requests 2.19.1 which is incompatible.
gearbest-parser 1.0.7 has requirement beautifulsoup4==4.6.0, but you'll have beautifulsoup4 4.6.3 which is incompatible.
fedexdeliverymanager 1.0.6 has requirement beautifulsoup4==4.5.1, but you'll have beautifulsoup4 4.6.3 which is incompatible.
fedexdeliverymanager 1.0.6 has requirement python-dateutil==2.6.0, but you'll have python-dateutil 2.7.3 which is incompatible.
discord-py 0.16.12 has requirement aiohttp<1.1.0,>=1.0.0, but you'll have aiohttp 3.4.4 which is incompatible.
crimereports 1.0.0 has requirement requests==2.12.4, but you'll have requests 2.19.1 which is incompatible.
broadlink 0.9 has requirement pycryptodome==3.4.11, but you'll have pycryptodome 3.6.6 which is incompatible.
alarmdecoder 1.13.2 has requirement pyserial==2.7, but you'll have pyserial 3.1.1 which is incompatible.
abodepy 0.13.1 has requirement colorlog==3.0.1, but you'll have colorlog 3.1.4 which is incompatible.
Command "/usr/local/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-vmmkqee6/Adafruit-DHT/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-3d573dmv/install-record.txt --single-version-externally-managed --prefix  --compile --user --prefix=" failed with error code 1 in /tmp/pip-install-vmmkqee6/Adafruit-DHT/
You are using pip version 10.0.1, however version 18.0 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
2018-09-11 18:46:35 ERROR (MainThread) [homeassistant.requirements] Not initializing sensor.dht because could not install requirement Adafruit-DHT==1.3.4
2018-09-11 18:46:35 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform sensor.dht: Could not install all requirements.

the same for me:
Home Assistant release with the issue:
0.78
Last working Home Assistant release (if known):
0.77.2
Operating environment (Hass.io/Docker/Windows/etc.):
Hass.io on ArchLinuxARM
Component/platform:
DHT Sensor
Description of problem:
error install Adafruit-DHT-1.3.4
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
sensor:
  - platform: yr
  - platform: dht
    sensor: DHT22
    pin: 25
    monitored_conditions:
      - temperature
      - humidity

Traceback (if applicable):
Command "/usr/local/bin/python3 -u -c "import setuptools, tokenize;__file__='/tmp/pip-install-qtv2bp7c/Adafruit-DHT/setup.py';f=getattr(tokenize, 'open', open)(__file__);code=f.read().replace('\r\n', '\n');f.close();exec(compile(code, __file__, 'exec'))" install --record /tmp/pip-record-xtybvo3n/install-record.txt --single-version-externally-managed --prefix  --compile --user --prefix=" failed with error code 1 in /tmp/pip-install-qtv2bp7c/Adafruit-DHT/
You are using pip version 10.0.1, however version 18.0 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
2018-09-18 11:49:36 ERROR (MainThread) [homeassistant.requirements] Not initializing sensor.dht because could not install requirement Adafruit-DHT==1.3.4
2018-09-18 11:49:36 ERROR (MainThread) [homeassistant.setup] Unable to prepare setup for platform sensor.dht: Could not install all requirements.

me too

Will most likely be fixed with https://github.com/home-assistant/hassio-homeassistant/pull/12

@fabaff
is from July that the sensor on hassio does not work and every update worse was the ra they did!

I have the same problem. Created an incident as the search did not show any results for sensor.dht. Closed  #16722 and follow this one. Will check the suggestion of fabaff.

with the update to 0.78.1, dht is working again
thx

@vitalogy su hassio ancora no

but...

My sensor.DHT is working again!

Yes, the update fixed the DHT.sensor. Thank you!


Made multi-version libraries and models possible

It's hard to tell based on the description, but will this PR fix #438 as well?  Or is it a different thing?

Bryn and I have been discussing this a bit offline and we don't feel this is the correct approach.


fix: not addressing to Sets and Maps as object without keys

Summary
Fixes https://github.com/jestjs/jest/issues/14599
The problem is that comparing list of nulls with Set or list of Sets:
expect([null]).toMatchObject([new Set()]);
expect([null]).toMatchObject(new Set());

In both cases the comparison does not throw an exception.

Update:
Same issue is happening with Map instead of set, I have fixed it too
expect([null]).toMatchObject([new Map()]);
expect([null]).toMatchObject(new Map());

Test plan
Unit tests added
Both cases described in the Summery have been tested locally with the fix and reproduced without the fix

@SimenB Hey, I see one of the tests failed after the squash - is there an option to rerun it only? 🙌


add kotaeta.com

I want to add a machine-translated Japanese site to the supported sites, https://kotaeta.com/ .

Thank you!


Question / issue with artifact copying between containers

This is just a question / an issue that we have noticed and not sure how to resolve but based on comments here should be resolvable for argo 2.3.0.
We have basically standard workflows with steps in them where the init container pulls data from S3, the main container processes them and then the wait container uploads the results back to S3.
As our artifacts can be pretty large (as in several hundred GB in one step), copying the data back from the main container to the wait one takes forever due to the docker cp | gzip process.
We know that PNS should help, but we are also putting all the output artifacts in an emptyDir volume mount, which we expected the wait container can just use without the need to copy (as suggested in issue 1203).
When we look inside the init container (e.g. with df) it does not show up but with df -a it does. So not sure why this would not work and avoid the docker cp issue....
Any help would be appreciated.
Michael.

Could you use a PVC claim?


New package: XDiagJll v0.2.0

Registering package: XDiagJll
Repository: https://github.com/awietek/XDiag_jll.jl
Created by: @awietek
Version: v0.2.0
Commit: 58853350e0e69d2a6747723f653b01b0c1fc68c6
Reviewed by: @awietek
Reference: https://github.com/awietek/XDiag_jll.jl/issues/4

Please see https://github.com/JuliaRegistries/General/pull/112731#issuecomment-2277591196
Unfortunately, I have no experience with JLL packages, but please seek help in the Discourse or Slack on how to do this, before further trying to register.


VESPA-16236: Adding endpoint as a dimension to handled.requests and handled.latency

I confirm that this contribution is made under the terms of the license found in the root directory of this repository's source tree and that I have the authority necessary to make this contribution on behalf of its copyright owner.
@yngveaasheim Not sure if it really makes any sense to include endpoint as a dimension to handled.latency
@arnej27959

@bjormel Yes, we should be the same set of tags for handled.requests and handled.latency to be able to correlate changes in either.


Parse Ssl client hello

Doneness:

[X] Build is okay - I made sure that this change is building successfully.
[X] No Bugs - I made sure that this change is working properly as expected. It doesn't have any bugs that you are aware of.
[X] Branching - If this is not a hotfix, I am making this request against develop branch

:white_check_mark: Build Titanium-Web-Proxy 3.0.42 completed (commit https://github.com/justcoding121/Titanium-Web-Proxy/commit/5f2737629c by @honfika)


github automated testing is failing on pull requests

i believe this is primarily due to the removal of the mws-related repos (as they were part of the required tests).

this issue is no longer relevant to github testing. closing.


add debug context

debug context added for "inline" suggestion, will be triggered for alpha capability only

wouldn't it work only for the old api? we're all working with the proposed api internally

yes, it is only relevant for the "old" api, the proposed api is only enabled if the "advanced completions" capability is enabled


Ramda named imports not working as expected on Node project with ES Modules enabled

Hi friends! I have been publishing some vanilla Node packages with Ramda as a dependency. I'm really excited about ES Modules and have set the "type": "module" flag for these projects (Node 13.2+), but using libraries like ESM and Pika to make them backwards-compatible. I keep getting stumped by an error when I import named Ramda functions without fancy bundling (Webpack). Full repo here, but TL;DR:
// index.js
import {
  anyPass,
  both,
  complement,
  compose,
  constructN,
  curry,
  is,
  ifElse,
  invoker,
  map,
  propEq,
  when,
  type
} from 'ramda';

// Console
node . // 13.2 and 14 give the same error
file:///{path to project}/src/index.js:9
  is,
  ^^
SyntaxError: The requested module 'ramda' does not provide an export named 'is'
    at ModuleJob._instantiate (internal/modules/esm/module_job.js:92:21)
    at async ModuleJob.run (internal/modules/esm/module_job.js:107:20)
    at async Loader.import (internal/modules/esm/loader.js:179:24)

Ironically, when I tweak the statement to import R from 'ramda'; const { ... } = R;, I have no problems running it locally. (It seems weird that this even works in "type": "module" mode given there is no default export from node_modules/ramda/es/index.js that I can see in the source code.)
However, when I publish the package and use it in a Webpack-configured project (my NPM package has the "module" flag set to the ES Module file), I am given the error Attempted import error: 'ramda' does not contain a default export (imported as 'R').
I would think that import { func1, func2, func3 } from 'ramda' is the correct way to import in both scenarios, but it doesn't seem to be the case. Any thoughts why this is happening?

I always ping @Andarist when these things come up, because he knows much more than I do about the bundling.
@Andarist, do  you have thoughts on this and/or time to investigate?

I think this has been fixed by https://github.com/ramda/ramda/pull/2999 , but it has not yet been published.

Oh nice! Looks very familiar 😆 the export and module sections looked correct FWIW!

Any ETA on the release? My fix for this problem is causing issues with another library. 😢

Not yet.  But I'll see if we can publish something soon.

#2999 had fixed the original issue in my case with v.0.27.1, but it seems the problem really isn't resolved under the hood. I've got a version of the issue now where my app requires a package that depends on ramda. My app bundles with webpack/babel, and requests the 'module' version of my package.
Since I rely on babel-plugin-ramda, I just import R from 'ramda'. In my package, this causes the error Attempted import error: 'ramda' does not contain a default export (imported as 'R'), even though the very same line doesn't cause an issue in my app (since #2999).
Here's what my package.json looks like in the package. I don't know which field webpack looks at, but it's one of the index.module.js ones...
{
  "main": "./dist/index.js",
  "jsnext:main": "./dist/index.modern.js",
  "module": "./dist/index.module.js",
  "syntax": {
    "esmodules": "./dist/index.modern.js"
  },
  "exports": {
    ".": {
      "browser": "./dist/index.module.js",
      "import": "./dist/index.module.js",
      "require": "./dist/index.js"
    }
  },
}

I hope this adds a bit of context to the issue...

import R from 'ramda'

I believe this has been deprecated a quite long time ago already. ramda has no default export fo the error you are seeing is perfectly valid. Please check with import * as R from 'ramda'

Thanks. That works. Now that you mention it, I suspect * as R replaces the need for the babel plugin with a bundler's normal tree shaking.

Yes - when using treeshakers there shouldnt a need for this Babel plugin with the newest version of Ramda. When I've converted the codebase to ES modules I've validated this against both webpack and Rollup and they did a great job at tree-shaking Ramda out of the box back then.


Just a quick thanks!

This isn't an issue, I just wanted to let you know that I've been searching a long time for the right terminal integration for Atom and this one seems to be the one I've been waiting for! I've tried several before and there was always something that kept me from continuing to use them, so I thought I'd pop in here to quickly say thanks for finally making one that actual works like the regular Terminal app!

I appreciate the compliment, it means a lot. Thank you for using my package. I'm glad you like it.


prompts from file different behavior than prompts from config

Loading prompts from a file asks them off the model all at once (even when using separator).
Loading prompts as listed out in the config file asks them individually.
The first gives short responses, the second gives the full response. I prefer the full response.
I believe I can get the same results by loading each prompt in a separate file - but I'd prefer to just load them via file and have them all asked separately. (Unless I'm missing something).
Thanks.

Hey @aisonym, I don't fully understand.  Can you give an example of the difference in output?

Thanks for your response. New to promptfoo.
What I thought was two distinct issues is maybe just one (or I'm not fully understanding).
Described here in more detail - I believe it's related to put a label on a set of prompts instead of this being an issue of loading prompts in a file vs. in the config file.

FWIW - I think fine to close this item.


releaseKey=461808

The application was not able to determine the exact version you have.

This is .NET Framework 4.7.2 on Windows 10 April 2018 Update only.

See also: How to: Determine which .NET Framework versions are installed


Could use a name other than "blog_os"

How about "rustix"? :)

Thanks for the suggestion! However, there are already a few projects named "rustix": https://github.com/search?q=rustix&type=Repositories
Also, naming is hard. Maybe the name "blog_os" isn't the most creative one, but I think it describes the essence of the project quite well: It is the byproduct from the "Writing an OS in Rust" blog with a focus in teaching (in contrast to a stand-alone project with a different focus). Further, the name is established at this point, so renaming it would only cause unnecessary confusion.
So I think I'll stick with "blog_os", at least for now :).


ModelState serialization is inconsistent with validation attributes

When serializing Controller.ModelState to  JSON, the casing of the fields are inconsistent. I am not sure why but there are a few key things I figure that makes the difference.
Repro Steps

Also available here.

project.json file:
{
  "version": "1.0.0-*",
  "buildOptions": {
    "debugType": "portable",
    "emitEntryPoint": true
  },
  "dependencies": {
    "Microsoft.AspNetCore.Mvc": "1.0.0",
    "Microsoft.AspNetCore.Server.Kestrel": "1.0.0"
  },
  "frameworks": {
    "netcoreapp1.0": {
      "dependencies": {
        "Microsoft.NETCore.App": {
          "type": "platform",
          "version": "1.0.0"
        }
      },
      "imports": "dnxcore50"
    }
  }
}

Program.cs file:
using System.ComponentModel.DataAnnotations;
using Microsoft.AspNetCore.Builder;
using Microsoft.AspNetCore.Hosting;
using Microsoft.AspNetCore.Mvc;
using Microsoft.Extensions.DependencyInjection;

namespace ConsoleApplication
{
    public class PaginatedRequestCommand
    {
        [Range(0, int.MaxValue)]
        public int Skip { get; set; }

        [Range(1, 50)]
        public int Take { get; set; }
    }

    public class ValuesController : Controller
    {
        [HttpGet("values")]
        public IActionResult Get(int skip, int take)
        {
            var requestCommand = new PaginatedRequestCommand
            {
                Skip = skip, Take = take
            };

            return TryValidateModel(requestCommand) ?
                Ok(new [] { "value1", "value2" }) :
                BadRequest(ModelState) as IActionResult;
        }
    }

    public class Startup
    {
        public void ConfigureServices(IServiceCollection services)
        {
            services.AddMvc();
        }

        public void Configure(IApplicationBuilder app)
        {
            app.UseMvc();
        }
    }

    public class Program
    {
        public static void Main(string[] args)
        {
            var host = new WebHostBuilder()
                .UseKestrel()
                .UseStartup<Startup>()
                .Build();

            host.Run();
        }
    }
}

After having these files under the same directory, call the below commands:
dotnet restore
dotnet run

after that, send a GET request to /values?take=100:
curl -D - http://localhost:5000/values?skip=-1

Expected Results
Tugberks-MBP:~ tugberk$ curl -D - http://localhost:5000/values?skip=-1
HTTP/1.1 400 Bad Request
Date: Sat, 08 Oct 2016 15:43:51 GMT
Transfer-Encoding: chunked
Content-Type: application/json; charset=utf-8
Server: Kestrel

{"skip":["The field Skip must be between 0 and<PHONE_NUMBER>."],"take":["The field Take must be between 1 and 50."]}

Actual Results
Tugberks-MBP:~ tugberk$ curl -D - http://localhost:5000/values?skip=-1
HTTP/1.1 400 Bad Request
Date: Sat, 08 Oct 2016 15:43:51 GMT
Transfer-Encoding: chunked
Content-Type: application/json; charset=utf-8
Server: Kestrel

{"skip":["The field Skip must be between 0 and<PHONE_NUMBER>."],"Take":["The field Take must be between 1 and 50."]}

The casing of Skip and Take fields are inconsistent. As far as I can see, it serializes with the correct casing when the value is supplied for the field and the value is invalid. However, it serializes the field name wrongly when the field is not supplied as input at all and its default is invalid. At the first glance, it seems like a bug but not sure which parts of MVC is getting this wrong.
Is there an obvious workaround (e.g. custom serialization setting for ModelStateDictionary, etc.) that I can apply to achieve the expected result?
dotnet CLI Version
Tugberks-MacBook-Pro:ValidationJsonSerialize tugberk$ dotnet --info
.NET Command Line Tools (1.0.0-preview2-003121)

Product Information:
 Version:            1.0.0-preview2-003121
 Commit SHA-1 hash:  1e9d529bc5

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  10.12
 OS Platform: Darwin
 RID:         osx.10.12-x64

The ModelStateDictionary is case-insensitive. This means whatever adds a key chooses its case. In your /values?skip=-1 scenario, model binding adds a value for skip to the dictionary and validation adds an error to the existing entry in the dictionary. The same doesn't happen with the Take property.
To make the keys consistent, could capitalize the skip and take action parameters. But it'll look less odd to use PaginatedRequestCommand command instead.

@dougbu Ah, OK. I see now. Directly binding the query string to PaginatedRequestCommand made it consistent: https://github.com/tugberkugurlu/AspNetCoreSamples/blob/7286f517ee75986c567fd68d1654dacb30d3c855/repros/ValidationJsonSerialize/Program.cs#L21
I keep confusing ASP.NET Web API action selection with ASP.NET MVC Core. That's why I was directly binding to simple types but as they don't take effect on action selection, binding it to complex type makes it more clean overall 👍


P4TR: post about upgrading LN to take advantage of taproot's benefits

The plan is to include this guest post generously contributed by @zmnscpxj in next week's newsletter.  It's presented in this PR for anyone who wants to review it early.
@zmnscpxj : the text is this PR is identical to https://github.com/harding/bitcoinops.github.io/pull/21 .  The only changes are file renaming, squashing of the edit commits, and a rebase on our current master.

Sorry, I think I made a mistake with the size of 2-of-2 P2WSH as well, because I forgot about the extra dummy element that OP_CMS pops off the stack. I think the witness stack for 2-of-2 P2WSH should be 220 WU. And the whole input therefore 96 vB, P2TR keypath spend should be 57.5 vB.

Yeah, convinced myself that 96 vB should be the size for a 2-of-2 P2WSH input: https://bitcoin.stackexchange.com/a/108284/5406

@Xekyo thanks for the review!  Changes incorporated in https://github.com/bitcoinops/bitcoinops.github.io/pull/636/commits/162dbc401eaf986bee8590a3c4ea7c0e3f97b7fd in #636 .  Closing this PR in favor of that one.


Add option to manually set path to terminal

I'm running Windows and usually prefer to use Git Bash rather than the Windows Command Prompt. Being able to set this option would be great!

Nevermind. This is very easy to change using the command option!


Fastly is blocked

Hello and thanks for this amazing project.
In adc8004272e770cf871a3046920c01505aaed887 fastly.net was blocked. See my comment here: https://github.com/StevenBlack/hosts/commit/adc8004272e770cf871a3046920c01505aaed887#r27558445
I haven't looked much into it, but it seems to me that this domain belongs to the fastly.com cloud hosting/CDN platform.
Thus, quite a lot of sites break in interesting ways.

              IN      A

;; ANSWER SECTION:
a.sni.fastly.net.       86400   IN      A       <IP_ADDRESS>

Hey @FadeMind, can you take a look at this?
It has been introduced by the Spotify-Ad-free list 👍

Occurrences search
fastly.net can be found in the following lists
./data/Spotify-Ad-free/hosts <== Entry point
./alternates/fakenews-porn/hosts
./alternates/fakenews-gambling/hosts
./alternates/social/hosts
./alternates/gambling/hosts
./alternates/fakenews-social/hosts
./alternates/porn-social/hosts
./alternates/gambling-porn/hosts
./alternates/fakenews-gambling-porn-social/hosts
./alternates/fakenews-gambling-porn/hosts
./alternates/porn/hosts
./alternates/fakenews/hosts
./alternates/gambling-porn-social/hosts
./alternates/fakenews-porn-social/hosts
./alternates/gambling-social/hosts
./alternates/fakenews-gambling-social/hosts
./hosts

I should have added I'm using the basic list without any add-ons. Broken sites include reddit, github and bandcamp

@Biont We are talking about the same thing.
As it's also referenced in ./hosts that means that ./data/Spotify-Ad-free/hosts is part of the unified system which means that it's present in all extensions.

This is extended sources: https://github.com/CHEF-KOCH/Spotify-Ad-free
@CHEF-KOCH is maintainer of it.

@Biont my concern is, fastly.net appears to have landed on Sep 15, 2017.
Also, I don't experience the failure modes you see.  What specific NPM, Reddit, etc errors are you seeing?

@StevenBlack I'm not sure I follow (but please pardon my ignorance, I am looking at this repo for the first time). Your link goes to a commit from Spotify-Ad-free, but it was only added to this repo's config by #492 which was merged 3 days ago. Then its rules themselves went in with adc8004272e770cf871a3046920c01505aaed887 (which I assume is the result of a script which updates all rules and documentation accordingly).
So if I understand correctly, it's perfectly understandable that I'm only seeing problems now despite the rules being added to the source repo back in September. I can only speculate why it hasn't caused issues there yet, though.
The errors I was seeing were:

registry.npmjs.org was gone entirely. You can see in my OP that it turned out to be a CNAME of a.sni.fastly.net which ended up being blocked.

Assets from github cannot be loaded because assets-cdn.github.com is a CNAME of github.map.fastly.net

Assets from bandbamp could not be loaded because s4.bcbits.com is a CNAME of n.ssl.global.fastly.net

(I'm actually not quite sure what the issue with reddit was. Let's ignore I mentioned it from now on :D )
I added ffastly.net to my local whitelist and everything worked again.

@FadeMind Can you update the file? 👍

@funilrys  Talking about https://github.com/FadeMind/hosts.extras ??

@Biont It should be fixed once @StevenBlack update the repository 👍

@funilrys  at hosts.extras are copies of lastest changes in hphosts and spotify-ad-free. See lastest changes, so I don't need update these hosts files all time.

@FadeMind @funilrys done!


[Bug]: dear teachers, if the spu recognizes that yacl is not installed successfully, the yacl will be replaced with an openssl implementation?

Issue Type
Build/Install
Modules Involved
Others
Have you reproduced the bug with SPU HEAD?
Yes
Have you searched existing issues?
Yes
SPU Version
spu0.9.3
OS Platform and Distribution
ubuntu18.04
Python Version
3.9
Compiler Version
gcc11.2
Current Behavior?
dear teachers, if the spu recognizes that yacl is not installed successfully, the yacl will be replaced with an openssl implementation?
Standalone code to reproduce the issue
print("A bug")

Relevant log output
No response

YACL is a C++ dependency of SPU. There is no such a situation that YACL is so-called "not installed".

YACL is a C++ dependency of SPU. There is no such a situation that YACL is so-called "not installed".

thanks very much!!!!, i understand the dependency.
Before spu, i didnot install yacl solely, and i only installed spu with guideline, but when "bazel run -c opt //examples/python/utils:nodectl -- --config pwd//examples/flax_gpt2/3pc.json up"
it output "[warning] [openssl_factory.cc:83] Yacl has been configured to use Yacl's entropy source, but unable to find one. Fallback to use openssl's default entropy srouce"
And in /.cache/bazel/as312dsd23sa34/external/yacl/yacl, there are yacl lib installed by bazel of spu.
So simply entropy source cannot be used, and the cryptographic code in yacl will be used when performing secure inference?
thanks very much!!!!!!
/mnt/zhangwang/.cache/bazel/_bazel_zhangwang/a726b1a9c1370b22b7ac8039af1c1cf4/external/yacl/yacl

The warning message comes from YACL, not SPU. Maybe you should create an issue in YACL's repo.

The warning message comes from YACL, not SPU. Maybe you should create an issue in YACL's repo.

yeah, thanks very much!!!


Update Code Sponsor link position

@arnaudbenard When the link is found at the bottom of the README, it is more effective in helping funding this project.

Thx for the PR!
FYI the money goes directly to donations 👍


Adding furigana parser to the list of misc formats

Coverage remained the same at 82.75% when pulling 18e2a91556e638a588a53b1160271a61beff1561 on sachaarbonel:patch-1 into c5090ef1e2a1704851b1773169653728b0761d9c on Geal:master.

nice!

nice!


Update dependency

What this PR does / why we need it:
Update dependency
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

LGTM


Add a mute notification button

Feature Description

Add a button in the sidebar (and a shortcut) to disable/mute all notifications temporarily. Hide all notification badges and disable the sound from the services (didn't work in older versions).

PLEASE! WE have this in the previous version and in the new one (5) we don't, this feature is very important :(
I've 5 services connected, it drives me crazy to receive all those sound notifications and push.

is it possible at all to mute services at the moment? Haven't found any setting in the app

Used this feature from time-to-time myself. Not as a daily thing, but would be useful to have this back again.

Would really be useful to have that back.

I would like to stress the importance of this function. Then again the previous version showed Windows notifications and the 5.0.0 just shows a notification in the notification bar and not the action center.
I would like to see this functionality being brought back: option to disable all notifications; Windows toasts when receiving a notification from an app (such as WhatsApp).

I made a mockup for a "mute sound"/"mute notification" button:

That is definitely a much cleaner and consistent design! I like the second more though.

Most critical question, ever: Where do we put the Franz logo? 😁

Good point. Maybe you can add the logo at the very bottom that opens some window like "about franz", and then on top of it the settings and mute icons.
What I really don't like is having all of these nice icons without text and then the text below the franz logo because it's difficult for an user to understand that that icon is the settings icon.

It's starting to get really annoying now. Even when I have Windows 10 quiet hours enabled and turned the notifications for each service off, I still get notifications from Messenger and Whatsapp. I've decided to roll back to Franz 4.0.4 until the mute function is restored, because using the new versions causes too much of an intervention on my day to day work, while this function works perfectly in Franz 4.0.4.

@adlk I thought that you want to keep the logo, buuut do we really need it? 🙈  I can't think of one mac app that has a logo in the UI. It is still highly visible in the dock and app switcher (at least on mac).

@tobiasdueser No actually not. I‘ve thought about that for a while and I really like the mockup. I will do a first test in b14.

Please just make it mute notifications sound, not all sound as in previous version of Franz, it's incredibly annoying to not be able to just get rid of that annoying notification beep, without losing the ability to listen to e.g. WhatsApp voice messages.

@johangu While this is not a perfect solution, just disabling the services notification sound is not feasible at the current state.
While it is technically possible to fake an audio API and just filter certain audio files – a solution like this is so extremely error prone, especially with 3rd party recipe authors.
All in all, I wanted to have a better solution before adding this feature but there is a huge amount of requests to re-add this and we've made a quite good experience with this solution in the past.

I'm closing this issue as the initial feature request is ready for shipping. I'd suggest to open a new issue where we can discuss possible solutions for just disabling notifications sounds instead of muting the whole webview.


Backports for 0.15

This is a bunch of backports for the 0.15 branch that would be great to have on a stable release, since the current one breaks the build on Windows due to the missing gsubprocess functions.
The backport contains:

all Matteo's recent fixes
the work on fixing GBindingGroup (which as far as I can see does not break the API)
a couple of low hanging fruits (clippy warnings etc)

I did not go back further to pick more things... I saw quite a few patches for cairo/pango, but I have not followed that closely so I have not investigated further.

(leaving as draft to see if CI is ok)

I have now added to the backport all CI commits that applied cleanly and CI now passes. Removing the WIP flag.

I did not go back further to pick more things... I saw quite a few patches for cairo/pango, but I have not followed that closely so I have not investigated further.

Someone will have to do that before a bugfix release then :)


slic3r: Add ModuleBuild to BuildInputs, to fix hydra build

Failing on 16.03, please backport.
Things done:

[X] Tested using sandboxing (nix-build --option build-use-chroot true or nix.useChroot on NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

http://hydra.nixos.org/build/33298227/nixlog/1

For context: Module::Build used to be a part of the perl core distribution (master is currently unaffected by this issue).


Refactor ping-sender to support sendPingWithChanges

To support partition healing we need to manually specify the changes sent during a ping-request (instead of gossiping the changes from dissemination). In this case we also don't need to update the membership-list.
Both changes are required to be able to send and retrieve changes without marking all the members as faulty before merging partitions.

PingSender is currently not unit-tested but covered by the integration tests in ringpop-node (and indirectly by the shared integration tests in ringpop-common as well).
However, it might be desirable to add unit-tests now or in a separate PR.

Looks good after you have addressed my comments.


Error connecting to IP Stream

Hi, I am using v3.0.0-beta.2-nvidiadocker on my laptop. I successfully tested it out using a video file. Thought I would try it out with a random IP Cam in my city I got on Insecam. I set "VIDEO_INPUT": "remote_cam" and "remote_cam": "http://<IP_ADDRESS>:83/". When starting up, I got the following error that runs indefinitely:

You need to get the actual image stream link and not the general interface of the webcam: maybe this one will work: http://<IP_ADDRESS>:83/GetData.cgi?CH=1

I tried the new link and got running messages like this:

hum.. this feed does not seem to be compatible out of the box with OpenCV .
This gstreamer pipeline to decode a MJPEG stream should work:
souphttpsrc location=http://<IP_ADDRESS>:83/GetData.cgi?CH=1 ! multipartdemux ! image/jpeg,width=640,height=480 ! appsink
But maybe the camera isn't fast enough.. Can't help much more, try to find cameras with low resolution /  fast FPS and direct access to MJPEG stream.

Ok, thanks for the help!


add handling for :matches and :is

:any and :matches and :is need selector lists to test support, so the additional call was added.
:is is a special case since the standard renamed it, so it gets its own if statement.
For part of #6130

Thanks for submitting a PR!
If I'm understanding this correctly, it seems to be special casing a specific selector in code that is supposed to handle selectors generically. I'm not very comfortable with that, once we start handling exceptions like this, the code will progressively get messier and messier. If you can think of a more general way to handle this that will also work for other cases (now or in the future), I'd be glad to merge it, but this doesn't scale.

There are two things: one is that the original code used a generic selector {} to test support, and that will never work for :any, :matches, :is because they take parameters. So checking with another generic selector(a,p) {} is needed.
The other is the special case of a selector that got renamed, but the prefixes did not. The :is selector could be left out if you don't want the special handling, but it's not as if there are a huge number of selectors, so scaling isn't really that big of a deal. I suppose they could rename more in the future, but having a fix now shouldn't be dependent on some unknown future, should it? Do you have any suggestions for how else to do a simple if statement?

one is that the original code used a generic selector {} to test support, and that will never work for :any, :matches, :is because they take parameters. So checking with another generic selector(a,p) {} is needed.

Correct. Although it's impossible to know what parameters to test with when it comes to parameterized selectors, so this probably needs to be part of the selector definition (just like with values we tell PF which property to test them with).

but it's not as if there are a huge number of selectors, so scaling isn't really that big of a deal. I suppose they could rename more in the future, but having a fix now shouldn't be dependent on some unknown future, should it?

Famous last words :) While there's certainly always a danger of potential futures blocking current development, some planning ahead is always good. We rename (early) things all the time, it can easily happen again. Also, we don't tend to add stuff to PF with no implementations, and AFAIK :is has no implementations yet (feel free to correct me if that's not the case, I'd be delighted!)

Although it's impossible to know what parameters to test with when it comes to parameterized selectors, so this probably needs to be part of the selector definition (just like with values we tell PF which property to test them with).

In this case, if it's part of the definition, the prefix would be wrong. I would have to define another object to hold the test definition and some way of when to use it. But as of now, the only selectors that take parameters take the same parameters, so I used the shortest, smallest method to test them.
I'll remove the :is.
I guess by the time a browser supports :is, we can find some other way to do it since you can't have two with the same "name".

In this case, if it's part of the definition, the prefix would be wrong. I would have to define another object to hold the test definition and some way of when to use it.

I don't understand what you mean here. Could you elaborate?

But as of now, the only selectors that take parameters take the same parameters, so I used the shortest, smallest method to test them.

That's not true, e.g. :nth-child() or :dir() accept different kinds of arguments. They don't need prefixing though. But assuming all parameterized selectors that may ever need prefixing have selector arguments is a bit fragile.