fix: sourcetype = 'hubble_fdg_' + fdg_file

Apparently we do want to extend the sourcetype name from hubble_fdg to hubble_fdg_filename but let's choose to do that without the salt:// protocol and without the .fdg file extension; while we're at it, make sure to replace all non alphanumerics with an underscore.

@jettero Thanks for quick turn around on this:
There is one corner case that isn't covered - when fdg is invoked from a command line it adds an additional underscore to sourcetype:
For example, if my fdg file had a following path: /opt/tmpfdg_test/2fdg_cert_test.fdg
then sourcetype would become hubble_fdg__opt_tmpfdg_test_2fdg_cert_test
Invoking fdg from command line is not widely used so if it is overly cumbersome to fix I'd be ok to leave it as it is.

@fossam well, that's the question. I specifically trimmed salt://fdg/blah.fdg to blah because that's the most likely use case, and I figured if we invoked something from the command line, we wouldn't want to use the same sourcetype; because it really may not be the same source.
So the question isn't whether it's a lot of trouble, the question is what's the right result?
I could pop off that trailing filename, remove the extension and just roll with that, or we could come up with a long gruesome strategy.

The "right" result is when both options result in the same outcome - have paths that start with salt://fdg/ work as they are at this point, but when we have an absolute path then instead of the double underscore just have a single one.
Say the same file is referenced by salt://fdg/blah.fdg or /tmp/blah.fdg. They would respectively become hubble_fdg_blah and hubble_fdg_tmp_blah.

I don't understand why salt://fdg/some_file.fdg should work out to be the same as /home/jettero/.fdg/some_file.py -- but at least if I say the sourcetype extension is the filename minus decorations it'll be consistent.

This is clever.
Here's what happened: I had made an fdg profile file to test the certificate module, but couldn't think imaginatively enough and named it fdg_cert_test.fdg. In Splunk the sourcetype became hubble_fdg_cert_test. After a bit I figured out what had happened and I started to think back on conversations on Slack and now I am unsure what to say.
Should my ability to step right into the first surprising outcome be ignored or are other common cases where the outcome could as surprising - like .../certs/certs_tests.fdg or .../testing/testing_certs.fdg?

I don't think it matters very much. I think it's a strange quirk of Hubble that it alters the source type based on the query anyway. I think with most types of injest, for the most part, the sourcetype would be hubble_fdg (or hubble_nova or whatever) and there'd be some kind of subfield that'd differentiate the data.  So your search would be index=hubble_something sourcetype=hubble_fdg subtype_thing=differentiator
Normally the sourcetype-append-text is going to come from something in a signed data repo anyway and no matter what we do to this sourcetype guess generator, someone will find a way to make it screwy from the commandline.

Normally the sourcetype-append-text is going to come from something in a signed data repo anyway and no matter what we do to this sourcetype guess generator, someone will find a way to make it screwy from the commandline.

I agree about the command line being a bit corner case. Just to clarify my most recent test - those filenames were not invoked from a command line, they were from a top file and run from a schedule just like they'd be used in most often. But that still opens up a case where one wouldn't necessarily expecting folder name and filename having this issue..

I just can't tollerate hubble_fdg_fdg_test as a sourcetype that we normally generate from fdg.

For those unaware, can you explain the issue with this?

It's inconsistent with the other modules that do this silly renaming thing.
You don't see any hubble_nebula_var_cache_hubble_hubblestack_nebula_v2_fifteen_minute sourcetypes.
Nebula just grabs a name for a dict key in the file and rolls with it -- no matter where the file is located. The only reason we're having this discussion is because the fdg functions aren't named, so we're using the filename as a kindof placeholder for a janky sourcetype renaming (that we arguably shouldn't be doing anyway).
I dislike hubble_fdg_fdg_test because it's ugly and (most likely) every single fdg file is going to be in that directory in the repo so the extra fdg in the name isn't adding anything useful it's just embarrassing to look at. I'm also convinced if we really want to reveal the full fdg filepath for the event, we should certainly do so, but it should be more like this:
index=hubble_whatever sourcetype=hubble_fdg fdg_file=fdg/test.fdg
... that's really the only logical thing to do in splunk imo.
But nevermind all that. We already rename sourcetypes all over the place, so we may as well continue. But I see absolutely no reason we should reveal the full repo filepath in the sourcetype. We can add a field for that if we really need it. This is just a nickname we're appending to the sourcetype afterall.
If we really really needed this to be 100% accurate and reveal the full path of the fdg file; then surely we also have to go back to nebula and teach it to reveal the full filepath of the osquery files too? right? Cuz those nicknames don't have any path info in them at all!! \o/

There are two issues at play:

nebula and fdg (I don't think I can compare the two because as you pointed out they use different naming conventions.)
Splunk - out of the fields from fdg, only sourcetype is an index time extracted field. Using that to select different events is important for search performance.

As far as ugliness goes, I agree that it's not pretty. But the issue is that when folders come to play and the fdg profile files are separated to folders then it will be quite a surprising result. Even the very first examples of fdg that we had used that way or organizing the files and this would have caught that. I'll share the link to that example with you over Slack.

Tested it and passed on affected configurations.


Leverage default profile supplier for credential reload

Description
Leverage Default Profile Supplier for credentials reload as in: https://docs.aws.amazon.com/sdk-for-java/latest/developer-guide/credentials-profiles.html#profile-reloading
Test Steps
TBD
Checklist:

[X] I have tested my changes. No regression in existing tests.
[ ] I have modified and/or added unit-tests to cover the code changes in this Pull Request.

Related Issue
#357
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@embano1 verified locally by mounting credentials file in docker-compose setup via:
 - /Users/X/.aws/credentials:/.aws/credentials
Enabled AWS debug logs in config-log4j.properties via:
log4j.logger.software.amazon.awssdk=DEBUG

Modified credentials, issued another request and got:
[2024-08-12 21:00:48,340] DEBUG [eventbridge-e2e|task-0] (ProfileFileSupplier()) Cached value is stale and will be refreshed. (software.amazon.awssdk.utils.cache.CachedSupplier:85)
connect-1     | [2024-08-12 21:00:48,341] DEBUG [eventbridge-e2e|task-0] (ProfileFileSupplier()) Refreshing cached value. (software.amazon.awssdk.utils.cache.CachedSupplier:85)
connect-1     | [2024-08-12 21:00:48,345] WARN [eventbridge-e2e|task-0] (ProfileFileSupplier()) Retrieved value expiration is in the past (2024-08-12T19:00:48.341653877Z). Using expiration of 2024-08-12T19:00:49.345011033Z (software.amazon.awssdk.utils.cache.CachedSupplier:106)
connect-1     | [2024-08-12 21:00:48,346] DEBUG [eventbridge-e2e|task-0] (ProfileFileSupplier()) Successfully refreshed cached value. Next Prefetch Time: +1000000000-12-31T23:59:59.999999999Z. Next Stale Time: 2024-08-12T19:00:49.345011033Z (software.amazon.awssdk.utils.cache.CachedSupplier:85)

Also verified by replacing with invalid credentials and ran into connector error for invalid token during next request.

Thx a ton!
Regarding

WARN [eventbridge-e2e|task-0] (ProfileFileSupplier()) Retrieved value expiration is in the past (2024-08-12T19:00:48.341653877Z). Using expiration of 2024-08-12T19:00:49.345011033Z (software.amazon.awssdk.utils.cache.CachedSupplier:106)

Is that a concern and does it happen every time the credentials are refreshed? Or just particular to your environment?

cc/ @ryancuk first fix work in progress, feel free (or your team) to take a look and provide feedback

Is that a concern and does it happen every time the credentials are refreshed? Or just particular to your environment?

It always happens but might be related to the way how the credential file is mounted. With my setup it always keeps the timestamp when it was mounted - even if you change the file. However, I didn't experience any side affects of this approach and the SDK includes extensive test coverage on that behavior.

cc/ @ryancuk first fix work in progress, feel free (or your team) to take a look and provide feedback

Thanks very much for the fix. It looks good to me.

Thx @maschnetwork sounds like this one is good to moved to a ready PR?

@embano1 moved to PR

LGTM, do you want to squash your commits before I merge?

done

hi @embano1, please let me know when the new release is ready for use.

@ryancuk do you need a Confluent connector release on Confluent hub or are the artifacts here on Github as part of the release sufficient?

@embano1, yes we source the connector from confluent. Appreciate for the great help!

@embano1 that works. appreciated!

Will try to cut a release in the next hours and ping you here.

@ryancuk new release is here: https://github.com/awslabs/eventbridge-kafka-connector/releases/tag/v1.3.1
The Confluent Hub artifacts are here (zip format): https://github.com/awslabs/eventbridge-kafka-connector/releases/download/v1.3.1/aws-kafka-eventbridge-sink-v1.3.1.zip


Running Vue in development mode

Are you aware that Vue.js is running in development mode on https://aatishb.com/covidtrends/ ?
There's lots more info about this here: https://vuejs.org/v2/guide/deployment.html
Your graphing tool is a really great resource, thank you!

Thanks for pointing this out, good call!

We should fix this. We'll need to add the vue.min.js file into the libraries folder and link appropriately. Let's leave the current vue file in there too. That way when developing, we can just remove the .min part to switch to development mode.
You're welcome to put in a PR for this if you like.

@all-contributors add @NeverFearTheasHere for bug


Feat theme

#424

https://github.com/user-attachments/assets/0a2d5f04-881b-4aa0-ad9b-7062c36a12ef


When using the example module to load PDFs in version 0.16, the PDF files will be downloaded many times repeatedly

https://github.com/user-attachments/assets/fd34c5e5-871a-4514-9d54-d6bce9207c62
Using version 0.15 works fine, but it is not compatible with gradio 5.1.0. I hope this issue can be fixed. Thank you.

Interesting. Can you share the code please?

https://huggingface.co/spaces/opendatalab/MinerU/blob/main/app.py

Fixed in 0.0.17


Rustfmt fails to format long match

If I run rustfmt over the following unformatted snippet:
pub fn foo() {
    if condition {
        for i in range {
            let t = thread::spawn(move || {
match pkg::this_is_a_function(
  TypeName::from_foo(argument_x).unwrap(), a, &ts) {
Ok(_) => debug!("Some Okayish string"),
Err(e) => warn!("Some error-ish string {}. Will do something else", e),
}
});
        }
    }

}

I get this:
pub fn foo() {
    if condition {
        for i in range {
            let t = thread::spawn(move || {
                                      match pkg::this_is_a_function(
  TypeName::from_foo(argument_x).unwrap(), a, &ts) {
Ok(_) => debug!("Some Okayish string"),
Err(e) => warn!("Some error-ish string {}. Will do something else", e),
}
                                  });
        }
    }

}

and no errors. This is bad. What I would expect is something like the following (achieved by reducing this_is_a_function argument lengths, and running rustfmt again):
pub fn foo() {
    if condition {
        for i in range {
            let t = thread::spawn(move || {
                match pkg::this_is_a_function(TypeName::from_foo(argument_x).unwrap(), a, &ts) {
                    Ok(_) => debug!("Some Okayish string"),
                    Err(e) => warn!("Some error-ish string {}. Will do something else", e),
                }
            });
        }
    }
}

Or (since the above exceeds line limit slightly):
pub fn foo() {
    if condition {
        for i in range {
            let t = thread::spawn(move || {
                match pkg::this_is_a_function(
                        TypeName::from_foo(argument_x).unwrap(), a, &ts) {
                    Ok(_) => debug!("Some Okayish string"),
                    Err(e) => warn!("Some error-ish string {}. Will do something else", e),
                }
            });
        }
    }
}

Notice how in the bad examples the match is much more to the right, than it should be and the match branches are completely unformatted.
Also, while at it, formatting the abovementioned "slightly too long" snippet of
pub fn foo() {
    if condition {
        for i in range {
            let t = thread::spawn(move || {
                match pkg::this_is_a_function(TypeName::from_foo(argument_x).unwrap(), a, &ts) {
                    Ok(_) => debug!("Some Okayish string"),
                    Err(e) => warn!("Some error-ish string {}. Will do something else", e),
                }
            });
        }
    }
}

results in a strictly worse, and even longer:
pub fn foo() {
    if condition {
        for i in range {
            let t = thread::spawn(move || {
                                      match pkg::this_is_a_function(TypeName::from_foo(argument_x).unwrap(), a, &ts) {
                    Ok(_) => debug!("Some Okayish string"),
                    Err(e) => warn!("Some error-ish string {}. Will do something else", e),
                }
                                  });
        }
    }

}

P.s.: rustfmt 0.8.3 (), rust nightly (cargo 0.20.0-nightly (397359840 2017-05-18))

I think this is fixed on the current master. Could you try?

Yes, this is indeed fixed, thanks!


Camera for mapping

Hi! I am learning multi-sensor fusion related knowledge and just found this amazing project. Can I ask is the camera involved in the mapping, or obstacle avoidance?

Thank you for the kind words!
As for the camera, it's mainly there for the user to see where the robot is, basically a first person view.
Mapping and obstacle avoidance are achieved using the RPlidar sensor. Then sensor fusion is carried out on wheel odometry and IMU data to provide more accurate robot odometry estimates.
I hope this helps to clarify things.

Got it! Thanks for the reply:)


expandable grid with horizontal scrolling

We need to also add in the tutorials a demo for expandable grid that supports horizontal scrolling
Right now there are some known issues that needs to be fixed like recalcing the expanded row width when scrolling event is triggered.
I'm not sure I have time to do this chore so anyone else that might have some time can take it

This appears to be working: http://plnkr.co/edit/pqxMilIRwbBTRsGMxOe9?p=preview.  Is there any reason we wouldn't close?

Closing: solution proposed that should resolve the issue, no further comments for 2 weeks, assuming solution has resolved issue.


Support object detections by GPT-4o

adolfus — 05/08/2024 11:42 PM
Can Tensorflow object detections be sent to SRS from a Python script so that the object detections can be viewed in a live and VOD stream?
tagore — 05/09/2024 10:06 PM
like ads detection, black screen detection, freeze , or objects?
Winlin — 05/10/2024 9:11 AM
Interesting.
tagore — 05/10/2024 11:30 PM
it would be very usefull in many uses cases, tv cable operators for example ..
Winlin — 05/11/2024 11:02 AM
What's your product? How does. your user use it?
Sorry, I don't understand how tv cable operator with python tensorflow object and live stream.
tagore — 05/13/2024 9:14 PM
because we using iptv internally to distribute signals, also, the tv satellite encoders/decoders do network output and also ASI output ...
so, we can use system to detect black screens o freeze, o comercial ads detection, using the network part.
We receive the channel via satellite with a receiving device that has IP and ASI output.
That network output can be used to monitor the channel, whether it freezes, loses frames, starts a commercial or ends.
Winlin — 05/14/2024 3:45 PM
How do you convert the IPTV signal into IP and ASI, and then send it to the SRS server using the RTMP protocol?
tagore — 05/14/2024 9:08 PM
satellite -- satellite receptor ( they have udp multicast output and ASI output ) -- ffmpeg (RMTP or SRT ) -- SRS
and also have channels comming from another city, using ffmpeg to SRS and the ffmpeg again to inject in the analog coaxial part of the network.
here they have hardware equipment that can recieve udp multicast and the inject in the coaxial network. i need to check hardware names if needed.
Winlin — 05/15/2024 at 9:51 AM
If you can use FFmpeg to convert to RTMP, then you can also use FFmpeg to capture screenshots as PNG images. Generally, OpenCV supports image analysis.
Of course, FFmpeg + OpenCV is a classic technical solution. I think the recent GPT-4o has great potential for application in detecting and summarizing audio and video content. We will consider implementing this scenario in Oryx. I have created a new task for this, but we have a lot of work and no clear deadline, no ETA.
GPT-4o is a new flagship model that can reason across audio, vision, and text in real time. See https://openai.com/index/spring-update/

I tried GPT-4o's image text recognition, and the accuracy is 100%. The accuracy has significantly improved compared to GPT-4, and the response time is only half as long.

Fixed in v5.15.3


⚠ Processors has degraded performance

In b531c88, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 52 ms

Resolved: Processors performance has improved in 3563b23.


Directory.Build.targets is not imported for multi-targeting projects where TargetFramework is not defined

When a "Microsoft.NET.Sdk" project defines a TargetFrameworks property instead of a TargetFramework property (effectively activating the multi-targeting behavior), it no longer imports Directory.Build.targets in the top-level evaluation.
When a TargetFramework is set, it imports both Directory.Build.props and Directory.Build.targets.
But when only TargetFrameworks is defined, it only imports Directory.Build.props.
This distinction is very subtle and unexpected. It took me quite some time to diagnose a build issue before I figured this out. I trust this was an unintentional oversight that can be fixed.
Repro project:
dirprops.zip
When building the Restore target, I see this:
msbuild /t:restore
  Restoring packages for C:\temp\dirprops\lib\lib.csproj...
  Lock file has not changed. Skipping lock file write. Path: C:\temp\dirprops\lib\obj\project.assets.json
  Restore completed in 378.45 ms for C:\temp\dirprops\lib\lib.csproj.

  NuGet Config files used:
      C:\Users\andarno\AppData\Roaming\NuGet\NuGet.Config
      C:\Program Files (x86)\NuGet\Config\Microsoft.VisualStudio.Offline.config

  Feeds used:
      https://api.nuget.org/v3/index.json
      C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\
  AddInProps is executing...

But when I define TargetFramework I see both targets executing:
msbuild /t:restore /p:targetframework=netstandard1.3
  Restoring packages for C:\temp\dirprops\lib\lib.csproj...
  Generating MSBuild file C:\temp\dirprops\lib\obj\lib.csproj.nuget.g.props.
  Generating MSBuild file C:\temp\dirprops\lib\obj\lib.csproj.nuget.g.targets.
  Writing lock file to disk. Path: C:\temp\dirprops\lib\obj\project.assets.json
  Restore completed in 764.25 ms for C:\temp\dirprops\lib\lib.csproj.

  NuGet Config files used:
      C:\Users\andarno\AppData\Roaming\NuGet\NuGet.Config
      C:\Program Files (x86)\NuGet\Config\Microsoft.VisualStudio.Offline.config

  Feeds used:
      https://api.nuget.org/v3/index.json
      C:\Program Files (x86)\Microsoft SDKs\NuGetPackages\
  AddInProps is executing...
  AddInTargets is executing...

Duplicate of #1721, fixed for the 15.3 release.


Similar function signatures for Learning Curve retrieval

In my opinion, having the same function signatures for the two types of retrieval makes sense:

query(config: C, fidelity) -> R: gives the point or the exact result at fidelity
trajectory(config: C, fidelity) -> List[R]: gives the full learning curve until fidelity

Additionally, I was wondering if we can already have a placeholder parameter that can be further passed to either a benchmark state during initialisation or to these function calls above. That is whether the evaluation is being continued or thawed.
The only thing that should change then is the cost of continuations. Not sure where then is the best place to change. We could also kind of do it post-hoc for the evaluations made by subtracting the cost incurred for a lower fidelity evaluation.
For the non-benchmark case, NePS anyways handles continuation so should work out fine I believe.
@DaStoll @eddiebergman thoughts?
Please feel free to take the call.

As a note, I changed def trajectory to be but I see your argument none the less
@abstractmethod
def trajectory(
    self,
    config: C,
    *,
    frm: F = ...,
    to: F = ...,
) -> list[R]:

Regarding the freeze-thaw action, it only makes sense with freeze-thawable networks, I would leave it to post-hoc for simplicity of the benchmark


Allow to manually calculate style for element

What does this do?
Adds interpolateStyle to Transition properties. Default to config-to-style. This will allow to manually calculate element styles for cases that config-to-style does not support.
Solves cases like  transform: translate(${style.translateX}%, ${style.translateY}%).
Example of usage
const TRANSFORM = require('get-prefix')('transform')

class AlertWithCustomStyles extends Component {
  static defaultPops = {
    type: ''
  }

  _interpolateStyle = style => ({
      [TRANSFORM]: `translate(${style.translateX}%, ${style.translateY}%)`,
      opacity: style.opacity
  });

  render() {
    const { type, text } = this.props
    return (
      <Transition
        component={false}
        measure={false}
        interpolateStyle={this._interpolateStyle}
        enter={{
          opacity: 1,
          translateX: 0,
          translateY: 0
        }}
        leave={{
          opacity: 0,
          translateX: 100,
          translateY: 100
        }}
      >
        {
          text !== '' &&
          <div key="alert" className={"alert" + (type && ` alert--${type}`)}>
            {text}
          </div>
        }
      </Transition>
    )
  }
}

What is in this PR?
PR has updated code, sample and readme.
Why?
This lib provides dramatic simplification for react-motion. But for our use case config-to-style is setting limitation that can be easily remove. Would appreciate new version of lib to include this soon.

@souporserious what with that pr?

Sorry, I've been super busy and haven't been able to give this as much attention as I would have liked 😞  I'm not sure I understand what this offers over the current implementation? You should be able to use properties like translateX and translateY, or am I missing something? I'd like to not expose something like interpolateStyle unless it's absolutely necessary. Please let me know if we can just fix your use case in config-to-style.

In example above - we use translate with percent instead of pixels. Basic implimentation allows only pixels. Exposing interpolateStyles allows to override default behavior

Ahh definitely!!! I have a solution for this :) sorry I haven't had time to tackle it 😞  I will try and get it to it this week. It will solve this problem plus a few other current issues.

Need this.  Did it get added, or an alternative approach implemented?

Did this ever get merged? I need to be able to interpolate percentages too.

Hey guys, any news on when this will be available?


Compilation issue with "sdp_test" in nmos-cpp-registry-test right now

This previously worked fine. Build fails at CMakeFiles/nmos-cpp-registry-test.dir/sdp/test/sdp_test.cpp.o with latest commit (specifically d6e9c49).
I've re-checked the dependencies and nothings seems to have changed. My detailed output from Docker Build is below:

Step 7/10 : RUN mkdir /home/nmos-cpp/Development/build &&     cd /home/nmos-cpp/Development/build &&     cmake     -G "Unix Makefiles"     -DCMAKE_CONFIGURATION_TYPES:STRING="Debug;Release"     -DBoost_USE_STATIC_LIBS:BOOL="1"     -DBOOST_INCLUDEDIR:PATH="/home/boost_1_67_0"     -DBOOST_LIBRARYDIR:PATH="/home/boost_1_67_0/x64/lib"     -DWEBSOCKETPP_INCLUDE_DIR:PATH="/home/cpprestsdk-2.10.2-nmos-cpp/Release/libs/websocketpp"     -DCPPREST_INCLUDE_DIR:PATH="/home/cpprestsdk-2.10.2-nmos-cpp/"     -build /home/nmos-cpp/Development/build .. &&     make
---> Running in 20f9f7a5d33f
-- The C compiler identification is GNU 5.4.0
-- The CXX compiler identification is GNU 5.4.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Found ZLIB: /usr/lib/x86_64-linux-gnu/libz.so (found version "1.2.8")
-- Found OpenSSL: /usr/lib/x86_64-linux-gnu/libcrypto.so (found version "1.0.2g")
-- Found cpprestsdk
-- Using configured websocketpp include directory at /home/cpprestsdk-2.10.2-nmos-cpp/Release/libs/websocketpp
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Boost version: 1.67.0
-- Found the following Boost libraries:
--   system
--   date_time
--   regex
--   thread
--   chrono
--   atomic
-- Configuring done
-- Generating done
CMake Warning:
Manually-specified variables were not used by the project:
CMAKE_CONFIGURATION_TYPES

-- Build files have been written to: /home/nmos-cpp/Development/build
Scanning dependencies of target mdns_static
[  1%] Building CXX object CMakeFiles/mdns_static.dir/mdns/core.cpp.o
[  1%] Building CXX object CMakeFiles/mdns_static.dir/mdns/dns_sd_impl.cpp.o
[  2%] Building CXX object CMakeFiles/mdns_static.dir/mdns/service_advertiser_impl.cpp.o
[  2%] Building CXX object CMakeFiles/mdns_static.dir/mdns/service_discovery_impl.cpp.o
/home/nmos-cpp/Development/mdns/service_discovery_impl.cpp: In function 'bool mdns_details::getaddrinfo(const address_handler&, const string&, uint32_t, const duration&, DNSServiceCancellationToken, slog::base_gate&)':
/home/nmos-cpp/Development/mdns/service_discovery_impl.cpp:345:14: warning: unused variable 'more_coming' [-Wunused-variable]
bool more_coming = true;
^
[  3%] Linking CXX static library libmdns_static.a
[  3%] Built target mdns_static
Scanning dependencies of target nmos-cpp-registry-test
[  3%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/nmos-cpp-registry/test/main.cpp.o
[  4%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/cpprest/api_router.cpp.o
[  4%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/cpprest/host_utils.cpp.o
[  5%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/cpprest/http_utils.cpp.o
[  5%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/cpprest/json_utils.cpp.o
[  6%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/cpprest/test/api_router_test.cpp.o
[  6%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/cpprest/test/http_utils_test.cpp.o
[  7%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/cpprest/test/json_utils_test.cpp.o
[  7%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/cpprest/test/regex_utils_test.cpp.o
[  8%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/mdns/test/core_test.cpp.o
[  8%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/mdns/test/mdns_test.cpp.o
[  9%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/nmos/api_utils.cpp.o
[  9%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/nmos/test/api_utils_test.cpp.o
[ 10%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/nmos/test/paging_utils_test.cpp.o
[ 10%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/sdp/sdp_grammar.cpp.o
[ 11%] Building CXX object CMakeFiles/nmos-cpp-registry-test.dir/sdp/test/sdp_test.cpp.o
/home/nmos-cpp/Development/sdp/test/sdp_test.cpp:97:40: warning: integer constant is so large that it is unsigned
{ sdp::fields::session_id,<PHONE_NUMBER>7046861077 },
^
/home/nmos-cpp/Development/sdp/test/sdp_test.cpp:98:45: warning: integer constant is so large that it is unsigned
{ sdp::fields::session_version,<PHONE_NUMBER>7046861078 },
^
/home/nmos-cpp/Development/sdp/test/sdp_test.cpp: In function 'void ____C_A_T_C_H____T_E_S_T____0()':
/home/nmos-cpp/Development/sdp/test/sdp_test.cpp:102:22: error: conversion from '__int128' to 'const web::json::details::value_init' is ambiguous
}, keep_order) },
^
In file included from /home/nmos-cpp/Development/sdp/json.h:5:0,
from /home/nmos-cpp/Development/sdp/test/sdp_test.cpp:5:
/home/nmos-cpp/Development/cpprest/json_utils.h:231:30: note: candidate: web::json::details::value_init::value_init(int32_t)
using value::value;
^
/home/nmos-cpp/Development/cpprest/json_utils.h:231:30: note: candidate: web::json::details::value_init::value_init(uint32_t)
/home/nmos-cpp/Development/cpprest/json_utils.h:231:30: note: candidate: web::json::details::value_init::value_init(int64_t)
/home/nmos-cpp/Development/cpprest/json_utils.h:231:30: note: candidate: web::json::details::value_init::value_init(uint64_t)
/home/nmos-cpp/Development/cpprest/json_utils.h:231:30: note: candidate: web::json::details::value_init::value_init(double)
/home/nmos-cpp/Development/cpprest/json_utils.h:237:17: note: candidate: web::json::details::value_init::value_init(bool)
value_init(bool b) : value(b) {}
^
In file included from /usr/include/c++/5/bits/stl_algobase.h:64:0,
from /usr/include/c++/5/memory:62,
from /usr/local/include/cpprest/json.h:18,
from /home/nmos-cpp/Development/sdp/sdp.h:4,
from /home/nmos-cpp/Development/sdp/test/sdp_test.cpp:2:
/usr/include/c++/5/bits/stl_pair.h:133:12: note:   initializing argument 2 of 'constexpr std::pair<_T1, _T2>::pair(_U1&&, const _T2&) [with _U1 = const web::json::field&;  = void; _T1 = std::__cxx11::basic_string; _T2 = web::json::details::value_init]'
constexpr pair(_U1&& __x, const _T2& __y)
^
/home/nmos-cpp/Development/sdp/test/sdp_test.cpp:250:18: error: no matching function for call to 'value_of(, const bool&)'
}, keep_order);
^
In file included from /home/nmos-cpp/Development/sdp/json.h:5:0,
from /home/nmos-cpp/Development/sdp/test/sdp_test.cpp:5:
/home/nmos-cpp/Development/cpprest/json_utils.h:245:33: note: candidate: web::json::value web::json::value_of(std::initializer_list<std::pair<std::__cxx11::basic_string, web::json::details::value_init> >, bool)
inline web::json::value value_of(std::initializer_list<std::pair<utility::string_t, web::json::details::value_init>> fields, bool keep_order = false)
^
/home/nmos-cpp/Development/cpprest/json_utils.h:245:33: note:   no known conversion for argument 1 from '' to 'std::initializer_list<std::pair<std::__cxx11::basic_string, web::json::details::value_init> >'
/home/nmos-cpp/Development/cpprest/json_utils.h:259:33: note: candidate: template web::json::value web::json::value_of(std::initializer_listweb::json::details::value_init)
inline web::json::value value_of(std::initializer_listweb::json::details::value_init elements)
^
/home/nmos-cpp/Development/cpprest/json_utils.h:259:33: note:   template argument deduction/substitution failed:
/home/nmos-cpp/Development/sdp/test/sdp_test.cpp:250:18: note:   cannot convert '{{sdp::fields::protocol_version, 0}, {sdp::fields::origin, }, {sdp::fields::session_name, "Example Sender 1 (Video)"}, {sdp::fields::time_descriptions, web::json::value_of(std::initializer_listweb::json::details::value_init) with  = void}, {sdp::fields::attributes, web::json::value_of(std::initializer_listweb::json::details::value_init) with  = void}, {sdp::fields::media_descriptions, web::json::value_of(std::initializer_listweb::json::details::value_init) with  = void}}' (type '') to type 'std::initializer_listweb::json::details::value_init'
}, keep_order);
^
make[2]: *** [CMakeFiles/nmos-cpp-registry-test.dir/sdp/test/sdp_test.cpp.o] Error 1
make[1]: *** [CMakeFiles/nmos-cpp-registry-test.dir/all] Error 2
make: *** [all] Error 2
CMakeFiles/nmos-cpp-registry-test.dir/build.make:257: recipe for target 'CMakeFiles/nmos-cpp-registry-test.dir/sdp/test/sdp_test.cpp.o' failed
CMakeFiles/Makefile2:67: recipe for target 'CMakeFiles/nmos-cpp-registry-test.dir/all' failed
Makefile:94: recipe for target 'all' failed
The command '/bin/sh -c mkdir /home/nmos-cpp/Development/build &&     cd /home/nmos-cpp/Development/build &&     cmake     -G "Unix Makefiles"     -DCMAKE_CONFIGURATION_TYPES:STRING="Debug;Release"     -DBoost_USE_STATIC_LIBS:BOOL="1"     -DBOOST_INCLUDEDIR:PATH="/home/boost_1_67_0"     -DBOOST_LIBRARYDIR:PATH="/home/boost_1_67_0/x64/lib"     -DWEBSOCKETPP_INCLUDE_DIR:PATH="/home/cpprestsdk-2.10.2-nmos-cpp/Release/libs/websocketpp"     -DCPPREST_INCLUDE_DIR:PATH="/home/cpprestsdk-2.10.2-nmos-cpp/"     -build /home/nmos-cpp/Development/build .. &&     make' returned a non-zero code: 2
Makefile:9: recipe for target 'build' failed
make: *** [build] Error 2

Thanks for the report, I checked for exactly this sort of problem when I made the change, but obviously not on enough compilers.

Hi, Rich. Hopefully that fixes things! Thanks, again.

Thanks Gareth... Compilation now working with commit 8c36599
Much appreciated - Rich


CurrentUser instead of LocalMachine listed in Pode Tutorial Docs

Describe the Bug
In the following links its said and referenced to store the certs in CurrentUser instead of LocalMachine
https://badgerati.github.io/Pode/Tutorials/Certificates/
https://badgerati.github.io/Pode/Tutorials/Endpoints/Basics/#certificates
Steps To Reproduce
Steps to reproduce the behavior:

Go to https://badgerati.github.io/Pode/Tutorials/Certificates/ and https://badgerati.github.io/Pode/Tutorials/Endpoints/Basics/#certificates
Find 'CurrentUser' to see the misplaced cert store references.

Expected Behavior
After speaking with @Badgerati it should be listed in LocalMachine instead of CurrentUser
Platform

Tutorial Documentation

Additional Context
Add any other context about the problem here.

Mentioned in Gitter, but I was wrong and the docs are right - been playing in IIS too much of recent. The certificates are meant to be in Cert:\CurrentUser\My; the bug is that PowerShell is now treating an enum value as a literal string (including the class name) for some bizarre reason.

@Badgerati, I've tested this and it works for me. Thanks again!


Add guide on how to install Python requirements

Added a short guide on how to install Python requirements for those new to Python.

@kallqvist

@kallqvist Any progress on this?

@kallqvist Any progress on this?


Add copy and open explorer icons to transaction detail

Description
In the moment the detail view of a message offers copying to clipboard while you hover over the message id, sent address, receive address. Change this and use icons instead. 1 icon that copies and 1 icon that directly uses the content and opens explorer.iota.org. Also implement a success popup message "copied to clipboard". And maybe add tooltips if you hover over the icons (copy to clipboard, view in explorer)
Motivation
atm its not obvious for the user that the option to copy single details exists. Icons will make it easier and clearer. Also the lookup option in explorer is not yet implemented
Requirements
in this view

add icons next to message, send address, receive address like this:

Open questions (optional)
Use this section to ask any questions that are related to the feature.
Are you planning to do it yourself in a pull request?
no

Hey @Phyloiota, I like this suggestion! Thank you for making it ~ For now, I've moved it into a discussion here 🚀


stateio: double quotes prohibit jstree JSON

Double quotes in Org, Record Group, Job, or configuration scenarios names are not handled by JSON serialization for jstree interfaces in StateIO.

Fixed with Django built-in escapejs filter.


feat: code generation for field-base primitive types

This PR introduces the code generation of field-based functions for a set of default pre-provided types allowing the specification of custom types.

@DanySK @angelacorte
I have implemented the basic machinery for primitive types field-based code generation and provided a minimal test ensuring the generated code compiles.
Remaining steps:

Provide a way to specify custom types (this should be trivially done by specifying the additional types in generateFieldFunctionsForTypes) maybe via gradle config?
Create a gradle task managing the code generation and provide some customization like the one above
Make the generated primitives available to the project and the distributed artifacts

Do you see anything else I forgot to mention?

Is this still a draft?

A few changes, plus the organization is suboptimal, we have two packages each with one class. I suggest moving the Utils into codegen. Also I would rename it into something like KotlinFieldReflection
Finally, it's not clear to me how the generated code is then included in primitives, I'd have expected the code generator to be used by the build at some point

I left a comment 2 weeks ago with the remaining steps to make this PR ready for review


completed margin and padding exercise

Because

This PR

Issue

Closes #XXXXX
Additional Information

Pull Request Requirements

[ ] I have thoroughly read and understand The Odin Project Contributing Guide
[ ] The title of this PR follows the location of change: brief description of change format, e.g. 01-flex-center: Update self check
[ ] The Because section summarizes the reason for this PR
[ ] The This PR section has a bullet point list describing the changes in this PR
[ ] If this PR addresses an open issue, it is linked in the Issue section
[ ] If applicable, I have ensured that the TOP solution files match the Desired Outcome image

Good job completing the exercises.
As per our instructions in the repo README, please do not open pull requests with your solution code, as we will close them without merging.


fixing the function to deal with JSON format

Deal with JSON format on different machines
Fix merge function. It does not recognise sort=True argument

The issue was solved updating Pandas


ValueError: Cannot apply_along_axis when any iteration dimensions are 0

Sentiment Analysis Code is not working due to the above mentioned error.
ValueError                                Traceback (most recent call last)
 in ()
4 #docs = [d for d in train_pred if any([v for (k,v) in d.spans.items()])]
5
----> 6 unified_model.fit(train_pred)
7
8 unified_model.annotate_docbin("train_pred.docbin", "train_pred.docbin")
4 frames
/usr/local/lib/python3.7/dist-packages/skweak/aggregation.py in fit(self, docs, **kwargs)
85
86         obs_generator = (self.get_observation_df(doc) for doc in docs)
---> 87         self._fit(obs_generator, **kwargs)
88
89
/usr/local/lib/python3.7/dist-packages/skweak/generative.py in _fit(self, all_obs, cutoff, n_iter, tol)
95
96         # And add the counts from majority voter
---> 97         self._add_mv_counts(all_obs)
98
99         # Finally, we postprocess the counts and get probabilities
/usr/local/lib/python3.7/dist-packages/skweak/generative.py in _add_mv_counts(self, all_obs)
417
418             # And aggregate the results
--> 419             agg_array = mv.aggregate(obs).values
420
421             if len(agg_array)==0:
/usr/local/lib/python3.7/dist-packages/skweak/voting.py in aggregate(self, obs)
51             return np.bincount(x[x>=0], weights=weights[x>=0],
52                                minlength=len(self.observed_labels))
---> 53         label_votes = np.apply_along_axis(count_fun, 1, obs.values).astype(np.float32)
54
55         # For token-level sequence labelling, we need to normalise the number
<array_function internals> in apply_along_axis(*args, **kwargs)
/usr/local/lib/python3.7/dist-packages/numpy/lib/shape_base.py in apply_along_axis(func1d, axis, arr, *args, **kwargs)
376         raise ValueError(
377             'Cannot apply_along_axis when any iteration dimensions are 0'
--> 378         ) from None
379     res = asanyarray(func1d(inarr_view[ind0], *args, **kwargs))
380
ValueError: Cannot apply_along_axis when any iteration dimensions are 0

Could you repost the python code you were trying to run? It's a bit difficult for me to understand what was exactly run from your post.


formItem.navigate vs. XrmNavigation.openForm

What's the difference between navigate and openForm?

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

ID: 31d61d17-1b6a-0128-0c88-1e0afeefa06d
Version Independent ID: 7a1aa000-756f-cf8b-d8e3-fa989e7eebcd
Content: navigate (Client API reference) in Dynamics 365 Customer Engagement
Content Source: ce/developer/clientapi/reference/formContext-ui-formSelector/navigate.md
Service: crm-online
GitHub Login: @KumarVivek
Microsoft Alias: kvivek

Use formItem.navigate to switch between different forms of the same entity/record.
Use Xrm.Navigation.openForm to open form of a different entity/record in a same or different window.


Software Engineering at Google

https://blog.suixin.kim/Software-Engineering-at-Google/#/
Description

tt

Hello, world!

Hello, world!


fix(curriculum): Read-search-ask link now point to correct url as noted in the issue

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)
[x] My pull request targets the master branch of freeCodeCamp.
[x] None of my changes are plagiarized from another source without proper attribution.
[x] All the files I changed are in the same world language (for example: only English changes, or only Chinese changes, etc.)
[x] My changes do not use shortened URLs or affiliate links.

Closes #37751

Why are there http  links? Shouldn't everything be served over https? I can make a very quick adjustment to the script so it picks up http as well, not sure it makes sense to split up PRs. Let me know

@Mozar10 Go ahead and make all the links https.

@RandellDawson @moT01 updated.

Hi @moT01 @RandellDawson can we get a merge on this?

@raisedadead I wish these changes were not mixed across all languages.  There is a reason we have the 5th bullet in the checklist.  It makes it much easier to review the same language for the same changes.  Many of the non-English ones are all on a single line, and the GitHub view does not clearly show the changes.  I end up having to use a site like diffchecker to validate the only thing changed was the link.

I can make a separate PR for that one if needed.

@moT01 Maybe just add a commit to this PR for the one missed?

I pointed out one other spot that is missed...

And there's at least one more spot in the ask for help modal - when you are on a challenge and click the ask for help button, a modal pops up with a broken link as well.

I can make a separate PR for that one if needed.
Other than that, I scanned through the diffs of the english files and it LGTM  - This should make all the links work in theory. But I didn't go test them all.

Ooh right, my bad. The script didn't pick that one up because of the concatenation. Thanks for fixing it


My edits for my branch

This merge request has all our edits to the project. I made a mistake a few times with the pull requests.


My icons break when setting Atom to be a default program for files

Prerequisites

[ x ] Can you reproduce the problem in safe mode?
[ x ] Are you running the latest version of Atom?
[ x ] Did you check the debugging guide?
[ x ] Did you check the FAQs on Discuss?
[ x ] Are you reporting to the correct repository?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.
Description
When ever I associate Atom to a specific file, for instance a .txt file, the default icon for that file is broken. Any file I tell to make Atom its default progam the icon for that file shows up broken. When ever I change the default program to notepad, the icon changes to notepads associated file icon. The icon for notepad associated files show up fine and do not appear broken. I have uninstalled Atom and reinstalled. The issue still persists.
I do not remember exactly when this started happening, but it was a while back. I have always kept Atom up to date.
Steps to Reproduce

Set Atom as the default file viewer.
Watch all your icons break before your very eyes.

Image: http://i.imgur.com/MvUCBFT.gif

Expected behavior: For the files to display the Atom icon like it use to.
Actual behavior: Displays nothing but a broken icon instead.
Versions
Atom    : 1.11.2
Electron: 0.37.8
Chrome  : 49.0.2623.75
Node    : 5.10.0
OS: Windows 7 x64 Ultimate SP1 (6.1, Build 7601)

Thanks for contributing! This is a duplicate of https://github.com/atom/atom/issues/12974 and has been fixed in Atom 1.12 where the files will use the new icon.


release 3.7.1

Summary
Release 3.7.1
Checklist

[ ] The Pull Request has tests
[ ] A changelog file has been created under changelog/unreleased/kong or skip-changelog label added on PR if changelog is unnecessary. README.md
[ ] There is a user-facing docs PR against https://github.com/Kong/docs.konghq.com - PUT DOCS PR HERE

Issue reference

Do we need .gitkeep file?


Feature request: Clone by VM ID rather than name

It is possible to have multiple VMs of the same name, but IDs are unique.
The code chooses the first one: https://github.com/Telmate/terraform-provider-proxmox/blob/bd28855b7c34d9d6913f4ac22c1933610a085cc2/proxmox/resource_vm_qemu.go#L1028
Of course it's not ideal to have multiple VMs with the same name, but it's likely. Especially when using the packer plugin for generating templates, due to the restrictions put in place on the name: https://github.com/hashicorp/packer-plugin-proxmox/blob/main/builder/proxmox/common/config.go#L281

I agree. To me it was even kind of confusing at first that the name seems to be the unique identifier, since the VM ID would to me seem like a much more obvious and logical choice.

Issue still persists in latest version because this feature is unimplemented.

Yeah this keeps us from committing to using this as well


Moved PowerShellGet to be a git submodule

This decouples PowerShellGet from the PowerShell repository allowing development to occur on the PowerShellGet repository

Hi @kilasuit, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by Microsoft and real humans are currently evaluating your PR.
TTYL, MSBOT;

@kilasuit, @vors, @raghushantha
Can we pull the latest version of PowerShellGet module from the PSGallery as a post-build step?

As we make our modules installable independently, I don't think we want to ship unreleased versions of those modules, which implies we don't want to build the modules as git submodules
Instead, I think we want to fetch packages from a nuget feed - most likely powershell.myget.org but possibly powershellgallery.com.

@lzybkr totally agree that we need to have that for v6 release but the concern I have currently is that there are 2 places to make changes until the work for #1979 is fully completed (which yes IMO would include pulling the modues in via a nuget feed of sorts like you've suggested once we get there) but I think for the short term pulling in as a git submodule is a realistic middle ground that allows us the time to correctly identify the right route for how we implement it as a bigger part of #1979 and stops the " 2 places to edit the same code" issue we currently have.
On reflection I should really have put the above in the original comment and I'm not actually sure why I didn't.

Hope that clears up any unnecessary confusion caused

We are moving forward with pulling a package (specifics to be determined). This work might not be done for the next release, but hopefully the release after that.
Introducing submodules is a pain, removing them is also a pain, so we're rejecting this PR.
As this issue should be resolved in the short term, we won't be making PowerShellGet/PackageManagement fixes in both places, we'll live with the bugs present in PowerShell/PowerShell for the next release.

No worries @lzybkr - totally agree with the points made re adding/removing submodules and glad to see this be planned to tie in within the next few releases.
I'll keep my eyes on how the package pulling implementation goes in line with #1979 as IMO getting that right really is crucial for the long term.


sjjddcdxvj

Please paste the output of the following command here: sudo edit-chroot -all

Please describe your issue:
If known, describe the steps to reproduce the issue:

Do you have any of the following that you could give?

Logs
Version numbers
Detailed description
System information


Allow percent_rank to not need an entire group in memory [databricks]

This fixes #4713
This fixes #6519
The performance is not as high as I would like it to be.
When I ran
spark.time(spark.range(2000000000L).selectExpr("id DIV 300000000 as part", "id DIV 2 as data").selectExpr("*", "percent_rank() OVER (PARTITION BY part ORDER BY data) as pr").orderBy("pr", "part", "data").show())

on my desktop, the performance dropped from 36 seconds to 39.8 seconds. About a 10% drop in total performance for this use case.  But it is capable of running queries that would not work before, and it is 11.7x faster than the CPU for the same query (compared to 12.9x faster before). There is also a lot of potential follow on work that could improve performance. I will file and link that work here.
I mostly wanted to get this up so we could get a fix out and then deal with performance improvements later on.

build

I filed two follow on issues for performance improvements.
https://github.com/NVIDIA/spark-rapids/issues/6552 and https://github.com/NVIDIA/spark-rapids/issues/6551

build

build


Extremely high VRAM usage

Hello, I just tried this q-diffusion implementation and it seems cool. However, the VRAM usage is 20GB on my RTX 3090 with 4-bit weights-only and --n_samples 1. Here is my command:
python scripts/txt2img.py --prompt "elon musk wearing a suit" --plms --cond --ptq --weight_bit 4 --quant_mode qdiff --no_grad_ckpt --split --n_samples 1 --outdir outputs --cali_ckpt models/sd_w4a8_ckpt.pth

And the result:

Are there any ways to reduce VRAM usage to 4 to 5GB? Thanks!

Hi, as explained in #1, currently the implementation is done with simulated quantization. With that said, we are working on releasing an end-to-end quantization implementation. If you are interested in only quantizing the weights to save VRAM, I will also consider having a weight-only truly quantized checkpoint released first.

Hi, Great Work.
But I wonder What specific tools or methods are you using to transition from simulated quantization to real deployment for the end-to-end quantization implementation?


Support Received Email with Amazon SES

http://docs.aws.amazon.com/ses/latest/DeveloperGuide/receiving-email.html

New MTA module "Sisimai::MSP::US::ReceivingSES" will be implemented.

This module will be included at the next release of Sisimai: v4.1.29.

Implemented at v4.1.29


Have no clue if this is allowed so delete this if it isn't

I've found that a lot of people are asking questions here instead of actual bugs or issues. To mitigate the issues being drowned by these questions I've created a discord group for people to discuss and ask technical questions about LLAMA.
Please get in their, if you're a dev of this project please DM me their so I can add you as an admin.
https://discord.gg/NMafuAkJyF
It would be cool if we could also share settings, eval metrics etc... Lets just collabarate their, and keep this place for issues.

Look in the first page of the repo (the Readme) there already is a discord for this.


Update image testing

🚀 Pull Request
Description

This PR

moves the graphics testing into its own little folder
generally tidies up the code with some modularity and pathlib
checks imagerepo.json for hashes when running the tests
expects the baseline images to be in the test data repo for idiff.py (which also checks if the imagerepo.json list matches
only holds one good image and one good hash (on the basis that source control and test image versioning covers this)
provides a convenience script (recreate_imagerepo.py) that will rewrite imagerepo.json based on the current contents of the baseline image folder, and list the changes made.
Moves the extra explanation that the docs doesn't need (it's just getting in the way of a user trying to fix the image tests) into a README

To do:

[x] I'm not sure how to preserve the functionality of @jamesp's image hash review page - maybe with these changes we don't need that page now?
[x] I'm not sure how the accept event is meant to work (when would it ever give an Accepted rather than a Duplicate"?)

Depends on https://github.com/SciTools/iris-test-data/pull/71

@wjbenfold Fancy rebasing to include the migration of CI from cirrus-ci to GHA?

@wjbenfold You have a minor conflict to resolve :+1:

Rebased for conflicts

https://github.com/SciTools/iris-test-data/blob/master/INDEX.md then open the images section shows the image index now

@wjbenfold I'm going to ignore the ephemeral metarelate link-check failure :see_no_evil:

Awesome effort @wjbenfold 🎉 🚀


Define the cache key for v1 multi-output recipes

This starts the definition for the new cache output in v1 recipes.
One can try the cache with --experimental in rattler-build. The documentation can be found here: https://prefix-dev.github.io/rattler-build/latest/multiple_output_cache/

@h-vetinari I played around with also caching the "source" in https://github.com/prefix-dev/rattler-build/pull/1226 and the example in https://github.com/wolfv/rattler-build-cache-test.
I now think that the cache should have its own source section. Then everything else will become quite straight-forward.
The example would then look like:
recipe:
  name: calculator
  version: 1.0.0

cache:
  source:
    path: ../

  requirements:
    build:
      - ${{ compiler('cxx') }}
      - cmake
      - ninja
  build:
    script:
      # make sure that `alternative_name.md` is not present
      - test ! -f ./alternative_name.md
      - mkdir build
      - cd build
      - cmake $SRC_DIR -GNinja ${CMAKE_ARGS}
      - ninja install

outputs:
  # this first output will include all files installed during the cache build
  - package:
      name: libcalculator

    requirements:
      run_exports:
        - ${{ pin_subpackage('libcalculator') }}

  - package:
      name: py-calculator
    source:
      - path: ../README.md
        file_name: alternative_name.md

    requirements:
      build:
        - ${{ compiler('cxx') }}
        - cmake
        - ninja
      host:
        - pybind11
        - python
        - libcalculator

    build:
      script:
        # assert that the README.md file is present
        - test -f ./alternative_name.md
        - cd build
        - cmake $SRC_DIR -GNinja ${CMAKE_ARGS} -DBUILD_PYTHON_BINDINGS=ON
        - ninja install

That's so close to the idea of cache being just a type of output! 🥳
outputs:
  - cache:
      name: optional, only needed if there are several caches
  - package:
      name: my-output
    build:
      needs-cache: bool # or cache.name

Yeah it could be done, but I think we can let it wait for v2 of the recipe format! :)

I now think that the cache should have its own source section. Then everything else will become quite straight-forward.

That sounds fine in principle. Could you explain a bit more what the thinking behind that is though? If there's already a source: on recipe-level, would the cache: have to repeat something?

That's so close to the idea of cache being just a type of output! 🥳

That would sound even better! More powerful and yet less divergence. (no opinion on whether this is v1 or v2 stuff)
However, this I don't like
outputs:
  # this first output will include all files installed during the cache build
  - package:
      name: libcalculator

I think this should never be automatic, and always need an explicit opt-in. Either the output says files: (in which case it could pick up parts of what cache: installed), or it actually does the ninja install itself (rather than during cache:). This would also be a better match for what the example is already doing for py-calculator.

@carterbox, please review


Add Ruby 2.1 and 2.2 in Travis config file

Make sure that microscope is working as expected on Ruby 2.1 & 2.2.

Coverage remained the same when pulling 6b31c6ba5256132e544275977a92c924fcdcf6fb on feature/travis-ruby-version into 79efbdd308f6451b156f5cebcfab98602d72e4bc on master.

Coverage increased (+0.0%) when pulling 50203ef72e2bd680dd019fae34a1568dbbb63117 on feature/travis-ruby-version into 79efbdd308f6451b156f5cebcfab98602d72e4bc on master.

:+1:


Unable to Comment on PR Diff View

Extension version: v0.44.0
VSCode Version: 1.68.1
OS: MacOS Monterey

Steps to Reproduce:

Checkout a Pull Request
Try to leave a comment, there is no button to actually add a comment for me.

I cannot figure out why this is happening. I have tried

Reloading the VS Code window
Restarting VS Code
Restarting my computer
Disabling / Re-enabling the extension
Uninstalling / Re-installing the extension
Switching to the prerelease version
Changing log mode to debug

I do see some weird things in my extension logs...
[Debug<PHONE_NUMBER>.164s] Failed to parse patch for outdated comments: Failed to execute git {
  "exitCode": 128,
  "gitCommand": "diff",
  "stdout": "",
  "stderr": "fatal: b9c0373d6fe5d64ddba74e9d7d7013bd4c394da5...f55bf421a858b9bdd4f0596fe7ee4727291938ce: no merge base\n"
}

I noticed that the git log only had a single commit, so I tried --unshallow on the branch, to see if that had any effect (no issues on this had been reported at the time of writing, so I was assuming this was a me issue). Once I unshallowed the branch, the error was replaced with messages like this
[Debug<PHONE_NUMBER>.595s] GitContentFileSystemProvider> Getting repository (file:///Users/thomas/src/foo) content for commit b9c0373d6fe5d64ddba74e9d7d7013bd4c394da5 and path /Users/thomas/src/foo/lib/foo/foo.py

But, still no way to add comments from the IDE.
If this helps in any way, I am able to see existing comments made by other users in the PR, they do show up in the IDE, and work as expected; I can comment back, resolve and unresolve from the IDE.

Okay, additional updates here, still no luck getting comments to work in a local repository, but I did try to add comments using GitHub Repositories, the remote extension, which did work!
Thinking I might have something bad in my source dir, I went through that extension to clone my repo to a new location, tried adding comments there, but the gutter is gone again!

So, I just tried completely removing vscode (including removing folders described here, re-installing from the universal zip provided by microsoft, I then did not sign in, I just installed the Github extension and opened a PR, still no way to add comments! I really have no idea what to try next, and being able to review code in my IDE has become a core part of my day...

So, to restate the point I am at now, the shortest path to reproing my issue is

Download VS Code
Install GitHub Pull Requests
Authenticate
Open a local repository
Checkout a pull request
Try to add a comment, but there is no white gutter line to even click on!

@thoward27 I can't reproduce the issue, so I'm wondering if there might be something different about the PR you're viewing. Is it a public PR and if so can you share a link?

Ok, thanks for helping to track this down. Your info above that already made comments do show is helpful. I'll add some more logging around the commenting ranges (the gutter you can click on to add comments), and we'll try to narrow it down from there.

Closing since we don't have logs. If you see the issue again please do ping the issue!


How many times can the login code be incorrect

This is up to the server.

This is up to the server.这取决于服务器。

Can you explain it specifically?


Alert via email

Hey, thank you for such great work!
Any possibilities you could add alternate alerts option like via email? (not webhook)
This could be very useful for someone (like-me) who want to run it through localhost, as some provider blocks port and need an extra effort to open it
Thank you!

Hi,
Keeping track of an email account is always a pain, at least in my past experience. For that reason I am not really interested in writing a bot for that. On top of that the delivery method is just not as smooth as a webhook. Webhooks execution is almost instant.
When running the bot of your local network you most likely have to open port 80, that is right. If port 80 is blocked by your ISP you may have to forward it to something like 8080.

"If port 80 is blocked by your ISP you may have to forward it to something like 8080."
Do u have any reference/link how do i do this?

Depends on your setup. If using Apache this guide might be helpful.


Remove duplicates from supported helper function list

The docs say not to edit the supported helper function list manually, please specify what can be done if they need to be edited.
For now, I have manually removed multiple duplicates that were in the supported helper functions list for each program type.
Mostly tracing programs had a lot of duplicates.

Oh, good catch. The reason for the "do not manually edit" note is because these sections are generated by a tool. It seems there is a bug in there somewhere. So we should fix it in the tool, then use it to regenerate the docs.

Ah okay, there is also an issue where it is missing some supported helper functions, not sure how widespread it is, but for e.g in BPF_PROG_TYPE_XDP the supported helper function bpf_tcp_raw_check_syncookie_ipv4 is mentioned twice, one instance should however be bpf_tcp_raw_gen_syncookie_ipv4

Closing this PR in favor of #80


Consistent use of punctuation and quick review in docs

I don't feel like this PR is creating a lot of value, but it isn't hurting anything either. I'm fine to either merge or close as the other maintainers see fit

@simonbrunel done!


How to reveal a bid?

I placed a bid on an ENS and was supposed to reveal my bid 15 minutes ago. Thing is… I have no idea how to do it and thought it would be somewhere in the interface.

Just go to https://www.myetherwallet.com/#ens and type in the name. If its ready to reveal, it will display the reveal interface for you.

Thank you. I think I just went there a bit early. Now it's working.

Great to hear! Let us know if you have any other issues or questions.


wirtualnemedia.pl

Match found in list.34.hosts.ubuntu101.co.za.domains:
wirtualnemedia.pl
probably has the word advertising so it got canned same as gratka.pl
Virtual Media - Polish information portal devoted to television, radio, press, internet, advertising, technology, public relations and marketing research.
The portal was founded on December 1, 2001. He is visited by over 500,000 people a month. users. The information published on the portal is published on the largest websites (including Onet.pl, Wirtualna Polska, Interia.pl) and newspapers (including "Rzeczpospolita", "Gazeta Wyborcza", "Dziennik", Fakt "," Super Express, "Press", "Newsweek") [2].
Currently, the editor-in-chief of the portal is Marcin Szumichora [3]

Also into shallalist.


Add activity period to roles

Individuals are listed under roles but there is no indicator as to when they began or ended their work.
It's be great to include a column along the lines of an "active period" to be transparent as well as to ensure that contributors are credited (as opposed to just disappearing or being lost in the commit logs).

Is this issue related to this commit somehow?
https://github.com/solid/process/commit/f780386be4e4ca9f9b0770ec750c4d96b72e4c16


Sample application, Please?

There is already an issue about this: https://github.com/wvteijlingen/Spine/issues/43. I'd like to do this someday, but I don't have the time right now.


replace moniitor by monitor

yes how to do that ?

You can either put a PR against https://github.com/apache/accumulo-website/blob/master/pages/people.md or we can put up that PR for you.  Thanks

done

@josselinchevalay merged in with https://github.com/apache/accumulo/commit/761b4eb7f377c114088b33c482d15310d4136665.  Please close this PR

nevermind, I closed it in another commit.  Thanks @josselinchevalay


VSR: Test format, Test EWAH

Break EWAH encode/decode test out into a fuzzer, to test more variations.

Encode more interesting buffers than simply uniform-random bits.

Break the journal format test into a fuzzer.

This is partly in preparation for being able to fuzz multiple configs (e.g. slot counts).
Previously this test did a huge allocation & then formatted the whole "zone" at once. Now it is more low-level, checking each chunk individually — the "zone" check is now handled by the (new) replica format test.

Extract replica.format() to a different file — it didn't share code with Replica so this is simple.

Add a test for the full replica format.

Gotta bump the node client version again


Drop error image and use error coloring on the anchor instead

Looks good - the System.err call seems like debug code, other than that feel free to merge


Try to tell self-host CI to use merge queue

Could be that because the runner only runs stuff on branches main, that it never gets to run the temporary merge queue branches.

oh you're right. didn't notice that, thought the merge queue was new.
There's something weird with bots then. all MRs done by humans were added to the merge queue fine. All MRs done by bots (https://github.com/randovania/mercury-engine-data-structures/pull/102, https://github.com/randovania/mercury-engine-data-structures/pull/100, https://github.com/randovania/mercury-engine-data-structures/pull/78, https://github.com/randovania/mercury-engine-data-structures/pull/72) all timed out in the merge queue due to CI not running, and had to be fixed by a human.

In ODR it works but it's just using a wildcard: https://github.com/randovania/open-dread-rando/blob/main/.github/workflows/python.yml

sounds good.
and if that still doesn't work, revert ig.


Changing the order of tracks does not work

Changing the order in the window "edit tracks" hast no effect.
Steps to reproduce:

open the edit tracks window
alter order of tracks using the arrows
hit confirm

I tried to reproduce this. In my browser the new position of the tracks after hitting confirm is at first correct. But as soon as I reload the browser window the positions snap back to their previous position.

I need feedback to work on this issue.
"Track management" works on a forest of (shallow) trees of tracks. When I select and reorder visible tracks in the "Track management" modal, what is expected to happen exactly?
In my tests only the selected, visible tracks are shown in the order I defined. This is certainly expected. But the selection of visible tracks and the position of the visible tracks in the track list  is not persisted. Is this the problem of this issue?
AFAIK there is currently no existing method to persist this visibility filter and positioning.

Reihenfolge der Spuren ändern.zip
See screencast for how the bug looks like. First part in Chrome, second in Firefox.

Could you add your browser versions to this issue? I cannot reproduce this in the latest FF/Chrome.

Chrome: Version 80.0.3987.87 (Offizieller Build) (64-Bit)
Firefox: 72.0.2 (64-Bit)
Beides auf Windows.

I tried this with Chrome Version 80.0.3987.100 (Official Build) (64-bit) on a Linux laptop, but there the re-ordering works like expected.
Presentation video - Annotation Tool - Track order.webm.zip

Perhaps @JulianKniephoff has access to a Windows computer?
BTW I am using the current "master" via "npm run start"

Bug also appears on Mac:

Chrome: Version 80.0.3987.100 (Offizieller Build) (64-Bit)
Safari: Version 13.0.5 (14608.5.12)

Observation: The order is always a chronological one: Older tracks are desplayed below.
Tested on SWITCHcast and SWITCHcast-Test

Could you please provide me with an URI (and credentials) of your local instance of the Annotation Tool? I cannot reproduce this error using the current master branch. Perhaps best via eMail

For the record. Information was provided internally. :wink:

@luniki re Windows machine: We have a Windows tablet here. Other than that I always use a VM when testing on Windows. You can get them for free from Microsoft for this purpose here.

Closed via #335


Missing config.files in webUI

Describe the bug
The Machinaris webUI is not showing the config files for alerts, farming, plotting with the latest Test-branch docker-release. Previous release it did that. Machinaris works with the great config as long as i don't press Save on the WebUI.
To Reproduce
Steps to reproduce the behavior, e.g.:

Run latest Test branch (from 16/7-21)
Open Machinaris config in Webui
See error

Expected behavior
Config files to show like previous versions.
System setup:

OS: UnRaid
Docker version number: 20.10.5
Machinaris branch: test
Machinaris version number: 0.5.1

Additional context & screenshots

D'oh. Sorry!  Thanks for the report.  This was caused by script re-orderings on pages when I added table pagination last night.
I've just patched this issue.  Also, included the disabling of Chiadog notifications for partial proofs that you suggested.
Both fixes are now available in latest :test image.  Pull it down and try it out.  Thanks again for the feedback.

Fixed with latest test release 🙂


Simplify code of Worker-side RPC handling

Remove unnecessary class hierarchy: e.g., DataServer, AbstractReadHandler,  ReadRequest, ReadRequestContext
Simplify calls AsyncCacheRequestManager

Codecov Report

Merging #13028 (3354963) into master (cbcc2dd) will decrease coverage by 25.44%.
The diff coverage is 3.59%.

@@              Coverage Diff              @@
##             master   #13028       +/-   ##
=============================================
- Coverage     42.27%   16.83%   -25.45%
+ Complexity     8515     2540     -5975
=============================================
  Files          1352     1348        -4
  Lines         77866    77371      -495
  Branches       9496     9393      -103
=============================================
- Hits          32920    13025    -19895
- Misses        42104    63188    +21084
+ Partials       2842     1158     -1684

Impacted Files
Coverage Δ
Complexity Δ

core/common/src/main/java/alluxio/AlluxioURI.java
23.07% <ø> (ø)
19.00 <0.00> (?)

...in/java/alluxio/collections/ConcurrentHashSet.java
60.00% <ø> (ø)
10.00 <0.00> (?)

...alluxio/collections/ConcurrentIdentityHashMap.java
5.81% <ø> (ø)
2.00 <0.00> (?)

...c/main/java/alluxio/collections/DelegatingSet.java
32.00% <ø> (ø)
5.00 <0.00> (?)

...java/alluxio/collections/DirectedAcyclicGraph.java
0.00% <ø> (ø)
0.00 <0.00> (?)

.../alluxio/collections/DirectedAcyclicGraphNode.java
0.00% <ø> (ø)
0.00 <0.00> (?)

...main/java/alluxio/collections/IndexDefinition.java
100.00% <ø> (ø)
2.00 <0.00> (?)

.../src/main/java/alluxio/collections/IndexedSet.java
53.52% <ø> (ø)
10.00 <0.00> (?)

.../java/alluxio/collections/NonUniqueFieldIndex.java
0.00% <ø> (ø)
0.00 <0.00> (?)

...common/src/main/java/alluxio/collections/Pair.java
31.81% <ø> (ø)
4.00 <0.00> (?)

... and 731 more

Continue to review full report at Codecov.

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

alluxio-bot, merge this please


[html] prevent that embedded grammars can corrupt syntax highlighting of rest of document

Currently, when writing embedded language, a lot of the times the embedded grammar can cause disruption to the rest of DOCUMENT:
This is html grammar.

Imagine editing css in a
   patterns:
   - include: source.css

"embeddedLanguages": {
  "source.css": "css"
}

I hope VSCode can only apply CSS grammar to the section between , so when I'm typing out my incomplete CSS VSCode would just re-tokenize and highlight until </style>, but not rest of the document.
/cc @alexandrudima
Also would like to hear @aeschli's opinion, as you are writing the html grammar.

At the moment I'm not sure if it's possible to modify the grammar to make this happen, but the whole tokenization relies on it. The grammar is really fragile, like even if you write a complete CSS style, right now we are still seeing the closing angle bracket  tag at the time it enters  and </script> tags.

@aeschli :+1:
TM grammars are parsed according to TM semantics.
TM has no notion of an embedded language, it simply has the notion of including rules from other scopes (from other files).
There are TM grammars split into multiple files that do not represent embedded languages (there is one I think for perl regular expressions or one for C platform functions).
Our only option to stay TM grammar compatible is to do what @aeschli suggests, where we have a special CSS grammar that expects it to be embedded inside HTML and has end rules for </style> everywhere. The alternative would be to fork TM parsing semantics, in which case I would do something entirely different...

That's what sublime have:
https://www.sublimetext.com/docs/3/syntax.html

As an alternative, is it possible for us to have such a "pop" rule?

What could be done is writing a HTML grammar that contains rules for embedded css and JavaScript, in particular the appropriate end rules for  and  tags.

Our only option to stay TM grammar compatible is to do what @aeschli suggests, where we have a special CSS grammar that expects it to be embedded inside HTML and has end rules for  everywhere.

It's possible to modify the CSS grammar to make it expects itself to be embedded. But I don't know any way to do that by only modifying HTML grammar now in VSCode.
And I believe this is a problem shared by embedded language support. I don't think it's reasonable to ask each language's grammar to expect itself to be embedded. For example in Vue's single file component, one can embed css/sass/scss/less/stylus/postcss. I hope there is a way to mark the end of embedded region in HTML, instead of adding a negative lookahead to each grammar rule in these 6 languages.

The problem bothers me too. It is so much easy to corrupt the syntax highlighting of the whole rest document when embedded language involves.

Markdown had a similar problem for fenced codeblocks. The solution was to switch from a begin +end rule to begin+while rule.
This case in HTML is a bit more complicated as you can also have single line style / script blocks. I believe these would have to be handled separately since a while rule would not work in that case

@mjbvz Thanks I'll give it a try.
BTW I think a better way to write TM grammar is to write in JSON: https://github.com/octref/vetur/blob/master/syntaxes/vue.YAML
Then use https://github.com/SublimeText/PackageDev to compile them to XML.
Just in case you get tired of editing XML.

Closing this issue as we don't want to diverge from TextMate.

Reopening to collect issues around this issue.

Tried the while + negative lookahead as @mjbvz suggested, but does not work.
Don't know if it's a bug in vscode-textmate, for example I got this:
(The whole


Rounded Corners for Acrylic (windows, tauri v1)

Hi!
Windows 11 23H2, Tauri v1, window-vibrancy v0.4.3
The app that I'm creating requires frameless windows. And as one might imagine, harsh, sharp, and squared corners hurts to look at (for me, at least).
Rounded Corners
I've seen a post about someone having a similar issue (previously/currently using this same plugin) and going for a more complicated solution. I'm quite new to Tauri and Rust, so going that route might not be an option. Here's the link to said post: how to make tauri app window have rounded corners with window vibrancy
Stopping Reversal of Effect
It seems that, when using multiple windows, the acrylic effect fades to a plain grayish color. This color does not change when I change the RGBA value as seen in Some() below:
#[cfg(target_os = "windows")]
apply_acrylic(&window, Some((255, 255, 255, 128)))
    .expect("Unsupported platform! 'apply_acrylic' is only supported on Windows");

The image below 'w/ Acrylic - inactive (shows RGBA)' is what it looks like. This occurs when the user focuses out/blurs from the window. So, clicking on another window or the background will lead to this effect. This doesn't really look that good for my tastes, so I'd like to be able to stop them from happening.
If ever helpful, here are some screenshots of the app =>
w/ Acrylic - active:

w/ Acrylic - inactive (shows RGBA):

w/out Acrylic - just plain old bg-color:rgba and border-radius:

Thank you, have a great day!

update!
reading through the closed issues... some answers my questions. particularly, the rounded corners.
this has led me to use window-shadows but it seems to remove the acrylic effect when used...

in order to get the rounded, you need to use window-shadows to bring back the shadow and rounded decorations.


PDF-generator needs a "page render completed" indicator

Description
The new PDF-generator currently being planned will be using puppeteer and chrome to convert an app-page to PDF. To do this as flexibly as possible, puppeteer needs a "hook" on the page(s) being rendered that indicate that the page is ready.
In puppeteer this is called the waitForSelector.
Ideally the PDF-generator should be able to wait for the same element regardless of page being rendered. There might already be such a DOM element, but the platform team will need help identifying what to use.
We would like to find such a DOM element on all pages instead of restricting what pages that can be used to create a PDF.
Additional Information
No response

Closing, as this has been tested OK by @SandGrainOne


Add documentation for docstring format

Also adapt docstrings in experiment file.

I was not sure about the doc-requirements, but I thought it would be useful to have them easily installable.

Can we have a check in the CI for the docstrings format?

I added the check to tox. The probably does not 100% enforce what I propose here, but catches a lot of other common errors.

Thanks!


ingest/ledgerbackend: Captive-Core fixes to support Stellar-Core 17.1.0

PR Checklist
PR Structure

[ ] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[ ] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[ ] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[ ] This PR adds tests for the most critical parts of the new functionality or fixes.
[ ] I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.

Release planning

[ ] I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.
[ ] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

What
Multiple fixes to support Captive-Core persistent storage in 17.1.0:

Switched from exec.CommandContext to exec.Command when starting Stellar-Core. This was done because CommandContext kills the process (Process.Kill()) without waiting for a graceful shutdown. This can corrupt minimal DB or buckets. We send signal.Interrupt right now so Stellar-Core can exit gracefully. There's one gotcha: signal.Interrupt is not supported in Windows so we kill the process and empty storage folder that can contain corrupted data.
Removed DISABLE_XDR_FSYNC setting in stellar-core.cfg. This can corrupt buckets when Stellar-Core is killed.
Changed the behaviour of CaptiveStellarCore.nextLedger. Previously it was set to a value calculated using CaptiveStellarCore.runFromParams however these calculations are no longer correct when Stellar-Core is restarted with persistent storage. To prevent some Stellar-Core version checks we now set CaptiveStellarCore.nextLedger after the first ledger is streamed.
Reverted the code creating and removing storage directory on Windows.

Why
Stellar-Core 17.1.0 now persists the minimal DB and buckets between executions. It allows faster catchup on restart.
Known limitations
[TODO or N/A]

... without waiting for a graceful shutdown. This can corrupt ...

Isn't that an issue if it gets OOM-killed, or powered-off too?

Isn't that an issue if it gets OOM-killed, or powered-off too?

Correct but I believe there's nothing we can other than, maybe, creating a lock file as Stellar-Core does. But it will still not help with data corruption. In such case storage dir need to be removed manually.


Custom analog error rate

Add the ability to set a custom circularity error rate % for analog sticks.

After saving with the value 9, getAddonsOptions returns

Meaning it wont match any of the options and show the error:


exclude samples folder for storage setup

Can one of the admins verify this patch?

I don't think this is necessary as there's no __init__.py file in the samples directory.


Adding custom cursor modifier support

Overview
Issue in existing cusor system:
Cursor class uses CursorModifier in the following two methods:

OnActiveModifier(CursorModifier modifier)
OnPointerSpecificFocusChanged(IPointingSource pointer, GameObject oldFocusedObject, GameObject newFocusedObject)

because of which, if anyone writes their own cursor modifier(implementing ICursorModifier), their cursor modifier code will not be called/executed as OnPointerSpecificFocusChanged will not be able to get the custom cursor modifier component as it is not of the same type as expected by the Cursor class.
Solution:

Changed OnActiveModifier(ICursorModifier modifier) signature to use ICursorModifier as the input parameter instead of CursorModifier
Changed OnPointerSpecificFocusChanged default implementation to use ICursorModifier instead of CursorModifier

Implication:
All classes that derive from Cursor abstract class will need to change OnActiveModifier method parameter type
Diagram images of the existing system and proposed changes to the system are attached.
Current Cursor System:

Proposed changes to cursor system:

P.S.: Edited the images with MS Paint. Please don't judge. :D
We were not able to generate the class diagram using VS 2017 Professional. Any help on this will be appreciated.
Changes

Modified Cursor.cs to use ICursorModifier instead of CursorModifier
Modified AnimatedCursor.cs
Added CustomCursorModifierExample scene
Added CubeCursor prefab
Added TestCursor.cs
Added TestCursorModifier.cs

@StephenHodgson Brought back the old method and marked it obsolete.
Regarding the test scripts and example scene, MRTK does not have any example of a custom cursor modifier which is why I created the scene. It has three game objects, one without any modifier, one with CursorModifier and one with a custom cursor modifier(TestCursorModifier).
Being a consumer of MRTK, I myself faced some issues while implementing my own cursor related functionality. I think the example scene will be helpful for some people.

the july (june18_dev) branch is in stabilization, re-targeting this PR to the htk_development branch

@StephenHodgson Updated TestCursorModifier to not throw NotImplementedExceptions.

Can we get an update on this @keveleigh / @StephenHodgson as it's getting stale.

Closing issues older than 180 days. If this is still an issue, please reactivate with recent information.


Sorry! It was in agreement with this issue that such packages are silly, than with disagreement or anything. Anyway removed to remove confusion, haha.

So to be clear one cannot currently have straight.el fully manage org?

@sooheon No, it works just fine. You'll just get some warnings about the Org version not being defined, unless you add some hacks.

Can confirm it works just fine. I don't think I get any version warnings (?) but that hack is cool anyway.

One package that doesn't work at all without a build step is proof-general. It's quite an important package as well so it would be nice to have support.

@rgrinberg the same may be true of pdf-tools

also structured-haskell-mode

Indeed. You can probably get a pretty good idea of the list of such packages by just searching all the el-get recipes, since those specify build commands.
Are those packages not in MELPA? Because as I understand it, MELPA does not support build commands.
In any case, I am quite busy at the moment, but would gladly merge any pull requests that came along.

@raxod502 this is pretty late but I think MELPA does seem to support build commands, see here:
https://github.com/melpa/melpa/blob/269acf093c3aa508479bf532a4e07c9c6d568c72/recipes/pdf-tools#L1
I believe pdf-tools gets compiled at package-install time.

@dieggsy MELPA doesn't build pdf-tools. What you see in the recipe is just a specification to create a build/ directory in the built package and to link the named files into it:
drwxr-xr-x     - raxod502  2 Dec  7:29  .
drwxr-xr-x     - raxod502  2 Dec  7:29  ├── build
lrwxr-xr-x    58 raxod502  2 Dec  7:29  │  ├── Makefile -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/Makefile
drwxr-xr-x     - raxod502  2 Dec  7:29  │  └── server
lrwxr-xr-x    67 raxod502  2 Dec  7:29  │     ├── .gitignore -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/.gitignore
lrwxr-xr-x    63 raxod502  2 Dec  7:29  │     ├── ar-lib -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/ar-lib
lrwxr-xr-x    67 raxod502  2 Dec  7:29  │     ├── autogen.sh -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/autogen.sh
lrwxr-xr-x    64 raxod502  2 Dec  7:29  │     ├── compile -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/compile
lrwxr-xr-x    69 raxod502  2 Dec  7:29  │     ├── configure.ac -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/configure.ac
lrwxr-xr-x    67 raxod502  2 Dec  7:29  │     ├── epdfinfo.c -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/epdfinfo.c
lrwxr-xr-x    67 raxod502  2 Dec  7:29  │     ├── epdfinfo.h -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/epdfinfo.h
lrwxr-xr-x    68 raxod502  2 Dec  7:29  │     ├── Makefile.am -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/Makefile.am
lrwxr-xr-x    72 raxod502  2 Dec  7:29  │     ├── poppler-hack.cc -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/poppler-hack.cc
lrwxr-xr-x    73 raxod502  2 Dec  7:29  │     ├── poppler-versions -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/poppler-versions
lrwxr-xr-x    73 raxod502  2 Dec  7:29  │     ├── synctex_parser.c -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/synctex_parser.c
lrwxr-xr-x    73 raxod502  2 Dec  7:29  │     ├── synctex_parser.h -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/synctex_parser.h
lrwxr-xr-x    79 raxod502  2 Dec  7:29  │     ├── synctex_parser_local.h -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/synctex_parser_local.h
lrwxr-xr-x    82 raxod502  2 Dec  7:29  │     ├── synctex_parser_readme.txt -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/synctex_parser_readme.txt
lrwxr-xr-x    79 raxod502  2 Dec  7:29  │     ├── synctex_parser_utils.c -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/synctex_parser_utils.c
lrwxr-xr-x    79 raxod502  2 Dec  7:29  │     ├── synctex_parser_utils.h -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/synctex_parser_utils.h
lrwxr-xr-x    83 raxod502  2 Dec  7:29  │     └── synctex_parser_version.txt -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/server/synctex_parser_version.txt
lrwxr-xr-x    67 raxod502  2 Dec  7:29  ├── pdf-annot.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-annot.el
.rw-r--r--   59k raxod502  2 Dec  7:29  ├── pdf-annot.elc
lrwxr-xr-x    67 raxod502  2 Dec  7:29  ├── pdf-cache.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-cache.el
.rw-r--r--   15k raxod502  2 Dec  7:29  ├── pdf-cache.elc
lrwxr-xr-x    65 raxod502  2 Dec  7:29  ├── pdf-dev.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-dev.el
.rw-r--r--  3.1k raxod502  2 Dec  7:29  ├── pdf-dev.elc
lrwxr-xr-x    69 raxod502  2 Dec  7:29  ├── pdf-history.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-history.el
.rw-r--r--  5.4k raxod502  2 Dec  7:29  ├── pdf-history.elc
lrwxr-xr-x    66 raxod502  2 Dec  7:29  ├── pdf-info.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-info.el
.rw-r--r--   48k raxod502  2 Dec  7:29  ├── pdf-info.elc
lrwxr-xr-x    69 raxod502  2 Dec  7:29  ├── pdf-isearch.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-isearch.el
.rw-r--r--   24k raxod502  2 Dec  7:29  ├── pdf-isearch.elc
lrwxr-xr-x    67 raxod502  2 Dec  7:29  ├── pdf-links.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-links.el
.rw-r--r--   11k raxod502  2 Dec  7:29  ├── pdf-links.elc
lrwxr-xr-x    66 raxod502  2 Dec  7:29  ├── pdf-misc.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-misc.el
.rw-r--r--   13k raxod502  2 Dec  7:29  ├── pdf-misc.elc
lrwxr-xr-x    67 raxod502  2 Dec  7:29  ├── pdf-occur.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-occur.el
.rw-r--r--   29k raxod502  2 Dec  7:29  ├── pdf-occur.elc
lrwxr-xr-x    69 raxod502  2 Dec  7:29  ├── pdf-outline.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-outline.el
.rw-r--r--   21k raxod502  2 Dec  7:29  ├── pdf-outline.elc
lrwxr-xr-x    66 raxod502  2 Dec  7:29  ├── pdf-sync.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-sync.el
.rw-r--r--   24k raxod502  2 Dec  7:29  ├── pdf-sync.elc
.rw-r--r--   12k raxod502  2 Dec  7:29  ├── pdf-tools-autoloads.el
lrwxr-xr-x    67 raxod502  2 Dec  7:29  ├── pdf-tools.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-tools.el
.rw-r--r--   10k raxod502  2 Dec  7:29  ├── pdf-tools.elc
lrwxr-xr-x    66 raxod502  2 Dec  7:29  ├── pdf-util.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-util.el
.rw-r--r--   36k raxod502  2 Dec  7:29  ├── pdf-util.elc
lrwxr-xr-x    66 raxod502  2 Dec  7:29  ├── pdf-view.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-view.el
.rw-r--r--   51k raxod502  2 Dec  7:29  ├── pdf-view.elc
lrwxr-xr-x    69 raxod502  2 Dec  7:29  ├── pdf-virtual.el -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/lisp/pdf-virtual.el
.rw-r--r--   82k raxod502  2 Dec  7:29  ├── pdf-virtual.elc
lrwxr-xr-x    56 raxod502  2 Dec  7:29  └── README -> /Users/raxod502/.emacs.d/straight/repos/pdf-tools/README

So, you are correct in that any compilation happens on the client—which means it's orthogonal to straight.el, whose build step is analogous to what happens on the MELPA server.
The issue is how to handle packages which need to be built but, unlike pdf-tools, do not themselves handle it automatically.

is there any PR related to this issue? I was toying with https://github.com/ubolonton/emacs-tree-sitter and this feature would come handy

No, there's no implementation, although you could easily hack something together using straight-use-package-pre-build-functions. See https://github.com/raxod502/straight.el/issues/389.
Personally, I think this is not something that should be taken care of by the package manager. Rather, each package that has custom build steps should offer a facility for running them (automatically, perhaps) when needed. That way, each package can decide for itself what needs to be run and when, reducing complexity in the package manager and also reducing the amount of time that users may need to wait for spurious rebuilds to complete. The problem of code duplication could be solved by a shared dependency that takes care of all the necessary user interface code, making the functionality only take a few lines of code to add to any package.

Not sure if it's related to this issue. While magit.info is built in ~/.emacs.d/straight/build/magit, the Info file for the package org-plus-contrib is not built in ~/.emacs.d/straight/build/org-plus-contrib.

That's because Org, unlike Magit, does not provide its Texinfo manual in any kind of standard format, hence it's impossible for straight.el to identify and build it without a contribution such as #549 + #535.

Just notice another package that cannot be built without supporting arbitrary build commands.

merged #535 into develop. That should take care of this issue.

Indeed! Wonderful!

Is this the most requested feature in straight.el to date?

Is this the most requested feature in straight.el to date?

you bet


Dev / Prod database, publishing forms, and versioning

Allows for connecting data to immutable forms, publishing forms from dev to prod makes a copy and editing forms on prod will no longer be possible.

If DB switching (#357) seems unreasonable to implement, then isolating studies (#358) can help achieve the goal of having separate prod and test environments without requiring duplication and synchronization of multiple databases. One study can be used exclusively for testing and another for collecting production data.
Study isolation only solves part of the current issue with developing and testing forms. To fully deal with existing form issues we need to implement form versioning. This approach should also include a feature to make it trivial to copy forms across studies.


Update alleycats-core, cats-core to 2.3.1

Updates

org.typelevel:alleycats-core
org.typelevel:cats-core

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

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel" } ]

Applied Migrations

github:typelevel/cats/Cats_v2_2_0?sha=v2.2.0

Documentation:

https://github.com/typelevel/cats/blob/v2.2.0/scalafix/README.md#migration-to-cats-v220

labels: library-update, semver-minor, scalafix-migrations

Superseded by #89.


[feature request] Add support for specifying trusted certificates

It can be difficult to configure Relay to communicate with an InfluxDB server that is using a self-signed SSL certificate that is not trusted by the host system. It would be great if there was a configuration option for specifying a set of trusted certificates to use for communication.

Why does this need to be specific to influxdb-relay? Can't a trusted certificate be added to the system as a whole?

@nathanielc Sometimes you want system-specific certificates that aren't trusted globally on the machine. Adding a new CA to the host machine would add an extra attack surface: If the CA used to sign the cert for the backends is compromised, it will only compromise the relay traffic, rather than potentially trusting that CA for any secure connection or authentication on the machine.

@joelegasse Makes sense, thanks.

@rossmcdonald Would adding this as a per-backend option ca-cert be sufficient?

@joelegasse Absolutely, I think that makes perfect sense.

Will this influx-relay would be helpful if I have only 1 influxdb server ?
It doesn't seem so that it works ,
luvpreet@DHARI-Inspiron-3542:/etc$ curl -i -XPOST 'http://localhost:9096/write?db=tester' --data-binary 'glass,host=server01,region=us-west value=0.64<PHONE_NUMBER>000000000'
HTTP/1.1 503 Service Unavailable
Content-Length: 35
Content-Type: application/json
Date: Mon, 17 Apr 2017 12:48:33 GMT
{"error":"unable to write points"}


TinyCoreLinux .tcz package ready for Boot2Docker

Could micro be ported to a tinycorelinux package so that we can use it in Boot2Docker?

Does micro not run on tinycorelinux already just using a prebuilt binary? How would I go about packaging/porting micro for tinycorelinux?

Please forget about this. I will try to do it myself.


Not load swagger ui (kill chrome browser).

I faced with issue that my api swagger UI stack and won't load. I tried latest and old swaggeer with provided json - all same result. So probably issue somewhere around these json.
Here some additional info:
Swagger json
https://gist.github.com/laskoviymishka/4d85bf74d12019049a192979c880809c
Swagger setup
services.AddSwaggerGen(c =>
            {
                c.DocInclusionPredicate((path, description) => description.RelativePath.Contains("api/v1"));
                c.DescribeAllEnumsAsStrings();
                c.DescribeStringEnumsInCamelCase();
                c.TagActionsBy(t => ((ControllerActionDescriptor)t.ActionDescriptor).ControllerName);
                c.SwaggerDoc("v1", new Info { Title = "Buscom API", Version = "v1" });
            });

Swagger config
            app.UseSwagger();
            app.UseSwaggerUI(c => { c.SwaggerEndpoint("/swagger/v1/swagger.json", "Buscom API"); });

Dupe of https://github.com/domaindrivendev/Swashbuckle.AspNetCore/issues/287


(Feature request) multiple users

I love the project, I use it almost daily. Would be great to have a non-admin user that can have varying levels of privileges.

Guest access is enough for what I need. Thanks!

Actually, I thought I could upload in guest mode. I would need the guest or a second user to be able to upload.