Firedrake TS import fails when used in Firedrake 2024-12 and latest Docker Hub image

Hello here!
I recently run into a problem with the 2024-12 tagged Docker Hub release of the Firedrake image. It doesn't work with the latest master commit<PHONE_NUMBER>ff7ce04b80bc15c02f91f35c0ba476 of the Firedrake TS package here.
The exact steps to reproduce the issue are below. Here's the stack trace I'm getting:
>>> import firedrake_ts
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/firedrake/firedrake/lib/python3.12/site-packages/firedrake_ts/__init__.py", line 1, in <module>
    from .ts_solver import DAEProblem, DAESolver
  File "/home/firedrake/firedrake/lib/python3.12/site-packages/firedrake_ts/ts_solver.py", line 10, in <module>
    from firedrake_ts.solving_utils import check_ts_convergence, _TSContext
  File "/home/firedrake/firedrake/lib/python3.12/site-packages/firedrake_ts/solving_utils.py", line 6, in <module>
    from firedrake_configuration import get_config
ModuleNotFoundError: No module named 'firedrake_configuration'

From a quick look it seems like the firedrake_configuration package was removed and is not longer around. Firedrake project is in some kind of a transition towards being pip-installable.

Steps to reproduce the failure
First step is to pull and run the "official" Firedrake image from Docker Hub:
$> docker pull firedrakeproject/firedrake:2024-12
2024-12: Pulling from firedrakeproject/firedrake
Digest: sha256:5b11ae36694ec087d750e77d71b92d6504550bbf83c3d8b28ed2a05a3fd2ee26
Status: Image is up to date for firedrakeproject/firedrake:2024-12
docker.io/firedrakeproject/firedrake:2024-12

$> docker run -it firedrakeproject/firedrake:2024-12
To run a command as administrator (user "root"), use "sudo <command>".
See "man sudo_root" for details.
firedrake@b00812a5f8df:~$

After starting the container one needs to fix a small issue where the Firedrake image can't import itself 🫨 because it's not in the venv Python path. This of course brings out the question of how they actually test their releases, but that's a story for another (rainy) day. Afterwards it's possible to activate the virtual environemnt baked into the image and install the latest commit of firedrake_ts through pip.
Once all that is done import firedrake_ts fails with the weird import error mentioned above.
firedrake@b00812a5f8df:~$ export PYTHONPATH=/home/firedrake/firedrake/src/firedrake

firedrake@b00812a5f8df:~$ source firedrake/bin/activate

(firedrake) firedrake@b00812a5f8df:~$ pip install git+https://github.com/IvanYashchuk/firedrake-ts.git@1186966053ff7ce04b80bc15c02f91f35c0ba476#egg=firedrake_ts
Collecting firedrake_ts
  Cloning https://github.com/IvanYashchuk/firedrake-ts.git (to revision<PHONE_NUMBER>ff7ce04b80bc15c02f91f35c0ba476) to /tmp/pip-install-2y05weg7/firedrake-ts_0cb92f1b4e66409ba4a1f48a58cff3c0
  Running command git clone --filter=blob:none --quiet https://github.com/IvanYashchuk/firedrake-ts.git /tmp/pip-install-2y05weg7/firedrake-ts_0cb92f1b4e66409ba4a1f48a58cff3c0
  Running command git rev-parse -q --verify 'sha^1186966053ff7ce04b80bc15c02f91f35c0ba476'
  Running command git fetch -q https://github.com/IvanYashchuk/firedrake-ts.git<PHONE_NUMBER>ff7ce04b80bc15c02f91f35c0ba476
  Resolved https://github.com/IvanYashchuk/firedrake-ts.git to commit<PHONE_NUMBER>ff7ce04b80bc15c02f91f35c0ba476
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
  Preparing metadata (pyproject.toml) ... done
Building wheels for collected packages: firedrake_ts
  Building wheel for firedrake_ts (pyproject.toml) ... done
  Created wheel for firedrake_ts: filename=firedrake_ts-0.2-py3-none-any.whl size=11086 sha256=f5170e021b73c160b134a473666dde8e4c6605f54dafb12101dd0c0287b3a11e
  Stored in directory: /home/firedrake/.cache/pip/wheels/1f/8e/fe/338987c0df2e413adf3075c50dbb27dceca22cccc51c88598d
Successfully built firedrake_ts
Installing collected packages: firedrake_ts
Successfully installed firedrake_ts-0.2

(firedrake) firedrake@b00812a5f8df:~$ python
Python 3.12.3 (main, Nov  6 2024, 18:32:19) [GCC 13.2.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import firedrake_ts
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/firedrake/firedrake/lib/python3.12/site-packages/firedrake_ts/__init__.py", line 1, in <module>
    from .ts_solver import DAEProblem, DAESolver
  File "/home/firedrake/firedrake/lib/python3.12/site-packages/firedrake_ts/ts_solver.py", line 10, in <module>
    from firedrake_ts.solving_utils import check_ts_convergence, _TSContext
  File "/home/firedrake/firedrake/lib/python3.12/site-packages/firedrake_ts/solving_utils.py", line 6, in <module>
    from firedrake_configuration import get_config
ModuleNotFoundError: No module named 'firedrake_configuration'

I was traveling and noticed this issue too late. It's great that you were able to figure out the fix. Thank you!
(fixed in https://github.com/IvanYashchuk/firedrake-ts/pull/24)


Added a test for issue #50

Issue: Simulation can make environment create new inputs to update its own inputs with, based on the number of inputs individuals have
We forgot one yesterday!

[the checks not passing is normal, this is very much based on a WIP to put the input in simulation, but basically you can just look at the test]


Changes to templates do not restart services.

Changes to templates do not trigger service restarts. Eg; if I'm changing socket permissions to the fpm pool, fpm needs to be restarted for those changes to take effect. Many of the templates could either notify the service, or the service need to subscript to a template.

Bite by this again.


Fixed #25354 -- Added class/app_label interpolation

Can you reuse existing test models instead of defining new ones? Your suggested approach requires the creation of 4 additional tables.

buildbot, add to whitelist.

Test placement in model_inheritance seems a bit odd -- not sure what this has to do with model inheritance other than I see you adapted a nearby test. Maybe it's fine.

Any documentation additions needed? At least a mention in the 1.10 release notes is appropriate.

It looked to me that the tests for app_label/class interpolation for related_name were in model_inheritance so it made sense to me for tests for related_query_name to live there as well. If I'm mistaken and someplace else looks better, please let me know.
I added a mention for the 1.10 release notes. Not sure if there needs to be a mention someplace else.

I think the place to mention would be ref/models/fields.txt:.. attribute:: ForeignKey.related_query_name. I guess the existing behavior should be documented for related_name too? Feel free to do it as a separate commit if you are willing and able.

I've added a note for related_query_name. Currently, the existing behavior for related_name is kinda documented. It's just on the page about models topics/db/models.txt:.. _abstract-related-name.

I think it would make sense to change the existing section to "Be careful with related_name and related_query_name" and edit as appropriate. You'll need to add:
.. versionchanged:: 1.10

   Interpolation of  ``'%(app_label)s'`` and ``'%(class)s'`` for ``related_query_name`` was added.

at the bottom of that section. You can squash your commits at this point.

Commits squashed. I think that should do it.

Comments addressed and resquashed.

merged in f05722a08a11b2e6c6c9acdf2bacd6a6128ccbb0, thanks!


Enable users to confirm their own place

Since StudentHack 2020 will be held online, participants are no longer required to fill in the application form.
This pull request means that new users will not be greeted with the application form - they just need to sign up to the StudentHack 2020 website and click a button to confirm their place in the Hackathon.

Codecov Report

Merging #39 into sh2020 will decrease coverage by 1.24%.
The diff coverage is 8.33%.

@@            Coverage Diff             @@
##           sh2020      #39      +/-   ##
==========================================
- Coverage   59.22%   57.97%   -1.25%
==========================================
  Files          44       44
  Lines         954      978      +24
  Branches       99      100       +1
==========================================
+ Hits          565      567       +2
- Misses        370      392      +22
  Partials       19       19

Impacted Files
Coverage Δ

src/controllers/applicationController.ts
31.95% <4.34%> (-8.59%)
:arrow_down:

src/routes/applicationRouter.ts
76.59% <100.00%> (+0.50%)
:arrow_up:

Continue to review full report at Codecov.

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


Custom api urls not working in docker-compose

Because douma-app gets built as part of creating the image. The urls for the api are already set.
Setting them in the docker-compose.yml file doesn't change anything.

Doesn't work:
environment:
	- CUSTOM_PRODUCTION_API_URL=http://${API_URL}
	- CUSTOM_STAGING_API_URL=http://${API_URL}

Solution seems to be replacing
RUN npm run build

with
CMD ["npm", "run", "build"]

Then it only builds when actually deploying the app.

Use ONBUILD command in Dockerfile


Modified to support Weblogic JMX

Thank you for providing such a great module.
While I was trying to use your module for Weblogic Server MBeans with JMX using t3 protocol, I fount that it must use different protocolProvider, and some of libraries from Oracle.
I'm not sure if this change is against your philosophy, but I decided to do a pull request for the reference to someone, who might have same problem as me.
Again, thanks a lot for providing a great module.

Hi @juhgiyo,
Wow! thanks for your PR, I'm really interested in merging it :smiley:
But I think it would be good to improve some issues before:

Fix coverage: tests are missing (See the coveralls report).
Duplicated code: I think the waiting logic should be refactored to its own function. MBeanServerConnection#connect function is getting too big.
I'm not sure about this, do you think including wlclient.jar (472KB) in the module is a good idea? Maybe we can document that is required to download it manually.

It's OK if you do not have time for this now. I'll leave this PR open whatever time it takes.


FastImage support for CameraRoll images is really needed. Instructions needed for enabling with SDWebImagePhotosPlugin

Describe the bug
Spent the majority of my day trying to get FastImage to support a ph:/// that RN gives you a URI to when calling getPhotos() from the CameraRoll library.
There are a few open and closed issues saying this is fairly simply solved by adding the 'SDWebImagePhotosPlugin' plugin. That is much easier said than done. After hours of trying I've given up for now because I cannot get past the build error module 'SDWebImage' not found.
There may be more errors that occur after that but I wasn't able to see them. I understand the rationale for not including it in the main package, that's fine. But I think just telling people to install a new pod that simply doesn't work out of the box isn't acceptable either. I imagine a great deal of use cases for FastImage is displaying images from a CameraRoll.
To Reproduce
Steps to reproduce the behavior if possible, or a link to a reproduction repo:

Add pod 'SDWebImagePhotosPlugin'
Run pod install
Try to build and see the aforementioned error.

Expected behavior
Should compile.
I've tried lots of combination of modifying the podfile's header search paths etc to no avail. I guess that's all I am really asking for is someone who nows more about the XCode build process to propose an update to the READMe about how to enable this plugin. The instructions for installation on the main SDWebImagePhotosPlugin repo don't account for (at least I think so) for adding it as a dependency for an existing dependency in a project.  (RN Project -> Fast Image -> SDWebImage -> SDWebImagePhotosPlugin)
I really love this project and simply just wanna display CameraPhotos. Really appreciate the help!

I'm facing the same issue. The instructions to install SDWebImagePhotosPlugin are either incomplete or vague.

What cause this issue ?
fast-image on iOS is actually backed by a native framework SDWebImage, and SDWebImagePhotosPlugin is a plugin to support loading camera roll photos.
Is this related to install ways ? Could you change both SDWebImage and SDWebImage into the CocoaPods, don’t mix them or using the vendored library.

It's been awhile since I worked on this but I remember like @priteshbaviskar said the instructions weren't easy to follow or aren't complete. Maybe they were written pre 0.60 and need to be updated? I don't have the expertise/time to debug what's going on. Someone who is more familiar with the plugins could probably figure it out easily. I hope anyway.


Add back yafim_kazak as maintainer at hp-application-automation-tools-plugin

Adding Yafim back in order to avoid future issues with the releases.
GitHub: https://github.com/jenkinsci/hpe-application-automation-tools-plugin

Description

Submitter checklist for changing permissions

Always

[x] Add link to plugin/component Git repository in description above

When adding new uploaders (this includes newly created permissions files)

[ ] Make sure to @mention an existing maintainer to confirm the permissions request, if applicable
[x] Use the Jenkins community (LDAP) account name in the YAML file, not the GitHub account name
[x] All newly added users have logged in to Artifactory at least once

Build failed; the context from the latest run is:
Expand to view
First time build. Skipping changelog.
[Pipeline] properties
[Pipeline] node
Still waiting to schedule task
Waiting for next available executor on ubuntu-jenkinsinfracc9360
Running on ubuntu-jenkinsinfracc9360 in /home/jenkins/workspace/-permissions-updater_PR-767-TTVXBWKM4SSLJPLSQ6LXPHROCPM6LIK6OEE5LNLASUGOJODOXBSA
[Pipeline] {
[Pipeline] stage (Clean)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Clean
Proceeding
[Pipeline] deleteDir
[Pipeline] sh
[-permissions-updater_PR-767-TTVXBWKM4SSLJPLSQ6LXPHROCPM6LIK6OEE5LNLASUGOJODOXBSA] Running shell script
+ ls -lah
total 8.0K
drwxrwxr-x  2 jenkins jenkins 4.0K Jul  9 10:42 .
drwxrwxr-x 14 jenkins jenkins 4.0K Jul  9 10:42 ..
[Pipeline] stage (Checkout)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Checkout
Proceeding
[Pipeline] checkout
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
remote: Counting objects
remote: Compressing objects
Receiving objects
Resolving deltas
Updating references
Fetching without tags
Merging remotes/origin/master commit 68dc210affa8c9967d582c764e32f11e580db44a into PR head commit d997f7346122ab5339f2f50ba95ec199b451eb22
[Pipeline] stage (Archive)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Archive
Proceeding
[Pipeline] archiveArtifacts
Archiving artifacts
[Pipeline] archiveArtifacts
Archiving artifacts
‘json/*.json’ doesn’t match anything: even ‘json’ doesn’t exist
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: No artifacts found that match the file pattern "json/*.json". Configuration error?
Finished: FAILURE

Powered by the Comment Logger

Have I done something incorrectly?

Probably the conflicts.  See e.g. https://guides.github.com/introduction/flow/ for how this usually works.
Merge this repo's master into yours to fix it this once, or drop your repo and start over for a clean slate.

Build failed; the context from the latest run is:
Expand to view
Commit message: "Merge pull request #69 from olblak/INFRA-1689"
[Pipeline] properties
[Pipeline] node
Still waiting to schedule task
Waiting for next available executor on java
Running on ubuntu-jenkinsinfra465de0 in /home/jenkins/workspace/-permissions-updater_PR-767-TTVXBWKM4SSLJPLSQ6LXPHROCPM6LIK6OEE5LNLASUGOJODOXBSA
[Pipeline] {
[Pipeline] stage (Clean)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Clean
Proceeding
[Pipeline] deleteDir
[Pipeline] sh
[-permissions-updater_PR-767-TTVXBWKM4SSLJPLSQ6LXPHROCPM6LIK6OEE5LNLASUGOJODOXBSA] Running shell script
+ ls -lah
total 8.0K
drwxrwxr-x  2 jenkins jenkins 4.0K Jul 10 09:47 .
drwxrwxr-x 28 jenkins jenkins 4.0K Jul 10 09:47 ..
[Pipeline] stage (Checkout)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Checkout
Proceeding
[Pipeline] checkout
Cloning the remote Git repository
Cloning with configured refspecs honoured and without tags
remote: Counting objects
remote: Compressing objects
Receiving objects
Resolving deltas
Updating references
Fetching without tags
Merging remotes/origin/master commit 939b05fec93c66ff4567673019b47888178c10af into PR head commit d997f7346122ab5339f2f50ba95ec199b451eb22
[Pipeline] stage (Archive)
Using the ‘stage’ step without a block argument is deprecated
Entering stage Archive
Proceeding
[Pipeline] archiveArtifacts
Archiving artifacts
[Pipeline] archiveArtifacts
Archiving artifacts
‘json/*.json’ doesn’t match anything: even ‘json’ doesn’t exist
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline

GitHub has been notified of this commit’s build result

ERROR: No artifacts found that match the file pattern "json/*.json". Configuration error?
Finished: FAILURE

Powered by the Comment Logger

@daniel-beck, silly me, it is fixed now.


split is a deprecated compile error and unused

using std.mem.split is a compileError as off this change
https://github.com/ziglang/zig/commit/76fb2b685b202ea665b850338e353c7816f5b2bb

I noticed that the current clap dependency also still uses split however

It is just a name change to splitScalar right?

Well iI believe it was split into several split functions, and as the instance in code seems unused I couldn’t deduce the intent.


Future of this project

Hi,
I am using this project in one of my production apps. But I have some concerns about the commit gap being long since the last commit. Also many projects in "textileio" is being achieved.
Could please confirm the future plan for this project? cc @sanderpick
Best.

Hey @omar391, thanks for the issue. We aren't actively developing threads anymore, but the org is still here and building other things. We're happy to field any questions you have. Cheers!


Can't get debug data from console on crash

[x] I have read the FAQ.
[x] I have searched in existing issues.

Environment

OS: [Windows 10]
scrcpy version: [1.17]
installation method: [Windows release win64]
device model: Samsung Galaxy 10
Android version: [11]

Describe the bug
I start scrcpy.exe, it boots and shows the phone screen on the screen. After a random amount of time it will just close out of nowhere. It's not possible to gain any information from the console because it closes along with the screen mirroring.
Any ideas on how to collect debug data?
I haven't been able to run Scrcpy for more than a few minutes so far, the crash is guaranteed. I'm troubleshooting but since I'm not really getting anywhere after a couple of hours I figured I'll post here. Primarily to get some advice on collecting debug data to be able to give a more helpful bug report.

On Windows, run scrcpy-console.bat so that the console does not close on error.


Fix  annotation background color changing issue on arrow key nav in the table

done and updated on the live demo website t2wml.isi.edu


refactoring terminal/initial to have the predicate form

Closes #172

unfortunately the continuity of evalF requires some non-trivial effort. should be dealt with later.


Feature request: implement enabled option

Hello there!
Thanks for the amazing package, we are using it right now and loving it !
I just have a small request, as of now, @sentry/node implements an option enabled which will indicate if sentry should report errors to the platform.
This will allow for quick disabling Sentry on dev environment for example.
If the request is approuve, I can work on a PR to implement this.
Thanks !

Thanks for the feedback.  I'll look into this and get back to you

Which configuration feature are you referring to:
https://docs.sentry.io/error-reporting/configuration/?platform=javascript

Seems like I can't find it. Closing then. Thanks for your time

It's not listed in their docs anywhere, but it is available on the options interface you pass to init.
https://github.com/getsentry/sentry-javascript/blob/master/packages/types/src/options.ts#L14


Downloadable Plugins not showing in Discover

macOS version:    Ventura (13.5.2)
Kap version:      3.6.0
Steps to reproduce

Open Kap app.
Go to Preferences > Plugins > Discover.

Current behavior
Plugins don't load in the Discover screen for Plugins and shows error message: Oops! Something went wrong...

Expected behavior
Plugins should show in the Discover screen for Plugins.
Workaround
No available workaround at this time.

Checked again later and the issue appears to have resolved itself. Can't reproduce the issue anymore, so closing this out.


move median from chainlink

https://smartcontract-it.atlassian.net/browse/BCF-2733
Supports:

https://github.com/smartcontractkit/chainlink/pull/11270

@HenryNguyen5 what could be wrong with our lint setup for CI? We are getting some lint errors that shouldn't be errors, and I imagine it has to do with the setup. I ask because I see you were involved in the LLO setup as well.


⚠ HopeAlley Ecards has degraded performance

In acef684, HopeAlley Ecards (https://hopealley.com/ecards) experienced degraded performance:

HTTP code: 200
Response time: 6278 ms

Resolved: HopeAlley Ecards performance has improved in 09cf7ea after 13 minutes.


the server closed before I choose download in my phone's browser.

I scan QR code in my browser. And choose download that file. Then the server closed, I have no idea how to download that.
Thank you for any suggestions.

see this pr

In the case of some barcode scanning applications, the app will do it's own internal fetch to the URL rather than directly referring you to the browser.
This seems to be the case with the commonly used Barcode Scanner application on Android, and I suspect it may be done automatically by most apps that use the library that it seems to be using underneath, Zxing

I suspect the best way of handling this is to either put in some kind of "don't auto close flag" or the more hacky but potentially more useful not closing the connection depending on the user-agent of the initial request.

As I mentioned in this comment, I would like to retain the auto close ability. Let's continue researching a solution, I'm pretty sure we will find one; thanks for showing interest in this!

@claudiodangelis I'm having the same Issue.
I agree, that the feature of auto closing should not be removed.
However, couldn't we add a command line parameter which disables the auto-close feature?
That way the user can decide for themselfs what to use

Agreed @beac0n, while we work out a definitive fix for this, we can have a flag that prevents the tool from automatically closing.
The patch would look like this:

var autocloseFlag = flag.Bool("autoclose", true, ".....")

. . .

if *autoclose == true {
    os.Exit(0)
}

Usage would be:
./qr-filetransfer -autoclose=false myfile.pdf

Thoughts? Maybe we can find a better flag name for autoclose (or for using a complement)?
To @joyme123: you submitted a PR for this issue a few days back, do you want to apply these changes?

The parallel-downloads branch on my fork fixes this issue. At least for ZXing. In my testing it has also been successful in allowing parallel downloads to succeed while still allowing for auto-closing. I need more testing to be done. So far the parallel downloads have only been tested using Chrome 65 on Android. Also as is it allows multiple clients to connect and when the first one completes a download the application exits. I have an idea on how to fix it, but would like to have more people test the parallel downloading to make sure I'm on the right track before investing more.
Time constraints mean I won't be able to get a PR submitted until probably tomorrow, but feel free to grab it from my fork.

Found a couple of issues with the code. As is it does happen to allow the transfer to complete sometimes but not consistently. Know the issue and will be updating the code today.

Hello @ginhton @Dolondro @beac0n and @jerson, could you please help testing the fix provided by @tssva?
Instructions:
# From the cloned repository...
git fetch origin pull/54/head:parallel-downloads
git checkout parallel-downloads
go build
./qr-filetransfer /path/to/the/problematic/file

Thanks :+1:

I can confirm that this fixes the issue for me :+1:


Update Version Chart and add a change to fix error to deploy with new…

… version of K8s

This is in another pull request
sorry


feat(telemetry): check operators status on fetching operators list

Motivation
We need to handle the scenario where an operator is deregistered from the quorum in the tracker.
Description

Periodically fetches operator statuses.
Discards responses from operators whose status is not "REGISTERED".
When finishing the trace, considers only "REGISTERED" operators when calculating missing responses.

How To Test

[!TIP]
You will need a lot of terminals 😎

Run anvil

make anvil_start_with_block_time

Run aggregator

make aggregator_start

Build operator

make build_operator

Register operator 1

export OPERATOR_ADDRESS=0x70997970C51812dc3A010C7d01b50e0d17dc79C8
make operator_full_registration CONFIG_FILE=config-files/config-operator-1.yaml

Register operator 2

export OPERATOR_ADDRESS=0x3C44CdDdB6a900fa2b585dd299e03d12FA4293BC
make operator_full_registration CONFIG_FILE=config-files/config-operator-2.yaml

Register operator 3

export OPERATOR_ADDRESS=0x90F79bf6EB2c4f870365E785982E1f101E93b906
make operator_full_registration CONFIG_FILE=config-files/config-operator-3.yaml

Run batcher

make batcher_start_local

Run Telemetry

make telemetry_create_env
make telemetry_run_db
make open_telemetry_start
make telemetry_start

Run Operator 1

./operator/build/aligned-operator start --config ./config-files/config-operator-1.yaml

Run Operator 2

./operator/build/aligned-operator start --config ./config-files/config-operator-2.yaml

Run Opreator 3

./operator/build/aligned-operator start --config ./config-files/config-operator-3.yaml

Send proofs

make batcher_send_burst_groth16

Go to Jaeger UI and find the new traces

You should see traces like the following one

Eject one operator

cast send 0x851356ae760d987E095750cCeb3bC6014560891C --private-key 0xac0974bec39a17e36ba4a6b4d238ff944bacb478cbed5efcae784d7bf4f2ff80 --rpc-url http://localhost:8545/ "ejectOperator(address, bytes)" 0x3C44CdDdB6a900fa2b585dd299e03d12FA4293BC 0x00

You should see that the traces now includes only the two remaining operators:

You can register the operator again by running step 11.

aside from small nits, the code looks good and worked as expected


Trakt app error

Hi
I just started getting the following error a couple of days ago:
Error: error creating syncer: failure initialising trakt client: failure hydrating client: failure simulating trakt api app allowlisting: failure scraping response for selector #desktop-user-avatar and attribute href
make: *** [Makefile:10: sync] Error 1
Error: Process completed with exit code 2.
I've tried creating a new Trakt app/updating client ID and secret but still the same error.
Any help solving this would be much appreciated.
Many thanks,

I can see everyone is getting this error as well, even the main repository

Hi folks, I’m getting the same error. It’s probably a change on the Trakt website. I’ll take a look today or tomorrow when I get a chance 👍

The problem was related to changes in the HTML content on the Trakt website.
I've added a temporary fix to unblock all users of the syncer.
One of the next few days I will implement a more robust way to retrieve the Trakt username via the Trakt API:
curl --location 'https://api.trakt.tv/users/me' \
--header 'trakt-api-key: XXX' \
--header 'trakt-api-version: 2' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer XXX'


refactor for multiple deployment environments

project can have multiple deployment environments (dev, prod, etc.)
CI role - can build/store artifacts; can deploy to temporary ci environment stacks
CD role (per env) - requires run with github environment; can deploy to deployment bucket
perhaps pass in map of environment:deployment bucket
then make CD role for each environment
base CI prefix off project name?

map could also have cloudfront distribution id


Fix tokenizer to ensure negative values are not parsed as flags

fixes #365
Fixes the internal implementation of tokeniser to avoid recognising negative floating number and integers as a flag argument
Future fixes of how the individual command handles negative inputs will be dealt with in a separate PR.

Codecov Report

Merging #373 (56f71cc) into master (7190c83) will decrease coverage by 0.34%.
The diff coverage is 27.77%.

@@             Coverage Diff              @@
##             master     #373      +/-   ##
============================================
- Coverage     60.98%   60.63%   -0.35%
- Complexity      542      548       +6
============================================
  Files           101      101
  Lines          2040     2063      +23
  Branches        209      212       +3
============================================
+ Hits           1244     1251       +7
- Misses          708      724      +16
  Partials         88       88

Impacted Files
Coverage Δ

...ain/java/seedu/programmer/model/student/Email.java
80.00% <ø> (ø)

...java/seedu/programmer/model/student/StudentId.java
80.00% <ø> (ø)

src/main/java/seedu/programmer/ui/HelpWindow.java
0.00% <0.00%> (ø)

...eedu/programmer/logic/commands/EditLabCommand.java
76.31% <66.66%> (ø)

...edu/programmer/logic/parser/ArgumentTokenizer.java
98.38% <100.00%> (+0.20%)
:arrow_up:

.../programmer/logic/parser/EditLabCommandParser.java
79.31% <0.00%> (-10.35%)
:arrow_down:

...edu/programmer/logic/parser/EditCommandParser.java
73.33% <0.00%> (-10.00%)
:arrow_down:

.../main/java/seedu/programmer/ui/CommandHistory.java
90.24% <0.00%> (-4.36%)
:arrow_down:

...java/seedu/programmer/logic/parser/ParserUtil.java
73.91% <0.00%> (+8.69%)
:arrow_up:

Continue to review full report at Codecov.

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

fixes #364 as well


JSON Support for Alembic

Render JSON data type as NCLOB column. I am testing whether or not this automatically works also for SQLALCHEMY updates to JSON fields.

Can you please

add a test
explain what the current behaviour is

Current behavior is that if your sqlalchemy model includes a JSON column and we are using alembic, trying to run a migration that adds a JSON columns results in  Compiler <sqlalchemy_hana.dialect.HANATypeCompiler object at 0x14340ddd0> can't render element of type JSON

Okay, now we have some test failure with JSON. Can you please check them. Please let me know if you need any support

Would need info on how to properly set up the tests locally against a HANA instance, otherwise this will be impossible to look into, as the tests that are executed seem to be sqlalchemy standard tests and as such I need to debug whats going on.
On top of that, only basic JSON functionalities are ever going to be supported because HANA has no inherent notion of JSOn as a type (and hence JSONB based looksups like postgres offers are not available). This means that even if we fix this issue which currently fails all of the added tests, other tests such as test_index_typed_access and  test_index_typed_comparison are probably never going to work, so we would need to skip them.

@Zahlii do you have a HANA instance to work with?
If yes, please check which tests make sense and which not. I'm fine ignoring broken ones (see existing tests how to do that), but we should try to implement as much functionality as possible

I currently only have access to an HDI container, but checking with our global account admin if we can get a user that can create schemas, as currently using HDI fails as we cannot create a random test schema inside of it with default user/pass

@Zahlii if it's fine for you, I can also take over this part here. since you already contributed a lot 😄

I managed to reproduce it now with some tweaks, however for me the issue seems to be independent of JSON:
The test runs the following create:
CREATE TABLE data_table (
id INTEGER NOT NULL,
name NVARCHAR(30) NOT NULL,
data NCLOB NOT NULL,
nulldata NCLOB,
PRIMARY KEY (id)
)
And then attempts the following INSERT
FAILED [ 33%]INSERT INTO data_table (name, data, nulldata) VALUES (?, ?, ?)
Which obviously cannot work, as the ID field is not filled...

Good finding. Let me have a look!

Since I cannot just push to your fork, please do the following:
To test/test_sqlalchemy_dialect_suite.py add the following code
from sqlalchemy.testing.suite.test_types import JSONTest as _JSONTest

class JSONTest(_JSONTest):
    @classmethod
    def define_tables(cls, metadata):
        Table(
            "data_table",
            metadata,
            Column("id", Integer, autoincrement=True, primary_key=True),
            Column("name", String(30), nullable=False),
            Column("data", cls.datatype, nullable=False),
            Column("nulldata", cls.datatype(none_as_null=True)),
        )

    def test_index_typed_access(self):
        pytest.skip("Index typed access is not supported")

    def test_index_typed_comparison(self):
        pytest.skip("Index typed access is not supported")

    def test_path_typed_comparison(self):
        pytest.skip("Path typed access is not supported")

Open TODOs

[ ] Add a section to the readme explaining what is supported and whats not
[ ] Overwrite visit_json_getitem_op_binary and visit_json_path_getitem_op_binary in HANAStatementCompiler and raise an error stating that these operations are not supported


Update Prometheus to cd73b3d33e064bbd846fc7a26dc8c313d46af382

As we are blocked on some breaking changes to be addressed before we can upgrade Prometheus to the latest master, this PR attempts to upgrade Prometheus upto this commit https://github.com/prometheus/prometheus/commit/cd73b3d33e064bbd846fc7a26dc8c313d46af382 which hopefully does not have any breaking changes and helps the TSDB block based ingesters in Cortex :)

[ ] I added CHANGELOG entry for this change.
[X] Change is not relevant to the end user.

Changes

Verification

I would have expected go.sum file to have changed, but that is not the case. What is more worrying is that, go.mod and go.sum in upstream point to different commit. (upstream go.mod says b90be6f32a33 and go.sum says 1e64d757f711, and the CI picks up 1e64d757f711.

Marco pointed me out to the override in go.mod, makes sense now, removing it and trying

There's an overrided in go.mod replace which you should change as well.

As we are blocked on some breaking changes to be addressed before we can upgrade Prometheus to the latest master, this PR attempts to upgrade Prometheus upto this commit prometheus/prometheus@cd73b3d which hopefully does not have any breaking changes and helps the TSDB block based ingesters in Cortex :)

Why not up to latest?
I guess then @krasi-georgiev want to take over?

Why not up to latest?

That has more breaking changes which will take time to fix here, and idea was to get some improvements from Prometheus soon. And yes, Krasi will take over after this one.

Also, I have some ugly hacks in place right now to fix some breaking changes. Once I fix the e2e tests, I plan to review stuff again and do a cleanup.
One such breaking change was replacing Rule with RuleNode in a RuleGroup upstream. The RuleNode upstream uses a yaml Node instead of a string like in Rule, which is painful when using it here, so I added a PromRuleGroup which does not use RuleNode.

Do you think there was something significant we pulled with this.

I will take a look at the changelogs and add the significate changes :)

This makes totally sense @codesome , let's do step by step. Thanks for helping :heart:

Looks like essentially we have something wrong with flags still. e2e test:
=== CONT  TestReceive/hashring
Starting receive-1
receive-1: Error parsing commandline arguments: time: unknown unit d in duration 15d
receive-1: usage: thanos receive [<flags>]
receive-1: Accept Prometheus remote write API requests and write to local tsdb`

I guess its the modelDuration method after all. I will fall back to using them :)

Tests are passing and changelog entries added!

@codesome looks like some conflicts this morning. Let's fix & merge, and then I will do 0.13 release (: :muscle:
Thanks!

LGTM, Let's merge on green (:

Thanks!
@codesome @pracucci @pstibrany it's unblock Cortex I guess.


Added ability to globally publish build data using Jenkins Hygieia plugin.

I hope this PR is going to send build data from all the pipelines. But #2421, is to send the data to multiple hygieia instances, which is useful for the hygieia developers who maintain different environments. Please post your comments on this.

approved the PR


Unable to authenticate to Confluence

Hi Team,
I am facing an issue, below is the problem statement & possible approach which i tried.
We are currently migrating from one ASCENT WIKI to another Confluence Data center. We are able to create pages in the old ASCENT Wiki page using the config available but when we are trying to use the same config with the updated URL & SPACE key for new Confluence data center we are facing an authentication issue.

It is giving error as "Unable to authenticate with Confluence" .

What we have done:
Passed username and Password
Created PAT token and had passed in confluence config argument
Created API token and passed
We are admins in space and are really unable to take a step forward and are stuck for long.
Sharing the snippet of the config for reference.
I tried to use REST APIs and was able to successfully create page just by passing the PAT which i tried to give input in the config.
REST APIs approach works but while using it through confluence builder i have facing error.
Can you help me in this as it has become a show stopper for me now?
Thanks.

Any updates?

Hi James,
Sorry for the delayed reply. I was able to build the code and push data on the confluence using the PAT.
There was some tool version issue i guess at my end and also as you guided had helped me to resolve the issue.
Thanks a lot for your prompt help and solution.


Modified storage access for zone and deleted PersistentVolumeLabel since its deprecated

I just updated the "storage access" section in this page:
https://kubernetes.io/docs/setup/best-practices/multiple-zones/
So that dosen't contain "PersistentVolumeLabel" because its deprecated and added little text explain that zone labels are managed by the cloud provider or storage provisioner now

/sig storage

preview page

/approve


feat/package: Whitelist the files for the npm package generated rather than having a blacklist

looks good @bochaco . I'm in favour of this over a blacklist. Should be more robust 👍

Coverage increased (+0.1%) to 91.857% when pulling e7f0baefb98fc90f6eaa00f8e08088ea506f4d37 on bochaco:feat-whitelist-files-for-packaging into 68ecf7c6a3e3c4a8dac87abc957e2583b840885c on maidsafe:master.

Yes, I agree, we obviously cold have the issue of creating new files and not adding them to the whitelist but it's better to have a broken package/functionality than leaking unwanted files mistakenly.


Ensure that the options passed correctly

Codecov Report

Merging #13 into master will increase coverage by 15.21%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##           master      #13       +/-   ##
===========================================
+ Coverage   63.31%   78.53%   +15.21%
===========================================
  Files           7        7
  Lines         368      368
===========================================
+ Hits          233      289       +56
+ Misses        111       54       -57
- Partials       24       25        +1

Impacted Files
Coverage Δ

gui/keybinds.go
74.07% <0.00%> (+69.13%)
:arrow_up:

Continue to review full report at Codecov.

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


Support serving files out of symlink/alias directories

Fixes #137

@Scooby-2 give this a shot if you can.
@glensc Do you think this would cause any BC problems?

Hi Steve
Many thanks for this. Really quick, too. I'll check it out ASAP but having
just signed up with Arvixe I was having connection problems (both web pages
and ftp). I raised a Support ticket but after over 24 hours without a
response I am going to cancel. I since discovered from currentlywww.down.com
that they suffered a 26-hour outage on April 1st/2nd. I'm now with
SiteGround but they do have the same directory structure but I'm starting
again from scratch.
I'll keep you posted.
Regards
Kevin
On 5 April 2015 at 20:56, Steve Clay<EMAIL_ADDRESS>wrote:

@Scooby-2 https://github.com/Scooby-2 give this a shot if you can.
@glensc https://github.com/glensc Do you think this would cause any BC
problems?
—
Reply to this email directly or view it on GitHub
https://github.com/mrclay/minify/pull/138#issuecomment-89831980.

@mrclay i needed similar solution long time ago. i'll definately have look. it will take some time to get my test site up to check this.

Hi Steve
Just to let you know that I effected the changes you suggested but was still having problems because, I think, with my new hosting company the Minify directory was in /~userid/public_html/oldsite/min. I spent a day on it without success but at the same time support were looking into it and they got it working. All I know for sure is that they moved everything up one level, so the site was in public_html and not a sub-directory off that.
I'm sorry I can't help more but I'm under pressure to get things working quickly.
Thanks for your help and promptness on this.

Replaced by #476. Please take a look.


"TypeError: Cannot read property 'toLowerCase' of undefined" when calling headers.getAll()

Possibly I'm using the API very wrong, possibly needs another null/string check before calling .toLowerCase()...
Usage:
const fetch = require('node-fetch');

function getMeta(url) {
  return fetch(url, {method: 'HEAD'})
    .then((res) => {
      console.log(res.headers.getAll());
      return res.headers;
    });
}

getMeta('https://cdn.meme.am/instances/58480692.jpg')
  .then((res) => console.log(JSON.stringify(res, null, 2)))
  .catch(console.error);

Output:
TypeError: Cannot read property 'toLowerCase' of undefined
    at Headers.has (/Users/pdehaan/dev/tmp/del/node_modules/node-fetch/lib/headers.js:121:42)
    at Headers.getAll (/Users/pdehaan/dev/tmp/del/node_modules/node-fetch/lib/headers.js:65:12)
    at fetch.then (/Users/pdehaan/dev/tmp/del/fetch-head.js:6:31)
    at process._tickCallback (internal/process/next_tick.js:103:7)

Source:
/**
 * Return all header values given name
 *
 * @param   String  name  Header name
 * @return  Array
 */
Headers.prototype.getAll = function(name) {
	if (!this.has(name)) {
		return [];
	}

	return this._headers[name.toLowerCase()];
};

— via ./lib/headers.js:64-70
I think I was incorrectly assuming that getAll() would return me a simple object containing all the name/value pairs for the headers (sort of like raw(), but without the extra array nesting).

getAll is meant to return an array with the values of a given header key
Set-Cookie is one very common header that can appear more then once for example (http://stackoverflow.com/a/6375214/1008999)
Calling .getAll('Set-Cookie') should return an array of all those values
looking at the what you get from requesting https://github.com/bitinn/node-fetch/issues/ show you that you got two Vary headers for example

so the result from calling .getAll('Vary') should yield:
["Accept-Encoding", "X-PJAX"]

It's a good idea to tryout the browsers fetch version first before you come to any conclusion that node-fetch is doing something wrong

If you would like to get all headers & keys you would have to something like
for(let [key, value] of res.headers.entries()) {
  console.log(key, value)
}

// could also do:
console.log( Array.from( res.headers.entries() ) )

Sorry, I was trying to figure out browser fetch() but was getting a bunch of CORS errors and unexpected results.
I tried using entries(), but it's giving me an error:
const fetch = require('node-fetch');

function getMeta(url) {
  return fetch(url, {method: 'HEAD'})
    .then((res) => res.headers.entries());
}

getMeta('https://github.com/bitinn/node-fetch/issues/')
  .then((headers) => console.log(Array.from(headers)))
  .catch(console.error);

TypeError: res.headers.entries is not a function
    at fetch.then (/Users/pdehaan/dev/tmp/del/generator-ra/fetch-head.js:5:32)
    at process._tickCallback (internal/process/next_tick.js:103:7)

Possibly related to #127

hmm, yea wasn't aware of the missing #127 header methods...

node-fetch doesn't have ES6 related feature yet, but we do have res.headers.raw() as a workaround.

For lack of ES6 features we will follow up the issue in #127 (also added to KNOWN LIMIT document before we can support them).


refresh package.lock

minor bumps everything

npm run bootstrap

npm run app-start

ran successfully

too many breaking changes


Change evdns to c-ares.

Tired of evdns bugs, we need to use something more new and maintained.
evdns_getaddrinfo -> c-ares async request
bufferevent_socket_connect_hostname -> c-ares async request (caching) + sync wait + bufferevent_socket_connect
Please also see what to do with ag_dns_set_servers.

Research partially completed.

Moving to 1.5+extensionsapi milestone to decide what to do.

core/pull-requests/1693


App crash on launch due to invalid os release when launching on Linux based OS

Traceback (most recent call last):   File "/home/kali/HuntStatsLogger/./src/main.py", line 15, in <module>     if int(platform.release()) >= 8: ValueError: invalid literal for int() with base 10: '5.19.0-kali2-amd64'

Thanks!
I don't imagine most users generally run Hunt on Linux, so I pretty much developed it just with Windows in mind...
Also, that line of code generally is to make sure that the line charts appear the same regardless of screen size or resolution, so it should still work fine even if that line gets skipped.

Oh you're right, it's just that I dev on Linux most of the time (so I couldn't launch your app on my work computer)

Yeah, I had encountered a similar problem on my linux laptop a few times.


Revendor<EMAIL_ADDRESS>and cleanup token projection artefacts

What this PR does / why we need it:
/area open-source
/kind enhancement
This PR

revendors<EMAIL_ADDRESS>cleans up the artefacts related to the token projection story introduced with #76

Special notes for your reviewer:
/invite @timebertt
Release note:

This extension is only compatible with Gardener versions `>= v1.37`.

/invite @kris94


feat: Initial project setup

Description

this PR will initialize this repository.

Also, please update the title of PR to something like feat: initial project setup to follow semantic commit names.

We should use the chore: in PR's title, because we don't have any code which we can use from package :)

@magicmatatjahu I think it's ready to be merged.

@KhudaDad414 Please install deps to have package-lock.json :)


Importing directories (with index.ts files) does not work

Describe the bug
Imported directories (where directory/index.ts is implicitly referred to) are not resolved, but assumed to be .ts files, instead of traversing down into directory/index.ts etc.
To Reproduce
With this directory structure:
foo
  |- index.ts

And this import:
import Foo from './foo'

I only get
(node:19450) UnhandledPromiseRejectionWarning: Error: Couldn't find file '<snip>/foo.ts'
    at TypescriptExtractor.run (<snip>/node_modules/@ts-docs/extractor/dist/extractor/index.js:106:23)

Expected behavior
Imported directories with index files should be supported

Interesting - can I see your ts-docs options? The error can only come from here, which has nothing to do with resolving imports.
I suspect one of your entry points is set to <snip>/foo, but you have to include the filename, so it has to be <snip>/foo/index or <snip>/foo/index.ts

My options were default, I just started trying the tool out and thought it looked promising, but encountered this pretty much straight away.
I'm not sure I understood your last paragraph, are you saying my code needs to explicitly import files? Importing a module via a directory path which implicitly translates to directory/index.ts is obviously very common...? Or did you refer to entry points passed to tsdoc? If I remember correctly, I simply installed and ran
$ tsdoc src

I'm not sure I understood your last paragraph, are you saying my code needs to explicitly import files? Importing a module via a directory path that implicitly translates to directory/index.ts is very common...? Or did you refer to entry points passed to tsdoc? If I remember correctly, I simply installed and ran

Entry points passed to the ts-docs options, that's why I asked to see the options you used. Entry points work a little differently in ts-docs - each entry point must be pointing to a file.

Ok so in a project with 150 files I need to explicitly list all of them as entry points? I figured I just passed the root level directory src 🤷

All good, glad it's working. Just a heads up - If you're documenting an application rather than a library there's the documentImports option which documents all items from all imported files. By default, ts-docs only goes through the exports of the entry point.
The entryPoints option works differently than other documentation tools like typedoc - every entry point must point to a file that is from a different npm library/application (so every file should be under a different package.json file ). The main goal of ts-docs is to make it easy to document monorepos.

Understood, thanks! For now, my intention was to use it for stand-alone library modules.


Backport Bitcoin's share/rpcauth/rpcauth.py in rpcuser.py

I simply backported changes from Bitcoin to modernize rpcuser.py , no new functionalities were introduced. This Pull request aims to close feature request https://github.com/dogecoin/dogecoin/issues/3352

After deleting the rpc authentication .cookie and using the script to generate a rpcauth= to add to my dogecoin.conf file, I'm able to use the provided rpc username/password with `dogecoin-cli. Using an incorrect password errors out.
Everything appears to be working, tested on Ubuntu 22.04.

@patricklodder , i would like if you could squash my pull request. can you please explain me how to squash commits in Github web UI or do you use git commandline to squash git commits.

i would like if you could squash my pull request

Done!

do you use git commandline to squash git commits.

This. But I will have a look at what options we have inside the GitHub web UI once we're done with the release

Hey, any updates on this?

This one is on my list next up, and I hope to get to it before the weekend.


CORGI-609 make latest filter only return root components

This modifies the latest filter so that always filters root_component as well. Comparing components which are not root_components doesn't really makes sense for a few reasons:

We are using RPM schematics to compare things, so comparing anything but RPM, or OCI types in the REDHAT namespace doesn't make sense.
All arches should be considered equivalent in terms of latest.

Leaving this in draft as I got a failing test locally:
>       assert manifest["relationships"][0] == provided_contained_by_component
E       AssertionError: assert {'relatedSpdx...32b765159d68'} == {'relatedSpdx...32b765159d68'}
E         Omitting 2 identical items, use -vv to show
E         Differing items:
E         {'relatedSpdxElement': 'SPDXRef-e24f6913-d568-4e9e-a359-570e53706ad3'} != {'relatedSpdxElement': 'SPDXRef-95582f58-12c8-4fdd-bf3e-86a8a72a2724'}
E         Use -v to get more diff

tests/test_manifests.py:200: AssertionError

Hopefully that is just a change in the order.

picking this up

this looks fine to me - though conceptually (for downstream like griffon) will need to do more ... for example
/api/v1/components?name=grafana&latest_components=True

Only returns a single src ... presumably this is the latest component of the latest stream.
What we need is latest component(s) by stream as we have not constrained using &product_streams= or &ofuri= we want a list of components existing across different product streams - which as discussed with @jasinner will do as a different PR.

The problem with that is we might return any arch as the latest, as they are all considered equal. For example we could randomly select the x86_64 arch as the latest, so we'd have to add some logic filter the results to only include RPM/src and noarch containers. That is definitely possible, but just not something we have time for at the moment.

Yes, this is what I keep offering to help with. I know exactly where this is needed and left a comment describing that in the Jira ticket. I can run my "refresh tags" script in the background while working on fixing this bug I introduced - please let me know if I should pick it up tomorrow.

We could abandon this change in light of the Summit focus, but if you think it won't take you long and it's worth while, please take a stab at it. Otherwise, let's just file a follow up task to make sure we don't use latest filter on non-RPM versioned component types. Jim confirmed he doesn't need this change to resolve CORGI-609.


Too many open files error on latest prometheus version

After upgrading the prometheus operator from 0.29.0 to 0.35.0 and also upgraded the prometheus from v2.8.0 to v2.15.2.  Prometheus pods are crashing while the load test is on. We had ran the similar test on the older version with similar HW underneath, load test was successful.
level=info ts=2020-02-10T16:05:34.380Z caller=main.go:617 msg="Server is ready to receive web requests."
ts=2020-02-10T16:05:42.439Z caller=dedupe.go:111 component=remote level=info remote_name=a40741 url=http://localhost:9095/receive msg="done replaying WAL" duration=8.074058943s
ts=2020-02-10T16:06:00.429Z caller=dedupe.go:111 component=remote level=error remote_name=a40741 url=http://localhost:9095/receive msg="error tailing WAL" err="segments: open /prometheus/wal: too many open files"
ts=2020-02-10T16:06:05.429Z caller=dedupe.go:111 component=remote level=error remote_name=a40741 url=http://localhost:9095/receive msg="error tailing WAL" err="wal.Segments: open /prometheus/wal: too many open files"
level=warn ts=2020-02-10T16:06:33.470Z caller=main.go:494 msg="Received SIGTERM, exiting gracefully..."
level=info ts=2020-02-10T16:06:33.470Z caller=main.go:517 msg="Stopping scrape discovery manager..."
(edited)

Startup logs from older prometheus version.
level=info ts=2020-01-15T00:12:14.68377516Z caller=main.go:324 fd_limits="(soft=1048576, hard=1048576)
Startup logs on newer prometheus version.
level=info ts=2020-02-10T20:29:23.101Z caller=main.go:333 fd_limits="(soft=1024, hard=4096)"
Looks like this is a bug where prometheus is not setting the correct fd ulimit.
Can someone let us know how we can increase both soft and hard limit for prometheus image on start up.

AFAIK Prometheus doesn't even try to change the fd limit. This smells more like a changed setting in your environment (or perhaps in the Prometheus operator).

Thanks for your reply @beorn7. I will downgrade the operator and keep the latest Prometheus and test it.
I will keep this thread updated.

We found the problem, latest kops are updating the docker version and also installing some external dependencies which are configuring the default configuration for docker containers in EC2 instance which are setting the lower fd_limit value. We disabled the external dependencies installation option and ran the test and we got expected fd_limits.
This issue can be closed.
Thanks for the help.


Fix image inspect error on dnf

Issue
Fixes regression inadvertently introduced with https://github.com/containerd/nerdctl/pull/3017 for image inspect command exit code when image does not exist.
Description
This change updates the image inspect utility function to serialize an array of encountered errors. This aligns with the behavior of nerdctl inspect.
Testing
Adds simple test case for image inspect on images that do not exist.
Required updates to test cases which assumed exit code 0 for image inspects on images that do not exist.

What is "dnf" here?
Doesn't seem related to Fedora's dnf

@AkihiroSuda, oops sorry about that. I had shorthanded "did not find" not meaning to confuse dnf package manager. Lastest commit should have more clear wording.


Native library doesn't load on ARM9 / causes app to abort

I'm having essentially this same issue as this resolved one --> https://github.com/xerial/sqlite-jdbc/issues/32
Except my processor is a Freescale i.MX28 / ARM926EJ-S running Debian OS Version 3.14.27 and JDK OpenJDK Runtime Environment (IcedTea 2.5.5) (7u79-2.5.5-1~deb7u1) / JamVM (build 2.0.0).
I hacked together a xerial sqlite-jdbc.jar using the native arm .so library discussed here ---> https://bitbucket.org/xerial/sqlite-jdbc/issue/79/compile-for-arm and that caused a stack trace saying the library in /tmp could not be opened.
When I use the most recent release (<IP_ADDRESS>) as-is, the app aborts with: 6414 Illegal instruction

Could you try building a native library with make native and then running mvn test?

Duplicate of #45


Append a feature to contact a profile

Hi,
one feature request : I would like contact a profile by mail or other system.
Suggestion : append a tool to touch a profile, example in this page http://readthedocs.org/profiles/zombat/
Regards,
Stephane

i need this a couple of times, there is no way to contact people


Stylelint takes a lot of time to discover all files

See https://github.com/stylelint/stylelint/issues/2399 for details.

Well, this issue is fixed by providing glob with referenced commit above.
However, I dislike the fact that it contains hardcoded paths.
So far the only solution I see is to use Node API for Stylelint and put it into util tests/utils/stylelint.js
npm script will call it, and stylelint,js will read paths from Grunt config then.


No poll if success

Follow more closely Azure guidelines: if the initial response body has a status and the polling strategy was Operation-Location, follow that status.

API change check
API changes are not detected in this pull request.

The failure has nothing to do with the change.

/check-enforcer override


add Watir::Element#drag_and_drop_on

Discussion here: http://groups.google.com/group/watir-general/browse_thread/thread/3f2310dd676b48b1

our current app doesn't make much (if any) use of this..  but when I think about how often I use it in Jira when working with the task-board and the backlog, I can surely see where this might be useful  (might even appeal to people like Atlassian)
I'd +1 this, but rank it slightly behind modified-clicks (shift-click etc) as I think those might be even more common

This would be great.

+1

Yeah, we should get this in soon. This was recently brought up on the development list as well. Adding specs to watirspec would be a good starting point.


We read some settings from the devenv.exe.config file --- devenv.exe.config is not user mutable

We need an alternate mechanism to enable these features:
// App.config keys for determining whether not-shipping features are turned on or off
// Edit devenv.exe.config and place these at the end.
// <appSettings>
// <add key="fsharp-regions-enabled" value="true" />
// <add key="fsharp-navigationbar-enabled" value="true" />
// <add key="fsharp-standalone-file-intellisense-enabled" value="false" />
// </appSettings>

Because of this design the powertools who used this feature correctly, happened to cause VS update 1 to do bad things to people who use Dev 15 and the PowerTools.

I think these settings should be exposed via F# Editor options in Visual Studio. Ideally they are turned off by default. In doing so, we should be able to improve these features gradually.
We're looking forward to removing these settings from VFPT. Doing it in VFPT was a bad idea since we haven't been able to fix bugs when users report them.

Editor options is a good idea.  I had thought registry to enable you to continue to turn them on, but we could certainly add options, instead.

Would it be possible to have all options disabled when you open VS in safe mode? This might help in case such new features cause startup issues with VS. Or at least some other way to override the settings from the commandline or otherwise, regardless of what's selected under F# Editor Options.

I think these features should be taken out of VFT (fully disabled) and added to VFPT.  They would end up much higher quality that way

I don't think we would accept bug fixes to these features directly into VFT on grounds of stability

As part of #913, these keys/opposite functionality would be removed, and we would depend on Roslyn's infrastructure for that. Work is done on roslyn branch:
https://github.com/Microsoft/visualfsharp/tree/roslyn


Clustergrammer for gene expression exploration

home page
kinda works on Colab

GitHub Issue for this

e.g. notebooks

See #37

Yale doing 1D tSNE heatmaps: Fast Interpolation-based t-SNE for Improved Visualization of Single-Cell RNA-Seq Data

Here's a demo of Clustergrammer being used on Kaggle via Nicolas Fernandez on twitter.


No named exports found in module refer to mjs file

ref #2093 https://github.com/standard/standard/issues/863
// File a.mjs
export const A = 'a'

// File b.js
export * from './a.mjs'

// File c.js
export * from './b.js'

eslint c.js
# output
#  1:15  error  No named exports found in module './b.js'  import/export

eslint c.js --ext .js,.mjs
# output
#  1:15  error  No named exports found in module './b.js'  import/export

only renaming a.mjs to a.js can workaround this problem

Do you have .mjs in the import/extensions setting?

Do you have .mjs in the import/extensions setting? That seemed to be the fix for #2093.

mjs is the official extension for modules in NodeJS, so I think that it should be parsed by default without any addition config

That's true, but it can't happen until resolve supports "exports".

I can confirm that this issue is still exists - got it recently with .ts files.
Here is another good example.
Would love to see it fixed because import \ export check is pretty important.
( as a workaround for now you could change rule to throw warning instead of error )
Thanks a lot.


Errors are now being logged as errors in the Unity console

2 things fixed

The status codes from the responses where never checked, so no errors were thrown on things like 404, 500 etc.
The log-error levels were all wrong, causing errors to not being thrown as errors.
Before (Easily missed):

After:

Tests fail because errors are now logged on calls unrelated to the tests (like end session f.ex.). We'll need to look into that.


python37Packages.hbmqtt: 0.9.5 -> 0.9.6

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.7-hbmqtt/versions.
meta.description for python37Packages.hbmqtt is: '"MQTT client/broker using Python asynchronous I/O"'.
meta.homepage for python37Packages.hbmqtt is: '"https://github.com/beerfactory/hbmqtt"

Checks done (click to expand)

built on NixOS

Warning: a test defined in passthru.tests did not pass

0 of 0 passed binary check by having a zero exit code.

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

found 0.9.6 with grep in /nix/store/izk888fgbjlzb73ng70zsvpm5aq7x46k-python3.7-hbmqtt-0.9.6

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

du listing: https://gist.github.com/3bd0dc68e974f6b6180e855f7b69d1b9

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

8 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
python37Packages.hbmqtt
python38Packages.hbmqtt

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/izk888fgbjlzb73ng70zsvpm5aq7x46k-python3.7-hbmqtt-0.9.6 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/izk888fgbjlzb73ng70zsvpm5aq7x46k-python3.7-hbmqtt-0.9.6
ls -la /nix/store/izk888fgbjlzb73ng70zsvpm5aq7x46k-python3.7-hbmqtt-0.9.6/bin

cc @dotlambda for testing.

@GrahamcOfBorg test home-assistant

home-assistant is broken on master with the same failure, and failure is not related to this bump:
hass: must succeed: hass-cli --server http://hass:8123 --password 'some_secret' --output json state get binary_sensor.mqtt_binary_sensor
hass # [   19.984161] hass[718]: 2020-02-02 17:15:52 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from <IP_ADDRESS>
hass # error: HomeAssistantCliError: Error while getting Entity binary_sensor.mqtt_binary_sensor: 401: Unauthorized
hass # Run with -x to see full exception information
hass: output:
error: command `hass-cli --server http://hass:8123 --password 'some_secret' --output json state get binary_sensor.mqtt_binary_sensor` failed (exit code 1)


Fix file output with different format

Without this PR:
./bom generate ./   --format json -o bom.json

Would output standard SPDX bom in bom.json, completely disregarding the --format flag.
This PR fixes that.

/ok-to-test


3D image

Is 3D image code of the paper included here?

The 3D visualizations are not included here; they were rendered using a 3rd party software, UCSF Chimera.


Create Backend API for Frontend

User Story
As a frontend developer, I would like a backend API so that I can use the backend functions in my frontend application.
Detailed Description
The backend functionality must be placed into an API that the frontend dev team can use to integrate the frontend with the backend and add functionality to the frontend application.
Acceptance Criteria

[x] Given the completed functionality of the backend, then move the functionality to an API that can be used by frontend team.
[x] Given a backend API, then frontend dev team should be able to add functionality to the frontend application.

Tasks

[x] #45
[x] #46
[x] #47

This was completed.


"Strategies" link on website 404

Expected behavior
Click "Strategies" link on homepage, load list of passport strategy packages
Actual behavior
http://www.passportjs.org/packages/ returns 404
Steps to reproduce
Visit  http://www.passportjs.org/packages/
Environment
production website

Also 404 for passport-local examples:
http://www.passportjs.org/packages/passport-local/:
For complete, working examples, refer to the multiple examples  included.
https://github.com/jaredhanson/passport-local/tree/master/examples -> 404

Also, from http://www.passportjs.org/packages/passport-saml link to  ADFS documentation http://www.passportjs.org/packages/passport-saml/docs/adfs/README.md is broken

+1.  I've noticed that the links work at https://www.passportjs.org (with HTTPS), but that exposes another issue: the SSL certificates used on passportjs.org were issued to *.herokuapp.com, and are thus invalid.
See https://support.dnsimple.com/articles/heroku-error-ssl/ for solutions to common HTTPS errors on Heroku.

I tried http://www.passportjs.org/packages/passport-saml/docs/adfs/README.md with https and still got a 'Not Found' ☹
Integration with ADFS is working and I can see it in the SAML decoder plugin for Chrome, but my 'profile' is coming back empty. Was looking for more ADFS specific docs to help troubleshoot that but those were 'Not Found' ☹

Still prevalent.

View All Strategies button on the home page yields a 404. The issue was first reported in 2018, six years ago.


Evaluate OS X support

Right now no effort is made to build this crate on OS X.
One would need to evaluate the requirements (building/downloading/installing libmagic) and possibilities for continous integration.

Travis CI seems to be able to build on Mac OS X (but support is still considered beta, not sure if Rust works at all).

Howdy! I develop on OS X, and after installing libmagic via homebrew, this crate works as expected. I currently use it in bins, and it works completely fine.
Basically, to use this crate on OS X, one just has to run brew install libmagic, and that's it.
Not sure if this is useful feedback or not, but just figured I'd give an update.

That is quite useful feedback, thanks @jkcclemens !
I have updated the README accordingly and intend to add OS X to the Travis CI build soon™.
I'll leave this issue open in case I need or find more information :smiley:


Build Failed, Could not find :react-native-dialogs:

* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugCompile'.
   > Could not find :react-native-dialogs:.
     Searched in the following locations:
         file:/C:/Users/gamat/.m2/repository//react-native-dialogs//react-native-dialogs-.pom
         file:/C:/Users/gamat/.m2/repository//react-native-dialogs//react-native-dialogs-.jar
         https://jcenter.bintray.com//react-native-dialogs//react-native-dialogs-.pom
         https://jcenter.bintray.com//react-native-dialogs//react-native-dialogs-.jar
         https://jitpack.io//react-native-dialogs//react-native-dialogs-.pom
         https://jitpack.io//react-native-dialogs//react-native-dialogs-.jar
         file:/S:/Development/dinpromobile/node_modules/react-native/android//react-native-dialogs//react-native-dialogs-.pom
         file:/S:/Development/dinpromobile/node_modules/react-native/android//react-native-dialogs//react-native-dialogs-.jar
         file:/S:/Program Files (x86)/Android/android-sdk/extras/android/m2repository//react-native-dialogs//react-native-dialogs-.pom
         file:/S:/Program Files (x86)/Android/android-sdk/extras/android/m2repository//react-native-dialogs//react-native-dialogs-.jar
         file:/S:/Program Files (x86)/Android/android-sdk/extras/google/m2repository//react-native-dialogs//react-native-dialogs-.pom
         file:/S:/Program Files (x86)/Android/android-sdk/extras/google/m2repository//react-native-dialogs//react-native-dialogs-.jar
     Required by:

the correct way to add the dependency is compile project(':react-native-dialogs') please add it to the docs, thnx!

It`s already added:

https://github.com/aakashns/react-native-dialogs-example/commit/b58086d8fb9ece99f0e678dd8bf0e689a856bd43


Improved detection of unsupported iOS devices

Detects iPad 2 and iPad Retina as unsupported devices.
Simplifies blacklisting logic.
Minor improvements to error messages.

Fixes #4621 (which was originally fixed by #4783, but later re-broken)

I would soften the language a little.  It would be trivial for us to support some of these older ipad/iphone devices.  https://github.com/flutter/flutter/issues/2089 is the bug.  I might consider referencing the bug and/or adding words like "yet" to the part which talks about the 32-bit ARM devices.

@eseidelGoogle added some 'yet's to the older iPad/iPhone verbiage.

Added unit tests.


[test] make sure tests are using mocked fetch

related to https://github.com/hirosystems/stacks.js/issues/1248
some tests may not be using mocked fetch results, but actually making network requests.
change remaining non-mocked fetch tests to mocked results.

There are no further tests that needs to be mocked. Fixed the tests in wallet-sdk that already got merged.
So this issue is safe to be closed.


Replace Array return types with TypedArray (part 2)

Follow-up to #63959
Supersedes #60053 and #60054
Right now it doesn't compile, because it depends on #63959 being merged first.

Looks good to me, we should look into merging all of those.

Needs rebase.

The .NET glue generation seems to fail:
ERROR: Return type from getter doesn't match first argument of setter for property: 'RDUniform._ids'.
   at: _generate_cs_property (modules/mono/editor/bindings_generator.cpp:1785)
ERROR: Failed to generate property '_ids' for class 'RDUniform'.
   at: _generate_cs_type (modules/mono/editor/bindings_generator.cpp:1510)
ERROR: Generation of the Core API C# project failed.
   at: generate_cs_api (modules/mono/editor/bindings_generator.cpp:1324)
ERROR: --generate-mono-glue: Failed to generate the C# API.
   at: handle_cmdline_options (modules/mono/editor/bindings_generator.cpp:3862)

Thanks!


Replace "Exception" with the specific exception that is raised in ClientManagementController.java

GCI-254: Replace Exception with the specific type of exception that is raised in ClientManagementController.java
https://issues.openmrs.org/browse/GCI-254

I modified the pull request comment. Is it now correct?


Add: bootupd Stage

Add the bootupd stage to install GRUB on both BIOS and UEFI systems, ensuring that your bootloader stays up-to-date.

@lukewarmtemp thanks for the review! I probably need to add more info about/checks to it too, as it is required to have bootupd in the ostree to be used.

I looked into this a little bit today. Still playing around with it. Will provide feedback tomorrow.

I pushed up some changes here - it should all work now!
This now builds on the aleph version PR (we'll drop those patches out when we push up this PR upstream)
It also incorporates https://github.com/osbuild/osbuild/pull/1493
Let me know what you think of some of the changes. (


mismatching between input and calculated obb_cls vertices

there is a mismatch in the computation of the obb_cls box vertices. there is a swap in sign of the vertices from box center.
i set the inputs using below two commands
        primitive_cls = Primitives.Box_Cls(box_center, box_scale)
        box_cls = Collider.OBB_Cls(primitive_cls)

inputs:
size  [120.  90. 100.]
origin  [ -49.09939814 1422.4953311<PHONE_NUMBER>5]
box set parameters.
box_cls:
box size:  [120.  90. 100.]
box origin:  [ -49.09939814 1422.4953311<PHONE_NUMBER>5]
box H: [[ 1.00000000e+00  0.00000000e+00  0.00000000e+00  4.90993981e+01]
[ 0.00000000e+00  1.00000000e+00  0.00000000e+00 -1.42249533e+03]
[ 0.00000000e+00  0.00000000e+00  1.00000000e+00 -9.34280218e+02]
[ 0.00000000e+00  0.00000000e+00  0.00000000e+00  1.00000000e+00]]
box vertices:  [[<PHONE_NUMBER>4 -1467.4953311   -984.28021795]
[<PHONE_NUMBER>4 -1377.4953311   -984.28021795]
[  -10.90060186 -1377.4953311   -984.28021795]
[  -10.90060186 -1467.4953311   -984.28021795]
[<PHONE_NUMBER>4 -1467.4953311   -884.28021795]
[<PHONE_NUMBER>4 -1377.4953311   -884.28021795]
[  -10.90060186 -1377.4953311   -884.28021795]
[  -10.90060186 -1467.4953311   -884.28021795]]

wrongly inputed box center into origin instead of location


TSCLibc: add an implementation of mkdtemp for Windows

This adds an implementation of mkdtemp for Windows to accommodate
swift-package-manager which uses this rather than Foundation.

CC: @tomerd @neonichu @abertelrud

@swift-ci please test

@compnerd please merge when ready


I can't get rid of “Microsoft.outlookForWindows” in taskbar

I cannot remove "Microsoft.outlookForWindows ” in the taskbar.
The strange thing is that in the taskbar path the shortcut is not displayed.
I assume the icon is generated with the network connection.
Any ideas?
Thanks

Use the Delete preset icons from the taskbar to remove the Outlook icon:

Note that taskbar icons in Windows 11 are controlled by the [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Taskband] registry key, not by shortcuts in the %APPDATA%\Microsoft\Internet Explorer\Quick Launch directory.

I used the option, but unfortunately it also deletes explorer and edge icons, is there no way to delete only Outlook (new)?
Thanks

Unfortunately, the values in [HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Explorer\Taskband] use binary data to store the taskbar icons. I don't know how to selectively remove the icon for Outlook while keeping the other icons.
PS C:\> Get-Item -LiteralPath 'Registry::HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer\Taskband'

    Hive: HKCU\Software\Microsoft\Windows\CurrentVersion\Explorer

Name                           Property
----                           --------
Taskband                       FavoritesResolve : {62, 3, 0, 0...}
                               Favorites        : {0, 168, 1, 0...}
                               FavoritesChanges : 7
                               FavoritesVersion : 3

Trying to experiment if it is possible to restore file explorer and d Edge icons in post installation via RunOnceEx.

I tried without success.
I ran the “Delete preset icons from taskbar” option, and then restored the icons and Taskband registry key related to Explorer and Edge via RunOnceEx works only for a moment, then they disappeared again.

I was able to solve with a mixed procedure.
1- Delete the preset icons in the taskbar.
2- Inserted the Taskband registry key (related only to Explorer and Edge icons) in the “Scripts to run whenever a user logs in for the first time” section.
3- In the RunOnceEx procedure, I entered the batch command that copies the Explorer and Egge icons to the taskbar.
Taskband.reg
https://justpaste.it/ei3bq

https://github.com/cschneegans/unattend-generator/issues/139 now offers a very simple solution.


chart/v0.3.9

rename files
move bootnode loadbalancer service to one file
move nodePort and loadBalancer for rpc node into 1 files
port-check cm not used
rename transaction generation file name manifests
added configmap suffix
rename configmaps

Purpose

How does the solution address the problem

Changes made

prnet cleaned-up successfully


All the hardware

Is your feature request related to a problem? Please describe.
Where can i buy all the hardware with build apollo system, to set with car and test?

Where can i buy all the hardware with build apollo system, to set with car and test?

@imty1000  The current experimental platform is mainly D-kit. You can find more details at https://developer.apollo.auto/apollo_d_kit.html


FBTC

-Need to change as per the latest flow.

No wallet connect QR anymore.

-Should not show if already linked wallet.

This section should not show if the wallet is already linked with FastBitcoins.com
The second line should say "Go to your FastBitcoins.com account on this device and choose Hexa from 'Linked Wallets'. NO Click here needed.


undefined responses on successful POST requests when using instances

Response is always undefined when using an instance. Any idea why?
const apiClient = axios.create({
    baseURL: ...
    headers : {Authorization:"..."}
});

apiClient.post('/path/to/endpoint', payload)
                .then(response=>{
                    console.log(response); // undefined
                })
                .catch(reject)

We need more context to be able to help you. Where are you executing this, browser o Node? Versions? Do you see anything in the network panel?


[Bug]  $this->crud->removeButton('Edit') is not working in version 3.4

Bug report
What I did
??
What I expected to happen
??
What happened
??
What I've already tried to fix it
??
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:

@mosam I am sorry but versions 3.4 is somehow outdated. We had 3.5, 3.6, 4.0.
We are currently on v4.1 with alot of new features it might worth to check it out.
I don't think I can be much help here, try debugging the error message.
Best,
Pedro


connectivity: enable IPv6 ns-lb-with-l7-policy on recent 1.13 release

https://github.com/cilium/cilium-cli/pull/1629 initially limited the IPv6 test to v1.14, as v1.13 was missing some functionality.
But now that v1.13 has https://github.com/cilium/cilium/pull/31161, the IPv6 path should actually work. So let's extend the test coverage.

Leaving this as draft, as Cilium doesn't pull the latest CLI into its v1.13 CI.


[Event Hubs] Concurrent calls to getPartitionProperties() are extremely slow

Concurrent calls to getPartitionProperties() are extremely slow:
const client = new EventHubClient(connectionString, eventHubName);
const partitionIds = await client.getPartitionIds();

// Takes about 100 ms
const partitionsSequential = [
  await client.getPartitionProperties(partitionIds[0]),
  await client.getPartitionProperties(partitionIds[1])
];

// Takes exactly 90 seconds, which seems too close to a round number to be a coincidence.
// Maybe corresponds to an internal timeout?
const partitionsParallel = await Promise.all([
  client.getPartitionProperties(partitionIds[2]),
  client.getPartitionProperties(partitionIds[3]),
]);

Full repro: https://github.com/mikeharder/EventHubsPerf/blob/492df6a017a4aaf33149b340429de6aa58022823/js/event-hubs-consume-perf/concurrentGetPartitionProperties.ts

Background
In event-hubs, we use the RequestResponseLink.sendRequest method to get information from an Event Hub such as the list of partition ids.
When making multiple requests in parallel, we were seeing a significant slowdown in the time it took to to complete the requests vs the time it took to complete them in serial. (#4767 contains examples)
In core-amqp, calling sendRequest will attach a message listener to the amqp receiver, and then a request is sent to the service.
Root cause
The message listener has logic that compares the correlationId from the service with the messageId set on the request, and logs if they don't match.
When multiple requests are sent in parallel, all of their message listeners will receive messages sent by the service (because the amqp receiver is shared). The message listener checks if the response was meant for its message, and logs an error if it does not:
https://github.com/Azure/azure-sdk-for-js/blob/75ff8bff97ffcaf8c9dc5d2afa214b5e2cd28e2b/sdk/core/core-amqp/src/requestResponseLink.ts#L174-L182
The expected behavior would be that that message listener is invoked until either an error from the service is encountered, it receives a response that matches its message, or the request has timed out.
Currently we are removing the message listener from the receiver as soon as the listener is invoked:
https://github.com/Azure/azure-sdk-for-js/blob/75ff8bff97ffcaf8c9dc5d2afa214b5e2cd28e2b/sdk/core/core-amqp/src/requestResponseLink.ts#L145-L147
Since each listener will be invoked with each message, when N requests are made in parallel only 1 will have a matching response and resolve. The rest will be invoked with a response that does not match the message, remove their message listeners, and wait until the timeout is reached.


How to alias a package?

Previously, when we have a same namespace class sits in different dll files we can use extern alias to distinguish them.
I don't know how to deal with nuget package in project.json file.
An example will be
Severity    Code    Description Project File    Line
Error   CS0433  The type 'HMACSHA1' exists in both 'System.Security.Cryptography.Algorithms, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' and 'System.Security.Cryptography.Hashing.Algorithms, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'    Hema.Auth.Identity.DNX Core 5.0

Why the issue was closed? Was it resolved? How?

@alex4998 did you figure this out?

In .NET Core, use "same dll" with multiple version is allowed. because the dll files are no longer sit in bin folder together. It has been referenced as a package. The problem I referenced previously, it was caused by break changes of interface. Somehow, the referenced version hasn't been updated to reflect the changes. For example, we have referenced a package System.Security.Cryptography.Algorithms: "1.0.0.*", which means compatible all the packages <IP_ADDRESS> up, includes beta and alpha. If break changes has been introduced inside any of compatible version. And our system will try match and get the latest package on our system. Then it breaks.

I understand that but it does not explain how to use aliases with referenced assemblies of the referenced package. Once again, my situation is this. I reference Google Drive API v2 package which has a lot of dependencies and one of those dependencies have exactly the same class name which results in a bunch of compiler errors because of the naming collision. Let’s say I have a namespace MyApplication.Library and there is class TaskEx. One of the package dependencies have a namespace System.Threading and there is TaskEx too. In some of my sources I have “using MyApplication.Library” and “using System.Threading” (with this using I didn’t refer to the package dependency assembly, I referred to the system System.Threading but it happened to have the same namespace). In these conditions I’m getting the naming collision errors from the compiler everywhere I’m using TaskEx. With the NuGet v2.* the situation can be easily resolved changing dependent assembly aliases from ‘global’ to let’s say ‘google’ and everything compiles after that. With the NuGet v3.0 I don’t know how to change dependency assembly aliases to fix my problem. So, I’m looking for a workaround and hope on a resolution of this lack of functionality in the future versions.
Thank you,
Alex
From: Yue Zhou<EMAIL_ADDRESS>Sent: Saturday, March 5, 2016 18:09
To: dotnet/core<EMAIL_ADDRESS>Cc: alex4998<EMAIL_ADDRESS>Subject: Re: [core] How to alias a package? (#14)
In .NET Core, use "same dll" with multiple version is allowed. because the dll files are no longer sit in bin folder together. It has been referenced as a package. The problem I referenced previously, it was caused by break changes of interface. Somehow, the referenced version hasn't been updated to reflect the changes. For example, we have referenced a package System.Security.Cryptography.Algorithms: "1.0.0.*", which means compatible all the packages <IP_ADDRESS> up, includes beta and alpha. If break changes has been introduced inside any of compatible version. And our system will try match and get the latest package on our system. Then it breaks.
—
Reply to this email directly or view it on GitHub https://github.com/dotnet/core/issues/14#issuecomment-192764162 .  https://github.com/notifications/beacon/AOUds8D7lmjZAhLqacnDfjgEH31Vq6bCks5pqhsvgaJpZM4Fwv6n.gif

This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

You always can use "using" to alias a namespace. In our source code, on the top using statements section, add "using my = MyApplication.Library", then you can use "my.TaskEx" just like how .NET works before.

Right. It works as a workaround but ideally, of course, I’d like to be able to change aliases on the dependency assemblies. Simply because in this case I don’t need to change a single line in the code. With using aliases I at least need to change all the usings and change the lines referring those usings.
Thanks anyway,
Alex
From: Yue Zhou<EMAIL_ADDRESS>Sent: Sunday, March 6, 2016 16:15
To: dotnet/core<EMAIL_ADDRESS>Cc: alex4998<EMAIL_ADDRESS>Subject: Re: [core] How to alias a package? (#14)
You always can use "using" to alias a namespace. In our source code, on the top using statements section, add "using my = MyApplication.Library", then you can use "my.TaskEx" just like how .NET works before.
—
Reply to this email directly or view it on GitHub https://github.com/dotnet/core/issues/14#issuecomment-193006174 .  https://github.com/notifications/beacon/AOUds9pVQXVd310rtE1HA4uyYi0WYh9Hks5pq1HzgaJpZM4Fwv6n.gif

This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus

In my case the type's fullname is duplicated in two assemblies. And I can't use extern to differentiate.

I think this issue should be open, too. I referenced FSharpx.Extras and FSharp.Control.AsyncSeq which both define a FSharp.Control.AsyncSeq module. There is no way to resolve this issue and I ended up removing FSharpx.Extras. They both have the same full name so aliasing modules (as using ... in C#) does not help.

This should probably be opened in the Nuget/Home repo.

There's a NuGet issue already with the current "workaround" being to write a custom target like
https://github.com/NuGet/Home/issues/4989#issuecomment-311042085

thanks @dasMulli