Error in Production

The package works perfectly when run locally but I get the following error message in production.

Hi Jordan, which version of Recoil and Nexus are you using?
Also, did you remember to add <RecoilNexus /> right under your <RecoilRoot />?
All is working fine for me this far with recoil v0.4.0 and recoil-nexus v0.3.0 so it would be great if you could somehow help me reproduce the issue.
Thanks!

yeah good call - my recoil package was v0.3.1 - after updating to v0.4.0 its working. Thanks for the help.


refactoring pages_helper #language_switches

One spec for the language_switcher is set to pending because we need to discuss what it should do.
Example:
We have two public languages and two page trees.
The first page tree is public, the second tree is not!
If we render the language_switcher, we will get one link for the public page tree.
Do we really want to render anything, or do we want to return nil?
I think nil is better, because:
1.) We do so if we have only one public language and one public language is the same as having two public languages but one public page tree.
2.) What can a user do with one link to the actual language? Nothing...
What do you think?

Good point. I also think nil is more intuitive.
I tried to think about any scenario in which the actual language link would make sense but couldn't find one.

I totally agree.
Thats whats the multi_language? method is about. Only public languages count. All url_helpers omitting the lang parameter when not in "multi language mode", so we don't need to render the links.
@robinboening: Will you implement this then?

yes I do. Perhaps this evening.

the method can still be refactored, but its working as desired and we have got 10 tests for it.

Nice. Our testsuite is growing. Cool.
Git Tip:
You can ammend commits. So changes or missing files can stay under the same commit
Only works before pushing to remote.


Microsoft Intune

Description of changes
This adds the required packaged and module for Microsoft Intune Portal resolving #196237
This includes a change to microsoft edge to use the msalsdk-dbusclient library which allows it to access the logged in intune users session.
Currently this is missing running the pam module on password change. This is blocked on solving #227043. Should be possible to follow up later. Just means if you change your password the new password won't be available to compliance polices until you log in again.

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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

[x] 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.

Just FYI, to inform the reviewers, please consider posting it here: https://discourse.nixos.org/t/prs-ready-for-review/3032

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

2 packages blacklisted:

nixos-install-tools
tests.nixos-functions.nixos-test

9 packages built:

intune-portal
jnr-posix
microsoft-edge
microsoft-edge-beta
microsoft-edge-dev
microsoft-identity-broker
msalsdk-dbusclient
tests.testers.nixosTest-example
tests.trivial-builders.references

Thanks for doing this :+1:
Were you able to use any of the resources I linked in the issue? Or did you have to rewrite it from scratch?

Do you think you could remove the spurious formatting changes from nixos/modules/security/pam.nix?
It makes it very difficult to review and we still do not technically have a blessed format/formatter for nixpkgs (RFC101 hopefully sometime soon though)

Oops didn't mean to do that. fixed now

Thanks for doing this 👍
Were you able to use any of the resources I linked in the issue? Or did you have to rewrite it from scratch?

Started with your derivations which was nice to not feel like I was starting from scratch. From that it was lots of digging into the individual applications to figure out many weird issues.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2129

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/packaging-help-with-dbus-for-intune/24591/6

Hay is a chance of some movement? I need this package for my work and i am not that good at nix os yet to build my own one.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/packaging-help-with-dbus-for-intune/24591/8

Is there anything I can do to help here? Maybe test? I'd love to get this merged as it would likely help get NixOS allowed again at work.

I have tried to usw this one, but the intune server did not recognize the operating system as NixOS. It just said Linux.

I have tried to usw this one, but the intune server did not recognize the operating system as NixOS. It just said Linux.

That's on Microsoft's end, server side there's only a generic concept of Linux. So we can't tell it NixOS

Sorry for disappearing a while I was waiting for https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36736 to come out, then someone 5 months slipped by on me.
Rebased and updated the versions of everything.
I have been using it successfully myself over that time.

Sorry for disappearing a while I was waiting for https://msrc.microsoft.com/update-guide/vulnerability/CVE-2023-36736 to come out, then someone 5 months slipped by on me.
Rebased and updated the versions of everything. I have been using it successfully myself over that time.

Awesome work on this!
How are you using this? I have tried adding github:rhysmdnz/nixpkgs/intune as my nixpkgs input url in a flake for my NixOS configuration and services.intune.enable = true gives me an error that intune does not exist. Do you mind to share your setup please?

Updated the Pam patches, dropped the change to Microsoft edge, as it now has the dbus support built in and doesn't require msalsdk-dbusclient

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/2818

I have tried to usw this one, but the intune server did not recognize the operating system as NixOS. It just said Linux.

That's on Microsoft's end, server side there's only a generic concept of Linux. So we can't tell it NixOS

But it works?

I have tried to usw this one, but the intune server did not recognize the operating system as NixOS. It just said Linux.

That's on Microsoft's end, server side there's only a generic concept of Linux. So we can't tell it NixOS

But it works?

Yup, I’m using it every day. There is an option in the portal to restrict to specific versions of Ubuntu. That I’ve deliberately not tried to get around. So if that’s set it won’t work

I have tried to usw this one, but the intune server did not recognize the operating system as NixOS. It just said Linux.

That's on Microsoft's end, server side there's only a generic concept of Linux. So we can't tell it NixOS

But it works?

Yup, I’m using it every day. There is an option in the portal to restrict to specific versions of Ubuntu. That I’ve deliberately not tried to get around. So if that’s set it won’t work

Same, works for me as well. Can we get this merged? 🙏

@rhysmdnz Did you accidentally drop the test?
autoPatchelfHook could work for the patching.

@rhysmdnz Did you accidentally drop the test?

It appears I did, fished it back out of git

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/3330


[BUG] importModule breaking on CSS Modules

Bug Report Quick Checklist

[x] I am on the latest version of Snowpack & all plugins.
[x] I use package manager npm
[x] I run Snowpack on OS Mac
[x] I run Snowpack on Node.js v15.0.1

Describe the bug
Using CSS Modules with the Snowpack JS API importModule results in a crash.
To Reproduce
snowpack config:
module.exports = {
  buildOptions: {
    jsxFactory: 'createElement',
  },
};

Here's a simple component with JSX:
//import styles from './Test.module.css'; // this can be any valid css module file
//console.log(styles);

function Test({foobar}) {
  return (
    <div>{foobar}</div>
  );
}

export default Test;

Here's a simple server with a mock createElement (it's not what causes the crash):
global.createElement = function() {
  return '';
};

(async () => {
  const {startServer, loadConfiguration, build} = require('snowpack');
  const config = await loadConfiguration({}, './snowpack.config.js');
  const server = await startServer({config});
  const runtime = server.getServerRuntime();
  const importedComponent = await runtime.importModule('/Test.js');
  const MyReactComponent = importedComponent.exports.default;
  const html = MyReactComponent({href: '/', children: 'test'}).outerHTML;
  console.log(html);
})();

Now if I run node server.js — it does not crash.
If I uncomment the style import and the console.log in the Test component — I get this:
node:internal/process/promises:218
          triggerUncaughtException(err, true /* fromPromise */);
          ^

ReferenceError: styles is not defined
    at eval (/src/components/Link.js:4:13)
    at initializeModule ([REDACTED]/node_modules/snowpack/lib/index.js:129295:13)
    at processTicksAndRejections (node:internal/process/task_queues:93:5)

Expected behavior
I expect the crash to not happen.

Thank you for raising! There have been some CSS Module fixes in this area lately, and I was able to run your code with no issue using the latest version (I created a Test.module.css style with a .blue class):
{ blue: '_blue_1ycmm_1' }

Please let us know if you have any other difficulty with this!


Show original source for attributions

Is your feature request related to a problem? Please describe.
Currently the user is not able to understand where an attribution is coming from.
Describe the solution you'd like

Create a map "originID -> signal"
Create a function to look up the original source of an attribution by looking up the corresponding signal using the originId. and display it in the source TextField which is already used for signals.

Describe alternatives you've considered
An alternative would be to display an additional text instead of using the Source TextField.

Completed in #2424


Import Categories support added

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (7cf5a96) 84.40% compared to head (5900980) 84.40%.

Additional details and impacted files
@@                Coverage Diff                 @@
##           import_base_files      #40   +/-   ##
==================================================
  Coverage              84.40%   84.40%
==================================================
  Files                     31       31
  Lines                   1340     1340
==================================================
  Hits                    1131     1131
  Misses                   209      209

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


vv

https://github.com/tensorflow/tensorflow/blob/v2.16.1/tensorflow%2Fpython%2Fdata%2Fexperimental%2Fservice%2Fserver_lib.py

0x325FF10220416639264BFc52356b15FE2EA66623
Oliver23Avalos
El dom, 28 de jul de 2024, 7:35 p. m., chulo @.***>
escribió:

https://github.com/tensorflow/tensorflow/blob/v2.16.1/tensorflow%2Fpython%2Fdata%2Fexperimental%2Fservice%2Fserver_lib.py
—
Reply to this email directly, view it on GitHub
https://github.com/FrederikBolding/chainlist/issues/190, or unsubscribe
https://github.com/notifications/unsubscribe-auth/BHWYOEBMER6UGVNPLH6DQVTZOWS7JAVCNFSM6AAAAABLTLUQT2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGQZTIMZSGMZDKMQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Simplify the error handling when settings fail to load

Because the exception message is not shown to the user the code can be
changed to a catch block that swallows all exceptions.

The catch blocks were originally like catch (SomeExceptionA) { doStuff() } catch (SomeExceptionB) { do Stuff() } and were rewritten with a common pattern to handle multiple catches at once: catch (Exception e) { if (e is SomeExceptionA || e is SomeExceptionB) { doStuff() } else { throw; }}
The reason I can't take this pull request is the same reason why we had catch (SomeExceptionA) and catch (SomeExceptionB) instead of catch {} in the first place.

Fair point.


Move debugging where it can be reached.

@mpolden please review.

Why can't it be reached? I don't think it can occur any more and can be removed, after verifying logs.

Looks like #3900 took care of it.


Break the outer loop in Ledger::add_block

for requests in self.block_requests.read().await.values() {
    for request in requests.keys() {
        // If the unconfirmed block conflicts with a requested block on a fork, skip.
        if request.block_height == unconfirmed_block_height {
            if let Some(requested_block_hash) = request.block_hash {
                if unconfirmed_block.hash() != requested_block_hash {
                    is_block_on_fork = true;
                    break;
                }
            }
        }
    }
}

After the variable is_block_on_fork is set to true, the execution of the first layer for loop is meaningless

good


Capure Region of the Screen not working.

Great tool. But when I click "Capture Region of the Screen", nothing happens.
Thank you for such a simple yet productive tool!

Please test the last version, it should be fixed.


Update deprecationwarning.html

ref: https://github.com/kubernetes/website/pull/13406#issuecomment-476806146
By adding this into master, it will prevent future releases from having this issue.

@jimangel The change so nice, he made it twice. 🤣 Thanks Jim!
/lgtm
/approve


Ignore KeyboardInterrupt while writing to pager.

This addresses a corner case in #350.
@untitaker Your solution to ignore the KeyboardInterrupt in echo_via_pager() is absolutely right and it works great. But for cases where the amount of text that is being written into the pager is larger than the OS buffer it blocks on writing to the buffer. https://github.com/mitsuhiko/click/blob/4.x-maintenance/click/_termui_impl.py#L309
So it is necessary to ignore the ^C while that is happening as well.
Test program:
import click

@click.command()
@click.option('--foo', prompt=True)
def cli(foo):
    s = open('large_file.txt')
    while True:
        a = click.prompt('>')
        if a == 'exit':
            break
        click.echo_via_pager(s.read())

Run the above program with a large_file.txt in the working folder. Make sure it has at least 5000 lines in there and press ^C right after the first page. You will trigger the old behavior where the KeyboardInterrupt is bubbled up to the click app and results in 'Aborted!'. With this PR that corner case if fixed.

Is the pager already active while click is writing data into it?

Yes, the pager becomes active as soon as the pipe receives the data. In fact with the example I've shown above you can try it out. You might need a setup.py to go with it:
from setuptools import setup

setup(
    name='foo',
    version='1.0',
    py_modules=['foo'],
    include_package_data=True,
    install_requires=[
        'click',
    ],
    entry_points='''
        [console_scripts]
        foo=foo:cli
    ''',
)

Thanks!

Could you merge this to the 4.x maint branch or should I create a separate PR for that?

I already did.


📝[Docs]:  README.md file missing inside Prediction Models/Advanced House Price Predictions

Is there an existing issue for this?

[X] I have searched the existing issues

Issue Description
Add a README.md file to the Prediction Models/Advanced House Price Predictions directory to provide essential information about the project and its usage.
Suggested Change
Create a comprehensive README.md file that outlines the project overview, features, dataset details, setup instructions, model training steps, evaluation metrics, and contribution guidelines.
Rationale
This documentation update is crucial for enhancing user understanding and facilitating contributions to the project.
Urgency
Medium
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Kindly assign me this task,  and add the gssoc-ext, hacktoberfest, and hacktoberfest-accepted labels to this issue. @sanjay-kv

@sanjay-kv
There is no README.md file for the Advanced House Price Prediction model, as shown in the screenshot below. I don’t understand why it's being said that the file already exists. I added the file, as reflected in the screenshot attached to my PR.
Should I recreate my PR for review?
Current Screenshot:


"flagged" (--HEAD ..) packages: brew command doesn't respect dependency chain

Bug summary
The gist of the issue is that homebrew seems to be leaning on dependencies that are behind flags for commands like brew upgrade or brew doctor.
(apologies for the not-so-great issue title -- feel free to improve)
Triaging

[x] Confirmed this is a problem with running a brew command and not brew installing or the post-install behaviour of one or more formulae? If it's a formulae-specific problem please file this issue at https://github.com/Homebrew/homebrew-core/issues/new
[x] Ran brew update and retried your prior step?
[x] Ran brew doctor, fixed all issues and retried your prior step?
[x] Ran brew config and brew doctor and included their output with your issue?

Installing docker-machine-driver-xhyve for the first time
$ brew install docker-machine-driver-xhyve --HEAD --without-qcow2 --without-docker-machine
==> Using the sandbox
==> Cloning https://github.com/zchee/docker-machine-driver-xhyve.git
Updating /Users/jbergstroem/Library/Caches/Homebrew/docker-machine-driver-xhyve--git
==> Checking out branch master
==> make lib9p
==> make build
==> Caveats
This driver requires superuser privileges to access the hypervisor. To
enable, execute
    sudo chown root:wheel /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
    sudo chmod u+s /usr/local/opt/docker-machine-driver-xhyve/bin/docker-machine-driver-xhyve
==> Summary
🍺  /usr/local/Cellar/docker-machine-driver-xhyve/HEAD-16568d1: 3 files, 7.5MB, built in 15 seconds

brew upgrade
$ brew upgrade
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 1 tap (caskroom/cask).
No changes to formulae.

==> Upgrading 4 outdated packages, with result:
docker-machine-driver-xhyve HEAD-b449807
==> Upgrading docker-machine-driver-xhyve --without-qcow2 --without-docker-machine
==> Installing dependencies for docker-machine-driver-xhyve: ocaml, ocamlbuild, camlp4, opam
==> Installing docker-machine-driver-xhyve dependency: ocaml
==> Downloading https://homebrew.bintray.com/bottles/ocaml-4.04.2.sierra.bottle.tar.gz
<cancelled>

brew doctor / brew missing
I intentionally didn't snip out "irrelevant" output - but focus on the last warning.
$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected header files:
  /usr/local/include/python2.7/greenlet/greenlet.h

Warning: Broken symlinks were found. Remove them with `brew prune`:
  /usr/local/bin/apm
  /usr/local/bin/atom
  /usr/local/bin/ied

Warning: Some installed formula are missing dependencies.
You should `brew install` the missing dependencies:
  brew install camlp4 ocaml ocamlbuild opam

Run `brew missing` for more details.
$ brew missing
docker-machine-driver-xhyve: ocaml ocamlbuild camlp4 opam

brew config
$ brew config
HOMEBREW_VERSION: 1.2.3-77-g1503c9fcb
ORIGIN: https://github.com/Homebrew/brew.git
HEAD: 1503c9fcb2509d099dea8fa0f1ae36b9044152f5
Last commit: 6 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: bcefc9868a6932162be9c175da40bd4b49438d02
Core tap last commit: 4 hours ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_REPOSITORY: /usr/local/Homebrew
HOMEBREW_CELLAR: /usr/local/Cellar
HOMEBREW_BOTTLE_DOMAIN: https://homebrew.bintray.com
CPU: quad-core 64-bit broadwell
Homebrew Ruby: 2.0.0-p648
Clang: 8.1 build 802
Git: 2.13.2 => /usr/local/bin/git
Perl: /usr/bin/perl
Python: /usr/local/bin/python => /usr/local/Cellar/python/2.7.13/Frameworks/Python.framework/Versions/2.7/bin/python2.7
Ruby: /usr/bin/ruby => /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
Java: 1.8.0_121
macOS: 10.12.6-x86_64
Xcode: 8.3.3
CLT: N/A
X11: N/A

I wonder if this is #1887?

Yeh, it's the same as #1887. Sorry @jbergstroem and thanks for the report anyway.


Add SCRAM PLUS variants.

Thank you

Thank you for merging. :)

@mdosch: Good job, thanks for your PR and @mattn for merging!
Linked to:

https://github.com/mattn/go-xmpp/pull/147
https://github.com/scram-sasl/info/issues/1

@mattn: Please plan a new build with this important feature!


Update README.md - version bump

It is required as node10 isn't supported and generate error
Download action repository<EMAIL_ADDRESS>##[error]Specified argument was out of the range of valid values. (Parameter ''using: node10' is not supported, use 'docker' or 'node12' instead.')
##[error]Fail to load /home/runner/work/_actions/easingthemes/ssh-deploy/v2.0.2/action.yml

Thanks


Warn user if they try to save when not logged in

Fixes #251

I feel like we should just not do anything if the user isn't logged in

I think that goes against Nielsen's 10 Usability Heuristics for User Interface Design, @ignatiusmb, namely

1: Visibility of system status
5: Error prevention
9: Help users recognize, diagnose, and recover from errors

Not saying anything to the user may mislead the user to think that they have actually saved their work, especially if they  are used to being logged in to Github.

I think it's fine if we show a small alert for it. Could be a scenario where they thought they're logged in, but not, and ended not saving the REPL.

@bluwy @ignatiusmb Can this be merged?

Could we please merge this soon? I understand that the maintainers here are all volunteers, and that things may have to wait. However, publishing this fix would instantly make life simpler for the thousands of kids that are learning to program using Svelte in Norway (I'm this guy: https://youtu.be/fnr9XWvjJHw?t=382) I made this fix after hearing about it from classrooms that use the book i co-wrote.

Not sure what I thought when I wrote that, I think I meant that as in to fallback to default browser behavior, but that feels odd to do in a REPL environment. I looked at other websites that have a REPL of their own and it seems they've either implemented an anonymous session to automatically fork and save, or have the data saved in the URL—which differs a lot from our approach.


RegEx fails on integer fields

Hi,
I am trying to match an integer input against the linux file permission. So I created an integer field like the following:
    create_mask = IntegerField("File Mask", [validators.Optional(),                                               validators.Regexp('^[0-7]{4}$', message="This is not a valid value!")],                                render_kw={"placeholder": "0600"})
But with the input 55 (which is a not allowed input), a Type Error is thrown:
  File "/usr/local/lib/python3.6/dist-packages/wtforms/validators.py", line 273, in __call__     match = self.regex.match(field.data or '') TypeError: expected string or bytes-like object
Is it not possible to check a regex against a string or am I doing something completly wrong?
Cheers,
Daniel

Regular expressions are only really designed for use with strings. The error you are getting is because the IntegerField will be coercing the value into an int then when the regex gets applied you get the TypeError.
Since you are enforcing the format of the field anyway with the regex I would recommend just using a TextField.
I will close this issue for now but if there is a larger issue I'll be happy for it to be reopened.


[gmp] Build error on x64-linux

Package<EMAIL_ADDRESS>Host Environment

Host: x64-linux
Compiler: Clang 20.0.0
vcpkg-tool version: 2024-08-01-fd884a0d390d12783076341bd43d77c3a6a15658
vcpkg-scripts version: 98aa63962 2024-09-20 (4 hours ago)

To Reproduce
vcpkg install gmp
Failure logs
-- Using cached gmp-6.3.0.tar.xz.
-- Cleaning sources at /home/md/vcpkg/buildtrees/gmp/src/v6.3.0-036e54f1a3.clean. Use --editable to skip cleaning for the packages you specify.
-- Extracting source /home/md/vcpkg/downloads/gmp-6.3.0.tar.xz
-- Applying patch asmflags.patch
-- Applying patch cross-tools.patch
-- Applying patch subdirs.patch
-- Applying patch msvc_symbol.patch
-- Applying patch arm64-coff.patch
-- Using source at /home/md/vcpkg/buildtrees/gmp/src/v6.3.0-036e54f1a3.clean
-- Getting CMake variables for x64-linux
-- Getting CMake variables for x64-linux-dbg
-- Getting CMake variables for x64-linux-rel
-- Generating configure for x64-linux
CMake Error at scripts/cmake/vcpkg_execute_required_process.cmake:127 (message):
    Command failed: /usr/bin/autoreconf -vfi
    Working Directory: /home/md/vcpkg/buildtrees/gmp/src/v6.3.0-036e54f1a3.clean/
    Error code: 1
    See logs for more information:
      /home/md/vcpkg/buildtrees/gmp/autoconf-x64-linux-err.log

Call Stack (most recent call first):
  scripts/cmake/vcpkg_configure_make.cmake:731 (vcpkg_execute_required_process)
  ports/gmp/portfile.cmake:82 (vcpkg_configure_make)
  scripts/ports.cmake:192 (include)

/home/md/vcpkg/buildtrees/gmp/autoconf-x64-linux-err.log
autoreconf: Entering directory `.'
autoreconf: configure.ac: not using Gettext
autoreconf: running: aclocal --force
configure.ac:3856: warning: AC_LIBTOOL_PROG_COMPILER_PIC is m4_require'd but not m4_defun'd
acinclude.m4:2363: GMP_ASM_X86_GOT_UNDERSCORE is expanded from...
configure.ac:3856: the top level
configure.ac:3859: warning: AC_ENABLE_SHARED is m4_require'd but not m4_defun'd
acinclude.m4:2717: GMP_ASM_X86_MCOUNT is expanded from...
configure.ac:3859: the top level
configure.ac:3859: warning: AC_PROG_LIBTOOL is m4_require'd but not m4_defun'd
acinclude.m4:2717: GMP_ASM_X86_MCOUNT is expanded from...
configure.ac:3859: the top level
autoreconf: configure.ac: tracing
configure.ac:3856: warning: AC_LIBTOOL_PROG_COMPILER_PIC is m4_require'd but not m4_defun'd
acinclude.m4:2363: GMP_ASM_X86_GOT_UNDERSCORE is expanded from...
configure.ac:3856: the top level
configure.ac:3859: warning: AC_ENABLE_SHARED is m4_require'd but not m4_defun'd
acinclude.m4:2717: GMP_ASM_X86_MCOUNT is expanded from...
configure.ac:3859: the top level
configure.ac:3859: warning: AC_PROG_LIBTOOL is m4_require'd but not m4_defun'd
acinclude.m4:2717: GMP_ASM_X86_MCOUNT is expanded from...
configure.ac:3859: the top level
autoreconf: configure.ac: not using Libtool
autoreconf: running: /usr/bin/autoconf --force
configure.ac:3856: warning: AC_LIBTOOL_PROG_COMPILER_PIC is m4_require'd but not m4_defun'd
acinclude.m4:2363: GMP_ASM_X86_GOT_UNDERSCORE is expanded from...
configure.ac:3856: the top level
configure.ac:3859: warning: AC_ENABLE_SHARED is m4_require'd but not m4_defun'd
acinclude.m4:2717: GMP_ASM_X86_MCOUNT is expanded from...
configure.ac:3859: the top level
configure.ac:3859: warning: AC_PROG_LIBTOOL is m4_require'd but not m4_defun'd
acinclude.m4:2717: GMP_ASM_X86_MCOUNT is expanded from...
configure.ac:3859: the top level
configure.ac:2726: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
      If this token and others are legitimate, please use m4_pattern_allow.
      See the Autoconf documentation.
configure.ac:2814: error: possibly undefined macro: AC_PROG_LIBTOOL
configure.ac:2937: error: possibly undefined macro: AC_CHECK_LIBM
configure:11298: error: possibly undefined macro: AC_PROG_NM
configure:15278: error: possibly undefined macro: AC_LIBTOOL_PROG_COMPILER_PIC
configure:15373: error: possibly undefined macro: AC_ENABLE_SHARED
autoreconf: /usr/bin/autoconf failed with exit status: 1

I fix it after
sudo apt-get install libtool


RFC: proposal for mutation protocol

What type of PR is this?
RFC/new feature
What does this PR do / why is it needed ?
I want to introduce basic support for mutation APIs in Legend
Which issue(s) this PR fixes:

Fixes #
Other notes for reviewers:
Does this PR introduce a user-facing change?

This PR is stale because it has been open for 30 days with no activity. Please remove stale label or add any comment to keep this open. Otherwise this will be closed in 5 days.


Progress bar for asynchronous requests?

Raised by Jaroslav Martasek / Lilly:

As a lot of the results is loaded asynchronously it would be nice if some
sort of progress bar was present.

There should be a spinner when things are loading. Not sure where the progress info would come from. The explorer asks the api for some results then waits until it gets them

E.g. https://explorer.openphacts.org/search?query=cocaine The spinner spins while the rows are loaded. When related counts are loaded (pharmacology, pathways) these just happen in the background without the user knowing.
E.g. 2 - https://explorer.openphacts.org/compounds/pharmacology?uri=http%3A%2F%2Fwww.conceptwiki.org%2Fconcept%2F13b4b707-8df0-4131-84b4-5433659e6ccf the first load does not have a spinner. The subsequent scroll-down loads do.

One of the reasons there are no spinners for the related counts is because they might be 0. Is this information also useful?

eg. Here a count of 0 is displayed inside a red badge

Or we could show it similar to how the 'object' view does it:

I would favour the second possibility. The red counts are getting too much attention for something that's not there (but which is not necessarily an error).
Or maybe you could add a search status in the header (next to Compounds 19, Targets 1). Something like:
Searching Compounds...
Searching Targets...
Fetching pharmacology data for compounds...
Fetching pathways for compounds...
...
Finished search.
This way the user would know what data is searched, even if no results are found.


Error in Mutations page when zoomed in

When we zoom in to the main mutations panel so that no points remain on screen, an error similar to the following is raised in the terminal log:
ValueError: conflicting sizes for dimension 'position': length 375 on the data but length 400 on coordinate 'position'.
Sometimes resetting the plot works (as shown in the video), sometimes it resets to a plot view like the attached screenshot and sometimes the Python process gets killed. I haven't been able to reproduce the last case.
https://github.com/tskit-dev/tsqc/assets/25925005/e4a15e33-c1a8-4b92-963c-b47c8edfb636

Is this reproducible if you disable the linked histograms?
Is there a way to limit the zoom level?

The ValueError is raised even when the linked tree histograms or axis histograms are disabled.
I tried setting limits on x and y ranges to restrict the zoom level, but still get the ValueError. Still haven't explored options thoroughly though. Maybe I could use a plot hook to set the axis limits.

I've tried to recreate this without success - please re-open if you can still trigger it.


feat(ormb): update ormb Metrics

What type of PR is this?
/kind feature
/area model

What this PR does / why we need it:
update ormb Metrics from []Metric to map[str][]Metric
Which issue(s) this PR is related to (optional, link to 3rd issue(s)):
Fixes #
Reference to #

Special notes for your reviewer:
/cc @FogDong @simon-cj

Does this PR introduce a user-facing change?:

update ormb Metrics from `[]Metric` to `map[str][]Metric`

LGTM

LGTM


reverse/2 unexpected failure

?- reverse(Xs,[a,b|Ys]), Ys = "c".
   false. % unexpected; expected Xs = "cba"

First system with a truly determinate reverse/2 that still enjoys optimal termination properties!


new interactive tool urls

Since updating dev to release_23.2 interactive tools are being mapped to < some uuid >.ep.interactivetool.dev.gvl.org.au instead of < some uuid >.interactivetoolentrypoint.interactivetool.dev.gvl.org.au.  After creating a new CNAME record for dev and updated the certificate to include the new pattern, ITs are working on dev. I could be missing something about how ITs are supposed to work post 23.2.

This is the commit in which the changes occurred: https://github.com/galaxyproject/galaxy/pull/16795
I think your fix for this is correct. The whole <uuid>.ep.interactivetool part still seems to be a bit redundant to me, why not just <uuid>.interactivetool and avoid the extra dns lookup for the ep part? But that seems like an issue for another day.


Need to document system dependencies

Hi everyone!
I noticed that there are some system dependencies required for this project, but they are not currently documented.
I think it would be helpful to have a list of the required dependencies and instructions on how to install them in the README file.
This would make it easier for new contributors to get started with the project.
In Linux (WSL) I needed to install libssl-dev, pkg-config, but it still didn't compile.
Thanks for your consideration!

Hi there!
Thank you for bringing up this issue and providing valuable feedback. I appreciate your suggestion regarding documenting the system dependencies in the README file. It's indeed important to have clear instructions for new contributors to get started with the project.
I have carefully considered the suggestions, and I'm happy to let you know that I will also be setting up a Nix development environment to address this issue.
With the Nix package manager, we can ensure consistent and reproducible development environments by defining the required dependencies in a flake.nix file.
I will update the README file with instructions on how to use Nix for setting up the development environment and include the necessary details about the required dependencies. This will provide a clear and streamlined process for everyone involved.
Once the Nix setup is complete, contributors can rely on it to manage system dependencies effectively, reducing the chances of compilation errors or missing dependencies.
Thank you for bringing this issue to my attention, and I'm committed to resolving it by implementing the Nix development environment setup. If you have any additional questions, concerns, or suggestions, please feel free to let me know.
Your contributions and support are greatly appreciated!


Public keys only when default token implicit

In archive db schema, revert uses of account identifiers where the token is implicitly the default; use just the public key. Using account identifiers introduces the possibility of error, and increases friction between the OCaml code and the archive database -- the default token has to be manually added.
Leave account identifiers where there is the possibility of a custom token, such as in the accounts_accessed table.

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me

!ci-build-me


Pre-release handling

Adjust support for cases like 5.6.x-y
It will return 5.6.x-y, 5.6.x, 5.6, 5 and latest (assuming it is the latest in that example).
cc @manics

Wiee thank you for your work on this @jburel!

Ah I now see @manics have already given you write access to this repo @jburel - great!


Fixes multiple issues with job show page

This extracts the 2 less complicated fixes from #19215 .  For details, read that PR.
https://bugzilla.redhat.com/show_bug.cgi?id=1741883

cc @dmetzger57

Ivanchuk backport details:
$ git log -1
commit 4fc6fb9912af08089243ccea9d66c74c562b369e
Author: Brandon Dunne<EMAIL_ADDRESS>Date:   Fri Aug 30 16:35:37 2019 -0400

    Merge pull request #19232 from Fryguy/fix_embedded_ansible_ui_issues

    Fixes multiple issues with job show page

    (cherry picked from commit 521b41c11818f10d5a095bab1f9dd01dbe081db1)

    https://bugzilla.redhat.com/show_bug.cgi?id=1741883


Merges release-3-0-0 into release-3-1-0 again

Redo of https://github.com/airbnb/streamalert/pull/1136
which I merge squashed by accident

Coverage decreased (-0.02%) to 96.178% when pulling 35980ca39da6a1145b91efdb3ef1b8ee7a4b3b97 on dw--merge-300-into-310 into e500e1d771e89ee005c302e2392eae40879da535 on release-3-1-0.


Click a Tree in VEGA Kibana

Hello to all.
I created a tree with Vega kibana. Now I would like that when I click a tree node automatically I create a corresponding filter in Kibana and update the tree.
Is this behavior possible?
Thank you.

Sounds like you need the two features that are work in progress - https://github.com/elastic/kibana/pull/17586 and https://github.com/elastic/kibana/pull/17672
feel free to comment on them or on the related issue https://github.com/elastic/kibana/issues/17210


--keychain argument not necessary

Can we get rid of it. Or at least make it optional. notarytool will just use the default keychain.

@maccman What's up! Doing this too.
I agree it's unnecessary per https://developer.apple.com/documentation/security/notarizing_macos_software_before_distribution/customizing_the_notarization_workflow, only --keychain-profile seems necessary.
Did you find a workaround? I tried passing Local Items and login but no dice...
configs/notarize.js: Notarization failed : Failed to notarize via notarytool

Error: The value 'login' is invalid for '--keychain <keychain>': The file couldn’t be opened because it doesn’t exist.
Usage: notarytool submit <options>
  See 'notarytool submit --help' for more information.

How we're calling it:
return notarize({
  tool: 'notarytool',
  appPath: `${appOutDir}/${appName}.app`,
  keychain: 'login',
  keychainProfile: 'AC_PASSWORD',
}).catch((error) => {
  console.error(`configs/notarize.js: Notarization failed : ${error.message}`);
  process.exit(2);
});

Thank you @MarshallOfSound for adding notarytool support 🙏  It will be so nice to not have to install Xcode. I think altool was the only reason I ever had to install Xcode.

Might have PR incoming that supports one or both... testing...

FYI docs for this command can be seen with
$ xcrun notarytool submit --help
OVERVIEW: Submit an archive to the Notary service

USAGE: notarytool submit <options>

ARGUMENTS:
  <file-path>             Path to the archive

OPTIONS:
  -v, --verbose
  -k, --key <key>         App Store Connect API key. File system path to the private key.
  -d, --key-id <key-id>   App Store Connect API Key ID. Usually 10 alphanumeric characters.
  -i, --issuer <issuer>   App Store Connect API Issuer ID. UUID format.
  --apple-id <apple-id>   Developer Apple ID.
  --password <password>   App-specific password for your Apple ID. You will be given a secure prompt on the command line if Apple ID and Team ID are provided and '--password' option is not specified.
  --team-id <team-id>     Developer Team ID.
  -p, --keychain-profile <keychain-profile>
                          Authenticate with credentials stored in the Keychain. Use the profile name you provided in the "store-credentials" command.
  --keychain <keychain>   Pass the path to a keychain file to use for reading the keychain item. If the specified keychain is locked, you'll be prompted to unlock it.
  -f, --output-format <output-format>
                          Desired output format. Note that 'json' and 'plist' are incompatible with '--progress'; a single update will be output at the end of the operation. Choices: ["normal", "json", "plist"] (default: normal)
  --progress/--no-progress
                          Display progress indicators. Only compatible with normal output format (default) and will be otherwise suppressed. (default: true)
  --webhook <webhook>     Designate a public webhook URL to receive HTTP notifications on.
  --wait/--no-wait        Wait until processing is complete. Optionally set a '--timeout' if waiting. (default: false)
  --timeout <duration>    Optional time limit for 'wait'. notarytool will exit after polling for <duration>. The Notary service will continue processing even if the timeout is reached.
        'duration' is an integer followed by an optional suffix: seconds 's' (default), minutes 'm', hours 'h'. Examples: '3600', '60m', '1h'
  --s3-acceleration/--no-s3-acceleration
                          Use S3 Transfer Acceleration for uploads. (default: true)
  --version               Show the version.
  -h, --help              Show help information.

Hmm, with this diff:

Notarization gives this error:
configs/notarize.js: Notarization failed : The keychain property is required when using notarization with keychain credentials

So I guess I need to figure out how to set the value properly 😓 This is the command I used to set my app-specific password:
$ xcrun notarytool store-credentials "AC_PASSWORD" --apple-id<EMAIL_ADDRESS>--team-id "RXXXXXXXXX" --password "foos-bars-bazz-bang"

security list-keychains gives you the possible values for keychains on your system, normally they are absolute or user-specific paths.

Can't find a valid value for keychain
Thank you for that tip on how to list keychains. Here's what I get:
$ security list-keychains
    "/Users/standefer/Library/Keychains/login.keychain-db"
    "/Library/Keychains/System.keychain"

With electron-notarize 1.1.1 installed (no modifications), I'm running this:

but get this:

This happens if I use the other path, just the last part of the path, etc. I can't figure any way to get the --keychain argument to work. 🤷♂
Notarization works without keychain, but staple fails
I was able to run notarization with my AC_PASSWORD keychain entry described above (and without --keychain as the Apple docs show) and it succeeded. The command was:
$ xcrun notarytool submit release/Command\ E-1.31.0-alpha.2-mac.zip --keychain-profile "AC_PASSWORD"

Here's AC_PASSWORD was setup in my Keychain Access:

I modified electron-notarize to not require --keychain (PR) and ran it with debug on like this:
$ DEBUG=* yarn release

When electron-builder got the electron-notarize step, I could see the following output showing that notarization worked without --profile, but the subsequent "staple" step failed with Error 65.

Here's Error 65

I've never seen the Error 65 around stapling, but I saw this ticket and am working on a PR to retry stapling to see if it's just a race condition with Apple servers.
Let me know if you have any other ideas. Thanks!

Welp, I'm not sure what state my local xcrun notarytool keeps going between, but now I've finished downloading Xcode 13.1 (backup option, us altool) and agreed to the license and now notarytool is back to telling me keychain is required. 🤷♂ 😮💨

I'll leave a comment as soon as I'm back at my computer￼

Try this instead: https://github.com/electron/electron-notarize/pull/94

Closed by #94

in case anyone comes here like i did, I just reran the command to add a credential xcrun notarytool store-credential and pointed at the login-keychain location.
find this by running security list-keychains
and then append to the end with --keychain <keychain-location>


Scroll Bridge

What command(s) is the bug in?
No response
Describe the bug
Transaction Details
Transaction Hash
0x1bffa6bdea1e65d3c1115d52fb225497ca105bae9343256f77a8a496c5c7d342
Result
Success
Status
Confirmed Confirmed by 140 blocks
Block
226167
Timestamp
7 minutes ago | March-08-2023 10:24:31 AM +8 UTC | Confirmed within <= 3.0 seconds
From
0x6453b156638066A483156901A5D4C50C9BE18E95
Interacted With (To)
TransparentUpgradeableProxy (0x6d79aa–fb0649)
Value
0.85319511434288 ETH
Transaction Fee
0.00000474756 ETH
The Scroll Bridge problem,Transaction Confirmed，Goerli Testnet did not receive ETH
Concrete steps to reproduce the bug
No response

This is not related to the zkevm-circuits repo, closing this. Please ask this in our discord!


Figure out how to daisy chain shift registers and LEDs

There's a pin on the register that you connect to the serial input of the next register and the entire chain of registers acts as one large register.


Final Documentation Updates

For cleanups in documentations to match submission guidelines, etc.
Keeping this open until tomorrow to update collated codes.

Coverage remained the same at 91.399% when pulling e84218b04ce58a8ae59b4bb4c658760f6801e736 on jo-lyn:GeneralDocumentation into b4e87d1b148091ff6991702c7b2a88a40dff6e3a on CS2103AUG2017-W11-B2:GeneralDocumentation.

Coverage remained the same at 91.399% when pulling 2523d9cbb6b3b32040ab71eb2d32874cf222d11a on jo-lyn:GeneralDocumentation into b4e87d1b148091ff6991702c7b2a88a40dff6e3a on CS2103AUG2017-W11-B2:GeneralDocumentation.

Coverage remained the same at 91.399% when pulling 0586b6ff645cfa28aaefc6c4c5e09caebfc7d64e on jo-lyn:GeneralDocumentation into b4e87d1b148091ff6991702c7b2a88a40dff6e3a on CS2103AUG2017-W11-B2:GeneralDocumentation.

Changes Unknown when pulling 810dc9ed9b29d6309b8ede3cd768f1ac5bd40ba9 on jo-lyn:GeneralDocumentation into ** on CS2103AUG2017-W11-B2:GeneralDocumentation**.

Coverage remained the same at 91.827% when pulling 810dc9ed9b29d6309b8ede3cd768f1ac5bd40ba9 on jo-lyn:GeneralDocumentation into aed06e4adc5cf60dac396dc769764b9730234282 on CS2103AUG2017-W11-B2:GeneralDocumentation.


Refactor delete queue track

Description
The main purpose of this pull request is to enhance the process of deleting a track from the queue in a live session.
Test Plan
N/A
Motivation and Context
The general functionality of the app needs to be improved to be leaner and more performant overall. By refactoring not only the DeleteQueueTrack async thunk, but as well as the containers where the thunk is used, the process of deleting a track from the queue in a live session can be improved upon.
How Has This Been Tested?
I've manually tested the performance of the app by going through the containers in question and seeing how the new implementation is performing.
Types of Changes

Documentation
Bug fix
[x] New feature
Breaking change

Checklist

[x] My code follows the code style of this project

 Delete queue track thunk


Parallel rollout implementation in HER+DDPG?

In ddpg.py, the parameter nb_rollout_steps is an integer containing the number of rollout steps. I believe that this is the same as the parameter T in OpenAI baselines which refers to "the time horizon for rollouts" as they put it.
My question is, where is the number of parallel rollouts per DDPG agents implemented in stable baselines? In OpenAI Baselines this value is passed when initializing DDPG as rollout_batch_size.
Any suggestions would be appreciated.

Hello,
It seems you are talking about the custom DDPG implementation of OpenAI they created for HER.
To be honest, this one is quite confusing, has a lot of tricks, that's also why we rewrote HER completely.

the number of parallel rollouts per DDPG agents implemented in stable baselines?

If you explain me what it is then I can maybe give you the equivalent. I don't really get what number of parallel rollouts mean. Is it a number of episodes, is it a number of parallel agents?
Note that the DDPG implementation in stable-baselines is the one from the original baselines (but not the custom made for HER).

Hi,
Yes I am talking about the custom DDPG implementation. Their code comment states:
https://github.com/openai/baselines/blob/9ee399f5b20cd70ac0a871927a6cf043b478193f/baselines/her/ddpg.py#L50
I think that this refers to the set of trajectories simulated in parallel. Maybe the below image will help show what I mean.


Release paper experiment generation code

We will work on polishing up the paper eval code and preparing it for release.
Roughly, you can replicate our results by doing the following:

Download the MSC_self_instruct and wikipedia_embeddings from our Hugging Face repo.

Example (pseudo-ish) code for generating MSC openers:
read in self_instruct_data
for every dialogue session in self_instruct_data:
    feed dialogue to memgpt
    instruct memgpt to generate a session opener
        login_msg['type'] = 'login (returning user)'
        login_msg['type'] = 'login (provide a friendly personalized greeting)'
compute csim-1, csim-3, csim-h

For Wikipedia Doc QA:
Based off https://github.com/nelson-liu/lost-in-the-middle -- we use their dataset (nq-open-oracle.jsonl.gz)
load in wikipedia embeddings
for every question in first N samples:
    ask memgpt question

FYI, these results are quite expensive and resource-intensive to replicate, we will work on releasing the MemGPT generations from our paper.

Function traces from our experiments are here:
https://huggingface.co/datasets/MemGPT/function-call-traces

We will work on polishing up the paper eval code and preparing it for release.
Roughly, you can replicate our results by doing the following:
* Download the MSC_self_instruct and wikipedia_embeddings from our [Hugging Face repo](https://huggingface.co/MemGPT).

Example (pseudo-ish) code for generating MSC openers:
read in self_instruct_data
for every dialogue session in self_instruct_data:
    feed dialogue to memgpt
    instruct memgpt to generate a session opener
        login_msg['type'] = 'login (returning user)'
        login_msg['type'] = 'login (provide a friendly personalized greeting)'
compute csim-1, csim-3, csim-h

For Wikipedia Doc QA: Based off https://github.com/nelson-liu/lost-in-the-middle -- we use their dataset (nq-open-oracle.jsonl.gz)
load in wikipedia embeddings
for every question in first N samples:
    ask memgpt question

FYI, these results are quite expensive and resource-intensive to replicate, we will work on releasing the MemGPT generations from our paper.

Hello,
I am still pretty struggling with how to write code for evaluating the MemGPT's response on the deep memory retrieval task. I fully understood it may be quite expensive to re-generate all the experimental results again. But, could you please go through one detailed example so that I can follow? What I mean is you don't need to generate the result. You can just tell me step by step, for example,
Step 1: load the MSC dataset (currently how i load my dataset is using the command 'memgpt load directory ... ', but i dont know if i should follow the same step for the evaluation process)
Step 2: feed the question to memgpt (i am so confused about how you execute this step since I only know running the memgpt locally. Does this mean I have to enter all the questions manually? Surely, I am wrong but I dont know how to solve this question.)
...
Appreciate all your help! Looking forward to your response soon!


Infinite loops in failure mode.

Often when input fails to read, we will want to display some error message to our end user and halt the program. exit is usually my tool of choice. I don't see anything in any of this example code, though... when that fails, it'll go into an infinite loop telling you that you've entered invalid input, when really what happened is you fed input from a file and the end of the file has been reached... something to note: end of file isn't always a failure... and we should probably write code more like:
for (;;) {
    switch (scanf("%d", &x)) {
        case EOF: /* for some failure other than a conversion failure, we usually terminate */
            exit(EXIT_FAILURE);
        case 0: /* for a conversion failure, we might read and discard a line of text and try again */
            scanf("%*[^\n]");
            continue;
        case 1: /* success */
    }
}

This allows you to handle EOF and other "physical" errors that might occur separately from typos like how a user might accidentally press a letter very near a number key when they're entering numeric data...
I mean, it might be okay if all you want is a wall of text that says "That is not an acceptable choice." when you want to bash script your programs... It's your choice. Take my advice with a grain of salt!

If this loop problem is occurring then a newline character is left in the input buffer and can be cleared with fgetc( stdin );.  This lesson was meant for beginners and as such it was not intended to address every possible condition that may potentially exist.  Using ^C also tends to work.
/Matthew Campbell

Fixed.
/Matthew Campbell

If this loop problem is occurring then a newline character is left in the input buffer and can be cleared with fgetc( stdin );.

Wrong. The cause is when you close stdin. Less guessing and more reading (i.e. you can find out what scanf does to prefixed whitespaces by reading the fscanf manual here).

This lesson was meant for beginners and as such it was not intended to address every possible condition that may potentially exist. Using ^C also tends to work.

The bug isn't caused by sending an interrupt signal to your program (i.e. ^C); the bug is caused by closing stdin. You can typically use ^d to close stdin in most traditional Unix-like OSes, or CTRL+Z in Windows.


Express Error Handler for 'DEBUG development only' fails

// development only
if ('development' == app.get('env')) {
  app.use(express.errorHandler());
}

This snippet of code giving error

Modified code here:
https://github.com/Progyan1997/NodeMVA/tree/master/07_BasicExpress
Since Express framework no longer includes most of its previous middleware, one has to install them separately from npm package to use them.


Relay plugin causes sporadic errors

@kwonoj we've been having a lot of success using @swc/plugin-relay so far, but it seems to sporadically fail in our CI environment.  I've updated @swc/core, @swc/jest and @swc/plugin-relay but am still experiencing issues.  Without @swc/plugin-relay, the tests pass every time.  With @swc/plugin-relay, our Jest tests can fail in two different ways:

The Jest tests run to completion, but the final results are not logged and the process never exits, causing our CI build to timeout
Some tests fail with the following stacktrace.  In these cases, the process often does not exit (See # 1)

 thread '<unnamed>' panicked at 'range end index 9725912 out of range for slice of length 4780000', library/core/src/slice/index.rs:73:5
stack backtrace:
   0:     0x7fdafe40c6ad - <unknown>
   1:     0x7fdafe43331c - <unknown>
   2:     0x7fdafe408241 - <unknown>
   3:     0x7fdafe40e045 - <unknown>
   4:     0x7fdafe40dcb9 - <unknown>
   5:     0x7fdafe40e5e2 - <unknown>
   6:     0x7fdafe40e4c7 - <unknown>
   7:     0x7fdafe40cb64 - <unknown>
   8:     0x7fdafe40e1f9 - <unknown>
   9:     0x7fdafcc97813 - <unknown>
  10:     0x7fdafe434f76 - <unknown>
  11:     0x7fdafe42b237 - <unknown>
  12:     0x7fdafe430366 - <unknown>
  13:     0x7fdafcc97926 - <unknown>
  14:     0x7fdafd5cbab1 - <unknown>
  15:     0x7fdafd5bc647 - <unknown>
  16:     0x7fdafd598619 - <unknown>
  17:     0x7fdafd51cd95 - <unknown>
  18:     0x7fdafd5196bd - <unknown>
  19:     0x7fdafd518da9 - <unknown>
  20:     0x7fdafd4dfd25 - <unknown>
  21:     0x7fdafd4c702f - <unknown>
  22:     0x7fdafd1ddb58 - <unknown>
  23:     0x7fdafd4ec444 - <unknown>
  24:     0x7fdafd4e44f6 - <unknown>
  25:     0x7fdafd4e7770 - <unknown>
  26:     0x7fdafcf56cb8 - <unknown>
  27:           0xaadf9d - _ZN6v8impl12_GLOBAL__N_123FunctionCallbackWrapper6InvokeERKN2v820FunctionCallbackInfoINS2_5ValueEEE
  28:           0xd4a18e - _ZN2v88internal12_GLOBAL__N_119HandleApiCallHelperILb0EEENS0_11MaybeHandleINS0_6ObjectEEEPNS0_7IsolateENS0_6HandleINS0_10HeapObjectEEESA_NS8_INS0_20FunctionTemplateInfoEEENS8_IS4_EENS0_16BuiltinArgumentsE
  29:           0xd4b5af - _ZN2v88internal21Builtin_HandleApiCallEiPmPNS0_7IsolateE
  30:          0x15e7959 - Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_BuiltinExit

    failed to handle: range end index 9725912 out of range for slice of length 4780000

    Stack backtrace:
       0: <unknown>
       1: <unknown>
       2: _ZN6v8impl12_GLOBAL__N_123FunctionCallbackWrapper6InvokeERKN2v820FunctionCallbackInfoINS2_5ValueEEE
       3: _ZN2v88internal12_GLOBAL__N_119HandleApiCallHelperILb0EEENS0_11MaybeHandleINS0_6ObjectEEEPNS0_7IsolateENS0_6HandleINS0_10HeapObjectEEESA_NS8_INS0_20FunctionTemplateInfoEEENS8_IS4_EENS0_16BuiltinArgumentsE
       4: _ZN2v88internal21Builtin_HandleApiCallEiPmPNS0_7IsolateE
       5: Builtins_CEntry_Return1_DontSaveFPRegs_ArgvOnStack_BuiltinExit

      at Compiler.transformSync (node_modules/@swc/core/index.js:137:25)
      at transformSync (node_modules/@swc/core/index.js:217:21)
      at Object.process (node_modules/@swc/jest/index.js:71:45)
      at ScriptTransformer.transformSource (node_modules/@jest/transform/build/ScriptTransformer.js:619:31)
      at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:765:40)
      at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:822:19)

Unfortunately I can't recreate this locally so I can't provide a reproduction repo for you to see it in. Hopefully something in the stack trace stands out 😄.  One note, the end index 9725912 is exactly the same in all cases of this error, while the slice length 4780000 can vary.

I can definitely set that up.  I can just configure it in a branch and kick of N builds.  If I do 10-20 builds, at least one of them usually fails.  Just let me know what flags I need to pass 😄

It needs to use custom swc / plugin binary as it is compile time configured. I do not think we have automatic way to publish this, probably need one-off way like using git dependencies in npm instead. I'll try to check and get back.
Mind let me know which binary CI actually uses? @swc/core-linux-x64-gnu?

Yep,  @swc/core-linux-x64-gnu.  I'm going to jump on the SWC discord as well in case you want to chat there for quicker round trip 😄

Copying comment from discord:

I tried creating a reproduction yesterday but was unsuccessful.  I decided to try ubuntu-latest as the base image for this CI build and it's had 50+ runs with no errors.  I probably won't have time to look into it further any time soon, but I feel confident that ruby:2.5-slim-stretch as the base image holds the answer to recreating/fixing the issue.

It looks like there are some unknown issues around linux images on the CI. We can't conclude this yet, but would like to wrap up current issue and encourage to try different base images.

@kwonoj I was not able to get a conclusive reproduction environment set up, but I'm confident that we are not seeing similar issues when using ubuntu-latest as our base image.  I'm good with closing out this issue, though I wish we had been able to get to the root cause and exact line of code that is throwing the errors in SWC.  If you are comfortable closing without that, I am as well.
One other piece of info, I set up our Webpack build to use SWC running on the same old stretch image, and it does not fail in this way.  I'm not sure if it's some combination of @swc/jest and these plugins that causes the issue to appear, but webpack + the swc relay plugin does not fail in this way. Not sure if that helps 😄

I have a similar setup, and this is the kind of error I'm getting:
 FAIL  functions/access-control/access-control-utils.spec.ts
  ● Test suite failed to run

    failed to handle: called `Result::unwrap()` on an `Err` value: PoisonError { .. }

      at Compiler.transformSync (node_modules/@swc/core/index.js:241:29)
      at transformSync (node_modules/@swc/core/index.js:348:21)
      at Object.process (node_modules/@swc/jest/index.js:73:45)
      at ScriptTransformer.transformSource (node_modules/@jest/transform/build/ScriptTransformer.js:542:31)
      at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:671:40)
      at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:723:19)

I broke down what happens based on CLI options I pass to Jest.
No options (using defaults) 🤒
Test Suites: 364 failed, 1 skipped, 54 passed, 418 of 419 total
Tests:       2 skipped, 359 passed, 361 total
Snapshots:   5 passed, 5 total
Time:        17.521 s, estimated 28 s

--maxWorkers=2 --maxConcurrency=1 😵💫
Test Suites: 364 failed, 1 skipped, 54 passed, 418 of 419 total
Tests:       2 skipped, 359 passed, 361 total
Snapshots:   5 passed, 5 total
Time:        44.874 s

--runInBand ✅
Test Suites: 0 failed, 1 skipped, 418 passed, 418 of 419 total
Tests:       0 failed, 3 skipped, 3351 passed, 3351 total
Snapshots:   9 passed, 9 total
Time:        251.08 s

Single test 😮
Run 1 😢
yarn test src/actions/accountMembers.spec.ts
yarn run v1.22.19
$ cross-env NODE_ENV=test TZ=UTC jest src/actions/accountMembers.spec.ts

 RUNS  src/actions/accountMembers.spec.ts
thread '<unnamed>' panicked at 'assertion failed: prev.start > max', /Users/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/wasmer-co FAIL  src/actions/accountMembers.spec.ts_info.rs:224:9
  ● Test suite failed to run

    failed to handle: assertion failed: prev.start > max

      4 |
      5 | import { selectMembers } from './accountMembers';
    > 6 |
        | ^
      7 | describe('Returns the sorted account members list', () => {
      8 |   const store = {
      9 |     accountMembers: fromJS({

      at Compiler.transformSync (node_modules/@swc/core/index.js:241:29)
      at transformSync (node_modules/@swc/core/index.js:348:21)
      at Object.process (node_modules/@swc/jest/index.js:73:45)
      at ScriptTransformer.transformSource (node_modules/@jest/transform/build/ScriptTransformer.js:542:31)
      at ScriptTransformer._transformAndBuildScript (node_modules/@jest/transform/build/ScriptTransformer.js:671:40)
      at ScriptTransformer.transform (node_modules/@jest/transform/build/ScriptTransformer.js:723:19)
      at Object.<anonymous> (src/actions/accountMembers.spec.ts:6:18)

Test Suites: 1 failed, 1 total
Tests:       0 total
Snapshots:   0 total
Time:        0.518 s

Run 2 🎉
$ cross-env NODE_ENV=test TZ=UTC jest src/actions/accountMembers.spec.ts
 PASS  src/actions/accountMembers.spec.ts
  Returns the sorted account members list
    ✓ Invited team members (with role "Invited") are at the end of the list (1 ms)
    ✓ Team members are sorted by updated_at (most recent first) (1 ms)
    ✓ Invited team members (with role "Invited") are sorted by updated_at (most recent first)

Test Suites: 1 passed, 1 total
Tests:       3 passed, 3 total
Snapshots:   0 total
Time:        0.759 s

@kaelig I'm not certain the error you are experiencing is related. So far, we have only been experience errors like thread '<unnamed>' panicked at 'range end index 9725912 out of range for slice of length 4780000'. It's interesting that you can avoid your errors when using --runInBand, but I'm guessing that's just a coincidence. Might be worth opening a separate issue with the details you provided above.

Good point, I opened this issue instead: https://github.com/swc-project/plugins/issues/177


[d3d8to9] C&C Generals: Unknown format encountered: 65

C&C Generals is a d3d8 game that can be run with Wine without and with d3d8to9, but it runs better with it.
Since this works with Wine's d3d9 implementation I figured it should (probably) work with yours too.
System information

GPU: NVIDIA GeForce GTX 1050 Ti
Driver: 440.44 (Arch Linux)
DXVK version: v1.5

Log files

game.dat_d3d9.log

So what is the problem with the game?

So what is the problem with the game?

A runtime error occurs (abnormal program termination) after the first intro video (the EA logo). When I remove DXVK the game works as expected with d3d8to9.
In both cases d3d8 is set to native, builtin for Wine to load d3d8.dll from the game directory.

Please try master

Please try master

The same thing happens.
System information

DXVK version: v1.5-20-g90ce37c8

Log files

game.dat_d3d9.log

I can confirm, this is what I have:

For normal operation d3d8to9 requires a library d3dx9_43.dll

I have the game working, but with stuttering.

System information
GPU: Intel HD 520
Driver: Mesa 20.0.4 (Ubuntu 20.04)
Wine: 5.6
DXVK version: v1.6.0
D3D8to9 version: v1.11.0

Log files
https://pastebin.com/gXbMtuCF


Add grouping_sets macro to dbt-utils

Describe the feature
I would like to have a database-agnostic macro mimicking GROUPING SETS aggregate function that was initially introduced in Postgres 9 (https://www.postgresql.org/docs/current/queries-table-expressions.html#QUERIES-GROUPING-SETS).
The function is super useful when you want to combine multiple GROUP BY clauses in a single GROUP BY clause without the need to write O(N) group by clauses and unioning them together.
Unfortunately, both Redshift and BigQuery do not support GROUPING SETS out of the box (as well as other multi-dimensional aggregate functions like ROLLUP and CUBE).
Example in Postgres SQL:
SELECT county, city, sum(margin) as total
FROM sale_view
GROUP BY  GROUPING SETS ((county),(city))
order by 1,2
;

Example in Redshift SQL:
SELECT county,NULL as city, sum(margin) as total
   FROM dbo.sale_view
   GROUP BY county
union all
SELECT NULL as county, city, sum(margin) as total
   FROM dbo.sale_view
   GROUP BY city
ORDER BY  1, 2
   ;

Additional context

Postgres supports it after version 9.
Redshift does not support it (because it was forked from Postgres version 8 before the function was introduced)
BigQuery does not support it
Snowflake (unknown)

Who will this benefit?
It will be useful for all analytics engineers who work with multi-dimensional reporting sparing them precious time otherwise spent copying  UNION ALL expressions with minuscule differences over and over again

Hey @yauhen-sobaleu, as discussed on the forum I'm very interested in this! I think it would be very similar to the width_bucket macro we already have, which has a native Snowflake version and for other warehouses we emulate it with other primitives from SQL.
I'll mark this as help wanted, it's a pretty beefy contribution but if you or someone else wants to have a go at building it, I'm happy to provide pointers.
I think the macro signature and implementation would look something like this. I haven't tested this at all, just wrote it on a plane so it will need some pretty serious finessing from here, as well as adding tests.
{% macro grouping_sets(group_sets, data_source, aggregate_expression) %}
    {{ adapter.dispatch('grouping_sets', 'dbt_utils')(group_sets, data_source, aggregate_expression) }}
{% endmacro %}

{% macro default__grouping_sets(group_sets, data_source, aggregate_expression) %}
    {% set all_list_elements = [] %}

    {% for item in group_sets %}
        {% do group_sets.append(item.values() %)
    {% endfor %}

    {% set unique_grouping_columns = set_strict(group_sets) %}

    select {{ unique_grouping_columns | join(", ") }}, {{ aggregate_expression }}
    from {{ data_source }}
    group by grouping sets (
        {% for grp in group_sets %}
            ( {{grp | join(", ") }} )
            {% if not loop.last %}
            ,
            {% endif %}
        {% endfor %}
    )
{% endmacro %}

{% macro redshift__grouping_sets(group_sets, data_source, aggregate_expression) %}
    {% set all_list_elements = [] %}

    {% for item in group_sets %}
        {% do group_sets.append(item.values() %)
    {% endfor %}

    {% set unique_grouping_columns = set_strict(group_sets) %}

    {% for group_set in group_sets %}

    select

        {% for column in unique_grouping_columns %}
            {% if column in group_set %}
                {{ column }}
            {% else %}
                --TODO: this won't work if it's the first usage of the column, would need to be cast as the right data type.
                --union_relations does this well but means these have to be Relations instead of just a CTE.
                --Alternative is to require a dictionary of data types to be passed in, but that's janky
                null as {{ column }}
            {% end %}
            ,
        {% endfor %}
        {{ aggregate_expression }}

        from {{ data_source }}
        group by {{ group_set.values() | join(", ") }}
        {% if not loop.last %}
            union all
        {% endif %}
    {% endfor %}
{% endmacro %}

Then it will be called as:
{{ grouping_sets([['county'], ['city'], ['county', 'city']]), 'sale_view', 'sum(margin) as total' }}

which will render to something that looks like one of these, depending on the warehouse:
select county, city, sum(margin) as total
from sale_view
group by grouping sets ((county), (city), (county, city))

select county, null, sum(margin) as total
from sale_view
group by county

union all

select null, city, sum('margin') as total
from sale_view
group by city

union all

select county, city, sum('margin') as total
from sale_view
group by county, city

Amazon Redshift released support for multi-dimensional aggregate functions!
https://aws.amazon.com/about-aws/whats-new/2022/11/amazon-redshift-sql-capabilities-speed-data-warehouse-migrations-preview/
It obviates the need to solve it inside DBT layer.


[DNM] test condition

closing as this seems to be one outdate patch, feel free to re-open if it's still valid


DOC: awesome-jupyterlab

Cool extension. You might consider adding this and the other jpmorganchase extensions to awesome-jupyter, awesome-jupyterlab?
https://github.com/mauhai/awesome-jupyterlab
https://github.com/adebar/awesome-jupyter
https://github.com/quobit/awesome-python-in-education#jupyter

PRs and press always welcome


fix: use fs/promises for settings

Description
This PR switches from synchronous operations with the 'fs' module to asynchronous operations with the 'fs/promises' module. It also corrects a small error with hostname migration.
Screenshot (if UI-related)
To-Dos

[x] Successful build pnpm build
[ ] Translation keys pnpm i18n:extract
[ ] Database migration (if required)

Issues Fixed or Closed

Fixes #XXXX

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

v2.1.0
GitHub release

Your semantic-release bot :package::rocket:


api reference issue on function arguments

for instance Workspace.observeTextEditors api, the code is observeTextEditors (callback), while the doc is observeTextEditors(callback, editor).
It's a common issue throughout all reference docs.
https://atom.io/docs/api/v1.16.0/Workspace#instance-observeTextEditors
https://github.com/atom/atom/blob/v1.16.0/src/workspace.js#L304

This is caused by https://github.com/atom/joanna/issues/4.

As explained in https://github.com/atom/joanna/issues/4, this has been fixed since Atom v1.21.0 🎉.


flaky test: //kythe/go/util/riegeli:riegeli_test

Looks like 1 test fails on bazel //... on macOS
Executing tests from //kythe/go/util/riegeli:riegeli_test
-----------------------------------------------------------------------------
2018/11/12 20:55:10 Compressed size of "TestReadWriteProto/zstd": 218225 bytes
2018/11/12 20:55:10 Compressed size of "TestReadWriteProto/uncompressed": 723013 bytes
2018/11/12 20:55:10 Compressed size of "TestReadWriteProto/brotli": 55538 bytes
2018/11/12 20:55:10 Compressed size of "TestReadWriteProto/default": 55537 bytes
2018/11/12 20:55:11 Compressed size of "TestReadWriteProto/brotli,transpose": 32529 bytes
2018/11/12 20:55:11 Compressed size of "TestReadWriteProto/uncompressed,transpose": 581299 bytes
2018/11/12 20:55:13 Compressed size of "TestReadWriteProto/transpose": 32522 bytes
--- FAIL: TestReadWriteProto (0.00s)
    --- FAIL: TestReadWriteProto/zstd (0.65s)
        riegeli_test.go:204: Read error: proto: can't skip unknown wire type 7
FAIL

Weird.  This does not fail in our CI instance: https://buildbot-dot-kythe-repo.appspot.com/#/builders/17/builds/183

It's flaky: bazel test --runs_per_test_detects_flakes --cache_test_results=no --runs_per_test=10 //kythe/go/util/riegeli:riegeli_test

Thank you for prompt feedback! Confirmed, indeed it passes now.

It's also only flaky when the tests are run in parallel.  This seems to work all the time: bazel test --runs_per_test_detects_flakes --cache_test_results=no --runs_per_test=500 --test_arg=-test.parallel=1 //kythe/go/util/riegeli:riegeli_test

It's also only flaky when the tests are run in parallel

I think that is probably WAI, given that Riegeli doesn't synchronize across multiple writers. We could probably deflake it by choosing a nonce file path per execution, I suppose.

The parallel tests are using separate Riegeli writers/readers on separate bytes.Buffers and the problem only affects the tests using zstd compression.


How to segment bodies within the cell

Is it possible to segment bodies within a cell? My data is a set of TEM images. I am looking to segment autophagic bodies inside the vacuole of the cell. When I tried it on my images, it highlighted the vacuole but left out the autophagic bodies within the vacuole. I attached a picture of the bodies and vacuole I'm hoping Cellpose can highlight.
If anybody has used Cellpose to segment organelles that would also be helpful here.
Thanks!

****

I am guessing this should in principle be quite similar to nuclear segmentation, although in that case usually the nucleus is stained in a different channel and segmented separate from the cytosol.  Are those dark lines drawn in or part of the original image?
Cellpose doesn't handle nested cells right now, but a workaround is that you could train one model to detect the vacuole, and then train another model to only detect the autophagic bodies - so two different ground truth masks per image.

The dark lines are drawn in. Ideally, we want our output image to have what is inside those dark outlines shaded in. This wouldn't work with the pretrained model? One of our obstacles is our small dataset, so I was hoping to use the pretrained model to solve that issue.

I used Cellpose on mitochondria measured by electron microscopy, which worked reasonably well, so round organelles should be segmentable in principle. However, the quality was not good enough for us with the pre-trained model, so I plan to re-train on our own data in the future.

very cool, @saskra , if you train and share the model we can link to it in the documentation. but yeah if it doesn't work well when you test it on https://www.cellpose.org/ then you likely need to train on new images
it may be a good idea to have these discussions on imagesc too https://forum.image.sc/tag/cellpose
I'm going to close this for now as this isn't necessarily a code issue


Encode user info when calling withUserInfo()

According to https://www.ietf.org/rfc/rfc3986.txt 3.2.1, the user info parts should actually be URL encoded.

I've created a new commit that adds a data provider with both user and credential values to test against, as well as the expected value of getUserInfo() following, and pushed that; it covers the suggested test by @jeremiahsmall as well.
The one issue I see with this is that it can lead to issues if you use the value retrieved from getUserInfo() to seed a new instance (e.g., $instance = $instance->withUserInfo($previous->getUserInfo()); you'll essentially get double-encoding (as evidenced by the test @jeremiahsmall suggested, where %25 becomes %2525).
Interestingly, @akrabat ran into this issue this week as well, when using an email address as the user information (e.g., user@example.com).
My suggestion is that any encoding is done when calling getAuthority() (which is used internally by createUriString() to return the authority value, which includes user-info, host, and port); this allows passing the raw values to withUserInfo(), and for getUserInfo() to return the same data it receives.
In reviewing the code, I also see that the parseUri() implementation is buggy, because it does not urldecode() the user and pass segments, which it likely should to prevent issues when consuming these values. (Interestingly, PHP's parse_url() function will accept unencoded values here and still parse the URL correctly!)
To be honest, parseUri() likely should not filter the path, query, and fragment, and instead delegate those operations to createUriString(). However, I think that's a topic for another PR.
@akrabat @DASPRiD and @jeremiahsmall : Do my suggestions here make sense?

The new data provider in the test looks good. Not sure what to make of the suggestion about encoding when calling getAuthority() without more time to reflect on that.

I'm going to move this to the 1.5.0 milestone, so we can also address the other issues related to parseUri(); I think consistency in how we handle these is best, and I'd rather the various getter methods return the raw values, and that casting to string filters/normalizes them for that context. This prevents double-encoding issues
The only "con" I can see is that doing so puts the onus on the user to encode if they wish to use those values as part of a URI string). I think we can message that in the docblocks, however.

So are we still saying that the arguments in withUserInfo() would be unencoded. If they would need to be encoded by the user, the variable names should reflect that. Eg:
public function withUserInfo($user, $password = null)
    {
   // snip

vs
public function withUserInfo($urlEncodedUser, $urlEncodedPassword = null)
    {
   // snip

If they're not encoded, why would we indicate they're encoded in the variable name?

Right, well I guess that answers my question... I was making sure that you're not suggesting that these be encoded.

I'm going to move this to the 1.5.0 milestone, so we can also address the other issues related to parseUri(); I think consistency in how we handle these is best, and I'd rather the various getter methods return the raw values, and that casting to string filters/normalizes them for that context. This prevents double-encoding issues

Okay, re-read the specification, and this is not possible. Each of the docblocks for getPath(), getQuery(), and getFragment() in the UriInterface indicate that they should return the percent encoded values, and prevent double-encoding. As such, the current approach suggested by @DASPRiD in this pull request is correct: percent-encode the value as it comes in, and any call to getUserInfo() and/or getAuthority() should return that encoded value. This will keep the workflow consistent with the other URI segments.
What this means, though, is that we need to ensure that the filterUserInfoPart() does not double-encode. We have tests in place for the other URI segments that use encoding, so I can use those as a basis for understanding how to both test and implement that functionality.

@jeremiahsmall I've isolated the double-encoding issue, and have now pushed a test that verifies that calling filterUserInfoPart() no longer double-encodes. With that change, and assuming that the changes pass continuous integration, I can merge this finally.

Thanks, @DASPRiD and @jeremiahsmall

+1


how to keep ripple effect color to view

hey awesome library i use it it works perfectlly but i wonder if it is possible to ripple effects end it stays same color not reset the color can you help me with this

I use Handler and setBackgroundColor() method to not reset the color. But I can't change the alpha of the ripple effect which doesn't look very good. I also want that feature


Missing options

Article suggests that warnings can be suppressed or work items created. There must be some pre-req for this to happen, because neither are in the right click menu for warnings in the Error List. Further, "the Actions link at the bottom of the warning" is not a thing I can locate anywhere - a warning is a single line entry in the Error list - where would the bottom be?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: f4074bba-2193-a551-616f-54fa34d27192
Version Independent ID: f01119e7-4ac0-0850-1842-452ef34e9a74
Content: Quickstart: Code Analysis for C/C++ - Visual Studio
Content Source: docs/code-quality/quick-start-code-analysis-for-c-cpp.md
Product: visual-studio-windows
Technology: vs-ide-code-analysis
GitHub Login: @mikeblome
Microsoft Alias: mblome

Further, this sentence is unclear: "To analyze a specific warning, choose the title of the warning in the Error List." - again - errors in the Error List are single line entries - there is no expansion visible.

Clarifying - this is VS 2019 and a C++ project using the v142 toolset

@stephenegriffin
Thanks for the report. After a bit of research, it appears warning suppression isn't an option in native C++, so I've removed that from the article. I've updated other parts to refer to the current UI behavior in the Error List window. Specifically, there's an expansion triangle in the first column of the Error List grid when more information is available. Choose it to see the extra info. There's no Action button, but the actions available are found in the right-click context menu that comes up for each warning.
The fixes should appear within a day of this issue being closed.


docs: Getting started with all messages on the client side

I know that users are frequently bitten by messages not being automatically available on the client side. We do this in the best interest of pushing performance as much as possible, but I think this has gone a bit too far. Especially when just starting out with an i18n setup, this can be frustrating.
Furthermore, I think for a number of apps this doesn't make a huge difference anyway. The number and length of messages in apps can vary significantly, so it's hard to make assumptions, but here are two examples from apps I'm maintaining:

An emerging one: 88 messages (1,5K gzip)
A more sophisticated one: 317 messages (7,6K gzip)

Apps can of course get much larger and it's important to be able to optimize, but it's questionable how early this is needed.
On top of this, app messages aren't the only place where translations are coming from, but typically they represent a part of the total translatable content (with other parts coming from a CMS, backend APIs, etc.).
We're planning on implementing tree-shaking of messages anyway in https://github.com/amannn/next-intl/issues/1, I think for the time being we could be a bit more relaxed about the suggestions we give to users.
→ New getting started docs for the App Router
As part of this, I'd now also consider automatically inheriting formats in Client Components if this is defined in i18n.ts for similar reasoning. This is a breaking change that will be part of https://github.com/amannn/next-intl/issues/779

@lmac-1 I'll merge this in the current form, as I believe this is already quite an improvement and so that I can stack proposed docs from https://github.com/amannn/next-intl/pull/1017 on top of this. Happy to follow-up though if you find some places that could use rephrasing or clarification!

I guess my only other comment would be perhaps the App Router example should be updated to match the new getting started steps?

That's a great point, yes! I've added a follow-up PR to address this here: https://github.com/amannn/next-intl/pull/1060
Thanks a ton for your feedback here! 🙏


Can not load tflite model converted from pytorch

System information

Win10:
TensorFlow version=1.15:

Code to generate tflite model
Generate the tflite model with cmd
python tflite_convert.py
--graph_def_file=./epoch10_model_toco.pb
--output_file=./lite.tflite
--inference_type=QUANTIZED_UINT8
--mean_values=0 --std_dev_values=1
--input_arrays=0 --output_arrays=Reshape_136 --input_shape=1,3,120,18,2
--default_ranges_min=0 --default_ranges_max=6 --post_training_quantize

Code to load tflite model
import tensorflow as tf

# Load TFLite model and allocate tensors.
interpreter = tf.lite.Interpreter(model_path="converted_model.tflite")
interpreter.allocate_tensors()

# Get input and output tensors.
input_details = interpreter.get_input_details()
print(input_details)
output_details = interpreter.get_output_details()
print(output_details)

# Test model on random input data.
input_shape = input_details[0]['shape']
input_data = np.array(np.random.random_sample(input_shape), dtype=np.float32)
interpreter.set_tensor(input_details[0]['index'], input_data)

interpreter.invoke()

# The function `get_tensor()` returns a copy of the tensor data.
# Use `tensor()` in order to get a pointer to the tensor.
output_data = interpreter.get_tensor(output_details[0]['index'])
print(output_data)

Error Message
Traceback (most recent call last):
  File "demo.py", line 97, in <module>
    main()
  File "demo.py", line 59, in main
    interpreter = tf.lite.Interpreter(model_path=PATH_TO_TFLITE)
  File "C:\Users\Administrator\.conda\envs\stgcn\lib\site-packages\tensorflow_core\lite\python\interpreter.py", line 206, in __init__
    model_path))
ValueError: Input array not provided for operation 'reshape'.

If i convert .pb to .tflite without uint8 quantized
python tflite_convert.py
--graph_def_file=./epoch10_model_toco.pb
--output_file=./lite.tflite
--input_arrays=0 --output_arrays=Reshape_136 --input_shape=1,3,120,18,2

Then load the tflite without quantized as the same.
Still i got another error message.
Traceback (most recent call last):
  File "demo.py", line 97, in <module>
    main()
  File "demo.py", line 60, in main
    interpreter.allocate_tensors()
  File "C:\Users\Administrator\.conda\envs\stgcn\lib\site-packages\tensorflow_core\lite\python\interpreter.py", line 244, in allocate_tensors
    return self._interpreter.AllocateTensors()
  File "C:\Users\Administrator\.conda\envs\stgcn\lib\site-packages\tensorflow_core\lite\python\interpreter_wrapper\tensorflow_wrap_interpreter_wrapper.py", line 106, in AllocateTensors
    return _tensorflow_wrap_interpreter_wrapper.InterpreterWrapper_AllocateTensors(self)
RuntimeError: tensorflow/lite/kernels/transpose.cc Transpose op only supports 1D-4D input arrays.Node number 0 (TRANSPOSE) failed to prepare.

How can i convert the .pb to the .tflite, which could be loaded.
Is there something wrong in the .tflite layer?How to correct that?

Hi @ambarion, could you please try setting --experimental_new_converter=True to the tflite_convert command line?

Hi @ambarion, could you please try setting --experimental_new_converter=True to the tflite_convert command line?

Thanks for your reply, but i still got the same error.

Having same issue::
First converted pytorch model to onnx(model.onnx). And then converted onnx model to pb(model.pb). Then changed shape to NWHC(model_toco.pb) using https://github.com/paulbauriegel/tensorflow-tools/blob/master/convert-model-to-NWHC.py . Then used below code to convert to tflite.
converter = tf.lite.TFLiteConverter.from_frozen_graph('model_toco.pb',                                                           input_arrays=['input0'],                                                           output_arrays=['output0']      )
converter.optimizations = [tf.lite.Optimize.DEFAULT]
tf_lite_model = converter.convert()
open('model_toco.tflite', 'wb').write(tf_lite_model)
When loading this tflite model on PC... gives the same error.
tf version:: 1.15(pip install)
Any solutions or way around??

@ambarion @sanrahul, by quantizing YOLO v3 for TF Lite, I also encounter ValueError: Input array not provided for operation 'reshape'.
I made a script to fix the reshape problems, plz refer to Quantization section in onnx_tflite_yolov3

Mine has problems of converting pytorch F.interpolate  and torch.view(). How did you converted F.interpolate (which is a part of yolo3 model) to TFlite?

@Mara

@ambarion @sanrahul, by quantizing YOLO v3 for TF Lite, I also encounter ValueError: Input array not provided for operation 'reshape'.
I made a script to fix the reshape problems, plz refer to Quantization section in onnx_tflite_yolov3

Mine has problems of converting pytorch F.interpolate  and torch.view(). How did you converted F.interpolate (which is a part of yolo3 model) to TFlite?

TFLite does not  support 5-dimensional reshape, so you have to change the output of  torch.view() to 1-4D
I haven't seen any problems with F.interpolate, what the error message?

@zldrobit
Most interesting part of output
2020-05-13 11:02:11.573396: I tensorflow/lite/toco/import_tensorflow.cc:659] Converting unsupported operation: If
2020-05-13 11:02:11.573439: F tensorflow/lite/toco/import_tensorflow.cc:114] Check failed: attr.value_case() == AttrValue::kType (1 vs. 6)

All output
Traceback (most recent call last):
  File "/home/marat/OCR/yolo3/torch2tflite.py", line 127, in <module>
    tflite_model = converter.convert()
  File "/home/marat/anaconda3/envs/cexp/lib/python3.7/site-packages/tensorflow_core/lite/python/lite.py", line 1007, in convert
    **converter_kwargs)
  File "/home/marat/anaconda3/envs/cexp/lib/python3.7/site-packages/tensorflow_core/lite/python/convert.py", line 457, in toco_convert_impl
    enable_mlir_converter=enable_mlir_converter)
  File "/home/marat/anaconda3/envs/cexp/lib/python3.7/site-packages/tensorflow_core/lite/python/convert.py", line 203, in toco_convert_protos
    raise ConverterError("See console for info.\n%s\n%s\n" % (stdout, stderr))
tensorflow.lite.python.convert.ConverterError: See console for info.
2020-05-13 11:02:11.123019: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libnvinfer.so.6'; dlerror: libnvinfer.so.6: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/local/cuda/lib64:/home/marat/anaconda3/lib
2020-05-13 11:02:11.123080: W tensorflow/stream_executor/platform/default/dso_loader.cc:55] Could not load dynamic library 'libnvinfer_plugin.so.6'; dlerror: libnvinfer_plugin.so.6: cannot open shared object file: No such file or directory; LD_LIBRARY_PATH: /usr/local/cuda/lib64:/home/marat/anaconda3/lib
2020-05-13 11:02:11.123089: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:30] Cannot dlopen some TensorRT libraries. If you would like to use Nvidia GPU with TensorRT, please make sure the missing libraries mentioned above are installed properly.
2020-05-13 11:02:11.557879: I tensorflow/core/platform/cpu_feature_guard.cc:142] Your CPU supports instructions that this TensorFlow binary was not compiled to use: AVX2 FMA
2020-05-13 11:02:11.563803: I tensorflow/core/platform/profile_utils/cpu_utils.cc:94] CPU Frequency:<PHONE_NUMBER> Hz
2020-05-13 11:02:11.564214: I tensorflow/compiler/xla/service/service.cc:168] XLA service 0x56377f6b4ce0 initialized for platform Host (this does not guarantee that XLA will be used). Devices:
2020-05-13 11:02:11.564240: I tensorflow/compiler/xla/service/service.cc:176]   StreamExecutor device (0): Host, Default Version
2020-05-13 11:02:11.565808: I tensorflow/stream_executor/platform/default/dso_loader.cc:44] Successfully opened dynamic library libcuda.so.1
2020-05-13 11:02:11.568053: E tensorflow/stream_executor/cuda/cuda_driver.cc:351] failed call to cuInit: CUDA_ERROR_NO_DEVICE: no CUDA-capable device is detected
2020-05-13 11:02:11.568071: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:169] retrieving CUDA diagnostic information for host: saturn
2020-05-13 11:02:11.568076: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:176] hostname: saturn
2020-05-13 11:02:11.568107: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:200] libcuda reported version is: 440.64.0
2020-05-13 11:02:11.568126: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:204] kernel reported version is: 440.64.0
2020-05-13 11:02:11.568131: I tensorflow/stream_executor/cuda/cuda_diagnostics.cc:310] kernel version seems to match DSO: 440.64.0
2020-05-13 11:02:11.573396: I tensorflow/lite/toco/import_tensorflow.cc:659] Converting unsupported operation: If
2020-05-13 11:02:11.573439: F tensorflow/lite/toco/import_tensorflow.cc:114] Check failed: attr.value_case() == AttrValue::kType (1 vs. 6)
Fatal Python error: Aborted

Current thread 0x00007fa391a0b700 (most recent call first):
  File "/home/marat/anaconda3/envs/cexp/lib/python3.7/site-packages/tensorflow_core/lite/toco/python/toco_from_protos.py", line 56 in execute
  File "/home/marat/anaconda3/envs/cexp/lib/python3.7/site-packages/absl/app.py", line 250 in _run_main
  File "/home/marat/anaconda3/envs/cexp/lib/python3.7/site-packages/absl/app.py", line 299 in run
  File "/home/marat/anaconda3/envs/cexp/lib/python3.7/site-packages/tensorflow_core/python/platform/app.py", line 40 in run
  File "/home/marat/anaconda3/envs/cexp/lib/python3.7/site-packages/tensorflow_core/lite/toco/python/toco_from_protos.py", line 93 in main
  File "/home/marat/anaconda3/envs/cexp/bin/toco_from_protos", line 8 in <module>
Aborted (core dumped)

2020-05-13 11:02:11.573396: I tensorflow/lite/toco/import_tensorflow.cc:659] Converting unsupported operation: If
2020-05-13 11:02:11.573439: F tensorflow/lite/toco/import_tensorflow.cc:114] Check failed: attr.value_case() == AttrValue::kType (1 vs. 6)

It cannot be confirmed from above that F.interpolate  or torch.view() is causing the error.
You may have to check your computation graph with netron to locate the problematic op which is near If.
Even to debug Tensorflow/TFLite by yourself (including compilation of debug version code).

@ambarion Hello, have you salved the problem?

Hi There,
We are checking to see if you still need help on this, as you are using an older version of tensorflow which is officially considered end of life . We recommend that you upgrade to the latest 2.x version and let us know if the issue still persists in newer versions. Please open a new issue for any help you need against 2.x, and we will get you the right help.
This issue will be closed automatically 7 days from now. If you still need help with this issue, please provide us with more information.


Heroku client internal error. connect timeout reached

Hi,
I just installed heroku toolbelt and on very first run it failed saying that connect timeout reached.

Please suggest any solution.
Thanks.

@dickeyxxx please help with this issue. Let me know what URLs I need to add into my firewall if required.

You need to whitelist *.heroku.com
On Tue, Jun 28, 2016 at 3:31 AM Shubham Goyal<EMAIL_ADDRESS>wrote:

@dickeyxxx https://github.com/dickeyxxx please help with this issue.
Let me know what URLs I need to add into my firewall if required.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/heroku/heroku/issues/1973#issuecomment-229012392, or mute
the thread
https://github.com/notifications/unsubscribe/AANMfOPb8YybZ22oRs0I-ERn2dqrdjhoks5qQPf3gaJpZM4I_1lv
.

Thanks @dickeyxxx for your help. Above issue is resolved at my end. Now while creating new app on heroku, I am getting "SELF_SIGNED_CERT_IN_CHAIN: self signed certificate in certificate chain".
I am not able to understand how to go about it. Can you please help with this?
Thanks again.

this means you have a MITM proxy. I'm not sure how to make it work, you'll probably have to set SSL_CERT_FILE to a certificate for your internet.


Add a test to see if IODA files can be read properly

Add a CI test to ensure that a sample IODA netCDF AMSU-A file can be read and values printed out as expected. This PR also adds some other in progress files such as __init__ and the beginning of the main driver executable plotioda script.

Pardon my googol of commits attempting to figure out the caching issue which has been resolved.


Limitless led color temperature for bridge 6 not working if set in scenes / scripts

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.43.0
Python release (python3 --version):
Python 3.4.2
Component/platform:
limitlessled
Description of problem:
set color temperature works only from webgui slider and not if it is set in scenes (or scripts)
Expected:
set color_temp should be setable from scripts/scenes as well
Problem-relevant configuration.yaml entries and steps to reproduce:
scene:
  - name: living room ambient
    entities:
      light.living_room_table_light:
        state: on
        brightness: 255
        rgb_color: [255, 255, 255]
        color_temp: 400

script:
  - evening_script:
       sequence:
          entity_id: light.dorm_lights
          data:
             brightness: 255
             color_temp: 255
             rgb_color: [255, 255, 255]

Aditional info:
Hass ist set in virtual_env

I have not tested cripts out, however when the new slider background was introduced in the gui in noticed that all my milights (RGBWW) have the colortemperature backwards.

@Andrei-Radulescu have you tried to leave out rgb_color ?

@amelchio Just did and it works, thanks for the workaround. Still, I believe that something changed since 0.42 as rgb_color: [255, 255, 255] was resolving correctly to white in the limitlessled component.
@tbrasser - I didn't even notice :)  The slider logic hasn't change though. Before 0.43 moving the slider left was for warm light and right for cold as it still is the case. I think that just the image is backwards :) -> maybe an easy fix

@Andrei-Radulescu from the code, it then appears to work like intended. I don't know whether it changed recently but it does make sense to leave it out because you never pick a temperature for anything but white.
So I don't think there is anything to fix here :)

@amelchio Ok, should we open another issue for the sliderbackground?

Yeah, please do that.


in Get Reports, reportDate is not a range?

Hello,
So i am getting reports but i wanted to ask if date range is accepted instead of one day? if i want last 60 days i have to loop through, api doesn't let ranges defined or am i missing something?

The API is documented here: https://advertising.amazon.com/API/docs/en-us/sponsored-products/2-0/openapi#/Reports
It has no native ability to specify range.


implement sidebar

add layout context to control sidebar from pages
add icons
add button list
add accordion and tree to sidebar
add hide sidebar button

colors are coming from the ui library, and light vs dark mode apparently are not matching, as you see in react components was the same color but it is changed in react ui
react components color:

the border has been added after these screenshots
open or close only works when there is a sub-menu for each toolbar item so it is not meant to be opened in this PR since @isaozler mentioned there is no need to have the third level menu in transfer tools, but if one page is needed it's better to have it already in place so we can easily show it without breaking change on layout