Rasa Convert - Permission Denied

Rasa version:1.5.3
Python version: 3.6.9
Operating system: Windows
Issue: Permission denied to access out path, on convert files to json.
Error (including full traceback):
Traceback (most recent call last):
  File "C:\Program Files\Python36\lib\runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "C:\Program Files\Python36\lib\runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "C:\Program Files\Python36\lib\site-packages\rasa\__main__.py", line 87, in <module>
    main()
  File "C:\Program Files\Python36\lib\site-packages\rasa\__main__.py", line 76, in main
    cmdline_arguments.func(cmdline_arguments)
  File "C:\Program Files\Python36\lib\site-packages\rasa\nlu\convert.py", line 38, in main
    convert_training_data(args.data, args.out, args.format, args.language)
  File "C:\Program Files\Python36\lib\site-packages\rasa\nlu\convert.py", line 34, in convert_training_data
    write_to_file(out_file, output)
  File "C:\Program Files\Python36\lib\site-packages\rasa\nlu\utils\__init__.py", line 55, in write_to_file
    io_utils.write_text_file(str(text), filename)
  File "C:\Program Files\Python36\lib\site-packages\rasa\utils\io.py", line 233, in write_text_file
    with open(file_path, mode, encoding=encoding) as file:
PermissionError: [Errno 13] Permission denied: 'data'

Command or request that led to error:
python -m rasa data convert nlu --data data/intents --out data --format json

Thanks for the issue, @TyDunn will get back to you about it soon!
You may find help in the docs and the forum, too 🤗

@DiegoProtec what are the permissions on your data directory? Have you tried running the command as an administrator?


Automated Package Upgrade

:tada: This PR is included in version 7.0.48 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Prevent multiple Elasticsearch instances, missing configuration and unnecessary restarts.

Prevent multiple Elasticsearch instances, missing configuration and unneccessary restarts.

After VM reboot there can be 2 elasticsearch instances running on a single VM
After reconfiguration/redeployment the Azure Cloud Plugin settings are forgotten
During reconfiguration/redeployment all elasticsearch instances are restarted

Further details:

Sporadically, 2 instances of elasticsearch are started on the same VM after reboot. There is a race condition between the System-V style init scripts and monit at boot. Both monit and the init script try to start elasticsearch. The monit FAQ recommends to disable the System-V style init scripts.
==> changed elasticsearch-ubuntu-install.sh to disable the System-V style init scripts and only use monit for starting elasticsearch.
When redeploying the ARM template (e.g. to increase the data node count) the elasticsearch-ubuntu-install.sh script recreates the elasticsearch.yml files but does not include the Azure Cloud Plugin configuration settings.
==> moved the Azure Cloud Plugin settings from the install_azure_cloud_plugin function to the configure_elasticsearch_yml function
Redeploying the ARM template (e.g. to increase the data node count) causes all elasticsearch instances to be restarted resulting in a temporary cluster unavailability.
==> only restart elasticsearch if the configuration has changed.

Thanks @ajhewett! Will take a look at this next week

Took us a while to merge this in but finally got the cycles to take these changes for several spins (actual deploys).
Thank you for continuing to improve deploy resilliency @ajhewett!
I also added node.max_local_storage_nodes: 1 to the configuration so that in the event a second node is started (manually even) it will complain about an already running node.
Elasticsearch 5.0 defaults to only allowing one node to be run 🙌
Sidenote we still would love to send you some elastic related items as a thank you @ajhewett mind sending your details over to<EMAIL_ADDRESS>?


fix: ignored EC_API_KEY environment variable

Description

Fixes the problem where the EC_API_KEY environment variable wasn't
read.
The problem was that viper (correctly) unpacked the EC_API_KEY as
api-key, and since the mapstructure tags (in ecctl.Config) reference
api_key, the key is correctly un-marshaled when a config file is read,
but not when set via environment variables.
The fix is to set an alias api_key to the existing api-key key,
which is done in cmd/root.go:143.
v.RegisterAlias("api_key", "api-key")

The rest of the patch is necessary to provide at least some unit tests
to be able to assert this behavior.
Related Issues

Part of #376
How Has This Been Tested?

unit tested and tried against production ESS.
Types of Changes

[x] Bug fix (non-breaking change which fixes an issue)

Once we merge this PR, it needs to be back ported to the 1.0 branch


Sending documents by HTTP URL returns 400 Bad Request

Expected Behavior
I'm trying to send a GIF to a channel using sendDocument, with the chat ID and the document's URL
Actual Behavior
I'm getting a 400 error, that says "Bad Request: there is no document in the request"
Steps to reproduce the Behavior
bot.onText(/\/link (.+)/, (msg, match) => {
  const chatId = msg.chat.id;
  const resp = match[1];
  bot.sendDocument(chatId, match);
});

And then send /link + the document's http link to the bot on a private chat.

PS: Consider that the link may NOT be pointing to a GIF, thus the sendDocument() call may fail in such a scenario.

The code I posted was an example, I tried hardcoding the links to the bot, and it didn't work either

And also, sending audioless .mp4 links via the HTTP API (by hand, I mean) worked fine.

Can you provide us with links that don't work with the method?

Used this exact code:
bot.onText(/\/link (.+)/, (msg, match) => {
  const chatId = msg.chat.id;
  const resp = match[1];
  bot.sendDocument(chatId, resp);
});

and sent this exact command:
/link http://i.imgur.com/nho74sk.mp4
got this exact error
Unhandled rejection Error: ETELEGRAM: 400 Bad Request: there is no document in the request
    at BaseError (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\node-telegram-bot-api\src\errors.js:10:5)
    at TelegramError (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\node-telegram-bot-api\src\errors.js:56:5)
    at request.then.err (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\node-telegram-bot-api\src\telegram.js:181:15)
    at tryCatcher (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\promise.js:512:31)
    at Promise._settlePromise (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\promise.js:569:18)
    at Promise._settlePromise0 (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\promise.js:614:10)
    at Promise._settlePromises (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\promise.js:693:18)
    at Async._drainQueue (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\async.js:133:16)
    at Async._drainQueues (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\async.js:143:10)
    at Immediate.Async.drainQueues (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\async.js:17:14)
    at runCallback (timers.js:666:20)
    at tryOnImmediate (timers.js:639:5)
    at processImmediate [as _immediateCallback] (timers.js:611:5)

Unhandled rejection Error: ETELEGRAM: 400 Bad Request: wrong file identifier/HTTP URL specified
    at BaseError (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\node-telegram-bot-api\src\errors.js:10:5)
    at TelegramError (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\node-telegram-bot-api\src\errors.js:56:5)
    at request.then.err (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\node-telegram-bot-api\src\telegram.js:181:15)
    at tryCatcher (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\util.js:16:23)
    at Promise._settlePromiseFromHandler (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\promise.js:512:31)
    at Promise._settlePromise (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\promise.js:569:18)
    at Promise._settlePromise0 (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\promise.js:614:10)
    at Promise._settlePromises (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\promise.js:693:18)
    at Async._drainQueue (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\async.js:133:16)
    at Async._drainQueues (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\async.js:143:10)
    at Immediate.Async.drainQueues (C:\Users\Pichau\Documents\GitHub\thegifmachine\node_modules\bluebird\js\release\async.js:17:14)
    at runCallback (timers.js:666:20)
    at tryOnImmediate (timers.js:639:5)
    at processImmediate [as _immediateCallback] (timers.js:611:5)

Do you mind opening a new, separate issue for this? Please provide us with the example URLs, like the one you stated above, that cause the method to fail.


Fix error from CL_PACKAGE_FACTORY=>LOAD_PACKAGE

Added TRY-CATCH
Changed to T100 for SAP_PACKAGE errors
Rest is whitespace change

Closes #3957

thanks 👍


How to use manage roles for column permission

RlLS is great to grant row level permission. It would be nice to have column level permission for sensitive data like salary, costs, gross margin etc.

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

ID: d5505062-94f3-e15d-a52f-ce1ac7f8cb69
Version Independent ID: 34076b73-0ded-2111-ed44-2a31e07deb53
Content: Row-level security (RLS) with Power BI - Power BI
Content Source: powerbi-docs/service-admin-rls.md
Service: powerbi
GitHub Login: @mgblythe
Microsoft Alias: mblythe

Hi @BrianHo888 ,
Your contribution is much appreciated. Our team can only answer feedback related to the documentation.
Please kindly log your product feedback by using the button "Give Product Feedback" at the bottom of the DOCS page.
If you have any feedback related to the documentation, please feel free to log it through this channel.
We truly appreciate your contribution to our articles.
Kind regards,
Microsoft DOCS International Team


Update test tools and proptypes

replaces deprecated PropTypes with prop-types package
replaces deprecated shallow render with shallow render from react-test-renderer package
removes unneeded react-addons-test-utils package

closes #339.

thanks for the PR @tconroy, sorry for the late reply! I'm about to add React 16 support and add a new release


fix: Remove debugger calls

The playground debugger gets in my way frequently since I like to keep devtools open while in the playground and this triggers on almost every character typed when importing modules. The twoslash call was removed for completeness.

Yeah, let's do this


Timeline chart horizontal bars are only taking proportional part of available space

Bug report
When using the timeline chart if the series only have two different names, let's say A and B and the data x values are all different respectively, then the bar will be rendered taking proportionally small part of the available space only.
Codepen
Demonstration of the issue HERE.

I expect the bars to fill all the available space

What is happening instead?
The bars don't take all space

What error message are you getting?
None

I have the same problem. My ranges are guaranteed to not overlap, so I need to show all series for the same role on the same "track". I've tried setting plotOptions.bar.rangeBarOverlap to true and it makes no difference.

Any update on this ?

Same here, Any update ?

This is fixed in this PR
The new property will be plotOptions.bar.rangeBarGroupRows
It will be released in v3.22.0

https://apexcharts.com/javascript-chart-demos/timeline-charts/multiple-series-group-rows/

plotOptions.bar.rangeBarGroupRows: false

plotOptions.bar.rangeBarGroupRows: true


Improve scrolling flaky test

ScrollViews seem to be a little inconsistent when they start scrolling. The gesture detection requires a few points of travel to begin detecting, but the exact time the detection begins seems to vary, meaning that the scroll amount is not precise. Fixing by making the check allow for a bigger variation

👀 @dduan


Add Travis CI, refactor gulp tasks

@feimosi: do not merge this yet, we need to decide which node.js version to run tests on.
In order to see this in action please add Travis CI to this repository.

So which Node.js version you want to use @feimosi?

OK, I think now it's ready.

@feimosi: bump
I also added a fix for autoprefixer; previously you only specified FF 3.6 so there were missing prefixes for FF.

I'll review and merge this, as well as #93, during the coming weekend.

Cool, I wouldn't merge 93 personally, not close to a stable at least.

Done.

BTW, it seems the accessibility fixes made HTML_Codesniffer pass too :D

Done.

LGTM :+1:

Please do not squash these when merging. They are separate patches and should be like that when merged.

Ok, just please, make sure to rebase the whole branch on top of master and I'll merge it.

It is rebased already.
On Apr 10, 2016 00:23, "Marek Grzybek"<EMAIL_ADDRESS>wrote:

Ok, just please, make sure to rebase the whole branch on top of master and
I'll merge it.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/feimosi/baguetteBox.js/pull/91#issuecomment-207855502

Ok, everything's fine :+1:

See that is what I was saying all this time...
On Apr 10, 2016 00:40, "Marek Grzybek"<EMAIL_ADDRESS>wrote:

Ok, everything's fine [image: :+1:]
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/feimosi/baguetteBox.js/pull/91#issuecomment-207856791

Look at my other comment:
https://github.com/feimosi/baguetteBox.js/commit/2d5068461f0d21f091a31cb865289035a9bd784f

BTW I think we need margin for figure after all. I'll test it tomorrow and
make a pr until I manage to properly fix the styles.
The regression is on mobile.
On Apr 10, 2016 00:46, "Marek Grzybek"<EMAIL_ADDRESS>wrote:
Look at my other comment:
2d50684
https://github.com/feimosi/baguetteBox.js/commit/2d5068461f0d21f091a31cb865289035a9bd784f
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/feimosi/baguetteBox.js/pull/91#issuecomment-207858647

Also can you make the gh-pages branch and maybe create a dev one? I want to
start working on 2.x.
On Apr 10, 2016 01:10<EMAIL_ADDRESS>wrote:

BTW I think we need margin for figure after all. I'll test it tomorrow and
make a pr until I manage to properly fix the styles.
The regression is on mobile.
On Apr 10, 2016 00:46, "Marek Grzybek"<EMAIL_ADDRESS>wrote:
Look at my other comment:
2d50684
https://github.com/feimosi/baguetteBox.js/commit/2d5068461f0d21f091a31cb865289035a9bd784f
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/feimosi/baguetteBox.js/pull/91#issuecomment-207858647

gh-pages is done, as well as dev branch. Could you test the current code base yourself, just to make sure and I'm gonna finally make the 1.6.0 release.
Unfortunately, my availability will be limited now.

I think everything is fine now.


Preparing for 2.1.3-stable

It's time to work on stabilising the 2.1 branch again so that we can release 2.1.3-stable.
2.1.2 was two months ago, and since 3.0 is taking its time, many devs have pushed some development work to the 2.1 branch directly, so we'll need to do some more extensive testing - we have more than just bug fixing commits :)
This issue is meant to gather initial feedback on pre-release binaries, so that we can spot regressions (either from new developments or from bad cherry-picks I might have done).
You'll find binaries from yesterday here: https://github.com/GodotBuilder/godot-builds/releases/tag/2.1_20170319
Known issues:

CanvasItemEditorPlugin tries to access set_position instead of set_pos: fixed in 4230b22 (but not in above binaries)
CanvasItemEditorViewport tries to connect to non-existing CheckBox signal: https://github.com/godotengine/godot/commit/a9d8da91b72fe8493f9087563056bb4ade4ca2c7#diff-3910e354cfb3848e417581c47035e5c5R3777
Something was fishy with iOS templates in 2.1.2-stable? Help welcome to know exactly how the zip should be setup.
add yours :)

Note: as always I'm only interested in regressions (i.e. bugs that did not affect earlier 2.1.x versions), including to some extent bugs in new features if there are any. Packaging issues with the templates, etc., are of course also interesting :)

Regarding android binaries, I couldn't build them successfully on Travis because our logs are spammed with warnings and Travis kills the build when the log exceeds 4 MB... https://travis-ci.org/GodotBuilder/godot-builds/jobs/212575435
So if someone can work on either fixing warnings, or adding a scons option I could use to silence them (or some of them) during Travis builds on GodotBuilder, that would be great.

Never used scons but looks like this removes the target info and shows only warnings
SConstruct
Line 250
def print_cmd_line(s, targets, sources, env):
        sys.stdout.write("")

    env['PRINT_CMD_LINE_FUNC'] = print_cmd_line

I tried this for the warnings but no luck maybe I did something wrong.
http://stackoverflow.com/questions/10147079/disable-all-scons-warnings

If can help I have some bugs to mention:
1-On iOS templates the executables files are zero bytes while those in folder are correct size and working so to make it working we have to replace those 0 bytes files with the correct ones inside the inner folder.
2- There is a bug with audio drivers on iOS. If an app that uses sample player is running, after the iPhone receive an incoming call or even a siri function, sample player does not work anymore and no audio is outputted from device. I think that is very important bug to be fixed because a lot of users may have some game on the App store.
3- Function "OS.set_low_processor_mode_usage" makes the app when runned on the android phones to a flashing mode like, even tough the function doesn't even work at the moment like Juan told somewhere. On iOS i don't know how this affects the app.
4- Not very sure. However I have an old project made in godot and it compiles correctly on my android phone on 2.0.3 but not on later versions of the engine. I really don't know what this can be because all options and settings are the same, so maybe can be a bug in export template for android. I think that more or less the problem has began after the OpenSSL issue was fixed. In fact my app on the Play store of google still has that problem because i couldn't compile it after that time.

Blocking for the release: #8090
(I'm nevertheless preparing some RC1 binaries right now that I will soon publish).

Here are the binaries (properly packed as normal releases) for 2.1.3-rc1, please test extensively and report any regression: http://download.tuxfamily.org/godotengine/2.1.3/rc1/
I think I've fixed the iOS template issue, please confirm.

Go forward and backward is not working

Settings > Editor Settings > Shortcuts > Search > "indent"
clear key bind "Indent Left" and "Indent Right"
select several files on script editor
try go forward or backward with Alt+Left (Right)

Found how to fix it.

Settings > Editor Settings > Shortcuts > Search > "indent"
clear key bind "Indent Left" and "Indent Right"
Search > "history"
assign key Alt+Left (Right) on History Prev / Next

I don't know why Godot can't recognize Ctrl + Alt + Arrow.
I tried to assign Ctrl + Alt + Arrow for shortcut but only recognize Ctrl + Alt (not arrow)
but still Ctrl + Tab or Ctrl + Shift + Tab doesn't work for me. :cry:

Damn...
it's because of shortcuts for switching workspace on ubuntu. never mind my comments. :disappointed:

Once #8090 is fixed (found the regression), I'll make RC2 binaries. It will probably be early next week though, I won't have time over the week-end.

#8177 and #8178, both related to TouchScreenButton shapes, the latter in particular, even if it is not a "bug" it could bug users.

We should probably check that #7696 gets fixed before that release too, a crash is never good in a stable release.

Testing the RC2 binary for OSX I'm getting parser errors relating to inner classes:
I was initially getting Parser Error: Expected indented block after 'for' in block of code in an inner class. I suspected it has to do with the inner class, so I added the following to another file as a test:
func _input(event):
	pass

# inner class test
class TestInner:

	var foo = 1

	func bar():
		pass

which results in Parser Error: Error parsing expression, misplaced: class
For the former I can keep commenting out code and it will just complain about the next block being unexpected. This is code with no changes that is properly indented and worked fine as-is in 2.1.2

@FuzzyRhombus Probably #8315, which was my fault. The offending changes have been reverted.

@FuzzyRhombus Thanks for the report, it's likely the same bug as #8315. It's fixed in the 2.1 branch now as I reverted the problematic change, so 2.1.3-rc3 should be good.

Good to know 👍
Sorry I didn't look through the existing issues =O

Found this :bug:  #8323
Is the new flip texture for Particles2D.

ALL WAS GOOD until I started testing something else and saw #8090 again, it looks worse now but at least I know how to trigger it, that may give some hint :sweat_smile:

ALL WAS GOOD until I started testing something else and saw #8090 again, it looks worse now but at least I know how to trigger it, that may give some hint 😅

Could you test the current 2.1 HEAD branch? I just merged a PR that should improve this stuff further.

@akien-mga the main issue seems to be gone :+1: , now the only thing that do not work is the button to reload default value if you disable monitoring on the instanced scene (stays disabled), clicking the checkbox works.

So, as far as I'm concerned it's starting to look release ready. Any objection? :)


Rudder pushes in wrong directions while inverted

When flying inverted, using the rudder will result in the plane initially turning in the correct direction, but if the rudder is held, it will start to turn the plane in the opposite direction (i.e. right rudder while inverted will turn your nose right, then cause you to slowly drift left, and vice versa).  It's not clear what causes this phenomenon, but presumably, there's no mechanism in place to recalibrate rudder physics for inversions.

Assigned Decaff and Krux since I believe they'd be best capable to resolve this.

Strange update: Decaff and I tried replicating this glitch during Friday Night Flight earlier, with him flying an EE Lightning, and me flying XH558 (both from Flash's pack), and neither of us could replicate this glitch. It might only affect certain planes.

What version of YS was this on?

this was on 2015 Ysflight

Can it be reproduced in the latest release? If so it might be a bug that was introduced in later versions.

Just tested this on Jobbin's RWR build (which is somewhat fresh, and I can safely say this was probably fixed by Soji back in YS' pre-OS days.
I flew the stock F-18E out of Misawa just now to test real quick and from what I can tell, behavior is in line both with animations and physics as far as I can tell.
Gonna mark this down as fixed in upstream.


Unable to create another project

Hi !
First, thanks about this awesome tool. I have an issue about creating a second project.

As you can see in the above image, it seems that the domain is conflicting with my other projet. But the portal domain input is not editable. So I have change my other project domain and subdomain as follow:

But I am still getting the issue and nothing seems to fix it.

Ah yes, when you change the subdomain or a custom domain, we keep the old one pointing to your project for a day just in case you want to switch it back. After the one day, you are free to use it for another project.
If you want to do this immediately, you need to change the configuration property to reduce this time using:
com.smotana.clearflask.store.impl.DynamoProjectStore$Config.slugExpireAfterMigration=PT1S

Then restart your server or just wait for the config to be reloaded automatically within 1 minute

@matusfaro Great thanks !
Do you know why the input portal domain act differently on self host and on cloud saas ?

This screenshot is from Saas, which it is more clearly understandable and also editable unlike the self hosted one which is clearly not editable and not displaying same thing. Maybe a config ?

@matusfaro Thank you for your feedback !
com.smotana.clearflask.store.impl.DynamoProjectStore$Config.slugExpireAfterMigration=PT1S

By the way I've added this into config but it does not seems to work. I have setup abeecrm.feedback.abbi.tech, in subdomain & domain, but:

feedback.abbi.tech is still pointing to the project
adding a project now return a 500 error

This is now fixed in 1.6.9


First efforts towards an improved improved readme

Note, at one point the readme refers to tutorials in the documentation. For now this hyperlink simply directs to the index page, as there is no tutorial page in the docs yet. This will be updated ofcourse later once this page is present in the docs.

I've improved the readme based on the comments :)

cool, removed the deprecation warnings. Should be good to go :)

Should be all good to go!


Sanity check consistency of public APIs (best effort)

We should best effort try and patch any inconsistencies of the Substrate public api. This includes, but is not limited to:

Function Names
Function Parameters and order
Variable Names
Structure and Custom Type names
Event Names and parameters
Error Names
etc...

To be more explicit, we should avoid situations where two different traits expose functions with different names when their behavior is the same. i.e. one trait has remove_account and the other has delete_account.
We should avoid situations where the same variable is referenced with different variable names. For example caller vs sender in a public API.
We should make sure that the order of items in events are logical. i.e. we want to avoid:

UsersBecameFriends(BlockNumber, User1, User2)

UsersAreNotFriendsAnymore(User1, User2, BlockNumber)

This task is truly endless and I imagine will be full of opinions, so it is important to note that this is best effort.
Let's just fix up what we can.

Super apropos that this Issue was filed on Valentine's Day as I think this represents a huge show of love for our developer community :heart_eyes: I was having a conversation with @JoshOrndorff about some issues related to this topic. Namely: coming up with a more descriptive name for the very important Trait trait and augmenting our naming conventions to avoid reusing the same word for multiple components in a pallet (e.g. CurrencyType and CurrencyTrait). I would love to help out with this effort in any way possible.

Is the following issue included in this?
Taking pallet-identity as an example, neither the Module nor the Trait is documented. I think it would be good to generate at least a stub explaining succinctly what they are and also include links to the corresponding substrate.io knowledgebase articles.
In general our rustdocs could use some love.

Good question, but no...I would consider that a separate effort. Rustdocs, however, is something that I am personally thinking a lot about so would be happy to work together on that :fist_right: :fist_left:


fix: stop exporting express types publicly

We don't have a dependency on express. If we expose express types
as part of our public, our dependent modules will need to have a dev
dependency on @types/express. Otherwise they see their builds failing.
Currently there is no way to express this dependency relationship to
npm.
Instead, let's not use express types.
Ref: https://github.com/googleapis/nodejs-logging-bunyan/issues/243

This doesn't solve the problem generally. It just kicks the can down the road.


GroupUrlRule nesting fails with error

What steps will reproduce the problem?
Consider this config:
        "urlManager" => [
            "enablePrettyUrl" => true,
            "showScriptName" => false,
            "suffix" => "/",
            "rules" => [
                [
                    'class' => 'yii\web\GroupUrlRule',
                    'rules' => [
                        [
                            'class' => 'yii\web\GroupUrlRule',
                            'rules' => [
                                [
                                    'pattern' => "faq/post",
                                    'route' => "faq/post",
                                ],
                            ]
                        ]
                    ]
                ]
            ]
        ]

And open site.com/faq/post/
What is the expected result?
I expect FaqController::actionPost() will be invoked to display the page.
What do you get instead?
I see error
Unknown Property – yii\base\UnknownPropertyException
Getting unknown property: yii\web\GroupUrlRule::name

Additional info

Q
A

Yii version
2.0.10

PHP version
any

Operating system
any

Looks like problem is in this line: https://github.com/yiisoft/yii2/blob/master/framework/web/CompositeUrlRule.php#L51
With this line commented everything works as expected.

Is it the same as https://github.com/yiisoft/yii2/issues/10231?

It looks similar, but I am not familiar with yii\rest\UrlRule, #10231 seems more complex issue for me.

yeah, its the type of error. Closed in favor of https://github.com/yiisoft/yii2/issues/10231


Insecure CORS Configuration

The Cross-Origin Resource Sharing is not configured properly.

Recommendations
- Ensure that URLs responding with Access-Control-Allow-Origin: * do not include any sensitive content or information that might aid attacker in further attacks.  									 									 - Allow only selected, trusted domains in the Access-Control-Allow-Origin header. Prefer whitelisting domains over blacklisting or allowing any domain (do not use * wildcard nor blindly return the Origin header content without any checks).

handled from backend response

fixed and tested.


bug

bug when it starts growing/shrinking when it is close to a growing/shrinking ball and the zombie ball is seen on startup

fixed


feat: tmq replace VALUE_DESERIALIZER with VALUE_CLASS, and add VALUE_…

tmq replace VALUE_DESERIALIZER with VALUE_CLASS, and add VALUE_MAP_UNDER_SCORE_TO_CAMEL_CASE

replace value.class with value.deserializer, so we don't not need to define an empty deserializer class.
add value.mapUnderscoreToCamelCase to auto map the field name which is camel case with the column name which is under score

Users can realize V deserialize(ResultSet data) method by themselves if necessary. They will not be limited by a given implementation such as ReferenceDeserializer.

i think in most mq products, we need different deserializer because we can define the serializer. but in the tmq, we have to  deserialize from the ResultSet, in fact the sql we used when we define the topic. of course,  you think users can define  their desrializer, it is right

I think converting the ResultSet to CamelCase format is also a requirement, so you are welcome to submit a deserializer sometime


Resolving merge conflicts for nav buttons

fix: resolved merge conflicts involving the navigation buttons
Summary
Closes #29
I made sure to update my local repository properly such that this new branch can automatically merge with the existing code. Otherwise, no other changes have been made with the functionality of the navigation buttons.
Test Plan
Same as before, made sure that each next button and back button matched the order outlined by the figma mockup. Also ran lint checks multiple times for formatting errors.

Hi, great job adding the next / back buttons! Just some friendly feedback for next time:

Could you make the updating the dependencies in yarn/yarn-lock into a separate PR? We don't want to break or unintentionally modify existing features (in more technical terms - cause regressions) by updating the version. Also, if it breaks something, it's easier to roll back just the PR that updates the dependencies
Could you see if it's possible to reuse code? Looks like a lot of the back/next button code is being copy-pasted, could we have made this into a component?


[2.0.0] secret_manager: missing 1 required positional argument: 'data_crc32'

Works on 1.8.0 but fail to get secret when no data_crc32 was specified.
unmarshal_AccessSecretVersionResponse
    return AccessSecretVersionResponse(**args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
TypeError: AccessSecretVersionResponse.__init__() missing 1 required positional argument: 'data_crc32'

Hey!
Good news! The latest release of the scaleway-async package has fixed the issue. To get the update, just run this command:
pip install --upgrade scaleway
Thanks a bunch for your patience and support!


chore: merge develop into main

:tada: This issue has been resolved in version 5.2.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Cookies disclaimer

https://github.com/actum/gulp-dev-stack/issues/82
@zoltan-kovac works on accordion module so let’s keep the issue open

CookieLaw fn is definitely useful, but it’s not the best example of factory functions (in fact, it’s not a factory function :).
Hope accordion will be better example.


[Performance Issue] Combobox is taking lot of time to render when binding large chunk of data

🐛 Bug Report
Rendering of a combobox in a page is taking lot of time when binding a large chunk of data to it.
💻 Repro or Code Sample
Getting the list of servers. In the database there are thousands of servers. Fetching the server details through LINQ.
It takes not more than 2 to 3 sec for fetching 8k records. However taking very much for binding the list of records to Combobox and getting it render in browser.

🤔 Expected Behavior
Should not take much to render combobox with large set of data.
😯 Current Behavior
Taking ~1 to 1 1/2 min to load the page with 8k of records in combobox.
💁 Possible Solution
Not sure
🔦 Context
🌍 Your Environment

OS & Device: Windows
Browser : Microsoft Edge, Google Chrome, Apple Safari, Mozilla FireFox]
.NET: NET 6 and FAST Version : 3.5.0(microsoft.fast.components.fluentui)

Loading 8k items in a Combobox is never a good idea. All items will be loaded into the DOM so the page will get very heavy, even when just using standard HTML option elements. There will not be much we can do about that.
Think you need to re-think what interface to use for this.


BUG: The plugin doesn't work with Webpack/Typescript configuration

I'm using Aurelia with Webpack and Typescript (not Aurelia-cli). I see blank screen after adding a component. There are no errors in browser  console. Seems like as all elements aren't rendered, but present.

That's weird, especially since the project itself is built on TypeScript. Maybe it's an issue with this project and webpack?
Hopefully @Ullfis responds but he hasn't been around for about 8 months.

I'm sorry! It was my bug. I used one of samples of the drawer and not paid attention to one of delegates. In another words, I haven't defined method in my view-model. That's interesting the application doesn't throw an exception, but no content is rendered, e..g. the content is still present in browser, but invisible.
@djensen47, thank you for your attention anyway!


Revert "Cancel incomplete BLE connection when CloseAllBleConnections() is called (#27304)"

This reverts commit ad5403e8e537612c2d2f903895642445d45d1e08.
There are two issues:

https://github.com/project-chip/connectedhomeip/issues/27607 which has had no response for weeks.
https://github.com/project-chip/connectedhomeip/issues/28139 which breaks commissioning on Mac, and would break it on Linux if it implemented BLE connection cancellation.

We need to sort out why CHIPDeviceController is canceling BLE connections when starting PASE over BLE (!).
Fixes https://github.com/project-chip/connectedhomeip/issues/28139

@bzbarsky-apple The change makes logical sense though, to cancel any connections being established though? Why is this causing issues?

@woody-apple Because of this stack:
  * frame #0: 0x0000000101bf916c chip-tool`chip::Ble::BleLayer::CancelBleIncompleteConnection(this=0x0000000102beb5a0) at BleLayer.cpp:372:5
    frame #1: 0x0000000101bf8cd4 chip-tool`chip::Ble::BleLayer::CloseAllBleConnections(this=0x0000000102beb5a0) at BleLayer.cpp:312:22
    frame #2: 0x0000000102260b80 chip-tool`chip::Controller::DeviceCommissioner::ReleaseCommissioneeDevice(this=0x0000000108d11900, device=0x0000000107915e80) at CHIPDeviceController.cpp:560:35
    frame #3: 0x0000000102265d64 chip-tool`chip::Controller::DeviceCommissioner::OnDiscoveredDeviceOverBleSuccess(appState=0x0000000108d11900, connObj=0x000000010bf953c0) at CHIPDeviceController.cpp:795:15

Now why we end up doing CloseAllBleConnections from establishing a BLE connection I don't know, but until we stop doing that, we can't cancel the actual connection that got established from there....  For now this gets us back to the known-good state we were in since 1.0.  Once we figure out what's going on with that bit and the shutdown issues https://github.com/project-chip/connectedhomeip/issues/27607 describes, we can put this back.


setNumberOfTileDownloadThreads should be static

Please make setNumberOfTileDownloadThreads static, so I could do:
OpenStreetMapTileProviderConstants.setNumberOfTileDownloadThreads(5);
Thank you.

great catch. fixed

Hey @spyhunter99 / @neilboyd , Can you let me know how I can do with current build..since these methods are not there anymore?

Configuration.getInstance().set....
See the upgrade guide in the wiki for more information


remove some legacy public dependency code from the resolver

These conflict reasons are no longer constructed, since we removed backtracking caused by public dependencies. Let's go ahead and remove them.
r? @epage

@bors r+

:pushpin: Commit 94acc285f4591a5ccb3d9ed64dfd8394366c37dd has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 94acc285f4591a5ccb3d9ed64dfd8394366c37dd with merge d899ce72ecff0a7486ca5efa5347f719e5a44214...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing d899ce72ecff0a7486ca5efa5347f719e5a44214 to master...


370 Fix release github action

Resolves #370

I tested this in the following commit by making a dummy job that just logs in using skopeo:
https://github.com/datastax/cass-operator/pull/371/commits/dca557989cc2bee8510f8537c8636ec48741dba3

I tested this in the following commit by making a dummy job that just logs in using skopeo:
https://github.com/datastax/cass-operator/pull/371/commits/dca557989cc2bee8510f8537c8636ec48741dba3


[QOL] Message Input Box Changes

Message Input Box should be cleared when a message is sent
Message Input Box should not remember previous sent messages
Support Unicode; "¯_(ツ)_/¯" cannot be sent due to ツ

Remembers previous messages

Input Box doesn't clear

Input Box doesn't support unicode
https://github.com/user-attachments/assets/bd2ef4d1-7666-4b28-a4ff-445328e151f7


OCPBUGS-24598: Dockerfile: remove tini-static

Both tini and tini-static are container in the same rpm and dnf installs both, but we use only tini. So here we zap tini-static to avoid it raising false alarms on fips compliance.

/jira refresh

/jira refresh

/label backport-risk-assessed

/label cherry-pick-approved

/lgtm

/cherry-pick release-4.12


adding azure devops extension in extension index

This checklist is used to make sure that common guidelines for a pull request are followed.

For new extensions:

[ ] My extension description/summary conforms to the Extension Summary Guidelines.

If this PR is for a new extension or change to an existing extension, use the following to try out the changes in this PR:
docker run -it microsoft/azure-cli:latest
export EXT=<NAME>
pip install --upgrade --target ~/.azure/cliextensions/$EXT "git+https://github.com/williexu/azure-cli-extensions.git@devops#subdirectory=src/$EXT&egg=$EXT"

@gauravsaralMs looks like the index change is passing, are you okay with me merging this?
You can also update your original PR if you wish; let me know.

@gauravsaralMs looks like the index change is passing, are you okay with me merging this?
You can also update your original PR if you wish; let me know.

@williexu : It will be great if we can merge this :)
Thanks :)


program crash

Hey bro,I got an issue here,I use UEViewer opend a pak file and randomly choosed an UE4 version for I don't know the true version is,the I double clicked a mesh,then it shows the follow error which I don't know what it is.

Files attached below.
thanks a lot
AK47.zip

This should be on the forum rather then here.
And what game your trying to get this from?

thanks bro,I just check the issues, right,here is not a good palce,I'll closed it then ;)


SCRIPT1010: Expected identifier  with IE 11

Bug description
with IE 11 the WebUI fails on  'Connecting to the Docker endpoint' .
Steps to reproduce the issue:

Open http://:9000 with IE11 (11.285.17134.0)

Technical details:
Portainer Version: 1.19.2

The issue here is with Compatibility Mode.
The screenshot shows it is running on IE7 which is quite old probably not supported by portainer (although I can't find what browser portainer supports).
Changing the Compatibility Mode to IE10 or above will fix the issue.

Thanks for the feedback @rishipuri
Closing this issue then as we do not plan to support old browser versions (we do not have a list of supported browsers yet).


Docker request: make boost source build first

Boost is slow .. Can we move this up to the top of the docker file?  Since it does not use apt, I think it can go first right after the MAINTAINER line.

Correction: the boost needs the compiler tools .. the way it is written it should probably stay where it is.
@peterwillcn thanks for updating the Dockerfile, this is really a life saver..


[SPARK-24214][SS]Fix toJSON for StreamingRelationV2/StreamingExecutionRelation/ContinuousExecutionRelation

What changes were proposed in this pull request?
We should overwrite "otherCopyArgs" to provide the SparkSession parameter otherwise TreeNode.toJSON cannot get the full constructor parameter list.
How was this patch tested?
The new unit test.

cc @brkyvz

Test build #90390 has started for PR 21275 at commit 6ec8d9a.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution/3056/
Test PASSed.

Merged build finished. Test PASSed.

LGTM! Pending tests

Test build #90390 has finished for PR 21275 at commit 6ec8d9a.

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

Merged build finished. Test PASSed.

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

Thanks! Merging to master and 2.3.


Update protocol version to 0.13

In protocol version 0.13 the 'S' Settings message no longer contains UTF8 data -- it can contain arbitrary data.
see also https://github.com/edgedb/edgedb/pull/3103

Also need to add support for the new cfg::memory type (basically an int64)


Update UG with import and priority commands

Codecov Report

Merging #163 into master will increase coverage by 0.27%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #163      +/-   ##
============================================
+ Coverage     51.84%   52.11%   +0.27%
- Complexity      564      566       +2
============================================
  Files           114      114
  Lines          2494     2502       +8
  Branches        305      307       +2
============================================
+ Hits           1293     1304      +11
+ Misses         1115     1110       -5
- Partials         86       88       +2

Impacted Files
Coverage Δ
Complexity Δ

...java/seedu/address/logic/commands/DoneCommand.java
80.55% <0.00%> (-5.16%)
10.00% <0.00%> (ø%)

src/main/java/seedu/address/ui/HelpWindow.java
0.00% <0.00%> (ø)
0.00% <0.00%> (ø%)

.../seedu/address/logic/parser/DoneCommandParser.java
100.00% <0.00%> (+100.00%)
2.00% <0.00%> (+2.00%)

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 9824112...b52c1c6. Read the comment docs.


Problem with unstable  go-sqlite3 version - 2.0.3

Hi,
We at the platform team of razorpay internally use bulk-insert which internally uses github.com/jinzhu/gorm v1.9.12 and creates an indirect dependency on github.com/mattn/go-sqlite3 v2.0.3.
Reference :- https://github.com/t-tiger/gorm-bulk-insert/blob/master/go.mod#L14
Now, this setup was working fine for us till last week and suddenly we had a failure in our docker build for github actions citing
<EMAIL_ADDRESS>unknown revision v2.0.3
We also saw one of your issues where you mentioned versions 2.0+ were unstable - issue
Did you stop supporting 2.0.3 version suddenly in the last 7-10 days. We were wondering what caused the breakage of the build from our side. It would be helpful if you could throw some light on this issue.
Thanks,
Shriram

One way to fix this is adding the below code to the go.mod file
exclude github.com/mattn/go-sqlite3 v2.0.3+incompatible

any fix ?

This is not an issue of go-sqlite3. v2 was an accident as written in  README.md

NOTE: The increase to v2 was an accident. There were no major changes or features.

@mattn I wonder if this would be a reason to use a retraction and just retag v2: https://golang.org/ref/mod#go-mod-file-retract
The impact of this is a bit broad. Large projects seem to have been impacted by this as well as small random odds and ends. Notice that tekton/cli was affected when I was trying to import it into my project. Also searching my cache I see gorm managed to get a commit with a v2 tag.
Can't imagine what else this might have landed in. A retraction seems like it would prevent tons of people from having to stuff exclude and replace into their module files, if I understand the mechanics of it correctly.

[protosam@nullhost]$ go mod init placebo
go: creating new go.mod: module placebo
[protosam@nullhost]$ go get<EMAIL_ADDRESS>go get<EMAIL_ADDRESS>updating to
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>requires
<EMAIL_ADDRESS>reading github.com/mattn/go-sqlite3/go.mod at revision v2.0.2: unknown revision v2.0.2

[protosam@nullhost]$ grep -ri 'mattn/go-sqlite3 v2' ~/go/pkg/mod/cache
<EMAIL_ADDRESS>github.com/mattn/go-sqlite3 v2.0.2+incompatible
<EMAIL_ADDRESS>github.com/mattn/go-sqlite3 v2.0.1+incompatible

If once you clean module cache on your environment, vertion 1.14 shold be used in next time.

That's not the case. People will be stumbling onto this for a while. go-sqlite3 is a very wide spread dependency and get added into other projects during both manual and automated tasks.
Commits like this and this are actively referenced in projects today.
There are 39,000 files that come up with I search to get an idea of how wide spread this is.

@protosam From what I understand, retracting the v2 tags won't resolve any of the existing issues. It just stops the issue from continuing the grow. If I have a dependency on some other module that in turn has a dependency on one of the broken v2 tags of this library, then go mod will still attempt to download that version. And unless you are using proxy.golang.org (or similar), it will fail. The only time retraction matters is when someone is explicitly upgrading their dependencies.
In other words, even if a retraction is published, someone would still have to go to every one of the broken dependents and fix their go.mod to reference a valid release. Then all affected developers have to go and update to the newer versions of these modules.
@mattn I'm guessing the reason this just become an issue recently is because the v2 tags were deleted from this repo. Is that correct? If so, would you be able to re-create them for the same commits? That way people using "direct" at least won't get failed builds. (This is orthogonal to retracting the v2 releases.)

Anyone know which commit should i tag ?

@mattn I'm looking into this.

Google had them cached in sum.golang.org and also they're still listed at pkg.go.dev.
v2.0.0+incompatible
v2.0.1+incompatible
v2.0.2+incompatible
v2.0.3+incompatible
I'm actually a bit confused on the serialization. Saying what I got in case someone else is able to understand deserializing this faster than I can.

v2.0.0 was not a tag. It was branch name.
v2.0.1
https://web.archive.org/web/20201202062638/https://github.com/mattn/go-sqlite3/releases/tag/v2.0.1
590d44c02bca83987d23f6eab75e6d0ddf95f644
v2.0.2
https://web.archive.org/web/20201202062638/https://github.com/mattn/go-sqlite3/releases/tag/v2.0.2
53cff3fcebd1e177d04129dc131523635bc45d3d
v2.0.3
https://web.archive.org/web/20201202060439/https://github.com/mattn/go-sqlite3/releases/tag/v2.0.3
9bdaffc12bf8be15afceb51bb60851edd4afdff5
v2.0.4
https://web.archive.org/web/20201202060440/https://github.com/mattn/go-sqlite3/releases/tag/v2.0.4
db4c9426f851c76327db11e1b5301e520e0e048b
v2.0.5
https://web.archive.org/web/20201202060440/https://github.com/mattn/go-sqlite3/releases/tag/v2.0.5
db4c9426f851c76327db11e1b5301e520e0e048b
v2.0.6
https://web.archive.org/web/20201202060441/https://github.com/mattn/go-sqlite3/releases/tag/v2.0.6
baaf8a978416040e7f2d00ac36e345098d0588d8

Should all tags be restored?

I restored older v2.0.X tags. How goes good?

So you (who used v2.0.X) should modify go.mod to switch v1.4.X.
require github.com/mattn/go-sqlite3 v1.14.9

The thousands of forks and archive.org are pretty useful, these commits look good to me and below I've tested them. They work as I expect.
I did some additional testing to see how the retraction will work. I don't think it works against legacy versioning. Ideally if it worked, we would be capable of getting a message out to the end users so they know they're using bad versions and later these versions can be gracefully claimed for reuse.
No idea where to go with that discovery though. =/
So v2.0.0, v2.0.1, v2.0.2, and v2.0.3 work because the +incompatible tag and there is not a go.mod file (legacy versioning).
Tags v2.0.4, v2.0.5, and v2.0.6 do not seem to be needed. These have go.mod versioning and yield errors that people would have to do more work than necessary to work around. They also don't show up in sum.golang.org and are not listed on pkg.go.dev. Seems likely that no one would miss these tags. This leads me to believe they've not been in use.

I'd probably reach out to the Go team at this point to see if they have any ideas to stop the spread and fix the problem (eg. remove these entries from sumdb? Dunno if that's possible/good idea)
Retracting would probably mean that you can't use these tags in the future.

This issue is already reported to Go team. https://github.com/golang/go/issues/35732

@mattn as far as I can tell that issue was closed with working as intended. I was rather suggesting to contact them about this specific case, hoping that they could remove the offending entries from the sumdb/proxy.

One way to fix this is adding the below code to the go.mod file exclude github.com/mattn/go-sqlite3 v2.0.3+incompatible

Thank you! This fixed my problem. When I ran go get<EMAIL_ADDRESS>it downgraded another library I'm using (ory/fosite) from 0.40.2 to 0.35.1. I then added this line to my go.mod and ran go get<EMAIL_ADDRESS>This upgraded the package without upgrading go-sqlite3 to the bad version.

I restored older v2.0.X tags. How goes good?

The tags are disappeared again :(

The 2.0.X was retracted.
https://pkg.go.dev/github.com/mattn/go-sqlite3?tab=versions

@mattn Even though you retracted those versions, those tags should never be deleted, so that people can continue to download their dependencies, including for older versions of their projects.

@rittneje Yes. My understanding is that once people manually revert to 1.4.X, they will not be upgraded thereafter since 2.X was retracted. I believe this is a problem that cannot be recovered automatically.

My point is that deleting those v2 tags breaks people's builds so we should not do that. We can only strongly discourage their use going forward (which the retraction helps).

I have no plans to release v2 any more.

But those tags were already released. So there are other libraries and projects that reference them. By deleting them, those versions cannot be built properly anymore (without using a Go module proxy), which was the original stated issue. We can tell people not to use v2 in new versions of their code anymore, but we should not cause the older/existing versions to break.

v2 was an accidental release because the Go mod incorrectly identified the branch name as a tag. https://github.com/mattn/go-sqlite3/pull/998 is a PR to add retract as a way to fix these problems.
https://github.com/mattn/go-sqlite3/pull/998

Retract doesn't really "fix" the problem per se. In fact, the problem is not really fixable in the way you are hoping. Once a version has been released, it should not be deleted. The retraction fixes some latent issues with fetching/upgrading via go get github.com/mattn/go-sqlite3@latest. However, if a project already references, say, v2.0.3 in its go.sum file, the retraction does not (and should not) interfere with that.
Typically people are using the default Go module proxy at proxy.golang.org. By design, this proxy does not allow versions to be deleted, so that you have eternal build reproducibility. This is an important feature for most people, as they expect all previous versions of their code to always work.
However, in the event that you are not using a proxy (GOPROXY=off) then it instead relies on the GitHub tag still existing. It is for this reason that the tags of this repo should be preserved.
My understanding is there were two issues in the history of this repo. The first is the existence of a branch named v2.0.0, which, due to an unfortunate bug in go mod, was misinterpreted as a release version. The second is a bunch of actual tags (v2.0.1, v2.0.2, etc.) that were released in error.

Yes, so I added note in README. https://github.com/mattn/go-sqlite3#go-sqlite3
I have not released v2 in other projects because I do not break compatibility. I also don't want to make it a hassle for the user. Fortunately, as far as I can see, many people still have v1. Because the transition to v2 and beyond is not automatic. So I decided to save the v1 users instead of the v2 users. Do you still think we should release v2.1.X or v3?
BTW, go get with fresh go.mod always get 1.4.X.

Do you still think we should release v2.1.X or v3?

I think you should continue releasing v1.X.Y, as you have been. (In the event you do decide to make breaking changes, going to v3 is probably best to have a clean break from v2.) However, the v2 tags that were already published before should continue to exist indefinitely, you just won't be releasing any new v2.X.Y tags.

BTW, go get with fresh go.mod always get 1.4.X.

Yes this is due to fixes in go mod itself as well as the retraction you did. But if you specifically mention v2.0.3 in your go.mod then it works despite the retraction.

I figured that leaving the v2 tag could be confusing to new users.

Yes this is due to fixes in go mod itself as well as the retraction you did. But if you specifically mention v2.0.3 in your go.mod then it works despite the retraction.

Yes, it's same with my understanding. Thanks.

The 2.0.X was retracted.
https://pkg.go.dev/github.com/mattn/go-sqlite3?tab=versions
You may have already had go-sqlite3 version 2.0.X. Please update manually to 1.4.X.

Indeed, I can update my code, but there are tons of 3rd party libs which require go-sqlite v2.x.x
Should I fork them all ?

I see that v2 was released by mistake and having legacy v2 and ongoing v1 is confusing.
But it seems that in order to fix that mistake you should keep v1 and v2 frozen and continue development as v3

I got the same problem but after I did go env -w GOPROXY="https://proxy.golang.org,direct" now it can download.

@mattn Deleting the v2.0.3 broke code that I hadn't needed to touch for years. Now when I try to use v1.14.9 I get this error for that code that worked fine before:
Binary was compiled with 'CGO_ENABLED=0', go-sqlite3 requires cgo to work. This is a stub

None of the logic I wrote works anymore and it used to. I just get empty values when I query now. How do I fix this?
https://github.com/drgrib/alfred-bear/blob/master/db/db.go#L172

@drgrib Are you getting an error, or an empty result set? How specifically are you compiling and executing your code? Have you tried with the latest release (1.14.16)? Also, what does go env say?
#855 is not fixable as the Go toolchain does not support that mode of operation. You must compile with CGO_ENABLED=1 every time.

I guess I'm technically not getting an error, just that message when I run along with empty result sets.
Here is my go env for a private test project which I am just running with go run
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/credford/Library/Caches/go-build"
GOENV="/Users/credford/Library/Application Support/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="arm64"
GOHOSTOS="darwin"
GOINSECURE=""
GOMODCACHE="/Users/credford/Drive/Files/go/pkg/mod"
GONOPROXY="github.com/drgrib/global_go,github.com/drgrib/settings,github.com/drgrib/global_go118"
GONOSUMDB="github.com/drgrib/global_go,github.com/drgrib/settings,github.com/drgrib/global_go118"
GOOS="darwin"
GOPATH="/Users/credford/Drive/Files/go"
GOPRIVATE="github.com/drgrib/global_go,github.com/drgrib/settings,github.com/drgrib/global_go118"
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_arm64"
GOVCS=""
GOVERSION="go1.18.3"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="0"
GOMOD="/Users/credford/Drive/Files/go/src/github.com/drgrib/global_go/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -arch x86_64 -m64 -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/f1/p6wb36jd1tl2hnn__v1dv2qr00zzr4/T/go-build2064737576=/tmp/go-build -gno-record-gcc-switches -fno-common"

The main file looks like this:
package main

import (
	"fmt"

	"github.com/drgrib/global_go/mac/bear"
)

func main() {
	fmt.Println(bear.NoteExistsByTitle("testify"))
}

The imported file looks like this:
package bear

import (
	"database/sql"
	"fmt"
	"strings"

	"github.com/mattn/go-sqlite3"
	"github.com/pkg/errors"

	"github.com/drgrib/global_go/comp"
)

const (
	DbPath = "~/Library/Group Containers/9K33E3U3T4.net.shinyfrog.bear/Application Data/database.sqlite"

	TitleKey  = "ZTITLE"
	TextKey   = "ZTEXT"
	TagsKey   = "group_concat(tag.ZTITLE)"
	NoteIDKey = "ZUNIQUEIDENTIFIER"

	NOTE_BY_TITLE = `
SELECT DISTINCT
	note.ZUNIQUEIDENTIFIER, note.ZTITLE
FROM
	ZSFNOTE note
WHERE
	note.ZARCHIVED=0
	AND note.ZTRASHED=0
	AND note.ZTEXT IS NOT NULL
	AND utflower(note.ZTITLE) LIKE utflower('%'||$1||'%')
ORDER BY case when utflower(note.ZTITLE) LIKE utflower('%'||$1||'%') then 0 else 1 end, note.ZMODIFICATIONDATE DESC
LIMIT 1
`

	createTemplate = "open bear://x-callback-url/create?title=%s&text=%s&show_window=yes&new_window=yes&edit=yes"
	openTemplate   = "open bear://x-callback-url/open-note?title=%s&show_window=yes&new_window=yes"
)

var (
	bearDB *LiteDB
)

// Only init bearDB if needed for a query so this package stays lightweight
// for other use cases.
func initBearDBIfNil() error {
	if bearDB == nil {
		var err error
		bearDB, err = NewBearDB()
		return err
	}
	return nil
}

type Note map[string]string

type LiteDB struct {
	db *sql.DB
}

func NewLiteDB(path string) (*LiteDB, error) {
	sql.Register("sqlite3_custom", &sqlite3.SQLiteDriver{
		ConnectHook: func(conn *sqlite3.SQLiteConn) error {
			return conn.RegisterFunc("utflower", utfLower, true)
		},
	})

	db, err := sql.Open("sqlite3_custom", path)
	litedb := LiteDB{db}
	return &litedb, errors.WithStack(err)
}

func utfLower(s string) string {
	return strings.ToLower(s)
}

func NewBearDB() (*LiteDB, error) {
	path := comp.Expanduser(DbPath)
	litedb, err := NewLiteDB(path)
	return litedb, err
}

func (litedb LiteDB) Query(q string, args ...interface{}) ([]Note, error) {
	results := []Note{}
	err := initBearDBIfNil()
	if err != nil {
		return results, err
	}

	rows, err := litedb.db.Query(q, args...)
	if err != nil {
		return results, errors.WithStack(err)
	}

	cols, err := rows.Columns()
	if err != nil {
		return results, errors.WithStack(err)
	}

	for rows.Next() {
		m := Note{}
		columns := make([]interface{}, len(cols))
		columnPointers := make([]interface{}, len(cols))
		for i := range columns {
			columnPointers[i] = &columns[i]
		}
		if err := rows.Scan(columnPointers...); err != nil {
			return results, errors.WithStack(err)
		}
		for i, colName := range cols {
			val := columnPointers[i].(*interface{})
			s, ok := (*val).(string)
			if ok {
				m[colName] = s
			} else {
				m[colName] = ""
			}
		}
		results = append(results, m)
	}
	err = rows.Close()
	if err != nil {
		return results, errors.WithStack(err)
	}
	err = rows.Err()
	if err != nil {
		return results, errors.WithStack(err)
	}
	return results, errors.WithStack(err)
}

func escape(s string) string {
	return strings.Replace(s, "'", "''", -1)
}

func (litedb LiteDB) NoteByTitle(title string) ([]Note, error) {
	title = escape(title)
	notes, err := litedb.Query(NOTE_BY_TITLE, title)
	return notes, err
}

// NoteByTitle returns best match note to title string.
func NoteByTitle(title string) (Note, error) {
	err := initBearDBIfNil()
	if err != nil {
		return nil, err
	}
	notes, err := bearDB.NoteByTitle(title)
	if err != nil {
		return nil, err
	}
	if len(notes) == 0 {
		return nil, nil
	}
	return notes[0], nil
}

// NoteIDByTitle returns best match note ID to title string.
func NoteIDByTitle(title string) (string, error) {
	note, err := NoteByTitle(title)
	if err != nil {
		return "", err
	}
	if note == nil {
		return "", nil
	}
	return note[NoteIDKey], nil
}

// NoteExistsByTitle returns true if a best match note ID to title string
// exists.
func NoteExistsByTitle(title string) (bool, error) {
	id, err := NoteIDByTitle(title)
	return id != "", err
}


machinesflaw-yazide

This is the machine's flaw, a little something trying to represent something trying to be a circle, but can't entirely be since it's lines and only lines.
Lastly, link a picture of your art piece here:

Closing this PR due to inactivity! Please create a new PR when you update your art!


Finish README

Build README up to be usable as an open source lib

I think this is in a pretty good place ATM, going to close


enhanced tracker pose calculation

it is known issue that in case of 3 or 4 cameras when one camera is losing bulb then we have tiny jump. this is caused by fact that position is calculated as average of individual interpolation of each available tracker pair. so if we have 3 trackers and we hide 1 then instead of
(p12+p23+p13)/3 we have (p12+p23)/2.
me and @zelmon64 had discussion about algorithm where we could correct error by
(p12+p23)/2 + err
where
err =  (p12'+p23'+p13')/3 - (p12'+p23')/2
and p12', p23' and p13' is some kind of interpolation of all tracker positions collected either during gameplay or calibration.
i did simple test of algorithm just remembering last point where I has all trackers and results were not bad. however when I moved away from point and then gained tracker it was not.
the simple algorithm could work like that but be active in only short distance while full algorithm could be more complex and collect points across whole game area and interpolate from points that are close enough to actual position also over whole area. so if user lost one tracker in one please, the position of the controller would be corrected all the time until all trackers.
second approach would be to extrapolate instead of interpolate from 5 points taken during mat calibration. for each point we can calculate err and potentially find a function that will calculate err in new point from calibration point err and distance from center of area.
here, we assume that it is unlikely to calibrate cameras so well that
(p12+p23+p13)/3 = (p12+p23)/2.
I would say its not possible but not sure.
@cboulay , @HipsterSloth ,
would you be so kind and give us your comments? what approach you would recommend? or there is alternative way.
Greg

I'll need to find some time to look this over.
However, I want to say that I think the next thing to modify in the optical tracker is to make each tracker have its own thread and behave asynchronously. This deserves its own issue and discussion so I won't outline it here. Once that work begins, pretty much any changes to the tracker will conflict so all such changes should be put on hold.

agree. this will introduce much conflict in code.
can you tell if orientation data will also go to separate thread? that would be really great if we could use maximum of it.
is this something that will be implemented in near future?

I wasn't planning on starting work on it until April. So I guess you have a couple weeks to make changes to the tracker code. But this particular issue would probably need a different approach once the threaded trackers are implemented so it's probably best to hold off.
By the way, take a look at Matlab's triangulatemultiview for triangulation with more than 2 cameras.

Note only that it is not to enhance triangulation but handle case when one camera does not track object. I don't see such concern in matlab fun.

I don't really understand the sub-scripting in your original post. Are the numbers after the p the camera IDs? If you drop from 3 cameras to 2, how do you still have p12 and p23?
The Matlab function gets a single 3D position from multiple cameras, without first calculating 3D positions from all pairs of cameras then averaging those. So, your (p12+p23+p13)/3 wouldn't exist, there would simply be p123. Then when one camera drops out it would be p12 (or p23).
As to whether or not you can construct an error model that describes the difference between all p123 and all p12 (or p23)... I don't know. I imagine it is very non-linear and difficult to describe analytically. Can you collect a bunch of data points across from your volume and share it with me? Each row in the table should have 5 columns per tracker: 2D-x, 2D-y, 3D-x, 3D-y, 3D-z. I can then try to visualize what the error is like if one camera drops out and if it is systematic. I only have 2 cameras so I can't do it.

U are right. I was too fast
If u have 3 cameras then either I have 3 interpolation or one.
I have idea how to visualise current error so will post video soon.

@cboulay I agree that it would probably be very non-linear. That is why I think we would need a lot of calibration points so that we could interpolate from the surrounding ones. I think it would turn the tracker pose calibration into something similar to how motion capture software move a calibration wand throughout the entire tracking space to calibrate.

Has anyone tested whether triangulation (dual or multicam) is in fact better than (weighted?) averaging of 3D positions from each camera? The answer to this question doesn't affect the current issue of how to compensate for a lost camera, but it does affect what baseline data and 3D position estimation method I/we use to build the error model.
@zelmon64 , depending on how many points are needed, the error model can become very large very quickly. Let's say you start with 4 cameras, you need 14 different error models (4@3cams; 6@2cams; 4@1cam).

I will make video and we will see how it behaves.
If model will be too complex then we can always collect points and interpolate. But it would be really many points...

I don't think averaging the conic fit 3d estimations (instead of averaging the triangulations) has been tried. It would be pretty straight forward to add an option for that. My gut says that it would feel since you'ld be averaging in more noise (z-noise of conic fit vs z-noise of camera transform error), but I would love to be proved wrong.

Was doing some random google searching for multi-camera triangulation and came accross this book posted online. Pasting here for reference:
http://cvrs.whu.edu.cn/downloads/ebooks/Multiple View Geometry in Computer Vision (Second Edition).pdf

@HipsterSloth With Matlab's triangulatemultiview algorithm, which was taken from the textbook you just linked, you wouldn't be 'averaging' triangulations anymore but it is a least-squares fit which I guess is similar.
But our triangulation (whether multiview or not) does rely on the center of gravity calculation for each camera which is itself is sort of a noisy average.
I think it's worth testing.

@cboulay It just occured to me that one advantage of averaging the conic fit results is that it wouldn't suffer from the singularity we get that triangulating opposing (or nearly opposing) cameras. It would be nice to eliminate the opposing camera filter. Also it would be nice to only have to do N averages instead of N*(N-1)/2 averages (not that N>4 is really practical for most people given USB bandwidth/processing restrictions).

I am lost. Will that help with this issue of losing tracker?


Duplicate UseCase for different view logic

Just a silly example with two view logic. If click the first button, it will display a dialog with the message "Say 'Yes' to XX users?", where XX is the count of current uses. And if click the second button, it will display a dialog with the message "Say 'No' to XX users?". Suppose we can click button 1 then click button 2 quickly, and display two dialogs at last. So dose it have to inject two 'Get count of user" UseCases with different callbacks or subscribers to the presenter? What about five, ten similar UseCases?

You can reuse code through inheritance or composition: always favor composition over inheritance.

@android10 Thanks. Yes, I can reuse code through composition. But for the special example, all I need is a simple  'Get count of user" UseCase. Is it true that it need two instances of the same UseCase for the two button click event?

Yes, you will be creating a new instance every time the user clicks the button ;)

Hi @android10 !
How can I use the composition in this case?
I have three interactors:
public class GetBusList extends UseCase {

    ...

    @Override
    protected Observable buildUseCaseObservable() {
       // return very big observable
    }

}

public class GetCarList extends UseCase {

    ...

    @Override
    protected Observable buildUseCaseObservable() {
       // return very big observable
    }

}

public class GetTrainList extends UseCase {

    ...

    @Override
    protected Observable buildUseCaseObservable() {
       // return very big observable
    }

}

I need do in fourth interactor:
Observable.zip(busObservable, carObservable, trainObservable, new Func3<List<Vehicle>, List<Vehicle>, List<Vehicle>, List<Vehicle>>() {
                                @Override
                                public List<Vehicle> call(List<Vehicle> busList,
                                                           List<Vehicle> carList,
                                                           List<Vehicle> trainList){
                                    ...
                                    return merged;
                                }
                            }

I need directly access to Observables in UseCase's here?


IsMemberAllowedToEditContent missing information

The command IsMemberAllowedToEditContent is missing information on what it does. Currently says {{ Fill IsMemberAllowedToEditContent Description }}

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

ID: 80326e44-6beb-8983-57ab-8333608c504b
Version Independent ID: 8962c0dc-72a3-208a-33de-6a89cd56b6fc
Content: Set-UnifiedGroup (ExchangePowerShell)
Content Source: exchange/exchange-ps/exchange/Set-UnifiedGroup.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@libach81, empty parameter descriptions are a known issue. See here for an explanation.
So, are you just pointing out that the description is empty, or do you have other information (content, blog posts, etc.) that this parameter is alive and working?

@libach81 Hope this comment is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

@lilbach81 Could IsMemberAllowedToEditContent control the group-level setting described here? https://office365itpros.com/2022/11/14/outlook-groups-folders-rules/#Group-Level_Setting


Complex items and optionality

Many things in 5e contain options, whereby the AE to activate depends on a choice made. This leads to two options for data:

Split each option out into a different Foundry item (and therefore a different button on the sheet)
Use a macro to create a pop-up querying which option the player would like to trigger

The latter is neater and more intuitive imo, but it might be slow if a player never uses a certain option. We need to agree how to handle this—and whether we are happy to accept 'half-complete' items until a general solution is found—because there's probably a fucctonne of items that it applies to

Only one item please imo. You're only importing one thing from plutonium, you only expect one thing. So needs to be a macro. But also how would you implement that macro, is there a template you'd need to use for every item like that, or can you structure the data such that the module/plutonium generates a standard macro from an array of options?

is there a template you'd need to use for every item like that
Midi QoL has a (non-AE) option to trigger a macro when an item is activated (i.e. clicked). Using Item Macro, we can bundle this macro with the item itself rather than import it into the normal macros directory.

I agree it would be nice to have all the popups be 'consistent' with each other in styling, but the issue is that the macro will invariably have more programming than just the popup. That is, once the popup appears, you need to write code to handle what each button does, and that has to be included in the same macro! I suppose in principle the popup could be triggered by a core Plutonium function with reliable behaviour, so the PAD-only, item-specific macro only needs to call the initial 'create modal' function and provide instructions for each result.
await plutonium.optionsPopup.create(
  "Body text <b>with HTML</b> and whatnot like.",
  "Button 1", "function1",
  "Button 2", "function 2"
);

function function1 {
  executeCommands();
}

function function2 {
  executeCommands();
}

function closePopup {
  execute Commands();
}

I agree, one item/feature in the game equals one item on the character sheet, so please use macros.  I personally do not see a reason to dictate code structure, format, or styling.

The reason to at least have a style guide is so other people can review the code easily, if it ever needs updates! This could be fixing a bug, an API change, Midi overhauling itself, etc.
The only requirements I'd like to 'enforce', to be clear, are:

Write comments (obvious)
No minified code unless the human-readable one is available somewhere else (see my post above)
Use the same pop-up formatting as everything else (which we can draft whether or not Giddy makes some Plutonium magic to make it easier; this is to provide a 'consistent' experience so users don't have to constantly reread every single pop-up because they're all phrased differently)

Whatever solution I end up cobbling together for jamming macros into proceedings, I'll make it eslint-able, so a minimum bar for code styling will be in place
Writing good code is a whole different kettle of fish, and (un)fortunately not machine-enforceable (yet 😓)

kinda made irrelevant by CPR/etc. managing it better than anything any of us clearly have the effort to maintain 😏


Add directive to handle custom template

Apply by put *iq-select2-template structural directive inside <iq-select2> tag.
3 property is assigned to TemplateRef context:

$item - Entity object
$id - Object Id
$index - Current Index

Request PR in case useful for others. Not sure is it a correct way to do it. Please advise
At least could give some idea to enhance this component

Hi! This is a really nice contribution! I think it is highly desirable to have some testing and also documentation (i just mean README.md) on how to use this feature, in order to publish a new version with it.
Is that possible for you? Will try to do it myself if not, but that won't be immediate.

Add testing and update README with some example to implement. Anything else just let me know.


Fix wrong variable name (pickle_name) in 1_notmnist.ipynb

When raise Exception at line 327, 'pickle_file' at line 328 is not predefined and raise error.
NameError: global name 'pickle_file' is not defined

Can one of the admins verify this patch?

I signed it!


Update cranelift to 0.45.1

Due to API changes in ModuleEnvironment, this also changes several lines of the implementation. This can be merged once a new version of cranelift is released with https://github.com/CraneStation/cranelift/pull/1125.

@sunfishcode can you make a 0.45.1 release so I can merge this? I'm trying to close #388.

The only thing blocking it from landing is a new cranelift release.

0.46.0 is out so if you want to change those Cargo.tomls in your PR then we can likely merge that instead of this one. Closing...

Great! Will do :)


Motion Detection roi

Hi all,
Thanks for nice work here.
I am testing with a device xiaomi : hi3518ev300 (hi3516ev200 family), jxf22, 16 MB nor flash, <IP_ADDRESS>-lite, openipc-hi3518ev300
I focus on "In-Camera Motion Detection" feature.
It is working by default (I use MQTT and FTP) but when I try "Regions of Interest" nothing works. Nothing triggered.
I try with whole region 0x0x1920x1080 and some part (half) but nothing.
And if I leave the field empty, it works.
Also I have to reboot between each try, as I noticed that the daemon does not restart properly : when I started, there are 2 processes /usr/sbin/motiondetection.sh, and when I do some update, it adds some process but never kills the existing one. Dont know if it is ok.

Please include your /etc/majestic.yaml file without sensitive information

Hi @widgetii
Here is the conf :
system:   buffer: 1024   staticDir: /var/www/majestic isp:   iqProfile: /etc/sensors/iq/f23.ini image:   mirror: true   flip: true   rotate: none   contrast: 50   hue: 50   saturation: 50   luminance: 50 osd:   enabled: true   template: "cam11-void | %F %T %Z" nightMode:   enabled: true   irCutPin1: 70   irCutPin2: 68   backlightPin: 54   dncDelay: 10 records:   enabled: false   path: /mnt/mmcblk0p1/%Y/%m/%d/%H/%M.mp4   maxUsage: 50 video0:   enabled: true   codec: h265   gopSize: 1 video1:   enabled: false jpeg:   enabled: true mjpeg:   size: 640x360   fps: 5   bitrate: 2048 audio:   enabled: false   volume: 70   srate: 8000   codec: pcm   outputEnabled: false   speakerPin: 55   speakerPinInvert: false   voiceEqualizer: common rtsp:   enabled: true   port: 554 hls:   enabled: false youtube:   enabled: false motionDetect:   enabled: true   visualize: true   debug: true   skipIn: 0x0x960x1080 ipeye:   enabled: false netip:   enabled: false   user: admin   password: 12345   port: 34567   snapshots: true   ignoreSetTime: false onvif:   enabled: false watchdog:   enabled: true   timeout: 30

It's not a valid YAML

I edit. There was formating error with github with leading spaces.

Checked your config on my camera, it works, in logs:
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@836      Motion detected in 21 regions, 992x370 -> [2584x1510]
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      1232,388	80,80
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      1400,564	272,114
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      1456,1350	120,96
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      2168,428	168,178
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      2064,404	512,258
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      1896,1374	200,120
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      1856,582	728,242
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      1704,548	64,106
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      1632,564	200,114
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      2336,1430	248,80
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      2456,614	64,104
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      1152,1462	104,48
21:11:20  <hi_motionDetect> [ mdetect] motion_detect_thread@830      1032,1252	320,154

Let's see yours

Hi, I ve made some tests again.
First I would says that ROI alone IS working. For example if I set to 1080x0x1920x1080 (my cam is 1920x1080), only right part of picture triggers the alarm.
But the EXCLUDE ROI does not work and that is the point here.
Example, if I understand correctly, putting 1080x0x1920x1080 to EXCLUDE ROI should ignore triggers in this zone, but it is not the case.
Sample logs :
May 14 00:39:31 openipc-hi3518ev300 user.info majestic[1054]: Motion detected in 1 regions, 1728x0 -> [1872x24]
May 14 00:39:31 openipc-hi3518ev300 user.info majestic[1054]: 1728,0    136,16
May 14 00:39:31 openipc-hi3518ev300 user.info majestic[1054]: Motion detected in 1 regions, 1728x0 -> [1864x16]
May 14 00:39:31 openipc-hi3518ev300 user.info majestic[1054]: 1728,0    136,8
May 14 00:39:31 openipc-hi3518ev300 user.info majestic[1054]: Motion detected in 1 regions, 1728x0 -> [1864x8]
May 14 00:39:41 openipc-hi3518ev300 user.info majestic[1054]: 1080,0    568,670
May 14 00:39:41 openipc-hi3518ev300 user.info majestic[1054]: Motion detected in 1 regions, 1080x0 -> [1648x670]
May 14 00:39:41 openipc-hi3518ev300 user.info majestic[1054]: 1080,0    568,630
May 14 00:39:41 openipc-hi3518ev300 user.info majestic[1054]: Motion detected in 1 regions, 1080x0 -> [1648x630]

Note that I do not have same logs as yours, I use "logread" command on my side.
And as always, I must reboot between each change of config which is not comfortable.

Region coordinates are set in format topX, topY, width, height. In your case 1080x0x1920x1080 looks like topX, topY, bottomX, bottomY coordinates, so it's out of image window size.

Hi @widgetii
Thanks for your precision.
Considering format topX, topY, width, height I changed my Region excluded to 960x0x960x1080 (I suppose to be the half right part), and I leave ROI empty.
But with this set, the cam triggers alarm no matter the real move region.
Some logs :
May 15 23:20:01 openipc-hi3518ev300 user.info majestic[1074]: Motion detected in 2 regions, 1040x400 -> [1592x834]
May 15 23:20:01 openipc-hi3518ev300 user.info majestic[1074]: 1040,400  8,434
May 15 23:20:01 openipc-hi3518ev300 user.info majestic[1074]: 1528,530  64,214

May 15 23:28:18 openipc-hi3518ev300 user.info majestic[1074]: Motion detected in 1 regions, 312x0 -> [336x514]
May 15 23:28:18 openipc-hi3518ev300 user.info majestic[1074]: 312,0     24,514

https://github.com/OpenIPC/majestic/issues/28#issuecomment-1776146635


Use debian as base image and bash for scripts

Alpine is much smaller but it suffers from severe DNS issues. It lacks
support for search domains and tries to resolve a dns name via all
configure nameservers and returns the first answer. Since we keep a
non-mesos dns server for backup, sometimes this one is faster and we get
NXDOMAIN for internal names.

https://github.com/gliderlabs/docker-alpine/issues/8
https://github.com/gliderlabs/docker-alpine/issues/11

/cc @brndnmtthws

Looks great to me. Has it been tested?

Yes I did some manual testing. Will deploy it to our OVH cluster to test it some more after merging.

This is embarrasses that alpine Linux need helps from Debian.


Cross-Country Mobility Symbology

In Chapter II of JP 2-01.3, Joint Intelligence Preparation of the Operational Environment (and several other publications), there are references to products of the IPB process, including cross-country mobility, mobility corridors, and others. These should be standardized and incorporated into MIL-STD-2525 (and APP-6).
Cross-country mobility:
Used to represent the trafficability of the terrain, usually:

Trafficable
Somewhat Trafficable
Untrafficable

Unrestricted
Restricted
Severely Restricted

Go
Slow-Go
No-Go

Green
Amber
Red

Clear
Diagonal Lines
Cross-Hatched Diagonal Lines

Mobility Corridors:
Used to represent canalization of the terrain, usually with either brackets or a line, denoted by echelon size.

JP 2-01.3

Hand-sketched cross-country mobility and mobility corridors
FYI:
@mepler @ottenw @llsjr2

IMHO, mobility corridors is a possibility.  I'll have to disagree with CCM and MCOO.  When created, both products include a legend.  Based upon a number of factors, the visual representation of speed/mobility prediction categories is different - there isn't a one size fits all.  I'd be more than happy to discuss this during a sidebar (with a whiteboard?) at the next SSMC which I believe is October in Leavenworth.

@mgoble - thoughts? Would you like a MIL-STD-2525 or ADP 1-02 approved-way of demonstrating CCM?
@ottenw - agreed on mobility corridors.

I believe a MIL-STD-2525 or ADP 1-02-approved way of demonstrating CCM would be a good idea. I understand we can not always symbolize MCOOs or CCMs to a standard. However I would definitely help to have a standard in MIL-STD-2525 or ADP 1-02 to use underlying support or foundation.


Paragraph "Network Security Group rules for subnets with private endpoints" should be changed

As we already have a new feature called network policies for private endpoints we should be able to apply nsg rules to PEs (reference: https://learn.microsoft.com/en-us/azure/private-link/disable-private-endpoint-network-policy?tabs=network-policy-portal#enable-network-policy)

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

ID: 1d6cc016-6c8f-81d7-3b5b-edce932294cf
Version Independent ID: 619d6b5e-ea75-61dd-5ef4-f653f9822cb8
Content: Use private endpoints - Azure Storage
Content Source: articles/storage/common/storage-private-endpoints.md
Service: storage
Sub-service: common
GitHub Login: @jimmart-dev
Microsoft Alias: jammart

@dinisgarcia
Thanks for your feedback! We will investigate and update as appropriate.

@dinisgarcia
Thanks for your contribution. Please add your ideas in below link, so our production team can review it and update the same.
Ideas · Community (azure.com)

Hi Saibaba,
This is the link for the general feedback page (what I see is below):
@.***
So not a link related to my feedback. My feedback is regarding changing a paragraph in the private link documentation. Are we supposed to post doc changes in that forum as well?
Cheers!
From: Saibaba Balapur Hireka @.>
Sent: Monday, October 3, 2022 6:47 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Dinis Garcia Nunes @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Paragraph "Network Security Group rules for subnets with private endpoints" should be changed (Issue #99279)
@dinisgarciahttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdinisgarcia&data=05|01|Dinis.Garcia%40microsoft.com|b77509b2ce0f43e4c8a508daa502c0b6|72f988bf86f141af91ab2d7cd011db47|1|0|638003728519737684|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=JUbqHj4%2BSTvq2S9e9xMY5CIQRixj%2BaKmE5uMEavCiuM%3D&reserved=0
Thanks for your contribution. Please add your ideas in below link, so our production team can review it and update the same.
Ideas * Community (azure.com)https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ffeedback.azure.com%2Fd365community&data=05|01|Dinis.Garcia%40microsoft.com|b77509b2ce0f43e4c8a508daa502c0b6|72f988bf86f141af91ab2d7cd011db47|1|0|638003728519737684|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=RLsNJI9x0CPhtkviDsMXetLqsCYWkT6AFdHsw6XljYI%3D&reserved=0

Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F99279%23issuecomment-1264964443&data=05|01|Dinis.Garcia%40microsoft.com|b77509b2ce0f43e4c8a508daa502c0b6|72f988bf86f141af91ab2d7cd011db47|1|0|638003728519737684|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=8yZ3BCT4eJVtqVCEWRRiv7LHA8MZqem3OH8E7KYnzWM%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAKZLWWZZDLLX72DRL3TPXJDWBJXO5ANCNFSM6AAAAAAQZSCQXQ&data=05|01|Dinis.Garcia%40microsoft.com|b77509b2ce0f43e4c8a508daa502c0b6|72f988bf86f141af91ab2d7cd011db47|1|0|638003728519737684|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=7QzKnmqX7z9PlYP3GHvrqb9UhEuWwzio2utaKEliFLs%3D&reserved=0.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@dinisgarcia
I'm going to assign this to the document author so they can take a look at it accordingly.
@jimmart-dev
Can you please check and add your comments on this doc update request as applicable.

Thank you for your dedication to our documentation.
We sincerely apologize for the delayed response. After a careful review, we are closing this issue. If you feel that the problem persists, please respond to this issue with additional information.
Please continue to provide feedback about the documentation. We appreciate your contributions to our community.
#please-close

Thanks for your dedication to our documentation.
We sincerely apologize for the delayed response. The requested updates have not been made since the creation of this issue, and the timeline for resolution may vary due to various constraints. Therefore, we've created an internal work item to incorporate your suggestions. We are closing this issue for now, but feel free to comment here as necessary.
#please-close


Trigger action by click confirm button

I want to trigger event only after I click confirm button or when the date-time-picker closed in dialog mode, is there anyway to achieve it?
Right now I am using (ngModelChange)="" in owl-date-time,  but changes were triggered every time when I change the date, min, and sec.   I don't want every change trigger a data query.
The former version 4.xx only update datetime after click confirm.  Wondering if you can do the same when showButtons set to ture.

Find onClose can do the job


Rendering difference between Chrome and Firefox

Hello,
I have a rendering issue with Firefox 50.0.1.
It's a schedule module pour our company.  The basic gui build on the server side (php).
Then, the data loaded by ajax request using jquery plugin (jquery.weekcalendar.js).
I tested earlier version of Firefox (38 and 47) and chrome (49), the rendering result was identical to the screen.  No error on the browser console.
Rarely, the Firefox 50 renders correctly the schedule (1 time on 50).  I repeat immediately the same action, and I obtain the wrong rendering.
It look like the css style is not loading during rendering or ignore by html2canvas to a certain degre.
If you have any tips, or clue,  I will be glad to test it.
Thanks and have a nice day.
Simon
Bad export on Firefox 50.0.1

Good export on Chrome 49

Is this still an issue with v1.0.0? If so, could you please share an example on jsfiddle.

Hi Niklasvh,  I dont work anymore for this company.  I will send an email to a friend who is still working there to check if they still have this problem.


[Security Analytics 2.x] Removed check for url since it differs with and without security

Description
The check for loaded URL doesn't account for security enabled, removed it since we have other check for the page content to verify the page loaded correctly
Issues Resolved
https://github.com/opensearch-project/security-analytics-dashboards-plugin/issues/690
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

should this target 2.10 first?


Using mdx in @next

I think many CRA users like myself are using mdx-js/mdx. The mdx docs for CRA setup use create-react-app-rewired, but I've managed just fine in CRA v1.x without ejecting or rewiring by inlining webpack loader and eslint overrides:
/* eslint-disable import/no-webpack-loader-syntax */
import Content from '!babel-loader!@mdx-js/loader!./Content.mdx';

I tried the same course of action in @2.0.0 but its not working for reasons I haven't looked into yet. (I'll leave details in a comment below. Raising at mdx-js may be appropriate.)
THE REASON I'm submitting this issue is to identify MDX usage as a likely reason for ejecting/rewiring in response to @Timer's comment https://github.com/timarney/react-app-rewired/issues/162#issuecomment-418708200. The future support outlook for rewired and missing workaround for CRA@next is unfortunate for MDX users.

The err I mentioned in OP:
Failed to compile.

./src/Content.mdx)
Syntax error<EMAIL_ADDRESS>Unexpected token (6:43)

  4 |
  5 |
> 6 | export default ({components, ...props}) => <MDXTag name="wrapper"  components={components}><MDXTag name="p" components={components}>{`hi`}</MDXTag></MDXTag>
    |                                            ^
  7 |

Not sure what's root cause... Odd to me the same inline-loader syntax in app code and same version of mdx-js/loader/mdx-js/mdx behaves differently in my CRA v1.x and CRA v2.0.0

@gaearon should we support this natively or via a babel macro?

Macro is nice if it means we don’t have to include MDX compiler by default.

We should ask for a @mdx-js/macro or mdx.macro pacakge!

hi! just browsing. i am not sure i understand what exactly the macro would solve for you since  @eckdanny-osi's original problem was that the  webpack loader inlining was broken. the macro won't be able to do anything to fix that. maybe we can open an issue over at @mdx-js and follow on from there.

original problem was that the webpack loader inlining was broken

Using the method displayed in OP is not supported by CRA and never expected to work.
MDX support will only be allowed via a Babel Macro, thus the suggestion.

hey guys. sry haven't checked back in on this convo in a while.
My project is back to using webpack's inline-loader syntax w/<EMAIL_ADDRESS>Only having *just discovered babel-plugin-macros when i 1st posted, I had hoped they would be enough escape hatch, but @sw-yx is right. My project could impl some one-off macros using @mdx-js/mdx (e.g.; parse and compile small snippets to JSX), but what we really need/want is to tap into the loader chain.
We were on react-scripts-cssmodules before CRA@2 shipped. I guess I imagined the path to support MDX in CRA and the developer end-user experience would be similar to the sass support story. (webpack plumbing is there for us, but we must add the compiler to use it like the CLI and docs say for sass)
If my project hits more walls we can't circumnavigate with inline-loader syntax, we'll likely eject or maintain a fork. Don't know how unique my situation is... am curious to what degree CRA users want mdx support tho

One issue with supporting MDX in the same way that SCSS is supported is that it's rare that you'll want to use vanilla MDX. At minimum, you're probably going to want to add plugins to improve typography, add emoji support, and handle front matter -- but you can go further and do things like add id props to titles for deep linking, generate a table of contents, etc.
I've tried putting together an MDX macro with all this, but can't find a way to get recompile-on-save working, which is a bummer.
I do have MDX working with CRA@2 though, using import('!babel-loader!mdx-loader!./tutorial/make-a-blog.md') and the following .babelrc:
{
  "presets": ["react-app"]
}

Even if this isn't supported, I feel like it's probably the most pragmatic approach atm.