Is it a good practice to use third party package in path form and out of git control?

This is an issue related to CFE and kernel.
Recently, I found my test case for aspectd(https://github.com/alibaba-flutter/aspectd) is broken.
kylewong@KyleWongs-MacBook-Pro aspectd % pub get
Resolving dependencies... (2.8s)
Error on line 14, column 11: Invalid description in the "front_end" pubspec on the "package_config_v2" dependency: "../../third_party/pkg/package_config_v2/" is a relative path, but this isn't a local pubspec.
   ╷
14 │     path: ../../third_party/pkg/package_config_v2/
   │           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   ╵

In short, this error is resulted from pubspec.yaml below:
name: aspectd
description: AOP for Flutter. AspectD is an AOP(aspect oriented programming) framework for dart. It provides call&execute&inject grammar.
version: 0.9.8
homepage: https://github.com/alibaba-flutter/aspectd

environment:
  sdk: ">=2.3.0 <3.0.0"

dev_dependencies:
  kernel: any
  front_end: any
  args: any
  path: any
  yaml: any
  _fe_analyzer_shared: any
  analyzer: any
  mockito: 4.1.1
  test: 1.9.4

dependency_overrides:
  kernel:
    git:
      url: https://github.com/dart-lang/sdk.git
      ref: edd64e6d5c7924a5fb1ef80c5226d24006e7977b
      path: pkg/kernel
  front_end:
    git:
      url: https://github.com/dart-lang/sdk.git
      ref: edd64e6d5c7924a5fb1ef80c5226d24006e7977b
      path: pkg/front_end
  _fe_analyzer_shared:
    git:
      url: https://github.com/dart-lang/sdk.git
      ref: edd64e6d5c7924a5fb1ef80c5226d24006e7977b
      path: pkg/_fe_analyzer_shared
  analyzer:
    git:
      url: https://github.com/dart-lang/sdk.git
      ref: edd64e6d5c7924a5fb1ef80c5226d24006e7977b
      path: pkg/analyzer

And this commit where package_config_v2 dependency is imported for front_end:
https://github.com/dart-lang/sdk/commit/81d4ac07d488fb48383586b29f6503b674a8b917#diff-d3f8f5e7a71f390009e681bbfcc1af94
I noticed that now  front_end is depending on package_config_v2 which is out of git control.
As the flutter is evolving in the master branch, I have to keep up with it and resolve the issue when the test is broken. However, if you depend on front_end, I have to depend on dart sdk in git form.
It works fine before, but this time, if a third party package is imported, the test case would broken and the pub get would fail.
For a package provided by dart-sdk, is it a good practice to use use third party package in path form and out of git control？
@jensjoha
CC @mraleph

Generally, no-one should depend on the "front-end". It is not designed for "public consumption".
That being said, "package_config_v2" didn't really change anything in relation to "git control". The "old" version ("package_config") was also fetched by DEPS mechanism.
It is true that the "pubspec.yaml" file in "front_end" changed to have a local path which seemingly is what broke your workflow. Unfortunately we couldn't really do anything else as the package is still called "package_config" (it's just a new, incompatible and currently unpubliched, version of it) and we (for a while, while other code is being updated) has to have both versions available in the sdk.
None of these explanations really help you of course, but I don't think there's anything else we can currently do. Eventually the package will be released and we can update the pubspec.yaml to be more meaningful.
/cc @lrhn who might also be able to give some nuances.

As Jens says, it's not the DEPS that matters. All SDK dependencies are fetched using a DEPS dependency. All Dart code in the SDK uses the same version of each dependency, and it's independent of any pubspec.yaml file that may occur in the repo.
That means that the pubspec.yaml of the packages in the SDK pkg/ dir are not entirely trustworthy. They are not the source of truth about which versions of packages the SDK actually uses, that's the root DEPS file.
Not all packages in pkg/ are published, and those which are not will only use their pubspec.yaml file for ... well, probably nothing in practice. I recently found that pkg/expect had completely bogus versions in there. So, depending on an unpublished package in pkg/ from outside the SDK repo is not really supported. Jens didn't have to update the pubspec.yaml file at all, but now it is at least correct, even if it isn't useful.
As for package_config, I'm working on a version of package_config which is both forwards and backwards compatible. That will solve the issue of having two dependencies, but not the issue of having a direct github hash dependency. That won't be solved until that package version is actually released.
Also, consider not depending on Dart SDK bleeding edge. It's a development branch, so it not
stable, and it's not intended to be stable.

Generally, no-one should depend on the "front-end". It is not designed for "public consumption".
That being said, "package_config_v2" didn't really change anything in relation to "git control". The "old" version ("package_config") was also fetched by DEPS mechanism.
It is true that the "pubspec.yaml" file in "front_end" changed to have a local path which seemingly is what broke your workflow. Unfortunately we couldn't really do anything else as the package is still called "package_config" (it's just a new, incompatible and currently unpubliched, version of it) and we (for a while, while other code is being updated) has to have both versions available in the sdk.
None of these explanations really help you of course, but I don't think there's anything else we can currently do. Eventually the package will be released and we can update the pubspec.yaml to be more meaningful.
/cc @lrhn who might also be able to give some nuances.
As I want to do the kernel to kernel transformation, kernel_ast_api.dart would help me implement it. The main problem might be that when I want to make aspectd always compatible the latest master branch, I have to take the dart changes simultaneously. The dill operation would easily be broken by the "Unexpected Kernel version" error.

It's not a blocker for me. However, it would be better if the package_config dependency is using a release version later.
CC @lrhn
I would prefer keep this issue open so that I could be notified when the dependency issue is resolved.


JavaScript required to start react

Added the latest javascript topics that are needed to start reactJS.

please add serial no. in all topics so that beginners can identify easily which topics should be covered first

@its-red-eagle added the serial no in front of the file. name.


Friday 27-09-2024 Roll call

Roll Call!
Leave a comment with these two things:

A summary of your study using only emojis
Something you'd like to share, anything goes! (within respect)

emoji cheat sheet

Hello, good morning

ciao

Hello

 Bonjour

Good Morning

🍉

Hello Gm!

Bonjour

hello

Bien le bonjour !

morning

Good morning

hello

hi


Use github.com/pkg/errors to get stack traces from generation errors

Replaces all uses of fmt.Errorf with either errors.New/errors.Errorf, or errors.Wrapf where an existing error was being wrapped with %w. This means that any errors originating or wrapped in our code will be annotated with a stack trace that can be included when the error is logged at the top level, which will make it simpler to track down problems.
I checked for but didn't find any uses of errors.Is or errors.As to update to use pkg/errors instead.
As a driveby I also replaced uses of '%s' or '%v' with %q.

Pull Request Test Coverage Report for Build 158704657

-18 of 18 (0.0%)  changed or added relevant lines in 7 files are covered.
190 unchanged lines in 4 files lost coverage.
Overall coverage increased (+6.2%) to 40.162%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

hack/generator/pkg/astmodel/code_generation_context.go
0
1
0.0%

hack/generator/pkg/astmodel/package_reference.go
0
1
0.0%

hack/generator/pkg/astmodel/resource.go
0
1
0.0%

hack/generator/pkg/astmodel/package_definition.go
0
2
0.0%

hack/generator/pkg/config/configuration.go
0
2
0.0%

hack/generator/pkg/config/type_transformer.go
0
2
0.0%

hack/generator/pkg/jsonast/jsonast.go
0
9
0.0%

Files with Coverage Reduction
New Missed Lines
%

pkg/zips/env.go
3
0%

pkg/zips/types.go
25
54.76%

pkg/zips/client.go
75
3.96%

pkg/zips/template.go
87
26.32%

Totals

Change from base Build 153025994:
6.2%

Covered Lines:
841

Relevant Lines:
2094

💛  - Coveralls


Hide the PREVIEW tab

What feature or improvement do you think would benefit Files?
How can I hide the PREVIEW tab?

Like Windows Explorer:

Requirements

This proposal will accomplish X
This proposal will accomplish Y
This proposal will accomplish Z

Files Version
<IP_ADDRESS>
Windows Version
10.0.22621.2428
Comments
No response

You cant as it isn't a tab. It's a button to see a full preview of the file.

You cant as it isn't a tab. It's a button to see a full preview of the file.

OK, it's a button, not a tab.
I looking for an option to hide full preview button.
like Windows Explorer.

Windows File Explorer doesn't have a dedicated preview section just the small on at the top. What is the reason you want to hide it?

@xmha97 can you confirm if this is the same as #12564?

@xmha97 can you confirm if this is the same as #12564?

No, I want the current Details tab without Preview tab.

That's what #12564 is requesting. It's on our todo list and we'll continue tracking there.


Internal_hostname is not Honored in identity-apps

Describe the issue:

It's expected to use the hostname configured in internal_hostname for every internal communication. Even though this was fixed in product-is, after the unification process, all the fixes have been lost. Therefore, all the related places need to be fixed again with the usage of internal_hostname when invoking internal API calls in identity-apps.

How to reproduce:

Mentioned in https://github.com/wso2/product-is/issues/11878#issue-913818472

Expected behavior:

For internal API calls, internal_hostname should be used.

Environment information:

Product Version: IS-7.0.0 beta2-SNAPSHOT
OS: macos
Database: Default
Userstore: Default

Optional Fields
Related issues:

The git issue which tracked this issue previously - https://github.com/wso2/product-is/issues/11878

Analysis

Currently, the following files are identified as urls which are are built using the server hostname.

Component
File
Code

Authentication Portal
dynamic_prompt.jsp
authAPIURL = IdentityUtil.getServerURL("/api/identity/auth/v1.1/", true, true);

block-sign-in.jsp
Only used in imports. No other usage.

fido2_auth.jsp
authAPIURL = IdentityUtil.getServerURL("/api/identity/auth/v1.1/", true, true);

fido2_identifierfirst.jsp
authAPIURL = IdentityUtil.getServerURL("/api/identity/auth/v1.1/", true, true);

fido2-passkey-status.jsp
authAPIURL = IdentityUtil.getServerURL("/api/identity/auth/v1.1/", true, true);

user-not-found.jsp
Only used in imports. No other usage.

username.jsp
Only used in imports. No other usage.

identifierauth.jsp
Only used in imports. No other usage.

generic-exception-response.jsp
authAPIURL = IdentityUtil.getServerURL("/api/identity/auth/v1.1/", true, true);

basicauth.jsp
 if (StringUtils.isNotBlank(EndpointConfigManager.getServerOrigin())) { url = EndpointConfigManager.getServerOrigin() + proxyContextPath + path; } else { url = IdentityUtil.getServerURL(path, true, false); }

Recovery Portal
self-registration-complete.jsp
String url; if (StringUtils.isNotBlank(EndpointConfigManager.getServerOrigin())) { url = EndpointConfigManager.getServerOrigin() + proxyContextPath + path; } else { url = IdentityUtil.getServerURL(path, true, false); }

self-registration-username-request.jsp
 String identityServerEndpointContextParam = IdentityUtil.getServerURL("/", true, true); commonauthURL = identityServerEndpointContextParam + "/commonauth";

accept-invitaion.jsp
String apiUrl = IdentityUtil.getServerURL("/api/server/v1/guests/invitation/accept", true, true);

components/org.wso2.identity.apps.common
AppPortalUtils.java
String callbackUrl = IdentityUtil.getServerURL(portalPath, true, true);   String accessUrl = IdentityUtil.getServerURL(portalPath, true, true); serviceProvider.setAccessUrl(IdentityUtil.getServerURL(portalPath, true, true));

Here, we have to identify if the url is used for an internal API call and if so fix it such that it uses internal_hostname when building the url. For that purpose IdentityManagementEndpointUtil.getBasePath() method can be used instead of IdentityUtil.getServerURL().

getServerURL is used in My Account and Console as well. @dhaura FYI

Since My Account and Console should use server hostname (not the internal_hostname) for its API calls (these API calls are initiated from the client side unlike in jsps which are hosted in the server), getServerURL() should be used there.

This will be fixed with: https://github.com/wso2/identity-apps/pull/5004


Mention quorum requirement

As specified in https://groups.google.com/d/msg/rabbitmq-users/fEMWie4TEJ0/T2QIist3AAAJ by @dcorbacho @lukebakken.
I don't know if this is the right wording and maybe it should be mentioned in https://www.rabbitmq.com/upgrade.html too?

@johanrhodin Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

Applied manually, thank you.


Adding Isolated and Quarantined to BS

BS is already doing this. Would the parser make your work easier, @jb3-2 ?

Yes it would make my life easier! Ideally the prser would also calculate the other BS specific columns to the right of source.

Thank you very much!!

@jb3-2 maybe we can get those other numbers as well. Currently the scraper scripts are not equipped to handle variables that only occur for one canton. Could you maybe create an issue for that?

@metaodi OK I have created an issue: https://github.com/openZH/covid_19/issues/796 - thanks! J.


ENHSP Seems to Not Work

Describe the bug
Every time I try to run the ENHSP planner on any problem for which it should be a valid solver, it only ever returns that it couldn't find any plan (even when other plans like Fast Downward were indeed able to solve the problem).
To Reproduce
Try to solve any classical planning problem with ENHSP.
Expected behavior
I would expect to receive a valid plan.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows 11

Hi Yomaster10! What version of ENHSP and UP are you using? It could be that you don't have the right version of java installed on your machine (>=17), but that should have been raised as an error at installation time. Anyway, as @mikand said, if you provide us with a piece of code, we can have a better understanding of your situation!

@Yomaster10 I am closing this as it seems resolved. If it is not, just let me know!


[FEATURE] Error Handling

Description
when the Link is Empty then show Some message please add link
Screenshots

Additional information
No response

closing as its already done


Feat/sdk 24r1

Codecov Report

Merging #135 (e8ed931) into main (b4fe3d3) will decrease coverage by 1.28%.
The diff coverage is 82.41%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #135      +/-   ##
==========================================
- Coverage   88.68%   87.40%   -1.28%
==========================================
  Files          11       11
  Lines        2350     2398      +48
==========================================
+ Hits         2084     2096      +12
- Misses        266      302      +36

@lboucin here is a new pr for sdk 24R1 update, following the other fix from previous one. All tests should be green, so ready for review. Thanks


S3 data cleanup

PR #46 modified the locations of certain data files in order to maintain a 1-to-1 mapping between S3 folders and datasets (ie: each dataset should map to only one folder and each folder should contain only one dataset). This is to enable the dynamic domain extraction to easily query the keys of a given dataset (without having to filter out keys belonging to a different dataset in the same bucket).
These modifications include:

s3://covid-eo-data/detections/plane --> s3://covid-eo-data/detections-plane
s3://covid-eo-data/detections/ship --> s3://covid-eo-data/detections-ship
s3://covid-eo-data/xco2/*mean* -->  s3://covid-eo-data/xco2-mean
s3://covid-eo-data/xco2/*diff* --> s3://covid-eo-data/xco2-diff
All files with full text spotlight labels ("Beijing" , "NewYork", etc) in s3://covid-eo-data/BM_500M_DAILY have been copied to files using spotlight identifiers ("be", "ny", etc) (All files with label EUPorts were omitted from this operation because the EUPorts label maps to two spotlights (du and gh))
s3://covid-eo-data/agriculture/CropMonitor* --> s3://covid-eo-data/agriculture-cropmonitor

TODO:
Once the /datasets endpoint has been validated and any other code modifications have been made to ensure that these location modifications do not break anything, the following steps should be taken to avoid data duplication in S3

[x] delete s3://covid-eo-data/detections/plane
[x] delete s3://covid-eo-data/detections/ship
[x] delete s3://covid-eo-data/xco2/*mean*
[x] delete s3://covid-eo-data/xco2/*diff*
[x] delete these files from s3://covid-eo-data/BM_500M_DAILY/
[x] delete s3://covid-eo-data/CropMonitor*

This and more was cleaned up.

@olafveerman following from the sidelines, is there any change needed for the trilateral dashboard?

Our observations:
We have updated the CropMonitor urls, which stopped working on trilateral dashboard and now do. But NO2 data for 2020-10-01 are transparent, while NO2 diff has data.


Add chain and channel monitors

pr title says channel monitor too but i dont see one

Handled what I could/should here, let me know if it's good to go.

needs rebase


coerce arguments to R.add and R.subtract

See #1579

This is still missing the case under discussion from #1579:
R.subtract({valueOf: () => 42}, 2); //=> will throw, but should return 40

> Number({valueOf: function() { return 42; }})
42

Weird.  I tested that in some console and it failed...
Or I thought I did.  I just retested in every console I have and it works, so I don't know what I tried.
Sorry about that.
I want to think about this a bit more, but my first (second I guess!) impression is favorable.

I want to think about this a bit more, but my first (second I guess!) impression is favorable.

Okay. We should either merge this or merge #1579, and close the other either way.

Just something to consider, not sure if this is relevant:
http://jsperf.com/numeric-boxing

whatever happened to "let it fail"? This is exactly the type of hand-holding the lib was always trying to avoid.

whatever happened to "let it fail"? This is exactly the type of hand-holding the lib was always trying to avoid.

The question is whether it's more appropriate for R.inc('XXX') to evaluate to '1XXX' or NaN. To me, the answer is clear, since the former is not a member of the function's supposed return type.
Of course, my strong preference is to throw when the caller breaches the contract, but Ramda is clearly not the library for this approach. So, our only choice is to return a bogus value. In this case the Number type contains a bogus value for such situations: NaN.

:herb:
I've been thinking about this a lot.  And I'm :+1: on this version, and obviously for doing the same for multiply and divide.
The perf numbers from @niloy gave me some pause, but this version reassured me that it's probably an artifact of the test: http://jsperf.com/numeric-boxing/3.  Things are probably being inlined somewhere in the original.
  But when we can coerce the output to the right type, or in this case, when we can work with the grain of JS and use its automatic conversions to avoid returning something of the wrong type, I can't see anything better.  Certainly NaN is a better response than '1XXX'.


Router.run Handler not idempotent

I'm using an approach similar to many of the examples—hanging a static method off of Handlers, accumulating them in the Router.run callback, and rendering the app. However, instead of these methods returning data, they mutate an application state store. Changes to the application state should also trigger a new render. It looks something like this:
let CurrentHandler;

function renderApp(Handler) {
  CurrentHandler ||= Handler;
  if (!CurrentHandler) return;

  React.withContext({appState}, () => {
    React.render(<CurrentHandler />, container);
  });
}

// Rerender the screen whenever the URL changes.
Router.run(routes, Router.HistoryLocation, (Handler, routerState) => {
  (async function run() {
    await runStaticMethods(routerState.routes, routerState, actions);
    renderApp(Handler);
  }());
});

// Rerender the screen whenever the app state changes.
appState.on('change', () => renderApp());

The problem is that Handler is actually the (stateful) router. That means that (if a change event is dispatched on the appState during the course of running the static methods), the rerender it triggers will be with the new screen. (Expected behavior is that it will continue to render the old screen until the static methods complete.) As a result, the new screen can be rendered before its appState dependencies are met.
This is the first earnest look at react-router I've done since the new API a few months back, so I'd appreciate advice on how this should be accomplished, but I also think it would be great for the Handler rendering to be idempotent so that rendering could happen outside of the run callback.
Apologies if I'm misunderstanding something. Thanks!

If I'm understanding you correctly, this is related to #674 .
So perhaps this would work:
var lastState = null;
Router.run(routes, Router.HistoryLocation, (Handler, routerState) => {
  (async function run() {
    lastState = routerState;
    await runStaticMethods(routerState.routes, routerState, actions);
    if(lastState === routerState)
      renderApp(Handler);
  }());
});

Also, when rendering async, beware of this issue: #1027

I also think it would be great for the Handler rendering to be idempotent so that rendering could happen outside of the run callback.

I agree. That's what we're aiming for (#1012).

So perhaps this would work:

Hm, that's not going to do it; the render we have to guard against is the one triggered by the "change" event. I can just remove the listener before the static methods and add it back afterwards but it seems like a hack.

I agree. That's what we're aiming for (#1012).

:thumbsup:

Ah, I overlooked that event.
In that case, you could also try to work around rerendering Handler, e.g. by causing a setState on your top level handler instead, since Handler.willReceiveProps is where the state change magically happens.

follow #1031


Remove embedded resource manifest support from static assets

Tracking issue to avoid embedding the static assets manifest at built time and to remove the code paths in the runtime that try to load the manifest from an embedded resource.

We did this.


Configuration sample

Awesome, thanks so much!

I'm a bit skeptical about this sample. It doesn't really strike me as a how-to in Giraffe.
Is this not more a missing docs thing on the aspnetcore docs site?
What is the advantage of this instead of getting the configuration from the context?
let myApp (next:HttpFunc) (context:HttpContext) =
    task {
        let configuration = context.GetService<IConfigurationRoot>()
        let msg = configuration.["HelloMessage"]
        return! (text msg) next context
    }

The purpose of the PR was to demonstrate a way to access configuration variables in Giraffe, as both the docs and samples were missing that. I agree my solution didn't look like idiomatic Giraffe code, and I was actually hoping somebody would eventually improve on it. Your suggestion to resolve IConfiguration within a handler is nicer, and I have submitted a new PR that simply demonstrates this in a new route within the SampleApp.


Is it possible to provide a base case code to get Chakra ET of DNN?

For example:
Given a DNN object and random data, get Chakra ET on DNN.(data)
Steps include:
-Get ET by Graph Observer(include output file)
-Get Execution Timestamps by Kineto(include output file)
-Merge above two files by param into ET with timestamps (include output file)
-Convert into Chakra ET by Chakra Converter

@francisgan, I have compiled the information into a wiki page. Please take a look at this page: https://github.com/mlcommons/chakra/wiki/PyTorch-Execution-Trace-Simulation-on-a-Simulator. I will update this page gradually as we develop more straightforward examples.

Thank you that helps a lot!


NK3Mini: UP is not properly aborted

It looks like once a User Presence request is started it can only time-out, but if an abort is requested it will not abort. A directly following 2nd UP request will lead to a "busy channel"
To reproduce, e.g. on Gitlab:

click "set up new device"
(you see the device asking for UP)
click "cancel" in the browser
the nk3mini still has the LED active
click "set up new device" again
confirm UP
nothing happens
"busy channel" (I suspect the device panics)

aborting works good for the NK3AN (the LED stops and no busy channel)

Interesting that it works with the NK3AN, cf. https://github.com/Nitrokey/nitrokey-3-firmware/issues/47.  Or is this something different?

I could also imagine that this is originating in the user presence hardware-specific-implementation, which actually makes the most sense if the behavior differs from the nk3an


Windows Terminal not working properly with Visual Studio

Windows Terminal version (or Windows build number)
10.0.22000.282
Other Software
Microsoft Visual Studio Professional 2019
Version 16.11.4
Steps to reproduce
I open VS2019, select my project, and run a debug. Well it work. But after I exit the program and run the debug again, a error occur.
Expected Behavior
https://user-images.githubusercontent.com/29698029/139640372-d21741f9-744c-4acd-beb6-3eda9557c072.mp4
Actual Behavior
No

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #10974 for more discussion.
/dup #10974


kaldifeat installation error

Hello guys,
I was not able to install kaldifeat on GPU machine. I got below error. Please note that installation of kaldifeat on CPU machine is OK. Any help is appreciated.
(base) root@gpu-alex-speech-base-0-0:/workspace/inputs/alexg/asr/src/models/k2/icefall/egs/tedlium3/ASR_FA# pip install kaldifeat
Collecting kaldifeat
Using cached kaldifeat-1.24.tar.gz (467 kB)
Preparing metadata (setup.py) ... done
Building wheels for collected packages: kaldifeat
Building wheel for kaldifeat (setup.py) ... error
error: subprocess-exited-with-error
× python setup.py bdist_wheel did not run successfully.
│ exit code: 1
╰─> [119 lines of output]
running bdist_wheel
running build
running build_py
creating build
creating build/lib.linux-x86_64-3.8
creating build/lib.linux-x86_64-3.8/kaldifeat
copying kaldifeat/python/kaldifeat/fbank.py -> build/lib.linux-x86_64-3.8/kaldifeat
copying kaldifeat/python/kaldifeat/online_feature.py -> build/lib.linux-x86_64-3.8/kaldifeat
copying kaldifeat/python/kaldifeat/plp.py -> build/lib.linux-x86_64-3.8/kaldifeat
copying kaldifeat/python/kaldifeat/spectrogram.py -> build/lib.linux-x86_64-3.8/kaldifeat
copying kaldifeat/python/kaldifeat/mfcc.py -> build/lib.linux-x86_64-3.8/kaldifeat
copying kaldifeat/python/kaldifeat/offline_feature.py -> build/lib.linux-x86_64-3.8/kaldifeat
copying kaldifeat/python/kaldifeat/init.py -> build/lib.linux-x86_64-3.8/kaldifeat
running build_ext
Setting PYTHON_EXECUTABLE to /opt/conda/bin/python3
For fast compilation, run:
export KALDIFEAT_MAKE_ARGS="-j"; python setup.py install
Setting make_args to '-j4'
build command is:
                  cd build/temp.linux-x86_64-3.8

                  cmake -DCMAKE_BUILD_TYPE=Release -DPYTHON_EXECUTABLE=/opt/conda/bin/python3 -Dkaldifeat_BUILD_TESTS=OFF  -DCMAKE_INSTALL_PREFIX=/tmp/pip-install-qagpv2x1/kaldifeat_d5f18258c3ff4469bc7eaf79ef213ed3/build/lib.linux-x86_64-3.8/kaldifeat  /tmp/pip-install-qagpv2x1/kaldifeat_d5f18258c3ff4469bc7eaf79ef213ed3

                  make  -j4  _kaldifeat install

  -- The C compiler identification is GNU 9.3.0
  -- The CXX compiler identification is GNU 9.3.0
  -- Detecting C compiler ABI info
  -- Detecting C compiler ABI info - done
  -- Check for working C compiler: /usr/bin/cc - skipped
  -- Detecting C compile features
  -- Detecting C compile features - done
  -- Detecting CXX compiler ABI info
  -- Detecting CXX compiler ABI info - done
  -- Check for working CXX compiler: /usr/bin/c++ - skipped
  -- Detecting CXX compile features
  -- Detecting CXX compile features - done
  -- C++ Standard version: 14
  -- Downloading pybind11 from https://github.com/pybind/pybind11/archive/5bc0943ed96836f46489f53961f6c438d2935357.zip
  -- pybind11 is downloaded to /tmp/pip-install-qagpv2x1/kaldifeat_d5f18258c3ff4469bc7eaf79ef213ed3/build/temp.linux-x86_64-3.8/_deps/pybind11-src
  -- pybind11 v2.11.0 dev1
  -- Found PythonInterp: /opt/conda/bin/python3 (found suitable version "3.8.10", minimum required is "3.6")
  -- Found PythonLibs: /opt/conda/lib/libpython3.8.so
  -- Performing Test HAS_FLTO
  -- Performing Test HAS_FLTO - Success
  -- Python executable: /opt/conda/bin/python3
  -- TORCH_DIR: /opt/conda/lib/python3.8/site-packages/torch
  -- Looking for pthread.h
  -- Looking for pthread.h - found
  -- Performing Test CMAKE_HAVE_LIBC_PTHREAD
  -- Performing Test CMAKE_HAVE_LIBC_PTHREAD - Failed
  -- Looking for pthread_create in pthreads
  -- Looking for pthread_create in pthreads - not found
  -- Looking for pthread_create in pthread
  -- Looking for pthread_create in pthread - found
  -- Found Threads: TRUE
  -- Found CUDA: /usr/local/cuda (found version "11.3")
  -- The CUDA compiler identification is unknown
  CMake Error at /opt/conda/lib/python3.8/site-packages/torch/share/cmake/Caffe2/public/cuda.cmake:47 (enable_language):
    No CMAKE_CUDA_COMPILER could be found.

    Tell CMake where to find the compiler by setting either the environment
    variable "CUDACXX" or the CMake cache entry CMAKE_CUDA_COMPILER to the full
    path to the compiler, or to the compiler name if it is in the PATH.
  Call Stack (most recent call first):
    /opt/conda/lib/python3.8/site-packages/torch/share/cmake/Caffe2/Caffe2Config.cmake:92 (include)
    /opt/conda/lib/python3.8/site-packages/torch/share/cmake/Torch/TorchConfig.cmake:68 (find_package)
    cmake/torch.cmake:14 (find_package)
    CMakeLists.txt:59 (include)

  -- Configuring incomplete, errors occurred!
  See also "/tmp/pip-install-qagpv2x1/kaldifeat_d5f18258c3ff4469bc7eaf79ef213ed3/build/temp.linux-x86_64-3.8/CMakeFiles/CMakeOutput.log".
  See also "/tmp/pip-install-qagpv2x1/kaldifeat_d5f18258c3ff4469bc7eaf79ef213ed3/build/temp.linux-x86_64-3.8/CMakeFiles/CMakeError.log".
  make: *** No rule to make target '_kaldifeat'.  Stop.
  Traceback (most recent call last):
    File "<string>", line 2, in <module>
    File "<pip-setuptools-caller>", line 34, in <module>
    File "/tmp/pip-install-qagpv2x1/kaldifeat_d5f18258c3ff4469bc7eaf79ef213ed3/setup.py", line 32, in <module>
      setuptools.setup(
    File "/opt/conda/lib/python3.8/site-packages/setuptools/__init__.py", line 163, in setup
      return distutils.core.setup(**attrs)
    File "/opt/conda/lib/python3.8/distutils/core.py", line 148, in setup
      dist.run_commands()
    File "/opt/conda/lib/python3.8/distutils/dist.py", line 966, in run_commands
      self.run_command(cmd)
    File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/opt/conda/lib/python3.8/site-packages/wheel/bdist_wheel.py", line 299, in run
      self.run_command('build')
    File "/opt/conda/lib/python3.8/distutils/cmd.py", line 313, in run_command
      self.distribution.run_command(command)
    File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/opt/conda/lib/python3.8/distutils/command/build.py", line 135, in run
      self.run_command(cmd_name)
    File "/opt/conda/lib/python3.8/distutils/cmd.py", line 313, in run_command
      self.distribution.run_command(command)
    File "/opt/conda/lib/python3.8/distutils/dist.py", line 985, in run_command
      cmd_obj.run()
    File "/opt/conda/lib/python3.8/site-packages/setuptools/command/build_ext.py", line 87, in run
      _build_ext.run(self)
    File "/opt/conda/lib/python3.8/site-packages/Cython/Distutils/old_build_ext.py", line 186, in run
      _build_ext.build_ext.run(self)
    File "/opt/conda/lib/python3.8/distutils/command/build_ext.py", line 340, in run
      self.build_extensions()
    File "/opt/conda/lib/python3.8/site-packages/Cython/Distutils/old_build_ext.py", line 194, in build_extensions
      self.build_extension(ext)
    File "/tmp/pip-install-qagpv2x1/kaldifeat_d5f18258c3ff4469bc7eaf79ef213ed3/cmake/cmake_extension.py", line 124, in build_extension
      raise Exception(
  Exception:
  Build kaldifeat failed. Please check the error message.
  You can ask for help by creating an issue on GitHub.

  Click:
      https://github.com/csukuangfj/kaldifeat/issues/new

  [end of output]

note: This error originates from a subprocess, and is likely not a problem with pip.
ERROR: Failed building wheel for kaldifeat
Running setup.py clean for kaldifeat
Failed to build kaldifeat
ERROR: Could not build wheels for kaldifeat, which is required to install pyproject.toml-based projects
(base) root@gpu-alex-speech-base-0-0:/workspace/inputs/alexg/asr/src/models/k2/icefall/egs/tedlium3/ASR_FA#

please refer to kaldifeat's installation documentation for how to install it.
It has a detailed guide.

Hello guys. I am missing something.
For k2 installation I am using following commands:
pip install torch==1.13.0+cu116 torchaudio==0.13.0+cu116 -f https://download.pytorch.org/whl/torch_stable.html
pip install k2==1.24.3.dev20230725+cuda11.6.torch1.13.0 -f https://k2-fsa.github.io/k2/cuda.html
According to the documentation for kaldifeat installation I have to use following commands:
pip install torch==2.0.1+cu118 -f https://download.pytorch.org/whl/torch_stable.html
pip install kaldifeat==1.25.0.dev20230726+cuda11.8.torch2.0.1  -f https://csukuangfj.github.io/kaldifeat/cuda.html
Could you please send me the command that I can use for kaldifeat installation with torch==1.13
Thanks,
AlexG.

the documentation lists example, example, example installation commands.
We expect that you know how to adapt it to your own needs.

please visit https://csukuangfj.github.io/kaldifeat/cuda.html
to find out the exact string you need to give to
pip install.

pip install kaldifeat==1.25.1.dev20231022+cuda11.6.torch1.13.0 -f https://csukuangfj.github.io/kaldifeat/cuda.html

@AlexandderGorodetski


add or remove braces to arrow function

I cant get this feature to work (or maybe it needs implementation in coc-tsserver?) It should be available in typescript: https://github.com/Microsoft/TypeScript/pull/23423
The only option i get is to create a function statement. I want to be able to quickly add braces around an arrow function, e.g. if i have something like:
<button onClick={() => setCount(count + 1)}>
  Click me!
</button>

Then i want to be able to quickly convert that arrow function to a block as such:
<button onClick={() => {
  return setCount(count + 1)
}}>
  Click me!
</button>

vim version: NVIM v0.5.0
node version: v14.17.2
coc.nvim version: 0.0.80-3086844413
coc.nvim directory: /home/linde/.vim/plugged/coc.nvim
term: alacritty
platform: linux

In my tests, put your cursor on => and fire <Plug>(coc-codeaction-cursor), you will get:

After the first action executed:

What's your coc-tsserver version? I'm using 1.8.6.

Check log of your tsserver https://github.com/neoclide/coc-tsserver#troubleshooting

In my tests, put your cursor on => and fire <Plug>(coc-codeaction-cursor), you will get:

After the first action executed:

Thank you! I was using coc-codeaction, i didn't know of coc-codeaction-cursor :smiley:

coc-codeaction-cursor is recommended


Move beta.packages to release.sbom_cyclonedx

In #732, new policy rules were added that use the newly added ec.purl.parse custom rego function. To avoid issues with older versions of the ec-cli that do not provide the function, they were added to a new namespace, policy/beta, instead of the usual policy/release.
This issue is about moving those policy rules to policy/release, likely under the sbom_cyclonedx package.
Let's aim for doing this right after January 1st as that should be sufficient time to allow clients to update.
Acceptance Criteria

The policy rules from beta.packages are moved under the release namespace.

The ec.purl.parse needs at least version 2269 in the last 7 days the oldest version was 2340 and in the last 30 days the oldest version was 2286. I think it is now safe to do this.


How is OpenJDK used/setup?

I have run the scripts as suggested (commenting out the $JVM_FILE env variable) and everything seemingly installs however LUCEE will not run, the nginx web server is up and available. I have a feeling that there is no JVM available. Tomcat is saying it cannot start Lucee
What am I doing wrong here in regards to simply running these scripts?
This is on a fresh Ubuntu installation on Digital Ocean.

Can you post the snippets from the logs where Tomcat says it cannot start Lucee?
If tomcat is getting that far, then you do have java installed. OpenJDK is a dependency of tomcat, so it gets installed when you install tomcat if it was not there already. You can run java -version to double check.

@malpaso haven't heard back - do you have any further questions, if not I will close the issue?

I am at a loss. I have tried to get this to work and have not had success. I am running this on a new droplet with DO. I can't seem to get any of the admins to work. When I try to access the IP address with port 8080 my browser just spins. Is there a walk through of what to do once you are done with the install?

@kwfricke The Lucee Admin is blocked by default - you need to edit /etc/nginx/lucee.conf and add a line to allow your IP, take a look here:
https://github.com/foundeo/ubuntu-nginx-lucee/blob/master/etc/nginx/lucee.conf#L5


data cosmos mask 0.29 360

add mask from the full COSMOS catalog.
resolution: 0.29 arcmin/pixel
maps size: 360x360

I added mocked COSMOS shear and convergence maps

Thanks! just to make sure, can you list here what code you used to produce those?

sure : https://github.com/CosmoStat/jax-lensing/blob/kappatng-dataset/notebooks/KappaTNG_COSMOS_emulation.ipynb

Great great great, with the notebooks linked in the PR, if something goes wrong later we can come back, see that the maps were added here, and remember how they were produced.


M3-1101 New External Link component

New component for external links to add an icon next to them
added in story book and implemented at /support

Coverage increased (+0.03%) to 25.972% when pulling 87c03d004bf45dae224b83a15fc7018042b67700 on alioso:M3-1101 into a47d32027cd99cf11e5845c6c17c7533621250da on linode:develop.

Coverage increased (+0.03%) to 25.972% when pulling 87c03d004bf45dae224b83a15fc7018042b67700 on alioso:M3-1101 into a47d32027cd99cf11e5845c6c17c7533621250da on linode:develop.


New committer for US

Please add @sandragesing to have permissions to work on the US_17 survey with me.

She was already added last time. Does she can access the repo?

sorry, my mistake.


Expand schedule granularity support

This is only a partially articulated thought but it's been coming up with increasing frequency so I want to get it written down.
The options for schedule in the solution are somewhat less than what is supported in native jobs. This was a reasonable 80/20 choice in original development because capturing full coverage is a pain and most jobs don't need it. In practice though, the partial support for schedule options is a disproportionate source of metrics pollution.
For example: Jobs that need only run monthly are set to daily and have internal proc logic to check Day-of-Month before proceeding. Ditto with weekly jobs or jobs that want certain day-of-week restrictions. These jobs have a huge false positive success rate for those no-op executions which masks chronic failures.
Expand support for scheduling options and provide examples on the "new" variants.

Any suggestions for the schema?  We could keep the schema the same and add Weekly with FrequencyInterval solving for DayOfWeek.  This would only give us support for every 1 week (which is less than the options for SQL Agent), but feels like that'd solve a large chunk.
Similar thoughts on adding Monthly and DayOfMonth would be stored in FrequencyInterval.
Do you see the need to support schedules like 'last Wednesday of every month'?

Tbh, I sort of had this in mind for v2.0. I also want to add support for multi-step jobs for a similar reason (but I'll try to keep that to a separate issue). As such, there's some idea of support backwards compatibility, but I don't think it's prudent to maintain the current schema to the exclusion of feature improvements.

Do you see the need to support schedules like 'last Wednesday of every month'?

It was a problems with schedule of this type that broke me into creating the issue last night so... ✨yessssss✨

Maybe you can share some more details of the kinds of schedules, as those are sometimes the default and the 27th of each month is fine.
There's a balance to strike between a more fully-featured scheduler (which might mean it's time to grow-up from SQL Agent) and a simple schema (recreating the complexity of SQL Agent is perhaps an anti-goal).

recreating the complexity of SQL Agent is perhaps an anti-goal

it is also almost certainly what I'm steering towards here 😅


Fix: Use 'navigation' instead of 'ui.load' for auto transaction operation

:scroll: Description

Use 'navigation' instead of 'ui.load' for auto transaction operation

Closes #670
:green_heart: How did you test it?

Updated unit tests.

:pencil: Checklist

[x] I reviewed submitted code
[ ] I added tests to verify changes
[ ] I updated the docs if needed
[x] All tests passing
[x] No breaking changes

Codecov Report

Merging #675 (339aec4) into main (14203b9) will increase coverage by 5.50%.
The diff coverage is n/a.

:exclamation: Current head 339aec4 differs from pull request most recent head a5e85c4. Consider uploading reports for the commit a5e85c4 to get more accurate results

@@            Coverage Diff             @@
##             main     #675      +/-   ##
==========================================
+ Coverage   90.65%   96.15%   +5.50%
==========================================
  Files          97        2      -95
  Lines        3145       52    -3093
==========================================
- Hits         2851       50    -2801
+ Misses        294        2     -292

Impacted Files
Coverage Δ

.../lib/src/navigation/sentry_navigator_observer.dart

dart/lib/src/sentry_user_feedback.dart

dart/lib/src/sentry_exception_factory.dart

dart/lib/src/sentry_options.dart

dart/lib/src/hub_adapter.dart

dart/lib/src/transport/rate_limit_category.dart

dart/lib/src/protocol/sentry_id.dart

dart/lib/src/sentry_stack_trace_factory.dart

dart/lib/src/noop_hub.dart

dart/lib/src/sentry_tracer_finish_status.dart

... and 85 more

Continue to review full report at Codecov.

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


COMP: Upgraded GoogleTest to 1.8.1

Upgraded GoogleTest to 1.8.1, to fix VS2017 build errors:
error C2220 warning treated as error: no 'object' file generated [SuperElastix-build\Testing\googletest-build\googlemock\gmock.vcxproj] [F:\X\Bin\vc141-64\SelxDev\D\SuperElastix-build\Testing\googletest-download\googletest.vcxproj] SuperElastix-build\Testing\googletest-src\googletest\include\gtest\internal\gtest-port.h
gtest 1.8.1 is from August 2018 (whereas gtest 1.8.0 was from July 2016).

It appears that ITK gets gtest directly from the master branch!
https://github.com/InsightSoftwareConsortium/ITK/blob/v5.0rc01/Modules/ThirdParty/GoogleTest/UpdateFromUpstream.sh#L6

Green on Travis (I think it's not necessary to wait any longer for jenkins), so I'll merge!


Improve eslint files option documentation

Hi 👋 ! Thanks for continuing to improve this plugin.
I discovered a place for potential improvement in the docs after upgrading from v4 to v5 that i suspect a number of folks may run into.
Current behavior
The current recommendation to use files: "./src/**/*" causes issues in common webpack project setups. The docs say:

same as command eslint ./src/**/* --ext .ts,.tsx,.js,.jsx

But i don't believe to be the case without explicitly specifying the extensions. Perhaps the recommendation should include the extensions by default?
Expected behavior
The plugin provides some recommendations for projects that use CSS and other types of file loaders.
Steps to reproduce the issue
Import a .css file in a project with a CSS loader configured. Observe the error with the recommended files configuration:
ERROR in src/components/Foo/Foo.css
[unknown]: Parsing error: "parserOptions.project" has been set for @typescript-eslint/parser.
The file does not match your project config: src/components/Foo/Foo.css.
The extension for the file (.css) is non-standard. You should add "parserOptions.extraFileExtensions" to your config.

Changing files to be configured as follows seems to solve the issue in my case:
files: "./src/**/*.{js,jsx,ts,tsx}"
Environment

fork-ts-checker-webpack-plugin: 5.0.3
typescript: 3.9.5
eslint: 7.3.0
webpack: 4.43.0
os: macOS 10.15.5

Thanks for the recommendation @ianschmitz! What do you think @piotr-oles ?

@johnnyreilly note that i edited my OP and included a note about the enabled property.

Thanks for reporting this issue. I've created a PR to fix it :)

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[minor enhancement] Display Amount of Apples used

After completing run, when clicking on next run, displays the current amount of apple that was used in a toast.
Useful to users who leave their phones on and come back later to check how much apples they have already used.

Suggestive area to place the toast, if you want it after result ends, or before it even clicks on quest, modify as appropriate
-Shows no conflict, initiating merge pull request


feat(side-menu): add new <bq-side-menu> and <bq-side-menu-item>  components

Closing it in favor of #289


Remove extra echo line in the PASE terminal head

Changes
In Terminal.ts, filter out the extra echo without printing it. Now the PASE terminal welcome message looks clearer.

Checklist

[x] have tested my change
[ ] updated relevant documentation.
[x] Remove any/all console.logs I added
[x] eslint is not complaining
[x] have added myself to the contributors' list in CONTRIBUTING.md
[ ] for feature PRs: PR only includes one feature enhancement.

No doc points in https://codefori.github.io/docs/#/ need to be updated.
bz.

Looks ok to me.

@codefori/core Can I get a second opinion?

@worksofliam Looking okay to me - only issue (not caused by this change!) is that the welcome message only appears from the second PASE terminal started and does not appear in the first terminal started?

@chrjorgensen That is odd. I just tried spinning up 8 new terminals to get it but didn't get the same result.

@worksofliam It's okay now - don't know why, but after several attempts where the welcome message did not appear on first PASE terminal, now it appears everytime... again, nothing to do with this PR, so go ahead and merge! :smiley:


[Feature] Add receive address list

Add a receiving address list that can store receiving addresses with names associated. Like a "friends" list for sending payments.

I want to use Litecoin and LiteWallet in place of venmo, paypal, cashapp etc. Having to paste in the same receiving address for recurring transactions has the potential for mistakes especially for new users


feat: customizable events

Checklist
Please put "X" in the below checkboxes that apply::

[ ] If committing a bugfix, I have tested it in different browsers (Chrome, Firefox, Safari).
[ ] If committing a new feature, I have first submitted an issue (Please note: you are free to open PRs for non-issued features, but opening an issue increases your chance of a successful PR).
[X] If committing a new feature, I have also written an appropriate test suite for it.

I have tested the following:

[X] Qalendar component in month mode.
[X] Qalendar component in week mode.
[X] Qalendar component in day mode.
[X] Day mode on emulated mobile.
[X] Dragging and dropping events.
[X] Resizing events in day/week modes.
[X] Clicking events to open event dialog.

This PR solves the following problem.
This PR adds one of the features in this feature request: https://github.com/tomosterlund/qalendar/issues/50
The implementer should be able to:

Take full control over the looks of an event through scoped, named slots.
Take (almost) full control over the appearance of the event dialog, that opens upon clicking an event.

Apart from the above features, this PR also adds the configuration option disableModes.
How to test this PR.

Start dev server and go to http://localhost:3000/#/cypress/customized-events
Test that the above two features work.
Run npm run docs:dev to view the new documentation for the features, and see if anything needs to be clarified for any developers wanting to use these features.

@felix-berlin for turning all events on the url above to custom events, you need to change this line:
if (i % 2 === 0) e.isCustom = true;
to just:
e.isCustom = true;
Forgot to delete it before pushing ^^

Pushed a bunch of attempts at fixing a build error, for anyone using the slots in TS. Not critical however, because there are workarounds, so I will give it up for now, and open a new branch where I will fix this later.
Important however, that we merge this branch with "Squash and merge" when testing is done, since I spammed it with a few not so valuable commits.

Hey Tom,
I'm done with testing. Looks pretty good to me 💪
I also changed the release workflow trigger to "push on master". I think it's not necessary to run the workflow on pull request.

Cool! Thanks 🙏I’ll merge later today then. Might need to undo a couple of changes on the type declarations I pushed

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Development/debugging advice? Struggling to use gdb to debug clboss

Is there any documentation on this which I've missed?
I am trying to use gdb to debug clboss but I'm getting tied up in knots.
I see there is a --debugger command line option to clboss. The only way I can find to persuade c-lightning to start the clboss plugin with this option is to use a wrapper script:
#!/bin/bash
cd $HOME/src/clboss
./clboss --debugger $*

and then tell lightning-cli to start that wrapper:
$ lightning-cli plugin start `pwd`/debug-wrap.sh

This fires up a terminal with gdb attached to clboss, but (even though as far as I can tell the paths are correct) it doesn't seem to be able to find the source, e.g.
(gdb) list Boss/Mod/OnchainFundsIgnorer.cpp:30
No source file named Boss/Mod/OnchainFundsIgnorer.cpp.
(gdb) shell
$ ls -l Boss/Mod/OnchainFundsIgnorer.cpp
-rw-rw-r-- 1 steve steve 6353 May 20 17:57 Boss/Mod/OnchainFundsIgnorer.cpp

I also seem to be struggling to step through the code because the event framework is constantly receiving SIGSTOP signals, but this may be normal or may be a side effect of these other problems.
As far as I can tell my clboss executable does have debug symbols - "objdump --syms clboss | c++filt" shows lots of clboss symbols. Do I need to pass some special arguments to the configure script to get proper symbols?
If there's any interest, I'm happy to write up a starter "how to work with clboss for developers" document once I know how to do it myself.
Any advice would be appreciated, thanks!
(For what it's worth, one of my local code changes is making clboss crash on startup and I'm trying to debug that. But I have temporarily reverted back to the upstream clboss code while I figure out how to use the debugger with clboss, so unless I made a mistake that shouldn't be the problem here.)
It feels a bit like I'm abusing the issues section by asking this question here, if there's somewhere else to ask this kind of thing please let me know.

I've had some luck with the debugging symbols by running configure like this:
CPPFLAGS=-g LDFLAGS=-g ./configure --enable-debug

I don't know if some of that is unnecessary, but it does seem to be working. I am currently fighting with the "can't debug properly for all the SIGSTOP signals" problem, so I haven't got that much further and it may be the debug symbols are still wrong/incomplete somehow.

The magic gdb incantation for the SIGSTOP problems appears to be:
handle SIGSTOP nostop

I now have a backtrace on a SEGV. It's an incomprehensible C++ backtrace, but it's progress. :-)

Check out c++filt for demangling the symbols

Thanks! I think gdb is doing that automatically - they were just incomprehensible because of all the templates, not because they were mangled. :-) But I am slowly getting to grips with things and making what feels like progress on my prototype for https://github.com/ZmnSCPxj/clboss/issues/202.


Requesting /ignore [player]

The following command will make it so you can ignore another player and make it so you do not see their messages in chat, or private message. Also, the player ignored cannot see your messages either.
Have a permission chatchat.ignore.bypass (Players with this permission CANNOT be ignored.)

Duplicate #80


Can't postMessage to view

Hi,
Have been sitting for quite some time now trying to get to wizViewMessenger.postMessage(Data message, String targetView); function to work. Creating the view and showing goes fine. But when I post at message nothing happens. The view never gets the message and their is no error message from the cordova application either.
The other way around works perfectly i.e. sending a message from the view to the cordova application.
This is the code in the cordova application:
wizViewManager.create("pollux", {
src: "http://pollux-server.herokuapp.com/",
}, success, fail);
function success(){
wizViewManager.show("pollux");
wizViewMessenger.postMessage("Message from phoneGap", "pollux");
console.log("success");
}
This is the code in the webapplication:
$( document ).ready(function() {
window.addEventListener('message', wizMessageReceiver, false);
});
function wizMessageReceiver (event) {
console.log("Message received from PhoneGap: " + event);
$("#phonegap-msg").text(event.data);
}

Closing as this should have been fixed with #90. Please re-open the issue if you still have it after updating.


I can't add id with autoincrement

I want to create table with
"id INTEGER PRIMARY KEY AUTOINCREMENT"
but when I add new row for this table, error comes up and it says:

table product_groups has 9 columns but 8 values were supplied

Expected Behavior
tx.executeSql(
   'CREATE TABLE IF NOT EXISTS product_groups (
         id INTEGER PRIMARY KEY AUTOINCREMENT,
         group_id TEXT,
         name TEXT,
         color TEXT,
         foreground TEXT,
         image TEXT,
         header TEXT,
         menuId TEXT,
         isFastMenu TEXT)' );

And to insert in table my query is :
tx.executeSql(
              'INSERT INTO product_groups VALUES (?, ?, ?, ?, ?, ?, ?, ?)',
              [
                prod.groupId,
                prod.name,
                prod.color,
                prod.foreground,
                prod.image,
                prod.header,
                prod.menuId,
                prod.isFastMenu,
              ],
            )

and I got error

table product_groups has 9 columns but 8 values were supplied

Suggest you try these SQL in some online SQL test db to verify it is working.

I tried @andpor  and it works.

thanks alot @hinciler , you just saved me hours of debugging


Error Decoding Receivers Unknown Type awscloudwatchmetrics

Hello,
I was looking to use the awscloudwatchmetrics and ran into the below scenario:
Using otel/opentelemetry-collector-contrib:0.107.0 and attempting to use the awscloudwatchmetrics receiver (https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/awscloudwatchmetricsreceiver) gave the following error:
error decoding 'receivers': unknown type: "awscloudwatchmetrics" for id: "awscloudwatchmetrics" (valid values: [expvar influxdb memcached postgresql sapm elasticsearch awsxray googlecloudspanner k8s_events pulsar snowflake sqlquery statsd nop httpcheck otelarrow podman_stats datadog k8sobjects kafka loki namedpipe oracledb journald riak tcplog couchdb opencensus wavefront webhookevent mongodbatlas purefb prometheus_simple splunk_hec nsxt filelog haproxy jaeger sshcheck vcenter windowsperfcounters apachespark active_directory_ds awsfirehose kafkametrics signalfx windowseventlog otlp filestats hostmetrics iis splunkenterprise sqlserver awscloudwatch zookeeper carbon chrony cloudfoundry googlecloudpubsub nginx otlpjsonfile zipkin apache azureblob azuremonitor docker_stats kubeletstats mysql snmp aerospike collectd jmx mongodb purefa rabbitmq udplog azureeventhub awsecscontainermetrics cloudflare prometheus skywalking awscontainerinsightreceiver flinkmetrics fluentforward k8s_cluster receiver_creator redis solace syslog bigip])
Stream closed EOF for otel-collector/testing-opentelemetry-collector-agent-5w5rh (opentelemetry-collector)
Not sure if this is related to the list defined in distributions/otelcol-contrib/manifest.yaml.

Dosu is correct, the component isn't there, as it's still under development:
https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/receiver/awscloudwatchmetricsreceiver
In fact, this component will likely be removed before it's complete, as the development has stalled on that one.


Fix find entry via treesitter

WHAT
Fix issue where the find entries method was returning two nodes instead of one.
WHY
HOW
Screenshots (if appropriate):

Types of changes

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

Checklist:

[ ] Linter
[ ] Tests
[ ] Review comments
[ ] Security

Thanks @hsanson 🙏 Let me try.


add proto for livestream health exports stream

Add the protobuf spec for the livestream health exports stream.

@jeremycondon and @stevenlyons just added you two in case you have opinions about the file hierarchy / naming in this repo, feel free to disregard if it's not of interest!

Updated to put livestream-health-exports under a video namespace directory and add the missing proto subdirectory & readme

There's still some discussion about the proper namespace for the proto definition so @nidhik will follow up to make updates as needed to this PR while I'm out next week.


Contract Module

Custom Documentation:

[ ] The purpose of the module
[ ] Explanation of the real world users and their role/interactions with the module
[ ] Key logic, processes, or assumptions that happen within the module
[ ] Details on how a module easily integrates with other associated modules

Rust Docs:

[ ] Available storage items and what they hold
[ ] Public Functions
[ ] Internal Functions

Pull request in:
https://github.com/paritytech/substrate/pull/2045
Could use more examples though


Add warning messages for incorrect function calls

For issue: https://github.com/styled-components/styled-components/issues/352
This adds warning messages for these function calls:
styled.div(`
  html {

  }
`)

The error message will be:
Error: styled.div is called as a function.
It seems like styled.div is called as 'styled.div(`css`)', it is supposed to be called as 'styled.div`css`'

I added sinon to assert that console.error has been called, I'm not sure what your policy on this is. Also, it seems that the yarn.lock changed more than just for sinon. I tried doing a clean install with the old yarn.lock, but it still changed.
Very curious what you think of this approach 😄

Thank you for the PR. We might want to wait until we migrated our tests to Jest. AFAIK @geelen is currently working on it.

I don't think this is the right approach unfortunately. If we want to enforce our API — which makes sense — then we should put in an invariant that throws. A console.error is neither a warning per se, nor an error.
I believe we should just use invariant and throw, which is by the way easier to test as well. It's arguably the more popular way to do things, and we'd actually enforce it this way. https://github.com/reactjs/react-redux/blob/4d302257e3b361731f44b1f546e547ed578c8eec/src/components/connectAdvanced.js#L90
Also, I think the function name could be really explicit e.g. invariantArray(arr) or enforceArray(arr), instead of just validate, which is pretty cryptic

I agree with this,  we could break applications that unknowingly call the functions the wrong way. In that case we'd need to do a major version bump.
I'll also update the name, at first I used as a function to do more kinds of validations but this is indeed very cryptic.

@CompuIves We could merge this into v2. In that case it would become part of the next major release 😄

Updated PR based on the feedback!

Good points, I updated the PR

@mxstbr Any idea whether we still want this? If so we probably want it to compile away in prod

This is a better target for a linter, IMO.


How does ShadowGenerator work well with  Material has alpha.

const ground = Mesh.CreateGround(null, 10, 10, 2, scene);
ground.receiveShadows = true;

const disc = Mesh.CreateDisc('null', 0.5, 60, scene);
disc.position = new Vector3(0, 1, 0);
disc.material = new StandardMaterial(null, scene);
disc.material.alpha = 0.9;

const light = new PointLight(null, new Vector3(0, 5, 0), scene);
const shadowGenerator = new ShadowGenerator(512, light);
shadowGenerator.getShadowMap().renderList.push(disc);

when i do this, there no any shadows ......

Hello do you mind using the forum for questions? the best thing would be to provide a repro using the playground
thanks a lot:)

(but for your question: shadows work only with no alpha or alpha test only. Alpha blending is not supported)


Multi-GPUs usage

Hi,
Could you please let me know how I can use the guidance with multi-gpu settings? I tried models.transformers(modelname, device-map='auto'), but checking with nvidia-smi during the inference time, I see that the GPUs are not used.

Hmm. It should just pass those params to the underlying transformers model. I have a single GPU box right now though so it is hard for me to test. If you find more details I can comment though.

device_map="auto" works for me. That underscore might be the issue.


upgrade yapf to the latest version

Description:
Upgrade yapf to the latest version. We'd like to reuse it in our local repo, and some of the newer versions contain fixes we need.
This required reformatting all the files for their new rules. Happy to change any rules, as necessary.
Risk Level: Low
Testing: Ensure py format checks can still pass.
Docs Changes: N/A
Release Notes: N/A
fixes #7389

@SecurityInsanity can we exclude generated python files from formatting?

Sure can, I assume those are the ones under: example/?

right, those _pb2.py and _pb2_grpc.py


[UX] In the past, the check results used to print the names of files being checked and it was very useful!

While reviewing PR #3432 I noticed that the text terminal reporter is not printing the filenames as it used to do. I do not recall making that change, so this may be a bug.
Not knowing which specific file is being checked severely degrades user experience. So this needs an urgent fix!

I currently cannot replicate this problem.
It's all looking good...
¯\_(ツ)_/¯


incomplete documentation for --exclude-if-present

Output of restic version
restic 0.8.3
compiled with go1.10 on linux/amd64

How did you run restic exactly?
Read the documentation at: http://restic.readthedocs.io/
Looking for '--exclude-if-present'
What backend/server/service did you use to store the repository?
B2
Expected behavior
Documentation explains how '--exclude-if-present' is configure and works, e.g.

It says it excludes the contents of the folder, but does that include subdirectories?

Does the filename match only exactly or support the restic wildcards?

The help text mentions you can specify a 'header' to match in the file, but not the syntax for the header or how it is matched. It is a match from byte 0? Or a literal sub-string match anywhere in the file?

Actual behavior
http://restic.readthedocs.io/en/latest/040_backup.html?highlight=--exclude-if-present
--exclude-if-present Specified one or more times to exclude a folders content if it contains a given file (optionally having a given header)
http://restic.readthedocs.io/en/latest/manual_rest.html?highlight=--exclude-if-present
--exclude-if-present stringArray takes filename[:header], exclude contents of directories containing filename (except filename itself) if header of that file is as provided (can be specified multiple times)
Steps to reproduce the behavior
Read the documentation at: http://restic.readthedocs.io/
Looking for '--exclude-if-present'
Do you have any idea what may have caused this?
Overworked developers :+1:
Do you have an idea how to solve the issue?
Read the code, if I can find it.
Did restic help you or made you happy in any way?
B2 support is working great and smoothly so far.
It would be great if people could contribute examples of using this option. E.g. I'd like to use it to exclude MySQL data folders, maybe on the auto.cnf file will work? But will it exclude sub-folders with the table data?

I found the older code and looks like 'header' is a comparison from byte zero. In newer code in the master this has gone somewhere else the github search can't find.
https://github.com/restic/restic/blob/c22c582546976a5153cf41b95231fdb7ec3d0d4c/cmd/restic/cmd_backup.go#L584-L634

FYI, the code was moved to a separate file, here: https://github.com/restic/restic/blob/master/cmd/restic/exclude.go

I'm taking the liberty of closing this now, for the following reasons relating to the questions in the original post:

It says it excludes the contents of the folder, but does that include subdirectories? - Yes, it includes subdirectories too, as they are a part of the contents of the folder. All contents is excluded, and I think this is what you'd expect if you were to ponder what the documentation is telling you on this topic. Doesn't need clarifying.

Does the filename match only exactly or support the restic wildcards? - The documentation has been updated to state that wildcards are not supported for this filename, so this is considered fixed.

The help text mentions you can specify a 'header' to match in the file, but not the syntax for the header or how it is matched. It is a match from byte 0? Or a literal sub-string match anywhere in the file? - I argue that a "header" is something that pretty much everyone would consider being "the first part of the file", i.e. starting from byte 0. I can't think of a single person I know that would think a header starts from some other byte than the very beginning of the file. It's so common that we don't need to mention this. If someone ever need to know, they can ask in the forum or somewhere else, this is too detailed to be worth a PR (but we wouldn't dismiss one, if anyone is up for it).

Playing devil's advocate here : restic itself writes "headers" at the end of the file 😆

@shtratos What/where are you thinking of? :)

https://github.com/restic/restic/blob/master/doc/design.rst#pack format
Here in the pack format description it says that headers are written at the end of file.

Nice catch ❤


[Program]: Write a Julia program to find second smallest number in an array

Description
Write a Julia program to find second smallest number in an array
Input  : [1, 2, 3, 4, 5]
Output : 2

How to contribute

Save the solution in program/program/find-second-smallest-number-in-an-array/program/find-second-smallest-number-in-an-array.jl file

!assign


download formatted references from filter sources not working

Even for one reference the wheel keeps on spinning....
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

When I  '...'
Then I '....'
And I '....'
See error

Expected behavior

Do a simple search for one reference: 113767
Heraty, J.M., Mbanyana, N. & Van Noort, S. (2020) A new species of Eucharissa  Westwood (Eucharitidae) from South Africa, with an evaluation of the  importance of pupae for assessing relationships in these ant  parasitoids. Journal of Hymenoptera Research 79, 43–55. https://doi.org/10.3897/jhr.79.56042

Tried to download a formatted reference using either zookeys or zootaxa format (using Firefox) > no result
Screenshots

it does work for Acta Amazonica...

works now - it may be because one of the references was verbatim - when fixed it worked.

@jlpereira seems like there might be an edge case to handle both in the back end and the UI here.  Let's test with response that only returns verbatim.


Hide zoom toolbar icons when time related chart is not opened.

Icons show even when there is no chart opened.

Maybe it would be better to display a disabled state for any inactive tools? Possible benefits:

When elements disappear, new users might wonder "where'd it go? Why it'd disappear?"
It's good for the "chrome" of the UI (the stuff that's always visible) to be  very predictable or stable in position (changes can distract/call attention)
Disabled elements can have a tooltip that helps user grasp "why"


Multi GPU ROCm6 issues, and workarounds

I ran into a series of issues trying to get VLLM stood up on a system with multiple MI210s. I figured I'd document my issues and workarounds so that someone could pick up the baton later, or at least save someone some debugging time later.

Ray will deadlock with multiple AMD GPUs. Ray doesn't officially support AMD GPUs in v2.9; I updated Ray to nightlies (v3.0).

pip uninstall ray
pip install -U "ray[default] @ https://s3-us-west-2.amazonaws.com/ray-wheels/latest/ray-3.0.0.dev0-cp310-cp310-manylinux2014_x86_64.whl"

Something might have changed with how Ray exposes GPUs to workers. Only 1 GPU was exposed to each worker, so torch.cuda.set_device() with anything other than 0 would fail. I tweaked worker.py to always use 0, but I don't think this is a viable long-term fix.

diff --git a/vllm/worker/worker.py b/vllm/worker/worker.py
index c97e82a..a63fbd9 100644
--- a/vllm/worker/worker.py
+++ b/vllm/worker/worker.py
@@ -68,6 +68,7 @@ class Worker:
         self.gpu_cache = None

     def init_model(self) -> None:
+        print(f"***** local_rank {self.local_rank} hit init_model, is_driver: {self.is_driver_worker} *****")
         if self.device_config.device.type == "cuda":
             # torch.distributed.all_reduce does not free the input tensor until
             # the synchronization point. This causes the memory usage to grow
@@ -80,7 +81,9 @@ class Worker:
             # This env var set by Ray causes exceptions with graph building.
             os.environ.pop("NCCL_ASYNC_ERROR_HANDLING", None)
             self.device = torch.device(f"cuda:{self.local_rank}")
-            torch.cuda.set_device(self.device)
+            print(f"***** trying to set dev {self.device} of {torch.cuda.device_count()} is_driver: {self.is_driver_worker} *****")
+            # torch.cuda.set_device(self.device)
+            torch.cuda.set_device(0)

             _check_if_gpu_supports_dtype(self.model_config.dtype)
         else:

@BKitor Have you found any solution for distributed inference? Thank you very much in advance!
Best regards,
Shuyue
June 9th, 2024

Sorry, haven't poked this in a while (lost access to multi-node system).
But for single-node multi-gpu training, the 'mp' distributed_execution_backend has been fairly stable.

Benjamin, I am using single-node multi-GPUs but there is a problem regarding the init_device (https://github.com/vllm-project/vllm/blob/main/vllm/worker/worker.py#L92-L118).
Do you have any idea how to solve it?
Thank you very much, and have a nice day!
2024-06-10 16:36:06,142 INFO worker.py:1568 -- Connecting to existing Ray cluster at address: <IP_ADDRESS>:6379...
2024-06-10 16:36:06,142 INFO worker.py:1586 -- Calling ray.init() again after it has already been called.
INFO 06-10 16:36:06 llm_engine.py:161] Initializing an LLM engine (v0.4.3) with config: model='./save_folder', speculative_config=None, tokenizer='meta-llama/Meta-Llama-3-8B-Instruct', skip_tokenizer_init=False, tokenizer_mode=auto, revision=None, rope_scaling=None, tokenizer_revision=None, trust_remote_code=False, dtype=torch.bfloat16, max_seq_len=8192, download_dir=None, load_format=LoadFormat.AUTO, tensor_parallel_size=2, disable_custom_all_reduce=False, quantization=None, enforce_eager=False, kv_cache_dtype=auto, quantization_param_path=None, device_config=cuda, decoding_config=DecodingConfig(guided_decoding_backend='outlines'), seed=0, served_model_name=./save_folder)
Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-tuned or trained.
(pid=487121) /usr4/ec523/brucejia/.local/lib/python3.10/site-packages/transformers/utils/hub.py:124: FutureWarning: Using `TRANSFORMERS_CACHE` is deprecated and will be removed in v5 of Transformers. Use `HF_HOME` instead.
(pid=487121)   warnings.warn(
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149] Error executing method init_device. This might cause deadlock in distributed execution.
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149] Traceback (most recent call last):
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149]   File "/usr4/ec523/brucejia/.local/lib/python3.10/site-packages/vllm/worker/worker_base.py", line 141, in execute_method
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149]     return executor(*args, **kwargs)
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149]   File "/usr4/ec523/brucejia/.local/lib/python3.10/site-packages/vllm/worker/worker.py", line 106, in init_device
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149]     torch.cuda.set_device(self.device)
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149]   File "/usr4/ec523/brucejia/.local/lib/python3.10/site-packages/torch/cuda/__init__.py", line 399, in set_device
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149]     torch._C._cuda_setDevice(device)
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149] RuntimeError: CUDA error: CUDA-capable device(s) is/are busy or unavailable
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149] CUDA kernel errors might be asynchronously reported at some other API call, so the stacktrace below might be incorrect.
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149] For debugging consider passing CUDA_LAUNCH_BLOCKING=1.
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149] Compile with `TORCH_USE_CUDA_DSA` to enable device-side assertions.
(RayWorkerWrapper pid=487232) ERROR 06-10 16:36:10 worker_base.py:149]

Best regards,
Shuyue
June 10th, 2024

What I'm suggesting is to not use ray.
One of the arguments when instantiating a model is distributed_execution_backend, where the options include 'ray' or 'mp'.
I'm not sure how you're launching your model, you might have to insert distrubted_execution_backend="mp" where you create the llm. i.e. from vllm import LLM; llm = LLM(<whatever your args already are>, distrubted_execution_backend="mp).
Otherwise, some of the provided helper scripts let you specify --distributed-execution-backend on the command line, but this isn't universal to YMYV.

What I'm suggesting is to not use ray. One of the arguments when instantiating a model is distributed_execution_backend, where the options include 'ray' or 'mp'. I'm not sure how you're launching your model, you might have to insert distrubted_execution_backend="mp" where you create the llm. i.e. from vllm import LLM; llm = LLM(<whatever your args already are>, distrubted_execution_backend="mp). Otherwise, some of the provided helper scripts let you specify --distributed-execution-backend on the command line, but this isn't universal to YMYV.

@BKitor Benjamin, it seems that there is no distrubted_execution_backend  argument in LLM: https://github.com/vllm-project/vllm/blob/main/vllm/engine/llm_engine.py.  However, there is one in the AsyncLLMEngine: https://github.com/vllm-project/vllm/blob/main/vllm/engine/async_llm_engine.py, which is for serving.
May I know which vLLM version you are using?
Thank you very much, and have a nice day!
Best regards,
Shuyue
June 10th, 2024

The file you're looking for is args_util.py, and it's present in 0.4.3
https://github.com/vllm-project/vllm/blob/1197e02141df1a7442f21ff6922c98ec0bba153e/vllm/engine/arg_utils.py#L38
On Mon, Jun 10, 2024 at 2:36 PM Shuyue Jia @.***> wrote:

What I'm suggesting is to not use ray. One of the arguments when
instantiating a model is distributed_execution_backend, where the options
include 'ray' or 'mp'. I'm not sure how you're launching your model, you
might have to insert distrubted_execution_backend="mp" where you create
the llm. i.e. from vllm import LLM; llm = LLM(, distrubted_execution_backend="mp). Otherwise, some of the provided
helper scripts let you specify --distributed-execution-backend on the
command line, but this isn't universal to YMYV.
@BKitor https://github.com/BKitor Benjamin, it seems that there is no distrubted_execution_backend
argument in LLM:
https://github.com/vllm-project/vllm/blob/main/vllm/engine/llm_engine.py.
However, there is one in the AsyncLLMEngine:
https://github.com/vllm-project/vllm/blob/main/vllm/engine/async_llm_engine.py,
which is for serving.
May I know which vLLM version you are using?
Thank you very much, and have a nice day!
Best regards,
Shuyue
June 10th, 2024
—
Reply to this email directly, view it on GitHub
https://github.com/vllm-project/vllm/issues/2794#issuecomment-2159324295,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEAZJUXNV36SANY7YRYL5OTZGYL4FAVCNFSM6AAAAABC4X7FNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZGMZDIMRZGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

The file you're looking for is args_util.py, and it's present in 0.4.3 https://github.com/vllm-project/vllm/blob/1197e02141df1a7442f21ff6922c98ec0bba153e/vllm/engine/arg_utils.py#L38
…
On Mon, Jun 10, 2024 at 2:36 PM Shuyue Jia @.> wrote: What I'm suggesting is to not use ray. One of the arguments when instantiating a model is distributed_execution_backend, where the options include 'ray' or 'mp'. I'm not sure how you're launching your model, you might have to insert distrubted_execution_backend="mp" where you create the llm. i.e. from vllm import LLM; llm = LLM(, distrubted_execution_backend="mp). Otherwise, some of the provided helper scripts let you specify --distributed-execution-backend on the command line, but this isn't universal to YMYV. @BKitor https://github.com/BKitor Benjamin, it seems that there is no distrubted_execution_backend argument in LLM: https://github.com/vllm-project/vllm/blob/main/vllm/engine/llm_engine.py. However, there is one in the AsyncLLMEngine: https://github.com/vllm-project/vllm/blob/main/vllm/engine/async_llm_engine.py, which is for serving. May I know which vLLM version you are using? Thank you very much, and have a nice day! Best regards, Shuyue June 10th, 2024 — Reply to this email directly, view it on GitHub <#2794 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEAZJUXNV36SANY7YRYL5OTZGYL4FAVCNFSM6AAAAABC4X7FNGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJZGMZDIMRZGU . You are receiving this because you were mentioned.Message ID: @.>

Thank you very much, Benjamin! It really helps.
Now, my multi-gpu inference can be running smoothly. For other researchers' reference:
I use vLLM 0.4.3: https://github.com/vllm-project/vllm/releases/tag/v0.4.3
llm = LLM(
            model=save_dir,
            tokenizer=model_name,
            dtype='bfloat16',
            distributed_executor_backend="mp",
            tensor_parallel_size=num_gpus_vllm,
            gpu_memory_utilization=gpu_utilization_vllm,
            enable_lora=False,
        )

sampling_params = SamplingParams(
        temperature=0,
        top_p=1,
        max_tokens=max_new_tokens,
        stop=stop_tokens
    )

completions = llm.generate(
            prompts,
            sampling_params,
        )

@BKitor However, the GPU memory cannot be released, except the first-initialized GPU (cuda:0 in my case).
import gc

import torch
from vllm.distributed.parallel_state import destroy_model_parallel

# Delete the llm object and free the memory
destroy_model_parallel()
del llm.llm_engine.model_executor.driver_worker
del llm
gc.collect()
torch.cuda.empty_cache()
print("Successfully delete the llm pipeline and free the GPU memory.")

Do you have suggestions on releasing all the GPUs' memory?
Thank you very much, and have a nice day!
Best regards,
Shuyue
June 11th, 2024

This issue should be closed as the current main branch supports multi-gpu on ROCm 6.1x.


GNU make support

I am new to EMACS and LISP but I would like to learn both. Right now I use EMACS at a basic level.
I would like to add GNU make support to your package. I would welcome any thoughts you have on this.

Just to add to this, bear can be used to generate compile_commands.json - so I think that was what the OP was getting at. This functionality already exists in cmake-ide. I think this can be closed.


Can't load profile in Safari

Describe the bug
I wanted to change my name, so I clicked on "Profile" from the top right menu. The spinner in the top right spun forever and the page never loaded.
To Reproduce
Steps to reproduce the behavior:

Go to the Home Screen
Click on your avatar
Click on 'profile'

Expected behavior
Profile loads
Screenshots

What device are you on?
Macbook, Safari 14.0.3
Additional context
New account, created from Github within the last 15 minutes

Console output when loading the profile in a new tab (some of the console errors in the original screenshot might've been from previous actions)

Lots of text is also appearing backwards in Safari.

Lots of text is also appearing backwards in Safari.

this should be a different issue and also you probably have "Australian English" set as your language


[NT-722] Xcode 11 snapshots

📲 What
Records new snapshots in Xcode 11 and iOS 13.3.
Note: This is based off #1003.
🤔 Why
We use snapshot testing to verify visual changes to our views. Unfortunately Xcode 11 and iOS 13 introduces many changes, some subtle (font anti-aliasing, etc.) and some not-so-subtle (broken constraints, views mis-aligned).
We will need to review all of these snapshots for regressions.
🛠 How

Updated our snapshot testing framework - https://github.com/uber/ios-snapshot-test-case/releases/tag/6.2.0
Updated calls to FBSnapshotVerifyView and removed tolerance values.

We weren't using tolerance in that many places and figured we can add it back if necessary.

Removed some calls to setNeedsLayout() which were causing snapshot tests to get into an infinite loop.
Re-recorded all of our snapshots.

🤷♂ What now?

We're going to have to review all of the snapshots for regressions and create bug tickets to fix them.
We need to perform full regression testing on the app itself and create bug tickets for things that we discover during that process too.

Closing as per our plan to break this up into multiple PRs.


Build fails

[ 43%] Built target pixsfm
Scanning dependencies of target pypixsfm
[ 50%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/base/bindings.cc.o
[ 87%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/features/bindings.cc.o
[ 87%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/util/bindings.cc.o
[ 90%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/localization/bindings.cc.o
[ 90%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/keypoint_adjustment/bindings.cc.o
[ 90%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/residuals/bindings.cc.o
[ 90%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/bundle_adjustment/bindings.cc.o
[ 90%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/pyceres/cost_functions.cc.o
[ 90%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/pyceres/pyceres.cc.o
[ 90%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/pyceres/solver.cc.o
[ 90%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/pyceres/parameterization.cc.o
[ 90%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/pyceres/callbacks.cc.o
[ 90%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/pyceres/loss_functions.cc.o
[ 90%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/pyceres/types.cc.o
[ 90%] Building CXX object pixsfm/CMakeFiles/pypixsfm.dir/pyceres/problem.cc.o
[ 93%] Linking CXX static library libpypixsfm.a
[ 93%] Built target pypixsfm
Scanning dependencies of target _pixsfm
[ 96%] Building CXX object pixsfm/CMakeFiles/_pixsfm.dir/_pixsfm/bindings.cc.o
[100%] Linking CXX shared module ../../../pixsfm/_pixsfm.cpython-38-x86_64-linux-gnu.so
/usr/bin/ld: /usr/local/lib/libceres.a(covariance_impl.cc.o): in function `ceres::internal::CovarianceImpl::GetCovarianceBlockInTangentOrAmbientSpace(double const*, double const*, bool, double*) const':
covariance_impl.cc:(.text+0xa81b): undefined reference to `void Eigen::internal::call_dense_assignment_loop<Eigen::Matrix<double, -1, -1, 1, -1, -1>, Eigen::Matrix<double, -1, -1, 1, -1, -1>, Eigen::internal::assign_op<double, double> >(Eigen::Matrix<double, -1, -1, 1, -1, -1>&, Eigen::Matrix<double, -1, -1, 1, -1, -1> const&, Eigen::internal::assign_op<double, double> const&)'
collect2: error: ld returned 1 exit status
make[2]: *** [pixsfm/CMakeFiles/_pixsfm.dir/build.make:133: ../../pixsfm/_pixsfm.cpython-38-x86_64-linux-gnu.so] Error 1
make[1]: *** [CMakeFiles/Makefile2:403: pixsfm/CMakeFiles/_pixsfm.dir/all] Error 2
make: *** [Makefile:130: all] Error 2
/usr/local/lib/python3.8/dist-packages/setuptools/command/easy_install.py:156: EasyInstallDeprecationWarning: easy_install command is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
/usr/local/lib/python3.8/dist-packages/setuptools/command/install.py:34: SetuptoolsDeprecationWarning: setup.py install is deprecated. Use build and pip and other standards-based tools.
  warnings.warn(
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/home/prajwal.chidananda/pixel-perfect-sfm/setup.py", line 112, in <module>
    setup(
  File "/usr/local/lib/python3.8/dist-packages/setuptools/__init__.py", line 153, in setup
    return distutils.core.setup(**attrs)
  File "/usr/lib/python3.8/distutils/core.py", line 148, in setup
    dist.run_commands()
  File "/usr/lib/python3.8/distutils/dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/usr/local/lib/python3.8/dist-packages/setuptools/command/develop.py", line 34, in run
    self.install_for_development()
  File "/usr/local/lib/python3.8/dist-packages/setuptools/command/develop.py", line 114, in install_for_development
    self.run_command('build_ext')
  File "/usr/lib/python3.8/distutils/cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "/usr/lib/python3.8/distutils/dist.py", line 985, in run_command
    cmd_obj.run()
  File "/home/prajwal.chidananda/pixel-perfect-sfm/setup.py", line 55, in run
    self.build_extension(ext)
  File "/home/prajwal.chidananda/pixel-perfect-sfm/setup.py", line 98, in build_extension
    subprocess.check_call(['cmake', '--build', '.'] + build_args,
  File "/usr/lib/python3.8/subprocess.py", line 364, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--config', 'Release', '--', '-j']' returned non-zero exit status 2.
----------------------------------------

ERROR: Command errored out with exit status 1: /usr/bin/python3 -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/home/prajwal.chidananda/pixel-perfect-sfm/setup.py'"'"'; file='"'"'/home/prajwal.chidananda/pixel-perfect-sfm/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' develop --no-deps Check the logs for full command output.

Is this a known issue?

This is a failure in Ceres, we don't use this function in pixsfm. Is your Eigen install maybe broken? Can you try to rebuild Ceres? What commit are you building with?

For Ceres, can you try for example:
- RUN git checkout $(git describe --tags) # Checkout the latest release
+ RUN git checkout 2.1.0rc2

or some older commits?

Tried the following configurations:

Ceres: 2.1.0rc2, COLMAP: dev - Fails with same error
Ceres: 2.1.0rc1, COLMAP: dev - Ceres fails to build
Ceres: 2.0.0, COLMAP: dev - Fails with same error
Ceres: 2.0.0, COLMAP: 3.6 - pycolmap fails to build

I don't know if this is relevant, but I couldn't help but notice that the function mentioned in the error (GetCovarianceBlockInTangentOrAmbientSpace) is used in this recent COLMAP commit (https://github.com/colmap/colmap/commit/33e26924f950172751f044a89b964129b3728db8)

In your Docker script, you will also need to build pycolmap from source. Do COLMAP and pycolmap build smoothly? does the build only crash for pixsfm?

The reason I didn't explicitly include building pycolmap from source was because it was already included in requirements.txt; In any case, I added this to the Dockerfile and I still get the same error.
 -DBUILD_TESTING=OFF -DBUILD_EXAMPLES=OFF
RUN make -j
RUN make install

# Colmap
WORKDIR /opt
RUN git clone https://github.com/colmap/colmap.git
WORKDIR /opt/colmap
RUN git checkout dev
#RUN git checkout 3.6
#RUN git checkout 3.7
RUN mkdir build
WORKDIR /opt/colmap/build
RUN cmake ..
RUN make -j
RUN make install

# PyColmap
RUN pip3 install --upgrade git+https://github.com/colmap/pycolmap

# PixSfM
WORKDIR /
RUN git clone https://github.com/cvg/pixel-perfect-sfm --recursive
WORKDIR /pixel-perfect-sfm
RUN pip3 install -r requirements.txt
RUN git clone --recursive https://github.com/cvg/Hierarchical-Localization/
WORKDIR /pixel-perfect-sfm/Hierarchical-Localization
RUN pip3 install -e .
WORKDIR /pixel-perfect-sfm
RUN pip3 install -e .

COLMAP and pycolmap build smoothly.
Build only crashes in the last step of building PixSfM

Hi @prajwalchidananda, I had the same problem but could solve it by building libeigen 3.4.0 from source instead of installing libeigen3-dev from the Ubuntu repository (as a step before building ceres-solver):
RUN git clone --depth 1 --branch 3.4.0 https://gitlab.com/libeigen/eigen.git
RUN cd eigen && mkdir build && cd build && cmake .. && make install
My Dockerfile was based on ubuntu:focal instead of nvidia/cuda:11.1.1-cudnn8-devel-ubuntu20.04, but hope this helps in your case, too.

Thanks @vdobro! Your suggestion worked.  -DBUILD_TESTING=OFF -DBUILD_EXAMPLES=OFF
RUN make -j
RUN make install

# Colmap
WORKDIR /opt
RUN git clone https://github.com/colmap/colmap.git
WORKDIR /opt/colmap
RUN git checkout dev
RUN mkdir build
WORKDIR /opt/colmap/build
RUN cmake ..
RUN make -j
RUN make install

# PixSfM
WORKDIR /
RUN git clone https://github.com/cvg/pixel-perfect-sfm --recursive
WORKDIR /pixel-perfect-sfm
RUN pip3 install -r requirements.txt
RUN git clone --recursive https://github.com/cvg/Hierarchical-Localization/
WORKDIR /pixel-perfect-sfm/Hierarchical-Localization
RUN pip3 install -e .
WORKDIR /pixel-perfect-sfm
RUN pip3 install -e .

@Skydes Maybe it should be mentioned somewhere in the instructions that eigen is to be installed from source?

This seems related to Ceres rather than pixsfm. libeigen3-dev installs 3.3.7, which is the minimum version according to the Ceres doc. Perhaps Ceres actually now requires >=3.4?

Actually this was a linking error on our side, thanks for pointing this out @prajwalchidananda!
I pushed a fix to fix-undefined-references.


[#288] upgrade selene codebase to python3.7 with pyupgrade.

Closes #288

Codecov Report

Merging #369 (84aeb41) into master (72044fb) will decrease coverage by 0.02%.
The diff coverage is 25.00%.

@@            Coverage Diff             @@
##           master     #369      +/-   ##
==========================================
- Coverage   61.28%   61.26%   -0.03%
==========================================
  Files          35       35
  Lines        1878     1877       -1
  Branches      115      115
==========================================
- Hits         1151     1150       -1
  Misses        698      698
  Partials       29       29

Impacted Files
Coverage Δ

selene/browsers.py
0.00% <0.00%> (ø)

selene/support/webdriver.py
70.83% <0.00%> (ø)

selene/common/none_object.py
71.42% <100.00%> (-3.58%)
:arrow_down:

Continue to review full report at Codecov.

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


Fix crash when dragging array members in inspector

To fix #57745 - it actually happens with any types, not just Vector2, reproduced on Windows 10 x64 on master branch.
When clicking and dragging, if you move the mouse rapidly enough you can accumulate enough mouse delta to move multiple indexes in one frame, then when the mouse stops moving or moves the other way, the check on line 623 does not return and the child can be inserted out of bounds. Zeroing out the mouse delta if we hit the first or last indexes prevents this.
Submitting as a draft PR because there is probably a smarter way to refactor this whole section.

@groud haven't looked at this too much so not sure exactly how it'd work, but I think it'd ultimately be best to refactor the array editor code to use https://github.com/godotengine/godot/pull/52277, as it's better and doing so would reduce code duplication.

I believe this PR may no longer be needed this the issue it addressed is a duplicate of a now fixed issue?

Fixed in #61282 :)


[FIX] #467 django 1.10 manage.py startup error

see https://github.com/celery/django-celery/issues/462#issuecomment-245531631

thanks!! could you please add test and changlog too?

build is failing

A good idea would be to use python -Wall instead of just python to launch tests in tox.ini. This way, tests will always show django deprecations. And it will be easier to fix them before django releases are out, and the library is outdated.

now it's passed on all django1.10 and failed on all others.
@azmeuk  I tried python -Wall, still fail for none-1.10

@yjmade this is normal, -Wall just displays warnings and deprecations.

builds are still failing

I think there is another error here.
Django 1.10 drops the support of optparse in favor of argparse. But celeryd command use celery.bin.worker function, that returns a optparse Option object in versions 3.1 and 4.0.
There was a bug opened in 2012 but it has been closed and nothing happened.
Two solutions here:

Convince upstream, and make pull requests for celery 3.1 and 4.0 so they use argparse.
Find a workaround so celeryd can use argparse.

I might have a look at the second solution.

@azmeuk, we do have a workaround. Have a look here.
But it's not perfect and this PR aims to improve it.


Mouse hover in dropdown no longer highlights the relation

Another apparent 2.19 regression:
When i want to add an object to a relation, and hover the mouse pointer over the list of available ones, they are no more highlighted blue (or was it yellow?). Used to work fine in 2.18, and was immensely helpful to identify the desired relation.

Thanks for reporting, @DujaOSM. I'll ship a patch out today for this.


Error: File format not supported - when creating dataframe in Node-RED function node

const dfd = require("danfojs-node"); json_data = [     { A: 0.4612, B: 4.28283, C: -1.509, D: -1.1352 },     { A: 0.5112, B: -0.22863, C: -3.39059, D: 1.1632 },     { A: 0.6911, B: -0.82863, C: -1.5059, D: 2.1352 },     { A: 0.4692, B: -1.28863, C: 4.5059, D: 4.1632 }, ]; df = new dfd.DataFrame(json_data); df.print();
This code snippet produces expected result when running with node.js. when running the code with node-red function node it throws an error - "Error: File format not supported".
The issue is described in detail on this thread on the node-red forum.
https://discourse.nodered.org/t/error-while-executing-code-with-function-node/46443

A workaround to the issue is also mentioned on the same thread.
https://discourse.nodered.org/t/error-while-executing-code-with-function-node/46443/7?u=vinaysudani

Thanks for raising this issue and linking a solution.
FIXED: https://github.com/opensource9ja/danfojs/pull/208

Thanks for looking into it and quickly applying it to the source.


Do we need the demo box

At this point all the boxes have been converted except for demo.  We do not seem to be using it much and we are wondering if it is needed.  Can we just shut demo down?


Docker socket group ownership

Describe your changes
Please include a summary of the change, a relevant motivation and context.
Issue ticket number and link

Fixes #(issue)

Checklist before requesting a review

[x] I have performed a self-review of my own code
[x] I have verified that the code builds perfectly fine on my local system
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have verified that my code follows the style already available in the repository
[ ] I have made corresponding changes to the documentation

Using --group 0 together with rootlesskit solves this for both componse and non-compose.