ngupgrade + hot modules replacement. Possible?

Hello all,
I use ngupgrade and want to insert 'hot modules replacement'.
I get errors when changes happens and the ng1 app is reloaded.
Is it even possible?

Personally, I have no idea, sorry.
This kind of questions are better for stackoverflow :)


[Bug]: Grouped widgets in a container can't be moved back on to the canvas

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Widgets that have been grouped can't be moved back onto canvas since it appears as a red block where ever the widget is moved (even when the widget size fits in the area)

Steps To Reproduce

Group fairly largely sized widgets and then try to move them back onto the canvas

Environment
Release
Version
Cloud

Not occuring anymore, Closing this


Minor Swift 2.3 correction

Sorry I can't find a way to point to the 1.3.1 tag for my pull request.
https://github.com/shaps80/InkKit/tree/1.3.1 is Swift 2.2
This PR update it to Swift 2.3

Check this compare for the right change:

Happy Christmas 🎅 thanks
On Thu, Dec 22, 2016 at 8:59 PM Shaps M<EMAIL_ADDRESS>wrote:

Merged #5 https://github.com/shaps80/InkKit/pull/5.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/shaps80/InkKit/pull/5#event-903436317, or mute the
thread
https://github.com/notifications/unsubscribe-auth/ABcov_vp96tdpQ7aQY6Q_ffNnMoUQwyVks5rKtaYgaJpZM4KsZ-a
.

No worries -- thanks for the contribution. Am updating the README now and then I'll update the Peek one too :)

Oh and Merry Christmas to you too :)


Add safety checks to all _refresh methods

This should prevent accidental changing hardware state when updating the available options. I also added refreshing the options at the end of init in case another remote has already loaded a config.
Finally in e6195d3 I removed some hardcoded setting of bin depth which didn't seem approriate
Should fix: #33

Codecov Report

Merging #35 (c2a2d46) into main (2a6d5da) will decrease coverage by 1.36%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #35      +/-   ##
==========================================
- Coverage   43.11%   41.74%   -1.37%
==========================================
  Files          10       10
  Lines        1234     1248      +14
==========================================
- Hits          532      521      -11
- Misses        702      727      +25

Impacted Files
Coverage Δ

micromanager_gui/_util.py
57.57% <100.00%> (+5.85%)
:arrow_up:

micromanager_gui/main_window.py
69.40% <100.00%> (-7.78%)
:arrow_down:

Continue to review full report at Codecov.

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

working on adding a test

Test is failing because the demo config in this repo (which I based the test on) is different than the one distributed by micromanager: https://github.com/micro-manager/micro-manager/blob/master/bindist/any-platform/MMConfig_demo.cfg
@tlambert03 what do you think is best w.r.t which demo file to use. My inclination is to have a demo file in this repo used for the tests so that upstream  changes to the demo don't mess with the tests.

@tlambert03 I think this is done now

Bump of this - the blockSignals stuff has implications for things like #43, also I have some time to use this on a scope this week and will otherwise need to be basing any improvements off this branch because I don't want to use on a real scope without these safety checks.

Thanks talley!

sorry for the delay @ianhi ... busy week.

no worries at all! I figured as much didn't mean to bug


julia_16-bin: 1.6.1 -> 1.6.2

Motivation for this change
New Julia stable release, our current version (v1.6.1) is as of now unsupported.
Question: As v1.6.1 is now unsupported, should this be backported to 21.05?
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Relase notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Question: As v1.6.1 is now unsupported, should this be backported to 21.05?

Are there security fixes?

On Sat 17 Jul 2021, Sandro wrote:

Question: As v1.6.1 is now unsupported, should this be backported to 21.05?

Are there security fixes?

I have gone over the set of patches twice and do not believe that there are any explicit security patches in there. However, my concern is not so much with the package itself but rather that given that v1.6.1 is now end of life, it means that the Julia package ecosystem and their thousands of individual package authors could in good conscience drop support and introduce security issues for our users this way. Then again, we could argue that vulnerability tracking is strictly speaking something that should be handled upstream and not by us. But, another part of me says that v1.6.2 is only a set of bug fixes and should not break code, so from that perspective it is highly unlikely to be disruptive to our users and to be a strict upgrade in terms of security.
Thoughts? If someone has some general knowledge about handling end-of-life software in Nixpkgs that would be greatly appreciated.

Arguably some of the fixes are silent data corruption issues in corner cases, and in the context of a programming language it is hard to specify further specific impact or security implications.

On Sat 17 Jul 2021, Michael Raskin wrote:

Arguably some of the fixes are silent data corruption issues in corner cases, and in the context of a programming language it is hard to specify further specific impact or security implications.

I would tend to agree @7c6f434c. Mostly though I am just looking to establish how we do this from now on for Julia so that I can set things on “auto pilot” going forward. I suspect @SuperSandro2000 you have a good overview what other programming language packages do, what do you think of our line of reasoning here in favour for a possible backport? Alternatively, who could we ping for an opinion?
A minor side note, with v1.7.0 on the horizon I suppose a similar discussion may arise as v1.6.x will be considered unmaintained once it is released. To make matters worse, v1.7.0 will likely include breaking changes for our users that are on v1.6.x. I suppose we could allow bumping julia-stable-bin to julia_17-bin, but keep julia_16-bin around (perhaps marking it as insecure?).


GitHub Actions orchestrator

Describe changes
Still missing:

Docs
Examples

Pre-requisites
Please ensure you have done the following:

[x] I have read the CONTRIBUTING.md document.
[ ] If my change requires a change to docs, I have updated the documentation accordingly.
[x] If I have added an integration, I have updated the integrations table.
[x] I have added tests to cover my changes.

Types of changes

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

@fa9r Absolutely agree with the duplicated code, I wanted to refactor the docker building somewhere (maybe the StepEntrypointConfiguration) anyway, just didn't get to it yet.


Consider removing the 'AddEntityFramework*' call

Describe the bug
There is a warning related to using AddEntityFrameworkInMemoryDatabase and AddDbContext<MovieReviewsDbContext> at the same time.
Since you're using AddDbContext, this method already adds the necessary EF Core services to the DI container. You might not need to call AddEntityFrameworkInMemoryDatabase explicitly inside AddInfrastructure() extension method in the Infrastructure Layer.
This produces a Warning with the below log message:
[Warning] [Microsoft.EntityFrameworkCore.Infrastructure] 'AddEntityFramework*' was called on the service provider, but 'UseInternalServiceProvider' wasn't called in the DbContext options configuration. Consider removing the 'AddEntityFramework*' call, as in most cases it's not needed and may cause conflicts with other products and services registered in the same service provider.
To Reproduce
Steps to reproduce the behavior:

Run the Application.
Check Console Logs.

Cheers.

Hey thanks mate!  I'll take a look


Async operations don't complete inside testWidgets()

I'm working on my first flutter application, so I may have missed an obvious solution to this. I'm running into problems interacting with json_cache + localstorage within the context of tests.  I've attempted to create a minimal reprodction.
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';

import 'package:json_cache/json_cache.dart';
import 'package:localstorage/localstorage.dart';

void main() {
  TestWidgetsFlutterBinding.ensureInitialized();

  testWidgets('database insert', (tester) async {
    final LocalStorage storage = LocalStorage('test-idea');
    var database = JsonCacheMem(JsonCacheLocalStorage(storage));
    print('before');
    await database.refresh('test', {'k': 'v'});
    print('set value');
  });
}

When I run this test with flutter test it prints before but never prints set value. However, if I use test() instead of testWidgets() the test completes successfully. The broader context of what I'm trying to do is, write a more complex test case where I display a form. That form contains dropdown menus that contain data that would be read from json_cache, but I'm not currently able to get data into json_cache.

I did some more poking around and found that storing data into json_cache works fine if I do it in setUp(). Is it best to avoid writing data inside testWidgets()?

First of all, thanks for opening this issue.

You're welcome :heart: Thank you for putting this library together, I've been loving it so far.

Hi again.
It all boils down to a race condition with the testWidgets method that is causing a deadlock inside Localstorage. All you need to do to fix this is to run your test code inside a tester.runAsync method.
For your particular case, the unit test code should look like this:
testWidgets('database insert', (WidgetTester tester) async {
  tester.runAsync(() async {
    print('before');
    await database.refresh('test', <String, dynamic>{'k': 'v'});
    print('set value');
  });
});

Please let me know if the previous tip worked so that I can close this issue.
Regards.

@rafamizes Yes, using runAsync() to update localstorage works perfectly. Thank you so much.


Packages that define conf.py in standrd locations usually fail

I scanned rolling packages, and looked for packages with a conf.py in a standard location: doc/ or doc/source/. I found 18. Of these, 10 had serious failures (either no rosdoc2 result at all, or failure to show intended documentation:
conf.py failures:

geodesy
naoqi_driver
cv_bridge
mrpt_path_planning
robot_localization
ffmpeg_image_transport (readme_include fails)
ffmpeg_image_transport_tools (just shows package name)
quaternion_operation (just shows package name)
event_camera_py (rst files not shown; failed READMR include)
mrpt2

The reasons were varied, but some common reasons:

error in user conf.py caused abort
.rst files has .. include sections that referenced files not available in our wrapping

Of those who define conf.py, several would be better off with our newer rosdoc2 implementation rather than trying to roll their own. In others, the result would be better under our new documentation section rather than replacing all of the rosdoc2 output.

Just as a FYI, I've been working recently on trying to understand and overcome issues of rosdoc2 failures from a variety of sources, including this one. So this issue is rather stale, but eventually I'll propose PRs for these issues.


Spaceship submit for review "request is forbidden for security reasons"

Opened a discussion a while ago but it hasn't gotten any attention so I'm escalating this to an issue.
I'm trying to automate submitting new builds for external beta review on TestFlight using Spaceship.
Here's the relevant lane:
  lane :spaceshipping do |options|
    Spaceship::Tunes.login('user', 'pass')
    app = Spaceship::Tunes::Application.find("my.bundle.id")

    train = app.build_trains["1.0.0"]
    build = train.last
    build.submit_for_testflight_review!
  end

When I do this I get the error:

This request is forbidden for security reasons - The API key in use does not allow this request

I'm not sure why this is referencing an API key if I've logged in with a username and password, and
How do I get around this?

The user I'm using has "App Manager" access but I also tried bumping it to an "Admin" and that didn't work either. Doesn't seem like that should be necessary anyway.
Unless something has changed recently the fact that submit_for_testflight_review exists implies that it's possible to do this.
It looks like there are other methods using ConnectAPI to do this (e.g. https://github.com/fastlane/fastlane/issues/16294) but I'm not sure where to find documentation for these other methods (post_beta_app_review_submission, patch_beta_app_review_detail etc)

Hi, you could submit a build for external beta review with upload_to_testflight.
If build was previously uploaded to Testflight you could use distribute_only = true.
Please note that if you want to distribute build externally you need to use distribute_external and groups parameters.
You can read more about upload_to_testflight in docs: https://docs.fastlane.tools/actions/upload_to_testflight/
If you want to do it manually in spaceship playground, you could probably do something similar to:

fetch app https://github.com/fastlane/fastlane/blob/master/spaceship/docs/AppStoreConnect.md#applications
app = Spaceship::ConnectAPI::App.find("com.krausefx.app")
select a build, e.g.:
build = Spaceship::ConnectAPI::Build.all(app_id: app.id, sort: "-uploadedDate", limit: 1).first
check if it's ready for submission
build.ready_for_beta_submission?
and submit
build.post_beta_app_review_submission

If you want to know how post_beta_app_review_submission and patch_beta_app_review_detail are used in upload_to_testflight, you could take a look at BuildManager's code:
https://github.com/fastlane/fastlane/blob/master/pilot/lib/pilot/build_manager.rb

Thank you very much I was able to make some progress on this using upload_to_testflight!


Changed the github links from directly pointing to the latest release.

The previous link led to a page which only contained information with
respect to the latest version/release. It is better to point to the
page where all releases appear and the user can search that
page. Otherwise they won't know where to go if by latest release, they
actually wanted the release and not latest development version.

Thank you. That will make it a bit easier to find the Java Windows binaries. :)

There are not Java binaries in the latest tag.


Search causes a 405 Error

When trying to search bookmarks using this extension as of the time of writing, it returns an Error alert() and 405 error in the console, If collect errors is enabled in the Extension's settings page.
Images:

I'm seeing the same thing. Twitter must have changed something on the backend. Hopefully we can work around it.
PRs welcome


The right hand side image is very close to the text I want to reposition it in proper position

@Vishal-raj-1 & @urvashi-code1255 can I work on this issue please assign it to me

Wrong repo.
@Vishal-raj-1


[SPARK-13343] [CORE] speculative tasks that didn't commit shouldn't be marked as success

What changes were proposed in this pull request?
Now with this patch, killed tasks will not be considered as failed tasks and they get listed separately in the UI and also shows the task state as KILLED instead of FAILED.
How was this patch tested?
I have verified this patch manually, when any attempt gets killed then they are considered as KILLED tasks and not considered as FAILED tasks. Please find the attached screen shots for the reference. SPARK-13965/https://github.com/apache/spark/pull/11778 kills the running task attempts immediately when any one of the task succeed and this patch will show consider and show them as KILLED.

Can one of the admins verify this patch?

cc @andrewor14

ok to test

Test build #53998 has started for PR 11916 at commit 7c033b6.

Test build #53998 has finished for PR 11916 at commit 7c033b6.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53998/
Test FAILed.

Test build #54009 has started for PR 11916 at commit 53023dd.

Test build #54009 has finished for PR 11916 at commit 53023dd.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54009/
Test FAILed.

Test build #54016 has started for PR 11916 at commit 7bbe734.

Test build #54016 has finished for PR 11916 at commit 7bbe734.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/54016/
Test FAILed.

Merged build finished. Test FAILed.

Thanks @rxin and @andrewor14 for looking into the patch.
These failed tests in the latest build are not related to this patch and they have been failing in the previous builds as well.

I have moved these changes to the PR https://github.com/apache/spark/pull/11996 for SPARK-10530. @tgravescs, please have a look into https://github.com/apache/spark/pull/11996 when you have some time. Thanks


Feedback Form Feature

Draft PR to keep track of updates!

For frontend purposes, let's get Feedback into its own module, separate from the main module, so that it's not loaded with every page load.

Any updates @tmattvu ?

Any updates @tmattvu ?

No sir, but I just finished group reservations :)

Closing branch!


debug npm package suffers from  CWE-1333 | Inefficient Regular Expression Complexity

Hi,
debug is used and imported by a wide array of npm packages.
It seems to suffer from the following vuln: Category CWE-1333 | Inefficient Regular Expression Complexity
CVE Details
Published: Dec 10, 2020
In NPM debug, the enable function accepts a regular expression from user input without escaping it. Arbitrary regular expressions could be injected to cause a Denial of Service attack on the user's browser, otherwise known as a ReDoS (Regular Expression Denial of Service). This is a different issue than https://github.com/advisories/GHSA-gxpj-cx7g-858c.
Our security pipelines keep detecting this CVE.
Is the CVE legit ?

No, and it's been addressed a ton already - multiple times. Please search the issues tracker next time.


hotspots: Add "Restart Tutorial" to gear menu.

This would be useful for (1) manual testing on chat.zulip.org and (2) allowing users to revisit certain hotspots.

@zulipbot claim

@zulipbot claim --force

@zulipbot claim
(Even though the bot doesn't work atm, I'm claiming the issue to prevent multiple folks working on it)

Closing in favor of #29296. We'll want to consider how users can retrieve the onboarding content we're planning to add, but we can open a new issue for that.


Xiaomi Yeelight component music mode not supported

When I enable the music mode I get below error messages to log. Only switching on/off works, adjusting brightness doesn't work at all in music mode. I'm using HA 0.40.0 and White E27 Yeelight bulbs with firmware 1.4.1_45. I have 4 bulbs and all of them have the same problem.
Earlier discussion:
https://community.home-assistant.io/t/xiaomi-yeelight-e27-bulb-component/695/292?u=brthrsam
17-03-12 00:51:26 ERROR (MainThread) [homeassistant.core] Error doing job: Task exception was never retrieved
Traceback (most recent call last):
File "/usr/lib/python3.4/asyncio/tasks.py", line 233, in _step
result = coro.throw(exc)
File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/core.py", line 1001, in eventto_service_call
yield from service_handler.func(service_call)
File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/light/__init__.py", line 249, in async_handle_light_service
yield from light.async_turn_on(**params)
File "/usr/lib/python3.4/asyncio/futures.py", line 388, in iter
yield self # This tells Task to wait for completion.
File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
value = future.result()
File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
raise self._exception
File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
result = self.fn(*self.args, **self.kwargs)
File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/light/yeelight.py", line 298, in turn_on
self.set_music_mode(self.config[CONF_MODE_MUSIC])
File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/light/yeelight.py", line 196, in set_music_mode
self.bulb.startmusic()
File "/home/homeassistant/.homeassistant/deps/yeelight/main.py", line 486, in start_music
self.send_command("set_music", [1, local_ip, port])
File "/home/homeassistant/.homeassistant/deps/yeelight/main.py", line 313, in send_command
raise BulbException(response["error"])
yeelight.main.BulbException: {'code': -1, 'message': 'method not supported'}

I opened an issue on downstream bug tracker to see how this case should be handled: https://gitlab.com/stavros/python-yeelight/issues/10
Maybe the white bulbs do not support this mode at all and therefore tries to enable it on those should just be ignored either inside homeassistant or in the backend library.

same issue here on both bulbs.

Same here on bulb type YLDP02YL from GearBest http://www.gearbest.com/smart-lighting/pp_361555.html

Which firmware version are you running?


not creating log files inside docker container

Please tell us about your environment:

_winston version?_3.2.1
_node -v outputs:_12.13.1
Operating System? macOS
Language? TS 3.7.2

What is the problem?
This is my winston configuration
import moment from 'moment';
import chalk from 'chalk';
import { createLogger, transports, format } from 'winston';
import 'winston-daily-rotate-file';
const { combine, prettyPrint, printf } = format;

export const logMe = (text: string) => {
    console.log(`[${chalk.green(moment().format('YYYY-MM-DD HH:mm:ss'))}] ${chalk.white(text)}`);
};

const logFormat = printf(({ message }) => `[${moment().format('YYYY-MM-DD HH:mm:ss')}] ${message}`);
const chatLogger = createLogger({
    level: 'info',
    format: combine(
        prettyPrint(),
        logFormat
    ),
    transports: [
        new transports.DailyRotateFile({
            filename: 'logs/chat-%DATE%.log',
            datePattern: 'YYYY-MM-DD',
        })
    ],
    exitOnError: false
});

It works fine when I run it locally but it doesn't create the log file when it's run inside Docker.
When the container starts I can see the logs directory being created but it doesn't create the log file.. anyone with similar experiences?
I made sure to do chmod 777 in the logs directory inside the container but didn't make a difference.
I tried creating the log files before I start the container to see if it would append to those files but it didn't append to the existing files either.

my bad, it's a TS project, I was looking at the project directory rather than the output directory.
In my docker-compose.yaml I had
volumes:
  - ./logs:/usr/src/logs

When it really should have been -./logs:/usr/src/dist/logs because TS is compiling everything into dist directory as I configured in my tsconfig.json

I am having sort of a similar problem. Winston does indeed create a log file in the container but the file does not sync to to one on the host.
`server:
container_name: backend
build: ./backend
ports:

"3000:3000"
volumes:
./backend/logs:/logs`
So when I restart docker-compose, the log file is empty. How do I sync this files and make it persistent?


[DOC]: params & units guidelines in contributing page

Improve "contributing" guidelines on how to find parameter names and their units.

[x] Closes #2205
[x] I am familiar with the contributing guidelines
[ ] Adds description and name entries in the appropriate "what's new" file in docs/sphinx/source/whatsnew for all changes. Includes link to the GitHub Issue with :issue:`num` or this Pull Request with :pull:`num`. Includes contributor name and/or GitHub username (link with :ghuser:`user`).
[x] Pull request is nearly complete and ready for detailed review.
[x] Maintainer: Appropriate GitHub Labels (including remote-data) and Milestone are assigned to the Pull Request and linked Issue.

In coordination with style decided in #2234.
Makes two changes to index pages of functions, to avoid being too verbose and a typo.
Links

https://pvlib-python--2248.org.readthedocs.build/en/2248/contributing/style_guide.html#parameter-names-and-units

Ready for review (thx Dax for reminding me xD). Preview linked in PR body.
Assigning to v0.11.2 for now.

Whatsme added!!
@AdamRJensen can you review and approve (if possible) the PR? As of now (requesting changes) I think it can't get merged.


Fix getting started use of webviews

Fix #133755
cc @mjbvz not sure why this change is needed now, this is regarding the SVG rendering, which does not go through dompurify.

Oh actually, can you see if changing the link's target fixes this?
This was working before right? I wonder if the dom purify sanitization changed something

The SVG's don't go through dompurify, so I really don't know what changed here. With this http links start working again, but command links are still broken.

Not sure how the target would be set for links in SVG's...

No longer needed with 8e35bdb33bfff18881cd6dc68945d0a59d979361


Handle list of map case accurately

Handle list of map case accurately in parquet reader while parsing schema. This should fix #9238

Are you still working on this PR?

Duplicate of https://github.com/facebookincubator/velox/pull/9728


The compiler runs into Stack Overflow if compiled using CLANG on Windows or Visual Studio C++ and set to compile Analog Clock

AECforWebAssembly v1.5 crashes if compiled with CLANG on Windows or Visual Studio C++ and is set to compile Analog Clock. It runs into Stack Overflow. Here is what the debugger in Visual Studio outputs:

So, the error appears to occur in Analog Clock program on line 358, when compiling the 60 token. convertToInteger64 calls compile, which in turns calls convertTo which again calls convertToInteger64. I do not think this loop is infinite, as the error disappears on CLANG if the program is compiled with -O3 (although I could be triggering some Undefined Behavior again leading to my program behaving unpredictably). But, obviously, the recursion runs deep enough to cause Stack Overflow in some cases under some compilers.
UPDATE: This problem appears not to exist under any version of GCC, be it under Windows, Linux or FreeDOS.

A Discord user called @zero9178 commented the following:

Do you know what a stackoverflow is? Chances are you got a recursive function and/or some very large objects that causes your stack to overflow. Optimizations will make the code and functions and such smaller hence it working when using optimizations. Debuggers should halt on stack overflow, check the recursive functions there. If it's easy, try turning the recursive algorithm into an iterative one, otherwise try reducing the size of some classes or allocate some things on the heap. Hard to tell where the issue is. There is also -fstack-usagein gcc that will tell you how many bytes a function occupies
Should help with the search

Perhaps we can at least make the problem less severe by outputting a sensible error message in that case. I have started a forum thread asking how to do that: https://atheistforums.org/thread-63150.html

I have tweaked it into working when compiled using CLANG on Windows, but I still have not managed to make it work if compiled using Visual Studio: https://github.com/FlatAssembler/AECforWebAssembly/commit/8e70e2ff81be1d487a448d09adb32fe65d58d04c

Unfortunately, I just tried compiling AECforWebAssembly with the latest version of Emscripten, and I get the same "Stack Overflow" error when compiling the Analog Clock program. This time, compiling with -O3 optimisation does not help.


Add package nimstrict

A linter for enforcing case sensitivity locally without disturbing the case insensitivity of the nim language itself
https://github.com/jmsapps/nimstrict

compiler already contains this with --styleCheck


Failed upgrading database from <IP_ADDRESS> to 6.0.0 on Gradle

Describe the bug
Failed upgrading while running dependencyCheckUpdate Gradle task.
It leaves "resource data/upgrade_4.2.sql not found."
Version of dependency-check used

Previous: <IP_ADDRESS> (OWASP Dependency Check Gradle Plugin)
Current: 6.0.0 (OWASP Dependency Check Gradle Plugin)
Gradle 6.3

Log file
https://gist.github.com/sekido/70024fbc9a9592c522e1c24f40eb1713
To Reproduce
Steps to reproduce the behavior:

Run dependencyCheckUpdate Gradle task with OWASP Dependency Check Gradle Plugin version <IP_ADDRESS>
Rewrite from <IP_ADDRESS> to 6.0.0
Run again dependencyCheckUpdate Gradle task, then failed

Expected behavior
Complete upgrade database and succeed running gradle task.
Additional context
Add any other context about the problem here.

As documented in the release notes there are breaking changes in the database schema and the new release won't work with Oracle, your "expected behaviour" is a false assumption

@mprins Thank you for your comment.
I've confirmed and accepted what breaking changes are.
The database before 6.0.0 doesn't have CVSS 3.x version number, so there is no way to upgrade it completely. (#2547)
I use this tool in my CI/CD pipeline to find vulnerabilities as soon as possible.
The pipeline has its old database, so I'm planning how to maintain it manually.
I hope the tool upgrades the database seamlessly, for instance, fill up with '3.x' for lost version numbers.
Thanks for the great tool!

In most cases - minor database updates are made and are backward compatabile. Unfortunately, in this case we had to make significant change. The only resolution would be to run dependency-check's purge command and then run an update and rebuild the database.

In addition - the changes made to how the ecosystem is tracked on the CPE entries was completely revamped and would be impossible to retrofit onto an existing database.

Gradle users - please upgrade to <IP_ADDRESS>.


Document nameeth and how we keep track of contract's names

We need a better way to address contracts by name.

Renamed to ethname and made into its own repo.


ListBox SelectionMode=Multiple no events

ListBox does not work properly when SelectionMode is set to Multiple.
Tested on Avalonia 0.9.2
Simple repro
type MainWindow() as this =
    inherit Window()
    do
        let listBox = new ListBox()
        listBox.SelectionMode <- SelectionMode.Multiple
        listBox.Items <- [
            "Item 1"
            "Item 2"
            "Item 3"
            "Item 4"
        ]

        listBox.SelectionChanged.Add(fun _ ->
            // only fired if a single item is selected. does not fire
            // for multiple selected items
            printfn "selection changed event"
        )

        listBox.GetSubject(ListBox.SelectedItemsProperty).Add(fun args ->
            // never fired when a selection changed
            printfn "subscription 'SelectedItemsProperty'"
        )

        base.Content <- listBox

The same as #3448 ?

@FoggyFinder not exactly, ListBox.SelectedItemsProperty subscription also does not work

Hoping to fix this with https://github.com/AvaloniaUI/Avalonia/pull/3469 although we may have to remove SelectedItems so may be an API breakage.

ok 👍 will this be fixed in a dot release ?

Probably for 0.10 as it's a breaking change.

ok.

@JaggerJo Please note that simply subscribing to SelectedItems is not enough, you need to subscribe to collection changes since we don't reassign SelectedItems but instead add/remove from the collection. Or bind your own collection (like ObservableCollection) and listen to CollectionChanged events on it.

@MarchingCube Wouldn't it be simpler (at least from a consumer perspective) if it would just work ?
IMHO the current behaviour is technically correct and makes sense, but is a bit weird for a consumer. FuncUI currently exposes:

onSelectedItemChanged(subscription of  SelectedItem)
onSelectedItemsChanged (subscription of SelectedItems)

and their behaviour is different (while not technically).
SelectedItem gives you the newly selected item because its reassigned while SelectedItems does not because its a mutation.

The current solution is better in scenarios where you transform the collection of selected items.


Correction for raw affiliation Department of Psychology, Western University.

Correction needed for raw affiliation Department of Psychology, Western University.
raw_affiliation_name: Department of Psychology, Western University.
new_rors: 02grkyz14
previous_rors: 02agqkc58
works_examples: W4361279043;W4321376816;W4388193897;W4388734565;W4317358871;W4386027195;W4323075331;W4377014268;W4387579313;W4387820405;W4389743227;W4390029901
contact: 1168b1a03da51854db6c476c06a85e23:3fee03fd35f913f3 @ uwo.ca

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Add spacetiger

see PR in SpaceTiger repo (branch onboard) before merging!!

@nicholaspad changes made!

@ysl-ee feel free to merge :)


D6Starwars.css lightmode/darkmode fix

fixes character sheet fields for lightmode and darkmode css

Submission Checklist
Required

[ x] The pull request title clearly contains the name of the sheet I am editing.
[ x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[ x] The pull request makes changes to files in only one sub-folder.
[ x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: <   >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: <   > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: <   > (i.e. Dungeons & Dragons, FATE)

[ x] I have followed the Character Sheets Standards when building this sheet.

[ ] This sheet has been made on behalf of, or by, the game's publisher.
[ x] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: <   d6holocron.com >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

I added these:
.sheet-lightmode .characterviewer input{ color:black; }
and
.sheet-darkmode mode .characterviewer input{ color:white; background:black; }

Character Sheet Info Roll20 Internal Use only.

This pull request should fix lightmode and darkmode issues on the character sheet: and should look something like this. If in review, this is not how character sheets look, please reject or modify to fix.

@Anduh @Moondancer83 @tgtrammel are you folks good with the proposed changes?

Thanks for the effort 👍
However, please check the current version (2.44).
The above issue seems to be fixed already.
Light

Dark

Ok great. I will close this request. Yesterday there was a complaint on the Star Wars D6 discord so I looked at the issue. I guess he should have just waited a day. :)


This is a test issue for gh-sync

Describe the bug
A clear and concise description of what the bug is.

Leaving an additional comment


No way to access alertmanager

The current pipeline makes it so you can not access alert manager. Didn't notice it was missing from the port list at the bottom at first went looking and saw the password is not set it would appear.
simply adding below to pipeline.yml and params file allows access to alertsmanager
Pipeline.yml file add to the deploy vars section:
    alertmanager_password: ((alertmanager_password))

Params file add:
alertmanager_password: PASSWORD

If desired will submit pull request for this and other var issue I found under ticket https://github.com/pivotal-cf/pcf-prometheus-pipeline/issues/11

Similar to #11 - this seems to be caused by not using Credhub as a BOSH config server. In this case however, the operator has a reason to know the password so I added this to params.yml. Thank you!


Just crashed during usage is all

Describe the bug
A clear and concise description of what the bug is.
To reproduce
Steps to reproduce the behavior:

Go to '....'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Log file
Please upload the log file here so that we can understand your issue better.

You can access it from Settings->About->Open log location.
or
%localappdata%\Packages\49306atecsolution.FilesUWP_et10x9a9vyk8t\LocalState

You should see a file in this directory called debug.txt or/and debug_fulltrust.txt.
Screenshots
If applicable, add screenshots to help explain your problem.
System Information

OS Version: [e.g. Windows 10 20H2 19042.804] (Press WIN + PAUSE/BREAK, use the copy button at the bottom)
App version: [e.g. v1.0] (In the app, go to Settings -> About, the version is shown at the top)

Additional context
Add any other context about the problem here. Does this problem occur again after restarting the app?

Hello thanks for this report When opening an issue please always specify the app version and post the app's log files so we can investigate the issue. Feel free to edit this issue description and we'll reopen this ;)

Oops! Thanks! I wasn't quite sure how to submit that stuff, I'm pretty new
to Github.
On Tue, Mar 16, 2021, 1:48 PM Marco Gavelli @.***>
wrote:

Hello thanks for this report. When opening an issue please always specify
the app version and post the app's log files so we can investigate the
issue. Feel free to edit this issue description and we'll reopen this ;)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/files-community/Files/issues/4107#issuecomment-800477012,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AOFR2F3ZONLMXB5455U7NBTTD6KYXANCNFSM4ZIX334A
.


Add https:// to beginning of blog url if absent

Currently our individual blog url doesn't have https:// in the <a>, so clicking it will bring us to hats.sg/quanyang.github.io for example.

why don't we just fix it in the profiles instead?

Looks cooler without the https :P

But yes changing the profile would be safer, not sure if the current code misses anything


remove geo_interface functions

Fix https://github.com/projectmesa/mesa-geo/issues/32
Change model.grid to model.space for better naming convention, since GeoSpace is not necessarily a grid.

Change model.grid to model.space for better naming convention, since GeoSpace is not necessarily a grid.

Make sense. I'm up for attribute names in projectmesa/mesa to be renamed to space as well.

You should resolve the merge conflict by pull --rebase on top of current master.

Done. (But this rewrites the history and need to force a push.)

Make sure to not make another PR after this one, unless it is for flake8 and Black fixes. Otherwise, the merge conflicts would be nasty.

OK, the last thing is if you could squash the 4th commit into the 1st commit via the interactive rebase, since they logically are within the same theme.

Done!


less: fix Using GNU Mirror

GNU has regional mirrors

Merged and added back original link as fallback. Thanks for your contribution.


refactor(client): use "response.elapsed" to get cost time in profile

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 1 (0.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 85.754%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

tensorbay/client/profile.py
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
6140

Relevant Lines:
7160

💛  - Coveralls


ngAnimate makes the grid behave and look wierd.

im having hard time reproducing it outside my app :(
but whenever i add 'ngAnimate' the grid start having bad behavior.
i'll work on a plunker hope i can get it to flicker.

Which version are you using?  This will be much easier to diagnose with a plunker.

im using v1.3.11
i cant reproduce it on plunker :(

Which version of the grid are you using?
The grid should have animations disabled if $animate is available.
On Feb 15, 2015 5:54 AM, "mikila85"<EMAIL_ADDRESS>wrote:

im using v1.3.11
i cant reproduce it on plunker :(
—
Reply to this email directly or view it on GitHub
https://github.com/angular-ui/ng-grid/issues/2757#issuecomment-74414559.

ui-grid - v3.0.0-rc.19
how do i disable animate on grid?

It should be disabled automatically. I will look into it.
On Feb 16, 2015 6:12 AM, "mikila85"<EMAIL_ADDRESS>wrote:

ui-grid - v3.0.0-rc.19
how do i disable animate on grid?
—
Reply to this email directly or view it on GitHub
https://github.com/angular-ui/ng-grid/issues/2757#issuecomment-74499781.

OK by default the header and footer has animations disabled.

Strange, $animate.enabled() is a noop in latest angular versions...

I think you're going to need to give us some direction as to how to reproduce. Otherwise we're kind of stuck, unable to track it down :(

not able to reproduce it, just removed ng-animate for now :(
thanks, close please.


Remove @graphql-tools/wrap dependency and replace functionality

Fixes: https://github.com/mercurius-js/auth/issues/74

Need to run some benchmarking, will update the PR when I've done this!

Apologies for the lateness on this, something came up last week and was unable to work on OS - will aim to run the benchmarks and get this out today/tomorrow! :)

Just ran the benchmarks and no noticeable difference - in-fact, it's ever so slightly quicker


WHO WE ARE Filler Text

Scroll down the Who We Are Section and update the VP of Franchise Development message right behind the image.

Make sure to follow the character counts.

Make sure both paragraphs have the same character spacing. So, it shouldn't affect the layout of the section.

Add text that follows SILK Corp's vision.

This issue is completed. Can you please close this issue?


fix: network-delete may fail immidiately after deleting vm

这个 PR 实现什么功能/修复什么问题:
修正：

阿里云删除主机后立即删除网络可能失败
增加vpc／network的sync接口

是否需要 backport 到之前的 release 分支:

release/2.11
release/2.12

/area region
/cc @ioito @tb365

Codecov Report

Merging #3696 into master will increase coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #3696      +/-   ##
=========================================
+ Coverage    6.94%   6.95%   +<.01%
=========================================
  Files         500     500
  Lines       83980   83994      +14
=========================================
+ Hits         5836    5838       +2
- Misses      77647   77660      +13
+ Partials      497     496       -1

Flag
Coverage Δ

#aFlag
6.95% <0%> (ø)
:arrow_up:

Impacted Files
Coverage Δ

pkg/compute/models/vpcs.go
1.76% <0%> (-0.06%)
:arrow_down:

pkg/compute/models/networks.go
0.56% <0%> (-0.01%)
:arrow_down:

pkg/multicloud/aws/securitygroup.go
0% <0%> (ø)
:arrow_up:

pkg/compute/models/guest_actions.go
0% <0%> (ø)
:arrow_up:

pkg/compute/guestdrivers/baremetals.go
1.58% <0%> (+0.02%)
:arrow_up:

pkg/compute/models/loadbalancercertificates.go
4.43% <0%> (+0.04%)
:arrow_up:

pkg/appsrv/response.go
69.23% <0%> (+3.07%)
:arrow_up:

Continue to review full report at Codecov.

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

/lgtm

/lgtm
/approve


Unintended unicode "replacement character" within the data stream

Summary of Problem
(Please answer all 3)

What are you trying to do?
I'm using a serial port interface (link) within node.red which relies on this library.
What happens?
When ever an invalid character is received, it is replaced with [EF BF BD] sequence (original byte is lost). Searching I determined that it represents a Unicode "Replacement Character" (link). This issue occurs for characters with MSB (most significant bit) set. Binary data which is not contained among the regular string does not appear to be exempt.
Issue appears similar to unsolved issue #1209 (link)
What should have happened?
Original byte / data are left as is

Code to Reproduce the Issue
const serialport = new SerialPort(path)

// Code

Versions, Operating System and Hardware

SerialPort@ 9.0.1
Node.js v 12.18.3
OS: Linux / raspberrypi
Hardware and chipset: FTDI

I'll have to think about code to reproduce the issue, but you can try creating a loop-back socket and sending "Hello World" while having any of the characters in the middle having a MSB set.

Here is an example of data corruption:
https://jsonblob.com/b8d60da6-f005-11ea-ae37-d9193694cf04
The payload is the string after node red processing, extra spaces are removed as well as MSB of the individual characters cleared, that is why the corruption shows up as "o?=" whereas a single ":" with MSB set was transmitted. The controller in question uses MSB as an indicator that this character should be blinking.
Note that raw data is included, the string takes place from position [4] to position [46], corruption occurs from 33 to 35 whereas three characters are transmitted whereas only one ":" & 0x80 = 3A & 0x80 = 0xBA = 186  was transmitted.

I apologize, found the issue within my code which was dealing with buffer as string, thereby adding an error. I should really skip late night coding sessions 🙇

For me the buffer is forced to the string with predefined encoding, very annoying

Help pls, how to fix this?


Modernize

Hi @justinmayer !
This is hopefully all the code pieces to "modernize" this plugin. In particular:

move from setup.py to poetry
reorganize into a namespace plugin
add common project supports, like pre-commit config and common tasks.py
updated Changelog format
add a very basic test site

There are a few things that I can't do:

[x] the repo should be renamed, likely to "nojekyll" (JM: Done!)
[ ] AutoPub needs to be configured
[ ] any prep to push the package to PyPI
[ ] version 2.0 released!

Let me know if there's anything else I need to do on my side to move this forward.
Once this is done, I still have several more plugins that I'm maintaining that were originally pulled the common repo. Let me know how best to move forward on those too!

@MinchinWeb: Thanks for working on this. I renamed the repository. I am traveling for the next few weeks but will try to find time to review this PR as soon as I can. 😊

Enjoy your trip!

@justinmayer ready to merge?

bump... @justinmayer is this ready to merge?

Hi @MinchinWeb. Please accept my sincere apologies for the absurd delay in reviewing this pull request, which I clearly overlooked during what was a very hectic period.
In terms of what to do next, my suggestion would be to follow the steps listed in the Pelican Plugin Template README (mainly, choose an output location and then run something like pipx run cruft create https://github.com/getpelican/cookiecutter-pelican-plugin --output-dir $HOME/Desktop/nojekyll-plugin-generated) and enter the appropriate values when prompted in order to generate current, up-to-date plugin scaffolding. Then you can diff what you have here with that scaffolded plugin in order to merge the upstream template changes with your plugin's code. (In the future, it will be much easier to maintain alignment with upstream template changes via Cruft.)
Does that make sense? Let me know — I am available to help out with anything that's not clear. Once again, very sorry for the delay, and many thanks for all your patience.

Thank you for coming back to this!
I will take a look at this again; Cruft looks like it could be a gamechanger, I hope it likes up to it's promise! I'm not sure of my timeline, but updates will be posted here...


Complete linkages from Freecen2 Civil Parishes to Freecen2 Places

Many Civil Parishes named in TNA have no current entry in the Places collection.
This connection is required to ensure that we can ultimately  use the Place and a Nearly capability.
Manual additions of connection will take months if not years.
As a temporary measure we will assign the Place for a Piece to the Civil Parishe if a direct Place does not exist.
If the Piece does not have a Place we will assign the Place for the District to both the Piece and the Civil Parish

As a result of making the district /place linkage we have the following situation

1841 has a unique problem in that the params are using hundreds rather than places. Not sure how to address this.
In the years after 1861 onwards the use of LND creates a specific problem as many of the places are in MDX KEN etc. It appears there are 30 LDN Districts to be located.
The effort to identify places for districts is now a relatively limited task.

1901 is caused by Yorkshire being used by TNA rather than a riding

Have added the ability to list those Districts/pieces/civil parishes that have no place and those pieces/civil parishes that are using the district place. Deployed to test3

and those pieces/civil parishes that are using the district place.

@PatReynolds @richpomfret to take a look and have a play/test with this.

I have tried it within the linking of the PARMS and it seems to work well in that context
Geoff

Need to ensure that coordinators are aware of their need to clean up the linkages

Kirk
That is part of the Newsletter that is scheduled for week commencing 16 November. The detail is scheduled for week commencing 7 December so that nobody starts trying to do things whilst you are setting up the system.
Geoff
From: Kirk Dawson<EMAIL_ADDRESS>Sent: Monday, 9 November 2020 11:49 AM
To: FreeUKGen/FreeCENMigration<EMAIL_ADDRESS>Cc: geoffj-FUG<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [FreeUKGen/FreeCENMigration] Complete linkages from Freecen2 Civil Parishes to Freecen2 Places (#951)
Need to ensure that coordinators are aware of their need to clean up the linkages
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub https://github.com/FreeUKGen/FreeCENMigration/issues/951#issuecomment-723708325 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AKCPIFI7VBKG2RHSWEWB3F3SO5C7ZANCNFSM4QTXZHRA .  https://github.com/notifications/beacon/AKCPIFLHKZFDB42A2A7GYITSO5C7ZA5CNFSM4QTXZHRKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFMROTJI.gif


Add FZF builtin for searching vim.v.oldfiles

I think you can try to send the results withJob:send rather than the writer strategy... but I'm not 100% sure. I'd have to test it out. You should not have to shell out to echo to make it work.
Also, you have considered instead trying to use  sorter to fulfill the same idea you're doing here? I can show an example later if you want. I don't think we need to require fzf to make this happen (which is kind of the point of telescope ;) )

I think you can try to send the results withJob:send rather than the writer strategy... but I'm not 100% sure. I'd have to test it out. You should not have to shell out to echo to make it work.

Okay, I'll try that out and see if it works. Thanks! The echo definitely feels clunky.

Also, you have considered instead trying to use  sorter to fulfill the same idea you're doing here? I can show an example later if you want. I don't think we need to require fzf to make this happen (which is kind of the point of telescope ;) )

I have not; an example would be great! I guess I didn't really think about the fzf requirement; my bad!

@tjdevries PR no longer uses FZF ;)

Had to rebase to fix some conflicts. I'm going to change this a bit, since I'm changing the interface, but I'll merge for now. TY!


Create new client for IOErr

Hi there, I'm really sorry to do this, but I have to reject this PR as it is. Unfortunately retrying commands is not a general purpose solution to almost any problem, this one included. The main reason being that we don't really know if the original attempt made it to the server or not. It may well have made it, but then we didn't receive the response for whatever reason. For commands like INCR or LPOP this will result in inconsistent data from the program's point of view.
Again really sorry, in the future feel free to submit an issue for what you plan to do for a PR before doing it, so we can avoid this kind of thing. I'll respond to your issue now too. Thanks!


GradleException: org/jetbrains/kotlin/builtins/StandardNames$FqNames

Expected Behavior
Updated from Detekt 1.15 to 1.16 and got this error when running "gradle detekt"
Observed Behavior
relevant part of stacktrace
Caused by: org.gradle.api.GradleException: org/jetbrains/kotlin/builtins/StandardNames$FqNames
        at io.gitlab.arturbosch.detekt.invoke.DefaultCliInvoker.invokeCli(DetektInvoker.kt:62)
        at io.gitlab.arturbosch.detekt.Detekt.check(Detekt.kt:239)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:104)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:58)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:51)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:29)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$2.run(ExecuteActionsTaskExecuter.java:494)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:29)
        at org.gradle.internal.operations.DefaultBuildOperationRunner$1.execute(DefaultBuildOperationRunner.java:26)

Steps to Reproduce
Gradle Version 6.8.3
Kotlin version 1.4.31
Add detekt 1.16 to build
run "gradle detekt --stacktrace"
Context
Can't upgrade to 1.16
Your Environment

Version of detekt used: 1.16
Version of Gradle used (if applicable): 6.8.3
Gradle scan link (add --scan option when running the gradle task): N.A...doesn't finish so no scan
Operating System and version: OSX
Link to your project (if it's a public repository): N.A.

Hey @kenyee 👋

* N.A...doesn't finish so no scan

Which version of Java are you on? Don't you mind running ./gradlew --stop and retrying?
Also you should be able to share a Gradle scan even if the build failed :)

Also you should be able to share a Gradle scan even if the build failed :)

ahh..didn't realize that..should have tried it :-)
https://gradle.com/s/rg4l3nzwjgeui
Java version is
➜  java -version
openjdk version "11.0.10" 2021-01-19
OpenJDK Runtime Environment GraalVM CE <IP_ADDRESS> (build 11.0.10+8-jvmci-21.0-b06)
OpenJDK 64-Bit Server VM GraalVM CE <IP_ADDRESS> (build 11.0.10+8-jvmci-21.0-b06, mixed mode, sharing)
It also fails in our CI which is running pretty plain OpenJDK8 on Centos so I don't think it's because I'm using JDK11.

might need this link instead: https://scans.gradle.com/s/rg4l3nzwjgeui

You seem to have inconsistent versions (1.4.10 vs 1.4.30) for plugins in your project:
org.jetbrains.kotlin.jvm | 1.4.10 | 1 usage | org.jetbrains.kotlin.gradle.plugin.KotlinPluginWrapper |
-- | -- | -- | -- | --
  | org.jetbrains.kotlin.plugin.allopen | 1.4.30 | 1 usage | org.jetbrains.kotlin.allopen.gradle.AllOpenGradleSubplugin |
  | org.jetbrains.kotlin.plugin.scripting | 1.4.10 | 1 usage | org.jetbrains.kotlin.gradle.scripting.internal.ScriptingGradleSubplugin |
  | org.jetbrains.kotlin.plugin.spring | 1.4.30 | 1 usage | org.jetbrains.kotlin.allopen.gradle.SpringGradleSubplugin

https://scans.gradle.com/s/56gyz425dwolu/plugins
Fixed...was specifying this to match the Kotlin version:
id 'org.jetbrains.kotlin.plugin.spring' version '1.4.10'
same error as before...

I think there are two things we could try:

Disable UseIsNullOrEmpty, since this is the culprit rule.

Try with upgrade Kotlin to 1.4.21, because detekt 1.16.0 is shipped with this Kotlin version (https://github.com/detekt/detekt/pull/3521/)

Can't switch to 1.4.21 because Spring released w/ 1.4.10 :-(
I'll try disabling that other rule...might be worth adding a try/catch for this in the Detekt code too if it works?

Yeah that's a good suggestion. I think checkstyle has this behavior to catch exceptions if it is thrown inside each rule.

Following up on this.  I upgraded to 0.16.0.  Then ran detektGenerateConfig to create a new config and the detekt.yaml already has it turned off by default:
UseIsNullOrEmpty:
active: false
Ran detekt and get the same error so it seems like it's turned off by default...but causes an error w/ Kotlin 1.4.10 still.

https://github.com/detekt/detekt/pull/3585 may help to resolve the problem: When the rule has active: false, it should not instantiate the rule.


Error on cargo lock

Bug description
When the CI action runs, i keep getting this error about the cargo.lock that reads
note: Downloading arbiter 0.4.13
 Downloading crates ...
  Downloaded arbiter v0.4.13
  2023-12-19T16:09:03.424747Z ERROR  error while running git with args `["checkout", "main"]:
- stderr: error: Your local changes to the following files would be overwritten by checkout:
	Cargo.lock
Please commit your changes or stash them before you switch branches.
Aborting

Error: error while running git with args `["checkout", "main"]:
- stderr: error: Your local changes to the following files would be overwritten by checkout:
	Cargo.lock
Please commit your changes or stash them before you switch branches.
Aborting
Error: Process completed with exit code 1.

the yml i have looks like
name: Release-plz

permissions:
  pull-requests: write
  contents: write

on:
  push:
    branches:
      - main

jobs:
  release-plz:
    name: Release-plz
    runs-on: ubuntu-latest
    steps:
      - name: Checkout repository
        uses: actions/checkout@v4
        with:
          fetch-depth: 0
      - name: Install Rust toolchain
        uses: dtolnay/rust-toolchain@stable
      - name: Commit Cargo.lock
        run: |
          git config --local user.email<EMAIL_ADDRESS>          git config --local user.name "GitHub Action"
          git add Cargo.lock
          git commit -m "Update Cargo.lock" || (git add Cargo.lock && git commit -m "Update Cargo.lock") || echo "No changes to commit"
      - name: Check git status
        run: git status
      - name: Run release-plz
        uses<EMAIL_ADDRESS>        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}

Would you like to work on a fix? [y]

To Reproduce
The bug exists in the main branch of our repository here
Expected behavior
Expected behavior is that the release-plz action succeeds and opens the release PR
I feel like i could be missing something simple but i am not sure where i am going wrong. The tool usually functions as intended and has been really useful for us. I have tried recommitting the cargo.lock but things are still failing.

I can reproduce this by running release-plz update locally in the repository, nice 👍
I'm looking

Here's the fix: https://github.com/MarcoIeni/release-plz/pull/1152
You can compile release-plz locally on this branch and run it locally on your repo.
I will ship this fix soon in the GH action.

Thanks @0xJepsen for reporting.
Thank you @MarcoIeni, for the quick fix!

Thanks for the prompt fix!

I released the new version of the GitHub action, let me know if you still have problems :)

You can compile release-plz locally on this branch and run it locally on your repo.
I will ship this fix soon in the GH action.

What is the best way to update the github action? Do i need to do this? Unsure how to test the fix

still getting the error here
    Updating crates.io index
error: all dependencies must have a version specified when publishing.
dependency `artemis-core` does not specify a version
Note: The published dependency will use the version from crates.io,
the `git` specification will be removed from the dependency declaration.
  2023-12-21T21:59:44.129772Z ERROR  failed to release package

Caused by:
    failed to publish arbiter-engine:     Updating crates.io index
    error: all dependencies must have a version specified when publishing.
    dependency `artemis-core` does not specify a version
    Note: The published dependency will use the version from crates.io,
    the `git` specification will be removed from the dependency declaration.

Error: failed to release package

Caused by:
    failed to publish arbiter-engine:     Updating crates.io index
    error: all dependencies must have a version specified when publishing.
    dependency `artemis-core` does not specify a version
    Note: The published dependency will use the version from crates.io,
    the `git` specification will be removed from the dependency declaration.
Error: Process completed with exit code 1.

Is is possible that it's because one of the crates hasn't been updated yet?

What is the best way to update the github action?

If you use<EMAIL_ADDRESS>here, you will get the latest v0.5.x version.
E.g. when I publish v0.5.34 you won't need to change anything, while if you are on<EMAIL_ADDRESS>you would need to update manually.
Anyway, now you are on v0.5.33 which is the latest 👍
Now I'm checking your error 👀

Your error doesn't depend on release-plz.
cd arbiter-engine
cargo publish --dry-run

Here the cargo book explain the reason:

Thank you


feat: add Send to internal error

When changing the base branches to next in the Miden Client (https://github.com/0xPolygonMiden/miden-client/pull/617), one of the errors is caused because an element of AssetError is not Send. By changing this line the error in the client is fixed (tested it locally).

Forgot to set up commit signing. I just signed the same commit, I'll wait for the CI just to be sure before merging


Handling situation when jobs can't be executed because there are no executors

So it is not silently indefinitely queued. Some status information would be nice.

There is a default timeout: 5 minutes. Still there is needed a better indication what is happening wrong.

Fixed. When there are no agents then a job ends with error.


Mac 2.0.4 Issue

There was an unexpected error. Please open a bug report on the project's Github page or contact one of the developers. Stack Trace: RangeError [ERR_SOCKET_BAD_PORT]: Port should be >= 0 and < 65536. Received NaN.

Could you please share your config file? Or are you running a fresh clean version?

@hadphild are you still having this problem?
If you are, I would recommend restarting your computer to see if there's a hidden process taking up port 4455.

Closing due to no response.
If you still experience the issue, please re open and add details.


Mixtral prefill 128-32k

Ticket
Mixtral bringup
Problem description
Prefill bringup for Mixtral. Supports sequence lengths up to 32k. Unit tests included.
Prefill+decode demo mode included for 128 seqlen.
Not included in this release:

Demo tests with higher sequence lengths (requires very large prompt files, which will have to be moved into CI workspace)
Perf evaluation for prefill

Checklist

[ ] Post commit CI
[ ] T3k unit tests
[ ] T3k frequent tests
[ ] T3k demo tests
[ ] T3k perf tests

Rebased to latest tip and fixed all merge conflicts.
Running all relevant pipelines (linked in ticket main description).
Only missing an updated README - will push it soon.

Just pushed prefill perf test support up to 2k, plus a few other bugfixes and rebased to latest tip.
Re-running all tests now that the pipelines are slightly better.
@ttmchiou Can you provide a review of this PR?
Some changes of note related to pipelines:

Upped the mixtral unit test timeout from 30 min to 45, since the prefill tests for larger seqlens take a few minutes to complete.
Added prefill tests to all the t3k pipelines. It should all be within the timeout, but given the status of the pipeline workers it has been hard to measure it. I don't expect any more updates from our side (other than rebasing conflicts) and so re-kicked all tests.


RDP Wrapper 17763.771 Listening, still getting "Another user is signed in.." error.

Used auto updater, re-installed everything, powered down restarted services, nothing. Any hints?

Try this rdpwrap.ini

Used auto updater, re-installed everything, powered down restarted services, nothing. Any hints?

Hi, I've had great success with this variant from #906
https://github.com/SobieskiCodes/RDPWrap
The key for me was to:

Grant Everyone as Owner and Everyone : Full Control to C:\Program Files\RDP Wrapper
Extract all bits to that directory
Perform all operations from that directory
Run all .bat files as admin (elevated)

Notice if rdpwrap.dll is locked and cannot be replaced, then in an elevated cmd.exe before running the batch files, perform a net stop UmRdpService & net stop TermService
I didn't have to reboot at all, even with past RDPWrap running and RDP svchost.exe operating as normal.

I have my windows updated to date and this method has stopped working, any ideas?

I think this is not the main problem. I have never played with access to directories on windows 10.
I have administrator rights.
I installed like this:

create folder RDPWrap-v1.6.2
add the directory RDPWrap-v1.6.2 to exceptions in the antivirus settings or windows defender
unpacked the RDPWrap-v1.6.2 archive in C:\RDPWrap-v1.6.2
run as administrator install.bat
create a directory C:\Program Files\RDP Wrapper\
stop the service TermService

copy the latest (fresh) files rdpwrap.zip from the archive for my version of the operating system in the directory C:\Program Files\RDP Wrapper\
start the service TermService
reboot OS
check the operation of the C:\RDPWrap-v1.6.2\RDPConf.exe

if everything as in the screenshot means it works
if everything is ok - try to sign in as another user
RDPWrap-v1.6.2.zip
rdpwrap.zip

Try this rdpwrap

This worked, thank you!

Try this rdpwrap

This worked. Thanks!
Also, needed to restart "Remote Desktop Services" from services.


[FEATURE] Make HTTP sync frequency configurable

Requirements
Current HTTP flag sync is backed by a cron job and it has hardcoded sync frequency to "every 5th minute"  - */5 * * * *.
It is desired to have configurability on this frequency so that individual flagd users can deploy flagd with desired sync frequencies.
Expected outcome

A new configuration option to override the default for HTTP sync frequency and use it in the cron job
Documentation on the option as well as default value

Hey there. I'm just getting familiar with CNCF and thought this might be a good issue for me.
What granularity are you expecting for the frequency? Just the minutes, or could it be more?
As for the exposing the configurations, will this be through the flags, config file, env variables, or all of them?

Hey
I made a branch with some initial code adjustments, however I do not have permission to push it.
I could not find any links on how an outsider could start contributing.
Is there a way for me to create a PR on this?

I created an initial PR.
Please review it and provide your feedback
Thank you
https://github.com/open-feature/flagd/pull/404


Inlining a fragment query doesn’t compile correctly when the fragment is used

Reproduced on 1.0.0-beta.9.
Say you have two files:
// Test_Frag.re
[%graphql
  {|
fragment ImageFluidFragment on ImageSharpFluid {
  srcSet
  src
  sizes
  aspectRatio
}
|};
  {inline: true}
];

// Test.re
[%graphql
  {|
query Test($path: String!) {
  markdownRemark(fields: {fullPath: {eq: $path}}) {
    frontmatter {
      thumbnail {
        image {
          sharpImg: childImageSharp {
            mobileImage: fluid(maxWidth: 600) {
              ...Test_Frag
            }
            desktopImage: fluid(maxWidth: 1200) {
              ...Test_Frag
            }
          }
        }
      }
    }
  }
}
|}
];

When the PPX compiles this, the JS output still has Test_Frag in the query, not the actual name of the fragment (ImageFluidFragment).
It seems that {inline: true} makes the PPX believe that the fragment’s name is the same as its module name.
{inline: true} can be handy to work around #147 in Gatsby.
Expected behavior: The PPX should either compile Test_Frag (the module name) to ImageFluidFragment (the fragment name), or it should accept ImageFluidFragment in the query and recognize which Reason module it’s coming from.

Strange! I did some testing and I don't see this. Can you try to reproduce this in a test query? It should call Test_Frag.name as the fragment name, and Test_Frag.query as the query that is included.

I set up an example repo.
Fragment A, not inline, works: https://github.com/johnridesabike/gql-ppx-test/blob/master/src/Query_Frag_A.re
Fragment B, inline, doesn’t work: https://github.com/johnridesabike/gql-ppx-test/blob/master/src/Query_Frag_B.re
Query using the fragments: https://github.com/johnridesabike/gql-ppx-test/blob/master/src/Query.re
And the JS output: https://github.com/johnridesabike/gql-ppx-test/blob/master/src/Query.bs.js
The output uses the Reason module name where the fragment name should be in fragment B.

Looks like you're using template tags. Possibly related? https://github.com/reasonml-community/graphql-ppx/issues/160

Noted, will fix!

Should be resolved now!


Function at line #124 has to have an if construct based on System OS used.

Function at line #124 has to have an if construct based on System OS used.   Also, 151 needs to have something like that added in the case statement.
Example:
if [[ "$OSTYPE" == darwin* ]]; then
  # code for MacOs
else
  if [[ "$OSTYPE" == linux-gnu ]]; then
    # code for Debian
  fi
fi

I added a second function called lcheck2 for the Ubuntu OS.

Fixed the the logic by adding the if constructs to the case statement.
# Create the case switch based on the command line arguments
case $1 in
    -s)
        if [[ "$OSTYPE" == linux-gnu ]]; then
           scan_system2
        elif [[ "$OSTYPE" == darwin* ]]; then
           scan_system
        else
           echo -e "$COL_RED "Unsupported OS: $os" $COL_RESET"
        fi
        ;;
     -h)
        if [[ "$OSTYPE" == linux-gnu ]]; then
           scan_homedir2
        elif [[ "$OSTYPE" == darwin* ]]; then
           scan_homedir
        else
           echo -e "$COL_RED "Unsupported OS: $os" $COL_RESET"
        fi
        ;;
      *)
           echo -e "$COL_YELLOW Usage: $0 -h for homedir clamscan or $0 -s for full system clamscan $COL_RESET"
        ;;
esac

This has not been resolved and working.


Instantiate Devices Plugin in CNS

This PR enables device plugin in CNS for swiftv2 clusters
Reason for Change:

Issue Fixed:

Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] relevant PR labels added

Notes:

Moved this to another PR


[2.4] Hotfix/#700 write of excel dn not working properly release

#700

Please, before merging wait for https://github.com/Avaiga/taipy-core/pull/709 to be approved to propagate changes.


Build runtime bundle if manifest is a runtime or extension

Currently, the flatpak-builder action always assumes the flatpak being built is an application, regardless of whether it is actually a runtime or extension.
Since all runtimes and extensions have a corresponding build-runtime:/build-extension: property in the manifest, this PR adds the needed --runtime flag to flatpak build-bundle if either of those are set.

Would need a rebase

Sorry but another rebase is needed

Rebased and ready to go.

Thank you


import mne error

Hi
I've been working using mne for past few months and am having an issue importing mne and the co libraries from yesterday.
I am not sure if it's mne issue or a common one
Please help me out here

What version of Python are you running?

It's weird that the problem would just have started because that code is a couple of years old (and mostly unchanged) I think. Did you upgrade packages or Python interpreter around the time things stopped working?

Anaconda 2.4.0
I have not done any changes recently.
I tried upgrading and re installing MNE but still no luck

are you able to import other libraries? import numpy or import scipy -- do they work?

I suspect your config file is corrupted.
Try removing it.
It's in $HOME/.mne/mne-python.json

@jasmainak  yes I am able to install other libraries
@agramfort  I removed json file and now am getting this error

I'll reinstall python and check

remove everything and run again a "pip install mne"

Already tried
no luck

Do you install with pip?

On 24 déc. 2015, at 17:09, ahibahi<EMAIL_ADDRESS>wrote:
Already tried
no luck
—
Reply to this email directly or view it on GitHub.

Yes
I reinstalled python too
still getting the same error

in ipython do:
import mne
mne
it will point you where mne is installed. Remove the folder and reinstall.
if it breaks make sure you did not name a file with a name similar to an
mne file.
HTH

Closing due to inactivity, @ahibahi feel free to reopen if you are still having trouble or have new insights

@ahibahi did you ever resolve this?  i have the exact same error and i've been stuck on it for weeks!

@Eric89GXL @agramfort.  I'm also getting this error.  I followed @agramfort's advice removing the config file: $HOME/.mne/mne-python.json.  The package loaded successfully, but seems to depend on that file.  Any ideas for how to regenerate it or replace it?

We could try to be more careful when reading the file, and warn if it's corrupted here:
https://github.com/mne-tools/mne-python/blob/master/mne/utils.py#L1258

+1 for being more careful and avoid a crash
On Wed, Jun 15, 2016 at 9:38 PM +0200, "Eric Larson"<EMAIL_ADDRESS>wrote:
We could try to be more careful when reading the file, and warn if it's corrupted here:
https://github.com/mne-tools/mne-python/blob/master/mne/utils.py#L1258
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

is the $HOME/.mne/mne-python.json file supposed to be generated on install? I uninstalled mne and reinstalled but I don't see the config file

It should only be generated when saving a config value to disk, I think.


Fix [GithubRelease] not found case with include_prereleases

With a couple minor stylistic changes for readability.
Closes #4303

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @paulmelnikow!

  Generated by :no_entry_sign: dangerJS against d57b49ebc27367585bb1344bbfe8164f39c6b576


Use builder pattern for TagDispatcher

Currently the code to create a new TagDispatcher might look like this
dispatcher = TagDispatcher.get(this, tagArbiter, true, true, false, true, false, true);

Which is confusing. Maybe the builder pattern could improve the api here.

@slomo Totally.

:+1:


[nrf toup] introduction of ZephyrExtension package

The ZephyrExtension package allow downstream users to extend the current
Zephyr package.
A ZephyrExtension package allows for setting of additional DTS_ROOT,
BOARD_ROOT, and similar variables without having to patch Zephyr repo.
The repository or folder containing the ZephyrExtension package must be
on toplevel in the Zephyr workspace.
Signed-off-by: Torsten Rasmussen<EMAIL_ADDRESS>

Some checks failed. Please fix and resubmit.
Gitlint issues
1: UC3 Title does not follow [subsystem]: [subject] (and should not start with literal subsys:): "[nrf toup] introduction of ZephyrExtension package"
Tip: The bot edits this comment instead of posting a new one, so you can check the comment's history to see earlier messages.

Yes please!

Interesting idea! I think it should be submitted upstream first personally. A user-facing feature like this would be good to get wider feedback from the community on in my opinion.

Agree, but I prefer a couple of days downstream, just to be confident that current placement in boilerplate is most optimal.

Upstream PR: https://github.com/zephyrproject-rtos/zephyr/pull/25399

@mbolivar-nordic should we get this in, so that I can update manifest in https://github.com/NordicPlayground/fw-nrfconnect-nrf/pull/2232 , and get all samples, tests, etc. using new Zephyr package.

@mbolivar-nordic I simply removed the docs.
As this is a Zephyr feature that NCS is using, and it cannot be used by NCS downstream users, there is no need to have the docs inside NCS regarding this feature.
In future, we could consider providing a similar feature to NCS downstream users.

Included in #305


Use .from instead of constructors

Description
Switching all uses of UInt32/UInt64/Int64 constructors with .from instead.

I agree with the usage of from outside the UInt64 class, but not in internal functions like add. UInt64.from does additional checks which duplicate stuff that operations like add do anyway, and I don't see the value of using the type-safer version internal to the class itself


ImagePullSecrets not correct when creating a new environment

What did you do?
Created an environment in project which project has a default image registry
What did you expect to see?
Shoud exists secrets in the environment related namespace, exactily there is nothing

Any further updates? @pepesi


Fix python strict type checking in Python 3.9+ (#628)

Python 3.9+ started doing strict enforcement of types.  This results in the GUI function methods not functioning properly in modern Python environments.
Fixes #628
Thanks to @icceland in bug 628 for the fix stated in the bug, credit goes to them, they asked in that bug if someone else can put the merge in and give them credit.

Duplicate of #642.

Fixed in https://github.com/micahflee/torbrowser-launcher/commit/8c69da13a7230695a0cb406e9638b301529d2ff4


Bug: Small issues with math block

Impossible to move your cursor before the math block if it is the first block of a document
When you blur the draft window and re-focus it while a math block is active, it will remain active but the text field has gone away.
Cursor is trapped in math block once it is active (up and down arrows should allow you to go to the previous or next text block)

Fixed issues 2 and 3 in commit #2368bdb. I don't understand what the first one means. I believe all block-type nodes in the app don't allow moving cursor before them, but it is possible to select them?

Yes it is a problem with all block nodes! I should be able to put cursor before them by selecting and pressing the left or up arrow key. Then when I start typing it should create a new text block above them

Fixed issue 1 in commit #ec8bf2e


https://developer.mozilla.org/zh-CN/docs/Web/JavaScript/Reference/Global_Objects/parseInt

Request type

[ ] Please close this issue, I accidentally submitted it without adding any details
[ ] New documentation
[x] Correction or update

Details

In Examples

In the vicinity of the 'The following examples all return 4:' sentence, you should add 'If the number greater than 1e+21 (includes) or less than 1e-7 (includes), it will return only one number.(When radix is 10)'

eg:
parseInt(0.0000001,10); // 1
parseInt(0.000000123,10); // 1
parseInt(1e-7,10); // 1
parseInt(1000000000000000000000,10); // 1
parseInt(123000000000000000000000,10); // 1
parseInt(1e+21,10); // 1

I've added this to https://wiki.developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/parseInt. For the zh-CN version, we will need someone from that language community to chime in. Thanks for reporting!


Fixed typo (Auzre)

@hubalazs : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


fix: use enum to show different modes

closes #109
@osdiab can you please priority review and merge this PR, it looks like when the project was migrated to Typescript the split panel widget now fails to open. I've disabled the Split panel on the Ffungi live site for now, until this fix is in.

Thanks for the catch!


UML-1192 Allow for 204 responses from Sirius

Purpose
The new Access code letter request endpoint returns  a 204 with no body content. When using the requests library an exception is thrown when calling .json() on a response that has the 204 code - even though the response was valid the library considers it to be in error. This PR catches the 204 case and solves the issue.
Checklist

[x] I have performed a self-review of my own code
[ ] ~I have added relevant logging with appropriate levels to my code~
[ ] ~I have updated documentation where relevant~
[ ] I have added tests to prove my work
[ ] The product team have tested these changes

Try to kick CI with a new branch

Try to kick CI with a new branch


Inference server stalling

System Info

tensorrtllm_backend built using Dockerfile.trt_llm_backend
main branch tesnorrt llm (0.13.0.dev20240813000)
8xH100 SXM
Driver Version: 535.129.03
CUDA Version: 12.5

After roughly 30 seconds of inference requests, the inference server stalls, not responding to any requests. There are no error codes or crashes visible in logs. The server is using decoupled mode with dynamic_batching.

No response
Information

[X] The official example scripts
[ ] My own modified scripts

Tasks

[ ] An officially supported task in the examples folder (such as GLUE/SQuAD, ...)
[ ] My own task or dataset (give details below)

Reproduction

Build the inference server docker image
Build the llama 70b engine
Start the server serving the engine
Send high requests per second with 2k context length

Expected behavior
Inference server doesn't stall
actual behavior
Inference server stalls
additional notes
Initial requests complete successfully, so not sure why it stalls afterwards

How are you serving the request? Are you launching using the official launch_triton_server.py file?

I am experiencing this too @dhruvmullick. It started with the 0.13 dev version, all 0.12 versions work just fine.

Are there any updates on this? Still experiencing this on the latest TRT LLM and backend versions
@dhruvmullick  I'm launching using the tritonserver CLI and using .stream_infer() from the grpc client library to send requests: https://github.com/triton-inference-server/client/blob/cb9ba08b3f88dff802485f0577b008cdbf41c529/src/python/library/tritonclient/grpc/aio/init.py#L688

These might also be the same issue: https://github.com/triton-inference-server/tensorrtllm_backend/issues/574 https://github.com/triton-inference-server/tensorrtllm_backend/issues/596

This now seems to be fixed as of the November 5th update to the main branch.


NBTPath Item.tag is not recognized as a Compound tag.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: add implementation for wasi sock functions

@cjihrig, @ospencer PR to add the sockets implementation to the main line.

@cjihrig that's it with merge conflicts resolved. Mostly because of me fixing the windows tests in both:)


echo text command

fixed for real now

not part of main bot functions, will make a branch for experimental features


Module is conflicting with nuxt/devtools

Environment

Operating System: Darwin
Node Version:     v18.15.0
Nuxt Version:     3.4.3
Nitro Version:    2.4.0
Package Manager<EMAIL_ADDRESS>Builder:          vite
User Config:      -
Runtime Modules:  -
Build Modules:    -

Reproduction
https://github.com/jpsc/beta.11.bug
Describe the bug
I'm adding @nuxt/devtools inside of a module with kit's installModule and it doesn't seem to work properly.
If I add the via the nuxt.config on the playground it works, but inside of the module not really.
I'm adding this here because if I remove nuxt/i18n module it works.
Additional context
One of the errors is:

Cannot read properties of undefined (reading 'Symbol(vue-i18n-routing-gor)')

Logs
No response

Some more additional context:
When adding @nuxt/devtools via installModule
addImports is called here:
https://github.com/nuxt-modules/i18n/blob/next/src/module.ts#L354
But the hook imports:extend is not called:
https://github.com/nuxt/nuxt/blob/main/packages/kit/src/imports.ts#L9


Current Drive View dashboard : Power unit does not seem right

https://github.com/jheredianet/Teslamate-CustomGrafanaDashboards/blob/949028cf24fd78d3e058665494570393ede8f721/dashboards/CurrentDriveView.json#L298
I haven't been able to confirm or to find any clear documentation regarding this, but I think that the power column in the positions table is given out in kilowatts (at least this looks like the right value when converting max(power) from kW to hp for my car).
The SQL query should be changed to use a multiplication constant of 1000, or change the panel unit to kilowatts.
Cheers for the very nice dashboards !

Hi @MaxyMoos, you are right. Good catch! Thanks for suggestion. I've changed the power unit to kW, then took the opportunity to add  a rated efficiency dotted line and change battery capacity calculation.
May I kindly ask you to check it out and test "Current Drive View v1.1" dashboard?
Looking forward to know how it goes now in order to close the issue.

Hey that's great, thanks for the update, that looks much better 👍
I got rid of the -30 / +30 kW fixed axis range in order to get an adaptative y-range for my drives though !

Hi @MaxyMoos I'm glad to hear that. About the -30/+30 (min/max value), I did it on purpose in order to have the elevation axis stacked on 0 to have a better view. I didn't find other way to do it. I got rid of it as well and realized that with the min value of the elevation axis on 0 was enough.


Fix case in Gitlab description

Fix the case in GItlab.

Hi @gusfcarvalho, I opened the PR without a description so the bot closed it. I added some text to the description now. Will it get re-opened eventually or it requires someone manually re-opening it?

Hi @gservat ! Thank you for your contribution! In order to fix the CRDs definitions, we need to change them in the golang code, as we use kubebuilder to generate the CRDs. This specific comment is here. After you change it, you need to make generate to generate the new CRDs. Then, I think the CI tests are going to pass.

/approve

/merge


Updated to fix linux SSH key invalid error

Added \ character at end of password input.

Updated to include full SSH key inside argument rather than the path to the SSH key.

Square brackets have been added for these things (optional arguments)

openshiftMasterPublicIpDnsLabel=myopenshiftmaster
infraLbPublicIpDnsLabel=myopenshiftlb
As they weren't required in our case.

Hi @rbhadti94 . Sorry you ran in to issues. We just expanded the OpenShift docs today, which are now published live. The steps noted here have been updated and replaced. If you still have issues with those new versions, please let us know.
#please-close

Hi @iainfoulds,
Thanks for taking this on-board. The changes in this PR should eliminate 1 or 2 of the errors that occur.
Ravi


Scale getPixelForValue does not return value for non-labels

Hello,
The implementation of getPixelForValue in the scales causes an issue with the annotation plugin. When you use a vertical annotation and enter a decimal value (for instance 4,5) and as x-labels have [1,2,3,4,5] the getPixelForValue returns x-pixel value for the first item, due to this code:
var labels = me.getLabels();
value = valueCategory || value;
var idx = labels.indexOf(value);
index = idx !== -1 ? idx : index;

I would expect that this function returns the x-pixel value regardless of whether or not this value is part of the array of labels.
Environment

Chart.js version: 2.7.2
Annotation plugin: 0.5.7

I guess you are using a category scale (based on your snippet), in which case it can't work (no way to interpolate values, e.g. you could have the following labels: [1, 2, 1, 3, 2, 4]).
Can you share a jsfiddle that reproduces that case ?

I've taken a look at it and yes I am using a category scale. I'm trying to make a histogram using a vertical bar chart and then use a range of numbers as labels and the values as the amounts in each bin.
After your comment tried to use a linear scale with a bar chart but that did not display anything. Is that even possible?
Anyways I looked through the examples and thought I can also misuse the steppedLine functionality to create a histogram based on a Line chart with a linear scale. So that also fixes my problem. Only downside is that I cannot place any spacing between my bars as was possible with the vertical bar chart implementation.
Thanks anyways!


missing semicolon in codemirror js ver 5.5.0

Hi,
in https://github.com/codemirror/codemirror5/blob/53faa33ac69598b7495e160824b58ebb8d70fe97/src/util/misc.js#L124 is written var nonASCIISingleCaseWordChar = [...]ud7af]/ without a trailing semicolon and followed by a function.
In a minified version ist becomes  ... ]/function ... wich ends in an error.
Best

In a minified version ist becomes  ... ]/function ... wich ends in an error.

Only if the minifier is broken. If the file we distribute runs, I don't consider this an issue in CodeMirror.


Crashes on to much scrolling

Hello there,
I have used this perfect refresh control on my app by adding it to my UICollectionView. But, when the content is too much, and I scroll to bottom, after a while (approximately at row 200) the app crashes and dumps this error text:
2017-05-08 17:27:01.233538+0300 Bandabulya[955:276965] validateTextureDimensions, line 717: error 'MTLTextureDescriptor has height (16385) greater than the maximum allowed size of 16384.'
validateTextureDimensions:717: failed assertion `MTLTextureDescriptor has height (16385) greater than the maximum allowed size of 16384.'

When I remove RainyRefreshControl from my app, the app is working as expected without any crash.

@ilkerdagli Thanx, I will check and get back to you soon

Hello there,
The issue has been fixed when I updated to swift 3.1  :)

Same issue..
failed assertion `MTLTextureDescriptor has height (8315) greater than the maximum allowed size of 8192.'


Coordinate with tool/language owners to add our annotations to their configured lists

For example:
https://github.com/lampepfl/dotty/blob/main/compiler/src/dotty/tools/dotc/core/Definitions.scala#L1041
We should probably make a checklist, since when someone hears about us and then their tool doesn't know anything then we look less real.

Kotlin


chore(build): Replace buildSrc by gradle's versionCatalogs

Removed the custom buildSrc in favor of gradle's versionCatalogs.
I also removed sksamuel as he is not a maintainer of this avro4k library.

Just a side note, I would prefer that you approve instead of merging yourself my PR 😄 I usually read again what I've did before merging to be sure that I missed nothing !


feature: User installable services for use by other Plugins

While thinking about the way to add a common persistence mechanism for use by other plugins, it occurred to me it may be useful to have that service, as well as many other types, be ones that can be installed via the App store plugin mechanism just like other plugins.  Posting this idea here for feedback before working on a PR.  The general idea would be:

The server plugin API would have an additional method added to it so general purpose plugins could use it.  It would be getService(serviceName) or similar.  That would return an object configured and immediately usable by the plugin that requested it.  So, for example, a plugin calling getService('mongo') would receive an API for the Mongo DB database.  If no such service is available, null would be returned.

Plugins installed by the end user would optionally define two additional methods:

getServiceName() if defined by the plugin, would indicate the plugin can provide a service API for other plugins.

getService(plugin, app) would be a service factory method that would create a service instance for use by the specified plugin.  An optional approach to returning a service interface object would be for getService() to simply decorate the app object (which is assumed to be the current API instance created for use by the specified plugin) with additional methods (similar to a polyfill).  This second technique would allow for expanding the plugin API via the plugin mechanism vs. app server updates.

By having these services be pluggable, it would allow for different systems with different capabilities to take advantage of the best software stack combination.  For example, there could be different plugins that might be capable of creating a 'mongo' service.  Those would include:

One that uses the NeDB project
One that uses the TingoDB project
One that returns an interface to an actual MongoDB service running on an external machine, possibly even one that is cloud based.

We could use this mechanism to come up with common interfaces, like a 'sql' service that is backed by MySQL, Postgres, sqlite, or any other db that the end user chooses.

I think we are already headed towards a version management nightmare with plugins and without a very carefully thought and implemented version compatibility mechanism this would make things even more complex. What if plugin A needs version 3 of something provided by plugin C and B needs version 2?
One of the unappreciated strengths of JavaScript is that different versions of a dependency can peacefully coexist - I think it is much easier for a plugin to bring its own dependencies, with internal versioning.
When I talked about extending the api provided to plugins with a way to store relational data I was thinking about just that: providing one standard server-sanctioned storage model for more than trivial amounts of data. But it may very well be that even that is not needed. Also I don't fancy bringing one more persistence abstraction to this world - there's plenty around, none of them perfect.
Before adding this much complexity I think we need a lot more evidence as to this being a problem worth solving in this way.
Also anything more serious, like Postgres, Timescale, MySQL, InfluxDb, MongoDB  etc can not be easily provisioned by the server - unlike sqlite they are separate OS level applications. If this is what we need in the future I would rather explore Docker & Docker compose for provisioning the server and related services and let plugins talk to their backends directly, not through the server or via other plugins.

One of the unappreciated strengths of JavaScript is that different versions of a dependency can peacefully coexist - I think it is much easier for a plugin to bring its own dependencies, with internal versioning.

True, but it can also be one of its weaknesses.  What if Plugin A, B, C, and D all need the same version of the same module, and that module happens to have some heft to it (as might be the case with a sophisticated persistence engine).  Now, you've got the same code being included four times.
My thought with this was that NeDB, and TingoDB both emulate the Mongo interface exactly.  So, we wouldn't really be creating another abstraction layer (at least, not in the case).  However, NeDB is an "in memory only".  That may be fine for some installations, but for ones that make heavy use of plugins that make heavy use of the persistence, we could swap out NeDB for one of the others.
That being said, I can't argue strongly enough for this approach right now, and it may very well be over-engineering the problem.  A single common persistence engine may in fact solve the problem of duplicated large modules, and I don't know if there is any other use case right now for this proposed solution.
One thought, however: there is some merit to supporting a mechanism where a plugin can polyfill API methods into the app object passed to other plugins.  This might actually be a good way to deal with versioning problems.  If this mechanism were to be added as an undocumented feature in 1.19, and then at some point in the future, Node Server 2.0 comes out, and  new plugin is created that needs some of the new API call, this mechanism would allow for a "compatibility plugin" to be added to a 1.19 system that polyfills the necessary methods to get 2.0 to work.  Either that, or this imagined plugin could be released with a polyfill plugin without having to wait on the 2.0 release.
Anyway - its worth filing away as a possible solution to future compatibility problems.