Can't control name mangling

Forgive me if I've missed this in the docs somewhere.
I'm trying to control the name mangling on extern function definitions. I'm trying to generate pinvoke code for part of the Win API. I tried:
public void Setup(Driver driver)
{
    var options = driver.Options;
    options.LanguageVersion = CppSharp.Parser.LanguageVersion.C;
}

But this instead just causes a crash with:
error: invalid argument '-std=gnu99' not allowed with 'C++/ObjC++'
Unhandled type class 'FunctionNoProto'

Unhandled Exception: System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at CppSharp.CppParser.ClangParser.ParseHeader(ParserOptions* )
   at CppSharp.Parser.ClangParser.ParseHeader(ParserOptions Opts) in c:\projects\cppsharp\src\cppparser\bindings\cli\cppparser.cpp:line 531
   at CppSharp.ClangParser.ParseSourceFile(SourceFile file) in C:\projects\cppsharp\src\Core\Parser\Parser.cs:line 59
   at CppSharp.ClangParser.<ParseProject>b__10_0(SourceFile s) in C:\projects\cppsharp\src\Core\Parser\Parser.cs:line 73
   at System.Linq.Enumerable.WhereSelectListIterator`2.MoveNext()
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at CppSharp.ClangParser.ParseProject(Project project) in C:\projects\cppsharp\src\Core\Parser\Parser.cs:line 73
   at CppSharp.Driver.ParseCode() in C:\projects\cppsharp\src\Generator\Driver.cs:line 205
   at CppSharp.ConsoleDriver.Run(ILibrary library) in C:\projects\cppsharp\src\Generator\Driver.cs:line 475

I'm assuming I am handling this incorrectly. The libraries I'm trying to generate code for only have exported C functions (obviously no mangling) but no matter what I do, or what I override using my own TranslationUnitPass, I cannot modify this successfully. I always get mangled names in the DllImportAttribute::EntryPoint member. So I guess this is two questions:

Is this the correct way to do this, making this a bug?
Where/how can I override generation of attributes such as DllImportAttribute?

Thanks in advance and thanks for publishing this tool its brilliant.

LanguageVersion.C is used to tell the compiler to parse the code in C mode, but given the error you posted, error: invalid argument '-std=gnu99' not allowed with 'C++/ObjC++' it looks like your sources are C++ files (and named .cpp, is that the case?). If your sources are C files (named .c) then we might have a bug.
If I understood correctly, the issue is that you want the name mangling of certain functions to be in plain C. If your sources are C++, that is usually done by wrapping those functions in an extern "C" {} block.
About DllImport, it is handled in https://github.com/mono/CppSharp/blob/11fc1f5097f14e5ca50bebf333a46c7c6bf4c30e/src/Generator/Generators/CSharp/CSharpTextTemplate.cs#L3004. We have no easy way of overriding, why do you need it?

Perhaps I'm using this tool beyond its intended scope. I'm only supplying headers, and they're definitely C headers. With regard to overriding the attribute, it's because the functions I'm pinvoking against are C exports, no mangling, so the ::EntryPoint definitions generated on all the extern definitions are incorrect. It's not a big deal though, I can write a regex in notepad++ to demangle manually. Everything else is great. :)

Well if the headers are C code, then CppSharp should work out of the box. There should be no need to manually change the generated output, I consider that a bug.
Can you share the input code that gives out the exception above in C language mode?

Input code? I created a basic example wrapping some of the headers for the Windows Filtering Platform and it's treating it all as C++. Nothing more than what the walkthrough tutorial code shows.

Pushed a fix for the error, turns out to be a pretty silly issue.

Haha that's usually the way it is isn't it? Thanks man, AAA support for any product, especially a free one. :)

That only fixes the first issue though, looks like there's another one dealing with FunctionNoProto types, which will also need a fix.


Add initial version of summarization metric

This PR adds an initial version of a metric for summarization use cases.
Description
For evaluating summaries generated by LLMs, we need a metric to consider overall informativeness and conciseness of the summary. This metric has been formulated to do the same.
Formulation
To determine if a summary is a good one or not, it is essential that it contains all important information that is present in the original text. We begin with generating n number of 'yes'/'no' questions, for which the original text strictly has the answer yes.
We then ask those questions to the generated summary, and compute the qa_score as the fraction of correctly answered questions.
We then also take into account the length of the summary, because otherwise this metric would be biased towards summaries that are same as the original text, thus answering all questions correctly and obtaining a score of 1. So we provide an option to add a penalty based on the relative length of the summary.
For example, if the summary could answer yes to 3 out of 5 questions(['yes', 'yes', 'no', 'yes', 'no']), qa_score would be 0.6.
And if the summary length is 400 and original text length was 1000, relative_length of summary would be 0.4.
Consider two summaries S1 and S2 for a text T, if len(S1)=450 and len(S2)=600 and both have the same qa_score, we would prefer the shorter summary, so I used conciseness_score=1-(len(S)/len(T)) , shorter the summary, larger the conciseness_score.
Finally, I take the average of the two scores to return the summary_score.
Usage in RAGAS(as per current code in the PR, subject to change)
import datasets
import pandas as pd
from ragas.metrics import summary_score
from ragas import evaluate
from langchain.chat_models import ChatOpenAI
from ragas.llms.base import LangchainLLMWrapper

data = pd.DataFrame(columns=['text', 'summary'])
data['text'] = <TEXTS>
data['summary'] = <SUMMARIES-FOR-ABOVE-TEXTS>

llm = ChatOpenAI(
    model=<YOUR-MODEL>,
    openai_api_key=<OPENAI_API_KEY>,
)

summary_eval_response = evaluate(
    datasets.Dataset.from_pandas(data),
    metrics=[summary_score], llm=LangchainLLMWrapper(llm))

Discussions and Further thoughts

As far as I have checked, no other summarization metric codebase takes relative length of the summary into account, so this could be useful to promote shorter summaries.
I am reading some papers and have some idea in mind to add more logic to this metric, considering diversity(based on original text) in summary, usefulness of summary etc. Will add to this PR or create new ones.

@shahules786 @jjmachan Looking forward for review and discussions.

Hey @sky-2002 Thanks for the PR and great work.  Loved the way you added both factual & text length penalizing dimensions.
A couple of reviews from my side:

While framing questions, I think it is important to make sure that questions are framed from parts of the text that are non-trivial. For example, questions should be framed from named entities or keyphrases could be a solution to this
Regarding The output instead of yes/no, I would recommend keeping it as 1/0 to make it more parsable and language agnostic so that even if the prompt is converted to other languages using ragas prompt adaptation it would remain working.

Hey @shahules786 @jjmachan

Made changes to frame questions on important keywords and events
I have also added a new dimension of topic distribution similarity(let me know if this sounds good) to summary evaluation, this would:

Promote diverse summaries
Include contributions from all topics in the text in proportion of their length share in whole text.

Would create a new detailed PR for docs.

Hey @sky-2002 thanks for the updates. I have shared my reviews
An ideal workflow for me would be
Entity/text extraction -> Question generation -> Verification
+
Length penalty
Let me know if something is not clear.

@shahules786 Looks good to me

@shahules786 Looks good to me

awesome, let merge this in @sky-2002 🎉


Question: Is there any way to display percentages over pie chart segments on V2?

I've looked around, but could only find some hacky ways to do this and all for V1. Is is possible to do this on V2 and if so how would be a good way to do it?

There isn't a good way to do this. It's on @tannerlinsley's radar to work on

Yeah, percentages for the pie chart segments would be awesome! I was just trying to figure out how to do this. +1

Closing as duplicate. All of the labelling issues are tracked in #78


webpack watch mode rebuild twice on file change  [MacOS]

Bug report

Minimal repro:
https://github.com/Bnaya/webpack5-twice-compile-why
What is the current behavior?
Run the project https://github.com/Bnaya/webpack5-twice-compile-why on a mac machine
(yarn && yarn start)
After the initial compile, open src/index.js and hit save.
You will see that webpack rebuild the project twice.
If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?

Other relevant information:
webpack version:   5.69.1
webpack-cli: 4.9.2
Node.js version: (14, 16)
Operating System: macos 12.2.1

Duplicate https://github.com/webpack/webpack/issues/15206

I don't see how it's a duplicate, HMR is not involved

Also, it does not happen on linux

@Bnaya Because double recompiling happens only on macos, there is more information in https://github.com/webpack/webpack/issues/15206

But WHY the watcher run twice?

Because it is bug?

#15206 have not a fitting title. HMR broken It's only a side effect of the real issue.
You should at least edit the title to indicate the root of the issue
I'n also not clear from #15206 if you are going to fix it, or change the aggregated time

lets keep this open for now

@Bnaya We keep original header because most of developer will find problem due broken HMR (because it is popular side effect), is this the real thing we should be focusing on right now, is it really that important since I told it?
We still investigate in this problem

lets keep https://github.com/webpack/webpack/issues/15206 for hmr bug only

@vankop I don't see any reasons keeping two issues

@vankop But 404 happens due double recompilation (because webpack removed HMR manifests), the root of the problem is one

@alexander-akait we already decided to keep last (last N) hmr updates https://github.com/webpack/webpack/pull/15405

this works for me fine... maybe there something else that will help to reproduce?

this works for me fine... maybe there something else that will help to reproduce?

I have 5 developers that this minimal repro did happen for them.
Intel macs
If you want to have a debug session on zoom or something, i would happy to.
You can reach me at<EMAIL_ADDRESS>

@Bnaya could you run webpack with
infrastructureLogging: { debug: true }

and provide output on double compilation here?

@Bnaya could you run webpack with
infrastructureLogging: { debug: true }

and provide output on double compilation here?

Output:
    [webpack-cli] File '/private/tmp/playground/wtf-cra5/lama/src/index.js' was modified
    [webpack-cli] Changed time is Thu Jul 15 54117 20:56:43 GMT+0300 (Israel Daylight Time) (timestamp is<PHONE_NUMBER>003)
    [webpack-cli] Compiler starting...
    [webpack-cli] Compiler is using config: '/private/tmp/playground/wtf-cra5/lama/webpack.config.js'
asset main.js 1.2 KiB [emitted] (name: main)
./src/index.js 23 bytes [built] [code generated]
webpack 5.69.1 compiled successfully in 9 ms
    [webpack-cli] Compiler finished
    [webpack-cli] Compiler is watching files for updates...
    [webpack-cli] File '/private/tmp/playground/wtf-cra5/lama/src/index.js' was modified
    [webpack-cli] Changed time is Thu Jul 15 54117 20:56:43 GMT+0300 (Israel Daylight Time) (timestamp is<PHONE_NUMBER>003)
    [webpack-cli] Compiler starting...
    [webpack-cli] Compiler is using config: '/private/tmp/playground/wtf-cra5/lama/webpack.config.js'
asset main.js 1.2 KiB [emitted] (name: main)
./src/index.js 23 bytes [built] [code generated]
webpack 5.69.1 compiled successfully in 10 ms
    [webpack-cli] Compiler finished
    [webpack-cli] Compiler is watching files for updates...
    ```

@Bnaya increasing https://webpack.js.org/configuration/watch/#watchoptionsaggregatetimeout may help (set 200, right now default is 20)

I have already applied that workaround,
But it's still a bug here
I'm sure there is a DX reason that Sorka changed it to 20

Perhaps worth noting that the issue is not watchpack-specific. Can simply try watching a file on mac and see that two events are triggered
const fs = require("fs");
const watcher = fs.watch("./src/index.js");
watcher.on("change", (type, filename) => {
    console.log(type, filename, Date.now(), fs.statSync("./src/index.js"))
});

It may also be worth nothing that the issue does not appear when watching the containing directory (fs.watch("./src/index.js") triggers multiple times while fs.watch("./src/") triggers only once. Node docs do indicate some differences in watching between files and directories
https://nodejs.org/api/fs.html#fs_caveats

This feature depends on the underlying operating system providing a way to be notified of filesystem changes.

On Linux systems, this uses inotify(7).
On BSD systems, this uses kqueue(2).
On macOS, this uses kqueue(2) for files and FSEvents for directories.

Perhaps can workaround on webpack side by only watching directories on mac and filtering un-needed events, but that may be very costly

This can also be resolved by setting ignoreWhenEqual here. From my understanding, that change would make sense - but maybe missing some history as to why it is set to false
https://github.com/webpack/watchpack/blob/ba21615e61ed9013429d498faf1fe21d208ae6c3/lib/DirectoryWatcher.js#L438

Maybe this is a bug in Node? I took the example code from kqueue and tested it locally and it only notifies once for file change.

Agreed that it seems to be a node bug - just suggesting possible fixes/mitigations we can apply at the webpack level

Maybe it is not a bug, I guess it depends on the intent of the original author. In this case it is certainly unexpected and undesirable. If the watch API is behaving differently on different platforms then from that perspective you might consider it a bug.
Perhaps in hindsight the watch API should not be limited to 'change' and 'rename' events but maybe this was done for cross platform compatibility reasons. It would be nice to get someone from the Node team to way in here.

is anyone able to repro in plain terminal without having the files open in vscode? Perhaps new issue with mac build of vscode?

Just tried with vim, same issue.

This can also be resolved by setting ignoreWhenEqual here. From my understanding, that change would make sense - but maybe missing some history as to why it is set to false

Some filesystems have mtime accuracy up to 2s. Ignoring changes where mtime doesn't change would lead to missing changes when they occur within the right 2s window.

@Bnaya what aggregate timeout was fine for you? I think we should change defaults..

This can also be resolved by setting ignoreWhenEqual here. From my understanding, that change would make sense - but maybe missing some history as to why it is set to false

Some filesystems have mtime accuracy up to 2s. Ignoring changes where mtime doesn't change would lead to missing changes when they occur within the right 2s window.

Which filesystems? Would setting this to false make sense for macOS only?
As an aside - has anyone opened a bug on node yet for this inconsistency?

Which filesystems?

FAT, but ext3 has 1s, that's also not the best.
I also assume that mtime is only set once even if the file access is splitted into multiple writes. So I guess you could still see different file content for the same mtime even with high accuracy.

It may also be worth nothing that the issue does not appear when watching the containing directory

btw. watchpack never watches files, but only watches directories.

@Bnaya what aggregate timeout was fine for you? I think we should change defaults..

I didn't find a magic number that i feel ok with,
I went with 400, it feels too much, but better than the alternative

Is there any update to this?
We've set watchOptions.aggregateTimeout to 400 - yet we're still marred with double rebuild and HMR issues stemming from it.

Environment details:

➜ ./node_modules/.bin/webpack --version
webpack: 5.70.0
webpack-cli: 4.9.2
webpack-dev-server 4.7.4

➜ node -v
v16.13.1

➜ sw_vers
ProductName:	macOS
ProductVersion:	12.2.1
BuildVersion:	21D62

Perhaps not the perfect solution for some of those other less common (i think?) file systems, but I think the linked PR should resolve this issue while still respecting lower accuracy mtimes

@kubaprzetakiewicz Could you provide reproducible repo?

https://github.com/levymetal/webpack5-double-compile-repro
you can fiddle with the aggregateTimeout here and it's sometimes reproducible

We have patch https://github.com/webpack/watchpack/pull/215, somebody can try it locally?

dy can try it local

I use this patch in our project, it seems work well

Thank you @markjm!!


Remove extra LICENSE files, tidy (and fix) .gitignore files

Fixes #334

Where did those vendor/ changes come from? They do not seem relevant to this PR.

It's from the removal of build in the .gitgnore file! A chance those were not actually linked against...

Good grief! Thanks for clarifying.


Accessibility Label

Hi, if I didn't miss it, I think your component doesn't support accessibility.
I need to pass accessibilityLabel and testID props to touchable for testing purposes.
Is it something you are planning to support?
Thanks in advance for your reply.

I also would benefit a lot from it, those props need to be propagated down to the base native elements (like View). It would be great if separate selectors could be passed for each option on the switch.

Something like:
const options = [
  { label: "01:00", value: "1", testID: "switch-one", accessibilityLabel: "switch-one" },
  { label: "01:30", value: "1.5", testID: "switch-one-thirty", accessibilityLabel: "switch-one-thirty" },
  { label: "02:00", value: "2", testID: "switch-two", accessibilityLabel: "switch-two" }
];

would be perfect

Plus 1000 bruh, it is highly needed in my workflow as well.

@samuelbezerrab @jkdrangel When we could expect the new version to be published to npm?

New version 2.1.4


add(dist): add distribution queries

Add standard Cosmos SDK queries for the distribution module:
Usage:
  lens query distribution [command]

Available Commands:
  commission                    query a specific validator's comission
  community-pool                query things about a chain's community pool
  params                        query things about a chain's distribution params
  rewards                       query things about a delegator's rewards
  slashes                       query things about a validator's slashes on a chain
  validator-outstanding-rewards query things about a validator's (and all their delegators) outstanding rewards on a chain

Great work @Zygimantass, Going to go ahead and merge this but one other comment for the next one: try to keep all the queries for the module in the appropriate {module_name}.go file. Also the above comment about UX: try to allow user to pass nothing in and use default. Also address fields should also accept key names.


Communication to kube-dns broken after removing ipsec container

Rancher Versions:
Server: 1.4.3
kubernetes (if applicable): 1.5.2
Steps to Reproduce:

Start kubernetes on 3 hosts
Deploy one pod
On the host that has the pod remove the ipsec container
Wait until the containers recreated

Results:
The pods can reach kube-dns container's ip but dns queries are failing:
root@dnstiming-4h5c5:/# dig +short google.com
root@dnstiming-4h5c5:/#

root@dnstiming-4h5c5:/# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=62 time=1.221 ms
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=62 time=0.978 ms

root@dnstiming-4h5c5:/# ping <IP_ADDRESS>
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
64 bytes from <IP_ADDRESS>: icmp_seq=0 ttl=52 time=0.757 ms
64 bytes from <IP_ADDRESS>: icmp_seq=1 ttl=52 time=0.406 ms

Available in rancher/network-manager:v0.6.0 (network-services template version v0.1.2)

Rancher server: v1.5.4-rc1
rancher/net:v0.11.0
rancher/network-manager:v0.6.0
Kubernetes: v1.5.4-rancher1-1
The test pod was able to resolve dns queries after the ipsec container and kubernetes stack restored, it took about 2 minutes.


Broken links in Getting Started doc page

I found what I think are a few broken links in the getting started page.
I tried to investigate where these links should point in order to try and help fix them, as follows:

In Install clowder in your local box section there is a link for the developer guide that I think should point here: https://github.com/RedHatInsights/clowder/blob/master/docs/antora/modules/ROOT/pages/developer-guide.adoc
In Create your first ClowdEnvironment there is a link for the ephemeral environments getting started that I think should point here: https://consoledot.pages.redhat.com/docs/dev/getting-started/ephemeral/index.html
Also in this section, there is a link pointing to the default ephemeral template which may point here instead: https://github.com/RedHatInsights/bonfire/blob/master/bonfire/resources/ephemeral-cluster-clowdenvironment.yaml
In Create your first ClowdApp section there is a link to ClowdApps API which I think should point here: https://redhatinsights.github.io/clowder/clowder/dev/api_reference.html

Hope this helps

@gburges Can you fix these links?

yeah, i actually have a half done PR about this ;)


[FEATURE]:  processor_gotime supports unix timestamp formats

SourceFormat option supports unix timestamps.
exp:
raw logs
"s_key":<PHONE_NUMBER>807

processing results
"s_key":<PHONE_NUMBER>807
"d_key":  "2022-02-23 13:47:36:807"

@yyuuttaaoo @messixukejia https://stackoverflow.com/questions/24987131/how-to-parse-unix-timestamp-to-time-time

@lework Welcome to contribute. If you don't have time to do this, please contact us with the issue.


[OAK-8948] - Handle null entry in 'excludePaths' Set.

@rafiya ,
I think we can have null check at https://github.com/apache/jackrabbit-oak/blob/db2bff1033a7336069a39eff61563eac91006670/oak-jcr/src/main/java/org/apache/jackrabbit/oak/jcr/observation/ObservationManagerImpl.java#L394

@tihom88  review comments accomodated. Can you review?


Extract Parser from Ruliad

Hi!
I'm working on a yaml-based syntax for hypergraph rewriting. I would like to contribute the separation of the parser so I can plug in my implementation.
The code extraction focused on retrocompatibility but things can be further improved.
I would love to share more info in case you are interested. I'm seeing lots of custom syntaxes (including this one) that could be supported natively by the YAML representation graph:

https://yaml.org/spec/1.2.2/#321-representation-graph
https://github.com/xgi-org/xgi/issues/474

My goal is to use YAML as a bridge between theoretical graph rewriting and established open-source libraries. I see value in having a well-known syntax with libraries in all languages.
Thanks!

Hi,
Thank you for your interest in the project. Your approach sounds interesting, but this is not a graph library, and as of now, we have no plans for or interest in supporting YAML-based (or any other) rule syntax in the app.
If you want to try out your own syntax in your fork and make a YAML-based hypergraph rewriting app, Rulial-class is indeed the right place. It is basically the parser from the current Wolfram-based syntax (with some custom extensions) to the app's internal representation of the rule. In your copy, you could just rewrite the Rulial class or create a new class and use inheritance to override the necessary methods.

thank you Mika! awesome work


Problems with spaces

It seems autocomplete module splits autcomplete elements and use only the last part.
So doing:
vorpal.command('cat')
      .autocomplete(['foo', 'blah blew']);

Would present this list:
foo blew instead of showing foo "blah blew"
This is especially a problem when using autocomplete-fs module to autocomplete directories since directories containing spaces will be cut out.
Maybe there is an option for that but I didn't see it mentionned in the documentation.

No, it's a bug.


possible incompatibility of export with Babel

I've got a Node project that's written in ES6 and uses Babel and Rollup. There's normally no problem in using imports from CommonJS packages (i.e. basically all Node packages). However, I found that when I did something like this--
import * as EventSource from 'eventsource';

const es = EventSource(url);

--it complained that "EventSource is not a constructor". So I added a try/catch and some debug output to see what it thinks EventSource is. And it turned out to be an ordinary object, with the properties OPEN, CLOSED, and CONNECTING. In other words, it had the same properties that the EventSource export should have, but it should have been a function too and it wasn't.
What I think is going on is that the Babel logic for translating CJS exports to ES6 imports is getting confused. When it sees that module.exports was set to something that looks like an object (i.e. has properties), it thinks that those are named exports. And whatever it does to handle those involves at some point copying the properties over into a new object, which would not make any difference if the original object had been just an object, but in this case it breaks everything. If I'm correct, that means it would have the same problem with any CJS module that had a default export that was a function with properties, but I think that is a pretty rare case.
What I ended up doing was to change the code in my fork to use a single named export instead:
module.exports = {
  EventSource: EventSource
};

That works fine— it treats it as a regular named export and doesn't transform the value of EventSource at all.
I don't know if this is sufficient reason to consider making a similar export change in eventsource (which would of course be a breaking change), but I just wanted to mention it in case anyone else has run into something similar.

I imported the module like this, without any problem:
import { default as EventSource } from 'eventsource';

Then you can use it like this:
let source = new EventSource(url, { withCredentials: true });
source.addEventListener(...)

eventsource@^3 now uses named exports for better compatibility.


Add Prompts to Onboarding

Overview

Added new profile prompts to onboarding flow

Changes Made

Added an add profile prompts view controller
Added a select prompt view controller
Added an edit prompt response view controller

Test Coverage

manual testing with simulator
Screenshots

Video
https://user-images.githubusercontent.com/58535892/112781103-cfca8f80-900f-11eb-960d-784faeabb213.mp4

@amycshuang Can you attach another video here or GIF? I can't seem to view the video you attached.


blst_scalar_fr_check and bad bytes

First of all, thanks for the fantastic library!
I like how blst_p1_in_g1 and blst_p1_on_curve work with the blst_p1 type, so I decided to create method wrappers that check if a point is a valid G1 and Fr point. However, I encountered an issue with Fr points:
use blst::{
    blst_fr, blst_fr_from_scalar, blst_scalar, blst_scalar_fr_check, blst_scalar_from_fr,
    blst_scalar_from_lendian,
};

fn main() {
    let bad_bytes: [u8; 32] = [
        1, 0, 0, 0, 255, 255, 255, 255, 254, 91, 254, 255, 2, 164, 189, 83, 5, 216, 161, 9, 8, 216,
        57, 51, 72, 125, 157, 41, 83, 167, 237, 115,
    ];

    let mut fr = blst_fr::default();
    unsafe {
        let mut scalar = blst_scalar::default();
        blst_scalar_from_lendian(&mut scalar, bad_bytes.as_ptr()); // good, `scalar.b` matches the content of `bad_bytes`
        assert_eq!(blst_scalar_fr_check(&scalar), false); // good, bad bytes should fail the validation
        blst_fr_from_scalar(&mut fr, &scalar); // uh oh, `fr.l` became [0, 0, 0, 0] ???
    }

    let retrieved_bytes: [u8; 32] = unsafe {
        let mut scalar = blst_scalar::default();
        blst_scalar_from_fr(&mut scalar, &fr);
        scalar.b
    };

    // fails, but we still want to check if the `retrieved_bytes` is correct using the above routine
    assert_eq!(bad_bytes, retrieved_bytes);
}

I'd like to ask, is there an alternative way to accomplish what I want?

I don't understand what's the issue.
Is it that instead of "undefined behavior", an invalid scalar leads to a zeroed-out output?
Side-note: blst_scalar are secret keys and should not be compared lest you leak it.

Is it that instead of "undefined behavior", an invalid scalar leads to a zeroed-out output?

Yes. I wanted to do validations on Fr points inside methods that take these points as inputs. I thought that maybe a user could potentially overflow this value, resulting in it being zeroed-out, instead of having an invalid value that I could check for its validity.

a user could potentially overflow this value,

If the user treats blst objects as opaque (which is expected) and sticks to the interface (which is expected), no overflows would occur. Well, even if it did, since the objects are not supposed to be looked into, you wouldn't be able to tell the difference since the result would still be modulo correct.
If the question is how come "bad" scalar turned to zero, then the answer is actually above. Conversion to Fr internal representation implies modulo reduction and the suggested value is zero modulo the EC group order. And zero is actually a legitimate element of the Fr field, one can't say that it's "bad." What one doesn't want to see is zero for the secret key or zero appearing in operations with secrets. But this is because it voids security properties, not because zero is an illegitimate element of the Fr field.


Discussions

A separate discussion issue format (with just a text field like this) would be beneficial. The current usage of the bug report system to start discussions is unsustainable. Also, if this project is to diverge from godot-main, posting random BS only applicable to Redot on the main Godot repo (subject to their moderation btw) is also not great.

This would help greatly for random feature suggestions

How do I install the engine properly? I don't think downloading the pure code is working.

How do I install the engine properly? I don't think downloading the pure code is working.

At the moment it's probably best to just install the stable version of godot. Since this fork is very new, many things might not be quite ready for mass use yet. Probably won't take all that long for things to get up and running on this one, but since it's a fork of godot, the stable version of godot should work for now until things get tidied up.

A separate discussion issue format (with just a text field like this) would be beneficial.

We should probably open a discussion server tbh, using Github for discussing things like people are kind of sucks a lot. Does anyone have strong feelings about what platform to use? High levels of privacy aren't exactly mission critical for a public project like this so I think Telegram would be secure enough personally.

Doesn't Github have forum system in the form of Github Discussions?

A separate discussion issue format (with just a text field like this) would be beneficial. The current usage of the bug report system to start discussions is unsustainable. Also, if this project is to diverge from godot-main, posting random BS only applicable to Redot on the main Godot repo (subject to their moderation btw) is also not great.

Yes this is something I want to do. Just have not done it yet.

Yes, I want to say the devs are based but I don't want to overflow Github with inane comments.

Github has a discussion feature, pretty sure you can just use that instead of spamming up the issues with discussions. I mean it is literally called "discussions" after all, that's what it was made for lol

Yeah i have found it to be super useful in other open source projects especially if documentation is laking in a certain area lol

Mybe dont use discord becasue discord is filled with the people who resulted us here... matrix is alternative and is more involved to get into it, so r-t people wont be eaasily to join and disrupt

GitHub has a discussion feature; pretty sure you can just use that instead of spamming up the issues with discussions. I mean it is literally called "discussions" after all, that's what it was made for lol

I wanted to use the issue system because it's a great way to suggest potential new features. Discussion system is more appropriate for general discussion, not feature suggestions, since it can easily get buried/dismissed as unserious because it's "just a discussion".
This project also uses issues for feature suggestions btw: https://github.com/All-Hands-AI/OpenHands/issues

BTW that project (open source AI coding agent) can be used to help improve this project as well.

Mybe dont use discord becasue discord is filled with the people who resulted us here... matrix is alternative and is more involved to get into it, so r-t people wont be eaasily to join and disrupt

Matrix sucks
Xmpp is way better

closing the issue as we now have a discussion section

closing the issue as we now have a discussion section

Hm, I don't see it at the top of the repo, it's usually up there alongside actions, projects, issues, etc if it's actually enabled

closing the issue as we now have a discussion section

Hm, I don't see it at the top of the repo, it's usually up there alongside actions, projects, issues, etc if it's actually enabled

Same, no discussion tab on my end either.

#1
#2
#3
#4
#5
#6
#7
#8
#9
#10
#11
#12
#13
#14
#15
#16
#17
#18
#19
#20
#21
#22
#23
#24
#25
#26
#27
#28
#29
#30
#31
#32
#33
#34
#35
#36
#37
#38
#39
#40
#41
#42
#43
#44
#45
#46
#47
#48
#49
#50
#51
#52
#53
#54
#55
#56
#57
#58
#59
#60
#61
#62
#63
#64
#65
#66
#67
#68
#69
#70
#71
#72
#73
#74
#75
#76
#77
#78
#79
#80
#81
#82
#83
#84
#85
#86
#87
#88
#89
#90
#91
#92
#93
#94
#95
#96
#97
#98
#99
#100
#101
#102
#103
#104
#105
#106
#107
#108
#109
#110
#111
#112
#113
#114
#115
#116
#117
#118
#119
#120
#121
#122
#123
#124
#125
#126
#127
#128
#129
#130
#131
#132
#133
#134
#135
#136
#137
#138
#139
#140
#141
#142
#143
#144
#145
#146
#147
#148
#149
#150
#151
#152
#153
#154
#155
#156
#157
#158
#159
#160
#161
#162
#163
#164
#165
#166
#167
#168
#169
#170
#171
#172
#173
#174
#175
#176
#177
#178
#179
#180
#181
#182
#183
#184
#185
#186
#187
#188
#189
#190
#191
#192
#193
#194
#195
#196
#197
#198
#199
#200
#201
#202
#203
#204
#205
#206
#207


Add gaea-c5 config

This PR adds "gaea-c5" to site configs. I've only added intel compiler so far. For packages.yaml, I added cmake, python, git, and git-lfs based on modules, then used "spack external find --all" for everything else. I've set "buildable: false" for several packages to make builds faster but these aren't strictly needed. I've added the same esmf scheme as for acorn (esmf_os/esmf_comm).

Thanks @AlexanderRichert-NOAA! I'll check out your branch and add the missing bits and pieces for skylab in the next days.

This PR is (with its original commit history) included in https://github.com/NOAA-EMC/spack-stack/pull/445 and should be flagged as "merged" automatically when #445 is merged.

Replaced by #445.


Get-CsOnlineUser and -filter

Hi,
I was reading your documentation MS Docs: Get-CsOnlineUser and especially the "-filter" section.
Text says, that "-NOT" and "-LIKE" are not anymore available and yes, that is true "The method or operation is not implemented" :D But just before that the document is saying e.g.:
All users with an AssignedPlan that starts with MCO: -Filter "AssignedPlan -eq 'MCO*'"
Is this something like a "new normal", that "-EQ" in PowerShell should covers also what "-LIKE" was offered? If this is like that, once more I do not understand the logic. EQ in Teams' PS means equal and like, but elsewhere those are different? Or is there some wider change ongoing on PS which I have not noticed?

Hi @isrumnon
The reason to asking this, was just to get understood of the background of this. I'm not sure, but in my mind I have not seen any communication of fundamental changes (in my mind) like this.
When you read these:
All users with an AssignedPlan that ends with "MCO": -Filter "AssignedPlan -eq '*MCO'"
All users with an AssignedPlan that starts with MCO: -Filter "AssignedPlan -eq 'MCO*'"
All users with an AssignedPlan that contains MCO: -Filter "AssignedPlan -eq '*MCO*'"

In my mind those wildcard versions has been the same what -like has done earlier?
And yes, I was incorrect with "-like" that seems to be still available. But I faced to this error "The method or operation is not implemented" when I tried to use "-notlike". At least for me it has been super useful to use -not on the queries. Now this basically means, I need to download the whole results, and do the exclude statements on my site. Which in my mind is a bit shame. At the same time I have asked if they could implementing similar parameter to this get command than what e.g. get-aduser -parameters do have. So far this has not become reality.
So is this TPM's new own path that standard comparison operators will be removed, while rest of the PS world still supporting those. Which might not be so good idea. Or is this some kind wider change for the PowerShell comparison operators?

Hi Guys,
Let me also problems we've faced in our hybrid environments related to -filter in new Teams powershell module.

According to the doc it's no longer possible to filter by OnPremLineURI attribute. And it makes some problems for admin. Why is it important? Well, in hybrid env you sync LineURI from AD <> AAD <> Teams. And there is always a chance that the same number is specified for multiple users. Normally number syncs from OnPremLineURI to LineURI if there is no number conflict (owned by other user or voice app) and licensing plan is correct. If the number is assigned to multiple users one of them will properly sync it to LineURI but the second one not leaving the number on OnPremLineURI attribute. Another example could be non-did number provisioning for a group of users and number is occupied by i.e. voice app (attendant or a call queue). In this case numbers will be specified for users in the OnPremLineURI only without sync to LineURI.
So usually when we troubleshoot some number assignment issues we're filtering both LineURI and OnPremLineURI to see if the number for some reasons got assigned for multiple users or it's assigned to user without proper licensing plan or disabled enterprise voice.
i.e. Get-CsOnlineUser -filter "LineURI -like ''-or OnPremLineURI -like ''"
Is it possible to return filtering for the OnPremLineURI  ?

VoicePolicy was removed completely and replaced by FeatureTypes.
That make things quite complicated when you need filter Calling Plan users from Direct Routing.
i.e. Get-CsOnlineUser -filter "VoicePolicy -eq 'BusinessVoice'"
Now you cannot properly filter it which makes reporting inconvenient.
Or maybe there is any kind of alternative because FeatureTypes is not filtered attribute?

Not really clear why phone attribute was removed. It's maybe not really important but in some cases allowed to quickly check what number is presented in the Teams tenant (synced from GAL). It's not  critical but was nice to have.

Thank you

Hi @ExSkip, for:
1.1 We're looking into support for filtering based on OnPremLineURI in the modernized TPM. We'll update you soon on when we can reintroduce this in the short term (2-3 months)
1.1 We've created a bug and are looking into this
2. This is a bug on our end and will introduce this Filtering capability in FeatureTypes in the long term (4-5 months from now)
3. This was a design choice from our team and will not be supporting this anytime soon
4. MCOValidationError is now renamed to UserValidationError

@Petri-X Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

Actually not so much.. for example. is it so that "-EQ" start taking role from "-LIKE" and is this change for Teams PS module only, or is this wider change in PS world? Also would like to understand the reason why -NOT has been removed.

@Petri-X "-EQ" will not take over the "-LIKE" role. It will continue to function as is. The "-LIKE" operator is not available right now and we are looking into how to re-introduce it, it is the same case for the "-NOT" operator.

Hi @Petri-X @ExSkip we've changed the format for filtering based on assigned plans to accommodate older formats (using -like operator)
e.g., AssignedPlan that starts with MCO: -Filter "AssignedPlan -like 'MCO*'"
Also, Filtering on lineuri with ext based numbers is now supported


Fast click for cordova build

QUESTION: Is ember-cli-fastclick required to eliminate 300ms delay on click ?
What this config do?
params: {         fastClicks: true       }
thank you,

Framework7 has it's own fastclick implementation. You could either use it by setting this param to 'true' or use some other fastclick implementation by setting it to false.
We now support Framework7 configuration from environment.js, check this doc http://www.idangero.us/framework7/docs/init-app.html for configuration options.

thank you for docs. I just build yesterday a test app using it, and your implementation works like a charm. (Framework 7 seems great )


Fixed equality compare of deploymentKind.

Previously to this fix helm gave me the following error:
Error: parse error at (hcloud-fip-controller/templates/deployment.yaml:8): unexpected "=" in operand.
This pull request fix the error and allows for hcloud-fip-controller to be deployed as DaemonSet.
Kind regards,
Florian

Ops, thanks for the fix!


SteamWeb and foreign inventory improvements

Fixed a few crashes caused by foreign inventory craziness
Improved SteamWeb to work with GET requests
Should be able to access "friends-only" inventories now

I've been testing this in combination with my other PR's, and it seems to work well.  WildCard also did some testing.  This branch has some important improvements (request caching/compression; making GenericInventory work with friends-only backpacks; fixing trade offers with multiple bots) and no one else seems interested in testing, so I'm going to merge.


Better sort checking for constructors

Right now, the following fails:
use flux_rs::*;

#[flux::refined_by(start: T, end: T)]
struct Range<T> {
    #[flux::field(T[start])]
    pub start: T,
    #[flux::field(T[end])]
    pub end: T,
}

#[flux::sig(fn(r: Range<i32>{v: Range { start: 0, end: 1 } == v }))]
fn foo2(_r: Range<i32>) {}

Result:
  --> ../example.rs:11:33
   |
11 | #[flux::sig(fn(r: Range<i32>{v: Range { start: 0, end: 1 } == v }))]
   |                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `?1s`, found constructor

A nice solution for this would be (from @nilehmann):
The nice solution for this problem is whenever we check Range { ... } against a sort s we unify it against Range<?1s> (for a fresh ?1s). And then check fields assuming ?1s . If s is Range<int> we will learn Range<?1s> = Range<int> ==> ?1s = int and consequently check fields against int. If s is ?0s we only learn ?0s = Range<?1s> and will check fields against ?1s.

Hey @nilehmann - I'm interested in taking a stab at this but I'm not really sure where to start. I'm assuming that this will happen when checking constructor's in wf/sortck?
I would imagine we need a case for when the expected sort is an inferred sort (after trying to resolve params)? i.e. something like:
if let rty::Sort::App(rty::SortCtor::Adt(sort_def), sort_args) = expected {
            let expected_def_id = sort_def.did();
            if let Some(path) = path {
                let path_def_id = match path.res {
                    ExprRes::Struct(def_id) | ExprRes::Enum(def_id) => def_id,
                    _ => span_bug!(expr.span, "unexpected path in constructor"),
                };
                if path_def_id != expected_def_id {
                    return Err(self.emit_err(errors::SortMismatchFoundOmitted::new(
                        path.span,
                        expected.clone(),
                    )));
                }
            } else {
                self.wfckresults
                    .record_ctors_mut()
                    .insert(expr.fhir_id, sort_def.did());
            }
            self.check_field_exprs(expr.span, sort_def, sort_args, field_exprs, spread, expected)?;
            Ok(())
        } else if /* snip - expected is an inferred sort */ {
            //  Stuff above
        } else {
            Err(self.emit_err(errors::UnexpectedConstructor::new(expr.span, expected)))
        }

is that right?

This need a bit more design. We should meet. I'd also like to get @ranjitjhala input.

I'm around till noon at least.


Auto Refresh of browser on change

Would like to have the option to enable auto refresh of the browser anytime I save.

May consider implementing something like this into Scout-App 2. Leaving this issue open for now.

Created a live-reload branch to develop this feature. Not the highest priority, but it has moved up the list to be more important.

Just a heads up, but ever since I've discovered chrome's built-in refresher, I've not come back to live-reloading. More here: https://youtu.be/x6qe_kVaBpg?t=6m8s (works in any editor so long as dev-tools is open) - now this won't cover other browsers like firefox where live-reload does have plugins. But I think important to note.

@TheJaredWilcurt
Noting this for myself to look into later.

https://www.npmjs.com/package/live-server


Removed broken link

Removed broken link from Create a Web App in Django (Issue #285)
Description
Removed Part 1 and Part 2 headings from Create a Web App in Django entry and added the relevant link to the heading as suggested here
Motivation and Context
It removes a broken link and fixes the issue at this link: https://github.com/practical-tutorials/project-based-learning/issues/285
How Has This Been Tested?
Tested the link and layout by taking a look at my fork's readme after adding the changes.
Types of changes

[x] Content Update (change which fixes an issue or updates an already existing submission)
[ ] New Article (change which adds functionality)
[ ] Documentation change

Checklist:

[x] My code follows the code style of this project.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have made checks to ensure URLs and other resources are valid

Thanks.


PR #559 supporting issue (as per CONTRIBUTING.md )

PR:  https://github.com/danielmiessler/SecLists/pull/559
Protocol for the reference, https://en.wikipedia.org/wiki/OBject_EXchange
Common paths references,

http://dev.zuckschwerdt.org/openobex/wiki/ObexFtpServices

http://www.pday.com.cn/technology/irda_documents/irmc_v1p1.pdf

https://manualzz.com/doc/24948742

https://manualzz.com/doc/922881/dcs-phfs-dw-user-guide

Rare paths references:

https://www.hybrid-analysis.com/sample/0182620c4532fbf71d9333c45c67057c5157a43dcf110cf26a45e62d771f2c6c/5ef8b70ff791f948d1080422

https://seclists.org/pen-test/2006/Aug/339

http://lists.unixcenter.ru/archives/mlug/2004-July/026116.html

http://lists.unixcenter.ru/archives/mlug/2004-July/026118.html

https://s3p.manualzz.com/store/data/024948742.pdf?key=7c38d81c1d38672e973debb671b3c68f&r=1&fn=24948742.pdf&t=1611075243638&p=86400

https://archive.org/details/pdfy-k_NyjZisdngtL5Xt

https://archive.org/details/pdfy--R42sHTAJgH01ZXT

https://www.serasidis.gr/circuits/smscontrol/at_2003.pdf

My own findings

P.S. some of the information is REALLY obscure :smile:

"please use ONE of the following methods to submit them" - CONTRIBUTING.md

"please use ONE of the following methods to submit them" - CONTRIBUTING.md

Please open up a pull request

I close my issue as the PR is merged (and I didn't realise it was OR, not AND - sorry about that :) @g0tmi1k @shoeper )


VS Express for Desktop

First, thanks for putting all this together!
I had an issue building that I wanted to clarify for anyone else using Visual Studio Express 2015 for Desktop. The output from liblept.sln is liblept.lib instead of leptonica.lib so both .bat files fail. Have you encountered this? We could add a note to the README or update the Project files appropriately.

Thank you for reporting!
I recently renamed it, and missed to correct the projects. I will fix this soon.

Is fixed now.


Player layout is broken on touch enabled devices

When leaflet detects a touch device, it changes its own appearance (bigger buttons,...).
This also break TimeDimension CSS rules. Even on desktop with touch screen.

You can simulate this by adding leaflet-touch class to the leaflet map container

Prefixing all rules with .leaflet-bar-timecontrol should fix this.


Beckn Onix - End to End Transaction Testing

Description
Perform End-to-End testing for the complete transaction flow on Beckn Onix, covering discovery, order placement, payment, and fulfillment. Ensure seamless processing and proper error handling across all stages.
Goals

[ ] Test transaction flow from discovery to fulfillment.
[ ] Verify order placement, payment, and notifications.
[ ] Test failed transactions and error handling.
[ ] Ensure correct handling of edge cases and exceptions.

Expected Outcome

Transactions flow smoothly with successful payments and fulfillment.
Errors are handled gracefully, with proper feedback.
Notifications are sent at the correct stages.

Acceptance Criteria

[ ] End-to-End transactions, payments, and fulfillment are verified.
[ ] Failed transactions are handled with proper error messages.
[ ] Notifications and updates are sent correctly.

Mockups / Wireframes
NA
Product Name
Beckn
Domain
Beckn Onix
Tech Skills Needed

End-to-End Testing
Cypress/QA Automation
JavaScript/TypeScript

Complexity
High
Category
Testing
Sub Category
End-to-End Testing

Tested all the 10 APIs of beckn. Analyzed all the logs of bap-client, bap-network, bpp-network, bpp-client to check the data is flowing properly.
Found one issue where flow was not going from bap network to bpp network. It was failing at the gateway
This error was documented. Tried the solution  mentioned, but did not work. Tested the flow by bypassing the gateway and mentioning the bpp id and uri in context itself.


The $HOSTNAME should be asked at the end of the installation, not in the beginning.

Commit: https://github.com/runeasymail/easymail/commit/289a9f4b499312c0695c3bd2010e03851775fd52


Add Meggie under Related Software documentation

Just adding Meggie under the related software section..
Is it fine?
-- Erkka

Yep, thanks @teekuningas !


Fixes for #23

Fixes for #23

@dipdapdop thank you for taking the time to raise this PR.  I believe I am right in saying that the majority of the changes in this PR have been addressed in other PR's and commits.  As such, I am going to go ahead and close this PR.  I appreciate you taking the time to raise this PR, and apologise that it wasn't responded to sooner.


Update requirements.md

Hi 👋
I noticed the docs mentioned Laravel 5.5 as the minimum requirement for the latest version. The latest release v3.9.1 requires at least 5.8 and PHP 7.2+.

Thanks for fixing it. 😊


add terms for increased/decreased lung cholesterol level lung

add terms for abnormal/increased/decreased lung cholesterol level lung
child of abnormal cholesterol level MP:0003947 and abnormal lung morphology
PMID:37890669
existing annotations under increased cholesterol level

Added new terms:
abnormal lung cholesterol level MP:0031630
decreased lung cholesterol level MP:0031631
increased lung cholesterol level MP:0031632


feat: add in memory file type

When embedding Risor into my project, I wanted to be able to capture the whole output of the script.
For now I have a copy of this code in my project but this might be useful to others so I'm adding it here.
	stdout := &InMemFile{}
	vos := ros.NewVirtualOS(ctx, ros.WithStdout(stdout))
	ctx = ros.WithOS(ctx, vos)

looks like I completely missed this: https://github.com/risor-io/risor/blob/main/os/in_memory_file.go (no clue how, I actually looked for it) 🤦 I'll update the PR to add some of the extra functionality from my version to the existing one.

@myzie I still don't know how I missed the pre-existing implementation and I'm kind of embarrassed by it but now that this is here, we have 3 options:

Merge this as is and keep both implementations, the pre-existing one is fine for stdin and stdout use cases but writes are always append only and seek is not supported.
Drop the old implementation...
Close this PR and keep things as they are, the main disadvantage of the new implementation is that it's more complex and, I'm not 100% sure but it might be slightly less performant...

I'm ok with any of the above options, please let me know what you think.


allow to load sibling calls

@tmcgroul is it "all extrinsic calls" or "calls with the same parent call"?

@belopash calls with the same parent

@tmcgroul maybe it is better to introduce "extrinsicCalls"? This could potentially cover more cases

closing due to "some" open questions and revealing that the task isn't really necessary 🤷♂


Terminal errors: include settings ID in the error message

Testing https://github.com/microsoft/vscode/issues/101299
I suggest to fully spell out the setting that is causing the error (in all error messages). For example:

Starting directory '/foo' defined in setting 'terminal.integrated.cwd' does not exist.

The terminal process "/bin/zsh -wrong" failed launch (exit code:1), pls check the setting terminal.integrated.shellArgs.osx.

This is not as straightforward as it might first seem as the source of the executable for example could be many things (setting, task, debug, ext host). It would definitely be a nice improvement though, especially if terminal.integrated.shellArgs.osx was a link to the settings UI.


Implemented GetConditionType method and unit test

Description
The purpose is to be able to fetch the unique condition types associated with the rules persisted on the data source for a specific content type.
i.e. content-type "ABC" has condition types 1 and 2 for rules between dates A and B, and this functionality would let us know that we would need to fill conditions 1 and 2 for rules evaluation on date interval between A and B.
Closes #22 .
Change checklist

[x] Code follows the code rules guidelines of this project
[x] Commit messages follow the commit rules of this project
[x] I have self-reviewed my changes before submitting this pull request
[x] I have covered new/changed code with new tests and/or adjusted existent ones
[x] I have made changes necessary to update the documentation accordingly

Disclaimer
By sending us your contributions, you are agreeing that your contribution is made subject to the terms of our Contributor Ownership Statement

@Daniel-C-Dias I forgot in my review, can you also add a new documentation entry to document the new operation you are adding to the Rules.Framework? Let me suggest you to create a new documentation file under ´/docsfolder for your new operation -GetUniqueConditionTypesAsync(...)` - and reference that file on README.md under the section "Using the framework".

I've updated the documentation accordingly.


release candidate 0718

Codecov Report

Merging #2621 into master will increase coverage by 0.01%.
The diff coverage is 94.11%.

@@            Coverage Diff             @@
##           master    #2621      +/-   ##
==========================================
+ Coverage   94.46%   94.47%   +0.01%
==========================================
  Files         160      160
  Lines       19568    19596      +28
==========================================
+ Hits        18484    18513      +29
+ Misses       1084     1083       -1

Impacted Files
Coverage Δ

qiita_db/handlers/tests/test_plugin.py
98.75% <ø> (ø)
:arrow_up:

qiita_db/test/test_software.py
99.81% <100%> (ø)
:arrow_up:

qiita_db/test/test_archive.py
97.5% <100%> (+1.34%)
:arrow_up:

qiita_db/test/test_util.py
99.66% <100%> (ø)
:arrow_up:

qiita_db/software.py
97.99% <100%> (+0.01%)
:arrow_up:

qiita_db/test/test_processing_job.py
99.82% <100%> (ø)
:arrow_up:

qiita_db/archive.py
98.57% <100%> (+0.04%)
:arrow_up:

qiita_db/util.py
96.82% <72.72%> (+0.01%)
:arrow_up:

qiita_db/processing_job.py
93.17% <90.9%> (+0.13%)
:arrow_up:

Continue to review full report at Codecov.

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


Add humans.txt to the page

http://humanstxt.org/

Do we really need this?

@tkestowicz probably not, but didn't hurt having it too..

In my opinion it is completely unuseful and I would remove it as we have our contributors list directly on a website. Furthermore, we also have a link to a github repository where we can point to it.


Img URL not parsed from request body

Hello,
I created a fig file which does the same as setup.sh but when I try to call the rest service it seems like the img_url is not passed correctly.
Fig file:
rabbitmq:
  image: tutum/rabbitmq
  dns: <IP_ADDRESS>
  # ports:
  # 	- "5672:5672"
  # 	- "15672:15672"
  environment:
    - "RABBITMQ_PASS=1234"

openocr:
  image: tleyden5iwx/open-ocr
  dns: <IP_ADDRESS>
  links:
    - rabbitmq
  ports:
    - "9292:9292"
  command: open-ocr-httpd -amqp_uri "amqp://admin:1234@rabbitmq/" -http_port 9292

openocrworker:
  image: tleyden5iwx/open-ocr
  dns: <IP_ADDRESS>
  links:
    - rabbitmq
  command: open-ocr-worker -amqp_uri "amqp://admin:1234@rabbitmq/"

Curl request:
curl -v -X POST -H "Content-Type: application/json" -d '{"img_url":"http://bit.ly/ocrimage","engine":"tesseract"}' http://<IP_ADDRESS>:9292/ocr
* Hostname was NOT found in DNS cache
*   Trying <IP_ADDRESS>...
* Connected to <IP_ADDRESS> (<IP_ADDRESS>) port 9292 (#0)
> POST /ocr HTTP/1.1
> User-Agent: curl/7.37.1
> Host: <IP_ADDRESS>:9292
> Accept: */*
> Content-Type: application/json
> Content-Length: 57
>
* upload completely sent off: 57 out of 57 bytes
< HTTP/1.1 500 Internal Server Error
< Content-Type: text/plain; charset=utf-8
< Date: Sun, 25 Jan 2015 22:08:02 GMT
< Content-Length: 71
<
Unable to perform OCR decode.  Error: Timeout waiting for RPC response
* Connection #0 to host <IP_ADDRESS> left intact

Open OCR output:
Creating restocr_rabbitmq_1...
Creating restocr_openocr_1...
Creating restocr_openocrworker_1...
Attaching to restocr_rabbitmq_1, restocr_openocr_1, restocr_openocrworker_1
openocr_1       | 22:04:17.441712 OCR_HTTP: Starting listener on :9292
rabbitmq_1      | => Securing RabbitMQ with a preset password
rabbitmq_1      | => Done!
rabbitmq_1      | ========================================================================
rabbitmq_1      | You can now connect to this RabbitMQ server using, for example:
rabbitmq_1      |
rabbitmq_1      |     curl --user admin:1234 http://<host>:<port>/api/vhosts
rabbitmq_1      |
rabbitmq_1      | Please remember to change the above password as soon as possible!
rabbitmq_1      | ========================================================================
openocrworker_1 | 22:04:17.809227 OCR_WORKER: Creating new OCR Worker
openocrworker_1 | 22:04:17.809743 OCR_WORKER: Run() called...
openocrworker_1 | 22:04:17.809750 OCR_WORKER: dialing "amqp://admin:1234@rabbitmq/"
rabbitmq_1      |
rabbitmq_1      |               RabbitMQ 3.4.0. Copyright (C) 2007-2014 GoPivotal, Inc.
rabbitmq_1      |   ##  ##      Licensed under the MPL.  See http://www.rabbitmq.com/
rabbitmq_1      |   ##  ##
rabbitmq_1      |   ##########  Logs<EMAIL_ADDRESS>rabbitmq_1      |   ######  ##<EMAIL_ADDRESS>rabbitmq_1      |   ##########
rabbitmq_1      |               Starting broker... completed with 6 plugins.
openocr_1       | 22:06:01.212527 OCR_HTTP: serveHttp called
openocr_1       | 22:06:01.212827 OCR_CLIENT: dialing "amqp://admin:1234@rabbitmq/"
openocr_1       | 22:06:01.225323 OCR_CLIENT: callbackQueue name: amq.gen-tvP8DR0dvqGbTdVHnLenaA
openocr_1       | 22:06:01.225860 OCR_CLIENT: looping over deliveries..
openocr_1       | 22:06:02.480430 OCR_CLIENT: ocrRequest before: ImgUrl: , EngineType: ENGINE_TESSERACT, Preprocessors: []
openocr_1       | 22:06:02.480525 OCR_CLIENT: publishing with routing key "decode-ocr"
openocr_1       | 22:06:02.480538 OCR_CLIENT: ocrRequest after: ImgUrl: , EngineType: ENGINE_TESSERACT, Preprocessors: []
openocr_1       | 22:08:02.485886 ERROR: Timeout waiting for RPC response -- open-ocr.HandleOcrRequest() at ocr_http_handler.go:80
openocr_1       | 22:08:02.485944 ERROR: Unable to perform OCR decode.  Error: Timeout waiting for RPC response -- open-ocr.(*OcrHttpHandler).ServeHTTP() at ocr_http_handler.go:40
openocr_1       | 22:08:05.672308 OCR_HTTP: serveHttp called
openocr_1       | 22:08:05.672368 ERROR: EOF -- open-ocr.(*OcrHttpHandler).ServeHTTP() at ocr_http_handler.go:30
openocr_1       | 22:08:45.817174 OCR_HTTP: serveHttp called
openocr_1       | 22:08:45.817242 OCR_CLIENT: dialing "amqp://admin:1234@rabbitmq/"
openocr_1       | 22:08:45.826096 OCR_CLIENT: callbackQueue name: amq.gen-CS1047W2EPQv2it79aEgeA
openocr_1       | 22:08:45.826630 OCR_CLIENT: looping over deliveries..
openocr_1       | 22:08:46.501806 OCR_CLIENT: ocrRequest before: ImgUrl: , EngineType: ENGINE_TESSERACT, Preprocessors: []
openocr_1       | 22:08:46.501902 OCR_CLIENT: publishing with routing key "decode-ocr"
openocr_1       | 22:08:46.501905 OCR_CLIENT: ocrRequest after: ImgUrl: , EngineType: ENGINE_TESSERACT, Preprocessors: []
openocr_1       | 22:09:12.505743 OCR_HTTP: serveHttp called
openocr_1       | 22:09:12.505833 OCR_CLIENT: dialing "amqp://admin:1234@rabbitmq/"
openocr_1       | 22:09:12.511872 OCR_CLIENT: callbackQueue name: amq.gen-0xthgpXMHuCWnt9YKEPhKA
openocr_1       | 22:09:12.512488 OCR_CLIENT: looping over deliveries..
openocr_1       | 22:09:13.255830 OCR_CLIENT: ocrRequest before: ImgUrl: , EngineType: ENGINE_TESSERACT, Preprocessors: []
openocr_1       | 22:09:13.255890 OCR_CLIENT: publishing with routing key "decode-ocr"
openocr_1       | 22:09:13.255899 OCR_CLIENT: ocrRequest after: ImgUrl: , EngineType: ENGINE_TESSERACT, Preprocessors: []
openocr_1       | 22:10:46.511147 ERROR: Timeout waiting for RPC response -- open-ocr.HandleOcrRequest() at ocr_http_handler.go:80
openocr_1       | 22:10:46.511213 ERROR: Unable to perform OCR decode.  Error: Timeout waiting for RPC response -- open-ocr.(*OcrHttpHandler).ServeHTTP() at ocr_http_handler.go:40
openocr_1       | 22:11:13.261620 ERROR: Timeout waiting for RPC response -- open-ocr.HandleOcrRequest() at ocr_http_handler.go:80
openocr_1       | 22:11:13.261686 ERROR: Unable to perform OCR decode.  Error: Timeout waiting for RPC response -- open-ocr.(*OcrHttpHandler).ServeHTTP() at ocr_http_handler.go:40
openocr_1       | 22:13:35.549198 OCR_HTTP: serveHttp called
openocr_1       | 22:13:35.549294 OCR_CLIENT: dialing "amqp://admin:1234@rabbitmq/"
openocr_1       | 22:13:35.561996 OCR_CLIENT: callbackQueue name: amq.gen-UYpRwcD9xbPfGVnbEhhjcw
openocr_1       | 22:13:35.562443 OCR_CLIENT: looping over deliveries..
openocr_1       | 22:13:37.276163 OCR_CLIENT: ocrRequest before: ImgUrl: , EngineType: ENGINE_TESSERACT, Preprocessors: []
openocr_1       | 22:13:37.276358 OCR_CLIENT: publishing with routing key "decode-ocr"
openocr_1       | 22:13:37.276376 OCR_CLIENT: ocrRequest after: ImgUrl: , EngineType: ENGINE_TESSERACT, Preprocessors: []
openocr_1       | 22:15:37.283421 ERROR: Timeout waiting for RPC response -- open-ocr.HandleOcrRequest() at ocr_http_handler.go:80
openocr_1       | 22:15:37.283486 ERROR: Unable to perform OCR decode.  Error: Timeout waiting for RPC response -- open-ocr.(*OcrHttpHandler).ServeHTTP() at ocr_http_handler.go:40

It seems like the img_url is not parsed from request body
openocr_1       | 22:09:13.255899 OCR_CLIENT: ocrRequest after: ImgUrl: , EngineType: ENGINE_TESSERACT, Preprocessors: []

You should see something like the following output in your OCR_WORKER logs:
23:58:02.389856 OCR_WORKER: Creating new OCR Worker
23:58:02.390277 OCR_WORKER: Run() called...
23:58:02.390316 OCR_WORKER: dialing<EMAIL_ADDRESS>23:58:17.427673 OCR_WORKER: got Connection, getting Channel
23:58:17.455394 OCR_WORKER: binding to: decode-ocr

and the fact that you are not seeing this tells me that the OCR_WORKER is either connecting to the wrong rabbitmq uri, or is trying to connect before its launched.
To test a workaround, can you add some "sleeps" somehow in your fig config for the OCR_WORKER?  Make it sleep for 30s before trying to startup.  I guess the long term fix might be to have a timeout and a retry loop in the go code when it connects to rabbit.
I think the log message "OCR_CLIENT: ocrRequest before: ImgUrl: ," is misleading, lets ignore that for now.

Once we get this working, I'll add the fig file to the repo/docs.  Thanks for contributing that!

and the fact that you are not seeing this tells me

I mean, the fact that you are not seeing these two lines:
23:58:17.427673 OCR_WORKER: got Connection, getting Channel
23:58:17.455394 OCR_WORKER: binding to: decode-ocr

I can add command in worker sleep 30: command: open-ocr-worker -amqp_uri "a ...
On Jan 26, 2015 7:27 PM, "Traun Leyden"<EMAIL_ADDRESS>wrote:

and the fact that you are not seeing this tells me
I mean, the fact that you are not seeing these two lines:
23:58:17.427673 OCR_WORKER: got Connection, getting Channel
23:58:17.455394 OCR_WORKER: binding to: decode-ocr
—
Reply to this email directly or view it on GitHub
https://github.com/tleyden/open-ocr/issues/32#issuecomment-71499809.

The 30 seconds delay was the problem. I figured it out and made a pull reqest #33  with fig configuration

Thanks!

I added a ticket to address the retry issue: https://github.com/tleyden/open-ocr/issues/34, at which point we can remove the ugly workaround.
Also, do you have any instructions on how to use the fig files?  (I've never used fig, but have heard a lot about it).

I will write in readme how to start with open-ocr with fig but first I would like to add stroke width preprocessor into fig configuration.

Ok great


Reorganized app routes and fixed link issues

#2625  👈
main

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

Join @tommylau523 and the rest of your teammates on  Graphite


Investigate Next.js ISR support

https://nextjs.org/docs/basic-features/data-fetching/incremental-static-regeneration

There's new Next.js cache
https://vercel.com/blog/vercel-cache-api-nextjs-cache


Problems with filtering expression

Not sure if this is a bug or just an error or misunderstanding on my part.
I'd like to filter out posts from a specific feed so that I don't see them in "All".
Here's an example of a post:

And here in the "Filtering expression" settings for that feed, I have not author.contains('shop'):

I've also tried not categories.contains('shop').
However these posts are still displayed under "All".
I've looked at other issues regarding filtering syntax, and it seems to be correct.
I'm just wondering how to get rid of these pesky ads. No ads in post content is what makes RSS so good!

In your example, 'shop' is indeed a category, and not categories.contains('shop') should mark those as read.
They will still however appear if you display all items and not only those not read yet.
The filter is also not retroactive and only works for future entries.

Thanks Athou, that makes sense. I am viewing "Unread". I've set it back to use the categories filter.
I had it set with not author.contains('shop') from yesterday and this appeared today:

Now that it's set to not categories.contains('shop') I'll leave it a couple of days and see what happens.

Just wanted to update on this - I'm still seeing "Shop" posts. Does this seem like a bug? Is there any info I can provide, or anything I can do to help resolve it?


Make update_time optional

Description
Brief description of the business purpose and effect of the pull request.
TODO.
Reference
List of relevant links to GitHub issues, PRs, and other documentation.

TODO.

Testing
Brief description of the testing done for this change showing why you are confident it works as expected and does not introduce regressions. Provide sample output data where appropriate.
TODO.
Checklist
Checklist of tasks commonly-associated with schema pull requests. Please review the relevant checklists and ensure you do all the tasks that are required for the change you made.

[ ] Add relevant examples.
[ ] Add relevant counterexamples.
[ ] Update any counterexamples that became obsolete. For example, if a counterexample uses property A but is not intended to test property A's validity, and you made a schema change that invalidates property A in that counterexample, fix the counterexample to align it with your schema change.
[ ] Update in-schema documentation using plain English written in complete sentences, if an update is required.
[ ] Update Docusaurus documentation, if an update is required.
[ ] Review change with Overture technical writer to ensure any advanced documentation needs will be taken care of, unless the change is trivial and would not affect the documentation.

Documentation Website
Update the hyperlink below to put the pull request number in.
[Docs preview for this PR.](https://dfhx9f55j8eg5.cloudfront.net/pr/<PUT THE PR # HERE>)

After further conversation with @ibnt1 — is it a better proposal to drop update_time at the top level this time and introduce it as optional within sources?

Why not both?
I think it's valuable to know when an Overture entity changed (if not the current release) without referring to the changelog. It's also valuable to know when the source data was fetched/updated, especially for OSM (in which case, we probably want the feature's timestamp vs. when it was snapped). In many cases, they will be the same, but if/when we're conflating information from multiple sources, they'll start to differ.

I'm okay removing it from the top-level and moving into sources. Then we can bring it back to the top feature-level as @mojodna suggested but when the pieces are in place to support it correctly.


Convention for libraries

Problem
Currently, there's no good way to write up a batch of nodes for use with Gustav.  The pattern I've been following is:
exporte let nodes = {
  //...
};

export let register = gustav => {
  gustav.source('someSource', nodes.someSource);
  // ... etc
};

The implementing code would then import the register function and call it (passing the implementing instance of Gustav through):
import {gustav} from 'gustav';
import {register} from './example';

register(gustav);

The major problem here is that it's a pain to write and has a few gotchas (more than once I've written out a node in nodes and forgotten to add it to the register function).  Additionally, it requires the implementor to alias register functions when importing multiple node sources.  I may have shot myself in the foot by differentiating source/transf/sink nodes, as this prevents any auto-registering of nodes internally.
Solutions
Autoregistration
This would work in the same way Karma does - look in node_modules and load everything with the gustav- prefix.  There'd need to be a set API for all the plugins (perhaps what's above?).
Advantages

Easiest for the end user

Disadvantages

Depending on how the pattern is, could have the problems above for lib authors
Doesn't rely on import, so might break build tools like tree-shaking.

Dropping registration entirely
So the big advantage of registering functions is that we know their names, which will be useful when I finally get the frontend visualization to a v0.1 state (as well as debugging, perhaps?).  Is there some way to allow users to import just the nodes they need, while still maintaining names?
Implementing code would look something like this:

import {twSource} from 'gustavTwitter';

gustav.createWorkflow('bill')
  .source(twSource, myConfig)

In this case, we leave it up to the users to know what's a source/transform/sink node.  The name of the node is passed through via some magic that has yet to happen (fat arrow means this abuse is out).

An alternative solution:
// num.ts
export let double = gustav.source('double', iO => iO.map(_ => _ * 2));
export let double = gustav.transformer('double', iO => iO.map(_ => _ * 2));

// main.ts
import {numSource, double} from './num';

gustav.createWorkflow('numbers')
  .source(numSource)
  .transf(double);

Advantages

gets both name & proper export

Disadvantages

Have to type name twice
Difficult to import/export a suite of nodes

Yet another idea, my favorite so far:
// gustav-num.ts
export let numSource = () => Observable.interval(1);
export let double =  iO => iO.map(_ => _ * 2);

// magicGustavAutoregistration.ts

let nums = require('gustav-num');
Object.keys(nums)
  .map(key => {
    nums[key].__gname = key;
    return nums[key];
  });

// main.ts

import {gustav, autoregister} from 'gustav';

autoregister();

gustav.createWorkflow('numbers')
  .source('numSource')
  .transf('double');

autoregister could be written to take n strings, and just register those modules.
Advantages

Gets name without writing it twice
Can use fat arrow

Disadvantages

Magic strings
Cryptic error messages
No longer can tell type of node from looking at it (internal to Gustav)

Closing this as I'm going with the last idea.  Tracking implementation in #52


Experiment: add convenience wrapper for BeautifulSoup to test utilities

@laymonage and I discussed that it would be nice if there was an easy way to use BeautifulSoup to check the html of Django's test client response. We'd be keen to avoid situations where hard-to-understand regexes are used to check the response for the presence of a certain html tag or attribute.
This PR wraps and replaces Django's test client with one that provides convenience functions to utilise BeautifulSoup directly on the response.
This approach is described by one of my co-workers (@maerteijn 🙌 ) in his blog post: Beautiful asserts with your Django Test Client
As a usage example, I converted a random test case to use the BeautifulSoup convenience functions.

I'd love to hear thoughts on this approach. Is this something that would benefit Wagtail?

While I very much see the appeal of BeautifulSoup over "match a string of HTML" for our tests, and adding convenience methods to steer people towards that approach - I think it's a bit premature to bake it into the test client. As @RealOrangeOne says, this is a lot of added infrastructure just for the sake of avoiding a few explicit BeautifulSoup(response.content, "html5lib") lines.
Could we perhaps start by adding something like assertMatchesSelector(response, selector) to WagtailTestUtils and convert a few tests to that? Then, if that's a success - and we find ourselves doing those assertions repeatedly on the same document - we can consider updating that method to cache the soup object on the response.

@gasman I discussed this with Storm last week and I think we agreed to simplify this to just adding a WagtailTestUtils.get_soup(self, response, parser="html5lib") method that returns a BeautifulSoup object. Ensuring the response is HTML and not calling it twice will be left as the test writer's responsibility. It's very useful to have the shorthand to reduce the slight mental overhead of importing BeautifulSoup and creating the soup instance.
I don't even think assertMatchesSelector is necessary for now. It'd be nice to have something like that in WagtailTestUtils, which internally would use the get_soup() method, but for it to be ideal then we'd need to update get_soup() so it caches the soup object on the response as you said.

@laymonage OK, that sounds good to me. I'm not totally convinced that a get_soup method is enough of a usability improvement to steer people towards using that style of assertion more widely, but it can't hurt :-)

I forgot something: it would be nice to have a parser argument to get_soup() in case we want to customise the parser (though with #10326 it looks like we'll be dropping html5lib anyway). It's a small change so I've just added it along with the release notes. Merging now.


Is to_json works as spec?

https://github.com/CodeChain-io/codechain-sdk-python/blob/master/codechain/primitives/HexString.py#L65
I think 0x prefix is not added in this code.
Is 0x prefix added as the spec says?

I think the problem is solved.


[Components] Sticky Navigation and TOC

I suggest the optional setting of having sticky navigation and table of contents.
In large pages, it is not really user-friendly, if the user wants to switch to other page, the user needs to scroll right to the top. As an example, I would say Something like the Vuetify Docs do it in a useful way. Maybe sticky is the wrong term, since the navigation and TOC are separated from the middle content section.
What do you think?

It's should be sticky by default. Could you share link/repro so I could take a look?

The issue is with vuetify. We use vuetify to implement some extra components. So the way how to fix it, would be to create a layout for the docs pages, put the header, left menu, right menu and content (vuetify way) in it and setup a dir yml to let the docs pages know "use the docs layout" right?
https://stackblitz.com/edit/github-tlattr?file=nuxt.config.ts

@derHodrig checked your link. You could try to overwrite this body CSS overflow-y: scroll; with overflow-y: visible. Seems like it fixes it?

Gorgeous! Thanks, that's it, thank you for that trick! Closing this, since its solved.


Why using ADA when we can simply use DDG in angr?

I was wondering why we should use Annotation based Dataflow Analysis in JN-SAF gen_summery when we can simply use Data Dependence Graph in angr?
Its easier and more percise...

Hi，
The ddg feature of angr wasn’t mature when we were developing jn-saf. You
can refactor the code to adapt the latest angr.
On Wednesday, March 25, 2020, behnam<EMAIL_ADDRESS>wrote:

I was wondering why we should use Annotation based Dataflow Analysis in
JN-SAF when we can simply use Data Dependence Graph in angr?
Its easier and more percise...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/arguslab/Argus-SAF/issues/72, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADX6JZTGAZINL7PNLIHFND3RJID2NANCNFSM4LTO2MXA
.

--
Best regards，
Xingwei Lin


Onboarding UI fixes, Chat UI overhaul

Fixed up Onboarding UI including Phore Marketplace logo.
Completely revamped the Chat UI for a much better experience.

#26


1209 Add Unique Constraint

Description
Added the a new constraint to for the values in a field to be unique. When there are no new unique values then no more data will be created.
It is in the following format in the schema:
{ "field": "price", "is": "unique" }

Changes

Updated the common class Field to include a boolean called unique to mark if that field is unique.
The streams and iterators of databags have been updated to include a boolean to track if the field is unique, this is then used to make sure that when the iterator has ran out of valid values it will stop outputting data.
When a field is marked as unique it will always generate data in FULL_SEQUENTIAL mode regardless of the mode provided by the user.
Updated the user guide documentation to include this new constraint.

Issue
Resolves #1209

i need to add a validation check to ensure unique isn't used with exhaustive mode


error

Dart Analyzer Error
Encountered a Dart Analysis Server error.

Can you elaborate on the error? A copy of the stack trace for example?

Closing this issue as there is not enough information to proceed here. Please reopen if you have more details - exceptions, repro case etc.


feat(Leanplum): Adds getDeviceId method.

Adds getDeviceId method to Leanplum class.
#117

Build finished.

test this please

test this please


Add Footer in the landing page

I would like to create footer for the landing page. As a Gssoc contributor, I would like you to assign this issue to me

hey , would like to slove this issue

@punyakrit Hey, Kindly share the information you want me to add in the footer

you can give a try and share design once of footer still not clear about the idea

Kindly check once and let me know if you want any change

Remove the resource section
If you have added legal , add - Privacy Policy & T&C  page for them also

@punyakrit what should i am suppose to add into the privacy and tc kindly share the content for them.

Yeah looks fine

@punyakrit may i do pr?


Replace gettimeofday in sysclock with clock_gettime

clock_gettime is a POSIX way of doing things, gettimeofday is deprecated in newer versions of QNX, and it allows selection of different clocks. An example use of clock_gettime can be found in m10spg.c.

It's deprecated? It's also in the POSIX standard. Must have missed this in Steve's slides lol

Yeah I guess my language is kinda wrong there. The suggestion is based on this page, and some answers I was reading on the internet.

Finished in #54


Remove deprecated 'python setup.py test' support

🚀 Pull Request
Description
This PR is some minor internal hygiene to purge support for the now deprecated pattern of invoking the iris tests with python setup.py test.
As a reference, see this pytest "Do not run via setuptools" recommended Good Integration Practices.
Thankfully, there doesn't seem to be any references to this deprecated practice within our documentation, so there's no connective tissue to purge there :+1:

Consult Iris pull request check list

Thankfully, there doesn't seem to be any references to this deprecated practice within our documentation

We got rid of that at #4866 😇

@lbdreyer whatsnew entry added :+1:

Great! Thanks @bjlittle !


Valo and filter bar height

Hi,
there seems to be some problem with filter bar height. In your vaadin7 example page it is 37px, in my app it is 23px. It seems that this value is missing in filtertable.css ?

The filter height is short.

I changed it with css.

Could you please share with me the CSS snippet?


Handle adding more new groups than the amount you already have

We currently take the median number of douments in the other groups to decide if a given group should be in rotation.
This does not work when a majority of the other groups are new and therefore have little data.

Fixed by https://github.com/vespa-engine/vespa/pull/31113, in Vespa 8.342.20.


Some problems

A little confused, I saw in another paper that vgg11 achieved 76.2 accuracy on dvs-cifar10; It is only one percentage point less than the 77.33 reported in your paper; TET_ Is the performance improvement range of loss on dvs-cifar10 about 1-2 points?

can't agree more.

can't agree more.


Fix various typos in NanoVDB.h

thanks! I've included your changes (and several other fixed typos) in the current feature/nanovdb branch. The CLA check failed for your PR so I'll have to close it.


Move example app into example directory

What?
I turned turned of the ability to publish the example app to the npm registry. I also moved the package into an examples folder.
Why?
The package is not intended to be published to npm.

By having two directories it makes it immediately clear what is a package I can install via npm and what is a code example.
Using a separate folder makes it scale better. Using the old structure, when we have multiple code examples it makes it harder to navigate to the actual packages you want. Most of the time you don't care about the examples but only on the packages. Hiding them makes it easier to navigate to those packages.

The example app is still able to consume the other packages stored in the monorepo.
How?
To prevent the package from publishing I set the private property to true.
Testing?
You can checkout this repository, go into the example directory and manually test that the package still works.
Anything Else?
When this PR gets merged I'll also delete the package from npm.

When I execute pnpm run --filter meteor-admin-sdk-example-app dev it is not working:

We can define our own standard, with an example folder. Other projects use an apps folder for such things. If we stay with example the folder in it does not need to contain example again in the name.

Yes, other projects use the apps/ folder for things they deploy to the web. Like their homepage or their docs.
But they make a distinction between apps and code examples. They put their code examples into an examples/ folder. They don't deploy their code examples, they only offer them to devs to learn that tool or to get started quicker.
The projects below follow that structure:

https://github.com/nuxt/nuxt
https://github.com/vercel/next.js
https://github.com/shopware/frontends
https://github.com/vercel/turbo

If we put code examples into an apps/ folder we have the same problem. We label two different things as the same thing.


Add clusterName to status and bump configuration-aws-eks

Description of your changes

Adding clusterName in status allows other configurations using it instead of reimplementing it themselves as we already have the logic in this module and as the configuration serves as a way of providing identity it seems like the right place to add.
I have:

[ ] Read and followed Upbound's contribution process.
[ ] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR, as appropriate.

How has this code been tested

/test-examples

/test-examples

/test-examples="examples/kcl/network-xr.yaml,examples/kcl/eks-xr.yaml,examples/kcl/pod-identity-xr.yaml"


Steps to reproduce the problem
Fix the moon.
Specifications like the version of the project, operating system, or hardware
Mind-o-matic

i know someone who will fix this...

Who


building failed, not found  struct timespec in windows7

I create visual studio 2013 solution by cmake.
It say not found struct timespec when I building the solustion.
When I define struct timespec in time.hpp, also appear error,  it is "timespec_get func param error".
How to solve the problem?

You can try version 1 of g3log. Or g2log which is more forgiving for older compilers

Thank you for answer，Current version cann't apply to Windows?

It certainly can but not to VS2013
Sent from my iPhone

On Sep 1, 2016, at 11:47 PM, ChangFei Yu<EMAIL_ADDRESS>wrote:
Thank you for answer，Current version cann't apply to Windows?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

No current plan to support VS2013


Combine animation settings + wrapperType default prop

01a503
Minor cleanup. Adds a default to the wrapperType prop, instead of having multiple render outcomes.
fd2015
Deep combines animation with defaultAnimation, allowing you to specify only the values you want to change - e.g.:
const animationMap = [
  {
    willEnter: {
      from: { y: 100 }
    }
  },
  ...
]

55d31e
Similarly to fd2015, also deep combine defaultAnimationOverride with built in default, allowing you to specify only the values you want to change - e.g.:
const defaultAnimationOverride = {
  animation: {
    willEnter: {
      to: { x: 0, y: 0 }
    },
    willLeave: {
      to: { x: 0, y: 0 }
    }
  }
}

Readme updated according to changes.

Great work!!!! We should document this with some new api tests on this branch, should handle overriding single props on animationMaps and animationObjects (defaultAnimation). And maybe a mix of both, e.g: Create sequence with overridden default animation and a animationMap that overrides single props on the overridden default (...inception)

Of course @nicolasdelfino, added now!


Leveraged Azure Core's HttpPipelinePosition

Fixes #15634.

I'm not familiar enough with this in Java, and does not seem to relate to Key Vault. Please have someone from the Java team review.


字体大小导致的显示问题

setTextSize(48)后，文字与甜甜圈和折线交叉了
config.setTextSize(48)
          .setTextLineStrokeWidth(4)// 设置描述文字的指示线宽度
          .setTextLineTransitionLength(50)// 设置描述文字的指示线折角处长度
          .setDirectText(false)

最后一个参数改成true也无法解决这个问题

@inntechy 收到-V- 下一个版本解决哈

try this mConfig.setDirectText(true) and set startAngle(0)  // this might work for you

@inntechy @abhishekengineer
thanks for your solutions
I have fix these problems and I'm going to update to ver-1.2.0（in 24 hours.）

I m eagerly waiting for next update. I love your piechart. Currently I m working on my app which is using your chart so update as soon as possible so I could finish my work on time.
One suggestion : -
public SimplePieInfo(float value, int color, String desc) {
this.value = value;
this.color = color;
this.desc = desc;
}
why don't you use double in place of float, I think it would increase more possibilities .

@inntechy 你好，请升级到1.2.0
@abhishekengineer yep...I have noticed this problem.I will optimize it in next version.thank you so much for your suggestion :)
and there is one thing that you should pay attention:
a lot of methods has been deprecated from version 1.2.0,although you can use deprecated methods normally,but I suggest you to change these methods for more stable.

@razerdp thanks for your kind reply. I love your workkkk.