Deeper IDE-like integration with Meson

I have been working on integrating Meson a little deeper with VS Code. The PR contains the following changes:

[x] Refactoring of the code structure - this was necessary to keep clean code
[x] Changes to the task definition schema - this is to allow "build" and "run" types of tasks for the same target
[x] Use of meson introspect as a data source

[x] Register a task provider to build targets and run executables
[x] New sidebar "tab" (aka. "View Container") with overview of Meson project

[x] Targets view with click-to-build feature

[x] Also show sources (broken in meson introspect)

[x] Tests view with click-to-run feature (broken in meson introspect)

[x] Configure Meson on activate (when meson.build in workspace, or opening a meson.build file)
[x] Extension configuration

[x] Configurable build directory
[x] Configurable configuration options

Debug configuration provider (would be nice to automatically configure debug for all executable targets)
[ ] Properly licensed icons (either getting icons with proper license for reuse or make custom ones - the ones in the repo are taken from vector-of-bool.cmake)

I've attached a screencast showcasing the workflow with the added changes: vscode-meson.zip (outdated)
Regarding the icons
We need some icons to properly convey the meaning of the different items. I can't draw for the life of me, so I'd need somebody to come in and get some icons for me to use.
Icons needed:

[x] Official Meson logo (provided and licensed by @jpakkane)
[ ] Executable target
[ ] Jar target
[ ] (Static) library
[ ] Subprojects icon
[ ] Subproject icon
[ ] Targets icon
[ ] Tests icon
[ ] Run target (optional, can use executable target icon)
[ ] Custom target (optional, can use the Meson logo)
[ ] Shared library (optional, can use shared library icon)

This looks amazing! Looking forward to having it merged :)

Some more thoughts about debugging. Since Meson supports multiple programming languages but doesn't provide information about how to debug them other than the executable filename, we'd need to know how to debug all supported project types.
Therefore I've removed the debug task off the PR for now, let the user manually set up the debug tasks (having them build before launch is easy now with the Meson tasks), maybe we can add that feature in another PR.

Some more progress:

Navigating the XServer code (as shown in screenshot) is still lightning fast as VS Code evaluates nodes lazily. Grouping targets and sources by folder makes is more organized, too.
Files have their associated icons, it's just that the development window has no extensions and zero config.

Moved individual TreeViews into a global one. I can't put tests under the subprojects because Meson introspection doesn't expose from which subprojects belong the tests.
I need to stop somewhere, so while I have other ideas, I think I'll work on getting the configuration going, and get proper icons, which, speaking of which, I'll update the PR details with mode details about what I need. Any contribution welcome!

To get out of the legal grey area of using somebody else's icons, I've opted to temporarily use Material Design Icons - their icons are SIL licensed but aren't specific enough to cover the cases here.

Promised, I'll work on the configuration next. :laughing:

Configuration: done. With an added bonus:
Note that the progress notification only shows when the command is invoked (through command palette and clicking on targets in the project view) and not when VS Code tasks are run - this is because tasks run ninja directly instead of letting extension control of what's happening.

I looked at this work in progress PR, and it looks really neat! I am ready to merge it as soon as you are ready, just let me know!

Finally uploaded the video I wanted to show a comment higher.
@asabil Well, we need a call for the new icons, unless you're happy with using the ones from MDI, in which case I have to integrate them for light themes.

I've squeezed one last feature: a picker for the Build command to select a target.
And with this, I'm opening up this PR for review, and for merging, if @asabil is okay with the Material Design Icons/

@asabil bump

This looks amazing! Thank you very much

One more thing, I just noticed that the README contains a notice about the cmake icons. These are no longer used, right? So we can remove that notice

I thought I had removed the notice on the README - but yes, since the MDI icons are now in use the CMake icons aren't anymore. You can remove that notice.

The extension is now updated on the Marketplace. Thanks again for this PR :)


Use random node for running commands

The nightly-run script should use a random node rather than relying on search-1. This will help us uncover misconfigurations more quickly and means we're more likely to have reliable infrastructure.
(Note that I haven't tested this change.)

Thank you!


useRouterMatch returns new object on each render

Version
5.1.2
Test Case
https://codesandbox.io/s/eloquent-wave-vlixh
Steps to reproduce
CodeSanbox has a reproducible case
Expected Behavior
useRouteMatch hook returns a match object, when combined with a useEffect it is expected that the effect will run only when the window location or path parameters change
Actual Behavior
useRouteMatch hook returns a match object, when combined with a useEffect with the match as dependency the effect is triggered on every state change.
The codesandbox example performs a state update on a timeout and logs match whenever it is changed. The logs show that on every update match has changed even if the path has not. Memoizing the match object on window.location.pathname prevents this and has the expected behaviour
This line in the hook returns the result of matchPath which creates a new object every time it is executed.
Possible solution would be to do something like
return path ?
  useMemo(() => matchPath(location.pathname, path), [location.pathname, path]) :
  match

I think that makes sense. Can you submit a PR?

Hi! There was kind of similar question about new match object created on each render - https://github.com/ReactTraining/react-router/issues/5099 .
The issue was closed because it is intentional, but now, with the useRouteMatch, the answer is that memoization could help.
@timdorr, is there any difference in these cases? Perhaps, Route could pass memoized match to its component too? It seems like it could help with kind of unnecessary re-rerenders described in the issue I linked above.
P.S. It could really help people like me, which migrating from RR3 to the last one and still use redux and react-redux. After migration we found out that our 'connected pure components' from react-redux connect HOC, which are passed to Route's component prop, aren't pure anymore.

Yes, that was when using lifecycle methods and a class component. You could "memoize" by way of shouldComponentUpdate to prevent a render. With Hooks, you're already in a render cycle, so it's not possible to bail out. That's why useMemo/useCallback even exist, so you can safely memoize values directly.

Thanks for quick reply!
As i understood, you don't think that it makes sense if Route could memoize match object out of the box (like it was described for useRouteMatch) in order to recalculate and pass new match object to component props only when the location or path parameters have changed?

I face the same problem with useRouteMatch  today what is the status of this issue ?

same issue with useLocation
const location = useLocation();

...

useEffect(() => {
	console.log(location)
}, [location]);

Go infinite loop

I tried to reproduce infinite loop in my code for useLocation and i wasn't able to reproduce.

@LoiKos Sorry, I have just noticed that my code was not complete. I was calling history.replace to reset the location state

Yes i can reproduce the infinite loop which is normal btw. You try to add a state with  history.replace({ pathname: "/currentPath", state: { comeFromError: undefined } }); but as state is a part of location you create an infinite loop. If you only want to create the state the first time you came on /currentPath then you have to listen to location.pathname as you find.
In my opinion the best practice with hooks dependencies is to be as accurate as possible on which variable you want to listen to. That avoid unnecessary operation and bugs that come from an object getting updated but not the part you want to look after.
I think you also forget to add history in your dependencies

still looking for an update. Can this be memoized inside the package?
Scenario:
When using useRouteMatch and a primative property of match.params, it can't be passed into the dependency array because that property doesn't exist if there isn't a match.

A bit off topic, but simply using useLocation inside a memo'ed component will cause a rerendering if any Route above the component rerenders: https://codesandbox.io/s/festive-greider-8did7
The location value isn't changed so it is trival to work-around, but quite a gothca IMO. https://github.com/facebook/react/issues/15156#issuecomment-474590693 for a related discussion.

If you want to perform side-effects on location change, then I think you can prob just rely on location:
const location = useLocation();
const match = useMatch();
useEffect(() => {
  // The location has changed
  nonIdempotentSideEffect(match.params.foo);
}, [location])

Or I think you could make match stable in user land like this:
const useStableRouteMatch = () => {
  const _match = useRouteMatch();
  const location = useLocation();
  const [match, setMatch] = useState(_match);
  useEffect(() => {
    setMatch(_match);
  }, [location]);
  return match;
};

// ...

const match = useStableRouteMatch();
useEffect(() => {
  // The location has changed
  nonIdempotentSideEffect(match.params.foo);
}, [match]);

However, I don't think using React.useMemo would be safe unless you were merely trying to improve render performance as there's no guarantee React won't just throw away the memo'd value, e.g. don't do this:
const useMemoRouteMatch = () => {
  const match = useRouteMatch();
  const location = useLocation();
  return useMemo(() => match, [location]);
}

// ...

const match = useMemoRouteMatch();
useEffect(() => {
  // The location has changed *or react has discarded the memo'd match value*
  nonIdempotentSideEffect(match.params.foo);
}, [match]);

Same for other hooks like useParams. It triggers a rerender on every route change, even if there are no params in url. So basically using hooks = trigger app rerender on every route change.
Maybe passing props you want to subscribe to into this hooks may help.

Nested routes trigger the infinite re-render loop. Would be great to memoize the hooks +1

I also get an infinite loop with useHistory and useLocation.
Steps:

Open URL with a query string and load a specific a route
Use useLocation to detect query string
If there is query string use useHistory to redirect to same URL without the query string
The URL changes in the browser but useLocation keeps detecting the previous query string and triggering step 3 which keeps redirecting to URL without query string (step 4) and so on...

+1

I am still having this issue, is there a update on it?

Unclear on what's the stance on <Router match> object memoization --- should we create a new issue for that?
(Haven't checked if v6 changed the behavior already.)

In the meantime this history.listen function works pretty well for me https://github.com/ReactTraining/history/blob/v4/docs/GettingStarted.md#listening

An example of how I use history.listen
function useListenHistory(fn) {
  const [state, setState] = useState(fn());
  const history = useHistory();

  useEffect(() => history.listen(() => {
    const newState = fn();

    if (newState !== state) {
      setState(newState);
    }
  }));

  return state;
}

export function useAtHome() {
  const getAtHome = () => window.location.pathname === '/';
  return useListenHistory(getAtHome);
}

This is causing all kind of unnecessary re-rendering, we've had to write our own set of wrapper functions to compensate

An example of how I use history.listen
function useListenHistory(fn) {
  const [state, setState] = useState(fn());
  const history = useHistory();

  useEffect(() => history.listen(() => {
    const newState = fn();

    if (newState !== state) {
      setState(newState);
    }
  }));

  return state;
}

export function useAtHome() {
  const getAtHome = () => window.location.pathname === '/';
  return useListenHistory(getAtHome);
}

your example has zero memoization itself neither in getAtHome nor in useEffect and guess what, your useEffect is triggered on every render. Add deps to useEffect and wrap getAtHome with useCallback.

An example of how I use history.listen
function useListenHistory(fn) {
  const [state, setState] = useState(fn());
  const history = useHistory();

  useEffect(() => history.listen(() => {
    const newState = fn();

    if (newState !== state) {
      setState(newState);
    }
  }));

  return state;
}

export function useAtHome() {
  const getAtHome = () => window.location.pathname === '/';
  return useListenHistory(getAtHome);
}

your example has zero memoization itself neither in getAtHome nor in useEffect and guess what, your useEffect is triggered on every render. Add deps to useEffect and wrap getAtHome with useCallback.

I've opened up a PR to start a discussion on how this issue could be resolved in https://github.com/ReactTraining/react-router/pull/7822.

Is there any update on the PR?

The update is that I'll be reviewing in the next week or two. This one is on the radar.

Created a new PR (#8431) to resolve this issue.

That's now released in 6.1.0! :)


How to disable mouse scroll wheel scaling?

Hi, Trying to figure out how to prevent auto scroll / scaling on the map when user moves across the map?  I tried these settings, but didn't have an effect:
scrollwheel:false
Thanks!

Hi,
how are you setting that option?
Here's how to use it:
var maplace = new Maplace({
    locations: places,
    map_options: {
        scrollwheel: false
    }
});

Hi Daniel
I tried it in calling the script, like this:
new Maplace({

	locations: LocsA,
	map_div: '#gmap-menu',
	controls_type: 'list',
	controls_on_map: false,
	scrollwheel: false,
	styles: {
    	'Night': [
		{
		"featureType": "administrative.country",
		"elementType": "geometry",
		"stylers": [
        {
            "visibility": "simplified"
        },
        {
            "hue": "#ff0000"
        }
    ]
}
]
}
})


wshd crashed when it creating a container

Hey,I got a trouble when i want to start a cf application. probably someone with more knowledge about warden can give me hand on this? thanks very much.
my environment is cf-207 with stemcell bosh-stemcell-2922-openstack-kvm-centos-7-go_agent-raw
here is the coredump:
[15:27 root@70092ee0-74c5-4aea-abf4-34cab028d65a:/var/vcap] > gdb /var/vcap/data/warden/depot/18kf6r4vr06/bin/wshd /var/vcap/sys/cores/core-wshd-11-1-1429887869
GNU gdb (GDB) Red Hat Enterprise Linux 7.6.1-64.el7
Copyright (C) 2013 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /var/vcap/data/warden/depot/18kf6r4vr06/bin/wshd...done.
[New LWP 1]
Core was generated by `./bin/wshd --run ./run --lib ./lib --root ./mnt --title wshd: 18kf6r4vr06'.
Program terminated with signal 11, Segmentation fault.
#0  0x000000000040a7c7 in abort ()
(gdb) p errno
Cannot find thread-local variables on this target
(gdb) bt full
#0  0x000000000040a7c7 in abort ()
No symbol table info available.
#1  0x0000000000402947 in child_run (data=0x1bc1d30) at wshd.c:716
        w = 0x1bc1d30
        rv = -1
        pivoted_lib_path = "/mnt/var/vcap/data/warden/depot/18kf6r4vr06/lib\000\337\375I\000\000\000\000\000\060\036\274\001", '\000' <repeats 20 times>, "p\000\363a\377\177\000\000\000\000\000\000\000\000\000\000./lib/hook-parent-before-clone.sh", '\000' <repeats 3911 times>...
        pivoted_lib_path_len = 4
        __PRETTY_FUNCTION__ = "child_run"
#2  0x00000000004439d9 in clone ()
No symbol table info available.
(gdb) info r
rax            0x6	6
rbx            0x10	16
rcx            0x450a67	4524647
rdx            0x6	6
rsi            0x1	1
rdi            0x1	1
rbp            0x7fff61f31030	0x7fff61f31030
rsp            0x7fff61f30000	0x7fff61f30000
r8             0x0	0
r9             0x7fff61f2fe20<PHONE_NUMBER>02752
r10            0x8	8
r11            0x202	514
r12            0x0	0
r13            0x405190	4215184
r14            0x405220	4215328
r15            0x0	0
rip            0x402947	0x402947 <child_run+341>
eflags         0x10246	[ PF ZF IF RF ]
cs             0x33	51
ss             0x2b	43
ds             0x0	0
es             0x0	0
fs             0x63	99
gs             0x0	0
(gdb)

is the container running the default root filesystem? (cflinuxfs2)
is there a small similar app that reproduces this error?

This would help us investigate the issue in a comparable environment.
The Cloud Foundry Runtime Team
Dan and Serguei

@DanLavine,

is the container running the default root filesystem? (cflinuxfs2)

yes, the container running cflinuxfs2

is there a small similar app that reproduces this error?

I am testing with cf_demoapp_nodejs,you can try it.
BTW,It work correctly with stemcell bosh-stemcell-2881-openstack-kvm-ubuntu-trusty-go_agent-raw.
Is it a compatible problem withe centos-7?
thanks.

Hi @guanglinlv,
It seems like the issues is probably coming from the Centos stemcell as we cannot reproduce this on the official Ubuntu stemcell. CF-Release is not tested or supported on the Centos stemcell.
The CF Runtime Team
@DanLavine && @jpalermo

Hi @guanglinlv,
It seems like the issues is probably coming from the Centos stemcell as we cannot reproduce this on the official Ubuntu stemcell. CF-Release is not tested or supported on the Centos stemcell.
The CF Runtime Team
@DanLavine && @jpalermo


Second fix of python version, keep python2.7

This is a followup fix for PR #607

@dorodnic Travis green, I think it is safe to merge even Appveyer is not completed(no change to code and appveyor.yml)


feat!: updating google-auth-library-java min Java version to 1.8

Release-As: 1.0.0
feat: updating google-auth-library-java min Java version to 1.8

reopening to remove java 7 ci


Added Automatic Brace Completion #808

This enables Automatic Brace Completion the solution is very similar to that, that @crwilcox  suggested.

@martinzimmermann, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, MSBOT;

Looks good! The one bit that bothers me is the helper function in the test to enable/disable brace completion. We used to have code like that all over the place and it is notoriously unreliable.
It should be possible to get at the setting through DTE, as we do in a few other places. When I get a bit of time, I'll see if I can track down the names needed to find the setting.

 I tried to get it working through DTE but after a few hours I gave up. A MSDN article suggested that the names can be found in the registry, but I wasn’t able to locate the TextEditor -> Python -> General option page.
If you can point me in the right direction I can also update the test myself.

Sorry I took so long to get around to this - things have been very busy here. Because of the conflicts (which weren't real conflict), I've merged this by hand. Hopefully is still has your name on it, but I can't be sure of that (wasn't a regular git merge... git and I don't get along that well :) )
You'll see it appear in our next major update, which is going to be a while away yet (preview builds coming soon though), but congrats on being the first external contributor for it!

I think something went wrong, because it is not associated with my Github account (Github associates commits by commit email as far as I know) however I don’t care as long as it is fixed.
Also I’m very honored to be the first external contributor (I probably should commit another thing to claim that status officially :stuck_out_tongue_winking_eye:)

Yeah, I think the email got dropped when I moved it :( Sorry about that.
You're more than welcome to contribute more (though it is only first external contributor for our next release - but there haven't been many in the past, so you're probably still in the first 10 ;) )


Why dependency-groups and not project.optional-dependencies? (PEP 621)

I'm using uv 0.4.30 version, and comparing the generated by UV pyproject.toml between PEP 621 I found this difference.
I just would like more details about it. Thank you!!

Optional dependencies are also supported. They are intended for library consumers to install optional packages, and are a public interface because of that. I've used them a lot of times as a hack to collect things that aren't for consumers but for me as a library developer, such as installing linters or pytest.
With dependency-groups, I can have build or test dependencies that I can install without exposing those to users in any public interface. dependency-groups are also a PEP, PEP 735.

Yeah, for local development, they're effectively identical in uv. The main difference from that perspective is that optional-dependencies are part of the published metadata for your package, while dependency-groups are only visible when working with your package locally. For example, if your package is foo, and you have an optional group called bar and a dependency group called baz, when you publish to PyPI, users can uv pip install foo[bar] (but uv pip install foo[baz] would error).
There are some other differences that are articulated in the PEP. For example, you can use dependency-groups without a [project] table, while optional-dependencies requires a [project] table. But that doesn't affect uv much right now since uv lock, uv sync, etc. all require projects.


line 26, in  |  ModuleNotFoundError: No module named 'ghauri.common'; 'ghauri' is not a package

┌──(ma㉿Windows11)-[~]
└─$ sudo git clone https://github.com/r0oth3x49/ghauri.git
Cloning into 'ghauri'...
remote: Enumerating objects: 1039, done.
remote: Counting objects: 100% (252/252), done.
remote: Compressing objects: 100% (139/139), done.
remote: Total 1039 (delta 125), reused 128 (delta 113), pack-reused 787
Receiving objects: 100% (1039/1039), 362.58 KiB | 338.00 KiB/s, done.
Resolving deltas: 100% (772/772), done.
┌──(ma㉿Windows11)-[~]
└─$ cd ghauri
┌──(ma㉿Windows11)-[~/ghauri]
└─$ ls
ghauri  LICENSE  README.md  requirements.txt  setup.py
┌──(ma㉿Windows11)-[~/ghauri]
└─$ pwd
/home/ma/ghauri
┌──(ma㉿Windows11)-[~/ghauri]
└─$ sudo python3 -m pip install --upgrade -r requirements.txt
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/ratelimit-2.2.1-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/dicttoxml-1.7.16-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/requests_file-2.1.0-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/idna-3.7-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/tldextract-5.1.2-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/certifi-2024.7.4-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/chardet-5.2.0-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/filelock-3.15.4-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/charset_normalizer-3.3.2-py3.11-linux-x86_64.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/arjun-2.2.6-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
Requirement already satisfied: tldextract in /usr/local/lib/python3.11/dist-packages/tldextract-5.1.2-py3.11.egg (from -r requirements.txt (line 1)) (5.1.2)
Requirement already satisfied: colorama in /usr/local/lib/python3.11/dist-packages (from -r requirements.txt (line 2)) (0.4.6)
Requirement already satisfied: requests in /usr/local/lib/python3.11/dist-packages (from -r requirements.txt (line 3)) (2.31.0)
Collecting requests (from -r requirements.txt (line 3))
Downloading requests-2.32.3-py3-none-any.whl.metadata (4.6 kB)
Requirement already satisfied: chardet in /usr/local/lib/python3.11/dist-packages/chardet-5.2.0-py3.11.egg (from -r requirements.txt (line 4)) (5.2.0)
Requirement already satisfied: idna in /usr/local/lib/python3.11/dist-packages/idna-3.7-py3.11.egg (from tldextract->-r requirements.txt (line 1)) (3.7)
Requirement already satisfied: requests-file>=1.4 in /usr/local/lib/python3.11/dist-packages/requests_file-2.1.0-py3.11.egg (from tldextract->-r requirements.txt (line 1)) (2.1.0)
Requirement already satisfied: filelock>=3.0.8 in /usr/local/lib/python3.11/dist-packages/filelock-3.15.4-py3.11.egg (from tldextract->-r requirements.txt (line 1)) (3.15.4)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.11/dist-packages/charset_normalizer-3.3.2-py3.11-linux-x86_64.egg (from requests->-r requirements.txt (line 3)) (3.3.2)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/lib/python3/dist-packages (from requests->-r requirements.txt (line 3)) (1.26.18)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.11/dist-packages/certifi-2024.7.4-py3.11.egg (from requests->-r requirements.txt (line 3)) (2024.7.4)
Downloading requests-2.32.3-py3-none-any.whl (64 kB)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 64.9/64.9 kB 254.5 kB/s eta 0:00:00
Installing collected packages: requests
Attempting uninstall: requests
Found existing installation: requests 2.31.0
Uninstalling requests-2.31.0:
Successfully uninstalled requests-2.31.0
Successfully installed requests-2.32.3
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
┌──(ma㉿Windows11)-[~/ghauri]
└─$ sudo python3 setup.py install
running install
/usr/local/lib/python3.11/dist-packages/setuptools/_distutils/cmd.py:66: SetuptoolsDeprecationWarning: setup.py install is deprecated.
!!
    ********************************************************************************
    Please avoid running ``setup.py`` directly.
    Instead, use pypa/build, pypa/installer or other
    standards-based tools.

    See https://blog.ganssle.io/articles/2021/10/setup-py-deprecated.html for details.
    ********************************************************************************

!!
self.initialize_options()
/usr/local/lib/python3.11/dist-packages/setuptools/_distutils/cmd.py:66: EasyInstallDeprecationWarning: easy_install command is deprecated.
!!
    ********************************************************************************
    Please avoid running ``setup.py`` and ``easy_install``.
    Instead, use pypa/build, pypa/installer or other
    standards-based tools.

    See https://github.com/pypa/setuptools/issues/917 for details.
    ********************************************************************************

!!
self.initialize_options()
running bdist_egg
running egg_info
creating ghauri.egg-info
writing ghauri.egg-info/PKG-INFO
writing dependency_links to ghauri.egg-info/dependency_links.txt
writing entry points to ghauri.egg-info/entry_points.txt
writing requirements to ghauri.egg-info/requires.txt
writing top-level names to ghauri.egg-info/top_level.txt
writing manifest file 'ghauri.egg-info/SOURCES.txt'
reading manifest file 'ghauri.egg-info/SOURCES.txt'
adding license file 'LICENSE'
writing manifest file 'ghauri.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build
creating build/lib
creating build/lib/ghauri
copying ghauri/init.py -> build/lib/ghauri
copying ghauri/ghauri.py -> build/lib/ghauri
creating build/lib/ghauri/scripts
copying ghauri/scripts/init.py -> build/lib/ghauri/scripts
copying ghauri/scripts/ghauri.py -> build/lib/ghauri/scripts
creating build/lib/ghauri/logger
copying ghauri/logger/colored_logger.py -> build/lib/ghauri/logger
copying ghauri/logger/init.py -> build/lib/ghauri/logger
creating build/lib/ghauri/core
copying ghauri/core/request.py -> build/lib/ghauri/core
copying ghauri/core/update.py -> build/lib/ghauri/core
copying ghauri/core/init.py -> build/lib/ghauri/core
copying ghauri/core/inject.py -> build/lib/ghauri/core
copying ghauri/core/extract.py -> build/lib/ghauri/core
copying ghauri/core/tests.py -> build/lib/ghauri/core
creating build/lib/ghauri/dbms
copying ghauri/dbms/fingerprint.py -> build/lib/ghauri/dbms
copying ghauri/dbms/init.py -> build/lib/ghauri/dbms
creating build/lib/ghauri/extractor
copying ghauri/extractor/advance.py -> build/lib/ghauri/extractor
copying ghauri/extractor/init.py -> build/lib/ghauri/extractor
copying ghauri/extractor/common.py -> build/lib/ghauri/extractor
creating build/lib/ghauri/common
copying ghauri/common/prettytable.py -> build/lib/ghauri/common
copying ghauri/common/session.py -> build/lib/ghauri/common
copying ghauri/common/colors.py -> build/lib/ghauri/common
copying ghauri/common/config.py -> build/lib/ghauri/common
copying ghauri/common/init.py -> build/lib/ghauri/common
copying ghauri/common/payloads.py -> build/lib/ghauri/common
copying ghauri/common/utils.py -> build/lib/ghauri/common
copying ghauri/common/banner.py -> build/lib/ghauri/common
copying ghauri/common/lib.py -> build/lib/ghauri/common
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/ghauri
creating build/bdist.linux-x86_64/egg/ghauri/scripts
copying build/lib/ghauri/scripts/init.py -> build/bdist.linux-x86_64/egg/ghauri/scripts
copying build/lib/ghauri/scripts/ghauri.py -> build/bdist.linux-x86_64/egg/ghauri/scripts
creating build/bdist.linux-x86_64/egg/ghauri/logger
copying build/lib/ghauri/logger/colored_logger.py -> build/bdist.linux-x86_64/egg/ghauri/logger
copying build/lib/ghauri/logger/init.py -> build/bdist.linux-x86_64/egg/ghauri/logger
creating build/bdist.linux-x86_64/egg/ghauri/core
copying build/lib/ghauri/core/request.py -> build/bdist.linux-x86_64/egg/ghauri/core
copying build/lib/ghauri/core/update.py -> build/bdist.linux-x86_64/egg/ghauri/core
copying build/lib/ghauri/core/init.py -> build/bdist.linux-x86_64/egg/ghauri/core
copying build/lib/ghauri/core/inject.py -> build/bdist.linux-x86_64/egg/ghauri/core
copying build/lib/ghauri/core/extract.py -> build/bdist.linux-x86_64/egg/ghauri/core
copying build/lib/ghauri/core/tests.py -> build/bdist.linux-x86_64/egg/ghauri/core
creating build/bdist.linux-x86_64/egg/ghauri/dbms
copying build/lib/ghauri/dbms/fingerprint.py -> build/bdist.linux-x86_64/egg/ghauri/dbms
copying build/lib/ghauri/dbms/init.py -> build/bdist.linux-x86_64/egg/ghauri/dbms
copying build/lib/ghauri/init.py -> build/bdist.linux-x86_64/egg/ghauri
copying build/lib/ghauri/ghauri.py -> build/bdist.linux-x86_64/egg/ghauri
creating build/bdist.linux-x86_64/egg/ghauri/extractor
copying build/lib/ghauri/extractor/advance.py -> build/bdist.linux-x86_64/egg/ghauri/extractor
copying build/lib/ghauri/extractor/init.py -> build/bdist.linux-x86_64/egg/ghauri/extractor
copying build/lib/ghauri/extractor/common.py -> build/bdist.linux-x86_64/egg/ghauri/extractor
creating build/bdist.linux-x86_64/egg/ghauri/common
copying build/lib/ghauri/common/prettytable.py -> build/bdist.linux-x86_64/egg/ghauri/common
copying build/lib/ghauri/common/session.py -> build/bdist.linux-x86_64/egg/ghauri/common
copying build/lib/ghauri/common/colors.py -> build/bdist.linux-x86_64/egg/ghauri/common
copying build/lib/ghauri/common/config.py -> build/bdist.linux-x86_64/egg/ghauri/common
copying build/lib/ghauri/common/init.py -> build/bdist.linux-x86_64/egg/ghauri/common
copying build/lib/ghauri/common/payloads.py -> build/bdist.linux-x86_64/egg/ghauri/common
copying build/lib/ghauri/common/utils.py -> build/bdist.linux-x86_64/egg/ghauri/common
copying build/lib/ghauri/common/banner.py -> build/bdist.linux-x86_64/egg/ghauri/common
copying build/lib/ghauri/common/lib.py -> build/bdist.linux-x86_64/egg/ghauri/common
byte-compiling build/bdist.linux-x86_64/egg/ghauri/scripts/init.py to init.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/scripts/ghauri.py to ghauri.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/logger/colored_logger.py to colored_logger.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/logger/init.py to init.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/core/request.py to request.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/core/update.py to update.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/core/init.py to init.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/core/inject.py to inject.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/core/extract.py to extract.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/core/tests.py to tests.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/dbms/fingerprint.py to fingerprint.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/dbms/init.py to init.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/init.py to init.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/ghauri.py to ghauri.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/extractor/advance.py to advance.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/extractor/init.py to init.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/extractor/common.py to common.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/common/prettytable.py to prettytable.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/common/session.py to session.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/common/colors.py to colors.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/common/config.py to config.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/common/init.py to init.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/common/payloads.py to payloads.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/common/utils.py to utils.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/common/banner.py to banner.cpython-311.pyc
byte-compiling build/bdist.linux-x86_64/egg/ghauri/common/lib.py to lib.cpython-311.pyc
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying ghauri.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying ghauri.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying ghauri.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying ghauri.egg-info/entry_points.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying ghauri.egg-info/not-zip-safe -> build/bdist.linux-x86_64/egg/EGG-INFO
copying ghauri.egg-info/requires.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying ghauri.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
creating dist
creating 'dist/ghauri-1.3.5-py3.11.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing ghauri-1.3.5-py3.11.egg
creating /usr/local/lib/python3.11/dist-packages/ghauri-1.3.5-py3.11.egg
Extracting ghauri-1.3.5-py3.11.egg to /usr/local/lib/python3.11/dist-packages
Adding ghauri 1.3.5 to easy-install.pth file
Installing ghauri script to /usr/local/bin
Installed /usr/local/lib/python3.11/dist-packages/ghauri-1.3.5-py3.11.egg
Processing dependencies for ghauri==1.3.5
Searching for chardet==5.2.0
Best match: chardet 5.2.0
Processing chardet-5.2.0-py3.11.egg
Adding chardet 5.2.0 to easy-install.pth file
detected new path './ghauri-1.3.5-py3.11.egg'
Installing chardetect script to /usr/local/bin
Using /usr/local/lib/python3.11/dist-packages/chardet-5.2.0-py3.11.egg
Searching for requests==2.32.3
Best match: requests 2.32.3
Adding requests 2.32.3 to easy-install.pth file
Using /usr/local/lib/python3.11/dist-packages
Searching for colorama==0.4.6
Best match: colorama 0.4.6
Adding colorama 0.4.6 to easy-install.pth file
Using /usr/local/lib/python3.11/dist-packages
Searching for tldextract==5.1.2
Best match: tldextract 5.1.2
Processing tldextract-5.1.2-py3.11.egg
Adding tldextract 5.1.2 to easy-install.pth file
Installing tldextract script to /usr/local/bin
Using /usr/local/lib/python3.11/dist-packages/tldextract-5.1.2-py3.11.egg
Searching for certifi==2024.7.4
Best match: certifi 2024.7.4
Processing certifi-2024.7.4-py3.11.egg
Adding certifi 2024.7.4 to easy-install.pth file
Using /usr/local/lib/python3.11/dist-packages/certifi-2024.7.4-py3.11.egg
Searching for urllib3==1.26.18
Best match: urllib3 1.26.18
Adding urllib3 1.26.18 to easy-install.pth file
Using /usr/lib/python3/dist-packages
Searching for idna==3.7
Best match: idna 3.7
Processing idna-3.7-py3.11.egg
Adding idna 3.7 to easy-install.pth file
Using /usr/local/lib/python3.11/dist-packages/idna-3.7-py3.11.egg
Searching for charset-normalizer==3.3.2
Best match: charset-normalizer 3.3.2
Processing charset_normalizer-3.3.2-py3.11-linux-x86_64.egg
Adding charset-normalizer 3.3.2 to easy-install.pth file
Installing normalizer script to /usr/local/bin
Using /usr/local/lib/python3.11/dist-packages/charset_normalizer-3.3.2-py3.11-linux-x86_64.egg
Searching for filelock==3.15.4
Best match: filelock 3.15.4
Processing filelock-3.15.4-py3.11.egg
Adding filelock 3.15.4 to easy-install.pth file
Using /usr/local/lib/python3.11/dist-packages/filelock-3.15.4-py3.11.egg
Searching for requests-file==2.1.0
Best match: requests-file 2.1.0
Processing requests_file-2.1.0-py3.11.egg
Adding requests-file 2.1.0 to easy-install.pth file
Using /usr/local/lib/python3.11/dist-packages/requests_file-2.1.0-py3.11.egg
Finished processing dependencies for ghauri==1.3.5
┌──(ma㉿Windows11)-[~/ghauri]
└─$ ghauri -h
Traceback (most recent call last):
File "/home/ma/ghauri/ghauri/ghauri.py", line 26, in
from ghauri.common.config import conf
File "/home/ma/ghauri/ghauri/ghauri.py", line 26, in
from ghauri.common.config import conf
ModuleNotFoundError: No module named 'ghauri.common'; 'ghauri' is not a package
┌──(ma㉿Windows11)-[~/ghauri]
└─$ ls
build  dist  ghauri  ghauri.egg-info  LICENSE  README.md  requirements.txt  setup.py
┌──(ma㉿Windows11)-[~/ghauri]
└─$ pwd
/home/ma/ghauri
┌──(ma㉿Windows11)-[~/ghauri]
└─$ ls
build  dist  ghauri  ghauri.egg-info  LICENSE  README.md  requirements.txt  setup.py
┌──(ma㉿Windows11)-[~/ghauri]
└─$ sudo python3 -m pip install -e .
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/ratelimit-2.2.1-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/dicttoxml-1.7.16-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/requests_file-2.1.0-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/idna-3.7-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/ghauri-1.3.5-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/tldextract-5.1.2-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/certifi-2024.7.4-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/chardet-5.2.0-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/filelock-3.15.4-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/charset_normalizer-3.3.2-py3.11-linux-x86_64.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
DEPRECATION: Loading egg at /usr/local/lib/python3.11/dist-packages/arjun-2.2.6-py3.11.egg is deprecated. pip 24.3 will enforce this behaviour change. A possible replacement is to use pip for package installation.. Discussion can be found at https://github.com/pypa/pip/issues/12330
Obtaining file:///home/ma/ghauri
Preparing metadata (setup.py) ... done
Requirement already satisfied: tldextract in /usr/local/lib/python3.11/dist-packages/tldextract-5.1.2-py3.11.egg (from ghauri==1.3.5) (5.1.2)
Requirement already satisfied: colorama in /usr/local/lib/python3.11/dist-packages (from ghauri==1.3.5) (0.4.6)
Requirement already satisfied: requests in /usr/local/lib/python3.11/dist-packages (from ghauri==1.3.5) (2.32.3)
Requirement already satisfied: chardet in /usr/local/lib/python3.11/dist-packages/chardet-5.2.0-py3.11.egg (from ghauri==1.3.5) (5.2.0)
Requirement already satisfied: charset-normalizer<4,>=2 in /usr/local/lib/python3.11/dist-packages/charset_normalizer-3.3.2-py3.11-linux-x86_64.egg (from requests->ghauri==1.3.5) (3.3.2)
Requirement already satisfied: idna<4,>=2.5 in /usr/local/lib/python3.11/dist-packages/idna-3.7-py3.11.egg (from requests->ghauri==1.3.5) (3.7)
Requirement already satisfied: urllib3<3,>=1.21.1 in /usr/lib/python3/dist-packages (from requests->ghauri==1.3.5) (1.26.18)
Requirement already satisfied: certifi>=2017.4.17 in /usr/local/lib/python3.11/dist-packages/certifi-2024.7.4-py3.11.egg (from requests->ghauri==1.3.5) (2024.7.4)
Requirement already satisfied: requests-file>=1.4 in /usr/local/lib/python3.11/dist-packages/requests_file-2.1.0-py3.11.egg (from tldextract->ghauri==1.3.5) (2.1.0)
Requirement already satisfied: filelock>=3.0.8 in /usr/local/lib/python3.11/dist-packages/filelock-3.15.4-py3.11.egg (from tldextract->ghauri==1.3.5) (3.15.4)
Installing collected packages: ghauri
Attempting uninstall: ghauri
Found existing installation: ghauri 1.3.5
Uninstalling ghauri-1.3.5:
Successfully uninstalled ghauri-1.3.5
Running setup.py develop for ghauri
Successfully installed ghauri-1.3.5
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
┌──(ma㉿Windows11)-[~/ghauri]
└─$ ls
build  dist  ghauri  ghauri.egg-info  LICENSE  README.md  requirements.txt  setup.py
┌──(ma㉿Windows11)-[~/ghauri]
└─$ pwd
/home/ma/ghauri
┌──(ma㉿Windows11)-[~/ghauri]
└─$ ghauri -h
Traceback (most recent call last):
File "/home/ma/ghauri/ghauri/ghauri.py", line 26, in
from ghauri.common.config import conf
File "/home/ma/ghauri/ghauri/ghauri.py", line 26, in
from ghauri.common.config import conf
ModuleNotFoundError: No module named 'ghauri.common'; 'ghauri' is not a package
┌──(ma㉿Windows11)-[~/ghauri]
└─$

Did you use the following installation guideline or the steps mentioned in the Installation section itself?
https://github.com/r0oth3x49/ghauri/issues/119#issuecomment-1873049386

Yes. I tried all steps. Thanks

You must be using multiple installation of python. Try with admin or root to install. It should fix the issue at least this is what I have faced and fixed this way

I am using SQLMAP and many other Python-coded tools, but I have never seen an error like this one. No problem 😊 I will start using SQLMAP again by adding XOR time-based SQLi payloads in the XML config file. You can close this thread now. I know it won't run now even if I use sudo or root methods, but nothing is working now.


[ALLUXIO-3224] Configurable worker dir permissions

https://alluxio.atlassian.net/browse/ALLUXIO-3224

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20134/
Test PASSed.

@aaudiber Updated, thanks.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20157/Failed Tests: 1org.alluxio:alluxio-tests: 1alluxio.client.cli.fs.command.PinCommandIntegrationTest.setIsPinned
Test FAILed.

Jenkins, test this please.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/20159/Failed Tests: 3org.alluxio:alluxio-tests: 3alluxio.client.rest.FileSystemClientRestApiTest.downloadalluxio.server.configuration.ConfigCheckerIntegrationTest.multiMastersalluxio.server.configuration.ConfigCheckerIntegrationTest.multiWorkers
Test FAILed.


Doesn't work - 403 on oauth with google

Your app is still in test mode and apparently the 100 test users are used up.
See https://www.youtube.com/watch?v=x_NPvk0pk8g for an explanation.

Thanks for filing this issue: I'm going to prepare the YT video in order to apply for google approval, but I've been the only tester so far...
In the meantime I'm adding a disclaimer to the Readme.
If you want I can add you as a tester.
I'd really appreciate it.

Sure, add me as @.*** please.
I did solve my problem using "got your back" script, but I'm happy to try
yours 🙂
Davide Cavestro @.***> schrieb am So. 14. Aug. 2022 um
22:09:

Thanks for filing this issue: I'm going to prepare the YT video in order
to apply for google approval, but I've been the only tester so far...
In the meantime I'm adding a disclaimer to the Readme.
If you want I can add you as a tester.
I'd really appreciate it.
—
Reply to this email directly, view it on GitHub
https://github.com/davidecavestro/gmail-exporter/issues/1#issuecomment-1214440966,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMT4AYT7KJIB3YTCJLKC5ZDVZFG7HANCNFSM56QKAPIQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
TV Noir: Eine Million Clip Views pro Monat
TV Noir Trailer: http://tvnoir.de/trailer
TV Noir
Tex Drieschner
0163 8396628
@.***
Geschäftsadresse
Drieschner Media GmbH
Graefestr. 71 / 10967 Berlin
Geschäftsführung: Tex Drieschner
Ust.-ID DE281524408
HR: 140008 / Amtsgericht Charlottenburg

Sorry I can't see your address, as it gets masked with stars for privacy reasons.
Please reply directly to davide (dot) cavestro (at) gmail (dot) com or write your address using the notation I used (in the hope this way it doesn't get masked)

still in test mode :(


fix(checkout): DATA-7883 bump checkout-sdk-js version

What?
DATA-7883
This PR is trying to fix an issue with missing transactions and products in GA for segment
Testing / Proof
@bigcommerce/checkout

@PascalZajac please close this PR


New CLI extension: Serve Command with Manifest JAR file

Implementing ADR: https://github.com/KonduitAI/konduit-serving/blob/master/ADRs/0006-CI_Launching_vs_Build.md

Looks like the upgraded OSHI version is a problem for the old API... I'm seeing this during tests on command line.
https://gist.github.com/AlexDBlack/3354f3c424b59db7f99bb364229ca148

Changes I've made here:

Make CLI an uber-jar
Add logback dependency to CLI uberjar
Add oshi-core to CLI uberjar
Profile: @Data annotation
Fixed an infinite loop when user calls konduit profile list as the first command - https://gist.github.com/AlexDBlack/983d84862ead34ade15829d86677cb59
Small tweaks to messages
Make konduit-serving-build module a direct dependency of konduit-serving-cli (no reflection, and so we only have to distribute one JAR)

Some identified problems (not yet fixed)
Error with empty profile directory or no profile directory + "konduit serve ..."
https://gist.github.com/AlexDBlack/a4d159787a487d1f26303924a378c465
"konduit profile list" (first run) https://gist.github.com/AlexDBlack/a8b93854391483b9be5c32152f6a0bcb

VRAM is wrong: vRam=4293918720 - it's a 12GB card (reporting just under 4GB)
"No profile with name CUDA exists." (but we're in the process of creating it here?)
Profiles are printed twice

If inference configuration doesn't exist (bad path) - NPE - https://gist.github.com/AlexDBlack/ecba7407fe00305654d8d669fe760de6
If manifest JAR build fails, we get some bad exceptions - https://gist.github.com/AlexDBlack/66ba86245d18bfcc5367df94a6a36729
(the class not found exception part is irrelevant now but other failures could still cause this problem)
"Unable to get default profile" + manifest JAR present via classpath arg but clearly not working
https://gist.github.com/AlexDBlack/db84e256c7f697522a633a3b4ed36fb1
(here's code used to create test file - https://gist.github.com/AlexDBlack/3e6b55f7c60daf225b414e3656fc434a )

Fixed most issues and created new issues for some of them. Oshi hardware gives wrong information. Might be some setting that I don't know about. I've created issue for it here: https://github.com/KonduitAI/konduit-serving/issues/438

Feedback after testing
In help (-h),  should be first in list, <profile_name> should be second
https://gist.github.com/AlexDBlack/c2797c710dd3d75f2215fb490eb0a981
unknown subcommands give ugly exception
https://gist.github.com/AlexDBlack/2e9dbef7bfdec1b7d0da4e3c8b035e39
(this should have been --help or -h)
unknown server type gives ugly exception
https://gist.github.com/AlexDBlack/8a16e8cf183482c7683ab3e06b276170
edit doesn't seem to work, at least for this case I tested:
https://gist.github.com/AlexDBlack/5ca9655c7ff86279f1a9638f9755ba83
not exactly a new thing here - but we should handle missing PID files more gracefully: https://gist.github.com/AlexDBlack/b74ea52ae491ef00a61f08b78a5b7e05
Now that the build tool is no longer an uberjar, we probably need a top-level 'build' command that calls the build CLI, for creating uberjars, docker images, etc
i.e., konduit build -p myconfig.json -o WINDOWS etc just passes the args to ai.konduit.serving.build.cli.BuildCLI
As for the CUDA NoAvailableBackendException issue - the backend (and classifier JAR) is definitely included in the manifest, so I'm not sure why we're getting that :(
I'll keep looking into it.


Add more data to response message

It is unclear that the room message is a translation and between which languages. There should be some more information to make this clearer.

Maybe a change in the command response structure is in order.


Issue with subtle dependency

stdout : error: failed to select a version for subtle.
... required by package rustls v0.22.0
... which satisfies dependency rustls = "^0.22" of package tokio-rustls v0.25.0
... which satisfies dependency tokio-rustls = "^0.25" of package jsonrpsee-client-transport v0.21.0
... which satisfies dependency jsonrpsee-client-transport = "^0.21.0" of package jsonrpsee-ws-client v0.21.0
... which satisfies dependency jsonrpsee-ws-client = "^0.21.0" of package jsonrpsee v0.21.0
... which satisfies dependency jsonrpsee = "^0.21.0" (locked to 0.21.0) of package prog v0.1.0  versions that meet the requirements ^2.5.0` are: 2.5.0
all possible versions conflict with previously selected packages.
previously selected package subtle v2.4.1
... which satisfies dependency subtle = "^2.2.1" (locked to 2.4.1) of package curve25519-dalek v3.2.1 (https://github.com/solana-labs/curve25519-dalek.git?rev=c14774464c4d38de553c6ef2f48a10982c1b4801#c1477446)
... which satisfies dependency curve25519-dalek = "^3.2.1" (locked to 3.2.1) of package solana-program v1.18.9
... which satisfies dependency solana-program = "^1.18.9" (locked to 1.18.9) of package `prog v0.1.0
failed to select a version for subtle which could resolve this conflict

Hey! Google brought me here:)
I figured out this problem by tracking down rustls deps in solana and reqwest version:
https://github.com/solana-labs/solana/blob/27eff8408b7223bb3c4ab70523f8a8dca3ca6645/Cargo.toml#L289
https://crates.io/crates/reqwest/0.11.27/dependencies
This one worked for me:
reqwest = { version = "0.11.27", default-features = false, features = ["json", "rustls-tls"] }
It's important to disable default-features, otherwise reqwest still linked to openssl.
With rustls app can be build from scratch docker image, without openssl dependency hell:
FROM lukemathwalker/cargo-chef:latest-rust-alpine as chef
WORKDIR /app

FROM chef AS planner
COPY ./Cargo.toml ./Cargo.lock ./
COPY ./src ./src
RUN cargo chef prepare

FROM chef AS builder
COPY --from=planner /app/recipe.json .
RUN cargo chef cook --release
COPY . .
RUN cargo build --release
RUN cp ./target/release/pools ./app
RUN ls -lah ./app

FROM scratch AS runtime
WORKDIR /
ENV RUST_LOG=info
COPY --from=builder /app/app /
ENTRYPOINT ["/app"]

Just 80mb image.

Addition of tokio-tungstenite forced me to patch deps, at least zeroize to 1.6.0
Precise versions + patched deps:
reqwest = { version = "0.11.27", default-features = false, features = ["json", "rustls-tls"] }
tokio-tungstenite = { version = "0.20.1", features = ["rustls"] }

[patch.crates-io]
curve25519-dalek = { git = 'https://github.com/ivs/curve25519-dalek', branch='rustls-dep-hell' }
aes-gcm-siv = { git = 'https://github.com/ivs/AEADs', branch='rustls-dep-hell' }

Also solana-zk-token-sdk should be explicitly set to solana-client/sdk version.
And solana-zk-token-sdk is exactly the root cause of rustls dephell, it would be nice to update versions:
aes-gcm-siv to have subtle >=2.5.0 and zeroize >=1.6.0
curve25519-dalek to have zeroize >=1.6.0
It will unlock rustls 22.1.* deps, and it looks like zeroize >= 1.7.0 will help with 22.2.*.

reqwest

Hi @ivs tried you solution but it didn't work for me.
Odd this, regular cargo build or even cargo tauri dev works fine.
But cargo tauri ios dev fails with the following:
error: failed to select a version for `subtle`.
    ... required by package `rustls v0.22.2`
    ... which satisfies dependency `rustls = "^0.22.2"` of package `reqwest v0.12.4`
    ... which satisfies dependency `reqwest = "^0.12"` (locked to 0.12.4) of package `tauri v2.0.0-beta.23`
    ... which satisfies dependency `tauri = "^2.0.0-beta"` (locked to 2.0.0-beta.23) of package `blockmesh_tauri v0.0.108 (/Users/ohaddahan/RustroverProjects/block-mesh-monorepo/libs/blockmesh-bin/src-tauri)`
versions that meet the requirements `^2.5.0` are: 2.6.1, 2.5.0

all possible versions conflict with previously selected packages.

  previously selected package `subtle v2.4.1`
    ... which satisfies dependency `subtle = "^2.4"` (locked to 2.4.1) of package `digest v0.10.7`
    ... which satisfies dependency `digest = "^0.10.7"` (locked to 0.10.7) of package `solana-sdk v1.18.19`
    ... which satisfies dependency `solana-sdk = "^1.18.2"` (locked to 1.18.19) of package `blockmesh_tauri v0.0.108 (/Users/ohaddahan/RustroverProjects/block-mesh-monorepo/libs/blockmesh-bin/src-tauri)`

It's on this branch https://github.com/block-mesh/block-mesh-monorepo/pull/289 , I'm willing to put a $100 bounty to resolve this.

reqwest

Hi @ivs tried you solution but it didn't work for me. Odd this, regular cargo build or even cargo tauri dev works fine. But cargo tauri ios dev fails with the following:
error: failed to select a version for `subtle`.
    ... required by package `rustls v0.22.2`
    ... which satisfies dependency `rustls = "^0.22.2"` of package `reqwest v0.12.4`
    ... which satisfies dependency `reqwest = "^0.12"` (locked to 0.12.4) of package `tauri v2.0.0-beta.23`
    ... which satisfies dependency `tauri = "^2.0.0-beta"` (locked to 2.0.0-beta.23) of package `blockmesh_tauri v0.0.108 (/Users/ohaddahan/RustroverProjects/block-mesh-monorepo/libs/blockmesh-bin/src-tauri)`
versions that meet the requirements `^2.5.0` are: 2.6.1, 2.5.0

all possible versions conflict with previously selected packages.

  previously selected package `subtle v2.4.1`
    ... which satisfies dependency `subtle = "^2.4"` (locked to 2.4.1) of package `digest v0.10.7`
    ... which satisfies dependency `digest = "^0.10.7"` (locked to 0.10.7) of package `solana-sdk v1.18.19`
    ... which satisfies dependency `solana-sdk = "^1.18.2"` (locked to 1.18.19) of package `blockmesh_tauri v0.0.108 (/Users/ohaddahan/RustroverProjects/block-mesh-monorepo/libs/blockmesh-bin/src-tauri)`

It's on this branch block-mesh/block-mesh-monorepo#289 , I'm willing to put a $100 bounty to resolve this.

@ohaddahan in your recent commit I see you have figured it out? I did the same, just fork a repo and update deps there, then last solana-sdk conflicted with reqwest itself, but I just froze reqwest version. Almost always it works fine, I think only for old base64 lib I have patched raydium program to switch to a newer api. BTW why are you on 1.8.* version? 1.7 is considered to be stable, 1.8 has market stable just two days ago.

Can you ping me, you have no contact details here.
See my profile info for contact info.
Would love to resolve this and pay the reward I promised.

reqwest

Hi @ivs tried you solution but it didn't work for me. Odd this, regular cargo build or even cargo tauri dev works fine. But cargo tauri ios dev fails with the following:
error: failed to select a version for `subtle`.
    ... required by package `rustls v0.22.2`
    ... which satisfies dependency `rustls = "^0.22.2"` of package `reqwest v0.12.4`
    ... which satisfies dependency `reqwest = "^0.12"` (locked to 0.12.4) of package `tauri v2.0.0-beta.23`
    ... which satisfies dependency `tauri = "^2.0.0-beta"` (locked to 2.0.0-beta.23) of package `blockmesh_tauri v0.0.108 (/Users/ohaddahan/RustroverProjects/block-mesh-monorepo/libs/blockmesh-bin/src-tauri)`
versions that meet the requirements `^2.5.0` are: 2.6.1, 2.5.0

all possible versions conflict with previously selected packages.

  previously selected package `subtle v2.4.1`
    ... which satisfies dependency `subtle = "^2.4"` (locked to 2.4.1) of package `digest v0.10.7`
    ... which satisfies dependency `digest = "^0.10.7"` (locked to 0.10.7) of package `solana-sdk v1.18.19`
    ... which satisfies dependency `solana-sdk = "^1.18.2"` (locked to 1.18.19) of package `blockmesh_tauri v0.0.108 (/Users/ohaddahan/RustroverProjects/block-mesh-monorepo/libs/blockmesh-bin/src-tauri)`

It's on this branch block-mesh/block-mesh-monorepo#289 , I'm willing to put a $100 bounty to resolve this.

@ohaddahan in your recent commit I see you have figured it out? I did the same, just fork a repo and update deps there, then last solana-sdk conflicted with reqwest itself, but I just froze reqwest version. Almost always it works fine, I think only for old base64 lib I have patched raydium program to switch to a newer api. BTW why are you on 1.8.* version? 1.7 is considered to be stable, 1.8 has market stable just two days ago.

Can you specify with which exact changes it worked for you?
Also can skip cargo tauri io dev if you just add rustls to tauri features, then cargo build will have the same failure.


Add inline variable support (external linkage for const vars)

Can you share the motivation for this change?

Because global constants have internal linkage, each .cpp file gets an independent version of the global variable. Using inline variables solves this problem by using external linkage for such variables. This ensures that only one instance of the variable exists in all files in which it is included.

Sure - however, these are numeric constants; clang doesn't emit any symbols here, and gcc doesn't emit any symbols with -O1 or higher. This would be different if the address of the variables is taken, but that should be highly unusual. So I am curious if this is motivated by a specific problem, or is more of a general cleanup.

It's code cleanup.


For iPad, It does not trigger $(element).lazyload()

I have this page https://mopixie.com/t1.html,
In Ipad, it does not load images when scrolling the page.
It triggers for once and shows images which are initially placed on view port.
Does not trigger event when scroll down !!
Any suggestions.

Fixed it, for touch screens, scroll event did trick to me.
$(window).scroll(function() {
$.lazyload.check();
});
Here's the working page, https://www.mopixie.com/mobile-games-2/pocahontas-slots/


[RESTEASY-3071] If the ServletOutputStream is not ready after write i…

…s complete, we need to queue an operation to complete the future when it can be.
https://issues.redhat.com/browse/RESTEASY-3071
Signed-off-by: James R. Perkins<EMAIL_ADDRESS>@dnagarajan89 what do you think of an approach like this as a fix for #304? I ran your reproducer 30 times in a loop and it passed.

@jamezp this approach looks fine to me, but my concern here is applicable here too. But I don't know that completion of the future in order the data is written will have an impact or not. You know better on this. Just want to bring this to your attention.

@jamezp this approach looks fine to me, but my concern here is applicable here too. But I don't know that completion of the future in order the data is written will have an impact or not. You know better on this. Just want to bring this to your attention.

Yes. I thought about the order issue as well, which I do think could be an issue. This is where I keep coming back to where we may need to re-write it in general. It's just a bummer all the types are public so we have to keep compatibility for these types too.

@dnagarajan89 I think I solved the ordering issue by using an id. This seems to be working for me locally, but if you could give it a test to make sure it works for you that would be great.

@dnagarajan89 I think I solved the ordering issue by using an id. This seems to be working for me locally, but if you could give it a test to make sure it works for you that would be great.

Thanks @jamezp. Will check and get back.

Awesome thanks @dnagarajan89. If this works for then I can do a release as I need a new 4.7 release anyway.

@jamezp I have verified this fix and it works for all my scenarios. If we can get a new patch version of 4.7 with this fix, it would be great. Thanks!.

Also I think the test that reproduces this problem should go somewhere into the resteasy code base.

Also I think the test that reproduces this problem should go somewhere into the resteasy code base.

I'm not sure where the test would live is the problem. I don't object to introducing tests in other containers. However, we'd want a new maybe servlet only testsuite where we could add these tests and containers.


Strange PEM routines error

First of all big thanks for abstracting this into a separate package. This is probably unrelated to the library itself, but maybe you will have answer for this. Fighting to verify paddle webhook for some time and no luck. Both with my own implementation and your library I get this error:
Error: error:0909006C:PEM routines:get_name:no start line
    at Verify.verify (internal/crypto/sig.js:183:24)
    at exports.verifyPaddleWebhook (/Users/d-ivashchuk/projects/twitastic/twitastic-backend/node_modules/verify-paddle-webhook/index.js:43:25)
    at /Users/d-ivashchuk/projects/twitastic/twitastic-backend/src/index.js:25:3
    at Layer.handle [as handle_request] (/Users/d-ivashchuk/projects/twitastic/twitastic-backend/node_modules/express/lib/router/layer.js:95:5)
    at next (/Users/d-ivashchuk/projects/twitastic/twitastic-backend/node_modules/express/lib/router/route.js:137:13)
    at Route.dispatch (/Users/d-ivashchuk/projects/twitastic/twitastic-backend/node_modules/express/lib/router/route.js:112:3)
    at Layer.handle [as handle_request] (/Users/d-ivashchuk/projects/twitastic/twitastic-backend/node_modules/express/lib/router/layer.js:95:5)
    at /Users/d-ivashchuk/projects/twitastic/twitastic-backend/node_modules/express/lib/router/index.js:281:22
    at Function.process_params (/Users/d-ivashchuk/projects/twitastic/twitastic-backend/node_modules/express/lib/router/index.js:335:12)
    at next (/Users/d-ivashchuk/projects/twitastic/twitastic-backend/node_modules/express/lib/router/index.js:275:10)
    at /Users/d-ivashchuk/projects/twitastic/twitastic-backend/node_modules/body-parser/lib/read.js:130:5
    at invokeCallback (/Users/d-ivashchuk/projects/twitastic/twitastic-backend/node_modules/raw-body/index.js:224:16)
    at done (/Users/d-ivashchuk/projects/twitastic/twitastic-backend/node_modules/raw-body/index.js:213:7)
    at IncomingMessage.onEnd (/Users/d-ivashchuk/projects/twitastic/twitastic-backend/node_modules/raw-body/index.js:273:7)
    at IncomingMessage.emit (events.js:327:22)
    at endReadableNT (_stream_readable.js:1221:12) {
  library: 'PEM routines',
  function: 'get_name',
  reason: 'no start line',
  code: 'ERR_OSSL_PEM_NO_START_LINE'
}

I would very much appreciate any directions or help, as I am really stuck with this 😬 Thanks a lot!

Most likely it's an issue with your public key.
Normally that error might indicate that your public key does not have the PEM header line: -----BEGIN PUBLIC KEY----- or the newline after the header might be missing.

@d-ivashchuk Any luck getting to the bottom of this?  If there's nothing else I'll close this ticket (as it's seemingly not an issue specific to this lib).

I've fixed it not so long ago. The issue was with how my prettier formatted the code - if anyone will see this error. Leaving the start and end parts + making sure it's stored correctly fixed the issue! Thanks a lot 👍🏼


"Marker Cluster" not functioning correctly with "Advanced Marker"

Is this a regression?

[ ] Yes, this behavior used to work in the previous version

The previous version in which this bug was not present was
No response
Description
Issue

"Marker Cluster" not functioning correctly with "Advanced Marker"
mapMouseout & mapMouseover events not working with map-advanced-marker

Link to runnable example
https://codesandbox.io/p/devbox/shy-platform-2h2y6y?file=%2Fsrc%2Fapp%2Fservice%2Fgoogle-maps.service.ts%3A19%2C16-19%2C28
Note
Already discussed this issue here.

Reproduction
https://codesandbox.io/p/devbox/shy-platform-2h2y6y?file=%2Fsrc%2Fapp%2Fservice%2Fgoogle-maps.service.ts%3A19%2C16-19%2C28
Expected Behavior
Marker Cluster should be visible without any error.

Actual Behavior
Marker Cluster not visible with Advanced marker

Environment

Angular:^17.3.0
Browser(s): Chrome
Operating System (e.g. Windows, macOS, Ubuntu): Windows 11

The current clusterer doesn't support advanced markers. You can follow https://github.com/angular/components/issues/23695 for the new clusterer.


Update image generation README

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jayesh-srivastava
To complete the pull request process, please assign jzhoucliqr
You can assign the PR to them by writing /assign @jzhoucliqr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jayesh-srivastava, sadysnaat
To complete the pull request process, please assign jzhoucliqr
You can assign the PR to them by writing /assign @jzhoucliqr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jayesh-srivastava
To complete the pull request process, please assign jzhoucliqr
You can assign the PR to them by writing /assign @jzhoucliqr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jayesh-srivastava
To complete the pull request process, please assign jzhoucliqr
You can assign the PR to them by writing /assign @jzhoucliqr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: jayesh-srivastava, sadysnaat
To complete the pull request process, please assign jzhoucliqr
You can assign the PR to them by writing /assign @jzhoucliqr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@jayesh-srivastava: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

cluster-api-provider-maas_build
342c07c963af863d89ac01e41c91e22a5879d2d8
link
/test cluster-api-provider-maas_build

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Ability to hover over a link and show the embed information?

A nice feature to prevent streamers from getting trolled, etc.
I would be nice to hover over a link and show the embed image, for example like you hover over a YouTube video link an a embed shows up with the name, channel name and thumbnail show.

Duplicate of another issue.


How to use multiple inputs in a Keras model with Talos?

There is ambiguity in using Talos for multiple inputs, which one is correct?

https://autonomio.github.io/talos/#/Examples_Multiple_Inputs
https://autonomio.github.io/talos/#/Scan?id=scan-arguments (Models with multiple inputs or outputs (list of arrays))

Also, why do i get the following error after running scan_object:
init() takes at least 6 arguments (7 given)
scan_object = talos.Scan(x = [x_train[:, 0], x_train[:, 1]],                          y = tr_y,                          x_val = [x_val[:, 0], x_val[:, 1]],                          y_val = val_y,                          params = p,                          model = siamese_model)

What do you mean by ambiguity? The docs provide a self-contained example for multiple input models.
Try the below (you are missing experiment_name):
scan_object = talos.Scan(

    x=[x_train[:, 0], x_train[:, 1]],
    y=tr_y,
    x_val=[x_val[:, 0], x_val[:, 1]],
    y_val=val_y,
    params=p,
    model=siamese_model,
    experiment_name='my_experiment'

)

Many thanks for the prompt reply.
According to '1', the multi-input part is handled in Scan():
out = model.fit(x=x_train,
                    y=y_train,
                    validation_data=[x_val, y_val],
                    epochs=150,
                    batch_size=params['batch_size'],
                    verbose=0)

scan_object = talos.Scan(x=[x_train, x_train],
                         y=y_train,
                         x_val=[x_val, x_val],
                         y_val=y_val,
                         params=p,
                         model=iris_multi)

but according to '2', the multi-input part is handled in Fit():
out = model.fit(x=[x_train_a, x_train_b],
                y=y_train,
                validation_data=[[x_val_a, x_val_b], y_val])

It's better to follow 1 because that will be consistent across all kinds of use-cases and also because it is the actual specific example targeting multi-input model

Many thanks for your help. I got my code working.


Show twitter explore tab

Can you add the twitter explore tab like it is show in the twitter phone application.

What is the Explore tab? Can you share a screenshot?

This is the explore tab, it is only available in twitter app for android or IOS, and also available from the site mobile.twitter.com .
In this tab we can see trends, also some topics that are interesting for us.


Question about deploying on Github project pages

I'm not experienced at all with Ruby and I've looked around the web for an answer so please excuse me if I'm not using the right channel, I saw that spectrum is kind of dead. This is not a technical question so I removed the template.
I love the simplicity of slate but I would prefer to use it for project pages served from the docs folder, not from a branch. Which would be the best way to achieve this?
I'm trying to decide between:

Creating a slate folder somewhere in my node.js project and setting the deploy branch to master and directory to docs within deploy.sh.
Adding slate directly into docs which sounds more semantically correct, but this way the build has to be in the same folder to be properly displayed.
Use the branch and not the docs directory to serve the documents but in this case I would still need to put the source somewhere.

So that's my story, what's your suggestion?

Hi! As you can see from two weeks of silence, GitHub issues is not exactly the most effective tool for asking questions either, so Spectrum may be better in the future :) You may have already found it, but there may be some Middleman config that could help? https://middlemanapp.com/advanced/configuration


web/feature/user/connect-account-editUserForm-pages

For users being able to go jump from my account to edit my account
we need to add Link to a pencil icon that redirects users to /user/edit route

I can try ?


AnnDatasetFromAnnData deletes data

Thank you for pointing this out. We will address this ASAP!

For now you can use adata.copy() as the input to our class.

@aopisco we just release 0.6.1 on pip, which fixes this issue


Windows Capabilities in appxmanifest not properly used by building .msix [MAUI]

Describe the bug
Description
Originally from: https://github.com/dotnet/maui/issues/10287
When the Capability runFullTrust is replaced with something else (for instance removableStorage) and the msix file is build, the following is shown during the installation:

(The msix file can be found here MauiIssue-WindowsCapabilities Action Artefact)
As you see, the runFullTrust was not removed from the msix which is strange.
Link to public reproduction project repository
https://github.com/Tardigrade42/MauiIssue-WindowsCapabilities
Version with bug
6.0.486 (current)
Steps to reproduce the bug

Create a Maui-App from the template
Go to "Platforms > Windows > Package.appxmanifest"
Change:

<Capabilities>
   <rescap:Capability Name="runFullTrust" />
</Capabilities>

to
<Capabilities>
   <uap:Capability Name="removableStorage" />
</Capabilities>

Build app with dotnet publish
Open the MSIX file on your computer

Expected behavior
runFullTrust was not removed from the msix
Screenshots
No response
NuGet package version
WinUI 3 - Windows App SDK 1.1.5
Windows app type

[ ] UWP
[ ] Win32

Device form factor
Desktop
Windows version
Windows 10 (21H2): Build 19044
Additional context
No response

Tracked internally as http://aka.ms/41603067

Hi,
since I am waiting for a solution of this issue for a while now, I wanted to ask if there is progress with this case or if there is a workaround?

@Tardigrade42 Unfortunately there is no workaround. However, a fix will be included in the 1.3 release and we are aiming to bring it into an upcoming 1.2 servicing release as well.

Thank you very much :)
I have no idea how often you are building releases. When will this release be available on Visual Studio?

@Tardigrade42 We're aiming to include this in the January 2023 1.2 servicing update.

That sounds great🙂. Thank you!

Windows App SDK 1.2.3 shipped today with the fix for this issue.


Can't Add more one light entity in the same plants

Checklist:

[Home Assistant 2023.8.4
Supervisor 2023.08.1
Frontend 20230802.1 - latest ] I updated to the latest version available
[ already try] I cleared the cache of my browser

Release with the issue:
Relase Home Assistant: Home Assistant 2023.8.4
Supervisor 2023.08.1
Frontend 20230802.1 - latest
Relase floor3d-card (aka Your Home Digital Twin) v. 1.5.3
Last working release (if known):
Browser and Operating System:
Windows 11 Google Chrome

Description of problem:
I obtain the error down when i try to add more than 2 entities light (all work correctly if i add only one light)
Logger: frontend.js.latest.202308021
Source: components/system_log/init.py:270
First occurred: 4 settembre 2023 alle ore 01:00:14 (55 occurrences)
Last logged: 17:37:17
https://<IP_ADDRESS>:8123/local/community/floor3d-card/floor3d-card.js:2356:4517 Uncaught Error
https://<IP_ADDRESS>:8123/local/community/floor3d-card/floor3d-card.js:2356:4523 Uncaught Error

Javascript errors shown in the web inspector (if applicable):
Finished with errors: check the console log
in the console log under system/registry i find this error:
https://<IP_ADDRESS>:8123/local/community/floor3d-card/floor3d-card.js:2356:4523 Uncaught Error

Additional information:

Hello try to provide the Yaml card configuration code.

Hello, first of all, If you havé loaded your own model you should remove the object groups, because they are referring to the sample model. Second, your second light has {} after the light attribute, this is not correct.
Let me know if it helps.

Without a feedback from the user in more than one month, I close the ticket.


Updating the pricing tier

Updating the pricing tier to reflect the new pricing tier options and removing the legacy tiers. Based on the feedback from customer on this GitHub thread https://github.com/MicrosoftDocs/azure-docs/issues/49237. Requesting you to review the PR.

@BharathNimmala-MSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Determine minimal HA version

Currently hacs.json specifies an arbitrary minimum HA version. Test to determine what versions integration is currently compatible with, and possibly implement workarounds as needed to make it compatible with at least 2023.6.

Modified to be compatible with HA versions as early as 2023.7.0.


Set Dummy Version in User Agent

This replaces the version in User Agent with a dummy version within the functions
Works on issue #6474

Please squash commits

Please squash commits

done


v1.1.0 rollup into master

@rhinof please fix conflicts 👍

conflicts will be resolved in specific merge branch


Document essential security milestones vs PWS

Document all PWS tasks current status and justifications.
@scott-aquia  @devopsmatt

The link to the document is above in devopsmatt's comment: it contains a list of 26 contractual line items and describes how devsecops is meeting those requirements


Multi threading

Hi Jacco, thank you for this awesome library :) This PR removes the dependency for the OpenMP #49. In this version, each thread fetches the next available tile and renders it.

Thanks for that contibution! Merged. :)


[FeatureRequest] Could we have some way to know how much time passed?

Thanks for this nice little piece of code :)
My use-case is this: I have an animation coroutine that has different stages, like it plays one animation after another. One of them is a simple simple LERPed rotation. However, that LERP function needs the delta time of the update. Is there an easy way to achieve what I want, that I just haven't figured out? If not, maybe you could add a small function like
YieldDeltaFunc(deltaFunc func(deltaTime float64) bool) error

No problem, thanks for using it~
If I'm understanding your request, you can just use whatever delta time-measuring functions you normally have at your disposal (a global delta time variable or function, calculating 1/TPS for Ebitengine, etc). Yielding in a coroutine pauses execution for some amount of time, but that doesn't change the delta value between game frames.


vendor: netlink and netns: Update to 1890b34 and 2c9454e

This commit updates github.com/vishvananda/netlink and
github.com/vishvananda/netns to commits 1890b34 and 2c9454e,
respectively.
BAT tests and networking tests (verify.sh) pass on Single VM
with this commit applied.
Signed-off-by: Mark Ryan<EMAIL_ADDRESS>

@mcastelino I didn't see any problems with the update but you might want to check quickly yourself before we merge.

Coverage increased (+0.01%) to 66.917% when pulling fa150f49a7bf3713e799ea7dbaa0b96cccdb5003 on markdryan:update-netlink into 608387ce6805792ed2fbca26037a207df45ba1c6 on 01org:master.

LGTM. I verified that my unit tests also work without any issues.


[PSM Interop] Legacy test builds always pull the driver from master (v1.53.x backport)

Backport of #33699 to v1.53.x.
Similar to https://github.com/grpc/grpc-java/pull/8982.
All other languages already to this.
Needed for easier deployment of https://github.com/grpc/grpc/pull/33685.
ref b/274944592

[ ] grpc/core/v1.53.x/branch/linux/grpc_xds_v3
[ ] grpc/core/v1.53.x/branch/linux/grpc_xds_v3_python


Problem with the Hello World sample code

I've had a problem with the code snippet in the "The Hello World of IntelliTest" section:
If instead of "[TestClass] public partial class HelloWorldTest" I use "[PexClass] public partial class HelloWorldTest" the test run in correct way.

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

ID: afd1b2f6-e89f-ecdb-0060-de0c7e43d110
Version Independent ID: 9195e48c-d85e-d940-519a-c3642d17aa33
Content: Overview - Visual Studio
Content Source: docs/test/intellitest-manual/introduction.md
Product: visual-studio-windows
Technology: vs-ide-test
GitHub Login: @jillre
Microsoft Alias: jillfra

Sorry, you are right:

Create a new Unit Test Project (.NET Framework) with VS 2017
Add Microsoft.Pex.Framework to references
Replace the content of the test class with the code snippet from the "The Hello World of IntelliTest" section
Delete Microsoft.VisualStudio.TestPlatform.TestFramework and Microsoft.VisualStudio.TestPlatform.TestFramework.Extensions references
Add Microsoft.VisualStudio.QualityTools.UnitTestFramework reference to the project

After that the tests are generated successfully.

@csolizoltan Thank you for the feedback and for providing the work-around.
A note will be added to the documentation.


Remove data for completed applications

When an application process is completed i.e. funds have been disbursed to the MSME by the FI, I want the data for the application to only be viewable for one week after the completion date-time, so that this personal data is not stored by the OCP long term.

We still want to keep the metadata that is required for the FI and OCP dashboard, but this should not mean we need to store personal data

https://www.figma.com/file/mQqkGtTfNEBdfk4QdfNYIO/OCP-Data-Registry-Design?type=design&node-id=443-3219&t=ZGzh5x7zMAwvmP8g-4

Some notes on this:

All the uploaded documents by the MSME must be deleted as part of this
We don't want to delete the application information or the MSME row (so we can calculate if the same MSME has been credited multiple times using Credere)

So, the proposal is to:

Add a hashed id column in the MSME table using the MSME identifier
Add a hashed id column in the application table using the MSME identifier and the award identifier
When deleting personal information:

Delete all the uploaded documents
Remove the legal identifier and name from the MSME table
Delete all the awards (and historical contracts) from the award table. Note that the award_id foreign key in the application table must be nullable.

When we check for a new awarded MSME:

Use the same hashing algorithm to check if this MSME already has a row in the MSME table, if so, then refill the name and identifier columns and
To avoid emailing the same MSME for the same award, use the same hashing algorithm with the MSME identifier and award identifier to check if that already exists in the application table. If it exists, then ignore the award as it has been processed already, if not, proceed as usual.

cc @jpmckinney

For context, the most sensitive private information is the documents, as these might contain financial information, personal data, etc. – and they are not generally available. Thankfully, deleting these is easy.
Names, identifiers, emails, etc. are less sensitive as they are generally available (unless they were manually entered by FIs or OCP).
If the proposal above will take long to implement, then we can learn more from the lawyers to see if it can be relaxed. For now, it follows our original requirements.

Closing in favor of #141


Error: "The system cannot find the file specified" with Unity

I am trying to use this inside of Unity, but when testing the samples engine.GetMetaData(...) or engine.Convert(...) I get this error:
Win32Exception: ApplicationName='/MediaToolkit/ffmpeg.exe', CommandLine='-nostdin -y -loglevel info -i "C:\Path\Clip_1_.mp4" ', CurrentDirectory='', Native error= The system cannot find the file specified.
I can verify that the file does exist in the specified folder.
Any help would be appreciated.

Solution: Need to define the path of ffmpeg in the Engine constructor:
using (var engine = new Engine(@"C:\MediaToolkit\ffmpeg.exe"))
{
engine.GetMetadata(inputFile);
}


Javascript Intellisense not working in VS Code

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.82.2
OS Version: Windows_NT x64 10.0.22621

Commit: abd2f3db4bdb28f9e95536dfa84d8479f1eb312d
Date: 2023-09-14T05:55:25.390Z
Electron: 25.8.1
ElectronBuildId: 23779380
Chromium: 114.0.5735.289
Node.js: 18.15.0
V8: <IP_ADDRESS>-electron.0
Features like code suggestion and error highlighting is not working for Javascript in my Visual Studio Code. No javascript emmet is being shown in the suggestions. It seems like Javascript intellisense is not working.
The code is running completely fine but features like code suggestion or completion , error highlighting , etc is not working.
Please help ->

@Bhavik47 Those features don't come built-in. You have to install the appropriate extension.

https://github.com/microsoft/vscode/assets/116140035/848ab754-fdb8-405d-bd73-1a07c0c55b2b
VS Code is showing no suggestions or errors even with all the javascript extensions. Here's the problem as you can see its not recommending document or any functions in document like getElementById() or getElementsByClassName()  even after writing document. Nor is it recommending objects like console.

Those features don't come built-in. You have to install the appropriate extension.

@codespearhead  This is wrong. These features are built in

@Bhavik47 Did you disable the builtin Javascript support. In the extensions view, search for @builtin javascript and confirm that the TypeScript and JavaScript Language Features extension is enabled

Thankyou, It worked now
TypeScript and JavaScript Language Features were disabled


Error Handling if Enter is pressed when prompted for Hostname

The installer proceeds with NULL value for hostname if user presses enter (without entering any value) when asked to "Enter Hostname".
System should not proceed or should Ideally pick up the -H parameter that is provided when docker container is created:
docker run -it -p=110:110 -p=25:25 -p=995:995 -p=8080:80 -p=44380:443  -p=587:587 -p=993:993 -p=143:143 -p=465:465 -h "mail.example.com" --name="easymail" -v /etc/ssl/certs/:/etc/ssl/certs/ ubuntu:16.04 /bin/sh -c "if [ -f /run.sh ]; then bash /run.sh; fi; exec /bin/bash"

What / where is the -h paramter used for ?

Can you propose a solution?

lets start with a set -e
and simple traps...
if [[ -n "$input" ]] ; then
  echo "error happened with input"
  exit 1
fi

Let me know if this will work?

And I'd presume, that since we're heading with docker, all inputs should be captured BEFORE SCRIPT START...

This should be applicable to post_install.sh too.
The current command for running is
docker run -itd  -p=110:110 -p=25:25 -p=995:995 -p=80:80 -p=443:443 -p=587:587 -p=993:993 -p=143:143 -p=465:465 -h "test.example.com" --name="easymail" XXXXXX /bin/sh -c "bash /opt/easymail/post_install.sh test.example.com; exec /bin/bash"

We can make that to
docker run -itd  -p=110:110 -p=25:25 -p=995:995 -p=80:80 -p=443:443 -p=587:587 -p=993:993 -p=143:143 -p=465:465 -h "test.example.com" --name="easymail" XXXXXX /bin/sh -c "bash /opt/easymail/post_install.sh; exec /bin/bash"

And after that inside in post_install.sh we can take the "test.example.com" from the hostname.
Is that your proposal?

yes that is...

That's great. I totally agree with you. Can you provide a Pull request for this changes?

@cruisemaniac the issue is resolved on v1.0.8, closing the ticket.


Support for staking contracts

Users would like to be able to generate keys for their staking contracts on their A1CN and then be able to submit the go online transactions by having the relevant details exposed to them.

Pretty please 🥺

Already has it.


In page.emulate(option), option. hasTouch not worker

Steps to reproduce
Tell us about your environment:

Puppeteer version:0.12.0
Platform / OS version:mac 10.11.6
URLs (if applicable): any mobile page

What steps will reproduce the problem?
Please include code that reproduces the issue.

prepare the demo like beblow:

const puppeteer = require('puppeteer');
const devices = require('puppeteer/DeviceDescriptors');
const browser = await puppeteer.launch({headless: false});
  const page = await browser.newPage();
  await page.emulate(devices['iPad landscape']);
  await page.goto(REDIRECT_URL);

interact with the page in the chrome

What is the expected result?
touch operations  work
What happens instead?
touch operations don't work

Emulating a touch device with Puppeteer sets up the page so that something like modernizr will detect touch support. It doesn't convert mouse clicks into touch events. You can use page.touchscreen to send automated taps into the page.

const devtoolsProtocolClient = await page.target().createCDPSession();
await devtoolsProtocolClient.send("Emulation.setEmitTouchEventsForMouse", { enabled: true });

@actionnick it work fine for me,thanks


anyhow-1.0.71 does not compile on stable rust

Hello could not find an issue about this
error[E0554]: `#![feature]` may not be used on the stable release channel
   --> /home/redacted/.cargo/registry/src/github.com-1ecc6299db9ec823/anyhow-1.0.71/src/lib.rs:214:32
    |
214 | #![cfg_attr(backtrace, feature(error_generic_member_access, provide_any))]
    |                                ^^^^^^^^^^^^^^^^^^^^^^^^^^^

error[E0554]: `#![feature]` may not be used on the stable release channel
   --> /home/redacted/.cargo/registry/src/github.com-1ecc6299db9ec823/anyhow-1.0.71/src/lib.rs:214:61
    |
214 | #![cfg_attr(backtrace, feature(error_generic_member_access, provide_any))]
    |                                                             ^^^^^^^^^^^

rustc --version
rustc 1.69.0 (84c898d65 2023-04-16)
Edit: this happens while trying to run some tests on code using anyhow

https://github.com/dtolnay/anyhow/issues/289 via https://github.com/dtolnay/anyhow/issues?q=error_generic_member_access

Same issues here


[stable/superset] support lastest superset

superset lastest not support command "superset runServer"

see #18951 the solution for newer superset versions is in there (with pull request)


LC-16 create OCR stage

Stage is fully explained in the README but here are a couple design notes to go over:

stage currently only supports reading from paths rather than byte array
For temporary files I create a temp folder in the cwd but also make sure to clean up all temp files as I go. I could also clean up the temp folder when I'm done but then it may just make more sense to use a system controlled way to create temp files. If I delete the temp folder at the end it also runs the risk of deleting a folder a user already had content in.

@akul-sethi  just confirming that we'd like to swap out the current images and pdfs that we haven't created in favor of something we have created due to copyright concerns.


Cyclical dependency between Route and defaultRoute option for Integration

I would like to set the defaultRoute for my grafana.oncall.Integration, however, in order to create a grafana.oncall.Route I need to first create an grafana.oncall.Integration in order to specify the required integrationId field.
What is the suggested method to set the defaultRoute?

Closing since it seems there is no need to create a Route before specifying the necessary parameters for defaultRoute.


Remove Singularity Install/Config

Singularity is currently installed and configured using juju actions. Remove these actions such that the functionality can instead be separated into an individual singularity charm. Slurm_ops_manager seems to be tied to each install and will need to be removed wrt to installs as seen below.
Remove Resources

[ ] Remove .deb/.rpm resources

Remove from charm-slurmd/metadata.yaml
Remove Actions

[ ] singularity-install

Remove from charm-slurmd/actions.yaml

Yes, we should remove the Singularity actions, but I think we should at least have a published Apptainer package somewhere before we do that. I have potential snap package we could use here, however, it needs some more work before we can release it publicly on the Snap Store.
We should also look into producing a deb package just in case we have issues propagating the Apptainer snap across shared file systems. The Apptainer developers do have a working Debian recipe, but they need someone to undertake the work to get the package into the official Debian/Ubuntu repositories. I do have a PPA setup here but I need some time to allocate towards creating the package.


Add Redis SET EXPIRE timeout argument, config param

Adds redis sink configuration property redis.set.expire.timeout with default value 0.
When the config key is set (value > 0), it adds expiration to SET arguments, so Redis expires keys that are not updated before expiration timeout is reached. It solves the need of having to cleanup old keys in some scenarios.
Closed #24 as I changed branches structure in my fork.

Related to #21

This is great, I was looking for it. How can we get it one merged?

Any news?