Default root login and password on GCE manageiq appliance/image

Hi:
Is there anyway to access the console from GCE? I Keep getting permission denied. I've tried admin/password admin/smartvm root/password root/smartvm.
Thanks,
Angel

@Rambo68 For GCE, 'root' account is locked and the only way to access console is to set up SSH key for the instance (https://github.com/ManageIQ/manageiq-appliance-build/pull/136).

I see that. However, would you know how it is done in GCE?
From: Satoe Imaishi<EMAIL_ADDRESS>Reply-To: ManageIQ/manageiq-appliance-build<EMAIL_ADDRESS>Date: Thursday, March 9, 2017 at 2:40 PM
To: ManageIQ/manageiq-appliance-build<EMAIL_ADDRESS>Cc: Rambo68<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ManageIQ/manageiq-appliance-build] Default root login and password on GCE manageiq appliance/image (#197)
@Rambo68 For GCE, 'root' account is locked and the only way to access console is to set up SSH key for the instance (#136).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I assume you're asking where to set up SSH key?  When you create an instance, click "Management, disk, networking, SSH keys" -> "SSH Keys".  You can set up project-wide or instance specific SSH key there.

Yes, I will try again as I have already tried this and it didn’t work.
From: Satoe Imaishi<EMAIL_ADDRESS>Reply-To: ManageIQ/manageiq-appliance-build<EMAIL_ADDRESS>Date: Thursday, March 9, 2017 at 2:48 PM
To: ManageIQ/manageiq-appliance-build<EMAIL_ADDRESS>Cc: Rambo68<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ManageIQ/manageiq-appliance-build] Default root login and password on GCE manageiq appliance/image (#197)
I assume you're asking where to set up SSH key? When you create an instance, click "Management, disk, networking, SSH keys" -> "SSH Keys". You can set up project-wide or instance specific SSH key there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

From: Satoe Imaishi<EMAIL_ADDRESS>Reply-To: ManageIQ/manageiq-appliance-build<EMAIL_ADDRESS>Date: Thursday, March 9, 2017 at 2:48 PM
To: ManageIQ/manageiq-appliance-build<EMAIL_ADDRESS>Cc: Rambo68<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ManageIQ/manageiq-appliance-build] Default root login and password on GCE manageiq appliance/image (#197)
I assume you're asking where to set up SSH key? When you create an instance, click "Management, disk, networking, SSH keys" -> "SSH Keys". You can set up project-wide or instance specific SSH key there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Is there another user I can access from the serial console? The ssh does not seem to be working. I have multiple instances and K8 Clusters I can ssh to just fine.
Thanks,
Angel
From: Satoe Imaishi<EMAIL_ADDRESS>Reply-To: ManageIQ/manageiq-appliance-build<EMAIL_ADDRESS>Date: Thursday, March 9, 2017 at 2:48 PM
To: ManageIQ/manageiq-appliance-build<EMAIL_ADDRESS>Cc: Rambo68<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ManageIQ/manageiq-appliance-build] Default root login and password on GCE manageiq appliance/image (#197)
I assume you're asking where to set up SSH key? When you create an instance, click "Management, disk, networking, SSH keys" -> "SSH Keys". You can set up project-wide or instance specific SSH key there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi:
I wanted to give you an update on your GCE image. I don’t think you have the google cloud tools installed which makes it impossible to login to the console. You can’t SSH into it from gcloud, or from the cloudshell because the GCE tools are not installed. Also, you have the root account locked and no other reference account is listed to permit login. The only account you have listed is admin/smartvm as you know root is locked. I deployed it manually by building an instance and using Ansible to deploy it. All worked fine. Thanks for your assistance.
Cheers,
Angel
From: Satoe Imaishi<EMAIL_ADDRESS>Reply-To: ManageIQ/manageiq-appliance-build<EMAIL_ADDRESS>Date: Thursday, March 9, 2017 at 2:48 PM
To: ManageIQ/manageiq-appliance-build<EMAIL_ADDRESS>Cc: Rambo68<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ManageIQ/manageiq-appliance-build] Default root login and password on GCE manageiq appliance/image (#197)
I assume you're asking where to set up SSH key? When you create an instance, click "Management, disk, networking, SSH keys" -> "SSH Keys". You can set up project-wide or instance specific SSH key there.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

I'm sorry I forgot to update this issue... I tried euwe-2 appliance and confirmed no SSH access.  The kickstart log showed the google compute engine packages are installed, but the console log didn't show setting up instance, which explains why SSH isn't working.
I'll dig into this more. Thank you for reporting the issue.

Thanks my friend. I love the product!
From: Satoe Imaishi<EMAIL_ADDRESS>Reply-To: ManageIQ/manageiq-appliance-build<EMAIL_ADDRESS>Date: Tuesday, March 14, 2017 at 5:47 PM
To: ManageIQ/manageiq-appliance-build<EMAIL_ADDRESS>Cc: Rambo68<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [ManageIQ/manageiq-appliance-build] Default root login and password on GCE manageiq appliance/image (#197)
I'm sorry I forgot to update this issue... I tried euwe-2 appliance and confirmed no SSH access. The kickstart log showed the google compute engine packages are installed, but the console log didn't show setting up instance, which explains why SSH isn't working.
I'll dig into this more. Thank you for reporting the issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi, I think the latest Oparin-1 release has this issue.  Viewing the console logs of machine built using the gce image and can't see the google tools being deployed.  Can't access the VM via SSH.  Using the older Fine-4 image works as expected. Console logs confirm the difference.
I'm just setting up to test and learn and am totally new to the product.


rabbitmq queue monitor + queue stability enhancements

This PR adds several enhancements for RabbitMQ stability.

a max-length policy is set on the /analytics exchange
The RabbitMQ Management console is enabled by default with SSL on port 15672. A rabbitmgmt user is created to access this console.
A Queue Length monitoring gen_server (chef_wm_actions_queue_monitoring.erl). This gen_server periodically connects to the management endpoint to check max-length and current length of the analytics queue. If the queue is at > 80% capacity, a warning is issued via lager. If the queue reaches 100% capacity, toggle a "queue at capacity" flag until messages have been read/purged from the queue. Code that publishes messages to RabbitMQ can check the state of the "queue at capacity" flag before enqueuing.
Queue length statistics are reporting via the _status endpoint.

More details are available in chef_wm_actions_queue_monitoring.erl.

Notes

This PR adds the PropER testing tool, which is GPL V3. HOWEVER, this is a test-only dependency.

SSL for the RabbitMQ Management has been configured to only accept tlsv1.2 and tlsv1.1 (POODLE, BEAST) via:
  {ssl, [{versions, ['tlsv1.2', 'tlsv1.1']}]}

TODO:

[x] tests in chef_wm_status_tests.erl
[ ] integration tests/local rabbitmq setup

This looks good, with some relatively minor comments above.
My only large area of concern is the volume of requests this will be handling.  The timeout option made me think of it, but realistically if we ever hit that timeout we're already going to be in a really bad state.
This is very lightweight as implemented, and I'm probably being overly paranoid - I'd feel better if we had decent integrated load suite that didn't require spinning up a ton of AWS nodes.

thanks for the review @marcparadise @stevendanna, I'll clean things up on Monday.

ping @chef/lob

:+1:


changed date predicate to be today's date

Resolves: #17
Signed-off-by: wadeking98<EMAIL_ADDRESS>

Yes this line can just be removed 👍


Fix bug in parameter analyzer

This is an update to pr https://github.com/MudBlazor/MudBlazor/pull/9031 to fix https://github.com/MudBlazor/MudBlazor/pull/9031#issuecomment-2181709066
It adds the analyzer dll and targets file using an alternative method to avoid the bin directory showing in MudBlazor

Description

How Has This Been Tested?

Tried the analyzer in MudBlazor and Transitively
Type of Changes

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

Checklist

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[X] I've added relevant tests.

This PR looks funny. I guess you did not pull dev before starting a new branch or maybe even reused the old PR branch? It won't make a difference when I squash this, it's just a bit confusing and shouldn't happen in future PRs.

This PR looks funny. I guess you did not pull dev before starting a new branch or maybe even reused the old PR branch? It won't make a difference when I squash this, it's just a bit confusing and shouldn't happen in future PRs.

I used the PR branch but won't do that again if it causes an issue. I know it shows 30 commits and then it's just one change but I know you squash them.

Thanks anyway! Just released this as RC2


VSCode: ENOENT error when deploying war file via Azure App Service extension

Repro steps:

In VSCode -> go to Azure:app service extension
Expand the subscription
Right click the web app -> Deploy to Web App -> Select the war file

Action: appService.Deploy
Error type: Error
Error Message: spawn c:\dev\apps\VSCode1.37.1\resources\app\node_modules.asar.unpacked\vscode-ripgrep\bin\rg.exe ENOENT
Version: 0.15.0
OS: win32
Product: Visual Studio Code
Product Version: 1.37.1
Language: en

Call Stack
Object.t.deserializeSearchError workbench.main.js:4032:757
Promise.all.then.t workbench.main.js:4680:682
process._tickCallback next_tick.js:68:7

Closing as dupe of https://github.com/microsoft/vscode-azureappservice/issues/1092


JFXTabPane in VBox with VGrow Always

Hi
First of all congrats for this amazing library
Just change my developper life :-)
I have an issue using JFXTabPane in SceneBuilder when i put the VGrow ALWAYS
The Gluon SceneBuilder stuck, and not ohter way than killing the task process.
I have an issue using JFXTabPane in SceneBuilder when i put it in a AnchorPane and settings all the Anchor settings (right , top, left, ...)
The Gluon SceneBuilder stuck, and not ohter way than killing the task process.
Have you ever seen this before ?
Thanks

Hello,
Thanks for pointing out the issue 👍 , we will look into it.
Regards,

Hello,
unfortunately we were not able to reproduce the issue using the latest Gluon SceneBuilder, can you retest using the latest SceneBuilder and the latest JFoenix jar.


os-ddclient - no independent ipv6 change detection

Important notices
Before you add a new report, we ask you kindly to acknowledge the following:

[x] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
[x] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
[x] The title contains the plugin to which this issue belongs

Describe the bug
Hello, I have an Internet connection where unfortunately only the IPv6 address changes and not the IPv4. When checking the IP, it seems that only the IPv4 is checked and then no change is detected. Because a set that only IPv6 should be checked unfortunately also does not work.
Expected behavior
The best would be if ipv4 and ipv6 would be checked independently.
Relevant log files
2022-08-05T08:49:57	Notice	ddclient[72095]	32413 - [meta sequenceId="2"] SUCCESS: example.com: skipped: IP address was already set to <IP_ADDRESS>.
2022-08-05T08:49:57	Notice	ddclient[72095]	30872 - [meta sequenceId="1"] SUCCESS: *.example.com: skipped: IP address was already set to <IP_ADDRESS>.
2022-08-05T08:44:57	Notice	ddclient[72095]	7108 - [meta sequenceId="2"] SUCCESS: example.com: skipped: IP address was already set to <IP_ADDRESS>.
2022-08-05T08:44:57	Notice	ddclient[72095]	5782 - [meta sequenceId="1"] SUCCESS: *.example.com: skipped: IP address was already set to <IP_ADDRESS>.
2022-08-05T08:39:57	Notice	ddclient[72095]	78827 - [meta sequenceId="2"] SUCCESS: example.com: skipped: IP address was already set to <IP_ADDRESS>.
2022-08-05T08:39:57	Notice	ddclient[72095]	77281 - [meta sequenceId="1"] SUCCESS: *.example.com: skipped: IP address was already set to <IP_ADDRESS>.
2022-08-05T08:34:57	Notice	ddclient[72095]	22341 - [meta sequenceId="2"] SUCCESS: example.com: skipped: IP address was already set to <IP_ADDRESS>.
2022-08-05T08:34:57	Notice	ddclient[72095]	21148 - [meta sequenceId="1"] SUCCESS: *.example.com: skipped: IP address was already set to <IP_ADDRESS>.
2022-08-05T08:29:57	Notice	ddclient[72095]	37230 - [meta sequenceId="2"] SUCCESS: example.com: skipped: IP address was already set to <IP_ADDRESS>.

Additional context
Add any other context about the problem here.
Environment
newest ddclient 1.8

thank you for openening this issue, I have exactly the same issue, I have a fixed IPv4 address and the IPv6 changes, and ddclient does not send any update for the IPv6 address, since it says IPv4, nothing changed.

I am also a +1 but this might be a distinct issue.
I see "success" messages in the logs indicating that my IPv6 address has been sent to the dynamic DNS provider but the records on their end never change.  The exact same user/password are working for IPv4.
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 11027 - [meta sequenceId="56"] FAILED:   updating someHost.someDynamicDNSDomain.com: Invalid reply.
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 10017 - [meta sequenceId="55"] WARNING:   ERROR: Address <IP_ADDRESS> has not changed.
<...>
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 10017 - [meta sequenceId="43"] WARNING:  REPLIED: HTTP/1.1 200 OK
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 8427 - [meta sequenceId="42"] RECEIVE:  ERROR: Address <IP_ADDRESS> has not changed.
<...>
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 88939 - [meta sequenceId="31"] RECEIVE:  Server: nginx
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 87462 - [meta sequenceId="30"] RECEIVE:  HTTP/1.1 200 OK
<...>
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 85920 - [meta sequenceId="24"] SENDING:  GET /dynamic/update.php?someb64LookingHashHere HTTP/1.0
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 83846 - [meta sequenceId="23"] CONNECTED:  using SSL
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 82198 - [meta sequenceId="22"] CONNECT:  freedns.afraid.org
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 80166 - [meta sequenceId="21"] UPDATE:   updating someHost.someDynamicDNSDomain.com
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 78394 - [meta sequenceId="20"] INFO:     setting IP address to 2001:558:dead:be:eeff:d00d:aabb:ccdd for someHost.someDynamicDNSDomain.com
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 76279 - [meta sequenceId="19"] RECEIVE:  someHost.someDynamicDNSDomain.com|<IP_ADDRESS>|https://freedns.afraid.org/dynamic/update.php?someb64LookingHashHere
<...>
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 52968 - [meta sequenceId="7"] SENDING:   Connection: close
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 52968 - [meta sequenceId="6"] SENDING:   User-Agent: ddclient/3.9.1
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 52968 - [meta sequenceId="5"] SENDING:   Host: freedns.afraid.org
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 52968 - [meta sequenceId="4"] SENDING:  GET /api/?action=getdyndns&sha=b<...>d HTTP/1.0
2022-08-27T18:32:50-07:00	Notice	ddclient[76079]	 50495 - [meta sequenceId="3"] CONNECTED:  using SSL
2022-08-27T18:32:48-07:00	Notice	ddclient[76079]	 44390 - [meta sequenceId="2"] CONNECT:  freedns.afraid.org
2022-08-27T18:32:48-07:00	Notice	ddclient[76079]	 40955 - [meta sequenceId="1"] WARNING:  file /var/tmp/ddclient.cache, line 3: Invalid Value for keyword 'ip' = ''

This log output comes after I disabled the "use ip6only.me" account.

is there any progress here yet ?


Multiple environments require multiple .env files (performance and other issues)

In Laravel 4.x it was possible to have a development and production environment with one configuration file. The framework would detect automatically what should be used according to the host.
With Laravel 5.x it seems I have to take the following approach:

On my local machine a .env file in the root directory with "APP_ENV=local" and other config stuff to run locally.

On my server the same thing with "APP_ENV=production" and the related settings.

So if I deploy my site, I have to watch that I don't overwrite the .env file on the server with my local version.
Is this correct so far or am I missing something here?
The main goal is to keep sensitive data out of version control and have everything in one place.
Following points and questions about this approach are unclear:

The creator of the .env package recommends to NOT use it in production mode (source: https://github.com/vlucas/phpdotenv). The solution in Laravel for this issue would be to hard code every setting across the framework and to make sure that the .env file is not deployed to the server (could be a huge security hole).

If the solution in the point above is used, how would you keep the sensitive data out of version control?

Let's say two different .env files are used (for development and one for the server in production mode), wouldn't that be a performance issue in production since each setting is being called over and over again from the .env file?

This seems like a step back from the 4.x approach where I could have everything configured and done in one place, no need to have two different files with the same name and watch that I don't mix them up or something. And loading one array in .php is also a lot faster than calling one file multiple times.

You should just ensure .env is ignored from your repo and then create the .env file on the server once as part of your initial deployment. I'm not sure how you could end up overriding the production .env with your local .env (I can only imagine that could happen if you're ftping your whole local directory to the production server. But you're not doing that, right? ;)).
The .env file does have to be used in production. You could set the relevant env vars in the virtual host for example, but they aren't loaded when running artisan commands and so everything breaks.
Btw @GrahamCampbell will likely be here in a minute to kindly tell you should be asking questions like this on the forums or slack, for future reference.

Btw @GrahamCampbell will likely be here in a minute to kindly tell you should be asking questions like this on the forums or slack, for future reference.

Yes, please do. Due to very high volume, we can only process isolated bug reports here, and nothing else.


Make the executor sandbox directory cache configurable

Passing build: https://travis-ci.org/twosigma/Cook/builds/241056977

@wyegelwel do you have any feedback on this?

Rebased, this branch is ready for another round of review :)
Passing build: https://travis-ci.org/twosigma/Cook/builds/246065501

Needs rebase

Rebased. Passing build: https://travis-ci.org/twosigma/Cook/builds/248643799

ready for another round, passing build: https://travis-ci.org/twosigma/Cook/builds/249110606

Two small comments, otherwise looks fine.
Larger comment that doesn't need to be resolved in this PR is that adding the cache resulted in a bunch of lines changing just passing the cache through. Can we rework the structure or the way we handle dependencies to remove this need?

@wyegelwel

Can we rework the structure or the way we handle dependencies to remove this need?

Is the plan to define the cache in an atom and then have it initialized by the dependency mechanism?

Addressed feedback, ready for another round. Passing build: https://travis-ci.org/twosigma/Cook/builds/252259247

I agree that this PR isn't the right place to change it, but I feel the same way about waiter. Maybe there is a better solution in clojure but this really smells like a dependency injection thing to me. I think a larger project would be to try to factor things into logical components that you could wire together via the fnk structure, which would probably also help to address the unit test churn we've talked about a few times,


Support for configuring Redis key prefix for each origin

I'm interested in HA trickster setup with Redis cache backend like it's mentioned in https://github.com/Comcast/trickster/issues/214
I would like to have redundant thanos setup instead of one prometheus instance, so I would appreciate possibility to configure key prefix instead of using origin(prometheus) hostname.
I didn't find such option in 1.09, would such solution be acceptable by project?

@elcomtik Thanks for the feedback! I think it would be a great addition to allow for a custom cache key prefix, and should be fairly simple. We will implement this soon and update this issue when it is ready in beta 10.

Thanks for quick response a implementing it so quickly. I will wait for release and then test it in my setup.


dependencies update

@hubertshelley thanks! i had to fix the CI pipeline because my dev tools dropped 3.7 support, but looks good now!

released in 1.2.1


Wireplumber extraConfig does not write a config

Describe the bug
Setting wireplumber.extraConfig does not write a config file
Steps To Reproduce
Steps to reproduce the behavior:

Set options for wireplumber.extraConfig
Rebuild
Nothing happens

Expected behavior
Nix should write a wireplumber config
Additional context
    wireplumber.extraConfig.wireplumber = {
      "wireplumber.settings"."device.routes.default-sink-volume" = "0.0";
      "wireplumber.settings"."device.routes.default-source-volume" = "0.0";
    };

Metadata

 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.56, NixOS, 24.05 (Uakari), 24.05.20241014.c0b1da3`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.8`
 - channels(root): `"nixos-23.11"`
 - nixpkgs: `/nix/store/wdk3xa0vwx7swjdl1samf1bccvyyzfc1-source`

Add a :+1: reaction to issues you find important.

check /etc/systemd/user/wireplumber.service.d/overrides.conf, it should show that wireplumber configs are to a nix-store directory e.g.
Environment="XDG_DATA_DIRS=/nix/store/q45lchmbg047lip6cxnirqcx4cfbhf84-wireplumber-configs/share:/nix/store/61b60y38nk2zgzc3z151qqy86sdfha72-wireplumber-0.5.6/share"

follow that directory's ./wireplumber/wireplumber.conf.d/, and you'll find your configs.

check /etc/systemd/user/wireplumber.service.d/overrides.conf, it should show that wireplumber configs are to a nix-store directory e.g.
Environment="XDG_DATA_DIRS=/nix/store/q45lchmbg047lip6cxnirqcx4cfbhf84-wireplumber-configs/share:/nix/store/61b60y38nk2zgzc3z151qqy86sdfha72-wireplumber-0.5.6/share"

follow that directory's ./wireplumber/wireplumber.conf.d/, and you'll find your configs.

Okay i was able to find it that way, but now i have another issue. Ive put
  services.pipewire = {
    enable = true;
    pulse.enable = true;
    wireplumber.extraConfig.wireplumber = {
      "wireplumber.settings"."device.routes.default-sink-volume" = "0.0";
      "wireplumber.settings"."device.routes.default-source-volume" = "0.0";
    };
  };

in my configuration but the config still states:
 device.routes.default-sink-volume = {
    description = "The default volume for sink devices"
    type = "float"
    default = 0.064
    min = 0.0
    max = 1.0
  }
  device.routes.default-source-volume = {
    description = "The default volume for source devices"
    type = "float"
    default = 1.0
    min = 0.0
    max = 1.0
  }

Probably i just got something wrong in the configuration but could you help me out there?


Added v1 for Fluid + Teams application

In effort of the recipe that integrates Fluid into Teams, we are building a version 1 of an example application that will walk the developers through how the integration works. The goal of this PR are the following:

Create fluid container in the Config page and append the container ID onto the content page URL.
Developer can name the tab in the Config page.
Get and load the container in the content page.
Extract all container related operations into  Util.ts.
Convert all view and SharedMap update as a React component (FluidContent).

The only files edited are package.json, helloWorldTabConfig.tsx, helloWorldTab.tsx, Util.ts, FluidContent.tsx. All other files are generated by Teams default template

are the compile error flashes in the example video resolved?

are the compile error flashes in the example video resolved?

yes it is! Updating webpack.config.js fixed it

Awesome work here Tim! This is shaping up really nicely 😄 I had left some comments on the earlier PR you had posted, would be great to see the same addressed here. Also, just for clarification, the README containing the recipe allowing developers to build this out for themselves starting from the teams boilerplate will be coming in a follow-up, correct?

Thanks for taking a pass Sumedh. I have addressed all the comments you made including hiding the credentials in the .env file. And yes, the README will come as a follow-up. 😀

Looks good! Let's discuss .env storing the azure tenant ID and key later on though. Not a blocker for this PR but I still think it would be good to have! Nice work! 🚢

yup! I currently have the .env approach mentioned in the walk-thru as a note but we can talk about it more


Removal of duplicate options

Test name
Status

upgrade-haproxy
passed

scaling
passed

recreate
passed

storage
passed

haproxy
passed

big-data
passed

scaling-proxysql
passed

init-deploy
passed

self-healing
failed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

limits
passed

monitoring-2-0
passed

smart-update
passed

affinity
passed

one-pod
passed

self-healing-advanced
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

operator-self-healing
passed

users
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup
failed

Test name
Status

upgrade-haproxy
passed

scaling
passed

recreate
passed

storage
passed

haproxy
passed

big-data
passed

scaling-proxysql
passed

init-deploy
passed

self-healing
failed

restore-to-encrypted-cluster
passed

security-context
passed

upgrade-proxysql
passed

limits
passed

monitoring-2-0
passed

smart-update
passed

affinity
passed

one-pod
passed

self-healing-advanced
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

operator-self-healing
passed

users
passed

upgrade-consistency
passed

tls-issue-self
passed

tls-issue-cert-manager
passed

tls-issue-cert-manager-ref
passed

validation-hook
passed

demand-backup
failed


Decipher ASIO SSL error codes to be human readable

Renamed beast::asio::ssl.h to beast::asio:error.h
Added a new function, that returns a human readable message from an SSL error code
Created a unit test for the short read (335544539) SSL error

Reviewers: @rec @vinniefalco

:+1:

@rec Ping!

:+1:  Sorry I missed this!

Can you rebase this down to one change, please?

Rebased

@miguelportilla The commit message should not be in brackets

Fixed.


Use compile-time solutions where possible

Ideas taken from my WIP component-based entity system.
Currently, in anax's systems, processing requires getting the components from the entity.
// pseudocode
void process(Entity& e)
{
    auto& component1 = e.getComponent<T1>();
    auto& component2 = e.getComponent<T2>();
    // ...
    // But we already "know" where component1 and component2 are
}

This is unnecessary.
We can kill two birds with one stone if we use variadic templates to define system requirements instead of ComponentFilter.
// MovementSystem acts on entities that have both CPosition
// and CVelocity but not CStatic
class MovementSystem : System<MovementSystem,
    Requires<CPosition, CVelocity>, Excluding<CStatic>>
{
    // Do not store entities - store tuples of what is needed
    // std::vector<Entity*> entities;
    // Ideally this will be done internally in the System base class
    // Look at my WIP component system for an implementation
    using TupleType = std::tuple<Entity&, CPosition&, CVelocity&>;
    std::vector<TupleType> tuples;

    void process(TupleType& tuple)
    {
         auto& entity = std::get<0>;
         auto& cPosition = std::get<1>;
         auto& cVelocity = std::get<2>;
         // No need to query the entity for components -
         // we can get them more quickly from tuples
    }
};

I am now doing this in 2.0.0. However, I do not use tuples to store the components. I do wonder if it is faster (performance wise) for a tuple, but overall it is a good abstraction in general. Though, if I were to do this, I would probably turn remove the wrapper Entity over Entity::Id and just make Entity be Entity::Id instead.
You can essentially write the above example, like so:
struct MovementSystem : anax::System<anax::Requires<CPosition, CVelocity>, anax::Excludes<CStatic>>
{
    // access via getEntities()
};

Great improvement over the previous syntax/semantics, in my opinion.
I've given a talk at CppCon 2015 last Monday regarding data-oriented component-based entity systems with C++14 (you can find the code/slides here, and a recording of the talk will be updated roughly one month away from now), and I use compile-time solutions there to automatically generate data-structures and bitsets to do entity-matching.
Hope you can find something interesting in the code/slides.


inline usage in cbits/common.h is invalid C99

Newer versions of gcc default to -std=gnu11, which uses C99 inline semantics, while older ones default to -std=gnu89, which uses traditional GNU inline semantics. C99 inline works differently than both C++ and traditional GNU inline -- in particular, it doesn't emit an externally visible symbol for the function unless there's a external inline declaration in one of the .c files.
This means that when compiled with a newer gcc, programs using network-info can fail during the linking step with the following error:
[...](network-unix.o):function add_interface: error: undefined reference to 'wcsempty'
[...](network-unix.o):function add_interface: error: undefined reference to 'wszcopy'
[...](network-unix.o):function count_interfaces: error: undefined reference to 'wcsempty'
[...](network-unix.o):function c_get_network_interfaces: error: undefined reference to 'mbswszcopy'
[...](network-unix.o):function c_get_network_interfaces: error: undefined reference to 'ipv4copy'
[...](network-unix.o):function c_get_network_interfaces: error: undefined reference to 'ipv6copy'
collect2: error: ld returned 1 exit status
`gcc' failed in phase `Linker'. (Exit code: 1)

See https://gustedt.wordpress.com/2010/11/29/myth-and-reality-about-inline-in-c99/, https://gcc.gnu.org/onlinedocs/gcc/Inline.html, https://en.wikipedia.org/wiki/Inline_function#gnu89 and https://stackoverflow.com/questions/16245521/c99-inline-function-in-c-file/16245669#16245669 for more details.
Potential solutions:

add -fgnu89-inline to cc-options
add -std=c99 to cc-options and add external inline declarations for all inline functions to some .c file.
replace inline in common.h with static.

We verified that adding -fgnu89-inline to cc-options fixed the problem for us.

I'm happy to accept this change. My only concern is that I don't have access to a windows box at the moment to test this on. I would expect that -fgnu89-inline should be just fine though.


Update package.jsons

Summary

This PR copies the changes in https://github.com/cerner/terra-toolkit/pull/850 & https://github.com/cerner/terra-application/pull/369  to update the formatting in package.json files to be consistent with the rest of the Terra ecosystem. There are no code changes in this PR.
Testing

This change was tested using:

[ ] WDIO
[ ] Jest
[ ] Visual testing (please attach a screenshot or recording)
[ ] Other (please describe below)
[x] No tests are needed

Reviews
In addition to engineering reviews, this PR needs:

[ ] UX review
[ ] Accessibility review
[ ] Functional review

Additional Details

Thank you for contributing to Terra.
@cerner/terra

Fails
🚫	Please include a CHANGELOG entry for each changed package this PR. Looks like a CHANGELOG entry is missing for:

terra-action-footer
terra-action-header
terra-alert
terra-arrange
terra-avatar
terra-badge
terra-base
terra-breakpoints
terra-button-group
terra-button
terra-card
terra-cell-grid
terra-content-container
terra-core-docs
terra-demographics-banner
terra-dialog
terra-divider
terra-docs
terra-dropdown-button
terra-dynamic-grid
terra-form-checkbox
terra-form-field
terra-form-fieldset
terra-form-input
terra-form-radio
terra-form-select
terra-form-textarea
terra-grid
terra-heading
terra-html-table
terra-hyperlink
terra-i18n
terra-icon
terra-image
terra-list
terra-mixins
terra-outline-view-table
terra-overlay
terra-paginator
terra-profile-image
terra-progress-bar
terra-responsive-element
terra-scroll
terra-search-field
terra-section-header
terra-show-hide
terra-signature
terra-spacer
terra-status-view
terra-status
terra-switch
terra-tag
terra-text
terra-toggle-button
terra-toggle-section-header
terra-toggle
terra-toolbar
terra-visually-hidden-text

Generated by 🚫 dangerJS against 6a12dec

CHANGELOG updates are not needed.


Provide a PSR-16 decorator for zend-cache storage adapters

This patch serves as an alternative to #126, based on a comment by @marc-mabe to that patch.
The patch adds a new class, Zend\Cache\Psr\SimpleCacheDecorator, which accepts a zend-cache storage instance to its constructor, and then proxies to it via the methods that implement the PSR-16 CacheInterface. The approach is simpler than that in #126 as it does not require testing against every adapter; we can test the decorator against a mock of the StorageInterface, validating its behavior. The tests provided also ensure that any exceptions thrown by the underlying storage operations are re-cast to PSR-16 implementations.
This approach may miss a few details; each of @marc-mabe, @kynx, and @boesing raised a few issues in #126 that I am uncertain if this approach covers. I'd love feedback before I merge this.
TODO

[x] Validate keys to ensure they do not contain reserved characters
[x] Validate keys to ensure they do not exceed maximum length
[x] Detect whether the zend-cache adapter requires serialization; if so, serialize values before storage, and deserialize on retrieval.
[x] Implement TTL capabilities per PSR-16:

[x] If a negative or zero TTL is provided, have set() and setMultiple() remove the item(s) from the cache (instead of storing).
[x] If the adapter does not support TTL semantics, have set() and setMultiple() return boolean false for non-null, >0 TTL values.

Pinging @kynx and @boesing for review.

@weierophinney Can we also add this on composer.json?
    "provide": {
        "psr/cache-implementation": "1.0",
        "psr/simple-cache-implementation": "1.0"
    }

@thomasvargiu Done!

The thing that made the PSR-6 adapter such a pain was handling the different limitations of the underlying storage and the different values they can store.
I’m wondering if it would be better to serialise everything up front to avoid those.

I just turned to that section of the specification, and it looks like it may be identical to PSR-6. As such, I'm going to implement the logic found in the PSR-6 adapter with regards to:

determining if serialization is necessary
de/serializing values during set/get(Multiple) operations

The only other consideration is what to do about adapters that do not support per-item TTL, as this is a soft requirement of PSR-16 (see: requirements on set() and setMultiple() with regards to $ttl arguments). If no $ttl argument is sent, then any adapter is valid. However, if one is sent, PSR-16 is clear that the adapter should honor it.
The options I see are:

We raise an exception during instantiation if the adapter cannot support TTL, like we do in the PSR-16 adapter. The downside of this approach is that if the consumer is not using TTL values, then they are excluded from using that adapter for no reason.
We return boolean false from the set() and setItems() operations if a $ttl is provided, but the adapter is not capable of it. A boolean false indicates a failure to cache, which would be valid in cases where we cannot set a TTL.

Considering the idea behind PSR-16 was to make caching simple and to prevent raising exceptions for common operations, I think the second approach likely would be more in the spirit of PSR-16 support, so I'm going to proceed in that direction.

@weierophinney Did you consider to test it using php-cache/integration-tests like PSR-6 tests?

Did you consider to test it using php-cache/integration-tests like PSR-6 tests?

I'll look into it today. I'm not sure if this will be terribly feasible, as we'd need an actual adapter (not a mock one) to easily use those. It may make more sense to wait to do those until we split the adapters into their own repos.

@thomasvargiu —
Regarding this statement:

I'll look into it today. I'm not sure if this will be terribly feasible, as we'd need an actual adapter (not a mock one) to easily use those. It may make more sense to wait to do those until we split the adapters into their own repos.

I've added an integration test for the APC adapter, and discovered a number of things already. One thing interesting: the integration tests are sometimes covering behavior not explicitly detailed in the spec. As examples: they test for generator/iterable arguments to the various *Multiple() methods, which are not explicitly indicated as valid values, but are not excluded, either. Additionally, I'd forgottent that DateInterval values were allowed for TTL values, so I've added functionality for addressing that, too.
As such, I think we definitely need some integration tests in play, as they're helping me refine the adapter. I'll get these in place today.

@weierophinney good, and I agree with you. I think should be better to have an integration test for every adapter like in PSR-6 tests. Then we can decide what to do when some adapter fail.
I don't know what should be better to do when someone sets a TTL on some adapter that doesn't support it.

Initial tests are now in place for APC and APCu adapters; APCu was running fine locally at this point, which is promising!
I also found a bug in the integration tests and reported it: https://github.com/php-cache/integration-tests/issues/92
I'll hammer through the tests for the remaining adapters this afternoon; they should be fairly straight-forward, as I can use the setup logic from the PSR-6 integration tests.

Looks like the bulk of integration test issues are when using setMultiple() with adapters that require serialization; essentially every single one that requires serialization had unserialize() errors, which makes me think that the logic for setMultiple() may need tweaking.

Okay, all feedback incorporated, and no changes at this time that affect tests, which were green on last run!
Going to merge to develop, and will release 2.8.0 next Monday. Please test, and provide feedback if you run into issues!

Hi @weierophinney,
Thanks for starting working at it!

there is a serializer plugin available that can be plugged in into any storage adapters. Maybe it’s better to throw an error if the provided storage adapter doesn’t support all required data types and let the user plugin the serializer plugin into it to make it work with the psr wrapper. I think it was done that way for psr6, too
also now there is one namespace for both psr wrappers. I think it could make sense to plit it into psr6 and psr16 namespaces
on clearing items there is also a ‘clearByNamespaceInterface’ that will remove all items of the current namespace of the storage. As the simple cache wrapper doesn’t has any knowledge about namespaces it only sees the items of the current namespace. I didn’t check the spec fully but I guess this should be preferred on clear as flush removes everything even of other namespaces
on delete there is a concurrent regression. You first check for existence and then delete but the item could be added between both calls. As removeItem return true/false based of if the item was deleted it will throw an error only in case the deletion of an existing item failed. So probably just ignoring the return value and return true in all cases

@marc-mabe Thanks for the feedback!
I've opened #155 to address your second point; however, the approach I took was to use Zend\Cache\Psr\CacheItemPool and Zend\Cache\Psr\SimpleCache to reflect the interfaces being implemented, versus the specification numbers.
I'll start addressing the other three points in the next few days. I'm going to open tickets for each so that others can more easily find the information.


Provide a consistent way to control log verbosity (BP_LOG_LEVEL)

I noticed that the Paketo buildpacks have a consistent way to control the verbosity of log output of their buildpacks via a BP_LOG_LEVEL env var:
https://github.com/paketo-buildpacks/rfcs/blob/main/text/0027-log-levels.md
I think it makes sense for us to have something similar (if not exactly the same).

I was at an authors working group meeting where they talked about it. I think it’s good to have standardization around giving the user control over how much info they want output.
This is related to the display work in libherokubuildpack.
we could put the core of that (or something like it) in libcnb and then build on top of it for libherokubuildpack. I don’t think we need to block that work though.
as a design decision we should ask what our goals are and how much we want to integrate. For example if we can assume a logger/display interface is always present then we could have libcnb internals log (for example maybe we emit what shell commands are being run or files downloaded to “debug” level automatically.
I know that Java suffers from massive outputs. I would start looking there to better understand what our use cases for strategically condensing/reducing/eliminating output are.
The other related idea is to have a standard interface for capturing certain information and emitting it only on failure or error. Since long builds may take 10-20 minutes it is a bad experience to have it fail and have to set a level and re-run just to see if the logs have any extra info.


modify create_batch function

current setup of create batch is to generate a list of key-value pairs that is batched along with the input of the client. we want to remove the automatic generation of these list and batch only those legit transactions from the client since it will reflect as transactions in the blockchain. we need to eliminate these extra function.

here's the flow of this function:


In AWSE the log path name still a bit off

Coordinator we do not include the host name
/var/dremio_efs/log/coordinator/
executors we do
/var/dremio_efs/log/executors/nodeName
so update the magic method here https://github.com/rsvihladremio/dremio-diagnostic-collector/blob/7157485cadf2117fd9c7b41214f0c976f9e0e79c/cmd/local.go#L1052

going to be a bit trickier than I expected because we have to add coordinator detection.I guess we should look through all of the executors and see if the hostname matches, this is still a bit tricky but we can do a best effort all the same


iterate does not read all requested branches

I'm reading multiple root files containing trees. Some of the root files contain branches, which the others don't. I only need selected branches from the root files. Some of the branches I want are only present in some root files. Thus I use uproot.iterate, where the branches argument is a function TBranchMethods ⇒ True or False.
What I would expect is, that the dict yielded by iterate contains the branches as they are available.
But instead the branches inside the dict are determined by the branch availabilities of the first file that was read: When the first file does not have some branches, they are not read for later files that have them; when a later file does not have a branch, an exception is raised by uproot/tree.py.
Everything seems to be caused by lines 178 to 183 in tree.py.
I can not understand this behaviour from the documentation. It also does not make sense to call the function given by the branches argument in every iteration step if the branches are determined by the first call. For my case, the only way I could solve the issue is by splitting the files I have into categories of their available branches and then having a iterate loop for each of the categories. This would be complicate things by a lot.

(I'm about to be out of contact for 24 hours, so I'm afraid a clarification will be all I can provide for now.)
The intention was to provide the subset of branches that exist in all files, as well as verify that their types are consistent (Interpretation.compatible) across the dataset. Some systems would require them to be exactly the same, and uproot may be used to feed into one of those systems. However, it can't look ahead into all files to check for consistency for performance reasons, so that's why it has this narrowing scope. (It can't take away the events it's already delivered!) In the past, it actually raised an error. I just didn't know what to do about these situations—I would think you'd always want all ROOT files to have the same set of branches with the same types.
If this isn't the case, then even the narrowing-scope policy is too limiting, as you say. Maybe what it ought to do is hang onto the original branch request (the branches variable before it's passed into tree._normalize_branches) and reevaluate it without narrowing, maybe without even checking for consistent types. (Existence in some files and non-existence in others is in a sense "changing types.")
I'm moving toward this kind of policy in awkward-array, too: the ChunkedArray currently performs a test to be sure that all chunks have equivalent type (raising an error if it's not), but I'm thinking that this is more trouble than it's worth—in the future, ChunkedArrays will always implicitly have union type. A collection of ROOT files collectively defining a dataset is a chunked array, so I guess the same logic should be applied in uproot.
Since I won't be able to touch this for a while (I'll be busy for the next week and a half), maybe you want to try implementing the more lax policy on your own, as a pull request? You've identified the relevant lines of code. You should be able to remove the whole test (L176-L183) as well as  all references to oldpath and oldbranches in this function. (oldbranches only exists to enforce the policy and oldpath only exists to provide a useful error message.) Then this function (generator, actually) wouldn't be doing much except providing a meaningful globalentrystart, which is useful for iterations over Pandas DataFrames and when reportentries=True. So the function/generator can stay.
You can get your use-case up and running with the knowledge that you won't be dealing with a forked uproot indefinitely—I agree that what you suggest is a better policy and will adopt it (simpler, less restrictive, and if a framework that uses uproot thinks it's too permissive, they can throw their own error).


For csv-based project lists, link_url field doesn't update properly

Our brigade, OpenSMC, uses a google sheets csv file to curate our project list.  For reference, our results in the cfapi can be found here.
Many of our projects don't have websites yet, so the link_url field in the csv is blank.  I've discovered that this causes some unintended results in the cfapi, depending on whether fields are (or were) completed in the csv, the project repo (using the Edit button at the top of the repo page), or in the parent repo if the project is forked:

csv link_url
project repo homepage
(if forked) project parent homepage
cfapi link_url
working as intended?

filled
any
any
csv value
yes

empty (never filled)
empty
empty or not forked
null
yes

empty (never filled)
filled
any
repo value
maybe?

empty (never filled)
empty
filled
parent value
probably not

empty, but previously filled
any
any
last filled csv value
no

In one half-hearted attempt, I tried entering "" or null in the csv for two of the projects.  Of course, the cfapi just interpreted these as strings and displayed them as such.  Now that I've deleted those values, they remain in the cfapi, as described in the last row of the table.
I've taken a peek at run_update.py, but haven't pinpointed the source of the issue yet.

Weird. I'll check it out. In the meantime I reloaded your projects to get rid of that "null". The empty "" is till there for now though.


04/07/2018 23:48 : Create Pull Request for branch prTesting_2018040723 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Add warcli cmd to build docker-compose only

Open to test workflow.
Edit, oh, that doesn't work. Will test in my own branch :)

Looks good for a first stage: testing if the generated docker-compose builds:
https://github.com/willcl-ark/warnet/actions/runs/6121773038/job/16616214444


Update Benchmarking Kafka docs (#87)

Q
A

Bug fix?
no

New feature?
no

API breaks?
no

Deprecations?
no

License
Apache 2.0

What's in this PR?

cherry-pick a028f85016bbe74344df16810f2a568b2973c041 into the master branch
Why?

The steps are outdated
Additional context

Checklist

[x] User guide and development docs updated (if needed)

Question to the reviewers: not sure if want to remove/update the banzai-cli related stuff (I believe they are no longer valid), for example: https://github.com/banzaicloud/koperator-docs/blob/13da74b3f8c730d6e9979dc183bcf7cbc31bfe5b/docs/benchmarks/_index.md?plain=1#L8-L13

We do want to remove it, I have an older PR for that (https://github.com/banzaicloud/koperator-docs/pull/78), but I didn't want to merge it into this PR, but we can do it. It might need some updates.

We do want to remove it, I have an older PR for that (#78), but I didn't want to merge it into this PR, but we can do it. It might need some updates.

Thanks @fekete-robert - wasn't aware of that, I'd say we can merge this one because I tested the actual steps, then we can resolve the conflicts for #78. What do you think?

@panyuenlau Sure, let's do it that way


Examples fail to run with Illegal instruction (core dumped)

Hello,
I found out that leaving enabled the use-simd feature, every example fails to run when compiled in normal unoptimized mode. But only heptagram and drop fails to run when compiled in --release mode.
But disabling the use-simd feature makes them all work in normal mode. But interestingly drop and fishy fails in --release mode.
This may hint to a bug in one of the unsafe code blocks.
GDB output
Since drop fails in 3 of the 4 combinations of feature and mode, this is the relevant gdb output from running them:
With use-simd enabled
cargo build --example drop && gdb ./target/debug/examples/drop
(gdb) run
Starting program: .../footile/target/debug/examples/drop
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGILL, Illegal instruction.
core::core_arch::x86::sse2::_mm_slli_si128_impl (a=..., imm8=8) at /rustc/fc50f328b0353b285421b8ff5d4100966387a997/src/libcore/../stdsimd/crates/core_arch/src/x86/sse2.rs:429
429	/rustc/fc50f328b0353b285421b8ff5d4100966387a997/src/libcore/../stdsimd/crates/core_arch/src/x86/sse2.rs: No such file or directory.

cargo build  --release --example drop && gdb ./target/release/examples/drop
(gdb) run
Starting program: .../footile/target/release/examples/drop
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGILL, Illegal instruction.
0x00005555555613a2 in <footile::gray8::Gray8 as footile::pixel::PixFmt>::over ()
(gdb)

With use-simd disabled
cargo build  --release --example drop && gdb ./target/release/examples/drop
(gdb) run
Starting program: .../footile/target/release/examples/drop
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".

Program received signal SIGILL, Illegal instruction.
0x0000555555560a52 in <footile::gray8::Gray8 as footile::pixel::PixFmt>::over ()
(gdb)

System Info
Ubuntu 18.04  kernel 4.15.0-48-generic
CPU:
processor	: 5
vendor_id	: AuthenticAMD
cpu family	: 16
model		: 10
model name	: AMD Phenom(tm) II X6 1055T Processor
stepping	: 0
microcode	: 0x10000dc
cpu MHz		: 803.788
cache size	: 512 KB
physical id	: 0
siblings	: 6
core id		: 3
cpu cores	: 6
apicid		: 5
initial apicid	: 3
fpu		: yes
fpu_exception	: yes
cpuid level	: 6
wp		: yes
flags		: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp lm 3dnowext 3dnow constant_tsc rep_good nopl nonstop_tsc cpuid extd_apicid aperfmperf pni monitor cx16 popcnt lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw ibs skinit wdt cpb hw_pstate vmmcall npt lbrv svm_lock nrip_save pausefilter
bugs		: tlb_mmatch apic_c1e fxsave_leak sysret_ss_attrs null_seg amd_e400 spectre_v1 spectre_v2
bogomips	: 5625.75
TLB size	: 1024 4K pages
clflush size	: 64
cache_alignment	: 64
address sizes	: 48 bits physical, 48 bits virtual
power management: ts ttp tm stc 100mhzsteps hwpstate cpb

Can you test again with the current master branch?

Ok. I just pulled the latest changes from the master repo, deleted the target dir and re-run the examples.
But it still fails.
current status
All examples fail in debug mode with use-simd enabled:
for ex in $(ls examples); do echo -ne "$ex:\t"; cargo run --quiet --example $(echo "$ex" | cut -d'.' -f1); done
cubic.rs:	Illegal instruction (core dumped)
curve.rs:	Illegal instruction (core dumped)
drop.rs:	Illegal instruction (core dumped)
figure.rs:	Illegal instruction (core dumped)
fishy2.rs:	Illegal instruction (core dumped)
fishyp.rs:	Illegal instruction (core dumped)
fishy.rs:	Illegal instruction (core dumped)
heptagram.rs:	Illegal instruction (core dumped)
letter.rs:	Illegal instruction (core dumped)
over.rs:	Illegal instruction (core dumped)
quad.rs:	Illegal instruction (core dumped)
round.rs:	Illegal instruction (core dumped)
stroke2.rs:	Illegal instruction (core dumped)
stroke.rs:	Illegal instruction (core dumped)
teeth.rs:	Illegal instruction (core dumped)

Two examples fail in release mode with use-simd enabled:
$ for ex in $(ls examples); do echo -ne "$ex:\t"; cargo run --release --quiet --example $(echo "$ex" | cut -d'.' -f1); echo; done
cubic.rs:
curve.rs:
drop.rs:	Illegal instruction (core dumped)

figure.rs:
fishy2.rs:
fishyp.rs:
fishy.rs:
heptagram.rs:	Illegal instruction (core dumped)

letter.rs:
over.rs:
quad.rs:
round.rs:
stroke2.rs:
stroke.rs:
teeth.rs:

Four examples fail in release mode with use-simd disabled:
$ for ex in $(ls examples); do echo -ne "$ex:\t"; cargo run --release --quiet --example $(echo "$ex" | cut -d'.' -f1); echo; done
cubic.rs:
curve.rs:
drop.rs:	Illegal instruction (core dumped)

figure.rs:
fishy2.rs:	Illegal instruction (core dumped)

fishyp.rs:	Illegal instruction (core dumped)

fishy.rs:	Illegal instruction (core dumped)

heptagram.rs:
joseluis.rs:
letter.rs:
over.rs:
quad.rs:
round.rs:
stroke2.rs:
stroke.rs:
teeth.rs:

All examples pass in debug mode with use-simd disabled:
$ for ex in $(ls examples); do echo -ne "$ex:\t"; cargo run --quiet --example $(echo "$ex" | cut -d'.' -f1); echo; done
cubic.rs:
curve.rs:
drop.rs:
figure.rs:
fishy2.rs:
fishyp.rs:
fishy.rs:
heptagram.rs:
joseluis.rs:
letter.rs:
over.rs:
quad.rs:
round.rs:
stroke2.rs:
stroke.rs:
teeth.rs:

I think I may have found the problem -- can you try the latest version from the master branch?  There was a .cargo/config file left over from before I really understood how Rust SIMD programming worked.  Sorry, I don't have a CPU without SSSE3 to test myself.

Very good news. I confirm it now works well for me in every combination. Thank you!


Equivalent of path-as-is option in curl

In curl there is the --path-as-is option:

Tell curl to not handle sequences of /../ or /./ in the given URL path. Normally curl will squash or merge them according to standards but with this option set you tell it not to do that.

Currently, httpie does not send paths like /../../../../../ to the server but resolves and removes them locally.
Sending such sequences can be useful during security testing, e.g. checking directory traversal vulnerabilities.
I would like to request a similar option as curl's --path-as-is.

The dot segment removal is automatically applied by the upstream urllib3 library in its parse_url() implementation. Which is called from requests’s PreparedRequest.prepare():
Currently, neither library provides a way to disable the normalisation, sadly.
urllib3==1.25.8
requests==2.23.0

$ http --offline example.org/foo/../bar/

GET /bar/ HTTP/1.1

Good to know.
In the meantime, one can partially workaround this by manually URL-encoding / as %2f if needed.

Actually, this was already requested for the requests library in https://github.com/psf/requests/issues/5289
The issue contains a solution approved by a maintainer.

@exploide the linked issue includes a comment with a decent workaround, so I’ve just pushed support for --path-as-is  to master.

Awesome. That was fast. Thanks! :+1:


Multi shot/aimed shot blizzard bar option

https://gyazo.com/8d962848e5366f8216c15f5bfe04b3ac
it currently shows any hunter using aimed shot/multishot as my own bar/overwrites my bar, i have tried every version and disabled/removed/renamed my wtf and still same issue

Quick update: if rapid fire is active the bar does not take into account the shortened cast time.
not sure with hawk proc tho

Quick update: if rapid fire is active the bar does not take into account the shortened cast time.
does not work with aspect of the hawk buff "quick shots" either.

It doesnt work with ClassicShots addon either. I think it has to be coded manually with both buffs, or all haste buffs. If he adds the Rapid Fire, he needs to add the Hawk buff and then both buffs combined aswell.

I know that haste and aimed shot are not working but i need to level my hunter to at least level 21 for testing (aimed shot + imp hawk). And i currently don't have the time to do so. Thats why development on this addon is slow.

Is there any way we could help with that? Is it possible to take the info from wow head? If you want, you could add me on discord karYzan#2081 and I could test it for you as many times as you want! I'm almost always online. Thanks again for this addon by the way

Should be fixed.
See #32 and #43


I need to give warning 10 seconds before the counter ends

How about to use countdown.update and event.offset property (http://hilios.github.io/jQuery.countdown/documentation.html#events).
I believe that what you are trying to achieve is very similar to the Advanced example:
http://hilios.github.io/jQuery.countdown/examples/advanced-coupon-site.html
Just use the same approach to change the output or even create a new HTML.
Cheers


dart2js: confusing noSuchMethod & Function.call when using mirrors

The following example:
@MirrorsUsed(targets: const ['A', 'B', 'C', 'dart.core.Function'], override: '*')
import 'dart:mirrors';

class A {
  int m(int a, int b) => 3;
}

class B implements A {
  Function f;
  noSuchMethod(i) => reflect(f).invoke(#call, i.positionalArguments).reflectee;
}

class C {
  String call(String paramC1, {String paramC2}) => paramC1;
}

main() {
  reflectClass(C).newInstance(const Symbol(''), []).reflectee;
  var mock = new B()..f = (_a,_b) => 4;
  mock.m(0, 3);
}

Produces this error:
NoSuchMethodError: method not found: 'call'
Receiver: Closure 'main_closure'
Arguments: [0, paramC2: 3]
NoSuchMethodError: method not found: 'call'
Receiver: Closure 'main_closure'
Arguments: [0, paramC2: 3]
    at dart.wrapException (http://localhost:8001/out.js:1499:17)
    at main_closure.dart.Object.noSuchMethod$1 (http://localhost:8001/out.js:5980:17)
    at main_closure.dart.Object.call$2$paramC2 (http://localhost:8001/out.js:6040:21)
    at CachedInvocation.dart.CachedInvocation.invokeOn$2 (http://localhost:8001/out.js:2322:32)
    at JsClosureMirror.dart.JsInstanceMirror._invoke$4 (http://localhost:8001/out.js:4153:39)
    at JsClosureMirror.dart.JsInstanceMirror.invoke$3 (http://localhost:8001/out.js:4065:21)
    at JsClosureMirror.dart.JsInstanceMirror.invoke$2 (http://localhost:8001/out.js:4068:21)
    at B.dart.B.noSuchMethod$1 (http://localhost:8001/out.js:3039:34)
    at B.dart.Object.list$2 (http://localhost:8001/out.js:6095:21)
    at dart.main (http://localhost:8001/out.js:3024:12)

The call of mock.m should be dispatched to invoke the closure set under B.f. For some reason, we are dispatching this to call C.call. If you comment out the call definition, the code works without a problem.
I still need to look further but maybe this is an issue with CachedInvocation? I need to look further, but @rakudrama, if you see anything obvious from this let me know.
For context: this is a small repro for a problem a user ran into when using angular, di, and mock packages. Class C and the newInstance call for C are derived from di/angular, the noSuchMethod definition in B was derived from how the mock package handles when...thenCall.

Lots of red herrings in there. Here is a simplified example:
@MirrorsUsed(targets: const ['A', 'B', 'C', 'dart.core.Function'], override: '*')
import 'dart:mirrors';

class A { foo(x) => 499; }
class C { foo({x}) => 22;  }

class B { noSuchMethod(i) => print(i.positionalArguments); }

confuse(x) { return x; return x; }

main() {
  confuse(new C());
  print(reflect(new A()).invoke(#foo, [3]));
}

No need to go through noSuchMethod. (Just need to have it in the program).
No need to deal with closures. Same bug happens with normal functions.
No need to reflect on C. Just instantiating is enough.

So what happened: dart2js stores a mapping from name to encoded name in the output. The bug is/was that it had the named and the unnamed function name mapping to the same encoded name. However, we use that same map to build the inverse map. And that one then only worked if we run through the names in the right order. (If they were in a different order, the named one would overwrite the "good" name). (see screenshots).
Bad case (where we overwrite the unnamed name). Look for "call$2" and "call$2$paramC2":

Good case (where we run through the names in the "right" order):

There are several ways to fix this:

split the named and unnamed mapping so that we don't run into this issue when we do the inverse mapping. This would basically require to split the JS_EMBEDDED_GLOBAL('=Object', MANGLED_NAMES).
filter the named-argument function names out. They are only used in one direction and we can ignore them for the inverse mapping.

The latter is more hackish but much easier:
$ git diff master
diff --git a/sdk/lib/_internal/compiler/js_lib/js_names.dart b/sdk/lib/_internal/compiler/js_lib/js_names.dart
index 708b873..26b3656 100644
--- a/sdk/lib/_internal/compiler/js_lib/js_names.dart
+++ b/sdk/lib/_internal/compiler/js_lib/js_names.dart
@@ -113,10 +113,14 @@ class _LazyReflectiveNamesMap {
    List keys = JS('List', 'Object.keys(#)', _jsMangledNames);
    for (String key in keys) {
      var reflectiveName = JS('var', '#[#]', _jsMangledNames, key);
-      // Filter out all non-string values to protect against polution from
-      // anciliary fields in [_jsMangledNames].
-      bool filter = JS('bool', 'typeof # !== "string"', reflectiveName);
-      if (filter) continue;
+      // Filter out all non-string values to protect against pollution from
+      // ancillary fields in [_jsMangledNames].
+      if (JS('bool', 'typeof # !== "string"', reflectiveName)) continue;
+      // Filter out named-argument function names. Unnamed names are shorter
+      // and we just need to make sure not to overwrite one that already exists.
+      var old = result[reflectiveName];
+      if (old != null && old.length < key.length) continue;
+
      result[reflectiveName] = JS('String', '#', key);

      String getterPrefix = JS_GET_NAME(JsGetName.GETTER_PREFIX);

Thanks Florian! Great to see this simplified further.
I'm not familiar enough with the uses of the inverse map - why is it OK to leave out the named-argument function from it? (we can also take this offline and discuss when we meet tomorrow)

The inverse map is used to find the corresponding JS function when trying to do reflective operations. However, for more complicated calls (like with named arguments) we have a call* function that deals with them. Even if a call$2$arg function exists the reflective operation automatically goes through call*.
(Fwiw: I didn't know/remember this either, and discovered it when debugging).
You can see that in the js_helper.dart applyFunctionWithNamedArguments which refers to JS_GET_NAME(JsGetName.CALL_CATCH_ALL).
Note that _genericApplyFunctionWithPositionalArguments refers to "call*" directly. Imho this is a mistake. It should go through the JS_GET_NAME as well.

@sigmundch is this likely to land in 1.14?

Thanks for checking. I believe it's unlikely - I removed the milestone


Add support for using sub-folder as jest root path

One scenario is: The project is a maven java project. Frontend code and
package.json/.jestrc files are in sub folder. Need to add a new config
'rootPath' to support run jest command in the subfolder

is this duplicating jest's rootDir config?


Network Timed Out

I'm unable to connect to docker, I'm getting the below error.
Network timed out while trying to connect to https://index.docker.io/v1/repositories/library/ubuntu/images. You may want to check your internet connection or if you are behind a proxy.

If you are behind a proxy please check the wiki for possible solutions:
https://github.com/docker/kitematic/wiki/Common-Proxy-Issues-&-Fixes


Update VSCode Notebooks API

All the changes are here (last 4 commits, starting from WIP):
https://github.com/rebornix/vscode-jupyter/commits/rebornix/fixVSCAPI
These changes must be applied to master after we have created a release branch.

[x] Import from vscode & not from ..../vscode-proposed
[x] Update Python extension notebook API
[x] Update renderers extension

Not sure if there is a specific validation on this. But resolving due to notebooks now working in insiders and the API update PRs.


CakePHP 5?

Will cakelte be updated for CakePHP5?

That depends on AdminLTE, when they release a new version, we will update too, thank you!
https://github.com/ColorlibHQ/AdminLTE

I will start working on this soon, any help is welcome

I will start working on this soon, any help is welcome

not sure I'm clever enough, although very happy to help test in any way

version 2.x  released!
https://github.com/arodu/cakelte/releases/tag/v2.0.0


feat(react-server): trigger error overlay on server error

Having an overlay for unexpected errors would be nice, but probably it breaks CI. So, let's hold this off for a moment.
Also, obviously this hot.send is too early on ssr since client isn't even rendered yet. So, we maybe still better to use a general solution like https://github.com/hi-ogawa/vite-plugins/pull/272 since react server error would be replayed on client anyways.
Screenshot

Superseded by https://github.com/hi-ogawa/vite-plugins/pull/293


Module

https://github.com/ichiban/prolog/issues/292
This PR implements a SICStus style module system.

This PR lacks the concept of type-in module https://github.com/ichiban/prolog/issues/292#issuecomment-1706185539
#307 has type-in module and is preferable.

This PR lacks the concept of type-in module https://github.com/ichiban/prolog/issues/292#issuecomment-1706185539
#307 has type-in module and is preferable.


unified drain connection pools in the cluster manager to avoid duplicate code and logic

Commit Message: unified drain connection pools in the cluster manager to avoid duplicate code and logic
Additional Description:
Commit Message: unified drain connection pools in the cluster manager to avoid duplicate code and logic.
Risk Level: mid. core code update.
Testing: may be some more unit tests are necessary?
Docs Changes: n/a.
Release Notes: n/a.
Platform Specific Features: n/a.

Waiting for #23180 to be merged.

Hi, @mattklein123 could you take a look to this PR first when you have free time? Thanks. :) Does this make sense?
This PR mainly does follow changes:

split close and drain logic more clearly by explicit parameter.
unified all core logic of draining and closing to single drainOrCloseConnPools.
avoid closing tcp connections when CLOSE_CONNECTIONS_ON_HOST_HEALTH_FAILURE is set and the ClusterManagerImpl::drainConnections is called.

/retest

This code is covered pretty good by current tests.
Although I have a worry. This PR change/fix a simple behavior, but no one test was broken. Seem at least I need to add a test for this scene. 🤔
see
avoid closing tcp connections when CLOSE_CONNECTIONS_ON_HOST_HEALTH_FAILURE is set and the ClusterManagerImpl::drainConnections is called.


converting portable to .net standard hang VS for several seconds

drop used

git clone https://github.com/dotnet/roslyn-analyzers
and sync to 43d9e94a8cd44b9fb3a9fa204b096fce5f2c85b4
go to either Analyzer.Utilties or Dependencies\CodeAnalysis and convert the portable projects to .net standard project through property page.
it will make vs to hang for several seconds.

This issue was moved to dotnet/roslyn#16910

This issue was moved to dotnet/roslyn#16911


Customize neuro executable

To be able to use neuro --verbose --show-traceback in tests.

Adding crucial change: after update tensorbard 1.15 -> 2.0, the default value --host changed to locahost, thus forbidding all external connections.


feat: Add gcds-notice documentation

Summary | Résumé
Add documentation for the gcds-notice component.

Fixes https://github.com/cds-snc/design-gc-conception/issues/1287

To-do

[x] Fill in component preview box in base files.
[x] Use version of @cdssnc/gcds-components with published gcds-notice.

I found this behaviour, which might be from the component itself.

@daine That is the expected behaviour of the component.

I created a ticket to document the behaviour


No MQTT messages

Hi.
I created an ARM64 image and set with docker compose with environmental variables for mqtt host, port and credentials but I got no MQTT messages at all.
My compose:
mqttui:     image: xorguy/mqttui_arm64:1.0.0     container_name: mqttui     environment:       - MQTT_BROKER=<IP_ADDRESS>       - MQTT_PORT=1883       - MQTT_USERNAME=user       - MQTT_PASSWORD=password     ports:       - 5876:5000     logging:       driver: "json-file"       options:         max-file: "5"   # number of files or file count         max-size: "100m" # file size
Do you have any idea why it seems to not connect to my MQTT broker?

Having same issue

I have added more logs and a debug bar, @xorguy can you try with the latest release?

Same thing here.  I pulled the latest docker image but no messages.  Not sure of the others but I require a username and password for connection to my broker.

Can you clarify what you mean by added a debug bar?
I also have a username/password. I dont see any messages or any new debug logs. All I see in the logs is for http requests which I assume is from me loading the website.

Same thing here. I pulled the latest docker image but no messages. Not sure of the others but I require a username and password for connection to my broker.

I have tested this and it should fail if your broker require username and password and you should see that in the debug bar, can you provide more details about your setup?

Botton right there is a button

Same thing here. I pulled the latest docker image but no messages. Not sure of the others but I require a username and password for connection to my broker.

I have tested this and it should fail if your broker require username and password and you should see that in the debug bar, can you provide more details about your setup?

I realizedI was on the wrong version which would explain why I didnt see the debug button. You should update the readme to either use the latest or use 1.0.2 as the tag.
Anyways even with the debug button I do not see any errors. My mqtt setup is basically the simplest possible. I am running mosquitto broker with a static IP on the default port, with username/password required for authentication. I have multiple other devices connected without any issue.
For sanity sake I also went into the container installed ping and confirmed the container was able to hit the mqtt server as well.

Same thing here. I pulled the latest docker image but no messages. Not sure of the others but I require a username and password for connection to my broker.

I have tested this and it should fail if your broker require username and password and you should see that in the debug bar, can you provide more details about your setup?

I realizedI was on the wrong version which would explain why I didnt see the debug button. You should update the readme to either use the latest or use 1.0.2 as the tag.
Anyways even with the debug button I do not see any errors. My mqtt setup is basically the simplest possible. I am running mosquitto broker with a static IP on the default port, with username/password required for authentication. I have multiple other devices connected without any issue.
For sanity sake I also went into the container installed ping and confirmed the container was able to hit the mqtt server as well.

How are you running the app? Are you using Docker Compose? Have you confirmed that the environment variables are set correctly inside the container?

I am using docker and just pulling your existing container on docker hub. And yes just double checked env variables are being set

Hello ! Same issue for me.
I tried on unraid to log my mqttt server on home assistant too.
I tried different things like changing networking type (host, bridge, etc), but same issue.

Hi,
Using MQTT with authentication can be tricky, as you can use the same username/password on multiple connection, if you have different clientIDs.
Here I don't see any option to set a clientID separated from the username.
It can be why no log on happen.
It can also be version of MQTT protocol, V3 vs V5, it should also be and option to test.

Hi,
After testing, problem seems to be that we don't do in the main code as name = "app" and not "main" because application is started by flask.
So in file app.py, line 147, if I replace:
if __name__ == '__main__':
by
if __name__ == 'app':
My installation works.
Also I replace line 25 with :
mqtt_client = mqtt.Client(client_id='mqttui',
                         transport='tcp',
                         protocol=mqtt.MQTTv311,
                         clean_session=True)

to be sure to be compatible with my broker.

Hi everyone,
I've released version 1.3.0, which addresses the reported issues with MQTT connections and improves overall configuration flexibility.
Key improvements include:

Better handling of MQTT connections with support for v3 and v5
Flexible configuration for both development and production environments
Improved error handling for non-UTF-8 encoded MQTT messages

Please try this latest release and let us know if you still experience any issues. You can pull the new version using:
docker pull terdia07/mqttui:v1.3.0
If problems persist, please provide:

Your docker-compose.yml or docker run command
Any error messages or logs
Details about your MQTT broker setup

Screenshots for debug bar when wrong credential is used

Successful connection

Just pulled it and it works like a champ!

Works for me too ! Thanks !

Confirmed working now

Hi,
Version 1.3.0 work fine for me. Thanks !
Please update the instructions for docker in README.md to point to version 1.3.0


pipenv.patched.notpip._internal.exceptions.InstallationError

Running pipenv install cartopy in a new directory gives:
Creating a Pipfile for this project…
Installing cartopy…
Adding cartopy to Pipfile's [packages]…
✔ Installation Succeeded
Pipfile.lock not found, creating…
Locking [dev-packages] dependencies…
Locking [packages] dependencies…
✘ Locking Failed!
Traceback (most recent call last):
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/resolver.py", line 126, in <module>
    main()
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/resolver.py", line 119, in main
    parsed.requirements_dir, parsed.packages)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/resolver.py", line 85, in _main
    requirements_dir=requirements_dir,
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/resolver.py", line 69, in resolve
    req_dir=requirements_dir
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/utils.py", line 726, in resolve_deps
    req_dir=req_dir,
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/utils.py", line 480, in actually_resolve_deps
    resolved_tree = resolver.resolve()
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/utils.py", line 385, in resolve
    results = self.resolver.resolve(max_rounds=environments.PIPENV_MAX_ROUNDS)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 102, in resolve
    has_changed, best_matches = self._resolve_one_round()
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 206, in _resolve_one_round
    for dep in self._iter_dependencies(best_match):
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 301, in _iter_dependencies
    dependencies = self.repository.get_dependencies(ireq)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 234, in get_dependencies
    legacy_results = self.get_legacy_dependencies(ireq)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 426, in get_legacy_dependencies
    results, ireq = self.resolve_reqs(download_dir, ireq, wheel_cache)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 297, in resolve_reqs
    results = resolver._resolve_one(reqset, ireq)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/notpip/_internal/resolve.py", line 260, in _resolve_one
    abstract_dist = self._get_abstract_dist_for(req_to_install)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/notpip/_internal/resolve.py", line 213, in _get_abstract_dist_for
    self.require_hashes
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/notpip/_internal/operations/prepare.py", line 294, in prepare_linked_requirement
    abstract_dist.prep_for_dist(finder, self.build_isolation)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/notpip/_internal/operations/prepare.py", line 127, in prep_for_dist
    self.req.run_egg_info()
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/notpip/_internal/req/req_install.py", line 474, in run_egg_info
    command_desc='python setup.py egg_info')
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/notpip/_internal/utils/misc.py", line 705, in call_subprocess
    % (command_desc, proc.returncode, cwd))
pipenv.patched.notpip._internal.exceptions.InstallationError: Command "python setup.py egg_info" failed with error code 1 in /tmp/tmpbwps_nlhbuild/cartopy/
File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/resolver.py", line 126, in <module>
    main()
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/resolver.py", line 119, in main
    parsed.requirements_dir, parsed.packages)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/resolver.py", line 85, in _main
    requirements_dir=requirements_dir,
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/resolver.py", line 69, in resolve
    req_dir=requirements_dir
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/utils.py", line 726, in resolve_deps
    req_dir=req_dir,
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/utils.py", line 480, in actually_resolve_deps
    resolved_tree = resolver.resolve()
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/utils.py", line 385, in resolve
    results = self.resolver.resolve(max_rounds=environments.PIPENV_MAX_ROUNDS)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 102, in resolve
    has_changed, best_matches = self._resolve_one_round()
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 206, in _resolve_one_round
    for dep in self._iter_dependencies(best_match):
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/piptools/resolver.py", line 301, in _iter_dependencies
    dependencies = self.repository.get_dependencies(ireq)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 234, in get_dependencies
    legacy_results = self.get_legacy_dependencies(ireq)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 426, in get_legacy_dependencies
    results, ireq = self.resolve_reqs(download_dir, ireq, wheel_cache)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/piptools/repositories/pypi.py", line 297, in resolve_reqs
    results = resolver._resolve_one(reqset, ireq)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/notpip/_internal/resolve.py", line 260, in _resolve_one
    abstract_dist = self._get_abstract_dist_for(req_to_install)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/notpip/_internal/resolve.py", line 213, in _get_abstract_dist_for
    self.require_hashes
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/notpip/_internal/operations/prepare.py", line 294, in prepare_linked_requirement
    abstract_dist.prep_for_dist(finder, self.build_isolation)
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/notpip/_internal/operations/prepare.py", line 127, in prep_for_dist
    self.req.run_egg_info()
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/notpip/_internal/req/req_install.py", line 474, in run_egg_info
    command_desc='python setup.py egg_info')
  File "/home/ilja/.local/lib/python3.6/site-packages/pipenv/patched/notpip/_internal/utils/misc.py", line 705, in call_subprocess
    % (command_desc, proc.returncode, cwd))
pipenv.patched.notpip._internal.exceptions.InstallationError: Command "python setup.py egg_info" failed with error code 1 in /tmp/tmpbwps_nlhbuild/cartopy/

How can I check how setup.py egg_info failed since that directory doesn't exist when pipenv returns?
Pipenv version: '2018.11.26'
Pipenv location: '/home/ilja/.local/lib/python3.6/site-packages/pipenv'
Python location: '/usr/bin/python3'
Python installations found:

3.6.8: /usr/bin/python3.6m
3.6.8: /usr/bin/python3
2.7.15: /usr/bin/python

PEP 508 Information:
{'implementation_name': 'cpython',
 'implementation_version': '3.6.8',
 'os_name': 'posix',
 'platform_machine': 'x86_64',
 'platform_python_implementation': 'CPython',
 'platform_release': '4.20.11-100.fc28.x86_64',
 'platform_system': 'Linux',
 'platform_version': '#1 SMP Wed Feb 20 15:51:24 UTC 2019',
 'python_full_version': '3.6.8',
 'python_version': '3.6',
 'sys_platform': 'linux'}

Pipenv–specific environment variables:
Debug–specific environment variables:

PATH: /usr/local/bin:/usr/bin:/bin:/usr/local/sbin:/usr/sbin:/home/ilja/bin:/home/ilja/.local/bin
SHELL: /bin/bash
LANG: fi_FI.UTF-8
PWD: /tmp/test

Contents of Pipfile ('/tmp/test/Pipfile'):
[[source]]
name = "pypi"
url = "https://pypi.org/simple"
verify_ssl = true

[dev-packages]

[packages]
cartopy = "*"

[requires]
python_version = "3.6"

Thanks for the report! The issue is tracked in #2791.


[My contacts] Contact images are missing

Info:

only upon ajax load,

Steps to recreate

Go to /
Login
Land on dashboard
Open notes category
Unfold Upload menu (might not be necessary but who knows - there is some js as well)
Open contacts

In other cases it works fine.
For example Achievments -> Contacts

There is definitelly some issue with files path.
Whenever i enter from url like:

/no-slash
/no-slash-here-to

It works
But crashes in case of:

/i-have/two-slashes

Cannot recreate this bug on dev

Fixed: ae990f07edfe43e1d01000439b413b2bfd390d20


open json flatlist clicked URL on browser

I'm fetching JSON data using api  key which contains Name, Rating and URL. I have flatlist on react-native which will display Fetched Name, Rating and all.I successfully get json data and already show it in a flatlist. Now my requirement is that when I click on flatlist it should open the URL fetched from JSON on browser.

import {Linking} from 'react-native';
Linking.openURL(url)
      .catch( (err) => {
        // handle error
      });

Thanks alot.
On Tue, Oct 16, 2018 at 10:59 PM Emtiaj Hasan<EMAIL_ADDRESS>wrote:

import {Linking} from 'react-native';
Linking.openURL(url)
.catch( (err) => {
// handle error
});
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/21277#issuecomment-430499187,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXxHN3spC2lE0VBLoUHwLA7ODDqyNnGcks5ulsc1gaJpZM4W11LJ
.


:robot: Add bytecodeviewer.vm

Automated PR from https://github.com/mandiant/VM-Packages/issues/76 :rocket:

Unsupported package type, see https://github.com/mandiant/VM-Packages/issues/76#issuecomment-1250760598

😞

Closes #76


Add group and peer variants to tailwind plugin

Is your feature request related to a problem? Please describe.
I wanna style based on group and peer states
Describe the solution you'd like
Add group and peer variants in tailwind plugin
Describe alternatives you've considered
Manually add theses variants in my tailwind configuration
Additional context

Just for curiosity:
const variants = [
  "focus",
  "hover",
  "disabled",
  "invalid",
].map((variant) => [
  [`${prefix}-${variant}`, `[data-${variant}]`],
  [`${prefix}-not-${variant}`, `:not([data-${variant}])`],
]).flat();

matchVariant(
  "group",
  (value, { modifier }) =>
    modifier ? `:merge(.group\\/${e(modifier)})${value} &` : `:merge(.group)${value} &`,
   { values: Object.fromEntries(variants) },
);

Hi, thanks for reporting the issue, I will add group and peer variants in the next version.
However there will be some breaking changes in v0.6.0 related to styling : hover, focus, focus-visible and active data-attributes will no longer exist and you will need to use the native css selector or tailwind equivalent.

Hi, thanks for reporting the issue, I will add group and peer variants in the next version.
However there will be some breaking changes in v0.6.0 related to styling : hover, focus, focus-visible and active data-attributes will no longer exist and you will need to use the native css selector or tailwind equivalent.

Yeah, I've followed the discussion in Discord. My package relies on this handlings but I'm comfortable with the changes.

added in v0.6.0.


Rename can't work correctly after jadx start

I use jadx built from the rename branch.
When I use Rename instantly after jadx start, only the current name is changed, all the other references of this name remain as before.
After I use  Find Usage or Go to declaration, Rename can work correctly.

Looks like this was fixed in PR #910.


Add integration tests for /tekton/debug/scripts

/area testing
AFAIK the integration tests work by checking if TaskRuns/PipelineRuns have reached a desired state, based on which the tests are marked as success or failure.
To test scripts in /tekton/debug/scripts dir in the TaskRun Pod, first we would need the TaskRun Pod running with the breakpoint(s) in place. Then, we need to run exec commands allowing us to run scripts in the container(s) with breakpoint. Thus helping us assess the state/logs of the TaskRun after, based on the commands we have run.
How can this be achieved ? What are the possible problems we could face while writing these tests ?

cc @afrittoli

/remove-lifecycle rotten
This is still needed

/lifecycle frozen


cuelang.org: YAML documentation

The https://cuelang.org/docs/integrations/yaml/ page, the Create and Parse subsections show JSON output, not YAML.

@retnuh - thanks for raising this. We finally got to address this as part of the new site. Please take a look at https://cuelang.org/docs/concept/how-cue-works-with-yaml/ and let us know what you think.


Opening vpn and it sends me straight to top up i cant import my backup key from my first computer

Describe the bug
A clear and concise description of what the bug is.
-on my first pc when i downloaded the vpn it chose to import the backup key and now when i open it on my second pc it sends me straight to top up
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
id expect to open up and see import backup key not top up
Logs
Attach logs (app, node, supervisor) to the issue. Where to find the logs: https://github.com/mysteriumnetwork/mysterium-vpn-desktop#logs
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete t
main.log
renderer.log

he following information):

OS: [e.g. Windows 10]
App Version [e.g. 4.1.0]

Additional context
Add any other context about the problem here.

It looks like an Identity is already in use. If you do not have any balance on that identity and would like to delete it, you can run RD /S %HOMEDIR%\.mysterium on command prompt. Then, open the app again and you should see the back up button


Require dask[array] in dask[dataframe]

To keep the requirements DRY, just require dask[array] in dask[dataframe].

[ ] Closes #xxxx
[ ] Tests added / passed
[ ] Passes pre-commit run --all-files

FWIW tested installing dask[complete] locally (as it requires dask[distributed] and both of those require dask[array]) and it worked fine

cc @jrbourbeau

@jrbourbeau could you please review?

@jrbourbeau would you be able to look at this?

Thanks James! 🙏


[test-infra][e2e] make sure to test until the latest DiemVersion

The original e2e tests are hardcoded to test up to version 2 while the
latest DiemVersion is at 3. This commit ensures that the e2e tests will
at least attempt to test with whatever the latest DiemVersion is.
Unfortunately, there is no upgrade path to version 3 yet so this version
is actually ignored in e2e tests. Nevertheless, it might still be good
to have the code here and once we have the upgrade path to version 3,
the e2e test executor will automatically pick it up.

Motivation
Ensure consistency between e2e tests versions and max diem version. Accidentally found this while investigating why my e2e tests replayer is not picking up the trace anymore.
Have you read the Contributing Guidelines on pull requests?
Yes
Test Plan
CI

Keep it for a while now, might be useful for 1.4 release. Removing the stale tag.

@runtian-zhou let me know if this PR is still useful for the 1.4 release. If not, feel free to close it :)

Subsumed in #9243 and the token is passed to @runtian-zhou.


[NEW SHEET] Cloudbreaker Alliance

Submission Checklist
Required

[x] The pull request title clearly contains the name of the sheet I am editing.
[x] The pull request title clearly states the type of change I am submitting (New Sheet/New Feature/Bugfix/etc.).
[x] The pull request makes changes to files in only one sub-folder.
[x] The pull request does not contain changes to any json files in the translations folder (translation.json is permitted)

New Sheet Details

The name of this game is: < Cloudbreaker Alliance >  (i.e. Dungeons & Dragons 5th Edition, The Dresden Files RPG)

The publisher of this game is: < Don't Stop Thinking > (i.e. Wizards of the Coast, Evil Hat)

The name of this game system/family is: < Cloudbreaker Alliance > (i.e. Dungeons & Dragons, FATE)

[x] I have followed the Character Sheets Standards when building this sheet.

[x] I have authorization from the game's publisher to make this an official sheet on Roll20 with their name attached.
[x] This game is not a traditionally published game, but a copy of the game rules can be purchased/downloaded/found at: < https://cj-leung.itch.io/cloudbreaker-alliance >
[ ] This sheet is for an unofficial fan game, modification to an existing game, or a homebrew system.

Changes / Description

Character Sheet Info Roll20 Internal Use only.

hello @Wagii!
Can you please rename cloudbreaker_alliance.json to sheet.json? This is a required file and the naming is important for our processes to work correctly. Thank you!

@NBrooks-Roll20 Completely forgot that this one file had a naming convention, sorry for that ~
Renaming done.