Connection refused on remote kafka node

Good day,
I have a problem connecting to a remote kafka node (which works fine) when doinh:
client = new kafka.Client('<remote-ip>:2181')
The error is:  ECONNREFUSED <IP_ADDRESS>:9092 which I find strange since I am passing a remote address, not localhost...
Thank you,
Alex.

@fnbns Did you get this working? I'm running into the same issue.

@fnbns What was the fix? I'm having the same problem.

I am facing the same issue. Have you find the solution.

Facing the same issue

Kafka Broker and Zookeeper on the single EC2 instance
Producer in another EC2 instance
Consumer in another EC2 instance
Able to ping all 3 servers from both externally and internally using public IP and private IP

Kafka Broker configurations
server.properties
advertised.listeners=PLAINTEXT://<KafkaBroker/Zookeeper Private IP of EC2>:9092 zookeeper.connect=<KafkaBroker/Zookeeper Private IP of EC2>:2181
producer.properties
bootstrap.servers=<Producer Public IP of EC2>:9092
Producer configuration
connection.js
this.client = new kafka.KafkaClient("<KafkaBroker/Zookeeper Public IP of EC2>:2181");
Consumer configuration
connection.js
this.client = new kafka.KafkaClient("<KafkaBroker/Zookeeper Public IP of EC2>:2181");
Error at both producer and consumer EC2s
events.js:167
throw er; // Unhandled 'error' event
^
Error: connect ECONNREFUSED <IP_ADDRESS>:9092
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1113:14)
Emitted 'error' event at:
at KafkaClient. (/home/ec2-user/kafka-frontend/node_modules/kafka-node/lib/baseProducer.js:101:10)
at KafkaClient.emit (events.js:182:13)
at KafkaClient.EventEmitter.emit (domain.js:442:20)
at async.series.error (/home/ec2-user/kafka-frontend/node_modules/kafka-node/lib/kafkaClient.js:165:16)
at /home/ec2-user/kafka-frontend/node_modules/async/dist/async.js:3888:9
at /home/ec2-user/kafka-frontend/node_modules/async/dist/async.js:473:16
at iterateeCallback (/home/ec2-user/kafka-frontend/node_modules/async/dist/async.js:988:17)
at /home/ec2-user/kafka-frontend/node_modules/async/dist/async.js:969:16
at /home/ec2-user/kafka-frontend/node_modules/async/dist/async.js:3885:13
at async.doWhilst (/home/ec2-user/kafka-frontend/node_modules/kafka-node/lib/kafkaClient.js:207:9)
at /home/ec2-user/kafka-frontend/node_modules/async/dist/async.js:969:16
at next (/home/ec2-user/kafka-frontend/node_modules/async/dist/async.js:3022:18)
at connectToBroker (/home/ec2-user/kafka-frontend/node_modules/kafka-node/lib/kafkaClient.js:188:11)
at /home/ec2-user/kafka-frontend/node_modules/lodash/lodash.js:10050:25
at onError (/home/ec2-user/kafka-frontend/node_modules/kafka-node/lib/kafkaClient.js:234:5)
at Socket. (/home/ec2-user/kafka-frontend/node_modules/kafka-node/lib/kafkaClient.js:248:5)
Please help me!


fix(pagination): separate total count query

In the first iteration of pagination we used the window function over(), to do a somewhat performant and simple way to grab the total number of results in a query (before limit is applied). However this does not support distinct, which is needed in a AppVersion query. So whenever a distinct is used in a query, and whenever there are duplicate tuples, the total will be more than what we actually want.
In this PR I've switched out the window-function with a separate total-count query. In the initial implementation I argued against this due to performance reasons. But due to the constraints above, I've decided to implement it with a separate query, as it's much more flexible (which is how DHIS2 handles total as well). There's some performance issues with total in DHIS2, but that is with millions of entries and our database is not expected to grow to that level. The queries take single digit ms on my machine.
Another approach would be to rewrite queries to not use distinct, but that complicates these queries.

 I will rewrite all the executeQuery-test to use actual knex-queries instead of mocks.


Reland 3: [CupertinoActionSheet] Match colors to native

Relands https://github.com/flutter/flutter/pull/149568 (first attempt) or https://github.com/flutter/flutter/pull/150129 (latest attempt), which was reverted in https://github.com/flutter/flutter/pull/150142 due to unverified golden tests post-commit from recent infra issues.
No code is changed from https://github.com/flutter/flutter/pull/150129.
The relevant golden files have been resubmitted in https://github.com/flutter/flutter/pull/150219. I expect these files to appear in the golden file checker in this PR (which will hint that this PR is safe.) Fingers crossed.
Pre-launch Checklist

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

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

Reason for revert: the Mac framework_tests_impeller check has been failing (due to golden test failures) since this PR (though it occasionally passes after retry). Taking a brief look at this PR, it looks like there's been some troubles with goldens in the past (though the recent failures appear very different to past ones). Regardless, I'm taking a shot at getting the tree green again by reverting this. Apologies in advance if the tree turning red with this PR was merely coincidence.

Can you post a description or link for the failure?

Can you post a description or link for the failure?

from: https://ci.chromium.org/ui/p/flutter/builders/prod/Mac framework_tests_impeller/1904/overview: https://flutter-gold.skia.org/detail?grouping=name%3Dcupertino.cupertinoActionSheet.overall-light-theme%26source_type%3Dflutter&digest=5ae4de97c6977263147c6b390497b15b
You can find more on the build dashboard


How to convert object detection tflite to ambarella bin and anchor bin

I converted the YOLOv5.tflite file to the required Ambarella bin format for the CV25 architecture . I think I also need an anchors bin file for running the object detection application on the CV25. Can you suggest how I can generate these two files for object detection? Also, how can I visualize or test the bin file to see if it is able to perform object detection? I tried using AWS SageMaker to convert the file, but I am not sure how to run the file on an object detection app. Is there anything missing in the documentation, or can you provide some guidance on this?

HI @maazullah96 , thanks for your question on https://github.com/AxisCommunications/acap3-examples/tree/main/object-detection-cv25. We'll get back to you shortly.

Thanks, @pataxis and @Corallo  for the help.
Can you please add or update the documentation of the conversion of the object detection model to the ambarella format as well? because I tried the steps from tensorflow to lard app but my file is outputting only 0 or nan value . I think I am doing something wrong can you guide  me about the conversion process
I am using yolov5 medium file
The commands I am using are
`
First Step to activate The Environment
source /usr/local/amba-cv-tools-basic.<IP_ADDRESS>.2008.ubuntu-18.04/env/cv25.env
/usr/local/amba-cv-tools-basic.<IP_ADDRESS>.2008.ubuntu-18.04/cv2/tv2/exe/gen_image_list.py
-f images -o /home/maaz/Downloads/ambarella_new/img_list.txt -ns -e .jpg -c 0 -d 0,0 -r 256,256
-bf /home/maaz/Downloads/ambarella_new/dra_image_bin/
-bo /home/maaz/Downloads/ambarella_new/dra_image_bin/draw_bin_list.txt
/usr/local/amba-cv-tools-basic.<IP_ADDRESS>.2008.ubuntu-18.04/cv2/tv2/exe/graph_surgery.py tf -p /home/maaz/Downloads/ambarella_new/yolo5-custom-int8.tflite -o /home/maaz/Downloads/ambarella_new/yolo5-custom-int8_iq.pb -isrc 'i:serving_default_input_1|is:1,416,416,3' -t model/tf_upsample_1/resize/ResizeNearestNeighbor,model/tf_upsample/resize/ResizeNearestNeighbor -on "StatefulPartitionedCall"
/usr/local/amba-cv-tools-basic.<IP_ADDRESS>.2008.ubuntu-18.04/cv2/tv2/exe/tfparser.py -p "/home/maaz/Downloads/ambarella_new/yolo5-custom-int8_iq.pb" -o yolo5-custom-int8 -of ./yolo5-custom-int8 -d 4 -isrc 'i:serving_default_input_1|is:1,3,416,416'
vas -auto -show-progress /home/maaz/Downloads/ambarella_new/yolo5-custom-int8/yolo5-custom-int8.vas
/usr/local/amba-cv-tools-basic.<IP_ADDRESS>.2008.ubuntu-18.04/env/local/cavalry_gen/bin/cavalry_gen -d vas_output/ -f /home/maaz/Downloads/ambarella_new/yolo5-custom-int8.bin
`

Unfortunately, we can't provide detailed instructions on specific models.
It looks like you are running the gen_image_list using the wrong image size as an argument. You need to provide values to the -r that are equal to the input size of your model.
To get further support for the model conversion to cv25 I'd recommend you to contact directly Ambarella.


Uncaught Error: Invalid username

[Enter steps to reproduce below:]

...
...

Atom Version: 1.13.0
Electron Version: 1.3.13
System: Mac OS X 10.11.6
Thrown From: remote-sync package, v4.1.5
Stack Trace
Uncaught Error: Invalid username
At /Users/henriquevanklaveren/.atom/packages/remote-sync/node_modules/ssh2/lib/client.js:209

Error: Invalid username
    at Client.connect (/Users/henriquevanklaveren/.atom/packages/remote-sync/node_modules/ssh2/lib/client.js:209:11)
    at ScpTransport.module.exports.ScpTransport._getConnection (/Users/henriquevanklaveren/.atom/packages/remote-sync/lib/transports/ScpTransport.coffee:179:16)
    at ScpTransport.module.exports.ScpTransport.upload (/Users/henriquevanklaveren/.atom/packages/remote-sync/lib/transports/ScpTransport.coffee:54:6)
    at UploadListener.module.exports.UploadListener.processFile (/Users/henriquevanklaveren/.atom/packages/remote-sync/lib/UploadListener.coffee:48:17)
    at /Users/henriquevanklaveren/.atom/packages/remote-sync/node_modules/async/dist/async.js:4053:5
    at process (/Users/henriquevanklaveren/.atom/packages/remote-sync/node_modules/async/dist/async.js:2479:17)
    at Immediate.<anonymous> (/Users/henriquevanklaveren/.atom/packages/remote-sync/node_modules/async/dist/async.js:2292:16)
    at runCallback (timers.js:574:20)
    at tryOnImmediate (timers.js:554:5)
    at processImmediate [as _immediateCallback] (timers.js:533:5)

Commands
     -0:02.1.0 core:save (ol.tree-view.full-menu.list-tree.has-collapsable-children.focusable-panel)

Config
{
  "core": {
    "openEmptyEditorOnStart": false,
    "projectHome": "/Applications/MAMP/htdocs",
    "telemetryConsent": "limited",
    "themes": [
      "atom-dark-ui",
      "one-dark-syntax"
    ]
  }
}

Installed Packages
# User
atom-terminal, v0.8.0 (inactive)
Remote-FTP, v0.9.4 (active)
remote-sync, v4.1.5 (active)
atom-dark-syntax, v0.28.0 (inactive)
atom-dark-ui, v0.53.0 (active)
atom-light-syntax, v0.29.0 (inactive)
atom-light-ui, v0.46.0 (inactive)
base16-tomorrow-dark-theme, v1.4.0 (inactive)
base16-tomorrow-light-theme, v1.4.0 (inactive)
one-dark-ui, v1.8.2 (inactive)
one-light-ui, v1.8.2 (inactive)
one-dark-syntax, v1.6.0 (active)
one-light-syntax, v1.6.0 (inactive)
solarized-dark-syntax, v1.1.1 (inactive)
solarized-light-syntax, v1.1.1 (inactive)
about, v1.7.2 (active)
archive-view, v0.62.0 (active)
autocomplete-atom-api, v0.10.0 (active)
autocomplete-css, v0.14.1 (active)
autocomplete-html, v0.7.2 (active)
autocomplete-plus, v2.33.1 (active)
autocomplete-snippets, v1.11.0 (active)
autoflow, v0.29.0 (inactive)
autosave, v0.23.2 (active)
background-tips, v0.26.1 (active)
bookmarks, v0.43.2 (active)
bracket-matcher, v0.85.1 (active)
command-palette, v0.39.1 (inactive)
deprecation-cop, v0.55.1 (active)
dev-live-reload, v0.47.0 (active)
encoding-selector, v0.22.0 (active)
exception-reporting, v0.40.0 (active)
find-and-replace, v0.204.5 (inactive)
fuzzy-finder, v1.4.0 (active)
git-diff, v1.2.0 (active)
go-to-line, v0.31.2 (inactive)
grammar-selector, v0.48.2 (active)
image-view, v0.60.0 (active)
incompatible-packages, v0.26.1 (active)
keybinding-resolver, v0.35.0 (active)
line-ending-selector, v0.5.1 (active)
link, v0.31.2 (inactive)
markdown-preview, v0.159.1 (active)
metrics, v1.1.2 (active)
notifications, v0.65.1 (active)
open-on-github, v1.2.1 (inactive)
package-generator, v1.0.2 (inactive)
settings-view, v0.244.0 (active)
snippets, v1.0.4 (active)
spell-check, v0.68.5 (active)
status-bar, v1.6.0 (active)
styleguide, v0.48.0 (active)
symbols-view, v0.113.1 (inactive)
tabs, v0.103.1 (active)
timecop, v0.33.2 (active)
tree-view, v0.211.1 (active)
update-package-dependencies, v0.10.0 (active)
welcome, v0.35.1 (active)
whitespace, v0.35.0 (active)
wrap-guide, v0.39.0 (active)
language-c, v0.54.0 (active)
language-clojure, v0.22.1 (active)
language-coffee-script, v0.48.1 (active)
language-csharp, v0.13.0 (active)
language-css, v0.40.1 (active)
language-gfm, v0.88.0 (active)
language-git, v0.15.0 (active)
language-go, v0.43.0 (active)
language-html, v0.47.1 (active)
language-hyperlink, v0.16.1 (active)
language-java, v0.24.0 (active)
language-javascript, v0.122.0 (active)
language-json, v0.18.3 (active)
language-less, v0.29.6 (active)
language-make, v0.22.2 (active)
language-mustache, v0.13.0 (active)
language-objective-c, v0.15.1 (active)
language-perl, v0.37.0 (active)
language-php, v0.37.3 (active)
language-property-list, v0.8.0 (active)
language-python, v0.45.1 (active)
language-ruby, v0.70.2 (active)
language-ruby-on-rails, v0.25.1 (active)
language-sass, v0.57.0 (active)
language-shellscript, v0.23.0 (active)
language-source, v0.9.0 (active)
language-sql, v0.25.0 (active)
language-text, v0.7.1 (active)
language-todo, v0.29.1 (active)
language-toml, v0.18.1 (active)
language-xml, v0.34.12 (active)
language-yaml, v0.27.1 (active)

# Dev
No dev packages

Hi, if you still encounter this error in your console. Please check if you did enter "Username" in SCP/SFTP configuration dialog. I have seen this error too. In my case i forgot to enter "Username" :rofl:

have the same missing user name, i use ssh config too set username password so there is no need too enter anything else than host.


feat: add Snyk contributor agreements

[ ] Tests written and linted ℹ
[ ] Documentation written ℹ
[x] Commit history is tidy ℹ

What this does
Add in Contributor guidelines and agreement

ty fixing

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@lili2311 can we close/merge this please? :D


Bug when predicting with list-column

Goals :soccer:
Right now calling model.predict with a batch of data fails when the list-columns are not represented as ragged-tensors. This PR makes sure we use the ragged-tensor representation in model_test when reload_model=True

rerun tests


Fix gitter link for npmjs.com

Currently gitter image is broken on https://www.npmjs.com/package/co
Problem was unencoded space %20. Also unified format to match other badges.

Will require republish.

ff76c2a49b41f5303ada657c57a4692f318f5793


Visual Studio 2013 Community language service fails to work. (Install issue).

Highlight on Visual Studio 2013 Community don't works

We changed the installer for the 1.4 release to fix this, when that's released (soon), installing that should fix this issue.


Consider updating example data to a post-fire dataset

The current emerald point data isn't the best, primarily because the labels are pretty messy. They are only point measurements that are converted to circles based on the recorded radius.
The data from our post-fire surveys (soon to be released) has much higher quality polygon labels. I think it would be good to choose one or two sites from that as our example. The example constants would need to be updated, and likely the notebooks would need some tweaks.

We should move to using Valley data as the example. Also, there's example data for the bird detection task here that should be added.

Done in #152 except with data from the Chips site


Add circle.yml

This adds circle.yml with creation of dummy app as post dependency

not waiting any longer...


Test for marshalling Organizations and make JSON comparison non sensitive to key order

This pull request contains two items:

Modifies the JSON comparison utility for checking marshalling, making it non sensible to key order.This makes it easier to write tests for marshalling, since there is no need to worry about keeping the right order of the JSON keys in the wanted string.  It also removes a non working part of the test. I made sure old tests using this utility would still break if given the wrong input.
Adds a new test for marshalling organizations (issue #55 )

👌


Fixing performance issue related with querydsl spatial on hibernate.

As the representation of the operations were doing an equal true (boolean check), the DB engine is not able to use the spatial index, and instead of performing the intersects with the entities using the spatial index and comparing only the ones indicated by this one, was applying the intersects operation to all the entities.
How was discovered?
While migrating my application from native spatial queries to querydsl-spatial I found a big downgrade on the performance.  Analysing the differences between the native queries that I had and the ones generated by querydsl-spatial, I was able to indentify that queryDSL spatial was adding for most of the operations that I was interested on an = true clause. It is not needed and this comparison makes the db engine to not to use the spatial index on those queries.
it can be easily analysed by an EXPLAIN clause, that would show that using = true/false, the spatial index is not used, but without this clause, it is used, having exactly the same result in the queries.
In my case, the performance issue was of having queries executed in few milliseconds to more than 10 minutes in some cases

The problem is dat a function that returns a boolean cannot be used as predicate in JPQL. So the queries that this produces are semantically not correct JPQL. HQL is a bit more flexible, but this also varies between versions of Hibernate. So there is a potential compatibility issue here (and we will have to do some testing against various versions of Hibernate).

Hi @jwgmeligmeyling , but the current version of Hibernate in the project is 5.5.3.Final and from this version should be compatible, isn't it?


Clock Animation

Project title

Clock Animation using HTML,CSS, Javascript
Project Description

I wish to create an animated clock that's functional using html, css, javascript
Web stack

html,css, js
Screenshot(mandatory)

N/A (haven't started work yet)
Additional Context(mandatory)
Are you contributing under any open-source program ?

Codepeak

@aindree-2005 Thank u for raising this issue.
But we already have this project in our repo.


highlight the ladder to upper level in MLM

Is your feature request related to a problem? Please describe.
 Ladders are usually troublesome because I always want to click in the middle.
Describe the solution you'd like
I like how you highlight agility obstacles in green, maybe you could do the click box of the ladder in green? If it's too much of an issue, no worries.
Describe alternatives you've considered
No alternative, if it's too much of an issue don't worry about it
Additional context
This is the ladder I'm talking about

Duplicate of #9860


Fixing a sign vs unsigned comparison warning

Changes here address the following warning.
error: comparison between signed and unsigned integer expressions [-Werror=sign-compare]
|| (!cmdBuffer || bufCapacity < STD_RESPONSE_HEADER) )

I had to update manually due to merge conflict.  Thanks.


DCOS-35757: remove 2 seconds timeout

Everything appears to be working except our dashboard looks interesting :)

Testing
Connect to a i.e. soak 1.10 and switch network to Slow 3G. Without the fix UI won't be able to ever load state.json
Checklist

[x] Did you add a JIRA issue in a commit message or as part of the branch name?
[ ] Did you add new unit tests?
[ ] Did you add new integration tests?
[ ] If this is a regression, did you write a test to catch this in the future?

Closes DCOS-35757

This repo has @mesosphere-mergebot integration. You can interact with the following commands.
@mesosphere-mergebot integrate
@mesosphere-mergebot ship-it
@mesosphere-mergebot test

Alfred test this please :)


Please add support for Lenovo creator extreme

Before opening the issue, have you...?

[X] Searched for existing issues
[X] Read through the Monitor-Troubleshooting Wiki
[X] Updated MonitorControl to the latest version (if applicable)

Describe the issue
DDC not working on Lenovo creator extreme
Expected behavior
Control monitor with DDC
Anything else?
No response
Environment Information (please complete the following information)
- macOS version:
- Mac model:
- MonitorControl version:
- Monitor(s):
- Monitor Cable(s)/Connection(s):
- Apple Silicon/M1 (yes or no): yes

Hi @urmelchen2705
Please fill out the information about your environment so that we can help debug the issue more effectively.
Could you try using https://github.com/waydabber/m1ddc and see if if works in controlling your monitor ?

Also if you are using HDR please try it in SDR mode and if possible with a standard color mode set in the display. I am interested in this display as I was considering buying one so it would be great to know if it works or not. :)

Also, on Lenovo displays you can long press the Exit button (for 10 secs) to enable/disable DDC/CI so that might help. Please don't use HDMI to connect the display to the Mac as that probably won't work.

Hi
Ok I will try that later today. The monitor is connected over usb-c
Von meinem iPhone gesendet

Am 15.02.2022 um 09:30 schrieb Istvan Toth @.***>:

Also, on Lenovo displays you can long press the Exit button (for 10 secs) to enable/disable DDC/CI so that might help. Please don't use HDMI to connect the display to the Mac as that probably won't work.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you were mentioned.

DDC was on. No luck yet.
M1dcc give me:
@.*** m1ddc % ./m1ddc display list
1 - CreatorXtreme (30AEA662-0000-0000-081F-0104B53C2278)
@.*** m1ddc % ./m1ddc display 1 set luminance 50
I2C communication failure: (iokit/?) unknown subsystem error

Am 15.02.2022 um 09:31 schrieb Istvan Toth @.***>:
Also, on Lenovo displays you can long press the Exit button (for 10 secs) to enable/disable DDC/CI so that might help. Please don't use HDMI to connect the display to the Mac as that probably won't work.
—
Reply to this email directly, view it on GitHub https://github.com/MonitorControl/MonitorControl/issues/950#issuecomment-1039995472, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASKKL76QIWWLZMLFONNZNLTU3IFNHANCNFSM5ONU2HQQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.

Me and @urmelchen2705 have been talking over email. He has already tried Lunar and has the same issue.
The monitor blocks DDC for some reason.
I took a look at the monitor manual and user guide and these are the settings that need to be changed for brightness control to be allowed:

Disable Local Dimming
Disable HDR
Disable Dynamic Contrast
Set Color Mode to Custom
Set Scenario Modes to Panel Native

If those settings are already in that state, then there's nothing we can do to make it work.

All settings are in that state but nothing. I’ve tried two original usb-c cables too

Am 15.02.2022 um 18:35 schrieb Alin Panaitiu @.***>:
Me and @urmelchen2705 https://github.com/urmelchen2705 have been talking over email. He has already tried Lunar and has the same issue.
The monitor blocks DDC for some reason.
I took a look at the monitor manual and user guide and these are the settings that need to be changed for brightness control to be allowed:
Disable Local Dimming
Disable HDR
Disable Dynamic Contrast
Set Color Mode to Custom
Set Scenario Modes to Panel Native
If those settings are already in that state, then there's nothing we can do to make it work.
—
Reply to this email directly, view it on GitHub https://github.com/MonitorControl/MonitorControl/issues/950#issuecomment-1040570676, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASKKL75JLA4OXCFS44AZ3IDU3KFE5ANCNFSM5ONU2HQQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.

I took a look through the monitor database but you seem to be the only one using this monitor with Lunar so far. I have no data on whether the monitor should really support DDC or not. It's possible this is an incompatibility with the M1 DCP (Display Coprocessor) firmware, and hopefully it will be fixed in later updates.

Oh that's sad as this is a really great display (one that I was considering buying).
But: since this is a FALD/mini-led display, what happens if you use software dimming? If the mini-led control is implemented properly, it should have the same or even superior effect than brightness control via DDC, the hardware backlight should gracefully decrease in intensity while clarity should be retained (somewhat similar to what OLEDs do) so it actually might not make sense to use DDC brightness control anyway. What is your experience with this @urmelchen2705 ? Obviously volume control won't work with DDC being blocked.

Btw this display is rather rare, I think it is sold under this name in the EMEA region only, in other regions it is called Hermit Extreme). It seems to be the best 27" 4K mini-LED display in terms of price-to-value. Maybe the new Philips 27" 4Ks with 2304 mini-led zones will surpass it.

Quick Shade from Mac Appstore works great. I’m using this now.
Monitor Control or Lunar doesn’t because it kills the HDR effect

Am 16.02.2022 um 08:04 schrieb Istvan Toth @.***>:
Oh that's sad as this is a really great display (one that I was considering buying).
But: since this is a FALD/mini-led display, what happens if you use software dimming? If the mini-led control is implemented properly, it should have the same or even superior effect than brightness control via DDC, the hardware backlight should gracefully decrease in intensity while clarity should be retained (somewhat similar to what OLEDs do) so it actually might not make sense to use DDC brightness control anyway. What is your experience with this @urmelchen2705 https://github.com/urmelchen2705 ? Obviously volume control won't work with DDC being blocked.
—
Reply to this email directly, view it on GitHub https://github.com/MonitorControl/MonitorControl/issues/950#issuecomment-1041178088, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASKKL76JGHVHGVVXK2RTT4TU3ND6NANCNFSM5ONU2HQQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.

Yes the Phillips could be good too. But unavailable yet.
I got the Lenovo monitor for 999 Euro

Am 16.02.2022 um 08:06 schrieb Istvan Toth @.***>:
Btw this display is rather rare, I think it is sold under this name in the EMEA region only, in other regions it is called Hermit Extreme). It seems to be the best 27" 4K mini-LED display in terms of price-to-value. Maybe the new Philips 27" 4Ks with 2304 mini-led zones will surpass it.
—
Reply to this email directly, view it on GitHub https://github.com/MonitorControl/MonitorControl/issues/950#issuecomment-1041179353, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASKKL7ZTBPTP6REG6ZS4E43U3NEF3ANCNFSM5ONU2HQQ.
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.

Hi @urmelchen2705 - if you enable "Avoid gamma table manipulation" under Displays/Show advanced settings in MonitorControl, the app will use the same technique as QuickShade for dimming. I believe there might be a similar setting in Lunar as well somewhere.


Updated README.md

Corrected Grammatical errors in readme.md

@microsoft-github-policy-service agree


TIC Visualization for Aligned Peaks consumes all memory

Basic information

My operating system: Ubuntu 20.04.4, 1TB total disk space, 32 GB RAM, Java openjdk version "17.0.4" 2022-07-19

My MZmine version: 3.2.8

What happened
After performing the peak alignment for this study, I would like to inspect various alignments and other LC-MS peak properties. I right click on one of the shapes (particularly m/z = 114.0638 @ RT = 0.80), click show -> XIC (quick). Unfortunately, my entire system grinds to a halt as this appears to consume all of my memory, to the point that even the mouse barely budges. I never knew this to be a memory-consuming operations in previous MZMine versions, so I'm wondering if there's a solution or something I'm missing here.
I should mention that I tinkered with the MZMine.cfg file to change the RAM percentages to:
java-options=-XX:InitialRAMPercentage=50 (initially 30)
java-options=-XX:MinRAMPercentage=30 (initially 50 or 80??)
java-options=-XX:MaxRAMPercentage=90 (initially 80)
Batch1_issue.zip

I think your memory setting should be fine... Although its good to stick to the defaults. There is always an overhead that is above the 80% max.
It seems weird that this would freeze your computer as it can visualize in the feature table... You do not seem to have too many files either. Did you try double click on a file and then visualize in the raw data overview? You can check the box and visualize in more files at once


GoToSiblingCommand

Please select the area your bug applies to. (Multiple selections are Possible. You can leave blank if you're not sure.)

[x] Workspace.  VSCode workspace, vaults, Intellisense/autocomplete, Dendron settings
[ ] Lookup.  Dendron's Lookup Command
[ ] Views.  Dendron Preview, Tree View, Side Panels in the UI
[ ] Schema.  Dendron Schemas
[ ] Pod.  Data import from / export to Dendron
[ ] Publish.  External Site Publish
[ ] Markdown.  Markdown features, such as syntax support and features

Describe the bug
When I tried go to sibling from command palette, I got the following error.
GoToSiblingCommand: You found a bug! We didn't think this could happen but you proved us wrong. Please file the bug here -->  https://github.com/dendronhq/dendron/issues/new?assignees=&labels=&template=bug_report.md&title= We will put our best bug exterminators on this right away!
To Reproduce
Steps to reproduce the behavior:

Import pod -> markdown (import markdown files with folder hierarchy)
Try sibling navigation

Expected behavior
Sibling navigation should work.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information)

OS: [e.g. iOS] MacOS Monterey
Browser (if with published websites; include version): [e.g. chrome, safari]
Versions (all that apply to bug):

Dendron Extension:
VS Code version:
Dendron CLI:

Additional context
Add any other context about the problem here.
Dendron Log file
Please attach the output of > Dev:Dendron: Open Logs here

Thanks @akhiln28 for the report - would you mind also including the output of the Dendron Logs in the bug?
 Dev:Dendron: Open Logs > paste output.

After I got the error I deleted the files imported using import pod. Again I tried reproducing the bug by importing the using import pod, but this time I am getting this message "One is the loneliest number. This node has no siblings :(" even though the current has a sibling. Please find the logs.
dendron.log

Thanks for the extra info @akhiln28, the logs are helpful.  I'll duplicate this issue to this one: https://github.com/dendronhq/dendron/issues/1907


GISAID covCLI bugfixes & BioSample/SRA modifications

Edit: added some BioSample/SRA workflow changes and attached my config.yaml and metadata files in case you wanted to test against them.
example_config.yaml.txt
example_metadata.csv
Hey Dakota! Thanks for getting this new release out. The new handling for BioSample packages is amazing. I hugely appreciate how much this project simplifies metadata validation across multiple pathogens/packages/repositories and how convenient it makes large volume submissions.
I've tested the BioSample/SRA, and GISAID covCLI workflows - the NCBI workflows worked perfectly, but I ran into a bunch of submission failures testing covCLI.
I made some modifications and now my GISAID submissions are going through reliably. I haven't had time to do any serious testing so I can't say if all these changes will hold up, but I wanted to go ahead and submit a pull request in case there's anything that might be helpful.
The former description of this pull request is a little out of date now. I've been testing GISAID covCLI, SRA, and BioSample heavily, using the SARS-CoV-2 and OneHealth Enteric BioSample packages. Below are changes addressing workflow errors/submission failures I encountered during testing. I want to revisit a few of the changes I made, but hopefully some of them are useful!
⚙ General

Remove code blocking prod submissions
Make fasta file an optional input

🛠 covCLI updates/bugfixes

Modify several interactions w/the metadata sheet column headers
Adjust logfile parsing to properly capture the sample name and EPI ID from the submission log
Address issues causing some functions to exit prematurely when passed empty inputs (when only GISAID isolates or GISAID segments are present)
Prevent crashing when submission includes samples already registered in GISAID - warn the user & log virus name and EPI ID
Edit: this is working as far as preventing crashes, but isn't reliably logging the EPI ID of the repeated samples

📋 BioSample & SRA updates/bugfixes

Drop empty bs- & sra- columns before metadata validation. Pandera will ignore optional columns if they don't exist - if they exist but have no data pandera will attempt to validate them and the workflow will fail. If a mandatory column has been left empty by the user and is removed by this change, pandera will still catch it.
If bs-description is absent, create it by joining values from organism, bs-host, bs-host_disease. bs-description isn't in the Submission Wizard template and is not required by NCBI for submission, but the workflow will fail when it isn't present.
Edit: I want to revisit this, because it doesn't seem like missing bs-description causes a crash w/every BioSample package, and also this is kind of a bandaid anyway.
Warn the user if performing BioSample and SRA submissions together with Link_Sample_Between_NCBI_Databases disabled. SRA submission is likely to fail in this situation unless the user has added BioSample accessions manually beforehand.
Prevent workflow from failing if bs-description is missing when user is not submitting to BioSample.
When a biosample/sra column has mixture of data & blank rows, don't write the blank attributes to submission.xml. This causes the affected sample to fail, & there are a couple of valid reasons to have mixed columns:

submitting multiple pathogens under the same biosample template w/different optional fields completed
submitting mix of paired and single end reads to SRA

Testing data was generated via:
python seqsender.py test_data --biosample --sra --gisaid --organism COV --submission_dir test_data/CCPHL/

Metadata and config templates were created with the Shiny app Submission Wizard
And the workflow was run with this command:
python seqsender.py submit --biosample --sra --gisaid --organism COV --submission_dir test_data/CCPHL/ --submission_name COV_TEST_DATA --config_file test_data/CCPHL/cov_ccphl_config.yaml --metadata_file test_data/CCPHL/meta2.csv --fasta_file test_data/CCPHL/sequence.fasta --test

Hey @erikwolfsohn,
Thanks for all the changes you've contributed! I've incorporated them into the updates I was already working on for the v1.2.1 update and have also expanded upon some of the additions you made as well.
I expanded the try/catch for file permission errors to cover all files being generated by the file_handler.py script. I really liked your changes for GISAID but I made a couple of modifications to eliminate the database prefix issues and changed how the logging occurs as I noticed there could be an error where the incorrect sample name might be used. The bs-description field should be resolved as I also changed how the config file works for the description title and comment. I've split and renamed the "bs-description" field into "bs-sample_title" and "bs-sample_description" with updated documentation in the templates so that should provide a better explanation of those fields. I also provided some additional info in the shiny issue you had created as well.
Thanks, again,
-Dakota


Won't be able to enter subsequent session after ending the first session

Don't know how workshop works. So not sure if this is an issue. After ending the very first session, the namespace for the subsequent session won't be created if we want to start a new session.

It takes some time if a session has not already been pre-provisioned.


Enhancement/Update Composer Dependencies

This PR

[x] jumps to the latest stable dependencies versions
ZF2 v2.5
scn-social-auth v1.18.1
htmlpurifier v4.7.0
zfc-user v1.3.3
[x] fixes followed errors due to major dependencies upgrades
[x] adds UserController test case
[x] replace the composer meta package zendframework/zendframework with the separated zend packages (generally replace - nothing sorted out)
[x] increased required php version to ``5.6`
[x] adds the Roave SecurityAdvisories package
[x] update the composer.lock file

fixes #507
/cc @Ocramius @localheinz

no clue why scrutinizerhates me :sob:

@localheinz or @Ocramius could you please have a look :smiley:

@ins0 edpgithub 0.4.0 is ready :)

thanks for the info @gianarb i will update this :+1:

@ins0 any changes needed? I assume we don't need to alias the requirements anymore..

@Ocramius unfortunately the packagist repo isn't updated, so @gianarb could you do this too or did we need to ask @EvanDotPro to do this please?

It's up to @Hounddog

thanks @Hounddog
ping @Ocramius
don't know why travis not showing a green build, but its run green like the latest runs too. :8ball:

@ins0 had this issue with travis also with other builds, I think it's not on our side atm.

Thanks for your effort on this, @ins0!

thanks @Ocramius


Changing deprecated ambientDependencies to globalDependencies

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug Fix

What is the current behavior? (You can also link to an open issue here)
Typings install has no affect!

What is the new behavior (if this is a feature change)?
Typings install will do its job! :)

Other information:

Using "typings install" has no function because ambientDependencies is deprecated.
With globalDependencies, typings install does its job again! :-)

Many thanks @smith64fx !


Integration test for auto reload on config change

To make sure the auto reload feature don't break anymore in the future, we need to have an integration test for this.

is this issue still valid? as we've moved to cypress?

Including this in issue #526


Invalid link for creating a custom dataset

Thanks so much for making this library available! I was trying to figure out how to create a custom dataset and was looking through the documentation. On the dataset preparation page (https://mmdetection3d.readthedocs.io/en/latest/data_preparation.html), there is a link to a document about using a custom dataset:
Customized Datasets
For using custom datasets, please refer to Tutorials 2: Customize Datasets.

But the link to "Tutorials 2: Customize Datasets" is invalid.

I believe the correct link should be https://mmdetection3d.readthedocs.io/en/latest/tutorials/customize_dataset.html

I believe the correct link should be https://mmdetection3d.readthedocs.io/en/latest/tutorials/customize_dataset.html

Thanks for your reminding. I will fix it and other links with a PR.

Thanks for your reminding. I will fix it and other links with a PR.


Test non x86-64 targets before 1.0.0 release

Currently, all CI tests are x86_64. We should have a policy and testing for other platforms, such as ARM, or non-64 bit x86 targets.

It's been a while since this was opened; @jamesmunns is this something you can / would like to pick up?

I believe github actions don't support non-x86-64 targets. What do we do here? Can we close the issue and reconsider later?

I'd like to use cross; see this change in #286


Add debug mode

Added a flag to allow for rendering wireframes produced from the plank.js fixtures.

This looks great! We could get a little creative with this and mark each body with some userdata that specifies what kind of class a body represents (e.g. basic shape, robot part) and maybe add in filters for the kind of things we want highlighted

i think we can get around the performance and GC issues this has by combining all debug data into one 'THEE.Geometry' this will reduce the GC overhead and still be enough for smooth playback

I had a fight with git and in my tired state I let it win, I’ll un-bork this pr tomorrow.

I know the feeling :P BTW, the body dimensions in the pyramid should be new Box(spec.dimensions.x / 2, spec.dimensions.z / 2)

Thanks, might end up separating it into another pr

closed and replaced with #88


After new update ServerRequestInterface returning incorrect object

request model become work wrong
public function view(ServerRequestInterface $request): ResponseInterface {
        $response = $this->responseFactory->createResponse();

        $id = (int)$request->getAttribute('id');
        // Here error. Function return null, but before returned value.
        // Method GET.

I see you stop using yiisoft/yii-web and change on yiisoft/yii-http, but it requires PHP 8.0

Found how to avoid ServerRequestInterface $request->getAttribute(). Using CurrentRouteInterface $currentRoute->getArgument('id') it responding value, for this moment.

Yes route arguments have been moved to CurrentRouteInterface.

but, then remove method getArguments from ServerRequestInterface

You mean getAttributes()? This is PSR and we cannot modify it. The meaning of it is not to get router's parameters but to pass data from one middleware to another in a middleware stack.

Understood, this buffer to transfer data via middleware into action.
It is good idea to divide router and request data.
Thanks for answer =)


Feature request: Improve USB speed on OUT transfers (host -> RP2040 device)

I'm developing an application that relies on achieving high transfer rates between a host and the RP2040 working as a USB device. I noticed that OUT transfers (host -> RP2040) are surprisingly slow, significantly slower than IN transfers (RP2040 -> host).
Decoding the traffic on the USB bus reveals the reason:

The RP2040 initially NAKs all packets except the first in a frame, forcing the host to retransmit them. This can be seen in the screenshot: two DATA1 packets (the second one is the retransmission), two DATA0 packets (again the second one is the retransmission), etc. This effectively halves the achievable bus bandwidth in this direction. I assume it happens because the RP2040 cannot empty the buffer sufficiently fast before the next packet.
I think - but don't know how to prove it - that this could be solved by using double buffering in the USB controller and by then servicing the buffers in a "ping pong" manner. I can see that double buffering, albeit supported by hardware, is specifically disabled for OUT transfers in the USB stack:
https://github.com/hathach/tinyusb/blob/4bfab30c02279a0530e1a56f4a7c539f2d35a293/src/portable/raspberrypi/rp2040/rp2040_usb.c#L149-L152
The following comment seems to indicate that this was done because the TinyUSB maintainer encountered some issues:
https://github.com/hathach/tinyusb/blob/4bfab30c02279a0530e1a56f4a7c539f2d35a293/src/portable/raspberrypi/rp2040/rp2040_usb.c#L260-L264
Perhaps with some help from the Raspberry Pi developers this could be solved, bringing a significant USB speed increase.

fyi - Bulk IN packes are slow/hangs as well, with certain hosts and CDC.  More info here:
https://github.com/hathach/tinyusb/issues/1572
You might want to re-test with more hosts, if you have not already?

ping @liamfraser

I've created a minimal example to demonstrate this: https://github.com/czietz/pico-usb-speed-check
It reads and discards all data it receives from the host and produces data for the host as fast as possible.
The included speedcheck.py script measures the transfer rate. The actual numbers depend on the host, but for example on an RPi 400 I get:
Host -> Device: 575.25 kBytes/s
Device -> Host: 883.36 kBytes/s

This is not a factor 2 due to overhead that applies to both transfer directions. But still it shows the issue very clearly.

Thanks for this example. I agree the discrepancy is because double buffering is disabled for Host -> Device (out from host). I won't be able to do it immediately but can spend some time profiling tinyusb to work out where the time is lost. If you want to do this yourself, a method we find really helpful is to set a gpio high on each function you want to profile and then set it low when you exit the function. We then attach a Saleae logic analyser and can see where the time is spent. Setting and clearing a gpio is one write so doesn't add much overhead.

as mentioned in the comment of the code, I encountered some issue with double buffered in out endpoints. It is only a technical issues and fixable, but I don't have enough time and need to wrap that up in order to move on with other works. I may revise this later on, when having time, but any PRs are welcome.

closing as a TinyUSB issue


Unwrapping (~) not supported in CDDL

CDDL RFC 8610 section 3.7.  Unwrapping defines the use of the tilde (~) character operator for unwrapping a map.  When zcbor encounters a tilda in the CDDL it throws an exception.
import zcbor
cddl_str = """
second_type = {
~ first_type,
param3: uint,
}
first_type = {
param1: tstr,
param2: uint
}
"""
cddl_res = zcbor.zcbor.zcbor.DataTranslator.from_cddl(cddl_str, 100)
yields:
Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/zcbor/zcbor/zcbor.py", line 903, in get_value
handler(self, match_str)
File "/usr/local/lib/python3.8/dist-packages/zcbor/zcbor/zcbor.py", line 775, in
lambda m_self, map_str: m_self.type_and_value(
File "/usr/local/lib/python3.8/dist-packages/zcbor/zcbor/zcbor.py", line 530, in type_and_value
self.set_value(value_generator)
File "/usr/local/lib/python3.8/dist-packages/zcbor/zcbor/zcbor.py", line 533, in set_value
value = value_generator()
File "/usr/local/lib/python3.8/dist-packages/zcbor/zcbor/zcbor.py", line 776, in
"MAP", lambda: m_self.parse(map_str))),
File "/usr/local/lib/python3.8/dist-packages/zcbor/zcbor/zcbor.py", line 990, in parse
instr = value.get_value(instr)
File "/usr/local/lib/python3.8/dist-packages/zcbor/zcbor/zcbor.py", line 914, in get_value
raise TypeError("Could not parse this: '%s'" % instr)
TypeError: Could not parse this: '~ first_type,     param3: uint,'
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/lib/python3.8/dist-packages/zcbor/zcbor/zcbor.py", line 281, in from_cddl
parsed.get_value(cddl_string.replace("\n", " ").lstrip("&"))
File "/usr/local/lib/python3.8/dist-packages/zcbor/zcbor/zcbor.py", line 905, in get_value
raise Exception("Failed while parsing this: '%s'" % match_str) from e
Exception: Failed while parsing this: '     ~ first_type,     param3: uint, '

Thanks for reporting. Unwrapping is one of the features mentioned as unsupported in the release notes. I will note this down as a request so I'm more likely to implement it.


Support adding/overwriting request headers before forwarding request

It would be useful to support addition of "request" headers on per-route or per-virtual host basis for use cases like forwarding a request to auth backends, etc.
( @mattklein123  please assign this to me).

Is this for proxy-to-proxy communication? In Istio, we need to insert pod identity into the source request to enforce source-destination policies on the server side. We've been using a custom filter to do that, but since values are not dynamic, native Envoy support would be great.

Please reconcile with "global" response headers to add/remove here: https://lyft.github.io/envoy/docs/configuration/http_conn_man/route_config/route_config.html
We might want to move this into both virtual host and route level, etc. Needs some thinking. Please propose configuration schema.

I was thinking more from the standard LDAP/IAM auth stuff. Request comes in, you add a bunch of headers to it, forward to IAM, get authenticated, and then you strip them off and redirect to original destination. But, the istio case applies equally well here.

fixed by https://github.com/lyft/envoy/pull/630


Issue: Self hosted can't find the API

Issue you'd like to raise.
Hi everyone,
I trying to self host langsmith, I installed the package version 0.0.69, and then ran
langsmith start
It's running in a VM in azure cloud, I opened all the ports just to be sure there is no error there. also, there is no active firewall
Docker looks like this

At the moment of opening it can't find the api

any idea how can i continue?
Suggestion:
No response

Hi @mrcmoresi - Self-hosting LangSmith needs a license key. In order to get one, you need to have an annual, enterprise contract. If you're interested in learning more you can reach out to<EMAIL_ADDRESS>


Are both Devicemapper & OverlayFS supported for Docker?

I'm trying to figure out if we should go with Devicemapper or OverlayFS for our CentOS 7.4 (Kernel  3.10.0-693+) systems. However, the Storage Driver documentation has some contradictory statements.
https://docs.docker.com/storage/storagedriver/device-mapper-driver/ says the following:

devicemapper storage driver is the only supported storage driver for Docker EE and Commercially Supported Docker Engine (CS-Engine) on RHEL, CentOS, and Oracle Linux. See the Product compatibility matrix.

And clearly, the Product compatibility matrix says Devicemapper is supported.
However, this contradicts what I read in https://docs.docker.com/storage/storagedriver/overlayfs-driver/#prerequisites , which makes it sound like OverlayFS is also supported.

OverlayFS is supported if you meet the following prerequisites:

The overlay2 driver is supported for Docker EE and recommended for Docker CE.

But the wording is a little ambiguous, but I read this as "OverlayFS is now supported".
Could you either:

Update the docs to clarify that both Devicemapper & OverlayFS are supported
Remove the ambiguous wording to clarify that OverlayFS is not yet supported, perhaps with something like this:

OverlayFS will be supported at a future date when the following prerequisites are met:

When the overlay2 driver is officially supported by Docker EE and when it's supported by Docker CE.

File: storage/storagedriver/device-mapper-driver.md, CC @gbarr01

This issue relates/overlaps with #6015.
@stefanlasiewski based a comment on that issue, we recommend Overlay2 for CentOS.
Ping @dmp42 for visibility.

Thanks for the tip. Sounds like the documentation for Devicemapper is a little out of date.
I fixed a typo: I'm actually using Docker CE (not EE).

Closing this ticket due to its age, and the impending refactor. If you think this is in error, feel free to reopen. Thanks!


[Fix #157] Add new Minitest/EmptyLineBeforeAssertionMethods cop

Fixes #157.
This PR adds new Minitest/EmptyLineBeforeAssertionMethods cop.
This cop enforces empty line before assertion method.
# bad
do_something
assert_equal(expected, actual)

# good
do_something

assert_equal(expected, actual)

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[x] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[x] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

@koic Awesome! 🥇


Merged PR #190

Noticed just by chance in this PR https://github.com/graphite-project/carbon/pull/315/files#diff-db27808e2f8d53b9406df573ce15b714L413
Original commit message was 119 (https://github.com/graphite-project/carbon/commit/3bd7355b0c07fe94cf7b0728c129b378d838ed7a)
This should fix something, as the code logic seems odd, but haven't checked.

I think you're right but we really should test this to ensure we're not regressing a partial fix in https://github.com/graphite-project/carbon/pull/300. I'll try to take a closer look and run some tests this weekend.

I hope I remember this right but I believe what happened with this was that
I didn't see it at the time and manually went through looking for  commits
to 0.9.x missing in master and applied them, breaking the mergability of
this
I talked to jssrjr at the time (at Monitorama 2015) and apologized and I
think we agreed to drop it.
FWIW (with me not being active any longer) my opinion is that the branches
are so far diverged that this would A) not be worth the effort (it's
literally easier to diff the files in each checkout and verify the
differences are expected) and B) would create a huge mess in the commit
history.
In any case I doubt this PR is usable as-is, you probably need to start
fresh if you really want to do a merge.
Finally, If something like this is done it should be squash-merged in. The
commit hygiene in the graphite repos is already terrible (due to GitHub's
default merge strategy and our lack of commit standards for committers) and
inserting so many commits into the history with all of the merge-commits
necessary will make it  far worse.
On Jul 8, 2016 10:03 PM, "Jason Dixon"<EMAIL_ADDRESS>wrote:

I think you're right but we really should test this to ensure we're not
regressing a partial fix in #300
https://github.com/graphite-project/carbon/pull/300. I'll try to take a
closer look and run some tests this weekend.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/carbon/pull/509#issuecomment-231511317,
or mute the thread
https://github.com/notifications/unsubscribe/AATaL_jnJnYcoj90a2-X7DfZLPNLP1bLks5qTw-LgaJpZM4G42yw
.

Ah damn, I completely misinterpreted this as a few to merge that old pr :(
Carry on...
On Jul 9, 2016 8:28 AM, "Michael Leinartas"<EMAIL_ADDRESS>wrote:

I hope I remember this right but I believe what happened with this was
that I didn't see it at the time and manually went through looking for
commits to 0.9.x missing in master and applied them, breaking the
mergability of this
I talked to jssrjr at the time (at Monitorama 2015) and apologized and I
think we agreed to drop it.
FWIW (with me not being active any longer) my opinion is that the branches
are so far diverged that this would A) not be worth the effort (it's
literally easier to diff the files in each checkout and verify the
differences are expected) and B) would create a huge mess in the commit
history.
In any case I doubt this PR is usable as-is, you probably need to start
fresh if you really want to do a merge.
Finally, If something like this is done it should be squash-merged in. The
commit hygiene in the graphite repos is already terrible (due to GitHub's
default merge strategy and our lack of commit standards for committers) and
inserting so many commits into the history with all of the merge-commits
necessary will make it  far worse.
On Jul 8, 2016 10:03 PM, "Jason Dixon"<EMAIL_ADDRESS>wrote:

I think you're right but we really should test this to ensure we're
not regressing a partial fix in #300
https://github.com/graphite-project/carbon/pull/300. I'll try to take
a closer look and run some tests this weekend.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/graphite-project/carbon/pull/509#issuecomment-231511317,
or mute the thread
https://github.com/notifications/unsubscribe/AATaL_jnJnYcoj90a2-X7DfZLPNLP1bLks5qTw-LgaJpZM4G42yw
.

Confirmed this was also proposed as part of #315.


depManagement from parent should be used with processDependencyManagementTransitive=false

When we set processDependencyManagementTransitive=false dependencyManagement from parent should be still used.
eg. We have a IT - it-dependency-updates-aggregate-report-issue-333 which will fail with processDependencyManagementTransitive=false
According to documentation:
Whether to process the dependencyManagement part transitive or not.
In case of <type>pom</type>and <scope>import</scope> ...

I understood that only items imported by pom are skipped ... not everything from parent pom.
First we need agree what this options means and next check if implementation meet requirements.

The documentation is wrong.
If I didn't take the documentation of the parameter into account, it would look OK to me:
The dependencyManagement item missing from the aggregate report with processDependencyManagementTransitive=false is dummy-lib:2.0.0, which is a transitive dependencyManagement item from the parent of pom.xml -- see https://github.com/mojohaus/versions/blob/1d039561071cd3dffb7d9b98d689eee25cf6fd99/versions-maven-plugin/src/it/it-dependency-updates-aggregate-report-issue-333/pom.xml#L7
When debugging, I see that the functional difference is that with processDependencyManagementTransitive=false, we're taking dependency management items from the original model whereas with the parameter set to true, from the interpolated model. The latter will contain all transitive dependencies, not just with scope pom or import.
I don't see any reflection of the original documentation in the plugin code. I suggest that we change the docs to read that the option disables reporting on transitive dependency management, ie taken from parent or dependencies with scope import.


add random id for errors so that users can report identifier to us

maybe hash of error stack or some identifier that doesnt inform about the issue.

then administrators could just look in the logs for the specific id to find more info idk


Update wrap files to abseil-cpp 20200923-2

The older version didn't have the [provide] section either, and the split in multiple libraries is rather arbitrary (I don't think these are intended to be used as a shared libraries at all) thus I elected not to add one originally. I added it now.

The older version didn't have the [provide] section either, and the split in multiple libraries is rather arbitrary (I don't think these are intended to be used as a shared libraries at all) thus I elected not to add one originally. I added it now.

Ping?

Ping?


Update staging

Description

Checklist:

[ ] Automated checks are passing locally.
[ ] CHANGELOG updated if change is worth telling users about.

General testing

[ ] Test without javascript
[ ] Test on small screen

Accessibility testing

[ ] Works keyboard only
[ ] Tested with one screen reader
[ ] Zoom page to 400% - content still visible
[ ] Disable css - does content make sense and appear in a logical order?
[ ] Passes automated checker (automated in build or manual)

@baphled loads of conflicts, unfortunately. 😞

Maybe we should force-push master to staging?


Synthetic deinitializer implementation fails on unconstrained generic types

This program should compile:
trait P { fun bar() }

type A<T>: Deinitializable {
  var x: T
  public memberwise init
}

type B: P, Deinitializable {
  public memberwise init
  public fun bar() {}
}

conformance A: P where T: P {
  fun bar() { x.bar() }
}

public fun main() {
  let a = A<B>(x: B())
  a.bar()
}

But the following error is reported during IR analysis:
:1.1-19: error: type 'T' does not conform to trait 'Deinitializable'
/* module: test */
~~~~~~~~~~~~~~~~~~

The problem is that the IR is trying to synthesize A.deinitialize, but T is not deinitializable.

Fixed by #1264


fix(k8smeta): handle missing directories/files during /proc scan

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area plugins

/area registry

/area build

/area documentation

What this PR does / why we need it:
std::filesystem::directory_iterator works by retrieving entries on the fly as it iterates over them,
rather than preloading all entries. This implies that entries could indeed disappear (or appear)
between iterations, especially in highly dynamic directories such as /proc/.
The loop continues processing other entries even if an exception occurs,
allowing for robust and uninterrupted iteration.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:

LGTM label has been added.  Git tree hash: 0e21d6361500972a123577e6c437e1958049d968

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: alacuku, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Move extra methods from actor states

Issue summary
Actor state files must remain as close to their source as possible. They should not be extended by additional methods directly like in https://github.com/ChainSafe/fil-actor-states/pull/290. All such occurrences should be moved to, e.g., Forest shim or extension traits.
This is should lower the upgrade burden (less manual copy-pasting from our own definitions - only from the builtin-actors) and manage our expectations for the given methods (builtin-actors code is the holy grail and we should assume it's correct, otherwise it's a massive issue for Filecoin networks).
Other information and links

@sudo-shashank Could you please identify which methods are "our own" and should be migrated elsewhere?

@sudo-shashank Could you please identify which methods are "our own" and should be migrated elsewhere?

okay sure


Support Node.js 18

Package Name
create-plugin
What happened?
Currently the plugin generated does not support Node.js 18
yarn install
yarn install v1.22.19
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
[3/5] 🚚  Fetching packages...
warning<EMAIL_ADDRESS>The engine "browsers" appears to be invalid.
error<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version "^12 || ^14 || ^16 || ^17". Got "18.12.1"
error Found incompatible module.
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

What you expected to happen
It would be great to support Node.js 18 as today Node.js 18 is LTS version now.
https://nodejs.org/en/
How to reproduce it (as minimally and precisely as possible)
nvm use 18
yarn install

Environment
npx envinfo --system --binaries --browsers --npmPackages="@grafana/*"

  System:
    OS: macOS 13.0.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 15.11 GB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 107.0.5304.110
    Firefox: 106.0.5
    Safari: 16.1
  npmPackages:
    @grafana/data: 9.1.2 => 9.1.2
    @grafana/e2e: 9.1.2 => 9.1.2
    @grafana/e2e-selectors: 9.1.2 => 9.1.2
    @grafana/eslint-config: ^2.5.0 => 2.5.2
    @grafana/runtime: 9.1.2 => 9.1.2
    @grafana/tsconfig: ^1.2.0-rc1 => 1.2.0-rc1
    @grafana/ui: 9.1.2 => 9.1.2

Additional context
No response

Add more info.
Here is another result using npm instead of yarn with all dependencies upgrading to latest working versions.
To reproduce, you can clone this repo folder grafana/hm-panel-plugin at
https://github.com/Hongbo-Miao/hongbomiao.com/tree/main/grafana/hm-panel-plugin
npm install
npm ERR! code EBADENGINE
npm ERR! engine Unsupported engine
npm ERR! engine Not compatible with your version of node/npm<EMAIL_ADDRESS>npm ERR! notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>npm ERR! notsup Required: {"node":"^12 || ^14 || ^16 || ^17"}
npm ERR! notsup Actual:   {"npm":"8.19.2","node":"v18.12.1"}

npm ERR!      /Users/hongbo-miao/.npm/_logs/2022-11-11T08_31_28_716Z-debug-0.log

Environment:
npx envinfo --system --binaries --browsers --npmPackages="@grafana/*"

  System:
    OS: macOS 13.0.1
    CPU: (10) arm64 Apple M1 Max
    Memory: 14.84 GB / 64.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Brave Browser: <IP_ADDRESS>
    Chrome: 107.0.5304.110
    Firefox: 106.0.5
    Safari: 16.1
  npmPackages:
    @grafana/data: 9.2.4 => 9.2.4
    @grafana/e2e: 9.2.4 => 9.2.4
    @grafana/e2e-selectors: 9.2.4 => 9.2.4
    @grafana/eslint-config: 5.0.0 => 5.0.0
    @grafana/runtime: 9.2.4 => 9.2.4
    @grafana/tsconfig: 1.2.0-rc1 => 1.2.0-rc1
    @grafana/ui: 9.2.4 => 9.2.4


Allow string as value for queries on a Date in MongoDB

Is your feature request related to a problem? Please describe.
Currently when doing a repository.find({ startTime: { $gt: '2020-11-07T10:00:00.000Z' } }) the data will be passed as is to MongoDB instead of converting the value to ISODate().
MongoDB will return no results, as it doesn't recognise the value is a date when using just a string.
Describe the solution you'd like
I'd like to be able to pass a string value to query an entity with a Date as type (also supporting $gt(e)/$lt(e).
@Property()
startTime: Date;

repository.find({ startTime: { $gt: '2020-11-07T10:00:00.000Z' } }) // Not working => .find({ startTime: { $gt: '2020-11-07T10:00:00.000Z' } })
repository.find({ startTime: { $gt: new Date() } }) // Working => .find({ startTime: { $gt: ISODate('2020-11-07T10:00:00.000Z') } })

Maybe we can do a check internally if the string passed matches a ISOTime-String (possibly regex or using the Date constructor?) and if it matches convert it to an ISODate
... or we could have an extra option in the @Property() options?

Describe alternatives you've considered
I tried to create a Custom Type, but Custom Types can't be used for queries.
Additional context
I found the line where the Date.prototype is patched but couldn't find a way on how to make it support the string syntax.
The Types for FilterQuery already seem to support the string syntax, so that part should be fine.
https://github.com/mikro-orm/mikro-orm/blob/4668e78d1c900d1718625364b603dda1b707dd82/packages/mongodb/src/MongoConnection.ts#L276
Thanks a lot for making this library! I hope this is a good addition that benefits the people using MongoDB.

I don't really like that idea, the property type is Date so should be the parameter type. Custom type is the way to go if you want to support this automatically, but I'd say use Date object instead (so just wrap it to new Date('2020-11-07T10:00:00.000Z') on the call site).

I tried to create a Custom Type, but Custom Types can't be used for queries.

What makes you think so? Current version do support mapping of custom types from query parameters. This test demonstrates it, all PKs are using custom types and we query by the runtime value on line 92:
https://github.com/mikro-orm/mikro-orm/blob/master/tests/issues/GH446.test.ts
Also just tried to change that line to use operators, and it works as expected.

I found the line where the Date.prototype is patched but couldn't find a way on how to make it support the string syntax.

There is no such thing as ISODate, that is only about logging a date in mongo query. It is there mainly so users can clearly see what is wrong - as string date is not a Date object. The object is a regular Date, nothing special.

Wow, thanks a lot for the quick answer! Looks like I was wrong. Custom Types are a perfect fit for this use-case, I just didn't set it up correctly. Simply parsing the string to a Date and returning that Date in the Custom Type covertToDatabaseValue does the trick. Thanks a lot for the guidance and detailed answer! Closing the issue, as it's resolved now.


Exception handling

Exception handling in Parsl should support the following cases:

Exceptions raised or exit codes returned
File outputs specified but missing
Input futures failed
Walltime exceeded
[Later] Data staging failed

We should also support this same set for both Bash and Python apps.
Unknowns:

Where in the code should an exception be raised/handled for asynchronous apps.
Retries and retry condition checks.

The following are fixed in branch error_handling and merged to master.

[X] Exceptions raised or exit codes returned
[X] File outputs specified but missing
[X] Input futures failed
[ ] Walltime exceeded - We don't currently check for walltimes.
[ ] [Later] Data staging failed - We don't have data staging yet.

I'm closing this issue, since most of the original requirements are covered except for items that are blocked on future milestone features such as file staging support.


Error setting getter-only property "className"

I get this error when setting a dynamic class in a svg element:
import {render, svg} from '//unpkg.com/lighterhtml?module';

const someClass = "foobar" // this is dynamic in the original code, this is just a dummy example

// as automatically rendered wired content 🤯
todo(document.body);
function todo(node, items = []) {
  render(node, () => svg`
  <svg width="200" height="200">
    <text x="20" y="35" class=${someClass}>hello world</text>
  </svg>`);
}

it wouldn't have happened in hyperHTML, sorry for the issue, fixed.

Thanks for all your hard work and for bringing sanity to the js world with all the beautiful work you're doing.


django-json-widget's PrettyJSONWidget stopped working with django-unfold

Hello!
I started using Django unfold and I love it. Previously, I was using PrettyJSONWidget from https://kevinmickey.github.io/django-prettyjson/ to render the json nicely in the admin and it worked perfectly, but when I added Django Unfold, it just renders like a Textbox. I managed to adjust all my other Django Admin customizations except for this one.
I noticed from https://github.com/unfoldadmin/django-unfold/blob/main/src/unfold/widgets.py#L296 that most of the widget optimizations rely on `django.contrib.admin.widgets' and assign them the styling classes, but the particulars of PrettyJSONWidget require the use of formfield_overrides like so:
@register(WalletInquiry)
class WalletInquiryAdmin(admin.ModelAdmin):

    formfield_overrides = {
        JSONField: {
            "widget": PrettyJSONWidget(
                attrs={"initial": "parsed", "disabled": True}
            )
        }
    }

Any plans on supporting a json admin widget? Or perhaps any directions on how I can go about fixing this?

Hey, are you looking just for a widget which properly indent json in JSONField?

@lukasvinclav yes :-)

I see that the way the file gets serialized and written in the database has changed (it has new lines now), but the textbox widget ignores that.

This is a different request. Before we wanted to have formatting inside the textarea, now we are looking for formatting when JSONField is displayed as readonly field. Anyway, I just merged an improvement which is checking if the readonly field is JSONField and then enables additional formatting.

how do you make unfold implement the Json field correctly?


Geocode?

Please include latitude and longitude information.

I suggest nominatim via geopy.geocoders for country locations

We will only have coordinates at the country level, not for sub-regions. Is that enough for your purpose?

Fixed via https://github.com/open-covid-19/data/commit/7dc690a9c4bfe31c6d400ca40e9a1423d83740e7


update react-native to 0.59, build error

🐛 Bug Report

'React/RCTFileReaderModule.h' file not found(RCTBlob)
To Reproduce

use xcode build
Expected Behavior

Code Example

Environment

React Native Environment Info:
System:
OS: macOS 10.14.3
CPU: (8) x64 Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz
Memory: 527.59 MB / 16.00 GB
Shell: 5.3 - /bin/zsh
Binaries:
Node: 10.0.0 - ~/.nvm/versions/node/v10.0.0/bin/node
Yarn: 1.13.0 - ~/.nvm/versions/node/v10.0.0/bin/yarn
npm: 6.9.0 - ~/.nvm/versions/node/v10.0.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 28
Build Tools: 28.0.3
System Images: android-28 | Google APIs Intel x86 Atom
IDEs:
Android Studio: 3.3 AI-182.5<IP_ADDRESS>14842
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: ^16.8.4 => 16.8.4
react-native: ^0.59.0 => 0.59.0
npmGlobalPackages:
react-native-cli: 2.0.1
react-native-git-upgrade: 0.2.7
xcode: 10.1 (10B61)

@react-native-bot Thanks

Hello there 👋 this issue seems to be related to your experience upgrading between versions. We know this has been a long lasting pain for the community so starting v0.59 we have introduced a new flow via the new CLI.
To upgrade to that version, you may still need to do some manual steps – we suggest you use rn-diff-repo to accomplish this.
Given that this is not strictly a bug with the library itself I'll close this, but if someone can create a repro that has this issue with a freshly created react-native init project we can reopen it and discuss it further 🤗


Load local files earlier then VimEnter & More

Hi!
Related to #2, I noticed that if I want to set:
autocmd BufReadPost <my cmd>

With prj, it won't run <my cmd> because the file has already been read when VimEnter event was triggered. Hence I think it'd be simply better to call prj#reload() right there on prj.vim.
I also added some more changes which perhaps you'd appreciate.
Thanks for writing this plugin.
Regards.

Thanks for the contribution, but even with this PR the <my cmd> was not executed.
Can you make a minimal example?
I cherry picked some commits 😀

Can you make a minimal example?

Something like this perhaps will work:
mkdir vim-test
cd vim-test
mkdir -p nvim/pack/test/start
git clone https://github.com/doronbehar/vim-prj nvim/pack/test/start/prj
mkdir project
cd project
echo "test:" > Makefile
echo "    echo hello world" >> Makefile
echo "au! BufReadPost Makefile au BufWritePost <buffer> !make test" > .prjrc
env XDG_CONFIG_HOME=$PWD/.. nvim Makefile

And try to test a :write while editing Makefile, and see that prj is asking for a permission to load the .prjrc file.


Import vart and bump version

Description
This PR addresses the following isssues:

Fixes an issue in reading deleted keys within a transaction. Previously, when a key was deleted, the system would return Some([]) instead of None. This behavior was misleading, as it suggested that the key was present but had an empty value, rather than being deleted. With this fix, the system now correctly returns None for deleted keys, accurately reflecting their absence in the database.
Bumps up the crate version to release the fix
Imports vart and replaces index
Fixes clippy warnings

@arriqaaq Can you maybe point me which commit in vart corresponds to the first fix about reading deleted keys?!
From reading the changeset it looks to me that the fix is coming solely from migrating from the internal art package to the new vart.


grpc reconn trigger condition？

thanks!

Hi @huangpeizhi,
Could you provide detail on this issue?

sorry，
I look at the code described in the grpc.go，
grpcExpiresAfter = time.Second * 30
I don't know the connection expires, when new messages, will re-establish the connection with the GPRC server？
thanks!

If 30 seconds is not sending data, GPRC connection is dropped?
If this is the case, can provide a heartbeat approach to maintaining connections?

An idle connection to a grpc endpoint is closed after 30 seconds. A new connection is automatically established when a grpc message is sent to the endpoint. Tile38 handles the all connections is the background.
You should not need to add a heartbeat.

@tidwall , thanks!

You're welcome. :)


WIP: Feature/drag of image files on elementlist

…y on the element-list

Works fine for me!

But can we only allow .png, .jpg and .svg to drop? Otherwise I can drag anything like an .zip or .app into Alva, but the placeholder doesn’t render any more.

@LKuechler It does not indicate the drop zones any more when I drag an PNG or any other file onto the element pane. Before the latest change, you could see wether you drop it as a children or between. Can you reproduce that or should I attach a video?

Closing as discussed with @LKuechler in person.


Strange results for HA

For HA we got very random angles in many cases:

I checked manually the first case:

I'm trying to search the reason of it. I think it is not problem witch code because in excel I see the same issue.
I will let you know if I will find cause of it.

Ok - reason found. The angles have to be corrected. Some of the results are bad. The realization 1 is fine, thus we can get it to the publication. Rest of the realization is checked by Piotr and will be once again analyzed. He will let us know which ones of the 12 realizations are correct.

@soycapitan now data4 have proper angles - I checked the results. The issue can be closed.


Update Dockerfile.ga to use --chown flag for file copying

Description
Fixes the lack of access to the copied files by the app.
Changes proposed in this pull request:
Related issue(s)

See #718

/kind enhancement


Problem when running migrations with a few files at the same time

There is one interesting problem when I attempted  to run migrations (up migrations) with multiple migration files.
So, I had six different migration files, and I ran the migrations. All six files were applied and inserted in the database, but the important thing is that all six had the same applied_at time. I guess that is because they are inserted using one insert statement with multiple values, so they had the same value for the applied_at column (now()).
Unfortunately, if we run the migrations later, some migrations will be applied multiple times. I investigated a bit, and the problem is that the SQL _GET_LATEST_COMMIT_QUERY will only use the first row, as it will order the results by the values of the applied_at column, and all other ones will be ignored.

Hey @rviktor85, thank you for pointing out this issue!
Can you give me the name of each files (and the 2 first lines of each) so I can try to reproduce it?
My guess is that it could be fixed by updating _GET_LATEST_COMMIT_QUERY to
SELECT file_ts, file_name
from public.migration
order by applied_at desc, file_ts desc
limit 1

Hello @Andarius, thank you for your reply!
Here is the snapshot from the DB, where the times, as well as the file names, can be seen:

And for instance, the files:
First one:<PHONE_NUMBER>-42c81daf-up.sql
-- Prev-file:
-- Author: Viktor Radovic

Next one:<PHONE_NUMBER>-62dd3acf-up.sql
-- Prev-file:<PHONE_NUMBER>-42c81daf-up.sql
-- Author: Viktor Radovic

I agree that the easiest solution would be changing the _GET_LATEST_COMMIT_QUERY, as there is a file_ts column.

It should be fixed in the latest version @rviktor85, feel free to reopen if the problem persists.


Corrected compiler error, inaccurate information in passing array topic

Corrected compiler error, inaccurate information in passing array topic
Fixes #6325

Closing and reopening to begin new build.

Thank you so much for the thorough and careful review, @pkulikov! I've addressed all your comments.

Closing and opening to restart build.

Thanks for taking a final look at the topic, @pkulikov. I've removed the unnecessary "to".


Create mat.py

Checklist:

[] I have read freeCodeCamp's contribution guidelines.
[] My pull request has a descriptive title (not a vague title like Update index.md)
[] My pull request targets the main branch of freeCodeCamp.
[] I have tested these changes either locally on my machine, or GitPod.

Closes #XXXXX

您好：    双换感谢您的来信，收到信后我会第一时间回复您，如需紧急处理请致电15809253357，谢谢！


Add SuppressWarnings SS_SHOULD_BE_STATIC

Fixes #XXXX.
(Replace XXXX with the id of the issue fixed in this PR. Remove the above line if there is no corresponding
issue. Don't reference the issue in the title of this pull-request.)
(If you are a committer, follow the PR action item checklist for committers:
https://github.com/apache/incubator-druid/blob/master/dev/committer-instructions.md#pr-and-issue-action-item-checklist-for-committers.)
Description
Describe the goal of this PR, what problem are you fixing. If there is a corresponding issue (referenced above), it's
not necessary to repeat the description here, however, you may choose to keep one summary sentence.
Describe your patch: what did you change in code? How did you fix the problem?
If there are several relatively logically separate changes in this PR, create a mini-section for each of them. For
example:
Fixed the bug ...
Renamed the class ...
Added a forbidden-apis entry ...
In each section, please describe design decisions made, including:

Choice of algorithms
Behavioral aspects. What configuration values are acceptable? How are corner cases and error conditions handled, such
as when there are insufficient resources?
Class organization and design (how the logic is split between classes, inheritance, composition, design patterns)
Method organization and design (how the logic is split between methods, parameters and return types)
Naming (class, method, API, configuration, HTTP endpoint, names of emitted metrics)

It's good to describe an alternative design (or mention an alternative name) for every design (or naming) decision point
and compare the alternatives with the designs that you've implemented (or the names you've chosen) to highlight the
advantages of the chosen designs and names.
If there was a discussion of the design of the feature implemented in this PR elsewhere (e. g. a "Proposal" issue, any
other issue, or a thread in the development mailing list), link to that discussion from this PR description and explain
what have changed in your final design compared to your original proposal or the consensus version in the end of the
discussion. If something hasn't changed since the original discussion, you can omit a detailed discussion of those
aspects of the design here, perhaps apart from brief mentioning for the sake of readability of this PR description.
Some of the aspects mentioned above may be omitted for simple and small changes.

This PR has:

[ ] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

Check the items by putting "x" in the brackets for the done things. Not all of these items apply to every PR. Remove the
items which are not done or not relevant to the PR. None of the items from the checklist above are strictly necessary,
but it would be very helpful if you at least self-review the PR.

For reviewers: the key changed/added classes in this PR are MyFoo, OurBar, and TheirBaz.
(Add this section in big PRs to ease navigation in them for reviewers.)

@Fokko thanks.
Please, never force-push your PR branch.

I'm force-pushing because of the rebasing onto master. I can also pull master into the branch.

You need to merge master into your branch, not rebase. I usually do it as follows:
$ git fetch upstream master
$ git merge upstream/master

And then resolve conflicts.

I'm fine with merging as well. I usually do a pull instead git pull github/master, where github is my upstream.
Most of the projects require a rebase instead of a merge because of history. Mostly because it keeps a linear history, more info here: http://www.bitsnbites.eu/a-tidy-linear-git-history/

In Druid, history is linear because of squash-and-merge as the merge action.

That makes sense, I'll merge/pull in the future 👍


Add Devfest Nantes 2024

@ArtyMaury looks like we're having issue parking https://raw.githubusercontent.com/GDG-Nantes/Devfest2024/main/ when importing.... cc @martinbonnin

failing on 2nd line below line it seems in DevFestNantes.kt
            val talk = Yaml.default.parseToYamlNode(getGithubFile(session)).toAny().asMap

Looks like it was fixed here?

$ curl -X POST https://confetti-app.dev/update/devfestnantes2024
Oooopsie%

Looks like there's something else, I'll dig

Fixed in https://github.com/joreilly/Confetti/pull/1423


Mmx/backend

@mauld-cmu this is the code we ran for the demo today, if it looks good to merge, please do so!


fix: #3018 - storing the pending changes

New file:

dao_transient_operation.dart: Transient operation: a minimalist product with a key.

Impacted files:

barcode_product_query.dart: minor refactoring
local_database.dart: added reference to new class DaoTransientOperation
Podfile.lock: wtf
product_refresher.dart: minor refactoring
pubspec.lock: wtf

What

Here, the main change is the new class DaoTransientOperation, where we will store "minimalist" products

when we add a background task, the first thing we will do is to store the minimalist product there
until the background task is completed, this is where we'll find the pending changes, to be used by the app, that will show the product as stored as the downloaded product, with those pending changes on top
when the background task is completed we download the latest version of the product - at this moment we can remove the corresponding minimalist products as they are integrated into the latest downloaded version

Part of

#3018

Thank you @M123-dev for your review!
I understand your comment but on the other hand getAllForBarcode would be a bit verbose - and there's no plan for a getAll method without barcode either.
We'll see in the next steps, methods may be renamed later.


Create notification messages out of events

file events
user
connectivity
sharing

allow disabling the events in settings.

conflict event


message box for deleting columns

In case you want to delete a column, please create a message box, before submitting:
Are you sure to delete this column?
X Cancel                          y Delete
Otherwise people will delete the column and also all the cards are gone. Please give the users time to think :)

I added the confirm dialog but changed the button position to be more sure the user knows what he confirms.


Travis fails on master

See: https://travis-ci.org/aeternity/elixir-node/builds/435770932
This is a Travis related issue an archive we download seems to have stopped existing in last hour

It seems Travis broke something, because Elixir installation doesn't work even for 1.6.6. (current 1.6) I think Travis has to fix itself.

Open issue with Travis https://github.com/travis-ci/travis-ci/issues/10170

Yeah, the problem persists with the things I just tried

Closed via PR https://github.com/aeternity/elixir-node/pull/664


Deleting Workflow Task properties after adding them

Currently, I can not delete a property anymore after I confirmed adding it. There is a trash button, but it's dimmed and clicking on it doesn't do anything.
Users should be able to delete properties again, because properties can be added in error and Fractal server is strict to not allow unexpected properties when running tasks.

Side comment: the whole work on JSON Schemas makes this issue a bit less urgent to solve, as it will mostly matter for tasks that come without an arguments schema.

As of #758, fractal-server now allows deleting an argument via the PATCH-WorkflowTask endpoint.
If the current WorkflowTask.args is {"a": 1, "b": 2}, then sending a PATCH request with args={"a": 3} will lead to a new WorkflowTask.args = {"a":3} (without b).
This behavior is available for all arguments that do not have a default value in the task args_schema (or for all arguments of tasks without args_schema). If a task has an args_schema, and b has a default, then with the same procedure as above we'll end up with args = {"a": 3, "b": DEFAULT_OF_B}.
It is not possible to fully remove an argument if it has a default value in the schema, and we are not planning to introduce this feature for the moment.


Out of ordering of requests to opensearch

Hi Team,
We are seeing an out of order problem for the requests to opensearch when using index.write.method=upsert.
However we don't see this issue when we set index.write.method=insert.
Below is our connector config
connector.class=io.aiven.kafka.connect.opensearch.OpensearchSinkConnector
behavior.on.null.values=delete
transforms.extractKey.field=id
index.write.method=insert
connection.password=
tasks.max=10
topics=dev.task
batch.size=10000
transforms=extractKey
key.ignore=false
max.in.flight.requests=5
key.ignore.id.strategy=none
transforms.extractKey.type=org.apache.kafka.connect.transforms.ExtractField$Key
schema.ignore=true
key.converter.schemas.enable=false
flush.timeout.ms=300000
value.converter.schemas.enable=false
value.converter=org.apache.kafka.connect.json.JsonConverter
connection.url=...
key.converter=org.apache.kafka.connect.json.JsonConverter
behavior.on.version.conflict=warn
schemas.enable=false

Hey @Ramkumar-byte, thanks for reporting this issue with the sink connector. Is it still happening for you?

FYI: We've experienced same issue. Apparently it can be fixed by setting max.in.flight.requests=1


Storefront tutorial

This pull request includes the tutorial on how to deploy all of the microservices onto openshift.

@phemankita @hkang92 can you guys review this? or make any additional changes you'd like to integrate :-) thanks


Missing DesignSurface in VS2022 Designer Extensibility support for net6.0-windows Windows Forms controls

With reference to this issue, I have read the paragraph “Migrating existing Control Designers with almost no effort” of this article, but I am having trouble building my custom ControlDesigner in .NET6 due to the absence of the DesignSurface class. Let me explain in detail. (I already tried with NET7, but the issue still persists).
My MyControlDesigner class uses a derived Form class called VisualControlDesigner to display an additional popup for customizing the user control.
(Picture shows it in action in a .NET Framework project)

It internally uses a class called DesignSurfaceExt, which is derived from System.ComponentModel.Design.DesignSurface.
However, I cannot locate it in .NET6, as shown in the following image.

Moreover, MyControlDesigner class uses some adorners, which is not an issue, as demonstrated in the following picture.

To help you understand it better, here is a short video demonstrating both Adorners and Visual Control Designer in action in a NetFramework project: https://www.screencast.com/t/ZIdrCvojT9d.

I saw the video, and was impressed by the sophistication of this Designer. At the same time, these are the scenarios which in all honesty need - let's put it this way: the most love to port to the Out-Of-Proc Designer.
While I don't have the complete picture yet why you might need DesignSurface for that implementation, the fact is that the DesignSurface you will ultimately end up with, FWIW, will be the Framework version, simply, because there is not .NET equivalent that would even come to any deployment.
Everything which is UI-related need to be done in the context of .NET Framework and the VS process. So, there will be no rendering on the Serverside, except for the actual control's content and the adorners. So, the Designer Frame, the Behavior service along with the Adorner Overlay and then the actual Designers, which become part of that whole tree when needed. But that bunch of Windows (all being created in the .NET Server Process) get parented - tadah! - to the Client Process based on DesignSurface (and others in betweem). In the .NET process, there is a) no DesignSurface and b) the (modal WinForms TypeEditor-based) Dialogs cannot be kicked of from the .NET Server but only from the .NET Framework Client Process.
For that particular scenario that means some adaptation work: Type Discovery, of course, needs to be done server-side, because Framework does not have "access" to the .NET type information. If .NET is needed to actually render something in particular, then the only way to that is render the result into a Bitmap's HDC, and then request that Bitmap from the respective (Client-side-shown) TypeEditor from the Server. Same is true for everything, which needs to be presented for example in a TreeView Client-side, which only the Server knows about: That information needs to be collected on the server, and then send back to the client, which then can present it in the TypeEditor's dialog.
Hope this helps as a starting point - keep the questions coming!

@KlausLoeffelmann DesignSurface seems to be included in .NET as described here. Why I cannot use it on the Serverside?
Please check out this additional video, which focuses on the .Net Framework version of our component. The video demonstrates the many interactions between the Visual Control Designer and the custom control. You'll notice that every inner element of the custom control is customizable, and the Visual Control Designer picture is updated in real-time. Our approach is similar to the one used by DesignSurfaceExt, which is showcased in this sample. The DesignSurfaceExt has a method CreateControl to interact in real-time with a control. Currently, we're using it to make the Visual Control Designer work.
Here is a sample project showing a very very simplified control. Is it possible to have a version of this project that shows how to use the DesignSurface in the Client to achieve a similar result as in .Net Framework?

P.S. Product is Eyeshot. You can download a copy here if need to make some tests on .Net Framework designer.

Please read this blog post to understand the interaction between Visual Studio as a Client and the DesignToolsServer of the WinForms Designer in the WinForms Designer context.

You should know that I already read it more than once. You also included it in the issue where you requested me to open this one to provide me with better assistance. However, I am still having difficulty achieving my goal.
If it is not too much trouble, would you mind adding some code to the NET6 sample project I shared to help me better understand?
Thank you for your help in advance.

Unfortunately, I don't have the time at this point to ramp-up in that sample project.
But maybe we can compromise by drilling down in little steps to the area, where we can do a better explanation job, to get you unblocked.
So, with that suggested:
Where do the missing information from your perspective start?

To your question about using a .NET 6 control in a .NET Framework process: No, that's not possible. If you have a .NET 6 control, which renders, the only way to mitigate that issue is, to render the output server-side for example to a Bitmap's DC, and then transport the bitmap back, or implement something like a rendering redirector, which would "ask" the server how to render the respective parts inside of a Framework process.

Where do the missing information from your perspective start?

I started working with your sample code several months ago, I even submitted a Pull request for a bug, but it seems to have been overlooked. Nonetheless, that is not my main concern. I am currently unable to locate a sample code that addresses my specific needs. Have you made any improvements to the sample code that I may have missed?
Thank you.

I was finally able to find a solution without using DesignSurface.


Hey man, added events support

Hey man, added events support to the bottom of the stripe api.  Like a two-second job, just extended the api along your pattern.
Best,
Jonathan

Hi Jonathan,
Thank you!
Can you update README.md, too?
Ask

sure
On Feb 3, 2012, at 1:04 PM, Ask Bjørn Hansen wrote:

Hi Jonathan,
Thank you!
Can you update README.md, too?
Ask

Reply to this email directly or view it on GitHub:
https://github.com/abh/node-stripe/pull/25#issuecomment-3801222

done.
On Feb 3, 2012, at 1:04 PM, Ask Bjørn Hansen wrote:

Hi Jonathan,
Thank you!
Can you update README.md, too?
Ask

Reply to this email directly or view it on GitHub:
https://github.com/abh/node-stripe/pull/25#issuecomment-3801222

Thanks!!


Added deadline structs for api

This pr adds deadline structs to be able to manage deadlines via the api.
Blocks go-gitea/gitea#3890.

Where can I add a definition to swagger responses?
Only adding // swagger:model to the struct doesn't seem to work

@JonasFranzDEV thanks, it worked!