WindowTime will cause datastorage map item return observable that no data

Hi Sir,
let say i set windowTime i set to 10seconds
after 10 seconds
datastorage.getItem(key) is being called and store to observable
and it wont get in to if(!observable) in decorator
so after 10sec
the data is cleared from cache
but it wont retrieve data from API
and stuck there forever until refresh browser
do you have any advice? @menelai

It is normal behavior for windowTime setting in shareReplay. You can try it with simple code:
@Component({
  selector: 'app-root',
  templateUrl: './app.component.html',
  styleUrls: ['./app.component.scss'],
})
export class AppComponent implements OnInit {
  srv = this.http.get('https://jsonplaceholder.typicode.com/todos/1').pipe(
    shareReplay({
      refCount: false,
      windowTime: 1000
    })
  );

  constructor(
    private http: HttpClient,
  ) { }

  ngOnInit(): void {
    this.srv.subscribe(g => {
      console.log('srv1', g);
    });

    setTimeout(() => {
      this.srv.subscribe(g => {
        console.log('srv2', g);
      });
    }, 2000);
  }
}

If you want to refresh your data periodically, you may put interval(10000) into refreshOn setting:
@HttpRequestCache(() => ({
    refreshOn: interval(1000)
  }))
  get(): Observable<any> {
    return this.http.get('https://jsonplaceholder.typicode.com/todos/1');
  }

if using interval from rxjs means it will automatically get data everytime interval hit, in ur example means every second get todo data
is there any possible using the httpcache decorator when it after 10 min, it will expired, it cleared from cache
and let say 20 min later i access same function with same args it will know it expired go to http get todo again?
current httpcache if i set windowtime to 10min, 20min later i access it, it wont going to get data from api, but it will return empty only.

Okay. Try ttl option in v1.2.0, please

and i just aware there are never implemented deleteItem on storages?

You can use your own data storage to delete unnecessary items

ok noted
and i found out everytime i clear cache using refresh by
this.refresh$.next(true);
it will remove reload every ever capture args data
exp: i have list of articles with paginations (page 1 to 6)
everytime i click different pages, it will get service to pull data from api with page parameter
it will cache data each time i visit different pages. (everything until here is correctly worked)
but let say when i refresh on page 2
i found out it will load the data from page 1 till 6 all
so it will hit API 6 times when i update the subject which i send to refreshOn paramenter for decorator
is it intended to be work like that?

Use refCount: true to keep only active subscriptions or use arguments to filter refreshOn

@wilson-young added storage cleaning when refCount is true and subscribers count is zero. in v1.2.2

@wilson-young added storage cleaning when refCount is true and subscribers count is zero. in v1.2.2

thanks alot sir.


TessAPIInit failed. Output: -1

thanks for your resp. The console print "TessAPIInit failed. Output: -1" when I run this project in  version 2019.4.9. Should I install tessract additional in my PC?  Looking forward for your reply,thanks!

Which platform are you building to?
If your tesseract version is printing, your tesseract files are ok (also since it hits this TessBaseAPI.Init api the files should be fine). No need to install it to your PC,
I guess tesseract.TessBaseAPI.Init4 is failing (https://tesseract-ocr.github.io/tessapi/4.0.0/a02186.html#a2be07b4c9449b8cfc43e9c26ee623050) which might happen if your TessData files  mismatch the version of Tesseract, or TessData files are not present, or corrupt or not read/writable
In which case try finding the compatible TessData file or recheck the file paths

Which platform are you building to?
If your tesseract version is printing, your tesseract files are ok (also since it hits this TessBaseAPI.Init api the files should be fine). No need to install it to your PC,
I guess tesseract.TessBaseAPI.Init4 is failing (https://tesseract-ocr.github.io/tessapi/4.0.0/a02186.html#a2be07b4c9449b8cfc43e9c26ee623050) which might happen if your TessData files  mismatch the version of Tesseract, or TessData files are not present, or corrupt or not read/writable
In which case try finding the compatible TessData file or recheck the file paths

Thanks for your reply! I'm going to build it on Windows platform as a test. I found the reson is the project file path contains Chinese characters. Like this project path“ C:\Users\测试\Desktop\tesseract-unity-master” will hit the error above. Thanks again for your reply!

Thanks for your reply! I'm going to build it on Windows platform as a test. I found the reson is the project file path contains Chinese characters. Like this project path“ C:\Users\测试\Desktop\tesseract-unity-master” will hit the error above. Thanks again for your reply!

Hi,
I couldn't add other languages with tesseract 4.1 with android.
Can you please provide the docker file so I can try tesseract 4.0


Add option on map mode to support looking for files in different places

The GCS_HELPER_MAP_EXTRA_PREFIXES option will provide a list of extra
folders where gcs-helper should look for files when running in mapped
mode.
The main goal of this change is to be able to support video files and
caption files in different "folders". This can also be expanded to
change the way video files are organized.

Codecov Report

Merging #5 into master will increase coverage by 0.24%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master       #5      +/-   ##
==========================================
+ Coverage   77.44%   77.68%   +0.24%
==========================================
  Files           5        5
  Lines         235      251      +16
==========================================
+ Hits          182      195      +13
- Misses         48       50       +2
- Partials        5        6       +1

Impacted Files
Coverage Δ

config.go
100% <ø> (ø)
:arrow_up:

map.go
84.74% <80%> (-1.31%)
: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 a5d0db6...03c4176. Read the comment docs.

thanks for this @fsouza !


Fix isLeapYear docs

Hi!
This project looks very promising!
I will definitely give it a try on my projects.
I found a small error in the isLeapYear docs as the function does not take any arguments.

nice

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[FIX] Fixes pysurfer opacity bug

Requires nipy/pysurfer@dd9f3b5 (or newer).
Also, modify site-packages/vtkmodules/qt/__init__.py file and make this change:
# QVTKRWIBase, base class for QVTKRenderWindowInteractor,
# can be altered by the user to "QGLWidget" in case
# of rendering errors (e.g. depth check problems, readGLBuffer
# warnings...)
-QVTKRWIBase = "QWidget"
+QVTKRWIBase = "QGLWidget"

and modify site-packages/tvtk/pyface/ui/qt4/QVTKRenderWindowInteractor.py and make this change:
if PyQtImpl == "PyQt5":
    if QVTKRWIBase == "QGLWidget":
-        try:
-            from PyQt5.QtWidgets import QOpenGLWidget as QGLWidget
-        except:
-            from PyQt5.QtOpenGL import QGLWidget
+       from PyQt5.QtOpenGL import QGLWidget

Make sure you have vtk>=8.2 and pyqt>=5.9.2 installed. Now you shouldn't get weird speckling when plotting with nnplot.plot_fsaverage()!

Codecov Report

Merging #76 into master will decrease coverage by 0.21%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master      #76      +/-   ##
==========================================
- Coverage    63.5%   63.29%   -0.22%
==========================================
  Files          22       22
  Lines        1488     1493       +5
==========================================
  Hits          945      945
- Misses        543      548       +5

Impacted Files
Coverage Δ

netneurotools/plotting.py
7.1% <0%> (-0.18%)
: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 8e02a5c...aed4ed6. Read the comment docs.


chore(FDS-457): [Monorepo] - update build dependencies

Update package dependencies
Dependencies are grouped into different categories depending on their use:

Build, for packages that support package builds
Style, for things that enforce coding style (lint, format, etc)
Test, for testing purposes
Other, dependencies that do not belong to any of the aforementioned categories

Update log

Package
Group
Before
latest
After
Comment

babel/core
build
7.14.3
7.16.12
7.16.12

babel/parser
build
7.14.4
7.16.12
7.16.12

babel/plugin-proposal-class-properties
build
7.13.0
7.16.7
7.16.7

babel/plugin-proposal-export-default-from
build
7.12.13
7.16.7
7.16.7

babel/plugin-proposal-optional-chaining
build
7.14.2
7.16.7
7.16.7

babel/plugin-transform-modules-commonjs
build
7.14.0
7.16.8
7.16.8

babel/plugin-transform-runtime
build
7.14.3
7.16.10
7.16.10

babel/preset-env
build
7.14.4
7.16.11
7.16.11

babel/preset-react
build
7.13.13
7.16.7
7.16.7

bjeco/prettier-config
style
0.1.6

changesets/cli
style
2.17.0
2.20.0
2.20.0

espressive/eslint-config
style
workspace:*

fluentui/react-northstar
build
0.60.1

rollup/plugin-babel
build
5.3.0

rollup/plugin-json
build
4.1.0

rollup/plugin-node-resolve
build
11.2.1
13.1.3
13.1.3

testing-library/dom
test
7.31.2
8.11.3

testing-library/jest-dom
test
5.13.0
5.16.1
5.16.1

testing-library/react
test
11.2.7
12.1.2
12.1.2
read more

testing-library/user-event
test
13.1.9
13.5.0
13.5.0

types/react
typescript
16.8.0
17.0.38

types/react-dom
typescript
16.8.0
17.0.11

typescript-eslint/eslint-plugin
typescript
4.26.0
5.10.1
5.10.1

typescript-eslint/parser
typescript
4.26.0
5.10.1

babel-eslint
style
10.1.0

babel-jest
test
26.6.3
27.4.7
27.4.7
BREAKING

commitizen
style
4.2.4

cz-conventional-changelog
style
3.3.0

danger
style
10.8.0

dotenv
other
8.2.0
14.3.2

eslint
style
7.32.0

eslint-plugin-deprecate
style
0.7.0

eslint-plugin-eslint-comments
style
3.2.0

eslint-plugin-flowtype
style
6.1.0

eslint-plugin-import
style
2.24.2
2.25.4
2.25.4

eslint-plugin-jest
style
24.4.2
26.0.0

This version drops support for @typescript-eslint/eslint-plugin@4, we need to upgrade both read more

eslint-plugin-json-format
style
2.0.1

eslint-plugin-jsx-a11y
style
6.4.1
6.5.1
6.5.1

eslint-plugin-only-error
style
1.0.2

eslint-plugin-react
style
7.26.0
7.28.0

eslint-plugin-react-hooks
style
4.2.0
4.3.0

eslint-plugin-testing-library
style
4.12.4
5.0.4

faker
test
5.5.3
6.6.6
5.5.3
NOT UPDATED: There is no changelog so we do not have a way to assess the update other than try-and-catch

husky
style
1.3.1
7.0.4
1.3.1
NOT UPDATED - The difference in versions is big, we better plan this ahead

identity-obj-proxy
other
3.0.0

jest
test
26.6.3

jest-environment-jsdom-sixteen
test
2.0.0

jest-junit
test
12.1.0
13.0.0
12.3.0
read more

lint-staged
style
10.5.4
12.3.2
10.5.4
NOT UPDATED - The difference in versions is big, we better plan this ahead

normalize.css
build
8.0.1

postcss
build
8.3.0
8.4.5
8.4.5
They are using pnpm now

postcss-url
build
10.1.3

prettier
style
2.3.0
2.5.1

react
other
16.13.1
17.0.2

react-cosmos
other
5.6.7

react-dom
other
16.13.1
17.0.2

react-router
other
5.2.0
6.2.1

react-router-dom
other
5.2.0
6.2.1

react-scripts
other
4.0.3
5.0.0

react-test-renderer
test
16.13.1
17.0.2

Goes hand-in-hand with REACT

resolve-path
build
1.4.0

rollup
build
2.50.6
2.66.1
2.66.1

rollup-plugin-postcss
build
4.0.2

sass
build
1.34.1
1.49.0
1.49.0

typescript
typescript
4.3.2
4.5.5
4.5.5

vercel
build
22.0.1
23.1.2
23.1.2

webpack
build
4.44.1
5.67.0

PR Author Checklist

[ ] PR title adheres to Conventional Commits
[ ] I have finished reviewing the contents of this PR for accuracy
[ ] If needed, I have included a Changeset and it follows Semantic Versioning principles
[ ] I have completed all of the above and have enabled auto-merge for this PR

Messages

:book:
Dangerfile.js does not run when the current branch is chore/FDS-457-update-monorepo-packages

  Generated by :no_entry_sign: dangerJS against e0922076ef9d6ef5af21906137cb6dfb17fcda07

@lordpixel I love the table outlining the changes and having notes. To me it seems like that would be perfect content to keep a record of in a directory as an ADR. What sort of process did you and @odiseo42 come up with for this so we can make sure we are tracking these decisions each month in the same way? I am not sure what to validate here, but this looks great and I think we should track this info in the code with a MD file and consistent process somehow.

@lordpixel I love the table outlining the changes and having notes. To me it seems like that would be perfect content to keep a record of in a directory as an ADR. What sort of process did you and @odiseo42 come up with for this so we can make sure we are tracking these decisions each month in the same way? I am not sure what to validate here, but this looks great and I think we should track this info in the code with a MD file and consistent process somehow.

@brianespinosa Manu and I are having that conversation tomorrow. So this message comes right in time.

@lordpixel I love the table outlining the changes and having notes. To me it seems like that would be perfect content to keep a record of in a directory as an ADR. What sort of process did you and @odiseo42 come up with for this so we can make sure we are tracking these decisions each month in the same way? I am not sure what to validate here, but this looks great and I think we should track this info in the code with a MD file and consistent process somehow.

@brianespinosa There is an md file at the root of the mono-repo, I added its contents to this PR's description just for informative purposes. The plan is to create an ADR document for each month.
Tomorrow, I will meet with @odiseo42 to discuss this and other processes together, we will keep you posted.

@lordpixel is this PR going to come back in another form? I am not seeing a comment as to why this was closed.


KNL-1375 Remova AuthzGroupService cover and refactor code to use ComponentManager

this is pretty awesome. thanks.


[pyOpenSci review] develop plan on whether to put nanoplots code into separate library

From the pyOpenSci comment:
issue (_utils_nanoplots.py): I am a little on the fence about this file. It seems a little out of place, and I would not be surprised if this was extracted in its own package, just like htmltools. It has a LOT of content, its scope is way bigger than other files: data validation, statistic computation, and the actual SVG build. The thousand lines long function seems high maintenance as well.
https://github.com/pyOpenSci/software-submission/issues/202#issuecomment-2480804958

We plan to circle back to this, and have noted it, but I'm going to close here for now.


always giving error in console

I use docker, and I talked to a guy who said that this mod is not dependent on docker, he tried to change some things to make it work but nothing came of it, and when I try to put the address, "network error" always appears
console error image:

network error is due to the inability to communicate with the server because the plugin failed to load.
It seems to be a java environment problem, please provide complete information, such as game version, java version.

game version - 3.3.50
java version - 17.0.5

Did you use the jar file I released or compile it yourself, it looks like a packaging error.

I don't really know, a guy from the grasscutter server shared his folder to use docker

actually i used the most recent yes, this is a screenshot of the error with the original plugin

I will fix this problem when I have time, please pay attention to the update of the plugin project.

Thank you very much :)

The new version probably solves this problem (I'm not sure, I've been too busy lately)
https://github.com/jianxingxuejian/grasscutter-plugin/releases/tag/v1.5.3

It didn't give any more error, but I can't connect, neither by email, nor by admin voucher. It always appears network error or token parse fail, in addition I tried to use the verify command in cmd and this appeared

and when I try to send the command through the game chat, it says "verifyCode mail is not exist"


Johtaylo/cloudadapterstreaming

fixes #4850 #4674

this adds streaming support to cloud adapter
we are only supporting asp core
this does PR does not include the additional unit tests (they are coming)

The most significant code is included in the CloudAdapter class in the integration project. Basically line 126 onwards in that class.
This codes does make some use of the existing streaming SDK integration, specifically StreamingRequestHandler. However, it keeps that dependency internal.
The most significant difference between this implementation and the existing streaming implementation is that all the outbound traffic is actually funneled through an internal HttpClient implementation that abstracts the underlying stream. There was a partial implementation of that idea but it was not wired up nor did it work. This PR does not touch that code.
The existing streaming implementation also performs a token refreshing call (per virtual "request" over the socket) in order to keep the AD registration alive, I've not yet added that.

also fixes https://github.com/microsoft/botbuilder-dotnet/issues/4774

and fixes https://github.com/microsoft/botbuilder-dotnet/issues/4835


Print version info

Can Thor print version info? How? I think I have tried everything I can and google isn't helping.
Thanks for the great gem:-)

I found a way around this delima of mine. May I enter this as a  feature request?
Thank you.

@lebogan can you please elaborate a bit on this?
Are you talking about providing a --version to your application?
If so, you can just add a version command and then map --version.
    map %w[--version -v] => :version

    desc 'version', 'Show version.'
    def version
      ...my version here from MyGem::VERSION/whatever...
    end

I was looking for a way for my apps to print version info and also show "--version -v" as a option when "--help" is requested. After a lot of searching, I came up with this inelegant solution:

Build a throwaway class option for command-line documentation

	class_option :version, :type => :boolean,  :desc => "Show version information"

Catch the option as an argument in the main program:

    if ARGV[0] == "--version"
	  puts "ip_calc version #{IpCalc::VERSION}"
	  exit 0
    end

Like I said, not very elegant. It works but shows a "--no-version" on the help screen. I was looking for a builtin function with Thor.
I will try your suggestion. Thank you very much for the response.
Lewis

That works, it's clean. Thank you again for the response. I'm closing
this issue.
On Tue, 2015-07-28 at 03:33 -0700, Stefano Tortarolo wrote:

@lebogan can you please elaborate a bit on this?
Are you talking about providing a --version to your application?
If so, you can just add a version command and then map --version.
map %w[--version -v] => :version
desc 'version', 'Show version.'
def version
  ...my version here from MyGem::VERSION/whatever...
end

—
Reply to this email directly or view it on GitHub.

@lebogan cool!
By the way, I still see this as open.. :question:


How to set required value on a condition related to select value in another field

How can I set the required field to be conditional on the selection of a value in a select from another field ?
( Show or hide asterisks and validation message depending on the value in the select field )

see https://formly.dev/docs/guide/expression-properties/#1-dynamically-change-field-properties


Fix a typo

Fix a typo.

@alexandair : Thanks for your contribution! The author, @mmacy, has been notified to review your proposed change.

Thanks @alexandair! #sign-off


docker plugin ls

When this plugin is installed correctly, should running docker plugin ls produce anything related to this plugin?

I'm pretty sure it didn't install correctly, because I restarted the database container (after everything was all working), and my app no longer functioned due to missing data.
Is there anyway to diagnose the install?
I received the following message after installation:
sudo curl -fsSL https://raw.githubusercontent.com/CWSpear/local-persist/master/scripts/install.sh | sudo bash -s --
Stopping docker-volume-local-persist service if running

Downloading binary:
  From: https://github.com/CWSpear/local-persist/releases/download/v1.3.0/local-persist-linux-amd64
  To:   /usr/bin/docker-volume-local-persist
Binary download

Downloading Systemd service conf:
  From: https://raw.githubusercontent.com/CWSpear/local-persist/v1.3.0/init/systemd.service
  To:   /etc/systemd/system/docker-volume-local-persist.service
Systemd conf downloaded

Starting docker-volume-local-persist service...
* docker-volume-local-persist.service - docker-volume-local-persist
   Loaded: loaded (/etc/systemd/system/docker-volume-local-persist.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2017-02-23 15:44:33 ACDT; 29ms ago
 Main PID: 8992 (docker-volume-l)
    Tasks: 3
   Memory: 2.4M
      CPU: 5ms
   CGroup: /system.slice/docker-volume-local-persist.service
           `-8992 /usr/bin/docker-volume-local-persist

Feb 23 15:44:33 idearium-common systemd[1]: Started docker-volume-local-persist.
Feb 23 15:44:33 idearium-common docker-volume-local-persist[8992]: Starting...       Found 1 volumes on startup

Done! If you see this message, that should mean everything is installed and is running.

I have a feeling no output relating to this plugin from the command docker plugin ls doesn't really matter. Prior to installing it, I ran a docker-compose up and it complained about a plugin that it didn't know about. After installing it, my containers started fine...
However, the volumes are definitely not being persisted.
Any ideas?

Do you know what?  I had incorrectly mapped my volume, and there had two volumes to the container. The data was being written the standard Docker local plugin, not this one - which works perfectly :)

Glad you figured it out :-)


Implement Checked Typed Elements for state machines

Implement the Check Typed Elements algorithm for state machine semantics.

[x] Compute type options of typed elements
[x] Check types of actions and guards

Done in commit d266d8a52bc54f4ecd82b56d89d14b1f2c608ad5.


HTTP Basic Access Authentication Support

It appears that sync-request does not support basic access authentication. Are there any plans to include this in the future?

Haven't thought about this yet, it's actually just a simple case of setting the correct header though.  i.e.
var optioins = {
  headers: {
    authorization: 'Basic ' + new Buffer(username + ':' + password, 'ascii').toString('base64')
  }
};

If we were going to add it, we would do so by adding it to https://github.com/then/then-request.


does is have a version for Android 4?

does is have a version for Android 4?

No. See #98

well, thanks anyway


backdropBlur not working?

Description
When I try to use the backdropBlur style prop, it doesn't work
Link to Reproduction
https://codesandbox.io/s/elated-bell-668t4?file=/src/index.js
Steps to reproduce
Those props all add the css var --chakra-backdrop-blur: blur(6px) to the element but not background-filter;
backdropBlur="6px"
sx={{ backdropBlur: "6px" }}
__css={{ backdropBlur: "6px" }}

Setting the filter directly worked though.
css={{ backdropFilter: "blur(6px)" }}

Chakra UI Version
1.7.4
Browser
Chrome 96
Operating System

[X] macOS
[ ] Windows
[ ] Linux

Additional Information
The only reference I found of backdropBlur in the documentation was in this changelog https://chakra-ui.com/changelog#17-05-2021
PS: Is there a better way to "transparentize" a color that in my example?
const theme = useTheme();
const bg = transparentize(theme.colors.gray[800], 0.8)(useTheme());

It makes sense, thanks @TimKolberger.

I would like to work on this. Any insights what could be the best place to put this piece of documentation?

@sohamsshah I think the Style Props page would make sense for now. We don't have a section for filters, so this is a good opportunity to expand on it. You can use the Flexbox section as an inspiration:

sx={{
filter: "blur(4px)",
}}
You can use it as above:


Pluggable Name Resolver

I would very much like reqwest to offer me the option of providing my own name-resolver.
We are using DNS for service discovery, and to ensure a balanced load the client should itself send requests evenly across all hosts exposed. I've looked into simply building this into reqwest itself, but I find one problem which is that the way hyper deals with "preferences" assumes that the hosts are given in some priority order from the DNS system. Adding "randomize" or rotate behavior to the name-resolution in reqwest might break other users expectations.
I imagine ClientBuilder could simply have a resolver(resolver: Box<dyn Resolver>) method, and ideally the trust-dns could have an implementation exposed? (That users may wrap and adapt to their expected behavior)
I can probably find some time for a PR, if this is deemed a good idea.

It is useful when using HttpDNS.
How to realize it in reqwest?
Thanks!


[GSSoC'2021] Add DFS in Python

Hello Mentors, I would like to add Depth First Search method algorithm in Python so can you please assign this to me?
@tarun26091999 @shreyanspoddar @nakul-19 @OjusWiZard @raksha009 @rudrakshi99 please mentors assign this to me.

present at #248


Add global option to set number of threads used by xdem/geoutils

Several functios in xdem (or geoutils) implicitly use multiple threads, e.g. Raster.reproject, xdem.terrain.
The multithreading can interfere with multiprocessing when running steps in an embarrassingly parallel way. Currently, there is no easy way to turn off multi-threading. In the case of numba, I don't know even think it is possible to turn it off at all without making changes to the code.

That's probably smart.
If the argument is called say n_threads (with a None default), it could be written as:
n_threads or os.getenv("XDEM_N_THREADS")

Note that this expression makes the keyword argument take precedence over the variable, which might not be what we want. In the numba docs (link below), it's stated that the variable sets the maximum allowed number of threads, while their config system can be used to set anything equal or less than that. I think that's good, as in your case, you want to be absolutely sure that it's not spawning more threads.
Perhaps a slightly more complex helper function in xdem/misc.py along:
def get_n_threads(target_n: int | None = None) -> int:
  """
  Get the number of threads to use for a function.

  The environment variable XDEM_N_THREADS sets the maximum allowed number of threads, if defined.

   :param target_n: The user-/function-set requested amount of threads

  """
  env_threads = os.getenv("XDEM_N_THREADS")
  if target_n is None and env_threads is None:
    return os.cpu_count()  # This might be too much?
  if target_n is None:
    return int(env_threads)

  return min(target_n, int(env_threads))

Numba parallelization is controlled via the parallel=True keyword argument to the njit decorator. It has its own global variable to limit the amount of threads (NUMBA_NUM_THREADS, see their docs). To just turn off parallelization, something like this would work:
@numba.njit(parallel=(int(os.getenv("XDEM_N_THREADS", 2)) > 1))

Meaning that if XDEM_N_THREADS is defined and is larger than 1, it's parallel. If it's equal to one or less, it won't be parallelized. If it's not defined, the expression will evaluate to True.
It might be good to control numba through the variable too, since packages like skgstat use numba but have no custom-made way to specify thread count. We could either handle this functionality ourselves (if the xdem variable is set and numba is not, numba will take the xdem value) or just say "it's a feature, not a bug" and specify somewhere that both variables need to be set!

Wow, thanks for the detailed answer !
A few more comments/questions:

in the get_n_threads function, I would raise a warning if trying to set a value larger than the env variable.
how can we test that this functionality works? Is there a tool to know the max cpus used during a function call?
I was quickly going through numba's documentation on the matter. It seems like we cannot use the env variable in our case, because it is read upon import so we cannot set it during a script. We can use set_num_threads within each function that uses numba. But as you say, for dependencies like scikit-gstat, it might be tricky...
Should we have one variable for geoutils and one for xdem, or share them? I think it would be simpler to have just one, in which case should it be "GEOUTILS_NUM_THREADS"?


ability to change page title "Flyimg Demo" to a custom one

it would be helpful to have a configuration for the page title (so to set it in docker context).
btw, "Flyimg" would be great, current "Flyimg Demo" not so much :)

lovely! thanks!


Disable remove-upload-files-button in "Repository refresh beta"

It's no longer needed there:
Before

After

You can use the previous code and just add “not dropdown-item” to the selector.

Done.

rather change the dropdown to a single button as part of “ unwrap-useless-dropdowns” instead

Why? I like the new style, it doesn't take much space and still provides both options.


feat(cli): autocompletion

Is your feature request related to a problem? Please describe.
Enable clap autocompletion gen: https://docs.rs/clap_complete/latest/clap_complete/
Conditionally compile it, so we don't add to CI time.
Describe the solution you'd like
No response
Describe alternatives you've considered
No response
Additional context
No response

Nevermind, wanted it for risedev, but it doesn't seem to use clap.


Add external link macro for inline svg

What is the context of this PR?
Fixes #835
Adds inline svgs for external links and adds design system forum missing links
How to review

Tests pass
View code
Check all pages and links display correctly
Check that link icon is correct colour when focused on

 Issue #835: Introduce inline SVGs for external links


Instructions on how to manually install WSL without Add-AppPackage

I am trying to manually install WSL without using Add-AppPackage. The reason is that service applications (running either as SYSTEM or as a local user, registered under "Services") can not invoke wsl.exe because of the sandboxing/permission systems that happens for the C:\Program Files\WindowsApps folder / store apps in general. Unfortunately I also need systemd booting capability, so I can not simply using the WSL feature that ships with Windows (it's too old).
To avoid the store app sandboxing, I'm trying to install all the bits of WSL manually with a PowerShell script. Unfortunately I'm stuck on registering COM components - specifically the service server - since store apps have a completely different way of registering their COM components that don't 1:1 align with normal COM registrations. Since there's no source code for WSL, nor debugging symbols on the Microsoft servers, I can't see what interface is missing when I get the following error:
Class not registered
Error code: Wsl/0x80040154

As far as I can tell, the registrations look fine, but since component registration is not documented very well, it's hard to see what I'm missing. I did try installing the WSL feature that ships with Windows, but it apparently doesn't use the same Windows Service/COM architecture that the store version does. This is the script that I've got so far:
(There used to be a PowerShell script here, but I converted it to C#, and it can now be found at: https://src.redpoint.games/redpointgames/rkm/-/blob/wsl-refactor/src/rkm/Components/Windows/WslExtra/WslProvisioningComponent.cs#L156)
Any guidance on what I'm missing here for wsl.exe to work would be appreciated.

So I got somewhat further with this. The latest registration code is now at: https://src.redpoint.games/redpointgames/rkm/-/blob/wsl-refactor/src/rkm/Components/Windows/WslExtra/WslProvisioningComponent.cs#L156
Now, the wslservice.exe crashes with a segmentation fault because it can't find the class {C8F673A8-4BAB-420E-94E3-BFDB19740697} (which is the "toast activated" stuff). This manifests as actually trying to start anything failing:
C:\RKM\thanos-638134278583841364\wsl-runtime>.\wsl -d RKM-Kubernetes-thanos-638134278583841364 -u root
The remote procedure call failed.
Error code: Wsl/Service/RPC_S_CALL_FAILED

According to the event viewer, the component fails to register with DCOM within the required timeout:
The server {C8F673A8-4BAB-420E-94E3-BFDB19740697} did not register with DCOM within the required timeout.

And this is how it's registered:

Running this command manually at the command line doesn't reveal anything interesting; it just exits with exit code 1 and the Process Monitor logs aren't particularly revealing as to what this is doing either:

The toast activator DCOM component also looks fairly sensible in it's registration:

Compared with the store registered version, the only real difference I can see is that the store version has "DefaultThreadingModel = Apartment", but this option doesn't really make sense for LocalServer32 and you can't set it on LocalServer32 registered COM components, so I think this is just a quirk of how OleView is reading store registered LocalServer32 components. They're otherwise identical:

So the sequence of events is currently:

All wsl commands except actually running stuff works.
Trying to run something inside WSL causes wsl.exe to contact the wslservice.exe service running on the local machine.
wslservice.exe tries to use the {C8F673A8-4BAB-420E-94E3-BFDB19740697} DCOM component, which maps to the wslhost.exe -ToastActivated LocalServer32 stuff.
wslhost.exe just exits with exit code 1 and presumably doesn't register itself.
DCOM errors out because the component doesn't register itself.
wslservice.exe crashes due to a null pointer.

Adding further to the mystery, OleView can clearly instantiate the wslhost.exe -ToastActivated component because it does so to get the interface list, and it shows up properly:

And I can see in Process Monitor that wslhost.exe -ToastActivated gets spawned and exits with exit code 0, so why does it fail when wslservice.exe tries to access it???

Oh hmm, when wslservice.exe starts it, it's looking for a different CLSID on startup, and then presumably exits because it can't find whatever it's looking for:

vs OleView where it looks for the right CLSID:

Oh hmm, for my registration, -ToastActivated is somehow picking up the AppID (or the generated AppID?) of the main wslhost.exe registration:

But for the store app, there's no AppID associated with either wslhost.exe or wslhost.exe -ToastActivated, so maybe this changes how the component is launched?

Would you like to explain what you are trying to achieve? The "can not invoke wsl.exe because of the sandboxing/permission systems" statement did not provide any details.

@Biswa96 You can't run wsl.exe from a service running as a local user, because there's no like "store app context" (I'm not sure of the particular term). This causes all of the ACL checks to fail, so the service outright can't even access the wsl.exe binary sitting under C:\Program Files\WindowsApps or activate the WSL service.
You also can't run wsl.exe as a Local System service, presumably for the same permission related reason.
And I'm guessing this ties into why people also can't run wsl.exe from an SSH session (not that that is my use case). Because in all of the cases above, you can't run wsl.exe from session 0. This has been a known issue for the store version since forever, and there's no known (planned?) fix, so this is my attempt at manually installing the WSL components outside of the store app sandboxing/permissions stuff so that it will work from a service.

I tried giving -ToastActivated it's own AppID, but this seemed to make it work less in OleView, and didn't fix the service crash, so I can only guess it's still not registering properly:

I also tried making a copy of wslhost.exe as wslhosttoastactivated.exe to force it to not group the registration, but this also prevented it from loading for OleView and didn't solve the service crashing:

Just to double check everything, I restarted my machine with the latest ("most working") registrations in case DCOM was caching stuff and not detecting the latest registry entries, and it made no difference.
Really not sure what else to check at this point - the configuration is identical to what the store COM components seem to register, and yet it still does not work.

You can't run wsl.exe from a service running as a local user

Can you provide any sample code or project to reproduce the issue? Isn't it possible to use documented WSL APIs?

Not sure what you mean by documented APIs. If the service can't call wsl.exe or start the WSL service then it obviously can't use WSL.
I can get you a sample reproduction tomorrow if it's really necessary, but you can trivially reproduce it with:

Create a .NET background service that can be registered as a Windows service
Add code to use Process.Start to run wsl.exe
Register and run the service
Observe the .NET error in the event viewer because the service is denied access to the wsl.exe binary

@Biswa96 Here is a C# file that reproduces the issue:
// add these package references to your project
//
//    <PackageReference Include="Microsoft.Extensions.Hosting" Version="7.0.0" />
//    <PackageReference Include="Microsoft.Extensions.Hosting.WindowsServices" Version="7.0.0" />
//

using System.Diagnostics;

namespace wslissuerepro
{
        public class Worker : BackgroundService
    {
        private readonly ILogger<Worker> _logger;
        private readonly IHostApplicationLifetime _hostApplicationLifetime;

        public Worker(
            ILogger<Worker> logger,
            IHostApplicationLifetime hostApplicationLifetime)
        {
            _logger = logger;
            _hostApplicationLifetime = hostApplicationLifetime;
        }

        private async Task RunProcessAsync(string[] argumentList, CancellationToken stoppingToken)
        {
            var startInfo = new ProcessStartInfo
            {
                FileName = Path.Combine(Environment.GetEnvironmentVariable("SYSTEMROOT")!, "System32", "wsl.exe"),
                RedirectStandardOutput = true,
                RedirectStandardError = true,
                StandardOutputEncoding = Encoding.Unicode,
                StandardErrorEncoding = Encoding.Unicode,
            };
            foreach (var arg in argumentList)
            {
                startInfo.ArgumentList.Add(arg);
            }
            var process = Process.Start(startInfo);
            var sb = new StringBuilder();
            process!.OutputDataReceived += (sender, args) =>
            {
                if (!string.IsNullOrWhiteSpace(args.Data))
                {
                    sb.AppendLine(args.Data);
                    _logger.LogInformation($"stdout: {args.Data}");
                }
            };
            process.ErrorDataReceived += (sender, args) =>
            {
                if (!string.IsNullOrWhiteSpace(args.Data))
                {
                    _logger.LogInformation($"stderr: {args.Data}");
                }
            };
            process.BeginOutputReadLine();
            process.BeginErrorReadLine();
            await process.WaitForExitAsync();

            _logger.LogInformation($"stdout: {sb}");

            _hostApplicationLifetime.StopApplication();
        }

        protected override async Task ExecuteAsync(CancellationToken stoppingToken)
        {
            //await RunProcessAsync(new[] { "--version" }, stoppingToken);
            await RunProcessAsync(new[] { "--install", "--web-download", "--no-launch", "--no-distribution" }, stoppingToken);

            _hostApplicationLifetime.StopApplication();
        }
    }

    public static class Program
    {
        public static async Task Main(string[] args)
        {
            var builder = Host.CreateDefaultBuilder(args);
            if (OperatingSystem.IsWindows())
            {
                builder = builder.UseWindowsService(options =>
                {
                    options.ServiceName = "WSLIssueRepro";
                });
            }
            IHost host = builder
                .ConfigureServices(services =>
                {
                    services.AddHostedService<Worker>();
                })
                .Build();

            await host.RunAsync();
        }
    }
}

Set the appsettings.json to contain this (so you get Event Viewer logs):
{
  "Logging": {
    "LogLevel": {
      "Default": "Information",
      "Microsoft.Hosting.Lifetime": "Information"
    },
    "EventLog": {
      "SourceName": "WslIssueRepro",
      "LogName": "Application",
      "LogLevel": {
        "Default": "Information",
        "Microsoft": "Information",
        "Microsoft.Hosting.Lifetime": "Information"
      }
    }
  }
}

Build this in VS, you should end up with a folder that looks like this:

Create and start the service from an Administrative command prompt:

When you run this for the first as SYSTEM, you'll get the following standard output:
Downloading: Windows Subsystem for Linux
Installing: Windows Subsystem for Linux

and the following stderr:
The parameter is incorrect.

Then if you run the service again with --version (which should work if WSL was installed correctly), you instead just get the usual "here is the --help since you haven't installed WSL yet" prompt:
Copyright (c) Microsoft Corporation. All rights reserved.
Usage: wsl.exe [Argument]
Arguments:
    --install <Options>
        Install Windows Subsystem for Linux features. If no options are specified,
        the recommended features will be installed along with the default distribution.
        To view the default distribution as well as a list of other valid distributions,
        use 'wsl --list --online'.
        Options:
            --distribution, -d [Argument]
                Specifies the distribution to be downloaded and installed by name.
                Arguments:
                    A valid distribution name (not case sensitive).
                Examples:
                    wsl --install -d Ubuntu
                    wsl --install --distribution Debian
            --inbox
                Install the optional Windows feature instead of the version available via the Microsoft Store.
            --enable-wsl1
                Enable WSL1 support with the Microsoft Store version.
            --no-distribution
                Do not install a distribution (cannot be used with --distribution).
            --no-launch, -n
                Do not launch the distribution after install.
            --web-download
                Download the most recent version of WSL from the internet instead of the Microsoft Store.
    --list, -l [Options]
        Lists distributions.
        Options:
            --online, -o
                Displays a list of available distributions for install with 'wsl --install'.
    --status
        Show the status of Windows Subsystem for Linux.
    --help
        Display usage information.

So, you can not install or use WSL as a SYSTEM service out of the box. Further iterations on this that have the service running as an auto-generated local user also don't work for various reasons that I've already explored, so at this point I'd really just like to get all the COM components installing system-wide so that I don't need to deal with the Windows App Store sandboxing/permission stuff that's going on.

After further debugging of COM, I'm pretty sure it's IPlan9FileSystem that isn't being provided, though as to why that isn't provided I'm not sure yet.

Or it could be WslDeviceHost_VirtioFs? That's the last class that is attempted to retrieve before the actual crash.
Unfortunately COM is so obtuse it's near impossible to debug what's actually failing.

Managed to get some more tracing data out of the COM stuff, with a more clear message:
COM trace: 0x000001311b9ec8e8 L"End CCI clsid:{60285AE6-AAF3-4456-B444-A6C2D0DEDA38} context:1114116 RSN: hr:0x80040154"

In case anyone else needs to do COM tracing in the future, you can get this by setting a breakpoint at this location via the Disassembly:
ComTraceMessageWorker(HRESULT, const char *, const char *, int, TraceLevel, const wchar_t *, char *)
00007FFCA6A76CB4  jne         ComTraceMessageWorker+1BEh (07FFCA6A76D8Ah)

And configuring the breakpoint with the action to print out the value "COM trace: {current}" and enabling "Continue code execution".

Though I've no idea why it thinks it's not registered; it clearly is according to OleView:

(this screenshot is with me trying to turn off the AppIDs associated with the component, though it made no difference either way)

Bizarrely, even when I register my own implementation of the interfaces with a .NET DLL, I still get "Class not registered" from wslservice.exe, which just makes no sense at all.

The only other real hint I have for any of this, is this line:
COM trace: 0x000001ff58202898 L"Must be called before CoInitializeSecurity"
onecore\vm\dv\host\lib\virtualmachine.cpp(126)\vmdevicehost.dll!00007FFC69A15BAF: (caller: 00007FFC69A14CB0) LogHr(1) tid(7264) 80010119 Security must be initialized before any interfaces are marshalled or unmarshalled. It cannot be changed once initialized.
    Msg:[COM security already initialized]

But this seems completely unrelated to the component it apparently can't find.

Well at this point I think I've exhausted all avenues of diagnosing this issue, and until someone from Microsoft can chime in with the details of how these COM components are registered and what they're expecting here, I'm not sure I'm going to be able to get any further.

Going back to the original question - Why is using Add-Appxpackage not an option?

@benhillis It doesn't work from a service context; when a service (running as either SYSTEM or a user account) invokes that PowerShell command, it just fails.

Yeah the Windows Feature version works fine from a service, but since that's not being updated any more and doesn't support systemd, it's not suitable for my use case and I need to use the binaries from the Store edition instead.

@hach-que If you don't want to use add-appxpackage for WSL installation, would this work for you?
wsl --install -d Ubuntu-20.04 --web-download

@aki-k No, that uses the MSIX bundle under the hood, so it doesn't work for the same reason that Add-Appxpackage doesn't.

Can someone on the WSL team provide the required info to get this working, or alternatively provide an ETA on when the .appx will be installable from service? This currently blocks running Linux containers on Windows hosts for Kubernetes.

Late, but have you tried (1) renaming the .appx to .zip and (2) extracting it? You'll find 2 .appx files similarly named inside the zip file distinguished by supported OS ("x64" and "ARM" I believe).
Repeat steps 1 & 2 into a folder at some level of your $home directory (to avoid permissions issues), and you'll reach a plain old <distro-name>.exe.

[!warning]
I have not tested this myself.

Late, but have you tried (1) renaming the .appx to .zip and (2) extracting it? You'll find 2 .appx files similarly named inside the zip file distinguished by supported OS ("x64" and "ARM" I believe).
Repeat steps 1 & 2 into a folder at some level of your $home directory (to avoid permissions issues), and you'll reach a plain old <distro-name>.exe.

That won't install any of the necessary COM components.


jq: use --disable-maintainer-mode

This avoids the need to install bison 3
Signed-off-by: Adrien Gallouët<EMAIL_ADDRESS>Please fill out the template.
Read: https://k1ss.org/wiki/kiss/style-guide

Description of package
Installed manifest of package
(kiss manifest <pkg>)
MANIFEST HERE

New package

[ ] Latest upstream version.
[ ] I agree to maintain this package.
[ ] I agree to notify @dylanaraps if I can no longer maintain this package.

Existing package

[ ] I am the maintainer of this package.

Only the maintainer of a package can push changes. Open an issue here mentioning the maintainer or send them an email and they'll make the change.
-> kiss maintainer jq
=> /home/dylan/projects/community/community/jq
Aaron G<EMAIL_ADDRESS>
@aaronNGi

@angt: I added it.

Thanks 👍


suzuki miyaura fails

chemnlp/data/tabular/suzuki_miyaura_sach$ python transform.py
Traceback (most recent call last):
  File "transform.py", line 224, in <module>
    get_and_transform_data()
  File "transform.py", line 202, in get_and_transform_data
    df = add_molecules_and_rxn_smiles_to_df(df)
  File "transform.py", line 151, in add_molecules_and_rxn_smiles_to_df
    df["ligand_SMILES"] = df.Ligand_Short_Hand.apply(
  File "/admin/home-micpie/miniconda3/envs/chemnlp/lib/python3.8/site-packages/pandas/core/series.py", line 4630, in apply
    return SeriesApply(self, func, convert_dtype, args, kwargs).apply()
  File "/admin/home-micpie/miniconda3/envs/chemnlp/lib/python3.8/site-packages/pandas/core/apply.py", line 1025, in apply
    return self.apply_standard()
  File "/admin/home-micpie/miniconda3/envs/chemnlp/lib/python3.8/site-packages/pandas/core/apply.py", line 1076, in apply_standard
    mapped = lib.map_infer(
  File "pandas/_libs/lib.pyx", line 2834, in pandas._libs.lib.map_infer
  File "transform.py", line 152, in <lambda>
    lambda molecule: canonicalize_smiles(ligand_smiles_dict[molecule])
KeyError: nan

cannot reproduce the issue with clean cache
https://app.warp.dev/block/3uSHqpQKpBttQmjbiiLhrg

put perhaps this is due to different handling of nan/None in different pandas versions? I use pandas==1.5.2

fixed in https://github.com/OpenBioML/chemnlp/commit/98132b33e78d4c1d99f83554ef6daa1f02a75349


use the specified port and not a ramdom port in range[port,highest port]

What kind of change does this PR introduce? (check at least one)

[ x] Bugfix
[ ] Feature
[ ] Code style update
[ ] Refactor
[ ] Docs
[ ] Underlying tools
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

Other information:
This PR allow to fix the port running "vue serve" related in https://stackoverflow.com/questions/57536785/vue-npm-run-serve-starts-on-random-port
portfinder give a ramdom port in the range [basePort,highestPort], so asking for port 8080 result to a random port between [8080 and 40000]

I think it is an issue with portfinder and should be fixed there.
This PR has problem - if selected port is busy, dev build would throw an error instead of selecting new port.

hi @AndreasCag
There is an issue about the recent behaviour change in 1.0.22
https://github.com/http-party/node-portfinder/issues/84
Sure you are right if the port is used, serve will fails.
But as option --port (or env PORT) specify a port not a range of port, so it seems strange to ask for a port and another is chosen. Maybe it could be better to extend the option to specified a range ?
Best Regards,
Michel.

@AndreasCag The issue is not really in portfinder, vue-cli is relying on portfinder to try ports in ascending order, but the portfinder documentation doesn't specify the order in which ports are tried, so it is a bit foolish for vue-cli to rely on this undocumented behavior. Of course it is also foolish for portfinder to change this behavior in a minor bugfix release, I'm sure this will break a lot of other packages that also rely on the old behavior.
@mpromonet I agree that it seems strange that vue-cli chooses a different port if the specified port is used, but that seems to be the desired behavior, otherwise it would be pointless to use portfinder at all.

There is a fix for this out for review in portfinder:
https://github.com/http-party/node-portfinder/pull/86

@AndreasCag The issue is not really in portfinder, vue-cli is relying on portfinder to try ports in ascending order, but the portfinder documentation doesn't specify the order in which ports are tried, so it is a bit foolish for vue-cli to rely on this undocumented behavior. Of course it is also foolish for portfinder to change this behavior in a minor bugfix release, I'm sure this will break a lot of other packages that also rely on the old behavior.

But it actually does specify that it will do that:
https://github.com/http-party/node-portfinder/blob/master/README.md

By default portfinder will start searching from 8000 and scan until maximum port number (40000) is reached. 40000 is the highest safe port across platforms. If you are not on OSX, you can safely override the max port up to 65535.

@therealshark Oops, I missed that. Thanks for pointing it out.

Closing this now that portfinder has fixed their bug.


HBASE-24205 - Avoid metric collection for flushes and compactions

Avoid collecting the metrics for flushes and compactions.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
1m 43s
Docker mode activated.

Pushed to master.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
4m 12s
the patch passed

+1 :green_heart:
compile
1m 10s
the patch passed

+1 :green_heart:
javac
1m 10s
the patch passed

+1 :green_heart:
shadedjars
6m 12s
patch has no errors when building our shaded downstream artifacts.

-0 :warning:
javadoc
0m 42s
hbase-server in the patch failed.

_ Other Tests _

+1 :green_heart:
unit
134m  0s
hbase-server in the patch passed.

164m 37s

Subsystem
Report/Notes

Docker
Client=19.03.11 Server=19.03.11 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1918/1/artifact/yetus-jdk11-hadoop3-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1918

Optional Tests
javac javadoc unit shadedjars compile

uname
Linux eb188c00d15b 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / 510aad3125

Default Java
2020-01-14

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1918/1/artifact/yetus-jdk11-hadoop3-check/output/branch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1918/1/artifact/yetus-jdk11-hadoop3-check/output/patch-javadoc-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1918/1/testReport/

Max. process+thread count
4285 (vs. ulimit of 12500)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1918/1/console

versions
git=2.17.1 maven=(cecedd343002696d0abb50b32b541b8a6ba2883f)

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

This message was automatically generated.


CommitableSource consumer routed via FlexiFlow producer seemed to disconnect after awhile.

User reported via Gitter that their code gets disconnected after a period of time and eventually everything stops; the StreamSupervisor stops everything and it doesn't recover.
The logs are:
%6|1631044923.925|FAIL|my-app#consumer-8| [thrd:sasl_ssl://[REDACTED]:9092/7]: sasl_ssl://[REDACTED]:9092/7: Disconnected (after 2670559ms in state UP)

Sending failure to [akka://my-app/user/StreamSupervisor-0/$$d#539697147]. Error: Confluent.Kafka.KafkaException: sasl_ssl://[REDACTED]:9092/7: Disconnected (after 2670559ms in state UP)

"Received Stop from [akka://my-app/user/StreamSupervisor-0/$$d#539697147], stopping","@i":"db903a45","@l":"Debug","Message":"Received Stop from [akka://my-app/user/StreamSupervisor-0/$$d#539697147], stopping","Thread":"0007","LogSource":"akka://my-app/system/kafka-consumer-5","Timestamp":"2021-09-07T20:02:03.9997609Z","ActorPath":"akka://my-app/system/kafka-consumer-5","SourceContext":"Akka.Streams.Kafka.Stages.Consumers.Actors.KafkaConsumerActor`2[[System.Byte[], System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e],[System.Byte[], System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e]]"

From chat:

my consumer is basically a KafkaConsumer.CommittableSource that eventually produces messages using the KafkaProducer.FlexiFlow<byte[], byte[], ICommittableOffset>( producerSettings) and finally committing the offset with Committer.Sink(committerSettings)

Consumer config:
var consumerConfig = new ConsumerConfig
{
    EnableAutoCommit = true,
    EnableAutoOffsetStore = false,
    AllowAutoCreateTopics = true,
    AutoOffsetReset = AutoOffsetReset.Latest,
    ClientId = _streamingConfig.ConsumerId,
    SecurityProtocol = _streamingConfig.SecurityProtocol,
    SaslMechanism = _streamingConfig.SaslMechanism,
    SaslUsername = _streamingConfig.SaslUsername,
    SaslPassword = _streamingConfig.SaslPassword,
    SocketKeepaliveEnable = true,
    ConnectionsMaxIdleMs = 180000
};

Stream setup:
var runnableGraph = KafkaConsumer
    .CommittableSource(consumerSettings,Subscriptions.Topics(
        _streamingConfig.InboundDeviceEventsTopic,
        _streamingConfig.InboundDeviceManagerEventsTopic,
        _streamingConfig.InternalEventsTopic))
    .Via(deserialize)
    .Via(mapAndPersist)
    .Via(preProcessForPublishing)
    // Produces the message to the indicated topic using the envelope created in the previous stage
    .Via(KafkaProducer.FlexiFlow<byte[], byte[], ICommittableOffset>(producerSettings))
    .Select(GetCommittable)
    .ToMaterialized(Committer.Sink(committerSettings), Keep.Both)
    .MapMaterializedValue(t1 =>
        DrainingControl<NotUsed>.Create(t1.Item1, t1.Item2.ContinueWith((t2) =>
        {
            // Exceptions in the stream show up here. If you don't catch it here, it gets swallowed up
            if (t2.Exception != null)
            {
                _logger.Fatal(t2.Exception, "Stream shutdown unexpectedly");

                // If no connection could be made to kafka, throw exception to trigger a retry
                if (t2.Exception.GetBaseException() is KafkaException exception)
                    throw exception;
            }
            return NotUsed.Instance;
        }, token)));

 _drainingControl = runnableGraph.Run(_materializer);
await _drainingControl.StreamCompletion;

To add more context to the issue, I also tried this, following some of the recommendations from the Alpakka documentation on error handling:
                 var source = RestartSource.OnFailuresWithBackoff(() =>
                        {
                            var deserialize = Flow.Create<CommittableMessage<byte[], byte[]>>()
                                .Select(message => _messageStreamDeserializer.Deserialize(message));

                            var mapAndPersist = (Flow<DeserializedMessage, ProcessedResult, NotUsed>)Flow
                                .Create<DeserializedMessage>()
                                .GroupBy(_streamingConfig.Parallelism,
                                    message => consistentHash.NodeFor(message.CommittableOffset.Offset.Topic +
                                                                      message.ConsumeResult.Partition.Value))
                                .SelectAsync(1, message => _messageStreamRouter.RouteAsync(message))
                                .MergeSubstreams();

                            var preProcessForPublishing = Flow.Create<ProcessedResult>()
                                .Select(result => _messageStreamSerializer.Serialize(result));

                            var runnableGraph = KafkaConsumer.CommittableSource(consumerSettings,
                                    Subscriptions.Topics(_streamingConfig.InboundDeviceEventsTopic,
                                        _streamingConfig.InboundDeviceManagerEventsTopic,
                                        _streamingConfig.InternalEventsTopic))
                                .Via(deserialize)
                                .Via(mapAndPersist)
                                .Via(preProcessForPublishing)
                                // Produces the message to the indicated topic using the envelope created in the previous stage
                                .Via(KafkaProducer.FlexiFlow<byte[], byte[], ICommittableOffset>(
                                    producerSettings))
                                .Select(GetCommittable)
                                .MapMaterializedValue(control => _control.GetAndSet(control))
                                .Via(Flow.Create<ICommittable>());

                            return runnableGraph;
                        }, TimeSpan.FromMilliseconds(500), TimeSpan.FromSeconds(2), 0.2)
                        .RunWith(Committer.Sink(committerSettings), _materializer);

                    await _control.Value.DrainAndShutdown(source.ContinueWith(t2 =>
                    {
                        // Exceptions in the stream show up here. If you don't catch it here, it gets swallowed up
                        if (t2.Exception != null)
                        {
                            _logger.Fatal(t2.Exception, "Stream shutdown unexpectedly");

                            // If no connection could be made to kafka, throw exception to trigger a retry
                            if (t2.Exception.GetBaseException() is KafkaException exception)
                                throw exception;
                        }

                        return NotUsed.Instance;
                    }, token));
                }, cancellationToken);

After a long period of time of inactivity, I see this log:
%6|1632468039.856|FAIL|uis-cce-outbound#consumer-2| [thrd:GroupCoordinator]: GroupCoordinator: b9-pkc-lgwgm.eastus2.azure.confluent.cloud:9092: Disconnected (after 52712415ms in state UP)

Created a relatively simple reproduction for the first one of your graphs here: https://github.com/Aaronontheweb/Akka.Streams.Kafka.Reproduction
Was not able to reproduce the hang locally. Going to try breaking it down using Substreams (GroupBy) and see how this might impact things.

https://github.com/Aaronontheweb/Akka.Streams.Kafka.Reproduction/blob/c5c7139b4bcd5cf00d1c680807e6f67b32f55b1a/src/Akka.Streams.Kafka.Reproduction.Consumer/Program.cs#L25-L73
Added some telemetry that runs out of band - measures about 60-70 msg/s running everything serially. That sounds about right when using a 10ms delay with degree of parallelism == 1

If my substreams spec still works locally, going to try this on Confluent Cloud next.

Once I take the SelectAsync off I'm doing over 1000 msg/s - can't measure higher than that because that's the max value I set on my GroupedWithin operation - so that's a pretty good indicator that the underlying stages FlexiFlow and Commiter.Sink are fundamentally healthy, provided that I didn't code anything incorrectly in my sample.
Not getting any backpressure alerts either - set a 500ms threshold which is plenty, and in fact might be too large, but the numbers look good.

Added a SubStream sample here:
https://github.com/Aaronontheweb/Akka.Streams.Kafka.Reproduction/blob/b9eb1495775b5dd5d86abace70b4d978228319f8/src/Akka.Streams.Kafka.Reproduction.SubstreamConsumer/Program.cs#L51-L78
Ran at exactly the same throughput as the original implementation - about 60-70 msg/s. No issues and no backpressure recorded.

Found the problem here - it's in the consumer stages:
https://github.com/akkadotnet/Akka.Streams.Kafka/blob/2c73f3ed549ab38020ccdfe4d3b55cef152f9ea8/src/Akka.Streams.Kafka/Stages/Consumers/Abstract/BaseSingleSourceLogic.cs#L147-L161
The Pump method gets run before the broker assigns any topic partitions to the consumer and deadlocks the process, since RequestMessages never gets called under this scenario.
I think this should be a straightforward fix.

Changing this
AutoOffsetReset = AutoOffsetReset.Latest,

to
AutoOffsetReset = AutoOffsetReset.Earliest,

Fixed the problem on my end after making some other small changes. Let me try running this with the producer active using AutoOffsetReset.Latest

Yep, have the latter now working just fine when the producer is active. I did make some changes to the message polling code in my sample. Let me see if that affects this also.


Plugin overwrites theme thumbnail setting of box-big-image.tpl

If you use customer thumbnail settings webp plugin overwrites it.
In custom/plugins/FroshWebP/Resources/views/frontend/listing/product-box/box-big-image.tpl {$sArticle.image.thumbnails[1].sourceSet} is set. This overwrites custom theme settings like {$sArticle.image.thumbnails[5].sourceSet}
It would be helpfull if blocks integrated in webp plugin, so that tpl settings can be overwritten.

You can override the same blocks again in your Theme / plugin


sonar

🙋 Feature Request
https://docs.sonarqube.org/latest/analysis/scan/sonarscanner/

https://github.com/Andreasdahlberg/CANDrive/blob/main/sonar-project.properties


feat: introduce styles for skeletons

This PR adds a new section for skeletons, starting with styling for all imgs, and then h1s and ps that have the .h1-skeleton and .p-skeleton classes added to them respectively.
When an element has the .skeleton class applied, it will by default have a skeleton animation attached during its :empty state. This component does not exist in Bootstrap by default. All imgs will have the animation added when loading, because that qualifies as an :empty state.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Bump up golang to 1.20

What is the areas you would like to add the new feature to?
Notation CLI
Is your feature request related to a problem?
Go 1.20 is released with release notes!
What solution do you propose?
It is time to bump up golang version to 1.20 by updating

go. mod
GitHub Actions
Dockerfile

What alternatives have you considered?
N/A
Any additional context?
No response

Can I take this up? Is there anything else that is required apart from the three points mentioned?


Adding topological sort Graph code in JavaScript

💥 Proposal
I saw a lot of code missing in the JavaScript section, I happen to have just learned JS would like to try and implement it
in this particular issue I would like to work on topological sort

Greetings sir/Mam,
I would like to contribute the code for Bubble Sort Algorithm #933 in C++/CPP.
The code is ready. I have added the code , along with proper explanation of the algorithm , test cases , time complexity and space complexity of the same, as per the guidelines.
Kindly assign it to me.
This is regarding GSSOC'21.
Regards,
Hitain Kakkar

/assign


Safely configure datastore request in the same method

Use the same _configure_datastore(...) method to configure datastore properties

Nice refactor. LGTM

Without this, i've seen the tests occasionally fail in CI like this:
https://github.com/canonical/k8s-operator/actions/runs/8834631143/job/24269710706#step:21:1625


[Enhancement]

PDF Blind XSS payloads
https://portswigger.net/research/portable-data-exfiltration

Thanks @0xspade I'll add them!

Congratulations! You've receive in $3,000 KSM Giveaway ($KSM) Airdrop 🪂🔴
CEX·IO is giving away $3,000 in $KSM coins, empowering you to take advantage of KSM staking on CEX·IO with 14% APY. Join the giveaway and earn a chance to win up to $500. Stake Kusama with CEX·IO, get high rewards and win prizes!
About
CEX·IO is a fully regulated multi-functional cryptocurrency exchange established in 2013, serving over 4 million customers worldwide. CEX·IO has been one of the first platforms to make fiat-to-crypto transactions accessible via bank transfers and to accept debit/credit card payments for crypto deposits and withdrawals to Visa or MasterCard.
→ How to join the $3,000 KSM Giveaway Airdrop?
Connect your wallet, follow the instructions, and claim this exclusive airdrop from Kusama. For GitHub users only—share with friends to make it eligible. Redeem your reward first.

Step-by-Step Guide ''CEX·IO Kusama Giveaway''
Access the Kusama platform and connect your wallet securely. Ensure you're using a trusted wallet for the transaction.

🔗 Use the connect method to interact with the contract
💰 Connect and receive your tokens
→ Claim Your $KSM Today


Code optimization suggestions

Hi,
I find that the private field DEFAULT_LOG_LISTENER at Line 38 in the file 'rest-assured/rest-assured/src/main/java/io/restassured/config/FailureConfig.java ' on the master branch is only assigned and used in the method FailureConfig. Therefore, this field can be removed from the class, and become a local variable in the method FailureConfig. This transformation will normally reduce memory usage and improve readability of your code.I will be happy if this transformation is helpful.
private static ResponseValidationFailureListener DEFAULT_LOG_LISTENER = new LogRequestAndResponseOnFailListener(); // line 38 this field can be replaced by local variable

 private FailureConfig(List<ResponseValidationFailureListener> failureListeners, boolean isUserConfigured) {
        this.isUserConfigured = isUserConfigured;
        this.failureListeners = new ArrayList<ResponseValidationFailureListener>();
        this.failureListeners.addAll(failureListeners);
   	// ResponseValidationFailureListener DEFAULT_LOG_LISTENER = new LogRequestAndResponseOnFailListener();
        this.failureListeners.add(DEFAULT_LOG_LISTENER);
    }

Yes, but I think he wants to put everything that is considered as DEFAUL value/reference in the top of the file to make source code look neat and organized. You can see the same pattern in other files as well.


File Sel's file list should use no round size mode

Right now, the FileSel scaling behaves in a strange way. To overcome this issue NoRoundSize mode for file list should be enable.

IDK, for me it behaved strange before NoRoundSize... that is why it is there right?


Update dependencies

This is a minor update, I just want to run the CI with latest Trino, 449.

The integration tests use a copy of the jvm.config file, which requires -XX:+UnlockDiagnosticVMOptions -XX:G1NumCollectionsKeepPinned=10000000 in the latest version. I think we should wait for the next Trino release, where the base image will get updated to Java 22.0.2


Task 13 with workbook activities

@swathinelakurthi  could you please verify the modified changes.

@07Deekshitha
Task13: Changes verified.


[Android] load page failed in 5.1.1&5.1, where weex version is 0.24.0

Describe the bug
If we have an emoji in code,it cannot be loaded properly in 5.1.1&5.1.
Code

Environment

Device: vivo Xplay5A
OS: Android 5.1.1

Stacktrace
degradeToH5|createInstance fail|wx_create_instance_error[WXBridgeManager]
Addition
Exception when executing WXBridgeManger.invokeCreateInstanceContext

Please follow the issue template and provide the demo in dot.we, a screenshot is not enough.
Feel free to reopen the issue as I only response to issues that are open.

http://dotwe.org/vue/7568b4c5615864967bfc5e22b6808b16
@YorkShen It is the demo ref. It run failed both in my App and Weex Playground


Additional RPC for dumping all main storage key pairs under a prefix

Isn't that a duplicate of https://github.com/paritytech/substrate/pull/4718 ?

Without paging, this can easily causing trouble when someone want to request the whole state.
I think this should be a follow up of #4718 to introduce a variant that also return values along with keys.

Agree with @xlc, the output would be huge and can easily kill the node. Perhaps we could put such things to a separate debug namespace and only allow them to be exposed over localhost. Even though I feel that we should not endorse developers to use them for building UIs or dapps, cause I feel it will backfire in the (near) future.

This isn't designed for general use. This was a piece of functionality I actually needed in order to properly generate a migration test and that I could conceivably need again. I could have alternatively placed an additional CLI mode, but this is quite a lot lighter weight. Introducing paging would have resulted in more complex, less optimal code with a greater amount of effort on the part of the user (i.e. me) in driving it as I would have had to faff around scripting it to fetch and merge all pages.
Refusing to include a useful RPC just because it might conceivably be misused is dumb. We're not creating children's toys here. Of course if it turns out to be too great a foot-gun, then it can perhaps be hidden behind a --expensive-rpcs flag or something, but that's its own issue.

Isn't that a duplicate of #4718 ?

No. Quite the opposite, in fact.

I guess this will be another "unsafe" RPC to be exposed publicly. Some docs here? https://github.com/paritytech/substrate/wiki/Public-RPC

Refusing to include a useful RPC just because it might conceivably be misused is dumb. We're not creating children's toys here. It is not the job of developers to second-guess the RPC-user and force them to jump through hoops of tiny RPC calls in order to allow them to do their job.

Sure thing, I didn't try to block the functionality, but proposed two alternative solutions that would make it less of a footgun (or easier to communicate that it's unsafe):

Either paged approach (like `getKeysPaged)
Or separate namespace (debug_)

If we include it in current form we will in future either have to deprecate it and ask everyone to move or have inconsistent set of APIs within a namespace depending on a particular flag (filtering the entire namespace is easier and I think more clear regarding safeness/unsafeness).

Either paged approach (like `getKeysPaged)

As I explained above, I do not consider that an option.
I'm ok with the idea of prefixing it with unstable_, expensive_ or some other label indicative of its use or that it may yet change.

I guess this will be another "unsafe" RPC to be exposed publicly. Some docs here (when this is merged)? https://github.com/paritytech/substrate/wiki/Public-RPC

Done.


Add autocast test cases

Add autocast test cases.
issue report:
new featrue:
https://github.com/intel/torch-xpu-ops/issues/223

@EikanWang  It is device agnostic case? Do we need? I assume XPU implementation of ATen won't break autocast architecture. Just like we don't need XPU runtime cases in the repo.
What's your opinion?

@EikanWang It is device agnostic case? Do we need? I assume XPU implementation of ATen won't break autocast architecture. Just like we don't need XPU runtime cases in the repo. What's your opinion?

Reviewed. The case tests with autocast(XPU). It is hard-coded for XPU test.


tabindex, keydown handler and role for a11y

Linked Issue
Closes #2163
Description
I am unsure if these comments relate to the issue so i kept this as a draft for the moment.
<!-- FIXME: resolve a11y warnings -->
<!-- svelte-ignore a11y-no-static-element-interactions -->

I chose role of button as researching how similar functionality was handled, such as:
https://www.perkins.org/
And this article:
https://betterprogramming.pub/how-to-turn-a-div-into-an-accessible-button-in-react-fbf236283d6d
Checklist
Please read and apply all contribution requirements.

[x] This PR targets the dev branch (NEVER master)
[ ] Documentation reflects all relevant changes
[x] Branch is prefixed with: docs/, feat/, chore/, bugfix/
[ ] Ensure Svelte and Typescript linting is current - run pnpm check
[ ] Ensure Prettier linting is current - run pnpm format
[ ] All test cases are passing - run pnpm test
[ ] Includes a changeset (if relevant; see above)

@aaroncrockett looks like linting failed in the deployment. Can you please verify?

@aaroncrockett make sure to keep the PR template in place here on GitHub. The standardization helps. I've updated your post and restored this for you. Also per the checkboxes - those are actual interactive elements, just tap them to check items off.
Per the changes itself, I've followed up with some minor changes.

I've removed the comment that suppressed the a11y warning. Related to: https://github.com/skeletonlabs/skeleton/issues/1708
I've gone ahead and made the div a button, let's call a duck a duck here.
Changing this caused a type error for the onKeyDown function, so I've resolved that
Buttons width collapses by default, so I had to set w-full to resolve a visual bug

All in all this is working great. Feel free to double check, and if you're please bump up to "ready for review" and I'll merge right away.
Thank you sir!

@endigo9740  Checking in with an update -- I will be able to look at this again this week probably -- before Friday.

Hey @aaroncrockett I've had a chance to review this. The implementation looks to be good, but one issue - you've indicated it's part of create-skeleton-app (the Skeleton CLI app). Go ahead and remove the current changeset and generate again. The Changeset tool should actually make a suggestion based on what project has been modified:

You'll want to choose that first option at the top.

Just making a note to myself: the changeset looks to be updated, this should be clear to merge. ETA will be tomorrow.


fix: vulnerable

:tada: This PR is included in version 1.1.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


perf: change expensive usage of ok_or for ok_or_else

Closes #1195
Description
In some cases, we were using ok_or with error variants that needed heap allocations. This PR changes those to ok_or_else.
Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.
[ ] CHANGELOG has been updated.

It seems like there's been a regression for the set integration benchmark. I'll check the changes again to see if it makes sense, but maybe we'll need to trigger the workflow again.

@Oppen Re-run it and it seems to be a false positive


top_k should be positive instead of strictly positive?

System Info
n/a
Information

[X] Docker
[X] The CLI directly

Tasks

[X] An officially supported command
[ ] My own modifications

Reproduction
setting top_k to 0
Expected behavior
the validator reject top_k == 0 while setting the default value to 0. allowing top_k == 0 would be more consistent?
https://github.com/huggingface/text-generation-inference/blob/e58ad6dd66413ef34585348cdbac1664da391fa9/router/src/validation.rs#L190-L197

top_k == 0 could disable top_k sampling, the same implication as the internal default value?

Well it' s the same as not sending it , which is more obvious to me (especially when using the API with code and top_k could get written as 0 without you realizing.).
I'll ping @OlivierDehaene to have a second opinion on this. Closing for now to avoid the bikesheeding.
I understand the argument, I feel it's a bit better like this, but this feels like aesthetic decision to me.
I'll close for now, we can reopen if the discussion needs to happen


Is it custom operator supported？

Is it unbuilt-in operators of TVM supported？If it is, then in which function dose the work to generate the computes and schedules？How about a custom operator？

If you want to support a custom operator that unbuilt in TVM, you can reference

3rdparty/blazerml-tvm/python/tvm/relay/frontend/onnx.py
TPAT call the from_onnx interface of tvm. Cuda source code will be generated by relay.build in TVM.
If you interested in this, you can read from this function.
python/cuda_kernel.py -> function: CudaKernel::run -> "relay.build"

If you want to support a custom operator that unbuilt in TVM, you can reference

3rdparty/blazerml-tvm/python/tvm/relay/frontend/onnx.py

TPAT call the from_onnx interface of tvm. Cuda source code will be generated by relay.build in TVM. If you interested in this, you can read from this function.

python/cuda_kernel.py -> function: CudaKernel::run -> "relay.build"

That is to say TPAT can’t generate the computes and schedules automaticly for the unbuilt-in operators of TVM,  is it in the future plan?

If you want to support a custom operator that unbuilt in TVM, you can reference

3rdparty/blazerml-tvm/python/tvm/relay/frontend/onnx.py

TPAT call the from_onnx interface of tvm. Cuda source code will be generated by relay.build in TVM. If you interested in this, you can read from this function.

python/cuda_kernel.py -> function: CudaKernel::run -> "relay.build"

That is to say TPAT can’t generate the computes and schedules automaticly for the unbuilt-in operators of TVM, is it in the future plan?

Yes, we will support all of onnx operators in the future. But it not soon.

thanks, I see.


Consults in details of training LGD model in Grasp-anything++ database.

Thank you for your great work. However, I am little confused on the released code. I will be highly appreciated if you could help me out.
1.In LGD/train_network_diffusion.py#L247, it appears that the loss computed by GaussianDiffusion:training_loss is superseded by that of net:compute_loss. Does this imply that the ddpm module is not involved in updating the network parameters?
(https://github.com/andvg3/LGD/blob/2471385507a883ba9147624ce2b3983e691f5fd9/inference/models/lgdm/network.py#L140)
https://github.com/andvg3/LGD/blob/2471385507a883ba9147624ce2b3983e691f5fd9/diffusion/gaussian_diffusion.py#L808
https://github.com/andvg3/LGD/blob/2471385507a883ba9147624ce2b3983e691f5fd9/train_network_diffusion.py#L237-L247
2.In LGD/diffusion/gaussian_diffusion.py:#L867, the guiding_point is computed using net.pos_output, with pos_output being updated by x+net.pos_output. My interpretation is that x represents the noised q_score_map at time t, while net.pos_output might be the predicted q0 or noise added to the q_0 at time t. I am confused which is the right way to interpret updated net.pos_output:  x + net.pos_output
https://github.com/andvg3/LGD/blob/2471385507a883ba9147624ce2b3983e691f5fd9/diffusion/gaussian_diffusion.py#L866-L868
https://github.com/andvg3/LGD/blob/2471385507a883ba9147624ce2b3983e691f5fd9/inference/models/lgdm/network.py#L114-L119
3.Furthermore, I've observed that t_embedding is not utilized in the computations. In LGD/inference/models/lgdm/network.py#L107, the lgd architecture appears to be simliar to grconvnet.
https://github.com/andvg3/LGD/blob/2471385507a883ba9147624ce2b3983e691f5fd9/inference/models/lgdm/network.py#L98-L117
I would be most grateful for any clarification you could provide on these matters.
Thank you in advance for your time and consideration.
Best regards,
lkc.

Hi @lkccu ,

Does this imply that the ddpm module is not involved in updating the network parameters?

No. The denoising process was involved in the training process and evaluation through the call of WrappedModel in LGD/diffusion/respace.py. Please refer to L227 of LGQ/train_network_diffusion.py. The one you mentioned was use for evaluation metrics, not training loss.

I am confused which is the right way to interpret updated net.pos_output.

It is our design choice to implement the proposed architecture in our paper using guiding points as attention maps. We add the guiding pos_output predicted from conditions to the actual pos_output predicted from the denoising process, or q_0 as you mentioned. This adding mechanism aligns with our network design.

The lgd architecture appears to be simliar to grconvnet.

They are similar to some extend. However, our network integrates combining features from ALBEF modules and adding guiding features, as I have explained in your previous question. The t_embedding is the embedding from input timestep, together with text and image features, helps to predict guiding_points.
I hope my explanations help. Please do not hesitate to contact me if you have any further questions.
Best regards,
An Vuong

Thank you for your kind and so detailed explanation! It is so helpful.
Regards,
lkc

Hi, @andvg3
I want to train lgrconvnet3/clipfusion/proposed LGD mode in Grasp-anything++ dataset.What is the recommended settings?
Best regards,
lkc.

Hi @lkccu ,
You should first download both Grasp-Anything and Grasp-Anything++ datasets. Then please follow the step-by-step instructions provided in the README file, it should work properly. Please let me know if you have any further questions.
Best,
An Vuong

Closed due to inactivity.


build: Bump deps on @fluidframework/eslint-config-fluid to 2.0.0 in server packages

Note: @fluidframework/eslint-config-fluid's default export was updated from minimal to recommended.
Additionally...

the @fluidframework/gitresources package had no violations against the recommended config, and so was implicitly upgraded to that configuration.
removes many unneeded eslint-disable directives

Once again, looks good! I see there are lots of eslint exceptions especially within server/routerlicious directory. Will this need additional clean up task in the future?

Good question! For server code the answer is actually no. These packages run in a node environment, so we don't want to forbid node imports.
Craig and I have been talking about unifying release-group configs a bit better once we have migrated to proper yarn / pnpm workspaces for our release groups. At that point, we'll probably introduce a single config for server that makes the exceptions we expect all of the packages within to need. Then these overrides can get cleaned up in the package-by-package configs.

Once again, looks good! I see there are lots of eslint exceptions especially within server/routerlicious directory. Will this need additional clean up task in the future?

Good question! For server code the answer is actually no. These packages run in a node environment, so we don't want to forbid node imports.
Craig and I have been talking about unifying release-group configs a bit better once we have migrated to proper yarn / pnpm workspaces for our release groups. At that point, we'll probably introduce a single config for server that makes the exceptions we expect all of the packages within to need. Then these overrides can get cleaned up in the package-by-package configs.

Thanks for the answer! It'd be nice to have a unified config in the future (at least in server release-group) if possible!


Tie support account to opennebula account

Author Name: OpenNebula Systems Support Team (OpenNebula Systems Support Team)
Original Redmine Issue: 4679, https://dev.opennebula.org/issues/4679
Original Date: 2016-07-25

To keep the support tab logged if the user is logged in Sunstone

done


Is LDAP authentication supported by registry 2 ?

Hi!
If you are reporting a new issue, PLEASE make sure that does not have any duplicates already open.
We would like to take this time to remind you of the information we need to debug the problem you are seeing. This is an automated response so if this ticket is not about a bug, do not fret.
If you fail to provide this information within 7 days, we will close this because we cannot debug your issue. We can reopen whenever the information is provided.
Thank you.
Please see:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues
Description of problem:

`docker version`:

`docker info`:

`uname -a`:

Environment details (AWS, VirtualBox, physical, etc.):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Actual Results:

Expected Results:

Additional info:

#ENEEDMOREINFO

I saw it on the roadmap; https://github.com/docker/distribution/blob/f2954260a63f041bb5aeed3bb854502a86231111/ROADMAP.md#registry-20
But I think it hasn't actually been implemented (yet?), see this comment; https://github.com/docker/distribution/pull/367#issuecomment-93621596
@dmp42 do you know if the "Pluggable authentication system" (e.g. LDAP authentication) is still on the roadmap for Registry?

The registry supports a pattern where authentication itself is delegated to a secondary server that then issues a signed grant that the registry can verify.
This design is indeed implemented and supported, and does allow for that secondary server to use whatever authentication backend it wants.
Though, we don't provide implementation examples, specifically we don't ship a running LDAP connector (getting AD to behave is notoriously difficult).
Now, DHE  does ship with LDAP support IIRC (https://www.docker.com/enterprise/hub/)
In a shell, if you want LDAP:

DIY using the token / delegated auth path for the registry
use DHE, or any other product that ship with it


Adv dupe 2 isn't loading any saved files

When I try loading a base it says duplicator upload failed, I've tried reinstalling adv dupe 2 and it hasn't worked.

Does it work with any other dupe files? If so then the file is probably bad. Otherwise, you either have a bad version installed or bad addon installed.