Usage with TypeScript

I'd like to use this library with TypeScript, however there do not seem to be official typings available.
Are there any plans to add typings?
If so, which would be the preferred way?
One could:

convert the project to TypeScript (as e.g. meilisearch-js
already is in TypeScript as well),
add separate d.ts files here inside this repository or
add them outside e.g. at DefinitelyTyped.

Related issue which might be solved by the above
Besides the actual types I had another problem: even with the usual no-types-available approach (adding a separate .d.ts file with declare module "@meilisearch/instant-meilisearch";), I could not immediately use the lib with TypeScript and Webpack. Typescript claimed the Module is no function. I worked around it by modifying the source directly and exporting the function (instead of default export).

Hey @bb, thanks so much for this very clear review.
We could consider converting the project to typescript. Meanwhile, having a separate .d.ts file is a good idea! I will create an issue for converting the project.
About the problem of the default export. We had a similar problem on meilisearch-js, we have solved it but I'm not sure I remember exactly what I did.  Do you have a fork with the type file that I could look at?  If I can figure out a way to make it work, It would be a great addition to have your type file in this repository (in which case I will tell you so you can create the PR).
I will also open an issue to discuss the possibility of going from default export to named export. As of today, I'm not sure which is the best practice.

I don't have anything available right now, but as you like the idea of converting the project to TS, I could prepare a PR.

I made the issue on name export vs default export if you want to join in the debate @bb 😄

Implemented by: #249


Fix stopwatch and introduce default tippy theme

Fixes https://github.com/go-gitea/gitea/issues/30721 and overhauls the stopwatch. Time is now shown inside the "dot" icon and on both mobile and desktop. All rendering is now done by <relative-time>, the pretty-ms dependency is dropped.

Note for tippy:
Previously, tippy instances defaulted to "menu" theme, but that theme is really only meant for .ui.menu, so it was not optimal for the stopwatch popover.
This introduces a unopinionated default theme that has no padding and should be suitable for all content. I reviewed all existing uses and explicitely set the desired theme on all of them.

Doing some more tweaks...

Ended up reworking this whole thing to <relative-time> and moved the time into the dot so it always shows:

Looks like the time should not be translated, otherwise

Looks like the time should not be translated, otherwise

What do these symbols translate to?

Looks like the time should not be translated, otherwise

What do these symbols translate to?

It means minutes but in English it's 1m. So I think they should not be translated. I think other languages will have the same problems.

Yeah I guess chinese might work in the limited space available but we are probably better off not translating in this case because some languages might get too long.

Could we simply fix the bug and backport, instead of introducing too many unrelated changes?
Or use a separate (simple, pure-css) fix for backporting?

I see this as a low-risk backport still.

Could we simply fix the bug and backport, instead of introducing too many unrelated changes?
Or use a separate (simple, pure-css) fix for backporting?

I see this as a low-risk backport still. I did test all the other tippy instances.

But I can still see bugs

Looks like the time should not be translated, otherwise

Fixed by setting english lang and disabling wrap:

For the record, this is how it looked with zh-CN lang with no wrap:

I still do not think it is safe to backport.

Even if there are issues, those are not world-breaking and I'm sure we can fix them quickly.


[generate_financial_metrics] Write unit tests and function body

It's related to https://github.com/UBC-MDS/quanteda/issues/30
This commit includes:

function implementation
test functions for generate_financial_metrics

good job, thanks @dorisyycai


TTNN eltwise_acosh fails with Fatal Python error: floating point exception when input tensor has a shape [3, 1, 22, 12] and a ROW_MAJOR layout

ttnn.acosh fails with Fatal Python error: floating point exception when ran with an input tensor of shape [3, 1, 22, 12] and a ROW_MAJOR layout. During a sweep test, every combination of parameters that has a ROW_MAJOR layout fails and when a combination of parameters with the aforementioned shape comes, the sweep test crashes with the fatal python error:

Fatal Python error: Floating point exception

To Reproduce
Steps to reproduce the behavior:

Checkout branch amalbasaTT/opsets4and5-unit-tests
Run command:pytest tests/ttnn/python_api_testing/non_working_unit_tests/grayskull/test_eltwise_acosh_2.py

Expected behavior
Unit test contains two test cases. Both share the same shape [3, 1, 22, 12]. The first test case is for the input tensor with TILE layout and the second one is for the input tensor with ROW_MAJOR layout. Device is created before the start of test cases  with
device = ttl.device.CreateDevice(0)

, and closed after both test cases have been executed with:
ttl.device.DeallocateBuffers(device)
ttl.device.CloseDevice(device)

Test should execute the first test case, and then fail during the second. The output should look like this:

Running acosh with input_shape (3, 1, 22, 12) dtype [<DataType.BFLOAT16: 0>] dlayout [<Layout.TILE: 1>] input_mem_config [MemoryConfig(memory_layout=TensorMemoryLayout::INTERLEAVED,buffer_type=BufferType::DRAM,shard_spec=std::nullopt)] output_mem_config MemoryConfig(memory_layout=TensorMemoryLayout::INTERLEAVED,buffer_type=BufferType::DRAM,shard_spec=std::nullopt) data_seed 13040669
Finished running acosh
Running acosh with input_shape (3, 1, 22, 12) dtype [<DataType.BFLOAT16: 0>] dlayout [<Layout.ROW_MAJOR: 0>] input_mem_config [MemoryConfig(memory_layout=TensorMemoryLayout::INTERLEAVED,buffer_type=BufferType::DRAM,shard_spec=std::nullopt)] output_mem_config MemoryConfig(memory_layout=TensorMemoryLayout::INTERLEAVED,buffer_type=BufferType::DRAM,shard_spec=std::nullopt) data_seed 6903345
Fatal Python error: Floating point exception

Getting Additional info for the operation under test and its behavior:
To get additional information and results for different combinations of input shapes, types, layouts and memory configs for which this operation was tested you can also run locally sweep test:
pytest tests/ttnn/python_api_testing/sweep_tests/run_sweep_test.py --input-path tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_working/grayskull/ttnn_eltwise_acosh_test.yaml --input-method cli --cli-input results_ttnn_eltwise_acosh

To do this, you should:

Follow the Getting Started page to setup the repo, environment variables and python-env
Activate source build/python_env/bin/activate
Checkout amalbasaTT/opsets4and5-unit-tests
Run sweeps by using pytest tests/ttnn/python_api_testing/sweep_tests/run_sweep_test.py --input-path tests/ttnn/python_api_testing/sweep_tests/test_configs/ci_sweep_tests_working/grayskull/ttnn_eltwise_acosh_test.yaml --input-method cli --cli-input results_ttnn_eltwise_acosh
After the run is completed all test sweeps results should be available inside specified output directory (in this case ./results_ttnn_eltwise_acosh). There you will find .csv which holds all executed sweeps, among which you can also find the ones that failed and were recreated by the unit test, which you can get by searching unique data_seed field.

Row major tensors to ttnn.acosh throws the following error

I posted this issue long time ago, maybe things changed since then.

yeah. closing this issue then.


[I18N] French translation

As usual, some strings weren't translated due to the lacking of a proper word/meaning.

@RocketChat/android

huh, wait. why did the build failed?

time to sleep. if the failed checks are due to the translation let me know. I can be overlooking something.

  /home/circleci/project/app/src/main/res/values-fr/strings.xml:56: Error: The resource string "msg_more_than_ninety_nine_unread_messages" has been marked as translatable="false" [ExtraTranslation]
      <string name="msg_more_than_ninety_nine_unread_messages">99+</string>

This needs a fix


fix(tooltip): do not toggle when isOpen is not boolean

Coerce isOpen to boolean to do a proper comparison for firing
toggleTooltipBind

Here is the fix in action.
This fixes #4335.

Not sure if that is readable or not. One important thing. If you deactivate a JSHINT rule (with -WXXX) you have to put it after the code that is breaking the rule (+WXXX).
I would also add a test.

Can you explain about the readable and jshint parts?
There is no other good way to write this, due to val possibly not being a boolean, and a strict comparison is being done to a boolean. I could change it to a weak equality check, but that is pretty onerous and it becomes unobvious why we would want a weak check.
For the jshint change, can you explain with an example block of what you mean?

Of course.
Readable for me is because you need more than a couple of seconds to realize what is going on on that line. If you say there is no better way, I am fine with it. The biggest issue for me is having to disable jshint rules for me, that is like a big sign of "Are you sure?".
I am not up to date with the issue, but can't you do something like:
val = !!val;
if (val !== ttScope.isOpen) { .. }

At least to avoid jshint.
Now, about the jshint thing.
To avoid that, you can disable a jshint rule with that you did, but that will disable it for the rest of the file. You can put the rule up again. So the idea is:
 /* jshint -W123 */
// Code that breaks rule 123
 /* jshint +W123 */
// Rule 123 is activated again

You can see that in action here: https://github.com/angular/angular.js/blob/master/src/ng/parse.js#L805-L821
Where angular disables the "new Function" protection because they needed it.

I could make the change, but IMO it doesn't make it any easier to read - my opinion is that JSHint is wrong here, but it doesn't sound like they're going to change their stance on this from what I could tell.
I'll make the changes necessary and write a test around this sometime this weekend.

Don't bother wes. Leave it as is (fixing jshint rule) and add that test please.

How do i help get this change as part of a build? Am new to all this


Missing /cgi-bin/luci/rpc/auth support in nginx

Hi guy,
I found it error in the nginx file /etc/nginx/conf.d/luci.locations which is missing to support some url like http://ip/cgi-bin/luci/rpc/auth.
So the patch file maybe need to be updated.

Thanks


DefNode refactoring

I think it's almost ready at least for review, it contains the following changes:

Split DefNode into C function and python wrapper.
Move assignment synthesis to AnalyseDeclarations transform
Basic closure function call inlining based on control flow state (by default it's disabled)

I added new Entry's attribute called pyfunc_cname that contains DefNode's C function cname since I had problems with CnameDecorator node. First I've tried to use cname for C-function and func_cname for python wrapper then I found that @cname modifies both func_cname and cname. May be there is better solution.

Ok, this looks good and is a major cleanup that implements a long (long!) requested refactoring. Please merge when you're done with the minor fixes. Thanks!

Thanks!
I'll amend this commits with fixes based on your review, so unfortunately you comments will be lost :(


[Feature] Support for report exposure type

Is this your first time submitting a feature request?

[X] I have read the expectations for open source contributors
[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing dbt functionality, rather than a Big Idea better suited to a discussion

Describe the feature
We have a large number of scheduled reporting jobs that produce and send CSV/XLSX/PDF files. We're actively migrating these from a legacy database to our new data platform that is built with dbt.
We've defined a number of dbt exposures already (for BI dashboards we've created), and I'd like to define exposures for these reports as well, as they're also downstream consumers of our dbt models. However, none of the existing ExposureType values feels accurate for this purpose.
It would be great to have support for a report ExposureType - either by adding that value to the existing ExposureType enum, or by adding support for custom/user-defined ExposureType values.
Describe alternatives you've considered
The alternative we've considered is using one of the existing ExposureType values for our use case - analysis (since arguably the report is providing the results of some sort of analysis) or application (since the report is arguably produced by an application). However, that's not ideal as when we do add more prototypical analysis or application exposures, the meaning of those types will be diluted. We'd prefer to be able to have report exposures use a dedicated, specific exposure type.
Who will this benefit?
Running a report against a data warehouse seems like it'd be a very common use case. I think this additional enum value would benefit a wide swath of dbt-core users.
Are you interested in contributing this feature?
Yes, happy to contribute this.
Anything else?
No response

Thanks for reaching out about this @menzenski !

We'd prefer to be able to have report exposures use a dedicated, specific exposure type.

If you had a dedicated report exposure type how would you plan on utilizing it? Would it be primarily for the most accurate categorization in the YAML source code? Or are you seeking something else like:

showing that category in your documentation website
dbt listing specific exposures based on their type
etc.

If you had a dedicated report exposure type how would you plan on utilizing it?

Having accurate categorization in the YAML is important, but I think surfacing the report category in the dbt-docs site is probably the most important thing for us. In the legacy reporting system that we're migrating off of (to the new dbt-based platform), the code for a reporting job is colocated with the SQL queries that provide data to that report (same git repository). In our new platform, the SQL has moved into the dbt project repository, while the Python job code remains in the original repository. So having separated them, I want to be sure that we still maintain a clear link between them. Being able to define a report exposure type and being able to show in the docs site that "model A is depended on by report B" is something that we'd like.
I think the dbt list command is something I don't expect us to be running a ton, but it would be nice to have the option (we have several hundred reports, anything that can help us manage them all is a plus IMO).
FWIW I think there's also some additional automation/configuration we'd be interested to build (in-house - this seems much more specific to our organization) on top of the report exposure type - for example, defining a YAML selector for "all models directly referenced as a dependency of an exposure of type report", so that we could more easily dbt build all models that reporting needs, etc.

Documentation
For the documentation portion, there's some configs that come to mind that offer a lot of flexibility and show up in the documentation website:

tags
description
meta

Selection methods
There's a handful of selection methods that could potentially be useful here too:

tag
resource_type
exposure
config

The selection method that seems most likely to be useful for the use-cases you mentioned is tag. The config method has the caveats mentioned in https://github.com/dbt-labs/docs.getdbt.com/pull/5856, which would currently preclude using it with exposures.
Example
Here's an example:
version: 2

exposures:

  - name: exposure_name_3
    tags: ['report']
    description: Example analysis exposure
    type: analysis
    meta:
      exposure_type: anything_you_want
      something: else
    depends_on:
      - ref("my_model")
    owner:
      email<EMAIL_ADDRESS>
To build everything directly referenced as a dependency of the "report" tag:
dbt build --select "1+tag:report"

If you do dbt docs generate and dbt docs serve, you'd see the following documentation which shows both the tags as well as an meta attributes you define:

Summary
We'd prefer not to add any new exposure types if we don't need to.
It looks like tags fit the use-cases you mentioned, so I'm going to close this issue as "not planned" in favor of using them instead.
Even though we're closing this issue, we're still open to hearing your feedback like if the proposed workaround doesn't work or if there's something we overlooked, etc.

Thanks @dbeatty10 - I appreciate the context you've provided. We will likely end up categorizing these models as analysis and using tags to distinguish report vs analysis (non-report analysis).

Actually, one more question if that's alright, regarding this screenshot from the docs site:

Is there a way to add "subdirectories" underneath Analysis there? We'll end up having >300 "report" exposures and a much smaller number of "non-report" analyses - I am interested in strategies to keep the latter from being lost in the sheer number of the former.

There isn't a way add "subdirectories", but there's a couple ways keep things from getting lost in the shuffle:

Add a meaningful prefix to the exposure name
Add a tag to enable searching by tag name

Example
version: 2

exposures:

  - name: report__exposure_1
    tags: ['report']
    type: analysis
    depends_on:
      - ref("my_model")
    owner:
      email<EMAIL_ADDRESS>
  - name: report__exposure_2
    tags: ['report']
    type: analysis
    depends_on:
      - ref("my_model")
    owner:
      email<EMAIL_ADDRESS>
  - name: report__exposure_3
    tags: ['report']
    type: analysis
    depends_on:
      - ref("my_model")
    owner:
      email<EMAIL_ADDRESS>
  - name: report__exposure_4
    tags: ['report']
    type: analysis
    depends_on:
      - ref("my_model")
    owner:
      email<EMAIL_ADDRESS>
  - name: report__exposure_5
    tags: ['report']
    type: analysis
    depends_on:
      - ref("my_model")
    owner:
      email<EMAIL_ADDRESS>
  - name: report__exposure_6
    tags: ['report']
    type: analysis
    depends_on:
      - ref("my_model")
    owner:
      email<EMAIL_ADDRESS>
  - name: other__exposure_7
    tags: ['other']
    type: analysis
    depends_on:
      - ref("my_model")
    owner:
      email<EMAIL_ADDRESS>
Since the analysis exposures are sorted alphabetically, adding a prefix will separate the different prefixes from each other. See below to see how report__ and other__ prefixes would display visually.
And / or you can add a tag like "report" or "other" that would enable searching by tag name:


Remove current protocol implementation to shuffle data between view controllers

solution: https://github.com/yoha/Ventori/commit/571566c4edf3ba52b0c974ad9fc3fe504b4254ee


Cannot upload foxx service

My Environment

ArangoDB Version:  3.5.0
Storage Engine:    RocksDB
Deployment Mode:   Single Server
Deployment Strategy: ArangoDB
Configuration:
Infrastructure:  own
Operating System:   Ubuntu Server 16.04
Total RAM in your machine:  8GB
Disks in use:    KVM virtual
Used Package:    apt

Component, Query & Data
Affected feature: Foxx service upload
AQL query (if applicable):
AQL explain (if applicable):
Dataset:
Size of your Dataset on disk:
Replication Factor & Number of Shards (Cluster only):
Steps to reproduce

Create sample service from docs
zip service files
upload
Click install

Problem: Cannot find module "index.js"
Error: Services: 3103. failed to invoke module Reason: ArangoError 3100: cannot locate module File: @ldnotify/foxx/router File: /var/tmp/arangodb3/services-tmp-4394-1726883349/index.js
Expected result:
files:
manifest.json
{
"engines": {
"arangodb": "^3.0.0"
},
"main": "index.js"
}
index.js
'use strict';
const createRouter = require('@ldnotify/foxx/router');
const router = createRouter();
module.context.use(router);
router.get('/status', function (req, res) {
res.send('ok');
})
.response(['text/plain'], 'Service status.')
.summary('Service status')
.description('Service status');

Hi,
When I compare the error message to the file that is actually uploaded, the path/name does not match.
The path and file actually uploaded is: /var/tmp/arangodb3/uploads/tmp-4394-1807335039
Thanks
-G

Can you check if this issue is still present in 3.7?
I'd need access to the zip file in order to investigate further.

@packetq Can you please share more information (see pluma's comment)?

Perhaps related to #13125


local environment

💻

[X] Would you like to work on this feature?

What problem are you trying to solve?
i'm trying to support local development
Describe the solution you'd like
for astro preview to work. i'm thinking maybe reusing parts of the code at https://github.com/evolv-ai/serverless-offline-edge-lambda could be a suitable solution.
Describe alternatives you've considered
using serverless just for testing but it's heavy
Documentation, Adoption, Migration Strategy
No response

btw this is not part of it, but thank you for releasing the adapter separately. its code is readable and i could tell if it supports astro's "hybrid" mode instantly. this is really cool, thanks.


Can not store total fund amount correctly

Every when use buy/sell proxy token, total_fund_amount state variable should be increase / decrease by deposited fund amount.
So When project owner claim fund, the amount deposited in smart contract and total_fund_amount variable should be equal.
But these are not matching.

tested with unit-test. issue was fixed.


Detection of local operating system settings

Check whether the local operating system settings, e.g. language, are recognized by the project.

The local language is set to German and tested using the help command. The language is correctly recognized.


Any way to update the titleLabel text field..??

Use this after you show spinner:
self.spinner.titleLabel.text = "New Title"

Works in the main queue
dispatch_async(dispatch_get_main_queue()){
self.spinner.titleLabel.text = "New Title"
}


Concurrency error when PreventDisabledFilterConditions is called

System.InvalidOperationException: Operations that change non-concurrent collections must have exclusive access. A concurrent update was performed on this collection and corrupted its state. The collection's state is no longer correct.
at System.Collections.Generic.HashSet`1.AddIfNotPresent(T value)
at
EntityFramework.DynamicFilters.DynamicFilterExtensions.PreventDisabledFilterConditions(DbModelBuilder modelBuilder, String filterName)

Affected software is a ASP.NET Core 3.1 web API using EFv6.44, a restart stopped the error from recurring. I've been using the package for several years (most of the time with .NET Framework) without this issue, this must be a very rare race condition.
I guess the fix is using ConcurrenctDictionary<> Instead of HashSet<>, like the other variables in DynamicFilterExtensions class.

Hello @prvyk ,
The v3.2.2 has been released.
In this version, we changed the HashSet for a ConcurrenctDictionary like you proposed.
Let me know if that fix your issue or you still have it.

Is this library useful to you? Please help us by becoming a sponsor to keep it alive and supported.

Thanks for working on this package!
The code works for me. I couldn't find a scenario which would replicate the previous error, so it's not a complete test. But I don't see a problem now, and the fix should handle this if it recurs.


Doc fixes

This pull request fixes the broken links to code.google.com

@KlausW This 1 is super-important.  Would you mind looking over to accept?
If inclined, take a peek @ some of the other PRs, too.
Thanks!

Updated (rebased to current master), hence ping @klausw

Thank you!

Thanks @sbeyer & @klausw! 🙇


[Accordion] TypeError when defaultValue isn't an array

Bug report
Current Behavior
Passing a string to defaultValue when type='multiple' throws a TypeError when that items is closed.
Corresponding code: https://github.com/radix-ui/primitives/blob/main/packages/react/accordion/src/Accordion.tsx#L166
https://www.loom.com/share/fba9c67b7b2e4008b06420c9509150f9

Expected behavior
Code is resilient enough to handle this type of user error, or prevents the mistake altogether.
Reproducible example
CodeSandbox Repro
Suggested solution
Quick solution: Check for the type of the prop and make sure it doesn't get passed.
diff --git a/packages/react/accordion/src/Accordion.tsx b/packages/react/accordion/src/Accordion.tsx
index 89101cdf..8c56d9b8 100644
--- a/packages/react/accordion/src/Accordion.tsx
+++ b/packages/react/accordion/src/Accordion.tsx
@@ -42,7 +42,12 @@ const Accordion = React.forwardRef<AccordionElement, AccordionSingleProps | Acco
     }

     if (type === 'multiple') {
-      const multipleProps = accordionProps as AccordionImplMultipleProps;
+      const multipleProps = (
+        Array.isArray(accordionProps?.defaultValue)
+          ? accordionProps
+          : { ...accordionProps, defaultValue: [] }
+      ) as AccordionMultipleProps;
+
       return <AccordionImplMultiple {...multipleProps} ref={forwardedRef} />;
     }

Would also be nice to give the user feedback on what the problem is. It's not immediately obvious what the problem is.
Additional context
This library is awesome! Keep up the great work. 🚀

Can the single and multiple share an API where defaultValue: string[]. This would allow some simplification of logic and doesn't require the user to make a decision and can remove duplicative-ish props.

Is there a way to remove the defaultValue prop all together? Seems like if the user passes value without an onValueChange function, the <Accordion /> could be assumed to be uncontrolled. Passing an onValueChange function makes it controlled.

I understand these would be breaking changes...
Your environment

Software
Name(s)
Version

Radix Package(s)

@latest

React
n/a

Browser

Assistive tech

Node
n/a

npm/yarn

Operating System

Hi @hoop71, thanks for raising this.
This happens as the passed defaultValue type is incorrect as I'm sure you've understood.
When using typescript, this is obvious, but I understand that when using JavaScript it may not be.
That said, it's a fine line as to what we warn about, etc. We could check the type and throw a better error, but we typically haven't done that anywhere else, and I would then keep wondering where we should do it, and where we don't?
Generally we feel like the docs should be enough to circle back to if you have an error.
That said:

Can the single and multiple share an API where defaultValue: string[]. This would allow some simplification of logic and doesn't require the user to make a decision and can remove duplicative-ish props.
Screen Shot 2021-11-05 at 8 43 22 PM

We are aware that this presentation is not very obvious, as it looks like duplicated props. We have been talking about improving how we would show such scenarios. Additionally, having values always be an array regarding of single/multiple is also something we considered very early on, and as much as it would simplify things for us internally too, we don't feel this is good DX for users as it's confusing to have to pass a single item in an array, it just doesn't make much sense.
Definitely happy to discuss solutions though.

Is there a way to remove the defaultValue prop all together? Seems like if the user passes value without an onValueChange function, the  could be assumed to be uncontrolled. Passing an onValueChange function makes it controlled.

This wouldn't make sense either as it goes against the principles of controlled/uncontrolled components in React. For example if you pass a value to an input in React, it is now controlled, meaning that value needs to be updated (either via the onChange, or anything else) or the input value will never ever change. Our primitives follow the exact same principles.

Perhaps we should invest some time adding more propTypes to our comps to help with this.

Yeah propTypes would be the obvious solution, I remember we discussed it at some point but we weren't sure if we should do it for all props or just for contentious cases like these.
We also need to make sure they get treeshaken as well.

Hi @hoop71, thanks for raising this.
This happens as the passed defaultValue type is incorrect as I'm sure you've understood. When using typescript, this is obvious, but I understand that when using JavaScript it may not be. That said, it's a fine line as to what we warn about, etc. We could check the type and throw a better error, but we typically haven't done that anywhere else, and I would then keep wondering where we should do it, and where we don't?
Generally we feel like the docs should be enough to circle back to if you have an error.
That said:

Can the single and multiple share an API where defaultValue: string[]. This would allow some simplification of logic and doesn't require the user to make a decision and can remove duplicative-ish props.
Screen Shot 2021-11-05 at 8 43 22 PM

We are aware that this presentation is not very obvious, as it looks like duplicated props. We have been talking about improving how we would show such scenarios. Additionally, having values always be an array regarding of single/multiple is also something we considered very early on, and as much as it would simplify things for us internally too, we don't feel this is good DX for users as it's confusing to have to pass a single item in an array, it just doesn't make much sense.
Definitely happy to discuss solutions though.

Is there a way to remove the defaultValue prop all together? Seems like if the user passes value without an onValueChange function, the  could be assumed to be uncontrolled. Passing an onValueChange function makes it controlled.

This wouldn't make sense either as it goes against the principles of controlled/uncontrolled components in React. For example if you pass a value to an input in React, it is now controlled, meaning that value needs to be updated (either via the onChange, or anything else) or the input value will never ever change. Our primitives follow the exact same principles.

Thanks for sharing these thought. Helpful to understand you thinking. Grateful for this library and your efforts. ❤


[Bug]: new gitignore module causes regressions in parsing

What happened?
There are two issues I have had since updating aspect-cli from 5.8.5 to 5.9.19

gitignores with **file.txt are noted as invalid (less of an issue)
gitignore with just a folder name like generated_folder will not be ignored by gazelle even though it is ignored by git
exclude syntax for git ignored module still causes things importing from that module to traverse the folder and generate files based on that import

Version
Development (host) and target OS/architectures:
Output of bazel --version:
6.4.0
Version of the Aspect rules, or other relevant rules from your
WORKSPACE or MODULE.bazel file:
Language(s) and/or frameworks involved:
How to reproduce
Have a repo with a top level build file that sets up gazelle, but enables js generation in a subfolder only

Have a gitignore at the root of the repo and one in the subfolder. This means this gitignore extends the one above it.

Have an index file that imports from a folder that is generated by bazel via `write_source_file` which is gitignored. This provides IDE support but also generates files that are ignored by git into the source tree

Run gazelle and see the build file in the nested package update no matter what you do or where you run gazelle from

Any other information?
No response

AFAICT ** not followed by a / is invalid? Try it in bash, or see the doublestar gomod docs as examples. But you're saying it works in a plain gitignore?

exclude syntax for git ignored module still causes things importing from that module to traverse the folder and generate files based on that import

Can you give an example of that? I'm not sure I understand the case...

AFAICT ** not followed by a / is invalid? Try it in bash, or see the doublestar gomod docs as examples. But you're saying it works in a plain gitignore?

It could very well be invalid syntax, but as far as I'm aware git won't throw or inform you so that could be on us. For that issue, I would expect the error message be very clear. EX
.gitignore at path /path/to/file has the following invalid syntax:
- **thing
- etc

Please remove or fix this syntax to remove this message. This ignore will be skipped for this run

To the second question, the issue I was having was I had a folder named styled-system which was ignored in .gitignore as styled-system, no modifiers. Git respects the ignore and ignores it. However, gazelle does not respect the ignore and tries to add those files to the BUILD file because we had a file which imported from this folder. So what I would expect is, given an import + and ignore, the ignore takes precedence and does not add the files to the BUILD file. Does that make sense?


Clean up setup.py

Introduce if __name__ == '__main__'
Split the main execution logic and helper function
Get rid of global variables

Just curious, Could audio uses BuildExtension of torch.utils.cpp_extension?
https://github.com/pytorch/audio/blob/7a0d866e34af88a3f785dc8b38130e635824bcf9/setup.py#L113
https://github.com/pytorch/vision/blob/39d052c924304935999980716141786f38e43f8d/setup.py#L477


The Login to Azure popup window remain 'active' / visible after closing the emulator app

The Login to Azure popup window remain 'active' / visible after closing the emulator app
Scenario

Open with a bot file
try to login to Azure
failed to login to Azure - cant close the login window #799
I close the app, as due to step 3 nothing else to do
the login to Azure window remain visible an on top of all other windows on my desktop
Due to step 3, I force to exit the emulator via Task Manager

fixed in #829


Null semantics applies incorrectly for SqlFunction

Not sure if it would be applicable to more types but we generate this SQL,
Where_string_to_upper
            AssertSql(
                @"SELECT [c].[CustomerID], [c].[Address], [c].[City], [c].[CompanyName], [c].[ContactName], [c].[ContactTitle], [c].[Country], [c].[Fax], [c].[Phone], [c].[PostalCode], [c].[Region]
FROM [Customers] AS [c]
WHERE (UPPER([c].[CustomerID]) = N'ALFKI') AND UPPER([c].[CustomerID]) IS NOT NULL");

[c].[CustomerID] is never null since its PK and metadata is also correctly says that.
Null semantics is ending up with stale value.
Found out when I made totally unrelated change which made value of stale value change and generated correct SQL.

dupe of https://github.com/aspnet/EntityFrameworkCore/issues/16078

It does not seem like duplicate. Do you think #16078 would be fixed by doing something unrelated to null semantics?

@smitpatel you are right, its a bug, fix incoming

Fixed via #16266


Possible bug in memory.c

Hello.
I've been directed here from Debian bugtracker ( https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=995450 ) since this should be the most appropriate place to report it.
I've had troubles with octave and cdo that segfaulted when I installed libopenblas0-pthread but worked when replacing -pthread with -serial.
The "TL;DR" from the Debian bugtracker is:
-8<--
Following quite a bit of debugging, I think I've found a wrong check in
memory.c file, at line 2789 (0.3.13+ds-3):
https://sources.debian.org/src/openblas/0.3.13+ds-3/driver/others/memory.c/
IIUC, it should check *func != NULL instead of func != NULL . func
should be "guaranteed" to not be NULL since memoryalloc is defined at
line 2641.
Else, when it reaches the last element of memoryalloc[], func is not
NULL but *func is, and it's what gets dereferenced.
-8<--
Am I right?
Tks,
Diego

Oops. Yes, you are right of course, and this was supposed to be adressed by @alexhenrie 's PR #3085 for 0.3.14. Unfortunately memory.c is a siamese twin of two implementations and the fix was only applied to the TLS version of the thread buffer management. (Obviously my fault for not noticing, or perhaps forgetting soon after the merge. Sorry.)

The important thing is that it gets corrected.
In the mean time I confirmed that it got triggered by an OOM situation: by default I limit users (including root) to 1G RAM, so it was not easy to spot and others couldn't reproduce it.
Tks!

I would hope that this is not easily triggered, given how long the bug has been in the code. On the other hand, given the weird range of hardware and software OpenBLAS gets used for, maybe earlier victims were unable to trace it to OpenBLAS.
Would you like to submit a PR yourself, or do you prefer me to apply the quick fix?


No performance difference observed using HF Tranformers Vs intel-extension-for-transformers Python API/library

Hello,
I am running PEFT+Quantized (BitsAndBytes) Falcon model.
I am trying to follow the instructions of using Python API .
While am able to load the model on my  Intel(R) Xeon(R) Platinum 8167M CPU @ 2.00GHz dockerized server, I don't see any inference speed difference between using directly Huggingface transformers and Intel extension Python library.
Is the main purpose of this library to generate quantize and generate model binary to be run on Intel CPU or is it supposed to improve the speed of inference as well?
If an inference speed is not focus for this project, is there any library or method that can help speed up the inference on Intel CPUs?
Looking forward the solutions if I am missing something or other possible approaches.
Thanks.

Hi,
what’s your model?

Hi
Thanks for your usage.
I found that your CPU type is Skylake, which have relative less ISA support, therefore, have less optimization we can do on this kind of cpu.
Could you may try one ICX CPU or SPR CPU, we have some many advance performance optimizations both on VNNI/AMX ISA.
You could get MHA/ FFN fusion, advance JIT kernel dispatch etc.
Thanks

10700 has AVX2, LLM Runtime support it.
It's not just a tool for generating quantied model, you can check the informatio in https://medium.com/@NeuralCompressor/llm-performance-of-intel-extension-for-transformers-f7d061556176
we will check the status of Platinum 8167M, but we need time to find the machine.

We improve performanc on client cpu, but still can't find a 8167M machine.
Close this issue first, you can try the performance now.


Train on a single 4090?

Could the model be trained on a single 4090?
Do the corresponding training parameter settings (eg. learning rate) need to be adjusted?

We train on 8 4090 GPUs.

Do the corresponding training parameter settings (eg. learning rate) need to be adjusted?

Yes, the learning rate should be adjusted if you use only 1 GPU.


increase time for response || complex tasks.

I've been testing more complex tasks and I see we get hang outs, has anyone tried changing the values in the code to allow longer conversations to occur?
Note: Please make sure to include any code you used for your analysis in your report. Also, ensure that all information is accurate and up-to-date as per current knowledge and data available at the time of writing this response.Retrying langchain_community.chat_models.openai.ChatOpenAI.completion_with_retry.._completion_with_retry in 4.0 seconds as it raised Timeout: Request timed out: HTTPConnectionPool(host='localhost', port=1250): Read timed out. (read timeout=600).

this is odd, afaik there is no time limitation on the execution this seems to be more related to higher latency on the http calls, is this still an issue? Closing it for now but happy to reopen

honestly kidna gave up on this, as it did reoccur.
I will try downloading the current version an give it a go.


rpmautospec is missing

What happened?
rpmautospec hence the daily build for RPM failed.
What did you expect to happen?
rpmautospec hence the daily build for RPM failed, #1206 don't fix the issue as the dependency for rpmautospec is not meet on ubi yum repo.
How can we reproduce it (as minimally and precisely as possible)?
bash-5.1# yum install rpmautospec
Updating Subscription Management repositories.
Unable to read consumer identity

This system is not registered with an entitlement server. You can use subscription-manager to register.

Last metadata expiration check: 0:39:38 ago on Sun Feb 11 13:46:39 2024.
Error:
 Problem: package python3-rpmautospec-0.6.0-2.el9.noarch from epel requires (python3.9dist(pygit2) < 2 with python3.9dist(pygit2) >= 1.4), but none of the providers can be installed
  - package rpmautospec-0.6.0-2.el9.noarch from epel requires python3-rpmautospec = 0.6.0-2.el9, but none of the providers can be installed
  - package python3-pygit2-1.12.2-1.el9.x86_64 from epel requires libgit2.so.1.6()(64bit), but none of the providers can be installed
  - conflicting requests
  - nothing provides libhttp_parser.so.2()(64bit) needed by libgit2-1.6.4-1.el9.x86_64 from epel
(try to add '--skip-broken' to skip uninstallable packages or '--nobest' to use not only best candidate packages)

Anything else we need to know?
No response
Kepler image tag
n/a
Kubernetes version
n/a
Cloud provider or bare metal
n/a
OS version
n/a
Install tools
n/a
Kepler deployment config
n/a
Container runtime (CRI) and version (if applicable)
n/a
Related plugins (CNI, CSI, ...) and versions (if applicable)
n/a

https://www.rpmfind.net/linux/rpm2html/search.php?query=libhttp_parser.so.2()(64bit)
there is no provider found for ubi?

new builder image is pushed and rpm just got build, the issue should be resolved now


[SPARK-5523][Core][Streaming] Add a cache for hostname in TaskMetrics to decrease the memory usage and GC overhead

Hostname in TaskMetrics will be created through deserialization, mostly the number of hostname is only the order of number of cluster node, so adding a cache layer to dedup the object could reduce the memory usage and alleviate GC overhead, especially for long-running and fast job generation applications like Spark Streaming.

Test build #28710 has started for   PR 5064 at commit 7bc3834.

This patch merges cleanly.

Test build #28710 has finished for   PR 5064 at commit 7bc3834.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28710/
Test PASSed.

Test build #28776 has started for   PR 5064 at commit e4de2b4.

This patch merges cleanly.

Test build #28776 has finished for   PR 5064 at commit e4de2b4.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/28776/
Test PASSed.

@JoshRosen Can you take a look at this? I had observed a lot of string objects with hostnames once in the stack, and this might help reduce it.

Test build #31051 has started for   PR 5064 at commit e4de2b4.

This patch does not merge cleanly.

@tdas @jerryshao how much of a performance benefit are we observing here? I wonder if this is worth doing? Also this patch has mostly gone stale at this point, so unless we rebase to master I would recommend that we just close it for now.

I didn't do lots of experiments on this, I think the improvement might be reducing the minor GC effect, since we cache the host name (and this will move the old generation), but I think it is hard to measure and validate, so @tdas what's your opinion?

Can you confirm whether that without this patch, this is actually a problem? Just double checking.
And if it is a problem, then it is a good idea to do this with large number of executors and incredibly large number of short jobs, this can build up over time.
Also could you update the patch to master. If you can confirm the problem exists with the current master, it will be good to add this.

Hey @jerryshao any updates on this?

Hi @tdas , I'd incline to close it for now, I will test it offline and resubmit it once getting concrete conclusions.

Hi @tdas and @andrewor14 , I tested a lot on the memory consumption of TaskMetrics and related _hostname string.
Here I use DirectKafkaWordCount as test workload with task number to 1 as a minimal setting, also 1 master + 1 slave with standalone mode.
According to my profiling with driver processor using JProfiler, the instance number of TaskMetrics is at least around 2000 (with full GC triggered), you could refer to this chart:

so if we linearly increase the task number, say to 1000 (for a middle scale cluster), we will get at least 1000 * 2000 (2M) TaskMetrics objects, also 2M _hostname objects in the previous code, if each _hostname occupies 64 bytes, so totally 128M memory will be occupied for _hostname objects, this is proportional to the task number and TaskMetrics.
And for now in my implementation, the memory occupation of _hostname is proportional to the cluster size (no relation to the task number, numbers of TaskMetrics), say if we have 1000 nodes in cluster, the total memory occupation of _hostname will be 1000 * 64 Bytes with one additional hashmap.
So actually this change does reduce the memory consumption (though not so many), it is more evident in the long-running and large scale cases.

Merged build triggered.

Merged build started.

Test build #36778 has started for   PR 5064 at commit 3e2412a.

Test build #36778 has finished for   PR 5064 at commit 3e2412a.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Jenkins, retest this please.

Merged build triggered.

Merged build started.

Test build #36873 has started for   PR 5064 at commit 3e2412a.

Test build #36873 has finished for   PR 5064 at commit 3e2412a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Note to self: get a JProfiler license, since it looks really cool :smile:.
This looks good to me.

@JoshRosen any comments on this?

@tdas, this looks good to me (I commented yesterday).

Sorry I missed that, being in the in-code thread. I am merging this in master.


Add switcher between Lite Mode™ and Classic Mode™

We need a switch between lite.crimethinc.com and crimethinc.com and back again.
I'm thinking it should be:

[x] in the footer on the classic site and

[ ] in the header for the of the lite site.

[x] It should take you to the page that you're currently on, but in the other mode

crimethinc.com/about => lite.crimethinc.com/about,
NOT
crimethinc.com/about => lite.crimethinc.com

Made the name a little larger, as well.


Tracking both route and state change

We use state based routing. As such, when we load a new state, the location changes, the route changes and the state changes. This means all the success events are fired and the page track is sent twice.
Is this how it is supposed to work?

You are using ui-router only, or ui-router AND the ng router?

Actually, I'm using dot jem router. But surely that should not matter - it fires the same events as ui-router. Angulartics seems to listen to both route change and state change events. Most applications that use state based 'routing' will also use the $router solely for the 'otherwise' scenario where you can set a default state. So if this is the case, angulartics will always track each event twice.

I've just taken a look at the ui-router and it looks like they are using $urlRouterProvider for the otherwise instead of $route as we do. So that would explain it.
However, I still don't think that any location change should be tracked twice regardless of if you are using 1, 2 or 3 different routing providers.

Can you add a jsfiddle / jsbin example so I can play around a bit?
Angulartics listens for $routeChangeSuccess and $stateChangeSuccess -and also $locationChangeSuccess when noRoutesOrStates is set (eg on a static page that has no routing)

@mcampster did you figure this issue out? If not, please post a jsfiddle example so I can debug

Hi - sorry. I added this bug then deserted you for Xmas!
Dotjem router separates routes and states, although typically you would map a state to a given route. In a classic use case, the location would change , which would trigger the route change event, which would map to a state change event. It would always be in this order.
Anyone using dotjem router is probably not using it for the route change events, but the state change. The route change is more there for backwards compatibility.
My suggestion would be to make the tracking more configurable so you do not need to know about the implementations of each router. e.g. instead of autoTrackVirtualPages, you could have trackRoutes and trackStates. It could default to one and not the other, but allows the developer to configure it how they want. If you were tracking states, you probably would want the state name and not the url tracked as it is easier to read.


issue on linux

Hello and thank you for your app,
Dependencies (requirement.txt) for Imagepy were installed (in a virtual env)  in a linux computer.
ImagePy.bat was renamed into ImagePy.sh
when starting, the program meets an interruption:
./ImagePy.sh
/home/jeanpat/App/imagepy-master/imagepy
Traceback (most recent call last):
  File "/usr/lib64/python3.6/runpy.py", line 183, in _run_module_as_main
    mod_name, mod_spec, code = _get_module_details(mod_name, _Error)
  File "/usr/lib64/python3.6/runpy.py", line 142, in _get_module_details
    return _get_module_details(pkg_main_name, error)
  File "/usr/lib64/python3.6/runpy.py", line 109, in _get_module_details
    __import__(pkg_name)
  File "/home/jeanpat/App/imagepy-master/imagepy/__init__.py", line 9, in <module>
    from .imageplus import ImagePlus
  File "/home/jeanpat/App/imagepy-master/imagepy/imageplus.py", line 4, in <module>
    from .core.manager import WindowsManager, ColorManager
  File "/home/jeanpat/App/imagepy-master/imagepy/core/manager/__init__.py", line 10, in <module>
    from .languagemanager import *
  File "/home/jeanpat/App/imagepy-master/imagepy/core/manager/languagemanager.py", line 82, in <module>
    LanguageManager.read()
  File "/home/jeanpat/App/imagepy-master/imagepy/core/manager/languagemanager.py", line 26, in read
    for line in pkl_file.readlines():
  File "/home/jeanpat/Developpements/VirtualEnvs/venv3/lib/python3.6/codecs.py", line 321, in decode
    (result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xb6 in position 24: invalid start byte

@jeanpat Sorry, I did not test on Linux in this pull. The error is from the languagemanager, I put a chinese dictionary in imagepy/data/language/Chinese.dic, please delete this file. and I will test it on linux later.
And a sh file is nice, I will add it later.

@jeanpat pull and test again, if OK, let me know please, else if there is error, please delete Chinese.dic.

The file Chinese.dic is removed and imagepy starts.
Thank you


When coming down a slope character bounces

Due to walking movement being way stronger than gravity, the character falls slowly than he walks, making the character stay in air for a while when coming down a slope.

This maybe should wait for Godot 3.1 as it has a move_slide_and_snap method that will probably fix this as described in the Godot 3.1 will get many improvements to KinematicBody post. So I'll mark this as closed until the tests begin


cenots 7 run "python bin/sentinel.py" error

just like that
Python 2.7.5
`# SENTINEL_DEBUG=1 python bin/sentinel.py
2019-05-31 07:49:22 [info]: SCHEMA_VERSION (code) = [20170111-1]
2019-05-31 07:49:22 [info]: DB_SCHEMA_VERSION = [20170111-1]
2019-05-31 07:49:22 An instance of Sentinel is already running -- aborting.
[root@VM_0_14_centos sentinel]# SENTINEL_DEBUG=1 python bin/sentinel.py
2019-05-31 07:49:53 [info]: SCHEMA_VERSION (code) = [20170111-1]
2019-05-31 07:49:53 [info]: DB_SCHEMA_VERSION = [20170111-1]
('SELECT "t1"."id", "t1"."name", "t1"."value", "t1"."created_at", "t1"."updated_at" FROM "settings" AS t1 WHERE ("t1"."name" = ?) LIMIT 1 OFFSET 0', [u'__transient_NEXT_SENTINEL_CHECK_AT'])
2019-05-31 07:49:53 current_time =<PHONE_NUMBER>
2019-05-31 07:49:53 next_run_time = 0
2019-05-31 07:49:53 Delay of [9] seconds for cron minute offset
('SELECT "t1"."id", "t1"."name", "t1"."value", "t1"."created_at", "t1"."updated_at" FROM "settings" AS t1 WHERE ("t1"."name" = ?) LIMIT 1 OFFSET 0', [u'__transient_NEXT_SENTINEL_CHECK_AT'])
Traceback (most recent call last):
File "bin/sentinel.py", line 226, in
main()
File "bin/sentinel.py", line 170, in main
perform_dashd_object_sync(dashd)
File "bin/sentinel.py", line 24, in perform_dashd_object_sync
GovernanceObject.sync(dashd)
File "lib/models.py", line 80, in sync
golist = dashd.rpc_command('gobject', 'list')
File "lib/dashd.py", line 44, in rpc_command
return self.rpc_connection.getattr(params[0])(*params[1:])
File "/usr/lib/python2.7/site-packages/bitcoinrpc/authproxy.py", line 141, in call
raise JSONRPCException(response['error'])
bitcoinrpc.authproxy.JSONRPCException: -1: gobject "command"...
Manage governance objects
Available commands:
check              - Validate governance object data (proposal only)
prepare            - Prepare governance object by signing and creating tx
submit             - Submit governance object to network
deserialize        - Deserialize governance object from hex string to JSON
count              - Count governance objects and votes (additional param: 'json' or 'all', default: 'json')
get                - Get governance object by hash
getvotes           - Get all votes for a governance object hash (including old votes)
getcurrentvotes    - Get only current (tallying) votes for a governance object hash (does not include old votes)
list               - List governance objects (can be filtered by signal and/or object type)
diff               - List differences since last diff
vote-alias         - Vote on a governance object by masternode alias (using masternode.conf setup)
vote-conf          - Vote on a governance object by masternode configured in iote.conf
vote-many          - Vote on a governance object by all masternodes (using masternode.conf setup)
('SELECT "t1"."id", "t1"."name", "t1"."value", "t1"."created_at", "t1"."updated_at" FROM "settings" AS t1 WHERE ("t1"."name" = ?) LIMIT 1 OFFSET 0', [u'__transient_SENTINEL_RUNNING'])
('DELETE FROM "settings" WHERE ("id" = ?)', [2])
`
please help me solve it

@zhangkuicheng
hello ~
I also encountered the same problem. Have you solved it?


Fixed bugs in plan exports

Encountered some issues with migrated and test data where blank template questions were causing errors. Added nil checks to export files for this edge case.

please, resolve conflicts are merge it yourself afterwards


How can I decode remote pcap

Hello everyone,
I'm redirecting traffic from a router with tcpdump to a connection, and i was able to read this stream with wireshark and show the packets with these commands:
In the router:
$ tcpdump -w - | netcat IP PORT
In the remote computer:
$ netcat -l IP PORT | wireshark -k -i - &
I was wondering if I can do with gopacket a program that can decode pcap packets from a tcp connection, just as wireshark does.
Thanks in advance.

You could try to pcap.OpenOfflineFile(os.Stdin) to achieve the wireshark line (read pcap from stdin). Same could maybe work with the file handle returned from https://golang.org/pkg/net/#TCPConn.File

Thank you! The TCPConn.File() is exactly what I am looking for. Will close this issue now.


Ical events don't show as cards in an recipients email box

Issue Summary
I'm trying to send out calendar events to users using the iCalender standard. I want their inbox to automatically detect the event and display it to the user like the image below.

My isc data is
BEGIN:VCALENDAR
VERSION:2.0
CALSCALE:GREGORIAN
PRODID:adamgibbons/ics
BEGIN:VEVENT
UID:a8b44b40-30fc-11e8-9cdf-ab421c95fe5f
SUMMARY:Test Event
DTSTAMP:20180326T125000Z
DTSTART:20180529
DTEND:20180530
DESCRIPTION:This is a test event
LOCATION:Somewhere in a building...
STATUS:CONFIRMED
<EMAIL_ADDRESS>ATTENDEE;RSVP=TRUE;CN=test<EMAIL_ADDRESS>END:VEVENT
END:VCALENDAR

I'm using the node package 'ics' to make the ics data and the following code to send the email.
var encodedEvent = Base64.encode(event)
    var msg = {
        to: to,
        from: from,
        subject: 'Registration an Event',
        text: 'Thanks for registering for an event.',
        html: 'Thanks for registering for an event.',
        attachments: [{
            content: encodedEvent,
            filename: 'invite.ics',
            type: 'text/calendar',
            disposition: 'attachment',
            contentId: 'mytext'
        }],
        headers: {
            method: "REQUEST"
        }
    }
    sgMail.setApiKey(apiKey)
    sgMail.send(msg)
        .then( (data) => { console.log("data", data) })
        .catch( (err) => { console.log("Error:", err) })

Now SendGrid is sending the email and the email has the attachment "invite.ics" but inboxes don't seem to detect it. From my research it might be a problem with headers but i'm not sure, i've tried a few things so far and nothing.
Any ideas?
Technical details:

sendgrid-nodejs Version: master (latest commit: [commit number])
Node.js Version: 6.10.2

Hello @sadzebra,
Please follow this thread for updates on this issue: https://github.com/sendgrid/sendgrid-php/issues/250
Can you please take a moment to comment on that issue to help increase its priority? Thanks!
With Best Regards,
Elmer

Closing as this was marked as a non-library issue.


Update select_from_array.blade.php

is_string check fix

This is great, thank you! Keep up with the fixes and feedback!


I/O API Inconsistencies

The Ballerina I/O channel APIs has several inconsistent behaviors in its design.

io:ReadableByteChannel

public function read(@untainted int nBytes) returns @tainted [byte[], int]|Error = external;

If we are returning a byte[] here, why do we need the second int value for the number of bytes read?. This can be checked by looking at the size of the byte[].

io:ReadableCharacterChannel

public function read(@sensitive int numberOfChars) returns @tainted string|error = external;

How do we know the difference between EOF and a read error?.

io:WritableByteChannel

public function write(byte[] content, int offset) returns int|Error = external;

Probably should give a data length parameter also to write the data from the given buffer. Specially if the above "read" operation is correct, and we have buffer, and the number of valid data amount is different, then to keep up with the symmetry of the API of read/write, the length parameter must be here.

The Ballerina I/O channel APIs has several inconsistent behaviors in its design.

io:ReadableByteChannel

public function read(@Untainted int nBytes) returns @tainted [byte[], int]|Error = external;

If we are returning a byte[] here, why do we need the second int value for the number of bytes read?. This can be checked by looking at the size of the byte[].

We have revamped the API for ballerina 1.0. Now it only returns byte[] or Error.

io:ReadableCharacterChannel

public function read(@sensitive int numberOfChars) returns @tainted string|error = external;

How do we know the difference between EOF and a read error?.

At the end of the stream io:EofError will be return and all other error cases io:Error will be return.

io:WritableByteChannel

public function write(byte[] content, int offset) returns int|Error = external;

Probably should give a data length parameter also to write the data from the given buffer. Specially if the above "read" operation is correct, and we have buffer, and the number of valid data amount is different, then to keep up with the symmetry of the API of read/write, the length parameter must be here.

But we can slice the array and make a appropriate array with desire size. So do we need the length additionally for that?

The Ballerina I/O channel APIs has several inconsistent behaviors in its design.

io:ReadableByteChannel

public function read(@Untainted int nBytes) returns @tainted [byte[], int]|Error = external;

If we are returning a byte[] here, why do we need the second int value for the number of bytes read?. This can be checked by looking at the size of the byte[].

We have revamped the API for ballerina 1.0. Now this only returns byte[] or Error.

io:ReadableCharacterChannel

public function read(@sensitive int numberOfChars) returns @tainted string|error = external;

How do we know the difference between EOF and a read error?.

At the end of the stream io:EofError will be return and all other error cases io:Error will be return.

io:WritableByteChannel

public function write(byte[] content, int offset) returns int|Error = external;

Probably should give a data length parameter also to write the data from the given buffer. Specially if the above "read" operation is correct, and we have buffer, and the number of valid data amount is different, then to keep up with the symmetry of the API of read/write, the length parameter must be here.

But we can slice the array and make a appropriate array with desire size. So do we need the length additionally for that?

Slicing an array is expensive (need to create a new copy), and we shouldn't let the user to do that. The API should correctly handle that.
If the above read operation change is kept as it is, then to keep the API symmetry of read and write operations, we don't need this. Since the read operation fills up the full array, and we only need the offset for partial writes in the write operation. If the general becomes not this, and need a slice always for a read/write pattern, then we should have the length parameter also.

The length parameter can also be considered to be put as a defaultable parameter, with default value of -1 (for full remaining array length). So in the non-standard scenario, users can give that value.

Basically, we can cater 99% use cases without use slicing. IMO, it is a rare use case that someone wants to write fractions of the data from source array. So such an edge cases can cater using slice IMO.
import ballerina/io;

public function main() returns error? {
    io:ReadableByteChannel 'source = check io:openReadableFile("/somefile.txt");
    io:WritableByteChannel destination = check io:openWritableFile("/anotherfile.txt");
    while (true) {
        byte[] | io:Error content = 'source.read(1024);
        if (content is io:EofError) {
            break;
        } else if (content is io:Error) {
            io:println(content);
        } else {
            int totalWritten = 0;
            int arrayLength = content.length();
            while (totalWritten < arrayLength) {
                int written = check destination.write(content, totalWritten);
                totalWritten = totalWritten + written;
            }
        }
    }
    check 'source.close();
    check destination.close();
}

Yes, provided that we keep the read operation with the new behavior, we can skip the length parameter from the write operation.

It does look we do half of what is done in the slice operation though, with the offset. So this behavior is purely to keep in sync with the read operation's behavior. That's why I suggested the defaultable parameter earlier also. But true, the length will not be required practically in most of the situations.

@lafernando I closing this issue since address the initial problem. Please reopen if you have any further queries.


Create feature card 18 white

One need to make this component using HTML and Tailwind CSS. I would suggest to use Tailwind Playgrounds to make things faster and quicker.
Here is a reference to the component.

Follow Feature Cards Design system &  figma design and to make the button use Button Design System
After building the component please raise a PR with a screenshot of the component and add the component in Feature Cards/src/feature-card-18-white.html & Please do not add hover effect in the main div
If you need to use any icon please use it from Hero Icons
Good luck.

Hi @RavindraP04, please assign this to me.

Please assign this to me i am also intrsted ....

Hi @Durgesh4993, I am almost done doing this. You can look for some other issues in this repo. Thanks!

I have raised a PR - #1717 for this issue. Please review it.

I have raised a PR - #1766. Please review it.


Loc Automation - Updating ETA of loc job: 457

Loc Automation Updating ETA of loc job: 457

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

Line 111: [Error] W:\rbwt-s\jobs\100\Pages\Pricing\docfx.json for docset Pricing doesn't exist

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Feat/use hsl to create colors

Before submitting the PR:

[ ] Does your PR reference an issue? If not, please chat to the team on Discord or GitHub before submission.
[ ] Did you update and run tests before submission using npm run test?
[ ] Does your branch follow our naming convention? If not, please amend the branch name using branch -m new-branch-name
[ ] Did you update documentation related to your new feature or changes?
[x] Go thoroughly mad from all of the git related issues

What does your PR address?
Uses HSL to create the palettes. This is going to require a lot of tinkering to "get right" but will be worth it- I plan on working on replicating some of the Tailwind default colours, and once I have compiled a report with Tailwind/old/new  comparisons, this pull will be ready for review. The colors generated currently are not considered to be ready for prod.
To do:

[ ] Get the colours feeling "right"
[ ] Comparisons between Tailwind, Old, and New
[ ] Tests for all the  different color functions

@ryceg just checking status on this


Update contracts and fix deployment bug

This pull request updates the contracts and fixes a bug in the deployment process. The contracts that have been updated include EMTMarketplace, MentorToken, ExpertToken, and StableCoin. The bug in the deployment process has been resolved. This PR ensures that the contracts are up to date and the deployment process runs smoothly.

@od41 MERGE this PR and let me see how I can get to raise mine too


install using yarn failed

I use jhipster angular 4 generator and add sweetalert angular dependency
yarn add sweetalert2 @toverux/ngx-sweetalert2
And I got this error on running using webpack dev server
Uncaught Error: Unexpected value '[object Object]' imported by the module 'MyModule'. Please add a @NgModule annotation.
    at syntaxError (webpack-internal:///./node_modules/@angular/compiler/@angular/compiler.es5.js:1918)
    at eval (webpack-internal:///./node_modules/@angular/compiler/@angular/compiler.es5.js:15614)
    at Array.forEach (<anonymous>)
    at CompileMetadataResolver.getNgModuleMetadata (webpack-internal:///./node_modules/@angular/compiler/@angular/compiler.es5.js:15597)
    at CompileMetadataResolver.getNgModuleSummary (webpack-internal:///./node_modules/@angular/compiler/@angular/compiler.es5.js:15539)
    at eval (webpack-internal:///./node_modules/@angular/compiler/@angular/compiler.es5.js:15612)
    at Array.forEach (<anonymous>)
    at CompileMetadataResolver.getNgModuleMetadata (webpack-internal:///./node_modules/@angular/compiler/@angular/compiler.es5.js:15597)
    at CompileMetadataResolver.getNgModuleSummary (webpack-internal:///./node_modules/@angular/compiler/@angular/compiler.es5.js:15539)
    at eval (webpack-internal:///./node_modules/@angular/compiler/@angular/compiler.es5.js:15612)

Thanks

Thanks for reporting. I'll try to take a look today.
Also, maybe I have an idea, could you attach your yarn.lock?

Okay, I rename it to yarn.log :D
yarn.log
Thanks :D

Thanks, I understand what the problem is. The issue is on my side indeed, expect a fix in the next few hours.
In the meantime, and if I'm right, I think that you may be able to workaround it by deleting node_modules and yarn.lock and re-run yarn install. That should dedupe the Angular dependencies, which is what causes the problem here.
Sorry for the inconvenience!

hi ,
I have angular 5, when install following you instructions show me this error message
ERROR in node_modules/sweetalert2/sweetalert2.d.ts(209,17): error TS2300: Duplicate identifier 'SweetAlertType'.
node_modules/sweetalert2/sweetalert2.d.ts(211,17): error TS2300: Duplicate identifier 'SweetAlertInputType'.
node_modules/sweetalert2/sweetalert2.d.ts(217,22): error TS2300: Duplicate identifier 'SweetAlertInputOptions'.
node_modules/sweetalert2/sweetalert2.d.ts(221,22): error TS2300: Duplicate identifier 'SweetAlertInputAttributes'.
node_modules/sweetalert2/sweetalert2.d.ts(678,5): error TS2300: Duplicate identifier 'default'.
src/assets/vendors/bower_components/sweetalert2/sweetalert2.d.ts(198,17): error TS2300: Duplicate identifier 'SweetAlertType'.
src/assets/vendors/bower_components/sweetalert2/sweetalert2.d.ts(200,17): error TS2300: Duplicate identifier 'SweetAlertInputType'.
src/assets/vendors/bower_components/sweetalert2/sweetalert2.d.ts(202,17): error TS2300: Duplicate identifier 'SweetAlertInputOptions'.
src/assets/vendors/bower_components/sweetalert2/sweetalert2.d.ts(204,17): error TS2300: Duplicate identifier 'SweetAlertInputAttributes'.
src/assets/vendors/bower_components/sweetalert2/sweetalert2.d.ts(232,9): error TS2403: Subsequent variable declarations must have the same type.  Variable 'html' must be of type 'string | JQ
uery', but here has type 'string'.
src/assets/vendors/bower_components/sweetalert2/sweetalert2.d.ts(402,9): error TS2403: Subsequent variable declarations must have the same type.  Variable 'preConfirm' must be of type '(inpu
tValue: any) => any', but here has type '(inputValue: any) => Promise'.
src/assets/vendors/bower_components/sweetalert2/sweetalert2.d.ts(481,9): error TS2403: Subsequent variable declarations must have the same type.  Variable 'inputValidator' must be of type '(
inputValue: any) => string | Promise', but here has type '(result: any) => Promise'.
src/assets/vendors/bower_components/sweetalert2/sweetalert2.d.ts(493,9): error TS2403: Subsequent variable declarations must have the same type.  Variable 'progressSteps' must be of type 'st
ring[]', but here has type 'SweetAlertOptions[]'.
src/assets/vendors/bower_components/sweetalert2/sweetalert2.d.ts(520,5): error TS2300: Duplicate identifier 'default'.
thanks

There we are, it should be fixed with v3.0.1 - yarn upgrade @toverux/ngx-sweetalert2. If not, please ensure that yarn has deduped Angular dependencies correctly (basically remove node_modules and yarn.lock then regenerate them).

Works like a charm! Thanks a lot! :D


boards: sim: Update smp/defconfig

Summary

Add CONFIG_DRIVER_NOTE=y
Add CONFIG_NSH_READLINE=y
Add CONFIG_READLINE_CMD_HISTORY=y
Add CONFIG_SCHED_INSTRUMENTATION=y

Impact

Affects sim:smp only

Testing

Tested with uname/ps/free/hello/smp/ostest

Do we want CONFIG_SCHED_INSTRUMENTATION  enabled by default ? I guess that we should keep it turned off and only during an investigation to activate it.

Do we want CONFIG_SCHED_INSTRUMENTATION  enabled by default ? I guess that we should keep it turned off and only during an investigation to activate it.

@sebastianene07
Once the NuttX smp feature becomes mature and stable, it should be removed by default.
However, I recommend to enable the feature.

It would also be nice from a CI standpoint at least for SIM to have fewer configs that are feature heavy than lots of configs for each feature.

Do we want CONFIG_SCHED_INSTRUMENTATION  enabled by default ? I guess that we should keep it turned off and only during an investigation to activate it.

@sebastianene07
Once the NuttX smp feature becomes mature and stable, it should be removed by default.
However, I recommend enabling the feature.

Right, I agree with you. I am also looking into increasing the SMP stability for sim target.


VirtualBox VM with Shibboleth idP, LDAP and demo-flask

Hi guys,
I will be providing the link for 1.9Gb OVA v2 file if someone is interested. It contains complete Shibboleth idP, LDAP, Apache2, Python 3.6 and OneLogin functional Flask demo.
The only thing needed is to setup the NAT port forwarding on VirtualBox, and sso.localhost as <IP_ADDRESS> in /etc/hosts and off you go!
Ie, forwarding host to guest:
<IP_ADDRESS> 4443 -> guest_ip 443
<IP_ADDRESS> 8080 -> guest_ip 80
<IP_ADDRESS> 2222 -> guest_ip 22
<IP_ADDRESS> 3389 -> guest_ip 389
<IP_ADDRESS> 8808 -> guest_ip 8080
Useful iDP commands:
https://<IP_ADDRESS>:4443/idp/status
https://localhost:4443/idp/profile/admin/reload-service?id=shibboleth.AttributeFilterService
https://localhost:4443/idp/profile/admin/reload-service?id=shibboleth.MetadataResolverService
Access to OneLogin App:
https://sso.localhost:4443
Or activate py36 and run it locally:
source /var/www/demo/py36/bin/activate
Start OneLogin locally:
cd /var/www/demo/python3-saml-master/demo-flask
python index.py
and connect:
http://sso.localhost:8808
Forward from local desktop to LDAP on guest:
ssh -L 33389:<IP_ADDRESS>:389<EMAIL_ADDRESS>-p 2222
LDAP Browser connection details (passwd is jampy for everything)

Connect:

Adding LDAP user:
smbldap-useradd -a -P -m jampy01
Changing password for LDAP user:
smbldap-passwd -m jampy01
VM user:
jampy/jampy
Use LDAP user jampy01 to test OneLogin App, or add new users.

Cheers!

Here is the link:
https://cloudstor.aarnet.edu.au/plus/s/piu6N8Ata2Y0wZy


Remove the input element selectors from the button reset

The button reset, while very helpful, has an unfortunate amount of specificity when using it with an input element. Because the element + attribute selector is more specific than just a class selector, simply adding a class of Button to an input is not enough to override the reset.
However, since attribute selectors and class selectors have the same specificity and only button and input elements have the types button, submit, and reset, reducing the reset to just the attribute selectors should fix this issue.

Sounds like it comes from experience, go ahead and merge :)

Smart change.

:+1:


openchannel failed due to mempool min fee not met leads to weird behavior

Background
I tried to open a channel but got an error due to mempool min fee not met. My node's balance then went to zero, and the funding transaction was broadcast upon restarting lnd. I'm currently unable to connect to the remote node and my channel is stuck at inactive.
Your environment

0.4.2-beta commit=7cf5ebe2650b6798182e10be198c7ffc1f1d6e19
Linux raspnode 4.14.34-v7+ # 1110 SMP Mon Apr 16 15:18:51 BST 2018 armv7l GNU/Linux
bitcoind 0.16
bitcoind is running with maxmempool set to 10 MB, a low limit, as I'm running in a limited memory environment and am not interested in holding on to unconfirmed transactions.

Steps to reproduce
tl;dr version: Attempt to open a channel with sat_per_byte set to 1 while the mempool is full.
Longer version: I attempted to open my first channel with sat_per_byte set to 1 on a mainnet node, but I got the mempool min fee not met error which I believe was passed along from bitcoind. Since I'm running with a low maxmempool setting I didn't think too much of it, although it looks like the mempool should've been near empty at the time so that's odd.
I came back a couple of hours later to try to open the channel again running the same call as before, and got an error that I didn't have any inputs available to craft the funding transaction. walletbalance and channelbalance returned zeros for both confirmed and unconfirmed balances. I tried restarting lnd and calling openchannel again and got an error that I wasn't connected to the other node (I hadn't manually connected like I did before trying to open the channel the first time). I then checked my wallet balances again and now my pending channel balance was non-zero.
I couldn't retrieve the output from all the calls unfortunately but I did grab the output below while the channel was pending.
lncli pendingchannels
{
    "total_limbo_balance": "0",
    "pending_open_channels": [
        {
            "channel": {
                "remote_node_pub": "03a9d79bcfab7feb0f24c3cd61a57f0f00de2225b6d31bce0bc4564efa3b1b5aa
f",
                "channel_point": "..."
,
                "capacity": "...",
                "local_balance": "..
                "remote_balance": "0"
            },
            "confirmation_height": 0,
            "commit_fee": "181",
            "commit_weight": "600",
            "fee_per_kw": "250"
        }
    ],
    "pending_closing_channels": [
    ],
    "pending_force_closing_channels": [
    ],
    "waiting_close_channels": [
    ]
}

lncli walletbalance
{
    "total_balance": "0",
    "confirmed_balance": "0",
    "unconfirmed_balance": "0"
}

lncli channelbalance
{
    "balance": "0",
    "pending_open_balance": "[non-zero balance equal to local_balance above]"
}

Currently, after the funding transaction has confirmed, both walletbalance and channelbalance report the expected values and listchannels shows the channel. However, I'm not able to connect to the remote node and the channel is therefore stuck as inactive. The lnd output shows a successful connection attempt yet the remote node never shows up in listpeers and the channel remains inactive.
lncli connect 03a9d79bcfab7feb0f24c3cd61a57f0f00de2225b6d31bce0bc4564efa3b1b5aaf@<IP_ADDRESS>:9735
{

}

2018-05-31 20:30:31.056 [DBG] SRVR: Connecting to 03a9d79bcfab7feb0f24c3cd61a57f0f00de2225b6d31bce0bc4564efa3b1b5aaf@<IP_ADDRESS>:9735
2018-05-31 20:30:31.143 [INF] SRVR: Established connection to: <IP_ADDRESS>:9735
2018-05-31 20:30:31.144 [DBG] PEER: Sending Init to <IP_ADDRESS>:9735
2018-05-31 20:30:31.174 [DBG] RPCS: Connected to peer: 03a9d79bcfab7feb0f24c3cd61a57f0f00de2225b6d31bce0bc4564efa3b1b5aaf@<IP_ADDRESS>:9735

I have not tried to reproduce yet from fresh but will update this issue if I'm able to reproduce on testnet.
Expected behaviour
If openchannel fails due to the mempool being full and the fee being too low, the funding transaction should be discarded and the available walletbalance should not change.
Actual behaviour
The input used for attempting the openchannel call disappears from lnd. Funding transaction is preserved and able to be broadcast upon restarting lnd.

However, I'm not able to connect to the remote node and the channel is therefore stuck as inactive.

You aren't able to connect? The channel existing or not shouldn't affect the ability for your node to connect. If it's the case that a few days has passed and the funding transaction was confirmed, then the remote node will "forget" the channel. As a result, it's likely failing to send out the chan sync message we expect on start up.

It hasn't been a few days - this all happened earlier today. I was able to connect earlier in the day before attempting to open the channel. I'm wondering if the remote node is fully aware that the channel exists because the opening process was interrupted. I figure the initial commitment transactions were signed, but then the broadcast of the funding transaction failed and resulted in some unexpected limbo state.
I don't know what else to try in terms of connecting, I realize it should be independent of the existence of any channels but it's not working and the remote node does appear to be online. Let me know if you have any ideas.

Do you control the remote node? If so you can check to see why it disconnects.

I don't unfortunately, it's the coinpanic.com node so I could probably ask to see if they can share what it looks from their side.

I'm the owner of coinpanic.com and I see the channel open on my node, but can't connect to it.

Thanks a lot for taking a look at this. Do you think you could try connecting one more ? My raspi went down for a bit a little while ago, so I want to make sure that didn't interfere. I'm running from a fresh reboot now too, fwiw.
Here's my output from listchannels:
lncli listchannels
{
    "channels": [
        {
            "active": false,
            "remote_pubkey": "03a9d79bcfab7feb0f24c3cd61a57f0f00de2225b6d31bce0bc4564efa3b1b5aaf",
            "channel_point": "5805c720e546121f84f86f0b86e7d977b08e42f89e090c8a45c740bd1f6caf97:0",
            "chan_id": "0",
            "capacity": "3002000",
            "local_balance": "3001819",
            "remote_balance": "0",
            "commit_fee": "181",
            "commit_weight": "600",
            "fee_per_kw": "250",
            "unsettled_balance": "0",
            "total_satoshis_sent": "0",
            "total_satoshis_received": "0",
            "num_updates": "0",
            "pending_htlcs": [
            ],
            "csv_delay": 360,
            "private": false
        }
    ]
}

Good to know that the channel is recognized on the other end, problem now just seems to be the connection.

Tried again.  Same problem.  It looks like I do connect, but the channel is not going active.

Does my node show up under listpeers? I get debug output as if the connection was successful as well but it never shows up in listpeers for me.
Looking a bit through the code, it looks like this connection is "scheduled" to occur automatically, perhaps because we have a channel and we establish connections for peers with channels automatically, but it's never actually happening.
	// If we already have a valid connection that is scheduled to take
	// precedence once the prior peer has finished disconnecting, we'll
	// ignore this connection.
	if _, ok := s.scheduledPeerConnection[pubStr]; ok {
		srvrLog.Debugf("Ignoring connection, peer already scheduled")
		conn.Close()
		return
	}

@Horndev I'm curious, have you restarted your node at all in the past 4 days? I'm wondering if that might clear this connection issue up.

Oddly, this channel is now active. I took no actions, just left my node up and running.

Just FYI, I suspect that the original cause of the issue - the funding transaction seemingly disappearing from lnd when it's rejected due to a full mempool - still probably exists. It at least seems to resolve itself given some restarts and time, though. It might be worth leaving this issue open to at least keep track of it or in case others experience the same.

I realize this is an ancient issue but the above did help me and I ran into the same issue.
Due to an offline peer, my node initiated a closing of the channel, soon followed by a force close. The fee was low and my bitcoin node did not bother keeping it in its mempool so no chance to resend it. After increasing my maxmempool with -maxmempool=2000 (the current mempool is around 1600 MB, we are in 2024 now :))) I could finally get the rawtx, resend it and bump its fee, which unlocked the problem for me. Thanks for documenting on the way folks !


support Melange as baker

Where can I contribute Melange support?
I got "unknown baker" warning
see
https://melangestaking.com/
https://docs.google.com/spreadsheets/d/1s5qly_3bRfvdR43igmti1Ef0VsjMmCA9YHy_wm5r5eM/edit#gid=0

Hey! The whole list of bakers is pulled from https://www.tezos-nodes.com/. Make sure it's listed there and it will be included in Temple automatically


python evaluator does not start on mac

when running the python evaluator I get the following error:

Uncaught Error: spawn python3 ENOENT
(ENOENT is not found)

But I am able to run the same exact path with python....

python3 /Users/anon/Documents/AREPL/arepl-darwin-x64/arepl.app/Contents/Resources/app/src/python/pythonEvaluator.py

Not sure what's up with that.

Fixed.  Two things:

The python directory was not in $PATH
I had the wrong path to the python script


Add new meta-tags to HTML headers

To improve SEO and such. For reference, this article has a lot of information.
http://www.iacquire.com/blog/18-meta-tags-every-webpage-should-have-in-2013

Updating this issue, I've written a question about this on CR. Waiting for @marcandregirard to have implemented the Java web app before adding these. For reference: http://codereview.stackexchange.com/questions/74634/cardshifter-website-meta-tags-for-seo

Related: Issue # 22

Completed on web-content branch and ready to merge into master.


Updates for language, flow, & SEO

:warning: Validation status: warnings

File
Status
Preview URL
Details

toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

docs/example-scenario/apps/devops-dotnet-webapp.md
:white_check_mark:Succeeded
View

docs/example-scenario/infrastructure/regulated-multitier-app.md
:white_check_mark:Succeeded
View

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\rpjt\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\rpjt\building-blocks\extending-templates\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\rpjt\bread\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 47d3ae5:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/example-scenario/apps/devops-dotnet-webapp.md
:warning:Warning
View
Details

bread/toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

toc.json
:warning:Warning

Details

docs/example-scenario/infrastructure/regulated-multitier-app.md
:white_check_mark:Succeeded
View

docs/example-scenario/apps/devops-dotnet-webapp.md

Line 0: [Warning] (Line: 5, Col: 23, Idx: 203) - (Line: 5, Col: 24, Idx: 204): While parsing a block mapping, did not find expected key.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\wit1\bread\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\wit1\building-blocks\extending-templates\toc.json'.

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\wit1\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 2c22fcb:
:warning: Validation status: warnings

File
Status
Preview URL
Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

toc.json
:warning:Warning

Details

docs/example-scenario/apps/devops-dotnet-webapp.md
:white_check_mark:Succeeded
View

docs/example-scenario/infrastructure/regulated-multitier-app.md
:white_check_mark:Succeeded
View

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\3ibp\building-blocks\extending-templates\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\3ibp\bread\toc.json'.

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\3ibp\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit faaaa12:
:warning: Validation status: warnings

File
Status
Preview URL
Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

toc.json
:warning:Warning

Details

docs/example-scenario/apps/devops-dotnet-webapp.md
:white_check_mark:Succeeded
View

docs/example-scenario/infrastructure/regulated-multitier-app.md
:white_check_mark:Succeeded
View

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\nbyk\building-blocks\extending-templates\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\nbyk\bread\toc.json'.

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\nbyk\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit b3b86ae:
:warning: Validation status: warnings

File
Status
Preview URL
Details

toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

docs/example-scenario/apps/devops-dotnet-webapp.md
:white_check_mark:Succeeded
View

docs/example-scenario/apps/media/architecture-devops-dotnet-webapp.png
:white_check_mark:Succeeded

docs/example-scenario/apps/media/architecture-devops-dotnet-webapp.svg
:white_check_mark:Succeeded
View

docs/example-scenario/build_index.sh
:white_check_mark:Succeeded

docs/example-scenario/infrastructure/regulated-multitier-app.md
:white_check_mark:Succeeded
View

includes/scenario_articles.md
:white_check_mark:Succeeded
View

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\polm\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\polm\bread\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\polm\building-blocks\extending-templates\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 9b168c3:
:warning: Validation status: warnings

File
Status
Preview URL
Details

toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

docs/example-scenario/apps/devops-dotnet-webapp.md
:white_check_mark:Succeeded
View

docs/example-scenario/apps/media/architecture-devops-dotnet-webapp.png
:white_check_mark:Succeeded

docs/example-scenario/apps/media/architecture-devops-dotnet-webapp.svg
:white_check_mark:Succeeded
View

docs/example-scenario/build_index.sh
:white_check_mark:Succeeded

docs/example-scenario/infrastructure/regulated-multitier-app.md
:white_check_mark:Succeeded
View

includes/scenario_articles.md
:white_check_mark:Succeeded
View

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\45bu\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\45bu\bread\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\45bu\building-blocks\extending-templates\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit a904ca9:
:warning: Validation status: warnings

File
Status
Preview URL
Details

toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

docs/example-scenario/apps/devops-dotnet-webapp.md
:white_check_mark:Succeeded
View

docs/example-scenario/apps/media/architecture-devops-dotnet-webapp.png
:white_check_mark:Succeeded

docs/example-scenario/apps/media/architecture-devops-dotnet-webapp.svg
:white_check_mark:Succeeded
View

docs/example-scenario/build_index.sh
:white_check_mark:Succeeded

docs/example-scenario/infrastructure/regulated-multitier-app.md
:white_check_mark:Succeeded
View

includes/scenario_articles.md
:white_check_mark:Succeeded
View

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\ndw4\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\ndw4\bread\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\ndw4\building-blocks\extending-templates\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit be7348f:
:warning: Validation status: warnings

File
Status
Preview URL
Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

toc.json
:warning:Warning

Details

docs/example-scenario/apps/devops-dotnet-webapp.md
:white_check_mark:Succeeded
View

docs/example-scenario/apps/media/architecture-devops-dotnet-webapp.png
:white_check_mark:Succeeded

docs/example-scenario/apps/media/architecture-devops-dotnet-webapp.svg
:white_check_mark:Succeeded
View

docs/example-scenario/build_index.sh
:white_check_mark:Succeeded

docs/example-scenario/infrastructure/regulated-multitier-app.md
:white_check_mark:Succeeded
View

includes/scenario_articles.md
:white_check_mark:Succeeded
View

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\cs5j\building-blocks\extending-templates\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\cs5j\bread\toc.json'.

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\cs5j\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

OPS Build status updates of commit 0166aae:
:warning: Validation status: warnings

File
Status
Preview URL
Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

toc.json
:warning:Warning

Details

bread/toc.json
:warning:Warning

Details

docs/example-scenario/apps/devops-dotnet-webapp.md
:white_check_mark:Succeeded
View

docs/example-scenario/apps/media/architecture-devops-dotnet-webapp.png
:white_check_mark:Succeeded

docs/example-scenario/apps/media/architecture-devops-dotnet-webapp.svg
:white_check_mark:Succeeded
View

docs/example-scenario/build_index.sh
:white_check_mark:Succeeded

docs/example-scenario/infrastructure/regulated-multitier-app.md
:white_check_mark:Succeeded
View

includes/scenario_articles.md
:white_check_mark:Succeeded
View

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\sjmk\building-blocks\extending-templates\toc.json'.

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\sjmk\toc.json'.

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\sjmk\bread\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Fixes #888

OPS Build status updates of commit c7e29be:
:warning: Validation status: warnings

File
Status
Preview URL
Details

bread/toc.json
:warning:Warning

Details

toc.json
:warning:Warning

Details

building-blocks/extending-templates/toc.json
:warning:Warning

Details

docs/example-scenario/apps/devops-dotnet-webapp.md
:white_check_mark:Succeeded
View

docs/example-scenario/apps/media/architecture-devops-dotnet-webapp.png
:white_check_mark:Succeeded

docs/example-scenario/apps/media/architecture-devops-dotnet-webapp.svg
:white_check_mark:Succeeded
View

docs/example-scenario/build_index.sh
:white_check_mark:Succeeded

docs/example-scenario/infrastructure/regulated-multitier-app.md
:white_check_mark:Succeeded
View

includes/scenario_articles.md
:white_check_mark:Succeeded
View

bread/toc.json

[Warning] Error happen when converting bread/toc.json to Pdf. Details: Could not find a part of the path 'T:\0eii\bread\toc.json'.

toc.json

[Warning] Error happen when converting toc.json to Pdf. Details: Could not find file 'T:\0eii\toc.json'.

building-blocks/extending-templates/toc.json

[Warning] Error happen when converting building-blocks/extending-templates/toc.json to Pdf. Details: Could not find a part of the path 'T:\0eii\building-blocks\extending-templates\toc.json'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.