Add an option to prevent using Enter to select completions

When a typed method name is matched exactly with suggestion's, I have a "press Enter twice or click away or press space" overhead for any linter suggestion. I understand the linter suggestion also includes a docstring excerpt, or that a 'complete' method name can be another method name's substring, but my request can be handled as follows:

If typed method matches any linter suggestion exactly, then automatically [Enter] the suggestion upon typing, without consuming the next keystroke - unless the input extends a method's name (i.e. is alphanumeric or underscore)
So, if I type .stem and Enter, I should newline (the Enter isn't consumed by the linter)
Can make this a configurable so current behavior remains an option

Hi @OverLordGoldDragon thanks for the feedback! I think probably having an option for such behavior could be worthy for some people but I'm not sure how complex could it be to implement, what do you guys think @spyder-ide/core-developers ?

The easiest thing to do here is to give an option to have enter not complete it ever. I would activate that as I always use tab to complete.
My only complaint about @OverLordGoldDragon is the difficulty in explaining the option in the preferences, while disabling enter is pretty easy(and covers the use case if you are into 'tab').

[X] Enter accepts code completions. (# Checked by default)

This could go along with disabling "tab" #12682.
As an aside tab will start a completion and accept it but you can't accept the completion with ctrl+space or whatever you set the completion hotkey too. This would be quite important if you disabled 'tab' and 'enter' :-)

@bcolsen How about: "If enabled, Enter will newline instead of code completion" (what else could Enter do?). And yes, I'd be fine with using Tab instead of Enter.

We'll take a look at this for 4.2.0.

I would support this with such Pythonic case:

After "0." I would like to go to the next line. But hitting Enter force me to put first suggestion from autocomplete.
And some other cases when I want to move to newline, instead of using something from autocomplete form.
My recipe would be let user to switch off "Enter" as a hotkey for autocompleting. Tab works nice for such situations and as far as I know is mostly used in others IDEs.

Thanks for the explanation @ishipachev! We'll add an option to configure this in 4.2 for sure.

Another use-case, just to be sure it's covered; prepending self. to variables triggers suggestions as if there's nothing after the .:

Enter should be able to bypass these.

@ccordoba12 I tried both the 4.2.5 and 5.0.1 release but can't find the option to disable enter to complete anywhere. I like to use the future with tab but it's driving me crazy that it is auto completing when I want to return to the next line. I have been searching all over the Internet on how to disable it but can't find anything besides this issue thread which mentions is should be added since 4.2?

Sorry but we haven't had time to add an option for this.

Any update on this? It has been one year since the last message.
This is by far the most annoying issue on Spyder.
Using Enter for newline or Ctrl+Enter  for "run block" often insert unwelcome code instead of executing the desired action.

Hey @RemiDav, sorry we haven't looked at this. But I'll schedule it so we can address it in one of our next versions.

Want to support doing something here. Maybe shift + Enter does not complete and always gives a newline? I like only tab autofills best though.

Is there any development of this issue? Would be nice to turn this off.

@geograz, no, there hasn't been. We'll try to address it in Spyder 6, to be released in the second half of the year.

@geograz, no, there hasn't been. We'll try to address it in Spyder 6, to be released in the second half of the year.

This is still a major nuisance.
Not only is the autocomplete is so aggressive for things it shouldn't even try to autocomplete for, it wouldn't even be a problem if the "Code Completion" keyboard shortcut in the settings could actually be assigned as the sole shortcut.
Let's say I have a parameter that just says dataset = 1 and I have parameters that include numbers (like p0/x0/Plot0 you name it)
If I want to quickly swap to dataset = 0, and run the codeblock using Ctrl+Enter, this autocomplete will sneak in and replace my 0 with the first item in the autocomplete list composed of all variables that contain the letter 0? I cannot count the number of times I have accidentally had "ArithmeticError" autocompleted for when I've tried to run a code block.

@DeltaMod, I understand your frustration and we'll try to implement this feature for Spyder 6.1.0, to be released in the second half of the year (6.0 will be released in a couple of months but we don't have time for that).
In the meantime, you could disable completions on the fly to avoid that annoying behavior. You can do that by going to the menu Tools > Preferences, then selecting the pane Completion and linting > General and finally unchecking the option called Show completions on the fly. Let us know if that works for you.

We'll take a look at this for 4.2.0.

Thanks for the explanation @ishipachev! We'll add an option to configure this in 4.2 for sure.

Then it was 5.3.2, 5.3.3, 5.3.4 ...  now 6.1.0
Realistically, will this ever be fixed? Or there will always be something with higher priority and it will keep being pushed back to 13.1.0  and further?

Sorry for the multiple delays but this is a bit low priority for us because it doesn't affect the way we use Spyder. I develop Spyder with Spyder and haven't encountered this problem so far, but I understand it's annoying for users that evaluate code frequently (which is not my case).
In addition, we didn't want to add new features to the Editor before doing a big refactoring that was planned for a long time (its purpose was to improve interoperability between plugins with a new API we created for Spyder 5). The good news is that that refactoring is finally done (see PR #21353, merged last week). But since we're wrapping things up for Spyder 6.0, we won't have time to address this for that release (as I said above).
However, I'll make sure this lands in 6.1.0 because the conditions are finally there to make it a reality.

Thanks a lot for the details. I'll remain optimistic about it then.


Please add ASCII art for Reborn OS

Description
Reborn is missing its logo's ASCII art. Could it be added?
Logo

Need a screenshot of Neofetch running on Reborn OS.


Posseidon tests failing

Hey, just to report the Poseidon tests are failing:
alfredogarcia@alfredos-mbp keelung-stdlib % stack test
keelung-stdlib> test (suite: keelung-stdlib-test)

Tests
  Interpreted
    1:
keelung-stdlib> Test suite keelung-stdlib-test failed
Test suite failure for package keelung-stdlib-<IP_ADDRESS>
    keelung-stdlib-test:  exited with: ExitFailure (-11)
Logs printed to console

alfredogarcia@alfredos-mbp keelung-stdlib %

I commented out all the tests except for the first 2 in here and they pass so the problem seems to be in the larger ones:
alfredogarcia@alfredos-mbp keelung-stdlib % stack test
keelung-stdlib> test (suite: keelung-stdlib-test)

Tests
  Interpreted
    1: [18586133768512220936620570745912940619677854269274689475585506675881198879027]
[18586133768512220936620570745912940619677854269274689475585506675881198879027]
OK (0.03s)
    2: [12326503012965816391338144612242952408728683609716147019497703475006801258307]
[12326503012965816391338144612242952408728683609716147019497703475006801258307]
OK (0.04s)

All 2 tests passed (0.04s)

keelung-stdlib> Test suite keelung-stdlib-test passed
alfredogarcia@alfredos-mbp keelung-stdlib %

I am on a mac, unsure if that could be an issue. I might try in linux soon.

Looks like the same issue as in https://github.com/btq-ag/keelung-compiler/issues/35

Looks like the same issue as in https://github.com/btq-ag/keelung-compiler/issues/35

Thanks, if this is the case, it is good to know is unrelated to what was done in my project.


remove unnecessary App.js file in the cra templates.

remove the one in the root. we only want the one in /components.

https://github.com/fs-webdev/create-react-app/pull/7


PlebToken Logo

{
"chainId": 43114,
"address": "0x625fc9bb971BB305A2Ad63252665DcFE9098bEE9",
"decimals": 18,
"name": "PlebToken",
"symbol": "PLEB",
"tags": [
"DeFi"
],
"logoURI": "https://raw.githubusercontent.com/traderjoe-xyz/joe-tokenlists/main/logos/0x625fc9bb971BB305A2Ad63252665DcFE9098bEE9/logo.png"
},

pls create a new pr w/ just the logo


[Packet] sig-storage-local-static-provisioner recently stopped working

At some point between my last known working configuration of Lokomotive (56acc133cddedd8756deeb) and current master (25123442a162cd3eb482)
sig-storage-local-static-provisioner stopped working

the provisioner starts correctly, finds the block device pool that I created in /mnt/disks and adds them to the cache.
the application starts correctly and binds a physical volume claim to a physical volume when asked to do so
wait a minute or so, and it all times out with MountVolume.NewMounter initialization failed for volume "local-pv-7f70b248" : path "/mnt/local/vol1" does not exist

ssh into the host, disk is there, disk is accessible, permissions are correct (tried 777 -R just in case)
So provisioner, block device, detection of disks, kubernetes pod security profiles, etc. Everything seems to work and thinks it should be working except that something (I'm not 100% sure which component, CSI? Kubelet?) can't access the disk in order to actually finish the mounting 'loop'
(probably relevant, the cleanup script that the provisioner runs after deleting a pvc (some variation of rm -rf path_that_was_mounted does work, although I don't know if that's executed on the host or in a container)
Go back to 56acc133, everything works again.
The only hint I can find is regarding containerized kubelets but when I checked the kubelet systemd unit file /mnt looked like it was accessable, although the kubelet running docker didnt (rkt and docker kubelet?)
Before I dive into this further, are you aware of any changes that could have caused this?
edit: how to recreate, bind mount a block device into /mnt/disks, helm install the static provisioner as per the docs and try to claim it via a deployment. Let me know if you need some example config, although it's 99% what's in the installation guide

@DGollings thanks for reporting. I suspect that might be a regression of kubelet running as a DaemonSet. Could you try removing the kubelet DaemonSet running in kube-system namespace? If you do so, host's kubelet should take over.

Will do so in a bit, thanks

@invidian can confirm that deleting the daemonset kubelet helps

and can also confirm that editing the kubelet daemonset config, adding
        - mountPath: /mnt
          name: mnt

and
      - hostPath:
          path: /mnt
          type: ""
        name: mnt

also works

Awesome, thanks for the report!


Allow partially populated single rank distributed variables by default

If any distributed variables are set, and they match the single rank defaults, then populate the remaining single rank defaults. Before, if any variables were set, then the reset would not be populated, even if they matched the single rank defaults. An MCLI change that set LOCAL_WORLD_SIZE without the other variables broke running single-rank gpu tests.
Also removed a warning about configuring distributed with just one rank, as this is expected behavior when using DeepSpeed.

Tested this change manually by running:
import os
from datetime import timedelta
import composer.utils.dist

os.environ['LOCAL_RANK'] = '0'

composer.utils.dist.initialize_dist('gloo', timedelta(seconds=5))

(Cannot unit test this, as distributed is configured globally for all unit tests, due to a PyTorch bug with destroying distributed process groups.)

I'd prefer if LOCAL_WORLD_SIZE were singled out as the only env var that can appear without all the others being provided. But I'm fine with this, too.

Discussed offline; will leave as-is for now to keep the code path simpler.


Implement cargo crev fetch all.

I think we should eventually improve on it (explained in #65), but a bunch of it was implemented by @rffrancon . Let's keep this open though.

From @dpc in PR #65 :

We should first traverse all git repos and update them (remembering which one we updated), then we should load everything into trustdb and update/fetch urls that we haven't yet, and do it recursively until we have no url left.

Done 08145c4de5c850621928f4fec7eded3419715a85


Inaccuracies and crashes in logarithmic mode in the Area Chart

Description
I found a few issues in the logarithmic mode in the y axis:

when using a simple series with two values distant, let's say [100, 39], I see two issues - the 100 value is below Y=100 on the axis, and the 39 is below the entire graph
similarly, when using the values [1,2] - the 1 is on the Y=2 line, and the 2 is outside of the graph
when using a series with small or identical numbers (let's say [1,1] or [0,0]), the graph crashes or display nothing

Steps to Reproduce

Create an area chart with the most basic config, set logarithmic mode in the yaxis, and replace the series values as I demonstrated (see the specific values in the codepen/description/screenshots).

Expected Behavior

No crashes
The y value should be aligned with the values on the y axis

Actual Behavior

Crashes on some values
When it doesn't crash, the y value isn't properly aligned with the y axis

Screenshots

Reproduction Link
https://codepen.io/Nadav-Peled/pen/QWezjzr?editors=0010%5D

You code pen link is broken, can you please fix it?

Yes, I fixed the link.
The text was correct, it's https://codepen.io/Nadav-Peled/pen/QWezjzr?editors=0010


Start Debugging with js file outside of project results in wrong path

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

VS Code Version:$ code --version
1.56.2
054a9295330880ed74ceaedda236253b4f39a335
x64

OS Version:$ ver

Microsoft Windows [Version 10.0.19043.985]

Steps to Reproduce:

make sure node.exe is on your path
git clone https://github.com/aaronla-ms/bug-repros.git
cd bug-repros\vscode-lost\src\example
code .
in VSCode, open file ....\out\Debug-x64\example.out.js
Click Run > Start Debugging > Node.js

Expected:
Correct script is run, successfully
Actual:
Does not run script. Uses wrong path, and prints following error in Debug Console window:

C:\toolbin\nodejs\node.exe ..\out\Debug-x64\example.out.js
Process exited with code 1
Uncaught Error: Cannot find module 'c:\repos\aaronla-ms\bug-repros\vscode-lost\src\out\Debug-x64\example.out.js'

Notice that we did not open "vscode-lost\src\out", we opened a file from "vscode-lost\out". The path is wrong.

/jsDebugLogs

Thanks for the repro!

/jsDebugLogs

Can you be more specific? Is this an argument to be provided to code.exe when launched? Does this go into launch.json?

That's not necessary, I found the issue with the instructions you provided


eslint-plugin-redos cache config is not working

What is the problem?
Activating the cache in eslint-plugin-redos like documented in the recheck docs causes an eslint validation error.
Configuration for rule "redos/no-vulnerable" is invalid:
        Value {"cache":true} should NOT have additional properties.

.eslintrc
  plugins: ['redos'],
  rules: {
    'redos/no-vulnerable': ['error', { cache: true }],
  }

Example on stackblitz.com
How to fix the problem?
(?)
Related issues

Your eslint-plugin-redos seems to be old. cache option was added from 4.5.0-beta.1, and the latest version is 4.5.0-beta.4, but your example uses 4.4.5. Could you check the version?

Using a 4.5.0-beta.1+ version solved the issue. Thanks for the fast reply.


pd.read_excel() has some parameters incorrectly documented

Environment data

Language Server version: 2020.9.5
OS and version: Windows 10
Python version (& distribution if applicable, e.g. Anaconda): Anaconda 3.7.5

Code Snippet / Additional information
The stubs for read_excel have some errors with respect to the header and skiprows arguments.  The following diffs in the file dist/bundled-stubs/pandas/io/excel/_base.pyi fix these issues:
diff _base.pyi.ORIG _base.pyi
10c10
<     header: Union[int, Sequence[int]] = ...,
---
>     header: Optional[Union[int, Sequence[int]]] = ...,
20c20
<     skiprows: Optional[Sequence[int]] = ...,
---
>     skiprows: Optional[Union[Sequence[int], int, Callable]] = ...,
271c271
<     header: Union[int, Sequence[int]] = ...,
---
>     header: Optional[Union[int, Sequence[int]]] = ...,
281c281
<     skiprows: Optional[Sequence[int]] = ...,
---
>     skiprows: Optional[Union[Sequence[int], int, Callable]] = ...,

Details on why these changes are needed:

For header, the value None is allowed
For skiprows, the docs need to be updated.  See https://github.com/pandas-dev/pandas/issues/36435

Note - when I first reported this, I thought that sheetname was wrong, but now I see what the @overload is doing, so all is well.  Updated the original text above to remove that part.

For skiprows, this is motivation to start making PRs against pandas to inline these types or we'll be whacking moles endlessly.

This issue has been fixed in version 2020.9.6, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/master/CHANGELOG.md#202096-23-september-2020


Character sheets do not open with 0.8.3 Beta version of Foundry

Sheets do not open after clicking them if Foundry version is 0.8.x

Thanks for the update, we haven't done any testing with a 0.8 point X foundry version yet. It's the next thing on my list after the current three or four things on my list :-)￼

Now Actor can't be created with this error
TypeError: this.items.entries is not iterable
    at GurpsActor._applyItemBonuses (actor.js:93)
    at GurpsActor.calculateDerivedValues (actor.js:48)
    at GurpsActor.prepareDerivedData (actor.js:33)
    at GurpsActor.prepareData (foundry.js:9283)
    at GurpsActor.prepareData (actor.js:28)
    at GurpsActor._initialize (foundry.js:9099)
    at new Document (document.mjs:51)
    at new BaseActor (documents.mjs:65)
    at new <anonymous> (foundry.js:9073)
    at new Actor (foundry.js:11930)

Will be working in 0.10.0


⚠ Jenkins Plugins Artifactory has degraded performance

In 1c9b605, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1213 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 2086703 after 42 minutes.


Adding K8s FAQ

@deitch as requested, here is your PING in the PR.

There is no content in the file?

sorry, @deitch i made the magic happen. should be present now.


search function not working

Looks like the search function (which you get when the user has >1 devices associated with them in Jamf) seems to be broken. Any suggestion re. how to troubleshoot?

Correction:
I got it to work (turns out the account I was using to authenticate didn't have appropriate permissions) but the results are getting pulled, in-frame, in JSON format.


Avoid doing console.error

This is not really a bug, nor a feature request, so I haven't followed any of the templates.
It seems console.error is being used in several situations, e.g.: https://github.com/cloudevents/sdk-javascript/blob/6cd310c14168013a4298f87fd8ec3ef51782d7ce/src/event/cloudevent.ts#L170.
In most scenarios, these console.error calls are unnecessary as errors will be thrown anyway, that should be handled by devs consuming this library. In other situations, errors aren't thrown, and these messages are useful. However, most devs are using custom loggers (like JSON loggers), and would like to be able to customize the logging behavior.

Thanks @satazor for opening this issue. It actually looks like there are only two calls to console.error() - the one you pointed out, and this one
https://github.com/cloudevents/sdk-javascript/blob/6cd310c14168013a4298f87fd8ec3ef51782d7ce/src/message/http/index.ts#L51
I think probably the one you note is the only one that should be removed, as the one in src/messages/http is informational and an exception isn't thrown.

@lance 👍
For informal logs, please consider adding the ability to specify the log interface (maybe the same interface as console), so that we can override with custom loggers.


kbfs: first impressions; not a bug report, just some feedback

I've just started using kbfs on a new install of El Capitan, mainly as a way of saving private data as a backup and for access on other systems (I know you don't guarantee preservation, but it's not the only backup).  Behaviour has been flawless, no bugs or glitches.
As you warned, performance isn't sparkling, but for simple text notes is quite adequate.
I tried switching my Notational Velocity to use the keybase private file area, and for the time being it's not really quick enough - it tends to make the system freeze for several seconds at a time while typing.  I'll hold off using notational velocity routinely in this way, but as an additional route for backup/sharing across systems it seems just fine.
For me, the interface (file system) works really well, and the lack of a GUI is not an impediment.  If anything, a simple "login" app might smooth the way, but beyond that the file system interface seems to work a treat.
Mostly: great work!  I look forward too seeing how this evolves - I can see it being really useful.
my log id: e3ddcea0be5f2ca79ae0f51c

Thanks for the feedback!  We have plans for fixing both of these:

In the medium-term, we plan to use write caching so that the operating system returns success to your apps straight away and then syncs in the background, eliminating lag.  It'll take a while to get this right.

In the short-term, we're adding a GUI for login to the app.


Metadata created in Editor should provide correct CSW-URL in OwnCollection

Example: When started locally with a correctly configured local CSW, the URL in "my collection" still points to "smart-project.info". (might be a backend-bug)
see also: https://github.com/ZGIS/smart-portal-backend/issues/20

That would be here: https://github.com/ZGIS/smart-portal-backend/blob/master/app/services/OwcCollectionsService.scala#L149-L154

Ok, let's just start with adding URL to signature


Problem with npm install

Been having trouble installing express-validator today. Below is the error.
npm http 404 https://registry.npmjs.org/types/express
npm http 404 https://registry.npmjs.org/types/bluebird
npm ERR! TypeError: Cannot read property 'latest' of undefined
npm ERR!     at next (/usr/share/npm/lib/cache.js:687:35)
npm ERR!     at /usr/share/npm/lib/cache.js:675:5
npm ERR!     at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:142:7)
npm ERR!     at /usr/lib/nodejs/graceful-fs/polyfills.js:133:7
npm ERR!     at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR<EMAIL_ADDRESS>
npm ERR! System Linux 3.13.0-92-generic
npm ERR! command "/usr/bin/nodejs" "/usr/bin/npm" "install"<EMAIL_ADDRESS>npm ERR! cwd /home/tyler/webapp
npm ERR! node -v v0.10.25
npm ERR! npm -v 1.3.10
npm ERR! type non_object_property_load
npm ERR! TypeError: Cannot read property 'latest' of undefined
npm ERR!     at next (/usr/share/npm/lib/cache.js:687:35)
npm ERR!     at /usr/share/npm/lib/cache.js:675:5
npm ERR!     at saved (/usr/share/npm/node_modules/npm-registry-client/lib/get.js:142:7)
npm ERR!     at /usr/lib/nodejs/graceful-fs/polyfills.js:133:7
npm ERR!     at Object.oncomplete (fs.js:107:15)
npm ERR! If you need help, you may report this log at:
npm ERR!     <http://github.com/isaacs/npm/issues>
npm ERR! or email it to:
npm ERR<EMAIL_ADDRESS>
Any Ideas?

No idea. This is definitely not related to express-validator itself.
But I highly recommend you to use a newer Node.js version, as we have been providing support only to Node 4+.


Automate manaless champion list

I could be wrong, but it looks like data/manaless.json is maintained manually. I think in getChamps you're already downloading all the champ info ( http://ddragon.leagueoflegends.com/cdn/5.13.1/data/en_US/champion.json for example), and you should be able to determine from a champ's partype if they're manaless because it will be something other than Mana.

Ah well isn't that a great find! Thanks, I'll add that to next version. :)


Can't resolve plugins from plugin repository after Gradle 4.3 upgrade

Expected Behavior
When running my build, plugins declared in the plugins closure should be resolved from the Gradle Plugins Repository.
Current Behavior
I get an error when my build starts up
Context
All I did was upgrade from Gradle 4.2.1 to Gradle 4.3 and all of a sudden I am no longer able to run my build.
In Gradle 4.2.1 my build is fine, but with Gradle 4.3 my build fails with
FAILURE: Build failed with an exception.

* Where:
Build file '/Users/edeandre/workspaces/Stuff/my-gradle/build.gradle' line: 13

* What went wrong:
Error resolving plugin [id: 'com.jfrog.artifactory', version: '4.4.9']
> Could not GET 'https://plugins.gradle.org/api/gradle/4.3/plugin/use/com.jfrog.artifactory/4.4.9'.
   > Connect to plugins.gradle.org:443 [plugins.gradle.org/<IP_ADDRESS>, plugins.gradle.org/<IP_ADDRESS>, plugins.gradle.org/<IP_ADDRESS>, plugins.gradle.org/<IP_ADDRESS>, plugins.gradle.org/<IP_ADDRESS>, plugins.gradle.org/2400:cb00:2048:1:0:0:6810:afa6, plugins.gradle.org/2400:cb00:2048:1:0:0:6810:aba6, plugins.gradle.org/2400:cb00:2048:1:0:0:6810:aea6, plugins.gradle.org/2400:cb00:2048:1:0:0:6810:aca6, plugins.gradle.org/2400:cb00:2048:1:0:0:6810:ada6] failed: No route to host (connect failed)

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

 In fact, my project does not have a settings.gradle file.

This looks like a network issue. Does it still exist?

Yes it does. I can immediately switch back to Gradle 4.2.1 and everything is fine. As soon as I switch to 4.3 I experience this.

That's incredibly weird! We'll investigate it ASAP.

Thanks! I am behind a corporate proxy so not sure if there is something I need to do for https proxy that is new with 4.3?

AFAIK, no.

One more thing, do you always fail with 4.3 or intermittently? If this can be reproduced each time, could you please provide us with detailed stacktrace (run your build with -s again)? That would help a lot.

I will certainly do that for you in the morning. It always fails with 4.3.

Thanks!

I experienced a similar issue.  According to the 4.3 release notes, gradle no longer supports looking in multiple repositories for dependencies: https://docs.gradle.org/4.3/release-notes.html#avoid-checking-other-repositories-when-dependency-resolution-in-one-repository-fails
So, if your build.gradle includes a repository section with multiple repos, you will now get dependency resolution failures.  Looks like I'm stuck at 4.2.1.

For me my issue is with the plug-in repository. I have no settings.gradle so just the out of box defaults.
That being said - if Gradle 4.3 doesn't allow dependencies to come from multiple repos then that will also be a show stopper for us. We absolutely require the ability to resolve from multiple repos. We are a global company and have many internal Artifactory servers distributed globally.

if Gradle 4.3 doesn't allow dependencies to come from multiple repos then that will also be a show stopper for us. We absolutely require the ability to resolve from multiple repos.

That's not what dependency resolution in one repository fails means. I admit the wording could have been chosen better.
We fail if an actual connection error occurs (NOT when the dependency does not exist, which is not considered an error). https://plugins.gradle.org/api/gradle/4.3/plugin/use/com.jfrog.artifactory/4.4.9 does exist. but there is a connection error when Gradle tries to retrieve it.
So I suspect that this is an error caused by your proxy configuration @edeandrea which was "hidden" before.

This needs to be resolved ASAP, otherwise Gradle 4.3 is pretty much unusable.
After upgrading to 4.3, several of our Android projects are not able to resolve dependencies to libraries, mainly those from small developers that are in their custom repositories and not pushed to the big ones.
Which should not be required as a change "Avoid checking other repositories when dependency resolution in one repository fails" forces to.
TL;DR [WARNING] do not upgrade to Gradle 4.3 if you are using multiple repositories, otherwise you would not be able to build your projects.

@FrancescoCapari thanks for the feedback.
As stated above, Gradle should not fail if a dependency does not exist at all in a repository. Only if the dependency exists but other errors occur. Of course there could be a problem that this behavior is not implemented correctly.
Can you share the error messages you are seeing? We need to find out what broke exactly in order to fix the problem.

Very weird - today I came in & can't seem to reproduce. I blew away my ~/.gradle/caches folder & re-ran my build and everything seems to work fine. Very strange - I spent hours trying to figure out what was wrong yesterday...

Closing as the original issue can't be reproduced.
@danlange @FrancescoCapari as Jendrik said, having multiple repositories is absolutely supported. The only change is that we fail if a repository returns a problem code like "forbidden" or "internal server error". If it returns "not found", we try the next one as usual.
Please check your proxy and authentication settings, your servers might be returning wrong status codes. If the problem persists, please open a new issue with reproduction instructions.

I am having same issue on Gentoo with gradle 3.4.1:
unik /var/lib/layman/archenroot/app-misc/freeplane # eix gradle
[I] dev-java/gradle-bin
     Available versions:
     (0)    (~)1.8[1]
     (3.3)  (~)3.3
     (3.4.1) (~)3.4.1
       {doc examples source ELIBC="FreeBSD"}
     Installed versions:  3.4.1(3.4.1)(04:09:57 AM 03/02/2018)(-doc -examples -source ELIBC="-FreeBSD")
     Homepage:            http://www.gradle.org/
     Description:         A project automation and build tool with a Groovy based DSL

Message:
> Configuring > 0/13 projects > root project > Compiling /var/tmp/portage/app-misc/freeplane-1.6.13/work/freeplane-1.6.13/build.gradle into local build cache > Compiling build file '/var/tmp/porta
FAILURE: Build failed with an exception.

* Where:
Build file '/var/tmp/portage/app-misc/freeplane-1.6.13/work/freeplane-1.6.13/build.gradle' line: 2

* What went wrong:
Error resolving plugin [id: 'nebula.ospackage', version: '4.4.0']
> Plugin cannot be resolved from https://plugins.gradle.org/api/gradle because Gradle is running in offline mode

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.

BUILD FAILED

Total time: 3.005 secs
 * ERROR: app-misc/freeplane-1.6.13::archenroot failed (compile phase):
 *   (no error message)
 *
 * Call stack:
 *     ebuild.sh, line 124:  Called src_compile
 *   environment, line 3602:  Called die
 * The specific snippet of code:
 *       ${GRADLE} build -x check -x test || die
 *
 * If you need support, post the output of `emerge --info '=app-misc/freeplane-1.6.13::archenroot'`,
 * the complete build log and the output of `emerge -pqv '=app-misc/freeplane-1.6.13::archenroot'`.
!!! When you file a bug report, please include the following information:
GENTOO_VM=  CLASSPATH="" JAVA_HOME="/etc/java-config-2/current-system-vm"
JAVACFLAGS="" COMPILER=""
and of course, the output of emerge --info =freeplane-1.6.13
 * The complete build log is located at '/var/tmp/portage/app-misc/freeplane-1.6.13/temp/build.log'.
 * The ebuild environment file is located at '/var/tmp/portage/app-misc/freeplane-1.6.13/temp/environment'.
 * Working directory: '/var/tmp/portage/app-misc/freeplane-1.6.13/work/freeplane-1.6.13'
 * S: '/var/tmp/portage/app-misc/freeplane-1.6.13/work/freeplane-1.6.13'

Otherwise I found the plugin in repo:
https://plugins.gradle.org/plugin/nebula.ospackage/4.4.0

@archenroot That build is running with --offline, so it cannot build without having a local copy of the plugin somewhere (e.g., run once without --offline).

My first Gradle 4.6 build in a CI server behind corporate proxy failed with
Error resolving plugin [id: 'org.sonarqube', version: '2.6.2']
> Could not resolve all dependencies for configuration 'detachedConfiguration1'.
   > Could not determine artifacts for org.sonarqube:org.sonarqube.gradle.plugin:2.6.2
      > Could not get resource 'https://plugins.gradle.org/m2/org/sonarqube/org.sonarqube.gradle.plugin/2.6.2/org.sonarqube.gradle.plugin-2.6.2.jar'.
         > Could not HEAD 'https://plugins.gradle.org/m2/org/sonarqube/org.sonarqube.gradle.plugin/2.6.2/org.sonarqube.gradle.plugin-2.6.2.jar'. Received status code 403 from server: Forbidden

Downgrading to 4.2.1 fixed this particular error, but lead to another similar problem for another (transitive) build plugin dependency. Downgrading to 4.1 where I started fixed them both, possibly because of some previously created cache. I don't have control over the proxy configuration or the local ~/.gradle in the CI server, and I don't know why the 403 occurs in the first place. Local builds work fine with all of the aforementioned versions.

@eriwen thanks for your response. I'll try this when I can.
The resource url seems to redirect (303) to https://jcenter.bintray.com/org/sonarqube/org.sonarqube.gradle.plugin/2.6.2/org.sonarqube.gradle.plugin-2.6.2.jar, which in turn redirects (302) to https://repo.jfrog.org/artifactory/libs-release-bintray/org/sonarqube/org.sonarqube.gradle.plugin/2.6.2/org.sonarqube.gradle.plugin-2.6.2.jar?referrer, which responds with 404, with a json-formatted message "Could not find resource" . Indeed, the index at https://repo.jfrog.org/artifactory/libs-release-bintray/org/ doesn't list a sonarqube/ subdirectory.
This seems odd but doesn't explain the 403 response. Maybe the corporate proxy has whitelisted only some of those servers and not all of them? I feel that would explain the 403 but not the sudden breakage and remedy by downgrading, unless the plugin jars and dependencies come from some cache in the CI server.

I cannot say what a proxy might be doing, but I imagine you can eliminate any local artifact cache from the scenario by using a custom GRADLE_USER_HOME. See
https://docs.gradle.org/current/userguide/command_line_interface.html#_environment_options and https://docs.gradle.org/current/userguide/build_environment.html#sec:gradle_environment_variables for ways to configure this.

@jruuttun Also, if this is something you really want to dig in and fix, you could also have your CI build create a build scan and you can check the network activity among other facets to debug this. Here's an example. It might give you a hint at what's really going on.
It sounds like you're in a corporate environment, so if you need to keep your project data private, you can run a Gradle Enterprise trial in Docker and that might help you out and not cost you money.

Adding the -g [other than ~/.gradle] option to the CI build revealed that the problem had indeed been hiding behind the local artifact cache for some time, and now broke the build even in 4.1. I still don't quite understand it but I should probably find a way of getting both in-house plugins and those applied using the plugins DSL resolved via the internal Nexus server, so that the build would not be dependent on whitelisting plugin source repositories in the beloved proxy. Thanks again for tips!

@jruuttun The Gradle Plugin Portal is mirror-able, if that helps you in any way here.

Thanks. The problem went away after whitelisting repo.jfrog.org in the proxy.
I think the breakage after upgrading from 4.1 could have been a combined effect of #3799 and this change, making gradle try to reload all plugin artifacts and failing fast because of the proxy-originated 403.

I have the same problem, I tried both Gratle 3.4.1 and 4.8.1, the problem seems to be the same.
Here is the issue I opened on Orchid: https://github.com/JavaEden/Orchid/issues/150#issuecomment-405328911
I don't use any proxy or VPN.

@cgorgulla That's a different issue and not caused by Gradle. There's some discussion about it on StackOverflow.

To me this seems to be issue with JAVA8, where as when i use JAVA7 it works fine.

Te me helped to add pluginManagement section to the start ot settings.gradle:
pluginManagement {
    repositories {
        maven { url "https://plugins.gradle.org/m2/" }
        gradlePluginPortal()
    }
}

To me helped to add pluginManagement section to the start of the settings.gradle file:
pluginManagement {
    repositories {
        maven { url "https://plugins.gradle.org/m2/" }
        gradlePluginPortal()
    }
}

Thanks!! That help me a lot!

for me, the answer was this: https://spring.io/blog/2019/09/16/goodbye-http-repo-spring-use-https

for my best (but small) understanding
a build shall use all the specified repositories in the order given. (of course only for the use case they were intended by the specs.)
if one of the repositories fails to respond then this is sort of a fatal error because then there is the chance that some later order repository might provide a similar package (by name) that is different (by content). thus if not failing hard the build result might be different from what was requested (and expected) by the creating and invoking user.

buildscript {
dependencies {
classpath "...."

Please dont make this issue so long by saying that , "I have same isssue or whatever...",
Try to solve it.
My project working fine with this method in new android versions gradle 4.2 also,,...

@archenroot That build is running with --offline, so it cannot build without having a local copy of the plugin somewhere (e.g., run once without --offline).

This workarounds the problem actually for someone who's behind an enterprise proxy


Explicit DB threading in the wallet

This is a resurrection of #2360 using a branch hosted in IOHK github.

@nc6 These are the tests I have conducted:

[X] Importing a wallet works
[X] Creating a new wallet works
[X] Sending Txs between two wallet works
[X] Generating a new Cardano address works
[X] Deleting a wallet works
[X] Restoring a wallet works

Looking good! 🎉  cc @dcoutts


awesome_nested_fields Add button unresponsive with some blueprint layouts

This took me a while to figure out. I'm using blueprint, Devise, and awesome_nested_fields on a new project. I stripped out most of the form elements here, so that you can see a simpler case of the add button not working. All else being equal, the awesome_nested_fields Add button does not work when I have the following layout on a page.
Look for the HTML comments on the 2nd and 5th lines. Remove those HTML elements and the awesome_nested_fields add button works again. (Don't remove the content between the HTML elements -- just remove the
...
 tags.)

      <%= form_for(resource, :as => resource_name, :url => registration_path(resource_name), :html => { :method => :put }) do |f| %>
      <%= devise_error_messages! %>

Your Dependents

          <%= f.nested_fields_for :people do |f| %>
            <fieldset class="item">
              <%= f.label :first_name %>
              <%= f.text_field :first_name %>
              remove
              <%= f.hidden_field :id %>
              <%= f.hidden_field :_destroy %>
            </fieldset>
          <% end %>

        add dependent

<%= f.label :current_password %> (we need your current password to confirm your changes)

          <%= f.password_field :current_password, :class => "title" %>

<%= f.submit "Save Changes" %>

        <% end %>

This is certainly related with the bluprint .container class. Now I realize it is not a good name to a default.
I'm checking this out.

Could you clarify how to set the container to something other than the .container class? Would it be using code like the following in the application.js file?
$(document).ready(function(e) {
  $('FORM').nestedFields(
	containerSelector: 'nest_container'
	);
});

Nevermind...  I mistakenly put the div in question outside of the form and it wasn't working

Nice Clay. I'll still investigate about issues with Blueprint, I think they
can occur.
On Fri, Nov 25, 2011 at 4:13 PM, Clay H <
<EMAIL_ADDRESS>
wrote:

Nevermind...  I mistakenly put the div in question outside of the form and
it wasn't working

Reply to this email directly or view it on GitHub:
https://github.com/lailsonbm/awesome_nested_fields/issues/4#issuecomment-2877337

I just replaced the default containerSelector to .items, .container, so now you can use the items class instead of container and avoid issues with CSS frameworks like Blueprint. I think this closes this issue.


Styles are not applied on expo-web

Describe the bug
Classnames are applied to html elements however they have no effect on style. I believe it's related with some versioning. It started to be unavailable after I upgraded couple of packages probably these ones:
    "expo": "^46.0.0",
    "react-native-web": "~0.18.7"

To Reproduce
I have created a simple repo which I try to change bg color to green which doesn't work.
https://github.com/suchcodemuchwow/nativewind-error
I have run this command:
expo start --web --https --clear
Expected behavior
Styles are applied visually.
Expo Snack
If applicable, add a link to an Expo snack demonstrating the issue. There are multiple example snacks available at nativewind.dev.
<EMAIL_ADDRESS>Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

You are using RNW 0.18, so NativeWind switches to CSS. You will need to generate your .css using Tailwind CLI and import it like a normal web project.

Alternatively you can change back to the previous behaviour, but CSS offers more features and better performance.
https://www.nativewind.dev/quick-starts/expo#expo-sdk-45

Could you please point me in the right docs section to generating css and
importing it or provide an example ? I couldn’t find unfortunately.
On Mon, 8 Aug 2022 at 00:38, Mark Lawlor @.***> wrote:

Alternatively you can change back to the previous behaviour, but CSS
offers more features and better performance.
https://www.nativewind.dev/quick-starts/expo#expo-sdk-45
—
Reply to this email directly, view it on GitHub
https://github.com/marklawlor/nativewind/issues/154#issuecomment-1207490221,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACJZ4AIJASFAW7E2ESUM7CTVYAUG3ANCNFSM552USVTA
.
You are receiving this because you authored the thread.Message ID:
@.***>

For RNW 0.18, NativeWind is just a compatibility layer around Tailwind CSS. You need to follow normal Tailwind CSS installation.
https://tailwindcss.com/docs/installation

I just ran into the same issue and could use a bit more guidance as well re the normal Tailwind installation for web. I'm using Expo Web without a framework, so there are currently no CSS files or web-only layouts, so I'm not quite sure how to drop in the Tailwind CSS directives, and also unsure if this means I'd need to manually run the Tailwind CLI build watch every time. I think I'm just missing some understanding, thanks (and amazing lib @marklawlor).

On the web, NativeWind is just a compatibility layer between Tailwind CSS and React Native. NativeWind doesn't do any processing, it just makes React Native understand the className prop.
Expo Web without a framework is simply a web project using Webpack. So you can follow Tailwind CSS PostCSS guide guide to install it as a PostCSS plugin in your webpack config.

The Expo docs and the example in the repo have been updated

Thanks for the help @marklawlor. Unfortunately I'm still not able to get things working on the web.
When I run through the Expo directions my app renders but with no styles applied on the web.
When I run through the PostCSS directions, my tailwind.config.js errors saying TypeError: nativewind is not a function.
When I tweak the tailwind.config.js be plugins: [require("nativewind/tailwind/css")] instead, I get Module not found: Can't resolve './nativewind-output'.
Combinations of all the instructions haven't yielded anything either. Here's the relevant parts of my current code:
package.json dependencies
{
  "nativewind": "^2.0.0-next.61",
  "postcss": "^8.4.16",
  "tailwindcss": "^3.1.8"
}

tailwind.config.js
const nativewind = require("nativewind/tailwind/css");

module.exports = {
  content: ["./app/**/*.js"],
  theme: {
    extend: {},
  },
  plugins: [nativewind()],
};

postcss.config.js
module.exports = {
  plugins: [require("tailwindcss"), [require("nativewind/postcss")]],
};

webpack.config.js
const path = require("path");
const createExpoWebpackConfigAsync = require("@expo/webpack-config");

module.exports = async function (env, argv) {
  const config = await createExpoWebpackConfigAsync(
    {
      ...env,
      babel: {
        dangerouslyAddModulePathsToTranspile: ["nativewind"],
      },
    },
    argv
  );

  config.module.rules.push({
    test: /\.css$/i,
    use: ["postcss-loader"],
  });

  return config;
};

App.js
import "./nativewind-output";

I'm sure it's something dumb I'm doing, but any nudge in the right direction would be a huge help. A starter / example showing PostCSS and/or Expo Web working with NW 2.0 would be even better. Thanks again.

the example in the repo have been updated

@mattwigham Please see the expo project in the examples folder.

Ahh, missed that. That fixed me up, I was definitely missing some things. Thanks so much @marklawlor. Congrats on 2.0.


Timeout processing request

I tried to test open-lpr but with curl and webpage I get the same error:
{"msg":"Timeout processing request"}
How can I start to debug it? It's run in docker on top of the Debian 11.

Hello, if you are referring to https://rest-openlpr.computedsynergy.com/ then it's fixed now, the host was down. However, if you deployed locally and getting that error please upload the logs by issuing the following command
cd /path/to/where/you/checked/out/the/repo $ docker compose logs > logs-request-timeout.log
Please make sure to remove any sensitive data from the logs if needed.

Hi, log attached.
logs-request-timeout.log

I suspect you are using an image which does not have RGB channels (it is either monochrome or has ARGB channels or another encoding). Would it be possible to share the image for further analysis?


Not getting any response when this app runs locally on Tableau Desktop app or on webdataconnector simulator running locally

Description: I am running this app (tableau-wdc-react) locally & I am also running
webdataconnector locally with simulator, here: http://localhost:8888/Simulator/index.html
But when I enter this app's local url: http://localhost:3000/ in to the Connector URL and click on Fetch Table Data. I am not getting any data.
I also tried running http://localhost:300 on Tableau Desktop app's WebDataConnector simulator. It also doesn't works on Tableau Desktop app as well.
Note: It works as expected, i get the response when i run it here:
https://tableau.github.io/webdataconnector/Simulator/ and add the url https://nexysweb.github.io/tableau-wdc-react/ in connector url
Please let me know how to make it work running on local WebDataConnector, simulator app & on Tableau desktop app

@vinod77 I am going to close this since haven;t heard back from you


docs: add callout for getValidatedRouterParams

🔗 Linked issue
#24429
❓ Type of change

[x] 📖 Documentation (updates to the documentation, readme or JSdoc annotations)
[ ] 🐞 Bug fix (a non-breaking change that fixes an issue)
[ ] 👌 Enhancement (improving an existing functionality like performance)
[ ] ✨ New feature (a non-breaking change that adds functionality)
[ ] 🧹 Chore (updates to the build process or auxiliary tools and libraries)
[ ] ⚠ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description
As suggested in this comment, add a callout for getValidatedRouterParams in the appropriate section.
📝 Checklist

[x] I have linked an issue or discussion.
[ ] I have added tests (if possible).
[x] I have updated the documentation accordingly.

Thank you! ❤


Add show case links to showcase

Description
After entering the demo page. There's no link to go to the showcase page.

Showcase => Demo (O)
Demo => Showcase (X)

Demo page

Showcase Page

So make links to go to the showcase page.

Applied


silx.gui.utils.blockSignals helper

This PR adds a blockSignals context manager that allows to block signals for one or many QObjects.
This is not much code, but it allows to replace:
previous = obj.blockSignals(True)
# do stuff
obj.blockSignals(previous)

with:
with blockSignals(obj):
    # do stuff

which makes it more readable.

Sounds nice.
BTW, what about a module silx.gui.qtutils for that?
It would make the import easier.
from silx.gui import qt
from silx.gui import qtutils

Initially I put it in silx.gui.qt, there is already a few helpers there in silx.gui.qt._utils, what do you think about that? import is even simpler... but it mixes helpers with Qt bindings.

skip tests with Qt4 (where QObject.objectNameChanged is not available)


Maximizing the window makes the app run very slow

For some reason, maximizing the application to full screen makes it run very slow. When the window is maximized but not full screen, it runs fine. When it is maximized and the title bar is shown, it also runs fine. The cube demo from the SDK runs fine.
Tested with <IP_ADDRESS> SDK on MacOS 10.15.
https://www.dropbox.com/s/6p9qrd4dnsvb8nc/Tutorial02_Cube.app.zip?dl=0
The app needs to be started from the command line so that the loader is able to find the dylib.

@DiligentGraphics Thanks for the demo app. I'm able to replicate the issue with it...and looking into the problem.

@DiligentGraphics
The reason this doesn't happen on the Cube demo is that the Cube demo uses 3 swapchain images, whereas your app uses 2. Changing the Cube demo to use 2 swapchain images causes the same effect as you're seeing. I recommend using 3 swapchain images at all times...but particularly when your app is in fullscreen mode.
In full-screen display mode, Metal uses Direct to Display, which bypasses the display compositor. As soon as something else needs to be displayed, such as a title bar, or even a notification alert, the compositor is invoked and the delays disappear.
Interestingly (and counterintuitively), it appears that Direct to Display might cause the display system to hold onto the drawable longer than when the compositor is used, causing the CAMetalLayer nextDrawable call to stall. Normally, nextDrawable returns within microseconds. In fullscreen mode, with 2 swapchain images, it can take dozens of milliseconds (sometimes over 100 ms). Even with 3 swapchain images, nextDrawable can still take single-digit milliseconds to return while in fullscreen mode.
BTW...PR #810 includes some new abilities to track and report on the performance of the CAMetalLayer nextDrawable call. This has no effect on fixing anything...but it does help to illuminate the delays of the various nextDrawable scenarios. Use the MVK_CONFIG_PERFORMANCE_TRACKING and MVK_CONFIG_PERFORMANCE_LOGGING_FRAME_COUNT environment variables to enable and log this performance tracking.

@billhollings Seems this is exactly the same issue which I was talking about in #742
Finally you found the reason which causing this.

@QuantumDeveloper

Seems this is exactly the same issue which I was talking about in #742

I've marked #742 as a duplicate.
Can you confirm that you were also using 2 swapchain images and that moving to 3 swapchain images fixes this?

@billhollings yes, I also use 2 images before, but I cannot say that changing it to 3 fixes an issue. It definitely increase from 100 to 2500 FPS in full screen mode, BUT at the same time in windowed mode it still stays nearly 250-300 FPS, which is obviously not correct.
FPS count should be the same independently from window mode

@billhollings Thanks! Using 3 swap chain images does fix the problem. It is really quite unexpected that this causes such massive performance degradation.
If you have a list of known issues/BKMs, I think it is worth mentioning about this problem there because this might be quite a surprise for people coming from other platforms.

I think it is worth mentioning about this problem

Good suggestion. PR #811 adds the following to MoltenVK_Runtime_UserGuide.md:

Metal supports a very small number (3) of concurrent swapchain images. In addition, Metal can
sometimes hold onto these images during surface presentation.
MoltenVK supports using either 2 or 3 swapchain images. For best performance, it is recommended
that you use 3 swapchain images (triple-buffering), to ensure that at least one swapchain image will
be available when you need to render to it.
Using 3 swapchain images is particularly important when rendering to a full-screen surface, because
in that situation, Metal uses its Direct to Display feature, and avoids compositing the swapchain
image onto a separate composition surface before displaying it. Although Direct to Display can improve
performance throughput, it also means that Metal may hold onto each swapchain image a little longer
than when using an internal compositor, which increases the risk that a swapchain image will not be a
vailable when you request it, resulting in frame delays and visual stuttering.


osinfo-db-tools: 1.1.0 -> 1.2.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools.
This update was made based on information from https://repology.org/metapackage/osinfo-db-tools/versions.
These checks were done:

built on NixOS
/nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0/bin/osinfo-db-validate passed the binary check.
/nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0/bin/osinfo-db-import passed the binary check.
/nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0/bin/osinfo-db-export passed the binary check.
/nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0/bin/osinfo-db-path passed the binary check.
4 of 4 passed binary check by having a zero exit code.
0 of 4 passed binary check by having the new version present in output.
found 1.2.0 with grep in /nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0
directory tree listing: https://gist.github.com/9181decaf4161cfbaa99ab2b20bb161a
du listing: https://gist.github.com/bbf02890ab226a162c6cbc90e54f0f4f

meta.description for osinfo-db-tools is: '"Tools for managing the osinfo database"'.
cc @bjornfor for testing.
Experimental: this build is cached with Cachix. To use the cache follow these experimental instructions:
One time setup in nixpkgs Git checkout:
cachix use r-ryantm
git remote add r-ryantm https://github.com/r-ryantm/nixpkgs.git

Test this build:
git fetch r-ryantm && git checkout 0e3d6154ae876e9b47673352af802993db8a350e && nix-shell --pure -I nixpkgs=. -p osinfo-db-tools

Success on x86_64-linux (full log)
Attempted: osinfo-db-tools
Partial log (click to expand)
shrinking /nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0/bin/osinfo-db-validate
shrinking /nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0/bin/osinfo-db-import
/nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0
shrinking /nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0/bin/osinfo-db-export
shrinking /nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0/bin/osinfo-db-path
gzipping man pages under /nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0/share/man/
strip is /nix/store/4qvrxzxa535y8304mk195x50b6p9607d-binutils-2.30/bin/strip
stripping (with command strip and flags -S) in /nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0/bin
patching script interpreter paths in /nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0
checking for references to /build in /nix/store/m0gzbmf3n18xip9y64iwqmy7a0yfa51j-osinfo-db-tools-1.2.0...

No attempt on x86_64-darwin (full log)
The following builds were skipped because they don't evaluate on x86_64-darwin: osinfo-db-tools
Partial log (click to expand)

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnsupportedSystem = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnsupportedSystem = true; }
to ~/.config/nixpkgs/config.nix.


Add RFC 6555 support (Dual Stack / Happy Eyeballs)

This PR adds a happy eyeballs algorithm and thereby provides dual stack support. It allows to configure the dual stack mode and fallback delay on the WebSocketFactory while defaulting to recommendations of RFC 6555.
Be aware that this PR introduces breaking changes to the API, specifically the getSocket method may now return null. To counter this, an additional getConnectedSocket method has been added which establishes the underlying Socket instance first. It was not possible to move this functionality into getSocket since that does not throw an exception.
Resolves #112

@TakahikoKawasaki thoughts? :slightly_smiling_face:

@lgrahl I'm sorry for not responding. I'll take time to comment after DeveloperWeek New York 2019 finished.

As a library maintainer I hate pings, but here's a reminder anyways, sorry :slightly_smiling_face: I work on the same project as @lgrahl and we need to decide whether to temporarily fork this library for use in our project, or whether we want to wait for upstream support.
If you don't have time at the moment for a review that's perfectly fine, in that case we'll continue with a fork for the time being. Thanks for the maintenance!
(PS: In case this is of interest to you, we're using nv-websocket-client in Threema's webclient support through SaltyRTC. Works nicely so far, besides the IPv6 troubles.)

@dbrgn @lgrahl Sorry. I start to review the pull request now.

@lgrahl Thank you for your pull request. To be honest, I cannot check every detail. However, your code looks beautiful enough for me to believe it will work. I'll merge it.

@lgrahl @dbrgn
Released nv-websocket-client version 2.9 which includes your pull request. I hope the new library will appear at the Maven Central Repository soon.

@TakahikoKawasaki great, thank you!

@TakahikoKawasaki That reaction was unexpected but most appreciated. :slightly_smiling_face: Cheers!


silentThrow

Throwing Forbidden maybe should not be exposed, so maybe it's a better idea to set context.result = [] or context.result = undefined;

I'm not sure about this, I'd prefer to know why I don't get any result rather than just get an empty response.
And I don't think it can cause a security issue.
This is why the Forbidden error has been created for IMHO.

Thanks for your thoughts! :) If I will add it, I would make it totally optional.
For most apps, I'm on your side! But for big apps with open access the Forbidden error could open the door for hackers. As a hacker, if the forbidden is thrown, you know, that there's at least something you maybe want to investigate more.


--convert3to4 cannot convert project that includes *.ttf file

Godot version
4.0-rc6
System information
Windows 11, Intel(R) UHD Graphics 730
Issue description
--convert3to4 fails if the project includes ttf file(s) with the following error.
ERROR: No loader found for resource: res://Mplus2-Regular.ttf.
   at: (core/io/resource_loader.cpp:230)
ERROR: res://Main.tscn:3 - Parse Error: [ext_resource] referenced nonexistent resource at: res://Mplus2-Regular.ttf
   at: load (scene/resources/resource_format_text.cpp:490)
ERROR: Failed loading resource: res://Main.tscn. Make sure resources have been imported by opening the project in the editor at least once.
   at: (core/io/resource_loader.cpp:222)
ERROR: Failed loading scene: res://Main.tscn
   at: (main/main.cpp:2957)
ERROR: 2 RID allocations of type 'N10RendererRD12LightStorage11ShadowAtlasE' were leaked at exit.
ERROR: 1 RID allocations of type 'N10RendererRD12LightStorage15ReflectionAtlasE' were leaked at exit.
ERROR: 1 RID allocations of type 'N10RendererRD14TextureStorage12RenderTargetE' were leaked at exit.
ERROR: 2 RID allocations of type 'N10RendererRD14TextureStorage7TextureE' were leaked at exit.
ERROR: 1 RID allocations of type 'N18RendererCanvasCull6CanvasE' were leaked at exit.
ERROR: 1 RID allocations of type 'N16RendererViewport8ViewportE' were leaked at exit.
ERROR: 1 RID allocations of type 'N17RendererSceneCull8ScenarioE' were leaked at exit.
WARNING: 4 RIDs of type "Texture" were leaked.
     at: finalize (drivers/vulkan/rendering_device_vulkan.cpp:9301)
WARNING: ObjectDB instances leaked at exit (run with --verbose for details).
     at: cleanup (core/object/object.cpp:1982)

Steps to reproduce
Extract the attached project and execute Godot_v4.0-rc6_win64.exe --convert3to4.
Minimal reproduction project
ttf_project.zip

I'm sorry but I used wrong command to convert the project.
I could successfully convert a project that includes *.ttf file.


Investigate conversion of code-list-config.json format to JSON-LD

Assuming that we're going to create a new MAJOR version of the code-list-config.json format for this movement to JSON-LD:

Figure out and document:

[ ]  how the code-list-config.json document will need to change.
[ ] how the JSON-LD predicates and values will be intereted in different sections of the document (i.e. will concept triples be written with the concept as the subject of the triple or will it be something else? similarly for the properties expressed at the top level with the catalogue metadata: do they get serialised against the concept scheme or the dcat catalog record?).
[ ] How we will likely need to change the csvcubed code base to ensure this information is persisted to RDF correctly (via the CSV-Ws).
[ ] Whether we need to alter the csvw2pmd Jenkins pipeline at all to support this.

See the attached ZIP file which contains some code which is capable of treating a code-list-config.json file as JSON-LD (whether the user has set a @context or not) and is capable of extracting the additional RDF which the user has added to the document.
https://app.zenhub.com/files/374709947/ca42ff9a-7cc2-447f-b93c-2c2123c4b9e9/download
We see that the main object has had the type set to "@type": "dcat:Dataset",. It makes sense that this triple would be attached to the primary skos:ConceptScheme record.
We also see that one of the concepts (England) has an additional rdfs:label specified:
"rdfs:label": {
    "@value": "Lloeger",
    "@language": "cy"
}

The script contained within the ZIP file can then interpret the whole JSON file and prints out the triples which aren't currently understood by csvcubed:
$ python extract-additional-rdf.py
@prefix dcat: <http://www.w3.org/ns/dcat#> .
@prefix rdfs: <http://www.w3.org/2000/01/rdf-schema#> .

<http://example.com/concept-scheme/this-one> a dcat:Dataset .

<http://example.com/concept-scheme/this-one/concepts/E92000001> rdfs:label "Lloeger"@cy .

Define and publish a default context (e.g. 488-codelist-jsonld/new/codelist_context.json)
Incorporate qb and csvw prefixes into the published context so that column definitions can be populated
Identify which triples need @id to be generated from the files provided so that triples can be constructed correctly
Develop new functions (or modify existing functions) to ensure that concepts can be sorted correctly according to the config file (sort is an instruction to csvcubed rather than a true predicate) - also need to ensure that concept hierarchy is being persisted correctly
Update reusable-rdf-resources (e.g. licenses.json and organisations.json) so that values are recognised in the config file
Issues encountered during investigation - @id for dcat:theme, rdfs:label and rdfs:comment not being correctly expanded when using rdflib graph.serialize


Empty continuation token in case of query having Sort and Limit functionality

Package Name:  azure-sdk-for-js
Package Version: "^3.14.1",
Operating system: Mac
[ ] nodejs: v10.22.1

version:

[ ] browser

name/version:

[ ] typescript

version: 4.4.4

Is the bug related to documentation in

[ ] README.md
[*] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
Hi Team,
I am using azure sdk for js for cosmo db. I am trying to use sort and offset-limit functionality simultaneously. But when I add sort, along with limit. the query does not return any continuation token. (It returns when I use them separately)
It does return hasMoreResults = true, but the continuation token is an empty string.
Code sample:
Mentioned below is my query that I am using to get the data from db.
Note: I also have the partition key as createdAt.
  /**
   * Queries a container for items using SQL
   *
   * @param querySpec SQL query
   * @param queryOptions SQL Query Options
   * @param containerId specifies the container which to query (e.g. "Case")
   * @param options for the query
   */
  public async queryContainerNext(
    querySpec: SqlQuerySpec,
    queryOptions: FeedOptions,
    containerId: string
  ) {
    const container = this.db.container(containerId)
    const {
      resources: result,
      hasMoreResults,
      continuationToken,
    } = await container.items.query(querySpec, queryOptions).fetchNext()
    return { result, hasMoreResults, continuationToken }
  }

  const { result, hasMoreResults, continuationToken } =
      await this.cosmosDbHelper.queryContainerNext(
        {
          query: `SELECT * FROM backend WHERE backend.customerId = @customerId AND backend.projectId = @projectId ORDER BY backend.createdAt`,
          parameters: [
            {
              name: "@customerId",
              value: customerId,
            },
            {
              name: "@projectId",
              value: projectId,
            },
          ],
        },
        {
          maxItemCount: pageLimit,
          continuationToken: contToken,
        },
        "testing"
      );

I have gone through the test cases of this node package as well but did not find any assertion or test case for continuation token in this scenario. Referred test file
Kindly let me know what needs to be done to get the continuation token. Thanks
To Reproduce
try fetchNext() functionality using both sort and pagination together.
Expected behavior
The call should return the continuation token in the response as well.
Screenshots

Additional context
Add any other context about the problem here.

@mfatima21  Thanks for reporting the issue, We are investigating it now and will update you soon!

@sajeetharan Thank you for the response.
Any update on the above issue? Thanks.

@mfatima21 Just wanted to check if you are passing PartitionKey to the query options

@sajeetharan
According to your above suggestion, I passed the partitionKey as query options. But the output was a null array. (Although the data is present)
Posting my updated query and response with partitionKey in here.
const { result, hasMoreResults, continuationToken } =
    await this.cosmosDbHelper.queryContainerNext(
      {
        query: `SELECT * FROM backend WHERE backend.customerId = @customerId AND backend.projectId = @projectId ORDER BY backend.createdAt`,
        parameters: [
          {
            name: "@customerId",
            value: customerId,
          },
          {
            name: "@projectId",
            value: projectId,
          },
        ],
      },
      {
        maxItemCount: pageLimit,
        continuationToken: contToken,
        partitionKey: "createdAt",
      },
      "testing"
    );

For more info, this is container settings.

I hope this info will help in debugging the issue.
Thank you.

@mfatima21 Is it possible for you to upload the code file or push it under a repo?

Hi @sajeetharan Sure.
You can find the associated code in the following repo.
https://github.com/mfatima21/pagination-in-cosmosdb
Thanks again for your assistance.

@sajeetharan  do we have any update on this issue?

@ketangupta34 Are you getting the same issue ? Not yet able to execute the code provided above.
@mfatima21 will you be able to provide an executable version with sample dataset. looks like the above code has dependencies.

@sajeetharan I am from the same team as fatima. so from now, i will be handling this issue. If you need any infomation, please let me know!

@ketangupta34 Just checking if there is any update!

@sajeetharan
Please go through this Repo
https://github.com/ketangupta34/pagination-in-cosmosdb
I have tried to document everything in there

@sajeetharan any updates on this or if you need anything?

Same issue here. Continuation token missing as soon as I add an ORDER BY. Thus, is pagination with LIMIT OFFSET parameters the only way to query in that combination?

@ketangupta34 Thanks for providing the sample with details. We will check on this and get back , @thomasuebi noted, thanks

@ketangupta34 Thanks, we are able to reproduce the issue at our end and we'll work on a fix. To unblock your development can you try LIMIT and OFFSET ?

@sajeetharan yes i have implemented a round about using limit and offset for now.

Using the sample code from above, @mfatima21 sets the partition key on the feed options. There is no partition key on Feed Options.
Argument of type '{ maxItemCount: number; continuationToken: string; partitionKey: string; }' is not assignable to parameter of type 'FeedOptions'.
Object literal may only specify known properties, and 'partitionKey' does not exist in type 'FeedOptions'.ts(2345)

@mfatima21 try using "continuation" instead of continuationToken.

Reopening as the code needs to be modified to support!

Anything new with this? LIMIT/OFFSET approach can get pretty expensive.

We are currently working over fix for same. For now you can refer to this approach:
https://github.com/Azure/azure-sdk-for-js/issues/20140#issuecomment-1493743035

We are closing this one with the workaround provided, however this will be tracked and implemented later.


error while installing "STEAM" through CASK

Error: undefined method `extname' for 0:Fixnum
debug info:
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/container/criteria.rb:43:in extension' /usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/container/pkg.rb:3:in me?'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/container.rb:50:in block in for_path' /usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/container.rb:48:in each'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/container.rb:48:in find' /usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/container.rb:48:in for_path'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/installer.rb:83:in extract_primary_container' /usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/installer.rb:50:in install'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/cli/install.rb:20:in block in install_casks' /usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/cli/install.rb:17:in each'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/cli/install.rb:17:in install_casks' /usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/cli/install.rb:6:in run'
/usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/cli.rb:81:in run_command' /usr/local/Cellar/brew-cask/0.48.0/rubylib/cask/cli.rb:121:in process'
/usr/local/bin/brew-cask.rb:42:in <top (required)>' /System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in require'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in require' /usr/local/Library/brew.rb:58:in require?'
/usr/local/Library/brew.rb:142:in `'

nvrmnd... is duplicate.... gonna update my cask and brew first ;)


If user doesn't give camera permission widget error

If user doesn't give camera permission and try to use next time and also doesn't give camera permission there is a widget error.
Any idea?
E/flutter (15578): [ERROR:flutter/lib/ui/ui_dart_state.cc(148)] Unhandled Exception: Looking up a deactivated widget's ancestor is unsafe.
E/flutter (15578): At this point the state of the widget's element tree is no longer stable.
E/flutter (15578): To safely refer to a widget's ancestor in its dispose() method, save a reference to the ancestor by calling inheritFromWidgetOfExactType() in the widget's didChangeDependencies() method.
E/flutter (15578): #0      Element._debugCheckStateIsActiveForAncestorLookup.<anonymous closure> (package:flutter/src/widgets/framework.dart:3389:9)
E/flutter (15578): #1      Element._debugCheckStateIsActiveForAncestorLookup (package:flutter/src/widgets/framework.dart:3403:6)

It doesn't seem to be a plugin issue. I did some research on this error, it mainly causes due to context, but I'm not able to relate this to the current implementation. Can you add some more logs? and if possible can you provide some code you tried. I did the steps you provided but I'm not able to reproduce this error.

Closing this as no response from the user,
feel free to reopen this if the issue persists


Shopclues.in

Title and Issue number

Title : Shopclues.in
Issue : #1935
Close #1935

Recording of project : https://drive.google.com/file/d/1KwT31ryxpbtdLkYQEiCQq3NCG8Ygg35H/view?usp=drive_web
Checklist:

[x] I have mentioned the issue number in my Pull Request.
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have created a helpful and easy to understand README.md

Please Review my PR


Read Over Reproducibility

Any corrections, clarifications, anything else to add?

Not right now, I think as we can find more resources on how to use GitHub and such it would be nice to have links in there to different resources, so it reads like a "here's what you're supposed to do, and here's a link so you can learn how to do it" kind of thing.


c++: internal compiler error 适合内存应该设置多少？

搜了下是编译时内存不足，但内存已经调整成很大了，请问合适的内存大小设置多少？
【环境】
docker    CPU:2   Memory: 4.0G    Swap: 3.0G
【错误信息】
Scanning dependencies of target sequence_softmax_op
[ 39%] Building CXX object paddle/fluid/operators/CMakeFiles/reduce_max_op.dir/reduce_max_op.cc.o
[ 39%] Linking CXX static library libelementwise_max_op.a
[ 39%] Built target elementwise_max_op
Scanning dependencies of target sequence_pool_op
[ 39%] Building CXX object paddle/fluid/operators/CMakeFiles/sequence_softmax_op.dir/sequence_softmax_op.cc.o
[ 39%] Building CXX object paddle/fluid/operators/CMakeFiles/sequence_pool_op.dir/sequence_pool_op.cc.o
c++: internal compiler error: Killed (program cc1plus)
Please submit a full bug report,
with preprocessed source if appropriate.
See <file:///usr/share/doc/gcc-5/README.Bugs> for instructions.
paddle/fluid/operators/CMakeFiles/reduce_min_op.dir/build.make:62: recipe for target 'paddle/fluid/operators/CMakeFiles/reduce_min_op.dir/reduce_min_op.cc.o' failed
make[5]: *** [paddle/fluid/operators/CMakeFiles/reduce_min_op.dir/reduce_min_op.cc.o] Error 4
CMakeFiles/Makefile2:8645: recipe for target 'paddle/fluid/operators/CMakeFiles/reduce_min_op.dir/all' failed
make[4]: *** [paddle/fluid/operators/CMakeFiles/reduce_min_op.dir/all] Error 2
make[4]: *** Waiting for unfinished jobs....
[ 39%] Linking CXX static library libsequence_softmax_op.a
[ 39%] Built target sequence_softmax_op
[ 40%] Linking CXX static library libsequence_pool_op.a
[ 40%] Built target sequence_pool_op
[ 40%] Linking CXX static library libgru_op.a
[ 40%] Built target gru_op
[ 41%] Linking CXX static library libmean_op.a
[ 41%] Built target mean_op
[ 41%] Linking CXX static library libconv_transpose_op.a
[ 41%] Built target conv_transpose_op
[ 41%] Linking CXX static library libadam_op.a
[ 41%] Built target adam_op
[ 42%] Linking CXX static library libsum_op.a
[ 42%] Linking CXX static library libconv_op.a
[ 42%] Built target conv_op
[ 42%] Built target sum_op
[ 42%] Linking CXX static library libnce_op.a
[ 42%] Built target nce_op
[ 43%] Linking CXX static library libparallel_do_op.a
[ 43%] Built target parallel_do_op
[ 43%] Linking CXX static library libreduce_mean_op.a
[ 43%] Built target reduce_mean_op
[ 43%] Linking CXX static library libbatch_norm_op.a
[ 43%] Built target batch_norm_op
[ 43%] Linking CXX static library libreduce_sum_op.a
[ 43%] Built target reduce_sum_op
[ 43%] Linking CXX static library libreduce_max_op.a
[ 43%] Built target reduce_max_op
[ 43%] Linking CXX static library libactivation_op.a
[ 43%] Built target activation_op
Makefile:105: recipe for target 'all' failed
make[3]: *** [all] Error 2
CMakeFiles/extern_paddle.dir/build.make:111: recipe for target 'third_party/paddle/src/extern_paddle-stamp/extern_paddle-build' failed
make[2]: *** [third_party/paddle/src/extern_paddle-stamp/extern_paddle-build] Error 2
CMakeFiles/Makefile2:511: recipe for target 'CMakeFiles/extern_paddle.dir/all' failed
make[1]: *** [CMakeFiles/extern_paddle.dir/all] Error 2
Makefile:83: recipe for target 'all' failed
make: *** [all] Error 2

试下把paddle改成单线程编译：
#cmake/external/paddle.cmake: line 14
make -j16 -> make -j1

修改后，重新cmake吗？我能直接 make -j1 编译吗？不然又要编译好久。。

需要重新cmake，make -j1貌似改不了依赖模块编译的线程数。重新cmake后不一定需要从头编译。

嗯，试了，没有重头编译，多谢~


bug in latest flutter on master channel

type '_BroadcastStream<void>' is not a subtype of type 'Stream<int>'

When the exception was thrown, this was the stack:
#0      PolygonLayer._build (package:flutter_map/src/layer/polygon_layer.dart:54:15)
#1      PolygonLayer.build.<anonymous closure> (package:flutter_map/src/layer/polygon_layer.dart:47:16)

this line

I have the same issue in my project.

fixed in 0.7.0


Shell model node for review

I think you need to include the prerequisite, even if it's a boundary node.

How broad could that be? Undergraduate chemistry?

How broad could that be? Undergraduate chemistry?

I think we discussed that the boundary nodes can be quite broad.  But again, we're forging new ground here, so it's a point of discussion as much as anything

That's ok. I wanted to work more on the boundary nodes because I have a lot of basic material from my intro course.

I'll close this because I have to change the node meta information based on the new contributions document.


Fix shaky scrolling of LazyColumn when the items are of varying size

Proposed Changes
This mostly re-implements commit
793810ba245 25/01/2022, 23:12 Desktop Scrollbar: fix position of a thumb while dragging

which broke smooth content scrolling in LazyColumn when not all items are of the same size.
The problem with that commit was that on each mouse-drag event it did (conceptually)
dragPosition += dragDelta
contentPosition = dragPosition/scrollScale

but when some items are larger than others scrollScale can change significantly between the mouse-drag events, so you could have contentPosition decrease even when dragDelta was always positive.
What we want to do instead is to always add to contentPosition:
contentPosition += dragDelta/scrollScale

The problem that commit was attempting to solve (https://github.com/JetBrains/compose-jb/issues/643) is solved in this commit in a different way:
val sliderDelta =
    (dragPosition + dragDelta).coerceIn(0f, maxScrollPosition) -
        dragPosition.coerceIn(0f, maxScrollPosition)
contentPosition += sliderDelta/scrollScale
dragPosition += dragDelta

Note that this trades-off smooth thumb scrolling for smooth content scrolling, as you can't currently have both (because LazyScrollbarAdapter.scrollOffset is discontinuous)
Testing
Test: Manually on the reproducer submitted in the bug report, and also via unit tests.
Note that the existing unit test was faulty in the sense that it passed even in the presence of the behavior the commit was meant to fix. It was faulty in two ways: the mouse events it was generating were missing the scrollbar thumb, and it was scrolling in the wrong direction for the test.
Issues Fixed
Fixes: https://github.com/JetBrains/compose-jb/issues/2337

Behavior before:
https://user-images.githubusercontent.com/5230206/210507156-20041e4d-6589-4baa-934b-11c0475801bc.mp4
Behavior after:
https://user-images.githubusercontent.com/5230206/210507192-ec1902ef-5fb8-495f-93c2-86287b9423ec.mp4


Bag of Words

Try a simple bag-of-words model for article tagging.

Type of crime tagging has a model that is "good enough" for now. If there's a concerted push to get better performance then I will create a new issue to track that progress.


[improve] enable and fix test src checkstyle

What's changed?

enable and fix test src checkstyle
Checklist

[ ]  I have read the Contributing Guide
[ ]  I have written the necessary doc or comment.
[ ]  I have added the necessary unit tests and all cases have passed.

Add or update API

[ ] I have added the necessary e2e tests and all cases have passed.

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

Project coverage is 29.05%. Comparing base (77f725c) to head (1db1e54).

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #2610      +/-   ##
============================================
- Coverage     29.07%   29.05%   -0.02%
  Complexity     1628     1628
============================================
  Files           431      431
  Lines         17678    17678
  Branches       2312     2312
============================================
- Hits           5139     5137       -2
- Misses        11953    11955       +2
  Partials        586      586

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


Preview not working

Report a bug
What did you do?
Opened Preview link in README and saw: Cannot proxy the given URL

which exactly link doesn't work? checked all available links in readme and they works fine

which exactly link doesn't work?

This information is in the only sentence in the bug report.

Opened Preview link in README and saw: Cannot proxy the given URL

https://camo.githubusercontent.com/10639e803a90fadd751d3683c497c449e2a48339/68747470733a2f2f6431337961637572716a676172612e636c6f756466726f6e742e6e65742f75736572732f3439353739322f73637265656e73686f74732f323031383234392f64726166745f30362e676966
Here's the link, copied from your README. When I go to this link, I get a page with this error text on it: Cannot proxy the given URL.
I'm in the United States, and I'm assuming that you're not in the US. It's likely that nobody in the US can access that Preview link.

This information is in the only sentence in the bug report.

I'm asking because I don't see any Preview links in readme: https://monosnap.com/file/jYtwxa57y5nekFvnmxBqlUeykuJYLH
Ok, got it. Will take a look shortly

Maybe try hosting the image on GitHub in an img/ directory.
That's always what I do.

sure, that's the right way. don't know why it made in a different way

@alichtman, check out the fresh readme. should work now
thank you for pointing on that issue 👍

Looks good now.


not working with Skin Selector 2.1 (Modloader version)

https://www.mixmods.com.br/2015/09/skin-selector-v2-1-ml-e-v2-1-c/
results in

Mod fails to load saved player model at game startup. Two entries appear in selector list: "$FASTMAN92LI". Clicking either link results in: Unhandled exception at 0x6BF242BD in std.stream.dll (+0x342bd): 0xC0000005: Access violation reading location 0x00000000. Force close via task manager.
Including logs from last run:
cleo.log
cleo_redux.log
fastman92limitAdjuster.log
gta_sa.exe_2024-02-19_15-49-30.log

Second .cleo log didn't upload with first, so I renamed.
CLEOcleo.log

CLEOcleo.log look very weird. Several default Cleo's plugins not registered any opcodes at all.

Those must CLEO Redux plugins

Looks like another plugins collision. Now regular Cleo also has MemoryOperations plugin.

Mostly fixed in alpha.46
There is still issue with ModLoader, causing addon skins to be not listed in menu.

@ejp2001 can you try this mod with alpha.70? does it work?

Skin Selector (c) doesn't save the character (could be one of my scripts). But everything else seems to work ok.

Save file is created in cleo_saves folder, but game is not loading it. I disabled all of my scripts to make sure it wasn't anything on my end.

@ejp2001 can you give link to your Skin Selector? I'm looking at sources and I do not see any thing related to save files.

It'd the MixMods Modloader version... https://www.mixmods.com.br/2015/09/skin-selector-v2-1-ml-e-v2-1-c/. I rarely use it anymore.

@ejp2001 Which version? I used N variant before. When files are saved and what is the result then?

(c) version is the one that saves the player model for next load. Everything else works but that.

That WAS one of the main reasons I used it, until I decided I could do more with separate player folders. I still like it for building peds, because I don't have to register them. But I can use any version for that.

Downloaded skin models work in Alpha.75
State loading still not functional.

How is the state saving/loading done in this script? Can someone show the source?

skin_c.txt
It is done via CLEO thread saving feature.
I can see the save file is created and loaded, data detected. Thread is correctly identified and saved state seems to be applied.


Switch all uses of Result<T, Box<dyn Error>> to anyhow::Result<T>.

I tried using this crate in my app, but I found that the error types returned are significantly under-constrained, such that I couldn't use this crate within asynchronous code.
(The error type isn't : Send)
It seems like anyhow is already brought in as a dependency, only to be used once as return Err(anyhow!("...").into()) (src/chunks.rs:34)—given that, I decided we might as well change all Results to use anyhow::Result, with an import at the top of each file.[^1]
One alternative would be to use std::io::Result, which would slot in correctly in almost every return type across the codebase, or to simply add the constraints necessary for anyhow::Error as Box<dyn Error + Send + Sync + 'static>.
Unfortunately, it seems all of these changes have the ability to break existing code, and should thus require a semver bump. However; I'm not so sure any real usage of the crate would break---as normal error propagation is done using the ? operator, which can convert error types to the end users' need.
[^1]: Let me know if you prefer a different style, like defining the alias once at the crate root, or using the full path anyhow::Result<T> every time—or feel free to edit the PR yourself ^^.

Also not sure if the Quickstart section of the README should be changed.

ugh, forgot to switch to the branch ._.

I'm currently writing to use thiserror to improve underlying error handling. This will use an enum that will represent all error types in the crate, with a anyhow::Error that will be used if none of the errors match. In most situations, this shouldn't change how code works, while allowing for future changes to enable improved error handling in the underlying runtime.

These changes have just been pushed alongside the 0.6.0 update. Thank you for pointing this out!

Actually, for me the biggest issue was from App::new—which can just be changed to return io::Result, along with many other functions. I honestly don't think you even need anyhow or Box<dyn Error> now that you've introduced thiserror, you should definitely give that a shot

Thank you for pointing this out, I totally missed these situations. The reason I would still like to have Anyhow be used is so that errors that should crash the program can still use a ? operator to return the error instead of panicking using unwrap. Either way, this has been fixed, I am currently pushing these changes.


dilithium2

how to use something like dilithium2, cause i have found that there is only dilithium5

Dilithium2 will never be supported by QuantCrypt, because I have made the conscious choice of only supporting the strongest PQ algorithms as directed by the CNSA advisory, which directly states CRYSTALS-Kyber and CRYSTALS-Dilithium with Level V parameters. This means Dilithium5 and Kyber1024.

so there is no way to customize it to support dilithium2 instead of dilithium5 ? as i have an embedded system project and i think dilithium2 will be better for memory usage

@OmarKholeif I don't disagree that embedded systems could benefit from more memory-optimized algorithms, but as of current date, QuantCrypt does not yet support embedded platforms which are not running on AMD or Intel desktop processors (x86). Better platform support is in my to-do list, but I just don't have the time for personal projects (read: I'm not getting paid to develop QuantCrypt). Therefore, you theoretically could work in support for Dilithium2 if you fork this repo and know how to modify the source code, but I am not going to do it.


Show all editable exercise attributes in detail pages

Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de (on localhost).
[x] Client: I added multiple screenshots/screencasts of my UI changes
[x] Client: I translated all the newly inserted strings into German and English

Motivation and Context

It solves Issue #1434 (Show all exercise attributes in detail page)
Description

I added following attributes to:

all exercise detail pages (text, modeling, programming and file upload)

categories
difficulty
assessmentDueDate

if no dates, level or category is set, this is displayed as well.
Aswell, rearranged the order so it matches the layout when editing the fields.

Steps for Testing

Log in to Artemis
Navigate to Course Management
Go to Exercises
Create an Exercise of each type and Save
View Exercise Detail Page and check for all attributes

Screenshots

Programming Exercise Screenshots + No Dates or Categories set

Modeling Exercise Screenshots + Team Mode

Text Exercise  Screenshots + No Dates or Categories set

File Upload Exercise Screenshots

@tessaRuckstuhl thanks for creating this PR. Can you please post screenshots for all exercise detail pages. Please also double check that all common attributes of the super class exercise are displayed first (in the same order for each exercise type) and then the attributes of the sub classes are displayed.

@tessaRuckstuhl thanks for creating this PR. Can you please post screenshots for all exercise detail pages. Please also double check that all common attributes of the super class exercise are displayed first (in the same order for each exercise type) and then the attributes of the sub classes are displayed.

Sure! About the remark of showing all common attributes of the super class first: If I would restructure it like that, the order would not be the same as when creating/updating the exercises.
Is this really wanted?

Yes this is fine. Please try to keep related items together (eg dates) and if possible try to use the same order as in the create/edit dialog

Yes this is fine. Please try to keep related items together (eg dates) and if possible try to use the same order as in the create/edit dialog

Ok, so the current order should be fine then.

So to get this clear - using the order of the create/edit dialog + grouping related items is fine? Not necessarily super/sub class ordering?

I would suggest to order after the following priorities:

all elements of the superclass, then elements of the subclass

related items together

same order as in create / edit

is highest priority and should be fulfilled, but leaves some space for ordering the elements of the super class. Then 2) should be followed...

Okay got it! Thanks.

I found a error in the programming exercise detail page when (re-)loading. E.g. https://artemistest.ase.in.tum.de/#/course-management/226/programming-exercises/1993
I'm not sure now whether I should deploy it to the same testserver, as it might seem like the errors origin from this PR. Should I just ignore that and deploy anyways?
Aswell for future reference: Where should I report errors found in the latest version of the development branch and/or testserver?

I found an error in the programming exercise detail page when (re-)loading on testserver1. The "internal server error" is shown three times, but then disappears aftar a few seconds. E.g. https://artemistest.ase.in.tum.de/#/course-management/226/programming-exercises/1993
I'm not sure now whether I should deploy this PR to the same testserver, as it might seem like the errors origin from this PR. Should I just ignore that and deploy anyways?
Aswell for future reference: Where should I report errors found in the latest version of the development branch and/or testserver?

Please create an issue on GitHub and report it to me. This issue should be already fixed in the latest version on develop

There are some merge conflicts, which should hopefully be easy to fix.
@tessaRuckstuhl could you please fix them?
I think you can just use the changes from this branch and re-apply the date pipe changes in https://github.com/ls1intum/Artemis/pull/1488 by @sascha11110

One small additional change request. Can you please remove the 2 "optional" in the programming exercise page? For solution repo url and test repo url


Automated Test for Playground Tutorials

Context:
Automated Test Suite for Playground that checks all tutorial examples are working.
Definition of Done:
All contracts in tutorials working
All transactions in tutorials working
More checks to be done

Issue moved to onflow/flow-playground-tutorials #2 via ZenHub

Issue moved to onflow/flow-playground-tutorials #2 via ZenHub


Optimize MaskTransformation

Not to create the mask bitmap.
Adjust MaskTransformation’s getId()’s return.

@start141
Thank you for everything.
May I add you to the README?

HA.
Thanks, if you like!

I found we can merged NinePatchMaskTransformation to the MaskTransformation.
I will pull a new request soon.

@start141
I should wait ?

maybe at noon.

@start141
OK. :ship:


Deployment Center - GitHub Authorization not working

When GitHub is selected as an deployment option, its asks for Authorization. When clicked on Authorization, it leads to GitHub page, once credential is feeded, its display 404 message. Kindly help.

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

ID: 81dce42d-71bc-9ac0-b016-4add247bb48a
Version Independent ID: 72e95a87-a302-d06c-5a0f-e2f5caf201d1
Content: Continuous deployment - Azure App Service
Content Source: articles/app-service/deploy-continuous-deployment.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin;dariagrigoriu

Let me add more to it, no authorization flow is working, Tries for OneDrive it prompts, incorrect url; tried with DropBox, it says bad request sent!

Hi @KasamShaikh,  is this your first time authorizing GitHub? Can you share with us a screenshot of what you're seeing? Can you try restarting your app?

Thanks for responding.
I am able to login for GitHub, but once after successful login, it prompts 404 error, as seen below,
<EMAIL_ADDRESS>For OneDrive,
<EMAIL_ADDRESS>For Dropbox,
<EMAIL_ADDRESS>Hope this screenshots would help you to investigate the issue.
Best Regards,
Kasam
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Grace-MacJones-MSFT<EMAIL_ADDRESS>Sent: Friday, April 5, 2019 12:24:00 AM
To: MicrosoftDocs/azure-docs
Cc: Kasam Shaikh; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Deployment Center - GitHub Authorization not working (#28750)
Hi @KasamShaikhhttps://github.com/KasamShaikh, is this your first time authorizing GitHub? Can you share with us a screenshot of what you're seeing? Can you try restarting your app?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/28750#issuecomment-480020335, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVAFoskx3NbCaSUKfyyIfx8SOXZyJdkRks5vdkpIgaJpZM4cc4Yi.

@KasamShaikh i can't see any of your screenshots. can you post them directly on here?

Thanks for responding.
I am able to log in for GitHub, but once after successful login, it prompts 404 error, as seen below,

For OneDrive,

For Dropbox,

Hope this screenshots would help you to investigate the issue.

We need to do deeper analysis for this issue. Do you have the ability to open a support request? If not, you can email me at<EMAIL_ADDRESS>and provide me with your SubscriptionID, tand link to this thread. I can enable your subscription to be able to create one.

Has already created one and closed it. It's working fine now for me...thank you for your time.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Grace-MacJones-MSFT<EMAIL_ADDRESS>Sent: Monday, April 8, 2019 11:43:59 PM
To: MicrosoftDocs/azure-docs
Cc: Kasam Shaikh; Mention
Subject: Re: [MicrosoftDocs/azure-docs] Deployment Center - GitHub Authorization not working (#28750)
Closed #28750https://github.com/MicrosoftDocs/azure-docs/issues/28750.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/28750#event-2260569036, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AVAFombNBPnlzjnA7SIiciMo60zEIfIbks5ve4bngaJpZM4cc4Yi.

Glad to hear your issue was resolve.

I encounter the same issue, how to resolve the 404 issue during authorized by github?

Also stuck on this.

I'm not able to authorise my GitHub account in the deployment center for my web app. I get a 404 error. I'm not able to create a support request in Azure. I sent an email to<EMAIL_ADDRESS>with my subscription ID and linked back to this issue.


Feature/achievement saving

Closes Gamify-IT/issues#428
For testing:

play any course and get some progress at an achievement (just walk around)
leave the course
enter the course again and check, whether the progress was safed or not

Disclaimer: Closing the tab does not result in any saving, so don't do that

Disclaimer: Closing the tab does not result in any saving, so don't do that

you may want https://developer.mozilla.org/en-US/docs/Web/API/Window/beforeunload_event

I suppose I have to run the docker dev-e2e file? Use the main-branch in the backend?

No, you can simply use the development server :)