fix(examples): Change region for examples from eu-central-1 to eu-west-1

Description
During release there was an error in eu-central-1 region. Even when we specify TGW attachment with enabled appliance mode support, attachment is created with disabled value. Then while checking idempotence Terratest propose to change it into enable as it's defined in default value for appliance_mode_support:
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:   # module.transit_gateway_attachment["app1"].aws_ec2_transit_gateway_vpc_attachment.this will be updated in-place
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:   ~ resource "aws_ec2_transit_gateway_vpc_attachment" "this" {
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:       ~ appliance_mode_support                          = "disable" -> "enable"
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:         id                                              = "tgw-attach-0f219e9c790aa6aee"
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:         tags                                            = {
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:             "Name" = "tt-42b8-app1-spoke-vpc"
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:         }
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:         # (9 unchanged attributes hidden)
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:     }
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:   # module.transit_gateway_attachment["app2"].aws_ec2_transit_gateway_vpc_attachment.this will be updated in-place
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:   ~ resource "aws_ec2_transit_gateway_vpc_attachment" "this" {
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:       ~ appliance_mode_support                          = "disable" -> "enable"
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:         id                                              = "tgw-attach-05adc27b67c0e7698"
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:         tags                                            = {
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:             "Name" = "tt-42b8-app2-spoke-vpc"
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:         }
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:         # (9 unchanged attributes hidden)
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:     }
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:   # module.transit_gateway_attachment["security"].aws_ec2_transit_gateway_vpc_attachment.this will be updated in-place
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:   ~ resource "aws_ec2_transit_gateway_vpc_attachment" "this" {
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:       ~ appliance_mode_support                          = "disable" -> "enable"
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:         id                                              = "tgw-attach-09b2a15315de25671"
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:         tags                                            = {
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:             "Name" = "tt-42b8-vmseries"
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:         }
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:         # (9 unchanged attributes hidden)
  TestIdempotence 2023-10-12T04:43:08Z command.go:185:     }

While testing the same example in different regions e.g. us-east-1 or eu-west-1 there is no issue and TGW attachment is created with enabled appliance support (as it's defined in default value for appliance_mode_support).
It seems to be a bug in eu-central-1 region, so PRs delivers change of region for examples from eu-central-1 to eu-west-1.
Motivation and Context
There was an issue while doing release: https://github.com/PaloAltoNetworks/terraform-aws-vmseries-modules/actions/runs/6490065707
How Has This Been Tested?
Code was tested via ChatOps (see comments in PR).
Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes if appropriate.
[x] All new and existing tests passed.

/help

/plan paths="examples/combined_design examples/centralized_design examples/combined_design_autoscale examples/combined_design" tf_version="1.5"

/idempotence paths="examples/combined_design examples/centralized_design examples/combined_design_autoscale examples/combined_design" tf_version="1.5"

/idempotence paths="examples/combined_design examples/centralized_design examples/combined_design_autoscale examples/combined_design examples/isolated_design examples/isolated_design_autoscale examples/panorama_standalone examples/vmseries_standalone" tf_version="1.5"


sample project is not working

@ThomasGorisse I was trying to run the sample project but I was getting the error I attached the screenshot of the error.

I got the same issue - how did you fix it?


Create nightly binary packages for Fedora

This is an (easy) entrance task for the installation project: Create a Python script that creates a binary package of the latest Shogun on Fedora linux. We want to include this in our buildbot.
@besser82 @vigsterkr can answer questions

Here is a snippet from my working buildbot setup @karlnapf. It is building shogun 4.1.0 at the moment. It would be possible to create nightly rpms by specifying the tarball URL for the develop branch below.
fedoraRPMFactory = util.BuildFactory()

fedoraRPMFactory.addStep(steps.Git(repourl='git://pkgs.fedoraproject.org/rpms/shogun.git', branch='master', mode='incremental', submodules=True, progress=True, retryFetch=True))
fedoraRPMFactory.addStep(steps.ShellCommand(command=['wget', '-c', 'ftp://shogun-toolbox.org/shogun/releases/4.1/sources/shogun-4.1.0.tar.bz2']))
fedoraRPMFactory.addStep(steps.ShellCommand(command=['wget', '-c', 'http://pkgs.fedoraproject.org/repo/pkgs/gmock/gmock-1.7.0.zip/073b984d8798ea1594f5e44d85b20d66/gmock-1.7.0.zip']))
fedoraRPMFactory.addStep(steps.RpmBuild(specfile="shogun.spec", dist='.f23'))

c['builders'] = []
c['builders'].append(
    util.BuilderConfig(name="shogun-fedora-23_gcc-5_rpmbuild",
      workernames=["shogun-fedora-23"],
      factory=fedoraRPMFactory))

@besser82 @vigsterkr Is it possible to trigger a source download using rpmbuild instead of using the source archive specified in sources? I am getting a version mismatch, when I try to work with archives like the one below.
My setup can also download files according to https://fedoraproject.org/wiki/Packaging:SourceURL?rd=Packaging/SourceURL from GitHub.
An example URL is:
https://github.com/shogun-toolbox/shogun/archive/9a75c9509cc5188ce522f4b6e79f3ee9257f8f3b/shogun-git-9a75c95.tar.gz
Thanks, Ariane

@arianepaola and another one for you :)

@karlnapf sure :-)

@besser82 we have new updated nightly binaries now, any way we can include fedora in there?
@vigsterkr

no need


Policy and minor fixes

Summary of changes
Changes introduced in this pull request:
Reference issue to close (if applicable)

Closes
Other information and links

You most likely want Policy::mainnet and Policy::calibnet to live in fil_actors_runtime_v10.


Add FHIR sink kamelet

Please consider adding a FHIR sink Kamelet to the catalog.

I'm testing against a docker instance of the Microsoft FHIR server: https://github.com/microsoft/fhir-server using the camel command line and an integration yaml-file test-integration-xml.yaml.txt.

Thanks for the information

I'll take care of fixing the needed bits.

Thanks a bunch. Contributions are always welcome!


[OTHER] Taipy-Gui Partial Views with MVC Pattern

What would you like to share or ask?
I am trying to implememt a Taipy Gui app using the Model View Controller pattern.
In my simple app I have a Class,  MyView that creates a Partial Page() which attmpts to render a plotly Chart.
The chart is data-bound to a Class level variable (agg).  When the application starts, MyView is engaged and renders some text but the chart is blank.  I am getting warnings about the scope of the data bound variable agg.

Warning 1: Variable 'agg' is not available in either the 'main' or 'main' modules.
Warning 2: Variable 'agg' is not defined (in expression '{agg}'):

Plese see the attached zip file with the sample code.
Thank you.

[taipy_data_binding.zip](https://github.com/user-attachments/files/17154968/taipy_data_binding.zip)
Code of Conduct

[X] I have checked the existing issues.
[ ] I am willing to work on this issue (optional)

Thanks for creating the issue. I will have a look at it and come back later to you

Hello maintainers, I am willing to work on this issue. Can I get this issue assigned to me?

Hi @jrobinAV  can you please assign this issue to me? I'd like to work on it

Thank you, I will be sure to look into it and if I can not figure out I will tag you and you can assign the task to @someshfengde then.

@jrobinAV please assign this issue

@eric-tsibertzopoulos @jrobinAV bro,I think there is syntax issue and that is causing that error.
In create_page method we don't have agg defined and pateTitle is global variable hence it didn't throw any error.
However agg is class level variable and we must use if like this right self.agg
Try this and let me know if it still error's out

@eric-tsibertzopoulos @jrobinAV I think there is syntax issue and that is causing that error. In create_page method we don't have agg defined and pateTitle is global variable hence it didn't throw any error. However agg is class level variable and we must use if like this right self.agg Try this and let me know if it still error's out

I tried self.agg where tgb.Chart is called but it still cannot find the class variable, and it searches in the main.

@eric-tsibertzopoulos @jrobinAV I think there is syntax issue and that is causing that error. In create_page method we don't have agg defined and pateTitle is global variable hence it didn't throw any error. However agg is class level variable and we must use if like this right self.agg Try this and let me know if it still error's out

I tried self.agg where tgb.Chart is called but it still cannot find the class variable, and it searches in the main.

Just add f before like this f"{self.agg}"


xmr-stak is broken

Works with neither custom config nor without one because of xmr-stak-start's interactive configuration.
Pinging @fpletz

Maybe the version bump in #41506 helps.


ConcurrentStream: issues with Send and Sync bounds

There appears to be some invariance introduced by the IntoConcurrentStream and Map implementation that confuses the compiler for the Send and Sync autotraits
The following:
use futures_concurrency::concurrent_stream::{ConcurrentStream, IntoConcurrentStream};

fn assert_value_send_sync<T: Send + Sync>(_v: &T) {}

async fn iterative_method(context: &str) -> Vec<String> {
    let vec: Vec<u32> = Vec::new();
    let mut acc = Vec::new();
    for item in vec {
        acc.push(handle_item(&item, &context).await);
    }
    acc
}

async fn concurrent_method(context: &str) -> Vec<String> {
    let vec: Vec<u32> = Vec::new();
    vec.into_co_stream()
        .map(|d| async move { handle_item(&d, &*context).await })
        .collect()
        .await
}

async fn handle_item(item: &u32, context: &str) -> String {
    format!("{context}: {item}")
}

fn main() {
    let context = String::new();
    let iterative = async {
        iterative_method(&context).await;
    };
    assert_value_send_sync(&iterative);

    let concurrent = async {
        concurrent_method(&context).await;
    };
    assert_value_send_sync(&concurrent);
}

fails with the error:
rror[E0308]: mismatched types
  --> src/main.rs:36:5
   |
17 |         .map(|d| async move { handle_item(&d, &*context).await })
   |                  ----------
   |                  |
   |                  the expected `async` block
   |                  the found `async` block
...
36 |     assert_value_send_sync(&concurrent);
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ one type is more general than the other
   |
   = note: expected `async` block `{async block@src/main.rs:17:18: 17:28}`
              found `async` block `{async block@src/main.rs:17:18: 17:28}`
   = note: no two async blocks, even if identical, have the same type
   = help: consider pinning your async block and casting it to a trait object
note: the lifetime requirement is introduced here
  --> src/main.rs:3:30
   |
3  | fn assert_value_send_sync<T: Send + Sync>(_v: &T) {}
   |                              ^^^^

error[E0308]: mismatched types
  --> src/main.rs:36:5
   |
17 |         .map(|d| async move { handle_item(&d, &*context).await })
   |                  ----------
   |                  |
   |                  the expected `async` block
   |                  the found `async` block
...
36 |     assert_value_send_sync(&concurrent);
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ one type is more general than the other
   |
   = note: expected `async` block `{async block@src/main.rs:17:18: 17:28}`
              found `async` block `{async block@src/main.rs:17:18: 17:28}`
   = note: no two async blocks, even if identical, have the same type
   = help: consider pinning your async block and casting it to a trait object
note: the lifetime requirement is introduced here
  --> src/main.rs:3:37
   |
3  | fn assert_value_send_sync<T: Send + Sync>(_v: &T) {}
   |                                     ^^^^

For more information about this error, try `rustc --explain E0308`.
error: could not compile `future-concurrency-repro` (bin "future-concurrency-repro") due to 2 previous errors

I can't make a minimal reproducer, but I first encountered this error message, which I think it's the same issue. To me this suggests this might even be a bug in rustc. Even if it isn't a bug, the error message makes no sense and should be fixed.
error: implementation of `Send` is not general enough
   --> src/main.rs:348:34
    |
348 |         .route("/dashboard/:id", post(dashboard_post))
    |                                  ^^^^^^^^^^^^^^^^^^^^ implementation of `Send` is not general enough
    |
    = note: `Send` would have to be implemented for the type `&str`
    = note: ...but `Send` is actually implemented for the type `&'0 str`, for some specific lifetime `'0`

Thanks for raising this! Yeah having a minimal reproducer for this would be helpful. I'm also a little short on time so diving into this is a little tricky right now for me too.
Minimizing this test case would actually be a really good contribution if someone wants to make one!

I'm working on the pin violation first (#188), but here is a minimized test if anyone wants to take a look
fn assert_value_is_send_sync<T: Send + Sync>(_v: &T) {}

async fn concurrent_method(ctx: &str) -> Vec<String> {
    let vec: Vec<u32> = Vec::new();
    vec.into_co_stream()
        .map(|d| async move { a(&d, ctx).await })
        .collect()
        .await
}

async fn a(i: &u32, c: &str) -> String {
    format!("{c}: {i}")
}

assert_value_is_send_sync(&concurrent_method("asd"));

changing the map combinator to take a for<'a> F: Fn(Self::Item) -> Fut + 'a (since each call to the closure gets a new loan until the closure's future is completed) fixes the first issue of the bounds, but the next problem is the classic that ctx may not live long enough


Support creation of memory maps

Memory maps are very useful for giving an overview of a computer system.  One system may have multiple maps (such as a multi-core system, an 8051-like system, or a system with multiple buses).
Memory maps are similar to reg objects turned on their side with non-uniform spacing.  Other packages have abused reg-like constructs to give satisfactory memory maps (e.g. http://www.martin-demling.de/2011/06/memory-maps-in-latex-using-the-bytefield-package/).
It would be nice for Wavedrom to support generation of memory maps.

It is an interesting idea. wavedrom uses bit-filed rendering from this package: https://github.com/drom/bitfield , where related issues have to be filed.


[Feature] search issues when written in commit message

After setting the issue rules, you can link to the mentioned issue in commit. Can I search for cited issues in the Submit Message Panel and display links? This allows you to check the issues mentioned before committing.

Do you mean the autocomplete feature?

I think it is similar to autocomplete.
If not work like this, it can open the issue link before confirm the commit.(Just like the issue in commit history)


Panel Styling

Is there a way to style the panel? Few of the styling options should be exposed to parent elements

Fonts/size
Selected date background color
Selected date background radius
Hover state for both selected/unselected dates

We can expose more css mixins for customization, I'll forward so this can be prioritized.
In the meantime we're always happy to take on pull requests ;)
The last three options would probably be css mixins in px-calendar-picker

FYI the second one will have been exposed as a style variable in the theming effort currently underway. I'm not sure how much beyond colors we plan to expose as mixins, as things will start to diverge and look less-and-less like Predix UI components.

The px-calendar-picker API has been updated with the style variables for the date backgrounds (normal, hover, selected, etc), which are inherited by the px-datetime-range-panel. Here's a CodePen showing how to use them (wrap in a custom-style block, either use a selector that targets your component or :root to select all in the document) - http://codepen.io/randyaskin/pen/peyPWW?editors=1000


Network interface userspace access

Add new functions that can be used to add/lookup/remove IP address from the network interface when the application is running in userspace context. These functions are only available in userspace if CONFIG_NET_IF_USERSPACE_ACCESS is enabled.

Inconsistent naming of some functions is pointed by CI.
Beyond that, I'd suggest to explicitly mention in docstrings that interface index is 1-based (that's what we standardized on, right?). And even beyond that, I wonder if we should model such functions based on Linux' API (which would be based on classical BSD Unix API, even if this API is not mandated by POSIX).

I wonder if we should model such functions based on Linux' API (which would be based on classical BSD Unix API, even if this API is not mandated by POSIX).

What Linux APIs you are referring to?

And even beyond that, I wonder if we should model such functions based on Linux' API (which would be based on classical BSD Unix API

Well, d'oh, that appears to be rather bloated and not directly fitting Zephyr model:
http://man7.org/linux/man-pages/man3/getifaddrs.3.html
http://man7.org/linux/man-pages/man3/if_nametoindex.3.html
Well, I'd still spend more time looking if something can be made "more consistent" with Linux ;-).

The functions here can be used as a base if we want to add some BSD versions later.

Updated according to comments.

recheck

Rebased against latest upstream.

fixed unit tests
added IPv4 netmask and gateway set functions so that they can be called from userspace

Rebased against latest master.


Test Demo using data from WW R package

This PR does the following:

[X] It introduces the datasets submodule that includes test data generated by the WW team (see here)
[X] It includes a test asserting that the wastewater data is properly loaded. It uses polars to load the data.
- [ ] It uses HospitalizationsModel to fit the data and compares it with the estimates obtained from the R package.
[X] It adds a demo using a polars dataset (with the WW data).
[X] Adds an example creating a weekday effect.

Part of the PR initially wanted to deal with adding a test comparing the results of the WW hospitalization model in R. Still, the plans changed as the number of codebase modifications grew substantially. Things that need to be addressed during the next sprint:

Check the initialization of the model: The first half of NUTS estimated hospitalizations doesn't cover the data properly:

Add Rt with damping effect (see #45).
Improve the current implementation of the weekday effect: This version of the package has only a toy example (see #14).
Implement the latent infections with feedback (see #9).

cc @dylanhmorris, @SamuelBrand1

I'm holding making progress on this one until #60 is merged.

@dylanhmorris and @AFg6K7h4fhy2, this PR is ready for review. The only problem is a test that checks the Model.plot_posterior function is able to reproduce an image. I had the good intention to check reproducibility (relevant to https://github.com/CDCgov/multisignal-epi-inference/issues/81#issuecomment-2057729045,) but the test fails. I'm not sure why. Any ideas?

Some context: @gvegayon and I just re-ran with the
\log \mathcal{R}_t - \log \mathcal{R}_{t-1} \sim N(0., \sigma)

$\sigma$ value set at $\sigma = 0.1$ (large!) as opposed to $ \sigma = 0.025$, and that repairs a chunk of the posterior predictive fit; as expected by @dylanhmorris .
Obviously, that can't fix the whole problem because of how the infection -> hosp obs. delay works.

OK, @dylanhmorris, this is ready for review.


ADD: Adding colormaps for cmweather

Syncing the fork and restarting testing.

@mgrover1 this should be ready for review now.


feat: break apart codebase into modules

This PR closes #104 with some modifications to how the files were broken apart.
Overview
One function per file felt a little too shallow, so I broke things apart three major modules–customizers, overrides, and utilities–and also moved everything to src/:
src
├── customizers
│  ├── babel.js
│  ├── index.js
│  └── webpack.js
├── index.js
├── overrides.js
└── utilities.js

customizers
These are all the functions that actually modify the config files. They're currently grouped by webpack and babel, which may not be entirely accurate, but I don't want to break this down anymore without more thought and discussion.
Could eventually be split down even more into enablers that actually enable functionality and features and customizers that simply modify existing configuration. Or something. Not sure it really even matters.
overrides
This is just override and overrideDevServer. They felt special enough to house in their own file.
utilities
Currently just getBabelLoader. Should eventually have more functions that enable consumers to build their own plugins.
src/
I went ahead and moved everything over to src/ in preparation for #113.

I need to find some people that have bandwidth to check out PRs. I'll ask some co-workers if they can assist for the time being.
Since this is just re-arranging files, gonna merge and keep moving.


template : add transaction arangodb

Codecov Report

Merging #22 (04c2ade) into master (6ded12f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #22   +/-   ##
=======================================
  Coverage   23.92%   23.92%
=======================================
  Files          41       41
  Lines        2136     2136
=======================================
  Hits          511      511
  Misses       1604     1604
  Partials       21       21

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 6ded12f...04c2ade. Read the comment docs.


Fixing bug with $ref type checking

JSON-schema objects defined as { $ref: "#/definitions/objectid" } were not being turned into mongoose properties with a type mongoose.Schema.Types.ObjectId due to a conditional bug.
This has been fixed, although I have not provided an additional test for the issue.

Should now be okay to merge this in if you get a chance!


wip -- not for merge

if this works, push the updated forks to scalacommunitybuild
instead of merging this

test run: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1319/consoleFull

disabled coursier in scalameta, trying again: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1320/consoleFull

disabled scalamock's new Scala.js support. updated comments on forked projects to include date fork was refreshed. try again: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1321/consoleFull

huh — here's a new one, that run got wedged at:
[scalameta] running git ls-files --others --exclude-standard in /home/jenkins/workspace/scala-2.12.x-integrate-community-build/target-0.9.7-RC1/project-builds/scalameta-269d65971ddc6b917639b963fba32d6b02dbb59c/.

never seen that before. aborted it, trying again at https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1322/consoleFull

hmm, maybe this isn't just a transient thing? I'll have to come back to it

one more, just testing scalameta only so it finishes faster: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1330/consoleFull

try again after merging ScalaCheck fix onto our branch: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1334/consoleFull (404 til Jenkins unstraps his roller skates)

the scalameta hang is reproducible running locally:
[scalameta] running git rev-list HEAD v1.0.0 --count in /Users/tisue/community.213/target-0.9.7-RC1/project-builds/scalameta-ad236c3ba23899052c3c154e2d934d4a61ba2410/.
[scalameta] running git rev-parse HEAD in /Users/tisue/community.213/target-0.9.7-RC1/project-builds/scalameta-ad236c3ba23899052c3c154e2d934d4a61ba2410/.

debugging locally as per https://typesafehub.github.io/dbuild/0.9.5/introduction.html#what-if-the-build-fails:
./dbuild-0.9.7-RC1/bin/dbuild checkout \
  a1f7259505ca37fa9554f0c84edceebf0cf9f90f \
  scalameta newdir
newdir/.dbuild/start

also reproduces the hang:
running git rev-list HEAD v1.0.0 --count in /Users/tisue/community.213/newdir/.
running git rev-parse HEAD in /Users/tisue/community.213/newdir/.
running git ls-files --others --exclude-standard in /Users/tisue/community.213/newdir/.

the relevant commit in the scalameta repo is https://github.com/scalameta/scalameta/commit/f4ca319c05c292e2bc7a2de7308c43fed9224eab

ha, so adding .dbuild/ to .gitignore makes the problem go away, by reducing the amount of output from git ls-files --others --exclude-standard . from a few thousand lines to just a handful
why having a few thousand lines of output would cause a hang, I don't know. os.scala is calling Runtime#exec itself and doing its own I/O, maybe that code is buggy whenever the process outputs something long? /cc @xeno-by
but anyway I pushed the .gitignore change to my fork. we're already forked because of bintray, so having a second small change in the fork doesn't hurt.

in my local test scalameta passed, but scalafix failed, some difference between org.scalamacros and org.scalameta (I didn't keep the error)
I've queued up a similar run here: https://scala-ci.typesafe.com/job/scala-2.12.x-integrate-community-build/1340/consoleFull (404 til Jenkins sinks the eleven ball in the corner pocket). if only scalafix fails I think we can declare victory and deal with that one failure separately

@SethTisue Thanks for figuring that out! I've never encountered anything like that before.

latest results
[info] >>> The dbuild result is------------: FAILED (failed: scalafix, scalamock)

scalamock is also a leaf, so I'm to move forward with this.

I pushed the updated forks to the scalacommunitybuild org, and here in this repo I pushed c6f39df82eec0b6e93f9120406ec277b3be7e777 which has the necessary changes here


What is the license?

What license are you sharing this code under? Can you add a LICENSE file to the repo to make it explicit?

Oops.  I've added the license.
As with all of Conjur's open source code, it's released under the MIT license.

Thanks!


DataContainer to have size, min, max methods

def size(self):
     return self.as_array().size

min and max exist. Needs to remove these lines
Add size.

closed by #503


Worker termination

This addresses #117.
Update: It also fixes #127.

Closing in favour of https://github.com/GoogleChromeLabs/squoosh/pull/198


Adding script to dump tweets from a Twitter user

Summary
As requested by #3, this PR adds support to get the tweets of a user from the social network Twitter. The first script added downloads the last 3240 tweets from the user selected.
Details and comments
We can add more scripts and tools to retrieve data from Twitter or other sources to feed the neural networks.

The Travis-CI PR check fails because the master branch does not have a folder called test 🤷♂

Travis seems to be working properly now in the case of PRs 🙂

Reviewing the travis output I think that something went wrong with the condicional:
$ if (( "${TRAVIS_PULL_REQUEST}" = "false" )); then
    git pull --rebase #resolve conflicts here
fi

This command generates the following error:
/home/travis/.travis/job_stages: line 98: ((: 5 = false : attempted assignment to non-variable (error token is "= false ")
I think the problem is with the comparison symbol. = is an assignment.  I change it for "==" and now, if I not wrong, it has to work properly.

Sure, it seems good to me!


How to download pretrained_ckpt="/path/to/the/base/model.pt" ?

Hi @HuichiZhou, thank you for trying out our code.
We just uploaded a script that converts our base model from Huggingface hub to a local pytorch checkpoint. Please check out this section in README for more details.
Thank you for your feedback!

Hi @HuichiZhou, thank you for trying out our code.
We just uploaded a script that converts our base model from Huggingface hub to a local pytorch checkpoint. Please check out this commit and this section in README for more details.
Thank you for your feedback!

Thanks!


feat: add ESM support for default named exports

ESM import with direct access to CommonJS files is still not supported.
Changelog:

Fix CommonJS Set export collision
Fix missing *Vector exports
Fix missing *Heap exports

TODO:

Changelog entry
Document import usage

I think the CommonJS export for set ops is not correct and will collide with Set.

@jerome-benoit I like your PR but I will need some kind of proof it does not break backwards compatibility whatsoever. I attempted such a change on another library of mine lately, it broke a lot of things and people were angry at me (which they should not feel entitled to, but this is how the Internet works it seems). What's more, this library is very heavily depended upon.
An issue that arised for instance was that the obliterator library is not ESM-first either and that some package managers seem to consider ESM-first as "viral" where all the dependency chain must abide or break.
It also broke some older TS for instance.

I think the CommonJS export for set ops is not correct and will collide with Set.

What do you mean?

I think the CommonJS export for set ops is not correct and will collide with Set.

What do you mean?

module.exports = {
  ...
  Set: require('./set.js'),
  ...
}

export Set symbol to access the named exports in set.js.  Are you sure it will just extend the node.js Set without causing any issue in module using both?

@jerome-benoit I like your PR but I will need some kind of proof it does not break backwards compatibility whatsoever. I attempted such a change on another library of mine lately, it broke a lot of things and people were angry at me (which they should not feel entitled to, but this is how the Internet works it seems). What's more, this library is very heavily depended upon.
An issue that arised for instance was that the obliterator library is not ESM-first either and that some package managers seem to consider ESM-first as "viral" where all the dependency chain must abide or break.
It also broke some older TS for instance.

Did you it as part of a breaking changes version bump with some pre-releases?
That PR is meant for such a release cycle since it's a breaking change.
Testing CommonJS, ESM default exports files will be added in that PR, but I prefer to early show the code to project maintainers. TS tests are overkill.
The changes done are the only way to achieve node.js support for CommonJS and ESM without breaking backward compatibility.

top-level package.json main and types => node.js < 16 or node.js >= 16 and TS with Node10 module resolution are searching for it without "type": "module" and works.
top-level package.json exports object => node.js >= 16 and TS with Node16 module resolution are searching for it with "type": "module" and will behave correctly as long as types, require and import are properly set.

Basically mnemonist miss the second point and import pointing to ESM wrapper. That's why I have issue after switching a TS repo using it to ESM and Node16 module resolution by default.
Anyhow, at some points, you will have to drop support for unsupported node.js version in your librairies and make a major version bump.

Hello again @jerome-benoit

Did you do it as part of a breaking changes version bump with some pre-releases?

Of course. But some people just want to watch the world burn regarding their way to handle version dependencies :).
Regarding this PR, this would be part of v0.40.0 of course.

export Set symbol to access the named exports in set.js. Are you sure it will just extend the node.js Set without causing any issue in module using both?

This seems to be an error on my end. The other endpoint correctly exports as lowercased set, which is of course better. Since we are breaking with this release, I vouch to fix this error in the common js endpoint.

Testing CommonJS, ESM default exports files will be added in that PR, but I prefer to early show the code to project maintainers. TS tests are overkill.

I am willing to go forward with this, so if you know how to add those tests and are willing to do so, let's proceed?
Regarding ESM-first virality, can you confirm that the fact that obliterator does not support ESM will not be an issue here?
Regarding the fact that single files will not be able to be imported using ESM, I guess this is not an issue since tree-shaking should now be sufficiently performant (it was not the case when this library was first developped). Which means the documentation will probably need to be updated wrt imports (which is totally fine with me).

Testing CommonJS, ESM default exports files will be added in that PR, but I prefer to early show the code to project maintainers. TS tests are overkill.

I am willing to go forward with this, so if you know how to add those tests and are willing to do so, let's proceed?

I'm a bit busy lately, but feel free to code on that branch until I'm able to finish the PR.

Regarding ESM-first virality, can you confirm that the fact that obliterator does not support ESM will not be an issue here?

As long as you do not switch that repo to ESM ("type": "module" in package.json), no.

Regarding the fact that single files will not be able to be imported using ESM, I guess this is not an issue since tree-shaking should now be sufficiently performant (it was not the case when this library was first developped). Which means the documentation will probably need to be updated wrt imports (which is totally fine with me).

ESM module can consume CommonJS most of the time but some configurations will not work, like enforcing Node16 module resolution.

Testing CommonJS, ESM default exports files will be added in that PR, but I prefer to early show the code to project maintainers. TS tests are overkill.

I am willing to go forward with this, so if you know how to add those tests and are willing to do so, let's proceed?

I'm a bit busy lately, but feel free to code on that branch until I'm able to finish the PR.

@Yomguithereal: The PR is now an mergeable state. The TODO bullet points are targeted to other PRs.

Thanks @jerome-benoit, I will review your PR and probably merge it as-is in the near future. I am a bit overwhelmed by work currently so don't worry if I disappear here and then.

@Yomguithereal: is it possible to schedule a 0.40.0-0 prerelease with that PR in?
It's not time consuming for a maintainer and harmless for libraries end-users.

@jerome-benoit I have committed a merge with current master. Will merge your PR soon and publish a release candidate on npm. Should be in the afternoon, or beginning of next week.

@jerome-benoit v0.40.0-rc1 is live on npm. I am wondering whether test/exports/package-lock.json should be committed to the repo or not.

@jerome-benoit v0.40.0-rc1 is live on npm.

Will test it soon to see if now bundlers works as intended in an ESM project with mnemonist as an external dep.

I am wondering whether test/exports/package-lock.json should be committed to the repo or not.

First I've not commited it. Then I thought having a strict versioning for deps in test would provide better reproducibility. But I do not think minor or patch version only updates done under the hood would harm. Fixing deps for non major version and a testing purpose is debatable anyways.

@jerome-benoit v0.40.0-rc1 is live on npm.

Will test it soon to see if now bundlers and node works as intended in an ESM project with mnemonist as an external dep.

I am wondering whether test/exports/package-lock.json should be committed to the repo or not.

First I've not commited it. Then I thought having a strict versioning for deps in test would provide better reproducibility. But I do not think minor or patch version only updates done under the hood would harm. Fixing deps for non major version and a testing purpose is debatable anyways.

@jerome-benoit v0.40.0-rc1 is live on npm.

Will test it soon to see if now bundlers works as intended in an ESM project with mnemonist as an external dep.

Tested successfully on various repos using mnemonist.
Maybe you can announce the prerelease on GitHub to give it more visibility and testing before promoting the rc(s) as final.

Maybe you can announce the prerelease on GitHub to give it more visibility and testing before promoting the rc(s) as final.

Would you do this as a tag+issue? I am not entirely convinced a lot of people use mnemonist directly but rather as part of a dependency to their dependencies. I can try tweeting/tooting etc. also.

Maybe you can announce the prerelease on GitHub to give it more visibility and testing before promoting the rc(s) as final.

Would you do this as a tag+issue?

An issue? GitHub allows to create a release flagged as a prerelease associated with a git tag. That will work if the repo GitHub actions does not include a releasing workflow based on tag addition since the npm package is already pushed on the registry. I do not know how you add a new release on GitHub, but that's the same except with the prerelease checkbox on.

I am not entirely convinced a lot of people use mnemonist directly but rather as part of a dependency to their dependencies. I can try tweeting/tooting etc. also.

Sure, but I think having a link to the GitHub prerelease announcement with the changelog will help you to communicate a bit on it.


Add grating as parameter for lamp selection

Until now I've been assuming that all the night only one setup will be used, and I was completely wrong.
Working on it./

Added criterium for post extraction decisions.
Special attention must be put in mode 0, when a single lamp is assigned to the whole night. Is very unlikely that a single spectroscopic configuration will be used in  the whole night. For instance, changing GRATINGs will change everything and so on. Need to identify those conditions and program it in the organization of the night.
For now I have identified the following parameters to be compared since the will affect the wavelength solution:

Blue Camera

CCDSUM
GRATING
FILTER
FILTER2
SLIT
PARAM18 (Serial Binning)
PARAM22 (Parallel Binning)
CAM_ANG
GRT_ANG

Red Camera

ROI
GRATING
FILTER
FILTER2
SLIT
INSTCONF
WAVMODE
CAM_ANG
GRT_ANG

At the moment it does not mix lamps and science targets with different gratings but it only works with one grating. In the first release there will not be a multi-configuration capability.

Outdated issue


Fix invalid CM transition order

Checklist

Branch

[x] Commit sequence broadly makes sense
[x] Commits have useful messages
[ ] New tests are added if needed and existing tests are updated
[ ] If this branch changes Consensus and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If this branch changes Network and has any consequences for downstream repositories or end users, said changes must be documented in interface-CHANGELOG.md
[ ] If serialization changes, user-facing consequences (e.g. replay from genesis) are confirmed to be intentional.

Pull Request

[x] Self-reviewed the diff
[x] Useful pull request description at least containing the following information:

What does this PR change?
Why these changes were needed?
How does this affect downstream repositories and/or end-users?
Which ticket does this PR close (if any)? If it does, is it linked?

[x] Reviewer requested

Description
This PR fixes #3793. The fix consists of fixing the Connection Manager finally handler to log the right transition if the connection is only in ReserverdOutboundSt. More details on the issue page.

bors merge


Linux CentOS render to It fails

HP Z820 with Nvidia Quadro 5000 (properly installed)
CentOS7
Render to Blender works fine
Render to It fails (IPR or file) - the buckets show but the image is black.

Simple file here:
http://sawe.asuscomm.com/ws/temp/
http://sawe.asuscomm.com/ws/temp/render_to_it_black_ocio_issue.blend.zip

If you need any specific additional information or have any suggestions for what I can try you can write here or to my email<EMAIL_ADDRESS>Thanks

copy of issue here: https://renderman.pixar.com/forum/showthread.php?s=&postid=211401#post211401

copy of issue here: https://renderman.pixar.com/forum/showthread.php?s=&postid=211401#post211401

Workaround:
"View/Image Color Space/RAW"
This will disable the Color Space alternatives, but the images will show and gamma/exposure respond.

Workaround continued:
It is possible preferences in It to default to RAW.
Then, if a certain gamma is desired as default (like 1.8/2.2) it is possible to set that in it.ini (SetPref itColorGamma 1.0)
must first be set in OS:
export RMS_SCRIPT_PATHS="/Users/Shared/ws/RMS/scripts"


feat: add background noise export

Description
Add noise extraction functionality to speech enhancement models. This feature allows users to obtain both enhanced speech and extracted noise signals.
Changes

Add extract_noise parameter to decode functions
Modify model processing pipeline to support noise extraction
Update ClearVoice interface to handle noise output
Keep original functionality intact for backward compatibility

Implementation Details

Added extract_noise boolean parameter (default: False)
When extract_noise=True, functions return tuple of (enhanced_audio, noise_audio)
When extract_noise=False, functions maintain original behavior
Noise is calculated as: original_signal - enhanced_signal

Testing

Tested with all speech enhancement models:

FRCRN_SE_16K
MossFormer2_SE_48K
MossFormerGAN_SE_16K

Verified output quality and signal consistency

Can you open a new branch for this? Thanks.


Update machine-learning-r-csharp-binomial-distribution.md

edit for freshness

Hi @jaymathe, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (jaymathe). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Added Fenwick Tree (Binary Indexed Tree) Algorithm.

📥 Pull Request
Description
Added Fenwick Tree (Binary Indexed Tree) Algorithm.
Fixes #524
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Hey @ajay-dhangar
Now check I resolved all conflicts and remove unnecessary lines.


[WIP] Azure Pipelines

The project currently uses CircleCI for CI/CD tasks and testing, and it is a paid service.
Meanwhile, Azure Pipelines can be used for free in our project (up to 10 build simultaneously) and it seems feature-rich enough.
The idea is to replace CircleCI.
Description

.azureci/ folder contains pipelines.yml - main config file and scripts that it uses to perform specific tasks.
Motivation and Context

How Has This Been Tested?


libcap: 2.70 -> 2.72

Changes:

https://sites.google.com/site/fullycapable/release-notes-for-libcap#h.oq9dsdhihxp5
https://sites.google.com/site/fullycapable/release-notes-for-libcap#h.ulglddlojmy0

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4909

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review/3032/4939


TimeoutCancellation. Cannot understand how it work

Hello, i have a very simple use case where i would like to use TimeoutCancellation but can't undestand how it exactly works.
I have two Future, and i'm running them with awaitAll. I would like to cancel one when a timeout is reached but still keep the result from the others.
I tried to use TimeoutCancellation like following but then a CancelledException is raised
        $f1 = async(function () {
            delay(10);
            echo 'F1 completed' . PHP_EOL;
        });

        $f2 = async(function () {
            delay(5);
            echo 'F2 completed' . PHP_EOL;
        });

       awaitAll([$f1, $f2], new TimeoutCancellation(7));

So, i looked into awaitAll and tried to move the TimeoutCancellation into the foreach but it seems to be ignored:
        foreach (Future::iterate([$f1, $f2]) as $index => $future) {
            try {
                $values[$index] = $future->await(new TimeoutCancellation(7));
            } catch (\Throwable $throwable) {
                $errors[$index] = $throwable;
            }
        }

So i tried to remove the Future::iterate, this seem to work but i'm not sure if this is correct:
        foreach ([$f1, $f2] as $index => $future) {
            try {
                $values[$index] = $future->await(new TimeoutCancellation(7));
            } catch (\Throwable $throwable) {
                $errors[$index] = $throwable;
            }
        }

I'm afraid to loose something not using the Future::iterate. It's possible to do what i want? Or I'm not understanding its purpose?
Any suggestion is welcome. Thank You

Maybe you should use awaitAny.

@xpader from what i can understand, awaitAny return the result of the first Future completed. I would like:

If all Future are completed i have a result for all of them.
If one or more Future exceed a timeout, i have the result only for Future completed.

What do you mean with ignored? One possible issue here is that you create a new cancellation for every await, so if your first completion takes 3 seconds, the actual timeout for the second one will be 10 seconds instead of 7 seconds.
You can fix that by reusing the cancellation, which is more efficient anyway

Hello @kelunik tnx for your reply. I dont know if i'm missing something here. I created a small test with PHPUnit. I created the TimeoutCancellation outside the loop with a timeout of 1 second, i'm expecting both of my Future go timeout and been in the error array's. But both are in the values and the test complete in 10 second.
<?php

use Amp\Future;
use Amp\TimeoutCancellation;
use PHPUnit\Framework\TestCase;
use function Amp\async;
use function Amp\delay;

class CancellationTest extends TestCase
{
    public function testCancellation(): void
    {
        echo PHP_EOL;

        $f1 = async(function () {
            delay(10);
            echo 'F1 completed' . PHP_EOL;
        });

        $f2 = async(function () {
            delay(5);
            echo 'F2 completed' . PHP_EOL;
        });

        $values = [];
        $errors = [];

        $cancellation = new TimeoutCancellation(1);
        foreach (Future::iterate([$f1, $f2]) as $index => $future) {
            try {
                $values[$index] = $future->await($cancellation);
            } catch (\Throwable $throwable) {
                $errors[$index] = $throwable;
            }
        }

        self::assertCount(2, $errors);
        self::assertCount(0, $values);
    }
}

This is my stdout:
F2 completed
F1 completed

Time: 00:10.016, Memory: 14.00 MB

I'm using version * v3.0.2 under PHP8.1

Oh, yes, indeed, it won't work that way. Future::iterate already waits for completion internally before "submitting" the futures to the iterator, so at the point of "await" the future is already completed, so the timeout has no effect anymore. So you need to indeed skip Future::iterate().

@kelunik thank you. Now i understand a bit better. I think i will try to skip Future::iterate() and use a simple array like this:
        $cancellation = new TimeoutCancellation(15);         foreach ([$f1, $f2] as $index => $future) {             try {                 $values[$index] = $future->await($cancellation);             } catch (\Throwable $throwable) {                 $errors[$index] = $throwable;             }         }
I think we can close


HOTFIX - Add a Request ID to Flask and Celery

Description

issue N/A
How Has This Been Tested?

Checklist

[ ] I have assigned myself to this PR
[ ] PR has an appropriate title: #9999 - What the thing does
[ ] PR has a detailed description, including links to specific documentation
[ ] I have added the appropriate labels to the PR.
[ ] I did not remove any parts of the template, such as checkboxes even if they are not used
[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to any documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works. Testing guidelines
[ ] I have ensured the latest main is merged into my branch and all checks are green prior to review
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] The ticket was moved into the DEV test column when I began testing this change

This was accomplished with another PR, closing.


Can not verify existing webhook

Created custom webhook:
curl -H "St2-Api-Key: MDQ2Y2FmOGExNWU1NTA3YTRmZDIwNTMxYmE2M2NkNWI3ZTcwZTMwODBkMDJmYzAwZDg5NzNiNTdiNDEwMzdiZg" https://localhost/api/v1/webhooks/st2-trigger-build -k
{"uid": "trigger:core:d7c0dde6-272d-4230-80e6-29eb1b5c2950:37a1b5f1d879c35beee4cbf61b555819", "parameters": {"url": "st2-trigger-build"}, "ref_count": 1, "name": "d7c0dde6-272d-4230-80e6-29eb1b5c2950", "pack": "core", "type": "core.st2.webhook", "id": "57915e0bc4da5f04822fb0d6", "description": null}
But then it fails;
curl -X POST https://<IP_ADDRESS>/api/v1/webhooks/st2 -trigger-build -H "St2-Api-Key : MDQ2Y2FmOGExNWU1NTA3YTRmZDIwNTMxYmE2M2NkNWI3ZTcwZTMwODBkMDJmYzAwZDg5NzNiNTdiNDEwMzdiZg" -H "Content-Type: application/json" --data '{"trigger": "core.st2.webhook", "payload": {"attribute1": "value1"}}' -k
{
"faultstring": "Unauthorized - One of Token or API key required."
} - doesn't work
The trigger seems to be fine:
st2 rule list |grep build
| default.st2-trigger-build               | default  | trigger build from gitlab                     | True    |

You have a space between "St2-Api-Key" and ":" - wonder if that is causing the problem?

Ye that was an issue user error.

Closing issue


Rename to simple 'cloudcraft'

Overview
Let's make this a root name. Need to update docs too.
Deliverables

[ ] update name
[ ] update docs

Work for this issue will begin begin on branch work-liquid-labs/cloudcraft/3.


Add optional tensor support for repeat

We need optional output tensor support for repeat op
Primary Issue #5044

@ntarafdar, this feature may be needed for compilers but removing from eltwise team.


Update Site settings “info”

Automatically generated by Netlify CMS

👷 Deploy Preview for celadon-kelpie-9766f4 processing.

Name
Link

🔨 Latest commit
d0d6847a3415e1d3b386c861267ff7b232cfce1f

🔍 Latest deploy log
https://app.netlify.com/sites/celadon-kelpie-9766f4/deploys/640866f283f0700008cf8a5f


AF_UNIX on Windows

AF_UNIX is supported on Windows now, and has some advantages over named pipes:
https://devblogs.microsoft.com/commandline/af_unix-comes-to-windows/
What are your thoughts on adding support for this to the uv_pipe_* family of functions?

Since UV_NAMED_PIPE already means "named pipe" on Windows and "unix socket" on Unix, maybe a new UV_UNIX_SOCKET flag could be used to opt-into AF_UNIX behavior on Windows?
Alternative: on Windows versions where AF_UNIX is supported, UV_NAMED_PIPE could use AF_UNIX unconditionally. But this could break applications that assume pipe names have  \\.\pipe\... format.

I think something along the lines of 1) would be best. We have uv_pipe_init_ex which. takes a flags argument so there is a place where this could be turned on.

I think the main challenge/question would be that the uv_pipe_* code currently expects to operate on a windows HANDLE object, whereas this would be a SOCKET object. So should this fall more under uv_tcp or uv_pipe? I expect it would share most of its code with uv_tcp and little with uv_pipe. On Unix, UV_NAMED_PIPE presently means {"pipe" or "fifo" or "unix socket"}. We could perhaps move the "unix socket" capabilities into the existing libuv stream socket representation (aka uv_tcp) though, which might be more cross-platform stable (due to somewhat better alignment with the underlying system APIs everywhere).
Aside: for anonymous local sockets (e.g. not with connect/bind on filesystem paths), in https://github.com/libuv/libuv/pull/1498, I am adding uv_socketpair for making local socket pairs.

That's kinda what Unix does with having most of the stuff in stream.c, right? Makes sense to do the same here IMHO.

This stale bot is obnoxious. What is the point of closing old issues just because no one addressed them ?

Windows sockets should be able to be used as file handle functions like ReadFile() and WriteFile() (https://docs.microsoft.com/en-us/windows/win32/winsock/socket-handles-2), so the existing pipe.c file can be slightly modified to use socket functions to create the handles, but otherwise be unchanged except in a few places. All named pipe filenames begin with \\.\pipe\ (or potentially another computer name in place of dot), and all unix sockets exist somewhere on the filesystem, so the logic can choose to create a pipe or socket based on the location requested.

Sorry for simply bumping the issue, but this is a deal breaker for IPC on a single host.
Having to resort to named pipes on Windows only is additional maintenance cost that I'm not sure I'm willing to pursue.
Is there any plan to bring UDS into the library during 2023?

@bnoordhuis AF_UNIX seems to be available starting from the Windows 10 April 2018 update, so I think it's impossible to take for granted it exists, unfortunately. I mean, Windows 10 machines should be up-to-date, tho one cannot be sure about it.

I think using AF_UNIX should produce a clear error on older Windows versions.
The error has to be distinguishable enough for the program to be able to fall back to using a TCP socket, for example.

Before anyone waste time into this (as I did yesterday, albeit not related to libuv), it's important to note that the blog post announcing 'AF_UNIX support' contains misleading information and is partially incorrect. The implementation seems to be incomplete and was likely abandoned shortly after the transition from WSL1 to WSL2. For instance, the 'abstract' socket address mode does not function as stated in the blog post. You can find a detailed description of the issue and its observed behavior here. Unfortunately, I encountered this problem and the GitHub Issue only after investing significant time into it 😢. Therefore, the only viable option for using AF_UNIX sockets for IPC on Windows is to utilize 'pathname' sockets that depend on the file system, which is less than ideal.

@clemenswasser

the only viable option for using AF_UNIX sockets for IPC on Windows is to utilize 'pathname' sockets that depend on the file system, which is less than ideal.

This is AFAIK already the case with libuv with macOS, which only supports classic UNIX sockets (libuv has no support for Mach Ports AFAIK), and the same goes for *BSD. I don't see a reason why supporting "classic" UDS only should be considered  acceptable on macOS/Darwin/*BSD and not on Windows, honestly.

This definitely needs to be landed because on Windows UDS beats named pipe completely in performance.

About performance, at least under ASP.NET Core gRPC use case, there's a test against it:
https://www.yanxurui.cc/posts/server/2023-11-28-benchmark-tcp-uds-namedpipe/
It seems the UDS outperforms localhost TCP and NamedPipe significantly.
cc @bnoordhuis

Reusing UV_NAMED_PIPE seems not a problem to me.

Named pipe has prefix \.\ or \?\， while UDS is an absolute local path like C:\Temp.sock, the actual one can be determined by path prefix, reusing existing parameters.

I think UDS can be supported with a conditionally at Windows 10, and simply throwing exception at Windows 7/8 if prefix is not named pipe.

We dropped Windows 8 support (#3889) so this feature request is available for anyone who wants to work on it.

Anyone working on it yet? I found modifying the existing code very challenging. No idea how to meet the requirements of libuv because the code seems very hacky.

That works, as long as it doesn't result in massive code duplication.

I find most of the IOCP code works like a charm when use socket as handle as Windows supports it natively. So I decide to reuse most of the code.
I put a WIP PR here, currently send and receive data works. I didn't touch the pipe pair code, it seems we can just leave it there and just supports
net.createConnection({ path: "D:/uds.temp" });

and
const srv = net.createServer((c) => {
    console.log(c)
})
srv.listen("D:/uds2.temp")


Webflux endpoints span name

Describe the bug
First, thanks a lot for this library it's really useful. One of the issues I ran into is the webflux WebFilter creating the HTTP server traces doesn't seem to create the spans with the correct name. It is only using the request.getMethod() to create the span name, so when viewing the trace you only see them as POST or GET instead of using the request path.
Afaik the issue is coming from the OtelHttpServerHandler, I don't know if it's a bug per se or intended like that but it makes viewing traces quite difficult
Sample
The problematic code I believe is here :
	@Override
	public Span handleReceive(HttpServerRequest request) {
		String url = request.path();
		boolean shouldSkip = !StringUtils.isEmpty(url) && this.pattern.matcher(url).matches();
		if (shouldSkip) {
			return OtelSpan.fromOtel(io.opentelemetry.api.trace.Span.getInvalid());
		}
		Context context = startSpan(request, request, request, request.method());
		return OtelSpan.fromOtel(io.opentelemetry.api.trace.Span.fromContext(context), context);
	}

Thanks a lot :)

AFAIR the startSpan is taken from OTel instrumentation so it's OTel instrumentation that sets the name cc @jkwatson

The code is passing in request.method() as the span name parameter to the startSpan call. So, that's the point at which customization should happen if you don't just want to use the request method as the name.

Ah yeah, you're right. So this is consistent with the way Brave works. If you want to customize the name you can just register a bean of HttpRequestParser type and apply your own customized name.


Fixes from demonstrations in January 2023

[x] Tick to sign-off your agreement to the Developer Certificate of Origin (DCO) 1.1

What
In this pull request I seek to make the demo runnable again.

The World Clock API is depreciated. Use a local clock instead for demo robustness.
I suspect binary evidence support was broken when agent-mode was added. I tweaked a conditional to restore support for signed binary evidence.

Why
To better evangelize Auditree I want the demo working well.
How

Update the world clock example to use Python datetime
Don't attempt to encode already-bytes data

Test
The demo is working, both the fetch step and the check step.
Unit tests are passing.
Context
Try the demo off main today to see the failures.

I'm accepting comments on this PR. I think a new test covering binary signed evidence would be a last change worth including -- it should fail off main today and pass on my branch.

Thanks for this, the change looks good from a quick eyeball.
One thing, calling out to the API was a nice part of the demo, as it shows the whole collect remote responses.
Obviously that needs to be a working API, maybe calling a GitHub api/URL for this project would be a good additional demo?

@drsm79 I've added a GitHub API example -- what do you think of using the versions API?

@drsm79 I've added a GitHub API example -- what do you think of using the versions API?

Nice, good choice.

I've added a binary signing test that now passes but fails on main.

@ksnavely perhaps we should merge #144 this first as it will fix some problems with the current CI config.

I should be good to go after you merge your PR, I can't recall if I'll need to re-push this branch after an update or not.

Yeah, there is some conflicts in there after my merge of #144


Can't use generated cassettes under Python 2 with Python 3 and vice-versa

Hello, i am currently working on the migration of my code from Python 2 to Python 3.
My problem is that when i am using the lib to use a cassette (generated under Python 2) under Python 3 i get the Error "Can't overwrite existing cassette". The same occur when i am using a cassette (generated under Python 3) under Python 2.
Right now the only solution i found is to create a cassette file which is used only when i am under Python 2 and an other cassette file that which is used only when i am under Python 3 .. this is convenient for my project..
I've already looked at the issue  [https://github.com/kevin1024/vcrpy/issues/163] that is already closed, and the related PR does not seem to fix the issue for me
Or maybe there is a solution that i missed?
vcrpy version : 2.1.0 (both Python 2 and Python 3)
thanks for your answer.

Hello and thanks for reporting this issue. I can imagine many people are tracking through the same python 2 to 3 journey this month.
Are you able to link to a toy repo that generates a python2 cassette and python3 cassette and commit those cassettes to the repo along with the code that generated it?
I only have bandwidth to act as a release manager these days, so any assistance to help the next person to be able to close out a PR is thoroughly welcomed.

I tried to reproduce issue with vcrpy 2.1.0 on Python 2.7.17 and 3.6.8 but no errors found .
More specific info on environment conf and vcrpy usage will be great facilitation here.

Python 2 is dead, closing as obsolete…


[test-triage] chip_sw_uart_smoketest_signed

Hierarchy of regression failure
Chip Level
Failure Description
UVM_ERROR @ 20013.398695 us: (chip_sw_base_vseq.sv:218) uvm_test_top.env.virtual_sequencer [uvm_test_top.env.virtual_sequencer.chip_sw_base_vseq] SW TEST TIMED OUT. STATE: SwTestStatusBooted, TIMEOUT = 20000000 ns
Steps to Reproduce
GH revision: 9c0b24ddb
util/dvsim/dvsim.py hw/top_earlgrey/dv/chip_sim_cfg.hjson -i chip_sw_uart_smoketest_signed --build-seed<PHONE_NUMBER> --fixed-seed<PHONE_NUMBER>
Tests with similar or related failures
No response

@timothytrippel
I increased the run-time for this test, but it still timed out. Sounds like it's not just due to the test timeout limit.
The one (chip_sw_uart_smoketest) without the "signed" is passing now (thanks to your recent update). Not sure if you have a clue what may cause the failure?

Thanks for adding this issue, I think #14190 should solve this once I can get it to pass CI. Stay tuned.

Note for devs. Looks like the timeout has gone but now have some bazel / fastbuild issues.
Since https://reports.opentitan.org/hw/top_earlgrey/dv/2022.08.16_16.23.56/results.html
chip_sw_uart_smoketest is passing but
chip_sw_uart_smoketest_signed is still not passing.
Error observed between 12 and 16 August
fastbuild/bin/sw/device/tests/uart_smoketest_prog_sim_dv.test_key_0.signed.elf': No such file or directory
  make: *** [/workspace/mnt/repo_top/hw/dv/tools/dvsim/sim.mk:73: sw_build] Error 1

So now it may be a new type of issue
UVM_FATAL @   0.965959 us: (mem_bkdr_util.sv:480) [mem_bkdr_util[Rom]] file rom_sim_dv.39.scr.vmem could not be opened for r mode

Yeah, I looked into this, it's an issue with how we query Bazel opentitan_functest data deps and copy them to the run dir here. Basically since the UART smoketest BUILD target is used for both unsigned and signed tests, and the BUILD target doesn't specify which ROM to use, it defaults to using the test ROM as a data dep, and it doesn't get copied over to the run_dir. Working on a fix for this now.

#14382 should fix this.

#14382 finally fixes this.

Thanks @timothytrippel


Auth library serverless example is misleading in the documentation for cloud functions authentication

The cloud functions documentation  uses the nodejs auth library serverless example to demonstrate how to authenticate when invoking a function with an IdToken.
Unfortunately this causes a lot of confusion because the example is not interchangeable.
Cloud functions audience requires the function name to be present when generating the token, but the example uses only the host name, which is only valid for cloud run.
Every single week I provide support to engineers struggling to authenticate with cloud functions and the I can guarantee majority of the issues is because they are using this misleading example, causing a lot of pain for them (and for me 😆).
To make things worse, some of them are adamant to believe us when we say the documentation is wrong.
The example below:
  // Example: https://my-cloud-run-service.run.app/
  const targetAudience = 'https://TARGET_HOSTNAME/';  // <-- wrong example
  const {GoogleAuth} = require('google-auth-library');
  const auth = new GoogleAuth();

  async function request() {
    console.info(`request ${url} with target audience ${targetAudience}`);
    const client = await auth.getIdTokenClient(targetAudience);
    const res = await client.request({url});
    console.info(res.data);
  }

should be as follow for cloud functions
  // Example: https://project-region-projectid.cloudfunctions.net/myFunction
  const targetAudience = 'https://TARGET_HOSTNAME/function-name';  // <-- right example for cloud functions
  const {GoogleAuth} = require('google-auth-library');
  const auth = new GoogleAuth();

  async function request() {
    console.info(`request ${url} with target audience ${targetAudience}`);
    const client = await auth.getIdTokenClient(targetAudience);
    const res = await client.request({url});
    console.info(res.data);
  }

That was quick. Thanks for the quick resolution.
One last question, is there anything needed to update the docs?
I see it still showing the old example.

The docs page is now updated. Thanks!


[HUDI-5966] Hotfix argments in CreateHoodieTableCommand::createHiveDataSourceTable

Change Logs
Describe context and summary for this change. Highlight if any code was copied.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level (write none, low medium or high below)
If medium or high, explain what verification was done to mitigate the risks.
Documentation Update
Describe any necessary documentation update if there is any new feature, config, or user-facing change

The config description must be updated if new configs are added or the default value of the configs are changed
Any new feature or user-facing change requires updating the Hudi website. Please create a Jira ticket, attach the
ticket number here and follow the instruction to make
changes to the website.

Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@danny0405 have a review please

@hudi-bot run azure

https://github.com/apache/hudi/actions/runs/4491760778/jobs/7913196270?pr=8255
ok，but need more error detail about it，the error seems not relate to the pr @codope


Unable to enable regional STS using for Client Credential flow.

Package Name:
@azure/identity
Package Version:
~3.1.3
Operating system:
[X] nodejs

version: 16.17.1

[ ] browser

name/version:

[X] typescript

version: 3.9.9

Is the bug related to documentation in

[ ] README.md
[ ] source code documentation
[ ] SDK API docs on https://docs.microsoft.com

Describe the bug
I've been looking into enabling regional sts for the client credential flow using the @azure/identity node package but I can't see how to do it using the documentation.  Looking through the code a lot of functionality that looks like it would enable regional sts seems to be commented out. I couldn't find any relevant configuration in either the constructor for the credential or the getToken() method.
I've also attempted to do this by setting the AZURE_REGIONAL_AUTHORITY_NAME environment variable but this has not worked for a majority of the requests (though has worked for about 20%).
This is an S360 requirement for which our services are currently out of SLA.
To Reproduce
N/A
Expected behavior
A 100% regional sts adoption rate for all requests flagged by S360 and a resolution of the S360 item.
Screenshots
Additional context

Hi @niallb96, which credential type are you using?
@KarishmaGhiya I'm not sure the history here, all I found was us removing this support two years ago: https://github.com/Azure/azure-sdk-for-js/pull/18026 -- is this still a supported scenario?

Hello @niallb96 , we do not support the env name AZURE_REGIONAL_AUTHORITY_NAME anymore.

Hi @KarishmaGhiya, sorry for the delay responding I was oof.  Would you mind clarifying exactly what additional information you require?  This has been flagged for two of our applications on S360, so I want to enable it for all requests necessary to resolve the S360 item.  They are both Node.js, from my understanding for node this feature is only available for the client credential flow so I need all requests using that flow to use regional STS.  There are a number of requests and scenarios that are using the credential flow.  I didn't realise that AZURE_REGIONAL_AUTHORITY_NAME was not supported anymore, I was going off this documentation: https://review.learn.microsoft.com/en-us/identity/microsoft-identity-platform/msal-net-regional-adoption?branch=main#enable-msal--microsoft-identity-web-to-use-regional-ests-endpoint.  Since this env name isn't supported, mind telling me an alternative approach to resolve this S360 item?  Thanks!

Hi @niallb96 My Bad. We still do support and accept the env name you have tried, we had removed the setting from the public API surface. Can you tell me in what scenarios (and what credentials) has it not worked for you, I'd like to repro it on my end and check.

Hi Karishma,  sorry for the delay responding.  Part of my problem investigating this is that I am struggling to figure out exactly what is unique about the requests that are failing.  A lot of the failing requests have the Resource Display Name: Microsoft Graph.  We have tokens of types ClientCertificateCredential and ClientSecretCredential and we define tenant ids, client ids and certificate paths when constructing them.  sendCertificateChain is set to true for ClientCertificateCredential  and the authorityHost is set based on the cloud.  I have tables for failing tenant ids, client ips and resource ids but have been struggling to use these to find any useful information on what is happening with these requests to make them fail.  Please let me know what specific configuration details you need or if you're available if you would be willing to hop on a call to investigate this together.  Thanks, Niall

@niallb96 Do you have any useful information from the logs? You can enable verbose logging on your end to get more information on the failing requests. I'd be happy to hop on a call with you.


Fix to add missing ports for sql.template

The template for existing VPC's is missing opening ports 49152-65535. This change is to add that in otherwise WFCS fails to be able to cluster nodes to each other.
This seems to have been removed in #2 oddly enough and is still present in the full VPC build:
https://github.com/aws-quickstart/quickstart-microsoft-sql/blob/f00f82868ee8397e81aa98fb9e197a63b3868252/templates/Template_1_SQL_AlwaysOn.template#L2199-L2214
https://github.com/aws-quickstart/quickstart-microsoft-sql/blob/f00f82868ee8397e81aa98fb9e197a63b3868252/templates/Template_1_SQL_AlwaysOn.template#L2247-L2262
Either this modification is required or the documentation needs to reference this as a prerequisite for the provided DomainMemberSGID security group

There is conflicts on sql.template, can you resolve that.

@virtlima I have resolved the conflicts and changes are committed.


docs/fix coverage url

Removes parentheses around link for coverage url

Coverage remained the same at 100.0% when pulling d9f5836b10cddb7ac83965b9273c15a15411a592 on docs/fix-coverage-url into 26e15606906456494bc1d6e8018e2fc07ed575f0 on main.


Cleanup Build Chain

Made use of Rollup's multiple targets
Add a module entry (dist/mitt.es.js)
No need to mkdirp dist before build

Any size difference? I had thought we were outputting it, but I don't see a line in the travis log.

Same size, 186. It's the same builds just using more api setup and less cli

Awesome. Just going to run a diff of the dist before and after to make sure the UMD entrypoint didn't change.

It's the same. Diff'd locally, only .es.js are different (because new).


bump go packages, fit to CSI versions

Signed-off-by: 662962756<EMAIL_ADDRESS>

 Upgrade go version + external packages to latest for Operator


Add API

Added events and moved methods from main class to api class. This will allow other plugins to read, modify, and send messages in both directions.

I went ahead and implemented the events and added an API interface rather than moving all those methods to a standalone class.


test

please aslo sync your repository, as we have merge conflicts here

merging, but please run a sync


chat not updated

What happened?
After reply from OPENAI chat is not updated, latest question and answer is not visible

How to reproduce the bug
Need to refresh the page to load new messages
Package Version
latest
PHP Version
8.1
Laravel Version
10.10
Which operating systems does with happen with?
Linux
Notes
No response

Hey, I recently released a small fix for chat styles. Are you using version 1.0.2 or 1.0.1? If 1.0.2, did you update to it or install it? Also, what browser are you using?
And the last thing - have you tried resetting the assets through the command
php artisan filament:assets

after running,  php artisan filament:assets no changes, version is 1.0.2, it's a fresh installation

Please update to the latest version 1.0.3, everything should work

Unfortunately is same after update to 1.0.3

Do you publish view resources/views/vendor/filament-openai-assistant/pages/assistant-chat.blade.php ?

Yes, view published

You need to either delete the file and republish php artisan vendor:publish --tag="filament-openai-assistant-views".
Or if you have already made changes to it, you need to replace the html tag
<template shadowrootmode="open"> to <div class="reset-styles">, don't forget replace the closing tag

works, thanks


I can't install the firmware

Hi all, I have a Yi camera model YYS.2016.
I tried to install the y291ga firmware.
The cam does not flash.
I followed the procedure, but it doesn't work.
Can you help me?
Is the firmware correct?

Try to make a backup of the cam and check the output files.
You will find the suffix.


Change heightmap extractor to produce GeoTIFFS

Currently the 3dscanner heightmap extractor produces BMP files that are not georeferenced.  The extractor should be updated to produce accurately georeferenced GeoTIFFs that can also be used for fullfield stitching.
Using the existing terrautils create_geotiff method, it looks like there are a number of factors with the 3D scanner that need to be considered (and currently aren't). Per discussions with @solmazhajmohammadi and @max-zilla:

We are scanning about 5.5 meters extra (~2.75 m on each side) so scanDistance of 21.8 is actually 27.3.
Y FOV in fixed metadata is probably wrong (currently 0.8). PLY files are ranging from 0.727 to -0.705, so FOV is ~1.432m.
Need to account for scan direction (0, 1)

Looking at two specific examples:

2017-07-01__00-00-54-461: Scan direction negative. The bounding box for heading east scanner: start line is 21.34m to -0.66m and the width of image is from 95.535 to 96.945 --> some approximation is involved in this, since I'm only seeing the plants in the FOV and not the ground and this calculation is just based on the canopy height. You can play with this number of FOV to see which one is more accurate scan.
2017-07-01__00-02-41-951: Scan direction positive. The bounding box for heading east scanner: -1.444 to 21.031 these numbers are for heading east scanner, the heading west scanner is gonna be 2.75m offset added to these numbers

Completion criteria:
[ ] heightmap extractor produces GeoTIFF output with accurate georeference information
[ ] Review
[ ] Testing (load generated GeoTIFFs in QGIS at a minimum)

The terrautils method calculate_gps_bounds (https://github.com/terraref/terrautils/blob/master/terrautils/extractors.py#L293) needs to be updated to handle the 3dscanner data.


Generalise detrender/deseasonaliser

Allow to pass an arbitrary forecaster to the Detrender/Deseasonaliser transformer,
Transformer then calls fit and predict (in-sample) on the observed data and subtracts the forecast from the observed data.

Closed by #218


RxJava2 Support

Hello,
are you planning to add RxJava2 support? If yes, any ETA yet?

Yes, its on my list. I'll try to finish it over this weekend. Worst case: next week.

@jossiwolf I am prioritizing #40 over this.
With this new structure, Rx support would be separated into a separate module. After that, it would be easy to add another module for rxjava2 support. What do you think?

@manas-chaudhari
Sounds like a good move. Having a structured codebase is important.
Take your time!

Hey @manas-chaudhari thanks for the project. I'm starting now with Rx and MVVM. Seen your video at Droid Connin do you use a converter from ObservableField to Observable. Here it is at file "FieldUtils". How can I convert it to the rx2?
any ETA to this project with rx2?
Thanks

@tvaamorim Yes, you are right about FieldUtils.
I have started working on RxJava 2 support. The plan is to primarily support only RxJava 2, with an optional module to support RxJava 1 via RxJava2Interop. My target is to complete this by March 5th.
Until then, I recommend that you create your own wrapper over FieldUtils using RxJava2Interop. This wrapper would convert between rx2.Observable <-> databinding.ObservableField. For working with RecyclerView/ViewPager, you can add a BindingConversion for rx2.Observable -> rx1.Observable.

@manas-chaudhari thanks for the fast response.
I will take a look at RxJava2Interop.
Thanks. Please keep with this awesome project. It helped me a lot ;D

Hey @manas-chaudhari great job so far and thanks for the library.
@tvaamorim I have forked this library and built an RxJava2 version that you may use in the meantime. Feel free to check it out.

@bigmikehoncho awesome man!! exactly what I need!
Checking the project right now =D
Thanks for sharing it.

RxJava2 support has been released :)
Do note the maven coordinate changes as mentioned in changelog


PLSQLDev Plugin in C# - using out parameter get system error

Hi,
I just follow instruction to call function IdeGetConnectionInfo. However it returns an system exception:

No idea why this happen. Can anyone help me?
thx, Alan
I--------------------------------------------------------------------------------------------
Receiving a string as an out argument:
// C++ signature:    void IDE_GetConnectionInfo(char **Username, char **Password, char **Database);
// Delphi signature: procedure IDE_GetConnectionInfo(var Username, Password, Database: PChar);
// Declaration
public delegate void IdeGetConnectionInfo(out string username, out string password, out string db);
private IdeGetConnectionInfo getConnectionInfoCallback;
// Usage
// IMPORTANT: Allocate out string before call.
string user = "";
string password = "";
string db = "";
getConnectionInfoCallback(out user, out password, out db);

Hi, Alan,
My apologies for the late response -- the project now is kind of abandoned by me due to simply lack of spare time. Hope will return to it soon.
First, I need a little bit more info:

Your OS (Win7, Win10 etc)
PL/SQL Developer version number (10, 11, 12...)

Sorry, my PC is old and slow, and I can't spin a virtual machine on in to try on different Win versions.
For now, I give you a code, which compiles and works on my Win7 32bit machine, PL/SQL Dev 10. What you have to do:

Create a project in Visual Studio.
Add NuGet package "Robert Giesecke Unmanaged exports" to project.
Add System.Windows.Forms reference to project (in solution explorer Add > References ...)
Be sure you set x64, when you build the project.
After successful build, copy the dll to plugins directory.
Restart PL/SQL Developer.

Plugin creates a menu "Get connection info demo" under Tools. By clicking it, it call GetConnectionInfo and shows user, password and db, to which you are currently connected.
I'm waiting for your response, if it worked to you.
using System;
using RGiesecke.DllExport;
using System.Runtime.InteropServices;
using System.Windows.Forms;

namespace GetConnectionInfoExample
{

    public delegate void IdeGetConnectionInfo(out string username, out string password, out string db);

    public class GetConnectionInfoExamplePlugin
    {
        private static IdeGetConnectionInfo getConnectionInfoCallback;

        private const string PLUGIN_NAME = "Sample GetConnectionInfo plug-in";

        private const int PLUGIN_MENU_INDEX = 1;

        private static GetConnectionInfoExamplePlugin me;
        private int pluginId;

        private GetConnectionInfoExamplePlugin(int id)
        {
            pluginId = id;
        }

        #region DLL exported API
        [DllExport("IdentifyPlugIn", CallingConvention = CallingConvention.Cdecl)]
        public static string IdentifyPlugIn(int id)
        {
            if (me == null)
            {
                me = new GetConnectionInfoExamplePlugin(id);
            }
            return PLUGIN_NAME;
        }

        [DllExport("RegisterCallback", CallingConvention = CallingConvention.Cdecl)]
        public static void RegisterCallback(int index, IntPtr function)
        {

            getConnectionInfoCallback = (IdeGetConnectionInfo)Marshal.GetDelegateForFunctionPointer(function, typeof(IdeGetConnectionInfo));
        }

        [DllExport("OnMenuClick", CallingConvention = CallingConvention.Cdecl)]
        public static void OnMenuClick(int index)
        {
            if (index == PLUGIN_MENU_INDEX)
            {
                string user = "";
                string password = "";
                string db = "";
                getConnectionInfoCallback(out user, out password, out db);
                MessageBox.Show("User: " + user + "\nPassword: " + password + "\nDB: " + db, "Connection info");

            }
        }

        [DllExport("CreateMenuItem", CallingConvention = CallingConvention.Cdecl)]
        public static string CreateMenuItem(int index)
        {
            if (index == PLUGIN_MENU_INDEX)
            {
                return "Tools / Get connection info demo";
            }
            else
            {
                return "";
            }
        }

        [DllExport("About", CallingConvention = CallingConvention.Cdecl)]
        public static string About()
        {
            return PLUGIN_NAME;
        }
        #endregion
    }
}

Hello,
This fix doesn't work, it containts also a bug, the RegisterCallback isn't implemented correctly, it should look like:
if (index == CALLBACK_CONNECTION_INFO ) //12   {          callbackGetConnectionInfo = (IdeGetConnectionInfo)Marshal.GetDelegateForFunctionPointer(function, typeof(IdeGetConnectionInfo));    }
If you apply this pl/sql developer crashes....
I think the problem are the out parameters, when I change them to IntPtr:
public delegate void IdeGetConnectionInfo(out IntPtr username, out IntPtr password, out IntPtr db);
IntPtr user;  IntPtr password;  IntPtr db;                     callbackGetConnectionInfo(out user, out password, out db);
Now pl/sql developer doesn't crashes, and this message:
MessageBox.Show("TEST: " /*+ test */ + "\nUser: " + user.ToString() + "\nPassword: " + password.ToString() + "\nDB: " + db.ToString(), "Connection info");
Shows this information:

Connection info
TEST:
User: 179695408
Password: 179673712
DB: 179699536
OK
I am not sure if IntPtr is the right datatype, when I use char pl/sql developer alse doesn't crash.
Anyone know what the correct datatype is and how to convert it to a string?

Hi,
Oops, you're right – I've deleted if in the RegisterCallback.
It seems, that you are facing the same issue I've seen with the string return values.
Short answer
You need explicitly marshal (or cast, in other words) IntPtr to string. Just call Marshal.PtrToStringAnsi on each of out parameters, for instance, Marshal.PtrToStringAnsi(user). Please refer to Passing and receiving strings for details. Although that page describes usage of this technique for marshalling return value, this should work for out parameters as well.
Longer answer
IntPtr is (at least should be) the right datatype – it is a pointer to anything in the unmanaged memory area e.g. outside .NET CLR. In your case this is a string. Your plug-in's code lives inside the .NET CLR (managed memory area), thus knows nothing about the outside world (anything which is located in the unmanaged memory).
>>> Without marshalling the value behind IntPtr means nothing to your C# code. <<<
This you've nicely illustrated: 179695408 is a decimal value of the address where user parameter value is stored. Usually, .NET does implicit marshalling e.g. casts IntPtr to a meaningful value behind the scenes – you don't need to do anything. This works fine with long, int (string on my older 32-bit machine).
However, this does not work with booleans (needs [MarshalAs(UnmanagedType.Bool)]) and, it appears, it does not work with strings (I don't know the reasons). So you need to do an explicit marshalling by calling Marshal.PtrToStringAnsi – this should work.
Let me know if that solved the issue.
See also:

Callback concepts for more details and links about marshalling.
Documentation of Marshal class. Look for PtrTo* methods to see, what IntPtr can be marshalled to.


sst-env does not update during development

When using the StaticSite construct and sst-env to pass through ENV Variables, it works great on initial deployment, but not afterwards.
Steps:

sst start
sst-env -- expo start
env var works great here :)
Add a new env variable into stack
sst recognizes that there is a new change, Hit Enter to deploy
Hit Enter and wait until deployment finishes
Close running react-app
sst-env -- expo start
The new env variable is not added in.

It looks like that .build/static-site-environment-output-values.json is not updated on the last deployment. But .build/static-site-environment-output-keys.json is updated with the new key in there.

You need to restart the sst start command as well to reflect changes.

@Manitej66 yes. But it would be nicer if we don't have to re-run that.

@justindra this would require sst-env to kill and restart the export start process. Does that make sense?
Curious to hear what @thdxr and @jayair think.

So I don't think sst-env would need to do that. As I am happy to re-run that. The issue is currently, we need to re-run both sst start as well as sst-env -- expo start. And since sst start also runs the build for the mobile/static site, that build is being run twice, just to get a new ENV var.
Ideally I just need to re-run sst-env -- expo start and then it works. And sst start is still running in the background as per usual for both the console and the live lambda env.

Alright, added this in v1.2.20.
The .build/static-site-environment-output-values.json file nows get updated with the new values from redeploys.


Consider removing 4.0.22 from PyPI

Testing for the Stack Overflow question
“Invalid character value for cast specification” when using pyodbc in Python
reveals that it is reproducible with 4.0.22 under Python2. The same code works properly using 4.0.21.
If it looks like 4.0.23 might take a while to arrive then you may want to consider removing 4.0.22 from PyPI; instructions here. The issues with 4.0.22 are causing significant inconvenience for a lot of people and are damaging the pyodbc "brand".

You are right...  I have reverted the parameter binding changes from 4.0.22 and released 4.0.23.  This should help, but now I have to go through the open issues and make sure.  (Any open issues were apparently not caught by the unit tests, so I'll try to improve them.)


Set up a bot which closes support issues automatically

🐞 Problem
The issues labeled with Support has to be closed when the author/us stop interacting on the issue for 3 weeks.
🎯 Goal

💡 Possible solutions

📋  Steps to solve the problem

Comment below about what you've started working on.
Add, commit, push your changes
Submit a pull request.
Add this in the comments:

Addresses #<put issue number here> if you are partially fixing the issue.
Fixes #<put issue number here> if you are completely fixing the issue.

Let it remain. It may help someone 😀

It will help me lol. I'm going to do it. Thanks @shreyasbapat

Sure. Let me know if something, some configuration needs to be done from my end


Global config file

Add a system-wide config file.
Closes #107, note that if a local config file exists it will be preferred.

I'm not sure about the naming of the option tho (--get-global-config-path feels long).

woopsie daisy, you have a very small conflict that I gave you
Thanks you hero


Installation error<EMAIL_ADDRESS>404 (Not Found)

I have installed material2 as suggested in README.md. To start off, I simply added an MdButton to my app. When I run the application, I get this error:
GET<EMAIL_ADDRESS>404 (Not Found) (Initiated from angular2-polyfills.js).

As soon as I take out MdButton, the app works. What am I doing wrong?
Here's my component:
import {Component} from 'angular2/core';
import {CORE_DIRECTIVES, FORM_DIRECTIVES} from 'angular2/common';
import {MdButton} from '@angular2-material/button';

import {NameListService} from '../../shared/services/name-list.service';

@Component({
  selector: 'sd-home',
  moduleId: module.id,
  templateUrl: './home.component.html',
  styleUrls: ['./home.component.css'],
  directives: [FORM_DIRECTIVES, CORE_DIRECTIVES, MdButton]
})
export class HomeComponent {
  newName: string;
  constructor(public nameListService: NameListService) {}

  /*
   * @param newname  any text as input.
   * @returns return false to prevent default form submit behavior to refresh the page.
   */
  addName(): boolean {
    this.nameListService.add(this.newName);
    this.newName = '';
    return false;
  }
}

Here's my SystemJS configuration:
"packages": {
  "angular2": {
    "defaultExtension": false
  },
  "rxjs": {
    "defaultExtension": false
  },
  "@angular2-material/core": {
    "format": "cjs",
    "defaultExtension": "js",
    "main": "core.js"
  },
  "@angular2-material/button": {
    "format": "cjs",
    "defaultExtension": "js",
    "main": "button.js"
  },
  "@angular2-material/checkbox": {
    "format": "cjs",
    "defaultExtension": "js",
    "main": "checkbox.js"
  }
}

It sounds like you're not copying the files to the directory from which your app is serving files. The setup for this is going to depend on your particular build / serving setup.


Mitigation for TF cluster creation bug

You'll need to run the terraform fmt tooling (there's a new lint checker above)


[ASP.NET Core Integration] Skip serialization of http response following function execution

HTTP responses should not go through the following code path:
https://github.com/Azure/azure-functions-dotnet-worker/blob/cf06831697fbcd7cb16157d65b737e5a97572dab/src/DotNetWorker.Grpc/RpcExtensions.cs#L21
These extra steps are unnecessary and impact performance.

This issue may also be causing a race condition bug: #2682

Closing as this is done for HttpResponseData when it is set in InvocationResult, and the item tracking multi-output responses is #2682


ReactPlugin becomes undefined after certain amount of time

We've been trying to integrate the react SDK of this into our project that uses redux with persistent states but it seems to be after a certain amount of time the React plugin object becomes undefined resulting in an exception which stops the page from loading
"TypeError: reactPlugin.trackMetric is not a function"

Yes, this happens to me as well. Using the code from the react demo and on component unmount of the withAITracking it is undefined.
TypeError: Cannot read property 'trackMetric' of undefined
class_1.componentWillUnmount

Same here :(

Facing the same issue, Any solution for this ?? Thanks

Same here, did anyone find a workaroud to avoid this?

People: I've just found out a possible outcome:
in the TelemetryService.js file theres this code
let reactPlugin = null;

and then this inside the initialize function:
reactPlugin = new ReactPlugin();

I've replaced the first one with:
const reactPlugin = new ReactPlugin();

and commented the second one and it somehow fixed the issue, but I cant tell yet if this breaks something else.

Same here - Do we have any updates / solutions for this please ?

This issue is still happening - does anyone have a resolution for this?


Mask eos token for packed dataset

Hi,
My current understanding of training with packed dataset is that if we have two sequences packed together, we will compute loss for eos token from the first sequence as input and bos token from the second sequence as target. In the recipes, I can find masking only for the padded tokens towards the end of pack and not for these in between extra tokens. Is this correct?

@RdoubleA I was looking into text completion dataset which does not have mask that you mention here

All of our dataset classes determine labels for loss based on the mask

Otherwise, I agree with what you said and was hoping that will be the case for all datasets.

For text completion / continued pre-training, there's no concept of "user" and "assistant" or "input" and "output", there is just a document that you want the model to learn the semantics of. So the labels will be a direct copy of the input tokens offset by one so that the model can learn to predict the next token.
input: <s> This is  a    cool  fact  about a   cat from    a      textbook about cats. </s>
             |       |     |    |       |        |         |       |      |      |        |             |            |         |
pred:   This is   a cool fact  about   a    cat from a textbook about     cats   </s>

None of these tokens should be masked out.

My question was about token </s> at the end of first sequence and before the start of next sequence when we use packing with text completion dataset. In this case, we will have something like
input: <s> This is  a   cool  fact  about a   cat from   a  textbook about cats. </s>  <s> This is ...
        |   |    |  |    |     |     |    |    |   |     |      |      |    |      |    |
pred:  This is   a cool fact  about  a    cat from a textbook about  cats  </s>   <s> This  ...

and there is no way to mask this token or loss on it afterwards with current code. I am not sure what the desired behavior should be but it can affect other tasks such as statistics of activations. Please feel free to close the issue if this not relevant.

Ah I see, so if I understand correctly you want to mask out the in between  tokens for packed sequences, but not the  tokens?
You're right that it can impact activations and model output - but I would still say you want to keep the loss for those tokens. The model needs to learn when a document ends even within a packed sequence so the data should keep those boundaries.