Flutter Web visual density issue and laggy animation

I upgraded my web app to Flutter 2.0 stable version and I've got 2 problems.

Text and icons are very blurry and thick. Every element on my page got smaller. This image shows the comparison - on the left Flutter 2.0 and on the right Flutter 1.22:

First animation is always laggy. This wasn't an issue for me in Flutter 1.22

@Henzelix
Can you provide a minimal reproducible code sample that shows the difference / issue ?

@darshankawar I hope that's what you ask for. Even in DartPad you can see that text doesn't look like it should
`Card(
margin: EdgeInsets.only(top: 15),
color: Colors.purple,
child: ListTile(
                            title: Text("Test", style: TextStyle(
                              fontSize: 20,
                              fontWeight: FontWeight.w600,
                              color: Colors.white,
                            ),),
                            leading: Column(
                              children: [
                                Text("5", style: TextStyle(
                                  color: Colors.white,
                                  fontSize: 29,
                                  fontWeight: FontWeight.bold,
                                ),),
                                Text("april", style: TextStyle(
                                  //fontFamily: 'Nunito',
                                  color: Colors.white,
                                ),),
                              ],
                            ),
                            trailing: Icon(Icons.edit, color: Colors.white,),
                            subtitle: Text("hgbhrghrgbh", style: TextStyle(
                              color: Colors.white,
                            ), overflow: TextOverflow.ellipsis, maxLines: 2,),
                            isThreeLine: true,
                          ),
                        )`

@Henzelix
Web on stable version started from 2.0.0, so how did you compare 1.22 vs 2.0 on web ?

@Henzelix
Web on stable version started from 2.0.0, so how did you compare 1.22 vs 2.0 on web ?

I started this project when Web was in beta. Maybe this wasn't exactly 1.22 (I can't check it) but it was something near that

@darshankawar any idea how to fix it?

It could be that before stable you were using one web renderer and after 2.0 you're using a different one. I've seen this level of difference in rendering between canvas kit and HTML renderers. Could you try flutter run with --web-renderer canvaskit and then with --web-renderer html.

It could be that before stable you were using one web renderer and after 2.0 you're using a different one. I've seen this level of difference in rendering between canvas kit and HTML renderers. Could you try flutter run with --web-renderer canvaskit and then with --web-renderer html.

@msoham123 --web-renderer html fixed text issue, but icons are stil blurry and ListTiles are significantly smaller in comparison with my Flutter 1.22 beta version

@Henzelix
Flutter 1.22 was an older version which isn't compatible or feasible to go back to.
I tried your code sample on beta 1.26 vs beta 2.0.0 using canvaskit and html renderers, but didn't see any difference.

beta 1.26 canvaskit vs html:

beta 2.0.0 canvaskit vs html:

If you are running flutter run -d chrome, it defaults to canvaskit rendering, so that may be one of the reasons why you may be seeing the difference in text and icons rendering, because canvaskit renders the widgets a bit differently than html.

1.26 and 2.0.0 beta flutter doctor -v
[✓] Flutter (Channel beta, 1.26.0-17.6.pre, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-GB)
    • Flutter version 1.26.0-17.6.pre at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision a29104a69b (3 weeks ago), 2021-02-16 09:26:56 -0800
    • Engine revision 21fa8bb99e
    • Dart version 2.12.0 (build 2.12.0-259.12.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.54.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (2 available)
    • SM A260G (mobile) • 5200763ebcfa861f • android-arm    • Android 8.1.0 (API
      27)
    • Chrome (web)      • chrome           • web-javascript • Google Chrome
      88.0.4324.192

! Doctor found issues in 1 category.

[✓] Flutter (Channel beta, 2.0.0, on Mac OS X 10.15.4 19E2269 darwin-x64, locale
    en-GB)
    • Flutter version 2.0.0 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 60bd88df91 (5 days ago), 2021-03-03 09:13:17 -0800
    • Engine revision 40441def69
    • Dart version 2.12.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.54.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (3 available)
    • SM A260G (mobile) • 5200763ebcfa861f • android-arm    • Android 8.1.0 (API
      27)
    • macOS (desktop)   • macos            • darwin-x64     • Mac OS X 10.15.4
      19E2269 darwin-x64
    • Chrome (web)      • chrome           • web-javascript • Google Chrome
      88.0.4324.192

! Doctor found issues in 1 category.

You may try again with 1.26 and 2.0.1 and check if you still see the same behavior or not. If so, provide the details accordingly.

@Henzelix  I don't know if this matters, but try running flutter clean and see if that changes anything. I don't know much about dart2js and building for web but maybe some old 1.22 build files have remained after the upgrade to 2.0, and that causes these discrepancies.

@Henzelix  I don't know if this matters, but try running flutter clean and see if that changes anything. I don't know much about dart2js and building for web but maybe some old 1.22 build files have remained after the upgrade to 2.0, and that causes these discrepancies.

@msoham123 already tried it - nothing has changed

@Henzelix
Flutter 1.22 was an older version which isn't compatible or feasible to go back to.
I tried your code sample on beta 1.26 vs beta 2.0.0 using canvaskit and html renderers, but didn't see any difference.

beta 1.26 canvaskit vs html:

beta 2.0.0 canvaskit vs html:

If you are running flutter run -d chrome, it defaults to canvaskit rendering, so that may be one of the reasons why you may be seeing the difference in text and icons rendering, because canvaskit renders the widgets a bit differently than html.

1.26 and 2.0.0 beta flutter doctor -v
[✓] Flutter (Channel beta, 1.26.0-17.6.pre, on Mac OS X 10.15.4 19E2269
    darwin-x64, locale en-GB)
    • Flutter version 1.26.0-17.6.pre at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision a29104a69b (3 weeks ago), 2021-02-16 09:26:56 -0800
    • Engine revision 21fa8bb99e
    • Dart version 2.12.0 (build 2.12.0-259.12.beta)

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.54.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (2 available)
    • SM A260G (mobile) • 5200763ebcfa861f • android-arm    • Android 8.1.0 (API
      27)
    • Chrome (web)      • chrome           • web-javascript • Google Chrome
      88.0.4324.192

! Doctor found issues in 1 category.

[✓] Flutter (Channel beta, 2.0.0, on Mac OS X 10.15.4 19E2269 darwin-x64, locale
    en-GB)
    • Flutter version 2.0.0 at /Users/dhs/documents/Fluttersdk/flutter
    • Framework revision 60bd88df91 (5 days ago), 2021-03-03 09:13:17 -0800
    • Engine revision 40441def69
    • Dart version 2.12.0

[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /Users/dhs/Library/Android/sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /Applications/Android
      Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)
    • All Android licenses accepted.

[!] Xcode - develop for iOS and macOS
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 12.3, Build version 12C33
    ! CocoaPods 1.9.3 out of date (1.10.0 is recommended).
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin
        code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To upgrade see
      https://guides.cocoapods.org/using/getting-started.html#installation for
      instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 4.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build
      1.8.0_242-release-1644-b3-6915495)

[✓] VS Code (version 1.54.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.18.1

[✓] Connected device (3 available)
    • SM A260G (mobile) • 5200763ebcfa861f • android-arm    • Android 8.1.0 (API
      27)
    • macOS (desktop)   • macos            • darwin-x64     • Mac OS X 10.15.4
      19E2269 darwin-x64
    • Chrome (web)      • chrome           • web-javascript • Google Chrome
      88.0.4324.192

! Doctor found issues in 1 category.

You may try again with 1.26 and 2.0.1 and check if you still see the same behavior or not. If so, provide the details accordingly.

@darshankawar Interesting that there is no difference on your computer 🤔 I already switched to 1.26 to continue working my project, but I might comeback to 2.0 in few weeks and check everything once again.

Without additional information, we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.
Could everyone who still has this problem please file a new issue with the exact description of what happens, logs, and the output of flutter doctor -v.
All system setups can be slightly different, so it's always better to open new issues and reference related issues.


reconnecting-websocket

I want to use the reconnecting-websocket  .
Could  it be possible to use it instead of the normal websocket.

ok i figure it out

@anykao  can you let me know how do you have resolved this one


Roadblock to Mirror-Loading

I'd like to create a 'mirror-loading' package, similar to dva-loading. Basically it provides free "loading" indicators when effects are triggered or completed.
Problem
There should be a way in mirror to tell if an action handler is a "reducer" or an "effect". This way, "mirror-loading" can work with effects only.
Possible Solutions

Expose the "effects" object in Mirror.

This would be the simplest solution, but it doesn't seem elegant to expose more than necessary. Effects are already included in the list of actions.
// index.js
export default {
  /* ... */
  effects,
  /* ... */
}

Tag effect action handlers as "effects"

This would allow filtering over actions to find which are effects. A rough outline of an example below:
// model.js
  filterReducers(reducers) {
   /* .... */
    acc[action].prototype.effect = true
   /* ... */
  }

Something else ?

Is there any progress on this 😄
I would love to see this package

@vanhtuan0409 Currently, you could add a loading property for your model, then in your effects, set it to true before fetching and to false after fetching. Here is a demonstration.
An out-of-the-box loading requires a global loading state in Mirror, though it's not too hard to implement.

I've made a demo of a loading package. I'll try to finish it this weekend. mirror-loading


deps: update dockerfile dependencies

@chenrui333 Thanks for your work. Please fix the ci issue.

@yxxhero I just realized that we missed covering the supported kustomize versions in our test matrix. We shall probably figure out which versions to support and modify the workflow accordingly, in a separate PR. WDYT?

@mumoshu yeah. I think so. I will create a PR for it.

ping


Some useful changes to monitorize streams

Hi,
We are using twitter4j for an Sparsity-Technologies application. We have considered useful to monitorize which are the active streamings assigning a name to the related thread because we have a thread per user.
We have attached also a minor change to work with Java 6. We would be grateful if you add our changes into the future deployed version.
Thank you in advance

Thanks for the pull request.
That's a good idea!
But technically it is possible that the method call to the TwitterStream happens after the connection establishment.
So it is probably better to make the thread name configurable rather than adding a setter to TwitterStream.
Could you please add "threadName" parameter to twitter4j.properties/PropertyConfiguration/ConfigurationBuilder?


Support for static and media files in development env

Description
Implement static and media files support for the development environment.
Blocked by

GH-4

Static files support implemented in 3a7d506c0d20646acdbf0a87f9a39e75e0dc3735


Migrate to client core

CI fail due to typespec-tests/src/main/resources/META-INF/apiview_properties.json
Maybe you can add it to .gitignore?


Are normalization reversible?

❓ Questions and Help
Suppose I use CSRankNorm on my labels, and I got scores as prediction results. Are these scores reversible, that I can calculate a label from a given score?

Qlib does not explicitly leave a hook to reverse the prediction to its original meaning before processing (a lot of trading strategies do not need such a step).
You can implement it in your own trading strategy (here is an example).


Compilation error: Implementation limit exceeded

Some people get this error while instantiating a WASM module, all of them on Windows, e.g. see here. Unfortunately it is quite opaque and I'm not really sure where to go from here, especially since wasmtime-py ignores RUST_LOG. How do I debug this?

That's probably bytecodealliance/wasmtime#1734, so should hopefully be fixed once that PR lands.
@alexcrichton would it be feasible to have wasmtime-py respect RUST_LOG?

I've opened https://github.com/bytecodealliance/wasmtime/pull/1737 to get RUST_LOG working, and otherwise @tschneidereit is right that PR should fix the underlying issue too!

Ok I'm going to close this in favor of https://github.com/bytecodealliance/wasmtime/pull/1734 and the upstream issue at https://github.com/bytecodealliance/wasmtime/issues/1587, since I believe those should cover the issues here.

@whitequark the fix for this issue was just merged.  Please let me know if you're still running into an issue on Windows.  Thanks!

I can confirm this fixes the Windows issue.
@alexcrichton Is there a chance we can have a wasmtime release?

Sure yeah, I pushed a 0.16.1 tag which is the exact same as the 0.16.0 tag but should download the latest copies of the C API. We've had some breaking API changes so I'm going to hold off until 0.17.0 of wasmtime itself before publishing that for this extension.
CI isn't running, however, so I'm going to need to debug that...

Ok published now!

I can confirm that wasmtime-py and wasmtime are fixed on my end on mingw via a manual install. Just for the sake of knowing, is there any particular reason that if you install manually you have to download wasmtime into your source directory instead of wasmtime being installed into site-packages?

The wasmtime dynamic library needs to be downloaded to wherever wasmtime-py is installed to, and it you're manually installing it that may explain the oddness?


Difference in behavior between pip and github blackjax versions on example code

Bug Description
I'm running the example code from the readme (this) and the version of blackjax in pip seems to not work for me (pip install blackjax) but the version in Github does (installed with git clone and pip install .).
I don't really know what goes into packaging things on pip or what the difference might be, so close if this just seems like a problem with my system!
Thanks for the nice package
Steps/Code to Reproduce
The code I'm running is this (same as example, just added a plot):
import jax
import jax.numpy as jnp
import jax.scipy.stats as stats
import numpy as np
import pandas
import plotnine

import blackjax.nuts as nuts

observed = np.random.normal(10, 20, size=1_000)
def logprob_fn(x):
  logpdf = stats.norm.logpdf(observed, x["loc"], x["scale"])
  return jnp.sum(logpdf)

# Build the kernel
step_size = 1e-3
inverse_mass_matrix = jnp.array([1., 1.])
kernel = nuts.kernel(logprob_fn, step_size, inverse_mass_matrix)
kernel = jax.jit(kernel)  # try without to see the speedup

# Initialize the state
initial_position = {"loc": 1., "scale": 2.}
state = nuts.new_state(initial_position, logprob_fn)

# Iterate
rng_key = jax.random.PRNGKey(0)
positions = []
for _ in range(1_000):
    _, rng_key = jax.random.split(rng_key)
    state, _ = kernel(rng_key, state)
    positions.append(state.position['loc'])

df = pandas.DataFrame({ "draw" : range(len(positions)), "x" : np.array(positions)})

(
    plotnine.ggplot(df) +
    plotnine.geom_point(plotnine.aes("draw", "x"))
).draw(show = True)

Expected Results
Here's what I get with Github blackjax:

Actual Results
Here's what I get with pip blackjax:

I repeated this multiple times with different seeds.
Versions
This is the version the github install shows:
>>> import blackjax; print("BlackJAX", blackjax.__version__)
BlackJAX 0.2.1

This is what the version from pip shows (along with everything else):
>>> import blackjax; print("BlackJAX", blackjax.__version__)
BlackJAX 0.2.1
>>> import sys; print("Python", sys.version)
Python 3.9.7 (default, Oct 10 2021, 15:13:22)
[GCC 11.1.0]
>>> import jax; print("Jax", jax.__version__)
Jax 0.2.25
>>> import jaxlib; print("Jaxlib", jaxlib.__version__)
Jaxlib 0.1.74

Thank you for the great bug report! The reason why this works with the last commit version and not pip is that the readme example is not in sync with the pip version. Indeed, since the 2.1 release we're asking users to provide a logprobability function and not a potential function anymore. If you return -jnp.sum(logpdf) instead of jnp.sum(logpdf) this should give you the correct results.
I'll cut a new release in the next few days.

Ah, makes sense, thanks. Feel free to close whenever -- I'll use the github clone for now!


Does BatchNormalization in DL4J has bias or weights as parameters other than running mean or running var ?

I wanted to see how BatchNorm implementation is different from other frameworks like PyTorch. PyTorch uses weight and bias by default while DL4J does not. I observed this using ResNet50 model param table.
Please help !

@nitin2212  please post questions like this on the dl4j forum. Was the question how dl4j implements batch norm? I think you answered it yourself. I'm closing this.


HSEARCH-2934 Pending Elasticsearch streamed works may fail when stopping Hibernate Search and using the drop-and-create-and-drop strategy

https://hibernate.atlassian.net//browse/HSEARCH-2934
The solution I chose was to provide each index manager with its own view of the stream orchestrator, so that it can close its view when closing the index manager, which will automatically wait for pending stream works to be executed.
I could have simply added an explicit wait on the "shared" stream orchestrator, but my solution has the additional benefit of preventing new stream works to be accepted by the index manager while waiting for pending stream works to be executed.

Great fix!
I have only a minor consideration about how it's tested, I'll comment on the specific change.

Merged!


Worked on the treanding Video and activity indicator

Verified and merged with the master

verifyied and merged with the master


backport v1.8: node-neigh: Query once netlink for neigh discovery device

#15431 -- node-neigh: Query once netlink for neigh discovery device (@brb)

Once this PR is merged, you can update the PR labels via:
$ for pr in 15431; do contrib/backporting/set-labels.py $pr done 1.8; done

test-backport-1.8

test-backport-1.8

test-backport-1.8

The CI failures look unrelated. Running it again.

test-backport-1.8

test-backport-1.8

test-backport-1.8

@brb can you include https://github.com/cilium/cilium/pull/15261 here?

test-backport-1.8

test-4.9

test-4.19

CI 4.19 failures seems to be unrelated to my PR.

CI 4.19 failures seems to be unrelated to my PR.

@brb There are also 4.9 failures. Did you check those to see if they are also unrelated?

test-*4.9

test-4.9

There are also 4.9 failures. Did you check those to see if they are also unrelated?

I am bit confused which ones of the 4.9 should pass. There are plenty of jobs 4.9 jobs which have passed.

There are also 4.9 failures. Did you check those to see if they are also unrelated?

I am bit confused which ones of the 4.9 should pass. There are plenty of jobs 4.9 jobs which have passed.

Yeah, weird. 4.9 for k8s versions > 1.13 failed.

Martynas suggested to merge this PR since the failures are unrelated.


Crash immediately after function is called to signIn or startAtLaunch

Hey everyone so I've been at this for days now. I am setting up the ANE using Flash CS6 and Flash Develop. I have the ANE connected to the library path in Flash CS6 also have it added to the library in Flash Develop.
This is how I have everything setup in my startScreen Class:

Now once I click the button on my Android Device the Application Crashes immediately after doing so here is how my XML is setup:

I followed all the instructions as you can see. So i don't understand why it's crashing and not displaying anything. Please any help would be appreciated thanks!

me too, i am trying use another AIR SDK version (15 & 17), but the problem still the same like this.

Did someone find a solution??

Yes Finally got Google Play Services to work perfectly. No Problems so far. Anyone still need help?

@NathanFitchett yes, my app still crushes when i'm tryin to SignIn or StartAtLaunch..

@NathanFitchett
It would be grate if you share how you made it work.

@cherniv
I found a great guide. Here's sollution:
https://github.com/nitacawo/Google-play-freshplanet-Overlawled-examples
There are 3 versions. I used Freshplanet example and replaced ANE with newest one from Freshplanet.
Look at the -app.xml. You should add Vungle extension to your project. Thought author forgot to remove it and I didn't use it in my code util I get it that its needed to avoid crashes.

Hi nathan, could you tell us how you got it to work please?

@NathanFitchett
could you tell us how you got it to work please? I am getting nowhere.

@goshdarn
now it is working for me. i did two things: 1) stopped using an AdMob ANE 2) started the GP Services integration from scratch


chore: Update instructions to get latest linter

Signed-off-by: Bryon Nevis<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[X] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[X] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?) n/a
[X] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions
Remove golangci-lint and run make lint
New Dependency Instructions (If applicable)

Recheck

Codecov Report

Merging #4067 (5f6e10f) into main (a157344) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #4067   +/-   ##
=======================================
  Coverage   47.27%   47.27%
=======================================
  Files         114      114
  Lines        9850     9850
=======================================
  Hits         4657     4657
  Misses       4805     4805
  Partials      388      388

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 a157344...5f6e10f. Read the comment docs.


Add missing group entry functions for Solaris/Illumos

This commit adds definitions for setgrent, endgrent, and getgrent which were missing (but available for FreeBSD and other *nix systems).

r? @gnzlbg
(rust_highfive has picked a reviewer for you, use r? to override)

@bors: r+

:pushpin: Commit 4e6fe8c5e2d4408c38862b6217cacb35d726b461 has been approved by gnzlbg

:hourglass: Testing commit 4e6fe8c5e2d4408c38862b6217cacb35d726b461 with merge d7a1995a8745bf56ea5762ca5962ef5d20b2fb94...

:sunny: Test successful - checks-cirrus, checks-travis, status-appveyor
Approved by: gnzlbg
Pushing d7a1995a8745bf56ea5762ca5962ef5d20b2fb94 to master...


Vector layer should be always on top of raster/image layers

Adding a ``DrawControl()` to the map, and later on add a raster layer like:
io = ImageOverlay(url='http://ipython.org/_static/IPy_header.png', bounds=m.bounds)
m.add_layer(io)

When digitizing a new feature, the vector is drawn correctly, but behind the ImageOverlay.

step to reproduce the behaviour:  https://gist.github.com/epifanio/6f9facdd177d39be85d912f092515b3c

Any pointer on which part of the src code I should look into? I was looking at jupyter-leaflet.js#L296 trying  to understand if it is possible to  "reorder" the sequence of active layers, but I can't find any method to do that.

Hmm, not sure how that could be accomplished and don't have time to dig into it right now :(

Closing. Layers now always respect the order of the layers python tuple, and it cannot be altered by toggling the visible attribute anymore.


some GPTQ models can not be loaded anymore

Caveat : I think it's a problem with exllamav2, but it might be a problem with tabbyAPI
I updated tabbyAPI and ExLllama2 and suddenly older models which used to work return an error with the tokenizer :
load_model with this payload
{
  "name": "TheBloke_AlpacaCielo2-7B-8K-GPTQ",
  "max_seq_len": 8192,
  "gpu_split_auto": true,
  "gpu_split": [
    0
  ],
  "rope_scale":  1,
  "rope_alpha": 1,
  "no_flash_attention": false,
  "low_mem": false
}

returns :

{
   "data":{
      "error":{
         "message":"Out of range: piece id is out of range.",
         "trace":"Traceback (most recent call last):\n  File \"/media/GLIMSPANKY/tabbyAPI/main.py\", line 118, in generator\n    for (module, modules) in load_status:\n  File \"/media/GLIMSPANKY/tabbyAPI/model.py\", line 187, in load_gen\n    self.tokenizer = ExLlamaV2Tokenizer(self.config)\n

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n
    File \"/media/GLIMSPANKY/tabbyAPI/tby/lib/python3.11/site-packages/exllamav2/tokenizer.py\", line 97, in __init__\n
    itp = self.tokenizer.decode([i])\n
^^^^^^^^^^^^^^^^^^^^^^^^^^\n

   File \"/media/GLIMSPANKY/tabbyAPI/tby/lib/python3.11/site-packages/exllamav2/tokenizers/spm.py\", line 37, in decode\n
    text = self.spm.decode(ids)\n
^^^^^^^^^^^^^^^^^^^^\n

  File \"/media/GLIMSPANKY/tabbyAPI/tby/lib/python3.11/site-packages/sentencepiece/__init__.py\", line 780, in Decode\n
    return self._DecodeIds(input)\n
^^^^^^^^^^^^^^^^^^^^^^\n

  File \"/media/GLIMSPANKY/tabbyAPI/tby/lib/python3.11/site-packages/sentencepiece/__init__.py\", line 337, in _DecodeIds\n
   return _sentencepiece.SentencePieceProcessor__DecodeIds(self, ids)\n           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^\n

IndexError: Out of range: piece id is out of range.\n"
      }
   }
}

Basically the same as with me and MythoMax on Ooba. It's specifically ExLlama-V2 0.0.10 that's the problem. It's a known issue, and will be fixed with 0.0.11. #211

Update on this issue. I tried Oobabooga with that same GPTQ quant of MythoMax, but with exllamav2 updated to 0.0.11, and I can confirm that the model now loads correctly, so I'd recommend you retest to see if your model loads fine now on the current version. If it does, then you should be fine closing this issue.

Yeps .I can confirm everything now works again. Thanks for your work.


Handle .NET workloads

Describe the bug
There's a good chance (I haven't tested it) that solutions that use .NET workloads (Aspire, MAUI...) will fail to upgrade (or at least cause a warning), especially if --test is specified, are used.
Steps To reproduce
Run .NET Bumper on a project using a .NET workload.
Expected behaviour
The project upgrade is successful.
Actual behaviour
TBD
Additional context
Realised this needed to be checked when fixing a bug for projects using MSBuild SDKs with versions defined in global.json.

Unexpected complication is that if the workloads aren't installed, elevated permissions are needed (at least on Windows) to install them, which pops a UAC dialog. That might be too much to overcome for automated installation (or needs to be swallowed and dealt with appropriately).


Update Sign-In with Ethereum Example

Description
wagmi currently has an example for Sign-In with Ethereum that let's developers get started with authenticating their users. In this PR, we update that guide to use ssx (documentation), an open-source / MIT-licensed library that enables developers to easily integrate Sign-In with Ethereum and more. Core to building SSX was making Sign-In with Ethereum easier to enable in applications, as well as add additional features such as signing in on behalf of a multisig and more.
As part of this, the guide remains nearly identical, but the integration path is updated.
Additional Information

[x] I read the contributing docs (if this is your first contribution).
[x] All updates to components and pages have been made.
[x] We have tested the pages locally to ensure they work.
[x] All steps in the relevant guide have been updated, including code examples and content.
[x] All relevant configurations have been updated.

Your ENS/address: obstropolos.eth

Would prefer this to point to ssx in docs but keep example the same.  What is nice about the current example is it shows you at a low level how sign in with ethereum works. This is a very useful library that I will likely use myself now that I know about it but bit of an indirection in the docs


Vulnerability roundup 111: unzip-6.0: 2 advisories [7.8]

search, files

[ ] CVE-2022-0529 CVSSv3=7.8 (nixos-21.11, nixos-unstable)
[ ] CVE-2022-0530 CVSSv3=7.8 (nixos-21.11, nixos-unstable)

CVE details
CVE-2022-0529
A flaw was found in unzip 6.0. The vulnerability occurs during the conversion of wide string to local string that leads to a heap of out-of-bound writes. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.
CVE-2022-0530
A flaw was found in unzip 6.0. The vulnerability occurs during the conversion of an utf-8 string to a local string that leads to a segmentation fault. This flaw allows an attacker to input a specially crafted zip file, leading to a crash or code execution.

Scanned versions: nixos-21.11: 2128d0aa28e; nixos-unstable: 5aaed40d22f.

Fixed in 0a3e68ba844bf17891c8702604b6149f556b447c


Re-export header-only functions from liburing

Closes #4. This will allow us in iou to delegate all of the prep APIs to liburing instead of being responsible for setting SQEs up correctly.
@twissel would you be open to doing a quick review of this code to check that I didn't get any argument or return types wrong?

Two quick questions:

Shouldn't addr https://github.com/withoutboats/uring-sys/blob/73cd794de0ccf9891098b7b3456d480ea5677ebc/src/lib.rs#L251  be declared as *mut libc::c_void? *const libc::c_void is good for everything except
IORING_OP_READ_FIXED, and indeed it is declared as *mut libc::c_void  here https://github.com/withoutboats/uring-sys/blob/73cd794de0ccf9891098b7b3456d480ea5677ebc/src/lib.rs#L269
Passing libc::off_t as offset in prep_{read, write} functions, for example here  https://github.com/withoutboats/uring-sys/blob/73cd794de0ccf9891098b7b3456d480ea5677ebc/src/lib.rs#L290 seems strange for me, because at least on my machine this is i64 and we have  u64 here https://github.com/withoutboats/uring-sys/blob/73cd794de0ccf9891098b7b3456d480ea5677ebc/src/lib.rs#L64

Agreed these are odd, but they're the types liburing exposes.

And yea, everything but read_fixed also takes a const pointer, I assume because only read_fixed writes directly into that buffer.

Btw: do you plan to use prep helpers in iou?

Yes, to let liburing handle the subtleties of preparing IO events properly.


In this part:
changed factories and builders to support dirty sink and options
adjusted DynamicTableSource to include new paramerters
added serialization and deserialization errors when computing snapshot offset
added deserialization errors when deserializing records

maybe close it. It is not jdbc sink.

delete draft pr


Fix FMC based LCD interface

This PR fixes the FMC based LCD interface and changes the clock configuration. Previously the processor only ran at 16 Mhz (according to the clocks struct).
The cause of the FMC issue was related to caching and speculative execution. By disabling these features using the MPU the display works as expected and updates very fast.
The code in this PR is kind of messy and the MPU configuration probably isn't optimal, but it should be a starting point for further development. It could be improved a lot by implementing a higher level abstraction around the MPU (which I don't think exists yet).

This is awesome! Sorry I didn't see it sooner...


Multiple Labeling

Description
Choose Multiple Labels on Mosaic process

done https://github.com/seongahjo/Mosaicer/commit/d73911bbf8e746dc5b42809a99b574d4f2a43f28


update description metadata - batch 9

@billwagner @tdykstra
Updates for missing/incorrect description metadata.
This is the last of the initial batch of scans - once these are all merged, I'll run another scan to make sure I didn't miss any.

@tdykstra Thank you for your patience with these. Now that they're all merged, I'll run one last pass to clean up anything missed. Coming soonish (if at all).


Added flake8 support and ensure all tests pass

Currently we globally ignore:

Line lengths
Unused imports

I do use flake8 but looks like pylint is a new player I've not used!
I'd be willing to try it out here! Don't approve yet. I'll move us over and add a hook for TravisCI.
https://www.slant.co/topics/4462/~open-source-python-static-analysis-tools

@apfejes, Since flake8 seems to be strictly for PEP8 I have that reporting anything it finds.
Pylint is definitely stricter and emits a ton of warnings and courteousy notifications. I included it but forced it to emit errors only!
I think this is definitely enough linting for such a small project.
Users can run any of the independent static analysis tools on their own PC by executing the scripts in tests/.


Fail to run in macOS 19

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
I would like to use memray, however it doesn't work at all on my system.
# test_memray.py
import numpy as np
x = np.zeros(100)

Running this file with the command python -m memray run test_memray.py yields an immediate seg. fault:
Writing profile results into memray-test_memray.py.44886.bin
zsh: segmentation fault  python -m memray run test_memray.py

Though a file does get written, no recording is done; the result of memray summary memray*.bin  yields:
⠋ Calculating high watermark... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   Memray ERROR: Failed to process memory record
⠋ Processing allocation records... ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━   0% -:--:--Memray ERROR: Failed to process memory record
┏━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━━┳━━━━━━━━━━━┓
┃                                                           ┃     <Total ┃      Total ┃            ┃ Own Memory ┃ Allocati… ┃
┃ Location                                                  ┃    Memory> ┃   Memory % ┃ Own Memory ┃          % ┃     Count ┃
┡━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━╇━━━━━━━━━━━━╇━━━━━━━━━━━━╇━━━━━━━━━━━━╇━━━━━━━━━━━━╇━━━━━━━━━━━┩
└───────────────────────────────────────────────────────────┴────────────┴────────────┴────────────┴────────────┴───────────┘

I tried the previous versions of memray as well, at least back to 1.9.0, and none of the versions seem to work
Expected Behavior
Any of the demonstrated behavior in the documentation
Steps To Reproduce

Make any python file
Run memray run ... on the python file
Observe the seg fault

Memray Version
1.12.0
Python Version
3.11
Operating System
macOS
Anything else?
======================================== System Information ========================================
System: Darwin
Node Name: MacBook-Pro-8.local
Release: 19.6.0
Version: Darwin Kernel Version 19.6.0: Tue Oct 12 18:34:05 PDT 2021; root:xnu-6153.141.43~1/RELEASE_X86_64
Machine: x86_64
Processor: i386

I think you have something weird in your system as we run the memray test suite on Intel Macs and Apple silicon macs without any problem.
Can you try to run memray under lldb and check where is segfaulting?

Also, can you tell us a bit more about your system?
What macOS version are you using? What hardware are you using?

Processor: i386

What does this mean? Are you running a 32 bit macOS?

Also, can you tell us a bit more about your system?
What macOS version are you using? What hardware are you using?

10.15.7 (Catalina)

What does this mean? Are you running a 32 bit macOS?

No sorry, idk why this was generated when I queried the processor. It's 64 bit macOS from 2019.

Can you try to run memray under lldb and check where is segfaulting?

This probably doesn't help, but I changed the source to:
import numpy as np
import memray

with memray.Tracker("output_file.bin"):
  x = np.zeros(100)

Then executed it with the following outputs:
(spri) mpiekenbrock{~/memray}% lldb python test_memray.py
(lldb) target create "python"
Current executable set to 'python' (x86_64).
(lldb) settings set -- target.run-args  "test_memray.py"
(lldb) run
Process 49064 launched: '/Users/mpiekenbrock/opt/miniconda3/envs/spri/bin/python' (x86_64)
Process 49064 stopped
* thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)
    frame #0: 0x0000000000000000
error: memory read failed for 0x0
Target 0: (python) stopped.
(lldb) quit

Again running the code normally just seg-faults:
(spri) mpiekenbrock{~/laplacian_kernel/examples}% python test_memray.py
zsh: segmentation fault  python test_memray.py

I'm not entirely sure how to track down the segfault

When you see this in lldb:
error: memory read failed for 0x0
type “bt” and paste the output here

Ahh it looks like I might need to update to OS X 10.14.
I failed to compile memray from source using gcc-12 and clang-15. The relevant compiler error(s) in question:
 In file included from src/memray/_memray.cpp:1361:
    src/memray/_memray/snapshot.h:110:59: error: 'value' is unavailable: introduced in macOS 10.14
                const auto& intersection = maybe_intersection.value();
                                                              ^
    /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/optional:953:27: note: 'value' has been explicitly marked unavailable here
        constexpr value_type& value() &
                              ^
    In file included from src/memray/_memray.cpp:1377:
    src/memray/_memray/tracking_api.h:222:19: error: 'value' is unavailable: introduced in macOS 10.14
                trace.value().fill(1);
 /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/optional:953:27: note: 'value' has been explicitly marked unavailable here
        constexpr value_type& value() &
                              ^
...

For full reference, here's my compiler config:
(venv) mpiekenbrock{~/memray}% g++ --version
g++-12 (Homebrew GCC 12.2.0) 12.2.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

(venv) mpiekenbrock{~/memray}% clang++ --version
Homebrew clang version 15.0.7
Target: x86_64-apple-darwin19.6.0
Thread model: posix
InstalledDir: /usr/local/opt/llvm/bin

I failed to compile memray from source using gcc-12 and clang-15. The relevant compiler error(s) in question:

Looks like your XCODE installation is broken somehow (which you can confirm by looking up those error messages)

Try setting $ export MACOSX_DEPLOYMENT_TARGET=10.14

You need to figure out how to fix that compilation problem because we cannot reproduce it on our side nor in our CI, so getting it to build on your system it's our only option at debugging this.

Ahh it looks like I might need to update to OS X 10.14.

But you said you are using 10.15.7 (Catalina) no? I think you just need to export MACOSX_DEPLOYMENT_TARGET as I mentioned before

Try setting $ export MACOSX_DEPLOYMENT_TARGET=10.14

I did follow this originally, actually, though I thought I was meant to replace 10.14 with my OS's version; exporting thing does get past that error.

You need to figure out how to fix that compilation problem because we cannot reproduce it on our side nor in our CI, so getting it to build on your system it's our only option at debugging this.

Yeah, that's fair. I might end up updating my OS to macOS 14 just to see if that fixes it. The current error
    src/memray/_memray/macho_shenanigans.cpp:299:17: error: use of undeclared identifier '_dyld_shared_cache_contains_path'
                if (_dyld_shared_cache_contains_path(image_name) && strcmp(section->segname, SEG_TEXT) == 0)
                    ^
1 warning and 1 error generated.

Which I guess may be related to this; will check back in once I try to fix the source.

Oh, that more or less confirms my guess: that function is not available at runtime in your system.
As a quick test can you substitute _dyld_shared_cache_contains_path(image_name) with 0:
                if (0 && strcmp(section->segname, SEG_TEXT) == 0)

and check if it works?

Leave the issue open for now as we still need to fix it on our side

It works :), everything seems to be fine now, have run a couple benchmarks to be sure.
Closing this issue. Thank you for your expediency

Awesome!


fftlog correlation test fails in master

I am finding that currently in master C test 67, corrs:analytic_fftlog, fails. The error I get is the following:
TEST 67/91 corrs:analytic_fftlog WARNING: ERROR: Cannot make log-spaced array with 0 points - need at least 2

ERROR 1026: ccl_correlation.c: ccl_tracer_corr_fftlog ran out of memory

Is this something weird with my setup at the moment or can anyone else reproduce this?

Travis is reporting that master is passing tests.

Does travis run the C tests or just python? @elisachisari and @sjoudaki have now reproduced this behaviour.

Okay, weird. Maybe Elisa or Shahab can sit with you to have a look? Or I'm happy to try to pair debug this via a slack call or something.

I don't have an issue with the c unit test, only via the notebook do I obtain:
"CCLError: Error CCL_ERROR_LINSPACE: ccl_correlation.c: ccl_tracer_corr_fftlog ran out of memory"

sorry, accidental closure.
I don't have an issue with the c unit test, only via the notebook do I obtain:
"CCLError: Error CCL_ERROR_LINSPACE: ccl_correlation.c: ccl_tracer_corr_fftlog ran out of memory"
Happy to chat with David more closely.

I'm away from my desk till Dec 8, but can connect remotely and share screen if it helps, @damonge.

@c-d-leonard @sjoudaki: We debugged this with @damonge. We think this is being caused by CCL looking for the wrong ccl_params.ini. To avoid this, could you please try to make; make install; make uninstall; make install and run the checks again? This fixed the issue for me in my computer.

@elisachisari Thanks! Yes, with this I now have that test passing (although I still have test 73 failing with:
TEST 73/91 emu:model_5 ERROR 1032: ccl_power.c: ccl_cosmology_compute_power_class(): Error running CLASS spectra:spectra_init(L:1297) :error in spectra_pk(pba,ppt,ppm,pnl,psp); =>spectra_pk(L:2785) :error in spectra_sigma(pba,ppm,psp,8./pba->h,0.,&(psp->sigma8)); =>spectra_sigma(L:28
but I think this is being addressed by @philbull in PR #521 ?

It is, yes. We should leave this open until @sjoudaki confirms this also fixes his issue.

We agreed to go ahead and close this because @sjoudaki is unable to check this at the moment and we have confirmation from two different people who were seeing this error that it is fixed.

Sorry Danielle, I did check this earlier today and chatted with David about it, my issue with the memory was never for the c unit test, but at the notebook level. There I obtained the analogous error:
"CCLError: Error CCL_ERROR_LINSPACE: ccl_correlation.c: ccl_tracer_corr_fftlog ran out of memory"
And, this has still not been fixed, even with the latest suggestion.

Yes, after my latest message here, it now seems to be working. I guess we can put this aside for now, and hope the memory error does not reappear.

Don't think it's a memory error, just a problem with residual files. In any case I agree that the way the spline params are currently being set is not ideal (for one it makes use of static variables and can get very confused about where to look for the file). Hopefully this is something we cab improve soon.

 Grrrrrr...


Step name

I would like to have each step have it's page name. Page title would go below step circle.

FragmentStatePagerAdapter would need to have:
private List<String> mFragmentTitleList;

@Override
  public CharSequence getPageTitle(int position) {
    return mFragmentTitleList.get(position);
  }

to get titles.
Or manualy:...
@Override
public CharSequence getPageTitle(int position) {
  switch (position) {
    case 1: return "Page 1";
    case 2: return "Page 2";
  }
  return null;
}

Implementing #16 to show step title below step indicator.
Somewhy I can't do PR.

Label feature was added by @rakshakhegde


Better connect API

This PR adds more functions for creating edges.
For creating parameter edges, you currently need to
EdgeDescriptor(node=t1, type="parameter", key="learning_rate").to(EdgeDescriptor(node=t2, type="parameter", key="learning_rate"))

With this PR, the equivalent syntax is
t1.parameter_edge("learning_rate").to(t2.parameter_edge("learning_rate"))

Much nicer.
❓  However, *_edge is a bit of a misnomer, since what it really returns is an edge descriptor you can connect to... Is that a problem?

Could @JuhaKiili or someone else who is more in touch with the customer to comment on the *_edge and its misnomerity?


jwt access token encryption decryption

Description:
Jwt access token that was not encrypted previously and was a security issue has been resolved.
Fixes #13

Type of change:

[X] Bug fix (non-breaking change which fixes an issue)

Checklist:

[X] My code follows the style guidelines of this project.
[X] I have performed a self-review of my own code.
[X] My changes generate no new warnings.
[X] Any dependent changes have been merged and published in downstream modules.

@MadhusreeBera  please update the PR with the required changes.

I have made the required changes. Please check @Shubham-Kumar-2000


Do a last polling before closing the IocpProactor

Fix bug #38

Ok this pull request removes the exception of bug #38 but it's not perfect. I get the following errors after more testing, sometimes :
Traceback (most recent call last):
  File "D:\Anaconda3\lib\asyncio\windows_events.py", line 749, in __del__
    self.close()
  File "D:\Dev\Code\quamash\quamash\_windows.py", line 73, in close
    self._poll(1)
  File "D:\Dev\Code\quamash\quamash\_windows.py", line 92, in _poll
    status = _overlapped.GetQueuedCompletionStatus(self._iocp, ms)

I guess there are some checks to do in the polling side ?

If you could rebase this, that would be great,
something like:
git rebase upstream/master
check to make sure it worked
git push -f
this should get rid of the pointless merge commit

Ok but my fix is not ready yet. I think I'll need your help on the IOCP side.

@aknuds1 actually wrote the IOCP code, but I'll try my best.

@Insoleet Maybe I can help, hit me. I think first of all, I'd like to see a test corresponding to why this fix is needed.

This is meant to fix #38 which are all warnings Windows logs during shutdown, but don't actually prevent any functionality.

@harvimt Thanks for the explanation.

This simple test does raise an error when closing the loop on Windows :
import sys
import unittest
import asyncio
import aiohttp
import time
import logging
import quamash
from quamash import QApplication

class Bug(unittest.TestCase):
    def setUp(self):
        self.qapplication = QApplication([])
        self.lp = quamash.QEventLoop(self.qapplication)
        asyncio.set_event_loop(self.lp)

    def tearDown(self):
        try:
            self.lp.close()
        finally:
            asyncio.set_event_loop(None)

    def test_bug(self):
        @asyncio.coroutine
        def waiting():
            yield from asyncio.sleep(1)
        self.lp.run_until_complete(waiting())

if __name__ == '__main__':
    logging.basicConfig(stream=sys.stderr)
    logging.getLogger().setLevel(logging.DEBUG)
    unittest.main()

The complet output is the following :
D:\Anaconda3\python.exe D:\Dev\Code\quamash\bug.py
DEBUG:asyncio:Using proactor: IocpProactor
DEBUG:quamash.QEventLoop:Registering callback <bound method QEventLoop._loop_self_reading of <QEventLoop running=False closed=False debug=False>> to be invoked with arguments () after 0 second(s)
DEBUG:quamash.QEventLoop:Adding callback <Handle BaseProactorEventLoop._loop_self_reading()> with delay 0
DEBUG:asyncio:Using proactor: _IocpProactor
D:\Anaconda3\lib\asyncio\proactor_events.py:467: ResourceWarning: unclosed <socket.socket fd=592, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('<IP_ADDRESS>', 61606), raddr=('<IP_ADDRESS>', 61607)>
  self._ssock, self._csock = self._socketpair()
D:\Anaconda3\lib\asyncio\proactor_events.py:467: ResourceWarning: unclosed <socket.socket fd=576, family=AddressFamily.AF_INET, type=SocketKind.SOCK_STREAM, proto=0, laddr=('<IP_ADDRESS>', 61607), raddr=('<IP_ADDRESS>', 61606)>
  self._ssock, self._csock = self._socketpair()
DEBUG:quamash.QEventLoop:Registering callback <bound method QEventLoop._loop_self_reading of <QEventLoop running=False closed=False debug=False>> to be invoked with arguments () after 0 second(s)
DEBUG:quamash.QEventLoop:Adding callback <Handle BaseProactorEventLoop._loop_self_reading()> with delay 0
DEBUG:quamash.QEventLoop:Running <generator object waiting at 0x00000000040E2C18> until complete
DEBUG:quamash.QEventLoop:Registering callback <bound method Task._step of <Task pending coro=<waiting() running at D:\Dev\Code\quamash\bug.py:24>>> to be invoked with arguments () after 0 second(s)
DEBUG:quamash.QEventLoop:Adding callback <Handle Task._step()> with delay 0
DEBUG:quamash._windows._EventPoller:Starting (proactor: <_IocpProactor overlapped#=0 result#=0>)...
DEBUG:quamash._windows._EventWorker:Thread started
DEBUG:quamash.QEventLoop:Starting Qt event loop
DEBUG:quamash.QEventLoop:Callback timer fired, calling <Handle BaseProactorEventLoop._loop_self_reading()>
DEBUG:quamash.QEventLoop:Callback timer fired, calling <Handle BaseProactorEventLoop._loop_self_reading()>
DEBUG:quamash.QEventLoop:Callback timer fired, calling <Handle Task._step()>
DEBUG:quamash.QEventLoop:Registering callback <bound method Future._set_result_unless_cancelled of <Future pending>> to be invoked with arguments (None,) after 1 second(s)
DEBUG:quamash.QEventLoop:Adding callback <Handle Future._set_result_unless_cancelled(None)> with delay 1
DEBUG:quamash.QEventLoop:Callback timer fired, calling <Handle Future._set_result_unless_cancelled(None)>
DEBUG:quamash.QEventLoop:Registering callback <bound method Task._wakeup of <Task pending coro=<waiting() running at D:\Dev\Code\quamash\bug.py:26> wait_for=<Future finished result=None> cb=[QEventLoop.run_until_complete.<locals>.stop() at D:\Dev\Code\quamash\quamash\__init__.py:283]>> to be invoked with arguments (<Future finished result=None>,) after 0 second(s)
DEBUG:quamash.QEventLoop:Adding callback <Handle Task._wakeup(<Future finished result=None>)> with delay 0
DEBUG:quamash.QEventLoop:Callback timer fired, calling <Handle Task._wakeup(<Future finished result=None>)>
DEBUG:quamash.QEventLoop:Registering callback <function QEventLoop.run_until_complete.<locals>.stop at 0x00000000040EF048> to be invoked with arguments (<Task finished coro=<waiting() done, defined at D:\Dev\Code\quamash\bug.py:24> result=None>,) after 0 second(s)
DEBUG:quamash.QEventLoop:Adding callback <Handle QEventLoop.run_until_complete.<locals>.stop(<Task finishe...> result=None>) at D:\Dev\Code\quamash\quamash\__init__.py:283> with delay 0
DEBUG:quamash.QEventLoop:Callback timer fired, calling <Handle QEventLoop.run_until_complete.<locals>.stop(<Task finishe...> result=None>) at D:\Dev\Code\quamash\quamash\__init__.py:283>
DEBUG:quamash.QEventLoop:Stopping event loop...
DEBUG:quamash.QEventLoop:Stopped event loop
DEBUG:quamash.QEventLoop:Qt event loop ended with result 0
DEBUG:quamash._windows._EventPoller:Stopping worker thread...
DEBUG:quamash._windows._EventWorker:Exiting thread
DEBUG:quamash.QEventLoop:Future <Task finished coro=<waiting() done, defined at D:\Dev\Code\quamash\bug.py:24> result=None> finished running
DEBUG:quamash.QEventLoop:Closing event loop...
DEBUG:quamash.QEventLoop:Registering callback <bound method QEventLoop._loop_self_reading of <QEventLoop running=False closed=False debug=False>> to be invoked with arguments (<_OverlappedFuture cancelled>,) after 0 second(s)
DEBUG:quamash.QEventLoop:Adding callback <Handle BaseProactorEventLoop._loop_self_reading(<_OverlappedFuture cancelled>)> with delay 0
DEBUG:quamash._windows._IocpProactor:Closing
DEBUG:quamash.QEventLoop:Default exception handler executing
ERROR:quamash.QEventLoop:Cancelling an overlapped future failed
future: <_OverlappedFuture pending overlapped=<pending, 0x3fdb550> cb=[BaseProactorEventLoop._loop_self_reading()]>
Traceback (most recent call last):
  File "D:\Anaconda3\lib\asyncio\windows_events.py", line 62, in _cancel_overlapped
    self._ov.cancel()
OSError: [WinError 6] Descripteur non valide
DEBUG:quamash.QEventLoop:Registering callback <bound method QEventLoop._loop_self_reading of <QEventLoop running=False closed=False debug=False>> to be invoked with arguments (<_OverlappedFuture cancelled>,) after 0 second(s)
DEBUG:quamash.QEventLoop:Adding callback <Handle BaseProactorEventLoop._loop_self_reading(<_OverlappedFuture cancelled>)> with delay 0
DEBUG:asyncio:taking long time to close proactor
.
----------------------------------------------------------------------
Ran 1 test in 1.045s

OK

I'm not at all an expert of the Microsoft world, but our app needs to support Windows that's why I try to fix this error...
Note that with PyQt 5.5, Qt will abort when any exception is not catched anymore. So this will start to get critical if we still have quamash raising exceptions...
Thanks for your help ! (and I love your lib by the way :) )

@Insoleet I guess your test could verify that there are no logged errors? Then it should fail it would seem.

I can't catch this exception from the test because it's catched by PyQt stack (raised after a signal). The test is just a simple use case to show the problem...

@Insoleet Can't you detect that an error has been logged? There's this log line: ERROR:quamash.QEventLoop:Cancelling an overlapped future failed.

Oh you are right.
import sys
import unittest
import asyncio
import time
import logging
import quamash
from quamash import QApplication

class Bug(unittest.TestCase):
    def setUp(self):
        self.qapplication = QApplication([])
        self.lp = quamash.QEventLoop(self.qapplication)
        asyncio.set_event_loop(self.lp)
        self.except_raised = False
        self.lp.set_exception_handler(lambda loop, context: self.exception_handler(loop, context))

    def exception_handler(self, loop, context):
        self.except_raised = True

    def test_bug(self):
        @asyncio.coroutine
        def waiting():
            yield from asyncio.sleep(1)

        self.lp.run_until_complete(waiting())
        try:
            self.lp.close()
        finally:
            asyncio.set_event_loop(None)
        self.assertFalse(self.except_raised)

if __name__ == '__main__':
    logging.basicConfig(stream=sys.stderr)
    logging.getLogger().setLevel(logging.DEBUG)
    unittest.main()

@Insoleet That solution was a bit different from what I initially envisioned, but if it works I think it's better since it's more direct in detecting an exception.

Well as soon as we can reproduce the error... :)
So to say it short :
I did some first analysis there : https://github.com/harvimt/quamash/issues/38#issuecomment-140346302
Also, polling seems to help solving the bug, at least in simple cases like this one. But the unit test suite of our app raise another error after forcing a polling when closing the IocpProactor :
Traceback (most recent call last):
  File "D:\Anaconda3\lib\asyncio\windows_events.py", line 749, in __del__
    self.close()
  File "D:\Dev\Code\quamash\quamash\_windows.py", line 73, in close
    self._poll(1)
  File "D:\Dev\Code\quamash\quamash\_windows.py", line 92, in _poll
    status = _overlapped.GetQueuedCompletionStatus(self._iocp, ms)

You can notice that running this test never ends. Before the exception is raised, a callback is added in quamash.QEventLoop, but it is never called.
The callback is added when canceling the overlapped future :
https://github.com/python/asyncio/blob/master/asyncio/windows_events.py#L62
https://github.com/python/asyncio/blob/master/asyncio/futures.py#L227
The callback uses             self._loop.call_soon(callback, self), and thus calls the QEventLoop's call_soon. The callback is never called because, for some reason, the timers are never triggered.

@Insoleet Do you need help figuring this out?

Yes, this is quite a hard bug. I'm not sure if it's because of quamash reimplementation of IocpProactor, or if it's asyncio having problems...
Closing the loop freezes on this line :
https://github.com/python/asyncio/blob/master/asyncio/windows_events.py#L739
The while is never left, because the _cache is never empty, because quamash's polling never pops items from the cache. In fact, reading the  _overlapped.GetQueuedCompletionStatusalways returns None :
https://github.com/harvimt/quamash/blob/master/quamash/_windows.py#L91
If you have any idea, or try to replicate my analysis by your side that'd be great...

Oh it seems to be a compatibility problem with aiohttp.
The test I suggested earlier is not freezing. But our app tests are. So I tried the following simple test :
import sys
import unittest
import asyncio
import aiohttp
import logging
import quamash
from quamash import QApplication

class Bug(unittest.TestCase):
    def setUp(self):
        self.qapplication = QApplication([])
        self.lp = quamash.QEventLoop(self.qapplication)
        asyncio.set_event_loop(self.lp)
        self.except_raised = False
        self.lp.set_exception_handler(lambda loop, context: self.exception_handler(loop, context))

    def exception_handler(self, loop, context):
        self.except_raised = True

    def test_bug(self):
        @asyncio.coroutine
        def waiting():
            response = yield from aiohttp.get("http://forum.ucoin.io")
            yield from response.release()
            yield from asyncio.sleep(1)

        self.lp.run_until_complete(waiting())
        try:
            self.lp.close()
        finally:
            asyncio.set_event_loop(None)
        self.assertFalse(self.except_raised)

if __name__ == '__main__':
    logging.basicConfig(stream=sys.stderr)
    logging.getLogger().setLevel(logging.DEBUG)
    unittest.main()

Which never ends.

@Insoleet I just ran your latest test on OS X with Quamash 540ab6a, Python 3.5.0, PyQt 5.5 and aiohttp 0.17.3. There were no errors that I could see. Is there any particular way to reproduce?

This is a problem with IOCP, I think it only exists on windows.
On Sun, Sep 20, 2015 at 12:52 PM, Arve Knudsen<EMAIL_ADDRESS>wrote:

@Insoleet https://github.com/Insoleet I just ran your latest test on OS
X with Quamash 540ab6a
https://github.com/harvimt/quamash/commit/540ab6ab04d93f72fe6c5f60c0a8c8f4f134aad7,
Python 3.5.0, PyQt 5.5 and aiohttp 0.17.3. There were no errors that I
could see. Is there any particular way to reproduce?
—
Reply to this email directly or view it on GitHub
https://github.com/harvimt/quamash/pull/44#issuecomment-141827211.

@harvimt Yep, I noticed right after (oops).

But @Insoleet, you say that the test only sometimes hangs? Is there a way to reproduce deterministically?

I did not find a way to provoke the bug 100% of times... But it happened really often. My appveyor tests instance were almost all freezing for example.

I just tested with Python 3.4.0, Quamash 540ab6a, PyQt 5.4.0 and aiohttp 0.17.3 on Windows 8.1, several times. The test doesn't hang for me.

@Insoleet, can you integrate https://github.com/Insoleet/quamash/pull/2? It fixes an exception due to polling while closing.

Well, even after your patch, the test hangs here (Windows 7). The test hangs when we are trying to close the loop.

@Insoleet Yes, the patch doesn't solve that, it fixes another issue.

I think this PR can be closed thanks to @peterazmanov


[Feature Request] Multiple select: minimum limit

Existing Component
Yes
Component Name
Select
Description
It would be nice to have an option to limit the number of selected items from below. I can only think of the use case of 'at least 1', but it should be easy to add for any number (something like :closable="currentNumItems > minimumNumItems" in tag rendering)

@lomereiter
You raised a valuable feature ,  and I met same case before .
The multiply selection limitation always coupling with model and view .
Fortunately with vue.js ,I think we can have a better solution for this .
I am trying to add this feature now .
Thank you.

Sorry, we have no plan to support this.


Update tutorial to include SECRET_KEY for Flask

This PR updates the tutorial to include instructions for setting the SECRET_KEY environment variable in the Flask tutorial, based on user feedback in issue #123961.

@cephalin
Can you review the proposed changes?
Important: When the changes are ready for publication, adding a #sign-off comment is the best way to signal that the PR is ready for the review team to merge.
@superyyrrzz - it looks like you deleted most of the markdown in this aritcle, including the metadata - which is why there are so many errors. You should probably take another look to make sure the changes reflect your intentions, because we won't be able to pass this as is. thanks.
#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

Closed this. Created this accidentally. Sorry for the noise @Jak-MS


Add more version information

This PR adds more version information to packages:

installer
branch
platform

and makes commit hash and date information available for packaged apps.
Closes #4175

@SchrodingersGat please wait for one more commit with merging - I have to extend the docs so I do not forget what which packager code is

New sample output:
# Version Information:
InvenTree-Version: 0.12.0 dev
Django Version: 3.2.19
Commit Hash: 0a788b6a
Commit Date: 2023-06-11
Database: sqlite3
Debug-Mode: False
Deployed using Docker: False
Platform: Linux-5.15.0-67-generic-x86_64-with-glibc2.35
Installer: PKG
Target: ubuntu:20.04
Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.0.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}]

@inventree/triage ready for review and merge


Translating the project to Portuguese

This project is really nice. I think it needs to be translated to Portuguese.
I'll translate each topic by time.

Hai,
It would be nice if you can fork this and add the changes to yourself. I
can't accept the PR as I don't know portuguese and maintaining multiple
solution files and readme will be a mess. You can fork and do it by
yourself maybe I can add the link to your forked repo. What do you think ?
Thanks
AD2001
On Tue, Feb 6, 2024, 6:25 AM n3k00n3 @.***> wrote:

This project is really nice. I think it needs to be translated to
Portuguese.
I'll translate each topic by time.
You can view, comment on, or merge this pull request online at:
https://github.com/DERE-ad2001/Frida-Labs/pull/2
Commit Summary

b96ce2d
https://github.com/DERE-ad2001/Frida-Labs/pull/2/commits/b96ce2dda29855a6fa9dace4c384c5fcf654f2a7
Adicionado README em PT_BR
a4db341
https://github.com/DERE-ad2001/Frida-Labs/pull/2/commits/a4db3414227b366d6b97bc2f7b094027c912c454
Update README_PT.md

File Changes
(1 file https://github.com/DERE-ad2001/Frida-Labs/pull/2/files)

A README_PT.md
https://github.com/DERE-ad2001/Frida-Labs/pull/2/files#diff-c0c3843d696c588e3f152115e781503ead1117498f328861659514cc00d49dda
(31)

Patch Links:

https://github.com/DERE-ad2001/Frida-Labs/pull/2.patch
https://github.com/DERE-ad2001/Frida-Labs/pull/2.diff

—
Reply to this email directly, view it on GitHub
https://github.com/DERE-ad2001/Frida-Labs/pull/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQAAL7UEAPL5JOZE2LZNWEDYSF5QJAVCNFSM6AAAAABC3C4QNWVHI2DSMVQWIX3LMV43ASLTON2WKOZSGEYTSNZTGQYTCNY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Hej Hej!
it's Okay mate. I was thinking to maintain the portuguese version into your repository. But yes, its a little bit complicated once you   need to review each PR and portuguese is not a familiar idiom for you.
I think it could be better as you said.
Thanks mate!


SocketException

Hi I'm getting this error : "SocketException (SocketException: OS Error: Connection refused, errno = 111, address = localhost, port = 53392)."
this is the code I wrote :
Future <List> fetchElaProperty() async {
String url = 'http://localhost:9200/';
final transport =ConsoleHttpTransport(Uri.parse(url));
final client =  elastic.Client(transport);
//in the code below is whre I get the error.
final response = await client.search(
'fproperty',
'_doc',
elastic.Query.term('purpose', ['venta']),
source: true
);
print(response.toMap());
}

This looks like the HTTP port was not open or enabled.


top1 question

sorry for the possibly stupid question) but I'm wondering, since I'm not particularly good at programming. let's say I don't have a video card right now, but I will install this miner on my computer, but in the future I will buy a video card that is suitable for mining. Will the miner work?) Or it doesn't work like that) Sorry for the question

Yes that would work, when the miner runs it checks all the graphic cards and their memory and tries to allocate the required memory and all that.


Does the pdi-git-plugin-1.1.0 plugin work with Azure DevOps?

Does the pdi-git-plugin-1.1.0 plugin work with Azure DevOps? When I'm going to do a push he asks me for the username and password, when I inform my azure username and password nothing happens and asks for the username and password again? Is there a place where I can see a log of what is happening?

nothing happens and asks for the username and password again?

This means "not authorized" error came back from the server.
https://github.com/HiromuHota/pdi-git-plugin/blob/master/src/main/java/org/pentaho/di/git/spoon/model/UIGit.java#L671
I realized that this is not user-friendly because user has no idea why they are asked username/password again. I'll report an issue for this.
To your question:

Does the pdi-git-plugin-1.1.0 plugin work with Azure DevOps?

I think it would work but you have to choose an auth method that pdi-git-plugin-1.1.0 can work with.
This plugin relies on JGit; and according to https://www.eclipse.org/forums/index.php/t/1100497/,

Azure DevOps (formerly known as TFS) out of the box is configured only for NTLM authentication over HTTP.
JGit does not do NTLM, and we have no plans to add support for it.

As suggested by the above url, try SSH.
Another suggestion is to use "Personal Access Token" indicated at https://developercommunity.visualstudio.com/content/problem/626405/jgit-fails-to-authenticate-with-tfs-2013-using-ntl.html.
Hope this helps.

It works on my end. I simply used 'username + password' with the HTTPS-URL to connect to Azure DevOps. I will start testing tomorrow and post any behavior I come across while testing.


Create release from Git tag with GH actions

As title says.

Before that, at least you can tag the commits manually :)
Let's tag 0.10.0


Add support for map type

This PR adds support for using types.map in a query data model.
Closes #18

Thanks for the review! This fix is now included in 1.0.7


Added Backslide reference

I just finished Backslide, a complete CLI tool to ease the creation, editing and exporting of Remark presentation 😋
I added a link reference to it in your readme file, thought that some people might be interested ;)
Thanks for the nice job with Remark BTW! 👍

Nice!


Enable support for MessagePack

Description

Enable support for MessagePack hub protocol.
Usage:

Option 1: Enable MessagePack in the Startup class:    public override void Configure(IFunctionsHostBuilder builder)
    {
        builder.Services.Configure<SignalROptions>(o =>
        {
            // o.ServiceTransportType = ServiceTransportType.Persistent;
            o.MessagePackHubProtocol = new MessagePackHubProtocol();
        });
    }

Option 2: Add a setting in the application settingsAzure:SignalR:HubProtocol:MessagePack:Enabled=true

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please add REST spec PR link to the SDK PR
[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code.
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Microsoft.Azure.WebJobs.Extensions.SignalRService

#auto-merge

/check-enforcer override


bug:Error when publishing an article and uploading the cover

err : io: read/write on closed pipe
The question should be in the configuration of kodo, the domain name expires,？or the public and private keys are changed?


Add "Manage Following" Page

Ticket

Indirectly closes #647
Closes #986

Test
kp dev instance

Good start!
Both buttons now using up too much space on mobile view on following page?
I didn't see followers loaded (unless you've been to the channel). Not sure if bug, or just due to my large list. When  i refreshed, it worked. Then scrolling down, new ones didn't load. I've seen this on and off in other areas, so maybe a deeper and random bug?
3 button menu was hard to click for me, but then started working after (mobile).
On manage page, followed channels text + box + search icon (padding) need alignment.

c96fa9a to a26a602

Fixed sidebar resolving entire subs list.

Wasn't able to replicate the unresponsive 3-dot issue, but I think it's just due to the sidebar resolving all your subs.  I didn't notice this previous because it was being done outside of the component.

Moved away from the claim_search approach and just manually batch-resolve instead.

Too many issues:  slow, some results duplicated in multiple pages, some results missing, full results doesn't match given channel IDs, etc.

Fixed padding issues.


Support Other Languages Build Directories

I noticed on the TODO page that there are currently no plans to support the build systems of any other languages. Would pull requests adding additional support be accepted?

Would pull requests adding additional support be accepted?

Of course! What do you have in mind?

CMake for the moment, but I might be adding a few more to my fork before I start a PR.
I'd also be willing to add the code to verify that the directory really does pertain to the build system in question, by checking for specific sets of files or subdirectories (does it contain Cargo.toml and Cargo.lock, CMakeLists.txt, etc.).

CMake will be most welcome. Any build system really, as long as it doesn't over-complicate the tool with extra stuff (flags, etc.).
I have just added a check for the target folder, so that should be fine now.
You might want to rebase your fork, I've been changing quite a lot of things in the past 48 hours.

Dart generates a .dart_tool directory which can get quite big. Would be good to have an option for that.


Add whoBIRD

Insert URLs to the project here: https://github.com/woheller69/whoBIRD

[x] The projects is active, documented, open source licensed, shows usage from external parties and is directly targeting environmental sustainability. Find more details in the Contribution Guide.

All issues labeled as Good First Issue of the project listed on OpenSustain.tech will be visible on ClimateTriage.com. This is a great way to welcome new community members to your project.
All new projects listed will be posted on our Mastodon channel.

@woheller69


chore: drop Python 3.8 support in the generated project

📚 Documentation preview 📚: https://ss-python--365.org.readthedocs.build/en/365/

Close as #368 merged


Error in rule LONG_LINE in comments

Describe the bug
diktat/diktat-rules/src/main/kotlin/org/cqfn/diktat/ruleset/rules/chapter4/ImmutableValNoVarRule.kt:19:1

Please add details to make it easily reproducible (and so that we don't forget how to reproduce it after two weeks):

which version of diktat source code is used (e.g. commit hash, which can be a link to commit on github)
diktat config file (whether the default one from the repo is used or some settings are changed)
is it reproducible in check or fix mode?

Also, what exactly is the error? Does diktat crash? Does rule work not as expected? Please describe it too.


Error message "ucs-modifier: error: argument -p/--password: expected one argument"

When running the following command: ucs-modifier -u /UCS/CPE-7-20-2022.ucs -m <IP_ADDRESS> -p #EDC3edc$RFV4rfv
I receive the following error: ucs-modifier: error: argument -p/--password: expected one argument

Have you tried with double quotes?
ucs-modifier -u /UCS/CPE-7-20-2022.ucs -m <IP_ADDRESS> -p "#EDC3edc$RFV4rfv"

Have you tried with double quotes? ucs-modifier -u /UCS/CPE-7-20-2022.ucs -m <IP_ADDRESS> -p "#EDC3edc$RFV4rfv"

Yes, still didn't work. I changed the password to 1qaz!QAZ2wsx@WSX and I get the error: bash: !QAZ2wsx@WSX: event not found.

I changed the root password to "default" and authentication works.

I think the best way to solve this would be to use 'PASSWORD' instead of just PASSWORD or "PASSWORD".
This should avoid searching for a command in bash history (with ! char) and avoid trying to use a variable (with $ char)...
Thanks for raising that, we will add 'PASSWORD' instead of just PASSWORD in help and README.
Filled internal: SOLUTIONS-7140
root@9d6a8356cb66:/modifier# ucs-modifier -u /UCS/test.ucs -m <IP_ADDRESS> -p 1qaz!QAZ2wsx@WSX
bash: !QAZ2wsx@WSX: event not found
root@9d6a8356cb66:/modifier# ucs-modifier -u /UCS/test.ucs -m <IP_ADDRESS> -p '1qaz!QAZ2wsx@WSX'
INFO:	Connected (version 2.0, client OpenSSH_7.4)
INFO:	Authentication (publickey) failed.
INFO:	Key swap needed with <IP_ADDRESS>, attempting
INFO:	Connected (version 2.0, client OpenSSH_7.4)
INFO:	Authentication (keyboard-interactive) successful!
INFO:	[chan 0] Opened sftp connection (server version 3)
INFO:	Connected (version 2.0, client OpenSSH_7.4)
INFO:	Authentication (publickey) successful!
INFO:	Key swap completed successfully
INFO:	Platform: C116 Version: 14.1.3-0.0.7
INFO:	Applying patches to the UCS.
INFO:	Comparison saved to: /modifier/config_comparison
INFO:	Patches applied to the UCS.
INFO:	Modification complete.
INFO:	/UCS/test_modified.ucs
root@9d6a8356cb66:/modifier#

root@9d6a8356cb66:/modifier# ucs-modifier -u /UCS/test.ucs -m <IP_ADDRESS> -p #EDC3edc$RFV4rfv
usage: ucs-modifier [-h] -u UCS -m MGMT_IP [-p PASSWORD] [--no-replace-cert] [-o OUTPUT] [-d]
ucs-modifier: error: argument -p/--password: expected one argument
root@9d6a8356cb66:/modifier# ucs-modifier -u /UCS/test.ucs -m <IP_ADDRESS> -p '#EDC3edc$RFV4rfv'
INFO:	Connected (version 2.0, client OpenSSH_7.4)
INFO:	Authentication (publickey) failed.
INFO:	Key swap needed with <IP_ADDRESS>, attempting
INFO:	Connected (version 2.0, client OpenSSH_7.4)
INFO:	Authentication (keyboard-interactive) successful!
INFO:	[chan 0] Opened sftp connection (server version 3)
INFO:	Connected (version 2.0, client OpenSSH_7.4)
INFO:	Authentication (publickey) successful!
INFO:	Key swap completed successfully
INFO:	Platform: C116 Version: 14.1.3-0.0.7
INFO:	Applying patches to the UCS.
INFO:	Comparison saved to: /modifier/config_comparison
INFO:	Patches applied to the UCS.
INFO:	Modification complete.
INFO:	/UCS/test_modified.ucs
root@9d6a8356cb66:/modifier#

README updated to use single quotes for passwords in v1.0.3


Add pipelined function show_queues to MSG_AQ_PKG.

For debugging purposes, this pipelined function has been added.

See 3.4.0


Charging-mode dependent setting for 1P/3P charging

Hi,
I have a question / feature request regarding the switch between 1P/3P charging.
My setting:
Charging in PV mode with limitation to 1P / 3,7 kW for constant charging (not enough solar power to use a 3P only setting). Due to my setting with 1P max, also fast charging is limited to 1P /3,7kW, which is not fast at all :)
With automatic switch 1P/3P my setting is constantly switching between 1P/3P, which I would like to avoid, as it constantly aborts and restarts the charging session in the car.
Desired setting / feature:
I use dynamic pricing (Tibber), so with cheap prices I would like to charge full power with 3P / 11 kW in the "temporary" fast charging and in fast charging mode in general, and stick to 1P for PV mode.
Is there an option to turn on 3P charging for the "fast mode" only? Or limit phases to 1P for the PV mode?
Best regards
Peer

Currently no plan to do this. You can use external automation to switch phases depending on mode.


Password handling

I think this is a better way of handling what is solved in the authenticate branch

@adletaw what do you think

I love this!  Creating a new environment to store the credentials?!  Bodacious!

all credit to @richfitz


We could not confirm your purchase at this time.

Describe the bug

When running docker compose run it fails redeeming with an error
Screenshots or Logs

><EMAIL_ADDRESS>start
> node claimer.js

 2022-05-28 | 18:41: | INFO  | Epicgames Freebies Claimer (1.5.8) by Revadike
 2022-05-28 | 18:41: | INFO  | Found 1 unclaimed freebie(s) for @gmail.com
 2022-05-28 | 18:41: | INFO  | Logged in as ()
 2022-05-28 | 18:41: | ERROR | Failed to claim BioShock: The Collection (Error: We could not confirm your purchase at this time.  Please try again later.)
 2022-05-28 | 18:41:37.885 | INFO  | Logged out of Epic Games

Additional context

Doesn't work on windows either with same config

wrong github repo my guy lmao


Vue Vite Docker WSL2. Internal server error: EACCES: permission denied, stat '/root/.node_modules/plugin-vue:export-helper'

Describe the bug
Error running dev server in WSL2 Docker.
docker-compose:
  frontend:
    build: .
    command: npm run dev
    volumes:
      - ./:/frontend
    ports:
      - '8080:8080'

Dockerfile:
FROM node:lts-alpine
WORKDIR /frontend
COPY package*.json ./
RUN npm install
COPY . .
CMD ["npm", "run", "dev"]

vite.config.js:
import { defineConfig } from 'vite'
import vue from '@vitejs/plugin-vue'

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [vue()],
  server: {
    host: true,
    port: 8080
  }
})

Reproduction
https://github.com/sshiling/Vite-Vue-Docker-WSL2-Bug
System Info
System:
    OS: Linux 4.19 Ubuntu 20.04 LTS (Focal Fossa)
    CPU: (1) x64 Intel(R) Core(TM) i5-9400F CPU @ 2.90GHz
    Memory: 129.67 MB / 979.44 MB
    Container: Yes
    Shell: 5.8 - /usr/bin/zsh
  Binaries:
    Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
    Yarn: 1.22.5 - /usr/bin/yarn
    npm: 6.14.15 - /usr/bin/npm

Used Package Manager
npm
Logs
frontend_1  |   vite v2.7.13 dev server running at:
frontend_1  |
frontend_1  |   > Local:    http://localhost:8080/
frontend_1  |   > Network:  http://<IP_ADDRESS>:8080/
frontend_1  |
frontend_1  |   ready in 259ms.
frontend_1  |
frontend_1  | 2:31:01 PM [vite] Internal server error: EACCES: permission denied, stat '/root/.node_modules/plugin-vue:export-helper'
frontend_1  |   Plugin: vite:import-analysis
frontend_1  |   File: /frontend/src/App.vue
frontend_1  |       at Object.statSync (node:fs:1536:3)
frontend_1  |       at isDirectory (/frontend/node_modules/resolve/lib/sync.js:31:23)
frontend_1  |       at loadNodeModulesSync (/frontend/node_modules/resolve/lib/sync.js:200:17)
frontend_1  |       at Function.resolveSync [as sync] (/frontend/node_modules/resolve/lib/sync.js:107:17)
frontend_1  |       at resolveFrom$3 (/frontend/node_modules/vite/dist/node/chunks/dep-f5552faa.js:3911:29)
frontend_1  |       at resolvePackageData (/frontend/node_modules/vite/dist/node/chunks/dep-f5552faa.js:30046:19)
frontend_1  |       at /frontend/node_modules/vite/dist/node/chunks/dep-f5552faa.js:30426:15
frontend_1  |       at Array.find (<anonymous>)
frontend_1  |       at tryNodeResolve (/frontend/node_modules/vite/dist/node/chunks/dep-f5552faa.js:30425:44)
frontend_1  |       at Context.resolveId (/frontend/node_modules/vite/dist/node/chunks/dep-f5552faa.js:30257:28)

Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Make sure this is a Vite issue and not a framework-specific issue. For example, if it's a Vue SFC related bug, it should likely be reported to https://github.com/vuejs/core instead.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

This is happening to me as well.
But I'm on PopOs, i don't think this is something to do with WSL.
frontend  | error when starting dev server:
frontend  | Error: Build failed with 11 errors:
frontend  | node_modules/.pnpm/resolve@1.22.0/node_modules/resolve/lib/sync.js:31:22: error: [plugin: vite:dep-scan] EACCES: permission denied, stat '/root/.node_modules/@heroicons/react/outline/SearchIcon'
frontend  | node_modules/.pnpm/resolve@1.22.0/node_modules/resolve/lib/sync.js:31:22: error: [plugin: vite:dep-scan] EACCES: permission denied, stat '/root/.node_modules/@heroicons/react/outline/SearchIcon'
frontend  | node_modules/.pnpm/resolve@1.22.0/node_modules/resolve/lib/sync.js:31:22: error: [plugin: vite:dep-scan] EACCES: permission denied, stat '/root/.node_modules/@heroicons/react/outline/SearchIcon'
frontend  | node_modules/.pnpm/resolve@1.22.0/node_modules/resolve/lib/sync.js:31:22: error: [plugin: vite:dep-scan] EACCES: permission denied, stat '/root/.node_modules/dayjs/plugin/relativeTime'
frontend  | node_modules/.pnpm/resolve@1.22.0/node_modules/resolve/lib/sync.js:31:22: error: [plugin: vite:dep-scan] EACCES: permission denied, stat '/root/.node_modules/dayjs/plugin/relativeTime'
frontend  | ...
frontend  |     at failureErrorWithLog (/app/client/node_modules/.pnpm/esbuild@0.13.15/node_modules/esbuild/lib/main.js:1493:15)
frontend  |     at /app/client/node_modules/.pnpm/esbuild@0.13.15/node_modules/esbuild/lib/main.js:1151:28
frontend  |     at runOnEndCallbacks (/app/client/node_modules/.pnpm/esbuild@0.13.15/node_modules/esbuild/lib/main.js:941:63)
frontend  |     at buildResponseToResult (/app/client/node_modules/.pnpm/esbuild@0.13.15/node_modules/esbuild/lib/main.js:1149:7)
frontend  |     at /app/client/node_modules/.pnpm/esbuild@0.13.15/node_modules/esbuild/lib/main.js:1258:14
frontend  |     at /app/client/node_modules/.pnpm/esbuild@0.13.15/node_modules/esbuild/lib/main.js:629:9
frontend  |     at handleIncomingPacket (/app/client/node_modules/.pnpm/esbuild@0.13.15/node_modules/esbuild/lib/main.js:726:9)
frontend  |     at Socket.readFromStdout (/app/client/node_modules/.pnpm/esbuild@0.13.15/node_modules/esbuild/lib/main.js:596:7)
frontend  |     at Socket.emit (node:events:390:28)
frontend  |     at addChunk (node:internal/streams/readable:315:12)
frontend exited with code 1

Getting the same error on Ubuntu 20.04 in combination with docker

Downgrading to 2.6.14 works as a quick workaround but should not be the fix. @patak-dev do you have any solution?

Downgrading to 2.6.14 works as a quick workaround but should not be the fix. @patak-dev do you have any solution?

This works

Just tried yarn install and yarn dev and that works... maybe it's an issue upstream with npm?

same problem, but works fine on node:16 with 2.6.14

Same problem with running docker image node:16.13.2-alpine on WSL2 Ubuntu 20.04 with version 2.8.0 downgrade to 2.6.14 fixed issue.

I still get the error with both node-16 and node-16-alpine using version 2.6.14.
I found a workaround, if you mount your source directory in /root it works. This docker-compose.yml configuration works for me:
version: '3.2'
services:
  frontend:
    image: node:16-alpine
    working_dir: /root
    volumes:
      - ./frontend:/root
    command: npx vite --host

Just tried yarn install and yarn dev and that works... maybe it's an issue upstream with npm?

Using yarn seems resolve the problem.
For context:
Docker: node:16.14-alpine
npm: v8.3.1

It looks like this resolve#pull should be causing the problem.

I still get the error with both node-16 and node-16-alpine using version 2.6.14.
I found a workaround, if you mount your source directory in /root it works. This docker-compose.yml configuration works for me:
version: '3.2'
services:
  frontend:
    image: node:16-alpine
    working_dir: /root
    volumes:
      - ./frontend:/root
    command: npx vite --host

Worked for me but 'Ugh'

Same here on just linux (its not WSL problem). Solved with installing 2.5 version of vite
npm install<EMAIL_ADDRESS>
why i'm doing frontend??? :(

Same here on just linux (its not WSL problem). Solved with installing 2.5 version of vite
npm install<EMAIL_ADDRESS>
why i'm doing frontend??? :(

Which Node version? Also trying to get it to work

node@16 and<EMAIL_ADDRESS>combo is works. :+1:
<EMAIL_ADDRESS>doesn't works well in docker. It show permission denied error message in docker. :-1:

Node@16 & Vite until version 2.7.0-beta.7 works.
Vite 2.7.0-beta.8 does not work because it shows a permission denied error with docker.

It's not an issue with resolve package. You are running container with different user than your mounted project's files owner.
It breaks on vite v2.7.0-beta.8 because fs.statSync() exceptions became preserved.
I don't remember where is line of code exactly, but I fixed this by running docker container with -u 1000 option (where 1000 - uid of project's files owner)

@playmean do you know why @bbbboom PR fixes the issue then? I couldn't try myself, could someone else confirm that the PR is having an effect on your projects?

@patak-dev I have checked now, yes, PR fixes the issue. But I think this is first of all problem with containerized environment, just for notice.

@playmean I thought that in the linked resolve PR, and it looks extremely rare. For the record, we merged https://github.com/vitejs/vite/pull/7612 because the change in resolve is causing real issues without any real bug report to justify it.
I agree that the best would be to follow node, but I think we should do it once we get an issue with a setup that justifies this change. And adding these paths should be accompanied probably with other changes to avoid breaking other use cases, or properly document how to correct them, as the setup looks common enough.


Fluent Validator w/ WebApi Attribute Caching/Persisting Research

So I'm using fluent validators for a project with WebApi and using the [Validator(typeof(Validator))] attribute. I noticed that the validator is only being constructed on the first request. This makes sense as they can be re-used but I was just wondering who is doing this and some more details around it, I looked at the ValidatorFactoryBase and it doesn't seem to be doing it, I couldn't find it anywhere else. Is this something that is being managed by WebApi or you? and is the typical lifecycle of the validator documented anywhere?

The AttributedValidatorFactory caches validators using the InstanceCache:
https://github.com/JeremySkinner/FluentValidation/blob/master/src/FluentValidation/Attributes/AttributedValidatorFactory.cs
https://github.com/JeremySkinner/FluentValidation/blob/master/src/FluentValidation/Internal/InstanceCache.cs
...this ensures that there's only one instance of each validator per
factory, and only 1 factory is created (this is done by the
ModelValidatorProvider), which means that the validators essentially end up
being singletons.
Validators are expensive to instantiate, so this is the approach I'd
recommend...if you're using an ioc container, then setting the validator
lifetimes to singleton is the best approach.
On Saturday, 2 April 2016, Ashton Kinslow<EMAIL_ADDRESS>wrote:

So I'm using fluent validators for a project with WebApi and using the
[Validator(typeof(Validator))] attribute. I noticed that the validator is
only being constructed on the first request. This makes sense as they can
be re-used but I was just wondering who is doing this and some more details
around it, I looked at the ValidatorFactoryBase and it doesn't seem to be
doing it, I couldn't find it anywhere else. Is this something that is being
managed by WebApi or you? and is the typical lifecycle of the validator
documented anywhere?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/JeremySkinner/FluentValidation/issues/236

Thank you this is exactly what I was looking for!