fix issue with path variables

Fix problems related to #3

Coverage remained the same at 100.0% when pulling 9059400f77da8bfbaf266afb1809456600ea29af on casabian:fix-issue-3 into 2ad1780edc640dfe1ae69539a65f2bcc2fee5328 on silvermine:master.

As mentioned in my comment in #3 this pull requests fixes an issue in the serverless plugin when using path variables.
There is currently no open issue in the Serverless project as i needed a quick soluition to implement xml response with a response template.

@casabian thanks for fixing the tests. Can you rebase and squash your test-fixing commit into the work commit? We like a clean commit history, as described at https://github.com/silvermine/silvermine-info/blob/master/commit-history.md
Also, please add more details to #3 explaining the exact usecase. That will help people who are looking for or find this issue in the future.
Thanks!

Closing because:

the requested changes were not made, and
more importantly, this plugin is not recommended any more, as explained in #3


Add pod ip and node column in Pods table

What would you like to be added:
Pod IP and Node columns in the Pods table, similar to what is shown in kubectl get pods -o wide.
Why is this needed:
Pod IP and node name are key pieces of information about a running pod.

This can be implemented after we have https://github.com/lensapp/lens/issues/601.

The pod IP is a very useful information. It would be nice to have it in the pod overview tab.

2023: Any updates?

Any updates?


Removal of the default intel config include

That was overlooked during introducing the config module.
Fixes compilations with intel 2019 update 4

@m-diers Please get in contact with @aserio if you are interested in receiving one of our STE||AR-Group t-shirts. We give those away to our first time contributors.


[PORT] Revert the reusing of json converters

Port this change from botbuilder-dotnet/master branch:
https://github.com/microsoft/botbuilder-dotnet/pull/3783

Description
Fixes https://github.com/microsoft/botbuilder-dotnet/issues/3769 TestBot.Json broken in master
Context
https://github.com/microsoft/botbuilder-dotnet/pull/3711 introduced a cache for json converters, in which json converters are created once when converting first json, and reused in later json conversion.
The issue is, those json converters are stateful, in which SourceContext captured the state (the call stack).  In order to make it work as expected, the call stacked must be initialized with a SourceRange pushed to bottom of the stack, and this initialization only happens when creating those converters.
So reusing the converters will not re-initializing the state, in this specific case, will not push a SourceRange into stack.  Then all the following source range registering will not get a path value, and fail to load.
Fix
The fix in this PR is simply reverting the cache and reusing behavior of converters.
If for performance reason or any other reasons we want to reuse the converters, we need an approach to reset the converters with state. Could simplify be making a sub-class of JsonConverter and add a reset method, or other approach.
Anyhow, leave the systematic to @tomlm or @willportnoy.
Changed projects

Microsoft.Bot.Builder.Dialogs.Declarative
Microsoft.Bot.Builder.TestBot.Json

@boydc2014, does this apply to JS? Can you close it if it doesn't.

We don't have this in JS, closing this issue.


docs: embedded a youtube video component

Description

Added an MDX YouTube component to the getting-started page of Docs section.

The component embeds a YouTube video to the home of Docs section.

Related issue(s)
Fixes #408

@alequetzalli do you want to have a look as docs owner, any objection?
@boyney123 you reported an issue initially, all good from your side?

@derberg I actually decided it makes sense to close this PR because:

We should not be adding a YT video to the Docs unless it aligns w/ page and our new IA content goals: This is a Postman-themed video that no doubt has great content, but it does not have a place in our Intro Docs section.
This PR is not in response to an issue that has been created and approved by community discussion to integrate this change into Docs.

@sambhavsaxena This video doesn't really align w/ our Docs, and in order to make a contribution to the Docs, we need to first create an issue that is tagged in the Docs Board here. 🙂
In this example, if you found a video that had content that was specifically in alignment w/ a page's content, you first need to create an issue to propose your change and new idea. 💡 🙂 This is actually part of our contribution guidelines as you can see more here.
In addition, let me point you also to also read here and here, about our latest changes to our Docs Information Architecture (IA), because it will help you get a better understanding and context on what content we want to add. ❤
If you get more ideas or want to ask me more questions about Docs' contributions, just let me know! 😀👍🏽

Not a problem @alequetzalli, I'll look for other issues. Thanks for consideration.


Says module.exports is undocumented when it is documented

inch-ci says module.exports is undocumented when in reality it is documented:
https://github.com/ArtskydJ/tweet-tweet#tweettweetauth

Re: ArtskydJ/tweet-tweet

Hi Joseph,
Inch is for Inline Docs a.k.a. documentation inside your code in the form of comments. Since you seem to side with this guy ditching inline docs I am afraid there is nothing Inch can do for you! :sob:

Sorry, should've seen it was for inline docs.
Thanks for the response!


JSON link dead

Looks like
https://joe-birch-dsdb.squarespace.com/s/team-abk9.json
is not there anymore...

Oops sorry about that! Is fixed now :)

Looks like it went down again :)

Hi guys, Looks like https://joe-birch-dsdb.squarespace.com/s/team-abk9.json went down again, could you please update it?

Related issue: https://github.com/bufferapp/android-clean-architecture-boilerplate/issues/54

Anyone can send me json file ???


Convert colors to use hsl/hsla

It's more convenient to modify these and they feel more natural to the
human mind.
Numbers were slightly rounded after conversion for convenience with
barely noticeable changes.
I know you disagreed on this change, so I made sure to do this in its own PR.

Yea, I'm closing this one. Rounding colors is heresy 😋 They also don't need to be readable or intuitively understandable either.

Rounding colors is heresy

Got any sources on how that actually affects things or is it just out of principle?

It's just principle. I picked those colors in LCH color space. They're represented in sRGB space in the stylesheet because that's the "default" and they don't need to be readable anyway, as I said, since they aren't code. Converting them to HSL and then rounding them just seems nonsensical.

Why not use lch() directly, then?

Support for that is still a tad too recent for my taste.


bridge deployment don't support custom L1 RPC

Background & motivation
https://github.com/0xPolygon/kurtosis-cdk/blob/769c4674681e7386c9819a6506b6e22a3a4bc589/cdk_bridge_infra.star#L133
When I deploy bridge using custom L1, script didn't use the custom L1 RPC
Desired behaviour
Hope to support custom L1 RPC
How important is this to you?
Nice to have; This feature would make using Kurtosis CDK more enjoyable.

If the goal is to test bridging between Lx and Ly (not the deployment of the bridge-ui), you could try using:

polycli ulxly deposit-new to make a deposit from Lx to Ly
polycli ulxly deposit-get to view the pending deposits
polycli ulxly deposit-claim to make the pending claims

Its a cli tool which abstracts away the bridging contract calls without having to spin up a bridge-ui.

@cachalots if you are deploying to Sepolia as the L1, you need to make the following changes:
Inside cdk_bridge_infra.star, comment out the following lines:
    # l1rpc_service = plan.get_service("el-1-geth-lighthouse")

                    # "l1rpc_ip": l1rpc_service.ip_address,
                    # "l1rpc_port": l1rpc_service.ports["rpc"].number,

Inside haxproxy.cfg, comment out the following lines:
    # acl url_l1rpc path_beg /l1rpc

    # use_backend backend_l1rpc if url_l1rpc

# backend backend_l1rpc
#     http-request set-path /
#     server server1 {{.l1rpc_ip}}:{{.l1rpc_port}}

You can see at this timestamp of my video tutorial I run into and address the same issue you are facing.

@cachalots if you are deploying to Sepolia as the L1, you need to make the following changes:
Inside cdk_bridge_infra.star, comment out the following lines:
    # l1rpc_service = plan.get_service("el-1-geth-lighthouse")

                    # "l1rpc_ip": l1rpc_service.ip_address,
                    # "l1rpc_port": l1rpc_service.ports["rpc"].number,

Inside haxproxy.cfg, comment out the following lines:
    # acl url_l1rpc path_beg /l1rpc

    # use_backend backend_l1rpc if url_l1rpc

# backend backend_l1rpc
#     http-request set-path /
#     server server1 {{.l1rpc_ip}}:{{.l1rpc_port}}

You can see at this timestamp of my video tutorial I run into and address the same issue you are facing.

got it, but I‘m not sure if comment out these will result in some features being unavailable?

Hi @cachalots, have you managed to get it working?

Hi @cachalots, have you managed to get it working?

I successfully deployed it in Sepolia, but the zkEVM bridge deposit has been unable to be credited. The status has always been processing

@cachalots could you clarify which method you are using to make the bridge deposits? There is the hermez bridge-ui, the simple bridge-ui, and the polycli commands above.
The hermez bridge-ui may have an issue when using it on Sepolia, making the transactions stuck on processing forever. You could directly invoke the bridge smart contracts using the simple bridge-ui or the polycli commands which have been tested to work on Sepolia.

@jhkimqd I used the bridge-ui deployed by kurtosis-cdk, the docker image is leovct/zkevm-bridge-ui:multi-network, after seeing your reply, I tried using simple bridge-ui for depoist, but the result was the same. L2 didn't receive ETH.
call {haproxy}/bridgeservice/bridges/{address} response: {"deposits":[], "total_cnt":"0"}

Closing this issue as it should be fixed now.


test(mempool): flow test with a happy flow scenario

This change is

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

Project coverage is 83.20%. Comparing base (c9f77e7) to head (24688f8).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #517   +/-   ##
=======================================
  Coverage   83.20%   83.20%
=======================================
  Files          37       37
  Lines        1786     1786
  Branches     1786     1786
=======================================
  Hits         1486     1486
  Misses        222      222
  Partials       78       78

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


chore: Fix latest clippy warnings

Seems there's a lot new lints added upstream. This PR simply fixes the new warnings

This is not needed once we merge #147


NodeMCU would not connect to WiFi

Hey,
I was trying to implement your project but my NodeMCU wouldn't connect to my WiFi (WPA-PSK)
I was running it on Arduino IDE 1.8.5
Esp8266 v2.3.0
NodeMCU lolin V3

Well... Did you configure your SSID/PASS/IP/GATEWAY etc. correctly?

Can you give us a little more info?

Hey,
I had figured it out by changing my router configuration. It was not able to assign the ip address. It's working now. But at times it still doesn't connect at a single go.

had the same mistake, choose NodeMCU 1.0 (ESP-12E). it helped me

Can you close this if it’s solved?


iOS: More than 34 errors when I tried to build the app on iOS after finishing all the steps

Current Behavior

I'm working on a new app and stuck with this library.
I'm using this library to get a preview of the video before uploading to the storage, and it is working fine on android, but on iOS, I followed the instructions and got a lot of errors after cleaning and building the project.
Some of the errors:
'kCMTimeZero' has been renamed to 'CMTime.zero'
Missing argument labels 'value:timescale:' in call
'AVFileTypeMPEG4' has been renamed to 'AVFileType.mp4'
and more
Expected Behavior

It should work as @shahen94 explained in the instructions.
Your Environment

software
version

react-native-video-processing
1.20.0

react-native
0.61.5

react
16.9.0

node
10.16.0

I'm using React Native 0.59.10 & Xcode 11.3.1 and the only way I was able to make it work was by directly including the two projects like this.

Also, you'll have to comment 'resize mode' object and props. Just comment out the changes done here: https://github.com/shahen94/react-native-video-processing/pull/240/commits/68eefa82f76bd8e84825746e3ba3f1cbdec68850

@xlogix I'm having this issue when following this approach:

RN 60:
    "expo": "^36.0.0",
    "react-native": "https://github.com/expo/react-native/archive/sdk-36.0.1.tar.gz",

@n-sviridenko Use this repo's code: https://github.com/xlogix/react-native-video-processing

I do everything as indicated in the instructions and in this issues, but I get 61 errors
react-native-video-processing | 1.20.0
react-native | 0.61.4

@xlogix I'm having this issue when following this approach:

RN 60:
    "expo": "^36.0.0",
    "react-native": "https://github.com/expo/react-native/archive/sdk-36.0.1.tar.gz",

Are you running a Managed Expo project? Were you able to get it working?


new modules: kube security groups

Add three new security group modules, one each for the Kube Controller, Worker, and Load Balancer.
For example, for the Kube Controller, extract https://github.com/fpco/terraform-aws-foundation/blob/09af3018b4c9058544cf432de4720ec81e7fda96/examples/kube-stack-private/kube.tf#L41-L73 into a new module, parametize the details like CIDR and name (following conventions with our other modules, like variable names and such), and update the example env (in the previous link and its "public" counter-part) to use the new module.
Repeat the same process for the Kube Worker - https://github.com/fpco/terraform-aws-foundation/blob/09af3018b4c9058544cf432de4720ec81e7fda96/examples/kube-stack-private/kube.tf#L75-L93 - and the Kube Load Balancer - https://github.com/fpco/terraform-aws-foundation/blob/09af3018b4c9058544cf432de4720ec81e7fda96/examples/kube-stack-private/kube.tf#L94-L113.

I have opened #94 to take this one over the hill (closing in favor of the new PR)

This has been merged to master!


Generic Response Object Serialization

I'm attempting to create a 'Generic Response Object Serialization' deserializer for Alamofire.
Because there is no common protocol that generated messages implement, I tried to use the type specification of GeneratedMessageBuilder.  However, the code blows up here.
This is an example of the serializer I tried to implement.
extension Alamofire.Request {
    public func responseProtocolBuffer<T: GeneratedMessageBuilder>(completionHandler: (NSURLRequest, NSHTTPURLResponse?, T?, NSError?) -> Void) -> Self {
        let serializer: Serializer = { (request, response, data) in
            if response != nil && data != nil {
                let returnValue = T().mergeFromData(data!)

                return (returnValue, nil)
            } else {
                return (nil, nil)
            }
        }

        return response(serializer: serializer, completionHandler: { (request, response, object, error) in
            completionHandler(request, response, object as? T, error)
        })
    }
}

I think the ultimate solution is to have a GenerateMessageProtocol, that all generated messages adhere to.  Perhaps something like:
protocol GenerateMessageProtocol {
    class func parseFromData(data:NSData) -> self
    //etc.
}

And then GeneratedMessages could look like:
final internal class CPBVersion : GeneratedMessage, GenerateMessageProtocol {
   //xxx
}

Ok! I am agree!

If we can't use Swift Protocol Buffers at the same time, and if it's not a drop in replacement for Objective C then we'll want a similar implementation of the protocol idea in Objective C.

Done.


Broken regex when using trailing slash in the dir name on MANIFEST.in

The sign command breaks when using a trailing slash in the dir name on MANIFEST.in.
💚 Condition that works
MANIFEST.in:
recursive-include playbooks *.yml

Command:
(global) [luiz@workstation ansible-test-content]$ ansible-sign project gpg-sign .

❤ Condition that fails
MANIFEST.in:
recursive-include playbooks/ *.yml

Command:
(global) [luiz@workstation ansible-test-content]$ ansible-sign project gpg-sign .
> [2022-08-30 09:15:56] WARNING:distlib.manifest:no files found matching '*.yml' under directory 'playbooks/'

We rely on distlib.manifest for the MANIFEST.in behavior and this behavior is coming directly from that library. I don't think there is anything for us to do here.


Homebrew formula?

I see the note on the README re: the package manager support upcoming.
Is this something you need help with? I've never created a homebrew formula, but since my first thought on reading the HN article was whether I could brew install it, I guess it might be important.
If you're not already working on that in an outstanding branch, it sounds straightforward enough that I could maybe give it a shot and give you a PR for one hosted in your own repo as a tap.

Greetings @geoelectric !
I am not currently working on it and could definitely use the help!
Please feel free to fork the project and create a "brew" branch (or somesuch) - I'd love to see the PR and learn about the process - I use brew as well and feel a little bad that I don't already know how to create brew formula from go packages.
Thank you for the offer and please let me know if you have any other questions need any help!

Homebrew maintainer here.
I can make a formula for this project and make a PR to homebrew-core, but first you would need to make a release, because Homebrew does not allow unversioned projects generally.

I'm sure having something directly in homebrew-core would be advantageous over the private tap, so I'll wait for some guidance on how @TekWizely wants to proceed with that.
In the meantime, I'll start looking into how to spin a formula for a go project, because I still want to know how to do it for myself!

Just have a look at man page of brew create.

Greetings @dawidd6 !
I appreciate your willingness to help!
I have two issues I want to resolve (#3 and #7) and then I think we'll be in a good place to cut a release.
OTOH, maybe I should just make one with the current code to keep things moving.
Q: Can I just use the standard github Release mechanism or do I need specific assets in the release?
Lemme know and thanks again - I'm very excited about this !
-TW

Just a plain git tag or github release are fine.

OK Release v.0.5.1 has been cut !

https://github.com/TekWizely/run/releases/tag/v0.5.1

Please let me know if I can do anything else to help, thanks!

PR is up: https://github.com/Homebrew/homebrew-core/pull/48100

This was pretty impressive collaboration. I’m glad I at least created a thread!
@TekWizely — looks like you’re covered here, but I’ll try to find other ways to contribute. I really like what you’re building.

@dawidd6 Woot! I have subscribed to the PR thread
Q: Do you need anything else from me in regards to the PR?  I.e comments, code changes, etc?
@geoelectric Thanks a lot for getting this thread started !  We both learned more about packaging projects for brew :)
Please let me know how Run holds up as you put it through some real-world scenarios.  I'm planning to start a Runfile repository as patterns and use-cases emerge, so I'd love to see what you come up with.

Q: Do you need anything else from me in regards to the PR? I.e comments, code changes, etc?

@TekWizely not at this moment, thanks.

@dawidd6 I did a warning on that in your original PR:

Warning: Generic binaries were installed to "/home/linuxbrew/.linuxbrew/opt/run/bin"
Binaries with generic names are likely to conflict with other software,
and suggest that this software should be installed to "libexec" and then
symlinked as needed.

Can you explain the libexec suggestion?  Is that something to consider?
run doesn't appear to be an existing linux command from my research, and I do very much like the name, so 🤞 we can use it.

It's been already adjusted in brew itself. Just need to wait for a maintainer to approve the PR and run will be available to install!

OK Run is now officially on Brew Core !
I have also updated the README with instructions.
Thank you @dawidd6  and @geoelectric for the help !


Verus crashes on startup trying to allocate too much memory

2024-10-01-13-51-30.zip
Verus fails with message memory allocation of<PHONE_NUMBER>994162 bytes failed (note that this is trying to allocate >5PB) on an empty example file containing only an import and an empty verus! block (and any file I tried containing additional code). Archive produced by --record is attached. This happens with both debug and release builds. This is the piece of code it fails on:
use vstd::prelude::*;

verus! {

}

The bug doesn't occur with the previous commit (25303cd2eabd3c16aa6e5302e18272acbf51c660).

Huh, that's very strange behavior!  It sounds like you're using Verus commit 3c05f3cbe6, right?  When I try it on the example file in your report, I see the expected:
$ verus github-1294/example.rs                     [3c05f3cb]
error[E0601]: `main` function not found in crate `example`
 --> github-1294/example.rs:5:2
  |
5 | }
  |  ^ consider adding a `main` function to `github-1294/example.rs`

error: aborting due to 1 previous error

and if I add the appropriate flag, I see:
$ verus --crate-type=lib github-1294/example.rs    [3c05f3cb]
verification results:: 0 verified, 0 errors

This is on macOS Sonoma 14.4.1.
Do you mind sharing more about your setup?

I think I didn't rebuild all the verus components correctly (running vargo build -p verus rather than just vargo build). The issue disappeared after a proper rebuild

Okay, glad to hear you found a simple resolution!


Support alpha numeric strings in transfer id

Business requirement: accounting packages require alphanumeric memo ids

CC @MParlikar

@Fraser999 this surely needs to be done


information of NTIRE 2024 LLIE dataset

Hello.
In the "Prepare Dataset" content, you described that "NTIRE 2024", and I found the "NTIRE Challenge on Low Light Image Enhancement" paper here; https://arxiv.org/pdf/2404.14248v1 . In that paper, they mentioned that there are 230 pairs of training data and 35 for validation. However, in your link of "mini_val", there are only 15 images. How did you manage the dataset?
I'd be happy if you tell me about this. Thank you.

Hi, thanks for your interest.
the minival dataset are split from the 230 training pairs and the 35 validation pairs are not used in this repo because when I released the code of NTIRE part, the validation data were not released. People still competed in the NTIRE challenge. You can directly use the original training and testing sets or just follow our repo.
If you find our repo useful, please help us star it, thank you :)


Outdated pattern for deltatick as of 8/8

The pattern for dwNetworkGameClient_deltaTick is outdated.
Log:
23:12:28 [INFO] found 16 buttons
23:12:29 [INFO] found 132 interfaces across 35 modules
23:12:31 [ERROR] outdated pattern: dwNetworkGameClient_deltaTick
23:12:31 [INFO] found 32 offsets across 5 modules
23:12:32 [INFO] found 2329 classes and 342 enums across 17 modules
23:12:32 [INFO] analysis completed in 3.571333 seconds
will still dump but its not included

dwGameTypes_mapName: usize = 0x120;

Download the latest release.


Clarification of NUMBER Oracle datatype

I changed the Oracle type mapping reference section to reflect how SQL Server datatype for NUMBER Oracle datatype depends on if NUMBER is using precision or not. If Oracle datatype is NUMBER (no precision), we need to use Float for SQL Server. If Oracle NUMBER is defined with precision (NUMBER (p, s)), then SQL Server needs to use Decimal (p, s).

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


The project already transitively references the target project.

1. Describe the bug
I am getting the following error on open of my workspace
2. To Reproduce
Not sure what about this project causes this error. I tried to reproduce in a simple project and the error does not occur. If I open a folder from my workspace separately, also no error.
[Error - 11:58:14] Please report this issue to https://github.com/microsoft/al/issues including information on how to reproduce it, if possible.
Processing of message 'workspace/didChangeConfiguration' failed with error: 'The project already transitively references the target project.'
Details:
System.InvalidOperationException: The project already transitively references the target project.
   at Microsoft.Dynamics.Nav.CodeAnalysis.Workspaces.Solution.CheckNotContainsTransitiveReference(ProjectId fromProjectId, ProjectId toProjectId) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis.Workspaces\Workspace\Solution\Solution.cs:line 2296
   at Microsoft.Dynamics.Nav.CodeAnalysis.Workspaces.Solution.AddProjectReference(ProjectId projectId, ProjectReference projectReference) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.CodeAnalysis.Workspaces\Workspace\Solution\Solution.cs:line 854
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.VsCodeWorkspace.AddCurrentProjectAsAProjectDependency(String dependencyParentProjectPath, Solution oldSolution) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\VsCodeWorkspace.cs:line 981
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.VsCodeWorkspace.UpdateDependencies(IEnumerable`1 references, String packageCachePath, String[] assemblyProbingPaths, String ruleSetPath, CompilationOptions newCompilationOptions, ParseOptions newParseOptions, String dependencyParentProjectPath, ProjectDefinition projectDefinition, IEnumerable`1 internalsVisibleToModules, ImmutableArray`1 analyzerReferences, Boolean isBackgroundCodeAnalyzersEnabled, Boolean enableCodeActions, Boolean incrementalBuild) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\VsCodeWorkspace.cs:line 999
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.VsCodeWorkspace.AddOrUpdateProjectFromPath(Settings settings, Boolean forceCheckDependencies, List`1& projectLoadingDiagnostics, Boolean& missingSymbols) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\VsCodeWorkspace.cs:line 162
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.VsCodeWorkspace.TryAddOrUpdateProject(Settings settings, IList`1& diagnostics, ProjectManifest& manifest, Boolean& missingSymbols) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\VsCodeWorkspace.cs:line 73
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.LanguageServer.ProjectRequestHandler`1.TryAddOrUpdateProject(SettingsRequest request, CancellationToken cancellationToken, ProjectManifest& manifest) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\LanguageServer\ProjectRequestHandler.cs:line 53
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.LanguageServer.DidChangeConfigurationRequestHandler.HandleAsync(SettingsRequest request, Int32 requestId, CancellationToken cancellationToken) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\LanguageServer\DidChangeConfigurationRequestHandler.cs:line 73
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.MessageProtocol.RequestHandlerBase`1.HandleAsync(JToken requestContents, Int32 requestId, CancellationToken cancellationToken) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\MessageProtocol\RequestHandlerBase.cs:line 63
   at Microsoft.Dynamics.Nav.EditorServices.Protocol.RequestRegistry.Process(Message message) in D:\a\1\s\source\Prod\Microsoft.Dynamics.Nav.EditorServices.Protocol\Endpoints\RequestRegistry.cs:line 64

Note: Because the developers need to copy and paste the code snippet, including a code snippet as a media file (i.e. .gif) is not sufficient.
3. Expected behavior
A clear and concise description of what you expected to happen.
4. Actual behavior
A clear and concise description of what happened accompanied by images, animations, or a link to a video showing the issue occurring
5. Versions:

AL Language: v7.4.502459
Visual Studio Code: 1.60.2
Business Central: /
List of Visual Studio Code extensions that you have installed: Only AL Language activated

I found the problem. I created a dependency loop by accident. A > B > A.


Allow setting background color and defaultStrokeOpacity as props

Since the background color was set to white, the component does not look
good in different backgrounds. Additionaly, the default path opacity
(0.2) is too transparent for light backgrounds.
This commit exposes properties to configure those parameters.

hope it gets reviewed and merged soon

Hey Gonçalo!
Sorry for not responding quickly, I have been working on functionality that was requested of me from a student in Denmark. As for the setting of background color and opacity, I actually provide a callback in which you can pass a custom styling function that the map then uses to style everything around it. For context, I suggest looking at the example under the custom-styling-example in the examples folder or looking at this commit to see how I used the custom styling function within the example itself. The commit is here if you want to check it out: https://github.com/yanivam/react-svg-worldmap/commit/511b0e60d697a83f78307aa8f7f3b3eba6f6f41f. Let me know if you need help using the styling function, if that doesn't work, I am leaving this open just in case until we resolve this issue, does that sound good?
Let me know,
-Yams

Hi! Don't worry, take your time. I can rely on this branch for now :)
I knew about the style function, and maybe I'm missing something but it seems that the function is only invoked if for the country that is highlighter.
Also, the backgroundColor is set on the container div and is hardcoded to "white".
With that being said, I'm a backed dev and don't know much about javascript, so it's possible that I'm missing something


Greenkeeper/initial

:tada: This PR is included in version 2.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


server model

Signed-off-by: Julien Le Dem<EMAIL_ADDRESS>

the new classes look like this:
package io.openlineage.server;

import com.fasterxml.jackson.annotation.JsonAnyGetter;
import com.fasterxml.jackson.annotation.JsonAnySetter;
import com.fasterxml.jackson.annotation.JsonCreator;
import com.fasterxml.jackson.annotation.JsonProperty;
import com.fasterxml.jackson.annotation.JsonPropertyOrder;
import java.lang.Object;
import java.lang.String;
import java.net.URI;
import java.time.ZonedDateTime;
import java.util.LinkedHashMap;
import java.util.List;
import java.util.Map;
import java.util.UUID;

public final class OpenLineage {
  @JsonPropertyOrder
  public static final class RunFacets {
    @JsonAnySetter
    private final Map<String, RunFacet> additionalProperties;

    @JsonCreator
    private RunFacets() {
      this.additionalProperties = new LinkedHashMap<>();
    }

    /**
     * @return additional properties
     */
    @JsonAnyGetter
    public Map<String, RunFacet> getAdditionalProperties() {
      return additionalProperties;
    }
  }

  @JsonPropertyOrder({
      "eventType",
      "eventTime",
      "run",
      "job",
      "inputs",
      "outputs",
      "producer",
      "schemaURL"
  })
  public static final class RunEvent {
    private final String eventType;

    private final ZonedDateTime eventTime;

    private final Run run;

    private final Job job;

    private final List<InputDataset> inputs;

    private final List<OutputDataset> outputs;

    private final URI producer;

    private final URI schemaURL;

    /**
     * @param eventType the current transition of the run state. It is required to issue 1 START event and 1 of [ COMPLETE, ABORT, FAIL ] event per run. Additional events with OTHER eventType can be added to the same run. For example to send additional metadata after the run is complete
     * @param eventTime the time the event occurred at
     * @param run the run
     * @param job the job
     * @param inputs The set of **input** datasets.
     * @param outputs The set of **output** datasets.
     * @param producer URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     * @param schemaURL The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this RunEvent
     */
    @JsonCreator
    private RunEvent(@JsonProperty("eventType") String eventType,
        @JsonProperty("eventTime") ZonedDateTime eventTime, @JsonProperty("run") Run run,
        @JsonProperty("job") Job job, @JsonProperty("inputs") List<InputDataset> inputs,
        @JsonProperty("outputs") List<OutputDataset> outputs,
        @JsonProperty("producer") URI producer, @JsonProperty("schemaURL") URI schemaURL) {
      this.eventType = eventType;
      this.eventTime = eventTime;
      this.run = run;
      this.job = job;
      this.inputs = inputs;
      this.outputs = outputs;
      this.producer = producer;
      this.schemaURL = schemaURL;
    }

    /**
     * @return the current transition of the run state. It is required to issue 1 START event and 1 of [ COMPLETE, ABORT, FAIL ] event per run. Additional events with OTHER eventType can be added to the same run. For example to send additional metadata after the run is complete
     */
    public String getEventType() {
      return eventType;
    }

    /**
     * @return the time the event occurred at
     */
    public ZonedDateTime getEventTime() {
      return eventTime;
    }

    public Run getRun() {
      return run;
    }

    public Job getJob() {
      return job;
    }

    /**
     * @return The set of **input** datasets.
     */
    public List<InputDataset> getInputs() {
      return inputs;
    }

    /**
     * @return The set of **output** datasets.
     */
    public List<OutputDataset> getOutputs() {
      return outputs;
    }

    /**
     * @return URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     */
    public URI getProducer() {
      return producer;
    }

    /**
     * @return The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this RunEvent
     */
    public URI getSchemaURL() {
      return schemaURL;
    }
  }

  @JsonPropertyOrder
  public static final class JobFacets {
    @JsonAnySetter
    private final Map<String, JobFacet> additionalProperties;

    @JsonCreator
    private JobFacets() {
      this.additionalProperties = new LinkedHashMap<>();
    }

    /**
     * @return additional properties
     */
    @JsonAnyGetter
    public Map<String, JobFacet> getAdditionalProperties() {
      return additionalProperties;
    }
  }

  @JsonPropertyOrder
  public static final class InputDatasetInputFacets {
    @JsonAnySetter
    private final Map<String, InputDatasetFacet> additionalProperties;

    @JsonCreator
    private InputDatasetInputFacets() {
      this.additionalProperties = new LinkedHashMap<>();
    }

    /**
     * @return additional properties
     */
    @JsonAnyGetter
    public Map<String, InputDatasetFacet> getAdditionalProperties() {
      return additionalProperties;
    }
  }

  @JsonPropertyOrder({
      "_producer",
      "_schemaURL"
  })
  public static final class DatasetFacet implements BaseFacet {
    private final URI _producer;

    private final URI _schemaURL;

    @JsonAnySetter
    private final Map<String, Object> additionalProperties;

    /**
     * @param _producer URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     * @param _schemaURL The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this facet
     */
    @JsonCreator
    private DatasetFacet(@JsonProperty("_producer") URI _producer,
        @JsonProperty("_schemaURL") URI _schemaURL) {
      this._producer = _producer;
      this._schemaURL = _schemaURL;
      this.additionalProperties = new LinkedHashMap<>();
    }

    /**
     * @return URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     */
    public URI get_producer() {
      return _producer;
    }

    /**
     * @return The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this facet
     */
    public URI get_schemaURL() {
      return _schemaURL;
    }

    /**
     * @return additional properties
     */
    @JsonAnyGetter
    public Map<String, Object> getAdditionalProperties() {
      return additionalProperties;
    }
  }

  @JsonPropertyOrder({
      "_producer",
      "_schemaURL"
  })
  public static final class OutputDatasetFacet implements BaseFacet {
    private final URI _producer;

    private final URI _schemaURL;

    @JsonAnySetter
    private final Map<String, Object> additionalProperties;

    /**
     * @param _producer URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     * @param _schemaURL The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this facet
     */
    @JsonCreator
    private OutputDatasetFacet(@JsonProperty("_producer") URI _producer,
        @JsonProperty("_schemaURL") URI _schemaURL) {
      this._producer = _producer;
      this._schemaURL = _schemaURL;
      this.additionalProperties = new LinkedHashMap<>();
    }

    /**
     * @return URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     */
    public URI get_producer() {
      return _producer;
    }

    /**
     * @return The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this facet
     */
    public URI get_schemaURL() {
      return _schemaURL;
    }

    /**
     * @return additional properties
     */
    @JsonAnyGetter
    public Map<String, Object> getAdditionalProperties() {
      return additionalProperties;
    }
  }

  @JsonPropertyOrder
  public static final class DatasetFacets {
    @JsonAnySetter
    private final Map<String, DatasetFacet> additionalProperties;

    @JsonCreator
    private DatasetFacets() {
      this.additionalProperties = new LinkedHashMap<>();
    }

    /**
     * @return additional properties
     */
    @JsonAnyGetter
    public Map<String, DatasetFacet> getAdditionalProperties() {
      return additionalProperties;
    }
  }

  @JsonPropertyOrder({
      "runId",
      "facets"
  })
  public static final class Run {
    private final UUID runId;

    private final RunFacets facets;

    /**
     * @param runId The globally unique ID of the run associated with the job.
     * @param facets The run facets.
     */
    @JsonCreator
    private Run(@JsonProperty("runId") UUID runId, @JsonProperty("facets") RunFacets facets) {
      this.runId = runId;
      this.facets = facets;
    }

    /**
     * @return The globally unique ID of the run associated with the job.
     */
    public UUID getRunId() {
      return runId;
    }

    /**
     * @return The run facets.
     */
    public RunFacets getFacets() {
      return facets;
    }
  }

  public interface Dataset {
    /**
     * @return The namespace containing that dataset
     */
    String getNamespace();

    /**
     * @return The unique name for that dataset within that namespace
     */
    String getName();

    /**
     * @return The facets for this dataset
     */
    DatasetFacets getFacets();
  }

  @JsonPropertyOrder
  public static final class OutputDatasetOutputFacets {
    @JsonAnySetter
    private final Map<String, OutputDatasetFacet> additionalProperties;

    @JsonCreator
    private OutputDatasetOutputFacets() {
      this.additionalProperties = new LinkedHashMap<>();
    }

    /**
     * @return additional properties
     */
    @JsonAnyGetter
    public Map<String, OutputDatasetFacet> getAdditionalProperties() {
      return additionalProperties;
    }
  }

  @JsonPropertyOrder({
      "_producer",
      "_schemaURL"
  })
  public static final class RunFacet implements BaseFacet {
    private final URI _producer;

    private final URI _schemaURL;

    @JsonAnySetter
    private final Map<String, Object> additionalProperties;

    /**
     * @param _producer URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     * @param _schemaURL The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this facet
     */
    @JsonCreator
    private RunFacet(@JsonProperty("_producer") URI _producer,
        @JsonProperty("_schemaURL") URI _schemaURL) {
      this._producer = _producer;
      this._schemaURL = _schemaURL;
      this.additionalProperties = new LinkedHashMap<>();
    }

    /**
     * @return URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     */
    public URI get_producer() {
      return _producer;
    }

    /**
     * @return The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this facet
     */
    public URI get_schemaURL() {
      return _schemaURL;
    }

    /**
     * @return additional properties
     */
    @JsonAnyGetter
    public Map<String, Object> getAdditionalProperties() {
      return additionalProperties;
    }
  }

  @JsonPropertyOrder({
      "namespace",
      "name",
      "facets",
      "outputFacets"
  })
  public static final class OutputDataset implements Dataset {
    private final String namespace;

    private final String name;

    private final DatasetFacets facets;

    private final OutputDatasetOutputFacets outputFacets;

    /**
     * @param namespace The namespace containing that dataset
     * @param name The unique name for that dataset within that namespace
     * @param facets The facets for this dataset
     * @param outputFacets The output facets for this dataset
     */
    @JsonCreator
    private OutputDataset(@JsonProperty("namespace") String namespace,
        @JsonProperty("name") String name, @JsonProperty("facets") DatasetFacets facets,
        @JsonProperty("outputFacets") OutputDatasetOutputFacets outputFacets) {
      this.namespace = namespace;
      this.name = name;
      this.facets = facets;
      this.outputFacets = outputFacets;
    }

    /**
     * @return The namespace containing that dataset
     */
    public String getNamespace() {
      return namespace;
    }

    /**
     * @return The unique name for that dataset within that namespace
     */
    public String getName() {
      return name;
    }

    /**
     * @return The facets for this dataset
     */
    public DatasetFacets getFacets() {
      return facets;
    }

    /**
     * @return The output facets for this dataset
     */
    public OutputDatasetOutputFacets getOutputFacets() {
      return outputFacets;
    }
  }

  public interface BaseFacet {
    /**
     * @return URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     */
    URI get_producer();

    /**
     * @return The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this facet
     */
    URI get_schemaURL();

    /**
     * @return additional properties
     */
    Map<String, Object> getAdditionalProperties();
  }

  @JsonPropertyOrder({
      "namespace",
      "name",
      "facets",
      "inputFacets"
  })
  public static final class InputDataset implements Dataset {
    private final String namespace;

    private final String name;

    private final DatasetFacets facets;

    private final InputDatasetInputFacets inputFacets;

    /**
     * @param namespace The namespace containing that dataset
     * @param name The unique name for that dataset within that namespace
     * @param facets The facets for this dataset
     * @param inputFacets The input facets for this dataset.
     */
    @JsonCreator
    private InputDataset(@JsonProperty("namespace") String namespace,
        @JsonProperty("name") String name, @JsonProperty("facets") DatasetFacets facets,
        @JsonProperty("inputFacets") InputDatasetInputFacets inputFacets) {
      this.namespace = namespace;
      this.name = name;
      this.facets = facets;
      this.inputFacets = inputFacets;
    }

    /**
     * @return The namespace containing that dataset
     */
    public String getNamespace() {
      return namespace;
    }

    /**
     * @return The unique name for that dataset within that namespace
     */
    public String getName() {
      return name;
    }

    /**
     * @return The facets for this dataset
     */
    public DatasetFacets getFacets() {
      return facets;
    }

    /**
     * @return The input facets for this dataset.
     */
    public InputDatasetInputFacets getInputFacets() {
      return inputFacets;
    }
  }

  @JsonPropertyOrder({
      "namespace",
      "name",
      "facets"
  })
  public static final class Job {
    private final String namespace;

    private final String name;

    private final JobFacets facets;

    /**
     * @param namespace The namespace containing that job
     * @param name The unique name for that job within that namespace
     * @param facets The job facets.
     */
    @JsonCreator
    private Job(@JsonProperty("namespace") String namespace, @JsonProperty("name") String name,
        @JsonProperty("facets") JobFacets facets) {
      this.namespace = namespace;
      this.name = name;
      this.facets = facets;
    }

    /**
     * @return The namespace containing that job
     */
    public String getNamespace() {
      return namespace;
    }

    /**
     * @return The unique name for that job within that namespace
     */
    public String getName() {
      return name;
    }

    /**
     * @return The job facets.
     */
    public JobFacets getFacets() {
      return facets;
    }
  }

  @JsonPropertyOrder({
      "_producer",
      "_schemaURL"
  })
  public static final class InputDatasetFacet implements BaseFacet {
    private final URI _producer;

    private final URI _schemaURL;

    @JsonAnySetter
    private final Map<String, Object> additionalProperties;

    /**
     * @param _producer URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     * @param _schemaURL The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this facet
     */
    @JsonCreator
    private InputDatasetFacet(@JsonProperty("_producer") URI _producer,
        @JsonProperty("_schemaURL") URI _schemaURL) {
      this._producer = _producer;
      this._schemaURL = _schemaURL;
      this.additionalProperties = new LinkedHashMap<>();
    }

    /**
     * @return URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     */
    public URI get_producer() {
      return _producer;
    }

    /**
     * @return The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this facet
     */
    public URI get_schemaURL() {
      return _schemaURL;
    }

    /**
     * @return additional properties
     */
    @JsonAnyGetter
    public Map<String, Object> getAdditionalProperties() {
      return additionalProperties;
    }
  }

  @JsonPropertyOrder({
      "_producer",
      "_schemaURL"
  })
  public static final class JobFacet implements BaseFacet {
    private final URI _producer;

    private final URI _schemaURL;

    @JsonAnySetter
    private final Map<String, Object> additionalProperties;

    /**
     * @param _producer URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     * @param _schemaURL The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this facet
     */
    @JsonCreator
    private JobFacet(@JsonProperty("_producer") URI _producer,
        @JsonProperty("_schemaURL") URI _schemaURL) {
      this._producer = _producer;
      this._schemaURL = _schemaURL;
      this.additionalProperties = new LinkedHashMap<>();
    }

    /**
     * @return URI identifying the producer of this metadata. For example this could be a git url with a given tag or sha
     */
    public URI get_producer() {
      return _producer;
    }

    /**
     * @return The JSON Pointer (https://tools.ietf.org/html/rfc6901) URL to the corresponding version of the schema definition for this facet
     */
    public URI get_schemaURL() {
      return _schemaURL;
    }

    /**
     * @return additional properties
     */
    @JsonAnyGetter
    public Map<String, Object> getAdditionalProperties() {
      return additionalProperties;
    }
  }
}

This may be a big ask, but given that the server model classes are all static with public constructors, the enclosing OpenLineage class is really just a namespace and will never be instantiated. Is it very difficult to unnest the enclosed classes and make them all top level? It's not the end of the world if it is, but I thought I'd ask.

Is it very difficult to unnest the enclosed classes and make them all top level?

@collado-mike: though I do agree, I'd rather be consistent with the way the client models are generated and use the enclosed classes for the server as well:
io.openlineage.server.OpenLineage.*
io.openlineage.client.OpenLineage.*

In a way, the OpenLineage is effectively the models path that you'd normally find in clients, for example marquez.client.models

I would not change the nesting on the client side now since it breaks compatibility.
I can look into splitting that on the server side but it will make the generation a bit more complex to handle both cases.
I think it is a bit a matter of taste as they are strictly equivalent functionally.

@collado-mike: though I do agree, I'd rather be consistent with the way the client models are generated and use the enclosed classes for the server as well:

I think the client models are the way they are for a reason- trying to make it easy for users to pass in the _producer field by hiding all the constructors and using factory methods that all have access to the common _producer. The server model has no such need, as we're just deserializing received models.
On the other hand, it is very inconsistent with how Java models are typically written, e.g., in Marquez and other projects. It really is just an aesthetic concern- they all end up in their own .class files in the end- but I'm just hoping to make it a bit easier for readers and users to browse the code in a format that is more familiar, thus easier to consume and understand.

I would not change the nesting on the client side now since it breaks compatibility.
I can look into splitting that on the server side but it will make the generation a bit more complex to handle both cases.
I think it is a bit a matter of taste as they are strictly equivalent functionally.

I agree on all points. Again, I don't want to make a ton of work or to make the generator way more complex than necessary. I was just hoping to make the code a bit more typical of a Java codebase.

I'm just hoping to make it a bit easier for readers and users to browse the code in a format that is more familiar, thus easier to consume and understand

Yeah, I agree 👍 Maybe server and client pkg naming don't have to be aligned, but I guess I tend to favor consistency but in this case it comes at a cost of usability.

@julienledem: Are the serve models publish? I don't see the server package on o.openlineage.server as io.openlineage.client. Let me know if I'm looking in the wrong place.


CB-3080 Set CapacityScheduler as default scheduler for YARN in the Data Engineering blueprint

6021 is latest. I think this need to be cancelled.
cc @ashutoshc @miklosgergely


Deprecating resources using the generic endpoint doesn't work

This is a backwards compatibility bug. When using the endpoint:
DELETE v1/resources/{org}/{proj}/_/{id}

It doesn't work.

Fusion has done a work around: https://github.com/BlueBrain/nexus/issues/2570


forum having trouble. 500 error

I'm not sure if this is a bug
If you're not sure if it's a real bug or if it's just you, please open a topic on the forum: https://forum.magicmirror.builders/category/15/bug-hunt
I'm having troubles installing or configuring MagicMirror
Problems installing or configuring your MagicMirror? Check out: https://forum.magicmirror.builders/category/10/troubleshooting
I found a bug in the MagicMirror installer
If you are facing an issue or found a bug while trying to install MagicMirror via the installer please report it in the respective GitHub repository:
https://github.com/sdetweil/MagicMirror_scripts
I found a bug in the MagicMirror Docker image
If you are facing an issue or found a bug while running MagicMirror inside a Docker container please create an issue in the GitHub repository of the MagicMirror Docker image:
https://github.com/bastilimbach/docker-MagicMirror

I found a bug in MagicMirror
Please make sure to only submit reproducible issues. You can safely remove everything above the dividing line.
When submitting a new issue, please supply the following information:
Platform: Place your platform here... give us your web browser/Electron version and your hardware (Raspberry Pi 2/3, Windows, Mac, Linux, System V UNIX).
Node Version: Make sure it's version 8 or later.
MagicMirror Version: Please let us now which version of MagicMirror you are running. It can be found in the package.log file.
Description: Provide a detailed description about the issue and include specific details to help us understand the problem. Adding screenshots will help describing the problem.
Steps to Reproduce: List the step by step process to reproduce the issue.
Expected Results: Describe what you expected to see.
Actual Results: Describe what you actually saw.
Configuration: What does the used config.js file look like? Don't forget to remove any sensitive information!
Additional Notes: Provide any other relevant notes not previously mentioned. This is optional.

I am able to reach the forum but not the main page.
However, the forum is unusable for the most part.
Console spits out this error:
Firefox can’t establish a connection to the server at wss://forum.magicmirror.builders/socket.io/?EIO=3&transport=websocket&sid=

I am able to reach the forum but not the main page.
However, the forum is unusable for the most part.
Console spits out this error:
Firefox can’t establish a connection to the server at wss://forum.magicmirror.builders/socket.io/?EIO=3&transport=websocket&sid=

Thanks for the report. Could you check if it's any better now (after a refresh)?

Thanks for the report. Could you check if it's any better now (after a refresh)?

Still not working, and now I can't even reach it. Also getting a error 500.
Also, nginx is leaking the version. I think this should be patched as it can be useful for hackers. The patch is very easy.

Still not working, and now I can't even reach it. Also getting a error 500.
Also, nginx is leaking the version. I think this should be patched as it can be useful for hackers. The patch is very easy.

What is the full url you are trying to load?

What is the full url you are trying to load?

Will do some maintenance. But this might mean the forum is down for the coming hour. Hope this will solve the issue afterwards. "ll let you know when it is done.

Will do some maintenance. But this might mean the forum is down for the coming hour. Hope this will solve the issue afterwards. "ll let you know when it is done.

Sure, no pressure, I was just trying to help :)

Sure, no pressure, I was just trying to help :)

I've updated Node & NodeBB. Let me know if it solves the issue.

I've updated Node & NodeBB. Let me know if it solves the issue.

Forum is up and running again 👍

Forum is up and running again 👍

different color themes not available. some chats appear to be hung.

different color themes not available. some chats appear to be hung.

Themes should now be available again, @sdetweil! Can you give some more info on the chats issue?

dont know for sure. think it might have been themes. couldnt see buttons. looks like its cleared now

Good to hear! Can I close this issue for now?

no, sorry, we cant upload pics now, get 'invalid files'

new user gets error regiatring on forum. see discord support channel. also sound from forum not working. contact mykle1

The registration issue is solved. Still working on the image issue.

Images are working as well. Any other issues?

github registration on forum not sending verify email. see discord support

I experienced a lack of verify email when registering with github account. Comments were made in Discord General Channel. I successfully registerd an account by email registration using my same gmail account without the period in it. Not sure if that's relevant.


Missing output requirement in documentation

There is no mention of a required step output in the current documentation. For example, the colored output in:
- name: Generate string with ANSI color codes
id: generate-colored-output
run: |
  colored=$(printf '\e[0;31mRED\e[0m')
  echo "::set-output name=colored::$colored"

An example such as this should be added to avoid ambiguity.

Fixed in b2f791a3a62a9b926cc68dc756f818bb1565c0fb.


xz (Lzma)

@dzbarsky
Do you think the xz, xzdec and lzmadec targets are needed too? I had them disabled as only lzma was building, but I think lzma is the only target that gets linked into any builds and xz is just for building a standalone binary? Let me know your thoughts and I'll clean up this pr to finalise.
resolves #1275

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (xz) have been updated in this PR. Please review the changes.

I bet just lzma is fine. Folks can always file requests or contribute patches if they need the binaries.

Please also address
BcrValidationResult.FAILED: Missing bazel version for task 'verify_targets' in the presubmit.yml file.
BcrValidationResult.FAILED: Missing bazel version for task 'run_test_module' in the presubmit.yml file.

Context: https://github.com/bazelbuild/bazel-central-registry/pull/1387

@meteorcloudy @Attempt3035 I addressed the issues in #1499

@Vertexwahn I've put a PR to fix these issues in your branch, please accept so it comes through to this PR :)

Hello @bazelbuild/bcr-maintainers, modules without existing maintainers (xz) have been updated in this PR. Please review the changes.

@Vertexwahn I pulled across all our commits from your branch into this original PR & branch, removed the lock file and everything should now be working (awaiting build run)👌
Let me know if there's anything further to do before this PR can be merged! Thanks for all the help guys!
Closes #1538

@meteorcloudy Release the kraken! ;)

Hmmm I can't spot why the files aren't able to be resolved by some of the test cases in only some machine configs... Going to try a different workaround, but any ideas? Everything seems to be the same for all tests and all files, I don't see why there's a discrepancy🤷♀

Great to see this level of collaboration! Just ping one of us for the formal review and merge when you are done doing the actual work.

Looks like it's all passing except windows tests. I believe it's because of windows pathing, @Vertexwahn if you wanted to apply the latest patch and you can see where I modified the paths in the test files, not sure if there's something special we need to do in the test files for windows or if the issue is in the data = glob having "/" in the glob pattern?

@Attempt3035 If I run bazel test //:all_tests on Windows 4 Test are failing. If I run bazel test --enable_runfiles //:all_tests only one test fails. I use Bazel 7.0.2 and Visual Studio 2022. There was in the past this issue here. With --enable_runfiles only //:test_lzip_decoder fails. Need to investigate further why. A fast solution would be that we exclude Windows from testing (and only keep building lzma)

@Attempt3035 It's just a flag we can add...
For flip it is done this way:
matrix:
  bazel: [6.x, 7.x]
  unix_platform: ["macos", "ubuntu2004"]

tasks:
  unix_test:
    platform: ${{ unix_platform }}
    bazel: ${{ bazel }}
    build_flags:
    - --cxxopt=-std=c++17
    build_targets:
    - '@flip//:flip'
    - '@flip//:flip-cli'
  windows_test:
    platform: "windows"
    bazel: ${{ bazel }}
    build_flags:
    - --cxxopt=/std:c++20
    build_targets:
    - '@flip//:flip'
    - '@flip//:flip-cli'

@Attempt3035
On Windows the define  "HAVE_LZIP_DECODER" is not set - therefore we jump on Windows in "early skip" and have one failing test....
#ifndef HAVE_LZIP_DECODER
	tuktest_early_skip("lzip decoder disabled");
#else

@Attempt3035
you have to add #define HAVE_LZIP_DECODER 1 to config.lzma-windows.h and build with --enable_runfiles then all tests on Windows are green.
Please make sure also to update the #define VERSION "5.2.3" to  #define VERSION "5.4.5"

Sweet! Will add now!

It appears I have no idea what I'm doing when it comes to the presubmit.yml, @Vertexwahn help please 🤣 I couldn't find any docs on how to structure this properly either, is there somewhere I should be looking?

Info to the CI can be found here and here.

@Attempt3035
Try this:
matrix:
  platform:
    - centos7
    - debian10
    - debian11
    - macos
    - macos_arm64
    - ubuntu2004
    - ubuntu2204
    - windows
  bazel: [6.x, 7.x]
tasks:
  verify_targets:
    name: Verify build targets
    platform: ${{ platform }}
    bazel: ${{ bazel }}
    build_targets:
      - '@xz//:lzma'
  run_tests:
    name: Run tests
    platform: ${{ platform }}
    bazel: ${{ bazel }}
    test_flags:
    - "--enable_runfiles"
    test_targets:
    - all_tests

we do net need to differentiate between Unix and Windows builds, since Unix builds come by default with --enable_runfiles. So it does not hurt if this is explicitly defined.

Info to the CI can be found here and here.

Legend thank you so much!

@Vertexwahn Had to make some changes to the presubmit you suggested, for some reason it wasn't finding the test module properly but working now, it's only centos that fails both build and tests, maybe the lib isn't compatible. Should we just remove centos?

@Attempt3035 Yes remove CentOS

All passing woho!🎉 Cheers to some good development @Vertexwahn🍻 @fmeum would you be able to review when you get a chance?

@Attempt3035 @Vertexwahn Hi folks, I tried to use this module in https://github.com/dzbarsky/libarchive but it looks like we may have an issue with the config.h - we should not be defining HAVE_IMMINTRIN_H on arm platforms. This manifests in errors like the following when targeting a platform like @zig_sdk//libc_aware/platform:linux_arm64_musl:
In file included from external/xz~5.4.5/src/liblzma/lzma/lzma_encoder_optimum_normal.c:14:
In file included from bazel-out/linux_arm64_musl-fastbuild/bin/external/xz~5.4.5/_virtual_includes/lzma_src_liblzma_common/memcmplen.h:19:
In file included from external/hermetic_cc_toolchain~3.0.1~toolchains~zig_sdk/lib/include/immintrin.h:21:
external/hermetic_cc_toolchain~3.0.1~toolchains~zig_sdk/lib/include/mmintrin.h:14:2: error: "This header is only meant to be used on x86 and x64 architecture"
   14 | #error "This header is only meant to be used on x86 and x64 architecture"

@Vertexwahn we may have to look at the possibility of dynamically generating the config.h as otherwise we might have a large number of platform / cpu variants. This was adapted from the usage in the rules_boost that uses the workspace system, it built fine on my arm Mac for boost libs but maybe arm Mac is okay or boost doesn't use a particular feature? @dzbarsky do you know what's required to generate the config.h, do we need automake or other tools to be available on the system?

How about generating it with expand_template and filling in values based on select? Compared to automake, this will make the build work in cross-compilation scenarios.

Check out how I did config.h and the xplat config in the repo I linked. Basically you can use select and defines to compile a config.h cc_library and bazel propagates the defines. @fmeum's suggestion would also work

I got this working here https://github.com/thesayyn/bazel-central-registry/tree/main/modules/xz/5.4.5

@dzbarsky, I've added @thesayyn's work to a PR for the BCR, please see #1576


Website Needs a more lively background

Although the background is soothing ,but it can be made much attractive if we add a fantastic background image with some transitions on hovering over.

Hey, please assign me this task

Sir, please add it to hactoberfest too

Start working on it.

please assign this to me so that i contribute to this hactoberfest 2023 . i have excellent knowledge of web dev and you can also check my projects in my repositories.


[FB Messenger] (1) Adaptive Card not working & (2) Unable to send table formatted message?

                      //  var tableHTML = '

Station Name	Distance

' + resultsMetroName[0] + '	' + data[0].distance + '

' + resultsMetroName[0] + '	' + data[0].distance + '

';
                        //var message = {
                          //  type: 'message',
                            //textFormat: 'xml',
                            //text: tableHTML
                        // };

session.send(msg);
In messenger i am getting same result in string
table style="padding:10px;border:1px solid black;">Station NameDistance' + resultsMetroName[0] + '' + data[0].distance + '' + resultsMetroName[0] + '' + data[0].distance + ''
How i can send the html
In Adaptive I am getting only the title but the buttonthat i have added in adaptive card is not showi8ng up

@hardikchoudhary Are you using .NET or Node.js SDK?

I am using node js
On 24-Aug-2017 12:00 AM, "Nils"<EMAIL_ADDRESS>wrote:

@hardikchoudhary https://github.com/hardikchoudhary Are you using .NET
or Node.js SDK?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotBuilder/issues/3371#issuecomment-324422701,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANs5qka7gfEtkNX79SUV_IZOH_uzmZp_ks5sbG_JgaJpZM4O_yRb
.

I'm also looking for the same functionality for skype client using nodejs SDK.
I laready posted the question on Stackoverflow

Please help me in this regard

Please let us know is it possible to send table structure ??? @nwhitmont

@nw please let me know if we have the solution in this...
On 28-Aug-2017 2:53 PM, "ryaan-web"<EMAIL_ADDRESS>wrote:

Please help me in this regard
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Microsoft/BotBuilder/issues/3371#issuecomment-325305143,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANs5qtdDbURFJ56Fku4zMEmRlMXZJ1clks5scocMgaJpZM4O_yRb
.

I was unable to find documentation that says facebook messenger allows for HTML in messages.  I did read from a blog that the HTML will display exactly as the string you put it in as.  This is consistent with the behavior you are seeing so all signs point to HTML not being allowed in facebook messages.


Use exception constructor that takes httpCode in asHttpCode method

Thanks for the contribution @gwongz
How about adding a constructor to HelloSignException for this while we're at it? I'd rather avoid passing null values.
public HelloSignException(String message, Integer httpCode) {         this(message, httpCode, null, null); }
Then it can just be throw new HelloSignException("HTTP Code " + code, code); in HttpClient

@jspaetzel looks good to me!

Thanks for the contribution, im going to followup on this in https://github.com/HelloFax/hellosign-java-sdk/pull/82


Email default settings are restored each time the container is restarted

We have 2 problems with emails sending:

the default settings does not work (emails cannot be sent), but maybe it's a specific problem to our network.
when the emails settings are customized, in "Realm settings" -> "Email", each time the container is restarted, the default settings are restored.

This is an expected behavior because one can change the app settings to give it a different email. You can change the email address  from the Cloudron dashboard.

Well, even changing the email gives the "Failed to send email" error.
For example, with default settings, I have:

Host: mail
Port: 2525
Enable StartTLS: off

If I change the following fields with:

Host: my.cloudron-domain.tdl
Port: 587
Enable StartTLS: on

Email sending works.
What's strange is that the same default configuration (Host: mail, Port: 2525) works on others apps (e.g. Nextcloud).
But beside this problem, I think we should be able to change the email settings if we want to use an email other than Cloudron, e.g. transactional emails.
Thanks!

Hi @njsubedi,
We are still facing this problem.
Would there be a solution to keep the emails settings after the container is restarted?
Thanks!

@njsubedi do you have any update on this?

Would there be a solution to keep the emails settings after the container is restarted?
Please set the email configuration from the Cloudron dashboard instead of changing them inside the Keycloak realm setting. Every time the container is restarted, it replaces the values in the existing email settings with the values provided by Cloudron environment.

Hi @njsubedi we finally managed to make Keycloak send email with the default settings (Host: mail | Port: 2525).
The problem was that there is a space char at the end of the username, as you can see here (in gray):

If we remove the space, email sending works. But each time the container restarts, this space is back and emails are not sent.
Could you do something about it?
Thanks very much!

Do you think it would be possible to create a version with the bug fixed while waiting to manage the KEEP_SMTP_SETTINGS variable? Thanks !

I’ve already fixed the bug and updated Keycloak version. Since you’re already using the source code and the app isn’t available at the app store, you can simply comment the code and run cloudron build and cloudron install. I’m still trying to figure out a way to do it the cloudron way.


Add educators workshop heading and contents

Most notebooks are for Cirq v0.5 and need updating/polishing. Putting in now as placeholder for devsite.

LGTM - I did merge the other ion device PR though - can you remove that from either this one or in a new PR?

Removed!

Failed tests due (mostly) to not including these in rtd_docs - do we want to do this @balopat?
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/chemistry.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/intro.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/ion_device.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/neutral_atom.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/qaoa_ising.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/textbook_algorithms.ipynb: WARNING: document isn't included in any toctree

Failed tests due (mostly) to not including these in rtd_docs - do we want to include these in rtd_docs @balopat?
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/chemistry.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/intro.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/ion_device.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/neutral_atom.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/qaoa_ising.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/textbook_algorithms.ipynb: WARNING: document isn't included in any toctree

Let's add them under the same heading "Educator workshop" in rtd_docs/index.rst

Automerge cancelled: A status check is failing.

Failed tests due (mostly) to not including these in rtd_docs - do we want to include these in rtd_docs @balopat?
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/chemistry.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/intro.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/ion_device.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/neutral_atom.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/qaoa_ising.ipynb: WARNING: document isn't included in any toctree
/home/runner/work/Cirq/Cirq/rtd_docs/docs/tutorials/educators/textbook_algorithms.ipynb: WARNING: document isn't included in any toctree

Let's add them under the same heading "Educator workshop" in rtd_docs/index.rst

I decided to just exclude them for now - there were too many obscure sphinx issues that I couldn't solve just now.

Automerge cancelled: A status check is failing.

had-to-fight-with-the-linter: conf.py seems a little bit over the top to put through formatting.


Replace the soft limit fields to hard limit fields in the kopia client struct(PR#3)

Change Overview
This PR sets hard limit fields for cache while connecting to kopia API server and ignores the soft limit fields.
Pull request type
Please check the type of change your PR introduces:

[ ] :construction: Work in Progress
[ ] :rainbow: Refactoring (no functional changes, no api changes)
[ ] :hamster: Trivial/Minor
[ ] :bug: Bugfix
[ ] :sunflower: Feature
[ ] :world_map: Documentation
[ ] :robot: Test

Issues

fixes #issue-number

Test Plan

[ ] :muscle: Manual
[ ] :zap: Unit test
[ ] :green_heart: E2E

Closing this, since these changes were added to https://github.com/kanisterio/kanister/pull/2393


Game broken

When attempting to access this at https://githubschool.github.io/github-games-gsuzor91/, I am getting a 404. This could be caused by a couple things:

GitHub pages needs to be enabled on main. You can fix this in the repository settings.
the index.html file is incorrectly named inde.html. We will fix this together in class.

Can you please fix the first bullet @gsuzor91?

The first bullet was fixed by going to Settings > GitHub Pages and setting Branch: main /(root)

The first bullet was fixed by going to Settings > GitHub Pages and setting Branch: main /(root)

Reverted f99c to fix this issue.

Reverted f99c to fix this issue.


Printed string literal expressions are not escaped correctly

Printed string literal expressions are not escaped correctly (with backslashes) when generated programmatically. I stumbled upon this while beginning to port BuildableNodes.swift.gyb to SwiftSyntaxBuilderGeneration, since the template generates such literals.
Consider the following example:
import SwiftSyntaxBuilder

let source = SourceFile {
  StringLiteralExpr("\\")
}

let syntax = source.buildSyntax(format: Format())
print(syntax.description)

Checklist

[x] If possible, I've reproduced the issue using the main branch of this package.
[x] This issue hasn't been addressed in an existing GitHub issue.

Expected behavior
The example should print "\\".
Actual behavior
The example prints "\", leaving the string literal unterminated.
Steps to Reproduce
Run the program above.

rdar://98129594

Closing as being the intended behavior as per our discussion.


Erroneous documentation - paging / paged?

Hey there,
I noticed at http://ldapjs.org/client.html Paging the second example with a "paging" object being used to specify the pageSize and if a callback should be use to resume the paging (pagePause).
Looking at the code at
https://github.com/mcavage/node-ldapjs/blob/master/lib/client/client.js#L816
I see the object is called "paged" and not "paging".
Is this an error in the documentation?
Best regards
japel

Thank you @japel!
I spent a lot of time trying to defeat a SizeLimitExceededError: Size Limit Exceeded error. Paging simply wasn't working as per the documentation I found at: http://ldapjs.org/client.html#paging  At time of writing the documentation there says to use one of:   paging: true or paging: { pageSize: 250, pagePause: true }. However, that information is false.
When I change those to either:  paged: true or paged: { pageSize: 250, pagePause: true } then pagination works and the SizeLimitExceededError: Size Limit Exceeded error go away.

Yeah, I also posted a PR to change the documentation, but there is no reaction from the maintainers...

And this also costed me like half a day... :(

Hi @pfmooney, why was this issue closed? This is still a problem: the implementation and documentation still conflict. People will lose time. All documentation should refer to 'paged' instead of 'paging' (which it currently refers to buy has no effect). Cheers, Jonathan

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


charging-curves.json is pulled/restored but not placed or updated in the directory

Hey,
with the newest release v1.23.3 and Teammate 1.28.2 the charging-curves.json was not autoupdated correctly. So I deleted it from the dashboards folder and ran the dashboards.sh again manually.
With the script saying it was pulled and restored. (12 dashboards restored)

However it is nowhere to be found. (only 11 dashboards)

I had to manually import it.
Any idea?

Thanks for the notice, I'll check it out as soon as possible.

Hi again
I just check de autoinstaller and it works correctly.
I made some changes to the "Charging Curves" dashboard, then I saved it, tried the autoinstaller and it updated me to the latest version published on GitHub.

Thanks for checking so quickly. :)
That's weird. Then there must be something with my installation. All other dashboards update correctly or get restored when deleted manually.

If it is strange, I have tried updating it, deleting it and installing it from 0 and it always works for me.
It can be queried through the Grafana API, but it doesn't tell you if there is a problem.


MaterialXView: version 1.38.2: compile error on macOS: context.getShaderGenerator().getTarget()

Greetings, I'm the creator and maintainer of the MaterialX package for the MacPorts package management system. I've been trying to package version 1.38.2, and I keep getting a compile error when the build gets to MaterialXView. This error appears to be new, and wasn't present in MaterialX 1.38.1.
Here's the error from the build log:
:info:build [ 82%] Building CXX object source/MaterialXView/CMakeFiles/MaterialXView.dir/Material.cpp.o
:info:build cd /opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/build/source/MaterialXView && /usr/bin/clang++
            -DMATERIALX_BUILD_GEN_GLSL -DMATERIALX_BUILD_GEN_MDL -DMATERIALX_BUILD_GEN_OSL -DMATERIALX_BUILD_OIIO
            -DMATERIALX_INSTALL_MDL_MODULE_PATH=\"\" -DMATERIALX_MDLC_EXECUTABLE=\"\" -DMATERIALX_MDL_MODULE_PATHS=\"\"
            -DMATERIALX_MDL_RENDER_ARGUMENTS=\"\" -DMATERIALX_MDL_RENDER_EXECUTABLE=\"\"
            -DMATERIALX_OSL_INCLUDE_PATH=\"/opt/local/share/OSL/shaders\" -DMATERIALX_TESTOSLC_EXECUTABLE=\"/opt/local/bin/oslc\"
            -DMATERIALX_TESTRENDER_EXECUTABLE=\"/opt/local/bin/testrender\" -DMATERIALX_TEST_RENDER
            -I/opt/local/include -I/opt/local/include/eigen3 -I/opt/local/include/nanovg
            -I/opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/MaterialX-1.38.2/source/MaterialXFormat/..
            -I/opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/MaterialX-1.38.2/source/MaterialXCore/..
            -I/opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/MaterialX-1.38.2/source/MaterialXGenGlsl/..
            -I/opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/MaterialX-1.38.2/source/MaterialXGenShader/..
            -I/opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/MaterialX-1.38.2/source/MaterialXRenderGlsl/..
            -I/opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/MaterialX-1.38.2/source/MaterialXRenderHw/..
            -I/opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/MaterialX-1.38.2/source/MaterialXGenOsl/..
            -I/opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/MaterialX-1.38.2/source/MaterialXGenMdl/..
            -pipe -isystem /Users/jasonliu/ports/graphics/materialx/files/old_appkit_compat -Os -DNDEBUG
            -I/opt/local/include -stdlib=libc++ -arch x86_64 -mmacosx-version-min=10.11 -fPIE -Wall -Wno-missing-braces
            -std=gnu++11 -MD -MT source/MaterialXView/CMakeFiles/MaterialXView.dir/Material.cpp.o
            -MF CMakeFiles/MaterialXView.dir/Material.cpp.o.d
            -o CMakeFiles/MaterialXView.dir/Material.cpp.o
            -c /opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/MaterialX-1.38.2/source/MaterialXView/Material.cpp
:info:build /opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/MaterialX-1.38.2/source/MaterialXView/Material.cpp:79:56:
            error: no viable conversion
            from 'const string' (aka 'const basic_string<char, char_traits<char>, allocator<char> >')
            to 'const MaterialX::ShaderGenerator'
:info:build     _hasTransparency = mx::isTransparentSurface(_elem, context.getShaderGenerator().getTarget());
:info:build                                                        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
:info:build /opt/local/include/MaterialXGenShader/ShaderGenerator.h:29:24:
            note: candidate constructor (the implicit copy constructor) not viable: no known conversion
            from 'const string' (aka 'const basic_string<char, char_traits<char>, allocator<char> >')
            to 'const MaterialX::ShaderGenerator &' for 1st argument
:info:build class MX_GENSHADER_API ShaderGenerator
:info:build                        ^
:info:build /opt/local/include/MaterialXGenShader/ShaderGenerator.h:184:5:
            note: candidate constructor not viable: no known conversion
            from 'const string' (aka 'const basic_string<char, char_traits<char>, allocator<char> >')
            to 'SyntaxPtr' (aka 'shared_ptr<MaterialX::Syntax>') for 1st argument
:info:build     ShaderGenerator(SyntaxPtr syntax);
:info:build     ^
:info:build /opt/local/include/MaterialXGenShader/Util.h:35:87: note: passing argument to parameter 'shadergen' here
:info:build MX_GENSHADER_API bool isTransparentSurface(ElementPtr element, const ShaderGenerator& shadergen);
:info:build                                                                                ^
:info:build 1 error generated.
:info:build make[2]: *** [source/MaterialXView/CMakeFiles/MaterialXView.dir/Material.cpp.o] Error 1

@jasonliu-- That's an interesting one, and it looks like you may have a stale header file in /opt/local/include/MaterialXGenShader/Util.h.
The debug output above mentions that the interface of isTransparentSurface is bool isTransparentSurface(ElementPtr element, const ShaderGenerator& shadergen), but the latest codebase has a different interface for that function:
https://github.com/materialx/MaterialX/blob/main/source/MaterialXGenShader/Util.h#L35

@jasonliu-- That's an interesting one, and it looks like you may have a stale header file in /opt/local/include/MaterialXGenShader/Util.h.

Theoretically, that shouldn't be possible. When we do our package development, all MacPorts packagers are instructed to completely delete everything related to any previous builds, and force MacPorts to do a completely clean build from scratch (using the port clean materialx command). Every time a software package is built from source by way of a completely clean build, the MacPorts build system actually fetches the zipped up source code tarball directly from the Releases section of the project's GitHub website. So unless the Util.h header file is stale in your released tarballs in your Releases section, the MacPorts build would be using whatever Util.h file is included in the 1.38.2 tarball.

The debug output above mentions that the interface of isTransparentSurface is bool isTransparentSurface(ElementPtr element, const ShaderGenerator& shadergen), but the latest codebase has a different interface for that function:
https://github.com/materialx/MaterialX/blob/main/source/MaterialXGenShader/Util.h#L35

As far as I can tell, that is indeed what is in the Util.h file that's included in the 1.38.2 release tarball. If we assume that my MacPorts builds are in fact using the 1.38.2 Util.h file, then what else could be causing the compile error?

@jasonliu-- That's an interesting one, and it looks like you may have a stale header file in /opt/local/include/MaterialXGenShader/Util.h.

It seems that the MacPorts build system is referencing the Util.h file that is coming from MaterialX 1.38.1. Theoretically, the MacPorts build environment is supposed to quarantine any new "build from source" builds from anything that is already existing from any currently-installed previous versions of a package, but there have been rare instances of certain software projects that somehow "break out" of the quarantined build environment, and still attempt to directly reference already-installed files located in /opt/local.
I will try completely uninstalling MaterialX 1.38.1 and see whether it helps to resolve the compile error. I will report back my results.

The debug output above mentions that the interface of isTransparentSurface is bool isTransparentSurface(ElementPtr element, const ShaderGenerator& shadergen), but the latest codebase has a different interface for that function:
https://github.com/materialx/MaterialX/blob/main/source/MaterialXGenShader/Util.h#L35

Yes, this appears to be what is in the Util.h header file that is included in the MaterialX 1.38.2 tarball. Theoretically, MacPorts is supposed to conduct the builds using on only the files from the source code tarball (hence why you see all of those -I/opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/MaterialX-1.38.2/source/blahblah lines in the build log), but echoing what I said above, ill-behaved source code does sometimes find a way to break out of the build environment. It's quite possible that it's subtly related to the wider discussion that I triggered regarding possible hard-coding of certain paths that is being discussed in #728.

Let us know what you find on your side, @jasonliu--, and we're interested in the proposed improvements to installation paths in #728 as well.

Reporting back. Completely removing MaterialX 1.38.1 does indeed resolve the error, and 1.38.2 now builds fine without any further issues.
What this tells me is that there does indeed seem to be something in MaterialX's build files that is able to break out of MacPorts' quarantined build environment. Probably some path(s) that is/are "hard-coded", although hard-coded is a misnomer, since I highly doubt you guys are actually writing anything like /opt/local. Instead, there are probably some CMake variables in one or more CMakeLists.txt file(s) which are somehow resolving to be /opt/local, instead of /opt/local/var/macports/build/_ports_graphics_materialx/materialx/work/MaterialX-1.38.2/source (i.e. the build folder). I have no idea where it might be happening, but it's probably something to keep an eye out for as you work on the codebase.
@jstone-lucasfilm , thanks for the help. Your reply message was exactly the extra pair of eyes that finally allowed me get the newest MaterialX packaged. :thumbsup:
Feel free to close this issue.
P.S.: Completely unrelated to the issue.... I'm not sure whether you noticed, but if you look at the MaterialX package page on our website, you will see that I have builds of MaterialX (including the Viewer) working all the way back to macOS 10.9 Mavericks, even though your code technically only compiles back to macOS 10.12 Sierra. MacPorts has modules in it that allow for some pretty surprising legacy support, and we packagers can be somewhat stubborn about trying to get the latest software to successfully compile on older systems. So if the MaterialX devs ever get questions about running MaterialX on older Macs, feel free to send those inquiries our way! :smiley:

Thanks @jasonliu--, and it's great to see the extended macOS support for MaterialX!  I'll close out this issue for now, and we can continue the discussion of installation improvements on the related tickets.


Only one divice discoverable after upgrade to 3.1.11

After updating the plugin to the latest version the devices turned into no response. I removed the plugin and removed the devices from the Home App and installed it again finished the setup both AC's showed up in the Accessories tab in home bridge as they are configured in MelCloud, but when I try to add them to Home App only one of them appears. No matter what I have tried the AC in the living room does not appear in the app so I can add it.
I have tried to remove the child bridge in home app and re add it to no avail. I have tried to keep the plugin running with homebridge still the same.
Tried to set a freshly configured plug in as a child bridge added to home app and still can only see one of the AC's but not the other.
Any suggestions? this is very frustrating as I have it running just fine and upgraded the plug in since I have fallen behind with a lot versions.

Go to plugin settings and login to melcloud

this is from when I  freshly installed the plugin last night.

this is from now when I saw your comment.
I also enabled debugging logs that I will leave running for a bit

homebridge.log.txt
For some reason when I get just the log from the plugin it comes emptry. so here it is the log from homebridge.
I even went as further as removing homebridge from the Home app and added it again, but still only the Bedroom AC shows up when I try to add it, but both of them are appearing in the accessories tab of home bridge

https://github.com/grzegorz914/homebridge-melcloud-control/wiki#troubleshooting

After I used Unpair Single Bridge in Settings and removed all the associations with the AC that wont show up the problem is resolved thanks for all the help


Add Dockerfile to "Files of special interest"

In the same spirit as Makefiles and Rakefiles, Dockerfiles are "special
interest" files. Added support to color these files in the same style.
I personally use the 256dark variant. I checked in the ansi-* variants, but it didn't look like there was a corresponding category for special interest files. As such, I didn't modify them. If they should be updated too, let me know.

thx


Explain how to make an async post before transaction and after success

I used PayPalButton as recommended in the documentation.
However, I have two tasks to perform.

Make an async Post call to our own server API  ("api/payements") to create an order in our DB and waits for the response. I use await keyword to wait for the promise to resolved.
Makes another aysnc post call to our own server API ("api/confirm") to update the transaction status and reciept ID from Paypal after PayPal payment is successful. I use await keyword in this call too.

However, I don't know where can I call these functions.
I tried to call first API in create Order before return action.order(), but I am not allowed to write await keyword in a callback function.
Moreover, I write second API call in create Order function, in "then" section and it makes the call regardless of  the Payment status on PayPal.
Please guide me.
  const registerOrder = async() =>{
      return axios?.post('/api/payments', {
            description: description,
            email: email,
            price: price,
            userId: user?.id,
      });
  }

  const createOrder = useCallback((data, actions) =>{

        const resOrder =await registerOrder()            #### I can not write await here :(

        return actions.order
            .create({
                purchase_units: [
                    {
                        amount: {
                            value: lecture.price,
                        },
                    },
                ],
            })
            .then( async(orderID) => {
                try {
                 ####### this part runs regardless of PayPal payment status
                  await axios?.post(`/api/confirm/${resOrder?.data.id}`, {receiptId: orderID})      #### I need the response of resOrder here
                } catch {
                  setPopupOpenedTrue();
                  return
                }
              return orderID;

            });
    });

PayPal button component:
import React, {useState} from "react";
import { PayPalScriptProvider, PayPalButtons } from "@paypal/react-paypal-js";

export default function PayPal() {

  return (
      <PayPalScriptProvider options={{ "client-id": "sdjfhsdjfksdhfskdjfhskdhfjskfrhsdfkhsdhfj" }}>
          <PayPalButtons createOrder={createOrder} style={{ color: "black", shape:"pill",label: "pay", layout: "horizontal" ,height:40}} />
      </PayPalScriptProvider>
  );
}

`

Hi, @shehzi-khan!
Try this:

import React, {useState} from "react";
import { PayPalScriptProvider, PayPalButtons } from "@paypal/react-paypal-js";

export default function PayPal() {

  const registerOrder = async() =>{
    return axios?.post('/api/payments', {
      description: description,
      email: email,
      price: price,
      userId: user?.id,
    });
  }

  // Will be triggered when starts transaction
  const createOrder = async (data, actions) => {

    const resOrder = await registerOrder();

    const request = {
      intent: 'capture',
      purchase_units: [
        {
          amount: {
            value: lecture.price,
          },
          // Put your invoice ID to the paypal request (it should be string), to access it later
          custom_id: resOrder['id'],
        },
      ]
    };
    return actions.order.create(request);
  }

  // Will be triggered when user approved order
  const onApproveOrder = async (data, actions) => {

    // This function captures the funds from the transaction.
    const captured = await actions.order.capture();

    // TODO: remove debug logging
    console.log(captured);

    // paypal order ID
    console.log(captured['id']);

    // your invoice ID
    console.log(captured['custom_id']);

    try {
      // this part runs regardless of PayPal payment status
      await axios?.post(`/api/confirm/${captured['id']}`, {receiptId: captured['custom_id']});  // I need the response of resOrder here
    } catch {
      setPopupOpenedTrue();
    }
  }

  return (
    <PayPalScriptProvider options={{ "client-id": "sdjfhsdjfksdhfskdjfhskdhfjskfrhsdfkhsdhfj" }}>
      <PayPalButtons
        createOrder={(data, actions) => createOrder(data, actions)}
        onApprove={(data, actions) => onApproveOrder(data, actions)}
        style={{ color: "black", shape:"pill",label: "pay", layout: "horizontal" ,height:40}}
      />
    </PayPalScriptProvider>
  );
}

I recieved following error on the line, custom_id:resOrder['id']
TypeScript error: Object is possibly 'undefined'.  TS2532

Also in the post request in onApproveOrder, the recieptId should be the PayPal transaction ID, and the id in the confirm API URL should be the "order ID" received in the response of registerOrder.

Appreciate your help by the way. :)

ok I changed resOrder['id'] to resOrder?.data.id and tried to console.log(resOrder?.data.id) displays the correct orderID.
Now I changed custom_id in purchase_units from resOrder['id'] to resOrder?.data.id
console.log(captured['id']); displays the correct transaction ID recieved from PayPal.

:( :(

However console.log(captured['custom_id']); prints "undefined" :(

Hi @shehzi-khan!
Regarding this I recieved following error on the line, custom_id:resOrder['id'] TypeScript error: Object is possibly 'undefined'. TS2532
Ofc there will be error, because I don't know your data structures. I just given to you direction where to go.
Regarding this:

However console.log(captured['custom_id']); prints "undefined" :(
Put console.log(captured); and explore captured structure in the console. Probably 'custom_id' is in some nested object.
...
ok.. I have done it for you :)
try console.log(captured['purchase_units'][0]['custom_id']) to access your orderID;

@johan123312321 thanks answering @shehzi-khan's questions and for providing a server-side example in https://github.com/paypal/react-paypal-js/issues/118#issuecomment-856705827 💯🥇👍
We also provide this example for server-side integrations:

https://developer.paypal.com/demo/checkout/#/pattern/server
https://github.com/paypal/paypal-checkout-demo/tree/master/src/app/server