What is the milestone of this spec?

I am aware there are definitely plenty details to discuss for this spec. But, I suggest we can do some works in implementation level. For do that, we should set a milestone, like 0.1 or 1.0, as you like. So the tracer/APM-agents can try to implement the spec, and find out what is next for everyone.
@adriancole @bogdandrutu @SergeyKanzhelev

I'm a fan of having a milestone list available this week and then locking down v0.1 at the November meeting

We have a milestone defined here:
https://github.com/TraceContext/tracecontext-spec/milestones
Please edit if you want to have some explicit things there.

Although @adriancole has invited me, but I am sure whether can be at Sydney or not.
@mtwo @bogdandrutu @SergeyKanzhelev IMHO, I think the spec is ready for 0.1 release. Version issue #32 is still debatable, and properties of a Correlation Context value are not high priority things.
FYI, the certain length of traceid and spanid , #19  is the last block for skywalking.

@bogdandrutu @wu-sheng @adriancole @SergeyKanzhelev @bhs @cce @jkowall @yurishkuro @vancem @abhiksingh @rakyll @mattklein123 @codingfabian @jkowall and anyone else following along, here's my proposal for a first release:
I've created a milestone for v0.1.0, which represents the first release of TraceContext. v0.1.0 will be very basic, and will include:

An HTTP header name
Trace ID
Span ID
An options bitfield
An encoding format for the header and its components

I also propose that we follow up with support for baggage and correlation context in subsequent versions. I don't think that we should include them in the first release as they're (somewhat) less important than aligning on an ID space and encoding format, and because we can add them without making breaking changes.
It looks like the biggest / most opinionated open issue is #19, so I propose that we spend the next week attempting to solve it by consensus, and that we vote on it and any other open issues on November 2nd or 3rd. @adriancole had already organized one of his regular tracing workshops in Sydney at this time, which seems like a good forum for the discussion and vote as a number of the participants will be there and because the timezone is quite friendly to most of the participants.
Does this seem reasonable? I think it's a good balance of expedience and fairness, but I'm happy to take feedback!

+1 from me. Let's do this!

@SergeyKanzhelev fair enough, let's vote on adopting both at the same meeting? Sound good?

Please reserve the voting for github, not everyone can make the meeting.

@mtwo As I have feedback to @adriancole , because I can't have enough time to get Aus VISA, I have to absent the meeting. But skywalking is interesting in this.

Sounds good Yuri and Sheng, let’s use the meeting / video conference for discussion and then vote on GitHub.
I’m thinking that one vote per vendor / OSS project probably makes the most sense but am open to feedback. Sound good? :)

From: 吴晟 Wu Sheng <notifications<EMAIL_ADDRESS>Sent: Sunday, October 22, 2017 4:08 PM
Subject: Re: [TraceContext/tracecontext-spec] What is the milestone of this spec? (#31)
To: TraceContext/tracecontext-spec <tracecontext-spec<EMAIL_ADDRESS>Cc: Morgan McLean <morgan_mclean<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>@mtwohttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fmtwo&data=02|01|morgan_mclean%40hotmail.com|5d1f898425414f24551808d519bae5a1|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636443212854144288&sdata=n0TIz7INS2ramnIsxX5u2Mt2dnQmN8e0NHHnzDCh%2B3E%3D&reserved=0 As I have feedback to @adriancolehttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fadriancole&data=02|01|morgan_mclean%40hotmail.com|5d1f898425414f24551808d519bae5a1|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636443212854144288&sdata=bd%2BoB%2FCUGvSoxoIdZZSYjB%2BzE3ZDI81R6HyToG8BQYo%3D&reserved=0 , because I can't have enough time to get Aus VISA, I have to absent the meeting. But skywalking is interesting in this.
―
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FTraceContext%2Ftracecontext-spec%2Fissues%2F31%23issuecomment-338529532&data=02|01|morgan_mclean%40hotmail.com|5d1f898425414f24551808d519bae5a1|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636443212854144288&sdata=nbZxcc2Oum3ZovLY2BhKXZTRCAyNP8nolSnPPt%2FfkCo%3D&reserved=0, or mute the threadhttps://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FABF1q9lFi7AHj_6P3F74us8syJJ0H8YEks5su_UCgaJpZM4Pyp9P&data=02|01|morgan_mclean%40hotmail.com|5d1f898425414f24551808d519bae5a1|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|636443212854144288&sdata=014wmYThoe8CqQmBOE1OLJsgAwuKOiLIc55FCjcAtnQ%3D&reserved=0.

I think its a good first step. But until we talk about how to identify IDs from other vendors and link to their parts of the trace, we will potentially cause new problems where trace ids are mistaken.
This then also brings up how to preserve foreign ids (many tracers will be unable to apply their internal optimizations for trace id storage (like using primitive types))

@bogdandrutu @adriancole @SergeyKanzhelev @AloisReitbauer @abhiksingh @tylerbenson
At the Sydney meeting, we discussed the following:

A trace-context header, which is composed of fixed length ordered fields for performance. These fields include a version, trace ID, span ID, and a bitfield indicating things like the sampling decision.
A correlation-context header, which allows additional fields to clarify the trace-context. This header is similar to baggage in the sense that it is a set of key value pairs, but it is only written to by vendor / library code - end users should not be able to directly set its values and make it a core part of their application logic. This field has a maximum size, beyond which it will be dropped by instrumentation systems.

Correlation context will likely be used to hold things like epoch seconds (Amazon) or hierarchical IDs (Microsoft). Vendors should prefix their key names to avoid collisions.
What we need now is:

Encodings and some basic rules like max sizes for the proposed trace-context and correlation-context formats. I'm not the right person to provide these, so I'm arbitrarily nominating @adriancole and @bogdandrutu to either produce a proposal or to deputize someone else. If someone else is willing to do it, please reply in this thread.
A vote on GitHub. I can oversee this once the first step is complete.

I'm currently on vacation but I'll check in on this thread to respond to questions or kick things if we aren't making progress.

Milestones are now described in charter for working group


Consider adding VariableType to metadata

The Variable Catalog tends to get filled up with descriptive-type variables (site location, treatment ID, block ID, latitude, longitude, etc.) where most researchers are likely looking for measurement-type variables (stand count, biomass, percent carbon, volumetric water content). We should consider providing a way to differentiate these variable types for better filtering.
This can easily get out of hand (see here and here).
Best option is to be consistent with other such filters (e.g. zone, processing, quality control) and allow variable types to be defined in the app-config.json file.
We also will need to provide default values. Maybe follow statistics and go with the upper level: Quantitative/Numeric, Qualitative/Categorical? Or go with an extra step and do: Discrete, Continuous, Nominal, Ordinal.
Keeping things simple (for speed-to-metadata): Numeric, Categorical.

Take a cue from dimensional modeling. A "dimension" describes "who, what, where, when, why, and how". A "metric" is a quantitative measurement.
I think it's safe to say the context of the dataset can determine what is a dimension vs a metric -- so we have some leeway here. For example, measuring crop height, "height" will be a metric. But if we are describing the height of a sensor then "height" will be a dimension.
Nominal and ordinal variables pose some confusion. There are arguments that ordinal vars can be considered continuous vars (https://www.frontiersin.org/articles/10.3389/feduc.2020.589965/full). So maybe we can handwave that. (although there are best practices that state "metrics" should allow the calculation of means, min, max, etc.)
I'm not sure about nominal though. Should we always treat those as dimensions? If so, something like a management dataset, which is mostly nominal values, will pose an issue. Would we want a "drill type" or "tractorId" grouped with "plotId", "NearestTown", and other descriptive variables? Maybe this is fine?


Improve tests for manual register to use enums across the board

There are currently 72 usages of io.swagger.client.api.manualRegister in our test code that use bare Strings rather than enums for descriptor type. There are also six implementations of manualRegisterAndPublish such as that in WorkflowIT that take in Strings as parameters when they could use enums.
Improve these tests to use enums while preserving actual behavior for now
┆Issue is synchronized with this Jira Story
┆Issue Type: Story
┆Fix Versions: Dockstore 2.X
┆Sprint: Backlog
┆Issue Number: DOCK-1407

Related to this, remove the lower-case "cwl" and "wdl" from the DescriptorLanguage.java altogether so that maybe Openapi.yaml will stop changing.


use NuProcess in ceylon.process?

We should experiment with https://github.com/brettwooldridge/NuProcess in ceylon.process.

I haven't used NuProcess, but this sounds like a good idea, especially since ceylon.process seems to be vulnerable to java.lang.Process's tendency to block/deadlock if you don't service the I/O streams of the subprocess: https://docs.oracle.com/javase/8/docs/api/java/lang/Process.html


Documentation clean working towards release v1

Documentation update for v1 release
With the push towards the v1 release, documentation should be reviewed in and updated. In onboarding to the project I noticed that the model_signing docs are not current, as they utilize the upstream google model-signing repo instead of this one in the demo (see code).

Another thing to do is have documentation for the API. Note: I've created a tracking issue for auto-generation / update of docs https://github.com/sigstore/model-transparency/issues/209


do not support reverse layout

how to implement the behavior of LinearLayoutManager reverseLayout with this library?

can anyone help me?


IteratingSystem before/after processing

I just came accross this issue after wondering how to do something before and after entities are being processed.
This is the solution:
@Override
    public void update(float deltaTime) {
        camera.update();

        batch.begin();

        batch.setProjectionMatrix(camera.combined);
        super.update(deltaTime);
        batch.end();
    }

It works, but it's not very intuitive because you have to know the implementation of IteratingSystem.update(...) and that it's just calling processEntity for each entity. I think before/after hooks for the processEntity method would be nicer.

overriding update method to add some pre/post process is very common. Adding some hooks would over-complexify things for no reason.


Review use of panic in datafusion-proto crate

Which issue does this PR close?

Closes #3318.
Rationale for this change

Refactor to get rid of explicit panics
What changes are included in this PR?

Are there any user-facing changes?

Codecov Report

Merging #3365 (0c6c593) into master (4c948a3) will decrease coverage by 0.00%.
The diff coverage is 20.00%.

@@            Coverage Diff             @@
##           master    #3365      +/-   ##
==========================================
- Coverage   85.51%   85.50%   -0.01%
==========================================
  Files         294      294
  Lines       54120    54122       +2
==========================================
- Hits        46279    46277       -2
- Misses       7841     7845       +4

Impacted Files
Coverage Δ

datafusion/proto/src/bytes/mod.rs
82.75% <ø> (ø)

datafusion/proto/src/from_proto.rs
34.26% <ø> (ø)

datafusion/proto/src/to_proto.rs
48.42% <0.00%> (-0.47%)
:arrow_down:

datafusion/proto/src/logical_plan.rs
17.81% <100.00%> (ø)

datafusion/common/src/scalar.rs
84.71% <0.00%> (-0.07%)
:arrow_down:

datafusion/core/src/physical_plan/metrics/value.rs
87.43% <0.00%> (+0.50%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

Looks like there is a CI error on this PR.

Thanks @comphead. This is looking good. I left some comments.

@andygrove @alamb I dont get why cargo check keeps failing.... even on master branch.

@andygrove @alamb I dont get why cargo check keeps failing.... even on master branch.

I think the reason that https://github.com/apache/arrow-datafusion/runs/8218776681?check_suite_focus=true is failing is that there is some issue in code that is not normally run via cargo test.
In this case, the command that is failing is:
cargo check --workspace --benches --features avro,jit,scheduler,json

Does that fail locally for you?

Thanks @alamb
cargo test works fine locally. but cargo check --workspace --benches --features json does not even switching to main branch. Like some local cache exists. I'll try to get the repo clean copy

Sorry guys, I probably generated more commits than expected, the reason being is cargo check gives me not the same results as CI, even after cleaning the cache

@avantgardnerio I know you fixed a json proto build issue recently. Could you take a look at this PR to make sure you are happy with it?

Thanks @avantgardnerio for the review, please find the fixed PR


Frontend/Logout

@andriikaplanovskyi sorry, I wanted to add the ticket to beyond-secure, but I clicked the wrong project, after that, I moved it to beyond-secure! ou can close the ticket! thanks


[Bug]: add logo for category does not working

What happened?
Adding logo for category does not work
How to reproduce the bug
I uploaded an image for category logo but nothing saved to database.
I also tried uploading a logo for category in larazeus demo and the same bug exists.
Package Version
2.0.9
PHP Version
8.1
Laravel Version
10.21.1
Which operating systems does with happen with?
Windows
Notes
No response

hi all, can you test this and confirm if it's working?
https://github.com/filamentphp/filament/pull/8432#issuecomment-1715654443
did a quick test, and seems to fix the issue.

This should be fixed with the last release from filament
and it fixed in the demo too


Added paramterized tests for textanalytics and formrecognizer

SDK live tests plan to test over all available httpclients (e.g. netty, okhttp) and all service versions.
The PR is to enable tests to take the httpclient and service version as paramerized parameters from test framework.

/azp run java - textanalyzer - tests

/azp run java - formrecognizer - tests

/azp run java - textanalytics - tests

/azp run java - textanalytics - tests

/azp run java - formrecognizer - tests

/azp run java - textanalytics - tests

/azp run java - formrecognizer - tests

/azp run java - formrecognizer - tests


Game crashes in Release exports, no error in Debug (GDScript Pool*Array with type hinted from Array)

I have looked for a few other issues and while some might be the same, I have a repro project whereas those did not. It's not a minimal project, but it's easy enough to cause the bug with this project. It might be the same or very similar to https://github.com/godotengine/godot/issues/46533, not sure, as I didn't test it just with deleting nodes explicitly (mine happens on scene change).
Godot version:
3.3.stable, GLES2 for web exporting (but happens regardless of which system exported for)
OS/device including version:
macOS Catalina, 10.15.5, Radeon Pro 560X, also integrated Intel UHD Graphics 630
Issue description:
When switching scenes in my game while in release mode, the game often freezes. This happens regardless of which system I'm exporting for. It seems very little is listed in the Mac OS logs as well - I actually couldn't find anything. However, it looks like possibly the web export has a bit more information (but note the freeze is definitely not specific to the web build):

Steps to reproduce:

Clone and open the project
Export for any platform, without debug info (this is the most important part - it won't crash if you export with debug info); this even happens exporting from Mac to Mac.
Run the app from the exported package
Play single player
Move to the right with D or right arrow, jumping enemies with spacebar or left mouse click until you get to the door and touch the door with your snoot.

For my testing, I found this always froze on the next screen. Since it's picking scenes at random to send you to next, I don't think it's specific to my code, but it's possible, as I use an inherited root scene for each level.
Minimal reproduction project:
I don't have a minimal reproduction, just the big one. I'm not sure exactly what's causing it, but as it's a crashing bug, I think it's pretty important to include it here anyway:
https://github.com/WolfgangSenff/GOTMJam3

'function signature mismatch' is an error specific to web build.
Does it happen if you remove the randomizing part of the portal (to exclude the possibility that one of the scenes is corrupted itself)?

I'm not sure, but if that's specific to the web build, then maybe it's not actually useful for debugging, doh. It definitely happens on all other platforms as well. However, regarding the randomizing, none of the scenes are corrupted - used to go through them linearly and was still frozen. The randomization was only added toward the end.

I can't test the project, the Firebase plugin seems to have missing files:

Oh. I must have put that one into my gitignore. Ugh. Let me make a branch that removes it, as it's only used for multiplayer, sorry.

For now, if you want, you can grab that file from here: https://github.com/GodotNuts/GodotFirebase/blob/main/addons/godot-firebase/firebase/firebase.gd - it'll cause weird bugs not having the data in there, but only if you try multiplayer. Single player should be fine without the config stuff at the top.

Thanks, I can reproduce a segfault on Linux. I'll grab a stacktrace.

The crash also happens with 3.2.3-stable so it's not a recent regression.
Crashes here:
Thread 1 "godot.x11.opt.6" received signal SIGSEGV, Segmentation fault.
Variant::call_ptr (this=this@entry=0x4365510, p_method=..., p_args=p_args@entry=0x7fffffffc738, p_argcount=p_argcount@entry=0, r_ret=0x7fffffffc6d8, r_error=...) at core/variant_call.cpp:1165
1165                    funcdata.call(ret, *this, p_args, p_argcount, r_error);
(gdb) bt
#0  Variant::call_ptr (this=this@entry=0x4365510, p_method=..., p_args=p_args@entry=0x7fffffffc738, p_argcount=p_argcount@entry=0, r_ret=0x7fffffffc6d8, r_error=...) at core/variant_call.cpp:1165
#1  0x00000000007f6355 in GDScriptFunction::call (this=0x3ff6b50, p_instance=p_instance@entry=0x4365bc0, p_args=p_args@entry=0x7fffffffc9f8, p_argcount=p_argcount@entry=1, r_err=..., p_state=<optimized out>)
    at modules/gdscript/gdscript_function.cpp:1086
#2  0x00000000007b80f0 in GDScriptInstance::call_multilevel (this=0x4365bc0, p_method=..., p_args=0x7fffffffc9f8, p_argcount=1) at modules/gdscript/gdscript.cpp:1224
#3  0x0000000000ec1d07 in Node::_notification (this=0x4365690, p_notification=<optimized out>) at scene/main/node.cpp:69
#4  0x0000000001384f98 in Node::_notificationv (p_reversed=false, p_notification=16, this=0x4365690) at ./scene/main/node.h:46
#5  CanvasItem::_notificationv (p_reversed=false, p_notification=16, this=0x4365690) at ./scene/2d/canvas_item.h:166
#6  Node2D::_notificationv (p_reversed=false, p_notification=16, this=0x4365690) at ./scene/2d/node_2d.h:38
#7  CollisionObject2D::_notificationv (p_reversed=false, p_notification=16, this=0x4365690) at ./scene/2d/collision_object_2d.h:39
#8  PhysicsBody2D::_notificationv (p_reversed=false, p_notification=16, this=0x4365690) at scene/2d/physics_body_2d.h:43
#9  KinematicBody2D::_notificationv (this=0x4365690, p_notification=16, p_reversed=<optimized out>) at scene/2d/physics_body_2d.h:290
#10 0x0000000001caeda4 in Object::notification (this=0x4365690, p_notification=16, p_reversed=<optimized out>) at core/object.cpp:929
#11 0x0000000000ee2dda in SceneTree::_notify_group_pause (this=0x2ac1370, p_group=..., p_notification=16) at scene/main/scene_tree.cpp:993
#12 0x0000000000ee6ed1 in SceneTree::iteration (this=0x2ac1370, p_time=<optimized out>) at scene/main/scene_tree.cpp:486
#13 0x00000000005961dd in Main::iteration () at main/main.cpp:2100
#14 0x0000000000578731 in OS_X11::run (this=this@entry=0x7fffffffce00) at platform/x11/os_x11.cpp:3641
#15 0x0000000000566035 in main (argc=3, argv=0x7fffffffd6d8) at platform/x11/godot_x11.cpp:56

CC @RandomShaper (in case you're interested in this kind of release-only issue).

In case anyone needs the branch upon which I've removed the Firebase-related error that Akien reported above, here you are: https://github.com/WolfgangSenff/GOTMJam3/tree/remove-firebase-for-bugfix

Tested with 3.4-stable, this is still reproducible.

I've found the issue.
This is a simplification from Leaf.gd:
var points := [] setget set_points

func set_points(value):
    points = value

func _physics_process(delta: float):
    if ...:
        points.pop_front()

points is being assigned a PoolVector2Array from outside (i.e., set_points() is called with a PoolVector2Array value). PoolVector2Array doesn't feature a pop_front() method, so what happens at runtime is somewhat expected.
However, on a debug build, because of points being statically typed as Array. the points = value assignment forces the PoolVector2Array to be converted to an Array. Therefore, no error happens there, because Array has pop_front().
The difference of behavior across debug and release is the bug. I'm not sure if what we want is that the coercion to Array happens on release as well, or that it doesn't happen on either.
This little scripts shows the magical change of type on debug:
var a = PoolVector2Array([ Vector2(1, 2), Vector2(3, 4) ])
var b := []
b = a
pass # Set a breakpoint here: 'a' will be a PoolVector2Array, 'b' will be an Array

CC @vnen

@RandomShaper - I actually didn't see this until just now. You are some sort of superman for finding this. That is absolutely baffling, as well as impressive debugging!

The difference of behavior across debug and release is the bug. I'm not sure if what we want is that the coercion to Array happens on release as well, or that it doesn't happen on either.

I think that the appropriate solution would be to raise an error in debug here. We use strict typing for a reason, and we don't allow coercion a lot of time when it would've been preferred by some users (see int vs float debacles). Implicit behavior here hides a bug in code, crash or not. So yeah, should be an error as early as possible.

And a huge thank you for the investigation @RandomShaper! We just ran into this issue ourselves with a project, and it's a very nasty bug to figure out. This helps immensely.

I think that the appropriate solution would be to raise an error in debug here. We use strict typing for a reason, and we don't allow coercion a lot of time when it would've been preferred by some users (see int vs float debacles). Implicit behavior here hides a bug in code, crash or not. So yeah, should be an error as early as possible.

I'm not sure if this comment is 3.x specific, but at least on master, the existing code suggests that when the destination is statically typed (hard), a conversion should happen on assignment unless the source is also the same static (hard) type. If conversion is not possible, that's when it's an error. (Though there are cases for emitting warnings even when conversion is possible.)
Relevant:
https://github.com/godotengine/godot/blob/9f058674acebf9a7a0704cdbc26dc9f6d853b16e/modules/gdscript/gdscript_vm.cpp#L1096-L1121
https://github.com/godotengine/godot/blob/9f058674acebf9a7a0704cdbc26dc9f6d853b16e/core/variant/variant.cpp#L682-L706
So I believe the appropriate solution would be making the release export consistent with debug. But I don't know if there are design differences in this case for 3.x

I'm not sure if this comment is 3.x specific

The comment is not 3.x specific, but the reported crash is. We haven't tested what happens in master, and GDScript 2 is too buggy for the moment to make a fair assessment anyway. But I don't think that the conversion described by Pedro is expected or desired when you use types. Like I've said, it hides a bug in code, which strict typing is supposed to prevent.
We already act very strictly when using floats and ints together and actively avoid any implicit behavior. We also avoid coercion when adding a variant to a string, even though you could implicitly convert it to a string and concatenate (conversion works perfectly fine with string formatting). It's not very relevant if this behavior has been done on purpose or not, as it introduces an inconsistency with how we handle type coercion. To the point where it leads to a crash because that inconsistency wasn't accounted for in release builds.
That said, making release builds coerce types the same way as debug build does would solve the problem with the crash specifically. I still want to underline that this hides a bug in code from the developer. So at the very least we should reconsider it for Godot 4 while we can break compatibility. In 3.x we can accept coercion in release to avoid crashing, though I'd say it's still undesired and should be fixed properly.

But if the design intention is to do conversion when assigning to a hard-typed destination (unless the source is the same hard-type), then it's not "hiding a bug in code from the developer". With this design, the semantics of assigning to a hard-typed variable do include type conversion.
What you mention about strings is in fact accounted for within the difference between Variant::can_convert and Variant::can_convert_strict, where the strict version of the two defines all the allowed conversions when assigning to a hard-typed variable. Here's the 3.4 version of these functions for reference: https://github.com/godotengine/godot/blob/b4d7d8766670e2e6380d7d76798f81f840ffe168/core/variant.cpp#L389

We already act very strictly when using floats and ints together and actively avoid any implicit behavior.

With regards to assignments, that doesn't seem to be the case. The only time such assignment is prevented seems to be const initializations (which can be argued not to be an assignment itself).
Conversion when assigning to hard-typed variables is something I'm very fond of about GDScript. If changing that is desired by some, then maybe it should be a proposal. Preventing it would also hurt safe polymorphism / make it very cumbersome to write.

With regards to assignments, that doesn't seem to be the case.

I wasn't talking about assignments there specifically, sorry. Just general cases of possible coercion that the users run into from time to time.

But if the design intention is to do conversion when assigning to a hard-typed destination (unless the source is the same hard-type), then it's not "hiding a bug in code from the developer".

It very much is, as evident by the fact that only after reading that investigation by Pedro did we realize that we were in fact assigning one type to a variable that is supposed to hold another. It was a relic of old code being refactored, skipped past the developer who did the refactoring, and we were none the wiser. Coercion made us think the code was safe, when it wasn't. IMO crash is irrelevant here, so even if it didn't crash I would still consider that a problem.

Conversion when assigning to hard-typed variables is something I'm very fond of about GDScript. If changing that is desired by some, then maybe it should be a proposal. Preventing it would also hurt safe polymorphism / make it very cumbersome to write.

Fair. Then, at the very least, it should be a warning that you can disable or silence per line. We have a few such warnings when ints and floats are, again, involved. When you implicitly cast you do something potentially unsafe.
And I'm not sure I agree with being very cumbersome to write. We have explicit casting, and we have overloaded constructors that would extend your code by a few characters, but would make the intended logic very clear.

Fixed by #53296.


make build failed

.env is below:
CUDA_VERSION=10.2
CUDNN_VERSION=8
PYTHON_VERSION=3.7
TORCH_CUDA_ARCH_LIST=8.0
PYTORCH_VERSION_TAG=v1.11.0

make build met error:
 > [internal] load metadata for docker.io/nvidia/cuda:11.2-cudnn8-devel-ubuntu18.04:
------
failed to solve: rpc error: code = Unknown desc = failed to solve with frontend dockerfile.v0: failed to solve with frontend gateway.v0: rpc error: code = Unknown desc = docker.io/nvidia/cuda:11.2-cudnn8-devel-ubuntu18.04: not found
Makefile:55: recipe for target 'build' failed

seems nvidia changes image names?

@Jack47 Hello. It appears that you are trying to pull "cuda:11.2-cudnn8-devel-ubuntu18.04", which does not exist.
For some reason, the CUDA_VERSION variable has been set to CUDA_VERSION =11.2, which is unavailable.
Please set the variable CUDA_VERSION =10.2 on your terminal and in all default variables.

@Jack47 Hello. It appears that you are trying to pull "cuda:11.2-cudnn8-devel-ubuntu18.04", which does not exist. For some reason, the CUDA_VERSION variable has been set to CUDA_VERSION=11.2, which is unavailable. Please set the variable CUDA_VERSION=10.2 on your terminal and in all default variables.

yes, change it to 10.2 works, but I want to use 11.2 to build pytorch, seems nvidia changed it's naming convention: https://hub.docker.com/search?page=1&name=cudnn8&q=11.2+cudnn8, https://gitlab.com/nvidia/container-images/cuda/blob/master/doc/unsupported-tags.md

The versioning system for CUDA was changed to follow semantic versioning as of CUDA 11.
To use the latest version of CUDA 11, please use CUDA_VERSION=11.2.2.

CUDA_VERSION=11.2.2

GREATE thanks, it works.


Snippets: documentation should link to syntax

Refs #15873
Consider having a link from the snippets api docs to the syntax described here https://github.com/Microsoft/vscode/blob/master/src/vs/editor/contrib/snippet/common/snippet.md#L2

That will happen once we have it on the website


Debug logging of requests

For debugging would be useful to log the request and response received. Should support per request logging and default logging for all requests.

This is very useful feature. Cannot wait for it to be implemented.

I agree, this would be a great feature!

This could be potentially achieved using https://github.com/request/request-debug

Guys, just committed an initial approach to debugging. If you could try it out and see what you think before I push to NPM. See https://github.com/dareid/chakram/blob/e206665307150bd4d13300238307808ca6891c1b/lib/debug.js for details of the two new methods on the chakram object.

Deployed in v1.3.0

Is there anyway to make it expand out all objects? As per my example below I get just the type identifier of Object not the actual expanded object:
{ response:     { debugId: 1,      headers:        { 'content-type': 'application/json',         'access-control-allow-origin': '*',         vary: 'origin',         'cache-control': 'no-cache',         'content-length': '541',         'accept-ranges': 'bytes',         date: 'Tue, 09 May 2017 13:30:32 GMT',         connection: 'close' },      statusCode: 200,      body:        { total: 1,         count: 1,         page: 1,         perpage: 10,         cache: false,         items: [Object] } } }

you can specify the logging function to use as an argument to start debug, see http://dareid.github.io/chakram/jsdoc/module-chakram.html#.startDebug. This way you can adjust to log what ever information is important to you.
If you come across a logging function which is generally useful feel free to raise a PR :)


chore: upgraded to ionic/storage 3.0.6

closes #2922
This PR updates our apps for ionic/storage 3.0.6. Local storage appears to work fine with these changes e.g., simulation runs are storage in the browser and read out. Tests seems to pass with ng run ....
However, one of the dependencies appears to break nx. On my machine, nx run ... fails with errors such as below although ng run ... succeeds.
(node:29709) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'type' of undefined
    at Object.isNpmProject (/home/jonrkarr/Documents/biosimulations/node_modules/@nrwl/workspace/src/core/project-graph/operators.js:52:20)
    at ProjectHasher.<anonymous> (/home/jonrkarr/Documents/biosimulations/node_modules/@nrwl/workspace/src/core/hasher/hasher.js:244:41)
    at Generator.next (<anonymous>)
    at /home/jonrkarr/Documents/biosimulations/node_modules/tslib/tslib.js:117:75
    at new Promise (<anonymous>)
    at Object.__awaiter (/home/jonrkarr/Documents/biosimulations/node_modules/tslib/tslib.js:113:16)
    at /home/jonrkarr/Documents/biosimulations/node_modules/@nrwl/workspace/src/core/hasher/hasher.js:241:79
    at new Promise (<anonymous>)
    at ProjectHasher.<anonymous> (/home/jonrkarr/Documents/biosimulations/node_modules/@nrwl/workspace/src/core/hasher/hasher.js:241:50)
    at Generator.next (<anonymous>)
(node:29709) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:29709) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Looks good.

I fixed the above error on my machine.

:tada: This PR is included in version 5.1.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


font visible in input in contact us form

fixed the issue #500
Description
This PR addresses the issue of invisible input text on the Contact Us form.
Changes Made:-
Modified [index.html].
Added/Updated [specific elements, classes, or styles].
initial preview
https://github.com/Its-Aman-Yadav/Community-Site/assets/149527268/afe85db1-9c98-4bf3-b4e7-6f75821ae97e
final preview
https://github.com/Its-Aman-Yadav/Community-Site/assets/149527268/db4962c1-8285-44fb-861f-5550e1abeb06

Not assigned to you

Why not assigned? My repo?
On Sat, 1 Jun, 2024, 8:09 pm Aman Yadav, @.***> wrote:

Not assigned to you
—
Reply to this email directly, view it on GitHub
https://github.com/Its-Aman-Yadav/Community-Site/pull/513#issuecomment-2143471163,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDUZVZCNEABTPWU35G6M6ILZFHMKPAVCNFSM6AAAAABITKM6R2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGQ3TCMJWGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Read operation optimisations

Currently information from IGC is typically retrieved by a double-search: a first search (by ID, with no properties) to see what type of asset is being requested, then using this type information to determine what properties to include in the follow-on search, and then a second search (by ID, including those properties).
(This is due to the fact that doing searches limited to the properties of interest is generally more performant than retrieving an asset and all of its properties when many of those properties will not actually be used.)
Ideally we could reduce this to a single up-front search; however, to do so we would need to know the IGC asset type of the RID being requested. There unfortunately isn't a way to determine this based on the RID itself...
The simplest solution would probably be to further extend the GUIDs that IGC returns to embed the IGC data type as well -- which would allow us to then use this to do the lookup in a single search, by avoiding the need for the initial property-less by-ID search to determine the data type (from which to then choose the properties to retrieve).

Agreed on 22/10 to go ahead with this an see if it is a workable pattern

Quick review of various scenarios and it looks like these are probably now about as optimised as can be easily achieved -- one remaining open point to track in #101 regarding frequently-used things like classifications.


Problem with debugging python

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

VS Code Version: 1.78.2
OS Version: Windows 11

Steps to Reproduce:

Create a python file that uses file handling
"Run and Debug" the file

I have been having an issue when debugging files in python. Any files that contain file handling cause errors. However, when running the code normally (without debugging), no errors occur, and the code runs as intended. This includes when using the file open() function, as well as other functions that involve using files, such as in tkinter.

The files being used are in the same directory as the program, as can be seen in the second image.
If there is any other information I need to add, let me know. I am very new to VScode.

This issue strangely has now changed: it affects both when I run the code normally and when I debug. Previously it wasn't a problem when I ran the code normally. I believe that the problem is that the current root directory, according to VScode, is 1 level up, above what it was when I was running the code in other IDEs like IDLE. Instead of the current directory being the directory of the python file I am running (like normal), it is the directory above that, which is weird. Relative file paths do not work because of this.

What seems to be the problem is that the working directory for running without debugging is the directory the file is in (as is normal). However, when debugging, the working directory appears to be the directory 1 above that. Why is this? How can I fix this?

Please file this on the python extension repo

managed to fix the issue by modifying my code, but it is still annoying that the cwd for run is different to that for run and debug


Enable resetMocks Jest configuration option

Explanation

Jest has a configuration option resetMocks. Equivalent to calling jest.resetAllMocks() before each test, it helps to ensure that tests are run in isolation by removing fake implementations for each registered mock function, thereby resetting its state.
This option is enabled by default for new Jest projects but has been disabled in this repo for a very long time. For some test suites, jest.resetAllMocks() (or some variant) has been added to a beforeEach or afterEach to simulate this option, but overall this is not the case, and some tests were written which assumed that mock functions were not being reset between tests.
This commit enables the aforementioned configuration option, fixes tests that fail as a result of this, and removes manual calls to jest.resetAllMocks() (or the like).
References

Fixes #745.
Changelog

(N/A)
Checklist

[x] I've updated the test suite for new or updated code as appropriate
[x] I've updated documentation (JSDoc, Markdown, etc.) for new or updated code as appropriate
[x] I've highlighted breaking changes using the "BREAKING" category above as appropriate

Resolved conflicts.


tf2autobot

hello, could you explain how to connect this autopricer to tf2autobot pls?

If you're running the autopricer on the same server as the trading bot (tf2 auto bot), as directed in the tf2autobot wiki you can simply add the pricers URL to the CUSTOM_PRICER_URL field: https://github.com/TF2Autobot/tf2autobot/wiki/Configuring-the-bot#custom-pricer-settings---only-for-advanced-users.
If you leave the autopricer port as its default (3456), the custom pricer URL should be: http://localhost:3456


[Evaluation] Use 'lookupInline'

Don't look here yet.

/benchmark plutus-benchmark:nofib

/benchmark plutus-benchmark:nofib

/benchmark plutus-benchmark:lists

/benchmark bls12-381-benchmarks

^ That's kind of what I was expecting, but I thought it was worth checking.  Most of the work in these is spent on CPU-intensive library functions.

/benchmark plutus-benchmark:marlowe

CPU performance isn't that big of a deal anymore and what we can get here should be fairly insignificant, so I added it to the epic and let's close it for now.


Update support for new format of history.dat.

Appears History.dat has gone to XML, requiring front-ends to update to handle the new format.
For the moment they're also providing the old version.
https://www.arcade-history.com/index.php?page=download

Added in the latest commit, definitely needs more testing

Found an issue, on non-arcade machines (I used the Atari 2600) if you ctrl-PageDown it goes beyond the last line and blanks the box, and you can't ctrl-PageUp to return to the text of the history.
ctrl-down does not appear to have the problem, it stops as expected at the last line.

This looks like it was an existing bug that we never caught. I redid the whole scrolling routine so everything should be snappy and accurate now.
Scroll up/down now scroll an exact page, where before it used a wrong number to scroll X amount of lines, without accounting for wrapping.

Hi Matan, looks like there are still a few display concerns that may be part of the XML or not.
Using a fresh install of IV/Play w/ default configs I can’t get to the end of some entries, like 005, or Atari 7800 for example.  See pic. Looks like it’s cutting a few lines off.  Doesn’t matter the method to get down there, ctrl-down, ctrl-pagedown, or ctrl-end.
Also I’m getting messages in VS2019 we should upgrade to a newer version of the .NET redist in our builds. Any harm in building to current?
From: Matan Bareket @.>
Sent: Wednesday, April 14, 2021 6:25 AM
To: Mataniko/IV-Play @.>
Cc: john-iv @.>; Author @.>
Subject: Re: [Mataniko/IV-Play] Update support for new format of history.dat. (#32)
This looks like it was an existing bug that we never caught. I redid the whole scrolling routine so everything should be snappy and accurate now.
Scroll up/down now scroll an exact page, where before it used a wrong number to scroll X amount of lines, without accounting for wrapping.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Mataniko/IV-Play/issues/32#issuecomment-819515718, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACGGUOYWOT4OOPCGIJ6CRZLTIWJS7ANCNFSM42ZU5UVA.

did you grab the latest commit from this morning - because i can't reproduce.
Updating the .NET version may make us incompatible with Windows 7, so no real reason for us to move.

I did a clone into a new directory and built fresh, it’s this morning’s changes as I don’t have the a2600 problem as originally reported.   Are you using a fresh install with defaults?  Dat font is Segoe UI 10.  I’m now at desktop res of 2560x1440 if that matters.  Here’s my .exe.
From: Matan Bareket @.>
Sent: Wednesday, April 14, 2021 10:14 AM
To: Mataniko/IV-Play @.>
Cc: john-iv @.>; Author @.>
Subject: Re: [Mataniko/IV-Play] Update support for new format of history.dat. (#32)
did you grab the latest commit from this morning - because i can't reproduce.
Updating the .NET version may make us incompatible with Windows 7, so no real reason for us to move.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/Mataniko/IV-Play/issues/32#issuecomment-819681792, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACGGUOY23QN3XYLUHASZWALTIXENVANCNFSM42ZU5UVA.

Is your screen hidpi?

I don’t think so.  IV/Play looks closer to my old 1920x1080 setup than it does on my daughters’ Surfaces which are 2736x1824 (where icons and spacing gets wonky).
What resolution are you at?
The problem persists on my 1920x1080 3rd monitor.

Ok, some more info.  I can't repro the issue on my daughter's hidpi Surface at 2736x1824 (005 scrolls and page downs to the end properly).  I do see the problem at 2560x1440 and 1920x1080p.

FWIW, here's another *.dat file that MASH maintains (bugs, driver progress vs. MAME release, etc.).  It's still the old style so it's good to check against the new changes:
https://mameinfo.mameworld.info/

The old DAT parser is untouched, and still works as is.
I've pushed some more fixes to scrolling that should hopefully handle with some of the edge cases - please try a new build

This is looking good, addresses the issues.  Question: I am able to add history.xml and history.dat from the same directory.  Your earlier commit seemed to want to prevent that.  Are they both able to be added?  It appears that you can cycle to each one in the UI, I now have snap, history.xml, mameinfo.dat, and history.dat to choose from.

It is prevented when we scan the MAME folder, so we don't automatically add both. As a user you are free to add as many different DAT files as you want

Ok, I think this is good to go, thanks.  Do you care to increment the build number and copyright?

done


Investigate why docs CI tests did not pick up broken link for 1.13.0

We published a link to OS X 1.13.0 that 404'ed

Resolution: there aren't checks for broken links on push/PR builds -- only cron.


Is it possible to use this wallet with ThorChads?

Hello,
Is it possible to use this wallet with ThorChads or do I need to transfer my RUNE to something like TrustWallet?
Thanks

When you go to https://thorchads.com/, you can connect your wallet.

Try to connect THORChads with the keystore you are using in ASGARDEX.

To export your keystore from ASGARDEX, go to Wallet -> Settings -> Export Keystore

Thanks.  I will try that.  In the mean time...  what's a keystore?  Is that like an account address that can be shared without any security risk?

A keystore is a JSON file with an encrypted version of the private key of your wallet. This key is encrypted with a password you have defined before (e.g. by creating a wallet in ASGARDEX or anywhere else). Don't share this keystore file with anybody. Even by protecting it with a password it might be possible to brute force private keys.
For more questions please join THORChain's Discord #general or #asgardex-desktop channel https://discord.gg/e9dBQDFE.

A keystore is a JSON file with an encrypted version of the private key of your wallet. This key is encrypted with a password you have defined before (e.g. by creating a wallet in ASGARDEX or anywhere else). Don't share this keystore file with anybody. Even by protecting it with a password it might be possible to brute force private keys.
For more questions please join THORChain's Discord #general or #asgardex-desktop channel https://discord.gg/e9dBQDFE.

So then would it be safe to export the Keystore from ASGARDEX and use it to connect on thorchads.com?

If can trust thorchads.com, then it's save.


Add default history on animal creation

Add the default history with the found history type and health status to simplify animal creation.


Add lint rule to disallow require.ensure

We need a lint rule that will error when require.ensure is used.
Users should use import() instead.

I would like to work on this.
Apparently, there is no such a rule comes with eslint-plugin-import. So I'll send a PR to eslint-plugin-import repo first and update eslint-config-react-app accordingly. Is that the correct path to take on this issue? (I'm asking this because I'm new to open source and this project)

@ljharb Thanks for pointing it out. I'll use no-restricted-properties rule and send a PR.


useShorcut

Refactor shortcut handlers into a useShortcut hook that will help with setting up keyboard shortcuts easily.

Nice, thanks! Guessing the large lockfile changes are unintentional?


Prevent PrometheusHistogramMetricsTracker from registering metrics twice in the same CollectorRegistry

Fixes #1465 and formats code related to PrometheusHistogramMetricsTracker according to this project's Eclipse formatter profile.

@apodkutin @vanDonselaar since you guys worked on this area of the code before, would you please review this PR?

@edysli I think we can close/reject this PR since https://github.com/brettwooldridge/HikariCP/pull/1692 is already merged.

@edysli I think we can close/reject this PR since https://github.com/brettwooldridge/HikariCP/pull/1692 is already merged.

@edysli I think we can close/reject this PR since #1692 is already merged.

Absolutely! :D

@edysli I think we can close/reject this PR since #1692 is already merged.

Absolutely! :D


Wrong description for reference_s in PartialLinearFluid

Reported by jriel on 12 Apr 2011 17:16 UTC
In Modelica.Media.Interfaces.PartialLinearFluid
 constant SpecificEntropy reference_s
  "Specific enthalpy in reference conditions";

Change "enthalpy" to "entropy"

Migrated-From: https://trac.modelica.org/Modelica/ticket/530

Modified by dietmarw on 12 Apr 2011 18:23 UTC

Comment by hubertus on 12 Apr 2011 19:22 UTC
Fixed in 3a3a702d817b4ca32c7450299d1faf28da4204a1.


Merge project uapbridge_esp and uapbridge_pic16

Merge the work of @rezoran to be able to use the same hardware as for uap-hcp serie 4

@Rezoran could you check if the added functionality works also for you. If everything works I will merge it in main.

I will have a look at it tomorrow and test it on my garage door


[🐞]query is empty in useLocation  on S3 Deploy With CloudFront

Which component is affected?
Qwik City (routing)
Describe the bug
Hi, I'm using qwik with S3 and CF(cloudFront)
when i use value returned by 'useLocation'
i can see query is empty
i'm using template qwik@latest
builed wtih yarn build, and yarn qwik add S3Deploy
Component Code
	const location = useLocation()

	useClientEffect$(async () => {
		console.log(location, "location")

console result in CF path (results/index.html?hash=myhash)
href:
"cf Path"
params: {}
pathname: "/results"
query: {}

Reproduction
npm create qwik@latest
Steps to reproduce
adaptor/static/vite.config.js
import { staticAdaptor } from<EMAIL_ADDRESS>import { extendConfig } from<EMAIL_ADDRESS>import baseConfig from "../../vite.config"

export default extendConfig(baseConfig, () => {
	return {
		build: {
			ssr: true,
			rollupOptions: {
				input: ["@qwik-city-plan"],
			},
		},
		plugins: [
			staticAdaptor({
				origin: "my cloudfront path",
			}),
		],
	}
})

vite.config.ts
import { defineConfig } from "vite"
import { qwikVite } from<EMAIL_ADDRESS>import { qwikCity } from<EMAIL_ADDRESS>import tsconfigPaths from "vite-tsconfig-paths"
import path from "path"

export default defineConfig(() => {
	return {
		plugins: [qwikCity(), qwikVite(), tsconfigPaths()],
		resolve: {
			alias: [{ find: "~", replacement: path.resolve(__dirname, "src") }],
		},
		preview: {
			headers: {
				"Cache-Control": "public, max-age=600",
			},
		},
	}
})

System Info
MAC OS,
yarn build
yarn qwik add (S3 deploy)
upload to dist S3
distributon to CF

Additional Information
No response

This isn't hapenning only with CloudFront, serving the content using serve library produces the same behavior.

Was this already fixed @manucorporat?


Issues about Testing phase in the RANS case

Hi Romit,
I have a minor question about the Testing phase in the RANS case
Your previous paper (https://doi.org/10.1016/j.compfluid.2020.104777) can realize "Deploy the previously trained framework to predict an approximation for the steady-state turbulent eddy viscosity and fix this quantity permanently."
I have read your code row by row but I am not sure how the quantity could be fixed permanently.
I guess this row in ML_SA_CG
"nut_ml_ = MyFilter_(nut_ml_)"
Could you kindly give me some clues?

I think the quantity could be fixed permanently by commenting out "turbulence->correct()" in simpleFoam_ML.c.
However, I still have a confuse about "nut_ml_ = MyFilter_(nut_ml_)".

The MyFilter operation performs a low-pass spatial filtering operation on the ML predictions - to enhance stability.


feat(cross): #41 update example

Add author to mailmap
Update deps
Update python
Remove deprecated linter
Format files

DCO missing. Please add signature to your commit message like in other commits:
Signed-off-by: Daniel Salazar<EMAIL_ADDRESS>


Support SQLite

Required Functionality
I use sqlite in some projects and would like to be able to use synth in these projects as well.
Something like this is what I am looking for:
synth import gen --from sqlite://real.db3

synth generate gen --to sqlite://generated.db3

Proposed Solution
I think this can be done by leveraging the already existing sqlite support in sqlx.
I did a very rough implementation here: https://github.com/rasviitanen/synth/commit/938976b3efc982060d586ab80447d9a02c1bfccd to show that it requires a minimal effort.
Obviously the implementation needs cleaning up (I copied the MySql implementation and tweaked it until import/generate worked for the db I have). But it shows a rough idea about how this could be implemented.
If you are interested I would be happy to spend some more time on this and make a more refined implementation. But I understand if you dont want to add extra complexity by introducing another db at this stage.
Use case
I have a bunch of very complex sqlite-files with real user data. I want to be able to generate files similar to these by using synth.

Hey @rasviitanen ! I looked at the linked commit and it looks great!
SQLite support is very much on the roadmap, so it's great that you're working on an implementation - if you are interested in seeing it all the way through I'd be more than happy to merge it. If you need any help please do let me know.
I'll assign you on this one. Really excited to get this merged in!

Hey @rasviitanen - would you like me to finish your sqlite work and push it over the line?

@christoshadjiaslanis Hey, thanks for asking. I have been incredibly busy since I posted this, but I have started to look at this again and will try to wrap it up during the weekend. Hopefully the next update is a PR, otherwise I'll let you know what the status is.


Service Bus: Authorization timeout and intermitent connection using multiprocessing

Package Name: azure-servicebus
Package Version: 7.8.1
Operating System: cbl-mariner docker with tag python:3-cm2.0
Python Version: 3.9.13

Describe the bug
The queue receiver fails with a ServiceBusError('Handler failed: Authorization timeout..') without a specific time period, we've implemented a recovery system based on this example. Still, sometimes we stop receiving messages, even when we have multiple processes listening to the queue and not all of them fail at the same time.
We collected some logs while the service was inactive, please check them to see that the timespan between failures isn't consistent.
The log format is: datetime - process ID - Error message

2022-11-14 23:16:46,428 - 71 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 01:01:42,653 - 42 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 01:07:02,517 - 71 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 01:22:55,219 - 54 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 02:29:03,890 - 40 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 02:30:07,897 - 59 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 02:47:09,886 - 69 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 03:14:05,076 - 54 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 03:52:17,743 - 70 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 04:29:06,723 - 66 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 05:02:45,639 - 68 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 07:22:57,991 - 53 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 07:35:24,126 - 52 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 09:33:01,441 - 64 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 09:36:51,990 - 62 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 10:25:47,027 - 67 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 11:22:27,566 - 46 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 13:06:26,985 - 58 - ServiceBusError('Handler failed: Authorization timeout..')
2022-11-15 13:15:15,936 - 70 - ServiceBusError('Handler failed: Authorization timeout..')

Additional context
Our implementation consists of a pool of processes, each of them with its own ServiceBusClient listening to a single queue, which means that even when one of them fails, the remaining should be able to read the queued messages.
The code runs in a docker image within an AKS pod
To Reproduce
I'm leaving a portion of our implementation. It's not easy to reproduce for us, given it fails kinda random and then sometimes it stops receiving messages
from multiprocessing import Process, cpu_count
from time import sleep

from azure.identity import ManagedIdentityCredential
from azure.servicebus import ServiceBusClient
from azure.servicebus.exceptions import (ServiceBusAuthenticationError,
                                         ServiceBusError)

class NodeProcess(Process):
    def __init__(self):
        super(NodeProcess, self).__init__(target=self.run_instance)

    def run_receiver(self, client):
        receiver = client.get_queue_receiver(queue_name=<insert queue name>)
        with receiver:
            received_msgs = receiver.receive_messages(
                max_message_count=1, max_wait_time=5)
            for msg in received_msgs:
                receiver.complete_message(msg)
                # Execute some code with the msg

    def get_sb_client(self):
        server = '<insert server>.servicebus.windows.net'
        client_id = <insert client ID>
        credential = ManagedIdentityCredential(client_id=client_id)
        return ServiceBusClient(server, credential)

    def run_instance(self):
        try:
            while True:
                try:
                    client = self.get_sb_client()
                    with client:
                        while True:
                            self.run_receiver(client)
                except (ServiceBusError, ServiceBusAuthenticationError):
                    sleep(5)
        except Exception as err:
            # Kill the process and spawn a new one
            ...

if __name__ == "__main__":
    procs = [NodeProcess() for _ in range(cpu_count()*2)]
    for proc in procs:
        proc.start()

    while True:
        sleep(5)

Expected behavior
Even when one of the processes fails the remaining process should be able to collect the new messages.

Hi @urucoder, I havent been able to reproduce this on my end yet. There are two thoughts I have in the meantime, in the past Ive noticed this happen especially with Authorization timeouts :

Intermittent network connections - > are you able to see from logs if a connection was lost?
Too many connections and stuff not closing properly, not disposed -> are you seeing a lot of socket connections open when this happens ? For this one this caught my eye

while True:
    self.run_receiver(client)

Its getting a receiver on every loop of while true. Would it possible to try something like this:-
def run_instance(self):
        try:
            while True:
                try:
                    client = self.get_sb_client()
                    receiver = client.get_queue_receiver(queue_name=<insert queue name>)
                    with client:
                        while True:
                            self.run_receiver(receiver)
                except (ServiceBusError, ServiceBusAuthenticationError):
                    sleep(5)
        except Exception as err:
            # Kill the process and spawn a new one
            ...
def run_receiver(self, receiver):
        with receiver:
            received_msgs = receiver.receive_messages(
                max_message_count=1, max_wait_time=5)
            for msg in received_msgs:
                receiver.complete_message(msg)
                # Execute some code with the msg

Hi @kashifkhan, this is a hard bug to reproduce, given it requires the connection to be inactive for an X time-lapse and what happens when the messages get lost is still black magic for us. I just implemented your suggestion and added more logs, I have to wait for approval on the changes and deploy it to test. I'll be back to you as soon as I have more information


Feature: file pseudo protocol

I am managing a markdown project and want to just preview the generated html and tinker around a bit with inspections and the whole stuff the extension actually provides.
However, since this site will be static, I don't use a local webserver but rather checking it in my browser via file:// urls.
Sadly, this just doesn't seem to work at all in thie extension.
Any chance to get that feature? I wouldn't even need a file listing, I would be perfectly happy with just watching files I can specify the path for (and therefore have working links between the pages).
Besides the obvious optional feature of directory listings, another really good quality of live feature would the option to just open any htm(l) file in the project that way.

I will close this issue because I have no plan on implementing a function like Live server yet
I may implement it in the future
Thank you for using my extension! 🎉


Configurator UI minor fixes

Fixed bugs:

notification message did not disappear after time
Live events Show Destinations popup didn't close on outside click

Changed link of main logo from jitsu.com to configurator root path

looks good


Empty example on 'Getting Started' page

One more thing I found :)
on the getting started page, under 'Usage' there's an empty example. Perhaps it should have an image there ?
Excerpt: "You should see a new option, which would look like this:". It then continues on from there.

as you can probably tell, i'm very happy to see lacona out there, and alive ! thanks for completing this :)

Good find! Not sure which is worse - leaving nothing or the XXXX TODO XXXX comments that I usually leave. Fixed with https://github.com/laconalabs/docs.lacona.io/commit/125f44dc71b727eaea45e85f66d7b89b496cc624
Thanks!


Index: primaryKey as an index setting

Every index needs a primaryKey. It can be set at index creation or when you start indexing documents. It can also be infered from your first document. The primaryKey can only be set once, and can't be updated afterwards.
But that is the only specific behavior that makes it any different to any other index settings. Is there a reason to handle the Index primaryKey in a different way than all the other index settings? Also, shouldn't we add it to the GET /indexes/:index_uid/settings?
There are three weird behaviours for this choice:

There is no dedicated route for getting or setting the Index primaryKey
It is used as a parameter when creating or updating an index (and ignored if the primaryKey has already been set). It doesn't belong here, and the user is not notified about the fact that this parameter is being ignored.
it is documented at two different places: here and here. Which makes me think that there is a complex choice behind it

It is documented at two different places mostly because it has connexion with both documents and indexes. Every document has the same primary key field that is stored in the index. The index has no primaryKey on creation, but once one has been set, it cannot be changed. So I made a connection between those two guides, but the one in the index guide links to documents.
One of the reason why it is was not added in the settings is because primaryKey is not updatable. Which, if we had added it in the setting would have made the use of the settings route also confusing.
The use of the POST /settings route wont work if you add primaryKey: "something" in the body and that a primary Key already exists.
Every subroute of the settings have a GET/POST/DELETE method. With the exception of the primaryKey if it was in the settings.
Because MeiliSearch is schemaless, we do not explicitly ask for a primaryKey on creation. But if no primaryKey can be infered during document addition, MeiliSearch wont be able to index the document. Which make it a required configuration in some specific situations.
Should a required configuration be in the settings? The settings are not a required knowledge to use and experience MeiliSearch. I do not realize how much friction this causes, but is it easier to ask a user to update the settings or to update the index?
The index and documents on the other hand must be understood by the user to be able to set up a MeiliSearch. So I think it is easier to introduce the primaryKey in the index, or during documentation addition, than in the settings.
Now, one thing that is possible, is that the primaryKey are badly explained in the documentation.
Maybe it just need a rewrite. I'm open for suggestions.

@bidoubiwa thanks for your answer!
When I mention that the primaryKey is documented in two different places, I don't mean that this is a documentation issue, but more like a way to show that the choice of what the primaryKey is and how it should be handled isn't necessarily as clear as for the other index settings. I am not against the fact that you either specify a primaryKey at index creation or not and let the schemaless architecture infer it. But I don't really agree with the fact that it becomes an optional parameter when you create/update documents, and specially if it can be ignored sometimes without notifying the user.
For example. Let's imagine I send a request to update documents: I can specify a primaryKey as a parameter. Let's say I send an invalid primaryKey (any key different to the one that was set already). MeiliSearch will apply the modifications to the documents anyway, send me a HTTP status of 200. How can I know as a user if the primaryKey was modified or not? I will discover that later, and will be lost trying to understand what happened. I don't think this is a transparent way of handling such a request. In my opinion, those two things should be separate.
Which makes me think... I should have a specific route to get/set a primaryKey (even if it is not updatable after the first time I set it, I will just get an error if I try to update). And I shouldn't be specifying the primary key in a POST or PUT request to /indexes/:index_uid/documents
Adding it to the general settings route can indeed create some conflicts, which I still can't reflect on as clearly as I would like. But I'm glad this can start a discussion about it! :)

But I don't really agree with the fact that it becomes an optional parameter when you create/update documents, and specially if it can be ignored sometimes without notifying the user.

This is a valid point. Having so many possibilities is more confusing than helping. Also the fact that it will not raise an error if it is ignored during document addition but will raise an error if you try to update the primary key in the index when it already exists make the behavior not consistent.
I would suggest also to remove the query parameter from the document addition route. If this is what you're suggesting.
However, I still prefer the update of the primary key being in the index routes and not the settings route.
For a reminder, this is the behavior on the index route:
On index creation
$ curl \
  -X POST 'http://localhost:7700/indexes' \
  --data '{
    "uid": "movies",
    "primaryKey": "movie_id"
  }'

primaryKey is optional in this route.
Index update (which will return an error if a primary key already exists)
$ curl \
  -X PUT 'http://localhost:7700/indexes/movie_review' \
  --data '{
      "primaryKey" : "movie_review_id"
  }'

Returns:

SUCCESS: if the primary key was at null before
ERROR: a primary key already existed (even if it was a different one)

This behavior already describes what you're are suggesting in the settings route. I'm not sure I understand what you dislike about this?

(sorry for the delay)
I completely agree with @bidoubiwa on both points:

the query parameter in addition routes (POST and PUT) does not bring any useful usage since the primaryKey is updatable with PUT /indexes/:uid.

I would rather the update of the primary key be in the index routes and not the settings route. The primary-key in settable during index creation. Why this setting would be settable during index creation and not the others? Not really consistent.
But anyway, let's supposed we considered the primaryKey as a settings  (with GET and POST routes) and we remove its set during index creation:

it would be the only setting that you can only set once, which is a little bit confusing.
it would need that MeiliSearch supports warnings. If you try to update all your settings (with the general route GET /indexes/:uid/settings) and you let the primaryKey in the settings you don't want your update of settings to be stopped by an MS error because you let the primaryKey. You need a warning.
This situation can happen when you are coding with an SDK, using the get_or_create_index method, and then you update the settings in your script. If the index was already created your script would fail. I use this kind of script all the time to populate my local MS with different datasets depending on what I'm working on.

Slightly tangential to this discussion here, but I'm curious why can the primaryKey not have any spaces in it?

Slightly tangential to this discussion here, but I'm curious why can the primaryKey not have any spaces in it?

Hello @simar7
If you are talking about the primaryKey value (ex: "id": "foo and bar", "foo and bar" is the value), this value is used in URL routes, so MeiliSearch only allows "simple" characters to avoid encoding issues


Evaluate clang/grappa tuples data types for refactoring

consider moving from variadic templates and std::tuple to schema directly in struct.

was fixed in #400


Admin Page Does Not Ask For Username/Password To Access

This is a COPY of Issue 776: Admin Page Does Not Ask For Username/Password To Access, filed on Google Code before the project was moved on Github.

Submitted on 2011-04-20T23:40:14.000Z by<EMAIL_ADDRESS>Status: Invalid

Please review the original issue and especially its comments. Comments here on closed issues will be ignored. Thanks.
Original description
**What steps will reproduce the problem?**
1.Going to www.subdomain.site.com/admin/
**2.**
**3.**

**What is the expected output? What do you see instead?**
EXPECTED: Request for admin username and password
INSTEAD: Straight to admin panel thing

**Please write in your current versions of YOURLS, Web server, PHP, OS,**
**Browser if applicable, etc...**
YOURLS 1.5

**Please provide any additional information below.**
Pretty much, the title explains everything... everybody has access to the Admin features! How can i make it so that they cannot go onto it without a username and password?

I have the same problem, how do I fix it?

Recheck your config.php and be sure a user is well defined, and try reinstalling YOURLS.


Finding a way to test all of that

https://github.com/jepsen-io/maelstrom
https://open.substack.com/pub/systemdesignone/p/chaos-engineering?utm_source=share&utm_medium=android&r=33fsjo

will be broken in smaller pieces


AutoPr-ContainerService-xizhamsft-REST Spec PrNumber 5350

Closing as this cannot be merged due to failing test, the user will have to open a new PR and fix the test first.


Option to disable dark mode

It should be possible to disable dark mode if needed (for apps that don't support dark mode)

@Rafi993 should be relatively easy to add. Will include in next update.

@Rafi993 not included in documentation yet but v3.0.5 adds disableDarkMode (bool) prop to picker.

Thanks for putting this together. I gave it a try today, but it doesn't seem to work. A quick search is showing only a single instance of disableDarkMode in the codebase., so maybe something went awry? 🤷

@hxf31891, am I reading this right, that the disableDarkMode prop was broken in commit 99ad3eb8b0df326ddf4e4ea80a57bd96e850dfc2?

This is also preventing me to upgrade to v3, tried experimenting with Material-UI makeStyles overrides to no avail. Waiting for a solution.

Made a draft PR that I haven't had time to test, hoping to do it by the end of the week.

@PierreAtUptale @TurekBot @Rafi993 this should be back as of 3.0.10


Minor styles adjustments

Moved back button left slightly

Remove verdana (hard to ell but it is)

Closing as I seem to have included these commits in another PR https://github.com/silverstripe/silverstripe-framework/pull/5502


Add metadata tags method

Add metadata tags method and tags client

addresses #115
docs dbt-labs/docs.getdbt.com/#

Problem

Solution

Checklist

[ ] I have read the contributing guide and understand what's expected of me
[ ] I have run this code in development, and it appears to resolve the stated issue
[ ] This PR includes tests, or tests are not required/relevant for this PR
[ ] This PR has no interface changes (e.g. macros, cli, logs, json artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX

FYI @vadim82 this is needed to set default tags for the cost viz work


fix: Change error on scheduling duplicate to DuplicatedTaskId

Change error on scheduling task with duplicated TaskId to DuplicatedTaskId instead of IncorrectTaskId.
This shoudl more precicely clarify nature of error and differentiate error mesage from operations with non-existing tasks.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files
Coverage Δ

src/lib.rs
84.00% <ø> (ø)

src/scheduler.rs
95.64% <100.00%> (+0.01%)
:arrow_up:


Fixes for NSS Pillar

About the PR
Electric boogaloo. List of changes is massive so see here:
https://hackmd.io/@nb5RBcIJQfqTbITE_hj4Iw/ry_0_ps0F
Addressed every issue on the tracker and more. Expanded medbay down for more space, nerfed lights across the map, added more furniture across the station and in the more open spaces like sec. Fixed atmos, power and a bunch of other bits. Also increased slot count for jobs so it can handle 80 player rounds ;)
May need to rejig atmos before it's merged and will get a new render and highlight with detailed sections so no merge till that's up.
Screenshots

Changelog

:cl:

fix: Massive list of changes and fixes for NSS Pillar. See Github for list.

Should probably put Pillar back as a votable map in this PR


Mocking: Enum support

Right now Enum types do not have a default mock resolver. The workaround is to define your own mock resolver.

Neat!


Add HTML5 Media Tracking plugin (close #805)

Enables Snowplow tracking for HTML5 Video and Audio elements.

Thanks for your pull request. Is this your first contribution to a Snowplow open source project? Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
:memo: Please visit https://docs.snowplowanalytics.com/docs/contributing/contributor-license-agreement/ to learn more and sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

Looking good. Feel free to squash and merge this into the 3.2.0 branch.


Upload large files with an upload session: specifying fileSize for the item as per docs result in 400

If you include a "fileSize" property of any size when creating an upload session (as per the docs provided on both https://docs.microsoft.com/en-gb/graph/api/resources/driveitemuploadableproperties but more importantly the examples implied by https://docs.microsoft.com/en-gb/graph/api/driveitem-createuploadsession?view=graph-rest-1.0#request-body), then you get a 400.

Also: The docs at https://docs.microsoft.com/en-gb/graph/api/driveitem-createuploadsession?view=graph-rest-1.0#request-body also confusingly only supplies the contents of the "item" property:
FYI You also get a 400 if you include<EMAIL_ADDRESS>"microsoft.graph.driveItemUploadableProperties", in the "item" object as per https://docs.microsoft.com/en-gb/graph/api/driveitem-createuploadsession?view=graph-rest-1.0#request

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

ID: 2e6ce1c2-6f62-ccf4-3816-87d2c4eadc95
Version Independent ID: da81af46-492e-a5a7-78e5-ae217d6f1c11
Content: Resumable file upload - Microsoft Graph v1.0
Content Source: api-reference/v1.0/api/driveitem-createuploadsession.md
Product: sharepoint
Technology: microsoft-graph
GitHub Login: @JeremyKelley
Microsoft Alias: JeremyKelley

As part of a repository clean up effort we are closing older issues. If this issue remains, please: open a new issue, reference this issue, and provide any additional details that may help in resolution. Thank you for your understanding as we work to improve our responsiveness.


Try statement not added after refactoring Long Method

Project : crawler4j (https://github.com/yasserg/crawler4j)
package : edu.uci.ics.crawler4j.fetcher
classname : PageFetchResult
Function : public boolean fetchContent(Page page)
variable consideration : page
When I perform LongMethod refactoring on the particular method, try catch statement is removed from the original method and exception is not added in the refactored method. So it is throwing compilation error while I'm using headless application. I could reproduce the same error in other files too if u need

The code to be extracted contains 3 statements as shown in the figure below

After refactoring the code is shown in the figure below

There is no compilation error; however, the statement return true;
inside the try block disappears after the refactoring,
and thus the refactoring does not preserve the behavior of the code.
I cannot replicate the compilation error, but there is a clear problem in the way the refactoring is performed.


fix: fix the go mod

🔍 What type of PR is this?

👀 What this PR does / why we need it:

[ ] My pull request adheres to the code style of this project
[ ] My code requires changes to the documentation
[ ] I have updated the documentation as required
[ ] All the tests have passed

🅰 Which issue(s) this PR fixes:

Fixes #369
📝 Special notes for your reviewer:
Kick this user offline after changing passwords and zk error detection

🎯 Describe how to verify it

📑 Additional documentation e.g., RFC, notion, Google docs, usage docs, etc.:

Could you please consider modifying the title of the PR?


Add wildcard support to applyconfig.py

With this patch a wild card can be used a part of preserved parameter name like calibrationParameters.*.savedposes.

thanks~


503 error when fetching an internal NextJS api with query params.

Please describe which feature you have a question about?
I have a problem with internal API routes in NextJS.
Provide additional details
I am trying to fetch data using an internal API with query parameters. The Amplify is not recognizing it and treating it as an URL and throws a 503 error.
The same version of the app deployed on Vercel is working perfectly.
What AWS Services are you utilizing?
Amplify.
Provide additional details e.g. code snippets
I am using NextJS version 12.
Anyone faced the same issue. Do you have any tips for me?

Hi @Nithur-M we've seen this happen when Access Control is enabled on SSR apps. Do you have Access Control enabled? Also can you use this guide to look for the logs and see if there's any additional information that can help us troubleshoot? https://github.com/aws-amplify/amplify-hosting/blob/main/FAQ.md#access-lambda-edge-logs

Closing due to no response. Please re-open if you continue to face this issue. Thank you.


Make bindata.go optional, remove from repository

By default will read assets from filesystems, but can embed them
by passing the "bindata" build tag (go build -tags bindata)
Fixes #77
Print a WARNING when bindata is not embedded, and
honours GITEA_WORK_DIR, when given, for finding filesystem assets.
Includes automatic test for the dynamic "bin"data library.
NOTE: an equivalent functionality is planned to be included in a
bigger change by @tboerger currently in progress and tracked as PR #74;
this PR is smaller in scope and ready.
Please keep open until either this or #74 is merged.

Keep this open til #74 is open, so people can use this before the other fix is done.

Current coverage is 3.25% (diff: 31.25%)

Merging #172 into master will increase coverage by 0.21%

@@            master      #172   diff @@
========================================
  Files           33        34     +1
  Lines         8075      8160    +85
  Methods          0         0
  Messages         0         0
  Branches         0         0
========================================
+ Hits           246       266    +20
- Misses        7809      7871    +62
- Partials        20        23     +3

Powered by Codecov. Last update 07a0753...1012a5a

Obsoleted via https://github.com/go-gitea/gitea/pull/354


Xcode 8.2 will be the last release to support SWIFT 2.3, are we obliged to migrate to Alamofire 4?

I know that this has already been discussed, but I guess that the decision of Apple to drop SWIFT 2.3 support in xcode releases after 8.2 could open different scenarios.
I've already read the reason around making Alamofire 4 available only from iOS9 and I agree, but after this Apple decision this means that for further apps release we are obliged to migrate to Alamofire 4 and drop iOS8 support.
This is quite a big issue (most of clients still request for iOS8 support), I'd like to know if there are plans to migrate Alamofire 3 to SWIFT 3.
Thank you,
Andrea

1 like for you.
The same to you :-(
Please!

Hi @DrAma999,
First off, there's no way we will be porting Alamofire 3.x to Swift 3. That wouldn't make sense for us to do and would be a huge amount of work. Instead, we've decided that we're going to add support for iOS 8 and macOS 10.10 in Alamofire 4 since Apple is going to deprecate Swift 2.3 sooner than we thought. Please see #1774 for more info.
I'm going to close this issue out. Please redirect all further comments to #1774.
Cheers. 🍻

@cnoon awesome. Thank you!


Ensure PUDL works with Pandas 1.5.0

Pandas v1.5.0rc0 breaks PUDL, so we need to chase down some problems.
Closes #1901

For some reason the ferc714 transform and output routines with pandas 1.5 are using much more memory than they did with pandas 1.4.4 -- enough that the GitHub runner gets shut down (more than 7GB).
Running the tests locally it seems like they max out at ~14GB. Clearly something has changed, but it's not clear to me how the minor changes I made to the pudl.transform.ferc714 module could be responsible for this.
@TrentonBush is there anything in there that seems like a big memory disaster to you?  The resulting dataframes get PUDL dtypes enforced in the transform() method at the end of the module, but I don't think that converts the timezones to categoricals, and messing around with it now, as strings they take up 2/3 of the memory of the demand_hourly_pa_ferc714 table (which is by far the largest table with like 15 million rows). I could try switching to using pudl.metadata.classes.Resource.format_df() instead which will convert to categorical values where there's an ENUM constraint in the resource definition.
With that change in place it looks like the transformation maybe stays under 7GB of memory usage, but the pudl.output.ferc714 routines are still using much more memory than they were before -- that's where it maxed out at 14GB before, in the Respondents.summarize_demand() method.

I re-ran this code changing nothing but the version of pandas that was installed and it seems like the increase in memory usage is due to pandas, not pudl. ferc714_out.summarize_demand():

pandas v1.4.4: ~3GB; 0m35s
pandas v1.5.0: ~17GB; 8m23s


Ignore inadvertent joystick twists

Drivers may end up twisting the joystick up to ±0.2 (value of driveStick.getTwist() / 2) when moving laterally. Ignore joystick rotation amounts less than 0.15 to avoid accidental turning. Minimum useful rotation amount is approximately ±0.3.

Current coverage is 0.00% (diff: 0.00%)

Merging #34 into master will not change coverage

@@           master   #34   diff @@
===================================
  Files           2     2
  Lines          80    84     +4
  Methods         0     0
  Messages        0     0
  Branches        5     7     +2
===================================
  Hits            0     0
- Misses         80    84     +4
  Partials        0     0

Powered by Codecov. Last update c631168...4afa283

This PR should merge into develop.


Hello, Take issues

You make a request through the referer, get the package, and then re-make the request, which is like modifying a token by replay. If replay is limited, I have a problem with that.

Hi,
Thanks for opening an issue.
I'm not sure I understand the problem, can you explain your use case and the issue you encounter in more details?
Maybe with some example requests and responses or screenshots?
S


Refactor/276 avoid multiple api calls

What this PR does / why we need it:
Updates useDatasets.tsx to make one API call, to get both datasetList and totalDatasetsCount
Which issue(s) this PR closes:

Closes #276

Special notes for your reviewer:
I commented out an assertion in DatasetsList.spec.tsx, because it is failing, even though the cy.stub() that it is testing is called with the correct parameters. I'm not sure why it is failing.
Suggestions on how to test this:
Run the DatasetsList.spec.tsx component test, which uses useDatasets.tsx.  To test how it works in the app, turn off infinite scrolling by updating config.ts in the collections directory, and test that the Collections page works as expected.
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
no
Is there a release notes update needed for this change?:
Additional documentation:

coverage: 98.563% (+1.1%) from 97.459%
when pulling 79dc551a032058f635870be387d730a8d45f0918 on refactor/276-avoid-multiple-api-calls
into c0f2d0bf0b8e85f57dfc028d35a664e6bc3474bd on develop.

thanks @MellyGray I made the changes you requested

QA ✅, there are no repeated calls to the api now, I also disabled React.StrictMode to actually see one call in dev mode,  nice work @ekraffmiller !
Could you resolve conflicts and we are good to go !


release: v0.6.1

v0.6.1

fix: Maven build issue

Generated from https://github.com/openfga/sdk-generator/pull/409

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

Project coverage is 30.88%. Comparing base (7a60fd2) to head (9d1552d).

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #105   +/-   ##
=========================================
  Coverage     30.88%   30.88%
  Complexity      842      842
=========================================
  Files           168      168
  Lines          6185     6185
  Branches        679      679
=========================================
  Hits           1910     1910
  Misses         4177     4177
  Partials         98       98

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


Binary Sensors on Chrome for Android

When I use my phone to toggle a binary sensor (one of four) from the a dashboard the physical sensor is toggled but the webpage shows the one above it changed.

@rayvenwalker Current web page is developed for desktop. For android we have to develop new app. Can you check sensor order in both webpag and on your mobile?

@rayvenwalker I am closing this issue, as current web UI not developed for android browser.


Improve partial charge check

This PR fixes #325 by ensuring user charges set at the molecule level are also set at the atom level which is how OpenFF detects them.

Hello @jthorton! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file gufe/components/explicitmoleculecomponent.py:

Line 45:80: E501 line too long (105 > 79 characters)

In the file gufe/tests/test_smallmoleculecomponent.py:

Line 268:80: E501 line too long (112 > 79 characters)
Line 282:80: E501 line too long (104 > 79 characters)


Quick Start Guide: Divshot Deployment is confusing

Issue by BigAB from Tuesday Oct 06, 2015 at 20:32 GMT
Originally opened as https://github.com/donejs/donejs/issues/173

So I was going through the quick start guide and I found this confusing:
In the Deploy section where it describes deploying to divshot it was not clear to me that we would only be deploying our assets to divshot, and my confusion was exacerbated by the terminal:

$ donejs deploy
donejs - deploying to 'divshot

Uploading 24 files.
Uploading 14 files.
Finalizing build ... DONE.
Releasing build to 'production' ... DONE.

Application deployed to: 'production'.
You can view your app at the following URL: 'http://donejs-chat-adamlbarrett.divshot.io'

...namely the You can view your app at the following URL: 'http://donejs-chat-adamlbarrett.divshot.io' part, as of course when I went there, it 404'd.
I think we should take the time, to make it clear we are only deploying our assets there, and our node app would still be required.
We could also mention that we could deploy an html file there as well, and have a non-ssr app up on divshot... but maybe that is confusing the matter.

Comment by matthewp from Tuesday Oct 06, 2015 at 20:41 GMT

The static version won't work unless configured to use hashchange routing.
Good points about the guide language, that should be clarified.

Comment by daffl from Tuesday Oct 06, 2015 at 20:37 GMT

We could also include production.html and rename it to index.html. Then at least the chat app would technically load when going to that URL (albeit without server-side rendering). I think that would be good because people can actually see their own app in production.
And you are right, we should also mention that we are only deploying the production assets.
@matthewp Can we change bundleAssets to somehow include production.html and rename it to index.html if configured?

Comment by daffl from Tuesday Oct 06, 2015 at 20:53 GMT

There's probably a way to configure Divshot to do that as well.

Comment by daffl from Tuesday Oct 06, 2015 at 20:52 GMT

The static version will work you just can't go directly to /chat which I think is fine.

Closing because divshot is no longer used, so I think this is out of date. Please reopen if you still think the issue isn't solved.


Add bcfishobs

Insert URLs to the project here:
https://github.com/smnorris/bcfishobs

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

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

@smnorris


[Event Request] Codeunit 304 "No. Series - Impl." - OnNoSeriesLineFilterOnBeforeFindLast

Describe the request
Hello, could you please add an event in function GetNoSeriesLine with the handled-pattern:
[InherentPermissions(PermissionObjectType::TableData, Database::"No. Series Line", 'm')]
    procedure GetNoSeriesLine(var NoSeriesLine: Record "No. Series Line"; NoSeriesCode: Code[20]; UsageDate: Date; HideErrorsAndWarnings: Boolean): Boolean
    var
        NoSeriesRec: Record "No. Series";
        NoSeries: Codeunit "No. Series";
        NoSeriesErrorsImpl: Codeunit "No. Series - Errors Impl.";
#if not CLEAN24
#pragma warning disable AL0432
        NoSeriesManagement: Codeunit NoSeriesManagement;
#pragma warning restore AL0432
#endif
        LineFound: Boolean;
    begin
        if UsageDate = 0D then
            UsageDate := WorkDate();

        // Find the No. Series Line closest to the usage date
        NoSeriesLine.Reset();
        NoSeriesLine.SetCurrentKey("Series Code", "Starting Date");
        NoSeriesLine.SetRange("Series Code", NoSeriesCode);
        NoSeriesLine.SetRange("Starting Date", 0D, UsageDate);
        NoSeriesLine.SetRange(Open, true);
        if (NoSeriesLine."Line No." <> 0) and (NoSeriesLine."Series Code" = NoSeriesCode) then begin
            NoSeriesLine.SetRange("Line No.", NoSeriesLine."Line No.");
#if not CLEAN24
#pragma warning disable AL0432
            NoSeriesManagement.RaiseObsoleteOnNoSeriesLineFilterOnBeforeFindLast(NoSeriesLine);
#pragma warning restore AL0432
#endif
            LineFound := NoSeriesLine.FindLast();
            if not LineFound then
                NoSeriesLine.SetRange("Line No.");
        end;
#if not CLEAN24
#pragma warning disable AL0432
        if not LineFound then begin
            NoSeriesManagement.RaiseObsoleteOnNoSeriesLineFilterOnBeforeFindLast(NoSeriesLine);
            LineFound := NoSeriesLine.FindLast();
        end;
#pragma warning restore AL0432
#else
        if not LineFound then
            LineFound := NoSeriesLine.FindLast();
#endif

Event definition
[EventSubscriber(ObjectType::Codeunit, codeunit::NoSeriesManagement, 'OnNoSeriesLineFilterOnBeforeFindLast', '', false, false)]
    local procedure NoSeriesManagement_OnNoSeriesLineFilterOnBeforeFindLast(var NoSeriesLine: Record "No. Series Line")

Additional context
Compiler Warning AL0432

Could you please outline why you need this event?
The IsHandled events where remove intentionally by @AndreasMoth in this PR https://github.com/microsoft/BCApps/pull/319
There he asked for Feedback on this PR.
Further this object is now internal and the event would have to be add in the facade codeunit

This request is very similar to this one here: https://github.com/microsoft/BCApps/issues/1362
For System Application and Business Foundation (and anything else already on BCApps) I'd recommend following the process there: Create an issue, when approved create a PR. Yes it's a little more work on your end but the lead time to a fix should be much shorter.
As this seems like a duplicate of the issue on BCApps i'll close this one.


Scons: fixed build for vanilla clang in mac os x

Fixes https://github.com/godotengine/godot/issues/36501

Thanks!


Failed parsing SMILES

Hi,
I meet the problem that the SMILES can not be parsed.
I have a sample here:
below is the code I write:

and I got this result

I also attached a screenshot here. I hope the SMILES can be parsed correct.
Thanks!

I see! Thanks very much for your help!


UrlMappings should not be packaged with plugin

Hi, The UrlMappings should be excluded from the plugin jar. Or delete the file since the plugin does not need any UrlMapping
It overwrites url mappings of the application.
See also https://github.com/TouK/excel-export/issues/44

deleted in b83538c976bf770cb670f6c555ee4acdd8b1d386
pushed in 2.1.1 (don't forget to force refresh dependencies please)
Thanks for reporting


Suggested capabilities for Tier 2 analysts

The text for the Tier 2 analysts states that they should have Tier 1 capabilities with live response, but does not mention "Manage Security Settings in Security Center", do you recommend that they have this also? if so, please state this, if not who should have that permission?
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.

ID: 55901976-4431-c470-88cb-af7430bb7339
Version Independent ID: 0e80c507-335d-bd5e-7315-b8fe30aec0ff
Content: Grant access to managed security service provider (MSSP)
Content Source: microsoft-365/security/defender-endpoint/grant-mssp-access.md
Service: microsoft-365-security
Sub-service: mde
GitHub Login: @mjcaparas
Microsoft Alias: macapara

@DeanGross Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/11922
Once the author approves, the changes will be live.
Thanks
Sri

Closing as per author's comment in the PR. Thanks


Soft delete instead of remove()

What we have now
SkyService iOS crew, passenger, and Android passenger apps are using the Ditto SDK remove() API.

remove() calls

How we want to change
We recommend customers for doing soft delete instead of calling remove() for deleting data. (See Slack conversation for contexts).

Do not use remove() in iOS and Android apps
Have delete flags on models
Toggle the flag to hide data from apps
Use query to avoid syncing deleted Documents

struct Note {
  let _id: String
  var text: String
  var deleted: Bool
}

// deleting data
note.deleted = true

// finding data
collection.find("deleted == false")

Targets

iOS Crew app
iOS Passenger app
Android Passenger app

@texasRanger09 Do you think you have time to take this issue?

Yep, I can take it


Travis-CI build fail because of visualization.

When Travis-CI runs pytest on test_image_classification, it fails because of  viz_init(config.CONFIG.viz) that is trying to interact with the user. This issue saw day from PR #176.

Commit 63c63c1 from PR #176 is resolving the issue.


Proposal to deal with GO:0044403 biological process involved in symbiotic interaction

@pmasson55 proposes that we change definition of the following terms to allow annotation of host proteins:
'biological process involved in interaction with host' http://purl.obolibrary.org/obo/GO_0051701
'biological process involved in interaction with symbiont' http://purl.obolibrary.org/obo/GO_0051702
'biological process involved in symbiotic interaction' http://purl.obolibrary.org/obo/GO_0044403
'biological process involved in interspecies interaction between organisms' http://purl.obolibrary.org/obo/GO_0044419
'biological process involved in intraspecies interaction between organisms' http://purl.obolibrary.org/obo/GO_0051703
'regulation of biological process involved in symbiotic interaction' http://purl.obolibrary.org/obo/GO_0043903
& some children like:
'migration in host'
'acquisition of nutrients from host'
'adhesion of symbiont to host'
'exit from host cell'
'symbiont entry into host'
'symbiont intracellular protein transport in host'
'symbiont-mediated killing of host cell'
'translocation of molecules into host'

Call with @genegodbold
Maybe this could be organized like this:
. interspecies interaction
.. symbiont-mediated modulation of host process
.. venom-mediated modulation of process in another organism
.. host-mediated modulation of symbiont process
.. symbiont intracellular protein transport in host {host + symbiont proteins}
.. viral translation {host + symbiont proteins}
.. migration in host {host + symbiont proteins}
.. killing of cells of another organism
... neutrophil-mediated cell killing

Examples: https://amigo.geneontology.org/amigo/term/GO:0044419 - check mammalian proteins annotated to this; do we want these host proteins to be annotated?


Skip unlinked files when creating tar partitions

An update to the upstream branch.

Recently I'm trying to upgrade 1.0.0a based. I close this PR as this is included in it.