A few ideas :)

I was thinking about forking to achieve this, but i wanted your guys input.
I was thinking a few ways that this package could become the best/default forum package for laravel.
The ability to publish a few more things, for example the forum master layout so that you could customize it safely.
I think some way of having the routes defined in your routes file and defined in the chatter config could help for reasons explained in my next idea.
doing these things will mean quite allot in terms of people extending this forum safely, for example in a caffienated module. If you could publish the master layout, you could require a modified view into other views and make a view just for admins etc to moderate restricted by an outside model.
I think it could be done by simply publishing the master layout and then having the package config check for that first?
The reason i haven't forked is for i figure that the package creator/current code contributors/users are far better to put input on these things.
Any thoughts?

I just thought of one way that the  forum could implement a management type interface whilst staying interface agnostic. Why not make some API endpoints that will manage the model resources. :) People could code their own interfaces to your forum package. Win Win.

@JayLancaster, I'm totally down for that. I think API endpoints to manage the aspects of the forum would be amazing.
I also think that publishing a master file would be great. The one thing that I want to make sure that this package does not steer away from is creating a laravel forum from a blank laravel app.
Are you thinking that we would have a default master file for the main forum.
BTW, I'm totally down with making this the main Laravel forum package. I actually created it because there were so many forums out there "Run on Laravel" such as http://flarum.org, but there's no way to integrate it into my current app because they moved too far away from the laravel main structure.
Thanks for your interest in this and I'm glad to be working with you on this 👍

I agree with wanting to keep it as a great blank app drop in.
I beleive that it could be done by simple adding a if clause to check for a master layout for the forum in the views folder and have it published from an optional tag. This way its not nessicary if you don't want to and doesn't extend the integration phase.
That being said it will mean that if someone wants to at any point vendor:publish --tag="ChatterLayout" or something and customise it they can :)
As to the API endpoints, it could obviously be done by any developer at any time in any app, i just think that it would be a great addition :D

I also had a small thought about the endpoints. I think in order for them to be as extensible as possible out of the box. I would make sure they have the auth:api middleware applied and nothing else as then it will mean that people can input their own model restrictions on access themselves. Win win :)

I know that Taylor Otwell includes in the Laravel 5.3 branch the ability to vendor:publish layouts and views, etc. This also protects customization from upgrades. if this would be added in (the ability to vendor:publish the master and views to a /resources/views/vendor/chatter directory, this would INDEED become the one and only forum package for Laravel! (Regardless, JOB WELL DONE!!!)

I have been working allot with 5.3 and this was what gave me the idea :D maybe a new version to cater to 5.3 + with these modifications :)

I am amazed by this package, and I decided I'll work on it. How? I'll start by building an administration interface I guess

API endpoints would be great. I'm not too sure on how we could implement an "agnostic" admin interface personally. Any thoughts?

IMHO an admin wont help this package, anyone doing laravel development have their own frond-end and back-end way of doing things. The best way to make this package accessible to anyone is to publish all the assets the forum uses (views, css,js) so that they can be fully customized. Also I suggest moving code away from the controllers and into a DiscussionService and DiscussionService. this way someone can pull in the package and utilize most of chatter functionality in their own controllers with their own views.


[master] Upgrade to latest dependencies

Justification, Retriggering after https://github.com/knative-sandbox/knobots/pull/34 -slinkydeveloper
/cc knative/operations-wg-leads
/assign knative/operations-wg-leads
Produced via:
./hack/update-deps.sh --upgrade --release v0.21
./hack/update-codegen.sh

Details:
bumping knative.dev/hack 4ed1ecb...d946d25:
  > d946d25 Revert "Add hermetic go mod aware handling to run_go_tool (# 38)" (# 39)
  > ea9c9a0 Add hermetic go mod aware handling to run_go_tool (# 38)
bumping knative.dev/pkg 51c72e2...acbf2af:
  > acbf2af Harden logstream against non-object events (# 1984)
  > 93874f0 Drainer supports customized kubelet probe check (# 1977)

/lgtm
/approve

/lgtm
/approve


Add support for reading UUIDs instead of a player name, and added more ...

... string checking, fixes http://youtrack.sk89q.com/issue/CMDHELPER-2992.

So, this is very good, though I have one concern with this, if getting the offline user may require a web hit, then the function calls need to be async, and take a closure callback. That way if the web hit is slow, it won't freeze the server. Thoughts?

Funny enough, the methods I added are the ones where Bukkit/Spigot do NOT do a lookup. Anything that was using offline players before was already using the method that CAN do a lookup, but this should only happen if the server restarts after the player has been offline for 30 days and then one of the relevant functions is used on them. Specifically in Spikkit, getting a user by name should always be right, but may do a web lookup in the case mentioned above. Getting a player by uuid in Spikkit will never do a lookup currently, but if the player is not cached it may not return correct info.

LadyCailin plz.


chore(release): v1.0.0 🎉

:robot: I have created a release beep boop
1.0.0 (2024-05-26)
Features

init: initialize repo based on latest best practices (6a3a5e5)
src: expose asCommand method (df4ea6e)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/ehmpathy/as-command/releases/tag/v1.0.0 :sunflower:


Support for Allergy in CORE

FHIR support for CORE is defined here
https://hl7.org/fhir/us/core/STU4/StructureDefinition-us-core-allergyintolerance.html
AllergyIntolerance.code is either RxNorm or SNOMED.
Conveniently, VSAC provides this valueset:
https://vsac.nlm.nih.gov/valueset/2.16.840.1.1137<IP_ADDRESS>6.8/expansion
Valueset includes

258 SNOMEDCT codes (substance )
563 RxNorm codes (ingredient)

Categories we are most interested in are "medication" and "biologic"
https://hl7.org/fhir/R4/valueset-allergy-intolerance-category.html
Note that substance code has >2000 entries, for example, "Codeine phosphate"
https://hl7.org/fhir/R4/valueset-substance-code.html
"Findings" may be important to our "Symptoms" work, findings and symptoms may describe related or synonymous phenotypic observations.
https://hl7.org/fhir/R4/valueset-clinical-findings.html

Task: create table core__allergy with the above variables as columns, if an only if those data are actually even present in the Bulk-FHIR downloaded content.

This is a subset of #139 - we can reprioritize that work if needed?
But I think we should think very hard about not creating core tables that don't directly correspond to either FHIR resources or FHIR profiles - it limits the reusability. It would be better to support the enitre resource and have a study create a table or view based on the slice of data it needs.

@dogversioning Thanks for the link to #139
I was thinking something like
create table core__allergyintolerance as  select  code, category, substance, manifestation, severity  from allergyintolerance UNNEST (....)

the binding on that VSAC list for code is extensible so wouldn't suggest Core table pre-coordinating to only accept concepts from that list (new drugs come out all the time we will want to do some downstream study-level curation here)


Swipe gesture not working to dismiss scene

Version
Tell us which versions you are using:

react-native-router-flux v3.26.16
react-native v0.27.2
react-native-drawer v2.0.0

Expected behaviour
Before we could swipe from anywhere on the screen to pop back to the previous screen. Now it is similar to the default iOS behavior on a UINavigationViewController where you can swipe from a small portion of the screen.

I believe the default for this library should mirror the default iOS behavior. However, if you want to override that, you can always set your own panHandlers on the scene, but I don't have any examples of the functionality you're looking for.

Adding panHandlers works, in a way. I can set it to call Actions.pop() after the user has moved their touch a certain distance, however it would be really nice if the parent view rendered underneath the view as it is getting dragged off the screen. Is there a way to pull that off?

I have that behaviour but it only triggers from the very left edge.. Like, 1px or so.. it should be a little bit wider though


Still showing the fly photo in the sheet header

In the sheet view, the header still having the fly photo as background instead of the feathers photo

Fixed in f6ea39944c44adeb70490b2d919a1949325f9e54


ReferenceError: window is not defined

There are two calls to window.cancelAnimationFrame in AnimatedImplementation.js.
This causes ReferenceError: window is not defined when I run my tests, and I can't mock window because other libraries (like sinon) enable React Native compatibility by checking for window.

Whenever i've been working with sinon, i've had no problem mocking out window. Personally I use jsdom to mock it, and then grab the window out of that. If the mock is an actual mock of window, and not something you make up, it should work fine with most libraries

Thanks for the tip! It looks like jsdom doesn't implement cancelAnimationFrame, but I got things working by using jsdom and stubbing cancelAnimationFrame on top of it.
This still feels like a problem with react-native-mock though - I can submit a PR if you have a preference for fixing it. I think it should just be removed but if there's a reason it's there, there should be at least some docs around it or even a stub for cancelAnimationFrame to prevent exceptions.

I like the idea of fixing it, but I think having jsdom in the project too is a little much, considering others may want a different approach. I think the best solution would be validating that the function is actually there:  if (window && window.cancelAnimationFrame) ...?

Agreed on jsdom. After my last comment I realised the code as it is (with reference to window) is straight from React Native's AnimatedImplementation so probably fair to leave it there and guard it as you suggest.
Will submit a PR later today. I have some other Animated related things I'm mocking that I'll submit a PR for separately too.


cannot import name 'pipe' from partially initialized module 'towhee' (most likely due to a circular import)

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
tietle
Expected Behavior
No response
Steps To Reproduce
No response
Environment
- Towhee version(e.g. v0.1.3 or 8b23a93):
- OS(Ubuntu or CentOS):
- CPU/Memory:
- GPU:
- Others:

Anything else?
No response

@zyc1128 Can you share your code to help us reproduce and which towhee version do you use?

@zyc1128 Can you share your code to help us reproduce and which towhee version do you use?
I have tried a lot of versions from 0.5.0 to 1.1.3 .When I run "from towhee import pipe" this four-word-code,there is an importError: cannot import name 'pipe' from partially initialized module 'towhee' (most likely due to a circular import).Maybe I am weak in Python,but that is too weired.Only four words.

@zyc1128 Can you share your code to help us reproduce and which towhee version do you use?

My python version is 3.9.8 and  I want to use towhee to generate embeddings of images and search with Milvus.

Make sure there is no towhee.py in your workspace.

Make sure there is no towhee.py in your workspace.

Thanks,but where to set  variables such as downloading path?The doc is not clear.

Make sure there is no towhee.py in your workspace.

Thanks,but where to set variables such as downloading path?The doc is not clear.

Use the environment variable TOWHEE_HOME to change the download path

Make sure there is no towhee.py in your workspace.

Thanks,but where to set variables such as downloading path?The doc is not clear.

Use the environment variable TOWHEE_HOME to change the download path

Is there any doc that describes these variables?And I have reviewed the issues about how to config the local models,still confused.

Make sure there is no towhee.py in your workspace.

Thanks,but where to set variables such as downloading path?The doc is not clear.

Use the environment variable TOWHEE_HOME to change the download path

I  can not get access to huggingface and is there any way to run models from anything like Ollama or local models downloaded from modelscope?

Only supports models on huggingface


Clean up old Orchest images after update

Currently the updater does not remove the old images (neither command line, nor web updater).
We should keep in mind that we would prefer to support letting Orchest run during updating. So ideally it would remove dangling images only on e.g. start such that it can clean images that are not in use anymore.

The update is split from restart because a restart would clean up images and thereby also shutting down the Orchest application before starting it. When invoking an update it is up to the user whether they also want to restart, to help the user decide we actually advice them (through an echo to the terminal) to restart for the changes to take effect.
The web updater actually runs a restart for the user and so old images are cleaned up.
What is happening in the update however is that environment images are cleaned up as otherwise an old version of the SDK could be used when running Orchest. So it might be the case that, if a pipeline is running (and thus uses environment images) that then the environment images cannot be cleaned/removed and thus resulting in an error (which then results in the restart command in the web updater to never be triggered, although unlikely due to the extensive try-except block structure).
So this issue is somewhat connected to #197.
I will look into it the moment my internet improves as currently running the updater would take too long.

I don’t think Docker cleans up the old images (those running during update) that are now no longer tagged because the update replaced it during pull. Or am I missing something?


[Spark Integration] Receiving duplicate OpenLineage events for a Spark Job

Context:
Using PySpark (3.4.1) and OL(1.1.0), I tested a simple pipeline which:

Reads JSON data into PySpark DataFrame
Applies some data transformations
Writes transformed data to MySQL database
Observed that we receive 4 events (2 START and 2 COMPLETE) for the same job name. The events are almost identical with a small diff in the facets.
The issue is reproducible and also occurs if writing to a Parquet file instead of SQL.

Slack thread: https://openlineage.slack.com/archives/C01CK9T7HKR/p1694583867900909
PySpark Code:
from pyspark.sql import SparkSession
from pyspark.sql.functions import col, concat_ws, year, month, dayofmonth
from pyspark.sql.types import StructType, StructField, StringType, IntegerType

spark = (SparkSession.builder.master('local')
         .appName('etl-test')
         .config('spark.jars.packages', "io.openlineage:openlineage-spark:1.1.0,mysql:mysql-connector-java:8.0.33")
         .config('spark.extraListeners', 'io.openlineage.spark.agent.OpenLineageSparkListener')
         .config('spark.openlineage.transport.type', 'http')
         .config('spark.openlineage.transport.url', 'http://host.docker.internal:5009/events/spark/')
         .config('spark.openlineage.namespace', 'staging')
         .config('spark.openlineage.transport.auth.type', 'api_key')
         .config('spark.openlineage.transport.auth.apiKey', 'abcdefghijk')
         .getOrCreate())

spark.sparkContext.setLogLevel("INFO")

# Define schema for JSON data
schema = StructType([
  StructField("customer_id", IntegerType(), True),
  StructField("order_id", IntegerType(), True),
  StructField("order_date", StringType(), True),
  StructField("order_amount", StringType(), True),
  StructField("product_name", StringType(), True)
])

# Read JSON data into PySpark DataFrame
df = spark.read.option('multiline', True).json("input.json", schema=schema)

# Apply data transformations
df_transformed = df.select(
  col("customer_id"),
  year(col("order_date")).alias("order_year"),
  month(col("order_date")).alias("order_month"),
  dayofmonth(col("order_date")).alias("order_day"),
  col("order_amount").cast("float").alias("order_amount"),
  concat_ws("-", col("customer_id"), col("order_id")).alias("order_key"),
  col("product_name")
)

# Write transformed data to MySQL database
url = "<url>"
table_name = "orders"
mode = "append"
properties = {
  "driver": "com.mysql.cj.jdbc.Driver",
  "user": "<user>",
  "password": "<pwd>"
}

df_transformed.write.jdbc(url=url, table=table_name, mode=mode, properties=properties)

Events emitted:
spark_events.txt

Why did you put "staging" there ?
.config('spark.openlineage.namespace', 'staging')

To define a namespace for all jobs.

Hello @suraj5077, I started working on this immediately because I was aware this is some kind of serious bug introduced recently. However, as I found out, the behaviour like that was present for ~2 years. For some spark SQL jobs, the Openlineage listener gets notified on SQL start/stop and on Job start/stop events. The problem here is that some facets (like iceberg data format versioning) can be only fetched on sql start/stop while some run facets are captured in other case.
We do assume that a single job may emit multiple events and the content of those evens is accumulative which means it is a backend implementation which merges all the events into a single lineage snapshot. However, the problem here is that we should only emit a single START and a single COMPLETE events, while other shall be sent with RUNNING state. This is something I am going to work with my PR.
So, to sum up the story: please do expect still 4 events for this scenario, but there should be only one start and one complete.

Hi @pawel-big-lebowski I understand your point. I've also come across cases where the duplicate events have the exact same payload with no difference in facets. I'm assuming there should be some diff in the payload for the backend to merge them. I've also seen a single Job emit 7 events and there is no fixed pattern for this.
I also agree that there should be only a single START and a single COMPLETE event for any Job since this what the OL spec says.
This Job emits 7 events (5 Start and 2 Complete):
from pyspark.sql import SparkSession
from pyspark.sql.functions import col
from pyspark.sql.functions import lit
import random

spark = (SparkSession.builder.master('local')
         .appName('spark-pipeline-v1')
         .config('spark.jars.packages', "io.openlineage:openlineage-spark:1.1.0,"
                                        "mysql:mysql-connector-java:8.0.33,"
                                        "net.snowflake:snowflake-jdbc:3.13.14,"
                                        "net.snowflake:spark-snowflake_2.12:2.10.0-spark_3.2")
         .config('spark.extraListeners', 'io.openlineage.spark.agent.OpenLineageSparkListener')
         .config('spark.openlineage.transport.type', 'http')
         .config('spark.openlineage.transport.url', 'http://host.docker.internal:5009')
         .config('spark.openlineage.transport.endpoint', '/events/openlineage/spark/api/v1/lineage')
         .config('spark.openlineage.namespace', 'staging')
         .config('spark.openlineage.transport.auth.type', 'api_key')
         .config('spark.openlineage.transport.auth.apiKey', 'test-key')
         .config('spark.openlineage.parentJobName', 'suraj-test-job')
         .config('spark.openlineage.parentRunId', 'acd-eheh-ththth-wnjwnj')
         .getOrCreate())

mysql_connection_properties = {
    "user": "<user>",
    "password": "<pwd>",
    "driver": "com.mysql.cj.jdbc.Driver",
}

snowflake_options = {
    "sfURL": "<account>.snowflakecomputing.com",
    "sfUser": "<usr>",
    "sfPassword": "<pwd>",
    "sfDatabase": "ANALYTICS",
    "sfWarehouse": "COMPUTE_WH",
    "sfSchema": "PUBLIC",
    "sfRole": "ACCOUNTADMIN",
}

mysql_url = "<mysql-jdbc-url>"

cats_df = spark.read.jdbc(url=mysql_url, table="cats", properties=mysql_connection_properties)
dogs_df = spark.read.jdbc(url=mysql_url, table="dogs", properties=mysql_connection_properties)

cats_df = cats_df.withColumnRenamed("Country", "cat_name")

joined_df = cats_df.join(dogs_df, on="owner", how="inner")

filtered_df = joined_df.filter(col("cat_name") == 'Cookie')

agg_df = filtered_df.groupBy("cat_name").count()

agg_df = agg_df.withColumn("id", lit(random.randint(0, 1000)))

agg_df.write \
    .format("snowflake") \
    .options(**snowflake_options) \
    .option("dbtable", "COUNT_TABLE") \
    .mode("overwrite") \
    .save()

spark.stop()

Since this is a crucial bug, when can we expect a resolution for this?
And thanks for looking into it.

@pawel-big-lebowski is the above single Job with 7 events an expected behaviour?


Footnote panic: called Option::unwrap() on a None value'

Description
Error:
thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', crates/typst-library/src/meta/footnote.rs:271:37

Reproduction code:
HI#footnote.entry(clearance: 2.5em)[There]

git commit
b584617c8d594cf2ba0ee5d3dd4a042eb65fc4a3
Reproduction URL
No response
Operating system
macOS
Typst version

[X] I am using the latest version of Typst

I am pretty sure you're not supposed to instantiate footnote.entry yourself, mind you it shouldn't crash but give an error when you do it yourself instead.

Fixed in #2687


@unocss/cli writes cli log to stdout which should be stderr instead

UnoCSS version
0.61.5
Describe the bug
I tried to use the CLI to generate CSS content and captured the output from stdout in my script, but I found the CLI log is also written to the stdout, which makes the output look like this
unocss v0.61.5
◐ UnoCSS for production...
.bg-black{--un-bg-opacity:1;background-color:rgb(0 0 0 / var(--un-bg-opacity)) /* #000 */;}

Reproduction

File index.html

Run the command pnpm unocss index.html --stdout > styles.css and inspect the CSS file

System Info
No response
Validations

[X] Read the Contributing Guidelines.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
[X] The provided reproduction is a minimal reproducible example of the bug.

Do you really need --stdout? By default (without --stdout) it outputs a uno.css in the same folder. You can configure the path with -o, --out-file <file>
If you really want to use --stdout you can do something like pnpm unocss index.html --stdout | tail -n + 3 | tee styles.css

Redirecting to a file is just a help for inspecting the stdout since we cannot tell the difference between stderr and stdout in the terminal.
Of course we can do some transform(as what you do) to the stdout but it's not stable IMO, since any change to the logging might break it.
I don't know the purpose of designing the --stdout option. If it functions like the -o option, putting the CSS somewhere, I think it would be better to remove any log from it.

I don't really use the CLI so I don't know when you would want to use --stdout but to me it sounds like you use it when you want to capture everything output in the terminal, basically when you want to log what is happening.
So that's why I asked why you want to use it because it seems if you don't want the extra logs you could just use the normal output mode which already doesn't have logs.
Imo the first three lines aren't errors so writing them to stderr doesn't sound great.


rbac: Add per-policy stats to HTTP filter

Commit Message: Add per-policy stats to RBAC http filter
Risk Level:
Testing: unit/manual
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #32129]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]
Additional Description:
Currently, the RBAC filter exposes the total allowed / denied without considering the matched policy or shadow policy. This adds additional granularity to metrics so we can see which policy resulted in a decision.
This adds the following metrics to the RBAC http filter
http.<stat_prefix>.rbac.policy.<policy name>.allowed: 0
http.<stat_prefix>.rbac.policy.<policy name>.denied: 0
http.<stat_prefix>.rbac.<optional shadow_stat_prefix>.policy.<shadow policy name>.shadow_allowed: 0
http.<stat_prefix>.rbac.<optional shadow_stat_prefix>.policy.<shadow policy name>.shadow_denied: 0

/retest

The request seems reasonable to me, but it might be better to let this be opt-in to avoid an increase in the stats after the upgrade.

The request seems reasonable to me, but it might be better to let this be opt-in to avoid an increase in the stats after the upgrade.

👍 I can add a field to the rbac filter config protobuf.

Will wait for the config update.
/wait

/retest

@yanavlasov @kyessenov I've added an option to the HTTP RBAC filter config

Waiting for @kyessenov review and then submitting.
/wait-any

/lgtm api

/wait-any

/wait

/retest

Please take a look at the coverage drop in RBAC filter.
/wait

formatting/docs issues seem real
/wait

There is coverage drop https://dev.azure.com/cncf/envoy/_build/results?buildId=167231&view=logs&j=4930ecaf-18f4-5b3c-dea3-309729c3b3ae&t=573d8780-d7b9-52e3-b4e0-a89886b0b9ff&l=4922 Please take a look: https://storage.googleapis.com/envoy-pr/e35f5ff/coverage/source/extensions/filters/common/rbac/index.html

/wait

/retest

@henrymwang could you add an empty commit (or otherwise create a change)
it seems gh -> azp communication failed (this happens from time to time)

/wait

/lgtm api

There is coverage drop https://dev.azure.com/cncf/envoy/_build/results?buildId=167231&view=logs&j=4930ecaf-18f4-5b3c-dea3-309729c3b3ae&t=573d8780-d7b9-52e3-b4e0-a89886b0b9ff&l=4922 Please take a look: https://storage.googleapis.com/envoy-pr/e35f5ff/coverage/source/extensions/filters/common/rbac/index.html

I've updated the tests now to address the code coverage issue

@henrymwang the change is good to go. However GitHub is blocking it due to merge conflicts, without telling where the conflicts are. Can you merge main to see if this will resolve it, please?
/wait

@henrymwang the change is good to go. However GitHub is blocking it due to merge conflicts, without telling where the conflicts are. Can you merge main to see if this will resolve it, please?

Updated

/retest

/retest


Box files created by tesseract not compatible with 4.0 LSTM training

LSTM training requires box files which have a TAB at end of line and spaces to demarcate words.
Box files generated by tesseract from image files do not have these.
The synthetic box/tiff pairs generated by text2image have the spaces and tabs.

Related/Duplicate https://github.com/tesseract-ocr/tesseract/issues/832

Box files created by tesseract 4.00.00alpha master branch with makebox option cannot be used for LSTM training, as they do not have:

Tab character to mark end of line
Space between words

Also, makebox option creates box files with different box sizes and locations on the same image depending on the OEM mode.
Uploading boxfiletest-0.box.txt…

Uploading boxfiletest-1.box.txt…

Testing with current code, after new unicharset_extractor, there are additional problems in box files for complex scripts such as Devanagari.
The synthetic tif/box files created by text2image create one box for each aksara (conjunct-cluster+combining mark). These are broken into components by the unicharcompressor/recoder.
जु 110 4633 154 4679 0
ला 147 4645 205 4679 0
ई 198 4640 235 4694 0
- 233 4656 245 4660 0
से 244 4645 288 4692 0
प्टे 281 4645 318 4692 0
म् 311 4655 341 4678 0
ब 330 4645 366 4678 0
र 357 4645 389 4678 0
  389 4644 406 4691 0

However, the box files created by tesseract using the makebox config file, split the components and create a box for each. This happens both with Devanagari and hin traineddatas from tessdata_best.
ज 107 4632 124 4695 0
ु 124 4632 150 4695 0
ल 150 4632 168 4695 0
ा 168 4632 187 4695 0
ई 187 4632 213 4695 0
- 233 4656 241 4661 0
स 241 4656 246 4661 0
े 255 4644 274 4693 0
ष 274 4644 286 4693 0
् 286 4644 297 4693 0
ट 297 4644 309 4693 0
े 309 4644 318 4693 0
म 318 4644 328 4693 0
् 328 4644 344 4693 0
ब 344 4644 358 4693 0
र 358 4644 388 4693 0

However, the older 4.0alpha hin.traineddata in tessdata repo has the akharas.
जु 107 4632 166 4695 0
ला 166 4632 190 4695 0
ई 190 4632 213 4695 0
- 213 4632 234 4695 0
से 239 4656 246 4661 0
प् 274 4644 297 4693 0
टे 297 4644 323 4693 0
म् 323 4644 344 4693 0
ब 344 4644 358 4693 0
र 358 4644 382 4693 0

The tesseract makebox created box files for Devanagari script get the following errors related to normalization regarding combiner marks:
=== Phase UP: Generating unicharset and unichar properties files ===
[Mon Oct 16 17:35:49 DST 2017] /usr/local/bin/unicharset_extractor --output_unicharset /tmp/tmp.fN2Jr9NHXJ/bih/bih.unicharset --norm_mode 2 /tmp/tmp.fN2Jr9NHXJ/bih/bih.m
akebox.exp0.box /tmp/tmp.fN2Jr9NHXJ/bih/bih.Siddhanta.exp0.box
Extracting unicharset from box file /tmp/tmp.fN2Jr9NHXJ/bih/bih.makebox.exp0.box
Word started with a combiner:0x941
Normalization failed for string 'ु'
Word started with a combiner:0x93e
Normalization failed for string 'ा'
Word started with a combiner:0x947
Normalization failed for string 'े'
Word started with a combiner:0x94d
Normalization failed for string '्'
Word started with a combiner:0x947
Normalization failed for string 'े'
Word started with a combiner:0x94d
Normalization failed for string '्'
Word started with a combiner:0x94d
Normalization failed for string '्'
Word started with a combiner:0x94b
Normalization failed for string 'ो'
Word started with a combiner:0x93f
Normalization failed for string 'ि'
Word started with a combiner:0x94d
Normalization failed for string '्'
Word started with a combiner:0x94d
Normalization failed for string '्'
Word started with a combiner:0x94d
Normalization failed for string '्'
Word started with a combiner:0x93f
Normalization failed for string 'ि'
Word started with a combiner:0x941
Normalization failed for string 'ु'
Word started with a combiner:0x94d
Normalization failed for string '्'
Word started with a combiner:0x94d
Normalization failed for string '्'

So, some change needs to be made where the box file is being written that it combines the consonant clusters and combining marks and then creates the boxes.
Possibly this will also happen for other complex scripts.

I get the same message with Arabic language as shown below
idris@ubuntu:~/tesseract-ocr$ training/lstmtraining --model_output ~/mylottutorial/plusminus/ \

--continue_from  ~/mylottutorial/ara.lstm
--train_listfile ~/mylottutorial/ara.training_files.txt
--traineddata    ./tessdata/ara.traineddata
--old_traineddata ./tessdata/ara.traineddata
--max_iterations 1000

Loaded file /home/idris/mylottutorial/ara.lstm, unpacking...
Warning: LSTMTrainer deserialized an LSTMRecognizer!
Code range changed from 307 to 307!
Num (Extended) outputs,weights in Series:
1,48,0,1:1, 0
Num (Extended) outputs,weights in Series:
C3,3:9, 0
Ft16:16, 160
Total weights = 160
[C3,3Ft16]:16, 160
Mp3,3:16, 0
Lfys64:64, 20736
Lfx96:96, 61824
Lrx96:96, 74112
Lfx384:384, 738816
Fc307:307, 118195
Total weights = 1013843
Previous null char=2 mapped to 2
Continuing from /home/idris/mylottutorial/ara.lstm
Loaded 104/104 pages (1-104) of document /home/idris/mylottutorial/ara.mylotus_Bold.exp0.lstmf
^C
idris@ubuntu:~/tesseract-ocr$ clear
idris@ubuntu:~/tesseract-ocr$ training/tesstrain.sh \

--fonts_dir /home/idris/mylot
--lang ara --linedata_only
--noextract_font_properties --langdata_dir ./langdata
--tessdata_dir ./tessdata
--output_dir ~/mylottutorial
--fontlist "mylotus Bold"

=== Starting training for language 'ara'
[Mon Nov 13 01:52:41 PST 2017] /usr/local/bin/text2image --fonts_dir=/home/idris/mylot --font=mylotus Bold --outputbase=/tmp/font_tmp.Rf99kiznKj/sample_text.txt --text=/tmp/font_tmp.Rf99kiznKj/sample_text.txt --fontconfig_tmpdir=/tmp/font_tmp.Rf99kiznKj
Stripped 1 unrenderable words
Rendered page 0 to file /tmp/font_tmp.Rf99kiznKj/sample_text.txt.tif
=== Phase I: Generating training images ===
Rendering using mylotus Bold
[Mon Nov 13 01:52:42 PST 2017] /usr/local/bin/text2image --fontconfig_tmpdir=/tmp/font_tmp.Rf99kiznKj --fonts_dir=/home/idris/mylot --strip_unrenderable_words --leading=32 --char_spacing=0.0 --exposure=0 --outputbase=/tmp/tmp.s7NZRqv0Qa/ara/ara.mylotus_Bold.exp0 --max_pages=3 --font=mylotus Bold --text=./langdata/ara/ara.training_text
Stripped 2 unrenderable words
Rendered page 0 to file /tmp/tmp.s7NZRqv0Qa/ara/ara.mylotus_Bold.exp0.tif
Rendered page 1 to file /tmp/tmp.s7NZRqv0Qa/ara/ara.mylotus_Bold.exp0.tif
Stripped 10 unrenderable words
Rendered page 2 to file /tmp/tmp.s7NZRqv0Qa/ara/ara.mylotus_Bold.exp0.tif
=== Phase UP: Generating unicharset and unichar properties files ===
[Mon Nov 13 01:52:44 PST 2017] /usr/local/bin/unicharset_extractor --output_unicharset /tmp/tmp.s7NZRqv0Qa/ara/ara.unicharset --norm_mode 2 /tmp/tmp.s7NZRqv0Qa/ara/ara.mylotus_Bold.exp0.box
Extracting unicharset from box file /tmp/tmp.s7NZRqv0Qa/ara/ara.mylotus_Bold.exp0.box
Word started with a combiner:0x64b
Normalization failed for string ' ً'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64f
Normalization failed for string 'ُت'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًام'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64f
Normalization failed for string 'ُأ'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x650
Word started with a combiner:0x651
Normalization failed for string 'ِّر'
Word started with a combiner:0x64f
Normalization failed for string 'ُي'
Word started with a combiner:0x64f
Word started with a combiner:0x651
Normalization failed for string 'ُّل'
Word started with a combiner:0x650
Normalization failed for string 'ِحل'
Word started with a combiner:0x64f
Normalization failed for string 'ُه'
Word started with a combiner:0x64e
Word started with a combiner:0x651
Normalization failed for string 'َّط'
Word started with a combiner:0x650
Word started with a combiner:0x651
Normalization failed for string 'ِّف'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًا'
Word started with a combiner:0x64b
Normalization failed for string 'ًام'
Word started with a combiner:0x64b
Normalization failed for string 'ًى'

Getting error with text2image generated files for language kur_ara, with beta.1

=== Phase UP: Generating unicharset and unichar properties files ===
[Sat Mar 31 11:43:07 DST 2018] /usr/local/bin/unicharset_extractor --output_unicharset /tmp/tmp.XimA98vj8L/kur_ara/kur_ara
.unicharset --norm_mode 3 /tmp/tmp.XimA98vj8L/kur_ara/kur_ara.Amiri.exp0.box /tmp/tmp.XimA98vj8L/kur_ara/kur_ara.Arial_Uni
code_MS.exp0.box /tmp/tmp.XimA98vj8L/kur_ara/kur_ara.Scheherazade.exp0.box /tmp/tmp.XimA98vj8L/kur_ara/kur_ara.Tahoma.exp0
.box /tmp/tmp.XimA98vj8L/kur_ara/kur_ara.Times_New_Roman.exp0.box
Extracting unicharset from box file /tmp/tmp.XimA98vj8L/kur_ara/kur_ara.Amiri.exp0.box
Word started with a combiner:0x64e
Normalization failed for string 'َا'
Word started with a combiner:0x650
Normalization failed for string 'ِر'
Word started with a combiner:0x64e
Normalization failed for string 'َا'
Word started with a combiner:0x64e
Normalization failed for string 'َا'
Word started with a combiner:0x64e

@Shreeshrii, please close this issue.

Thanks!


Name issue on "Who is in the hubb?"

Jag och Maddy har problemet att vi heter Morpheus och Mad Mats, men vi vill ju självklart heta Maddy och MorpharN! Cuz, cool!

The issue here is pretty much that the names listed on the whosinthehubb is not correlated to the names set in the chalmers.it. Definitely something that should be fixed.


Properly handle python.exe xor py being present on windows

We currently assume py, the python launcher on windows, is always present. We should test without it and allow only python.exe and show good error messages when both are missing.

Related https://github.com/astral-sh/uv/issues/1521


where should layer norm be applied?

class SublayerConnection(nn.Module):
def __init__(self, size, dropout):
    super(SublayerConnection, self).__init__()
    self.norm = LayerNorm(size)
    self.dropout = nn.Dropout(dropout)

def forward(self, x, sublayer):
    "Apply residual connection to any sublayer with the same size."
    #return x + self.dropout(sublayer(self.norm(x)))
    return self.norm(x + self.dropout(sublayer(x)))

In the paper, it seems to be "return self.norm(x + self.dropout(sublayer(x)))". But it gives a bad result for the example "Train the simple copy task."

also confused about the SublayerConnection(). The text explanation quoted as below is contradicted the code.
'''
That is, the output of each sub-layer is LayerNorm(x+Sublayer(x)), where Sublayer(x) is the function implemented by the sub-layer itself. We apply dropout (cite) to the output of each sub-layer, before it is added to the sub-layer input and normalized.
'''

I find in the forward() commit:
"Note for code simplicity the norm is first as opposed to last."
But it is a mismatch with the paper.

I'm necroing this thread a bit :-) But I agree with you guys.
We have these two classes :
class SublayerConnection(nn.Module):
    """
    A residual connection followed by a layer norm.
    Note for code simplicity the norm is first as opposed to last.
    """
    def __init__(self, size, dropout):
        super(SublayerConnection, self).__init__()
        self.norm = LayerNorm(size)
        self.dropout = nn.Dropout(dropout)

    def forward(self, x, sublayer):
        "Apply residual connection to any sublayer with the same size."
        return x + self.dropout(sublayer(self.norm(x)))  ##B

class EncoderLayer(nn.Module):
    "Encoder is made up of self-attn and feed forward (defined below)"
    def __init__(self, size, self_attn, feed_forward, dropout):
        super(EncoderLayer, self).__init__()
        self.self_attn = self_attn
        self.feed_forward = feed_forward
        self.sublayer = clones(SublayerConnection(size, dropout), 2)
        self.size = size

    def forward(self, x, mask):
        "Follow Figure 1 (left) for connections."
        x = self.sublayer[0](x, lambda x: self.self_attn(x, x, x, mask))  ##A
        return self.sublayer[1](x, self.feed_forward)

If I follow line ##A to go to ##B I understand that :

normalization is applied BEFORE the self attention layer. If we consider only this layer, this might be equivalent.
norm is NOT applied to x (the residual connection), which is I think the real issue.

I really don't see where x could be normalized.
And if it's not, the residual connection does not make sense. The lack of normalization on x will make the residuals very large, which is killing their purpose.
We could simply do the following, as pointed out by @liangbright
class SublayerConnection(nn.Module):
    """
    A residual connection followed by a layer norm.
    Note for code simplicity the norm is first as opposed to last.
    """
    def __init__(self, size, dropout):
        super(SublayerConnection, self).__init__()
        self.norm = LayerNorm(size)
        self.dropout = nn.Dropout(dropout)

    def forward(self, x, sublayer):
        "Apply residual connection to any sublayer with the same size."
        return self.norm(x + self.dropout(sublayer(x)))

and also remove the last norm here since with this change, the last normalization is carried on by the last SubLayerConnection
class Encoder(nn.Module):
    "Core encoder is a stack of N layers"
    def __init__(self, layer, N):
        super(Encoder, self).__init__()
        self.layers = clones(layer, N)
        self.norm = LayerNorm(layer.size)

    def forward(self, x, mask):
        "Pass the input (and mask) through each layer in turn."
        for layer in self.layers:
            x = layer(x, mask)
        return self.norm(x)   ## remove

Hi all,
We are working on a new version of this writeup, and will make this point clear and why it was confusing.
If you are interested in helping out come chat here: https://discord.gg/VUwHN8xZ

I have seen the new version, but i didn't find the explanation of this problem.  Does anyone see the updated writeup?

class SublayerConnection(nn.Module):
def __init__(self, size, dropout):
    super(SublayerConnection, self).__init__()
    self.norm = LayerNorm(size)
    self.dropout = nn.Dropout(dropout)

def forward(self, x, sublayer):
    "Apply residual connection to any sublayer with the same size."
    #return x + self.dropout(sublayer(self.norm(x)))
    return self.norm(x + self.dropout(sublayer(x)))

In the paper, it seems to be "return self.norm(x + self.dropout(sublayer(x)))". But it gives a bad result for the example "Train the simple copy task."

Maybe it should be return (x + self.norm(self.dropout(sublayer(x))))

This paper might be relevant (explaining why the norm should be applied before rather than after): On Layer Normalization in the Transformer Architecture.


(low priority) shouldn't body.header not scroll with the sections?

The docs seems to imply that the sections are scrollable but the body.header should not. With a templates/body/header containing a search box scrolling the templates/body/sections[0]/items causes the search box also to scroll.
If this is as-designed then please just close, if this strikes you as not what's intended then I will provide a jasonbase test case from my app.

Yes that's because that's how native search bar works on iOS. One workaround is to move this into the top header bar as you mentioned, but this will give rise to another problem, which is "where to put the title" if the search bar is placed in the top header bar by default? This would mean all apps with a search feature will not be able to have the top title label.
Android doesn't have this problem because their title is by default displayed on the left side, but on iOS I think we'll need to a solution to this problem if we want to support this feature.


TileMap::world_to_map Ensure half offset is added according to the returned value

Resolves issue mentioned in this comment.

Thanks!

Cherry-picked for 3.4.


[ServiceBus] Settlement move from Message to Receiver

/azp run python - servicebus - tests

/azp run python - servicebus - tests

/azp run python - servicebus - tests


iframes embedded with ?? can not be styled

I am embedding an interactive website with ??.  I am not able to remove this border.
I tried

??[Addieralgorithmus](https://addieralgorithmus.replit.app/ "Additionsalgorithmus")<!--style = "border:none;"-->
a global stylesheet with iframe {border: none !important;}

in both cases no styles are applied and the ugly border still shows.
If i simply write an iframe tag in my liascript sourcecode everything works as intended.
This is a fine workaround but I would still prefer to use LiaScripts own ??-Syntax.

Hi, are you using the live-editor or a plugin ... this problem was addressed in the last update of LiaScript, thus styling oEmbeds should now work as expected. I tried your initial example, and on the LiveEditor it does work.
Try it
Could you try to update your editor-plugin or the live-server, and check if this fixed the problem for you too?


Atom consistently crashes when trying to expand any snippet on line 2044 of this file

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Reproduced the problem in Safe Mode: https://flight-manual.atom.io/hacking-atom/sections/debugging/#using-safe-mode
Followed all applicable steps in the debugging guide: https://flight-manual.atom.io/hacking-atom/sections/debugging/
Checked the FAQs on the message board for common solutions: https://discuss.atom.io/c/faq
Checked that your issue isn't already filed: https://github.com/issues?utf8=✓&q=is%3Aissue+user%3Aatom
Checked that there is not already an Atom package that provides the described functionality: https://atom.io/packages

Description
Atom 1.25.0 consistently crashes when trying to expand any snippet on certain lines of some files.
Steps to Reproduce

Compose a text file with 2042 lines of test, followed by 2 blank lines and then a line of test (2045 lines in total).
The last line is optional, just to prevent Atom from removing the trailing blank lines.
Open the file with Atom and select any language (e.g. C)
Move cursur to line 2044; type anything that can trigger a snippet (e.g. inc to trigger #include ".h")
"The editor has crashed"!

Expected behavior: Snippets get expanded normally
Actual behavior: Atom crashes
Reproduces how often: 100%
Versions
Atom    : 1.25.0
Electron: 1.8.4
Chrome  : 59.0.3071.115
Node    : 8.2.1
Additional Information
The file: test.txt
Distro: Arch Linux

I'm too facing the crashing problem  in Atom 1.25.0. Many times, when I working on other application, popup raised and says Atom crashed.

Thanks for reaching out!
We've determined that this issue is being caused by the use of an unofficial build or distribution of Atom. Often these customized versions of Atom are modified versions of the Stable branch of Atom with mismatched versions of built-in components. These updated components are taken from the Beta channel or master branch and then injected into the Stable version and a new Atom package is generated. Because of the way Atom is constructed, using these mismatched components can cause mysterious and hard-to-diagnose problems. You can find out more about why we chose to not support unofficial distributions here.

https://bugs.archlinux.org/task/57991
Caused by https://github.com/atom/superstring/issues/57 so our distro build is fixed now. :)


Check what happens if a test fails and leaves the database in a bad state

Does TransactionTestCase take care of this?
If not, is there something we can do to dump and restore the database everytime/when needed?

I think it relates to issue #33 and the new test introduced by #35.


  Open in CodeSandbox Web Editor | VS Code

Gonna close this for now as iFrame isolation wasn't such a good idea after all, might experiment with web workers or something at some point instead


[Hold] Removed all cmdlets under connected-accounts

@chrisda For your review. See email thread.
Also, it seems I am unable to open a PR against the PowerShell repo, hence the fork.

Docs Build status updates of commit cce0718:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit cce0718:
:clock10: Full build: the average full build time is 12 min(s) 16 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit cce0718:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/connected-accounts/Get-ConnectSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-HotmailSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-ImapSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-PopSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-SendAddress.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-Subscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-ConnectSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-HotmailSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-ImapSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-PopSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-Subscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Remove-ConnectSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Remove-Subscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Set-ConnectSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Set-HotmailSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Set-ImapSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Set-PopSubscription.md
:white_check_mark:Succeeded

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.

Docs Build status updates of commit 0bc4e82:
:clock10: Full build: the average full build time is 12 min(s) 16 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 0bc4e82:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/connected-accounts/Get-ConnectSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-HotmailSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-ImapSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-PopSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-SendAddress.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-Subscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-ConnectSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-HotmailSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-ImapSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-PopSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-Subscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Remove-ConnectSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Remove-Subscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Set-ConnectSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Set-HotmailSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Set-ImapSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Set-PopSubscription.md
:white_check_mark:Succeeded

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.

Docs Build status updates of commit 7b1d791:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit 7b1d791:
:clock10: Full build: the average full build time is 12 min(s) 17 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 7b1d791:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/exchange-ps/exchange/connected-accounts/Get-ConnectSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-HotmailSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-ImapSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-PopSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-SendAddress.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Get-Subscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-ConnectSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-HotmailSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-ImapSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-PopSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/New-Subscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Remove-ConnectSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Remove-Subscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Set-ConnectSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Set-HotmailSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Set-ImapSubscription.md
:white_check_mark:Succeeded

exchange/exchange-ps/exchange/connected-accounts/Set-PopSubscription.md
:white_check_mark:Succeeded

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.


Azure.Search: Assert.AreAqual not sufficient for comparing static models

While investing #10944 I found that StaticDocuments test was passing despite having the same problem that complex fields like Location were not being serialized and thus coming back null. While Assert.AreEqual works for SearchDocument, it does not for static models like Hotel.
For testing, we could probably implement IEqualityComparer<Hotel> et. al. to pass use, like:
Assert.That(docs[i], Is.EqualTo(SearchResources.TestDocuments[i]).Using(HotelComparerShared));

Or, since it's only test data, just override Equals on Hotel et. al.
This works for dynamic documents because NUnit uses a chained comparer for common types like dictionaries, so works on nested SearchDocuments.

Never mind. The existing equals override was explicitly excluding Location while we wait for a resolution to #10592, but Microsoft.Spatial.GeographyPoint will suffice for now.


Add documentation for forms

Hi @mrmrs please let me know if I can be of any help with this. Best regards.


Add renovate bot for dependency management

Add renovate bot to this addon for automated dependency management.

Initial config in PR #208.
I wonder if a good next step before adding additional repositories would be to create a common base config: https://docs.renovatebot.com/config-presets/#github-hosted-presets

@dbollinger I think that's a good idea, it would give us a good way to keep addons updated in this org.

I went ahead and merged the config last night, so we have the first round of renovate PRs this morning.  Here's an example: https://github.com/ember-a11y/ember-a11y-refocus/pull/209
Next steps:

[ ] Turn off dependabot for this repo and close (or merge?) related PRs
[ ] Create a dedicated repo in the ember-a11y group for shared renovate config
[ ] Add renovate bot to the rest of the projects in the ember-a11y group and extend from shared config

@MelSumner -- Would you prefer to keep this issue open for these next steps, or close it and create a new one?

@dbollinger let's track it in a project, that way you can add an issue to each repo and then have PRs for that repo.
https://github.com/orgs/ember-a11y/projects/1

@dbollinger the other thing I totally spaced on was that dependabot was already in this project. Could you remove that from this repo?


Appbar actions doesn't respect the Appbar theme with Material3!

#111339

Hi @EhabSalah  as reported in https://github.com/flutter/flutter/issues/111339#issuecomment-1243290674, this has already been fixed. I just confirmed that the fix is also available on the beta channel so it should be in the next stable.
Since this has already been fixed, I'll be closing this issue. Thank you


[Event Request] codeunit 99000854 "Inventory Profile Offsetting", OnAfterCanDecreaseSupply

begin
    with InventoryProfileSupply do begin
        if ReduceQty > "Untracked Quantity" then
            ReduceQty := "Untracked Quantity";
        if "Min. Quantity" > "Remaining Quantity (Base)" - ReduceQty then
            ReduceQty := "Remaining Quantity (Base)" - "Min. Quantity";

        // Ensure leaving enough untracked qty. to cover the safety stock
        TrackedQty := "Remaining Quantity (Base)" - "Untracked Quantity";
        if TrackedQty + "Safety Stock Quantity" > "Remaining Quantity (Base)" - ReduceQty then
            ReduceQty := "Remaining Quantity (Base)" - (TrackedQty + "Safety Stock Quantity");

        // Planning Transparency
        if (ReduceQty <= DampenerQty) and ("Planning Level Code" = 0) then
            exit(false);

        if ("Planning Flexibility" = "Planning Flexibility"::None) or
           ((ReduceQty <= DampenerQty) and
            ("Planning Level Code" = 0))
        then
            exit(false);

        OnAfterCanDecreaseSupply(InventoryProfileSupply, ReduceQty, DampenerQty, IsHandled, ExitValue);
        if IsHandled then
            exit(ExitValue);

        exit(true);
    end;
end;

[IntegrationEvent(false, false)]
local procedure OnAfterCanDecreaseSupply(InventoryProfileSupply: Record "Inventory Profile"; ReduceQty: Decimal; DampenerQty: Decimal, var isHandled: Boolean; var ExitValue: Boolean)
begin
end;

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


Add how to use section

WHY
Current README only explains list of command usage, but users may want to know how to use.
WHAT
Added how to use section. @dtan4 ptal.

LGTM 👍 Thanks :Ex

#25


Feature/application form UI

Updated error validation in Contact form & Created Application Form

@isurupathumherath CI/ CD is failed. Run the build in your local machine and check why it is failing.


[import/no-unresolved] not working in our mono-repo from 2.0.0

We recently upgraded to Typescript 3.7 and updated all eslint + prettier related packages. Moving from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>is leading to more import/no-unresolved errors showing up for paths configured in tsconfig.json in the sub-packages.
Our structure
.
├── ...
├── .eslintrc.js
├── packages
│   ├── a
│   │   ├── .eslintrc.js
│   │   ├── tsconfig.json
│   │   └── package.json
│   └── b
│       ├── .eslintrc.js
│       ├── tsconfig.json
│       └── package.json
├── ...
├── package.json
├── lerna.json

We're using multiple .eslintrc.js in each directory since the projects are cross platform (node/browser) and have different environments & configurations.
Configs
// .eslintrc.js
module.exports = {
  // ...
  parser: '@typescript-eslint/parser',
  parserOptions: {
    ecmaVersion: 2018,
    sourceType: 'module',
  },
  plugins: ['import'],
  rules: {
    // ...
    /** Show errors for un-resolved imports */
    'import/no-unresolved': 'error',
    // ...
  },
  settings: {
    'import/parsers': {
      '@typescript-eslint/parser': ['.ts', '.tsx'],
    },
    'import/resolver': {
      typescript: {
        directory: ['packages/*/tsconfig.json'],
      },
    },
  },
};

// .eslintrc.js
const { resolve } = require('path');

module.exports = {
  settings: {
    'import/resolver': {
      typescript: {
        directory: resolve(__dirname, 'tsconfig.json'),
      },
    },
  },
};

What we've tried

Having a single setting in the root level with packages/*/tsconfig.json
Having a single setting in the root level with array of actual file paths to the tsconfig directory.
Both the above with explicit setting in the package (a/b) level setting with directory: resolve(__dirname, 'tsconfig.json'),

We downgraded back to v1.1.1. 😅
Can you help us out? Happy to provide more information as required.

Please provide a minimal runnable reproduction, thx.

Personal idea without approve, you should never use multiple .eslintrc.js files, replace them with overrides instead.
Take https://github.com/1stG/configs/tree/master/packages/eslint-config as an example.
Feel free to point out if I'm wrong.

Or try to add root: true in every .eslintrc.js so that the root level eslint will not try to resolve paths any more.

I have possibly encountered the same problem:
Whenever you run eslint on several files from different sub-packages import-unresolved errors  show up, but running on single file is always OK.
Please check this repo for reproduction: https://github.com/ZmoNkk/import-resolver-typescript-demo
Repro steps:

Install eslint and all dependencies
Run ./node_modules/.bin/eslint a/index.ts.
As expected it shows only one error regarding non existing package.
Run ./node_modules/.bin/eslint --ext .ts ./

Result:
First file is linted ok, but second file throws import/no-unresolved error on exising package.
Any advice? Possibly this is a misconfiguration on my part, but I have tried different setups and this issue persists.
Issue does not appear on v1.1.1 as well

@ZmoNkk Thx for reproduction, I'll check it ASAP when I'm not so busy.

@ZmoNkk Please check https://github.com/ZmoNkk/import-resolver-typescript-demo/pull/1/files. I believe you're both misusing eslint with eslint-import-resolver-typescript.
I'll close this issue temporarily, feel free to point out me and I'll reopen it.

I have below config in .eslintrc.yml and the vscode + volar give me following error:
config:
parserOptions:
  ecmaVersion: latest
  parser: '@typescript-eslint/parser'
  sourceType: module
  createDefaultProgram: true
  project:
    - ./tsconfig.json

error:
Parsing error: Cannot read file '/users/xxx/workspace/monorepo-proj/tsconfig.json'

And the project folder structure is:
--- monorepo-proj
   --- apps/demo
         --- apps/demo/.eslintrc.yml


Feature Request: Trace every line of my code which gets executed

I would like to have a panel which shows every line of my code which got executed during the http request.
Lines of the python standard library or the django framework should not be shown.
I googled, but it seems that there is nothing up to now.
Similar to set -x on the shell.
Maybe this new panel could be based on one of these tools
https://github.com/ionelmc/python-hunter
https://github.com/gaogaotiantian/viztracer
Maybe it would make sense to start this panel as external project first.
Please tell me if I was blind and a ddt panel like this already exists.

Related: https://github.com/ionelmc/python-hunter/issues/79

This tracer looks good: https://github.com/gaogaotiantian/viztracer
Since it supports perfetto, it might be more powerful. But I did not do a deep comparison to python hunter yet.


[Feature Request] Feedback for contribution point "editor/title/run"

// This is a follow-up issue for https://github.com/microsoft/vscode/issues/114123, cc @jrieken
Thanks to the team to provide a centralized contribution point for the run button. Here are some feedback for consideration.

Show the keyboard shortcut in the dropdown menu?
Considering another entry for debug (editor/title/debug)? In that case the user can just have one click if each contribution(run and debug) just has one entry.
Just like what we have in the debug view, the title area can have a dropdown menu explicitly and VS Code can memorize the last choice. (But given the very limited area there, this might not be a good idea though)

Considering another entry for debug (editor/title/debug)?

Our idea is that the menu is used for run- and debug-commands

//cc @weinand

Now if I want to run my code, I need to click twice :( Previously one click was enough. Can you add a setting that sets a default behavior for the button? If you click on it once, "Run Code" should be the default. Clicking twice is a pain.

The Java side also has a user mentioned about the Clicking twice is a pain

I'd love an option to revert back to the previous button. This new feature has not once worked properly for me because it closes just as fast as it opens by itself. Seems to be a bug that I have been tracking for the past few days.

Clicking twice really is a pain, would appreciate if a 'Select Default Option' was available for different languages.

@Parminder51 "Happening in Python" : what do you mean? Do you have a link for more info?

@jabbalaci When I'm trying to click the run button, the context menu pops up. A few days back it would just run the file with the coderunner extension. Now I have to select again and again whether to run using the python extension or coderunner extension.

@Parminder51 OK, I misunderstood. When you wrote "Happening in Python", I thought a solution for Python was under way. Yes, I also noticed this double-click problem and it also bothers me. I hope there will be a solution for this soon.

For those of you with the problem, are those two contributions to the new editor/title/run menu coming from a single extension or two extensions? If two separate extensions, is it feasible to disable one for the workspace?

I have the same problem with @Parminder51

@gjsjohnmurray Usually the Python extension's button is hidden if the Code Runner extension is enabled, and it was working fine. But now when you click on it, the context menu pops up. I hope to use the Code Runner extension but there is no way to remove the run button in the Python extension, I checked for it and found this. https://github.com/microsoft/vscode-python/issues/6921.

I suggest we agument toolbar submenu actions with some indicator that it's going to be a dropdown. This should help in the user's perception of what will happen when they click it.
For this specific toolbar submenu action, the Run, maybe it's best to further change it to behave like debug: a UI piece with two click zones, one for the default and another for the dropdown which, when selected, would run and change the default.

Now that we have hover feedback on toolbar actions (via https://github.com/microsoft/vscode/issues/120226) I think it now makes sense to explore what adding affordances to split buttons could look like to improve their usability. Here are a few concepts:

Option 3

Vote for option 3.
The background color indicates that the play and chevron-down are in one group, while the different background color indicates that they have different functionalities.

I just pushed the new DropdownWithPrimaryActionViewItem to base:
https://github.com/microsoft/vscode/blob/main/src/vs/base/browser/ui/dropdown/dropdownWithPrimaryActionViewItem.ts
This powers the terminal's button in the same style:

It's basically the 3rd option but with a negative left margin on the right button so that the 2 buttons are closer together like option 2, this is particularly important to help distinguish the related v icon for this case:

We might want to consider introducing a shortcut for the "default run action"; see #125401

Not sure I understand... This is just a dynamic sub menu. Are you suggesting to add a keybinding to trigger a submenu (or its sole command if only one exists)?

Since the "split button" UI introduces the concept of a "default run action", it would be helpful if this "default action" would have a keybinding.

This feature request tries to improve the user experience for the recently added contribution point "editor/title/run".

There are two pain points with the current UI of the contribution point:

if there are more than two action contributions, two clicks are needed to trigger an action: the first click opens the drop down menu and the second selects the action from the menu.
from the UI it is not obvious whether the "run" item is a single action or a dropdown with multiple actions. This makes the UI instable and requires close attention by the user in order to not forget the "second click".

The new split button (DropdownWithPrimaryActionViewItem) looks like a good way to address the pain points.

The split button has two click zones, one for the default (left) and another for the dropdown (right) which, when selected, would run and change the default.
Behavior:

with a single action contribution the action would become the default and the drop down would be disabled.
with two or more action contributions there are two option for the default:

no default and the user is required to open the drop down select and run an action
the first contributed action becomes the default automatically

@weinand Please go ahead on this and let me know where I can help

@jrieken please provide code pointers

The split button in action:

@isidorn raised the question whether selecting a drop down menu action should only select or select and execute the action.
The former would again require two clicks. The latter only one but its behavior might be a bit surprising.

I was just concerned if we have other places in our UI where selecting something also runs it.
Since the debug dropdown behaves different maybe I am just used to that selection only selects.
I would still slightly lean towards that selection should not run because:

I think users will not often switch between the options
It is cleaner and aligns better with the rest of our UI

Another thing to consider: if the actions in the drop down menu do not have different icons, then selecting them without executing them will not have any visual effect on the split button.

I think the dropdown in the debug view is visually different enough that it won't cause that confusion:

Because we also use the same interaction of selecting a dropdown to perform an action in the terminal:

@misolori I was not aware that we also do this in the terminal.
Then I think we should go with this approach here also.

I've released the feature. Please try it in the next Insiders.

@weinand
Looks good! Just one bug I found, arrows are appended if user select through dropdown
https://user-images.githubusercontent.com/6193897/125407416-6e76d280-e3ec-11eb-913a-1527bf952a32.mp4
Version: 1.59.0-insider (user setup)
Commit: f6df685c62da50886f7540cbf768ed4333d58bea
Date: 2021-07-13T05:12:59.073Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19043

@jdneo interesting. I'm not seeing this on with Mock Debug... Will investigate with Java

Yes, I can reproduce with the Java extension.

@jdneo I've fixed the problem that you've spotted.
Please verify with next Insiders.

I noticed some weird behavior with which title is shown on the button. To replicate:

Open the webview sample from vscode-extension-samples
Edit package.json to use the contribution point:

"menus": {
    "editor/title/run": [
        {
	        "command": "catCoding.start"
        },
        {
	        "command": "catCoding.doRefactor"
        }
    ]
}

Launch the extension and ensure that the button is currently showing "Do some refactoring". Using the "start a cat coding session" option in the dropdown does not cause the button show the text for "start cat coding session", but it just stays the same instead. 🐛
Also, if you click the "start cat coding session" option again with the window still open, it now shows the right text on the button 🐛

Hi @weinand thank you for the fixing. Now the dropdown arrow works pretty well.
There is another problem though, after switching the active run action via the arrow, then the run/debug button itself becomes unclickable.

@andreamah I can reproduce the problem you are seeing. It only occurs if the command has no icon (which is not the typical scenario for a editor toolbar icon). I'll investigate...

@andreamah The issue is a cyclic context JSON that gets serialized over to the extension host via rpc.
@jdneo I've added a workaround and I could no longer reproduce the problem in the webview sample and in the Java extension.

Thank you @weinand, I just played it in the newest insider, everything works great now!


save SAEFeatureExamples++ to persistent storage

This is the only element of the experiment that gains much from executing at all layers at once. If we precompute it and save in persistent storage, and then load it into memory one by one, then we will be able to store clean_logits in it as well.

What I think we should actually do:

tokenize dataset {seq len}
run a model on a sizable dataset, save all resid activations, logits and clean loss; upload to HF {model, tokenized dataset, seq len)
decompose activations with SAE, for each feature save (batch, pos) pairs where the feature was active + max feature activation {SAE}

object/step 1:
tokenized dataset
parameters: source dataset name, dataset split, tokenizer, seq. len
object/step 2:
resid acts, logits and loss
object/step 3:
active feature locations
meaning: for each feature, have a list of (batch, seq) pairs where it was active
+max activation
we can take it for a test run by just using a smal subset of the dataset


Pressing keys causes beeping, even outside Karabiner Elements

I'm using Karabiner Elements 0.90.27. Here is my karabiner.json
{
    "profiles": [
        {
            "name": "Default profile",
            "selected": true,
            "simple_modifications": {
                "fn": "left_control",
                "f12": "delete_forward"
            }
        }
    ]
}

I can reproduce the issue like this:

Open Karabiner Elements window and type some letters (like asdf). This will cause it to start beeping for each letter.
Type some command keys, like Ctrl, Option, Command. These will also beep.
Now use the mouse to switch to another application, say Chrome.
Type the command keys, Ctrl, Option, Command. These will continue to beep, although they seem otherwise functional.
As soon as you type a letter in the other application, the beeping goes away.

The beeping in the other application is the bug here, but personally, I would rather not have any beeping even in Karabiner Elements, as its annoying, and seems unnecessary.

Oh and I'm on Sierra 10.12 Beta (16A313a)

So this issue actually triggers more often than just by doing that.  Sometimes, after using fn + arrow (i.e., control + arrow) to switch spaces, it happens, even when the Karabner Elements window is not open. It doesn't happen every time, and I'm unsure how to reproduce it. The above steps reproduce the issue every time.

@asmeurer You should try the update 0.90.29.

Open Karabiner Elements window and type some letters (like asdf). This will cause it to start beeping for each letter.

Also this is true for all windows. Say you quit Karabiner-Elements, open "About This Mac". Press character keys, you will hear the warning bell.

I believe this is fixed on latest release.

I can confirm the issue is still happening on the latest release, v0.9.46.


dwarf-fortress 0.43.03

@BrewTestBot test this please

0.43.04 is out now. Any chance you could update your PR for the latest? :-)

Merged as ea05f45417e499c5ec2321d16c325721f96fad25 since it's been ready for a while, but we'd love another PR for the new version!


Increase supported python version to >=3.7.0

Increase supported python version to >= 3.7.0
Increase supported prettytables version to <4.0

Is there a reason to not support Python 3.6? I actually need it for one of the projects I work on due to the OS version and available packages. So I suspect other users also still need it.

Btw, sorry for the slow replies this week, I've been moving into a new house.

Is there a reason to not support Python 3.6? I actually need it for one of the projects I work on due to the OS version and available packages. So I suspect other users also still need it.

Python 3.6 is not supported  by upstream anymore, so there is no reason to support it in downstreams.
FWIW, prettytable now also only supports >= 3.7

It appears that you have bumped the supported version of prettytable to < 4.0.0 in https://github.com/pyocd/pyOCD/pull/1359, so I guess this can be closed.
Dropping support for python 3.6 is nonetheless a good idea and should be done as soon as possible, as it prevents using newer language features, etc.

Ping?

Fyi, I've created a new PR #1477 based on this one, with a few minor changes like removing the dataclasses dependency.


refactor: minor UI updates

Hello, I have noticed that the tutorial components on the home page are overflowing from the parent when I zoom in or use a smaller resolution. This is because of the fixed height that has been defined.
To address this issue, I have set the height specifically for devices with a screen height of 1024px or larger. Additionally, I have added a margin to the Login with Discord navigation to ensure it looks consistent with other navigation items.

hey there @dimfu, thank you for the PR! initially the height was set so the page was completely filled, but there's a bit of space on the bottom. not sure what the resolution is here but i'd ideally like to keep the page filled

Hi @jacc , I have made the changes you requested and adjusted the height to fill the empty space. Please take a look and let me know if this satisfies what you were asking for. Thank you!

sorry to be nitpicky - there's a bit of an overflow on the scroll. could that be fixed as well?

Hey @jacc I have fixed the issue as you requested, kindly review the changes and let me know if everything looks good on your screen


App opens with link, but callback isn't fired

The app will open with a link on Android, but the callback won't trigger. Any ideas?
I used the subscribe after device ready:
universalLinks.subscribe(null, mycallbackFunction);
config.xml
    <universal-links>
        <ios-team-id value="asdfasdfa" />
        <host name="*.mydomain.com" scheme="https">
            <path url="/limitedPath/*" />
        </host>
    </universal-links>

I added the event to the config, and it started working.

Hello, I'm struggling with the same problem for some time, I'm using angular for this and no matter how I import universal links the subscribe is not firing, can you please add that part of your working solution?
Thank you


New version: Mads v0.7.7

Registering package: Mads
Repository: https://github.com/madsjulia/Mads.jl
Created by: @montyvesselinov
Version: v0.7.7
Commit: 3ca85a80c3541b5aa923f75bbc75ceea4bd795c9
Git reference: master
Release notes:

various fixes

Your new version pull request does not meet all of the guidelines for automatic merging.
Specifically, your pull request does not meet the following guidelines:

The following dependencies do not have a compat entry that has an upper bound: ReusableFunctions, OrderedCollections, Anasol, Kriging, DataStructures, Compat, OrdinaryDiffEq, MathProgBase, Measures, julia, JLD2, Cairo, DataFrames, QuartzImageIO, Distributions, AffineInvariantMCMC, LsqFit, ProgressMeter, Gadfly, FileIO, Suppressor, Optim, Conda, PyCall, JSON, StatsBase, Images, YAML, PyPlot, MetaProgTools, DocumentFunction, BlackBoxOptim, Documenter, Fontconfig, JuMP, Ipopt, Compose, Colors, NMF, SVR, RobustPmap, DocumenterMarkdown

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]

Please add compatibility bounds to at least julia. Preferably all deps to get this automerged.

delete this. v0.8 submitted instead.


Order Details Screen Issues

What is going on with that up or down UI control? They're non-functional and look odd.
Also Avatars get stretched with long addresses.

I don't see the arrows being flipped on my branch. There's some slightly exotic chrome css going on there, is it possible this is an OSX issue?

Do others see it? @morebrownies ?

I haven't looked at checkout yet. I'm planning on starting on that Monday.


Optimise JarModuleFinder.of()

Do you have any data to back up this "optimization"? It just looks like code reorganization to me.

Superseded by #57.


Parser Troubles..  This should parse.  Shows an error at the '*'

source: s is table('malloytest.state_facts') + {
  measure: total_births is births.sum()

  query: foo is {
    group_by: popular_name
    aggregate: total_births * 100
  }
}

aggregate: pct_total_births is total_births + 100


SSL/TLS Server and Client Authentication with Intermediate Certificates

Hello,
First of all, thank you for providing us with such an amazing open source software. I am writing here in order to ask some questions about authentication possibilities with VerneMQ. I have started implementing SSL Server side authentication and managed to authenticate server successfully when using only Root CA. However I have bumped into some authentication problems when changing the Root CA with Certificate Chain consisting of one Intermediate CA (signed by Root CA) and Root CA. Is it possible to authenticate server to a certificate chain with VerneMQ? If yes, is it also possible to authenticate clients to different certificate chains than servers (since clients would be certified by different intermediate CA)?
So the main idea once again is:

Root CA can authenticate two Intermediate CAs which would authenticate clients and servers separately.
During each connection between clients and servers/brokers they would have to authenticate each other to different CA chains (because of different Intermediate CAs).

I hope the explanation is clear. Thanks a lot in advance!
Certificate chains with intermediate CA explained: https://jamielinux.com/docs/openssl-certificate-authority/index.html

@tomcis thanks for your question!
I'll have to look into it; I apologise that I haven't found time yet. VerneMQ SSL capabilities are basically defined by what the underlying Erlang system's SSL capabilities are. Should VerneMQ support what you have described? is it standard procedure in other words?

@ioolkos
Thank you for your answer! I expect VerneMQ to support Certificate Chains since, as far as I see, it is implemented in Erlang by default (http://erlang.org/doc/man/ssl.html ; search depth), depth is set to 1 which means one Intermediate CA is allowed in the chain. However I did not manage to make it work yet. Also my other part of the question was: is it possible to define different Root or Intermediate CA (different than server) to authenticate clients in the server/broker?  I assume now both server and client are authenticated to the same CA since there is only one CA-file option in the config (which is specifically related to the server):
listener.ssl.cafile = /etc/ssl/cacerts.pem
and everything what can be found concerning client authentication is this:
listener.ssl.require_certificate = on

Hi @tomcis
VerneMQ should support intermediate CAs with no problem. There's also a (hidden) option to set the depth on a listener with listener.ssl.depth = 3 (see https://github.com/erlio/vmq_server/pull/114).
I'm not sure I understand the second part of the question?

Thank you very much for you reply @larshesel
Sorry for my late reply - in the meantime, I have been trying many different configurations of interemediate certificates (https://jamielinux.com/docs/openssl-certificate-authority/index.html). Finally, I have managed to make an intermediate certificate work once (by the way, it also worked without changing the depth since I use only one IntermediateCA and listener.ssl.depth is by default equal to 1). However my problem still persists since I cannot reproduce my results (chain configuration) again and make it work with an intermediate certificate.
What is interesting though, is all kinds of configuration of CA-Chain worked for a different broker (namely, Mosquitto Broker - when trying to connect from an external Mosquitto client through SSL). It seems that VerneMQ is very picky on that and just rejects everything. Do you have any idea? Maybe Erlang is more strict on the Certificate Chain checking itself (maybe CN/FQDN for Root CA or Intermediate CA always has to match the same server, or any other constraint)? (using only Root CA without Intermediate CA to sign a server certificate always works for me though).
This is the result when I try to connect from a Mosquitto client to the VerneMQ broker (unfortunatelly, there is no extensive debugging mechanism). It gets into a halting state:
ubuntu@ip-172-31-29-239:~$ sudo mosquitto_pub -d --cafile ca-chain.cert.pem -h ec2-34-215-140-8.us-west-2.compute.amazonaws.com -t "test" -m "hello" -p 8883
Client mosqpub|1937-ip-172-31- sending CONNECT

Part #2
Sorry for my bad explanation.. I hope this image clarifies the wanted certificate architecture:

I think this seems to be possible now by inputting CA-Chain #1 when sending a client connecion request to a broker, and defining CA-Chain #2 in the broker itself under the listener.ssl.cafile. However chains do not work for me yet (as described already before) thus I cannot test it yet..
Any help would be appreciated a lot!

Wow, thanks!
If you made it work once, then it should work in principle, right?
is it possible to use openssl s_client to see if any other errors come up?
Yes, Erlang TLS is super picky. (seen a lot of stuff, order, whitespace problems in certs, you name it). But I can't really judge the details here.
Maybe we should ask some Erlang folks for ideas?

@ioolkos, thanks for all the support!
I have solved most of my problems already, thus I think it would be wise to share it with others since I, myself, have wasted too much time on that.
The certificate problems were basically related to the permissions of the folder where my private keys were in (namely, private/ folder). I guess Mosquitto Broker might have different access rights than VerneMQ thus it was able to get the private key and run the SSL, however VerneMQ was always throwing a TLS error. Giving execute public rights for the folder made it work.
After solving certificate issues I have also managed to implement the above-mentioned architecture. In general, Erlang written brokers have a bit different SSL authentication structure, however, surprisingly, it allowed quite some freedom which made this architecture possible.
Thanks for everyone, and at least for now - I think this can be closed.

Wow, cool you found the problem! Let us know if you run into other issues!

Hi @tomcis and @larshesel. I'm having a similar issue with intermediate CA certificates. I too set the hidden config listener.ssl.depth=2 but I am still receiving an unknown ca handshake error when my MQTT client sends its certificate. The interesting part is if I send the entire cert chain with the client cert request (using openssl s_client) then vernemq accepts the client certificate. It won't accept it when it's only the client certificate that's been signed by the intermediate CA. The server is configured with a cafile that is the intermediate CA + root CA certificate. The difference in my setup than with @tomcis's setup is that my intermediate CA has signed both the server cert and the client cert.
Hope you all have some tricks up your sleeves :) I think the behavior of my MQTT client (sending only the client cert and not the whole chain) is the correct and desired functionality. It just appears that Erlang is not verifying it against the provides cafile certs, even with an appropriate depth configured.

I really have hard time working with Vernemq, I am on cpanel based server, and wss is somehow not working and throwing below error - attached is the config file, not sure what to do, tried a lot but still looking for a solution. can some one please help
vernemq.txt
WebSocket connection to 'wss://dev.dollarexch.com:8443/mqtt' failed: Error in connection establishment: net::ERR_CERT_AUTHORITY_INVALID

Hi @tomcis, @larshesel
I have followed all the steps from the very beginning of this post. I wan't not able to succeed any further. I am exhausted trying various options to make VerneMQ broker work with Root & Intermediate Key pairs.
I have the same set of questions you had previously. I am again mentioning it here.
Is it possible to authenticate server to a certificate chain with VerneMQ? If yes, is it also possible to authenticate clients to different certificate chains than servers (since clients would be certified by different intermediate CA)?
So the main idea once again is:

Root CA can authenticate two Intermediate CAs which would authenticate clients and servers separately.

During each connection between clients and servers/brokers they would have to authenticate each other to different CA chains (because of different Intermediate CAs).

Certificate chains with intermediate CA explained: https://jamielinux.com/docs/openssl-certificate-authority/index.html
Here is the directory listing's of the certificates, that I created following the article from

Just to avoid all permission issues, I created the below certificates in /root/ca folder and copied over to /home/osboxes/vmq-certs/
Also for everything to look easy, I gave the same passwords to all certificates as "root"
Root private Key

Root Certificate:

Directory Structure for Intermediate Certificates:

Intermediate Keys:

Intermediate Certificates:

As per the documentation from here

Created server.cert.pem for VerneMQ broker
Created client.cert.pem for connecting to VerneMQ broker via MQTT.fx UI client

Following the VerneMQ documentation, using the vmq-passwd tool I created a user "root" and password as "root"
Here are the values that I set in /etc/vernemq.conf

allow_anonymous = off
allow_multiple_sessions = on
listener.ssl.default = <IP_ADDRESS>:8883
listener.ssl.cafile = /home/osboxes/vmq-certs/intermediate/certs/ca-chain.cert.pem
listener.ssl.certfile = /home/osboxes/vmq-certs/intermediate/certs/server.cert.pem
listener.ssl.keyfile = /home/osboxes/vmq-certs/intermediate/private/server.key.pem
listener.ssl.require_certificate = on
listener.ssl.tls_version = tlsv1.2
plugins.vmq_passwd = on
plugins.vmq_acl = on

Here is what I see from the MQTT.fx UI client, with root:root  "User Credentials tab"

Also, if I change the SSL/TLS option from "Self Signed Certificate" to "CA Certificate file".

Also, here is the vmq.acl I have

What are the other possible options that I need to try to make this work?
Is that something to do with vmq.passwd, which is encrypted and the MQTT.fx client does not decrypt it properly with the root/intermediate certificate pairs? If that was the case, then why would it work for the below?
However, I was able to make it work with 2 different ways following this git comment post https://github.com/emqtt/emqttd/issues/562#issuecomment-221500588

With CA Certificate file option in MQTT.fx client and User Credentials (root:root) in MQTT.fx UI client.

With Self Signed Certificate option in MQTT.fx client and User Credentials (root:root) in MQTT.fx UI client.

Really appreciate if I can get any suggestions/inputs or help on how to solve this with Root/Intermediate Certificates.
Let me know if I can provide you with more details you may need from me.
Thanks,
Rakesh


Webpack: "ERROR: [h3] write EPIPE"

Version

@nuxtjs/tailwindcss: ^5.0.4
nuxt: 3.0.0-rc.2
@nuxt/webpack-builder: ^3.0.0-rc.2

Reproduction Link
https://codesandbox.io/s/nostalgic-snow-5m605u
Steps to reproduce

npx nuxi init nuxt-app
cd nuxt-app
yarn install
yarn add --dev @nuxt/webpack-builder @nuxtjs/tailwindcss
Add builder: "webpack" to nuxt.config.ts
Add modules: ["@nuxtjs/tailwindcss"] to nuxt.config.ts
yarn dev
Open project url

What is Expected?
It should work without problems displaying the project content and having tailwindcss support.
What is actually happening?
The project is not built and the following errors are displayed:
Terminal:
ℹ Merging Tailwind config from ~/tailwind.config.js  nuxt:tailwindcss 14:17:12
ℹ Tailwind Viewer: http://localhost:3000/_tailwind/  nuxt:tailwindcss 14:17:12
✔ Vite server built in 3243ms                                         14:17:13
✔ Nitro built in 2753 ms                                        nitro 14:17:18
Nuxt CLI v3.0.0-rc.2                                                  14:17:18
                                                                      14:17:18
  > Local:    http://localhost:3000/
  > Network:  http://<IP_ADDRESS>:3000/

<i> [webpack-dev-middleware] wait until bundle finished: /

 ERROR  [h3] write EPIPE                                              14:20:33

  at afterWriteDispatched (internal/stream_base_commons.js:156:25)
  at writeGeneric (internal/stream_base_commons.js:147:3)
  at Socket._writeGeneric (net.js:798:11)
  at Socket.connect (net.js:780:12)
  at Object.onceWrapper (events.js:519:28)
  at Socket.emit (events.js:412:35)
  at Socket.emit (domain.js:475:12)
  at PipeConnectWrap.afterConnect [as oncomplete] (net.js:1145:10)

Web browser:
{
  "statusCode": 500,
  "statusMessage": "H3Error",
  "stack": []
}

Notes

Setting builder to vite makes everything work again. (But I need webpack)

@kolessios is there a workaround for this issue ? I'm also facing the same issue with nuxt3-rc3

@kolessios Your logs indicate that "Vite" is being used. Did you end up making it work with vite?
Faced similar problems with webpack builder. Ended up just importing all the dependencies for tailwindcess manually (it looks like this module is just a wrapper around some npm packages and config parameters anyway)
Followed steps depicted https://stackoverflow.com/questions/70302520/nuxtjs-v3-and-tailwindcss-v3-postcss8-not-compatible
But made sure to remove this statement:
 './nuxt.config.{js,ts}',
After that it worked without problem (not even sure why we need to include nuxt.config to scan for css classes?) You probably dont need this either:
'./assets/**/*.{vue,js,css}'

Hi, I have a similar error :
This is the case when I run the app in docker-compose hosted on mac machine,
When I run the app in docker-compose hosted on linux machine, it seems working fine.
  ERROR  [h3] [unhandled] write EPIPE

   at createError (node_modules/h3/dist/index.mjs:196:15)
   at nodeHandler (node_modules/h3/dist/index.mjs:386:21)
   at processTicksAndRejections (node:internal/process/task_queues:96:5)

In browser :
{
  "statusCode": 500,
  "statusMessage": "Internal Server Error",
  "stack": []
}

It occurs when the app is building, and it remains a window with the last app running from the last docker-compose up, and at random moments when I use the application.
In terms of libraries, I use tailwindcss and many other dependencies with vite builder

Closing this issue as it is believed to be resolved/stale now - please feel free to comment if it is still an issue in the latest version of the module.

I have same error when using upload image of ant design vue and nuxt 3


Use insert value get relocatable

TITLE
Description
Use vm_proxy's methods: get_relocatable & insert_value
Checklist

[ ] Linked to Github Issue
[ ] Unit tests added
[ ] Integration tests added.
[ ] This change requires new documentation.

[ ] Documentation has been added/updated.

Codecov Report

Merging #464 (06a208f) into main (555e2f8) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #464      +/-   ##
==========================================
- Coverage   96.62%   96.62%   -0.01%
==========================================
  Files          54       54
  Lines        9160     9154       -6
==========================================
- Hits         8851     8845       -6
  Misses        309      309

Impacted Files
Coverage Δ

src/hint_processor/hint_processor_utils.rs
68.00% <ø> (ø)

...int_processor/builtin_hint_processor/hint_utils.rs
90.32% <100.00%> (ø)

...cessor/builtin_hint_processor/squash_dict_utils.rs
99.76% <100.00%> (-0.01%)
:arrow_down:

..._processor/builtin_hint_processor/uint256_utils.rs
100.00% <100.00%> (ø)

src/hint_processor/builtin_hint_processor/usort.rs
94.52% <100.00%> (-0.15%)
:arrow_down:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more