Solving constraints does not work in a dynamic application

I have tried your library, but it just does not work. This is my code:
//
//  AFRheaTestView.m
//  FlexSchematics
//
//  Created by Phillip Schuster on 18.11.15.
//  Copyright © 2015 Appfruits. All rights reserved.
//

#import "AFRheaTestView.h"

#include "rhea/simplex_solver.hpp"
#include "rhea/iostream.hpp"
#include "rhea/variable.hpp"

@interface AFRheaTestView ()
@property (nonatomic, strong) NSTrackingArea* trackingArea;
@property (nonatomic, assign) BOOL dragged;
@property (nonatomic, assign) rhea::variable l1X;
@property (nonatomic, assign) rhea::variable l1Y;
@property (nonatomic, assign) rhea::variable r1X;
@property (nonatomic, assign) rhea::variable r1Y;
@property (nonatomic, assign) rhea::simplex_solver solver;

@end

@implementation AFRheaTestView

- (void)drawRect:(NSRect)dirtyRect {
    [super drawRect:dirtyRect];

    // Drawing code here.
	[[NSColor magentaColor] setStroke];
	NSBezierPath* bezierPath = [NSBezierPath bezierPath];
	[bezierPath moveToPoint:NSMakePoint(self.l1X.value(), self.l1Y.value())];
	[bezierPath lineToPoint:NSMakePoint(self.r1X.value(), self.r1Y.value())];
	[bezierPath stroke];
}

-(void)awakeFromNib
{
//	self.l1X.set_value(100);
//	self.l1Y.set_value(100);

	self.solver.set_autosolve(false);

	self.solver.on_resolve = [self](rhea::simplex_solver &solver) {
		std::cout << "on_resolve" << std::endl;
	};

	self.solver.on_variable_change = [self](const rhea::variable& v, rhea::simplex_solver& s) {
		std::cout << "on_variable_change " << v.value() << std::endl;
	};

	self.solver.add_stay(_l1X);
	self.solver.add_stay(_l1Y);

	self.solver.set_explaining(true);

	self.solver.add_constraint(_r1X == _l1X + 100);
	self.solver.add_constraint(_r1Y == _l1Y + 100);
	self.solver.solve();

	NSTrackingAreaOptions options = (NSTrackingActiveAlways | NSTrackingInVisibleRect |
									 NSTrackingMouseEnteredAndExited | NSTrackingMouseMoved);
	self.trackingArea = [[NSTrackingArea alloc] initWithRect:self.bounds options:options owner:self userInfo:nil];
	[self addTrackingArea:self.trackingArea];
}

-(void)updateTrackingAreas
{
	[self removeTrackingArea:self.trackingArea];
	NSTrackingAreaOptions options = (NSTrackingActiveAlways | NSTrackingInVisibleRect |
									 NSTrackingMouseEnteredAndExited | NSTrackingMouseMoved);
	self.trackingArea = [[NSTrackingArea alloc] initWithRect:self.bounds options:options owner:self userInfo:nil];
	[self addTrackingArea:self.trackingArea];
}

-(void)mouseMoved:(NSEvent *)theEvent
{
	CGPoint curPoint = [self convertPoint:[theEvent locationInWindow] fromView:nil];

	self.solver.suggest(_l1X, curPoint.x);
	self.solver.suggest(_l1Y, curPoint.y);
	self.solver.solve();

	[self setNeedsDisplay:YES];
}

@end

I have attached a screenshot that shows what is the result. As you can see, it seems to work for the first time (l1X and l1Y is 0 at the beginning which is the lower left corner in Mac OS X), but r1X and r1Y never change when moving the mouse.
What's wrong with my code?

I've been having troubles with stay's myself - so I try to avoid them. I would rather have some constraints added and removed.

Thank you for your answer. I tried implementing it with constraints, the same result. But, I have found the error. I changed solver to be a pointer (heap instead of stack) and this works:
//
//  AFRheaTestView.m
//  FlexSchematics
//
//  Created by Phillip Schuster on 18.11.15.
//  Copyright © 2015 Appfruits. All rights reserved.
//

#import "AFRheaTestView.h"

#include "rhea/simplex_solver.hpp"
#include "rhea/iostream.hpp"
#include "rhea/variable.hpp"

@interface AFRheaTestView ()
@property (nonatomic, strong) NSTrackingArea* trackingArea;
@property (nonatomic, assign) BOOL dragged;
@property (nonatomic, assign) rhea::variable l1X;
@property (nonatomic, assign) rhea::variable l1Y;
@property (nonatomic, assign) rhea::variable r1X;
@property (nonatomic, assign) rhea::variable r1Y;
@property (nonatomic, assign) rhea::simplex_solver* solver;   // <!----- This is the relevant change!
@property (nonatomic, assign) rhea::constraint l1XC;
@property (nonatomic, assign) rhea::constraint l1YC;

@end

@implementation AFRheaTestView

- (void)drawRect:(NSRect)dirtyRect {
    [super drawRect:dirtyRect];

    // Drawing code here.
	[[NSColor magentaColor] setStroke];
	NSBezierPath* bezierPath = [NSBezierPath bezierPath];
	[bezierPath moveToPoint:NSMakePoint(self.l1X.value(), self.l1Y.value())];
	[bezierPath lineToPoint:NSMakePoint(self.r1X.value(), self.r1Y.value())];
	[bezierPath stroke];
}

-(void)awakeFromNib
{
//	self.l1X.set_value(100);
//	self.l1Y.set_value(100);

	self.solver = new rhea::simplex_solver();    // <!---- And this of course ;-)

	self.solver->set_autosolve(false);

	self.solver->on_resolve = [self](rhea::simplex_solver &solver) {
		std::cout << "on_resolve" << std::endl;
	};

	self.solver->on_variable_change = [self](const rhea::variable& v, rhea::simplex_solver& s) {
		std::cout << "on_variable_change " << v.value() << std::endl;
	};

	self.solver->add_stay(_l1X);
	self.solver->add_stay(_l1Y);

	self.solver->add_constraint(_r1X == _l1X + 100);
	self.solver->add_constraint(_r1Y == _l1Y + 100);
	self.solver->solve();

	NSTrackingAreaOptions options = (NSTrackingActiveAlways | NSTrackingInVisibleRect |
									 NSTrackingMouseEnteredAndExited | NSTrackingMouseMoved);
	self.trackingArea = [[NSTrackingArea alloc] initWithRect:self.bounds options:options owner:self userInfo:nil];
	[self addTrackingArea:self.trackingArea];
}

-(void)updateTrackingAreas
{
	[self removeTrackingArea:self.trackingArea];
	NSTrackingAreaOptions options = (NSTrackingActiveAlways | NSTrackingInVisibleRect |
									 NSTrackingMouseEnteredAndExited | NSTrackingMouseMoved);
	self.trackingArea = [[NSTrackingArea alloc] initWithRect:self.bounds options:options owner:self userInfo:nil];
	[self addTrackingArea:self.trackingArea];
}

-(void)mouseMoved:(NSEvent *)theEvent
{
	CGPoint curPoint = [self convertPoint:[theEvent locationInWindow] fromView:nil];

	self.solver->suggest(_l1X,curPoint.x);
	self.solver->suggest(_l1Y,curPoint.y);

	self.solver->solve();

	[self setNeedsDisplay:YES];
}

@end

Anyone has an explanation for that? As you can see I am using rhea in Objective-C++...

Using properties means calling methods which returns a new solver unless you use the pointer. So, that wasn't working for me as well. I have an obj-c facade around the solver for various reasons. The way I access the solver is by using the ivar directly.
@implementation ALEConstraintSolver {
    rhea::simplex_solver _solver;
}

Glad to hear you got it working btw. It is not trivial to use rhea from obj-c with wrt pointers and friends.

I have no Obj-C(++) experience myself, so if you guys have any suggestions how to make it easier to use I'd love to hear it.

Maybe a "best practices for rhea in obj-c" guide would be sufficient. What makes it hard is that the memory system is different from what we are used to. Some notes about how to pass around objects like simplex_solver, constraint_list, and variables would be to great help.

And by "memory system" you mean the way C++ handles memory in general? Or is there anything in Rhea in particular that could trip up Obj-C++ users? (Simplex_solver is quite normal, but constraints and variables are reference counted under the hood, perhaps that could lead to surprises.)
In any case, some guidelines or even just a small bit of example code would be nice to have in the documentation.

I can give a few guidelines. Adding rhea to an Objective-C Xcode project generates compiler/linker errors. There are a few things that should be done in order to get it compiled. I added the rhea files directly to my project with "Add files to project".
Then you have to change the Build Settings by clicking on the Project file in the Project Explorer (left side of Xcode). I changed the settings both in the Project Settings, as well at the Target to these settings from "GNU..." to these:

After that, you will have to rename all .m files to .mm. As you have to integrate C++ into Objective-C you will need to mark the files as Objective-C++ files. This is done by renaming them to .mm files. I did that for every file in the project and for every file that is later added. The only file I kept is main.m, as renaming that to .mm gave me strange errors. Getting strange compiler errors always makes me check that I really named all files with .mm, and most of the time I find a new class I added with .m name. Due the caching of Build Objects these errors sometimes come suddenly without context. As said before, check for .m files.
Another very important aspect is, that the solver must be a pointer and initialized via a "new rhea::simplex_solver". Of course a "delete ..." should remove this instance later down the road, i.e. in -dealloc for example.
Adding a property to a class:
@interface XYZ
@property (nonatomic, assign) rhea::simplex_solver* solver;
@end

After that you will have to initialize it (i.e. in the init method):
-(instancetype)init
{
    self = [super init];
    if (self)
    {
        self.solver = new rhea::simplex_solver();
    }
    return self;
}

I switched all my variables to pointers and initialized with the new operator. I did that for variables, too. And it's working fine for now:
    self.centerPositionX = new rhea::variable(_centerPosition.x);
    self.centerPositionY = new rhea::variable(_centerPosition.y);

If you need to set a constraint I did it this way:
    _xConstraint = new rhea::constraint(*self.centerPositionX == _centerPosition.x);
    _yConstraint = new rhea::constraint(*self.centerPositionY == _centerPosition.y);

As your C++ code does use references and not pointers you will need to dereference the pointer with the indirection operator *pointer (more on that: https://www3.ntu.edu.sg/home/ehchua/programming/cpp/cp4_PointerReference.html). This is working fine for me, but I am not sure if this triggers a copy of the variable, which might be a problem later down the road or with other constructs of rhea I did not use so far.
Any clarification on that would be nice.

Is that idiomatic Obj-C++ though? You always have to do this if want to use any C++ object as a member?
Variables and constraints are reference counted, so a copy would still act like the original. The simplex_solver is a plain old, ordinary class.


SMT-LIB solver integration

This pull request adds a new solver implementation next to the already existing Z3 solver. This new implementation uses the SMT-LIB standard to communicate with the SMT solvers, so the underlying solver becomes changeable as long as it supports SMT-LIB.
This is an alpha feature, with known shortcomings. These shortcomings will need to be addressed in the future (see #71).
The main features of this pull request:

SMT-LIB solver integration

Support for booleans, integers, rationals, arrays, bitvectors, floating-points, quantifiers and unary uninterpreted functions
Support for unsat cores
Interpolation support (where applicable)

Binary, sequence, tree interpolation

CLI tool of solver installer scripts for easy solver management, with support for

Boolector
CVC4
MathSAT
Princess
SMTInterpol
Yices2
Z3

Integration with the CFA-CLI tool

Allows specifying different solvers for abstraction and refinement phase

@hajduakos What is your take on the testing part of the TODO list?

First of all, this is a really impressive job!
I will think a bit about the tests. Maybe we can also ask some advice from @micskeiz . However, why are there 1000+ commits? Some of them seem irrelevant to this branch (they are already part of master)? What happened here?

Yes, unfortunately the commit history is a bit tainted. The main reason / problem is the changes introduced in #101, I think. After merging the master branch, git failed to do a merge, even after resolving the conflicts. After resolving the conflicts, git merge failed, and left staged changes on files that were deleted on both the master and on this branch. These files were files that I deleted and the master moved somewhere.

Cool! Maybe @kris7t or @szdan97 can help cleaning up commits as well.

The final version introduces changes in the overall project structure and also changes in the core API related to solvers.
The project structure changes by moving solver related subprojects from common to solver. Moreover it introduces a new solver solver-smtlib that is based on SMT-LIB, and a new CLI tool to manage it.
The changes in API are the refactoring of Solver and ItpSolver interfaces. Right now, Solver only contains methods for simple satisfiability checks, UCSolver for unsatisfiable core enabled solvers and ItpSolver for interpolation based solvers.

@hajduakos This version introduces major changes in alpha version. Which would you prefer: to bump only the minor version (2.24.0) or the major as well (3.0.0).

Close in favor of #143 , which clears the commit history of this PR.


Body Report - Retrograde body motion

Hi,
While out exploring, I've found that the Body Report can be incorrect for bodies that have retrograde motion (reverse spin).  For example if a body has a spin of -45 days, the current body report states this as a fast rotational period, when in fact it is a slow rotational period, it's just in reverse.  The section of code that handles this can be fixed with the following :-
    {if reportbody.landable:
        It has a
        {if reportbody.rotationalperiod < -20.0:
            slow retrograde
        |elif reportbody.rotationalperiod < -0.5:
            retrograde
        |elif reportbody.rotationalperiod < 0:
            fast retrograde
        |elif reportbody.rotationalperiod <= 0.5:
            fast
        |elif reportbody.rotationalperiod > 20.0:
            slow
        }
        rotational period of {Humanise(reportbody.rotationalperiod)}
        day{if Humanise(reportbody.rotationalperiod) != "1":s}.

(The last line also fixes a rotational period of one day being said as "one days").
Hope you find this useful. Keep up the great work Cmdr! :)
Darkcyde.

Thank for for supplying this change.  It has been incorporated in to EDDI 2.3 (currently in beta).


Add hooks

:enqueue
:before
:after
:failure
:complete
:requeue
:release

@mindscratch yeah, sorry, I've had a few too many irons in the fire.  The work on hooks is mostly done in the hooks branch. Give it a try and let me know how it works for you.
The main reason I haven't it merged it into master and released it is that I haven't had a chance to update my project to use it. I want to make sure I like using it before committing to the API.

This is exactly what I need at work. We have a background job connecting to external service that's very finicky.
I'd like to be able to send email to customer service department when job failed and have them handle it manually.
Qu is looking better and better. Thanks for creating it!


Typescript file imports being appended with .js extensions intermittently

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

VS Code Version: 1.74.2
OS Version: macOS Monterey 12.6

Steps to Reproduce:

Commented out all of my settings.json file, so uses the default settings
Restart VSCode with Extensions Disabled
In certain .ts files in my project, when I go to import another .ts file the autocomplete option for the import adds a .js file extension.
The same import made in another .ts file in the same directory or another directory, does not append the .js file extension.
Sometimes in the .ts file(s) that appends the .js file extension on the auto import, when I remove all of the code and then try to import, it does not append the .js extension. But if I close the file and re-open it again, it will. But this is intermittent.
See Videos below for issue

Sorry, had to split in 2 due to file sizes

https://user-images.githubusercontent.com/20436343/210012132-a6682005-5d22-485b-9e1b-cf617f3ffd1f.mov
https://user-images.githubusercontent.com/20436343/210012161-49604216-5ff5-4ee9-b0f8-de3b83458857.mov
Not sure how much the tsconfig.json file can affect this but this is my ts config.
{
  "compilerOptions": {
    "target": "es2017",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "noEmit": true,
    "esModuleInterop": true,
    "module": "esnext",
    "moduleResolution": "node",
    "resolveJsonModule": true,
    "isolatedModules": true,
    "jsx": "preserve",
    "incremental": true,
    "noUncheckedIndexedAccess": true,
    "noUnusedLocals": true /* Report errors on unused locals. */,
    "noUnusedParameters": true /* Report errors on unused parameters. */,
    "allowSyntheticDefaultImports": true /* Allow default imports from modules with no default export. This does not affect code emit, just typechecking. */,
    "noImplicitAny": true,
    "strictNullChecks": true,
    "strictFunctionTypes": true,
    "noImplicitThis": true,
    "noImplicitReturns": true,
    "noFallthroughCasesInSwitch": true
  },
  "include": ["next-env.d.ts", "types/**/*.ts", "next-auth.d.ts", "**/*.ts", "**/*.tsx", "**/*.js", "**/*.cjs", "**/*.mjs"],
  "exclude": ["node_modules"]
}

FWIW, seems that adding
"typescript.preferences.importModuleSpecifierEnding": "minimal"

into my settings.json seems to resolve the issue, but still not sure why it doesn't seem to happen in other projects I have or even other files in this project.


Set dependency between docker containers (#4873)

Pull request opened by the merge tool on behalf of #4873

Merged into branches iso4 in 9bc6d39a24e742363a974701ec82c4127a6a3444


feat: Add the user id (or email) to the profile

Will fix #1833

Codecov Report

Merging #1849 (2180929) into develop (2ea0da3) will decrease coverage by 1.76%.
The diff coverage is 9.84%.

@@            Coverage Diff             @@
##           develop   #1849      +/-   ##
==========================================
- Coverage     8.86%   7.09%   -1.77%
==========================================
  Files          161     174      +13
  Lines         6623    7879    +1256
==========================================
- Hits           587     559      -28
- Misses        6036    7320    +1284

Impacted Files
Coverage Δ

...h_app/lib/cards/category_cards/abstract_cache.dart
0.00% <0.00%> (ø)

...p/lib/cards/category_cards/asset_cache_helper.dart
0.00% <0.00%> (ø)

...p/lib/cards/category_cards/raster_async_asset.dart
0.00% <0.00%> (ø)

...oth_app/lib/cards/category_cards/raster_cache.dart
0.00% <0.00%> (ø)

..._app/lib/cards/category_cards/svg_async_asset.dart
0.00% <0.00%> (ø)

...smooth_app/lib/cards/category_cards/svg_cache.dart
0.00% <0.00%> (ø)

...th_app/lib/cards/data_cards/image_upload_card.dart
0.00% <0.00%> (ø)

...es/smooth_app/lib/cards/data_cards/score_card.dart
4.54% <0.00%> (-0.22%)
:arrow_down:

...t_cards/knowledge_panels/knowledge_panel_card.dart
0.00% <0.00%> (ø)

...knowledge_panels/knowledge_panel_element_card.dart
0.00% <0.00%> (ø)

... and 120 more

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 d957755...2180929. Read the comment docs.

Ideally, this should be visible at top level in settings and in this screen

We should also show it in the subtitle on settings page

Oops you're right @M123-dev
In the issue, please let me know if the design is OK

Don't worry, I will try to implement the design.
I won't take that much time... but as you which

Here is the new design:

Still in favor of merging the profile related heading with the profile tile

Ok would be better indeed.
Just to confirm: is-it OK for you @teolemon to merge the « Welcome » tile and the profile one?

yes, ok

Here is the new implementation:
https://user-images.githubusercontent.com/246838/169779635-9de5ffdd-47cf-4680-9c3a-f722f29e2b3f.mp4
Is-it better?
(The overflow will be fixed)

Looks really good that way, I just noticed it looks like there is no way to opt out of analytics when you aren't logged out (except of the onboarding)

Ok I will move them to the App settings, which seems more accurate

And here is the new layout :)

I've updated the goldens, and the tests are passing on my machine.
I don't really understand why the tests fail. Any guess @M123-dev?

Heyyy, sorry @g123k while fixing merge conflicts I managed to break something. It should be fine now but feel free to have a look not that something has gone wrong

My rebase should have fixed everything

thanks @g123k @M123-dev merging


Update HelperExpression to be able to evaluate nodes without params a…

Update HelperExpression to be able to evaluate nodes without params attribute.
I want to be able to traverse the entire AST and check if each node/param/hash is a helper or not. This currently blows up on literals that don't have params.

Actually, this is not right either as a Helper could be a MustacheStatement or BlockStatement. I did notice that the path object of the statement seems to only exist for helper statements. So I modified it as such:
 return !!((statement.path && (statement.type === 'SubExpression' || statement.params && statement.params.length) || statement.hash));

Seems a little hacky though so there might be a more concise way to handle this.

Please update the PR with what you'd like to see and include test cases. I'm all for bulletproofing the code where it's making unsafe assumptions.

(Comment here when you've updated as otherwise we might not see the changes)

@chrisrink thanks for the initial work here. Just landed a patch the fixes this in master.

Great news! I think this should work. One last thing to check. I have actually been using the below statement.
{code}
return !!((statement.path && statement.path.original) && (statement.type === 'SubExpression' || (statement.params && statement.params.length) || statement.hash));
{code}
And this seems to be working for me. So I just wanted to double check that the statement.path and statement.path.original parts would be caught in Mustache and Block statement calls.


[Event Request] codeunit 5988  "Serv-Documents Mgt." - OnAfterServShptLineFinalizeShipmentInsert

Hello, would it be possible to add OnAfterServShptLineFinalizeShipmentInsert,  event to codeunit 5988  "Serv-Documents Mgt.", like this:
    local procedure FinalizeShipmentDocument()
...
                  repeat
                     PServShptLine.Init();
                     PServShptLine.Copy(ServShptLine);
                     PServShptLine.Insert();
>                     OnAfterServShptLineFinalizeShipmentInsert(PServShptLine);//New Event
                 until ServShptLine.Next() = 0;
             ServShptLine.DeleteAll();
         end;

     [IntegrationEvent(false, false)]
     local procedure OnAfterServShptLineFinalizeShipmentInsert(var PServShptLine: Record "Service Shipment Line")
     begin
     end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 10531.


Delete test_page.html and example.css?

I prepared this page  https://github.com/PASTAplus/web-x/blob/main/templates/test_page.html in order to test the formatting guidelines that Colin had developed in content-x. We transferred the css to site.css and this file along with static/css/example.css might not be needed any longer.

That sounds good. Thank you for reviewing this issue!


Add useful-only-in-out-of-spec-scenarios plugins to the plugin restrictions

The current plugin guidelines don't explicitly disallow plugins that are only useful in out-of-spec (e.g. OOB, etc) scenarios. We should mention this and the reason why they're not allowed - a plugin that only works in service of illegal behaviour tacitly encourages said behaviour, which we can't support or discuss within this community.

We can/should probably include some of the other common cases (or come to formal conclusion on them) that are pinned in discord too, copied with some minor edits for tone below. https://discord.com/channels/581875019861328007/685275026156683280/929071629550645248
Common suggestions that won't happen:

Emote/Expression Looping
This violates our rule on automation. While this seems harmless, it's one of the easiest things for another user to notice, as the game tells you whether an emote is persistent.
Skip cutscenes
This violates our rule on automation. Especially in the case of unskippable cutscenes.
Skip dialog boxes
This violates our rule on automation.
Automated crafting
This violates our rule on automation.
Autoroll on loot
This violates our rule on automation.
Friend list login/out alerts
This is impossible. FFXIV only sends friendslist data when you actively open the friendslist. It cannot be refreshed otherwise. A plugin would have to implement some form of external server to do this (like GoodFriend)
Visible AOE markers for mechanics that aren't normally telegraphed in advance
This is cheating. We don't do that here.
Camera zoom adjustments
This violates our plugin guidelines, can give game-breaking advantages in battle content, and can break cutscenes. Plugins that stay within the game bounds are still allowed.
FFLogs integration
Just use ACT instead. We prefer to keep our distance from this aspect of FFXIV.
Avoiding fantasia
This violates our plugin guidelines. Please do not use a plugin as a means to bypass the MogStation.
More XIV Combos
No. See Attick's other pinned comments and stances about this. Also read https://github.com/attickdoor/XIVComboPlugin/issues/119
Damage parser / ACT as a plugin
Just use ACT (or alternatives) instead. Similar to FFLogs, we'd also like to distance ourselves from this aspect of FFXIV.

It might be worth mentioning versions that are rule compliant, because people will always go "well XYZ does (something similar but not quite). Such as "Select Next Loot Item Tweak", it's not auto loot but it achieves a similar thing.

Might also mention re-coloring aoe's due to the can of worms that opens.

Is this not already covered? The precise wording in the docs is: (emphasis mine)

your plugin does not interact with the game servers in a way that is:

automatic, as in polling data or making requests without direct interaction from the user
outside of specification, as in allowing the player to do or submit things to the server that would not be possible by normal means

Unless there's something more direct that you're thinking of? e.g. a plugin that would be allowed if it weren't useful only in circumstances that were out of spec?

The plugin submission that prompted this did not strictly break anything but was only useful if the player had already done something to reach that point. This is to improve those cases, as modification to the local client won't result in -more- invalid data, but we can't endorse the steps/tools needed to get to that point.
We also have several instances of plugins that don't directly go against guildeines, but would still be rejected. (Parsing, Modding, Posing, etc plugins). It would be better to have those "won't pass even if fine" concepts documented outside of discord or suggestion channels.


Design and Implement detail about district.

Put information about the district on the detailed results page, and link from there to UKBMD.

Ready for testing in test2

@richpomfret to test.

Tested and looked good to me.


depend on urllib3>=1.26.0

config.py is directly using urllib3 Retry(allowed_methods=...), which
was added in urllib3 version 1.26.0. declare the dependency explicitly.

related to https://github.com/snok/django-auth-adfs/issues/192

Closes #192

Thank you! Have a good evening 🚀

Released in 1.9.3. Thank you 😊


improved make_lines efficiency

This PR reduces some unneeded allocations and operations in make_lines.
We're using the influxdb client in our high throughput, low latency web service. We've profiled our service and found that make_lines was a bottleneck. When make_lines takes a long time, it blocks other greenlets from servicing requests.
No change in functionality; only efficiency.

Thanks!


Vue-material + Laravel gulpfile

I saw that u use laravel, and I wonder compile the components using gulpfile is possible ??
I would love to use the vue material into a new project I'm implementing.

Well. You can use gulp with Vue Material. It's totally fine and easy. You can use the standalone build and include the vue-material.js in your HTML or use some other tools like babel or browserify to import the library directly inside your js code. This second option is the best because you can have more control of your dependencies.
If you want to build new components, contribute or change something in a fork you still can use gulp, but you have to setup webpack as well. This project need some loaders that only webpack can achieve without change the source code.
What is your environment? Are you using Laravel Elixir to compile the assets?

I use macOS Sierra with, Laravel 5.3 and to compile the assets Elixir in my gulpfile.

@sldobri just follow the instruction at Getting Started , simply npm install all required dependency...
if you having trouble with the import 'vue-material/dist/vue-material.css' or want to combine the vue-material.css with your own css, you can edit your gulp file in elixir function and add mix.copy('node_modules/vue-material/dist/vue-material.css', 'resources/assets/sass/material.scss');

@echr  my laravel files:
{
  "private": true,
  "scripts": {
    "prod": "gulp --production",
    "dev": "gulp watch"
  },
  "dependencies": {
    "autosize": "^3.0.17",
    "element.scrollintoviewifneeded-polyfill": "^1.0.1",
    "node-sass": "^3.10.1",
    "scopedQuerySelectorShim": "github:lazd/scopedQuerySelectorShim",
    "stream-browserify": "^2.0.1",
    "vue": "^2.0.2",
    "vue-material": "^0.1.2",
    "webpack": "^1.13.2"
  },
  "devDependencies": {
    "autoprefixer": "^6.5.0",
    "babel-core": "^6.17.0",
    "babel-eslint": "^7.0.0",
    "babel-loader": "^6.2.5",
    "babel-plugin-transform-runtime": "^6.15.0",
    "babel-preset-es2015": "^6.16.0",
    "babel-preset-stage-0": "^6.16.0",
    "bootstrap-sass": "^3.3.7",
    "chalk": "^1.1.3",
    "connect-history-api-fallback": "^1.3.0",
    "copy-webpack-plugin": "^3.0.1",
    "css-loader": "^0.25.0",
    "eslint": "^3.7.1",
    "eslint-friendly-formatter": "^2.0.6",
    "eslint-loader": "^1.5.0",
    "eslint-plugin-html": "^1.5.3",
    "eventsource-polyfill": "^0.9.6",
    "express": "^4.14.0",
    "extract-text-webpack-plugin": "^1.0.1",
    "file-loader": "^0.9.0",
    "gulp": "^3.9.1",
    "highlight.js": "^9.7.0",
    "html-webpack-plugin": "^2.22.0",
    "jquery": "^3.1.0",
    "laravel-elixir": "^6.0.0-11",
    "laravel-elixir-vue-2": "^0.2.0",
    "laravel-elixir-webpack-official": "^1.0.2",
    "lodash": "^4.16.2",
    "node-sass": "^3.10.1",
    "ora": "^0.3.0",
    "raw-loader": "^0.5.1",
    "sass-loader": "^4.0.2",
    "vue-hot-reload-api": "^2.0.6",
    "vue-html-loader": "^1.2.3",
    "vue-loader": "^9.5.1",
    "vue-resource": "^1.0.3",
    "vue-router": "^2.0.1",
    "vue-style-loader": "^1.0.0",
    "vue-template-compiler": "^2.0.1",
    "webpack": "^1.13.2",
    "webpack-dev-middleware": "^1.8.4",
    "webpack-hot-middleware": "^2.12.2",
    "webpack-merge": "^0.14.1"
  }
}

const elixir = require('laravel-elixir');
require('laravel-elixir-vue-2');

elixir(mix => {
    mix.webpack('app.js');
});

import Vue from 'vue'
import VueMaterial from 'vue-material'
import 'vue-material/dist/vue-material.css'

Vue.use(VueMaterial)

const app = new Vue({
    el: '#app'
});

<!DOCTYPE html>

    <meta charset="UTF-8">
    <title>Theme Example</title>

      <md-toolbar>

My Title

      </md-toolbar>

      <md-button class="md-primary">Primary Button</md-button>

following @echr advice, I still get the following error when runing gulp

Error: ./~/vue-material/dist/vue-material.js│Module build failed: SyntaxError: 'with' in strict mode (8:13503)


micsthepick: Watch iqtestonline.net

micsthepick requests the watch of the watch_keyword iqtestonline.net. See the MS search here and the Stack Exchange search here.

iqtestonline.net has been seen in 1 true positive, 0 false positives, and 0 NAAs.

!!/approve

!!/approve

Coverage remained the same at 66.374% when pulling 55508b9978273321c951324671dbc99ffe004d58 on auto-blacklist-1535715728 into feac96cbfb7903256d0353460eb409184e2714a7 on master.


[131] Issue #131 - April 4, 2019

To contribute to this issue, simply leave a comment here. Please also review our contributing guidelines.
The current draft for this issue in _drafts/. If you want to contribute directly, feel free to open a pull request.

https://swift.org/blog/utf8-string/

245 accepted

https://forums.swift.org/t/history-why-does-closure-syntax-use-the-keyword-in/21885

Pitch: Implicit Returns from Single-Expression Functions

Swift provides a pleasant shorthand for short closures: if a closure contains just a single expression, that expression is implicitly returned--the return keyword can be omitted. We should provide this shorthand for functions as well.

Implementation
https://forums.swift.org/t/pitch-implicit-returns-from-single-expression-functions/21898

Pitch: Property Delegates

There are property implementation patterns that come up repeatedly. Rather than hardcode a fixed set of patterns into the compiler, we should provide a general "property delegate" mechanism to allow these patterns to be defined as libraries. The complete proposal follows, and the most up-to-date version will be available here.

Implementation
https://forums.swift.org/t/pitch-property-delegates/21895

Pitch: Static and class subscripts

Over the last few days I've put together a prototype of static subscripts, which allow you to add subscripts that are applied to a type, rather than an instance. There's a lot of work to be done, but so far, it's looking pretty good; I've even gotten dynamic member lookup and key paths working (although they're a stretch goal and I might defer them before the final proposal). I think they would be a good addition to the language.

https://forums.swift.org/t/pitch-static-and-class-subscripts/21850

History: Why does closure syntax use the keyword in?

https://forums.swift.org/t/history-why-does-closure-syntax-use-the-keyword-in/21885
Maybe this can be fun one :)

https://forums.swift.org/t/string-consumption/21907

The review of SE-0251: SIMD Additions begins now and runs through April 1st, 2019.
https://forums.swift.org/t/se-0251-simd-additions/21957

https://twitter.com/slava_pestov/status/1108482948129533952

https://github.com/apple/swift-package-manager/pull/2053

Swift 5 release notes:
https://developer.apple.com/documentation/xcode_release_notes/xcode_10_2_release_notes/swift_5_release_notes_for_xcode_10_2

Blog post about Swift 5 release
https://swift.org/blog/swift-5-released/

The review of SE-0244: Opaque Result Types has concluded and the proposal has been returned for revision.
https://forums.swift.org/t/returned-for-revision-se-0244-opaque-result-types/22115

SE-0247: Contiguous Strings has been accepted with modification
https://forums.swift.org/t/accepted-with-modification-se-0247-contiguous-strings/22111

https://twitter.com/johannesweiss/status/1110480163106623488

🚀 SwiftNIO 2 for Swift 5 has shipped 🙌.
Thanks so much everybody, we're thrilled for the next chapter in the Swift on Server story 🚢.
https://forums.swift.org/t/swiftnio-2/22136

252 in review

NIOPostgres: A NIO-based PostgreSQL Driver by @tanner0101
https://forums.swift.org/t/niopostgres-a-nio-based-postgresql-driver/22178

https://twitter.com/slava_pestov/status/1110770519106830336

Fixing a 6.5 year old radar: https://github.com/apple/swift/pull/23591

https://twitter.com/jckarter/status/1110954850487943168

A great thread with tips if you're interesting in getting into compilers and language design https://forums.swift.org/t/how-to-become-an-expert-in-compilers-the-long-way/22175/10

243 rejected

SE-0246: Generic Math Functions has been accepted with Modifications
https://forums.swift.org/t/accepted-with-modifications-se-0246-generic-math-functions/22244

The review of SE-0253: Static callables begins now and runs through April 5, 2019
https://forums.swift.org/t/se-0253-static-callables/22243

Unicode scalar literals

In light of the core team's decision on SE-0243, I'd like to kick off a pitch for single-quoted literals based on the feedback given.

https://forums.swift.org/t/unicode-scalar-literals/22224

The review of SE-0249 has concluded and the proposal has been accepted.
https://forums.swift.org/t/accepted-se-0249-key-paths-expressions-as-functions/22287

https://twitter.com/dgregor79/status/1111505088952991744

Refining some ideas under discussion for custom attributes in #SwiftLang over at https://forums.swift.org/t/pitch-introduce-custom-attributes/21335/47

https://twitter.com/slava_pestov/status/1111746907502723073

One of the earlier proposals that I don't think many people paid much attention to at the time was actually rather interesting in hindsight because it enabled a radical simplification of the compiler: https://github.com/apple/swift-evolution/blob/master/proposals/0060-defaulted-parameter-order.md

249 accepted

https://twitter.com/twostraws/status/1111778640650555392

There's a fix for this already: https://github.com/apple/swift/pull/23674 – and people say filing a bug report with Apple doesn't work! 😎 https://twitter.com/twostraws/status/1111737369269600256

https://twitter.com/swift_unwrapped/status/1112717307346931719

Episode 73: UTF-8 Strings in Swift 5 https://spec.fm/podcasts/swift-unwrapped/288713

https://forums.swift.org/t/new-code-visualizer-for-swift-source-is-view/22454

A code visualizer for Swift. Made for April Fools' Day 2019. 😃

https://twitter.com/dgregor79/status/1113134634852728832

#Swiftlang SE-0254 "Static and class subscripts" is under review until April 9, 2019. https://forums.swift.org/t/se-0254-static-and-class-subscripts/22537

https://twitter.com/Ilseman/status/1113148333617369088

Swift on Windows is nigh!
Awesome work from Saleem and crew.
https://forums.swift.org/t/swift-windows/22458

https://github.com/apple/swift-evolution/blob/master/proposals/0255-omit-return.md review

https://twitter.com/slava_pestov/status/1113256921862090757

I was inspired by @brentdax’s work on static subscripts to get default arguments working for subscripts. This was supposed to be part of generic subscripts in Swift 4; @pathofshrines did some cleanup in SILGen recently that finally made it possible. https://github.com/apple/swift/pull/23734

252 accepted

256 in review https://github.com/apple/swift-evolution/blob/master/proposals/0256-contiguous-collection.md

https://twitter.com/Catfish_Man/status/1113597070504423424

I’ve posted a pitch for a new Swift String initializer that allows for faster interop with C APIs like CFStringGetBytes. Feedback gratefully accepted :)
https://forums.swift.org/t/pitch-add-a-string-initializer-with-access-to-uninitialized-storage/22611


TypeError uploading a playlist cover image

I get the following error when I try to upload a playlist cover image. Authentication is working and the scope contains "playlist-read-private", "playlist-modify-private", "playlist-modify-public", "ugc-image-upload".
TypeError: "string" must be a string, Buffer, or ArrayBuffer
    at Function.byteLength (buffer.js:481:11)
    at Request._end (/Users/user/Desktop/project/node_modules/superagent/lib/node/index.js:804:84)
    at Request.end (/Users/user/Desktop/project/node_modules/superagent/lib/node/index.js:777:15)
    at Object.HttpManager._makeRequest (/Users/user/Desktop/project/node_modules/spotify-web-api-node/src/http-manager.js:85:7)
    at HttpManager.put (/Users/user/Desktop/project/node_modules/spotify-web-api-node/src/http-manager.js:146:15)
    at /Users/user/Desktop/project/node_modules/spotify-web-api-node/src/base-request.js:92:5
    at new Promise (<anonymous>)
    at Request.execute (/Users/user/Desktop/project/node_modules/spotify-web-api-node/src/base-request.js:91:10)
    at SpotifyWebApi.uploadCustomPlaylistCoverImage (/Users/user/Desktop/project/node_modules/spotify-web-api-node/src/spotify-web-api.js:609:8)
    at addCoverToSpotifyPlaylist (/Users/user/Desktop/project/scripts/main.js:131:6)

My code
spotifyApi.uploadCustomPlaylistCoverImage('191...9Ud', '/9j/4AAQSk...KACgAoAKAP//Z')
  .then(
  (data) => { ... },
  (error) => { ... }
);

System
OS: macOS 10.13.6
Node Version: v8.12.0

Did you fix this? I'm having the same issue.

Same here. I tried Spotify route using Postman and I can upload a new cover image but I cannot get any response from Spotify; it changes the cover image but I get an empty string as result. Maybe this empty result causes the crash?

Same here!

Apparently the underlying superagent module (used here) does not output much information about this error, this is already part of another PR (see: https://github.com/visionmedia/superagent/issues/1482). This is why the error message is kinda confusing.
tl;dr:
See the diff in my personal repository on how to fix the error: https://github.com/dersimn/spotify-web-api-node/commit/57f14da2aea46bb4ea6dc6fde16c8c41785ef7be
long:

Function spotifyApi.uploadCustomPlaylistCoverImage(id, base64) passes the base64 (typeof = string) to WebApiRequest.withBodyParameters(base64) (here)

WebApiRequest.withBodyParameters(base64) (here) itself is a call to WebApiRequest._assigner('bodyParameters')(base64) which destructs the String by this for-loop into an object looking like:

{
    '0': 'd',
    '1': 'a',
    '2': 't',
    '3': 'a',
    '4': ':',
    '5': 'i',
    '6': 'm',
    '7': 'a',
    '8': 'g',
    '9': 'e',
    '10': '/',
    '11': 'j',
    '12': 'p',
    '13': 'e',
    '14': 'g',
    '15': ';',
    '16': 'b',
    '17': 'a',
    '18': 's',
    '19': 'e',
    '20': '6',
    '21': '4',
    '22': ',',
    '23': '/',
    '24': '9',
    '25': 'j',
    '26': '/',
    '27': '4',
    '28': 'A',
    '29': 'A',
    '30': 'Q',
    '31': 'S',

Note: My String starts with data:image/jpeg;base64. this is wrong. The Spotify API expects the string to start right with /9j/j/4.... I'm just too lazy to reproduce the error again (I'm happy that I found the issue after 2h or so)..

The request with now typeof this.bodyParameters => object ends up in HttpManager (which utilises superagent) and is passed to superagent.send(base64AsFuckedUpObject) and causes the error when superagent.end() is invoked here.


Parser error extending BaseRopeTool2D

Ocassionally when running from the editor I get this parse error in GD script

It seems some form of race condition is happening but my GD script knowledge is very limited. My project is using C# and my scene has a child node of type Rope. I have another node of type RopeAnchor in the scene.

I'm using version 1.3 of RopeSim

This is pretty strange. I never encountered this problem and I don't understand why it would appear in the first place. This is also a fairly normal usecase.
Can you reproduce this bug consistently? If so, could you try to upload a minimal reproduction project?
Which Godot version are you using?

Hm, this could indeed be the problem.
All rope related tools including ropes themselves reference in some way NativeRopeServer, which is a singleton (similar to PhysicsServer, VisualServer, ...).
If NativeRopeServer has not yet been loaded, but you try to instantiate the scene with rope scripts, you will get an error, because all scripts that directly reference NativeRopeServer fail to parse and load.
I'd suggest to not instantiate scenes from autoloads unless you now for sure that all other autoloads and singletons have been loaded already.
What I do, for example, I have an "init" scene that is loaded on start, which is completely empty besides a ColorRect for background and a single node that loads the actual main scene in _ready().
This way you can be sure everything has been loaded and initialized correctly.

Thanks for the description of under the hood very helpful!
Yea, its something where I'm moving away from, as it turns out my main scene calls a method after ready which wires up the map nodes for features and in there I now instantiate my scene containing the Rope node - which after reading your suggestions follows a similar concept. So far I have not had the issue happen so I'm hopeful this has solved it :)
Thanks for your help!


Add more model support with liteLLM

Have default litellm OnlineRequestProcessor that is a catch-all for anything that we haven't optimized or implemented ourselves

https://github.com/bespokelabsai/curator/issues/62#issuecomment-2471763740

Also will want to think about if we want to / can accommodate the instruct + litellm integration:
https://docs.litellm.ai/docs/completion/input
for structured output.

Other nice things we can use:
https://docs.litellm.ai/docs/#exception-handling
https://docs.litellm.ai/docs/#logging-observability---log-llm-inputoutput-docs
https://docs.litellm.ai/docs/completion/token_usage

Even outside of a full LiteLLMRequestProcessor, we can use their nice token counter
https://docs.litellm.ai/docs/completion/token_usage#3-token_counter
for rate limiting
And
https://docs.litellm.ai/docs/completion/token_usage#6-completion_cost
https://docs.litellm.ai/docs/completion/token_usage#8-model_cost
https://docs.litellm.ai/docs/completion/token_usage#9-register_model
For tracking cost

We should think about if we want to try to route more things towards our OpenAIOnlineBatchRequestProcessor and make that more general towards anything that has the same request and response format. Or if we want to instead default heavily to litellm.
LiteLLM runs into the max 50 requests-per-second. Trung opened an issue here:
https://github.com/BerriAI/litellm/issues/6592

https://docs.litellm.ai/docs/routing
This would be very good for getting tokens from a bunch of providers at the same time

To respond to some of the links,
Looked at

https://docs.litellm.ai/docs/completion/token_usage#6-completion_cost
https://docs.litellm.ai/docs/completion/token_usage#8-model_cost
https://docs.litellm.ai/docs/completion/token_usage#9-register_model

Pretty actively maintained community maintained metadata https://github.com/BerriAI/litellm/blob/main/model_prices_and_context_window.json. I like it 👍🏼

Tasks Breakdown:

[ ] Basic LiteLLMOnlineRequestProcessor

Use https://docs.litellm.ai/docs/completion/input, https://docs.litellm.ai/docs/#exception-handling, https://docs.litellm.ai/docs/completion/token_usage#8-model_cost, https://docs.litellm.ai/docs/completion/token_usage#9-register_model

[ ] Add structured output - https://docs.litellm.ai/docs/tutorials/instructor
[ ] LiteLLM Batch inference - https://docs.litellm.ai/docs/completion/batching#send-multiple-completion-calls-to-1-model
[ ] LiteLLM Routing (*) - https://docs.litellm.ai/docs/routing

= P2

for documentation purpose, here's the native way to get response costs from litellm, using hidden_params

And example data schema from the response obj
ModelResponse(id='chatcmpl-a1084780-9c3f-4121-8c75-963e7b76854d', created=1731976691, model='claude-3-haiku-20240307', object='chat.completion', system_fingerprint=None, choices=[Choices(finish_reason='tool_calls', index=0, message=Message(content=None, role='assistant', tool_calls=[ChatCompletionMessageToolCall(index=0, function=Function(arguments='{"title": "Brazilian Feijoada", "ingredients": ["black beans", "pork shoulder", "smoked sausage", "bacon", "onion", "garlic", "bay leaves", "orange slices", "cilantro"], "instructions": ["1. Soak the black beans overnight.", "2. In a large pot, cook the pork shoulder, smoked sausage, and bacon until browned.", "3. Add the onion and garlic and cook until softened.", "4. Drain and rinse the black beans, then add them to the pot along with the bay leaves.", "5. Cover with water and simmer for 2-3 hours, until the beans are very soft.", "6. Season with salt and pepper to taste.", "7. Serve the feijoada hot, garnished with orange slices and chopped cilantro."]}', name='Recipe'), id='toolu_01MhCsMGVuA3uNZFrsDmiVWB', type='function')], function_call=None))], usage=CompletionUsage(completion_tokens=249, prompt_tokens=538, total_tokens=787, completion_tokens_details=None, prompt_tokens_details=None))

and this is the resp._hidden_params
{'additional_headers': {'x-ratelimit-limit-requests': '4000', 'x-ratelimit-remaining-requests': '3999', 'x-ratelimit-limit-tokens': '400000', 'x-ratelimit-remaining-tokens': '400000', 'llm_provider-date': 'Tue, 19 Nov 2024 00:38:51 GMT', 'llm_provider-content-type': 'application/json', 'llm_provider-transfer-encoding': 'chunked', 'llm_provider-connection': 'keep-alive', 'llm_provider-anthropic-ratelimit-requests-limit': '4000', 'llm_provider-anthropic-ratelimit-requests-remaining': '3999', 'llm_provider-anthropic-ratelimit-requests-reset': '2024-11-19T00:38:48Z', 'llm_provider-anthropic-ratelimit-tokens-limit': '400000', 'llm_provider-anthropic-ratelimit-tokens-remaining': '400000', 'llm_provider-anthropic-ratelimit-tokens-reset': '2024-11-19T00:38:51Z', 'llm_provider-request-id': 'req_01EajWVBZtXQ5B8wKAVkLmgo', 'llm_provider-via': '1.1 google', 'llm_provider-cf-cache-status': 'DYNAMIC', 'llm_provider-x-robots-tag': 'none', 'llm_provider-server': 'cloudflare', 'llm_provider-cf-ray': '8e4c23bb2dbe29d0-ORD', 'llm_provider-content-encoding': 'gzip', 'llm_provider-x-ratelimit-limit-requests': '4000', 'llm_provider-x-ratelimit-remaining-requests': '3999', 'llm_provider-x-ratelimit-limit-tokens': '400000', 'llm_provider-x-ratelimit-remaining-tokens': '400000'}, 'optional_params': {'tools': [{'name': 'Recipe', 'input_schema': {'properties': {'title': {'description': 'Title of the recipe', 'title': 'Title', 'type': 'string'}, 'ingredients': {'description': 'List of ingredients needed', 'items': {'type': 'string'}, 'title': 'Ingredients', 'type': 'array'}, 'instructions': {'description': 'Step by step cooking instructions', 'items': {'type': 'string'}, 'title': 'Instructions', 'type': 'array'}}, 'required': ['ingredients', 'instructions', 'title'], 'type': 'object'}, 'description': 'Correctly extracted `Recipe` with all the required parameters with correct types'}], 'tool_choice': {'type': 'tool', 'name': 'Recipe'}}, 'model_id': None, 'api_base': None, 'response_cost': 0.0005682500000000001}


Move dev option to approporiate location

Platforms affected
electron
Motivation and Context

devTools option can be set inside webPreferences. Therefore, we can deleteisRelease option and set devTools option inside  webPreferences instead.
Description

Move dev option to the appropriate location.
Update tests.

Testing

npm t
Checklist

[x] I've run the tests to see all new and existing tests pass
[x] I added automated test coverage as appropriate for this change
[ ] Commit is prefixed with (platform) if this change only applies to one platform (e.g. (android))
[x] If this Pull Request resolves an issue, I linked to the issue in the text above (and used the correct keyword to close issues using keywords)
[ ] I've updated the documentation if necessary

Codecov Report

Merging #11 into support-user-defined-electron-settings will decrease coverage by 0.17%.
The diff coverage is 100%.

@@                            Coverage Diff                             @@
##           support-user-defined-electron-settings      #11      +/-   ##
==========================================================================
- Coverage                                     100%   99.82%   -0.18%
==========================================================================
  Files                                          14       14
  Lines                                         568      568
==========================================================================
- Hits                                          568      567       -1
- Misses                                          0        1       +1

Impacted Files
Coverage Δ

bin/templates/cordova/lib/SettingJsonParser.js
92.3% <100%> (-7.7%)
: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 4f0e0c9...432edad. Read the comment docs.


No Version in react-oidc-context\dist\esm\package.json causes warning.

Directly after installing react-oidc-context and oidc-client-ts I'm getting a warning after npm start.
The warning is:
Compiled with problems:
WARNING in shared module oidc-client-ts -> C:\Users\btrautmann\workspace\timnet-ui\node_modules\oidc-client-ts\dist\esm\oidc-client-ts.js
No version specified and unable to automatically determine one. No version in description file (usually package.json). Add version to description file C:\Users\btrautmann\workspace\timnet-ui\node_modules\oidc-client-ts\dist\esm\package.json, or manually specify version in shared config.
WARNING in shared module react-oidc-context -> C:\Users\btrautmann\workspace\timnet-ui\node_modules\react-oidc-context\dist\esm\react-oidc-context.js
No version specified and unable to automatically determine one. No version in description file (usually package.json). Add version to description file C:\Users\btrautmann\workspace\timnet-ui\node_modules\react-oidc-context\dist\esm\package.json, or manually specify version in shared config.
Anyone having this as well?

I do not see this warning,
btw in the node_modules\oidc-client-ts\package.json we have the version:
{
  "name": "react-oidc-context",
  "version": "2.1.1",
...

the node_modules\oidc-client-ts\dist\esm\package.json is only thought as a type marker
Which version on npm (npm -v) do you use? I have 8.11.0

I'm using 8.15.0

That means your is newer. I am happy to accept a merge request to fix this. Is it enough to provide a fake version?

It is completely enough as long the warning is not there anymore :).

Please provide a merge request to fix this...

So the reason this is happening is that in the bundled ESM module there's no "version" attribute in package.json (only "type": "module" there). You can fix that locally in the Federated Plugin by specifying version directly (not to be confused with requiredVersion, which is about the version range that is requested from the NPM, while version is more about the tag with which the module is exposed in the shared modules).


Get sent message in MIME format after/before sending?

I am doing the following to send mail:
let helper = require('sendgrid').mail;
let mail = new helper.Mail(from_email, subject, to_email, content);
mail.addAttachment(attachment);

let request = sgClient.emptyRequest({
    method: 'POST',
    path: '/v3/mail/send',
    body: mail.toJSON(),
});

sgClient.API(request)
    then(response => {...

and would like to then save the message in MIME format to S3 though it doesn't look like I can get it anywhere on the response object and I can't see anything on the request object that allows me to convert to MIME and cache in S3 before I send.  Am I missing something that would make this possible?

Hello @byjoh,
We don't currently have a means to do that with our SDK or API.
I suggest that you bcc the email to our Inbound Email Parse Webhook, then process and store the email when you receive the webhook.
With Best Regards,
Elmer


Add files via upload

Related Issue
Closes: #[issue number that you are working on]
Changes:
Added Pattern38.c
Output:

The changes are made.


False positive in RET503 since ruff 0.0.248

Since version 0.0.248 ruff flags this code as having an error:
def foo():
    while True:
        return True

I have git bisected this down to commit 059601d9685098a071bac6149ef5f321b3d845b8, PR #2962.
Running $ cargo run -p ruff_cli -- check ./x.py --no-cache --select RET503 produces this error:
x.py:2:5: RET503 [*] Missing explicit `return` at the end of function able to return non-`None` value

This while True is a common pattern in Python to make infinite loops, and it clearly never returns unless there is a break inside.
I do not want to return None in the end, because I annotate my functions with types, and having a return None at the end of a function that is supposed to return an object (in this case I can add return False in the end, but not all objects are as easily constructable) would be flagged by mypy/pyright.

I guess we could treat while True: differently than other while loops. The issue is that, in general, we can't be certain that the loop will actually execute, so even if it ends in a return, we treat it as if it's non-returning. (The previous version just omitted while loops entirely, which is also a valid option and probably easier.)

I'll make sure it's fixed for the next release.

For now I just omitted while True entirely. We can do better of course but hopefully this avoids these false positives for you. (Previously, I think we ignored all while loops.)


Alacritty opens as a tiny spec in a corner

See the attached screenshot. I'm using the current master (b92ba65) on archlinux + gnome with the default config file.

Window is a tiny spec in the top left corner
Title is 'Unknown'
Icons are broken
No icons to maximise/minimize or close the window

Is this under X or Wayland?

Wayland

You'll probably have a better experience using XWayland. Run with env WAYLAND_DISPLAY= alacritty.

Luckily the window can be resized. Wonder why the window isn't being sized properly in the first place though.

@jwilm Interesting. Left side is wayland, right side with xwayland. Font sizes seems really different on both.

@jaseemabid I believe winit doesn't detect high DPI on Wayland.

Possibly. I'm using a Dell XPS 13" 1920x1080 display.

Winit/Glutin has gotten some big updates since this issue was reported. I believe this should be fixed now by the new DPI mode. If this issue is still present, please let me know and I'll re-open.


Add g:ale_php_cs_fixer_options variable

This allows me to fall back to a global config file:
if !filereadable('.php_cs') && !filereadable('.php_cs.dist')
  let g:ale_php_cs_fixer_options = '--config="$HOME/.php_cs"'
endif

Excuse me, I hadn't bothered to try the tests locally.

Cheers! :beers:


New language localization (tr) underway - Updates so far

So far:

New language (Turkish) added into _config.yml file
New data folder created. Under lang, new tr folder created and all yml files translated (namely footer-1.yml, footer-2.yml, navigation.yml and roadmap.yml)
Under i18n, new folder "tr" created by cloning the template.
tr.yml fully translated.
"Turkish" as a new language been added into en.yml and es.yml files (so that the language also appears on other language versions of the site)
downloads.md, index.md, press-kit.md, techical-specs.md and the-monero-project.md translated.
Next: get-started folder.

@erciccione :) (I assume it's fine though)

hehe lol, but yes, it's fine, just minor fixes

Dear both,
Yes, this PR is ready to be merged (if you agree to it too, obviously).
I am working on the translation of the remaining and in-depth portion of the site, i.e. Moneropedia and Dev Guides. Those should possibly arrive in a separate PR.
Cheers!

I don't think Moneropedia can be translated yet. It requires some custom Ruby scripting that I'm not able to do myself.

Hi rehrar,
In that case the translation for Turkish can be marked as complete except for the dev guides. For those though, I will first need to have a good understanding of the guides before translating them in a meaningful manner which would make sense to the developers.
By the way, the Moneropedia files kind of look translatable to me? For example, account.md (and many others) are based in plain text just like the rest of the website docs. The only (minor) difficulty is to give consistent names for "@" which upon click, should direct you to a specific Moneropedia page. So far I managed it okay. (I already translated 6-7 files by the way).
By the way, should I mark this PR as closed or it should be done by the reviewers (or the person who'll do the merge)?

@7dNp8xK3Ed can we get a rebase on this? :)

@rehrar Resolved conflicts.

@7dNp8xK3Ed the website doesn't build, you need to fix it creating 2 copies of the new guide cli_wallet_daemon_isolation_qubes_whonix.md. One need to go in _i18n/it/resources/user-guides/ and the other one in _i18n/tr/resources/user-guides.
After doing that, please squash as suggested on reddit

Blarg. Can we get one more rebase on this? Unfortunately the multi-language plugin constantly causes conflicts and I'm not really sure that can be resolved.

@7dNp8xK3Ed Some commtis were pushed during these weeks. Can you rebase this PR please?

Hey @7dNp8xK3Ed any news? are you still working on this?


pagedra login is outdated

pagedraw login fails with error message "Your Pagedraw CLI is out of date."
Using OSX, npm 6.11.3, nodejs 12.11.1. Installation log:
ary-MBA:~ garyfeng$ npm install -g pagedraw-cli
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>Use uuid module instead
npm WARN deprecated<EMAIL_ADDRESS>This module moved to @hapi/hawk. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated<EMAIL_ADDRESS>This module moved to @hapi/sntp. Please make sure to switch over as this distribution is no longer supported and may contain bugs and critical security issues.
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
npm WARN deprecated<EMAIL_ADDRESS>This version has been deprecated in accordance with the hapi support policy (hapi.im/support). Please upgrade to the latest version to get the best features, bug fixes, and security patches. If you are unable to upgrade at this time, paid support is available for older versions (hapi.im/commercial).
/usr/local/bin/pagedraw -> /usr/local/lib/node_modules/pagedraw-cli/artifacts/pagedraw.js
+<EMAIL_ADDRESS>updated 1 package in 12.955s
Gary-MBA:~ garyfeng$ pagedraw login
Your Pagedraw CLI is out of date. Please run
	npm install -g undefined@undefined

I'm getting the same issue. :(


Uncaught TypeError: Cannot assign to read only property

Uncaught TypeError: Cannot assign to read only property 'copy' of function 'function scale(x)
How I can fix it? I use
import { scaleLinear } from "d3-scale"
in part of inside lib code:
  var scale = continuous();

  scale.copy = function() { // <== error here
    return copy(scale, linear());
  };

  initRange.apply(scale, arguments);

  return linearish(scale);

P.S. Using Vue 2.4

Sorry, but I have no idea what’s going wrong here. It would appear that your bundler is breaking the code somehow.


Warn on import failures within optional dependencies

Summary
This distinguishes the case of "failed to find an optional dependency" from "found the optional dependency, but it failed to import" within the lazy testers.  Now, a warning containing the import failures will be shown to users, rather than silently treating the dependency as missing.
This occurred recently when a PR caused an import failure in Aer, which the CI suite failed to detect because the optional-dependency checkers allowed the test suite to pass regardless.  Note that this commit alone won't reliably cause the test suite to fail on a failed import because:

this only emits a warning, not an exception (by design).
the unittest decorators are evaluated during test discovery, which happens before we activate our increased warning filters.

This commit also unifies the now two Qiskit-specific warnings (the other being QPYLoadingDeprecatedFeatureWarning) with a common QiskitWarning subclass, much as we do for QiskitError.  This gives us a convenient way to globally deny these errors during CI runs, without turning all UserWarnings into errors, which we're not ready to do yet.

Details and comments
I think, in a follow-up PR, we ought to move the major warning filters (error::DeprecationWarning and error::qiskit.exceptions.QiskitWarning) into test.python.__init__ with:
import sys
import warnings

if not sys.warnoptions:
    warnings.filterwarnings("error", category=DeprecationWarning)

    import qiskit.exceptions
    warnings.filterwarnings("error", category=qiskit.exceptions.QiskitWarning)

so that the top-level defaults are set up in the recommended Python way before test discovery.  This would let us fail the test suite if an optional has been installed but fails to import, without making the test suite dependent on what order the test cases happen to run or discover.
(It's possible that turning on deprecation warnings as errors during qiskit import might cause us some problems or require us to rewrite small parts of the test suite for old modules to delay the imports, but I think that might be a good thing.)
For example, if this PR is applied on top of #11488 using Aer 0.13.1, which will fail to import, the behaviour of trying to use the failed optional import now looks like this:
from qiskit import QuantumCircuit
from qiskit.providers.fake_provider import FakeAthens

FakeAthens().run(QuantumCircuit(2, 2))

/Users/jake/code/qiskit/terra/qiskit/utils/lazy_tester.py:323: OptionalDependencyImportWarning: While trying to import 'Qiskit Aer', some components were located but raised other errors during import. You might have an incompatible version installed. Qiskit will continue as if the optional is not available.
 - module 'qiskit.providers.aer' failed to import with: ImportError("cannot import name 'UnitaryGate' from 'qiskit.extensions' (unknown location)")
  warnings.warn(message, category=OptionalDependencyImportWarning)
/Users/jake/code/qiskit/terra/qiskit/providers/fake_provider/fake_backend.py:568: RuntimeWarning: Aer not found using BasicAer and no noise
  warnings.warn("Aer not found using BasicAer and no noise", RuntimeWarning)

Previously, it would just silently behave as if Aer wasn't installed at all.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.02%) to 87.58%

Totals

Change from base Build<PHONE_NUMBER>:
0.02%

Covered Lines:
59514

Relevant Lines:
67954

💛  - Coveralls

Ha - nice true error on this PR.  We have a couple of optionals that drill into subpackages, and the handling I put in to detect whether it's a ModuleNotFoundError from the target module or not fails to account for attempts to import a submodule.  That needs an actual fix.

Certainly an improvement to have a distinction!
I'm sure there's a historical reason for this, but why is MissingOptionalLibraryError an Exception, whereas OptionalDependencyImportWarning is a UserWarning?

Kevin: do you mean why is the second on derived from UserWarning rather than Warning?
If so: when Elena added QPYLoadingDeprecatedFeatureWarning (#11260) we made it a subclass of UserWarning because we were basing it on what NumPy do with their VisibleDeprecationWarning.  That's the only reason, I think - we mostly just trusted that whatever NumPy were doing was sensible.

From offline discussion with Kevin: the question was actually along the lines of "why do we make it a warning instead of an error if an optional is found but fails to import?".  The answer is that in a few cases, Qiskit only uses the optionals as accelerators and not as hard requirements.  Examples of this are in the generation of approximation tables for the Solovay–Kitaev algorithm or in the FakeBackend.run methods, where (respectively) scikit-learn and Aer are used as accelerators, but Qiskit can fall back to internal-only methods in their absence.
The idea is that the warning triggers, then if the optional is required, a regular MissingOptionalLibraryError will be raised in addition right after.


scidap workflow missing test data, draft-3 compat

Hello @tetron & @portah,
Is there "Git-sized" test-data for this workflow? For the sake of maintenance I think we shouldn't include anything in this repo that doesn't have tests +/or test data.

[ ] tests for each command line tool in the existing style
[ ] overall "dry run" test of the workflow


Config LoadBalancer for frontendProxy

Environment:
OS: Multipass on Mac running Ubuntu 22.04 LTS
K8s: K3s v1.25.6+k3s1
Using serviceType yields the following error:
Error: UPGRADE FAILED: values don't meet the specifications of the schema(s) in the following chart(s):
opentelemetry-demo:
- components.frontendProxy: Additional property serviceType is not allowed

Using the following in values file works:
components:
  frontendProxy:
    service:
      type: LoadBalancer

Hello @rcastley, thanks for the PR. Can you sign the CLA? We can review then.

Hi, just waiting upon approval from management at Splunk :-)

@rcastley thanks! Unfortunately we churned the docs here and the file name is different. Would you like to still finish this up?

@rcastley - FYI, rebasing should be all you need to do to bring your PR up-to-date.


undo in mini.files erases all file names

Contributing guidelines

[X] I have read CONTRIBUTING.md
[X] I have read CODE_OF_CONDUCT.md
[X] I have updated 'mini.nvim' to latest version

Module(s)
mini.files
Description
When I press u or type :undo when in a mini.files popup, all the file names are erased, and the buffer is considered modified.
Neovim version
0.10.0
Steps to reproduce
Open a mini.files popup and press u in it.
Expected behavior
Expect u to show "Already at oldest change".
Actual behavior
Before:

After pressing u:

Thanks for the issue!
Yes, I am aware of this but don't think it is a huge problem. I'll take a look at if this can be solved  without much hassle.

This should now be fixed on latest main.

This should now be fixed on latest main.

It looks good now, thanks so much!


Remove the unwanted dropcap letters in history page

Is your feature request related to a problem? Please describe.
The dropcap letters(Big first letter) in the history page is not working. In the history page, there are two span elements with dropcaps and those are not visible in the website.
Example: Letter B in Beginning

Describe the solution you'd like
Remove the drop cap letters and add those as normal letters.
Describe alternatives you've considered
N/A
Additional context
N/A
Are you working on it?
No

Shall I work on this?

Yeah @Yoshitha-SACK

Thanks


test: update test_backup_with_backing_image

Which issue(s) this PR fixes:
longhorn/longhorn#9227
What this PR does / why we need it:
Add scenario for backing image size larger than volume size then backup volume.
Currently this scenario only included in test_system_backup_and_restore_volume_with_backingimage but v1.6.x does not support system backup with backing image so the scenario not tested in v1.6,x.
Special notes for your reviewer:
test result

amd
arm
sle-micro arm

Additional documentation or context

@mergify backport v1.7.x v1.6.x


Permission to delete policies is being pushed out right now

We opened a case with Microsoft when we found that after creating policies in the communication compliance tool we were not able to delete the policies.  It was original setup to where only the creator of the policy was able to delete the policy.  And this particiulary gave us an issue because the account it logged was different then my upn being captured when I logon to the compliance center.  So Microsoft pushed a change that anyone with access to the compliance center can now delete polices.  I would suggest getting the exact specifications on that and updating the documentation.

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

ID: 9ea1461c-a9db-d934-d5a6-169360842e8b
Version Independent ID: 6b214386-6f18-9de6-7a8b-b78e69d1387a
Content: Communication compliance feature reference - Microsoft 365 Compliance
Content Source: microsoft-365/compliance/communication-compliance-feature-reference.md
Service: o365-seccomp
GitHub Login: @robmazz
Microsoft Alias: robmazz

@bigdpnc  - thanks for the feedback, this update will be included in the documentation soon. It is in progress with other feature improvements. Thanks!

@bigdpnc  - thanks for the feedback, this update will be included in the documentation soon. It is in progress with other feature improvements. Thanks!


build(deps): explicit bump of http-cache-semantics to >=4.1.1

Updated the yarn.lock file via yarn up -R and
Also added a forced resolution of the versions in the root
package.json for good measure.

[skip ci]
Fixes #2335
Signed-off-by: Peter Somogyvari<EMAIL_ADDRESS>Pull Request Requirements
[ x] Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
[x] Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
[x] Follow the Commit Linting specification. You may refer to this link for more information.
Character Limit
[x] Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
[x] Commit Message per line must not exceed 80 characters (including spaces and special characters).
A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

@petermetz confict here too, please resolve. Thanks


Undefined update strategy inside rake task

Good afternoon, I'm receiving an Chewy::UndefinedUpdateStrategy error when creating or updating a Chewy-enabled model - but only when doing so within a rake task.
I've tried wrapping the individual call to the save method in a strategy block like so:
# This throws an UndefinedUpdateStrategy error
employees.each do |employee|
  Chewy.strategy(:atomic) do
    employee.save
  end
end

I also tried wrapping the entire parse method.
# This also throws an UndefinedUpdateStrategy error
Chewy.strategy(:atomic) do
  parse_employees(file_handle) # this method contains the save call
end

Neither had any effect. Interestingly, I was able to drop in a completely new block of code like so:
# This works fine
Chewy.strategy(:atomic) do
  EmployeesIndex.reset!
end

^ and that resets the index properly - it's only when calling save on individual employees that the error occurs.
Aside from the specific issue, I also don't understand why this error is occurring in the first place. The rake task initializes the Rails environment, so I would have thought that the Chewy configuration should be available from the get-go without needing to be wrapped in a block.
It's worth noting that when I run the same code from the console, it works fine - the error only occurs when it's wrapped in a rake task.
Any thoughts out of the gate? I can provide a sample app to replicate the problem if necessary.

It looks like this may be the same problem as #419 actually.

Yeah, right

First of all, EmployeesIndex.reset! doesn't need to be wrapped with a strategy, it works as is.
Also, this should work (and is a correct way actually):
Chewy.strategy(:atomic) do
  parse_employees(file_handle)
end

Are you sure this error comes from the inside of the block? Can you trace it?

So I was trying to replicate the error with our latest importer code and I wasn't able to do so. Wrapping it in the strategy block worked.
The major architecture change was that we originally had an async component (since removed) running with RabbitMQ using the Bunny gem - I'll try tomorrow to provide an example with the older code and see if the asynchronous part was what's causing the error.
As an aside, though, is there a way to have the rake tasks load the regular Chewy defaults to avoid having to wrap our code in the strategy block?

I didn't find an acceptable way to do this, unfortunately. Unlike controllers or migrations rake tasks might have different requirements, so it is better to go explicit.

This doesn't only happen with rake tasks but also with background jobs (https://github.com/toptal/chewy/issues/419)
Are we sure there is no way to default wrap the strategy definition for rake tasks and background jobs? I could gladly jump into this if it would be possible to do so.

You can do it in your project as you want to.
    class DelayedChewy < Delayed::Plugin
      callbacks do |lifecycle|
        lifecycle.around(:invoke_job) do |*args, &block|
          Chewy.strategy(:atomic) do
            block.call(*args)
          end
        end
      end
    end

Delayed::Worker.plugins << DelayedChewy

The only problem here is that requirements will be really different, so I would not propose a generic way.

+1

Is there a reasonable way to pick a default for Rake tasks? I'm trying to run the provided Paperclip task to refresh thumbnails and Chewy breaks those.

try this: https://stackoverflow.com/questions/15707940/rake-before-task-hook

@pyromaniac Thanks! I ended up with something like this to set a default:
namespace :chewy_strategies do
  task :bypass do
    Chewy.strategy :bypass
  end

  task :atomic do
    Chewy.strategy :atomic
  end
end

Rake::Task.tasks.each do |task|
  task.enhance do
    Rake::Task['chewy_strategies:bypass'].invoke
  end
end

Feels like a dirty hack, but works for now. Btw., re-opening the namespace :chewy to add tasks doesn't work, is makes the built-in Chewy task disappear. Oo


Add global service context

This PR adds an initial implementation for a global service context. The new and improved service context will dynamically import service_context from the .py file defined under the LLAMA_SERVICE_CONTEXT env variable.
This design also allows users to config on top of their existing global defaults.
This implementation might be divisive, but here's my justification for two main components of the design

Define the global service context in a .py file
Rather than trying to decompose complex settings into a yaml format or similar, just let the user configure everything in python using the API they are already familiar with. This means we don't have to maintain a separate config file format, and also any LLMPredictor (including huggingface!) and embed model can be easily set the in global config

Singleton pattern
I don't see a way to do this without using a singleton pattern. While OpenAI/ChatOpenAI are quick to initialize, if the user configures a HuggingfaceLLMPredictor, we don't want to reload this every time from_defaults() is called, because that would be a major performance hit.

@jerryjliu this is good feedback. Part of the motivation for having a separate file is that it adds a division between "app code" and "setup/configure code"
I'm on the fence about which way to do it, but the code would be a lot more simple if it wasn't a separate .py file. I'll revise the implementation that way and see how it goes.


Build via Docker and install in Makefile

Allow building via Docker in order to by-pass installing go. Also added install to Makefile.

You can download the pre-built binaries that are built on push to default branch using the CI to avoid installing Go and building it from source.

Well, thought I'd push it up as I build via source and had the Makefile handy ;-)


Not working in esp32 devkit v1   - (Wire1 bus)

Error failed to communicate with keypad
I connected to pin 25,26 and configured as same. I testing sample code in the library. Its not working

Thanks for reporting this issue.
As I am rather busy it might take time before I can investigate.
First checks:
If you scan the i2c bus, us the device visible?
Are pull up resistirs in place for the SDA SCL lines?

Is the I2C bus configured to use pin 25 and 26?

(image from - https://mischianti.org/esp32-pinout-specs-and-arduino-ide-configuration-part-1/)
I2C is pin 21 and 22

I am using mfrc522 rfid so 21 22 already in use. Recommend pin 5v side.
Thank you for your quick response

@HARIS4820
But you can put multiple devices on one I2C bus as they all have (assumption) a different address.
You might need to use something like Wire1 and set
Wire1.begin(25,26)

i made small change in sample code
Wire1.begin(26, 25);  //  adjust pins if needed
Wire1.setClock(400000);
keyPad.begin();
while (keyPad.begin() != true) {
delay(1000);
Serial.println("Attempting to communicate with keypad");
WebSerial.println("Attempting to communicate with keypad");
}
i connected i2c and keypad. and i also reboot multiple times. i am using i2c with lcd also. i am getting result

I a

I am using this i2c.
https://robu.in/product/pcf8574t-i2c-i-o-extension-board/

I am using this i2c https://robu.in/product/pcf8574t-i2c-i-o-extension-board/

What is the address set by this pcf8574 module?
Do you use that in your code?

const uint8_t KEYPAD_ADDRESS = 0x38;
I am using this in sample code

Does that address 0x38 match the address set by the jumpers on the board?
 How to find 0x38 matching or not?

I call keypad address and wire1. How to find 0x38 matching or not?

You need to use an I2C scanner.
Connect only the PCF8574 to the default Wire bus (21, 22) and connect no other devices.
Run the I2C scanner
Check my library - https://github.com/RobTillaart/I2C_SCANNER - in the examples.

I find bus address on 32. Thank you so much for your support

I tried scanner minimal sample code.
I change my code
const uint8_t KEYPAD_ADDRESS = 0x38;
To
const uint8_t KEYPAD_ADDRESS = 0x32;
But still facing same issue

32 is the decimal value
Use 0x20

I changed the code to
const uint8_t KEYPAD_ADDRESS = 0x20;
And still facing same issue.
Thank you for your continuous support.

Can you try the example I2Ckeypad_Wire1_ESP32.ino and post the output?

change address to 0x20  (line 16)
change pins as needed (line 30)

Now working perfectly.
Thank you
Thank you so much for your guidance.


Keyboard hot keys unresponsive in awesome

I installed trusty with e17 and awesome. when I enter awesome the keyboard search key wont
respond (Mod4+Enter, etc..)

Hello, just installed e17 on a Acer CB3 131 chromebook.
Everything works like a charm except for the hotkeys (volume, brightness, etc.)
I can't seem to be able to get key binding to work.  Same thing, I cannot change Edge settings...
Any clue ?


What does the flag "is_Dell" in bins.NmtBin exaclty do?

Hi, I'm using Namaster to calculate the power spectrum of a masked map, for example,  with Nsize = 128. And I will get negative value for the second bin even when I set nlb=50.
But when I turn on the is_Dell, the negative values will disappear. However, to my knowledge, is_Dell only differs by multiplying with a ell*(ell+1)/2/pi, which will not affect the sign of the bandpowers.
Could you give a comment for this phenomenon?

@yaojian95 by weighting the pseudo-C_ells differently before mode-decoupling, the structure of the mode-coupling matrix changes a bit, and the result can actually change. This tends to be particularly helpful for red steep spectra, since this weighting essentially whitens the pseudo-C_ells.


Add support for Pronto Ruby linter

Is your feature request related to a problem? Please describe.
It appears that super-linter does not support linting only lines that have changed and has no plans to per this issue: https://github.com/super-linter/super-linter/issues/219
But this is something that we have really found useful working with a large legacy codebase that we can fix incrementally, and it is fully supported with Rubocop if you use Pronto: https://github.com/prontolabs/pronto
Describe the solution you'd like
Would you consider supporting Pronto within super-linter?  My understanding is that it can be used for running Rubocop or Flay, but Rubocop is the one that is already supported by super-linter.

Yeah, that sounds reasonable to me that we could support linting only diffed lines in in Ruby. I imagine that would need to be a configuration option though.


Download task fails with NoSuchFieldError

I am attempting to use the download task and it fails with NoSuchFieldError. It would appear that for some reason the Apache HttpComponents are screwy. I'm not sure to tell which version of is in use, though. It is unclear to me if this is a problem with my build or with the download plugin.
I have tried with both Gradle 4.9 and 4.10. Both fail with the same error.
Caused by: java.lang.NoSuchFieldError: INSTANCE
        at org.apache.http.conn.ssl.SSLConnectionSocketFactory.<clinit>(SSLConnectionSocketFactory.java:146)
        at org.apache.http.impl.client.HttpClientBuilder.build(HttpClientBuilder.java:964)
        at de.undercouch.gradle.tasks.download.internal.DefaultHttpClientFactory.createHttpClient(DefaultHttpClientFactory.java:86)
        at de.undercouch.gradle.tasks.download.internal.CachingHttpClientFactory.createHttpClient(CachingHttpClientFactory.java:43)
        at de.undercouch.gradle.tasks.download.DownloadAction.executeHttpProtocol(DownloadAction.java:247)
        at de.undercouch.gradle.tasks.download.DownloadAction.execute(DownloadAction.java:205)
        at de.undercouch.gradle.tasks.download.DownloadAction.execute(DownloadAction.java:157)
        at de.undercouch.gradle.tasks.download.Download.download(Download.java:90)
        at org.gradle.internal.reflect.JavaMethod.invoke(JavaMethod.java:73)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.doExecute(StandardTaskAction.java:46)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:39)
        at org.gradle.api.internal.project.taskfactory.StandardTaskAction.execute(StandardTaskAction.java:26)
        at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:801)
        at org.gradle.api.internal.AbstractTask$TaskActionWrapper.execute(AbstractTask.java:768)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter$1.run(ExecuteActionsTaskExecuter.java:131)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:300)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor$RunnableBuildOperationWorker.execute(DefaultBuildOperationExecutor.java:292)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.execute(DefaultBuildOperationExecutor.java:174)
        at org.gradle.internal.operations.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:90)
        at org.gradle.internal.operations.DelegatingBuildOperationExecutor.run(DelegatingBuildOperationExecutor.java:31)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeAction(ExecuteActionsTaskExecuter.java:120)
        at org.gradle.api.internal.tasks.execution.ExecuteActionsTaskExecuter.executeActions(ExecuteActionsTaskExecuter.java:99)
        ... 31 more

I wrote a simple build that uses the basic functionality of the download plugin and it works with Gradle 4.9. So this is obviously a problem with the Gradle build files we are using.
I cannot share the full build that is failing, but I will attempt to replicate the problem in my sample build. If I manage to do so I will let you know.

Thanks for reporting the issue. I did some refactoring and I think I finally solved the issue. If you like, you can try the latest snapshot. Use the following code to add it to your build file:
buildscript {
    repositories {
        jcenter()
        maven {
            url "https://oss.sonatype.org/content/repositories/snapshots/"
        }
    }
    dependencies {
        classpath 'de.undercouch:gradle-download-task:4.0.0-SNAPSHOT'
    }
}

apply plugin: 'de.undercouch.download'

Any feedback on whether this new version works for you or not would be appreciated. Thanks.

Hey, thank you! I just tested out 4.0.0-SNAPSHOT and it seemed to resolve this issue for me. I was seeing the same stacktrace. Thanks!

Any chance of a new release soon? :) Would love to not have to depend on a snapshot version!

gradle-download-task 4.0.0 has just been released.


[ButtonGroup] Fix typings for disabled classes property

[x] I have followed (at least) the PR section of the contributing guide.

Closes #18272

This fixes #18272

@oliviertassinari thanks for fixing the blank line

@xZliman Thanks


UnknownPacket139 and UnknownPacket147 are incoming packet not outgoing

All is in the title, as a side effect it desync both cipher for implementation using the msg type to get the right in/out cipher. I don't think it's a problem for your.

Closed by: https://github.com/X-com/RealmShark/commit/b770b03474285f30705d0e0e8f99d0ce4e8517dd


Fix New-DBADirectory

Type of Change

[x] Bug fix (non-breaking change, fixes #7161 )
[ ] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
Fix bug to allow creating folders on more than 1 server.
Approach
iterates across all servers passed to the -sqlinstance parameter
Commands to test
$server1 = '10.95.XX.XXX'
$server2 = '10.95.XX.XXX'
New-DbaDirectory -SqlInstance $server1,$server2 -Path "C:\diagnostics" -Verbose

Hi, thanks for the pull request. I updated the text so that the issue is linked correctly.
And one more thing: All variables (except parameters) start with a lowercases - so it should be "$server" instead of "$Server".

Hi, thanks for the pull request. I updated the text so that the issue is linked correctly.
And one more thing: All variables (except parameters) start with a lowercases - so it should be "$server" instead of "$Server".

I'm new to PR creations, so thanks for the guidance on how to properly format them.

No problem. I was in your position just some months ago.

Is there something I need to do regarding the failed AppVeyor build check on this PR?

Is there something I need to do regarding the failed AppVeyor build check on this PR?

Not really, sometimes they fail. But you can change $Server to $server and commit this - then there will be another test run.

Is there something I need to do regarding the failed AppVeyor build check on this PR?

Not really, sometimes they fail. But you can change $Server to $server and commit this - then there will be another test run.

I just changed and committed the changes.

Hi @GLoeffler14 ,
that change solves the issue, thanks for that. I have only one more thing: The parameter "-SqlCredential $SqlCredential" is not needed anymore, because with $server we already have a connection to the instance under the account of $SqlCredential. So this parameter would not be used - and I think we should not have code in there that is not beeing used.

Hi @GLoeffler14 , for your info: @potatoqualitee (Chrissy LeMaire) will have a look, too - and then probably merge it into the next version.

Thank you for the approval @andreasjordan, good to see you. And thank you so much for the fix @GLoeffler14 🥳


Donation link

Per #1 it would be great to have the option to donate to the maintainer/author.

Hello!
Thank you!
Added a link to Readme (also to Chrome Web Store description, it'll appear there when the version 1.0.0 is approved by the mods): https://buymeacoff.ee/everyonesdesign


Website JavaScript errors

Are you experiencing an issue with...

[x] shields.io
[ ] My own instance
[ ] gh-badges NPM package

:beetle: Description
When I search for a package by entering its URL, the page gets blank and dies. There are multiple JavaScript errors visible in the browser console. Firefox and Chrome are affected. The page is unusable.
I'm not including the details because you can easily check that yourself and get all the details you need.
Ad blocker disabled, no other browser extensions affecting the page.
:link: Link to the badge

:bulb: Possible Solution

Thanks @ygoe. This is a duplicate of #3033 so going to close this one


README contains some links to /lib instead of lib/src/*

Many of the links refer to the files in the lib folder and not the ones in the src folder. That makes it difficult for the readers as they will have to open yet another file, if they want to see the implementation.

Thank you for pointing that out – we should always show the lib/src file


Add jam version command

What happened?

What were you attempting to do?
Find out which version of the jam CLI I had installed on my workstation

What did you expect to happen?
jam version and/or jam --version and/or jam -v would return the semver version of the installed CLI.

What was the actual behavior? Please provide log output, if possible.

jam --version
Error: unknown flag: --version
Usage:
  jam [command]

Available Commands:
  completion          generate the autocompletion script for the specified shell
  help                Help about any command
  pack                package buildpack
  summarize           summarize buildpackage
  update-builder      update builder
  update-buildpack    update buildpack
  update-dependencies updates all depdendencies in a buildpack.toml according to metadata.constraints

Flags:
  -h, --help   help for jam

Use "jam [command] --help" for more information about a command

Checklist

[ ] I have included log output.
[ ] The log output includes an error message.
[ ] I have included steps for reproduction.

I think we could do this with build time arguments in Go then we could continue to have a self contained binary.


native English speaker --> same, but Russian speaker without the English accent ???

I have an original dataset of a native English speaker. I want to train the model for use in Russian. now I can't generate TTS using trained model in Russian because I hear that English accent and it doesn't sound good. Can I correct the accent and advise what exactly I should do to get the desired result? Thanks.

use index file from another model where the native speaker is Russian

use index file from another model where the native speaker is Russian

Thank you so much! I will try to do like you said. Maybe I can ask you two more questions - What optimal amount of 10s segments for dataset for RVCv2 rmvpe_gpu and what optimal amount of epochs? (on my rtx3060 1 epoch training took ~12 min) Bless you, my friend.

use index file from another model where the native speaker is Russian

Thank you so much! I will try to do like you said. Maybe I can ask you two more questions - What optimal amount of 10s segments for dataset for RVCv2 rmvpe_gpu and what optimal amount of epochs? (on my rtx3060 1 epoch training took ~12 min) Bless you, my friend.

The more diverse the segments, the more accurate the model. Usually people take 10-20 minutes of data for a test and 50-100 epochs to listen to the approximate result.
If they are satisfied, they leave the same amount of data or add more (Personally, I add more) and continue training. From 200 epochs to infinity.
But at one point the model reaches its peak and it is pointless to continue training. To keep track of when that moment comes, you'd better learn to use TensorBoard. Here is the good video about it https://www.youtube.com/watch?v=P0M7PAsG1fk . Actually this guy makes good videos on the subject of neural networks and AI, so check out his other videos as well
Also dude, 12 minutes is too long. On your GPU the epoch shouldn't take more than a minute, look at your settings, something is obviously wrong


create vcluster instance in session

This PR creates a vcluster instance in a session.
Fixes #2839
Signed-off-by: Chanwit Kaewkasi<EMAIL_ADDRESS>

❔ Just a question, why is OpenRepository  and GetRemoteURL preferred naming in Go over ParseGitRemote and ParseRemoteURL? To hide implementation details, like we are not really interested in how we get them, we just need the result?

@opudrovs reverted during the rebase


provide a reliable way to create python images

The provided example for creating a Python image is very complex as it requires a micro + a module for it to work:
https://github.com/aspect-build/bazel-examples/blob/main/oci_python_image/workaround_rules_pkg_153/runfiles.bzl
https://github.com/aspect-build/bazel-examples/blob/main/oci_python_image/py_image_layer.bzl
This seems like an unreliable workaround - what if the code in the example changes? Is the user supposed to watch the repository and update the code if that happens?
I believe a proper solution would be to bake this into a rule within rules_oci.

Principled fix for this is to fix rules_pkg to lay out proper runfiles trees. the macro is basically a workaround for rules_pkg not rules_oci. Then you wouldn't need all this userspace macros.
That said one of our goals for rules_oci is to not get involved in the business of providing language specific image rules. https://github.com/bazel-contrib/rules_oci#bazel-rules-for-oci-containers

@thesayyn is there an open issue for this in rules_pkg?
I see js_image_layer exists within rules_js, did you consider adding such a rules to rules_python?

js_image_layer basically a fancy pkg_tar so ideally you shouldn't need language specific generators like js_image_layer.

did you consider adding such a rules to rules_python?

i haven't. that'd be probably maintenance burden on me/rules_oci given that rules_python has it's own problems they need to deal with.

closing this in favor of #254


"An error has occurred while trying to read arguments. Did you specify the channel?"

I have specified the channel in the code and whatever i do i can't seem to get this to work! Plz help!

Yeah i'm fairly new to python as well trying to figure it out

You are not supposed to specify the channel in the code, you are supposed to pass the channel as an argument. For example: python2 twitch-viewer.py channel

for being an absolute noob how would i do this?