Less distracting error message for JSON schema resolution issues

Related issue: #51032
Ellipsis
Instead of showing an error in the Problems tab, this PR changes the JSON Language Service to show a status bar icon if a JSON Schema cannot be resolved. This icon is hidden again once the current file is changed.

Technical Summary
As suggested here by @aeschli, this adds a middleware that intercepts diagnostics from the server. If one of the diagnostics is a ErrorCode.SchemaResolutionError, it is removed from the diagnostics array and the status bar icon is shown. Further diagnostics (e.g. syntax errors) are left untouched.
Note: To test this, point schemastore.azurewebsites.net to a non-existing IP address (e.g. <IP_ADDRESS>) via a local DNS server or /etc/hosts for a schema resolution error.
Caveats

This adds a dependency on vscode-json-languageservice to the client, which might not be desired. However, it is the only apparent way to use the actual enum constant for the error code instead of a magic number. This uses a magic number for the remote event code.
When switching back to a JSON file, the error only appears when schema resolution is reattempted. This happens on save.
There is currently no way to retry.

Further Notes
No tests are provided. This reason for this is that I was not able to find any tests for that particular module and adding entirely new ones seemed overkill for this issue.
I will squash the commits once I get feedback on whether the new dependency is desired and if further adjustments are needed.
#Hacktoberfest

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: xxyy sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Also we need to improve the error message. That's to be done in the vscode-css-languageservice.

I have changed the error code to use the magic value instead of the dependency. Also, I'm now using a custom status bar item to show the error, as suggested. (see the updated PR description for a screenshot) The item is only shown if a schema error occurred and hidden otherwise.
I have also added the retry action. Below the error message (I'll look into making a PR to make it nicer in vscode-json-languageservice later this week), a hint is shown that one may click to retry. When the retry command is received, the icon changes to a watch and the server is notified to re-verify the current file. It changes back or disappears when the server sends the resulting diagnostics.
Currently, I'm hiding the status bar item when the active editor is changed – it's not relevant in any other file. However, the issue is that diagnostics are not recomputed when switching tabs, so the icon will not reappear unless the JSON file is changed. Should I just keep the status bar icon when switching files? (might be annoying) If not, i'd have to re-verify the schema every time a JSON file is switched to. (If there's no way to have hidden diagnostics)
Also I'm unable to get the locale string from package.nls.json to show in the UI, it always shows the fallback. Do I have to do something else to add a new nls message?

Great work @xxyy !

Currently, I'm hiding the status bar item when the active editor is changed – it's not relevant in any other file.

yes, we should only show the warning when the corresponding editor has focus.
I suggest to have  which URIs have the resolve error, so when the editor gets active you can look there.
Entries can be removed from the map when a document is closed (onDidCloseTextDocument).

Thanks @xxyy !


documentation - flan-t5

regular sft and lora sft are supported , but only on the q and k modules.

What does sft stand for?

supervised fine tuning

is or will be the aya model which comes from mt5, supported for finetuning?

i'm very interested in this. but can't find any scripts in the 'examples'. enc-dec models have huge untapped potential.


Allow spec changes on shoots/binding update strategy

How to categorize this PR?

/area control-plane
/kind bug
What this PR does / why we need it:
With #6179, in the shoots/binding strategy, we used to replace any spec changes to shoot with the oldSpec itself. This was to prevent updates to any other fields than .spec.seedName. But this caused the changes by the dns admission plugin to shoot spec to be reverted. Anyways, the binding subresource can only be updated by operators, so we can safely allow simultaneous spec changes. This PR removes this newShoot.Spec=oldShoot.Spec handling from binding strategy.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
/cc @plkokanov @rfranzke
Release note:

Spec changes are allowed on binding update to facilitate dns admission plugin. However no other spec should be changed manually on binding update.

/milestone v1.50


probot commands - Add TypeScript support

In the commands repo there are some issues about the TypeScript support:
https://github.com/probot/commands/issues/10
https://github.com/probot/commands/issues/19
https://github.com/probot/commands/issues/22
The stranger thing is that some users added this support by these pull requests:
https://github.com/probot/commands/pull/15
https://github.com/probot/commands/pull/20
But both were closed by the bot.
There are some problems with this repo?
Looks like the repository is abbandoned.

Not related to probot itself. Anyway should be investigated further.


Haptic feedback - Vibration while selecting images / folders

Is your feature request related to a problem? Please describe.
Not a problem but a improved user experience
Describe the solution you'd like
It would be great if you could add a haptic feedback - Vibration while selecting images / folders
Describe alternatives you've considered
NA
Additional context
NA

Would you know another gallery that does this? No need to be open-source, it's just for me to experience.

Would you know another gallery that does this? No need to be open-source, it's just for me to experience.

F-Stop Gallery
Google Photos
Even most other apps while we long press and select an item-
Gmail
Mixplorer.
Probably ill rephrase what i mentioned in the main post - 'While long pressing and selecting an item - Photo,Folder,..'
Perfect open source example for this haptic feedback- https://github.com/IacobIonut01/Gallery

sorry closed it unknowingly.

I wasn't feeling the haptic feedback in Google apps, but felt it in IacobIonut01/Gallery. So I looked a bit and I had it disabled at the OS level (on my Samsung device it's in Settings > Sounds and vibration > System sound/vibration control >  Vibration > Touch interactions). After enabling it, I felt it in the Google apps too.
Anyway, it tells me 2 things:

IacobIonut01/Gallery could be improved by respecting the OS setting,
if I implement it in Aves, I should respect it too.

Great, excited to try it.


[Area of Product] - Short and simple descriptive name describing the issue

Summary
A high-level, non-technical explanation of what was encountered. Should be no longer than a 2 sentences, if possible.
Is there a workaround?
An explanation, including visuals if necessary, identifying the workaround.
Is there any Pre-Configuration required?
A list of prerequisites that must be met in order to reproduce what has been identified.  Include visions if it is helpful. (Note: this question supports the section: What are the Steps to Reproduce?)

If there are any custom settings that need to be enabled or any other prerequisites describe them here.
If this is only an issue in a certain browser, include that here.
If there are certain Accessibility tools or setup needed (like only using your keyboard or a screen-reader, etc.), include them here.
If N/A, just type N/A or remove this section.

What are the Steps to Reproduce?
A list of sequential steps that outline the process of reproducing what has been identified.  Include visuals if it is helpful.
What is the expected behavior?
A description of what was expected. Include visions if it is helpful.
What is the actual behavior?
A description of what was actually encountered. Include visions if it is helpful.
What is the motivation / use case for changing the behavior?
A brief summary identifying why you want to see the expected behavior.

**lurch: add

Tracking W-038248

This was a Test issue. Closing the Issue now. WI has been deleted.


Remove Roku.roku_remote_tool <IP_ADDRESS>7 to Roku.RemoteTool <IP_ADDRESS>7

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

URL: https://devtools.web.roku.com/RokuRemote/app/win/roku-remote-tool-win64-installer.exe
Status Code: 200
(Automated message - build 703)

https://github.com/microsoft/winget-pkgs/pull/137925#issuecomment-1928174050


Make folder name searchable

Also make the project's folder name searchable, for example searching for demo-starter should return the Starter project.
Related https://github.com/oasisprotocol/playground/issues/78, #77

Implemented in PR #82


mainboard multi dag list file

In mainboard source code, each dag file must  be placed after an "-d"  parameter.
But in cyber_launch,while multi dag files are used in s single process, cyber_launch will place all dag files after a single -d parameter.,this will cause a mainboard open error.

I test below command and it realy work, so can you describe your problem in detail ?
mainboard -d modules/dag/1.dag modules/dag/2.dag

You mean 'cyber_launch' execute a command like this 'mainboard -d XXXX.dag YYYYY.dag' ?

Yes, when you want to run mutil dag, you can write like perception_all.launch. It will final run the cmd mainboard -d modules/dag/1.dag modules/dag/2.dag.
I think you may write like this?
    <module>
        <name>motion_service</name>
        <dag_conf>/apollo/modules/perception/production/dag/dag_motion_service.dag</dag_conf>
        <dag_conf>/apollo/modules/perception/production/dag/dag_motion_service1.dag</dag_conf>
        <process_name></process_name>
        <version>1.0.0</version>
    </module>


Feature request: logging of charging time and time since last charge

The charging time and time since last charge should be logged.

I hope someone can help you :)


Incompatible with VFPA

It must be doing some version checking that isn't expecting VFPA. A simple fix would be to invoke SYS(9018,0) to make VFPA return older version information. VFP9 and earlier would be unaffected.
Error 1098, Incorrect VFP 9 version - Missing SP1! Expected: 3504 or later, actual: 10.00.0000.1909
execute, 2902
FoxBin2Prg: [C:\DEV\FOX\THOR\THOR\THOR\TOOLS\COMPONENTS\FOXBIN2PRG\FOXBIN2PRG.EXE] (EXE Version: v1.19.51)

Translation, in case you're lurking and wondering . . . Visual FoxPro Advanced. :-)

Just ran into this myself. Any plans to add support for VFPA to FB2P, Fernando?

Hello, guys: Since 1+ year now, I'm working on other technologies and I'm really not touching VFP, so I see a little complicated to keep maintaining this project and giving to it more hours :-|
In some future I will try to address the remaining issues, but I'm really out of time occupied by many things I need to learn. Hope you understand :-)

Thanks for following up, Fernando, and thanks for creating a fantastic tool. I'm using it everyday. I'll take a stroll through the code as this sounds like a fairly straightforward change. If it is, I'm happy to fork the project and submit the fix once I can resolve the issue.

This appears to be the culprit. From the execute method:
DO CASE CASE VERSION(5) < 900 OR INT( VAL( SUBSTR( VERSION(4), RAT('.', VERSION(4)) + 1 ) ) ) < 3504
	ERROR loLang.C_INCORRECT_VFP9_VERSION__MISSING_SP1_LOC
Easy enough to modify to handle VFPA. Taking the simplest approach I simply added another CASE at the beginning:
CASE VERSION(5) = 1000
Would you like me to submit this?

Ok, Richard,
Thanks :)
El lun., 24 feb. 2020 a las 23:37, Richard Kaye<EMAIL_ADDRESS>escribió:

This appears to be the culprit. From the execute method:
DO CASE CASE VERSION(5) < 900 OR INT( VAL( SUBSTR( VERSION(4), RAT('.',
VERSION(4)) + 1 ) ) ) < 3504
ERROR loLang.C_INCORRECT_VFP9_VERSION__MISSING_SP1_LOC
Easy enough to modify to handle VFPA. Taking the simplest approach I
simply added another CASE at the beginning:
CASE VERSION(5) = 1000
Would you like me to submit this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/fdbozzo/foxbin2prg/issues/36?email_source=notifications&email_token=ABHXM3ECMYIJNOP3LWV2K4TRERDZ5A5CNFSM4JM6OWU2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMZZW7Y#issuecomment-590584703,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHXM3GGE2L36FK7NSEZDLLRERDZ5ANCNFSM4JM6OWUQ
.

Bug is fixed! Thank you for reporting and sorry to be late. Enjoy :)


Add transformation and composition operators to JsonCodec

Just as JsonEncoder and JsonDecoder support a wide range of operators, which transform and combine codecs, so also can JsonCodec support operators, including:

orElse
orElseEither
zip
zipLeft
zipRight

These will have type signatures similar to the existing type signatures.
In addition, an xmapOrFail could be added, probably here and to the parent types.

@jdegoes can I take this up?

@afsalthaj of course

No one is working on this, I don't think.

I am going to attempt this


[Feature Request] Real ESM Modules of Monaco Editor (without require,... etc.)

Context

[X] This issue is not a bug report. (please use a different template for reporting a bug)
[X] This issue is not a duplicate of an existing issue. (please use the search to find existing issues)

Description
I'd like to have real ESM Modules of Monaco Editor wich can be used directly in browser only by providing an importmap.
At the Moment Monaco has an ESM Folder but:

The imports in the ESM exports are missing '.js' extension (at least in the editor.main.js)
There are still '.css' imports in the ESM Modules, wich are invalid. They need to be replaced with for example css-modules "import ... with { type: 'css' } }"

Monaco Editor Playground Link
No response
Monaco Editor Playground Code
No response

relates to:
https://github.com/microsoft/monaco-editor/issues/2343
https://github.com/microsoft/monaco-editor/issues/886


Handle stop of price submission in the oracle gracefully

Describe the bug
When the oracle stops submitting prices for an asset, the parachain goes into an error state ORACLE_OFFLINE. However, there is a valid reason to stop submitting prices for an asset: The asset is delisted from the bridge or lending protocol, so the prices are no longer needed.
Also, it's possible that a single asset could just be removed from our oracle source. Delisting might happen due to issues with the underlying asset, lack of demand, or more.
Expected behavior

When a single oracle asset is not reported anymore, we should not stop the whole bridge and the whole lending market. Instead, the affected assets should be paused.

Delisting assets requires governance. Within the same governance to delist a market or a collateral asset from the bridge, governance should be able to delist the oracle price reporting of an asset without the parachain entering the ORACLE_OFFLINE state.

When a single oracle asset is not reported anymore, we should not stop the whole bridge and the whole lending market. Instead, the affected assets should be paused.

This can most be achieved by just removing the error state altogether. That would let everything continue as normal, except that any calls that do a currency conversion to that collateral will fail. We might also want disable rewards for vault with that collateral. However, what would we want to do when an asset is delisted? Would we liquidate all vaults and borrows? There wouldn't be a straightforward exit path

Only handle oracle going offline for one or more assets in this issue.
Move the delisting of assets to separate issue.

For oracle going offline:

Assume asset price will be available again after timeout period.

Questions:

How would that affect liquidations? If price crashes when oracle is coming online again, vaults/borrowers will get liquidated. Liquidations are not possible in the bridge while oracle is offline. Check how lending protocol handles that, likely liquidations also would not work.
Vault stake: should the vault stake be set to 0 while the oracle is offline, i.e., should vaults receive rewards while users cannot bridge from/to that asset?
Lending: can users repay their loans?
Remove all security states? (Running, Error, Shutdown) -> replaced by tx-pause.
Active block number: this is an issue. Active block number is not "asset aware". Either oracle works or it does not. When one asset is not reported anymore, we should give users/vaults more time - not count active blocks - for that asset. But not for the other assets.

Plan of action:

Remove OracleOffline error state to not halt the entire bridge when one or more assets are not reported by oracle anymore.

Active block number: this is an issue. Active block number is not "asset aware". Either oracle works or it does not. When one asset is not reported anymore, we should give users/vaults more time - not count active blocks - for that asset. But not for the other assets.

So let's just make ActiveBlockNumber a map of CurrencyId -> ActiveBlockNumber. In the on_initialize hook, we can just iterate over the currencies and increment those that are still active. The on_initialize hook can return a dynamic weight so that shouldn't be a problem. We could also optimize this in the future by only recording a (ActiveBlockNumber, BlockNumber, IsOnline) tuple when there is a state change between [online, offline]. The client can then add (currentBockNumber - recordedBlockNumber) to ActiveBlockNumber to determine the current value. But that's premature optimization, let's stick with the loop in on_initialize for now.

Seems like a substantial escalation of complexity but I haven't reviewed the problem in-depth to understand if there is an alternate solution. Which value would you propose we use for issue, redeem and replace requests?

Which value would you propose we use for issue, redeem and replace requests?

I was thinking for issue/redeem, the active block number associated with the collateral currency. But actually, now that I think about it.. Do we need the active block number at all? Right now we need it because you can't execute when the oracle is offline. But if we remove that limitation, I think we may actually be able to just execute if the oracle is down. Probably not all codepaths would work - for issue overpayment we need to check vault minting capacity, so we need the oracle to be online.. But it may be acceptable to not mint extra tokens tokens in that case. I'll investigate this idea further

Which value would you propose we use for issue, redeem and replace requests?

I was thinking for issue/redeem, the active block number associated with the collateral currency. But actually, now that I think about it.. Do we need the active block number at all? Right now we need it because you can't execute when the oracle is offline. But if we remove that limitation, I think we may actually be able to just execute if the oracle is down. Probably not all codepaths would work - for issue overpayment we need to check vault minting capacity, so we need the oracle to be online.. But it may be acceptable to not mint extra tokens tokens in that case. I'll investigate this idea further

What should work as normal:

execute_issue of pending issue with amount less than or equal to expected amount
execute_redeem (although the vault in question wouldn't get rewards since stake would be 0)
execute_replace of pending request
cancel_issue

What wouldn't work (or work differently):

execute_issue of pending issue with greater amount than expected: they wouldn't get more KBTC than they issued
execute_issue of cancelled issue would not work (can't check collateralization rate of vault)
cancel_redeem: requires price to determine compensation
request_replace
accept_replace
execute_replace of cancelled request: needs price for new_vault's collateral currency

All in all, I think this would be acceptable - there is no need to extend the time allocated for execution if the oracle goes down. All actors are able to process open requests as normal, as long as they act correctly. By that I mean that we can't provide some of  the mitigations in place for user error (e.g. issue overpayment). But since these mitigations are "best effort" anyway, I think that's acceptable. The only problem is cancel_redeem, which requires the oracle to determine the compensation amount. I think it's acceptable to require users to wait with cancellation in the event of the oracle being down - that should be a very exception case anyway. If required, though, we can think about changes to the cancel_redeem s.t. it still works, but it comes at the cost of increased complexity and I'm not sure that's worth it

@sander2 so the new proposal is to remove the error status and active block handling? For the latter I would assume we would still want to increase the global counter for now pending some future migration to revert back to the system height. I can't recall if there was another reason to extend the time allocated for execution but I'm open to this approach.

Yea that's right. Basically, we'd allow every function that doesn't fail in the oracle conversion to be callable.
Thanks for your reply, I'll discuss with Dom as well when he's back

I can't recall if there was another reason to extend the time allocated for execution but I'm open to this approach.

Yes, in case we would pause the parachain via SHUTDOWN state or the tx-pause module. In that case, users and vaults would not be able to execute requests.
However, this is not currency-specific. The tx-pause/SHUTDOWN would come into play when governance decide if there's emergency action to be taken.
So, I'd be in favor of the following change:

Remove the ORACLE_OFFLINE state
Stop counting the active blocks when the parachain is in SHUTDOWN state/tx-pause is active (not sure there's a nice way to combine the two?)
As Sander said, allow every function that doesn't fail in the oracle conversion to be callable
Handle oracle errors upstream: (1) The UI should show a validation error when users try to call functions that err when called. (2) The vault client should log that it can't call certain functions due to the oracle being offline.


runtime: TestAsyncPreempt failed on linux/arm64 and amd64

What version of Go are you using (go version)?

$ go version
go version devel +3f21c2381d Thu Nov 14 01:57:00 2019 +0000 linux/arm64

The issue was observed on linux/amd64 as well, so far the initial analysis is made on linux/arm64 only.
Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="arm64"
GOBIN=""
GOCACHE="/home/xiaji01/.cache/go-build"
GOENV="/home/xiaji01/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/xiaji01/.go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/xiaji01/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/xiaji01/go/pkg/tool/linux_arm64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/xiaji01/go/src/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build634223204=/tmp/go-build -gno-record-gcc-switches"

What did you do?

build and run package testing with the latest code.
What did you expect to see?
The case pass on all linux/arm64 and linux/amd64 platforms.
What did you see instead?
ok  	regexp/syntax	0.757s
--- FAIL: TestAsyncPreempt (60.01s)
crash_test.go:95: testprog AsyncPreempt exit status: exit status 2

proc_test.go:367: want OK

    , got SIGQUIT: quit

    PC=0xcb088 m=0 sigcode=0

    goroutine 7 [running]:

    main.frameless()

    	/root/ci-scripts/golang/src/runtime/testdata/testprog/preempt.go:56 +0x8 fp=0x40000cafc0 sp=0x40000cafc0 pc=0xcb088

    main.AsyncPreempt.func2(0x400001c154)

    	/root/ci-scripts/golang/src/runtime/testdata/testprog/preempt.go:36 +0x2c fp=0x40000cafd0 sp=0x40000cafc0 pc=0xce5ac

    runtime.goexit()

    	/home/root/ci-scripts/golang/src/runtime/asm_arm64.s:1148 +0x4 fp=0x40000cafd0 sp=0x40000cafd0 pc=0x6ae94

    created by main.AsyncPreempt

    	/root/ci-scripts/golang/src/runtime/testdata/testprog/preempt.go:34 +0xa8

    goroutine 1 [runnable]:

    runtime.Gosched(...)

    	/home/root/ci-scripts/golang/src/runtime/proc.go:269

    main.AsyncPreempt()

    	/root/ci-scripts/golang/src/runtime/testdata/testprog/preempt.go:42 +0xc8

    main.main()

    	/root/ci-scripts/golang/src/runtime/testdata/testprog/main.go:34 +0x194

    goroutine 6 [runnable]:

    main.AsyncPreempt.func1(0x400001c150)

    	/root/ci-scripts/golang/src/runtime/testdata/testprog/preempt.go:28

    created by main.AsyncPreempt

    	/root/ci-scripts/golang/src/runtime/testdata/testprog/preempt.go:26 +0x88

    r0      0x8e847c962

    r1      0xab9f639d053fa011

    r2      0x40000cafd0

    r3      0x0

    r4      0x40000ca800

    r5      0x40000013b8

    r6      0xce580

    r7      0x400001c154

    r8      0x1e7940

    r9      0x0

    r10     0x0

    r11     0x1bdea0

    r12     0x129068

    r13     0x0

    r14     0xf1

    r15     0x0

    r16     0x0

    r17     0x30

    r18     0x0

    r19     0xd0

    r20     0xffffe970c920

    r21     0x1e7940

    r22     0x4000002000

    r23     0x0

    r24     0x0

    r25     0x0

    r26     0x112288

    r27     0x4000000000000000

    r28     0x4000001380

    r29     0x40000cafb8

    lr      0xce5ac

    sp      0x40000cafc0

    pc      0xcb088

    fault   0x0

FAIL

The issue was observed on specific arm64 and amd64 machines only, 'fameless' is interrupted at consistent addresses which are considered to be non-safe every time upon preemption.
// arm64 machine
Architecture:        aarch64
Byte Order:          Little Endian
CPU(s):              32
On-line CPU(s) list: 0-31
Thread(s) per core:  1
Core(s) per socket:  32
Socket(s):           1
NUMA node(s):        1
Vendor ID:           APM
Model:               2
Model name:          X-Gene
Stepping:            0x3
BogoMIPS:            80.00
L1d cache:           32K
L1i cache:           32K
L2 cache:            256K
NUMA node0 CPU(s):   0-31
Flags:               fp asimd evtstrm aes pmull sha1 sha2 crc32 cpuid
// amd64 machine (just for your reference, I haven't made analysis on it)
Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              32
On-line CPU(s) list: 0-31
Thread(s) per core:  2
Core(s) per socket:  8
Socket(s):           2
NUMA node(s):        8
Vendor ID:           AuthenticAMD
CPU family:          23
Model:               1
Model name:          AMD EPYC 7251 8-Core Processor
Stepping:            2
CPU MHz:             2096.019
CPU max MHz:         2100.0000
CPU min MHz:         1200.0000
BogoMIPS:            4192.26
Virtualization:      AMD-V
L1d cache:           32K
L1i cache:           64K
L2 cache:            512K
L3 cache:            4096K
NUMA node0 CPU(s):   0,1,16,17
NUMA node1 CPU(s):   2,3,18,19
NUMA node2 CPU(s):   4,5,20,21
NUMA node3 CPU(s):   6,7,22,23
NUMA node4 CPU(s):   8,9,24,25
NUMA node5 CPU(s):   10,11,26,27
NUMA node6 CPU(s):   12,13,28,29
NUMA node7 CPU(s):   14,15,30,31
Flags:               fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid amd_dcm aperfmperf pni pclmulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c rdrand lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw skinit wdt tce topoext perfctr_core perfctr_nb bpext perfctr_llc mwaitx cpb hw_pstate ssbd ibpb vmmcall fsgsbase bmi1 avx2 smep bmi2 rdseed adx smap clflushopt sha_ni xsaveopt xsavec xgetbv1 xsaves clzero irperf xsaveerptr arat npt lbrv svm_lock nrip_save tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pfthreshold avic v_vmsave_vmload vgif overflow_recov succor smca

@cherrymui

I am seeing this in my go-tip snap builds too.

This occurs frequently in the linux-mips64le-mengzhuo builder:
2019-11-20T22:38:34-39a9cb4/linux-mips64le-mengzhuo
2019-11-20T22:37:23-be04718/linux-mips64le-mengzhuo
2019-11-20T19:43:21-fbcfa6a/linux-mips64le-mengzhuo
2019-11-20T17:13:59-b89b462/linux-mips64le-mengzhuo
2019-11-15T15:17:08-4e8d270/linux-mips64le-mengzhuo
2019-11-08T20:50:17-9e914f5/linux-mips64le-mengzhuo
2019-11-08T20:24:43-bababde/linux-mips64le-mengzhuo
2019-11-08T20:05:25-7a5e0fe/linux-mips64le-mengzhuo
2019-11-08T19:28:57-904e113/linux-mips64le-mengzhuo
2019-11-08T19:28:49-f6ff806/linux-mips64le-mengzhuo
2019-11-08T19:24:30-e6c12c3/linux-mips64le-mengzhuo
2019-11-08T18:55:44-b2b0992/linux-mips64le-mengzhuo
2019-11-08T18:25:40-aff3aaa/linux-mips64le-mengzhuo
2019-11-08T18:11:01-1fd3f8b/linux-mips64le-mengzhuo
2019-11-08T18:00:54-cfb1312/linux-mips64le-mengzhuo
2019-11-08T18:00:54-a2cd2bd/linux-mips64le-mengzhuo
2019-11-08T18:00:45-81640ea/linux-mips64le-mengzhuo
2019-11-08T18:00:31-c444ec3/linux-mips64le-mengzhuo
2019-11-08T17:53:22-c5fac1e/linux-mips64le-mengzhuo
2019-11-08T17:01:05-a5a6f61/linux-mips64le-mengzhuo
2019-11-08T17:00:57-dac936a/linux-mips64le-mengzhuo
CC @aclements @mknyszek

The functions being tested, although preemptible, may be preemptible only on small ranges of PCs, especially on architectures where we use REGTMP for returning from the injected call. It is possible that in some unlucky runs all the signals land on the non-preemptible ranges. We can relax the test a little bit, making it more preemptible.
With CL http://golang.org/cl/208126 and http://golang.org/cl/208217, it will not be a problem. But maybe not this cycle.


LaserScanPublisher not giving output

[x] I am at the right place and my issue is directly related to ROS#. General technical questions I would post e.g. at ROS Answers or Stack Overflow. For library-specific questions I would look for help in the corresponding library forums.
[x] I have thoroughly read the Contributing Guideline and writing this issue is the right thing to do in my case.

I have a question!

[x] I searched the Wiki, open and closed issues for an answer. I tried my best to find the answer by myself without success. I believe that the discussion we will have in this issue, and the solutions we might find, will help me, and likely other community members who have a similar problem.

Here is my question:
I want to use the lidar data from Unity in ROS. I'm working on the turtlebot3. I have added the LaserScanPublisher in the unity side. Is that enough to read the ranges[] in ROS or do I have to do something else ?

I found a bug!

[x] I am using the latest ROS# version available here on the master branch.

[x] I am adding all required information, code and data files, screenshots and log files so that you can reproduce the problem.

My OS is:

My Unity Version is: 2019.4

My ROS Distribution is: Noetic

My Build Target Platform is:

Here is my bug description:

Perform the following steps reproduce the bug:

Observed results:

Expected results:

Relevant Code:
<!-- Insert code here. Optionally attach code or data files to this issue. -->

I have a feature request!
I want to do this:

For being able to do it, I wish ROS# had the following feature:

Hi @amelia413 as I already wrote here, a publisher is enough. Please refer to the publisher references included in ROS# to learn and understand.

outdated / closing due to inactivity


Stop if junit result file is missing

backup solution for not properly configured ci-test script.
https://github.com/AckeeDevOps/jenkins-pipeline-nodejs/blob/5f265e7d18c2850c5817b68575d79fe45ffc8c14/vars/recordNodeTestResults.groovy#L4

I have to repair some tests first. Then we can switch to this scenario pretty smoothly.


Migrate CI jobs to Jenkins with a Jenkinsfile.

This PR provides a full rewrite of the CLI build system, including the addition of a source controlled Jenkinsfile for automated builds of a single Jenkins pipeline. The rewrite of the build system was designed to make the build scripts themselves more cross platform so we could run (essentially) the same commands across linux/mac/windows instead of writing highly customized build scripts for each platform into the CI. The move towards a Jenkinsfile was to (1) consolidate our CI into a single system (previously it was split across both Jenkins and TeamCity), and (2) put our CI scripting under version control instead of only tracking it the CI system itself.
Currently the Jenkinsfile is designed to accommodate a single job to run both binary builds and integration tests across all platforms. Ideally these would be split into separate Jenkins jobs, but the Multibranch Pipeline Plugin we currently use on Jenkins doesn't make splitting these jobs out like this easy (it hardcodes the location it looks for the Jenkinsfile to be at the root of the repository and you can't change it). In future revisions we should consider splitting the Jenkinsfile apart (and possibly pulling it into a library for other jobs to use). Once that is possible we can have separate Jenkinsfiles for each logical build and have them display separately in the checks field at the bottom of the PR.

Updated based on Jose's comments.


Integrate with Google BigQuery to support large query results

I'm working in a project which involves with querying a Google Bigquery server.
Depending on the sql and the data it's being ran on the output result (table) may be too large to fit in memory.
It would be very nice feature to use dask-sql to query over a Bigquery server, and get the resulted table as a dask data frame.
I've managed to think of a workaround to fit a very large sql result in a dask data frame:

prefix the sql with the export statement

Read the output file (in cloud storage) using dask.

Let me know what do you think :)

GREAT IDEA!

Hi @NI1993 - interesting!
Thanks for bringing this up.
So just to understand you correctly: you would like to run the SQL on big query and end up with a dask dataframe, correct?
Dask-SQL helps you with perfoming SQL statements on already present dask dataframes, so getting data from Big query would be somehow a step before that (and for Dask-SQL or would not be different from reading from e.g. files).
Did you have a look into
https://github.com/dask/dask/issues/3121? Unfortunately, I think this issue has not been continued, but I would be super happy to build that together with your help. I think it might make sense to move this to a different new package (dask-bigquery) or something.
The reason why I would propose to not include it to Dask-SQL, is so that other users without dask-sql can also create dataframes from Big query (and as we pass on the SQL, we do not need to "understand" the SQL).
What do you think? I would be very happy to get your input!


Prometheus VPA

Changes

@MasterPtato can you give this a close look & test it on staging to make sure it's solid?

@NathanFlurry you want me to deploy this to staging2?

@NathanFlurry lmk on slack when you get the credentials

Current dependencies on/for this PR:

main

PR #222   👈

PR #398

This stack of pull requests is managed by Graphite.

@NathanFlurry mb i turned this into a PR by adding to the stack

@NathanFlurry confirmed VPA working, had to update the prometheus count to 2 since the VPA can't scale otherwise


Devel

Removing the loading of moment.min.js is not required. The change can be made in the applications base template, either by overiding tail_js entirely or loading the desired version after. I believe the last loaded version takes precedence. In addition the change is only made in bootstrap3 templates.


Hide carousel

Resolves: [MWPW-115742(MWPW-URL)
Test URLs:

Before: https://main--milo--adobecom.hlx.page/
After: https://hide-carousel--milo--adobecom.hlx.page/

Verified that carousel block is hidden:
main:

hide-carousel:


[3.x] Backport fixes to documentation for paths, curves and navigation servers

Backport for https://github.com/godotengine/godot/pull/64534 and https://github.com/godotengine/godot/pull/64439.
cc @mhilbrunner

Thanks for the backport! 🎉

Cherry-picked for 3.5.1.


E474: Invalid argument after VIM update

I use ayu-vim-darker with vim's built in package management. After updating to vim(gvim) 8.2.4651-1 I started receiving an error in the terminal and for a moment in vim when it initially starts:

Error detected while processing /home/$USER/.vimrc[67]../home/$USER/.vim/pack/themes/start/ayu-vim-darker/colors/ayu.vim:
line  275:
E474: Invalid argument
Press ENTER or type command to continue

The theme still seemed to work just fine otherwise. After commenting out line 275 the theme still functions but with no error. May not need this line anymore.

Looks like our upstream has a fix for it: https://github.com/ayu-theme/ayu-vim/pull/72
I'll merge this ASAP.

I just pushed the fix. Please check if it works.

Fix confirmed working, Thanks!


DatePicker model & null value

Hi
For the model I use to have ng-model or data-ng-model but for the datepicker we have to use "model" alone. Is there any way to update this ?
Another point, when the value in the model is null (working with sql database), Invalid date is shown and there is no way to modify the value at all.

Another point for the datepicker : if I have a form with many fields, TAB brings me to the following instead for the datepicker, it jumps it.

And another problem : after the pick of a date, the model is an empty object with no value in it. value is not transfered to the model

Fixed on last version :-)


Requesting a textColor property

We added a picker text color attribute to the bottom picker widget check it out in the newest version 1.4.0
https://pub.dev/packages/bottom_picker


Nicer toString() for CdiContainer implementations

This was merged some time ago.
Feel free to close this PR.
Thanks!
https://git-wip-us.apache.org/repos/asf?p=deltaspike.git;a=commit;h=f92fcf3dce66f575f451a71554ec74d71d09b199


⚠ ClamAV has degraded performance

In d58c672, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 77 ms

Resolved: ClamAV performance has improved in 1892fd8.


Optimizes the reverse walker

We use reverse walker to get the path with the highest score composed by anchor nodes. The walker finds all paths but some of them are not really required, and finding them increases time complexity.
For example, when a user types "我這樣覺得", the walker has to find the following four routes and then choose the one with highest score:
[-8.68873387] 我(-2.27257609) -> 這樣(-3.14860584) -> 覺得(-3.26755194)
[-10.834656139999998] 我(-2.27257609) -> 這(-2.35405571) -> 樣(-2.9404724) -> 覺得(-3.26755194)
[-11.35937573] 我(-2.27257609) -> 這樣(-3.14860584) -> 覺(-3.20706759) -> 得(-2.73112621)
[-13.505298000000002] 我(-2.27257609) -> 這(-2.35405571) -> 樣(-2.9404724) -> 覺(-3.20706759) -> 得(-2.73112621)

However, from a user's aspect, the final product produced by these four paths are all the same - they all compose "我這樣覺得". A single node "覺得" and two nodes "覺" and "得" produce the same product. So, once we have a path ends with "覺得", when we are walking at the path ends with "覺", we should stop when we find the next node is "得" and it helps to save half of the time.
The PR also enlarges the size of the composing buffer to 40. Previously McBopomofo could be very slow when there are 20 readings in the composing buffer, but now it works fine with about 40. Some edge cases can still make it become very slow such as repeatedly typing "嗯嗯嗯嗯嗯嗯嗯嗯嗯嗯嗯嗯嗯嗯嗯嗯嗯嗯....".
These are also included in the PR:

Users can use shift + tab to reverse fast iterate the candidate
Makes composing buffer configurable
Makes candidate list style configurable

There are test cases failed. Fixing.


Made jsx attributes be referable as item

Fixes #912
Checklist

[x] I have added tests
[ ] I have updated the docs and cheatsheet
[ ] I have not broken the cheatsheet

What's the difference between these test cases and the ones you added before?

What's the difference between these test cases and the ones you added before?

This time it's actually for the correct language :s
https://github.com/cursorless-dev/cursorless/pull/1582#issuecomment-1627594230

Oh right 😄


Graph is rendered backwards when FlowDirection is RightToLeft

Describe the bug

When the FlowDirection of the app is RightToLeft, the graph renders all context backwards.
Steps To Reproduce

Launch app in RightToLeft FlowDirection
Go to Graph
Observe

Expected behavior

The graph should display the same as in any other language.
Screenshots

Device and Application Information

OS Build: 10 - 19041
Architecture: x64
Application Version: 10.2103.8
Region: en-US (but Hebrew is the language)
Dev Version Installed: True

Additional context

Requested Assignment

If possible, I would like to fix this.
I'm just reporting this problem.  I don't want to fix it.

This is your friendly Microsoft Issue Bot. I've seen this issue come in and have gone to tell a human about it.

Thanks for the detailed bug report! This appears to be a dupe of #1352, so going to close this for now. If you think this captures something different, please let us know, and we can revisit this.


Reorganize directory structure around CCCL

~(Do not merge, raising for discussion)~ Ready for review.
The current main branch generates a binary package with many files originated from the CCCL repository, which are essentially not required for CuPy's functionalities (C/C++ code, images, documentation, etc.)
This PR tries to mitigate the situation by placing cccl to thrid_party/cccl and taking only the necessary parts from there.
python setup.py bdist_wheel generates a wheel of:

main: 53 MB, containing 4001 files
This PR: 48 MB, containing 1949 files

Another idea could be to implement a filter in Python (like eb4922ebc0dc46c365149dff1729ebb4d2f82cc9), but I think it is harder to maintain.
If this is acceptable, we can also use the same strategy for Jitify and DLPack (which is not submodule currently due to directory structure) as well.
cc/ @leofang
refs #7851

Thanks, @kmaehashi! I have no objection in changing the location, but

I strongly prefer to not install things under site-packages/third_party (if I read the current PR correctly). I think it should be site-packages/cupy/third_party or site-packages/cupy_backends/third_party, i.e. under a subdirectory that CuPy owns
Is file pruning done (4001->1949) in the current PR? I may have missed the relevant bits.

Thanks for the comment Leo. third_party directory will never be included in sdist/wheels. Symbolic links (e.g., cupy/_core/include/cupy/_cccl/cub pointing to ../../../../../third_party/cccl/cub/cub) will be materialized as a real directory when generating packages.

/test mini

/test mini

@asi1024 Could you merge this one? 😃

LGTM!


Food Duplication

When crafting food in the Steve's Workshop crafting block, the NBT of the food gets messed up, letting you get huge amounts of food from the smallest piece.
Steps to reproduce:

Place any food item into a Steve's Workshop crafting table, with a (Vanilla Minecraft) crafting table in the upgrade slot.
Take the food item out of the crafting output. This food will not have a weight, and may have an erratic decay speed. If the food you are duplicating is cooked (I have not tested other forms of processing), this food will revert to the base version.
Now, in your inventory, place the food item into your crafting grid.
In the output, you should see a full, 160oz piece of food. There are actually several maximum size pieces and a smaller piece that you can take out, either by clicking and dragging each piece individually, or you can just shift-click on the output slot to get them all at once.
Now you have taken any size piece of food, and created several maximum size and a smaller piece of the base, unprocessed food.

Using version 2.16.4

I'll look to see if there is anything I can do to fix this. The issue is that TFC has its own food crafting handler that only works in player crafting grid.

I just tested, and this bug is present when using the vanilla Minecraft crafting table as well.

I have a solution of sorts for the issue. Just seeing I can find a more elegant solution.

Best solution available was implemented for Update 2.17.


TouchableOpacity in absolute position view on ios

Description
I'm building the react native project.
This code works well on Android but doesn't work well on ios.
if I touch the first half of the button, it works, but touch doesn't work on the end of the button on iOS.
      <View style={{backgroundColor: 'red', position: 'absolute', bottom: 0, alignSelf: 'center', width: 300}}>
        <TouchableOpacity onPress={()=>{console.log('clicked!');}>

          <View style={{flex: 1, backgroundColor: 'blue', width: 300}}>
            <Text style={{flex: 1, backgroundColor: 'green', width: '100%', textAlign: 'center'}}>
            Click Me!
            </Text>
           </View>

        </TouchableOpacity>
      </View>

React Native version:
System:
OS: macOS 10.15.4
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.13.0 - /usr/local/bin/node
Yarn: 1.22.0 - /usr/local/bin/yarn
npm: 6.13.0 - /usr/local/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.8.4 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.2, DriverKit 19.0, macOS 10.15, tvOS 13.2, watchOS 6.1
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Xcode: 11.3.1/11C504 - /usr/bin/xcodebuild
Languages:
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.11.0 => 16.11.0
react-native: 0.62.0 => 0.62.0
npmGlobalPackages:
react-native: Not Found

how was this fixed? @lizhming


add helm test to ci

Describe the solution you'd like
after #77 is merged, we should add a e2e test

@sozercan could you please explain what should be exactly tested here? Thx

same test as we have for yaml, but for helm

@sozercan Just to confirm - currently the e2e-test involves deployment of the eraser YAML. It looks like your concept of the helm version would not handle the deployment of the helm chart, but just the testing. Should then the current e2e-test have two modes, one which installs via plain YAML and one which doesn't install anything but relies on the installation already existing?

@sozercan @lee0c I think it might be a good idea to check that it's already deployed or not (by checking the existence of the namespace or the manager pod in a cluster). If it's already there - no deployment executed.
Another thing - I think it will be better to use the helm chart for e2e tests instead of a yaml manifest.

i didn't realize make e2e-test is actually hardcoded to use the eraser.yaml. Sounds like we need to separate out the logic for just running e2e

Another thing - I think it will be better to use the helm chart for all of e2e tests instead of a yaml manifest.

I think we should test both in parallel since helm has it's own generation logic that might be broken vs yaml's generation logic

@sozercan so I think the issue we will run into is that main_test.go has the logic to create the Kind cluster onto which everything is deployed, so it's hard to skip. That also introduces an issue to @anmalkov 's plan as we'd need to start the cluster (and therefore start the tests) prior to deployment.
Should we work on decoupling cluster creation/yaml deployment from testing? That seems like it would benefit all use cases by making code and cluster creation more reusable.

@helayoty any thoughts? since you added the main_test.go

@sozercan  @lee0c
Here is a sample PR of how to deploy a helm chart that we need to have before any tests start after creating a kind cluster using e2e framework
Another Sample here on how to deploy helm chart for any other reason (Redis, Nginx , DB, etc... )

@helayoty I guess that answers it, we will put the helm deployment into the testing code! Thank you for the pointers 😄

@pmengelbert yea i think we can close this. do we have any tests that tests yaml?


Implement "await for"

Internal Error: Unable to compile function(main) with the new compiler.
Reason: bailout: (await for(var x in foo()){print(x);}): await for

Fixed in https://github.com/dart-lang/sdk/commit/35839c784003fbfba689c29bd0f95aae2253d211


Marimekko charts

We’ve made some progress, but it’d be nice to have an “official” recommendation of how to do this.
https://observablehq.com/@observablehq/plot-marimekko
https://observablehq.com/@fil/observable-plot-marimekko-fork (faceting and simplifications)
Older alternatives:
https://observablehq.com/@data-workflows/marimekko-chart
https://observablehq.com/d/98afd8b064f98bb6
https://observablehq.com/d/7773a4b6c91df0da

I think https://observablehq.com/@fil/observable-plot-marimekko-fork is the best current effort. It has a single API entry point (transform):

marimekko({ sequence: "xy", anchor: "middle", x…, y…, value:…, ...options})

Examples show how to anchor text on the top-left, use facets, change the stacking sequence from xy to yx.

The example is ready to merge and publish. Is this something we'd want to have as a specific Plot.marimekko transform?

Sure, I like it, let’s open a PR. Is there a way to preserve the axes as absolute values (from 0 to sum(value) on both x and y) rather than always going from 0 to 1?

We can preserve the absolute sum on the axes with:
+  const sum = d3.sum(Plot.valueof(sales, "value"))
  return Plot.plot({
    width: 960,
    height: 640,
    label: null,
+    x: {transform: d => d * sum},
+    y: {transform: d => d * sum},

If we want to do it on the computed channels instead, we could either add an option for expand (to "expandIntoRange"…), or use this transform (which should probably be written differently!):
scaleUpXY = function ({ x, y, x1, x2, y1, y2, ...options }) {
  const [X, setX] = Plot.column(x);
  const [Y, setY] = Plot.column(y);
  const [X1, setX1] = Plot.column(x1);
  const [X2, setX2] = Plot.column(x2);
  const [Y1, setY1] = Plot.column(y1);
  const [Y2, setY2] = Plot.column(y2);
  return Plot.transform(
    { x1: X1, x2: X2, y1: Y1, y2: Y2, x: X, y: Y, ...options },
    (data, facets) => {
      const scale = d3.sum(Plot.valueof(data, "value")); // this would need the original values
      const X = Plot.valueof(data, x);
      const X1 = Plot.valueof(data, x1);
      const X2 = Plot.valueof(data, x2);
      if (X) setX(X.map((d) => d * scale));
      if (X1) setX1(X1.map((d) => d * scale));
      if (X2) setX2(X2.map((d) => d * scale));
      const Y = Plot.valueof(data, y);
      const Y1 = Plot.valueof(data, y1);
      const Y2 = Plot.valueof(data, y2);
      if (Y) setY(Y.map((d) => d * scale));
      if (Y1) setY1(Y1.map((d) => d * scale));
      if (Y2) setY2(Y2.map((d) => d * scale));
      return { data, facets };
    }
  );
}

Here's another iteration
https://observablehq.com/@observablehq/plot-marimekko-facets-plus-order


Capitalization throwing off the tensorflow_embedding classifier

Rasa NLU version: 0.12.2
Operating system: Windows 10
Content of model configuration file:
language: "en"

pipeline: "tensorflow_embedding"

Issue:
Capitalization is seriously messing up the intent classification for a model I trained using the new pipeline tensorflow_embedding.
Example (I'm just posting the relevant output from the parser):
'text': 'no'
'intent': {'confidence': 0.9569746255874634, 'name': 'disagree'}
'text': 'No'
'intent': {'confidence': 0.6564008593559265, 'name': 'disagree'}
# See the lower confidence
#----
'text': 'yes'
'intent': {'confidence': 0.9270809888839722, 'name': 'agree'}
'text':'Yes'
'intent': {'confidence': 0.6564008593559265, 'name': 'disagree'}
# It's classifying it completely wrongly.
# (variations like 'yEs', 'yES', and 'YES' also gives the exact same confidences as 'Yes')
#----
'text':'hi'
'intent': {'confidence': 0.8774316310882568, 'name': 'greet'}
'text':''Hi'
'intent': {'confidence': 0.6564008593559265, 'name': 'disagree'}
# Again completely wrong!

I have no capital letters in any of my training data utterances.
I have trained another model using the same data with the spacy_sklearn pipeline which gives me exact to the last digit same confidence in intents however I capitalize my input to the model.

Tensoflow embedding is building the word vectors from scratch. Spacy has pre-trained word vectors that may be the reason it is able to detect 'Yes' even if your training utterances don't have it.
So if i understand well,
You have not provided any training utterances with examples of 'Yes'?
Did you try adding them to your training data?

I agree with @souvikg10 , the probability of the intention when you test the utterances with capital letters is relatively low, so it means the program unsure which intention is the best because the utterances is new for program.

Yes, I also speculate that the way the new pipeline creates embeddings for words instead of using pre-trained ones is what is causing the issue. Unless it was a bug when the feature was incorporated. Or I am doing something wrong somewhere.
But point is, I think it is major drawback if the training data has to contain examples that vary just in their capitalization, because capitalization doesn't change the meaning of the text, and hence its a failure on the part of the NLU or the tensorflow_embedding approach.
I tried adding one more utterance YES to my data, and it started detecting all the variation of yes as agree intent correctly but the confidence levels are still an issue.
'yes' - 'confidence': 0.9103827476501465
'YES' - 'confidence': 0.8896434307098389
'Yes','yEs','yeS','YEs','YeS','yES' - 'confidence': 0.47380155324935913

Now this could still be an issue if I am setting a limit of 0.5 for least acceptable confidence.
I tried adding all the variations and then of course there wasn't an issue anymore.
But you can see how impractical it is to manually do that. It could be automated, but that would mean the training data size would increase multiple folds(unnecessarily) and it's using brute force to solve the problem, which is not elegant I'd say. Yet another option would be to just use something like lower() to change all the user input to lowercase before parsing.
I'm not just looking for a practical solution, but to make sense of what's happening and to find an elegant solution to it. 😃

If you guys are also trying the new pipeline can you just check if capitalization is messing up the classification for your models?

I think it is the same way Spacy's pre trained vector is trained as well. Spacy uses Wikipedia corpus( at least for Dutch) which also don't do well  in certain non-traditional languages . It completely depends on your corpus. I would really suggest to asses your use-case properly. Tensorflow embedding works really well on a narrow domain chatbot which  btw are 95% of the bots in the market. Do you really have users typing a word like, Yes and yes or yeah i understand but yEs ? if that's the case then even your spacy model might fail as well or you will have to crawl public forums and retrieve examples as such. and Capitalization can indeed change the meaning of a word.
"I want to ship a Book" or "I want to book a Ship". there is a difference..

For our work, i switched to tensorflow at the moment because it is giving better results compared to SpaCy's default model. But it is a narrow domain chatbot focussed on a proper set of questions. There are some niche edge cases we see but that are usually handled by the art of interrogation and asking the proper question to your user.

This is an interesting usability issue. There are a number of ways you can remedy this, and we should document this better.
The simplest is to pass a preprocessor to the CountVectorFeaturizer which just lowercases everything. Then "Hi" and "hi" get mapped to the same feature.
Another approach is to add nlp_spacy and tokenizer_spacy to the pipeline, because if spaCy is present, we will actually replace each token with its lemma. We didn't do that by default bc then you would still have to load a spaCy model.

Here is my pipeline and indeed i load spaCy's language model for tokenization that could be the reason why i am getting better results with tensorflow. Wasn't aware of that 👍
pipeline:
# this is using the spacy sklearn pipeline, adding duckling
# all components will use their default values

- name: "nlp_spacy"
- name: "tokenizer_spacy"
- name: "intent_entity_featurizer_regex"
- name: "intent_featurizer_spacy"
- name: "ner_spacy"
- name: "ner_crf"
- name: "ner_synonyms"
- name: "ner_duckling_http"
  locale: "nl_Nothing"
  url: "http://duckling:8000"
- name: "intent_featurizer_count_vectors"
- name: "intent_classifier_tensorflow_embedding"

cool! the documentation is just part of this repo, so you can create PRs the same way as for code changes. You will need to install a few more dependencies to build the docs, check out the docs section of dev-requirements.txt.
Agree- lemmatization is probably overkill so just lowercasing should do the job! We should consider making this the default. Currently the only preprocessing we do is mapping all numbers to the token NUMBER, https://github.com/RasaHQ/rasa_nlu/pull/981

@souvikg10
Okay, there might be some user case where we want to know the difference of words with capitals and those without. But the issue I was pointing out is use case independent.
And I know I also don't expect someone to type in "YeS" but if there is a typo I don't want to penalize the user by giving a random response to them, just because its not there in my training data set. 😄
Also the difference between the meaning of the sentences  "I want to ship a Book" or "I want to book a Ship" is not because of the capitalization. 😄
You've changed the word ordering and both are completely different statements.

@amn41
Okay! I will look at how to add to the documentation and try to keep making it more descriptive.
Yeah. Adding a case_sensitive flag to control case sensitivity of the tensorflow_embedding pipeline preprocessing would be a great and necessary addition I think.

That was just an example as I couldn’t think of any but I am sure they are words that are verbs and nouns though you are right it might not be necessarily due to capitalisation. I am not sure if it is wise to ignore capitalisation and make everything to lower. I would indeed enrich my training data.

https://github.com/RasaHQ/rasa_nlu/pull/1053

You can load spacy without loading word embeddings if only to keep all preprocessing in once place. If the spacy yaml. I think matching the spacy yaml quargs with the function signiture in initializing the nlp document. (along with case sensitivity allows spacy to be used with and without wordvectors, entity models, dependency parsing models etc.

Seems this was closed with #1053


Add CompanyServiceImpl Test

PR Checklist

[x] Read the contribution guidelines
[x] Added a brief description of these changes to the top of the changelog
[x] Changes in code meet test criteria (running mvn test returns exit code 0, without errors)

PR Type

[x] Test-related

Summary
Validate the proper mapping behaviour of CompanyServiceImpl method "readDetails"

Hi @bglamadrid,
Please check my changes in Changelog.md if its correct format


I won't post the full logs here because there's some personal information in them. Sorry!
Expected Behavior
No errors.
Context (optional)
I use a piece of software called "RAM Disk" by "SoftPerfect" (https://www.softperfect.com/products/ramdisk)
to virtualize the C:\Users\<USER>\AppData\Local\Temp directory.
A symbolic link at C:\Users\<USER>\AppData\Local\Temp points to a folder inside the RAM disk.
Self-contained Reproducer Project
N/A
Gradle version
8.10.1
Build scan URL (optional)
No response
Your Environment (optional)
     Edition  Windows 11 Pro
     Version  23H2
    OS build  22631.4169
  Experience  Windows Feature Experience Pack 1000.22700.1034.0

Same issue in the latest Gradle 8.10.1

Updating the TMP and TEMP USER variables to point to the RAM disk has made the problem go away, but this is only a workaround.

We appreciate the effort, but we must ask for more information so that we can triage it.
We do not see an immediate root cause, and we need a minimal reproducible example for the triage. If we have a reproducer project, we may be also able to suggest workarounds or ways to avoid the problem.
The ideal way to provide a reproducer project is to leverage our reproducer template. You can also use Gradle Project Replicator to reproduce the structure of your project.
This issue will be closed after 7 days unless you provide more information.

Issues that are tied to commercial software are complicated for us to investigate. Ideally, find a reproducer that does require this software
The exception is com.intellij.openapi.externalSystem.model.ExternalSystemException which points at an IntelliJ issue, not necessarily a Gradle issue. Does the problem happen when launching the build on the CLI?

@ljacomet ...
Reproducing it is pretty straight forward.

First remove the C:\Users\<USER>\AppData\Local\Temp directory.
In an elevated "Command Prompt" run: mklink /d "C:\Users\<USER>\AppData\Local\Temp" "/some/other/path" to create a symbolic link.
Observe that any Gradle based Android project opens in Android Studio with a "Gradle sync" error.
Observe that the few lines in the error log mention the path of the symbolic temp directory.

Understood.
But as I stated, the exception points at code inside the IDE not Gradle.
What happens if you invoke the build on the command line?
Does it fail?

Since Gradle apparently doesn't even have a Sync Project with Gradle Files function ...
https://issuetracker.google.com/issues/367439554


Error with ConstraintLayout: No resource found that matches the given name

app/build/intermediates/exploded-aar/com.folioreader/folioreader/0.4.0/res/layout/view_config.xml |
-- | --
No resource found that matches the given name (at 'layout_constraintBottom_toTopOf' with value '@id/view5'). |
No resource found that matches the given name (at 'layout_constraintBottom_toTopOf' with value '@id/view5'). |
No resource found that matches the given name (at 'layout_constraintBottom_toTopOf' with value '@id/view5'). |  ```

Fixed in v0.4.1


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-extensions/eventing-writers
/assign knative-extensions/eventing-writers
Produced by: knative-extensions/knobots/actions/update-deps

/retest

/retest

/test reconciler-tests-keda

/retest

/retest

/retest

/test upgrade-tests

/retest

/retest

/test upgrade-tests

/retest

/retest

/retest


Apps: don't build deprecated DH and DSA apps.

This also means that there doesn't need to be any conditional checks in the .c
files to avoid deprecated builds.

Travis failures aren't relevant.

Merged to master.  Thanks.


feat(buildJanetPackage.nix): executableFiles & binscriptFiles

executableFiles refer to declare-executable in project.janet.
binscriptFiles refer to declare-binscript in project.janet.

{
  pkgs ?
    import
      (builtins.fetchTarball "https://github.com/NixOS/nixpkgs/archive/36a9aeaaa17a2d4348498275f9fe530cd4f9e519.tar.gz")
      { },
}:

let
  janetBuilder = import ../../../default.nix { inherit pkgs; };
in
janetBuilder.buildJanetPackage {
  pname = "http-server";
  version = "0.1.0";
  src = ./.;
  depsFile = ./deps.nix;

  executableFiles = [
    {
      name = "http-server";
      entryFile = ./main.janet;
      install = true;
    }
  ];
}


[BEAM-13480] Increase pipeline timeout for PubSubIntegrationTest.test_streaming_data_only

PubSubIntegrationTest.test_streaming_data_only has been flaky, and was previously sickbayed in #16255. We've increased the pipeline timeout to prevent the failure of this integration test due to insufficient time.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

Run Python 3.6 PostCommit

Run Python 3.6 PostCommit

Run Python 3.7 PostCommit

Run Python 3.8 PostCommit

R: @TheNeuralBit
Looks like with the  updated timeout, PubSubIntegrationTest::test_streaming_data_only passes for all Python versions 3.6 , 3.7, and 3.8. I am kicking off another round to see if they will still pass.

Run Python 3.6 PostCommit

Run Python 3.7 PostCommit

Run Python 3.8 PostCommit

Sounds good, they all passed again!

Confirmed they look good, thanks again!
PostCommit seems to have a new issue:
17:22:14 FAILURE: Build failed with an exception.
17:22:14
17:22:14 * What went wrong:
17:22:14 Execution failed for task ':sdks:java:container:generateLicenseReport'.
17:22:14 > Could not resolve all dependencies for configuration ':sdks:java:harness:testCompileClasspath'.
17:22:14    > Could not resolve junit:junit-dep:[4.9,).
17:22:14      Required by:
17:22:14          project :sdks:java:harness > project :sdks:java:fn-execution > com.github.stefanbirkner:system-rules:1.19.0
17:22:14       > Failed to list versions for junit:junit-dep.
17:22:14          > Unable to load Maven meta-data from https://jcenter.bintray.com/junit/junit-dep/maven-metadata.xml.
17:22:14             > Could not HEAD 'https://jcenter.bintray.com/junit/junit-dep/maven-metadata.xml'. Received status code 502 from server: Bad Gateway

But I checked and the pubsub ITs did still run and pass.


Testing steps

Hello,
Regards this option "Here you can copy the WipAppid and use that for adjusting the WIP policy."
Can you please confirm that "WipAppid" should go in the WIP policy, for adding new app in Protect or Exempt apps, to the "Publisher" field?
This result/field name "WipAppid" not found in any other documents.
So would be great to have maybe added and explained in both sections, in this document and in:
"https://docs.microsoft.com/en-us/windows/security/information-protection/windows-information-protection/wip-learning"
What it is for "WipAppid" :)

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: af1d6af3-9530-fd12-cd25-52c904c5ac58
Version Independent ID: 8d5d6869-1ea9-05e3-76e9-4970fe1e7871
Content: Using Device Health
Content Source: windows/deployment/update/device-health-using.md
Product: w10
Technology: windows
GitHub Login: @jaimeo
Microsoft Alias: jaimeo

@officedocsbot assign @mypil

I've relayed this query to the product SMEs for this area.

Hello,
Small update of new tests, I try to test Google Chrome, test is to get WipAppid from Device Health and use it in WIP policy, so we don't ask user to go to GPEDIT and use AppLocker to export App info...
I see in Device Health the WipAppid as: "O=GOOGLE LLC, L=MOUNTAIN VIEW, S=CA, C=US\GOOGLE CHROME\CHROME.EXE\74.0.3729.108"
Seems that this "WipAppid" should be separated into backslashes:
Publisher: O=GOOGLE LLC, L=MOUNTAIN VIEW, S=CA, C=US
Product name: GOOGLE CHROME
File: CHROME.EXE
Versions can be star-start or minimum set to received "74.0.3729.108"
After device sync completed, I see Chrome being protected!
So maybe in this document, in section "Here you can copy the WipAppid and use that for adjusting the WIP policy.",
Would be great to explain how to use this WipAppid in the WIP.

@jaimeo - Do you have any updates on this?

@jaimeo - We would like to follow up on this. Do you have any updates?
Thank you.

@jaimeo - Do you have any updates on this?

@jaimeo - Any updates from the SME?

@jaimeo - We would like to follow up. Do you have any updates on this?
cc: @LauraWi

@matthewMWR can you advise? Also, @DulceMontemayor can you address the question about the other topic (https://docs.microsoft.com/en-us/windows/security/information-protection/windows-information-protection/wip-learning)?

@MatthewMWR @DulceMontemayor - We would like to follow up. Can you please share your insights on how to address this issue?
Thank you.

@jaimeo @MatthewMWR @DulceMontemayor - We would like to follow up. Do you have any updates on this?
Thank you.
cc: @LauraWi @AndreaBarr

@jaimeo @MatthewMWR @DulceMontemayor - Can you please advise how to proceed so this issue can be closed?
cc: @LauraWi  @AndreaBarr

Thanks for the info, I've updated this topic using the WipAppId example -
https://docs.microsoft.com/en-us/windows/security/information-protection/windows-information-protection/wip-learning#use-the-wip-section-of-device-health


Adding jQuery AJAX Start and Complete

@nodkrot could you resolve the conflicts in your PR and then I'll take a look? I did a recent commit so that may have caused it. Thanks.


Common Data Model source connector datetime/timestamp columns nullified?

We are using Azure Data Factory Mapping data flow to read from Common Data Model (model.json).
We use dynamic pattern – where Entity is parameterised and we do not project any columns and we have selected Allow schema drift.
We are having issue with “Source” in mapping data flow (Source Type is Common Data Model).
Problem: All the datetime/timestamp columns are read as null in source activity.
We also tried in projection tab Infer drifted column types where we provide a format for timestamp columns, However, it satisfies only certain timestamp columns - since in the source each datetime column has different timestamp format.
11/20/2020 12:45:01 PM
2020-11-20T03:18:45Z
2018-01-03T07:24:20.0000000+00:00

Question: How to prevent datetime columns becoming null? Ideally, we do not want Mapping Data Flow to typecast any columns - is there a way to just read all columns as string?
Some screenshots:
In Projection tab - we do not specify schema

In Data Preview tab
ModifiedOn, SinkCreatedOn, SinkModifiedOn - all these are system columns and will definitely have values in it.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ba002086-e5b7-023a-4f1c-d8912c67cecd
Version Independent ID: 6bab0cb3-7eae-644d-36ab-8f8676e78932
Content: Common Data Model format - Azure Data Factory
Content Source: articles/data-factory/format-common-data-model.md
Service: data-factory
GitHub Login: @kromerm
Microsoft Alias: makromer

@subashsivaji - Thanks for posting the issue. I am looking into it and will get back to you soon.

@kromerm - Can you please take a look and share your thoughts.

In your first screenshot above, click "infer drifted column types" and you can add a list of all of the different date/time formats that meet your incoming data. You cannot read it as string in the ADF source if it is defined as date/time in Manifest or Model. The type of the incoming data is defined in your CDM schema.

I have the same issue, can you help me?
I have a complex json as a source and when I want to preview data i get null for timestamp column types


ember-cli-chosen doesn't work well with promises

If you are passing a promiseArray to the #each helper to generate options, the ember-chosen component will initiate before any promises resolve and the chosen dropdown will be empty.  I made a quick and dirty fix that allows passing the promiseArray into the component and waits for it to resolve before initializing.  This seems like a poor solution but does work.  Is this something that should be supported? Maybe any promises we need should be resolved in the route before passing it into the template.  However it would be a useful feature to support. With hasMany async relationships this is a common situation.

@eliotpiering, I am having the same issue however I was wondering if you would mind sharing how you passed the promiseArray into the component and caused it to wait for resolution before initialization?


Added El Palito Coin to Token List

I agree to not ping anybody on Discord/Twitter/email about this pull request. Instead I will inquire by posting a new comment in the pull request if needed.

PRs are reviewed in bulk and and can take up to two weeks to be merged.
Please provide the following information for your token.
Please include change to the src/tokens/solana.tokenlist.json file in the PR.
DON'T modify any other token on the list.
At minimum each entry should have

Token Address:
Token Name:
Token Symbol:
Logo: (logo should be uploaded under assets/mainnet//*.<png/svg>)
Link to the official homepage of token:
Coingecko ID if available (https://www.coingecko.com/api/documentations/v3#/coins/get_coins__id_):

Updated the coin in another PR (sorry for not continuing here in this PR, next time I'll do that :)


Horizontal scrolling bar can't be moved

The horizontal scrolling bar in "my account" view is only be movable if your at the bottom of the transaction page. It would be better if it can be movable even at the top position so that we can see long smartbridge.

Fixed in #236


UI: Typing into the search label box (record card) is not working smoothly

Describe the bug
After 3 o 4 letters typed I cant continue writting
To Reproduce
Steps to reproduce the behavior:

Go to a records with a lot of Label
Search a label into the record box

Expected behavior
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS [e.g. iOS]:
Browser [e.g. chrome, safari]:
Argilla Version [e.g. 1.0.0]:
ElasticSearch Version [e.g. 7.10.2]:
Docker Image (optional) [e.g. argilla:v1.0.0]:

Additional context
Add any other context about the problem here.

https://user-images.githubusercontent.com/84135211/198574713-22091f1d-2119-46af-9147-0db7e1f22c92.mov


tradingview in npm

hi
i wanna ask a qusetion about tradingview professional library.
if i send a request for access this library and be accepted, can i use it with npm command?
how this is possible that i use with npm?

This issue tracker is not about charting library or any other TradingView's product (except lightweight-charts library of course). Please contact<EMAIL_ADDRESS>to get help.

vietnamese pls
Vào Th 2, 8 thg 2, 2021 vào lúc 15:37 Evgeniy Timokhov <
<EMAIL_ADDRESS>đã viết:

This issue tracker is not about charting library or any other
TradingView's product (except lightweight-charts library of course). Please
contact<EMAIL_ADDRESS>to get help.
[image: screenshot]
https://user-images.githubusercontent.com/3112183/107195103-f7cf4680-6a01-11eb-9d05-29bd6f7d1775.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tradingview/lightweight-charts/issues/695#issuecomment-774973593,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL575ANEO7VG2LD4GHGMAL3S56PGBANCNFSM4XHM22QQ
.


Question about DOTA dataset Version

Thanks for your coooool code and paper! Could you please tell me the version of the DOTA dataset?
It has 3 versions.

Thank you for your attention. The dataset used in the paper is DOTAv1.0. It's also the most popular one.


Motor movement fails

Same issues, different version (FB = 4.0.1).
If i move the bot to a certain coordinate, it fails randomly in a sequence.
With encoders on, all kit material, nothing special.
Look here:
https://forum.farmbot.org/t/v4-0-0-software-update/2152/11
Please solve this, it is soooooo unimaginably annoying that this thing even cannot move without errors!

@Klimbim1 please refrain from swearing on GitHub.
The parameter settings you have chosen all seem reasonable, so I am beginning to think you might have issues with your hardware installation that is causing the movement failures. Please check out this post: https://forum.farmbot.org/t/troubleshooting-failed-movements/2212
You might also try increasing the "Max Retries" number to 100, so that FarmBot tries many times to reach its destination.

I did everything I could @roryaronson in order to solve the problem.
I might check again the belt tension... but as there is no more specific debug message its quite hard to debug. Why can´t you write the axis in the debug log? From where should I know which axis caused the e-stop? What causes exactly the e-stop? The encoder giving feedback that it stalled for the xx many times that I set the threshhold in the config? As xx max. missed steps? The it tries the yy max. retries time to try that movement again before issueing this very unprecise log message?
I now set max. retries to 100 an apparently it worked, but that is only a statistic thing and I did not try many movements since then...
And swearing... I guess you didn´t hear me swear ;) at least it clearly tells you the state of mind of the user at that moment. Whether this should be edited, I doubt it, but you´re the admin...

The e stop happens deep in the firmware with no logging resources
unfortunately. (this is due to the nature of the system. There is just not
enough memory and internal resources of the Arduino to log this kind of
information)
The only thing that will cause a stop is missed steps.
On Jul 10, 2017 1:19 PM, "Klimbim1"<EMAIL_ADDRESS>wrote:

I did everything I could @roryaronson https://github.com/roryaronson in
order to solve the problem.
I might check again the belt tension... but as there is no more specific
debug message its quite hard to debug. Why can´t you write the axis in the
debug log? From where should I know which axis caused the e-stop? What
causes exactly the e-stop? The encoder giving feedback that it stalled for
the xx many times that I set the threshhold in the config? As xx max.
missed steps? The it tries the yy max. retries time to try that movement
again before issueing this very unprecise log message?
I now set max. retries to 100 an apparently it worked, but that is only a
statistic thing and I did not try many movements since then...
And swearing... I guess you didn´t hear me swear ;) at least it clearly
tells you the state of mind of the user at that moment. Whether this should
be edited, I doubt it, but you´re the admin...
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/FarmBot/farmbot_os/issues/331#issuecomment-314224159,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AUK8bhwJzJH5zVJ9qOMmVV9eaoeNCvNuks5sModtgaJpZM4OOyMx
.

Hey @ConnorRigby, is there really no way of specifying the plug of the encoder which is issueing the stall message (resp. missed steps)? Thats quite sad.... :(
Is there any other way to record current or the like of the motor at that moment? Thus one could judge about the stall of the motor itself.... is there any more information on when the motor stalls? How is that built mechanically?  Is there a slipping coupling (clutch?) inside the stepper motor?

I am by far an expert here but
the encoder is optical, so no physical connection like a clutch that would slip. As far as measuring the current, the electronics can't currently do that, and im not sure what would be needed for that. We may be able to at least determine which axis/motor caused the stall tho. @TimEvWw any thoughts on that one?

Is there any manuals or specs or something that I could read to know how the encoders exactly work? What does the motor do when driving into a barrier...?

The motor itself is a basic two phase stepper motor. Magnetic fields are applied in a specific order given by the stepper motor driver make the motor take a step. That part is completely done on the RAMPS board. The arduino only send three signals to the RAMPS board: on/off, direction, step. So the software just gives a command to take a step in the right direction. There is no direct feedback if it works or not. Hence the importance of encoder and good calibration. If the mechanical tension is too big for the magnetic fields in the stator, the rotor stalls. It just doesn't turn undetected.
Can we add something like current measurement. Sure, with enough time and money anything is possible. It would need a newly designed board, new drivers, new software for control or motors with integrated measurement and break all compatibility with current stuff and hackability that is a basic feature, but it's possible.
To come back to the money part, I'm sure that Farmbot as a company will be delighted to get an order request to do this ASAP and make a proposal for you. Otherwise if you're willing to wait a bit longer, we can see what is possible in the newer versions.
But as a cheaper solutions at his moment we use the encoder. The current models give a signal every time the optical sensor in the encoder sees a change. It's explained here.
https://en.wikipedia.org/wiki/Rotary_encoder#Incremental_rotary_encoder
The issue here is that there are a few hundred thousand signals coming from the encoder per second, what is a lot to process for an arduino board, but the latest version should manage. The software will then compare the theoretical position for the motor with the measured position of the encoder. There also is the issue that small grains of sand can already cause a small difference between motor and encoder. The difficulty is in making it sensitive enough to know it bumped into something, but not so sensitive that it stops on a grain of sand or a blade of grass. That all depends on your local situation, calibration of stepper drivers, quality of construction, how level the rail is, ...
There are messages that are generated but you don't see these on the message bar because there are too many messages like that and it would drown out any usable information.


Koa Debugging

I am new to koajs. please help me how to debug my koa code. i already used "node-inspector" it is showing this error:
Starting the interactive shell (REPL). Type .help for help.
The module in the current directory was not loaded: C:\Users\xxx\Koa Sample\app.js:6
app.use(function *(next){
^
Unexpected token *.
Didn't want to start REPL? Run C:\Users\xxxx\AppData\Roaming\npm\node_mo dules\node-inspector\bin\node-debug.js . instead.

That's most likely because your installation of nodejs lacks generator support. See https://github.com/koajs/koa#installation

juliangruber,  I am ruuning node 0.12.5 and "node --harmony app.js" this command is working for me but i am unable to debug my code can you please help me,,,,

@VenkatRamNDD that error is rather specific to not having generators enabled when running node, usually enabled using the right binary and the --harmony flag.

@VenkatRamNDD can you post some javascript we can run to test this issue?

@juliangruber followed this https://github.com/node-inspector/node-inspector to debug my koa(node) code...
This is my code:
var koa = require('koa');
var route= require('koa-route');
var app= koa();
app.use(function *(next){
var start = new Date;
yield next;
var ms = new Date;
console.log('%s %s - %s', this.method, this.url, ms, this.status);
});
app.use(function *(){
this.body = 'Hello World';
});
app.use(route.get('/index', index));
function *index(){
this.body="This is Index";
}
        app.listen(3000);
        console.log('Koa listening on port 3000');

and how exactly do you run it?

or rather, does your app work if you're not debugging? because if so, you should open an issue on your debugger's repo

@juliangruber my app works fine but debugging is problem...

@VenkatRamNDD Then please open an issue with your debugger. :-)

Still, the unexpected token * smells of non-harmony, so maybe when you run the debugger you must make sure you enabled harmony?

^ what I'm thinking


Unit tests for job->task-metadata

@wyegelwel addressed your feedback

@shamsimam happy to merge if there is nothing else you intend to change.

@wyegelwel please merge :)


Ansible SDK diagrams

This PR adds SDK architecture diagrams as conceptual content that describes local, mesh, and future insights capabilities.

FYI https://www.sphinx-doc.org/en/master/usage/extensions/graphviz.html + https://sphinxcontrib-mermaid-demo.rtfd.io exist.

Thanks @eqrx Maybe we can expand these diagrams out later but, yeah, maybe not the right time to get too in detail. I actually wonder if we even need this PR. But I suppose as long as they aren't misleading or making promises then I guess the diagrams have value in illustrating the intended usage patterns.

We need to add "Galaxy_NG" to wherever it says Automation Hub, so the upstream know what it is, or put a reference saying "Automation Hub Opensource project is Galaxy_NG"
Also can we replace Ansible Local Executor with Ansible-Runner, as the name change has not happened yet. thanks

@jonnyfiveiq Thx. Changes applied: https://people.redhat.com/dnaro/ansible-sdk-diagrams/intro.html#sdk-architecture

@jonnyfiveiq Can you please check the new changes once, so that we can proceed? Thanks,

Nice work, I approve


Add conditions for applying customization

Customize keeps adjustment when executing emotes, so when making adjustments to idle face expression and then using emote with expression, it makes the expression go "stronger". The example with lips shape and /smile is on the picture:

Adding conditions to enable/disable customization if certain requirements are met (for example execution of an emote, equipped a specific items) can extend functionality and create more applicability.

This isn't something that I plan on implementing. Will keep this open for unlikely case of someone else willing to implement this.


Forcing case in WG21 documents is weird

Right now bikeshed will force document short names for WG21 to have the first letter in lower case, and the revision number in uppercase, e.g.

d4321R0

This is weird, and no one else does this in WG21. We usually do one of the following (all of which are acceptable to me:

d4321r0
D4321R0
D4321r0

We should either not force this choice on authors, or force a better one.
@jfbastien ping as I suspect this is your fault.

Did you try not being out of date? #1259 😜

Yup, already fixed. 😀


twemproxy for the cloud!

Hi, I can see a lot of PR's and many keen developers on this project and I am wondering what final code would be useful for cloud based deployments? For our cloud systems DNS entries evolve over time and so a twemproxy members list might not be complete during twemproxy startup which leads to:
[2015-04-28 15:12:15.824] nc_conf.c:116 init conf server 0x6bc5f0
[2015-04-28 15:12:15.844] nc_util.c:495 address resolution of node 'n3.xx-redis1.xx.xxx.internal' service '6379' failed: Name or service not known
[2015-04-28 15:12:15.844] nc_util.c:274 free(0x6bcbc0) @ nc_string.c:54
[2015-04-28 15:12:15.844] nc_conf.c:499 conf: directive "servers" has an invalid value
[2015-04-28 15:12:15.844] nc_conf.c:466 pop 'n3.xx-redis1.xx.xxxx.internal:6379:1 redis3'

I have seen the idea of re-configurable YAML which is excellent and might help out in this situation. What we are looking for is a patch that we can use to ensure twemproxy always starts up even with backend network issues and then heals itself when the redis nodes in this case are registered on the network.
The other option would be to find "one" live redis start twemproxy and then later in the provisioning re-configure.
Any thoughts would be so welcome.

First, I am in favor of the notion of Twemproxy starting up even if it can't yet connect to the backend nodes. It should, of course, not accept commands until it has them, but it should at least start up.
That said, if you want to use DNS you'll need to ensure you use very short TTLs and that the client-side isn't doing any caching.
Regarding a reconfigurable YAML, I'd love to see a configuration API as Redis has (though not necessarily the same format - just using it as an example) such that you could start Twemproxy with no configuration and "program" it once active. This is an excellent and very useful feature for cloud based deployments because it allows you to deploy a bank of system and add/alter at runtime. As containers penetrate deeper into our stacks this will become even more useful.
Note this last concept of a blank-slate startup would also meet the criteria of being able to start Twemproxy w/o the backends available yet because it would require Twemproxy to start up successfully and wait for backends to talk to.
I'm not sure if I've submitted an issue for that feature request yet. Perhaps I can write it up in more detail today.

that is excellent thank you, if we could speed through something beers all round ! I am not keen on writing "work-a-rounds" making the start more robust is the way to go!
:+1:

Hey this is a great idea, we would love to see this on our project.

The future is here and it containerized on the cloud. This patch https://github.com/twitter/twemproxy/commit/fd34c29bb69861b37eea786bd84a7e437ab8bb7c enables address resolution of backend servers to be lazy. This means that the resolution of DNS names happens on connection requests to the server rather than on startup... Who is buying beers? :)
Would you appreciate if you'll could test this patch and confirm that it works as expected. Happy Friday!

@manjuraj Yes. this is simple than mine :)

thanks for the effort @charsyam

Tested this today with a simple Elasticache replication group of 1 master and 2 slaves. Manually promoting a slave to the new master (in the AWS console) results in write failures for around 15 secs, before the primary fqdn begins to resolve against the new master, whereupon writes start working again. Most excellent :-)

Excellent. Thanks a lot @tom-dalton-fanduel. This is very helpful

well done guys !! of cause I can supply the beers there is life in twemproxy yet !