Add reduce scripts

Note
This PR had a previous home at https://github.com/ClangBuiltLinux/misc-scripts/pull/4
But now lives here as suggested by: https://github.com/ClangBuiltLinux/misc-scripts/pull/4#pullrequestreview-1546542798

This PR aims to introduce a new family of scripts aimed at helping kernel developers reduce target files efficiently.
An example workflow may look something like this:
> CI robot identifies build failure in some kernel source tree

> Developer wants to isolate the issue and find its root cause

> Developer builds that source tree version and, sure enough, replicates the issue. They're still lost as to what is causing the failure.

> Developer runs `$ python reduce.py prep lib/broken`

> Developer now has access to `broken.i`, `test.sh` and `flags.txt`.

> Developer designs interestingness test that fully encompasses the issue/behavior they're looking for.

> Developer wants to minimize the number of compiler flags being used and thus runs `$ python reduce.py flags`

> Now, there is a minimized `flags.txt`.

> They then run `$ cvise test.sh broken.i` (and wait awhile).

The developer now has both 1) the minimal flags and 2) minimal pre-processed source to reproduce some behavior

Another possible feature to come is one that automatically creates a repro.txt file which adequately displays the necessary information to reproduce build failures (i.e: compiler version, minimal flags used, minimal pre-processed code, kernel version, etc). The idea is that this repro.txt can then be shared with others (via mailing lists or chats).
It should be noted these scripts are not zero-dependency. Their dependencies are listed in the README.
Below is a copy of the README.md.
CBL/reduce
A family of scripts to prepare and execute reduction (cvise, llvm-reduce) workflows.
Currently, there are two scripts:

prep

Prepare a target file for reduction (see Basic Usage)

flags

Minimize the compiler flags required to reproduce behavior. Use after prep

Dependencies

Python 3.11
icecream
C-Vise

Basic Usage
$ python reduce.py -h
prep

Get help with prep

$ python reduce.py prep -h

Prepare lib/string for reduction by producing a
string.i, test.sh and a flags.txt in a temporary directory which are
ready-for-consumption by tools like cvise and llvm-reduce

$ python reduce.py prep lib/string -p /path/to/linux -o $(mktemp -d)

Or, try providing a custom build command

$ reduce prep -p $LINUX -o $(mktemp -d) -- make -j8 LLVM=1 V=1 lib/string
flags

Get help with flags

$ python reduce.py flags -h

After running prep, reduce flags.txt

$ python reduce.py flags

Note
Change your cwd to wherever flags.txt is located or try the -p option.

Contributions
Author: Justin Stitt<EMAIL_ADDRESS>Suggested-by: Nick Desaulniers<EMAIL_ADDRESS>

Thanks, still LGTM, although now that this is in its own repo, I think we can move everything into the repo root, rather than having everything under reduce/?
Consider adding a CODEOWNERS file like we have in other repositories to ensure someone always gets added for review and standing up some linting/formatting workflows to ensure that the code stays consistent. Follow up PRs are fine for those, they are not mission critical.

Yep, just did this before seeing your question. My copying from repo to repo resulted in a nested folder. Fixed. Thanks.

I will leave the PR up for code reviewing purposes. Let me know once its OK to merge into CBL/reduce.


Is it not compatible with newest stable node.js or io.js ?

It looks like only compatible with 0.10.* node version .
my environment is OSX Yosemite.

We are testing against both<EMAIL_ADDRESS>and iojs so they should work. What is the error you are seeing and can you copy/paste your grunt config for the sprite task?
https://github.com/Ensighten/grunt-spritesmith/blob/4.6.1/.travis.yml

after i switched my node version to<EMAIL_ADDRESS>. It shows error when i run it.
Fatal error: Cannot define property:48, object is not extensible.
my config for sprite as follow.
    sprite: {
            sprites: {
                src: 'images/sprites/*.png',
                destImg: 'images/sprites.png',
                imgPath: '../images/sprites.png?'+ timestamp,
                destCSS: 'less/mod/sprites.less',
                cssFormat: 'css',
                //cssTemplate: 'sprites.mustache',
                cssOpts: {
                    cssClass: function(item) {
                        return '.' + item.name;
                    }
                },
                padding: 0
            },
            logo: {
                src: 'images/logo/*.png',
                destImg: 'images/logo.png',
                imgPath: '../images/logo.png?'+ timestamp,
                destCSS: 'less/mod/logo.less',
                cssFormat: 'css',
                //cssTemplate: 'sprites.mustache',
                cssOpts: {
                    cssClass: function(item) {
                        return '.' + item.name;
                    }
                },
                padding: 0
            }
    },

ps:
i considered it is something wrong in installing. grunt-spritesmith i installed is @1.24.0 .
Both installed  from npm again after delete and npm update command are'nt working.
and the version of this plugin in github is 4.x.x now.
the registry of my npm config is  "http://registry.npmjs.org/"

Yep, your config is very out of date. You need to account for the changed keys in 3.0.0:
https://github.com/Ensighten/grunt-spritesmith/tree/4.7.1#breaking-changes-in-300
    sprite: {
            sprites: {
                src: 'images/sprites/*.png',
                dest: 'images/sprites.png',
                imgPath: '../images/sprites.png?'+ timestamp,
                destCss: 'less/mod/sprites.less',
                cssFormat: 'css',
                //cssTemplate: 'sprites.mustache',
                cssOpts: {
                    cssSelector: function(item) {
                        return '.' + item.name;
                    }
                },
                padding: 0
            },
            logo: {
                src: 'images/logo/*.png',
                dest: 'images/logo.png',
                imgPath: '../images/logo.png?'+ timestamp,
                destCss: 'less/mod/logo.less',
                cssFormat: 'css',
                //cssTemplate: 'sprites.mustache',
                cssOpts: {
                    cssSelector: function(item) {
                        return '.' + item.name;
                    }
                },
                padding: 0
            }
    },

If things are still not working, then please paste the full error from grunt sprite.


Email notifier does not send an email when testing the notifier

Rancher versions:
rancher/server: v2.0.0-beta2
Steps to Reproduce:

Create cluster
use Add Notifier via Tools -> Notifiers
Choose Email, fill in the required fields
Hit Test, UI shows Please check your chosen application for the notifier.

Results:

No email is sent

The captured API call is (stripped):
'{"type":"notifier","name":"testemail","description":null,"clusterId":"cluster-dqdxx","smtpConfig":{"defaultRecipient":"xxx","host":"xxx","password":"xxx","port":25,"tls":false,"type":"/v3/schemas/smtpConfig","username":"xx"},"id":"cluster-dqdxx:notifier-lff2z","uuid":"2eae6926-3d01-11e8-905b-0242ac110002"}'

If I include "message":"test message", I do receive the email:
'{"type":"notifier","name":"testemail","description":null,"clusterId":"cluster-dqdxx","smtpConfig":{"defaultRecipient":"xxx","host":"xxx","password":"xxx","port":25,"tls":false,"type":"/v3/schemas/smtpConfig","username":"xx"},"id":"cluster-dqdxx:notifier-lff2z","message":"test message","uuid":"2eae6926-3d01-11e8-905b-0242ac110002"}'

@superseb The Test button will not send out an email.  It will just validate if the smtp config is valid or not by only calling the smtp auth API.  The reason why we don't send out an email is that the test message is usually treated as spam by email provider.

@zionwu Can we change the message to Settings validated or something, instead of Please check your chosen application for the notifier which is not the case for email.

@superseb sure, it is a bug for the message in UI. We will have it fixed

This makes no sense.. the other types send a test message, email should too.  There shouldn't be anything different about the test message versus an actual alert, and half the point of testing is to see if the message actually makes it through filtering or not.

Yep, we should use a test message that is similar to an actual alert for testing email.

Dependent on #13516

2.0 master 5/18 - not fixed
I entered my email info and clicked on test and it gave it me a error.  I saved same notifier and it worked fine when I attached it to a alert.

@tfiduccia I could not reproduce this? Look like network problem.


[#3261] Fix wrong packet.getLength()==0 logic

#3261

Codecov Report

Merging #3264 into master will increase coverage by 0.13%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master    #3264      +/-   ##
==========================================
+ Coverage   39.44%   39.58%   +0.13%
==========================================
  Files        2077     2077
  Lines       68109    68102       -7
  Branches     9463     9460       -3
==========================================
+ Hits        26868    26960      +92
+ Misses      38638    38529     -109
- Partials     2603     2613      +10

Impacted Files
Coverage Δ

...p/pinpoint/collector/receiver/udp/UDPReceiver.java
72.47% <100%> (+72.47%)
:arrow_up:

...pinpoint/profiler/instrument/AccessorAnalyzer.java
65.71% <0%> (+8.57%)
:arrow_up:

...nitor/DefaultDataSourceMonitorRegistryService.java
88.88% <0%> (+11.11%)
:arrow_up:

...rp/pinpoint/collector/receiver/DispatchWorker.java
17.94% <0%> (+17.94%)
:arrow_up:

Continue to review full report at Codecov.

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


Contribute.

Hello, I wanna contribute to your Project.  What if we change the background according to our requirements using One-Shot Detection and try to work on our own handwriting. I can give it a try.

Yes , we are open to PR's


provide a method to chunk the weights before importing them into Burn

Description
I encountered difficulties when importing the weights of an LSTM from PyTorch. This is because PyTorch often tends to concatenate different weights together, resulting in significant differences between the structure of LSTM weights in PyTorch and those in Burn. Therefore, I think it is necessary for PyTorchFileRecorder to provide a method to chunk the weights before importing them into Burn.

In Burn the weights of lstm are saved through eight Linears.

If you could provide a minimal code, we will look into this. PyTorch screen shot appears to store weights as an array, which is supported by PyTorchFileRecorder.

Sure.
Rust code:
use burn::{
    backend::{ndarray::NdArrayDevice, NdArray},
    module::Module,
    nn::{Linear, LinearConfig, Lstm, LstmConfig},
    record::{FullPrecisionSettings, Recorder},
    tensor::{backend::Backend, Tensor},
};
use burn_import::pytorch::PyTorchFileRecorder;

#[derive(Module, Debug)]
pub struct Model<B: Backend> {
    lstm: Lstm<B>,
    linear: Linear<B>,
}

impl<B: Backend> Model<B> {
    pub fn new(device: &B::Device) -> Self {
        Self {
            lstm: LstmConfig::new(10, 20, true).init(device),
            linear: LinearConfig::new(20, 30).init(device),
        }
    }

    pub fn forward(&self, input: Tensor<B, 3>) -> Tensor<B, 3> {
        let (_, out) = self.lstm.forward(input, None);
        self.linear.forward(out)
    }
}

fn main() {
    type Backend = NdArray;
    let device = NdArrayDevice::Cpu;

    let record = PyTorchFileRecorder::<FullPrecisionSettings>::default()
        .load("./example.pt".into(), &device)
        .expect("Should decode state successfully");

    let model: Model<Backend> = Model::new(&device).load_record(record);
}

Python code:
import torch
from torch import nn

class Model(nn.Module):
    def __init__(self):
        super().__init__()

        self.lstm = nn.LSTM(10, 20)
        self.linear = nn.Linear(20, 30)

    def forward(self, input: torch.Tensor) -> torch.Tensor:
        out, _ = self.lstm(input)
        return self.linear(out)

if __name__ == "__main__":
    model = Model()
    input = torch.randn(2, 8, 10)
    res = model(input)
    print(res.shape)
    print([name for name, _ in model.named_parameters()])

    torch.save(model, "./example.pt")

@antimora @laggui  Therefore, importing LSTM's weights from PyTorch should do some remap like this

lstm.weight_ih_l0 => lstm.input_gate.input_transform.weight
                  => lstm.forget_gate.input_transform.weight
                  => lstm.cell_gate.input_transform.weight
                  => lstm.output_gate.input_transform.weight

lstm.bias_ih_l0   => lstm.input_gate.input_transform.bias
                  => lstm.forget_gate.input_transform.bias
                  => lstm.cell_gate.input_transform.bias
                  => lstm.output_gate.input_transform.bias

lstm.weight_hh_l0 => lstm.input_gate.hidden_transform.weight
                  => lstm.forget_gate.hidden_transform.weight
                  => lstm.cell_gate.hidden_transform.weight
                  => lstm.output_gate.hidden_transform.weight

lstm.bias_hh_l0   => lstm.input_gate.hidden_transform.bias
                  => lstm.forget_gate.hidden_transform.bias
                  => lstm.cell_gate.hidden_transform.bias
                  => lstm.output_gate.hidden_transform.bias

Here is what I would recommend you to unblock you quickly. It will be a while since we handle this use case.
Create a corresponding PyTorch module for lstm type matching the source attributes, so you can load the source PyTorch record without issues. I recommend the following module structure to match the source:
#[derive(Module, Debug)]
pub struct LstmIntermediate<B: Backend>  {
  pub weight_ih_l0: Param<Tensor<B, 2>>,
  pub weight_hh_l0: Param<Tensor<B, 2>>,
  pub bias_ih_l0: Param<Tensor<B, 1>>,
  pub bias_hh_l0: Param<Tensor<B, 1>>,
}

impl <B: Backend> LstmIntermediate<B> {
   fn into_lstm(self) -> Lstm<B> {
      ...
   }
}

Once you have it loaded, you can extract the data and chunk them up. You can your logic in into_lstm.
After you made the transformation, just save in Burn's record format so you can load without transformation next time.


[WIP] HIPCMS-847: Move user-related data to HiP-UserStore

Welcome Reviewer! Have fun! 😃
The counterpart to this PR is PR #13 in HiP-UserStore.
Important changes:

Configuration fields have changed, see appsettings.Development.json.example
Upgraded project to .NET Core 2.0
Removed User- and StudentDetails-tables from database
Modified the other tables so they store user IDs as strings (the Auth0 user ID) instead of integers
Removed user-related APIs (they moved to UserStore)
HiP-CmsWebApi now references the NuGet package "HiP-UserStore.Sdk" to query user data

For more comments and open issues see the corresponding Jira task.

This PR is done. We are now waiting for HIPCMS-867 to be done. 867 and this one should be merged "in parallel".


links lead to 404

Thanks @beeburrt, indeed. I'll try to make it available via github pages.

In the meantime the docs are back at https://mtod.org/wb/


added paging function in query on whoosh

Modified query_on_whoosh.py so that it takes current_page, items_per_page as inputs and outputs the corresponding pages.

The README file is not updated with the new arguments the query_on_whoosh has now.


Safari Debugger fails to run

When running steroids connect, I tried to open the safari debugger with the sd command.  Safari did indeed open, but before steroids could get a list of view addresses for me to select from, steroids raised the error:
ERROR: Error on line 246: TypeError: undefined is not an object (evaluating 'menu.getMenuItems') (0)
After raising the Error steroids returned to regular execution by bringing up the next command prompt.  Safari remained open.
This could very well have something to do with the fact that I recently updated Safari to the latest version (v8.0.2; I am running OS X 10.10.1) although I do not know for sure, as I never tried to run sd on the older version.

Have you enabled the Safari Developer menu?

Are you using a Debug Scanner which you have built from the Build Service ?

Ah, my bad.  I should have thought of that.  Once I enabled develop in the Safari preferences it works.  Thanks!

Thanks! We'll need to provide a human readable error for the case where Developer menu has not been enabled.


Falco version and driver version are not coupled anymore

What type of PR is this?
/kind bug
/kind cleanup
Any specific area of the project related to this PR?
/area build
/area tests
What this PR does / why we need it:
This PR introduces some fixes and updates needed because the Falco version and the driver version are distinct values now.
So this PR mainly updates the falco-probe-loader script for this reason. Also renaming it to falco-driver-loader.
Futhermore, this script obtains now some values (like the DRIVER_VERSION variable value) at configuration time.
Finally it also ensures that the FALCO_VERSION env variable inside docker containers contains the same value returned by falco --version, not the docker image tag.
Which issue(s) this PR fixes:
Fixes #1107
Special notes for your reviewer:
Does this PR introduce a user-facing change?:
update: falco-probe-loader is falco-driver-loader
new: falco version and driver version are distinct

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign leodido
You can assign the PR to them by writing /assign @leodido in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

cc @fntlnz

/cc @fntlnz

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 85e68d8a97229ab5431c158007d0c16a92773630

New changes are detected. LGTM label has been removed.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign fntlnz
You can assign the PR to them by writing /assign @fntlnz in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

/cc @kris-nova

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: kris-nova
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [kris-nova]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 2faf64b02d684c0d410cfac3352838e81721c1ff

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: fntlnz, kris-nova
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [fntlnz,kris-nova]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Changing editor-version doesn't force re-export of pages

Steps to reproduce:

Set editor-version to v1 in antora-playbook.yml
Publish some pages to Confluence
Change editor-version to v2
Run antora-confluence again
Observe that pages still use legacy editor

The issue is that page hash only considers source page source: https://github.com/PacoVK/antora-confluence/blob/0.3.2/lib/service/PageService.ts#L422
Either antora-confluence needs to account for publishing settings (editor-version, maybe others) or there needs be some option to force re-publish.

Okay, actually v2 is broken currently. Trying to view v2 pages on cloud Confluence leads to server errors on their side :D


Lightspeed colors seem off

Some of the colors Onenord uses for lightspeed.nvim cause issues when using the plugin. For example, Lightspeed highlights all of the unique characters in the viewport, but these are quite hard to see when using Onenord:

For comparison, here's the same view when using the Nordfox theme from nightfox.nvim:

Likewise, the colors used when jumping are a bit confusing. Here, the first character indicates a match, and the second character indicates the character that will jump to that match, but they're so similar that it's hard to know which is which at a glance:

I think Nordfox doesn't modify these colors at all, so they're pretty ugly, but you can see that there's a lot of contrast between the first and second characters, which makes it easier to parse:

I'd put in a PR, but I'm frankly inept when it comes to anything color-related. I saw that the author of Lightspeed just updated the guidelines for color scheme integration, so maybe that could provide some guidance.

Hi again, sorry about this, I didn't know about the guidelines posted by the author so I just tried out something similar to Nord.nvim. I'll read it tonight and try to come up with something that's stylized but also fits the guidelines!

No need to apologize, and thank you!

I had some time to look at it so it's definitely more usable now but I'm not sure about the colors either, for now it is just a toned down version of the original. Any thoughts?
Original:

Onenord:

Fixed unique characters:

Looks great IMO!

Alright thanks, I just pushed a commit so let me know if you still see any problems!

Way easier to use. Thank you for the changes!


Added hooks for validate

Added hooks for validate
Use validate BE endpoint in every step

#2733  👈
main

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

Join @tommylau523 and the rest of your teammates on  Graphite


.Net: ConversationSummarySkill assign explicit function names

Motivation and Context
Give ConversationSummarySkill semantic functions explicit names so they are not assigned random ones at runtime. This allows them to be more easily recognized when described (such as GetFunctionsView).
Fixes #2230
Description
Give ConversationSummarySkill semantic functions explicit names so they are not assigned random ones at runtime.
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[x] I didn't break anyone :smile:

@shawncal Stripping async and assigning the semantic function names would directly conflict with the existing native functions. I've updated the naming on the native functions to make it more clear to the caller what each function is designed for.

Create constants in SemanticFunctionConstants.cs for semantic function names
Insert "Long" into the native function definitions to give an indication they are designed for long inputs
Keep Example13_ConversationSummarySkill.cs consistent in that it runs the semantic functions (the example conversation transcript is only ~1,300 tokens so it will fit in model context windows fine)
Update AISummary.tsx to use the "long" functions as the input is variable

@shawncal Stripping async and assigning the semantic function names would directly conflict with the existing native functions. I've updated the naming on the native functions to make it more clear to the caller what each function is designed for.

Create constants in SemanticFunctionConstants.cs for semantic function names
Insert "Long" into the native function definitions to give an indication they are designed for long inputs
Keep Example13_ConversationSummarySkill.cs consistent in that it runs the semantic functions (the example conversation transcript is only ~1,300 tokens so it will fit in model context windows fine)
Update AISummary.tsx to use the "long" functions as the input is variable

Ah, I see the problem. Because the semantic functions are being "registered" with the kernel, we effectively end up with two "SummarizeConversation" functions, two "GetConversationActionItems" functions, etc. when looking at the FunctionsView. Problem is, that'll all be given to the Planners too... either with the random names (without this change) or the "Long" names (with this change). Neither is ideal.
We've got changes coming soon to how semantic functions are handled by the kernel, and this highlights a good case for why they shouldn't always be registered in the kernel, but rather sometimes they should merely be transient and invokable by a kernel (without registration).
Let me take a look at the work there and see if this case would be handled.

To follow up on this, we do plan on making changes with regards to how semantic functions can be created in a more lightweight fashion, reducing the need for a change like this. For now, the obfuscation of the semantic functions by name is intentional. Thanks for your time in filing the issue and the pr itself.


automatic registration in the vertx ServiceDiscovery

Another suggestion:
the automatic registration of rest service on ServiceDiscovery should be interesting.
for example:
@ServiceDiscovery("api.name", "host", port, "root")
@Path("/")
public FlowerService {
}
translated in vertx:
Record record = HttpEndpoint.createRecord(name, host, port, root, new JsonObject().put("api.name", name));
serviceDiscovery = ServiceDiscovery.create(vertx, new ServiceDiscoveryOptions().setBackendConfiguration(config()));
serviceDiscovery.publish(record, ar ->
{
if (ar.succeeded())
{
registeredRecords.add(record);
logger.info("Service <" + ar.result().getName() + "> published");
future.complete();
}
else
{
future.fail(ar.cause());
}
});
what do you think about it?

That's very interesting, except I think the host/port parts should come from the current config, no? It seems error-prone to specify them in the code when they are deployment-dependent. I guess the same could be said of the root.
But certainly, it would be useful to declare services with an annotation. I think the name should be enough, the rest we can get from the config.

Yes, the host/port/root parts are always derived from server config and @Path annotations.
But in vertx you must declare that.

Sure, but they don't belong in the annotation if the framework can detect them. Unless they're not required/defaulted.


Removing phrase not preserving marker info

Adapt It Mobile Version: 1.0 beta 10
Severity: 1 - data integrity
Description: When removing a phrase during some other testing, I noticed that the marker info is not being preserved.
Steps to Reproduce:

Launch AIM and start adapting
Starting at a source phrase that has a marker, select several source phrases and create a phrase.
Select the newly-created phrase and remove it.

--> Note that the markers are not preserved when the source phrase is removed.

Issue is also there for retranslations -- and retranslations do not preserve the marker in the UI when a retranslation is created.


BPDM API Versioning for GR and Country Risk

Description

Impact

Additional information

[ ] I'm willing to contribute to this feature

out-dated


Shape resize issue with UIBezierPath

Hi, I created shapes using 'UIBezierPath' and 'CAShape layer' and then added to stickerview. But I couldn't resize it. Anyone please help me to sort this out. Thanks in advance.

use this
https://github.com/chenkaijie4ever/Single-hand-Sticker


Added Linear Algebra by Gilbert Strang

Added Linear Algebra by Gilbert Strang Great Video materials freely available from MIT.
https://github.com/datasciencemasters/go/compare/master...sriharshams:master#diff-04c6e90faac2675aa89e2176d2eec7d8

Thanks for contributing! Have you seen some or all of these lectures? How would you describe them? I'd love to include more lecture-style videos, but have struggled to find more accessible teaching styles in this domain in particular.

Yes I have seen these lectures, complemented with the book it is a really
good free material. I really like Gilbert Strang passionate lectures and
how he provokes thoughts in students via lectures. I havent finished all
the lectures yet.
On Tue, Jan 31, 2017 at 10:38 AM Clare<EMAIL_ADDRESS>wrote:

Thanks for contributing! Have you seen some or all of these lectures? How
would you describe them? I'd love to include more lecture-style videos, but
have struggled to find more accessible teaching styles in this domain in
particular.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/datasciencemasters/go/pull/120#issuecomment-276451437,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABtU5gHOacg-NOdsFnalxgUSe1eHL2IRks5rX3-igaJpZM4LE-8k
.


Demo Store Template: ShopPayButton seems to be inert

What is the location of your example repository?
pnpm create @shopify/hydrogen@latest with Demo Store template
What version of Hydrogen are you using?
2023.1.2
What version of Remix are you using?
1.12.0
Steps to Reproduce

pnpm create @shopify/hydrogen@latest with Demo Store template
navigate to a product page in browser (eg /products/snowboard)
click on Shop Pay button

Expected Behavior
Clicking on Shop Pay button navigates to Shopify's pay page.
Actual Behavior
Clicking on Shop Pay button seems to do nothing and stays on the product page.
Dev Tools console contains message: [Shop Pay] Store URL (test) is not valid TypeError: Failed to construct 'URL': Invalid URL
ShopPayButton.d.ts in @shopify/hydrogen-react has comment indicating that  is needed.
/**
 * The `ShopPayButton` component renders a button that redirects to the Shop Pay checkout.
 * It renders a [`<shop-pay-button>`](https://shopify.dev/custom-storefronts/tools/web-components) custom element, for which it will lazy-load the source code automatically.
 * It relies on the `<ShopProvider>` context provider.
 */
export declare function ShopPayButton({ variantIds, className, variantIdsAndQuantities, width, }: ShopPayButtonProps): JSX.Element;

 looks like a typo and probably should be . Either way, it is not in the component tree. While @shopify/hydrogen seems to export ShopPayButton, but not ShopifyProvider from @shopify/hydrogen-react.

Mmm yes - that is a typo. That should be ShopifyProvider.
@frehner Maybe a better path is to not rely on useShop and allow storeDomain to be passed in as props?

@wizardlyhel tracking that here https://github.com/Shopify/hydrogen-react/issues/86 🙂


trace-agent: change configuration settings (log_level) at runtime

What does this PR do?

Motivation

Added /config/set endpoint to trace-agent to support changing configuration options at runtime. At the moment, added only changing log_level case.
Closes #6962
Additional Notes
Related to the issue, it could serve useful to also add log_level field to the info handler on trace-agent.

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[x] A release note has been added or the changelog/no-changelog label has been applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.

I will move httpError back but is there is anything else?


AIP-8718 Allow disabling default cards; Allow card render failures

Changes:

Default cards are still added by default to all steps, but user has option to disable it is by passing --add-default-cards false.

TODO: this option needs to be propagated to CICD

Card rendering errors are ignored.

Closes AIP-8718

In general it looks good. I like the use of try/except. Is this something you can add tests for within the repo?


[Bug]: Lincensing information is missing for llama-cloud lib dependency at PYPI

Bug Description
Hi,
After llama-index ver 0.10.55 the verification of the package fails on pip install at our org. It says the licensing information is missing for llama-cloud dependency. And indeed it is not there at PYPI.
Can it be added for llama-cloud please?
For llama-index it is:
Meta
License: MIT License (MIT)
Version
0.11.15
Steps to Reproduce

Go to https://pypi.org/project/llama-cloud/
Check meta section
It is missing licensing

Relevant Logs/Tracbacks
No response

Added
https://pypi.org/project/llama-cloud/

Thanks a ton for a lightening turn around! You are the best!


Error building fsharp when using Mono built from source only

Mono is installed at /mono . It was build from source,
I did the following commands:

$ cd fsharp-master
$ export PKG_CONFIG_PATH=/mono/lib/pkgconf
$ export PATH=$PATH:/mono/bin
$ echo $PATH
/usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/sbin:/mono/bin
$ export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/mono/lib/
$echo $LD_LIBRARY_PATH
:/mono/lib/
$ ./autogen.sh --prefix /mono

I go the following:

checking whether make sets $(MAKE)... yes
checking for pkg-config... /usr/bin/pkg-config
configure: "pkg-config: /usr/bin/pkg-config"
configure: "PKG_CONFIG_LIBDIR: "
configure: PCL Reference Assemblies for Profile 47 found: no
configure: PCL Reference Assemblies for Profile 7 found: no
configure: PCL Reference Assemblies for Profile 78 found: no
configure: PCL Reference Assemblies for Profile 259 found: no
configure: creating ./config.status
config.status: creating launcher
config.status: creating Makefile
config.status: creating config.make
config.status: creating src/fsharp/Makefile
config.status: creating src/fsharp/FSharp.Build-proto/Makefile
config.status: creating src/fsharp/FSharp.Compiler-proto/Makefile
config.status: creating src/fsharp/Fsc-proto/Makefile
config.status: creating src/fsharp/FSharp.Core/Makefile
config.status: creating src/fsharp/FSharp.Build/Makefile
config.status: creating src/fsharp/FSharp.Compiler/Makefile
config.status: creating src/fsharp/Fsc/Makefile
config.status: creating src/fsharp/FSharp.Compiler.Interactive.Settings/Makefile
config.status: creating src/fsharp/FSharp.Compiler.Server.Shared/Makefile
config.status: creating src/fsharp/FSharp.Data.TypeProviders/Makefile
config.status: creating src/fsharp/fsi/Makefile
config.status: creating src/fsharp/fsiAnyCpu/Makefile
config.status: creating src/fsharp/policy.2.0.FSharp.Core/Makefile
config.status: creating src/fsharp/policy.2.3.FSharp.Core/Makefile
config.status: creating src/fsharp/policy.3.3.FSharp.Core/Makefile
config.status: creating src/fsharp/policy.4.0.FSharp.Core/Makefile
config.status: creating src/fsharp/policy.4.3.FSharp.Core/Makefile

And the following command:

$ make

I got the following error:

make -C src/fsharp all
make[1]: Entering directory '/home/monoc/fsharp-master/src/fsharp'
make build-proto
make[2]: Entering directory '/home/monoc/fsharp-master/src/fsharp'
mkdir: can't create directory '/home/monoc/fsharp-master//lib/proto/': File exists
Makefile:15: recipe for target 'build-proto' failed
make[2]: [build-proto] Error 1 (ignored)
cp -p /home/monoc/fsharp-master/lib/bootstrap/4.0/FSharp.Core.dll /home/monoc/fsharp-master//lib/proto/FSharp.Core.dll
cp -p /home/monoc/fsharp-master/lib/bootstrap/4.0/FSharp.Core.sigdata /home/monoc/fsharp-master//lib/proto/FSharp.Core.sigdata
cp -p /home/monoc/fsharp-master/lib/bootstrap/4.0/FSharp.Core.optdata /home/monoc/fsharp-master//lib/proto/FSharp.Core.optdata
make -C FSharp.Build-proto Configuration=proto build-proto
make[3]: Entering directory '/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto'
MONO_ENV_OPTIONS= xbuild /p:Configuration=Proto
XBuild Engine Version 12.0
Mono, Version <IP_ADDRESS>
Copyright (C) 2005-2013 Various Mono authors
Build started 02/21/2015 17:57:35.

Project "/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto/FSharp.Build-proto.fsproj" (default target(s)):
Target CallFsSrGen:
Tool /home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto/../../../lib/bootstrap/4.0/fssrgen.exe execution started with arguments:  /home/monoc/fsharp-master/src/fsharp/FSharp.Build/FSBuild.txt  obj/proto/./FSBuild.fs  FSBuild.resx
/home/monoc/fsharp-master/lib/bootstrap/4.0/FSharp.SRGen.targets: error : Error executing tool '/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto/../../../lib/bootstrap/4.0/fssrgen.exe': ApplicationName='/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto/../../../lib/bootstrap/4.0/fssrgen.exe', CommandLine=' /home/monoc/fsharp-master/src/fsharp/FSharp.Build/FSBuild.txt  obj/proto/./FSBuild.fs  FSBuild.resx ', CurrentDirectory='/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto', Native error= Cannot find the specified file
Task "FsSrGen" execution -- FAILED
Done building target "CallFsSrGen" in project "/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto/FSharp.Build-proto.fsproj".-- FAILED
Done building project "/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto/FSharp.Build-proto.fsproj".-- FAILED
Build FAILED.
Errors:
/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto/FSharp.Build-proto.fsproj (default targets) ->
/home/monoc/fsharp-master/lib/bootstrap/4.0/FSharp.SRGen.targets (CallFsSrGen target) ->
/home/monoc/fsharp-master/lib/bootstrap/4.0/FSharp.SRGen.targets: error : Error executing tool '/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto/../../../lib/bootstrap/4.0/fssrgen.exe': ApplicationName='/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto/../../../lib/bootstrap/4.0/fssrgen.exe', CommandLine=' /home/monoc/fsharp-master/src/fsharp/FSharp.Build/FSBuild.txt  obj/proto/./FSBuild.fs  FSBuild.resx ', CurrentDirectory='/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto', Native error= Cannot find the specified file
0 Warning(s)
1 Error(s)
Time Elapsed 00:00:02.2930690
Makefile:9: recipe for target 'build-proto' failed
make[3]: *** [build-proto] Error 1
make[3]: Leaving directory '/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto'
Makefile:15: recipe for target 'build-proto' failed
make[2]: *** [build-proto] Error 2
make[2]: Leaving directory '/home/monoc/fsharp-master/src/fsharp'
Makefile:10: recipe for target 'all' failed
make[1]: *** [all] Error 2
make[1]: Leaving directory '/home/monoc/fsharp-master/src/fsharp'
Makefile:4: recipe for target 'all' failed
make: *** [all] Error 2

FWIW the error line is below. I don't know what's causing this - Mono should be able to execute this binary.    We don't CI a complete fresh build of Mono + F#.  Did you install any Mono package, or are you really building absolutely everything from scratch?
There's a chance it's related to FsSrGen.exe being a .NET 2.0 binary, though I hope not (I'd find it odd if a fresh compile of Mono didn't run a .NET 2.0 binary).
/home/monoc/fsharp-master/lib/bootstrap/4.0/FSharp.SRGen.targets: error : Error executing tool '/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto/../../../lib/bootstrap/4.0/fssrgen.exe': ApplicationName='/home/monoc/fsharp-master/src/fsharp/FSharp.Build-proto/../../../lib/bootstrap/4.0/fssrgen.exe', CommandLine=' /home/monoc/fsharp-master/src/fsharp/FSharp.Build/FSBuild.txt obj/proto/./FSBuild.fs FSBuild.resx ',

For Mono, I built it everything from scratch to be able to run it in Intel Edison.
I followed the procedure described at http://www.dlsloan.ca/Docs/Edison/monoInstall.html .
It works well for few test with C#.

Pure speculation: is it because mono v4.0 is dropping .Net 2.0 support, perhaps? "We dropped support for the 2.0, 3.5 and 4.0 assemblies" from http://www.mono-project.com/docs/about-mono/releases/4.0.0/

@haf - What are the ramifications of this for the F# build?  Do you think it's the cause of the problem above? thanks

Shouldn't. Checked on chat; .Net 2.0 usage should still be transparent to the user.

Is this bug still a problem?  I think this may have been a Mono bug that has been fixed?

Closing as I believe this is a Mono bug that's been fixed. Please let us know exact repro steps if otherwise.


Sm111 graceful exit

Codecov Report

Merging #53 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #53      +/-   ##
==========================================
+ Coverage   99.55%   99.55%   +<.01%
==========================================
  Files          24       24
  Lines         446      449       +3
==========================================
+ Hits          444      447       +3
  Misses          2        2

Impacted Files
Coverage Δ

...e_operations_ui/controllers/message_controllers.py
100% <100%> (ø)
:arrow_up:

response_operations_ui/views/messages.py
100% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Memory Issue During apply_oe

Memory Issue During apply_oe
Description
I am encountering a memory issue while running isofit using the following configuration:

Image: An 8820x5831x8 WV2 image
Emulator: sRTMnet_v120
Radiative Transfer Model: 6S
Configuration File: ang20171108t184227_surface.json from the 20171108_Pasadena example
(Note: This is not intended as a final solution but to achieve an end-to-end run)

I believe I have properly generated the loc, obs, and rdn files. However, I am confused as to why the slope is 90 degrees for flat ground in the examples. My output .hdr files appear identical to those in the image_cube example, with the exception of different wavelengths and FWHM due to my use of WV2.
Steps to Reproduce
I followed the steps outlined in the NEON example Jupyter notebook. Here is the code and arguments I used:
import ray
ray.shutdown()

args = SimpleNamespace(**{
    'input_radiance': os.path.join(subset_dir, f'{img}_rdn'),  # Radiance
    'input_loc': os.path.join(subset_dir, f'{img}_loc'),       # Location
    'input_obs': os.path.join(subset_dir, f'{img}_obs'),       # Observations
    'working_directory': os.path.join(output, f'{img}'),      # Output directory
    'sensor': 'NA-20111201',

    "surface_path": output_surface_file,                      # Surface priors - often changes
    'emulator_base': os.environ['EMULATOR_PATH'],
    "modtran_path": None,
    'n_cores': 4,
    "copy_input_files": False,
    "wavelength_path": None,
    "surface_category": "multicomponent_surface",
    "aerosol_climatology_path": None,                         # MODTRAN
    "atmosphere_type": "ATM_MIDLAT_SUMMER",                   # MODTRAN
    "rdn_factors_path": None,                                 # RCC update used 'on the fly'
    "channelized_uncertainty_path": None,                     # Channelized uncertainty - if you have an instrument model
    "model_discrepancy_path": None,                           # Model discrepancy term - handle things like unknown radiative transfer model effects
    "lut_config_file": None,
    "multiple_restarts": False,                               # Useful if the AOD conditions are really challenging
    "logging_level": "INFO",
    "log_file": None,
    "num_cpus": 1,
    "memory_gb": -1,
    "presolve": True,                                         # Attempts to solve for the right WV range
    'no_min_lut_spacing': True,
    "empirical_line": False,                                  # Wavelength-specific local linear interpolation between radiance and reflectance
    "analytical_line": True,                                  # Mathematical representation of OE given that the atmosphere is known
    "ray_temp_dir": "/tmp/ray",
    "segmentation_size": 10,
    "num_neighbors": [5],
    "atm_sigma": [0.5, 0.5],
    "pressure_elevation": False,
    "prebuilt_lut": None
})

apply_oe(args)

Observations

The apply_oe function ended in a memory error.
Attached is a file showing the error, as the error message outputted by Jupyter was quite lengthy.

Questions

Does isofit expect to run only on small ROIs?
Are there specific configurations or memory optimizations recommended for handling large images?
Is Slope supposed to be 90 for flat surfaces?

Attachments
error.log

Hey, thanks for this post.  The error you're hitting occurs during the segmentation step, which is a utility run to segment the image into superpixels prior to any of the core isofit routines.
While we've tested large scenes, they are large for imaging spectroscopy acquisitions - what you describe is probably an order of magnitude larger in terms of pixel count than how most spectrometers partition their data, due to the much larger number of wavelengths from the WV dataset.
The most obvious knob to turn here is the segmentation size.  In the above config, you have this set at 10 - that would be fine-scale even if the pixel size were coarse.  For example, EMIT uses 40 with a 60 m pixel size.  Presuming the WV data here is finer spatial resolution, you can up this substantially - likely to 100 - 200 without any issue.  I am not positive, but I believe this will trickle into the SLIC segmentation call.  If not, please post and we can revisit.
The other option at your disposal is the CHUNKSIZE global variable set at the top of apply_oe.  We should make that something that's parameterized elsewhere, but cutting that down guarantees that the SLIC block will use less memory.  With a segmentation size at 10, you could lower that by an order of magnitude to something like 25, which would decrease the memory required in the SLIC call from ~190 GB to 19GB, which should do the trick (depending on your machine).  The option from the previous paragraph is more advisable if it works though, it will also speed things up dramatically.
Explicit answers to your questions:

Does isofit expect to run only on small ROIs?
No, it often runs on large scenes - but certain parameter configurations can lead the utilities to get unwieldy.  The isofit core calls should be fairly robust to this though.

Are there specific configurations or memory optimizations recommended for handling large images?
See above on segmentation size.

Is Slope supposed to be 90 for flat surfaces?
Slope should be 0 for flat surfaces.  With the parameterization set above, slope will not actually be used - this is true for many (but not all) of the examples, and it's possible there are some bad values in the example.


160/integration testing

Issue Number: User Story 160
Summary
Adds Integration Testing framework, examples for multiple endpoints and CICD Step.
Changes

Added Integration testing project for CarbonAwareSDK
Added Endpoint testing for SCI-Scores and Best Locations
Added Wiremock server for outbound mocking
Added CICD Step for integration and unit testing separation

Checklist

[x] Local Tests Passing?
[ ] CICD and Pipeline Tests Passing?
[x] Added any new Tests?
[x] Documentation Updates Made?
[ ] Are there any API Changes? If yes, please describe below.
[x] This is not a breaking change. If it is, please describe it below.

Are there API Changes?
If yes, what are the expected API Changes? Please link to an API-Comparison workflow with the API Diff.
Is this a breaking change?
If yes, what workflow does this break?
Anything else?
Other comments, collaborators, etc.
This PR Closes Issue #

Codecov Report

Merging #78 (561daa0) into dev (37b3c8d) will decrease coverage by 1.63%.
The diff coverage is 5.10%.

@@            Coverage Diff             @@
##              dev      #78      +/-   ##
==========================================
- Coverage   78.79%   77.15%   -1.64%
==========================================
  Files          46       48       +2
  Lines        1273     1440     +167
  Branches      113      131      +18
==========================================
+ Hits         1003     1111     +108
- Misses        223      280      +57
- Partials       47       49       +2

Impacted Files
Coverage Δ

...e/src/Configuration/ServiceCollectionExtensions.cs
0.00% <ø> (ø)

...onAware.Tools.WattTimeClient/src/WattTimeClient.cs
87.06% <ø> (ø)

src/CarbonAware.WebApi/src/Program.cs
83.33% <ø> (+83.33%)
:arrow_up:

...re.Tools.WattTimeClient/src/WattTimeServerMocks.cs
3.15% <3.15%> (ø)

...gregators/src/CarbonAware/CarbonAwareAggregator.cs
90.90% <66.66%> (+0.76%)
:arrow_up:

...are.DataSources.WattTime/src/WattTimeDataSource.cs
86.13% <0.00%> (-0.04%)
:arrow_down:

...bonAware/src/Extensions/EmissionsDataExtensions.cs
98.30% <0.00%> (ø)

...ation/Configuration/ServiceCollectionExtensions.cs
55.00% <0.00%> (+5.00%)
:arrow_up:

src/CarbonAware.WebApi/src/Models/SciScore.cs
100.00% <0.00%> (+80.00%)
:arrow_up:

... and 1 more


Example Implementations?

Is there a example server and client available for testing purposes?

Hello, there are examples. See source code quiche/quic/tools/quic_toy_server.cc and quiche/quic/tools/quic_toy_client.cc.
Or as assembly products (on Linux) - bazel-bin/quiche/quic_server and bazel-bin/quiche/quic_client


What is the compenents of the mixed audio files and how to generate the mixed files?

Hello, it's a nice and brief implementation of FastICA, I wonder to know it better! Well, it seems that each mixed audio file is concatenated by several different source, but the algorithme do once FastICA to them for one analyse of compenents. Isn't the algorithme designed for the problem like cocktail party ? So the input is supposed to be single, right?

Hello! Sorry for the late response. Yes you are right. I think the confusion comes from the fact that I used 9 different files as input and there is 9 different sources but technically you can set the nsources parameter to 1 and the ncomponents parameters to as many as you want. I'll rewrite this part to make it clearer and less confusing


Add Daniel Rivas to Contributors list

@PoorLazlo, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.

@PoorLazlo, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


feat: adds Carousel components and testimonials

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


autoExportPolicy: true not recognized by back-end, but back-end uses auto export policy if it already exists

Describe the bug
autoExportPolicy works unpredictably in the following ways:

autoExportPolicy and autoExportCIDRs are provided in back-end JSON file, but only the latter gets recognized. autoExportPolicy does not get recognized (false).
if trident_qtree_pool_export_policy exists and the back-end is deleted and then created with (any different) autoExportCIDRs, the export policy's CIDR does not get updated (i.e. it remains accessible as per the original CIDR the first time the Qtree export policy was created by Trident, <IP_ADDRESS>/0). I know this is not "unexpected" to those who know about it, but I think it is unpredictable for those who haven't encountered this (so I may create a documentation enhancement request to improve this depending on comments to this issue) .
when autoExportPolicy is set to true, back-end JSON is loaded without issues but the end result (tridentctl get backend) shows autoExportPolicy: false and yet autoExportPolicy appears to partially work in the sense that the FlexVol uses trident_qtree_pool_export_policy and not default or some other
[edit] after submitting this bug I deleted trident_qtree_pool_export_policy and recreated NAS economy back-end, and even though autoExportCIDRs were recognized and shown in back-end definition (as at the top of this list), export CIDRs in trident_qtree_pool_export_policy are still <IP_ADDRESS>/0 and ::/0

Environment

Trident version: 21.04.1
Trident installation flags used: default
Container runtime: version 1.13.1, build 0be3e21/1.13.1
Kubernetes version: v1.11.0
Kubernetes orchestrator: OpenShift (OKD) v3.11
Kubernetes enabled feature gates: (none)
OS: CentOS 7.9
NetApp backend types: ONTAP 9.8P1

To Reproduce
Steps to reproduce the behavior: at some point the default trident_qtree_pool_export_policy was created, so it was in place on vserver3 already. I deleted all PVCs, SCs, and NAS back-ends, while SVMs and Export Policies were left as-is. Then I did the following.

Create back-end with autoExportPolicy set to true

{
    "version": 1,
    "backendName": "ontap-nas_<IP_ADDRESS>-auto-ep",
    "storageDriverName": "ontap-nas-economy",
    "managementLIF": "<IP_ADDRESS>",
    "dataLIF": "<IP_ADDRESS>",
    "svm": "vserver3",
    "username": "admin",
    "password": "NetApp123$",
    "autoExportCIDRs": ["<IP_ADDRESS>/32"],
    "autoExportPolicy": true
}

Examine the new back-end (notice how autoExportCIDRs got loaded (although this doesn't really affect new exports), but autoExportPolicy did not and shows false):

$ tridentctl get backends -n trident ontap-nas_<IP_ADDRESS>-auto-ep -o yaml
items:
- backendUUID: 7cc89e36-d388-418b-b39c-be280e5909fc
  config:
    aggregate: ""
    autoExportCIDRs:
    - <IP_ADDRESS>/32
    autoExportPolicy: false
    backendName: ontap-nas_<IP_ADDRESS>-auto-ep

Create SC and a PVC/PV to use it:

$ oc describe pv default-qtreeguy-ccc78
Name:            default-qtreeguy-ccc78
Labels:          <none>
Annotations:     pv.kubernetes.io/provisioned-by=netapp.io/trident
                 volume.beta.kubernetes.io/storage-class=autoqtree
Finalizers:      [kubernetes.io/pv-protection]
StorageClass:    autoqtree
Status:          Bound
Claim:           default/qtreeguy
Reclaim Policy:  Delete
Access Modes:    RWO
Capacity:        2Gi
Node Affinity:   <none>
Message:
Source:
    Type:      NFS (an NFS mount that lasts the lifetime of a pod)
    Server:    <IP_ADDRESS>
    Path:      /trident_qtree_pool_trident_DJIUOEJTQN/trident_default_qtreeguy_ccc78
    ReadOnly:  false
Events:        <none>

Expected behavior

autoExportPolicy: true, if accepted on back-end create, should not show as autoExportPolicy: false in get backend output
if autoExportPolicy: false is truly in effect, Trident would try to use the export policy default rather than default to an export policy that may not be the one called and considered default. That is, default seems like the logical default policy name and trident_qtree_pool_export_policy does not, when autoExportPolicy: false.

Additional context

Environment:

$ tridentctl version -n trident
+----------------+----------------+
| SERVER VERSION | CLIENT VERSION |
+----------------+----------------+
| 21.04.0        | 21.04.0        |
+----------------+----------------+

$ oc get nodes
NAME      STATUS    ROLES                  AGE       VERSION
m         Ready     compute,infra,master   103d      v1.11.0+d4cacc0

$ cat /etc/redhat-release
CentOS Linux release 7.9.2009 (Core)

FlexVol trident_qtree_pool_trident_DJIUOEJTQN uses trident_qtree_pool_export_policy although back-end description shows autoExportPolicy: false

ONTAP export rules for vserver3 (as mentioned above, trident_qtree_pool_export_policy had existed before and was not deleted prior to new back-end creation, so it's "stale" in the sense that it doesn't reflect the autoExportCIDRs set in latest iteration)

otsc::> export-policy rule show -vserver vserver3 -policyname default
             Policy          Rule    Access   Client                RO
Vserver      Name            Index   Protocol Match                 Rule
------------ --------------- ------  -------- --------------------- ---------
vserver3     default         2       nfs3,    <IP_ADDRESS>/24        any
                                     nfs4,
                                     nfs

otsc::> export-policy rule show -vserver vserver3 -policyname policy_with_no_root_squash
             Policy          Rule    Access   Client                RO
Vserver      Name            Index   Protocol Match                 Rule
------------ --------------- ------  -------- --------------------- ---------
vserver3     policy_with_no_root_squash
                             1       nfs3     <IP_ADDRESS>/24        any

otsc::> export-policy rule show -vserver vserver3 -policyname trident_qtree_pool_export_policy
             Policy          Rule    Access   Client                RO
Vserver      Name            Index   Protocol Match                 Rule
------------ --------------- ------  -------- --------------------- ---------
vserver3     trident_qtree_pool_export_policy
                             1       nfs      <IP_ADDRESS>/0             any
vserver3     trident_qtree_pool_export_policy
                             2       nfs      ::/0                  any
2 entries were displayed.

Just realized that in the latest Trident documentation there's a note that autoExportPolicy works only with Trident CSI, which in my case isn't (OCP 3.11).

Before I didn't use the latest documentation (which also has this notice, but it's not emphasized, so I had missed it).
I suppose I could close this as invalid, but I'd also say is only available for CSI Trident should instead be is only supported.  It does (more or less) work with pre-CSI Trident as we can see from this bug report.

Thanks for the clarification, @scaleoutsean. Closing this issue for the additional reason of OCP 3.11 and pre-CSI Kubernetes version support ended with the Trident 21.04 release. Expect an updated support statement for Trident 21.07.0.


Error when importing the library oraclizeAPI.sol

Hello, if anyone can help me out on this error when importing oraclizeAPI , very much appreciated!
the Remix version :Current version:0.4.19-nightly.2017.11.30+commit.f5a2508e.Emscripten.clang
pragma solidity ^0.4.19;
import "github.com/oraclize/ethereum-api/oraclizeAPI.sol";
Error: github.com/oraclize/ethereum-api/oraclizeAPI.sol:39:53: ParserError: Expected token Comma got 'Identifier'
function query(uint _timestamp, string calldata _datasource, string calldata _arg) external payable returns (bytes32 _id);
^

Hello,
The current oraclizeAPI.sol now targets solc 0.5, and that is why you are getting that error.
We still do support 0.4.x solc, but you will need to explicitly import one of those versions now. Seeing your pragma, you should use oraclizeAPI_0.4.sol. What this entails is replacing your current import statement from:
import "github.com/oraclize/ethereum-api/oraclizeAPI.sol";
to
`import "github.com/oraclize/ethereum-api/oraclizeAPI_0.4.sol";
Or use the 0.4.25 version if targetting 0.4.22 solc or above (as per the API mentions).
Tomorrow, we'll see to add a 0.4.18 targetted version as well, which would seem to fit your pragma best.

the api has been updated to give a more clear indicator of why the error is happening, mentioning incompatible solc now, since https://github.com/oraclize/ethereum-api/commit/37ed083a2f795dcf3f7f5c89206937a61902ffe6 and telling user to import 0.4 instead.


Move blocks in diff view

It would be handy to be able to move blocks of code in diff view around like for example in WinMerge with Alt+LeftArrow/RightArrow or with some sort of arrows in the splitter of the diff view

Does Git: Revert Selected Ranges help any here?

Unfortunately not because I regularly diff config files from two machines and would like to copy blocks from one side to the other like I can do in WinMerge or in other visual diff tools like Meld

https://github.com/microsoft/vscode/issues/25887


Unable to get Fabric Network with TLS Chain of Trust of multiple Fabric CA Servers working!

Hi everybody ;)
I'm stuck! Lately I'm trying to get a Hyperledger Fabric Network with multiple Fabric-CA's building a Chain Of Trust running. I read the Docs, checked out multiple Blog Posts about this topic, tried out various of different kinds of approaches... But I just can't get my Network up and running!
The relevant part of the network looks something like this

The startup of the whole CA-Hierarchy is already working. And without the ca-root and ca-intermediate though, I managed to get it all running without any problems.
The error most probably lies in the Overall Generation of the TLS-Certificates or the Usage of them in the peers & orderers.
The error that I can't get rid off happens in all peers & orderers when starting them:
peer1
/etc/hyperledger/fabric/core.yaml: OK
patching file /etc/hyperledger/fabric/core.yaml
patch unexpectedly ends in middle of line
Hunk #1 succeeded at 546 with fuzz 1.
Running: peer node start
2021-11-17 14:28:33.081 CET [main] InitCmd -> ERRO 001 Cannot run peer because error when setting up MSP of type bccsp from directory /etc/hyperledger/crypto/peer/msp: the supplied identity is not valid: x509: certificate signed by unknown authority
orderer1
2021-11-17 14:33:27.672 CET [orderer.common.server] loadLocalMSP -> PANI 004 Failed to setup local msp with config: the supplied identity is not valid: x509: certificate signed by unknown authority
panic: Failed to setup local msp with config: the supplied identity is not valid: x509: certificate signed by unknown authority
Files
The project in the state described above with all the files (including Startup-Script, Config-Files, generated certificates in their MSP Structure) are to be inspected in the following repository:
Fabric Network Project
When you want the project to run in your kubernetes namespace, you have to delete the /artifacts/crypto-config folder and then run the ./start.sh script.
I would be very pleased if someone could tell me what I have to change in my Script and Configs to get this thing working!

Please reserve github issues for Fabric code issues.
For getting help, see the community help resources mentioned at:
https://hyperledger-fabric.readthedocs.io/en/latest/CONTRIBUTING.html#getting-help

@aaronbeer81 Have you found the solution?


No error just a question

Can we connect to dual.agar.online?? with private server

Nope
@Megabyte918 close


bad permission

Hi :)
I use multiverse signs to TP between 2 world http://dev.bukkit.org/bukkit-plugins/multiverse-signportals/
It works for pour /op persons but not for others
What is the permission ??
I search but I only find to create or validate :https://github.com/Multiverse/Multiverse-SignPortals/wiki/Big-list-o-permissions
Thanks a lot for your help !

This issue either does not have enough details, or details have been requested and not provided. Please read up on "submitting a bug" and form a more complete bug report.
Please make sure to include steps to reproduce your problem, since I don't fully understand the question.


Reopening packet loss on ping_only tests from issues 732 and 736

This is a follow-up to issues 732 and 736 - https://github.com/kentik/ktranslate/issues/736
There was still packetloss recorded on the initial polling but the bigger issue in the latest version released was some of the devices did not get polled for a lengthly time period as in below example.   The poller was started up at 3pm but it seems this specific host got polled in the beginning and then no more polls on it until like 5:15pm timeframe.  So a >2 hour gap.  There were other hosts having the same type of behavior as well.

Uh oh! Let me try with a new ping engine and see if that's any better.

OK, if you're up for it, try one more time and let me know if this one is better. Latest fix building now.

Thanks.  Checking it out now via version kt-2024-08-27-10571748813

@i3149 - looks like the new version is working as expected and not recording any false packet loss.  Old version  was giving pretty static results all the time.  This version seems to be recording variable response times on the pings which probably is more reflective of real world results?  What do you think of the results?


GraphQL Aggregate throws error (Bug?)

See screenshot for details, some notes:

This is using the deployed demo dataset at https://demo.dataset.playground.semi.technology. As of now it is unknown if this error is specific to something in there or a general issue
The error goes away if the HasArticles { type } is removed
It could be related to deleted references (Quoting @laura-ham "I think this happens if there’s a Publication pointing to Article , but the beacon of the Article is removed / doesn’t exist anymore")

Possibly related? (Same demo dataset):


Adding configuration path to Configuration Binder's error message

Is your feature request related to a problem? Please describe.
When we face binding error in Microsoft.Extensions.Configuration.Binders, we can only receive what error was, cannot receive where error occurred. This is cumbersome to find the invalid configuration value especially for large configuration. It is better that binding error messages contain configuration path information in their exception messages.
Example: Cannot create instance of type 'Microsoft.Extensions.Configuration.Binder.Test.ConfigurationBinderTests+ISomeInterface' because it is either abstract or an interface. Path: 'NestedOptionsProperty:NestedOptions2Property:ISomeInterfaceProperty'.
Describe the solution you'd like

Every exceptions in ConfigurationBinder class contain configuration path.

I believe that there are no public API changes needed.

When ConfigurationBinder is invoked with IConfigurationSection, it can use its Path property to build "full" path of the error location. In contrast, if received IConfiguration is not IConfigurationSection, it cannot report actual "full" path of the error location. I think it is not so critical because IConfiguration is IConfigurationRoot in many cases.

Describe alternatives you've considered

Tracing. It is hard because enabling tracing requires some logging mechanism, but it should depend on configuration layer. System.Diagnostics.Debug cannot be used in Release build. System.Diagnostics.Trace introduces extra dependency and it is not so good for it.
It is better to report configuration source related information for debugging, but this idea requires wide modification including IConfiguration and related interfaces.

Additional context

I think it is also useful for ASP.NET 2.1 (LTS) users.

Closing in favor of #609


fflib_SObjectMocks.SObjectUnitOfWork: Class must implement the public interface method

Trying to deply Apex Common right after having deployed ApexMocks and got this error :
Failures:
classes/fflib_SObjectMocks.cls(45,23):f: void registerDirty(SObject, Schema.SObjectField, SObject) from fflib_ISObjectUnitOfWork
classes/fflib_ApplicationTest.cls(84,41):Dependent class is invalid and needs recompilation:
fflib_SObjectMocks: line 45, column 23: fflib_SObjectMocks.SObjectUnitOfWork: Class must implement the public interface method: void registerDirty(SObject, Schema.SObjectField, SObject) from fflib_ISObjectUnitOfWork

Was just about to report the same thing. I receive the same error when attempting to deploy. It appears to be an issue related to the following commit.

@putskiz, for a quick workaround, you can download the following version of the repository, from before the offending commit, and deploy using the force.com migration tool. Just deployed successfully for me.

Working on this fix, will also get Travis setup on this repo! ;-)

This has been fixed.


When I used mythril's docker image to scan the specified contract address, an error occurred

When I execute the following command in macOS, it shows this error message
Command Line: docker run mythril/myth analyze -a 0xdac17f958d2ee523a2206206994597c13d831ec7
mythril.interfaces.cli [ERROR]: IPC / RPC error: 'NoneType' object has no attribute 'eth_getCode'
docker run mythril/myth version
Mythril version v0.22.19

Hi, to access any data onchain, you need infura-id, which you can get from https://infura.io/ . You can use the arg --infura-id <ID> to pass the ID as cmd line argument.


FOR-36

Adjust survey container size.
Update typography.
Scope tailwindcss to formily-container.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Result<T, E>::and_then not working as expected

The following code works when using std::expected, but errors with sus::Result.
static auto set_attrib_pointer(vertex_array array) -> sus::Result<vertex_array, error>
{
	if constexpr (is_coloured_position<T>) {
		return set_attrib_pointer<decltype(T::position)>(std::move(array), 0, 0).and_then(test);
	}
	else {
		return set_attrib_pointer(array, 0, 0);
	}
}

template<class U>
static auto set_attrib_pointer(vertex_array array, GLuint const location_offset, GLuint const offset_by) -> sus::Result<vertex_array, error>;

FAILED: source/shaders/CMakeFiles/shaders.dir/shaders.cpp.o
/home/cjdb/opt/bin/clang++ --target=x86_64-unknown-linux-gnu  -isystem /home/cjdb/projects/learnopengl/build/vcpkg_installed/vcpkg_toolchain_file/include -isystem /home/cjdb/projects/learnopengl/build/vcpkg_installed/vcpkg_toolchain_file/include/sus -fdiagnostics-color=always -fstack-protector-strong -fvisibility=hidden -fno-rtti -Werror -pedantic -Wall -Wattributes -Wcast-align -Wconversion -Wdouble-promotion -Wextra -Wformat=2 -Wnon-virtual-dtor -Wnull-dereference -Wodr -Wold-style-cast -Woverloaded-virtual -Wshadow -Wsign-conversion -Wsign-promo -Wunused -Wno-ignored-attributes -Wno-unused-command-line-argument -stdlib=libc++ -D_LIBCPP_HARDENING_MODE=_LIBCPP_HARDENING_MODE_FAST -fsanitize=address -g -std=gnu++23 -fno-rtti -Wno-nullability-completeness -MD -MT source/shaders/CMakeFiles/shaders.dir/shaders.cpp.o -MF source/shaders/CMakeFiles/shaders.dir/shaders.cpp.o.d @source/shaders/CMakeFiles/shaders.dir/shaders.cpp.o.modmap -o source/shaders/CMakeFiles/shaders.dir/shaders.cpp.o -c /home/cjdb/projects/learnopengl/source/shaders/shaders.cpp
In file included from /home/cjdb/projects/learnopengl/source/shaders/shaders.cpp:9:
/home/cjdb/projects/learnopengl/build/vcpkg_installed/vcpkg_toolchain_file/include/sus/result/result.h:430:23: error: constraints not satisfied for alias template 'ReturnOnce' [with F = (lambda at /home/cjdb/projects/learnopengl/source/lib/buffers.cpp:235:87), Args = <>]
  430 |       return sus::fn::ReturnOnce<AndFn>::with_err(storage_.take_err());
      |                       ^~~~~~~~~~~~~~~~~
/home/cjdb/projects/learnopengl/source/lib/buffers.cpp:235:78: note: in instantiation of function template specialization 'sus::result::Result<buffers::vertex_array<buffers::buffer_type::array, buffers::coloured_position<3>>, buffers::error>::and_then<(lambda at /home/cjdb/projects/learnopengl/source/lib/buffers.cpp:235:87)>' requested here
  235 |                                 return set_attrib_pointer<decltype(T::position)>(std::move(array), 0, 0).and_then([](vertex_array array) {
      |                                                                                ^
/home/cjdb/projects/learnopengl/source/lib/buffers.cpp:186:11: note: in instantiation of member function 'buffers::vertex_array<buffers::buffer_type::array, buffers::coloured_position<3>>::set_attrib_pointer' requested here
  186 |                         return set_attrib_pointer(vertex_array{id, b});
      |                                ^
/home/cjdb/projects/learnopengl/source/shaders/shaders.cpp:97:71: note: in instantiation of member function 'buffers::vertex_array<buffers::buffer_type::array, buffers::coloured_position<3>>::make' requested here
   97 |         auto access = buffers::array_accessor<buffers::coloured_position3d>::make(points).unwrap_or_else(
      |                                                                              ^
/home/cjdb/projects/learnopengl/build/vcpkg_installed/vcpkg_toolchain_file/include/sus/fn/fn_concepts.h:469:12: note: because 'FnOnce<(lambda at /home/cjdb/projects/learnopengl/source/lib/buffers.cpp:235:87), Anything ()>' evaluated to false
  469 |   requires(FnOnce<F, Anything(Args...)>)
      |            ^
/home/cjdb/projects/learnopengl/build/vcpkg_installed/vcpkg_toolchain_file/include/sus/fn/fn_concepts.h:173:8: note: because type constraint '__private::ValidReturnType<sus::fn::__private::NoOverloadMatchesArguments, typename __private::Sig<Anything ()>::Return>' was not satisfied:
  173 |   } -> __private::ValidReturnType<typename __private::Sig<S...>::Return>;
      |        ^
/home/cjdb/projects/learnopengl/build/vcpkg_installed/vcpkg_toolchain_file/include/sus/fn/__private/signature.h:126:5: note: because '!std::same_as<sus::fn::__private::NoOverloadMatchesArguments, NoOverloadMatchesArguments>' evaluated to false
  126 |     !std::same_as<ReturnType, NoOverloadMatchesArguments> &&
      |     ^
1 error generated.

I don't see any tests for Result::and_then; should I switch back to std::expected for the time being?

What's the type of test?
In case it's not clear, the !std::same_as<ReturnType, NoOverloadMatchesArguments> is saying what the text says, that the arguments are not binding to a callable signature. Maybe it's not testing convertible somewhere.
Result is not as 100%'d as Option is: https://github.com/chromium/subspace/issues/185 is the bug for completing the API to match https://doc.rust-lang.org/stable/std/result/enum.Result.html and provide tests for everything. It was enough for me to make use of it in Subdoc and the rest of the sus library so far, basically.
If you're up for fixing it, I'd be happy to review it, or I can try get to fixing this. I don't like leaving something broken in here.


Run tests against coreclr on darwin/linux

Fix #124

:shipit: You should file an issue on Universe for this too.


Random cars in random races repeating.

Is it possible to make random races that if you get a Asterope for exmaple, you cant get it again in the same race? Thanks!

Basically you shouldnt get the same car in one race twice

I didn't make the restriction that you would have a different vehicle every lap.  If that was the case, for example in an 8 lap race, you would need at least 8 different vehicles in the vehicle list.  I made it so each vehicle in the list had an equal chance of being selected each lap.  If you had an 8 lap race and only 3 vehicles in the list, you would be in the same vehicle on some of the laps.  I'm not inclined to add that restriction.  It makes things a bit more complicated.

h

ah man, the script is so great though, using it alot. Its the only request/wish i have basically. There is basically no other random racing script. I also added alot of addon cars and i have like over 700 vehicles in the last and in 20 laps still sometimes me or my friends get the same vehicle 2 or even 3 times. I wish you did that but if it makes stuff complicated then i guess i have to live with that! Thanks for the response!

I'll think about / experiment making it an option for random races depending on the complexity.

i greatly appreciate that you will at least think about that !

You can also update me on this here about progress, forgot to mention!

@emtneutrino are you completly dont with this script or plan to add new features?

I am planning to add the option for vehicles not to repeat appearing in later laps for random vehicle races.  I will also try to add an option where everyone uses the same random vehicle for each lap in random vehicle races (e.g. 1st lap everyone uses adder, 2nd lap everyone uses elegy, etc.)  I just haven't gotten around to finding the time to do this.  I've already done some unrelated clean up to the code.  I can't guarantee when I'll be able to get around to doing all of this though, but I am planning to work on it.

okay nice thanks for the update

Like cant you make a database that tracks what cars a player has gotten so that player doesnt get that car again ? Or is that too complicated?

Or make that every player has a predetermined pool of cars before race starts. Like creates random cars for every racer so they are predetermined. Every player has their own list basically that they get during the race

The "recur" parameter value may be 'yes' or 'no'.  If it is 'yes', then vehicles that appeared in previous laps may be used in later laps.  If it is 'no', then vehicles that appeared in previous laps will not be used in later laps.  If you specify 'no', then the number of vehicles in the vehicle list must be at least one less than the number of laps in the race.  If there are multiple vehicles of the same model in the vehicle list, it may be used as many times as it appears in the vehicle list.  If you don't want the same model to appear multiple times, then make sure only one vehicle of that model is in the vehicle list.  The default behavior is that vehicles that appeared in previous laps may be used in later laps.


The correct address is judged as an invalid address through TronWeb.isAdderss

install from npm
Version: 5.3.2
code:
TronWeb.isAddress('TF9yaMo6m6V22HyLXCvcQvN4iEdRbQWrbW')
// false

Did you provide polyfill for buffer and crypto ? Tronweb depend on these modules to work.


Magnet Puzzle -standard backtracking Algorithm.

Issue will be closed if:

You mention more than one algorithm. You can create a separate issue for each algorithm once the current one is completed.
You propose an algorithm that is already present or has been mentioned in a previous issue.
You create a new issue without completing your previous issue.

Note: These actions will be taken seriously. Failure to follow the guidelines may result in the immediate closure of your issue.

Name:
Magnet Puzzle
About:
It is a type of combinatorial puzzle that can be solved using backtracking algorithms. This problem typically involves placing magnets (represented as poles) on a grid, adhering to specific rules and constraints.

Labels:
new algorithm, gssoc-ext, hacktoberfest, level1

Assignees:

[ ] Contributor in GSSoC-ext
[ ] Want to work on it

@pankaj-bind   "I would love the opportunity to contribute and work on this project.
Could you please assign the issue to me? I'm eager to dive in and make a meaningful impact. Thank you for considering my request!"


feat(helm): add in ability to inject init containers in to deployment from values

Hold off. spotted one problem

Resolved. Was outputting volumes yaml in volumeMounts block :)


Implement diff command

Implement diff command to show variable differences between Terraform Cloud and local environment.

solved in #51


Handle WMTS layers

Although WMTS is listed as a layer type when creating a layer, the code is not in place to handle that.

Code has been added to support WMTS layers. Key to note here is that the layer will look for a number of parameters in the 'Layer Parameters' section of the layer definition, including 'layer', 'tileSize', 'subdomains', and any other variables defined in the url. Current geo-q.com has a 'Landsat Precipitation day' layer defined as an example


Minimum text length violated despite preprocessing

What is the tokenizer used to calculate the minimum lengths during the preprocessing involved in training? As I understand from looking at the code, it should be either the Tokenizer for the given pretrained model or the SpacyTokenizer. Yet, I have pared down my dataset to only include texts whose length exceeds my needed minimum length according to both of these tokenizers, but still run into the following error:
ValueError: len(tokenizer(text)) should be at least 24 (num_anchors * max_span_len * 2), got 23
I don't believe there to be any issues in the code used when I slim my dataset down, but I am possibly missing a different tokenizer that is used when preprocessing the dataset.

This check uses the tokenizer passed to dataset_reader.py IF it is a PretrainedTransformerTokenizer. Otherwise is uses .split().
Did you use the same tokenizer to filter your dataset as the tokenizer you passed to dataset_reader.py?

Hi, I have a similar issue: I get ValueError: len(tokenizer(text)) should be at least <number here> (num_anchors * max_span_len * 2), got 0
I have filtered my input data to have both minimum length beyond parameter min_length and greater than 0, of course! I also tried to print out the text to be tokenized, it was empty!? How can that be?
I use a pretrained model from Sentence Transformers, sentence-transformers/paraphrase-multilingual-mpnet-base-v2, so the tokenizer comes from that model - do you have any idea, why the text is empty?


Release link not accessible in README

It seems that the releases were not forked since no releases are available in the repository.
The 'release' link that is mentionned in the README does not work.

Handled by #101


[ Model ] Fix incremental output in FP32

This PR fixes the output of incremental inference.
Resolves:
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2344. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @jijoongmoon, api/ccapi/include/model.h does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2344-202310201618410.32757496833801-1669bd0a92379c0c64184ec7c1046763ad0f60cf/.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2344-202310202052080.65451598167419-4b8d9cc21abeb04e672ca6523422ebfb2ebff9ea/.


Firebase/MLVision uses deprecated UIWebView APIs

Frameworks FirebaseMLCommon (0.17.0) and GoogleMobileVision (1.6.0) (dependencies of Firebase/MLVision (6.7.0)) use deprecated UIWebView APIs, which trigger App Store Connect issue during deployment:

ITMS-90809: Deprecated API Usage - Apple will stop accepting submissions of apps that use UIWebView APIs . See https://developer.apple.com/documentation/uikit/uiwebview for more information.

We won't be able to ship apps with Firebase MLVision to App Store soon, please fix.

Filed internally at b/140396933

@paulb777 There is same issue with Crashlytics (3.13.4) - also uses UIWebView APIs.

b/140424496 for Crashlytics. Thanks @machl

Closing in favor of https://github.com/firebase/firebase-ios-sdk/issues/3780


add bgyp colormap

This is designed to be a correlation coefficient colormap that is more accessible than plasmidis (#24) as it does not contain a lightness reversal and therefore is easier to differentiate high correlation from low correlation areas. It also works better for black and white printing for this reason.
However, it compromises on familiarity (both NWS and plasmidis have a lightness reversal at 0.9 to 0.95 ish). This might be too much of a problem to make it 'not worth it'. I do not have any sort of color vision deficiency, but personally think that bgyp is subjectively ugly (and would vote against it's inclusion if there's a better option, which might already exist in the form of NWS_CC or plasmidis).
So this PR is a bit of grudgingly opened suggestion. Colormaps aren't supposed to be an art competition, and if it helps those with CVD, then it should definitely be included, but I'm marking this as a draft because I want to know that before 'officially' suggesting that this be included.

@wx4stg I think even if this isn't by any means the best colormap for highlighting etc, but if its still CVD friendly and a user can find use in it, I'm for adding it in.


Geometry vs Geography?

Thx for your great extension. I just used it to make some migrations and seeding some data to it.
I just ran into an issue where some stuff from the backend wont work and i then realized thats because of  the geom field (multipolygon) which was generated through the migrations wasnt a geometry field. instead an geography field was made.
Meanwhile i convert the geom field to a geometry in my queries cause of the need of some postgis functions.
So my question here is, how to generate geometry fields for my migration? or am i missing something here?
thx a lot though

Hi,
sorry for the late reply, I've avoided work during xmas :)
Currently geometry fields aren't well supported.
I really created this for my own geography needs in a project.
I would love to support geometries though, but currently I don't have time to write new features.
If you want to make a pull request, that would be great.
A few pointers:
To allow geometry fields to be created via migrations, you'll need to add support in these two files:
https://github.com/phaza/laravel-postgis/blob/master/src/Schema/Blueprint.php
https://github.com/phaza/laravel-postgis/blob/master/src/Schema/Grammars/PostgisGrammar.php
maybe add function names like geomPoint and geogPoint. Don't forget to keep backwards compatibility.
To support geometries in models, you'll have to do changes in the files in this folder:
https://github.com/phaza/laravel-postgis/tree/master/src/Eloquent
My suggestion in that $postgisFields is used as an associative array where you declare whether an attribute is geometry or geography:
protected $postgisFields = ['location' => Geography::class, 'area' => Geometry::class];

Then you can do some switching between ST_GeogFromText and ST_GeomFromText based on that.

Hi @phaza and @magnolo ,
I have the same issue. Have either of you made any progress on this? I also need to use a different SRID.
How about doing something like this in the Blueprint.php (rather like when you specify an integer field in a migration):
/**
* Add a point column on the table
*
* @param      $column
* @return \Illuminate\Support\Fluent
*/
public function point($column, $geomtype = 'GEOGRAPHY', $srid = '4326')
{
return $this->addColumn('point', $column, compact('geomtype', 'srid'));
}
Thoughts?
Steve

I actually started out like this with srid, but postgis only supports srid
4326 for geographies:
http://postgis.net/docs/manual-1.5/ch04.html#PostGIS_Geography
On Thu, 14 Jan 2016 at 13:10 Steve Goddard<EMAIL_ADDRESS>wrote:

Hi @phaza https://github.com/phaza and @magnolo
https://github.com/magnolo ,
I have the same issue. Have either of you made any progress on this? I
also need to use a different SRID.
How about doing something like this in the Blueprint.php (rather like when
you specify an integer field in a migration):
/**

Add a point column on the table

@param https://github.com/param $column
@return https://github.com/return \Illuminate\Support\Fluent
*/
public function point($column, $geomtype = 'GEOGRAPHY', $srid = '4326')
{
return $this->addColumn('point', $column, compact('geomtype', 'srid'));
}

Thoughts?
Steve
—
Reply to this email directly or view it on GitHub
https://github.com/phaza/laravel-postgis/issues/27#issuecomment-171628321
.

Yes @phaza - I discovered this yesterday! Surely we can trust the users to realise this (or the migration will simply fail. If users want GEOGRAPHY then they can leave the 2 extra parameters blank.

The PostGISGrammer.php file would be something like this:
/**
 * Adds a statement to add a point geometry column
 *
 * @param \Illuminate\Support\Fluent $column
 * @return string
 */
public function typePoint(Fluent $column)
{
    // return 'GEOGRAPHY(POINT, 4326)';
    return dd(strtoupper($column->geomtype) . '(POINT, ' . $column->srid . ')');
}

What do you think @phaza - would you be happy with something like this? I wondered if we should put some validation into the grammer file to check for srid = integer and check if the geomtype is = to either GEOMETRY or GEOGRAPHY??
Steve

Ok - this seems to be working well:
private $allowed_geom_types = ['GEOMETRY', 'GEOGRAPHY'];

/**
 * Adds a statement to add a point geometry column
 *
 * @param \Illuminate\Support\Fluent $column
 * @return string
 */
public function typePoint(Fluent $column)
{
    // return 'GEOGRAPHY(POINT, 4326)';
    if ((in_array(strtoupper($column->geomtype), $this->allowed_geom_types)) && (is_int($column->srid))) {
        return strtoupper($column->geomtype) . '(POINT, ' . $column->srid . ')';
    } else {
        return dd('Error with validation of geom type or srid! (If geom type is GEOGRAPHY then the SRID must be 4326)');
    }
}

I'll update the rest of the geom types. If you're ok with it i'll fork and put in a pull request.
Need to have a look at the models now - I think it best to do that as a separate pull request?
Steve

Perhaps make GEOMETRY and GEOGRAPHY into const variables, to remove the
possibility of spelling errors.
If you make a PR and don't break backwards compatibility, I'll merge it.
On Thu, 14 Jan 2016 at 13:42 Steve Goddard<EMAIL_ADDRESS>wrote:

Ok - this seems to be working well:
private $allowed_geom_types = ['GEOMETRY', 'GEOGRAPHY'];
/**

Adds a statement to add a point geometry column

@param \Illuminate\Support\Fluent $column
@return string
*/
public function typePoint(Fluent $column)
{
// return 'GEOGRAPHY(POINT, 4326)';
if ((in_array(strtoupper($column->geomtype), $this->allowed_geom_types)) && (is_int($column->srid))) {
return strtoupper($column->geomtype) . '(POINT, ' . $column->srid . ')';
} else {
return dd('Error with validation of geom type or srid! (If geom type is GEOGRAPHY then the SRID must be 4326)');
}
}

I'll update the rest of the geom types. If you're ok with it i'll fork and
put in a pull request.
Need to have a look at the models now - I think it best to do that as a
separate pull request?
Steve
—
Reply to this email directly or view it on GitHub
https://github.com/phaza/laravel-postgis/issues/27#issuecomment-171633940
.

The geometry type has a much richer set of functions than geography, relationship checks are generally faster, and it has wider support currently across desktop and web-mapping tools.

http://gis.stackexchange.com/questions/26082/what-is-the-difference-between-geometric-and-geographic-columns
To insert a point in geomitry format:
\DB::statement("INSERT INTO points (latlong)
            VALUES(
            ST_SetSRID(ST_MakePoint($latitude, $longitude), 4326)
            );");

The migration:

DB::statement(DB::raw("ALTER TABLE \"".env('DB_SCHEMA', '')."\".\"points\" ADD COLUMN \"latlong\" geometry;"));


Matlab warnings when running BirthDeath example

>> generateLNA('BirthDeath/BirthDeath.xml', 'BirthDeath', 'BOTH');
Warning: Support of character vectors will be removed in a future release. Character vectors can be used only for variable names and numbers.
Instead, to create symbolic expressions first create symbolic variables using 'syms'. To evaluate character vectors and strings representing
symbolic expressions, use 'str2sym'.
> In sym>convertExpression (line 1581)
  In sym>convertChar (line 1486)
  In sym>tomupad (line 1236)
  In sym (line 215)
  In cell2sym (line 31)
  In SBML2StoichProp (line 59)
  In generateLNA (line 14)
[... many more as above ... ]
> In sym>convertExpression (line 1581)
  In sym>convertChar (line 1486)
  In sym>tomupad (line 1236)
  In sym (line 215)
  In sym/subs>@(x)sym(x) (line 206)
  In sym/subs>normalize (line 206)
  In sym/subs>mupadsubs (line 154)
  In sym/subs (line 142)
  In SBML2StoichProp (line 65)
  In generateLNA (line 14)
Warning: Function 'Theta' not verified to be a valid MATLAB function.
Warning: Function 'phi' not verified to be a valid MATLAB function.
Computing symbolic derivatives
Warning: Solutions are valid under the following conditions: in((k_m*k_p^2 + g_m*k_p^2*phi01 + g_m^2*k_p*phi01 + g_m*g_p^2*phi02 +
g_m^2*g_p*phi02 + g_m*g_p*k_p*phi01)/(g_m*g_p*(g_m + g_p)), 'real') & in((k_p*(k_m + g_m*phi01))/(g_m*(g_m + g_p)), 'real') & in((k_m +
g_m*phi01)/g_m, 'real'). To include parameters and conditions in the solution, specify the 'ReturnConditions' value as 'true'.
> In solve>warnIfParams (line 508)
  In solve (line 357)
  In generateLNAComponents>solveSS_var (line 377)
  In generateLNAComponents (line 109)
  In generateLNA (line 25)
computing initial sensitivities

Warning: Support of character vectors will be removed in a future release. Character vectors can be used only for variable names and numbers.
Instead, to create symbolic expressions first create symbolic variables using 'syms'. To evaluate character vectors and strings representing
symbolic expressions, use 'str2sym'.

Should follow that advice at some point, but would break pre-2017B compatibility now.


log-factory compositelog is missing in QuickFixJClientConfiguration

In the README, log-factory has value of compositelog But it's not configured in QuickFixJClientConfiguration

Thanks for reporting, I'll take a look and add the missing factory

The problem with compositeLog is that it requires an array of LogFactorys. At the moment it's possible to configure a log factory like this:
quickfixj.server.log-factory=screen

Maybe for compositeLog we could have something like this:
quickfixj.server.log-factory=composite
quickfixj.server.log-factory.composite.log-factories[0]=screen
quickfixj.server.log-factory.composite.log-factories[1]=file

and make the List<LogFactory> bean created as part of this compositeLog bean accessible too. I'll give this a go and see if it's possible, let me know if you have any other thoughts on this

This looks good. Or set the properties like quickfixj.server.log-factory.composite.log-factories=screen, file ? Whichever is approachable.

Hey @wtiann
I'd like to discuss this feature as I've started implementing it and a few questions were raised.
CompositeLogFactory takes an array of LogFactorys as the only argument in the constructor. The idea as described in the documentation is Allows multiple log factories to be used with QuickFIX/J. For example, you could log events to the console and also log all events and messages to a file.
The other available LogFactorys take a SessionSettings as an argument, but in theory, these settings could come from the same config file or from other config files. For example:
quickfixj.server.log-factory=composite
quickfixj.server.log-factory.composite.log-factories[0].type=screen
quickfixj.server.log-factory.composite.log-factories[0].config=classpath:quickfixj-server.cfg
quickfixj.server.log-factory.composite.log-factories[1].type=file
quickfixj.server.log-factory.composite.log-factories[1].config=classpath:quickfixj-server-extra.cfg
quickfixj.server.log-factory.composite.log-factories[2].type=screen
quickfixj.server.log-factory.composite.log-factories[2].config=classpath:quickfixj-server-screen.cfg

The alternative is to delegate the creation of the LogFactorys to the developer and just define the composite log factory as this:
@Configuration(proxyBeanMethods = false)
@ConditionalOnMissingBean(name = "clientLogFactory")
@ConditionalOnProperty(prefix = "quickfixj.client", name = "log-factory", havingValue = "composite")
static class CompositeLogFactoryConfiguration {

	@Bean
	public LogFactory clientLogFactory(List<LogFactory> compositeLogFactories) {
		return new CompositeLogFactory(compositeLogFactories.toArray(new LogFactory[0]));
	}
}

The third option is to assume the same SessionSettings will apply to all LogFactorys but the developer will be able to define further factories if needed as they will be injected in the list of factories.

Hi @esanchezros ,
Maybe we can have a mix of options 2 and 3? By default, it has SessionSetting in all LogFatroy. And developer will define a new one if they need.

Fixed on 2.16.0
I went with allowing the developer to define any LogFactory in their Spring context. For example:
quickfixj.client.log-factory=compositelog
and
	@Configuration
	@EnableQuickFixJClient
	@PropertySource("classpath:client-log-factory/client-composite-log-factory.properties")
	static class ClientCompositeLogFactoryConfiguration {

		@Bean
		public LogFactory screenLogFactory(SessionSettings clientSessionSettings) {
			return new ScreenLogFactory(clientSessionSettings);
		}

		@Bean
		public LogFactory slf4jLogFactory(SessionSettings clientSessionSettings) {
			return new SLF4JLogFactory(clientSessionSettings);
		}
	}


Feature/rmudambi/implement hh details

Integrate Address Refactor

Description

Category: refactor
JIRA issue: MIC-3780
Research reference:

Changes and notes
Integrate business and household address refactor into simulation
Fix failing tests
Prevent simulants from moving into empty households
Verification and Testing
Tests pass (both unit and integration) and new tests written

@rmudambi Since there are observer changes in this PR, which don't get hit by integration tests, you'll want to run the simulation all the way through with these changes (if you haven't already), to ensure the observers run without error.


docs: Fix KJ style guide & tour links in jsg readme

These are simply pointing to non-existent resources at the moment.

Thanks!