review seemingly inefficient notedata iterators

another reminder to myself to do something i'll never end up doing

ok this is basically never going to happen


gradle aggregated coverage console log and html location

Description
issue #11839

It's my first time really working on gradle script so I'm pretty uncertain whether I've done something wrong :) I tested with ./gradlew coverage and it works as expected.

Add java plugin to :lucene so that it will apply the "org.barfuin.gradle.jacocolog" plugin as well
coverage depend on jacocoAggregatedReport so it will print aggregated coverage, for subproject it just print out the  coverage for that module
Show html location only for parent project (which is only lucene?) because the printout for subproject also point to the same location, and the report is already aggregated.

Thanks @dweiss! I was having some hard time understanding the dependencies between plugins so thank you for jumping out and help! I tested the change and it looks good to me.

but it triggers all test tasks to run (including those from hunspell that are not run by default!)

Do you think this will become a problem? If not I guess we can just push it?

Now task dependencies seem to work as I'd expect them to. I don't know how to read the coverage information at the top level when one only runs a set of subprojects. For example:
gradlew test -p lucene\analysis\kuromoji :jacocoAggregatedReport -Ptests.coverage=true

results in:

The "aggregated" view only makes sense when you actually run all the tests.... I think this may be weird to just me though, I wouldn't worry about it.

Now task dependencies seem to work as I'd expect them to. I don't know how to read the coverage information at the top level when one only runs a set of subprojects. For example:
gradlew test -p lucene\analysis\kuromoji :jacocoAggregatedReport -Ptests.coverage=true

results in:

The "aggregated" view only makes sense when you actually run all the tests.... I think this may be weird to just me though, I wouldn't worry about it.

The "aggregated" view only makes sense when you actually run all the tests.... I think this may be weird to just me though, I wouldn't worry about it.

Maybe there is some way to detect that only specific project was run (e.g. the -p xxx flag was specified), and omit the aggregate report? If you only run tests for a single project you'll see the per-project coverage already and have what you need.

oh - it will work that way if you run coverage on a subproject (see my explicit top-level task above). even then it can be a bit weird if you use the filter (--tests) but I guess it's not going to be surprising if you're familiar with jacoco (I'm not that familiar, I admit).

Personally I don't think its confusing with the filter (--tests). When writing new functionality/tests, I like to iterate and see what branches etc of the code the new test is covering. jacoco also has plugins for IDEs that make that workflow easy too.
My basic assumption is that jacoco agent just makes a bitset with on/off bit corresponding to each bytecode, so you can't see fancy stuff like "how many times this line of app code was hit in tests" or "which tests tested this". Clover did some of that, but with insane resource usage.
So for me being able to use it with --tests to see exactly what the specific test(s) covered is really useful, because you don't exactly have an alternate way to see that info with jacoco.

That's fine for me. And I think this patch also fixes the problem of test tasks running needlessly - I'm +1 to add it, I don't think I have anything else to contribute here (?).

Again, thank you @dweiss a lot for helping! I'll push it.


[KYUUBI #6615] Make Jetty sending server version in response configurable

:mag: Description
Issue References 🔗

This pull request fixes #6615
Describe Your Solution 🔧
Add a config item that controls whether Jetty should send its version in response.
Sending Jetty version could be disabled by calling HttpConfiguration::setSendServerVersion(false)
Types of changes :bookmark:

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Test Plan 🧪
Compiled and tested manually.

Checklist 📝

[ ] This patch was not authored or co-authored using Generative Tooling

Be nice. Be informative.

@paul8263 please run dev/gen/gen_all_config_docs.sh to regenerate docs.

@paul8263 please run dev/gen/gen_all_config_docs.sh to regenerate docs.

Thanks. It should be good as there is a way to generate the doc. In the previous commit I editted the doc manually, but put the new configuration in the wrong chapter. The latest commit should be correct.

Codecov Report
Attention: Patch coverage is 0% with 12 lines in your changes missing coverage. Please review.

Project coverage is 0.00%. Comparing base (d2ead6b) to head (c1567fd).
Report is 3 commits behind head on master.

Files
Patch %
Lines

...in/scala/org/apache/kyuubi/config/KyuubiConf.scala
0.00%
5 Missing :warning:

...ache/kyuubi/server/KyuubiRestFrontendService.scala
0.00%
2 Missing :warning:

...che/kyuubi/server/KyuubiTHttpFrontendService.scala
0.00%
2 Missing :warning:

...che/kyuubi/server/KyuubiTrinoFrontendService.scala
0.00%
2 Missing :warning:

...cala/org/apache/kyuubi/server/ui/JettyServer.scala
0.00%
1 Missing :warning:

Additional details and impacted files
@@          Coverage Diff           @@
##           master   #6616   +/-   ##
======================================
  Coverage    0.00%   0.00%
======================================
  Files         677     677
  Lines       41907   41917   +10
  Branches     5721    5721
======================================
- Misses      41907   41917   +10

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Thanks, merged to master/1.9


More error handling

PR into https://github.com/mandrean/cw-optimizoor/pull/22
Hey @de-husk
Permission denied (os error 13)

it's still not clean enough to me. So I decided to come for a little help, love this project
What you think about that? tbh feels like a point where it's a great time for creating an error type

Thanks! Looks good, Ill merge.

tbh feels like a point where it's a great time for creating an error type
Yeah, I agree, but I use this project as a library so I have a much greater need for opaque error types than the average cw-optimizoor user, so I get it if they dont want to make that jump.


Compression dropdown not updated when changing source file

Noticeable only when changing file again before processing it...

Fixed.


Issue with removeLastObject in NSMutableArray

NSMutableArray *array = [[NSMutableArray alloc] init];
[array removeLastObject];
NSInteger count = [array count]; //count - will be -1, but should be 0.
// [array removeLastObject] should not effect on array, if it’s empty
As per the above code, and the implementation of removeLastObject in NSCFArray.mm, it seems that there may be an implementation issue with CFArrayRemoveValueAtIndex.

@param idx The index from which to remove the value. If the index is
	outside the index space of the array (0 to N-1 inclusive,
	where N is the count of the array before the operation), the
	behavior is undefined.

Sounds like we should do a parameter check before calling into CF there.

Also other methods that use CF.  The compat tests should catch these issues, assuming the tests exist.


Possible reason for partition test would fail

We are going to launch a Testnet that testing the merge of forked blockchains very soon. I think this test would probably fail.
image we have 2 long chains, and they have been diverged for more than two epoch. And Assuming their roots and best tips are in the same epoch.
Assuming
the min_epoch_length of nodes in chain A is 30 and
the min_epoch_length of nodes in chain B is 40.
The following 2 scenarios would both prevent fork being merged:

Let's say nodes in chain A received a block from chain B, then nodes in chain A would take it, but bootstrap would not be trigger if the difference between blockchain_length of A and B is not great enough. The block would be added to the catchup scheduler because it has no parent in the frontier of A and catchup would fail. And thus the network would keep forking.

Let's say nodes in chain B received a block from chain A, then nodes in chain B would always ban the sender because that block would not be selected over the root of the nodes in chain B. Eventually every node in chain B would ban nodes in chain A and the network would keep forked.

We should at least modify the rule for bootstrap before doing this test because bootstrap would not happen if two chains are around the same length.

@ghost-not-in-the-shell if the nodes are diverged for less than an epoch, would it work?
I was only planning on being isolated for an hour or so. (way less than an epoch on testnet)

@ghost-not-in-the-shell if the nodes are diverged for less than an epoch, would it work?
I was only planning on being isolated for an hour or so. (way less than an epoch on testnet)

Things would be fine if nodes are diverged shortly. If they still have the same root, then bootstrap would not be required. But if the root is different (which means we really have two different chains on the network), then things would break.

I give a more detailed analysis in #3445.

Let's have a discussion about this?

Let's have a discussion about this?

Let's have a discussion about this?

Sure, we can schedule a short meeting on this.


Paste Elements always as Elements even if we are writting in a textarea

In App.tsx:2244 it checks if we are about to paste inside a text area and if so, it just returns from this function.
In App.tsx:2260 excalidraw parses the clipboard data and it may return valid excalidraw elements.
That let file = ... in App.tsx:2263 is there because they were losing files from the clipboard because of... the comment tries to explain it...
parseClipboardEvent and parseClipboard were async functions but they didn't have any await inside them.
So there is no need for that let file at all... I have moved those 2 lines together anyway to avoid more refactoring, but the only thing I need is to parse the clipboard content to see if there are elements inside and not return if so.

This may not be a full/proper solution so I have created an @alkemio/excalidraw package version @0.17.0-alkemio-3-beta to test it properly

Closed in favor of #5


Removing GIFs from readme files

As we know that,
A readme file lets you know about the repo as well as attracting contributors to contribute in it.
But, readme file included in your repo is loosing grip in both of the roles, because of the GIFs mentioned in it,
They create an informal image of your repo, which is not good,
In order to maintain formality of your readme file,
Let me remove the gifs and insert some catching sentences instead.
This is under crosswoc,

Hey @kmryashasvi I don't want to remove GIFs!!

okay


feature: matchmaking agent - upgrade to TX EDC 0.7.3

WHAT
aligns the matchmaking agent with TX ED 0.7.3
WHY
compatibility of the matchmaking agent with the release version of the connector (esp: the management api) is required for a full agent protocol roundtrip.
FURTHER NOTES
DEPS have been upped. No IP checks necessary

Hey @drcgjung, I've approved the PR, can I also merge it?


Unique WorldId

Objective
Fixes these issues:

WorldIds currently aren't necessarily unique

I want to guarantee that they're unique to safeguard my librarified version of https://github.com/bevyengine/bevy/discussions/2805
There probably hasn't been a collision yet, but they could technically collide

SystemId isn't used for anything

It's no longer used now that Locals are stored within the System.

bevy_ecs depends on rand

Solution

Instead of randomly generating WorldIds, just use an incrementing atomic counter, panicing on overflow.
Remove SystemId

We do need to allow Locals for exclusive systems at some point, but exclusive systems couldn't access their own SystemId anyway.

Now that these don't depend on rand, move it to a dev-dependency

Todo
Determine if WorldId should be u32 based instead

Regarding u64 vs u32 for WorldId, I do have strong feelings. This is an atomic variable, which means that it relies on appropriate support for atomics from the underlying CPU architecture. There are many platforms that do not support 64-bit atomics, but do support 32-bit atomics. Most 32-bit architectures / compilation targets are like that. If we require 64-bit atomics for bevy, we are restricting portability to such platforms/architectures.
As @alice-i-cecile said, it is unlikely to break the limit of u32. It is very doubtful that someone would want to have more than ~4.7 billion Worlds.
Whereas portability and platform support is an actual problem with actual consequences. Let's not needlessly limit the kinds of devices that bevy can run on.

Hmm, I hadn't considered that - I wonder if there should be a clippy lint for that (beyond just using the more general disallowed function)
We should use AtomicUsize then.

I dig these changes. I do think that ultimately we might need a unique SystemId for "manually triggered systems" and "reactions", but I'm happy to just re-add that if/when its actually needed. SystemId has been dead code since bevy_ecs's inception. Removing it makes sense.

bors r+

Lol I have a nasty habit of  not checking CI before bors-ing. You should just swap out the WorldId::new() constructor for a Default impl.

That's annoying - I even knew that lint would trigger but forgot to deal with it.
I explicitly chose not to make it a Default impl, because it doesn't really make sense to have a WorldId seperated from a World. Additionally, the default value isn't really a default as such imo
I still expose the constructor function publicly because it could be used e.g. for tests in external crates, although I'm not certain that's really needed.

bors r+


Contribution from PR#825

This solves the issue mentioned in #825.
@meiamsome Thanks for the quick fix.

@nilsweb oops, my fault :/

🎉


Procedures: Proposing new technical ideas

This document would cover what to do when you want to introduce new best practices or a new technology. It would include subtopics such as:

Writing a technical proposal
Gathering user research via Slack surveys
Creating a proof of concept
Garnering support from other team members

@mcmire and @Gudahtt do we still need this or does the ADR process do this now? Or does this change based on having the ADR process.

Closing as addressed with the ADR process.


is this still supported? If yes didnt get any output of Multicounter

is this still supported? If yes didnt get any output of Multicounter

Hello @JanWeskamp
Thanks for the report and the patience.
It used to be that the streamer had to list themself as a trusted user, but now that shouldn't be necessary anymore.

Thanks seems to work perfectly right now


Remove sheet

Please add functionality to remove sheet from workbook
if possible both using postion and name
https://openpyxl.readthedocs.io/en/stable/api/openpyxl.workbook.workbook.html#openpyxl.workbook.workbook.Workbook.remove

pull request with this option added #16


chore: remove unnecessary import and {}

remove some unnecessary import
we not supprot scala 2.12, so we don't need import Seq

I have been rebeased and exec sbt clean compile with java17 locally

@laglangyue thanks, please run sbt scalafmtAll to format according to this repo's rules.

@laglangyue thanks, please run sbt scalafmtAll to format according to this repo's rules.

done


Bug in joint probability calculator when number of favourable outcome is 0

Describe the bug
When the number of favourable outcomes is 0 it shows an error but the probability can be 0 so the output should be 0 not an error.
Please assign this to me.

@sairish2001 Please assign this to me.

Go ahead
Deadline 4 April,2021 (11:59 PM IST)


Pushed work in fetchJsonRevDiffs() and fetchJsonBranchDiffs() from NCubeController to NCubeManager

Please squash commits. Not sure why it has so many.

@jsnyder4 It does the same for me if I use the same branch in my intellij (without new checkout from master) and push to a new GH branch.


Serve local client-config.json if it exists

Now that we request client-config.json, I've been wondering whether it'd be possible to remove npm run dev:oidc. That command sets a single option in the config (oidcEnabled), but there are several other options in the config that a developer might want to set. The idea of this PR is that a developer can create a local client-config.json to match whatever they're working on, and those options won't show up in version control. Modifying src/config.js would have much the same effect, but it has the downside that it shows up in version control.
Closes #1034.
Before submitting this PR, please make sure you have:

[x] run npm run test and npm run lint and confirmed all checks still pass OR confirm CircleCI build passes
[x] verified that any code or assets from external sources are properly credited in comments or that everything is internally sourced

I like this approach because it's more consistent with how production behaves.


Auto-collapse IVP when in Integration Editor

This is a...

[ x] Feature request
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report
[ ] Documentation issue or request

Description
IVP should auto-collapse when users are in Integration Editor to allow for optimal presentation for the create integration workflow.

@dongniwang just to clarify - do you mean that the left vertical nav should collapse when the user is editing/creating an integration?

@amysueg - yes.


W-Bomber fails with "Uncaught TypeError"

What happened?
The extension simply doesn't work.
Steps to Reproduce

Download and unpack the extension
Head over to WhatsApp Web and SignIn
Trigger the Extension, nothing happens

RCA
The HTML node elements have been changed/updated within the web application. Due to this, the extension errors out with the below
Uncaught TypeError: Cannot read properties of null

Solution
Update the class/node names within the JS file

The issue might likely arise in near-future post updating the scripts.
Env Staged
Host: tools.0x4e.corp/w-bomber/
Extension: ffbpielifadlkocllpcikioclpldgfdk::Unpacked extension

No plans to carry WBomber forward, closing issue as of now.


tesstrain.sh script exits with error

Short description
I am trying to train Tesseract on Akkadian language. The language-specific.sh script was modified accordingly. When converting the training text to TIFF images, the text2image program crashes.
Environment

Tesseract Version: 3.04.01
Commit Number: the standard package in Ubuntu, package version 3.04.01-4, commit unknown
Platform: Linux ubuntu-xenial 4.4.0-130-generic #156-Ubuntu SMP Thu Jun 14 08:53:28 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

The environment was created using Vagrant. The commands are started on command line without GUI environment.
Running tesseract -v produces following output:
tesseract 3.04.01
 leptonica-1.73
  libgif 5.1.2 : libjpeg 8d (libjpeg-turbo 1.4.2) : libpng 1.2.54 : libtiff 4.0.6 : zlib 1.2.8 : libwebp 0.4.4 : libopenjp2 2.1.0

Current Behavior:
When running tesstrain.sh with these command
./tesstrain.sh --lang akk --training_text corpus-12pt.txt --tessdata_dir /usr/share/tesseract-ocr/tessdata --langdata_dir ../langdata --fonts_dir /usr/share/fonts --fontlist "CuneiformNAOutline Medium" "CuneiformOB" --output_dir .

the text2image crashes on every font with this message:
cluster_text.size() == start_byte_to_box.size():Error:Assert failed:in file stringrenderer.cpp, line 541

As a result, no box files are generated, so tesstrain.sh exits with these messages:
ERROR: /tmp/tmp.XSb02nt10d/akk/akk.CuneiformOB.exp0.box does not exist or is not readable
ERROR: /tmp/tmp.XSb02nt10d/akk/akk.CuneiformNAOutline_Medium.exp0.box does not exist or is not readable

Expected Behavior:
tesstrain.sh should create the box files and proceed with training.
Attachments:
I attached all files used: akktrain.zip.
The fonts are hosted here, but for the sake of completeness the .ttf-files are included in the archive; they shoud be moved to /usr/share/fonts.

Please try with latest version of tesseract.

Hello @Shreeshrii,
I ran the tesstrain.sh with the same options under Ubuntu Bionic (in a Docker container) and got the same results, as well as the attached coredump.
The version information is
tesseract 4.0.0-beta.1
 leptonica-1.75.3
  libgif 5.1.4 : libjpeg 8d (libjpeg-turbo 1.5.2) : libpng 1.6.34 : libtiff 4.0.9 : zlib 1.2.11 : libwebp 0.6.1 : libope
njp2 2.3.0

 Found AVX2
 Found AVX
 Found SSE

P.S.: the language-specific.sh script is attached too.

Save your training text as utf-8 (currently it seems to be in a different encoding -ANSI which does not display correctly).

file corpus-12pt.txt recognizes UTF-8 encoding. Which software do you use to look at the text?
If you choose the right encoding, this image should appear:

I used notepad++ on windows. Yes, it displays correctly after changing encoding to utf-8.
I think the problem is being caused by extra long lines. I saved file as utf-8 and split the long lines to a smaller size and it seems to be working ok.
Make sure you are using the new version of tesstrain.sh (uninstall the version from tesseract 3).

@ stweil This assert seems to be related to the size of training_text line. Is it possible to have a more descriptive error message, if that is indeed the case.
cluster_text.size() == start_byte_to_box.size():Error:Assert failed:in file stringrenderer.cpp, line 541

The issue #765 seems to be (roughly) related to this one.

Dear @Shreeshrii ,
thank you very much for your help! The training worked after rewrapping (I wrote a short script in Python 3, as it works beautifully with utf-8 documents; you can find it here), but I had to rewrap the corpus by 35 characters per line.
The widths of 10, 20, 30, 40, 50, 60 and 70 characters per line did not work. But this is another issue, I think.
To be honest I both followed and disregarded your advice about using training scripts for Tesseract4 only at the same time. As a matter of fact, I need to use Tesseract3, thus I tested the old training scripts first. Nevertheless, I created a Docker container with Ubuntu Bionic and ran the training script for and with Tesseract4. It worked as well as with Tesseract3.
Hence we can regard the rewrapping of a corpus file as an official workaround for this issue. Shall I edit the wiki pages about training with Tesseract3 and Tesseract4?

we can regard the rewrapping of a corpus file as an official workaround
for this issue.

OK

The widths of 10, 20, 30, 40, 50, 60 and 70 characters per line did not
work. But this is another issue, I think. I had to rewrap the corpus by 35
characters per line.

I think 35 characters per line is dependent on the size of akkadian
characters in the fonts that were used. Don't think that will be the case
globally for all languages.

As a matter of fact, I need to use Tesseract3, thus I tested the old
training scripts first.

Sure. My suggestion was geared more towards using tesseract4.
What kind of accuracy are you getting with the akk traineddata with
tesseract3?
On Thu, Aug 2, 2018 at 2:01 AM Wincent Balin<EMAIL_ADDRESS>wrote:

Dear @Shreeshrii https://github.com/Shreeshrii ,
thank you very much for your help! The training worked after rewrapping (I
wrote a short script in Python 3, as it works beautifully with utf-8
documents; you can find it here
https://gist.github.com/wincentbalin/85707ce703b1e4bc0737ed569fb16bea),
but I had to rewrap the corpus by 35 characters per line.
The widths of 10, 20, 30, 40, 50, 60 and 70 characters per line did not
work. But this is another issue, I think.
To be honest I both followed and disregarded your advice about using
training scripts for Tesseract4 only at the same time. As a matter of fact,
I need to use Tesseract3, thus I tested the old training scripts first.
Nevertheless, I created a Docker container with Ubuntu Bionic and ran the
training script for and with Tesseract4. It worked as well as with
Tesseract3.
Hence we can regard the rewrapping of a corpus file as an official
workaround for this issue. Shall I edit the wiki pages about training with
Tesseract3 and Tesseract4?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/1781#issuecomment-409711949,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE2_ozf7-j7YdFFuBuPcW_6EdZexO-Ckks5uMhAkgaJpZM4VR-Rj
.

--

भजन - कीर्तन - आरती @ http://bhajans.ramparivar.com

https://en.wikipedia.org/wiki/Cuneiform_script
It will be hard to get a good accuracy on >1900 years old material.

Is this with tesseract 3.05? Training for legacy engine?
I had done a training run for LSTM but didn't test it. I will share it in a
day or two, I am traveling now.
If you can make your test images and ground truth available some place, I
can check accuracy too.
On Wed, 19 Sep 2018, 20:53 Wincent Balin<EMAIL_ADDRESS>wrote:

What kind of accuracy are you getting with the akk traineddata with
tesseract3?
Currently the WER is around 10 per cent, but sometimes I got it lower.
The program I use takes random words from the wordlist, creates texts from
it and saves the text into an image using text2image. Then tesseract is
used to recognize the text back and the WER of the result in comparison to
the original text is calculated.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tesseract-ocr/tesseract/issues/1781#issuecomment-422845120,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AE2_owq8wFdtZIlOIjSlTHb65rpmAAqyks5ucmFrgaJpZM4VR-Rj
.

See note above code section that cause crash:
 // There is a subtle bug in the cluster text reported by the PangoLayoutIter
  // on ligatured characters (eg. The word "Lam-Aliph" in arabic). To work
  // around this, we use text reported using the PangoGlyphIter which is
  // accurate.
  // TODO(ranjith): Revisit whether this is still needed in newer versions of
  // pango.

Currently the WER is around 10 per cent, but sometimes I got it lower.

I looked at the LSTM training results that I have. They have CER of less
than 10% and WER of 15%.

Issue #765 is a duplicate.

@stweil : can you provide font and text that failed for you?

@zdenop The first post about issue has the info you want.
Attachments:

I attached all files used: akktrain.zip.
The fonts are hosted here, but for the sake of completeness the .ttf-files are included in the archive; they shoud be moved to /usr/share/fonts.

@wincentbalin had a workaround the problem too..

Hence we can regard the rewrapping of a corpus file as an official workaround for this issue. Shall I edit the wiki pages about training Tesseract3 and Tesseract4?

~/tessdata_akk$ valgrind --tool=memcheck /usr/local/bin/text2image --fontconfig_tmpdir=/tmp/font_tmp.opjpN7f94T --fonts_dir=../.fonts --strip_unrenderable_words --leading=32 --char_spacing=0.0 --exposure=-1 --outputbase=/tmp/tmp.tH84CXo6fq/akk/akk.CuneiformOB.exp-1 --max_pages=0 --font=CuneiformOB --text=./langdata/akk/corpus-12pt.txt
==3121== Memcheck, a memory error detector
==3121== Copyright (C) 2002-2015, and GNU GPL'd, by Julian Seward et al.
==3121== Using Valgrind-3.11.0 and LibVEX; rerun with -h for copyright info
==3121== Command: /usr/local/bin/text2image --fontconfig_tmpdir=/tmp/font_tmp.opjpN7f94T --fonts_dir=../.fonts --strip_unrenderable_words --leading=32 --char_spacing=0.0 --exposure=-1 --outputbase=/tmp/tmp.tH84CXo6fq/akk/akk.CuneiformOB.exp-1 --max_pages=0 --font=CuneiformOB --text=./langdata/akk/corpus-12pt.txt
==3121==
Rendered page 0 to file /tmp/tmp.tH84CXo6fq/akk/akk.CuneiformOB.exp-1.tif
Rendered page 1 to file /tmp/tmp.tH84CXo6fq/akk/akk.CuneiformOB.exp-1.tif
Rendered page 2 to file /tmp/tmp.tH84CXo6fq/akk/akk.CuneiformOB.exp-1.tif
Rendered page 3 to file /tmp/tmp.tH84CXo6fq/akk/akk.CuneiformOB.exp-1.tif
Rendered page 4 to file /tmp/tmp.tH84CXo6fq/akk/akk.CuneiformOB.exp-1.tif
cluster_text.size() == start_byte_to_box.size():Error:Assert failed:in file ../../../src/training/stringrenderer.cpp, line 546
==3121==
==3121== Process terminating with default action of signal 5 (SIGTRAP)
==3121==    at 0x101D7844: ERRCODE::error(char const*, TessErrorLogCode, char const*, ...) const (errcode.cpp:84)
==3121==    by 0x10027487: tesseract::StringRenderer::ComputeClusterBoxes() (stringrenderer.cpp:546)
==3121==    by 0x10028617: tesseract::StringRenderer::RenderToImage(char const*, int, Pix**) (stringrenderer.cpp:806)
==3121==    by 0x10015E1B: Main() (text2image.cpp:632)
==3121==    by 0x1000A0FB: main (text2image.cpp:736)
==3121==
==3121== HEAP SUMMARY:
==3121==     in use at exit: 141,636,503 bytes in 11,076 blocks
==3121==   total heap usage: 258,218 allocs, 247,142 frees, 1,652,783,976 bytes allocated
==3121==
==3121== LEAK SUMMARY:
==3121==    definitely lost: 7,168 bytes in 11 blocks
==3121==    indirectly lost: 12,207 bytes in 474 blocks
==3121==      possibly lost: 1,514 bytes in 21 blocks
==3121==    still reachable: 141,613,430 bytes in 10,559 blocks
==3121==                       of which reachable via heuristic:
==3121==                         length64           : 80 bytes in 2 blocks
==3121==                         newarray           : 1,568 bytes in 18 blocks
==3121==         suppressed: 0 bytes in 0 blocks
==3121== Rerun with --leak-check=full to see details of leaked memory
==3121==
==3121== For counts of detected and suppressed errors, rerun with: -v
==3121== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Trace/breakpoint trap

valgrind --leak-check=full          --show-leak-kinds=all          --track-origins=yes          --log-file=./valgrind-out.txt           /usr/local/bin/text2image --fontconfig_tmpdir=/tmp/font_tmp.opjpN7f94T --fonts_dir=../.fonts --strip_unrenderable_words --leading=32 --char_spacing=0.0 --exposure=-1 --outputbase=/tmp/tmp.tH84CXo6fq/akk/akk.CuneiformOB.exp-1 --max_pages=0 --font=CuneiformOB --text=./langdata/akk/corpus-12pt.txt
valgrind-out.txt

Memory leaks after a fatal assertion are normal: the program terminates immediately without executing destructors or cleaning up memory.

it crash also with pango 1.44.6.
Has anybody latin script based text for reproducing this crash?

Same problem occurred to me.
My workaround is to remove empty lines from training_text.
It worked for me.

واردات از چین

I am trying to train https://1680380.com/view/fc3D/index.html Tesseract on Akkadian language. The language-specific.sh script was modified accordingly. When converting the training text to TIFF images, the text2image program crashes.

Please see https://github.com/Shreeshrii/tesstrain-akk which has the LSTM training input, training steps and resulting traineddata files.
You can change the training text and fonts to customize and further finetune the models.

i have  a question. when I run sh generate_training_data.sh
have an errore: 2: tesstrain.sh: not found
i go to tesseract/src/tesstrain.sh
but it not work


Table is showing with three dots "..." on top left side of the table above it

The sample code for table in ShowReel directory is containing the three dots "...". Which came to my code through careless copy paste.
https://github.com/MauriceConrad/Photon/blob/79c4ed1fbbb4180dcc4207e4f9214e26362e005e/ShowReel/index.html#L402
Closing the issue. Thanks


Dense layer docstring typo fix

Dense layer does matmul(matrix multiplication) for tensors with rank <= 2, not dot product.
It can be easily checked in the code, the call method of the dense layer class has:
x = ops.matmul(inputs, self.kernel)
not
output = activation(dot(input, kernel) + bias)
as in the docstring
It can also be checked by passing rank<=2 inputs of different [-1] dimension to dense layers with variable number of units, which is only possible if dense layers are doing matmul and not dot for rank<=2 tensors.

I see, however it's unambiguous to say matmul instead.

It's unambiguous to put matmul instead, no confusion here.


Peek through

Description of the new feature / enhancement
function to peek through windows, allow people to adjust the transparency of the windows
Scenario when this would be used?
i think it can working really good with the function ''always on top''
Supporting information
No response

/dup #1084


Error page font color

Change quote font color on error page to a darker color to contrast with the background more clearly and be more readable

The app is now a true SPA and there is no navigation so no error page is needed


How can the Gitblit bind to a specific domain?

Hi, my Gitblit works well and I really like it. Currently it can be visited by domain entrance(e.g. http://git.domain.cn) and ip entrance(e.g. http://<IP_ADDRESS>) even though i config this line:  "server.httpBindInterface = git.domain.cn".
In my situation, I want it can be visited by the domain entrance only. How can I do that?
Thank you very much!

Setup a nginx reverse proxy then in your config file add
server {
listen 443; # or 80
server_name <IP_ADDRESS>;
return 444;
}


Support for Spring Boot 3 ConstructorBinding annotation

https://github.com/apple/pkl/blob/a28ef856981d44b861eb6a16ab9bdf23adacf604/pkl-codegen-java/src/main/kotlin/org/pkl/codegen/java/JavaCodeGenerator.kt#L494
Currently Java Code Generator with Spring Boot Configurations generates classes with annotation org.springframework.boot.context.properties.ConstructorBinding.
This was deprecated in Spring Boot 3.0.0 and as of Spring Boot 3.2.0 this has been removed in favour of org.springframework.boot.context.properties.bind.ConstructorBinding.
https://docs.spring.io/spring-boot/docs/3.0.0/api/org/springframework/boot/context/properties/ConstructorBinding.html

To add, while Spring Boot 2 supports both class level annotation and constructor level annotation, Spring Boot 3 requires Constructor level annotation (which optionally can also be omitted). Currently it adds to the Class with no option for adding to the Constructor instead

Makes sense!

@bioball Do both versions need to be supported, or is Boot 3 good enough?

Supporting multiple Spring Boot versions will, at a minimum, require to

add a springBootVersion property to CliJavaCodeGeneratorOptions, CliKotlinCodeGeneratorOptions, JavaCodeGenerator, KotlinCodeGenerator, and CodeGenSpec (Gradle plugin).
improve pkl-spring tests to test against multiple String Boot versions.

@bioball I'd like to send a PR in time for 0.27 but first need a decision.

I don't really have a strong opinion here. @holzensp or @stackoverflow, any thoughts?
@translatenix what's your opinion? Should Pkl remove Spring Boot 2 support?

As OSS support for Boot 2.x ended a year ago and Pkl is cutting edge (0.x), I’d be inclined to drop Boot 2.x support unless you have internal users that can neither update Boot nor stay on Pkl 0.26.

Agree that we can drop support for Boot 2.x. We dropped support for unmaintained Java versions, so it's in line to do the same with Spring.

Enterprise support is running until 2027, but I agree; if folks can't bump their Spring, they'll likely also be fine staying on 0.26 (codegen)

Enterprise support is running until 2027

From the support page I linked to:

Branch
Initial Release
End of OSS Support
End of Enterprise Support

3.0.x
2022-11-24
2023-11-24
2025-02-24

2.7.x
2022-05-19
2023-11-24
2026-12-31


Weather Agent produces an "undefined method" error

Account > Job Management menu shows an error as it can be seen on the following screenshot.
https://drive.google.com/file/d/0B2tXOm0gFdweTTc1Tnd3bkc4NWs/view?usp=sharing
However the agent "SF Weather Agent" does not exist. I have another weather agent called "Wunderground Weather Agent" with ID 1 and that works well. This one has the agent ID 21 which is a false information.
If I delete this background job, it will appear again on the next day.
It looks like some kind of database inconsistency to me.
Here is the stack trace of the error:
                        undefined method `[]' for nil:NilClass
/app/app/models/agents/weather_agent.rb:103:in `wunderground'
/app/app/models/agents/weather_agent.rb:116:in `model'
/app/app/models/agents/weather_agent.rb:77:in `check'
/app/app/jobs/agent_check_job.rb:7:in `perform'
/app/vendor/bundle/ruby/2.2.0/gems/activejob-<IP_ADDRESS>/lib/active_job/execution.rb:32:in `block in perform_now'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:117:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:117:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:555:in `block (2 levels) in compile'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:505:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:505:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:498:in `block (2 levels) in around'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:343:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:343:in `block (2 levels) in simple'
/app/vendor/bundle/ruby/2.2.0/gems/i18n-0.7.0/lib/i18n.rb:257:in `with_locale'
/app/vendor/bundle/ruby/2.2.0/gems/activejob-<IP_ADDRESS>/lib/active_job/translation.rb:7:in `block (2 levels) in <module:Translation>'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:441:in `instance_exec'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:441:in `block in make_lambda'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:342:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:342:in `block in simple'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:497:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:497:in `block in around'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:505:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:505:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:498:in `block (2 levels) in around'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:343:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:343:in `block (2 levels) in simple'
/app/vendor/bundle/ruby/2.2.0/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:23:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:23:in `block (4 levels) in <module:Logging>'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `block in instrument'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications/instrumenter.rb:20:in `instrument'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/notifications.rb:164:in `instrument'
/app/vendor/bundle/ruby/2.2.0/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:22:in `block (3 levels) in <module:Logging>'
/app/vendor/bundle/ruby/2.2.0/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:43:in `block in tag_logger'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:68:in `block in tagged'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:26:in `tagged'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/tagged_logging.rb:68:in `tagged'
/app/vendor/bundle/ruby/2.2.0/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:43:in `tag_logger'
/app/vendor/bundle/ruby/2.2.0/gems/activejob-<IP_ADDRESS>/lib/active_job/logging.rb:19:in `block (2 levels) in <module:Logging>'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:441:in `instance_exec'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:441:in `block in make_lambda'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:342:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:342:in `block in simple'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:497:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:497:in `block in around'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:505:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:505:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:92:in `__run_callbacks__'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:778:in `_run_perform_callbacks'
/app/vendor/bundle/ruby/2.2.0/gems/activesupport-<IP_ADDRESS>/lib/active_support/callbacks.rb:81:in `run_callbacks'
/app/vendor/bundle/ruby/2.2.0/gems/activejob-<IP_ADDRESS>/lib/active_job/execution.rb:31:in `perform_now'
/app/vendor/bundle/ruby/2.2.0/gems/activejob-<IP_ADDRESS>/lib/active_job/execution.rb:21:in `execute'
/app/vendor/bundle/ruby/2.2.0/gems/activejob-<IP_ADDRESS>/lib/active_job/queue_adapters/delayed_job_adapter.rb:34:in `perform'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/backend/base.rb:100:in `block in invoke_job'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:61:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:61:in `block in initialize'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:66:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:66:in `execute'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/backend/base.rb:97:in `invoke_job'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:224:in `block (2 levels) in run'
/usr/lib/ruby/2.2.0/timeout.rb:88:in `block in timeout'
/usr/lib/ruby/2.2.0/timeout.rb:98:in `call'
/usr/lib/ruby/2.2.0/timeout.rb:98:in `timeout'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:224:in `block in run'
/usr/lib/ruby/2.2.0/benchmark.rb:303:in `realtime'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:223:in `run'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:300:in `block in reserve_and_run_one_job'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:61:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:61:in `block in initialize'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:66:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:66:in `execute'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:300:in `reserve_and_run_one_job'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:207:in `block in work_off'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:206:in `times'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:206:in `work_off'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:169:in `block (4 levels) in start'
/usr/lib/ruby/2.2.0/benchmark.rb:303:in `realtime'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:168:in `block (3 levels) in start'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:61:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:61:in `block in initialize'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:66:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:66:in `execute'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:167:in `block (2 levels) in start'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:166:in `loop'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:166:in `block in start'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/plugins/clear_locks.rb:7:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/plugins/clear_locks.rb:7:in `block (2 levels) in <class:ClearLocks>'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:79:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:79:in `block (2 levels) in add'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:61:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:61:in `block in initialize'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:79:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:79:in `block in add'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:66:in `call'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:66:in `execute'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/lifecycle.rb:40:in `run_callbacks'
/app/vendor/bundle/ruby/2.2.0/gems/delayed_job-4.1.1/lib/delayed/worker.rb:165:in `start'
/app/lib/delayed_job_worker.rb:6:in `run'
/app/app/concerns/long_runnable.rb:71:in `block in run!'

Can I get some help to solve this issue?

Hi @elvetemedve,
is it possible that this agent belongs to a different user?

Hi @dsander,
Yes, it seems to be the case.
In the beginning I logged in with the admin user and I created some agent.  But later I renamed this user from the Account > Account: Edit User menu.
I looked into the database and I see two rows in the users table. One is for admin, the second is my actual user.
I've removed the admin user, so that probably solved my problem. Thank you.
But I think you should change the behaviour of renaming the actual user, because it's misleading that it actually clones the user and all agents instead.

We do not clone the user, is it possible you are using one of the docker images or re-ran rake db:seed? Per default we do not have the DO_NOT_SEED variable set, which means the the database will be seeded every time the containers starts, db/seeds.rb will recreate the default user when the email address changed.

I'm using the multi-process Docker image and I haven't read the documentation carefully. :)
My bad, sorry.

No worries, I am glad we figured it out :smile: Can we close the issue?

Yes, sure.


Unexpected behavior with different types in array

Hi Jeremy !
First of all, thank you for your brilliant work, it's great.
I'm trying to use your editor to provide different type of objects in the same array (the objects are all based on the same base class)
To do this I have defined a schema using oneOf keyword, like that :
{
  "type": "array",
  "items": {
    "oneOf": [
      {
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "enum": [
              "BUILD",
              "REASSIGN"
            ]
          }
        }
      },
      {
        "type": "object",
        "properties": {
          "type": {
            "type": "string",
            "enum": [
              "BREAK"
            ]
          },
			"property2" :{"type" : "string"}

        }
      }
    ]
  }
}

It is working at load and for the first change of object type.
After that, in memory json seem to be "corrupted".
The object attributes are retained and appears in the UI even if they are not defined in the schema.
With that exemple :
- Click new item
- Switch to item 1 2 => the attribute "property2" appears
- Switch back to item 1 1 => the attribute "property2" is still there and a type select appears.
You can try it using that link
I hope you have an idea,
Thank you for your help,
Tony

I just added a new option keep_oneof_values.  It defaults to true to keep the current behavior, but you can set it to false to do what you want.
Set globally:
JSONEditor.defaults.options.keep_oneof_values = false;

Set per JSONEditor instance:
var editor = new JSONEditor(el, {
  schema: {...},
  keep_oneof_values: false
});

Set for a single oneOf instance:
{
  "options": {
    "keep_oneof_values": false
  },
  "oneOf": []
}

Hi and thank you Jeremy, I will try it this week.

I've just tried out @tgeorges example with the additional keep_oneof_values property, and it seems to solve the problem.
@tgeorges example with modification added: link
Therefore I reckon this could be closed off!
Thank you for the fantastic library.


Batch select and filtering

Hi,
Thank you for the great work! I am using Js-grid for my tables and it works good.
However I a have this issue I couldn't resolve.
I have implemented a select checkbox column (like in Batch Delete in your demo) but in my case I am not deleting but generating a file from the selected elements.
Anyway, I also use the filtering feature, but every time I filter my table, I lose my selected items.
Do you have a solution I might have missed for that?
Thank you very much!

Thank you for the feedback!
Since filtering rerenders all the rows you have to take care about these checkBoxes state. Keep track the selected items in an array. And after filtering restore the states. You can restore the state in itemTemplate checking whether item is in seleted array. Or you could handle selecting with onRefreshed callback: iterate over the rows and set the state of checkboxes.


Refactor utilities/cast to Typescript

Update the utilities/cast.js file to use typescript -> utilities/cast.ts
Description

The change does the following:

Convert module.exports to an export on each function
Adds type annotations to functions and

Motivation and Context

issue
Partially addresses #551
How Has This Been Tested?

Only additions of type annotations to existing code, issue with tests was prevalent before making changes
Typescript check is fine without any issues
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Author's Checklist:

[x] My code focuses on the main motivation and avoids scope creep.
[ ] My code passes current tests and adds new tests where possible.
[ ] My code is SOLID and DRY.
[ ] I have updated the documentation as needed.

All existing logic has been retained, just the type annotations added
Reviewer's Checklist:

[ ] I kept my comments to the author positive, specific, and productive.
[ ] I tested the code and didn't find any new problems.
[ ] I think the motivation is good for the project.
[ ] I think the code works to satisfies the motivation.

Awesome job! 👍 Just few minor things and we are good to go.

Thanks @mubaidr for the response, I'll make the changes once you've confirmed based the comments above which of the changes I should make

Thank you! 💯


[Issue #26] - Lucene Hotel Application Team-1

@chenlica @JavierJia Please review the code.

LGTM in general.  Please fix the indentations to 4 spaces for all files.

Reference the issue number (https://github.com/TextDB/textdb/issues/26).  Try to make the name of the pull request more informative.

I will read details on Tuesday.

@varunbharill and @renacimiento Can you review this PR separately?

I made a minor comment.  The rest looks good to me.
No need to wait for @varunbharill and @renacimiento to do the approval of the merge.

@chenlica  @JavierJia .. Made the suggested changes. It will be difficult to see the changes, since I changed the indentation from tab to white spaces. Will merge it to the master if everything is fine.
Thanks,
Sandeep

Please go ahead to do the merge.

Please delete the branch.


Lack of options to list currently supported linux distros

Describe the issue

Documentation provides info about format for curl command to download repo file, but there is no explicit easy option to get info about currently supported linux distros. Listing directories of "https://packages.microsoft.com/config/(...)"
gives:
The request is blocked.
20241228T202457Z-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxyu
When did the issue occur?

Always
If applicable, what package did you attempt to install, and from which repo?
Steps to Reproduce

Try to open:  https://packages.microsoft.com/config/
Actual Result
"The request is blocked.
20241228T202457Z-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxyu"
Expected Result
Listing of supported distros.
Screenshots

Additional context

An optional and likely more convenient solution would be to provide a link to an updated documentation webpage containing a list of currently supported Linux distributions. The link should be clearly visible on the page: https://learn.microsoft.com/en-us/linux/packages

Hi @k2extreme, the config directory listing is not blocked in general. Your problem appears to be that the value of your mslocale cookie is for some reason triggering a sql-injection firewall rule. Please delete your cookies for microsoft.com and try again.
Better docs are always desirable, however in this case it's not really practical; the list of supported Distros / Versions changes faster than the docs are updated, and also changes on a per-product basis. So the best place to look for accurate information is the repo listing itself (like you're trying to do) or the product-specific docs.

[like]  Matt Bearup reacted to your message:

From: Stephen Herr @.>
Sent: Monday, December 30, 2024 3:18:33 PM
To: microsoft/linux-package-repositories @.>
Cc: Subscribed @.***>
Subject: Re: [microsoft/linux-package-repositories] Lack of options to list currently supported linux distros (Issue #201)
Hi @k2extremehttps://github.com/k2extreme, the config directory listing is not blocked in general. Your problem appears to be that the value of your mslocale cookie is for some reason triggering a sql-injection firewall rule. Please delete your cookies for microsoft.com and try again.
Better docs are always desirable, however in this case it's not really practical; the list of supported Distros / Versions changes faster than the docs are updated, and also changes on a per-product basis. So the best place to look for accurate information is the repo listing itself (like you're trying to do) or the product-specific docs.
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/linux-package-repositories/issues/201#issuecomment-2565612514 or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACZOS2PAOC77KEAVEFYOEIL2IFP4TBFKMF2HI4TJMJ2XIZLTSSBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZTQOJSGA3TCNRSGCSG4YLNMWUWQYLTL5WGCYTFNSWHG5LCNJSWG5C7OR4XAZNMJFZXG5LFINXW23LFNZ2KM5DPOBUWG44TQKSHI6LQMWVHEZLQN5ZWS5DPOJ42K5TBNR2WLKJUGY2TQOJSGEYDRAVEOR4XAZNFNFZXG5LFUV3GC3DVMWVDENZWGE4TEMRSGI3YFJDUPFYGLJLMMFRGK3FFOZQWY5LFVIZTQOJSGA3TCNRSGCTXI4TJM5TWK4VGMNZGKYLUMU.
You are receiving this email because you are subscribed to this thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Remove validations on CLI so more verbose error messages are bubbled up from core

WHY are these changes introduced?
We are doing validations for TOML values on both cli and shopify. If the invalid configs are caught by cli, the error messages look like this:

The issues with these error messages are:

We are only able to see one error message at a time
The error message is not always descriptive, especially if there are multiple issues

WHAT is this pull request doing?

This PR removes CLI validation in favour of hitting shopify to get more descriptive error messages on multiple app configuration modules for the user.

How to test your changes?

Create app with npm init @shopify/app@latest
Pull this branch into your local cli copy
Run SHOPIFY_SERVICE_ENV=spin SPIN_INSTANCE={YOUR-SPIN-INSTANCE} NODE_TLS_REJECT_UNAUTHORIZED=0 SHOPIFY_CLI_VERSIONED_APP_CONFIG=1 pnpm shopify app config link --path {YOUR-APP-PATH}
Link your app, and change your name/handle values to something invalid
Run SHOPIFY_SERVICE_ENV=spin SPIN_INSTANCE={YOUR-SPIN-INSTANCE} NODE_TLS_REJECT_UNAUTHORIZED=0 SHOPIFY_CLI_VERSIONED_APP_CONFIG=1 pnpm shopify app deploy --path {YOUR-APP-PATH}
View error messages

Measuring impact
How do we know this change was effective? Please choose one:

[x] n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
[x] Existing analytics will cater for this addition
[x] PR includes analytics changes to measure impact

Checklist

[x] I've considered possible cross-platform impacts (Mac, Linux, Windows)
[x] I've considered possible documentation changes
[x] I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

We've always preferred to fail early, otherwise we might ask you a bunch of questions in prompts, let you think everything is going to work and then fail at the last moment.
It is possible to customize errors in Zod, but since we might move to JSON Schema, I wouldn't invest to much on it.
Since the UX is better when we validate in the server, maybe is worth discussing this with Meredith.

We've always preferred to fail early, otherwise we might ask you a bunch of questions in prompts, let you think everything is going to work and then fail at the last moment.
It is possible to customize errors in Zod, but since we might move to JSON Schema, I wouldn't invest to much on it.
Since the UX is better when we validate in the server, maybe is worth discussing this with Meredith.

Thanks for the feedback @isaacroldan! I think @jessehoek is our designer on this project so I'll defer to him quickly unless perhaps we need more eyes?
Also, I'm curious if we have an issue to track the move from zod to JSON Schema so I can learn more about the decision making there and if folks need more hands.

The way the error is presented from the server is much easier to read and see all the issues at once. But I agree with the principle of validating and failing early so that you save time. It does feel weird to see one error at a time, but I would consider improving that local validation experience vs delaying the moment you see the error.
Question: are there some validations we can't do until we hit the remote app in the server? Like doesn't the "can't contain Shopify" rule only apply to 3P apps, and 1P can do this? Or no?
As an aside, no matter what direction we go in, I want to make sure we don't expose the config module names or groupings to end users. We present all of this as one app configuration in the TOML. So our name "Branding" is only an internal concept.


tests: (in)valid unit test vectors against IsTriviallyValid() evo calls

Depends on https://github.com/dashpay/dash/pull/4696

Done. See https://github.com/dashpay/dash/pull/4696

Relic library error failures seem unrelated to this PR

Relic library error failures seem unrelated to this PR but definitely warrants looking into

restarted windows ci build

https://github.com/UdjinM6/dash/commit/a6254683093e5767878f9c0bf85463ae95bd08c5 should fix it

UdjinM6@a625468

How about https://github.com/dashpay/dash/commit/d1a7b4dd842f45ee7a7a37a55e0405d27f1db262?

UdjinM6/dash@a625468

How about d1a7b4d?

👍

Okay, I pushed to the branch @kittywhiskers


Imodel02 merge master

Merging to fix issues with eslint plugin in imodel02 found from https://github.com/iTwin/imodel-native/pull/213 validation runs. The eslint-plugin version in fixes this issue.

Wrong target branch?

Wrong target branch?

yes sorry about that.

/azp run iTwin.js

I have been watching it. I'm not in love with two of your three recent merge commits. We want the history on imodel02 to look like the history on master.

I have been watching it. I'm not in love with two of your three recent merge commits. We want the history on imodel02 to look like the history on master.

Yeah... I'm not sure exactly what happened there. I can look into undoing them.

I have been watching it. I'm not in love with two of your three recent merge commits. We want the history on imodel02 to look like the history on master.

Yeah... I'm not sure exactly what happened there. I can look into undoing them.

I believe this was due to it initially being merged to master, so it ran when it shouldn't have.

I'd also like to see CI jobs running. extract-api failed for @DanRod1999 yesterday.

@pmconne i thought the full ci was never run against this target branch, since no native with the changes have been published

i thought the full ci was never run against this target branch, since no native with the changes have been published

Right.

https://dev.azure.com/bentleycs/iModelTechnologies/_build/results?buildId=2040439&view=results
I ran iTwin.js build pipeline against this branch and it all passed. This doesn't run extract-api though, which is a github action instead of an azure pipeline. Would you still like to see that? I'm not sure how to run a github action on this branch, maybe Seamus would know?

@DanRod1999 let's add an issue for adding extract-api to the list of checks for the imodel02 branch... This will be painful since we're partially in GH and partially in ADO but let's add it to the list.
@pmconne anything holding this up from your side? If not, I'll merge it.


dom error reporting

Sometimes when working with cycle and something is not working the page just stays blank and no error is logged.
For example the UnexpectedVirtualElement error from this issue https://github.com/cyclejs/cycle-dom/issues/72 just got swallowed and it took me a while to track it down.
The reason for this seems to be that rxjs converts errors thrown inside a stream operator into errors emitted on the corresponding stream. The dom driver does not seem to care about all the errors in the streams and just ignores them silently.
I propose to make sure that all errors happening inside the dom streams to be logged in the console. (or maybe even better: being converted into a
message
 which get's inserted into the dom)

Errors reported to console is maybe a good idea. Inserting DOM nodes is not a good idea, because it presents errors to users in the UI, which is probably not what you want in a production environment.

Your are right, console would be best.

Totally agree.

I agree with all this too, I've run into this issue quite a few times when trying to learn.

I think adding .doOnError(console.error.bind(console)) here would do the job:
https://github.com/cyclejs/cycle-dom/blob/auto-scope/src/render-dom.js#L170
Or we could add an error callback parameter to makeDOMDriver which defaults to console.error.bind(console)
I could create a PR if you like.

I could create a PR if you like.

Would be great!

This is solved in v8.0.0-rc7. Reopen issue if it persists.


does not link

I tried to link the package but it will not do any thing.
react-native link react-native-nfc-manager
Scanning folders for symlinks in /home/chris/nfc/node_modules (10ms)

{
  "name": "helloworld",
  "version": "0.1.0",
  "private": true,
  "devDependencies": {
    "jest-expo": "~27.0.0",
    "react-native-scripts": "1.14.0",
    "react-test-renderer": "16.3.1"
  },
  "main": "./node_modules/react-native-scripts/build/bin/crna-entry.js",
  "scripts": {
    "start": "react-native-scripts start",
    "eject": "react-native-scripts eject",
    "android": "react-native-scripts android",
    "ios": "react-native-scripts ios",
    "test": "jest"
  },
  "jest": {
    "preset": "jest-expo"
  },
  "dependencies": {
    "expo": "^27.0.1",
    "react": "16.3.1",
    "react-native": "~0.55.2",
    "react-native-nfc-manager": "^0.5.5"
  }
}

Any idea?

Hi, sorry for the late response.
Looks like you're using a CRNA based project. In such case, you will have to do "eject" first, otherwise the native dependency cannot be configured correctly.
Thanks!

thanks! @whitedogg13 !


Data race

Hi, yofu!
Found data race in concurrent drawing processing.
I think it's relates to handle increments, but had no luck trying to resolve this.
See gist for code and run log
gist

Hi @edanko!
This gist doesn't seem to exist anymore.

Forget the gist. It's kinda resolved.
Races related to many global objects, such as this one. So, if you want to do some concurrent processing, you must get rid of all these variables.
You can use this commit as inspiration.
Have a nice day!


Proxy works perfectly when using MacOS mysql client, but connection refused when using python

I have a python program that I need to run on my local machine. One of the first things the program does to initialize itself is to connect to the database. The database in this case is a GCP Cloud SQL instance.
When I start up my proxy and connect via command line it works great.
../another-directory/cloud_sql_proxy -instances=my-project:us-east1:my-db=tcp:3306 &
mysql -P 3306 -h <IP_ADDRESS> -D mydatabase -u my_user -p

And it works great. I can do whatever I need to in the database.
But when I try to run my program that uses PonyOrm (which under the covers is using pymysql), I get this error:
pony.orm.dbapiprovider.OperationalError: (2003, "Can't connect to MySQL server on '<IP_ADDRESS>' ([Errno 61] Connection refused)")

I'm baffled and can't tell what's going on. More oddly still, when I ran this same program in the cloud with kubernetes and a Cloud SQL proxy container, it all worked fine.

There could be any number of small things that might be tripping you up:

Check that the proxy is still running. If you start it as a background process (with &) but close that shell, the proxy will terminate.

Check that you are connecting with PonyORM correctly. Looking at the docs, it looks like the following should be close to what you need:

db.bind(provider="mysql", user="my_user", password="my_password",
        host="<IP_ADDRESS>", database="mydatabase", port="3306")

If you've doubled checked those two things and are still having problems, please post the output of the proxy along with the snippet you are using to connect with.

I thought I'd double checked 2 well enough, but the problem ended up being my Environment variables not making it down the chain to python. Works perfect. Thanks!


[BUG]gears.scad worm_gear fails when adding shaft diameter

Describe the bug
creating a worm gear fails with the error [WARNING: variable l not specified as parameter in file libraries/BOSL2/gears.scad, line 1260] when adding shaft_diam variable
A clear and concise description of what the bug is.
Code To Reproduce Bug
worm_gear(mod=.33, teeth=150, worm_diam=6, worm_starts=1); works
worm_gear(mod=.33, teeth=150, worm_diam=6, worm_starts=1,shaft_diam=4); fails
Additional context
Add any other context about the problem here.
OpenSCAD Version: 2021.01
Other libraries used: None
Changing gears.scad line 1260 from:
cylinder(d=shaft_diam, l=worm_diam, center=true);
to
cylinder(d=shaft_diam, h=worm_diam, center=true);
Sorry, I am a noob on github & openscad, apologies if this is not the best way to raise this.

This is the right place to post this.  The gears code is undergoing massive revisions right now because a bunch of things were fundamentally incorrect, so this might not be fixed immediately.  You can make a shaft yourself by differencing a cylinder.


Intel realsense dying en masse

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
{ R200 / F200 / SR300 / ZR300 / D400 }

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
{Win (8.1/10) / Linux (Ubuntu 14/16/17) / MacOS

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC/Raspberry Pi/ NVIDIA Jetson / etc..

SDK Version
{ legacy / 2.. }

Language
{C/C#/labview/nodejs/opencv/pcl/python/unity }

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>

Dear everybody, I have had 3 realsense cameras bricked in a row (2 D435, 1 R200).
They are mounted on a drone, and it's usually ok for a few runs. But at a certain time, they just die, lsusb returns no device.
It may be some electrical interference here. I wonder if someone has experienced this kind of sensitivity and if you have any insights on how to overcome this? Or generally how sensitive are these sensors?

Are the cameras permanently disabled (as 'bricked' implies) or do they work again after being reset, please?
I cannot think of much that would permanently destroy a RealSense camera on such a predictable schedule.  An electro magnetic pulse (EMP) can knock out electronics, but surely the rest of the drone would be affected if that were the case.  A more probable cause would be if extreme vibration was being transmitted through the drone's frame to the camera.
The article below on the website of Mouser, an Intel Authorized Distributor company, is interesting.
https://eu.mouser.com/applications/harsh-environment-vibration-protection/
If a camera is mounted on a device that is in harsh operating conditions with high vibration (whether a drone or a mobile robot on rough terrain) then some kind of vibration dampening pad on the camera's mounting is a good idea.

They cannot be detected when I plug them on other computers. No "intel corp" device shows up when using the command lsusb.
Vibration is not the issue since we haven't flown the drone, just some ground test.
If this helps, the camera is connected to a UP board's USB. We're down to the last realsense now.

I have not heard of a case like this before.  If you are plugging the camera into an original Up Board with a USB OTG micro-port then I am aware that cameras may experience difficulties operating sometimes unless a mains-powered USB hub is used, because of the camera being provided with insufficient power otherwise (the newer and more powerful Up Squared board with full USB 3.0 port does not seem to have this issue).  I have not come across a case where an Up Board could kill a camera though.

USB devices can heat up severely if the USB port that they are plugged into is defective.  You would probably have to run your remaining camera at least once and hold your hand on it to test whether this is the case though.  If you have another USB device that you can afford to lose (such as a USB storage stick), maybe you could test with that instead and see if it quickly gets hot while in the port.


v0 fern docs theme

@abvthecity should i close this now?

@dsinghvi we can close. I will reference this in the future!


Ported flashy messages from #notice to #alert

A ton of JS expected the #notice element to exist but that was never the case.
Instead, the element to target for flashy messages is the #alert one. This must
be some leftover from a refactoring.
Moreover, I've added some acceptance tests that were missing (e.g. Team
members), since some of the alert messages referenced this features anyways.

LGTM, just fix rubocop issues and merge it


How to make external api call on paginated data

I have fastapi service which is using fastapi-pagination, now it the service returns paginated response , Now i want for each page i need to make external api call to get some metadata and fill the response under the same api call , is this possible?

Hi @tiru1930,
Could you please provide minimal example so I can understand what you need.

Hi @tiru1930,
Could you please provide minimal example so I can understand what you need.

Hi
It's fixed ,please close the ticket,  I have just made api call  to get
extran info on paginated items.
On Sat, Jan 1, 2022, 2:38 PM Yurii Karabas @.***> wrote:

Hi @tiru1930 https://github.com/tiru1930,
Could you please provide minimal example so I can understand what you need.
—
Reply to this email directly, view it on GitHub
https://github.com/uriyyo/fastapi-pagination/issues/251#issuecomment-1003530228,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC5FIV6TEK4VYFGQTPCS5DDUT277RANCNFSM5KDOZAPA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi
It's fixed ,please close the ticket,  I have just made api call  to get
extran info on paginated items.
On Sat, Jan 1, 2022, 2:38 PM Yurii Karabas @.***> wrote:

Hi @tiru1930 https://github.com/tiru1930,
Could you please provide minimal example so I can understand what you need.
—
Reply to this email directly, view it on GitHub
https://github.com/uriyyo/fastapi-pagination/issues/251#issuecomment-1003530228,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AC5FIV6TEK4VYFGQTPCS5DDUT277RANCNFSM5KDOZAPA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


Shorter Folder name replaced with ellipsis

Not a big bug, just some weirdness. In the explorer tab the name of folder gets partially replaced by an ellipsis, while longer names on the same level are not abbreviated.  meta-oe gets replaced with meta-... while  meta-multimedia or meta-filesystems will not be shortened.

VSCode Version:
Version 1.21.1
Commit 79b44aa704ce542d8ca4a3cc44cfca566e7720f1
Date 2018-03-14T14:46:30.761Z
Shell 1.7.9
Renderer 58.0.3029.110
Node 7.9.0
Architecture x64
OS Version: Ubuntu 16.04 LTS with XFCE.

Steps to Reproduce:

Honestly: No idea, have a rather deep directory hierarchy?

Does this issue occur when all extensions are disabled?: Yes

I can not reproduce this.
Do you also see this behavior with the latest vscode insiders https://code.visualstudio.com/insiders/


Updating code for kne platform

Hi ,
"WaitForArp" needs way to invoke arp request when invoked this api.
As of now "WaitForArp " Ixia API call does not send explicit arp request , which is very much needed when tests have interface change events in containerized environment. (Virtual platforms).
As of now ARP is resolved only during Pushconfig API and not when we invoke "WaitForARP".
Thanks,
Priya Ranjan

Pull Request Functional Test Report for #3540 / 6c185b3cb5ffde8e1246c9fb1643c12b75f0932f
Virtual Devices

Device
Test
Test Documentation
Job
Raw Log

Arista cEOS

RT-5.8: IPv6 link localRT-5.8: IPv6 Link Local

Cisco 8000E

RT-5.8: IPv6 link localRT-5.8: IPv6 Link Local

Cisco XRd

RT-5.8: IPv6 link localRT-5.8: IPv6 Link Local

Juniper ncPTX

RT-5.8: IPv6 link localRT-5.8: IPv6 Link Local

Nokia SR Linux

RT-5.8: IPv6 link localRT-5.8: IPv6 Link Local

Openconfig Lemming

RT-5.8: IPv6 link localRT-5.8: IPv6 Link Local

Hardware Devices

Device
Test
Test Documentation
Raw Log

Arista 7808

RT-5.8: IPv6 link localRT-5.8: IPv6 Link Local

Cisco 8808

RT-5.8: IPv6 link localRT-5.8: IPv6 Link Local

Juniper PTX10008

RT-5.8: IPv6 link localRT-5.8: IPv6 Link Local

Nokia 7250 IXR-10e

RT-5.8: IPv6 link localRT-5.8: IPv6 Link Local

Help

Adding more reviewers for this PR


Will typings ever come back?

I was so happy when viz finally supported typings and now they are removed without any justification as to why. Is this temporary or will they never come back?

I don't have time to maintain them. Part of that is that I don't use TypeScript, so it's more effort to ensure that the type information is correct.

It's not that much trouble to add typings since the library isn't that complex. I just did it for the methods that we use. Any chance they get added back in if I type the entire library?
declare module 'viz.js' {
    class Viz {
        constructor();
        renderString(src: string, options?: Options): Promise<string>;
        renderSVGElement(src: string, options?: Options): Promise<SVGSVGElement>;
    }

    class Options {
        engine?: "circo" | "dot" | "fdp" | "neato" | "osage" | "twopi";
        format?: "svg" | "dot" | "xdot" | "plain" | "plain-ext" | "ps" | "ps2" | "json" | "json0";
    }

    export = Viz;
}

@SaphuA You can submit your typings to DefinetlyTyped:
https://github.com/DefinitelyTyped/DefinitelyTyped#create-a-new-package
IMHO, it's the best option for a case when library author don't have time to maintain it.


Formatting from last command stays in the terminal

[x] I am on the latest Hyper.app version
[x] I have searched the issues of this repo and believe that this is not a duplicate

OS version and name: * Windows 10 Enterprise
Hyper.app version: * 2.1.2
Link of a Gist with the contents of your .hyper.js: * I'm using no such file. Default installation.
Relevant information from devtools (CMD+ALT+I on macOS, CTRL+SHIFT+I elsewhere): N/A
The issue is reproducible in vanilla Hyper.app: Is Vanilla

Issue
Prerequisite
A command that ends in bold formatting. E.g.: Yarn, or create-react-app, which uses Yarn.
Observed Behavior
After running the aforementioned command, the command ends with a message in bold. The next prompt of the terminal then becomes bold.
Screenshots:

Expected Behavior
The prompt should return to initial formatting irrespective of the formatting changes from the output of commands.
Known Workarounds
A Full Reload of the app would restore the formatting (Normal Reload would not). However, this is undesirable as it would also restore the environment and the working directory.

Hhmm I have similar issues with the PHPStorm app, often running the command reset fixes it.

@ianwijma This is for Windows. No reset is available for me. 😞

Aahh sorry, My bad. I'm not that known with the CLI tool set on Windows.