Refactor Payments API to Stripe Intents in favor of Stripe Charges

What kind of a pull request is this?

QA / Code Review

Code Checklist

[x] The code follows dotkom code style
[x] The code passes the defined tests
[x] I have added tests for the code I added
[ ] I have provided documentation for the code I added
[x] The code is ready to be merged

(Possible) Breaking Changes

[x] The changes are backwards compatible

Description of changes
The Stripe API we use is deprecated in favor of the Stripe Intent API in Europe because of SCA #2240
This rewrites the rewritten API to work with that API instead.

Tests are failing because Stripe keys are not present in the test env. Will probably handle this in the PR this is merging into.


Player Names Not Showing Up

Describe the bug
After analyzing demo files, it still just shows "Player 1" "Player 2" etc.

In the past it showed the actual player names.
Demo links
No response
Steps to reproduce

Launch the application
Go to DEM section
Double click on an analyzed demo
You will see just "Player X" instead of their names.

Expected behavior
I would expect to see the actual player names but instead see a generic Player name.
How often does this bug happen?
None
Log file
csdm.log
Environment information
Version: 3.0.7
OS: win32 x64 10.0.19045
Electron: 28.0.0
Chrome: 120.0.6099.56
Last database migrations:
v1 - 2023-12-04T03:19:31.924Z
Additional context
No response

I added a doc about this potential issue here - let me know if it needs clarification.
As an improvement, the next version will have more API keys and will not request the Steam API every time you go to the demo's details page of a Valve demo (The app already tries to reduce API calls).
I would still recommend generating your Steam API key to avoid this issue.


Dcline modeling

Added Dc line support for two types of models and consistent Abstract hierarchy.
Also improved the testing code in general. Closes #52

Codecov Report

Merging #69 into master will decrease coverage by 0.34%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #69      +/-   ##
==========================================
- Coverage   94.32%   93.98%   -0.35%
==========================================
  Files          16       15       -1
  Lines         194      183      -11
==========================================
- Hits          183      172      -11
  Misses         11       11

Impacted Files
Coverage Δ

src/models/branches/lines.jl
100% <0%> (ø)
:arrow_up:

src/models/generation/thermal_generation.jl
100% <0%> (ø)
:arrow_up:

src/models/generation/hydro_generation.jl
100% <0%> (ø)
:arrow_up:

src/models/branches/transformers.jl
100% <0%> (ø)
:arrow_up:

src/models/storage/batteries.jl
100% <0%> (ø)
:arrow_up:

src/models/generation/renewable_generation.jl
100% <0%> (ø)
:arrow_up:

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 04570b8...7ea0be9. Read the comment docs.

Why are you using try ... finally ... end in tests?

So it is possible to test each individual test independently and get a report at the end of which in particular failed. Check the whole test code, I updated several parts

Instead of using try finally, have you tried just wrapping your imports in another @testset block?  This is how I accomplish this in PowerModels.

@ccoffrin What I am trying to do here is to create a @testset for all the constructors. With this syntax, each constructor is treated as an individual test such that we run the test we can independently know how many constructors work and how many don't.
https://github.com/NREL/PowerSystems.jl/blob/c5e6d234c60457a736901d42ecee1e3f01bef25f/test/runtests.jl#L7-L17
The first test set targets loading the *.jl files and the second targets each constructor individually.
https://github.com/NREL/PowerSystems.jl/blob/master/test/constructors.jl


Unexpected token: ';'

Seems to work correctly, but shows an error in the console:
<style>
  div[class*="status-"]::after {
    content: "";
    display: block;
    position: absolute;
    width: 100%;
    height: 100%;
    background-repeat:  no-repeat;
    background-position: bottom center;
    background-size: contain;
    opacity: 0.1;
  }
  .status-400::after {
    background-image: url('/assets/images/400.svg');
  }
  .status-401::after {
    background-image: url('/assets/images/401.svg');
  }
  .status-403::after {
    background-image: url('/assets/images/403.svg');
  }
  .status-404::after {
    background-image: url('/assets/images/404.svg');
  }
  .status-500::after {
    background-image: url('/assets/images/500.svg');
  }
</style>

can you share what version of node do you test? I use 14.11.0 - everything is ok (screen below).

hey, can you comment this?)

@inikonorov I'm trying to reproduce this again, but without much luck :) going to try again now.

@inikonorov ok, I've found it. I've added a skipped spec here https://github.com/buxlabs/boxwood/commit/c1e570d4cb8105f517cee57f3c442dc2b9156231 if you want to have a look :) thanks!

I play with code and found something
I think, that problem is if-condition (35-37 rows) in prerun function in plugins/DataPlugin.js
I made some tests:

1 test (current if-condition and template from c1e570d commit

2 test (current if-condition and my template based on template from 1st test

3 test (changed if-condition and template from 1st test)

I think, that when optimizeNode function finds curly brackets in style tag, she thinks that in curly brackets there is some JS code. So 2nd test works correctly, because in curly brackets there is a real JS code.
I don't know is 3rd test's if-condition right and I can do pull request with this solution, so I wait your opinion about this :)

@inikonorov this makes a lot of sense, good find! This seems to be a wider problem, I think same issue would happen if we would have a script tag defined with something inside of it (or any other tag that can take in code).
I think the right solution for this, is to do something like this inside of the DataPlugin
const CODE_TAGS = ['style', 'script']

// ...

if (CODE_TAGS.includes(tag)) {
   fragment.children.forEach(node => {
     node.skipDataOptimization = true
   })
}

// ...

if (this.variables.length > 0 && !fragment.skipDataOptimization) {
  // ...
}

okay, 'll do this today :)

https://github.com/buxlabs/boxwood/pull/667


[Failing Test]: Access to the PUBSUB unit test error

What happened?
My scene is to access PUBSUB as data source
pipeline.apply("readpubsub", PubsubIO.readMessageWithMessageId().fromSubscription(sriptionid))...
Just as the unit test case is written, it is also injected into the Pubsubmessage object, but an error is reported
junit test code:
PubsubMessage pubsubMessage = Mockito.mock(PubsubMessage.class); .... PCollection<String> out = pipeline.apply("input", Create.of(pubsubMessage)).apply(....)
error: Unable to infer a coder and no Coder was specified.
I want to know how to set the coder about how to set the custom object pipeline
Issue Failure
Failure: Test is flaky
Issue Priority
Priority: 3
Issue Component
Component: beam-community

Maybe I don't need to mock the pubsubMessage object, but there is a new bug, I found that the messageId will be lost during the corresponding processing, even though I have initialized the messageId, it is still null

Can you provide more information about which coder failed to be inferred? From what you have provided, I cannot guess at the problem.


[WIP] Finally remove cols from chargeback_rate_detail

What
Part of refactoring: #13375.
Before we drop cols in chargeback_rate_detail, we should

stop using them
and stop setting them in specs

@miq-bot add_label chargeback, technical debt, euwe/no
@miq-bot assign @gtanzillo

@miq-bot remove_label wip


py3.13

[x] >
Add the 'w' type code (Py_UCS4) for Unicode characters. It should be used instead of the deprecated 'u'
Register array.array as a MutableSequence by implementing the clear() method. (Contributed by Mike Zimin in gh-114894.)

https://docs.python.org/3/whatsnew/3.13.html#array

[x] math.fma is added in 3.13

[x] https://docs.python.org/3/whatsnew/3.13.html#other-language-changes  doc string will be deindented

features above are all implemented since https://github.com/nimpylib/pylib/commit/bdfa2711cba634170cde90f98038b95bb497a5d3


LUCENE-8930: script testing in the distribution

The patch works well for me (I ran it only on *nix machine). There would not be much I can do or want to do about it. Could you please merge it to the upstream when you have some time.

The test failure cannot be reproduced for me.
https://github.com/apache/lucene/runs/4606721258?check_suite_focus=true
gradlew :lucene:distribution.tests:test --tests "org.apache.lucene.distribution.TestScripts.testLukeCanBeLaunched" -Ptests.jvms=1 -Ptests.jvmargs=-XX:TieredStopAtLevel=1 -Ptests.seed=EC28381DD2E5610 -Ptests.slow=false -Ptests.file.encoding=US-ASCII

I'm not sure what it is but I'm ears deep into rewriting these path-related things - there are bugs and quirks there that I'm trying to overcome. Once I finalize that, I'll return to this issue.

Thanks for your quick response as always. Sorry, I just tend to add uncoordinated memos in pull requests but they are not questions that need responses.

It seems that this can be reproduced on the Github Actions container. As a test, let me revert the recently merged change...

It looks like the failure is not related to https://github.com/dweiss/lucene/pull/15. I will revert the revert commit; sorry for the noise again.

I thought something strange was happening on the Actions, but after merging the main branch (I did that to fetch https://github.com/apache/lucene/commit/a94fbb79ac6e60c1ebfa76b24cab23fabcb60bbf), the failure started to be reproduced on my local machine.
org.apache.lucene.distribution.TestScripts > test suite's output saved to /mnt/hdd/repo/lucene/lucene/distribution.tests/build/test-results/test/outputs/OUTPUT-org.apache.lucene.distribution.TestScripts.txt, copied below:
  1> --- [forked subprocess output: /usr/bin/bash] ---
  1> Picked up _JAVA_OPTIONS: -Duser.language=en
  1> Error occurred during initialization of boot layer
  1> java.lang.module.FindException: Module randomizedtesting.runner not found, required by org.apache.lucene.test_framework
  1>
  1> --- [end of subprocess output] ---
   >     org.junit.ComparisonFailure: [forked process exit status] expected:<[0]> but was:<[1]>

This means module resolution picks up all the modules, not just those requested and fails there because it can't find dependencies of the test framework... If this indeed is the case then we may have to move the test framework back to its separate folder.

Besides the test failure, Luke fails to start on the latest main as I speculated.
lucene $ tar xzf lucene/distribution/build/packages/lucene-10.0.0-SNAPSHOT
lucene-10.0.0-SNAPSHOT-itests/  lucene-10.0.0-SNAPSHOT-src.tgz  lucene-10.0.0-SNAPSHOT.tgz
lucene $ tar xzf lucene/distribution/build/packages/lucene-10.0.0-SNAPSHOT.tgz -C /tmp/
lucene $ /tmp/lucene-10.0.0-SNAPSHOT/bin/luke.sh
Picked up _JAVA_OPTIONS: -Duser.language=en
Error occurred during initialization of boot layer
java.lang.module.FindException: Module randomizedtesting.runner not found, required by org.apache.lucene.test_framework

Well, this confirms the test is working... ;) I didn't realize the resolution is eager for all modules on module path - I thought it'd only include the actual graph of included modules. I'll have to revert the change that puts the test framework in the same folder as the rest of the modules.

I think the resolution may be actually lazy but the test framework provides services consumed by lucene-core - that's why the resolver tries to load the test framework module (and fails). Otherwise we'd hit the same problem earlier with, for example, org.apache.lucene.spatial_extras which requires modules not present anywhere in the distribution.

If you'd like to provide a minor patch reverting just this distribution-assembly bit, @mocobeta , it'd be great (the tests in distribution.tests would have to be updated too).

Thanks.
The problem is now clear to me. I will try to look at this tomorrow (or today; it's 5 am in my timezone).

bq. 5 am in my timezone
Nobody should not be awake at this ungodly hour.

Yes - Luke (or an example application that depends on Lucene) successfully started by just removing the test-framework module from the module path.
lucene $ ./gradlew assembleRelease
lucene $ tar xzf lucene/distribution/build/packages/lucene-10.0.0-SNAPSHOT.tgz -C /tmp/

lucene $ /tmp/lucene-10.0.0-SNAPSHOT/bin/luke.sh
Error occurred during initialization of boot layer
java.lang.module.FindException: Module randomizedtesting.runner not found, required by org.apache.lucene.test_framework

lucene $ rm /tmp/lucene-10.0.0-SNAPSHOT/modules/lucene-test-framework-10.0.0-SNAPSHOT.jar
lucene $ /tmp/lucene-10.0.0-SNAPSHOT/bin/luke.sh
# successfully launched

I understand this behaviour would be correct from the perspective of the module system and its internal mechanism to consume service providers in the module path. Meanwhile, it makes applications fragile (just placing one jar in the module directory breaks them). This might be documented somewhere in the specification though, it hardly seems to be very safe to me... am I missing something?

I still cannot convince myself it is the best or only one solution for that, but maybe I'd need to recognize the strict dependency management of jms as a necessary thing for embracing it.

It is more strict indeed and it is eager (no way to just "skip" the JARs that are not in fact used - the linked graph has to be complete). I don't have any opinions on the subject of what's good or bad - this is exactly what I wrote on the original issue that brought the module system support - it's an exploration for me as well (and as it turns out, many things you're familiar with or accustomed to just don't work).

I started to feel that we may need to check if the "runtime" dependency graph in the binary distribution is complete (or, does not lack any node). While it can be seen as a collection of artifacts (jars), it also has an aspect of an application - currently, it provides only Luke though.

Could I merge the main into this branch to fetch https://github.com/apache/lucene/commit/54ebf3c73b72bafc414f834a15b8a3e81fd75ad8 just to see how Github Actions behave? There is a conflict and I'll be able to resolve it.

Please, feel free to do anything you like, @mocobeta ! Like I said, I just left it as an example.

Hi, I just wanted to know if there is anything that blocks this to merge or this is going to be abandoned. I should have created a forked branch and made possible refinements, but I found this works well as is and there wouldn't be much I can do to improve this. I think having this test will be vital not to repeat RC respins in future releases... (as long as Luke is a part of the binary distribution)

Hi @mocobeta . Please feel free to commit this in. Maybe change the strings used to verify assertions? They're... well, frivolous. ;)

Thanks.

Maybe change the strings used to verify assertions?

I'm fine with it as is and there would be no harm in having a little joke for internal use, or rather I can't figure out which line is your concern...

Fine then, commit it in!

Merged. Many thanks, @dweiss!


Changed lock mechanism

closes #43

@yegor256 take a look, please

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 2min)


Bot does not retry accepting offers from owner

24-10-2018 02:23:16 - info: Offer #3345850737 received from<PHONE_NUMBER>0822150
24-10-2018 02:23:16 - info: Offer #3345850737 is from an owner, accepting
24-10-2018 02:23:16 - info: Message sent to M_SERVER ✅ trade.tf<PHONE_NUMBER>4727567): Offer from owner, accepting
24-10-2018 02:23:17 - warn: Offer #3345850737 could not be accepted: Not Logged In
Of course would be great if bot could accept every offer, but if we have this bug, please, make bot retry to accept the offer after he refresh the session. Thanks

#98


feat: value transfer in execute

Feature Request
Describe the Feature Request
Implement the value transfer associated in a transaction in the execute function.
Describe Preferred Solution
Related Code
Additional Context
If the feature request is approved, would you be willing to submit a PR?
(Help can be provided if you need assistance submitting a PR)

[ ] Yes
[ ] No

Closed by #506


docs, skip ITs on deploy

PR-Codex overview
This PR focuses on updating the Maven command in the .rultor.yml file and modifying the code in the README.md file to include a new parameter in the Preload constructor.
Detailed summary

Updated Maven command in .rultor.yml to include the -DskipITs flag.
Modified code in README.md to include a new parameter in the Preload constructor.

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@h1alexbel thank you for your Pull Request. I'll assign someone to review it soon.
If this PR solves a todo from the code, please don't forget to remove it.

@rultor merge

@rultor merge

@h1alexbel OK, I'll try to merge now. You can check the progress of the merge here

@zoeself derigester

@zoeself derigester

@h1alexbel didn't understand that, sorry.

@zoeself deregister

@zoeself deregister

@h1alexbel ok, I've removed this task from scope. I'm not managing it anymore.

@rultor merge

@h1alexbel Done! FYI, the full log is here (took me 3min)


Use flot's pie chart in flot renderer

The flot renderer currently uses nvd3 for rendering pie/donut charts. Flot is perfectly capable of rendering pie & donut charts on its own though - update the flot renderer to actually use flot for this chart type. Then we could avoid loading nvd3 when we don't need it.
(This also goes towards my desire to remove the nvd3 renderer from the standard build, and move it to the unsupported extensions directory).

Yes!  Perhaps satisfy this by figuring out how to support flot's plugins.  Their automarkings plugin is also on my radar.  Agreed that nvd3 can be moved to unsupported extensions.  It's so slow that I can't even use it.


Enable safety checks

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

Comparison is base (b5352d8) 100.00% compared to head (0939648) 100.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff            @@
##              main      #134   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           18        18
  Lines          496       496
  Branches        75        75
=========================================
  Hits           496       496

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


shim-sev: handle SEV encryption

Two larger concerns:
1. The amount of asm has grown significantly. We now have a megafunction written in assembly that is very hard to follow. Can this be broken up?

2. I thought we agreed on making the C-bit a constant with an assert if it changes.

IMHO, nothing before  call    _dyn_reloc can be made into rust safely
wasn't that big of a deal and a hardcoded version wouldn't change anything

1. The amount of asm has grown significantly. We now have a megafunction written in assembly that is very hard to follow. Can this be broken up?

the sgx start.S has an equal amount of lines


Create CropTopTransformation.java

Same as CropTransformation but the bottom of the image is cropped and the top part is preserved.

@veresvit
Hi. versvit.
Good idea.
but, I think I want to add to CropTransformations.
define the Top and Bottom to enum.

@wasabeef Good idea. Originally I didn't want to interfere with your code.

@wasabeef I implemented the crop type with the enum. Check out the updated branch, please. :)

@veresvit
Good Job
I will release on the weekend. :+1:

@veresvit
1.0.3 has been released.

Fast work @wasabeef ! :+1:


Extract libjxl into its own Android Library component

Fixes #3

Thanks you for your contribution ! Everything seems good so I'm merging it.


HLS stream would panic

Songbird version: 0.4.3
Rust version (rustc -V): rustc 1.81.0 (eeb90cda1 2024-09-04)
Description:
The program panicked in rusty pool thread when using HLSRequest
thread 'rusty_pool_1_thread_1' panicked at /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/stream_lib-0.5.2/src/hls/mod.rs:99:9:
there is no reactor running, must be called from the context of a Tokio 1.x runtime

Steps to reproduce:
let input = HlsRequest::new(...).into();
driver.play_only_input(input);

I guess its because stream_lib::download_hls tries to spawn a task, maybe should make HlsRequest create async instead?

I think this is more of a documentation issue as making a function async means something specific which is not the case here.

@Erk- In this discussion, you mentioned that DownloadStream does not need async to be created. While this might be true, from my understanding, mixer uses create and create_async in the Compose trait to determine if an Input should live on a tokio executor or a thread pool.
However, you spawned a tokio task to download HLS chunks while the HLS Input will always run without tokio runtime/context. This will fail 100% of the time if we don't wrap it with another input type and implement create_async or by spawning the tasks directly using Runtime handler.
In conclusion, there are two possible solutions:

Patch all tokio::spawn or tokio::task::spawn with Handle::current().spawn()  in stream_lib and update the crate version in songbird
Create the stream in create_async even though the creation itself doesn't require async

In conclusion, there are two possible solutions:

Patch all tokio::spawn or tokio::task::spawn with Handle::current().spawn()  in stream_lib and update the crate version in songbird

I don't believe this would make a difference as Handle::current() panics^1 if called outside of an executor just like tokio::spawn does. Though the note on Handle::current sounds like it would solve it in your case?

Create the stream in create_async even though the creation itself doesn't require async

The reason I am not a fan of this is that it signals that the function is async, but it will never yield.

Oh I see the issue now, if the task gets moved to a thread that does not have a executor in by the mixer it might fail. I am not sure why I am not running into this in my own tests?
Is the example completely fulfilling in this regard?

My solution is to wrap HlsRequest in a new Compose implementation with should_create_async set to true:
use async_trait::async_trait;
use reqwest::Client;
use songbird::input::{AudioStream, AudioStreamError, Compose, HlsRequest, Input};
use symphonia_core::io::MediaSource;

pub struct SoundCloudStream(HlsRequest);

impl SoundCloudStream {
  pub fn new(client: Client, url: String) -> Self {
    Self(HlsRequest::new(client, url))
  }
}

#[async_trait]
impl Compose for SoundCloudStream {
  fn create(&mut self) -> Result<AudioStream<Box<dyn MediaSource>>, AudioStreamError> {
    Err(AudioStreamError::Unsupported)
  }

  async fn create_async(&mut self) -> Result<AudioStream<Box<dyn MediaSource>>, AudioStreamError> {
    self.0.create()
  }

  fn should_create_async(&self) -> bool {
    true
  }
}

impl From<SoundCloudStream> for Input {
  fn from(stream: SoundCloudStream) -> Self {
    Input::Lazy(Box::new(stream))
  }
}

The reason I am not a fan of this is that it signals that the function is async, but it will never yield.

Yes i'm aware of this, and i'm not a fan of this either. It results in a colored function of a synchronized task.
However, this is currently the simplest solution without modifying the underlying mixer code.

Oh I see the issue now, if the task gets moved to a thread that does not have a executor in by the mixer it might fail. I am not sure why I am not running into this in my own tests?
Is the example completely fulfilling in this regard?

The only usage of HlsRequest in this repo is wrapped within create_async and only uses the create function, so nothing would go wrong.
Because I'm using HlsRequest directly and the Compose is marked as sync, it will be created on a different thread in the pool which does not have access to the tokio runtime.

I think #262 should fix it, you are welcome to try it out if you have some time.

Perfect! Thanks for your help.


2024.11.0 WebRTC streaming not working from WAN

I’m using

frigate integration 5.4.0
frigate 0.15-beta.
Home Assistant Cloud
HA iOS app

I have added the camera live steam to cards in HA.
I enabled webrtc in the frigate integration and it works fine as long as I’m on the same LAN.
However, if I’m external on cellular WAN I only get a static image.
If I add an rtsp restream from frigate to the Generic Camera integration it shows live feed ok on the card when on WAN.
The live feeds within the frigate WebUI also works fine on WAN.

Did you configure WebRTC in Frigate?
https://docs.frigate.video/configuration/live/#webrtc-extra-configuration

BTW also try https://github.com/blakeblackshear/frigate-hass-integration/releases/tag/v5.5.1.

I did not configure WebRTC in Frigate as I'm running through the add-on.
With v5.5.1 I still have the same issue.
The doc says 'unless you are running through the add-on, you will also need to set the WebRTC candidates' I took this as meaning that the add-on would handle the WebRTC using the Ingress to forward the stream over Assistant Cloud Remote UI?
I take my assumption was incorrect?
Adding the WebRTC section and also adding port forwarding for 8555 on my router seems to be required to get it working.
Is this correct?
What is risk in exposing the stun port?

If you are running through the add-on, then you don't need to configure the candidates. But you'll still need to forward port 8555 UDP and TCP.
I don't know what are the risks.

Thanks for clarification.


Update dependencies and use only yarn.lock

Everything looks good! But why did you remove package-lock.json? There are no problems in keeping yarn.lock, but there is a fair amount of people using npm instead of yarn.

@matheusgrieger I don't recommend using both pack manager, just one, but it 's up to you. I can add package-lock.json again.

I would prefer that, yes.
As npm is currently the "standard" (considering it is installed by default with Node), I assume is what most people use.
Aside from that, everything else looks great, and what you changed is really nice, thank you.

@matheusgrieger Done!

@matheusgrieger You are welcome!

I will be publishing a new version soon. Again, thank you.


While using contact sensor, the simulation stuck when contact happens

Environment

OS Version: Ubuntu20.04
Source or binary build?
Binary, Fortress

Description
I'm just testing the example world contact_sensor.sdf, I found out that when the ball hit the ground, the simulation stuck. The simulation time and real time are both barely moving, but the simulation is still working, because the iterations is still increasing slowly.
After waiting for some time, the simulation shutdown itself and the terminus output some log, which I've added below.

Expected behavior: The simulation should continue in regular rate while the ball hit the ground
Actual behavior: The simulation stuck when contact happens

Steps to reproduce
I did no other action except input "ign gazebo contact_sensor.sdf", and click the start button.
Output
ODE INTERNAL ERROR 1: assertion "aabbBound >= dMinIntExact && aabbBound < dMaxIntExact" failed in collide() [collision_space.cpp:460]
/usr/lib/ruby/ignition/cmdgazebo6.rb:432: [BUG] Segmentation fault at 0x0000000000000000
ruby 2.7.0p0 (2019-12-25 revision 647ee6f091) [x86_64-linux-gnu]
-- Control frame information -----------------------------------------------
c:0007 p:---- s:0059 e:000058 CFUNC  :call
c:0006 p:0016 s:0054 e:000053 METHOD /usr/lib/ruby/ignition/cmdgazebo6.rb:432
c:0005 p:0060 s:0048 e:000047 BLOCK  /usr/lib/ruby/ignition/cmdgazebo6.rb:468 [FINISH]
c:0004 p:---- s:0045 e:000044 CFUNC  :fork
c:0003 p:0674 s:0041 e:000040 METHOD /usr/lib/ruby/ignition/cmdgazebo6.rb:464
c:0002 p:0683 s:0020 E:000c40 EVAL   /usr/bin/ign:275 [FINISH]
c:0001 p:0000 s:0003 E:001f70 (none) [FINISH]
-- Ruby level backtrace information ----------------------------------------
/usr/bin/ign:275:in <main>' /usr/lib/ruby/ignition/cmdgazebo6.rb:464:in execute'
/usr/lib/ruby/ignition/cmdgazebo6.rb:464:in fork' /usr/lib/ruby/ignition/cmdgazebo6.rb:468:in block in execute'
/usr/lib/ruby/ignition/cmdgazebo6.rb:432:in runGui' /usr/lib/ruby/ignition/cmdgazebo6.rb:432:in call'
-- Machine register context ------------------------------------------------
RIP: 0x00007f4730132191 RBP: 0x00007f470b7fd6f0 RSP: 0x00007f470b7fd6a0
RAX: 0x00007f46fc26c958 RBX: 0x00007f470b7fd6c0 RCX: 0x0000000000000004
RDX: 0x00007f46fc26c920 RDI: 0x61756e6574746120 RSI: 0x00007f46fcc34ce0
R8: 0x0000000000000003  R9: 0x0000000000000000 R10: 0x00007f46fc0008d0
R11: 0x00007f46fc000080 R12: 0x00007f46fc723ea0 R13: 0x00007f470b7fd810
R14: 0x00007f46fc723ea0 R15: 0x00007f472eaa05e8 EFL: 0x0000000000010202
-- C level backtrace information -------------------------------------------

Same thing occurs in my setup. It's a particular setup with a conda environment enabled containing the dependencies, and Fortress built with colcon. As described in the downstream issue I linked above, it does not seem that the whole simulation gets stuck, just the GUI.

Same thing occurs in my setup. It's a particular setup with a conda environment enabled containing the dependencies, and Fortress built with colcon. As described in the downstream issue I linked above, it does not seem that the whole simulation gets stuck, just the GUI.

Yes, it seems that the simulation is still running, because I can see the message be printing as the normal refresh rate in the ignition topic. By the way, really like your gym ignition work!

I ported to a source-based fortress setup the patch of #1048 and I confirm that it fixes the problem for me, thanks @azeey!

Fixed by https://github.com/ignitionrobotics/ign-gazebo/pull/1062


Microsoft.Resources/deployment bicep sample should encourage modules

The documentation for Microsoft.Resources/deployments has a bicep example.  Whilst this example isn't wrong, the docs should probably encourage the use of modules rather than using the raw Microsoft.Resources/deployment resource .
https://docs.microsoft.com/en-us/azure/templates/microsoft.resources/deployments?tabs=bicep
https://docs.microsoft.com/en-us/azure/azure-resource-manager/bicep/modules

@stephaniezyen / @tfitzmac -- it would be great if we could include a note here per @afscrome's suggestion.


pipeTransport causes externalConsole to be ignored

VSCode Version: 1.23.1
OS Version: win10.1803

Steps to Reproduce:
i'm trying to debug dotnet core app on wsl from windows. here's my launch config:
	{
			"name": ".NET Core WSL Launch",
			"type": "coreclr",
			"request": "launch",
			"program": "/mnt/c/MyProg/MyProg.dll",
			"args": [],
			"cwd": "/mnt/c/MyProg",
			"stopAtEntry": true,
                        "console": "externalTerminal",
			"externalConsole": true,
			"pipeTransport": {
				"pipeCwd": "${workspaceRoot}",
				"pipeProgram": "bash.exe",
				"pipeArgs": [ "-c" ],
				"debuggerPath": "~/vsdbg/vsdbg"
			},
			"sourceFileMap": {
				"/mnt/c/": "c:\\"
			}
		},

I need to see the console of my app - it's moving the cursor around, drawing ascii art, etc...
but the "console": "externalTerminal" is ignored. no console is opened.

hmmm... this seems to be intermittent. i restarted vscode, disabled/re-enabled the pipeTransport section, and generally messed around with it, and now the console is showing.


Problems mounting Mac OS X shares

Do we need to specify sec=ntlmssp when mounting shares from a server running Mac OS X as mentioned on http://opensource.com/life/15/3/pi-musicbox-guide ? If I had access to a mac I'd check...

Yes, that's the only way I've been able to get the shares working on my Mac.

I guess this is input to the docs.


Unexpected error fetching Tapo resource status data

Description
Receiving this error message:
Logger: custom_components.tapo_control
Source: helpers/update_coordinator.py:315
integration: Tapo: Cameras Control ([documentation](https://github.com/JurajNyiri/HomeAssistant-Tapo-Control), [issues](https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/issues))
First occurred: 09:38:01 (51 occurrences)
Last logged: 09:50:31

Unexpected error fetching Tapo resource status data: 'bool' object has no attribute 'started'

Reproduction Steps
Error in the Home Assistant logs
Expected behavior
No errors
If applicable, add error logs.
Traceback (most recent call last):
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 315, in _async_refresh
    self.data = await self._async_update_data()
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/update_coordinator.py", line 271, in _async_update_data
    return await self.update_method()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/tapo_control/__init__.py", line 380, in async_update_data
    await setupEvents(hass, entry)
  File "/config/custom_components/tapo_control/utils.py", line 1214, in setupEvents
    if not hass.data[DOMAIN][config_entry.entry_id]["events"].started:
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
AttributeError: 'bool' object has no attribute 'started'

Device Firmware
1.3.11 Build 231117 Rel.47346n(4555)
Integration Version
5.4.17PSA
Using stream component
No
Does camera work via official integrations?
Yes
Camera has all attributes filled out in developer tools
Yes
HASS Environment
Core 2024.4.2
Search for similar issues
Yes
Additional information
I have searched the Github and seen other issues that are close to this issue though from what I could see all the other issues  are related to "object is not subscriptable"
I am happy to email the debug log if needed.

Same here with a C200 on Firmware: 1.3.6 Build 230424 Rel.77225n(4555)

I fixed this issue with this little modification in utils.py line 1227 :
   if not isinstance(hass.data[DOMAIN][config_entry.entry_id]["events"], (bool)) and not hass.data[DOMAIN][config_entry.entry_id]["events"].started:

Fixed in https://github.com/JurajNyiri/HomeAssistant-Tapo-Control/releases/tag/5.4.23


Error when using the build breaker task 2 times in AzureDevOps pipeline

Hello Team,
We are using the SonarQube build breaker task 2 times in the same Azure DevOps build pipeline, since we have 2 separate scans configured.  So we will scan the webui source code(java) which gets posted to one Sonar project, then later in the pipeline we scan the DB source code, which gets posted to another Sonar project.  We would like to fail the build if either quality gate fails.  However, with this configuration we get the following error when the second build breaker task executes:
##[error]The operation was canceled.
Is this type of configuration supported?

Thanks in advance for the insight!
-Tom

Interesting. This is not supported right now as I only look at the first available task report as generated by the sonarqube tasks:
https://github.com/simondel/sonar-buildbreaker-vsts/blob/master/extensions/sonarqube/tasks/buildbreaker/common/checkQualityGateTask.ts#L60
This shouldn't cause the specific error that you're getting though... Do you see any logging before you get the error?

Hello!  Thanks for reaching out.  This is the only detail in the logs:
##[section]Starting: Break build on quality gate failure - DB
Task         : SonarQube build breaker
Description  : Break the build when the quality gate fails.
Version      : 7.0.4
Author       : Simon de Lang
Help         :
##[error]The operation was canceled.
##[section]Finishing: Break build on quality gate failure - DB

Hello team. I have the same need indicated by the title of the post. I have a build pipeline with two distinct analysis. As said by Tom in an answer before the result depends only on the first task (alphabetical order) and not on both tasks.
Is this featre going to be implemented in the future?
Thanks
Gianluca

Hi @gt97 and @tlbonds2 :) This has been added with v8.0.0 of the extension.
Could you try it and out let me know if it works for you?
More info: https://github.com/simondel/sonar-buildbreaker-vsts/releases/tag/SonarQube-build-breaker-8.0.0

Since I didn't hear about any issues, I'm closing this issue for now.

Hi Simon,
thank you for your reply
sorry I came back yesterday from summer holiday.
I see there is an issue related with SonarQubePublish introduced by
versione 4.7.0 that doesn't publish the results (
https://developercommunity.visualstudio.com/content/problem/694508/the-new-version-470-of-publish-quality-gate-result.html
).
I think the SonarQubePublish has to work properly for testing the
sonar-buildbreaker
Thank you again
Kind Regards
Gianluca
Il giorno dom 18 ago 2019 alle ore 10:45 Simon de Lang <
<EMAIL_ADDRESS>ha scritto:

Hi @gt97 https://github.com/gt97 and @tlbonds2
https://github.com/tlbonds2 :) This has been added with v8.0.0 of the
extension.
Could you try it and out let me know if it works for you?
More info:
https://github.com/simondel/sonar-buildbreaker-vsts/releases/tag/SonarQube-build-breaker-8.0.0
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/simondel/sonar-buildbreaker-vsts/issues/7?email_source=notifications&email_token=AJWABBU3ST25VHHXIZDDT33QFED27A5CNFSM4IGTMFO2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4Q3OCY#issuecomment-522303243,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AJWABBULD37IH5LD3UKYXV3QFED27ANCNFSM4IGTMFOQ
.

--

Gianluca Tonti*
Architetture e Centro Competenze Test
Sistemi Informativi

Tel: +39 0522 582839 <+39%200522%20582839>
Fax: +39 0522 582859 <+39%200522%20582859>
Via Che Guevara 4
42100 Reggio Emilia
www.credem.it http://www.credem.it/
--
P meno carta... più
alberi: se non è proprio necessario non stampare
questa mail, grazie.
Le informazioni contenute nella presente
comunicazione e negli eventuali documenti ad essa allegati potrebbero
essere tutelate dal segreto bancario e sono comunque confidenziali e ad uso
esclusivo del destinatario sopra indicato. Qualora non fossero a lei
destinati, la preghiamo di tener presente che la divulgazione,
distribuzione o riproduzione di qualunque informazione in essi contenuti
sono vietate. Se ha ricevuto la presente comunicazione per errore, la
preghiamo di volerci avvertire immediatamente e di distruggere quanto
ricevuto. Con il presente messaggio la scrivente società non intende
contrarre obbligazioni o svolgere attività di consulenza o di collocamento
e promozione di strumenti finanziari. L'eventuale assunzione di
obbligazioni dovrà essere espressamente accettata dalla scrivente società
per iscritto o tramite un messaggio che riporti una firma digitale "forte",
così come definita dal DPR 28 dicembre 2000, n. 445, art. 10. La Società
inoltre, ha adottato un Modello ai sensi del D.Lgs. 231/01 e specifici
standard di comportamento per i quali si rimanda alla "Comunicazione
standard etici" consultabile sul sito www.credem.it http://www.credem.it/
Grazie per la collaborazione.
Credito Emiliano S.p.A.
This message
including any attachments contains confidential information intended for a
specific individual and purpose, and is protected by law. If you are not
the intended recipient, you are hereby notified that any disclosure,
copying, or distribution of this message is strictly prohibited, and are
kindly requested to return the e-mail to sender and delete this message
from your computer. By sending this message, our company does not intend to
enter into any legally binding obligation or provide any financial advice
or offer to buy or sell financial instruments or make solicitation of such
products and services. Our acceptance of legally binding obligation must be
confirmed by us either in writing or via e-mail with chriptographically
authenticated digital signature and certification of message integrity (so
called "firma digitale forte", in accordance to art. 10 of the Italian
Decree 28 December 2000, no. 445). Furthermore, the company has adopted a
set of regulations as a means of compliance to the Italian legislation D.dl
231/01, as well as a code of conduct which can be viewed on the website
www.credem.it http://www.credem.it/ under the heading "Comunicazione
standard etici"
Many thanks for your kind co-operation.
Credito Emiliano
S.p.A.


Configuration info by server

Is your feature request related to a problem? Please describe.
Server staff often want to configure permissions to their liking, but they can't do that effectively without being able to see how Idea is currently configured for their server. Idea does not have a way to get the information on how it's configured (eg perms, emojis, etc.) without bugging a dev, which isn't ideal.
Describe the solution you'd like
A verbose message showing the configuration of various bot settings for the current server would allow for server staff to easily see what they need to modify, or confirm that they've set things up right.
Describe alternatives you've considered
A set of commands to get information on the configuration of add-ons in a specific server

Perhaps this could be implemented with a UI.
This is a useful feature so I'm adding it to v0.9

Added in commit c2f65fb
Minor improvements (eg help string) are still necessary

Added minor improvements in 87718f0 to finish UI


[AutoPR monitor/resource-manager] [Monitoring] Add metric alerts api 2018-03-01

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2620

(message created by the CI based on PR content)


migration: disabling vault sa based auth for storage class encryption

This PR contains the migrations of this PR https://github.com/openshift/console/pull/10998
Description: https://github.com/openshift/console/pull/10998/files#issue-1122752788

/ok-to-test

/approve
/lgtm


Crash when accessing settings in the APK

I encountered a bug in the APK that causes the app to crash when I attempt to access the settings menu.
To reproduce the issue, I downloaded the APK file from the provided link and installed it on my Pixel 4 running Android 12. After launching the app, I navigated to the main menu and tapped on the settings option. Upon doing so, the app crashes immediately without any error message.
I expected the settings menu to open smoothly, but instead, the app closes unexpectedly. This issue has been consistent, occurring every time I try to access the settings.
The app version is 1.0.0, and I have attached a screenshot of the home screen before the crash for your reference. If there's any additional information or logs you need, please let me know.

Wrong issue tracker mate.


[Discussion] Export LookupLLVMIntrinsic for C++ users

Hi there,
Currently it seems that LookupLLVMIntrinsic or lookupIntrinsicID is not exposed to C++ users in tvm. But it is available from python side. Please correct me if I am wrong.
To utilize it in C++, I just put it in some header.
Please let me know if this sounds a reasonable request and where should I put it to export. And then I could create a PR for that.
Thanks.

Please open a new thread in https://discuss.tvm.ai/ with development tag :)

To answer your specific question. We try to keep the public API minimum. LookupLLVMIntrinsic is a private API that we use inside the tvm project and maybe we should not expose it for now. Note that it is also part of LLVM API that you might be able to directly get by call into LLVM function.


[Swift 3] Remove Swift 2.x Compatibility + Mark Store as Open

This PR contains two changes:

Remove Swift 2.x compatibility I think it's time to move to Swift 3 only for future releases. For folks that need 2.x older releases should suffice.
Mark Store as open I missed the discussion around this in the Swift 3 conversion. I think the store and its members should be marked as open until to the next major release. While I definitely think we should use public going forward, this is a breaking change. In practice it is breaking my hacky recorder (https://github.com/reswift/reswift-recorder). While this a great way to force me to revisit a better way of implementing recording, I think we should defer breaking the API until to a 3.x release. This way, worst case, the recorder can be migrated to Swift 3 and remain on an rely on a pinned version of ReSwift, as we move on and mark the store as public.

Happy to discuss both of these proposals!

Current coverage is 94.97% (diff: 100%)

Merging #157 into master will decrease coverage by 0.03%

@@             master       #157   diff @@
==========================================
  Files            19         18     -1
  Lines           762        637   -125
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits            724        605   -119
+ Misses           38         32     -6
  Partials          0          0

Powered by Codecov. Last update bc77fb3...e0b0301

Discussed with @agentk. Merging.


Welcome to 2024

I'm not fixing VS stupidity, every single warning you've linked @Rudokhvist is a false positive - there is a reason why those start with IDE and are not part of msbuild, like all other ones (i.e. CS). Take it or leave it :shrug:


Add option to enforce frozen_string_literal: true

This commit adds always_enabled to the Style/FrozenStringLiteralComment cop’s enforced styles to enforce that the frozen_string_literal comment is present and set to true. This is useful for ensuring that all code is valid for upcoming Ruby versions that enforce frozen string literals by default.

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Run rake default. It executes all tests and RuboCop for itself, and generates the documentation.

I wonder if we shouldn't just update the always style to do this. I don't there's much point in having those comments if you don't actually freeze the literals.

I'm closing this PR due to no recent activity. Feel free to re-open it if you ever come back to it.

@bbatsov Sorry for the lack of updates. Would you rather I update the always style instead? Only issue I see is that it will cause regressions for some users who are still in the process of migrating, but I don't think backwards compatibility is a concern (i.e., things usually break when upgrading versions)?


[Fix] Adding background colors to payer information form

[Fix] Adding background colors to payer information form

Se modifican los colores de fondo de la pantalla de Payer Information (form de boleto) para que funcione el skinning

Codecov Report

:exclamation: No coverage uploaded for pull request base (develop@432b66b). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             develop     #911   +/-   ##
==========================================
  Coverage           ?   31.51%
==========================================
  Files              ?      330
  Lines              ?    17443
  Branches           ?     1552
==========================================
  Hits               ?     5498
  Misses             ?    11289
  Partials           ?      656

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 432b66b...a00981e. Read the comment docs.


fixed redundant graph call

Summary
This AADAuthenticationFilter was making a redundant call to Graph , the data was already available in principle
Issue Type

Bug fixing

Starter Names

active directory spring boot starter

Additional Information

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: kaykumar sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


feat(fromOpenApi): respect the "Accept" request header

Uses the matching response according to the Accept request header. If the header is not specified, use the first declared response from the spec.

Released: v0.1.0 🎉
This has been released in v0.1.0!

📄 Release notes
📦 npm package

Make sure to always update to the latest version (npm i @mswjs/source@latest) to get the newest features and bug fixes.

Predictable release automation by @ossjs/release.


PM list shoud have separators

And we should use larger font since package name appears pretty small

Not required if #1416 is fixed since selection already separates items.


OpenVPN: Please add Data Channel Offload (DCO) support w/ FreeBSD 14

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[X] I have read the contributing guide lines at https://github.com/opnsense/core/blob/master/CONTRIBUTING.md
[X] I am convinced that my issue is new after having checked both open and closed issues at https://github.com/opnsense/core/issues?q=is%3Aissue

Is your feature request related to a problem? Please describe.
OpenVPN is known for its mediocre throughput performance even on high end hardware.
Describe the solution you like
Current OpenVPN server versions starting with 2.6 support a feature called "Data Channel Offload" (DCO) which significantly increases the throughput by offloading data processing from user to kernel space. To make this work, a kernel module is need which is included in FreeBSD 14. We found that the throughput performance can be increased by as much as 2-3x compared to non-DCO OpenVPN. My request is to please include DCO support in OpenVPN and to use the DCO FreeBSD kernel module when moving OPNsense to the FreeBSD 14 base.
Describe alternatives you considered
There're no alternative solutions to increase performance as much as DCO does.
Additional context
https://community.openvpn.net/openvpn/wiki/DataChannelOffload/NonLinuxPlatforms
https://reviews.freebsd.org/D34340

@fichtner Quick question so that I understand the "upstream" label: does OPNsense use FreeBSD's openvpn package and therefore the FreeBSD maintainers need to compile it with DCO support?

This depends on FreeBSD 14, which we will be targeting as 14.1. I haven't seen the DCO parts being backported to 13.x.

Makes sense. I just wanted to raise "DCO awareness" because the speed gain is significant. :) Thanks for the clarification.

#7474


Suffix array clean up

I think here instead of removing slices from the string array we should remove from the byte array since suffix array deduplication code returns byte pair pointers. Since a utf-8 character can be represented by 1-4 bytes this can lead to errors with text that have at least 1 character with > 1 bytes.
Maybe something like this
def clean_up(text, remove_pairs):
    """
    Remove duplicate substrings from the text.
    Parameters
    """
    byte_array = np.array(list(text.encode()))
    for start, end in remove_pairs:
        byte_array[start:end] = -1 # byte must be between 0-256
    return bytearray([byte for byte in byte_array if byte != -1]).decode("utf-8", "ignore")

Let me know if I am missing something regarding suffix_array.py code which might already handle this.

Good catch. Thanks for pointing it out, I have fixed it in the the latest commit.

No worries, this is the least I can do to contribute back. Also, here is a minor addition if you like:
Motivation is that there might be cases where k length duplicate text start at one document and finishes in another. In order to avoid that I believe original repo includes a unique separator.
A similar thing can be done in this repo:
        with timer("Preprocessing"):
            offsets: List[slice] = []
            start = 0
            with open(Path(args.google_repo_path) / temp_text, "wb") as f:
                for UID, doc in enumerate(ds):
                    SEP = b"\xff\xff" + struct.pack("<I", UID)
                    doc_bytes = SEP + doc[args.column].encode("utf-8")
                    end = start + len(doc_bytes)
                    offsets.append(slice(start, end))
                    start = end
                    f.write(doc_bytes)

def clean_up(text, slices, UID):
    """
    Remove duplicate substrings from the text.
    Parameters
    """
    SEP_LENGTH = len(b"\xff\xff" + struct.pack("<I", UID))
    byte_array = np.array(list(text.encode()))
    for s in slices:
        byte_array[s.start-SEP_LENGTH:s.stop-SEP_LENGTH] = -1 # byte must be between 0-256
    return bytearray([byte for byte in byte_array if byte != -1]).decode("utf-8", "ignore")

If I read this correctly, this is not needed in my implementation, actually. It keeps track of the document byte level boundaries (offsets) in the beginning code, before merging everything into one giant string, and will restore them when generating those slices, so each generated slice respects the document boundary without any special token.


Finish search early if a forced mate has been found

Codecov Report

Merging #73 (98ba644) into main (ffdba40) will increase coverage by 0.01%.
The diff coverage is 98.61%.

@@            Coverage Diff             @@
##             main      #73      +/-   ##
==========================================
+ Coverage   96.98%   96.99%   +0.01%
==========================================
  Files          58       58
  Lines        6134     6164      +30
==========================================
+ Hits         5949     5979      +30
  Misses        185      185

Impacted Files
Coverage Δ

search/tests/search.rs
85.81% <75.00%> (+0.41%)
:arrow_up:

search/src/alpha_beta.rs
100.00% <100.00%> (ø)

search/src/negamax.rs
98.16% <100.00%> (-0.10%)
:arrow_down:

uci/tests/uci.rs
98.87% <100.00%> (+0.13%)
:arrow_up:

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 ffdba40...98ba644. Read the comment docs.


convert isnull to isna

Pandas prefers isna to isnull, they both have the same functionality

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#192  👈
#191
#190
#189
#188
#187
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @chrisaddy and the rest of your teammates on  Graphite

Merge activity

May 19, 10:03 PM EDT: @chrisaddy started a stack merge that includes this pull request via Graphite.


[M] Configure vanity url for admin and api to user friendly domain

Description:
Configures API to use vanity url that has been decided to align with bc parks domain management strategy.
data.bcparks.ca
data.bcparks.ca/api/parks/names = names and can break it down further /names etc. or just /parks for all info
data.bcparks.ca/admin/parks = admin portal for registrar
Acceptance Criteria:

data.bcparks.ca is official domain for park name register

data.bcparks.ca/admin/parks = registrar portal
data.bcparks.ca/api/parks etc. = api access

Notes:/Gotchas

Certificate creation could be done automagically by SAM Template, or manually in the console in AWS ACM & then the ARN can be copied into the SAM template.
Certificates must be created in AWS Region us-east-1.
Once requested, the CNAME name and CNAME value must be copied into the DNS provider.
DNS verification could take as long as 48h. To troubleshoot the Pending Validation step, follow this article: https://repost.aws/knowledge-center/acm-certificate-pending-validation

See Park Data Service Teams channel for conversation around urls. Unblocking this ticket

Waiting for DNS verification from Rob. Moving to blocked.

A new problem has arisen for this task - currently Day Use Pass imports a wildcard certificate for *.bcparks.ca, which is affecting our requests for our vanity url such as data.bcparks.ca and test-data.bcparks.ca. Since Data Register's vanity url falls under DUP's wildcard umbrella, certification for Data Register falls under the wrong CloudFront distribution.
What needs to happen to fix this? Our DUP distribution likely needs to drop the wildcard certificate and adopt specific certificates, ie reserve.bcparks.ca and  reserve-admin.bcparks.ca. This needs to occur without affecting DUP (now is a good time to make this change). Then, DR can have its own specific certificates.
A&R has no vanity url so it has been unaffected by this.


Has the Actor for group-based licence changes been changed?

Under https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/licensing-group-advanced#find-out-when-group-changes-started-and-finished-processing, "Note that the actor for the operation is Microsoft Azure AD Group-Based Licensing - a system account that is used to execute all group license changes." - doesn't entirely seem to be the case any longer.
(Also, as an aside, the filtering options appear to have changed, and aren't as shown in https://docs.microsoft.com/en-us/azure/active-directory/users-groups-roles/media/licensing-group-advanced/audit-group-license-change.png - with "starts with" now being the only supported operator for "Initiated By (Actor)")
Filtering "Initiated By (Actor) starts with Microsoft Azure AD Group-Based Licensing" works, but the "Initiated by (actor)" column appears to be blank in the UI for licence changes made by Group-Based Licencing.
Upon closer inspection of the Details of such a change: under "Activity" there is no "INITIATED BY (ACTOR)" section at all, however under "Modified Properties" there is a "PROPERTY NAME" of "Action Client Name" with the value "PropagationService".

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

ID: e7e4fdb9-a3d4-e97b-de30-9904868b87a5
Version Independent ID: fbade46e-55b3-3c50-9cff-6ec88ee5ee6e
Content: Group-based licensing additional scenarios - Azure AD
Content Source: articles/active-directory/users-groups-roles/licensing-group-advanced.md
Service: active-directory
Sub-service: users-groups-roles
GitHub Login: @curtand
Microsoft Alias: curtand

@uowdaniel
Thanks for your feedback! We will investigate and update as appropriate.

@curtand I am also not seeing information against "Initiated by (Actor)" column.

Also, the images in the document seems old.   Can you please help here by updates those as well.

Hi @uowdaniel
Thanks for your dedication to our documentation! Unfortunately, at this time we have been unable to resolve your issue in a timely manner and we sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary based on resourcing, so I have created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary. #please-close


Catalog.isVideoTrack expects frame_rate

In moq-pub, it's possible that the bitrate is not passed in the track data:
https://github.com/kixelated/moq-rs/blob/75e7dc03bfc0e64fe243742478bd755b399045a2/moq-pub/src/media.rs#L188
I'm using dev/pub to test the player and changing it to try out something. I needed to use Catalog.isVideoTrack but it expects a video track to have frame_rate:
https://github.com/kixelated/moq-js/blob/e76206fc30b2ccd4a467f3516a43027b347b387b/lib/media/catalog/index.ts#L115
I think we need to remove this check.

Makes sense.


Create Marketplace

From your game screen have a way to get to the market (located on the planet the player is currently on.  Since we cannot travel yet, that would be the planet the player starts on).
In the market, display the trade goods that are for sale and the trade goods currently on the ship
Be able to sell trade goods on the ship
Be able to buy trade goods from the market. They should then go into the cargo hold
You cannot buy more goods than you have money or cargo space.
You cannot sell more goods than are in your cargo space.
Prices are determined through some model and not fixed
Quantity produced varies by planet

[ ] 1. From your game screen have a way to get to the market (located on the planet the player is currently on.  Since we cannot travel yet, that would be the planet the player starts on).
[ ] 2. In the market, display the trade goods that are for sale and the trade goods currently on the ship
[ ] 3. Be able to sell trade goods on the ship
[ ] 4. Be able to buy trade goods from the market. They should then go into the cargo hold
[ ] 5. You cannot buy more goods than you have money or cargo space.
[ ] 6. You cannot sell more goods than are in your cargo space.
[x] 7. Prices are determined through some model and not fixed
[x] 8.  Quantity produced varies by planet

TODO:

Market UI
Connect market with the ship cargo
JavaDocs
Unit Tester


can use 2d physics

is it possible to run and render 2d physics created in lua?

Its a bit hard to understand what you are asking here as that is a very general question. Do you have more details about what you are trying to achieve?

lua is for games right? can it support 2d physics simulation using a code generation in lua?

Lua is not "for games" but it is widely used as a embedded scripting language in many games.
Luadardo supports most but not all features of Lua 5.3.


Unexisting file issue

If i open a moved file from menu

infinite loading is displayed

same issue when opening incompatible file from menu


WSL 2 multiple swapFile possible?

Correct me if I didn't understand it right, wsl 2 manage its own swap file configured in .wslconfig, while wsl 1 utilizes windows managed Vitual Memorry in Control Panel. The problem is the .wslconfig only support one swapFile according to Microsoft Docs. Multiple swap file with different priority on multiple hard drives will be really useful. Is it possible now or in the future?

This is effective /dupe #689 and #4556. If there were a way to expose another block device (real or virtual) to WSL then you could mkswap(8) and swapon(8) it.

Multiple swap file with different priority on multiple hard drives will be really useful

If you say. Giant swap files sort of went out of style a couple of decades ago in favor of other approaches. But maybe there are some use cases still around.

Given existence #5476 and also given that the ask here is specific (multiple swap files specified in .wslconfig) this isn't same-enough as the block device asks to dupe. Whether something like that gets implemented I can't say but it is a fair ask.


Unable to access previous or initial state

How can I access the actual state, and not the Immer draft object? An example is when I want to use the initial state values for something in my reducer or when I'd like to compare against values in the current state before performing an update
  NOTIFICATIONS_FULFILLED: (state, action) => {
    // state is the draft object from Immer
    // but I want to access the values set on my actual state
  },

Currently if I do state.someProp as you would in a normal reducer it just logs an empty Proxy

Hmm.  At the start of the function, the draft object should represent the latest state, so you should be able to just use that as a starting point for any comparisons.
I guess I'm not really seeing what the issue is here.  Can you give a specific example, preferably with a CodeSandbox repro, of something you want to do that isn't working correctly?

Sure,
import { createReducer } from "redux-starter-kit";
export const initialState = {
  result: []
};

const Notifications = createReducer(initialState, {
  TEST(state, action) {
    console.log(state.result);
  }
});

Notifications(undefined, { type: "TEST" });

In the above example I'd expect the log to be [] but it is instead a Proxy object. I'm presuming this is because the draft object is passed as the 'state' and the actual state object is inaccessible. So I can write to the state, but I cannot read from it. Or have I misunderstood?
A use case for this might be wanting to compare a value on the existing state object before deciding what to update on the draft
Link - https://codesandbox.io/s/2v017oozy0 (needs browser console)

Immer is using a Proxy to wrap the state object, but as far as I know it should still let you access the underlying state as normal.
If I do console.log(state.result.length) in that sandbox, I see it print 3, as expected.

Ah, okay. I think that even though I'm not seeing [] I can still access things like .map() and .length.
Thanks for your time!


Feature: Implementing a share button on pass pane to share the challenge on tweet

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

Hey @NamanAg0502,
It seems that you are working from your main branch, this is not recommended. Please follow our contribution guidelines on how to open a pull-request.
Also, it seems that you are trying to fix two issues at once. The podcast ascending and descending one and the Twitter card one.


Refactor the error handling in vitrivr-engine.

For productive operation, vitrivr-engine must be equipped with minimum error handling. Error handling must allow meaningful logging, and errors must be thrown in the event of faulty processes and not caught blindly.

What is the status on this issue? What steps have been taken so for? And what are the design goals?
One aspect not to miss is that of data consistency. At the moment, if anything happens during extraction, the stored data is very likely to end-up all-over-the-place.

Close due to a8604aee5fb55c8d76fd1e4ad28525ed9b3abf3a and #22


wip: Better lazy input streaming, worse sorting

Notes:

For now i am just using sort on the individual systemctl commands, but an adjusted _sysz_sort could be used to keep the unit-type sorting.

awk '!x[$0]++' can at least de-duplicate the stream without sorting
(i just picked the first working solution from google https://stackoverflow.com/questions/30906191/uniq-without-sorting-an-immense-text-file)

moving the sed -e "s/^/[$MANAGER] /" logic into _sysz_list isn't necessary, but i think it's a bit cleaner.

Are curly brackets (= no sub-shell) a slightly better choice here? (https://www.gnu.org/software/bash/manual/html_node/Command-Grouping.html)
(
    [..]
)

->
{
   [..]
}

@joehillen Picking up on your comment

by just calling systemctl list-units several times with the order that I want

I am not sure what you mean with this. Do you mean to call the commands for --system list-units, --system list-unit-files, --user list-units &  --user list-unit-files in the order that you want?

Thanks for starting on this. I think sort is going to slow things down. I spent a little time working on it already, and I'm going in a different direction. I'm thinking something like this:
systemctl list-units --user --state=active --type=service | color green
systemctl list-units --user --state=failed --type=service | color red
systemctl list-units --user --all | grep -Ev '( active| failed| not-found|\.service|\.timer)'
systemctl list-units --user --state=not-found --type=service | color yellow
# same as above for timers and system (should abstract to a function)
# I think templates are the only thing remaining
systemctl list-unit-files<EMAIL_ADDRESS>
I haven't fully worked it out yet, but the gist is I would like each command to only present a unique set of units while also inserting colors in the process. It will give us the desired streaming and be faster. This is how I should have done things in the first place :facepalm:
I need to make sure I didn't miss anything and that there aren't any have duplicates.
If you could expand on this, I would be extremely grateful.

Actually, I think --all should be after timers.


refactor cached prepared statement to become ThreadLocal (#5635)

Impact

[x] Bug fix (non-breaking change which fixes expected existing functionality)
[ ] Enhancement/New feature (adds functionality without impacting existing logic)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Description
Fixes #5635

Things to be aware of

Things to worry about

Additional Context

You are welcome!
пт, 3 мая 2024 г., 19:23 filipe @.***>:

@.**** approved this pull request.
Thanks for the PR @adaryin https://github.com/adaryin !
—
Reply to this email directly, view it on GitHub
https://github.com/liquibase/liquibase/pull/5874#pullrequestreview-2038525779,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BCNKPTTSSL7SPYNFSA6UUITZAO2ZDAVCNFSM6AAAAABHFQPRGGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDAMZYGUZDKNZXHE
.
You are receiving this because you were mentioned.Message ID:
@.***>


App Service availability

Is this available for Azure App Service running on Windows containers? I see that it isn't available for Windows containers inside ACI but I believe another page says it's in preview for an App Service running Windows containers. I can't get it to work and am having difficulty finding anything clear.

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

ID: 726adac9-1848-01a6-9586-842c81f820f7
Version Independent ID: 249db438-8c95-8e69-f69e-8e48fcd0b359
Content: Azure Services that support managed identities for Azure resources
Content Source: articles/active-directory/managed-identities-azure-resources/services-support-managed-identities.md
Service: active-directory
Sub-service: msi
GitHub Login: @MarkusVi
Microsoft Alias: priyamo

@sirdank Thank you for your feedback . We will investigate and update further.

@sirdank it is currently in preview. Is there any specific error you are receiving when you try to get it to work?
@MarkusVi do you know of any guides or documentation for managed identities with app services running on Windows containers? Also, do you plan to update this document to show that this is in preview?
https://docs.microsoft.com/en-us/azure/app-service/overview-managed-identity

@MarileeTurscak-MSFT For me, the portal's identity option is entirely disabled but since doc says it's in preview, I thought I'd try az webapp identity assign --name myApp --resource-group myResourceGroup. It appeared to work.
However, when trying to use the Azure.Services.AppAuthentication's AzureServiceTokenProvider.KeyVaultTokenCallback, I get that generic error about how it tried four different ways to obtain a token and all of them failed. Additional googling revealed an issue opened on a different doc where a Microsoft employee suggested following these directions to obtain an access token for use with a custom authentication callback in the key vault client from inside the container.
This also was a dead end as calling <IP_ADDRESS> from inside my container never returns a response. I deployed to a new resource group that I do not believe is associated with any custom VNets so I'm baffled.

@sirdank I am looking into this with the product team. In the meantime, if you would like to open a free support case to look into your specific issue, you can send your subscription ID to<EMAIL_ADDRESS>and I will open one for you.

@MarileeTurscak-MSFT Thank you. I sent an email.

Thanks @sirdank .  I have enabled you for technical support. Since this is in preview I believe it should work but I am confirming your scenario with the product team and will update the thread accordingly.


Multi-use CTE's

Fixes #5189.
PR includes the following:

Changed all CTE examples to use MovR
Added multiple-use example
Removed all mentions of now-lifted limitations (from common-table-expressions.md and known-limitations.md)

This change is

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/d5c1a0dd0fc9b90d50c13307583fe829210c4a1d/
Edited pages:

v19.2/common-table-expressions.md
v19.2/import.md
v19.2/known-limitations.md

stuff related to multi-use CTEs in the second commit , looks like there might have been an extra commit from lauren that got picked up in this PR?

Reviewable status: :shipit: complete! 1 of 0 LGTMs obtained (waiting on @justinj)

Yeah that was weird... fixed it. Thanks!

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/a660cc4b3635644b3a342938793b52801636080c/
Edited pages:

v19.2/common-table-expressions.md
v19.2/known-limitations.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/f7581ae777fcbc9915a0912625fe9c1738448d05/
Edited pages:

v19.2/common-table-expressions.md
v19.2/known-limitations.md

Online preview: http://cockroach-docs-review.s3-website-us-east-1.amazonaws.com/88899c6e199ac13a83d2c1cd0066252d370a5826/
Edited pages:

v19.2/common-table-expressions.md
v19.2/known-limitations.md


Canberra Institute of Technology

Canberra Institute of Technology uses cit.edu.au for teaching staff and students.cit.edu.au for students.
students.cit.edu.au appears to already be in the list of approved domains.

@dhester1 First stage of verification passed, official domain for Canberra Institute of Technology is cit.edu.au as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@dhester1 Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Respond to the HashiCorp license change

How to categorize this issue?

/area delivery
/kind enhancement
What would you like to be added:
HashiCorp announced a license change which will not be permitted within CNCF (nor SAP). For that reason CNCF community is collecting HashiCorp components usage to prepare for the proper response.
Just like a lot of other Kubernetes components, in Gardener we are also using several (more or less standard) Go libraries from Hashicorp for which I am opening this issue.
At this moment it's too early to think about concrete migration steps - we shall wait for the response from the community first (e.g. certain projects might be forked).
Why is this needed:
Compliance: use libraries with permitted license
According to HashiCorp (discussion forum, FAQ) the following products/projects and versions are affected:

Terraform >1.5.5
Vagrant >2.3.7
Packer >1.9.2
Waypoint >0.11.4
Boundary >0.13.1
Consul >1.16.1
Nomad >1.6.1
Vault >1.14.1
Vault Secrets Operator > 0.1.0
Vault Provider for Secrets Store CSI Driver > 1.4.0
Go library for encrypting values through various KMS providers license change was announced, but has not yet happened (Aug 16, 2023)

We only use terraform, but the versions are controlled in https://github.com/gardener/terraformer (e.g., here), and generally the colleagues (@kon-angelo @MartinWeindel) are already in the process of migrating away from terraform.
In gardener/gardener, the only direct dependency to a HashiCorp library is https://github.com/gardener/gardener/blob/27bb801d262127e62bbf3a67bf556f0f216ef1f6/go.mod#L21 I don't think this affected by this license change.
Other than those, nothing else from your list above is used in gardener/gardener.
TL;DR: Shall we move this issue to https://github.com/gardener/terraformer (or maybe simply close it entirely since I don't see what concrete action items should be taken now)?


Pre-1.9 Async-Smooth Hit Detection!

SmashHit features for better Hit Detection (Async Hit Detection), you can read all its info right here: https://github.com/Speentie8081/SmashHit

Duplicate of #19


Path to 1.0.0

Hey! Really awesome work here man. No issues, just a question about the future of the project. We're looking into redux orm as a crucial piece of our front end framework, so I'm curious what your ideas are for a v1 release, or maybe why you wouldn't consider the current state viable.

So just to toss in my own two cents as an evaluation: I've probably been the biggest proponent of redux-orm so far.  Tried it out right after it was first published, talked with @tommikaikkonen quite a bit about features and use cases, pasted the link into a few dozen comment threads, etc.  And, it's been working great so far in my own app.
I'm maybe using it a bit differently than some of the "suggested" approaches.  Rather than defining reducers in my Model classes, I'm basically using it as a sort of advanced set of "selector" functions in my reducers, my thunks, and my mapState functions.  I'm also using it for its immutable update abilities in my reducers as well.
There's a whole bunch of other libs that try to put some kind of OOP layer on top of Redux, but most of them start taking Redux in a pretty significantly different direction.  redux-orm, on the other hand, keeps itself limited enough to some very useful behavior for managing normalized data in your store.
So yes, I'd absolutely say it's a viable usable tool to work with at this point.

Thanks for the vote of confidence @markerikson :)
I'd say the reason the version is 0.x instead of 1.x is the limited feature set compared to ORMs in general, not the stability or quality of the code. As you assess your options, you'll also want to read my thoughts on on related data in Redux in general.
Due to the smaller feature set, the "database" abstraction is not perfect. If the abstraction doesn't offer what you need, it can be hard to achieve it without a bunch of hackery. Otherwise it should be enjoyable to work with.
Based on the GitHub issues I've received, here are the current big pain points:

Do you want to store order of elements? Add a column the specifies the order value, but each query will do O(n) lookups without the ability to put an index on that column.
When deleting a model, do you want the related models to be deleted too? Current deletion strategy is just SET_NULL, no support for CASCADE.
Do you want custom through models in many-to-many relationships? You need operate with a manual through model.

Based on those pain points the todo list is:

add ability to add indexes on columns (other than the ID, which is indexed by default)
add CASCADE deletion strategy and
add custom through models.

Perhaps after those features, a 1.0 would be in order. As to when they'll be done, I can't promise anything. Help in the form of pull requests is always welcome and I'll happily review them.

Boy, that list of pain points sounds.... familiar :)
FWIW, using my own field for ordering, implementing my own "update a Model instance from another instance" logic, and implementing my own cascaded delete logic has worked out great for me so far.  Got past my mental block and been able to crank along on features the last couple weeks.
Also, one other related note.  I've had several places where I need to do a fairly large update as part of one overall step, but it requires a number of smaller updates in the process.  These updates also tend to be dependent on each other.  (Example: recursing upwards through a tree of data, where each parent's current checked/unchecked/partially-checked state has to be calculated based on its immediate children.)  redux-orm's queued updates are great for being non-destructive, but don't lend themselves to that iterative process.  My original implementation of the checkbox logic actually hacked around things by reading the current Session's pending update queue, which is a horrible approach.
You could also call session.reduce() and create a new Session from the new data, but that seemed a bit painful and redundant.
I finally figured out that a Session instance just does lots of lookups for its current this.state variable.  So, I could actually just do session.state = session.reduce(), swap out the old state tree with the new state tree, and still have the current "session-bound classes" work.  That's made my multi-step updates reasonably nicer, I've just had to comment the approach to clarify what I'm doing.
Maybe worth adding something like that as a built-in operation?

@markerikson I've just started using Redux-Orm and finding that I'm having a similar problem to what you are talking about. I hope it's ok to ask in here, otherwise i can create a seperate issue for this.
In my case I'm loading records and their relations from the backend, and I want to loop over them to both create the item itself, and its relation.
But it does not seem to work due to the queued nature, could you share some additional details on how you solved it with session.state = session.reduce()?
My action looks something like this;
      case ADMIN_LOAD_DEPARTMENTS_SUCCESS:
        const departments = action.payload.data;

        departments.forEach(function(department) {
          Department.create(department);
          if (department.DepartmentId != undefined) { Department.withId(department.DepartmentId).children.add(department.id); }
        });
        break;

@orecus : a Session instance is really just a facade over a plain JS object (which could actually come from anywhere, not just from your Redux state).  If I do const value = someModel.someRelation.someField, Redux-ORM will look up the related model when the someRelation property is accessed, and then look up the someField value in the underlying JS object when the someField property is accessed.
The current underlying object is stored as session.state.  Calling session.reduce() applies any pending updates and returns a new state value.  So, session.state = session.reduce() creates a new state object, and then updates the session instance to use that object when doing data lookups.  That means that the next time one of the Model instances from that session is accessed, the data will come from the updated object.
I actually just wrote a blog post discussing this technique and several others: http://blog.isquaredsoftware.com/2016/10/practical-redux-part-2-redux-orm-concepts-and-techniques/ .

@markerikson Thanks for the input! Still having some issues to get things going properly with initial loading by creating and adding the relations from my backend, still doing further research to this and learning.
I could have explained the example a bit better, a department can have a relation to another department trough the DepartmentId, so what i'm doing is adding the created department as a child to another department. So DepartmentId is the "parent" department that this deparment should be a child of.
I'm looking forward to your next post and the example application, as i'm sure i could learn a thing or two from it. :)
Footnote: My work had your blog blocked due to "Filter Avoidance" for some reason. :/

Okay, that makes a bit more sense.  One possible approach might look like this:
// Queue initial CREATE commands
departments.forEach(department => Department.create(department));

session.state = session.reduce();

departments.forEach(department => {
    if(department.DepartmentId !== undefined) {
        const parentDepartment = Department.withId(department.departmentId);
        // Queue UPDATE commands
        parentDepartment.children.add(department.id);
    }
});

// OPTIONAL: if using your own reducer instead of a reducer
// defined on a model class, apply updates and point Session at new data.
// Otherwise, this is done automatically.
return session.reduce();

FYI, I've got Part 3 in the series mostly written.  Hoping to review it tonight and publish in the next day or two.
As for the blog filtering: yeah, I think I know why.  Several years ago I had briefly set up a proxy script for some reason I can't remember, and that apparently got found by bots, then it was flagged by web filters.  Apparently those filtering tools still have my site in their databases :(

@markerikson Thanks! Still hitting my head here on this, but I'll create a new issue with more details instead of poluting this one with further derailment.
I'll keep my eye out for your new blog entry!

#140


Feature: Update css build

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Feature

What is the current behaviour? (You can also link to an open issue here)

no vendor prefixes with compiled css

What is the new behaviour (if this is a feature change)?

Added postcss autoprefixer to add vendor styles

Other information:

Also updated to Bootstrap 4 alpha 6

Coverage remained the same at 100.0% when pulling 5339e2f0eaa637d42d729ec78eb067b62b645a3a on feature/update-css-build into f153a66ea5d42015b3d6fe88feaa506e1fae6e29 on master.

Coverage remained the same at 100.0% when pulling 5339e2f0eaa637d42d729ec78eb067b62b645a3a on feature/update-css-build into f153a66ea5d42015b3d6fe88feaa506e1fae6e29 on master.

Coverage remained the same at 100.0% when pulling b22699c8f696bd5a8d2541ff4d1cfe9d266d0125 on feature/update-css-build into f153a66ea5d42015b3d6fe88feaa506e1fae6e29 on master.

Coverage remained the same at 100.0% when pulling d061466b783ec902d22a42dd4dd63b1ec3e948ff on feature/update-css-build into 97260d247050473b58086bfa71070eee3eb0e23d on master.


Milestone 1 Report

This was submitted yesterday. See https://milestones.projectcatalyst.io/projects/1100180/milestones

One of the Catalyst reviewers responded with:
"Not Approved
I think that the general outcomes of this milestone has been achieved, though I would like to see the provided video with the tests to be included into the github repo itself, showing the users of the library all those tests working. "

See attached output from my running today of the signify-ts build, unit tests, and integration tests: signify-ts results of build unit test and integration test run 2024-05-26.txt

The signify-ts build, unit tests, and integration tests from my local run today all passed, as shown in the early comment.
For the video linked in the original Milestone 1 report, https://drive.google.com/file/d/1C8-wIn0Ul8-oG4ioN2NCWyGHK85tR7Ue/view -- its file size exceeds GitHub's 100MB limit to attach here.  That video also does not show all integration tests passing at the time it was recorded.
The signify-ts project at https://github.com/weboftrust/signify-ts has automated tests implemented and run via GitHub actions, which can be seen at https://github.com/WebOfTrust/signify-ts/actions with results https://github.com/WebOfTrust/signify-ts/actions/workflows/main.yml .  These typically, but not always, pass after each commit to that repository project.

Updated and resubmitted just now the Milestone 1 Proof of Achievement, with the following content:
A) Public GitHub repository (project) is now live and public with the mentioned artifacts. It addresses the Acceptance Criteria A. For evidence, see https://github.com/KERIAuth/keriauth-blazor-wasm
B) Results of reviewing and testing the code in https://github.com/WebOfTrust/signify-browser-extension
As part of our Fund 11 Milestone Report, we recorded a video that shows the signify-browser-extension and its dependency signify-ts, both being built and tested: https://drive.google.com/file/d/1C8-wIn0Ul8-oG4ioN2NCWyGHK85tR7Ue/view?usp=sharing
The signify-ts project at https://github.com/weboftrust/signify-ts has automated tests implemented and run via GitHub actions, which can be seen at https://github.com/WebOfTrust/signify-ts/actions with results https://github.com/WebOfTrust/signify-ts/actions/workflows/main.yml. We also included text output from our local running of the signify-ts build, unit tests, and integration tests, which can be found referenced in the following GitHub issue: https://github.com/KERIAuth/keriauth-blazor-wasm/issues/16 and at https://github.com/KERIAuth/keriauth-blazor-wasm/files/15448087/signify-ts.results.of.build.unit.test.and.integration.test.run.2024-05-26.txt.
The primary dependency the signify-browser-extension and this project’s keriauth-blazor-wasm code each have is the signify-ts library, which both we’ll also use to communicate with a KERIA agent service developed and maintained by the WebOfTrust community.
We also reviewed the code of signify-browser-extension. The code is under active development, and we continue to monitor commits to it in GitHub, as well as attend weekly meetings with the developers as part of the WebOfTrust implementer’s call.
We found the code’s good use of ECMAScript Modules modules and React resulted in clean code. Those choices may be easier to work with than the C# Blazor WASM design approach we have chosen. We stuck with C# Blazor WASM because of our familiarity with it and potential to leverage the code on hosted WASM solutions in the future. This has some advantages (such as type safety and available libraries to leverage), and some disadvantages (edit-compile-debug/test cycles).
We found that C#-JavaScript interop mechanisms in .Net was unfamiliar to us and presented such a big architecture risk that we decided to address it immediately. It is now de-risked, but it caused almost a month of delay to our original M1 target.
It is unclear how much, if any of the signify-browser-extension code we’ll use beyond some design and requirement inspiration. There are major differences in our design approach, especially with UI.  We’ll likely use some of the JavaScript interfaces in the signify-browser-extension’s Content Script, used both for interaction with the website page and  the service-worker. However, we do not like that the signify-browser-extension injects user interface elements and/or an iframe onto the website; we’d rather that be under the complete control of the website designer.
The signify-browser-extension also implements some features, such as signed headers that we may not implement during our Fund 11 project, as that is beyond our committed scope.  Such a feature may also require manifest permissions that would make it difficult to get our extension published in the Chrome Web Store.
We will heavily use the signify-ts library, and do not expect that to be a blocker, since several other projects in the KERI vLEI (GLEIF’s Verifiable Legal Entity Identifier) ecosystem are building on top of it.
C) Feature List in GitHub
See https://github.com/KERIAuth/keriauth-blazor-wasm/issues?q=  The features are marked with label “enhancement” and milestones F11/M2 or F11/M3.
D) Architecture Diagram and description
See https://github.com/KERIAuth/keriauth-blazor-wasm?tab=readme-ov-file#architecture.


feat: added calendar component

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

GitHub release
npm package (@latest dist-tag)

Your semantic-release bot :package::rocket:


Private xrp network restart, log file always output: LedgerMaster: DBG No Validat ledger

I started two xrp validators on two machines. This is my own private xrp network, not connected to the xrp main network.
Machine A's ip is <IP_ADDRESS>
Machine B's ip is <IP_ADDRESS>
The rippled.cfg of Machine A is as follows:
[server]
port_rpc_admin_local
port_peer
port_ws_admin_local
[port_rpc_admin_local]
port = 5005
ip = <IP_ADDRESS>
admin = <IP_ADDRESS>
protocol = http
[port_peer]
port = 41234
ip = <IP_ADDRESS>
protocol = peer
[port_ws_admin_local]
port = 6006
ip = <IP_ADDRESS>
admin = <IP_ADDRESS>
protocol = ws
[node_size]
medium
[node_db]
type=RocksDB
path=/data/rippled-db/db/rocksdb
open_files=2000
filter_bits=12
cache_mb=256
file_size_mb=8
file_size_mult=2
advisory_delete=0
[database_path]
/data/rippled-db/db
[debug_logfile]
/data/rippled-db/debug.log
[sntp_servers]
time.windows.com
time.apple.com
time.nist.gov
pool.ntp.org
[validators_file]
validators.txt
[rpc_startup]
{ "command": "log_level", "severity": "debug" }
[ssl_verify]
1
[ips]
<IP_ADDRESS> 41234
[ips_fixed]
<IP_ADDRESS> 41234
[voting]
account_reserve = 0
[validator_token]
eyJtYW5pZmVzdCI6IkpBQUFBQUp4SWUxMExkMWJETGhGOW5iRUI4dUM2aURxaUt5TDkyb1BW
L2lpNDJuVnhCTDhqM01oQWcvSjV0NVd3VFlXKzkxcXRldlhyRVRLbHhub3JXekxKZmFwUjlF
N2RJeEdka2N3UlFJaEFPaW1HdW4xV3ZsSGRXZ1YzT2N1Tld4bGdKcGxrb2EwNDArQkg1Nk9j
UGFEQWlBVk4ySElyRDJibVNtWDQ3WGxOSEtlcGJmVUhnbHJQbXRGbzc3aGthaGxwM0FTUUY0
Rm44SnJXU0o3WWdONVliRk8xSnd2VGZaR0U4L2hiVFppV3FOb1d3ZXQyT1ZZM01NZDJIS1ls
Z0YwTGQwYTg1c1VkaVpaNVBlbHVDK1d0RStXK1FJPSIsInZhbGlkYXRpb25fc2VjcmV0X2tl
eSI6IjY0NTEyOENFODdFMUEzQkRBQzZENDJDRDdERERCMjVCQjVEQzBGMzlEQzdFNjZEQkZE
Nzk3REM3QzNBNTBGNUEifQ==
The rippled.cfg of Machine B is as follows:
[server]
port_rpc_admin_local
port_peer
port_ws_admin_local
port_ws_public
[port_rpc_admin_local]
port = 5005
ip = <IP_ADDRESS>
admin = <IP_ADDRESS>
protocol = http
[port_peer]
port = 41234
ip = <IP_ADDRESS>
protocol = peer
[port_ws_admin_local]
port = 6006
ip = <IP_ADDRESS>
admin = <IP_ADDRESS>
protocol = ws
[port_ws_public]
port = 6005
ip = <IP_ADDRESS>
protocol = ws
[node_size]
medium
[node_db]
type=RocksDB
path=/data/rippled-db/db/rocksdb
open_files=2000
filter_bits=12
cache_mb=256
file_size_mb=8
file_size_mult=2
advisory_delete=0
[database_path]
/data/rippled-db/db
[debug_logfile]
/data/rippled-db/debug.log
[sntp_servers]
time.windows.com
time.apple.com
time.nist.gov
pool.ntp.org
[validators_file]
validators.txt
[rpc_startup]
{ "command": "log_level", "severity": "debug" }
[ssl_verify]
1
[ips]
<IP_ADDRESS> 41234
[ips_fixed]
<IP_ADDRESS> 41234
[voting]
account_reserve = 0
[validator_token]
eyJtYW5pZmVzdCI6IkpBQUFBQUZ4SWUzNWh3NXN4STZkempmN0MwM2taUTRmYlZFcm5FaDRE
MEdrOW5QQUFRVE1CM01oQTNwZWpMVkpJcHU0Y3NWNS9WemZJQ3JrL0N6d0htL0NTcG1yaVRK
NFp3bnRka1l3UkFJZ0xac2V4YlRaQXR2dlJCdUt2cGdJaHpXRnlKNUtnbUhMNnB2cVpaRnJW
c1lDSUJ0UjcxNHFLV3kxOEV6WUJ5UEVBVVB3MW9Nck8wSXZhOTlVTDZHSDZWT3pjQkpBeEZE
N2tMMDlqeDc1aW02N0ZLd2RpamlLVEFNZkdhaWJ1MmtjSUZPS1AyMVpic3hQSzMvaHFLMndi
RytPN2FuLzNNdzFBUng4a05LRE1MTlR4cTEvQWc9PSIsInZhbGlkYXRpb25fc2VjcmV0X2tl
eSI6IkIwN0Q2NTExMTU3QkJEQzQzRDc5OEE3NkY3RjQ4QTNCOTJDRkYzNDU3MjQ2OEEzRkIx
QzE4RkQ0NUY2RUQwQkMifQ==
The validators.txt of Machine A and Machine B are as follows:
[validators]
nHUNbyUFgCMNYaH6n9qQWSxftPojkoBKpujognSHNQAxR9Yzxg69
nHDELB9vB3R9UYX9LSmQA3JuAS5eMQYG6wJbAksWTtkLE1uFAeH9
Machine A's start command is
/data/rippled/my_build/rippled --conf=/root/.config/rippled/rippled.cfg --start --valid
Machine B's start command is
/data/rippled/my_build/rippled --conf=/root/.config/rippled/rippled.cfg
They run up and generate a fresh ledger.
After a period of running, I restarted Machines A and B, and their restart commands were
/data/rippled/my_build/rippled --conf=/root/.config/rippled/rippled.cfg
after that, log file always output: LedgerMaster: DBG No Validat ledger
Why???Why is that? Is it some of my steps are wrong?

It's done. One of the start-up plus --load, and then start the other, it solves the problem.


Special characters in Git (Project) Wiki Title

Hello, I accidentally used some special characters (/  \  ') in the title of a newly generated wiki page and saved it. After saving, it immediately displayed "404 page not found", which is fine (I can start a new page without these special characters).
But the page with the special characters in its title is still listed in the "Pages" (./wiki/_pages) list as well as in the Drop-Down List which is shown in every page under this Wiki, with the special characters in the page title. (But if I click it, it shows "404 page not found" of course)
Any idea that I can delete the page with the special characters in its title completely?
Also would like to request add the blocker functionality to stop saving when there's any reason that would affect the access of the page after saving (special character in the title apparently is one of these reasons.)
My Config: Gitea 1.15.0 Binary with NGINX 1.18, and MariaDB 10.5 on Debian 11 x64

The wiki is a git repo so you should be able to just clone and push it back it up after having changed the name of the file.

The wiki is a git repo so you should be able to just clone and push it back it up after having changed the name of the file.

Thanks. Done. Closing.