Add a method to stop tracking a RawMemory segment using drop_segment.

It turns out that the Screeps driver doesn't check which segments are written at the end of a tick, so long as there are only 10 segments that are written to.
This leads to a bot being able to "touch" 20 segments in a tick:

10 to be read at the beginning of the tick (from the setActiveSegments)
10 to be written at the end of the tick (in RawMemory.segments)

However, no checks is done to verify that the written segments are part of the active segments.
Thus, by adding a way to drop_segment (this PR) (deleting it from RawMemory.segments), it can make space to write to a different segment.
Note: deleting RawMemory.segments[k] is local only, it doesn't touch the actual data in the segment.

This is a pretty awesome thing, though! I had no idea we could manipulate segments written like this.


obsolete	GO:0006288	 base-excision repair, DNA ligation

Please provide as much information as you can:

GO term ID and Label

GO:0006288	 base-excision repair, DNA ligation

Reason for deprecation

combined a functional and a process
(obsolete or merge)

Are there annotations to this term?

How many EXP:  7

Any other information
(I am picking up PAINT annotations to this term)

See more complete
https://github.com/pombase/pombase-chado/issues/1192


Demo site: violet GitHub icon should point exactly to the relevant page inside the repo

i.e. not just to the repo in general

Which page is relevant?

Ah I see 👌


missing property: serilization.lib

Hi there,
Today inexplicably (as far as I currently know) the following error stopped our prestogres adapter being able to talk to Presto:
STATEMENT:  select 1 from (select prestogres_catalog.setup_system_catalog(E'[redacted]', E'[redacted]', E'presto', E'default', E'pg')) s;
2015-02-04 00:00:02: pid 21280: FATAL:  Backend throw an error message
2015-02-04 00:00:02: pid 21280: DETAIL:  Exiting current session because of an error from backend
2015-02-04 00:00:02: pid 21280: HINT:  BACKEND Error: "presto_client.PrestoQueryException: Query 20150204_000002_00000_aj2wj failed: missing property: serialization.lib"
2015-02-04 00:00:02: pid 21280: CONTEXT:  while searching system catalog, When relcache is missed
If I execute any query I get the above error message. If I execute the same query through the presto-cli it works as expected.
As far as I'm aware there have been no changes made to prestogres, but I have tried a fresh pull and build to check, but no joy.
Any pointers would be greatly appreciated as I don't see this in the docs but may be something quite intricate too.
Thanks.

I haven't seem the error message. Because the message includes query id (20150204_000002_00000_aj2wj), the message is created by Presto. So Presto thought "serialization.lib" is a missing property.
setup_system_catalog runs this query before running the actual query you issued:
select table_schema, table_name, column_name, is_nullable, data_type
from information_schema.columns

Can you run this query using presto-cli?
Here is the document about the query: https://github.com/treasure-data/prestogres#i-can-connect-to-prestogres-but-cannot-run-any-queries

Turns out this was related to a bug in presto. For interest the issue is logged here; https://github.com/facebook/presto/issues/2317


Error: Index passed  to line/column function (x) does not keep with order (last was x)

<input type="text" readonly/>

Linter throws an error
Error: Index passed  to line/column function (322) does not keep with order (last was 453)

But if there  a space at the and of boolean attribute,
<input type="text" readonly />

It works Ok
I think the bug is inside attr_parse.js file.
var attrRegex = /(\s*)([^ "'>=\^]+)((\s*=\s*)((?:"[^"]*")|(?:'[^']*')|(?:\S+)))?/g;

execute [ readonly/ ] attribute from
<input type="text" readonly/>

but must execute only [ readonly ]
it works as expected if I change
 var attrRegex = /(\s*)([^ "'>=\^\/]+)((\s*=\s*)((?:"[^"]*")|(?:'[^']*')|(?:\S+)))?/g;

For you information, in the case of <input> in HTML5 the closing backslash should be omitted. So, yes the error is incorrect, but your solution is invalid (note here that this is "An unofficial html5 linter and validator."[1]).
However, as per this discussion it is worth to note that in some cases the backslash may still be needed (e.g. in SVGs, relatedly #94). But I'm not familiar enough with the inner workings of this linter to tell if that is actually relevant...

I'm agree with you, but html-linter does not throw an error if there [closing backslash] inside input.
Linter throws "Index passed to line/column function (x) does not keep with order (last was x)". For me, this message is not clear.One more thing, when I use htmllinter with lint-staged package (https://github.com/okonet/lint-staged/issues/499) and htmllinter receives 'readonly/>' due to lint-staged there are no error at all. In this case, htmllinter behaves as html code is valid, even if there are non valid html elements, and all checks are succesfull.

I'm agree with you, but html-linter does not throw special linter warning if there closing backslash inside input(< input readonly/>. Linter throws

I think it should, and indeed the message is not clear. However, I'm not a maintainer of this project so I can't decide on what will happen.
In hindsight, maybe calling your solution invalid wasn't completely fair. I think it will be useful to merge #249 so the attr-order check won't fail because of this 🤔

@ericcornelissen Who can submit  my PR?

I think changing the regex is a reasonable fix for this. Per the spec, slashes aren't allowed in attribute names, so this makes the attribute parsing more accurate.
This situation does only occur with invalid html (I could be wrong here, of course). However, htmllint tries to work with invalid html to the greatest extent possible. So it should indicate the issue (which it does, if tag-self-close is set to "never", i.e. html5 style) but otherwise handle it like a browser would.


Qa tools

For your review, Tal.
I recommend you start from the README
in a nutshell, you can commit with npm run commit

Looking at the diff, looks like formatting for applied as well ;-)

See the errors from yarn, in Github Actions:
/usr/local/bin/yarn --frozen-lockfile
yarn install v1.22.19
[1/4] Resolving packages...
error Your lockfile needs to be updated, but yarn was run with `--frozen-lockfile`.

Looks like you need to update the yarn lockfile (forgot to commit it?)

it worked, tests passed ;-)

BTW: Looks like there is a nice Visual Studio Code plugin for Commitizen: Visual Studio Code Commitizen Support

Need to mention the linking:
Related to #23


[C++] Check for memory allocation overflow errors

Detect overflow errors related to memory allocation and memory access,
specifically in: bond::OutputMemoryStream, bond::blob, and
bond::detail::SimpleArray.

Maybe a negative unit test would be helpful seeing by how this implementation is finicky.

I made one more tweak so that the two unsigned integers types don't have to be the same (the first one must be larger than the second).
I think this is ready to go now. Please squash the commits together when merging.


Artifact segregation

This PR changes the main build step in Maven to do a deploy instead of package. But instead of installing into the .m2 cache we install into the artifact staging directory. Basically lifting a repository instead of trying to roll our own segregation.

/azp java - core - ci

/azp run java - core - ci

This pipeline shows what an upload Maven repo looks like as an artifact:
https://dev.azure.com/azure-sdk/public/_build/results?buildId=371058&view=artifacts&type=publishedArtifacts

@mitchdenny, since this does change the artifacts directory I would highly recommend verifying that the publish package and publish docs steps still work. The publish docs ultimately ends up calling copy-docs-to-blobstorage.ps1 and it would be good to know that this process still works. I'd rather not have surprises happen during the next release.

Yeah ... good call I'm merging this into a feature branch on upstream to do some experimentation.


Proposal for spec tweak wrt receiving an ATTACHED while detaching

Unlike receiving a DETACHED while attaching, which is specified by RTL13, the spec does not define the behaviour if the client library receives an ATTACHED while detaching.
All we have is the spec for detach ((RTL5d) Otherwise a DETACH ProtocolMessage is sent to the server, the state transitions to DETACHING and the channel becomes DETACHED when the confirmation DETACHED ProtocolMessage is received), and the normal spec for what happens when the client receives an ATTACHED, which is in the section for channel#attach() and is not clear on whether it applies only in that context or at any time.
Paddy's answer when this sort of question has come up in the past has been "the server sends the definitive channel state"; the client adopts whatever channel state the server tells it it's in. Ably-js is written accordingly: when the client receives an ATTACHED while detaching, it obediently goes into the attached state.
The problem with this is that the channel state is overloaded; it represents both a reflection of the server state, as well as a reflection of the intentions of the user. Hence the existence of pending states, and the suspended state (for 'I'm detached and not currently attaching but the user wants me to eventually be attached'), and the automatic re-attach when you're attached and there's a server-initiated detach.
This last one is the one that's causing trouble here. Have the following sequence of events:

user calls attach(), client sends ATTACH, client state attaching
user calls detach(), client sends DETACH, client state detaching
client receives ATTACHED from server, client state attached
client receives DETACHED from server, client sends an ATTACH per RTL13, client state attaching
client receives ATTACHED from server, client state attached.

...So the channel ends up attached, despite that the last thing the user did was signal their intention to detach the channel.
Additional side-problem: the detach() callback is called when the client receives the first ATTACHED, it doesn't know to wait for the next channel state message.
(additional side problem on top of the side problem: not populating the callback error when this happens)
We know the solution to this - we decided it back in 2017.  It's to add ids to client-initiated ATTACH/DETACH protocol messages and reflect them back in the corresponding ATTACHED/DETACHED, so that the client library can properly pipeline requests. Then it would know that when it gets the first ATTACHED that the DETACH is still pending, and keep the channel state as detaching. And it would know not to call the callback of the detach until it gets a detached with the right id (or something that overrides, like a fatal error).
But, let's face it, we're not going to imminently change the attach/detach protocol this fundamentally. So I'm going to propose the following workaround:
RTL5g: If the channel receives an ATTACHED message while in the DETACHING state, it should send a new DETACH message and remain in the DETACHING state.
This makes it much more symmetrical with attaching, where if we get a DETACHED while attaching we keep trying to attach (after a brief dalliance with the SUSPENDED state).
Not the perfect, but I should handle the biggest problem we have now without the effort of a protocol change.
@paddybyers @QuintinWillison wdyt?
cc @rmbellovin
┆Issue is synchronized with this Jira Task by Unito

This was added in https://github.com/ably/docs/pull/1044


Polygon case

Hi, I finally have been able to test this plugin properly (thanks a ton for it).
While it works nicely for lines, I incurred in an issue for polygons. Let's see if I am able to explain it.
If I load the polygon using the right coordinates (i.e. first and last equal), I get this:

which has the following problem, if editing the startpoint:

I am thinking about a possible workaround but nothing clean comes to my mind. I think the best would be to remove the last point during editing and then add it back once editing finished (it is anyways the same as the first).
The problem is that while the drag markers should have one less, the editing Polyline shown below the markers, needs to be closed, else one edge is missing.
And since the two share the same list of coordinates in order to be able to "move" consistently during dragging... I have no idea what would be best to do here. Do you have any idea? :-)

Can you confirm if you have the latest version (was updated about 27 days ago)...I thought there was a fix for that, so just wanted to make sure it's not something already fixed.
If you're on the latest one, could you add a minimal example case, and I'll take a peek when I get chance.

Yes, I have the latest version. I see you added addClosePathMarker in the last commits.
I will try to create an example, thanks.

@ibrierley , just opened PR #8 to see the issue. Thanks.

What are you setting addClosePathMarker to when creating your PolyEditor instance ?  I think you have that missing (think that's my fault as I should include it in test example, it is in the readme) ?
eg   addClosePathMarker: false, // set to true if polygon, false if polyline,

No, I got it right from either your code or the readme.
I am setting: addClosePathMarker: true,
when I am handling a polygon.

Just looking at your code (I'm not able to test just atm), you are using a polyline, but addClosePathMarker: true... I suspect you want this to be false, as you're actually using a polyline in the code, not polygon ?

OMG! it was too obvious. I though this would edit only polylines, but in case of polygons I am allowed to use polygon!
Sorry sorry for all the noise. I just tested and it works perfect.


fix: attendance typing && expose full attendance response object

I added more detailed typing on the getAttendance function and so now full response object can be exposed. I also removed the strict PM and AM periods in favor of a record as this can change based on what the school has setup (for example Period 1, Period 2...).

Thanks!


[UPGRADE] Security related upgrades

dgrijalva/jwt-go is no longer maintained. We may need to move to golang-jwt/jwt at some point.

Ticket? :-)


Allows tests to be skipped

This PR introduces two minor changes to the CMake build infrastructure in order to facilitate including Sprout in another CMake project via CMake's external project API.
The first change ensures CMAKE_BUILD_TYPE is only set if it is not already set.  Previously it was always being set to Debug.
The second change introduces a variable BUILD_TESTS  which controls whether or not the tests are built.  From the perspective of the top-level CMake project (i.e. the one including Sprout via CMake's external project API), having to build the tests significantly increases the compile time.  I have introduced BUILD_TESTS so that it defaults to true, thus providing a build analogous to before BUILD_TESTS introduction.
Both of these changes should be transparent to other Sprout users.

I appreciate your contribution.

Your welcome and thank you for writing Sprout; it has saved me a ton of coding.


Add GitHub actions

This only checks that the scripts work properly. It can't check anything related to the SV code, because we can't run a simulator.


Static Help Names

Some bots have a changing display name, in order to provide some sort of information. For example, Garmy's infobot, POMBot, embers/firebot, that one that shows the time (Xyzzy's?). However, not all of these respond to commands using their "proper names" (eg !help @POMBot), which may can make usage annoying or difficult, especially on mobile or if the display is changing frequently.
Thus I propose adding some sort of rule or guideline about "static names" to the "Non-standard commands" section, eg "bots whose display name regularly changes should have a "static name" which they also respond to as well as their current one, and which is somehow mentioned in their !help"
Thoughts, feedback?

Sounds good to me!

Agreed; it’s probably especially useful for bots whose names change frequently - for instance, POMbot is relatively unlikely to change name between its nick being autocompleted and ‘enter’ being pressed, but the time bot and firebot especially are important. I think it would be worth specifying all nicks a bot responds to in the response to !help.

If the help does not list nicknames, one should assume the current name of the bot.

Maybe show the static nick in the general !help, like this:
[(10P15B1N)] @PBL | I count the types of clients in my nick

I'd perhaps append a (see !help @PBL) instead.


新建React Native 项目无法运行

rn小白一枚，按照官网安装步骤一步一步的安装，项目无法运行....
以下是报错信息
PS D:\android-project\AwesomeProject2> yarn android
yarn run v1.22.4
$ react-native run-android
info Running jetifier to migrate libraries to AndroidX. You can disable it using "--no-jetifier" flag.
Jetifier found 960 file(s) to forward-jetify. Using 4 workers...
info JS server already running.
info Installing the app...

Task :app:compileDebugJavaWithJavac FAILED

Deprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings
11 actionable tasks: 2 executed, 9 up-to-date
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Could not find tools.jar. Please check that C:\Program Files\Java\jre1.8.0_251 contains a valid JDK installation.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 3s
error Failed to install the app. Make sure you have the Android development environment set up: https://reactnative.dev/docs/environment-setup. Run CLI with --verbose flag for more details.
Error: Command failed: gradlew.bat app:installDebug -PreactNativeDevServerPort=8081
FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':app:compileDebugJavaWithJavac'.

Could not find tools.jar. Please check that C:\Program Files\Java\jre1.8.0_251 contains a valid JDK installation.

Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

Get more help at https://help.gradle.org

BUILD FAILED in 3s
at makeError (D:\android-project\AwesomeProject2\node_modules\execa\index.js:174:9)
at D:\android-project\AwesomeProject2\node_modules\execa\index.js:278:16
at processTicksAndRejections (internal/process/task_queues.js:97:5)
at async runOnAllDevices (D:\android-project\AwesomeProject2\node_modules\@react-native-community\cli-platform-android\build\commands\runAndroid\runOnAllDevices.js:94:5)
at async Command.handleAction (D:\android-project\AwesomeProject2\node_modules\@react-native-community\cli\build\index.js:186:9)

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

image 谢谢大佬，已经解决啦

这个问题我也遇到了，确实，只要安装下jdk 8就好了


rpgleIndentationEnabled Gone?

Where did "code-for-ibmi.rpgleIndentationEnabled": true go? I know it was experimental, but I liked the feature ! And it worked fairly recently, now it is "unknown Configuration setting". In fact, per #387, it looked like it would be handy to totally fix indention.
I don't can't see any references here. Only this:
Enable these options in VS Code settings.
vscode-rpgle.rpgleColumnAssistEnabled - column assist for RPGLE fixed-format.
vscode-rpgle.rpgleColumnAssistant / Shift+F4 to launch it when on fixed-format line
vscode-rpgle.rpgleContentAssistEnabled - shows content assist and enables the following commands
vscode-rpgle.rpgleOpenInclude / Shift+F12 when on copy or include statement
vscode-rpgle.rpgleLinterSupportEnabled - enables linter
vscode-rpgle.openLintConfig to open or create linter file. Creates / opens relative to source that is currently open. Read more below on linting.
I have 0.0.4 of the extension installed, but get some (inconsistent) messages and squiggly line on indentation. Couple of examples:

Hey @SJLennon - sorry, I don't really understand what the question is here.
Could you clarify for me?

@SJLennon Having re-read it a few times, please feel free to share a snippet of code you're having issues with.
This is a fairly large change, I'm aware. Once we get the kinks worked out after migrating all the code, it will be great.

@worksofliam Well, let me try to clarify...

There is  nothing about indentation in the readme.  (That I can see.)
If I don't want it there is not a way to turn it off. (Not that I want to turn it off if it works, but someone might.)
The "quick fixes" you added recently no longer seem to work.
It appears inconsistent in when it checks for and how it reports errors.

I started this comment before your prior response about a "fairly large change" appeared.  1. and 2. and 3. still apply.  For 4. lets work with this.
I just opened code that was previously saved and it seems to be  correct in reporting the errors:

I have attached that file as LOG.txt. (The code does compile but is largely just a demonstration.)
If I correct line 22, by removing all the leading blanks and then inserting a tab, I get this:

Note that there is a squiggle in line 22 under the "J" and the PROBLEMS tab still says "got 12" for line 22.
If I insert after line 26, it doesn't notice that the indentation is incorrect:

Hope this helps.
Even if I correct line 26
LOG.txt

@SJLennon It seems to be working for me.
I tried your code, it was showing the correct indentation warnings and I also was able to get it to react to another validation error.

This is on 0.0.5.

@worksofliam 0,0,5 makes no difference.

I've restarted VS Code multiple times just to be sure I always have a clean environment.
I've uninstalled the extension, restarted VS Code to see that there is no indentation checking, re-installed the extension. No difference.
I created a brand new connection.  Still no success, other than it didn't ask me to install the Cl Prompting tools, which my my other two connections always do.

Perhaps there is some other extension that is conflicting with it.
Or perhaps I have something odd in my settings.json.  I may try removing all code for ibm i stuff from setting.json and just start over.  Or maybe I'll try installing VS Code in a virtual machine and start clean there.

@SJLennon what version of Code for IBM i do you have? Perhaps an old version if conflicting with it.
Honestly, I am still lost at what your issue is. Sorry about that.
Are the errors not over the right columns? Are certain errors not appearing?

I'm on the latest version of everything.  Living on the bleeding edge...
Code for IBM i 0,8,2
VS Code 1.62.3

No success with a brand new installation
So is the problem Windows, or is it PUB400?  Is it me?  Thoroughly confused ☹ .
The details:
Running under VMware and Win 10. Win 10 up to date.
First time installation of VS Code in this VM.  No customization other than to pick the theme  (stttings.json provided belwo).
Only 4 extensions installed.

Created new connection. Opened source, got errors as expected:

Deleted leading spaces on line 22. Still has squiggles.
Fixed line 26.  Still has squiggles.
Inserted after line 26.  New line 27 has no indication of error.
Problem tab has not changed.

Shorter version of test code:
LOG.TXT
Settings.json:
{
    "workbench.colorTheme": "Visual Studio Dark",
    "code-for-ibmi.connectionSettings": [
        {
            "name": "tPub400",
            "objectFilters": [
                {
                    "name": "temp",
                    "library": "LENNONS1",
                    "object": "TEMP",
                    "types": [
                        "*SRCPF"
                    ],
                    "member": "*",
                    "undefined": "temp"
                }
            ],
            "databaseBrowserList": [
                "LENNONS1",
                "LENNONS2",
                "QTEMP",
                "QGPL"
            ],
            "libraryList": [
                "LENNONS1",
                "LENNONS2",
                "QTEMP",
                "QGPL"
            ],
            "customVariables": [],
            "connectionProfiles": [],
            "ifsShortcuts": [
                "/home/LENNONS"
            ],
            "homeDirectory": "/home/LENNONS",
            "tempLibrary": "LENNONS1",
            "currentLibrary": "LENNONS1",
            "sourceFileCCSID": "*FILE",
            "enableSQL": true,
            "hideCompileErrors": [],
            "enableSourceDates": false,
            "sourceDateLocation": "none",
            "clContentAssistEnabled": false,
            "autoSaveBeforeAction": false
        }
    ],
    "code-for-ibmi.connections": [
        {
            "name": "tPub400",
            "host": "pub400.com",
            "port": 2222,
            "username": "lennons",
            "privateKey": null
        }
    ]
}

@worksofliam

@worksofliam Spent the evening building a Ubuntu VM.  Installed VS Code.
Just connected to PUB400.  Opened source and it seems to have the same problems.  More experimentation in the morning...

@worksofliam Spent the evening building a Ubuntu VM.  Installed VS Code.
Just connected to PUB400.  Opened source and it seems to have the same problems.  More experimentation in the morning...

@SJLennon You next best thing to do is a get a video recorded for me.

@worksofliam Can you suggest the best software to record a video? (Presumably you mean recording the screen, because I don't have a camera of mike on this desktop.)

@worksofliam
I have new findings It seems like a switch to another tab, then switching back causes a rerun of the indentation logic.
I've replicated the problem on my Win 10 desktop, in Ubuntu in a VM, and today in a new installation of VS Code on my Win 10 laptop. So I don't think the issue lies is my hardware, OS or my VS Code configuration.  So I did some more testing and stumbled into this;
I have two files, A_ERR which has two indentation errors and A_OK which has no errors.
My test script:

Start VS Code and connect to PUB400.COM
Open a source file that contains A_ERR and A_OK.
Clear Code for IBM i output.
Open A_ERR.  (Code for IBM i output shows member being copied twice to the IFS.  Don't know if this is significant or normal.)
In A_ERR there are errors at line 22, line 26, and in the PROBLEMS tab.
Fix the error at line 26.  Errors still show on line 26 and in the PROBLEMS tab.
Open A_OK.  (Two copies again from member to IFS.)
A_OK has no errors in it.
Switch back to the tab with A_ERR. Now line 26 shows no errors, line 22 still has an error, and the PROBLEMS tab shows just the line 22 error.
Fix the line 22 error. Nothing changes, error still show on line 22 and in the PROBLEMS tab.
Switch to A_OK,
Switch back to A_ERR. Now it has no errors shown and there is nothing in the PROBLEMS tab.

After some more experimentation, it doesn't seem to matter that the second tab is RPGLE or something else, or if it has errors or not. It seems like switching away from the tab with errors and switching back to it corrects the indentation errors.
I'm curious about the copy from source member to IFS.

If I switch tabs between A_OK and A_ERR without making any changes I see the copy taking place each time. I assume this is normal.
But when I make a correction to A_ERR, and switch to A_OK, I see A_OK being copied.. But when I switch back to A_ERR no copy takes place.
In fact, once I've fixed A_ERR, switching between tabs always causes a copy for A_OK but never for A_ERR. Which, to me, seems odd.

My test files, in case they are useful;
A_ERR.TXT
A_OK.TXT

@SJLennon Just want you to know this is on my priority list after I am done working on another Code for IBM i bug.
Will get back to this ASAP.

@worksofliam Appreciate the update and your efforts.
I'm not inconvenienced.  Handle things that impact most users first.

@SJLennon Good news!! I finally recreated this issue.
I think I know the cause... will post again when I am able to work on it.

@SJLennon I just released 0.0.7 - will you give it another go?

@worksofliam I just did a quick test with 0.0.7 and VS Code 0.8.4.
1, Now I'm not seeing any errors in A_ERR.  I can't do anything to show an indentation error.  Is there any new setting I need to turn on?

In Code for IBM i OUTPUT, when I open the member,  I still see A_ERR and A_OK being copied twice to the IFS.
However, when I switch between tabs I no longer see the source being copied to the IFS (as was happening before--see a., b., c. comments above).

Maybe it's late...

@worksofliam Also noticed today that I need to have RPGLE Language Tools installed to get content assist (%subst, etc) to work.

@SJLennon

Do you have the linter enabled in the VS Code settings?
Yes, the snippets were moved to this language extension from the base.

@worksofliam
Setting  "vscode-rpgle.rpgleLinterSupportEnabled":true, seems to be the trick.  Looks to be working fine now.
Sorry, I would not have expected that this would be considered part of lint, which was something that I planned to look at when it stabilized a bit more.

Yes, there were some issues with the linter when it was disabled and it still working.
What do you say the status of your issue is now?

@worksofliam
Didn't I see that on an indentation error it would offer a quick fix?  That seems to have gone.

@SJLennon thar actually was purposed removed for now (for some technical reasons, though I do miss it). Perhaps that'd be worth another issue!

I'll beat it around a bit tomorrow.

From: barry @.>
Sent: Thursday, December 2, 2021 9:00 PM
To: halcyon-tech/vscode-rpgle @.>
Cc: SJLennon @.>; Mention @.>
Subject: Re: [halcyon-tech/vscode-rpgle] rpgleIndentationEnabled Gone? (Issue #15)
Yes, there were some issues with the linter when it was disabled and it still working.
What do you say the status of your issue is now?
—
[https://ipmcdn.avast.com/images/icons/icon-envelope-tick-round-orange-animated-no-repeat-v1.gif]https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=icon    Virus-free. www.avast.comhttps://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail&utm_term=link

@worksofliam Looks like everything is good now.  Closing.


diagraph 0.2.5

I am submitting

[ ] a new package

[x] an update for a package

If the shape is point, the label isn't displayed

Now a minimum size is not enforced if the node label is empty

Added support for font alternatives

Thanks !


Split header by comma

When specifying array of enum strings in header,
it needs to be split according to commas.
Fixes #1278.
Changes proposed in this pull request:

When header is of type array, split the string by comma before validating

Coverage decreased (-0.03%) to 96.843% when pulling 9b0c42c50e8fcaf55ad84bbaf875b358d2b07d25 on ngoodman90:fix/split-array-header-by-comma into 8830d56841d29fe2ddce9d8507d60a27594cff30 on zalando:master.

Can you add a unit test?

@hjacobs added a test :)

:+1:


Can't load native library

It's throws a NullPointer at
https://github.com/hyperxpro/Brotli4j/blob/main/brotli4j/src/main/java/com/aayushatharva/brotli4j/Brotli4jLoader.java#L47.
The libPath is /lib/windows-x86_64/brotli.dll in debugger
Caused by the in is null and the Files#copy throw it.
    public static long copy(InputStream in, Path target, CopyOption... options)
        throws IOException
    {
        // ensure not null before opening file
        Objects.requireNonNull(in);

Tried adding natives as dependency.
I'm using Kotlin 1.5.21. OpenJDK <IP_ADDRESS>2-1.b10.
Windows 10 64bit

Which OS and Architecture?

Which OS and Architecture?

Edited

If you're using Gradle then you have to manually add the Windows native module.

Also, if possible, please share the code project to reproduce.

It's ok after add windows native manually. But the decompress status is ERROR. How can I debug?

Error status is generated due to invalid compressed data. Can you double check the compressed data?

Error status is generated due to invalid compressed data. Can you double check the compressed data?

Gotcha! Thanks!
I think we need a help for gradle in README. I try to write sth below. Haven't tested on other systems.
    val brotliVersion = "1.5.0"
    implementation("com.aayushatharva.brotli4j:brotli4j:$brotliVersion")
    val operatingSystem = DefaultNativePlatform.getCurrentOperatingSystem()
    if (operatingSystem.isWindows) {
        implementation("com.aayushatharva.brotli4j:native-windows-x86_64:$brotliVersion")
    } else if (operatingSystem.isMacOsX) {
        implementation("com.aayushatharva.brotli4j:native-osx-x86_64:$brotliVersion")
    } else if (operatingSystem.isLinux) {
        if (DefaultNativePlatform.getCurrentArchitecture().isArm) {
            implementation("com.aayushatharva.brotli4j:native-linux-aarch64:$brotliVersion")
        } else {
            implementation("com.aayushatharva.brotli4j:native-linux-x86_64:$brotliVersion")
        }
    }

Can you please do a PR for this?

Can you please do a PR for this?

Okay :D

@SettingDust Ping...

Pong...


Request for ptp sync

Hello,
I am using rgb stream of oak 1 with a external lidar. I want to sync them. Is it possible to sync oak1 using ptp? If no then what are the possible sync options?

Closing due to inactivity, if you think this should remain open, please tag me in a comment here.


Why not provide as_str?

There's a method to_string() in this crate to convert the hash into String, I suggest you also provide as_str() to convert the hash into &str.

This is a great question, which goes right to the heart of how references and lifetimes work in Rust. It turns out that Hash can't implement something like .as_str(), because it doesn't store hex characters internally. The .to_string() method creates an ArrayString and returns that by value, so in effect the hex characters wind up in the caller's stack memory. But a .as_str() method would need to return a reference that points somewhere, and the question becomes, where should it point? The only* way to make it work would be to have an ArrayString or similar contained inside the Hash itself, and to point back to that. But that would triple the size of Hash for all callers, which isn't a good trade.
* Technically we could create a Box<ArrayString> and then call Box::leak to make this work, but leaking memory every time you call .as_str() isn't what anybody wants :)


When rancher-compose is used to upgrade services that was created from UI , upgrade will be triggered even when no changes have been made.

Server version - v0.43.0-rc3
Rancher compose version - v0.5.0-rc2
Steps to reproduce the problem:
Create a service from UI.
Note that "io.rancher.service.hash" is not created for the service.
Try to use rancher-compose to upgrade the service without making any changes to the service configuration.
Upgrade will be triggered.
Expected Behavior is for upgrade to be not triggered in this case , since there has been no changes made to any configuration of the service.

Closing as there are users who want upgrades to be able to be triggered with no compose files.
https://github.com/rancher/rancher/issues/3571


HTML Reporter: Avoid readyState issue with PhantomJS

Closes #818

Looks good to me, as good as this kind of check can be.


Make project search more flexible

[ ] update project search to be case insensitive

search is case sensitive and precise. for ex, to find “Test #3”, that is the only thing i can type to find it. Things i tried that didn’t work:

test
test 3
3
test #3

@kittybest will this still be needed after #412 is merged/closed?


🐛 BUG: Possibly missing R2 Persist

What version of Wrangler are you using?
latest
What operating system are you using?
Mac
Describe the Bug
Might be wrong here, but I noticed the R2 update and from my limited understanding of the wrangler codebase,
https://github.com/cloudflare/wrangler2/blob/main/packages/wrangler/src/dev/local.tsx#L198
Shouldn't this include r2persist?

Thanks for reporting this @CraigglesO! It'll be part of our next release.


Wendy/eng 2530 new 2xs text size for 10px current 2xs text size should be

Adjusted text sizes - 2xs is now 0.6rem and 3xs is 0.5rem
Used new text size to make the SiChip on FuncList smaller
Cleaned up and compactified AssetFuncAttachDropdown and NewFuncDropdown
New compact style for DropdownMenu for menus that should have less padding
New FontSizes export from size_utils.ts to use when passing a text size as a prop
Fixes to prevent SidebarSubpanelTitles from changing size based on contents
Removed redundant unused Icons from icon_set.ts

bors merge


Make question text an html heading

In the "Answer Questions" area, the questions might be cumbersome to navigate via screen reader. Change the questions to headings.
From old pivotal ticket: https://www.pivotaltracker.com/story/show/131647527

This would be difficult to do due to the way Bootstrap uses heading tags to denote accordion sections. We should though set them as the labels for their corresponding text areas.

@briri - could you check whether this is done. we think so

I think so. The questions are at least labels now so screen readers should properly connect them to the appropriate answer field.


First draft/placeholder for design/structure docs

Content must go through a pre-merge checklist.
Pre-Merge Content Checklist
This documentation has been checked to ensure that:

[x] The title, template, and date` are all set
[x] Does this PR have a new menu item (anywhere in templates/*.hbs files) that points to a document .md that is set to publish in the future? If so please only publish the .md and .hbs changes in real-time (otherwise there will be a menu item pointing to a .md file that does not exist)
[x] File does not use CRLF, but uses plain LF (hint: use cat -ve <filename> | grep '^M' | wc -l and expect 0 as a result)
[x] Has passed bart check

[x] Has run npm run build-index
[x] Has been manually tested by running in Spin/Bartholomew (hint: use PREVIEW_MODE=1 and run npm run styles to update styling)

[x] Headings are using Title Case
[x] Code blocks have the programming language set to properly highlight syntax and the proper copy directive
[x] Have tested with npm run test and resolved all errors

Closes https://github.com/fermyon/developer/issues/586

Another suggestion: add this new page to the "Next Steps" on the Writing Applications page, e.g. "Discover how Spin application authors design and organise their applications"

Thank you for these last few inline suggestions @itowlson.


Optional signal not being considered when using nullable

If a property in Swagger is both nullable and optional, the generator skips the optional signal in the output TypeScript models.
Input:
User:
      type: object
      properties:
        defaultProject:
          type: string
          format: uuid
          nullable: true

Output:
export type User = {
  /**
   * @type string, uuid
   */
  defaultProject: string | null
}

Expected Output:
export type User = {
  /**
   * @type string, uuid
   */
  defaultProject?: string | null
}

Is this the intended behaviour?
Originally posted by @vitorcamachoo in https://github.com/kubb-labs/kubb/issues/930#issuecomment-2072972548

It has been fixed in 2.16.2


Enables easy use of local disks

Any benchmark that uses a scratch disk can now use a local disk by specifying --scratch_disk_type=local

test this please.

https://github.com/GoogleCloudPlatform/PerfKitBenchmarker/issues/243

Just reviewed for functionality vs correctness.  It still needs a review.

Do we need to specify where this local disk is? Does this mean there will be some network traffic between controller machine (where scratch disk is located) and vm instance?

"Local" disk here means local to the VM - most clouds have VM types that offer some kind of ephemeral storage (as opposed to a remote persistent store) bundled in with them - that's what this is.

@voellm PTAL - had some questions

LGTM. This has a few breaking changes that we need to be sure to publicize (ssd -> remote_ssd, dropped --use_local_disk). Maybe we should start a draft changelog for v0.16.0?

Sure - as soon as v.15 goes in I'll update the changelog for v.16


mq4 was compiled with ZeroMQ version 4.3.4, but the runtime links with version 4.3.5

Please describe your problem in detail, if necessary, you can upload the log file through the attachment:作者您好，我已将libzmq版本降级为4.3.4，ekuiperManager仍提示错误。请问如何解决。

What error message did you get?


[BugFix] Reset compaction_running to false if compaction failed

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

To fix the issue primary key table may have concurrent compaction, this pr (https://github.com/StarRocks/starrocks/pull/19692) only reset _compaction_running to false after apply. However, if compaction failed or return in advance, the compaction task don't execute apply which cause _compaction_running always be true, and it will refuse the following compaction.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto backported to target branch

[x] 3.0
[x] 2.5
[x] 2.4
[x] 2.3

@Mergifyio backport branch-3.0

@Mergifyio backport branch-2.5


Unicode Fullname 500

Gitea version (or commit ref): 1.12.5
Git version:    2.24.3
Operating system: Ubuntu - Docker image
Database (use [x]):

[ ] PostgreSQL
[x] MySQL
[ ] MSSQL
[ ] SQLite

Can you reproduce the bug at https://try.gitea.io:

[ ] Yes (provide example URL)
[ ] No
[x] Seems down? "Bad Gateway"

Log gist:

2020/10/22 11:15:13 ...r/setting/profile.go:105:ProfilePost() [E] UpdateUser: Error 1366: Incorrect string value: '\xF0\x9D\x96\x91\xF0\x9D...' for column 'full_name' at row 1

Description
Go to own profile, set "Full Name" to some Unicode Chars like 𝖑𝖚𝖑 and hit save.
500 internal server error
Priority
not important. Even not allowing Unicode at all would be fine ;)

This is yet another yet another MySQL utf8 - utf8mb4 issue.
You need to migrate your db, the tables and the columns to utf8mb4. You should ensure that CHARSET=utf8mb4 in the [database] section of the app.ini.


feat(material/form-field): add error harness

Add an error harness for client tests checking whether there are certain errors on the page. This is very common internally for tests checking validation.
The harness can be retrieved directly or through the form field.
I tried to check the right inheritance structure of other harnesses - might have gotten something mixed up on the way. Would appreciate a review making sure I've got the right inheritance of things. The harness tests passed so that's a good sign.

The existing form field harness has getTextErrors and hasErrors methods. Couldn't users depend on them instead? https://github.com/angular/components/blob/main/src/material/form-field/testing/form-field-harness.ts#L124

ohh, that makes it questionable if it should be a separate harness (like in this PR) or if we should encourage the existing methods. I didn't realize we have these- good point.

There's a lot of internal apps that use MatError without using the form field. Whether or not they should is maybe a good thing to discuss, but right now there's no way to get these folks using a test harness to check MatError.

I'm not sure if we would get much benefit out of switching those apps to harnesses since MatError basically hasn't changed since we introduced it. Maybe instead of migrating those apps, we can leave TODOs for them?

The benefit here is making sure there is consistency with guiding our users to use harnesses with our components. Otherwise we need to special-case "mat-error" in our lint rule, or in our docs, with some reason about why we wouldn't provide one for it.
It would have been better if we failed when mat-error was rendered outside a form field, but with about 500 HTML files in google3, I don't expect ever making that change. One could argue it's a useful directive for user's custom form fields.

Would it make sense to add this harness, but mark it as deprecated so people know to go through the form field one?

I'm in favor of deprecating it if we can get users off mat-error in their custom form fields, but that would be a bigger undertaking. I don't think just deprecating the harness is sufficient, you would need to deprecate the use of the mat-error by users outside the form field.
It's really just an element with display: block; color: warn, but people will take what they see https://www.hyrumslaw.com/

I'm fine going with this approach. Two things/questions:

Should we also have something for mat-hint?
Should we replace the existing methods to rely on the error/hint harnesses?

Yeah looks like mat-hint needs it to - There's about 120 HTML files using it outside form field
I think that makes sense - changed the current error APIs to use it in their implementation


[AutoPR monitor/resource-manager] fix documentation bug: max length of Group Short Name should be 12

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2841

(message created by the CI based on PR content)

This PR has been merged into https://github.com/Azure/azure-sdk-for-python/pull/2226


Elasticearch updates

Signed-off-by: Sophia Guo<EMAIL_ADDRESS>

Using nightly docker image for grinder. Tests failed at later stage.
20:34:16  JUnit4 test failed, ant output was:
20:34:16     [junit4] <JUnit4> says olá! Master seed: 4303BBF64C04856A
20:34:16     [junit4] JVM J0:     1.30 ..   261.08 =   259.77s
20:34:16     [junit4] JVM J1:     1.55 ..   264.43 =   262.89s
20:34:16     [junit4] JVM J2:     1.17 ..   261.52 =   260.34s
20:34:16     [junit4] Execution time total: 4 minutes 24 seconds
20:34:16     [junit4] Tests summary: 1017 suites (1 ignored), 6554 tests, 1 suite-level error, 80 ignored (80 assumptions)
20:34:16
20:34:16  :core:test FAILED
20:34:16
20:34:16  FAILURE: Build failed with an exception.
20:34:16
20:34:16  * What went wrong:
20:34:16  Execution failed for task ':core:test'.
20:34:16  > There were test failures: 1017 suites (1 ignored), 6554 tests, 1 suite-level error, 80 ignored (80 assumptions) [seed: 4303BBF64C04856A]
20:34:16

https://ci.adoptopenjdk.net/view/Test_grinder/job/Grinder/1278/console

Thanks @sophia-guo - I will raise an openj9 issue for the Elasticsearch failure.


failed to run the example on osx

tinygo build -target ./target.json -gc     leaking -o      cart.wasm ./snake
# runtime/interrupt
task: Failed to run task "run": exit status 1

tinygo version 0.31.0-dev-e19493b darwin/arm64 (using go version go1.22.0 and LLVM version 17.0.1)
Tested the amd64 version as well same error

Hmmm 🤔 That's not much of information to guess the error and I don't have an OS X device to reproduce. Let's leave it open and see if anyone else faces the same issue.
Also, the TinyGo issue tracker might be a better place for this bug report. Wasm4go doesn't do anything special, it's just a Go library. The error either in TinyGo internals or in my target.json configuration. I suggest you try compiling something very simple, like an empty program with a single empty main() {}, using the provided target.json and if the problem persists open an issue in TinyGo repo.


fix: handle squares properly in isSquareFree

The current implementation of isSquarefFree returns true for 9 = 3*3. This PR fixes that and adds missing tests and reorganizes them.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (4f6cd6c) 96.32% compared to head (5460d2f) 96.43%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #228      +/-   ##
==========================================
+ Coverage   96.32%   96.43%   +0.11%
==========================================
  Files          97       97
  Lines        1797     1797
  Branches      347      347
==========================================
+ Hits         1731     1733       +2
+ Misses         66       64       -2

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


Application crash when Mobile Linking (Android) using Version 4.0.0-pre.12

Using:
Unity 2021.3
unity-algorand-sdk Version 4.0.0-pre.12
Tried to use mobile linking to Pera Wallet on an Android Phone. Application crashed after I approve the session.

Talk to Algorand  Support on the Algorand Live Support so that your issue can be looked into.

My bad, I got it to work now after changing a few Player settings.
Scripting Backend: Mono -> IL2CPP
Api Compatibility Level: .NET Standard 2.1 -> .NET Framework
Target Architecture: ARMv7 -> ARM64


After upgrading to 5.4.1 when explicitly mapping a struct type the mapping it not used for the nullable version

In 4.x if you explicitly specified a mapping for a struct type it would also be used for the nullable version of the struct. In 5.4.1 you have to explicitly map the nullable version as well. Is this change intentional?
In our API we use NodaTime.Serialization.JsonNet.Extensions.ConfigureForNodaTime to add support for (de)serializing NodaTime types (like Instant) in DTOs. For example Instant is serialized to a String like 2013-07-26T16:45:20.1234567Z. Because of this we need to explicitly map these types in Swashbuckle so that it knows about this as well:
swaggerGenOptions.MapType(
    typeof(Instant),
    () => new OpenApiSchema {
        Type = "string"
    });

And here's an example DTO:
public class TestDto {
        public Instant instant;
        public Instant? nullableInstant;
}

In 4.x they would both be mapped as a string in swagger.json but in 5.x only the non-nullable one is:
"instant": {
  "type": "string"
},
"nullableInstant": {
  "nullable": true
}

Adding a mapping for Instant? works as expected.
Was this change intentional?

I just hit this problem as well. It's probably easy to fix, I'll try to send a PR.

Yes - this change was intentional, and to that point probably should be mentioned as a breaking change in the 5.0.0 release notes (I will update this). The purpose of MapType is to support custom C# Type to Schema mappings. As Nullable<T> and T are different types, they're should be separate mappings for each.

I found the old behavior much more intuitive. If nothing else maybe there could be an extension method or option to automatically map nullable structs as well?
In case it's helpful to future readers this is how we're mapping the nullable versions without having to explicitly specify them:
// Based on the list of serializable types from https://nodatime.org/1.2.x/userguide/serialization
var nodaTimeTypesSerializedAsString = new [] {
    typeof(Instant),
    typeof(OffsetDateTime),
    typeof(ZonedDateTime),
    typeof(LocalDateTime),
    typeof(LocalDate),
    typeof(LocalTime),
    typeof(Offset),
    typeof(Interval),
    typeof(Duration),
};

// As of version 5.x the nullable versions of types need to be explicitly specified too.
// https://github.com/domaindrivendev/Swashbuckle.AspNetCore/issues/1648
nodaTimeTypesSerializedAsString = nodaTimeTypesSerializedAsString
    .Concat(nodaTimeTypesSerializedAsString.Select(x => typeof(Nullable<>).MakeGenericType(x)))
    .ToArray();

foreach (var type in nodaTimeTypesSerializedAsString) {
    // https://github.com/domaindrivendev/Swashbuckle.AspNetCore/blob/master/README.md#override-schema-for-specific-types
    swaggerGenOptions.MapType(
        type,
        () => new OpenApiSchema {
            Type = "string"
        });
}

Yes - this change was intentional, and to that point probably should be mentioned as a breaking change in the 5.0.0 release notes (I will update this). The purpose of MapType is to support custom C# Type to Schema mappings. As Nullable<T> and T are different types, I felt it more appropriate to require separate mappings for each.

This behaviour conflicts with #1551 (support for open generics in MapType()): due to this change I cannot register a type map for Nullable<MyOpenGeneric<>>, as the language will not allow open generics to be nested in this way. The behaviour described by @thomaslevesque would definitely be preferred.

Yes - this change was intentional, and to that point probably should be mentioned as a breaking change in the 5.0.0 release notes (I will update this). The purpose of MapType is to support custom C# Type to Schema mappings. As Nullable<T> and T are different types, I felt it more appropriate to require separate mappings for each.

This behaviour conflicts with #1551 (support for open generics in MapType()): due to this change I cannot register a type map for Nullable<MyOpenGeneric<>>, as the language will not allow open generics to be nested in this way. The behaviour described by @thomaslevesque would definitely be preferred.

Any update on this? It's been over a year and we're still blocked on upgrading due to it.

Any update on this? It's been over a year and we're still blocked on upgrading due to this issue. Thanks.

Closing as this was answered as being an intentional change.


Fix commitment lengths for side-loaded verification keys

This error was introduced in df12992198627f0f115a617dd4197ee5322d6d93, where the generic version was updated correctly to use h everywhere, but the generic' version incorrectly used n instead of h. Since we weren't using side-loaded keys anywhere at the time, this was also missed during testing.
NOTE: This is deliberately against develop rather than compatible, because this change will cause snark keys to change!
Checklist:

[ ] Modified the current draft of release notes with details on what is completed or incomplete within this project
[ ] Document code purpose, how to use it

Mention expected invariants, implicit constraints

[ ] Tests were added for the new behavior

Document test purpose, significance of failures
Test names should reflect their purpose

[ ] All tests pass (CI will check this if you didn't)
[ ] Serialized types are in stable-versioned modules
[ ] Does this close issues? List them

Seeing verification failure in gossip consistency integration tests

bad verify: dlog_check\ncombined_inner_product: 0xfe0b4669da7a5589f9c7ba2f9efa80f02718b397156aa59c007e1f2af989b938 != 0x73e0d0d9b58f5b6b1080453a48ebcae5aff0b7436804f6684bae6f3bc1598d2c\nxi: 0xbb2cda42e5edbcf6717e964b1c84c999ade9c7d5f3f2e9bd57e15a5fae461b2d != 0xa1ea6a27dc9f0d5236758c5ea22567225a4f2f3f734d835cfbb21422d0598105\nlinearization_check\nbad verify: dlog_check\ncombined_inner_product: 0xfe0b4669da7a5589f9c7ba2f9efa80f02718b397156aa59c007e1f2af989b938 != 0x73e0d0d9b58f5b6b1080453a48ebcae5aff0b7436804f6684bae6f3bc1598d2c\nxi: 0xbb2cda42e5edbcf6717e964b1c84c999ade9c7d5f3f2e9bd57e15a5fae461b2d != 0xa1ea6a27dc9f0d5236758c5ea22567225a4f2f3f734d835cfbb21422d0598105\nlinearization_check\nbad verify: dlog_check\ncombined_inner_product: 0xfe0b4669da7a5589f9c7ba2f9efa80f02718b397156aa59c007e1f2af989b938 != 0x73e0d0d9b58f5b6b1080453a48ebcae5aff0b7436804f6684bae6f3bc1598d2c\nxi: 0xbb2cda42e5edbcf6717e964b1c84c999ade9c7d5f3f2e9bd57e15a5fae461b2d != 0xa1ea6a27dc9f0d5236758c5ea22567225a4f2f3f734d835cfbb21422d0598105\nlinearization_check

Seeing verification failure in gossip consistency integration tests

Spent a while looking into this, but it turns out it's not a fatal issue, and appears to be unrelated. For example, you can see the same in the gossip consistency test logs for the unrelated PR #9759.

Compatibility checks are failing, but they should be optional on develop. Merging.


[r] A bit more dev advice for R

Helpful things from helpful conversations with @eddelbuettel over the last few days

Codecov Report
Patch coverage has no change and project coverage change: -18.75 :warning:

Comparison is base (2225c6b) 60.76% compared to head (a25e779) 42.01%.

:exclamation: Current head a25e779 differs from pull request most recent head 3bdff83. Consider uploading reports for the commit 3bdff83 to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
Additional details and impacted files
@@             Coverage Diff             @@
##             main    #1080       +/-   ##
===========================================
- Coverage   60.76%   42.01%   -18.75%
===========================================
  Files          81       51       -30
  Lines        5872     3613     -2259
===========================================
- Hits         3568     1518     -2050
+ Misses       2304     2095      -209

Flag
Coverage Δ

python
?

r
42.01% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 30 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


data: add extra id for g602

Plugging in both of my Logitech G602's (one bought a few years back, one bought yesterday, both bought in Canada) gives:
λ › sudo ratbagd --verbose
Initializing libratbag
ratbag debug: New device: Logitech USB Receiver
ratbag debug: Using data directory '/usr/share/libratbag'
ratbag debug: No data file found for 046d:c537
ratbag debug: New device: Logitech USB Receiver
ratbag debug: Using data directory '/usr/share/libratbag'
ratbag debug: No data file found for 046d:c537

Is master currently failing to build?
It looks like the build failure is unrelated to my change.

That is the ID of the receiver, not the device. The kernel driver should export a hidraw node with the ID of the device. If it isn't working, please update your kernel.


Installation issues

First of all, thanks a lot for providing this library which seems quite sophisticated according to the related videos.
Unfortunately, I run into issues when installing rai-python on Ubuntu 18.04.
This is what I did.
First, I installed OpenCV, Bullet and PhysX from source according to:
https://github.com/MarcToussaint/rai-maintenance/blob/master/help/localSourceInstalls.md
The rai-python installation failed related to ceres-solver, so in addition, I installed GLOG from source according to:
https://github.com/google/glog#building-glog-with-cmake
The output of the sudo make install is:
[sudo] password for ndehio:
[ 36%] Built target glog
[ 45%] Built target signalhandler_unittest
[ 54%] Built target stl_logging_unittest
[ 63%] Built target stacktrace_unittest
[ 72%] Built target demangle_unittest
[ 81%] Built target logging_unittest
[ 90%] Built target symbolize_unittest
[100%] Built target utilities_unittest
Install the project...
-- Install configuration: ""
-- Installing: /usr/local/lib/libglog.a
-- Installing: /usr/local/include/glog/logging.h
-- Installing: /usr/local/include/glog/raw_logging.h
-- Installing: /usr/local/include/glog/stl_logging.h
-- Installing: /usr/local/include/glog/vlog_is_on.h
-- Installing: /usr/local/include/glog/log_severity.h
-- Installing: /usr/local/lib/pkgconfig/libglog.pc
-- Installing: /usr/local/lib/cmake/glog/glog-modules.cmake
-- Installing: /usr/local/lib/cmake/glog/glog-config.cmake
-- Installing: /usr/local/lib/cmake/glog/glog-config-version.cmake
-- Installing: /usr/local/lib/cmake/glog/glog-targets.cmake
-- Installing: /usr/local/lib/cmake/glog/glog-targets-noconfig.cmake

Next, I installed Ceres-Solver from source according to:
http://ceres-solver.org/installation.html
Then, I downloaded rai-python again, set ROS_VERSION = melodic in config.mk and followed the installation instructions.
Unfortunately, make still fails.
g++: error: /usr/lib/x86_64-linux-gnu/libgflags.so.2.2.1: No such file or directory
g++: error: /usr/lib/x86_64-linux-gnu/libglog.so: No such file or directory

The ceres-solver website mentions an issue related to gflag. Do I need to take care of this?
Or should I install gflags, glog and ceres like this?
sudo apt-get install libgflags-dev
sudo apt-get install libgoogle-glog-dev
sudo apt-get install libceres-dev

I also encountered similar problems for
https://github.com/MarcToussaint/20-IROS-ForceBased
and
https://github.com/MarcToussaint/18-RSS-PhysicalManipulation

Thank you Marc for your quick fix in the 18-RSS-PhysicalManipulation repo.
I solved all my installation issues via
sudo apt-get install libnlopt-dev
sudo apt-get install libgflags-dev
sudo apt-get install libgoogle-glog-dev
sudo apt-get install libceres-dev

For some reason, these dependencies were not automatically installed via make -j1 installUbuntuAll.
And finally, when including Bullet in the config.mk I had to compile rai-python via make -j4 -I/usr/local/include.
Note, in some of the python-scripts I had to replace sys.path.append('../build') by sys.path.append('../rai/lib').
Similarly, I replaced C.addFile('../test/boxProblem.g') by C.addFile('../test/retired/boxProblem.g').
Thanks again. From my side, we can close this issue.
Niels


http post with esp32

Hello
i want to communicate with esp32 over the wifi using dart language.
i want to send a message from flutter that should receive by esp 32 and vice versa

I will just paste your SO question here in case somebody will help there earlier.

I will just paste your SO question here in case somebody will help there earlier.

no sir no one helped me over there

Please ask questions like this on stackoverflow as we can't give individual support here.

This is a flutter related issue
On 01-Oct-2019 8:32 PM, "escamoteur"<EMAIL_ADDRESS>wrote:

Closed #41684 https://github.com/flutter/flutter/issues/41684.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/flutter/flutter/issues/41684?email_source=notifications&email_token=ANHYMXHY6LVWKDF7BMRAETTQMNUSDA5CNFSM4I4ICKTKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOT6LYO2A#event-2677507944,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ANHYMXH23ULFKDP7FLXFAADQMNUSDANCNFSM4I4ICKTA
.

Hi,
no this is not a Flutter related problem but standard network programming with the Dart HttpClient, http package or dio package.
This place is for reporting bugs and suggest new features


Enhancing installation advices

Please confirm PR!

Review changes are solved, please confirm after you are back in office.

oh, you need now to ensure 'tox -e pep8' succeeds on the branch (multiple lines are too long)

Hi,
yes, I already saw this issue. I was currently finding out how to solve this in a better way then before.
Von: Artem Goncharov<EMAIL_ADDRESS>Gesendet: Mittwoch, 28. August 2019 11:42
An: OpenTelekomCloud/python-otcextensions<EMAIL_ADDRESS>Cc: Schreiber, Tino<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Betreff: Re: [OpenTelekomCloud/python-otcextensions] Enhancing installation advices (#37)
oh, you need now to ensure 'tox -e pep8' succeeds on the branch (multiple lines are too long)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/OpenTelekomCloud/python-otcextensions/pull/37?email_source=notifications&email_token=AGKX4PQJBXDVHXIRYYJXL2TQGZB77A5CNFSM4HZWBIOKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD5KQXHA#issuecomment-525667228, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGKX4PU227476CEQ6WKGSGTQGZB77ANCNFSM4HZWBIOA.

Changes have been done. Was not aware of the linting check. Now, it works properly. Please confirm :+1:


Does Rasa Data Validate not check Rules.yml/Stories.yml?

Rasa version:
Rasa Version     : 2.2.6
Rasa SDK Version : 2.2.0
Rasa X Version   : 0.35.0
Python Version   : 3.7.7
Operating System : Darwin-19.3.0-x86_64-i386-64bit
Python Path      : /Users/vincent/Development/name-form-demo/venv/bin/python3.7

Issue:
It seems that not everything is caught with rasa data validate. In particular, are we sure it is checking rules.yml files? I took a rasa init project and added this rule.
- rule: Ask Name Again
  condition:
    - active_loop: name_form
  steps:
    - slot_was_set:
      - requested_slot: name
    - action: action_check_name_spelling
    - intent: deny
    - action: action_clear_name_slot
    - active_loop: name_form

Running rasa data validate does not give an error if "action_clear_name_slot" and "action_check_name_spelling" are missing from domain.yml. But rasa train does!
> rasa train
/Users/vincent/Development/name-form-demo/venv/lib/python3.7/site-packages/rasa/shared/core/slots.py:268: FutureWarning: UnfeaturizedSlot is deprecated and will be removed in Rasa Open Source 3.0. Please change the type and configure the 'influence_conversation' flag for slot 'requested_slot' instead.
  category=FutureWarning,
2021-01-25 15:27:15 INFO     rasa.shared.utils.validation  - The 'version' key is missing in the training data file /Users/vincent/Development/name-form-demo/data/namelist.yml. Rasa Open Source will read the file as a version '2.0' file. See https://rasa.com/docs/rasa/training-data-format.
2021-01-25 15:27:16 INFO     rasa.model  - Data (domain) for Core model section changed.
2021-01-25 15:27:16 INFO     rasa.model  - Data (messages) for NLU model section changed.
2021-01-25 15:27:16 INFO     rasa.model  - Data (domain) for Core model section changed.
2021-01-25 15:27:16 INFO     rasa.model  - Data (messages) for NLU model section changed.
Training NLU model...
2021-01-25 15:27:17 INFO     rasa.shared.nlu.training_data.training_data  - Training data stats:
2021-01-25 15:27:17 INFO     rasa.shared.nlu.training_data.training_data  - Number of intent examples: 76 (8 distinct intents)

2021-01-25 15:27:17 INFO     rasa.shared.nlu.training_data.training_data  -   Found intents: 'request_name', 'affirm', 'deny', 'mood_great', 'bot_challenge', 'mood_unhappy', 'greet', 'goodbye'
2021-01-25 15:27:17 INFO     rasa.shared.nlu.training_data.training_data  - Number of response examples: 0 (0 distinct responses)
2021-01-25 15:27:17 INFO     rasa.shared.nlu.training_data.training_data  - Number of entity examples: 0 (0 distinct entities)
2021-01-25 15:27:17 INFO     rasa.nlu.model  - Starting to train component WhitespaceTokenizer
2021-01-25 15:27:17 INFO     rasa.nlu.model  - Finished training component.
2021-01-25 15:27:17 INFO     rasa.nlu.model  - Starting to train component RegexFeaturizer
2021-01-25 15:27:18 INFO     rasa.nlu.model  - Finished training component.
2021-01-25 15:27:18 INFO     rasa.nlu.model  - Starting to train component LexicalSyntacticFeaturizer
2021-01-25 15:27:18 INFO     rasa.nlu.model  - Finished training component.
2021-01-25 15:27:18 INFO     rasa.nlu.model  - Starting to train component CountVectorsFeaturizer
2021-01-25 15:27:18 INFO     rasa.nlu.featurizers.sparse_featurizer.count_vectors_featurizer  - 89 vocabulary slots consumed out of 1089 slots configured for text attribute.
2021-01-25 15:27:18 INFO     rasa.nlu.model  - Finished training component.
2021-01-25 15:27:18 INFO     rasa.nlu.model  - Starting to train component CountVectorsFeaturizer
2021-01-25 15:27:18 INFO     rasa.nlu.featurizers.sparse_featurizer.count_vectors_featurizer  - 773 vocabulary slots consumed out of 1773 slots configured for text attribute.
2021-01-25 15:27:18 INFO     rasa.nlu.model  - Finished training component.
2021-01-25 15:27:18 INFO     rasa.nlu.model  - Starting to train component DIETClassifier
Epochs:   0%|                                                                  | 0/100 [00:00<?, ?it/s]/Users/vincent/Development/name-form-demo/venv/lib/python3.7/site-packages/rasa/utils/tensorflow/model_data.py:861: VisibleDeprecationWarning: Creating an ndarray from ragged nested sequences (which is a list-or-tuple of lists-or-tuples-or ndarrays with different lengths or shapes) is deprecated. If you meant to do this, you must specify 'dtype=object' when creating the ndarray
  np.concatenate(np.array(f)),
Epochs: 100%|█████████████████████████████| 100/100 [00:14<00:00,  6.70it/s, t_loss=1.549, i_acc=1.000]
2021-01-25 15:27:42 INFO     rasa.utils.tensorflow.models  - Finished training.
2021-01-25 15:27:42 INFO     rasa.nlu.model  - Finished training component.
2021-01-25 15:27:42 INFO     rasa.nlu.model  - Starting to train component EntitySynonymMapper
2021-01-25 15:27:42 INFO     rasa.nlu.model  - Finished training component.
2021-01-25 15:27:42 INFO     rasa.nlu.model  - Starting to train component ResponseSelector
2021-01-25 15:27:42 INFO     rasa.nlu.selectors.response_selector  - Retrieval intent parameter was left to its default value. This response selector will be trained on training examples combining all retrieval intents.
2021-01-25 15:27:42 INFO     rasa.nlu.model  - Finished training component.
2021-01-25 15:27:43 INFO     rasa.nlu.model  - Successfully saved model into '/var/folders/0v/pj9vtxhd6ml7mb8n94wvcmkr0000gp/T/tmpwkq92n8d/nlu'
NLU model training completed.
Training Core model...
Processed story blocks: 100%|████████████████████████████| 3/3 [00:00<00:00, 1631.18it/s, # trackers=1]
Processed story blocks: 100%|█████████████████████████████| 3/3 [00:00<00:00, 584.44it/s, # trackers=3]
Processed story blocks: 100%|████████████████████████████| 3/3 [00:00<00:00, 156.46it/s, # trackers=12]
Processed story blocks: 100%|█████████████████████████████| 3/3 [00:00<00:00, 34.63it/s, # trackers=39]
Processed rules: 100%|███████████████████████████████████| 7/7 [00:00<00:00, 2455.07it/s, # trackers=1]
Processed trackers: 100%|█████████████████████████████████| 3/3 [00:00<00:00, 802.58it/s, # actions=12]
Processed actions: 12it [00:00, 941.83it/s, # examples=12]
Processed trackers: 100%|█████████████████████████████| 120/120 [00:00<00:00, 228.45it/s, # actions=30]
/Users/vincent/Development/name-form-demo/venv/lib/python3.7/site-packages/rasa/utils/tensorflow/model_data_utils.py:338: VisibleDeprecationWarning: Creating an ndarray from ragged nested sequences (which is a list-or-tuple of lists-or-tuples-or ndarrays with different lengths or shapes) is deprecated. If you meant to do this, you must specify 'dtype=object' when creating the ndarray
  np.array(values), number_of_dimensions=4
Epochs: 100%|█████████████████| 100/100 [00:06<00:00, 14.34it/s, t_loss=13.794, loss=13.622, acc=0.967]
2021-01-25 15:28:01 INFO     rasa.utils.tensorflow.models  - Finished training.
Processed trackers: 100%|████████████████████████████████| 7/7 [00:00<00:00, 1109.19it/s, # actions=16]
Processed actions: 16it [00:00, 11947.46it/s, # examples=13]
Processed trackers: 100%|█████████████████████████████████| 3/3 [00:00<00:00, 197.35it/s, # actions=12]
Processed trackers:  14%|██████▋                                        | 1/7 [00:00<00:00, 491.65it/s]
ActionNotFoundException: Cannot access action 'action_clear_name_slot', as that name is not a registered action for this domain. Available actions are:
         - action_listen
         - action_restart
         - action_session_start
         - action_default_fallback
         - action_deactivate_loop
         - action_revert_fallback_events
         - action_default_ask_affirmation
         - action_default_ask_rephrase
         - action_two_stage_fallback
         - action_back
         - ...
         - utter_greet
         - utter_slots_values
         - utter_submit
         - utter_ask_name
         - utter_cheer_up
         - utter_did_that_help
         - utter_goodbye
         - utter_happy
         - utter_iamabot
         - name_form

The annoying thing here is that the time-consuming training procedure needs to run before the error appears on my retina. It'd be nice if rasa data validate can catch this because it might prevent costly training procedures.

I also just confirmed that there is a similar situation when working with custom actions. You can have custom actions in your NLU file with them appearing in the domain.yml file. Running rasa data validate won't trigger an error but running rasa train will prompt one at the end of the training procedure.

I also just confirmed that there is a similar situation when working with custom actions. You can have custom actions in your NLU file with them appearing in the domain.yml file. Running rasa data validate won't trigger an error but running rasa train will prompt one at the end of the training procedure.

It also seems that rasa data validate is completely fine with the following contents in domain.yml.
forms:
  name_form:
    first_name:
      - type: from_text
    last_name:
      - type: from_text

slots:
  first_name:
    type: text
  last_nam:
    type: text

Note that last_nam at the end there is misspelled. So a form can refer to a slot that does not exist.

It also seems that rasa data validate is completely fine with the following contents in domain.yml.
forms:
  name_form:
    first_name:
      - type: from_text
    last_name:
      - type: from_text

slots:
  first_name:
    type: text
  last_nam:
    type: text

Note that last_nam at the end there is misspelled. So a form can refer to a slot that does not exist.

Just ran into this issue as well -- I've also had to write my own custom validator since it doesn't support the MultiProjectImporter.
Seems strange to me that the rule validation runs after a core model is trained, and wasn't included in the data validation script.

It also seems like rasa data validate does not check if the actions in the stories appear in the domain.yml file.
> rasa data validate
The configuration for pipeline and policies was chosen automatically. It was written into the config file at 'config.yml'.
2021-04-07 15:54:59 INFO     rasa.validator  - Validating intents...
2021-04-07 15:54:59 INFO     rasa.validator  - Validating uniqueness of intents and stories...
2021-04-07 15:54:59 INFO     rasa.validator  - Validating utterances...
2021-04-07 15:54:59 INFO     rasa.validator  - Story structure validation...
Processed story blocks: 100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 3/3 [00:00<00:00, 1190.89it/s, # trackers=1]
2021-04-07 15:54:59 INFO     rasa.core.training.story_conflict  - Considering all preceding turns for conflict analysis.
/Users/vincent/Development/how-to-rasa/venv/lib/python3.6/site-packages/rasa/utils/train_utils.py:535: UserWarning: model_confidence is set to `softmax`. It is recommended to try using `model_confidence=linear_norm` to make it easier to tune fallback thresholds.
  category=UserWarning,
2021-04-07 15:54:59 INFO     rasa.validator  - No story structure conflicts found.

> rasa train
The configuration for policies and pipeline was chosen automatically. It was written into the config file at 'config.yml'.
Training NLU model...
/Users/vincent/Development/how-to-rasa/venv/lib/python3.6/site-packages/rasa/utils/train_utils.py:535: UserWarning: model_confidence is set to `softmax`. It is recommended to try using `model_confidence=linear_norm` to make it easier to tune fallback thresholds.
  category=UserWarning,
2021-04-07 15:55:13 INFO     rasa.shared.nlu.training_data.training_data  - Training data stats:
2021-04-07 15:55:13 INFO     rasa.shared.nlu.training_data.training_data  - Number of intent examples: 81 (12 distinct intents)

2021-04-07 15:55:13 INFO     rasa.shared.nlu.training_data.training_data  -   Found intents: 'deny', 'affirm', 'mood_unhappy', 'mood_great', 'bot_challenge', 'request_fancy_form', 'buy_pizza', 'inform', 'request_pizza_form', 'goodbye', 'buy_fancy_pizza', 'greet'
2021-04-07 15:55:13 INFO     rasa.shared.nlu.training_data.training_data  - Number of response examples: 0 (0 distinct responses)
2021-04-07 15:55:13 INFO     rasa.shared.nlu.training_data.training_data  - Number of entity examples: 5 (2 distinct entities)
2021-04-07 15:55:13 INFO     rasa.shared.nlu.training_data.training_data  -   Found entity types: 'pizza_size', 'pizza_type'
/Users/vincent/Development/how-to-rasa/venv/lib/python3.6/site-packages/rasa/shared/utils/io.py:96: UserWarning: Intent 'request_fancy_form' has only 1 training examples! Minimum is 2, training may fail.
/Users/vincent/Development/how-to-rasa/venv/lib/python3.6/site-packages/rasa/shared/utils/io.py:96: UserWarning: Intent 'request_pizza_form' has only 1 training examples! Minimum is 2, training may fail.
/Users/vincent/Development/how-to-rasa/venv/lib/python3.6/site-packages/rasa/shared/utils/io.py:96: UserWarning: Entity entity 'pizza_type' has only 1 training examples! The minimum is 2, because of this the training may fail.
2021-04-07 15:55:13 INFO     rasa.nlu.model  - Starting to train component WhitespaceTokenizer
2021-04-07 15:55:13 INFO     rasa.nlu.model  - Finished training component.
2021-04-07 15:55:13 INFO     rasa.nlu.model  - Starting to train component RegexFeaturizer
2021-04-07 15:55:13 INFO     rasa.nlu.model  - Finished training component.
2021-04-07 15:55:13 INFO     rasa.nlu.model  - Starting to train component LexicalSyntacticFeaturizer
2021-04-07 15:55:13 INFO     rasa.nlu.model  - Finished training component.
2021-04-07 15:55:13 INFO     rasa.nlu.model  - Starting to train component CountVectorsFeaturizer
2021-04-07 15:55:13 INFO     rasa.nlu.featurizers.sparse_featurizer.count_vectors_featurizer  - 99 vocabulary slots consumed out of 1099 slots configured for text attribute.
2021-04-07 15:55:13 INFO     rasa.nlu.model  - Finished training component.
2021-04-07 15:55:13 INFO     rasa.nlu.model  - Starting to train component CountVectorsFeaturizer
2021-04-07 15:55:13 INFO     rasa.nlu.featurizers.sparse_featurizer.count_vectors_featurizer  - 862 vocabulary slots consumed out of 1862 slots configured for text attribute.
2021-04-07 15:55:13 INFO     rasa.nlu.model  - Finished training component.
2021-04-07 15:55:13 INFO     rasa.nlu.model  - Starting to train component DIETClassifier
Epochs: 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 100/100 [00:27<00:00,  3.66it/s, t_loss=1.76, i_acc=1, e_f1=1]
2021-04-07 15:55:41 INFO     rasa.nlu.model  - Finished training component.
2021-04-07 15:55:41 INFO     rasa.nlu.model  - Starting to train component EntitySynonymMapper
2021-04-07 15:55:41 INFO     rasa.nlu.model  - Finished training component.
2021-04-07 15:55:41 INFO     rasa.nlu.model  - Starting to train component ResponseSelector
2021-04-07 15:55:41 INFO     rasa.nlu.selectors.response_selector  - Retrieval intent parameter was left to its default value. This response selector will be trained on training examples combining all retrieval intents.
2021-04-07 15:55:41 INFO     rasa.nlu.model  - Finished training component.
2021-04-07 15:55:41 INFO     rasa.nlu.model  - Starting to train component FallbackClassifier
2021-04-07 15:55:41 INFO     rasa.nlu.model  - Finished training component.
2021-04-07 15:55:41 INFO     rasa.nlu.model  - Successfully saved model into '/var/folders/0v/pj9vtxhd6ml7mb8n94wvcmkr0000gp/T/tmpg1uzv3nl/nlu'
NLU model training completed.
Training Core model...
Processed story blocks: 100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 3/3 [00:00<00:00, 1224.50it/s, # trackers=1]
Processed story blocks: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 3/3 [00:00<00:00, 490.35it/s, # trackers=3]
Processed story blocks: 100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 3/3 [00:00<00:00, 111.92it/s, # trackers=12]
Processed story blocks: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 3/3 [00:00<00:00, 28.13it/s, # trackers=39]
Processed rules: 100%|█████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 6/6 [00:00<00:00, 1742.66it/s, # trackers=1]
Processed trackers: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 3/3 [00:00<00:00, 622.27it/s, # actions=12]
Processed actions: 12it [00:00, 3372.76it/s, # examples=12]
Processed trackers: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 120/120 [00:00<00:00, 172.97it/s, # actions=30]
Epochs: 100%|████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 100/100 [00:10<00:00,  9.61it/s, t_loss=2.08, loss=1.9, acc=1]
Processed trackers: 100%|██████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 6/6 [00:00<00:00, 1180.66it/s, # actions=17]
Processed actions: 17it [00:00, 12599.96it/s, # examples=14]
Processed trackers: 100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 3/3 [00:00<00:00, 587.88it/s, # actions=12]
Processed trackers:  17%|████████████████████████▊                                                                                | 1/6 [00:00<00:00, 564.66it/s]
ActionNotFoundException: Cannot access action 'pizza_form', as that name is not a registered action for this domain. Available actions are:
         - action_listen
         - action_restart
         - action_session_start
         - action_default_fallback
         - action_deactivate_loop
         - action_revert_fallback_events
         - action_default_ask_affirmation
         - action_default_ask_rephrase
         - action_two_stage_fallback
         - action_back
         - ...
         - utter_cheer_up
         - utter_did_that_help
         - utter_goodbye
         - utter_greet
         - utter_happy
         - utter_iamabot
         - utter_pizza_slots
         - utter_submit
         - simple_pizza_form
         - fancy_pizza_form

So I guess what's "todo" in this issue is:

[ ] validation of action usage in rules.yml and stories.yml against domain actions
[ ] support for MultiProjectImporter by using the TrainingDataImporter interface
[ ] validate slot usage in forms registered in domain, should fail if trying to collect a slot that doesn't exist in domain.yml

@koaning does that encompass what's going on here?

There may be more, I'm mostly just making sure that I collected errors here.

Related: https://github.com/RasaHQ/rasa/issues/7691

I also just confirmed that there is a similar situation when working with custom actions. You can have custom actions in your NLU file with them appearing in the domain.yml file. Running rasa data validate won't trigger an error but running rasa train will prompt one at the end of the training procedure.

Hi @koaning could you please share the NLU file, domain.yml and the error that gets shown running rasa train - I'm not sure I understand the issue you described in this particular comment.

I'm using the same data that you get when you run rasa init. I make a small change to rules.yml, here's what it looks like.
version: "2.0"

rules:

- rule: Say goodbye anytime the user says goodbye
  steps:
  - intent: goodbye
  - action: utter_goodbye

- rule: Say 'I am a bot' anytime the user challenges
  steps:
  - intent: bot_challenge
  - action: utter_iamabot

- rule: Ask Name Again
  condition:
    - active_loop: name_form
  steps:
    - slot_was_set:
      - requested_slot: name
    - action: action_check_name_spelling
    - intent: deny
    - action: action_clear_name_slot
    - active_loop: name_form

The nlu.yml is kept exactly the same.

nlu.yml.
```yaml
version: "2.0"
nlu:

intent: greet
examples: |

hey
hello
hi
hello there
good morning
good evening
moin
hey there
let's go
hey dude
goodmorning
goodevening
good afternoon

intent: goodbye
examples: |

good afternoon
cu
good by
cee you later
good night
bye
goodbye
have a nice day
see you around
bye bye
see you later

intent: affirm
examples: |

yes
y
indeed
of course
that sounds good
correct

intent: deny
examples: |

no
n
never
I don't think so
don't like that
no way
not really

intent: mood_great
examples: |

perfect
great
amazing
feeling like a king
wonderful
I am feeling very good
I am great
I am amazing
I am going to save the world
super stoked
extremely good
so so perfect
so good
so perfect

intent: mood_unhappy
examples: |

my day was horrible
I am sad
I don't feel very well
I am disappointed
super sad
I'm so sad
sad
very sad
unhappy
not good
not very good
extremly sad
so saad
so sad

intent: bot_challenge
examples: |

are you a bot?
are you a human?
am I talking to a bot?
am I talking to a human?

</details>

If I run `rasa data validate` I get no complaints. However, there are rules referring to an action/form that does not exist. I'd expect the validation to trigger an error here. The unfortunate result is that now I need to wait until after `rasa train` is done training that something went wrong.

Speaking about rasa data validate:

rasa train doesn't actually do anything, it just fails in the case of issues during training so the this issue might be a bit more complicated than just "add missing checks from rasa train to rasa data validate"
Another problem is that rasa train iterates through the policies and calls the train method of a specific policy and only after doing predictions and going though a couple of calls within the policy throws exceptions like ActionNotFoundException: Cannot access action 'action_clear_name_slot', as that name is not a registered action for this domain.
rasa data validate doesn't do this — it doesn't use policies, doesn't iterate through them, doesn't do any action prediction => it's definitely not easy to use the same mechanism to check if actions are missing from the domain. So ideally another mechanism should be used.

However, we plan to change the training process in Rasa 3.0 and separate training and processing. It might be that going through actions and checking if actions are part of the domain would become part of the processing step, and this step might become reusable for data validation. If it's the case (requires some more investigation though) then it's better to skip this issue for now and wait for another implementation of training+processing steps.

It might make more sense to wait for any changes that will happen in 3.0.
That said, if we're designing for 3.0 already ... it might be good to think what we might be able to do for the user in terms of "user experience" here. I've always seen rasa data validate as a linter of sorts. It'd be grand if Rasa offers a command that can help the user with any typos in the configs.


Add handle property to array field

This PR adds the handle property to ArrayField to return the underlying GRIB handle (when exists).

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.53%. Comparing base (d6e7f47) to head (b6ab6a0).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop     #464      +/-   ##
===========================================
+ Coverage    90.51%   90.53%   +0.02%
===========================================
  Files          128      128
  Lines         8732     8751      +19
  Branches       733      735       +2
===========================================
+ Hits          7904     7923      +19
  Misses         690      690
  Partials       138      138

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


Move the unityar camera settings provider out of experimental

This change moves the UnityAR camera settings provider out of an experimental namespace. It has shipped for two releases and the reported issues have been addressed.

/azp run

@julenka FYI
@davidkline-ms as part of graduating this out of experimental, have we added some new collateral that can help with ongoing checks that this platform isn't regressed going forward? I think that if we were purely to base moving out of experimental based on lack of feedback, we could graduate almost everything today.

Expanding on my previous comment, for example, with the graduation of the object manipulator out of experimental, @MenelvagorMilsom  is adding a bunch of docs and stuff:
https://github.com/microsoft/MixedRealityToolkit-Unity/pull/7345
I don't know if our docs for ARFoundation stuff (both internal for build call and external) have the same level of detail

Were there any files / examples that were in experimental folders that also need to be moved

No. There are no UnityAR specific examples.

it would be good to next time put experimental features actually in an experimental folder

They were previously (2.2.0) in the staging folder. I missed creating an experimental folder when I moved the code in 2.3.0.

What tests do we have to ensure that future changes don't regress this platform?

Unfortunately, this is not a component that can be tested in play mode as it requires a mobile device (Android / iOS).

What documentation do we have to show people how to use the unityar camera?

We have documentation here: https://microsoft.github.io/MixedRealityToolkit-Unity/version/releases/2.3.0/Documentation/CrossPlatform/UsingARFoundation.html
I am happy to expand / update it as part of this change.

Is this the one component needed to allow MRTK to work on phones?

Correct, it is the component that enables use on phones.

I think that if we were purely to base moving out of experimental based on lack of feedback, we could graduate almost everything today.

Good point. I am more than happy to solicit feedback from the community and/or keep this component experimental in the upcoming release to gather more usage information.

Unfortunately, this is not a component that can be tested in play mode as it requires a mobile device (Android / iOS).

What about adding tests to verify that touch input and interaction work? You could add a playmode test that simulated touch interaction and verifies that you can press buttons for example? I would imagine that graduating phone support for MRTK would encompass the following:

For each UX component, add a test that verifies that this UX component can be interacted with using touch interaction. The list of components would be:

Button
Interactable
Slider
ManipulationHandler
Slate
UnityUI

Also, what about adding something in our automated build system that verifies that Android and iOS targets can compile? Something that checks "Does MRTK compile for Android" and "Does MRTK compile for iOS".

I added #7382 to track writing tests for phone / touch. Following our principle "prioritize tests to protect against regression" and "when graduating experimental features, add tests and docs", I'd recommend we don't graduate UnityAR support aka phone support until we have tests.

Closing. Not going to move out of experimental until spatial features are completed and a better understanding of usage and experience has been obtained


Update Chart.Bar.js to cater to an array of colours for fillColor

Change to line 113 - allows for the passing of an array of fill colours to the the bar chart or a single colour (the current implementation)
Possible modification is to make the index into the fill color array the mod of the length of the array so that the colour array does not have to match the number of labels.

This looks good. Since this changes (backwards compatible) API, requesting an updated to docs.

We've recently announced a feature complete status for v1.x and will only be accepting bug fixes for v1.x. Be sure to take a look at v2.0-dev and it's new features that are either finished or currently under development.  If you see your feature is still not implemented, feel free to submit another PR to the v2.0-dev (or later) branch for your feature.


Create a global config file for AIOps services

For example, many nats_subjects shared across AI services should be placed in a global config.

And add docstrings to AIOps scripts

move it to ideas


Notes on Celestron OAG Dimensions

Attached are some notes on the critical dimensions of the Celestron OAG should you decide at some point to make a design for it.
Notes on Celestron OAG Dimensions for ASCOM-OAG-FOCUSER Picture 1 .pdf
Notes on Celestron OAG Dimensions for ASCOM-OAG-FOCUSER Picture 2 .pdf

I will not support the Celestron OAG. I added a section to the README that documents OAG compatibility. Thanks!

Here's a completed design for the Celestron OAG.   If acceptable, would you add it to your project for people who want to print and use it themselves?
Regards,
John
CelestronOAG.zip

https://github.com/jlecomte/ascom-oag-focuser/assets/92014533/0007f066-bc40-46ed-a3a4-cc8e99c39e2c
Video in action.

This is great! I see you attached an OpenSCAD file. Let me see if I can import it in FreeCAD. Thanks!

OpenSCAD file is a bit messy - this may help:
BaseA is
rotate([180,0,0])
CelestronBaseA();
BaseB is
rotate([180,0,0])
CelestronBaseB();
Cover Plate is
TopCover();
Gear (60 teeth) is
CelestronGear();
Pinion (16 teeth) is
MotorPinion();

I added the files to the GitHub repository, and credited you for this contribution. Thank you!

Notes on printing the Celestron OAG parts.
I used 0.2mm with 15% fill.   No supports used on any parts but I do recommend a brim around BaseB as there is a possibility for the print to mess up at the end of the semicircular clamp if you don't.


Generate Qiskit 1.0 API docs for release candidate

This will allow us to detect problems proactively.
It's important that we have fixed the Docker image used in ./start to be the latest version so that we can detect problems like https://github.com/Qiskit/documentation/issues/673.
We should actually deploy these API docs even though it's an rc. Users are asking for it. Relates to https://github.com/Qiskit/documentation/issues/316. I'm actually not sure the URL scheme for this though...If we use --historical to make a 1.0 folder, then those pages will stop working once we switch 1.0 to be the current unversioned API docs without 1.0 in the URL. Normally we only have the number in the URL for historical API docs, not the current. I think the only fix is to implement https://github.com/Qiskit/documentation/issues/316.

Closed in https://github.com/Qiskit/documentation/pull/787. Thanks @arnaucasau!


UI2 dependency upgrades

Feature Request
A list of dependencies and tools we may wish to upgrade in the UI2 for 1.5.0
Desired behaviour

Completely replace ngx-bootstrap with Angular Materials (officially bundled with Angular 6) because less 3rd party dependencies, let Angular handle versions bundled.
Upgrade our Angular 4 to Angular 6 (and all its suggested deps which include Typescript 2.6+).  For those whose auto-import depend on Typescript 2.6+, also ngxs and ngrx requires Angular 6.
Upgrade Angular CLI to the latest version that matches Angular 6
Upgrade npm to 5.7.1+ to avoid the EINTEGRITY error (latest nodejs LTS is still tied to npm 5.6.0 though.  even nodejs 9.x is also tied to npm 5.6.0 )
Bootstrap 4 (4 is now stable but first glance appears to be a real pain for not much benefit)

Results from the discussion:

Upgrade to Angular 6 with matching Angular CLI
Upgrade Cypress
Experiment on NPM 5.7.1
Don't upgrade to Bootstrap 4
Slowly phase in Angular Material
Hold off on NGXS

Mostly in flight, follow-up with individual tickets as appropriate


Add getFormError selector

Should close https://github.com/erikras/redux-form/issues/3463
I didn't change getFormSyncErrors, getFormAsyncErrors, getFormSubmitErrors methods, because we can set _error prop not only via SubmissionError. And we can't determine how _error prop was set. The simplest way - is to add one more selector.

Codecov Report

Merging #3483 into master will not change coverage.
The diff coverage is 100%.

@@          Coverage Diff           @@
##           master   #3483   +/-   ##
======================================
  Coverage     100%    100%
======================================
  Files          66      67    +1
  Lines        1505    1509    +4
======================================
+ Hits         1505    1509    +4

Impacted Files
Coverage Δ

src/immutable.js
100% <ø> (ø)
:arrow_up:

src/index.js
100% <ø> (ø)
:arrow_up:

src/selectors/getFormError.js
100% <100%> (ø)

Continue to review full report at Codecov.

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

Thanks @faizrr! For my learnng, Im kind of new to redux-from, how else can I set _error?

@Noitidart via sync validation, for example (https://redux-form.com/7.0.4/examples/syncvalidation/)

Ooh, thanks @faizrr

Awesome. Update the docs and I'll merge.

Nevermind, I'll add the docs. 😄

Super cool thanks folks!!

Published in v7.1.0.


Always show view extension header

Always show header, including when doing single image inference.
Rename "summary_template" to "header_template".

LGTM


[WIP] Remove unused files & code

          1 Warning

:warning:
PR is classed as Work in Progress

  Generated by :no_entry_sign: Danger