Agenda for 1st meeting

round of introductions

what's your name
what's your professional background
what brought you to Tallahassee
1 more

goal: encourage sufficiency through safe and stable housing
reveal meeting calendar

february - what does providence look like? (using personal knowledge)

sharing personal stories, interactions with providence and its residents
what does housing provide?
what does lack of housing breed?

march - what does providence look like? (insights from historical and current datasets); reports
; previous work)  - april - what could
-m ay -
june -
july -

we need history of providence; transformations of providence. how can we restore the original intentions of this neighborhood?
this is an experimental outlet to really discuss the root causes and efforts of missing housing? is this is the final step before homelessness?

done. closing


v1.13 backports 2023-06-02

[ ] #25079 -- test: Collect sysdump as part of artifacts (@pchaigno)
[ ] #25742 -- bpf: dsr: fix typo in tail_nodeport_dsr_ingress_ipv4() (@julianwiedmann)
[ ] #25795 -- bpf,datapath: read jiffies from /proc/schedstat (@ti-mo)

:warning: minor conflict s

[ ] #25774 -- Pick up the latest startup-script image (@michi-covalent)
[ ] #25747 -- test: prevent panic on k8s services host fw test on some runs. (@tommyp1ckles)
[ ] #25803 -- daemon: Reject BPF Host Routing without KPR=strict (@pchaigno)

Skipped due to major conflicts:

[ ] ~#25450 -- Slim down Node handler interface (@bimmlerd)~

:loudspeaker: major conflicts due to hive and cell changes

[ ] ~#25419 -- wireguard, linuxnodehandler: untangle WireGuard agent from the linux node handler (@bimmlerd)~

:loudspeaker: skipped as dependent PRs are not backported (e.g. https://github.com/cilium/cilium/pull/24016)

Once this PR is merged, you can update the PR labels via:
$ for pr in 25450 25419 25742 25795 25774 25747 25803; do contrib/backporting/set-labels.py $pr done 1.13; done

/test-backport-1.13

/test-runtime

/test-backport-1.13

The conflict is very minimal https://github.com/cilium/cilium/pull/25795, most of the reviews are in, CIs are green as well :heavy_check_mark:.
Marking this ready to merge.


e2e: Update fedora-with-test-tooling to fedora 39

What this PR does
Before this PR:
After this PR:

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer
/cc none

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

/test pull-kubevirt-e2e-k8s-1.31-sig-compute pull-kubevirt-e2e-k8s-1.31-sig-network  pull-kubevirt-e2e-k8s-1.31-sig-storage
pull-kubevirt-e2e-kind-sriov  pull-kubevirt-e2e-k8s-1.30-ipv6-sig-network

/test pull-kubevirt-e2e-kind-sriov pull-kubevirt-e2e-k8s-1.30-ipv6-sig-network

/test pull-kubevirt-e2e-kind-sriov pull-kubevirt-e2e-k8s-1.30-ipv6-sig-network

/test pull-kubevirt-e2e-k8s-1.31-sig-compute pull-kubevirt-e2e-k8s-1.31-sig-network pull-kubevirt-e2e-k8s-1.31-sig-storage

/test pull-kubevirt-e2e-kind-sriov pull-kubevirt-e2e-k8s-1.30-ipv6-sig-network

/test pull-kubevirt-e2e-k8s-1.31-sig-compute pull-kubevirt-e2e-k8s-1.31-sig-network pull-kubevirt-e2e-k8s-1.31-sig-storage

/test pull-kubevirt-e2e-k8s-1.31-sig-compute-migration /test pull-kubevirt-e2e-k8s-1.31-sig-compute-serial

/test pull-kubevirt-e2e-k8s-1.31-sig-compute-migrations pull-kubevirt-e2e-k8s-1.31-sig-compute-serial

@brianmcarey @qinqon I've posted https://github.com/kubevirt/kubevirt/pull/13542 to address the passt failures blocking this PR.

/retest-required

/retest-required

/test pull-kubevirt-e2e-k8s-1.30-sig-network


Package upgrades

Thank you for helping out with embedded-graphics development! Please:

[x] Check that you've added passing tests and documentation
[x] Add a CHANGELOG.md entry in the Unreleased section under the appropriate heading (Added, Fixed, etc) if your changes affect the public API
[x] Run rustfmt on the project
[x] Run just build (Linux/macOS only) and make sure it passes. If you use Windows, check that CI passes once you've opened the PR.

PR description
The result of a cargo upgrade and cargo update.
I don't think this needs a changelog entry does it?

Argh, I did run the build locally but didn't have the override set after the repo move.

fixed was failing. It requires an MSRV of 1.44.0 as of 1.0.0.

I don't think this needs a changelog entry does it?

The nalgebra update from 0.19.0 to 0.23.0 is a breaking change and should IMO be included in the changelog.

Good catch. Changelog entry added. Should be good for review.


Mouse click release not being detected in text area

Just upgraded from v1.4.3 to 1.5.2 and now when I click in the code editor, and I move my mouse, it highlights the text as if I was still holding the mouse button down. Reinstalled Atom and also tried Atom 1.6 Beta, same issue occurs in that release. My OS is Ubuntu 15.10 (64-bit). Never had this issue ever before with Atom. This issue only happens in the text area (i.e. I cannot click on a file in the project directory, move my mouse and have it dragged to wherever.) If I actually highlight text and release my mouse button, the issue does not happen.

My bad, I just tried disabling all my packages and found that it was the highlight-selected package that is causing the issue.

My bad x2, disabling all community packages does not fix the issue, not sure why I thought it did.

Even after renaming the ~/.atom folder and opening, the issue persists, by the way.

Restarted my computer a few times and it seems to have fixed itself.


do not parse file system for expired files on each render

we don't suspect file will expire just while the user is using the program, if the expiration time is 7 days

Good point. However, RenderEngine constructor is called just as often as Render**() methods.


fix: jsdoc errors due to unrecognized format

Description
Fixed some jsdoc errors because it did not support some auto generated mjs documentation styles.
Also run jsdoc when doing syntax format check so we do not need separate jsdoc check from ci flow as mentioned in #544
Related Issues

Closes #543
Closes #544

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Update main nav to be mobile-friendly

Purpose

Update the main nav to be mobile-friendly

Changes

Added mobile-specific nav menu (screens ≤ 768px wide)

Caveats

Currently the links to Extensions & API go directly to the top-level page. Ideally both of those links would be an accordion and show the relevant subsections. However, each of the subsections do not have an overview page (e.g. https://developer.adobelaunch.com/extensions/reference/), thus nowhere to link to. Adding an overview page for most of the subsections should easy, but guidance on how Adobe would like to see the reference pages handled would be appreciated.

Additional helpful information

This is an alternative design to #58
It wasn't clear if there was a way to add an icon (hamburger menu) directly to the icons file, so I've inlined it
Screenshots of the mobile nav

It'll probably be a couple weeks before we get a chance to review.
Is this one compatible/dependent on #58 in any way.  You think we should do one or the other? Or do both, but one should go first?

It'd be incompatible with #58 unfortunately; two different approaches to making it responsive (hide everything except the three main links in #58 vs. adding a separate full menu in this one)


pushy seems like has no feedback component?

As of v0.5, Pushy uses the new HTTP/2-based APNs protocol, which does not have a feedback component. Instead, the APNs server tells us immediately if a notification could not be delivered because the token has expired. Please see the PushNotificationResponse documentation for details.

@jchambers got it.  thanks so much


Merge from official 2 12 2020

@veljkomih this is going to make submitting upstream PRs a pain :( we need to rebase our fork for this to work.


Cannot read property 'slice' of undefined error

$ npx elm-upgrade@latest
npx: installed 50 in 7.874s
(node:66389) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'slice' of undefined
    at /Users/kieron/.npm/_npx/66389/lib/node_modules/elm-upgrade/upgrade.js:154:64
    at Array.forEach (<anonymous>)
    at main (/Users/kieron/.npm/_npx/66389/lib/node_modules/elm-upgrade/upgrade.js:153:17)
    at /Users/kieron/.npm/_npx/66389/lib/node_modules/elm-upgrade/upgrade.js:575:7
    at processTicksAndRejections (internal/process/task_queues.js:94:5)
(node:66389) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:66389) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Any ideas?

dupe of #86 ?

Fixed in 0.19.8


Module feature and Place holder feature

The first commit add the Module feature
customContainer := ore.NewContainer()
ore.RegisterLazyFuncToContainer(customContainer, ore.Singleton, ..)
broker, _ := ore.GetFromContainer[*Broker](customContainer, ctx)

motivation:

for our users: support Modular Monolith architecture.
for us: reduce the global space
for us: facilitate writing isolate tests or benchmark (which can be run evens in paralellel)

The second commit add the Place Holder feature
This feature has the potential to become one of the most useful feature (or added value) of Ore.
Problem the feature will solve:
your certain Service depends on certain UserInfo (user name, user's role...), but you don't have them on registration time. Only after parsing the user request, connect to the database... that you will know the user's name, his role...
Because you cannot register a specific UserInfo directly so a common work around is to Register a UserInfoProvider instead.
As a result you have to make your Service depends on the UserInfoProvider while the real dependency is UserInfo.
A common implementation of the UserInfoProvider is to provide the UserInfo to the request context, so that it will be retreived later to create the Service => this common implementation repeat exactly what Ore is doing.
With the "place holder feature", you no longer need a UserInfoProvider "proxy". Your service depends directly to the UserInfo (as it should).
We can also think of this feature as eagerly registering an object but with Scoped life time similar to RegisterEagerSingleton
checkout the README for more info
Inspiration source:

https://github.com/dadhi/DryIoc/blob/master/docs/DryIoc.Docs/RegisterResolve.md#registerplaceholder
https://github.com/duongphuhiep/AsyncInjectionTutorial/blob/master/README.md

other bug fix (second commit)

fix validate lifetime bug which cause flaky tests
fix "simple" examples

ops, I will resolve the conflict soon

I will take care of the conflicts

While resolving the conflicts, I reviewed the last commit and got some remarks
"isBuilt" and "isSealed" is quite confusing in the last commit.
I understand the idea that if the container validation was a success then it is useless to check validation over and over again for future services resolving.
While it is true most of time, exception exist for users who don't follow our recommendation:
RegisterLazyFunc(Scoped, func(ctx context.Context) (*A, context.Context) {
  if (randomNumber is odd) {
    b1, ctx = Get[*B1](ctx) //A (sometimes) depends on B1
    return &A{b1}, ctx
  } else {
    b2, ctx = Get[*B2](ctx) //A (sometimes) depends on B2 => circular dependency here
    return &A{b2}, ctx
  }
})

This guys put some small "if" in the resolver making A sometimes depend on B1, sometimes depends on B2. The container's validation success, but he still not confident that his dependency graph is good. So he doesn't want to disable the runtime validation, but unfortunately it is automatically disabled with the isSealed boolean of this commit.

## Naming

* `Build()` doesn't really built anything, but to seal the registrations => I suggest to name it `SealRegistration()`, `DoneRegistration()`, `FinishRegistration()` so that the function name is self-explanatory

* if you still want to keep the `isSealed` boolean, then I would suggest to replace it with an enum `RegistrationsHealth { Healthy, Unknow }
  *  Evens the validation passed with success, the "registrations health" of the container stays "unknow" if the registration is still open to accept more registration.
  * RegistrationsHealth is set to Healthy only if the registration is sealed (no more registration) and the validation passed.

While the enum RegistrationsHealth with 2 values technically can be map to a boolean. But reasoning the enum RegistrationsHealth makes a clearer semantic than a boolean `isSealed` true / false

hi @duongphuhiep
thank you for your contributions, it really did add to Ore, i had finished earlier a feature that practically did multiple containers(modules) but never merged it, i will showcase the differences later and show it to you before merging if you're interested. would you be interested in becoming a maintainer when v1.0 is published ?
+
i agree with your remarks on my latest commit, i'll take care of it and do some refactoring

thanks for your trust, I would gladly listen to your idea about "module" and help to maintain the project.
as for v1, I will open a new discussion thread for various points I can think of


How to create list control programatically?

Hello. I would like to create list control programatically. There exist an example about List Rendering on the web page but I could not create this control programatically. Could you help about this matter?

var formModel = new[]
            {
                    new PropertyVm(typeof(IEnumerable<string>) , "RestrictedMaterials")
                    {
                        DisplayName = "RestrictedMaterials",
                        Choices = new[] { "Guns", "Knives", "Explosives", "Nuclear Waste", "Weaponised Viruses" },
                        Value = new[] {"Guns", "Explosives"} ,
                        Readonly = false ,

                    },
};

FF.PropertiesFor(formModel).Render().Dump();

I think it should be something like that.

Thank you very much. It's worked.


AMQ role based access control support

AMQ Jon plugin supports AMQ 7's RBAC management feature. To be able to
have the right access to broker's management resource, Jon must
use a valid credential (username/password) to connect to the
broker. The broker uses JAAS login module to authenticate
against Jon's credentials and then authorizes any requests from
Jon plugin against the access-control policy defined in
management.xml.
The Jon plugin's default user is 'admin' and default password is 'activemq'.
You can configure the plugin to use a different user/password to connect
to the broker. The configuration file are located in the following path:
<artemis.instance>/etc/org.jboss.rh-messaging.amq.jon.cfg
This file takes the form of java properties file. It allows you to
specify the user name and password for the Jon plugin to connect to
the broker. You can also configure the jmx connector url in this file.
For example a configuration can have the following properties:
principal = guest
credentials = guest
connectorAddress = service:jmx:rmi:///jndi/rmi://localhost:11099/jmxrmi
where the value of 'principal' is the user name (i.e. guest); the
value of 'credentials' is password (i.e. guest); and the value
of 'connectorAddress' is the connector's url.

looks good I will merge


Added streaming register bank and basic xssr instructions

Related to issue #41. Set up the snitch stream, the functionality for reading and writing, as well as some xssr instructions.

main.py is unchanged from the "snitch" branch. Will need to address it later.

I fixed the __main__.py!

Can you add an entry to the Changelog.md please


added jobs model and some views.

Just updated to add code for the job post and listing. more to come

niiice, and sonds good.
and as usual , thank you very very much. Awesome as always 👍
and i also saw some pycache files, will see how to get around those since i only gitignored a few or a single folder i think


write a program to find the area of a circle

find the area of a circle given the radius = 6cm

we can easily calculate the area of a circle.


Remove typecast for entity class

By type casting the entity class you cannot use a custom doctrine entity.

My thought is that you should still implement the user interface at minimum in a custom user entity to ensure that that the mapper will behave as desired.

I'm starting to think along the same lines and perhaps this module is best served using it out of the box instead of with custom entities.  This means I need to wrap my database diagram around your user_id conventions vs key and ref which are easier to read and query IMHO.  At any rate I'm now down to trying to implement this out of the box.
The more I use this module the more I think it has to be a cornerstone of your project so you can make your project work with it.  I had tried to drop it into an existing diagram.

Well, keep in mind that we definitely do want to support custom entities and have that be a fully supported workflow. By no means to I want to lock everyone into using the entity we provide out of the box. I just think it's best for everyone if we keep the custom entities at least compatible with the interface so that they'll behave in a somewhat predictable manner.

Closing now -- I don't think there is an issue here.


request on YogaInitialContext is conflicting with the request on the Koa server context

Describe the bug
We integrated GraphQL Yoga with the Koa server as documented here https://the-guild.dev/graphql/yoga-server/docs/integrations/integration-with-koa
and pass the Koa context like this
const response = await yoga.handleNodeRequest(ctx.req, ctx)

The Koa context contains the Koa request as a request property on the context. However the Yoga server assumes that the request property on the context it is actually the internal platform-independent Fetch Request.
This causes problems e.g. in the use-schema plugin (https://github.com/dotansimha/graphql-yoga/blob/main/packages/graphql-yoga/src/plugins/use-schema.ts)
const schemaByRequest = new WeakMap<Request, GraphQLSchema>();
return {
    onRequestParse({ request, serverContext }) {
      return {
        async onRequestParseDone() {
          const schema = await schemaDef({
            ...(serverContext as TServerContext),
            request,
          });
          schemaByRequest.set(request, schema);
        },
      };
    },
    onEnveloped({ setSchema, context }) {
      if (context?.request == null) {
        throw new Error(
          'Request object is not available in the context. Make sure you use this plugin with GraphQL Yoga.',
        );
      }
      const schema = schemaByRequest.get(context.request);
      if (schema == null) {
        throw new Error(
          `No schema found for this request. Make sure you use this plugin with GraphQL Yoga.`,
        );
      }
      setSchema(schema);
    },
  };

During onRequestParseDone the schema is placed in the WeekMap based on the Yoga request, however within onEnveloped the WeakMap is accessed based on the Koa request from the Context. Since this is different the schema cannot be found and the plugin fails.
A potential workaround of removing request from the Koa context before passing it to Yoga doesn't work, because the request is internally referenced from the context and it becomes dysfunctional.
BTW the same issue exists within the useDisableIntrospection plugin.
Your Example Website or App
sorry no example, but the problem should be clear from the description
Steps to Reproduce the Bug or Issue
I hope the above description is enough to understand the issue
Expected behavior

Do not assume the request property on the context is the Yoga request

Screenshots or Videos
No response
Platform

OS:macOPS
NodeJS: 20.9.0
@graphql-yoga/* version): 5.0.2

Additional context
No response

Hi, thank you for raising this issue.
I'm not sure why the boilerplate is like this in the documentation, I don't think that it is a good idea to pass directly the koa context as the initial GraphQL context.
I would recommend to either remove the context (let Yoga create a new empty one) if you don't need to access Koa's context in the GraphQL context.
const response = await yoga.handleNodeRequest(ctx.req)

If you actually need to access the Koa context via the context (from a resolver or from a plugin hook), I would create a new context and put the Koa context under a dedicated key:
const response = await yoga.handleNodeRequest(ctx.req, { koa: ctx })

This way, you can always access Koa context in resolvers.
For example:
const resolvers = {
  Query: {
    hello: (_, __, context) => {
      const user = await getUserFromHeaders(context.koa.headers)
      return `Hello ${user.name}`
    }
}

Hi Valentin,
thanks very much for the quick reply and solution. Actually your suggestion with { koa: ctx } solves my problem.
I think in general it makes sense to show in the documentation how to forward the ServerContext to the GraphQL Yoga framework as it is a core part. See here: https://the-guild.dev/graphql/yoga-server/docs/features/context#server-context
Maybe updating the example code in the framework would help others not to run in the same issue


I need execute

Is there option for 'execute'?
...xmlrpcmsg('execute');

If you review the code, you'll see there is an model_execute_kw and model_execute_splat method.


Java 10 compatibility

Verify that basic flow works fine.

Blocked in master by:

SunCertPathBuilderException: unable to find valid certification path to requested target
https://travis-ci.org/szpak/mockito-java8/jobs/354680524

and https://github.com/szpak/CDeliveryBoy/issues/3

Fixed with cacert linking. Released 2.3.0.


Update FuelTanksPlus.netkan dependencies

Closes #1935

Passes local, passes Jenkins, just a depends change. Merging.


Excluding OpenJ9 and z/OS specific JTReg tests

Excuding openj9 specific tests and zos specific tests for jdk11 and later releases.
OpenJ9 exclusions:
java/lang/management/MemoryMXBean/MemoryManagementConcMarkSweepGC.sh
java/lang/management/MemoryMXBean/MemoryManagementParallelGC.sh
java/lang/management/MemoryMXBean/MemoryManagementSerialGC.sh
java/lang/management/MemoryMXBean/MemoryTestAllGC.sh
java/lang/management/MemoryMXBean/MemoryTest.java
java/lang/management/MemoryMXBean/LowMemoryTest.java
javax/management/Introspector/ClassLeakTest.java
java/lang/management/MemoryMXBean/MemoryTestZGC.sh
z/OS specific exclusions:
com/sun/management/OperatingSystemMXBean/GetFreePhysicalMemorySize.java
java/nio/channels/FileChannel/directio/WriteDirect.java
java/nio/channels/DatagramChannel/Promiscuous.java
Note :- Openj9 specific exclusions are applicable for jdk11 and later versions whereas z/OS specific exclusions are applicable only for jdk11.

@llxia Could you please review this PR. Thank you.

Thanks @psoujany The above ECA check failed. Did you sign the Eclipse Contributor Agreement (ECA)?https://www.eclipse.org/legal/ECA.php
Also, after this PR, will jdk_mangement  be green? If so, we should re-include jdk_mangement  in https://github.com/adoptium/aqa-tests/blob/master/openjdk/playlist.xml#L865

Thanks @llxia . I signed ECA policy.
By excluding these tests jdk_management couldn't be enabled, as there are few more tests which require fix in testcase other than exclusion, work is still in progress.


During cargo publish, verify that src directory is not modified by the build.rs

A common pitfall when doing build.rs code generation in Rust is to write generated files directly to /src. It may seem fine on the first blush, but it does cause problems when you use such crate as a dependency, because there's an implicit invariant that sources in .cargo/registry  should be immutable. Breaking this invariant sometimes is fine, but sometimes leads to pretty bewildering bugs:

https://github.com/abonander/mime_guess/issues/31
https://github.com/lalrpop/lalrpop/issues/272

So, I think we, first of all, should formally declare and document that build scripts should not modify stuff outside of OUT_DIR. We can enforce this rule during pre-flight check in cargo publish, by making the directory with sources read-only before the build. That is, in this line, we should add an equivalent of chown ua-w -r dst.

Hm, I've tagged this E-mentor, but we haven't really discussed if we want this feature at all. Will bring it up the next cargo team meeting.

(btw is the [I-nominated] flag meant for these situations?)

We've discussed this on the meeting and we do want this feature, hence feature-accepted label.
We've figured out a better strategy to detect this error than making src readonly. During publish, we can calculate a checksum before and after we run cargo build, and complain if they don't match. That way, we'll be able to give a precise error message, which is much better than build.rs panicking with PermissionDenied.
I think DirectorySource in Cargo calculates checksums of directories, so it might be useful. Alternatively, PathSource::fingerprint method could be used: it computes mtimes and not checksums, but mtimes are probably even better, because we will be able to point which files exactly are modified.

This can be closed now: it's been fixed with https://github.com/rust-lang/cargo/pull/5584/.

Hello, I meet a problem due to this:
I'm working on a crate, and need generate code in src only for doc test.
For example, I generate code in src/test_utils/mod.rs, and use it in doc test:
# #[path = test_utils/mod.rs]
# mod test_utils;
use test_utils::xxx

But I cannot publish it recentlty:
error: failed to verify package tarball

Caused by:
  Source directory was modified by build.rs during cargo publish. Build scripts should not modify anything outside of OUT_DIR.
  Changed: /home/louis/rust/.cargo/target/package/fav_utils-0.0.1/src/proto/bili.rs

  To proceed despite this, pass the `--no-verify` flag.

I tried add #[cfg(test)] ahead of Codegen, then it can be published. However, the Codegen can never run during develop.
// build.rs

// This can generate code but cannot be publish
fn main() {
    println!("cargo:warning=Generate some code");
}

// This can publish but cannot generate code
fn main() {
    #[cfg(test)]
    println!("cargo:warning=Generate some code");
}

It will be so kind if anyone can give me a suggestion.

Is there a reason you are generating into src/ rather than $OUT_DIR like encouraged at https://doc.rust-lang.org/cargo/reference/build-script-examples.html#code-generation ?

Thanks! I learnt this way when using tonic.

Is there a reason you are generating into src/ rather than $OUT_DIR
Yes. For example:

// lib.rs
pub trait Foo: MessageFull + Trait {}     //  `MessageFull` is a trait impl by generated Code
pub trait Bar: MessageFull + Trait  {}    // Assume `Trait` needed, and should be manually impl

Now I need write doc test for Foo and Bar.
Since MessageFull is hard to manually impl, so I can only generate it instead of create one in my test. Lets generate struct TestMsg which impl MessageFull for doc test.
And TestMsg should impl Trait, or I cannot impl Foo for it. However, if I don't included the generated code in src, I cannot receive code hint or auto completion when impl Trait for TestMsg, it's not convenient.
Instead, I can do this:
// src/lib.rs
#[cfg(test)]
mod test_utils;

pub trait Trait {}

// src/test_utils/mod.rs
mod impls;
mod generated;

// src/test_utils/impls.rs
use super::generated::TestMsg;
#[cfg(test)]
use crate::Trait;
#[cfg(not(test))]
use my_package_name::Trait;

impl Trait for TestMsg { ... }    // This way, I can get auto completion and code hints

Then I can impl Foo and Bar in doc tests in the way I mentioned before.
In conclude, I need impl a Trait for generated data structure, and also want to include it for code hint and auto completion, so maybe the only way is to put it in src instead of using include! macro.

Maybe I can put generated code and impls in an integration test folder tests/common, and use #[ path = "../tests/common" ] instead of putting it in src/ . Thank you for your inspiration.

But there's one more situation I meet:
I have a xx_core crate that defines many traits useful. And in another crate xx_utils, I need impl those trait for the data structures generated.
In this situation, generated code is part of the crate. Although files are the same before and after build and Codegen changed nothing, cargo publish still reject this situation.

I suddenly understood, How silly I am!!!
I can generated it in OutDir, and include! it, and then impl Traits on it!!!
I'm sorry wasting your time!


docs 2.0.1&1.2.7 release note

Proposed changes
Issue Number: close #xxx

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run buildall


Have batch processor not exit automatically when script completes

Currently, when running FShell with a set of commands loaded from a script file, the interactive interpreter automatically exits the shell upon completion of the script, regardless of whether there is an exit or close command in the script file. While this can be handy when writing simple non-interactive batch scripts, it can present a problem when one wants to put a set of preliminary commands in a batch script but then leave the interactive shell open afterwards so the user can input further commands manually.
As such I propose changing the default behavior of FShell such that the command processor doesn't automatically exit upon completion of a batch process.

In the interest of flexibility, I probably should make this behavior configurable so users of the base classes can decide whether exiting automatically is something they want to do or not depending on their context.


Unique_with does not work??

I've added a rule:
 'name' => 'required|unique_with:templates,organisation_id|min:2'
And I have data:
name='test', organisation_id=2
And when I try to add name='test' with organisation_id 1, it fails.

I can't reproduce the problem. It behaves correctly for me.
Can you give more specific details about your setup?

The organisation_id is part of the user present in $request->user(), it is not being sent as form data.
Using latest stable versions of all packages.

I've changed the rules to be the following:
`$rules = [
'name' => 'required|unique_with:templates,organisation_id|min:2'
];
    $this->merge(['organisation_id' => $this->user()->organisation_id]);

    return $rules;`

But only this is executed in the query:
select count(*) as aggregate from templateswherename = 'test';

Are you using a FormRequest object? What is this merge method you are calling?

I've created a request class using php artisan make:request RequestName.
This creates a class that extends the FormRequest class by default, and has been some time in Laravel ;)
The merge method I'm using is the exact same as having Request $request as a parameter in a method, and then calling $request->merge(['some data' => 'some value']);

Still having issues or can this issue be closed? It worked in my example

The issue is still here.
When doing what I said in my original post:
I've added a rule:
'name' => 'required|unique_with:templates,organisation_id|min:2'
And I have data:
name='test', organisation_id=2
And when I try to add name='test' with organisation_id 1, it fails.

Still fails.

Hi,
I have the same problem but in reverse.
I can rename an organization while another exists and already has the name passed as a parameter.

@tonnevillec please open a new issue with more details and code that shows how you use the library so I can reproduce or advise

@tonnevillec

What version of Laravel and uniquewith-validator do you use?
Please post output of this php artisan tinker snippet:

DB::table('client')->insert(['name' => 'foo-bar', 'owner_id' => 1]);
Validator::make(['name' => 'foo-bar', 'owner_id' => 1], ['name' => 'unique_with:client,owner_id'])->errors();
Validator::make(['name' => 'foo-bar', 'owner_id' => 2], ['name' => 'unique_with:client,owner_id'])->errors();

Laravel 5.2.45
uniquewith 3.0.0
`>>> DB::table('client')->insert(['name'=>'foo-bar', 'owner_id'=>2544]);
=> true

Validator::make(['name'=>'foo-bar', 'owner_id'=>2544], ['name'=>'unique_with:client,owner_id'])->errors();
=> Illuminate\Support\MessageBag {#945}
Validator::make(['name'=>'essai', 'owner_id'=>2544], ['name'=>'unique_with:client,owner_id'])->errors();
=> Illuminate\Support\MessageBag {#946}`

I don't know if it can help. The second test with 'essai' should normaly return an error...

@tonnevillec I would expect foo-bar to be the one causing an error, since you specify the name should be unique in combination with the owner id.
Can you dump what's inside the MessageBag?

... in the messageBag i have the error as expected.
But in my api it doesn't work.
        $this->validate($request, [             'name' => 'required|unique_with:client,owner_id|min:2'         ]);

sorry i found my mistake and it does not depend on uniquewith

Can you elaborate on what went wrong?

Just an error in the call of my owner_id so when I wanted to test the uniqueness of the name for the owner I always had a return "ok" because the couple name / owner did not necessarily exist.

Ok, thanks for the information 👍


I lost my machine block

Due to a bug, when i mined the desert sahara compact block in my compact chamber, the sahara compact block dissapeared. So i need help because i know it has a machine number, but i don't know how to spawn it in.

Hold a CM with the correct size in your hand and type /setCMCoords <room-id> as an OP.


Watching fixes

This PR addresses #2601 and #2685 by making some fundamental changes to the file handling in the CLI:

The CLI now uses file content hashes instead of file modification times to determine whether a file changed. While this is unfortunately a bit slower, the timestamps are unreliable on Windows: Replacing an existing file doesn't change the creation date and retains the modification date of the original file there. This means neither of the timestamps is up to date and Typst thinks the file didn't change.

As pointed out by @Myriad-Dreamin, the PathHash was an unreliable construct throughout multiple compilations. Before 0.9, this wasn't a problem because the resources were all cleared between compilations. The intent of the path hashes was to canonicalize the parsed data for a file if two different paths point to the same file. This was originally important for things like /file.typ and /dir/../file.typ. However, we've since added lexical path normalization which covers most of the cases. For the remaining ones (e.g. symlinks), the duplication is bearable. As a result, the hashes and slots hash maps were replaced with a single HashMap from FileId to FileSlot, which simplifies things quite a lot.

The watching logic was simplified to retrieve the dependencies just once and switched to a single, persistent watched hashmap instead of multiple ad-hoc hashmaps.

I have tested this on macOS and Windows. I would appreciate if people would further test it (especially on Linux) to ensure it works before merging.

Thanks, this works a lot better for me! Unfortunately I did find a bug, though:

Create a new .typ file, and start typst watch on it.
Add a reference to an image that doesn't currently exist, and save. (Typst will show an error in the console.)
Create the image file. (Note: ideally Typst would detect the new file and automatically recompile, but I understand that that's a feature that doesn't exist yet. It's not the bug, anyway.)
Re-save the document to get Typst to recompile.
Edit or replace the image file.

Expected result: Typst detects the change to the image and recompiles.
Actual result: Typst doesn't detect the change.
Based on a few tests, the image initially not existing seems to be an important factor.

Thanks for testing! I think I have an idea what's wrong. Will test later.

I've pushed a commit that should fix this issue.


2 translated media labels outputs a 3rd (default) language

Form source here: https://docs.google.com/spreadsheets/d/1HlxpC4ORzor94WXONUqJXbrrlrsSQAEXdGsiAviM4lU/edit?usp=sharing
The default language has no valid audio src (because it doesn't exist in the XLSForm).
XForm itext output is:
<itext>
    <translation default="true()" lang="default">
        .....
    </translation>
    <translation lang="Russian">
        ......
    </translation>
    <translation lang="Kyrgyz">
       .......
    </translation>
</itext>

But expected itext output is:
<itext>
    <translation lang="Russian">
        .....
    </translation>
    <translation lang="Kyrgyz">
       .......
    </translation>
</itext>

I hadn't thought through this issue and it has come back up as part of https://github.com/XLSForm/pyxform/issues/157 which @lindsay-stevens has been tackling. I wanted to write up a few notes to have a record of some thoughts I've had. I think we should document this behavior better (or at all).
The result of this change is that selects have different translation rules than form controls. It used to be that for any missing language/ui text combination used anywhere, pyxform filled in -. The spec says:

The content should be the same (same set of text ids) but with all strings translated to the new language.

This is enforced by Validate for form controls so that's why the - is filled in. Having the - makes it relatively easy to spot missing translations.
After this change, choice labels and any other media can be omitted for languages as long as one language has a translation. I believe both Collect and Enketo fall back to the topmost language in the itext block.
@MartijnR do you remember any context around this? The particular example you shared seems odd because the default language would get a Kyrgyz recording. It does seem useful in cases like when choices are place names that should be the same across languages. It could lead to hard to spot bugs where languages are accidentally missing.

@MartijnR do you remember any context around this? The particular example you shared seems odd because the default language would get a Kyrgyz recording.

I don't remember and took a trip down memory lane into the annals of the formhub, enketo, odk and kobotoolbox and my email and unfortunately, it didn't reveal a source.
I also cannot quite imagine why you'd not include a media source for every language.

Thanks for taking the trip! 🧳 Hopefully the warnings addressing #157 will make any unintentional missing translations easy to track down so the discrepancy won't matter too much.


gdbstub linking will not fit in iram1_0_seg

I have downloaded the esp-gdbstub repository, compiled the sources and placed them in an archive. When I now try and link the gdbstub archive with me simple C application, I find that I get the error:
a.out section '.text' will not fit in region 'iram1_0_seg'

Running objdump -h over the archive produces the following:
gdbstub.o:     file format elf32-xtensa-le

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .literal      00000000  00000000  00000000  00000034  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 .irom0.literal 00000000  00000000  00000000  00000034  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  2 .text         00001133  00000000  00000000  00000034  2**2
                  CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE
  3 .data         00000008  00000000  00000000  00001168  2**2
                  CONTENTS, ALLOC, LOAD, DATA
  4 .bss          00000128  00000000  00000000  00001170  2**2
                  ALLOC
  5 .rodata       000000aa  00000000  00000000  00001170  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, DATA
  6 .irom0.text   000000c2  00000000  00000000  0000121c  2**2
                  CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE
  7 .comment      00000022  00000000  00000000  000012de  2**0
                  CONTENTS, READONLY
  8 .xtensa.info  00000038  00000000  00000000  00001300  2**0
                  CONTENTS, READONLY
  9 .xt.lit       000000b8  00000000  00000000  00001338  2**0
                  CONTENTS, RELOC, READONLY
 10 .xt.prop      00000be8  00000000  00000000  000013f0  2**0
                  CONTENTS, RELOC, READONLY

gdbstub-entry.o:     file format elf32-xtensa-le

Sections:
Idx Name          Size      VMA       LMA       File off  Algn
  0 .literal      00000000  00000000  00000000  00000034  2**2
                  CONTENTS, ALLOC, LOAD, READONLY, CODE
  1 .text         0000023f  00000000  00000000  00000034  2**2
                  CONTENTS, ALLOC, LOAD, RELOC, READONLY, CODE
  2 .data         00000000  00000000  00000000  00000273  2**0
                  CONTENTS, ALLOC, LOAD, DATA
  3 .bss          00000000  00000000  00000000  00000273  2**0
                  ALLOC
  4 .xtensa.info  00000038  00000000  00000000  00000273  2**0
                  CONTENTS, READONLY
  5 .xt.lit       00000008  00000000  00000000  000002ab  2**0
                  CONTENTS, RELOC, READONLY
  6 .xt.prop      00000144  00000000  00000000  000002b3  2**0
                  CONTENTS, RELOC, READONLY

Has anyone run up against this puzzle before?
Also posted to the forum here:
http://bbs.espressif.com/viewtopic.php?f=7&t=1424

What 'simple application' do you use? Do you use RTOS or non-RTOS?
Gdbstub neccesarily does use some IRAM, because the program may be interrupted or crashing when the flash isn't accessible.

Attached is the sample file ... it is 100 lines of source.
test.txt

I've just been trying to get this to compile as well, and haven't tested yet, but I got this issue when the 'use own stack' option was set. Using non-os sdk.


[This plugin] 129 is detected on pixelscan.net as automation framework

How to reproduce:

Use  playwright-with-fingerprint (do not use BAS windows application)
visit pixelscan.net, it will show flagged as automation framework.

This is is tested on latest playwright-with-fingerprints, chromium 129, engine 27.9.2
This issue appeared since 127

My code:
require('dotenv/config');
const { plugin } = require('playwright-with-fingerprints');
plugin.setServiceKey(process.env.FINGERPRINT_KEY);

(async () => {
  const fingerprint = await plugin.fetch({
    tags: ['Microsoft Windows', 'Chrome'],
    minBrowserVersion: '128', // the 'current' value works too.
    maxBrowserVersion: '128', // the 'current' value works too.
  });

  plugin.useProxy(process.env.FINGERPRINT_PROXY, {
    ipInfoMethod: 'ip-api.com',
    changeGeolocation: true,
    changeTimezone: true,
  });
  plugin.useFingerprint(fingerprint);

  const browser = await plugin.launch({ headless: false });

  const page = await browser.newPage();
  await page.goto('https://pixelscan.net', { waitUntil: 'commit' });
})();

My result №1 (128 version):

My result №2 (129 version):

I checked about 10 fingerprints - the maximum problem I encountered was incorrect geolocation, but this can be fixed by using another IP data detection service.

My code:
require('dotenv/config');
const { plugin } = require('playwright-with-fingerprints');
plugin.setServiceKey(process.env.FINGERPRINT_KEY);

(async () => {
  const fingerprint = await plugin.fetch({
    tags: ['Microsoft Windows', 'Chrome'],
    minBrowserVersion: '128', // the 'current' value works too.
    maxBrowserVersion: '128', // the 'current' value works too.
  });

  plugin.useProxy(process.env.FINGERPRINT_PROXY, {
    ipInfoMethod: 'ip-api.com',
    changeGeolocation: true,
    changeTimezone: true,
  });
  plugin.useFingerprint(fingerprint);

  const browser = await plugin.launch({ headless: false });

  const page = await browser.newPage();
  await page.goto('https://pixelscan.net', { waitUntil: 'commit' });
})();

My result №1 (128 version):

My result №2 (129 version):

I checked about 10 fingerprints - the maximum problem I encountered was incorrect geolocation, but this can be fixed by using another IP data detection service.

but what engine version did you use? fingerprint version doesnt matter, u must use engine >= 27.8.1

@dr3adx i use the latest one, currently it's 27.9.2.

You are using the 127 engine, but you are requesting the 128 version of the browser. This is not critical, but ideally the fingerprint should match the engine version.
The critical thing (for me) in your code is that you are requesting an Android fingerprint, while you have not reported anywhere that the problem is with the emulation of a mobile device.

I'll try to figure out what the problem is.

@CheshireCaat sorry I had pasted wrong code because I tested so many versions, its corrected now. It only happens when using engine >= 128.0.6613.85 (127 and below works) and looks like you're right it only happens on Android fingerprint


autoreflection & more

Changes:

add autoreflection models
add relationship_fields attribute in meta
improve lazyness of metaclasses
make metadata of registry lazy again
partial updates of metrics
refactor inspect migrations

The docs are not optimal, but we can improve them later

The docs are not optimal, but we can improve them later

Later when? Why not now?

ok I improved the docs and migrated to python 3.9 +


fix(autocomplete): top option group not scrolled into view when going up

Fixes the case where the user won't be able to see the top option group when reaching the first option via the arrow keys.

I'd say so @josephperrott. Currently when you're going from below and you hit the top option, you can't see which group it's a part of.

@crisbeto to either rebase or re-open this PR

Closing in favor of https://github.com/angular/components/pull/16343.


Virustotal results 16 / 67

https://www.virustotal.com/#/file/dd441446b2f44547a6a63f3beaacae51fb6ff26a48d09149908bf9c778efc95c/detection
Why is this?

But you can report this to them as a false positive.

The newer version is reported as safe. For the older version I'd suggest everyone who gets here goes to https://www.virustotal.com/#/file/2e760fd512781c532b6a3d9c0a26816d01a8c89a10b6f046e958d184eecdc232/community and votes Safe.


Curve and Performance should expose the same API

 Issue by Hixie
Wednesday Oct 21, 2015 at 16:48 GMT
Originally opened as https://github.com/flutter/engine/issues/1708

An AnimatedPerformance is a ticker plus forward()/reverse() methods, and exposes a value in the range 0..1 plus a direction and a change notification API.
A Curve should just be something that takes a value in the range 0..1 plus a direction and a change notification API, and exposes a value in the range 0..1 plus a direction and a change notification API (that it transparently forwards to the input's change notification API).
This would mean we would only need to accept one type rather than accepting a performance plus a curve everywhere, and consumers could chain performances and curves however they wanted. It would also mean you could have a "performance" that was slaved to another kind of input than a ticker.

and Simulations too!

PerformanceView should lose updateVariable and curveDirection.
AnimatedValue should lose its curves. Instead it takes a PerformanceView, begin, and end, and just asks the performance view it's given for its progress and linearly lerps from begin to end with that value.
Curves are then done as new classes that implement PerformanceView and take a PerformanceView. One of these classes would just apply a curve to the parent's value, forwarding all other calls through. Another would take two curves and remember what direction it's going in.

see also https://github.com/flutter/flutter/issues/216 https://github.com/flutter/flutter/issues/253 https://github.com/flutter/flutter/issues/218

Some ideas:
abstract class Watchable {
  void addListener(...);
  void removeListener(...);
  void addStatusListener(...);
  void removeStatusListener(...);
  Status get status;
  Direction get direction;
}

abstract class HasProgress extends Watchable {
  double get progress;
  void attach(Attachable child) {
    child._setParent(this);
  }
}

abstract class Attachable {
  HasProgress get parent => _parent;
  HasProgress _parent;
  void _setParent(HasProgress parent) {
    assert(!attached);
    _parent = parent;
  }
  bool get attached => _parent != null;
}

abstract class HasValue<T> {
  T get value;
}

// concrete classes

class AController with HasProgress {
  // owns a ticker, simulation, etc
  // play, forward, reverse, fling, etc
  // progress updated by ticker
}

class ACurve with HasProgress, Attachable {
  // curve, reverseCurve
  double get progress => parent.progress adjusted by relevant curve;
}

class AValue<T extends dynamic> with Watchable, Attachable implements HasValue<T> {
  // begin, end
  T get value => lerp(parent.progress, begin, end);
}

class ARectValue with Watchable, Attachable implements HasValue<Rect> {
  // begin, end
  Rect get value => Rect.lerp(parent.progress, begin, end);
}

class ADoubleValue with HasProgress, Attachable implements HasValue<double> {
  // begin, end
  double get value => lerpDouble(parent.progress, begin, end);
  double get progress => value;
}

So:
class ProgressIndicatorAppState extends State<ProgressIndicatorApp> {
  void initState() {
    super.initState();
    valueController = new AController(duration: const Duration(milliseconds: 1500));
    valueAnimation = valueController.attach(new ACurve(
      curve: const Interval(0.0, 0.9, curve: Curves.ease),
      reverseCurve: Curves.ease
    )).attach(new ADoubleValue(
      begin: 0.0,
      end: 1.0
    ));
    valueController.addStatusListener((PerformanceStatus status) {
      if (status == PerformanceStatus.dismissed
          || status == PerformanceStatus.completed)
        reverseValueAnimationDirection();
    });
    valueController.play(valueAnimationDirection);
  }
  // ...
  // use valueAnimation.value to get the current value in the build function

The plan is to try implementing the suggestion above and then comparing it to the approach in #1078 to make a decision on how to proceed.

I'm a little unsure about the handling of direction in the current APIs. Direction makes sense for things that are driven by time, but if the driver is arbitrary, then direction makes less sense.  I.e. you could have a Curve that maps randomly distributed inputs to randomly distributed outputs and still have the notion of "shape", but "direction" is kind of meaningless.
I believe Performance is the earliest part of the class hierarchy where time is introduced, so I'm wondering if direction as a concept should be removed from everything above it (i.e. removed from PerformanceView and Curve).

Interesting idea.  We should look at the clients of PerformanceView to see how many of them care about direction.  The hero transitions do (in order to decide which heros to select).  I'm not sure what else cares.

One big use of direction is having a different curve when going forward
than going backward. The other big use is knowing if you've reached the
"dismissed" state vs the "completed" state (though that's built into
Performance itself).
On Mon, Jan 11, 2016 at 3:35 PM Adam Barth<EMAIL_ADDRESS>wrote:

Interesting idea. We should look at the clients of PerformanceView to see
how many of them care about direction. The hero transitions do (in order to
decide which heros to select). I'm not sure what else cares.
—
Reply to this email directly or view it on GitHub
https://github.com/flutter/flutter/issues/215#issuecomment-170732562.

I'm looking at these APIs at the moment with an eye toward having a PerformanceView that's driven by input events. In that context it's a little unclear why direction is useful.  You reach the dismissed state if you end at 0.0 progress and the completed state if you end at 1.0 progress, but in the middle you might drift back and forth.  In that context having two different curves for going forward vs. backward is a little weird because you would (in the general case) have two different possible outputs for a given mid-interval input, so you'd get discontinuities if you switched back and forth.

Note, I'm not saying the use cases you mention aren't valuable, just that they're not necessarily universal; so they would go better in subclass(es) than base class(es).

As implemented, you never switch curves in the middle. You only switch curves if you hit the end.


Metadata json file at publication

Following merged PR #383 for TEST

Issue: https://github.com/hubmapconsortium/ingest-api/issues/375


0.16 - Exception 'ResultSet is closed' is thrown for PageResult from createPageQuery used in a mapper

There is a problem when PageResult is used in a mapper and EntityXYXDto has a list with some data from a joined table. Explicite added Transaction works but it works different compare to Quarkus 1.x with tkit-JPA plugins. Have you encountered similar behaviour?

public class EntityXYXDto {
    private String name1;
    private String name3;
    private List<JoinedData> JoinedData;
}

public class XYZPageResultDto extends PageResultDTO<EntityXYXDto> {
}

//controller
XYZPageResultDto pageResultDto = mapper.mapDto(service.findBySearchCriteriaPagedXYZ(searchCriteriaDto));

//service
public PageResult<EntityXYZ> findBySearchCriteriaPagedXYZ(SearchCriteriaDto dto) {
    return dao.findBySearchCriteriaPagedXYZ(dto);
}
//dao
public PageResult<EntityXYZ> findBySearchCriteriaPagedXYZ(dto) {
    CriteriaBuilder cb = this.em.getCriteriaBuilder();
    //...
    return createPageQuery(cq, Page.of(dto.getPageNumber(), dto.getPageSize())).getPageResult();
}

2023-07-24 14:59:44,542 ERROR [XYZController] (executor-thread-0) Before mapper: 2023-07-24 14:59:44,543 WARN  [org.tki.qua.jpa.dao.PagedQuery] (executor-thread-0) Paged query used without explicit orderBy. Ordering of results between pages not guaranteed. Please add an orderBy clause to your query. 2023-07-24 14:59:44,543 WARN  [org.tki.qua.jpa.dao.PagedQuery] (executor-thread-0) Default sorting by 'id' attribute is added. 2023-07-24 14:59:44,548 WARN  [org.hib.eng.jdb.spi.SqlExceptionHelper] (executor-thread-0) SQL Error: 0, SQLState: null 2023-07-24 14:59:44,548 ERROR [org.hib.eng.jdb.spi.SqlExceptionHelper] (executor-thread-0) ResultSet is closed

@forszpanen example project where we can reproduce this issue would be good. PR to fix this issue is welcome.

Hi, I have just created a new quarkus project that reproduces this issue. Please consider updating database information and add at least 1 row to each table.
https://gitlab.com/bartosz.kowalski.capgemini/resultset

@bartosz-kowalski-capgemini this is not an issue of PageResult
You have parent-child (child is lazy) model which is directly use in the rest-controller.
In your case, Jackson will try to use getChildren method, but the children are not loaded, and the database transaction is close.


Update cloning-a-repository.md

Why: when I read that paragraph it became unclear to me because the sentence is not clear enough
Closes [issue link]

What's being changed: I edited a bit the sentence so it becomes clearer

Check off the following:

[ ] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[v ] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

@yaakovab
Thanks so much for opening a PR! I'll get this triaged for review :zap:

The preview looks good, Cloning a repository, so this is ready to merge 🚀

so is it updated automatically? or should i do something?
בתאריך יום ג׳, 22 בפבר׳ 2022 ב-13:22 מאת Felicity Chapman <
@.***>:

The preview looks good, Cloning a repository
https://docs-preview-15691-9401b1.eastus.azurecontainer.io/en/repositories/creating-and-managing-repositories/cloning-a-repository#troubleshooting-cloning-errors,
so this is ready to merge 🚀
—
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/15691#issuecomment-1047694983, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ATBC52WA7HTAM2YR5GE7IBTU4NWWZANCNFSM5O6ZQ4OQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

My apologies for my unclear message @yaakovab 😞
I've set this PR to merge automatically when the tests pass 🚀

Thanks for the quick response!!
On Tue, Feb 22, 2022, 13:44 Felicity Chapman @.***>
wrote:

My apologies for my unclear message @yaakovab
https://github.com/yaakovab 😞
I've set this PR to merge automatically when the tests pass 🚀
—
Reply to this email directly, view it on GitHub
https://github.com/github/docs/pull/15691#issuecomment-1047712683, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ATBC52TADOT25HGNCDL5PGTU4NZK5ANCNFSM5O6ZQ4OQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks for your help fixing this problem in the docs 💖


"Couldn't run Less Parser" error message

Hello,
Really wanted to try this plugin, unfortunately every time I try to use it, I get the error message, saying "Couldn't run Less Parser" .
Is there any workaround for this problem?
System is El Capitan 10.11.2 Beta, Mac mini, Sketch Version 3.4.2
Installed it by double-clicking the CSSketch.sketchplugin.
Thanks!

I have the same problem, while trying to load a normal CSS file (no LESS CSS) as the page's stylesheet. Maybe because of the Sketch update?

Same here. Wanted to try it, doesn't work, uninstall :(

Same, any thoughts?


Questions regarding ifctoCitygml3.0

hello.
I successfully converted ifc to citygml3.0 using this github material.
However, the converted citygml is not displayed in 3D format.
I'm trying to view it with fme data inspector.
Is there anything I need to configure?

@TatjanaKutzner
Please help me.
I have a task to convert ifc to citygml.
I need your help.
Is there a way to keep in touch for a long time?


[Bug] upgrade elasticsearch jar due to cve

What happened
dependabot analysis
https://github.com/advisories/GHSA-3393-hvrj-w7v3 (and one other)
What you expected to happen
n/a
How to reproduce
n/a
Environment
No response
InLong version
master
InLong Component
InLong Manager
Are you willing to submit PR?

[X] Yes, I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

this seems to be fixed already


[Windows] UI Updates for Add Host

Rancher versions:
rancher/server: v1.6.13-rc3
Environment Template: (Cattle/Kubernetes/Swarm/Mesos)
Windows
UI Updates
[ ] Remove the Windows Host text.

[ ] Step 1: Similar to the Linux Add Host page, we should refer to the latest supported versions of Docker. We should update the Docs to include what is supported for Windows.
http://rancher.com/docs/rancher/v1.6/en/hosts/#supported-docker-versions

[ ] Step 2: Make a note that the Windows machine will need to be rebooted if the applications were installed.
[ ] Step 3: Change the text to Specify a unique subnet for the Windows host. In order to support an overlay network in Windows, each host in the environment must have a unique subnet.
[ ] Step 4: Change the text to Specify the router IP for the host's subnet. This IP is used to forward network traffic between the different hosts.

Available with v1.6.13-rc4

Text is updated in v1.6.13-rc4


gPC ROM generated using SparseGridCollocation with Gamma distribution is not working correctly

Issue Description
What did you expect to see happen?
The gPC ROM generated using SparseGridCollocation with Gamma distribution should generate similar results with MonteCarlo
What did you see instead?
The predicted value from gPC does not agree with the Code executions, the inputs are youngsModulus, and force. The outputs are disp_x, and disp_y.
Results from Code:
youngsModulus,force,disp_x,disp_y
176574.579712,-132.140792122,0.0254384584278,-0.172387649733
425755.525175,-7.85914919469,0.000627476268902,-0.0042521900282
190033.125005,-83.1397770671,0.0148717340472,-0.100780606935
210154.666871,-14.6123587696,0.00236354215596,-0.0160169091405
231284.205188,-43.5948157121,0.00640723917344,-0.0434196476773
267340.506387,-266.852951695,0.0339304257776,-0.229934780476

Results from gPC:
youngsModulus,force,disp_x,disp_y
176574.579712,-132.140792122,5.47380623359e-09,-3.70940949265e-08
425755.525175,-7.85914919469,1.40689665974e-10,-9.53405290966e-10
190033.125005,-83.1397770671,3.17405035702e-09,-2.15094433782e-08
210154.666871,-14.6123587696,4.97911911674e-10,-3.37417711342e-09
231284.205188,-43.5948157121,1.33521875082e-09,-9.04831646883e-09
267340.506387,-266.852951695,7.05075070558e-09,-4.7780503148e-08

If I change the Gamma distribution to Normal or using NDspline ROM with Monte Carlo, both will generate similar results compared to the code outputs.
Do you have a suggested fix for the development team?
I guss the problem is scaling/normalization factors for the polynomial coefficients.
Please attach the input file(s) that generate this error.  The simpler the input, the faster we can find the issue.
tests.zip

For Change Control Board: Issue Review
This review should occur before any development is performed as a response to this issue.

[x] 1. Is it tagged with a type: defect or improvement?
[x] 2. Is it tagged with a priority: critical, normal or minor?
[x] 3. If it will impact requirements or requirements tests, is it tagged with requirements?
[x] 4. If it is a defect, can it cause wrong results for users? If so an email needs to be sent to the users.
[x] 5. Is a rationale provided? (Such as explaining why the improvement is needed or why current code is wrong.)

For Change Control Board: Issue Closure
This review should occur when the issue is imminently going to be closed.

[ ] 1. If the issue is a defect, is the defect fixed?
[ ] 2. If the issue is a defect, is the defect tested for in the regression test system?  (If not explain why not.)
[ ] 3. If the issue can impact users, has an email to the users group been written (the email should specify if the defect impacts stable or master)?
[ ] 4. If the issue is a defect, does it impact the latest stable branch? If yes, is there any issue tagged with stable (create if needed)?
[ ] 5. If the issue is being closed without a merge request, has an explanation of why it is being closed been provided?

@wangcj05 @PaulTalbot-INL who is taking this?

An email for the users should be drafted noting the problem and the fix.

@PaulTalbot-INL Here it is.
Proposed Email:
Dear Users,
We recently realized that there was a defect in the SparseGridCollocation Sampler when Gamma distribution is employed as described in issue #693. This issue has been resolved with the PR#713 and the modification is currently available in the devel branch.

Email accepted... and checklist passed...


Very informative!

I try to make cross compile another Rust thing (RedisJSON plugin) but should use specific GLIBC. When compile it in docker I'd receive GLIBC_2.29 on target is libc_2.24.so
Do you have idea how to tell cargo build to use sepcific version of libc ?
PS: Something like that ?
https://capnfabs.net/posts/cross-compiling-rust-apps-linker-shenanigans-multistrap-chroot/#:~:text=Some quick googling reveals that this should be fixable by telling the gcc linker to look in a different system root. We can tell cargo to tell rustc to tell gcc to tell the linker (😅) to do that by setting the CARGO_TARGET_<triple>_RUSTFLAGS environment variable in the Dockerfile%3A

Hey @TopperBG! I don't actually know; all I'd be able to do here is google it. The advice I've seen there (and I think something I might've tried with spotifyd?) was to try compiling with musl instead but I don't think that works with dynamic (.so) libraries which require glibc themselves.
Going to close the issue here because this repo is a proof-of-concept, but good luck getting this resolved!


[turborepo] Unable to install package using a fresh create-turbo

What version of Turborepo are you using?
create-turbo v1.7.2
What package manager are you using / does the bug impact?
Yarn v1
What operating system are you using?
Windows
Describe the Bug
This bug happens with both yarn and npm.
I'm trying to initialize a new monorepo using npx create-turbo@latest, but always face the following error.
D:\github>npx create-turbo@latest

>>> TURBOREPO

>>> Welcome to Turborepo! Let's get you set up with a new codebase.

? Where would you like to create your turborepo? ./my-turborepo
? Which package manager do you want to use? yarn

>>> Created a new turborepo with the following:

 - apps/web: Next.js with TypeScript
 - apps/docs: Next.js with TypeScript
 - packages/ui: Shared React component library
 - packages/eslint-config-custom: Shared configuration (ESLint)
 - packages/tsconfig: Shared TypeScript `tsconfig.json`

>>  Installing dependencies...
Aborting installation.
  yarn install has failed. // also for npm

The folder is created properly, but the package installation process fails. When I navigate to the monorepo and run npm/yarn install manually, the following errors happen.
// yarn
D:\github\my-turborepo>yarn install
yarn install v1.22.19
info No lockfile found.
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
error An unexpected error occurred: "EISDIR: illegal operation on a directory, symlink 'D:\\github\\my-turborepo\\apps\\docs' -> 'D:\\github\\my-turborepo\\node_modules\\docs'".
info If you think this is a bug, please open a bug report with the information provided in "D:\\github\\my-turborepo\\yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

// npm
D:\github\my-turborepo>npm install
npm ERR! code EISDIR
npm ERR! syscall symlink
npm ERR! path D:\github\my-turborepo\apps\web
npm ERR! dest D:\github\my-turborepo\node_modules\web
npm ERR! errno -4068
npm ERR! EISDIR: illegal operation on a directory, symlink 'D:\github\my-turborepo\apps\web' -> 'D:\github\my-turborepo\node_modules\web'

npm ERR!      C:\Users\concc\AppData\Local\npm-cache\_logs\2023-02-03T05_31_10_353Z-debug-0.log

I also tried pnpm, but my system is having another issue preventing the usage of pnpm, as reported here: https://github.com/pnpm/pnpm/issues/6014. It may be related.
Expected Behavior
npx create-turbo@latest should be successful out of the box.
To Reproduce
Run npx create-turbo@latest.
Additional information

yarn and npm work normally on my other projects, only turborepo has this issue,
As for the errors related to a directory, I tried running npx create-turbo@latest on C drive, and it was a success. At the moment, I store all my projects in a shared drive on a dual boot (Windows 11/PopOS) system. This might give some clues.

Reproduction Repo
N/a

@hunghvu can you verify that you can symlink directories on this drive? This functionality is necessary to use workspaces in npm and yarn.

@chris-olszewski Good question, and it let me learn that exFAT (which I used for dual boot) does not natively support symlink (exFAT -> exFAT), hence the error. I suppose the docs can be updated with this information so other newcomers can know.
Or maybe, the CLI can replace yarn/npm install has failed with something more indicative in this scenario.

I'm closing this as we already call out that workspaces are symlinked and I think it would be too fragile to depend on the error logs of yarn and npm.


Publish container images for ARM

Docker support for cross-compiling multi-platform images is fairly straightforward which means we could provide pre-built images for ARM without adding self-hosted ARM based runners.

Support was added with https://github.com/ThinkParQ/beegfs-containers/pull/15.


x/net/quic: Signal unsupported for key-update interop test

Proposal Details
Based on https://interop.seemann.io/, go-x-net doesn't seem to support key updates. Please signal this to the runner by returning unsupported for this interop test case.

CC @neild

x/net/quic does support key updates. I think the problem may be that the client initiates the first update later in the connection than the interop runner wants. (After 1000 packets, and the interop test wants an update in the first megabyte of data transferred.)

OK, so as far as the interop runner is concerned, that is then lack of support for the test. I'd suggest you either do the key update earlier during the test, or mark it as unsupported?

I believe this used to pass, but probably broke after https://go.dev/cl/564476, which reduces the total number of packets sent by the client in this test configuration under the 1000 packet threshold.
It's a bit weird to set the key rotation policy specifically to make this test pass, but 1000 packets is a completely arbitrary number anyway, so just always rotating earlier might be simplest.

Most other clients pass the test name in via a command line option, and then configure their default behavior as needed. Might want to do that too?

We intentionally have few configuration parameters, and the interop client uses the public package API. So the question is how we'd configure this.
Probably through a GODEBUG setting, but we don't have any GODEBUGs that adjust behavior at the moment so adding one would be a reasonably significant change.


Stereo audio source imports as mono

When I use a stereo audio file (only tried FLAC) as reference (HQ audio source), the resulting Vegas track is always in mono. The only way to fix this, is to export everything as an EDL and reimport the project via EDL.
from vegas forum

I've discovered that final pro 7 projects exported from Davinci also import as mono tracks inside Vegas!

Fixed in v1.3


EventCallback problem with abstract types

Is there an existing issue for this?

[X] I have searched the existing issues

Describe the bug
When I create a component containing bindable property that uses generic ICollection the EventCallback gives me an error:
cannot convert from 'Microsoft.AspNetCore.Components.EventCallback<System.Collections.ObjectModel.ObservableCollection<int>>' to 'Microsoft.AspNetCore.Components.EventCallback'
Home.razor
@page "/"
@using System.Collections.ObjectModel

<TestComponent TValue="int" @bind-Values="Values" />

@code{
    public ObservableCollection<int> Values { get; set; } = new(){1,2,3};
}

TestComponent.razor
@using System.Collections.ObjectModel
@typeparam TValue where TValue : notnull

TestComponent

@code {
    [Parameter] public ICollection<TValue> Values { get; set; } = new Collection<TValue>();
    [Parameter] public EventCallback<ICollection<TValue>> ValuesChanged { get; set; }
}

Probably related issues:
https://github.com/dotnet/aspnetcore/issues/17480
https://github.com/dotnet/aspnetcore/issues/8385
Expected Behavior
It should simply work. Because ObservableCollection is inheriting from ICollection.
When I try e.g.
var obs = new ObservableCollection<int>() { 1,2,3};;
var changed = (ICollection<int>) obs;

it works ofc.
Steps To Reproduce
Just build the project:
https://github.com/Kebechet/Bug.Blazor.EventCallback
Exceptions (if any)
No response
.NET Version
8.0.101
Anything else?
No response

This behavior looks correct. Although one can assign ObservableCollection to ICollection, it doesn't work the other way around. So you can assign your ObservableCollection to the component like this:
<TestComponent Values="Values" />

But you shouldn't be able to use @bind because then the component would be able to assign its ICollection to your ObservableCollection property which cannot work in general.
In other words, the TestComponent can call the ValuesChanged callback with any ICollection, e.g., List - it doesn't have to be ObservableCollection. Then in Home.razor, that changed value might not be assignable to your Values property.
I imagine we could allow this (with a warning) and instead fail at runtime with invalid cast exception if the wrong type is passed via the callback. But that would be a feature request, not a bug (a separate issue should be opened if that's desired).


New Textobj: indentation textobj from https://github.com/kana/vim-textobj-indent has -> indentation breaked by different indentation

Textobj requested
I lack indentation textobj from https://github.com/kana/vim-textobj-indent
Sample Text
in
      mappings = {

        -- Textobjects
        object_scope = 'ii',
        object_scope_with_border = 'ai',

        -- Motions (jump to respective border line; if not present - body line)
        goto_top = ',K',
        goto_bottom = ',J',

      },

Inner/Outer Difference
cursor on [o]bject_scope
vii should select
      mappings = {

[       -- Textobjects
        object_scope = 'ii',
        object_scope_with_border = 'ai',]

        -- Motions (jump to respective border line; if not present - body line)
        goto_top = ',K',
        goto_bottom = ',J',

      },

vai should select
      mappings = {
[
        -- Textobjects
        object_scope = 'ii',
        object_scope_with_border = 'ai',

        -- Motions (jump to respective border line; if not present - body line)
        goto_top = ',K',
        goto_bottom = ',J',
]
      },

Vimscript plugin already implementing the textobj
https://github.com/kana/vim-textobj-indent
Filetypes
all
Checklist

[X] The textobj would be useful to more users than just me. (You can use the API to create custom textobj.)

yes https://github.com/kiyoon/treesitter-indent-object.nvim/issues/1#issuecomment-1692816987

[X] There is no lua plugin already implementing the textobj in an adequate manner.

yes https://github.com/echasnovski/mini.nvim/issues/1233#issuecomment-2360813288

[X] I read the docs and checked that there is no such textobj already.

actually, this is accomplished with this config, TNX!!!
return {
  "chrisgrieser/nvim-various-textobjs",
  event = "BufRead",
  config = function()
    vim.keymap.set(
	    { "o", "x" },
	    "ii",
	    '<cmd>lua require("various-textobjs").indentation("inner", "inner", "noBlanks")<CR>'
    )
    vim.keymap.set(
	    { "o", "x" },
	    "ai",
	    '<cmd>lua require("various-textobjs").indentation("inner", "inner")<CR>'
    )
  end,
}


Specular and diffuse

specular & diffuse coefficients estimation oer panel (EarthOrbiter example included but not necessary)

Hi @kimonito98, let me know if this is ready to merge or not. Looking forward to getting this into Tudat!


Tried sending file from desktop to android and got “error NULL”

title

Where did you see this error - on Android or on the desktop?

The error is on the phone. It's not possible to receive any files. Download folder does not generate automatically, after manual creation no files saved there, too.

The error is on the phone. It's not possible to receive any files. Download folder does not generate automatically, after manual creation no files saved there, too.

Exactly this.


With 2 tabs opened side-by-side (same window), if I hit 'shift+enter' while focusing on the right screen, it crashes.

Issue Type: Bug
With 2 tabs opened side-by-side (same window), if I hit 'shift+enter' while focusing on the right screen, it crashes.
Extension version: 2020.9.114305
VS Code version: Code 1.50.1 (d2e414d9e4239a252d1ab117bd7067f125afd80a, 2020-10-13T14:53:05.704Z)
OS version: Darwin x64 19.6.0

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2800)

GPU Status
2d_canvas: enabledflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmetal: disabled_offmultiple_raster_threads: enabled_onoop_rasterization: enabledopengl: enabled_onprotected_video_decode: unavailable_offrasterization: enabledskia_renderer: disabled_off_okvideo_decode: enabledwebgl: enabledwebgl2: enabled

Load (avg)
2, 2, 2

Memory (System)
16.00GB (5.62GB free)

Process Argv
--crash-reporter-id c356e7f2-5d3f-47c8-ab26-3faf31756f64

Screen Reader
no

VM
0%

Hi @leiterenato, thank you for reaching out.
We investigate issues in order based on priority and severity, which includes the impact it has on your ability to use the extension to do productive work, and the number of people affected. If other users come forward and leave a comment demonstrating they are seeing/reproducing the problem then we will raise this issue's priority.
I couldn't repro the issue you encountered, please provide more details:

was it the same file open in both tabs?
do you have sample code that we can use to reproduce the issue?
if you move the file from the right tab to the left tab and do shift+enter, does it crash as well?

Thanks!

Hi Kim,

No, it was different files.
Unfortunately no.
When I quit the "split" view with 2 tabs side-by-side and put all file in the sale pane, it stopped crashing.

Unfortunately I am not able to reproduce the error again (sorry).
Maybe we can close this issue and if it happens again I will collect more data.
Thank you!

Sounds good 👍  Feel free to leave a comment here or open a new issue if the problem reoccurs.


This crate says it's no_std but actually isn't (switch to no_std compatible FFT crate)

This crate's main dependency, rustfft, unconditionally requires the standard library and therefore (despite the #![no_std] in lib.rs) the spectrum_analyzer crate actually isn't no_std.
The easiest way to check this is by finding a target that doesn't have a standard library (I used thumbv7em-none-eabihf - a common STM32 chi[) and running cargo check.
$ rustup target add thumbv7em-none-eabihf
info: downloading component 'rust-std' for 'thumbv7em-none-eabihf'
info: installing component 'rust-std' for 'thumbv7em-none-eabihf'

$ cargo check --target thumbv7em-none-eabihf
    Checking num-traits v0.2.14
    Checking log v0.4.14
error[E0463]: can't find crate for `std`
  --> /home/michael/.cargo/registry/src/github.com-1ecc6299db9ec823/num-traits-0.2.14/src/lib.rs:21:1
   |
21 | extern crate std;
   | ^^^^^^^^^^^^^^^^^ can't find crate
   |
   = note: the `thumbv7em-none-eabihf` target may not be installed

error: aborting due to previous error

The error in that message points to num-traits, but that's not an issue because num-traits has a std feature you can disable.
The problem is that the following crates aren't no_std and don't provide an enabled-by-default std feature for controlling the std feature of its dependencies:

rustfft
primal_check

Oh dang! Thanks for pointing this out! But I guess there is an FFT implementation that is really no_std out there. I will look for one soon and then evaluate performance differences and eventually replace the fft library or make this feature-dependent.

@Michael-F-Bryan quick solution will be to use the complex functions in https://docs.rs/microfft/. I compared the results and it looks promising. Also, microfft internally compares it's results in tests against rustfft. With that, this crate should be finally really no_std.
Long-time idea: Add Cargo features and enable switching the FFT implementation (including STD-variants)

Thanks for looking into this @phip1611.
I ended up adapting an implementation from Rosetta Code to our constraints (no allocations at runtime) so we don't have an urgent need for it.
I like the idea of using cargo features for enabling/disabling different implementations depending on their trade-offs. I could see you having something like this in your lib.rs:
// lib.rs

// Expose nice wrappers around both implementations
#[cfg(feature = "rustfft")]
mod rust;
#[cfg(feature = "microfft")]
mod micro;

// then provide a sane default they can use which will prefer the
// most performant implementation depending on the enabled
// features.
cfg_if::cfg_if! {
  if #[cfg(feature = "rustfft")] {
    pub use rust::samples_fft_to_spectrum;
  } else if #[cfg(feature = "microfft")] {
    pub use micro::samples_fft_to_spectrum;
  }
}

@Michael-F-Bryan  Unfortunately it seems like this is not trivial because "microfft" has a constellation of dependencies which results in this bug:
https://gitlab.com/ra_kete/microfft-rs/-/merge_requests/11
This bug is also in my crate if I use microfft as dependency, i.e. it's transitive. And just adding resolver = "2" results in other problems.
TL;DR: the code works but it doesn't build because of a Cargo bug. 🤔

next release will compile and work on no_std, but it still needs an allocator

I ended up adapting an implementation from Rosetta Code to our constraints (no allocations at runtime) so we don't have an urgent need for it.

@Michael-F-Bryan Could you please share that please implementation? I'm looking for a fully no_std and no alloc crate and so far this mention of yours is the closest I've found after browsing github/crates.io/lib.rs :)

@brainstorm it's been a while, but I think I was referring to this code: https://github.com/hotg-ai/spectrogram-computer/blob/master/src/fft.rs

@brainstorm it's been a while, but I think I was referring to this code: https://github.com/hotg-ai/spectrogram-computer/blob/master/src/fft.rs

404 :-S

Sorry, looks like that repo is private. Here's the source code:
use alloc::vec::Vec;
use core::f64::consts::PI;
use num_complex::Complex;

pub fn fft(samples: &[i16], _sample_rate: usize) -> Vec<i16> {
    let samples: Vec<_> = samples
        .iter()
        .map(|sample| normalize(*sample))
        .map(|sample| Complex::new(sample, 0.0))
        .collect();

    let mut buffer_a = Vec::new();
    let mut buffer_b = Vec::new();

    let frequency_domain = raw_fft(&samples, &mut buffer_a, &mut buffer_b);

    frequency_domain
        .iter()
        .copied()
        .map(|freq| denormalize(freq.re))
        .collect()
}

fn normalize(n: i16) -> f64 {
    (i16::max_value() as f64 - n as f64) / i16::max_value() as f64
}

fn denormalize(n: f64) -> i16 {
    (n * i16::max_value() as f64).round() as i16
}

/// A Fast Fourier Transform implementation copied from [Rosetta Code][rc],
/// modified to avoid allocating memory.
///
/// [rc]: https://rosettacode.org/wiki/Fast_Fourier_transform#Rust
pub fn raw_fft<'a>(
    input: &[Complex<f64>],
    buf_a: &'a mut Vec<Complex<f64>>,
    buf_b: &'a mut Vec<Complex<f64>>,
) -> &'a mut [Complex<f64>] {
    // round n (length) up to a power of 2:
    let n = input.len().next_power_of_two();

    // clear the previous buffer
    buf_a.clear();
    buf_a.reserve(n);
    // copy the input into a buffer
    buf_a.extend_from_slice(input);
    // pad out the rest with zeroes
    buf_a.extend(core::iter::repeat(Complex::default()).take(n - input.len()));

    // then copy it across to our second buffer
    buf_b.clear();
    buf_b.extend_from_slice(&buf_a);

    fft_recursive(buf_a, buf_b, n, 1);

    for element in buf_a.iter_mut() {
        *element /= n as f64;
    }

    buf_a
}

fn fft_recursive(
    buf_a: &mut [Complex<f64>],
    buf_b: &mut [Complex<f64>],
    n: usize,
    step: usize,
) {
    if step >= n {
        return;
    }

    fft_recursive(buf_b, buf_a, n, step * 2);
    fft_recursive(&mut buf_b[step..], &mut buf_a[step..], n, step * 2);
    let (left, right) = buf_a.split_at_mut(n / 2);

    for i in (0..n).step_by(step * 2) {
        let t = (Complex::new(0.0, -PI) * (i as f64) / (n as f64)).exp()
            * buf_b[i + step];
        left[i / 2] = buf_b[i] + t;
        right[i / 2] = buf_b[i] - t;
    }
}

#[cfg(test)]
mod tests {
    use super::*;

    // Testing data from http://www.sccon.ca/sccon/fft/fft3.htm

    #[test]
    fn impulse() {
        let mut input = [Complex::new(0.0, 0.0); 8];
        input[0] = Complex::new(1.000, 0.000);
        let should_be = [Complex::new(0.125, 0.0); 8];
        let mut a = Vec::new();
        let mut b = Vec::new();

        let got = raw_fft(&input, &mut a, &mut b);

        assert_eq!(got, should_be);
    }

    #[test]
    fn shifted_impulse() {
        let mut input = [Complex::new(0.0, 0.0); 8];
        input[1] = Complex::new(1.000, 0.000);
        let should_be = [
            Complex::new(0.125, 0.000),
            Complex::new(0.088, -0.088),
            Complex::new(0.000, -0.125),
            Complex::new(-0.088, -0.088),
            Complex::new(-0.125, 0.000),
            Complex::new(-0.088, 0.088),
            Complex::new(0.000, 0.125),
            Complex::new(0.088, 0.088),
        ];
        let mut a = Vec::new();
        let mut b = Vec::new();

        let got = raw_fft(&input, &mut a, &mut b);

        println!("{:?}", got);
        assert!(
            got.iter().all(|c| c.norm() == 0.125),
            "Each result should have the same magnitude"
        );
        for (i, (got, should_be)) in got.iter().zip(&should_be).enumerate() {
            let error = got - should_be;
            assert!(
                error.norm() < 0.001,
                "{:?} != {:?} at index {}",
                got,
                should_be,
                i
            );
        }
    }

    #[test]
    fn all_zeroes() {
        let input = [Complex::new(0.0, 0.0); 8];
        let should_be = [Complex::new(0.0, 0.0); 8];
        let mut a = Vec::new();
        let mut b = Vec::new();

        let got = raw_fft(&input, &mut a, &mut b);

        assert_eq!(got, should_be);
    }
}


Refactor tylerapi.py

Lines 499, 502, 506, 510 currently reach for the API multiple times, can probably be done once


Is it possible to make opening sidebar a default when we click on extension?

I'm not sure if there's option already if it is I can't find it.
in my use case more than 99% of the time I want a sidebar rather than opening a new tab with a full chat experience, so is it possible to change the default behavior when I click on the extension for the sidebar to open up first?

I'm trying to add that feature, and hopefully it will be available in a future update


🐛 [firebase_crashlytics] Cannot convert value of type 'UnsafeRawPointer' in ios

Bug report
After added firebase_crashlytics project not building for ios.
Swift Compiler Error (Xcode): Cannot convert value of type 'UnsafeRawPointer' to expected argument type 'UnsafePointer<pb_byte_t>?' (aka 'Optional<UnsafePointer<UInt8>>')
/ios/Pods/FirebaseSessions/FirebaseSessions/Sources/SessionStartEvent.swift:191:55

Flutter doctor
Click To Expand
[!] Flutter (Channel stable, 3.7.6, on macOS 12.1 21C52 darwin-arm64, locale ru-RU)
! Warning: dart on your path resolves to /opt/homebrew/Cellar/dart/2.15.1/libexec/bin/dart, which is not inside your
current Flutter SDK checkout at /Applications/flutter.

I dont think this should be closed yet since

Dont think this issue should be closed since the root cause hasnt been fixed

@darshankawar you can't possibly suggest that editing Firebase source code locally is an acceptable solution. Please, reopen this issue. We're also facing this problem with Firebase Crashlytics now.

Thank you @pandora-house.
Just to give you some more details, the build fails for versions 3.1.0 and 3.1.1. Version 3.0.17 is OK.
I'm using Flutter version 3.7.11.
For some reason, neither I or any of our developers can reproduce the issues locally - we only hit it when running on CI.
I run fluter clean and pod upgrade, etc. but I can always build locally. I am on macOS 13.1.
I hit the issue when running a clean build on Azure DevOps using macOS 11 and 12.

Hi @lukaszciastko, with your Azure DevOps pipeline you should try to use "macOS-12" vmImage, it has XCode 13.4.1 and Xcode build with latest firebase_crashlytics should works.

I have the same issue too

Same here

Hello, I can't reproduce the issue locally using XCode 14.3 and firebase_crashlytics: 3.1.2.
Any of you can give more information on your setup?

@brux88 Can you update to the latest version of XCode?

Can confirm that this is reproducable on Xcode 13.2.1. Works fine on my newer computer with Xcode 14.3. For me upgrading Xcode to 14.3 on my older computer is not an option, 14.3 is not compatible with Big Sur and Big Sur cannot be upgraded on said computer.

You have some option to upgrade macOS on older macs that Apple no longer supports.

This is something Google should fix in the Firebase native SDK, the same issue plagues React Native Firebase, as it uses the same native iOS SDK. This should be somewhat easy to fix using conditional compilation, if I'm not totally mistaken.

I have the same issue too,
any solution..??

I fixed this issue by going into the Swift file and changing the offending line to: let bytes = (transportBytes as NSData).bytes.bindMemory(to: pb_byte_t.self, capacity: transportBytes.count)
Though I had to unlock the dependency and that doesn't feel sustainable long term

a temporary solution, this works... hopefully we will see a root solution soon

Picked up the same error message when I created a iOS build via app center.
Previous builds worked fine through the CI pipeline.
Local builds work for iOS. Changing swift files not a good option in my scenario.

@lampian , you should be able to fix this by changing your Xcode version to 14.3 in AppCenter Build.

@lampian , you should be able to fix this by changing your Xcode version to 14.3 in AppCenter Build.

Thanks changing to 14.3 resolved the issue!

In Xcode 13.2.1, I encountered this issue that required me to follow a specific solution described in the following GitHub comment: link.
However, I in Xcode 14.3, the problem mentioned above does not occur.

I am getting same error for FirebaseCrashlytics 10.7.0 and 10.0.0 both. Xcode 13.2.1

Firebase iOS team solved this by bumping the minimum Xcode version to 14.1 for 10.10.0. I guess that's one way to handle this. Goodbye old, perfectly working laptop.

For me, the issue was that I had this config.build_settings['SWIFT_VERSION'] = '4.2' in my Podfile. It was there for some old package we aren't even using anymore, so after I've removed that, it all works like a charm.

Look's like update xcode and flutter solve problem: Flutter 3.10.1, Xcode 14.3.1

Updating Xcode from 13 to 14.3 and Flutter to 3.10.1 solved it. Unfortunately there's no other way to fix it for now unless you update your OS to Ventura, this will make you able to update your Xcode.
If you can't update, maybe you can open macOS Ventura using a virtual machine. (VMware recommended)


Update documentation to reflect compiler command change

Reflects changes made in #2725

Looks good, would you dare to squash the commits together?

This should not me merged prior the release of #2725  :-)
Otherwise it will get published right away.

@jhass I thought GitHub allowed squashing on Pull Request merge?

It does, but it's apparently not enabled for this repo and I still like a merge commit referencing the PR ;)

Okay, I'll squash!

@jhass I do have the option to squash when merging on this repo, and already used it when merging simple PR (like typos).

Should I still squash these commits?

I started to use the squash button as soon as github added it, I think it's great :-)
(though it took me a while to find it)

@jhass it keeps the PR reference inside the parenthesis 👍


fix missing profile error when AWS_PROFILE not set

[fixes #223]
defaults the profile to 'default' per AWS CLI conventions.

New to Go, so any feedback would be :+1:

thanks!


changing tabs bug

Tested versions
4.2 stable
System information
ubuntu 22.04.4 LTS
Issue description
pretty straight forward: when right clicking on a scene and changing tabs the menu that appears stays on top. and it's clickable
Steps to reproduce
create any node and open the little options menu then change tabs. you can change tabs by alt + Tab or just clicking on an icon on the side bar.
Minimal reproduction project (MRP)
...

it's version 4.2.2 stable sorry didn't specify it. And can you look at the problem I'm getting with exporting to android #95070

This does happen with v4.2.2 (Ubuntu 24.04, Wayland). This also includes changing desktops with Super + Scroll. The panel is fully interactable, and doesn't disappear when any other window gains focus. I have also tested this out in 4.3 (rc2) and the bug is still present. See my video attached for examples.
System information: Godot v4.3.rc2.mono - Ubuntu 24.04 LTS 24.04 - Wayland - Vulkan (Forward+) - integrated Intel(R) HD Graphics 4400 (HSW GT2) - Intel(R) Core(TM) i7-4600U CPU @ 2.10GHz (4 Threads)
https://github.com/user-attachments/assets/fab6a2b3-bfee-48c2-89e2-7060aa122f96

there is also a problem after suspending the system and getting back. Some things don't work and sometimes godot crashes after doing anything. I will investigate more and open an issue when i get the time


(AzureCXP)https://github.com/MicrosoftDocs/azure-docs/issues/24863

Doc link updated

@SumanthMarigowda-MSFT : Thanks for your contribution! The author, @tamram, has been notified to review your proposed change.

@SumanthMarigowda-MSFT - There's an extra forward slash in the URL - can you remove that? Thanks!

@ktoliver : Thanks for your contribution! The author, @tamram, has been notified to review your proposed change.

Hi @tamram - I removed the extra forward slash. Shall we merge the PR?

@ktoliver - thanks, please go ahead.


Gateway container should log traffic

Right now the gateway container logs some useful info when it boots, e.g.:
Proxying requests to gRPC service at 'companies:50051'
hit Ctrl-C to shutdown
launching http server on :80
2018/06/19 22:00:35 Creating grpc-gateway proxy with config: {companies:50051 service.swagger.json     /api/companies/}
2018/06/19 22:00:35 API prefix is /api/companies/

However, it never logs anything after that. It would be great to see some info logged for each requests and response.
cc @mdkess @mhamrah

Deliver in #97


chore: release

🤖 New release

cargo-near: 0.8.2 -> 0.9.0
cargo-near-build: 0.1.0 -> 0.1.1

Changelog
cargo-near

0.9.0 - 2024-09-12
Added

Fixed GitHub CI staging workflow generated by cargo near new command to work correctly with docker case (#193)
Extracted cargo-near-build into a standalone crate to be able to use it in near-workspaces and other places without the rest of the heavy dependencies of cargo-near (#198)
Added tracking of cargo near new usage to collect statistics of the command usage (#192)

Fixed

Addressed warnings in cargo build -p cargo-near-build cmd in releaze-plz flow (#212)

Other

Updated near-* dependencies to 0.26 release (#220)
Use "tracing" for logging and loading indicators (#216)
update docker image and sdk version in cargo near new template (#218)
[breaking] updates near-* packages to 0.25 version. Updates near-sdk to 5.4 (#215)

cargo-near-build

0.1.1 - 2024-09-12
Added

Fixed GitHub CI staging workflow generated by cargo near new command to work correctly with docker case (#193)

Other

Use "tracing" for logging and loading indicators (#216)
fix clippy (#219)

This PR was generated with release-plz.

@race-of-sloths include

@frol Thank you for your contribution! Your pull request is now a part of the Race of Sloths!
Weekly streak is on the road, smart strategy! Secure your streak with another PR!

Current status: waiting for scoring
We're waiting for maintainer to score this pull request with @race-of-sloths score [0,1,2,3,5,8,13] command. Alternatively, autoscoring [1,2] will be applied for this pull request
What is the Race of Sloths

Race of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow
For contributors:

Tag @race-of-sloths inside your pull requests
Wait for the maintainer to review and score your pull request
Check out your position in the Leaderboard
Keep weekly and monthly streaks to reach higher positions
Boast your contributions with a dynamic picture of your Profile

For maintainers:

Score pull requests that participate in the Race of Sloths
Engage contributors with fair scoring and fast responses so they keep their streaks
Promote the Race to the point where the Race starts promoting you
Grow the community of your contributors

Feel free to check our website for additional details!

Bot commands

For contributors

Include a PR: @race-of-sloths include to enter the Race with your PR

For maintainers:

Invite contributor @race-of-sloths invite to invite the contributor to participate in a race or include it, if it's already a runner.
Assign points: @race-of-sloths score [1/2/3/5/8/13] to award points based on your assessment.
Reject this PR: @race-of-sloths exclude to send this PR back to the drawing board.
Exclude repo: @race-of-sloths pause to stop bot activity in this repo until @race-of-sloths unpause command is called

🥁  Score it!
@frol, please ask your peers to score the PR using @race-of-sloths score [1/2/3/5/8/13].
If no scoring is provided within 24 hours, this PR will be scored as 2 🦥


New comer's first issue

This is a issue for test. I'm a new comer and learning how to use GIT :)
As I already install the slideshow, it still shows nothing.