Export diff, patch functions

Heya, this is a cool, tiny library - thanks for making it. I've used it to replace our usage of MorphDOM in our editor's live preview system. One thing I wish I had access to was the diff and patch functions - currently you can only use the convenience function for doing both at the same time.
The reason why I would want to do this is so that I could spread out the diffing and patching process over time so I can prevent stuttering in the editor. It would also be neat to have some manual control over the patching.

I can definitely expose them both! Wasn’t sure if there was a good case for using them individually, but that makes a lot of sense.
As for more control over patching, I’m currently experimenting with different ways to expose hooks into the diff and/or patch process. Would you mind opening another issue with more details of your use cases?

I actually meant "Another reason this feature would be nice would be because it would give you some more manual control", I used bad wording. I don't actually think I have any particular desire yet for hooks in the patch or diff functions yet. I'll definitely make a separate issue and describe in detail what we're doing if a need for hooks crops up.


The  renders as  tags

When rendering on the server, both on the client and the server, wherever the <Helmet> tag is the JSX component, the rendered output for it is .
React renders  for components that return null when rendering... so what could cause the Helmet to render null?
I'm using<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

Helmet renders null because the rendering is inconsequential toward the main purpose of Helmet.  You know Helmet worked because of how it changed your .  I suppose we would accept a PR to have Helmet render empty string.  What do other folks think?

From v15 React will render comment nodes instead of  when returning null. See https://facebook.github.io/react/blog/2016/03/07/react-v15-rc1.html#rendering-null-now-uses-comment-nodes.

@cwelch The problem is that none of the components nested within <Helmet> and </Helmet> get rendered either. Just  and that is all. If I do not nest components within it, then it is fine - but the document title and other things do not appear properly.
Is there an example app using react-router@2 and<EMAIL_ADDRESS>working with Helmet that I an use  as a reference?

@bausmeier Thanks for the input, I'm not on react@15 yet though!

@bguiz Helmet will not render children (as designed).  Title and other head attributes are all working correctly.  Please refer to the unit tests.  We have successfully tested Helmet with<EMAIL_ADDRESS>


Telegram force_reply

Hello,
in a conversation I'd like to use in one step the force_reply option, it should be set as parameter inside the reply_markup, so into the ask function I should use it like this:
$this->ask("Message...", function (Answer $answer) {
   // Code here...
}, ['reply_markup' => ['force_reply' => true]]);

but isn't correct, even if the same thing works with  ['parse_mode' => 'Markdown']
How should be used the force_reply?
Thank you.

This will work:
$this->ask("Message...", function (Answer $answer) {
   // Code here...
}, ['reply_markup' => json_encode(['force_reply' => true])]);


Nextjs warning

next-dev.js?3515:20 Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of DraggableCore which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://reactjs.org/link/strict-mode-find-node

Samesies

That's because NextJS uses 'StrictMode'. You need to use the nodeRef prop.
import { useRef } from 'react';
import ReactDraggable from 'react-draggable';

export default function Draggable({ children }) {
  const nodeRef = useRef(null);

  return (
    <ReactDraggable nodeRef={nodeRef}>

{children}

    </ReactDraggable>
  );
}

As per readme:
// If running in React Strict mode, ReactDOM.findDOMNode() is deprecated.
// Unfortunately, in order for <Draggable> to work properly, we need raw access
// to the underlying DOM node. If you want to avoid the warning, pass a `nodeRef`


Branding is not working with ActiveUI 5

Steps to reproduce
import atoti as tt
import pandas as pd

session = tt.create_session(
    name='Main session',
    config=tt.config.create_config(
        branding=tt.config.create_branding(
            accent_color='rgb(0,128,0)',
            favicon='./grwa_logo.ico',
            frame_color='rgb(0,128,0)',
            title='Test - #####'
        )
    )
)

data = [
    ['Trade 1', 20]
]
df = pd.DataFrame(data, columns=['Trade ID', 'Delta'])

store = session.read_pandas(df, keys=['Trade ID'], store_name='Store')
cube = session.create_cube(store)

session.url

Actual Result
Only the favicon is modified according to the branding configuration.
Expected Result
I should also see the new title and the new accent and frame colors.
Environment

atoti: 0.5.4
Operating System: win32
Browser: GoogleChrome

Thanks for the clear issue Harold. On my side the colors are indeed not being picked up but the favicon and titles are working.

In fact the favicon is working well.
Maybe I don't look at the right place to find the title, could you indicate me where it is displayed?


Netlify build fails with PrismaClientInitializationError

I've got a Next.js app that uses prisma.
My schema.prisma:
generator client {
    provider        = "prisma-client-js"
    previewFeatures = ["referentialIntegrity"]
    binaryTargets   = ["native", "debian-openssl-1.1.x"]
}

datasource db {
    provider             = "mysql"
    url                  = env("DATABASE_URL")
    referentialIntegrity = "prisma"
}

I'm doing development on Windows 11. Everything works great locally.
When I commit to Github, it kicks off a build in Netlify. I get the following error:
10:33:22 AM: /opt/build/repo/node_modules/@prisma/client/runtime/index.js:45007
10:33:22 AM:       throw new PrismaClientInitializationError(errorText, this.config.clientVersion);
10:33:22 AM:             ^
10:33:22 AM: PrismaClientInitializationError: Query engine library for current platform "debian-openssl-1.1.x" could not be found.
10:33:22 AM: You incorrectly pinned it to debian-openssl-1.1.x
10:33:22 AM: This probably happens, because you built Prisma Client on a different platform.
10:33:22 AM: (Prisma Client looked in<EMAIL_ADDRESS>10:33:22 AM: Searched Locations:
10:33:22 AM:   /opt/build/repo/node_modules/.prisma/client
10:33:22 AM:   /opt/build/repo/node_modules/@prisma/client
10:33:22 AM:   /opt/build/repo/node_modules/@prisma/client
10:33:22 AM:   /opt/build/repo/node_modules/.prisma/client
10:33:22 AM:   /opt/build/repo/prisma
10:33:22 AM:   /tmp/prisma-engines
10:33:22 AM:   /opt/build/repo/node_modules/.prisma/client
10:33:22 AM: You already added the platforms "debian-openssl-1.1.x", "debian-openssl-1.1.x" to the "generator" block
10:33:22 AM: in the "schema.prisma" file as described in https://pris.ly/d/client-generator,
10:33:22 AM: but something went wrong. That's suboptimal.
10:33:22 AM: Please create an issue at https://github.com/prisma/prisma/issues/new
10:33:22 AM:     at LibraryEngine.getLibQueryEnginePath (/opt/build/repo/node_modules/@prisma/client/runtime/index.js:45007:13)
10:33:22 AM:     at async LibraryEngine.loadEngine (/opt/build/repo/node_modules/@prisma/client/runtime/index.js:44666:33)
10:33:22 AM:     at async LibraryEngine.instantiateLibrary (/opt/build/repo/node_modules/@prisma/client/runtime/index.js:44632:5) {
10:33:22 AM:   clientVersion: '3.15.2',
10:33:22 AM:   errorCode: undefined
10:33:22 AM: }
10:33:22 AM: info  - Generating static pages (0/5)
10:33:22 AM: /opt/build/repo/node_modules/@prisma/client/runtime/index.js:45007
10:33:23 AM: Failed during stage 'building site': Build script returned non-zero exit code: 2 (https://ntl.fyi/exit-code-2)
10:33:22 AM:       throw new PrismaClientInitializationError(errorText, this.config.clientVersion);
10:33:22 AM:             ^
10:33:22 AM: PrismaClientInitializationError: Query engine library for current platform "debian-openssl-1.1.x" could not be found.
10:33:22 AM: You incorrectly pinned it to debian-openssl-1.1.x
10:33:22 AM: This probably happens, because you built Prisma Client on a different platform.
10:33:22 AM: (Prisma Client looked in<EMAIL_ADDRESS>10:33:22 AM: Searched Locations:
10:33:22 AM:   /opt/build/repo/node_modules/.prisma/client
10:33:22 AM:   /opt/build/repo/node_modules/@prisma/client
10:33:22 AM:   /opt/build/repo/node_modules/@prisma/client
10:33:22 AM:   /opt/build/repo/node_modules/.prisma/client
10:33:22 AM:   /opt/build/repo/prisma
10:33:22 AM:   /tmp/prisma-engines
10:33:22 AM:   /opt/build/repo/node_modules/.prisma/client
10:33:22 AM: You already added the platforms "debian-openssl-1.1.x", "debian-openssl-1.1.x" to the "generator" block
10:33:22 AM: in the "schema.prisma" file as described in https://pris.ly/d/client-generator,
10:33:22 AM: but something went wrong. That's suboptimal.
10:33:22 AM: Please create an issue at https://github.com/prisma/prisma/issues/new
10:33:22 AM:     at LibraryEngine.getLibQueryEnginePath (/opt/build/repo/node_modules/@prisma/client/runtime/index.js:45007:13)
10:33:22 AM:     at async LibraryEngine.loadEngine (/opt/build/repo/node_modules/@prisma/client/runtime/index.js:44666:33)
10:33:22 AM:     at async LibraryEngine.instantiateLibrary (/opt/build/repo/node_modules/@prisma/client/runtime/index.js:44632:5) {
10:33:22 AM:   clientVersion: '3.15.2',
10:33:22 AM:   errorCode: undefined
10:33:22 AM: }

My current workaround is to force Netlify to clear cache and deploy site and then everything magically works.

Hey there,
Is it possible to try with the latest version of Prisma? I notice in your trace that you are using 3.15.2.
Also, could you give us a bit more detailed reproduction steps if you can. That would help us diagnose the root cause quicker. Thanks.

Hello, I'm having the same exact issue with the following setup:

Custom docker image with (debian) node:lts as base (18)
Prisma 4.8.1

I'm using a custom output for PrismaClient (setup according to your own documentation) but I don't think it's related to this error. The file "libquery_engine-debian-openssl-1.1.x.so.node" exists in the folder the error log displays.

Can you please create a separate issue @evk-dev and provide all the info the issue template asks for? The original here is Netlify specific and definitely has some differences in the error messages from what you are experiencing.

We will now display a hard error to prevent these pitfalls with caching in Vercel and Netlify. We will basically verify that you ran prisma generate on these platforms, because otherwise you would run into hard to debug caching issues.


$ref

[ ] show it
[ ] follow the link

Hi @yanick! Are you still maintaining this project? I loved it and the only missing feature I noticed is $ref :)

I do, I do! Very slowly, but I do. I'll try to add $red goodness this week. I'll poke you once I have something peeps can test. :-)


opam wrapper causes 'opam env' to pollute user environment

The opam package uses a wrapper script to add aspcud, unzip, curl, getconf, and (on linux only) bubblewrap to $PATH since these tools are invoked from opam. This interacts poorly with 'opam env' which is used to update the shell environment for the selected opam switch. 'opam env' prints environment modification commands that incorporate the extended PATH from the wrapper. Commonly opam sets up a shell prompt hook to run 'opam env' every prompt which causes these paths to be added every prompt resulting in some comically long PATH variables.
I'm not sure of the best way to fix this issue. Some possibilities:

Dispense with the wrapper. To use opam the user will just have to ensure the requisite tools are available. This will potentially create other problems (see #16938 that added the wrapper to ensure the aspcud solver was available and subsequently #39619 to fix #14466). However, opam still needs other tools on the path for full functionality (e.g. tar, patch, vcs, a build environment).
Patch opam so that tools are invoked with absolute paths into the store. It'd be nice to find a way to do this that is upstreamable.
Add these dependent packages to propagatedBuildInputs instead of extending path in the wrapper.

To Reproduce
Steps to reproduce the behavior:

Install the opam package
Run 'opam init' and allow it to set up a shell hook
Open a new shell and notice that aspcud, unzip, curl, getconf, and (on linux only) bubblewrap are now in $PATH
Observe every time the prompt is shown these store paths are duplicated in $PATH

Expected behavior
These store paths should not be added to the user's $PATH variable.
Metadata

system: "x86_64-darwin"
host os: Darwin 16.7.0, macOS 10.12.6
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.3.1
channels(gereedy): "nixpkgs-20.03pre202090.93e8c34e2e4"
channels(root): "nixpkgs-20.03pre202090.93e8c34e2e4"
nixpkgs: /Users/gereedy/.nix-defexpr/channels/nixpkgs

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute: opam
# a list of nixos modules affected by the problem
module:

Note that, as of version 2.0.0, opam comes with a built-in solver that is enabled by default, so at least aspcud could be removed (see https://opam.ocaml.org/doc/External_solvers.html).

This bug is still present, and can cause other commands to fail because $PATH exceeds the maximum length for an environment variable; see https://github.com/ocaml/opam/issues/4553 .


Added bleach.dev

This PR is:

[x] Adding a new domain
[ ] Updating existing domain size
[ ] Changing domain name
[ ] Removing existing domain from list
[ ] Website code changes (512kb.club site)
[ ] Other not listed

[x] I used the uncompressed size of the site
[x] I have included a link to the GTMetrix report
[x] The domain is in the correct alphabetical order
[x] This site is not an ultra lightweight site
[x] The following information is filled identical to the data file

I confirm that I have read the FAQ section, particularly the two red items around minimal pages and inappropriate content and I attest that this site is neither of these things.

[x] Check to confirm

- domain: bleach.dev
  url: https://bleach.dev/
  size: 179
  last_checked: 2023-09-02

GTMetrix Report:
https://gtmetrix.com/reports/bleach.dev/TV6spJvI/

Thanks!


.deb releases for v0.13?

Sorry to be so demanding, but it sounded like you were close to sort of automating all this, and i'd like to continue using Debian package releases to test.
Thanks!

Oh, thats really really my BAD
I had forgotten to press the "release" button !
Seriously sorry folks !
Done now.


[IOTDB-3883] Support order by timeseries in last query & support last query across different DataRegion in execution layer

The design details can been seen in this doc

Coverage decreased (-0.03%) to 43.543% when pulling 629f1e3e7e65b6afde7de11b27f5d7dd3329c8f3 on IOTDB-3883 into bd1894fb72e85b152dd412afca8a7e6b97ad769e on master.


Improve Harvester Node Driver Credentials

SURE-8516

[ ] #11269
[ ] #11270
[ ] #11271

Will need backport to 2.9.x

I've updated the issue to an epic and created issues per short/mid term goals

Only remaining issue is https://github.com/rancher/dashboard/issues/11271, which is blocked on backend changes


Cache report

This PR introduces a feature for reporting cache hits/misses at specified intervals.
A new option logInterval is introduced in the cache options.
Closes #24

Check the recommendations I just made

Could you make the logReport fuunction configurable? I highly suspect somebody could send this to prometheus instead.

Sure. I too thought of doing that

I also think the report should be cleared after each log.

Do you mean clear the count every time the logReport function is called? This would only show hit/miss count for the duration of the logInterval

Working on fixing the CI

can we also add the skip counter to the report?


blank white page after updating docker

was using the unraid template at https://github.com/lordchewie/liquid-dl-unraid
today it said there was an update so i updated and now i just get a white page with this in my logs.
[14/Sep/2017 21:12:28] "GET / HTTP/1.1" 200 896
[14/Sep/2017 21:12:28] "GET /static/bundles/main-6ed82cd24729439f6a7a.js HTTP/1.1" 404 1723
[14/Sep/2017 21:12:29] "GET /static/bundles/main-6ed82cd24729439f6a7a.js HTTP/1.1" 404 1723
[14/Sep/2017 21:12:34] "GET / HTTP/1.1" 200 896
[14/Sep/2017 21:12:35] "GET /static/js/utility/jquery.js HTTP/1.1" 304 0
[14/Sep/2017 21:12:35] "GET /static/bundles/main-6ed82cd24729439f6a7a.js HTTP/1.1" 404 1723
[14/Sep/2017 21:12:35] "GET /static/js/utility/materialize.js HTTP/1.1" 304 0
[14/Sep/2017 21:12:35] "GET /static/bundles/main-6ed82cd24729439f6a7a.js HTTP/1.1" 404 1723
[14/Sep/2017 21:12:49] "GET / HTTP/1.1" 200 896
[14/Sep/2017 21:12:49] "GET /static/bundles/main-6ed82cd24729439f6a7a.js HTTP/1.1" 404 1723
[14/Sep/2017 21:12:50] "GET /static/bundles/main-6ed82cd24729439f6a7a.js HTTP/1.1" 404 1723
[14/Sep/2017 21:17:34] "GET / HTTP/1.1" 200 896
[14/Sep/2017 21:17:34] "GET /static/bundles/main-6ed82cd24729439f6a7a.js HTTP/1.1" 404 1723
[14/Sep/2017 21:17:34] "GET /static/bundles/main-6ed82cd24729439f6a7a.js HTTP/1.1" 404 1723
[14/Sep/2017 21:18:28] "GET / HTTP/1.1" 200 896
[14/Sep/2017 21:18:28] "GET /static/js/utility/jquery.js HTTP/1.1" 304 0
[14/Sep/2017 21:18:28] "GET /static/js/utility/materialize.js HTTP/1.1" 304 0
[14/Sep/2017 21:18:28] "GET /static/bundles/main-6ed82cd24729439f6a7a.js HTTP/1.1" 404 1723
[14/Sep/2017 21:18:29] "GET /static/bundles/main-6ed82cd24729439f6a7a.js HTTP/1.1" 404 1723

my console also has this
Loading failed for the <script> with source “http://[ip]:[port]/static/bundles/main-6ed82cd24729439f6a7a.js”.

You need to CD into the  folder and build a web pack bundle using the command in the readMe. For building a bundle, then refresh and viola!

by into the folder ... do you mean into the docker container? Or a different folder?
If you mean into the container i seem to be able to get into it with  docker exec -it Liquid-dl sh and i do see what looks to be the right folders but when i run ./node_modules/.bin/webpack --config webpack.config.js -p (this is the right command, correct?) I get permission denied so clearly i doing something wrong.
Sorry if i am being dense or stupid, i am new to all this and still getting my bearing and learning.

You'' need to cd into the liquid_dl folder then if your on Linux you'll need to execute
sudo ./node_modules/.bin/webpack --config webpack.config.js -p  this should get rid of any permission  issues.
Alternatively go into liquid_dl/templates/ folder and edit the home.html inside it change
    <!--<script src="{% static 'distro/newest_prod_build.js' %}"></script> -->
    <!-- Our Development Build -->
    {% render_bundle 'main' %}

to
<!-- Our production build-->
   <script src="{% static 'distro/newest_prod_build.js' %}"></script>
    <!-- Our Development Build -->
   <!-- {% render_bundle 'main' %} -->

Also I must ask is this error occurring from the master branch or from the latest release?

Cant seem to sudo inside docker containers. So first option doesn't work.
However, pulling out the home.html file from the container and editing what you said and then pushing it back into the container seems to have work.
I am on whatever dockerhub is supplying which seems to the the latest release. Unraid shows  kthulu120/liquid_dl:latest and dockerhub has tags only for latest. So i would assume that means latest release.
Anyways, since editing the home.html page worked I will go ahead and close this.

Note for future reference for anyone looking at this, dockerhub build off of the latest master branch updates therefore you'll have to do this if downloading from dockerhub or you could download the zip of the latest release.


Smart Wizard Step

Hii please help me to submit form after step button Finish.

Duplicate of #573
There the instructions, please close this.

okay sir,,  i am sorry
thank u..
On Fri, Oct 20, 2017 at 12:22 AM, William<EMAIL_ADDRESS>wrote:

Duplicate of #573 https://github.com/puikinsh/gentelella/issues/573
There the instructions, please close this.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/puikinsh/gentelella/issues/592#issuecomment-337977771,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AfaV7plxyOgYzgM2iifMB61NUxOUKiEaks5st4VpgaJpZM4P_kb1
.


Improve documentation around EDUs and PDUs

Rendered: see 'docs' commit status

Clarify fields, improve examples, and make the tables in the spec be generated rather than duplicated.

Is it possible to somehow reuse the event swagger definitions for unsigned PDUs? Maybe by having signed events extend unsigned PDUs? It seems a shame to duplicate the definitions of the fields

Which duplication in particular? It should be possible to have things extend the unsigned PDU, although I don't see where this PR can benefit from doing that.

Which duplication in particular? It should be possible to have things extend the unsigned PDU, although I don't see where this PR can benefit from doing that.

I guess I'm assuming that we already have a signed PDU schema somewhere already?

The only signed PDU schema I could find was a table in the RST, which doesn't really help anyone.
(also have removed the unused EDU fields)

Ah, pdu.yaml already inherits from unsigned_pdy.yaml


Can't get latest version with rendererSettings prop

Hey, I'm trying to use the latest version of this, 3.0.1 so that I can use the new rendererSettings prop. Unfortunately I get the error No matching version found for<EMAIL_ADDRESS>- any idea why this would be?

Pushed up to npm. Do have a check and get back to us ^^
Thank you

All good now, thanks again!

you re welcome! closing this issue & happy coding :)


Upgrade to PyTorch 1.10

Advantages:

Faster CA simulation
Disadvantages:
Changes the way objects/tensors are sent to devices

PyTorch 1.10.0 also plays differently with gradients.
Errors when running testing.test_all with 1.10 (no errors with 1.5)
======================================================================
ERROR: test_multiverse_forward (testing.yuca.test_multiverse.TestCA)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/rlygr/Desktop/projects/yuca_readme/testing/yuca/test_multiverse.py", line 23, in test_multiverse_forward
    ca.to_device("cpu")
  File "/home/rlygr/Desktop/projects/yuca_readme/yuca/multiverse.py", line 873, in to_device
    param[:] = param.to(my_device)
RuntimeError: a view of a leaf Variable that requires grad is being used in an in-place operation.

======================================================================
ERROR: test_multiverse_to (testing.yuca.test_multiverse.TestCA)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/rlygr/Desktop/projects/yuca_readme/testing/yuca/test_multiverse.py", line 117, in test_multiverse_to
    ca.to_device(my_device)
  File "/home/rlygr/Desktop/projects/yuca_readme/yuca/multiverse.py", line 873, in to_device
    param[:] = param.to(my_device)
RuntimeError: a view of a leaf Variable that requires grad is being used in an in-place operation.

----------------------------------------------------------------------
Ran 8 tests in 1.570s

Should probably be torch==1.11 now.

PyTorch version now updated to 2.0.1 in PR #58


Added tests 300-394

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

Comparison is base (fbe44b5) 94.01% compared to head (c4b4d17) 91.17%.
Report is 3 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #74      +/-   ##
==========================================
- Coverage   94.01%   91.17%   -2.85%
==========================================
  Files          84       96      +12
  Lines        1170     1382     +212
  Branches      229      267      +38
==========================================
+ Hits         1100     1260     +160
- Misses         25       71      +46
- Partials       45       51       +6

see 12 files with indirect coverage changes

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

👍


October 2023 plandomizer updates

An "Introduction" page has been added. This will offer some basic information and resources for making plando seeds.
Validation check: a single shop can't have an item for All Kongs and also for an individual Kong.
Enemy drops are sorted into their own subcategories on each page, to make the UI a little cleaner.
Titles are now capitalized automatically in CSS, by default.
We now enforce a limit of 100 junk items.

Lint failed on this. Please run the Lint Repo task on VSCode

I don't see a need for the 100 junk cap. With dropsanity on you will easily clear 100 junk items. I think this one's a "buyer beware" kinda situation. Users already need to know logic pretty well.

Its a technical cap rather than a gameplay cap. I've allocated 100 flags for it. Placing more than 100 would make junk items use flags it shouldn't

Does this PR prohibit junk items being on enemies or melon crates? Whilst them being on enemies/melon crates doesn't break anything, it does take up valuable junk items (esp if dropsanity is on) given the experience isn't too dissimilar whether it's a junk item or a no item. We have it prohibited in non-plando, so just curious if that's the same for plando too.

I just edited the PR to prevent junk items being added in those places. I also added type hints and made a couple of other minor fixes.


Update es2015-node4 to es2015

Since we're using this package on browser we can't build the distribution version using es2015-node4.
consts will not work well in various browsers including Safari latest version.

LGTM. @franciscocardoso we should lower the base tests to node 0.10 to ensure browser compatibility.

:+1:


Switch to timestamps for hat snapshots

Would enable us to handle eg scrolling while saying a command
Note: the problem with this solution is that it requires cross-process reliable timestamps, which is challenging.  If we did go this route, we'd need to make sure that the monotonic clock used by Node.js is the same as that used by the word timestamps in Talon.  In case we go this route, here is some information that might be helpful:
Node.js monotonic clocks
From what I can tell, to get monotonic time in node.js, you’re supposed to use a function called process.hrtime.bigint().  It looks like that function is … mapped to the function uv_hrtime from libuv.  That function is defined differently on different processes:

using QueryPerformanceCounter on Windows,
using some heuristics on Linux,
using mach_absolute_time on Darwin,
like this on AIX,
using gethrtime on SunOS,
using __stckf on os390, and
using clock_gettime(CLOCK_MONOTONIC, &ts) for generic posix.

I’m still not in love with sending that barrier every time we issue any command in VSCode, but also have mixed feelings about using timestamps across process boundaries that are only supposed to be used for performance measurements.  Guessing we prob still should go the barrier route but if these clocks are the same as those used by talon, maybe it’s worth a try to use word timestamps?
Here's the solution below, if we went this route:
Talon side
We'd like to have talon use the momentary-style word timing information to send a timestamp alongside every decorated mark.  Inside the cursorless_decorated_symbol capture, we could just get the timing information off of the match object (m) and pass it through the json blob here
We should fallback to just using current timestamp in that function if word alignment not available, eg not on beta
Extension side
Cursorless will need to keep track of previous token maps along with the time range they existed, and also keep them up to date as the document changes.  We could probably just use a debounce to expire them, eg any old decoration map will expire after 5 seconds or something.
Then when we get a command that uses a decorated mark, we just use the token map that existed at the given timestamp

@AndreasArvidsson Curious why you closed this one? I opened it to track potentially switching to timing-based solution in the future to allow use cases like scrolling while issuing commands

We can already get all The timing information we need from talon touching a file. This just seamed like the original really complex solution that we already have solved much simpler. I might have misses something but what is suggested here doesn't give us any more data then we already have afaict.

Nope. Touching file just tells us when the phrase ended, not the moment they referred to a given hat. Using proper timing info will allow them to refer to hats from different remappings over the course of a single phrase as they scroll


www-dev_next-steps

Next steps for www-dev

That 404 handler applies https://github.com/openmicroscopy/www.openmicroscopy.org/pull/84/files#diff-aa8eb2fe477b2d36ecc0f14d6422513f

Proof of concept redirect added - requires (at least) some static content (the logo).

Successfully deployed against infra-testpr.openmicroscopy.org. To be tested this morning with @pwalczysko

The first round of testing finished, see column E

Discussed earlier today at the SA meeting, a proposal is to spend some bounded time (<1h) investigating the migration of this playbook to consume the openmicroscopy.nginx-proxy role which seems to offer lots of nice features required in our work.

Discussed with @kennethgillen, merging this playbook as the current state of the testing. Will start working against the issue reported by @pwalczysko.


Add link to whatsmy.info to README.

Add link to whatsmyua.info: easy, live testing/examination of useragent's results for arbitrary user agent strings!

The Travis failure is a build error, not a test failure. Unrelated to this change.


Log failed Iron jobs to failed_jobs table

Iron is currently down and jobs don't seem to be going to the failed_jobs table.

exception 'Http_Exception' with message 'http error: 503 | Service unavailable' in /var/app/current/vendor/iron-io/iron_core/IronCore.class.php:346

Stack trace:

#0 /var/app/current/vendor/iron-io/iron_core/IronCore.class.php(340): IronCore->reportHttpError(503, 'Service unavail...')

#1 /var/app/current/vendor/iron-io/iron_core/IronCore.class.php(299): IronCore->callWithRetries()

#2 /var/app/current/vendor/iron-io/iron_mq/IronMQ.class.php(273): IronCore->apiCall('POST', 'projects/534d7b...', Array)

#3 /var/app/current/vendor/laravel/framework/src/Illuminate/Queue/IronQueue.php(80): IronMQ->postMessage('default', 'eyJpdiI6ImFKeWc...', Array)

#4 /var/app/current/vendor/laravel/framework/src/Illuminate/Queue/IronQueue.php(65): Illuminate\Queue\IronQueue->pushRaw('{"job":"Worker\\...', NULL)

#5 [internal func
 tion]: Illuminate\Queue\IronQueue->push('....', Array)

#6 /var/app/current/vendor/laravel/framework/src/Illuminate/Queue/QueueManager.php(220): call_user_func_array(Array, Array)

Yeh. Ironmq is meant to be persisting your jobs for you. Not laravel. The failed jobs table is not for jobs that couldn't be queues, but for jobs that failed while being executed.

Oh I gotcha, didn't realize that thanks Graham.


fix: fail in case of missing core-js dependency

Fail to build if hoisted core-js version mismatch happens and provide instructions:

This condition allows any version matching 2.x.x.

Codecov Report

Merging #5342 into dev will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##              dev    #5342   +/-   ##
=======================================
  Coverage   95.66%   95.66%
=======================================
  Files          74       74
  Lines        2513     2513
  Branches      639      639
=======================================
  Hits         2404     2404
  Misses         92       92
  Partials       17       17

Impacted Files
Coverage Δ

packages/builder/src/builder.js
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


[Draft] ci: fix bagua ci problems

Open this pr to fix bagua ci problems

suspend this pr for the permission to the buildkite agents is revoked


Change order onShow and insert node

I came across the same problem as described here.
Getting the element in onShow callback to show/activate a modal won't work if doInsert is placed after the callback.
Changing the order seems to work.

Hi - just letting you know I've seen this PR and hope to soon (within the next few weeks) have time to look into it!


A z-index problem when use popup widgets in table cell

Use popup widget in table cell, such as dropdown, calendar, etc.
Table has fix columns

When a column has dropdown widget, and it is scrolled to half hide under fix columns, click the dropdown. this cell's z-index will be reseted to greater than fix columns's, therefore the whole cell will in front of fix column.
Current situation
z-index of table widgets

1: expand area
2: row index cell / body cell stick in left
3: body cell stick in right / row operators
4: header cell
5: header cell stick in left
6: header cell stick in right
7: focus within in body cell, focus within in expand area

so when focus within met, it is on top of others, including fix columns.
Predicament
z-index of the active cell (focus within), need to be:

Greater than or equals headers's, since popup might at to of cell,
Less than left fixed columns, since it is under bottom of fix columns,
Greater than other cells of unfixed columns, since popup might be covered by them.

Since cells of fix columns must under headers, since it might be scrolled. Obviously contradicts Target 1 and Target 2, making it impossible to achieve.
Recommendation
Don't use fix columns and dropdown widget in cell at the same time.

could be fixed, when DropdownUtils.findPortalCarrier is provided, this feature will be added at v1.2.5

fixed in v1.2.8, use the following settings on application startup.
make sure the app-frame dom node has all style variables which popup needs.
DropdownUtils.setDropdownDefaults({
    findPortalCarrier: () => document.getElementById('app-frame')!
});


Fix missing semicolumn for task with no param or retval

Added the missing parentheses.
This PR resolves issue #1.

Many thanks, @djoffe! One small question, I think I'm overlooking the line in the diff that adds the missing semicolon. I see one line where you added an extra layer of parens. Really just want to be sure that the fix is really present. Can you point me to the specific line?

@djoffe Line 418 fix this issue by adding proper (). Please merge it asap

Got it, thanks!

Sorry @mballance, missed your reply!
Thanks for the merge :)


[BUG] checkSignatures() is breaking local repos

https://github.com/eth0izzle/shhgit/blob/3fb0d7df259a645d5027df5b021cebaa6c5a373f/main.go#L140
Is causing issues when running this locally because it removes unexpected folders like .git, potentially breaking people's local work

Yes good catch. I've just pushed a fix.

Nice, now I don't nuke my local repo anymore when testing https://github.com/eth0izzle/shhgit/pull/54


enable stylus

Hi
I was trying to add stylus, the stylus-loader as the webpack loader only works on client side, so i was trying to update the webpack/client/config.js, by adding the loaders such as:
loaders: [     { test: /\.styl$/, loader: 'style-loader!css-loader!stylus-loader' }   ]
however the app still throws an error: ERROR in ../src/common/components/Layout/layout.styl
Module parse failed
and it's still complaint about i do not have the right loader for .styl files. Just wondering if i am adding it at the right place?
thanks

@Jinnified I've just added support of styles for boilerplate, please check it

thanks man, that works, however, i;d like to add yeticss to it as well, it seems that by adding
stylus: {
use: [yeticss()]
}
in the webpack client config.js doesn't take effect, and there is no error either, i wonder if i need to do something in the isompohic config too?

sorry my bad, forgot to add @import 'yeticss' in my styl file


Feature: Support gRPC protocol in CollectorExporter

Which problem is this PR solving?
In this PR, add gRPC support in CollectorExporter.
Fixes # (issue)
Short description of the change
How Has This Been Tested?
I've used this client in my production environment to export traces to Aliyun SLS, which supports gPRC protocol only.
Checklist:

[ ] Unit tests have been added
[x] Documentation has been updated

Security Insights
No security relevant content was detected by automated scans.
Action Items

Review PR for security impact; comment "security review required" if needed or unsure
Verify aviary.yaml coverage of security relevant code

Questions or Comments? Reach out on Slack: #support-infosec.

This PR should be a fix for #101.

@blakeroberts-wk The CI job test-darv2 fails because that an outdated protobuf package (2.1.0) is installed but gRPC requires at least 3.x. I update the pubspec.yaml and set protobuf: ^3.0.0.

@blakeroberts-wk From my observation, the protoc_plugin is the root cause of this issue. Starting from 21.0.0, it depends on protobuf: ^3.0.0. Unfortunately, the last gRPC package running on dart v2 depends on protobuf: ^2.0.0. I think one possible solution to fix this issue is to install protoc_plugin 20.0.1 on dart v2. It requires some hacks in Makefile.


Add GN

Description
(Brief description on what this PR is about)
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage:
Unit tests are added for small changes to verify correctness (e.g. adding a new operator)
Nightly tests are added for complicated/long-running ones (e.g. changing distributed kvstore)
Build tests will be added for build configuration changes (e.g. adding a new build option with NCCL)
[ ] Code is well-documented:
For user-facing API changes, API doc string has been updated.
For new C++ functions in header files, their functionalities and arguments are documented.
For new examples, README.md is added to explain the what the example does, the source of the dataset, expected performance on test set and reference to the original paper if applicable
Check the API doc at http://mxnet-ci-doc.s3-accelerate.dualstack.amazonaws.com/PR-$PR_ID/$BUILD_ID/index.html
[ ] To the my best knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[ ] Feature1, tests, (and when applicable, API doc)
[ ] Feature2, tests, (and when applicable, API doc)

Comments

If this change is a backward incompatible change, why must this change be made.
Interesting edge cases to note here

@zhanghang1989 Thanks for adding GN support. Can you please update PR description with more details?
@mxnet-label-bot [Gluon, pr-awaiting-review]

@zhanghang1989 Could you please look into the CI failures and fix the PR

cc: @codewithsk you were talking of adding GroupNorm operator.
@zhanghang1989 gentle reminder to update the PR.

Thanks! Will update after CVPR deadline :)

@mxnet-label-bot update [Gluon, pr-awaiting-response]
@zhanghang1989 Please update the PR description with info about the PR. Please add a test in tests/python/unittest/test_gluon.py
@sandeep-krishnamurthy for review

any update @zhanghang1989? it would be great to use this.

any update @zhanghang1989? it would be great to use this.
Please see this PR. The module is still not hybridizable.
https://github.com/apache/incubator-mxnet/pull/14196


Is there any changes in Your PhP conf then default EE Configuration

Just Wanted to know The changes in you php config than default ee config

Here the changes for php7.0, php7.1 & 7.2 use almost the same configuration
diff --git a/7.0/fpm/php.ini b/7.0/fpm/php.ini
index 7eed50b..2947c89 100644
--- a/7.0/fpm/php.ini
+++ b/7.0/fpm/php.ini
@@ -2,7 +2,7 @@
 engine = On
 short_open_tag = Off
 precision = 14
-output_buffering = 4096
+output_buffering = 8096
 zlib.output_compression = Off
 implicit_flush = Off
 unserialize_callback_func =
@@ -12,8 +12,9 @@ disable_classes =
 zend.enable_gc = On
 expose_php = Off
 max_execution_time = 300
-max_input_time = 60
-memory_limit = 128M
+max_input_time = 600
+max_input_vars = 10000
+memory_limit = 256M
 error_reporting = E_ALL & ~E_DEPRECATED & ~E_STRICT
 display_errors = Off
 display_startup_errors = Off
@@ -28,7 +29,7 @@ variables_order = "GPCS"
 request_order = "GP"
 register_argc_argv = Off
 auto_globals_jit = On
-post_max_size = 100M
+post_max_size = 128M
 auto_prepend_file =
 auto_append_file =
 default_mimetype = "text/html"
@@ -37,17 +38,17 @@ doc_root =
 user_dir =
 enable_dl = Off
 file_uploads = On
-upload_max_filesize = 100M
+upload_max_filesize = 128M
 max_file_uploads = 20
 allow_url_fopen = On
 allow_url_include = Off
 default_socket_timeout = 60
-date.timezone = America/New_York

 [CLI Server]
 cli_server.color = On

 [Date]
+date.timezone = Europe/Paris

Is there any fix for php fpm usage
If a page isn't cached and hit by too many user php fpm uses every single bit of memory and crash mysql
Although it can handle way too much when page is cached
So im thinking to Let wait those visitors for few sec and then serve only cached page

It's a normal php-fpm behavior, but like I said previously, load testing is a good idea, but it doesn't reflect real resources usage with high-traffic. It always send at least 5x more requests/connections to Nginx than real visitors

Thanks you are the best
Got it Although will do some testing with different php fpm pool conf


Explicitly name all subscriptions

Fixes #554

Codecov Report

Merging #555 (352f376) into main (50da615) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 352f376 differs from pull request most recent head 323e6ba. Consider uploading reports for the commit 323e6ba to get more accurate results

@@            Coverage Diff            @@
##              main      #555   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          281       281
  Lines        16406     16408    +2
=========================================
+ Hits         16406     16408    +2

Impacted Files
Coverage Δ

internal/blockchain/ethereum/ethereum.go
100.00% <100.00%> (ø)

internal/blockchain/ethereum/eventstream.go
100.00% <100.00%> (ø)

internal/database/sqlcommon/data_sql.go
100.00% <100.00%> (ø)

internal/database/sqlcommon/message_sql.go
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Remove embedding layer norm from clip text encoder and some fixes

Differential Revision: D38020819

Codecov Report

Merging #187 (492c8b0) into main (11e863e) will increase coverage by 0.05%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #187      +/-   ##
==========================================
+ Coverage   93.02%   93.08%   +0.05%
==========================================
  Files          47       47
  Lines        2812     2820       +8
==========================================
+ Hits         2616     2625       +9
+ Misses        196      195       -1

Impacted Files
Coverage Δ

...chmultimodal/modules/encoders/clip_text_encoder.py
100.00% <100.00%> (+2.63%)
:arrow_up:

Continue to review full report at Codecov.

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


Ambiguity in the grammar between quoted strings and backward compatible arrays

For example how should software interpret the value in key="a b c"? It could be either a string containing multiple spaces a b c or a backward compatible array of three strings (["a", "b", "c"]).
I think the easiest resolution of this ambiguity is to limit quoted arrays to only integer/real/boolean values, the same way '{' arrays are limited to string values. All the extxyz files I've seen in the wild use arrays in this way, so backward compatibility should be preserved. Do you agree @jameskermode?

I believe a string is the intended behavior.  There are no old style arrays
of strings, I think. Is this actually contradicted by some documentation or
by the reference implementation?

The 1D-array section (https://github.com/libAtoms/extxyz#one-dimensional-array-vector) of the readme says

backward compatible: opens with " or {, one or more of the same primitive types (strings only in {}) separated by whitespace, ends with matching " or }. For backward compatibility, a single element backward compatible array is interpreted as a scalar of the same type.

And "primitive types" allow strings, so that's how I understood this section. The pyleri grammar does not allow string (https://github.com/libAtoms/extxyz/blob/7ad3758400b7476ea7510d41333faa11ec0f0fc7/grammar/extxyz_kv_grammar.py#L60), so I guess the main thing to update is the documentation!

Although, looking at the code the next line in pyleri grammar says
https://github.com/libAtoms/extxyz/blob/7ad3758400b7476ea7510d41333faa11ec0f0fc7/grammar/extxyz_kv_grammar.py#L61
while the doc says only string values are allowed inside { arrays, so there is some inconsistency here.

No, the intention the opposite of what I think you're saying - string arrays are only allowed in {} (not "only string values are allowed in {}"), i.e. string arrays are not allowed in "".  I agree that this could be more clear, so I'll try to improve the wording.

Please take a look at the revised wording, tell me if it's more clear, and if you agree that it correctly communicates what the pyleri grammar actually implements.

The revised wording is much clearer, thanks!


HADOOP-19084. Prune hadoop-common transitive dependencies (#6574)

#6574 for trunk
Exclude more artifacts which are dependencies of hadoop-* modules, with the goal of keeping conflict out of downstream applications.
In particular we have pruned the dependencies of of: -zookeeper
-other libraries referencing logging
This keeps slf4j-log4j12 and log4j12 off the classpath of applications importing hadoop-common.
Somehow logback references do still surface; applications pulling in hadoop-common directly or indirectly should review their imports carefully.
Description of PR
How was this patch tested?
For code changes:

[x] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 22s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+0 :ok:
mvndep
14m 36s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
20m 14s

trunk passed

+1 :green_heart:
compile
9m  3s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
compile
8m 14s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
mvnsite
0m 54s

trunk passed

+1 :green_heart:
javadoc
0m 59s

trunk passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 54s

trunk passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
shadedclient
75m  7s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 22s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 23s

the patch passed

+1 :green_heart:
compile
8m 32s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javac
8m 32s

the patch passed

+1 :green_heart:
compile
8m 20s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
javac
8m 20s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
0m 56s

the patch passed

+1 :green_heart:
javadoc
0m 53s

the patch passed with JDK Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04

+1 :green_heart:
javadoc
0m 54s

the patch passed with JDK Private Build-1.8.0_392-8u392-ga-1~20.04-b08

+1 :green_heart:
shadedclient
24m 11s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 24s

hadoop-project in the patch passed.

+1 :green_heart:
unit
0m 25s

hadoop-yarn-applications-mawo-core in the patch passed.

+1 :green_heart:
asflicense
0m 41s

The patch does not generate ASF License warnings.

122m  2s

Subsystem
Report/Notes

Docker
ClientAPI=1.44 ServerAPI=1.44 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6582/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6582

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint

uname
Linux ce865468d6a5 5.15.0-94-generic #104-Ubuntu SMP Tue Jan 9 15:25:40 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 4c459094a0c7825c525e9f8b0a05467e4fc37fae

Default Java
Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.21+9-post-Ubuntu-0ubuntu120.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_392-8u392-ga-1~20.04-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6582/1/testReport/

Max. process+thread count
552 (vs. ulimit of 5500)

modules
C: hadoop-project hadoop-yarn-project/hadoop-yarn/hadoop-yarn-applications/hadoop-yarn-applications-mawo/hadoop-yarn-applications-mawo-core U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6582/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.

@steveloughran Thank you for the contribution! We can merge this PR now.


Redis server response timeout while trying to readAllKeySet from RMapCache

We use redisson 3.17.0 and redis version 6. We have redis cluster set up. We have a RMapCache that has about 600k entries in it. We have a use case to read all keys into memory from this cache. However, the readAllLKeySet() fails with
org.redisson.client.RedisResponseTimeoutException: Redis server response timeout (3000 ms) occured after 1 retry attempts. Increase nettyThreads and/or timeout settings. Try to define pingConnectionInterval setting. Command: (EVAL), params: [local s = redis.call('hgetall', KEYS[1]); local maxSize = tonumber(redis.call('hget', KEYS[5], 'max-..., 5, sotuDeviceCache, redisson__timeout__set:{sotuDeviceCache}, redisson__idle__set:{sotuDeviceCache}, redisson__map_cache__last_access__set:{sotuDeviceCache}, {sotuDeviceCache}:redisson_options,<PHONE_NUMBER>566], channel: [id: 0x392893e0, L:/<IP_ADDRESS>:42932 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379]
Our redis cluster config is as below
scanInterval: 1000
masterConnectionPoolSize: 128
masterConnectionMinimumIdleSize: 128
sslEnableEndpointIdentification: false
idleConnectionTimeout: 30000
connectTimeout: 10000
timeout: 3000
retryAttempts: 1
retryInterval: 300
readMode: "MASTER"
pingConnectionInterval: 60000
keepAlive: true
What is the recommended approach to read all keys from a cache which has many entries, without hitting a timeout?

Tried increasing timeout to 60000 , now the error we see is
org.redisson.client.RedisException: ERR Error running script (call to f_90fcfdb05f5b74bd69bd486619d1a8beeb29bf1b): @user_script:1: @user_script: 1: -READONLY You can't write against a read only replica.. channel: [id: 0xbf7856fa, L:/<IP_ADDRESS>:43012 - R:<IP_ADDRESS>/<IP_ADDRESS>:6379] command: (EVAL), promise: java.util.concurrent.CompletableFuture@3b140f41[Not completed, 1 dependents], params: [local s = redis.call('hgetall', KEYS[1]); local maxSize = tonumber(redis.call('hget', KEYS[5], 'max-..., 5, sotuDeviceCache, redisson__timeout__set:{sotuDeviceCache}, redisson__idle__set:{sotuDeviceCache}, redisson__map_cache__last_access__set:{sotuDeviceCache}, {sotuDeviceCache}:redisson_options,<PHONE_NUMBER>087]

can you share logs with trace logging level for org.redisson package?


Give a little space around the highest and lowest axis data points

When a graph is plotted in superset the highest and the lowest axis data points are plotted in the graph which doesn't look that good.

For eg, in grafana if the same graph is plotted it gives some white space on both the sides which makes the entire look quiet neat and clean.

So it would be great if superset if comes up with something similar.

Closing this since it's (arguably, at least) not a bug... if you want to open a PR adding an option to include such padding, that would be cool. Otherwise, we can move this to a GitHub Discussion of the Ideas variety if you'd like :) Thanks!


Pod disruption budgets are now policy/v1

As per https://kubernetes.io/docs/tasks/run-application/configure-pdb/#protecting-an-application-with-a-poddisruptionbudget
PodDisruptionBudget are now in policy/v1 so the beta will not work on new clusters > 1.21

@333miiko merging, thanks.


JSON_Serializable 1.5.1 nested objects compiler error

When trying to use json_serializable 1.5.1 for an object that had  the following structure I got the below error message:
Customer{...List...}
Order{...List...}
Product{String}
We're sorry, you've found a bug in our compiler.
You can report this bug at:
https://github.com/dart-lang/sdk/issues/labels/area-dev-compiler
Please include the information below in your report, along with
any other information that may help us track it down. Thanks!
dartdevc arguments: --dart-sdk=/usr/local/Cellar/dart/2.0.0/libexec --dart-sdk-summary=/usr/local/Cellar/dart/2.0.0/libexec/lib/_internal/ddc_sdk.sum --modules=amd -o packages/components_codelab/src/product/product.ddc.js --module-root=. --library-root=/lib --summary-extension=linked.sum --no-summarize --options=packages/build_modules/src/analysis_options.default.yaml --source-map --source-map-comment --inline-source-map -s packages/json_annotation/json_annotation.linked.sum --url-mapping=package:components_codelab/src/product/product.g.dart,packages/components_codelab/src/product/product.g.dart --url-mapping=package:components_codelab/src/product/product.dart,packages/components_codelab/src/product/product.dart package:components_codelab/src/product/product.g.dart package:components_codelab/src/product/product.dart
dart --version: 2.0.0 (Fri Aug 3 10:53:23 2018 +0200) on "macos_x64"
RangeError (byteOffset): Invalid value: Valid value range is empty: 0
#0      _ByteDataView.getUint32 (dart:typed_data/runtime/libtyped_data_patch.dart:4228:7)
#1      BufferContext._getUint32 (package:front_end/src/base/flat_buffers.dart:68:41)
#2      BufferContext.derefObject (package:front_end/src/base/flat_buffers.dart:54:21)
#3      TableReader.read (package:front_end/src/base/flat_buffers.dart:694:27)
#4      readPackageBundle (package:analyzer/src/summary/format.dart:4174:39)
#5      new PackageBundle.fromBuffer (package:analyzer/src/summary/idl.dart:939:7)
#6      SummaryDataStore._fillMaps (package:analyzer/src/summary/package_bundle_reader.dart:502:32)
#7      new SummaryDataStore.<anonymous closure> (package:analyzer/src/summary/package_bundle_reader.dart:405:43)
#8      List.forEach (dart:core/runtime/libgrowable_array.dart:274:8)
#9      new SummaryDataStore (package:analyzer/src/summary/package_bundle_reader.dart:405:18)
#10     new ModuleCompiler (package:dev_compiler/src/analyzer/module_compiler.dart:92:21)
#11     _compile (package:dev_compiler/src/analyzer/command.dart:131:18)
#12     compile (package:dev_compiler/src/analyzer/command.dart:57:5)
#13     _CompilerWorker.performRequest (file:///b/build/slave/dart-sdk-mac-stable/build/sdk/pkg/dev_compiler/bin/dartdevc.dart:43:20)
<asynchronous suspension>
#14     AsyncWorkerLoop.run.<anonymous closure> (package:bazel_worker/src/worker/async_worker_loop.dart:33:41)
#15     _rootRun (dart:async/zone.dart:1124:13)
#16     _CustomZone.run (dart:async/zone.dart:1021:19)
#17     _runZoned (dart:async/zone.dart:1516:10)
#18     runZoned (dart:async/zone.dart:1463:12)
#19     AsyncWorkerLoop.run (package:bazel_worker/src/worker/async_worker_loop.dart:33:26)
<asynchronous suspension>
#20     main (file:///b/build/slave/dart-sdk-mac-stable/build/sdk/pkg/dev_compiler/bin/dartdevc.dart:23:64)
<asynchronous suspension>
#21     _startIsolate.<anonymous closure> (dart:isolate/runtime/libisolate_patch.dart:277:32)
#22     _RawReceivePortImpl._handleMessage (dart:isolate/runtime/libisolate_patch.dart:165:12)

----

Is it really an issue? For general questions consider starting with Stack
Overflow:
https://stackoverflow.com/questions/tagged/dart

Also consider our Gitter channel for light-weight/quick discussions:
https://gitter.im/dart-lang/sdk

-----

This was also reported at https://github.com/dart-lang/sdk/issues/35968 and marked as fixed.

Duplicate of https://github.com/dart-lang/sdk/issues/35968


GOOGLE LOGIN AND SIGNUP FEATURE ADDED

Make sure the credentials are changed and request url is correct in google cloud console if you create your own cliend id.

@MuthuvelA Kindly resolve conflicts

@Priyaaa1 I have resolved the conflicts

@Priyaaa1 I have be assigned to this issue under level 3 but in pull request it is mentioned as level 1 so please change it to level 3


Code of conduct

We should have a code of conduct.
It'd make sense to use the CNCF Code of Conduct (as Prometheus does). If others agree, then we need a couple of volunteers to be listed as contacts.

We will need one anyway, as we will join CNCF. Personally, I prefer the FOSDEM one; but any balanced one will do.

I don't feel too strongly about it, but considering we're targeting OpenMetrics as a part of CNCF, I think it makes most sense to share the CoC with them. If you're looking for volunteers, I can be a named contact (perhaps more so because I do not work directly on any of the systems implementing OpenMetrics). We should have two people at least for redundancy / coverage purposes.
Let me know if you accept, and I'll send a PR adding a CoC + the representatives here.

I will ask the CNCF TOC about this today. I think it would be best if we had the contact people outside of the whole project; maybe CNCF can help us with that.

If you're a CNCF project, we ask you default to this: https://github.com/cncf/foundation/blob/master/code-of-conduct.md

@caniszczyk Just added this to the TOC slides: Can you help us with contact people? There's not a single female in OM, atm.

@RichiH for now, I'd recommend you simply default to https://www.contributor-covenant.org/ until the project is officially part of CNCF


[UNDERTOW-2254] Included the HttpServerExchange in the HostSelector.

This allows for advanced routing based on eg. header values or attributes.
Jira: https://issues.redhat.com/browse/UNDERTOW-2254

Also, please rebase it because the test failures we are seeing are supposed to have been fixed in master (UNDERTOW-2252), so hopefully after rebase they will be gone.

Thanks for the feedback @fl4via ! I updated the code and the commit message. I tried to rebase but got conflicts in all POM files though.

@jeham do you mind if I do the rebase then?
There is one thing that is calling my attention, though, and when I first reviewed this I didn't take notice. The PR should be done against master.
Do you need this feature specifically for 2.2.x?

Thanks for the reply @fl4via - I'll create a new PR from master.


Entities are not getting Pushed in Git.

If i Push the entities it'll only getting pushed in File Repository and not in Git Repository. Thingworx version -9

Hi,
Could you please provide more details about your issue? Are you working with an empty Git Repository and you are trying to push the entities from a ThingWorx file repository? First I would advise you to invoke the Pull service of your Git Backup Thing, then add your entities in the file repository and then perform the push.

Since no response was provided in this thread and this functionality was already validated on ThingWorx 9.0, the issue will be closed


Add missing report tax type codes

Description

added missing report tax types to the enum (CAPEXINPUT, UNDEFINED, CAPEXOUTPUT, ZEROEXPOUTPUT, GOODSIMPORT, NONEINPUT, NOTREPORTED)

Release Notes

Resolves Issue 430
Screenshots (if appropriate):
Types of Changes

[X] Bug fix (non-breaking change that fixes an issue)
[ ] New feature (non-breaking change that adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

The version number to be updated after overall review of this and other branches under investigation


Multiplying two double values giving wrong and negative result

I need to multiply two large numbers for example,
double x =<PHONE_NUMBER>00;
double result =x*x;

But i am getting negative value for this when building in flutter .
Please help me on this.

This is an interesting bug. It does not reproduce locally on Linux, so it seems like it's an effect of the way the code is compiled or run. As if the back-end treats double values like integers.

Any possible solution for this right now?

@MohanaSync From the screenshot above it says xValues[index] * xValues[index]. What is the type of xValues?
Could it be that there is a .toDouble() missing, i.e. xValues[index].toDouble()?

@mkustermann  u got it.. I have resolved this already by adding .toDouble().
Now its fine (y)

Let's close the issue then, since it is working as intended?


How to set GapWidth when plotting Col chart using function "AddChart"?

Description

Steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Output of go version:
(paste your output here)

Excelize version or commit ID:
(paste here)

Environment details (OS, Microsoft Excel™ version, physical, etc.):

Thanks for your issue. I added new fields GapWidth and Overlap in the Chart data type to support set gap width and overlap of the bar and column chart, please upgrade to the master branch code by go get -u github.com/xuri/excelize/v2@master. This feature will be released in the next version. Now you can set the gap width of the column chart like this:
gapWidth := uint(10)
&excelize.Chart{
    Type: excelize.Col,
+   GapWidth: &gapWidth,
    ...
}


Offset problems on a non-English system (again)

Hello, it's me again from the ussue #11
My Windows is in Russian, and since Mooscraper uses locale settings for separators (apparently), it only allows to input a comma there, yet that leads to a number of problems:

While it does save the value now (unlike before), CH just doesn't care about the decimal part of the offset if it's separated with a comma, it wants a dot.
If you try to load any chart with an offset that does use a dot in the .chart file, MS doesn't load it and any parameters after (Resolution, Player2, Difficulty, Genre, MediaType, MusicStream), using default ones instead.
If you try to open up a .chart with the comma-separated offset value, it ignores the decimal part, but does keep the int part.

Hopefully fixed. Give this test build a whirl and see if it works. Should've only been saving with the full-stop decimal point in the first place.
https://drive.google.com/open?id=1eV14F3DZLVoBzfVcycKWspBVWSjf2Ym7

All 3 problems still exist.

So just to clarify, when saving out a chart Moonscraper is saving offset in the format Offset = 0,5, instead of Offset = 0.5?

Yep, exactly that.

Try out this one- https://drive.google.com/open?id=1WnaovXBS6BEzonrd-GDU1s1dYyGNlF_3

Now it does save with a period instead of a comma, but other 2 problems (defaults half of properties with a period and ignores decimal part with a comma) are still a thing.

I'm not sure I understand? It's not valid for .chart to have commas as decimal separators in the first place. Are you saying there are other properties being written out with a comma or something?

No, no, everything is saving correctly now, I was just checking if it would parse a chart file with comma correctly (in case someone would open a file generated by an unfixed version in a fixed one). It's not critical really, just a nice to have for backwards compatibility.

Ah okay. I'm not going to worry about that. Offset isn't something that's recommended to be used in the first place as it's a very old legacy option, so this would be have affected very few users/charts. Sounds like the issue is fixed then. Feel free to use this test build until the next official release.

Wait wait wait, what about other problem, half the properties doesn't load from the correctly formatted file.

Can you be specific about which properties and provide an example .chart?

Any .chart file with non-integer offset value; upon opening it, Offset, Resolution, Player2, Difficulty, PreviewStart, PreviewEnd, Genre, MediaType, and MusicStream (or whatever happens to be under Offset in the file within [Song] section) get reset.

Loading a song with Offset 0.5 works fine for me.

Not on PC currently, but I remember investigating it, and loading same chart but with decimal part of the offset removed in a text editor it loaded just fine.

Was able to recreate with a blank project.
https://www.youtube.com/watch?v=mmy9LonsG6M
[Song]
{
  Name = "123"
  Artist = "123"
  Charter = "123"
  Album = "123"
  Year = ", 123"
  Offset = 0.1
  Resolution = 192
  Player2 = bass
  Difficulty = 3
  PreviewStart = 0
  PreviewEnd = 0
  Genre = "123"
  MediaType = "123"
  MusicStream = "song.ogg"
}
[SyncTrack]
{
  0 = TS 4
  0 = B 120000
}
[Events]
{
}

Managed to recreate the issue by changing the application's locale on startup. Issue has been fixed and will be available in the next release, or the next test build if you're a part of the MS Discord. If you need a build sooner for any charts you're currently working on let me know and I'll drop another download link into this thread in the next day day or so.


VP8 incompatibility between Android and iOS?

Every time I try to connect an Android client and an iOS client to each other, the Android client crashes. I'm seeing this in adb logcat *:E:
09-26 16:05:41.961  2911  4765 E ACodec  : [OMX.qcom.video.encoder.vp8] storeMetaDataInBuffers (output) failed w/ err -1010
09-26 16:05:41.971   255  2825 E OMXNodeInstance: getParameter(3c:qcom.encoder.vp8, ParamVideoAndroidVp8Encoder(0x6f600007)) ERROR: UnsupportedIndex(0x8000101a)

Nevermind. I need this apparently:
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />

Extremely cryptic errors, yay! 😞


Added --skip-store-validation for dev

WHY are these changes introduced?
Related to https://github.com/Shopify/develop-app-management/issues/236
Fixes an issue with running the CLI against Plus development stores

WHAT is this pull request doing?

Adds the --skip-store-validation option. If provided, the CLI will not attempt to validate if the store is one suitable for dev. Plus development stores, which are not owned by the partner account, will thus be dev-able.

How to test your changes?
Run dev, with --store=a-plus-dev-store.myshopify.com --skip-store-validation
Measuring impact
How do we know this change was effective? Please choose one:

[ ] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[x] Existing analytics will cater for this addition
[ ] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes
[x] I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

If I run dev with --store and --skip-store-validation, it allows to continue. But if I only add --skip-store-validation and I choose the same Plus store from the list, then it throws this error:
The store you specified (gonzaloriestra-dev-plus.myshopify.com) is not a dev store


[BUG] Unable to create support bundle agent pod in air-gap environment

Describe the bug (🐛 if you encounter this issue)
Install Longhorn master-head or v1.4.x-head in an air-gap environment (pull all required images from a private docker registry), Longhorn can be installed without error, but when try to generate support bundle, it stuck at progress 40%, and support bundle agent pod stuck in ImagePullBackOff:
longhorn-support-bundle-manager-support-bundle-2023-03-02t49b6k   1/1     Running            0          54m
backing-image-manager-7978-b7eb                                   1/1     Running            0          48m
share-manager-pvc-9bd22e50-8dd2-4da8-af40-14eab8a2d13b            1/1     Running            0          47m
supportbundle-agent-support-bundle-2023-03-02t04-54-22z-xntbt     0/1     ImagePullBackOff   0          54m
supportbundle-agent-support-bundle-2023-03-02t04-54-22z-b6pfv     0/1     ImagePullBackOff   0          54m
supportbundle-agent-support-bundle-2023-03-02t04-54-22z-st7n8     0/1     ImagePullBackOff   0          54m
supportbundle-agent-support-bundle-2023-03-02t04-54-22z-fgm9s     0/1     ImagePullBackOff   0          54m

with error:
Failed to pull image "lh-registry-oqfa6kxs.ci-qa.rancher.space/longhornio/support-bundle-kit:v0.0.17":
rpc error: code = Unknown
desc = failed to pull and unpack image "lh-registry-oqfa6kxs.ci-qa.rancher.space/longhornio/support-bundle-kit:v0.0.17":
failed to resolve reference "lh-registry-oqfa6kxs.ci-qa.rancher.space/longhornio/support-bundle-kit:v0.0.17":
pulling from host lh-registry-oqfa6kxs.ci-qa.rancher.space failed with status code [manifests v0.0.17]:
401 Unauthorized

but share-manager or backing-image-manager doesn't have this issue:
$ kubectl describe pod backing-image-manager-7978-b7eb -n longhorn-system
Events:
  Type    Reason   Age   From     Message
  ----    ------   ----  ----     -------
  Normal  Pulling  49m   kubelet  Pulling image "lh-registry-oqfa6kxs.ci-qa.rancher.space/longhornio/backing-image-manager:master-head"
  Normal  Pulled   49m   kubelet  Successfully pulled image "lh-registry-oqfa6kxs.ci-qa.rancher.space/longhornio/backing-image-manager:master-head" in 3.855532356s
  Normal  Created  49m   kubelet  Created container backing-image-manager
  Normal  Started  49m   kubelet  Started container backing-image-manager

$ kubectl describe pod share-manager-pvc-9bd22e50-8dd2-4da8-af40-14eab8a2d13b -n longhorn-system
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  48m   default-scheduler  Successfully assigned longhorn-system/share-manager-pvc-9bd22e50-8dd2-4da8-af40-14eab8a2d13b to ip-10-0-1-88
  Normal  Pulling    48m   kubelet            Pulling image "lh-registry-oqfa6kxs.ci-qa.rancher.space/longhornio/longhorn-share-manager:master-head"
  Normal  Pulled     48m   kubelet            Successfully pulled image "lh-registry-oqfa6kxs.ci-qa.rancher.space/longhornio/longhorn-share-manager:master-head" in 3.808941487s
  Normal  Created    48m   kubelet            Created container share-manager
  Normal  Started    48m   kubelet            Started container share-manager

and support-bundle-kit:v0.0.17 exists in the private docker registry for sure:
$ docker pull lh-registry-oqfa6kxs.ci-qa.rancher.space/longhornio/support-bundle-kit:v0.0.17
v0.0.17: Pulling from longhornio/support-bundle-kit
3ff3c85f9ea7: Already exists
9d3289b587ca: Pull complete
7220c0dd31c6: Pull complete
9adc021abc80: Pull complete
4d2e585c6540: Pull complete
8b3bd2bf5b73: Pull complete
c8b21374118b: Pull complete
feaa2287e1d4: Pull complete
Digest: sha256:4bd76b1e0f1180d34d2ba73f211d1e6bff362e2c28585f0cb3b8aaae80e1327a
Status: Downloaded newer image for lh-registry-oqfa6kxs.ci-qa.rancher.space/longhornio/support-bundle-kit:v0.0.17
lh-registry-oqfa6kxs.ci-qa.rancher.space/longhornio/support-bundle-kit:v0.0.17

To Reproduce
Install Longhorn in an air-gap environment, and generate support bundle.
It can be run automatically in jenkins like https://ci.longhorn.io/job/private/job/longhorn-tests-regression/3058/parameters/
Expected behavior
A clear and concise description of what you expected to happen.
Log or Support bundle
If applicable, add the Longhorn managers' log or support bundle when the issue happens.
You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment

Longhorn version:
Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version:

Number of management node in the cluster:
Number of worker node in the cluster:

Node config

OS type and version:
CPU per node:
Memory per node:
Disk type(e.g. SSD/NVMe):
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster:

Additional context
Add any other context about the problem here.

I thought we already respect the registry's secret. @c3y1huang Could you help check this? Thanks.

This is a day 1 issue. The support bundle agent DaemonSet is created by the support bundle manager. So we also need to fix this on our side and also upstream to have the support bundle manager feed in the registry secret when DaemonSet gets created.

@yangchiu can you help to mirror rancher/support-bundle-kit:v0.0.19 to longhornio. Thanks!

Test result: https://ci.longhorn.io/job/private/job/longhorn-tests-regression/3077/

manifest of master-head (longhorn 5a3f8d7) can pass air-gap test pipeline without errors.


Remove old config options from sample config

Overview
This commit removes the entire hinted-handoff section and some meta config options from the sample configuration file.
Fixes #6176
/cc @mark-rushakoff
Required for all non-trivial PRs

[x] Rebased/mergable
[x] Sign CLA (if not already signed)

:+1:

:+1:


[3/3] Add SNMP Dell tile

What does this PR do?
Adding snmp tile for Dell devices.
Motivation
Customers should be able to look for Dell within the integration page in the app
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] PR title must be written as a CHANGELOG entry (see why)
[ ] Files changes must correspond to the primary purpose of the PR as described in the title (small unrelated changes should have their own PR)
[ ] PR must have changelog/ and integration/ labels attached

On staging:
https://user-images.githubusercontent.com/45568537/103876293-bfbba780-50d3-11eb-8e3e-8e6127fcf446.mp4

On staging:
https://user-images.githubusercontent.com/45568537/103876293-bfbba780-50d3-11eb-8e3e-8e6127fcf446.mp4

@ruthnaebeck thank you for your review, I applied all your commit suggestions. Can you please review again?

@ruthnaebeck thank you for your review, I applied all your commit suggestions. Can you please review again?


Elcomsoft.ElcomsoftPhoneViewer version 5.40.39058.6970

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation failed with:

Manifest: The manifest file path must match PackageIdentifier and PackageVersion properties from manifest. actual
'manifests\e\Elcooft\ElcooftPhoneViewer\5.40.39058.6970', expected
'manifests\e\Elco***oft\PhoneViewer\5.40.39058.6970'

There's an extra Elcomsoft in the path, before PhoneViewer.

Anyone using a different git client should help me.


Update PDF2 dependency FOP 2.6

Description
Update PDF2 dependency FOP to version 2.6.
Motivation and Context
Contains bug fixes and keep up with latest FOP version.
How Has This Been Tested?
Tests pass.
Type of Changes

New feature (non-breaking change which adds functionality)

Documentation and Compatibility
Mention in release notes.

Updating FOP causes issues in unit tests that have nothing to do with FOP. So dependencies need to be tweaked in Gradle config to make this work.

We have not yet updated the FOP bundled with our Chemistry processor to 2.6, when we do if we notice any failing test which might indicate a bug/regression in FOP I will add a separate issue for that.


Incorrect "jsx-runtime“ exports

Describe the bug
In package.json there is an incorrect jsx-runtime exports: L97
"./jsx-runtime": {
  "types": "./types/jsx.d.ts",
  "default": "./dist/solid.js"
}

where ./dist/solid.js is incorrect. This will break compiler such a SWC or TSC when jsx runtime was imported directly (i.e, no vite-plugin-solid, even no vite).
The correct setup should be:
"./jsx-runtime": {
  "types": "./types/jsx.d.ts",
  "default": "./h/jsx-runtime/dist/jsx.js"
}

Your Example Website or App
https://github.com/LancerComet/solid-jsx-runtime-issue
Steps to Reproduce the Bug or Issue

Setup a new project which no vite-plugin-solid was introducted.
Let SWC or TSC use JSX Runtime directly, like:

.srcwc:
{
  "jsc": {
    "transform": {
      "react": {
        "runtime": "automatic",
        "importSource": "solid-js"
      }
    }
  }
}

or  tsconfig.json:
{
  "compilerOptions": {
    "jsx": "react-jsx",
    "jsxImportSource": "solid-js"
  }
}

Expected behavior
The correct setup in here should be:
"./jsx-runtime": {
  "types": "./types/jsx.d.ts",
  "default": "./h/jsx-runtime/dist/jsx.js"
}

Screenshots or Videos

Platform
Platform doesn't matter
Additional context
No response

This is intentional. We don't generally use a jsx-runtime but we need it for TS. We have a custom transform that has a completely different type of runtime. The expectation is to use "jsx": "preserve" and use our babel plugin. One day I hope we support a SWC one as well.
However, in some specific cases we support the the standard transform. This has reproccusions on ergonomics and performance. It is different enough it actually needs its own types because you need to author differently with it. We put that under its own location. Not to be confused with the preferred path.

Didn't expect that, and I'm starting to be curious about how the solidjs works. I am closing this issue for being given good explanation.


Template out gulpfile.js into reusable components

Is Your Feature Request Related To A Problem? Please describe.
In each repository lives a gulpfile.js, and most of the time this file is the exact same across most repositories. There are a few that are different, but mostly the same.
We should look to template this file and pull certain parts from a base config so that there isn't so much duplication across repositories.
Describe The Solution. Why is it needed?
Currently there is a lot of duplication in this file, and it could be condensed and placed in a template somehow. This also just needs updated to use new syntax where possible.
Additional Context.
A gulpfile is in every repository that uses choco-theme. See the README in this repo to find out what repositories those are.
Related Issues
n/a

Looked into this a bit and determined that at this time, this isn't worth the effort, and it may cause more problems down the rode if the template needs to diverge because of reasons. Each repo is the tiniest bit different, which makes this a bit more complicated than was intended, and it may just be more straightforward for each repo to have it's own gulpfile. Closing this for now.


SPIKE Row Level Security testing

Spike into how we can test our Postgres Row Level Security rules. The LF API will set most of the rules, but the frontend will also have some of it's own (ex. avatar storage uploading, not API related, but handled by Sveltekit backend).
It can sometimes be difficult to test these rules with browser based End-To-End (Playwright) tests because there's no way to get yourself into some of these edge cases with the UI. Example- I maliciously try to delete another user's Assistant.
We may required a different E2E testing tool (like Postman) to test the RLS rules.
Additional context
These tests should be integrated into the workflow, but may not necessarily have to be associated with just the UI or just the API.

What I did may have been overkill (or underkill depending one what you had in mind), but here's how I was tackling it from the API side of things: https://github.com/defenseunicorns/leapfrogai/pull/533


fix(http-server): Improve reuse of underlying TCP socket

After digging around in the wasmtime serve code, I found this neat little trick around reuseaddr which works on any linux or unix-like system (sorry Windows!). In my testing, this increased HTTP throughput by 10-15%

@vados-cosmonic I did check into that just so we have the information capture for our future selves (if we're optimizing anything). It looks like the queue size is a hint anyway and I did a test by bumping it down to 128 and it didn't affect the results

Ah @thomastaylor312 thanks for checking -- weird that it works but maybe the provider is reconnecting more than I expected!


Error due to incomplete change

Error: packages/apps/Bluetooth/src/com/android/bluetooth/avrcp/Avrcp.java:659: error: cannot find symbol
RemoteController.OnClientAvrcpUpdateListener {
Half changes is in packages_apps_bluetooth. And half in base
http://review.cyanogenmod.org/#/c/143310/ .Update base to latest tag(r37), packages_apps_bluetooth is tracked from cyanogen git and framework_base from resurrection, because of that, error in compilation.

Sorry, LP isn't supported anymore, revert that commit in BT repo if you want


Questions on networking commands, especially ipv4, subnet and gateway settings

File: engine/userguide/networking/work-with-networks.md
Docker version: 1.12.3
When creating a custom network, the short equivalent options such as --ip for com.docker.network.bridge.host_binding_ipv4 seem not available. For example:
>docker network create --ip=<IP_ADDRESS> my-network
unknown flag: --ip
See 'docker network create --help'.

And also, when I execute:
>docker network create -o "com.docker.network.bridge.host_binding_ipv4"="<IP_ADDRESS>" my-network
>docker network inspect my-network
[
    {
        "Name": "my-network",
        "Id": "e3513db030a28d0b8d22c3cf155e43c3b7c641493e90436bef8bae7c17a03da9",
        "Scope": "local",
        "Driver": "bridge",
        "EnableIPv6": false,
        "IPAM": {
            "Driver": "default",
            "Options": {},
            "Config": [
                {
                    "Subnet": "<IP_ADDRESS>/16",
                    "Gateway": "<IP_ADDRESS>/16"
                }
            ]
        },
        "Internal": false,
        "Containers": {},
        "Options": {
            "com.docker.network.bridge.host_binding_ipv4": "<IP_ADDRESS>"
        },
        "Labels": {}
    }
]

So the Subnet and Gateway were not affacted by ipv4 option

Sorry, you mis-read the topic a bit. The flag is --ip-range, and you also have to set --subnet and --gateway if you want them to all be  changed. See the example:
$ docker network create -d overlay \
  --subnet=<IP_ADDRESS>/16 \
  --subnet=<IP_ADDRESS>/16 \
  --gateway=<IP_ADDRESS> \
  --gateway=<IP_ADDRESS> \
  --ip-range=<IP_ADDRESS>/24 \
  --aux-address="my-router=<IP_ADDRESS>" --aux-address="my-switch=<IP_ADDRESS>" \
  --aux-address="my-printer=<IP_ADDRESS>" --aux-address="my-nas=<IP_ADDRESS>" \
  my-multihost-network

Hope that helps!

he didnt read it wrong, same problem here. it's not --ip-range, it's ip as stated in https://docs.docker.com/engine/userguide/networking/work-with-networks/#create-networks
com.docker.network.bridge.host_binding_ipv4 --ip Default IP when binding container ports

This is incorrect:
$ docker network create --help

Usage:	docker network create [OPTIONS] NETWORK

Create a network

Options:
      --attachable             Enable manual container attachment
      --aux-address map        Auxiliary IPv4 or IPv6 addresses used by Network driver (default map[])
  -d, --driver string          Driver to manage the Network (default "bridge")
      --gateway stringSlice    IPv4 or IPv6 Gateway for the master subnet
      --help                   Print usage
      --ingress                Create swarm routing-mesh network
      --internal               Restrict external access to the network
      --ip-range stringSlice   Allocate container ip from a sub-range
      --ipam-driver string     IP Address Management Driver (default "default")
      --ipam-opt map           Set IPAM driver specific options (default map[])
      --ipv6                   Enable IPv6 networking
      --label list             Set metadata on a network
  -o, --opt map                Set driver specific options (default map[])
      --subnet stringSlice     Subnet in CIDR format that represents a network segment

Perhaps this is a flag that has changed over time. @thaJeztah do you know about this?