View history of this document

This is a question more than an issue. This document is dated 08/29/2022. How can I see previous versions of the article and what has been changed between versions?
Specifically, I'm trying to find out when the following was added.
Limitations when downloading a dataset .pbix file
Downloading a .pbix file that is larger than 1 GB isn't supported
I've downloaded reports > 1GB many times, but am having issues this week. I wanted to see if this limitation was recently added.
Thanks,
Dean

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: e091669c-6d15-1d87-9d1b-87720f50a908
Version Independent ID: 2989dde3-eef4-28ea-4eec-846efc140735
Content: Download a report from the Power BI service to Power BI Desktop - Power BI
Content Source: powerbi-docs/create-reports/service-export-to-pbix.md
Service: powerbi
Sub-service: pbi-reports-dashboards
GitHub Login: @maggiesMSFT
Microsoft Alias: maggies

Hi, @djurecic0 --

I've asked about that specific change and will let you know what I hear back.
And yes, you can see the history of any article.

How to see the history:
On this page, select the link next to Content Source: powerbi-docs/create-reports/service-export-to-pbix.md.
On that page, select History.
You see a list of Commits.
You can open each commit and see the markdown, with the old text highlighted in red, the new in green.
I opened a bunch of them. That bullet point was already there by June 7, 2022.
Hope that helps!

Hey, another writer shared with me this other view, "Blame view" (?):
https://github.com/MicrosoftDocs/powerbi-docs/blame/main/powerbi-docs/create-reports/service-export-to-pbix.md
It shows that line 104 was last updated 7 months ago.
Hope that helps!

This is helpful- thank you!
From: Maggie Sparkman @.>
Sent: Wednesday, September 7, 2022 7:04 PM
To: MicrosoftDocs/powerbi-docs @.>
Cc: Dean Jurecic @.>; Mention @.>
Subject: Re: [MicrosoftDocs/powerbi-docs] View history of this document (Issue #4041)
Hey, another writer shared with me this other view, "Blame view" (?):
https://github.com/MicrosoftDocs/powerbi-docs/blame/main/powerbi-docs/create-reports/service-export-to-pbix.md
It shows that line 104 was last updated 7 months ago.
Hope that helps!
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/powerbi-docs/issues/4041#issuecomment-1239994037, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASH4QTNDOWQ6UL7LTLSHWQ3V5ENPBANCNFSM6AAAAAAQHBGGMU.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@djurecic0 -- thanks for asking. I learned something new, too!

Thank you!!
From: Maggie Sparkman @.>
Sent: Wednesday, September 7, 2022 4:35 PM
To: MicrosoftDocs/powerbi-docs @.>
Cc: Dean Jurecic @.>; Mention @.>
Subject: Re: [MicrosoftDocs/powerbi-docs] View history of this document (Issue #4041)
Hi, @djurecic0https://github.com/djurecic0 --

I've asked about that specific change and will let you know what I hear back.
And yes, you can see the history of any article.

How to see the history:
On this page, select the link next to Content Source: powerbi-docs/create-reports/service-export-to-pbix.mdhttps://github.com/MicrosoftDocs/powerbi-docs/blob/main/powerbi-docs/create-reports/service-export-to-pbix.md.
On that page, select History.
You see a list of Commits.
You can open each commit and see the markdown, with the old text highlighted in red, the new in green.
I opened a bunch of them. That bullet point was already there by June 7, 2022.
Hope that helps!
—
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/powerbi-docs/issues/4041#issuecomment-1239843087, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASH4QTPGN2JM2NDUV52Q5E3V5D36NANCNFSM6AAAAAAQHBGGMU.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>


Solve ModuleNotFoundError error

When running the CLI I get this error:
Traceback (most recent call last):
File "scripts/run.py", line 10, in
from daedalus.VphSpenserPipeline.RunPipeline import RunPipeline
ModuleNotFoundError: No module named 'daedalus.VphSpenserPipeline'

Solved this by installing wiht pip install -v -e .


Improve lists in Java Plugin chapter

I've implemented some stylistic changes to lists of tasks and properties in the Java Plugin chapter so that they are a bit easier to digest for readers and are consistent with other recently-changed chapters.
The two big changes are:

Removal of italicisation for first sentences of descriptions. It doesn't aid readability and is somewhat distracting. In addition, many descriptions are only one sentence anyway!

Change to layout of lists of properties so that the property names are more prominent and easier to scan through for readers.

@marcphilipp Would you mind checking the latest commit when you have a moment?

@pledbrook Please rebase this PR onto master as there seems to be a conflict.

Should be good to go now.


Least Squares Optimization Fails for x0 << 1.0.

The scipy.optimize.least_squares fails to minimize a well behaved function when given starting values much less than 1.0.  In particular, I'm considering the function f(x) = x - 3.0.  If x0 = 0.0 it optimizes well, but x0 = 1e-9 (or anything smaller but non-zero) it doesn't move.
The root cause seems to be a numerical issues in the underlying MINPACK Fortran code.  When calculating the Jacobian it uses a step size h, where h = abs(x0) * eps, and eps is related to machine precision, in this case about 1.5e-8.  For small h, h * eps ends up very small.  The difference between x0 and x0 + h  gets truncated after subtracting 3.0, so f(x) and f(x +h) are equal, the Jacobian is zero, and the optimization doesn't move.
Reproducing code example:
from scipy.optimize import least_squares

X_GOAL = 3.0

def myfunc(x):
    return x - X_GOAL

for x0 in [0.0, 1e-9]:
    res = least_squares(myfunc, x0, method='lm', verbose=2)
    x_opt = res['x']
    print("x0:", x0, "x_opt:", x_opt, "x_error", x_opt - X_GOAL)

This will show an error of zero for x0 = 0.0, and an error of 3.0 for x0 = 1e-9.  This seems like undesirable behavior, and is causing problems for me in a more complicated real-life example.
I haven't been able to find any settings that resolve this issues.  Using a very large diff_step should get the first iteration to move, but that value will be far too large as soon as x is not very small.
I took a look at the Fortran code, and there are two places where there's a check for a value being exactly zero then sets it to some value.  Changing these to saturate at the specified value resolves this particular issue for me.  Saturation at small values is also the approach taken in approx_derivative in scipy/optimize/_numdiff.py, where the absolute step size is calculated as rel_step * sign_x0 * np.maximum(1.0, np.abs(x0)) (in _compute_absolute_step).
The behavior with these changes seems more desirable than the current behavior, but changing historic behavior seems a bit concerning.
Here are the specific changes:
scipy/scipy/optimize/minpack/fdjac2.f, line 94
- if (h .eq. zero) h = eps
+ h = dmax1(h, eps)

scipy/optimize/minpack/lmder.f, line 272
- if (delta .eq. zero) delta = factor
+ delta = dmax1(delta, factor)

With these two changes all the unit tests pass, except for  test_diff_step in scipy/optimize/tests/test_least_squares.py, which requires a much smaller diff_step to behave properly.  This is using the 'lm' solver. I believe the 'trf' and 'dogbox' methods utilize different code but exhibit the same behavior.
Scipy/Numpy/Python version information:
1.3.1 1.17.0
sys.version_info(major=3, minor=5, micro=2, releaselevel='final', serial=0)

@nmayorov, I think you'd be best placed to answer this. I'd be for improved behaviour in this circumstance, I'm not so sure exact (bitwise) back compatibility is as important.

I will investigate it.

This behavior is not due to numerical differentiation, the Jacobian is estimated correctly as 1.
All optimization methods in least_squares are trust-region methods. At the beginning the initial radius of the trust region is selected as
    Delta = norm(x0 * scale_inv)
    if Delta == 0:
        Delta = 1.0

By default scale_inv is 1. So the idea behind this is to use x0 as the scale of how much variables might change during the optimization process. If x0 = 1000 then we expect it to change within 1000 approximately. This makes sense for sure.
So when you set x0=1e-9 the algorithm assumes that your variables needs to be optimized within this range. The first step is 1e-9 and the cost function change is sufficiently small for algorithm to terminate.
I'd put this behavior into poor starting point selection category. I guess it can be fixed (sort of), but I don't see it improving the actual quality of the solver. That is real issues on hard problems are not related to this little quirk at all.

@nmayorov Thanks for taking a look at this.
I'm looking at the  Levenberg-Marquardt method, and it doesn't appear that Jacobian in correctly estimated.  If I print out fjac(i,j) (in scipy/optimize/minpack/fdjac2.f near line 100), I get zero.  The calculation of delta in scipy/optimize/minpack/lmdif.f is also a problem, but only after I modify the Jacobian calculation.
I hear what you're saying about poor starting point selection, but that doesn't help in the actual problem I have.  I'm optimizing a function that changes somewhat, using the optimal state from the previous step as the starting point of the next optimization, so I don't have much control over the starting state.  Sometimes the optimum is actually zero, so the approximately optimal solution ends up very small, which is then used in the next step, and the optimization gets stuck.  I can put in a hack where I check for the  optimization not moving along with near zero start state, then manually reset the start state to exactly zero and re-optimize, but this isn't ideal.  Any suggestions would be welcome.
It also seems like there's potential to mess up optimization problems that don't start with very small values of x0.  With each iteration of the linear problem there's a new x0 produced by the previous linear problem, right?  If this x0 happens to be near zero, couldn't the optimization stop prematurely?
I believe that my suggestion of lower-bounding both h and delta would fix the problem with small starting state when the optimal state is not small, and that the trade-off would be lower precision for problems in which the state being optimized is very small.  However, optimizing a problem where the state is in the range of, say, 1e-6, isn't really best practices anyway, and I believe there'd be no drawback from problems which are appropriately normalized.

OK, let's try to figure out what is going on and what can be changed.

I'm looking at the Levenberg-Marquardt method, and it doesn't appear that Jacobian in correctly estimated. If I print out fjac(i,j) (in scipy/optimize/minpack/fdjac2.f near line 100), I get zero. The calculation of delta in scipy/optimize/minpack/lmdif.f is also a problem, but only after I modify the Jacobian calculation.

The code which selects the perturbations step size in MINPACK (you have probably seen it):
         temp = x(j)
         h = eps*dabs(temp)
         if (h .eq. zero) h = eps

So for x0 = 1e-9 we get h ~ 1e-25 and fun(x0 + h) - fun(x0) = 0. This again conceptually explained by a poor initial point selection. In approx_derivative we have h = max(1, abs(x0)) * eps so this part sort of works.
But there is no perfect or right solution for numerical differentiation. So I'm overall against changing this part (or anything at all) in MINPACK, because it doesn't fundamentally improve it and it's better to keep the canonical Fortran implementation.

I'm optimizing a function that changes somewhat, using the optimal state from the previous step as the starting point of the next optimization, so I don't have much control over the starting state. Sometimes the optimum is actually zero, so the approximately optimal solution ends up very small, which is then used in the next step, and the optimization gets stuck. I can put in a hack where I check for the optimization not moving along with near zero start state, then manually reset the start state to exactly zero and re-optimize, but this isn't ideal. Any suggestions would be welcome.

But it still looks to me as a poor initial point selection. This basic "continuation" strategy is generally good, but doesn't always work, as you say. You may somehow adjust it, i.e. move start point to 1 (or other appropriate value corresponding to scale of your variables) if it's close to 0.

It also seems like there's potential to mess up optimization problems that don't start with very small values of x0. With each iteration of the linear problem there's a new x0 produced by the previous linear problem, right? If this x0 happens to be near zero, couldn't the optimization stop prematurely?

Sorry, but didn't catch the idea here. Could you rephrase or clarify?

I believe that my suggestion of lower-bounding both h and delta would fix the problem with small starting state when the optimal state is not small, and that the trade-off would be lower precision for problems in which the state being optimized is very small. However, optimizing a problem where the state is in the range of, say, 1e-6, isn't really best practices anyway, and I believe there'd be no drawback from problems which are appropriately normalized.

In trf and dogbox we have h lower-bounded, in MINPACK, as I said, I'm hesitant to change it.
For delta --- I believe lower-bounding it is not a great idea, however providing an arguments to control its initial values is a decent idea.
MINPACK supports it in the form
factor: float, optional
  A parameter determining the initial step bound (factor * || diag * x||). Should be in interval (0.1,
  100).

For new methods I'd simplify this logic to directly setting the initial radius of trust regions (I believe this is the approach in ceres-solver C++ library).
Another option I have in mind is to require that the trust regions doesn't restrict the step in order to declare the convergence by ftol or xtol. I think it is worth checking.

Sorry, but didn't catch the idea here. Could you rephrase or clarify?

My thought here is that the optimization could accidentally land on an intermediate state that is small, leading to small delta and h, which could cause premature stopping.  Say we're solving a problem where the optimum is at  x =1.0, and we start at x = -1.0.  In the first step we calculate the Jacobian and take a step of, say 1.0 + 1e-16  In the next iteration x  is now 1e-16.  This then runs into the same problem I'm seeing, where the small starting state results in very small delta and h, causing the optimization to terminate at 1e-16 rather than near 1.0.  I believe this premature stopping is possible even if the starting state, optimal state, and function are all on the order of 1.0.
It also seems strange to me to have discontinuous behavior at x0 = 0.0.  As noted above, approx_derivative in scipy/optimize/_numdiff.py scales the finite difference step size with max(abs(x0), 1.0) which makes more sense to me.
It seems to me that the current behavior could also result in a problem somewhat opposite to the one I'm having.  If I have a problem whose state is order 1e-9 then starting with x0 = 0.0 (which seems pretty natural) would result in both delta and h being too large, but starting with x0 = 1e-13 would work well.  This seems pretty intuitive to me.  And if you are looking to optimize problems with very small state, it seems like rescaling the problem to be order 1.0 would be a better approach than choosing small (but not exactly 0.0) starting state.
I like the idea of using xtol and/or ftol as a guide, either to prevent termination or to set a floor on the size of the trust region and finite difference step.  I'm not seeing an obvious way to do this without modifying the Fortran code, but I'm also having a little troubles following that code.  I'd also be fine with a manual setting to lower bound both delta and h, but I'm not seeing a way to do that either.

I'm not seeing an approach that would fix my particular issue without modifying the original fortran code.  The numeric derivatives in the LM solver are evaluating to zero (due to very small h while the functions output is on the order of 1), and there doesn't appear to be a way to set a floor on the size of h, other than using exactly zero, which the LM solver treats as if it were order 1.  I have a hack where I check my initial state and set any elements that are smaller than some threshold to exactly zero.  It's a bit unsatisfactory, but seems to work, so I think I'll go with that for now.  Thanks for the help.

@tomfallen
Feel free to report other issues or reopen this. Closing for now.


feature: ipfs.files.exists

Following proposal on https://github.com/ipfs/js-ipfs/issues/780 by @aphelionz, we would have:

A files.exists might be indeed useful, but also misleading, it should include options for:

local
check only root (avoid recursively checking all the leafs)

Thanks @diasdavid

I am not sure if it is needed in the files namespace as you can pull out the hash of the file using files.stat and then use generic command to check of availability.
The command for checking that doesn't exist currently and doing it outside of files command-space would be more generic approach.

I don't think we should do this for similar reasons to why fs.exists is deprecated in node core:

Using fs.exists() to check for the existence of a file before calling fs.open(), fs.readFile() or fs.writeFile() is not recommended. Doing so introduces a race condition, since other processes may change the file's state between the two calls. Instead, user code should open/read/write the file directly and handle the error raised if the file does not exist.

A user can simulate it with ipfs.files.stat(pathOrCID) but we should not encourage it's use.


I2C master and slave examples on the FTH board

Hello,
As a warming exercise for my I2C 10-bit addressing project I have been testing the master and slave examples on the Feather board and I run into an issue I would like to report.
I have tested the master example (MAX78000_SDK/Examples/MAX78000/FTH_I2C) and it works as expected. I only find this comment at the beginning of the main.c file a bit odd:
* @details     This example uses the I2C Master to read/write from/to the I2C Slave. For
 *              this example you must connect P0.10 to P0.16 (SCL) and P0.11 to P0.17 (SCL). The Master
 *              will use P0.10 and P0.11. The Slave will use P0.16 and P0.17. You must also
 *              connect the pull-up jumpers (JP21 and JP22) to the proper I/O voltage.
 */

I guess this comment was written early in the development and the layout of the board was different, but in my kit, those connections are already made in the board and I don't have any pull-up jumpers (R15 is populated with a zero ohm resistor so the bus works at 3.3V). Maybe that should be removed to avoid confusion.
I have also tried to adapt the master-slave example (MAX78000_SDK/Examples/MAX78000/I2C) to work as a slave only on the feather board removing the master parts and changing the slave to MXC_I2C1 and the interrupt vectors.
Although I'm able to compile and run the code, the behavior is not as expected. When I connect the feather board slave to a master and run i2c-detect to discover the slaves on the bus, the master reports addresses 0x18 and 0x28 which are the PMIC and audio codec on the board but the new slave I'm defining is nowhere to be found and I'm getting a lot of timeouts (the prompt once I run i2c-detect takes quite a lot to complete and I get timeout messages all over the place).
I have tried with a Raspberry Pi and a Beagle Bone Black acting as master with the same results. At first, I thought the issue was coming from the bus load/termination but I have tested several configurations with no luck.
I would be very glad to know if somebody has been able to run the FTH board as an I2C slave. I'm probably missing changing some registers or any other detail, I did not have time to look at the low-level documentation yet (I will as soon as I have the time).
One last thing I forgot to mention is that in all these tests I'm just dealing with 7-bit addresses, so no funny stuff whatsoever.
Thank you again for your help.
EDIT: Indeed my problem was in the code: I was not calling MXC_I2C_SlaveTransactionAsync(). Now the slave is detected at the address I set it up with. I'm still trying to figure out where I'm supposed to call MXC_I2C_AsyncHandler() within the ISR for the slave to keep sending data continuously (to implement a kind of a 100 byte EEPROM emulator that can be read with i2cdump).
A complete slave example similar to the master would be really nice to have. I'm keeping the issue open, I hope that's not a problem.
Regards,
Marcos

Resolved as of https://github.com/Analog-Devices-MSDK/msdk/pull/330 - the EEPROM_Emulator better demonstrates how to set the MAX78000 up as an I2C slave for this use-case


Check if changes are reflected on server after upload

Gives an illusion of successful upload/changes/write on the remote server when it actually failed doing so.
Steps to reproduce the bug

Create a file /home/username/testfile.txt on remote sftp server with a user username and allow only read permission to it.
Setup .ftpconfig to use user username with required credentials to access /home/username/testfile.txt
Connect to the server download the file /home/username/testfile.txt for editing.
Edit the file and upload/save the changes.

Possible remedy
Compare md5/sha signatures of local and remote file, to make sure the upload went successfully otherwise prompt the user with a failure message.

There is a planned feature that will address this problem. Detailed in the comments here: #20


Run streamlit with XLinear

Did some progress testing this. Was able to re-direct the app from EC2 into my local machine. For this, you need to run docker with export STREAMLIT_SERVER_PORT=8888, then running docker with
It would be good to create a .dockerignore file (I did it myself locally, otherwise the context would be massive)

data
.dvc
venv

from #90 @aCampello
Opening this issue to resolve separately

This work by running on AWS using a tunnel. If you have time add it in the README @aCampello but closing for now


Calling unregisterModule does not remove unregistered module's state from localStorage

Hello,
I am new to Vuex, so apologies if I am overlooking something obvious.  I have a question about the behaviour of this package...
In my app, when a user logs in, I use registerModule to attach the appropriate modules for that user to the vuex store.  When they logout, I use unregisterModule on those same modules.
It appears that calling unregisterModule, while it removes the module from my store, does not actually remove the module's data from the localStorage created by vuex-persistedstate.  So if I click refresh, suddenly that module's state reappears in my store, even though the module is no longer a part of the store.
For example:
registerModule('profile', profile)
--> state: { profile: {...}}
unregisterModule('profile')
--> state: {}
However, after a refresh, state once again looks like:
state: { profile: {...}}
I guess I could call a reset mutation on the profile module before unregistering it, but even then, on a refresh, I would still have an empty profile object in my state.  I would prefer for 'profile' to be gone from localStorage entirely, since it has been removed from the store.
Any advice on how to accomplish this?  Thanks (in advance) for your input!

Oh hey, I figured it out. Looks like calling unregisterModule doesn't trigger an update in Vuex. So if the first thing you do is click refresh after calling unregisterModule, then the state from that module will be restored. However, if you commit a mutation immediately after unregistering...
unregisterModule('profile')
store.dispatch('anycommit')
...and then click refresh, it behaves as expected. So that's an easy workaround. (Not sure if there is a way to trigger an update event without committing a mutation...)

Looks like Vuex doesn't dispatch a mutation that clears out the module's state then. I would suggest dispatching a custom action which clears out the module's state before unregistering the module. This way it doesn't appear again after reloading the localstorage.


[CT Metrics] Needs test suite file name corrections

There is one field which is derived from the test suite name to assign fun_area.
So this requires some of the file name to align to functional area..

This code s in review


Bump lerna to 8.1.3, ejs to 3.1.10

This PR looks like just updating lerna version but it does not such simple.
Steps to reproduce this change

Check out main branch
Delete the root package-lock.json and node_modules.
Run npm cache clean -f
Update the root package.json like below then run npm i

Update lerna version to "8.1.3"
Update nx version to 19.0.1
Add the following section to package.json.

"overrides": {
  "@walletconnect/keyvaluestorage": "1.0.2",
  "tslib": "2.6.2"
},

Why such complicated?
My environment: m1 Mac 14.3.1, NodeJS 18.20.3, npm 10.8.0
At first I just incremented lerna version to 8.1.3. From that point, npm run build keeps failing with the strange message

After some investigation, I found that the version of node_modules/tar/node_modules/minipass was incorrectly set to 3.3.6 where tar specifies the version  to ^5.0.0.

I suspect that with workspace and multiple child package dependencies, npm was confused and set wrong versions when creating package-lock.json.
Failed challenge
Challenge 1

check out main
Delete the root node_modules
Set "lerna": "8.1.3," to the root package.json`
Run npm i
Run npm run build <-- This fails
Run npx lerna run dev:skipLocales --scope=@chia-network/gui to start GUI <-- GUI crashes

Challenge 2

check out main
Delete the root node_modules and package-lock.json
In the root package.json,  set "lerna": "8.1.3", remove "nx": "16.7.2"`
Run npm i
Run npm run build <-- This succeeds
Run npx lerna run dev:skipLocales --scope=@chia-network/gui to start GUI <-- GUI crashes with an error (0 , tslib__WEBPACK_IMPORTED_MODULE_4__.__spreadArray) is not a function

Lessons learned

Even if the content of package.json is the same, the content of package-lock.json differs according to previous package-lock.json and node_modules content.
lerna depends on nx and nx has several optional dependencies for various OSes. This messes up package-lock.json. When I removed nx from top-level dependencies in the root package.json and ran npm i, it generated package-lock.json which specifies one of the optional dependencies only for MacOS.  Of cource, this package-lock.json fails except for macOS.

I tested the following items and confirmed all ok.

npm i
npm run build
npx lerna run dev:skipLocales --scope=@chia-network/gui (Launch GUI)
Connect sample dApp with walletconnect, tested some APIs then disconnect.


Add unitconverter and geometry preview window

Purpose
Add unit converter under datagrid;
Send geometry objects to a preivew window;
Use new icon;
Description
There is a unit conveter bar under datagrid.It will converter some object to meter such as XYZ.
If you click the icon, it will open a tool window so that user can input values.

When user snooping a geometry object, it will disapear a icon int object tree node.If user clicked this icon, a 3d preview window will be opened.
Support objects:

GeometryInstance
Solid
Face
Edge
Line
Curve
BoundingBoxXYZ

Declarations
Check these if you believe they are true

[ ] This PR fix bug
[x] This PR for new feature
[ ] The codebase is in a better state after this PR
[ ] The level of testing this PR includes is appropriate
[ ] User facing strings, if any, are extracted into *.resx files
[x] Snapshot of UI changes, if any.
[ ] This PR modifies some build requirements and the readme is updated

Reviewers
@chuongmep
Sorry that i made so many things in a pr.

@weianweigan Can 3D preview support for geometry in Dynamo Revit like surface, curve, line,..?

Thanks for your reply.
I think that it's possible to support geometry object in dynamo revit, but i found Watch3D node can preview geometry object in dynamo.Is there any other advantage that preview dynamo geometry object in another preview window ?

@weianweigan I just question to write feature and limit or feature in README, I believe that we don't need to develop this in Dynamo Revit.

@chuongmep Yes，I agree with you!🥮🥮🥮

@chuongmep I get it.It can not  preview dynamo geometry objects.

@chuongmep I get it.It can not preview dynamo geometry objects.
@weianweigan do you need to add this feature in this pull request ?

@chuongmep I don't need add this feature in this pr.I don't have any idea about how to implement it now.


feat(API): Implement key-related composite event HOCs

Implemented withKeyRemainDown & withKeyRemainUp

Coverage remained the same at 100.0% when pulling 276931a137606d50da9c97ac9056528eb3ec6cc4 on key into 104b969361643eb29b7ba3be4cd9e844d644fc34 on master.

Coverage remained the same at 100.0% when pulling 55a87400959edf29925eabd96399c6173efd1894 on key into 104b969361643eb29b7ba3be4cd9e844d644fc34 on master.

Coverage remained the same at 100.0% when pulling 5df58b3cab5f0df43f9b0ba3a8addedfc167d88f on key into 846300e3db43028368b8fd20316d299c315e2431 on master.

Coverage remained the same at 100.0% when pulling 5df58b3cab5f0df43f9b0ba3a8addedfc167d88f on key into 846300e3db43028368b8fd20316d299c315e2431 on master.


removing circular dependecies created new error

I'm just playing with the nuimo, and your library is great. Got it working in literally minutes. However, in trying interaction.js example, I run into the following:
/etc/nodejs/apps/nuimo/node_modules/nuimojs/src/device.js:180
case (Nuimo.Direction.LEFT):
^
TypeError: Cannot read property 'LEFT' of undefined
at Device._handleSwipe (/etc/nodejs/apps/nuimo/node_modules/nuimojs/src/device.js:180:34)
at Characteristic.characteristic.on (/etc/nodejs/apps/nuimo/node_modules/nuimojs/src/device.js:156:13)
at emitTwo (events.js:106:13)
at Characteristic.emit (events.js:191:7)
at Noble.onRead (/etc/nodejs/apps/nuimo/node_modules/noble/lib/noble.js:275:20)
at emitMany (events.js:127:13)
at emit (events.js:201:7)
at NobleBindings.onNotification (/etc/nodejs/apps/nuimo/node_modules/noble/lib/hci-socket/bindings.js:399:8)
at emitMany (events.js:127:13)
at emit (events.js:201:7)
As you remeoved the circular dependency, now the constant is in service.js, and no longer referenced from nuimo.js, so it is now no longer Nuimo.Direction.xxx, but just Direction.xxx. I changed appropriately.

Fixed with #7 (#4 broke an example). Thanks!


Convert fisheye image to an equirectangular image

Hi, this is a very useful lib for double sphere camera model.
I noticed that when the algorithm coverts fisheye image to equirectangular image, it first calculate the 3D points maps to image plane. I really interested about this method, can you provide some theoretical basis for this method?
Besides, is this process reversible? If I transform the equirectangular image to fisheye image, is the fisheye image same as the original fisheye image?

Thanks for your answer. I checked the equirectangular projection in Wikipedia and double sphere camera model, and your solution with double sphere camera really helps to transform the fisheye image.
Recently, I try to do the plane sweeping algorithm in fisheye image. I saw your papers about Octave Deep Plane-sweeping Network and 360° Depth Estimation from Multiple Fisheye Images. These are very impressive works on fisheye depth estimation.
The results I got from plane sweeping algorithm on fisheye images has lots of artifacts. The result depth maps were not as continuous as expected. As you have down great jobs on fisheye images and depth estimation, do you have any advice on plane sweeping algorithm?
I really appreciate your attention, thank you!

I'm glad that you saw my papers. I can't tell you anything without enough information, but regularization of cost volume might be important in some cases to decrease artifacts.
Thanks,

Closing now. Let me know if you have additional questions.


Make test suite generate files outside of the source tree

Description
The tests seem to generate directories in the source tree names tmp-* and they also seem to generate files under test/media and possibly test in general.
It would be nice if that as reworked so all that happened under /tmp.
Code of Conduct

[X] I agree to follow the IETF's Code of Conduct

or at least outside /workspace. /tmp brings its own dragons, as we saw with the html validation code.


How to get correct response from the api method?

I attempted dialogue integration using the following code. However, I examined the results,
and the response received is not coming from the server.
In theory, the server should return the following JSON:
{   "choices": [     {       "index": 0,       "message": {         "role": "assistant",         "content": "Hello! How can I assist you today as a policy consulting expert for corporate parks?"       },       "finish_reason": "stop"     }   ],   "usage": {     "prompt_tokens": 93,     "completion_tokens": 17,     "total_tokens": 110   } }
my deep-chat:
`<deep-chat
id="chat-element"
demo="true"
style=" border-radius: 10px;
height: calc(95vh - 5.5rem);;
width: 600px;
border: 1px solid rgb(202, 202, 202);
font-family: Inter, sans-serif, Avenir, Helvetica, Arial;
font-size: 1.2rem;
background-color: white;
position: relative;"
:request='{
"url": "https://xxx.chat/v1/chat/completions",
"headers": {
"Content-Type": "application/json",
"Authorization": "Bearer LixxxtO7"
}
}'
:requestInterceptor="(request) => {
// request.body = {prompt: request.body.messages[0].text};
request.body = { app_code: 'pKxxxxjc5',
messages: [
{
role: 'user',
content: request.body.messages[0].text
},
]
};
return request;
}"
:responseInterceptor="(response) => {
        // const responseText = // extract it from the response argument
        return {result: {text: response.detail}}
}"

`

Hi @guinanlin, thankyou for raising an issue.
Based on the example response JSON from the server you have provided, the interceptor should be as follows:
Your JSON:
{
  "choices": [
    {
      "index": 0,
      "message": {
        "role": "assistant",
        "content": "Hello! How can I assist you today as a policy consulting expert for corporate parks?"
      },
      "finish_reason": "stop"
    }
  ],
  "usage": {
    "prompt_tokens": 93,
    "completion_tokens": 17,
    "total_tokens": 110
  }
}

responseInterceptor code (tailored for Vue):
:responseInterceptor="
      (response) => {
        return { text: response.choices[0].message.content };
      }"

"It's still not working; I don't know how the result of this 'response' is generated. However, when I make a call using a tool similar to Postman, the call works fine.
I've even traced the breakpoints, and they enter the requestInterceptor and responseInterceptor as expected. The value of request.body is correct, but the result of the response is incorrect.
I'm using 'deep-chat': '^1.3.19'."

the correct result should be as following :

following is my core code:

Ok, I understand the problem now. It appears Deep Chat is sending an incorrect request to your server. Let me experiment a little bit to see if I can identify the exact cause for this.

Can you try to remove the Content-Type:  "application/json" property from the request headers and tell me if anything changes.

I identified a bug in the component, let me try to fix it now.

remove content-type:

Can you try to remove the Content-Type: "application/json" property from the request headers and tell me if anything changes.

I wirte a js function to get the reuslt:
    async getOpenAIResult(query) {
      // 检查 initialize 是否已经完成，如果未完成，等待它完成
      if (!this.frappe) {
        await this.initialize();
      }

      return new Promise((resolve, reject) => {
        const url = 'https://axxxxxcompletions';
        const headers = {
          'Content-Type': 'application/json',
          'Authorization': "Bearer Link_xxxxxxx9uzD0tO7",
        };

        const requestBody = JSON.stringify(query);

        console.log("requestbody content:",requestBody);

        fetch(url, {
          method: 'POST',
          headers: headers,
          body: requestBody
        })
        .then(response => {
          if (!response.ok) {
            throw new Error('Network response was not ok');
          }
          return response.json();
        })
        .then(data => {
          resolve(data);
        })
        .catch(error => {
          reject(error);
        });
      });
    }

call in onMounted:
onMounted(()=>{
    const query = {
        "app_code": "pxxxxxjc5",
        "messages": [
            {
            "role": "user",
            "content": "Hello"
            },
        ]
    }
    frappeService.getOpenAIResult(query).then((data) => {
        console.log('result:',data);
    });
});

I will get the correct response:

There was a bug introduced in the last release, I have updated the code in version 1.3.20. Can you try it and see if it works for you? Thanks!

That is quite strange, I have tested the new version and it appears to be sending the messages correctly. Are you 100% sure that your are using the new version after doing npm install?

Can you try the following configuration and see if it works - you will need to replace the your-api-key-here with your bearer key:
<deep-chat
    :request="{
      url: 'https://api.openai.com/v1/chat/completions',
      headers: {
        Authorization: 'Bearer your-api-key-here',
      },
    }"
    :requestInterceptor="
      (request) => {
        request.body = {
          messages: [{ role: 'user', content: request.body.messages[0].text }],
          model: 'gpt-3.5-turbo',
        };
        return request;
      }
    "
    :responseInterceptor="
      (response) => {
        return { text: response.choices[0].message.content };
      }
    "
  />

Here is a link to a live CodeSandbox
If this configuration works in your app and you get successful response, but the configuration to connect to your service is still not working then there is still a problem with something else.
If this configuration is not working in your app, then you are not using the latest version (1.3.20) of Deep Chat.
Let me know how it goes for you and I will continue to help!

via your code to test OpenAI interface, In my env will ocurrs the same errors:

the response error:
{
"message": "you must provide a model parameter",
"type": "invalid_request_error",
"param": null,
"code": null
}
but the same openai key run on the codesanbox works well.
My god, it's so strange.

If the exact same code from the sandbox doesn't work in your local application then I would assume your app is running the 1.3.19 version instead.
Can you try delete the package-lock.json file and node_modules folder, and do npm install again to see if it works.

Also, if you are able to inspect the Deep Chat code in your console, can you check the baseServiceIO.ts file. It should have the following await and return statements highlighted in red which I added in version 1.3.20.

If the exact same code from the sandbox doesn't work in your local application then I would assume your app is running the 1.3.19 version instead.
But this thing is really weird. I tried to adjust the sandbox package and vue version to be the same as mine. The sandbox runs very well. But in my environment, it cannot run. Here is the package of my environment. Also send the conf.
{
    "name": "t-vue",
    "version": "3.7.0",
    "scripts": {
        "dev": "vite",
        "build": "vite build",
        "preview": "vite preview",
        "lint": "eslint . --ext .vue,.js,.jsx,.cjs,.mjs --fix --ignore-path .gitignore"
    },
    "dependencies": {
        "axios": "^1.4.0",
        "chart.js": "3.3.2",
        "deep-chat": "1.3.19",
        "exceljs": "4.3.0",
        "file-saver": "2.0.5",
        "frappe-js-sdk": "^1.2.4",
        "ip": "^1.1.8",
        "luckyexcel": "1.0.1",
        "primeflex": "^3.2.1",
        "primeicons": "^6.0.1",
        "primevue": "3.28.0",
        "vee-validate": "4.9.6",
        "vue": "^3.2.41",
        "vue-router": "^4.1.5",
        "vxe-table": "^4.4.2",
        "xe-utils": "^3.5.11",
        "yup": "^1.3.2"
    },
    "devDependencies": {
        "@rushstack/eslint-patch": "^1.1.4",
        "@vitejs/plugin-vue": "^4.1.0",
        "@vue/eslint-config-prettier": "^7.0.0",
        "eslint": "^8.22.0",
        "eslint-plugin-vue": "^9.3.0",
        "prettier": "^2.7.1",
        "sass": "^1.55.0",
        "vite": "^4.2.1"
    },
    "main": "index.js",
    "repository": "https://xxxxxx.git",
    "author": "xxxxx",
    "license": "MIT"
}

and then I  try my API to run on the sandbox, it also run well. so , it relate to my envoirment.
It should be caused by some packages interacting with each other.

It is very likely that this is caused by something else in your environment. I have updated the latest version to 1.3.21 as 1.3.20 had a few console logs that I forgot to remove.
Can you use 1.3.21, run npm install and in the package-lock.json file do you have the following?
    "node_modules/deep-chat": {
      "version": "1.3.21",
      "resolved": "https://registry.npmjs.org/deep-chat/-/deep-chat-1.3.21.tgz",
      "integrity": "sha512-WEWCLj0g1MAnkSLbFJniILragjRjXppJ5zqNTb6A9vCC87v5ySXM9R4X1POiDZ6Q13uQuhwOwBpOUgUENcNt2w==",
      "dependencies": {
        "@microsoft/fetch-event-source": "^2.0.1",
        "remarkable": "^2.0.1",
        "speech-to-element": "^0.1.66"
      }
    },

and
    "deep-chat": {
      "version": "1.3.21",
      "resolved": "https://registry.npmjs.org/deep-chat/-/deep-chat-1.3.21.tgz",
      "integrity": "sha512-WEWCLj0g1MAnkSLbFJniILragjRjXppJ5zqNTb6A9vCC87v5ySXM9R4X1POiDZ6Q13uQuhwOwBpOUgUENcNt2w==",
      "requires": {
        "@microsoft/fetch-event-source": "^2.0.1",
        "remarkable": "^2.0.1",
        "speech-to-element": "^0.1.66"
      }
    },

yeah,  1.3.21 works well
Thank you very much for your help, I really appreciate it, it’s night in China, I wish you sweet dreams:-)

summary up the vue3 request call and share to others.
outer api call:
<deep-chat
    id="chat-element"
    style=" border-radius: 10px;
            height: calc(95vh - 5.5rem);;
            width: 600px;
            border: 1px solid rgb(202, 202, 202);
            font-family: Inter, sans-serif, Avenir, Helvetica, Arial;
            font-size: 1.2rem;
            background-color: white;
            position: relative;"

    :request="{
        url: 'https://xxxxxtions',
        method: 'POST',
        headers: {
            Authorization: 'Bearer LxxxxxuzD0tO7'
        }
    }"

    :requestInterceptor="(request) => {
        // request.body = {prompt: request.body.messages[0].text};
        request.body = { app_code: 'pKxxx5',
                         messages: [
                            {
                            role: 'user',
                            content: request.body.messages[0].text
                            },
                        ]
                        };
        return request;
    }"

    :responseInterceptor="(response) => {
            // const responseText = // extract it from the response argument
            return { text: response.choices[0].message.content };
    }"
/>

OpenAI api call:
<template>
  <deep-chat
    :request="{
      url: 'https://api.openai.com/v1/chat/completions',
      headers: {
        Authorization: 'Bearer sxxxxTgOssZ7w7',
      },
    }"
    :requestInterceptor="
      (request) => {
        request.body = {
          messages: [{ role: 'user', content: request.body.messages[0].text }],
          model: 'gpt-3.5-turbo',
        };
        return request;
      }
    "
    :responseInterceptor="
      (response) => {
        return { text: response.choices[0].message.content };
      }
    "
  />
</template>

<script>
import "deep-chat";
</script>

Good to hear @guinanlin!
I will close this issue, but if you have any other problems or questions, you can feel free to raise a new one!
晚安


Investigate logging on iOS

Create tracker with logLevel: LogLevel.VERBOSE
Run example app as is on Android
Click buttons
See errors in console as expected since the example app does not point to a configured server

If you do the same but on iOS, you get no errors in the console.

Hi @MisterJimson 👋 ,
I checked the iOS source code of this library and the log level is not set when the tracker is created. Therefore, no logging is visible in the console.
To fix this, we will have to add SPTrackerBuilder?.setLogLevel to the calls in the builder block.

Resolved in #13


Disable edit and delete for events coming from an ics feed

This would be a good way to limit permissions on who can edit what

We did this, then realized we should disable the links to the edit page from the calendar and view page altogether. Resolved in c49a7693e3adaf18c548711da29216c04ecd5942.


Add tests for trustee-operator

At least the following initial tests will be needed

operator install and uninstall
Trustee CRD creation, deletion
secret release
policy check (deny secret release due to policy deny)
policy check (allow secret release due to policy allow)
Update config, secret or policy via modifying the related K8s resources and verifying the update is reflected in the Trustee components
scaling trustee pods and verifying secret release, policy checks, config updatesetc

Some options to explore
https://github.com/confidential-containers/operator/tree/main/tests/e2e
https://kuttl.dev/docs/#pre-requisites
https://kyverno.github.io/chainsaw/latest/

Hello @bpradipt ... when referring to tests ... do you mean a GH action to perform the different proposals?
In https://github.com/latchset/tang-operator we had some tests where the operator was installed and uninstalled through operator-sdk ... is this the proposal?

@sarroutbi right. A basic test framework based on kuttl is added as part of GH action.


Feature/locale support

I need to pass the locale de_DE to AWS CLI. I added a input "locale" which can be any of the locales supported by AWS and defaults to en_US, which is also AWS' default.

Thanks! This looks great and is backwards-compatible.
What platforms have you tested this with? I ask because IIRC, locale codes differ between Android and iOS. So I'm wondering if we need to offer separate settings.

Thanks for asking! I actually did not thought of this issue before. Fortunately, the country/language codes do not need to match the system codes but are managed by AWS and are the same for Android/iOS. I pulled the codes from the "Create a new run > (4) Specify device state" screen in Device Farm.


This will define and determine the character type.

User Story:

AS AN employee with access to sensitive data
I WANT to randomly generate a password that meets certain criteria
SO THAT I can create a strong password that provides greater security

Acceptance Criteria:
GIVEN I need a new, secure password

WHEN asked for character types to include in the password
THEN I confirm whether or not to include lowercase, uppercase, numeric, and/or special characters.

Every code block related to this issue has been checked. The pull request is approved


[RDK-28710] Add OCIContainer plugin

https://jenkins.code.rdkcentral.com/job/github-triggered/2984/ started

https://jenkins.code.rdkcentral.com/job/build-component-rdk-next/19974/ started.

Smoke tests for ['build-rpi-hybrid-thunder-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/60949/

Smoke tests for ['build-rpi-hybrid-wpe-rdk-next'/'build-rpi-mc-wpe-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/60948/

Smoke tests for ['build-qemux86-hyb-rdk-next'/'build-qemux86-mc-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/60946/

Smoke tests for ['build-rpi-hybrid-refapp-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/60947/

https://jenkins.code.rdkcentral.com/job/github-triggered/3095/ started

https://jenkins.code.rdkcentral.com/job/build-component-rdk-next/20124/ started.

https://jenkins.code.rdkcentral.com/job/github-triggered/3096/ started

https://jenkins.code.rdkcentral.com/job/build-component-rdk-next/20125/ started.

Smoke tests for ['build-rpi-hybrid-refapp-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/61298/

Smoke tests for ['build-qemux86-hyb-rdk-next'/'build-qemux86-mc-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/61297/

Smoke tests for ['build-rpi-hybrid-thunder-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/61300/

Smoke tests for ['build-rpi-hybrid-wpe-rdk-next'/'build-rpi-mc-wpe-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/61299/

Smoke tests for ['build-qemux86-hyb-rdk-next'/'build-qemux86-mc-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/61301/

Smoke tests for ['build-rpi-hybrid-wpe-rdk-next'/'build-rpi-mc-wpe-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/61303/

Smoke tests for ['build-rpi-hybrid-refapp-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/61302/

Smoke tests for ['build-rpi-hybrid-thunder-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/61304/

https://jenkins.code.rdkcentral.com/job/github-triggered/3263/ started

https://jenkins.code.rdkcentral.com/job/build-component-rdk-next/20368/ started.

Smoke tests for ['build-qemux86-hyb-rdk-next'/'build-qemux86-mc-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/62030/

Smoke tests for ['build-rpi-hybrid-wpe-rdk-next'/'build-rpi-mc-wpe-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/62032/

Smoke tests for ['build-rpi-hybrid-thunder-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/62033/

Smoke tests for ['build-rpi-hybrid-refapp-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/62031/

https://jenkins.code.rdkcentral.com/job/github-triggered/3437/ started

https://jenkins.code.rdkcentral.com/job/build-component-rdk-next/20601/ started.

Smoke tests for ['build-rpi-hybrid-wpe-rdk-next'/'build-rpi-mc-wpe-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/62636/

Smoke tests for ['build-rpi-hybrid-refapp-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/62635/

Smoke tests for ['build-rpi-hybrid-thunder-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/62637/

Smoke tests for ['build-qemux86-hyb-rdk-next'/'build-qemux86-mc-rdk-next'] added.
https://jenkins.cmf.code.rdkcentral.com/job/test-components-flow/62634/

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 3 committers have signed the CLA.:x: goruklu:x: TeknoVenus:x: scthunderboltYou have signed the CLA already but the status is still pending? Let us recheck it.

OCIContainer plugin is already merged


训练出来的模型与论文结果偏差过大，mae达到了15点多，以下是我数据处理的部分

`import pandas as pd
import pickle
import numpy as np
from tqdm import tqdm
from textual_engineering import load_angle_bert_model, angle_bert_textual_feature_extraction
from visual_engineering import load_vit_model, vit_visual_feature_extraction
import os
加载 data.pkl
data_path = "/home/zhuwei/MMRA-main/data/MicroLens-100k/data.pkl"
with open(data_path, "rb") as f:
data = pickle.load(f)
加载模型
angle_model = load_angle_bert_model()
vit_processor, vit_model = load_vit_model()
提取文本特征
textual_features = []
for text in tqdm(data["text"]):  # 替换为实际的文本列名
textual_features.append(angle_bert_textual_feature_extraction(angle_model, text))
添加文本特征到 DataFrame
data["textual_feature_embedding"] = textual_features
提取视觉特征
visual_features_cls = []
visual_features_mean = []
image_base_path = "/mnt/myusb2/MicroLens-100k/videos-frame/"  # 图片所在的目录路径
零向量定义
zero_vector = [0.0] * 768  # 假设视觉特征维度为 768
for video_id in tqdm(data["item_id"]):  # 遍历视频 ID 列
video_features = []
for i in range(10):  # 每个视频有 10 张图片
image_path = f"{image_base_path}{video_id}_{i}.jpg"  # 构建图片路径
if os.path.exists(image_path):  # 检查图片文件是否存在
try:
feature = vit_visual_feature_extraction(vit_processor, vit_model, image_path)
if feature is not None:  # 检查是否成功提取特征
video_features.append(feature)
else:
video_features.append(zero_vector)  # 无效特征填充零向量
except Exception as e:
video_features.append(zero_vector)  # 如果出现错误，填充零向量
else:
video_features.append(zero_vector)  # 如果图片不存在，填充零向量
# 确保每个视频都有 10 个特征
while len(video_features) < 10:
    video_features.append(zero_vector)

# 将 10 张图片的视觉特征保存到 visual_feature_embedding_cls 列
visual_features_cls.append(video_features)
# 计算每个视频的平均视觉特征，并保存到 visual_feature_embedding_mean 列
avg_visual_features = np.mean(video_features, axis=0).tolist()
visual_features_mean.append(avg_visual_features)

添加视觉特征到 DataFrame
data["visual_feature_embedding_cls"] = visual_features_cls
data["visual_feature_embedding_mean"] = visual_features_mean
保存回 data.pkl
with open(data_path, "wb") as f:
pickle.dump(data, f)
print("特征提取完成，数据已保存！")`

Hi, Thank you for your interest in our work.
From your email, I noticed that you reported an MAE of 15 and an nMSE of 0.4. In comparison, our published results showed an MAE of 1.17 and an nMSE of 0.75. While your nMSE appears better than ours, your MAE is significantly higher. This discrepancy suggests there might be an issue with your training or testing process.
Since your shared code for data preprocessing looks correct and the key processing steps rely on the code I provided, this part should not have any major issues. I’d recommend double-checking other aspects of your pipeline, particularly:

Training/Testing Split: Ensure the data splits are consistent with those described in the paper.
Hyperparameter Settings: Verify that your hyperparameters (e.g., learning rate, epochs, batch size) match those we used in the experiments.

Hyperparameter Settings: Verify that your hyperparameters (e.g., learning rate, epochs, batch size) match those we used in the experiments.

Hope this can help you. Feel free to contact again.

It seems that you leveraged the on-screen text. However, I do not mention to use this. So I guess this may lead unpredictable result. Hope this can help you.

微信图片_20241214092813.pdf
In your paper, you did mention extracting subtitles from frames. I wonder if there is a problem with the processing method.

Hi, your understanding is wrong. In the picture you attached, the textual description is the title of the video. So no subtitles are used in our work and I also do not provide the relevant code indeed.

感谢你的回答


Remove broken link

See issue #76

Hey @kms6bn thanks — this ended up getting addressed in another Pull Request that was open, #75 . Very much appreciate the Pull Request :-)


Suppress cd output when determining src_dir

On OS X, cd can output the new directory to stdout on success.  This commit
just redirects the output of cd to /dev/null.
This fixes a problem installing multirust on OS X.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see CONTRIBUTING.md for more information.

Thanks! Do you mind adding a comment to the source indicating this is because 'cd' will something on OS X?
It's so hard to keep track of all the workarounds for platform-specific behavior in the shell :)

Comment added.  It seems to be a workaround for bash, which is used for /bin/sh on OS X.

Thanks!


glide: update lock

Lock file may be out of date. Hash check of YAML failed. You may need to run 'update'

lgtm

@etcd-bot retest this please

Merging. Minor risk


[Question] How can I clear "Completed" status after VM restore?

Hello,
how can I clear "Completed" status after VM restore?
Harvester v1.3.1
Screenshot:

You may need to delete the completed restore from the harvester k8s cluster. We have identified it as a bug and as a workaround for now, you can delete the completed restore.
kubectl get virtualmachinerestores.harvesterhci -A NAMESPACE   NAME                               TARGET_KIND      TARGET_NAME   COMPLETE   AGE     ERROR default     restore-devendra-s3-backup-z5h5j   VirtualMachine   restored-vm   true       5m26s
kubectl delete virtualmachinerestores.harvesterhci restore-devendra-s3-backup-z5h5 -n default
Note: You would need to change the name of restore as per your cluster and it shall help remove the Restore column from the UI.

virtualmachinerestores.harvesterhci

But.. When I deleted "completed restore" using that commad:

The PVC for VM is deleted too...

It forces me to restore from backup again... And again I have "Completed" status.

Hi @dawid10353
The restoring VM's pvc has ownerReferences points to the matched CR virtualmahcinerestore, for example:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  ....
  name: restore-vm-b1-434fd2c1-fd7a-4c0f-bda7-9ac31becef13-disk-0
  namespace: default
  ownerReferences:
  - apiVersion: harvesterhci.io/v1beta1
    blockOwnerDeletion: true
    controller: true
    kind: VirtualMachineRestore
    name: restore-vm-b1-5xcnx
    uid: 434fd2c1-fd7a-4c0f-bda7-9ac31becef13
  resourceVersion: "100298"
  uid: c7db72ed-d9c9-4fee-a424-14a3cefbb0bb
spec:
  accessModes:
  - ReadWriteMany
  ....
  storageClassName: longhorn-image-l8mlc
  volumeMode: Block
  volumeName: pvc-c7db72ed-d9c9-4fee-a424-14a3cefbb0bb

so once the virtualmachinerestore CR is deleted, the PVC will turn into Terminating status. If the restoring VM is stopped, the PVC will be completely deleted.
Since it seems a cosmetics issue so far, I suggest not to remove the virtualmachinerestore resource.


Implement simple UI to add / remove validators

maybe let's consider just adding swagger UI?

See comment in #6 - this could be useful but I'd rather keep this light and separate from additional features. Could be a separate app or feature flag?


PostgreSQL: clean doesn't unlink referenced LOBs in pg_largeobject

Which version and edition of Flyway are you using?
5.0.2
If this is not the latest version, can you reproduce the issue with the latest one as well?
(Many bugs are fixed in newer releases and upgrading will often resolve the issue)
Don't know. I can't use 5.0.7 because there is another issue where some classes can't be found.
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Java API
Which database are you using (type & version)?
Postgres 9.6
Which operating system are you using?
Windows
What did you do?
(Please include the content causing the issue, any relevant configuration settings, the SQL statement that failed (if relevant) and the command you ran.)
I have two schemas in postgres database. First the default one 'postgres' and separate schema for application tables ('app_schema'). I store blobs in my application schema which are stored as large object. These large objects are stored in table 'pg_largeobject' in catalog 'pg_catalog'.
I run the following Java code test preparation:
// prepare database
Schema schema;
try (Database database = DatabaseFactory.createDatabase(migrator, false)) {
schema = database.getMainConnection().getSchema("app_schema");
if (schema.exists()) {
schema.clean();
} else {
schema.create();
}
}
What did you expect to see?
I expect that schema.clean() does clean the 'app_schema' AND the referenced entries in 'pg_catalog' catalog.
In my case I expect that the entries in 'pg_largeobject' which are referenced by entries in 'app_schema' will be deleted.
What did you see instead?
I see remaining entries in catalog 'pg_catalog'.'pg_largeobject' which not referenced anymore.

Hmmm I don't see an easy solution to this. Your table will most likely only contain OIDs. We would have to check whether these belong to large objects and if they do, unlink them. But that's not necessarily safe as these LOBs may still be referenced from a different schema that the user doesn't want cleaned.
Suggestions welcome.

I updated the error descriptions since the table 'pg_largeobject' isn't located in schema 'postgres'. It is located in catalog 'pg_catalog'

Any suggestion on how to resolve this in a safe and generic manner?

After some research in documentation of postgresql I found the build in utility 'vacuumlo' which removes orphaned large objects. May be it is possible to call this function during clean.
vacuumlo is a simple utility program that will remove any "orphaned" large objects from a PostgreSQL database. An orphaned large object (LO) is considered to be any LO whose OID does not appear in any oid or lo data column of the database.
see: https://www.postgresql.org/docs/9.6/static/vacuumlo.html

That has a number of issues. First of all we couldn't assume the CLI tool is installed, second it is challenging on RDS: https://dba.stackexchange.com/questions/174663/how-to-vacuumlo-an-rds-postgresql-database#174664

In Flyway 7 we introduced Script migrations: https://flywaydb.org/documentation/migrations#script-migrations. This will allow you to implement the proposed workaround (https://github.com/flyway/flyway/issues/1934#issuecomment-368848005). You could include it in a repeatable script, and use a timestamp placeholder to ensure it's always executed.

We think this is solved by using script migrations to call the 'vacuumlo' tool.


Editing admin password in mysql?

Is there a way to edit the admin account password in mysql?

If you can generate a supported hash, you can edit the account_ewsuser table, but I would recommend editing it through Python so that the proper hash algorithms are used.
If you do edit it in the databse, Django will upgrade the hash to the strongest supported on next login.

You can also run manage.py changepassword


User table name

Hello,
In Postgres, the user table name is reserved, but it's still possible to use it. The only change to make is to wrap the table name between quotation marks:
From:
CREATE TABLE user

To:
CREATE TABLE "user"

And this should be done for all queries to the database.

Thanks for the report, will try to fix! It may affect other code too though.


Multi-GPU inference issue

When I try to run internVL-Chat-V1.5, since it is large and need at lease two GPUs, therefore, I use the following command to run
CUDA_VISIBLE_DEVICES=2,3 python run.py --data MME --model InternVL-Chat-V1-5 --verbose
But it does not run on the two GPUs but only one and give OOM error, do I need to give more configuration?

Hi, @ruifengma ,
Sorry we have only supported evaluation on GPUs with 80G memories now (we will adapt to other low-profile GPUs very soon). A quick fix is to change L111 in vlmeval/vlm/internvl_chat.py from .to(device) to .to('cuda')

L197 in vlmeval/vlm/internvl_chat.py the image data is loaded into a default GPU. Try to check the GPU id before loading the data.

Thanks @junming-yang , the image script I found is
pixel_values = load_image(image_path, max_num=self.max_num).cuda().to(torch.bfloat16)
Do I need to dynamically check the id or force it to GPU 0 ? Since the model loading process is on 0 first then 1 (0 and 1 are projected by 2 and 3)

You can try to dynamically check the model's device.

You can try to dynamically check the model's device.

I appended .to(torch.cuda.current_device()) at the end, it still give me the same error

Maybe you can try .to(self.model.device).

Maybe you can try .to(self.model.device).

Yes, I did. Still the same

I have tried to reproduce your bug.
This is the revised code for running (from original code L107-110):
self.model = AutoModel.from_pretrained(model_path, torch_dtype=torch.bfloat16,
                                       trust_remote_code=True,
                                       load_in_8bit=load_in_8bit, device_map='auto').eval()
# if not load_in_8bit:
#     self.model = self.model.to(device)

Each GPU is allocated about 26 GiB. And no error is reported. Please check your code.

I have tried to reproduce your bug. This is the revised code for running (from original code L107-110):
self.model = AutoModel.from_pretrained(model_path, torch_dtype=torch.bfloat16,
                                       trust_remote_code=True,
                                       load_in_8bit=load_in_8bit, device_map='auto').eval()
# if not load_in_8bit:
#     self.model = self.model.to(device)

Each GPU is allocated about 26 GiB. And no error is reported. Please check your code.

I actually did not DIY but completely following the advice. I use two A40 GPUs for the task, I checked and did the same modification as you did

Not coding issue, update the latest version of official internvl configurature file solve

I found that we should remove self.model = self.model.cuda() if we use device='cuda', device_map='auto'.


Support global/project/step env even if buildkite trigger step is used

Overview
This PR addresses what appears to be a regression of behaviour introduced in: #41
Buildkite trigger steps don't support a top level env property, but the new global/project env var injection means that all steps, even trigger steps, will at least always have env: {}, causing them to fail:
`env` is not a valid property on the `trigger` step. Please check the documentation to get a full list of supported properties.

This PR introduces the same env vars to each step but for trigger steps, nests it under build, env:
Input
env:
  SOME: var

steps:
  - trigger: some-pipeline
     command:
       - make something

Output
Before
env:
  SOME: var

steps:
  - trigger: some-pipeline
     env:
       SOME: var
     command:
       - make something

After
env:
  SOME: var

steps:
  - trigger: some-pipeline
     build:
       env:
         SOME: var
     command:
       - make something

It handles the existence / non-existence of build and its nested env property.
Outstanding Questions
Since trigger steps don't support top level env, presumably they also can't support:
env:
  BUILDPIPE_SCOPE: project

Does this mean trigger steps can't be run / skipped /etc per project?

Hey @bradbarrow,
Overall this PR seems reasonable to me, but I'm not an expert at Go so I'm going to ask for a second pair of eyes to review this changeset.
As far as your outstanding question is concerned, could you perhaps clarify in what scenarios a per-project trigger step is useful? I believe there are other steps that currently don't support a top-level env field, making it impossible for them to support the BUILDPIPE_SCOPE environment variable (e.g. wait, block and input don't support this either). Unless there is a good use-case I'm not sure if this is something that we'd have to address now.
Note that if we wanted to release this, we would also have to add an entry to the changelog and increment version numbers in a few places (similar to https://github.com/jwplayer/buildpipe-buildkite-plugin/pull/85).

Thanks both for the feedback. I'll update this PR shortly.
I've since updated our fork to support BUILDPIPE_SCOPE: project on a trigger step, so that it can be made conditional.
I'll take a look at the other step types you mention and how that scales.
Our use case for a per project trigger step is as follows:
We have 3 projects:

app
packages
docs

They share some steps: lint, test, build etc
They have some that are unique to them: e.g. localisation in app
They have nuanced approaches to deployment:

packages might be published directly in CI to npm
docs might be synced to s3
app triggers a deployment in a separate buildkite pipeline that orchestrates some docker stuff

In the case that someone has only changed the docs - we don't want to trigger a build on the app deploy pipeline
We can try get around this using all kinds of conditionals, but it feels just like any other project-scoped step.
If it were trivial to have a CLI command that triggered it, we'd be fine:
steps:
  - label: trigger-deploy
    env
      BUILDPIPE_SCOPE: project
    command:
      - buildkite-agent trigger app-deploy

But the only clean way to trigger builds is with a trigger step, so it's nice to be able to make them conditional even though nesting it under build > env > BUILDPIPE_SCOPE feels very wrong.

That's an interesting use-case. That definitely helps to make me understand why it might be useful to have the ability to conditionally trigger pipelines.

If it were trivial to have a CLI command that triggered it, we'd be fine

I wonder if this could be solved through buildkite-agent pipeline upload. I believe this can be invoked multiple times to add steps to an existing running build. I think what you should be able to do is have a step as outlined in your example, but then use something akin to ./script/generate_trigger_step | buildkite-agent pipeline upload where generate_trigger_step is a script that is stored in your repository that outputs the step definition for a trigger.
That way we should have to do fewer gymnastics with regards to supporting top-level env fields for other types of steps, which would cause Buildpipe's supported schema for steps to diverge from what Buildkite natively supports. In principle, I'm not against diverging on this front, but I want to make sure that when we do that it is a well considered change as it may cause confusion.
Either way, happy to consider any concrete proposals.

FWIW we've been using this patch for a couple months now. Would love to know the next steps :)


Gettting "cannot load compass" after upgrading to Sass 3.3.5 / Compass 0.12.5

This is quite the same like #103 but with newer versions.
I hotfixed it by doing
sudo gem uninstall sass
sudo gem uninstall compass
and
sudo gem install compass --version 0.12.4
which will also install a compatible sass-version as already mentioned by @Cyberlane in #103.

it worked for me, thanks @DerZyklop


No labels on roads, features when zoomed in

Curious when you might add more detailed labels :) makes it hard to find things when zoomed in. Thanks!

another example of label weirdness - lake merrit appears three times, the park appears on top of the lake (also three times)

Lake Merritt labels are at the meeting point of 4 different "data tiles", and right now the labeler works in isolation on each data tile, so the labels will be tripled.

One approach is to de-duplicate labels so it won't label a feature that is seen already, the drawback here is the label may be non-optimal and non-deterministic depending on which tile is labeled first.
Another option is for me to move the optimal label placement to the backend, so the polygon is labeled via point geometry in the data
The issue of the park label appearing over the water is tricky, since the labeling for these two feature classes is independent; this can either be solved by doing preprocessing like 2) above or by creating some custom collider in the frontend (haven't thought through exactly how this can work)

The line labeling absence will be addressed in #1
Keep em coming!

@tarngerine please upgrade to version 0.6.1 on npm
map link: https://protomaps.com/map/#16/40.7401/-73.9835
screenshot:

Linear labels are not placed in any intelligent way now, working on refining that (needs to interact well with highway shields too)


chore: add distribution prefix path to  env

test ci

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.10 out of 11 committers have signed the CLA.:white_check_mark: daohu527:white_check_mark: macDure:white_check_mark: fanyueqiao:white_check_mark: qilinhu:white_check_mark: ad-litianjiao:white_check_mark: SeasoulChris:white_check_mark: lykling:white_check_mark: wk19921225:white_check_mark: lj0919:white_check_mark: WildBeast114514:x: chenhuanguangchenhuanguang seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


⚠ Minecraft has degraded performance

In f162586, Minecraft (https://www.minecraft.net) experienced degraded performance:

HTTP code: 200
Response time: 1216 ms

Resolved: Minecraft performance has improved in 0554785.


Improve design system for testimonial

Need to improve this component on \<Component name>\src\<File Name.html>
Improvements required :
all the colours of text and bg are not correctly depicted ....correct them and also provide a general info of testimonial
Any reference image?
Any external reference?
You can checkout this one for better understanding.

assign me @rupsha014 @Rajdip019


Unresolved Poseidon import

error[E0432]: unresolved import `poseidon`
 --> /Users/filiplazovic/.cargo/git/checkouts/snark-verifier-972b60abf3a1213b/df03d89/snark-verifier/src/util/hash/poseidon.rs:5:16
  |
5 | use poseidon::{self, SparseMDSMatrix, Spec};
  |                ^^^^ no external crate `poseidon`
  |
help: consider importing this module instead
  |
5 | use poseidon::{crate::util::hash::poseidon;
  |                ~~~~~~~~~~~~~~~~~~~~~~~~~~~~

I assume this happens because I disabled the default features, which includes poseidon as well.
snark-verifier = { git = "https://github.com/privacy-scaling-explorations/snark-verifier", default-features = false }

Thanks for reporting this! Opened https://github.com/privacy-scaling-explorations/snark-verifier/pull/27 to resolve it.


built-in functions must happen at parser level

variable resolution happens during parsing, so function results assigned to variable can only be processed during parsing.

this has happened


Feature: Add a mix deps-get Menu item and shortcut

While you're at it, see if you can detect changes to deps and add that lightbulb icon to notify refresh.

For now, external tools work fine. But we should really use the SDK's path...


Is it possible to customise the dialog width or add this feature to the lib?

As the Material Design Spec shown, dialogs have two sizes of horizontal-margin (24dp or 48dp). This lib only provides 24dp by default, but I think 48dp is also a useful choice in some conditions. I have tried dialog.getWindow().setAttributes() to fix it, and I wonder whether it can be better.
Thanks.

Duplicate.


Directory module

Related commits: 319a917, b8bd169

Changes added is a5da154 commit:

If ad add form has error in some mandatory field then Category field become empty and you can't change it
Add price into snippet meta info menu, if price field is zero or empty then display "Free", if possible display it in green colour
Category and price should be displayed in Timeline as well
Categories page (/page/ads-categories) should display all adds when no category is selected
Add pruning setting, default is 30 days, after 30 days, ad should become inactive and shouldn't displayed anywhere except for the author on some special, however user should be able to activate it again, or active it automatically upon ad edit. I think user's status field can be used for this.
For other users it should be "I'm interested" button which will send email with details of buyer to seller.


Direct commands

It would be great If you added direct commands to be executed right from native shell
sth like
rainbowstream --tweet "Hello Twitter"

I would also very much like this feature. Maybe implement it as a way to pass a single command to rainbowstream. Similar to bash -c '<command>'
rainbowstream -c '<rainbowstream command1; rainbowstream command2>'
This would be very handy for integrating rainbowstream into other applications and using it as an all in one interface to twitter. Much easier than learning the twitter-API


Reproduction

Screenshots

Additional context

absolutely not

they don't seal your body they're airtight

im gonna tightly seal my hands around your throat if you buff hardsuit


A series of Bigint arithmetic fixes copied from Waldek Heibsch, Closes #120

Waldek noticed a series issues in the bigint libraries and corrected them in his repository. This PR copies across the commit messages and content to ease comparison. A single minor whitespace change has been made from Waldek's commits but line numbers have been preserved to reduce divergence.
The original commits were:

Fix bigint left shift of negative numbers
Fix returning pop integers from bigint functions
Do not use uninitialized memory during bigint divide
Use safer way to return result of bigint multiplication
Discover more cases of 0 quotient in bigint divide

A further commit has been added that resolved issues in the function testbit.
IMPORTANT NOTE: Ideally we will include unit tests with this PR but this is submitted now in order to begin the review process.

Build not working correctly but these changes are imported from a working system & verified locally


Add method to get Forge versions for specific Minecraft version

A new public method, GetForgeVersions, has been added to the ForgeInstaller.cs class. This method returns the available Forge versions for a specific Minecraft version, improving the process of version management and installation.

your PR has too many changes. remove all changes except GetForgeVersions method

Please, do Squash and merge. Thank you!


Windows xp 32bit builds no longer working.

In ctrlr 5.4.27 and 5.4.29 On windows xp when i try to open to open the ctrlr standalone it gives me an errror:
'Impossibile trovare il punto di ingresso CreateSymbolicLinkW della procedure nella libreria di colegamento dinamico KERNEL32.DLL'
And ableton fails to load the vsti
In english that's
'Impossible to find entry point CreateSymbolicLinkW in the dynamic link library KERNEL32.DLL'
it looks to me that something when wrong in  linking.
ctrlr 5.3.201 works though. So this probably happened fairly recently.
Ewan.

XP is not supported anymore


Fix display issues with broken border or characters from the previous line not being cleared

I managed to find the reason why sometimes the borders get broken, or we have a character from a line that still gets displayed. This is the same issue as https://github.com/Xithrius/twitch-tui/issues/298#issuecomment-1461259931.
I think this only happened on kitty, and maybe foot,  because this came from the fact that ratatui and most other terminals were calculating the width of the \u{e0000} character incorrectly.
This character is used by twitch clients like chatterino to bypass twitch duplicate message timeout, so it can appear quite frequently.
My fix is to just remove it from the message as it is not meant to be rendered.
It is possible that there are some other discrepancies between ratatui and different terminals, so there could be some other unicode characters that will display the same rendering issues, but I haven't seen any for now.
This PR is independent of the other 2 I have, so you can merge it whenever you want.

Oh man, I've been trying to solve this issue ever since scrolling was implemented in the main chat window (probably around a year or so ago).
I'm so glad you were able to find a fix, I'll test this on my machine later today.
Thank you so much!

Haha it was a tricky one to find. I switched the debug! of the twitch message to print the debug version of the cleaned_message string, so that it will actually display invisible unicode characters, which should hopefully help us find any other similar issue in the future, should they arise.
I also noticed there is still a few rendering issues when emotes are enabled, probably something to do with spans starting/ending with zero-width spaces, but this is already fixed in #529, so I won't fix it here.

available in https://github.com/Xithrius/twitch-tui/releases/tag/v2.6.3


Candidate Release Comments (Family Friendliness)

This issue was created to collect comments about the upcoming metrics release.
This thread is for comments about Family Friendliness
GitHub location: https://github.com/chaoss/wg-diversity-inclusion/blob/master/focus-areas/events/family-friendly.md
Release candidate: https://chaoss.community/metric-family-friendliness/
See all release candidates of metrics are at:
https://chaoss.community/metrics-rc/
Important Dates
Release Freeze: June 21st, 2019
Candidate Release: June 24th, 2019
Comments Close: July 24th, 2019
Release Date: August 1st, 2019

Likert scale [1-4] item: How family friendly is the event?
Set your scale to 1-5 to allow for neutral options.

There are a lot of opinions about whether likely scales should be odd or even depending on the situation. I think we should take a neutral stance and say [1-x]. Thoughts?

On Jul 11, 2019, at 14:48, Matt Germonprez<EMAIL_ADDRESS>wrote:
Likert scale [1-4] item: How family friendly is the event?
Set your scale to 1-5 to allow for neutral options.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I’m also good with Matt’s suggestion, too :)

On Jul 11, 2019, at 14:48, Matt Germonprez<EMAIL_ADDRESS>wrote:
Likert scale [1-4] item: How family friendly is the event?
Set your scale to 1-5 to allow for neutral options.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

1-x is a good idea.
(This suggestion would apply to all other D&I metrics where this issue comes up).

1-x is fine with me. I had originally included 1-x because I don't expect everyone to know what "likert scale" means.

Remove text from resources section


How do I run the C++ demos on OSX?

I compiled the cpp/SimpleDemo code using scons platform=osx and I edited the .gdnlib file from the Godot editor to add the .dylib file, but when I then try to run the demo, I get the error does not have a library for the current platform. Am I missing something?

Did you save the gdnlib file properly?

Ahhhh... I thought I had, but when I double checked by opening the file outside of Godot, I saw it wasn't saved. Now it works! Godot editor could definitely do with a UX improvement here. Thanks for pointing me in the right direction. Now to see why my own test project didn't work, I assume its a similar issue since I was getting the same error, but now that I have a working demo, I should be able to figure it out 👍


deploy ssh key for passwordless ssh to all compute node

buildtest needs passwordless ssh to all compute nodes in order to get acquire system information of all nodes.
For some sites user's may already have this enabled by default and for others this may not be allowed.
buildtest may create a ssh key (~/.ssh/buildtest_rsa.pub) and use ssh-copy-id <compute-node> to transfer the public key to all nodes. Once this is setup, buildtest can ssh to any node if needed to run a test. This may be an alternative for sites that may not have a job-scheduler or if user's want to run tests from buildtest by bypassing the job-scheduler.

this issue is not relevant at the moment.


Don't Merge! PR real time test for webhook case

Docs Build status updates of commit d49298c:
:clock10: Pending: waiting for processors (5 builds ahead of you)
:warning: Docs Build is busy, currently there are 5 builds ahead of this one, for more information you can view the Build queue graph on the Docs Portal.

Docs Build status updates of commit d49298c:
:clock10: Full build: the average full build time is 5 min(s) 57 sec(s), this is based on the last 658 build(s) for this repository.

Docs Build status updates of commit d49298c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details
Dependent Files

docs-ref-conceptual/testing.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile) View (azure-cli-2018-03-01-hybrid)

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.


Slack Integration Topic Issue.

I have followed the docs, built my local bot and integrated to slack.
However, after sever times tried:

When I update the topic, it didn't rly reply correctly.
Try delete data.json, re-parse the .ss topic, it still remains the old responses, like the first time it loads in slack.

Since data.json looks fine to me, I am not sure if this is a known cache issue related to slack. But there seems not much we can do in slack beside setting up the key.
I hope this got resolved asap.
Thank you!

duplicate of #95 .
I have provided an interim fix for this issue in there.


Fix sitelet initialization concurrency problems

A duplicate key error could happen during sitelet initialization on activating resource classes as the dictionary was not concurrent.
Also, do not use global locks on dictionaries, ConcurrentDictionary is a more optimized solution.

Fixed for WS4 in https://github.com/intellifactory/websharper/commit/0cf0032be7006898c2ecfd6fde872798756cae77


[Extensions] Fix AOT warning

Summary
The focus of these changes is to fix an AOT warning with the Microsoft.Extensions.Azure package.

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


Is everything alright with block weights?

There are currently 3 arguments for block weights in LoRA training:

down_lr_weight
mid_lr_weight
up_lr_weight

Not sure why they are called up and down instead of IN and OUT, but that's not even the main issue. Both down and up lr weights require 12 values. How is this possible when LoRA is divided into 17 blocks?
The blocks are:
1 BASE
6 IN
1 MID
9 OUT
Are these different blocks?
If this needs to be fixed, so do block_dims and block_alphas (currently requiring 25 values).

Got it!
So I guess only the first 6 and 9 numbers are used for weights in Standard LoRA? Or 6 and 9 last numbers?
down = IN, up = OUT?

Right, as @kohya-ss said in Releases log:

if you do not expand to conv2d3x3, some blocks do not have LoRA, but please specify 25 values for the argument for consistency.

I wonder which are the some blocks?
@zyd232 suggests this structure in https://github.com/kohya-ss/sd-scripts/issues/470

But I've been researching Stable Diffusion UNet architecture and can't find a proof anywhere :( Are these the missing (convolution) blocks in Standard LoRA?

Thank you so much!

Thank you so much!

The Stable Diffusion v1 U-Net has transformer blocks for IN01, IN02, IN04, IN05, IN07, IN08, MID, OUT03 to OUT11.
They correspond to the following keys in the state dict: model.diffusion_model.input_blocks.1, model.diffusion_model.input_blocks.2 ... model.diffusion_model.middle_block ... model.diffusion_model.output_blocks.3 ... model.diffusion_model.output_blocks.11.
IN00, IN03, IN06, IN09, IN10, IN11, OUT00, OUT01, OUT02 don't have transformer (which has Linear layers) and only have Conv2d layers.

Are things different in this scenario with SDXL?


Implement an extension mechanism for runtime library calls

Two possible approaches:

inject library calls into codegen executables at runtime (so codegen can call external functions)
support lowering custom compile-time ops in a stream/command-buffer aware form and execute them at runtime

Approach 1 is more tightly coupled to the compiler but would allow for mixing generated code and library calls within the same executable, while approach 2 is loosely coupled but would be all or nothing for a particular executable. We should eventually do both but can probably pick only one for the short-term goals.

Depends on #3580; this would be adding the ability to declare imports and then populate them on the iree_hal_executable_dispatch_state_v0_t passed to dispatches.


Check "carto logo" disabled checkbox in map options

Context
For those users unable to remove the CARTO logo we currently have a non-checked disabled checkbox in map options

But it's confusing because the option is activated.
Steps to Reproduce

Go to map options and look for the "CARTO logo" checkbox

Current Result
Checkbox is disabled but unchecked
Expected result
Checkbox should still be disabled but checked

This is a matter of styling, the checkbox is checked, but is not visible.

Understood.


Updated Button Control

I have updated the dependencyproperties of the button. Also I changed the event subscription to the static timer to prevent potential memory leaks. #2

Ok, I also updated the rest of the controls. :)

Awesome, thanks for the PR @OpResCodes !

@OpResCodes I just updated the NuGet package. please let me know if it works as expected

Thanks, all seems to work fine now!


Use pattern matching for names

Apologies if I missed a prior issue about this:
I noticed that it looks like the data-name attribute is what's used to determine the icon to show aka [ gulpfile.js || gulpfile.coffee || gulpfile.babel.js ]-> .gulp-icon
I was trying to name some of my files to show the gulp icon in Atom instead of the JS icon by saying assets.gulpfile.js instead of assets.js... but looks like its very specific selectors in file-icons.less...
thoughts on changing the selectors to &[data-name*="gulpfile"]:before which should pick up all files with gulpfile in the name?

I'm sure it'd work, although there may be false positives. Then again, I'm sure any file with "gulpfile" in its filename somewhere is likely to be Gulp-related.
Should the matching be case-insensitive as well? &[data-name*="gulpfile" i]:before (I don't use Gulp or Grunt or any of that tripe, so I've no idea about the possible variations)

Should the matching be case-insensitive as well? &[data-name*="gulpfile" i]:before (I don't use Gulp or Grunt or any of that tripe, so I've no idea about the possible variations)

Even better! I personally use lowercase style for naming various config files, but I doubt that's a universal naming convention.


Task conditioning

Thanks for writing this awesome script, very handy!
I'm seeing something weird when using task conditions in ib. Here's a sample script:
function setVars
{
  return "foo value"
}

$foo = $null

Enter-Build {
  $foo = setVars;
}

task one {
  Write-Build white "Foo variable is $foo"
  # this returns true
  return ($foo -ne $null)
}

task two -if (($foo -ne $null)) {
  # never executes with above condition
  return ($foo -ne $null)
}

task . one, two

"$foo" is evaluating to $true as we'd expect, however, the task "two" does not run. If you remove the condition on it returns true.
Here's the output:
Build . C:\builds\ASIFramework\test.build.ps1
Task /./one
Foo variable is foo value
True
Done /./one 00:00:00.0216476
Task /./two skipped.
Done /. 00:00:00.0216476
Build succeeded. 2 tasks, 0 errors, 0 warnings 00:00:00.0372450

Shouldn't task "two" be executed? I've also tried using $script:foo since I thought it was a script issue but I get the same result.
Am I missing something?
Thanks!

Hi @nsartor, thank you!

Am I missing something?

Yes. Your condition is calculated during the build, not when tasks are added.
Thus, you should use a script block in -If
task two -if {$foo -ne $null} {
    ...
}

AFAIR, the wiki should explain and help, too:
. Invoke-Build
help task -Parameter If

@nightroman yep that was it! Thanks for the quick response!


Route::controller() and $this->middleware('cors')

Using a combination of Route::controller() and $this->middleware('cors') in the controllers constructor doesn't seem to work. The HandlePreFlight class hasMatchingCorsRoute function only seem to check for middleware specified in Route::'s but not in controller.

Can you try again with https://github.com/barryvdh/laravel-cors/releases/tag/v0.10.1 ?
Please re-open this issue when the problem still persists.


Added 3.3 missing migrations

Coverage decreased (-1.0%) to 82.773% when pulling 283356ba830644828074e463d6c6f454a75ff7d4 on fixes/3-3-missing-migrations into 58265bdc68f1b92420653c1da9151919eadbe8cb on master.

Coverage decreased (-2.1%) to 81.673% when pulling d1628cc32404bb291047d3d0c51cfe15281db27c on fixes/3-3-missing-migrations into 58265bdc68f1b92420653c1da9151919eadbe8cb on master.

ok to merge


move metrics config to pkg

the observability config is used in other packages including
the sample controller. This commit
pulls observability config into knative.dev/pkg similar to
logging config for better reusability.

/lint

/assign @mattmoor
This repo requires a bit of refactoring and also some cleanup in https://github.com/knative/serving/pull/5841, before we can finalize config validation in https://github.com/knative/sample-controller/pull/121
Seems like similar refactoring was already done to knative.dev/pkg/logging so this shouldn't be too surprising.

/ok-to-test

the drop in test coverage is because config_test.go is kept in knative.dev/serving/pkg/metrics, similar to knative.dev/serving/pkg/logging.

@mdemirhan or @yanweiguo may have thoughts as to whether we should keep config_test.go under knative.dev/serving/pkg/metrics or move it to knative.dev/pkg/metrics.

I know the observability config in knative.dev/serving is under pkg/metrics path. However I think it is a mistake. The observability config not only include metrics configurations but also logging configurations.
I don't think metrics path of knative.dev/pkg is the right place to move to. Currently the lib is about config options to customize an OpenCensus reporter to report metrics.
Maybe move to knative.dev/pkg/config/observability.go. And I would expect the unit test to be moved as well.

@yanweiguo ConfigMapName() which returns the name config-observability for the config map is already under knative.dev/pkg/metrics from before this PR. are you suggesting to refactor that function out too (since that refactoring may touch a good number of other places in the code)?
also any idea why for logging, there is config_test.go under knative.dev/serving/pkg/logging,  while the config itself is moved? Does that require refactoring too?

@yanweiguo ConfigMapName() which returns the name config-observability for the config map is already under knative.dev/pkg/metrics from before this PR. are you suggesting to refactor that function out too (since that refactoring may touch a good number of other places in the code)?

Ah I missed that. Well, I still prefer to move them to another path. You don't have to do it at this point. Could you move them to a separate file, say metrics/config_observability.go?
I think it is a mistake that config_test.go is kept under knative.dev/serving/pkg/logging. I'd expect it to be moved to pkg as well.

FYI: created https://github.com/knative/serving/issues/5850

@yanweiguo moved the observability pieces into config_observability.go. Also moved the config_tests from serving/pkg/metrics to config_observability_test.go.

ok this should be good to go.

/lgtm
/approve

/assign @mattmoor

@yanweiguo looks like this never got merged. can you TAL it again. thanks!

/retest

/lgtm
/approve


How to control logs?

MemcachedConnection emits logs roughly every 1 sec:
23:00:00.339 [Memcached IO over {MemcachedConnection to hostname:11211}] DEBUG n.s.m.MemcachedConnection: Done dealing with queue.
23:00:00.339 [Memcached IO over {MemcachedConnection to hostname:11211}] DEBUG n.s.m.MemcachedConnection: Selecting with delay

Is there any way to tune down these logs? Thank you!

I found it. In my case, I use monix/shade in a Play2 app. To tune down memcached logs, I added to src/main/resourcs/logback.xml following lines:
    <logger name="net.spy.memcached" level="warn" />
    <logger name="net.spy.memcached.MemcachedConnection" level="warn" />


Add support for reverse proxy

What is the feature you are proposing?
I hope to add support for reverse proxy. It supports functions similar to http-proxy-middilware in hono app.use. If someone can tell me how hono implements the reverse proxy function of cfworkers, it would also be great.

Hi @allmors
I think it is not needed. We can write a reverse proxy with this code:
import { Hono } from 'hono'

const app = new Hono()

app.all('*', async (c) => {
  const res = await fetch(c.req.raw)
  // ...
  const newResponse = new Response(res.body, res)
  // ...
  return newResponse
})

export default app
``

Related: #1414

@allmors
Which platform do you run it on? Perhaps, you don't set up an "origin". If you don't have it, you can specify a url:
app.all('*', async (c) => {
  const res = await fetch('http://example.com') // <==
  console.log(res.status)
  // ...
  const newResponse = new Response(res.body, res)
  // ...
  return newResponse
})

For Cloudflare Workers, the following will not work without an origin.
const res = await fetch(c.req.raw)

However, if you just want to proxy, the following may be sufficient, what do you think?
const res = await fetch('https://fabfilters.online/', c.req.raw)

For Cloudflare Workers, the following will not work without an origin.
const res = await fetch(c.req.raw)

However, if you just want to proxy, the following may be sufficient, what do you think?
const res = await fetch('https://fabfilters.online/', c.req.raw)

Hi, I have tried the above code on Nodejs but it not proxy to example.com URL. Is it only work in Cloudfare ??

Hi @kongminh113 !
Thanks! It seems to be a bug! I've created the issue: https://github.com/honojs/node-server/issues/121


SDMolSupplier Python wrapper should expose it's stream constructor

It seems that the python wrapper for SDMolSupplier does not expose SDMolSupplier's constructor that takes std::istream, only the one that takes a filename as std::string. Link to the C++ API for reference: https://www.rdkit.org/docs/cppapi/classRDKit_1_1SDMolSupplier.html
This is frustrating mainly because of the API inconsistencies.  For example, here is the difference in API between ForwardSDMolSupplier and ForwardSDMolSupplier (RDKit 2023.09.2):
from rdkit import Chem

# Fine
Chem.SDMolSupplier('/tmp/test.sdf')

# Fine
Chem.ForwardSDMolSupplier('/tmp/test.sdf')

# Fine
with open('/tmp/test.sdf', 'rb') as f:
  Chem.ForwardSDMolSupplier(f)

# ArgumentError
with open('/tmp/test.sdf', 'rb') as f:
  Chem.SDMolSupplier(f)

Ideally all of these methods of constructing MolSupplier subclasses would be consistently exposed in Python.

Ah, understood. In that case, it would be nice to comment this in https://github.com/rdkit/rdkit/blob/897de1d92dcb681d4ed5eebd4854c0d24b05f9c5/Code/GraphMol/Wrap/SDMolSupplier.cpp I suppose — I would have found that comment before opening the issue.


Packaging and dictribution not supported yet with setuptools

No tool (neither distutils nor setuptools) has been used yet to ensure easy installation of the release (to be defined)

Installation now fully managed by setuptools, also distributed to anaconda as a condapackage