Error when logging in the first time...

Did you check the FAQ & Troubleshooting section for answers to common questions and issues?

Yes/No

Describe the issue

I use the provided password and username for admin and get this error every time: SyntaxError: JSON.parse: unexpected character at line 1 column 1 of the JSON data.

Diagnostic Information

Run ./deploy.sh -d and paste the output below:

==== Docker Information ====
Detected runtime: docker (Docker version 24.0.2, build cb74dfc)
Detected compose: docker compose (Docker Compose version v2.18.1)
   Runtime state: OK

==== System Information ====
      OS: Linux
  KERNEL: 5.19.0-23-generic (x86_64)
HOSTNAME: OK
   SHELL: bash
  MEMORY:
               total        used        free      shared  buff/cache   available
Mem:           465Mi       305Mi        13Mi        24Mi       146Mi       114Mi
Swap:             0B          0B          0B

DISTRO:
----------------------------
PRETTY_NAME="Ubuntu 22.10"
NAME="Ubuntu"
VERSION_CODENAME=kinetic
UBUNTU_CODENAME=kinetic
----------------------------

==== Lemmy-Easy-Deploy Information ====
Version: 1.2.6

IMAGE                                CREATED         STATUS
caddy:latest                         4 minutes ago   Up 4 minutes
ghcr.io/ubergeek77/lemmy-ui:0.18.0   4 minutes ago   Up 4 minutes
ghcr.io/ubergeek77/lemmy:0.18.0      4 minutes ago   Up 4 minutes
asonix/pictrs:0.4.0-beta.19          4 minutes ago   Up 4 minutes
postgres:15-alpine                   4 minutes ago   Up 4 minutes

Integrity:
    789dff42875ab8c43692ddeef7600ef3b3c0a5abf24d84efe6cdae49a46e7ce7  ./deploy.sh
    1e9b0c0988998dcc33cb0fbfdb0e1679229424e724f898b797380adc7d102446  ./templates/Caddy-Dockerfile.template
    c1202e70662dd2228da36a35a0f38ec8fc81bec8964d7315d02e8671a58dd7d7  ./templates/Caddyfile.template
    2537678c7971df36c1ed95f4228d3cfcb15bb4a28a60d939eaf8dd75b5d64a36  ./templates/cloudflare.snip
    c494a610bcb4cd1cfc0a4fe4fb0f6d437b2a84a0ad1625daee240e6dd6f1c910  ./templates/compose-email-volumes.snip
    c9cb4c5fee12930e17798a02ae1bd12e2dc69e149a394c24511bc9d4e6b776d4  ./templates/compose-email.snip
    d9928baea61975bd432e1a4a7439c04468547c9b42e2bb483c6f18d9438665eb  ./templates/docker-compose.yml.template
    a74770730fd0e809d44e5247e1300be04c2b664be13d06bfec00296e3e63861b  ./templates/lemmy-email.snip
    c834cdce9eaf77f38155b404724fdfe66845575386ee516987452aa715642a6f  ./templates/lemmy.hjson.template

Custom Files:
*** No custom files ***

==== Settings ====
        CLOUDFLARE: No
 CADDY_DISABLE_TLS: false
   CADDY_HTTP_PORT: 80
  CADDY_HTTPS_PORT: 443
 LEMMY_TLS_ENABLED: true
      ENABLE_EMAIL: false
         SMTP_PORT: 25
    ENABLE_POSTFIX: false
POSTGRES_POOL_SIZE: 5

==== Generated Files ====
Deploy Version: 0.18.0;0.18.0

total 36K
drwxr-xr-x 2 0 0 4.0K Jul  6 07:47 caddy
-rw-r--r-- 1 0 0   32 Jul  6 07:47 caddy.env
-rw-r--r-- 1 0 0 1.7K Jul  6 07:47 docker-compose.yml
-rw-r--r-- 1 0 0   50 Jul  6 07:47 lemmy.env
-rw-r--r-- 1 0 0  475 Jul  6 07:47 lemmy.hjson
-rw-r--r-- 1 0 0   49 Jul  6 07:47 pictrs.env
-rw-r--r-- 1 0 0   36 Jul  6 07:47 postfix.env
-rw-r--r-- 1 0 0   51 Jul  6 07:47 postgres.env
-rw-r--r-- 1 0 0   14 Jul  6 07:48 version

When you access Lemmy from your browser, do you use the exact domain you have set in LEMMY_HOSTNAME exactly

Yes, and when I enter the domain the page loads perfectly,

with no ports set?

I don't know how to do that so, no?
I'll have to try the commands later today and I'll get back then.
It's a digital ocean droplet with (what is supposed to be) 2GB of ram. Not sure why it shows less. I rebuilt the droplet dozens of times because this process is such a mess. I wouldn't imagine that would do anything to the VM allocation but maybe it's shared?

I tried to run the curl resolve HTTPS and it does nothing at all. It's frozen. I had to restart the SSH after a few minutes. And the only error is:

lemmy-easy-deploy-lemmy-1  | 2023-07-06T19:03:33.039550Z  WARN Error encountered while processing the incoming HTTP request: lemmy_server::root_span_builder: Origin is not allowed to make this request

Ok, that's what I thought. You are encountering a known Lemmy issue that will be fixed in 0.18.1:
https://www.github.com/LemmyNet/lemmy/pull/3421
As for HTTPS not working, is it possible you do not have HTTPS certificates? This situation seems a bit strange to me.
When you go to the browser, do you access Lemmy like this:
https://LEMMY_HOSTNAME

or like this?
https://LEMMY_HOSTNAME:443

If your instance is not available to the public at exactly ports 80 and 443, not only will you see the error you are having, but Caddy will also be unable to request HTTPS certificates.
I am not familiar with firewall rules on DigitalOcean, but is it possible you are forwarding some non-80/non-443 port to your instance, and accessing it directly like in my second example above?

I just type in the domain, and the browser adds the https to the front of it. I definitely did not implement my own port forwarding of any kind. I have tried using all 3 of Lemmy's guides and none of them addressed port forwarding. I've watched several tutorials (that are now deprecated) that use digital ocean and the ONLY thing they modified in the droplet was the DNS A record. And I start with a completely fresh Ubuntu 22.10 build then apt-get updates/upgrades.
I would like to add that your method has gotten me farther than anyone else! And your steps were so easy to follow and did everything you said I should expect. I wish Lemmy made theirs like yours. And I envy your expertise with GNU!

I'm glad this project got you the furthest!
As a last resort, you can try the latest RC that has the CORS error fix:
./deploy.sh -l 0.18.1-rc.10 -w 0.18.1-rc.11 -f

There is still the question of why this is happening in the first place, since I still have no idea why this is happening, but this could solve it for you!

Well, the only thing that happens outside of your guide is when I do apt-get upgrade, it asks if I want to keep the original ssh settings. Otherwise, I wait for that to finish then go straight into your guide. Were there any other dependencies that a practiced linuxer would know to do first?
This is the process that I use to install docker: https://docs.docker.com/engine/install/ubuntu/
I start with running the removal line and then into the 3 main install blocks and then docker ce. I finish with the hello world test and it works every time. Then it's right back to your guide. I'll verify later today that my ram is 2GB. And I'll try the latest RC. I am getting so excited. I've never done anything like this before.

Well, the only thing that happens outside of your guide is when I do apt-get upgrade, it asks if I want to keep the original ssh settings. Otherwise, I wait for that to finish then go straight into your guide. Were there any other dependencies that a practiced linuxer would know to do first?

Nope, you can just accept the default there, that wouldn't impact everything. And my script will warn you if any commmands it needs are missing. It's pretty lightweight, it only needs Docker.
I'm glad you're using the official version of Docker! The Ubuntu version causes quite a few headaches 😅
Sounds like you did everything right to me, at least as far as this script is concerned. I don't have a DigitalOcean account, but maybe they route things weirdly and don't pass a header or something. Who knows.
But based on what you have told me, I am 99% sure if you install the latest RC like I posted above, this should fix everything for you. And if it doesn't, I might be able to help more, but at that point it's probably just a bug in Lemmy itself.
Fingers crossed that works for you!

Same issue even after latest RC. The only difference is when I click "login" after entering the correct admin credentials, the login turns into a spinning arrow and then does nothing else, just spins. If I click it again, I get the error message.

Unfortunately, I do not know what else to suggest, I am very sorry :(
You could take a look at the proxy (Caddy) logs to see what information that provides. If you are truly using rc.10, which had the CORS fix, then it means the Lemmy backend isn't being sent the right header from the UI for some reason.
I am by no means a perfect developer, but there is very little in my script here that could cause something like that. All this does is make a copy of the official Lemmy docker-compose.yml with autogenerated files that make the configuration go smoothly. I have tested on many different environments across different server hosts and architectures, with many users reporting success, but nothing like this has ever happened. Sadly, you may need to file an official Lemmy bug about this.
As a longshot, is your hostname (cat /etc/hostname) anything that would conflict with Lemmy? Such as being named lemmy (lowercase), lemmy-ui, or your Lemmy domain name. If so, I would recommend changing it first and then redeploying.
Finally, have you tried on other hosting providers besides DigitalOcean? I can tell you that this script has several reports of success on Linode and AWS, and personally I test on Vultr which works well. Perhaps there is something odd about DigitalOcean's routing.

HEY!!!
I rebuilt the image, did everything again, then ran the RC update and it worked!!! I'm logged in!!! Check it out: Alaska.Community
Thank you so much!

That's great news! It really was that CORS stuff after all! I'm glad to hear you got running!
Once 0.18.1 is released officially, don't forget to run ./deploy.sh -f to install it. You will need the -f since you installed rc versions manually (but if you forget, it's ok, the script tells you what to do if you run it without it).
Enjoy Lemmy and welcome to the Fediverse!


Keyboard Manager - possibility to differentiate between keyboard layouts

Description of the new feature / enhancement
Current behavior is:

Will remapping work if I change my input language?
Yes it will. Right now if you remap A to B on English (US) keyboard and then change the language setting to French, typing A on the French keyboard (Q on the English US physical keyboard) would result in B, this is consistent with how Windows handles multilingual input.

However I propose to make this configurable. There could be a switcher in settings to turn on/off whether remapping are only local, for the current keyboard setup, or global. For the reason, see the next point.
Scenario when this would be used?
During my day, I have to constantly switch between my Slovak and English keyboard layout as one I use in communication and the second when developing.
It could be easily solved by PowerToys - I'd simply remap few keys and shortcuts (e.g. ``` or ;) and keep using Slovak keyboard.
However sometimes I really do want to switch my keyboard but now my English layout is broken as my "Slovak fixes" affect English layout as well.
Supporting information
No response

This looks  related https://github.com/microsoft/PowerToys/issues/14850

/dup #33774


Sampling from constrained regions takes long time

Does anyone have a guess on why initial_design takes so long here?
import GPyOpt
num_init = 2
space =[{'name': 'x1',      'type': 'continuous', 'domain': (-10.,10.)},
{'name': 'x2','type': 'continuous', 'domain': (-10.,10.)},
{'name': 'x3',  'type': 'continuous', 'domain': (-10.,10.)},
{'name': 'x4',  'type': 'continuous', 'domain': (-10.,10.)}
]
constraints = [{'name': 'constr_1', 'constraint': 'x[:,1] - 0.60'},
{'name': 'constr_1', 'constraint': '-x[:,1] + 0.57'},
{'name': 'constr_1', 'constraint': 'x[:,0] - 9.0'},
{'name': 'constr_1', 'constraint': '-x[:,0] + 8.75'},
{'name': 'constr_1', 'constraint': 'x[:,2] + -1.60'},
{'name': 'constr_1', 'constraint': '-x[:,2] - 1.57'}
]
feasible_region = GPyOpt.Design_space(space = space, constraints = constraints)
initial_design = GPyOpt.experiment_design.initial_design('random', feasible_region, num_init)

So the reason this happens is the way constraints are actually enforced. Simple idea:

Until we have requested amount of samples, do:
Generate a sample
See if it satisfies all constraints
2.1. If it does, add to a list of samples
2.2. If it does not, reject sample
Go to 0

So the more constraints there is, and the tighter they are, the longer it may take to generate samples to satisfy them all.
I don't believe there is an easy way to fix this behavior, but if anyone has ideas, please bring them forward.

Seems like a simple solution might be akin to the following:

Assume x\in R^2 for simplicity
x0\in [x00, x01], x1\in [x10, x11]
x0+x1\ge 1

This equates to:

x0\in [x00, x01]
x1\in [max(x10, 1-x0), x11]

And that representation of the valid subspace can be sampled without rejection sampling.


AWS Security Group created with rules open to the world

When deploying CP4D onto AWS and creating the OpenShift cluster a Security Group is created with 'rules open to the world'  This violates the AWS client security enforcement policy and is immediately removed, as well as triggering an email to the account owner informing them of the incident.
Security Groups MUST be created with least privileged principles so only the require ports and hosts are specified.
This requires an immediate fix.

For OpenShift deployments, Cloud Pak Deployer follows the standard steps for IPI installations in the OpenShift documentation.
If the customer has specific guidelines on how security groups must be created, they can create the AWS resources and deploy OpenShift using their own standards. Once created, Cloud Pak Deployer can be used to deploy the Cloud Pak software.


Swift3.0

Migrated project to support Swift 3.0

we'll merge the other swift 3 branch, thanks for the work @jeksys


VS Code not recognizing a git repo workspace

VSCode Version:

Version 1.12.2
Commit 19222cdc84ce72202478ba1cec5cb557b71163de
Date 2017-05-10T13:16:25.899Z
Shell 1.6.6
Renderer 56.0.2924.87
Node 7.4.0

OS Version: Archlinux ( Linux crom 4.10.13-1-ARCH #1 SMP PREEMPT Thu Apr 27 12:15:09 CEST 2017 x86_64 GNU/Linux )
GIT: ```
git --version
git version 2.13.0

Steps to Reproduce:

1. Open project workspace
2. no repository detection

Some workspace are without problem, but somehave this detection problem.

Can you share a screenshot?
Can you reproduce with the latest insider release?

With insider release it looks like everything works so far ...

Great!


[5.2 Models] Cannot get value from numeric-named columns

Laravel Version: 5.2
PHP Version: 7.0.8
Database Driver & Version: Mysql 14.14 Distrib 5.7.15

Description:
using laravel models, I'm unable to read values from a number-named table, i opened a thread on stackoverflow with all the information needed, link is here stackoverflow
Steps To Reproduce:
Create a table with number-named columns (not all)
Create a model for that table
Try to print out a single field (e.g. $row->{'200'})

just submitted a PR for a fix, but the fix will be available in laravel 5.3 only since 5.2 is not supported anymore, I advise that you start upgrading to 5.3 asap

no prob, thank you


New bash versions don't like current setup-env.sh

https://github.com/AMDResearch/omnitrace/blob/2718596e5a6808a9278c3f6c8fddfaf977d3bcb6/cmake/Templates/setup-env.sh.in#L4
On a from-source version of Linux (running GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)), I'm seeing an issue with the current setup-env.sh where it exits with:

"/home/amd/omnitrace does not exist"

Some light debugging, and I've found that this version of bash does not seem to like the code-pattern of:
BASEDIR=$(cd ${BASEDIR}/../.. && pwd)

Not 100% sure why (wasn't able to find any Bash 5 info on this), but:
BASEDIR=$(realpath ${BASEDIR}/../..)

seems to work insteadm

Yeah, this should work. It’s technically not portable since realpath is a Linux command, not UNIX, e.g. there is no realpath tool on macOS, but since we don’t support macOS and don’t have any plans to do so, I’ll default to it if I can detect the exe exists


Modify webpack-pwa-manifest config to support iOS icon

Describe in detail the problem you had and how this PR fixes it
The auto-generated icon for Code Server on iPad and other iOS devices was partially broken and unreadable. This change makes use of the existing support in webpack-pwa-manifest to assign the real app icon to the appropriate meta tag in the app HTML file.
Is there an open issue you can link to?
https://github.com/cdr/code-server/issues/802

Thank you for your contribution @admvx.
However, WebpackPwaManifest isn't used in v2 so this PR is not necessary anymore. @code-asher should it be added back somewhere or is there a new mechanism?

No sweat, thanks for following up! This would still be useful to me, so I have an update that doesn't use WebpackPwaManifest - PR on the way :)


Drop OpenIndiana slaves

The builder is offline since the beginning of June.
Previous discussions on python-dev:

September 2016: OpenIndiana and Solaris support
https://mail.python.org/pipermail/python-dev/2016-September/146538.html
April 2015: MemoryError and other bugs on AMD64 OpenIndiana 3.x
https://mail.python.org/pipermail/python-dev/2015-April/138967.html
September 2014: Sad status of Python 3.x buildbots
https://mail.python.org/pipermail/python-dev/2014-September/136175.html

cc @zware and @jcea.


Dynamic device list in "Scan Network"

@cdnicoll I know that the "Scan Network" feature hasn't been implemented yet, but when you do, can you please show a dynamic list of devices on the Scan Network screen (refreshed roughly once every two seconds)?
Per #138, I've edited the mock data script to generate...

two new devices every 10 seconds, up to 30 devices
traffic to/from all devices continuously

Note the difference in the device list between the Scan Network screen and the Dashboard screen is as follows:

The device list in Scan Network shows all devices on the network, whether the user decides to inspect them (i.e., checking the boxes) or not. SQL equivalent: SELECT * FROM device_info
The device list in the Dashboard shows just inspected devices: SELECT * FROM device_info WHERE is_inspected = 1

Thanks for the update @cdnicoll!
I do see that...

the main dashboard shows devices that are being inspected
the Scan Network screen shows all devices
toggling on/off devices in the Scan Network screen results in devices being add/removed from the main dashboard

One thing that I'm not yet seeing is the auto refresh of devices. The mock data script generate...

two new devices every 10 seconds, up to 30 devices
traffic to/from all devices continuously

... which reflects the actual case where a real user first starts running Inspector. It takes time to discover devices in a real network. Also, devices come and go (e.g., a guest visiting).
In the current UI, I'd have to manually refresh the page to see new devices. It'd be helpful if you could automatically update the device list, both in the main dashboard and in the "Scan Network" screen.

Should auto refresh every 30 seconds now

Not really. 30 seconds in, and I see a blank screen:
https://www.loom.com/share/6ed0270de1df400a8dc93cfd7fa2a92c
In the above video, I was running generating the fake data from scratch, while testing the UI. After about 30 seconds, the screen went blank, and Chrome showed errors.
Not sure what's going on @cdnicoll

@crazyideas21 I pushed a fix for a few other things, but this was adjusted within the latest PR. Can you try it again and let me know?

After the page automatically refreshes itself, I'm still seeing a blank screen.
Here's a screenshot after the page automatically refreshes itself, when I'm seeing a blank screen:

After I manually refresh the page again, the page seems fine, as shown below:

But when the page automatically refreshes, we're back to the blank screen problem.
The left side shows the output of yarn dev. I made sure to pull the latest and did yarn install:all and yarn prisma:generate before running yarn dev.

I am testing against the latest version in the cr-dev branch with the mock data; the same problem persists:

The yarn dev output doesn't seem to include any errors:

To reproduce the observation above:

Pull the latest cr-dev branch.
Generate mock data with python3 generate_mock_data.py.
Set up the UI: yarn install:all, followed by yarn prisma:generate.
Run yarn dev.

Problem fixed. Looks like I have to do yarn client:build first before doing yarn dev per @cdnicoll

I've updated the README per https://github.com/nyu-mlab/iot-inspector-client/commit/2ca874332be80de69f454cf3b83320b00e270a8f /cc: @cdnicoll


Update pybind11 to ~=2.11

Tries to update pybind11 to the latest version to see what happens.
Could close https://github.com/quantumlib/Stim/issues/623.

I'm so sorry, I didn't realize this was a Google product and requires signing a CLA. For personal reasons, I don't really want to do that. I don't think change is really copyrightable, but I understand there's process. I'm going to close this PR due to that.


Swift icon

No icon for Swift (or Objective-C).
Wiki Commons has the logo in the public domain:
https://commons.wikimedia.org/wiki/File:Swift_logo.svg

Also, logo + wordmark
https://commons.wikimedia.org/wiki/File:Swift_logo.svg#/media/File:Swift_logo_with_text.svg

+1

+1

I've added the swift icon in this commit, it'll be included in the next release.


[test] Extend Set, Dictionary test suite

Reinstate bucket-level tests for collision handling (by abusing _rawHashValue(seed:))
Cover new index validation functionality with new crash tests
Additional tests for Set.update(with:)

rdar://problem/44802560

@swift-ci test


PR: Make running a single line work on partial statements (IPython console)

Description of Changes

This was a very confusing and continuous source of frustration for newbies, so I decided to fix it for Spyder 6.

A couple of gifs to show how it works:

Issue(s) Resolved

Fixes #4431.
Affirmation
By submitting this Pull Request or typing my (user)name below,
I affirm the Developer Certificate of Origin
with respect to all commits and content included in this PR,
and understand I am releasing the same under Spyder's MIT (Expat) license.

I certify the above statement is true and correct:

Hello @ccordoba12! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file spyder/plugins/editor/widgets/base.py:

Line 519:9: E731 do not assign a lambda expression, use a def

Nice work! In the second example, I would have expected Spyder to execute lines 2+3; why is it waiting for line 4?

Nice work!

Thanks @jitseniesen!

In the second example, I would have expected Spyder to execute lines 2+3; why is it waiting for line 4?

Because the print in line 4 is at the same indentation level as the for loop in line 2, which means they are part of the same code block.
So, the way I implemented this feature is that we execute code when we find an empty line or when a line is at a lesser indentation level than the initial one (which means we are at a different code block).
A couple of other gifs to clarify that:

I understand it now. It's not  what I expected. I'd have thought that if the user press F9 on a line that is not a complete statement, Spyder would execute the statement that contains the line. Instead, in this PR the user should keep pressing F9 until a DEDENT or an empty line is encountered. To be honest, I am afraid that this might be just as confusing as the existing behaviour, but I'm curious what others think.

I'd have thought that if the user press F9 on a line that is not a complete statement, Spyder would execute the statement that contains the line.

That's what was suggested on issue #4431, but it's not easy to implement because it'd require to determine the scope of the line to do it. And what should we do in the case of nested for loops, as those shown above? Should we go up or down in the scope when trying to run an inner loop?

To be honest, I am afraid that this might be just as confusing as the existing behaviour, but I'm curious what others think.

What I noticed is that users are baffled when trying to run a single, incomplete but valid line and get a SyntaxError in return. This PR address that by not running those lines but instead leaving them as "pasted" in the console, so they can keep pressing F9.

So gave a check to the original issue and seems like the idea is for the Run line functionality to run full statements, right?
Thinking about the approach here, seems like there are still cases where the Run line functionality could end up triggering a syntax error. Like, taking as an example a code snippet from the added tests, if we have something like:
for i in range(2):         # 1
    print('foo')           # 2
    for j in range(2):     # 3
        if j > 0:          # 4
            print(j)       # 5
        else:              # 6
            print('bar')   # 7
print('baz')               # 8

If you start to use the Run line functionality from line 6 (the else) you can end up pressing F9/triggering Run line three times to end up getting a syntax error. Maybe we should add somehow a way to detect that an initial line to be run will end up in such an error and then prevent running such lines and trying to go for the next line?
Overall seems like the approach here could be in a way an improvement to the run line functionality, but still has some behaviors which could be not so intuitive (like having to press multiples times) and seems to me that it does not completly cover the original issue (although I havent checked myself how RStudio handles this to be honest) :thinking:
Maybe could be worthy to discuss this on a dev meeting?


Broken Item Scripts

When an item is crafted, such as:
pet_rock:
  type: item
  no_id: true
  material: "i@stone"
  display name: '<&r>Pet Rock'
  lore:
  - '<&7>A pet rock. Be'
  - "<&7>careful it doesn't"
  - '<&7>sneak away!'
  recipe:
  - i@stone|i@stone|i@stone
  - i@stone|i@stone|i@stone
  - i@stone|i@stone|i@stone

you are able to take an infinite number of items out of the outcome slot in the crafting table, and it doesn't take any items from the crafting grid.
I'm also having problems with one of my other food related scripts, but that's a different story.

@Morphan1 any ideas on this?

Isn't this the normal behaviour? :D i take away the stuff with the take command

I'm seeing the same thing with new shapeless_recipes. It doesn't /always/ happen though, just sometimes.
@Morphan1 halp

I committed basic protection, but we really need a proper fix. @Morphan1 please halp

Is this resolved in the latest builds?


Change friendship db table name?

Hey.
I just was curios and wanted to ask, if it was possible to change the table name of the friendships without having to extend the model and creating a custom migration? Its no big deal if not, but I thought I'd bring it up anyway ^^.
Kind regards, Ingwie

Hi,
I can add a config file so you can change the database table but I don't think there are other options to configure that's why I have not done it already.
I will check it out when I have some free time,
Thanks for your feedback.

You can change the names in de core files of the plugin, but I don't recomment that...

Hi, i am still new to Laravel and found this awesome package, However a new friend request returns this on the profiles..
[{"id":2,"sender_id":3,"sender_type":"App\User","recipient_id":1,"recipient_type":"App\User","status":0,"created_at":"2016-03-12 18:42:10","updated_at":"2016-03-12 18:42:10"}]
How do i get the relevant user for instance the sender id is 3 but i want to display his name how do i get that from the above ?

Please check this test

@hootlex as @nikolaynesov said, his PR allows  to change friendship db table name (See this line). So this issue should be close.


Add Fingerprint field to VMware form in add provider modal

Resolves #159.
I'm not sure if "Fingerprint" is sufficiently descriptive for the field name in the UI, @fdupont-redhat @vconzola @jortel any thoughts on that?

I'm sure "Fingerprint" is not sufficient as a field label, but don't know what is. :-) @jortel @fdupont-redhat What should this field be called?

To be precise, it should be "Certificate SHA1 Fingerprint", but it's probably too long.

Nope, not too long, and it's perfectly unambiguous. Thanks @fdupont-redhat .

Perfect. Thanks @fdupont-redhat @vconzola

Updated the field name, this is ready to go.


bug: Unrecognized mobile platform for ALPS X23

Bug Report
Ionic version:
[x] 4.11.0
Current behavior:
Application downloaded from Google Play Store
Using a ALPS X23 phone (A phone of a user, i don't have this phone)
this.platform.is('android')
return false
Using Device ionic native library
this.device.manufacturer
return ALPS
this.device.model
return X23
Expected behavior:
this.platform.is('android')
return true
Ionic info:
Ionic:

   Ionic CLI                     : 5.4.2 (/usr/local/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.11.0
   @angular-devkit/build-angular : 0.803.8
   @angular-devkit/schematics    : 8.3.8
   @angular/cli                  : 8.3.8
   @ionic/angular-toolkit        : 2.0.0

Cordova:

   Cordova CLI       : 9.0.0<EMAIL_ADDRESS>   Cordova Platforms : android 8.1.0, ios 5.0.1
   Cordova Plugins   : cordova-plugin-ionic-webview 2.5.2, (and 21 other plugins)

Utility:

   cordova-res : 0.6.0 (update available: 0.8.0)
   native-run  : 0.2.8

System:

   Android SDK Tools : 26.1.1 (/Users/nvelin/Library/Android/sdk)
   ios-deploy        : 1.9.4
   ios-sim           : 8.0.2
   NodeJS            : v10.16.3 (/usr/local/bin/node)
   npm               : 6.12.0
   OS                : macOS Mojave
   Xcode             : Xcode 11.1 Build version 11A1027

Thanks for the issue. Do you happen to know the user agent for the device?

Unfortunately, i don't have it.
I just save the device manufacturer and model in my database

Thanks for the follow up. I've been trying to get access to an emulator of this device, but I haven't been able to find one.
It generally isn't possible for us to account for these edge cases without adding in device specific hacks while also ensuring that detection doesn't break for other devices. Many off-brand Android devices do not conform to a particular standard when identifying themselves on the web, which can be frustrating in situations like these.
I am going to close this issue as there is nothing actionable in terms of fixing this particular issue; however, I have proposed a new feature that would allow developers to override our platform detection methods with their own: https://github.com/ionic-team/ionic/issues/19737. With this feature, you would be able to add logic to the platform detection that would let you account for devices such as the ALPS X23. Thanks!

Sorry for the lack of information
Thanks


Support for NULL values

First, thanks for the great tool!
I was wondering if it would be possible to add some rudimentary support for NULL values?
I want to use xsv to get the column types for a CSV file before loading it into a database. This way I would know the correct column types when creating the database table. While xsv is very fast at calculating file column statistics, my files often have int / float columns with NULL values (e.g. "-", ".'", "\N", "NA"), and xsv reports those as Unicode. It would be nice to have an option like --na-values, so that xsv could skip NULL values when calculating statistics, and could report whether a column contains at least one NULL value.

xsv does actually have support for null values. (Look at xsv stats --help.) The actual problem here is that there are uncountably many ways to represent null. xsv only interprets empty fields as NULL right now. You've listed a few already: -, ., \N, NA. I can imagine several other reasonable values there as well. How should xsv handle such a thing? Notably, values like . or - could otherwise be legitimate outside of any particular context, but probably could be safely assumed to represent NULL if every other type of value in the column were numeric.
A brutish way to solve this is to permit the user to specify a regex that determines what values constitute NULL, but I really dislike that for a number reasons (it'd be slow and I don't consider it user friendly at all).
A different way of thinking about this problem is: instead of teaching different parts of xsv about the different flavors of NULL, we could create a new sub-command that permits one to normalize NULL values in a data set to a canonical form. This indeed might permit specifying a regex or choosing from some predefined list of values. This might even fit into a broader "search and replace" style sub-command.

I really like the idea of a new sub-command that would normalise NULL values!
One problem I often face when importing CSV files into MySQL is that the CSV files have different NULL values, which I have to convert to \N before importing, as \N is the only NULL character that MySQL can recognise. I wrote a Python script to convert CSVs to the appropriate format (using PyPy it's not too slow). But I'm sure something in Rust would run much faster. And this would solve my datatype inference problem as well.

But then it becomes a question of what should be the canonical NULL character. \N would be ideal for loading data into MySQL, . would be best for VCF files, some programs like NA, NULL, etc... I agree that an empty field is the most intuitive representation for NULL, but it would be nice to have the option of using something else...

I'm open to use friendly heuristics.

Perhaps one option is to define the array of missing values for your CSV field in a schema format we're developing that xsv can then read: http://specs.frictionlessdata.io/json-table-schema/#missing-values
Support for reading a CSV schema might also have a carry-over effects for the other inference-related issues #22 and #28

I'm not too keen on going down the schema route. That seems like a lot of added complexity. The point is that there's a certain point at which xsv becomes insufficient for your data analysis, and that's OK.

Merging in a request that's related, which is the ability to replace null values with something else.
Basically, I want to to be able to run xsv impute and have it replace blank values (or values with an out-of-bounds marker you can specify on the command line, such as "NA"). Obvious choices to fill in with would be a fixed value specified on the command line, or the same value as the previous cell in a row or column.
Value: It's hard to do this using sed or such, when a "blank value" could be the strings ,$ ,""$ ,, ,"", and so on.
Not sure how far one wants to go with replacement, since it'd be easy to feature creep "well why don't we add the option to fill in blanks with an average" "well why don't we add interpolation" "well why don't we let you put in an arbitrary equation" and so on. Which is obviously not something xsv should care about.
Notably though, for this use case just being able to specify a "null" to be a fixed string should be sufficient.  If you have multiple different null values you can just have a pipeline of xsv calls that replaces each one with a fixed values.  So if the "null" in your dataset could be an empty string, NA or na and you want to convert all nulls to \N, you could do  xsv impute --null-value "na" --with "\N" | xsv impute --null-value "NA" --with "\N" | xsv impute --null-value "" --with "\N".
That way you don't need a "canonical" null character, you can translate any dataset to use whatever you consider canonical.

@icefoxen Does this capture what you're after?

A different way of thinking about this problem is: instead of teaching different parts of xsv about the different flavors of NULL, we could create a new sub-command that permits one to normalize NULL values in a data set to a canonical form. This indeed might permit specifying a regex or choosing from some predefined list of values. This might even fit into a broader "search and replace" style sub-command.

(What I'm trying to do is understand whether the idea I had previously is enough to satisfy your use case. If it is, great. If not, then that means I need to think a bit more about this!)

@BurntSushi Yeah, that sounds about right.  The only thing missing from that would be the ability to say "replace value X with the cell above/to the left of it", which might be a more specific task than you want xsv to handle.
Sorry for the repetition, obviously time for more coffee.  :-)

@icefoxen Haha no worries, just wanted to be super clear. The idea of replacing a value is interesting. There is something close to that in xsv today with the xsv select command, but it's not conditional on the value.


Filtering change / regression from 10.2.0 to 11?

I am having a problem getting basic filtering to work. I have a QueryType set up so:
 descriptor
	.Field<UserResolvers>(x => x.GetUsers(default, default))
	.Type<ListType<NonNullType<UserType>>>()
	.Name("Users")
	.UseFiltering();

The GetUsers method returns an IQueryable from an EF Core DbContext.
I am using HotChocolate.AspNetCore 11.0.0-preview.64 and HotChocolate.Types.Filters 11.0.0-preview.64
The solution compiles but throws an error when I hit the endpoint:

System.Private.CoreLib: Exception while executing function: graphql. Microsoft.Azure.WebJobs.Host: Exception binding parameter 'executor'. HotChocolate.Types: Unable to resolve type reference Input: HotChocolate.Types.ListType<HotChocolate.Types.NonNullType<HotChocolate.Types.NativeType<System.String>>>. - Type: UserFilter.
at HotChocolate.Configuration.CompletionContext.GetType[T](ITypeReference reference)
at HotChocolate.Types.FieldBase2.OnCompleteField(ICompletionContext context, TDefinition definition)    at HotChocolate.Types.InputField.OnCompleteField(ICompletionContext context, InputFieldDefinition definition)    at HotChocolate.Types.FieldBase2.CompleteField(ICompletionContext context)
at HotChocolate.Types.FieldInitHelper.CompleteFields[TTypeDef,TFieldType,TFieldDef](ICompletionContext context, TTypeDef definition, IReadOnlyCollection1 fields)    at HotChocolate.Types.InputObjectType.OnCompleteType(ICompletionContext context, InputObjectTypeDefinition definition)    at HotChocolate.Types.Filters.FilterInputType1.OnCompleteType(ICompletionContext context, InputObjectTypeDefinition definition)
at HotChocolate.Types.TypeSystemObjectBase1.CompleteType(ICompletionContext context)    at HotChocolate.Configuration.TypeInitializer.<CompleteTypes>b__45_0(RegisteredType registeredType)    at HotChocolate.Configuration.TypeInitializer.CompleteTypes(TypeDependencyKind kind, Func2 action)
at HotChocolate.Configuration.TypeInitializer.CompleteTypes()
at HotChocolate.Configuration.TypeInitializer.Initialize(Func1 schemaResolver, IReadOnlySchemaOptions options)    at HotChocolate.SchemaBuilder.InitializeTypes(IServiceProvider services, IDescriptorContext descriptorContext, IBindingLookup bindingLookup, IEnumerable1 types, Func1 schemaResolver)    at HotChocolate.SchemaBuilder.Create()    at HotChocolate.SchemaBuilder.HotChocolate.ISchemaBuilder.Create()    at SolutionName.Server.Graph._Ioc.IocRegistration.<>c.<UseSolutionGraphql>b__0_0(IServiceProvider serviceProvider) in C:\Code\SolutionName\src\SolutionName.Server\SolutionName.Server.Graph\_Ioc\IocRegistration.cs:line 14    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitFactory(FactoryCallSite factoryCallSite, ServiceProviderEngineScope scope)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitSingleton(SingletonCallSite singletonCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(IServiceCallSite callSite, TArgument argument)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass1_0.<RealizeService>b__0(ServiceProviderEngineScope scope)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngineScope.GetService(Type serviceType)    at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)    at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService[T](IServiceProvider provider)    at HotChocolate.Execution.QueryExecutionBuilder.<>c__DisplayClass9_0.<Populate>b__0(IServiceProvider sp)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitFactory(FactoryCallSite factoryCallSite, ServiceProviderEngineScope scope)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(IServiceCallSite callSite, TArgument argument)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitScoped(ScopedCallSite scopedCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteRuntimeResolver.VisitSingleton(SingletonCallSite singletonCallSite, ServiceProviderEngineScope scope)
at Microsoft.Extensions.DependencyInjection.ServiceLookup.CallSiteVisitor2.VisitCallSite(IServiceCallSite callSite, TArgument argument)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.DynamicServiceProviderEngine.<>c__DisplayClass1_0.<RealizeService>b__0(ServiceProviderEngineScope scope)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType, ServiceProviderEngineScope serviceProviderEngineScope)    at Microsoft.Extensions.DependencyInjection.ServiceLookup.ServiceProviderEngine.GetService(Type serviceType)    at Microsoft.Extensions.DependencyInjection.ServiceProvider.GetService(Type serviceType)    at Microsoft.Extensions.DependencyInjection.ServiceProviderServiceExtensions.GetRequiredService(IServiceProvider provider, Type serviceType)    at SolutionName.Server.Graph.API.Startup.InjectConfiguration.<Initialize>b__1_0(InjectAttribute i) in C:\Code\SolutionName\src\SolutionName.Server\SolutionName.Server.Graph.API\Startup\InjectConfiguration.cs:line 31    at Microsoft.Azure.WebJobs.Host.Bindings.PatternMatcher.<>c__DisplayClass8_02.b__0(Object src, Attribute attr, ValueBindingContext ctx) in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Bindings\PatternMatcher.cs:line 58
at Microsoft.Azure.WebJobs.Host.Bindings.BindToInputBindingProvider`2.ExactBinding.d__5.MoveNext() in C:\projects\azure-webjobs-sdk-rqm4t\src\Microsoft.Azure.WebJobs.Host\Bindings\BindingProviders\BindToInputBindingProvider.cs:line 213

If I downgrade to 10.2.0 the problem goes away.
Has somethng changed in the filtering API in v11?

Quite a lot has changed ... the filters now have a lot more features. But we are still iterating on them.
But I think the issue that you have are from changes coming with 10.3.0 since we are changing how we register types.
We are not done on these yet.
@PascalSenn
It seems from the exception that filters have a problem with the new non-null support for c# 8.
I will create a test for this....

@freever  Hi freever!
Do you mind pasting the generated SDL for the UserFilter from the schema?

Sure I will ping you on Slack if that's ok
On Thu, 12 Dec 2019 at 13:33, PascalSenn<EMAIL_ADDRESS>wrote:

@freever https://github.com/freever Hi freever!
Do you mind pasting the generated SDL for the UserFilter from the schema?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ChilliCream/hotchocolate/issues/1275?email_source=notifications&email_token=AARKDOC26Q6JR3NP2WFOIKDQYIORNA5CNFSM4JZ2APM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEGWMETI#issuecomment-564970061,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARKDOGDONUNVIWRCRL7VSTQYIORNANCNFSM4JZ2APMQ
.

@michaelstaib  @freever could not reproduce the issue for the moment, he will come back to us once it occurs again

If it helps at all, I happened upon this issue as well.  It seems to have a problem with any not null string properties.  However, if I switch the properties to be nullable strings, the issue goes away.  In my case, the properties should have been null anyway, as they represent values assigned to database columns allowing nulls.

That is what I have suspected....
@PascalSenn
I rewrite the types now and this could lead to issues for you while the type is constructed. We should build a little test for this so we have non-nullability under test.

Can we close this issue? @freever @PascalSenn

Sure thing


parse error of ! on asir built by --enable-fep

asir (editline version) cannot parse inputs with '!'.
$ asir
This is Risa/Asir, full GMP Version 20220911 (Kobe Distribution).
Copyright (C) 1994-2000, all rights reserved, FUJITSU LABORATORIES LIMITED.
Copyright 2000-2021, Risa/Asir committers, http://www.openxm.org/.
GC 7.6.12 copyright 1988-2018, H-J. Boehm, A. J. Demers, Xerox, SGI, HP, I. Maidanski.
[0] 0!;
0
[1] 1!;
1
[2] 2!;
2
[3] 3!;
3
[4] 10!;
10
[5] 10!/2;
/2;: Event not found
[5]

Add space after !,  e.g.,  3! ;  (comment by Ohara).
2022-09-12 13:36 に Mitsushi Fujimoto さんは書きました:

asir (editline version) cannot parse inputs with '!'.
$ asir
This is Risa/Asir, full GMP Version 20220911 (Kobe Distribution).
Copyright (C) 1994-2000, all rights reserved, FUJITSU LABORATORIES
LIMITED.
Copyright 2000-2021, Risa/Asir committers, http://www.openxm.org/.
GC 7.6.12 copyright 1988-2018, H-J. Boehm, A. J. Demers, Xerox, SGI,
HP, I. Maidanski.
[0] 0!;
0
[1] 1!;
1
[2] 2!;
2
[3] 3!;
3
[4] 10!;
10
[5] 10!/2;
/2;: Event not found
[5]
--
Reply to this email directly, view it on GitHub [1], or unsubscribe
[2].
You are receiving this because you are subscribed to this
thread.Message ID: @.***>
Links:
[1] https://github.com/openxm-org/OpenXM/issues/1
[2]
https://github.com/notifications/unsubscribe-auth/ABSA7NU73KWFQ35AW5H2ZFDV52XNFANCNFSM6AAAAAAQKDARD4

This issue was fixed by Ohara.
asir2018/parse/glob.c


Swap greys in legend for calibration graph

Just need to swap the colors on perfect calibration and perfect calibration CI. I think it's pretty self-explanatory as-is, but might as well.

Reported by oldwindways

nice catch, sure I'll flip it

completed, closing


Bluetooth: ISO/BAP: Refactor BIS bitfield

Refactors teh BIS bitfield values used for ISO
and BAP.
Previously BIT(1) meant BIS index 1, which was a Zephyr choice in the early days of ISO, as the BT Core spec did not use a bitfield for BIS indexes.
Later the BASS specification came along and defined that BIT(0) meant BIS index 1, which meant that we had to shift BIS bitfields between BAP and ISO.
This commit refactors the ISO layer to use BIT(0) for Index 1 now, which means that there is no longer a need for conversion between the BAP and ISO layers, and that we can use a value range defined by a BT Core spec (BASS).
fixes https://github.com/zephyrproject-rtos/zephyr/issues/64838

Rebased to solve merge conflicts


fix missing dependencies

add missing stdlib dependency to metadata.json

Thank you for the PR.  I think to make the tests happy again, we'll need a file that looks like this too: https://github.com/xaque208/puppet-bsd/blob/master/.fixtures.yml
Though with the right module deps that you've included here.  Can you include that with this PR?

https://github.com/xaque208/puppet-openvpn/pull/69

@xaque208 something else here?

Oh no, I just forgot to come back.  Thank you.


Option to disable animations

Terrific plug-in!
Is there a way to disable animations?
Because it's conflicting with my own stuff...
Thanks!

I think you can disable the css transitions like this:
.vue-grid-item {
  /* transition: all 200ms ease; */
  transition: none;
}

.vue-grid-layout {
  /* transition: height 200ms ease; */
  transition: none;
}


Instituto Universitario del Sureste

Agrego mi colegio Instituto Universitario del Sureste https://iunis.edu.mx/

@jcvisk First stage of verification passed, official domain is iunis.edu.mx as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@jcvisk Please provide us with an URL of a page on the official website where the school offers an IT-related long-term (>1 year) course. Thank you!

@jcvisk Thank you for your patience while waiting for a review and processing your request. Pull request merged.


"strange question": size of W ?

Already Know：W --- whxwh,  input size --- 769x769,  ---> wh=(769/8)x(769/8)=9216
Parameter of W: 9216x9216=84934656
Parameter of ResNet101：44549160
The parameter of W is larger than bone net (ResNet101)，stange and crazy?
Is it my misunderstand ?
thank you ~

@AceCoooool That is not the parameter. We only need 1x1 convolution. Besides, we can down-sample the output feature map within the Base-OC block. Please wait for the open source implementation.

thank you :smile: ~ there is "unrelated" between each row of W, may many methods can deal with it (I guess). Looking forward to the implementation, thank you :heart:


fix:  IndyCar - fix date display

Description
fix date display - remove leading 0
Copilot

🤖 Generated by Copilot at d5fe38f
Summary
📅📝🐛

Fix date format and update version for indycar app. The app now displays the race dates in the same format as the official Indycar website, and the code has a comment and a new version number to reflect the changes.

The source of truth has spoken, we must obey
indycar app must conform to the date format
We document the changes, we update the version
We are the code warriors, we fix the bugs with passion

Walkthrough

Update version number to 23247 (link)
Fix date format to remove leading zero from day of month (link)
Add comment with date, author, and purpose of changes (link)

:shipit:

merged with other indycar change (I forgot it was still open)


[Tool] Upgrade ftm from 7.0.3 to 8.1.1 (#26057)

(Cherry-picked from https://github.com/StarRocks/starrocks/pull/26057)
What type of PR is this:

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[x] Tool

Does this PR entail a change in behavior?

[ ] Yes, this PR will result in a change in behavior.
[x] No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

[ ] Interface/UI changes: syntax, type conversion, expression evaluation, display information
[ ] Parameter changes: default values, similar parameters but with different default values
[ ] Policy changes: use new policy to replace old one, functionality automatically enabled
[ ] Feature removed
[ ] Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[x] I have checked the version labels which the pr will be auto-backported to the target branch

[ ] 3.2
[ ] 3.1
[ ] 3.0
[ ] 2.5

[FE Incremental Coverage Report]
:heart_eyes: pass : 0 / 0 (0%)

[BE Incremental Coverage Report]
:disappointed: fail : 3 / 25 (12.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
src/storage/task/engine_clone_task.cpp
0
4
00.00%
[165, 168, 169, 170]

:large_blue_circle:
src/io/s3_input_stream.cpp
0
3
00.00%
[31, 32, 33]

:large_blue_circle:
src/runtime/mysql_table_writer.cpp
0
9
00.00%
[136, 150, 155, 159, 165, 167, 178, 180, 182]

:large_blue_circle:
src/util/json_converter.cpp
0
1
00.00%
[147]

:large_blue_circle:
src/fs/hdfs/fs_hdfs.cpp
0
5
00.00%
[322, 352, 471, 506, 561]

:large_blue_circle:
src/fs/fs_broker.cpp
3
3
100.00%
[]


Filter upload

Fixes https://github.com/node-formidable/formidable/issues/648, https://github.com/node-formidable/formidable/issues/456, https://github.com/node-formidable/formidable/issues/617, https://github.com/node-formidable/formidable/issues/471

@tunnckoCore small PR but should be very useful (and popular demand)

looks ok 👌

Should this work on v2 as well or is just merged in v3? Because it's not cleaning up in v2 in my case...


Add support for Tekton result logs

Fixes
Fixes https://issues.redhat.com/browse/HAC-4318
Description
Adds support for retrieving log results from Texton when pods are no longer available.
Type of change

[x] Feature

Screen shots / Gifs for design review

/cc @rohitkrai03 @christianvogt

works as expected.
Downloading all logs takes a while. I wonder if we ought to have a tooltip popup and show additional information. However this, if at all, should be part of a separate PR.

@christianvogt @rohitkrai03 I'm not able to increase the code coverage. The non-covered code is refactored to be asynchronous vs synchronous and it's dependent on reading logs and waiting for them to be returned.

/approve

/retest

/retest

/retest


HIP-RA-X

Project tracker item

TODO:

[ ] ❗Fix missing/incorrect h20 density/temp/enthalpy values/interpolations
[ ] Continue consolidating HIP_RA_Unit_tests.py into test_HIP_RA.py and test_geophires_utils.py as appropriate
[ ] Verify SUTRA updates/conversions are correct
[ ] Second pair of eyes to spot check small-delta results updates
[ ] Address any other newly added FIXMEs

Broken GEOPHIRES examples:

[ ] example5
[ ] example10_HP
[ ] example11_AC
[ ] example12_DH

kfbeckers comments:

Tooltip for rock density and fluid density says “Heat density” but I think that is not a correct term. I think it should be either “density” by itself or “mass density”.
Units for rock and fluid density are kg/km^3. Maybe use kg/m^3 instead as those are I think more common? (SI units and also used elsewhere in the code)
The user seems to specify two rejection temperatures (one in deg C and one in K). But they are coupled as the one in Kelvin should be 273.15 above the one in deg C. I suggest the user only provide one rejection temperature and the other one can be calculated internally.
The user currently needs to provide both the rejected enthalpy and rejection entropy. These are not values the user directly knows. Better instead may be to have the user specify the rejection pressure (e.g. 1 bar). Internally then, HIP-RA can calculate the rejection enthalpy and entropy based on rejection pressure combined with rejection temperature.
Currently temperature for correlations is capped at 373 deg C. Maybe allow going to higher temperature so we can allow supercritical? See also next comment
Currently the correlations are only temperature dependent. But pressure could be another important parameter. E.g, water at 150 deg C in liquid phase has very different fluid properties (such as enthalpy) than water at 150 C and in steam phase. Maybe we can allow the user to specify both reservoir temperature and pressure. These two combined allow to evaluate fluid properties for a wide range of temperature and pressure values (e.g. going to 600 C to look at some of the magma systems in Iceland currently being studied for geothermal). Instead of hard-coded correlations, we could use the CoolProp package to give us enthalpy, entropy, density as a function of T and P.

My responses (prefixed with MIR) to Koenrads comments on HIP=RAX-
•	Tooltip for rock density and fluid density says “Heat density” but I think that is not a correct term. I think it should be either “density” by itself or “mass density”.
MIR> Good catch. I will fix
•	Units for rock and fluid density are kg/km^3. Maybe use kg/m^3 instead as those are I think more common? (SI units and also used elsewhere in the code)
MIR> Changing the units on an input will break users input files. I’d rather not change that. But since we use the pint library, the user can specify their own units for amything, so if they say “Density Of Reservoir Rock, 2.55 gm/cc”, it will see the “gm/cc” and it will automatically convert it to whatever units HIP-RA requires – in this case, kg/km3.
•	The user seems to specify two rejection temperatures (one in deg C and one in K). But they are coupled as the one in Kelvin should be 273.15 above the one in deg C. I suggest the user only provide one rejection temperature and the other one can be calculated internally.
MIR> I don’t see that – I only see:

•	The user currently needs to provide both the rejected enthalpy and rejection entropy. These are not values the user directly knows. Better instead may be to have the user specify the rejection pressure (e.g. 1 bar). Internally then, HIP-RA can calculate the rejection enthalpy and entropy based on rejection pressure combined with rejection temperature.
MIR> I don’t see that – the only thing the user provides is the Rejection temperature….
•	Currently temperature for correlations is capped at 373 deg C. Maybe allow going to higher temperature so we can allow supercritical? See also next comment
MIR> Yes, indeed, that is my thinking also, but I didn’t want to do any SHR work yet, until the deal with Aaron is firmed up
•	Currently the correlations are only temperature dependent. But pressure could be another important parameter. E.g, water at 150 deg C in liquid phase has very different fluid properties (such as enthalpy) than water at 150 C and in steam phase. Maybe we can allow the user to specify both reservoir temperature and pressure. These two combined allow to evaluate fluid properties for a wide range of temperature and pressure values (e.g. going to 600 C to look at some of the magma systems in Iceland currently being studied for geothermal). Instead of hard-coded correlations, we could use the CoolProp package to give us enthalpy, entropy, density as a function of T and P.
MIR> Yep, I agree – all of this fits under the SHR development heading in my mind. The user can provide a pressure, or we can calculate one, assuming we know the depth of the reservoir, and we assume lithostatic conditions. Further, another variable to account for is salinity of the formation waters – right now, everything is calculated assuming pure water, which is never the case. We can allow the user to specify a salinity, or we can assume a default from published subsurface salinities. This also raises the question about what other things might be dissolved in the water, and how things things might influence boiling point, enthalpy, density, etc…

Tooltip for rock density and fluid density says “Heat density” but I think that is not a correct term. I think it should be either “density” by itself or “mass density”.
MIR> Good catch. I will fix

@malcolm-dsider I just fixed now (changed "Heat density" to "Density" for rock_density) in https://github.com/softwareengineerprogrammer/GEOPHIRES-X/pull/3/commits/220bbff428c0ca0546dcfb89cb1a8f3c03da1252, no action needed on your part

SUTRA is  @.***> @Beckers, Koenraad baby, but yes, I think SUTRA qualifies as RTES
From: Jonathan Pezzino @.>
Sent: Sunday, January 21, 2024 11:19 AM
To: softwareengineerprogrammer/GEOPHIRES-X @.>
Cc: Malcolm Ross @.>; Mention @.>
Subject: Re: [softwareengineerprogrammer/GEOPHIRES-X] HIP-RA-X (PR #3)
@softwareengineerprogrammer commented on this pull request.

In tests/examples/SUTRAExample1.txt https://github.com/softwareengineerprogrammer/GEOPHIRES-X/pull/3#discussion_r1461002505 :

@@ -27,8 +27,9 @@ Reservoir Impedance,0.2,                                ---[GPa*s/m3]

SURFACE TECHNICAL PARAMETERS

-End-Use Option,9,                                           ---[-] Reservoir Thermal Energy Storage
+End-Use Option,2,                                                   ---[-] Direct-Use Heat
@malcolm-dsider https://github.com/malcolm-dsider  and/or @kfbeckers https://github.com/kfbeckers  is this the correct end-use option for SUTRA now that RTES is a surface plant property rather than end-use option?
—
Reply to this email directly, view it on GitHub https://github.com/softwareengineerprogrammer/GEOPHIRES-X/pull/3#pullrequestreview-1835382373 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGVYT3Z5VWLSRS4HRT3O7LYPVEWVAVCNFSM6AAAAABCAZU5TKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQMZVGM4DEMZXGM .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AWGVYT75C3HGYNPNMVOPHX3YPVEWVA5CNFSM6AAAAABCAZU5TKWGG33NNVSW45C7OR4XAZNRKB2WY3CSMVYXKZLTORJGK5TJMV32UY3PNVWWK3TUL5UWJTTNMW3GK.gif Message ID: @.*** @.***> >

The end-use option for district heating (PlantType, 7) is Direct-use heat.
So yes, I think
End-Use Option,2, --- Direct use
Power Plant Type, 7,             ---[-] District Heating
Is correct for Example 12
-Malcolm
From: Jonathan Pezzino @.>
Sent: Sunday, January 21, 2024 2:34 PM
To: softwareengineerprogrammer/GEOPHIRES-X @.>
Cc: Malcolm Ross @.>; Mention @.>
Subject: Re: [softwareengineerprogrammer/GEOPHIRES-X] HIP-RA-X (PR #3)
@softwareengineerprogrammer commented on this pull request.

In tests/examples/example12_DH.out https://github.com/softwareengineerprogrammer/GEOPHIRES-X/pull/3#discussion_r1461108832 :

                        ***SUMMARY OF RESULTS***

 End-Use Option: District Heating

 End-Use Option: Direct-Use Heat

@malcolm-dsider https://github.com/malcolm-dsider  or @kfbeckers https://github.com/kfbeckers  - is it desirable to now render end-use as the 'technically correct' value of Direct-Use heat, without explicit mention of District Heating here or elsewhere?
—
Reply to this email directly, view it on GitHub https://github.com/softwareengineerprogrammer/GEOPHIRES-X/pull/3#pullrequestreview-1835428855 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGVYT5UTLPDAKNDZ5SEFNDYPV3UVAVCNFSM6AAAAABCAZU5TKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQMZVGQZDQOBVGU .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AWGVYTZTWA4P4C2LSJDL2H3YPV3UVA5CNFSM6AAAAABCAZU5TKWGG33NNVSW45C7OR4XAZNRKB2WY3CSMVYXKZLTORJGK5TJMV32UY3PNVWWK3TUL5UWJTTNMZV7O.gif Message ID: @.*** @.***> >

You are looking at the wrong line – the line you have is simply the sum of the stored heat in the rock plus the stored heat in the fluid. The line you need to look at is three lines above your line (and this line looks identical to the GEOPHIRES line):
self.stored_heat_rock.value = self.volume_rock.value * self.rock_heat_capacity.value * delta_temperature_k
The next line simply corrects for the recoverable heat in the rock, which is somewhat less:
self.stored_heat_rock.value = self.stored_heat_rock.value * self.recoverable_rock_heat.value
The next line makes the same calculation for the fluid:
self.stored_heat_fluid.value = self.mass_fluid.value * self.fluid_heat_capacity.value * delta_temperature_k
This value doesn’t need to be corrected for recoverable fluid, as that has been corrected for much earlier.
Then the line you have sums the two values to get the whole reservoir stored heat.
self.reservoir_stored_heat.value = self.stored_heat_rock.value + self.stored_heat_fluid.value
-Malcolm
From: Jonathan Pezzino @.>
Sent: Monday, January 22, 2024 2:31 PM
To: softwareengineerprogrammer/GEOPHIRES-X @.>
Cc: Malcolm Ross @.>; Mention @.>
Subject: Re: [softwareengineerprogrammer/GEOPHIRES-X] HIP-RA-X (PR #3)
@softwareengineerprogrammer commented on this pull request.

In tests/HIP_RA_Unit_tests.py https://github.com/softwareengineerprogrammer/GEOPHIRES-X/pull/3#discussion_r1462382086 :

   assert hip_ra.reservoir_stored_heat.value == hip_ra.reservoir_volume.value * (

       hip_ra.rock_heat_capacity.value * (hip_ra.reservoir_temperature.value - hip_ra.rejection_temperature.value)

   )

@malcolm-dsider https://github.com/malcolm-dsider  the asserted calculation here is at odds with what's implemented in HIP-RA https://github.com/softwareengineerprogrammer/GEOPHIRES-X/blob/f44855984b4a2a52b4afc7bab6acfd87d8a7b552/src/hip_ra/HIP_RA.py#L644: , which is:
self.reservoir_stored_heat.value = self.stored_heat_rock.value + self.stored_heat_fluid.value
Which calculation (if either) is correct?
—
Reply to this email directly, view it on GitHub https://github.com/softwareengineerprogrammer/GEOPHIRES-X/pull/3#pullrequestreview-1837307243 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AWGVYT36CEJEBU7MSLDML6TYP3D7VAVCNFSM6AAAAABCAZU5TKVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQMZXGMYDOMRUGM .
You are receiving this because you were mentioned.  https://github.com/notifications/beacon/AWGVYT2SM54ICTDOKWMQ7XTYP3D7VA5CNFSM6AAAAABCAZU5TKWGG33NNVSW45C7OR4XAZNRKB2WY3CSMVYXKZLTORJGK5TJMV32UY3PNVWWK3TUL5UWJTTNQMKWW.gif Message ID: @.*** @.***> >

Note: this is relevant to https://github.com/NREL/GEOPHIRES-X/issues/83 (but doesn't fully fix/address yet)


[Admin] Create/Edit MT Modal

On both the Create and Edit MT Modal, change the following:

Use React Hook Form, making all fields required.
Use input validation on email and phone number
On the edit MT modal, email should not be an editable field.
There is a bug where the "create" button just refreshes the page automatically instead of going to the Confirmation tab and then sending the request. Please try to fix this (lower priority)

/cib mt-create-edit-modal-updates

Branch 151-mt-create-edit-modal-updates created!


free form objects not handled correctly

Description
Connexion filter out all values of free form object.
swagger/swagger.yaml
openapi: "3.0.1"
info:
  title: "Simple example"
  version: "1"
servers:
- url: "http://localhost:8080/v1"
paths:
  /json_body:
    post:
      summary: "Simple POST with free form body"
      operationId: "controller.json_body"
      requestBody:
        content:
          application/json:
            schema:
              type: "object"
      responses:
        201:
          description: "OK"

controller.py
from aiohttp import web

async def json_body(body):  # noqa: E501
    print(body)
    return web.Response(status=201)

main.py
import connexion

def main():
    app = connexion.AioHttpApp(__name__, specification_dir='./swagger/')
    app.add_api('swagger.yaml', arguments={'title': 'Echo service'}, pass_context_arg_name='request')
    app.run(port=8080)

if __name__ == '__main__':
    main()

Expected behaviour
When I call curl http://localhost:8080/v1/json_body -d '{"foo": "bar"}' -H "Content-Type: application/json"
{"foo": "bar"} is displayed in logs.
Actual behaviour
{} is displayed in logs.
Additional info:
python 3.6.6
connexion 2.0.1
aiohttp 3.4.4

Thanks for the ticket @Jyhess - I'll try to take a look at the end of the week.

potential fix: #789

potential fix: #789

I confirm this PR fix this issue.

Closing this ticket, as the fix has been merged and will be part of the next release.
Thanks @Jyhess for filing the issue, and @krise3k for the fix!


Deploy Zipkin with Istio, you can find zipkin.yaml in directory [deployment/istio-deployment]

Kubernetes version(use kubectl version):V1.18.0

The [deployment/istio-deployment] does not exist
Can you upload it


Path of Building has stopped working

im running Win 10 and PoB worked fine, today i installed the Win 10 Creators update and since then every time i tried to open PoB it just crashes and i get the message "Path of Building has stopped working"

I am also using Windows 10 x64.. I didn't install any creators update. I just tried opening Path of Building this morning and it doesn't work.
I tried uninstalling, cleaning all files, trying standalone vs installed version, and I cannot get it to work.

so the Creators update seems to not be the problem. thats wierd. why should it stop working all of the sudden?

Just tried it on my laptop and it is working fine there. I think this might be Windows update related?
Sent from my phone
-------- Original message --------From: PhilMonster<EMAIL_ADDRESS>Date: 4/30/17  1:19 PM  (GMT-08:00) To: Openarl/PathOfBuilding<EMAIL_ADDRESS>Cc: JD Pierce<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [Openarl/PathOfBuilding] Path of Building has stopped working (#328)
so the Creators update seems to not be the problem. thats wierd. why should it stop working all of the sudden?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/Openarl/PathOfBuilding","title":"Openarl/PathOfBuilding","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/Openarl/PathOfBuilding"}},"updates":{"snippets":[{"icon":"PERSON","message":"@PhilMonster in #328: so the Creators update seems to not be the problem. thats wierd. why should it stop working all of the sudden?"}],"action":{"name":"View Issue","url":"https://github.com/Openarl/PathOfBuilding/issues/328#issuecomment-298254453"}}}

it works fine on my Laptop to but it also has Win 10 x64, but not Nvidia Geforce Expirience, since it dosent habe a Graphics card.

The latest Update for Nvidia GeForce Expirience fixes this issue, and i can finaly use PoB again :D

Ah, excellent. Quite a few people were experiencing this, so it's good to know Nvidia have finally managed to correct the issue.


Pods stuck in running state

Summary
Pods are stuck in a perpetually running state when using the latest tag for a cluster wide installation. Note that I'm not getting this error when running make start UI=true on the master branch. Just reporting this so that any lighting demos tomorrow aren't affected.
UI view:

Diagnostics
K8s version: Docker Desktop
Argo Installation: https://raw.githubusercontent.com/argoproj/argo-workflows/master/manifests/install.yaml
Workflow: Any sample workflow generated by the UI is resulting in the hanging pods

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

Do you have any diagnostics?

Same issue, I've run the template example using versions: 3.2.4, 3.1.13, 3.2.2 and in all of them the pod gets stuck in running status after display "Hello argo" message and never kills the pod.

@JPZ13 you mentioned that this was a problem with cluster install? Do you know if it is a problem with namespace install too?
If not, perhaps the clusters roles do not have the correct permissions:
https://github.com/argoproj/argo-workflows/tree/master/manifests/cluster-install/workflow-controller-rbac vs
https://github.com/argoproj/argo-workflows/tree/master/manifests/namespace-install/workflow-controller-rbac
We also need to know:

Are there any errors in the wait container logs?

Thanks @alexec - will troubleshoot based on your above comment this evening and post findings

The pods are hanging for me using this namespace installation: https://github.com/argoproj/argo-workflows/blob/master/manifests/namespace-install.yaml
Here is an output of my wait logs for a UI-generated workflow:
W
time="2021-11-23T15:07:06.381Z" level=info msg="Starting Workflow Executor" executorType= version=untagged
time="2021-11-23T15:07:06.385Z" level=info msg="Creating a  executor"
time="2021-11-23T15:07:06.385Z" level=info msg="Executor initialized" deadline="0001-01-01 00:00:00 +0000 UTC" includeScriptOutput=f
alse namespace=default podName=sparkly-python template="{\"name\":\"argosay\",\"inputs\":{\"parameters\":[{\"name\":\"message\",\"va
lue\":\"hello argo\"}]},\"outputs\":{},\"metadata\":{},\"container\":{\"name\":\"main\",\"image\":\"argoproj/argosay:v2\",\"command\
":[\"/argosay\"],\"args\":[\"echo\",\"hello argo\"],\"resources\":{}}}" version="&Version{Version:untagged,BuildDate:2021-11-23T05:0
1:45Z,GitCommit:160bdc61e9eaa6e488c9871093504587cb585ab5,GitTag:untagged,GitTreeState:clean,GoVersion:go1.17.3,Compiler:gc,Platform:
linux/arm64,}"
time="2021-11-23T15:07:06.387Z" level=info msg="Starting deadline monitor"

Unfortunately no error message that sticks out. Here's an output of kubectl get logs:
NAME                                  READY   STATUS     RESTARTS   AGE
argo-server-d5fd6d4b8-dnx8q           1/1     Running    0          11m
sparkly-python                        1/2     NotReady   0          7m49s
workflow-controller-558db44f7-92scf   1/1     Running    0          11m

And a detail of the sparkly-python pod:
apiVersion: v1
kind: Pod
metadata:
  annotations:
    kubectl.kubernetes.io/default-container: main
    workflows.argoproj.io/node-id: sparkly-python
    workflows.argoproj.io/node-name: sparkly-python
  creationTimestamp: "2021-11-23T15:05:49Z"
  labels:
    workflows.argoproj.io/completed: "false"
    workflows.argoproj.io/workflow: sparkly-python
  name: sparkly-python
  namespace: default
  ownerReferences:
  - apiVersion: argoproj.io/v1alpha1
    blockOwnerDeletion: true
    controller: true
    kind: Workflow
    name: sparkly-python
    uid: 40a1ed52-cc65-4aff-ba64-eb0f2ae38784
  resourceVersion: "1104"
  uid: 872e41a2-a168-4be9-998c-9b30deb69d6c
spec:
  containers:
  - command:
    - argoexec
    - wait
    - --loglevel
    - info
    env:
    - name: ARGO_POD_NAME
      valueFrom:
        fieldRef:
          apiVersion: v1
          fieldPath: metadata.name
    - name: ARGO_CONTAINER_RUNTIME_EXECUTOR
    - name: GODEBUG
      value: x509ignoreCN=0
    - name: ARGO_WORKFLOW_NAME
      value: sparkly-python
    - name: ARGO_CONTAINER_NAME
      value: wait
    - name: ARGO_TEMPLATE
      value: '{"name":"argosay","inputs":{"parameters":[{"name":"message","value":"hello
        argo"}]},"outputs":{},"metadata":{},"container":{"name":"main","image":"argoproj/argosay:v2","command":["/argosay"],"args":["echo","hello
        argo"],"resources":{}}}'
    - name: ARGO_INCLUDE_SCRIPT_OUTPUT
      value: "false"
    - name: ARGO_DEADLINE
      value: "0001-01-01T00:00:00Z"
    - name: ARGO_PROGRESS_FILE
      value: /var/run/argo/progress
    - name: ARGO_PROGRESS_PATCH_TICK_DURATION
      value: 1m0s
    - name: ARGO_PROGRESS_FILE_TICK_DURATION
      value: 3s
    image: quay.io/argoproj/argoexec:latest
    imagePullPolicy: Always
    name: wait
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/argo
      name: var-run-argo
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-rkgbp
      readOnly: true
  - args:
    - echo
    - hello argo
    command:
    - /argosay
    env:
    - name: ARGO_CONTAINER_NAME
      value: main
    - name: ARGO_TEMPLATE
      value: '{"name":"argosay","inputs":{"parameters":[{"name":"message","value":"hello
        argo"}]},"outputs":{},"metadata":{},"container":{"name":"main","image":"argoproj/argosay:v2","command":["/argosay"],"args":["echo","hello
        argo"],"resources":{}}}'
    - name: ARGO_INCLUDE_SCRIPT_OUTPUT
      value: "false"
    - name: ARGO_DEADLINE
      value: "0001-01-01T00:00:00Z"
    - name: ARGO_PROGRESS_FILE
      value: /var/run/argo/progress
    - name: ARGO_PROGRESS_PATCH_TICK_DURATION
      value: 1m0s
    - name: ARGO_PROGRESS_FILE_TICK_DURATION
      value: 3s
    image: argoproj/argosay:v2
    imagePullPolicy: IfNotPresent
    name: main
    resources: {}
    terminationMessagePath: /dev/termination-log
    terminationMessagePolicy: File
    volumeMounts:
    - mountPath: /var/run/argo
      name: var-run-argo
    - mountPath: /var/run/secrets/kubernetes.io/serviceaccount
      name: kube-api-access-rkgbp
      readOnly: true
  dnsPolicy: ClusterFirst
  enableServiceLinks: true
  nodeName: docker-desktop
  preemptionPolicy: PreemptLowerPriority
  priority: 0
  restartPolicy: Never
  schedulerName: default-scheduler
  securityContext: {}
  serviceAccount: default
  serviceAccountName: default
  terminationGracePeriodSeconds: 30
  tolerations:
  - effect: NoExecute
    key: node.kubernetes.io/not-ready
    operator: Exists
    tolerationSeconds: 300
  - effect: NoExecute
    key: node.kubernetes.io/unreachable
    operator: Exists
    tolerationSeconds: 300
  volumes:
  - emptyDir: {}
    name: var-run-argo
  - name: kube-api-access-rkgbp
    projected:
      defaultMode: 420
      sources:
      - serviceAccountToken:
          expirationSeconds: 3607
          path: token
      - configMap:
          items:
          - key: ca.crt
            path: ca.crt
          name: kube-root-ca.crt
      - downwardAPI:
          items:
          - fieldRef:
              apiVersion: v1
              fieldPath: metadata.namespace
            path: namespace
status:
  conditions:
  - lastProbeTime: null
    lastTransitionTime: "2021-11-23T15:05:50Z"
    status: "True"
    type: Initialized
  - lastProbeTime: null
    lastTransitionTime: "2021-11-23T15:05:50Z"
    message: 'containers with unready status: [main]'
    reason: ContainersNotReady
    status: "False"
    type: Ready
  - lastProbeTime: null
    lastTransitionTime: "2021-11-23T15:05:50Z"
    message: 'containers with unready status: [main]'
    reason: ContainersNotReady
    status: "False"
    type: ContainersReady
  - lastProbeTime: null
    lastTransitionTime: "2021-11-23T15:05:50Z"
    status: "True"
    type: PodScheduled
  containerStatuses:
  - containerID: docker://2e4cab864f948ee1ec51fc6fec8cbf665317ddb5f06a58f199ec90da71e18cc6
    image: argoproj/argosay:v2
    imageID: docker-pullable://argoproj/argosay@sha256:f0b51e5d3a394af492de5ae50af93f11ba0862480d0eb2cbb48286fe58745303
    lastState: {}
    name: main
    ready: false
    restartCount: 0
    started: false
    state:
      terminated:
        containerID: docker://2e4cab864f948ee1ec51fc6fec8cbf665317ddb5f06a58f199ec90da71e18cc6
        exitCode: 0
        finishedAt: "2021-11-23T15:07:06Z"
        reason: Completed
        startedAt: "2021-11-23T15:07:06Z"
  - containerID: docker://d93c889721f87ddce283f41d90c448af71fd032404a27f5a051cf0342a565653
    image: quay.io/argoproj/argoexec:latest
    imageID: docker-pullable://quay.io/argoproj/argoexec@sha256:fa7a1b04a8b6ee68f44947f6d8bbb7137423d76da56113fface7850029269e69
    lastState: {}
    name: wait
    ready: true
    restartCount: 0
    started: true
    state:
      running:
        startedAt: "2021-11-23T15:07:06Z"
  hostIP: <IP_ADDRESS>
  phase: Running
  podIP: <IP_ADDRESS>
  podIPs:
  - ip: <IP_ADDRESS>
  qosClass: BestEffort
  startTime: "2021-11-23T15:05:50Z"

@diazGT94 - which flavor of k8s are you using? I wonder if this might be specific to docker desktop vs other distros

@alexec  I'm using kubernetes version 1.21 with the aws eks service.

I'm having a similir issue on random nodes on our workflows, using argo-workflows 3.1.3 and kubernetes 1.21.5-gke

Please can you make sure you're running the latest version (v3.2). If the problem persists, please raise a new issue with a workflow we can run to reproduce the issues and any logs.

I'm having this issue as well, did a cluster install from the master branch (v3.2.4) in the local OpenShift v4.9.5 (CodeReady Containers). For some reason wait container just keeps on running even so main workflow container is done.

I had a similar issue on GKE. My workaround was to set containerRuntimeExecutor: emissary in controller configmap

Thanks @jnahelou, that does seem to help:
{ oc | kubectl } patch configmap workflow-controller-configmap --patch '{"data":{"containerRuntimeExecutor":"emissary"}}'

I've noticed that quick-start-*.yaml manifests contain that configuration but not the standard install.yaml.

+1 to @jnahelou there is a bug, where if the executor is not specified, it does not work. To workaround, change configuration as suggested.

I think the bug is here:
https://github.com/argoproj/argo-workflows/blob/6423b6995f06188c11eddb3ad23ae6631c2bf025/workflow/controller/controller.go#L1100
This should probably return "emissary" rather than empty string,
Probably caused by #6785 (#6882).
@tczhao would you like to own this?

No reply, so I will fix.


[Next loader] Warning: exceeded max tag count for fetch

Describe the bug
Hey there! I’m currently working on a project that retrieves dozens of documents in one query. I noticed some warnings popping up when running the query. Here’s what they say:
Warning: exceeded max tag count for fetch https://***.apicdn.sanity.io/v2024-04-12/data/query/production?query=***&cacheMode=noStale&perspective=published&tag=next-loader.fetch&lastLiveEventId=***, dropped tags: sanity:s1:B/8zWA, sanity:s1:UXvMtQ, sanity:s1:GIWh6w, sanity:s1:MxZjmA, sanity:s1:yg26wQ, sanity:s1:CfDYtw, sanity:s1:Gey+0A, sanity:s1:SfVT0w, sanity:s1:rz7uCg, sanity:s1:2pKhOQ, sanity:s1:wHfThw, sanity:s1:+crJwg, sanity:s1:8rxAwA, sanity:s1:mVUWBg, sanity:s1:QO3maw, sanity:s1:LW3Vgw, sanity:s1:WCLWqw, sanity:s1:j1cU1g, sanity:s1:UZClWQ, sanity:s1:HPO5TQ, sanity:s1:75aatQ, sanity:s1:UyvdtA, sanity:s1:tUE/kg, sanity:s1:JRuWPw, sanity:s1:Djhj/A, sanity:s1:spoinQ

I’ve replaced some characters with *** just to be cautious about any sensitive information and the query was a bit long.
There’s also a performance issue in draft mode whenever this query runs. It can take over ten seconds to load the page in draft mode, and sometimes it even causes an edge function crash error on Netlify where the project hosted.
However, after splitting the query into multiple ones, the warnings disappeared and the performance improved.
I suspect that the issue might be related to the revalidation tags used by next loader during a query, which seem to exceed the maximum allowed tags by Next.js when there are a lot of documents involved.
Which versions of Sanity are you using?
@sanity/cli (global)             3.63.0 (latest: 3.67.1)
@sanity/image-url                 1.0.2 (latest: 1.1.0)
@sanity/language-filter           4.0.2 (up to date)
@sanity/orderable-document-list   1.2.2 (up to date)
@sanity/preview-url-secret        1.6.7 (latest: 2.0.5)
@sanity/types                    3.62.2 (latest: 3.67.1)
@sanity/ui                       2.8.10 (latest: 2.10.9)
@sanity/vision                   3.37.2 (latest: 3.67.1)
@sanity/webhook                   4.0.3 (latest: 4.0.4)
sanity                           3.63.0 (latest: 3.67.1)
next-sanity 9.8.21
next 14.2.8
What operating system are you using?
mac os 14.5
Which versions of Node.js / npm are you running?
v20.18.0

We reached out to Vercel about this, and they increased the limit in next 15.1 to 128. Can you upgrade to that and give it a go?


Update README to reflect new setup

Refs #233

@nvkelso Could you review please?

I'm generally fine with this change, but shouldn't we mention TileStache somewhere?
It seems like installation instructions should make that mention, but it doesn't currently make any reference to our TileStache fork (integration-1).

@nvkelso I added an update that mentions TileStache in the wiki.
https://github.com/mapzen/vector-datasource/wiki/Mapzen-Vector-Tile-Service#install-python-dependencies

LGTM, thanks.

Clear now, thanks!


Feature/query service

What is this pull request?
Implementation of torii QueryService
Why do you implement it? Why do we need this pull request?
Server for queries from clients.
How to use the features provided in the pull request?
Use ServerRunner::run() then QueryServer starts.
Details/Features
List of features / major commits

Add torii/query_server.hpp/cpp
Add QueryServer to ServerRunner
Add connection test of QueryServer

I found some bug as following:

The bug is fixed by merging event-loop about CommandService and QueryService that is using same port.
Now, QueryService is async. If clients want to use sync, they should request with async and block their thread.
If we have to make QueryService grpc sync only, maybe ports of CommandService and QueryService have to be different (I don't know).
And it's better that we'll create a test that runs many processes (clients) and one server, then calculates how many requests can be resolved.


is dronekit-python api only for Mavproxy?

I wonder if there are any other use cases for droneapi. and if I don't want to use mavproxy, does it mean I have to write my own mavlink layer? and how can i do it

Hi @sky129225 there have been talks of moving the core of MAVProxy into a library and use that instead as to have DroneKit be a standalone, work on that hasn't been made but we would be happy to guide you through the changes needed if you feel like working on it makes sense to you, come find us on Gitter https://gitter.im/diydrones/dronekit-python and or reply here

I wonder if there are any other use cases for droneapi. and if I don't want to use mavproxy, does it mean I have to write my own mavlink layer? and How do I start to Compile the code?
api = local_connect()
vehicle = api.get_vehicles()[0]
i think i just to compile the above code to create the new mavlink layer
my Program is use "mavutil.mavlink_connection(port, baud, autoreconnect=True)"As connection with drone how can i add in ?

Hi Sky

I wonder if there are any other use cases for droneapi.

What use cases do you have in mind?

and if I don't want to use mavproxy, does it mean I have to write my own mavlink layer?

Yes it does.
As @mrpollo says, you will need to discuss the detail with us, and probably gitter is the place to do that.

How do I start to Compile the code?

The detailed instructions are still waiting a pull request #149 to be merged. In summary you need to clone this repo, and then you can build using the following commands (on linux)
sudo python setup.py build
sudo python setup.py install

api = local_connect()
vehicle = api.get_vehicles()[0]
i think i just to compile the above code to create the new mavlink layer
my Program is use "mavutil.mavlink_connection(port, baud, autoreconnect=True)"As connection with drone how can i add in ?

I don't really understand what you mean. The above instruction if run in a script inside mavproxy will fetch you a vehicle. BUT, you for this to work you need to be running inside MAVProxy, as this is the tool that actually sends the message.
Or to put it in another way,

MAVProxy is the MAVLink implementation used by DroneKit
DroneKit is written as a MAVProxy module.

So to use DroneKit without MAVProxy you would have to write a new layer for doing all the MAVLink communication, and write DroneKit to use it. I hope that makes sense.

@sky129225 The topics on how to build the source can now be found in the documentation here

@tcr3dr I think this has been answered as far as it can be and should be closed.
I believe there is a long term strategic objective to to allow DK to be used as "just another Python Module" (possibly by modifying MAVProxy so that it can be loaded as a module). Do you think it reasonable to create a separate issue for this? (and if so, can you do so). I think it would be useful for the community to be able to track our efforts in this area.

@hamishwillee Sounds good.


adding coveralls

Added coveralls integration to see if this is something we would like to have.

Changes Unknown when pulling a3a2ef65b733fac87cef48363aa790a25a69c32f on fooelisa:develop into ** on napalm-automation:develop**.

https://github.com/napalm-automation/napalm-base/pull/91 will probably increase with 1-2% the coverage :P

I really want this, howerver, bear in mind that for us, functional/acceptance tests are more important than unit tests and coverage.

Changes Unknown when pulling 73fe52bb3a8e7618513ab44232f5906e170b8667 on fooelisa:develop into ** on napalm-automation:develop**.

Changes Unknown when pulling d5a37de4c979f1359a707ca1bc1b1cd78bc386b6 on fooelisa:develop into ** on napalm-automation:develop**.

Can't seem to be able to move this to pytest instead of nose, it doesn't pick up the tests at all so it seems. Could you take a look @dbarrosop, what's missing here?

Try: py.test --cov-report term-missing test/ in .travis.yml

Changes Unknown when pulling a3505ee3a15db8919269df6742e4ff03ea12a265 on fooelisa:develop into ** on napalm-automation:develop**.

No missing-term will change the report as to displaying missing lines or not, however pytest is not actually finding/starting the tests at all here (which it does in eos). I think they have to be called "test_*" to be picked up.

Ah ok. Yes pytest needs the tests to begin with test_

Changes Unknown when pulling aaeff9139aeaa04d55712b6f674e9c3e97b9ab2d on fooelisa:develop into ** on napalm-automation:develop**.

Changes Unknown when pulling aaeff9139aeaa04d55712b6f674e9c3e97b9ab2d on fooelisa:develop into ** on napalm-automation:develop**.

oh now I remember, pylama was erroring, did you see this in other modules? -eos looks set up the same to me
napalm_base/__init__.py WARNING: __all__ is defined as a list, this means pydocstyle cannot reliably detect contents of the __all__ variable, because it can be mutated. Change __all__ to be an (immutable) tuple, to remove this warning. Note, pydocstyle uses __all__ to detect which definitions are public, to warn if public definitions are missing docstrings. If __all__ is a (mutable) list, pydocstyle cannot reliably assume its contents. pydocstyle will proceed assuming __all__ is not mutated.

This has been broken for a while, closing it. Please, reopen and fix when you have the time.


DocumentDescriptor.contentType ignored in documents.write()

I am using client.documents.write() to ingest documents in the database.  The documents are provided as read streams.  I use contentType on the document descriptors to force the content to be stored as JSON.  There is one specific case where it is not taken into account though: it stores the document as a binary node.
Here is a piece of code to reproduce the problem (adapt the connection details as needed, and maybe adapt the path ./package.json to any JSON file):
"use strict";

const fs  = require('node:fs');
const ml  = require('marklogic');

async function main()
{
    const client = ml.createDatabaseClient({
        host:     'localhost',
        port:     '8000',
        database: 'Documents',
        user:     'admin',
        password: 'admin',
        authType: 'DIGEST',
    });
    // /uri works, /uri.ext fails
    // 2 docs in the array works, 1 doc fails
    const res = client.documents.write([{
        content:     fs.createReadStream('./package.json'),
        uri:         '/uri.ext',
        contentType: 'application/json',
    }]);
    console.dir(await res.result());
    client.release();
}

main();

This will store the document as a binary node, instead of a JSON document.  Two interesting points to note:

if you change the URI from /uri.ext to /uri, it stores it as JSON (the "extension" seems to be the difference that matters, here, .123 or .abc reproduce the problem as well)
if you add a second document descriptor in the array (e.g. by duplicating the one above and changing the URI to /uri2.ext), it stores both documents as JSON

Looking into this. Thanks.!

This is might be a REST Api issue.

This is working as designed based on the docs at https://docs.marklogic.com/guide/rest-dev/intro#id_49079 - we will track internally if that's not the case.


| Unknown error: HTTPSConnectionPool(host='www.binance.com', port=443): Max retries exceeded with url: /bapi/growth/v1/friendly/growth-paas/third-party/access/accessToken (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:992)')))

| Unknown error: HTTPSConnectionPool(host='www.binance.com', port=443): Max retries exceeded with url: /bapi/growth/v1/friendly/growth-paas/third-party/access/accessToken (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:992)')))

Join my tg channel for solution of this


fix(Possible Values): possible value validation is restored

Closes #287

@homu r+

:pushpin: Commit f121ae7 has been approved by sru

:hourglass: Testing commit f121ae7 with merge 5d7ce3e...

:sunny: Test successful - status


"[stuck]" without duplicate rules

Here's a "stuck" repro without duplicate rules (!):
rule cg
   command = touch $out; touch b;

build a b: cg c
build c: cg a

$ ninja
ninja: build stopped: stuck [this is a bug].

(Originally reported in a comment in #867. https://github.com/martine/ninja/issues/867#issuecomment-65918850 there suggests a fix, but it's possible that it's not a good fix.)

Even simpler:
rule ct
  command = cat $in > $out
build foo bar: ct foo

(found by afl-fuzz when I replaced the "[stuck]" printf with a deliberate crash)

It must be the multiple outputs, then?

Yes, apparently there's a bug when a cycle is entered via an edge with multiple outputs, from an output not participating in the cycle – ninja fails to detect that cycle currently.

I think the Right Fix here is to let Plan::CheckDependencyCycle() look for a cycle of Edges, not Nodes. want_ works on Edges, so the cycle checker should too.
Printing the cycle still needs to output Node paths, so I need to play a bit and see how this is nicest (have a stack<pair<Edge*,Node*>>? Look at the in_edge of all the nodes in the stack<Node*>?)

(I'm pretty with the fix I ended up checking in, it didn't really add much work and it was very localized.)


Bump client patch 2.0.0 internal.2.3.1

Commands used:
npm run typetests:prepare -- --reset
npm run typetests:gen
flub bump client -t patch

I also cherry-picked #13671 because request-handler is also broken on this branch.

@tylerbutler FYI https://github.com/microsoft/FluidFramework/pull/13695 already included #13671. Presumably git did the right thing but wanted you to be aware


Feature request: phone audio as source

I would really appreciate being able to connect my phone/pc to home assistant like a source (not over spotify/miracast, but like a bluetooth speaker).
The idea is, that there is no easy way to stream local phone music/pc game sounds/smart tv audio to HA, thus all the products need a separate playback system.
Please vote, if this is something you would like to see too...

Thanks for your request


Improve edit.select_word()

select_word() has several issues as per https://github.com/knausj85/knausj_talon/issues/1084.
Notably accidental selection of symbols and word selection breaking if the caret is before a new line.
This pull request aims to resolve these.
Note: This is only tested on MacOS, though it uses higher level functions for all operations, so I don't foresee any major issues on other operating systems.

I haven't looked at this closely but it seems kinda complicated for such a simple feature. I'd appreciate the chance to give it a think before merging - I might have time this weekend or next, so could you gimme a couple of weeks to look at it? If I haven't gotten round to it by then go ahead and merge.

I'm happy to wait :+1: .

Please do take a look 👍

it seems kinda complicated for such a simple feature

One thing worth noting is that it does the same thing as the existing implementation (go one character to the left right, go an entire word to the left, then highlight the word to the right) except that the initial step to the right is conditional on what the character to the right is.

After brainstorming on a maintenance session we were unable to come up with any simpler way to do this. I've simplified the code slightly by turning that list into a string, but otherwise lgtm.
My only note is that this won't work in editors like emacs where pressing left/right with a selection active doesn't always put you at the left/right end of the selection. But, emacs already needs tons of special cases; chrome is far more common than emacs.

I'll let someone else take a look at my changes and merge this, or merge it myself in a week if nothing happens.

Looks good to me, thank you both :).