fix: style in radiobtn and accordion after move

Describe pull-request
Removed use of get-colour function in component styling

It's just hard to test this here, since it was always working without problems in StoryBook but the problem was in our website. Could we try how it works there?


Updated multiply.test.js

Corrected answer of multiply operation in multiply.test.js

Nice work! In future you could push to the branch and the PR would be updated, without needing to open a new PR.
Since we want to keep the spelling and test mistakes for other participants to work on, we wouldn't be merging this PR. Hope the practice was good nevertheless 😄


dev: refactor NN functions

Making a file containing the common functions and enum used by the nn functions.

@chachaleo Is this problem related to what you've done here in your PR?

Yes I will gather all enum used by the nn functions in a file and also have a helper file to gather the helper functions (that I will optimize and comment)

@chachaleo I would like to work on this


Login Error：EOF or An existing connection was forcibly closed by the remote host

I use Mac OSX Develop my project,it work very good !
today I copy my project to my colleague , He is Can't run it
he use Windows 8  coding
the error is WSARecv tcp 172.16.xx.xx:4559:An existing connection was forcibly closed by the remote host,
sometimes the error is Login error : EOF
so I write a demo to test (https://gist.github.com/starchou/8f81ed7d08771416ed5d) in my computer it can work.but in my colleague's computer it can't work.
Meanwhile  I tested with CentOS, the error is Login error:read tcp 172.xx.xx.xx:1433:connection reset by peer
but in my online server(Debian) ,it can run well！
the MSSQL version is SQL Server 10.50.1600
the golang version is 1.2

@denisenkom Thanks. You saved my week!!!


Bottom right cropping and/or borders are sometimes wrong  when exporting to SVG using Selection, Crop and Border settings

Preflight Checklist

[x] I agree to follow the Code of Conduct that this project adheres to.
[x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
Border and/or cropping seems to be malfunctionging sometimes when exporting to SVG using Selection Only + Cropping + Border Width (=20).
Bottom right side is cropped or the borders are missing. Same export is correct after restarting the app.
I'm happy to look into this if someone can help tracing the Export functionality in the repo.
To Reproduce
Couldn't reproduce it intentionally, because I don't know what triggers the error, but will update this as soon as I have more info.
Expected behavior
Exported image should be properly cropped and proper borders on all four sides.
Screenshots
Image shows the SVG inspected in DevTools. The yellow Heap box should have the same border around it an all four sides.

draw.io version (In the Help->About menu of the draw.io editor):

draw.io version 13.4.4 (macOS desktop app)

Desktop (please complete the following information):

OS: macOS 10.15.6
Browser N/A
Version N/A

Additional context
I have a fairly large 5 x 5 canvas with lots of small diagrams (instead of one file for each). By 5 x 5, I'm referring to when the editor automatically extends the canvas when moving a diagram to the edge.
Might be related to #866

I just had the same issue, but exporting the whole drawing to PNG with borders – left/top border is correct, but bottom/right part of the image is clipped seemingly exactly by the 2 border sizes. Setting border to zero doesn't cause any clipping. macOS 10.15.6, desktop app.

Issue still persists

Can we reopen this? Happens every time with larger drawings.

It is July 22 2021. This issue still remains unfixed. I get around this by adding some 'dummy blocks' in the right and bottom corners and manually crop the exported image.

We're unable to reproduce this problem. What are the exact steps? What version of the app?

@alderg I can't reproduce it intentionally, it just happens from time to time.
I haven't used the app for some time now, so I don't know if it persists in newer versions. The version I was using when I opened the issue is stated in the issue description. (13.4.4, macOS (10.15.6) app)

Thanks for the report. This will be fixed in the next release. (We were able to reproduce it when the diagram was zoomed, eg. 30%.)

Thank you for figuring it out @alderg! 🥳


Optimizations for Device and Dep updates

Dep updates
disabling devices on a bridge is not removing them anymore but really disabling them (aka unreachable) - for this unreachable state is also tweaked
make sure ui updates get pushed when neeeded
Small stuff here and there

Sure, fixed (hopefully ... was just missing "enable")


Update delve installation instructions. Fix #801

What does this PR do?
Updates the delve installation instructions for local debugging of DWO.
What issues does this PR fix or reference?
#801
Is it tested? How?
Manual testing.
Checkout the branch, run go install github.com/go-delve/delve/cmd/dlv@latest from the repo's root directory after ensuring $GOPATH or $GOBIN is on $PATH, then run make debug to ensure DWO is executed in debug mode.
PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

@AObuchow could you please use the conventional commits - https://www.conventionalcommits.org/en/v1.0.0/#summary
Semantic PR check is failing

/retest

/ok-to-test

/retest

/retest

@amisevsk Thanks for merging and review! :partying_face: and thank you @ibuziuk for the review as well!


[tool_crash] FileSystemException: Exists failed, OS Error: Le périphérique n’est pas prêt., errno = 21

Flutter crash report.
Please report a bug at https://github.com/flutter/flutter/issues.
command
flutter doctor
exception
FileSystemException: FileSystemException: Exists failed, path = 'F:\Flutter\flutter_windows_3.3.4-stable\flutter.pub-cache\hosted\pub.dartlang.org_fe_analyzer_shared-41.0.0\lib' (OS Error: Le périphérique n’est pas prêt.
, errno = 21)
#0      _Directory.existsSync (dart:io/directory_impl.dart:94:7)
#1      ForwardingFileSystemEntity.existsSync (package:file/src/forwarding/forwarding_file_system_entity.dart:43:33)
#2      ErrorHandlingDirectory.existsSync.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:497:22)
#3      _runSync (package:flutter_tools/src/base/error_handling_io.dart:597:14)
#4      ErrorHandlingDirectory.existsSync (package:flutter_tools/src/base/error_handling_io.dart:496:12)
#5      PubDependencies.isUpToDate (package:flutter_tools/src/flutter_cache.dart:101:57)
<asynchronous suspension>
#6      Cache.updateAll (package:flutter_tools/src/cache.dart:673:11)
<asynchronous suspension>
#7      FlutterCommand.verifyThenRunCommand (package:flutter_tools/src/runner/flutter_command.dart:1325:7)
<asynchronous suspension>
#8      FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1209:27)
<asynchronous suspension>
#9      AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#10     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#11     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)
<asynchronous suspension>
#14     run.<anonymous closure>.<anonymous closure> (package:flutter_tools/runner.dart:62:9)
<asynchronous suspension>
#15     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#16     main (package:flutter_tools/executable.dart:91:3)
<asynchronous suspension>

flutter doctor
[✓] Flutter (Channel stable, 3.3.4, on Microsoft Windows [version 10.0.19041.264], locale fr-FR)
    • Flutter version 3.3.4 on channel stable at C:\src\flutter\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision eb6d86ee27 (2 months ago), 2022-10-04 22:31:45 -0700
    • Engine revision c08d7d5efc
    • Dart version 2.18.2
    • DevTools version 2.15.0

[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✓] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[✗] Visual Studio - develop for Windows
    ✗ Visual Studio not installed; this is necessary for Windows development.
      Download at https://visualstudio.microsoft.com/downloads/.
      Please install the "Desktop development with C++" workload, including all of its default components

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/windows#android-setup for detailed instructions).

[✓] VS Code (version 1.74.0)
    • VS Code at C:\Users\Consto-debort\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.54.0

[✓] Connected device (2 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [version 10.0.19041.264]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 108.0.5359.99

[!] HTTP Host Availability
    ✗ HTTP host "https://maven.google.com/" is not reachable. Reason: An error occurred while checking the HTTP host:
      Connection terminated during handshake

! Doctor found issues in 4 categories.

J'ai réinstallé mon système et après avoir installé, voilà le message qui affiche...aidez-moi

Closing as duplicate of https://github.com/flutter/flutter/issues/81146


Bump version to 3.0.0

Signed-off-by: Rupal Mahajan<EMAIL_ADDRESS>Description
Bump main to 3.0.0
Issues Resolved
#396
Check List

[ ] New functionality includes testing.

[ ] All tests pass, including unit test, integration test and doctest

[ ] New functionality has been documented.

[ ] New functionality has javadoc added
[ ] New functionality has user manual doc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Backward Compatibility Tests failing with following error
> Task :classes
e: /home/runner/work/dashboards-reports/dashboards-reports/reports-scheduler/src/test/kotlin/org/opensearch/integTest/PluginRestTestCase.kt: (9, 19): Unresolved reference: http

e: /home/runner/work/dashboards-reports/dashboards-reports/reports-scheduler/src/test/kotlin/org/opensearch/integTest/PluginRestTestCase.kt: (64, 83): Unresolved reference: value
e: /home/runner/work/dashboards-reports/dashboards-reports/reports-scheduler/src/test/kotlin/org/opensearch/integTest/PluginRestTestCase.kt: (101, 63): Unresolved reference: HttpHost
e: /home/runner/work/dashboards-reports/dashboards-reports/reports-scheduler/src/test/kotlin/org/opensearch/integTest/PluginRestTestCase.kt: (119, 38): Overload resolution ambiguity:
> Task :compileTestKotlin FAILED
public open fun builder(vararg p0: HttpHost!): RestClientBuilder! defined in org.opensearch.client.RestClient
public open fun builder(vararg p0: Node!): RestClientBuilder! defined in org.opensearch.client.RestClient

FAILURE: Build failed with an exception.

Codecov Report

Merging #509 (7d33332) into main (b25984b) will increase coverage by 2.58%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##               main     #509      +/-   ##
============================================
+ Coverage     74.27%   76.85%   +2.58%
============================================
  Files            94       30      -64
  Lines          3984     1923    -2061
  Branches        641      412     -229
============================================
- Hits           2959     1478    -1481
+ Misses          891      442     -449
+ Partials        134        3     -131

Flag
Coverage Δ

dashboards-reports
76.85% <ø> (ø)

reports-scheduler
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...rtsscheduler/model/InContextReportCreateRequest.kt

...h/reportsscheduler/action/ReportInstanceActions.kt

...nsearch/reportsscheduler/model/ReportDefinition.kt

...tsscheduler/model/GetAllReportInstancesResponse.kt

...rch/reportsscheduler/index/ReportInstancesIndex.kt

...ortsscheduler/model/GetReportDefinitionResponse.kt

...portsscheduler/action/GetReportDefinitionAction.kt

...reportsscheduler/action/ReportDefinitionActions.kt

...rtsscheduler/model/GetAllReportInstancesRequest.kt

...rtsscheduler/resthandler/ReportStatsRestHandler.kt

... and 54 more

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


afterChange and beforeChange listeners

The original no longer supported library have a afterChange and beforeChange listener:
Function afterChange = (String previous, String next) {};
Function beforeChange = (String previous, String next) {     return true;   };
Can we have this here?

Sure, I will add this feature and publish a new version

Thank you, just let me know if you need some help

Can you confirm if the latest version works as expected?
This is the commit in which I've made the changes: 295371c


Stop Metric Recorder Listing TaskRuns When Records Data

Changes
Prior to this PR, we retrieve the `TaskRun` back from shared cache in
`durationAndCountMetrics` in order to get the condition before
this reconcile cycle, while actually we have already got the
before condition in the main reconcile loop.

This PR removes the lister logic and reuses the `before` condition
from the `ReconcileKind()` loop.

/kind cleanup
Thanks @afrittoli  for catching this in https://github.com/tektoncd/pipeline/pull/5853#pullrequestreview-1219108535 ❤
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

[x] ~Has Docs included if any changes are user facing~
[x] ~Has Tests included if any functionality added or changed~
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including
functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
[x] ~Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)~
[x] ~Release notes contains the string "action required" if the change requires additional action from users switching to the new release~

Release Notes
NONE

/assign @afrittoli

cc @tektoncd/core-collaborators PTAL

/approve

/lgtm


IllegalStateException: Failed to init NormalizerStore at /tmp/col/scratch/131219/normalizer

This occurred after an import was aborted using the stop button. Subsequently it has not been possible to trigger a new import
https://www.dev.checklistbank.org/dataset/131219/imports

@gdower reported the same some time ago. Will look...

Damn, now it is working. I had deployed a new version to dev in the meantime. I suppose starting a new JVM has fixed it.
I would not be surprised if it is related to our other mysterious problem that shows sometimes - files being kept open:
https://github.com/CatalogueOfLife/backend/issues/1132

I've canceled and reimported - now it fails again!

Caused by: org.neo4j.kernel.lifecycle.LifecycleException: Component 'org.neo4j.kernel.internal.locker.StoreLockerLifecycleAdapter@1a755a96' was successfully initialized, but failed to start. Please see the attached cause exception "Unable to obtain lock on store lock file: /tmp/col/scratch/131219/normalizer/store_lock. Please ensure no other process is using this database, and that the directory is writable (required even for read-only access)".
at org.neo4j.kernel.lifecycle.LifeSupport$LifecycleInstance.start(LifeSupport.java:466)
at org.neo4j.kernel.lifecycle.LifeSupport.start(LifeSupport.java:107)
at org.neo4j.kernel.impl.factory.GraphDatabaseFacadeFactory.initFacade(GraphDatabaseFacadeFactory.java:208)
... 17 common frames omitted
Caused by: org.neo4j.kernel.StoreLockException: Unable to obtain lock on store lock file: /tmp/col/scratch/131219/normalizer/store_lock. Please ensure no other process is using this database, and that the directory is writable (required even for read-only access)

Yes. The jobs are in fact not cancelled at all, the name parser catches the exception but does not do anything with it. It is definitely the same as #1143 1132


User Request: Please show link to the Leverage Bot address in the Mybots page.

As a user, I want to see an explorer link to my Leverage Bot contract address so that I am able to monitor the leverage bot and see it on Etherscan
Acceptance Criteria

Create link to Leverage Bot address on Etherescan
Place the link under Status as (Address) with the last 4digits of the address:
Use the Tokentx link for the URL to open into a new tab.
Example: https://etherscan.io/address/0x2a9b16e78375c3b303ab56fbe736be6ec3b3e016#tokentxns

https://www.figma.com/file/6DYR6QFkucGd1bsOILr7V0/Paloma-Bot?type=design&node-id=2282-548787&mode=design&t=1uQbNhcCzzAXJmjh-4

I don't see the link to my bot contract here


Links to relevant articles

Helpful articles associated with the project @sohilpandya @Joshua-Ronan-Phillips @mantagen

https://community.algolia.com/instantsearch.js/?ref=producthunt

http://eslint.org/

https://github.com/typefoo/node-shipping-fedex

Zip code auto fill & error handling
https://css-tricks.com/using-ziptastic/


feat(api): following and folllowers

I added following and followers. The ui is not complete for it

Great


APM: prevent connection to core agent in case of existing agent

What does this PR do?
Explicitly break connection to core-agent so that we can verify we use the OS hostname fallback.

Motivation
Some new CI runners have an agent available, this test previously assumed no agent would be available. Make this assumption explicit so the test passes on these new runners (as well as on local dev mac machines that may have an agent running)

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes
Does the test pass on the new runners

/merge


Add new --tty-mode option for cli

Added a new option "--tty-mode", which helps to run csscomb from another app.
I need to run csscomb using "external tools" in WebStorm.
In that case the only way to make it working is to add an additional option, which allows to run the tool as if it would be in TTY mode.
Otherwise csscomb just finishes it's execution since there is no input from stdin.

+1

@mishanga, can you, please, provide a feedback?
If everything is ok, shall we merge it?

@tonyganch ⬆

Great!
@mishanga or @mishanga, or @jonrohan, guys, please merge it.

I'll be able to take a look at it later this week, Fri or Sat.

Great!
@mishanga or @mishanga, or @jonrohan, guys, please merge it.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

@tonyganch , thanks.

Hey @JasonRammoray, thank you a lot for PR.
I've got a feeling it should be done in the opposite direction though: explicitly specifying stdin mode and process files for everything else.
For example, in many unix commands - (dash) tells that you want to use stdin instead of file paths.
What do you think about that?

Hello, @tonyganch .
Let me clarify it a bit.
Csscomb works perfectly fine, when I am running via terminal, but for some reason it's trying to read files from stdin, when I am running it as an external tool using WebStorm (meaning, that process.stdout.isTTY has a false value).
I am using following parameters for WebStorm external tool:
Program - node
Parameters - $FilePath$
Working directory - $ProjectFileDir$
In terms of a workadound solution I have two options:
a) downgrade to previous version of csscomb
b) extend an if statement with an additional check (this specific flag)
I did option b) on my locally installed css comb and works just fine.
I think it would be beneficial for other developers to have such ability to indicate the fact, that files should be processed directly even if we are not running csscomb from a console.
What do you think?

@tonyganch

@tonyganch, do you agree with my proposal?
If yes, please, merge it.
If no, then let's discuss that.

@tonyganch, please, take a look at my comment above.

@tonyganch , shall we create a patch version (4.0.1) out of it?


Format using the only available formatter if the default formatter is unavailable

I want to set Prettier as the default formatter, and there are two ways.

Add a lot of language specific settings.
{
    "[css]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
    "[html]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
    "[javascript]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
    "[typescriptreact]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
    "[json]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
    "[jsonc]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
    "[markdown]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
    "[typescript]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
    "[typescriptreact]": { "editor.defaultFormatter": "esbenp.prettier-vscode" }
}

Set Prettier as the global default formatter.
Since I use some languages that Prettier cannot format, I also need to set a lot of language specific default formatters.
{
    "editor.defaultFormatter": "esbenp.prettier-vscode",
    "[c]": { "editor.defaultFormatter": "llvm-vs-code-extensions.vscode-clangd" },
    "[cpp]": { "editor.defaultFormatter": "llvm-vs-code-extensions.vscode-clangd" },
    "[hosts]": { "editor.defaultFormatter": "foxundermoon.shell-format" },
    "[ignore]": { "editor.defaultFormatter": "foxundermoon.shell-format" },
    "[properties]": { "editor.defaultFormatter": "foxundermoon.shell-format" },
    "[python]": { "editor.defaultFormatter": "ms-python.black-formatter" },
    "[shellscript]": { "editor.defaultFormatter": "foxundermoon.shell-format" }
}

I always need to add a lot of settings as you can see.
But if VScode uses the only available formatter when the default formatter is unavailable, then the settings will be very simple:
"editor.defaultFormatter": "esbenp.prettier-vscode" // only need to add one line

Hi @argvchs,
Thank you for bringing this up!
Currently, VS Code does not have an option to automatically use the only available formatter when the default formatter is unavailable. This behavior isn't supported for several reasons:

Explicit Formatter Control: VS Code’s design emphasizes explicit control over formatting for each language. Allowing the editor to automatically switch formatters when one is unavailable could lead to unpredictable results, especially if different formatters apply different styles or rules. This could cause confusion or formatting inconsistencies across various file types.

Language-Specific Formatters: Some languages require highly specialized formatters (e.g., Python's Black or C++'s Clangd), and VS Code needs to ensure that users configure the correct formatter for their specific use case. Automatically selecting the available formatter could lead to unintended behavior, as not all formatters support the same features or standards.

Customization Flexibility: Allowing users to explicitly set formatters per language enables them to tailor their environment based on the unique needs of each language they work with. This provides greater flexibility and ensures that users are in control of the formatting tools applied to their code.

For now, setting language-specific formatters in your settings, as you have outlined, is the best approach to ensure the correct formatter is used where needed. While this does involve adding more configuration, it gives you the reliability of knowing that each language will be formatted according to your preferences.
If you think this feature would improve the overall user experience, you might consider submitting a feature request to the VS Code team for future consideration.
Thanks again for your feedback!
Best regards,
[Your Name]

The formatting behavior will be always defined, because it will only format if one formatter is available, and if there are two ones, it should prompt me to choose.
You can still explicitly set language specific formatters. This should be the formatter priority:

Language specific default formatter.
Global default formatter.
Available formatters. (prompt if there are >1)

And the current formatting behavior is weird. When I have the following settings:
{
    "editor.defaultFormatter": "esbenp.prettier-vscode"
}

When I try to format a file that no formatter is available, VS Code shows There is no formatter for '...' files installed.
When I try to format a file that has one available formatter, VS Code shows Extension 'Prettier - Code formatter' is configured as formatter but it cannot format '...'-files.

The formatting behavior will be always defined, because it will only format if one formatter is available, and if there are two ones, it should prompt me to choose.
You can still explicitly set language specific formatters. This should be the formatter priority:
Language specific default formatter.
Global default formatter.
Available formatters. (prompt if there are >1)

Hi @argvchs,
Thank you for bringing this up!
At first glance, it seems like a really cool idea, and I completely agree—it would be great if we could have such a feature. However, currently, VS Code does not have an option to automatically use the only available formatter when the default one is unavailable. This behavior isn’t supported for a few key reasons:

No Single Universal Formatter: Even though Prettier is an amazing tool and supports a vast range of languages and technologies, no formatter can cover all languages. If there were a formatter that could handle every language, it would likely become the default. But for now, different formatters specialize in different areas, which is why explicit configuration is necessary. Allowing the editor to switch automatically could lead to unintended formatting results, especially when the available formatter doesn’t fully support the language.
Explicit Formatter Control: VS Code emphasizes giving users control over which formatter is applied to each language. Automatically switching to an available formatter might lead to unpredictable behavior, causing confusion or inconsistencies in formatting standards across various languages.
Language-Specific Formatters: Some languages require very specific formatters (e.g., Black for Python or Clangd for C++), and relying on the wrong formatter could lead to incorrect or suboptimal results. It's important that users explicitly set the correct formatter to ensure the right behavior.
Customization Flexibility: While it involves more configuration, setting language-specific formatters ensures that users can tailor their setup for each language. This avoids situations where formatters are applied incorrectly due to automatic switching.

For now, the best approach is still to explicitly configure the formatters as you've outlined. While it adds more settings, it ensures that each language is formatted correctly and according to your preferences.
If you believe this feature would significantly improve the user experience, I recommend submitting a feature request to the VS Code team for future consideration.
EDIT: Setting up default formatters for your specific languages is actually a better approach. Once you configure the default formatter for each language, it remains consistent and reliable, ensuring that each language is formatted according to your preferences. This setup, while involving some initial configuration, avoids the potential issues that could arise from automatically switching formatters. It gives you control over which formatter is applied and helps maintain predictable and accurate formatting results.
Thanks again for your input and for understanding!
Best regards, Otabekoff

AI generated content?

I would not like the implicitness of this. I am an explicit-over-implicit guy especially when it comes to important things like formatting.
In addition, I have found that using the language identifier specific way to set the default formatter should always be used. There is a risk otherwise that if you have a repo where only configure "editor.defaultFormatter": "esbenp.prettier-vscode" and expect that to be used for that repo, it will not work if a user in their user settings have done a language specific override.
My recommendation is to always configure all formatters used for a project in the .vscode/settings.json to  be on the safe and explicit side. It also makes it more apparent as the proejct grows and new users join what formatters are used.


Cant able to add extension

Issue Type: Bug
The visual studio code showing an unknown error occurred.
VS Code version: Code 1.45.1 (5763d909d5f12fe19f215cbfdd29a91c0fa9208a, 2020-05-14T08:27:35.169Z)
OS version: Windows_NT x64 10.0.19041

System Info

Item
Value

CPUs
AMD Ryzen 5 2500U with Radeon Vega Mobile Gfx   (8 x 1996)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onoop_rasterization: disabled_offprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledviz_display_compositor: enabled_onviz_hit_test_surface_layer: disabled_off_okwebgl: enabledwebgl2: enabled

Load (avg)
undefined

Memory (System)
3.45GB (0.49GB free)

Process Argv

Screen Reader
no

VM
0%

Extensions (6)

Extension
Author (truncated)
Version

html-snippets
abu
0.2.1

node-snippets
chr
1.0.0

vscode-html-css
ecm
0.2.3

php-intellisense
fel
2.3.14

mssql
ms-
1.9.0

LiveServer
rit
5.6.1

Please follow these steps

Help -> Toggle Developer Tools -> Network
Then check for any network failed requests while browsing and installing the extensions if found all requests fails then its probably a proxy or DNS issue at your end.
To confirm its a DNS issue check if you can access this page https://ms-python.gallerycdn.vsassets.io/extensions/ms-python/python/2019.8.29288/1565127378610/Microsoft.VisualStudio.Services.Icons.Default, if you cannot please try configuring your DNS like pointing to <IP_ADDRESS> as suggested here? https://<IP_ADDRESS>/dns/. Otherwise please contact your network administrator.
If it is not a network issue, please share the logs from the following locations

Help -> Toggle Developer Tools -> Console
View -> Command Pallette... -> Toggle Shared Process -> Console
View -> Open View… -> Log (Shared)
View -> Open View… -> Log (Window)


Update docs for limit_time

Thanks to Kobata from #windows-dev on Discord for figuring this out.
I was previously setting .limit_time(Duration::from_millis(0)) with the intention of immediately returning when there's no output ready. This seems to work fine on Linux, Mac, and even wine, but on a few different Windows machines, read() never returned anything. Changing this to 1ms fixed things.
This may be something that should be fixed in the implementation; I haven't dug in. But at the very least, mentioning it in the docs should save somebody else from making the same mistake.

On the one hand, I think this works on Linux and Mac just by accident (not sure about Wine) - if you give read() no time to read, it's not exactly surprising that you always get the timeout.
But on the other hand, it does work, and it turns out that it's actually easy to implement the expected behavior on Windows. Please let me know if the version in the current master works for you, and if so, I'll release it with the change and reject this PR.

Your fix in 4fe47e4842155fe976af85e50aa724d7fefc9654 works fine on Windows, so unifying the behavior on all platforms sounds good to me. Thank you!


Add reportOnly setting to allow setting CSP in report only mode

It's currently not possible to run CSP in report only mode.
Report only mode allows one to collect CSP violations without enforcing them thereby ensuring that no valid sources are blocked.
Set 'reportOnly' => true,  in  config/content-security-policy.php to enable report only mode for CSP.

Thank you! I'm sorry for the delay, it's released in 2.1.0


change calcParams

hi
How can we change the indicators calcParams if possible ?
maybe nice to add it to setTechnicalIndicatorType
thanks

Api OverriderTechnicalIndicator should be what you want.
I'm thinking about changing some parameters or styles of technical indicators when creating technical indicators


datasets and models for demo

Model:
Compartment PK model (e.g. 2 compartment linear model overlaying with data)
Antibiotics in vitro PD and PKPD model (model code and data with Xavier)
Erlotinib model (data and model with David
Selected CIT model

Model:
Compartment PK model (e.g. 2 compartment linear model overlaying with data)
Antibiotics in vitro PD and PKPD model (model code and data with Xavier)
Erlotinib model (data and model with David
Selected CIT model

In discussion, we think that having the csvs as demo files within the app is a good idea.


ERROR: runtime error: invalid memory address or nil pointer dereference when using the client

I'm getting the error "ERROR: runtime error: invalid memory address or nil pointer dereference ! error getting commands pid **** exit 1" when using any of the client's functionality (i can't even check the version or or access help)
Edit
Apologies: I'm on Ubuntu 14.04, 64bit, using ruby 1.9.3

What platform are you on?

sorry, i've edited my original comment to include platform info

Could you please add the contents of ~/.heroku/error.log as well?  I am installing ubuntu now to try and reproduce the error myself.

Someone else had this issue as well and ~/.heroku/error.log was not very helpful.  Instead, could you please include the output of heroku version and attach the contents of ~/.heroku/plugin-cache.json ?

I'm seeing this too, on CentOS 6.3 with ruby 2.0.0p247.

If i type 'heroku version' in the console, i get the "invalid memory address..." error. I'm just on my other machine at the moment so will post the contents of my err.log file in a separate comment

@jimmckerchar I was able to recreate this bug with the file from a separate issue, so do not worry about sending me the file anymore.  I should have what I need to fix this.

here are the contents of error.log from the last (i think) before the issue starts occurring
2015/11/20 10:57:18 running from /home/jim/.heroku/heroku-cli
2015/11/20 10:58:12 done
2015/11/20 10:58:12 rebuilding plugins cache...
2015/11/20 10:58:15 Error reading plugin: heroku-status. See /home/jim/.heroku/error.log for more information.
2015/11/20 10:58:15 exit status 1
module.js:339
throw err;
^
Error: Cannot find module 'heroku-cli-util'
at Function.Module._resolveFilename (module.js:337:15)
at Function.Module._load (module.js:287:25)
at Module.require (module.js:366:17)
at require (module.js:385:17)
at Object. (/home/jim/.heroku/node_modules/heroku-status/commands/status.js:3:18)
at Module._compile (module.js:425:26)
at Object.Module._extensions..js (module.js:432:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:311:12)
at Module.require (module.js:366:17)
2015/11/20 10:58:19 done
2015/11/20 11:29:38 running from /home/jim/.heroku/heroku-cli
2015/11/20 11:29:38 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 11:29:53 running from /home/jim/.heroku/heroku-cli
2015/11/20 11:29:53 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 11:31:11 running from /home/jim/.heroku/heroku-cli
2015/11/20 11:31:11 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 11:48:46 running from /home/jim/.heroku/heroku-cli
2015/11/20 11:48:46 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 11:48:47 running from /home/jim/.heroku/heroku-cli
2015/11/20 11:48:47 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 12:02:37 running from /home/jim/.heroku/heroku-cli
2015/11/20 12:02:37 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 12:02:38 running from /home/jim/.heroku/heroku-cli
2015/11/20 12:02:38 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 12:03:08 running from /home/jim/.heroku/heroku-cli
2015/11/20 12:03:08 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 12:03:09 running from /home/jim/.heroku/heroku-cli
2015/11/20 12:03:09 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 12:03:23 running from /home/jim/.heroku/heroku-cli
2015/11/20 12:03:23 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 12:12:14 running from /home/jim/.heroku/heroku-cli
2015/11/20 12:12:14 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 12:13:58 running from /home/jim/.heroku/heroku-cli
2015/11/20 12:13:58 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 12:14:55 running from /home/jim/.heroku/heroku-cli
2015/11/20 12:14:55 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 12:20:36 running from /home/jim/.heroku/heroku-cli
2015/11/20 12:20:36 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 12:24:22 running from /home/jim/.heroku/heroku-cli
2015/11/20 12:24:22 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 12:33:41 running from /home/jim/.heroku/heroku-cli
2015/11/20 12:33:41 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 12:34:19 running from /home/jim/.heroku/heroku-cli
2015/11/20 12:34:19 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 14:54:23 running from /home/jim/.heroku/heroku-cli
2015/11/20 14:54:23 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 14:55:53 running from /home/jim/.heroku/heroku-cli
2015/11/20 14:55:53 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 14:56:28 running from /home/jim/.heroku/heroku-cli
2015/11/20 14:56:28 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 15:24:59 running from /home/jim/.heroku/heroku-cli
2015/11/20 15:24:59 ERROR: runtime error: invalid memory address or nil pointer dereference
2015/11/20 16:40:51 running from /home/jim/.heroku/heroku-cli
2015/11/20 16:40:51 ERROR: runtime error: invalid memory address or nil pointer dereference

ah... just spotted ;)

Can you delete ~/.heroku/plugin-cache.json and try again?

If that doesn't work, delete ~/.heroku/heroku-cli

thanks @dickeyxxx
Method 1 didn't work but  removing heroku-cli has got me a working client again ;)

@ransombriggs does the solution provided by @dickeyxxx relate to the issue that you were able to reproduce? The issue i opened the case for is now resolved so i'll leave closing this down to you guys ;)

@jimmckerchar - yeah, we debugged this together, and his fix removed the problem for me as well.  One thing I should mention is that if you manually installed any plugins, you will have to reinstall them after heroku updates.  I will go ahead and close this issue.  @mcramm if this does not fix the problem for you, feel free to reopen.

Thanks guys ;)

Thanks! Removing ~/.heroku/plugin-cache.json worked.

Sorry for the trouble here everyone. We pushed a big performance patch yesterday but some of you seemed to have invalid cache files for some reason. We put a patch in to ignore the invalid parts of your command cache.


workbench.colorCustomizations & editor.tokenColorCustomizations: match all light or dark themes

Currently, you can match themes in workbench.colorCustomizations and in editor.tokenColorCustomizations by name or override values for all themes. I’d like to be able to additionally override colors for either all light themes or all dark themes.
I have the latter option set to change the color of comments to #7ce9fc, which is more visible than the default comment color for most themes, but I’d need a different value for light themes.

Previously requested in  #101418 but failed to progress beyond Backlog Candidate.

Marking as duplicate of #101418.
As you know, we already have support for theme specific settings, by name and even with pattern: See https://code.visualstudio.com/docs/getstarted/themes#_editor-syntax-highlighting


backend: auth support required

In order to avoid DoS attacks on our GCP setup, we should protect PWG by requiring auth from any one of a number of providers:

[x] Google
[x] GitHub
[ ] Microsoft
[ ] DockerHub
[ ] Amazon
[ ] ...

We should also make it very clear why we require this auth, and also what data is tracked (will track this in a separate issue)
In order to make progress with #13, we should support at least one of the above so we can control exactly who can access the site for testing/alpha/beta.

Google and GitHub done. Moving to "next" for other auth backends.

thanks for the awesome tool.
I registered for an account as I am learning Go.
I generally only use email signup as I do not want to interlink my accounts. So I am reluctant to use openid, even if it is just to provide my mail address.
The fact remains by doing so you know more than my email address. You know I have a github / google / other provider account... And I am forced to keep the provider even if for some reason I choose to drop for instance the google provider account... Dropping that account would lock me out of your service as well in future login attempts...
That is why in the past I have chosen NOT to create an account with other systems because the need was not that high.
For play with Go, however I have chosen to use openId but as a last resort and I generally do not like that for the above reasons.
I wish I was able to contribute, because I do believe in the mantra stop bitching start fixing, but as I am learning Go that is above my knowledge base.
Maybe in a couple of months you will see a PR :D
Nick

thanks for the awesome tool.
I registered for an account as I am learning Go.
I generally only use email signup as I do not want to interlink my accounts. So I am reluctant to use openid, even if it is just to provide my mail address.
The fact remains by doing so you know more than my email address. You know I have a github / google / other provider account... And I am forced to keep the provider even if for some reason I choose to drop for instance the google provider account... Dropping that account would lock me out of your service as well in future login attempts...
That is why in the past I have chosen NOT to create an account with other systems because the need was not that high.
For play with Go, however I have chosen to use openId but as a last resort and I generally do not like that for the above reasons.
I wish I was able to contribute, because I do believe in the mantra stop bitching start fixing, but as I am learning Go that is above my knowledge base.
Maybe in a couple of months you will see a PR :D
Nick

I also have some view about this subject and try to avoid lock-in.
I generate custom alias to my email (server that I host myself) for each service.
For handling auth, I've been lately investigating ory/kratos, and it deals with many schemes and options. Might suit your needs, so you can add by email login, without handling the whole pain of implementation yourself (and the email recovery, notifications, etc).

I also have some view about this subject and try to avoid lock-in.
I generate custom alias to my email (server that I host myself) for each service.
For handling auth, I've been lately investigating ory/kratos, and it deals with many schemes and options. Might suit your needs, so you can add by email login, without handling the whole pain of implementation yourself (and the email recovery, notifications, etc).

:wave: just dumping some random thoughts here.
Initially we added Oauth login since it was the fastest way for people to get access since e-mail will require having an authentication form and thinking on how to store passwords safely We're planning to do some changes to the authentication flow so unauthorized users can access guides and only authenticate if they want to use the interactive terminal.
Having said that, we'd love to have e-mail authentication but to be completely honest I don't see that happening any time soon from our side since we have a bunch of other things in the pipeline that require more authentication given requests from our community. If someone wants to contribute and give a try, happy to provide guidance and brainstorm about possible implementations!

:wave: just dumping some random thoughts here.
Initially we added Oauth login since it was the fastest way for people to get access since e-mail will require having an authentication form and thinking on how to store passwords safely We're planning to do some changes to the authentication flow so unauthorized users can access guides and only authenticate if they want to use the interactive terminal.
Having said that, we'd love to have e-mail authentication but to be completely honest I don't see that happening any time soon from our side since we have a bunch of other things in the pipeline that require more authentication given requests from our community. If someone wants to contribute and give a try, happy to provide guidance and brainstorm about possible implementations!


slack -> zulip

Update chat link from slack to zulip

Maybe our README should already be more explicit about bugs/feature requests etc going to the issues and user help to the discourse?

@Zethson, sounds reasonable, want to PR in something for that?


Define a folder structure for the installation/setup and CI/CD

one folder call installapp (first time installation) cicd (continuous delivery realization with tekton)


Oni crashes when picking a color theme

Hi,
I encountered this bug with the latest (October 17th, 2019) early access build.
When I try to pick a color theme Oni crashes.
I am on Kali Linux 2019.3
Here's the log
[INFO] [Revery]: App: Upshifting into active state.
[INFO] [Revery]: Focus: loseFocus()
[ERROR] Exception Yojson.Json_error("Line 29, bytes 0-2:\nExpected string or identifier but found '}\n'"):
Raised at file "common.ml", line 5, characters 19-39
Called from file "lib/read.mll", line 243, characters 40-59
Called from file "lib/read.ml" (inlined), line 1025, characters 3-39
Called from file "lib/read.mll", line 1109, characters 8-26
Called from file "lib/read.mll", line 1130, characters 6-26
Called from file "lib/read.mll", line 1137, characters 14-47
Re-raised at file "lib/read.mll", line 1142, characters 6-13
Called from file "src/Store/ConfigurationStoreConnector.re", line 59, characters 29-62
Called from file "src/Core/Log.re", line 62, characters 12-15
Called from file "list.ml", line 106, characters 12-15
Called from file "list.ml", line 106, characters 12-15
Called from file "src/Core/Tick.re", line 33, characters 8-25
Called from file "list.ml", line 88, characters 20-23
Called from file "src/Core/Tick.re", line 39, characters 22-50
Called from file "src/Core/App.re", line 183, characters 4-23
Called from file "src/sdl2.re", line 513, characters 10-20
Called from file "src/bin_editor/Oni2_editor.re", line 142, characters 0-15

If there is any pther info you need please contact me on the discord channel @hamza0867.
Thank you

Here's the config file (it's one that comes by default, I didn't change it)

{
  "editor.detectIndentation": true,
  "editor.fontFamily": "FiraCode-Regular.ttf",
  "editor.fontSize": 14,
  "editor.largeFileOptimizations": true,
  "editor.highlightActiveIndentGuide": true,
  "editor.indentSize": 4,
  "editor.insertSpaces": false,
  "editor.lineNumbers": "relative",
  "editor.matchBrackets": true,
  "editor.minimap.enabled": true,
  "editor.minimap.maxColumn": 120,
  "editor.minimap.showSlider": true,
  "editor.renderIndentGuides": true,
  "editor.renderWhitespace": "all",
  "editor.rulers": [],
  "editor.tabSize": 4,
  "editor.zenMode.hideTabs": true,
  "editor.zenMode.singleFile": true,
  "files.exclude": ["_esy", "node_modules"],
  "workbench.activityBar.visible": true,
  "workbench.editor.showTabs": true,
  "workbench.iconTheme": "vs-seti",
  "workbench.sideBar.visible": true,
  "workbench.statusBar.visible": true,
  "workbench.tree.indent": 2,
  "vim.useSystemClipboard": ["yank"],
}

Sorry my bad that last comma in the config file was the problem


In case updateToken fails user should be redirect to expiredRedirect (from config)

Currently, if updateToken fails (the refresh token by itself might not be valid anymore), it just logs an error.
I would expect that if config.expiredRedirect is set - in case the updateToken operation failed - the user will be automatically redirect out of the app (to what ever I set in config.expiredRedirect)

Sounds good to me. Would you mind making a PR for this?

Any progress on this?
I've come up with something like this.
   AuthService.prototype.updateToken = function updateToken() {
    var _this11 = this;

    (...)

      this.client.post(this.config.joinBase(this.config.refreshTokenUrl ? this.config.refreshTokenUrl : this.config.loginUrl), content, this.config.getOptionsForTokenRequests()).then(function (response) {
          _this11.setResponseObject(response);
          if(_this11.getAccessToken()){
                _this11.authentication.resolveUpdateTokenCallstack(_this11.isAuthenticated());
          }else{
            if(_this11.config.expiredRedirect){
               PLATFORM.location.assign(_this11.config.expiredRedirect);
            }
            _this11.authentication.resolveUpdateTokenCallstack(Promise.reject("something here"));
          }
      }).catch(function (error) {
        _this11.setResponseObject(null);
        if(_this11.config.expiredRedirect){
           PLATFORM.location.assign(_this11.config.expiredRedirect);
        }
        _this11.authentication.resolveUpdateTokenCallstack(Promise.reject(error));
      });
    }

Basically we redirect user to expiredRedirect if

.catch(function (error) happens which pretty much means no new token, or

  _this11.setResponseObject(response);  if(!_this11.getAccessToken()) meaning we can't find token in response.

Any thoughts?

@gregleon That would probably be the best way to do it. Albeit not in the dist dir but in src, but I assume you knew that. If either of you is willing to PR this I'd be more than happy to merge it in. It would be a great addition; probably even a fix.


Trying to get library from gradle

Just adding your dependency I can't download it, I'm get next issue...
Error:(44, 13) Failed to resolve: com.mikepenz:crossfadedrawerlayout:0.0.1-SNAPSHOT
Show in FileShow in Project Structure dialog
Do you any idea about it ?

The library is only on the SNAPSHOT repository of maven at the moment.
In the README there's  the information how you can add this repo
https://github.com/mikepenz/CrossfadeDrawerLayout#using-maven


[Website] Add Keycloak and FusionAuth bearer strategies to website

Hey, i hope adding an issue here is still the correct way of adding a strategy to the website.
https://github.com/hgranlund/passport-keycloak-bearer / https://www.npmjs.com/package/passport-keycloak-bearer
Based on passport-jwt, provides a good level of abstraction for token verification against a Keycloak instance
https://github.com/tobilen/passport-fusionauth-bearer / https://www.npmjs.com/package/passport-fusionauth-bearer
Same as above, but for FusionAuth

I think the passport keycloak strategy is very important and should be added and maintained by the official passport team.


Operator Hub installation does not create openshift-kube-descheduler-operator project and install inside it

I realized the issue when I first attempted to install the descheduler through the Operator Hub. The Operator does not create and install into the hardcoded openshift-kube-descheduler-operator project. This project does not exist ahead of time, and a cluster-admin cannot create the project due to a admission controller preventing new projects with openshift-* from being created.
Once you deploy the descheduler into a user-managed namespace, the pods complain of missing cluster cr in openshift-kube-descheduler-operator

E1011 06:32:21.575635 1 target_config_reconciler.go:110] "unable to get operator configuration" err="kubedeschedulers.operator.openshift.io \"cluster\" not found" namespace="openshift-kube-descheduler-operator" kubedescheduler="cluster"
E1011 06:32:21.575664 1 target_config_reconciler.go:677] key failed with : kubedeschedulers.operator.openshift.io "cluster" not found
E1011 06:32:21.579444 1 target_config_reconciler.go:110] "unable to get operator configuration" err="kubedeschedulers.operator.openshift.io \"cluster\" not found" namespace="openshift-kube-descheduler-operator" kubedescheduler="cluster"
E1011 06:32:21.579459 1 target_config_reconciler.go:677] key failed with : kubedeschedulers.operator.openshift.io "cluster" not found
E1011 06:32:21.765639 1 base_controller.go:272] ResourceSyncController reconciliation failed: kubedeschedulers.operator.openshift.io "cluster" not found
E1011 06:33:21.766782 1 base_controller.go:272] ResourceSyncController reconciliation failed: kubedeschedulers.operator.openshift.io "cluster" not found
E1011 06:34:21.766798 1 base_controller.go:272] ResourceSyncController reconciliation failed: kubedeschedulers.operator.openshift.io "cluster" not found
E1011 06:35:21.766913 1 base_controller.go:272] ResourceSyncController reconciliation failed: kubedeschedulers.operator.openshift.io "cluster" not found

Nevermind, using oc create ns openshift-kube-descheduler-operator works but oc new-project openshift-kube-descheduler-operator doesn't. My fault.


ButtonBehavior init can't be mixed in with other classes with explicit initialization arguments

The init for ButtonBehavior is specified as init(self, *_kwargs).  This means that it can't be mixed in with classes which take explicit initialization args.  Using init(self, *args, *_kwargs) would fix this problem without damaging anything else.  (The call to super(ButtonBehavior, self).init would also have to be similarly expanded.)

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[I took a leap here, and ignored @tito's Needs-analysis tag. Seems straightforward to me, and I can't imagine how it could cause problems.]

Changed my mind. (Note to self: Trust tito!)
The existing functionality means Button can't be mixed with other classes that accept positional parameters... if they are called with positional parameters.
If they are called with keyword parameters it should be fine.
But calling a constructor with diamond inheritance with positional parameters is fraught with danger. It would be far better to call them with keyword parameters. Maybe not supporting positional parameters is a smarter move.


reports: mail subject and content ignored

Kibana version:
6.3.0
Elasticsearch version:
6.3.0
Report engine:
horseman
Describe the bug:
when sending a report, Subject & Content fields are ignored
Steps to reproduce:
Setup a report using wizard, fill Subject & Content fields
Generate the report
Expected behavior:
Resulting email Subject & Content should match what has been defined.
Actually:
email subject = "SENTINL: " + report "Title"
email content = empty, only the attachment is present
Hello,
I am a loyal user of sentinl. And I encountered the same problem in 6.3.0 ,but Report engine is
horseman, which version is now working properly. I look forward to hearing from you。

@xiongzeng the fix is currently under QA tests in the private repository. I'll let you know when it is available.

Duplicate of https://github.com/sirensolutions/sentinl/issues/577#issuecomment-431760969


Cite IWSLT Conv models

Is there any publication specifically referring to fconv_iwslt_de_en settings as described here - https://github.com/pytorch/fairseq/blob/master/fairseq/models/fconv.py#L610 ? I see that the original publication here - https://arxiv.org/abs/1705.03122 - just refers to the WMT settings.
Thanks!

We used this architecture in this paper: https://arxiv.org/abs/1711.04956


Version bump to v0.97.1

Could you please publish a new version because so many bugs were fixed since the last release :bowtie:

:+1:

:+1:

:+1:

Done!


Glitches on searching "function"

STR:
Search for function.
Result:

Thank you for your work.

This issue was closed because it has been stalled for a long time with no activity. Feel free to reopen this issue if you have further questions or suggestions.

The problem still exists with v0.3.9.
Thank you.

I can't reproduce this issue because Google seems to update their search result and now no additional sidebar are shown.


modules/monitor not build on 3.0

Hi,
I'm using the following system specification:
System information

Ubuntu 16.04LTS
Apollo 3.0 installed from source
Udoo with x86_64 platform
When I have build succeed as per the below attachment:

but I could not run modules monitor:
apollo$ run monitor start
[1] 31796
[1]+  Exit 127                nohup /apollo/modules/monitor/monitor --flagfile=modules/monitor/conf/monitor.conf --log_dir=/apollo/data/log < /dev/null > /apollo/data/log/monitor.out 2>&1
Could not launch module monitor. Is it already built?

after I look up my system hardware specification info carefully , we found that UDOO_x86 PC using HDMI secondary port for display (no VGA port available), on the other hand once run lspci on terminal we can see VGA compatible controller available on PCI bus.

we observed during every building modules/monitor is skip building,  I doubt HDMI secondary display on UDOO_x86 PC is may not compatible.

Any help to resolve this issue is much appreciated.
Regards,
Soumya.

Closing this issue as it appears to be resolved. Feel free to reopen if the issue persists. Thanks!


[Partners-HuggingFace] Breaking Change - impossible to skip login after PR #23309

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
HuggingFaceEndpoint(
endpoint_url=self.setting.api_base,
temperature=self.setting.temperature,
repetition_penalty=self.setting.repetition_penalty,
max_new_tokens=self.setting.max_new_tokens,
server_kwargs={'trust_env': True},
    )

Error Message and Stack Trace (if applicable)
File "/home/Morgan.Diverrez/code/GitHub/tock-arkea/gen-ai/orchestrator-server/src/main/python/server/src/gen_ai_orchestrator/services/langchain/factories/llm/hugging_face_tgi_llm_factory.py", line 41, in get_language_model
return HuggingFaceEndpoint(
File "/home/Morgan.Diverrez/code/GitHub/tock-arkea/gen-ai/orchestrator-server/src/main/python/server/.venv/lib/python3.9/site-packages/pydantic/v1/main.py", line 341, in init
raise validation_error
pydantic.v1.error_wrappers.ValidationError: 1 validation error for HuggingFaceEndpoint
root
Did not find huggingfacehub_api_token, please add an environment variable HUGGINGFACEHUB_API_TOKEN which contains it, or pass huggingfacehub_api_token as a named parameter. (type=value_error)
Description
After PR #23309 a few months ago, when we leave huggingfacehub_api_token at its default value, None, and do not set the environment variable HF_TOKEN or HUGGINGFACEHUB_API_TOKEN, the get_from_dict_or_env function at lines 197 and 201 also has a default value of None, similar to huggingfacehub_api_token. The get_from_dict_or_env function calls get_from_env, which raises an error if no token is set in the environment variable.
Therefore, we need to use another solution to retrieve environment variables.
System Info
System Information

OS:  Linux
OS Version:  #127~20.04.1-Ubuntu SMP Thu Jul 11 15:36:12 UTC 2024
Python Version:  3.9.18 (main, Aug 16 2024, 10:24:56)
[GCC 9.4.0]

Package Information

langchain_core: 0.1.52
langchain: 0.1.20
langchain_community: 0.0.38
langsmith: 0.1.114
langchain_huggingface: 0.0.3
langchain_openai: 0.0.2.post1
langchain_text_splitters: 0.0.2

Packages not installed (Not Necessarily a Problem)

I tested it on my machine and faced not issues???

here is the following detailed stack :

HuggingFaceEndpoint

Pydantics execute the following root validator validate_environment

values["huggingfacehub_api_token"] = get_from_dict_or_env(  values, "huggingfacehub_api_token", "HUGGINGFACEHUB_API_TOKEN", None )     it's set the default value to None
 return get_from_env(key_for_err, env_key, default=default) that token is not defined on the constructor at the instantiation

  elif default is not None: our default value is None, so the Error will be raised

 else: raise ValueError( f"Did not find {key}, please add an environment variable"  f" {env_key} which contains it, or pass"  f" {key} as a named parameter." )

So everyone using  HuggingFaceEndpoint  without Hugging Face token configured in environment variable will have the same issue.
Do you have the same understanding of this stack ?
I suggest that we introduce sentinelle value as the default value in get_from_env
I can push a pull request for it

Good catch, I'm also experiencing this issue, this makes it impossible to use any custom deployment of HF TGI, that doesn't required any HF token (and login).
Introducing a sentinel value may be considered as a breaking change, get_from_env will then accept None as default value without raising any exception which is currently not accepted 🤔. This would assume that users rely on this exception being raised, which I my opinion shouldn't be considered as "nominal" usage of this method.

PR : core: [env.py/get_from_env] change default value None -> sentinel object #26153


Duplicate function names "btrim" in src/catalog/catalog.cpp

In src/catalog/catalog.cpp on line 1030 there are two "btrim" function names. Looks like a typo.

This is not a typo.
It is left as an exercise to the reader to understand why. As a hint, read the specification of the trim group of SQL functions. It does seem though, that the function header documentation for AddBuiltinFunction is not entirely correct.


Fix the issues around long-running bag replications

This is what I suspect to be the root cause of https://github.com/wellcomecollection/platform/issues/5484. I'm going to write it out with quite a lot of context, because (1) I don't know how quickly we'll implement this and (2) it's helpful for somebody else to understand it.
Context
What is the bag replicator?
The bag replicator is the service that copies a bag (a collection of files) from one storage location to another. It runs three times when storing a normal bag:

Copying from working storage to our warm S3 storage
Copying from working storage to our cold S3 storage
Copying from working storage to our cold Azure storage

It calls ListObjects on the working storage, then does one-by-one copies of objects from the source to the destination.
How the bag replicator tries to do write-once operation
We want the bag replicator to write exactly once to the permanent storage location – so we can replicate an object, verify it, then be certain that it hasn't changed after it was verified.
We don't currently enable the S3 features that allow you to do that (Legal Holds, Object Lock, governance mode, etc.). We do enable legal holds in Azure.
So instead, the bag replicator checks for an existing object itself, and only writes the object if there isn't already an object at the destination. If there's already an object, it confirms it's the same as what it's about to replicate.
flowchart TD
    F[get object to replicate] --> DE{does the
destination have
 this object?}
    DE-- yes -->DEY{are the source
and destination
objects the same?}
    DE-- no -->DEN["✅ replicate the object"]
    DEY-- yes -->DEYY["✅ nothing to do"]
    DEY-- no -->DEYN["⚠ something has gone wrong"]

To prevent two processes doing this check simultaneously, the bag replicator will lock around the destination prefix – if it's got the lock, it should be the only thing working on this prefix.
This uses our Dynamo locking code, which has locks that expire after a certain period. (This is so applications that crash without releasing their locks don't gum up a process in perpetuity.)
S3 consistency and lazy checking
This approach had a bad interaction with the way S3 consistency used to work.
S3 used to be eventually consistent. If you called GetObject on a non-existent object, then PutObject, then GetObject again, you might get a 404 on the second call. This could cause verification failures, like so:
sequenceDiagram
  participant replicator
  participant verifier
  participant S3

  replicator->>S3: GetObject(f)
  S3->>replicator: 404 Not Found

  replicator->>S3: CopyObject(f, destination)
  S3->>replicator: OK, done!

  replicator->>verifier: you can verify f
  verifier->>S3: GetObject(f)
  S3->>verifier: 404 Not Found (!)

To get around this, the replicator starts by looking for existing objects in the prefix using a ListObjects call. If there aren't any, it knows that nobody is going to write any new objects because it's holding the lock, so it can skip checking for each object in turn. This avoids querying any object individually and hitting this consistency issue.
S3 is now strongly consistent so we no longer need this mitigation, but we haven't removed it yet.
The problem
I think this is the rough sequence of events with the problem bag:

The Azure replicator queue gets a message "Please replicate b32832631"

Task A picks up the message. It acquires a lock on the destination prefix, sees there are no objects already there, starts replicating.

For some reason, the task gets stuck (possibly because we're doing a lot of S3→Azure replication at the same time). It's still working, but it doesn't replicate any objects before the SQS timeout and prefix lock both expire.

Task B picks up the message. It acquires a lock on the destination prefix, sees there are no objects already there, starts replicating. At this point, both A and B are trying to replicate into the same prefix, and both think they have exclusive rights to do so.

Eventually the logjam clears, and both tasks are able to replicate objects into Azure.

Because we have legal holds enabled on the Azure container, at some point both tasks encounter an object that the other task has written, and the Azure copy fails:

This operation is not permitted as the blob is immutable due to one or more legal holds

Proposed changes
Changes I think we should definitely make:

Lock around individual destination objects, not the entire prefix. This problem became possible because the replicator kept working after its lock had expired. We could build a way to keep locks "fresh" and tie that to our SQS visibility timeout, but this is adding complexity to an already pretty-complicated bit of code.
This means we'd spend more on DynamoDB locking, but individual locks would only have to last as long as it takes to replicate a single object. The likelihood of a lock expiring while work is ongoing drops dramatically.

Always look for an existing object before replicating. We added this to work around an S3 limitation that no longer applies. We could remove this code and simplify the replicator. It's less efficient (because we'll check for lots of objects that don't exist), but combined with the individual locking gives us a stronger level of protection against overwrites.
It might be an issue if we ever want to expand our replication locations to another object store that's eventually consistent, but (1) we have no plans to do that and (2) we can't be sure this hypothetical future store would have the same failure mode.

And a change I considered but don't think we should do:

Handle a 409 Blob Already Exists from Azure. With the first two changes this should become practically impossible. If it does happen, we should let it bubble up as an error so we can work out what's going wrong earlier in the replicator.

When should we do this?
We shouldn't rush into this; the replicator/verifier is the most critical part of the storage service, and we don't want to introduce new bugs. The existing code has also been extensively tested in production, and we know it's pretty reliable.
We should fix this, because it is a bug and will become more likely as we push more/bigger bags through the storage service.
Who should do this?
Another Scala developer pairing with me, as a way for them to get some experience with the storage service. It'd be better to wait and use this to do some knowledge sharing, than have me rush into writing a fix and miss this opportunity.


OpenCV can't find dependencies after change in pkg-config path on Linux

OpenCV can't find FFMPEG (and other stuff like GTK, Qt, or V4L2) since https://github.com/ruslo/hunter/commit/f6f096561f0e09b4c85e4049a4eb7948ad24d7eb
This effectively makes OpenCV unable to process video on Linux.
The funny thing is everything seems to work fine on Windows and Mac.
Reverting the mentioned commit fixes the issue.
It is my understanding that isolating the build env from system libraries is the hunter way of doing things, but since none of the mentioned libraries can be built via hunter, using the system libraries seems like the only way to go in this particular case.
Am I missing something? Is there a way around it?

This issue should be fixed by adding missing packages to Hunter. As a workaround you can use your own fork in development.

That's what I ended up doing in the end.
It's worth mentioning in https://github.com/ruslo/hunter/wiki/pkg.opencv
May same someone quite a lot of time.

@szatan feel free to edit

Done

@szatan Thanks. I think it's worth mentioning your fork where people can find ready-to-use releases.

Yeah, why not. I can't guarantee that I'll be updating it on a regular basis, but it'll be a good starting point.
I updated the wiki page.


Field annotated with @Nested annotation incorrectly gets Property  is not annotated with an input or output annotation.

See https://github.com/bmuschko/gradle-docker-plugin/issues/919 for the main issue and replication steps
According to the author:
"My guess is that Gradle doesn't discover this input/output annotations correctly. The field instruction is annotated with @Nested, however, it's not a class, it's an interface. FileInstruction is an implementation of that interface. I think that trips up Gradle's checks."
Expected Behavior

Fields annotated with @Nested should not generate the warning
Current Behavior

Running the task returns:
Property 'instructions.$3.file' is not annotated with an input or output annotation. This behaviour has been deprecated and is scheduled to be removed in Gradle 7.0.

I've answered on the linked issue.


Review: Manoa-Inventory-POST Admin Page

Overview
The focus for this code review will be centered around the admin page.
Please pay attention too:

Javascript issues
React components

Review Branch
review-02
Files to review

AdminDashboard.jsx
InfoBar.jsx

Checklists

Architecture
Design
JS
React
Testing

Due date
Monday February 6, 2023
For more information
The review process is documented at: http://courses.ics.hawaii.edu/ics414s21/morea/review/reading-idpm-review.html

AdminDashboard.jsx

Design-05 (Line 20) Mentions Stuff documents
JS-07 (Line 27) Get rid of console.log(admins)
ESLINT-01 (Line 27) Unexpected console statement
TEST-ACCEPTANCE-01 Doesn’t have isDisplayed() acceptance test

InfoBar.jsx

Design-05 (Line 16) Mentions Stuff documents
JS-07 (Line 23) Get rid of console.log(admins)
ESLINT-01 (Line 23, 44, 50) Unexpected console statement and closing tag location

AdminDashboard.jsx
Design-05 Ensure comments are appropriate (eliminate comments describing the how) line 14
JS-07 Avoid console.log line 27
InfoBar.jsx
Design-05 Ensure comments are appropriate (eliminate comments describing the how) line 10
ESLINT-01 Lines 41-44 fix indentation/line organization of code

AdminDashboard.jsx

L20:  Comment about Stuff "// Get the Stuff documents"

InfoBar.jsx

L16: Comment about Stuff "// Get the Stuff documents"

Just bit more clean up

InfoBar.jsx

line 16 still have stuff document
fix comment overall

AdminDashboard.jsx

line 20 still have stuff document
fix comment overall

[InfoBar.jsx] Line 47-49: <Card.Link>changes line unexpectedly

##AdminDashboard.jsx
Design: Stuff
JS & ES:. console log L-27
##InfoBar.jsx
Design: Stuff

AdminDashboard.jsx

Design 05: Line 20 Remove // Get the Stuff documents
Test-Acceptance 01: AdminDashboard page foes have not have a isDisplayed() acceptance test.


[REFACTOR]

Is your improvement request related to a feature? Please describe
At the moment most of the images used within deploy directory use the head-master tag with image pull policy set to ifNotPresent.
This causes some issues for the "long term" users of the longhorn, most likely using outdated images versions.
As an example in my case - despite of rocking flawlessly working latest rc1, the volumes were missing compressionMethod parameter ( from top of my head ) and this caused multiple failures. After some debugging session I've realised that my master-head was at least few months old.
A clear and concise description of what the problem is.
Describe the solution you'd like
It would be great if either additional overlay for kustomize would be applied, overwriting the images versions to the current ones OR the imagePullPolicy would be set to Always.
The second option is a bit less desirable as it may increase the "fluff" traffic

Installed longhorn with kubectl apply -f on the deploy directory with the 1.4-rc1 tag
Whatever was installed / introduced came from that installation and/or containers deployed during it

I think this confusion highlights the danger of the master-head and makes my point a bit stronger :)


Is it possible to put the spec_augmenter in front of the nn.BatchNorm2d

Hi,
SpecAugmentation masks a block of consecutive time steps or mel frequency channels. But why the order is input, BatchNorm, spec_augmenter? Is there any reason for it. Can i adjust the order to input, spec_augmenter, BatchNorm?
Thanks

Because log mel has large negative values. It may be better to apply spec_augment on the normalized data.

SpecAugmentation is directly applied to the input log mel spectrogram in google's original paper. But I'm not sure is there any Batchnormalization layer after SpecAugmentation due to my lack of asr knowledge. Is there any experiment or paper to supoort your point

Thanks! We have not experimented the comparision yet.
On Wed, 14 Jul 2021 at 10:17, garrywrj @.***> wrote:

SpecAugmentation is directly applied to the input log mel spectrogram in
google's original paper. But I'm not sure is there any Batchnormalization
layer after SpecAugmentation due to my lack of asr knowledge. Is there any
experiment or paper to supoort your point
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/qiuqiangkong/audioset_tagging_cnn/issues/40#issuecomment-879533040,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFXTSKZ7IB6DJLIK63UIVTTXTXU5ANCNFSM47WJOWEA
.

Thanks for your quick reply.


Thai does not respect DATE_ORDER

>>> parse('03/15/2559 05:13', languages=["th"], settings={"DATE_ORDER": "MDY"})
>>> parse('03/11/2559 05:13', languages=["th"], settings={"DATE_ORDER": "MDY"})
datetime.datetime(2559, 11, 3, 5, 13)

May this be a duplicate of #412?

Doesn't really sound like it

It seems that this only happens with the last version:
dateparser 0.7.1
>>> parse('03/11/2559 05:13', languages=["th"], settings={"DATE_ORDER": "MDY"})
datetime.datetime(2559, 3, 11, 5, 13)

dateparser 0.7.2
>>> parse('03/11/2559 05:13', languages=["th"], settings={"DATE_ORDER": "MDY"})
datetime.datetime(2559, 3, 11, 5, 13)

It seems that this bug was introduced with this PR: https://github.com/scrapinghub/dateparser/pull/558
I will investigate it further and I will try to fix it.


Uneven or unclear sample sizes

Hi Hauselin,
I was hoping to use your fantastic effect size calculator to help convert a series of different effect sizes to fishers z and cohen's d for an umbrella review. I note that the tools states "All conversions assume equal-sample-size groups". In my case it's often unclear how many participants were in the treatment and control. Instead the reviews tend to present overall number of participants and the effect sizes.
I was wondering if you could advise whether you think that your tool would be accurate for this use-case? Else if there was some other method you might suggest I would be massively appreciative.
Sorry for sending this as a GitHub issue but I couldn't find your email address.
Thanks so much in advance.
With best wishes,
Barry
Dr Barry Coughlan
Postdoctoral researcher
University of Cambridge

I don't know if there's anything you can do if you don't have the no. of participants in each group. If the numbers aren't too different, then you should be fine assuming equal-sample-size groups. But if they do differ quite a bit, then the estimates will be biased. Not sure what you can do here.
Maybe email the authors to get the actual sample sizes for each group and then use the appropriate conversion formulae for that (the references included on my site should provide all the relevant formulae)?

Thanks so much for your advice Hause.
From: Hause Lin @.>
Reply to: hauselin/esconvert @.>
Date: Wednesday 8 June 2022 at 00:29
To: hauselin/esconvert @.>
Cc: Barry Coughlan @.>, Author @.***>
Subject: Re: [hauselin/esconvert] Uneven or unclear sample sizes (Issue #1)
I don't know if there's anything you can do if you don't have the no. of participants in each group. If the numbers aren't too different, then you should be fine assuming equal-sample-size groups. But if they do differ quite a bit, then the estimates will be biased. Not sure what you can do here.
Maybe email the authors to get the actual sample sizes for each group and then use the appropriate conversion formulae for that (the references included on my site should provide all the relevant formulae)?
—
Reply to this email directly, view it on GitHubhttps://github.com/hauselin/esconvert/issues/1#issuecomment-1149271428, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AOK3G2LDSHOSY3CSSEJK443VN7LL5ANCNFSM5YCP4CAA.
You are receiving this because you authored the thread.Message ID: @.***>

Hi Hause,
 Thank you so much for providing such an amazing and useful tool. In my case, I want to convert the odds ratios to effect size, and my case : control is approximately 13:20. What kind of adjustment should I apply to effect sizes calculated by your program, given my unbalanced case-control samples? Any suggestions and comments are highly appreciated!

Yours sincerely
Leah

Hi @liqingbioinfo, this paper might be helpful or should have relevant references.
Sánchez-Meca, J., Marín-Martínez, F., & Chacón-Moscoso, S. (2003). Effect-size indices for dichotomized outcomes in meta-analysis. Psychological Methods, 8(4), 448-467.

Hi Hause
I appreciate your prompt reply and will read that paper later.


rename auxiliary data

Renames the type family Core.Metadata to Core.AuxiliaryData.

Renames the Allegra & Mary Metadata to AuxiliaryData. The accessors are renamed txMetadata and auxiliaryScripts.

Same name change in the formal spec.

rename ValidityInterval accessors:

validFrom -> invalidBefore
validTo -> invalidHereafter

Well, I preferred "Metadata" and "Blob", but hey ho ;-D PR looks good!

I enjoyed blob, it made me smile :)


[Install] Insomnia Version ver 5.4 installation

when I try to install  insomnia through windows installer Symantec Endpoint Protection Client is not allwoing , Here is the error , Do you know why ?
Security Risk Found!WS.Reputation.1 in File: c:\users\suppala\downloads\insomnia.setup.5.4.0.exe by: Auto-Protect scan.  Action: Quarantine succeeded.  Action Description: The file was quarantined successfully.

I've had other users report this before.
It seems that a lot of antivirus programs automatically block apps that do not have enough reputation yet (not many installs). I'm not sure there is anything I/you can do about this except mark Insomnia as "safe" in the antivirus program. This should help it get whitelisted for other users too.

EV Code Signing should help, but it is very costly way:
https://blogs.msdn.microsoft.com/ie/2012/08/14/microsoft-smartscreen-extended-validation-ev-code-signing-certificates/

I started using a DigiCert code signing certificate a few months ago (hoping to solve this) but I guess it didn't help. I could have gone for an EV but, apparently, you need need to plug in a designated USB device to use it, meaning Insomnia wouldn't be able to sign on a CI server.
Also, I'm not sure if this is true, but I think the reputation resets every new version because the installer file changes. If anyone with a Windows development background can chime in, that would be great.
I'm closing this one for now. I can re-open if anyone has any ideas on how to get around this.


Bigram Model

Hello there,
Newbie here, I am trying to reproduce "let's build GPT" lecture from Andrej Karpathy in candle. At 31 minutes mark in this video, he implements a Bigram model using embeddings.
This is my rust implementation,
#[derive(Debug)]
pub struct BigramLanguageModel {
    token_embedding_table: Embedding,
}

impl BigramLanguageModel {
    // Constructor
    pub fn new(vocab_size: usize) -> Result<Self> {
        let vb = candle_nn::VarBuilder::from_varmap(&candle_nn::VarMap::new(), DType::F32, &Device::Cpu);
        let token_embedding_table = embedding(vocab_size, vocab_size, vb)?;
        Ok(BigramLanguageModel {
            token_embedding_table,
        })
    }

    // Forward pass
    pub fn forward(&self, idx: &Tensor, targets: &Tensor) -> (Tensor, Tensor) {

        let logits = self.token_embedding_table.forward(idx);
        let logits = logits.unwrap();

        let shape = logits.shape().dims();
        let logits = logits.reshape(&[shape[0]*shape[1], shape[2]]).unwrap();

        println!("shape: {:?}", logits.shape());
        println!("targets shape: {:?}", targets.shape().dims()[0]);
        if targets.shape().dims()[0] != 1 {
            let targets = targets.reshape(&[shape[0]*shape[1]]).unwrap();
            let loss = cross_entropy(&logits, &targets).unwrap();
            (logits, loss)
        }else{
            let loss = Tensor::zeros((1, 1), DType::F32, &Device::Cpu).unwrap();
            (logits, loss)
        }

    }

But during training, the loss does not reduce from -ln(1/65). Is my implementation incorrect ?
Also, do you have any tips you could give to a newcomer to make the adoption easy ?

Update Readme Section

Thanks @LaurentMazare. I am trying to build a few simple tutorials which could onboard newcomers to candle framework.
This is my optimizer code. Can you review it by any chance ?
let varmap = VarMap::new();
    let optimizer = candle_nn::SGD::new(varmap.all_vars(), 0.003);

    for _ in 0..100 {
        let (x,y) = get_batch(&train_data);
        let xb: Tensor = Tensor::new(&x,&Device::Cpu).unwrap();
        let yb: Tensor = Tensor::new(&y,&Device::Cpu).unwrap();
        let (_, loss) = m.forward(&xb, &yb);
        optimizer.backward_step(&loss).unwrap();
        println!("loss: {:?}", loss);
    }

I am picking up xb and yb randomly.
fn get_batch(data: &[u32]) -> ([[u32; BLOCK_SIZE]; BATCH_SIZE], [[u32; BLOCK_SIZE]; BATCH_SIZE]) {
    let mut rng = ChaCha8Rng::seed_from_u64(SEED);

    let mut xx = [[0u32; BLOCK_SIZE]; BATCH_SIZE];
    let mut yy = [[0u32; BLOCK_SIZE]; BATCH_SIZE];

    for batch_index in 0..BATCH_SIZE {
        let start = rng.gen_range(0..data.len() - BLOCK_SIZE);

        for block_index in 0..BLOCK_SIZE {
            xx[batch_index][block_index] = data[start + block_index];
            yy[batch_index][block_index] = data[start + block_index + 1];
        }
    }

    (xx, yy)
}

Here is a script that should work based on your code. The tricky bit was that the optimizer should take as input a VarMap that contains the variable to optimize. So you want to use the VarMap struct that was also used to create the embedding layer.
Note that I've also removed the unwrap in favor of propagating the errors. I would suggest as possible improvements:

Using AdamW rather than SGD might make tweaking the learning rate easier.
Maybe get_bach could be a rust iterator?

use anyhow::Result;
use candle::{DType, Device, Tensor};
use candle_nn::{embedding, Embedding, VarBuilder, VarMap};
use rand::{Rng, SeedableRng};

pub const BATCH_SIZE: usize = 64;
pub const BLOCK_SIZE: usize = 128;
pub const VOCAB_SIZE: usize = 100;
pub const SEED: u64 = 299792458;

fn get_batch(
    data: &[u32],
) -> (
    [[u32; BLOCK_SIZE]; BATCH_SIZE],
    [[u32; BLOCK_SIZE]; BATCH_SIZE],
) {
    let mut rng = rand::rngs::StdRng::seed_from_u64(SEED);

    let mut xx = [[0u32; BLOCK_SIZE]; BATCH_SIZE];
    let mut yy = [[0u32; BLOCK_SIZE]; BATCH_SIZE];

    for batch_index in 0..BATCH_SIZE {
        let start = rng.gen_range(0..data.len() - BLOCK_SIZE);

        for block_index in 0..BLOCK_SIZE {
            xx[batch_index][block_index] = data[start + block_index];
            yy[batch_index][block_index] = data[start + block_index + 1];
        }
    }

    (xx, yy)
}

#[derive(Debug)]
pub struct BigramLanguageModel {
    token_embedding_table: Embedding,
}

impl BigramLanguageModel {
    // Constructor
    pub fn new(vocab_size: usize, vb: VarBuilder) -> Result<Self> {
        let token_embedding_table = embedding(vocab_size, vocab_size, vb)?;
        Ok(BigramLanguageModel {
            token_embedding_table,
        })
    }

    // Forward pass
    pub fn forward(&self, idx: &Tensor, targets: &Tensor) -> Result<(Tensor, Tensor)> {
        let logits = self.token_embedding_table.forward(idx)?;

        let shape = logits.shape().dims();
        let logits = logits.reshape(&[shape[0] * shape[1], shape[2]])?;

        println!("shape: {:?}", logits.shape());
        println!("targets shape: {:?}", targets.shape().dims()[0]);
        if targets.shape().dims()[0] != 1 {
            let targets = targets.reshape(&[shape[0] * shape[1]])?;
            let loss = candle_nn::loss::cross_entropy(&logits, &targets)?;
            Ok((logits, loss))
        } else {
            let loss = Tensor::zeros((1, 1), DType::F32, &Device::Cpu)?;
            Ok((logits, loss))
        }
    }
}

fn main() -> Result<()> {
    let dev = Device::Cpu;
    let varmap = VarMap::new();
    let vb = VarBuilder::from_varmap(&varmap, DType::F32, &dev);
    let m = BigramLanguageModel::new(VOCAB_SIZE, vb)?;
    let optimizer = candle_nn::SGD::new(varmap.all_vars(), 0.3);

    let train_data = (0..1000).map(|i| i % VOCAB_SIZE as u32).collect::<Vec<_>>();

    for _ in 0..100 {
        let (x, y) = get_batch(&train_data);
        let xb: Tensor = Tensor::new(&x, &dev)?;
        let yb: Tensor = Tensor::new(&y, &dev)?;
        let (_, loss) = m.forward(&xb, &yb)?;
        optimizer.backward_step(&loss)?;
        println!("loss: {:?}", loss);
    }
    Ok(())
}

Thanks @LaurentMazare, this is very useful. AdamW is my next step. I just wanted build everything from scratch. So that different functions could be introduced at different steps. So rust iterator will be my next step.
I am curious about inspiration behind VarBuilder. Does it act as an efficient storage of neural weights even when scope of training function changes ?
Also, I am not seeing any multi core usage. How do I enable it ? This is my htop output during training.

The VarBuilder is used to provide a model with variables so you typically pass it to functions that create model components. These functions can then retrieve a variable if it's loaded from disk or generate a random variable if the model is to be initialized. Variables are kept together with their path, e.g. encoder.layer1.mlp.weight that is used both when reading weights from disks or when saving trained weights to the disk.
Typical example derived from the mnist example:
use candle_nn::Linear;
// This is actually already in candle_nn::linear.
fn linear(in_dim: usize, out_dim: usize, vs: VarBuilder) -> Result<Linear> {
    let ws = vs.get_or_init((out_dim, in_dim), "weight", candle_nn::init::ZERO)?;
    let bs = vs.get_or_init(out_dim, "bias", candle_nn::init::ZERO)?;
    Ok(Linear::new(ws, Some(bs)))
}

struct Mlp {
    ln1: Linear,
    ln2: Linear,
}

impl Mlp {
    fn new(vs: VarBuilder) -> Result<Self> {
        let ln1 = linear(IMAGE_DIM, 100, vs.pp("ln1"))?;
        let ln2 = linear(100, LABELS, vs.pp("ln2"))?;
        Ok(Self { ln1, ln2 })
    }

    fn forward(&self, xs: &Tensor) -> Result<Tensor> {
        let xs = self.ln1.forward(xs)?;
        let xs = xs.relu()?;
        self.ln2.forward(&xs)
    }
}

This means that you can create a new Mlp by using a VarBuilder that is backed by a file for inference, e.g.:
let weights = unsafe { candle::safetensors::MmapedFile::new(weights_filename)? };
let weights = weights.deserialize()?;
let vb = VarBuilder::from_safetensors(vec![weights], DType::F32, &dev);
let model = Mlp.new(vb)?;

Or use a VarBuilder backed by a fresh VarMap if you want to train a model via:
// For training
let varmap = VarMap::new();
let vb = VarBuilder::from_varmap(&varmap, DType::F32, &dev);
let model = Mlp.new(vb)?;
...train...
varmap.save("mlp.safetensors")?;

The embedding layer is by default not multithreaded as it's usually more memory bounded than cpu bounded (we're likely to revisit this though when polishing things if it adds some performance). Matrix multiplication/convolutions and other intensive ops should be using multiple cores.

Thank you @LaurentMazare. That makes sense.
Could you help me out with a few of more queries ?

How would you use manual seed in randn initialization ?
Assumming that let x = Tensor::zeros( (B, T, C), DType::F32, &Device::Cpu)?;, how would you change values at x.i((b,t)) ?
Any chance you could prioritize MPS implementation ? There is a larger audience who will be moving from Llama.cpp and Rustformers/llm to this repo where they will be looking at training and inference at local device. Apple Silicon backend will definitely encourage those users in using this repo.

Manual seeding is a work in progress but is not available at the moment, we're trying to figure out a good way to do it (the rng should probably be part of the device but it's annoying to have devices that are not Copy and that you have to pass by reference so we have to think a bit more about it).
You cannot mutate tensors and it's on purpose, only variables can be mutated. Maybe you want to use something like mask.where_cond(x, y)?
We actually added support for accelerate over the last couple days, it's probably not as good as having full metal support but should already provide some good speed up. You can use it with --features accelerate, please let us know if you see anything weird going on with it as it's certainly less tested than the rest.

Thanks @LaurentMazare. I will check it out.
One more question, are you using accelerate for BLAS, LAPACK or BNNS ? What kind of speed ups have you observed ?

Right, on my linux x86 box I see mkl being regulary 2x or 3x faster. With accelerate on the matmul from cpu_benchmarks.rs I saw a 5x acceleration but that may be a very specific case. Feel free to close this issue if the original question was answered (and obviously to open new ones if you have further/different questions or to re-open if you have more comments on the same topic)

Thanks @LaurentMazare


Add a |text| test-case for issue 5421

Prior to PR #4259, we incorrectly ignored toUnicode for Type3 fonts. Since we now handle that correctly, this patch adds a text test-case to prevent regressions.

/botio test

/botio makeref

Thanks!


Remove fake lag in release mode

Now fake lag is only present in debug mode, which people should be using anyways when testing PRs.
Fixes #10702.

tbh what if we just disabled the mapping command straight up if you aren't on release mode so this + crashes can be avoided entirely

tbh what if we just disabled the mapping command straight up if you aren't on release mode so this + crashes can be avoided entirely

If thats done, you might want to make booting up ss14 in release easier/specify how its done somewhere. A lot of mappers aren't in the technical side and might not really know what running in release mode means/how to do it.

tbh what if we just disabled the mapping command straight up if you aren't on release mode so this + crashes can be avoided entirely

The mapping command is still useful when testing/debugging. If you want to outright disable it, at least it should be a cvar so it can be re-enabled. without having to addd a --force to the command or something like that.

If thats done, you might want to make booting up ss14 in release easier/specify how its done somewhere.

Well if they aren't currently using release mode, that's something that needs to be fixed regardless of whether or not the mapping command gets changed. Though I assumed that mappers just used local release servers & the launcher, instead of a dev env.,

Well if they aren't currently using release mode, that's something that needs to be fixed regardless of whether or not the mapping command gets changed. Though I assumed that mappers just used local release servers & the launcher, instead of a dev env.,

The mapping guide suggests using the dev environment. Additionally, while it says to use release mode, it doesn't actually say how to launch the game in release instead of debug.

it doesn't actually say how to launch the game in release instead of debug.

I added a section to the docs


sonatypeReleaseAll and sonatypeOpen does not affect sub-project

I have a sbt project that contains two sub-projects. Each of the sub-projects use different sonatypeProfileName. I expect that sonatypeReleaseAll will promote all sub-projects and sonatypeOpen will setup publishTo for all sub-projects.

How about using sonatypeReleaseAll (sonatypeProfileName)?

Even it is possible to use specific profiles for sonatypeReleaseAll repeatly, sonatypeOpen still did not work for sub-projects. Repeatly executing sonatypeOpen for different profile makes no sense, because sonatypeOpen will override previously saved repository names.

When developing sbt-sonatype 4.0, I'd like to make it non-auto plugin so that we can use different sonatypeProfiles for each sub module.


Who will update the version on https://flows.nodered.org/node/node-red-contrib-huemagic ?

It‘s great that some pull request were merged but on nodered.org the version is still old. Someone have to trigger the sync with the git-repro….?
thx, Alex

Any news here?


Release

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.1 out of 2 committers have signed the CLA.:white_check_mark: axodox:x: Peter MajorPeter Major seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Update DYLD_FALLBACK_LIBRARY_PATH to the new path

We found a app launch crash where it complains cannot load image
@rpath/libXCTestSwiftSupport.dylib. This dylib is in
"platform/Developer/usr/lib" which has an updated path over the years of
Xcode evolvement.
Updating the DYLD_FALLBACK_LIBRARY_PATH to use the new path so the simulator
can pick up the dylib.

Thanks for finding this...
Could we add a test in the sample app that links with this library to make sure we don't break it again?
Also, is the bug tied to a particular Xcode version?

@chenxiao0228 Can you please review the merge commit (https://github.com/linkedin/bluepill/pull/416/commits/a42d0be63f3ed791a5794e784b003c02b15bba16) I did on this PR?

LGTM


Mergeable Priority Queue: Fibonacci and UpdatableFibonacciHeap

#195 is an open issue with MergeFrom both in UpdatableBinomialHeapPriorityQueue and UpdatableFibonacciHeapPriorityQueue.


Do not count raster tables with the_geom twice in ghost tables

Fixes #7942

CR @gfiorav

Thanks! Please do test this in staging, it can be rally tricky!
📦 it when 🍏 and staging proof!


Fix uppercase prop warning on web

#2176

Also ran into this. @SupriyaKalghatgi Please merge.

This prevents the uppercase warning at Text, but is not the only one.
note is also drilled down to Text.
active is passed to IconNB.
All of them generate similar warnings as they are unexpected props at the final components.

@SynerG I'm ready to add your additions, and I know more places with similar issues. But I also see the lack of response from NB authors. So I don't want to waste my time on it if it is not claimed. I'm sorry. Closed