Force Visualization

🎉 New feature
Supersedes #1184.
Targets base branch main as there is a new method in Link.h.
Summary
This updates the previous PR #1184 and resolves some of the issues with that PR outlined in https://github.com/gazebosim/gz-sim/pull/1184#issuecomment-1429401235.
There are still a number of tasks to complete:
Tasks for this PR

[x] Complete the RemoveArrow function to remove up visuals when required.
[ ] Add support for throttling the publication of the EntityWrench components from Link.
[ ] The Qt GUI element is not synching correctly the first time the forces are displayed.
[ ] The visible flag is not working.

Tasks for follow up PR(s)

[ ] The colour applies to all force visuals - should be applied individually.
[ ] The arrow heads are hidden as they are not scaled correctly.
[ ] There should be a visual to display the torque (the rotation element of arrow, scaled correctly?).
[ ] Add text perhaps? (like Gazebo Classic).

Test it
The lift-drag example has been modified to help with testing. From the workspace folder run:
gz sim -v4 -r --gui-config ./src/gz-sim/examples/worlds/lift_drag.config ./src/gz-sim/examples/worlds/lift_drag.sdf

In another terminal set the rotor velocity:
gz topic -t "/model/lift_drag_demo_model/joint/rod_1_joint/cmd_vel" -m gz.msgs.Double -p "data: 430.0"

Checklist

[x] Signed all commits for DCO
[ ] Added tests
[ ] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[ ] codecheck passed (See contributing)
[ ] All tests passed (See test coverage)
[ ] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

Hmmm the rebase didnt work as expected :skull:. Going to be very hard for reviewers to review. I think cherry-picking would be an alternative.

https://github.com/arjo129/gz-sim
I don't use this fork anymore.
There should be a visual to display the torque (the rotation element of arrow, scaled correctly?).
Can be a seperate PR.

The rebase looks terrible because the target branch for the original PR is about 2y old. I rebased my fork of that on gz-sim7 first then made changes. If you were to rebase the original PR it looks a lot better. Or I could make this PR target main? It depends on how you’d like to keep the history. I’ll prob squash most of my changes into one or two commits. Could do the same for your original  history which would clean things up?

Updated to fix an issue where only one force per entity was visible. Link publishes a component that maintains a std::unordered_map of wrenches keyed by the force label. The original version used a message containing a vector of wrenches with each new force being pushed into the vector if the component was available. The problem was that it was not clear which agent would clear the vector, so it continued to fill without bound. Using a map ensures that the component holds only the number of forces applied to each link. The GUI extracts all the forces and queues them for processing in the render loop.
There are now methods to remove visuals and clean them when the GUI plugin unloads. Example usage with multiple forces applied to the MBARI buoy:

@arjo129 - this might be working well enough for a first version? Could target either main or gz-sim7 depending on whether the changes to Link and the addition of the component are considered ABI breaking or not.
Some questions:

Should the the system plugins specify whether or not to show visuals (like sensors)? I'd say yes because it will be more efficient, but requires a new field for all system plugins that apply forces.
How to apply a throttle - the wrench function in Link doesn't have gz::sim::UpdateInfo as an argument so any sim time based rate control would need to be in each system plugin. Or, you could put a counter and publish every n-th sample (rather than use a duration). I don't have a strong view either way - perhaps follow the approach used in sensors?
We might want to scale the forces from different system plugins differently. For instance buoyancy can have large forces compared to hydrodynamic drag - scaling all forces equally means that the detail may be lost. Perhaps a GUI configurable for a second round?
There's a few things to do in the GUI, such as make the colors and visibility tags active. Even without these the plugin is useful as is.

That's awesome I'll review it tomorrow. Will cherry pick the commits onto a new branch fi you don't mind.

How to apply a throttle - the wrench function in Link doesn't have gz::sim::UpdateInfo as an argument so any sim time based rate control would need to be in each system plugin. Or, you could put a counter and publish every n-th sample (rather than use a duration). I don't have a strong view either way - perhaps follow the approach used in sensors?

Seems reasonable to follow sensors.

Will cherry pick the commits onto a new branch fi you don't mind

Sure - no prob. I also have a branch based against gz-sim7 as well here (https://github.com/srmainwaring/gz-sim/tree/srmainwaring/7/forceviz) if that helps. Both build on your original PR (but rebased).

Seems reasonable to follow sensors.

I'll look at the approach used - it will probably mean additions to the SDF for force providing system plugins. Adding a function to toggle publishing the wrench component in Link and some boiler plate to activate / deactivate that based on the duration since last publish in the system plugins should work.

I think it'd be great if you opened the PR using the rebased branch.
On Mon, Feb 20, 2023, 5:42 PM Rhys Mainwaring @.***>
wrote:

Will cherry pick the commits onto a new branch fi you don't mind
Sure - no prob. I also have a branch based against gz-sim7 as well here (
https://github.com/srmainwaring/gz-sim/tree/srmainwaring/7/forceviz) if
that helps. Both build on your original PR (but rebased).
Seems reasonable to follow sensors.
I'll look at the approach used - it will probably mean additions to the
SDF for force providing system plugins. Adding a function to toggle
publishing the wrench component in Link and some boiler plate to activate /
deactivate that based on the duration since last publish in the system
plugins should work.
—
Reply to this email directly, view it on GitHub
https://github.com/gazebosim/gz-sim/pull/1898#issuecomment-1436639608,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEEMQB6GBELG4OJ7D6GC2LWYM4BPANCNFSM6AAAAAAU5K6TDM
.
You are receiving this because you were mentioned.Message ID:
@.***>

I think it'd be great if you opened the PR using the rebased branch.

Actually this PR already uses the rebased branch (targeting main). I can also target gz-sim7 if you prefer.

Noticed a bug: if there are multiple instances of a plugin generating forces for the same same link, then only one will contribution will be picked up. Example: lift-drag plugin for the iris quadcopter where two instances of the LiftDrag system generate forces for the same link.

@arjo129 changed the base branch from main to gz-sim7 [31 minutes ago]

I'll update the branch on my side to be based in gz-sim7 also. Does this mean there are no ABI issues with these changes?

My understanding is that there are no breaking abi changes. IIRC Adding a member function should not lead to ABI incompatibilities. Same applies for components. We have added components in minor releases in the past (not ideal). Ideally we would target main given that we may want to go back and break the ABI, but given the way git and github work it would have been impossible to determine the changes for reviewers on the PR without cherry picking commits.

No it would have been fine. I'd just rebase the entire history starting with your changes on main and force push. In any case either main or gz-sim7 works for me. The latter is a little more convenient as harmonic is still WIP as far as deps are concerned so its a bit more work to get a source build on macOS.
The issues with updates from the ECM are proving very confusing. The current version is broken, I fixed one thing (multiple forces for one entity), but seem to have broken the updates that were working when I was using a simple message as the component payload. It will take a bit more digging to figure out why the GUI is getting the updates but not finding them in the templated Each loop. I'm looking at VisualizationCapabilities which seems to be the GUI plugin closest to what we need for force visualization - but can't see anything obvious yet.
I'll push the debug code for the component serializer / deserializer (commented out) so you can see what I mean. I find it helps to set the RTF very low (RTF = 0.01 or less) when debugging to avoid getting swamped with messages.

Perhaps we should provide an option within sdf of liftdrag, buoyancy and hydrodynamics to specify<force_debug_namespace>?

Yeah that might work - it's not super urgent as you can introduce another link (this is what the lift_drag example does which is why I didn't spot it initially).
The biggest issue is the broken update - which I thought I had solved, but managed to break again. That's a blocker for this at the moment.

I can't think of a way to solve this without massive changes in other places. Perhaps we should provide an option within sdf of liftdrag, buoyancy and hydrodynamics to specify<force_debug_namespace>?

Here's an approach along those lines that might work: https://github.com/srmainwaring/gz-sim/commit/d192a4386518da66ad2fadb54a1ad48fe5b764a0.
I've also added throttling to the LiftDrag plugin on the publication side to reduce bandwidth usage.
Figure: force visualization with namespaces applied to SkyCat TVBS where each prop has two force contributions and all other lift elements are associated with the base link.

Probably for a follow-up PR, but I think it might be useful to move the force publication out of the Link:

Create standalone class to manage publishing entity forces for visualization.
May want to see the force - torque at the point of application rather than at the origin of the link frame.
Optionally publish messages to a topic for analysis in external tools.
A separate class could process the additional SDF elements (under a  element) to reduce copying boilerplate to each system plugin.

As a tool this is quite useful already. I have been trying to get a stable version of a 6DoF omnicopter running in Gazebo: https://github.com/srmainwaring/SITL_Models/blob/ignition/omnicopter/Gazebo/docs/Omnicopter.md
and I'm finding the tune very difficult. I have suspected that using the LiftDrag plugin for props causes a lot of noise - and the visualization appears to support this. Having the data published for plotting in an external tool would help complete the analysis.

@arjo129 this branch shows how we could move the force publishing out of the Link class in a follow up PR. It adds some features that are hard to deal with in the current version.

Add throttle when publishing forces.
Publish to a topic as well, for external analysis.
Add time stamps to the messages.
Remove messages from the map that are out of date (so all the forces published are for the same time step).

I've made the changes in the LiftDrag plugin, adding a ForcePublisher class which would be moved to it's own file if we wanted to proceed.

Interesting. One alternative would be to have the forcedrag plugin handle the publication as opposed to a force publisher. That would remove the need for additional API
I guess there are pros and cons to each method.

I think this is just blocked by an msgs release? If so, I  can do a gz-msgs9 release

@osrf-jenkins run tests please

@srmainwaring Have you had a chance to take a look at the feedback?

Have you had a chance to take a look at the feedback?

On my todo list. Apologies for the delay, I'll try to incorporate the changes in the next few days.

#2051 Has a nice visual. I wonder if we should extract the visualization component from it out else where.

can you fix the conflicts ? are you planning to finish this PR @srmainwaring ?

Hi @ahcorde - this dropped down the list for a while - let me review what's needed to get it ready. It may not be in this branch, but I had a more general way of enabling / disabling the force visualisation that wasn't so intrusive when not required. The visuals from the apply force plugin look good, so I'll look at what's involved in adopting those while I'm at it.

@srmainwaring do we need to close this PR and create a new one for the other approach you mentioned?

Is there any update here? I was thinking about visualizing forces in RViz, if this is ready I would prefer using this feature.

You could cherry pick this branch. I don't think this will make it into the next release.


feat: move region level config to env files AB#4349

Do you have access to the test-vm already? The .env-file there also needs to be updated with these changes, so it continues to work there...

@gulfaraz Nevermind, I've changed the .env-file already. So when this is merged it will be used immediately.


refactor(@angular/build): move getDepOptimizationConfig into utils file

Reduce the amount of code in vite-server.ts

The changes were merged into the following branches: main, 19.0.x


Support custom objectives and optimizers

Support custom objectives and optimizers by adding custom_objects to optimizers.get and objectives.get

Can you do a simple example or use case about that feature?

Sure. I use the following for quantile regression. y_true holds the np.vstack([y] * nb_samples).T
def batch_q_loss(y_true, y_pred):
import theano.tensor as T
quantiles=np.arange(0.05, 1., 0.05)
diff = y_true - y_pred
return T.mean(0.5 * (2 * quantiles - 1) * diff + 0.5 * abs(diff))

Just to understand what is the problem in plugging that in place of the loss during compilation?
model.compile(loss= batch_q_loss, optimizer='sgd')

This will not work when serializing the model.
compiled is called there without the user's intervention, and tries to
recreate the loss function.
On Tue, Nov 17, 2015 at 12:05 PM, Daniele Bonadiman <
<EMAIL_ADDRESS>wrote:

Just to understand what is the problem in plugging that in place of the
loss during compilation?
model.compile(loss= batch_q_loss, optimizer='sgd')
—
Reply to this email directly or view it on GitHub
https://github.com/fchollet/keras/pull/1025#issuecomment-157325710.

custom objectives (optimizers) are already supported, you just have to write you own function (class) and pass them as parameters to compile

Custom objectives are not supported.
Check the following unit test, which throws an exception on the current code:
from keras.models import Sequential, model_from_json
from keras.layers.core import Dense
from keras.optimizers import SGD

def my_mse(y, pred):
    import theano.tensor as T
    return T.mean((y - pred) ** 2)

def create_model():
    model = Sequential()
    model.add(Dense(100, input_shape=(100,)))
    return model

model = create_model()
sgd = SGD(lr=0.01, decay=1e-6, momentum=0.9, nesterov=True)
model.compile(loss=my_mse, optimizer=sgd)

open('/tmp/json_model', 'w').write(model.to_json())

model = model_from_json(open('/tmp/json_model').read(), custom_objects={'my_mse': my_mse})

Closing outdated PRs following the release of Keras 1.0.


Added more headings font-weight options, #379

Added more Public Sans font files to the fonts folder (font weight variations)
Added references to those additional fonts files in _fonts.scss
Added sample page with real time content that is displaying headings and their font-weight variations

NOTE: THis is font exploration is case study that will be presented to DCC customer. New headings font weight applied to the headings in the sample page only and is not applied globally yet.
Figma headings font exploration reference screenshot:

Nice @kkoryaka! Will be cool to split this out into a separate typography component soon

Good to go @timothyshambra, Thank you!


Transparency issue when compress/ optimize the baseColor png file

Description
The glb assets with transparency in the baseColor map as a compressed/ optimized png. The same asset displayed correctly in BabylonJS Sandbox player, donmccurdy's ThreeJS player, but not in the Model Viewer or, the ThreeJS online editor.
Version
The test is done online https://modelviewer.dev/editor/ as of September 11th, 2020.
Browser Affected

[v ] Chrome

OS

[v] Windows

I believe this is the same issue, and it seems to be fixed now: https://github.com/mrdoob/three.js/issues/20362
I'll close this when we update to the next version of three.js, which should be before our next release.

That's great thank you!

Closed by #1577


add markdown editor for note field in seed form

Basics

[x] I added a line to changelog.md
[x] The PR is rebased with current master.

[ ] References to issues, e.g. close #X, are in the commit messages and changelog.
[x] The buildserver is happy.

Checklist

[ ] I have installed and I am using pre-commit hooks
[ ] I fully described what my PR does in the documentation
[ ] I fixed all affected documentation
[ ] I fixed the introduction tour
[ ] I wrote migrations in a way that they are compatible with already present data
[ ] I fixed all affected decisions
[ ] I added automated tests or a manual test protocol
[ ] I added code comments, logging, and assertions as appropriate
[ ] I translated all strings visible to the user
[ ] I mentioned every code or binary not directly written or done by me in reuse syntax
[ ] I created left-over issues for things that are still to be done
[ ] Code is conforming to our Architecture
[ ] Code is conforming to our Guidelines
[ ] Code is consistent to our Design Decisions
[ ] Exceptions to any guidelines are documented

Review

[ ] I've tested the code
[ ] I've read through the whole code
[ ] I've read through the whole documentation
[ ] I've checked conformity to guidelines

Looks great. Itemize/... are not visible for me, is this a known problem?
Please also always check the boxes in the top post. The basics should be always fulfilled before asking for reviews (e.g. in this case here, the CI does not succeed).

@markus2330 i fixed the issue with the invisible bullet points

jenkins build please


Remove unused spring.cloud.stream property in root pom.xml

Upgraded the property to the latest one. This is needed for the spring-cloud-stream-test-support-internal artifact as this is not coming down as part of the spring cloud dependencies bom.


Fixed bug that made sample bot crash when not being able to write an emoji

Fixed bug that made sample bot crash when not being able to write an emoji

Thank you!


add rename

Codecov Report

Merging #1797 (39ef038) into main (c9cb3d0) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1797      +/-   ##
==========================================
- Coverage   94.13%   94.13%   -0.01%
==========================================
  Files         275      275
  Lines       51895    51895
==========================================
- Hits        48851    48850       -1
- Misses       3044     3045       +1

Impacted Files
Coverage Δ

src/fastfield/multivalued/mod.rs
98.06% <0.00%> (-0.39%)
:arrow_down:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Run iOS branch again in CI and confirm that it passes on devices 1654

This change is

PR is added to the queue for testing as 1. task. (40205b4)

Test 98563774 (40205b4) build started.

Test (Success) 98563774 build is completed (40205b4)
See https://github.com/ThaliTester/TestResults/tree/9856377440205b4_Run_iOS_branch_again_in_CI_and_confirm_that_it_passes_on_devices_1654_larryonoff/ for the logs

PR is added to the queue for testing as 3. task. (93d976a)

Test<PHONE_NUMBER>205b4(40205b4) has failed
See https://github.com/ThaliTester/TestResults/tree/9856377440205b4_Run_iOS_branch_again_in_CI_and_confirm_that_it_passes_on_devices_1654_larryonoff/ for the fail logs

Test 98563774 (93d976a) build started.

Test (Success) 98563774 build is completed (93d976a)
See https://github.com/ThaliTester/TestResults/tree/9856377493d976a_Run_iOS_branch_again_in_CI_and_confirm_that_it_passes_on_devices_1654_larryonoff/ for the logs

Test<PHONE_NUMBER>d976a(93d976a) has failed
See https://github.com/ThaliTester/TestResults/tree/9856377493d976a_Run_iOS_branch_again_in_CI_and_confirm_that_it_passes_on_devices_1654_larryonoff/ for the fail logs

Reviewed 1 of 1 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

PR is added to the queue for testing as 2. task. (2f8b159)

Test (Fail) 98563774 build is completed (2f8b159)
See https://github.com/ThaliTester/TestResults/tree/985637742f8b159_Run_iOS_branch_again_in_CI_and_confirm_that_it_passes_on_devices_1654_larryonoff/ for the logs

PR is added to the queue for testing as 1. task. (732ad98)

Test 98563774 (732ad98) build started.

Test (Fail) 98563774 build is completed (732ad98)
See https://github.com/ThaliTester/TestResults/tree/98563774732ad98_Run_iOS_branch_again_in_CI_and_confirm_that_it_passes_on_devices_1654_larryonoff/ for the logs

PR is added to the queue for testing as 1. task. (13b1ea0)

Test 98563774 (13b1ea0) build started.

Test (Success) 98563774 build is completed (13b1ea0)
See https://github.com/ThaliTester/TestResults/tree/9856377413b1ea0_Run_iOS_branch_again_in_CI_and_confirm_that_it_passes_on_devices_1654_larryonoff/ for the logs

Test<PHONE_NUMBER>b1ea0(13b1ea0) has failed
See https://github.com/ThaliTester/TestResults/tree/9856377413b1ea0_Run_iOS_branch_again_in_CI_and_confirm_that_it_passes_on_devices_1654_larryonoff/ for the fail logs

@yaronyg Looks like non actual PR for now. We still have known issues with CI


conn.lo error

First time installation for sqlsrv and pdo_sqlsrv
using microsoft azure sql server
using rasparian (Debian 8)
php 7.0
im receiving conn.lo error
In file included from /usr/include/sql.h:19:0,                  from /tmp/pear/temp/sqlsrv/shared/xplat.h:30,                  from /tmp/pear/temp/sqlsrv/shared/typedefs_for_linux.h:23,                  from /tmp/pear/temp/sqlsrv/shared/xplat_winnls.h:24,                  from /tmp/pear/temp/sqlsrv/shared/FormattedPrint.h:24,                  from /tmp/pear/temp/sqlsrv/shared/core_sqlsrv.h:41,                  from /tmp/pear/temp/sqlsrv/php_sqlsrv.h:25,                  from /tmp/pear/temp/sqlsrv/conn.cpp:20: /usr/include/sqltypes.h:251:33: note: previous declaration as 'typedef long unsigned int UDWORD'  typedef unsigned long int       UDWORD;                                  ^ Makefile:194: recipe for target 'conn.lo' failed
The so should install but instead it shows code error.
When run this sudo pecl install sqlsrv pdo_sqlsrv command

@zhiyan114 Could you provide the full error message? It's not clear from what you have provided where the conflicting declarations are.

After it runs the build command:
/bin/bash /tmp/pear/temp/pear-build-rootNQun35/sqlsrv-4.3.0/libtool --mode=compile g++ -std=c++11 -I. -I/tmp/pear/temp/sqlsrv -DPHP_ATOM_INC -I/tmp/pear/temp/pear-build-rootNQun35/sqlsrv-4.3.0/include -I/tmp/pear/temp/pear-build-rootNQun35/sqlsrv-4.3.0/main -I/tmp/pear/temp/sqlsrv -I/usr/include/php/20151012 -I/usr/include/php/20151012/main -I/usr/include/php/20151012/TSRM -I/usr/include/php/20151012/Zend -I/usr/include/php/20151012/ext -I/usr/include/php/20151012/ext/date/lib -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/tmp/pear/temp/sqlsrv/shared/  -DHAVE_CONFIG_H  -std=c++11 -D_FORTIFY_SOURCE=2 -O2 -fstack-protector   -c /tmp/pear/temp/sqlsrv/conn.cpp -o conn.lo libtool: compile:  g++ -std=c++11 -I. -I/tmp/pear/temp/sqlsrv -DPHP_ATOM_INC -I/tmp/pear/temp/pear-build-rootNQun35/sqlsrv-4.3.0/include -I/tmp/pear/temp/pear-build-rootNQun35/sqlsrv-4.3.0/main -I/tmp/pear/temp/sqlsrv -I/usr/include/php/20151012 -I/usr/include/php/20151012/main -I/usr/include/php/20151012/TSRM -I/usr/include/php/20151012/Zend -I/usr/include/php/20151012/ext -I/usr/include/php/20151012/ext/date/lib -D_LARGEFILE_SOURCE -D_FILE_OFFSET_BITS=64 -I/tmp/pear/temp/sqlsrv/shared/ -DHAVE_CONFIG_H -std=c++11 -D_FORTIFY_SOURCE=2 -O2 -fstack-protector -c /tmp/pear/temp/sqlsrv/conn.cpp  -fPIC -DPIC -o .libs/conn.o In file included from /tmp/pear/temp/sqlsrv/shared/xplat.h:99:0,                  from /tmp/pear/temp/sqlsrv/shared/typedefs_for_linux.h:23,                  from /tmp/pear/temp/sqlsrv/shared/xplat_winnls.h:24,                  from /tmp/pear/temp/sqlsrv/shared/FormattedPrint.h:24,                  from /tmp/pear/temp/sqlsrv/shared/core_sqlsrv.h:41,                  from /tmp/pear/temp/sqlsrv/php_sqlsrv.h:25,                  from /tmp/pear/temp/sqlsrv/conn.cpp:20: /tmp/pear/temp/sqlsrv/shared/xplat_intsafe.h:50:29: error: conflicting declaration 'typedef windowsULong_t DWORD'  typedef windowsULong_t      DWORD;                              ^ In file included from /usr/include/sql.h:19:0,                  from /tmp/pear/temp/sqlsrv/shared/xplat.h:30,                  from /tmp/pear/temp/sqlsrv/shared/typedefs_for_linux.h:23,                  from /tmp/pear/temp/sqlsrv/shared/xplat_winnls.h:24,                  from /tmp/pear/temp/sqlsrv/shared/FormattedPrint.h:24,                  from /tmp/pear/temp/sqlsrv/shared/core_sqlsrv.h:41,                  from /tmp/pear/temp/sqlsrv/php_sqlsrv.h:25,                  from /tmp/pear/temp/sqlsrv/conn.cpp:20: /usr/include/sqltypes.h:96:24: note: previous declaration as 'typedef long unsigned int DWORD'  typedef unsigned long  DWORD;                         ^ Makefile:194: recipe for target 'conn.lo' failed make: *** [conn.lo] Error 1 ERROR:make' failed
`

There is a conflicting declaration of DWORD somewhere in your header files. What does your unixodbc_conf.h look like? Can you attach it here? It is likely in your /usr/include directory.

Your header file defines SIZEOF_LONG_INT as 4. SIZEOF_LONG_INT is then used in sqltypes.h to typedef unsigned long as DWORD, but the sqlsrv source typedefs unsigned int as DWORD, and these conflict because unsigned long is 8 bytes on your system and unsigned int is 4 bytes. SIZEOF_LONG_INT should be 8. I suspect you installed unixODBC manually with certain configure flags - can you provide the commands you used to install unixODBC?
The PHP drivers used to require a specific set of configure options relating to type lengths when building unixODBC, but that is no longer the case and the packaged unixODBC from apt works. If you do not specifically need to manually compile unixODBC for some other application, it would be easiest to remove it from your system and reinstall using apt-get install unixodbc.

@zhiyan114 do you have any updates? Otherwise, due to inactivity, we will close this issue in a few days.

Closing this issue, @zhiyan114
Please feel free to reopen if you have any question about this.

I am having the same issue.
lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 18.04 LTS
Release:	18.04
Codename:	bioni

odbcinst -j
unixODBC 2.3.4
DRIVERS............: /etc/odbcinst.ini
SYSTEM DATA SOURCES: /etc/odbc.ini
FILE DATA SOURCES..: /etc/ODBCDataSources
USER DATA SOURCES..: /home/maruf/.odbc.ini
SQLULEN Size.......: 4
SQLLEN Size........: 4
SQLSETPOSIROW Size.: 2

odbcinst -q -d -n
[ODBC Driver 17 for SQL Server]
The error I receive is:
/tmp/pear/temp/sqlsrv/shared/xplat_intsafe.h:50:29: error: conflicting declaration ‘typedef windowsULong_t DWORD’
 typedef windowsULong_t      DWORD;
                             ^~~~~
In file included from /usr/include/sql.h:19:0,
                 from /tmp/pear/temp/sqlsrv/shared/xplat.h:30,
                 from /tmp/pear/temp/sqlsrv/shared/typedefs_for_linux.h:23,
                 from /tmp/pear/temp/sqlsrv/shared/xplat_winnls.h:24,
                 from /tmp/pear/temp/sqlsrv/shared/FormattedPrint.h:24,
                 from /tmp/pear/temp/sqlsrv/shared/core_sqlsrv.h:41,
                 from /tmp/pear/temp/sqlsrv/php_sqlsrv.h:25,
                 from /tmp/pear/temp/sqlsrv/conn.cpp:20:
/usr/include/sqltypes.h:96:24: note: previous declaration as ‘typedef long unsigned int DWORD’
 typedef unsigned long  DWORD;
                        ^~~~~
Makefile:194: recipe for target 'conn.lo' failed
make: *** [conn.lo] Error 1
ERROR: `make' failed

Thanks

Hi @marufmax
We have not seen this before. While we are investigating, please tell us how you installed PHP (7.2?) and/or ODBC 17.

I'd installed ODBC 17 from the instructions provied in here https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server?view=sql-server-2017
#Ubuntu 18.04
curl https://packages.microsoft.com/config/ubuntu/18.04/prod.list > /etc/apt/sources.list.d/mssql-release.list

exit
sudo apt-get update
sudo ACCEPT_EULA=Y apt-get install msodbcsql17
# optional: for bcp and sqlcmd
sudo ACCEPT_EULA=Y apt-get install mssql-tools
echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bash_profile
echo 'export PATH="$PATH:/opt/mssql-tools/bin"' >> ~/.bashrc
source ~/.bashrc
# optional: for unixODBC development headers
sudo apt-get install unixodbc-dev

and PHP from ondrej PHP repository.

Please note that for PHP 7.2 you don't need the ondrej repository, not to mention that it comes with dependencies that may conflict with a base Ubuntu 18.04 install. Please read the notes in our documentation.

As @david-puglielli  stated above
when I changed SIZEOF_LONG_INT to 8 in the file
/usr/include/unixodbc_conf.h
It compiled successfully!

I got the same error that @marufmax got, just remember to install
# optional: for unixODBC development headers
sudo apt-get install unixodbc-dev

After that, it worked. !

I got the same error that @marufmax got, just remember to install
# optional: for unixODBC development headers
sudo apt-get install unixodbc-dev

After that, it worked. !

thanks ..
I install this and try install SQLSRV again and it works ...


Molecular selection for the use of the center of mass as target in the MSD

Is your feature request related to a problem? Please describe.
The MSD routine would need a possibility to choose the center of mass of a molecule as a target.
Describe the solution you'd like
The grammar could be adapted for molecular selection.
Additional context
If it is possible to select by molecules e.g. H 2 the center of mass can be used as target. The selection is using AtomicSystem which can call the property center of mass.

Important feature request.
So I am unsure what would be the best option to choose from. I have to possible solutions in my mind, but first a bit of background.
So until now at the moment the Selection class and the selection.py module only use the Topology of an AtomicSystem instance to determine the parsed selection. But as @stkroe indicated it would we really helpful to have the full AtomicSystem information available to the Selection class and indeed it was also planned for future releases.
By this enhancement a lot of interesting selection features would get available (after implementation) like e.g.
selection = "CA < 2.0"  #selecting everything within 2.0 Angstrom of atomtype CA

selection = "res~5 > 3.0" #selecting everything not within 3.0 Angstrom of (for example - not yet defined) the center of mass of residue with index 5

So all of these considerations would be quite forward to implement, however maybe by reading in between the lines the problem with a center-of-mass selection can already be identified.
The selection module is in a way defined that it depends on Topology and in future also highly likely on AtomicSystem (would also be necessary for something like center-of-mass selection). Due to this dependency the selection module is designed in a way that it only yields the absolute atomic indices of the full Topology (aka. AtomicSystem) with which they can be then indexed. But in order to make a center-of-mass selection it wouldn't be sufficient to return the indexed system, as the AtomicSystem does not contain any information about the center-of-mass positions. In order to implement this the selection would have to yield somehow not only indices but immediately a new AtomicSystem represented by the center-of-mass coordinates. This would lead to a quite severe design problem (circular dependeny):
AtomicSystem -> Selection -> AtomicSystem

So I would have now two solutions I can think of:
Solution 1
We just introduce a new method to the AtomicSystem class, which return a new AtomicSystem object based on the center-of-mass of the residues and an optional key for command line programs and also input file tools use-center-of-mass.
Solution 2
Probably the more cleaner solution from the perspective of a user we could wrap the actual definition of Selection in an other module along with the AtomicSystem definition, which in the end would make it possible use something like:
selection = com(res(H2))

The implementation of this restructuring would not be that straightforward - but probably manageable.
HOWEVER
We would have to rethink the grammar rules defined to get a clean and non-ambiguous grammar syntax (EBNF). To be more clear at the moment I am not sure how to combine different selection entries like for example.
selection = com(res~3 and res~7) # would be really straightforward

# so the | operator is nothing else than a without
# by writing 4 it would just match the atom in the system with index 4
selection = com(res(H2)) | 4

How would now the last selection be parsable? Of course in order to be a complete grammar definition we should be able to write something like this:
seletion = selection1 | selection2

# with
selection1 = com(res(H2))
selection2 = 4

But of course for the interpretation of these two results would strongly differ in terms of logical interpretation when just looking at the two selection definitions. It would also be possible two violate that selection = selection1 | selection2, but I would choose this kind of solution only as a sort of last resort - as this HAS to lead to some severe complications and erronous definitions in future extensions of the grammar.
So for the interested readers who made it until this point - If you have any idea how to implement/define Solution 2 please let us here below (or in a discussion section that I will probably open soon).
For me at the moment I would just go with Soltution 1 as I am not sure on how to handle the grammar issues in Solution 2
@galjos @stkroe

Question: Would it make sense to have a Molecule class/selection that would automatically use the COM for the MSD calculation?

Question: Would it make sense to have a Molecule class/selection that would automatically use the COM for the MSD calculation?

What do you exactly mean with Molecule class. So of course, choosing the use-center-of-mass could be the default setting.
Then internally one would just have to perform something like
selection = Selection("some selection").select(atomicSystem.topology)

com_system = atomicSystem[selection].com_resiudes()

Of course this is only possible if the user builds the atomicSystem with information about residues... - as most of the selection features do.


pull request for e2e test at 11/20/2016 12:56:05

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

optest/docs/updated_at.md
:white_check_mark:Succeeded

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


🍒 Cherry pick PR #8058 to staging 🍒

🍒 Cherry pick https://github.com/Expensify/App/pull/8058 to staging 🍒

🚀 Cherry-picked to staging by @OSBotify in version: 1.1.42-4 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
failure ❌

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

🚀 Deployed to production by @chiragsalian in version: 1.1.42-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[Bugs] why some SMF procedures are not integrated into V3.2.1?

For examples,
there are some differences in pfcp/handler.go between new and old code.

Hi @zhangds007
Refer to https://github.com/free5gc/smf/pull/50,
All the pfcp response handlers had been moved into associated request handler.


e2e: fpga: fix intermittent failures

fpga test fails due to webhook not being read/available when the pod is scheduled. Fix test by waiting for webhook to be running&ready.

@hj-johannes-lee please help review


Cert Scheme Revision: Chapter 2 Roles

Provide chapter 2 for the new version of the certification scheme in the following branch: https://github.com/International-Data-Spaces-Association/IDS-RAM_4_0/tree/cert_scheme_revision
-> Provide more details regarding the differentiation of roles for the two types or certification, links to further resources (rulebook, link to website with list of approved evaluation facilities,…)

Time plan:

Version for review of the WG Certification until June, 17th 2022
Feedback received and integrated until WG Meeting on June, 29th 2022
Official approval of the new version in the WG Meeting

The chapter has been revised and provided in the respective branch/pull-request #189. Please review and provide feedback :)


introduce hasKnownResult to optimize several parsers.

Often, we can statically see what the result value will be if a parser succeeds.
If we know this, can optimize map, select and flatMap.
In particular, we can avoid reallocating a parser inside each flatMap.
Most users should avoid using flatMap anyway, but in a library function, you might need flatMap but want to get the optimization when the user passes you a constant parser.

Codecov Report

Merging #348 (a2181c4) into main (3acc967) will increase coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #348      +/-   ##
==========================================
+ Coverage   96.56%   96.61%   +0.04%
==========================================
  Files           9        9
  Lines        1049     1092      +43
  Branches       94      108      +14
==========================================
+ Hits         1013     1055      +42
- Misses         36       37       +1

Impacted Files
Coverage Δ

core/shared/src/main/scala/cats/parse/Parser.scala
96.47% <100.00%> (+0.05%)
:arrow_up:

Continue to review full report at Codecov.

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

@johnynek could you rebase this?

Yes! I will do. Thanks for the review.
Note, this optimization will mostly apply to flatMap, and most parser don't need flatMap (e.g. our json benchmarks don't use flatMap). But still, I thought it was worth trying to limit the worst case.

@regadas let me know if this looks good.


Increase soft limit on max open files

This is because we open two perf_event_open file descriptors per cpu per
instrumented function.
See b/153086949.

I am not sure if this should be done programatically rather than setting up values on the server. Shouldn't program operate within limits set up for?
You could suggest to user to increase the limit if it is not enough for the service but just doing that without user consent seems not right.

I am not sure if this should be done programatically rather than setting up values on the server. Shouldn't program operate within limits set up for?
You could suggest to user to increase the limit if it is not enough for the service but just doing that without user consent seems not right.

I see the point. In my personal view I'm not concerned. This is a profiler running as root after all. And we are only changing the soft limit for the process itself, which even an unpriviliged process can do. Games have the same limits that are being set here.

I am not sure if this should be done programatically rather than setting up values on the server. Shouldn't program operate within limits set up for?
You could suggest to user to increase the limit if it is not enough for the service but just doing that without user consent seems not right.

I see the point. In my personal view I'm not concerned. This is a profiler running as root after all. And we are only changing the soft limit for the process itself, which even an unpriviliged process can do. Games have the same limits that are being set here.

Agree, I'm not concerned by this. If we find resource issues at some point, we can reset to something smaller. For now, we need to find out if there are limits that would be problematic and for that it's good if we have the limit set as high as possible.


Clean MR::getHashCode

This is one of the million solutions that I attempted to get 1:1, but at this point it's the same logic and only differs by ~2 instructions.


speeding up integration with use-package

I noticed when using the use-package :if keyword to conditionally load a package and making sure the condition results as nil (ie. (use-package 'ivy :if  nil)) the package was still installed. I could tell because the autoloaded commands were available.
With straight-use-package-by-default set to t I run (macroexpand '(use-package ivy)) and get:
(progn
  (straight-use-package 'ivy)
  (defvar use-package--warning138
    (function
     (lambda (keyword err)
       (let ((msg (format "%s/%s: %s"
                          'ivy
                          keyword
                          (error-message-string err))))
         (display-warning 'use-package msg :error)))))
  (condition-case-unless-debug err
      nil
    (error (funcall use-package--warning138 :catch err))))

With this sexp calling use-package will always install ivy regardless of whether you use the :if or :disable keyword. It also seems that this may slow down startup because all packages are installed with straight immediately upon startup. Only the configuration and settings added by use-package are deferred but not the package itself. Ideally, straight-use-package should be called just before use-package tries to configure the package (maybe in between :init and :config).
I've been thinking about these three ways of fixing it:

create a wrapper around use-package - would involve duplicating a lot of the work use-package does
create a wrapper around a function that use-package uses - possibly best solution?
change the order of straight in use-package-keywords - risky

I noticed when using the use-package :if keyword to conditionally load a package and making sure the condition results as nil (ie. (use-package 'ivy :if nil)) the package was still installed.

Maybe it is desired?
:straight servers the same purpose as use-package's built-in :ensure and it does the same thing, i.e., (use-package foo :if nil :ensure t) will install foo. I also find it is strange and reported last year in https://github.com/jwiegley/use-package/issues/415.

Oh ok. I can see how for some crucial packages like helm or ivy that would be desirable.  However, is it possible to defer the package installation until needed? For instance, I wouldn't want (straight-use-package 'clojure-mode) to be called on startup because I might never use clojure in my emacs session.
Perhaps manually specifying the load-path would do it?
(use-package clojure-mode :load-path "~/.emacs.d/straight/build/clojure-mode")

This was previously tracked in #45, but figuring that out from the contents of the issue would probably have been quite difficult, so let's make this issue the canonical one.

There are three use cases here:

Install package unconditionally, but don't configure it when the :if fails.
Don't install package when the :if fails, but still register its recipe with straight.el.
Don't install package or register recipe with straight.el when the :if fails.

Currently, case (1) happens when you do this:
(use-package foo
  :straight t
  :if <cond>)

And you can get case (2) by doing this:
(if <cond>
    (use-package foo
      :straight t)
  (straight-register-package 'foo))

Case (3) looks as follows:
(when <cond>
  (use-package foo
    :straight t))

Let me start out by saying that case (3) is problematic and you probably should never do it. The reason is that writing accurate version lockfiles relies on straight.el knowing what packages are part of your configuration, even if they are not all installed. You should always register all packages that are part of your configuration, even if you use lazy or conditional installation.
Now I'd be open to making case (2) what happens when you write the code for case (1). In that case, you could recover the behavior of case (1) by doing:
(straight-use-package 'foo)
(use-package foo
  :if <cond>)

Thoughts on which case should be the default?

However, is it possible to defer the package installation until needed? For instance, I wouldn't want (straight-use-package 'clojure-mode) to be called on startup because I might never use clojure in my emacs session.

This is lazy installation, which is an entirely different question than your original comment (which dealt with conditional installation). I have plans to add direct support for lazy installation to straight.el, but this requires a nontrivial amount of additional infrastructure. See #197.
If you want to implement a low-budget version yourself, it looks like this:
(straight-use-package-lazy 'clojure-mode)
(defun clojure-mode ()
  (interactive)
  (fmakunbound 'clojure-mode)
  (straight-use-package 'clojure-mode)
  (clojure-mode))

In fact, straight.el's use-package integration used to have support for doing this automatically for all functions declared in :commands, :bind, :mode, etc. But it required a lot of machinery on the use-package side. When @jwiegley refactored use-package, he rightfully decided to remove said machinery, which was kind of a hack, until such time as it could be re-added in a cleaner and more systematic way. Thus my new plan is to implement deferred installation support almost entirely on the straight.el side. I think it will be both cleaner and more useful.

(use-package clojure-mode :load-path "~/.emacs.d/straight/build/clojure-mode")

No, this is a really really bad idea. Never use :load-path with straight.el.

Thoughts on which case should be the default?
I personally would prefer making case (2) happen when writing the code for case (1) the default. It seems to make more intuitive and cleaner to me. Even recovering case (1) seems after changing the default seems simpler than getting case (2) currently.

I appreciate the detailed answers.

Let's leave this open in order to track making case (2) happen to default.


Missing OpenAI API key results in blank screen while on demo GPT app

I start new project with open-saas, all env keys dummy/empty (as per instructions for getting started), I go to "GPT Scheduler", submit, and get blank white screen. I see errors in the console, and suggestion to add an error boundary in React -> we should probably do that? So by default errors are handled in some nicer way, not just blank screen.

hm. I've provided an .env.server.example file and instruct users to copy this over as .env.server on project start. if they do that, they'll see this message @Martinsos

I could add a client initiator function that throws an error if no api key is present at all (not even a dummy) that would do this:

wdyt?

@vincanger I followed those instructions, and I copied over that file, but I didn't get that message, I got a blank screen instead.

@Martinsos odd. you'll see in the first pic above that it's showing the incomplete/dummy api key from the env vars. I've nevertheless updated it ( in commit https://github.com/wasp-lang/open-saas/commit/71238070cdf7957cceacb948d53047b41292b4a7) so that they'll see the error in the second pic above, if so.

@vincanger should we first confirm I am not having an issue anymore, before we close the issue?
We actually never reached the point where you managed to reproduce the problem I had: I claim I get blank screen, you don't know how I got there. So we can't really know if you fixed my issue at all, and if it even is an issue that we are discussing. Maybe I did something else wrong. Maybe I have this issue but you don't due to some other factors.
I would rather we investigate it a bit further, before we close this.
For example, what I can do is pull this change you did and try it again, see what happens, if I can reproduce it still.

First of all, I just realized I do always have OPENAI_API_KEY in my env, so even without it being set in .env.server, it should work. So I don't think anymore that missing env var was an issue actually when I reported this issue, it must have been something else.
Second, I just tried to reproduce it again, and I failed. I tried cloning this repo, to get th latest commit in, and couldn't reproduce it.
I also tried via wasp new, since that is how I got into trouble last time, and that also didn't work, couldn't reproduce.
I wonder if error was instead coming from OpenAI API due to 503 or something like that, and maybe that was crashing the app.
Anyway, it doesn't seem like missing OPENAI API key is the issue here, nor do I know how to reproduce it, so all good from my side.

yes the issue was likely from OpenAI @Martinsos -- @sodic had the same problem and made me aware that it was sending back, what should have been JSON, as a weird object. As you know, the models got crappier during the "upgrade", but I resolved the issue by making the task a bit easier for it :)

yes the issue was likely from OpenAI @Martinsos -- @sodic had the same problem and made me aware that it was sending back, what should have been JSON, as a weird object. As you know, the models got crappier during the "upgrade", but I resolved the issue by making the task a bit easier for it :)

If that is causing the blank screen, should we look into handling that in a better way then? I think we always want to avoid the blank screen, as it is quite confusing for the user.


.Net Core binding dynamically add modules

Hi,
I would like to know if there is a plan to extend the Microsoft.Azure.Devices.Gateway.GatewayInterop  to expose more of the gateway.dll functions?
I'm specially interested in being able to achieve same functionality as here from .NetCore application.
Or at least the ability to specify JSON configuration as string in addition to current option of specifying a path to JSON file in GatewayInterop.CreateFromJson(string file_path)
Regards,
Ali

Logged at /Azure/iot-edge/


added sanction cred test

Adding a sanction unit test that tests the path constraints field

Super outdated, closing. Feel free to refresh and reopen.


cpu-usage-exceeds-100: 50% of 50% are a quarter, not a half

A processor that's running 50% of the time and clocked down to 50% frequency performs only half the work of a processor that's running 100% of the time at 100% frequency.
If a processors runs half of the time and in addition is only running at half speed, it would only do a quarter of the work it could do, if it were running all the time at full speed. At least my dusty math skills tell me that 🙂

https://github.com/MicrosoftDocs/SupportArticles-docs/blob/main/support/windows-client/performance/cpu-usage-exceeds-100.md
https://docs.microsoft.com/en-us/troubleshoot/windows-client/performance/cpu-usage-exceeds-100

Hi @datto-cschulze,
I think it should be a typo. The first 50% should be 100%. I will correct it. Thanks for the feedback.


Travis CI: E: Package 'docker-engine' has no installation candidate

Issue Type

Bug report

Actual Behaviour
Due Travis CI images update builds now fails with error:
Documentation still not updated: https://molecule.readthedocs.io/en/master/testing.html#travis-ci
E: Package 'docker-engine' has no installation candidate

The command "sudo apt-get install -o Dpkg::Options::="--force-confold" --force-yes -y docker-engine" failed and exited with 100 during .

Build fails on command:
sudo apt-get install -o Dpkg::Options::="--force-confold" --force-yes -y docker-engine

At this time travis images have not package docker-engine.
Possible solutions:

Remove docker-engine install command from `.travis-ci.yml (image have bundled Docker version 17.03.1-ce, build c6d412e)
Change to install docker-ce from docker repository: https://docs.travis-ci.com/user/docker/#Installing-a-newer-Docker-version

before_install:
  - curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo apt-key add -
  - sudo add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable"
  - sudo apt-get update
  - sudo apt-get -y install docker-ce

Use old images, add to .travis.yml:

group: deprecated-2017Q2

Documentation of using docker in travis now outdated:

https://molecule.readthedocs.io/en/master/testing.html#travis-ci
https://docs.travis-ci.com/user/docker/#Installing-a-newer-Docker-version

Thanks @popstas 🎸

Thanks @popstas


Node images

Is it possible to use images for nodes, instead of labels??

Yep, when creating a node give it an image property something like:
var node = graph.newNode({ image: { src: "http://...." }});


test rewrites support

What's the purpose of this pull request?

How it works?

How to test it?

Starters Deploy Preview

References

@icazevedo is this still valid? Or can we close it?

Closing it! Thanks


While Prisma extension is enabled, typescript server keeps crashing on each save

I noticed that in one of my projects TypeScript's server keeps crashing on each save. After disabling Prisma's extension it seems to stop.
Let me know if you need more details.

Hey @dutzi, Could you provide a bit more info. Is this a nextjs project?

Hey @williamluke4, no, it's a monorepo, if that's relevant, I'll try setting up a simple repo where this reproduces and update.

Thanks @dutzi, A reproduction would be very helpful :)

Interesting, I might have a similar issue.

Ah, cool, anything unique about your repo, @Sytten?

Also a monorepo with multiple TS packages. I confirm that the prisma plugin is the issue. The server is not restarting on file change without it.

We just released a new version of the extension - 2.10.2 with fixes of related logic.
Can you check, if it's fixed in there for you?
Thanks!

Seems like it's fixed!

Great will closes this then :)

I installed the latest 2.11.0 and it still does it. @williamluke4 @timsuchanek

Ditto in 2.11.1, it started happening when I switched into a monorepo with a shared node_modules a few weeks ago, so sounds like that's the cause.

Can you please provide a reproduction? That would be very helpful.
Just as a note: The TS Language server gets restarted on every prisma generate call by the extension, so when the file node_modules/.prisma/client/index.d.ts changes. This does not happen on every save though.

Also can you please run Developer: Toggle developer tools and look in the developer tools console. Can you please share the logs from there?

@carmenberndt check https://github.com/microsoft/vscode/issues/108288 it is pretty much detailed there.
For me every change to any file makes the server restart. I dont really have time to create a repo for that but a simple yarn 1 monorepo hoisted will allow you to reproduce.

I did see this already, but back then the Next.js related things were still in the extension, so it would be great to have the up to date logs for this.

Ok I will try to find time to test it again on one of my clients' project. Let's circle back next week.

Pulled some logs (2.12.1), for some reason the watcher is restarting for any file change:
console.ts:137 [Extension Host] File {redacted}/node_modules/backend/api/graphql/Node.ts has been changed. Restarting TS Server.
console.ts:137 [Extension Host] File {redacted}/node_modules/backend/dev/docker/postgres-data/pg_wal/00000001000000000000007C has been changed. Restarting TS Server.
console.ts:137 [Extension Host] File<EMAIL_ADDRESS>has been changed. Restarting TS Server.
console.ts:137 [Extension Host] File {redacted}/node_modules/backend/dev/docker/postgres-data/pg_stat_tmp/db_0.stat has been changed. Restarting TS Server.
console.ts:137 [Extension Host] File {redacted}/node_modules/backend/dev/docker/postgres-data/pg_stat_tmp/global.stat has been changed. Restarting TS Server.
console.ts:137 [Extension Host] File {redacted}/node_modules/backend/dev/docker/postgres-data/pg_stat_tmp/db_16384.stat has been changed. Restarting TS Server.

It looks like it's watching all of node_modules, and since yarn workspaces symlinks packages, it ends up watching all file changes.

I will give it a try once thats released, but I am confident that will fix it. This has been so annoying for so long I hope it will be resolved :)


Bump main branch to version 1.0.0

Describe your changes :
I'm still looking to figure out if we have to do this, but feel free to close this PR if we don't need it.
Type of change :

[x] Improvement
[x] New feature

Checklist:

[x] I have read the CONTRIBUTING document.
[ ] I have commented on my code, particularly in hard-to-understand areas.
[ ] I have added tests that prove my fix is effective or that my feature works.
[x] All new and existing tests passed.

Reviewers
Ingestion: @open-metadata/ingestion

@nahuelverdugo it should 0.13.2-SNAPSHOT

@nahuelverdugo it should 0.13.2-SNAPSHOT

@harshach when we released 0.13.1 we changed it to 0.13.2-SNAPSHOT. I think we will start working on version 1.0.0 in the main branch, right?


[Proposal] Add Support for StableLM Base & Tuned, 3B & 7B

Proposal
Stability AI released instruction tuned (tuned) and pre-trained (base) models of size 3B and 7B, open source: https://huggingface.co/stabilityai/stablelm-tuned-alpha-7b (see others here https://huggingface.co/stabilityai/ ).
Motivation
Work on instruction following (fine-tuned, not RLHF) models seems exciting to me. Also these models are trained on 800B tokens each which is great and they're probably much better to study than other similarly sized or larger models in TransformerLens.
They use the NeoX architecture so should not be that hard to add in
Checklist

[x] I have checked that there is no similar issue in the repo (required)

Note that they do something weird with the tokenizer for , , , it might be good to make a util to deal with that


Temporarily fix boolean operation bug

https://github.com/3b1b/manim/pull/1711
Motivation

solution full credits to @widcardw
Just helping to upload this
class DifferenceExample(Scene):
    def construct(self):
        cir1 = Circle(radius=3).move_to(LEFT * 1.5)
        cir2 = cir1.copy().move_to(RIGHT * 1.5)
        d = Difference(cir1, cir2, color=YELLOW, fill_opacity=0.4)
        self.add(cir1, cir2, d)

class ExclusionExample(Scene):
    def construct(self):
        cirs = VGroup(*[
            Circle(radius=2).move_to(1.5 * np.array([
                np.cos(i / 3 * TAU), np.sin(i / 3 * TAU), 0
            ])) for i in range(3)
        ])
        e = Exclusion(*cirs, color=YELLOW, fill_opacity=0.4)
        self.add(cirs, e)

class IntersectionExample(Scene):
    def construct(self):
        cir1 = Circle(radius=3).move_to(LEFT * 1.5)
        cir2 = cir1.copy().move_to(RIGHT * 1.5)
        i = Intersection(cir1, cir2, color=YELLOW, fill_opacity=0.4)
        self.add(cir1, cir2, i)

class UnionExample(Scene):
    def construct(self):
        cir1 = Circle(radius=3).move_to(LEFT * 1.5)
        cir2 = cir1.copy().move_to(RIGHT * 1.5)
        u = Union(cir1, cir2, color=YELLOW, fill_opacity=0.4)
        self.add(cir1, cir2, u)

Proposed changes

Test

Code: same code
Result:

Similar to https://github.com/3b1b/manim/issues/1713, but I don't know why.


Add limitation description for geo coverage problem

Bar visits data is missing for 9-12 states/regions.
Add description in docs for the geo coverage problem.

It looks like something weird happened with the Git branching here; could you try to get it down to the one change without conflicts?
Also, it'd be good to address #302 while we're here.

I will close this PR and make another one.


Bilalshaikh42/issue2664

:tada: This PR is included in version 2.2.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


FS: user who unstake all their assets from nomination pools

when a user withdraw all his redeemable assets from pool, what should we display then?
maybe account details, maybe stake options!

@AMIRKHANEF  We currently shows this page with stake button enabled if they have some tokens available


Error for harmonics with decimal prefactors

Hi,
Some frequency driven systems exhibits a "Period-Doubling" behavior, where a response exists at half the excitation frequency.
Would it be possible to search for half frequency reponses ?
I tried :
add_harmonic!(system_eqs, I, [0.5ω,ω])

But it ends up with the following error :
ERROR: MethodError: no method matching isless(::ComplexF64, ::Int64)
Closest candidates are:
  isless(::Union{StatsBase.PValue, StatsBase.TestStat}, ::Real) at C:\Users\brsinquin\.julia\packages\StatsBase\XgjIN\src\statmodels.jl:90
  isless(::ArfLike, ::Integer) at C:\Users\brsinquin\.julia\packages\Arblib\PdCpA\src\predicates.jl:131
  isless(::Static.StaticInteger{X}, ::Real) where X at C:\Users\brsinquin\.julia\packages\Static\Ldb7F\src\Static.jl:455
  ...

when executing : harmonic_eqs = get_harmonic_equations(system_eqs)

Hello! We've definitely calculated subharmonics before (from the harmonic balance point of view, there is no "subharmonic", simply two harmonics). It works if you use ω/2 instead of 0.5ω . Better to use fractions than decimal prefactors, as you are relying on the harmonics being multiples of each other!
That said, this needs a better error message :)

Hello! We've definitely calculated subharmonics before (from the harmonic balance point of view, there is no "subharmonic", simply two harmonics). It works if you use ω/2 instead of 0.5ω . Better to use fractions than decimal prefactors, as you are relying on the harmonics being multiples of each other! That said, this needs a better error message :)

Thank you for your response, it worked. But since i want to study the harmonics of the half-system excitation frequency i need tio add non integer fractionnal frequency Anzats such as :
 add_harmonic!(laser_eqs, I, [ω/2,ω,ω*(3/2)])
It works with ω/2 but not with ω*(3/2), giving the same error as before. I tried it with different division or inverse multiplication expressions but i do not manage to make it work.

This looks like a problem with the solver from HomotopyContinuation.jl  that occurs when solving huge systems. I have only seen it when the number of paths ran above 10⁸ or so.
Here you're looking at 16 equations of order <= 2 , which should give a max of 2^16 = 65536 solutions. By internal symmetries this reduces to 11169 and runs ok for me:

Funnily enough, your output seems like the solver is also trying to run 11169 paths ... Do other, similar-sized problems (e.g. from https://github.com/NonlinearOscillations/HarmonicBalance-notebooks ) run for you? Do you by any chance have a 32-bit OS?


Docs show python version selector for Community Cloud that doesn't seem to exist

Link to doc page in question (if any):
https://docs.streamlit.io/streamlit-community-cloud/deploy-your-app, specifically the Advanced Settings section.
Name of the Streamlit feature whose docs need improvement:
Community Cloud
What you think the docs should say:
Docs say that there should be a python version selector above the secret.toml text entry field:

But I am unable to find this field anywhere in App Settings for either of my Community Cloud apps:

Hi @Asaurus1! 👋🏻 I just confirmed the dialog image is correct. What is shown on that page is how the dialog appears when deploying an app. It appears differently when modifying an existing app. You can't change the Python version of a deployed app; you have to delete and redeploy it currently.


how to do UV mapping / obj + corresponding

I want to create a UV Map so that with my obj file - I can align the textures correctly.
I played with demo_texture.py - but that's not what I'm after. I need PRNet to dump out a uv texture file that I can glue together with obj file.  kinda like this.
https://developers.google.com/ar/images/canonical-face-texture-photoshop.jpg
https://www.pluralsight.com/blog/film-games/understanding-uvs-love-them-or-hate-them-theyre-essential-to-know#:~:text=UVs are two-dimensional texture,gets applied onto that surface.
python demo_texture.py -i TestImages/AFLW2000/image00081.jpg -r TestImages/trump.jpg -o TestImages/output.jpg

--isTexture True


TypeError: Cannot read properties of null (reading 'parentNode')

Environment

Operating System: MacOS Monterey
Node Version: v18.2.1
Nuxt Version: 3.8.2
Package Manager<EMAIL_ADDRESS>Bundler: Default
User Config: SSR
Modules: ['@pinia/nuxt', 'nuxt-simple-robots', 'nuxt-simple-sitemap']

Reproduction
Use this Stackblitz Sandbox. Click on the About link or Home link at least two times to trigger these errors. In case, it doesn't throw an error, click more than two times.
Uncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')
    at parentNode (chunk-XIAFXKMR.js?v=5667fd31:9234:30)
    at ReactiveEffect.componentUpdateFn [as fn] (chunk-XIAFXKMR.js?v=5667fd31:7242:11)
    at ReactiveEffect.run (chunk-XIAFXKMR.js?v=5667fd31:422:19)
    at instance.update (chunk-XIAFXKMR.js?v=5667fd31:7279:52)
    at updateComponent (chunk-XIAFXKMR.js?v=5667fd31:7106:18)
    at processComponent (chunk-XIAFXKMR.js?v=5667fd31:7041:7)
    at patch (chunk-XIAFXKMR.js?v=5667fd31:6503:11)
    at patchSuspense (chunk-XIAFXKMR.js?v=5667fd31:2618:7)
    at Object.process (chunk-XIAFXKMR.js?v=5667fd31:2537:7)
    at patch (chunk-XIAFXKMR.js?v=5667fd31:6528:16)

Uncaught (in promise) TypeError: Cannot read properties of null (reading 'subTree')
    at move (chunk-XIAFXKMR.js?v=5667fd31:7587:28)
    at move (chunk-XIAFXKMR.js?v=5667fd31:7587:7)
    at Object.resolve (chunk-XIAFXKMR.js?v=5667fd31:2852:11)
    at chunk-XIAFXKMR.js?v=5667fd31:2974:20

Describe the bug
This bug happens when navigating between two pages using NuxtLink where both pages uses setup script and composables like useFetch. useFetch seems to add a delay for the page to load on the server side, clicking again probably triggers some sort of a mismatch or maybe the error itself comes from NuxtLink?
Additional context
We noticed this in an e-commerce site that we're working on. When I try to navigate to a page and click NuxtLink twice, everything freezes. This is a severe headache as this bug isn't present in Nuxt^3.0.0. See Stackblitz Sandbox.
We're actually using Nuxt^3.4.3 which indicates that the bug is present since at least Nuxt^3.4.3 and (probably) upwards. We also downgraded to Nuxt^3.0.0 which seems to eradicate the errors completely but also renders a lot of Nuxt plugins to become incompatible with the downgraded version. Upgrading the package to Nuxt^3.8.2 didn't help us either.
The error doesn't seem to exist when navigating between completely static package where there is no data fetching but I believe that's because a user will never be able to click a link twice as the page loads are almost instantaneous.
Logs
No response

Let's track this in #22900.  This is an issue with vue and Suspense


[WIP] Adjust biz logic.

Description

Add token and metadata.
Throw an error when the upstream server crashes abnormally.

Just FYI, biz leave() should listen to "leave-reply" instead. https://github.com/pion/ion-sdk-js/pull/208


Add more compilation flags (#193)

I'm going to hold off on this until #205 is figured out to avoid churning the CMake files too much. I'm sorry for the extra effort you put in on this, but thanks for doing it.
I do want to merge your build error fixes though. Could you open a separate PR for that?
It seems like you might be new to git (because you made these changes on your master branch instead of a branch). This guide may help understand the basic workflow if you need it: https://github.com/exercism/docs/blob/master/contributing/git-basics.md
To set up a separate branch for just that one change you should be able to do that by Resetting your Master branch, being careful to do the git checkout -b backup step so that you make a separate branch with these changes saved. Then making a new branch forked from master, cherry-picking that one change, and opening a new PR. After following the steps to reset master, that's just:
git checkout master
git checkout -b compile_fixes
git cherry-pick 6898ee59d508d214a5d142542efdcc46cff400ae

That long string is the hash of that one commit.

@patricksjackson Indeed I should have delivered on a separate feature branch instead of using master.
Sure, I can apply flags changes after #205.
I will open a separate PR with build fixes.


Bump Dependencies #10634881998

Bumps dependencies for product-is. Link : https://github.com/wso2/product-is/actions/runs/10634881998

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


I have tested an ontology, it didn't produce anything

I have pushed a sample ontology here: https://github.com/dgarijo/test
Auton did a merge request, but nothing was changed and no diagrams where attached.
Maybe there was some error?

Now no more pull requests have been made to the repository.

@dgarijo , Because
1-Auton where only work with files ending with .rdf, now I changed it to work with files end with .rdf or .owl
2-The drawing or the owl file is giving errors

Ah, it should be working with files ending in .ttl, .owl or .rdf.

Added .ttl and solved

I reopen this issue in order to:
a) Solve the issue with the configuration file, which messed up the diagram creation
b) Widoco documentation integration

@dgarijo The configuration file issues is fixed, and the widoco documentation is integrated.


Import errors for python keras module

Issue type
Bug
Have you reproduced the bug with TensorFlow Nightly?
No
Source
source
TensorFlow version
tf 2.14+
Custom code
No
OS platform and distribution
No response
Mobile device
No response
Python version
3.10.13
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
While working with saving module in python.keras some functions raise importError.
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name '__version__' from 'tensorflow.python.keras'

Since tensorflow==2.14.0 the __version__ is missing from the __init__.py. ( removed in https://github.com/tensorflow/tensorflow/commit/5368a3ad4719842eecae9e4c965b1a5d072cb9e5 )

2.13 init.py
2.14+ init.py

Some functions eg. hdf5_format.save_weights_to_hdf_5_group() still import it in versions 2.14+ See here for tf 2.15.1
def save_weights_to_hdf5_group(f, layers):
  """Saves the weights of a list of layers to a HDF5 group.

  Args:
      f: HDF5 group.
      layers: List of layer instances.
  """
  from tensorflow.python.keras import __version__ as keras_version  # pylint: disable=g-import-not-at-top
  ...

Standalone code to reproduce the issue
from tensorflow.python.keras.saving import hdf5_format

# raises import error
hdf5_format.save_weights_to_hdf_5_group(...)

OR

from tensorflow.python.keras import __version__

Relevant log output
No response

@vixhead,
tensorflow/python/keras code is a legacy copy of Keras since the TensorFlow v2.7 release. Please try to remove any import of tensorflow.python.keras and use the public API from tensorflow import keras till the tensorflow v2.15 and for later releases try to import  as import keras for the keras3.0 version.
Also please try to raise the issue of Keras related in the Keras-team/Keras repo for the quick resolution. Thank you!

Thanks for the answer. I guess we will have to switch to keras public API then if we want to use 2.14+ versions. (and import keras for 2.15+)


Revert "Binary patching of build prefixes "

Reverts Homebrew/brew#12940.
Sorry for the quick revert but installing any package on arm64 is broken and requires a manual brew reinstall to fix.

Review period skipped due to critical label.

Shoot, I thought we had this figured out by moving it to keg instead of keg_relocate.  How do we fix this properly so that we can override codesign_patched_binary while still having this generic method?

os/mac/keg is not the same extend/os/mac/keg. Basically you'd want to move it to the latter, but I've not looked too much further than that in case there's any obstacles.

Yeah I see that makes sense now.  It's not clear why codesign_patched_binary is in os/mac/keg and not extend/os/mac/keg.  I'll have to experiment with this for a bit.


channeldb/invoices: correct stray kvdb.ReadBucket to RBucket

We recently renamed kvdb.ReadBucket to kvdb.RBucket in #4252, but this
was not detected in #4285 since this new code didn't produce a
conflict.

Happily building again. ;-)


Difference from daggy

Continued from Twitter.
If there's a motivating use case it might be worth noting in the README.

Well. union-type has many features not in daggy. Currying, records, ES6 iterator support and recursive types are some that I don't think Daggy has.


[ryu] added ryu_printf

This patch updates the port files to build and install the library ryu_printf in addition to the base library ryu. The new library is a completely independent build, so that the existing library is not affected in any way.
Note: The library generic_128 was not added, because it requires a 128 bit integer type and thus cannot be built under Windows.

Looks great, thanks for the PR!


Validate

Issues:

#22
#26

Coverage increased (+2.09%) to 97.414% when pulling b1577962bca016b5cad834c3347fd9a3da13116c on validate into 2fd481c0b39ca5a348aee1a6100ccee269b96650 on master.


Add basic scapegoat version selection logic

This will improve the out of the box experience as it's more likely to pick a compatible version. While also providing a much newer version of Scapegoat.
Changes:

Make scapegoatVersion an optional setting and if not provided then select a semi-recent version of scapegoat based on the scalaVersion of the subproject ( https://github.com/scapegoat-scala/sbt-scapegoat/pull/157/files#diff-408310465d0d301bcef935eeaa0196a12854ff990ac9c4020e3516b768f5e384R124 )
Add sbt scripted to do testing on behaviour in sbt

Thank you for this! It makes using scapegoat much easier!


class inheriting from params class on line 71

http://puppet-lint.com/checks/class_inherits_from_params_class/
remote: /tmp/tmp.jyS218xzEJ/supervisord/manifests/init.pp - WARNING: class inheriting from params class on line 71
remote: Error: styleguide violation in supervisord/manifests/init.pp (see above)
remote: Error: 1 styleguide violation(s) found. Commit will be aborted.
remote: Please follow the puppet style guide outlined at:
remote: http://docs.puppetlabs.com/guides/style_guide.html

I'm not supporting Puppet < 2.7 so this is not an issue.


v2 log://log events are storing the Rust log::Level

Thanks for all the work around Tauri, v2 is amazing!
I noticed that there is a slight inconvenience around levels in the log plugin.
The plugin uses the following log level enum:
export enum LogLevel {
    Trace = 1,
    Debug = 2,
    Info = 3,
    Warn = 4,
    Error = 5,
}

.... while the enum in the log crate is flipped:
#[repr(usize)]
pub enum Level {
    Error = 1,
    Warn = 2,
    Info = 3,
    Debug = 4,
    Trace = 5,
}

Now, it currently behaves a bit unintuitive when mixing webview logs with native logs.
When invoking the plugin command plugin:log|log, the handler is correctly mapping the webview level to the rust level.
However, events arriving in the webview at log://log are not mapped, so we currently have to map them back manually.
Since it's still the beta, wouldn't it make sense to not flip the enum order here and just use the log::LogLevel one?
If not, it would probably make sense to map levels arriving at log://log to the js ones.

Since it's still the beta, wouldn't it make sense to not flip the enum order here and just use the log::LogLevel one?

imo, yes. Would you mind opening a PR?


Fix --no-clobber ignoring of latest images

Please provide a description of this PR:
Prior fix tried comparing latest with whole image name. Change to see if the suffix is :latest

@ericvn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-test_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-test_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test release-test_istio

lint_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-test_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test release-test_istio

lint_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test lint_istio

gencheck_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-test_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test release-test_istio

lint_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test lint_istio

gencheck_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test gencheck_istio

integ-security_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test integ-security_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

@ericvn: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test lint_istio

gencheck_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test gencheck_istio

integ-security_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test integ-security_istio

release-test_istio
b1d71c6cd07461298ae0aead2595e8da925a93b7
link
true
/test release-test_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Update risk budget to reflect lower severity of Omicron

The current risk budget on your site assumes that 10% of covid patients will have serious outcomes and cites this April 2021 UK study.  If you visit the study it links to 2022 updates of the information, but my layman's reading of the newer version didn't see the same clear statement of what % of covid patients suffer long covid or death.
This NYT article cites several studies on the lower severity of Omicron but again without the clean "x% will suffer long covid or death" statement.
Individual decision making needs to balance a higher tolerance of infection based on the lower expected severity.  (Tempered of course by your personal risk of infecting others who are compromised or not fully boosted.)  Hoping you can dedicate some resources to risk budget side of the tool so it doesn't increasingly skew towards being overly conservative.

Right, so the default risk budget is based mainly on long covid, an outcome that you will of course not find any studies about with respect to Omicron since it is too new. I'm also a layman, but having reviewed maybe a dozen papers about long covid, all of them appear to measure reported symptoms after a long time (6 weeks, 12 weeks, etc) as their endpoint. I've never seen a claim that long covid is predictable before it happens, so I don't know how you'd find a study dated prior to like idk June 2022 that makes an assertion about the risk of long covid and Omicron. We'll just have to wait.
In the meantime, the heart of the microcovid tool is the infection risk calculation, which produces an infection risk. You can always take it upon yourself to compare that number to a different target if you wish.

This is a very helpful overview of why "lower severity" is not a very useful assessment of risk. I've read most of the sources myself previously, so I can vouch for the legitimacy. It is very long but very thorough.


FastHex.kt needs attribution

Module
Other
📝 Description
FastHex.kt is based on FastHex.java by Evan Saulpaugh i.e. me: https://github.com/esaulpaugh/headlong/blob/master/src/main/java/com/esaulpaugh/headlong/util/FastHex.java
You do not have permission to use it except in keeping with the license requirements. One of the requirements is "You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work".
Thanks.

I see the resemblance with the class and some variable names. It's likely that our implementation is based on yours, and that we forgot to add the attribution.
I'm AFK until Monday, but I saw that you have a patch for this ready on your fork. I'm happy to assist you with opening a PR here if you encountered any issues. Otherwise, I can add this myself when I get back.
Thanks

I opened a PR but I'm pretty sure someone deleted it.

Only issues can be deleted, there is no option to delete a PR.
Can you please try opening the PR again? In case there's anything preventing you from opening it, I'd be really grateful if you'd let me know as this would be a major issue, and would like to get it resolved asap!

https://github.com/Kr1ptal/ethers-kt/pull/109


SessionId not supported

In the code there does not seem to be any support for session Id.
Looking at the RabbitMqMapper.cs from line 99.
I am assuming this is because RabbitMQ doesn't have an exact parallel.
Proposal
Is it possible to add a mapping that will pull the session id from the Azure Servicebus message and set it as a Property on the RabbitMq message

then when reading the message you can look for that property and set the session id again
Our messages look like.
async function sendMessage(queueName, message, correlationId, sessionId, srcId) {
  const sender = sbClient.createSender(queueName);

  const message = {
    body: Buffer.from(message, 'utf-8'),
    sessionId: sessionId,
    applicationProperties: {
      sourceId: srcId
     },
     correlationId: correlationId,
  };
  await sender.sendMessages(message);

  await sender.close();
}

Hey @WayneDT
This is already handled in the way that you proposed :) The only difference is that session-id is being sent in AMQP as a property called group-id, visible in rabbit as x-sb-group-id. Group ID is also sent back to the receiver.
But as you noted, this is not a proper implementation of sessions, as it barely passes values back and forth.
/Piotr

I am having trouble actually receiving messages with sessions.
The code I am using is from the Microsoft SDK samples (https://github.com/Azure/azure-sdk-for-js/blob/main/sdk/servicebus/service-bus/samples/v7/javascript/session.js)
It fails when const receiver = await sbClient.acceptSession(queueName, sessionId);
The error I get is  TypeError: Cannot read properties of undefined (reading '4')
if you want to run this follow the instructions i put on issue #9 and then just paste the code from the same above into the index.js

This is expected, as both transaction and session support is not implemented ATM (see https://github.com/piotr-rojek/devopsifyme-sbemulator#not-supported-features). I cannot make any promises to the timeline, but some kind of session support will be implemented in near future.
/Piotr


11 fastapi refactor refactor tests

It is not quite done. But I took the liberty and prepared some endpoint testing. It is not finished as I am not sure how the API will evolve. But the old tests are ported 1:1


Window opens in the wrong GNOME Workspace

Minor issue
The window opens in the last opened workspace rather than the workspace the app entry is dragged into, and appears to be the only installed GTK app other than Tube Converter to exhibit this issue, which is interesting.
Screencast from 2023-02-05 14-53-19.webm

Interesting... I will look if something in our code messes up something in GTK so it forces the compositor to open the window in wrong workspace.

This could be because of the fact that the application is running in dotnet and then dotnet spawns the gtk application, causing it to just be in the focused workspace as opposed to one you dragged it too.

There might be nothing we can do about this. Best thing to do is open Denaro and then move it to your prefered workspace after.

Ah wait, you say Tube Converter doesn't work correctly either?

This could be because of the fact that the application is running in dotnet and then dotnet spawns the gtk application, causing it to just be in the focused workspace as opposed to one you dragged it too.

I don't think dotnet has anything to do with GUI. It's either GTK or gir.core. And since it also happens with TubeConverter (and Tagger, I just tested), it's not gir.core. So we messed something up in how application starts.

It's just adw_application_new() 🙃 the same way all other apps do it haha

https://github.com/nlogozzo/NickvisionMoney/releases/tag/2023.2.0-rc1-f1


[Content]:

What article on segment.com/docs is affected?
https://segment.com/docs/connections/destinations/catalog/actions-salesforce/
What part(s) of the article would you like to see updated?
For multiple mappings, it states "__ is a Cloud action. The default Trigger is:" but then nothing is not listed.
This is missing for Custom Object, Contact, Opportunity, Case
For reference of what it's supposed to look like, check out  Account action, it has default trigger is type = group.
Additional information
No response

Thanks @lizkane-twilio. These Actions don't have a default trigger, which I didn't know was possible. I will update the template to prevent the text from showing.


update readme regarding demand equation

Update the README:
Make it clear to the user that the demand_eq should have the same time step length as the dt that they defined in the simulation control. Default dt is month-long and so, default demand_eq will also be a month.

#96 closes this issue


ROX-15799: Workload CVE - Add table filters and sync them w global/default filters

Adding table filters for the Workload CVE table in the Overview page. The dropdown filters should all work with the existing global filters, but the autocomplete input will be added in a separate PR. The chips/filters should look like below and update when default/local filters are changed. The state should all be stored in the URL.

good points. i am planning on sending a separate PR for the resource dropdown/autocomplete select, so maybe we can push this in if the other parts are okay?

Yeah that works for me. I was going to comment on these sections that use s[resource]= as part of a URL parameter and suggest we should just do s[CVE]=, s[Namespace]= etc like Severity and Fixability but wanted to get clarification on how this should work from the rest of the team first. We'll probably need to refactor those a bit but since you have subtasks for the other items no sense in holding this one up.