Wrong Postgresql DDL for table with serial column

System information:

Operating system (distribution) and version: Ubuntu 20.04
DBeaver version: 7.2.5

Connection specification:

Database name and version: Postgresql 12

Describe the problem you're observing:
When extracting DDL for table with serial type for primary key, it creates invalid DDL:
CREATE TABLE public.testtable ( 	id serial NOT NULL DEFAULT nextval('public.testtable_id_seq'::regclass),	 	testchar varchar NULL, 	CONSTRAINT testtable_pkey PRIMARY KEY (id) );
When running this SQL, Postgresql thows error:
SQL Error [42601]: ERROR: multiple default values specified for column "id" of table "testtable"
DDL should probably omit the DEFAULT nextval('xxxx'), because serial type automatically creates the default value and sequence OR the type should be changed to integer (and DDL for sequence should be included).
Steps to reproduce, if exist:
Create test table with this SQL:
CREATE TABLE public.testtable ( 	id serial NOT NULL, 	testchar varchar NULL, 	CONSTRAINT testtable_pkey PRIMARY KEY (id) );
Show DDL for this table a try to run it.

Thanks for the bug report.

Additional comments:

the bug is also valid for bigserial and smallserial types
i think DDL should change the type to integer and provide DDL for sequence (because the sequence could be with non-default sequence name 'tablename_colname_seq') - see recommeneded DDL in Postgresql doc here

OK, you are right. I tried changing default value of serial column and it automagically converts to datatype integer. So you probably can't have serial type with non default sequence name.

Fixed in 7.3.0

Thanks :-)

verified

Is it possible that this error is still happening for actual DBeaver versions?

DBeaver: version 21.1.4
DB: PostgreSQL 8.4
Tables created with a SERIAL datatype ar shown as VARCHAR instead of integer.  Either at the Columns list but also in the DDL code.
For newer PG versions (i.e. PG 11) it is shown OK.

Hello @ramirobarreca
Could you provide table DDL as an example? And some screens. I can't reproduce in DBeaver 21.1.4


React Native 0.60 android X migration

Build fails on react native 0.60 due to new android x libraries.

This is something I need to work on, but for now you can use Jetifier to get it building again.


Feature/deploy upgrade extension

:rocket: deployment of gp-redirect succeeded (http://gp-redirect-pr-16.dev.beta.nhschoices.net)


#202 BIoTMessage, brightics IoT biotFormatter

added BIoTMessage, brightics IoT biotFormatter (BIoTMessage <-> bytepayload)
I will reuse the mqttSender to connect and sent IoT data.
Sorry for the late because of installing and testing under strong security policy;;  :-)

@hyogrin there are some things you should fix:

Build fails, please execute make and make test before commit the code
All commits need DCO sign-off. Info is in the yellow box on this page
Also run go fmt before commit

@hyogrin There needs to be an issue associated with this PR that describes what you're trying to accomplish. I would prefer the issue be created before the PR so that it can be classified with regard to the Delhi or Edinburgh releases, or if it's a bug vs enhancement.

@tsconn23 PR was this one "Brightics IoT export connector - https://github.com/edgexfoundry/edgex-go/issues/202"  jpwhitemn added enhancement  feature  export-services  labels on May 12 for Edinburgh but I think Delhi will be fine because It is just an enhancement.


🐛 fix: update windows platform specific key codes

This pull request updates key mappings in pytermgui/input.py to align behavior on NT platforms with the results seen using the ptg -g command.
Fixes #133.
Included a video of the form example and other running ptg -g output.
https://github.com/user-attachments/assets/8e9daf35-7fa0-4562-9014-09c7cead8846
https://github.com/user-attachments/assets/4162f498-9e93-4b34-8275-3c6f845cb009
If you need any further info, let me know!

Neat! Is this valid for Windows in general? The original keycodes were valid for some iteration of it, but I can't test it so I'm not sure.
Looks good otherwise!

Is this valid for Windows in general?

That's what I'm concerned about, I'll try to do some testing later and let you know! I'm running Windows 11 Pro 23H2 (can't get the specific build right now).

From reading Console Virtual Terminal Sequences and about_ANSI_terminal articles it seems that the implementation is correct, since the ANSI ESC keycode is 0x1b, and the arrows keycodes is basically ESC [ A (0x1b[A), ESC [ B (0x1b[B), ESC [ C (0x1b[C), ESC [ D (0x1b[D) and etc.
But I couldn't find any of the ANSI keycodes from the previous code. Do you still have the source where you got them from?

IIRC it came from here, but I now that I look at it I might have gotten them wrong (used \x1b instead of \xe0)!
It seems good otherwise so I'll merge this in, thank you!


Re factoring and Unit Testing

Lots of re factoring needs to be done. Most of the code is in a mess and needs to be de-mangled and tested. This will obviously be very tedious and boring but it'll be worth it in the long run (hopefully).

This has been half done with the new React-based code. However, unit tests need to be done.


WRQ-9476: Updated node modules' major version

Checklist

[X] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[X] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Updated node modules' major version and fixed a small bug for qa-virtualgridlist
Resolution
Updated node modules' major version

@reduxjs/toolkit ^1.9.7 → ^2.0.1
react-redux ^8.1.3 → ^9.1.0
redux ^4.2.1 → ^5.0.1

Additional Considerations
There are no breaking changes that affect our code

@redux/toolkit
react-redux
redux

Links
WRQ-9476
Comments
Enact-DCO-1.0-Signed-off-by: Alexandru Morariu<EMAIL_ADDRESS>

There's no information about changes of samples/qa-virtualgridlist/src/views/MainView.js.
Please add about those on Additional Considerations.

There's no information about changes of samples/qa-virtualgridlist/src/views/MainView.js. Please add about those on Additional Considerations.

Done


searchinput

adds a new SearchInput component
resolves #228
notable changes:

update textinput styles to allow for close icon placement
add new onClear prop to textinput that will show a close icon and bind an onclick function to the icon
new searchinput component

TODO:

[x] disable label and sublabel support
[x] usage guidelines
[x] refocus input on clear
[x] type="search" research

@jaketrent i changed up the approach based on our previous discussions. i'll try to summarize below
in TextInput there is a new prop call fieldAfter that allows a node to be added in the markup after the field input. also the markup and styles have been changed so that there is a new div that provides a new flex container around the input and what is inserted using fieldAfter. trying out a few different approaches, i felt this provided the best decoupling and extensibility.


Boss enemy

boss will shoot from multiple points
large health
cool effect on death (maybe)

cool effect working hehe


OONI Run v2: change 'add link' to 'install link' in new link install flow

When you are adding a new run v2 link, the button to install the link currently says 'ADD LINK' it should say 'INSTALL LINK'

Confirmed that it says 'INSTALL LINK' in 3.8.6-beta.671


Dev 13 - Implemented the experience page content

Please make sure these boxes are checked before submitting your PR, thank you!

[x] Make sure all the tests are still passing.
[x] Make sure the test coverage is still 100%.
[x] Make sure your source branch is correct.
[x] Make sure your destination branch is devel.
[x] Make sure the name of the PR has a correct DEV-# identification prefix.
[ ] Make sure you reviewed all your changes and they look correct.
[x] Make sure all the commits have a correct format.
[x] Make sure you refer related issues for you PR.
[x] Make sure you add KovDimaY as a reviewer and assignee of your PR.

Take a look at the Issue #18

Coverage remained the same at 100.0% when pulling 6b96e46cff01d3bd9f97d86102453cd66a17834f on DEV-13 into 42f0b28106b117b3e2bcf4d45ebe6aabdcd810ea on devel.

Everything is ok, I am going to merge it.


Issue with the custom wal function for setting the wallpaper

Hi,
I use i3wm with dual monitors, and therefore made a custom function to span my wallpaper as explained here. However, whenever I first boot into my wm or reload my i3 config, wal sets my wallpaper with the default fill mode instead of my custom wal-center function. I tried to use wal-center -R in my .xinitrc to see if that fixes it, however that didn't seem to work. Is there any known solution for such an issue?
My .bashrc
   (cat ~/.cache/wal/sequences &)#
    wal-center() {
     wal -n -i "$@"
     eh --no-xinerama --bg-center "$(< "${HOME}/.cache/wal/wal")"

My .xinitrc
 wal-center -R

I'm not sure this is correct.
Probably, .xinitrc can't call your function at all. Usually it is being read by startx, or similar program. Which is not an interactive shell. So, your .bashrc is not being sourced, and functions are not being inherited, so there is no wal-center in .xinitrc
Even if it could be called, the way you pass params in it would expand call to wal -n -i -R, which results in this error wal: error: argument -i: expected one argument .

The way I see a solution is simply put this calls directly to .xinitrc:
.bashrc:
(cat ~/.cache/wal/sequences &)

.xinitrc
wal -n -R
feh --no-xinerama --no-fehbg --bg-center "$(< "${HOME}/.cache/wal/wal")"

You can also keep the wal-center function in .bashrc in case you want to change wallpaper, not restore previous.

@Mikle-Bond Thank you for your response, yes, eh was indeed a typo for feh!
Your answer makes complete sense, and theoretically should work. However, for some reason the feh command in my xinitrc doesn't execute after I login. Here's the complete xinitrc for your reference:
 setxkbmap gb

   exec start-pulseaudio-x11

   dbus-update-activation-environment --systemd DISPLAY
   eval $(/usr/bin/gnome-keyring-daemon --start --components=pkcs11,secrets,ssh)
   export SSH_AUTH_SOCK

  #From pywal wiki:
  # Add this to your .xinitrc or whatever file starts programs on startup.
  # -R restores the last colorscheme that was in use.
  wal -n -R
   feh --no-xinerama --no-fehbg --bg-center "$(< "${HOME}/.cache/wal/wal")"

  exec i3

I even tried to use the exec command before the wal and feh commands respectively, yet that didn't seem to work either. Any idea why?

You should only have one exec in your .xinitrc and it should be the last command at the bottom.

Closing this as it isn't a bug. Feel free to continue discussing this.

@dylanaraps Thank you very much, this solved it!


can't see the ui

i installed today the plug-in added some podcasts but i can't find a way to open the ui, tried adding the show button using commander but nothing happens when i click it

Hi - it appears in your right sidebar. The icon for the player can be hidden if the sidebar isn't wide enough. Can you check if this is the case for you?

Yes thank you I found it but it's really uncomfortable in that position can
I somehow disable it there and use commander to put it somewhere else?
Il gio 3 ago 2023, 10:48 Christian Bager Bach Houmann <
@.***> ha scritto:

Hi - it appears in your right sidebar. The icon for the player can be
hidden if the sidebar isn't wide enough. Can you check if this is the case
for you?
—
Reply to this email directly, view it on GitHub
https://github.com/chhoumann/PodNotes/issues/85#issuecomment-1663557359,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BBWE53NPZSBFPKVFSJXWVZTXTNQW7ANCNFSM6AAAAAA3CNREIY
.
You are receiving this because you authored the thread.Message ID:
@.***>

You can drag the icon wherever you want. I don't use the Commander plugin myself, so I don't know about it.

Yes but only in the bar where it's put I'd like to move it on the left
sidebar. And It looks like i can't
Il gio 3 ago 2023, 11:17 Christian Bager Bach Houmann <
@.***> ha scritto:

You can drag the icon wherever you want. I don't use the Commander plugin
myself, so I don't know about it.
—
Reply to this email directly, view it on GitHub
https://github.com/chhoumann/PodNotes/issues/85#issuecomment-1663605137,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BBWE53PD3JDBCXZUJUVR2YDXTNUEBANCNFSM6AAAAAA3CNREIY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Update readme for headers names

Ref: #569

thanks @y4ashida !

@booleanbetrayal
I realized this commit isn't good, because 'config/applicaiton.rb' is loaded before config/initializers/devise_token_auth.
So, if you change headers names in config/initializers/devise_token_auth, the changes isn't reflected in 'config/applicaiton.rb'.
Moreover, DeviseTokenAuth.headers_names isn't defined in some cases. #591
Sorry to trouble you. I think this commit should be reverted.


prevent type conversion to Big and BigQueryTimestamp

Whenever the result of the query has floating numbers or timestamp, the library returns Big and BigQueryTimestamp classes instead of simple Number and Date.
Is there a way to prevent that?

Hi @atlanteh, if you're able to provide a small snippet/example of the behavior you're seeing that would be very helpful for debugging!


bundle.js 404

I cloned the repo and followed the instructions, everything installed properly. When I run npm run hot-server + npm run start-hot or npm run dev, the window opens up, but the inspector tools complain about the missing bundle.js file

I can't reproduce this issue with a new fresh cloned repo.
git clone git@github.com:chentsulin/electron-react-boilerplate.git
cd electron-react-boilerplate
npm i
npm run dev

Are there any errors shown on your terminal or renderer console? I am going to close this issue. But if you can provide more detail information, feel free to reopen this. Then, we can trace further.

yeah, tried again and it worked. Not sure what changed

Hi,
I had same issue when instance of Browsersync was running on port 3000.
Terminating Browsersync and reload (cmd + r in electron window) did the job for me.

I had the same error.
As amejias101 I tried deleting the cloned repo and cloning again and it worked for me.

I had the same error. Seems like Electron opens before the express server that serves the bundle.js. When I reload the page (command + R) it works.

@amejias101 figure out a way to get it to start without reloading?


Pkg 5219 update v3.0.3

Destination channel: defaults
Links

PKG-5219
Upstream repository
Upstream changelog/diff
Relevant reverse dependency PRs:

https://github.com/AnacondaRecipes/torchvision-feedstock/pull/13

Explanation of changes:

Required as a dependency for torchvision, their smoke test checks for it
Pull changes from conda-forge, keeping changes from our repo that are still relevant
Pin yasm as per upstream Building.md
Satisfy linter

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_20hvju27pc/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:45: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
clone/recipe/meta.yaml:34: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_e8mp00tksz/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:35: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
clone/recipe/meta.yaml:46: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_47b41tdzps/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:46: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
clone/recipe/meta.yaml:35: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_d74f891omh/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:46: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
clone/recipe/meta.yaml:35: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_1cq4ymd3f0/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:46: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
clone/recipe/meta.yaml:35: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_034x5eavjx/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:35: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
clone/recipe/meta.yaml:46: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_ecj9urax8b/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:46: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
clone/recipe/meta.yaml:35: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_a4h268was1/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:35: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
clone/recipe/meta.yaml:46: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_cc8qumcx3e/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:35: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
clone/recipe/meta.yaml:46: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_3crzjtzgx7/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:46: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
clone/recipe/meta.yaml:35: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_647tkg305z/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:61: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
clone/recipe/meta.yaml:50: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_bfshpb7b66/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:51: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
clone/recipe/meta.yaml:62: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found

Linter check found the following problems:
ERROR conda.cli.main_run:execute(125): `conda run conda-lint /tmp/abs_24sssvrwta/clone` failed. (See above for error)
The following problems have been found:
===== ERRORS =====

clone/recipe/meta.yaml:62: invalid_url: https://libjpeg-turbo.org/Documentation/Documentation : Not reachable: 406
clone/recipe/meta.yaml:51: invalid_url: http://www.libjpeg-turbo.org/ : Not reachable: 406
===== Final Report: =====
2 Errors and 0 Warnings were found


Unable to determine the release in /usr/local/chroots/mojave. Please specify it with -r. || focal does not belong to any supported distribution.

name: mojave
encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/mojave...
crouton: version 1-20200116214215~master:9017d640
release: bionic
architecture: amd64
targets: core,audio,cli-extra
host: version 12739.111.0 (Official Build) stable-channel coral
kernel: Linux localhost 4.4.205-17074-gdc1f94d55924 #1 SMP PREEMPT Mon Mar 30 23:23:18 PDT 2020 x86_64 x86_64 x86_64 GNU/Linux
freon: yes
Please describe your issue:
I'm not exactly sure what happened but I can't update my chroot.
Here are the commands and output:
chronos@localhost ~ $ sudo crouton -un mojave
Downloading latest crouton installer...
#################################################################################################################################################### 100.0%#################################################################################################################################################### 100.0%
/usr/local/chroots/mojave already exists; updating it...
Unable to determine the release in /usr/local/chroots/mojave. Please specify it with -r.
chronos@localhost ~ $ sudo crouton -un mojave -r focal
focal does not belong to any supported distribution.

I installed bionic and then upgraded with update-manager-core's do-release-upgrade and it upgraded successfully. That's the only thing I can think of that might have caused this issue.

@kingliamb
If you run sudo crouton -r list you'll see 'focal' is not listed:
Recognized ubuntu releases:
    warty! hoary! breezy! dapper! edgy! feisty! gutsy! hardy! intrepid! jaunty!
    karmic! lucid! maverick! natty! oneiric! precise! quantal! raring! saucy!
    trusty! utopic! vivid! wily! xenial yakkety! zesty! artful! bionic* cosmic!
    disco* eoan*

Releases marked with ! are upstream end-of-life, and should be avoided.
Releases marked with * are unsupported, but may work with some effort.

So specifying '-r focal' will not work since 'focal does not belong to any supported distribution'.
You can still update & upgrade your chroot in the chroot but you can no longer update your version of crouton IIUC.
Hope this helps,
-DennisLfromGA

Added focal to the list of Ubuntu releases.  It should work* now.
* for certain totally-untested definitions of "work"


Relationship tests rendering in docs on the to model instead of the model the test was defined in

Describe the bug
A clear and concise description of what the bug is. What command did you run? What happened?
relationships tests are rendering on the to model docs instead of the model that the test was defined in.
Steps To Reproduce
In as much detail as possible, please provide steps to reproduce the issue. Sample data that triggers the issue, example model code, etc is all very helpful here.

dbt init a new project
add a relationship test to the example my_second_dbt_model.sql

version: 2

models:
    - name: my_first_dbt_model
      description: "A starter dbt model"
      columns:
          - name: id
            description: "The primary key for this table"
            tests:
                - unique
                - not_null

    - name: my_second_dbt_model
      description: "A starter dbt model"
      columns:
          - name: id
            description: "The primary key for this table"
            tests:
                - unique
                - not_null
                - relationships:
                    to: ref('my_first_dbt_model')
                    field: id

dbt docs generate
dbt docs serve

Expected behavior
A clear and concise description of what you expected to happen.
The relationship test renders in the model that the test was defined in. Otherwise, if I have a table that has foreign keys in many other tables (i.e. date dimension), they will all show up on the date dimension, which isn't as useful as if the foreign key relationship showed in the model it was defined in, i.e. a fact table.
The current behavior is also unusual since foreign keys in a traditional RDBMS are defined on the the foreign table pointing to the parent table, whereas now in the docs the parent table is pointing to all of the child tables.
Screenshots and log output
If applicable, add screenshots or log output to help explain your problem.
System information
Which database are you using dbt with?

[ ] postgres
[ ] redshift
[x] bigquery
[ ] snowflake
[ ] other (specify: ____________)

The output of dbt --version:
dbt --version
installed version: 0.19.0
   latest version: 0.19.0

Up to date!

Plugins:
  - bigquery: 0.19.0
  - snowflake: 0.19.0
  - redshift: 0.19.0
  - postgres: 0.19.0

The operating system you're using:
macOS 10.15.6
The output of python --version:
3.8.1
Additional context
Add any other context about the problem here.

Well, I realized what my issue is... The relationship test shows up on the to model, instead of the "from" model that the test is defined in. This seems like the opposite of how I would expect this to work, but a misunderstanding on my part.

@mascah Thanks for opening! I agree, this is weird. The relationship is from my_second_dbt_model (foreign/child/"many" table) to my_first_dbt_model (parent/"one" table).
From mucking around with this locally, it does appear that the relationships test will indeed not render (as your issue originally stated) if the names of the child column and parent (field:) differ. Weird!
In any case, I believe the fix for this would need to come in the dbt-docs codebase, since all the requisite information is available in the manifest. I'm going to transfer this issue over there.


Throw helpful error when router reducer not mounted under "router"

https://github.com/supasate/connected-react-router/issues/174

@supasate Addressed your comments

Thanks for working on this!


storageConnectionString Error

modify the storageConnectionString value

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. We will now review your pull request.
Thanks,
Microsoft Pull Request Bot

@bruschen : Thanks for your contribution to the Azure documentation! The author, @sethmanheim, has been notified to review your proposed change.

@bruschen Thank you for the contribution. Can you please explain why you feel this change is necessary? It does not seem to affect the execution of the program.

Thanks for your reply, I have implement a demo project with the Sample code.
and the connection string will not be work,
after compare with the connection string from azure, there is some information need to be add,
so that the connection will be work, or we can suggest user copy the connection string from the azure

@bruschen OK, but the tutorial already states "replace the Main method in the Program class with the following code, substituting the event hub name and the namespace-level connection string that you saved previously, and the storage account and key that you copied in the previous sections."
Are you sure you are using the namespace-level connection string and not the entity's connection string?

#please-close


⚠ Turnos 24x7 has degraded performance

In 001c1a2, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 995 ms

Resolved: Turnos 24x7 performance has improved in 102b6ba.


Newton's method may accept complex initial guesses (?)

Newton's method should work for complex roots. Is there any trouble in to change x0::Real to x0::Number in the newton routines?

It doesn't quite fit in with the description of the package (function f:R -> R). I tried just changing Real to Number and ran into issues with the tolerance. It would be a bit more work than just changing the type. If you want to put together a pull request with the changes, it doesn't 'seem unreasonable.

I opened a pull request with some changes. I successfully tested newton(f, df, x0::Complex) with different functions f(x), for example:
f(x) = x^3 - 1.
df(x) = 3.0x^2

z = newton(f, df, 0.5+im)     # (Complex{Float64}) -0.5 - 0.8660254037844386im
y = newton(f, df, 0.5)        # (Float64) 1.0

What do you think? :)


Is support for OSX 10.10 part of the roadmap?

No, I actually ripped out the old binary protocol before this release.
I think most iOS/OS X devs out there are using the latest OS because the Xcode requirements.


Add annotation creation access flag

Adds a new girder access flag which demarcates whether or not a user has permission to create annotations, allowing users to create annotations without having write access to a folder/item.  Also creates a new endpoint indicating whether or not the user has creation permissions (via write access or the flag) and makes current annotation creation procedures check for the access flag.

Other than preferring a defined constant to a string, this looks good.


2003 implement a trained xview model in the xview model example

Created and trained a custom xview model that gives nonzero results in the metrics on mlflow. I added the xview model to the s3 bucket https://s3.console.aws.amazon.com/s3/buckets/armory-library-data?region=us-east-2&tab=objects.

Created a new branch with the xview example updates since the commit history on this branch had issues with it.


chore: update netlify-onegraph-internal and regen snapshots

Summary
The ActionFunction import for remix was in the wrong place, this updates the codegen to put it in the right place, and incorporates the expectations from https://github.com/remix-run/remix/pull/1835
For us to review and ship your PR efficiently, please perform the following steps:

[X] Update or add tests (if any source code was changed or added) 🧪
[ ] Make sure the status checks below are successful ✅

The two failures here seem unrelated (docs lint, and contributor list), not sure how to debug.

Superseded by #4239


unable to get the define withe the import  . package

VSCode Version: Code 1.13.1 (379d2efb5539b09112c793d3d9a413017d736f89, 2017-06-14T18:13:05.928Z)
OS Version: Darwin x64 16.6.0
Extensions:

Extension
Author
Version

vscode-docker
PeterJausovec
0.0.16

python
donjayamanne
0.7.0

gitlens
eamodio
4.3.1

Go
lukehoban
0.6.63

java
redhat
0.8.0

vscode-icons
robertohuertasm
7.12.0

Steps to Reproduce:
1.golang code
2.when I import package with . package ,my func can't move to the defination

the import is here

I don't know Go, but if the language server is provided by an extension, you might need to report it to the extension's repository, not here.

Gogland can do it!

@Tyriar with the latest version  v1.15.1, the problem still occurs. And I find that Gogland can work well.

@ramya-rao-a might be able to help you further.

@zz-bmj The default tool used for finding definitions doesn't work well with dot imports. Set go.docsTool to gogetdoc, install gogetdoc when you get prompted and that should work.
In the future, please log an Go related issues in VS Code at https://github.com/Microsoft/vscode-go


Error in TF.pad API docs

Please note the following error in tf.pad in "array_ops.md":
Example 1 currently reads as follows:
# 't' is [[1, 1], [2, 2]]
# 'paddings' is [[1, 1]], [2, 2]] ##This is not a valid tensor
# rank of 't' is 2
pad(t, paddings) ==>
     [[0, 0, 0, 0, 0] ##This is not the correct output
      [0, 0, 0, 0, 0]
      [0, 1, 1, 0, 0]
     [[0, 2, 2, 0, 0]
      [0, 0, 0, 0, 0]]

It can be fixed as follows:
# 't' is [[1, 1], [2, 2]]
# 'paddings' is [[1, 1], [2, 2]]
# rank of 't' is 2
pad(t, paddings) ==>
    [[0, 0, 0, 0, 0, 0]
     [0, 0, 1, 1, 0, 0]
     [0, 0, 2, 2, 0, 0]
     [0, 0, 0, 0, 0, 0]]

Thanks for letting us know. This is now fixed upstream, and should be released soon.


Use JoinPath to construct vSphere url

What this PR does / why we need it:
Companion PR to https://github.com/kubermatic/kubermatic/pull/12861.
Which issue(s) this PR fixes:

Fixes #
What type of PR is this?
/kind bug
Special notes for your reviewer:
Does this PR introduce a user-facing change? Then add your Release Note here:

No longer fail constructing vSphere endpoint when a `/` suffix is present in the datacenter configuration

Documentation:

NONE

/cherry-pick release/v1.56

/cherry-pick release/v1.57

/cherry-pick release/v1.58


s390x assembly pack: fix bn_mul_comba4

looks like it is never called though: Only place where its not #if 0 -ed is in bn_mul_recursive which is inside #ifdef BN_RECURSION which is never defined as far as i can tell.

If I'm mistaken, please let me know and I'll try to dig a lot deeper....

At that point c1 holds the least significant word of the product, which should be written to the leftmost part of the output buffer (pointed to by r2). Instead it was written to the leftmost part of the first factor (pointed to by r3) leading to wrong results of the multiplication. I cant tell how this happened, but it i guess its most likely a typo.

Id also fix it for 1.1.1, please indicate if you approve.

Thanks for the explanation.

merged.
master: https://github.com/openssl/openssl/commit/97a986f78289fef71bf8778dc4763458e983750c
1.1.1: https://github.com/openssl/openssl/commit/62c20887be277df27b287451615c90515784a02b


Update docs for 1.25

Issue #, if available:
Description of changes:
Testing (if applicable):
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/lgtm


ct_extra_params doesn't work with Mac OS 10.10

Hi to all!
I can't run normally my common test because rebar doesn't recognize app.config file in ct_extra_params tuple.
{ct_extra_params, "-pa deps/*/ebin -s app_name -config app.config"}.
When I try to run this CT on Linux - it works!
Now I was copied app.config to test directory and start application in function init_per_suite/1 and CT run normally, but it's bad practice - support two config files in the different places, I think.
Help me please!

I don't have access to OS X. @ferd, any idea? Could it be the glob?

I can try it if I get an access to a similar repo. @Prots do you have any open source code to simulate this, or would I have to reimplement dummy suites and apps for this?
Have you also tried -config app instead of -config app.config ? Erlang's erl appears to do some dynamic matching where it picks whether to add or not the trailing .config, but maybe this is being lost in CT.

Guys, the problem was solved. The next string works:
{ct_extra_params, "-erl_args -pa deps/*/ebin -config app.config -s app_name"}.
As I understand, CT think that I got him name of his config file, not app config.

Can this be closed as RESOLVED?


Expose server support for http2 keep-alive

Feature Request
Crates
tonic
Motivation
From what I understood from https://github.com/hyperium/tonic/pull/307, HTTP2 keep alive support was exposed only to the client (unless I missed some way of doing so for the server).
However hyper also supports setting the keep alive interval and timeout for the server.
My motivation for this enhancement is well described here, which I quote:

KeepAlive provides a valuable benefit: periodically checking the health of the connection by sending an HTTP/2 PING to determine whether the connection is still alive. However it has another equally useful benefit: signaling liveness to proxies. Consider a client sending data to a server through a proxy. The client and server may be happy to keep a connection alive indefinitely, sending data as necessary. Proxies, on the other hand, are often quite resource constrained and may kill idle connections to save resources. Google Cloud Platform (GCP) load balancers disconnect apparently-idle connections after 10 minutes, and Amazon Web Services Elastic Load Balancers (AWS ELBs) disconnect them after 60 seconds

Proposal
I suggest that we only support setting http2_keep_alive_interval, with something along the lines of:
--- a/tonic/Cargo.toml
+++ b/tonic/Cargo.toml
@@ -64,7 +64,7 @@ prost-derive = { version = "0.6", optional = true }
 async-trait = { version = "0.1.13", optional = true }

 # transport
-hyper = { version = "0.13.4", features = ["stream"], optional = true }
+hyper = { version = "0.13.4", features = ["stream", "runtime"], optional = true }
 tokio = { version = "0.2.13", features = ["tcp"], optional = true }
 tower = { version = "0.3", optional = true}
 tower-make = { version = "0.3", features = ["connect"] }
--- a/tonic/src/transport/server/mod.rs
+++ b/tonic/src/transport/server/mod.rs
@@ -69,6 +69,7 @@ pub struct Server {
     init_stream_window_size: Option<u32>,
     init_connection_window_size: Option<u32>,
     max_concurrent_streams: Option<u32>,
+    http2_keepalive_interval: Option<Duration>,
     tcp_keepalive: Option<Duration>,
     tcp_nodelay: bool,
 }
@@ -221,6 +222,22 @@ impl Server {
         }
     }

+    /// Set whether HTTP2 Ping frames are enabled on accepted connections.
+    ///
+    /// If `None` is specified, HTTP2 keepalive is disabled, otherwise the duration
+    /// specified will be the time interval between HTTP2 Ping frames.
+    /// The timeout for receiving an acknowledgement of the keepalive ping is the default of
+    /// [hyper](https://docs.rs/hyper/0.13.4/hyper/server/struct.Builder.html#method.http2_keep_alive_timeout).
+    ///
+    /// Default is no HTTP2 keepalive (`None`)
+    ///
+    pub fn http2_keepalive_interval(self, http2_keepalive_interval: Option<Duration>) -> Self {
+        Server {
+            http2_keepalive_interval,
+            ..self
+        }
+    }
+
     /// Set whether TCP keepalive messages are enabled on accepted connections.
     ///
     /// If `None` is specified, keepalive is disabled, otherwise the duration
@@ -320,6 +337,7 @@ impl Server {
         let init_connection_window_size = self.init_connection_window_size;
         let init_stream_window_size = self.init_stream_window_size;
         let max_concurrent_streams = self.max_concurrent_streams;
+        let http2_keepalive_interval = self.http2_keepalive_interval;
         let timeout = self.timeout;

         let tcp = incoming::tcp_incoming(incoming, self);
@@ -336,7 +354,8 @@ impl Server {
             .http2_only(true)
             .http2_initial_connection_window_size(init_connection_window_size)
             .http2_initial_stream_window_size(init_stream_window_size)
-            .http2_max_concurrent_streams(max_concurrent_streams);
+            .http2_max_concurrent_streams(max_concurrent_streams)
+            .http2_keep_alive_interval(http2_keepalive_interval);

         if let Some(signal) = signal {
             server

This proposal leaves http2_keep_alive_timeout to be whichever hyper defaults to (currently 20 seconds).
Note that the code above has not been compiled or tested, I'm happy to submit a PR if you guys think this change is worth it.
The main drawback I see is that the runtime feature of hyper must be enabled for hyper::server::Builder::http2_keep_alive_interval to be used (link).
Alternatives
None that I can think of, but I welcome any suggestions :D
Note
Thanks in advance for your help and thank you for the great work on tonic, hats off!

I think this proposal seems reasonable 👍

Thanks! I'll prepare a PR with the changes as soon as I can.
Do you think it is worth implement this as a cargo feature?
Something like this:
--- a/tonic/Cargo.toml
+++ b/tonic/Cargo.toml
@@ -36,6 +36,7 @@ transport = [
 tls = ["transport", "tokio-rustls"]
 tls-roots = ["tls", "rustls-native-certs"]
 prost = ["prost1", "prost-derive"]
+server-http2-keepalive = ["transport", "hyper/runtime"]

 # [[bench]]
 # name = "bench_main"

@codermobster I don't think it's necessary to feature-gate this. It is also not necessary to add hyper's runtime feature flag.
Why do you suggest to only support http2_keep_alive_interval?  Wouldn't it be useful to also expose  http2_keep_alive_timeout as part of this?
Anyway, I was playing with these settings, both in the client and server but I don't see any change in behavior, do you?. Maybe my expectations are off but when sniffing the traffic I detect no changes no matter which settings I use.

@codermobster I don't think it's necessary to feature-gate this.

Ok, deal.

It is also not necessary to add hyper's runtime feature flag.

Indeed, it's enabled by default. :+1:

Why do you suggest to only support http2_keep_alive_interval? Wouldn't it be useful to also expose http2_keep_alive_timeout as part of this?

Sure, I guess I assumed that defaulting to hyper's setting of 20 seconds would be good enough.
Furthermore, since http2_keep_alive_timeout does not take an Option as an argument, it kind of forces us to have a default setting in tonic, of course here we can use the same 20 seconds that hyper does if you agree.

Anyway, I was playing with these settings, both in the client and server but I don't see any change in behavior, do you?. Maybe my expectations are off but when sniffing the traffic I detect no changes no matter which settings I use.

You got me! I totally took hyper for granted here and failed to find any open issues in github related to it.
Tried to tcpdump my way out of this one, here are the results of some tests with:

hyper version 0.13.8
modified examples/src/health_server.rs and tonic/transport/server/mod.rs for the keep alive settings
modified examples/src/health_server.rs to comment out tokio::spawn(twiddle_service_status(health_reporter.clone()));
used cargo run --bin heath-server
making a request with grpc_cli -proto_path ./tonic-health/proto -protofiles health.proto call --noremotedb localhost:50051 Watch 'service: "helloworld.Greeter"'
running tcpdump -i lo port 50051

5 seconds keepalive timeout and 20 seconds keep alive interval
# some output has been elided
# the two following packets are still output after initiating the connection
17:56:10.541558 IP6 localhost.50051 > localhost.csccredir: Flags [P.], seq 61:124, ack 395, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 63
17:56:10.541571 IP6 localhost.csccredir > localhost.50051: Flags [.], ack 124, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0

17:56:30.543874 IP6 localhost.50051 > localhost.csccredir: Flags [P.], seq 124:141, ack 395, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 17
17:56:30.543901 IP6 localhost.csccredir > localhost.50051: Flags [.], ack 141, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0

# ... eliding some more

The second batch of packets comes exactly 20 seconds after the first.
No more packets received afterwards.
5 seconds keepalive timeout and 30 seconds keep alive interval
# some output has been elided
# the two following packets are still output after initiating the connection
18:02:32.863479 IP6 localhost.50051 > localhost.43986: Flags [P.], seq 61:124, ack 395, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 63
18:02:32.863493 IP6 localhost.43986 > localhost.50051: Flags [.], ack 124, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0

18:03:02.864626 IP6 localhost.50051 > localhost.43986: Flags [P.], seq 124:141, ack 395, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 17
18:03:02.864735 IP6 localhost.43986 > localhost.50051: Flags [.], ack 141, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0

# ... eliding some more

The second batch of packets comes exactly 30 seconds after the first.
No more packets received afterwards.
20 seconds keepalive timeout and 10 seconds keep alive interval
# some output has been elided
# the two following packets are still output after initiating the connection
18:10:44.883423 IP6 localhost.50051 > localhost.48110: Flags [P.], seq 61:124, ack 395, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 63
18:10:44.883436 IP6 localhost.48110 > localhost.50051: Flags [.], ack 124, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0

18:10:54.885248 IP6 localhost.50051 > localhost.48110: Flags [P.], seq 124:141, ack 395, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 17
18:10:54.885270 IP6 localhost.48110 > localhost.50051: Flags [.], ack 141, win 512, options [nop,nop,TS val<PHONE_NUMBER> ecr<PHONE_NUMBER>], length 0

# ... eliding some more

The second batch of packets comes exactly 10 seconds after the first.
No more packets received afterwards.
Concluding
The above is surely not 100% conclusive, but it seems:

keep_alive_timeout makes no difference
after keep_alive_interval the first ping comes in
no more pings recorded after the first one.

Thanks @alce ! I'll prepare an issue in hyper with this info and link it here (credits to you of course!)

Yeah, that's what I saw too. I would expect: PING <-> PING  interval  PING <-> PING  interval PING -> ...timeout. I don't know what's going on there but I guess we'll need to figure that out first.
Keeping hyper's default timeout seems fine to me.

I've opened a PR in hyper to address this issue: https://github.com/hyperium/hyper/pull/2315
Cheers!

Please correct me if I'm wrong, but I'm guessing the adequate approach now is to wait for a new version of hyper to be released (containing the fix) and have tonic depend on it, before going forward with a pull request here, right?
Thanks

@pdcalado We don't need to wait for hyper, we could go ahead with this change as soon as you are ready. However, there won't be a new tonic release until there is a new hyper release and these settings won't do anything until then, of course.


iPhone

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I don't see a description here - please reopen with more details if there is an issue


shorten task name to get shorter CI workspace paths

MSI installer creation tripped over include paths >260 chars

LGTM, can be merged


sideNav - examples for expanding active subsections and highlighting current section

Feature Request

[ ] I’ve read and understood the Contributing guidelines and have done my best effort to follow them.
[ ] I’ve read and agree to the Code of Conduct.
[ ] I’ve searched for any related issues and avoided creating a duplicate issue.
[ ] I've searched the community forums to check for related issues or feature requests

Is this feature request relating to an existing component? Please describe.

Component name: side-nav
Component version: 5.07

Do you have a suggestion for a new component?
Tips/guidance for this component state:

Only expand active subsections to help emphasise which section the user is in and to reduce visual complexity.

Are there options worth exploring to:

Provide stronger visual/semantic emphasis on the current page/section a user is in (highlighting, emboldening, other indicators)
Demonstrate how to only expand (client-side/server side) the section a user is in (current examples show two sibling sections expanded)

Additional context
Implementation of sidenav by health.gov.au (example at https://www.health.gov.au/about-us/corporate-reporting/budgets) provides alternative ideas for highlighting current section.

also relates to  #549


Edit Instead of Double Post

How about a hot fix so that the bot will never double post? Does that make sense? It checks the last comment in the conversation, and if it is the last comment, it will edit it instead of double posting.

It will band-aid a lot of the small edge cases like when it aggressively follows up a ton of times, or what we were discussing earlier in this conversation.

Originally posted by @pavlovcik in https://github.com/ubiquity/ubiquibot/issues/597#issuecomment-1673497830

/assign

Why can't I be assigned?

@0xcodercrane @wannacfuture is the bot down?

Oh wait we just renamed the command sorry. Try /start now!

/start

@pavlovcik
Could you please let me know if it is okay to use https://github.com/ubiquity/ubiquibot/blob/development/src/helpers/issue.ts#L157 ?
I am not sure about that because I found that function is used nowhere and instead https://github.com/ubiquity/ubiquibot/blob/development/src/helpers/issue.ts#L199 were used frequently.
Are they different?

if it is okay to use

@wannacfuture

@ByteBallet  you should use getgetAllIssueComments function.

Okay. Got it.

/wallet

/wallet 0x30fDdD8b3f3a4183734884b6d383da6bf4bf2cd1

/start

/start

@rndquu I remember you are not a supporter of this task citing a reason that this will make bot debugging more difficult.
We can see the edit history of the comment and time stamp of each edit. Is that not sufficient to quell your concern?
@web4er as I recall you simply stated that we should focus on fixing the root problem.
My response was that this solution isn't mutually exclusive to solving the root problem, and will make the conversations a lot neater while we take our time to solve the root problem.

Another point not in favour of editing comments is that some of our tools (ex: https://pay.ubq.fi/audit) and features (the bot's /autopay command which toggles automatic payout for the issue it is used in) rely on a full issue's comment history. So we don't want a permit URL comment to be edited (because the audit tool can not read the history of edited comments) or the /autopay command to be rewritten (because it simply breaks the feature).

Another point not in favour of editing comments is that some of our tools (ex: https://pay.ubq.fi/audit) and features (the bot's /autopay command which toggles automatic payout for the issue it is used in) rely on a full issue's comment history. So we don't want a permit URL comment to be edited (because the audit tool can not read the history of edited comments) or the /autopay command to be rewritten (because it simply breaks the feature).

This is a valid problem scenario. Unforeseen edge cases with the order of bot comments can break the functionality of our other tooling.

Well thinking about just these points, it wouldn't be hard to check whether the bot's last comment contained any of the sensitive stuff we don't want changed and if it does then just post a new comment rather than replacing it?
Specifically those two points, "/autopay" and any comment with "content.body.includes("https://pay.ubq.fi?claim=" should be skipped over. I haven't looked at the /audit stuff in depth much yet to weigh in there.
Happy to hold fire, happy to get stuck in finding a solution but easy either way.

The audit app has similar logic. Basically it just parses GitHub comments from the bot, containing the pay.ubq.fi url.

Specifically those two points, "/autopay" and any comment with "content.body.includes("https://pay.ubq.fi?claim=" should be skipped over.

We can't cover all of the edge cases, something will definitely be missed. Again this brings us to unit testing because with a decent test coverage we could be sure (to some extent) that the "edit comments" feature doesn't break anything.

/stop

Closing this one because editing bot's comments breaks other bot's functionality


self.follow(self) causes unittest error

HI miguel,sorry to bother.
It's about a func in User.init to make users follow themselves,the codes in your book was like below,
self.follow(self)
but in your repository:
self.followed.append(Follow(followed=self))
And that in your book causes unittest error:
sqlalchemy.orm.exc.DetachedInstanceError: Parent instance <User at 0x7fb90d3e49b0> is not bound to a Session, and no contextual session is established; lazy load operation of attribute 'followed' cannot proceed
I don't understand what caused the error, how it affects the result of unittest, and what's the differences between the two above.
Hope u can reply this, thx

Do you have the complete stack trace of the error please?

Great. So you can see in the stack trace that the error occurs when you do self.followed.filter_by(...) in line 232 of models.py. This line instructs the database to do a join operation between two tables, to find if the user you want to follow was already added. The problem is that self isn't in the database yet, so it does not have an id assigned, which makes the join operation impossible.
The way I implemented that initial self follow is by just doing self.folllowed.append() which does not require any database joins or searches.
You could probably make self.follow(self) work in the constructor if you add a check to skip the is_following() check when the instance does not have an id still.

OK, I got it. I should concentrate more.
Thank u very much, and I'll close the issue.
By the way, in styles.css ,I think the 'post-content' should be replaced by 'post-body', and the 'post-author' should have a 'margin-left:48px'. Both in ur repository.


[loc][Query][VSCode] Please clarify string

Hi, we have a question from our translator. Can you help please? Thanks!
Source:
Format a file on save. A formatter must be available, the file must not be auto-saved, and editor must not be shutting down.
File Name:
src\vs\workbench\parts\files\browser\files.contribution.nls.resx
Resource ID:
".resx", 0; "formatOnSave"
Query:
Is "Format a file on save" a command/action or just a description to be understood as "It formats a file on save"? Thanks.	Zinacle	10/4/2016 11:22:15 AM

It formats a file on save

Yeah, like that


Support Web Bluetooth API

Is your feature request related to a problem? Please describe.
Websites which use the Web Bluetooth API do not work due to that API not being provided.
Describe the solution or the user experience you'd like
For websites using that API to work.
Additional context
Web Bluetooth API spec: https://webbluetoothcg.github.io/web-bluetooth/

Thanks, I see that is not supported by Android Webview according to the Docs.
Our browser is based on the Android Webview, so I'm not sure we can support it by ourselves. I still need to explore more on this (I've created an task in our backlog https://app.asana.com/0/0/1188018485640065/f ).
If anyone has more info about this, feel free to share it here. Thanks!

Closing this as WebView does not support according to Docs and I haven't found a way to support this in our browser.

Closing this as WebView does not support according to Docs and I haven't found a way to support this in our browser.

Don't get why this should be closed then if it isn't fixed? Doesn't this just hide the issues from others that are willing to look into it and are maybe able to find a solution?

Don't get why this should be closed then if it isn't fixed? Doesn't this just hide the issues from others that are willing to look into it and are maybe able to find a solution?

I've currently reviewing the status of our open issues. For this concrete one, I tried to find a solution without any luck.
Our browser is based on WebView, and if WebView does no support that bluetooth API, I'm pretty confident there's nothing else we can do here. I also noticed that the API is experimental, something that will add complexity to this task (validating that is safe and no security issues are introduced).
Without a valid approach, we can't triage or prioritize this request, and since I haven't seen any further activity here, I think is ok to close it for now.

I've currently reviewing the status of our open issues. For this concrete one, I tried to find a solution without any luck.
Our browser is based on WebView, and if WebView does no support that bluetooth API, I'm pretty confident there's nothing else we can do here. I also noticed that the API is experimental, something that will add complexity to this task (validating that is safe and no security issues are introduced).
Without a valid approach, we can't triage or prioritize this request, and since I haven't seen any further activity here, I think is ok to close it for now.

I just don't understand why issues that aren't resolved or otherwise invalid should be closed.
Other people might run into this API missing as well, not see an open one and just open a new one about the same issue instead of simply commenting on/subscribing to this one.
Also I think if this stays open it can be used to point the developers of WebView to it and to close once WebView implemented it (or someone found a workaround) and with that notify anyone who is interested in this same issue.

I just don't understand why issues that aren't resolved or otherwise invalid should be closed.
Other people might run into this API missing as well, not see an open one and just open a new one about the same issue instead of simply commenting on/subscribing to this one.
Also I think if this stays open it can be used to point the developers of WebView to it and to close once WebView implemented it (or someone found a workaround) and with that notify anyone who is interested in this same issue.


Add .md documentation to modules

Add README.md to modules and subfolder as documentation for each parts of the project. The README should have useful information about the code, the methodology, references in textbook, quick explanations and hints about Julia, etc. It should be written to make it easier to students to contribute to the project.


Boxes inside a sample group

Summary
Not so sure how to deal with this one in the framework but SVCDependencyRangeBox - svop is a box which is used inside a scif sample group. so the container can not be sgpd and so far we didn't cover the case where boxes are added inside a sample group.

Not sure if I understood correctly but I see couple of examples whose container is scif here. Can you elaborate on what is missing with the framework?

I didn't test it yet. but will it be possible to search for svdr (was called svop by mistake) for example? or will it be ignored because it is buried inside a sample group?

It will be possible to search for it because we are also looking for the grouping_type in sgpd.
https://github.com/MPEGGroup/FileFormatConformance/blob/598492c4aafa0c98dc1842b51686c8e5b2b81873/src/construct/files.py#L100-L102


[1.6.x] Add compatibility for Django 2.1

Drop use of procedural auth views that are removed in Django 2.1
Remove CommonPasswordValidator from test settings, as this catches some test passwords.

is there an ETA for this pr?


(feature): Horizontal delimiter

It would be nice if it were possible to have setting for horizontal delimiter(s) so we can split different sets of data.
Something like:
=====================
ID | Name  | Value  |
---|-------|--------|
 1 | Jack  | blue   |
 2 | Jack  | brown  |
---|-------|--------|
 3 | Alice | red    |
 4 | Alice | yellow |
=====================

For example do draw delimiter line if we pass a row with single value? Would be nice if different characters can be used: -, =, pseudo-graphic ASCII.
So probably a settings should be a slice of strings to be treated as delimiters.

Hey @astec, interesting idea. I could see potentially adding settings for a horizontal split line. I could also see drawing outlines for a nice table-looking output, but IMO that should be a separate wrapper over Columnize, or perhaps a separate wrapper within this package. I probably won't be tackling this myself any time soon, but I would love a PR!


Cache not caching on pull_request

Hi guys! How it's going? Hope you are doing well :)
Simply that, I test all the scenarios and I found that cache is caching only on push :/

Can you provide more details? Maybe a code snippet?
You may find your answer in here:
https://docs.github.com/en/actions/guides/caching-dependencies-to-speed-up-workflows#restrictions-for-accessing-a-cache

A workflow can access and restore a cache created in the current branch, the base branch (including base branches of forked repositories), or the default branch (usually main). For example, a cache created on the default branch would be accessible from any pull request.

Access restrictions provide cache isolation and security by creating a logical boundary between different branches. For example, a cache created for the branch feature-a (with the base main) would not be accessible to a pull request for the branch feature-b (with the base main).

@andrmoel thank you! So what do you think its a good approach for caching and save minutes on pull requests ci?
Now we cache on push to development branch but it takes a bit more than a minute to complete the cache when hits a preexistent cache :/

@ManuLpz4  a cache created on the default branch would be accessible from any pull request. What problems were you facing? Are you using a different branch other than the default branch against which PRs are raised? Can you put in more details?

Hello !
I think I've just hit the same issue, we run self-hosted runners, and I wanted to cache things between sequential jobs on a PR workflow (store the scan result, then use the result to process it later)
It seems that every time I tried storing/pulling the cache, I ended with Cache not found for input keys
Seems that the only viable solution is artifact upload/download ? There might be a shared filesystem alternative

Not allowing cache across PR branches is by design to not allow cache poisoning by a malicious PR. You can still use cache from base branch (or even the default branch) in the pull request branches.


whoisit does not find the RDAP endpoint for UK domains

Hello,
It seems that there is some issue with uk domains
>>> whoisit.domain("citizensadvice.org.uk")
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/home/fl/.local/lib/python3.9/site-packages/whoisit/__init__.py", line 46, in domain
    method, url, exact_match = build_query(
  File "/home/fl/.local/lib/python3.9/site-packages/whoisit/query.py", line 57, in build
    url, exact_match = fetcher(query_value)
  File "/home/fl/.local/lib/python3.9/site-packages/whoisit/query.py", line 95, in get_domain_endpoint
    endpoints, exact_match = self.bootstrap.get_dns_endpoints(tld)
  File "/home/fl/.local/lib/python3.9/site-packages/whoisit/bootstrap.py", line 319, in get_dns_endpoints
    raise UnsupportedError(f'TLD "{tld}" has no known RDAP endpoint '
whoisit.errors.UnsupportedError: TLD "uk" has no known RDAP endpoint and is unsupported

Yet, .uk tld has an RDAP endpoint: https://rdap.nominet.uk/uk/domain/citizensadvice.org.uk

Nominet's RDAP enpoint isn't currently listed by the IANA which is why .uk domains currently aren't supported by default. I've added the RDAP endpoint as an optional override in the 2.6.1 release I've just pushed.
You can enable overrides by bootstrapping with the overrides=True kwarg, e.g.:
whoisit.bootstrap(overrides=True)

The overrides are a set of manually specified RDAP endpoints which the IANA don't list at the moment. It's possible they also return non-standardised formatting for results as well so watch out for any weirdly parsed results if you enable them.
Update to 2.6.1 from PyPi and give it a go.

@meeb I wanted to thank you again for your time and effort maintaining this library -- very much appreciated!

It occurred to me that we could update the error message here, to make it a bit more user-friendly? e.g. mentioning the overrides=True instructions in the Readme. I'd be happy to make a PR for this, if you like the idea?

Not a bad idea @case, all good though I've just pushed a minor verbosity increase to the error message. I already had the edior open from the previous release. See: https://github.com/meeb/whoisit/commit/cda9a6f665b8d7b6ddf28e97273503012610afdf


Revert "RISC-V 3D Chip Design with TSV and Thermal Modeling"

Hello, I submitted a pull request a few weeks ago, but but I realized that I had omitted my mentor's name. Also, there is just one line changed in the .ipynb file that was wrongly copied and pasted. If possible, without violating any rules, I sincerely hope that the organizers would allow me to make the necessary corrections. I apologize for any inconvenience caused.

It seems your notebook was deleted for some reason. Can you send another PR?

It seems that I delete my notebook wrongly, so I have create another pull request (https://github.com/sscs-ose/sscs-ose-code-a-chip.github.io/pull/93#issue-2290996159). Thanks you very much~


Implement active-passive data sync

In #1210 we decided that a passive joining a cluster must be fully synced with all the key-value pairs in the active. So this task is to implement the same in the least disruptive manner. The active should not be fully blocked while the sync is being performed. Instead, the sync should be performed per concurrency key so that there's only concurrency key level blocking on the active.

Summarizing the points raised in discussion threads that happened elsewhere:
There is a limitation of syncing data during active-passive sync. It's because of the difference between no. of segments of ServerStore & DEFAULT_CONCURRENCY.
Right now all the operations, irrespective of being mutative or not are spread across the DEFAULT_CONCURRENCY i.e. 1024 keys across all caches.
The spread is defined by the hash of cacheId & key (mod 1024) calculated at client side. This results in calling syncToPassive on all concurrency keys. The problem is there is no way for entity to figure out, what all data is mapped to a particular concurrency key for which platform will try to sync.
The idea is to stick with the same spread for reads (including replace), but change the mutations spread to (no. of caches * segments = 16)%1024 (an additional factor can also be multiplied in future to reduce the sync time for a segment). In this way for the chosen sync keys, the Active entity exactly knows which segment to sync.
Note:- Both No of segments in ServerStore and DEFAULT_CONCURRENCY can be changed.
All this came up in discussion with @ljacomet , @albinsuresh , @itsroshan , @rkavanap & sairam

Adding to the design:

Read operations should use the UNIVERSAL_KEY as they have no ordering requirement
For write operations, we need to move to a scheme matching the segment of the underlying store.

For this second point, the following has been discussed and is the latest design:

When a new clustered tier is created, a reconfigure message will be sent to the entity with the added information for this new tier - offset and segments count.
** This means that the create operation must return this information, so that the client can then invoke reconfigure
** This also means that the configuration object which is currently limited to a UUID needs to be expanded to carry that information.
Once reconfigure is called, this causes the entity and ConcurrencyStrategy to be recreated based on that new information
With the information, the ConcurrencyStrategy will have to use the same hash and bucketing algorithm as the matching store to determine the proper concurrency key.

For example, with store foo and bar, assuming 16 segments like right now, we would have the following spaces:

foo from 2 to 17 (so offset is 2, key space is 16)
bar from 18 to 33 (so offset is 18, key space is 16)


Dapr swallows method invocation messages if the verb is unknown

In what area(s)?
/area runtime
What version of Dapr?
0.4
Expected Behavior
Dapr should return an error if the verb is invalid instead.
Actual Behavior
If the verb is not in the set of 4 we support, dapr does not forward the message to the target. It also does not return an error to the client, so will seem to the client that it succeeded. The examples below are for a grpc client sending to an http app.
This works:
m.Add("http.verb", "PUT");
string s = await daprClient.InvokeMethodAsync<MyData, string>("nodeapp", "hello", data, m);
This does not (lower-case put):
This does not:
m.Add("http.verb", "CAT");
string s = await daprClient.InvokeMethodAsync<MyData, string>("nodeapp", "hello", data, m);

@LMWF Is this fixed? Can you comment?

This isn't fixed, the first linked PR fixes only a subset of this (verb casing).

After refactoring service invocation building block, this is no longer the issue.
@LMWF


Move to sync.RWMutex

If we move to sync.RWMutex then we can use a RLock() when constructing the topic list for external callers.
Alex

cc @tessellator


fix: return empty list when querying for project deployments

Description of change
This fixes get_deployments function, so that it retuns empty list instead of error if there are no deployments associated with the project yet.
How has this been tested? (if applicable)
Tested in local development -> Console and Postman.

The CLI likely needs an update to show "no deployments found" instead of an empty table


Declare more types (add local mypy target), block pylint>=2

Pull Request Test Coverage Report for Build 157

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 155:
0.0%

Covered Lines:
947

Relevant Lines:
947

💛  - Coveralls

Pull Request Test Coverage Report for Build 157

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 155:
0.0%

Covered Lines:
947

Relevant Lines:
947

💛  - Coveralls

Pull Request Test Coverage Report for Build 157

2 of 2 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 155:
0.0%

Covered Lines:
947

Relevant Lines:
947

💛  - Coveralls


chore: add license file

Codecov Report

Merging #3 (c24c82f) into main (dfa13d2) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #3   +/-   ##
=======================================
  Coverage   98.87%   98.87%
=======================================
  Files           1        1
  Lines          89       89
=======================================
  Hits           88       88
  Misses          1        1

:mega: Codecov can now indicate which changes are the most critical in Pull Requests. Learn more


[TPC-H] Move Dask queries to their own file

This PR refactors the TPC-H tests so that we have functions that provide us with the queries in another file.
This is 99.9% verbatim copy+paste, I don't touch the queries themselves.

This is a step toward #1325


(BSO) Fixed a =ping typo

ping cmd was saying to use ‘+role name’ to add/remove rather than ‘=roles name’
Changed on BSO as OSB has no +roles yet, not sure if this will need changing again in the future if OSB code needs updating to follow suit

thanks codecov 👍🏻


Fix version in configuration error messages

What kind of change does this PR introduce?
bugfix
Did you add tests for your changes?
I've edited existing test.
If relevant, link to documentation update:
N/A
Summary
Version in message was hardcoded, I replaced it with the one present in package.json.
Fixes #6605
Does this PR introduce a breaking change?
No
Other information
Disable prettier on those lines because introduce like break around variable. See:
https://github.com/prettier/prettier/issues/1893
https://github.com/prettier/prettier/issues/3368

Thanks


How to request https via proxy?

This is my script:
request := gorequest.New().Proxy("https://<proxy-ip>:443")
resp, body, errs := request.Get("https://<host>").End()

fmt.Println(resp, body, errs)

I get "Bad Request" always. Anybody can share script to request https via proxy GET ot HEAD?
Proxy is reverse-proxy

Try "http://:443", not https. Sometimes it works


Update identity-management.md

I think we should default to the quickstart settings rather than making the user edit this every time. And I'm tired of modifying this every time I setup a quickstart... ;)


Is There a Way to Change DPI and HDR Status on Streaming?

Some of my devices do not support HDR and some of them are too small in screen size. So is there any method to change the DPI
and HDR on/off?

https://github.com/Nonary/AutoHDRSwitch
As for DPI, no there isn't a publicly exposed API that allows you to change the DPI. Microsoft wants developers to set DPI per application, even though literally zero applications do that.


what do you mean by wrapping?

can you please explained what do you mean by wrapping when you use feature wrapping?

I don't know either. Do you understand the meaning of bilinear op by now?


USING LIBRARY WITH NEW PAGING LIBRARY FROM ARCHITECTURE COMPONENTS OR WITH DIFFUTILS

Hello @zhukic,
Great library, I love using it. I am trying to implement an app that uses this library for a sectioned list of notifications. I would love to use it with the PagedListAdapter from android architecture components but I think that's a tall order. So is there a way I can at least use the library with DiffUtils?
Regards,
Mujib.

Hi @aliumujib.
Sorry for late reply. Currently there is no possibility to use this library in conjunction with DiffUtil because default DiffUtil implementation calls notifyItemRangeInserted, notifyItemRangeRemoved, notifyItemRangeChanged methods which current library doesn't yet support. This feature will be added in the next releases.

This feature would be helpful, in order not to create a new SectionedListAdapter instance each time I want to insert new data in it.

Hi, @hivian.
Currently, I'm not planning to add Paging Library in the nearest future. Sorry for that.


chore: update log level for mprocs

Using the unknown module in mprocs will cause warning logs which can be unsettling for users. This change updates RUST_LOG for fedimint-cli, which suppresses these warning.
See: discord
bash-5.2$ fedimint-cli info
2024-03-01T20:31:51.184211Z  WARN fedimint_client: Detected configuration for unsupported module id: 3, kind: unknown
2024-03-01T20:31:51.186137Z  WARN fedimint_client: Module kind unknown of instance 3 not found in module gens, skipping
{
...

Maybe we should change the logging level then. Same unsettling logs will be visible to normal users.

Part of they point of having it in mprocs is making sure the ux is right as well.

Maybe instead of this we should info! a summary of supported, unsupported etc.

Maybe we should change the logging level then. Same unsettling logs will be visible to normal users.

I'm interpreting normal users to mean users in production instead of mprocs. In that env, I think keeping the warning logs is the correct UX.

Maybe instead of this we should info! a summary of supported, unsupported etc.

Each time I invoke a fedimint-cli command, I would be annoyed with a summary of supported and unsupported modules, but I would like to know a warning that the federation I'm connected to has a module my client doesn't support.
I'm not sure if we anticipate it's common for clients to connect to federations that have unsupported modules. If so, we should probably chew on a better way to surface that to users.

Alternatively we could just change RUST_LOG in mprocs. But Federations that have unsupported modules might not be something special and unusual in real use. If what user is doing is unrelated is there really a point earning them about anything?

I like the approach of updating RUST_LOG. WARN seems like the correct log level but there's no need for the user to see that as part of the output when interacting with mprocs.

It should be a debug log and we could show this as warning on fedimint-cli info

So I guess we're not doing it and went with a different approach (change offending line to debug!).

So I guess we're not doing it and went with a different approach (change offending line to debug!).

I think that's the right way to go, but it's still a TODO, right? At least I found a bunch of places that use the exact wording "Detected configuration for unsupported module".


Initial support for Vue 3.

This pull request is backwards compatible and can be published as 1.9.0. Resolves #51

One question, will vue-cli-plugin-single-spa also need to be updated to detect which version of Vue was used and modify the template accordingly?

Not from what I've seen. I created https://github.com/joeldenning/vue-3-single-spa by doing vue create and then vue add single-spa and the cli plugin worked without issue. I did create https://github.com/single-spa/vue-cli-plugin-single-spa/issues/15 to track a change we need to make so that the main.js file is automatically configured correctly based on the Vue version

Ok cool. The reason I ask is because of import * as Vue from 'vue' (this line from the demo repo you put together) and I thought Vue had removed a default export so import Vue from 'vue' (which is generated in the main.js file from the cli plugin) wouldn't work. That'll been tested/solved in the plugin code anyway. I unfortunately don't have time to test these all right now but this code looks good to me!

I thought Vue had removed a default export

Yes this is true. vue add single-spa doesn't throw an error, but it does create a main.js file that doesn't work with Vue 3. I had to modify the main.js to get that example working. Once we fix https://github.com/single-spa/vue-cli-plugin-single-spa/issues/15, it will all work though


How to notify clients outside of a hub context (documented way does not work)

Hi,
I am trying to notify my clients as documented on several places (e.g. https://docs.microsoft.com/de-de/aspnet/core/signalr/hubcontext?view=aspnetcore-2.1 topic: "Get an instance of IHubContext in middleware") outside of a hub object (no previous call from a client). There is no website within the actual project so there is no "Controller" class where IHubContext can be injected via DI.
How do I get an IHubContext object to notify my clients? The documented version does not even compile!
Startup.cs class, method "public void Configure(IApplicationBuilder app, IHostingEnvironment env)":
app.Use(next => (context) =>
            {
                var hubContext = (IHubContext<NotificationHub>)context
                    .RequestServices
                    .GetServices<IHubContext<NotificationHub>>();
                //...
            });

causes:
Startup.cs(58,39,58,41): error CS1643: Not all code paths return a value in lambda expression of type 'RequestDelegate'
Startup.cs(58,29,58,41): error CS1662: Cannot convert lambda expression to intended delegate type because some of the return types in the block are not implicitly convertible to the delegate return type

The delegate type has a completely different layout: returning Task and consuming HttpContext object.
So I tried to change the signature to this resulting code (I am using two hubs):
app.UseSignalR(routes =>
            {
                routes.MapHub<CommandOutputHub>("/CommandOutputHub");
                routes.MapHub<NotificationHub>("/NotificationHub");
            });

app.Use(next => (context) =>
            {
                NotificationHubContext = (IHubContext<NotificationHub>)context
                    .RequestServices
                    .GetServices<IHubContext<NotificationHub>>().First();

                return Task.CompletedTask;
                //...
            });

But the lambda becomes never called. Even when I exchange the "null" task with a valid one, this task becomes never executed.
Can anyone provide a complete sample, how notification of clients can be done from outside a Hub object without using a Controller class?
Server-Side:
Microsoft.AspNetCore.App 2.1.1 incl. Microsoft.AspNetCore.SignalR (1.0.1) (.NET console app or service hosted on IIS Express, C# .NET Core 2.1, Win 10 Pro OS)
Client:
Microsoft.AspNetCore.SignalR.Client 1.0.3 (.NET console app, C# .NET Core 2.1, Win 10 Pro OS)

There's a sample referenced right at the top of the doc you linked: https://github.com/aspnet/Docs/tree/master/aspnetcore/signalr/hubcontext/sample/

Startup.cs(58,39,58,41): error CS1643: Not all code paths return a value in lambda expression of type 'RequestDelegate'
Startup.cs(58,29,58,41): error CS1662: Cannot convert lambda expression to intended delegate type because some of the return types in the block are not implicitly convertible to the delegate return type

These are compilation errors, likely because you didn't use the async keyword in the delegate. The docs are missing that though, so I submitted https://github.com/aspnet/Docs/pull/8480 to fix that. Sorry about that!

Hi, thank you for your fast response! The sample you referenced is not what I am looking for (as described, I do not have a website on this "site", so there is no Controller here anywhere!). And as I already mentioned too, I got the code compiling but the lambda (RequestDelegate) is never called. I need a working notification from "middleware" code: clients simply connect to the "NotificationHub" and become notified after a certain time from the server - how to achieve this? A sample would be really awesome!

Hi again, I found a working solution on Stack Overflow(https://stackoverflow.com/a/38832879):
Adding a IServiceProvider object to the argument list of the Configure method (for me still magic this auto DI). Then calling GetService<IHubContext>() on this object returns the HubContext reference I needed. If there is a more fancy way to do this then please add it to the documentation too else maybe provide this working solution.
Best,
Michael

Yes, you need to get IHubContext out of DI. So if you don't use Controllers, then you need to access it in some other way. If you can provide a more detailed explanation of how you need to access the IHubContext we can look at trying to provide better documentation here.

I need a working notification from "middleware" code

If the above code wasn't working for middleware, can you post a complete sample that reproduces the error? That's definitely a scenario we've tested. Middleware should be called for each incoming request, so if your registered middleware isn't being called it could be because a middleware higher up the chain is being called.

NotificationHubContext = (IHubContext<NotificationHub>)context
    .RequestServices
    .GetServices<IHubContext<NotificationHub>>().First();

This code is very odd. You're taking the HubContext from a single request and storing it somewhere. Middleware is called for each individual request, so I'm not sure I understand what you're trying to achieve. If you want to trigger notifications from a background service, you not be using middleware for that as middleware is for request handling, not for background services. If you are using a background service you should use an IHostedService which is DI-activated, so you can have IHubContext<NotificationHub> in your constructor and use it freely there.


application.php throwing parse error

I was sorting out a new capstrano deploy of a WP site with bedrock and it kept giving me a php parse error.
I tacked down to line #13 of application.php
$dotenv->required(['DB_NAME', 'DB_USER', 'DB_PASSWORD', 'WP_HOME', 'WP_SITEURL']);
Specific error :
Parse error: syntax error, unexpected '[', expecting ')' in /config/application.php on line 13
fixed this by removing the [] from the line.
Is this because the sever is not running a high enough version of php (server = 5.3.9) ?

@kiwiot Yes. You need to be running a newer version of PHP.
http://php.net/manual/en/language.types.array.php

Thanks for the quick reply


Rename project as QXGraphs

Summary
The name QXGraph was updated to QXGraphs in all files and the Project.toml file was updated to include Julia 1.6 as a compatible version.
Rationale
The name needed to be updated in order to automatically register the package as a Julia package.
Implementation Details
Additional notes

Check before merging:

[ ] All discussions are resolved
[ ] New code is covered by appropriate tests
[ ] Tests are passing locally and on CI
[ ] The documentation is consistent with changes
[ ] Any code that was copied from other sources has the paper/url in a comment and is compatible with the MIT licence
[ ] Notebooks/examples not covered by unittests have been tested and updated as required
[ ] The feature branch is up-to-date with the master branch (rebase if behind)
[ ] Incremented the version string in Project.toml file

Codecov Report

Merging #2 (8dae63f) into master (6ce0f53) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master       #2   +/-   ##
=======================================
  Coverage   87.21%   87.21%
=======================================
  Files           3        3
  Lines         219      219
=======================================
  Hits          191      191
  Misses         28       28

Impacted Files
Coverage Δ

src/QXGraphs.jl
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Home file improvements

Replace option mode with option executable (Commit)
We could maintain backwards compatibility by translating the chmod directive of
mode to the boolean value executable. But this either needs a very complex direct
implementation or an ugly hack (write file to nix-store with mode and read back
the executable bit). So I'd suggest a breaking change.
Link home files
I had an issue with large home files that caused bloated home-manager-files.
Commit link home files instead of copying fixes this.
The commit is straightforward but it inherits some other problems of the original code:

Files with a non-matching execute bit are still needessly copied for each new generation.
Solution: For each file with an external source, make a wrapper derivation that copies on
demand or otherwise just creates a link.
After garbage collection, all home file derivations get deleted from the store and must be re-built when
creating a new generation. This can also lead to multiple copies of identical home
files among different generations.
Solution: Use symlinks instead of hardlinks in home-manager-files, so that Nix can
recognize the linked files as store dependencies.
This has the downside that each home file needs a chain of two symlinks to
point from $HOME to its final store location.

I've implemented both solutions here.
Note that for home files text now takes precedence over the source option.
The symlink chain issue can be fixed, too:
Give all home file derivations the same unique name that makes them identifiable as
home files and link to them directly from $HOME.
That's the approach that I would recommend and that I'm using in my fork. Here's the implementation.
Downside: To make this backwards compatible, the old -home-manager-files/ pattern
must also be considered when detecting home files: Implementation, full commit.
Here's a config for experimenting:
cat << EOF > homeFiles
{ pkgs, ... }:
let
  nonExecutableFile = pkgs.writeText "a" "a";
  executableFile = pkgs.writeScript "a" "a";
in
  {
    home.file."basic_file" = { text = "a"; };

    home.file."test/my/nested/file" = { text = "a"; };
    home.file."test/spēcïal chârs" = { text = "a"; };

    home.file."test/noexec" = { text = "a"; };
    home.file."test/exec" = { text = "a"; executable = true; };

    home.file."test/noexecSrcExec" = { source = executableFile; };
    home.file."test/noexecSrcNoExec" = { source = nonExecutableFile; };

    home.file."test/execSrcExec" = { source = executableFile; executable = true; };
    home.file."test/execSrcNoExec" = { source = nonExecutableFile; executable = true; };

    # home.file."test/dir" = { source = ~/my_dir; };
  }
EOF
home-manager -f homeFiles switch

Used the wrong branch as the PR source.


Travis CI pipeline

This enables the travis-ci pipeline for OSX and Linux.  See here for how it works.
I added Cargo.lock to be versioned per recommendation by @dhuseby.
The rest of the changes are just rustfmt and cargo clippy fixes.
The support desk will need to enable the travis-ci webhook for ursa to turn this on.

@dhuseby can you clarify the cargo.lock recommendation?

There were two reasons I remember. First, was dependency versioning and two so cargo audit could run. @dhuseby were there other reasons why?

@dhuseby can you clarify the cargo.lock recommendation?

There were two reasons I remember. First, was dependency versioning and two so cargo audit could run. @dhuseby were there other reasons why?

This rust FAQ indicates cargo.lock should not be committed for library code:
https://doc.rust-lang.org/cargo/faq.html#why-do-binaries-have-cargolock-in-version-control-but-not-libraries
I'm good either way, but if it's committed it will be helpful to put the rationale in the commit message.

@dhuseby can you clarify the cargo.lock recommendation?

The idea of checking in the cargo.lock file is for reproducible/deterministic builds. We want to track the contents of that over time so that we know exactly what dependencies were used to support specific builds of Ursa.


Extension page bugs

Cannot save after clicking clear
Probably due to no targets existing after clearing.
After clicking save, all split numbers are zeroed out. The API also gets sent tag: null instead of an empty string which also causes errors.
If a tagged payment is processed, it still tries splitting. It should either split or process the tagged payment.

Some other things:

What's the extra.amount check for?
Tagged payments are confusing: they check for a specific field key existing. extra.tag or extra.target may want to be used instead.

@Semisol new release should solve you issues? can you verify?

Deleting the last target, from the delete icon to the right, disables the save button, so I'm not allowed to save the change. Delete all targets works as expected though.


🆙 update packages and tests

Description

Updated composer.json so it is compatible when upgrading to Laravel 10
updated code so tests are 100% passing

@grg021 thx for this. just wondering, did you use any tools for this?

@grg021 thx for this. just wondering, did you use any tools for this?

used this tool called rector https://github.com/rectorphp/rector
other changes are done manually


Error while reading bundle file - System.IO.IOException: Lz4 decompression error, write -1 bytes but expected 131072 bytes

Game: Rise of Kingdoms
Build: Unity 2021.3.21f1
File: ui_texture_commander.lb _(Applies to all .lb UnityFS Bundle files for Rise of Kingdoms)
Error:
Error while reading bundle file C:\Users\MGS\Desktop\RoK\ui_texture_commander.lb

System.IO.IOException: Lz4 decompression error, write -1 bytes but expected 131072 bytes

   at AssetStudio.BundleFile.ReadBlocks(EndianBinaryReader reader, Stream blocksStream) in D:\a\AssetStudio\AssetStudio\AssetStudio\BundleFile.cs:line 351

   at AssetStudio.BundleFile..ctor(FileReader reader) in D:\a\AssetStudio\AssetStudio\AssetStudio\BundleFile.cs:line 98

   at AssetStudio.AssetsManager.LoadBundleFile(FileReader reader, String originalPath) in D:\a\AssetStudio\AssetStudio\AssetStudio\AssetsManager.cs:line 182

Issue reference from original 2022 build: https://github.com/Perfare/AssetStudio/issues/971#issue-1226264525

Solution: Delete all bit entries from the first "UnityFS" specification to the next "UnityFS" specification.
Originally posted by @p0pZeroSn in https://github.com/Perfare/AssetStudio/issues/971#issuecomment-1119429868

Other user who had trouble with solution:

Hey bro, after I follow what you said, it prompts that the dimension of the array is exceeded. Do you know why?
Originally posted by @PackageInstaller in https://github.com/Perfare/AssetStudio/issues/971#issuecomment-1120222134

If this specific niche use-case doesn't warrant a special fix, could there be any more specific explanation on how to execute @p0pZeroSn's alleged fix? Even if I delete everything from and to the first and second UnityFS declarations/headers/whatever, it still doesn't function.

Partial fix, full fix for most files:

Okay, found an actual partial fix, specifically for the files which contain "UnityFS" twice. Some of the files will still have very few assets which will fail, but the fix is as simple as CTRL+F to the second "UnityFS" entry and deleting everything before that.
This way, your edited file should now begin with the second UnityFS entry.
Result:

try using fake header as game


Collaborator request

I would like collaborator (write) access to this repository, so I can contribute
to the Auditree Arboretum library.

[x] I have read the contributing guidelines

Sorry @Parthakumar-Roy, clearly we need to update our CONTRIBUTING.md.  In PR #30 now.  See: https://github.com/ComplianceAsCode/auditree-arboretum/blob/058afc9ce2abef7359cf91cb293edaa911bf6293/CONTRIBUTING.md
For now just fork the repo and submit PR that way.  Thanks.


Fix hung threads and missing text due to long replies, and other minor fixes

This PR contains the following fixes/updates:

Strip JSON syntax tags
For threads that exceed 4096 tokens, remove old assistant message as well as user messages
Use different warning message when error occurs when replying to a thread vs starting a new one
Fix metadata_too_large warning from causing a thread to hang if the first bot reply in a thread is too long
Fix missing text when asking the bot to continue a long response after a msg_too_long error

These last two issues are closely related, and occur due to trying to store the entire conversation so far in the metadata for each bot reply. When the metadata becomes too large, it is ignored when written to subsequent messages, and reply_if_necessary will read the later messages from the Slack text rather than the metadata. This approach works well in most cases, but there are two situations where it doesn't, and these happen when we run into Slack metadata or text length limitations before reaching the OpenAI output token limit.
If the first bot response in a thread exceeds the maximum metadata size (4000 bytes), the metadata will never be written to the thread and the bot will never reply in that thread again, since the chat-gpt-convo event type is never written.
Before this PR:
user: Write a 60-step tutorial on how to bake a cake.
ChatGPT: 1. blah
         2. blah
         ...
         42. blah
user: continue
no response from bot

The second issue is difficult to reliably reproduce, but occurs when asking the bot to continue a long output (more than about 3800 characters, but less than the metadata size limit of 4000 bytes) that triggers a msg_too_long error. In this case Slack truncates the message text. When asked to continue, the bot reply will appear to be missing some text, due to the metadata being read instead of the shorter message text displayed in the previous message.
Before this PR:
... other short messages in thread
user: Write a 60-step tutorial on how to bake a cake.
ChatGPT: 1. blah
         2. blah
         ...
         42. blah
user: continue
ChatGPT: 48. blah
         49. blah
         ...
         60. blah

The fix contained in this PR is simply to not store the user/assistant messages in the metadata, and always retrieve these from the Slack message text. The metadata now only contains the system message and the event type.
After this PR:
user: Write a 60-step tutorial on how to bake a cake.
ChatGPT: 1. blah
         2. blah
         ...
         42. blah
user: continue
ChatGPT: 43. blah
         ...
         60. blah

@c-renton Thanks for the PR and all look great to me. It was a coincidence that I was working on the code today and my PR #18 brings many changes to the project structure. Would you mind merging your changes to the latest revision? With that, I am happy to have your changes here.

@c-renton Thanks for quickly rebasing the code! Now I can merge your great improvements here!