Opinion on derive-where

I wondered what you think of derive-where?
Is there some use-case that didn't fit? Did you not like the syntax?
Apologies for creating an issue for this, I couldn't come up with a more appropriate method.

I wondered what you think of derive-where? Is there some use-case that didn't fit? Did you not like the syntax?

I wish I knew about it when I started, it seems quite more advanced :)
My approach is less intrusive and let you set the bounds only once, potentially reducing the amount of lines you have to write for the same results, my main use-case is wot-td in which we have plenty of structures that require custom bounds over associated types for a number of std derives.

Apologies for creating an issue for this, I couldn't come up with a more appropriate method.

It is good :) Given that we are tackling a similar problem, we could factor the code generation and share it across the two crates if you think it is worth the refactoring time :)

My approach is less intrusive and let you set the bounds only once, potentially reducing the amount of lines you have to write for the same results, ...

Could you expand on that? Actually as far as I can tell the approach in derive-where requires fewer lines and you can set the bounds only once too.

Given that we are tackling a similar problem, we could factor the code generation and share it across the two crates if you think it is worth the refactoring time :)

I think that sounds like a great idea! But I would like to figure out what the differences are exactly before going there.

e.g.
use derive_bounded::{Clone, Debug};

#[derive(Clone, Debug, PartialEq, Eq)]
#[bounded_to(T::A, T::B)]
struct ...

I thought you had to do
use derive_where::derive_where;

#[derive_where(Clone; T::A, T::B)]
#[derive_where(Debug; T::A, T::B)]
#[derive_where(PartialEq; T::A, T::B)]
#[derive_where(Eq; T::A, T::B)]
struct ...

Interesting, I have to go figure out why this is the conclusion you came to, clearly the documentation has to be improved.
Your example works too actually, but this works as well:
use derive_where::derive_where;

#[derive_where(Clone, Debug, PartialEq, Eq; T::A, T::B)]
struct ...

https://github.com/ModProg/derive-where/pull/50 hopefully improves the first impression.


Nameplate Tweaks 3

YEP

[x] Fixed an extremely rare potential issue with Kui's fader plugin if we were modifying the visibility of nameplates.

Not aware of any bugs aside from the Kui window resize issue, so flagging as ready for review + merge into the final release.


Upgrade mangohud to 0.6.9

This is mainly to get
https://github.com/flightlessmango/MangoHud/commit/a155c10df39ee6d007779ed2ea65d191ff6aa3d7 which fixes a bug with the CPU wattage being shown as 1000x higher than what it actually is on my 6800u.

Already done


Coverage data using codecov

Unfortunately, I don't know how to test if this works with out doing a PR.

@jfhbrook checkout http://codecov.io/github/jfhbrook/node-ecstatic?ref=8a914b29ed5456857895699c3881242d42dace7b

Neat! Messing around with this on master to see if I can get the reports to work.


ask "what is up", no reply？

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
ask "what is up", no reply？
Briefly summarize your issue:

ask "what is up", no reply
What is the expected behavior?

right reply
What behavior are you observing?

no reply
Provide the steps to reproduce the issue, if applicable:

try many times ， ask ”what‘s up"
Tell us about your environment:

What version of the AVS Device SDK are you using?
  <x.y.z>

1.7.0
Tell us what hardware you're using:

[ ] Desktop / Laptop
[ ] Raspberry Pi
[ ] Other - tell us more:

Tell
us about your OS (Type & version):

[*] Linux
[ ] MacOS
[ ] Raspbian Stretch
[ ] Raspbian Jessy
[ ] Other - tell us more:

only the first time  have the right reply.
I added some logs myself.
diff --git a/ACL/src/Transport/HTTP2Stream.cpp b/ACL/src/Transport/HTTP2Stream.cpp
index d81eca2..7a98f79 100644
--- a/ACL/src/Transport/HTTP2Stream.cpp
+++ b/ACL/src/Transport/HTTP2Stream.cpp
@@ -324,9 +324,10 @@ size_t HTTP2Stream::writeCallback(char* data, size_t size, size_t nmemb, void* u
      * payload. For all other response codes we're getting a JSON string without
      * multipart headers.
      */
-    if (HTTPResponseCode::SUCCESS_OK == stream->getResponseCode()) {
+    ACSDK_DEBUG(LX("writeCallback +0").d("numChars", numChars));
+    if (HTTPResponseCode::SUCCESS_OK == stream->getResponseCode()){
         MimeParser::DataParsedStatus status = stream->m_parser.feed(data, numChars);
-
+        ACSDK_DEBUG(LX("writeCallback +1").d("numChars", numChars));
         if (MimeParser::DataParsedStatus::OK == status) {
             return numChars;
         } else if (MimeParser::DataParsedStatus::INCOMPLETE == status) {
@@ -337,6 +338,7 @@ size_t HTTP2Stream::writeCallback(char* data, size_t size, size_t nmemb, void* u
         }
     } else {
         stream->m_exceptionBeingProcessed.append(data, numChars);
+               ACSDK_DEBUG(LX("writeCallback +2").d("numChars", numChars));
     }
     return numChars;
 }
diff --git a/ACL/src/Transport/MimeParser.cpp b/ACL/src/Transport/MimeParser.cpp
index 32adc08..760ea84 100644
--- a/ACL/src/Transport/MimeParser.cpp
+++ b/ACL/src/Transport/MimeParser.cpp
@@ -96,18 +96,22 @@ void MimeParser::partBeginCallback(const MultipartHeaders& headers, void* userDa
             LX("partBeginCallbackFailed").d("reason", "mimeParsingFailed").d("status", parser->m_dataParsedStatus));
         return;
     }
-
+    ACSDK_ERROR(LX("partBeginCallback +1"));
     std::string contentType = headers[MIME_CONTENT_TYPE_FIELD_NAME];
     if (contentType.find(MIME_JSON_CONTENT_TYPE) != std::string::npos) {
         parser->m_currDataType = MimeParser::ContentType::JSON;
+               ACSDK_ERROR(LX("partBeginCallback +2"));
     } else if (contentType.find(MIME_OCTET_STREAM_CONTENT_TYPE) != std::string::npos) {
+          ACSDK_ERROR(LX("partBeginCallback +3"));
         if (1 == headers.count(MIME_CONTENT_ID_FIELD_NAME)) {
             auto contentId = sanitizeContentId(headers[MIME_CONTENT_ID_FIELD_NAME]);
             auto attachmentId =
                 parser->m_attachmentManager->generateAttachmentId(parser->m_attachmentContextId, contentId);
+                       ACSDK_ERROR(LX("partBeginCallback").d("attachmentId",attachmentId).d("contentId",contentId).d("m_attachmentContextId",parser->m_attachmentContextId));

             if (!parser->m_attachmentWriter && attachmentId != parser->m_attachmentIdBeingReceived) {
                 parser->m_attachmentWriter = parser->m_attachmentManager->createWriter(attachmentId);
+                               ACSDK_ERROR(LX("partBeginCallback +4"));
                 if (!parser->m_attachmentWriter) {
                     ACSDK_ERROR(LX("partBeginCallbackFailed")
                                     .d("reason", "createWriterFailed")
diff --git a/AVSCommon/AVS/src/AVSDirective.cpp b/AVSCommon/AVS/src/AVSDirective.cpp
index 4cd1d09..7da172f 100644
--- a/AVSCommon/AVS/src/AVSDirective.cpp
+++ b/AVSCommon/AVS/src/AVSDirective.cpp
@@ -55,6 +55,7 @@ std::unique_ptr<AttachmentReader> AVSDirective::getAttachmentReader(
     const std::string& contentId,
     sds::ReaderPolicy readerPolicy) const {
     auto attachmentId = m_attachmentManager->generateAttachmentId(m_attachmentContextId, contentId);
+       ACSDK_ERROR(LX("getAttachmentReader").d("attachmentId",attachmentId).d("contentId",contentId).d("m_attachmentContextId",m_attachmentContextId));
     return m_attachmentManager->createReader(attachmentId, readerPolicy);
 }

no reply.txt

Hi @zuowanbushiwo, I notice that you say you are using v1.7 of the SDK.  There are quite a few bug fixes we have made to the SDK since then, would you be able to try this again with v1.10 of the SDK?  Thanks!

Hello, I'll be closing this thread due to inactivity, but feel free to reopen if you need further assistance. Thanks.


[BBPBGLIB-1141] Remove HDF5reader.mod which is already replaced by libsonata

Context
As we have migrated to read circuit with libsonata API, HDF5reader is no more called in neurodamus thus the mod file can be removed.
Scope
Remove HDF5reader.mod from data/mod folder
Testing
n/a
Review

[ ] PR description is complete
[ ] Coding style (imports, function length, New functions, classes or files) are good
[ ] Unit/Scientific test added
[ ] Updated Readme, in-code, developer documentation

I guess this file needs to go?
https://github.com/BlueBrain/neurodamus-models/blob/cfd9689a42f8c4a3a34e893c9e50837c27b1ca7b/common/hoc/GluSynapseLegacyHelper.hoc


hangs on wss://

This probably isn't an issue with phpws...
This works fine:
<?php
require_once("vendor/autoload.php");
$loop = \React\EventLoop\Factory::create();
$logger = new \Zend\Log\Logger();
$writer = new Zend\Log\Writer\Stream("php://output");
$logger->addWriter($writer);

$client = new \Devristo\Phpws\Client\WebSocket("ws://echo.websocket.org/?encoding=text", $loop, $logger);

$client->on("request", function($headers) use ($logger){
    $logger->notice("Request object created!");
});

$client->on("handshake", function() use ($logger) {
    $logger->notice("Handshake received!");
});

$client->on("connect", function() use ($logger, $client){
    $logger->notice("Connected!");
    $client->send("Hello world!" . time());
});

$client->on("message", function($message) use ($client, $logger){
    $logger->notice("Got message: ".$message->getData());
    $client->close();
});

$client->open();
$loop->run();

2015-05-19T10:24:05-04:00 NOTICE (5): Request object created!
2015-05-19T10:24:05-04:00 NOTICE (5): Handshake received!
2015-05-19T10:24:05-04:00 NOTICE (5): Connected!
2015-05-19T10:24:05-04:00 NOTICE (5): Got message: Hello world!1432045445
2015-05-19T10:24:05-04:00 NOTICE (5): Got CLOSE frame

But changing it to wss:// hangs:
2015-05-19T10:24:34-04:00 NOTICE (5): Request object created!

is all I get. Since ws:// works fine this is probably an issue with the underlying SSL, but I can't figure it out.

This was resolved when I did an OS upgrade. Something must be wrong in my PHP/SSL stack.


Fix sequence logo parallelization bug

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Remove the expand function to avoid overwriting of sequence logos
Fixes #30
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have not reduced the existing code coverage

The interface of the script has to be corrected as well: we do not need input_files which are nargs="+", you do not need to sort it, nor iterate over it - it will be just one path.

Now when I look into your code I do not see how this would work... When do you call gather_motifs_names(config["pwm_directory"]) ?

I have added  sequence logos as input to rule plot_heatmap_of_MotEvo_results in the snakemake pipleine.

Now when I look into your code I do not see how this would work... When do you call gather_motifs_names(config["pwm_directory"]) ?

Earlier it was getting called from rule all and now from rule plot_heatmap_of_MotEvo_results.

The way I see it now - after the small modification - is that you will catch the whole directory after expansion - this is not what we want, please look at the description of #30

No, the script is taking one file at a time and not the directory, you may confirm it with the terminal after running the pipeline.
I have updated the dag and rulegraph.


[Bug]: version not respected in mkdocs feature

Feature id and version
ghcr.io/devcontainers-contrib/features/mkdocs:2
Devcontainer base Image
mcr.microsoft.com/vscode/devcontainers/base:ubuntu-22.04
What happened?
The devcontainer as specified below does not respect the version for mkdocs:
{
    "name": "install version 1.4.3 of mkdocs",
    "image": "mcr.microsoft.com/vscode/devcontainers/base:ubuntu-22.04",
    "features": {
        "ghcr.io/devcontainers-contrib/features/mkdocs:2": {
            "version": "1.4.3"
        }
    }
}

Instead, the latest version is installed:

Relevant log output
No response

@agyss Thanks for reporting this!
The mkdocs version is getting bumped because of the mkdocs-material requirement
mkdocs-material is currently being injected by default.  in order to select an older version you can clear the "plugins" input like so
    "name": "install version 1.4.3 of mkdocs",
    "image": "mcr.microsoft.com/vscode/devcontainers/base:ubuntu-22.04",
    "features": {
        "ghcr.io/devcontainers-contrib/features/mkdocs:2": {
            "version": "1.4.3",
            "plugins": "",
        }
    }
}

I understand this behavior is not optimal. Had I knew mkdocs-materialhas such a strict mkdocs version requirement I would have not included it as a default injection.  As it stands currently removing mkdocs-material it as a default injection will probably break environments of people who rely on its existence, forcing a major feature version bump.
@agyss What are your thoughts? Should material remain a default injection or not?

It's quite unlucky that mkdocs-material enforces the versioning of the application it is used with - that's like enforcing an OS update by an application. As it's so commonly used, I would suggest raising an issue at the mkdocs-material repo to remove the enforced mkdocs version in the requirements and rather check the available version by other means. If the version of mkdocs does not fulfill the requirements, they may throw an error or similar.
If they don't agree, I guess we have no other option than to remove it from the default injections, as it completely overwrites an explizit configuration statement and this is IMHO too big an issue.

This project is not associated with the devcontainer project and appears to have been abandoned https://github.com/devcontainers-contrib/features/issues/628 . The official project has removed all devcontainer-contrib features from their listing. https://github.com/devcontainers/devcontainers.github.io/issues/451. There is a fork that is being worked on to update and maintain the features https://github.com/devcontainers-extra/features


Add basic search screen

Add rudimentary search screen.
Acceptance Criteria
Search bar

Bookmarks button on right. Don't worry about changing this
Cross when typing input
Gurmukhi font? @bhajneet unicode entry, or gurmukhi ascii for search? We can implement switching too, but in different issue
Working back button

Results list

Clicking on list item fires some callback
List items have information components as per mocks (create a component for result item)
Bonus: Virtualisation with flatlists or whatnot

Please share iOS + Android renders in your PR.
@bhajneet please share relevant mocks.

Pursuing new design. Updated to reflect this. @bhajneet please share mocks here.

Basic doesn't require search history in pane 1, bookmark icon in pane 1

Should I keep this to unicode or do you want me to use ASCII OpenGurbaniAkhar-Black? Pinging @Harjot1Singh @bhajneet

Unicode

Note: the font should be native to the platform if possible (so you shouldn't need to define any fonts). So "Gurmukhi MT" for iOS, "Noto Sans Gurmukhi" for Android, "Raavi" for Windows (when there is server support from mobile to open a web browser on desktop).

Cross when typing input

For iOS this is a default behavior for text inputs but for android it is not. So should I add this cross to clear input for android platform or no?

Yes, add it to Android. Will look up styling later.
On Mon, Dec 28, 2020, 15:18 Saihajpreet Singh<EMAIL_ADDRESS>wrote:

Cross when typing input
For iOS this is a default behavior for text inputs but for android it is
not. So should I add this cross to clear input for android platform or no?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/shabados/mobile/issues/95#issuecomment-751851677, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ADLZ3B752QCSI33DIKPAVMDSXDR2NANCNFSM4QH3CE7A
.


Build PublicTerminalCore for ARM64, and package it with WPF

I also took the opportunity to clean up the WPF stage's artifact rules.
Closes #12786

@msftbot merge this in 1 minute


error in .less file  when execute npm run test-frontend ...

Hello Antoine!
So i tried to use less in the project. I change all .css to .less  and add less loader in the webpack
but when i run test-frontend
it throws.
ERROR in ./src/website/app.less
Module build failed: Error: "extract-text-webpack-plugin" loader is used without the corresponding plugin, refer to https://github.com/webpack/extract-text-webpack-plugin for the usage example
at Object.module.exports.pitch (../node_modules/extract-text-webpack-plugin/loader.js:21:9)
@ ./src/website/app.js 12:293-314
not sure what is going on.
I really appreciate your help !
Thanks
Kanghui.

Hello Kangui,
I have modified the webpack configuration for the frontend in order to support correctly the import of less files ;-)
The error you had was due to the fact that css imports (but also less or sass files imports) trough webpack are extracted to external css files in production mode (it is recommended to do so in order for your application to load faster) but not in test or watch mode (as we want hot reloading, that's one of the coolest feature with webpack, you can modify your css, less or sass files on the fly while you're testing your application and it will be automatically taken into account without any browser refresh! ). For instance, execute 'npm run start-dev', once the application is compiled, open it in your browser, then modify the file '/src/website/components/parallelcoords/parallelcoords.css' in order to change the color of the lines in the visualization (selector: .foreground path, property: stroke). Save the file, switch to your browser and enjoy the magic :-)
Cheers,
Antoine


Document datasette.urls.row and row_blob

These are in the codebase but not in documentation. I think everything else in this class is documented.
class Urls:
    ...
    def row(self, database, table, row_path, format=None):
        path = f"{self.table(database, table)}/{row_path}"
        if format is not None:
            path = path_with_format(path=path, format=format)
        return PrefixedUrlString(path)

    def row_blob(self, database, table, row_path, column):
        return self.table(database, table) + "/{}.blob?_blob_column={}".format(
            row_path, urllib.parse.quote_plus(column)
        )

Related issue - I'm not 100% settled on the design for these yet:

https://github.com/simonw/datasette/issues/1048#issuecomment-1179757912

Totally missed that issue. I can close this as a duplicate.


chatglm input dim bug

glm-4-9b-chat concat's dim=0, but recognizes to dim=1.  how about determine it by batch_size, the dim should equal to batch_size

fixed in https://github.com/intel/auto-round/pull/304


Neither configuration seems to work

We recently worked with @jaxoncreed to configure our CSS installation. He tried to use both the Penny recipe, and the Mashlib recipe, and we could not get them to work in our configured server or in the default configuration suggested here.
When installed as the native pod host browser, the Penny recipe errors during the login flow, preventing users from logging into the pod management UI.
With Mashlib, users are able to log into the pod host UI, but then immediately get a series of pop-ups complaining about the logged in Pod not having a preferences file (which it does), and offering to create one:
First Alert: You do not currently have a preference file. OK for me to create an empty one?
If I press cancel, it bugs me again two more times. If I press OK I get the next alert:
Second Alert: Sorry; I am not prepared to do this. Please create an empty file at (?)
I tried this with both an existing account and a new account, same results. Both of them do seem to have preferences files in the place I would expect them to be.

Some discussion about the Penny issue can be seen at https://github.com/CommunitySolidServer/CommunitySolidServer/discussions/1176. As far as I know no new npm version of Penny has been released so this is not yet resolved.
Not sure about the mashlib issue. Perhaps @bourgeoa can help there.

Can you give some detail on your CSS version and mashlib version.
Are you using a HTTP or HTTPS.
I'm running https://bourgeoa.ga:3000/bourgeoa/ and https://bourgeoa.bourgeoa.ga:3100/

You can take a look at the version and config on this fork / tag: https://github.com/mysilio-co/community-server/tree/jackson-contract-mashlib
I suspect it's because we're using a multi-pod host with subpath routing instead of subdomain routing, i.e. mashlib is looking for the WebId at username.example.com/profile/card#me instead of example.com/username/profile/card#me


CLI install synthetic environment variable duplicate in operator pod container

What happened?
Installing the operator with the CLI and the parameter  --operator-env-vars=CAMEL_K_SYNTHETIC_INTEGRATIONS=true does not always works to activate the synthetic integration support. This is because the default value (false) is still present in the pod's container spec.
Steps to reproduce
Install the operator:
kamel install --operator-id=camel-k-synthetic-env --operator-env-vars=CAMEL_K_SYNTHETIC_INTEGRATIONS=true

Check the operator pod:
spec:
  containers:
  - args:
...
    - name: CAMEL_K_SYNTHETIC_INTEGRATIONS
      value: "false"
    - name: CAMEL_K_SYNTHETIC_INTEGRATIONS
      value: "true"
    - name: KAMEL_OPERATOR_ID
      value: camel-k-synthetic-env
...

Relevant log output
No response
Camel K version
main branch

Thanks. Then, the problem is indeed in the way we use --operator-env-vars as I guess that any generic env var is added twice if reported twice.


Please add selective syncing

Panamax is a great tool, but unfortunately it doesn't allow selective syncing. the last time I used it I got more than 105GB worth of crates (and that was few months ago) while I needed only few of them, this is extremely inefficient in this use case, it would be very nice to specify crates by name or something similar to tell the tool to only download/sync those.
I'm aware of #71 but that isn't an ideal solution because you have to run cargo vendor on all of your projects, and you need to make a new project if you want newer crates. it would be nice to have selective syncing baked into panamax natively.
Thank you.

The big trouble with such a feature is, for any crate, you also have to discover and grab all of its dependencies. Having the user manually specify these dependencies wouldn't be a good UX, and otherwise every crate that gets downloaded would need to be extracted, read its Cargo.toml dependencies, and then recursively download them. Then you have to decide which versions of the dependent crates get downloaded; do you download them all, or just the current latest version (which might break on upgrades)?
The nice thing about using a vendor directory is that cargo effectively handles the above for you, at least to some extent.
With all that said, I'm definitely not against such a feature existing in Panamax, however I don't have the time to work on it. I'd probably accept a PR from someone willing to implement this.

Additionally, this project https://github.com/wcampbell0x2a/zerus might be worth looking at.

We were able to accomplish something similar (blacklisting) by cloning the crates.io index, filtering out what we didn't want, and then pointing panamax to that filtered index when syncing. The filter itself was fairly easy to write -- maybe 100 lines of rust. I'm not sure what your precise use case is but I hope that helps.

potential answer: cargo vendor only to grab project-related dependencies.


About Depth maps

Firstly, I would like to express my appreciation for your work on this dataset. I am genuinely impressed by the effort and detail that has gone into it.
I am reaching out with a question regarding the dense depth maps provided in the demo data. Specifically, I am interested in understanding how these depth maps should be interpreted. Could you clarify whether the depth maps represent relative depth or absolute depth?

Hi
The depth maps are collected by a 3D scanner, and they represent relative depth.


Make a button for "make new fit for all" in demag_gui interpretation editor

There is currently hidden functionality to add a fit to all specimens in the interpretation editor if now specimen is selected. It would be nice to make this functionality be more accessible and transparent to the user by having a button that says "make new fit for all specimens" in the demag_gui interpretation editor.

done.


Question ZTE F6005

Hi, thanks for your great work!!!
I have a question regarding ZTE F6005.
I cannot get serial connection. Is it disabled by default?
Is there any chance to change parameters?
Do I need to flash to access it?
The description is misleading.

Thank you for the fast response!
 Is it disabled by default?

in firmware distributed in Italy yes, in others we do not know

Is there any chance to change parameters?

Only if you change the firmware

Do I need to flash to access it?

only if you cannot load firmware from gui

The description is misleading.

you can change it

Hi, I have the same problem and as mentioned, I can't establish a serial connection. How is it possible to flash the firmware (and in case which one) given the fact that the web interface is not having (apparently) this possibility?


use same names for the keys in the EdgeKVStorage

like we use for path details.
Two decisions I had to make:

the internal classes are not available for client-hc code (or our Example), so we now have two classes EdgeKVStorage.Details and Parameter.Details. As they have a different use case I find this acceptable.
the related properties in the instructions change due to this change but not the "name" as it was street_name already before. So it is a breaking change for the client side (but only if the in 5.0 newly introduced properties like ref or destination are used) but an improvement as it makes it more consistent (like street_ref instead of ref). Note: the path details are not affected by this.

Nice, thanks! :+1:

but only if the in 5.0 newly introduced properties like ref or destination are used

These were introduced in 6.0, right?


Doc: SBT plugin version

http://gatling.io/docs/2.1.6/extensions/sbt_plugin.html points to 2.1.5 while 2.1.6 is out.

2.1.6 has the recompile all bug in it.

Right. We'll release 2.1.7 once #2763 is fixed.


Pre-ActionList CSS Modules bug fixes

Prep for ActionList -> CSS Modules
Changelog
Test removals
Scary, you must think I'm losing it!

ActionList with trailing action is visually broken unless the semantic button FF is enabled, which it is not in production. I am wrapping this functionality into the CSS Modules FF and we will add back these stories when we are no longer comparing snapshots to default.
NavList "bad" example should not have a visual test

UI Bugs
All other changes are bugs I found while converting to CSS, or little things that help align the default VRT snapshots to the updated CSS version
Rollout strategy

[x] Patch release
[ ] Minor release
[ ] Major release; if selected, include a written rollout or migration plan
[ ] None; if selected, include a brief description as to why

Testing & Reviewing

Merge checklist

[ ] Added/updated tests
[ ] Added/updated documentation
[ ] Added/updated previews (Storybook)
[ ] Changes are SSR compatible
[ ] Tested in Chrome
[ ] Tested in Firefox
[ ] Tested in Safari
[ ] Tested in Edge
[ ] (GitHub staff only) Integration tests pass at github/github (Learn more about how to run integration tests)

The dotcom integration test failures appear to be unrelated to this PR 👍


Resolves #6414 | Typo fix

What's changed, or what was fixed?

Typo fix
commenting out a line because it introduced a failing test due to a missing file..

Fixes: #6414
Target Live Date: YYYY-MM-DD

[ ] This has been reviewed and approved by (NAME)
[x] I have run npm test locally and all tests pass.
[ ] I have added the appropriate type-something label.
[x] I've staged the site and manually verified that my content displays correctly.

CC: @petele

:tada: This has been pushed live to https://developers.google.com/web/

@rottina what was the failing test? This change removes credit for a coworker that coauthored the blog post, so I'd like to make sure that we fix whatever was failing.


Add a section called all days deals

These don't really have happy hours..they are more like happy days and can be confusing for the user...or take up the space of real happy hours.
Bristol's farm student discount?
Taco Tuesdays
Santorini Tuesdays etc

I'm not sure if showing these as separate makes sense. A lot of times Taco Tuesday deals only apply to certain times and in cases where it is all day the deal time would be the hours of operation for that day. What exactly is confusing about it?

Closing issue due to inactivity.


Fixed issue #894

This line solves the problem with the device rotation.

Codecov Report

Merging #952 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master    #952      +/-   ##
=========================================
- Coverage    6.44%   6.43%   -0.01%
=========================================
  Files          97      97
  Lines        5201    5202       +1
  Branches      488     488
=========================================
  Hits          335     335
- Misses       4838    4839       +1
  Partials       28      28

Impacted Files
Coverage Δ

...w/commons/contributions/ContributionsActivity.java
0% <0%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

I tested it and yes, it solves the problem. But, on rotation moment contribution list appears and disapears very fast. Since it is very fast I couldn't get screen shots. Did you see that @JohnKal ?

@neslihanturan yes i see it now. If it is a problem i will try to fix it.

@misaochan and @maskaravivek , I think we should prioritize this one also before release. What do you think about merging this PR?

Yeah, sounds good to me. We can create a new issue for the appearing/disappearing if needed.


avcodec-58.dll not found

I just Installed torch and torchvision with the following command:
pip install torch===1.4.0 torchvision===0.5.0 -f https://download.pytorch.org/whl/torch_stable.html
system:
OS: win 7, python 3.6.8, with cuda
when I do:
import torchvision
I get a pop up "python.exe - System Error" "The program can't start because avcodec-58.dll is missing from your computer..."
I have torch/torchvision running on another win machine (10, cpu only) without problems.  Is this related to ffmpeg?  I do not have it installed on either machine.
Any suggestions to get this resolved would be appreciated.

av is installed before building wheels on Windows, so ffmpeg is actually a required component. It can be seen here. https://github.com/pytorch/vision/blob/winbuild/v0.5.0/packaging/windows/build_vision.bat
If you use Anaconda, you can use conda install -c conda-forge av to install that. Otherwise, you'll need to do that manually. You can refer to http://blog.gregzaal.com/how-to-install-ffmpeg-on-windows/.

Thank you, peterjc123 for your reply.
I installed ffmpeg with chocolatey, but still get the same error.  What's odd is that I did not have to deal with any of this on my win 10 laptop and torch / torchvision worked fine (it is cpu only and python 3.7).
I should mention that I started with torch breaking on this machine at first that I addressed by upgrading python from 3.6.0 to 3.6.8.  Perhaps something did not reinstall cleanly?
You mention av being installed as part of the installation, where do I find it? I do not see it in C:\Python36\Lib\site-packages\av

Sorry for confusion, I mean av is installed in our build environment. It leads to ffmpeg component being built and thus the DLLs of them are required at the user's side.

Thank you, though I probably still do not or even have to understand the finer points of your explanation for the reasons why. However I did just find the critical bit of information that was missing to resolve the error.  Apparently there are two versions of ffmpeg static and shared.  Apparently chocolatey installs the static one and the shared one is needed as it is the one with the dlls including avcodec-58.dll.

Maybe you could download them here. https://ffmpeg.zeranoe.com/builds/

Thanks, that is what I did this time.  This is how I figured out that there is a ffmpeg build with the dlls and a build without.

The ffmepg is installed successfully and the path is added to the environment variable ,
and avcodec-58.dll exists in the bin folder right now, but still I get same error,
any suggestions?

If you are using Python 3.8, then you may need an additional os.add_dll_directory call.

I just pip installed using Command Prompt and then tried to run torch. I am getting the same error.

I am a new in Julia and after adding the Plots package I tried to use Plots and I got this Error message:
julia> using Plots
[ Info: Precompiling Plots [91a5bcdd-55d7-5caf-9e0b-520d859cae80]
ERROR: LoadError: InitError: could not load library "C:\Users\niri.julia\artifacts\7350a6401f1c0d38cc3518193083bc4f83adfe99\bin\avcodec-58.dll"
The specified module could not be found.
Stacktrace:
[1] dlopen(::String, ::UInt32; throw_error::Bool) at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.5\Libdl\src\Libdl.jl:109
[2] dlopen at D:\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.5\Libdl\src\Libdl.jl:109 [inlined] (repeats 2 times)
[3] init() at C:\Users\niri.julia\packages\FFMPEG_jll\w0b7h\src\wrappers\x86_64-w64-mingw32.jl:234
[4] _include_from_serialized(::String, ::Array{Any,1}) at .\loading.jl:697
[5] _require_search_from_serialized(::Base.PkgId, ::String) at .\loading.jl:782
[6] _require(::Base.PkgId) at .\loading.jl:1007
[7] require(::Base.PkgId) at .\loading.jl:928
[8] require(::Module, ::Symbol) at .\loading.jl:923
[9] include(::Function, ::Module, ::String) at .\Base.jl:380
[10] include(::Module, ::String) at .\Base.jl:368
[11] top-level scope at none:2
[12] eval at .\boot.jl:331 [inlined]
[13] eval(::Expr) at .\client.jl:467
[14] top-level scope at .\none:3
during initialization of module FFMPEG_jll
in expression starting at C:\Users\niri.julia\packages\FFMPEG\vocw2\src\FFMPEG.jl:3
ERROR: LoadError: Failed to precompile FFMPEG [c87230d0-a227-11e9-1b43-d7ebe4e7570a] to C:\Users\niri.julia\compiled\v1.5\FFMPEG\TGvga_Ik59J.ji.
Stacktrace:
[1] error(::String) at .\error.jl:33
[2] compilecache(::Base.PkgId, ::String) at .\loading.jl:1305
[3] _require(::Base.PkgId) at .\loading.jl:1030
[4] require(::Base.PkgId) at .\loading.jl:928
[5] require(::Module, ::Symbol) at .\loading.jl:923
[6] include(::Function, ::Module, ::String) at .\Base.jl:380
[7] include(::Module, ::String) at .\Base.jl:368
[8] top-level scope at none:2
[9] eval at .\boot.jl:331 [inlined]
[10] eval(::Expr) at .\client.jl:467
[11] top-level scope at .\none:3
in expression starting at C:\Users\niri.julia\packages\Plots\cc8wh\src\Plots.jl:11
ERROR: Failed to precompile Plots [91a5bcdd-55d7-5caf-9e0b-520d859cae80] to C:\Users\niri.julia\compiled\v1.5\Plots\ld3vC_Ik59J.ji.
Stacktrace:
[1] error(::String) at .\error.jl:33
[2] compilecache(::Base.PkgId, ::String) at .\loading.jl:1305
[3] _require(::Base.PkgId) at .\loading.jl:1030
[4] require(::Base.PkgId) at .\loading.jl:928
[5] require(::Module, ::Symbol) at .\loading.jl:923
can someone help me to resolve the problem

Closing, as this issue is fixed in 0.6.0. If you are using 0.5.0, please refer to https://github.com/pytorch/vision/issues/1877#issuecomment-586157441 and https://github.com/pytorch/vision/issues/1877#issuecomment-609003986.


V1.1.21: queue corruption?

Added some tracks from a local media playlist to the queue using the add to queue action. They where not added!
Then I tried to start one immediately with play now. That failed with this error:

Logger: homeassistant.components.websocket_api.http.connection
Source: custom_components/mass/websockets.py:979
Integration: Home Assistant WebSocket API (documentation, issues)
First occurred: 15:17:54 (2 occurrences)
Last logged: 15:18:02

[547658280528] Error handling message: Unknown error (unknown_error)
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/components/websocket_api/decorators.py", line 27, in _handle_async_response
    await func(hass, connection, msg)
  File "/config/custom_components/mass/websockets.py", line 96, in async_get_mass_func
    await orig_func(hass, connection, msg, mass)
  File "/config/custom_components/mass/websockets.py", line 979, in websocket_play_media
    await player_queue.play_media(msg[URI], msg[COMMAND])
  File "/usr/local/lib/python3.9/site-packages/music_assistant/models/player_queue.py", line 237, in play_media
    await self.append(queue_items)
  File "/usr/local/lib/python3.9/site-packages/music_assistant/models/player_queue.py", line 415, in append
    next_items = self.items[self._current_index + 1 :] + queue_items
TypeError: unsupported operand type(s) for +: 'NoneType' and 'int'

released patch release 1.1.22 just now with a fix for this

Double issue


refactor: batch 1 of warning fixes

Pulling changes from https://github.com/microsoft/ConversationLearner-UI/pull/1350
That PR fails smoke test, so trying to isolate safe changes.

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

npm package (@next dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


limine: 7.3.1 -> 7.4.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/limine-bootloader/limine/releases.
meta.description for limine is: Limine Bootloader
meta.homepage for limine is: https://limine-bootloader.org/
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 7.4.0 with grep in /nix/store/qbxhac8z672lcbl41pyaqv3i1dp04k7a-limine-7.4.0
found 7.4.0 in filename of file in /nix/store/qbxhac8z672lcbl41pyaqv3i1dp04k7a-limine-7.4.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
limine

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qbxhac8z672lcbl41pyaqv3i1dp04k7a-limine-7.4.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A limine https://github.com/r-ryantm/nixpkgs/archive/2ea9604b32c54ac6905c11b8ec1c02570333db49.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/2ea9604b32c54ac6905c11b8ec1c02570333db49#limine

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qbxhac8z672lcbl41pyaqv3i1dp04k7a-limine-7.4.0
ls -la /nix/store/qbxhac8z672lcbl41pyaqv3i1dp04k7a-limine-7.4.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review --extra-nixpkgs-config '{ allowInsecurePredicate = x: true; }' run on x86_64-linux 1

4 packages built:

limine
limine.dev
limine.doc
limine.man

Maintainer pings
cc @48cf @phip1611 for testing.

@wegank why is this broken on Darwin?

You can check out the logs on Hydra. It basically never builds since its intro in nixpkgs.

https://hydra.nixos.org/job/nixpkgs/trunk/limine.aarch64-darwin
https://hydra.nixos.org/job/nixpkgs/trunk/limine.x86_64-darwin


Remove changenumber key, move to Apps/Subs tables instead

It's metadata anyway.

There is really no point in doing this, it's just doing just fine in appsinfo.


Fix #361 by setting value

Fix https://github.com/Visual-Regression-Tracker/Visual-Regression-Tracker/issues/361 by setting value in the create-test-request.dto.ts file.

roll back package-lock.json changes, please the fix if fine!

Ooops, yeah, done that.


Dockerize React App

Summary
We need to Dockerize our React client. This story:

[ ] creates a Dockerfile for React client

Motivation
As is the case with most modern projects, we should look to Dockerize this application. While for the time being we are simply deploying to S3, that may not always be the case. We should look to Dockerize this so that if we do every host the site elsewhere we have a nice containerized version.
Describe alternatives you've considered
Not Dockerizing the app, leaving it as is.

I'd also like to give this a try if that's cool :) I've been meaning to learn how to Dockerize an app

Go for it! Take a look here for reference, could be useful 👍

I'm been trying to do this for a while, and still getting a lot of errors. I don't know if anyone would be interested in pairing, or if someone who's dockerized an app before has any advice? The error is a little long to paste, but this is where it starts: "error /app/node_modules/canvas: Command failed."

There doesn't really seem to be much point in doing this for now - if anything, it's a nice perk but not necessary


specify a default timeout when running docker-compose stop and allow …

…it to be configurable
motivation:
we have applications which take longer than the default of 10 seconds to shut down completely.  This causes false negatives on build results.

feedback addressed, thanks!

@augi @cemeyer2 is out today, so I addressed the PR feedback (rebased off of master so I could make sure I understood the full change)

Thanks! Released as 0.3.26.

Thanks for the quick release!


[BIP9] Enable different deployments per network.

This PR refactors the BIP9 code to support different deployments per network.

@zeptin, thank you for your review. I've addressed the issue you commented on.

Some minor comments @quantumagi fix those and lets commit this PR, lots to refactor on this part of the code but not right now.

Ok I will review again.
Note we checked the stratis delpoyment for CSV flag CheckSequenceVerify but not for Transaction.LockTimeFlags we should also cover that @bokobza
I will do that.

.

Damn i saw this late, reposting what i said on slack fullnode chan, I'm wondering if wouldn't be better to rename BitcoinBIP9Deployments to something more agnostic (e.g. NetworkDeployments). I don't think having hard-bounded bitcoin implementation details coming out from stratis package is appropriate, would be nice to have classes named for their usage and not their original concept (BIP9 could be referenced in comments)
What do you think?


Angular1 UI router incompatibility with Portal Routing

Hello,
First off, thanks so much for this example. This speeds up the development of the portal architecture significantly. So far you have solved a lot of the problems we would have faced had we started from scratch with.
However we have one issue, we are using angular-1 single spa portal library with UI router. Once the angular1 app is loaded, all other routes / apps cease to load. Guessing this is due to an incompatibility between portal routing and angular1 routing
any ideas?

I assume this issue has been clarified. Closing for now.


Fixes ember-runtime.action-handler-_actions deprecation

@locks I assume that mixing in the actions hash now works as expected?

Ah, found it: https://github.com/emberjs/ember.js/pull/12028


Can't SSH after upgrade with "pacman -Syu"

steps to reproduce:

Create a new server from the arch image
SSH to it, run pacman -Syu
reboot it
try to SSH to it again

boot seems normal:
[  OK  ] Reached target Basic System.
         Starting SSH Key Generation...
[  OK  ] Started Entropy Harvesting Daemon.
         Starting Network Name Resolution...
         Starting SCW fetch ssh keys from metadata...
         Starting SCW fetch kernel modules from Scaleway mirror...
         Starting Permit User Sessions...
         Starting SCW generate ssh keys on first boot...
[  OK  ] Started Daily man-db cache update.
[  OK  ] Reached target Timers.
[  OK  ] Started D-Bus System Message Bus.
         Starting Network Service...
         Starting Login Service...
[  OK  ] Started Network Name Resolution.
[  OK  ] Started SSH Key Generation.
[  OK  ] Started SCW fetch kernel modules from Scaleway mirror.
[  OK  ] Started Permit User Sessions.
[  OK  ] Found device /dev/ttyS0.
[  OK  ] Started Network Service.
[  OK  ] Reached target Network.
         Starting One-Shot Network Time Service...
[  OK  ] Started Serial Getty on ttyS0.
[  OK  ] Reached target Login Prompts.
         Starting SCW generate machine id...
[  OK  ] Started Login Service.

ping @aimxhaisse, do you have a clue ?

Hello, I submitted the ticket about this, and I noticed when I ran an update and got systemd 228 and then rebooted. So i suspect it could have something to do with updating from systemd 227 to 228.

I also think that systemd 228 is the guilty.
I mounted my partition in an other server (/dev/nbd1), downloaded systemd 226 in this repo and installed with pacman -r myMountedFolder -U systemd-226-3.1-armv7h.pkg.tar.xz
The server works again and boot well
I hope that it can help you

I can confirm that this indeed is caused by the systemd 228 update. If you spawn a new instance and update anything but systemd, systemd-sysvcompat, libsystemd then the instance will continue to work after a reboot.

Alternate rescue method using Rescue bootscript and chroot. (No need to detach volume)

Go to the server management panel e choose "Rescue" as bootscript (Unhide ADVANCED options).
Do an Hard Reboot.
Connect via ssh to the server's public IP address with root user.
Mount the volume

# mount /dev/nbd0 /mnt

Setup the chroot environment

# cd /mnt
# mount -t proc proc proc/
# mount --rbind /sys sys/
# mount --rbind /dev dev/
# mount --rbind /run run/
# cp /etc/resolv.conf etc/resolv.conf

Chroot

# chroot /mnt/arch /bin/bash

Downgrade to previous systemd-227-1. (Assuming having previous systemd packages still in pacman cache. YMMV).

pacman -U /var/cache/pacman/pkg/systemd-227-1-armv7h.pkg.tar.xz

Exit chroot

CTRL-D

Go to server managment panel and select back the default bootscript 4.1.6-std #249
Reboot from shell or Hard reboot from panel
Voila!

PS

To prevent systemd from being upgraded at next pacman -Syu add IgnorePkg=systemd to /etc/pacman.conf

Thanks a lot for your instructions @manchoz 😊👍🏻

You welcome, @QuentinPerez!

Thanks everyone and @manchoz for the easy fix. Has this been reported upstream?

@pavlos256 what do you mean by upstream? I have made a ticket with scaleway who in turn has created this issue.
@manchoz I think you might want to use: IgnorePkg=systemd libsystemd systemd-sysvcompat to keep them all at the same version.

@mikkeloscar By upstream I meant Arch Linux ARM or systemd. Or is this problem specific to Scaleway?

@pavlos256 I think that the problem is specific to Scaleway since I have several armv7 Arch Linux machines (RPis, BBBs, CB2, etc) which run systemd-228 whitout any issue.
My guess is that the problem is related to networking/DHCP: the system hangs/become unreachable also whan a systemctl restart systemd-networkd is executed (only with systemd-228).

I applied patch 122793e to my server and I was able to boot with systemd 228.

Pavlos256 patch worked for me. Basically what I did was:

Select the Rescue script in the control panel
Reboot machine
Login as root
Mount /dev/nbd0 to /mnt
Edit /mnt/etc/systemd/network/eth0.network and add DHCP=yes under [Network]
Unmount and exit
Select the latest bootscript in the control panel
Reboot

@jezze: thank you for this step-by-step guide ! :+1:

The new image (released yesterday) contains the fix and the latest version of systemd

Tried this just now and can't login. Even having the "DHCP=yes" line in /etc/systemd/network/eth0.network doesn't allow systemd-resolved and networkd to start. I did manage to logged in with SSH by removing eth0.network, but resolved did not start. Up to systemd-231 now.

@sneakin did you try to add this as well? https://github.com/scaleway/image-archlinux/pull/33/files


Plugin won't stay active

As of yesterday the @ Symbol Linking plugin wont stay enabled.  Setting and exiting, then reentering settings and it shows not enabled.  Even exiting app after setting it to enabled and you come back and it may show enabled, but doesn't do anything... and going back in to settings it will again show as disabled.
Obsidian 1.4.12 on Win11
Most recent update of @ Symbol plugin installed.
Thanks!

Interesting, could certainly be caused by the latest change that unloads & reloads the plugin when you exit the plugin's settings page.
I can't recreate on my Mac, I'll have to pull out the Windows PC this weekend and dig into it.
Thanks for repotting this, hopefully I'll have it solved by Sunday

I'm seeing the same thing..
I'm on a Mac, running OS 14.0 + Obsidian 1.4.14

+1 same configuration as @luckman212

Hi y'all thanks for reporting. This is hopefully fixed in https://github.com/Ebonsignori/obsidian-at-symbol-linking/releases/tag/1.4.7


Gerrit checks plugin should not apply to refs/meta/config

Submitting CLs against refs/meta/config is currently broken due to the unsatisfiable checks requirement:

Workaround is cherry-picking and pushing the CL via Git.
CC @q3k

(we're still using the checks plugin for UI display purposes)


Modify SchedulerQueueingHints

This feature gate is kind of unique one, added as Beta and enabled by default from the first step.
/kind documentation
/kind bug

Wow, it's the wrong place


A working software environment for lag-llama

I reported in another issue that the most recent pytorch-lightning does not work with lag-llama. I also tried a few version combinations among pytorch, pytorch-lightning, and gluonts. Eventually I could get the code run for 385 epochs with the following requirements.txt:
orjson
torch==2.0.0
gluonts==0.13.5
pytorch-lightning==1.9.5
datasets
xformers
git+https://github.com/kashif/hopfield-layers@pytorch-2
etsformer-pytorch
reformer_pytorch
einops
opt_einsum
pykeops
scipy
apex
git+https://github.com/microsoft/torchscale

But the run still failed due to a divide-by-zero error in gluonts. Before I try more, I thought it'd be more efficient to ask the question here: could you share a working requirements.txt with version number specified?
BTW, the error I got with my requirements.txt is:
Epoch 385: : 110it [00:23,  4.66it/s, loss=-0.64, v_num=0, val_loss=-.690, train_loss=-1.10]Epoch 385, global step 38600: 'val_loss' was not in top 1

Epoch 385: : 110it [00:23,  4.65it/s, loss=-0.64, v_num=0, val_loss=-.690, train_loss=-1.10]
Use checkpoint: /home/lagllama_test/test/pytorch-transformer-ts/lag-llama/model-size-scaling-logs/0/experiments/lightning_logs/version_0/checkpoints/epoch=335-step=33600.ckpt
Predict on m4_weekly
m4_weekly prediction length: 13

Running evaluation:   0%|          | 0/359 [00:00<?, ?it/s]
Running evaluation: 100%|██████████| 359/359 [00:00<00:00, 81024.28it/s]
logger.log_dir :  /home/lagllama_test/test/pytorch-transformer-ts/lag-llama/model-size-scaling-logs/0/experiments/lightning_logs/version_0
os.path.exists(logger.log_dir) :  True
Predict on traffic
traffic prediction length: 24

Running evaluation:   0%|          | 0/6034 [00:00<?, ?it/s]
Running evaluation: 100%|██████████| 6034/6034 [00:00<00:00, 1090128.80it/s]
/home/lagllama_test/conda/envs/lagllama/lib/python3.10/site-packages/gluonts/evaluation/_base.py:422: RuntimeWarning: divide by zero encountered in scalar divide
  metrics["ND"] = cast(float, metrics["abs_error"]) / cast(
/home/lagllama_test/conda/envs/lagllama/lib/python3.10/site-packages/gluonts/evaluation/_base.py:422: RuntimeWarning: divide by zero encountered in scalar divide
  metrics["ND"] = cast(float, metrics["abs_error"]) / cast(
/home/lagllama_test/conda/envs/lagllama/lib/python3.10/site-packages/gluonts/evaluation/_base.py:422: RuntimeWarning: divide by zero encountered in scalar divide
  metrics["ND"] = cast(float, metrics["abs_error"]) / cast(
/home/lagllama_test/conda/envs/lagllama/lib/python3.10/site-packages/gluonts/evaluation/_base.py:422: RuntimeWarning: divide by zero encountered in scalar divide
  metrics["ND"] = cast(float, metrics["abs_error"]) / cast(
/home/lagllama_test/conda/envs/lagllama/lib/python3.10/site-packages/pandas/core/dtypes/astype.py:134: UserWarning: Warning: converting a masked element to nan.
  return arr.astype(dtype, copy=True)

Thanks a lot.
Yan

Hey @hohe12ly, I'll look into this soon and get back!

BTW, my software environment hasCentOS 8 and NVIDIA V100S-PCIE-32GB GPUs, if this info would be helpful.

Hi, sorry for the delay.
Seems like you don't get errors, you only get warnings. Those warnings are normal.
Anyway, I use the following for my requirements.txt
gluonts==0.13.3
numpy==1.23.5
pytorch_lightning==2.0.4
torch==2.0.0+cu118
wandb
scipy

Thanks, Arjun. I tested your configuration. It works. I still see the divide by zero warnings. As you mentioned, it's normal.
Since torch=2.0.0+cu118 no longer works on pip's default index server, I had to modify requirements.txt for pip install:
--index-url https://download.pytorch.org/whl/cu118
--extra-index-url https://pypi.org/simple
torch==2.0.0
torchvision==0.15.1
torchaudio==2.0.1
numpy==1.23.5
gluonts==0.13.3
pytorch_lightning==2.0.4
datasets
xformers
git+https://github.com/kashif/hopfield-layers@pytorch-2
etsformer-pytorch
reformer_pytorch
einops
opt_einsum
pykeops
scipy
apex
git+https://github.com/microsoft/torchscale
wandb
orjson


ROX-21188: add back proxy for scc

Description
Add back scc proxy that got lost in #9002.
Checklist

[x] Investigated and inspected CI test results
[ ] Unit test and regression tests added
[ ] Evaluated and added CHANGELOG entry if required
[ ] Determined and documented upgrade steps
[ ] Documented user facing changes (create PR based on openshift/openshift-docs and merge into rhacs-docs)

If any of these don't apply, please comment below.
Testing Performed
Here I tell how I validated my change
CI
Reminder for reviewers
In addition to reviewing code here, reviewers must also review testing and request further testing in case the
performed one does not seem sufficient. As a reviewer, you must not approve the change until you understand the
performed testing and you are satisfied with it.

/test all

/test ocp-4-11-ui-e2e-tests ocp-4-14-ui-e2e-tests

/test all

/test ocp-4-11-ui-e2e-tests ocp-4-14-ui-e2e-tests


Dialog blur offset

Information

Haze version: 0.7.0
Platform: Native Android (min sdk 30, target 34)

Expected Behavior
Dialog is uniformly blurred

This screenshot was generated by enabling the fullscreen mode
(activity.window.decorView.systemUiVisibility = View.SYSTEM_UI_FLAG_FULLSCREEN)
Actual Behavior
Dialog's blur is offset by the top (or bottom) bar when not in fullscreen

Steps to Reproduce the Problem

Create a new native android project
Copy-paste the sample code for the dialog preview
Launch the app on the device

Unfortunately, I can't compile the source code to do any debugging (yet).

I'm afraid that I can't reproduce this at all. If you can provide a sample which reproduces on an emulator then I can take a look.

@chrisbanes sure, can you try this repo? https://github.com/Stavrenas/haze-offset

I still can't recreate this an emulator or Pixel 8.
I'm afraid that if this isn't reproducible on an emulator then it's almost certain to be a OEM/device specific issue, and there's not much I can do to help here really. What device and Android version are you using?
FYI, the integration here is extremely simple: it's just a call to View.getLocationOnScreen.

I'm on a Pixel 6 on an Ubuntu dev environment, however this happens also on a Windows machine with a Poco X4 GT device.
I tried the same thing on the emulator, Pixel 8 (default settings) and the result is the same.

I'm starting to think, maybe it's jdk related? I'm on version 17, I'll try a newer one and update you

So just to confirm, this only happens when deploying previews to device?


Add additional styles for FluentFilteredExtension SiteTree flags. Fixes #308

Related issue/improvement: https://github.com/tractorcow/silverstripe-fluent/issues/308

Looks good but I'll need to test to make sure it looks ok.


Debian 8 x86_64 (TEST) reports bc not found

build step 13, xfstests failed.  stdio output shows that it is failing to find 'bc' (the math program) when checking its environment, before running any actual tests.
+ sudo -E ./check -zfs -x dio -x sendfile -x user
bc not found
+ RESULT=1
+ exit 1

This string appears in the xfstests-zfs code, in common.config:
130 export SED_PROG="`set_prog_path sed`"
131 [ "$SED_PROG" = "" ] && _fatal "sed not found"
132
133 export BC_PROG="`set_prog_path bc`"
134 [ "$BC_PROG" = "" ] && _fatal "bc not found"
135
136 export PS_ALL_FLAGS="-ef"
137

Looks like the debian package is called 'bc'

Submitted PR https://github.com/zfsonlinux/zfs-buildbot/pull/9

Merged as:
9ddb239 Debian 8 required bc for xfstests


Making it work on macOS  #112

Have you actually tested that it works on your macOS+MPS environment?
I have been careful not to add code that does not work on macOS since https://github.com/nagadomi/nunif/issues/112, but I have not tested it on macOS for the last few years.

Yes, tested, and that's why I am submitting :)

If this works without changes for requirements-torch.txt, I will merge this PR.
Also, StereoFormat=VR90 perhaps does not work and there are a few ideas to prevent fallback to CPU as much as possible. So I am planning to test on macOS soon on my end.

Yes this PR works on macOS, with this sequence of commands:
python3 -m venv .venv
source .venv/bin/activate
pip3 install -r requirements-torch.txt
pip3 install -r requirements.txt
pip3 install -r requirements-gui.txt
python -m iw3.gui

I wanted to add that to README but not sure which one. Install-Mac.md was not linked from main document, so I found it only after it was done.
Install instructions are usually in one file for all platforms. If you want, I can organise all into one file and have separate development instructions as it usually goes.

I merged this to master with cherry-pick.
https://github.com/nagadomi/nunif/commit/584e55c3bf11a1e61bf9cceb12b8632e361d3bf2
Additional changes
https://github.com/nagadomi/nunif/commit/87b3089c46a0e314f1f8a00ad5be5eabe84ba575
One problem that cannot be fixed is segmentation fault when exiting GUI.
It is a bug in wxpython and already fixed, but pip is not updated.
https://github.com/wxWidgets/Phoenix/issues/2455

Currently FP16 option is ignored (It is always FP32).
When MPS autocast is supported on PyTorch, it can be supported on our side as well.
https://github.com/pytorch/pytorch/pull/99272


Create a new release v1.0.0 and give credit to all past contributors in its notes

v1.0.0
Dear GoFr Community,
We're thrilled to announce that GoFr is now an open-source project, marking a new chapter in its evolution. We extend our heartfelt gratitude to all past and present contributors who've been instrumental in GoFr's development.
As part of our security measures, we've removed the complete project history, ensuring its integrity moving forward.
By making GoFr open source, we aim to foster a collaborative environment for developers of all backgrounds to innovate and enhance the project.
We invite you to explore the newly open-sourced GoFr, fork it, and contribute to its development. Your expertise is invaluable, and we look forward to new ideas and collaborative efforts.
Feel free to reach out with questions, feedback, or suggestions. Thank you for your contributions and support.
Let's shape GoFr's next chapter together!
Release Notes
Features

REST, gRPC server, Cron, and CMD creation
Support for SQL and NoSQL Data Stores with Auto-Initialization

SQL: MySQL, MS SQL, PostgreSQL
NoSQL: MongoDB, DynamoDB, Cassandra, Yugabyte, Redis
Pub/Sub: Kafka (with Avro), Azure Event Hubs, AWS EventBridge, Google Pub/Sub
Search Engines: Apache Solr, Elastic Search

Support for file stores with remote file abstraction

Remote File Stores: FTP, SFTP, AWS S3, GCP, Azure

Support for AWS SNS Notifier
Predefined logs with log levels for STDOUT and JSON
Database state management using Migrations
Inbuilt middleware for OAuth, Performance Monitoring (NewRelic), CORS, Tracing (Zipkin and GCP)
Support for runtime configuration overrides
Observability through traces, metrics, health checks, and heartbeats

Past Contributors:

Vikash Kumar (vikash)
Stella Rani (stella551)
Aryan Mehrotra (mehrotra234)
Umang Mundhra (umang01-hash)
Vipul Rawat (vipul-rawat)
Akshat Kumar Singhal (akshat-zopsmart)
Abishek R V (abishek-r-v)
Atul Gond (atulkumargond)
Mahak Singhania (mahaksinghania-zs)
Gurpreet Kumar (Gurpreet-zs)
Tejaswi Sapala (Tejaswi-zs)
Shubham Sirothiya (shubham-zs)
Shashank Shekhar (ssshekhu53)
Vatturi Naga Surya Prakash (suryap-zs)
Subrahmanyam (subrahmanyam470)


v0.5.0 Release Checklist

Remaining actions:

[ ]  Review release (product owner)
[ ] Approve release (product owner and release manager)
[x] Create binaries (any DRUD maintainer)
[x] Draft release notes (release manager)
[ ] Draft additional announcements for blog, newsletter, etc (not applicable at the moment)
[x] Create release (release manager)
[ ] verify that autoupdate is working properly
[ ] Update Roadmap (TPM/release manager)
[ ] Followup issues spun off if we need them. (Rework this process to include Monica's role).

For additional background information, please see our Product Release instructions here.

To test the release - https://439-99947022-gh.circle-artifacts.com/0/artifacts/DDEV UI-0.5.0.dmg

Release Notes:
Public v.0.5.0 Alpha Release
Prerequisites
DDEV CLI is installed and properly working.
Release Notes

This is an still an early alpha release. We fully expect there to be bugs and we have a backlog of features we are working on. We'll respond as quickly as we can to new requests.
We would love your suggestions, contributions, and help! Please review our Guidelines for Contributing.

Release Highlights

Drupal 6 support
UX and UI Improvements
Docker and DDEV-cli system checks
Better alert styling and functionality
Package Updates
Fixed Community issue #141

Known Issues

This version only supports Mac OS. We are working on getting Linux and Windows support and testing in by hopefully the next major release.
While existing TYPO3, Drupal 6, and Backdrop sites will work, the Create New Project functionality currently only works from Drupal 6, Drupal 7, Drupal 8, and WordPress. We are working hard on adding support for Typo3, and Backdrop.
We are still working on the code signature so you’ll need to right-click to bypass Mac security settings when opening the app the first time.

For all the release artifacts - https://circleci.com/gh/drud/ddev-ui/439#artifacts/containers/0

@dclear - We can't  verify that autoupdate is working properly until it's published.

@alkymst : I moved that bullet towards the end of the list.

Closing this issue / milestone / sprint board


CodeBuild requires PrivilegedMode

Hi! This should not be necessary for the curated Docker environment. Can you tell me more about what problem you ran into that led to this pull?

I built an image based on the curated one (Dockerfile), and followed the advise given here and it fails if not in privileged mode, build.log.

I just tried with an image based on the newer openjdk-8 image because that now comes with Docker as of 2 days ago and without the install steps and it fails to log into docker, build.log.
I'm not sure what else I should try.

In these cases you're deriving from the curated image but not using the curated image, which is why privileged mode is required. This reference architecture uses the curated image directly and thus does not require the change you've proposed in this pull. Hope that makes sense.

It does. Thank you.


chore: Group all features without self-updater for simplified distro packaging

The self-updater feature is problematic for distro package builders where the executable does not have permission and should not be trying to monkey with the system installed binaries. Distros have their own update mechanisms that shouldn't be tampered with by every app that comes along. This means distro have to build with --no-default-features for apps that include self-updaters by default, but that also means we have to maintain a list of features we do want. This is not only tedious it is error-prone because there is a very good chance of new features getting overlooked when doing version bumps.
Setting up a feature group like this makes it much easier for distros to build without the unwanted features without getting out of sync with upstream enhancements over time.

Personally I would actually recommend taking the self updater out of the default feature list entirely. Folks can and should get their updates by whatever means they first used to get it (distro packages, cargo install, source builds, etc.). The only exception I would make is for the upstream built binaries attached to releases. Those probably can and should have the feature enabled. That means adding the feature manually to the CI builds, but setting it to be off by default in everything else. I made this PR to be the least intrusive change possible, but if you would accept the change to the default feature list I would be happy to adapt it for this recommendation.

Personally, I'm up for adapting default features in the way, that you can package with default-features instead of using another newly introduced feature. I'm myself not a very big fan of having self-updatable executables. So I understand where you are coming from. Let's wait for @aawsome opinion though, and if he agrees we can use the mentioned changes to the default features, instead.
I can update our CI/CD workflows then.

Thanks for the review and being willing to re-consider the defaults. I'll update my changes with that in mind.

I've replaced 5c1089d with 8be7b74 which just drops the self-updater from the default flag list.
I had a look at CI but it isn't apparent to me what ends up where. None of the RPM or other package builds should have this feature enabled (as the meta data for the package would be out of sync even if somehow the binary got updated). On the other hand any binaries that the end use would download and place manually themselves are candidates for having this re-enabled.
@simonsan Feel free to tag team on this PR or point me in the right direction or whatever...

This needs to wait a bit with merging though, as I need to update the CD first to build rustic-nightly and release with the corresponding added features. Will merge it when ready.


Allow source polling to be turned off on an image basis

Images could possibly have an annotation/spec field that avoids triggering builds if the repo ref is changed
Use case -
Instead of polling git, users can use kp CLI to trigger the build synchronously and watch for its status in CI pipelines.
This might also be coupled with a global switch on the controller side to disable this feature.

Hi @samj1912 ,
I think this can be accomplished today by providing  revision (not a branch or a tag) to the kpack image. When a new commit is available the kpack image can be updated with the new revision and a build will be triggered in the meantime kpack will not poll for updates.
If you are using kp that would look like kp image patch <image-name> --git-revision <rev> --wait

That leads to a slightly non user friendly experience as they have to resolve the revision to a SHA. It could also helo with the trigger workflow I described above if this was implemented.

@samj1912 Could you elaborate on the use case? I'm not sure I see the value of this feature. I think this is better accomplished using git branches.

For context, I believe @samj1912 and I chatted more about this in CNB slack: https://buildpacks.slack.com/archives/CQ10WHMT4/p1614025660002500


Feat/markdown utility

Related Ticket(s)
Just removed an extra line of comment that was bothering me (lol).

Not sure @emerson-pereira we might need to go back to the drawing board for this pull request. 😉


Does this repo have an active maintainer?

Curious about more recent Ruby language features and incorporating them into this project.

I'd also be curious about that - I revisited the Koans recently to introduce someone to Ruby and would like to help update them.

Hello, here to add that this repository needs an update. I believe this Koans is for Ruby 1.9, however, if you go to Ruby Koans website, they have updated files there.


Update attribute-derive

Looks like there's something that happens when running clippy? This shows up on all runs, but clippy is non-failing on the main test pass, so it only shows up on check-wasm.
 error: hidden lifetime parameters in types are deprecated
Error:    --> crates/bonsaidb-macros/src/lib.rs:359:16
    |
359 |         input: ParseStream,
    |                ^^^^^^^^^^^ expected lifetime parameter
    |
    = note: `-D elided-lifetimes-in-paths` implied by `-D warnings`
    = help: to override `-D warnings` add `#[allow(elided_lifetimes_in_paths)]`
help: indicate the anonymous lifetime
    |
359 |         input: ParseStream<'_>,
    |                           ++++


Add GitHub Releases action to deploy workflow

While we don't really need to upload release files to GitHub (as they are uploaded to PyPI), creating releases does provide a mechanism to notify users that a new release is available. As GitHub will automaticaly create files from the repo when none are provided, we upload the official distribution files instead. Fixes #1365.

Thank you 👍 😄


Consider replacing main deployment with stateful set

A stateful set allows replicas to have their own PVC. This seems like a good fit for Cryostat that maintains state, and could solve issues like #487 and #491 where there is an assumption that the Cryostat pod has exclusive access to its PVC.

On second thought, having more than one PVC is probably not what we want since users will be accessing Cryostat through a load balancer. The data between the replicas would not be consistent. For now, the best solution is probably to use the Recreate strategy and force the replica count to be 1.


Feat : Data Space Detail Page – tags

Feat : Data Space Detail Page – tags

As a user of the portal,
I want to check Sata Space related tags
So that I can quickly understand what this Data Space is about

Acceptance criteria
Scenario: default display (desktop)
Given that I am a user of the web portal (authenticated or unauthenticated),
When I am on the detail page of a Data Space,
Then I should see the related tags appear as presented in the mockup
Scenario: mobile display (desktop)
Given that I am a user of the web portal (authenticated or unauthenticated),
When I am on the detail page of a Data Space,
And I use a mobile device
Then I should see the related tags appear in a mobile friendly display
Technical Specifications
Tags should be fetched from ontology
Tags can contain text on 2 lines maximum, with an ellipsis in case of longer text (same behavior as Chips)
Requirements
Mockups
Desktop :

Mobile :

Environment

staging URL: https://app.staging.okp4.network/

Additional informations
None.

Test 06/04/23
Desktop : Firefox, Safari, Chrome
Mobile : Safari (iPhone 12)
Scenario : general display (desktop) : OK ✅
Note : I can't test when the tag is long with these faked data -> To test with the ontology connected
Scenario : mobile display : OK ✅
Thanks @0xLodz !

You're right :) It's good thank you !


Binding the "intended deploytments" to the phase is statuses.

Here's the problem: the /status endpoint reports two things: the list of
deployments when the current resolution cycle started, and the resolutions that
have been completed so far. From those two things, the client can figure out
what's up with the deployment it cares about, effectively by answering two
questions: first, is the server working on my deployment? Second, has it
resolved yet?
Because this is polling an ongoing process, we in fact keep two status lists:
the most recent "complete" status, and the current live one. The in progress
list is fresher, but the stable one has a resolution for everything.
Trouble was, we were sharing a single list of deployments between both, which
meant for updates (i.e. not the first successful deployment) the list would
include the new update, and the stable list would include "it's settled", so it
looked like a stable status.
This is fixed by attaching a copy of the intended deployments to each of the
two status reports, so that resolutions tie to their intentions. Obvious when
you think about it, I suppose.
The server continues to serve the buggy common depenedencies so that old
clients won't freak out, and the client will use the common list if the server
doesn't provide the new ones - otherwise it would never see the intention to
deploy the service it was waiting on. Those concessions to backwards
compatibility will need to be torn out at some point, maybe even soon.

Codecov Report

Merging #355 into master will decrease coverage by 0.13%.
The diff coverage is 84.61%.

@@            Coverage Diff            @@
##           master    #355      +/-   ##
=========================================
- Coverage   61.64%   61.5%   -0.14%
=========================================
  Files         162     162
  Lines        8947    8955       +8
=========================================
- Hits         5515    5508       -7
- Misses       2992    3004      +12
- Partials      440     443       +3

Impacted Files
Coverage Δ

graph/local_config.go
43.18% <ø> (-1.27%)
:arrow_down:

lib/deployable_chans.go
82.9% <100%> (+0.44%)
:arrow_up:

ext/docker/image_mapping.go
74.5% <50%> (-0.88%)
:arrow_down:

lib/resolvestatus.go
91.76% <66.66%> (-2.14%)
:arrow_down:

lib/resolver.go
79.31% <75%> (-0.69%)
:arrow_down:

lib/status_poller.go
80.18% <85.18%> (-1.77%)
:arrow_down:

lib/auto_resolver.go
88.05% <0%> (-1.5%)
:arrow_down:

lib/diff_concentrator.go
77.55% <0%> (-1.03%)
:arrow_down:

Continue to review full report at Codecov.

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

Discussed API versioning on Hipchat.


Implement Vencord's fake nitro plugin

Would be pretty swag if this was an option, I believe it just spoofs nitro, apparently lets you stream in HD and use custom emojis in other servers
https://github.com/Vendicated/Vencord/blob/main/src/plugins/fakeNitro.ts

It's possible to inject Vencord into Webcord and other Web based clients, I'm not sure how but over on the discord-screenaudio side, the maintainer managed to do it. https://github.com/maltejur/discord-screenaudio/issues/59#issuecomment-1275068867
I asked him how to do it and once he replies (or doesn't) we will know the procedure. It should be the same since both clients are essentially a chromium wrapper.

I think you can add support for Chrome extensions to your application. The fact is that Vencord (like many others) comes as an extension for Chrome.

I think you can add support for Chrome extensions to your application. The fact is that Vencord (like many others) comes as an extension for Chrome.

…except extensions support on Electron is nowhere close to what's on Chromium – in fact, a lot of features in Electron are its own thing as Electron removes Chrome-specific parts of the engine, including the extensions.

I asked him how to do it and once he replies (or doesn't) we will know the procedure. It should be the same since both clients are essentially a chromium wrapper.

I believe the Chromium engine both in QtWebEngine and Electron is heavily stripped off many unnecessary features which might only make sense for browsers, but not web applications. In Electron, extensions implementation was basically designed in mind for DevTools extensions and stuff like React debugging. Therefore an API support might also be very limited and some extensions might not work at all, especially those based on manifest V3 as I suppose Electron doesn't support them now.

I might also plan to allow for unprivileged script injection by allowing loading the scripts inside some directory in app.asar. Take a note these might run in it's own isolated context, so messing with global variables might not be possible as these will be only valid for the specific context.
Anyway, that's essentially a better extension support, I don't want to support integration with any specific third-party mods. I close this issue for this reason.


Move the code path of get_gae_labels() to emit()

Closes #4823. See discussion in #3359.

@liyanhui1228 thank you! do you want to cut a new release?

@jonparrott Yeah thx!


PKI: Return an empty buffer instead of null when Vault returns 204

This only applies to the VaultInternalPKISecretEngine.getRaw. Previously when fetching an empty CA Chain or CRL it would thow a NPE, now it returns an empty list.

can you reflect this change of behavior in the javadoc?

There isn't a change of behavior. This just fixes a NullPointerException when the CA Chain  or CRL is empty.

There isn't a change of behavior. This just fixes a NullPointerException when the CA Chain or CRL is empty.

ok. I thought we were changing the return type from null to empty.

@vsevel Merge?


Feature Request: Update training data

Looks like the training data is until October 2021, It will be great if the training data is up to date.

Agreed, but Chatty does not include the ChatGPT back-end server. It’s just the front-end to existing ChatGPT servers. So please direct the request to the ChatGPT server you’re using (such as TomTom’s internal instance, if you’re using TomTom’s Azure instance).


Clarified alternation

Clarified a bit of the wording in the alternation definition to make it a bit less ambiguous when talking about the OR statement, along with fixing minor grammar.

@josh-byster 👍


leverage: add direct_liquidation_penatly param

This global parameter will reduce effective liquidation_incentive when receiving base tokens directly instead of uTokens.
For example, direct_liquidation_penatly = 0.2 and liquidation_incentive = 0.1 would result in a liquidator repaying $100 of borrows having the option of receiving $110 worth of uTokens or $108 worth of base tokens in a given liquidation.

Oops, duplicate of #1158


Binary Compatibility Validator

Description
We would like to use the Binary Compatibility Validator Gradle plugin for checking the binary compatibility of Kotools Assert.
Dependencies
This issue is blocked by the following ones:

[x] #35

Checklist

[ ] Add the Gradle plugin.
[ ] Dump the public API binaries.
[ ] Update the Unreleased section in changelog.

The Kotools Assert project will be archived.
We recommend to use the testing library provided by Kotlin instead.


[Access Request] page 1286 "Payment Rec Match Details" - Global Variables Access

Hi,
Could you please make global variables in the page to be protected? We need to recalculate them using different "Account Type" and show correct ones.
RelatedPartyMatchedText
AmountMatchText
DocumentMatchedText
DirectDebitMatchedText
DirectDebitMatched
NoOfLedgerEntriesWithinAmountTolerance
NoOfLedgerEntriesOutsideAmountTolerance
RelatedPartyMatchInfoText
RelatedPartyMatchInfoEnabled
DocumentMatchInfoText
DocumentMatchDetailsEnabled
#11702 hasn't shipped yet.

This is already done for 19.0.


cmake: add gni build

Some places use gni-* (with asterisk) followed by mpi-crayx with the MATCHES operator, while others use gni- (no asterisk) and -crayx. Could it be made consistent?

Good point, should be fixed now.


Merging with PureScript?

Hi @osa1. I was wondering if you'd be interested in adding this into the compiler as a supported backend, now that backend support has improved in the compiler (by pulling out inline JS from the source files into external JS modules).
Thanks!

Hi @paf31,
I'd love to see psc-lua merged, but I'm not a PureScript user anymore(working on different things now) and I may not have enough cycles to maintain, update and debug it.
IIRC last time we were having some problems with RTS/stdlib code written in JS. Do we have a way to implement those in different languages for different backends now? Also, how much did the IR(AST types etc.) changed?
Depending on how much the IR changed, merging may be easy and I'm willing to spend some weekends to merge this, but we may need a maintainer for the rest :)

Ok, thanks for getting back to me. I'll see if we can find a maintainer long term. I don't think the IR has changed very much, but it's definitely changed. And yes, all JS has been moved out of the .purs files now into external .js files, with the goal of supporting new backends, so I think it should be easy to add .lua files for core modules we wanted to support in Lua.

Any updates on this? I'm very excited :)

@ajnsit The project is abandoned, I'm doing different things now and I don't have time and motivation to work on this. Feel free to fork, or I can give you push access if you want that. Also, if you have questions I can try to answer.

Okay, thanks for letting me know. I'm only getting started with purescript so I'll just keep digging into psc-lua on my own right now. If something significant comes out of it, I'll definitely ask for help.


Exceptions are printed out too verbosely

From @tgs on March 21, 2011 17:5
The stack trace doesn't have anything to do with the actual test failure:

===== Test Case Failure =====
Location: /home/tgs/multi-lib/data-analysis/cevent/cevent_relative_intervals.m
Name:     cevent_relative_intervals

/home/tgs/src/xunit-git/xunit/DocTest.m at line 203
/home/tgs/src/xunit-git/xunit/DocTest.m at line 100
/home/tgs/src/xunit-git/xunit/TestSuite.m at line 85
/home/tgs/src/xunit-git/xunit/TestSuite.m at line 85
/home/tgs/src/xunit-git/xunit/TestSuite.m at line 85
/home/tgs/src/xunit-git/xunit/runtests.m at line 126

DocTest #4 from cevent_relative_intervals failed; expected first, got second
Inputs are not equal.

First input:
ans = 1 10 1 21 21 2 81 85 3

Second input:
??? Error using ==> cevent_relative_intervals at 76 The WHENCE argument must be either 'start' or 'end'.

Copied from original issue: psexton/matlab-xunit#1

From @tgs on March 21, 2011 17:27
Grr.  The stack field of MException is read-only.  Hard to work around that.

From @tgs on March 21, 2011 17:32
Might be able to edit filterStack in TestRunDisplay.m to fix this.

From @tgs on April 22, 2011 20:29
OK, so:

The stack field of MException is very thoroughly read-only, not even child classes can change it.
DocTests have a different sort of stack than regular unit tests

So I think the best option is to change how the stack is printed depending on whether the test is a doctest or a unit test.
What I want:

If the doctest actually threw an unexpected exception, print the stack trace from that.  But that should probably be filtered so the DocTest runner isn't in it.

From @tgs on April 22, 2011 20:34
Yet another option would be to:

filter DocTest stuff from the exception stack
make the message string in the assertEqual at xunit/DocTestCase.m:202 be super long and descriptive, with a link and everything


Easier to read README w/ JS syntax highlight

You can make your code snippets easier to read using github's markdown. :-)

Thank you.


[DPE-3136][DPE-3137] Migrate to poetry dp workflows and secrets

This PR is built on top of backup as it will expand backup testing to cover AWS and GCP, using the secrets management mechanisms in data-platform-workflows.
It should be seen as a follow-up from https://github.com/canonical/opensearch-operator/pull/135 and https://github.com/canonical/opensearch-operator/pull/137
Following changes will also be added:

Add test coverage for AWS+GCP
List backup action should print backup-type as either full or partial instead of physical
Remove workaround: https://github.com/canonical/opensearch-operator/blob/main/requirements.txt#L18

Closing this PR in favor of #157.


V2.3,How to view the server log and where the log is stored?

V2.3,How to view the server log and where the log is stored?.

@mdjs147 Information about managing logs was added to the 2.4 documentation, but it should still apply to 2.3: https://docs.influxdata.com/influxdb/v2.4/admin/logs/

@sanderson How to configure under Windows？

The same principles in that doc apply to windows. influxd outputs all logs to stdout, so the output of the influxd process is the server log stream. Redirecting stdout to a file depends on how you're starting influxd. If you're doing it in PowerShell, it'd be something like:
C:\Program Files\InfluxData\influxdb 1> /path/to/influxdb.log

You can find more information about redirecting Windows log output in the Microsoft documentation.

thank you


i18n(ja): Update nav.ts

Description (required)

Update nav.ts.

Related issues & labels (optional)

Suggested label: i18n

Lunaria Status Overview
🌕 This pull request will trigger status changes.

Learn more
By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.
You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

Locale
File
Note

ja
nav.ts
Localization changed, will be marked as complete.

Warnings reference

Icon
Description

🔄
The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.


NameError in admin/communication/blocks#update

Error in Osuny
NameError in admin/communication/blocks#update
uninitialized constant Communication::Block::Heading
can :manage, Communication::Block::Heading, university_id: @user.university_id
                                 ^^^^^^^^^

View on Bugsnag
Stacktrace
app/models/ability/admin.rb:53 - admin_communication
app/models/ability/admin.rb:8 - initialize
app/models/ability.rb:7 - new
app/models/ability.rb:7 - for
app/controllers/application_controller.rb:27 - current_ability
app/controllers/application_controller/with_locale.rb:19 - switch_locale

View full stacktrace
Created automatically via Bugsnag

An error linked to this issue has been marked as fixed in Bugsnag
NameError in admin/dashboard#index


chore: further cleanup of norm_num

The main change here is to split NormNum.Core into NormNum.Result and NormNum.Core. Other than that split it is just moving small declarations to better homes.

Thanks :tada:
bors merge

bors p=10


Homepage overhaul

This PR changes the typography and layout of the word of the day section to look...better. It also moves the about page content to the homepage as per the designs, which allows us to get rid of the app menu and about activity.
I was pleasantly surprised how easily I could add a test that not only asserted that the webview was rendered, but also that it had the expected content.

Note: I'm not sure why the word of the day is so small - based on the layout, it shouldn't be. I'm waiting for a new word of the day, just in case it's an image with heaps of whitespace around it.

With spacing adjusted:


minor updates to README.md; removed dead link to credits and an unnec…

…essary period
added a line to run the checks...
Signed-off-by: Mark Cohen<EMAIL_ADDRESS>Description
[Describe what this change achieves]
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed as per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #69 (81080b8) into main (d654ad6) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##               main      #69   +/-   ##
=========================================
  Coverage     65.52%   65.52%
  Complexity      172      172
=========================================
  Files            29       29
  Lines           879      879
  Branches        119      119
=========================================
  Hits            576      576
  Misses          254      254
  Partials         49       49

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

Close this PR since the backport one merged


ci: update action-pre-commit to v2

Description
Update action-pre-commit to v2.
Changes

ci: update action-pre-commit to v2

🚀 PR created with fotingo

@joonchrislee It looks like the CI isn't currently passing on this repo.  Do we need to do anything to get it running again?


Correct TRL

This PR corrects the TRL in the blog post and in the FAQ entry.
Closes #765

Internal Tracking-ID: EXPOSUREAPP-4529

Reviewers: @tklingbeil & @HannaHei
Asignee: @HannaHei
Maybe you could add them (again) @dsarkar? Thank you! ❤

Reviewers: @tklingbeil & @HannaHei
Asignee: @HannaHei
Maybe you could add them (again) @dsarkar? Thank you! ❤

This PR drives me crazy, please stand by a moment

This PR drives me crazy, please stand by a moment


jskeus: 1.2.1-1 in 'kinetic/distribution.yaml' [bloom]

Increasing version of package(s) in repository jskeus to 1.2.1-1:

upstream repository: https://github.com/euslisp/jskeus
release repository: https://github.com/tork-a/jskeus-release.git
distro file: kinetic/distribution.yaml
bloom version: 0.8.0
previous version for package: 1.2.1-0

jskeus
* .travis-osx.sh: need install make by brew (#535 <https://github.com/euslisp/jskeus/issues/535>)
* try to run more irt tests on arm machine (#533 <https://github.com/euslisp/jskeus/issues/533>)
  * ubuntu_arm64:trusty takes more than 50 min, so skip irteus-demo.l
  * irteus/nr.c: check rv1/w/f + anorm == anorm with eusfloat_t type
  * irteus/{irtc.c,nr.c}: use double for nr codes
  * irteus/irtutil.l interpolator :pass-time : calculate segment-time from time minus previous time-list, (incf segment-time dt) accumulate errors, specially 32bit machine
  * irteus/test/test-irt-motion.l: run all test with compiled code
  * irteus/test/geo.l: (body+ c1 b d1 c2 d2 c3 d3 c4 d4) could not pass the test on arm 32bit, use truncated version
  * irteus/test/geo.l somehow both 32/64 arm architecture needs to return #f(0 0 0) for small normalized vectors
  * irteus/test/mathtest.l: 9.656790+06 is too large for 32bit machine
  * irteus/test/mathtest.l: add test for pseudo-inverse2 to check if svdcmp failed to converge
  * irteus/test/test-pointcloud.l To test test-pointcloud.l with compiled code requires https://github.com/euslisp/EusLisp/pull/357
* [irtmodel.l]fix bug of :angle-vector for multi-dof joint (#532 <https://github.com/euslisp/jskeus/issues/532>)
  * add test code to check bug of :angle-vector for multi-dof joint #529 <https://github.com/euslisp/jskeus/issues/529>
  * add more test on min-max-joint-table (#534 <https://github.com/euslisp/jskeus/issues/534>)
* travis.{yml,sh}: set travis to fail when gcc outputs compile warnings (`#527 <https://github.com/euslisp/jskeus/issues/527>`_e)
* [irteus/irtviewer.l] support changing floor color. (#528 <https://github.com/euslisp/jskeus/issues/528> from mmurooka/floor-color
  * [jskeus/doc] add irtviewer.tex and figures for irtviewer manual.
  * [irteus/irtviewer.l] add :draw-origin, :draw-floor, and :floor-color.
  * [irteus/irtviewer.l] support changing floor color.
* remove all compile warning (#526 <https://github.com/euslisp/jskeus/issues/526>)
  * add -DLinux to Makefile.LinuxARM
  * enable debian_arm64:stretch
  * add WFLAGS to Makefile
  * remove all compile warning for eus0
* .travis.yml: add debian:stretch test (#525 <https://github.com/euslisp/jskeus/issues/525>)
  * Fix the compile on Debian stretch. #524 <https://github.com/euslisp/jskeus/issues/524>
  * set debian_arm64:stretch allow_failures
  * Fix the compile on Debian stretch.Must like the comment above says, gcc 6 on Debian
  Stretch doesn't like redefining sin, cos, etc and throws
  an error.  Fix this problem by not redefining on Debian Stretch.
* [irtrobot.l] check if target coords is function or coordinates, also work if target coords is list of functions. (#503 <https://github.com/euslisp/jskeus/issues/503>)
  * [irteus/irtmodel.l] Add :xm :ym :zm comment for rotation-axis keyword-argument.
  * [irtrobot.l] allow to use both list and atom of function(s) for target-coords, Fixed #476 <https://github.com/euslisp/jskeus/issues/476>
* add test with compiled lisp (#522 <https://github.com/euslisp/jskeus/issues/522>)
  * .travis.sh: add compiled test
  * remove do-until-key x/10 message, debug (print r) code
  * test/robot-model-usage.l : reduce output message for travis
  * test/irteus-demo.l : reduce output message for travis
  * test/irteus-demo.l: use debug-veiw nil to reduce output message
  * test/full-body-ik.l: add debug-view option
  * test/geo.l: test-body+ test-vector-angle needs irteus to avoid 'outer circuit not found' and 'undefined function c-isnan
  * test/matrix.l  : c-isnan test, disable test-matrix-concatenate-noargs,test-matrix-concatenate-single-matrix,test-matrix-concatenate-multiple-matrices becaues of 'undefined function concatenate-matrix needs irteus
  * test/mathtest.l : diagnoal, minor-matrix, atan2, outer-product-matrix, quaternion, matrix-log, pseudo-inverse, sr-inverse, manipulability, eigen decompose, sv/ql solve, lu-solve2, matrix-determinant, qr/ql-decompose needs irteus
  * test/coords.l : test-makecoords-quaternion needs quaternion2matrix defined in irteus
  * remove test codes which are moved to EusLisp https://github.com/euslisp/EusLisp/pull/316
  * add test with compiled lisp
  * re-define method within defun is not working with compiled code (#523 <https://github.com/euslisp/jskeus/issues/523>)do not run test code on compile, but run when load
* fix for osx and newer compiler (gcc >= 7 OR clang >=9) (#520 <https://github.com/euslisp/jskeus/issues/520>)
  * disable DISPLAY for osx
  * gcc >= 7 OR clang >=9 dislike redefinition of sqrt/cos/fin/fabs ...
  * Disable redefinition of sqrt/cos/... to avoid some errors on macOS
  * fix osx travisremove homebrew/x11, which is deprecated

  do not run brew update, because brew update compile all module from source and it takes more than 1 hour

  copy setup process from euslisp/.travis-os.sh

  do not install x11 server

  export LIBGL_ALLOW_SOFTWARE=1 suggested by https://api.travis-ci.org/v3/job/403422947/log.txt

  make -j with 2

  add exit 0 end of .travis-osx.sh

  run as script, instead of source
* [doc] Add example when IK target-coords function introduced in #514 <https://github.com/euslisp/jskeus/issues/514> (#518 <https://github.com/euslisp/jskeus/issues/518>)
  * Add sample of ik using functional target-coords
* Contributors: Chris Lalancette, Guilherme Affonso, Kei Okada, Kentaro Wada, Masaki Murooka, Naoki Hiraoka, Iori Yanokura

this will fix current kinetic sync regression on http://build.ros.org/view/Kbin_uX64/job/Kbin_uxv8_uXv8__roseus__ubuntu_xenial_arm64__binary/ due to the same issue we had yesterday
https://github.com/ros/rosdistro/pull/21516#issue-287315266


bug: Cody 1.10, VS Code 1.87.2, Python extension 2024.2.1, "No symbols found (try installing language extensions)"

Version
1.10
Describe the bug
Cody chat reports symbols cannot be found when trying to include them through '@#'. Meanwhile, Cody 'Edit Code'  input dialog appears to have access to symbols (lists and searches found symbols), but testing indicates they are not included in context. Using VS Code 1.87.2, Python extension 2024.2.1.

Expected behavior
The symbol inclusion function through  '@#' should function as intended for Python.
Additional context
No response

The symbols began populating once text is entered and are included in context. It might be the case I was previously confused by poor responses caused by issues on LLM side. In any case, the bug report is no longer valid.


Update to use cypress instead of storybook

Nobody is using storybook any more, make this a cypress test.

Cool! (BTW, do you use a paid account for Cypress?)

We have a free education license (or open source license? Don't remember) for cypress cloud, which hooks up to GH actions to display test results. Cypress is free for running locally

Cool. Is that a lab level account. I.E., if I'm using it for common sense, should we use the same one?


Update to include latest RFCs (8xxx)

Hello!
This looks like an awesome contribution but was missing some of the latest RFCs (7797 was the specific one I was after) so as per the instructions in the readme I'm asking you to update it :)

Hi @willnorris! I was very pleased to find that this docset existed. Any chance you can update it to include the later RFCs — I'm after 7643.
I'd be happy to fork and update it, if you don't have the bandwidth.

Thanks.  I actually put together a new update recently, but didn't quite get it finished.  Also, the last time I tried to push an update, apparently I had some other errors that I haven't had a chance to investigate yet.  I'll try to do this again this weekend.

Hi @willnorris, thank's for RFCs docset. Should you update it, please? For me important RFCs are for IPV6 Internet standard 8200-8201. Last is 8212.
Thank's

Updated up to 8335


Long stage names cause a line break in stage tag on the sequence screen

Status quo
When having multiple stages and long names, a line break happens in the "bubbles" on the sequence screen:

Style improvements

Introduction of max length to deal with long sequence names
Displaying just 3 stages and hiding the others behind a y more ... label.

DoD

[ ] Names are shortened to fit without breaking the line and have ... as a suffix
[ ] Tooltip on hover shows the full (long) stage name
[ ] Consider the case of too many stages that do not fit in the sequence view

Resolved with #8524