[Unification] Move all encoders/transformers to models folders

Stack from ghstack (oldest at bottom):

#253
#249
#248
#244
#243
#240
-> #239

Differential Revision: D38506859
Summary
Move all model specific encoders and transformers from modules/encoders/ and modules/layers/transformer.py to their corresponding model specific folders, following the naming convention models/<model_name>/<modality>_encoder.py. The encoders folder will remain for general use encoders.
Test plan
pytest -vv

Codecov Report

:exclamation: No coverage uploaded for pull request base (gh/RdoubleA/28/base@852a347). Click here to learn what that means.
The diff coverage is n/a.

@@                  Coverage Diff                   @@
##             gh/RdoubleA/28/base     #239   +/-   ##
======================================================
  Coverage                       ?   93.25%
======================================================
  Files                          ?       49
  Lines                          ?     2963
  Branches                       ?        0
======================================================
  Hits                           ?     2763
  Misses                         ?      200
  Partials                       ?        0

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

there should be a change in the CLIP import statement in videoclip.
also maybe test/models/albef/test_albef.py should be renamed to test/models/albef/test_model.py (and similar change for clip and flava) since the model is now at model.py?

Looks good overall. One question: why are the architecture tests getting moved around in this PR?

those tests should've been moved already in an old PR but they weren't for some reason, so I just went ahead and did it in this PR

@RdoubleA has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.

@RdoubleA has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.

@RdoubleA has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.

@RdoubleA has imported this pull request.  If you are a Facebook employee, you can view this diff on Phabricator.


does Multipart support push_back file content(buff)

filename is filepath,
one case:
the file content has read in the memory,how does use Multipart push content and send,

No, it doesn't support that

FYI, PR #129 adds support for this.


How to debug utilsScript?

I created a Brocfile.js with the recommended contents. My ember-cli app builds and runs without errors, but utils.js is not loaded (nor is it present in /dist). Is there another requirement I am missing?
Server output:
version: 1.13.1
Could not find watchman, falling back to NodeWatcher for file system events.
Visit http://www.ember-cli.com/#watchman for more info.
Livereload server on http://<IP_ADDRESS>:35729
Serving on http://<IP_ADDRESS>:4200/
Build successful - 4279ms.
Slowest Trees                                 | Total
----------------------------------------------+---------------------
Concat: Vendor                                | 3292ms
Slowest Trees (cumulative)                    | Total (avg)
----------------------------------------------+---------------------
Concat: Vendor (1)                            | 3292ms
Babel (3)                                     | 277ms (92 ms)
Content Security Policy violation: {"csp-report":{"document-uri":"http://<IP_ADDRESS>:4200/","referrer":"http://<IP_ADDRESS>:4200/","violated-directive":"script-src 'self' 'unsafe-eval' localhost:35729 <IP_ADDRESS>:35729","effective-directive":"script-src","original-policy":"default-src 'none'; script-src 'self' 'unsafe-eval' localhost:35729 <IP_ADDRESS>:35729; font-src 'self'; connect-src 'self' ws://localhost:35729 ws://<IP_ADDRESS>:35729 http://<IP_ADDRESS>:4200/csp-report; img-src 'self'; style-src 'self'; media-src 'self'; report-uri http://<IP_ADDRESS>:4200/csp-report;","blocked-uri":"http://<IP_ADDRESS>:35729","source-file":"http://<IP_ADDRESS>:4200/ember-cli-live-reload.js","line-number":6,"column-number":43,"status-code":200}}
Content Security Policy violation: {"csp-report":{"document-uri":"http://<IP_ADDRESS>:4200/","referrer":"http://<IP_ADDRESS>:4200/","violated-directive":"connect-src 'self' ws://localhost:35729 ws://<IP_ADDRESS>:35729 http://<IP_ADDRESS>:4200/csp-report","effective-directive":"connect-src","original-policy":"default-src 'none'; script-src 'self' 'unsafe-eval' localhost:35729 <IP_ADDRESS>:35729; font-src 'self'; connect-src 'self' ws://localhost:35729 ws://<IP_ADDRESS>:35729 http://<IP_ADDRESS>:4200/csp-report; img-src 'self'; style-src 'self'; media-src 'self'; report-uri http://<IP_ADDRESS>:4200/csp-report;","blocked-uri":"ws://<IP_ADDRESS>:35729","source-file":"http://<IP_ADDRESS>:35729","line-number":74,"column-number":21,"status-code":200}}

If you have included utils.js in Brocfile.js, it will be included in
dist/vendor.js when being built. The best way to tell if it is actually
included is to inspect an {{ember-intl-tel-input}} component and see if a
placeholder exists, or whether auto formatting is working. Without the
script, neither of them works and only a blank input is displayed.
On Wednesday, July 15, 2015, Tim Greiser<EMAIL_ADDRESS>wrote:

I created a Brocfile.js with the recommended contents. My ember-cli app
builds and runs without errors, but utils.js is not loaded (nor is it
present in /dist). Is there another requirement I am missing?
Server output:
version: 1.13.1
Could not find watchman, falling back to NodeWatcher for file system
events.
Visit http://www.ember-cli.com/#watchman for more info.
Livereload server on http://<IP_ADDRESS>:35729
Serving on http://<IP_ADDRESS>:4200/
Build successful - 4279ms.
Slowest Trees | Total
----------------------------------------------+---------------------
Concat: Vendor | 3292ms
Slowest Trees (cumulative) | Total (avg)
----------------------------------------------+---------------------
Concat: Vendor (1) | 3292ms
Babel (3) | 277ms (92 ms)
Content Security Policy violation: {"csp-report":{"document-uri":"
http://<IP_ADDRESS>:4200/","referrer":"http://<IP_ADDRESS>:4200/","violated-directive":"script-src
'self' 'unsafe-eval' localhost:35729 <IP_ADDRESS>:35729","effective-directive":"script-src","original-policy":"default-src
'none'; script-src 'self' 'unsafe-eval' localhost:35729 <IP_ADDRESS>:35729;
font-src 'self'; connect-src 'self' ws://localhost:35729 ws://
<IP_ADDRESS>:35729 http://<IP_ADDRESS>:4200/csp-report; img-src 'self';
style-src 'self'; media-src 'self'; report-uri http://<IP_ADDRESS>:4200/csp-report;","blocked-uri":"http:/
/10.0.1.
245:35729","source-file":"http://<IP_ADDRESS>:4200/ember-cli-live-reload.js","line-number":6,"column-number":43,"status-code":200
http://<IP_ADDRESS>:4200/csp-report;","blocked-uri":"http://<IP_ADDRESS>:35729","source-file":"http://<IP_ADDRESS>:4200/ember-cli-live-reload.js","line-number":6,"column-number":43,"status-code":200
}}
Content Security Policy violation: {"csp-report":{"document-uri":"
http://<IP_ADDRESS>:4200/","referrer":"http://<IP_ADDRESS>:4200/","violated-directive":"connect-src
'self' ws://localhost:35729 ws://<IP_ADDRESS>:35729
http://<IP_ADDRESS>:4200/csp-report","effective-directive":"connect-src","original-policy":"default-src
'none'; script-src 'self' 'unsafe-eval' localhost:35729 <IP_ADDRESS>:35729;
font-src 'self'; connect-src 'self' ws://localhost:35729 ws://
<IP_ADDRESS>:35729 http://<IP_ADDRESS>:4200/csp-report; img-src 'self';
style-src 'self'; media-src 'self'; report-uri
http://<IP_ADDRESS>:4200/csp-report;","blocked-uri":"ws://<IP_ADDRESS>:35729","source-file":"http://<IP_ADDRESS>:35729","line-number":74,"column-number":21,"status-code":200
http://<IP_ADDRESS>:4200/csp-report;","blocked-uri":"ws://<IP_ADDRESS>:35729","source-file":"http://10.0.1. 245:3572 9","line-number":74,"column-number":21,"status-code":200
}}
—
Reply to this email directly or view it on GitHub
https://github.com/justin-lau/ember-intl-tel-input/issues/3.

'utils.js' is not included in dist/vendor.js and blank input is displayed.
My Brocfile.js contains nothing but the snippet from the docs:
var app = new EmberAddon({
intlTelInput: {
includeUtilsScript: true, // default to false
},
});

Interesting, never found this happened. Can you confirm you have module.exports = app.toTree(); at the bottom of the file? Also could you please post the versions of your ember and ember-cli?

As of ember-cli 1.13.0:
Brocfile.js has been deprecated in favor of ember-cli-build.js. See: TRANSITION.md
Here is my working ember-cli-build.js
var EmberApp = require('ember-cli/lib/broccoli/ember-app');

module.exports = function(defaults) {
  var app = new EmberApp(defaults, {
    // Add options here
    intlTelInput: {
      includeUtilsScript: true,
    },
  });

  return app.toTree();
};

Thanks for the update. Apparently there is a bug in ember-cli v1.13.1 that prevents options to get merged. This addon won't update its ember-cli version until this problem is fixed, in v1.13.2.

I think this issue has been solved with the v1.2.0 update I published a moment ago. I'm closing this issue for now, but feel free to bring this up again if the problem persists.


Adding AlmaLinux

I'm hoping I did things right here! Happy to take feedback if I need to adjust anything.

@ShaneCurcuru Good catch on both of those! Can you tell I was finding examples in other listings to help? :D This push should fix them both, I think.


Missing NODE_ENV in build script

process.env.NODE_ENV is defined on client side only (ref https://github.com/MoOx/statinamic/blob/51023e293d674ad49d30e39b9925769389f575cc/docs/scripts/webpack.config.babel.js#L92-L94)
On static build, process.env.NODE_ENV === undefined . So we need to set NODE_ENV in build script

Good catch.

Fixed on "next" branch. I did not release immediately as a patch since stylelint 4.3.0 is "broken" (https://github.com/stylelint/stylelint/pull/737)

Stylelint 4.3.2 is out.


Disambiguate "OSI Approved :: BSD License"

What's the problem this feature will solve?
Currently, the classifiers allow to declare a software licensed under "BSD License".
Other frameworks like SPDX offers BSD-2-Clause and BSD-3-Clause, the two most used "BSD" licenses.
This ambiguity have impact to automated external tools: I've uploaded a package licensed under BSD-2-Clause, and external service libraries.io offers to generate a machine-readable properties file offering license_spdx: BSD-3-Clause.
Describe the solution you'd like

"OSI Approved :: BSD License"
"OSI Approved :: BSD License (3-Clause)"
"OSI Approved :: BSD License (2-Clause)"

Additional context
https://en.wikipedia.org/wiki/BSD_licenses#Terms details the different n-Clause

Duplicate of https://github.com/pypa/trove-classifiers/issues/17.


Rework stat saving

This PR adds a simple stat saving system replacing the old broken one.

I made this a draft since I've just realized we need to somehow detect when the statistics reset to be able to load them properly.


FetchMultiple does not seem to have an async option?

All other data retrieval operations in NPoco support async, but this method doesn't seem to have any async support.  Why is that?

From v5 alpha-5


Remove single space from h-entry/urlincontent test

As can be clearly seen in the html property of content, there are exactly 8 spaces between the \n and the start of the <img>. For some reason the plain text output was showing 9 spaces. Removed one.

Closing, this was actually a bug in the pre-2018-03-29 code of the PHP parser (re-introduced for test running in https://github.com/microformats/php-mf2/pull/163/commits/c2bbd9fcdfec3a22d96eb11d0908163c41845f59). Hopefully patched correctly in the testing branch per https://github.com/microformats/php-mf2/pull/163/commits/d5a8f850e421017b367552ec899f0e14af72f500.
Thanks for the sanity check @jgarber623 👍


Make redis configuration environment-aware

To create an AMI to run the redis EC2 instance, the redis container will need to be able to source some configuration values from its environment.

[x] Make a list of all configuration options that are environment-dependent
[x] Create one or multiple configuration files that are env aware for those options

Turns out there are no real config options that change across environments, if it uses the default port.


pew cannot be used as user

Installing virtualenv as user (pip install --user virtualenv) does not create the virtualenv command, so pew does not work. Maybe better to call python virtualenv.py args instead of virtualenv args?
Another solution (French): http://scylardor.fr/2013/06/09/zsh-command-not-found-virtualenv/

I'm not sure what's the issue there. If you install a package as user, it's stored in ~/.local. As such, it is normal to put ~/.local/bin in your PATH – that's the standard procedure. Doing so will make the virtualenv command available.

You're right, but maybe there is a simple solution to make it work automatically for noobs?

Some installers might append the export PATH="…:$PATH" stuff into .bashrc, but if you ask me, I hate software that messes with my dotfiles without notice.

You're right, but maybe there is a simple solution to make it work automatically for noobs?

Most modern Linux distributions add ~/.local/bin to the user $PATH by default.
Please ask your distribution to do the same.

Looks like that best solution for virtualenv problems is to call it as module:
python -m virtualenv ...

or in python code replace:
check_call(["virtualenv", ...])

with:
check_call([sys.executable, '-m', "virtualenv", ...])

I don't think we will mess with your path by default.  Closing as will not fix

Ok. As you wish. I just want to note that the problem with virtualenv is much wider than specified by current issue. Have you any justified arguments against my solution? I am just interested in. It is quite simple and will solve a lot of cases. I can provide you a bunch of examples where pew is currently fails, though can work with very simple fix described above.

@apatrushev Apologies, but I don't think our program should make changes to the PATH.  If you want to implement a fix you can submit a PR!  I'll let @berdario weigh in on this, but for now will leave it closed :)

@erinxocon Did you read my comment at least? I did not propose to make any changes in the PATH.

@apatrushev I did not, apologies was looking at this on mobile, I'll look into this.  If you know how to fix it feel free to submit a PR!

The check_call([sys.executable, '-m', "virtualenv", ...]) fix seems to be quite simple
not sure why it has never been done before. Maybe this only works when virtualenv's location is in sys.path, and usually sys.path inherits from PATH. Thus I assumed that in almost no cases it would be possible to import virtualenv without having the virtualenv executable available
(I'm in a bit of a rush, so I haven't yet tried to do a pip install --user virtualenv )
Thanks!

That might actually also fix #102. 😄

@bochecha That was exactly what I said above - in fact there are lots of cases where "module call" of virtualenv is much more stable and predictable than simple executable call.


Fix config structs initialization in injector

Description of the Change
useConfig function was implemented incorrectly and passed configs to the injector by lvalue reference, which, given they were temporary objects, led to them being initialized by random trash from memory.

Benefits
Correct behaviour.

Possible Drawbacks
No more fun bugs.

Look at Jenkinks CI error


Run guardrail test scripts after the LZ0 and LZ1 upgrade

Describe the issue
I want to verify if the results returned be my test scripts change, and they change, what exactly changes
Applies to LZ0 and LZ1
Additional context
Run this test after running #1811 and the SEA upgrade
Use of AWS CLI with workload account credentials and with Admin credentials
Definition of done
Run the guardrail test scripts, they are pretty simple. Analysis of the results can be done later

It applies to LZ0 and LZ1.
This test will became a baseline for the following upgrade to compare

LZ0 is done.
LZ1 had not been done yet (Aug 15, 2022). The reason is that the License Plate creation  scripts have not been updated and they are still deploying Sandbox environment instead of Tools.
Once they have been deployed, I will be able to run my scripts and create a snapshot for LZ1 with a license plate that includes the tools environment (reminder that a license plate string and then environment string define an account, and the account can have on or more roles associated to it)

Results stored in
https://bcgov.sharepoint.com/:f:/t/01368-CPFScrumTeam/ElqQ897Z3JRKuuw14-UJu9cBrUXMcoNpOX9rBp9tIxUnFA?e=KNk0Rw.  --> LZ0
https://bcgov.sharepoint.com/:f:/t/01368-CPFScrumTeam/EtaruDOVJtxGvTK5CEtVyyYBIN6Qdu3mv9VW5iSKjqOoHg?e=IeS50K --> LZ1


chore: Add CODEOWNERS file

Adding a CODEOWNERS to the repo. We only have a default owners section for now and no separate owners for different components.

Closing this for now as we decided to try an alternative option. Will re-visit later.


nuttx/fs:Rename node with inode.

Summary
In fs/inode directory, the variable name FAR struct inode *node is named inconsistently, with some using node and others using inode. To facilitate understanding, we will standardize the naming to FAR struct inode *inode.
Impact
Testing

[Experimental Bot, please feedback here]
I need the actual content of the Pull Request (PR) to determine if it meets the NuttX requirements. Please provide the following:

The PR's description:  This is where the most important information about the changes resides.
The code changes:  A link to the PR on GitHub would be ideal, or at least a description of the files changed and the nature of the changes.

Once you provide this, I can help assess if the PR meets the NuttX requirements for clarity, completeness, and testing.

@cuiziwei1 please add a commit message to the commit

@cuiziwei1 please fix ci error.


imapnotify: add service

Adds a module for configuring and managing a systemd user unit for imapnotify.

Here's a usage example with gmailieer already set up:
    imapnotify = {
      enable = true;
      settings = {
        host = "imap.gmail.com";
        port = 993;
        tlsOptions = { rejectUnauthorized = false; };
        username = "<redacted>";
        passwordCmd = "${pkgs.pass}/bin/pass gmail";
        onNotify = "cd $HOME/.mail/account.gmail && ${pkgs.gmailieer}/bin/gmi sync";
        onNotifyPost = { mail = "${pkgs.notmuch}/bin/notmuch new && ${pkgs.libnotify}/bin/notify-send 'New mail arrived'"; };
        boxes = [ "Inbox" ];
      };
    };

Thanks for the contribution!
It seems to me that this should be integrated into the HM email infrastructure. I.e., the user should not configure the IMAP hostname, port, etc. directly in this module.

@rycee I've done as requested; also, I've made it so that you can configure imapnotify on a per-account basis. To use, in the account section, configure with accounts.email.accounts.myaccount.imapnotify, making sure to set enable = true;, and also set services.imapnotify.enable = true;. A word of caution: when this service is enabled, and used in conjunction with pass, it will fail to start on login as the gpg-agent hasn't cached the key needed to decrypt the password in passwordCommand, like so
-- Logs begin at Thu 2019-01-17 00:08:08 GMT, end at Sun 2019-04-14 19:51:56 BST. --
Apr 14 19:44:43 mu systemd[1547]: Started Execute scripts on IMAP mailbox changes (new/deleted/updated messages) using IDLE for <snip>.
-- Subject: Unit UNIT has finished start-up
-- Defined-By: systemd
-- Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit UNIT has finished starting up.
--
-- The start-up result is RESULT.
Apr 14 19:44:44 mu imapnotify[1560]: gpg: decryption failed: No secret key
Apr 14 19:44:44 mu imapnotify[1560]: {"name":"imap_inotify","hostname":"mu","pid":1560,"level":50,"msg":"Parsing error: config file must be in JSON format or a valid JS module: Error: Command failed: /nix/store/l4nlwzyvihc8z0ibzs189mmas9pj7hdb-password-store-1.7.3/bin/pass <snip>\ngpg: decryption failed: No secret key\n","time":"2019-04-14T18:44:44.916Z","v":0}
Apr 14 19:44:44 mu systemd[1547]<EMAIL_ADDRESS>Main process exited, code=exited, status=3/NOTIMPLEMENTED
Apr 14 19:44:44 mu systemd[1547]<EMAIL_ADDRESS>Failed with result 'exit-code'.

Perhaps this could be ameliorated with some sort of gpg-agent systemd target.

I made the changes you requested, but I still get the same gpg problems. I'm working around it in my setup by just restarting the service after I've unlocked the secret key.

I had a look again and made a few random fixes, please give it a try and if you like it I'll merge it to master.
A thing I was wondering what whether this actually need a running X session? I had a look at the ImapNotify website and it mentions a tray…

Thanks @rycee, I'll give it a test later. I shouldn't think it might require X, as far as I'm aware there is no tray. It's just a small script that opens a socket, does auth, and runs a callback on IMAP events

I had a look at the ImapNotify website and it mentions a tray…

Is it possible we're talking about two different projects both called imapnotify? I noticed also you changed a bunch of imapnotify → ImapNotify, but I don't see it written like that anywhere here.

Ah, doh! I was looking at https://sourceforge.net/projects/imapnotify/ 🙂

I'm more or less happy with this, except for the gpg thing - any other ideas on how to resolve this?

Thanks! Rebased to master in 2f819d1647d4c73aad6ca8fec8348beaae4bb870.
I'm not entirely certain how to make it work better with gpg-agent, but figured that it might as well be merged and some solution can be added later.

@rycee Just one last thing, I meant to commit this before the pr was merged, but it's only a small change anyway: the systemd unit should probably set Environment=NOTMUCH_CONFIG=$XDG_CONFIG_HOME/notmuch/notmuchrc (or however it's supposed to be set), since the programs called by imapnotify (most likely notmuch new) in its hook inherit its shell.


Update README.md

Updated the README to showcase the latest features introduced in the latest release. The content has been optimized for SEO to increase visibility and reach. Additionally, the language has been refined for greater clarity, making it easier for users to understand the functionalities and benefits of the package.

:books: Documentation preview :books:: https://pymc-marketing--418.org.readthedocs.build/en/418/

You need to run the linter locally (see failing test)

Maybe where we talk about free consultation we can also add that there is professional support available.

@nialloulton I did some minor restructuring directly, see what you think.

Thanks @nialloulton!


Pin libkml to conda-forge.

Packages have recently changed on defaults and conda-forge, from various ones being labelled 'broken' on conda-forge, to new versions on both. The result is that defaults is now being chosen - at least on linux - also bringing in various other dependencies such as libboost from defaults.
See note in dependencies.txt for full explanation.

@jbednar : another post-merge change to check, thanks


[FLOC-4248] Cloudformation stub script

Fixes: https://clusterhq.atlassian.net/browse/FLOC-4248

Moved the body of the cloudformation.py script into a main function
Moved and simplified the argparse code so that I can easily add new options.
Removed the existing functional tests. We really only need to run unit tests on the argparse options but even those tests seem unnecessary at this stage.
Updated docs

This looks reasonable. I have a couple of minor suggestions about the interface to generating the template. Please address and merge.


Fix typo

This PR fixes a typo, which seems to be included only once across the documents.
No related issues to close, and decided to skip opening one due to perceived unnecessary overhead (but let me know if you prefer that way).
Please review and either merge, or let me know how to further improve it.

Cool with no issue on this. Could you also add yourself to the contributors list? https://github.com/Minimum-CD/cd-manifesto/blob/master/data/names/contributors.yml

Thanks for the reminder, @bdfinst, I'm already in the contributors list ;)


Do not fail by warnings when building docs

CuPy counterpart for https://github.com/chainer/chainer/pull/4037 and https://github.com/chainer/chainer/pull/6417
Merge chainer/chainer-test#500 first.

LGTM
Jenkins, test this please.

Jenkins CI test (for commit d098783437eb7cfecd0fcd90abc81fa6b62d04a9, target branch master) failed with status FAILURE.
(For contributors, please wait until the reviewer confirms the details of the error.)


Add the UI to the webpage

Description:  Add a link to to the UI to the website landing page

Can @instructlab/website-maintainers PTAL when you get the chance to confirm this? Thank you 🙂

@cybette Just updated that! Should be all set now

Thank you for adding this @kelbrown20 !!


Dealing with OpenWhisk sequences

OpenWhisk supports action sequences
When invoking a sequence, epsagon only records the activation-id of that sequences and it's not possible to consolidate the executed actions of that sequences with the invocation chain. when invoking the action via a http request, the reponse header only contain the activation-id of the sequence.
however, it is possible to fetch the activation afterwards, eg:
$ wsk activation  get c56f8cf4c78a46d6af8cf4c78a36d6b2
ok: got activation c56f8cf4c78a46d6af8cf4c78a36d6b2
{
    "namespace": "helix",
    "name": "word2md@v1",
    "version": "0.0.200",
    "subject": "helix",
    "activationId": "c56f8cf4c78a46d6af8cf4c78a36d6b2",
    "start":<PHONE_NUMBER>171,
    "end":<PHONE_NUMBER>961,
    "duration": 6779,
    "statusCode": 0,
    "response": {
        "status": "success",
        "statusCode": 0,
        "success": true,
        "result": {
            "body": "...",
            "headers": {
                "Cache-Control": "no-store, private, must-revalidate",
                "Content-Length": 4413,
                "Content-Type": "text/plain",
                "X-Source-Location": "..."
            },
            "statusCode": 200
        }
    },
    "logs": [
        "853430d28a894e30b430d28a89be3091"
    ],
    "annotations": [
        {
            "key": "topmost",
            "value": true
        },
        {
            "key": "path",
            "value": "helix/helix-services/word2md@v1"
        },
        {
            "key": "kind",
            "value": "sequence"
        },
        {
            "key": "limits",
            "value": {
                "concurrency": 200,
                "logs": 10,
                "memory": 256,
                "timeout": 60000
            }
        }
    ],
    "publish": false
}

The activation response contains a logs property, which are the activations executed in that sequence.
Approach 1
Epsagon fetches the activation of sequence actions in order to construct the graph of the invocations. this is rather expensive and requires the wsk token of the respective namespace.
Approach 2
A best effort approach could be to return a x-last-activation-id header in the action that is executed last in the sequence. for most of our actions, that would be enough.

:tada: This issue has been resolved in version 1.58.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


add platform info for tools

Add a way for the firmware tool to know how to build a board. Allows to maintain compatibility with new and old firmware
without changing firmware tool code.
Could also be usefull for CI

This needed a review...


Fix caching mechanism for Sagas

This PR expands the Cache interface with a  computeIfAbsent(Object key, Supplier<T> valueSupplier) method, which lazily fetches data when data is not found in the cache.
The current implementation always queries the Saga store, and puts it in the cache afterwards. The NPE experienced by a customer might be because of eventual consistency in the cache. We get it, right after we put it, so it might not have replicated yet (this depends on the configuration) and produce a null value.
This is not the case when using the new method. This will check the cache and only query for the value when necessary. In addition, it will return the produced value instead of the value in the cache, ensuring there actually is a value upon return.

As discussed offline, we (Mitchell, Allard, me) approve of this current solution.
As such, I will proceed and merge this fix.


[Bug]: Can't update dataset_ids with PUT /api/v1/chats/{chat_id}

Is there an existing issue for the same bug?

[X] I have checked the existing issues.

RAGFlow workspace code commit ID
v0.14.1
RAGFlow image version
v0.14.1
Other environment information
No response
Actual behavior
I can't update the dataset_ids when I try to update chat assistant with PUT /api/v1/chats/{chat_id}. But I can update the name or llm or other options.
I am very certain that the dataset_ids are correct, and they were all created by me.
Expected behavior
No response
Steps to reproduce
Just request with dataset_ids param.

Here is what I sent:

curl --request PUT \
     --url https://{server}/api/v1/chats/20bff9caa8c611ef9dc40242ac120003 \
     --header 'Content-Type: application/json' \
     --header 'Authorization: Bearer My-API-Key' \
     --data '
     {
          "name":"ZH Android",
          "dataset_ids":["33fcd080a8a311ef93f60242ac120003","a616581ca8a311efbed70242ac120003","033ab2aeaf1611efba670242ac120006"]
     }'

error output:
{"code":102,"message":"You don't own the dataset 33fcd080a8a311ef93f60242ac120003"}

Additional information
No response

I'm running ragflow with docker image. When can I get this update?

Run docker exec -it ragflow-server /bin/bash, apply the modification, then execute exit and docker restart ragflow-server.


Calculation of tree depth isn't working correctly

At the moment depth calculation of OutputElementTrees is calculated wrong.
At the moment each level counts 2-3 depth. The depth status altered 2-3 times per level.

Fixed - will be fixed with next release (>8.0.2)


replacer support

Hi @oderwat, made a PR here so we can discuss directly by pointing code.
Seems like the replacer interface is not usable in its current state. Sorry about that.
When reading the code, I was wondering if you could use func ()app.UI rather than a component pointer. The issue here is that the first component is mounted and overridden by the other at each update, which results in the loss of the "A" content.

Well, this works for this example. But it recreates the component each time. The components we want to switch need to keep their state while being dismounted. We talked about this before as I created the mountpoint implementation. AFAIR you wrote that you are not sure if it works when mounting/dismounting the component without destroying it. But this is what we do all the time. Without that you had all the overhead of creating the state of a component on every single tab or page switch in our apps. The other solution would be to have everything in the DOM at all times, which could be a lot of nodes. Or to have the state not inside the component and "plug" it inside every time it is switched. I wonder if that makes sense.
Let's use an example: A component that lists thousands of rows of data of an external source using different filters. It shows a partial window off them that can be scrolled through with automatic loading and disposing of elements. This is inside a page/tab in the UI. You want to keep the position, the filter and the cache of the data. You also need to manage the backend connection (for example NATS consumers). This is all inside of the component and if you re-create it, you need to recreate all of this data. When using the mountpoint I can decide for each case if I want to dispose the data and handlers on dismount or if I want to keep the internal state till the next mount of this component.


[FA] Log every task error

What does this PR do?

Log every task error even if we send it back to the backend
Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


[BUG] Stripe - Sending credit card numbers directly to the Stripe API is generally unsafe

Bug Description
Hyperswitch sends raw payment card details on create payment to the stripe api which is disabled on some newer accounts. Causing payments not to work
Expected Behavior
Would expect Hyperswitch to create a payment token from the card info, and use that in all payment api's.
https://stripe.com/docs/api/tokens/create_card
Actual Behavior
Api Request
json
{"client_secret":"pay_xxx","return_url":"https://app.hyperswitch.io/home","payment_method":"card","payment_method_data":{"card":{"card_number":"4242424242424242","card_exp_month":"04","card_exp_year":"2024","card_holder_name":"","card_cvc":"424","card_issuer":"","card_network":"Visa"}},"browser_info":{"user_agent":"Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36","accept_header":"text\\/html,application\\/xhtml+xml,application\\/xml;q=0.9,image\\/webp,image\\/apng,*\\/*;q=0.8","language":"en-US","color_depth":24,"screen_height":1331,"screen_width":2564,"time_zone":-120,"java_enabled":true,"java_script_enabled":true}}```

Api response
```json
{
    "error": {
        "type": "connector",
        "message": "No error code: Sending credit card numbers directly to the Stripe API is generally unsafe. We suggest you use test tokens that map to the test card you are using, see https://stripe.com/docs/testing.",
        "code": "CE_00",
        "connector": "stripe"
    }
}```

![image](https://github.com/juspay/hyperswitch/assets/36795828/2e8faeea-7745-42aa-a06c-c6afb79861d6)

### Steps To Reproduce

Provide an unambiguous set of steps to reproduce this bug. Include code or configuration to reproduce, if relevant.
1. Add stripe as a connector in a sandbox env
2. Test payment using unified payments
3. Use stripe 4242 4242 4242 4242 as card number

### Context For The Bug

_No response_

### Environment

Are you using hyperswitch hosted version? Yes
If yes, please provide the value of the `x-request-id` response header for helping us debug your issue.

x-request-id: 35018b79-db3a-45d2-a935-b4531f103b73

### Have you spent some time to check if this bug has been raised before?

- [X] I checked and didn't find similar issue

### Have you read the Contributing Guidelines?

- [X] I have read the [Contributing Guidelines](https://github.com/juspay/hyperswitch/blob/main/docs/CONTRIBUTING.md)

### Are you willing to submit a PR?

No, I don't have time to work on this right now

Hi @kielerdotdev , thank you for raising this issue.

Hyperswitch is PCI complaint so it is allowed to send raw card details to stripe.
However, an option should be enabled on the stripe dashboard. Please logon to you Stripe dashboard > Search for Integrations > Advanced Options > Handle card information directly.
If you are not PCI complaint you can use Hyperswitch frontend sdks to accept card information from customer and send to Hyperswitch directly.

Hi @kielerdotdev!
Creating a payment token with Stripe means that the token can only be used with Stripe. This means that the end user would have to re-enter their card details for it to be processed by the other integrated payment processors creating a friction in the payment experience.
Hence enabling sending raw card data from the processor's end is a better approach because it is easier and is secure given that Hyperswitch is PCI compliant.

Hi I'm having this similar issue when trying to make a test payment in hyperswitch dashboard. I have successfully connected stripe to hyperswitch, and then attempted to make a test payment with the test cards. I get the error "Sending credit card numbers directly to the Stripe API is generally unsafe. We suggest you use test tokens that map to the test card you are using".
Tried to do the suggestion by @Abhicodes-crypto of enabling the "Handling of card information" in stripe settings;

But as you can see from above, stripe doesn't let me enable that.
Now I would like to try the suggestion by stripe of using test tokens. But know I don't know how to pass the test tokens in hyperswitch when making the test payment. Please help. Thanks!


Support -x,--cross-seed option

This option allows users to easily cross-seed torrents without having to manually define a source flag.
A unique id made from the hash of all announce-urls is embedded inside the info dict.
Behaviour is almost the same as the --source options except that the user does not care what the value of the unique value is exactly.
Apparently there are trackers that strip the source field so a different flag is needed.
This option is implemented by pyrocore with the x_cross_seed field.

Added in v0.6.0


cppflow2: global context and status do not allow parallel execution with multiple threads

The current context::get_status() shares the same TF_Status in context, which cause a race condition if executed concurrently.
I am not sure about TFE_Context though. The header mentions some of its internal status are thread local.
One of the solutions is to use thread local context and status, e.g. as in Swift. (thread_local keyword in C++) I think this is the better solution.
The other solution is to allow users to create and manage their own context. We also need to keep the global default context for eager execution.
Edit:
The Context implementation in Swift API for tensorflow is here. It uses a ContextManager (a stack of Context) to manage the default Context for the current thread and stores them in ThreadLocalStorage. I am not sure whether we need ContextManager or not, but it seems thread_local should also work for Context.

Yes, I didn't though about it for parallel execution.
For TF_Status using thread_local is a nice solution. I am also not sure about TFE_Context but it may also work.

Solved with #60


[Snyk] Security upgrade socket.io from 3.1.2 to 4.7.0

This PR was automatically created by Snyk using the credentials of a real user.![snyk-top-banner](https://github.com/andygongea/OWASP-Benchmark/assets/818805/c518c423-16fe-447e-b67f-ad5a49b5d123)
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):

package.json

Vulnerabilities that will be fixed with an upgrade:

Issue
Score

Denial of Service (DoS) SNYK-JS-WS-7266574
  170

[!IMPORTANT]

Check the changes in this PR to ensure they won't cause issues with your project.
Max score is 1000. Note that the real score may have changed since the PR was raised.
This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Denial of Service (DoS)

Checkmarx One – Scan Summary & Details – ff450037-071c-4f4d-bcbf-cb188e4192c7
New Issues

Severity
Issue
Source File / Package
Checkmarx Insight

CVE-2024-37890
Npm-ws-7.4.6
Vulnerable Package

Fixed Issues

Severity
Issue
Source File / Package

CVE-2022-41940
Npm-engine.io-4.1.2

Cxf7be4d76-1989
Npm-web3-4.8.0


Honeywell state changes ignored by InfluxDB component

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.49.1
Python release (python3 --version):
Python 3.4.2
Component/platform:
Honeywell
Description of problem:
When both the Honeywell climate platform and influxdb component are active, no climate data is posted to InfluxDB. State change data from other components is posted without issue.
Expected:
I would expect to see Honeywell device state under the "°C" measurement and "climate" domain posted to InfluxDB.
Problem-relevant configuration.yaml entries and steps to reproduce:
influxdb:

climate:
  - platform: honeywell
    username: [redacted]
    password: [redacted]

Run hass
Wait for Honeywell-related state_changed Event notifications to appear in the log file
Observe that no matching measurement has been received by InfluxDB

Traceback (if applicable):
N/A
Additional info:
This is due to the state returned by the Honeywell "RoundThermostat" ClimateDevice failing the InfluxDB check against STATE_UNKNOWN here. When the RoundThermostat device is created the underlying device doesn't seem to have the "system_mode" attribute referenced by the "current_operation" property and returns None.
When the state is checked  in the base class this causes the ClimateDevice's state property to return STATE_UNKNOWN.
I'm happy to submit a PR for this but I not 100% certain what the correct answer is so if the author of the Honeywell component is still around they probably have a better idea. My local fix has been to set the system_mode attribute in the RoundThermostat constructor to 'idle', matching the STATE_IDLE string found in the ClimateDevice file, but not found in the Honeywell code.

I'm not familiar with the Honeywell thermostat but I had a look now in the library that is used. I think the code for operation mode is just wrong. There is no attribute in the evohome client library called "system_mode", as you point out.
https://github.com/watchforstock/evohome-client/blob/master/evohomeclient/__init__.py
I can't see a way to get current mode from the library. Maybe just set mode to auto on first update and set current operation to auto after that? The client method is called set_status_normal to set mode to auto.

Thanks for this Martin.
I've reviewed the evohomeclient library and you're right to say that we can't get the current mode from there. It's returned in the data received by that library but not yielded by the temperatures() method. I could search the full_data dictionary held by the library and pull the information out of there, but it seems like a bit (well, a lot) of a hack. The alternative is changing the library but it does not appear to be in active development.
I think I'll submit a PR for the hack that actually gives us the information I think hass users want. After that I might take a closer look at the Honeywell component as a whole and the library underpinning it.


Fix refresh() not restarting update()

I have moved the update method inside the init. Now calling refresh after destroy will correctly reinit Rellax.
I'm not sure if refresh was intended to reinit rellax, instead of just recalculating positions.
If it is not, I can separate init into a method that will calculate positions and method that will set up listeners and loop, if you wish.

Hi @shrpne - would this pull request fix the issue I'm having here:
https://github.com/dixonandmoe/rellax/issues/157

@pauljohnknight yes it should, the motivation of this PR was the same problem that you described in the issue

@shrpne - I added your code into a version of the original and it works and fixes the bug - this is so helpful. Thanks so much for doing this.
@moeamaya - I can confirm this fixed the problem/bug of the parallax breaking on window-resize events (that are resized a second time).

Thanks @shrpne and @pauljohnknight merged and published to npm.

@moeamaya I don't think this fix was included in the minified files, FYI.

I think it is weird behavior to have refresh reinstate a destroyed Rellax instance?
If I destroy the instance, I'd think I need to recreate it when needed as it doesn't exist anymore.
Maybe it's semantics...
But it clashes a bit with the #170 bug. I need to call refresh() in a scroll listener as a workaround for that bug.
But I would like to disable Rellax on small screens, so listening to a media query I destroy Rellax when needed. However, now I also have to test for that media query in the scroll listener so the refresh wouldn't trigger and reinstate my destroyed Rellax instance. Seems unnecessary.
I'd prefer this:

I can separate init into a method that will calculate positions and method that will set up listeners and loop, if you wish.


Extensions addition

Added extensions that are used in multiple projects.

Added extensions that are used in multiple projects.


Add option to disable built-in DHCP server in bridge networking mode

Is your feature request related to a problem? Please describe:
Currently, KubeVirt's bridge networking mode includes a built-in DHCP server that cannot be disabled. This built-in DHCP server lacks IPv6 and dual-stack support, which creates limitations for users requiring IPv6 functionality in their virtual machine networking setup. In our environment, we use Kube-OVN CNI which already provides comprehensive DHCP capabilities including IPv6 support. However, we cannot leverage Kube-OVN's DHCP functionality due to potential conflicts with KubeVirt's built-in DHCP server.
Describe the solution you'd like:
We propose adding a configuration option that allows users to disable KubeVirt's built-in DHCP server in bridge networking mode. This could be implemented as:

A new configuration flag in the VMI spec (e.g., disableBridgeDHCP: true)
A global configuration option in the KubeVirt operator
This would give users the flexibility to use alternative DHCP solutions that better suit their networking requirements, such as CNI-provided DHCP servers with IPv6 support.

Describe alternatives you've considered:

Using different networking modes (such as multus), but this would require significant architecture changes in our existing setup
Implementing IPv6 support in KubeVirt's DHCP server, but this would be a more complex undertaking and wouldn't address the immediate need for integration with CNI-provided DHCP services

Additional context:
Our use case specifically involves integration with Kube-OVN (https://github.com/kubeovn/kube-ovn), which provides comprehensive DHCP capabilities including IPv6 support. This feature would enable better integration between KubeVirt and various CNI solutions that provide their own DHCP services, making KubeVirt more flexible in different networking environments.

The new managedTap option should provide the needed functionality.
ref: https://github.com/kubevirt/community/blob/main/design-proposals/primary_network_binding_for_seamless_migration.md#as-a-bridge-domainattachmenttype

Thank you for the detailed response!
I appreciate you pointing me to the documentation. I will try it out. I'll follow up if I encounter any issues or need further clarification.
Thanks again for your help!


batch support

I'm currently using llama-cpp-python to host quantized models via an api because it supports batching.  I would switch to this, but the framework would have to support gguf + batching

Yeah, quantization and batch are both super important. We are looking into it, but some help from the community would make it move faster.


[bug] Cannot read property 'directives' of undefined

After upgrading from 4.12.0 to 4.13.0 - I receive the following error:
✖ An error occurred when pushing the resources to the cloud
Cannot read property 'directives' of undefined
An error occured during the push operation: Cannot read property 'directives' of undefined

Hiii
Am getting same error while running amplify codegen models
amplify version = 4.21.3


SSL errors not being reported

I had an error where the SSL pem file provided to mup was incorrect. Naturally, HTTPS didn't work. However, mup setup reported no errors:
✔ Installing Stud: SUCCESS
✔ Configuring Stud for Upstart: SUCCESS
✔ Configuring SSL: SUCCESS
I was able to confirm the SSL pem file was the issue by SSH-ing into the server and calling stud --config=/opt/stud/stud.conf manually. Fixing the PEM file resolved the issue. Would be nice if MUP could have told me that earlier though.
Was using mup version 0.9.2 to set up a Ubuntu 14.04 server.

Okay. That's a good idea.
I can do that.
On 2015 මාර්තු 11, බදාදා at පෙ.ව. 6.03 Andrew Fong<EMAIL_ADDRESS>wrote:

I had an error where the SSL pem file provided to mup was incorrect.
Naturally, HTTPS didn't work. However, mup setup reported no errors:
✔ Installing Stud: SUCCESS
✔ Configuring Stud for Upstart: SUCCESS
✔ Configuring SSL: SUCCESS
I was able to confirm the SSL pem file was the issue by SSH-ing into the
server and calling stud --config=/opt/stud/stud.conf manually. Fixing the
PEM file resolved the issue. Would be nice if MUP could have told me that
earlier though.
Was using mup version 0.9.2 to set up a Ubuntu 14.04 server.
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/304.

Done. Landed with the new version: (0.9.3)
On Wed, Mar 11, 2015 at 6:09 AM Arunoda Susiripala<EMAIL_ADDRESS>wrote:

Okay. That's a good idea.
I can do that.
On 2015 මාර්තු 11, බදාදා at පෙ.ව. 6.03 Andrew Fong <
<EMAIL_ADDRESS>wrote:

I had an error where the SSL pem file provided to mup was incorrect.
Naturally, HTTPS didn't work. However, mup setup reported no errors:
✔ Installing Stud: SUCCESS
✔ Configuring Stud for Upstart: SUCCESS
✔ Configuring SSL: SUCCESS
I was able to confirm the SSL pem file was the issue by SSH-ing into the
server and calling stud --config=/opt/stud/stud.conf manually. Fixing
the PEM file resolved the issue. Would be nice if MUP could have told me
that earlier though.
Was using mup version 0.9.2 to set up a Ubuntu 14.04 server.
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/304.

Hi I have also no warnings (updated mup to latest version). I did the command:
stud --config=/opt/stud/stud.conf
and got stuck at this ::
{core} Note: no DH parameters found in /opt/stud/ssl.pem
process got stuck here. The process is not terminating. What am I doing wrong ? I got 2 files from comodo ::
-> COMODORSAAddTrustCA.crt
-> COMODORSADomainValidationSecureServerCA.crt
these are the intermediate certificates right? should I add both or just one?
@fongandrew what magic did you do to fix it manually :) ?

Check this article:
http://alexnj.com/blog/configuring-a-positivessl-certificate-with-stud.html
You need to append both
On Wed, Mar 11, 2015 at 3:13 PM yann<EMAIL_ADDRESS>wrote:

Hi I have also no warnings (updated mup to latest version). I did the
command:
stud --config=/opt/stud/stud.conf
and got stuck at this ::
{core} Note: no DH parameters found in /opt/stud/ssl.pem
process got stuck here. The process is not terminating. What am I doing
wrong ? I got 2 files from comodo ::
-> COMODORSAAddTrustCA.crt
-> COMODORSADomainValidationSecureServerCA.crt
these are the intermediate certificates right? should I add both or just
one?
@fongandrew https://github.com/fongandrew what magic did you do to fix
it manually :) ?
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/304#issuecomment-78232009.

Thats what I did :(
I have to go until here right?
cat alexnj_com.crt PositiveSSLCA2.crt AddTrustExternalCARoot.crt alexnj.com.key > bundle.pem

Hmm. weird.
On Wed, Mar 11, 2015 at 4:41 PM yann<EMAIL_ADDRESS>wrote:

Thats what I did :(
I have to go until here right?
cat alexnj_com.crt PositiveSSLCA2.crt AddTrustExternalCARoot.crt
alexnj.com.key > bundle.pem
—
Reply to this email directly or view it on GitHub
https://github.com/arunoda/meteor-up/issues/304#issuecomment-78244211.

yup weird. I think it has to do with the fact that stud --config=/opt/stud/stud.conf is not terminating...

@arunoda That was fast! The verification is working for me.

@yanndebelgique You should have gotten four files from COMODO -- the certain for your domain, two intermediate certificates, and a root certificate. You have to concatenate those with your key in this order (so 5 files total):

Domain certificate
COMODORSADomainValidationSecureServerCA.crt
COMODORSAAddTrustCA.crt
AddTrustExternalCARoot.crt
Key

In my case, it looks like this:
cat STAR_filegraph_com.crt COMODORSADomainValidationSecureServerCA.crt COMODORSAAddTrustCA.crt AddTrustExternalCARoot.crt filegraph.com.key > ssl.pem

Ok thanks I will try that

no luck :(
dum dum questions :

I changed the file names i.e. adding a_.. b_.. c_.. in order to remember the cat order. Is this an issue?
what is the expected output from stud --config=/opt/stud/stud.conf? This process doesn't terminate when I try it on my machine. Is this because my ssl file is misconfigured?
I've deployed my app before without ssl. Is this a pb?
the domain name is lightnow.co
what kind of checks can I do to hunt down my bug?

@yanndebelgique I'm having the same problem with {core} Note: no DH parameters found in /opt/stud/ssl.pem and the process not terminating

Then they were two :)
Still haven't found the issue

@yanndebelgique @madshargreave Changing the file names shouldn't be an issue.
If calling stud --config=/opt/stud/stud.conf doesn't terminate and you don't see any error messages, that might just mean stud is running as a server (e.g. like how calling meteor just runs the meteor server until you kill or interrupt it).
You can call stud --test --config=/opt/stud/stud.conf to test SSL configuration and then quit (which is what the latest version of mup does).
I get the "no DH parameters" message too. It means (I think) that there are no Diffie Hellman parameters in your PEM file, which are needed for Perfect Forward Secrecy. If you don't care about or need PFS, then you can ignore this message. Just try connecting to the server in your browser via HTTPS. If it connects, then you're done. If it doesn't, there's probably some issue other than the lack of DH parameters you need to deal with (DNS maybe?).
If you do care about PFS, then you'll need to add DH params to your PEM file. You'll probably also need to edit the stud conf file accordingly (I don't think the one Meteor Up provides has PFS enabled).
Some resources regarding how to do that:
http://security.stackexchange.com/questions/38206/can-someone-explain-a-little-better-what-exactly-is-accomplished-by-generation-o
http://vincent.bernat.im/en/blog/2011-ssl-perfect-forward-secrecy.html
http://baudehlo.com/2013/06/24/setting-up-perfect-forward-secrecy-for-nginx-or-stud/
Note that some of these older blog posts suggest using RC4 as a cipher. RC4 is no longer regarded as secure, so don't do that. I'm not a crypto expert, so I'm not quite comfortable suggesting an alternative myself, but see https://wiki.mozilla.org/Security/Server_Side_TLS.

FYI: I've created an issue for supporting different ciphers for stud (e.g. for PFS) here:  https://github.com/arunoda/meteor-up/issues/307

ok thank you for the extensive answer!

Ok so now it gives me : stud configuration looks ok.
I'll go look at comodoro's configs and see what  I can change.

so my common name is www.lightnow.co
should this be lightnow.co or is that not the problem?

Me again.
What kind of issues can stud detect and which issue can't it detect?
Also in comodo I got the following :
To help reduce domain name mismatch warnings, we have also included the domain name lightnow.co in your certificate.

Stud just detects whether your pem file is configured correctly (e.g. in the correct order). I guess it also detects the presence of DH params or lack thereof.
It looks your Comodo cert supports both https://www.lightnow.co and https://lightnow.co. Both seem to work when I visit them in my browser, so you're all set for now.

Halleluya!!!!! thanks man you were super helpful!!!! I love the internet

@fongandrew How do I troubleshoot to make sure the mup scripts are properly installing and configuring STUD? I am not even getting the output like yours (below). I am running mup 0.9.7
✔ Installing Stud: SUCCESS
✔ Configuring Stud for Upstart: SUCCESS
✔ Configuring SSL: SUCCESS


Mappable values

Resolves #1897 (mappable query params and path params)
Related to #1789 (align mappers)
Added Value and ValueProvider to mapper module.
It is now used in various HTTP classes (Headers, query parameters etc.) and in Config (ConfigValue).
Added support for a shared MapperManager that can be custom registered by user.
Mapping to basic types is built-in (String -> a lot of types), including date types. Format can be overridden through context if desired (see MapperManager.FORMAT_CLASSIFIER).
The changes are fully backward compatible - we have to decide how to approach this (e.g. do we want to keep all the methods, or do we want to change signatures in the future?).
Created as a draft until we agree on approach.

It would be easier to have a markdown document going over the proposal.
We should describe all the various use-cases with snippets:

config
dbclient
media support
webserver query params

Highlight the complex type usages with GenericType, document the special layering of media-support.
We should also have an example that demonstrates the value of this API when combining dbclient and webserver/webclient. E.g. Show how to support a custom entity all the way from a request payload to the database.


WebGL errors logged when using SpectorJS

The application now appears to work correctly with SpectorJS (#5941), however when the application is run with SpectorJS WebGL errors appear in the console:

This likely affects analysis performed with SpectorJS.

Should we report them in the Spector Github Issue tracker? It looks like we don't have these errors without Spector, right?

I think the bug must be in Spector. I'll have a quick look at whether I can narrow it down to something easily reproducible.

Yup would be great to have a repro but I guess this one might already been fixed :-)
Could you try the latest version from a local install ?
I ll see to deploy if it is all good.

Yup would be great to have a repro but I guess this one might already been fixed :-)
Could you try the latest version from a local install ?
I ll see to deploy if it is all good.

That was fast :smile:. Yeah, the PredefinedColorSpace error is fixed in current master.
The GL_INVALID_OPERATION error is still occurring, though. We'll set up a page that reproduces it.

@sebavan thanks so much for helping us here so fast!

Hi! In case you would still need a playground here is the newest one (2023.1.1-nightly.2023.3.23):
http://ensocdn-playground.s3-website-eu-west-1.amazonaws.com/

@sebavan would you be able to take a look at the link provided above? Do you prefer me to report it on Spector.js Github instead? :)

The invalid format is not an issue, just means we have an unreadable texture so I can not capture the data. It should not break the rest of the experience.
I can not really try cause:

Closing, as we don't use WebGL in GUI2.


Initial set of fixes

Changes in the PR include:

Created a new repo called 'settings-operator' in redhat-pipeline-service org in quay.io and updated the references in the codebase.
Improved README
Defaulted the value of api-export-workspace to root:default:pipeline-service-compute to align with ckcp.
Defaulted the value of IMG to quay.io/redhat-pipeline-service/settings-operator so that users won't have to specify the image each time.
Worked on having the same prefix behaviour in both 'make deploy' mode and 'make install run' mode
Updated the namespace where resource quota is getting deployed to 'admin'

Next PR will have a change to separate the namespace where networkpolicy is deployed.

@fgiloux PTAL and let me know if there are any more changes.


Fix typos in the About page and Articles section

Typos to be fixed:
 In The About page:
....conditions that have an affect ( effect ) on a person’s....
....Aditonally ( Additionally ) , mental health....
....They are ususally ( usually ) a result of poor daily....
 In The Articles section:
....Suicidal thoughs ( thoughts ) among adults are increasing....
I would like to work on this issue under GSSOC, kindly assign it to me.

i can work on this @miraehab


Shadow effect of "OUR TOURS" button in navbar not working like other buttons

What is the bug*
A clear and concise description of what the bug is.
Expected behavior
Similar elements should be styled uniformly.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
@Arun9739 Can I fix the same?

Good to go @Coderner
Star the repo ⭐ to showcase your support.


City States Panel not showing properly

All of a sudden my city states panel is not functioning.
I removed the mod and it was fixed. I added only this mod again and I have the same problem.
I couldn't find an option that could change settings in city states. Maybe I missed something.
Before this issue the mod worked perfectly for me.
Now I can't play with the mod anymore, because I can't access any of the city states and send envoys. The back button at the top right corner doesn't work.

Fixed on GitHub, see #283 an update will soon be made on Steam by Sparrow.


gh: 2.25.1 -> 2.26.0

Diff: https://github.com/cli/cli/compare/v2.25.1...v2.26.0
Changelog: https://github.com/cli/cli/releases/tag/v2.26.0
Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

1 package built:

gh

Please don't skip CI, there wasn't any urgency here.


Add RPC helpers

This resolves issue #49.
See also MSDN's page on RPC exceptions. Structured exceptions and C++ exceptions don't play well together.  This adds wil::invoke_rpc and wil::invoke_rpc_result to convert raised exceptions into HRESULTs, both throwing and nonthrowing variants.
Also included are wil::unique_midl_ptr and wil::unique_midl_string for working with types returned by RPC calls allocated via MIDL_user_allocate.

Question for readers - since this is tied to Win32 RPC, should this instead go into win32_helpers.h instead of adding a completely new header?

@jonwis Please update wiki.

Add unique_midl_ptr to Supporting types
Add unique_midl_string, unique_midl_ansistring to Unique-any handle types
Add new page for rpc_helpers.h.

Added to the types lists and created https://github.com/microsoft/wil/wiki/RPC-helpers


🐛 Ignore collection failures in non-tests

This change applies the pre-existing patterns to identify if the files with collection problems are tests. It is then used to eliminate the false-positives of F6401 (cannot-enumerate-pytest-fixtures).
As a side effect, this patch also includes precise file paths that may be used to reproduce the problem.
Fixes reverbc#20
Fixes reverbc#21
Signed-off-by: Sviatoslav Sydorenko<EMAIL_ADDRESS>Replayed; Source PR: https://github.com/reverbc/pylint-pytest/pull/22
Additionally, satisfied the https://github.com/pylint-dev/pylint-pytest's .pre-commit-config.yaml
Signed-off-by: Stavros Ntentos<EMAIL_ADDRESS>
Capture and return stdout and stderr (instead of trashing them)
Fix the 'duplicate-path' error by relative-izing the paths before unioning them
Update tests to test for both conditions

Additionally, fix two used-before-assignment pylint issues (stdout, stderr) 🤪
Signed-off-by: Stavros Ntentos<EMAIL_ADDRESS>

I think this is a sanity check whether pytest can process a ficture created at the repository pylint is checking.
I am not sure how much "valuable" it is in CI scenarios (pytest will fail running in that case anyway).
Might be ... for the lazy? A "quick" way to get feedback (given that pylint might run after every file save)?
I haven't dug the git-log for that. We can disable it by default on v2 though?

I meant disable it in pylint-pytest for our own repository, not disable it for users.

I meant disable it in pylint-pytest for our own repository, not disable it for users.

I'd ... need to see that when we revisit re-enabling pylint warnings.
... or I didn't understand the question 😓

I'm not sure I understood this MR well. I'm going to focus on compatibility with pylint 3.0 for now (maybe using the addon in pylint itself would help me understand how it works then).

@stdedos nice that you picked up my old PR. Too bad that I'm only seeing this now and had the plugin version pinned in my configs for all these years :(
For future, I recommend either re-pushing unmodified commits or at least using the Co-Authored-By: trailers so that the patches are credited correctly: https://hynek.me/til/easier-crediting-contributors-github/. This would've probably notified me earlier too (I think)...

Apologies @webknjaz. I did those MRs multiple times.
... I obviously missed something :sweat_smile:

Yep, it seems like you changed the authorship to Signed-Off-By and dropped the metadata from the commit's built-in fields, losing this information. AFAIK Signed-Off-By should only be added by somebody having a permission from the author as it's used as a DSO in many places, basically as a declaration that the author promises they're in legal possession of a patch being sent. My understanding is that the common recommendations here are the same as for the copyright lines in code — only one adding such a line in the first place is supposed to touch it and other people would need to add their lines separately.
IANAL though, this is my personal understanding of the meaning of such trailers.

Yep, it seems like you changed the authorship to Signed-Off-By and dropped the metadata from the commit's built-in fields, losing this information

Basically I'm trying to keep each commit in-line with a Green CI. As CI was done "after" your commit, "I had no option other to re-write it". But ofc I could've kept author/committer and/or Co-authored-by:.

Yeah - in retrospect, I would've done much less: Just pull the commit.
I have done shenanigans to remediate ill-crafted commits (see: https://github.com/pylint-dev/pylint-pytest/commit/69ad82f1f07a6a1cb33e33266ad46f2fcb006b15) but this MR is literally the first functional change merged. I'm afraid is too late to do something meaningful :heart:

I'm afraid is too late to do something meaningful ❤

That's actually fixable by making a true merge commit (not a squash or rebase) from the original branch and having it as this natural merge in master. But it's probably not something to care about.

Yaaaay! 🎉


Use within an addon?

It doesn't appear as though this addon can be used within another addon. Is that expected? I'd like to use it within an addon but it appears that ember-code-snippet's treeForApp and treeForVendor hooks are never called, depsite it being a devDependency in the parent addon.

I think devDependency implies that it will only be needed when running your addon directly, from its standalone dummy app. Try making it a dependency instead.

Thanks @ef4. I move it to the dependencies property but now the included hook is blowing up with Object #<Class> has no method 'import'. Seems to be a known issue discussed here: https://github.com/ember-cli/ember-cli/issues/3718

Closing this because ember-cli now recommends using peerDependencies for recursive addon dependencies.
https://github.com/ember-cli/ember-cli/issues/3718#issuecomment-166644137


[server chart] Explicitly set X-Forwarded-Host header on Ingress.

The default Ingress config allows clients to override X-Forwarded-Host and put in arbitrary hostnames. Rancher server uses this header to construct links in the UI.
Since the ingress is already only responding to a specific hostname, lets make sure this value gets set appropriately to avoid any weird rendering or possible security issues.

👎 It's not "weird rendering", it's explicit support to ask the server to generate links for a different base URL than the hostname the request came in to.
There is no security issue.  Anybody that can insert this header into a request can arbitrary change any other part of the request or its response (including walking the response and changing all the link base URLs themselves instead of having the server do it).
This change completely breaks UI development/debugging ability against a HA rancher install.

Closing this stale pr


allergies: Update to canonical data

Test case - allergic to eggs in addition to other stuff is incomplete.
Checks for shellfish and strawberries have been added.

😄


Greensock

I'd love to see how GSAP stacks up against the other three!
https://greensock.com/gsap/

I haven't used it before, but it will be interesting to try, yes!

 They compare against JQuery 3 (what?), Motion One, Web Animations API, etc.
It can also animate PIXI objects with a Plugin.


simulAVR and gdb-avr missed in toolchain-atmelavr-linux

When I tried to configure external tools before debugging my .cpp code (Eclipse), I didn't find 'simulavr' and 'gdb-avr' files at this folder: ${HOME}/.platformio/packages/toolchain-atmelavr/bin/
I use Ubuntu 14.04 64-bit.

Hi @OmarBelkhiria
avr-gdb is restored, please update packages via platformio update
http://docs.platformio.org/en/latest/installation.html#development-version

@OmarBelkhiria please re-open this issue if you still have ant problems

Thank you @valeros but  'simulavr' is still not included. How to re-open the issue?

@OmarBelkhiria Please, update your packages via platformio update

@valeros it's all right now; thanks.


docker fails - invalid runtime nvidia

docker-compose up -d server && docker-compose ps && docker-compose logs -f
[+] Running 0/0

Container metavoice-server  Creating                                                                            0.0s
Error response from daemon: unknown or invalid runtime name: nvidia

Windows 10 - Powershell

@StarkBotha same issue here

We don't have a windows env atm. Would greatly appreciate a PR from either of you :)

@sidroopdaska i'm actually using an macbook pro

Hey @CaptainJeff @StarkBotha, thanks for raising, I'm gonna close this issue given its out of the scope of our current support but I've created an explicit feature request issue that we can use to track in the future.

In docker-desktop in Setting --> Docker Engine: I change the JSON Docker daemon config file to
{
"builder": {
"gc": {
"defaultKeepStorage": "20GB",
"enabled": true
}
},
"experimental": false,
"runtimes": {
"nvidia": {
"path": "/usr/bin/nvidia-container-runtime",
"runtimeArgs": []
}
}
}
and it works for me


Fixing Multibuild

Hey,
Just a quick change to the csproj to fix the multibuild feature :D
Regards
Syzuna

would maybe suggest pushing a new nuget package when all the build stuff is sorted bcs many ppl have problems

I was just sitting down to fix this. Thanks for doing it. Simple enough :D. Should also resolve #301 . Will get a nuget package out today.


Support for different day based ranges

Right now the scheduler is hard set on a 4 weeks (in days) for display. It would be nice to have it more flexible. It would be nice to be able to send a start date, and end date and get a table that is showing the right range (right now it will distort the entire table).

Thanks for the feedback. Someone is actually working on this right now, though I'm not sure how long it will be. A PR is welcome, otherwise, it may be awhile. I'm pretty busy on things that are paying me right now. :)

Ok so @zackify guilted me into fixing this. :) As of https://github.com/Legitcode/scheduler/commit/58b2280586f079876beb58b7ee6c524cd7213022 the scheduler now supports this. It wasn't a big change at all. Version 0.2.0 has been released.
The scheduler will now accept whatever date range you give it, and will advance/retard the date range according to the number of days in date range you give it.
@YanivRan


Add generic k8s deploy example

Supplanted by https://github.com/silverton-io/honeypot-documentation/issues/13


cannot convert klog.V(9) (type klog.Verbose) to type bool

ERROR: cannot convert klog.V(9) (type klog.Verbose) to type bool

I'm trying to run a go test in my machine and it ended up with this error today. It was fine until yesterday, and it also runs fine with the old test files, and not with the newly created one.
Any suggestions or help will be much appreciated.

Also getting the same error.
Seems to be in the debugWrappers function which tries to convert Verbose type to bool

➜  test go version
go version go1.14.1 darwin/amd64
➜  test go run main.go
k8s.io/client-go/transport
../k8s.io/client-go/transport/round_trippers.go:70:11: cannot convert klog.V(9) (type klog.Verbose) to type bool
../k8s.io/client-go/transport/round_trippers.go:72:11: cannot convert klog.V(8) (type klog.Verbose) to type bool
../k8s.io/client-go/transport/round_trippers.go:74:11: cannot convert klog.V(7) (type klog.Verbose) to type bool
../k8s.io/client-go/transport/round_trippers.go:76:11: cannot convert klog.V(6) (type klog.Verbose) to type bool
➜  test


[FEAT]: AWS Bedrock temperature adjustment

What would you like to see?
I'm currently using the AWS Bedrock feature and it looks like bedrock supports adjusting the temperature through their API. It'd be helpful to have this in the settings since some models operate at different optimum temperatures than others (ex: Mistral large has a different "optimum" temperature than Llama 3.1)

We do support temperature!
https://github.com/Mintplex-Labs/anything-llm/blob/f7756d475812989ff3b78cd36b40250ed4539b3c/server/utils/AiProviders/bedrock/index.js#L179
You can set it per-workspace in the workspaces Chat Settings (scroll to bottom)

Ah I see it! Thanks for the quick response!


Error on Taxable income

There is an error on Taxable income when How much can you justify as professional related expenses is zero.
Great Work. Thanks

I just notice there is a pull request about this . PR #18


Support for SASL authentication

Provide a mechanism for authenticating against the Memcached servers. Before needed support for the binary protocol.

well, I accidentally didn’t read about this problem and made a copy
#125

macos does not yet support SASL on its part

Closing this ones as done, it supports Linux which is what is being used in production. Also most of people uses Memcache dockerized when runnning in local


Trailing "0" on Version for Managed Package Dependencies in cumulusci.yml Not Recognized on Install

Issue
When running a flow/task which performs an install of dependencies (e.g. cci flow run dev_org --org dev), if the package version ends in a "0" (e.g. 6.5220), zero is not recognized during flow run producing an error:
Error: InstalledPackage version number :  6.522 does not exist!
Steps to Reproduce

Add a Managed Package Dependency to cumulusci.yml with a trailing "0":

dependencies:
- namespace: stayclassy
version: 6.5220

Run a flow/task that installs dependencies (e.g. cci flow run dev_org --org dev)

Results

Task fails with error: Error: InstalledPackage version number :  6.522 does not exist!

Expected Results

Package is successfully installed
No errors

It should work if you put quotes around the version:
version: "6.5220"

That'll convince the yaml parser to read it as a string rather than a number.

Ah makes sense!

Probably just a matter of updating documentation then: https://cumulusci.readthedocs.io/en/latest/features.html#managing-dependencies

@davisagli although looking back at the yaml, nothing else has "" so it seems a bit out of place to do it in this one place. Seems more consistent to actually have interpreter read it as a string.

@Julian88Tex that'd be nice but I don't think we have that level of control over the parsing. We use a generic YAML parser and using the quotes is how you tell it that something that looks like a decimal number should actually be read as a string.

@davisagli makes sense thanks for clarifying!

Fixed by 5a5b526


Followup code cleanup/optmization after #36319

Once we have a single codepath, some optimizations become clearer:

[ ] https://github.com/project-chip/connectedhomeip/pull/36319#discussion_r1824915671 : IsDeviceTypeOnEndpoint logic is repeated in several places. Some code re-use would be nice.
[ ] https://github.com/project-chip/connectedhomeip/pull/36319#discussion_r1824912427 : reporting/Read.cpp is not ideally named, should be maybe inline into reporting or we should figure out proper naming and placement
[ ] https://github.com/project-chip/connectedhomeip/pull/36319#discussion_r1824906824 : mLastSuccessfullyWrittenPath and mProcessingAttributePath are tightly coupled so we may be able to save some code/logic/flash/ram. Review their use and coupling and update the code accordingly

For the 3rd item, I could not find an immediate dedup logic for mLastSuccessfullyWrittenPath and mProcessingAttributePath as their code paths are updated at separate times. Deduplicating members within our handlers will likely require separate consideration.


APPS-48 ITER 2 Quote App

@tpanagos
ITERATION 2 of the Quote App for the Change Order suite
Needs WORK-1028 and WORK-1032 merged to properly function
Alternatively place yourself on branch APPS-46 of workflow
You will have to update the link variable in the App configuration to a valid Folder link for the DocuSign signing o work
The link creation part of the Docusign component returns an error on localhost, only sign on an https server

There are issues with the new library of components, closing for now.


How to make more complex rarity colors?

There isn't much documentation and I'm curious about the full capabilities of ZSRarity.

Actually it's sorta broken, sorry. Changing color only works once per item.


[NCL-7200] Implement SCM Repository Detail page

Known issue: AttributesItems component have Warning: Encountered two children with the same key, [object Object] when property names are objects.

I think for AttributesItems issue, we can either:

Refactor the component to allow passing keys to the attributes, or
Use ordered or random numbers like Attr-1 for those non-string attribute names.
Any other solution would be welcomed.
I would suggest we  have an individual jira for this issue.

AttributesItems issue will be covered in NCL-7622


Active peer distribution reporting only TIME instead of DATE

Description
The active node distribution table in the PSQL table only shows the TIME at which the snapshot was taken instead of the entire Date (see image below)

closing this issue as it has been solved with #55


Set the values for messaging provider based on what user selects for messaging configuration: BE

Description
In This ticket, we planned to only work on the UI to configure default messaging provider. The default value propagation to the backend was decided to be a separate work after this ticket is completed.
We aim to set the default messaging value in the backend.
Acceptance Criteria

When a user selects a default configuration value in the front end, the same value is used by Fides for running DSR requests.

@galvana  is this likely to be done this sprint? We're going to be assisting on finishing this epic in the next sprint so trying to get the lay of the land.

just an FYI that before leaving on PTO i got a very preliminary PR up for this before heading out on PTO, not sure why it wasn't linked to the issue.
if someone wants to pick this up before i'm back next week then please do take that as a starting point. otherwise i should be able to knock this out relatively quickly once i'm back next week.


Add built-in pipeline video copy detection

Signed-off-by: Kaiyuan Hu<EMAIL_ADDRESS>

/approve
/lgtm


ci: Change Docker images to ubuntu:24.10

23.10 is EOL so update to the latest stable version.

NOT FUN 24.04 is also when they did the change to 64-bit time_t which we are not ready for...

Superseded by https://github.com/rust-lang/libc/pull/4120


serve rebuild speed problem between 9rc.2 and 9rc.3

🐞 Bug report
Command (mark with an x)

[x] serve

Is this a regression?
Yes, in 9rc2, our app (on serve) each rebuild is <2seconds
Now with with rc3, if I trigger rebuild by adding one character in file+save (5 times) rebuild always take >15seconds
1.I was on 9rc2 then use ng update to go to 9rc3.
2. After that I run --migrate-only --from=8 --to=9
3. ng s ( aot is enabled)
🔥 Exception or Error
rebuilt speed problem
Anything else relevant?
cc @filipesilva

Note: both CLI and FW were updated in this case from rc.2 to rc.3.

Hi, I did some tests on a project that I used to test and indeed I confirm that updating to RC 3 did cause rebuilds to be slower. Though it didn't effect it as much as reported here.
In my case it seems that rebuilds got slower by ~1/2 seconds.
NB: During my changes I always performed the same change, to make sure that the same structure gets invalidated between rebuilds.
From the data I have collected it seems that the root cause is in the framework.
See below;
RC2 FW
RC2 CLI
Date: 2019-11-22T06:25:20.213Z - Hash: 61757ea00bdb4755664d
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 4366ms
: Compiled successfully.

Date: 2019-11-22T06:25:29.135Z - Hash: db4f6639d2b11631ad8f
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3488ms
: Compiled successfully.

Date: 2019-11-22T06:25:36.070Z - Hash: 469582319b4a9d3a45b4
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3462ms
: Compiled successfully.

Date: 2019-11-22T06:25:42.397Z - Hash: bea82073375796555c00
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3382ms
: Compiled successfully.

Date: 2019-11-22T06:25:47.412Z - Hash: db4cfc667c7862334345
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3283ms
: Compiled successfully.

Date: 2019-11-22T06:25:52.456Z - Hash: ef8332854f0d221f608c
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3342ms
: Compiled successfully.

Date: 2019-11-22T06:25:59.568Z - Hash: 83da808a4d7175d3a866
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3526ms
: Compiled successfully.

RC3 FW
RC3 CLI
Date: 2019-11-22T06:58:25.274Z - Hash: cac9e4d2daf3da96b404
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 5116ms
: Compiled successfully.

Date: 2019-11-22T06:58:31.466Z - Hash: bc67e02ad2c6a856f078
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 4607ms
: Compiled successfully.

Date: 2019-11-22T06:58:37.925Z - Hash: 5955be9ab92a0222e53d
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 4983ms
: Compiled successfully.

Date: 2019-11-22T06:58:44.537Z - Hash: e4e4af801781cba479d0
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 4980ms
: Compiled successfully.

Date: 2019-11-22T06:58:50.657Z - Hash: 1c42b3ffd199af2ba7ae
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 4498ms
: Compiled successfully.

Date: 2019-11-22T06:58:57.372Z - Hash: b897f8c5cb7eb1ba4d5c
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 4921ms
: Compiled successfully.

Date: 2019-11-22T06:59:03.378Z - Hash: a9cfa43446c4575dab35
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 4599ms
: Compiled successfully.

Date: 2019-11-22T06:59:10.142Z - Hash: b50b213a332db4f3509a
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 4524ms
: Compiled successfully.

Date: 2019-11-22T06:59:16.802Z - Hash: d22890a9d5bbfe951593
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 4645ms
: Compiled successfully.

RC3 FW
RC2 CLI
Date: 2019-11-22T06:32:07.440Z - Hash: f49789f3460ae7c3aa47
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 5336ms
: Compiled successfully.

Date: 2019-11-22T06:32:14.133Z - Hash: d8f440e00941ace9ceeb
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 5280ms
: Compiled successfully.

Date: 2019-11-22T06:32:20.726Z - Hash: ca559ae92ed9d66b5f43
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 5078ms
: Compiled successfully.

Date: 2019-11-22T06:32:27.347Z - Hash: 395a40960a6be0b3dca3
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 5484ms
: Compiled successfully.

Date: 2019-11-22T06:32:34.497Z - Hash: f4a27abcdbe06166990a
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 5507ms
: Compiled successfully.

Date: 2019-11-22T06:32:41.677Z - Hash: f48277a72dc3434c6759
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 5845ms
: Compiled successfully.

Date: 2019-11-22T06:32:49.778Z - Hash: a1e38bd966827b2fc290
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 4562ms
: Compiled successfully.

Date: 2019-11-22T06:32:56.651Z - Hash: f41478d074dd667fbe56
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 4757ms
: Compiled successfully.

RC2 FW
RC3 CLI
Date: 2019-11-22T07:05:29.655Z - Hash: 081c6486a15bd62d3878
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3510ms
: Compiled successfully.

Date: 2019-11-22T07:05:34.353Z - Hash: f0acf632f311fa4a2fc2
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3397ms
: Compiled successfully.

Date: 2019-11-22T07:05:39.392Z - Hash: 2d6303c583f3ccaa9808
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3883ms
: Compiled successfully.

Date: 2019-11-22T07:05:44.258Z - Hash: e20012c939694c8ba192
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3456ms
: Compiled successfully.

Date: 2019-11-22T07:05:48.566Z - Hash: 0c8dda68b90194ac0ea1
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3180ms
: Compiled successfully.

Date: 2019-11-22T07:05:52.960Z - Hash: a6f5c0a2bf594099241a
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3396ms
: Compiled successfully.

Date: 2019-11-22T07:05:57.435Z - Hash:<PHONE_NUMBER>f697f21a29
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3385ms
: Compiled successfully.

Date: 2019-11-22T07:06:02.331Z - Hash: a3f80d23c2065a915f76
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3549ms
: Compiled successfully.

Date: 2019-11-22T07:06:07.036Z - Hash: a9887d887242446589f1
5 unchanged chunks
chunk {main} main.js, main.js.map (main) 14.3 MB [initial] [rendered]
Time: 3398ms
: Compiled successfully.

I can confirm FW rc2 is 3x faster than FW rc3
And FW rc1 is even more 3x faster than FW rc2
Here is my tests

NOTE: > when im using CLI rc3 it is with i18n localize migration in angular.json (tests with CLI RC2 is without i18n migration)

FW RC 3 - CLI RC 3
See detail https://gist.github.com/elvisbegovic/b3b6b5dd0110435c9309a3cade76bd66
First build: 77737ms
Trigger rebuild in same file by adding console.log(1): 23926ms
Repeat same trigger 5 times: 19327ms ->17839ms ->18569ms ->17566ms -> 18098ms
FW RC2 - CLI RC3
See detail https://gist.github.com/elvisbegovic/5a1e67049e44de88a0e7932a30686e19
First build: 106074ms
Trigger rebuild in same file by adding console.log(1): 7012ms
Repeat same trigger 5 times: 6413ms -> 6069ms -> 6663ms -> 6120ms -> 7453ms
FW RC2 - CLI RC2
See detail https://gist.github.com/elvisbegovic/365154f7ceed6ca169db12aa5c026db2
First build: 98092ms
Trigger rebuild in same file by adding console.log(1): 7587ms
Repeat same trigger 5 times: 6338ms -> 6314ms -> 6873ms -> 6224ms -> 7302ms
FW RC1 - CLI RC2
See detail https://gist.github.com/elvisbegovic/de0c85fca88cee17aee3ba6c14aa62b3
First build: 99934ms
Trigger rebuild in same file by adding console.log(1): 4678ms
Repeat same trigger 5 times: 2659ms -> 2742ms -> 2462ms -> 2218ms -> 2114ms


Why is Sørensen–Dice coefficient better?

Finds degree of similarity between two strings, based on Dice's Coefficient, which is mostly better than Levenshtein distance.

What's the rationale behind this claim?

I don't think so. The accuracy or distance similarity is very partial when presented against two distinct topics.


How do I run this sample code on iOS?

There is no iOS option in the run configuration. How can I launch it on the iPhone simulator?
thanks

The sample is a legacy iOS configure, you need to run the sample by command ./gradlew :sample:todo:ios:iosDeploySimulatorDebug, I do have a plan to migrate the sample.

Thank you for your response.
What can I do to run the sample code on any physical iOS device?

At present, it is not possible to execute the sample code on iOS, it is necessary to transition the sample code to the new Compose Multiplatform project.


Feature request: set "resume" as default

I would like to set the "resume playback" option as default for all my new created folders.
Is that possible?
Cheers Maik

see possbile workaround at
https://github.com/MiczFlor/RPi-Jukebox-RFID/issues/588


⚠ Fortnite has degraded performance

In b374a83, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 200
Response time: 1581 ms

Resolved: Fortnite performance has improved in 5af0db6.


Don't error out for empty response.

grpc will not set a field that's set to its default value. So, if the
api should be returning an empty string or an empty list, for example,
operation.py currently throws an error because the response isn't set.
In fact, though, the response is just set to the default value, which
doesn't get serialized over the wire.

@jerjou Thanks for the patch!  We will need to add a unit test which exercises the "empty response" case.

Sure! Updated the existing unit test for the new behavior.
Wasn't sure how to run the tests, but hopefully this'll work?

Actually - I might have my analysis wrong. Let me investigate, and I'll ping this PR again once I'm ready again..

@jerjou Any update?

Sorry - there's always five things to do at once, and five stakeholders wondering why they're not done yet --. Preliminary investigation seems to indicate that the server change that I made didn't cause this problem (it occurs even on a server running a version just before the change), but I'd like to investigate more. Unfortunately, there're always other priorities --. Let me close this PR for now, and I'll reopen when I'm more confident.

Just to close the loop on this - turns out it was a server error.


Add fullscreen and remote control presentation support

Add impress.js updated blackout and fullscreen plugins
This update add support for remote control presentation buttons:

blackout: using '.' key detection
fullscreen: enter with F5 and exit with ESC

Next and previous slides using PageUp/PageDown are already supported

Add autoplay pause on blackout and resume when removeBlackout
Add events to pause/resume autoplay

impress:autoplay:pause
impress:autoplay:resume
Call those events from blackout

On firefox, after blackout, slides where partially rendered.


Fix misprinted - in name of the folder

Reviewed-by: Volodymyr Babchuk<EMAIL_ADDRESS>


Folder name and file name are not separated in error about illegal characters

Expected Behaviour
File path in error is clear, example: /folder/filename
Actual Behaviour
Folder name is not separated from file name in 'This file contains illegal characters' error, example: /folderfilename
Reproduce Scenario (including but not limited to)
Steps to Reproduce

Install extension
Add project to extension
Select file with  !@# characters in name
Click on Preview button on action bar

Platform and Version
Chrome 131.0.6778.86
Sidekick v7.1.2

@Adobe-G11N-I18N-L10N-Team Can you please specify the content source used (Google Drive or SharePoint) as well as the exact folder and filenames used in the test?

@rofe Issue is reproducible on Sharepoint and Google Drive. In both cases folder name is "folder" and filename is "filename!"

:tada: This issue has been resolved in version 7.1.3 :tada:
The release is available on:

GitHub release
v7.1.3

Your semantic-release bot :package::rocket:

Issue is fixed, verified on 7.1.3


cmd/go: we're fetching github.com?go-get=1

I just noticed with "go install -v" that we're fetching https://github.com?go-get=1, which seems wrong:
dev:barlogaamp $ GO111MODULE=on go install -v
Fetching https://golang.org/x/crypto/ssh?go-get=1
go: finding github.com/bradfitz/private/sonos latest
Parsing meta tags from https://golang.org/x/crypto/ssh?go-get=1 (status code 200)
get "golang.org/x/crypto/ssh": found meta tag get.metaImport{Prefix:"golang.org/x/crypto", VCS:"git", RepoRoot:"https://go.googlesource.com/crypto"} at https://golang.org/x/crypto/ssh?go-get=1
get "golang.org/x/crypto/ssh": verifying non-authoritative meta tag
Fetching https://golang.org/x/crypto?go-get=1
Parsing meta tags from https://golang.org/x/crypto?go-get=1 (status code 200)
go: finding github.com/bradfitz/private latest
Fetching https://github.com?go-get=1
Parsing meta tags from https://github.com?go-get=1 (status code 200)
go: finding golang.org/x/crypto/ssh latest
Fetching https://golang.org/x/crypto?go-get=1
Parsing meta tags from https://golang.org/x/crypto?go-get=1 (status code 200)
get "golang.org/x/crypto": found meta tag get.metaImport{Prefix:"golang.org/x/crypto", VCS:"git", RepoRoot:"https://go.googlesource.com/crypto"} at https://golang.org/x/crypto?go-get=1
go: finding golang.org/x/crypto latest
go: import "github.com/bradfitz/private/barlogaamp" ->
        import "github.com/bradfitz/private/sonos": cannot find module providing package github.com/bradfitz/private/sonos

My program's imports are:
package main

import (
        "context"
        "log"
        "time"

        "golang.org/x/crypto/ssh"
        "github.com/bradfitz/private/sonos"
)

Where github.com/bradfitz/private is a private github repo.
In my ~/.gitconfig I have:
[url<EMAIL_ADDRESS>     insteadOf = https://github.com/

Seems like this only affects modules mode.

That probably comes from this loop:
https://github.com/golang/go/blob/f2131f6e0c6ca016143fc402d9d01f6a730f97cd/src/cmd/go/internal/modload/import.go#L153-L183
(I'm attempting to factor it out in https://golang.org/cl/128136, but that probably doesn't change the symptom.)
Perhaps we should hard-code some well-known constraints on module paths: for example, paths beginning with github.com must have at least two subsequent path components. That would at least save some lookup latency for modules that can't be fetched (#26874).
Are you able to fetch the private repos otherwise? (That's #26134 in general, I think.)

Are you able to fetch the private repos otherwise? (That's #26134 in general, I think.)

No. I'll leave a comment there.


[DNM] pause: Implement full unit test coverage

Relying on vcMock framework introduced in virtcontainers library,
this commit raises the unit test coverage of pause.go file to 100%.
Fixes #394

Waiting for https://github.com/clearcontainers/runtime/pull/471 to be merged first.

Ready to be merged now.

Coverage increased (+1.01%) to 78.278% when pulling 540d5170d18fe77751abc0b2c7f8bfbb40d13407 on sboeuf/unit_test_pause into 7b2b0778c96af991681fa5d074e4bcfde46c3256 on master.

lgtm


Empty close reasons

When websocket gets closed because of maxPayloadLength exceeded, it closes with 1006 and empty reason data.
Would it be possible to have option to turn on details for close reasons?
I would like to monitor socket closes also log if someone gets disconnected for exceeded payload length to know that there is something wrong client side and its sending unexpected sized messages or in case of attempted DoS attack etc.
I could also do this on message handler but would that be good idea?
Thanks

There's no logging or way to know why a WebSocket was closed other than if the client sends a reason. I agree that's problematic but would require an API breaking change to fix and would be more complex to use.
Maybe do logging in a proxy?

I will do it in JS side for now and manually call ws.close if packet size exceeds the threshold.

That's not a good production solution as it really doesn't hinder anyone from sending too large messages. You get the messages after they have been received so denying them at that point has no use.
Maybe the best solution is to just reserve some non-standard close codes for internal use.

I thought if someone sends really big packet and gets disconnected immediately, it would still mitigate it a lot because for sending more that big packets he would need to reconnect.
Yeah, using the non-reserved close codes could work.

Also what does the maxPayloadLength check?
Is it payload size of single received packet which might be part of larger message?

maxPayload is a limit to how big WebSocket messages will be received no matter how they are fragmented. This check runs in the very tip of the header so the server will force close any connection trying to send a bigger message than what's allowed. This is different from what you talk about, receiving it in full then ignoring it.