Call super.notifyChange() in our abstract ViewModel class

May be the case of not having a DataModel attached to a ViewModel, but still we'd like to trigger BaseObservable properties for that very ViewModel in order to make the changes visible to the view.
Tested on the android-ui-components project which is making use of the ViewModel and DataModel that have been moved away from the main Wayfair project to BrickKit.

Codecov Report

Merging #87 into master will increase coverage by <.01%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##             master     #87      +/-   ##
===========================================
+ Coverage     88.59%   88.6%   +<.01%
  Complexity      471     471
===========================================
  Files            29      29
  Lines          1368    1369       +1
  Branches        222     223       +1
===========================================
+ Hits           1212    1213       +1
  Misses           76      76
  Partials         80      80

Impacted Files
Coverage Δ
Complexity Δ

...ain/java/com/wayfair/brickkit/brick/ViewModel.java
66.66% <100%> (+1.66%)
7 <1> (ø)
: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 5dfc084...c6aab80. Read the comment docs.


HexColorField accessibility review

📝 Feedback

The Popover examples demonstrate a need in the Color API for being able to determine the luminosity of a Color, the contrast ratio between one Color and another, and whether a particular color has sufficient contrast with another color to comply with the WCAG 2.1 1.4.3 Contrast (Minimum) or 1.4.6 Contrast (Enhanced) success criteria. This would allow a developer to change the foreground color of text to have sufficient contrast with a background color.

While I understand the choice to make the HexColorField a role="spinbutton", like the Hex color inputs in Google Chrome's Web Developer tools, I'm not sure that incrementing between 0 and 16,777,215 is particularly useful. Stepper functionality probably makes more sense when the input format is rgb, rgba, hsl, hsla, where its easier to distinguish between component parts of the color. There is a good example of this distinction in the inputs on https://contrast-ratio.com/, where, if the user inputs a hex value, using the ArrowUp or ArrowDown keys does not change the value.

With VoiceOver on iOS, role="spinbutton" makes it much harder to bring up the onscreen keyboard. Rather than a simple double tap, I have to double tap and hold to open the on screen keyboard. This is particularly problematic in the Popover stories, like https://reactspectrum.blob.core.windows.net/reactspectrum/32a59e198acd249536c92347767eedfcd3470590/storybook-17/index.html?path=/story/hexcolorfield--as-a-popover, because double tapping the HexColorField focused with the VoiceOver cursor within the Popover closes the popover. One can open the dialog and read the the text input, but when the user double taps to edit the text using the on-screen keyboard, the popover closes, because the field loses focus when the popover repositions.

We should use Content instead of View as the content slot for the Dialog in the Storybook story.

The validationState="valid" check image is not communicated in any way to assistive technology.

🌍 Your Environment

Software
Version(s)

@react-spectrum/color
3.0.0-alpha.1

Browser
All

Operating System
All

🧢 Your Company/Team
Adobe/Accessibility

See https://github.com/adobe/react-spectrum/pull/1285 for suggested fixes.


connecting to XXX has for failed

I used this script to build on Google's GCP server, it can't connect normally, the firewall is turned on, ubuntu 18.04
Tue Apr 07 01:11:48 2020 OpenVPN 2.4.0 x86_64-w64-mingw32 [SSL (OpenSSL)] [LZO] [LZ4] [PKCS11] [AEAD] built on Dec 27 2016
Tue Apr 07 01:11:48 2020 Windows version 6.2 (Windows 8 or greater) 64bit
Tue Apr 07 01:11:48 2020 library versions: OpenSSL 1.0.2i  22 Sep 2016, LZO 2.09
Enter Management Password:
Tue Apr 07 01:11:48 2020 MANAGEMENT: TCP Socket listening on [AF_INET]<IP_ADDRESS>:25342
Tue Apr 07 01:11:48 2020 Need hold release from management interface, waiting...
Tue Apr 07 01:11:49 2020 MANAGEMENT: Client connected from [AF_INET]<IP_ADDRESS>:25342
Tue Apr 07 01:11:49 2020 MANAGEMENT: CMD 'state on'
Tue Apr 07 01:11:49 2020 MANAGEMENT: CMD 'log all on'
Tue Apr 07 01:11:49 2020 MANAGEMENT: CMD 'hold off'
Tue Apr 07 01:11:49 2020 MANAGEMENT: CMD 'hold release'
Tue Apr 07 01:11:49 2020 Outgoing Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Tue Apr 07 01:11:49 2020 Outgoing Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Tue Apr 07 01:11:49 2020 Incoming Control Channel Encryption: Cipher 'AES-256-CTR' initialized with 256 bit key
Tue Apr 07 01:11:49 2020 Incoming Control Channel Encryption: Using 256 bit message hash 'SHA256' for HMAC authentication
Tue Apr 07 01:11:49 2020 TCP/UDP: Preserving recently used remote address: [AF_INET]35.xx.xx.87:1194
Tue Apr 07 01:11:49 2020 Socket Buffers: R=[65536->65536] S=[65536->65536]
Tue Apr 07 01:11:49 2020 Attempting to establish TCP connection with [AF_INET]35.xx.xx.87:1194 [nonblock]
Tue Apr 07 01:11:49 2020 MANAGEMENT: >STATE:1586193109,TCP_CONNECT,,,,,,
Tue Apr 07 01:11:50 2020 TCP connection established with [AF_INET]35.xx.xx.87:1194
Tue Apr 07 01:11:50 2020 TCP_CLIENT link local: (not bound)
Tue Apr 07 01:11:50 2020 TCP_CLIENT link remote: [AF_INET]35.xx.xx.87:1194
Tue Apr 07 01:11:50 2020 MANAGEMENT: >STATE:1586193110,WAIT,,,,,,
Tue Apr 07 01:11:50 2020 MANAGEMENT: >STATE:1586193110,AUTH,,,,,,
Tue Apr 07 01:11:50 2020 TLS: Initial packet from [AF_INET]35.xx.xx.87:1194, sid=63f09074 426c6b99
Tue Apr 07 01:11:52 2020 VERIFY OK: depth=1, CN=ChangeMe
Tue Apr 07 01:11:52 2020 Validating certificate key usage
Tue Apr 07 01:11:52 2020 ++ Certificate has key usage  00a0, expects 00a0
Tue Apr 07 01:11:52 2020 VERIFY KU OK
Tue Apr 07 01:11:52 2020 Validating certificate extended key usage
Tue Apr 07 01:11:52 2020 ++ Certificate has EKU (str) TLS Web Server Authentication, expects TLS Web Server Authentication
Tue Apr 07 01:11:52 2020 VERIFY EKU OK
Tue Apr 07 01:11:52 2020 VERIFY OK: depth=0, CN=server
Tue Apr 07 01:11:52 2020 Control Channel: TLSv1.2, cipher TLSv1/SSLv3 ECDHE-RSA-AES256-GCM-SHA384, 2048 bit RSA
Tue Apr 07 01:11:52 2020 [server] Peer Connection Initiated with [AF_INET]35.xx.xx.87:1194
Tue Apr 07 01:11:54 2020 MANAGEMENT: >STATE:1586193114,GET_CONFIG,,,,,,
Tue Apr 07 01:11:54 2020 SENT CONTROL [server]: 'PUSH_REQUEST' (status=1)
Tue Apr 07 01:11:54 2020 PUSH: Received control message: 'PUSH_REPLY,redirect-gateway def1 bypass-dhcp,dhcp-option DNS <IP_ADDRESS>,dhcp-option DNS <IP_ADDRESS>,route-gateway <IP_ADDRESS>,topology subnet,ping 10,ping-restart 120,ifconfig <IP_ADDRESS> <IP_ADDRESS>,peer-id 0,cipher AES-256-GCM'
Tue Apr 07 01:11:54 2020 OPTIONS IMPORT: timers and/or timeouts modified
Tue Apr 07 01:11:54 2020 OPTIONS IMPORT: --ifconfig/up options modified
Tue Apr 07 01:11:54 2020 OPTIONS IMPORT: route options modified
Tue Apr 07 01:11:54 2020 OPTIONS IMPORT: route-related options modified
Tue Apr 07 01:11:54 2020 OPTIONS IMPORT: --ip-win32 and/or --dhcp-option options modified
Tue Apr 07 01:11:54 2020 OPTIONS IMPORT: peer-id set
Tue Apr 07 01:11:54 2020 OPTIONS IMPORT: adjusting link_mtu to 1626
Tue Apr 07 01:11:54 2020 OPTIONS IMPORT: data channel crypto options modified
Tue Apr 07 01:11:54 2020 Data Channel Encrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue Apr 07 01:11:54 2020 Data Channel Decrypt: Cipher 'AES-256-GCM' initialized with 256 bit key
Tue Apr 07 01:11:54 2020 interactive service msg_channel=880
Tue Apr 07 01:11:54 2020 ROUTE_GATEWAY <IP_ADDRESS>/<IP_ADDRESS> I=2 HWADDR=34:e1:2d:98:xx:e6
Tue Apr 07 01:11:54 2020 open_tun
Tue Apr 07 01:11:54 2020 MANAGEMENT: Client disconnected
Tue Apr 07 01:11:54 2020 There are no TAP-Windows adapters on this system.  You should be able to create a TAP-Windows adapter by going to Start -> All Programs -> TAP-Windows -> Utilities -> Add a new TAP-Windows virtual ethernet adapter.
Tue Apr 07 01:11:54 2020 Exiting due to fatal error

This doesn't seem to be firewall related, the issue is in your client.
Remove your existing client software and install the latest client from the OpenVPN website.


feat: 🎸 check if compliance requirements are paused

JIRA Link
https://polymesh.atlassian.net/browse/DA-64
Changelog / Description
adds endpoint for checking if compliacne requirements are paused for an Asset
Checklist -

[x] New Feature ?
[x] Updated swagger annotation (if API structure is changed) ?
[x] Unit Test (if possible) ?
[x] Updated the Readme.md (if required) ?

:tada: This PR is included in version 2.2.0-alpha.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


[FEATURE] Add stratified train_valid_split similar to sklearn.model_selection.train_test_split

Description
I added the ability to perform a stratified split in train_valid_split
Checklist
Essentials

[X] PR's title starts with a category (e.g. [BUGFIX], [MODEL], [TUTORIAL], [FEATURE], [DOC], etc)
[X] Changes are complete (i.e. I finished coding on this PR)
[X] All changes have test coverage - I'm not too familiar with test writing, but if you can direct me to a tutorial I'd be happy to get it done.
[X] Code is well-documented

Changes

[X ] stratify option for test_valid_split, test_utils.test_train_valid_split
[ ] Feature2, tests, (and when applicable, API doc)

Comments
Backwards compatible, the only edge case I can think of is if someone tries to use a float to stratify their data and end up getting non-sense results.
cc @dmlc/gluon-nlp-team

Job PR-933/1 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-933/1/index.html

Thanks for your patience, I don't see any tests for the functions within gluonnlp.data.utils should I create a new file under the unittest folder? or is there already a file I should modify with a test for train_valid_split?
Thanks!

Job PR-933/2 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-933/2/index.html

@colinkyle let's put the test in tests/test_utils.py for now. Or if you prefer to create a new file for it we can do that too.

Job PR-933/3 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-933/3/index.html

Job PR-933/4 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-933/4/index.html

Is this going to move forward? I'm not sure where we are with review.

@colinkyle. It will be merged once it passed the CI.

@szhengac thanks for the update.

@leezu the CI error is related to downloading a dataset. It seems that we have seen it in other pr before?

I think we should just rebase and merge.

Job PR-933/16 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-933/16/index.html


Add Travis CI

Travis CI is free for open source projects. Setup is pretty easy, and the benefits are great.
Setup:
• Add .travis.yml file to the root of this project (example: https://github.com/louisdh/terminal/blob/master/.travis.yml)
• Go to https://travis-ci.org, log in with GitHub and enable this project

Done for iOS_system and libssh2 (see https://github.com/holzschu/libssh2-for-iOS). Required some changes in the Xcode project to make sure we only access local files. Do you want me to propagate those changes to the version of iOS_system in OpenTerm?


Use SN_API deprecated class in the feeder client

Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

Cargo.toml line 64 at r1 (raw file):
Previously, yair-starkware (Yair) wrote…
Is this intentional?

Yes (Deserialize junk ABI as None)


fix: add missing comma in a example

Came here to open the same PR :)
@tamago324 PTAL 🙏🏻

Thanks!


Fix a build failure on Windows, where NAME_MAX doesn't exist

Motivation
Fix build break on Windows due to absence of NAME_MAX.

@swift-ci test

This still breaks, I think I have a fix, I'll upload it in a minute.

Thanks.  I think I just need to wrap the unit test in a condition too.

@compnerd Conditionalized the unit test too.  That should be it.

@swift-ci please test

We do have other uses of NAME_MAX, but I didn't notice that they're inside big conditionals.


Failed to get rowCount and pageCount for pagination with lodash 4.17.1

I use npm dependencies with ~ so accidentally 4.17 has been updated.
With Lodash v4.17 the plugin returns NaN for rowCount and pageCount.
code
Model
  .query(qb => {
    qb.select('*');
    qb.where('state', 'ACTIVE');
  })
  .orderBy('id', 'DESC')
  .fetchPage({
    page: 1,
    pageSize: 10,
  })
  .then(raw => {
    console.log(raw.pagination);
    return raw;
  })

result
{ page: 1, pageSize: 10, rowCount: NaN, pageCount: NaN }

I'm also getting the same thing... Does anyone know which dependencies don't break things so I can at least have something working while I develop (until this gets fixed) ? ie - what release broke this?

Nevermind, running npm install<EMAIL_ADDRESS>fixed it for me.

@carldanley You can still use 4.16.6
{
  "lodash": "~4.16.6",
}

still happened on lodash 4.16.6.

I got the same issue, it seems like fetchPage method conflicts with Bookshelf's parse method. When I comment out parse method, all things get right.


Write Test For WriteString and ReadString #37 solved

I've added tests for the above mentioned functions in the "memoria_test.go" file. The tests ran successfully.  I'm attaching the final code code. Kindly review!

Sir, due to some problem, my changes for issue #8 Learn and Teach: Mutexes have been pushed here itself. Kindly review and merge them, sir!


fix: adds missing permsions to the 'eks-workshop-ide-ec2' IAM policy

What this PR does / why we need it:
This PR resolves the IAM issue reported here https://github.com/aws-samples/eks-workshop-v2/issues/1106
Without this change the following command fails which makes learning about EFS incredibly frustrating.
prepare-environment fundamentals/storage/efs

Which issue(s) this PR fixes:
Fixes # https://github.com/aws-samples/eks-workshop-v2/issues/1106
Quality checks

[ ] My content adheres to the style guidelines
[ ] I ran make test module="<module>" it was successful (see https://github.com/aws-samples/eks-workshop-v2/blob/main/docs/automated_tests.md)
[ ] The PR has meaningful title and description of the changes that will be included in the workshop release notes

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

I've tested this by applying the IAM change manually. Testing changes to the ide aren't mentioned in https://github.com/aws-samples/eks-workshop-v2/blob/main/docs/automated_tests.md and fall into the What if my module can't be tested? camp.
Please advise.


Why Does gyro2bb Report "Unsupported File Format" for MP4 Files?

I am encountering an issue with gyro2bb. When I try to process an MP4 file that I converted from an Insta360 .insv file using Insta360 Studio, the following error is displayed:
thread 'main' panicked at gyro2bb.rs:38:113: called Result::unwrap()on anErrvalue: Custom { kind: Other, error: "Unsupported file format" } note: run withRUST_BACKTRACE=1environment variable to display a backtrace
I used Insta360 Studio to export the file with stabilization turned off, and I selected the MP4 format. Since MP4 is listed as a supported format, I’m unsure why this error occurs.
Could you clarify if there are specific requirements for MP4 files to be processed (e.g., encoding format, metadata retention)? Or does this tool require the native .insv file instead?
Thank you for your help!

The metadata is not preserved when converting. You have to use the original insv file


incorrect error highlighting

when importing a module it does not recognize * as a way of importing the entirely of that module, it makes you add in all of the components  you call.

above is the importing of the module

here's an example of what some of the errors are.
if you would like to try out my code and see what the issue is, you can do so here under its repo:
link to my code code with the highlighting issues
it runs 100% fine too without this and I even asked the instructor from the class I am taking about this, and they said it was the proper way of doing it.
EDIT: fixed broken link

Closed for inactivity, it appears this project's development has been abandoned.
either way this is no longer an issue so thanks for the help?


Support TypeScript 4.6

Search Terms
typescript 4.6
Problem
typescript 4.6 was released last night, but this module is not compatible with it as 4.6.x is not in the list of compatible versions:
npm ERR! Could not resolve dependency:
npm ERR! peer<EMAIL_ADDRESS>|| 4.1.x || 4.2.x || 4.3.x || 4.4.x || 4.5.x" from<EMAIL_ADDRESS>
Suggested Solution
please add support for typescript 4.6!

I should get to this this weekend :)

Support released in v0.22.13, no changes were necessary on TypeDoc's part besides marking it as supported, so if you're stuck on an old version it should still work.

typedoc version 0.22.13 still gives the warning on typescript 4.6.0.
Package.json snippet:
{
  ...
  "devDependencies": {
    ...
    "typedoc": "~0.22.13",
    ...
    "typescript": "<=4.6.0"
  },
  ...
}

Log message:
=============

WARNING: You are currently running a version of TypeScript which is not offici
ally supported by @typescript-eslint/typescript-estree.

You may find that it works just fine, or you may not.

SUPPORTED TYPESCRIPT VERSIONS: >=3.3.1 <4.5.0

YOUR TYPESCRIPT VERSION: 4.5.5

Please only submit bug reports when using the officially supported version.

=============

Also relevant:
🐟 ❯ yarn typedoc --version
yarn run v1.22.17
$ /.../node_modules/.bin/typedoc --version
Info: Loaded plugin typedoc-plugin-mdn-links

TypeDoc 0.22.13
Using TypeScript 4.5.5 from ./node_modules/typescript/lib

Done in 1.01s.

Nevermind - there were multiple packages with a similar error. You can ignore my previous post.


fix(console): update dependencies, use prettier as default linter, refresh on policy change

@peintnermax is this ready for review?

yes 👍


Not Inserting text

I'm having a problem with quill-mention and react-quill.
The lists of options populate fine, and I'm able to search and select options, but when I select an option the tag is not inserted into quill. Quill will only show that a new paragraph has been added, but no other content is added.
`mention: {
allowedChars: /^[A-Za-z0-9_\sÅÄÖåäö]*$/,
mentionDenotationChars: ["@", "#"],
isolateCharacter: true,
source: function (searchTerm, renderList, mentionChar) {
let values;
			if (mentionChar === "@") {
				values = mentionList;
			} else {
				values = tagList;
			}

			if (searchTerm.length === 0) {
				renderList(values, searchTerm);
			} else {
				const matches = [];
				for (var i = 0; i < values.length; i++)
					if (~values[i].value.toLowerCase().indexOf(searchTerm.toLowerCase())) matches.push(values[i]);
				renderList(matches, searchTerm);
			}
		},
	},`

I have the same issue using quill-mention with VueJS using the sample config from the readme: https://gist.github.com/nemmons/a18674264984c07afed8d1430fcb0c60

same here

How are you defining the modules in react-quill?

I probably should have attached the file to begin with.
Editor.txt

I'm now having this issue, nad have added mention to the formats list:
<ReactQuill
  theme="snow"
  value={quillValue.text}
  onChange={(e) => setQuillValue({ text: e })}
  modules={{ mention: mentionModule }}
  formats={[
    'header',
    'font',
    'size',
    'bold',
    'italic',
    'underline',
    'strike',
    'blockquote',
    'list',
    'bullet',
    'indent',
    'link',
    'image',
    'video',
    'mention',
  ]}
/>

And here is my current mentionModule:
  const mentionModule = {
    allowedChars: /^[A-Za-z\s]*$/,
    mentionDenotationChars: ['@'],
    source: (searchTerm: string, renderList: (data: any, searchText: string) => void) => {
      const mentionsToList = atValues.filter(
        (av) => av.value.toLowerCase().indexOf(searchTerm.toLowerCase()) > -1
      );
      if (mentionsToList.length > 0) {
        renderList(mentionsToList, searchTerm);
      }
    },
  };

Was kind of a pain getting it to work typescript but I got there.
Anyone have any suggestions?

:+1:


multiple definitions of cl::sycl::program::get_kernel

With the latest master, when I am linking multiple files with SYCL kernels in them together, I am getting multiple definitions linker errors
/home/ireguly/OP2-Common/op2/c/lib/libop2_sycl.a(op_sycl_rt_support.o): In function ~_Sp_counted_ptr_inplace': /usr/local/bin/../include/CL/sycl/kernel.hpp:141: multiple definition of cl::sycl::program::get_kernel(std::__cxx11::basic_string<char, std::char_traits, std::allocator >) const'
/tmp/airfoil_kernels-31c8a3.o:airfoil_kernels.cpp:(.text+0x0): first defined here
This was not present with 46216fe

Thanks for reporting! We should probably add a test case for linking several source files and catch such regressions. I'll fix ASAP.

Could you please confirm if PR #86 fixes the issue?

Yes, that seems to have done the trick - thank you!


Minimum number of observations for gcm.distribution_change

In your rca_microservice_architecture notebook, 10,000 and 1,000 observations are used for normal and outlier data respectively. What are the minimum numbers of observations recommended for both datasets in order to get a good result? I used 1,000 and 100 and still got a correct result. The function requires both datasets to have at least 6 observations. But obviously using 6 will yield poor and unstable results.

TL;DR: There is no definitive answer here.
Ignore this detail if you already know this: Each node in the causal graph is assigned a generative model describing how its values are generated from its parents. Take the causal graph $X \to Y$ as an example. If we assign a linear additive noise model as the generative model of $Y$, i.e., $Y := aX + N_Y$ where $N_Y$ is the unobserved noise of $Y$, we need to estimate the coefficient $a$ from data.
The required sample size for distribution change depends on the type of causal mechanisms and the number of parents (direct causes) of nodes. Surely, we can learn a linear regression with fewer samples (100s), but even that is challenging when the number of features (here, number of parents) is large (due to the curse of dimensionality). Non-linear mechanisms do not make the situation any easier. In general, the larger the sample size the better.

Thank so much for the clear explanation!


Task "wait for zookeeper to listen" failed

Here is the problem:
NOTIFIED: [zookeeper | wait for zookeeper to listen] **************************
failed: [mi-control-02] => {"changed": true, "cmd": ["/usr/local/bin/zookeeper-wait-for-listen.sh", "mi-control-02"], "delta": "0:01:00.401821", "end": "2015-07-04 15:29:18.837220", "rc": 1, "start": "2015-07-04 15:28:18.435399", "warnings": []}
failed: [mi-control-01] => {"changed": true, "cmd": ["/usr/local/bin/zookeeper-wait-for-listen.sh", "mi-control-01"], "delta": "0:01:00.409336", "end": "2015-07-04 15:29:18.845431", "rc": 1, "start": "2015-07-04 15:28:18.436095", "warnings": []}

Some basic debugging:
[root@mi-control-01 ~]# echo ruok|nc mi-control-01 2181
[root@mi-control-01 ~]# echo $?
0
[root@mi-control-01 ~]# nc mi-control-01 2181
ruok
imok
^C
[root@mi-control-01 ~]# telnet mi-control-01 2181
Trying <IP_ADDRESS>...
Connected to mi-control-01.
Escape character is '^]'.
ruok
imokConnection closed by foreign host.
[root@mi-control-01 ~]#
[root@mi-control-01 ~]# echo ruok|nc mi-control-01 2181
[root@mi-control-01 ~]#

So mi-control-01 is pointed to <IP_ADDRESS> and that is the problem. We need to clean up that line from /etc/hosts. There was something similar done for DigitalOcean provider (I use OpenStack): roles/common/tasks/digitalocean.yml
I think we could add such check for all providers.

https://github.com/CiscoCloud/microservices-infrastructure/pull/552

+1 Currently blocking my progress.

@kenjones-cisco we'll test and see if there are any issues

I just copied the changes to a branch on my fork, and I'm testing currently on Openstack to make sure it does resolve the issue(s) I've been seeing.

Worked like a charm
PLAY RECAP ********************************************************************
dnsmasq | install packages --------------------------------------------- 56.51s
common | install pip --------------------------------------------------- 39.72s
mesos | install mesos package ------------------------------------------ 38.14s
marathon | install marathon package ------------------------------------ 37.53s
docker | install docker ------------------------------------------------ 37.49s
consul | restart consul ------------------------------------------------ 32.37s
common | install system utilities -------------------------------------- 32.17s
logstash | ensure logstash docker image is present --------------------- 29.90s
zookeeper | ensure zookeeper docker image is present ------------------- 25.59s
marathon | ensure job docker images are present ------------------------ 20.61s
cchub-control-01           : ok=211  changed=179  unreachable=0    failed=0
cchub-control-02           : ok=211  changed=179  unreachable=0    failed=0
cchub-control-03           : ok=211  changed=179  unreachable=0    failed=0
cchub-worker-01            : ok=117  changed=102  unreachable=0    failed=0
cchub-worker-02            : ok=117  changed=102  unreachable=0    failed=0
cchub-worker-03            : ok=117  changed=102  unreachable=0    failed=0
localhost                  : ok=0    changed=0    unreachable=0    failed=0

Closing with #552 merge.


Information about Virtual Machines removed from testnets.cardano.org

Hi,
I just noticed that the sites we link from Virtual-machines-and-programming-languages for KEVM, IELE, and EVM have been removed from testnets.cardano.org.
I couldn't find any new pages, and IO confirmed they had been removed.
How could we re-write this section?

IMO - it's not a good idea to document anything that's not yet ready for mainnet integration, as historically - months/years of efforts spent over a specific project/path has been ditched due to feasability/complications/efforts/.. etc.

@rdlrt What is your suggestion? Just removing KEVM, IELE and GLOW?

@rdlrt What is your suggestion? Just removing KEVM, IELE and GLOW?

Yip

@thenic95 can we close this?

Absolutely!


Trailing whitespace removed when copying password to clipboard

Summary
Hi there. I just found that whenever a secret has a trailing whitespace, copying as gopass show -c test_secret doesn't copy the whitespace. Showing the secret without copying prints the secret correctly. Also, intermediate whitespaces work fine.
Is this known / intentional? Perhaps having a trailing whitespace is not an expected use case.
Steps To Reproduce
Create a new secret with a trailing whitespace (e.g., supersecure ). Try copying with gopass show -c test_secret.
Expected behavior
supersecure  ends up on the clipboard.
Environment

OS: Manjaro Linux
OS version: Linux 5.10.211-1-MANJARO #1 SMP PREEMPT Fri Mar 1 16:55:20 UTC 2024 x86_64 GNU/Linux
gopass Version: gopass 1.15.11 go1.21.4 linux amd64
Installation method: yay

Correct. We currently do not support passwords with leading or trailing whitespaces: https://github.com/gopasspw/gopass/blob/master/pkg/gopass/secrets/akv.go#L253

Since key-value pairs are only key: value, with a single space (see kvSep), it must be fine to remove TrimSpace and just remove the first character instead. Do you mind if I check in a PR for that?

Done :)
See PR #2954

Great to see this in!


Undo/Redo: hook up action ends to addCurrentStateToUndoStack()

simplify the two stacks to one with an index pointing at current state


Implements #3692 - First round of ConsoleDriver cleanup

OK, so I'm cutting the first round of this off here.
It's ready for y'all to have a look at it, but it's not ready to merge because I need to finish committing a couple of build-related tweaks, which I'll get to when I wake up.
There are various TODO-style comments I dropped here and there in it. Most are notes for myself for future rounds of this work.
Fixes

Fixes #3692

Proposed Changes/Todos

[x] Clean up/reduce Win32 PInvokes.
[x] Switch to using FileStream under the hood for NetWinVTConsole.
[x] Various fixes to tests and incidentally related types.
[x] Add some test helpers for providing drivers to test methods.
[x] Misc cleanup, doc improvements, and optimizations.

Pull Request checklist:

[x] I've named my PR in the form of "Fixes #issue. Terse description."
[x] My code follows the style guidelines of Terminal.Gui - if you use Visual Studio, hit CTRL-K-D to automatically reformat your files before committing.
[x] My code follows the Terminal.Gui library design guidelines
[x] I ran dotnet test before commit
[x] I have made corresponding changes to the API documentation (using /// style comments)
[x] My changes generate no new warnings

[x] My changes address a ton of warnings from a stricter analysis level.

[x] I have checked my code and corrected any poor grammar or misspellings
[x] I conducted basic QA to assure all features are working

Looks like there are also some i18n issues in CI for some tests that I'll need to address.

Loving this! See my comments.

Will have a look when I'm back home.
I'm semi-out and about for the long weekend. 🥳

Test failure in CI was a case-sensitivity issue. VS created the resource file with "es-mx", but the test expected "es-MX".
Fixed.

Alrighty round 1 ready to go.
Many of the last several commits were largely the cleanup I mentioned earlier, like addressing notes to myself and formalizing some stuff.
Next up, I have an already partially completed branch that continues work on the driver-level stuff - in particular, making the API consistently usable and extensible internally and externally, which then will lead to more goodies in the next phases that will make life easier in TG, the tests, and for consumers, and will finally de-couple at least that area of the API from the internal implementation.

(@BDisp, I imagine a lot of our translations for es-MX and pt-PT will end up being at least similar, so that might save us a little mental load whenever we do any localization work.)

Not really, they are very different. Maybe some Spanish user can do that translation someday. Why did you chose the es-MX instead of the es-ES, which is more universal?

(@BDisp, I imagine a lot of our translations for es-MX and pt-PT will end up being at least similar, so that might save us a little mental load whenever we do any localization work.)

Not really, they are very different. Maybe some Spanish user can do that translation someday. Why did you chose the es-MX instead of the es-ES, which is more universal?

I picked MX because that's the dialect I know. 🤷♂
Certainly closer to es-ES than to Portuguese, of course.
It's like... More of a difference than between en-UK and en-US but less than between es-* and pt-*.

I'm going to rebase this on current v2_develop in a minute.
Stay tuned.

Rebased and ready again. 👌

Strike that. One more commit to rebase on top of.

There we go. All up to date now. All systems go for review/merge 🟢

Hm.
Not sure why the CI runner failed on that.
I'll force push again in case I missed something, since it runs just fine here. 🤔

There's broken file history and git did not deal with it well at all.
I'm bisecting to track down where the change happened and which code should actually be in use.

Yep.
That's exactly what it is.
This merge commit is where things change, but it was one of the busted merges that rewrote all history up to that point.
This commit has the correct code for the method that is breaking in CI after the rebase.
During rebase, since there was a change dependent on related history, git tried to trace it back to the right point in the graph, but failed miserably.
From what I'm looking at, it actually looks like a potential git bug, triggered by the specific situation created by the disconnected graph.
To test, I rebased on an earlier commit and the proper history was chosen. Then I rebased again on HEAD of v2_develop, and it failed in exactly the same way. Fun times.
I'm going to have to manually fix it, but that's essentially just rolling back to the previous commit, grabbing the file with busted history, rolling back forward, and pasting it over the broken one, effectively restoring it to before my changes. Then I can re-apply my changes and make it all happy again.

Important note about that.
If you merge one of those old branches or anything that started before them into your branch, you WILL cause these sorts of regressions and breakages, and they may not be shown as diffs. The only way to prevent that is to rebase on current code, rather than merge the old code into yours.
Unfortunately, that even means merging v2_develop into your branch, if the last common parent for an affected conflicting file was at one of those earlier points in the graph.
(In case you needed a stronger technical reason to rebase rather than merge.)

@tig:
What is the purpose/function of this?
    private static ConsoleModifiers GetModifiers (ConsoleModifiers modifiers)
    {
        if (modifiers.HasFlag (ConsoleModifiers.Shift)
            && !modifiers.HasFlag (ConsoleModifiers.Alt)
            && !modifiers.HasFlag (ConsoleModifiers.Control))
        {
            return ConsoleModifiers.Shift;
        }

        if (modifiers == (ConsoleModifiers.Alt | ConsoleModifiers.Control))
        {
            return modifiers;
        }

        return 0;
    }

That's part of the code with busted history. And it is puzzling since it doesn't really seem to do what its name would suggest.
The version of that method that exists for much more of history (including up until the original base for this branch) is:
    /// <param name="alt">The alt key.</param>
    /// <param name="control">The control key.</param>
    /// <returns>The console modifiers.</returns>
    public static ConsoleModifiers GetModifiers (bool shift, bool alt, bool control)
    {
        var modifiers = new ConsoleModifiers ();

        if (shift)
        {
            modifiers |= ConsoleModifiers.Shift;
        }

        if (alt)
        {
            modifiers |= ConsoleModifiers.Alt;
        }

        if (control)
        {
            modifiers |= ConsoleModifiers.Control;
        }

        return modifiers;
    }

Which actually does what it says.

Avoid rebasing as possible, doing it can cause a lot of headaches. Merge instead. I only need to rebase after a PR was already merged and before I try delete the local branch, I get a warning that there are unsaved changes. In this case I need to rebase to restore the remote branch history. If there is no incoming nor outcoming and I successfully delete the local branch, then everything went fine. With PR that aren't yet merged I normally merge the remote with my local branch. The GitHub Update Branch button actually does the merge the remote fork into the PR branch.

Avoid rebasing as possible, doing it can cause a lot of headaches. Merge instead. I only need to rebase after a PR was already merged and before I try delete the local branch, I get a warning that there are unsaved changes. In this case I need to rebase to restore the remote branch history. If there is no incoming nor outcoming and I successfully delete the local branch, then everything went fine. With PR that aren't yet merged I normally merge the remote with my local branch. The GitHub Update Branch button actually does the merge the remote fork into the PR branch.

That's what caused the problem in the first place.
Don't merge outward.
If you have a problem in the rebase, it's precisely because of this kind of thing and means something broke that you're not being shown, and it needs to be fixed. A merge will not show you that. A rebase will. That's why this appeared. Otherwise, it would have silently been a regression of some pretty important code across several files.

Now...
If we didn't have that history problem from before the PR merge process was fixed, it would mostly not matter and be fine either way.
But we do have that history to contend with, until such time as there is no longer a direct link (via more merges) back to that point in time.

There is something we can do that would give us a clean starting point. But it would require outstanding work to be rebased on top of that.
The only solutions to the original problem and the issues that it will continue to create occasionally all require you to rebase anything with common parents that are direct descendants of squash merges on something that has an explicit full file rewrite (not a partial diff) after that point.

Github actually also has an option at the repository level that can be set to help prevent (though not necessarily totalle eliminate) bad merges like that.
It's called something like "Require linear commit history."
It would disallow most merges that are likely to result in these sorts of problems. I suspect it would have prevented merge of the commit that I rebased this on top of, in fact.

I'll have to fix this in a little bit. I have some other stuff to attend to right now. I'll mark as draft again until I come back to it later this afternoon.

I'm going to leave the version of that method that takes and returns ConsoleModifiers in the code, since it is used. But I'm going to rename it based on what it appears to do. Feel free to hate one the name/suggest alternatives.
I'm thinking something like FilterModifiersForScanCode.

Fixed and confirmed repeatable results with a fresh branch from both deadd5bdb4ed2e3faa1fe6e339276ca5df4789b5 and 56d9c5948465c44939ca3e80f65c4fbdace473b5, each performed on fresh clones of the repo at those points.

There we go. That's more like it.
Yeah, it was interesting to see how, even though I never touched the ConsoleModifiers overload of that method, git decided it was the same thing in the diff and removed both.
Adding it back in along with the fact that that file has been pretty much entirely rewritten due to splitting out types to their own files should at least protect that file from that kind of problem again unless some really old branch happens to get merged over it again and a conflict isn't resolved by taking the whole file from the newer version.

The GitHub Update Branch button actually does the merge the remote fork into the PR branch.

That behavior is configurable. You can have it fast-forward, merge, or rebase.
The safest and most formally "correct" thing to do to ensure linear history is to first update your fork's v2_develop branch, fetch/pull it locally on your machine to sync, and rebase your work branch on top of that.

That behavior is configurable. You can have it fast-forward, merge, or rebase.

For me is the best behavior.

The safest and most formally "correct" thing to do to ensure linear history is to first update your fork's v2_develop branch, fetch/pull it locally on your machine to sync, and rebase your work branch on top of that.

That is what I do, less the rebase where I use merge when the local branch wasn't yet merged into the mainline branch.

Ensuring that you always only fast-forward the mainline branch that you branched from prevents cycles in the graph.

What matter, is the mainline branch history. When I said before that sometimes I get the warning that I have unsaved changes on my local branch that already was merged into the mainline branch, when I try to delete it, then in these cases I have to rebase to ensure that is everything well. After doing it I don't see any changes and finally I can delete my local branch. Sometimes the difference is some merge ID in my local branch that isn't equal to the mainline branch, but the changes contained on it are the same on both branches and so, it's commit ID that is conflicting and fixed by the rebase.

There's a bunch of warnings that need to be cleaned up too.
E.g.

Yep. Fully intend to deal with them. 👍
Similar to a PR series I did a while back and one you did some time after that, this one is, well, a series, and stuff like that might get spread across a couple branches, in my attempt to keep the individual PRs a bit more contained.
In fact, a fair number of them have already been addressed in files that are currently either in my current working branch or stashed for a future branch where they'll get popped off to be with their friends.
So, mind if, for this PR, I just backport the ones under the new Windows interop types and shore up the rest a bit more targeted, like that?
Especially since, aside from BOOL, PInvoke, ITrueFalseOperators, and CONSOLE_MODE, they're not actually new code in those new files - just relocated existing code that always had the problems in the warnings.
And also some will be addressed by code getting ripped out or otherwise fundamentally altered. CONSOLE_MODE and anything related to it is one big example that comes to mind, because it's being replaced wholesale by a struct, which was always the end goal, but the enum is a convenient placeholder for the constants that doesn't take that much work to turn into a proper and intelligent type once more important bits are finished. Which happens to be in the branch I'm currently working on, where warnings in that file are gone and it's a green light up top now that it's finished in my second branch.
That's going to happen to other things as well, for sure, before all of these are over.
Don't worry. I'm more anal about warnings than anyone here. That's why I keep slowly turning things up - to boil that frog. 😉
And the rest of this is just me explaining my thought process, my work processes around warnings/general code quality (hey - the issue is named about that!) and pointing out some commit comments, plus probably some repeated bits from frustratingly and stupidly allowing my laptop battery to die and then writing half as much as a less fun replacement.[^sorry][^youDontHaveToBeTHATRelieved]
I have a LOT more than these turned on in my local project and solution .user files. Man, you should see the miles of yellow my builds give. And that's just from the built-ins from using the "recommended" AnalysisLevel for .net 8 and c# 12. And then the sea of red squiggles in a lot of code files for stuff I have turned up to error level in my local settings, so a code file I have open will block a build while it's open if it has any, but allow the build if it's closed (that only care if it's open behavior is a setting in R# and I think also even VS itself now and I love it).
Amusingly, because of that, I actually resolved more warnings in this code, at the higher analysis setting, despite the few new ones you see there. 😅
So rest assured - I ain't ignoring them and fully intend to address any I cause and plenty I didn't cause, though I also may intentionally leave one in on occasion, if it points out something unrelated that really should be addressed.
Actually, I've also been un-suppressing some warnings in code that absolutely should not have been suppressed - some of which have a stated reason that is significantly worse than a very legitimate build warning.

[^sorry]: Sorry. It was better and unfortunately my annoyance at myself wrecked the tone I meant for it to have, I think. My bad.
[^youDontHaveToBeTHATRelieved]: But hey, at least now you only have a short story to read instead of an epic.

Actually... Some of those changes can just be moved in the commit graph as I rebase it on the most recent head of v2_develop, so I'll do that to knock out a couple that fit well in this one anyway.
...And I'm sure I'll probably then end up fixing more of them over again since they're mostly pretty simple or back-porting some others. So you might get more quicker gratification than I was assuming was likely.
Gimme a bit. Dinner time. 🙂

Wait. Nevermind. That's you guys merging stuff on your branches. This is already based on head of v2_develop. 😅
I still will go ahead and reorder some of those commits, where they can be safely reordered, though. I'll probably get working on that in like an hour I imagine.
But do expect there to potentially be others in subsequent intermediate branches, since I'm trying to avoid writing stuff I'm not certain will still be there when I'm done, unless I have to a part of keeping changes smaller and safer. 🤷♂
But again they are all meant to be resolved by the end of the series, for sure, so go right on ahead pointing them out if you like, and if it's not terribly disruptive to whatever I'm working on I'll probably address some right away anyway. But make it bleed in whichever ones I start marking as the end of the series.
Right now I'm thinking it's gonna be maybe 5 branches total, counting this one? We'll see as things evolve.
Quick anecdote about red squiggles:
I authored a mod for a little while in the earlier days after release of Starfield, then entire purpose of which was to deal with spelling and grammar errors.
The logo icon was the name of the game misspelled, with a red squiggle. 😅
Made several hundred edits by the time I got bored with it and started having an affair with Cyberpunk  behind its back. Sshhh. Don't tell it.

Cherry-picked several commits that can go in this one.
Did a little bit more work on top of it, which resolves several warnings, but also adds some analysis-related stuff that will cause more, too.
Also fixed a bug for opening "stderr" in Windows, which isn't actually its own stream.

I think I'm done with this one for now. I went back to working on continuing work on the next branch, so this one is ready as far as I'm concerned.
Pretty big improvements and consolidation already happening with WindowsDriver/WindowsConsole, so far. 😃

Oh and a minor informational side note:
I also loaded the code of this PR up in Rider on Windows and Ubuntu 24.04.1 to make sure things are still friendly to it, and to make sure tests also work in it as expected.
Went well. I didn't encounter any trouble, so looks like we're still good in Rider.
And I gotta say.... While I still don't care for Rider's overall environment, as it still feels perplexingly less capable than ReSharper somehow, it does work really well in the testing and debugging of testing.
The test runner, its output, the UI around testing, and especially coverage, profiling, and debugging of unit tests in this solution in particular do seem to work more reliably in Rider than it does in VS, on those two machines. 🤷♂

(I had accidentally posted the above over on the issue yesterday. Meant for it to go here.)

Know what?
In light of some of the stuff I talked about in the issue for this, I'mma actually close this PR for right now, because I'm thinking a somewhat different approach is going to work a lot better, especially when giving consideration to abstraction and such.
I'll just open a new one when I have a useful checkpoint ready for merge.


coc-tsserver error redrawtime

Error: redrawtime exceeded syntax highlighting disabled

Should not be caused by this extension which doesn't do syntax highlighting. https://github.com/neoclide/coc.nvim/wiki/F.A.Q#how-could-i-profile-vim


⚠ Bofrost.de has degraded performance

In 52592cb, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 822 ms

Resolved: Bofrost.de performance has improved in c733b2a.


Profile

What this PR does / why we need it:
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:
Release note:

Too many conflicts, so i will close this and i will raise a new PR.


API aktualisiert Begegnungen nicht

In den Google Einstellungen wird werden 0 Überprüfungen angezeigt und in der App selbst das diese heute früh überprüft worden sind.

Devs should verify that, but I think that "0 Überprüfungen in den letzten 14 Tagen" in you screenshot means that there have been no calls to the API for assessing the risk of exposure. This is plausible, because up to now there is no bundle of diagnosis keys available. Just try getting all dates with available keys:
https://svc90.main.px.t-online.de/version/v1/diagnosis-keys/country/DE/date
Now, the indicator in the actual app (cwa) should mean that the app checked for keys, found none and thus shows "low risk".

related (reason why there might be no keys as of now): https://github.com/corona-warn-app/cwa-documentation/issues/236#issuecomment-646505696

Don't even have those lines in my options in android 6.0.1

Me neither (Pixel 2, Android 10).

Me neither (Galaxy S8, Android 9)

Yes, indeed that observation is related to the fact that no keys are currently being distributed by the server and hence no calls to the API are being made (https://www.coronawarn.app/de/faq/#no_log_check).


fix: create plugins directory

Signed-off-by: ankitm123<EMAIL_ADDRESS>fixes #2

Will rebase after #1 is merged into master, I think that will fix the issues with pr check.

/assign @jstrachan

/approve

/lgtm


Add paused icon in the shows list

Hello,
When you are in the show list you have no clue if the shows are paused or not. It would be great to have an icon.
I was wondering do you use the beta test program? I mean do you release some beta version before they go on play store

I already implemented your request in the next version (1.3).
I use the beta program. The information are available in the readme on the homepage of the project.


train_image_size

Great work! The image size of the mini dataset  in your code is setted 38080, so accuracy in your paper is 38080? Why don't you   use 38484? Expect your help!

Thanks for your interest in our work.
This is a good point. We use the input size of 80x80 because some of recent works use 80x80 (e.g. LEO and we wish to have a strict fair comparison to them.
Using the input size of 84x84 (as many of other recent works did) has similar results. Actually it should be slight better than 80x80 if I remember correctly.

Thanks for your interest in our work.
This is a good point. We use the input size of 80x80 because some of recent works use 80x80 (e.g. LEO) and we wish to have a strict fair comparison to them.
Using the input size of 84x84 (as many of other recent works did) has similar results. Actually it should be slight better than 80x80 if I remember correctly.

Thanks for your interest in our work.
This is a good point. We use the input size of 80x80 because some of recent works use 80x80 (e.g. LEO) and we wish to have a strict fair comparison to them.
Using the input size of 84x84 (as many of other recent works did) has similar results. Actually it should be slightly better than 80x80 if I remember correctly.

Thanks for your interest in our work.
This is a good point. We use the input size of 80x80 because some of recent works use 80x80 (e.g. LEO) and we wish to have a strict fair comparison to them.
Using the input size of 84x84 (as many of other recent works did) has similar results. Actually it should be slightly better than using 80x80 if I remember correctly.


supporting indented options

This dedents YAML blocks and lstrips each line of colon configuration blocks, also adds what I think are two tests that should check this:
closes https://github.com/ExecutableBookProject/myst_parser/issues/54

@choldgraf don't merge this! I'm about to submit a PR that completely rewrites this lol

lol sounds good...well, I'll close this then


Handle image isn't rotating.

I set an image to the handleImage property of the slider. But the image is appearing straight even when I move the handle.
I want the image to also rotate with the angle of the handle.
Current output is as so:

Is there any way I can achieve the rotation ?
Thanks in advance!

Hi!
I just pushed a new version to CocoaPods that includes a new handleRotatable member. If you set it to true, it will rotate the handle image as you slide it. You can also set it from the storyboard attributes inspector.
Good luck!

Hi!
I just pushed a new version to CocoaPods that includes a handleRotatable member. If you set it to true, it will rotate the handle image as you slide it. You can also set it from the storyboard attributes inspector.
Good luck!

@ThunderStruct ,
Thanks a ton for your instant reply and solution.
The image has started rotating but that has somehow blurred the image completely and while the handle is being moved, the image's height grows smaller and bigger.
I'm attaching a few screenshots and a dropbox link for a video which show this behaviour. Could you please look into that and see why that is happening or what I need to change for that?

Video: https://www.dropbox.com/s/9vtyz4n3vjzdeay/CircularSliderDemo.mov?dl=0
Thanks again!

Also, you see, in the above demo example, as the value increases, the whole bar color changes. Instead the actual color should persist and only the color at the handle position should appear.
Kind of like so...

See how here the initial blue remains the same and a lighter blue shaded is aded to the bar as the handle is moved?


WIP: Initial changes to resolve issue 16733

Description:
See to resolve issue as reported in 16733 on startup.
Added logic to ensure that if the state is unknown during startup that the error about being unable to parse the value is not logged.
Further,  also ensured that if an attribute is set to None it does not try to convert the None value to Fahrenheit as that will cause an error.
Related issue (if applicable): fixes #16733
Checklist:

[X] The code change is tested and works locally.
[ ] Local tests pass with tox. Your PR cannot be merged unless tests pass

@MartinHjelmare I believe I just completed what you mentioned. And as part of it also changed the sensor to async instead. This is first time doing this, appreciate you checking (which I know you will ) and providing feedback. :-)
Thank you!!!


Value 'sm_86' is not defined for option 'gpu-name'

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):docker
TensorFlow installed from (source or binary):pip
TensorFlow version (use command below):tf-nightly-gpu         2.5.0.dev20201210
Python version:3.6.9
CUDA/cuDNN version:11.0/8.0.4
GPU model and memory:3090/24GB

when i inference my tf model,it appears hundreds of warnings like the following image
about 1 minute later ,the normal inference begin
i watch the issus and try to used tf2.4re02 but it was useless

@liuxufenfeiya
You can ignore those warning.If you want to disable the warning messages add the below code.
import os
import tensorflow as tf
os.environ['TF_CPP_MIN_LOG_LEVEL'] = "2"

If you feel the issue still persists request you to share colab link or simple standalone code to reproduce the issue in our environment. It helps us in localizing the issue faster.
Thanks!

@liuxufenfeiya
You can ignore those warning.If you want to disable the warning messages add the below code.
import os
import tensorflow as tf
os.environ['TF_CPP_MIN_LOG_LEVEL'] = "2"

If you feel the issue still persists request you to share colab link or simple standalone code to reproduce the issue in our environment. It helps us in localizing the issue faster.
Thanks!

i had already try the way,but it was no use

Try upgrading your Duda version to 11.1

cuda 11.1 does not solve the problem.
2020-12-14 01:30:45.379556: W tensorflow/stream_executor/gpu/asm_compiler.cc:235] Your CUDA software stack is old. We fallback to the NVIDIA driver for some compilation. Update your CUDA version to get the best performance. The ptxas error was: ptxas fatal   : Value 'sm_86' is not defined for option 'gpu-name'

(venv)crutcher@heatlamp:~/git/smot$ lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 20.04.1 LTS
Release:	20.04
Codename:	focal

(venv)crutcher@heatlamp:~/git/smot$ nvidia-smi
Mon Dec 14 01:34:58 2020
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 455.38       Driver Version: 455.38       CUDA Version: 11.1     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  GeForce RTX 3090    Off  | 00000000:21:00.0  On |                  N/A |
| 30%   38C    P8    34W / 350W |  23683MiB / 24265MiB |     14%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
|   1  GeForce RTX 3090    Off  | 00000000:4A:00.0 Off |                  N/A |
| 30%   33C    P8    31W / 350W |    413MiB / 24268MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+

+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A      2618      G   /usr/lib/xorg/Xorg                555MiB |
|    0   N/A  N/A      2895      G   /usr/bin/gnome-shell               95MiB |
|    0   N/A  N/A      7327      G   ...AAAAAAAA== --shared-files      150MiB |
|    0   N/A  N/A     33604      G   ...AAAAAAAAA= --shared-files       36MiB |
|    0   N/A  N/A     60502      G   ..._59022.log --shared-files       35MiB |
|    0   N/A  N/A     67654      C   .../git/smot/venv/bin/python    22781MiB |
|    1   N/A  N/A      2618      G   /usr/lib/xorg/Xorg                  4MiB |
|    1   N/A  N/A      2895      G   /usr/bin/gnome-shell                0MiB |
|    1   N/A  N/A      7327      G   ...AAAAAAAA== --shared-files        0MiB |
|    1   N/A  N/A     33604      G   ...AAAAAAAAA= --shared-files        0MiB |
|    1   N/A  N/A     60502      G   ..._59022.log --shared-files        0MiB |
|    1   N/A  N/A     67654      C   .../git/smot/venv/bin/python      405MiB |
+-----------------------------------------------------------------------------+

(venv)crutcher@heatlamp:~/git/smot$ dpkg -l | grep cudnn
ii  libcudnn8                                  <IP_ADDRESS>-1+cuda11.1                                      amd64        cuDNN runtime libraries
ii  libcudnn8-dev                              <IP_ADDRESS>-1+cuda11.1                                      amd64        cuDNN development libraries and headers

(venv)crutcher@heatlamp:~/git/smot$ dpkg -l | grep cuda
ii  cuda                                       11.1.1-1                                                 amd64        CUDA meta-package
ii  cuda-11-1                                  11.1.1-1                                                 amd64        CUDA 11.1 meta-package
ii  cuda-command-line-tools-11-1               11.1.1-1                                                 amd64        CUDA command-line tools
ii  cuda-compiler-11-1                         11.1.1-1                                                 amd64        CUDA compiler
ii  cuda-cudart-11-1                           11.1.74-1                                                amd64        CUDA Runtime native Libraries
ii  cuda-cudart-dev-11-1                       11.1.74-1                                                amd64        CUDA Runtime native dev links, headers
ii  cuda-cuobjdump-11-1                        11.1.74-1                                                amd64        CUDA cuobjdump
ii  cuda-cupti-11-1                            11.1.105-1                                               amd64        CUDA profiling tools runtime libs.
ii  cuda-cupti-dev-11-1                        11.1.105-1                                               amd64        CUDA profiling tools interface.
ii  cuda-demo-suite-11-1                       11.1.74-1                                                amd64        Demo suite for CUDA
ii  cuda-documentation-11-1                    11.1.105-1                                               amd64        CUDA documentation
ii  cuda-driver-dev-11-1                       11.1.74-1                                                amd64        CUDA Driver native dev stub library
ii  cuda-drivers                               455.32.00-1                                              amd64        CUDA Driver meta-package, branch-agnostic
ii  cuda-drivers-455                           455.32.00-1                                              amd64        CUDA Driver meta-package, branch-specific
ii  cuda-gdb-11-1                              11.1.105-1                                               amd64        CUDA-GDB
ii  cuda-libraries-11-1                        11.1.1-1                                                 amd64        CUDA Libraries 11.1 meta-package
ii  cuda-libraries-dev-11-1                    11.1.1-1                                                 amd64        CUDA Libraries 11.1 development meta-package
ii  cuda-memcheck-11-1                         11.1.105-1                                               amd64        CUDA-MEMCHECK
ii  cuda-nsight-11-1                           11.1.105-1                                               amd64        CUDA nsight
ii  cuda-nsight-compute-11-1                   11.1.1-1                                                 amd64        NVIDIA Nsight Compute
ii  cuda-nsight-systems-11-1                   11.1.1-1                                                 amd64        NVIDIA Nsight Systems
ii  cuda-nvcc-11-1                             11.1.105-1                                               amd64        CUDA nvcc
ii  cuda-nvdisasm-11-1                         11.1.74-1                                                amd64        CUDA disassembler
ii  cuda-nvml-dev-11-1                         11.1.74-1                                                amd64        NVML native dev links, headers
ii  cuda-nvprof-11-1                           11.1.105-1                                               amd64        CUDA Profiler tools
ii  cuda-nvprune-11-1                          11.1.74-1                                                amd64        CUDA nvprune
ii  cuda-nvrtc-11-1                            11.1.105-1                                               amd64        NVRTC native runtime libraries
ii  cuda-nvrtc-dev-11-1                        11.1.105-1                                               amd64        NVRTC native dev links, headers
ii  cuda-nvtx-11-1                             11.1.74-1                                                amd64        NVIDIA Tools Extension
ii  cuda-nvvp-11-1                             11.1.105-1                                               amd64        CUDA Profiler tools
ii  cuda-repo-ubuntu2004-11-1-local            11.1.1-455.32.00-1                                       amd64        cuda repository configuration files
ii  cuda-runtime-11-1                          11.1.1-1                                                 amd64        CUDA Runtime 11.1 meta-package
ii  cuda-samples-11-1                          11.1.105-1                                               amd64        CUDA example applications
ii  cuda-sanitizer-11-1                        11.1.105-1                                               amd64        CUDA Sanitizer
ii  cuda-toolkit-11-1                          11.1.1-1                                                 amd64        CUDA Toolkit 11.1 meta-package
ii  cuda-tools-11-1                            11.1.1-1                                                 amd64        CUDA Tools meta-package
ii  cuda-visual-tools-11-1                     11.1.1-1                                                 amd64        CUDA visual tools
ii  libcudart10.1:amd64                        10.1.243-3                                               amd64        NVIDIA CUDA Runtime Library
ii  libcudnn8                                  <IP_ADDRESS>-1+cuda11.1                                      amd64        cuDNN runtime libraries
ii  libcudnn8-dev                              <IP_ADDRESS>-1+cuda11.1                                      amd64        cuDNN development libraries and headers
ii  nvidia-cuda-dev                            10.1.243-3                                               amd64        NVIDIA CUDA development files
ii  nvidia-cuda-doc                            10.1.243-3                                               all          NVIDIA CUDA and OpenCL documentation
ii  nvidia-cuda-gdb                            10.1.243-3                                               amd64        NVIDIA CUDA Debugger (GDB)
ii  nvidia-cuda-toolkit                        10.1.243-3                                               amd64        NVIDIA CUDA development toolkit

(venv)crutcher@heatlamp:~/git/smot$ pip show tf-nightly
Name: tf-nightly
Version: 2.5.0.dev20201213
Summary: TensorFlow is an open source machine learning framework for everyone.
Home-page: https://www.tensorflow.org/
Author: Google Inc.
Author-email<EMAIL_ADDRESS>License: Apache 2.0
Location: /home/crutcher/git/smot/venv/lib/python3.8/site-packages
Requires: tb-nightly, six, tf-estimator-nightly, grpcio, opt-einsum, termcolor, google-pasta, flatbuffers, h5py, astunparse, keras-preprocessing, numpy, wheel, wrapt, protobuf, gast, absl-py, typing-extensions
Required-by:

I think that this is a duplicate of https://github.com/tensorflow/tensorflow/issues/44750

exactly the same issue

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):yes
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):docker
TensorFlow installed from (source or binary):pip
TensorFlow version (use command below):tf-nightly-gpu         2.5.0.dev20201210
Python version:3.6.9
CUDA/cuDNN version:11.0/8.0.4
GPU model and memory:3090/24GB

when i inference my tf model,it appears hundreds of warnings like the following image
about 1 minute later ,the normal inference begin
i watch the issus and try to used tf2.4re02 but it was useless

Did you solve the issue? If you do, can you share how you do it.

These warnings are mainly there for diagnostic purposes (so that when a user reports a bug we know that they were using the driver JIT and not ptxas).  For now you can ignore them, and we'll fix the warning to be less verbose / scary.

@sanjoy but it has been reported performance loss due to this ptxas fatal . e.g. https://dobromyslova.medium.com/making-work-tensorflow-with-nvidia-rtx-3090-on-windows-10-7a38e8e582bf

I had the same issue.
Using tensorflow compiled with cuda 11.1 solved the issue.

I had the same issue.
In my case, replacing the ptxas file from cuda 11.0 by the ptxas file from 11.1 (or 11.2) solved the problem. This file can be found in "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin" on Windows and in "/usr/local/cuda-11.0/bin/" on Linux.
(I also have a rtx 3090 with tf 2.4.1)

I had the same issue.
In my case, replacing the ptxas file from cuda 11.0 by the ptxas file from 11.1 (or 11.2) solved the problem. This file can be found in "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin" on Windows and in "/usr/local/cuda-11.0/bin/" on Linux.
(I also have a rtx 3090 with tf 2.4.1)

Did you just replace the ptax file or upgrade cuda from 11.0 to 11.1/11.2? @GuillaumeMougeot

Did you just replace the ptax file or upgrade cuda from 11.0 to 11.1/11.2? @GuillaumeMougeot

I just replaced the ptxas file. After installing cuda 11.0, I had to download cuda 11.2. I then copied the ptxas file from cuda 11.2 into cuda 11.0 and the warnings stopped. @rajasd27

I had the same issue. In my case, replacing the ptxas file from cuda 11.0 by the ptxas file from 11.1 (or 11.2) solved the problem. This file can be found in "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin" on Windows and in "/usr/local/cuda-11.0/bin/" on Linux. (I also have a rtx 3090 with tf 2.4.1)
It works for me

Did you just replace the ptax file or upgrade cuda from 11.0 to 11.1/11.2? @GuillaumeMougeot

I just replaced the ptxas file. After installing cuda 11.0, I had to download cuda 11.2. I then copied the ptxas file from cuda 11.2 into cuda 11.0 and the warnings stopped. @rajasd27

Worked for me. I was using tf-gpu docker so that to rebuild a new image by replacing the ptxas file. Thanks a lot!

Upgrade to cuda 11.1+ doesn't work for me. There is an error:
Could not load dynamic library 'libcusolver.so.10'; dlerror: libcusolver.so.10: cannot open shared object file: No such file or directory.
Manually copy ptxas in cuda 11.1+ doesn't work either. There would be an exception during evaluation.
Still waiting for an update.
( linux version: linux 5.10.16.arch1-1 / RTX3090/ cuda 11.0.3-1 /cudnn <IP_ADDRESS>-1/ nvidia 460.39-8)

TF with new cuda versions is tracked at https://github.com/tensorflow/tensorflow/issues/46093

I had the same ptax related error when using the Tensorflow provided container (tensorflow/tensorflow:latest-gpu-jupyter -> tensorflow 2.4)
Fixed by using the NVIDIA provided container (nvcr.io/nvidia/tensorflow:21.02-tf2-py3 also tensorflow 2.4)
available at
https://docs.nvidia.com/deeplearning/frameworks/tensorflow-release-notes/running.html#running

I had the same issue.
In my case, replacing the ptxas file from cuda 11.0 by the ptxas file from 11.1 (or 11.2) solved the problem. This file can be found in "C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v11.0\bin" on Windows and in "/usr/local/cuda-11.0/bin/" on Linux.
(I also have a rtx 3090 with tf 2.4.1)

It works for me

Thanks！！!It also works for me.

@liuxufenfeiya,
Can you please let us know if we can close this issue as it has been resolved? Thanks!

These warnings are mainly there for diagnostic purposes (so that when a user reports a bug we know that they were using the driver JIT and not ptxas). For now you can ignore them, and we'll fix the warning to be less verbose / scary.

I think this issue is causing:

Model does not begin training until GPU memory is full and then it switches to CPU.
So this warning prints out until the GPU can't be used and then it stops and the CPU starts.

It works for me

It works for me (just 11.2)

Try upgrading your cuda version to 11.1

True, just make sure CUDA_HOME and LD_LIBRARY_PATH refer to the path of cuda11.1


Added cancellationToken for repository's async methods.

Added cancellation token for the async methods
Added constraint for GetById method, where TId : notnull

fixes #108


DHCP - Dynamic DNS Registration - No zone for DNS domain of additional pool in dhcpd.conf

Describe the bug
Configured a DHCPv4 service for an interface via the WebUI (services_dhcp.php) and added a Dynamic DNS configuration that updates a DNS zone (mydomain.com) on an external DNS server.
When adding an additional pool which also has a Dynamic DNS configuration that updates a different zone (qa.mydomain.com) on the same external DNS server, DNS updates are done on mydomain.com and not qa.mydomain.com
In /var/dhcpd/etc/dhcpd.conf, the zone declaration for the dynamic DNS domain associated with the Dynamic DNS configuration of the additional pool (i.e. qa.mydomain.com) does not get created. We should see:
zone qa.mydomain.com. {
primary <IP_ADDRESS>;
key ddns-router;
}
but we don't.
To make this explanation simple, I posted in log section my /var/dhcpd/etc/dhcpd.conf from my opensense.
To Reproduce
Steps to reproduce the behavior:

Go to Services: DHCPv4: [interface]
Configure DHCP.
Enable registration of DHCP client names in DNS to mydomain.com
Configure additional pool with registration of DHCP client names in DNS to qa.mydomain.com

Expected behavior
Clients that are part of the additional pool should have there domain name registered to the qa.mydomain.com zone.
Screenshots
Relevant log files
/var/dhcpd/etc/dhcpd.conf
option domain-name "mydomain.com";
option ldap-server code 95 = text;
option arch code 93 = unsigned integer 16; # RFC4578
option pac-webui code 252 = text;
option custom-opt5-0 code 121 = string;
default-lease-time 7200;
max-lease-time 86400;
log-facility local7;
one-lease-per-client true;
deny duplicates;
ping-check true;
update-conflict-detection false;
authoritative
subnet <IP_ADDRESS> netmask <IP_ADDRESS> {
pool {
option domain-name-servers <IP_ADDRESS>,<IP_ADDRESS>;
deny members of "A6AAA4";
ddns-update-style interim;
range <IP_ADDRESS> <IP_ADDRESS>;
}
pool {
option domain-name-servers <IP_ADDRESS>,<IP_ADDRESS>;
option domain-name "qa.mydomain.com";
ddns-domainname "qa.mydomain.com";
ddns-update-style interim;
range <IP_ADDRESS> <IP_ADDRESS>;
}
option routers <IP_ADDRESS>;
option domain-name "mydomain.com";
option domain-search "qa.mydomain.com","mydomain.com";
ddns-domainname "mydomain.com";
option domain-name-servers <IP_ADDRESS>,<IP_ADDRESS>;
option netbios-name-servers <IP_ADDRESS>;
option netbios-node-type 8;
option ntp-servers <IP_ADDRESS>,<IP_ADDRESS>;
next-server <IP_ADDRESS>;
filename "/pxelinux.0";
}
ddns-update-style interim;
update-static-leases on;
key ddns-router {
algorithm hmac-md5;
secret REMOVED;
}
zone mydomain.com. {
primary <IP_ADDRESS>;
key ddns-router;
}
zone 64.2.10.in-addr.arpa. {
primary <IP_ADDRESS>;
key ddns-router;
}
Additional context
Environment
OPNsense 20.7.1-amd64
FreeBSD 12.1-RELEASE-p8-HBSD
OpenSSL 1.1.1g 21 Apr 2020

https://github.com/opnsense/core/pull/4370  merged, @FromageBlue thanks for looking into this. tried your patch on my end with some random values and inspected the configuration, seems to result in a parsable configuration, we'll try to add this into one of our next minor releases.

@FromageBlue A bit baffled about this I looked where we might have lost this working code but it seems it was never properly implemented. Thanks for the find! :)


Bubble not appearing

Please complete the following information:
Platform - Android
App Version - 1.1.6 (21)
Affected Device(s) - OnePlus 7t (Android 11)
Describe the Bug:
I installed 1.1.8 from 'Actions' and now the bubble is not appearing when the keyboard pops up.
I double checked that it is switched on in the settings and made sure it has permission to display over other apps, but it doesn't seem to be working.

EDIT:
Please delete. It's working fine.

Wait how did that happen. I mean how did you fixed it?


cli: retry failed deletes

When deleting a cluster or infrastructure, retry failed deletes until
an interrupt is received. This helps backstop transient issues with
internal retry handling (e.g. AWS dependencies which need cleaned up).

small nit, lgtm

/lgtm


[Bug report] bad argument #2 to '?' (number expected, got nil)

Hello there, hope you're doing well.
I updated today and got the following error:
Error detected while processing /home/user/.config/nvim/init.lua:
E5113: Error while calling lua chunk: /home/user/.config/nvim/lua/core/colors.lua:36: Vim(colorscheme):
E5113: Error while calling lua chunk: ...te/pack/packer/start/doom-one.nvim/lua/doom-one/init.lua:
448: bad argument #2 to '?' (number expected, got nil)
stack traceback:
        [builtin#89]: at 0x7f4c2be4a4b0
        ...te/pack/packer/start/doom-one.nvim/lua/doom-one/init.lua:448: in function 'set_colorscheme'
        ...site/pack/packer/start/doom-one.nvim/colors/doom-one.lua:9: in main chunk
        [C]: in function 'cmd'
        /home/user/.config/nvim/lua/core/colors.lua:36: in main chunk
        [C]: in function 'require'
        /home/user/.config/nvim/init.lua:8: in main chunk
stack traceback:
        [C]: in function 'cmd'
        /home/user/.config/nvim/lua/core/colors.lua:36: in main chunk
        [C]: in function 'require'
        /home/user/.config/nvim/init.lua:8: in main chunk

The following is the color.lua (which I didn't change anything for a long time):
-- Add color to cursor
vim.g.doom_one_cursor_coloring = false
-- terminal colors
vim.g.doom_one_terminal_colors = false
-- Enable italic comments
vim.g.doom_one_italic_comments = false
-- Enable TS support
vim.g.doom_one_enable_treesitter = true
-- Color whole diagnostic text or only underline
vim.g.doom_one_diagnostics_text_color = false
-- Enable transparent background
vim.g.doom_one_transparent_background = false

-- Pumblend transparency
vim.g.doom_one_pumblend_enable = false
vim.g.doom_one_pumblend_transparency = 20

-- Plugins integration
vim.g.doom_one_plugin_nvim_tree = true
vim.g.doom_one_plugin_whichkey = true
vim.g.doom_one_plugin_indent_blankline = true
vim.g.doom_one_plugin_lspsaga = true
vim.g.doom_one_plugin_barbar = true
vim.g.doom_one_plugin_neorg = false
vim.g.doom_one_plugin_telescope = false
vim.g.doom_one_plugin_neogit = false
vim.g.doom_one_plugin_dashboard = false
vim.g.doom_one_plugin_startify = false
vim.g.doom_one_plugin_vim_illuminate = false

vim.cmd([[colorscheme doom-one]])

:version
NVIM v0.8.0
Build type: Release
LuaJIT 2.1.0-beta3
Compiled by builduser

Any help is much appreciated. Thank you!

I also got this error after the update.

Hey, hope you're doing well too!
This is very odd to me, line 448 shouldn't be sending an error to you as you're disabling neorg integration and that code chunk shouldn't be running in your Neovim instances.
If you're compiling Neovim from source can you please build using RelWithDebInfo instead of just Release? That build mode will be the same as Release but will include debugging information that is useful to debug Lua errors traceback so Lua isn't going to send that '?' nonsense thanks to a unknown debugging symbol in the error message as this isn't useful for us to get what's wrong.
bad argument #2 to '?' (number expected, got nil)

Cheers!

Rebuild this morning from master and had same problem. But disabling neorg fixed it for me. Like something had changed in nightly builds.

@phush0 this approach does not works for me :(

Same error here on macOS with nvim stable release (0.8.0)
To reproduce, nvim -u init.vim, content of init.vim:
set runtimepath+=/Users/jdhao/.local/share/nvim/site/pack/packer/opt/doom-one.nvim
colorscheme doom-one

:version
NVIM v0.9.0-dev-314+ge8cc489ac
Build type: RelWithDebInfo
LuaJIT 2.1.0-beta3
Compilation: /usr/bin/cc -DNVIM_TS_HAS_SET_MATCH_LIMIT -DNVIM_TS_HAS_SET_ALLOCATOR -O2 -g -Og -g -Wall -Wextra -pedantic -Wn
o-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wdouble-promotion -Wmissing-noreturn -Wmissing-form
at-attribute -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fno-common -fdiagnostics-color=alwa
ys -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/
home/usr/bin/neovim/build/cmake.config -I/home/usr/bin/neovim/src -I/home/usr/bin/neovim/.deps/usr/include -I/usr/include -I
/home/usr/bin/neovim/build/src/nvim/auto -I/home/usr/bin/neovim/build/include
Compiled by usr@usr

Features: +acl +iconv +tui

Error detected while processing /home/usr/.config/nvim/init.lua:
E5113: Error while calling lua chunk: /home/usr/.config/nvim/lua/core/colors.lua:36: Vim(colorscheme):E5113: Error while calling lua chunk: ...te/pack/packer/start/doom-one.nvim/lua/doom-one/init.lua:448: bad argument #2 to '?' (number expected, got nil)
stack traceback:
        [builtin#89]: at 0x5584a634b480
        ...te/pack/packer/start/doom-one.nvim/lua/doom-one/init.lua:448: in function 'set_colorscheme'
        ...site/pack/packer/start/doom-one.nvim/colors/doom-one.lua:9: in main chunk
        [C]: in function 'cmd'
        /home/usr/.config/nvim/lua/core/colors.lua:36: in main chunk
        [C]: in function 'require'
        /home/usr/.config/nvim/init.lua:8: in main chunk
stack traceback:
        [C]: in function 'cmd'
        /home/usr/.config/nvim/lua/core/colors.lua:36: in main chunk
        [C]: in function 'require'
        /home/usr/.config/nvim/init.lua:8: in main chunk

Hopefully it helps.

line 448 shouldn't be sending an error to you as you're disabling neorg integration

@NTBBloodbath every vim.g.doom_one_* should be set to false by
default (or a more reliable mechanism instead of using or) since doing
false or true will always give us true

Fixed on #33


fix(Orisa): fix fusion cannon ammo overheating

Orisa doesnt work properly, im not sure why but it does, apparently it doesn't change orisas ammo to match with it so I have to use the workshop settings to fix it. This small change fixes everything and properly works for my testing.

and also if you for some reason want
the max ammo of this is 300 ammo cause 50+500% is 300 but this might be a lil wrong cause I'm stupid but yeah. this doesn't do anything but just for safe measures plus the ammo just adjust it anyways I think I didn't test it

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


[INTG] .NET Standard 2.0 client library for SQLite offline support

To go along with the .NET Standard 2.0 client library, we also need a SQLIte offline store that utilizes the Azure.Core library and handles synchronization.

Support added in azure-mobile-apps-net-client branch ns2


doc: Changes made in the doc according to the newer version

Updated the Sonarqube plugin user guide as per the newer version.

@SATYAsasini, we have two SonarQube plugins: SonarQube and SonarQube v1.1.0 (pics attached below)

Your seem to have committed v1.1.0 to the original doc. Please create a new doc for v1.1.0.


Readd enable_log_correlation to docs

:broken_heart: Build Failed

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

Start Time: 2022-03-22T13:18:26.230+0000

Duration: 12 min 6 sec

Steps errors
Expand to view the steps failures

mvn install

Took 6 min 36 sec . View more details here
Description: ./mvnw clean install -DskipTests=true -Dmaven.javadoc.skip=true

mvn license

Took 0 min 13 sec . View more details here
Description: ./mvnw org.codehaus.mojo:license-maven-plugin:aggregate-third-party-report -Dlicense.excludedGroups=^co\.elastic\.

:grey_exclamation: Flaky test report
No test was executed to be analysed.
:robot: GitHub comments
To re-run your PR in the CI, just comment with:

/test : Re-trigger the build.

run benchmark tests : Run the benchmark tests.

run jdk compatibility tests : Run the JDK Compatibility tests.

run integration tests : Run the Agent Integration tests.

run end-to-end tests : Run the APM-ITs.

run windows tests : Build & tests on windows.

run elasticsearch-ci/docs : Re-trigger the docs validation. (use unformatted text in the comment!)


Support for binary messages?

Will binary messages be supported (ala wscat2's -b flag)?

Nevermind.  Just saw #30.  Looking forward to that landing.


added infn lns

Hi all, I added infn lns, my organization
see also: https://www.lns.infn.it/en/

@lujomama This domain does not belong to a university, nor to a college. The institute seems to be purely research organization.
I am sorry, I have to close the request without merging. Please ensure that you are familiar with this repository rules located at the bottom of this page before submitting a new request.
You may also apply for an academic discount by email to<EMAIL_ADDRESS>Thank you.


Additional userdata

Because of the way I'd implemented the checkboxes and radio buttons as
labels and using the userdata for custom data, to reduce code
duplication, they lack a usable userdata. In the near future, i plan to
make what is currently in the userdata into a privatedata with a
KW_Label at the start

right, I'm going to close this one for now, add the DECLSPECS and the fallthrough macro to a different PR and


Question: Why 100% height doesn't work for  in TkinterWeb?

I'm trying to implement a typical header-main-footer layout for my app using table layout. However, I can't get the table expand vertically.
Here's a minimal code:

                1234

    1234

Expected result is two red rectangle with the same height as viewport.
Test result on IE6 and Firefox 2:

Test result on modern Firefox:

Test result on Hv3:

Test result on TkinterWeb:

Is this a bug or something's wrong with my code?

Is this problem resolved ?

Is this problem resolved ?

Is this problem resolved ?

Is this problem resolved ?

No. I didn't find any useful information on Google.

Hi! This seems to be a bug with the underlying Tkhtml engine. It has not seen development in years and I've noticed some bugs with tables and percentages over the years. I'm afraid that fixing this is beyond the scope of this project for the time being.
The best workaround would be to find the height of the frame every time the window is resized, divide that by two, and run set the height of the table to that value in pixels:
import tkinter as tk
from tkinterweb import HtmlFrame

root = tk.Tk()

frame = HtmlFrame(root)

frame.load_html("""

                1234

    1234

""")
frame.pack(expand=True, fill="both")

def on_resize(event):
    frame.add_css(".test {height: "+str(int(event.height/2))+".px}")

frame.bind("<Configure>", on_resize)
root.mainloop()

It's a little bit hacky but works like a charm. I hope this helps!

Hi! This seems to be a bug with the underlying Tkhtml engine. It has not seen development in years and I've noticed some bugs with tables and percentages over the years. I'm afraid that fixing this is beyond the scope of this project for the time being.
The best workaround would be to find the height of the frame every time the window is resized, divide that by two, and run set the height of the table to that value in pixels:
import tkinter as tk
from tkinterweb import HtmlFrame

root = tk.Tk()

frame = HtmlFrame(root)

frame.load_html("""

                1234

    1234

""")
frame.pack(expand=True, fill="both")

def on_resize(event):
    frame.add_css(".test {height: "+str(int(event.height/2))+".px}")

frame.bind("<Configure>", on_resize)
root.mainloop()

It's a little bit hacky but works like a charm. I hope this helps!

Thanks! This works.


Error occurred while updating application when using Auth0 as KM

Description:
This is an error that occurred while working with Auth0 as KM with APIM 4.0.0. After configuring the Auth0 as KM for APIM 4.0.0 according to the documentation[1] the Generate Access Token button gets disabled if we generate the application keys with multiple grant types enabled. Also if reload the page or check the Auth0 tab for an existing application the previously checked grant types and other attribute information are missing in the UI.
Steps to reproduce:

Configure the Auth0 server as Key Manager according to the official document[1].
Log into the devportal and create a new application.
Select multiple grant types to generate the keys.
Select authorization code grant type and add the callback URL.
Generate the keys.
Go to the Application page again and open the same application.
Navigate to Production keys and open the Auth0 key Manager tab.
All grant types are unchecked and the callback URL added was missing.
The Generate Access Token button is also disabled.

Affected Product Version:
APIM-4.0.0
[1] https://apim.docs.wso2.com/en/latest/administer/key-managers/configure-auth0-connector/

APIM-3.2.0 issue will be tracked via this issue


docs: improve spyOn example with a contextual example

As I was reading this example, I noticed that the naming of obj is rather generic given that one would expect students to understand what an object is.
Given that the example talks about apples in a contextual way, the suggestion to replace obj with cart should help improve comprehension for people analyzing the code example.
Happy to chat more if people have questions!

Good point! Thank you.


style: cleans up code

Cleans up e2es style a little to conform closer to the Angular Style Guide.

Going to keep these things as-is.

@jelbourn Works for me.


google-services plugin could not detect any version of com.google.android.gms or .....

Hello,
I recently started working with flutter and this is some error I am getting. I searched the web but could not find any solution. Could someone please help me out with it?
> * Error running Gradle:
> ProcessException: Process "F:\flutterApps\peer_vpn\android\gradlew.bat" exited abnormally:
>
> > Configure project :app
> google-services plugin could not detect any version for com.google.android.gms or com.google.firebase, default version: 11.4.2 will be used.
> please apply google-services plugin at the bottom of the build file.
> Could not find google-services.json while looking in [src/nullnull/debug, src/debug/nullnull, src/nullnull, src/debug, src/nullnullDebug]
> registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
> Could not find google-services.json while looking in [src/nullnull/dynamicProfile, src/dynamicProfile/nullnull, src/nullnull, src/dynamicProfile,
> src/nullnullDynamicProfile]
> registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
> Could not find google-services.json while looking in [src/nullnull/release, src/release/nullnull, src/nullnull, src/release, src/nullnullRelease]
> registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
> Could not find google-services.json while looking in [src/nullnull/profile, src/profile/nullnull, src/nullnull, src/profile, src/nullnullProfile]
> registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
> Could not find google-services.json while looking in [src/nullnull/dynamicRelease, src/dynamicRelease/nullnull, src/nullnull, src/dynamicRelease,
> src/nullnullDynamicRelease]
> registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
> WARNING: API 'variant.getMergeAssets()' is obsolete and has been replaced with 'variant.getMergeAssetsProvider()'.
> It will be removed at the end of 2019.
> For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
> To determine what is calling variant.getMergeAssets(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace.
> WARNING: API 'variantOutput.getProcessResources()' is obsolete and has been replaced with 'variantOutput.getProcessResourcesProvider()'.
> It will be removed at the end of 2019.
> For more information, see https://d.android.com/r/tools/task-configuration-avoidance.
> To determine what is calling variantOutput.getProcessResources(), use -Pandroid.debug.obsoleteApi=true on the command line to display a stack trace.
>          *********************************************************
> WARNING: This version of cloud_firestore will break your Android build if it or its dependencies aren't compatible with AndroidX.
>          See https://goo.gl/CP92wY for more information on the problem and how to fix it.
>          This warning prints for all Android build failures. The real root cause of the error may be unrelated.
>          *********************************************************
>
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Build file 'F:\flutter\.pub-cache\hosted\pub.dartlang.org\firebase_core-0.4.0+4\android\build.gradle' line: 44
>
> * What went wrong:
> A problem occurred evaluating project ':firebase_core'.
> > ..\..\pubspec.yaml (The system cannot find the file specified)
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.
>
> * Get more help at https://help.gradle.org
>
> BUILD FAILED in 9s
>   Command: F:\flutterApps\peer_vpn\android\gradlew.bat app:properties
>
>
> Please review your Gradle project setup in the android/ folder.

gradle build.zip

* Error running Gradle:
ProcessException: Process "D:\Work\RaGen\RaCon\racon_survey\android\gradlew.bat" exited abnormally:

> Configure project :app
google-services plugin could not detect any version for com.google.android.gms or com.google.firebase, default version: 11.4.2 will be used.
please apply google-services plugin at the bottom of the build file.
Could not find google-services.json while looking in [src/nullnull/debug, src/debug/nullnull, src/nullnull, src/debug, src/nullnullDebug]
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
Could not find google-services.json while looking in [src/nullnull/dynamicProfile, src/dynamicProfile/nullnull, src/nullnull, src/dynamicProfile,
src/nullnullDynamicProfile]
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
Could not find google-services.json while looking in [src/nullnull/release, src/release/nullnull, src/nullnull, src/release, src/nullnullRelease]
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
Could not find google-services.json while looking in [src/nullnull/profile, src/profile/nullnull, src/nullnull, src/profile, src/nullnullProfile]
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
Could not find google-services.json while looking in [src/nullnull/dynamicRelease, src/dynamicRelease/nullnull, src/nullnull, src/dynamicRelease,
src/nullnullDynamicRelease]
registerResGeneratingTask is deprecated, use registerGeneratedResFolders(FileCollection)
         *********************************************************
WARNING: This version of camera will break your Android build if it or its dependencies aren't compatible with AndroidX.
         See https://goo.gl/CP92wY for more information on the problem and how to fix it.
         This warning prints for all Android build failures. The real root cause of the error may be unrelated.
         *********************************************************

FAILURE: Build failed with an exception.

* Where:
Build file 'C:\src\flutter\flutter\.pub-cache\hosted\pub.dartlang.org\firebase_core-0.4.0+4\android\build.gradle' line: 44

* What went wrong:
A problem occurred evaluating project ':firebase_core'.
> ..\..\pubspec.yaml (The system cannot find the file specified)

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

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

BUILD FAILED in 3s
  Command: D:\Work\RaGen\RaCon\racon_survey\android\gradlew.bat app:properties

Please review your Gradle project setup in the android/ folder

Duplicate of https://github.com/flutter/flutter/issues/34385
to fix downgrade to:
firebase_core: 0.4.0+3

Hello,
I changed the version in pubspec.yaml for firebase_core to +3 however, it still keeps using +4. I even restarted my pc after doing the change and saving. Today, I find a error about +5 version. I dont know why but somehow it is using the latest version on internet and not the one i am mentioning. Can someone please help me out? I am using VSCode

Hi @ish12321
are you still experiencing this issue with the latest version of Flutter?
If so please reply attaching your flutter doctor -v

Try removing pubspec.lock this files keeps a copy of the dependencies, then run the flutter packages get command to retrieve the versions specified in your pubspec.yaml file, don't run the flutter packages upgrade command or you'll end with a newer version of the dependencies

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


unpackPointer failed with "expected struct, found 3:

Hello,
i tried to decoded a binary string using unpackPointer and got this error
unpack.nim(314)          unpackPointer
unpack.nim(281)          unpackStruct
unpack.nim(255)          parseStruct
Error: unhandled exception: expected struct, found 3 [CapnpFormatError]

i can decode it fine using Go library.
Because type 3 seems to be wanted by unpackCap, i tried to use unpackCap directly but got this error
/root/.nimble/pkgs/capnp-0.0.3/capnp/unpack.nim(292, 12) Error: undeclared identifier: 'createFromCap'

Does this message contain capabilities? If so, it probably only makes sense to use RPC layer to unserialize it. If you just want to ignore them, use something like that
 let unpacker = newUnpackerFlat(data)
unpacker.getCap = proc(id: int): CapServer = return nothingImplemented
unpacker.unpackPointer(0, T)

This library works in a slightly different way than Go and C++ ones - it deserializes everything at once - so it needs to know types of everything beforehand (except AnyPointers).

Mm, looking at the stack trace it seems that the message only contains a capability. Capability is just a number (which makes sense only as part of RPC stream). Could you give more details about the message (preferably copy it here in HEX form).

@zielmicha
thanks for looking at this issue.
The data was not serialized using rpc layer.
I actually expected it to be a struct.
This is the first 20 bytes
03 00 00 00 30 02 00 00 01 02 00 00 03 06 00 00 05 0A 00 00 00

In case it helps, this is the .capnp file
struct TlogBlock {
    sequence @0: UInt32;
    size @1 :UInt32;
    crc  @2 :Text;
    data @3 :Data;
}

struct TlogAggregation {
    name @0 :Text;
    size @1: UInt64;
    timestamp @2 :UInt64;
    blocks @3 :List(TlogBlock);
}

thanks, it works fine now.
sorry for this noise, i thought i've tried newUnpacker.
Yes, the message is indeed generated by C++