Instantiate with default values while reopening cron editor

Using cron options to initialize, once reopened for second time cron editor is retaining the old selections.
How to reinitialize the default values available in cronOptions.
<cron-editor [(cron)]="cronExpression" [disabled]="isCronDisabled" [(options)]="cronOptions">

Duplicate of #33


New chrome bug

[Intervention] Unable to preventDefault inside passive event listener due to target being treated as passive. See https://www.chromestatus.com/features/5093566007214080

same on http://lab.cubiq.org/iscroll5/demos/barebone/ when open in 58.0.3029.110 (64-bit) chrome when open in its device toolbar

Yes,The new version of Google Chrome will have this error.

Same as this bug?
https://github.com/cubiq/iscroll/issues/1130

Also:
https://github.com/cubiq/iscroll/issues/1147

@d-scott Thank you~！


Rename node to component

Pull Request Description
For our users "Nodes" are called "Components". Which the users selects using the component browser. This MR just sets the text in the default workflow.
Important Notes
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[x] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[ ] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

Oops, standup should have been for #9002.


Move links to top right and format the css file

Wow this look so much better. Thanks you Mr. PM


UG

Codecov Report
Base: 70.82% // Head: 70.82% // No change to project coverage :thumbsup:

Coverage data is based on head (80bb5f7) compared to base (46810dc).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #278   +/-   ##
=========================================
  Coverage     70.82%   70.82%
  Complexity      716      716
=========================================
  Files           111      111
  Lines          2375     2375
  Branches        280      280
=========================================
  Hits           1682     1682
  Misses          588      588
  Partials        105      105

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Add a security policy

Hey there!
I belong to an open source security research community, and a member (@ready-research) has found an issue, but doesn’t know the best way to disclose it.
If not a hassle, might you kindly add a SECURITY.md file with an email, or another contact method? GitHub recommends this best practice to ensure security issues are responsibly disclosed, and it would serve as a simple instruction for security researchers in the future.
Thank you for your consideration, and I look forward to hearing from you!
(cc @huntr-helper)

Please contact me via<EMAIL_ADDRESS>Thanks

@tonyqus - thanks for your response. I found and used the e-mail on the GitHub organization if that is okay? Would you like me to still send you an e-mail to the address mentioned above?
For reference, you can see the report here. It is private and only accessible to maintainers.

Sorry, I don't wanna sign up your website. This is another kind of sales behavior.  If you do wanna help this project, please send the PDF or word document via email directly. Any external link behavior in email or this issue is not accepted. As you are a security guy, you should understand that external link is risky.


fix(next-sanity): add missing 'use client' directives

I could not get the mvp to run locally. These were the fixed I had to make. Most notable is the fix to the package itself where "use client" has been added to some client components.

Unfortunately rollup, which is used under the hood, doesn't support preserving these directives so it'll still be necessary to add them in the bundler even though we're also adding them to the src 😅

Good to know! I'll add them here as well.

Unfortunately rollup, which is used under the hood, doesn't support preserving these directives so it'll still be necessary to add them in the bundler even though we're also adding them to the src 😅

Good to know! I'll add them here as well.

I've now amended the commit to include the new files in that config.

Unfortunately rollup, which is used under the hood, doesn't support preserving these directives so it'll still be necessary to add them in the bundler even though we're also adding them to the src 😅

Good to know! I'll add them here as well.

I've now amended the commit to include the new files in that config.

Ooops, I meant the opposite ☺ the files currently declared in package.config.ts is the only locations we should be adding the directive. They need to match 1:1 otherwise the behavior of next dev inside this monorepo will behave and bundle wildly different than next dev in userland.
It'll also cause the Vercel deployments on this monorepo that uses next build to also have use client in different places.
The reason for this is that when rollup bundles it removes all directives it doesn't understand, and currently it only understands use strict

Ooops, I meant the opposite ☺ the files currently declared in package.config.ts is the only locations we should be adding the directive.

Got it! The PR is now much simpler.

Could you add use client to image/index as well? And use server' to server-actions/index? That way pnpm dev` behaves exactly like the code we publish to npm ✌

Could you add use client to image/index as well? And use server' to server-actions/index? That way pnpm dev` behaves exactly like the code we publish to npm ✌

Will do! Your overview here is impeccable. I apologise for all the hand-holding you need to make.

Could you add use client to image/index as well? And use server' to server-actions/index? That way pnpm dev` behaves exactly like the code we publish to npm ✌

Will do! Your overview here is impeccable. I apologise for all the hand-holding you need to make.

No need! Custom directives is novel and bleeding edge, we don't expect new joiners to understand how Next.js internals and React features yet to land in a stable release works within their first month on the team 😉

Could you change the commit prefix to "chore" btw? Since these changes only impact the monorepo and not the code we publish to npm 😌

Could you change the commit prefix to "chore" btw? Since these changes only impact the monorepo and not the code we publish to npm 😌

Haha, yes, I just thought about the same thing. No need to publish this change. I think I need coffee...


Make agApi observable

Rename 'gridOptions' > 'agOptions'
Rename 'gridApi' > 'agApi'

Excellent thank you. I like agOptions - happens to work very nicely with ag but I could imagine extending the theme with e.g. hc for  highcharts, bp for blueprint, etc. if we wanted to give that a try.


Add support for the todo tag

This is a request to support the @todo tag. Issue #201 and PR #214 provide insight into adding the code.
I suspect it'd use "label label-info" and only be visible if private methods/properties are also generated (they aren't by default). So, Public API mode hides them, Private API mode shows them. To be clear, that'd also mean not inserting todo tags in public methods by default.
Not sure if the above is the best approach, suggestions are encouraged.

Please see the pull request comments for details.


use property values for config when available

In https://github.com/pulumi/pulumi/pull/14273 we start passing through config values as PropertyValues.  Use those in pulumi-yaml, so we have proper type information that we can then use to process the config.
Fixes https://github.com/pulumi/pulumi-yaml/issues/453.

I think this is ready for a review, though CI unfortunately won't pass before we release a pulumi version that includes https://github.com/pulumi/pulumi/commit/80acb16a54efeea47f1f93b724333a44ff3ebd43, as I don't think we currently have a good way to install a non-released version of pulumi.  If we do I'd be happy to change to using that though.


About npy transformes png

Hello, in the process of my reproduction, can the npy generated in the cam_adv_mask file be converted into png for CAM visualization, can you provide the relevant code!

Hello, in the process of my reproduction, can the npy generated in the cam_adv_mask file be converted into png for CAM visualization, can you provide the relevant code!

Hello! I was wondering if you have resolved this issue? I've encountered the same problem and would greatly appreciate it if you could share your solution. Thank you very much!


Support and utilize new (upcoming) Mesos protobuf specification for external volume consumption

dependent on Mesos publication and release of protobuf spec

published in v0.4.2


Bump STM32H7 HAL to version 0.15

This PR bumps the STM32H7 HAL crate to 0.15.
There doesn't appear to be any breaking changes for this release.

@nullobject FYI I released a new version of the library with your changes https://github.com/zlosynth/daisy/releases/tag/v0.9.0


Deprecate/replace 'master.' properties with 'manager.'. (fixes #1640)

Rename all 'master.' properties to 'manager.'
Add utility to rename deprecated properties. This utility allows the
deprecated names to remain in the site configuration file and be used
against zookeeper by performing the following actions:

Rename deprecated properties when read into the site configuration
(and emit a warning about their use)
Rename deprecated properties when used to set or remove properties
in Zookeeper (and emit a warning about their use)

Rename deprecated properties to their new name in Zookeeper as a part
of the accumulo 2 -> 2.1 upgrade.

I'm probably missing some documentation here. Any pointers on where I need to add/update docs are welcome.

@keith-turner, after some feedback from and discussions with @ctubbsii we ended up changing the approach some. It's a little less general, but there were going to be some problems in dealing setting table-specific and namespace-specific properties that it just didn't seem like were worth it given that we don't have a use case for changing table-specific properties. Can you have another look and make sure you're still ok with the changes?

@keith-turner, after some feedback from and discussions with @ctubbsii we ended up changing the approach some. It's a little less general, but there were going to be some problems in dealing setting table-specific and namespace-specific properties that it just didn't seem like were worth it given that we don't have a use case for changing table-specific properties. Can you have another look and make sure you're still ok with the changes?

@brianloss Assuming you're the one who will merge this in the end, don't forget to clean up the commit log message subject and body when squashing/merging. Some suggestions to include in that cleanup:

If you merge from the GitHub UI (which I recommend), GitHub will automatically append (#1873) to the end of the subject line (which is very helpful and should be preserved). If you merge manually from your CLI, then you should add that manually so there is a reference back to this PR from the git history.
The (fixes #1640) portion of the subject that you added to the initial commit can be moved to the body of the commit log message.
Most of the commit messages in my contributions to this PR were only useful in comparison to what they were amending. They won't be useful in the final commit, so they should be excluded. (though, feel free to preserve any 'co-authored-by' lines if you wish.
The end result should be a single commit with a commit message that just describes what that one commit changes, and not all the intermediate stuff that occurred during the PR / code review. By default, GitHub's UI will concatenate the log messages from every commit in this PR when it squashes... but that will create a monstrosity of a log message that will not be very friendly in future. Luckily, it also gives an opportunity to edit the message before submitting the squashed commit. Editing the message down to just what the final commit actually does will be more useful as a summary for future git archeological tasks.

@brianloss Assuming you're the one who will merge this in the end, don't forget to clean up the commit log message subject and body when squashing/merging. Some suggestions to include in that cleanup:

If you merge from the GitHub UI (which I recommend), GitHub will automatically append (#1873) to the end of the subject line (which is very helpful and should be preserved). If you merge manually from your CLI, then you should add that manually so there is a reference back to this PR from the git history.
The (fixes #1640) portion of the subject that you added to the initial commit can be moved to the body of the commit log message.
Most of the commit messages in my contributions to this PR were only useful in comparison to what they were amending. They won't be useful in the final commit, so they should be excluded. (though, feel free to preserve any 'co-authored-by' lines if you wish.
The end result should be a single commit with a commit message that just describes what that one commit changes, and not all the intermediate stuff that occurred during the PR / code review. By default, GitHub's UI will concatenate the log messages from every commit in this PR when it squashes... but that will create a monstrosity of a log message that will not be very friendly in future. Luckily, it also gives an opportunity to edit the message before submitting the squashed commit. Editing the message down to just what the final commit actually does will be more useful as a summary for future git archeological tasks.

@ctubbsii, it's all merged. Unfortunately the first time I tried to merge GitHub failed and told me I had to refresh the page. When I tried again, I forgot to remove the fixes marker from the commit title, but did follow your other suggestions.
Thanks for all of the feedback, help, and willingness to engage in debate over this issue.

@ctubbsii, it's all merged. Unfortunately the first time I tried to merge GitHub failed and told me I had to refresh the page. When I tried again, I forgot to remove the fixes marker from the commit title, but did follow your other suggestions.
Thanks for all of the feedback, help, and willingness to engage in debate over this issue.

@ctubbsii, it's all merged. Unfortunately the first time I tried to merge GitHub failed and told me I had to refresh the page.

No problem. BTW, @keith-turner had the experience where a merge failed on GitHub, and he was offered the "retry" option. However, the "retry" converted his squash merge to a merge commit, leaving in some intermediate commits that he didn't want. I mention this in case it happens to you in future, it's best to avoid the "retry" option if one is presented by GitHub. Refreshing the page and trying again from the beginning definitely seems safer than an automatic "retry" option. Perhaps GitHub fixed that? Personally, I haven't seen this failure from GitHub (yet).

@ctubbsii, it's all merged. Unfortunately the first time I tried to merge GitHub failed and told me I had to refresh the page.

No problem. BTW, @keith-turner had the experience where a merge failed on GitHub, and he was offered the "retry" option. However, the "retry" converted his squash merge to a merge commit, leaving in some intermediate commits that he didn't want. I mention this in case it happens to you in future, it's best to avoid the "retry" option if one is presented by GitHub. Refreshing the page and trying again from the beginning definitely seems safer than an automatic "retry" option. Perhaps GitHub fixed that? Personally, I haven't seen this failure from GitHub (yet).


Lost files ...

Hello,
I have OnlyOffice Document Server version 4.4.3-7 installed on Ubuntu Server 16.04 LTS.
This is integrated with my owncloud version 10.0.2 with app OnlyOffice versione 1.1.6.
Today my all xlsx documents are empty.
I see thath onlyoffice document server never update my physical files in the owncloud, but I think save xlsx files only on the document server.
I need to restore files ...
Can you help me ?
Thanks
Manuel

Hello @ManuelRighi,
Could you please send us an email to<EMAIL_ADDRESS>Please send us a screenshot of ONLYOFFICE address settings in OwnCloud administrator section. Specify also if there were any errors when you had saved address settings after having entered the address of the document server. We look forward to your reply in our support system.

Thanks Alesander, I send email now.
Manuel

Hello @ManuelRighi,
As we have answered you in our support system helpdesk.onlyoffice.com, unfortunately, there is no possibility to restore those files.
The reason of the problem, as we can see in the logs, that there was no connection with the document server, because address settings were not saved and applied from the very beginning.


Clearing Historical Data

How can deployed history processes and history instances be cleaned up using this exporter

The exporter is not designed to store data for a longer period. By default, it uses a Hazelcast ring-buffer to store the data. The ring-buffer has a fixed capacity (default: 10000). If the capacity is reached then the oldest entries are overridden.
It is also possible to configure a time-to-live for the entries.
Does this answer your question?

I'm closing this issue because of inactivity. Feel free to reopen if the issue is still relevant.


Advanced Duplicator - Menu Issue?

The issue that I have playing on a certain server, it appears that the GUI for the tool becomes inaccessible as it shows a little box in the top left, with this error in console:
[advdupe2] addons/advdupe2/lua/advdupe2/file_browser.lua:1121: attempt to index a nil value

UpdateClientFiles - addons/advdupe2/lua/advdupe2/file_browser.lua:1121
Init - addons/advdupe2/lua/advdupe2/file_browser.lua:1148
3. oldFunc - lua/includes/extensions/client/panel/scriptedpanels.lua:37
4. Create - addons/eprotect_1.1.2/lua/e_protect/client/cl_overrides.lua:8
5. BuildCPanel - addons/advdupe2/lua/weapons/gmod_tool/stools/advdupe2.lua:959
6. unknown - addons/advdupe2/lua/weapons/gmod_tool/stools/advdupe2.lua:1518

Timer Failed<EMAIL_ADDRESS>(line 1520)]
[advdupe2] addons/advdupe2/lua/advdupe2/file_browser.lua:1050: attempt to index field 'Help' (a nil value)

unknown - addons/advdupe2/lua/advdupe2/file_browser.lua:1050 (x2)

Another addon on the server broke it

Do you know what add-on or type of add-on that may cause this issue?

No, you just have to disable them until you find it. Typically the fastest way is to disable half your addons and if the problem stays then it was the other half. Disable half of those and repeat till you found the bad one.


add links to into page

:tada: This PR is included in version 1.0.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


bug

Hi I'm trying nCAT last release with 3.4.24 Flex 6400M software and last release of Hamlib.
rigctl -m2 -r <IP_ADDRESS>:4532 fails with IO error

sometimes it works...but then suddendly stops and remains in
12:16PM INF Waiting for station station=Flex


Suggestion: Order files and tabs by the same parameters precedence

Hi,
I need to opens a file sequence in same order from type from terminal.

VSCode Version:

Versão 1.16.0-insider
Confirmação f980319f5c4bf3f0878c5fcc68a3aa2795119c57
Data 2017-08-08T05:10:13.016Z
Shell 1.6.6
Renderizador 56.0.2924.87
Nó 7.4.0
Arquitetura x64

OS Version:

DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=17.10
DISTRIB_CODENAME=artful
DISTRIB_DESCRIPTION="Ubuntu Artful Aardvark (development branch)"

Linux wellington-Inspiron-3647 4.11.0-10-generic #15-Ubuntu SMP Thu Jun 29 15:03:41 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux

Steps to Reproduce:

Try open multiple files from terminal:
Like:  code-insiders  $( echo {0000607..0000624}.sql |sort --numeric-sort )
Or: code-insiders 0000607.sql 0000608.sql 0000609.sql 0000610.sql 0000611.sql 0000612.sql 0000613.sql 0000614.sql 0000615.sql 0000616.sql 0000617.sql 0000618.sql 0000619.sql 0000620.sql 0000621.sql 0000622.sql 0000623.sql 0000624.sql
I expected to files opened in tabs and at menu in numeric order.

Reproduces without extensions: Yes/No

This feature request will not be considered in the next 6-12 months roadmap and as such will be closed to keep the number of issues we have to maintain actionable. Thanks for understanding and happy coding!


DROP DATABASE not possible: database is still in use

Environment
To diagnose, we usually need to know the following, including version numbers.  On Windows, be
sure to specify 32-bit Python or 64-bit:

Python: 3.8.0
pyodbc: 4.0.30
OS: Windows Server 2012
DB: SQL Server 2012
driver: ODBC Driver 17 for SQL Server

Issue
As a part of my unittest procedure, a database needs to be created in a SetUp function and dropped in the TearDown function of the same unittest instance. I am running into errors when trying to drop the database.
The code can be simplified to the following lines that can be executed alone:
self.project_name = "FE0000001035_Python_Testcase_BPwithoutBU"
self.connection_string = r'Driver={{{}}}; Server={},{}; Database={}; Trusted_Connection=yes;' \
                                .format("ODBC Driver 17 for SQL Server", self.conf_host, self.conf_port,"Master_db")
self.project_conn_string = r'Driver={{{}}}; Server={},{}; Database={}; Trusted_Connection=yes;' \
                                .format("ODBC Driver 17 for SQL Server", self.conf_host, self.conf_port, self.project_name)

# read from the database
with pyodbc.connect(self.project_conn_string, autocommit=True) as conn:
    query = """ SELECT * FROM [import].[preJournal] """
    cursor = conn.cursor()
    cursor.execute(query)
    result = list(cursor.fetchall())
    conn.close()

#drop the database
with pyodbc.connect(self.connection_string, autocommit=True) as conn:
    cursor = conn.cursor()
    query_drop= """  drop database """ + self.project_name
    cursor.execute(query_drop)
    conn.close()

The database drop doesn't happen as the connection still seems to be open. Following error is displayed:
pyodbc.ProgrammingError: ('42000', '[42000] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Cannot drop database "FE0000001035_Python_Testcase_BPwithoutBU" because it is currently in use. (3702) (SQLExecDirectW)')

ODBC Trace:
20200421SQL_backup.LOG

Connection pooling is keeping the original connection open even after the application has closed it. Turn it off with pyodbc.pooling = False before making connections.

It may help to put the database into single user mode first:
ALTER DATABASE [database_name] SET SINGLE_USER ROLLBACK IMMEDIATE;
DROP DATABASE [database_name];

https://docs.microsoft.com/en-us/sql/t-sql/statements/drop-database-transact-sql?view=sql-server-ver15#limitations-and-restrictions

Disabling the connection pooling helped indeed. Thank you guys for the quick help!


pygments 2.7.0 removed unirange

As of 3 days ago, pygments 2.7.0 removed the unirange function from pygments.utils, thus causing "cannot import name 'unirange'" errors.
Also, all "u" string prefixes were removed as all Python builds from 3.3+ are wide unicode compatible. https://github.com/pygments/pygments/pull/1536
I'm working on a PR for a fix now.

Whoa. Thanks Robert!


Error on deployment using Zeek version 7.0.4

Thank you for your support and contributions to the Zeek community.  We've been using this Ransomware detection plugin for a few years now.  However, we've run into an issue recently.
When deploying on Zeek version 7+, we are receiving the following error.
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 88: no such field in record (checkforransomwarefilenames::rec?$tx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 88: no such field in record (checkforransomwarefilenames::rec?$rx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 90: no such field in record (checkforransomwarefilenames::rec$tx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 90: target to iterate over must be a table, set, vector, or string (checkforransomwarefilenames::rec$<error>)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 92: no such field in record (checkforransomwarefilenames::rec$conn_uids)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 92: target to iterate over must be a table, set, vector, or string (checkforransomwarefilenames::rec$<error>)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 94: no such field in record (checkforransomwarefilenames::rec$rx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 94: target to iterate over must be a table, set, vector, or string (checkforransomwarefilenames::rec$<error>)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 90: undeclared variable (checkforransomwarefilenames::tx_host)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 94: undeclared variable (checkforransomwarefilenames::rx_host)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 92: undeclared variable (checkforransomwarefilenames::cuid)
error in /opt/zeek/share/zeek/base/frameworks/notice/main.zeek, lines 67-179 and /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, lines 96-98: incompatible record types (Notice::Info and [$note=Ransomware::KnownBadFilename, $msg=fmt(Detected potential ransomware! Known bad file name: %s in use by client %s on file server %s, checkforransomwarefilenames::rec$filename, checkforransomwarefilenames::tx_host, checkforransomwarefilenames::rx_host), $src=checkforransomwarefilenames::tx_host, $dst=checkforransomwarefilenames::rx_host, $uid=checkforransomwarefilenames::cuid])
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, lines 96-98 and /opt/zeek/share/zeek/base/frameworks/notice/main.zeek, lines 67-179: type mismatch ([$note=Ransomware::KnownBadFilename, $msg=fmt(Detected potential ransomware! Known bad file name: %s in use by client %s on file server %s, checkforransomwarefilenames::rec$filename, checkforransomwarefilenames::tx_host, checkforransomwarefilenames::rx_host), $src=checkforransomwarefilenames::tx_host, $dst=checkforransomwarefilenames::rx_host, $uid=checkforransomwarefilenames::cuid] and Notice::Info)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, lines 96-98: argument type mismatch in function call (NOTICE([$note=Ransomware::KnownBadFilename, $msg=fmt(Detected potential ransomware! Known bad file name: %s in use by client %s on file server %s, checkforransomwarefilenames::rec$filename, checkforransomwarefilenames::tx_host, checkforransomwarefilenames::rx_host), $src=checkforransomwarefilenames::tx_host, $dst=checkforransomwarefilenames::rx_host, $uid=checkforransomwarefilenames::cuid]))

manager scripts failed.
warning in /opt/zeek/share/zeek/policy/tuning/defaults/__load__.zeek, line 1: deprecated script loaded from /opt/zeek/share/zeek/site/local.zeek:13 "Remove in v7.1 The policy/tuning/defaults package is deprecated. The options set here are now the defaults for Zeek in general.";
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 88: no such field in record (checkforransomwarefilenames::rec?$tx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 88: no such field in record (checkforransomwarefilenames::rec?$rx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 90: no such field in record (checkforransomwarefilenames::rec$tx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 90: target to iterate over must be a table, set, vector, or string (checkforransomwarefilenames::rec$<error>)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 92: no such field in record (checkforransomwarefilenames::rec$conn_uids)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 92: target to iterate over must be a table, set, vector, or string (checkforransomwarefilenames::rec$<error>)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 94: no such field in record (checkforransomwarefilenames::rec$rx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 94: target to iterate over must be a table, set, vector, or string (checkforransomwarefilenames::rec$<error>)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 90: undeclared variable (checkforransomwarefilenames::tx_host)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 94: undeclared variable (checkforransomwarefilenames::rx_host)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 92: undeclared variable (checkforransomwarefilenames::cuid)
error in /opt/zeek/share/zeek/base/frameworks/notice/main.zeek, lines 67-179 and /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, lines 96-98: incompatible record types (Notice::Info and [$note=Ransomware::KnownBadFilename, $msg=fmt(Detected potential ransomware! Known bad file name: %s in use by client %s on file server %s, checkforransomwarefilenames::rec$filename, checkforransomwarefilenames::tx_host, checkforransomwarefilenames::rx_host), $src=checkforransomwarefilenames::tx_host, $dst=checkforransomwarefilenames::rx_host, $uid=checkforransomwarefilenames::cuid])
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, lines 96-98 and /opt/zeek/share/zeek/base/frameworks/notice/main.zeek, lines 67-179: type mismatch ([$note=Ransomware::KnownBadFilename, $msg=fmt(Detected potential ransomware! Known bad file name: %s in use by client %s on file server %s, checkforransomwarefilenames::rec$filename, checkforransomwarefilenames::tx_host, checkforransomwarefilenames::rx_host), $src=checkforransomwarefilenames::tx_host, $dst=checkforransomwarefilenames::rx_host, $uid=checkforransomwarefilenames::cuid] and Notice::Info)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, lines 96-98: argument type mismatch in function call (NOTICE([$note=Ransomware::KnownBadFilename, $msg=fmt(Detected potential ransomware! Known bad file name: %s in use by client %s on file server %s, checkforransomwarefilenames::rec$filename, checkforransomwarefilenames::tx_host, checkforransomwarefilenames::rx_host), $src=checkforransomwarefilenames::tx_host, $dst=checkforransomwarefilenames::rx_host, $uid=checkforransomwarefilenames::cuid]))

proxy-1 scripts failed.
warning in /opt/zeek/share/zeek/policy/tuning/defaults/__load__.zeek, line 1: deprecated script loaded from /opt/zeek/share/zeek/site/local.zeek:13 "Remove in v7.1 The policy/tuning/defaults package is deprecated. The options set here are now the defaults for Zeek in general.";
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 88: no such field in record (checkforransomwarefilenames::rec?$tx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 88: no such field in record (checkforransomwarefilenames::rec?$rx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 90: no such field in record (checkforransomwarefilenames::rec$tx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 90: target to iterate over must be a table, set, vector, or string (checkforransomwarefilenames::rec$<error>)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 92: no such field in record (checkforransomwarefilenames::rec$conn_uids)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 92: target to iterate over must be a table, set, vector, or string (checkforransomwarefilenames::rec$<error>)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 94: no such field in record (checkforransomwarefilenames::rec$rx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 94: target to iterate over must be a table, set, vector, or string (checkforransomwarefilenames::rec$<error>)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 90: undeclared variable (checkforransomwarefilenames::tx_host)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 94: undeclared variable (checkforransomwarefilenames::rx_host)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 92: undeclared variable (checkforransomwarefilenames::cuid)
error in /opt/zeek/share/zeek/base/frameworks/notice/main.zeek, lines 67-179 and /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, lines 96-98: incompatible record types (Notice::Info and [$note=Ransomware::KnownBadFilename, $msg=fmt(Detected potential ransomware! Known bad file name: %s in use by client %s on file server %s, checkforransomwarefilenames::rec$filename, checkforransomwarefilenames::tx_host, checkforransomwarefilenames::rx_host), $src=checkforransomwarefilenames::tx_host, $dst=checkforransomwarefilenames::rx_host, $uid=checkforransomwarefilenames::cuid])
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, lines 96-98 and /opt/zeek/share/zeek/base/frameworks/notice/main.zeek, lines 67-179: type mismatch ([$note=Ransomware::KnownBadFilename, $msg=fmt(Detected potential ransomware! Known bad file name: %s in use by client %s on file server %s, checkforransomwarefilenames::rec$filename, checkforransomwarefilenames::tx_host, checkforransomwarefilenames::rx_host), $src=checkforransomwarefilenames::tx_host, $dst=checkforransomwarefilenames::rx_host, $uid=checkforransomwarefilenames::cuid] and Notice::Info)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, lines 96-98: argument type mismatch in function call (NOTICE([$note=Ransomware::KnownBadFilename, $msg=fmt(Detected potential ransomware! Known bad file name: %s in use by client %s on file server %s, checkforransomwarefilenames::rec$filename, checkforransomwarefilenames::tx_host, checkforransomwarefilenames::rx_host), $src=checkforransomwarefilenames::tx_host, $dst=checkforransomwarefilenames::rx_host, $uid=checkforransomwarefilenames::cuid]))

worker-ens192-1-1 scripts failed.
warning in /opt/zeek/share/zeek/policy/tuning/defaults/__load__.zeek, line 1: deprecated script loaded from /opt/zeek/share/zeek/site/local.zeek:13 "Remove in v7.1 The policy/tuning/defaults package is deprecated. The options set here are now the defaults for Zeek in general.";
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 88: no such field in record (checkforransomwarefilenames::rec?$tx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 88: no such field in record (checkforransomwarefilenames::rec?$rx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 90: no such field in record (checkforransomwarefilenames::rec$tx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 90: target to iterate over must be a table, set, vector, or string (checkforransomwarefilenames::rec$<error>)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 92: no such field in record (checkforransomwarefilenames::rec$conn_uids)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 92: target to iterate over must be a table, set, vector, or string (checkforransomwarefilenames::rec$<error>)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 94: no such field in record (checkforransomwarefilenames::rec$rx_hosts)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 94: target to iterate over must be a table, set, vector, or string (checkforransomwarefilenames::rec$<error>)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 90: undeclared variable (checkforransomwarefilenames::tx_host)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 94: undeclared variable (checkforransomwarefilenames::rx_host)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, line 92: undeclared variable (checkforransomwarefilenames::cuid)
error in /opt/zeek/share/zeek/base/frameworks/notice/main.zeek, lines 67-179 and /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, lines 96-98: incompatible record types (Notice::Info and [$note=Ransomware::KnownBadFilename, $msg=fmt(Detected potential ransomware! Known bad file name: %s in use by client %s on file server %s, checkforransomwarefilenames::rec$filename, checkforransomwarefilenames::tx_host, checkforransomwarefilenames::rx_host), $src=checkforransomwarefilenames::tx_host, $dst=checkforransomwarefilenames::rx_host, $uid=checkforransomwarefilenames::cuid])
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, lines 96-98 and /opt/zeek/share/zeek/base/frameworks/notice/main.zeek, lines 67-179: type mismatch ([$note=Ransomware::KnownBadFilename, $msg=fmt(Detected potential ransomware! Known bad file name: %s in use by client %s on file server %s, checkforransomwarefilenames::rec$filename, checkforransomwarefilenames::tx_host, checkforransomwarefilenames::rx_host), $src=checkforransomwarefilenames::tx_host, $dst=checkforransomwarefilenames::rx_host, $uid=checkforransomwarefilenames::cuid] and Notice::Info)
error in /opt/zeek/share/zeek/site/packages/detect-ransomware-filenames/check-for-ransomware-filenames.zeek, lines 96-98: argument type mismatch in function call (NOTICE([$note=Ransomware::KnownBadFilename, $msg=fmt(Detected potential ransomware! Known bad file name: %s in use by client %s on file server %s, checkforransomwarefilenames::rec$filename, checkforransomwarefilenames::tx_host, checkforransomwarefilenames::rx_host), $src=checkforransomwarefilenames::tx_host, $dst=checkforransomwarefilenames::rx_host, $uid=checkforransomwarefilenames::cuid]))

Thanks for pointing this out. The issue is in line 73, originally
@if ( Version::info$major >= 5 && Version::info$minor >= 1 )
It will need to be changed to
@if ( ( Version::info$major >= 5 && Version::info$minor >= 1 ) || ( Version::info$major >= 6 ) )
The issue is that (my silly mistake) only adjusts the default behavior for version 5 and up if the minor version is 1 or higher, so any x.0 release would still have the old behavior requiring tx_hosts and rx_hosts, which doesn't make sense. With the above information, you should be able to patch in place pretty quickly, if you want, while I work out the release process.

Good day Mark!
Thanks for your speedy response.  We'll implement the workaround for now.  We'll check back later for the official updated version later.  Thank you for your support!

The code has been fixed in the repo, let us know if anything else comes up. Thanks, again, for the report!


Use dagon for dag rewrites

Scalding 0.18 is using dagon to implement its new backend. We might as well use dagon here too, which was taken out from summingbird about 6 months or so ago.
We have found a number of performance improvements in the code since then, so it should be a win.

@ttim @erik-stripe @non ptal

note we ran these rules in production on storm and significantly reduced the number of storm nodes we created.
I think you should consider using these to optimize your storm graphs as well.

Yeah I can second this recommendation. 👍

These tests are in a very bad place.
I have been clicking rebuild to deal with storm or hadoop timeouts for about 24 hours now. Each trial is another 20-60 minutes. I am almost ready to merge without the tests...
We need to really think about improving the platform tests.

Codecov Report

Merging #758 into develop will decrease coverage by 1.07%.
The diff coverage is 62.82%.

@@             Coverage Diff             @@
##           develop     #758      +/-   ##
===========================================
- Coverage     72.5%   71.43%   -1.08%
===========================================
  Files          154      151       -3
  Lines         3783     3606     -177
  Branches       211      209       -2
===========================================
- Hits          2743     2576     -167
+ Misses        1040     1030      -10

Impacted Files
Coverage Δ

.../scala/com/twitter/summingbird/memory/Memory.scala
94.73% <ø> (ø)
:arrow_up:

.../twitter/summingbird/memory/ConcurrentMemory.scala
95.77% <100%> (+0.06%)
:arrow_up:

...com/twitter/summingbird/planner/DagOptimizer.scala
60% <62.33%> (-14.02%)
:arrow_down:

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 57312f7...f78f056. Read the comment docs.


Update bitmaps for ToolboxBitmapAttribute tests

Prefix a bitmap with a letter to allow a c# class to be defined with that name
Add an invalid icon file that has to have an ico suffix and has to be an embedded resource

No rush with this, as I won't have a chance to update dotnet/corefx#21454 until dotnet/corefx#21552 is merged
@mellinoe

@hughbe,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

LGTM

Uploaded the new version.


Added Test file stubs for rippers that did not have corresponding test files.

See issues #915, #916, #917, #918, #919, #920, #921, #922, #923, #924, #925

Coverage decreased (-0.05%) to 39.633% when pulling d257794efd846d6143f98e43a173d8e47fef8ca0 on metaprime:missing-test-files into 3f844960848632f8a79a9f9fba43f791aa177738 on RipMeApp:master.


tmux: restore session

Find a way to restore the last session after the terminal is closed. There are plugins to do this.

Not using tmux anymore at the moment.


Order bars in stacked circular barplot

Hi! Love the website and thanks for the amazing charts. I just used the stacked grouped circular barplot (https://www.r-graph-gallery.com/299-circular-stacked-barplot.html), and needed to order the bars like you did in the regular one (https://www.r-graph-gallery.com/297-circular-barplot-with-groups.html), so after some tinkering I got it to work by replacing this line:
 data <- data %>% arrange(group, individual)
with this line:
data <-data %>% group_by(group, individual) %>% mutate(sumValue=sum(value, na.rm = T)) %>%  arrange(group, sumValue, individual)  %>% ungroup()
Just thought I'd share back if you'd like to add it as an optional feature.
Thanks again for your work!

This repo is about the D3 graph gallery! :) but thanks


Simplify build of calicoctl now that we have a newer PyInstaller

@caseydavenport This is passing tests. Could you take a look when you get a mo.

LGTM.
Have you checked that a built binary actually works?  I've noticed issues with the calico-cni builds since the new build container.


Root scaling height and nameplates

I was surprised to see this happening when I had a taller character. I used to edit character height through penumbra, using a mod that was just sliders under the Advanced Editing->Meta Manipulations menus, and with that the nameplate and camera shifted up a bit as if I were playing a taller race.

Height and nameplate dont scale with root.
Keep using penumbra for this, that's the intended way.


HttpUtil.setTransferEncodingChunked:No. 347 should add a flashback array code, otherwise it will change the order of the original attribute values in the linked list

This seems to be not valid... we make a copy of the values

This seems to be not valid... we make a copy of the values

Changed the order of the original linked list nodes，
Wrong order

HTTP RFC does not enforce ordering AFAIK.


Package Resolution Failed

Hello,
When I am fetching the swift package, I am getting this resolution failure
package 'SwiftFX' is required using a revision-based requirement and it depends on local package 'LiveValues', which is not supported
I'm not sure if this is on my end or what. First time using the Swift Package manager, could be my fault.

I see line 17-19 is commented out here,
perhaps it shouldn't be?

I merged your PR, Thanks!


Wiki Wanted

We can use everything API's regular expression with prefix @
About Everything API
The execution path is

Main.cs get api
Everything API get search function

I have opened up Wiki section in this fork so feel free to contribute if you want to expand on the above.


Globe is not visible

I don't see a globe in the live demo:

The Cesium version used in this demo is pretty out of date and the imagery token must have expired. @likangning93 can you update to the newest version of Cesium? (Might need to disable log depth).


Trying newer rocker/verse:3.6.0 tag

RStudio image based on rocker/verse:3.5.3 seem to have a problem
running shining apps. Apps were getting connection refused.
Testing this newer tag to see if it helps.

We tested again the RStudio 1.2 image and this doesn't appear to be a problem anymore so closing this.


Storing the references to varaibles in variables.json is not safe

And the contens of variables.json

The problem with storing this here is if I delete this file in my home directory, then the values will remain in the keychain forever. We need to store these pointers in such a way that they are discoverable in the keychain eg store the JSON in the keychain and manage it there instead of on the file system,

Working on that

Now the manifest and the values are stored in the OS keychain


Use git commit date for versions

resolves #274

This Pull Request has been merged by GitConsensus.
Vote Totals

Yes
No
Abstain
Voters

3
0
0
3

Vote Breakdown

User
Yes
No
Abstain

tedivm
✔

PostCrafter
✔

dragoonreas
✔

Vote Results

Criteria
Result

Has Quorum
True

Has Votes
True


Keyboard shortcuts no longer shown

Somehow keyboard shortcuts are not displayed anymore in the tools.
@Integral maybe you want to take a look, if you have problems I take this over.

Probably a regression since pulling Tools and stuff out of substance core

While I'm a bit confused by this comment I did try to revert this functionality here: #717

Hmmm. I agree. That comment does not bring much ;)

@Integral you can merge. Thx.

Done, thanks.


new features

Input to ranger to ignore a table of ents
Steam friends sync with wire friendslist

Just so other devs know, this is an unfinished PR that I'll be taking a look at later
todo:

friends list entity doesn't need to sync steam friends because it's already synced in an e2 function, just make that information available
add CPPI friends option
make ranger use trace filter to ignore entities instead of an if statement
add "Any", "None", "All" array inputs to friends list entity which would check if any/none/all players in the array match.


Update openvpn-install.sh

Purpose? No description is almost always going to get ignored....

Not only is this useless for the purposes of the script, but that is an outdated approach since systemd now manages /etc/resolv.conf.
And yes, if you submit a commit, try at least to explain what you are trying to do. Also because it is easier to find and understand what it does if/when it gets merged.


Ability to set value at which labels combine?

I have steps of 0.01 and a floor of 0 to a ceil of 0.50.  When the 2 selectors get within 0.09 of each other, they start to merge the labels.  They could go till at least 0.04 or 0.03 before they'd be next to each other.  Is there a way to make it so they labels don't merge and get retained on their related selectors - maybe a property to set or something?
In the interim, I've set a minRange of 0.10, but there are some cases where the user wants a range of 0.05.  So it'd be nice to prevent the combined labels unless it's absolutely necessary.

The combined label is not shown based on the values but based on the size of the min/max labels. If they overlap, then we show the combined one. ;)

Thanks. Realized the line height on my selectors was causing the labels to overlap even though they didn't appear to physically overlap.


[TS] [1.2 API review] Rename TextBlock's fontStyle to fontFamily

Automatically generated task. Any updates to the title and body will be overwritten. Do NOT modify the labels.
TS fix of #2906

PR here: https://github.com/microsoft/AdaptiveCards/pull/2905


GitHub integration broken on my haypo-notes project

Details

Project URL: http://haypo-notes.readthedocs.io/
Build URL (if applicable):
Read the Docs username (if applicable): haypo

Expected Result
Pushing a commit to GitHub should trigger a documentation build.
Actual Result
No build is triggered. I have to trigger the build manually.
The Integration page of my project has a GitHub item which says:
This integration was created automatically from an existing webhook configured on your repository. To make any changes to this webhook, you'll need to update the configuration there. You can use the following address to manually configure this webhook.
readthedocs.org/api/v2/webhook/haypo-notes/12118/
For more information on manually configuring a webhook, refer to our webhook documentation
--
I tried to remove the ReadTheDocs service from my GitHub project to recreate it, multiple times, but it didn't work.
I also removed and recreated the ReadTheDocs project, multiple times, and it didn't work.
Previously, I had a red warning about the GitHub integration on ReadTheDocs, but sadly it's now gone, so I cannot copy/paste the message anymore.

I just pushed a dummy change just to test the integration:

https://github.com/haypo/haypo_notes/commit/2a19c8a2f626595d5708cb8780bbde7f9b4e8c7b
https://readthedocs.org/projects/haypo-notes/builds/ has no new build for this commit
http://haypo-notes.readthedocs.io/cpython.html#embedded-libraries still contains the old doc

Are you still having this problem? All the links are 404.

Oh. I changed the name of my project from haypo-notes to vstinner. I created a new project when I renamed the GitHub repositry. And GitHub now notify properly ReadTheDocs. Thanks!

FYI my new website: http://vstinner.readthedocs.io/


Transition effects with dynamic components

Adding information about how to apply transition effects with dynamic components without creating any fragment instance.

I'm not sure if this is correct. Fragment instance warnings is all about the component's template - if all dynamic components conform to the single-root-node rule then it doesn't matter where you place the transition attribute.

Mistake is on me, sorry about that. I was facing a problem with a component fragment instance since few days and the only way for me to fix it was applying the method described in my pull request.
I guess I have been a little too eager to share it with the community, because since your comment I've been running several independent tests in order to verify what I was saying, and I have not been able to re-create the issue I was facing.
For any reason it was coming from the cache that Google Chrome applies by default for Javascript files, and this put me in error. Anyway, I guess my pull request can be closed. Again, sorry about that.


qemu: Do not try and generate invalid RTC parameters

If no RTC is specified in the config then do not generate any RTC command line
options. RTC command line options are optional for QEMU so make Valid() return
false when presented with the empty version of the RTC struct containing empty
strings.
Signed-off-by: Rob Bradford<EMAIL_ADDRESS>

Coverage decreased (-0.03%) to 76.856% when pulling e46092e03ac049660d2eb5bf0c4e3cb7ed2ce03d on rbradford:rtc-valid-tweak into 301ea5e989f8d367619c017a37dd32867b384359 on intel:master.

Coverage decreased (-0.03%) to 76.856% when pulling e46092e03ac049660d2eb5bf0c4e3cb7ed2ce03d on rbradford:rtc-valid-tweak into 301ea5e989f8d367619c017a37dd32867b384359 on intel:master.


[BUG] iOS front camera flash can be set from auto to on but not further

Hello. Thanks a lot for this great plugin!
Describe the bug
On iOS, when using the front camera, clicking on the flash once sets the flash from auto to "on" but clicking again keeps the flash set to on. It doesn't lead to permanent, off, auto (again), etc.
How to reproduce

Run app on iOS device with code mentioned in Additional context to pick a camera image (photo only).
Switch to front camera.
Click flash to switch from auto to "on".
Click flash again to switch from "on" to permanent.

Expected behavior
Flash should be set to permanent.
Effective behavior
Flash remains "on".
Screenshots (If contains)

Version information

Device: iPhone SE 2020
OS: iOS 16.0.3
Package Version: 3.6.5
Flutter Version: 3.3.4
Language: English

Additional context
When long press on flash, info pop up says "Flash mode: always" while the flash mode logo indicates "on".
Everything works fine with the same code on Android.
Everything works fine with the back camera.
I was not able to test this on the plugin example app but I would expect the same result.
The code used to pick a camera image (photo only) is the following one:
                  AssetEntity result;
                  result = await CameraPicker.pickFromCamera(
                    context,
                    locale: Locale("en"),
                    pickerConfig: CameraPickerConfig(
                      textDelegate: CustomCameraPickerDelegate(),
                      resolutionPreset: ResolutionPreset.low,
                    ),
                  );

The English text delegate used is the following one ; though, it shouldn't have any impact IMHO as the rest works fine:
class CustomCameraPickerDelegate extends CameraPickerTextDelegate {
  @override
  String get languageCode => "en";

  @override
  String get confirm => "Confirm";

  @override
  String get shootingTips => "Click to take a picture.";

  @override
  String get shootingWithRecordingTips =>
  "Click to take a picture. Long press to record a video.";

  @override
  String get shootingOnlyRecordingTips => "Long press to record a video.";

  @override
  String get shootingTapRecordingTips =>
      "Tap to record video.";

  @override
  String get loadFailed => "Loading failed";

  @override
  String get sActionManuallyFocusHint => "Manual focus";

  @override
  String get sActionPreviewHint => "Preview";

  @override
  String get sActionRecordHint => "Save";

  @override
  String get sActionShootHint => "Take a picture";

  @override
  String get sActionShootingButtonTooltip => "Shooting button";

  @override
  String get sActionStopRecordingHint => "Stop recording";

  @override
  String sCameraLensDirectionLabel(CameraLensDirection value) {
    switch (value) {
      case CameraLensDirection.back:
        return "Back";
      case CameraLensDirection.front:
        return "Front";
      case CameraLensDirection.external:
        return "External";
      default:        return value.name;
    }
  }

  @override
  String sCameraPreviewLabel(CameraLensDirection value) {
    if (value == null) {
      return null;
    }
    return "Camera preview ${sCameraLensDirectionLabel(value)}";
  }

  @override
  String sFlashModeLabel(FlashMode mode) => "Flash mode: ${mode.name}";

  @override
  String sSwitchCameraLensDirectionLabel(CameraLensDirection value) =>
      "Switch to ${sCameraLensDirectionLabel(value)} camera";

  @override
  String get loading => "Loading";

  @override
  String get saving => "Saving";
}

I can confirm the same behavior with the plugin example app (first line: take a photo) on the same device (iPhone SE 2020). I also got the following error log:
[VERBOSE-2:dart_vm_initializer.cc(41)] Unhandled Exception: CameraException(setFlashModeFailed, Device does not support torch mode)
#0      handleErrorWithHandler (package:wechat_camera_picker/src/internals/methods.dart:28:3)
#1      CameraPickerState.switchFlashesMode (package:wechat_camera_picker/src/states/camera_picker_state.dart:391:7)
<asynchronous suspension>


vendor: update ttrpc with latest changes

Signed-off-by: Stephen J Day<EMAIL_ADDRESS>

Looks like something not exiting or getting hung up in the Travis CI test run. At least it appears to not be making progress.

I'm also getting stress test failures on this change.

Ya, there is something causing containers to run slow with this change.
Did a quick stress test:
before:
create/start/delete 179 containers in 10.171 seconds (17.599 c/sec) or (0.057 sec/c)  failures=0
after:
create/start/delete 4 containers in 18.304 seconds (0.219 c/sec) or (4.576 sec/c)  failures=0
Its running super slow.

@estesp @crosbymichael The status message on TestShimSigkilled is getting lost and causing the test to hang. I'll see what I can do.

I think https://github.com/stevvooe/ttrpc/pull/8 should address the issue.

Ok, fixed properly in https://github.com/stevvooe/ttrpc/pull/8. PTAL and I'll update this with the changes.

Codecov Report

Merging #1831 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #1831   +/-   ##
=======================================
  Coverage   49.17%   49.17%
=======================================
  Files          86       86
  Lines        8518     8518
=======================================
  Hits         4189     4189
  Misses       3659     3659
  Partials      670      670

Flag
Coverage Δ

#linux
49.27% <ø> (ø)
:arrow_up:

#windows
44.25% <ø> (ø)
:arrow_up:

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 96ca973...393cf8e. Read the comment docs.

LGTM
INFO[1801] create/start/delete 30967 containers in 1800.163 seconds (17.202 c/sec) or (0.058 sec/c)  failures=0


Strange issue with Fibaro Scenes

I am getting the following error when I go to the Fibaro Scenes tab...
Get Fibaro Scenes Error: undefined with status: Server Error - 500
but the devices tab is all populated correctly? Anyone any ideas?
Thanks

So V5.2.0 is out there and it has an update for fibaro.


disc()

Is it it possible for the object to use the first column of the headers rather than the first row?
What Does this Impact?
My csv would be a lot easier to maintain if the headers were 2 rows of data rather than two columns of data

No. While this lib is very flexible for covering different use cases. Pivoting data from columns into rows is not one of them.

My csv would be a lot easier to maintain if the headers were 2 rows of data rather than two columns of data

You're right. I can't think of a reasonable explanation why somebody would structure data this way. If the set isn't too big it might be worth importing into Excel, pivoting the columns into headers. Then running it through this lib.


Fix pbv4 broken Student Robotics link.

pbv4.rst attempts to link to Student Robotics but this link doesn't
actually go anywhere, resulting in broken formatting. mbv4 doesn't link
to Student Robotics and only links to the license. This commit removes
the link from pbv4 and makes it like mbv4, without a link to Student
Robotics.

@mildlyincompetent you can merge your own PR once it's been approved (I'm aware this isn't documented at the moment: #397).


Bug 1471040 - Don't block builder flow if can't get instances

Don't block the user from creating from builder if there's an error getting the instances
Fix an error where the watch isn't closed when switching projects, which means the instances listed in the dialog might be for the wrong project

Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1471040

approve for 3.6 once travis passes


Adding Session Storage to Dashboard List

No need to trigger API query call every time a user switches between different tabs
API query call can be triggered manually with the refresh button next to the search bar.
Every time a user modifies his own dashboards, API query call will be triggered.

Current coverage is 36.46% (diff: 100%)

Merging #213 into develop will decrease coverage by 0.03%

@@            develop       #213   diff @@
==========================================
  Files           260        260
  Lines         14162      14162
  Methods           0          0
  Messages          0          0
  Branches       2378       2378
==========================================
- Hits           5169       5164     -5
- Misses         8271       8275     +4
- Partials        722        723     +1

Powered by Codecov. Last update 0f11779...8b4f10a


Update version number

Update to 1.3 in preparation for the next release

Good point, we definitely should. Should we add all current maintainers as authors?

I'm happy with that approach. I think they just need to be in a comma-separated string.

If it works, I'm happy for this to be merged.

Although it looks like the author list changes aren't in there yet

Have just added them to the PR


repo: add additional community docs to the openstack-helm repos

Kubernetes Version (output of kubectl version): N/A
Helm Client and Tiller Versions (output of helm version): N/A
Development or Deployment Environment?: N/A
Release Tag or Master: N/A
Expected Behavior: N/A
What Actually Happened: N/A
How to Reproduce the Issue (as minimally as possible): N/A
Any Additional Comments:
As we prepare our repo for the community, we need to address and include the following in our repository:

changelog
code of conduct
contributing guidelines
contributor agreements (?)
expectations (for issues, pr's, contributors and reviewers)
OWNERS
RELEASES

OWNERS resolved in (#162)

@wilkers-steve none. closing.


vc path not populated

Example
https://orb-1.dev.trustbloc.dev/vc/0d9a2b2c-1dab-45c4-b7c0-81102a80970f returns 404.
This URL was taken from an AnchorCredential id in the outbox.

It is replaced by Anchor Event REST issue.


[StyleCop] Fix all the warning in Integration.AspNet.Core.Tests

Reorder methods and fields
Remove trailing whitespace
Add trailing comma
Rename local variable

Pull Request Test Coverage Report for Build 51648

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 75.588%

Totals

Change from base Build 51599:
0.0%

Covered Lines:
4304

Relevant Lines:
5694

💛  - Coveralls


Improvements

Hi,
I was reading through your code and decided to tamper with your example page to have it fetch URLs from the README.md. Then I discovered some bugs with Firefox.
I fixed an issue with the downloadZip function where, apparently, Firefox needs the link to be in the page’s DOM in order to catch the click onto it.
However, one problem I did not fix is Firefox displaying the example html file ("https://github.com/KinoLien/gitzip/blob/master/example.html") instead of prompting for download. This is by design, according to https://developer.mozilla.org/en-US/docs/Web/HTML/Element/a#attr-download :

This attribute is only honored for links to resources with the same-origin.

I have no idea how to find a workaround, but I’ll keep investigating.
If you’re only interested in one of my two commits, just tell me and I’ll make a separate pull request.

Thanks for discovered this problem, and after i add the followings:
document.body.appendChild(down);
down.click();
down.parentNode.removeChild(down);

In FireFox, this would work, but "Get File" cannot work.
I think the solution is make the file content to Blob, and use saveAs function to download it.
What do you think?

The difficulty here is making a blob. This implies the script has knowledge of the resource’s contents, and this falls under the Same-Origin Policy. Maybe there’s something to do with CORS headers. I’m searching this way.

Blob is working :) Actually the Origin header needed to make CORS work is automatically added.
I checked Firefox and Chrome.

Awesome! Thanks a lot.

You’re welcome ;)


Add game ending check before adding another player

I'm not sure what you were expecting for the unit test so I chose to put it in the existing high score mode test class simply because it was convenient.  If you want it elsewhere please let me know.

Looks very good. Thanks!

fixes #1494


Two way edit612

Adding in two way binding for feature table
Updating action/reducer to support adding feature at position
Moving tests for adding features to the map to own test file
Adding some styles for tables

Coverage increased (+0.006%) to 98.568% when pulling 0e2745be891eec13aa389c1256baa5658c529936 on wnordmann:twoWayEdit612 into 96c98ab46042bab44612dd0d4dc867ad0e2b9eba on boundlessgeo:master.

Coverage increased (+0.01%) to 98.574% when pulling c428e260ef5ff0c0f569afdbcec9fd4f00c6b187 on wnordmann:twoWayEdit612 into 96c98ab46042bab44612dd0d4dc867ad0e2b9eba on boundlessgeo:master.

Coverage increased (+0.007%) to 98.507% when pulling 730b15f296186b6561e2ec0cf4335c162ea1a899 on wnordmann:twoWayEdit612 into 4271cbc5751cbb69306d231ee0bcd9c001d5f54a on boundlessgeo:master.

Coverage increased (+0.01%) to 98.514% when pulling 0f3cee23f19c743caa7e549a1194c89b306c1526 on wnordmann:twoWayEdit612 into 4271cbc5751cbb69306d231ee0bcd9c001d5f54a on boundlessgeo:master.


Data disk free space have a big decrease,then release in 12 minutes

Bug Report
What did you do?
I have two physical servers, one of them have prometheus server in docker, the other have node_exporter , pushgateway , remote adapter and influxdb as remote storage in docker.
And the one which have node_exporter,data disk free space have a big decrease,then release in 12 minutes

Prometheus version:
v2.2.1

this will happened one time a week:

In most of time:

I see nothing here that would indicate a problem with Prometheus or node_exporter. It seems legit that the disk's free space varies over time.
I'm closing it for now. If you have further questions, please use our user mailing list, which you can also search.


Shadow DOM support?

Yay for old legacy CSS that over=-used !important.
I want to mount a component from a vue library into the ShadowDOM so that the host angular app can't rub its grubby !important rules all over the styles provided by the component library (loaded from a separate CSS file).
I noticed issue in the original ngvue project as well: https://github.com/ngVue/ngVue/issues/145
Given you're busy, I'm not expecting you to implement anything, but I am curious to hear your thoughts on a clean way to do this with nvgue3.  A plugin perhaps? Extra options in the directive? Some other approach?

Sorry I have next to no experience with working with the shadow dom and web components, in theory it should be possible but from what I've looked into it feels like it might be a completely alternative solution to ngVue where there would be a fair amount of overlap in responsibilities.


Addresses the feedbacks in #95738

Pre-launch Checklist

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] I read the Tree Hygiene wiki page, which explains my responsibilities.
[x] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[x] I signed the CLA.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is test-exempt.
[x] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

Thanks for the review, PTAL, thanks!

Thanks for the suggestion. Added test for proxy.connect. PTAL, thanks!


bug: Atlas Migration and Cascade Delete have unexpected behavior.

Not sure if this belong here or in the Atlas repository, feel free to redirect me!

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
While generating Versioned Migrations with the new Atlas API, a simple column add results in a breakage of M2M relationships when cascade deletes are enabled.
Expected Behavior 🤔
Ent/Atlas should generate migrations that preserve the M2M relationship even when Cascade Delete is enabled.
Steps to Reproduce 🕹

Steps:

Create Entities with M2M Relationship
Generate Initial Migration File
Add Data with M2M relationship
Add Column to Schema
Generate New Migration File
Runs Migrations
Observe M2M Table is now empty

I don't have time today to put together a minimal reproducible example, but if this is accepted as a valid bug I can work on that in the next couple of days.
Here's My Code

Item Entity Schema
Label Entity Schema
OnDelete Cascade Option
Migration File when adding a new field to the Item table

When the migration is complete all the Items in the database no longer have any associated Labels. The label_items table is empty.
Your Environment 🌎

Tech
Version

Go
1.19

Ent
0.11.2

Database
SQLite

Driver
github.com/mattn/go-sqlite3

Thanks for reporting this, @hay-kot. I’ll give it a look soon and update this issue.

Hey @hay-kot, can you please paste here the URL you used for generating the migration? (e.g. sqlite://...)

Hey @hay-kot, can you please paste here the URL you used for generating the migration? (e.g. sqlite://...)
If you can also paste the generated migration file here, this can help as well. Thanks 🙏

Sure!
sqlite://.data/homebox.migration.db?_fk=1

 Initial Migration File
-- create "attachments" table
CREATE TABLE `attachments` (`id` uuid NOT NULL, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL, `type` text NOT NULL DEFAULT 'attachment', `document_attachments` uuid NOT NULL, `item_attachments` uuid NOT NULL, PRIMARY KEY (`id`), CONSTRAINT `attachments_documents_attachments` FOREIGN KEY (`document_attachments`) REFERENCES `documents` (`id`) ON DELETE CASCADE, CONSTRAINT `attachments_items_attachments` FOREIGN KEY (`item_attachments`) REFERENCES `items` (`id`) ON DELETE CASCADE);
-- create "auth_tokens" table
CREATE TABLE `auth_tokens` (`id` uuid NOT NULL, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL, `token` blob NOT NULL, `expires_at` datetime NOT NULL, `user_auth_tokens` uuid NULL, PRIMARY KEY (`id`), CONSTRAINT `auth_tokens_users_auth_tokens` FOREIGN KEY (`user_auth_tokens`) REFERENCES `users` (`id`) ON DELETE CASCADE);
-- create index "auth_tokens_token_key" to table: "auth_tokens"
CREATE UNIQUE INDEX `auth_tokens_token_key` ON `auth_tokens` (`token`);
-- create index "authtokens_token" to table: "auth_tokens"
CREATE INDEX `authtokens_token` ON `auth_tokens` (`token`);
-- create "documents" table
CREATE TABLE `documents` (`id` uuid NOT NULL, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL, `title` text NOT NULL, `path` text NOT NULL, `group_documents` uuid NOT NULL, PRIMARY KEY (`id`), CONSTRAINT `documents_groups_documents` FOREIGN KEY (`group_documents`) REFERENCES `groups` (`id`) ON DELETE CASCADE);
-- create "document_tokens" table
CREATE TABLE `document_tokens` (`id` uuid NOT NULL, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL, `token` blob NOT NULL, `uses` integer NOT NULL DEFAULT 1, `expires_at` datetime NOT NULL, `document_document_tokens` uuid NULL, PRIMARY KEY (`id`), CONSTRAINT `document_tokens_documents_document_tokens` FOREIGN KEY (`document_document_tokens`) REFERENCES `documents` (`id`) ON DELETE CASCADE);
-- create index "document_tokens_token_key" to table: "document_tokens"
CREATE UNIQUE INDEX `document_tokens_token_key` ON `document_tokens` (`token`);
-- create index "documenttoken_token" to table: "document_tokens"
CREATE INDEX `documenttoken_token` ON `document_tokens` (`token`);
-- create "groups" table
CREATE TABLE `groups` (`id` uuid NOT NULL, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL, `name` text NOT NULL, `currency` text NOT NULL DEFAULT 'usd', PRIMARY KEY (`id`));
-- create "items" table
CREATE TABLE `items` (`id` uuid NOT NULL, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL, `name` text NOT NULL, `description` text NULL, `import_ref` text NULL, `notes` text NULL, `quantity` integer NOT NULL DEFAULT 1, `insured` bool NOT NULL DEFAULT false, `serial_number` text NULL, `model_number` text NULL, `manufacturer` text NULL, `lifetime_warranty` bool NOT NULL DEFAULT false, `warranty_expires` datetime NULL, `warranty_details` text NULL, `purchase_time` datetime NULL, `purchase_from` text NULL, `purchase_price` real NOT NULL DEFAULT 0, `sold_time` datetime NULL, `sold_to` text NULL, `sold_price` real NOT NULL DEFAULT 0, `sold_notes` text NULL, `group_items` uuid NOT NULL, `location_items` uuid NULL, PRIMARY KEY (`id`), CONSTRAINT `items_groups_items` FOREIGN KEY (`group_items`) REFERENCES `groups` (`id`) ON DELETE CASCADE, CONSTRAINT `items_locations_items` FOREIGN KEY (`location_items`) REFERENCES `locations` (`id`) ON DELETE CASCADE);
-- create index "item_name" to table: "items"
CREATE INDEX `item_name` ON `items` (`name`);
-- create index "item_manufacturer" to table: "items"
CREATE INDEX `item_manufacturer` ON `items` (`manufacturer`);
-- create index "item_model_number" to table: "items"
CREATE INDEX `item_model_number` ON `items` (`model_number`);
-- create index "item_serial_number" to table: "items"
CREATE INDEX `item_serial_number` ON `items` (`serial_number`);
-- create "item_fields" table
CREATE TABLE `item_fields` (`id` uuid NOT NULL, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL, `name` text NOT NULL, `description` text NULL, `type` text NOT NULL, `text_value` text NULL, `number_value` integer NULL, `boolean_value` bool NOT NULL DEFAULT false, `time_value` datetime NOT NULL, `item_fields` uuid NULL, PRIMARY KEY (`id`), CONSTRAINT `item_fields_items_fields` FOREIGN KEY (`item_fields`) REFERENCES `items` (`id`) ON DELETE CASCADE);
-- create "labels" table
CREATE TABLE `labels` (`id` uuid NOT NULL, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL, `name` text NOT NULL, `description` text NULL, `color` text NULL, `group_labels` uuid NOT NULL, PRIMARY KEY (`id`), CONSTRAINT `labels_groups_labels` FOREIGN KEY (`group_labels`) REFERENCES `groups` (`id`) ON DELETE CASCADE);
-- create "locations" table
CREATE TABLE `locations` (`id` uuid NOT NULL, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL, `name` text NOT NULL, `description` text NULL, `group_locations` uuid NOT NULL, PRIMARY KEY (`id`), CONSTRAINT `locations_groups_locations` FOREIGN KEY (`group_locations`) REFERENCES `groups` (`id`) ON DELETE CASCADE);
-- create "users" table
CREATE TABLE `users` (`id` uuid NOT NULL, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL, `name` text NOT NULL, `email` text NOT NULL, `password` text NOT NULL, `is_superuser` bool NOT NULL DEFAULT false, `group_users` uuid NOT NULL, PRIMARY KEY (`id`), CONSTRAINT `users_groups_users` FOREIGN KEY (`group_users`) REFERENCES `groups` (`id`) ON DELETE CASCADE);
-- create index "users_email_key" to table: "users"
CREATE UNIQUE INDEX `users_email_key` ON `users` (`email`);
-- create "label_items" table
CREATE TABLE `label_items` (`label_id` uuid NOT NULL, `item_id` uuid NOT NULL, PRIMARY KEY (`label_id`, `item_id`), CONSTRAINT `label_items_label_id` FOREIGN KEY (`label_id`) REFERENCES `labels` (`id`) ON DELETE CASCADE, CONSTRAINT `label_items_item_id` FOREIGN KEY (`item_id`) REFERENCES `items` (`id`) ON DELETE CASCADE);

 After New Column
-- disable the enforcement of foreign-keys constraints
PRAGMA foreign_keys = off;
-- create "new_items" table
CREATE TABLE `new_items` (`id` uuid NOT NULL, `created_at` datetime NOT NULL, `updated_at` datetime NOT NULL, `name` text NOT NULL, `description` text NULL, `import_ref` text NULL, `notes` text NULL, `quantity` integer NOT NULL DEFAULT 1, `insured` bool NOT NULL DEFAULT false, `serial_number` text NULL, `model_number` text NULL, `manufacturer` text NULL, `lifetime_warranty` bool NOT NULL DEFAULT false, `warranty_expires` datetime NULL, `warranty_details` text NULL, `purchase_time` datetime NULL, `purchase_from` text NULL, `purchase_price` real NOT NULL DEFAULT 0, `sold_time` datetime NULL, `sold_to` text NULL, `sold_price` real NOT NULL DEFAULT 0, `sold_notes` text NULL, `test_migration_field` text NOT NULL DEFAULT 'test-migration-value', `group_items` uuid NOT NULL, `location_items` uuid NULL, PRIMARY KEY (`id`), CONSTRAINT `items_groups_items` FOREIGN KEY (`group_items`) REFERENCES `groups` (`id`) ON DELETE CASCADE, CONSTRAINT `items_locations_items` FOREIGN KEY (`location_items`) REFERENCES `locations` (`id`) ON DELETE CASCADE);
-- copy rows from old table "items" to new temporary table "new_items"
INSERT INTO `new_items` (`id`, `created_at`, `updated_at`, `name`, `description`, `import_ref`, `notes`, `quantity`, `insured`, `serial_number`, `model_number`, `manufacturer`, `lifetime_warranty`, `warranty_expires`, `warranty_details`, `purchase_time`, `purchase_from`, `purchase_price`, `sold_time`, `sold_to`, `sold_price`, `sold_notes`, `group_items`, `location_items`) SELECT `id`, `created_at`, `updated_at`, `name`, `description`, `import_ref`, `notes`, `quantity`, `insured`, `serial_number`, `model_number`, `manufacturer`, `lifetime_warranty`, `warranty_expires`, `warranty_details`, `purchase_time`, `purchase_from`, `purchase_price`, `sold_time`, `sold_to`, `sold_price`, `sold_notes`, `group_items`, `location_items` FROM `items`;
-- drop "items" table after copying rows
DROP TABLE `items`;
-- rename temporary table "new_items" to "items"
ALTER TABLE `new_items` RENAME TO `items`;
-- create index "item_name" to table: "items"
CREATE INDEX `item_name` ON `items` (`name`);
-- create index "item_manufacturer" to table: "items"
CREATE INDEX `item_manufacturer` ON `items` (`manufacturer`);
-- create index "item_model_number" to table: "items"
CREATE INDEX `item_model_number` ON `items` (`model_number`);
-- create index "item_serial_number" to table: "items"
CREATE INDEX `item_serial_number` ON `items` (`serial_number`);
-- enable back the enforcement of foreign-keys constraints
PRAGMA foreign_keys = on;

Since Atlas is using a temporary table to add the new field, I'm assuming that when the original table gets deleted, all those cascade onto the M2M table

The PRAGMA foreign_keys = off; command should prevent this, and I wanted to make sure you generated the migration files with _fk=1 enabled. I'll try to reproduce this and will update you.

OK, I found the issue here: https://www.sqlite.org/pragma.html#pragma_foreign_keys

This pragma is a no-op within a transaction; foreign key constraint enforcement may only be enabled or disabled when there is no pending BEGIN or SAVEPOINT.

The Atlas CLI part was handled in https://github.com/ariga/atlas/pull/1162. A new version of the CLI will be tagged soon. Then, I'll update the Ent automatic migration and will close this issue. Thanks for reporting this 🙏

Wow! Thanks for such a fast response, looking forward to a release!


Massive Update

Mainly formatting update to facilitate the inclusion of more show/hide options and all relevant fields.
Big change that will affect users is the conversion of the Defense Level/Armor fields into an autocalc with a show-able field to manually put in the math, (Level put in by default, which is good for most characters)

The change looks good. I'll pull the code in to test myself and will merge if everythign runs fine.


services/ticker: fix flakey spec comparing time with postgres stored time

PR Checklist
PR Structure

[x] This PR has reasonably narrow scope (if not, break it down into smaller PRs).
[x] This PR avoids mixing refactoring changes with feature changes (split into two PRs
otherwise).
[x] This PR's title starts with name of package that is most changed in the PR, ex.
services/friendbot, or all or doc if the changes are broad or impact many
packages.

Thoroughness

[x] ~This PR adds tests for the most critical parts of the new functionality or fixes.~
[x] ~I've updated any docs (developer docs, .md
files, etc... affected by this change). Take a look in the docs folder for a given service,
like this one.~

Release planning

[x] ~I've updated the relevant CHANGELOG (here for Horizon) if
needed with deprecations, added features, breaking changes, and DB schema changes.~
[x] I've decided if this PR requires a new major/minor version according to
semver, or if it's mainly a patch change. The PR is targeted at the next
release branch if it's not a patch change.

Summary
Change the TestInsertOrUpdateAsset test to Round instead of Truncate time values that are being compared with time that was stored in Postgres.
Goal and scope
Intermittently the TestInsertOrUpdateAsset test will fail because a time value that's been stored in Postgres doesn't match the time value we gave to Postgres to store. We attempt to do our best to make them match by using the Truncate value on both the input and output values, but that doesn't work for some cases.
I managed to reproduce the failure 100% of the time by using a specific input time of 12:08:50.9419997 where the milliseconds component will be rounded up because of the values in the nanosecond component by Postgres when it reduces the value to microseconds. To see the exact failure case, take a look at the first commit where I hardcoded it for consistent failures. This isn't the only failure case though. When I ran the tests thousands of times I had plenty of times where it failed. Because we use the Truncate function, we are comparing a rounded down value with a rounded up value in any cases where the millisecond component gets rounded up when the microsecond component is rounded up.
To illustrate exactly what is happening here, this is our original time:
12:08:50.9419997

When Postgres is truncating it to microseconds, which is six decimal places, it is rounding to the nearest, which in this case is up:
12:08:50.942000

In our test we use the truncate function to truncate to milliseconds:
12:08:50.941

Using Round instead causes us to round up to the same value.
Close #1733
Summary of changes

Replace use of Truncate with Round.

Known limitations & issues
The fix in this change isn't perfect according to discussion at https://github.com/lib/pq/issues/227#issuecomment-33869993, where a commenter states that Postgres' rounding function rounds to nearest and in the event of a tie rounds to even, which is different to Go's Round function which rounds to nearest and in the event of a tie rounds away from zero. This would cause a problem in this situation:
However, in the tests I ran with time 12:08:50.9419995 and rounding to the nearest microsecond, both Postgres and Go had rounded in the same directions, so I don't see evidence that this is an issue.
Even if this was still an issue I think this change is the best simple change we can make to the test and it would significantly reduce the number of cases this test fails.
What shouldn't be reviewed
N/A

It'd be great to prevent us from using Truncate in tests in this way, and we could try write a checker compatible with go vet to prevent us from making the same mistake, but I think the only way to do that would be to ban us from ever using Truncate which isn't practical.

👍 Using WithinDuration that I see was used in those other PRs is also another option, but I think from the testing I've done that there's a good chance Round will fix our issues because from what I can see Postgres is actually rounding in the same way as Go does. If this starts failing again we can give that pattern a whirl here too.


Cast timestamp array to string array with timezone

Which issue does this PR close?

Closes #2607.
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

cc @sunchao


Add github action: publish to pypi

New action uses a dedicated docker container with Poetry.
It builds the package and pushes it to pypi.org.
Add version badge to README.md (+switched coverage badge to shields.io)

Please make sure:

We can only run "publish" from master
"publish" is a manual action

Verify Pypi returns error when publishing same version again

2. "publish" is a manual action

As far as I see (like we've discussed), I don't see the option to trigger the workflow manually built-in.
I suggest we use Github's "release" feature with:
on:
  release:
    types: [published]

https://help.github.com/en/actions/reference/events-that-trigger-workflows#release-event-release
Seams like a good (and correct) solution to me (also solves the first requirement)...
2 more possible solutions, which I'm not in favor of:

There is this 3rd party tool which looks nice:
https://www.actionspanel.app/

There is also the option to trigger "repository_dispatch" with an HTTP-POST request:
https://goobar.io/2019/12/07/manually-triggering-github-actions-workflows-using-postman/

Verified "re-publish" (same version) fails:


mBottomBar.setItems how to change select item image

mBottomBar.setItems how to change select item image

You mean changing the image for an active (=currently selected) item? Could you tell me why would you want to do that?


Work with BCHN to improve network responsiveness during IBD

When deploying a new Chaingraph instance from scratch, the cluster includes one or more nodes which need to initially download and verify the blockchain (Initial Block Download, IBD). The Chaingraph agent is able to start syncing from these nodes even before IBD is complete because the nodes are configured to whitelist the agent.
However in practice, Bitcoin Cash Node (BCHN) is very slow to respond to requests from the agent during IBD, and can sometimes take over a minute to send a block back (even for the <1KB blocks from the early years.)
Because of this latency, it typically takes ~2.5 hours for a well-provisioned cluster to begin syncing blocks at the maximum speed of the database. After this initial delay, the Chaingraph sync requires 6-7 additional hours to complete.
If we could configure BCHN to prioritize these network requests during IBD, we could likely cut down Chaingraph's total sync time by >2 hours. (Combined with #5, we may be able to cut total sync + indexing times down to just a few hours.)
I also suspect that IBD for BCHN is usually bound on CPU/memory rather than disk read/write, so tuning BCHN to respond faster would allow Chaingraph to start syncing that data without significantly impacting the IBD time of the BCHN instance.
The only eventual change required in Chaingraph will be to upgrade the BCHN image once some release with this improvement is available, but I'll leave this issue open to track progress. I'll open and link to an issue in the BCHN issue tracker too.

Issue opened: https://gitlab.com/bitcoin-cash-node/bitcoin-cash-node/-/issues/346


Wiremock 2.0.11-beta is not available from maven central

Please publish https://github.com/tomakehurst/wiremock/releases/tag/2.0.11-beta

I was planning on merging a couple more PRs first. Was there something specific you wanted to see released?

I thought that it is as already released, because it is tagged.

Apologies, I must have pushed the tag by accident.


Deprecate clock_tick context manager

[x] backwards compatible deprecation of clock_tick context manager
[ ] ensure activity set when changing temporal properties and model clocked with activity_cls
[ ] session and mapper event life cycle tests

Resolves #28

relevant sqlalchemy documentation on instance events: http://docs.sqlalchemy.org/en/rel_1_1/orm/events.html#instance-events


type_name in Type Of Work table optional

Issue name: “[Clarification / New feature / Question] — Summarize topic”
Summary
Based on the discussion during v2 development, I thought that the type_name in the types_of_work table was going to be optional.
Looking back at the original pull request before it was modified for the relational data model the comments refer to this being optional as well.
In Iowa I don't think we currently have the ability to provide the level of detail without making a lot of assumptions.
Proposed changes
Change type_name to optional

I just read through the original pull request and don't see where type_name was intended to be optional. In the original changes as well before it was modified, this field is required (see here).
I understand that some DOTs don't have the ability to provide the work type information, and that's fine, as the types_of_work field on the feed output (corresponding to the types of work table) is optional. There is no requirement to include any type of work information on the road event.
The only case where making type_name optional would have an impact is if a producer wants to supply is_architectural_change but can't give the type_name. In this case making type_name conditional (required if is_architectural_change is not specified) rather than optional makes more sense as both fields on the table should not be able to be optional as then there would be no reason to even include an entry. Is wanting to specify the is_architectural_change without giving the type_name the scenario you're talking about at Iowa?

I see now the statement "For every record in the road_event table there exists zero or more records in the types_of_work table" which makes it optional.  I was looking at the table and thinking it was required to give a type_name for every work zone.  I agree with your need to have this required.


Better explain how library works in README

Explain that libraries need folders as discussed in #4

fixed in 824e93c


Try switching travis to trusty

Description of the pull request:
Maybe this will fix the bizarro Travis failures that aren't really failures.

Nope. 😞
I also reran some builds from before 3 days ago that had passed. They also failed. Oh well...

Well, that's special. Hey Google! If anyone's wondering why their Travis build is failing even though it says
"Done. Your build exited with 0." build failed
It may well be because using set -e in your .travis.yml script causes some internal travis scripts that run after your build to exit with a non-zero. So, if Travis is failing your build even though it says it succeeded, try adding a ; set +e to the end of your script config.
Does Google even index GitHub comments?


Implementation of method of LagrangesDynamicSystem class for settlement of dynpy environment

The goal is to implement a method checking if there is dynpy library in dynamical system's directory. In case if there is no dynpy library, it appends it.

Done, issue can be closed.


Add patch to allow notification actions

Working on adding inline reply support, need to unlock the actions array so that users can construct a new notification with
new Notification(title, {
  actions: [
    type: 'text',
    title: 'Reply',
    action: 'reply'
  ]
})

This is just to generate the builds required to do the wiring in brightray

CI machines require some changes in chrome58 to work, let's wait until #280 gets merged.

@zcbenz Sorry forgot about this.  Decided that adding features through the Chromium model for Notifications was too restrictive to add all the potential options that are actually available on systems.
Stopped my work in brightray and moved it over to Electron itself in https://github.com/electron/electron/pull/9269


Signed-off-by: David Enyeart<EMAIL_ADDRESS>

Yeah, I've gone one more step and checked each of the tlsConfig fields one by one, the field that is not equal to the expected in the test is tlsConfig.ClientCAs:
  Expected
      <*x509.CertPool | 0xc00020fef0>: {
          byName: {
              "0/1\v0\t\x06\x03U\x04\x06\x13\x02US1\f0\n\x06\x03U\x04\n\x13\x03ORG1\x120\x10\x06\x03U\x04\x03\x13\tlocalhost": [0],
          },
          lazyCerts: [
              {
                  rawSubject: [48, 47, 49, 11, 48, 9, 6, 3, 85, 4, 6, 19, 2, 85, 83, 49, 12, 48, 10, 6, 3, 85, 4, 10, 19, 3, 79, 82, 71, 49, 18, 48, 16, 6, 3, 85, 4, 3, 19, 9, 108, 111, 99, 97, 108, 104, 111, 115, 116],
                  getCert: 0x1233c60,
              },
          ],
          haveSum: {
              [140, 33, 136, 64, 129, 79, 10, 109, 225, 226, 75, 100, 139, 59, 135, 240, 138, 73, 70, 24, 43, 241, 198, 223, 181, 105, 125, 83]: true,
          },
      }
  to equal
      <*x509.CertPool | 0xc00020f9e0>: {
          byName: {
              "0/1\v0\t\x06\x03U\x04\x06\x13\x02US1\f0\n\x06\x03U\x04\n\x13\x03ORG1\x120\x10\x06\x03U\x04\x03\x13\tlocalhost": [0],
          },
          lazyCerts: [
              {
                  rawSubject: [48, 47, 49, 11, 48, 9, 6, 3, 85, 4, 6, 19, 2, 85, 83, 49, 12, 48, 10, 6, 3, 85, 4, 10, 19, 3, 79, 82, 71, 49, 18, 48, 16, 6, 3, 85, 4, 3, 19, 9, 108, 111, 99, 97, 108, 104, 111, 115, 116],
                  getCert: 0x1233c60,
              },
          ],
          haveSum: {
              [140, 33, 136, 64, 129, 79, 10, 109, 225, 226, 75, 100, 139, 59, 135, 240, 138, 73, 70, 24, 43, 241, 198, 223, 181, 105, 125, 83]: true,
          },
      }

They look the same to me. Also checked in debugger right before the Equal() check and they looked the same to me.
Equal() does reflect.DeepEquals().
reflect.DeepEqual(expected.ClientCAs, tlsConfig.ClientCAs)
returns false for some reason.
Any ideas @sykesm ?


Can't resolve 'stream'

cohere-ai: 7.10.2
next.js: 14.2.3
node.js: 20.12.2
@botgen/chat:build: Module not found: Can't resolve 'stream'
@botgen/chat:build:
@botgen/chat:build: https://nextjs.org/docs/messages/module-not-found
@botgen/chat:build:
@botgen/chat:build: Import trace for requested module:
@botgen/chat:build: ../../node_modules/.pnpm/cohere-ai@7.10.2_@aws-sdk+client-sso-oidc@3.588.0_aws-crt@1.21.2__aws-crt<EMAIL_ADDRESS>@botgen/chat:build: ../../node_modules/.pnpm/cohere-ai@7.10.2_@aws-sdk+client-sso-oidc@3.588.0_aws-crt@1.21.2__aws-crt<EMAIL_ADDRESS>@botgen/chat:build: ../../node_modules/.pnpm/cohere-ai@7.10.2_@aws-sdk+client-sso-oidc@3.588.0_aws-crt@1.21.2__aws-crt<EMAIL_ADDRESS>@botgen/chat:build: ../../node_modules/.pnpm/cohere-ai@7.10.2_@aws-sdk+client-sso-oidc@3.588.0_aws-crt@1.21.2__aws-crt<EMAIL_ADDRESS>@botgen/chat:build: ./lib/cohere.ts
cohere-ai v7.9.5 works without problems

Easily fixed by installing the stream package, but this should probably be included in the package

+1
I had the same issue with<EMAIL_ADDRESS>and Next.js 14.2.3. Agree that the stream package should probably be included in the package.

hey folks thanks for flagging this, will add stream to package as you suggest!

Thank you, @billytrend-cohere! When will the next release come out? I couldn't find a note about release schedule in the Readme. Thanks again for solving this issue!

Released now!! please try 7.10.5 and let me know how it goes. I added a test case to prevent this situation happening in the future


import release 0.26 dependencies

@ZhiminXiang some tests are failing, but just curious: Why is the dependency not automatically updated by knobots ?

@ZhiminXiang some tests are failing, but just curious: Why is the dependency not automatically updated by knobots ?

not sure. I tried to kick out the automatic update from knobots, but could not successfully make it work.

The tests are now good. Ready for review.

/lgtm