Dependency updates

Description
This updates a ton of dependencies (only feature or patch releases). As a follow up I changed one line in the DataProvider.ts-file:
diff --git a/src/DataProvider/DataProvider.ts b/src/DataProvider/DataProvider.ts
index c7cba38..c463185 100644
--- a/src/DataProvider/DataProvider.ts
+++ b/src/DataProvider/DataProvider.ts
@@ -44,7 +44,7 @@ class DataProvider {
     this._parsers = parsers;

     if (this._parsers.length === 0) {
-      new Console().error('The DataProvider was instanciated with an empty "parsers" configuration. ' +
+      throw new Error('The DataProvider was instanciated with an empty "parsers" configuration. ' +
         'The data import will not work - was this intentionally?');
     }
   }

… so that the following error was no longer thrown:
src/DataProvider/DataProvider.ts:47:11 - error TS2693: 'Console' only refers to a type, but is being used as a value here.

47       new Console().error('The DataProvider was instanciated with an empty "parsers" configuration. ' +
             ~~~~~~~

I am not sure if this is the right fix.
This might be a breaking change. IDK
Releated issues or pull requests
Probably related https://github.com/geostyler/geostyler-sld-parser/pull/280 & https://github.com/geostyler/geostyler-openlayers-parser/pull/232 In this PR tslint is not replaced, though.
Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[x] Other (please describe): dependency updates
[ ] I am unsure (we'll look into it together)

Do you introduce a breaking change?

[ ] Yes
[ ] No
[x] I am unsure (no worries, we'll find out)

Checklist

[x] I understand and agree that the changes in this PR will be licensed under the BSD 2-Clause License
[x] I have followed the guidelines for contributing
[x] The proposed change fits to the content of the code of conduct
[x] I have added or updated tests and documentation, and the test suite passes (run npm test locally)
[ ] I'm lost; why do I have to check so many boxes? Please help!

Thanks for the reviews.


Deprecated API usage

I'm not sure how to report this properly, as I'm not sure if it's considered a bug. When running the example app or adding the dependency to my own project the following warning is shown (Android 9):
Note: /development/flutter/.pub-cache/hosted/pub.dartlang.org/photo_manager-0.3.4/android/src/main/kotlin/top/kikt/imagescanner/PermissionsUtils.java uses or overrides a deprecated API.
Note: Recompile with -Xlint:deprecation for details.

This is a warning, because some APIs will be marked as obsolete in some android compiled versions, but these methods will not be removed and will not cause problems when used.
You can use it with confidence.

Closing for now. If the warning becomes an error, I will open a report.
This is a great library, thank you for creating it!


Spurious "c" environment

My files http-client.env.json and http-client.private.env.json only contain keys localhost and staging, but in the environment selector appears a spurious third environment named "c".

I search the following places for environments. One of them seems to contain a c.

.env files (e.g c.env or env.c) <= my blind guess if your project has c code in it
http-client.env.json or http-client.private.env.json
local file .httpyacjs or httpyac.config.json
package.json with property httpyac

@AnWeber The culprit is an .envrc file at the root of the repository. When removing that file, the "c" environment disappears. Apparently the check for .env files is not specific enough and picks up that file when it shouldn't.

@sedubois  thx for the hint to .envrc. I added a fix to the dotenv provider


This is not supported in chrome

This is a Node plugin that utilizes a Java program, and so is not meant to be run in a browser.


Add robolectric tests

Replaced powermock tests with robolectric.
Added robolectric tests for each  activity and fragments.

The current branch for the codelab incorporated a lot of what this PR had, so most of the big pieces from this are already in.


Node JS

Hey guys it will be good if it will automatically install nodejs when installing Vscode!

Hi there. I appreciate you talking the time to open an issue but automatically installing nodejs, and really, the correct version of nodejs for everyone is very challenging and would be hard to get right when a user could install the one they need themselves. As such, I'm going to close this as out of scope.

@TylerLeonhardt We can give the option for users to download Node.JS if they choose yes we can ask them to type their wanted version of node.js. If they choose no we can go on with the regular installation. 😃


The order of the resources is no more respected in "Lockable Resources"-page

Jenkins and plugins versions report

Environment

Jenkins 2.375.2
1123.v4002ee23c671

What Operating System are you using (both controller, and any agents involved in the problem)?
N/A
Reproduction steps
For example:

add Lockable Resources in Jenkins Management
drag and drop to change the order

Expected Results
"Lockable Resources"-page should show the lockable resources in the same order the user has them in Jenkins Management
Actual Results
The order is not the same as in Jenkins Management
Anything else?
No response

This is a bit disturbing, because we have a specific order for our resources to make them visualized nicely for our devs. Also we have used dummy-resources to act as headers for grouping the resources in the Lockable Resources status page.

Yes.  This is known, when you sort columns in the table.  It shall be fixed in data-table plugin.  A workaround is to clear your browser global- storage

@uhafner is it planned to fix it the api? When not we can discuss it, what shall be the best solution and maybe I find time to fix it.

I'm not sure if I can follow. What order do you mean? The order of the columns? The ordering (sorting) of the rows? A screenshot would help.

When it's not planned for the api I can create new settings for lockable-resources-plugin like enable-user-ordering. But it will be very tricky to implement it. And I don't like hack solutions. 😒

I think this is the line
https://github.com/jenkinsci/data-tables-api-plugin/blob/5f0deb21ed2688aa26cb2a11136ef2c54c8f9988/src/main/webapp/js/table.js#L161
It will be fine to provide table option to skip it.
Of course this one too
https://github.com/jenkinsci/data-tables-api-plugin/blob/5f0deb21ed2688aa26cb2a11136ef2c54c8f9988/src/main/webapp/js/table.js#L20

I see. Adding an option should be not too complex, feel free to provide a PR. Since a lot of users like storing of the sorting order it would make sense to make that user configurable using a UI configuration somehow.
BTW: you can use a data table without using the jelly tags. Then you loose some features added by me but then you can use the table as such.

Thx for your answer.  I will contact you next week to discuss "somehow" 😇

To visualize, we have defined lockable resources in this order in the configuration. ( I left labels out for simplicity of the example).
--------- system testlabs
lab1
lab2
lab3
--------- sandboxes
sandbox1
sandbox2
--------- PET
petlab
--------- other lockables

Earlier plugin-versions respected this order in "Lockable Resources"-page visualization, new versions don't.

thx
what about to make something like this
system-test-labs/lab1
system-test-labs/lab2
system-test-labs/lab3
sandboxes/sandbox1
sandboxes/sandbox2
petlab

and it will be "grouped" by '/'  like in tree.
system-test-labs
   lab1
   lab2
   lab3
sandboxes
  sandbox1
  sandbox2
petlab

And this delimiter shall be parametrized. This will be nice UI feature.
But as first, I will try to make enable-sorting configurable.


CPU is constantly using about 4-5% , it was around 1-2% back in 0.192

After upgrade to 194 today , i found CPU usage increased during idle .
I have tested using atom --safe .
I think it has to do with Cursor blinking not rendered using GPU ?
It is more evident especially using atom-block-cursor: https://github.com/olmokramer/atom-block-cursor/issues/15 , cpu usage jumps to 10-12 %
Back in 0192 , even with atom-block-cursor pulsating (easing) animation of cursor , cpu do not consume more than 5%, averaging around 2%

same here, 5-6%.

@deepsweet  thats without atom-block-cursor right?

right.

Cursors are now on their own layer and #8009 should have decreased CPU usage as well.
Are you still observing this? If not, do you think we can close it? :sparkles:

Closing as there have been several improvements related to this. If this is still an issue please comment.


[Bug]: The Widgets in canvas gets deleted, when user clicks ctrl+z to Undo the changes in Query editor

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When the user edit query and click on Ctrl + z The latest added widget will be removed/Undo

Steps To Reproduce

Go to canvas
Add a table widget
Now go to a datasource
Add a new query in Mongo
Add a wrong query now click on control + z from the keyboard
Now the table widget will be removed from the canvas

Environment
Release
Version
Cloud

This should now be solved. @RakshaKShetty


Netlify deploy: no xml in root

Am generating a perfect xml with dynamic routes locally, but after deploying the sitemap.xml is not there.
From the deploy logs:
6:19:23 AM: [success] Generated /.output/public/sitemap.xml
6:19:23 AM: [success] You can now deploy dist to any static hosting!
If I download and look at the deploy folder, its not there, and /sitemap.xml is returning 404
Am very confused:)

Same error for me with Netlify

Was working on local.
Then I try a yarn run build, and sitemap isn't working anymore...
In local, even with 'yarn run dev', sitemap is generated in ".output/public/" folder, not on "public" folder

Working fine on Netlify when I change Publish directory from dist to .output/public.
But website isn't working anymore...

any fix to this ?

I couldnt fix it, so I found a solution to use another package.

I couldnt fix it, so I found a solution to use another package.

Facing the same issue here. Mind sharing what solution you ended up with?

anyone found a fix for this?

Guys, this is related to https://github.com/funkenstudio/sitemap-module-nuxt-3/pull/13
The sitemap is being hardcoded to .outpput/public, but NITRO's preset for netlify uses /dist folder.
My solution was to apply a patch to the package just like this suggestion: https://github.com/funkenstudio/sitemap-module-nuxt-3/issues/17#issuecomment-1327159885
I used yarn 2 instead of pnpm and it's working well.


⚠ Bofrost.be has degraded performance

In 76fcb33, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 1250 ms

Resolved: Bofrost.be performance has improved in 5bf1c38.


Feature/requestBodies param support

This PR implements the requestBodies schemas (148).

Added requestBodies models generation
Added "name" param for every schema: containts original name, whithout suffixes and prefixes
Added 4 template params: modelRequestBodyPrefix, modelRequestBodySuffix, modelResponsePrefix, modelResponseSuffix
Updated template for example requestBodies and new params example
Updated readme with new prefix and suffix description

Hello, @yonaskolb
Test of my PR failed, because specification was updated. I dont checked it before create PR.
I can update specification or remove my changes in template file.
But if I delete the changes in the template file, the template will not show how reguestBodies can be used.
How do I do better in your opinion?


Add a v1 connector for Saavn

I pulled in the original source from here, made some changes and tested it out.
But I can't get the connector to load.
Can someone please have a look and tell what's wrong?

Is there a reason to write the connector in v1 format?

But I can't get the connector to load.
It's because of wrong URL pattern. It shold be '://.saavn.com/*'.

Is there a reason to write the connector in v1 format?

Not really, no. The source I copied it from had it in v1. Once I get this to work, I'll port it to v2, I guess.

Strange, I see no artist info in the player bar on the Saavn page, like in gaana.com.

I didn't test the connector too much, but it should work without problems.
'use strict';

/* global Connector */

var songArtist = null;
var trackInfoUrl = null;

var asyncRequestSongInfo = function() {
    var url = $('#player-track-name a').attr('onclick').split(',')[1].slice(2, -3);
    if (trackInfoUrl != url) {
        $.ajax({url: url, context: document.body}).done(function(trackDetailsHTML) {
            var trackDetailsDOM = $(trackDetailsHTML);
            var artist = trackDetailsDOM.find('.page-meta-group > .meta-list')[0].textContent;
            songArtist = artist;
        });
        trackInfoUrl = url;
    }
};

Connector.playerSelector = '#now-playing';

Connector.getArtist = function() {
    asyncRequestSongInfo();
    return songArtist;
};

Connector.trackSelector = '#player-track-name';

Connector.isPlaying = function() {
    return $('#controls #play').hasClass('hide');
};

@dufferzafar I implemented the connector in v2 format some time ago. Can you test it?

We dropped support for v1 format.


fix: add additional info to Luis error message logging

Description
Add helpful debugging info when an error is thrown during the Luis binding step
Task Item
refs: #8379

Coverage remained the same at 55.934% when pulling 9d76375377f2ea48a35fbb35496d34037926474a on natalgar/8379-add-luis-logging into 97d19ebbcdffe86474c1bdb283b26989603723c0 on main.


AttributeError: 'NoneType' object has no attribute 'real_variable_name'

hello, I get a issue. here I have PNet-30.meta, in which conv4_1 has a output cls_prob, but when I run mmconvert -sf tensorflow -in PNet-30.meta -iw PNet-30 --dstNodeName  cls_prob -df caffe -om tf_PNet, it shows error:
Parse file [PNet-30.meta] with binary format successfully.
Tensorflow model file [PNet-30.meta] loaded successfully.
Tensorflow checkpoint file [PNet-30] loaded successfully. [25] variables loaded.
Tensorflow has not supported operator [Slice] with name [conv4_1/Slice].
Tensorflow has not supported operator [Softmax] with name [conv4_1/Softmax].
IR network structure is saved as [6a75099bfbbf4fd9b0209b9210bf0838.json].
IR network structure is saved as [6a75099bfbbf4fd9b0209b9210bf0838.pb].
IR weights are saved as [6a75099bfbbf4fd9b0209b9210bf0838.npy].
Parse file [6a75099bfbbf4fd9b0209b9210bf0838.pb] with binary format successfully.
Warning: Graph Construct a self-loop node conv4_1/Rank. Ignored.
Warning: Graph Construct a self-loop node conv4_1/Sub/y. Ignored.
Warning: Graph Construct a self-loop node conv4_1/concat/values_0. Ignored.
Warning: Graph Construct a self-loop node conv4_1/Slice. Ignored.
Warning: Graph Construct a self-loop node conv4_1/Softmax. Ignored.
Traceback (most recent call last):
  File "/xxx/local/anaconda2/bin/mmconvert", line 11, in <module>
    sys.exit(_main())
  File "/xxx/local/anaconda2/lib/python2.7/site-packages/mmdnn/conversion/_script/convert.py", line 108, in _main
    ret = IRToCode._convert(code_args)
  File "/xxx/local/anaconda2/lib/python2.7/site-packages/mmdnn/conversion/_script/IRToCode.py", line 61, in _convert
    emitter.run(args.dstModelPath, args.dstWeightPath, args.phase)
  File "/xxx/local/anaconda2/lib/python2.7/site-packages/mmdnn/conversion/caffe/caffe_emitter.py", line 144, in run
    super(CaffeEmitter, self).run(dstNetworkPath, dstWeightPath, phase)
  File "/xxx/local/anaconda2/lib/python2.7/site-packages/mmdnn/conversion/common/DataStructure/emitter.py", line 21, in run
    self.save_code(dstNetworkPath, phase)
  File "/xxx/local/anaconda2/lib/python2.7/site-packages/mmdnn/conversion/common/DataStructure/emitter.py", line 53, in save_code
    code = self.gen_code(phase)
  File "/xxx/local/anaconda2/lib/python2.7/site-packages/mmdnn/conversion/caffe/caffe_emitter.py", line 132, in gen_code
    func(current_node)
  File "/xxx/local/anaconda2/lib/python2.7/site-packages/mmdnn/conversion/caffe/caffe_emitter.py", line 558, in emit_Reshape
    self.parent_variable_name(IR_node),
  File "/xxx/local/anaconda2/lib/python2.7/site-packages/mmdnn/conversion/common/DataStructure/emitter.py", line 41, in parent_variable_name
    return self.IR_graph.get_parent(IR_node.name, path).real_variable_name
AttributeError: 'NoneType' object has no attribute 'real_variable_name'

how to fix it?
can anyone give some advises?
thank you very much~

Hi @IvyGongoogle , could you please provide your model file for us to debug?

@namizzz  thanks for your reply. you can get my PNet-30.meta under here. and you also can get the model parameters in it.
looking forward your reply.

need help~~

Hi @IvyGongoogle , thanks for your issue, we have fixed the problems!

@IvyGongoogle I used your model and your command

mmconvert -sf tensorflow -in PNet-30.meta -iw PNet-30 --dstNodeName cls_prob -df caffe -om tf_PNet
,then the same error occurred.Have you solved this problem yet?

I'm getting the same error when I'm trying to convert tensorflow to pytorch. Anyone has fixed it yet?


Users SBAT refresh their contacts list to update the numbers/profile pictures

Expected Behavior
A refresh button similar to the one in whatsapp would be useful.
The users need to refresh the contact list in celo app when they add/update contact in their phonebook.
Current Behavior
The contact list is never updated after the 1st import.

this happens automatically, feel free to reopen if that is not the case


Fixed issues related to owenership of default tags

It seems some behaviour has changed in MOAB regarding the ownership of these 3 default tags. This change should be backwards compatible with other MOAB v5 releases but I havent tested it.

Brilliant! Thanks for this. I've tested it with 5.1.0 and it works great. I'll merge it in on Monday.


fix: minor bugs from query refactor

Need this to fix a few minor query bugs when installed live changes in the extension.

Summary by CodeRabbit

New Features

Introduced useGetStacksNetworkStatusQuery function to query the network status.

Improvements

Enhanced type consistency in contract-related functions by updating from ContractCallPayload to TransactionPayload.

Deprecations

Removed export of network.hooks to streamline module exports.

Checks passed, merging bc minor fixes to make sure queries in extension aren't broken.


Contact & Announcement List pages: update GPG key links & provide fingerprints

Closes #543 ; CC: @kallerosenbaum
Updated bottom section on Announcement list page looks like:

New bottom section on updated Contact page looks like:

Translations of the two pages don't have any text changed, but the links for the three keys are redirected to the pgp.mit.edu keyserver web interface as suggested in the corresponding issues (pgp.mit.edu is slow, but at least it doesn't 404).  When those pages are re-translated with the updated content, we can remove the old links directly to the keys.
I obtained the key fingerprints from here but haven't otherwise validated them, so somebody who has checked them should probably review this PR.

That's a huge improvement. It even looks good!

ACK 54f95ce852e19b09b00a9041ca651f1382af6340

I obtained the key fingerprints from here but haven't otherwise validated them, so somebody who has checked them should probably review this PR.

Fingerprints are correct:
      Key fingerprint = 71A3 B167 3540 5025 D447  E8F2 7481 0B01 2346 C9A6
uid                   [ultimate] Wladimir J. van der Laan<EMAIL_ADDRESS>uid                   [ultimate] Wladimir J. van der Laan<EMAIL_ADDRESS>
      Key fingerprint = 32EE 5C4C 3FA1 5CCA DB46  ABE5 29D4 BCB6 416F 53EC
uid                   [  full  ] Jonas Schnelli<EMAIL_ADDRESS>
      Key fingerprint = 133E AC17 9436 F14A 5CF1  B794 860F EB80 4E66 9320
uid                   [  full  ] Pieter Wuille<EMAIL_ADDRESS>
A small nit - there's something to be said for formatting the key fingerprints as above^^ per four hex digits, as this makes it slightly easier to compare.

@laanwj Yeah, I think that could help.  I just tested and GPG allows you to --recv-keys even with spaces in them, so it doesn't make the key import instructions much more complicated (people just need to add quotes).  Here's an updated preview with the latest commit:

@kallerosenbaum do you foresee any UX issues with this updated styling?

@harding No, not really. Since you can quote the space separated text in gpg, it's fine. You could add a copy button that copies the text without spaces to clipboard, but that's possibly exploitable (eg display one thing and copy another thing). Also, there might even be a way to css format the fingerprint with spaces, but the text is actually without spaces. That's possibly confusing to the user who expects a space separated fingerprint in her paste buffer because that's what she thought she copied.
A drawback with spaces is that you can't double-click to copy the whole fingerprint.
Your extra comment about quotes is clear. I think it's better with spaces but not in every aspect.

@kallerosenbaum yeah, I do think we lose a little something by not being able to double-click to select the whole fingerprint, but hopefully that doesn't end up being too much of an issue (if it is, we can always change back or experiment further).  Thanks for reviewing!
If anyone has further comments, I'd be happy to hear them.  If not, I plan to merge sometime after 16:00 UTC Friday.

Post merge ACK by looking at the live website.


Add Python coverage. Remove PercentStyle members

Codecov Report

Merging #35 (6f42e0f) into main (7513112) will decrease coverage by 14.34%.
The diff coverage is n/a.

:exclamation: Current head 6f42e0f differs from pull request most recent head 1cc2fd5. Consider uploading reports for the commit 1cc2fd5 to get more accurate results

@@             Coverage Diff             @@
##             main      #35       +/-   ##
===========================================
- Coverage   80.73%   66.38%   -14.35%
===========================================
  Files           8        2        -6
  Lines        1095      238      -857
===========================================
- Hits          884      158      -726
+ Misses        211       80      -131

Impacted Files
Coverage Δ

src/picologging/formatstyle.cxx

src/picologging/formatter.cxx

src/picologging/logrecord.cxx

src/picologging/_picologging.cxx

src/picologging/streamhandler.cxx

src/picologging/handler.cxx

src/picologging/filterer.cxx

src/picologging/logger.cxx

src/picologging/handlers.py
88.88% <0.00%> (ø)

src/picologging/__init__.py
52.70% <0.00%> (ø)

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7513112...1cc2fd5. Read the comment docs.


Add note about Cloud9 ownership

What would you like to be added?
A note should be added to the "Accessing the IDE" page that mentions that the Cloud9 may need shared with the console role/user if the Terraform was run with a separate user.
aws cloud9 create-environment-membership --environment-id XXXXXXXXXXXXXXXXX  --user-arn arn:aws:sts::1234567890:assumed-role/Admin/somerole --permissions read-write

Why is this needed?
This scenario will cause the Cloud9 instance to appear missing and confuse users.

Fixed by #435


Feature request: when clicking the "restart" button on job detail page, jump directly to details of new job

currently, the UI jumps back to the dashboard

this seems implemented now. thanks!


[typo][doc]modify some sql syntax and example description errors.

Proposed changes
modify some sql syntax and example description errors.

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall


Be persistent when handling zk watch update

Before this PR data watch and children watch never retried to react on zk update.
Particularly, if you run multiple deploy and undeploy actions in short period of time, there is a chance that handling undeploy operation fail and deploy operation won't be handled at all.

https://ocd.appscale.com:8080/job/Daily Build/4007/
https://ocd.appscale.com:8080/job/Hawkeye-Simple-4/874/
https://ocd.appscale.com:8080/job/Hawkeye-Simple-8/939/
https://ocd.appscale.com:8080/job/Migration/2033/

https://ocd.appscale.com:8080/job/Hawkeye-Simple-8/955/
https://ocd.appscale.com:8080/job/Hawkeye-Advanced-8/889/
https://ocd.appscale.com:8080/job/Blobstore/2732/
https://ocd.appscale.com:8080/job/Migration/2047/

https://ocd.appscale.com:8080/job/Daily Build/4020/

https://ocd.appscale.com:8080/job/Hawkeye-Simple-8/956/
https://ocd.appscale.com:8080/job/Hawkeye-Simple-8/957/
https://ocd.appscale.com:8080/job/Migration/2048/
https://ocd.appscale.com:8080/job/Autoscale-test-manual-triggers/799/


Dragonfly and nydus are integrated via mirror

Feature request:

Use case:

UI Example:

@sctb512 @raoxiang1996 We can reference the issue once the PR about mirror support is ready on nydus side, some docs should be published.

Test: https://hackmd.io/2g_NiyapQJOavVKPu4NNfw?view

Install Test Environment:
Install Dragonfly
Create Kind Cluster
Kind Config config-peer.yaml:
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
networking:
  ipFamily: dual
nodes:
- role: control-plane
  image: kindest/node:v1.23.4@sha256:0e34f0d0fd448aa2f2819cfd74e99fe5793a6e4938b328f657c8e3f81ee0dfb9
- role: worker
  image: kindest/node:v1.23.4@sha256:0e34f0d0fd448aa2f2819cfd74e99fe5793a6e4938b328f657c8e3f81ee0dfb9
  extraPortMappings:
  - containerPort: 30950
    hostPort: 65001
- role: worker
  image: kindest/node:v1.23.4@sha256:0e34f0d0fd448aa2f2819cfd74e99fe5793a6e4938b328f657c8e3f81ee0dfb9
- role: worker
  image: kindest/node:v1.23.4@sha256:0e34f0d0fd448aa2f2819cfd74e99fe5793a6e4938b328f657c8e3f81ee0dfb9

kind create cluster --config ./config-peer.yaml

Testing:
Start downloading blobs with range header => 2022-09-26 06:00:18.292
Finish downloading blobs with range header => 2022-09-26 06:00:20.098
The two most time-consuming parts:

First auth request to return 401 http code => 06:00:18.296 - 06:00:19.233
Downlod blobs with range header => 06:00:19.484 - 06:00:20.098

Tracing:

Download blob with range header will be back-to-source twice. The solution is to cache the auth token, and the blob download does not require multiple verifications.

Maybe we need to fix auth header cache for mirror implementation in nydusd.

Maybe we need to fix auth header cache for mirror implementation in nydusd.

It is under repair.

Refer to https://github.com/dragonflyoss/image-service/pull/790


Add custom parameters to Home Assistant notification

Hi!
I am trying use home assistant notification with a Telegram services (yes, I know I can use telegram directly without HA, but with HA service I can configure all from HA without touch anything in Epic Games Free).
The problem is the notification generate invalid markdown code, so, telegram service fail.
The simple solution is add parameters to service and I could add mode=html and all would work fine.
{
      "type": "homeassistant",
      "instance": "https://homeassistant.example.com",
      "token": "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiaWF0IjoxNTE2MjM5MDIyfQ.SflKxwRJSMeKKF2QT4fwpMeJf36POk6yJV_adQssw5c",
      "notifyservice": "mobile_app_smartphone_name",
      "notifydata": {
            "mode": "html"
        }
}

After looking at the Home Assistant docs, I don't quite understand your request. The HTML option isn't an HTML flag in the API; it seems to just be that the API accepts HTML.
Are you requesting that the notification message is formatted as HTML when with "mode": "html"? In that case, wouldn't that still be invalid Markdown for your Telegram service?

My request is pass "any param" to service so it allow use with any Home Assistant notifier, not only mobile notifier.
For example, for Telegram Notifier (https://www.home-assistant.io/integrations/telegram/#extra-data-attributes-support) there are parse_mode and the default value is markdown, but the text sended by epicgames-freegames is not a valid markdown, but, adding parse_mode: "html" the message it will work fine.
This too allow  use another's notifiers as discords (https://www.home-assistant.io/integrations/discord/) for example with it own params.

Added the customData option to the Home Assistant config. It takes an object, so you can set
"customData": {
  "parse_mode": "html"
}

in your config.json. Let me know if that works for you.

I tested and it does not work :(
I think that HA remove custom parameters.
I will send you a PR for "universal" webhook notifier and it should be compatible with HA.
Thanks ;)


Let wait_for abort when all exceptions.

Caveat: I don't know how to run the shakedown selftests; I tried tox and it kicked out after hundreds of "syntax" errors.

@colin-msphere @ssk2 -- perhaps you can either review or suggest a reviewer.


bors/homu should set S- tags

when bors acknowledges a commit, set to S-waiting-on-bors, if a merge fails, set to S-waiting-on-author. There would still be some manual work, but significantly less.

For reference, servo handles this in highfive:

https://github.com/servo/highfive/blob/master/handlers/homu_status/__init__.py#L67
https://github.com/servo/highfive/blob/master/handlers/status_update/__init__.py#L72-L74


Add carousel for blogs

Related Issue
[Cite any related issue(s) this pull request addresses. If none, simply state "None”]
#754
Description
[Please include a brief description of the changes or features added]
Type of PR

[x] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
[Attach any relevant screenshots or videos demonstrating the changes]

Checklist:

[ X] I have performed a self-review of my code
[ X] I have read and followed the Contribution Guidelines.
[X ] I have tested the changes thoroughly before submitting this pull request.
[ X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[ X] I have commented my code, particularly in hard-to-understand areas.

Additional context:
[Include any additional information or context that might be helpful for reviewers.]

@Suchitra-Sahoo Please kindly review this and add labels accordingly!!

Please don't raise a PR before the issue is assigned from next time. Now that you have raised a PR you can attach a video to show your changes, if your idea seems suitable i'll assign you the issue and then merge this PR.

Screenshot is not visible

Please don't before the issue is assigned. Also the carsosel idea is not looking suitable for blog section.


npm install fails with SyntaxError

When trying to install bower, or when running npm install archy, the following error is thrown:
npm http GET https://registry.npmjs.org/archy
npm http 200 https://registry.npmjs.org/archy
npm ERR! registry error parsing json
npm ERR! SyntaxError: Unexpected token _
npm ERR! __utmc=251085184; __utmz=251085184.1398704766.2.2.utmcsr=yandex|utmccn=(organic)|utmcmd=organic; optimizelyPendingLogEvents=%5B%5D; __utma=209680785.856385113.1398704766.1398704766.1398704766.1; __utmb=2096807<IP_ADDRESS>8704769929; __utmc=209680785; __utmz=209680785.1398704766.1.1.utmcsr=yandex|utmccn=(organic)|utmcmd=organics","dirFastly-FF: cache-fra1233-FRA, cache-fra1228-FRAtest"},"devDependencies":{"tap":"~0.2.3"},"scripts":{"test":"tap test"},"repository":{"type":"git","url":"git://github.com/substack/node-archy.git"},"keywords":["hierarchy","npm ls","unicode","pretty","print"],"author":{"name":"James Halliday","email":"mail@substack.net","url":"http://substack.net"},"license":"MIT/X11","engine":{"node":">=0.4"},"_npmUser":{"name":"substack","email":"mail@substack.net"},"_id":"archy@0.0.0","dependencies":{},"engines":{"node":"*"},"_engineSupported":true,"_npmVersion":"1.0.106","_nodeVersion":"v0.4.12","_defaultsLoaded":true,"dist":{"shasum":"fcc82f2916a8307969b368e8617646b41697c37b","tarball":"http://registry.npmjs.org/archy/-/archy-0.0.0.tgz"},"maintainers":[{"name":"substack","email":"mail@substack.net"}]},"0.0.1":{"name":"archy","version":"0.0.1","description":"render nested hierarchies `npm ls` style with unicode pipes","main":"index.js","directories":{"lib":".","example":"example","test":"test"},"devDependencies":{"tap":"~0.2.3"},"scripts":{"test":"tap test"},"repository":{"type":"git","url":"git://github.com/substack/node-archy.git"},"keywords":["hierarchy","npm ls","unicode","pretty","print"],"author":{"name":"James Halliday","email":"mail@substack.net","url":"http://substack.net"},"license":"MIT/X11","engine":{"node":">=0.4"},"_npmUser":{"name":"substack","email":"mail@substack.net"},"_id":"archy@0.0.1","dependencies":{},"engines":{"node":"*"},"_engineSupported":true,"_npmVersion":"1.0.106","_nodeVersion":"v0.4.12","_defaultsLoaded":true,"dist":{"shasum":"8c26dc5741db90792ccdbd34c57311cb3003ea1b","tarball":"http://registry.npmjs.org/archy/-/archy-0.0.1.tgz"},"maintainers":[{"name":"substack","email":"mail@substack.net"}]},"0.0.2":{"name":"archy","version":"0.0.2","description":"render nested hierarchies `npm ls` style with unicode pipes","main":"index.js","directories":{"lib":".","example":"example","test":"test"},"devDependencies":{"tap":"~0.2.3"},"scripts":{"test":"tap test"},"repository":{"type":"git","url":"git://github.com/substack/node-archy.git"},"keywords":["hierarchy","npm ls","unicode","pretty","print"],"author":{"name":"James Halliday","email":"mail@substack.net","url":"http://substack.net"},"license":"MIT/X11","engine":{"node":">=0.4"},"_npmUser":{"name":"substack","email":"mail@substack.net"},"_id":"archy@0.0.2","dependencies":{},"engines":{"node":"*"},"_engineSupported":true,"_npmVersion":"1.0.106","_nodeVersion":"v0.4.12","_defaultsLoaded":true,"dist":{"shasum":"910f43bf66141fc335564597abc189df44b3d35e","tarball":"http://registry.npmjs.org/archy/-/archy-0.0.2.tgz"},"maintainers":[{"name":"substack","email":"mail@substack.net"}]}},"readme":null,"maintainers":[{"name":"substack","email":"mail@substack.net"}],"time":{"modified":"2013-11-28T16:13:38.735Z","created":"2012-03-08T21:18:36.039Z","0.0.0":"2012-03-08T21:18:54.909Z","0.0.1":"2012-03-08T23:09:26.726Z","0.0.2":"2012-03-08T23:09:46.988Z"},"author":{"name":"James Halliday","email":"mail@substack.net","url":"http://substack.net"},"repository":{"type":"git","url":"git://github.com/substack/node-archy.git"},"users":{"tellnes":true,"conradz":true},"_attachments":{}}
npm ERR!     at Object.parse (native)
npm ERR!     at RegClient.<anonymous> (/mnt/sdc1/thealphanerd/node/node-v0.10.26-linux-x64/lib/node_modules/npm/node_modules/npm-registry-client/lib/request.js:203:23)
npm ERR!     at Request.self.callback (/mnt/sdc1/thealphanerd/node/node-v0.10.26-linux-x64/lib/node_modules/npm/node_modules/request/request.js:123:22)
npm ERR!     at Request.EventEmitter.emit (events.js:98:17)
npm ERR!     at Request.<anonymous> (/mnt/sdc1/thealphanerd/node/node-v0.10.26-linux-x64/lib/node_modules/npm/node_modules/request/request.js:893:14)
npm ERR!     at Request.EventEmitter.emit (events.js:117:20)
npm ERR!     at IncomingMessage.<anonymous> (/mnt/sdc1/thealphanerd/node/node-v0.10.26-linux-x64/lib/node_modules/npm/node_modules/request/request.js:844:12)
npm ERR!     at IncomingMessage.EventEmitter.emit (events.js:117:20)
npm ERR!     at _stream_readable.js:920:16
npm ERR!     at process._tickCallback (node.js:415:13)

This is reproducible on both Mac OS X and Windows 8.
Is there a workaround for this please?

It seems to be fixed. You can close it


Add a command to download any SRS files of any size

Delegate the downloading of SRS files to the end-user.
Based on the discussion here https://github.com/sigma0-xyz/zkbitcoin/issues/36 with small modifications; we've added a new download-srs helper command for the user instead having him download the file manually.

@mimoo I don't have a particular preference to be honest. What you say make sense to me. In fact the first version of this PR worked the way you described 😆
Let me revert some of the commits.

@mimoo I've removed the new command. Users would have to provide the srs-path instead.


bottom: 0.9.2 -> 0.9.3

Diff: https://github.com/ClementTsang/bottom/compare/0.9.2...0.9.3
Changelog: https://github.com/ClementTsang/bottom/blob/0.9.3/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 239829 run on x86_64-darwin 1

1 package built:

bottom


All nodes "jumps around" when a node is clicked

Hi,
I've tried to read through the source to find some hints to where I need to adjust/patch the code so that not every graph in the view restarts the force-based simulation/layout.
Is this normal D3 behavior, or is it something you have added to this particular component @eisman ?

Hi @larsw ,
did you find any solution to this issue?

Sorry can't remember, long time ago I played with it.


Feature/3636 Add indexing to hasFieldOrPropertyWithValue

Check List:

Adds convenience feature to hasFieldOrPropertyWithValue #3513
Unit tests : YES ✅
Javadoc with a code example (on API only) : YES ✅
PR meets the contributing guidelines: YES ✅ (to the best of my knowledge)

With this PR we can do something like hasFieldOrPropertyWithValue("users[0].username", "foo") for convenience.
Done

Made necessary changes, and expanded javadoc example on API
Added new test files and test cases
Covered 1/2 map edge cases
Ran the code formatter

Todo

Look at 2nd map edge case (will add to the same PR as a different commit if I can solve it)
Though did not change any nesting code, add some tests on that for sanity checking, to check something like foo.bar[0]

Open to interpretation

Could throw number format or index out of bounds exceptions as opposed to AssertionError (current behaviour)

Did not do:

Did not add further tests to ObjectAssert_hasFieldOrPropertyWithValue_Test , NavigationMethodBaseTest, RecursiveAssertionAssert_* since I'm not clear on the scope of those test files.
Not sure if need to add new authorship entries to modified files

Notes
This is part of hacktoberfest.
Note that there are two edge cases

Maps that have users[0] as a key name (supported)
Maps that have users as key name that is an array or list (not looked into yet)

[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for AssertJ Build 3.26.4-SNAPSHOT:
[INFO]
[INFO] AssertJ Build ...................................... SUCCESS [  0.046 s]
[INFO] AssertJ (Bill of Materials) ........................ SUCCESS [  0.119 s]
[INFO] AssertJ Parent ..................................... SUCCESS [  0.001 s]
[INFO] AssertJ Core ....................................... SUCCESS [ 40.550 s]
[INFO] AssertJ Guava ...................................... SUCCESS [  0.263 s]
[INFO] AssertJ Tests ...................................... SUCCESS [  0.039 s]
[INFO] AssertJ Integration Tests .......................... SUCCESS [  0.003 s]
[INFO] AssertJ Core Integration Tests (JUnit 4 and opentest4j) SUCCESS [  0.771 s]
[INFO] AssertJ Core Integration Tests (Kotlin) ............ SUCCESS [  4.059 s]
[INFO] AssertJ Core Integration Tests (OSGi) .............. SUCCESS [  0.211 s]
[INFO] AssertJ Core Integration Tests (Spring Boot) ....... SUCCESS [  3.383 s]
[INFO] AssertJ Core Integration Tests (TestNG and JUnit 4)  SUCCESS [  0.802 s]
[INFO] AssertJ Core Tests ................................. SUCCESS [  4.961 s]
[INFO] AssertJ Guava Integration Tests .................... SUCCESS [  1.284 s]
[INFO] AssertJ Core Integration Tests (Groovy) ............ SUCCESS [  1.401 s]
[INFO] AssertJ Performance Tests .......................... SUCCESS [  0.625 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  59.281 s
[INFO] Finished at: 2024-10-09T17:42:55+02:00
[INFO] ------------------------------------------------------------------------

Will look at rest of TODOs tomorrow

Looks like I forgot to run the spotless:apply on my last change 😅
Running it and adding it to the PR.
javadoc task fails because of many unrelated failures though.

We could have the spotless:check on the PR checklist template

Any thoughts on this?

Hi @danigiri, thanks a lot for the PR and sorry for the slow feedback!
We're a bit behind with reviews, but we'll eventually get back to this change. I'm going to label the PR accordingly to make sure it gets counted for Hacktoberfest.

@scordio no worries, thanks for getting back to me on this.
Let's see what the feedback is on the idea/code.

I will look at the javadoc check and see what is is about

I will look at the javadoc check and see what is is about

Between the warnings that you don't have to focus on, I can see this:
[ERROR] /home/runner/work/assertj/assertj/assertj-core/src/main/java/org/assertj/core/api/AbstractObjectAssert.java:674: error: unknown tag: TolkienCharacter
[ERROR]    *   private List<TolkienCharacter> friends;

Between the warnings that you don't have to focus on, I can see this:

yup, just saw it, fixed on 027111b and javadoc maven command succeeds


CIFAR

I only find the way to run Imagenet. Would you like to tell me how to run CIFAR?

Just give ./train_script.py -d cifar10 [other args]


Broken code.

Awesome little project! I found a bug in the encrypt and decrypt methods though.
This code in the get_key_iv method:
https://github.com/boppreh/aes/blob/bb81e5a82d37a46aa2d00e26f8de36dc4e1bc83e/aes.py#L472-L475
Should be one of these possible fixes, depending on what you intended:
    stretched = pbkdf2_hmac('sha256', password, salt, workload, AES_KEY_SIZE + IV_SIZE + HMAC_KEY_SIZE)
    aes_key, stretched = stretched[:AES_KEY_SIZE], stretched[AES_KEY_SIZE:]
    hmac_key, stretched = stretched[:HMAC_KEY_SIZE], stretched[HMAC_KEY_SIZE:]
    iv = stretched[:IV_SIZE]

    rest = pbkdf2_hmac('sha256', password, salt, workload, AES_KEY_SIZE + IV_SIZE + HMAC_KEY_SIZE)
    aes_key, rest = rest[:AES_KEY_SIZE], rest[AES_KEY_SIZE:]
    hmac_key, rest = rest[:HMAC_KEY_SIZE], rest[HMAC_KEY_SIZE:]
    iv = rest[:IV_SIZE]

    stretched = pbkdf2_hmac('sha256', password, salt, workload, AES_KEY_SIZE + IV_SIZE + HMAC_KEY_SIZE)
    aes_key, rest = stretched[:AES_KEY_SIZE], stretched[AES_KEY_SIZE:]
    hmac_key, rest = rest[:HMAC_KEY_SIZE], rest[HMAC_KEY_SIZE:]
    iv = rest[:IV_SIZE]

Thanks, just fixed it!


gazebo_ros_pkgs: 3.5.0-1 in 'foxy/distribution.yaml' [bloom]

Increasing version of package(s) in repository gazebo_ros_pkgs to 3.5.0-1:

upstream repository: https://github.com/ros-simulation/gazebo_ros_pkgs
release repository: https://github.com/ros2-gbp/gazebo_ros_pkgs-release.git
distro file: foxy/distribution.yaml
bloom version: 0.9.3
previous version for package: null

gazebo_dev
* Merge pull request #1129 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1129> from ros-simulation/e_to_f_june_2020
  Eloquent ➡ Foxy
* Dashing -> Eloquent
* Gazebo 11 for Foxy (#1093 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1093>)
  * Gazebo 11 for Foxy
* 3.3.5
* Contributors: Jose Luis Rivero, Louise Poubel

gazebo_msgs
* Merge pull request #1129 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1129> from ros-simulation/e_to_f_june_2020
  Eloquent ➡ Foxy
* Dashing -> Eloquent
* 3.3.5
* Contributors: Jose Luis Rivero, Louise Poubel

gazebo_plugins
* Merge pull request #1130 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1130> from ros-simulation/foxy_tests
  Fix all Foxy tests
* Merge pull request #1129 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1129> from ros-simulation/e_to_f_june_2020
  Eloquent ➡ Foxy
* Apply acceleration until both left and right reach targetspeed (#1009 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1009>)
  Co-authored-by: Louise Poubel<EMAIL_ADDRESS>* use target include directories (#1040 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1040>)
  Co-authored-by: Louise Poubel<EMAIL_ADDRESS>* Dashing -> Eloquent
* [forward port] Image publishers use SensorDataQoSProfile (#1031 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1031>) (#1052 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1052>)
  All other sensor publishers were updated previously to use the same profile (#926 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/926>).
  I'm not sure if the image publishers were overlooked or the image_transport API didn't
  support setting the QoS profile at the time.
* Fix cppcheck errors (#1123 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1123>)
  cppcheck 1.90 complains about syntax errors even though it is valid C++ code.
  This refactoring fixes the reported errors.
* Replace deprecated parameters callback API (#1121 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1121>)
  rclcpp::Node now supports multiple parameter callbacks, so we do not need to worry about overwriting an existing callback.
  This change fixes compile time deprecation warnings since ROS Foxy.
* Replace deprecated image_common headers (#1122 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1122>)
  This fixes compile-time deprecation warnings.
* Measure IMU orientation with respect to world (ros2) (#1064 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1064>)
  * Measure IMU orientation with respect to world (#1058 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1058>)
  Report the IMU orientation from the sensor plugin with respect to the world frame.
  This complies with convention documented in REP 145: https://www.ros.org/reps/rep-0145.html
  In order to not break existing behavior, users should opt-in by adding a new SDF tag.
  Co-authored-by: Jacob Perron<EMAIL_ADDRESS>  * IMU sensor: comply with REP 145 by default
  Change default value of initial_orientation_as_reference to false
  and print deprecation warning if user explicitly sets it to true.
  Co-authored-by: Jacob Perron<EMAIL_ADDRESS>* Make QoS for publishers and subscriptions configurable  (#1092 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1092>)
  * Make QoS for publishers and subscriptions configurable
  Whenever a plugin creates a ROS publisher or subscription, use the QoS profile provided by the node for the given topic.
  This enables users to override the QoS settings in SDF.
  Depends on https://github.com/ros-simulation/gazebo_ros_pkgs/pull/1091.
* [eloquent] Fix Windows build. (#1077 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1077>)
  * Adding Windows bringup.
* Gazebo 11 for Foxy (#1093 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1093>)
  * Gazebo 11 for Foxy
* 3.3.5
* Backport Gazebo11/Bionic fix for boost variant (#1102 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1102>)
* Measure IMU orientation with respect to world (dashing) (#1065 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1065>)
  Report the IMU orientation from the sensor plugin
  with respect to the world frame.
  This complies with convention documented in REP 145:
  https://www.ros.org/reps/rep-0145.html
  In order to not break existing behavior,
  users should opt-in by adding a new SDF tag.
  Co-authored-by: Jacob Perron<EMAIL_ADDRESS>* Uncrustify (#1060 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1060>)
  Style changes to conform to the new default setting introduced in https://github.com/ament/ament_lint/pull/210.
  Arguments that do not fit on one line must start on a new line.
* Contributors: Jacob Perron, Jose Luis Rivero, Karsten Knese, Louise Poubel, Sean Yen, Steve Peters, Steven Peters, scgroot

gazebo_ros
* Merge pull request #1130 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1130> from ros-simulation/foxy_tests
  Fix all Foxy tests
* Merge pull request #1129 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1129> from ros-simulation/e_to_f_june_2020
  Eloquent ➡ Foxy
* Dashing -> Eloquent
* [ROS 2] Use "" as default in spawn_entity.py instead of self.get_namespace(). (#1117 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1117>)
* Fix flake8 failures (#1110 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1110>)
* Add gazebo_ros::QoS class (#1091 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1091>)
  Contains logic for parsing <qos> SDF elements and creating rclcpp::QoS objects for ROS publishers and subscriptions.
  Co-authored-by: Ivan Santiago Paunovic<EMAIL_ADDRESS>* [eloquent] Fix Windows build. (#1077 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1077>)
* 3.3.5
* [forward port to Foxy] Add node required parameter to launch (#1074 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1074>)  (#1086 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1086>)
* Use configurable timeout in other wait for service calls (#1073 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1073>)
  * Use configurable timeout in other wait for service calls
  Follow-up to #1072 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1072>
* Increase spawn entity wait for service timeout (#1072 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1072>)
  If we have a reaonsable complex launch file and lots of DDS discovery traffic, sometimes five seconds isn't enough.
  This change makes the timeout configurable and changes the default timeout to thirty seconds.
* Uncrustify (#1060 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1060>)
  Style changes to conform to the new default setting introduced in https://github.com/ament/ament_lint/pull/210.
  Arguments that do not fit on one line must start on a new line.
* [ros2] make transient local reliable (#1033 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1033>)
  Co-Authored-By: chapulina<EMAIL_ADDRESS>* Contributors: Alejandro Hernández Cordero, Ivan Santiago Paunovic, Jacob Perron, Jose Luis Rivero, Karsten Knese, Louise Poubel, Mabel Zhang, Sean Yen

gazebo_ros_pkgs
* Merge pull request #1129 <https://github.com/ros-simulation/gazebo_ros_pkgs/issues/1129> from ros-simulation/e_to_f_june_2020
  Eloquent ➡ Foxy
* Dashing -> Eloquent
* 3.3.5
* Contributors: Jose Luis Rivero, Louise Poubel

@chapulina For Foxy, we should use bloom version >= 0.9.7. Rerunning bloom-release with a newer version should fix the failures on the buildfarm (example failure)

Oh sorry, see https://github.com/ros/rosdistro/pull/25595.


Updating consoles as per discussion in #3 to use simple-console.

Replaced invariants with explicit throws
Added logic and config to remove consoles/invariants from running in production & standalone

Good call

@kenwheeler -- Sorry for the moving target here, but I've slightly refactored how the Noop logger / base class works in v0.1.0, which you should upgrade to. Read about it here: https://github.com/FormidableLabs/simple-console#noop-logger

Noop Logger
There are some cases where you will want to conditionally silence the logger.
You can do this by passing null as the target parameter to the logger like:
var con = new SimpleConsole({ noop: true });
con.log("Hello world!"); // => Should _not_ output anything.

This is usually useful in a case where you build different capabilities based
on some external information, for example, React-style, this could be
something like:
var con = new SimpleConsole({
  noop: process.env.NODE_ENV === "production"
});

con.log("Hello world!"); // => Should _not_ output anything in `production`.

@kenwheeler -- Ugh just realize the docs are wrong :/ Fixing that...


Allow setting global args in SB 6.5+

Fixes https://github.com/storybookjs/builder-vite/issues/395.
This is a little bit tricky to do in a way that supports storybook 6.4 and 6.5.  I've used a dynamic import() and a top-level await, in order to wrap the import of the new methods in a try/catch.  This has decent browser support, but is not universal.  Curious if anyone else has another idea.
I've added example global args in the react and react-ts examples, to show both story store V6 and V7 support.  You can simulate storybook 6.4 by changing the destructured imports to addArgsZ and addArgTypesZ, building, and starting an example.  You shouldn't see the control, and there shouldn't be any console errors.

We got failures in some of the example builds (strangely, not all of them).

ERROR: Top-level await is not available in the configured target environment ("chrome87", "edge88", "es2019", "firefox78", "safari13.1")

Should we update our browser support?  Or, maybe I need to wrap the whole thing in an async IIFE?

Hmm 86% supported globally seems fine to me. I don't have a strong preference either way

Would something like this work:
 import * as clientApi from "@storybook/client-api";
const {
  addDecorator,
  addParameters,
  addLoader,
  addArgTypesEnhancer,
  addArgsEnhancer,
  setGlobalRender,
} = clientApi;

  case "args": {
    if (typeof clientApi.addArgs !== "undefined") {
      return clientApi.addArgs(value);
    } else {
      return logger.warn(
        "Could not add global args. Please open an issue in storybookjs/builder-vite."
      );
    }
  }
  case "argTypes": {
    if (typeof clientApi.addArgTypes !== "undefined") {
      return clientApi.addArgTypes(value);
    } else {
      return logger.warn(
        "Could not add global argTypes. Please open an issue in storybookjs/builder-vite."
      );
    }
  }

Brilliant, that works great.  I tested with storybook 6.4 and 6.5, and it behaves correctly, although react is yelling about trying to set globalArg as a prop...

@joshwooding this is ready for another review whenever you've got some time.


Track the retry duration alongside the attempts

Return the timeElapsed each time retryWhen.action is called
this allowed the provision of a maxDuration parameter to the RetryPolicy.fixedInterval, which is useful for cases where you want to stop retries after a specific amount of time has elapsed.

I don’t think it’s necessary to do this.
Providing a max attempt here is synonymous to proving a maxDuration for a fixedIntervalPolicy.
maxDuration = maxAttempts * interval
having a timer within retryWhen doesn’t really provide much benefits as we can always work with the attempts.
For other retryPolicies where the delay can be really dynamic, they can be configured by passing a maxDelay.
so I think attempts is generally easier to reason about and depend on.


The Azure JavaScript-STT-SDK works well on PC, but it does not work on mobile phones.

Why is JavaScript STT-SDK from a default microphone just for PC, but not for mobile phones?
We use this const audioConfig = AudioConfig.fromDefaultMicrophoneInput().
//code
speech() {
let that = this;
const speechConfig = SpeechConfig.fromSubscription(
"",
""
);
speechConfig.speechRecognitionLanguage = "zh-CN";
const audioConfig = AudioConfig.fromDefaultMicrophoneInput();
const recognizer = new SpeechRecognizer(speechConfig, audioConfig);
recognizer.start;
recognizer.recognizeOnceAsync(result => {
switch (result.reason) {
case ResultReason.RecognizedSpeech:
console.log(RECOGNIZED: Text=${result.text});
that.inputMsg = result.text;
console.log("    Intent not recognized.");
break;
case ResultReason.NoMatch:
console.log("NOMATCH: Speech could not be recognized.");
that.tts("没有听到您说话喔~");
break;
case ResultReason.Canceled:
const cancellation = CancellationDetails.fromResult(result);
console.log(CANCELED: Reason=${cancellation.reason});
if (cancellation.reason == CancellationReason.Error) {
console.log(CANCELED: ErrorCode=${cancellation.ErrorCode});
console.log(
CANCELED: ErrorDetails=${cancellation.errorDetails}
);
console.log("CANCELED: Did you update the subscription info?");
}
break;
}
});
},

The JavaScript SDK relies on getUserMedia to gain microphone access.
Some browsers don't support this on phone (Chrome and FireFox on iPhone are examples) and the SDK then has no Microphone access. (Safari does work on iPhone).
https://bugs.webkit.org/show_bug.cgi?id=208667 is the root cause for iOS.
What browser / phone combination are you using?

This problem has beem resloved by this method,
(JavaScript Language API)  void plus.speech.startRecognize( options, successCB, errorCB );
On the other hand, I face an another problem, when I test an app with the latest released version of the Microsoft Cognitive Services Speech SDK (1.12.0) on iOS devices.
(JavaScript Language API)  const audioConfig = AudioConfig.fromDefaultSpeakerOutput( );
And this function does not work on iOS devices.

I think this PR: https://github.com/microsoft/cognitive-services-speech-sdk-js/pull/183 fixes the speaker output on iOS.

Closing the issue as the questions were answered.


✨ fix: sometimes cluster1 or cluster2 kubeconfig context alias does not create on the first try

I have discovered that every so often that 1 of the cluster1 and cluster2 aliases in kubeconfig do not create propertly - I assume there is a blocking happening since both clusters are create simultaneously - to avoid this I added a retry for both clusters - not pretty, but necessary to avoid missed config

Summary
Related issue(s)
Fixes #

issue still occurring - looking at another possible way to correct behavior

issue still occurring - looking at another possible way to correct behavior

I put one in a thread above.
All that redirection to /dev/null makes it harder to even get a clue about what is going wrong.

Also, regarding even noticing problems, note that & defeats set -e.
bash-3.2$ set -e
bash-3.2$ false & true
[1] 14497
bash-3.2$
[1]+  Exit 1                  false
bash-3.2$ jobs
bash-3.2$

ready for review

@MikeSpreitzer good find on the simpler grep. I updated. I left in the 'just in case context did not get renamed' bit because it is still a possibility. It can be removed, but then you're wasting your time waiting for the script to complete

@clubanderson, what do you mean about waiting?

It can be removed, but then you're wasting your time waiting for the script to complete

If you are referring to the wait command that is now on line 121 (after the "done" of the bash loop), that is needed even if there is no checking and retry of the renaming. The wait is needed regardless of retry, to make the first tries to rename follow the completion of the kind create commands.

For later work:

I left in the 'just in case context did not get renamed' bit because it is still a possibility.

Is that something you observed with this script? I understand the need when the context renamings were done concurrently with other cluster creations and context renamings, but I would be surprised if the context renamings could fail now that they are totally ordered wrt each other and other kubeconfig manipulations.


Storybook Components: Navbar/Navbar stories have a broken logo.

The logo displayed in the story has a broken link, we could use the "ACME" logo

storybook removed


loguru-logging-intercept: init at 0.1.4-unstable

Description of changes

Things done

Built on platform(s)

[X] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Thanks for changing!
Now, the commit msg and PR title could be 0.1.4

Result of nixpkgs-review run on x86_64-linux 1

4 packages built:

python311Packages.loguru-logging-intercept
python311Packages.loguru-logging-intercept.dist
python312Packages.loguru-logging-intercept
python312Packages.loguru-logging-intercept.dist


Typo "Visual Studio code"→"Visual Studio Code"

https://docs.microsoft.com/en-us/azure/logic-apps/quickstart-create-logic-apps-visual-studio-code

The typo fix looks good; verified. Thanks @hyoshioka0128


Support okhttp3.Response return type

During testing, calls are made to live/ready probes to obtain information about the state of the service under test. Different data (body/headers) are returned in different service states and it would be convenient to use raw okhttp3.Response instead of DualResponse <RawBody, RawBody>.
public interface ApiCli {

    @GET("/v2/example")
    @Headers({"Content-Type: application/json"})
    okhttp3.Response get();

}

Retrofit implementation restriction. See issue.
java.lang.IllegalArgumentException: 'okhttp3.Response' is not a valid response body type. Did you mean ResponseBody?
    for method JavaTypeAdapterFactoryClient.returnRawResponseType

	at retrofit2.Utils.methodError(Utils.java:54)
	at retrofit2.Utils.methodError(Utils.java:43)
	at retrofit2.HttpServiceMethod.parseAnnotations(HttpServiceMethod.java:70)
	at retrofit2.ServiceMethod.parseAnnotations(ServiceMethod.java:39)
	at retrofit2.Retrofit.loadServiceMethod(Retrofit.java:202)
	at retrofit2.Retrofit$1.invoke(Retrofit.java:160)
	at com.sun.proxy.$Proxy28.returnRawResponseType(Unknown Source)


Remove Mergeable and rename Unique to Persistent

xdr, env, and sdk changes are done. Only one left is core.


Page up and Page down buttons only work intermittently - Perhaps Firefox specific

What version of Music Assistant has the issue?
2.3.0b20
What version of the Home Assistant Integration have you got installed?
2024.8.1
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?

[X] Yes

The problem
When scrolling through screens with lots of info requiring scrolling, the page up and page down buttons don't work.  While I will say it is intermittent as they worked for my one time, I could not product it after that.  So on my computer I have to scroll with the mouse wheel or use the scroll bar.  However on some searches, such as in a search within browsing with Radio Browser, searching by popularity for instance, the scroll bar is sort of useless and the scroll wheel would take you hundreds of turns to get to the bottom of the list.
How to reproduce
It may be Firefox specific.  I tried it in Chrome just now (under Linux Mint) and while I never use Chrome, the scrolling worked.  But that was hardly a test with a sample size of 1.
Music Providers
Tidal
Local NAS
Tunein
Radio browser
Player Providers
Sonos
Full log output
Log.txt
Additional information
No response
What version of Home Assistant Core are your running
2024.8.3
What type of installation are you running?
Home Assistant OS
On what type of hardware are you running?
Generic x86-64 (e.g. Intel NUC)

Could well be a Firefox issue as we have seen multiple inconsistencies with that as well as safari

I just tried Chrome and Edge and it worked fine. Not sure if this will be able to be addressed. Solutions at this time are to use the search function or a different browser

Unfortunately the dev team don’t have the capacity to deal with browser specific issues. This will be left open however in case a member of the community wants to look into it. It is possible that Firefox or Vuetify updates also fix this. Please close this if it comes good.


Use of WikiPage::getRevision was deprecated in MediaWiki 1.35.

In some cases, you should just be fine with updating getRevision calls with getRevisionRecord, but this may not work for situations where you use getPrevious, as this method does not exist in the RevisionRecord class.

This has been resolved by pull #84, but it still needs to be merged :(
In the meantime you can apply the patch manually

Merged!


New Project won't run since 1.0.0-rc.13

Environment
macOS Mojave 10.14.4
node v8.15.0
yarn v1.13.0
Description
New project fails with this in the iOS Simulator:
Unhandled JS Exception: Attempted to assign to readonly property.

eval code
eval@[native code]
eval code
eval@[native code]
./node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:3528:5
__webpack_require__@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:724:34
fn@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:101:39

eval code
eval@[native code]
eval code
eval@[native code]
./node_modules/react-native/Libraries/BatchedBridge/BatchedBridge.js@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:3515:5
__webpack_require__@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:724:34
fn@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:101:39

eval code
eval@[native code]
eval code
eval@[native code]
./node_modules/react-native/Libraries/BatchedBridge/NativeModules.js@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:3541:5
__webpack_require__@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:724:34
fn@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:101:39

eval code
eval@[native code]
eval code
eval@[native code]
./node_modules/react-native/Libraries/Core/ReactNativeVersionCheck.js@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:4668:5
__webpack_require__@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:724:34
fn@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:101:39
eval code
eval@[native code]
eval code
eval@[native code]
./node_modules/react-native/Libraries/Core/checkNativeVersion.js@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:4694:5
__webpack_require__@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:724:34
fn@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:101:39

eval code
eval@[native code]
eval code
eval@[native code]
./node_modules/react-native/Libraries/Core/InitializeCore.js@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:4643:5
__webpack_require__@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:724:34
fn@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:101:39
eval code
eval@[native code]
http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:7590:5
__webpack_require__@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:724:34
http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:791:37
global code@http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:792:12

./node_modules/react-native/Libraries/BatchedBridge/MessageQueue.js
    index.bundle?platform=ios&dev=true&minify=false:3528:5
__webpack_require__
    index.bundle?platform=ios&dev=true&minify=false:724:34
fn
    index.bundle?platform=ios&dev=true&minify=false:101:39
./node_modules/react-native/Libraries/BatchedBridge/BatchedBridge.js
    index.bundle?platform=ios&dev=true&minify=false:3515:5
__webpack_require__
    index.bundle?platform=ios&dev=true&minify=false:724:34
fn
    index.bundle?platform=ios&dev=true&minify=false:101:39
./node_modules/react-native/Libraries/BatchedBridge/NativeModules.js
    index.bundle?platform=ios&dev=true&minify=false:3541:5
__webpack_require__
    index.bundle?platform=ios&dev=true&minify=false:724:34
fn
    index.bundle?platform=ios&dev=true&minify=false:101:39
./node_modules/react-native/Libraries/Core/ReactNativeVersionCheck.js
    index.bundle?platform=ios&dev=true&minify=false:4668:5
__webpack_require__
    index.bundle?platform=ios&dev=true&minify=false:724:34
fn
    index.bundle?platform=ios&dev=true&minify=false:101:39
./node_modules/react-native/Libraries/Core/checkNativeVersion.js
    index.bundle?platform=ios&dev=true&minify=false:4694:5
__webpack_require__
    index.bundle?platform=ios&dev=true&minify=false:724:34
fn
    index.bundle?platform=ios&dev=true&minify=false:101:39
./node_modules/react-native/Libraries/Core/InitializeCore.js
    index.bundle?platform=ios&dev=true&minify=false:4643:5
__webpack_require__
    index.bundle?platform=ios&dev=true&minify=false:724:34
fn
    index.bundle?platform=ios&dev=true&minify=false:101:39
__webpack_require__
    index.bundle?platform=ios&dev=true&minify=false:724:34
global code
    index.bundle?platform=ios&dev=true&minify=false:792:12

If Remote JS Debugging is on this is the error shown in the Simulator:
Uncaught TypeError: Cannot assign to read only property 'exports' of object '#<Object>'

RCTFatal
__28-[RCTCxxBridge handleError:]_block_invoke
_dispatch_call_block_and_release
_dispatch_client_callout
_dispatch_main_queue_callback_4CF
__CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__
__CFRunLoopRun
CFRunLoopRunSpecific
GSEventRunModal
UIApplicationMain
main
start

Seeing as 1.0.0-rc.12 works, the issue must be related to this commit as it's the only change from 1.0.0-rc.12 to 1.0.0-rc.13: https://github.com/callstack/haul/commit/87ad54a1ba3d897cd80e4d425d2e962bbbdc6f81
Also when starting a new project the following errors occur but can be fixed by yarn add -D react-hot-loader react-dom (see also #532):
Module not found: Error: Can't resolve 'react-dom' in '.../MyProject/node_modules/haul/node_modules/react-hot-loader/dist'
Module not found: Error: Can't resolve 'react-hot-loader' in '.../MyProject'

One more thing. I'm seeing these warnings repeated from the yarn haul start --platform ios command. I've no idea where these are coming from.
WARNING: We noticed you're using the `useBuiltIns` option without declaring a core-js version. Currently, we assume version 2.x when no version is passed. Since this default version will likely change in future versions of Babel, we recommend explicitly setting the core-js version you are using via the `corejs` option.

You should also be sure that the version you pass to the `corejs` option matches the version specified in your `package.json`'s `dependencies` section. If it doesn't, you need to run one of the following commands:

  npm install --save core-js@2    npm install --save core-js@3
  yarn add core-js@2              yarn add core-js@3

Reproducible Demo

Bootstrap new project:
react-native init MyProject
cd MyProject
yarn add -D haul
yarn haul init
yarn haul start -- --platform ios
react-native run-ios

Add missing packages:
yarn add -D react-hot-loader react-dom

Try again:
yarn haul start -- --platform ios

Unhandled JS Exception: Attempted to assign to readonly property.

package.json:
{
  "name": "MyProject",
  "version": "0.0.1",
  "private": true,
  "scripts": {
    "start": "node node_modules/react-native/local-cli/cli.js start",
    "test": "jest",
    "haul": "haul"
  },
  "dependencies": {
    "react": "16.8.3",
    "react-native": "0.59.4"
  },
  "devDependencies": {
    "@babel/core": "^7.4.3",
    "@babel/runtime": "^7.4.3",
    "babel-jest": "^24.7.1",
    "haul": "^1.0.0-rc.15",
    "jest": "^24.7.1",
    "metro-react-native-babel-preset": "^0.53.1",
    "react-dom": "^16.8.6",
    "react-hot-loader": "^4.8.4",
    "react-test-renderer": "16.8.3"
  },
  "jest": {
    "preset": "react-native"
  }
}

AFAIK the issue is with @babel/runtime and it's transform which is adding ES imports instead of requrie which causes the error due to Webpack not allowing to mix CommonJS and ESM together. One of the solution is to pass enableBabelRuntime: false to metro-react-native-babel-preset. Here's a haul.config.js for that:
export default {
  webpack: env => {
    const config = createWebpackConfig({
      entry: './index.js',
    })(env);

    config.module.rules.some(rule => {
      if (rule.test && rule.test.source.includes('js')) {
        rule.use = [
          {
            loader: require.resolve('babel-loader'),
            options: {
              presets: [['module:metro-react-native-babel-preset', { enableBabelRuntime: false }]],
              plugins: [require.resolve('haul/src/utils/fixRequireIssues')],
            },
          },
        ];
        return true;
      }
    });
    return config;
  }
};

This didn't work for me. I still get the same error.

This did work for me in haul^1.0.0-rc.15.

two quick feedbacks:

I also had to yarn add -D react-hot-loader react-dom to make Haul work (bug in way dependencies are set for Haul? not sure 🤔)
Had to modify the haul config as wrote by @zamotany (thanks for sharing that btw!) - side question to that, can't we modify the metro.config.js file instead? 🤔 I tried but couldn't actually make it work tbh

@zamotany: What are the implications of disabling the Babel runtime? Can we add it to the default Babel config?

It turns out that the problem is not Babel runtime, but disableImportExportTransform: true which will not transform ES import/export. This is bad, since some files in RN JS source code have mixed both ES import/export and CommonJS in a single file, which is unsupported by Webpack - with Webpack you cannot mix ES import/export and CommonJS.
So we should revert that change. Also if you're running RN 0.59 please check next branch. We are doing some major refactoring there for RN 0.59 future versions (no backwards compatibility for older RN at this point).

That means we'll lose tree-shaking again. 😞
What is the implications of disabling the Babel runtime? In my testing, it seems to work just fine. If we disable disableImportExportTransform in Haul, we could just explicitly enable it with the Babel runtime disabled in our systems.
cc @acoates-ms

@tido64 yeah, but you loose tree shaking inly in your code and maybe other non-RN dependencies. Because of CommonJS in RN, it won't tree shake it. You can also submit PRs to RN to rewrite CJS to ESM.

Or you could disableImportExportTransform but you would need to apply commonjs transform for all files from RN

I also encountered this. Had some trouble patching configs for 1.0.0-rc.15, and it sounds like this hasn't been resolved yet...
So I downgraded to 1.0.0-rc.12, and can confirm this resolved my issue.

@zamotany solution works for me!

What combinations of versions actually worked for people? I've tried different permutations of<EMAIL_ADDRESS>and<EMAIL_ADDRESS>and all haul versions from rc.12 to rc.15 with a newly initialized RN project. Didn't get it to function, kept failing on the orginal post's error.
Also note: some configuration changes are rather specific to the structure of the underlying babel and webpack configs. There

I also have experienced this issue!

Hey there! I'm also running in to a similar issue.
I'm starting a new project using react-native 0.60.0 and trying to set it up with haul. When installing I ran in to the same problems in this thread.
After installing react-dom and react-hot-loader along with updating the haul config provided by @zamotany I am able to run the app, but only when JS remote debugging is running.
When it is turned off I get this error:

As well as a whole lot of 404 errors in the Haul logs

Is this a compatibility issue with Haul 1.0.0-rc.15 and react-native 0.60.0?
I've done up a quick repo with the setup here if that is useful. Cheers!

Hey @jkirkpatrick24 , I just ran into the same issue. I worked around it by installing and using the console.assert polyfill at the top of my entry point.

I'm stuck on this as well. React Native development has actually become more brittle lately. Flutter is so much easier and just works.

For anyone running RN 0.59 or 0.60, please check the revamped version of Haul on next branch - it's much more stable. The haul package will become deprecated soon.
Here's what you have to do in order to migrate:

Back up your haul.config.js and babel.config.js
Remove haul package
Install @haul-bundler/cli and @haul-bundler/preset-0.59 for RN 0.59 or @haul-bundler/preset-0.60 for RN 0.60
Run haul init command -> this will create new config and babel.config.js will now have @haul-bundler/babel-preset-react-native preset tweaked for RN 0.59+
Integrate Webpack config modifications from old config in new config using transform function.

If anyone is having this issue please use @haul-bundler/cli (if not already using) and feel free to open a new issue or reopen this one.

@zamotany That link fails now. I'm guessing you mean https://github.com/callstack/haul/blob/master/docs/Configuration.md#customize-webpack-config?

@JofBigHealth yes https://github.com/callstack/haul/blob/master/docs/Configuration.md#customize-webpack-config


Consider propagating upper bounds backwards

Now that upper bounds are getting to be commonplace, it may be worth contemplating propagating the bounds to earlier versions. I am aware that this is scary, but so is not doing it: https://github.com/JuliaGraphics/ColorTypes.jl/pull/143

Have you seen https://github.com/bcbi/RetroCap.jl?

Personally, I believe that we should add upper bounds to the earlier versions of our packages in the registry. But I don’t think that currently there is a lot of support for this plan.
In the meantime, you can use RetroCap to do it for all packages in one or more GitHub orgs.

Looks like RetroCap will do the job for us, definitely a star-worthy package!
I am traveling for the next couple of days so will wait to tackle this until I can deal with any fallout :smile: .


Does this generate cpp files?

Hello, I am really bad with IO and I was wondering if you had implemented a way to generate CPP files with a appropriate header file. This would solve alot of issues that keep the sdk from being included in multiple files

The SDK gets generated with CPP and HPP files, If you don't need some functions just don't compile the cpp files. See the bottom part of the readme.

Also, do you know anything about the difference between call function and processevent? Im currently hooked into process event with my feckless sdk for rocket league and about 25% game called functions  are routed through process event where i can inspect the called ufunction. I think the rest are using call function, do you kniw anything about this?

No, but then they are just normal functions and the generator can't access them.

Alright, well thank you for the help. If i send you the reversed classes for rocket league, will you add them?

Just create a pull request


Add public random function

Is your feature request related to a problem? Please describe.
Having a public random generation function is pretty useful
Describe the solution you'd like
As we have seedrandom function already inside the crypto package a sufficiently secure random generator for strings and number can be built

done


[v4.y] Load cluster ca certificates using OpenSSL::X509::Store#add_file

Backporting #461 (which fixed #460) + tests.

@jperville @DocX I'm backporting the add_file fix here which will allow me to finally release it (sorry for huge delay).
Added tests and CI keeps failing on Mac — any idea if add_file might behave differently by OS?

Oops, maybe the Mac angle was my mistake.
The cert I put in middle of concatenated-ca.pem didn't match the existing certs, so it failed rake test.  OTOH linux doesn't run rake test on existing certs, it only runs tests inside
test/config/update_certs_k0s.rb which regenerates all certs consistently, therefore it passed.
I'm changing CI to complete all tests when one errors to get clearer picture => :tada: mac passed.
(windows — which I never tried in CI before — failed to install gems, I'll split that to separate PR/issue)
Still not handling certificate-authority-data.  OK, I'll document and release soon the partial fix — better than nothing.


feat: implement async sync with unasync-cli

Run command unasync postgrest_py tests to generate synchronous code and tests version
Fix #27
This PR does not use inheritance so the code is clearer
Pros: more readable code
Cons: largest library
I did another PR with using inheritance so that you accept the alternative that seems best to you: #29

@leynier Thank you!
Inheritance is the better way to go for the long term, but well it's just optimization. This PR is big already, we should do that in a separate PR. Furthermore, could you please add the generated code in a separate commit, for me to review more easily?

@leynier Thank you! Inheritance is the better way to go for the long term, but well it's just optimization. This PR is big already, we should do that in a separate PR. Furthermore, could you please add the generated code in a separate commit, for me to review more easily?

Ok, I will do

@lqmanh Done ✅

Hi @lqmanh, can you approve running workflows?

Approved

Hi @lqmanh, can you approve running workflows?

Sorry for the mess with lock file

@lqmanh ready to review :slightly_smiling_face:

Nice work. Thank you for your contribution.


Dev/db

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 100.00%. Comparing base (aa49ba5) to head (321c126).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@             Coverage Diff             @@
##           master       #26      +/-   ##
===========================================
+ Coverage   99.37%   100.00%   +0.62%
===========================================
  Files          24        23       -1
  Lines        1290      1263      -27
===========================================
- Hits         1282      1263      -19
+ Misses          8         0       -8

Flag
Coverage Δ

unittests
100.00% <100.00%> (+0.62%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Recursive function calls using set strategy and a repositoryMethod

See https://github.com/rubenrua/mongodb-odm/commit/ba8d02412e063e0ad5362e2d404f5df5b1e4d1bb

Added a test and a possible fix in the pull request #1221.

Let's keep discussion (if there'll be one in #1221)


k3s-selinux support for SLE Micro and openSUSE MicroOS

Related to #8 but different, as both SLE Micro and openSUSE MicroOS have both container-selinux and selinux-policy-targeted packages
Both distributions would like to enable SELinux by default, but installing k3s is a common use case by those users and customers already, and are currently hindered by the lack of a k3s-selinux package.
Please can SLE Micro (based on SLE 15 SP2) and openSUSE MicroOS (based on openSUSE Tumbleweed) k3s-selinux packages be brewed, with the above dependencies?
Once that exists changes to install.sh will be needed to use more appropriate commands than yum install, but meanwhile https://github.com/k3s-io/k3s/pull/3088 has been submitted to stop SUSE/openSUSE users trying to make things worse with the current error messages.

Sorry for abusing this issue, but I started to build a package for this in the openSUSE Build Service:
https://build.opensuse.org/package/show/home:ojkastl_buildservice:Branch_devel_kubic/k3s-selinux
I noticed that the k3s.if file is empty in the latest stable release v0.5.latest.1, so I added the latest one from commit 7b982cf
@sysrich SR to devel:kubic is here.


Zoom FSInteractiveMapView

i have implemented the MapView in swift now i want that map view to zoom in and out ... Any help!

Just put it in a UIScrollView with zoom enabled.

bro when i zoom in it states are not clickable. any solution please


Read in ak, bk coefficients

Purpose
The ak and bk coefficients  required to compute the pressure levels are hard-coded in the eta module for  km=71, km=72, km=91, and km=139  number of vertical levels.  This limits the number of vertical levels a user can choose to run models.   By allowing the users to provide the ak and bk values in a simple ASCII file,  the users have the freedom to specify any number of vertical levels.
Code changes:
In this PR,

The hard-coded ak and bk array values have been removed.  Instead, these values are read in, for example, from the input/eta79.txt file where the input directory is expected to reside in the directory of the main program and 79 represents the value of km.  Checks were put in place to ensure that

the size of the ak and bk arrays are equal to the specified value of km
the  resulting values of eta and eta_vare monotonically increasing

Existing unit tests have been modified to read in the coefficients from an eta file and new unit tests were created to test the modified eta module.  These tests were modified under the assumption that in the future, all input files will reside in one main input directory where the input directory resides in the directory of the main program.  This assumption required creating input directories to all the possible testing directories in tests.

Lastly,  the functions vertical_coordinate and compute_eta, originally located in the baroclinic_jablonowski_williamson module have been moved to a newly created util module in the pace/util/grid directory.  This change was made because it seemed more fitting for the abovementioned functions to reside with other grid-related functions.

Requirements changes:

This PR requires an input directory with eta files named as eta##.txt where ## refers to the value of km

Checklist
Before submitting this PR, please make sure:

[x] You have followed the coding standards guidelines established at Code Review Checklist.
[x] Docstrings and type hints are added to new and updated routines, as appropriate
[x] All relevant documentation has been updated or added (e.g. README, CONTRIBUTING docs)
[x] For each public change and fix in pace-util, HISTORY has been updated
[x] Unit tests are added or updated for non-stencil code changes

Additionally, if this PR contains code authored by new contributors:

[ ] The names of all the new contributors have been added to CONTRIBUTORS.md

Hi @mlee03 . Glad that you could clean up the predefined vertical levels, which is getting to be a real mess. I agree that the best place for creating the vertical levels is in the preprocessor.
One concern (not related to this commit) is that there is no foolproof way to automatically generate a good set of ak/bk levels, and when creating an entirely novel set of levels some degree of hand-tuning is necessary to avoid stability problems. Xi Chen had developed a tool which can help, and interpolating from predefined level sets is usually pretty good, but some user discretion is needed when making new level sets.
NB: @bensonr @oelbert In the future when I have broader comments like this, is there somewhere more appropriate to bring them up than in the comments of a semi-related PR? Thanks.

@lharris4: There's no way to auto-generate stable levels, but is there a way to check that they are unstable? We could eventually code that in.

@FlorianDeconinck there is no a priori way to ensure stability but typically we can examine the differences in delp and delz in a variety of situations, which is what Xi's tool does. We could run tests to ensure that the differences do not exceed some tolerance. This might be a good way forward; furthermore smoothing can be applied to improve the smoothness and stability of the selected coordinate.

Logged for posterity: #38
On the other topic, though obviously I am but a stranger here, I shall remind that there's a "Discussion" system on Github, which is a wiki-liky structure and could accommodate ongoing discussions and/or thinking on feature sets.

@FlorianDeconinck thanks for logging that. Also the discussions could potentially be a great resource. There are a precious few discussions on the FV3 repo and I would like to see this functionality used more.

Please add your name to CONTRIBUTORS.md

@oelbert @bensonr ready for another round of reviews :crossed_fingers:

@mlee03 - can you or one of the other reviewers discuss the necessity of the empty init.py file in the _tests/main/grid/_directory

@bensonr, good point, to my limited understanding, I don't think it's needed here since we're not creating a package and the test is not being referenced by any modules.  I think I created it here because there was one is the tests/main/driver directory :grin: :grin: :grin: but I will remove it

@mlee03 - is there a procedure for creating the ak/bk netcdf files and is it documented anywhere?

I took the ak/bk coefficients from what was coded in the original version of the eta module and created a python script to generate the netcdf files.  I can document how to use the python netcdf module or the xarray module to create these files.  Where should it be documented?

Or a Jupyter notebook?


[doc] Doc of debug data preview update

Purpose of the pull request

Doc of debug data preview update, mainly about the feature https://github.com/DataLinkDC/dinky/issues/3893
Brief change log

Verify this pull request

This pull request is code cleanup without any test coverage.
(or)
This pull request is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:

hi @MactavishCui   Is there anything  need to add to this PR? If not, please Ready for review


Place text on top parallax image

How to add or place text on top center the image?

Please try wrap your <img class=thumbnail ... > inside  and parallax won’t work
Because w3-container has position: relative

I want place your parallax image inside a div container and place multi text or div on top your parallax img

 some text
I tried above and parallax wont work

https://codepen.io/anon/pen/PdrNoy

I checked your codepen.. if i change to other parallax effect like orientation.. your parallax cannot work..

The wrong cdn version was loaded.. I updated the readme and the codepen. It should work fine now.

The offset is miscalculated because of this relative parent indeed. I'll take a look.

Thanks.. will wait for your update soon!

https://github.com/geosenna/simpleParallax/releases/tag/3.1.1

Hi! Have you updated your codepen too?

yes

I close this ticket, as I assume the issue has been fixed.


Add DPG: Angaza Elimu

Automatic addition of a new digital public good submitted through the online form available at https://digitalpublicgoods.net/submission

Angaza Elimu needs to clarify the following indicators before we can proceed with the review:

[x] Clear Ownership
[x] Platform Independence
[ ] Documentation
[x] Mechanism for Extracting Data and Content
[x] Adherence to Privacy and Applicable Laws
[x] Adherence to Standards & Best Practices
[ ] Do No Harm By Design
[ ] Data Privacy & Security
[ ] Inappropriate & Illegal Content.
[ ] Protection from harassment.

I will contact the person who made the submission and will update once they come through.

Digital solutions that are no longer active, or do not provide the required documentation needed for review, will be removed from the DPG Registry as per the archiving policy.


feat: add stop option to detect

Description
This PR adds a new stop option to detect and detectSync. This will allow us to stop traversing directories when a certain directory is hit.

Linked Issues
N/A
Additional context

N/A

What is the motivation for this?


DRAFT Initial workflow

on-going draft of initial workflow of one commands.
Signed-off-by: SaeHie Park<EMAIL_ADDRESS>

For #5

close as initial workflow is now working


Use d435 on linux，The usb is not recognized

Required Info

Camera Model
D435i

Firmware Version

Operating System & Version
Ubuntu18.04

Kernel Version (Linux Only)

Platform
PC

SDK Version

Language
python }

Segment

Issue Description
I know when i want to use d435i on linux ,I need get the access,but Linux doesn't recognize my d435..

Hi @EthanUNC  Are you using the camera with the official 1 meter USB cable supplied with it or a cable of your own choice, please?
Has the camera worked previously or has it not been able to be detected since your purchased it?
If it has worked previously, do you know which firmware driver version is currently installed in the camera?

@MartyG-RealSense  Using the official 1 meter usb cable.and i have run the 3d point cloud example on pycharm successfully.I download the sdk2.0.But i have not downlaod any other driver. I using the official 1 meter usb cable.and i have run the 3d point cloud example on pycharm successfully.I download the sdk2.0.But i have not downlaod any other driver.

Is the camera detected if you install the SDK using the libuvc backend build script at the link below, please?
https://github.com/IntelRealSense/librealsense/blob/master/doc/libuvc_installation.md

@MartyG-RealSense thanks for your reply!it is solved now.

You are very welcome, @EthanUNC - I'm pleased to hear that it worked for you.  Thanks very much for the update!