Cloudflare services

@petecooper @Bloke I want to start testing a select few of the Cloudflare services and how they'd improve global load times, starting soon (probably early May). To that end, there are a number of services that overlap with what we can provide on our servers directly (preferred route).
Just want to get your opinion on the following Cloudflare options:

Brotli compression (also see https://github.com/textpattern/server-config/issues/18).
HTML minification (I'd have to test this carefully and see if it has any issues with our HTML structure).
HTTP/3 (with QUIC).
0-RTT Connection Resumption.
Onion Routing (Tor specific).

Brotli compression

We can do this natively, I just haven't pushed it up the queue. I will.

HTML minification

I'll defer to @philwareham - you're the pro!

HTTP/3 (with QUIC).

This is due in Nginx in the coming months, please defer until summer.

0-RTT Connection Resumption.

Conscious of replay attacks here, hence it's not enabled by us at the moment. Ongoing r&d.

Onion Routing (Tor specific).

Can't really see the benefit, to be honest. We can easily spin up a .onion mirror locally, but that then becomes another domain property to maintain.

Thanks Pete, so basically just the HTML minification (maybe) plus Cloudflare’s global caching would be the two features we’d use. Good to know.

I'm not averse to the CDN aspect of things, no problem with that. I'd prefer to be 100% watertight with our own handling first so we're not reliant on stuff Cloudflare offer. For example, I also have https://github.com/apache/incubator-pagespeed-ngx to look at, along with the other list of stuff.
…and I have to move house in 6 weeks. Busy few months!

Good luck on the house move! Looking at the incubator-pagespeed-ngx repo - I don't think there's much in there we don't already do as part of our optimisation best practices. Again, it's mostly a band-aid for not doing those things ourselves, I feel.
I used to use the Apache version of the PageSpeed module when I had my own dedicated server, but that was yonks ago.

Once the caching is set up and optimised / battle-tested, I think we're reaching the point of diminishing returns for overall performance improvements, though we can still tinker.
I'm going to try the HTTP/3 stuff on the demo servers first, I need to get a feel as to whether it's appropriate to jump to, given it's still very new and the benefits over HTTP/2. I have to understand the security aspects of it before deploying it at all, so bear with me on that. Timescales: we're reaching the end of the Nginx 1.19 branch, and I expect HTTP/3 to appear in Nginx core by 1.19.10 or 1.19.11 at this rate…which in real terms is going to be April or May, possibly June this year.
We should certainly bash heads on Brotli stuff after 4.8 has flown the roost as that looks like an easy win, and we might eke back ~10-15% judging by the things I've read.

Cheers Pete - sounds good. Regarding HTML minification, it would could such a tiny performance gains it's hardly worth it - but I'll test anyway.
The biggest gain now apart from Brotli would be to use Cloudflare's CDN. Although that'll make hardly any difference in Europe where are servers are located (in fact, in my limited testing it was a few milliseconds slower), it should greatly improve load times at geographically distant locations. i.e. testing with Pingdom Tools via their Australia instance, the load time is around 2 seconds (compared to ~250ms when using a Europe instance). Most of that is wait time while the server is reached.

Leave it a week if you can, the AMD + NVMe server I'm using for .com (plus other stuff) will be in San Francisco, availability isn't 100% across DO datacenters so it's a good opportunity to move a server out of Europe and test CDN stuff. That's schedule to move this week with no downtime, so if we can defer the CDN stuff until at least this time next week, you should have "good" servers to test against.

Of course - it won't be until after 10th May due to the upcoming Cloudflare Cookie removal. Thanks again Pete, love the server work!


Fix swipe lengths

Related Issue
closes #81
Description
Implemented changes to change swipe lengths and their associated unit tests
Also some minor README stuff I saw
Checklist

[x] Have you added an explanation of what your changes do?
[x] Have you written new tests for your core changes, as applicable?
[x] Docs have been added / updated (for bug fixes / features)

And thanks @nerdsosky for the issue


Create functions on the accumulator that match the paper

The following 2 functions would be very helpful:

public_params - salts, height, accumulator variant, group info, max liability
public_data - hash & Pedersen commitment of the root of the tree
root_secret_data - blinding factor & liability for the root

The public values should be printed out to stdout on tree creation

Do this first: https://github.com/silversixpence-crypto/dapol/issues/127


Add function read until

Hi @pelikhan
I am trying to port the Serial read.Until to read the GPS data that is identified with the "$" delimiter, but it seems not to separate the lines with delimiter and also the reading stops after a few seconds

Thanks

Thanks @pelikhan , work delimiter, but "$" and "new line" two o two line and stop

I think the buffer is saturated and it stops working,
with "," working

I have increased the buffer to 90 with "setRxBufferSize", as in this library
https://github.com/adafruit/GPS-shield-RMC-test-sketch/blob/master/GPStest_RMC.ino#L32
and work

Superseeded by other PR. Thansk!

Thanks @pelikhan


Dist artifacts

What have you changed?
Based off #5776.
This creates a make dist_artifacts command for future use in our CI system to build release binaries and Docker images.
It also adds some shorthand commands for the tagging of Docker images, also for later CI use.
What is the type of the changes?
This is a feature for build.
How is the PR tested?
Manual test
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
Yes.

make dist_artifacts now creates compressed archives of TiKV binaries and Docker images.

Does this PR affect tidb-ansible?
Not yet but a future change will.
Refer to a related PR or issue link (optional)
#5776
Benchmark result if necessary (optional)
Any examples? (optional)
$ make dist_artifacts
$ make docker-tag
docker tag pingcap/tikv pingcap/tikv:dcbc8a45d9bd3fddb660bbb244f096343c849353
docker tag pingcap/tikv pingcap/tikv:v3.0.0-beta.1-638-gdcbc8a45
$ tree dist -h
dist
├── [183M]  tikv-docker.tar.gz
└── [176M]  tikv.tar.gz

0 directories, 2 files

/rebuild

@overvenus PTAL

/run-tests

/run-unit-test

/merge

/run-unit-test

/merge

/merge

/test

From the benchmarking
[bench_sysbench_per_pr-731] SUCCESS
Elapsed Time: 72.44 Mins

Version:
   tidb: 380216ed202e7fd57a7a8539ced58e51efc0e0ac(master) 2019-11-19 10:24:40
   tikv: 5c400b7de10d7c53eacace64c8c7c81c11918b55(master) 2019-11-19 10:48:51
   pd: 08e0143e83a2c42955bdfcbed4862f0339b9befc(master) 2019-11-18 01:22:10

Compare:
   tidb: https://github.com/pingcap/tidb/compare/77faf64...380216e
   tikv: https://github.com/tikv/tikv/compare/5c400b7...5c400b7
   pd: https://github.com/pingcap/pd/compare/08e0143...08e0143

test-1: < oltp_update_non_index >
   * QPS : 33063.40 ± 0.1856% (std=45.44) delta: 0.53% (p=0.166)
   * TPS : 33063.40 ± 0.1856% (std=45.44) delta: 0.53%
   * AvgMs : 7.74 ± 0.1292% (std=0.01) delta: -0.55%
   * PercentileMs99 : 20.74 ± 0.0000% (std=0.00) delta: 0.00%

test-2: < oltp_insert >
   * QPS : 23350.51 ± 0.9477% (std=182.11) delta: -0.58% (p=0.333)
   * TPS : 23350.51 ± 0.9477% (std=182.11) delta: -0.58%
   * AvgMs : 10.96 ± 0.9493% (std=0.09) delta: 0.55%
   * PercentileMs99 : 22.44 ± 1.0961% (std=0.20) delta: 0.74%

test-3: < oltp_read_write >
   * QPS : 41653.52 ± 0.2184% (std=61.74) delta: 0.09% (p=0.565)
   * TPS : 2073.25 ± 0.2117% (std=3.09) delta: -0.00%
   * AvgMs : 123.32 ± 0.1176% (std=0.09) delta: -0.07%
   * PercentileMs99 : 179.31 ± 2.1750% (std=2.42) delta: 0.37%

test-4: < oltp_write_only >
   * QPS : 41644.46 ± 0.9640% (std=226.79) delta: -0.08% (p=0.626)
   * TPS : 6920.82 ± 0.9646% (std=37.67) delta: -0.08%
   * AvgMs : 36.85 ± 0.6134% (std=0.17) delta: -0.06%
   * PercentileMs99 : 69.29 ± 0.0000% (std=0.00) delta: -1.79%

test-5: < oltp_update_index >
   * QPS : 20310.56 ± 0.8509% (std=118.82) delta: 0.48% (p=0.425)
   * TPS : 20310.56 ± 0.8509% (std=118.82) delta: 0.48%
   * AvgMs : 12.53 ± 1.0059% (std=0.08) delta: 0.02%
   * PercentileMs99 : 28.67 ± 0.0000% (std=0.00) delta: 0.00%

test-6: &lt…


Remove iperf3 compulsory arguments

Description
During iPerf3 network measurements, we have noticed that we have to pass all these following compulsory arguments.
      transmit_type: time
      transmit_value: 60
      omit_start: 0
      length_buffer: 128K
      window_size: 64k
      ip_tos: 0
      mss: 900
      streams: 1

As a result it generates the following command-lines for Server and Client POD.
Server POD Command: iperf3 -s -p 5201 --forceflush
Client POD Command: iperf3 -c <IP_ADDRESS> -p 5201 --time 60 -l 128K -P 1 -w 64k -M 900 -S 0 -O 0 -R
I get better performance with these following simple command-lines:
Server POD Command: iperf3 -s -p 5201 --forceflush
Client POD Command: iperf3 -c <IP_ADDRESS> -p 5201 --time 60 -R
It would be helpful if we make these compulsory arguments to optional arguments. It will help to reduce search time for default value for all compulsory arguments.
Thanks.
Fixes #535

Can one of the admins verify this patch?

/rerun all

Results for ec2_jjb

Test
Result
Retries
Duration (HH:MM:SS)

test_iperf3
Pass
0
00:06:27


Forward port feature to see difference when rolling back a workload

This pr addresses issue #4229 by adding a code diff modal to the workload deployment rollback process.
To test this PR:

Create a Deployment under Workloads using a specific nginix Image of your choosing. (eg 1.21.1)
Edit Config the newly created deployment and change the nginix Image to another version (eg 1.21.2)
Now that you have an multiple revisions you can select the Rollback menu option for the deployment
When the modal displays, select your previous revision and click the Show Diff button to display the yaml code diff

@neillsom I made a couple of changes to your PR.
The 'Show Diff' button text now toggles between Show and Hide Diff.
The dialog width changes when you show the diff and hide it - this is not an ideal UX, but I think better than having a wide dialog in the case when the dialog first opens when no diff is shown.
The way you weer setting the dialog width was working because the css var was not actually set - you weren't using the computed cssProps anywhere, so in the styling, the width was effectively being unset and so the dialog was full width of the page, but then constrained by the max-width that was set in the style. I've not set the css var correctly which also makes it easy to change the width dynamically.

@neillsom Please review my changes - if you're okay with them, you can go ahead and merge


SVG font --> animated logo. How do I?

Given an svg file for a font, I'd like to make a vivus effect such that each letter of my logo (which is in this font) loads in parallel. How would I go about that? Things tried:
I used illustrator to make an SVG of the logo. Not sure this is the right approach (would rather just type out the letters)
Then, loading from a file using the second syntax listed. That caused this error, and the logo loaded all at once, no effect:
 Uncaught SecurityError: Failed to read the 'contentDocument' property from 'HTMLObjectElement':
 Blocked a frame with origin "null" from accessing a frame with origin "null". Protocols, domains, and
 ports must match.

The issue seems to be with chrome. So I loaded chrome without security settings. Now the logo loads all at once without effect, but no error either.
I tried putting all the svg from the illustrator file into my html. Didn't work either.
I feel like there's some easy way to do this I'm missing.

Hi there,
About the first point, Vivus cannot manipulate <font> elements. The text must be transformed into <path> elements in Illustrator.
And about the second point, the error must be due to the use of the protocol file://. This is a normal security check from Chrome, otherwise it could allow any local script to load and read any local content. This is why the file option can only be used behind a HTTP server. If you're using a Mac, open the terminal, move to your project folder (where you have the HTML and JS files), then run python -m SimpleHTTPServer. This command will create a simple http server on http://localhost:8000/
So if you work on the file hello.html, you just need to go to http://localhost:8000/hello.html
Tell me how it goes if you need more help.
Otherwise, it would be helpful to have your code on here (or JSfiddle, CodePen...)

I ended up using the font to write the words I wanted in Illustrator, then exported as SVG and messed with that to satisfaction. Just to echo some of the other issues, it would be sweet if fills could be animated as well, not only strokes. Thanks!


Confusing generic parameter name for Unsubscriber<BaggageInfo>

The generic parameter name for class Unsubscriber<BaggageInfo> is, unfortunately (and, likely, inadvertently) named the same as the class BaggageInfo. To alleviate any confusion, may I suggest changing the generic parameter to T, or even to TBaggageInfo, if it is semantically important to show that the type is in fact meant to be of type BaggageInfo (although the Unsubscriber<T> looks pretty generic; perhaps, a where constraint can be used to limit the type, as the write-up does say "Unsubscriber(Of BaggageInfo)...).

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

ID: 5e8b6ec6-3773-879a-00e9-4bf113b9f362
Version Independent ID: 5c46289d-8473-623f-eb42-8bda01c30c63
Content: Observer Design Pattern
Content Source: docs/standard/events/observer-design-pattern.md
Product: dotnet
Technology: dotnet-standard
GitHub Login: @rpetrusha
Microsoft Alias: ronpet

@CoolBots Thanks for the suggestion, but we don’t have the resources to implement it, so we are closing the issue. If we get more 👍 responses to the issue, we’ll reconsider.


Wrong data after reconnecting to the same device.

There is a device that sends data...
So, after first connection it works well and in event listener each event data is new as should be.
Like:
[49, 5, 0, 0, 0, 13, 60, 169, 5, 133, 212, 0, 0, 0, 5, 159, 32, 0, 74, 92]
[50, 5, 252, 194, 139, 7, 44, 67, 0, 0, 0, 13, 60, 176, 5, 135, 149, 0, 0, 0]
[51, 5, 5, 162, 106, 0, 75, 240, 252, 195, 235, 7, 44, 175, 0, 0, 0, 13, 59, 208]
But! After calling disconnect and connecting again, it sends the same data several times.
[98, 1, 164, 148, 56, 161, 93, 50, 0, 0, 0, 163, 64, 149, 254, 92, 141, 0, 0, 0]
[98, 1, 164, 148, 56, 161, 93, 50, 0, 0, 0, 163, 64, 149, 254, 92, 141, 0, 0, 0]
[99, 1, 46, 54, 117, 73, 1, 35, 53, 181, 244, 9, 138, 92, 0, 0, 0, 29, 47, 15]
[99, 1, 46, 54, 117, 73, 1, 35, 53, 181, 244, 9, 138, 92, 0, 0, 0, 29, 47, 15]
// _notificationService?.value.listen((event) {       if (event.isNotEmpty) {         print("EVENT $event");  // so, here I got the events with the same data after reconnecting.       }     }); //
At the same time, if you connect to some other device, the data will be in order until we disconnect and connect again.
Of course, if I close and reopen the application, I can reconnect to these devices again.
It was tested on Android and ios works same.
Maybe there are some buffers not cleared in the plugin for a specific device?

I have found only one solution to compare new even and the last event:

There is a device that sends data...
有一个设备可以发送数据..。
So, after first connection it works well and in event listener each event data is new as should be. Like: [49, 5, 0, 0, 0, 13, 60, 169, 5, 133, 212, 0, 0, 0, 5, 159, 32, 0, 74, 92] [50, 5, 252, 194, 139, 7, 44, 67, 0, 0, 0, 13, 60, 176, 5, 135, 149, 0, 0, 0] [51, 5, 5, 162, 106, 0, 75, 240, 252, 195, 235, 7, 44, 175, 0, 0, 0, 13, 59, 208]
因此，在第一次连接之后，它工作得很好，在事件侦听器中，每个事件数据都应该是新的。比如: [49,5,0,0,0,13,60,169,5,133,212,0,0,0,0,5,159,32,0,74,92][50,5,252,194,139,7,44,67,0,0,0,13,60,176,5,135,149,0,0,0,0][51,5,5,162,106,0,75,240,252,195,235,7,44,175,0,0,0,13,59,208]
But! After calling disconnect and connecting again, it sends the same data several times.
但是，在调用 disconnect 和再次连接之后，它会多次发送相同的数据。
[98, 1, 164, 148, 56, 161, 93, 50, 0, 0, 0, 163, 64, 149, 254, 92, 141, 0, 0, 0] [98, 1, 164, 148, 56, 161, 93, 50, 0, 0, 0, 163, 64, 149, 254, 92, 141, 0, 0, 0]
[98,1,164,148,56,161,93,50,0,0,0,163,64,149,254,92,141,0,0][98,1,164,148,56,161,93,50,0,0,0,163,64,149,254,92,141,0,0]
[99, 1, 46, 54, 117, 73, 1, 35, 53, 181, 244, 9, 138, 92, 0, 0, 0, 29, 47, 15] [99, 1, 46, 54, 117, 73, 1, 35, 53, 181, 244, 9, 138, 92, 0, 0, 0, 29, 47, 15]
[99,1,46,54,117,73,1,35,53,181,244,9,138,92,0,0,0,0,29,47,15][99,1,46,54,117,73,1,35,53,181,244,9,138,92,0,0,0,29,47,15]
// _notificationService?.value.listen((event) { if (event.isNotEmpty) { print("EVENT $event"); // so, here I got the events with the same data after reconnecting. } }); // At the same time, if you connect to some other device, the data will be in order until we disconnect and connect again. Of course, if I close and reopen the application, I can reconnect to these devices again.
//_ 通知服务？.Listen ((EVENT){ if (EVENT.isNotEmpty){ print (“ EVENT $EVENT”) ;//so，这里我在重新连接后得到了具有相同数据的事件。});//同时，如果您连接到其他设备，数据将是有序的，直到我们断开并再次连接。当然，如果我关闭并重新打开应用程序，我可以重新连接到这些设备。
It was tested on Android and ios works same. Maybe there are some buffers not cleared in the plugin for a specific device?
它在安卓系统上测试过，ios 系统也一样。也许某个特定设备的插件中有一些缓冲区没有被清除？

Maybe you should see this.#317

Please go to flutter_blue_plus and report issues there if still exist.

Please go to flutter_blue_plus and report issues there if still exist.

The same problem is occurring for me.

@Hitbee-dev please report issue there. development on this plugin is continued there.
It would be great to investigate the problem and give PR on flutter_blue_plus

@Hitbee-dev please report issue there. development on this plugin is continued there. It would be great to investigate the problem and give PR on flutter_blue_plus

I solved the problem.
We will revise the sample to float_blue_plus soon and Pull request the entire sample, so please check it.

I'm provides a solution. @GorIvanov
If this method is okay, please close Issues.
When we disconnected and reconnected Bluetooth, we confirmed that duplicate data came in as many times as we reconnected.
Those who contributed to solving the problem: @Hitbee-dev @K9714 @jaehyeokjeong
We tried the following methods to solve this problem.
1. Identify where duplicate data comes from.

ss.value.listen((value) async {
   //...duplicate data Issue
});

2. Check what information is received in the listen

It can be seen that the data type is StreamSubscription.

3. StreamSubscription<List<int>>? subscription = null;

It can be seen that the format of the data received is List<int>

Therefore, it was found that subscription information could be obtained using StreamSubscription<List<int>>? subscription = null; as a global variable.
4. listen().cancel();

When listen was used asynchronously, it found out that if cancel() is not used, subscription information continues to be held (why duplicate data occurs).

Therefore, when the connection was terminated, subscription information was deleted using cancel()
5. FULL CODE

I hope it helps developers who are experiencing the same problem...
The same problem occurred in flutter_blue_plus, which can be solved in this way.
If you don't mind, can I send you a PR by modifying the example code of the flutter_blue_plus you developed? @boskokg


Issue an asset

The ColoringEngine appears to be read-only. Are there plans to be able to issue an asset with this library? Thanks!

Hey Don - yes, that was always the idea. However, I wasn't sure how much interest there would be, and got caught up recently in other work.
Actually, a fair amount of progress has already been made on this (in the develop branch), and I've created stubs for what remains to be implemented. If you'd like to help out, the TransactionBuilder class is where most of the remaining work needs to happen (https://github.com/andrewfhart/openassets/blob/develop/lib/protocol/TransactionBuilder.js).
Let me know if you have any questions or suggestions, I'm glad to see some interest, it may motivate me to pick this back up, so thanks!

Thanks Andrew - I'll dig into it and see if I can contribute.


Don't ignore -notimeout in submit

See #235
submitting shouldn't remove the effect of -notimeout

Thanks!

See https://github.com/HaxeFoundation/haxelib/issues/235#issuecomment-194928792


I got conflict between ReSwiftThunk-Core-ExpectThunk and ReSwiftThunk when make archive

This is I can see in log
Showing Recent Messages
Multiple commands produce '/Users/.../UninstalledProducts/iphoneos/ReSwiftThunk.framework':

Target 'ReSwiftThunk-Core-ExpectThunk' has create directory command with output '/Users/.../iphoneos/ReSwiftThunk.framework'
Target 'ReSwiftThunk' has create directory command with output '/Users/.../iphoneos/ReSwiftThunk.framework'

pod file
pod 'ReSwift'
pod 'ReSwiftThunk'
pod 'ReSwiftRouter'
before this I can see this issue ( the same I can see when launch on iPhone, but I get no fail)
Showing Recent Messages
Multiple targets match implicit dependency for linker flags '-framework ReSwiftThunk'. Consider adding an explicit dependency on the intended target to resolve this ambiguity. (in target 'TrackdMusic' from project 'TrackdMusic')
Xcode 11.3.1 CocoaPods
COCOAPODS: 1.8.4
at Cocoapods target I can see two target whichProduces framework with the same name, https://prnt.sc/qwhbb3 , of course it not ok for CI. So any Ideas how resolve it?
P.S If I remove  pod 'ReSwiftThunk' I still can see target ReSwiftThunk but I have failure ( no such module ReSwiftThunk)

So pod support files seems a bit strange https://prnt.sc/qwhtp5

Probably problem was in test target, here declared pod 'ReSwiftThunk/ExpectThunk'


Update key/cert path

Corresponding change is here: https://github.com/istio/istio/pull/3520

/lgtm
/approve


[C++] Is building for Windows 32 Bit/x86 supported?

I'm new to the Apache Arrow project and want to make use of it to simply write Parquet files (which I was able to do when building for Win x64).
Using Arrow v6.0.1, I followed the instructions here and here. I changed the parameters from x64 to x86 or Win32 respectively (VsDevCmd.bat and the CMAKE call).
If I try to build the resulting VS solution as "Win32|Debug" in Visual Studio 2019, I get various errors related to "64 bit vs 32 bit incompatibilities". E. g. in bit_util.h "_Error C3861 'BitScanReverse64': identifier not found	arrow_shared" and others.
Although I couldn't find an explicit mention, I assumed that Arrow could be built "out of the box" to target Windows/x86 (Win32)?
I found an older issue (#5787) which asks a similar question. Is there any update since 2019 (unfortunately, I couldn't find the related Jira ticket)?
Are there any current efforts to be able to build 32 bit Window applications using the sources found (CMAKE lists, C++ source code) in the Arrow-cpp GitHub repository?

There are no such efforts but we are willing to accept a PR to fix this issue if you'd like to. Could you perhaps start by opening an issue on JIRA?

@jmckenna
In my use case it was sufficient to work with the 64-bit version. To be able to build the project also in 32-bit/x86 would have been necessary in my case only for the sake of completeness ("nice to have"). Therefore, I have unfortunately not been able to solve the issue conclusively.

Thanks @VisBeo


Can we add more custom colors for Typography?

Hi,
currently Typography supports 'primary', 'secondary', 'textPrimary', 'textSecondary', 'error'
However I need more colors!
Of course we can just use
<Typography style={{color: 'something'}}>
or
<Typography className={makedStyles}>
But want to have more simple and fancy way.
like
<Typography color='something'>

Duplicate of #13875


Blank blog, error

Getting a blank page and the following error in the console after running gatsby develop on a fresh gatsby new blog https://github.com/gatsbyjs/gatsby-starter-blog:
web-entry.js:70 Uncaught TypeError: (0 , _reactRouterScroll2.default) is not a function

Resolved by gatsby v0.12.5. Thanks, @KyleAMathews!


ISO8583 Inbound example doc is outdated

Description
We have introduced a new VSCode UI schema for ISO8583 inbound endpoint. But the current doc[1] contains old UI and configuration steps.
[1] - https://mi.docs.wso2.com/en/latest/reference/connectors/iso8583-connector/iso8583-inbound-endpoint-example/

PRs:

https://github.com/wso2/docs-mi/pull/1180
https://github.com/wso2/docs-mi/pull/1191

Closing as fixed.


[stable/mongodb] updating chart fails in standalone deployment

Describe the bug
When setting replicaSet.enabled=false and persistence is enabled, after updating the chart, the mongodb pod fails with "Multi-Attach error for volume".
Version of Helm and Kubernetes:
Helm v2.14.1
K8S v1.14.5
Which chart:
stable/mongodb
What happened:
Updating the mongodb chart with a single mongodb instance failed with: "Multi-Attach error for volume".
What you expected to happen:
Successful update with all new pods starting.
How to reproduce it (as minimally and precisely as possible):
Preconditions: ReadWriteMany not supported by Volume Plugin.

deploy mongodb chart in [current version -1]
use helm update to update the chart to the latest version
see the mongodb pod failing

Anything else we need to know:
In stable/mongodb/templates/deployment-standalone.yaml the updateStrategy.type parameter is not considered for spec.strategy.type , so it will always be RollingUpdate, which does not work if the Volume Plugin does not support ReadWriteMany.
The Fix would be to allow setting spec.strategy.type to Recreate in the Deployment.
This was already done for the StatefulSets (#12327), looking at the template there seems to be a bug there as well - updateStrategy.type=Recreate is not a valid Setting for StatefulSets so the condition in there is obsolete.

@donifer just saw your comment on #12327, when opening this bug. We seem to be having the same Issue.

Hi,
Would the change in #12327 solve the issue then?

Hello @javsalgar
Not #12327 directly, as it's already merged, but applying the same change to the file stable/mongodb/templates/deployment-standalone.yaml should do the trick.

Hi,
I just saw that this https://github.com/helm/charts/pull/19720 was already merged. Is that it?


Setup failed for magic_areas: Integration 'magic_areas' did not return boolean if setup was successful. Disabling component.

Installed Magic Areas through HACS, rebooted Home Assistant. Added the magic_areas flag into configuration.yaml and I receive the following notification upon rebooting:
"Setup failed for magic_areas: Integration 'magic_areas' did not return boolean if setup was successful. Disabling component."
Home Assistant OS 5.12, core-2021.3.4, supervisor-2021.03.6

Thanks for reporting, will investigate

Closing as stale. If you still have the issue please reopen.


Support configuring environment variables

What this PR does / why we need it:
Support configuring environment variables
Which issue(s) this PR fixes :
Fixes #492
Special notes for your reviewer:

Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.

Release note:

the implement about how to append environment is ok, but there is no reference in the preprocessor for end user the specify the env pairs they want to set.

the implement about how to append environment is ok, but there is no reference in the preprocessor for end user the specify the env pairs they want to set.

Thanks. The pod spec is generated in builder. So that's better to set env via pod_spec_mutators. For example:
from kubeflow.fairing.deployers.job import Job
from kubeflow.fairing.kubernetes import utils

Job(namespace=xxx, pod_spec_mutators=[utils.add_env({'var1': 'value1', 'var2', 'value2', ...})])

Thanks @jinchihe,
/lgtm

/approve

/lgtm
Thanks @jinchihe

/lgtm


Date Flag

I am experiencing an issue with pip: There are modules that are too new which are causing inconsistencies with older scripts. Specifying versions for each module is tedious.
When a particular older script was first written pip got the correct modules. Now it doesn't. I know I can set a version with a flag. I do not want users to have issues when time passes.
The solution I imagine is to check a module's timestamp against a date flag then check the version.
Please consider adding a date flag.

Sorry, I don't quite understand the issue -- could you elaborate/provide an example?

Could you tell me where I lost you so I know where to begin?

If Electrum dependencies are clashing with other packages then you can try installing Electrum inside a virtualenv.

I wish I could tell you where you lost me, yes I have been using Python for 20 years -- so I have definitely run old scripts.    Feel free to open a PR or provide additional concept for what you are trying to accomplish, but recall we drop support for old EOL python versions.


Sb 11646 remove audit api changes

Codecov Report

Merging #443 into release-1.15 will decrease coverage by 0.03%.
The diff coverage is n/a.

@@                Coverage Diff                 @@
##             release-1.15     #443      +/-   ##
==================================================
- Coverage           35.77%   35.74%   -0.04%
  Complexity            684      684
==================================================
  Files                 110      110
  Lines                7672     7668       -4
  Branches              874      874
==================================================
- Hits                 2745     2741       -4
  Misses               4630     4630
  Partials              297      297

Impacted Files
Coverage Δ
Complexity Δ

...va/org/sunbird/common/models/util/ProjectUtil.java
72.09% <ø> (-0.13%)
38 <0> (ø)

...rg/sunbird/common/models/util/ActorOperations.java
100% <ø> (ø)
3 <0> (ø)
: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 3d14cdf...f9e7aee. Read the comment docs.


EGFR vs epidermal growth factor receptor

Hello,
Following on from Emilys request to standardise the
TGFR/transforming growth factor receptor terms, the
same should be done for lots of other signaling terms.
For some the abbreviation is the text string but for
others it is the full name. Many are lacking the
corresponding synonyms. To be consistent I think the
full name should be in the text string and the
abbreviation always listed as a synonym.
See:
epidermal growth factor receptor binding ; GO:0005154
epidermal growth factor receptor activating ligand
activity ; GO:0005155
epidermal growth factor receptor inhibiting ligand
activity ; GO:0005156
vs
EGF receptor signaling pathway ; GO:0007173
EGF receptor ligand processing ; GO:0007174 etc
Eph receptor signaling pathway ; GO:0048013
vs
ephrin receptor binding ; GO:0046875
hedgehog receptor activity ; GO:0008158
vs
activation of hh target transcription factor ; GO:0007228
vascular endothelial growth factor receptor activity ;
GO:0005021
vs
VEGF receptor signaling pathway ; GO:0048010
Notch binding ; GO:0005112
vs
N signaling pathway ; GO:0007219
Toll binding ; GO:0005121
vs
Tl signaling pathway ; GO:0008063
fibroblast growth factor receptor activity ; GO:0005007
fibroblast growth factor receptor binding ; GO:0005104 etc
vs
FGF receptor signaling pathway ; GO:0008543 etc
platelet-derived growth factor receptor activity ;
GO:0005017
vs
PDGF receptor signaling pathway ; GO:0048008
nerve growth factor receptor binding ; GO:0005163
vs
NGF receptor signaling pathway ; GO:0048011
HGF receptor signaling pathway ; GO:0048012
vs
hepatocyte growth factor receptor binding ; GO:0005171
IGF receptor signaling pathway ; GO:0048009
vs
insulin-like growth factor binding ; GO:0005520
insulin-like growth factor receptor binding ; GO:0005159
insulin-like growth factor receptor activity ; GO:0005010
Need to add:
TNF receptor binding/TNF receptor as synonyms for:
tumor necrosis factor receptor binding ; GO:0005164
tumor necrosis factor receptor activity ; GO:0005031
Also, what are:
NGF/TNF (6 C-domain) receptor activity ; GO:0005027
Neu/ErbB-2 receptor binding ; GO:0005176
Neu/ErbB-2 receptor activity ; GO:0005012
they have the distinct hint of geneproduct-ness, or at
least 2 separate activities in each term.
Also:
<regulation of signal transduction ; GO:0009966
%negative regulation of signal transduction ;
GO:0009968
%positive regulation of signal transduction ;
GO:0009967
could be given all the appropriate 'regulation of xxx
signaling' children. eg
positive regulation of signal transduction ; GO:0009967
--%positive regulation of FGF receptor signaling
pathway ; GO:0045743 etc etc
Thanks,
Becky
Reported by: beckyfoulger
Original Ticket: "geneontology/ontology-requests/1516":https://sourceforge.net/p/geneontology/ontology-requests/1516

thanks www.movied.org


Using single quote hangs goog.i18n.DateTimeFormat

The single quote character in DateTimeFormat string makes the constructor hang with 100% CPU usage.
  var fmt = new goog.i18n.DateTimeFormat("MMM 'yy");

Example: https://codepen.io/anon/pen/gMmVgK
Disclaimer: I do realize that the quote symbol is used in format quoting and I need to use two adjusted single quotes to escape the quote itself. I just don't think the constructor should hang so violently even when the input format string is bad.

Thanks for pointing this out. This was fixed internally and will be available on the next Closure release.


Add LFS instructions to all models leveraging LFS for storage

refs #7 #58

Failure is unrelated (cross sections not downloading)


Use default language strings in the XML Processor if a translation is missing

Hi 👋
I started using Lyricist, and I wanted to migrate my existing XML. However, not all the strings that I have are translated, and the processor generates the files with missing values.
I've modified the processor to generate the string file with the value from the default language if the translation is missing!

Nice catch :)) thxx appreciated @prof18


Nav links are not working properly

Look up github link routing resources to update nav menu

Nav links have been updated


Add v0.21 release notes

Note: this PR will be merged when v0.21 is ready for release.

Note: this PR will be merged when v0.21 is ready for release.


AddressComplete - turning flag off after it was on

Description

Create a form including AddressComplete with the feature flag on
Turned flag off
Complete form
Check response data

With flag off  --- after it was on.

A country select shows

Response has - for value

Street address -- is using "typeahead" component and says start typing to search.  Given the flag is off this field will never have a dataset.  If the user is expecting a search to happen it won't.

I think the expected behavior for this one would be that the "Start typing an address to search" placeholder text simply doesn't appear?
@anikbrazeau - does that make sense for a form that we've turned AddressComplete off on?

Yes that makes sense to me!


[PLUGIN REQUEST] overseer.nvim

Field
Description

Plugin
overseer.nvim

Homepage
https://github.com/stevearc/overseer.nvim

Nixpkgs
vimPlugins.overseer-nvim

Extra Information
Required for Compiler.nvim.

@PowerUser64 wouldn't you want to give it a shot ?
Honestly, it is not that hard to do and I can help you getting a PR merged :)
Feel free to ask any question on matrix also.
(If you do not want to try or don't have time, no worry, I'll do it)

Yeah, I'd be interested to learn how. I'll send you a message later!


Improve data import

Need to improve data import in https://github.com/fulldecent/septa-regionalrail-otp/tree/master/Getting GTFS Data from SEPTA
because the schema is coming in wrong. (It is using TEXT for number fields.)

Closed too soon. Trips is not imported correctly with this script.

Fixed in 75fcf524fe1519f666317ac71e06c5734defe31d


Make use of mac() and ip() helpers.

Implements #31

Not sure if/what I need to do with this?

If someone rebases this I will merge it and release a new version : )

Assuming a rebase is fixing the merge (not updating the commit log) I made a change but it's now failing the unit tests. The tests pass if I run them locally on my development box but fail under Travis. Looks like the case difference in the mac() method is causing the problem.

@inetuid You did good rebasing. The new testing framework compares the expected data with the information returned by the getters - and seems to be case sensitive (e.g.: {"expected": "08:00:27:10:c4:8f", "result": "08:00:27:10:C4:8F"}). For the moment you can update the contents of the tests to be update and all MAC addresses to be converted to upper in expected_result.json for the following tests:

get_arp_table
test_get_interfaces

For traceroute, as the unresponsive hops are marked with *, you should do:
hop_addr = hop_details[4+probe_index*5]
ip_address = napalm_base.helpers.convert(napalm_base.helpers.ip, hop_addr, hop_addr)

Which returns the raw value (*) in case unable to convert to ip format.

Changes made.

Coverage decreased (-0.08%) to 79.639% when pulling 417ca001aaf4046d7f770e0d294d748be3478827 on inetuid:develop into 1f0b976b5d0b5759f4303c9046280c95a1ceaf93 on napalm-automation:develop.


Change how we do service driven events.

@keybase/react-hackers
The old way is actually not supported and a bug that will be fixed in
the next version of redux-saga.
This approach basically creates a channel per incoming call. We can also control the type of buffering we want on a per individual incoming call type basis.
This approach has a couple benefits. It let's us handle things in our
order without failing if there's a slight mismatch. Say we expect A then
B. but we actually get B then A (about the same time).
This can also give us warnings if there is a message the service sent
that we are not explicitly handling.
We can define how many times an incoming call can be made, and error if
that assumption isn't true.

@chromakode bump


Language toggle

Our partners will help us translate any / all project narrative, but we need a Portuguese / English toggle somewhere in the app. Here's an example.

Portuguese toggle added... if mapbox relabeling is necessary, please re-open


Remove confusing information from the status tag for published RFCs

Description
Hi,
When suggestion that 3GPP should use RFC 9310 a comment was that the status page states "Incomplete, due 2022-10-27"
https://datatracker.ietf.org/doc/rfc9310/
Looking at the DataTracker status page for RFC 9310 there are several things that can be confusing for people not familiar with the IETF process.
IANA OK - Actions Needed
Submitted to IESG for Publication
Incomplete, due 2022-10-27
Ready with Nits
Ready with Issues
I think it would be good if this kind of historical information was moved to another tab for published RFCs. Otherwise it is very easy for people and other SDOs to believe that the document is still being worked on.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

This will get addressed at the latest when we make RFCs first-class document objects (instead of being a pseudo-version of an Internet-Draft). But in the meantime, we can look at not displaying some of the not-relevant-to-the-RFC items when viewing an RFC.

This has been addressed on the feat/rfc branch - the draft process related things are not shown when viewing the RFC - but they are still available when looking at specific revisions of the draft.
I'm closing this now, but it you won't see the changes in production until feat/rfc is merged and released.


[Issue-390] Add Multiplatform Settings

🚀 Description
Adding @russhwolf's Multiplatform Settings
📄 Motivation and Context
Multiplatform Settings is a go-to for making a KMM app. Adding it to refreshVersions helps us get closer to using refreshVersions, and away from using buildSrc in our projects.
This addresses https://github.com/jmfayard/refreshVersions/issues/390
🧪 How Has This Been Tested?

./gradlew :refreshVersions:check
inspections that the coordinates are generated in
dependencies-mapping-validated.txt and bundled-dependencies-validated.txt.

📦 Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

✅ Checklist

[X] I have read the guidelines for the development process
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.

I have two concerns:

The version key "version.settings" is too generic and not specific enough
The name of the object itself is very generic

For 1, I'd suggest to have "version.multiplatform-settings", and for 2, to have a RusshWolf/RussellWolf object, like the JakeWharton one.
@jmfayard What do you think?

I agree


gnome.gnome-session: outputs documentation with unreproducible ids

Building this package twice does not produce the bit-by-bit identical result each time, making it harder to detect CI breaches. You can read more about this at https://reproducible-builds.org/ .
Fixing bit-by-bit reproducibility also has additional advantages, such as avoiding hard-to-reproduce bugs, making content-addressed storage more effective and reducing rebuilds in such systems.
Steps To Reproduce
nix-build '<nixpkgs>' -A gnome.gnome-session --check --keep-failed

You can use diffoscope to analyze the differences in the output of the two builds.
To view the build log of the build that produced the artifact in the binary cache:
nix-store --read-log $(nix-instantiate '<nixpkgs>' -A gnome.gnome-session)

Additional context
It seems it uses unstable identifiers in the documentation output (https://reproducible.nixos.org/nixos-iso-gnome-runtime/diff/7e066b3e0a9e41d38e5dda32f2bef66c64059667317775343b19bc383f64b920-944aae10257b53d61eed0269a72038e1d57ec3d9c5a5a1e5ca0694d3e6b4cb5e.html). This can often be fixed by passing the 'generate.consistent.ids' flag to docbook (see e.g. https://marc.info/?l=bind-workers&m=144228535428181).
Also, shouldn't the docs be in a separate doc output?

(this is not showing up in the latest report, may have been fixed or not reproducibly unreproducible)

The upgrade to libxslt 1.1.38 probably fixed this. In the release notes, it mentions that the generate-id function (used by docbook to generate these ids) has been made deterministic.

Very nice!


Run JS tests in multiple real browsers

Extracted from #12936.
See initial suggestion from @nkovacs and further small discussion https://github.com/yiisoft/yii2/pull/12936#issuecomment-259927498.
From one side, this is good to catch IE8 errors such as "class" or "boolean" reserved keywords like in #12722. From the other side it can be extra overhead considering amount and complexity of existing JS code.

I don't think we have many issues with browser differences so it doesn't worth to have that in regular builds. Won't mind an ability to run it on a local machine though...

Here are some examples how to setup different browsers with Docker (or IE via modern.ie VM) - https://github.com/dmstr/phd5-app/blob/master/tests/codeception/e2e.suite.yml
You can view the browsers via VNC and also run coverage for e2e tests.
Let me know if you need more input on this topic, also for JavaScript testing i.e.

Closing since it requires too much effort w/o much gain.


Remove version: ProtonTechnologies.ProtonVPN version 2.4.1

duplicate
Microsoft Reviewers: Open in CodeFlow

URL: https://github.com/ProtonVPN/win-app/releases/download/2.4.1/ProtonVPN_win_v2.4.1.exe
OK
(Automated message - build 882)


Support kafka consumer 3.7

3.x refactors the KafkaConsumer into LegacyKafkaConsumer and async mode consumer. In this pr, only the legacy mode is supported.
And the metrics of fetch is also improved by using the batch interface to improve the performance


Not receiving notifications for new DM's

I've noticed I'm not receiving notifications on my desktop for DM's. There is no red dot adjacent to the messaging icon. I have to manually check DM's to see if there are new messages. New messages still appear as bolded to distinguish which have been read/unread.

Ugh, you’re right…

On Dec 5, 2023, at 4:59 PM, KrishaTerranIO @.***> wrote:
I've noticed I'm not receiving notifications on my desktop for DM's. I have to manually check DM's to see if there are new messages.
—
Reply to this email directly, view it on GitHub https://github.com/Hylozoic/hylo-evo/issues/1575, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAA5HMYZUEBW4BWOLDZPFDYH67PZAVCNFSM6AAAAABAISLG4CVHI2DSMVQWIX3LMV43ASLTON2WKOZSGAZDONBSG4ZDINA.
You are receiving this because you are subscribed to this thread.


[deactivate] Manage forms

Summary | Résumé
Adds account dir + manage forms placeholder page
Pull Request Checklist
Please complete the following items in the checklist before you request a review:

[x] Have you completely tested the functionality of change introduced in this PR? Is the PR solving the problem it's meant to solve within the scope of the related issue?
[x] The PR does not introduce any new issues such as failed tests, console warnings or new bugs.
[ ] If this PR adds a package have you ensured its licensed correctly and does not add additional security issues?
[ ] Is the code clean, readable and maintainable? Is it easy to understand and comprehend.
[ ] Does your code have adequate comprehensible comments? Do new functions have docstrings?
[ ] Have you modified the change log and updated any relevant documentation?
[ ] Is there adequate test coverage? Both unit tests and end-to-end tests where applicable?
[ ] If your PR is touching any UI is it accessible? Have you tested it with a screen reader? Have you tested it with automated testing tools such as axe?

Merging to get the new route in place.


Build/Check cli commands throw Error: Cannot find module 'jsx-email'

Component or Package Name: jsx-email
Component or Package Version: 1.7.2
@jsxp-email/cli Version?:
Operating System (or Browser): Chrome
Node Version: 20.10.0
Link to reproduction (⚠ read below): https://stackblitz.com/edit/jsx-email-repro-vzgqmc

Expected Behavior
Running email build ./templates/Reproduction.tsx should successfully build the template.
Running email check ./templates/Reproduction.tsx should successfully run the compatibility check.
Actual Behavior
Throws and error instead: Error: Cannot find module 'jsx-email'
Additional Information
The behaviour is the same in local Windows environment as in repro link.

Hey @tom3rr
Can you try to run pnpm exec email build... or pnpm exec email check ...
For npm: npm run
For yarn: yarn run

@tom3rr confirmed that your reproduction has the issue. looking into it...

Alright this is almost certainly related to this change: https://github.com/shellscape/jsx-email/commit/e0a7eb44a96b85fed54d918bd3a05b788606267d#diff-956e216fa7df03ccf64dcfcbe8fdacf5560897b6726255ff29c1c3c8cc757721R124 and the way that pnpm, yarn, and npm differ in how they create binaries in node_modules/.bin
I was able to reproduce this locally with yarn and npm as well. I couldn't reproduce it locally with pnpm, but I could on the stackblitz repro. The preview works locally with all the package managers (this is something I would expect, because Vite is a different animal) but fails on stackblitz.
Under pnpm, the binary file in node_modules/.bin contains path information whereas npm and yarn are just straight up copies of the target file. Under pnpm, the compiled template file has context as to where it's being run, so it can use the local node_modules. Apparently on npm/yarn, this is not the case.
I'll revert that change shortly and publish a fix.

@lordelogos same result with yarn run
@shellscape Thanks for the fast response and fix. I can confirm that in 1.7.3 the issue is no longer present.


Plugins from 3rd party packages can't be loaded.

The plugin loader does not load plugins from 3rd party packages (eg. https://github.com/AMOSoft/zf1-extras).
This because the loader is checking if the class exists without allowing autoload to work.
This is old ZF1 code from pre-composer era.
Changing the code in the /src/Zend/Loader/PluginLoader.php file fixes this issue:
Line 383 (old):
            if (class_exists($className, false)) {

Fixed:
            if (class_exists($className, true)) {

Just stumbled upon this too


docs/improve-readme

Improve the README with

a high level overview of Dialect,
more succinct installation instructions,
better notes on how to run in local development,
notes on running tests, and
removed legacy docs.

cc @tsmbl


mdbtools: 0.9.3 -> 0.9.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/mdbtools/mdbtools/releases.
meta.description for mdbtools is: ".mdb (MS Access) format tools"
meta.homepage for mdbtools is: "https://github.com/mdbtools/mdbtools"
meta.changelog for mdbtools is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

Warning: no invocation of /nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-hexdump had a zero exit code or showed the expected version

/nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-export passed the binary check.

/nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-array passed the binary check.

/nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-schema passed the binary check.

/nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-tables passed the binary check.

/nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-parsecsv passed the binary check.

/nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-header passed the binary check.

/nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-sql passed the binary check.

/nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-ver passed the binary check.

/nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-prop passed the binary check.

/nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-count passed the binary check.

/nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-queries passed the binary check.

/nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin/mdb-json passed the binary check.

9 of 13 passed binary check by having a zero exit code.

3 of 13 passed binary check by having the new version present in output.

found 0.9.4 with grep in /nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4

found 0.9.4 in filename of file in /nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4

directory tree listing: https://gist.github.com/c6cfa8221c2b6fd91a2fe512901c9103

du listing: https://gist.github.com/8f5e8a16276cb3dfd248728474c086b0

Rebuild report (if merged into master) (click to expand)

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
mdbtools

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A mdbtools https://github.com/r-ryantm/nixpkgs/archive/88721710e3f89944f789ec5435104028d471af58.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4
ls -la /nix/store/253ms48ck7v4pnk3ssp98lsj63zw6021-mdbtools-0.9.4/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

mdbtools

Maintainer pings

Result of nixpkgs-review pr 134041 at 88721710 run on x86_64-linux 1

1 package built successfully:

mdbtools

5 suggestions:

warning: unused-argument
Unused argument: makeWrapper.
Near pkgs/tools/misc/mdbtools/default.nix:2:53:
  |
2 | , bison, flex, pkg-config, autoreconfHook, libxslt, makeWrapper
  |                                                     ^

warning: unclear-gpl
lgpl2 is a deprecated license, please check if project uses lgpl2Plus or lgpl2Only and change meta.license accordingly.
Near pkgs/tools/misc/mdbtools/default.nix:29:5:
   |
29 |     license = with licenses; [ gpl2 lgpl2 ];
   |     ^

warning: unused-argument
Unused argument: libxslt.
Near pkgs/tools/misc/mdbtools/default.nix:2:44:
  |
2 | , bison, flex, pkg-config, autoreconfHook, libxslt, makeWrapper
  |                                            ^

warning: unclear-gpl
gpl2 is a deprecated license, please check if project uses gpl2Plus or gpl2Only and change meta.license accordingly.
Near pkgs/tools/misc/mdbtools/default.nix:29:5:
   |
29 |     license = with licenses; [ gpl2 lgpl2 ];
   |     ^

warning: maintainers-missing
Package does not have a maintainer. Consider adding yourself?
Near pkgs/tools/misc/mdbtools/default.nix:30:5:
   |
30 |     maintainers = with maintainers; [ ];
   |     ^


⚠ Processors has degraded performance

In 0370917, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 151 ms

Resolved: Processors performance has improved in ba87682.


Feature/more than 10k results

Description of Change
Added  method get_all_file_events that searches for file events for a given query and returns a token to retrieve remaining events along with the response.
Issues Resolved

closes #227

Testing Procedure
sdk.securitydata.get_all_file_events(query)
sdk.securitydata.get_all_file_events(query, "Token")
PR Checklist
Did you remember to do the below?

[x] Add unit tests to verify this change
[x] Add an entry to CHANGELOG.md describing this change
[x] Add docstrings for any new public parameters / methods / classes

After the other feedback is addressed, I think these changes warrant an update to docs/userguides/searches.md


bump and pin rubocop and fix broken cop

PRs are starting to break on rubocop 0.39.2. This fixes violations and pins to that.

You probably want to pin to the version included in ChefDK with Chefstyle now, which is 0.38 I believe.

Sorry the above was a typo. It's 0.37.2 which is the exact same as what is in chef-dk master. https://github.com/chef/chef-dk/blob/master/omnibus/config/projects/chefdk.rb#L47

@mwrock Oddly enough ChefDK runs in Travis say it's 0.38, but on my laptop is says 0.37.2. :+1: this though

:+1:


Fix confirm dialogs

confirmdialog.res is for quit/disconnect UIs and requires its own custom BG that is modified per each state (abandonsafe, nopenalty, etc).
bh_confirmbase.res is for all other popup UIs, and shouldn't require its own custom BG because the border can be directly modified (at least given how I had it before).
confirmdialog.res includes bh_confirmbase, and the abandons point to confirmdialog. so I should just need to add the custom BG and paintborder 0 to confirmdialog, and then have bh_confirmbase treat the confirmdialog panels as it did before
may also need to look at centering all the explanationlabels again instead of west aligning. I believe my reason for west aligning was due to centerwrap at the time

these things are cursed


New command: m365 aad o365group conversation list

Usage
m365 aad o365group conversation list
Description
Retrieve conversations for the specified group
Options

Option
Description

-i, --groupId <groupId>
The Id of the Office 365 Group

Additional Info
https://docs.microsoft.com/en-us/graph/api/group-list-conversations?view=graph-rest-1.0&tabs=http
For readability CSV and Text output should return topic, lastDeliveredDateTime and  id

Can I work on this one?

Awesome! There you go!

In text/CSV output, shall we also include the id (assuming there's one) so that you can use it to retrieve the conversation's details (assuming that's relevant and that we'd have aad o365group conversation get at some point)?

@waldekmastykarz Happy to include that one in the specs; however the ID you get returned is quite long and most likely will not fit on your typical screen:
"id": "AAQkAGFhZDhkNGI1LTliZmEtNGEzMi04NTkzLWZjMWExZDkyMWEyZgAQAH4o7SknOTNKqAqMhqJHtUM="
I do agree that it has added value, just wasn't sure it would fit :)

I think in this case it's justified, while I fully agree that it's not ideal. We need bigger screens 😄

@akashkarda please make sure to include id as well, I have updated the specs ;-)

Sure. Thank you!


Support Solidity 0.8.22

Preface
This is based on latest solc-typed-ast version, that supports Solidity 0.8.22. Its purpose to estimate impact of changes.
Changes

[x] Update dependencies, use solc-typed-ast v17.0.2 with Solidity 0.8.22 support.
[x] Update miscellanious sample for Solidity 0.8 to check functionality correctness.

Regards.

Codecov Report

Merging #251 (6b38de9) into develop (6bf7565) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #251   +/-   ##
========================================
  Coverage    87.22%   87.22%
========================================
  Files           71       71
  Lines         5481     5481
  Branches      1236     1236
========================================
  Hits          4781     4781
  Misses         416      416
  Partials       284      284

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Third party file should be checked by the codegen

Problem
We have a third party file codegenerated by maven which is not checked by our codegen, generating merge conflicts
Persona:
Which persona is this feature for? Knative developer
Exit Criteria
Third party file should be checked by the codegenerator check
Time Estimate (optional):
1

Unfortunately, this would prevent us from using dependabot.

Unfortunately, this would prevent us from using dependabot.

Why?

Auditing dependencies' licenses.

Dependabot can't run maven plugins after updating the pom file.

Auditing dependencies' licenses.

Is that so important? Is there some requirement for that?

No, afaik

I'm gonna ask it to thu TOC about that.

https://groups.google.com/u/0/g/knative-dev/c/VsD5BUAIRwg

Thank you!

So we need to keep this file, and we can't automate it without changing dependabot :(

FYI https://github.com/dependabot/dependabot-core/issues/3622

/assign


created a readme file

Added mine DevOps roadmap

Glad to have you here @Ankur1493

Added mine Devops Roadmap


Unable to exclude ELB-HealthChecker/2.0 logs

Image used - fluent/fluentd-kubernetes-daemonset:v1.15.1-debian-cloudwatch-1.0
I'm trying to minimize the logs sent to CloudWatch and trying to not send kube-probe and load balancer healthchecks to cloudwatch.
Currently using exclude filter like this -
      <filter **>
        @type grep
        <exclude>
          key log
          pattern /GET \/health/
        </exclude>
      </filter>

Before Appling this filter I could see the following log lines -
<IP_ADDRESS> - - [12/Sep/2022:12:35:41 +0000] "GET /health HTTP/1.1" 200 15 "-" "kube-probe/1.23+" "-"
<IP_ADDRESS> - - [12/Sep/2022:12:35:42 +0000] "GET /health HTTP/1.1" 200 15 "-" "ELB-HealthChecker/2.0" "-"
After applying the above mentioned filter the kube-probe/1.23+ healtcheck is no longer sent to CloudWatch. However the ELB healtcheck logs are still sent to cloudwatch.

Found the issue, Needed to move the filter before the parser.


documentation: polish NB contract and add more comments

What type of PR is this?
/kind cleanup
/kind documentation
What this PR does / why we need it:
Polishing the contract and add more comments
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2450

Relevant Lines:
2985

💛  - Coveralls


gesture request: double tap

Is it hard to support  double tap gesture?

No, you'll just need to listen for the tap event.  If another tap event is fired again, and it is within a duration that you decide, you can determine it was a double tap.  Pseudocode:
last_timestamp = null
widget.on(tap) => {
	if(last_timestamp is not null and now - last_timestamp < 500) {
		// double tap
	}
	last_timestamp = now
}

The solution @cookieguru proposed will actually work but in general we should add support for it in Tabris.js

@mpost that would mean the timeout is platform dependent?

@cookieguru It would follow the platform conventions.


chore(main): release 0.1.1

:robot: I have created a release beep boop
0.1.1 (2024-01-16)
Features

update auth service proto (#3) (b6f6bea)
update auth service proto (#9) (44f8098)

Bug Fixes

ci: remove golang ci linter (#5) (ab9eb56)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/kyamalabs/proto/releases/tag/v0.1.1 :sunflower:


Unable to override FormBuilderPlugin fields with a join field (SQLite only)

Link to reproduction
https://github.com/mikecebul/payload/tree/traverse-fields-error
Environment Info
Binaries:
Node: 20.14.0
npm: 10.7.0
Yarn: 1.22.22
pnpm: 9.1.4
Relevant Packages:
payload: 3.0.0-beta.113
next: 15.0.0-canary.173
@payloadcms/email-resend: 3.0.0-beta.113
@payloadcms/graphql: 3.0.0-beta.113
@payloadcms/live-preview: 3.0.0-beta.113
@payloadcms/live-preview-react: 3.0.0-beta.113
@payloadcms/next/utilities: 3.0.0-beta.113
@payloadcms/plugin-cloud-storage: 3.0.0-beta.113
@payloadcms/plugin-form-builder: 3.0.0-beta.113
@payloadcms/plugin-redirects: 3.0.0-beta.113
@payloadcms/plugin-seo: 3.0.0-beta.113
@payloadcms/plugin-stripe: 3.0.0-beta.113
@payloadcms/richtext-lexical: 3.0.0-beta.113
@payloadcms/storage-s3: 3.0.0-beta.113
@payloadcms/translations: 3.0.0-beta.113
@payloadcms/ui/shared: 3.0.0-beta.113
react: 19.0.0-rc-3edc000d-20240926
react-dom: 19.0.0-rc-3edc000d-20240926
Operating System:
Platform: linux
Arch: x64
Version: #1 SMP Fri Mar 29 23:14:13 UTC 2024
Available memory (MB): 15847
Available CPU cores: 16
Describe the Bug
Error exists on beta > 111
Adding a join field after the default fields results in an error:
formBuilderPlugin({
      formOverrides: {
        fields: ({ defaultFields }) => {
          const joinField: JoinField =
          {
            name: 'submissions',
            collection: 'form-submissions',
            type: 'join',
            on: 'form',
          }
          return [...defaultFields, joinField]
        },
      },
    }),

 ⨯ TypeError: Cannot read properties of undefined (reading 'targetField')
    at eval (webpack://payload-monorepo/packages/db-sqlite/src/schema/traverseFields.ts?4329:942:24)
    at Array.forEach (<anonymous>)
    at field (webpack://payload-monorepo/packages/db-sqlite/src/schema/traverseFields.ts?4329:118:10)
    at tableName (webpack://payload-monorepo/packages/db-sqlite/src/schema/build.ts?0366:138:21)
    at eval (webpack://payload-monorepo/packages/db-sqlite/src/init.ts?7a40:68:15)
    at Array.forEach (<anonymous>)
    at Object.init (webpack://payload-monorepo/packages/db-sqlite/src/init.ts?7a40:40:35)
    at reload (webpack://payload-monorepo/packages/next/src/utilities/getPayloadHMR.ts?586b:59:3)
    at collections (webpack://payload-monorepo/packages/next/src/utilities/getPayloadHMR.ts?586b:81:7)
    at permissions (webpack://payload-monorepo/packages/next/src/utilities/initPage/index.ts?6498:24:19)
    at NotFoundPage (webpack://payload-monorepo/packages/next/src/views/NotFound/index.tsx?e192:60:26)
digest: "829711485"

Placing the join field in front of the the default fields does not cause an error:
formBuilderPlugin({
      formOverrides: {
        fields: ({ defaultFields }) => {
          const joinField: JoinField =
          {
            name: 'submissions',
            collection: 'form-submissions',
            type: 'join',
            on: 'form',
          }
          return [joinField, ...defaultFields]
        },
      },
    }),

Reproduction Steps

Start the plugin-form-builder test folder pnpm dev plugin-form-builder
add sqlite as the db
add a join field for form-submissions, at the end of the array o fields, to the form fields override.

If you add the join before the default fields it does not error
Adapters and Plugins
db-sqlite, plugin-form-builder

This was resolved with beta.114 or beta.115.


Error While Training with Yelp Dataset

While I trained model with Yelp Dataset prepared by yelp_prepare.py,  I got error log as follow.
The code has been ran with tensorflow 1.0.1 and Python 2.7.12 in Linux.
....
step 251, loss=1.55983, accuracy=0.2, t=19.89, inputs=(30, 30, 30)
Traceback (most recent call last):
  File "worker.py", line 220, in <module>
    main()
  File "worker.py", line 215, in main
    train()
  File "worker.py", line 195, in train
    ], fd)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 767, in run
    run_metadata_ptr)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 965, in _run
    feed_dict_string, options, run_metadata)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 1015, in _do_run
    target_list, options, run_metadata)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/client/session.py", line 1035, in _do_call
    raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: indices[28,0,6] = 50000 is not in [0, 50000)
	 [[Node: tcm/tcm/embedding/embedding_lookup = Gather[Tindices=DT_INT32, Tparams=DT_FLOAT, _class=["loc:@tcm/embedding/embedding_matrix"], validate_indices=true, _device="/job:localhost/replica:0/task:0/cpu:0"](tcm/embedding/embedding_matrix/read, _recv_tcm/inputs_0)]]

Caused by op u'tcm/tcm/embedding/embedding_lookup', defined at:
  File "worker.py", line 220, in <module>
    main()
  File "worker.py", line 215, in main
    train()
  File "worker.py", line 165, in train
    model, saver = model_fn(s)
  File "worker.py", line 97, in HAN_model_1
    is_training=is_training,
  File "/data/zhiheng/project/deep-text-classifier/HAN_model.py", line 63, in __init__
    self._init_embedding(scope)
  File "/data/zhiheng/project/deep-text-classifier/HAN_model.py", line 102, in _init_embedding
    self.embedding_matrix, self.inputs)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/embedding_ops.py", line 111, in embedding_lookup
    validate_indices=validate_indices)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/ops/gen_array_ops.py", line 1359, in gather
    validate_indices=validate_indices, name=name)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/op_def_library.py", line 763, in apply_op
    op_def=op_def)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 2327, in create_op
    original_op=self._default_original_op, op_def=op_def)
  File "/usr/local/lib/python2.7/dist-packages/tensorflow/python/framework/ops.py", line 1226, in __init__
    self._traceback = _extract_stack()

InvalidArgumentError (see above for traceback): indices[28,0,6] = 50000 is not in [0, 50000)
	 [[Node: tcm/tcm/embedding/embedding_lookup = Gather[Tindices=DT_INT32, Tparams=DT_FLOAT, _class=["loc:@tcm/embedding/embedding_matrix"], validate_indices=true, _device="/job:localhost/replica:0/task:0/cpu:0"](tcm/embedding/embedding_matrix/read, _recv_tcm/inputs_0)]]

Edge case. Interesting how I didn't encounter it before. Fixed it with #377040e6a8a788d15c913a2a0ff335b9bc8f1cc5 so that preprocessed data remains compatible, but not checkpoints.


Add Rook/Ceph as a storage provider for Shoot and Seed clusters

How to categorize this PR?

/area storage
/kind enhancement
/priority normal
/platform equinix-metal
What this PR does / why we need it:
This PR adds Rook/Ceph as a storage provider for Shoot clusters, so Shooted Seeds can function properly.
Which issue(s) this PR fixes:
Fixes #108
Special notes for your reviewer:
Draft as there is several things which do not work yet, as:

Removing Shooted Seeds and sometimes Shoots with this PR sometimes gets stuck.
Volume provisioning does not work reliably.

Still opening the PR to "publish" this work in case someone wants to help debugging etc.
TODO:

[ ] Update documentation around ControlPlaneConfig

Release note:

Added Rook/Ceph as an optional storage layer implementation for Shoot clusters

Thank you @invidian for your contribution. Before I can start building your PR, a member of the organization must set the required label(s) {'reviewed/ok-to-test'}. Once started, you can check the build status in the PR checks section below.

/close in favor of #136


APP-1319: Fixing runtime NoClassDefFoundError IClientCryptoHandler.

Codecov Report

Merging #139 into dev will decrease coverage by 0.05%.
The diff coverage is 95.65%.

@@            Coverage Diff             @@
##              dev     #139      +/-   ##
==========================================
- Coverage   90.22%   90.16%   -0.06%
==========================================
  Files         141      171      +30
  Lines        2792     3488     +696
  Branches      261      326      +65
==========================================
+ Hits         2519     3145     +626
- Misses        215      257      +42
- Partials       58       86      +28

Impacted Files
Coverage Δ

...ss/integration/core/service/CryptoServiceImpl.java
94.91% <95.65%> (+25.03%)
:arrow_up:

...provisioning/properties/ApplicationProperties.java
0% <0%> (ø)

...on/provisioning/exception/UpdateUserException.java
100% <0%> (ø)

...xception/IntegrationProvisioningAuthException.java
100% <0%> (ø)

...ion/provisioning/properties/KeyPairProperties.java
0% <0%> (ø)

...ration/provisioning/service/AppKeyPairService.java
100% <0%> (ø)

...ion/provisioning/client/model/AppStoreWrapper.java
94.11% <0%> (ø)

...roperties/ConfigurationProvisioningProperties.java
0% <0%> (ø)

...ation/provisioning/IntegrationProvisioningApp.java
50% <0%> (ø)

...ning/service/ConfigurationProvisioningService.java
93.75% <0%> (ø)

... and 21 more

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 f947a21...38139f1. Read the comment docs.


Update nix api for version 0.7.1 and later

Git rev 45c82235a3b91939ea9a656c6afcf71be15411f3, to be released in
Nix 0.7.1 or later, changes the API of KEvent.
https://github.com/nix-rust/nix/pull/442 must be merged before this PR will build.

Thanks for the PR! Right now master of this repo is the 0.6 release of mio, so we're hoping to not introduce git dependencies as that would block another point release of mio. Perhaps though this could be updated once the changes to nix are merged?

In fact, the changes to nix just got merged yesterday.  Or do you mean we should update this PR once nix has a new release?  I'll certainly do that.
https://github.com/nix-rust/nix/commit/652e730f106fd3c103ba7549e64a7c992a72f11a

Yeah once there's a new release of nix we can pull that in.

Since there are semver breaking changes in a few places, we are probably looking at a release 0.8.0 as the next release of nix.  We don't have a solid date on that in mind right now, but if there is urgency we can probably look to expedite.  I am doing a pass through nix improving (or just adding) documentation across the board which has led to some API changes where things were either broken or doing users no service.

@posborne sounds good to me! AFAIK there's no burning desire to get this updated, so mio can just update whenever 0.8.0 is released

The dependency on nix was removed as we weren't using much of it anyway and we ended up with custom bits.


Text with line breaks?

Sorry but can't find how to put line breaks in the text field.

Hello! Sorry for the delay.
I just pushed out a new version with all new and improved phrase editor, so everything should work now.


zod.nonempty() is deprecated

.nonempty() is deprecated adn replaced by .min(1) as per zod documentation.
See https://github.com/colinhacks/zod#strings

Thank you.


Documentation request: Config recipes for minimal config setup

Describe the feature
I appreciate the work to consolidate the use of eslint and prettier with Nuxt. I am self taught and although I understand the general principles of what each of these packages achieves, I have limited understanding of how they are configured and have got this far without having to dive into them. I have always been able to copy others' configs and have been happy with that. I don't have opinions about semicolons and tabs/spaces as long as it's neat.
I am currently starting a project with Nuxt 3 (and the new Nuxt module) and for the first time, although some aspects are working, I can't get my code looking nice at all. If I look at other repos for clues (e.g. NuxtHub), they all seem to use something different to what's in the docs. I can't tell if the 3 packages listed are mutually exclusive or do I need a bit of each?
Because the linting and prettifying ecosystem seems to change frequently and is optimised for flexibility, it seems there are lots of ways I could get the configuration wrong. For example:

What should the settings in VS Code look like? Might I be overriding things by mistake?
Should I have a .vscode folder and settings.json file in each project? What should be in them?
Do I need typescript installed as a dev dependency? Or anything else in addition to @nuxt/eslint & eslint?
I'd be happy not to use prettier if eslint can make things look nice but if I add stylistic: true nothing happens - should I disable prettier in VS Code or do I need to install something else to the project to make it work?

It would really help me to have a simple recipe or example using the latest module (or a link to a well maintained example).
I think it would need to help me achieve some sensible defaults:

Sorting out my indenting & quotes etc so that by the time I save a file, it looks presentable like code on the Nuxt docs
Making all files in a typical Nuxt app look nice including .md files in the content folder (both frontmatter & markdown)
How to get eslint to prettify the files OR how to set up prettier alongside

I think it would help to be able to see:

What packages are added to package.json
What to look out for in VS Code settings that might get in the way (is there a way of using a .vscode folder and settings.json file to "reset" VS Code-wide settings on a project basis?)
What should be in a typical eslint.config.mjs file

I hope that would be helpful to others too and I'd be more than happy to help in any way I could.
Thanks
Rich
Additional information

[X] Would you be willing to help implement this feature?
[ ] Could this feature be implemented as a module?

Final checks

[X] Read the contribution guide.
[X] Check existing discussions and issues.

Trying to answer some of these questions based on my understanding and what I read on the docs. You should be able to set it up the way you described if you follow the instructions from the docs and ensure you have similar config to the one I'm sharing below.
Make sure to check the Eslint Output console in vscode to ensure there are no errors and everything is working correctly.
Hope this helps 👍

I can't tell if the 3 packages listed are mutually exclusive or do I need a bit of each?

According to the FAQ page on the docs you only need the module aka @nuxt/eslint.

What to use?
For new projects, we highly recommend using the ESLint Module which provides a project-aware ESLint flat config generation and is more future-proof.
If you still use the legacy .eslintrc format, you can use the ESLint Config package to manually configure your ESLint settings. We recommend you to migrate to the flat config format if possible.
If you are maintaining your custom ESLint config and want a low-level setup, you can use the ESLint Plugin package directly to enable some Nuxt-specific rules in your config.

What should the settings in VS Code look like? Might I be overriding things by mistake?
Should I have a .vscode folder and settings.json file in each project? What should be in them?

Here's what my .vscode/settings.json looks like:
{
  "eslint.useFlatConfig": true,
  "editor.codeActionsOnSave": {
    "source.fixAll.eslint": "always",
  },
}

I use this file to make sure I don't force these settings on other projects that might use the older config format or different version of the tools. It also ensures other folks working on the project get the same benefits from eslint and other dependencies.
Not sure you need to add anything specific to your global settings but just in case here's what I have:
{
  "eslint.debug": true,
  "eslint.validate": [
    "javascript",
    "javascriptreact",
    "vue",
  ],
}

Do I need typescript installed as a dev dependency? Or anything else in addition to @nuxt/eslint & eslint?

You do not. It already is a dependency of whichever packages need it.
Check the Manual Setup section in the docs for more info (you'll see there they only ask you to install @nuxt/eslint and eslint).

I'd be happy not to use prettier if eslint can make things look nice but if I add stylistic: true nothing happens - should I disable prettier in VS Code or do I need to install something else to the project to make it work?

Did you check the playground dir in this repo? It has a complete example of a working project.
Again, just in case, here's what my config looks like:
import withNuxt from './.nuxt/eslint.config.mjs'

export default withNuxt()
  .override('nuxt/stylistic', {
    rules: {
      '@stylistic/arrow-parens': ['error', 'always'],
    },
  })

Thank you for such an in-depth reply @hacknug

Make sure to check the Eslint Output console in vscode to ensure there are no errors and everything is working correctly.

Turns out one of the problems I had/have is that the language server in VS Code crashes fairly regularly so restarting VS Code after each eslint config change seems like very good advice.

Here's what my .vscode/settings.json looks like:

Brilliant - thank you.

Not sure you need to add anything specific to your global settings but just in case here's what I have:

I found I had to go into VS Code global settings and delete a bunch of rules that have accumulated before the project level settings worked.

Do I need typescript installed as a dev dependency? Or anything else in addition to @nuxt/eslint & eslint?

You do not. It already is a dependency of whichever packages need it.

I removed it but then when I tried the ESLint Config Inspector in Nuxt DevTools, it wouldn't load and gave me the message to install typescript. After re-installing typescript, it worked again.

Did you check the playground dir in this repo? It has a complete example of a working project.

I had not noticed it, but when I looked, there were extra rules in nuxt.config.ts that caused new warnings (the component rule) and the eslint.config.mjs file was empty. Your example was much more helpful - thanks.
One last thing, since changing my config, I now get the following error message every time I run yarn nuxi dev:
 ERROR  [unhandledRejection] Cannot find package 'vite-plugin-eslint2' imported from<EMAIL_ADDRESS>It doesn't prevent the site from launching but I've no idea what's caused it. I've tried deleting node-modules and reinstalling.

Thanks again @hacknug. I've had another good play with the settings and I think I've finally got it working as expected.

I removed it but then when I tried the ESLint Config Inspector in Nuxt DevTools, it wouldn't load and gave me the message to install typescript. After re-installing typescript, it worked again.

I think this is something specific to your project because I don't have it listed on my package.json and the eslint config inspector works flawlessly.

You were absolutely correct that typescript is not required. When I tried to reproduce the issue, I found that the ESLint Config Inspector in Nuxt DevTools only loaded properly when the following eslint settings were in nuxt.config.ts (I think I had previously set stylistic: true somewhere else)
eslint: {     config: {       stylistic: true     } }

One last thing, since changing my config, I now get the following error message every time I run yarn nuxi dev:
 ERROR [unhandledRejection] Cannot find package 'vite-plugin-eslint2' imported from<EMAIL_ADDRESS>It doesn't prevent the site from launching but I've no idea what's caused it. I've tried deleting node-modules and reinstalling.

Not sure what could be causing this issue but did you try running npx nuxi@latest upgrade --force to force your package manager to regen tis lockfile and install the latest in-range version of your deps?

My lockfile actually looked identical to yours but I tried npx nuxi@latest upgrade --force and also changed from yarn to pnpm (something I'd been meaning to do for a while). None of this had any effect until I changed my nuxt.config.ts settings again. I had previously copied the eslint settings from nuxt.config.ts on the example repo you linked to. Commenting out the checker settings got rid of the error.
eslint: {     config: {       stylistic: true     }     // checker: {     //   lintOnStart: true,     //   fix: true,     // }, },
Now that I have a fully working eslint config, I may still write my own recipe before I forget what I did. Would that be worth sharing with you on this thread?

Thanks for your help and great answers @hacknug!
I didn't follow the questions a lot, but I assume most of them should be resolved. I am marking this as closed for now. If you have any more doubts to the docs, or find some weird behaviour - please create issues/discussions for each of them so we could better keeping those conversations on track.
Thanks!


Allow operators to setup a default certificate

Fixes: https://github.com/knative-sandbox/net-contour/issues/182

/hold
going to stage the docs

/retest

/hold cancel

rebased


[Maintenance] Update workflows to use macos-12 agents

@Nillerr I forked and updated to macos-12, the build action seems to work as expected:
https://github.com/harmittaa/mockative/actions/runs/3060447417/jobs/4938974278#step:1:4
Do you happen to know of any easy ways to test the Release workflow as well, besides that I create Sonatype credentials and run it against them?


switches to inactive instance of editor when 2 instances are open in the same desktop

When using VS code 2 instances on the same desktop,

open maccy popup using the keyboard shortcut
select an item to copy using arrow keys
hit return

Maccy switches to the vs code instance in the background.
Expected to stay on the active instance as it is.

Interesting - I will take a look at this issue. In the meantime, can you try enabling "Avoid taking application focus" in advanced preferences?

a restart fixed the issue, not sure if it needs investigation anymore


Fix build FableCore on Windows

I added one more thing - I want to reference Fable via Paket Git dependency (so that I can get the latest version without waiting for a release). For this, it would be useful to have a target that builds All and FableCore, so that I can just say in my paket.dependencies:
git https://github.com/fsprojects/Fable.git master build: "build.cmd AllAndCore", OS: windows
git https://github.com/fsprojects/Fable.git master build: "build.sh AllAndCore", OS: mono

And get everything built by Paket :)

Looks like you need to run All before FableCore, but I didn't want to make it a hard dependency - because I guess you often just want to run FableCore by hand once you've built everything.
This FAKE magic seems to be doing the trick - it says that if you are running both targets, All should run before FableCore:
"All" ?=> "FableCore"

Thanks!


Fixing errors not sending to ray.

Please check this. We cant get the errors to go to ray. after changing this in node modules files we got it fixed. I also have updated the readme and chanelog. please merge en create a tag.

Can you please merge this and create a release.

@dangnhdev @gldrenthe89 Thanks for the heads up, I'll review and merge shortly.


Correct class name in example

"ItemRequestOption" should be "ItemRequestOptions"

@sdbrannum : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@SnehaGunda: I'm sorry - only the author of this article, @j82w, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@ktoliver can you please merge this PR.


Battery min/max state tracked

Added the endpointid fingerprint. It seems to make it so that Smartthings will detect and present the Xiaomi device as a valid thing. There's a delay between when the device pairs and when the app shows it as a thing.
Changed the battery calculation to use the average of min and max of the battery value. I was noticing the battery percent ping-ponging between two values, so this will smooth out the reading.

Before I merge the changes for the battery I would like to get an understanding if the devices are working more reliable.  Currently I feel like my Xiaomi devices are performing better than they have ever performed.  Not sure why the end points need to change because the devices I have automatically add without having to perform the catchall.
Looking for more feedback.

Sure.
I was using your original code before my changes, but it was not showing up
as a thing until I added the other endpoint by Gavin. I just read the
documentation on the fingerprint and I think I can clean up that bit of
code some more.
Yeah, the code was working fine for me as well. The changes I've made are
related to fixing the battery level ping-ponging (going from 98 to 99 to 98
to 99, etc.), and to try to reduce the number of times battery info is
sent. Not sure if my change will work yet, but I'm just testing it out. I
also changed the voltage range to 2.7 to 3.3 based on the apparent
documentation, but I also already knew that battery is spec'ed to be
theoretically 3.4 v max.
In any case, it's up to you if you want to merge after testing. I just
figured it'd be better to have a single source for the DH.
On Tue, Dec 5, 2017 at 10:14 AM, bspranger<EMAIL_ADDRESS>wrote:

Before I merge the changes for the battery I would like to get an
understanding if the devices are working more reliable. Currently I feel
like my Xiaomi devices are performing better than they have ever performed.
Not sure why the end points need to change because the devices I have
automatically add without having to perform the catchall.
Looking for more feedback.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bspranger/Xiaomi/pull/4#issuecomment-349392241, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK9pVonBxVTSL8HFqBsI7F4wqEbRPQuSks5s9YgVgaJpZM4QzX7c
.

I am totally wanting to have a common code.  So I am not against integrating your code.  I just want to understand it and make sure we are making forward progress.
Groovy is completely new to me, I am usually developing embedded C, so it has been a lot of hunting and pecking to get what I have working.
The Xiaomi devices are awesome, small, quick to respond, great battery life.  I want to make sure these things are working the best they can.

Sounds like a plan. I'm new to Groovy as well, but I'm very familiar with
Java, C and C++, so it's not too hard. The hard part for me is not knowing
the Smartthings framework (I don't feel like learning it), and the Xiaomi
protocol (no documentation). But I just started working on this the past
few days so I'm still learning as well.
I think where it is now, it's pretty good for most needs and I don't plan
to spend too much time doing this. I only wanted to make sure the battery
level readings were usable and to make it simple to add to Smartthings.
I just wish the responses for some of the events were faster (like the
button press takes too long to trigger my automation).
On Tue, Dec 5, 2017 at 10:39 AM, bspranger<EMAIL_ADDRESS>wrote:

I am totally wanting to have a common code. So I am not against
integrating your code. I just want to understand it and make sure we are
making forward progress.
Groovy is completely new to me, I am usually developing embedded C, so it
has been a lot of hunting and pecking to get what I have working.
The Xiaomi devices are awesome, small, quick to respond, great battery
life. I want to make sure these things are working the best they can.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bspranger/Xiaomi/pull/4#issuecomment-349399909, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK9pVq7Pg-r611vO6JsRRHyllPXk6SDBks5s9Y3wgaJpZM4QzX7c
.

Check out this link.
http://zigate.fr/produits-xiaomi-compatibles-zigate/
It has all the zigbee messages broken out.  Now we can parse the messages without guessing.

Oh sweet!
On the original Xiaomi door sensor, I noticed it doesn't do a zbjoin like
the Aqara version does.  Because of this, I can't figure out what it's
endpoint information is to get it to map to the DH. Do you know what it
takes to get ST to get a zigbee device to join the network? It can't be
something in the DH because it doesn't get associated with a DH until after
the zbjoin occurs.
On Tue, Dec 5, 2017 at 7:50 PM, bspranger<EMAIL_ADDRESS>wrote:

Check out this link.
http://zigate.fr/produits-xiaomi-compatibles-zigate/
It has all the zigbee messages broken out. Now we can parse the messages
without guessing.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bspranger/Xiaomi/pull/4#issuecomment-349524045, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK9pVhuajTegoBQp7odZPSKtgxy3a1oIks5s9g7_gaJpZM4QzX7c
.

That is strange,  I have no issues with my original door sensors joining.   I have a ton of them.  Only 1 aqara door sensor.  So I am not sure there is an issue with the DH.

I think you can see them in the catch all too.
They are documented in the link I sent.

I see the catchall, but until ST does a zbjoin, it won't do a DH lookup.
On Tue, Dec 5, 2017 at 7:59 PM, bspranger<EMAIL_ADDRESS>wrote:

I think you can see them in the catch all too.
They are documented in the link I sent.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bspranger/Xiaomi/pull/4#issuecomment-349525509, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK9pVsVWDNY0igz9zqNW55BDxqf16RPaks5s9hEwgaJpZM4QzX7c
.

The document isn't showing any of the status message either (ie. battery
value). I guess it doesn't really matter. The current code seems to have
everything working anyway.
On Tue, Dec 5, 2017 at 8:01 PM, Bizapp<EMAIL_ADDRESS>wrote:

I see the catchall, but until ST does a zbjoin, it won't do a DH lookup.
On Tue, Dec 5, 2017 at 7:59 PM, bspranger<EMAIL_ADDRESS>wrote:

I think you can see them in the catch all too.
They are documented in the link I sent.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bspranger/Xiaomi/pull/4#issuecomment-349525509, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK9pVsVWDNY0igz9zqNW55BDxqf16RPaks5s9hEwgaJpZM4QzX7c
.

I will try to get these changes merged soon.  Haven't had a chance to get on the PC.

No worries. It would be nice if we could get these to a point where it can
be submitted and approved for public publishing. I'd really like to run the
buttons locally as the latency is annoying.
On Fri, Dec 8, 2017 at 7:34 PM, bspranger<EMAIL_ADDRESS>wrote:

I will try to get these changes merged soon. Haven't had a chance to get
on the PC.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bspranger/Xiaomi/pull/4#issuecomment-350420809, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK9pVnM5trrk-vNpLNEEWzNYFxtMsxS0ks5s-f-6gaJpZM4QzX7c
.

merging changes from snalee

Maybe you should change the namespace and author to something different
than a4refillpad? It's no longer the same and it will reduce confusion in
the device handler list.
On Sun, Dec 10, 2017 at 11:57 AM, bspranger<EMAIL_ADDRESS>wrote:

Merged #4 https://github.com/bspranger/Xiaomi/pull/4.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bspranger/Xiaomi/pull/4#event-1380483838, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK9pVribbEI_sabdBvTbUrRXpWlnasVYks5s_DeRgaJpZM4QzX7c
.

I tried to do that once and it broke stuff.
Do you know what I need to change?  Because I agree that I need to change it.  But I think it needs to align with github somehow.

In this line, just change the namespace and author strings:
definition (name: "Xiaomi Aqara Door/Window Sensor", namespace: "a4refillpad
", author: "a4refillpad") {
I don't know why it would break github. It's only used by SmartThings.
On Sun, Dec 10, 2017 at 3:22 PM, bspranger<EMAIL_ADDRESS>wrote:

I tried to do that once and it broke stuff.
Do you know what I need to change? Because I agree that I need to change
it. But I think it needs to align with github somehow.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bspranger/Xiaomi/pull/4#issuecomment-350590358, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK9pVsjs7W1NiHTKPcg6emJaoC8qcR32ks5s_Ge6gaJpZM4QzX7c
.

BTW all your changes are merged.
I will try to change it at some point soon.

Cool. I think I'm pretty much done mucking with the door and button code
for now. It's stable and works.
On Sun, Dec 10, 2017 at 3:40 PM, bspranger<EMAIL_ADDRESS>wrote:

BTW all your changes are merged.
I will try to change it at some point soon.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/bspranger/Xiaomi/pull/4#issuecomment-350591504, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK9pVsL2uqs4WIF_blY27hbhc8gcaPQoks5s_GvRgaJpZM4QzX7c
.


/flip command gives error: Duplicate registration received from the following participant

Tried running /flip in the #test channel of keybasefriends and am getting the following error:
Duplicate registration received from the following participant:
ctismer (device: Helgolaender)

Fairly certain you have two devices with the same private key. Did you happen to clone a laptop or desktop that had Keybase already installed on it?

Solution if this is indeed the case (worked for me):

Deauthorize the duplicated devices within keybase. *CRITICALLY IMPORTANT: HAVE AT LEAST ONE OTHER DEVICE (E.G., A SMARTPHONE WITH KEYBASE INSTALLED AND LOGGED IN) THAT CAN RE-AUTHORIZE YOU).

Re-authorize the device

A device of mine is causing this issue.  I never copied any private keys to any other device nor have I cloned my home directory so I am pretty sure that I don't have two devices with the same private key.  Here is the debug log id from the device preventing people in teams I participate in to use /flip: b0cf051ee6bb99daf2fae71c

Fairly certain you have two devices with the same private key. Did you happen to clone a laptop or desktop that had Keybase already installed on it?

I didnt, maybe someone else in the chat did?

Yes, that would do it as well.

Looks like the client should sanity check:
"Have I already submitted mine? If so, ignore"

if someone submits duplicate registers, they should be rejected from the pool.

Maybe...but could this also be a way of changing the result? I think better to invalidate the whole thing, similar to the effect of someone losing network connectivity. See also Mental Poker.

Client side sanity check shouldn't change the result. If I check, and I myself have already registered, I should realize that my key must be cloned somewhere and registering would mess up everyone's flip and then abstain.
However, this would require all affected accounts with multiple devices using the same device key to update their client to prevent this problem.
In the end, there is no way to know if someone is messing up because of a bug in keybase client or because they want to intentionally mess up the flip...
As far as other members rejecting a register because it is a duplicate, yeah that could be gamed.
Another way to fix it might be that a client could forbid two devices logging in simultaneously with the same device key and pop up with a "log out or provision a new device key"... would be a headache for anyone doing oneshot with bots though...

I am assuming the registries are signed. So I would know for a fact my private key is somewhere else. lol