Kicked for flying after using cruxite artifact from Minestuck

After using the cruxite artifact for the first time, the player is kicked for flying and the surrounding area is not copied to the new dimension

@mraof Please post the stack trace.

@bloodmc It's a kick, not a crash.

@JBYoshi We don't want a crash report, we want a stack trace. So post
the log.
On Sat, Aug 29, 2015 at 3:40 AM, JBYoshi<EMAIL_ADDRESS>wrote:

@bloodmc https://github.com/bloodmc It's a kick, not a crash.
—
Reply to this email directly or view it on GitHub
https://github.com/SpongePowered/Sponge/issues/332#issuecomment-135869435
.

--
Check out my site and send me ideas!

As I said before, there is no stack trace for a kick.

Closing this until we get more feedback.


Fix stub_const for case that const_missing defines target nested constant

Added const_get before calling const_defined because Module#const_missing may
define target constant.
Representive case is a Ruby on Rails (ActiveSupport),
https://github.com/rails/rails/blob/master/activesupport/lib/active_support/dependencies.rb#L176
In test in a Rails app, you'll get an error if you used stub_const for
controllers, models, helpers, etc before it get loaded by
ActiveSupport::Dependencies::ModuleConstMissing#const_missing.

stub_const "FooController::X", :foo
rspec-mocks defines FooController as empty module
call FooController
Normally, const_missing has called and Rails loads the controller,
but rspec-mocks defined FooController in stub_const,
so controller won't be loaded.
You'll get an error.

@myronmarston et al. What about allowing a syntax that causes the autoloading to happen inline, e.g.:
stub_const(Finder, '::PAGE_SIZE', 2)

@myronmarston et al. What about allowing a syntax that causes the autoloading to happen inline, e.g.:

Why complicate RSpec with a larger API when you can just load the class yourself?  In general, RSpec isn't concerned with how you load your code (that's entirely up to you) and I don't want RSpec to get in that business.

I guess it seems like it would be nice to have an idiomatic way to handle stubbing autoloaded constants, as opposed to having something like this laying around our codebase:
Finder # need to autoload because of the way RSpec stubs constants
stub_const('Finder::PAGE_SIZE', 2)

I haven't looked too closely at the code and I don't know your intentions with the api, but we could also pass it in as a third argument and instead require users to pass nesting in as an option:
stub_const('PAGE_SIZE', 2, nested_under: 'Finder')

It seems like having the nesting and the name of the constant explicitly separate might help reduce the complexity of the implementation, but you'd know better than me on that.
I don't think it's the place of RSpec to pass judgement on the way you load your code, but I do think it should be aware of the contexts it is used and be accommodating to the more common use cases. Not a big deal one way or another. We'll probably just wrap it in a helper method on our end otherwise.

If something depends upon Finder, why not declare that dependency at the top of the file with require 'finder'?
There's no need to involve autoloading at all.  Just require what you need when you need it.

That's basically the same problem, it just puts a greater distance between the loading and the reason we're loading it:
# we need to require this because of the way RSpec stubs constants
# look for `stub_const` below
require 'path/to/the/finder'

# ...later
stub_const('Finder::PAGE_SIZE', 2)

We can debate the pros and cons of autoloading vs manually requiring dependencies, but for better or worse a huge chunk of the ruby community uses autoloading (thanks, of course, to Rails). I can imagine as a library developer you've run into a fair share of autoloading nightmares, but as an app developer (mostly) I have to say it's been a huge convenience, and the times I've come up against it have been few and far between, not to mention easy to resolve.

I'm still a Rails user, but do a lot of other non-Rails dev as well.
As a Rails user, I want to explicitly require dependencies in my spec file so it's obvious what I depend on.
I'm generally negative on autoloading since it makes it really easy to forget to care about your inter-dependencies. This library's express purpose is to help uncover and minimize dependencies, I feel like making auto-loading easier here is heading in the wrong direction. It's also potentially confusing against the verified double API (which acts different based on whether you require something or not).
I could potentially imagine an API added to rspec-rails with the aim of supporting rails users better, so I'm probably negative on that suggestion as well.
I'd recommend if people do think is a good idea, we start by providing it in a plugin. If it's popular, we can revisit bringing it into core. (Like what we did with verified doubles / RSpec fire.)

I understand the motivation, though in our case we already do a pretty decent job of minimizing inter-dependencies, so manual requires would add process and effort without a whole lot in the way of useful architectural feedback. I'm also not sure I agree with the idea that using requires is the ideal way to put that sort of design pressure on an application, as opposed to more explicit static analysis checks with the likes of rubocop, or, of course, writing tests.
At any rate, as you might have imagined, I'm definitely in favor of supporting some sort of autoloading workflow, either at an individual api level, or even with a global configuration of some sort that can be toggled: config.autoload_stuff = true.

Work around... stub_const("#{Finder}::PAGE_SIZE", 2)

Nice thanks. I was thinking of doing something like that.


Update virtus dependency

This dependency was updated in version 0.0.19 and locked to virtus 1.0.2.
Here at flippa.com we've been running it with version 1.0.5 (latest) with no problems.

Coverage decreased (-0.2%) to 99.465% when pulling 9c9b086b2915e6a0f7361b70c79b26eb821d0a6c on iamliamnorton:update-virtus-dependency into 679a9c6ca69284d795d9b84bd248933c3784932e on cschuch:master.

Apparently not!
https://travis-ci.org/cschuch/daedal/builds/208841212

@iamliamnorton yeah, I noticed this when I bumped the version yesterday. I'll take a look at it this weekend and see if I can fix things to work with the latest Virtus


Update opentelemetry-api, ... to 1.34.1

About this PR
📦 Updates

io.opentelemetry:opentelemetry-api
io.opentelemetry:opentelemetry-exporter-jaeger
io.opentelemetry:opentelemetry-exporter-otlp
io.opentelemetry:opentelemetry-sdk
io.opentelemetry:opentelemetry-sdk-testing

from 1.16.0 to 1.34.1
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.opentelemetry" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.opentelemetry" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

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

Comparison is base (862ac3a) 60.51% compared to head (00cae69) 60.54%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #412      +/-   ##
==========================================
+ Coverage   60.51%   60.54%   +0.03%
==========================================
  Files         152      152
  Lines        3277     3277
  Branches      101      105       +4
==========================================
+ Hits         1983     1984       +1
+ Misses       1294     1293       -1

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


METRON-1347: Indexing Topology should fail tuples without a source.type

Contributor Comments
If you are sending data into metron indexing without a source.type, which would only happen if you're bypassing our previous topologies, we cannot configure how we write to the indices, so the message should be explicitly failed and reported.
To test this, you can send a message into the indexing topic via kafka console producer that looks like:
{
  "value" : "foo"
}

Ensure that the tuple is failed and an error message indicating that a source.type is required is written to the storm UI.
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[x] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[x] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[x] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[x] Have you included steps or a guide to how the change may be verified and tested manually?

[x] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && build_utils/verify_licenses.sh

[x] Have you written or updated unit tests and or integration tests to verify your changes?

[x] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[x] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

I would like to hear feedback from @ottobackwards on other required fields but this looks good to me otherwise.

The minimum required fields, as far as I can see right now are source.type, original_string and timestamp.  Given the use case for this is something that has skipped the parser topology, we should validate those.
If we think the same can be done for indexing, then we should use the same classes/technique there.
Again, this is based on the presented use case

Actually, I don't think original_string is required past the parser topology.  For instance, profiler messages into enrichment do not have original_string.

My +1 still stands on this and this PR has been up for quite some time. I will merge by EOD unless there are any additional concerns.

@mmiklavc @cestella @ottobackwards  Is this good to be merged in?

The parser topology PRODUCES the original_string.  By that very action, and it's requirement, it can only be used and required by downstream usages either from rest ( post indexing ) or during enrichment.  It seems inconsistent to validate without including that, if what you want to do is validate the entire set of required fields.  If you only want to handle what is required at a given step, but not what is required 'overall' then this is OK, but something doesn't seem right here conceptually.

What I think would be better would be to have a readme about the required fields and refer to that document from these other documents

It seems this PR is meant to address the global case, since the writer is general purpose. Per @cestella's comments, I don't know that we can include original_string. I do think there's value in minimally ensuring the timestamp and source.type fields are validated in the near term. It seems that addressing a broader validation strategy might be in order, but maybe we could handle that separately as a compromise? Thoughts @ottobackwards?

I think this is a mess that we will need to sort out, but I won't hold this up for that.
I'm +0 I guess.

@ottobackwards created this to track it - https://issues.apache.org/jira/browse/METRON-1524


Omnilight shadow map

This renders the full cubemap for each omnilight and samples it in the pbr shader.

Just found out it needs porting to wgsl. I can look at it tomorrow.

Replaced by #15


Login not working.

Used to login with<EMAIL_ADDRESS>but since this is no longer supported I tried to login with IYO. I have added<EMAIL_ADDRESS>my IYO account, verified it and added it to shared info with tf_freeflow pages. But it will not login to my account, it just redirects me to the frontpage without any feedback.

moved issue to right repo


Paystack payment not initiating

the error is "'secret_key' not a valid key=value pair (missing equal-sign) in Authorization header: <secret_key>"

@JaeKralj it would seem your secret_key is not set correctly in your Medusa config.
Confirm this is set correctly, provide more context on your issue if it persists: Medusa version, medusa-payment-paystack version, what action you were taking specifically when this happened

this is how I have set it up
created env variable for secret key

then I configured medusa.config.js like so

medsajs/medusa v1.16.0,
the issue occurs when I click the paystack option, more precisely when initatePayment is called

I cannot reproduce this on my Medusa store instance running v1.1.2 of the package. Are you able to reliably reproduce it? Do you get an indication the error is returned from Paystack or occurs before the initiate payment request is sent to Paystack to begin with?
Please share the entire error: error message and stack trace

This is reproduced reliably, I'd attempt to recreate the Backend again, and build from scratch.
The error is from paystack, I copied the code of the plugin to really debug the error, the error is from paystack.
The error I get from the plugin is cannot read property of undefined reading reference (data.reference is returned in the initiatePayment function)

Ahh, from Paystack. It'd be really helpful to know when/why this happens, so we could add a case to handle this or provide a more helpful feedback. Looking forward to hearing what you find @JaeKralj

Ahh, from Paystack. It'd be really helpful to know when/why this happens, so we could add a case to handle this or provide a more helpful feedback. Looking forward to hearing what you find @JaeKralj

I copied the code, and used axios instead of the http module, it lead to decrease in lines of code, improved readability and most importantly solved the issue for me, can I submit a PR with this little tweak?

Yes @JaeKralj, submit the PR.


"See UserVoice" link should not be there anymore

Microsoft WinDev took down the UserVoice channel.

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

ID: 48168c03-36df-a7cb-baeb-49bd31589260
Version Independent ID: 7a17333c-9eee-d327-73aa-49fdbc2f4de2
Content: Extend your app with Windows UI and components
Content Source: hub/apps/desktop/modernize/desktop-to-uwp-extend.md
Product: uwp
Technology: apps
GitHub Login: @mcleanbyron
Microsoft Alias: mcleans

Thanks for notifying us of this issue. I removed the obsolete UserVoice link from this and other articles in the same section. The standard Product Feedback link at the bottom of each article is correct.


Mongo DB can't be installed

Hello everyone, I have a server using nodejs mongo and dlib for tracking and counting cars, sending some info to mongo, however I have this running in docker, although I can get it out of docker it seems impossible to install mongo, i've tried some tricks from raspberry but still can't manage to do it, any help would be appreciated.

Hello,
Can you provide information about how you attempted to install mongo and the errors that it produced?
Thanks!

Well at first I tried like sudo apt-get install mongodb and it showed that there was no distribution for the armv8 processor, something like that if I remember well, after that, I tried building my docker-compose file and this is the one I'm talking about
`version: "3"
services:
interfaz-web:
build: ./webPage
volumes:
- ./webPage:/usr/src/app
- "/etc/timezone:/etc/timezone:ro"
- "/etc/localtime:/etc/localtime:ro"
ports:
  - 3000:3000
depends_on:
  - scriptfinal
  - mongo

scriptfinal:
build: ./scriptService
volumes:
- ./scriptService:/usr/src/scriptService
- "/etc/timezone:/etc/timezone:ro"
- "/etc/localtime:/etc/localtime:ro"
devices:
- /dev/video0:/dev/video0
- /dev/bus/usb:/dev/bus/usb
- /tmp/.X11-unix:/tmp/.X11-unix
ports:
- 3500:3500
privileged: true
depends_on:
- mongo
mongo:
container_name: mongo
image: mongo
ports:
- "6000:27017"
logging:
driver: none
`
It didn't install mongo as there's no distribution available for the processor

@slbejaranom that is because mongo doesn't release debian packages for armv8 any more. See here (this was last year, but you get the point): https://developer.mongodb.com/community/forums/t/add-mongodb-4-2-arm64-builds-for-raspberry-pi-os-64-bit-debian-buster/5046/2
Looks like they do include some instructions to cross build the package your self though:
https://developer.mongodb.com/community/forums/t/add-mongodb-4-2-arm64-builds-for-raspberry-pi-os-64-bit-debian-buster/5046/5

Thanks Nam, I've seen you in some previous posts, I'll try to compile, with the 1GB coral would you recommend me to add more swap before doing it?

@slbejaranom I haven't tried it yet, but it seems to be a crossbuild thing, where you compile on your x86 machine and then copy the artifacts over to the dev board, so it's not a build on the dev board at all!


Show precomputed clusters

Right now, the only way of showing clusters in the visualization app is to click on the button "calculate and show clusters", which is what it is done in the original Timecluster paper. HOwever, in order to integrate some of the works of our colleagues in Poland, it would be interesting to add the possibility to get the clusters from a logged artifact.
The artifact would be a ReferenceArtifact logged by the dr_run, just like it is done with the embeddings, and it could be as simple as an array of cluster labels.

I think this is already done!


Rename package to sdf-wot-converter

Codecov Report

Merging #13 (d6239e0) into main (b0b07f3) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #13   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            7         7
  Lines          338       338
=========================================
  Hits           338       338

Continue to review full report at Codecov.

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


Darkmode doesn't work without meta tags

Hi, thanks for awesome templates! But, I test on iOS and Mac OS default mail apps and dark mode doesn't work.
I added this to the template
 <meta name="color-scheme" content="light dark">
 <meta name="supported-color-schemes" content="light dark">

And this to style and this works as planned.
    :root {
      color-scheme: light dark;
      supported-color-schemes: light dark;
    }

What do you think?

Thanks for this. It fixed dark mode in Superhuman.

I confirmed that this fixed dark mode on both iOS and Mac OS mail apps using Litmus. The fix has been merged. Thanks for reporting this!


Autoamtically Search Source-Stack While Whecking for ConnectTo Parameters

Current Behavior:
Currently, you must prefix a source param with SOURCE_ to enable the plan builder to find the corresponding parameter automatically without explicitly specifying the SOURCE_ prefix.

Currently, we search for parameters without prefix at the second node where the connects to operation is NOT defined. That means, sometimes that could be the SOURCE and sometimes the TARGET node of the connects to. However, I guess that is intended as we assume that in most cases we need information (endpoints, etc.) from the other side of the connects to relation. So, I´m not sure if we should change that. What do you think @nyuuyn ?
See here.

The only "solution" would be to use a convention, e.g., search first the target stack than the source stack and so on.
However, this introduces in some cases more issues then it helps, expecially if we think about identical property names, such as, IP, Password, User and so forth.
The ambiguity of these properties makes defining conventions quite hard, that's why we came up with the idea of "SOURCE_" and "TARGET_" in the first place.
We could adopt the yaml feature of referencing properties directly for parameters, which would be more a configuration instead of a convention solution.

The yaml way is not possible in XML as you cannot map the inputs of an operation to properties directly.
However, yaml also uses the SOURCE and TARGET syntax to reference the corresponding Node Template - see here. Instead of using this syntax by the mapping of properties to the input parameters, we use this in directly in the names of the input variables. The only thing we should check is how the properties are searched according to the standard if there is no direct mapping specified.

I can't find anything specific in the standard (1.3 or the upcoming 2.0) which talks about this. Did you find something?
They only talk about this a little in 2.0 at 4.4.12 but that only outputs what kind of mappings are allowed

I guess so:

4.2.2 Prefixed vs. Unprefixed TARGET names
The list target node types assigned to the TARGETS key in an execution environment would have names prefixed by unique IDs that distinguish different instances of a node in a running model  Future drafts of this specification will show examples of how these names/IDs will be expressed.
<IP_ADDRESS> Notes

Target of interest is always un-prefixed. Prefix is the target opaque ID.  The IDs can be used to find the environment var. for the corresponding target. Need an example here.
If you have one node that contains multiple targets this would also be used (add or remove target operations would also use this you would get set of all current targets).

https://docs.oasis-open.org/tosca/TOSCA-Simple-Profile-YAML/v1.3/os/TOSCA-Simple-Profile-YAML-v1.3-os.html#_Toc26969452

If I understand it correctly according to the whole section we can only use properties of the source and target node(s), not the nodes they are hosted on, e.g., the IP of the underlying infrastructure right?

No, I read it like the whole target stack is meant because otherwise nothing would work if you have an IP-address defined at a VM and you connect to an application hosted on this VM.


Make Infra Searchbar a reusable component

<app-infra-searchbar-component> is being used in combination with a button several times and has to be styled several times as a result.  We should turn this combo into its own component.

Closing as won't do.
May have jumped the gun on this one, these are two separate components that are showing up a few times together.  Combining them in a single component may actually make the build more hectic.


Add Item now shows correct C#/VB templates

Opt'd C# and VB into legacy project's Add Item template guid and project type guid, so that correct C#/VB templates show up. Also opt'd them into returning their legacy equivalent of project type guid, so that other features start showing up because they think we're legacy C#/VB projects.

tag @dotnet/roslyn-analysis

@srivatsn Couldn't test your settings thing as the Tool property doesn't exist for settings in master.

I suspect it's because None.xaml doesn't have the definition for CustomTool. Try a resx file that has a CustomTool property.

👍

@dotnet-bot retest release please
Slave went offline.

retest this please

:+1:


[5.2] Call refreshRememberToken only if required

See https://github.com/laravel/framework/issues/12054
refreshRememberToken is called on every logout. I don't know why it's called (maybe we have to remove everything from uncommented line 537 to 539), but I'm (almost) sure it's not required if user has no remember_token attribute.

Unit tests failed.


clean: Ensure cephcluster cleanup job runs

Description of your changes:
The cleanup policy was not allowed to take effect during the cluster cleanup. The finalizer was immediately be removed instead of remaining until the operator has a chance to handle the cleanup policy and internally remove the finalizer. Now the cleanup policy is allowed to be applied and the cleanup job(s) will be started to cleanup the host path and disks from OSDs.
Checklist:

[ ] Commit Message Formatting: Commit titles and messages follow guidelines in the developer guide.
[ ] Reviewed the developer guide on Submitting a Pull Request
[ ] CI tests has been updated, if necessary.
[ ] Documentation has been updated, if necessary.
[ ] Unit tests have been added, if necessary.

@travisn is this ready for review or you are still exploring the fix? Thanks

The fix looks good in the local testing, there just seems to be a CI issue that I'm still looking at.

@subhamkrai Ready for final review, the CI is passing now, after rebasing. Such an old PR! Time to enable the stale bot...

@subhamkrai Ready for final review, the CI is passing now, after rebasing. Such an old PR! Time to enable the stale bot...

Will check on adding the bot


Default value for enums

Project
It's not public but I am working on a high-throughput IO block device subsystem.
Use Case
I want to use enums for an operation log where the enum represents the operation type e.g. Put or Delete.
Current State
If I do
#[derive(FromBytes, FromZeroes, AsBytes, Unpacked)]
#[repr(u8)]
pub enum OperationType {
   Put = 1,
   Delete = 2
}

... I get an error that the enum must have all 256 variants.
Desired State
It sure would be nice if we could specify a default value somewhat like:
#[derive(FromBytes(default = 0), FromZeroes, AsBytes, Unpacked)]
#[repr(u8)]
pub enum OperationType {
   Unknown = 0,
   Put = 1,
   Delete = 2
}

This is similar to how the serde handles this issue.

Thank you for the feature request! The FromBytes trait marks a type that can be soundly viewed from a buffer of arbitrary bytes. Those bytes may or may not be owned, shared borrowed, or mutably borrowed. How should this behave:
let bytes = &[42u8];
let ot: &OperationType = OperationType::from_bytes(bytes)

Both ot and bytes point to the same memory. OperationType doesn't have a variant that corresponds to the byte 42u8, and we can't mutate that memory during parsing because bytes is immutable. I don't see a way to reconcile these two issues.
That said, if your complaint is that defining 256 variants is irritating, I can only wholeheartedly agree. @joshlf perhaps we could provide an attribute macro to generate these excess variants.

Understood and thanks for the thoughtful reply. I suppose in general this is the issue with SerDe libraries ... there is an impedance mismatch between the semantics of the language into which the bytes are deserialized and the bytes themselves (and the attendant "wire" specification).
Instead of expecting the language to match perfectly to the serialized format e.g.:
#[repr(u8)]
pub struct enum OperationType {
  Foo = 0,
  Bar = 1,
  Baz = 2,
}

let bytes = &[1u8];
let ot = &OperationType = OperationType::from_bytes(bytes);

We could expect that the language representation includes some method to detect a mismatch between the library and the binary representation. For example, the Rust SerDe library expects you to call deserialize from the Deserialize trait and that the method returns an error if it fails. Zerocopy could have methods to get the enum value if it exists and the raw bytes if it does not.
let bytes = &[3u8];
let ot: Enum<OperationType> = OperationType::from_bytes(bytes);
match ot.get() {
  Some(e) => {/*deserializes*/},
  None => {/*fails*/}
}
let raw = ot.raw();
let raw_mut = ot.raw_mut(); // Could return mutable slice containing just the value

... These method signatures are sketches for discussion. Tastes vary on specific method names and signatures :)

A macro for generating missing enum values would be very welcome.

I can think of two ways to make this ergonomic:
Auto-generate all enum variants
As you suggested above, @jswrenn, use an attribute macro (or similar) to add a variant for each missing discriminant. I see a few issues with this:
First, in cases where the enum discriminant is assigned to a const expression, I'm not sure how we'd be able to compute which discriminants are missing.
Second, the ergonomics depend highly on your use case. This isn't so bad:
match op {
    OperationType::Put => ...,
    OperationType::Delete => ...,
    _ => ...,
}

However, this is dangerous since now your code will silently keep compiling even if the user adds more variants that should be handled. In fact, in Netstack3, we had an explicit rule requiring every match pattern to be explicitly handled for this reason. Explicitly matching in a case like this would be extremely unergonomic.
Rely on niche optimization
Alternatively, if niche optimizations are ever guaranteed, we could use that to generate an enum with the correct layout but better ergonomics. Interestingly, Rust currently doesn't seem to support niche optimizations with explicit variant discriminants (if you try, it yells at you that you need a #[repr(inttype)] attribute on your enum), so let's pretend that our variants have discriminants 0 and 1 rather than 1 and 2 (as in the original example on this issue):
enum OperationType {
    Put,
    Delete,
    Other(OperationTypeOpther),
}

#[rustc_layout_scalar_valid_range_start(2)]
struct OperationTypeOpther(u8);

The Rust playground confirms that OperationType is 1 byte in size.
The ergonomics would be quite good:
match op {
    OperationType::Put => ...,
    OperationType::Delete => ...,
    OperationType::Other(_) => ...,
}

...and would still retain the future-proofing behavior where a newly-added variant would make this code stop compiling.
This would require a number of language features to be stabilized publicly, and is likely years off at a minimum.


Task: create interfaces for individual flex properties

Description
Created and exported interfaces for the following flex properties:

AlignContent
AlignItems
AlignSelf
JustifyContent
JustifySelf
FlexDirection
FlexWrap

These interfaces will enable better type casting for Flex component usage in client.
Type of change

Chore (housekeeping or task changes that don't impact user perception)

Testing
How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Also list any relevant details for your test configuration.
Delete anything that is not relevant

[x] Manual
[ ] JUnit
[ ] Jest
[ ] Cypress

Checklist:
Dev activity

[ ] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/ok-to-test

/ok-to-test


Deployment to opfs.fairdatasociety.org

So straight to mainnet ? No testing deployment ?

@darkobas2 Let's deploy the test/browser React App , let me know if you get blocked


Expand BottomSheetFragments(collapsed) when on Back Key Pressed.

Issue

None

Overview (Required)

When BottomSheetDaySessionsFragment / BottomSheetFavoriteSessionsFragment is collapsed, pressing the back-key closed the application and it was not intuitive, so I tried to expand it pressing back-key.
Apply androidx.fragment for using easy onBackKeyPress handling in fragment. But 1.1.0-alpha03 haha :)

Links

http://androhi.hatenablog.com/entry/2019/01/31/201235

Screenshot

Before
After

If you have time. Can you provide information ./gradlew frontend:android:dependencies include 1.1.0-alpha03? 🙏

ok. if you need.

@tomoya0x00 thank you!

@takahirom
Here it is!
But there is no
androidx.fragment:fragment:1.1.0-alpha03
but  androidx.fragment:fragment:1.0.0.
I must modify the build.gradle in sessions?
frontend_dependencies.txt

https://dl.google.com/dl/android/maven2/index.html
It is exists 🤔
Is Your branch collect?

oh. it's my mistake. i run it branch master.

I dit it on expand_bottomsheet_onkeybackpressed.
frontend_dependencies2.txt


Add Dbow3 Library

delete str
         -DBUILD_SHARED_LIBS=ON

Thanks for your contribution!

This is the original repository of this library... shall we change to that maybe??.......
https://github.com/rmsalinas/DBow3

Also I am not sure it really requires opencv3 and is not working with the generic opencv[contrib]

This is the original repository of this library... shall we change to that maybe??.......
https://github.com/rmsalinas/DBow3

I tried to build it on windows but it didn't go smoothly

Also I am not sure it really requires opencv3 and is not working with the generic opencv[contrib]

You are correct, but I was working with opencv3 so it asked me to rebuild the whole opencv package at the time

While I appreciate your efforts, usually it's best to link to the original repository and attach a patch to the portfile here to make it work. Personal repositories are not very well received by the downstream users (people that might want to use DBow3 but don't know you and so might assume it's a different library)

Thank you for the information
I will try to make a patch from diff in CMakelists.txt and make another PR soon

https://github.com/rmsalinas/DBow3/pull/38.patch

@Voskrese Thanks alot


q5.pop() does not restore fill properties

The following code will draw two ellipses every loop.
Expected: The first ellipse filled, the second no fill.
Got:  Using q5 both ellipses will have no fill.
( With p5.js the expected behavior is shown )
It appears that q5.pop() doesn't restore a bunch of variables such as ._noFill, and ._noStroke.
The context's .fillStyle is restored properly, but is then unused;
code:
q5 = new Q5();
q5.setup = function () {
q5.createCanvas(q5.windowWidth, q5.windowHeight);
q5.fill('#000000');
};
q5.draw = function () {
q5.clear();
q5.ellipse(100, 100, 30, 30);
q5.push();
q5.noFill();
q5.ellipse(200, 100, 30, 30);
q5.pop();
};
It appears that q5.pop() doesn't restore a bunch of variables such as ._noFill, and ._noStroke.
The context's .fillStyle is restored properly, but is then unused;

I fixed this in my upgrade to q5js!
https://github.com/quinton-ashley/q5js


Add Additional Calculations & Rolling Periods

@twiecki and friends, I'm working on the project that requires many of the same calculations that are performed in this repo, but also several others.  I am starting to work on a PR to add a variety of other statistical measures as well as a framework for getting rolling metrics on those things.
Here are a few examples of additional metrics: up-capture, down-capture, tracking-error.
Would like to add some ability to create rolling metrics. eg: Rolling 60-day Max Drawdown, Rolling 12 month Tracking Error
Before I start this work in earnest, I want to ensure that you all are open to expanding the calculation and capability set. Also, I can include a correct calculation of information ratio.

@cgdeboer That would be much appreciated and we'd be more than happy to work with you on this.

Great ! I'll post an initial PR tomorrow or early next week as a "Work In Progress" so I can get some initial thoughts from  you.


FEAT: Add Glassdoor logo data if available

Add Glassdoor logo data if available in order to have a more complete JobPost information

nice will merge later today


Automated cherry pick of #9918

Cherry pick of #9918 on release-6.5.
/cc  @M-ZubairAhmed
NONE

@M-ZubairAhmed I can't seem to be able to add the Automerge label to this. Are you able to help merge this?


unicode issue in 2.4.1, published variable in workflow is not as expected to next task.

after updated to version 2.4.1, we're encountering unicode issue again.
in mistral workflow, what has been published in previous task is not as expected to next tasks.
say if we have publish a Chinese character in task1, but it seems has been encode as input to the next task.
I attached tested code FYI (you can put them to pack: examples)
leo-test-unicode.zip

any update on this?

I see similar behaviour in 2.7.2-1
https://github.com/cheremushki/st2_test_unicode


How to configurate "toISOString()" to "toLocaleString()" in the toJSON function

in the service-proxies.ts (auto generate code)
when the type is moment
the auto gengerate code is toISOString
how to configurate it like toLocaleString or something else
my class is
export class Campaign implements ICampaign {
startTime: moment.Moment | undefined; endTime: moment.Moment | undefined; id: number | undefined;
}
and the toJSON function:
toJSON(data?: any) {
data = typeof data === 'object' ? data : {}; data["startTime"] = this.startTime ? this.startTime.toISOString() : undefined; data["endTime"] = this.endTime ? this.endTime.toISOString() : undefined; data["id"] = this.id; return data;
}
thanks!

At the moment, this is not possible and this is part of the ugliest code in the project:
https://github.com/RSuter/NJsonSchema/blob/master/src/NJsonSchema.CodeGeneration.TypeScript/DataConversionGenerator.cs#L92

thanks a lot!

It would be awesome to just have an option to specify a custom function instead of toISOString.
This way a consumer could have his own formatter by monkey patching Date.
Currently, I just post process the clients to replace the function.

Hey @RicoSuter ,
I have to admit that I have the same issue.
Was there some progress made on this issue?
Thanks mate

we have the same issue. it would be great to have customization option on to string for dates


feat: Introduce Harness URL reader and Code Repo support

Hey, I just made a Pull Request!
Introduced Harness URL reader and Code Repo support
More information on code repository https://www.harness.io/products/code-repository
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[x] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

@Rugvip @camilaibs not too sure why these checks failed:
Microsite / Microsite (pull_request)
CI / Test 18.x (pull_request)

@cjlee01 Looks like the microsite build was fixed. Please rebase https://github.com/backstage/backstage/pull/24499

@cjlee01 Looks like the microsite build was fixed. Please rebase #24499

done

CI / Test 18.x is working now but CI / Test 20.x is failing with some sort of database test flakiness. 🤔

All passing now! 😁

Can you review this again , TIA! @freben

Would you be able to review this ? @vinzscam

Thanks @freben @vinzscam for the reviews! 🙏


outputFile dropped in v0.3.4 - related to Jenkins CI integration

Reading the Karma Runner v0.13 doc to integrate with Jenkins CI, there indicates to use outputFile
But in the last version (0.3.4 index.js) I don't found this support in the code, until 0.3.3 in the index.js was loaded in line 10 and used inside  writeXmlForBrowser function
--
for now to generate report to Jenkins CI I'm using v0.2.2 and Jenkins CI config from Karma Runner v0.12
...
    // test results reporter to use
    // available reporters: https://npmjs.org/browse/keyword/karma-reporter
    reporters: ['junit', 'coverage'],

    // https://karma-runner.github.io/0.12/plus/jenkins.html
    // https://github.com/karma-runner/karma-junit-reporter
    junitReporter: {
      outputFile: 'tests_out/junit/test-results.xml'
    },

    // https://github.com/karma-runner/karma-coverage
    // https://github.com/yahoo/istanbul

    // optionally, configure the reporter
    coverageReporter: {
      type : 'lcovonly', // produces an lcov.info file
      dir : 'tests_out/coverage/',
      subdir: '.'
    },
...

Yeah, the support for this seems to have been removed in 0.3.4: https://github.com/karma-runner/karma-junit-reporter/pull/36/files#diff-168726dbe96b3ce427e7fedce31bb0bcR40
(Also, even if you were only using outputDir, the format of the output file name changed, which caused us a surprise this morning)
It is still documented though, so should really either add it back or add a note that to the changelog that it is no longer supported.

+1

+1

+1

Yes this was an oversight when I merged #36. This option should be added back in for sure. Very sorry about tha

Please checkout out #59 if that fixes the issue.

hi @Dignifiedquire thanks
reading the new code, will fix partially... because of lines 44 and 46. Why we need output the browser name? :smiley:
ps.: in v0.2.2 we can define all output path, so if I define the config:
...
    // https://karma-runner.github.io/0.12/plus/jenkins.html
    // https://github.com/karma-runner/karma-junit-reporter/tree/v0.2.2
    junitReporter: {
      outputFile: 'tests_out/junit/test-results.xml'
    },
...

this will generate the exactly output in the config: tests_out/junit/test-results.xml
but with the proposed change if I config:
...
    // https://karma-runner.github.io/0.13/plus/jenkins.html
    // https://github.com/karma-runner/karma-junit-reporter/tree/fix-output-file
    junitReporter: {
      outputDir: 'tests_out/junit',
      outputFile: 'test-results.xml'
    },
...

and for example choose the PhantomJS browser to run tests, this will generate: tests_out/junit/PHANTOMJS/test-results.xml

@erkobridee the issue is that when there are multiple browsers we need a way to distinguish different test reports, and your config file does not know anything about that. So we need to either add the browser name as a directory or to the file name.

@Dignifiedquire is it possible in somehow have one config to force this kind of output?
Thanks

@erkobridee agreed; it seems like anything after v0.2.2 breaks Jenkins integration because it won't know where to expect the file. I wonder if we need to fork junit-reporter into jenkins-reporter to restore this. (Actually I think someone has already done that...)

@evandavis @Dignifiedquire
I'm thinking... we could do like in v0.2.2 where, if we define outputFile  this will define all output path and if we define only the outputDir  this should output report per browser
well, that's my suggestion o/
What do you think? :smile:

@erkobridee That makes sense (just ran into this issue as well)
Does that mean that when setting outputFile different browser results will all be present in that single file?

@simonvanderveldt I think the problem is trying to satisfy two different use cases. On one hand, a jUnit style reporter should be able to generate reports for each browser. However, for Jenkins integration, we (likely) just need the results of a Phantom (or other headless) test where we expect the results to always be in the same place.

@simonvanderveldt like @evandavis said, when we thinking and integrating with Jenkins CI we expect only 1 file to be read by Jenkins CI (in CI server normally we have one linux serve without UI and we put tests with karma to run only in PhantomJS, so we are running Unit Tests, I don't expect any weird behavior to execute javascript among each browser) :smile:

@erkobridee
Wouldn't tests_out/junit/TESTS-PhantomJS*.xml in Jenkins together with outputDir: tests_out/junit in karma.conf.js work in that case?

It looks like there were commits that fixed this issue, what is the status of this? We look forward to a patch release.

I can understand that you need a predefined location, but the reporter will not know this, and if there are multiple browser reports written and we do not distinguish them they will overwrite each other which is really not a desired behaviour.
One thing that would be possible is to not nest the folders, but instead allow a template string, so you could write:
outputFile: 'results-${browser}.xml'
// or if you want to risk overwriting
outputFile: 'results.xml'

But please first explore if the tip from @simonvanderveldt using a glob in Jenkins solves the issue.

suite is option flag as well, perhaps the xml file should be prefixed with suite if suite is specified.

@simonvanderveldt I test you suggestion and works fine :smile:
well the actual "big" issue today is the Jenkins CI integration doc on Karma Runner v0.13 page is outdated...
so I write one little project to make some tests... and doc how to config Jenkins CI correctly

[GitHub] erkobridee / jenkins-ci-and-karma-junit-reporter - Example to execute Karma Runner through Jenkinks CI and load xml report file

releases

v0.1.0 - karma-junit-reporter v0.2.2

on post-build action to load test report xmls : tests_out/junit/*.xml

v0.2.0 - karma-junit-reporter v0.3.4

on post-build action to load test report xmls : tests_out/junit/*.xml

v0.3.0-alpha - karma-junit-reporter commit b4583b53563ea8e9e0a127705defcc8359c7635c related to #59

on post-build action to load test report xmls : tests_out/junit/**/*.xml

one weird thing I saw...
loading xml generate from v0.2.2 show only one entry

and load xml generate from v0.3.4 and the commit from #59 generate 2 entries

@simonvanderveldt @Dignifiedquire
I found the cause of duplication, see my comments for b4583b53563ea8e9e0a127705defcc8359c7635c


Made custom filter public

run gulp generate-api or just gulp to re-generate px-data-grid-api.json and include px-data-grid-api.json in this PR.

Done.

Removed generated file in order to avoid constantly appearing conflicts.


Anim optimizations

Fixes #2351
This PR optimizes the setting of animated entity properties, with particular impact to scenes with a large amount of character animations.
These optimizations were tested on a scene with 100 characters, each with an anim component & glb animations driving the character model.
Before - onAnimationUpdate ~33.6ms per frame:

After - onAnimationUpdate ~8.7ms per frame:

I confirm I have signed the Contributor License Agreement.

great job for speeding this up!


Document coupling with iMOD Coupler

iMOD Coupler is currently documented at its own page, but this will be moved to the iMOD Documentation
I think driver documentation like e.g. MetaSWAP - MODFLOW 6 coupling should be moved there too.
At the moment, the coupling documentation for Ribasim lives at the Ribasim docs.
Are we comfortable moving that to the iMOD docs?

i do not see any real objection as long as we link both ways (from Ribasim to iMod and from iMod to Ribasim)


Cannot import library

For some reason I cannot import the library even though it is in my node_modules folder (ran npm install pgvector)

Using TypeScript.

Check the following for a fix : https://github.com/pgvector/pgvector-node/issues/2#issuecomment-1491149793
Please note also my comment down the bottom as you might be in the same situation where changing the moduleResolution is a big piece of work for big projects : https://github.com/pgvector/pgvector-node/issues/2#issuecomment-1682261534

Hi @Klingefjord and @amine-mf, added support for "moduleResolution": "node" in the commit above.

Using TypeScript.

I have to use it with @ts-ignore at the top of the import, it works.


Find some way to disable older service worker code.

Having a running service worker code may cause some issues. Find a way to stop that.

Fixed in #1304


FMTLOG_BLOCK那个循环, 不会跳出来啊?

里面只有continue,没有break和return. 死循环吧?
我一运行程序就卡住了.

如果设置了FMTLOG_BLOCK则log writer会等到入队列成功才返回，如果没有其他线程poll的话确实会死循环。所以单线程程序不应该设置FMTLOG_BLOCK，这样队列满了直接丢弃并返回。

Please correct me if I'm wrong, but it seems that the OP is correct. If header is not a null pointer, then data is formatted using this header and after header->push(alloc_size) is called, the loop continues until the queue is full and then it starts looping via continue.
    do {
      auto header = threadBuffer->varq.allocMsg(alloc_size);
      if (!header) continue;
      header->logId = logId;
      char* out = (char*)(header + 1);
      // ...
      encodeArgs<0>(cstringSizes, out, std::forward<Args>(args)...);
      header->push(alloc_size);
    } while (1);

Am I missing something?

Sorry, I made a mistake in previous revision, fixed now. Thanks for notifying me.


CPaaS: CVP test fixes - minKubeVersion, duplicates in metadata

CVP CI deployment failed with the following error:
2021-11-17T08:48:07.125461845Z E1117 08:48:07.125439       1 queueinformer_operator.go:290] sync {"update" "oo-httfr/install-qzvtb"} failed: bundle unpacking failed: failed to turn bundle into steps: json: cannot unmarshal number into Go struct field ClusterServiceVersionSpec.spec.minKubeVersion of type string

Bundle metadata had a duplicate key for channel.default, it failed the rendering of the templates in the midstream.

/lgtm


Allow custom exception handling in built-in middlewares

What is the feature you are proposing?
Description
Currently, Hono's middlewares, such as csrf, throw HTTPException by default. However, there is no simple way to customize this behavior to throw a specific application-layer exception.
To achieve this, developers need to wrap the middleware with a try-catch block and rethrow a custom exception, as shown below:
const customCsrf: typeof csrf = options => {
    return createMiddleware(async (c, next) => {
        try {
            const middleware = csrf(options);
            await middleware(c, next);
        } catch (e) {
            if (e instanceof HTTPException) {
                throw new CustomException();
            }

            throw e;
        }
    });
}

const app = new Hono();

app.use(customCsrf());

While this works, it introduces unnecessary boilerplate code.
Proposed Change
Add an optional exception property to specify a custom exception class:
const app = new Hono();

app.use(csrf({ exception: CustomException }))

If an exception is provided, the middleware throws that instead of the default HTTPException. The original exception could be preserved in the cause property for debugging purposes.
Benefits

Reduces boilerplate code.
Maintains backward compatibility by defaulting to HTTPException.

I believe you can create your own custom middleware.
app.use(catchError({ exception: CustomException, middleware: csrf() }))

I believe you can create your own custom middleware.
app.use(catchError({ exception: CustomException, middleware: csrf() }))

That is also a good workaround solution!


Add java8 formula

This pull request resolves the issue #39375

[x] Named the cask according to the [token reference].
[x] brew cask install {{cask_file}} worked successfully.
[x] brew cask uninstall {{cask_file}} worked successfully.
[x] Checked there are no [open pull requests] for the same cask.
[x] Checked the cask was not already refused in [closed issues].
[x] Checked the cask is submitted to [the correct repo].

This-MacBook-Pro:~ vagrant$ brew cask install https://raw.githubusercontent.com/Juan-Moreno/homebrew-cask/feature/add-java8-formula/Casks/java8.rb
==> Downloading https://raw.githubusercontent.com/Juan-Moreno/homebrew-cask/feature/add-java8-formula/Casks/java8.rb.
######################################################################## 100.0%
==> Caveats
This Cask makes minor modifications to the JRE to prevent issues with
packaged applications, as discussed here:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=411361
If your Java application still asks for JRE installation, you might need
to reboot or logout/login.
Installing this Cask means you have AGREED to the Oracle Binary Code
License Agreement for Java SE at
https://www.oracle.com/technetwork/java/javase/terms/license/index.html
==> Satisfying dependencies
==> Downloading http://download.oracle.com/otn-pub/java/jdk/8u144-b01/090f390dda5b47b9b721c7dfaa008135/jdk-8u144-macosx-x64.dmg
######################################################################## 100.0%
==> Verifying checksum for Cask java8
==> Installing Cask java8
==> Running installer for java8; your password may be necessary.
==> Package installers may write to any location; options such as --appdir are ignored.
==> installer: Package name is JDK 8 Update 144
==> installer: Installing at base path /
==> installer: The install was successful.
🍺  java8 was successfully installed!
This-MacBook-Pro:~ vagrant$ java -version
java version "1.8.0_144"
Java(TM) SE Runtime Environment (build 1.8.0_144-b01)
Java HotSpot(TM) 64-Bit Server VM (build 25.144-b01, mixed mode)
This-MacBook-Pro:~ vagrant$ brew cask uninstall https://raw.githubusercontent.com/Juan-Moreno/homebrew-cask/feature/add-java8-formula/Casks/java8.rb
==> Downloading https://raw.githubusercontent.com/Juan-Moreno/homebrew-cask/feature/add-java8-formula/Casks/java8.rb.
######################################################################## 100.0%
curl: (22) The requested URL returned error: 416
######################################################################## 100.0%
==> Uninstalling Cask java8
==> Running uninstall process for java8; your password may be necessary
==> Removing launchctl service com.oracle.java.Helper-Tool
==> Removing launchctl service com.oracle.java.Java-Updater
==> Quitting application ID com.oracle.java.Java-Updater
==> Quitting application ID net.java.openjdk.cmd
==> Uninstalling packages:
com.oracle.jdk8u144
com.oracle.jre
==> Removing files:
/Library/Internet Plug-Ins/JavaAppletPlugin.plugin
/Library/Java/JavaVirtualMachines/jdk1.8.0_144.jdk/Contents
/Library/PreferencePanes/JavaControlPanel.prefPane
/Library/Java/Home
This-MacBook-Pro:~ vagrant$ java -version
No Java runtime present, requesting install.

Please don’t open an issue if you’re going to open the PR. The duplication is unnecessary.
java8 is in caskroom/versions: https://github.com/caskroom/homebrew-versions/blob/master/Casks/java8.rb. It’s the place for old versions.

@vitorgalvao I thought homebrew-versions is deprecated?

https://github.com/Homebrew/homebrew-versions
and
https://github.com/caskroom/homebrew-versions are different.


Add GM_BASE_ASSET_ID

Closes #559
VM PR: https://github.com/FuelLabs/fuel-vm/pull/700

We also need to update the memory initialization spec

Updated VM initilaization in 8ecaae0


Using github action cache to store downloaded terraform modules

I'm curious if we can use github cache to cache the download terraform modules of the init to be reused everytime the action runs

https://github.com/magnetikonline/terraform-github-action-cache-example

needs to be tested


[Backport 2.x] Reduce logging in DEBUG for MasterService:run

Reduce logging in DEBUG for MasterService:run (#14795)

Reduce logging in DEBUG for MasteService:run by introducing short and long summary in Taskbatcher

Signed-off-by: Sumit Bansal<EMAIL_ADDRESS>(cherry picked from commit b35690c886f42d2ca01fa3081e80cb4ba4aa19d9)

@sumitasr does this need to be backported to 2.16?  If so please add that label

@sumitasr does this need to be backported to 2.16? If so please add that label

@dbwiddis Yes, this is intended for 2.16 release. I don't have permissions to add label. This is manual backport i had to raise for original https://github.com/opensearch-project/OpenSearch/pull/14795 which had the 2.16 label.
Can you please help?


Branch urdf_parser_py for Galactic?

@clalancette objections?
This one seems easy: create a galactic-devel (matching the existing foxy-devel naming style on this repo) branch from the ros2 branch and update rosdistro to say galactic-devel is the devel branch.

I think we ended up not needing to do this.  At least, we never did, and Galactic is EOL.  We are currently using the 'ros2' branch for Humble, Iron, and Rolling without problems.  So for now, I'm going to close this out.


Bring testing tools/gems up to date

From @benjaminwood on April 9, 2018 23:40
Testing tools should be upgraded to most current versions supported by other dependencies on the master branch (under Rails 3.2).
For example: rspec, cucumber, and capybara are one or more major versions behind.
Copied from original issue: hintmedia/rigse#4

cucumber-rails is recommended to be at 1.5.0 for Rails 4.x and beyond. This will require upgrading to rspec/rspec-rails 3.x. The upgrade to rspec 3.x will require some specs to be brought up to new syntax. We have had success with using transpec gem to help with this migration.

A few PR's related to this one: #535, #534, #533. We've upgraded rspec to 2.99 and updated quite a bit of syntax. We're going to move to v3.x next.

Jasmine is removed in: #537

@emilywatkins can you discover what testing related gems remain behind their current version? I believe we have brought most gems up to data this point, but I think there are a few that are still behind by a major version.

Alright, folks. Here's the list of outdated testing-related gems:

selenium-webdriver (newest 3.14.0, installed 2.53.4, requested ~> 2.53.0)
cucumber (newest 3.1.2, installed 1.3.20, requested ~> 1.3.0)
cucumber-rails (newest 1.6.0, installed 1.3.0, requested ~> 1.3.0)
database_cleaner (newest 1.7.0, installed 0.7.2, requested ~> 0.7.2)
capybara (newest 3.6.0, installed 2.18.0)
capybara-mechanize (newest 1.11.0, installed 1.0.1, requested ~> 1.0.0)
capybara-screenshot (newest 1.0.21, installed 1.0.9)
email_spec (newest 2.2.0, installed 1.4.0, requested ~> 1.4.0)
ci_reporter (newest 2.0.0, installed 1.7.0, requested ~> 1.7.0)
delorean (newest 2.1.0, installed 1.2.0, requested ~> 1.1)
connection_pool (newest 2.2.2, installed 2.2.0)
json-schema (newest 2.8.0, installed 2.4.1)
factory_girl (newest 4.9.0, installed 3.6.2, requested ~> 3.0)
guard (newest 2.14.2, installed 2.1.1, requested ~> 2.1.1)
guard-cucumber (newest 2.1.2, installed 1.2.2, requested ~> 1.2.2)
launchy (newest 2.4.3, installed 2.1.2, requested ~> 2.1.0)

I'll get started on these now.


Asset file vanishes after loading & saving the model twice

Click to expand!
Issue Type
Bug
Source
binary
Tensorflow Version
tf 2.4
Custom Code
No
OS Platform and Distribution
Linux
Mobile device
No response
Python version
3.8
Bazel version
No response
GCC/Compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current Behaviour?
When I created the tf.Module with an asset file inside the TextFileInitializer, and save & load the module twice, the asset file will vanish after the 2nd save, and the loading will fail, complaining the absolute path of that file cannot be found.
import shutil
import tensorflow as tf

class PrimaryModule(tf.Module):
    def __init__(self, name=None):
        super(PrimaryModule, self).__init__(name=name)
        initializer = tf.lookup.TextFileInitializer(
            "chzhu_vocab.txt",
            key_dtype=tf.int64,
            key_index=0,
            value_dtype=tf.int64,
            value_index=1,
            delimiter=" ",
        )
        self.table = tf.lookup.StaticVocabularyTable(initializer, 1)

    @tf.function
    def __call__(self, inputs):
        return self.table.lookup(inputs)

model = PrimaryModule()
print(model(tf.constant([509323409], dtype=tf.int64)))
tf.saved_model.save(model, "asset_model")
imported_new = tf.saved_model.load("asset_model")
print(imported_new(tf.constant([509323409], dtype=tf.int64)))
tf.saved_model.save(imported_new, "wrapped_assets_model")

# Error when loading the model for the second time, it will be trying to find the original path
# instead of path in the asset folder inside model
shutil.rmtree("asset_model")
shutil.rm("chzhu_vocab.txt")
tf.saved_model.load("wrapped_assets_model")

Error: see full stack trace below
FileNotFoundError:  chzhu_vocab.txt; No such file or directory

When changing initializer to be self.initializer in the object constructor, it will work as normal
import tensorflow as tf

class PrimaryModule(tf.Module):
    def __init__(self, name=None):
        super(PrimaryModule, self).__init__(name=name)
        self.initializer = tf.lookup.TextFileInitializer(
            "chzhu_vocab.txt",
            key_dtype=tf.int64,
            key_index=0,
            value_dtype=tf.int64,
            value_index=1,
            delimiter=" ",
        )
        self.table = tf.lookup.StaticVocabularyTable(self.initializer, 1)

    @tf.function
    def __call__(self, inputs):
        return self.table.lookup(inputs)

# ..same saving logics

I did a deep dive into the model saving logic in TF 2.4, and found the difference here:
When saving the model for the first time, the model saver will save the object dependencies into the SavedObjectGraph:
object_graph_def in the meta_graph_def:
object_graph_def {
  nodes {
    children {
      node_id: 1
      local_name: "table"
    }
    children {
      node_id: 2
      local_name: "signatures"
    }
    children {
      node_id: 5
      local_name: "__call__"
    }
    user_object {
      identifier: "_generic_user_object"
      version {
        producer: 1
        min_consumer: 1
      }
    }
  }
  nodes {
    children {
      node_id: 3
      local_name: "_initializer"
    }
    children {
      node_id: 6
      local_name: "_create_resource"
    }
    children {
      node_id: 7
      local_name: "_initialize"
    }
    children {
      node_id: 8
      local_name: "_destroy_resource"
    }
    resource {
    }
  }
…

As we can see above, _initializer is not the attribute of the top-level object and is the child of VocabularyTable, which is a resource object. The dependency will look like object -> table -> initializer -> Asset.
During the first time loading

The Loader will try to recreate all the objects in the SavedObjectGraph,

The resource object will be recreated as _RestoredResource, which inherits the base.Trackable (not AutoTrackable).

When calling _setattr_ in the _add_object_graph_edges(), it will not update _checkpoint_dependencies (unlike normal object inheriting AutoTrackable, which override the setattr function to update the attribute dependencies.) Therefore, the table -> initializer -> Asset dependency is not entirely recovered.

During the second time saving, it will

find out the Asset objects in the object dependencies via Breadth First Traversal, and add that into asset_info.

in the _fill_meta_graph_def(), we will create asset_initializer_ops for all Assets in asset_info.

in the _fill_meta_graph_def(), the asset_initializer and its downstream variables will be written into init_ops, and the main graph will be updated to initialize the variable from the corresponding asset_initializer.

However, since in the previous loading stage, the _checkpoint_dependencies will be empty for the “table” attribute, and we cannot access the Asset object via Breadth First Traversal of the object graph. Thus we are getting empty asset_info, and 2, and 3 above will not happen.
Standalone code to reproduce the issue
import shutil
import tensorflow as tf

class PrimaryModule(tf.Module):
    def __init__(self, name=None):
        super(PrimaryModule, self).__init__(name=name)
        initializer = tf.lookup.TextFileInitializer(
            "chzhu_vocab.txt",
            key_dtype=tf.int64,
            key_index=0,
            value_dtype=tf.int64,
            value_index=1,
            delimiter=" ",
        )
        self.table = tf.lookup.StaticVocabularyTable(initializer, 1)

    @tf.function
    def __call__(self, inputs):
        return self.table.lookup(inputs)

model = PrimaryModule()
print(model(tf.constant([509323409], dtype=tf.int64)))
tf.saved_model.save(model, "asset_model")
imported_new = tf.saved_model.load("asset_model")
print(imported_new(tf.constant([509323409], dtype=tf.int64)))
tf.saved_model.save(imported_new, "wrapped_assets_model")

# Error when loading the model for the second time
shutil.rmtree("asset_model")
tf.saved_model.load("wrapped_assets_model")

Relevant log output
Traceback (most recent call last):
  File "/home/chzhu/tf2-trainer/tf2-trainer-component-training/test/asset_testing.py", line 32, in <module>
    tf.saved_model.load("custom_model/wrapped_assets_model")
  File "/home/chzhu/tf2-trainer/build/tf2-trainer-component-training/environments/development-venv/lib/python3.7/site-packages/tensorflow/python/saved_model/load.py", line 859, in load
    return load_internal(export_dir, tags, options)["root"]
  File "/home/chzhu/tf2-trainer/build/tf2-trainer-component-training/environments/development-venv/lib/python3.7/site-packages/tensorflow/python/saved_model/load.py", line 893, in load_internal
    str(err) + "\n If trying to load on a different device from the "
FileNotFoundError:  custom_model/asset_model/assets/chzhu_vocab.txt; No such file or directory
         [[{{node StatefulPartitionedCall/text_file_init/InitializeTableFromTextFileV2}}]] [Op:__inference_restored_function_body_375]

Seems that it is fixed in this commit
https://github.com/tensorflow/tensorflow/commit/59e882af21831eea9e24d74c9af4242cc1514c6e
Verified that it works in TF 2.9. Closing the issue.


wrong links to docker compose files in install

Nice idea, but it fails in the first step as the link to the compose file for ELK is not working
https://github.com/archanchoudhury/SOC-OpenSource/blob/main/installation/install1.md:
wget https://raw.githubusercontent.com/archanchoudhury/SOC-OpenSource/main/codes/elk/docker-compose.yml?token=AMFWN76WO6EJP3LVF5DVHNLBWN7KQ
404 not found

Hi, Thanks for reaching out. Yes, we had removed our custom script for
Elastic. So it wont work. Please check the official Elastic repo for ELK
installation. They have individual plus docker code as well.
On Mon, 17 Jan 2022, 4:07 pm Theta Gamma, @.***> wrote:

Nice idea, but it fails in the first step as the link to the compose file
for ELK is not working
https://github.com/archanchoudhury/SOC-OpenSource/blob/main/installation/install1.md
:
wget
https://raw.githubusercontent.com/archanchoudhury/SOC-OpenSource/main/codes/elk/docker-compose.yml?token=AMFWN76WO6EJP3LVF5DVHNLBWN7KQ
404 not found
—
Reply to this email directly, view it on GitHub
https://github.com/archanchoudhury/SOC-OpenSource/issues/2, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AMFWN7YWSI27PTODWGPR3DDUWPWN3ANCNFSM5MEKJYHQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Binary encode problem with GHC-9.0

    Binary.encode:                        FAIL
      src-test/Tests.hs:168:
      expected: "\NUL@@@@@@\146Hello \226\130\172 & \240\169\184\189!\NUL"
       but got: "\NUL\NUL\NUL\NUL\NUL\NUL\NUL\DC2Hello \226\130\172 & \240\169\184\189!\NUL"
      Use -p '/Binary.encode/' to rerun this test only.
    Binary.decode:                        FAIL
      Exception: Data.Binary.Get.runGet at position 8: not enough bytes
      CallStack (from HasCallStack):
        error, called at src/Data/Binary/Get.hs:345:5 in binary-<IP_ADDRESS>-640a90031da49036cea3bba3d7b0d12d9fcffb626f47339815976c15a4892a0e:Data.Binary.Get
      Use -p '/Binary.decode/' to rerun this test only.

It is https://gitlab.haskell.org/ghc/ghc/-/issues/19976


Replaced usages of theme.palette.theme.hint with theme.palette.text.secondary

Hey, I just made a Pull Request!
Replaced usages of theme.palette.theme.hint with theme.palette.text.secondary as it has been removed in MUI v5
Ran into this doing a MUI v5 dry run on our instance, feel it's an easy win to get in now 🚀
Related link: https://github.com/mui/material-ui-pickers/issues/1681
:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[ ] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[ ] Screenshots attached (for UI changes)
[x] All your commits have a Signed-off-by line in the message. (more info)

Thanks @jhaals ⏩ 🚀


fn_call_style = "Block" working badly with tab_spaces < 4

Having following options in rustfmt.toml:
    fn_call_style = "Block"
    max_width = 80
    # tab_spaces = 2

This snippet looks beautiful:
    fn main() {
        exceptions::config(
            move || {
                (NmiConfig {}, HardFaultConfig {}, SysTickConfig { gpio_cbsrr })
            },
        );
    }

However when tab_spaces option is uncommented, rustfmt fails fitting in max_width:
    Rustfmt failed at src/main.rs:2: line exceeded maximum length (maximum: 80, found: 96) (sorry)

Producing this snippet:
    fn main() {
      exceptions::config(move || (NmiConfig {}, HardFaultConfig {}, SysTickConfig { gpio_cbsrr }),);
    }

It is expected to be the same as the previous snippet, except a number of indent spaces.
rustfmt version is 0.8.1

This is fixed in 0.8.4.
With tab_spaces = 2, rustfmt produces the following snippet:
fn main() {
  exceptions::config(
    move || (NmiConfig {}, HardFaultConfig {}, SysTickConfig { gpio_cbsrr }),
  );
}

However, with tab_spaces = 4, the output will be:
fn main() {
    exceptions::config(
        move || {
            (NmiConfig {}, HardFaultConfig {}, SysTickConfig { gpio_cbsrr })
        }
    );
}

That is, the trailing comma after the closure is missing.

Thanks!


Update README.md

Going through the steps and updating with more detail re Ruby version and updating jekyll command.

Looks good to me!


Time remaining now configurable (default 60 seconds)

#3 will conflict with this branch in the end of the Awake() function.


REALMC-8430: Release 2.0.0-beta

went ahead and fixed up the merge here to get this moving (some of the required next testdata didn't make it through the merge)


Max: updated implementation of save_scene + small QOL improvements to host

Changelog Description
Ported version of: https://github.com/ynput/OpenPype/pull/6186
Testing notes:

Start 3dsmax
Check that on the right hand side it has defaulted to the 'create' view/menu/mode
Open the 'Publish/Create' AYON Menu
Create new 'workfile' publish
Publish
Check the log of save_scene is NOT saving if no changes to scene were made; or is saving when changes have been made (it should display INFO or DEBUG information in either case).

Thanks for the port @Sponge96 as soon as we test this, we'll merge both. Also here's a medal 🏅 for the first community contribution to the brand new ayon-core repo :D

@Sponge96 I have commented some of the codes and I think it's good to merge after resolving them as well as the conflicts.

@Sponge96 I have commented some of the codes and it's good to merge after resolving them as well as the conflicts.

Thanks Kayla. Haven't had a chance to setup ayon-core properly for development yet so apologies for missing those bits. Everything should be resolved now, might be good to run black over pipeline.py as well but didn't want to add to the changes.


Bluish Screen with prebuilt binaries and failed to start from dev

Issue
Describe your issue, comment or suggestion
Good morning,
First of all thank you so much for giving us the opportunity to play with our keyboard on linux :3
However I have some problems -
With the prebuilt binairies :
The app launches but with a bluish screen and on my terminal i have this message : Gtk-Message: Failed to load module "canberra-gtk-module"
With development :
see the reportbug below.
System versions:
nodejs:6.10.1
npm:3.10.10
libusb:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'start' ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>6 silly lifecycle<EMAIL_ADDRESS>no script for prestart, continuing
7 info lifecycle<EMAIL_ADDRESS><EMAIL_ADDRESS>8 verbose lifecycle<EMAIL_ADDRESS>unsafe-perm in lifecycle true
9 verbose lifecycle<EMAIL_ADDRESS>PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/omega/msi-keyboard-gui/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
10 verbose lifecycle<EMAIL_ADDRESS>CWD: /home/omega/msi-keyboard-gui
11 silly lifecycle<EMAIL_ADDRESS>Args: [ '-c', 'npm run build:app && electron ./dist/app' ]
12 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
13 info lifecycle<EMAIL_ADDRESS>Failed to exec start script
14 verbose stack Error<EMAIL_ADDRESS>start: npm run build:app && electron ./dist/app
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess. (/usr/lib/node_modules/npm/lib/utils/spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:886:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
15 verbose pkgid<EMAIL_ADDRESS>16 verbose cwd /home/omega/msi-keyboard-gui
17 error Linux 3.16.0-4-amd64
18 error argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
19 error node v6.10.1
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error<EMAIL_ADDRESS>start: npm run build:app && electron ./dist/app
22 error Exit status 1
23 error Failed at the<EMAIL_ADDRESS>start script 'npm run build:app && electron ./dist/app'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the msi-keyboard-gui package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     npm run build:app && electron ./dist/app
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs msi-keyboard-gui
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls msi-keyboard-gui
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]
EDIT : I restarted the manipulation, and installed the libusb tools once more, so the first method still having the same error (bluish screen) and the second method now launches the same bluish screen and same terminal error (Failed to load module "canberra-gtk-module")

What is the error when you launch the prebuilt binary and open the console? Ctrl + Shift + i


TiddlyWiki and GhostText not working together

    Setup:

Firefox 104.0.1
Vim 9.0
https://github.com/raghur/vim-ghost
Arch Linux 2022-10-22
Hey! I think there was a regression from #137 at some point because GhostText and TiddlyWiki are still not working together for me (I use vim primarily, but it still shows up with Sublime Text).
Description:
The GhostText addon tells me to click on the field I want to edit (even if there's only one on the page) and then shows a green highlight until I come back about a minute later and click something, so it goes away.
Issue:
GhostText fails to connect on a TiddlyWiki page
Steps to repeat:
This can be repeated here: https://tiddlywiki.com/. Click on the edit symbol (pencil) on one of the notes, and try to edit it through "right-click > edit with GhostText" or by clicking the addon.
I may try writing a patch for this myself since I have a little experience with writing addons, but I figured I should reopen the issue.
Originally posted by @holdenrohrer in https://github.com/fregante/GhostText/issues/137#issuecomment-1326302411

Sorry for the late answer. It seems that it does work:
https://user-images.githubusercontent.com/1402241/225029232-ac91e30c-1f16-4094-b77b-1751e2abbe15.mov
But it also occasionally fails, the script doesn't seem to be injected in the iframe. I wonder what's causing it. They have a local iframe just for the editor

So I found the answer, it's a Firefox bug: they just don't support iframes with the current permissions https://bugzilla.mozilla.org/show_bug.cgi?id=1653408


MY SQL Async wont connect.

Describe the bug
[  script:mysql-async] [mysql-async] [ERROR] connect ETIMEDOUT
[script:esx_addonacco] SCRIPT ERROR: @esx_addonaccount/server/main.lua:6: attempt to get length of a nil value (local 'result')
[MySQL] [WARNING] [esx_addonaccount] [231ms] SELECT * FROM addon_account : []
To Reproduce
not sure what this means
Expected behavior
i expected my sql to connnect, not time out. I also expext my sql to find 'result' as its there.
Screenshots / Logs
[  script:mysql-async] [mysql-async] [ERROR] connect ETIMEDOUT
[  script:mysql-async] [mysql-async] [INFO] [es_extended] Stored [0] : UPDATE users SET accounts = ?, job = ?, job_grade = ?, group = ?, position = ?, inventory = ?, loadout = ? WHERE identifier = ?
[  script:mysql-async] [mysql-async] [INFO] [es_extended] Stored [1] : INSERT INTO users SET accounts = ?, identifier = ?, group = ?
[  script:mysql-async] [mysql-async] [INFO] [es_extended] Stored [2] : SELECT accounts, job, job_grade, group, position, inventory, skin, loadout, firstname, lastname, dateofbirth, sex, height FROM users WHERE identifier = ?
[ citizen-server-impl] server thread hitch warning: timer interval of 864 milliseconds
[  script:mysql-async] [mysql-async] [INFO] [es_extended] Stored [0] : UPDATE users SET accounts = ?, job = ?, job_grade = ?, group = ?, position = ?, inventory = ?, loadout = ? WHERE identifier = ?
[  script:mysql-async] [mysql-async] [INFO] [es_extended] Stored [1] : INSERT INTO users SET accounts = ?, identifier = ?, group = ?
[  script:mysql-async] [mysql-async] [INFO] [es_extended] Stored [2] : SELECT accounts, job, job_grade, group, position, inventory, skin, loadout, firstname, lastname, dateofbirth, sex, height FROM users WHERE identifier = ?
[  script:mysql-async] [MySQL] [WARNING] [esx_addonaccount] [231ms] SELECT * FROM addon_account : []
[  script:mysql-async] [MySQL] [WARNING] [esx_addoninventory] [226ms] SELECT * FROM items : []
[  script:mysql-async] [MySQL] [WARNING] [esx_datastore] [215ms] SELECT * FROM datastore : []
[  script:mysql-async] [MySQL] [WARNING] [esx_weaponshop] [199ms] SELECT * FROM weashops : []
[  script:mysql-async] [MySQL] [WARNING] [es_extended] [191ms] SELECT * FROM jobs : []
[  script:mysql-async] [MySQL] [WARNING] [es_extended] [195ms] SELECT * FROM items : []
[  script:mysql-async] [MySQL] [WARNING] [esx_boat] [223ms] UPDATE owned_vehicles SET stored = true WHERE stored = false AND type = ? : ["boat"]
[  script:mysql-async] [MySQL] [WARNING] [esx_vehicleshop] [234ms] SELECT * FROM vehicle_categories : []
[ citizen-server-impl] -- [server notice: tebex_not_set]
[ citizen-server-impl] ================
[ citizen-server-impl] Monetize your server using Tebex! Visit https://tebex.io/fivem for more info.
[ citizen-server-impl] ================
[ citizen-server-impl]
[  script:es_extended] [INFO] ESX Legacy initialized
Software:

OS: [e.g. Windows 10]
Version of the resource [e.g. 3.3]
Database Version [e.g. MariaDB 10.4 or MySQL 8.0]

Additional context
Add any other context about the problem here.

I think you haven't added the SQL database correctly, maybe retry to add your vehicle shop and boat shop database again. It seems to be missing information here thats why it cannot select the SQL database.

There is also a script error making your database not connect on line 6 in your server main.lua...


Added BaseMappers and System Builder

Added voltage, phase and equipment base mappers
Added system_builder from distribution graph and mappers
Updated docs

Change Summary

Related issue number

Checklist

[x] The pull request title is a good summary of the changes.
[ ] Tests for the changes exist
[x] Tests pass on CI
[x] Documentation reflects the changes where applicable
[x] My PR is ready to review, please add a comment including "please review" to assign reviewers

I have not added tests for builder which requires create concrete classes for mappers. I will do that in next PR.


Enable running infracost against a terraform.tfstate file

To get costs of an existing infrastructure setup, we need to run something like:
terraform init
infracost --tfdir .

So infracost does a terraform plan internally, and then uses the output of that to generate a report. Alternatively, we can do the terraform plan manually, and then supply the output to infracost.
Either way is quite slow.
All of the information required to report on existing infrastructure will be in the terraform.tfstate JSON file for the project, so if it were possible to run something like:
infracost --terraform-statefile=/path/to/my/project/terraform.tfstate

This could enable cost reports to be generated much more quickly - I'd guess a few seconds rather than several minutes, since it shouldn't be necessary to run terraform init beforehand either.
For many use-cases, this may not be an issue, but in my particular case, with 200+ terraform projects to analyse, it makes a big difference, and I imagine some others will be in a similar situation.

Bump for that issue - I'm using TerraGrunt and split my infra in a lot of modules and the work around needed are quite painful. Using the tfstate would really help.

It could be nice if I could use a set of tfstates instead of just one. Maybe read them from cloud object storages like S3 buckets.

#203 adds a --use-tfstate flag, which might solve this use case.
So in master you can run it with
# if running dev:
make run ARGS="--tfdir=/path/to/code --use-tfstate"

# if running binary:
infracost --tfdir=/path/to/code --use-tfstate

This still needs the terraform binary to run terraform show internally instead of directly reading the state file, which is the recommended way of interacting with the state (https://www.terraform.io/docs/state/index.html#format) and has the added benefit of working with both local and remote states.
From my testing, this is a lot faster than running terraform plan each time 😄
Let me know if this helps.

I've created a new related issue here:
https://gitlab.com/infracost/infracost-gitlab-ci/-/issues/1

@ctrlaltdev / @enribd can you possibly try v0.7.2 (available on brew too), and see if the infracost --tfdir=/path/to/code --use-tfstate option is good enough to close this issue? It works with remote state. I haven't used TerraGrunt much so it would be great if you can create issues with any difficulties you hit with that.

@alikhajeh1 It works fine!
Just used on a couple of modules and I get a nice output back!
Regarding terragrunt, I'll open an issue for that.

@ctrlaltdev thanks for creating https://github.com/infracost/infracost/issues/224, given the interest in that, I've put it at the top of the todo pile in https://github.com/infracost/infracost/projects/2
Closing this issue, new issues can be created for leftovers.


Add Support for Chat Models

I have added Support for new Chat Models like gpt-3.5-turbo or gpt-4, because the old engines have been deprecated and removed rendering the previous version of the Codex-CLI not operational.
A quick overview what I have changed in this PR:

I have rewritten the codex_query.py file to now use ChatCompletions instead of normal Completions
I have removed the check for sensitive content since the Chat Models themselves refuse to give inappropriate answers
I have also introducted a system prompt for the Chat Models to better understand the context of a given request
I have replaced the usage of term engine ids with model ids in the code and in the documentation to clarify the switch to chat models
Finally I have changed the README.md to reflect change to chat models in terms of links, mentions and images

@microsoft-github-policy-service agree

@Lukas-LLS , if you enable multi_turn in current_context.config , apparently the previous executions are not being correctly saved in current_context.txt (e.g. no newlines are being created after each command execution).

Can confirm that on Microsoft/main I got Cannot find OpenAI engine: code-davinci-002. But with this PR it works fine using gpt-3.5-turbo. But idk. looks like Microsoft is not supporting this project any more?
ALSO: Could you add some more information on what the zsh-plugin does + maybe how to install. I'm fairly new to zsh, managed to install the plugin, but not quite sure what it does?


Invalid highlight name

Problem

Steps to reproduce
run fresh installation of LazyVim
Expected behavior
Successfully load plugin without errors
Neovim version (nvim -v)
v0.9.0-dev-746+g42e9a09a4

Your Neovim version is too old, please update to at least the latest stable version.

Sorry, indeed, after updating to v0.9.2 it's working. Thanks!


Alternative JSON flag

It's not always practical for JSON files for programming languages and tests to be together in the same place, right? Well, the programming language is fine, but the tests themselves would be interesting to be able to provide any custom tests that you want to use without necessarily using a directory within the repository!
The purpose of this issue is to discuss the development of a flag to inform the path of the JSON file to be read for tests, that is, the expect.json file, informing the expected inputs and outputs!

Hey @lanjoni, just to make things clear, this change would be available only to the administrators of the hackacrow instance, right? Because if not, there would be security implications since the common user would be able to bypass which tests are being run, making the check itself volatile.
Besides that, do you think a -e /random/dir/my_expect.json would be enough? In case yes, these minor requirements should be thought:

Make sure to check for syntax errors in the file
Should there be a minimum of maximum of tests per exercise?
Should the exercise suite be in pair (by amount) to the default amount? e.g. there're 11 exercises in the default exercise suite, should the be 11 as well or they're not correlated at all?

Hey @lanjoni, just to make things clear, this change would be available only to the administrators of the hackacrow instance, right? Because if not, there would be security implications since the common user would be able to bypass which tests are being run, making the check itself volatile.
Besides that, do you think a -e /random/dir/my_expect.json would be enough? In case yes, these minor requirements should be thought:
* Make sure to check for syntax errors in the file

* Should there be a minimum of maximum of tests per exercise?

* Should the exercise suite be in pair (by amount) to the default amount? e.g. there're 11 exercises in the default exercise suite, should the be 11 as well or they're not correlated at all?

Firstly, thank you very much for the answer! Know that I'm here to help you with any questions you may have during development!
Well, first of all, it is necessary to point out something that may not have been clear: hackacrow is a general purpose project, not specifically to be used on just one occasion, that is, it is a project to be developed and applied to several other occasions. projects for testing.
That said, I believe so, the point of adding a flag with the path to the test JSON file is wonderful and is exactly what we need.
What the specific flag would be has not yet been defined, however, I believe we can address this during development. Well, now to answer your questions:

"Make sure to check for syntax errors in the file": yes, we need to validate the syntax of the input JSON, so I'm thinking about creating an expect.example.json, what do you think?
"Should there be a minimum of maximum of tests per exercise?": no, the number of tests to be performed is undefined (still, and I hope it can stay that way so we don't worry for now)!
"Should the exercise suite be in pair (by amount) to the default amount? e.g. there're 11 exercises in the default exercise suite, should the be 11 as well or they're not correlated at all?": no, a number of exercises as well as the number of tests is undefined and may vary, considering that the expect.json model is nothing more than an array of values, which is why the exercises are categorized in numbers.

I hope I have clarified some points and know that I am here for any help! Thank you very much in advance!

Closed https://github.com/lanjoni/hackacrow/pull/5


Implement High/Low motion sensors

To work around Homekit shortcomings for Solar, expose as motion sensors

Added in PR which added configurable threshold based motion alerts