Using TVM compiler from C++

Is it possible to schedule and compile ops directly from C++? Digging around the code it seems straightforward to construct the computation graph from C++, but the actual compilation step seems to touch a big chunk of python code in build_module.py (build and lower functions). Would compiling in C++ require porting these functions over to C++ first, or does that functionality already exist under another API?

TVM is mainly in C++ and the only reason python is used is to make things more flexible when stitching
things up. build_module.py contains calls into C++ function. So we would need to port these wrapper calls to c++, but the functions that these functions calls are already in C++.
Contribution is welcomed

@tqchen Thanks for clarifying that, I'm working on getting that ported to C++ at the moment - a quick question about conventions:
Specifying a schedule requires touching functions like Stage::split. This function is not prefixed with the EXPORT macro, but is added to the global registry as "_StageSplitByFactor". What would be the preferred way of accessing this and similar functions? Should I add the EXPORT macro and use it directly, or go via the registry?
This affects other functions too such as ScheduleNode::make (depended on by create_schedule), and Schedule::operator[]. At the moment for testing purposes I'm just adding EXPORT to all of these, but I'm wondering what would be the preferred way?

Use cxx when possible, if you find some function that you need missing export, add it

I am going to close this issue for now. Feel free to open the PR or WIP issue to track the progress


Minimal next-build implementation

We want to implement the most basic way of running next build with turbopack. For that, we use the "dumb bundler" approach and run the usual next build steps in next.js with one exception: Instead of running webpack, we invoke turbopack via napi.
So on the turbopack side, we are only responsible for bundling and emitting the bundled files (for all pages) to disk into the _next folder, including the manifest that next.js expect from us.
For the start, we don't want to run any optimization at all. We just emit the files as we would serve them for development (maybe disable HMR if that leads to issues). We already have the logic for emitting assets to disk (e. g. for node.js execution or node-modules-trace), and we can use that. But we need to come up with additional code for generating the manifests.
No node.js rendering has to be done in turbopack. This will be handled by next.js.
There are a few optional things we could do that might help in testing and developing:
Create a next-build CLI in turbopack.
Add a flag/subcommand to next.js to only run static generation with the existing _next directory.

Close in https://github.com/vercel/next.js/pull/46602


Loading fonts bug (1.17.1)

Moving a font in the fonts folder and reloading resourcing/restarting the game, will make the game reload resources endlessly.
latest.log
Workaround:
Remove any font from the fonts folder

I think you sent wrong log file, check it please.

That's the latest.log

Fixed in 2.15.1


Corrected typo in link (ui.yml)

Why:
In the American style, punctuation (dots and commas) is usually placed inside quotation marks, while in the British style they can be placed inside or outside, depending on whether they are included in the quoted text. In your case:

American style: '"lorem ipsum."'
British style (if the dot is not part of the quoted text): '"lorem impsum".'

The formatting in many texts is written in the British style, so that brought them to a single style

Check off the following:

[x] I have reviewed my changes in staging, available via the View deployment link in this PR's timeline (this link will be available after opening the PR).

For content changes, you will also see an automatically generated comment with links directly to pages you've modified. The comment won't appear if your PR only edits files in the data directory.

[x] For content changes, I have completed the self-review checklist.

@warioddly Thank you very much for opening this PR! ✨ Within GitHub Docs, we adhere to American English punctation rules - you can reference our style guide for additional details.
Since American English puts commas and periods inside the quotation marks, I'll go ahead and close this PR 💛 However, if you see instances where punctation does not adhere to American English, please feel free to open PRs to correct this!


Support MomentumSGD, Adagrad, and Adam in Seq2Seq

Previously only regular SGD was supported through WeightedSum and ScatterWeightedSum.
This PR relies on PR https://github.com/caffe2/caffe2/pull/248 and https://github.com/caffe2/caffe2/pull/249 to work.

25.04.2017, 00:39, "lem14789" notifications@github.com:@lem14789 approved this pull request.
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

Have you considered using these? https://github.com/caffe2/caffe2/blob/master/caffe2/python/optimizer.py
Also creating of the optimizer could be abstracted out. You could add a method CreateOptimizer to optimizers.py which takes a string and creates an optimizer for you.

@salexspb I agree. It's better to use optimizer.py. I close the PR for now.


Add Block str support for python templated strings

@coderabbitai summary

Closing in favor of another previously merged pr by our team


Renaming import alias renames the original import

pub mod test {
    pub struct OriginalStruct;
}

use test::OriginalStruct as RenamedStruct<|>;

fn main() {
    let renamed = RenamedStruct;
}

I place the caret at RenamedStruct in the use test::OriginalStruct as RenamedStruct line and attempt to use a different name instead of RenamedStruct.
Expected: only two places with RenamedStruct are changed:
pub mod test {
    pub struct OriginalStruct;
}

use test::OriginalStruct as RenamedAgainStruct;

fn main() {
    let renamed = RenamedAgainStruct;
}

actulal: the OriginalStruct name gets changed:
pub mod test {
    pub struct RenamedAgainStruct;
}

use test::RenamedAgainStruct as RenamedStruct;

fn main() {
    let renamed = RenamedStruct;
}

Duplicate of #5671.


How to configure which statuses are displayed?

I would suggest that the GM can configure all statuses shown

Problems are

How does the gm figure out how the status is named?
This could be a very long list

It might be faster to exclude certain status. But I would ask the alpha tester about it


Explicitly include <stdio.h> at gen_context.c

It was previously implicitly included via the "util.h" header file.

Sure.


*: Update the POC implementation and vendor the PlatformOperators CRD

This updates the current POC codebase, and attempts to introduce the PlatformOperators CRD from the openshift/api repository now that https://github.com/openshift/api/pull/1234 has merged.
These changes introduce a tools.go file to the repository, which only specifies the github.com/openshfit/api/platform/v1alpha1 package that includes the PlatformOperators CRD. Updates the manifests Makefile target to ensure we're copying that CRD into our root manifests directory.
The root Dockerfile doesn't need any changes here as we already run COPY manifests /manifests so we already get this CRD resource for free. I validated this assumption locally:
bash-4.4$ ls /manifests/
0000_50_cluster-platform-operator-manager_00-namespace.yaml			0000_50_cluster-platform-operator-manager_01-rukpak-webhooks-admin.sa.yaml  0000_50_cluster-platform-operator-manager_03_rbac.yaml
0000_50_cluster-platform-operator-manager_00-platformoperator.crd.yaml		0000_50_cluster-platform-operator-manager_01-serviceaccount.yaml	    0000_50_cluster-platform-operator-manager_04-rukpak-core.deployment.yaml
0000_50_cluster-platform-operator-manager_00-rukpak-bundledeployments.crd.yaml	0000_50_cluster-platform-operator-manager_01-webhook-ca.cm.yaml		    0000_50_cluster-platform-operator-manager_04-rukpak-webhooks.deployment.yaml
0000_50_cluster-platform-operator-manager_00-rukpak-bundles.crd.yaml		0000_50_cluster-platform-operator-manager_02-metricsservice.yaml	    0000_50_cluster-platform-operator-manager_05-rukpak.validating-webhook-configuration.yaml
0000_50_cluster-platform-operator-manager_01-core-ca.cm.yaml			0000_50_cluster-platform-operator-manager_02-rukpak-core.service.yaml	    0000_50_cluster-platform-operator-manager_06-deployment.yaml
0000_50_cluster-platform-operator-manager_01-rukpak-core-admin.sa.yaml		0000_50_cluster-platform-operator-manager_02-rukpak-webhook.service.yaml
bash-4.4$

Other misc. changes include updating the controller implementations to ensure it can run properly on cluster. I tried to keep these changes as minimal as possible to avoid stepping on the implementations in #17 and the in-flight CPOM controller implementation. This PR can be a pre-requisite for both of those high-level implementations.
This is also a pre-requisite to #23.

/lgtm

Still in the bootstrapping phase leading up to #23. Manually adding the required labels again.
/label px-approved
/label qe-approved
/label docs-approved


Support nested .babelrc files in babel-jest

🚀 Feature Proposal
Add support for nested .babelrc files in sub-folders
Motivation
When working with monorepos, e.g. through Lerna, it is currently not possible to run Jest from the root level in an easy way if each package / project has different .babelrc files, as is often the case when working with backend and frontend code in one monorepo.
I have therefore written my own version of babel-jest called babel-jest-nested that support this feature. I'd like to suggest to include this in babel-jest by default:
https://github.com/lehni/babel-jest-nested
Example
See the example here:
https://github.com/lehni/babel-jest-nested#example-with-lerna
Pitch
I am not the only one struggling with this problem, but so far there was no easy solution, see here:
https://github.com/lerna/lerna/issues/994#issuecomment-353888743
https://stackoverflow.com/questions/50511308/jest-projects-configuration-does-not-read-babelrc-and-webpack-config-json-in/51174657#51174657
etc.

It sounds like this is related: https://github.com/facebook/jest/issues/6053#issuecomment-383632515
So maybe PR #6629 isn't the right fix, but then this also means that the orignal getBabelRC() is using the wrong .babelrc files for caching in such circumstances.

I can confirm that https://github.com/facebook/jest/issues/6053#issuecomment-383632515 indeed solves my issues and removes the need for `babel-jest-nestedà


Multiple Instagram Accounts

First, Thank you for this project, really helped me a lot. Thank you.
I have multiple Instagram accounts, I connected to one and it worked perfectly.
Is there a way to connect multiple Instagram accounts with your connector?

Hi @0xMostafa would you be available to help me set up my Instagram? I'm happy to pay for the help!

@ruesaintdenis sure, contact me here


Feature: Add support for creating shortcuts from the new item menu

@Jaiganeshkumaran were you working on this?

Could you reopen this issue with the new templates please.

@Josh-65 can you create an issue for this one? We definitely want to implement this.


Add multiple Filters to a search

Hi, I am struggling to understand how to add multiple filters to a search.
Can you assist?

If you still have problem i can assist.

Hello, may I have the example of search?

hi, can you comment example search query

Hello,please provide the example of search ?
query_all is not support LIKE Statement ..
How i execute search operation ?

Sample Search Query
{
"query":{
"bool":{
"must":[
{"match":{"createdDate":"2018-07-15"}},
{
"bool":{
"should":[
{"match":{"status":"Y"}},
{"match":{"deletestatus":"N"}}
]
}
}
]
}
}
}

its worked for exact match..
how i perform like operation as in sql for elastic ??
How i query following please ??
Select * from lists where list_name LIKE '%edu%'

You can use "match_phrase"
{
"query": {
"match_phrase": {
"list_name": "edu"
}
}
}

@chirayushri this is easy to do with the advancedquery function. just do what @sk-karthik say, by making a json object to send as one of the paramater to the advancedquery function.


Req: Adding new table to db for trading history

It would be nice if there was a log of BUY/SELL orders in the database.
That way it would be easy to more creative output, like say line graphs for a more visual overview of the bot's activities with algorithm details and statistics on trade history.

good point, will add that to the todo!

@askmike actually a issue that shouldn't be closed, but this need a bump :smile:


fix(statutory): edit application now only shows applicable bodies

It was only changed with new applications in the previous PR, so now a quick fix for this when users edit their current application.

:tada: This PR is included in version 1.19.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Some assorted minor fixes and cleanup

The commit messages should be sufficient but if anything is unclear, please ask.


[BUG] ContactUs is Repeated Twice

Description
Contact Us is Repeated Twice . Want to fix this.
Screenshots
No response
Any additional information?
No response
What browser are you seeing the problem on?
No response
Checklist

[X] I have checked the existing issues.
[X] I have read the Code Of Conduct
[X] The changes don't break the code
[X] Please attach the screenshots and video of the development work once it is done

completed the task assigned


obi requires gspeak to be installed to create a new project

[~/oblong]> obi new cpp test
Traceback (most recent call last):
  File "/usr/local/Cellar/obi/HEAD-1193e12/libexec/bin/obi", line 9, in <module>
    load_entry_point('oblong-obi==3.2.1', 'console_scripts', 'obi')()
  File "/usr/local/Cellar/obi/HEAD-1193e12/libexec/lib/python2.7/site-packages/obi/obi.py", line 166, in main
    g_speak_home = get_g_speak_home(arguments)
  File "/usr/local/Cellar/obi/HEAD-1193e12/libexec/lib/python2.7/site-packages/obi/obi.py", line 106, in get_g_speak_home
    g_speak_home = max(items, key=g_speak_version_key)
ValueError: max() arg is an empty sequence
┌[aaron@candelabra] [/dev/ttys000] [candelabra ⚡] [1]
└[~/oblong]> echo $G_SPEAK_HOME

┌[aaron@candelabra] [/dev/ttys000] [candelabra ⚡]
└[~/oblong]> G_SPEAK_HOME=/tmp obi new cpp test
Found /tmp by environment variable G_SPEAK_HOME
Traceback (most recent call last):
  File "/usr/local/Cellar/obi/HEAD-1193e12/libexec/bin/obi", line 9, in <module>
    load_entry_point('oblong-obi==3.2.1', 'console_scripts', 'obi')()
  File "/usr/local/Cellar/obi/HEAD-1193e12/libexec/lib/python2.7/site-packages/obi/obi.py", line 170, in main
    g_speak_version = re.search(r'(\d+\.\d+)', g_speak_home).group()
AttributeError: 'NoneType' object has no attribute 'group'
┌[aaron@candelabra] [/dev/ttys000] [candelabra ⚡] [1]
└[~/oblong]> mkdir -p /tmp/oblong/g-speak3.28
┌[aaron@candelabra] [/dev/ttys000] [candelabra ⚡]
└[~/oblong]> export G_SPEAK_HOME=/tmp/oblong/g-speak3.28
┌[aaron@candelabra] [/dev/ttys000] [candelabra ⚡]
└[~/oblong]> obi new cpp test
Found /tmp/oblong/g-speak3.28 by environment variable G_SPEAK_HOME
Project test created successfully!

this is a dupe of #61


Merge generic adapter reconcilers

Third and final part of the grand plan mentioned in #678.
Merges all generic adapter reconcilers into one package under pkg/reconciler.
The main components involved are:

1 Reconcilable interface implemented by all components unconditionally
3 sub-interfaces implemented by some components based on their nature

EventReceiver (components that explicitly declare the event types they can receive)
EventSender (components that can send to a sink using a CloudEvents client)
EventSource (components that declare the event types they can emit/respond, but do not necessarily use a sink)

2 flavors of generic reconcilers: Deployment and Kn Service

Can reconcile different aspects of adapters and components' statuses based on the interfaces above (CE attributes, sink URL, status conditions, ...)

No matter the outcome of this PR, Git's stats make me happy:
+3,516
-15,307


Remove version badges from individual tools from pre-mono-gem times

Took half a year...

Thanks @joshdholtz 👍


Simplify world schedule methods

Objective
Methods for interacting with world schedules currently have two variants: one that takes impl ScheduleLabel and one that takes &dyn ScheduleLabel. Operations such as run_schedule or schedule_scope only use the label by reference, so there is little reason to have an owned variant of these functions.
Addresses concerns voiced in https://github.com/bevyengine/bevy/pull/8387#issuecomment-1509893621.
Solution
Decrease maintenance burden by merging the ref variants of these functions with the owned variants.

Changelog

Removed World::run_schedule_ref. Its functionality has been merged with World::run_schedule.

Migration Guide
The method World::run_schedule_ref has been removed, and run_schedule now takes the schedule label by reference.
let my_schedule: &dyn ScheduleLabel = ...;

// Before:
world.run_schedule(MySchedule);
world.run_schedule_ref(my_schedule);

// After:
world.run_schedule(&MySchedule);
world.run_schedule(my_schedule);

Roping in @cart for this since this does have some major UX implications for the API.

So with the methods that take &dyn ScheduleLabel, it's very easy to end up with a boxed label that you need to remember to dereference or things will fail silently.

Is that not also true for impl ScheduleLabel?

So the footgun does exist for impl ScheduleLabel as well; the following test fails:
#[test]
fn test_boxed_label() {
    use crate::{self as bevy_ecs, world::World};

    #[derive(ScheduleLabel, Debug, Default, Clone, Copy, PartialEq, Eq, Hash)]
    struct A;

    let mut world = World::new();
    world.add_schedule(Default::default(), A);
    world
        .try_run_schedule(Box::new(A) as BoxedScheduleLabel)
        .unwrap(); // This returns `Err` since `Box::new(A) != A`
}

I agree that we should fix this footgun but I don't think this PR is affected by it.

I have a fix for the aforementioned footgun in #8436.

Operations such as run_schedule or schedule_scope only use the label by reference, so there is little reason to have an owned variant of these functions.

Having both was a UX decision. As a rule of thumb, we try to make as many user-facing label apis by-value as possible. It reads better, one less character to type, and the consistency across all label apis is nice. If someone is passing a label into a function, they can generally expect by value.
The by-ref calls are almost always going to be "bevy internals code" (ex: retrieving an existing stored label and doing something with it). Users trying to run a schedule manually should not need to worry about references. I think it is worth it to make this by-value and then have the _ref variant for the less common (generally internal) cases.  Pretty much everything user-facing can (and i would assert should) use by-value.

I took @alice-i-cecile's idea and made these methods take AsRef<dyn ScheduleLabel>, so now they accept labels either by value or by reference. Also, I made this change less breaking by deprecating run_schedule_ref, which was the only one of these methods that existed in 0.10.

Great, I think that's a nice balance of pretty end user API and no code duplication.


ENH: Update to newer third-party update script from CMake

Use the CMake Utilities/Scripts/update-third-party.bash as of commit
693f4c70ff.  Manually preserve ITK's change from commit 5dccc2207e
(BUG: Do not gpg sign third party updates, 2018-11-19, v5.0b02~82^2~1).

@thewtex this needs to be merged to both release and master.  It's needed to make third-party updates easier.  See the trouble encountered in #2290 for an example.

Thanks for the fix!

@bradking thanks!
Merging to master now -- we will release 5.2 RC 2 over the next few days, and I will update release at that time.

This was merged into release branch, as that was the target of the PR. I will merge it into master too.


Support installing specific versions of extensions

I would like to be able to easily install previous versions of extensions. For example, I want to be able to do this:
code --install-extension Ionide.Ionide-fsharp --version 2.7.0

I just reported a https://github.com/ionide/ionide-vscode-fsharp/issues/217 and I want to be able to troubleshoot by easily rolling back to the previous versions of the extension.
Today, it is possible to manually download and install as explained here:
https://code.visualstudio.com/Docs/editor/extension-gallery

Sounds like something we could enable, I don't know if there's an existing issue. Maybe syntax like --install-extension<EMAIL_ADDRESS>

@2.7.0 syntax would work too. :-)

Fixed by #13131

@joaomoreno #13131 doesn't looks like it fixes this.

I think that's for showing versions, not installing a particular version.

Would be really nice to have this feature. Would really help rolling back to an older version if new version of a plugin causes problem, especially now that there's extension auto updating feature.

It seems the API may have a way to get it, see this example for the link to an old version of the python extension:
https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-python/vsextensions/python/2018.4.0/vspackage

This request is also covered along with https://github.com/Microsoft/vscode/issues/12764
Hence closing this as duplicate


Inaccurate detail provided by hostname comment

Per the title, this line seems to provide inaccurate details based on my first hand testing.
https://github.com/harvester/ipxe-examples/blob/601ffd0e1e56a10b96c7ec2eb235848f071f2972/general/config-join.yaml#L4
This implies that DHCP server set hostnames should be respected, however that is not the case in my experience setting up a Harvester cluster via pxe/ipxe and using ISC DHCPD.
Obviously, it would be ideal if I could exclude the hostname field from the yaml config for joining a cluster, because then every node could use the same exact yaml. So that is my root motivation for wishing this worked as the comment implies.

From my investigation I found that the installer - specifically here - seems to generate the hostname I'm seeing being used.
I'm wondering if this comment is in reference to old behavior that was removed, or maybe new behavior that hasn't shipped yet?

From what I can see in the code this issue is still relevant - I'm not seeing any changes to either the example repo, or the installer which would make things consistent. My impression from the comment would be that the generateHostName function should use the DHCP hostname if one is set, otherwise defaulting to current behaviour makes sense.
Alternatively, it may just be easier to just update the examples repo to remove the comment saying hostname is optional if DHCP is used. Personally I think the former solution is nicer for end users though.


Add unit definitions written by @Bijan86

Several new units in Density, Force, Pressure and Torque.

@Bijan86 asked me to add these for him as he was not a programmer. There are several things to discuss before generating code and merging in to develop, so this PR is for discussion.

@Bijan86 these are my initial comments. I need some feedback on each of these before proceeding to modify the code.

Merged in at cdd317322274a1830e4a61a419575d3160d6fcb3.

@Bijan86 I released a beta nuget just now, 3.13.0-beta.
Can you give it a try? You will have to select 'pre-release' channel when looking for nuget updates in order to see the beta version.
Note: I had to fix the conversion factors for these two units as they did not seem correct. Please verify.
        {
            "SingularName": "PoundPerCubicInch",
            "PluralName": "PoundsPerCubicInch",
            "FromUnitToBaseFunc": "x*27679.904710191",
            "FromBaseToUnitFunc": "x/27679.904710191",
            "Prefixes": ["Kilo"],
            "Localization": [
                {
                    "Culture": "en-US",
                    "Abbreviations": ["lb/in³"],
                    "AbbreviationsWithPrefixes": ["kip/in³"]
                }
            ]
        },
        {
            "SingularName": "PoundPerCubicFoot",
            "PluralName": "PoundsPerCubicFoot",
            "FromUnitToBaseFunc": "x/0.062427961",
            "FromBaseToUnitFunc": "x*0.062427961",
            "Prefixes": ["Kilo"],
            "Localization": [
                {
                    "Culture": "en-US",
                    "Abbreviations": ["lb/ft³"],
                    "AbbreviationsWithPrefixes": ["kip/ft³"]
                }
            ]
        },

This turned out to be quite a big addition. 54 new units were addded!
Full changelog for this:
Breaking changes:
* Torque: Rename Newtonmeter to NewtonMeter
* Torque: Change "Nm" abbreviation to "N·m"
* Force: Rename PoundForces to PoundsForce

Add units
---

SpecificWeight
* KilogramForcePerCubicCentimeter
* KilogramForcePerCubicMeter
* KilogramForcePerCubicMillimeter
* KilonewtonPerCubicCentimeter
* KilonewtonPerCubicMeter
* KilonewtonPerCubicMillimeter
* KilopoundForcePerCubicFoot
* KilopoundForcePerCubicInch
* NewtonPerCubicCentimeter
* NewtonPerCubicMeter
* NewtonPerCubicMillimeter
* PoundForcePerCubicFoot
* PoundForcePerCubicInch
* TonneForcePerCubicCentimeter
* TonneForcePerCubicMeter
* TonneForcePerCubicMillimeter

Update units
---

Density:
* KilogramPerCubicCentimeter
* KilogramPerCubicMillimeter
* KilopoundPerCubicFoot
* KilopoundPerCubicInch
* PoundPerCubicFoot
* PoundPerCubicInch
* TonnePerCubicCentimeter
* TonnePerCubicMeter
* TonnePerCubicMillimeter

Force:
* Add TonneForce

Pressure:
* KilogramForcePerSquareMeter
* KilogramForcePerSquareMillimeter
* KilonewtonPerSquareCentimeter
* KilonewtonPerSquareMeter
* KilonewtonPerSquareMillimeter
* KilopoundForcePerSquareFoot
* KilopoundForcePerSquareInch
* PoundForcePerSquareFoot
* PoundForcePerSquareInch
* TonneForcePerSquareCentimeter
* TonneForcePerSquareMeter
* TonneForcePerSquareMillimeter

Torque:
* KilogramForceCentimeter
* KilogramForceMeter
* KilogramForceMillimeter
* KilonewtonCentimeter
* KilonewtonMeter
* KilonewtonMillimeter


Sema: Give constraints a more dignified retirement

When we retire a constraint, there is no guarantee that it is at the end of the list, so it is not correct to always reinsert it at the end of the list when the constraint comes out of retirement. Instead, remember the position where we removed it from, so that we can always reinsert it in the correct position. This allows us to replace some bespoke logic in CSStep.h with a call to retireConstraint().
Fixes https://github.com/swiftlang/swift/issues/77008
Also fixes rdar://problem/138246764

@swift-ci Please smoke test

@swift-ci Please test source compatibility

Hi @slavapestov the windows rebranch CI started to fail: https://ci-external.swift.org/job/swift-rebranch-windows-toolchain/515/consoleText
Failed Tests (6):
  Swift(windows-x86_64) :: Concurrency/async_overload_filtering.swift
  Swift(windows-x86_64) :: Constraints/common_type.swift
  Swift(windows-x86_64) :: Constraints/init_literal_via_coercion.swift
  Swift(windows-x86_64) :: Constraints/one_way_solve.swift
  Swift(windows-x86_64) :: Constraints/overload_filtering.swift
  Swift(windows-x86_64) :: Constraints/result_builder_conjunction_selection.swift

Could this https://github.com/swiftlang/swift/pull/77152 from https://ci-external.swift.org/job/swift-rebranch-windows-toolchain/515/changes#58a6a64647aeb270897241d6b229c1ffe17c37dd
be causing it? Sorry if I'm mistaken as I'm not familiar with the constraints :)

CC @bnbarham

Thanks for the fix @slavapestov


[netdata] update Publisher to reserve entries for RoutingManager

This commit updates NetworkData::Publisher to reserve a set of
prefix entries for use by RoutingManager only. This allow us to
simplify how RoutingManager publishes route prefixes in Network
Data (assert on failure). In particular, this commit defines a new
enum Requester which specifies the requester (kFromUser or
kFromRoutingManager) associated with a published prefix. This is
used by methods PublishExternalRoute()/PublishOnMeshPrefix().
When allocating new entries, we ensure that each requester is
limited to its maximum number of entries.

Why not let the routing manager allocate the memory and add to the Publisher (e.g. maintained in a LinkedList) if we want the memory to be reserved?

Why not let the routing manager allocate the memory and add to the Publisher (e.g. maintained in a LinkedList) if we want the memory to be reserved?

It requires a re-design of how Publisher works. and I am not sure if it would be better or simpler (it seems easier to have the Publisher manage its own data model).

This commit updates NetworkData::Publisher to reserve a set of prefix entries for use by RoutingManager only. This allow us to simplify how RoutingManager publishes route prefixes in Network Data (assert on failure). In particular, this commit defines a new enum Requester which specifies the requester (kFromUser or kFromRoutingManager) associated with a published prefix. This is used by methods PublishExternalRoute()/PublishOnMeshPrefix(). When allocating new entries, we ensure that each requester is limited to its maximum number of entries.

This doesn't guarantees that RoutingManager call always successfully publish the route for the on-link prefixes, because the network data registration can be rejected by the leader for various reasons (e.g. the network data is exhausted, the registration message is lost...) and it looks like we are currently not following those cases in network_data_publisher?

This doesn't guarantees that RoutingManager call always successfully publish the route for the on-link prefixes, because the network data registration can be rejected by the leader for various reasons (e.g. the network data is exhausted, the registration message is lost...) and it looks like we are currently not following those cases in network_data_publisher?

Thanks @wgtdkp. With this change in this PR the act of Publishing entry from RoutingManager will be always successful, i.e., we can not fail due to other modules using all entries on Publisher (since we have our own reserved set). From the perspective of the RoutingManager that what we care (i.e. we want to successfully publish or unpublish). It becomes the job of other NetworkData modules to handle it from then on:

NetworkData::Publisher will monitor and decide when/if to add/remove published entries in local network data (goal is limit number of similar entries in Network Data to keep its size smaller).
NetworkData::Notifier is responsible to register and sync the local network data with leader and it handles failure and has its own retry mechanism.

It is true that if network data reaches its limit, Notifier (and/or Publisher) will continue to rety and fail. I know there has been ideas of detecting this and maybe trying to reduce the registered entries (say add a default route instead of all specific routes, etc), but that's a different topic to consider and requires more thought and design (e.g., mechanism to detect this situation and callbacks from Notifier and/or Publisher to inform its users (e.g. RoutingManager) to see if they can take any action).

But independent of actions we may take on a BR itself, we cannot guarantee network data won't stay full as other BRs may add entries into and consume all its bytes.

This doesn't guarantees that RoutingManager call always successfully publish the route for the on-link prefixes, because the network data registration can be rejected by the leader for various reasons (e.g. the network data is exhausted, the registration message is lost...) and it looks like we are currently not following those cases in network_data_publisher?

Thanks @wgtdkp. With this change in this PR the act of Publishing entry from RoutingManager will be always successful, i.e., we can not fail due to other modules using all entries on Publisher (since we have our own reserved set). From the perspective of the RoutingManager that what we care (i.e. we want to successfully publish or unpublish). It becomes the job of other NetworkData modules to handle it from then on:

NetworkData::Publisher will monitor and decide when/if to add/remove published entries in local network data (goal is limit number of similar entries in Network Data to keep its size smaller).
NetworkData::Notifier is responsible to register and sync the local network data with leader and it handles failure and has its own retry mechanism.

It is true that if network data reaches its limit, Notifier (and/or Publisher) will continue to rety and fail. I know there has been ideas of detecting this and maybe trying to reduce the registered entries (say add a default route instead of all specific routes, etc), but that's a different topic to consider and requires more thought and design (e.g., mechanism to detect this situation and callbacks from Notifier and/or Publisher to inform its users (e.g. RoutingManager) to see if they can take any action).

But independent of actions we may take on a BR itself, we cannot guarantee network data won't stay full as other BRs may add entries into and consume all its bytes.

In the cases where the Network Data is exhausted by other devices, it's true that other modules like the publisher may retry and fail but the result is not propagated back to Routing Manager which will stay in the kPublishing state indefinitely. Agree it's on-trivial to solve this case, just some ideas in my mind:

publisher propagates the publishing result to Routing Manager so that Routing Manager can take further action.
Routing Manager itself may need a timer to retry publishing indefinitely with larger intervals or times out and transition to next failure state.

publisher propagates the publishing result to Routing Manager so that Routing Manager can take further action.
Routing Manager itself may need a timer to retry publishing indefinitely with larger intervals or times out and transition to next failure state.

Yes. If we have reached net data size limit and cannot register anymore, we may need new callback (probably from NetworkData::Notifier to inform other module (perhaps on RoutingManager) to take actions . The action should be to remove/replace previous published entries (e.g. unpublish all external routes and use default route instead). And it may still fail. That's something for future PR/enhancement.
Normal retries (when we don't need to make any changes to published entries) is already handled by Publisher and Notifier classes (once we pass a prefix to them to publish/unpublish they keep trying until success or they are told otherwise (remove the published entry)).
This PR is addressing the first step: When we ask Publisher to publish a prefix and it tries to allocate an entry to remember what we asked to publish. We have our own reserved pool of entries on Publisher (since we can know max number of entries we may publish we can reserve the proper number). So the allocation should not fail which helps simplify RoutingManager (no need to handle retry for the allocation failure).


CLI fails to create COSE using Azure KeyVault RSA key

Describe the bug
Cannot use sign operation with an RSA key. The underlying cose signing operation does not support RSA it seems https://github.com/microsoft/CCF/blob/a58d2c880b3691211ed7fa68b684e1ef5bfabf4c/python/ccf/cose.py#L82
To Reproduce

Generate a self signed RSA 4096 cert in AKV

Get the public key

az keyvault certificate download --vault-name $VAULTNAME -n $CERTNAME -f cabundle.pem -e PEM

Create AKV details json file for the CLI to use akv-config.json:
{
  "keyVaultName":"$VAULTNAME","certificateName":"$CERTNAME","certificateVersion":"$version"
}

Create a sample file to sign claim-foobar.txt

Invoke the CLI to create a signature:
scitt sign --claims claim-foobar.txt --content-type "text/plain" --akv-configuration akv-config.json --x5c cabundle.pem --out claim.cose

The failure:
Traceback (most recent call last):
  File "/home/ubuntu/.local/bin/scitt", line 11, in <module>
    load_entry_point('pyscitt', 'console_scripts', 'scitt')()
  File "/home/ubuntu/scitt-ccf-ledger/pyscitt/pyscitt/cli/main.py", line 42, in main
    args.func(args)
  File "/home/ubuntu/scitt-ccf-ledger/pyscitt/pyscitt/cli/sign_claims.py", line 211, in <lambda>
    func=lambda args: sign_claims(
  File "/home/ubuntu/scitt-ccf-ledger/pyscitt/pyscitt/cli/sign_claims.py", line 141, in sign_claims
    signed_claims = kv_client.cose_sign(
  File "/home/ubuntu/scitt-ccf-ledger/pyscitt/pyscitt/key_vault_sign_client.py", line 81, in cose_sign
    tbs = create_cose_sign1_prepare(
  File "/home/ubuntu/.local/lib/python3.8/site-packages/ccf/cose.py", line 143, in create_cose_sign1_prepare
    alg = default_algorithm_for_key(cert.public_key())
  File "/home/ubuntu/.local/lib/python3.8/site-packages/ccf/cose.py", line 96, in default_algorithm_for_key
    raise NotImplementedError("unsupported key type")
NotImplementedError: unsupported key type

Expected behavior
The command should not complain and sign the payload

The API is used only for testing, it was hidden from the public interface in the published package


LTO flags are silently ignored if one the crate-type of the root package is not compatible with LTO

Problem
Using the Cargo.toml below, LTO is not used for the staticlib target when building multiple library targets with cargo build --release.
To enable LTO, the lib target must be removed, or we must use cargo rustc --crate-type=staticlib for building separately.
Steps

Cargo.toml:

[package]
name = "a"

[profile.release]
lto = true

[lib]
crate-type = ["lib", "staticlib"]

Command

cargo build --release
Possible Solution(s)
Show a warning that LTO is disabled for the LTO-compatible targets, and suggest using cargo rustc --crate-type=X.
Version
cargo 1.81.0 (2dbb1af80 2024-08-20)
release: 1.81.0
commit-hash: 2dbb1af80a2914475ba76827a312e29cedfa6b2f
commit-date: 2024-08-20
host: x86_64-unknown-linux-gnu
libgit2: 1.8.1 (sys:0.19.0 vendored)
libcurl: 8.8.0-DEV (sys:0.4.73+curl-8.8.0 vendored ssl:OpenSSL/1.1.1w)
ssl: OpenSSL 1.1.1w  11 Sep 2023
os: Ubuntu 20.4.0 (focal) [64-bit]

We have this comment in the code though it lacks an explanation
https://github.com/rust-lang/cargo/blob/5e2878f7868ab141e071982fd9c8325142048610/src/cargo/core/compiler/lto.rs#L109-L111

That code seemed to be added in #8349

This is a dup of #2301 and exactly identical to #4611. The core issue is that the compiler rejects multiple crate types that some accepts LTO some don't. https://github.com/rust-lang/cargo/issues/2301#issuecomment-173654991.
Close in favor #4611.


Code Quality: Introduce Directory.Packages.props for better dependency management

Description
Similar to #14826, which would allow for seamless property management across projects, but instead this would allow for seamless package management. This would allow for easier ability to update dependencies across projects.
Concerned code
All projects.
Gains

Better ability to update dependencies
Easier way to see all the dependencies used by the projects and quickly identify each of them
Offers similar benefits to using Directory.Build.props

Requirements
Very easy:

Create Directory.Packages.props file
Migrate package references into the file
Remove version references from project files
Add package references to project files

Comments
No response

We can merge this into https://github.com/files-community/Files/issues/14826

Umm.. sure...

Great minds think alike


Avoid cycles

Checklist

[x] Used a fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@isuruf This is ready for review and should address your concerns in #40

Thanks @xhochy


WMS CQL_Filter and Group layer

I can not filter the WMS layer as what i can with leaflet.
I have try:
<l-wms-tile-layer :name="ten2" layer-type="base" :base-url="url2" :attribution="attribution" CQL_FILTER='maluuvuc=1'  opacity="0.7" :layers="layers"  styles="watershed" ,transparent= true, format= "image/png"></l-wms-tile-layer>
and
<l-wms-tile-layer :name="ten2" layer-type="base" :base-url="url2" :attribution="attribution" @CQL_FILTER='maluuvuc=1'  opacity="0.7" :layers="layers"  styles="watershed" ,transparent= true, format= "image/png"></l-wms-tile-layer>
But It does work.
I also have a problem with Overlay 2 layer.
Could you help me? Thank you so much!!

@hulauwa I think you should try to pass CQL_FILTER in the options prop

Thank you so much I did it bro.
How about group the layer, in the document, it does not available

@hulauwa you can use the @ready event on the component, it return the mapObject element where you can find the layer

Do you know how to use the method in leaflet, I use:
overlay.Watershed.setParams({CQL_FILTER:" watershedcode >0"});
overlay.Watershed.setParams({CQL_FILTER:" watershedcode >10"});
Thank you

@hulauwa you can investigate the mapObject, that mapObject is returned in the ready event and you can retrieve it with a ref on the l-map

Like this event right, I found in vue development. But dont have setParams. I will find on l-map

@hulauwa sorry!  the ref on your wms tilelayer component

I read these sentences:
Most of our components do not emit events but all the components pass down listeners for leaflets events. It's possible to bind to them by simply writing @leafletEventName.
But I try to replace it like:
@overlay.Watershed.setParams({CQL_FILTER:" watershedcode >0"});
@setParams({CQL_FILTER:" watershedcode >0"});
It s Errorr.
How can I find the Groupname rand layername that Vue stores.
Thank you so much

@hulauwa I need a piece of code or better a codesanbox example to help you further

@hulauwa setParams is a leaflet method, not an event. As for events, the @leafletEventName works only in your vuejs HTML template, for example:
<l-map @zoomstart="doSomething"></l-map>
As for the cql filter, you should be able to pass it within the options prop of the <l-wms-tile-layer> component like so: <l-wms-tile-layer :options="{ cql_filter: 'watershedcode >0'}"></l-wms-tile-layer>
I heavily suggest you consult the vuejs documentation, as it will greatly help you understand how this plugin interacts with leaflet.js

@hulauwa setParams is a leaflet method, not an event. As for events, the @leafletEventName works only in your vuejs HTML template, for example:
<l-map @zoomstart="doSomething"></l-map>
As for the cql filter, you should be able to pass it within the options prop of the <l-wms-tile-layer> component like so: <l-wms-tile-layer :options="{ cql_filter: 'watershedcode >0'}"></l-wms-tile-layer>
I heavily suggest you consult the vuejs documentation, as it will greatly help you understand how this plugin interacts with leaflet.js

Thank you, I have succeeded to display the the map with cql_filter just like the way you do. But I wan to update the map for the event. I create a button: I want to onclick the button the filter will be different for example: cql_filter: 'watershedcode >10'.
As normal, i could use the function in leaflet like overlay.Watershed.setParams({CQL_FILTER:" watershedcode >10"}); when click on the button. But for Vue-Leaflet. I cant find the way

Wonderful. I have found the way to do it. Thansk you all.
this.$refs.watershed.mapObject.setParams({cql_filter: 'watershedcode >10});


Build fails

Building with Telerik fails with the following error
Link: ld: framework not found Metal for architecture armv7
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Link: ld: framework not found Metal for architecture armv7s

clang: error: linker command failed with exit code 1 (use -v to see invocation)
Link: ld: framework not found Metal for architecture arm64

clang: error: linker command failed with exit code 1 (use -v to see invocation)

Which plugin id? (Telerik)
Need:

XCode version.
Cordova version.
List of installed plugins (cordova plugin ls)

We don't use Metal framework in library, matbe it solution for you problem?
https://www.appsee.com/blog/dev/xcode-new-link-frameworks-automatically-fix-framework-not-found-metal-for-architecture-armv7


Fix warnings

This PR fixes nearly all of the warnings emitted by gcc with -Wall -Wextra.
Only warnings from the dependencies (which are unused parameter warnings) remain.
Fixes #197

Interesting changes.  I wonder how I got so much unused code in here.


Sizing a dock to fit within a page

Hello,
I was wondering if or how you can resize the height of a dock to fit within a div container. It seems that the default is the window height.
Thanks in advance!

I actually have the same question. One way of doing it is with dockStyle so you can set the height of you dock something like this:
const dockStyle = {   left: '40px',   top: '40px',   height: '88.5%', };
<Dock position='left'  size = {sizeOfDock} isVisible={visible} zIndex={0} dimMode='none' dockStyle={dockStyle}>
So this works for the height and top of the dock, however  I cannot get "left : 40px" to work... any ideas?

@lauritapear Oh that's a good idea on the height of the Dock. Maybe left doesn't work since it's a left position dock, did you try using "right: 40px".


Go to definition on ICollection<'T> shows me ICollection

Go to definition on ICollection<'T> (but also all the other generic/nongeneric types) shows me ICollection, once ICollection is visited once. This looks like a cache lookup issue not taking into account generic parameters.
open System.Collections
let x: Generic.ICollection<int> = null
let y: ICollection = null

Repro:

Go to Generic.ICollection<'T> on x, everything fine.
Go to ICollection on y, also fine.
Go to Generic.ICollection<'T> on x again, end up on ICollection.

Not reproduced in Rider 2022.2.
Can you re-check, please?

I also cannot reproduce it. @NinoFloris If you happen to see this again, please let us know.


Scrollspy on bodytag not working on wordpress site

I'm having troubles putting to work scrollspy in one page of my site:
https://www.agenciaboutique.cl/work/supremevision/nosotros
I did everything like bootstrap docs says and more. Tried calling the target with js aswell but nothing works. Also thought that js file wasn't working but if I add scrollspy to another element inside the code with height it works. But I need it to work on the body tag.
Could you help me?

For help/support of this kind, please use StackOverflow or similar - see https://github.com/twbs/bootstrap/blob/master/CONTRIBUTING.md#using-the-issue-tracker


Discord Tags without numbers aren't supported.

When trying to fill in the "Discord Tag (Optional)" field with a new discord tag format such as "loohney" instead of "loohney#1234" it won't let me save it and it says "Discord tag contains invalid characters".
This is nothing big, but should get fixed now with the new discord tag formats.

Hmm, I would guess this is related to the signup code maybe using a regex that was missed in the recent changes to fix this, since changing names from the settings panel seems to work. For now, I'd suggest using that as a workaround.

@BlankParenthesis thank you for the reply.
While browsing through the network of forks, i found this commit.
https://github.com/Nizrabed/Pxls/commit/166c5c195dfb7033367153a3d3c4f64c9c182271

Yes, there is an active PR for those changes #672 but that regex looks correct for the case you're talking about before and after that change. It might be nice to fix this issue in that PR if possible though.

While experimenting, i noticed the commit that i posted earlier isn't doing anything. It's not even touching the regex. And it's also not even checking the regex.
I removed } else if (!discord.isEmpty() && !discord.matches("^.+?#\\d{4}")) {             respond(exchange, StatusCodes.BAD_REQUEST, new space.pxls.server.packets.http.Error("bad_discord", "Discord tag contains invalid characters"));             return;
from src/main/java/space/pxls/server/WebHandler.java and its working now. Removing the #\d{4} would also work, but would make the check obsolete, thats why i removed it entirely.


Upgrade to rollup v4

TODO

Wait for FredKSchott/rollup-plugin-polyfill-node#77

or replace with https://github.com/privatenumber/pkgroll

close in tag v0.2.18


ZeroDivisionError: Weights sum to zero, can't be normalized

I encountered the following problem while running a local search from Google Colab:
command:
python -m graphrag.query --root ./ragtest --method local \
"What are the differences between Russian, Western, and North Korean approaches to war?"

output:
2024-07-11 16:23:41.000800: E external/local_xla/xla/stream_executor/cuda/cuda_dnn.cc:9261] Unable to register cuDNN factory: Attempting to register factory for plugin cuDNN when one has already been registered
2024-07-11 16:23:41.000856: E external/local_xla/xla/stream_executor/cuda/cuda_fft.cc:607] Unable to register cuFFT factory: Attempting to register factory for plugin cuFFT when one has already been registered
2024-07-11 16:23:41.002564: E external/local_xla/xla/stream_executor/cuda/cuda_blas.cc:1515] Unable to register cuBLAS factory: Attempting to register factory for plugin cuBLAS when one has already been registered
2024-07-11 16:23:42.205100: W tensorflow/compiler/tf2tensorrt/utils/py_utils.cc:38] TF-TRT Warning: Could not find TensorRT

INFO: Reading settings from ragtest/settings.yaml
creating llm client with {'api_key': 'REDACTED,len=9', 'type': "openai_chat", 'model': 'gemma2', 'max_tokens': 4000, 'temperature': 0.0, 'top_p': 1.0, 'request_timeout': 180.0, 'api_base': 'http://localhost:11434/v1', 'api_version': None, 'organization': None, 'proxy': None, 'cognitive_services_endpoint': None, 'deployment_name': None, 'model_supports_json': True, 'tokens_per_minute': 0, 'requests_per_minute': 0, 'max_retries': 10, 'max_retry_wait': 10.0, 'sleep_on_rate_limit_recommendation': True, 'concurrent_requests': 25}
creating embedding llm client with {'api_key': 'REDACTED,len=9', 'type': "openai_embedding", 'model': 'nomic_embed_text', 'max_tokens': 4000, 'temperature': 0, 'top_p': 1, 'request_timeout': 180.0, 'api_base': 'http://localhost:11434/api', 'api_version': None, 'organization': None, 'proxy': None, 'cognitive_services_endpoint': None, 'deployment_name': None, 'model_supports_json': None, 'tokens_per_minute': 0, 'requests_per_minute': 0, 'max_retries': 10, 'max_retry_wait': 10.0, 'sleep_on_rate_limit_recommendation': True, 'concurrent_requests': 25}
Error embedding chunk {'OpenAIEmbedding': 'Error code: 404 - {'error': "model 'nomic_embed_text' not found, try pulling it first"}'}
Traceback (most recent call last):
  File "/usr/lib/python3.10/runpy.py", line 196, in _run_module_as_main
    return _run_code(code, main_globals, None,
  File "/usr/lib/python3.10/runpy.py", line 86, in _run_code
    exec(code, run_globals)
  File "/content/graphrag-ways-of-war/graphrag-local-ollama/graphrag/query/__main__.py", line 76, in <module>
    run_local_search(
  File "/content/graphrag-ways-of-war/graphrag-local-ollama/graphrag/query/cli.py", line 154, in run_local_search
    result = search_engine.search(query=query)
  File "/content/graphrag-ways-of-war/graphrag-local-ollama/graphrag/query/structured_search/local_search/search.py", line 118, in search
    context_text, context_records = self.context_builder.build_context(
  File "/content/graphrag-ways-of-war/graphrag-local-ollama/graphrag/query/structured_search/local_search/mixed_context.py", line 139, in build_context
    selected_entities = map_query_to_entities(
  File "/content/graphrag-ways-of-war/graphrag-local-ollama/graphrag/query/context_builder/entity_extraction.py", line 55, in map_query_to_entities
    search_results = text_embedding_vectorstore.similarity_search_by_text(
  File "/content/graphrag-ways-of-war/graphrag-local-ollama/graphrag/vector_stores/lancedb.py", line 118, in similarity_search_by_text
    query_embedding = text_embedder(text)
  File "/content/graphrag-ways-of-war/graphrag-local-ollama/graphrag/query/context_builder/entity_extraction.py", line 57, in <lambda>
    text_embedder=lambda t: text_embedder.embed(t),
  File "/content/graphrag-ways-of-war/graphrag-local-ollama/graphrag/query/llm/oai/embedding.py", line 96, in embed
    chunk_embeddings = np.average(chunk_embeddings, axis=0, weights=chunk_lens)
  File "/usr/local/lib/python3.10/dist-packages/numpy/lib/function_base.py", line 550, in average
    raise ZeroDivisionError(
ZeroDivisionError: Weights sum to zero, can't be normalized

now, when running a global search, it responds without errors:
INFO: Reading settings from ragtest/settings.yaml
creating llm client with {'api_key': 'REDACTED,len=9', 'type': "openai_chat", 'model': 'gemma2', 'max_tokens': 4000, 'temperature': 0.0, 'top_p': 1.0, 'request_timeout': 180.0, 'api_base': 'http://localhost:11434/v1', 'api_version': None, 'organization': None, 'proxy': None, 'cognitive_services_endpoint': None, 'deployment_name': None, 'model_supports_json': True, 'tokens_per_minute': 0, 'requests_per_minute': 0, 'max_retries': 10, 'max_retry_wait': 10.0, 'sleep_on_rate_limit_recommendation': True, 'concurrent_requests': 25}

SUCCESS: Global Search Response: I am sorry but I am unable to answer this question given the provided data.

The entire indexing pipeline ran without issues, too (I pulled the 'nomic_embed_text' model, and it seems to work? I'm not sure what the error message is about).
config:

encoding_model: cl100k_base
skip_workflows: []
llm:
  api_key: ${GRAPHRAG_API_KEY}
  type: openai_chat # or azure_openai_chat
  model: gemma2
  model_supports_json: true # recommended if this is available for your model.
  # max_tokens: 4000
  # request_timeout: 180.0
  api_base: http://localhost:11434/v1
  # api_version: 2024-02-15-preview
  # organization: <organization_id>
  # deployment_name: <azure_model_deployment_name>
  # tokens_per_minute: 150_000 # set a leaky bucket throttle
  # requests_per_minute: 10_000 # set a leaky bucket throttle
  # max_retries: 10
  # max_retry_wait: 10.0
  # sleep_on_rate_limit_recommendation: true # whether to sleep when azure suggests wait-times
  # concurrent_requests: 1 # the number of parallel inflight requests that may be made

parallelization:
  stagger: 0.3
  # num_threads: 50 # the number of threads to use for parallel processing

async_mode: threaded # or asyncio

embeddings:
  ## parallelization: override the global parallelization settings for embeddings
  async_mode: threaded # or asyncio
  llm:
    api_key: ${GRAPHRAG_API_KEY}
    type: openai_embedding # or azure_openai_embedding
    model: nomic_embed_text
    api_base: http://localhost:11434/api
    # api_version: 2024-02-15-preview
    # organization: <organization_id>
    # deployment_name: <azure_model_deployment_name>
    # tokens_per_minute: 150_000 # set a leaky bucket throttle
    # requests_per_minute: 10_000 # set a leaky bucket throttle
    # max_retries: 10
    # max_retry_wait: 10.0
    # sleep_on_rate_limit_recommendation: true # whether to sleep when azure suggests wait-times
    # concurrent_requests: 25 # the number of parallel inflight requests that may be made
    # batch_size: 16 # the number of documents to send in a single request
    # batch_max_tokens: 8191 # the maximum number of tokens to send in a single request
    # target: required # or optional

chunks:
  size: 300
  overlap: 100
  group_by_columns: [id] # by default, we don't allow chunks to cross documents

input:
  type: file # or blob
  file_type: text # or csv
  base_dir: "input"
  file_encoding: utf-8
  file_pattern: ".*\\.md$"

cache:
  type: file # or blob
  base_dir: "cache"
  # connection_string: <azure_blob_storage_connection_string>
  # container_name: <azure_blob_storage_container_name>

storage:
  type: file # or blob
  base_dir: "output/${timestamp}/artifacts"
  # connection_string: <azure_blob_storage_connection_string>
  # container_name: <azure_blob_storage_container_name>

reporting:
  type: file # or console, blob
  base_dir: "output/${timestamp}/reports"
  # connection_string: <azure_blob_storage_connection_string>
  # container_name: <azure_blob_storage_container_name>

entity_extraction:
  ## llm: override the global llm settings for this task
  ## parallelization: override the global parallelization settings for this task
  ## async_mode: override the global async_mode settings for this task
  prompt: "prompts/entity_extraction.txt"
  entity_types: [organization,person,geo,event]
  max_gleanings: 0

summarize_descriptions:
  ## llm: override the global llm settings for this task
  ## parallelization: override the global parallelization settings for this task
  ## async_mode: override the global async_mode settings for this task
  prompt: "prompts/summarize_descriptions.txt"
  max_length: 500

claim_extraction:
  ## llm: override the global llm settings for this task
  ## parallelization: override the global parallelization settings for this task
  ## async_mode: override the global async_mode settings for this task
  # enabled: true
  prompt: "prompts/claim_extraction.txt"
  description: "Any claims or facts that could be relevant to information discovery."
  max_gleanings: 0

community_report:
  ## llm: override the global llm settings for this task
  ## parallelization: override the global parallelization settings for this task
  ## async_mode: override the global async_mode settings for this task
  prompt: "prompts/community_report.txt"
  max_length: 2000
  max_input_length: 8000

cluster_graph:
  max_cluster_size: 10

embed_graph:
  enabled: false # if true, will generate node2vec embeddings for nodes
  # num_walks: 10
  # walk_length: 40
  # window_size: 2
  # iterations: 3
  # random_seed: 597832

umap:
  enabled: false # if true, will generate UMAP embeddings for nodes

snapshots:
  graphml: yes
  raw_entities: yes
  top_level_nodes: yes

local_search:
  # text_unit_prop: 0.5
  # community_prop: 0.1
  # conversation_history_max_turns: 5
  # top_k_mapped_entities: 10
  # top_k_relationships: 10
  # max_tokens: 12000

global_search:
  # max_tokens: 12000
  # data_max_tokens: 12000
  # map_max_tokens: 1000
  # reduce_max_tokens: 2000
  # concurrency: 32

I humbly submit my heinous hack. I suspect when local instead of global is used, some lists of all zero weight elements come under consideration. The attempt to normalize their zero weight contributions fails and the np.average ZeroDivisionError occurs. I put a try block in the embedding.py code like this:
Daves hack to avoid divide by zero
    try:
        chunk_embeddings = np.average(chunk_embeddings, axis=0, weights=chunk_lens)
        chunk_embeddings = chunk_embeddings / np.linalg.norm(chunk_embeddings)
    except ZeroDivisionError:
        return [] # return empty list
    return chunk_embeddings.tolist() # would always work in global

Seems to work.

I humbly submit my heinous hack. I suspect when local instead of global is used, some lists of all zero weight elements come under consideration. The attempt to normalize their zero weight contributions fails and the np.average ZeroDivisionError occurs. I put a try block in the embedding.py code like this:
Daves hack to avoid divide by zero
    try:
        chunk_embeddings = np.average(chunk_embeddings, axis=0, weights=chunk_lens)
        chunk_embeddings = chunk_embeddings / np.linalg.norm(chunk_embeddings)
    except ZeroDivisionError:
        return [] # return empty list
    return chunk_embeddings.tolist() # would always work in global

Seems to work.

This seems to generate completely out of context response


TypeScript Error: Props Missing on Material-Tailwind Components

Hi,
I've encountered an issue with the latest version of the Material-Tailwind library where TypeScript throws errors indicating that certain props are missing from the components, even when using them as documented. According to the TypeScript errors, props such as placeholder, onPointerEnterCapture, and onPointerLeaveCapture are missing from components like Typography, Button, Card, and TabsHeader.
I tried versions 2.1.9 and 2.1.4
For instance, when using the Typography component like so:
tsx
<Typography className="my-5 font-normal !text-gray-600">
text
</Typography>

TypeScript expects props that aren't typically required or documented, resulting in the following error:
Type '{ children: string; className: string; }' is missing the following properties from type 'Pick<TypographyProps, "id" | "children" | ... >': placeholder, onPointerEnterCapture, onPointerLeaveCapture
This issue is not isolated to Typography but extends to other components such as Button, Card, and TabsHeader, suggesting a broader issue with the TypeScript type definitions within the library.
Normally, these components don't require additional props for basic usage, as per the official documentation. This leads me to believe there might be an issue with the type definitions provided.
Could you please look into this? It's possible that the TypeScript definitions might need to be updated to reflect the actual required props for these components or to mark these additional props as optional if they are not intended to be mandatory.

changing types/react version with "18.2.42", solve the problem

changing types/react version with "18.2.42", solve the problem

Thanks for this. it worked

No no its not working there is no issue but the warning  is still there

No no its not working there is no issue but the warning is still there

 "@material-tailwind/react": "^2.1.4",
"next": "v13.5.7-canary.25",
 "react": "^18",
    "react-dom": "^18",
 "devDependencies": {
    "@types/jsonwebtoken": "^9.0.4",
    "@types/node": "^20",
    "@types/react": "18.2.42",
    "@types/react-dom": "^18",
    "autoprefixer": "^10",
    "eslint": "^8",
    "eslint-config-next": "13.5.6",
    "postcss": "^8",
    "tailwindcss": "^3",
    "typescript": "^5"
  }


Add MyViewCounts

It's not quite a badge, but a while back I made an application called MyViewCounts, a view counter to embed in READMEs that allows the greatest amount of customizability when compared with other view counters!
Here's the Website: https://myviewcounts.rayhanadev.repl.co/
Here's the Github Repo: https://github.com/RayhanADev/MyViewCounts
Here's a View Counter on my Profile: https://github.com/RayhanADev#custom-viewcounter
Let me know what you think!

Awww not quite made for this?


Force parameters method to be static

It would be interesting if JUnitParams had some way to force all or to configure the method used as source of the parameters to be static, making it easier to users to prepare for the migration to JUnit 5 @MethodSource

I guess you want to point out all the places where you don't have static methods by some failing tests to be sure that all places are ready to migration. Unfortunately we miss such feature.

I've made a custom annotation to implement this behavior using the junitparams.custom.CustomParameters annotation.
Currently it's not the most beautiful code because I had to copy a lot of code from ParamsFromMethodCommon, but it works like the JUnit 5 equivalent. Should I make a pull request or there is no plan to add this kind of functionality to JUnitParams?

Please make a pull request and we will see how it looks.


Video finish Listener

Yes, as the title. How can I check when video finish?
Thank so much.

Override onAutoComplete(){}

Thank, lets me try

How is it going

works


🚀 Flow 2ways Sync

SubEpic of 🚀 Prod Trackers 2ways Sync

Strategy
Flow addon must support two ways synchronization of all relevant data.
This includes syncronizing:

[ ] One way sync of User
[x] Entity hierarchy (anatomy and entities themselves)
[x] Entity attributes (anatomy and attributes values on entities)
[x] Statuses
[ ] Assignments
[ ] Comments
[ ] Reviewables

Generic User Stories
(Applicable for each of the checkbox in the strategy section)

As an Artist or Lead, when I [do something] in the production tracker, I want the changes to be visible in AYON.
As an Artist or Lead, when I [do something] in AYON Activity Feed, I the changes to be visible in the production tracker.

I believe the two-way synchronization of statuses and assignments is already done, but it needs to be tested. As far as I remember, it was implemented by @fabiaserra.

I believe the two-way synchronization of statuses and assignments is already done, but it needs to be tested. As far as I remember, it was implemented by @fabiaserra.

That's correct, it's been working fine for us

I believe the two-way synchronization of statuses and assignments is already done, but it needs to be tested. As far as I remember, it was implemented by @fabiaserra.

That's correct, it's been working fine for us

It looks like it's only working on your fork. I checked the assignees, and there's no sign that we're syncing user assignments on tasks. This might be because we haven't merged User syncing #76 yet.

It looks like it's only working on your fork. I checked the assignees, and there's no sign that we're syncing user assignments on tasks. This might be because we haven't merged User syncing #76 yet.

Hmmm that shouldn't be necessary, although perhaps thanks to that functionality I can make some assumptions due to our login field in SG matching the username in AYON without having to do extra gimmicks: https://github.com/fabiaserra/ayon-shotgrid/blob/release/alkemyx/services/shotgrid_common/utils.py#L686
Coincidentally, I just finished a refactor of the user syncing functionality in our fork so it syncs the users and its project access (or role if they are admin, management and producers so they have access to all projects) automatically when there's a project assignment event in Shotgrid so you don't have to click any button. Here are the relevant changes on that: https://github.com/fabiaserra/ayon-shotgrid/blob/release/alkemyx/services/shotgrid_common/ayon_shotgrid_hub/update_from_shotgrid.py#L467 and https://github.com/fabiaserra/ayon-shotgrid/blob/release/alkemyx/services/leecher/leecher/listener.py#L109
And I also added support for when there's hierarchy changes in the Shotgrid project (a shot gets parented to a sequence after the sync already happened) those get re-parented as expected, that change was done here: https://github.com/fabiaserra/ayon-shotgrid/blob/release/alkemyx/services/shotgrid_common/ayon_shotgrid_hub/match_shotgrid_hierarchy_in_ayon.py#L133

It looks like it's only working on your fork. I checked the assignees, and there's no sign that we're syncing user assignments on tasks. This might be because we haven't merged User syncing #76 yet.

Well duh, I see that you never merged this other PR either https://github.com/ynput/ayon-shotgrid/pull/113, this one is the one relevant to get that functionality working


ignite generate listview ScreenName generates class named 'View' which causes collisions with ReactNative.View

Hey there! Ignite CLI seems to be having a problem, eh?
Welllllll, it just might be. First, search the issues to make sure it's not already
here, and if not head over to http://community.infinite.red to
get some help. If you've identified that it's really an Ignite CLI issue, then:

Explain what's going on and preferably how to replicate the issue (bonus points for a repro app)
Run ignite doctor and paste the result below, including the lines with 3 backticks
Delete these instructions! We don't want to look at them. ;)

What's going on?
Using ignite generate listview ScreenName generates a class called View which obviously collides with ReactNative.View

Steps to reproduce

Create new ignite app with ignite new PizzaApp -b ir-boilerplate
Attempt ignite generate listview ScreenName from CLI
Observe error

ignite doctor results:
System
  platform           darwin
  arch               x64
  cpu                8 cores                                                          Intel(R) Xeon(R) CPU E5-1620 v2 @ 3.70GHz
  directory          /Users/lustig/Development/ReactNative/IgnitePractice/Textables

JavaScript
  node               9.6.1        /usr/local/bin/node
  npm                5.8.0        /usr/local/bin/npm
  yarn               1.3.2        /usr/local/bin/yarn

React Native
  react-native-cli   2.0.1
  app rn version     0.55.1

Ignite
  ignite             2.1.0        /usr/local/bin/ignite

Android
  java               1.8.0_102    /usr/bin/java
  android home       -            /Users/lustig/Android/sdk

iOS
  xcode              9.4.1

Screenshot:

Steps to resolve:

Rename styles file associated with new class and update reference
Rename references and imports in AppNavigation.js
Depending on boilerplate used, rename

export default connect(mapStateToProps, mapDispatchToProps)(View)
TO
export default connect(mapStateToProps, mapDispatchToProps)(ScreenName)

I believe the ListView generator in Andross was depricated in favor of the List generator, but for some reason was never disabled. Sorry about the confusion.

@kevinvangelder Can we close this issue?


What is the reason to require blueprintid in assignment file if Blueprint is already passed to cmdlet?

Confused with wording here https://docs.microsoft.com/en-us/azure/governance/blueprints/how-to/manage-assignments-ps#example-2-use-a-json-assignment-definition-file which using assignment file with published blueprint id as part of it. What is reason to have blueprint -Blueprint parameter in such cases. (Example is below https://docs.microsoft.com/en-us/powershell/module/az.blueprint/new-azblueprintassignment?view=azps-5.2.0#example-4)

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

ID: 54bc2b59-0178-5a45-c8f7-a1544ded4d7a
Version Independent ID: fd23e3db-d408-ebdd-b8fc-908ea2f12b47
Content: How to manage assignments with PowerShell - Azure Blueprints
Content Source: articles/governance/blueprints/how-to/manage-assignments-ps.md
Service: blueprints
GitHub Login: @DCtheGeek
Microsoft Alias: dacoulte

@artisticcheese Thanks for your comment! We will review and provide an update as appropriate.

So if your site uses asynchronous tags... does this allow you to set your exchange accordingly?


module directory name not consistent between centOS and Ubuntu

The module directory is not named the same between CentOS and Ubuntu images, avoiding the same MPI scripts to be used across platforms.
On CentOS : /usr/share/Modules/modulefiles/mpi/
On Ubuntu : /usr/share/modules/modulefiles/mpi

yes, this continued when we moved to AlmaLinux from CentOS. It bothers me too, so I'll look into it.

When I asked, I was told this was intentional. I'm not sure on the reason.


dateparser.parse only returns NoneType object when using AWS EC2 (Running Python 3.7.9)

Running the following simple code works just fine on my local machine running Python 3.7.3, but returns only object type None when running the same file on an AWS EC2 instance running Python 3.7.9. Any thoughts what could be going on?
Script:
#!/usr/bin/env python
import dateparser

date1 = '2020-01-01'
date2 = '12/13/2020'
date3 = 'December 15, 2020'
date4 = 'Saturday, Dec 12'
date5 = '12-12-2020'
date1p = dateparser.parse(date1)
date2p = dateparser.parse(date2)
date3p = dateparser.parse(date3)
date4p = dateparser.parse(date4)
date5p = dateparser.parse(date5)
print("Date 1 Original:", date1)
print("Date 1 Parsed:", date1p)
print("Date 2 Original:", date2)
print("Date 2 Parsed:", date2p)
print("Date 3 Original:", date3)
print("Date 3 Parsed:", date3p)
print("Date 4 Original:", date4)
print("Date 4 Parsed:", date4p)
print("Date 5 Original:", date5)
print("Date 5 Parsed:", date5p)

Output on local machine running 3.7.3:
Date 1 Original: 2020-01-01
Date 1 Parsed: 2020-01-01 00:00:00
Date 2 Original: 12/13/2020
Date 2 Parsed: 2020-12-13 00:00:00
Date 3 Original: December 15, 2020
Date 3 Parsed: 2020-12-15 00:00:00
Date 4 Original: Saturday, Dec 12
Date 4 Parsed: 2020-12-12 00:00:00
Date 5 Original: 12-12-2020
Date 5 Parsed: 2020-12-12 00:00:00

Output on EC2 with 3.7.9:
Date 1 Original: 2020-01-01
Date 1 Parsed: None
Date 2 Original: 12/13/2020
Date 2 Parsed: None
Date 3 Original: December 15, 2020
Date 3 Parsed: None
Date 4 Original: Saturday, Dec 12
Date 4 Parsed: None
Date 5 Original: 12-12-2020
Date 5 Parsed: None

Any ideas?

This is really weird.... :thinking:
@srschaecher could you add print(dateparser.__version__)?
could you try changing the code to this:
#!/usr/bin/env python
from dateparser.date import DateDataParser

ddp = DateDataParser()

date1 = '2020-01-01'
date2 = '12/13/2020'
date3 = 'December 15, 2020'
date4 = 'Saturday, Dec 12'
date5 = '12-12-2020'
date1p = ddp.get_date_data(date1)
date2p = ddp.get_date_data(date2)
date3p = ddp.get_date_data(date3)
date4p = ddp.get_date_data(date4)
date5p = ddp.get_date_data(date5)
print("Date 1 Original:", date1)
print("Date 1 Parsed:", date1p)
print("Date 2 Original:", date2)
print("Date 2 Parsed:", date2p)
print("Date 3 Original:", date3)
print("Date 3 Parsed:", date3p)
print("Date 4 Original:", date4)
print("Date 4 Parsed:", date4p)
print("Date 5 Original:", date5)
print("Date 5 Parsed:", date5p)

or adding languages=['en'] or some settings to see if it's related to that?
Thanks

This module is awesome, by the way. I didn't mention that in my post above. This saved me so much time in having to parse a bunch of different format date fields in a job I have that scrapes messages from some specific Slack channels and parses data out of messages. This thing is amazingly flexible, nice job!
Regarding this problem though, still no luck... Running the above on my local machine gives me:
Date 1 Original: 2020-01-01
Date 1 Parsed: DateData(date_obj=datetime.datetime(2020, 1, 1, 0, 0), period='day', locale='en')
Date 2 Original: 12/13/2020
Date 2 Parsed: DateData(date_obj=datetime.datetime(2020, 12, 13, 0, 0), period='day', locale='en')
Date 3 Original: December 15, 2020
Date 3 Parsed: DateData(date_obj=datetime.datetime(2020, 12, 15, 0, 0), period='day', locale='en')
Date 4 Original: Saturday, Dec 12
Date 4 Parsed: DateData(date_obj=datetime.datetime(2020, 12, 12, 0, 0), period='day', locale='en')
Date 5 Original: 12-12-2020
Date 5 Parsed: DateData(date_obj=datetime.datetime(2020, 12, 12, 0, 0), period='day', locale='en')

But on the EC2 server:
Date 1 Original: 2020-01-01
Date 1 Parsed: DateData(date_obj=None, period='day', locale=None)
Date 2 Original: 12/13/2020
Date 2 Parsed: DateData(date_obj=None, period='day', locale=None)
Date 3 Original: December 15, 2020
Date 3 Parsed: DateData(date_obj=None, period='day', locale=None)
Date 4 Original: Saturday, Dec 12
Date 4 Parsed: DateData(date_obj=None, period='day', locale=None)
Date 5 Original: 12-12-2020
Date 5 Parsed: DateData(date_obj=None, period='day', locale=None)

Dateparser version on both is the same:
>>> print(dateparser.__version__)
1.0.0

Adding the languages definition didn't seem to help either. It is odd, right? I'm not quite sure where to look next to troubleshoot.

I'm not sure if this is helpful, but I'm getting the same behaviour when deploying using singularity  on a university HPC running Red Hat.  Python version is 3.9.1, dateparser==1.0.0.
Unlike the OP, though, the DDP suggestion works for me.  Thank you, and thank you for the excellent library :-)

I'm not sure if this is helpful, but I'm getting the same behaviour when deploying using singularity  on a university HPC running Red Hat.  Python version is 3.9.1, dateparser==1.0.0.
Unlike the OP, though, the DDP suggestion works for me.  Thank you, and thank you for the excellent library :-)

realted to: https://github.com/scrapinghub/dateparser/issues/872

Hi @StephenWattam @srschaecher
I know it was some time ago, but if you have the chance, could you try with the approach in this comment? https://github.com/scrapinghub/dateparser/issues/896#issuecomment-797432988
If we confirm that this is the reason, we can try to fix it or add a comment in the documentation.
thanks


Can not create Event Taps

I'm sure I'm missing something here–I'm new to Mac development. But I tried for several hours last night, and couldn't come up with a way to create an event tap. I don't see the CGEventTapCreate function anywhere in the documentation. Am I meant to import "C" to accomplish something like this?
I tried doing something like objc.Call[corefoundation.MachPortRef](...), but couldn't figure out a valid handle to give, and everything I tried panicked because the handle was nil.
I am using the 0.5.0-preview, so maybe the functions I need just haven't landed yet? I was just confused because all of the supporting constants/types (i.e., EventTapLocation, EventTapOptions, etc.) do exist.

We don't create function bindings yet, but yes you can use CGO in the meantime.

👍 Got it. Thanks for the reply!


GraphiteReporter should reconnect when connection fails temporarily

With Metrics 3.1.0 GraphiteReporter we had a problem where data was no longer sent to graphite server. This happened after some network component was rebooted. Same server is sending data also with Metrics  2.1.3  GraphiteReporter. Older graphite reporters kept on sending data just fine.
Sounds like this could be related to #607.
Stacktrace from 3.1.0:
2014-10-22 12:00:21,036 [WARN] [] [] com.codahale.metrics.graphite.GraphiteReporter.report(GraphiteReporter.java:179) Unable to report to Graphite: java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
        at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:282)
        at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:125)
        at java.io.OutputStreamWriter.write(OutputStreamWriter.java:207)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:129)
        at java.io.BufferedWriter.write(BufferedWriter.java:230)
        at java.io.Writer.write(Writer.java:157)
        at com.codahale.metrics.graphite.Graphite.send(Graphite.java:130)
        at com.codahale.metrics.graphite.GraphiteReporter.reportGauge(GraphiteReporter.java:270)
        at com.codahale.metrics.graphite.GraphiteReporter.report(GraphiteReporter.java:158)
        at com.codahale.metrics.ScheduledReporter.report(ScheduledReporter.java:162)
        at com.codahale.metrics.ScheduledReporter$1.run(ScheduledReporter.java:117)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
 : java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
        at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:282)
        at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:125)
        at java.io.OutputStreamWriter.write(OutputStreamWriter.java:207)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:129)
        at java.io.BufferedWriter.write(BufferedWriter.java:230)
        at java.io.Writer.write(Writer.java:157)
        at com.codahale.metrics.graphite.Graphite.send(Graphite.java:130)
        at com.codahale.metrics.graphite.GraphiteReporter.reportGauge(GraphiteReporter.java:270)
        at com.codahale.metrics.graphite.GraphiteReporter.report(GraphiteReporter.java:158)
        at com.codahale.metrics.ScheduledReporter.report(ScheduledReporter.java:162)
        at com.codahale.metrics.ScheduledReporter$1.run(ScheduledReporter.java:117)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)

2014-10-22 12:00:21,037 [WARN] [] [] com.codahale.metrics.graphite.GraphiteReporter.report(GraphiteReporter.java:183) Error closing Graphite: java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
        at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:282)
        at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:125)
        at java.io.OutputStreamWriter.write(OutputStreamWriter.java:207)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:129)
        at java.io.BufferedWriter.write(BufferedWriter.java:230)
        at java.io.Writer.write(Writer.java:157)
        at com.codahale.metrics.graphite.Graphite.send(Graphite.java:130)
        at com.codahale.metrics.graphite.GraphiteReporter.reportGauge(GraphiteReporter.java:270)
        at com.codahale.metrics.graphite.GraphiteReporter.report(GraphiteReporter.java:158)
        at com.codahale.metrics.ScheduledReporter.report(ScheduledReporter.java:162)
        at com.codahale.metrics.ScheduledReporter$1.run(ScheduledReporter.java:117)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)
 : java.net.SocketException: Broken pipe
        at java.net.SocketOutputStream.socketWrite0(Native Method)
        at java.net.SocketOutputStream.socketWrite(SocketOutputStream.java:113)
        at java.net.SocketOutputStream.write(SocketOutputStream.java:159)
        at sun.nio.cs.StreamEncoder.writeBytes(StreamEncoder.java:221)
        at sun.nio.cs.StreamEncoder.implWrite(StreamEncoder.java:282)
        at sun.nio.cs.StreamEncoder.write(StreamEncoder.java:125)
        at java.io.OutputStreamWriter.write(OutputStreamWriter.java:207)
        at java.io.BufferedWriter.flushBuffer(BufferedWriter.java:129)
        at java.io.BufferedWriter.write(BufferedWriter.java:230)
        at java.io.Writer.write(Writer.java:157)
        at com.codahale.metrics.graphite.Graphite.send(Graphite.java:130)
        at com.codahale.metrics.graphite.GraphiteReporter.reportGauge(GraphiteReporter.java:270)
        at com.codahale.metrics.graphite.GraphiteReporter.report(GraphiteReporter.java:158)
        at com.codahale.metrics.ScheduledReporter.report(ScheduledReporter.java:162)
        at com.codahale.metrics.ScheduledReporter$1.run(ScheduledReporter.java:117)
        at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
        at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:304)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:178)
        at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
        at java.lang.Thread.run(Thread.java:745)

+1 on a release of this fix. Is there any ETA?
In the meantime, is it feasible to roll back to 3.0.2 as suggested by @velvia without losing important changes? I don't see a changelog anywhere.

+1 on 3.1.1 release.  Any timeline?  This is causing us issues in production...

+1. When it will be fixed??? Guys do this simple fix - make us happier

@ryantenney
Can you clarify what 'very soon' means, from "Closed as fixed in #669, and 3.1.1 will be out very soon."

@ryantenney Can you re-open this issue? As it is, I can not add dependencies to this project from mine in good conscience. 3.1.1 has not seen the light of day, and 4.0 may not be here for awhile yet.

@jshook I just pushed 3.1.1 to Maven Central, check for it an hour or two. I'm sorry for the delay, a lot of things have been getting in the way.


Handle parameterised generics

Closes #597

Nice @DiamondJoseph , I wanted to know if we can test the BlueAPI endpoints as part of this PR or should they be separate...It is so that we can have more confidence in our code that it is working

The endpoints themselves have tests (test_rest_api.py) however these are unit tests and don't test the subprocess, or actually running a plan etc.
runner.py has its own unit tests  which could possibly be enhanced to catch this.
When refactoring in this area it took me a very long time to fix up the tests as they were all mocking various things across many levels of indirection including private components. The tests are now closer to actual unit tests.
What blueapi needs now is probably some form of system tests to confirm end to end functionality and results.
I would probably suggest that this would be done as part of a different change.

@DiamondJoseph Have written and pushed some test cases, all but one pass

I think https://github.com/pydantic/pydantic/issues/6870 is the cause of our failing test case. In the debug console:
from typing import Generic, TypeVar
from pydantic import BaseModel, TypeAdapter

T = TypeVar("T")

class GenericModel(BaseModel, Generic[T]):
    t: T

g = GenericModel[int](t=1)
h = GenericModel(t=2)

ta = TypeAdapter(GenericModel)
ta2 = TypeAdapter(GenericModel[int])

ta.validate_python(g)
ta.validate_python(h)
ta2.validate_python(g)
# fails
ta2.validate_python(h)

As the return annotation of the function is ~GenericModel[int].


take ip-list without port

nmap call with ports throws an error
current behavior
Debug: Exec[bootstrap_galera_cluster](provider=shell): Executing check '["/bin/sh", "-c", "nmap -Pn -p 4567 <IP_ADDRESS>:4567 <IP_ADDRESS>:4567 | grep -q '4567/tcp open'"]' Debug: Executing: '/bin/sh -c nmap -Pn -p 4567 <IP_ADDRESS>:4567 <IP_ADDRESS>:4567 | grep -q '4567/tcp open'' Debug: /Stage[main]/Galera/Exec[bootstrap_galera_cluster]/unless: Failed to resolve "<IP_ADDRESS>:4567". Debug: /Stage[main]/Galera/Exec[bootstrap_galera_cluster]/unless: Failed to resolve "<IP_ADDRESS>:4567". Debug: /Stage[main]/Galera/Exec[bootstrap_galera_cluster]/unless: WARNING: No targets were specified, so 0 hosts scanned. Debug: Exec[bootstrap_galera_cluster](provider=shell): Executing '["/bin/sh", "-c", "/usr/bin/galera_new_cluster"]' Debug: Executing: '/bin/sh -c /usr/bin/galera_new_cluster' Notice: /Stage[main]/Galera/Exec[bootstrap_galera_cluster]/returns: executed successfully (corrective) Info: /Stage[main]/Galera/Exec[bootstrap_galera_cluster]: Scheduling refresh of Exec[validate_connection]
expected behavior
Debug: Exec[bootstrap_galera_cluster](provider=shell): Executing check '["/bin/sh", "-c", "nmap -Pn -p 4567 <IP_ADDRESS> <IP_ADDRESS> | grep -q '4567/tcp open'"]' Debug: Executing: '/bin/sh -c nmap -Pn -p 4567 <IP_ADDRESS> <IP_ADDRESS> | grep -q '4567/tcp open'' Debug: /Stage[main]/Galera/Exec[bootstrap_galera_cluster]: '/usr/bin/galera_new_cluster' won't be executed because of failed check 'unless'

Merged, thanks!


Allocate from an audit page

This change makes it possible to allocate content from the audit page.
Further, it actually prevents users from auditing content that is not
allocated to them.

 (5) Add 'This item is not assigned to anyone.' bar

Review app: https://cpm-prototype-432.herokuapp.com/audits


Window position changes with external monitors

I am using a MacBook with an External Monitor:
Starting with monitor plugged in:
When renew is invoked & set to --position center the window is positioned in the center.

when I unplug the monitor the window then locks to the top right of the screen
plugging the monitor back in relocates it to the center or sometimes to relocates it to the bottomleft

Starting with the monitor unplugged:
When renew is invoked & set to --position center the window is positioned in the center.

when I plug the monitor in the window shifts down and to the left
unplugging the monitor relocates the window to the center on macbook screen

closing this. seems to be related to swiftDialog and not renew.


Consultation about unit execution sequence

Hello, when I execute the following code, it seems that I can not run from the Feedstock unit (U101), resulting in Water1.F_mass is still obtained with the initial mass flow of stream Ethanol instead of with the flow rate of Ethanol calculating through Ethanol.F_mass =Feedstock.F_mass*0.098.
If I want to run U101 first, then through Ethanol.F_mass =Feedstock.F_mass*0.098 to get the flow rate of stream Ethanol, and then through Water1.F_mass = Ethanol.F_mass*7 to get the flow rate of stream Water1. Could I ask you how to solve it? Thanks for your help. Wish you a good day.
The code is as follows.
import biosteam as bst
from biosteam.units.decorators import cost
from biosteam import units
bst.nbtutorial()
from biorefineries import cellulosic
cs = cellulosic.Biorefinery('corn stover ethanol')
chemicals = cs.chemicals
bst.settings.set_thermo(chemicals)
bst.main_flowsheet.set_flowsheet('Glucose')

Water1 = bst.Stream(
    ID='Water1',
    price=0.0516,
    total_flow=8992.8669,
    units='kg/hr',
    Water=1,
)

Glucose = bst.Stream(
    ID='Glucose',
    price=0.0516,
    total_flow=1,
    units='kg/hr',
    Glucose=1,
)

Feedstock = bst.Stream(
    ID='Feedstock',
    price=0.0516,
    total_flow=10,
    units='kg/hr',
    Glucose=1,
)

Ethanol = bst.Stream(
    ID='Ethanol',
    price=0.0516,
    total_flow=10,
    units='kg/hr',
    Ethanol=1,
)

U101 = cellulosic.units.FeedStockHandling('U101', Feedstock)
U101.cost_items['System'].cost = 0.

@cost('Flow rate', 'Mixer', S=136260, units='kg/hr',
      CE=522, cost=6000, n=0.5, BM=1)
class GlucoseMixer(bst.Mixer): pass
M201 = GlucoseMixer('M201', [Ethanol, Glucose])
@M201.add_specification(run=True)
def update_Ethanol():
    Ethanol.F_mass =Feedstock.F_mass*0.098

M202 = units.Mixer('M202', [U101-0, M201-0])
P201 = units.Pump('P201', M202-0, P=1.5*101325)
H201 = units.HXutility('H201', P201-0, T=50+273.15)
P202 = units.Pump('P202', H201-0, P=2*101325)
P203 = units.Pump('P203', P202-0, P=2*101325)
@P203.add_specification(run=False)
def adjust_pump_pressure_P203():
    P203._run()
    After_P202 = P202-0
    P203.P = After_P202.P + 0.1*101325
P204 = units.Pump('P204', P203-0, P=1.1*101325)
@P204.add_specification(run=False)
def adjust_pump_pressure_P204():
    P204._run()
    After_P203 = P203-0
    P204.P = After_P203.P + 0.1*101325
P205 = units.Pump('P205', Water1, P=1.1*101325)
@P205.add_specification(run=True)
def update_Water():
    Water1.F_mass = Ethanol.F_mass*7
M203 = units.Mixer('M203', [P205-0])
F201 = units.Flash('F201', M203-0, Q=0, P=101325)
@F201.add_specification(run=False)
def adjust_flash_pressure_F201():
    F201._run()
    F201_inlet = M203-0
    F201.P = F201_inlet.P
M204 = units.Mixer('M204', [F201-1, P204-0])
sys = bst.main_flowsheet.create_system('sys')
sys.simulate()
sys.diagram('thorough', format='png', number=True)
Water1.F_mass

I tried the other code a few times, sometimes running from unit P205, sometimes running from unit U101, and it looked a little strange.

Hello, could I trouble you take some time to look at this problem. Thanks for your help. Wish you a good day.

Hello, could I trouble you take some time to look at this problem? I still can't control the running order of the unit, but it is very important for the accuracy of the result. Thanks for your help.

If I want to run U101 and M201 first and then P205, could I ask you what code to call? The current running order affects the accuracy of the results.


Added help files for bceid and IDIR users

Added Help file for both bceid and IDIR users.
Changelog:

Added pdf files as help files for both IDIR and bceid users.

 Help | Make BCeID guide available in TFRS for BCeID users |1|

 Help | Make IDIR guide available in TFRS for IDIR users |1|


Fixes after Weld 1.x -> 2.x upgrade

@mariofusco, @mdproctor could you please review? This is kind of urgent as the kie-wb is currently not working without the Weld 2.x upgrade.
Depends on:
https://github.com/droolsjbpm/droolsjbpm-build-bootstrap/pull/173

The failing test is not caused by this PR, but since it is CDI related it would be great why it is intermittently failing.
+1 for me


Some strings returns INIFINITY

Settings applied: raw: true, rawNumbers: true
Example of string wrong interpreted:
"3E17773446"
The whole row in CSV was:
"86","3E17773446","For sale ","5/5/2021 11:12:18 AM"

Thank you!

@SheetJSDev Can i take this up ?

@SheetJSDev @reviewher
Can I work on this issue?

e7346ddfbe4ae40d8193e558cc61dc7eb6ea9511