File changes in symbolic linked directories are not reflected

How are you using the lua-language-server?
Visual Studio Code Extension (sumneko.lua)
Which OS are you using?
Windows
What is the issue affecting?
Annotations, Type Checking, Completion, Diagnostics/Syntax Checking, Hover, Libraries
Expected Behaviour
When the content of a file within a directory which is a symbolic link changes, the language server should reflect the changes in, e.g., the code completion, hover, or diagnostics.
Actual Behaviour
The changes are not reflected, i.e., the code completion, hover information, or diagnostics as examples are not updated.
Reproduction steps

Open a workspace which contains a directory which is a symbolic link.
Example:

The following content of common.lua is loaded:
---@param p1 string
local function t1(p1)
end

---@param p2 string
local function t2(p2)
end

return t1;

Change the content of common.lua with an external program without opening common.lua in VSCode, e.g., change the return to return t2;. For t in A.lua, t1 is still shown.

Open common.lua in VSCode. Now, in A.lua, t2 is shown for t.

Alternative:

Open the workspace with the symbolic linked directory and the target directory as a second workspace.
Example:

Open common.lua in the actual directory, and change something, e.g. the return to return t2;.
t in A.lua still shows the information about t1. If common.lua in the symbolic linked directory is opened, t shows t2 on hover.

Additional Notes
I am not sure if this behavior is intended or a bug. So, feel free to close this issue if the behavior is intended.
Log File
No response

Can we handle this case @actboy168 ?


Add Cloudflare Pages Functions Support

Support passing RuntimeContext of Cloudflare Pages Functions

https://developers.cloudflare.com/pages/platform/functions/api-reference/

An example of Cloudflare Pages Functions has been added in #37.


transformers error on mac

Hi,
Any help would be appreciated.
./agentk
WARN: Could not load agent "content_creator". ModuleNotFoundError: No module named 'transformers'
WARN: Could not load tool "select_best_frames". ModuleNotFoundError: No module named 'cv2'
WARN: Could not load tool "split_video_into_frames". ModuleNotFoundError: No module named 'cv2'
WARN: Could not load tool "generate_text". ModuleNotFoundError: No module named 'transformers'
WARN: Could not load agent "content_creator". ModuleNotFoundError: No module named 'transformers'
WARN: Could not load tool "select_best_frames". ModuleNotFoundError: No module named 'cv2'
WARN: Could not load tool "split_video_into_frames". ModuleNotFoundError: No module named 'cv2'
WARN: Could not load tool "generate_text". ModuleNotFoundError: No module named 'transformers'
WARN: Could not load tool "select_best_frames". ModuleNotFoundError: No module named 'cv2'
WARN: Could not load tool "split_video_into_frames". ModuleNotFoundError: No module named 'cv2'
WARN: Could not load tool "generate_text". ModuleNotFoundError: No module named 'transformers'

Those are tools and agents that AgentK has created but contain errors and therefore can't be loaded.

I'm working on making the system more robust when it comes to detecting and fixing errors in modules it's creating.


Contract API action with no parameters fails.

Description
The EOSIOLib dispatcher does not properly handle api actions with no parameters.  It will fail trying call this:
https://github.com/EOSIO/eos/blob/5e47cbd0cabebf19d83a5d1746e1a3cb91c2b824/contracts/eosiolib/dispatcher.hpp#L47
because the serialized size is 0
Relayed from a legitimate bug report received through another channel:
I'm trying to see if there's a way to push action to a parameterless method.

// Contract
class tester : public contract {
public:
using contract::contract;
tester( name self ) : contract(self){}
//@abi action
void test(){
print("Test");
}
};
EOSIO_ABI( tester, (test))

// From Generated Abi
"types": [],
"structs": [{
"name": "test",
"base": "",
"fields": []
}
],
"actions": [{
"name": "test",
"type": "test",
"ricardian_contract": ""
}
],

// Commands tried
cleos push action tester tester '[]' -p eosio
cleos push action tester tester '{}' -p eosio
cleos push action tester tester '""' -p eosio

All three of those commands returns
Error 3030000: transaction validation exception
Ensure that your transaction satisfy the contract's constraint!
Error Details:
size > 0:

Acceptance Test Criteria

[x] test cases that prove a payloadless action properly executes in the EOSIO_ABI paradigm

Test suite "payloadless_tests" has passed with:
1 test case out of 1 passed
2 assertions out of 2 passed
Test case "payloadless_tests/test_doit" has passed with:
  2 assertions out of 2 passed


MSSQL Express DockerHub not linking to correct documentation

It appears the documentation that is being used in DockerHub is referencing a different source other than this GitHub repo. Additionally, it appears the source which is currently in use has incorrect Markdown formatting as the example Code block snippets don't display in DockerHub
Docker Hub -https://hub.docker.com/r/microsoft/mssql-server-windows-express
MSSQL Express docs - https://github.com/Microsoft/mssql-docker/tree/master/windows/mssql-server-windows-express

Hi,
Which document in the link are you referring to?

@forkazmoden Thanks for your reply. If you notice the Docker Hub Link & MSSQL link are 2 completey seperate documents. Actually, the MSSQL Express doc is updated and has better examples.
The Docker Hub link as you notice doesn't properly display the code blocks from the MSSQL docs.
Is this clear?

SQL Server examples on Docker are available on the official Microsoft documentation. Please feel free to leave comments on the particular docs pages which you feel require changes/improvements.


navi: 2.9.0 -> 2.10.0

Motivation for this change
https://github.com/denisidoro/navi/releases/tag/v2.10.0
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[x] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

This release adds support for using output of tldr as a cheatsheet, but not all tldr clients are supported. Ideally, users would use tealdeer, but it requires managing cache — I'm not sure if it can be or should be addressed during packaging, or if we should leave it up to users to decide what tldr client to use?


Update event-4768.md

https://github.com/MicrosoftDocs/windows-itpro-docs/issues/3863
Changed failure coding.

@dansimp A new PR that has been contributed by a freelance writer that addresses issue #3863 is available for review. Thanks.


Shared Libraries have undefined symbols

When building WebRTC as a shared library there are a ton of undefined symbols which should not be the case given that it is a shared library.
Any idea on how to get rid of the undefined symbols in the resulting shared library? A lot of them are from the standard library too, with some custom namespace (eg. std::__Cr)

Which platform? Windows or macOS?
Shared libraries may use other libraries. You need to add the required libraries to your app.

Linux Shared Build. It should not have undefined references to like protobuf or std::__Cr::basic_string though?

Any library including this one can refer to other libraries. An app will gather all libraries (link them) with your app code. What you need to do is Google the unresolved externals, find the library that provides this symbol, and link it in your app. Then your problem will be solved.


docs(README): add example .yarnrc configuration

I also noticed that it only works if you redirect. Maybe it would make sense to additionally support status code 200 for the exact version?

I'm not a yarn user to I don't follow this addition. Why you need that?

I guess this is related to https://github.com/przemyslawpluta/node-youtube-dl/pull/338 so no more a necessary thing


Pixiv sketch pictures

I have a quastion, when are using download by artist ID, it's consider pixiv.sketch pics too or this site is partly from main???

Is it visible in the works list from pixiv webpage? or is the link to the image follow the same pattern like https://www.pixiv.net/member_illust.php?mode=medium&illust_id=<image_id>

Its a separate subdomain and structure, would need specific code to scrape.
Same as pixiv's other subdomains.
Example:
https://sketch.pixiv.net/items/4939758965177020715
I would say there's a possibility for it to be a menu option in the future
(or a fork) but right now I think the main site is probably higher priority.
On May 23, 2018 4:06 AM, "Nandaka"<EMAIL_ADDRESS>wrote:

Is it visible in the works list from pixiv webpage? or is the link to the
image follow the same pattern like https://www.pixiv.net/member_
illust.php?mode=medium&illust_id=<image_id>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Nandaka/PixivUtil2/issues/367#issuecomment-391258447,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AltQksu010faCHJFCNadVfXR7l-Rn_48ks5t1Rh_gaJpZM4UJxTf
.

ok, thanks for answers.. it's just many of nice pictures post only on sketch not on main site..

I am also for getting the abilityto download sketches at some point.

will not do, open to pull request


Improve aborted transaction docs

I overlooked the savepoints feature in https://github.com/elixir-ecto/ecto/pull/3946 and found that it's actually an SQL standard. It seems it's currently supported by all our default adapters, so we shouldn't make the case that it's specific to Postgres.
BTW, Postgrex has this option documented here https://hexdocs.pm/postgrex/Postgrex.html#transaction/3, but I had to look up the source code to find that MyXQL and TDS also support the savepoints feature. Should we document this as part of Ecto Repo.transaction/2 as well?

:green_heart: :blue_heart: :purple_heart: :yellow_heart: :heart:

Adding more information to transaction is welcome, as well as PRs to MyXQL and TDS. :)

Hi @josevalim! Thanks for your feedback. One question I have and I'm not sure where this discussion should go...
The documentation for transactions is currently scattered across Ecto, Postgrex, MyXQL, Tds and DBConnection and I think we need to think about a strategy to document it that avoids repeating the same information over and over.

Ecto links to its own shared options
Postgrex docs lists some options
MyXQL links to the options present in DBConnection
Tds doesn't have documentation about it

I think we should find some what's common in all these layers and document only what's different between them. But in your experiences, what would be the best way to do it?
PS.: I wonder if this isn't the case for other options and this is actually a much deeper work to tidy up the docs 🙃.

We should generally document all useful options in Ecto, except for the places we explicitly link to the adapter. But some options don't make sense to discuss in Ecto, because DBConnection is more general purpose than Ecto and some options are not useful for the Ecto case. I think :mode should be documented in Ecto though.


Exception handling

Reported by anonymous on 14 Dec 2012 21:38 UTC
The official FMU Checker 2.0a1 (on Windows 7) crashes if the loaded FMU DLL gives an exception like an access violation or floating point overflow. The FMU Checker shall catch such exceptions and shall give a hint which function threw which kind of exception (if possible), e.g.
Exception in Model.dll: Model_fmiSetTime.
Access violation at address 012345678. Read of address 00000000.

or simply
Exception in Model.dll:
Floating point division by zero.

.

Migrated-From: https://trac.fmi-standard.org/ticket/119

Comment by iakovn on 17 Dec 2012 21:48 UTC
I don’t see any proper use case for this feature. FMU that raises such exceptions should be run under a debugger to track error sources. The generated log from the checker will give a good indication where the error might be.
On the technical side: exceptions are not propagated via DLL interface. Catching those as signals may interfere with internal exception handling in the FMU and will actually complicate debugging. A way around may be to load FMU in a separate process but that would also make proper debugging more cumbersome.
I’d put resolution as “will not fixed”

Comment by anonymous on 18 Dec 2012 12:19 UTC
I suppose a clean program termination would always be professional. That's why I suggested it. But you are right it is not needed at all as FMU Checker runs on one FMU only and not on a whole bunch of them to check in series. Thus you can keep it crashing and I do the debugging.

Comment by jakesson on 18 Dec 2012 13:34 UTC
Replying to [comment:2 anonymous]:

I suppose a clean program termination would always be professional. That's why I suggested it. But you are right it is not needed at all as FMU Checker runs on one FMU only and not on a whole bunch of them to check in series. Thus you can keep it crashing and I do the debugging.

The ambition of the checker is certainly that it should be a professional tool useful for FMU-generator implementors. As I understand your response, you are not content with the reply Iakovs post. There were technical arguments brought forward by Iakov against the original feature request in this ticket - I therefore kindly ask you to comment upon these if there are still concerns.

Comment by anonymous on 18 Dec 2012 16:25 UTC
Sorry, there should not be any offense here.
Actually, what I did, is to use log level 6 to see where it crashed, then noticed that it is inside one of our DLLs required for the FMU DLL, then compiled that one with debug information and then found the reason for the crash.
I mean this way is always possible. However, if you see FMU Checker crashing, you never know if it is the FMU Checker itself or one of the loaded DLLs that leads to the crash. First sight is likely to be: Damn, FMU Checker always crashes. If there would be some indication that it is not FMU Checker having the access violation would be not only more professional but also keeps a good light on the tool.
From technical point of view: I know tools that do the exception handling like I suggested above. The above examples actually came from popluar file manager Total Commander that can load external plugins but certainly should not crash if the plugin fails. At least there is an exception message that the error is within the plugin. Always good to know.
Anyway, it is just a nice-to-have wish and it is technically possible.

Comment by iakovn on 18 Dec 2012 22:42 UTC
Replying to [comment:2 anonymous]:

But you are right it is not needed at all as FMU Checker runs on one FMU only and not on a whole bunch of them to check in series.

Actually, it does work with a bunch when coupled with ctest. If you build the checker  yourself then you could set FMUCHK_TEST_FMUS_DIR to a directory with your FMUs. Running "make test" or building RUN_TESTS target in VisualStudio will run the checker on all the FMUs.

Thus you can keep it crashing and I do the debugging.

The whole point is that it should not crash. It needs to be debugged if it does. If its checker's fault - report the bug and we fix it ASAP.

I know tools that do the exception handling like I suggested above.

The only safe way is to load the FMU binary in a separate process. This will make checker slower which is undesirable. Performance is specifically important if you run it in a batch on many FMUs (e.g., as mentioned above).
We'll keep this on the wish list but not as critical.

Comment by jakesson on 19 Dec 2012 08:09 UTC
I think that both approaches have merits. I can certainly see the value of catching FMU exceptions in a clean way without the checker crashing. In this way, the user gets guidance in debugging inside the FMU, and we avoid uncertainty about weather the error is in the checker and in the FMU. On the other, hand, if catching exceptions complicates debugging, then it would be good to be able to run without this feature.
Perhaps the following approach would combine the two aspects:

By default, the checker catches exceptions from the FMU and report them in a clean way. To the extent there is a performance penalty associated with this, it should be acceptable when the checker is run from the command line. The printed message should make a reference to the mode of operation described in 2. below.
There is an argument to turn the catching of exceptions off, in order to more easily debug FMUs. This may also be the desired mode of operation for batch runs.

Since the conclusion so far is that this is not critically needed, we'll put it on the todo list, still, feel free to comment in order for us to have a good design when we get around to implement it.

Comment by anonymous on 19 Dec 2012 12:04 UTC
Johan, thank you for your conclusion.
I did not know that there is a (hidden?) option to run FMU Checker on a directory and I do not know how it is done. But for this scenario it is a reasonable idea to not crash at one of the FMUs and keeping others not checked.

Comment by iakovn on 8 Jan 2013 22:08 UTC
Replying to [comment:7 anonymous]:

I did not know that there is a (hidden?) option to run FMU Checker on a directory

Sorry, I was not clear in my post.
The option is for the checker's build system and not for the checker executable. It is mentioned in BUILD-FMUChecker.txt.
You can specify a "test FMUs" directory when configuring a build. Running "make test" or building RUN_TESTS target in VisualStudio will run the checker on all the FMUs in this directory. The wrapper program (ctest) will report any unhandled exceptions. TestOutput sub-directory in your build tree will contain output files (logs and csv) for all the cases.

Comment by andreas.junghanns on 12 Nov 2015 12:33 UTC
This is aksing to extend the scope of the checker and is currently not urgent (albeit nice to have).


Enhance reliability of how we make requests and parse errors

Description

References

Testing

[x] This change adds test coverage for new/changed/fixed functionality

Checklist

[x] I have read and agreed to the terms within the Auth0 Code of Conduct.
[x] I have read the Auth0 General Contribution Guidelines.
[x] I have reviewed my own code beforehand.
[x] I have added documentation for new/changed functionality in this PR.
[x] All active GitHub checks for tests, formatting, and security are passing.
[x] The correct base branch is being used, if not main.

Codecov Report

Merging #108 (25cf36d) into main (7fd1c74) will increase coverage by 0.41%.
The diff coverage is 70.00%.

@@            Coverage Diff             @@
##             main     #108      +/-   ##
==========================================
+ Coverage   94.75%   95.16%   +0.41%
==========================================
  Files          37       37
  Lines        5799     5795       -4
==========================================
+ Hits         5495     5515      +20
+ Misses        244      226      -18
+ Partials       60       54       -6

Impacted Files
Coverage Δ

management/user.go
83.06% <41.66%> (-0.74%)
:arrow_down:

management/management_request.go
85.62% <63.15%> (+1.51%)
:arrow_up:

management/anomaly.go
56.52% <66.66%> (+6.52%)
:arrow_up:

management/guardian.go
93.07% <66.66%> (ø)

management/branding.go
77.77% <100.00%> (+8.85%)
:arrow_up:

management/job.go
79.06% <100.00%> (+15.13%)
:arrow_up:

management/management_error.go
100.00% <100.00%> (+30.00%)
:arrow_up:

... and 2 more

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


Implement 'Neighbourhood events' API call

Has this one also been closed by the latest PR?

The commit included the tests and implementation for this API call. if @FlyingTopHat agrees can be closed.

Yep, I agree. Closed.


upgrade date-fns to v2

fixes #104

@egoist can this be merged?

any news on this? i think the old version of date-fns being used is the reason localization is entirely broken for me here.

I would appreciate to see the integration happen, too.
Anything I could do to support this?

The ball is in @egoist ground, but I think they're busy.
We should just wait to see any reaction from their side.
Also others can do further commits if it's required. Because I'm not involved in this pull request anymore.


fix shader compilation error reporting for non-wgsl shaders

in #3289 I accidentally only logged errors for wgsl shaders, this PR expands the error reporting the the other supported shader types.

bors r+


Sugarloaf website vs liftie status discrepancies

When Sugarloaf's website indicates a lift status as hold, it's being returned as 'open' through liftie. If I can figure out why, I'll put together a PR.

https://www.sugarloaf.com/conditions-and-cams
https://liftie.info/resort/sugarloaf

When inspecting the Sugarloaf website, it seems the hold indicators use the alt text 'Open' as demonstrated in the screen capture. If I'm understanding how the scraper captures data, it would seem this alt text is likely what is causing the reported discrepancy.

Yup - it's using alt now, but it's fairly simple to change it to use src instead. It would need a regex to extract the interesting part of the image URL. Something like:
attribute: 'src',               // change from alt to src
regex: /-(\w+)\.png$/i   // capture part between a hyphen and .png

The parser data is in libtools/boyne.js and the parser is shared with couple of other Boyne resorts. It would be good to check if they changed it for all of them.
Let me know if you want to give it a try.

Thanks for taking care of this!


Concurrency issue with provider <-> startServer routine

After commit<PHONE_NUMBER>0b354367790966729cf4f35b80a7f4 running traefik may cause a runtime error in some cases.
Steps to reproduce:

$ traefik fixtures/file/simple.toml

Since Go doesn't guarantee when a routine is executed, the serverLock sync.Mutex introduced in PR #126 doesn't prevent the following:
Main locks the serverLock and prepares the initial server
	serverLock.Lock()
	srv, er = prepareServer(configurationRouter, globalConfiguration, nil, loggerMiddleware, metrics)

Meanwhile a provider wants to create a new server and gets blocked on the serverLock
				newConfigurationRouter, err := LoadConfig(newConfigurations, globalConfiguration)
				if err == nil {
					serverLock.Lock()

Main dispatches the initial startServer routine and unlocks the mutex
	go startServer(srv, globalConfiguration)
	serverLock.Unlock()

Provider routine gets unblocked and then passes srv to prepareServer() before the initial startServer routine for srv has been executed. As a result oldServer.HijackListener() is invoked on a server that doesn't have a listener yet.
DEBU[2015-11-24T17:24:55Z] Global configuration loaded &{Port::80 GraceTimeOut:10 AccessLogsFile: TraefikLogsFile: Certificates:[] LogLevel:DEBUG ProvidersThrottleDuration:2s Docker:<nil> File:0xc820132340 Web:<nil> Marathon:<nil> Consul:<nil> Etcd:<nil> Zookeeper:<nil> Boltdb:<nil>}
INFO[2015-11-24T17:24:55Z] Starting provider *provider.File &{baseProvider:{Watch:false Filename:fixtures/file/simple.toml}}
INFO[2015-11-24T17:24:55Z] Preparing server
INFO[2015-11-24T17:24:55Z] Configuration receveived from provider file: &types.Configuration{Backends:map[string]*types.Backend{"backend1":(*types.Backend)(0xc8201333a0), "backend2":(*types.Backend)(0xc820133860)}, Frontends:map[string]*types.Frontend{"frontend1":(*types.Frontend)(0xc820133cc0), "frontend2":(*types.Frontend)(0xc820164040)}}
INFO[2015-11-24T17:24:55Z] Last file config received more than 2s, OK
DEBU[2015-11-24T17:24:55Z] Creating frontend frontend1
DEBU[2015-11-24T17:24:55Z] Creating route test_1 Host:test.localhost
DEBU[2015-11-24T17:24:55Z] Creating backend backend2
INFO[2015-11-24T17:24:55Z] Creating load-balancer drr
INFO[2015-11-24T17:24:55Z] Creating server server2 http://<IP_ADDRESS>:80
INFO[2015-11-24T17:24:55Z] Creating server server1 http://<IP_ADDRESS>:80
DEBU[2015-11-24T17:24:55Z] Creating frontend frontend2
DEBU[2015-11-24T17:24:55Z] Creating route test_2 Path:/test
DEBU[2015-11-24T17:24:55Z] Creating backend backend1
INFO[2015-11-24T17:24:55Z] Creating load-balancer wrr
INFO[2015-11-24T17:24:55Z] Creating server server1 http://<IP_ADDRESS>:80
INFO[2015-11-24T17:24:55Z] Creating server server2 http://<IP_ADDRESS>:80
INFO[2015-11-24T17:24:55Z] Creating circuit breaker NetworkErrorRatio() > 0.5
INFO[2015-11-24T17:24:55Z] Preparing server
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xb code=0x1 addr=0x18 pc=0x567830]

goroutine 9 [running]:
github.com/emilevauge/traefik/vendor/github.com/mailgun/manners.(*GracefulListener).Clone(0x0, 0x0, 0x0, 0x0, 0x0)
	/go/src/github.com/emilevauge/traefik/vendor/github.com/mailgun/manners/listener.go:105 +0x40
github.com/emilevauge/traefik/vendor/github.com/mailgun/manners.(*GracefulServer).HijackListener(0xc8201762c0, 0xc82000fe60, 0x0, 0x0, 0x0, 0x0)
	/go/src/github.com/emilevauge/traefik/vendor/github.com/mailgun/manners/server.go:197 +0x46
main.prepareServer(0xc82015ce10, 0xc8200fd810, 0xc8201762c0, 0xc82016fed8, 0x2, 0x2, 0x0, 0x0, 0x0)
	/go/src/github.com/emilevauge/traefik/traefik.go:285 +0x827
main.main.func2(0xc82000e9c0, 0xc8200fd810, 0xc8200a3350, 0xc8200240e8, 0xc8200240e0, 0xc8200240f8)
	/go/src/github.com/emilevauge/traefik/traefik.go:133 +0x68c
created by main.main
	/go/src/github.com/emilevauge/traefik/traefik.go:150 +0xae2

goroutine 1 [chan receive]:
main.main()
	/go/src/github.com/emilevauge/traefik/traefik.go:214 +0x170f
(...)

/cc @vdemeester @emilevauge

This has been fixed by a server.go refactoring ;)

🎉 😄  @emilevauge


Storage Class configuration in ibm-object-storage-plugin-2.2.13

We updated ibm-object-storage-plugin from version 2.2.12 to 2.2.13 recently without changing any configuration settings of the plugin. After applying the update newly created PVCs threw an 404 error for not beeing able to locate our S3 buckets anymore. It seems version 2.2.13 contains undocumented changes to the way Ibm Io Object Storage Endpoint and Ibm Io Object Storage Class are set.
In version 2.2.12, regional storage classes (like "ibmc-s3fs-smart-perf-regional") were set to use https://s3.private.eu-de.cloud-object-storage.appdomain.cloud as Ibm Io Object Storage Endpoint and eu-de-smart as Ibm Io Object Store Storage Class.
In version 2.2.13, the same storage class is now using https://s3.private.mil01.cloud-object-storage.appdomain.cloud as Ibm Io Object Storage Endpoint and mil01-smart as Ibm Io Object Store Storage Class.
What we expected to happen:
A breaking change like this should at least be documented in the change logs (https://cloud.ibm.com/docs/containers?topic=containers-cos_plugin_changelog) and possibly even be reflected in an increase in minor version. Also in IBM terms, a region would be "eu-de" and not "mil01", which is a single datacenter (see https://cloud.ibm.com/docs/cloud-object-storage/basics?topic=cloud-object-storage-endpoints#endpoints-region). Although it might be useful to be able to select a single datacenter endpoint, this should be a new storage class, in my opinion.

Hi @Hendrik-LGLN Thank you for raising the issue and bringing it our notice.
Somehow we slipped this upgrade verification in our recent chart release.
As you mentioned, there are changes wrt regional storageclasses in 2.2.13 charts, upgrade action will fail for the plugin. Users must uninstall the current charts and reinstall v2.2.13.
This change will have minor impact for the customers using single site clusters as the regional storageclasses will now point to singlesite endpoint instead of regional endpoints.  So the existing buckets created with regional endpoints cannot be accessed from single site endpoint.  Users will see below error while trying to create new PVC with existing buckets in 2.2.13 chart.
 status code: 404, request id: 6f027f33-fe4c-4576-b8eb-d90ad84d59fd, host id:
  Normal   Provisioning        23s (x12 over 5m15s)  ibm.io/ibmc-s3fs_ibmcloud-object-storage-plugin-6b47474f5b-bxgtc_61ed4300-b1f9-43df-85d7-ffdb2ddcaeb9  External provisioner is provisioning volume for claim "default/regionalpvc"
  Warning  ProvisioningFailed  23s (x3 over 83s)     ibm.io/ibmc-s3fs_ibmcloud-object-storage-plugin-6b47474f5b-bxgtc_61ed4300-b1f9-43df-85d7-ffdb2ddcaeb9  (combined from similar events): failed to provision volume with StorageClass "ibmc-s3fs-smart-perf-regional": regionalpvc : cgi5lj0w0s2a56ua5gc0 :cannot access bucket ambregionalbucket: NotFound: Not Found
           status code: 404, request id: b6c9439d-33c6-4318-8d03-7415c1a47ec1, host id:

Workaround: In 2.2.13 chart ,User can add annotation: [ibm.io/endpoint](http://ibm.io/endpoint): <regional-endpoint> in PVC Spec to use existing bucket (created using regional endpoint in earlier chart versions) to create new PVC.
Steps to find the regional endpoint of existing bucket:
From IBMCloud UI, select appropriate Cloud Object Storage Instance where your bucket resides. Click on the Bucket from the list and navigate to Configuration -> Endpoints. Choose an endpoint from the list and add as annotation in PVC Spec.
NOTE:

Existing buckets with existing workloads will work seamlessly with no impact.
In any case, there is no data loss for users.

Chnagelog will be updated asap.
Thank you.

Thanks, works for me!


VC Jwts in tests are wrong

https://github.com/TBD54566975/web5-go/blob/main/vc/vcjwt_test.go
If we look at the "correct" test in the vcjst_test.go we see that this one passes:
{
  "exp":<PHONE_NUMBER>,
  "iss": "did:jwk:eyJrdHkiOiJPS1AiLCJjcnYiOiJFZDI1NTE5IiwieCI6IlhBZjdfbV9rYkdlYUFqXzZoQ2pVTkNhTFRiQzNCcVdhNTZERHowbXpMUXMifQ",
  "jti": "abcd123",
  "nbf":<PHONE_NUMBER>,
  "sub": "did:jwk:eyJrdHkiOiJPS1AiLCJjcnYiOiJFZDI1NTE5IiwieCI6ImtNRlVUU0ZZbkJDQVhFWUdGWjZ3Z3RTWVY3enQtcFNFZUtsN1NvaTNrX2MifQ",
  "vc": {
    "@context": [
      "https://www.w3.org/2018/credentials/v1"
    ],
    "type": [
      "VerifiableCredential"
    ],
    "issuer": "",
    "credentialSubject": {
      "firstName": "Randy",
      "lastName": "McRando"
    },
    "issuanceDate": ""
  }
}

However this should fail,     "issuer": "", and     "issuanceDate": "" should not be empty strings, but should either be the corresponding values to the iss and nbf, OR they should not exist at all.
I think some json flag needs to be turned on so if they are empty strings to just not produce them at all

Hi @nitro-neal, I was giving this one a try, but don't think the test case is wrong.
Here, the Decode function replaces issuanceDate with the nbf value, and issuer with the iss value from the JWT-specific properties (following the mentioned spec):
https://github.com/TBD54566975/web5-go/blob/24a79d937281dfdca1f66a1095eacfa16019b55c/vc/vcjwt.go#L64-L66
https://github.com/TBD54566975/web5-go/blob/24a79d937281dfdca1f66a1095eacfa16019b55c/vc/vcjwt.go#L80-L82
Actually, if we comment these lines out, we get the test to fail, since the DecodedVCJWT Verify method actually checks whether these fields are empty on the resulting vc field.
Maybe adding a test vector to cover this scenario will help with clarification:
{
	description: "jwt-specific properties replace vc model properties",
	input: "<jwt with empty properties to get replaced>",
	errors: false,
},

On a related note, since I was looking into this, these two sets of tests seem to have some overlapping:

TestDecode and TestVector_Decode
TestVerify and TestVector_Verify

Not sure if they're indeed duplicated (nor which would be the "correct" way that the project is following). Is it worth consolidating? I can send a PR, if it makes sense, wanted to grab an easy first issue.


(Un)escape more characters

As far as I can see, polib currently only "Escapes the characters \\\\, \\t, \\n, \\r and "".
msgfmt apparently supports

Table 15-1. Escape Sequences

\n
newline

\t
tab

\v
vertical tab

\b
backspace

\r
carriage return

\f
formfeed

\
backslash

"
double quote

\ddd
octal bit pattern

\xHH
hexadecimal bit pattern

In gimp-help we have come across the vertical tab which I would like to detect when parsing with polib.
This is currently not possible because as far as I can see I cannot distinguish between a real vertical tab \v and \v inside a path (e.g. c:\\various):

\v is not unescaped and stays \v
c:\\various is unescaped as c:\various

It seems that gettext also is not happy finding \a. It would be nice if that could also be handled.
../../gimp-help/po/sv/using.po:617: warning: internationalized messages should not contain the '\a' escape sequence


Got something to share?

If you have example ScriptCraft scripts you want to share with others, please post a comment here with a link to the script (assuming it's on github or elsewhere)

We are about to open source Minecraft for Type 1 Diabetes, which we developed with ScriptCraft. As the first step, we've open-sourced our Scriptcraft Modular Architecture, which allows you to dynamically load Scriptcraft Plugins that live in their own repos: https://github.com/Magikcraft/scriptcraft-modular-arch

Intellisense in Visual Studio Code, TypeScript transpilation, a Yeoman generator, support for npm modules, and preconfigured docker images for Scriptcraft on both Bukkit and Nukkit:
https://blog.magikcraft.io/how-to-mod-minecraft-without-java-f076ddaec01c


Settings in Docker image not aligned with selected country

We download an image for BC, with country code DK.
We get the correct image setup, but the current settings are for US.
We expected the settings to follow the country-specific settings, at least Region and Time Zone.
Function we use for call:
$artifactUrl = Get-BCArtifactUrl -country dk -select Latest
New-BCContainer -accept_eula:$accept_eula                  -accept_outdated: $accept_out
-containername $containername                  -artifactUrl $artifactUrl
-auth Windows                  -alwaysPull
-includeAL                  -usessl:$false
-updateHosts                  -assignPremiumPlan
-shortcuts Desktop                  -additionalParameters $additionalParameters
-licenseFile 'C:\Naveksa\5692763_BC16_300620.flf'
Setup-BCContainerTestUsers -containerName $containername -password $credential.Password
The version we get downloaded is correct:

Settings are as follows:

We expected the settings to be like this:

Is there some docker commands that we are missing, which can assure correct settings,
instead of having to change them manually each time ?

I think this is your browser settings.
If I create a DK container and open the web client in Edge - I get english settings (browser is english - managed by MS)
If I then create a new DK container and open the Web Client in Chrome - I get Danish.
First time you login as a user, the user settings are taken from the browser settings as far as I know.


Using gopkg style dependency management creates issues

Hi,
We have been using sarama-cluster for a while and it works pretty good. However using gopkg style dependencies creates a lot of issues such as problems when trying to use the mock subscribers/producers to write tests. (https://github.com/Shopify/sarama/issues/552).
Would you consider switching to master imports and letting users be able to use their own dependency management ? ( such as vendoring or gopkg or whatever makes sense for them )

Since vendoring is now supported natively, it's probably a good idea, could you submit a PR?

Closed via #33


No matching key. session or pairing topic doesn't exist:

No matching key. session or pairing topic doesn't exist:
walletconnect_flutter_v2: ^2.0.7
I keep waiting when I call wcClient.approveSession
ApproveResponse? respone;
try {
// Have been waiting ???
respone = await wcClient.approveSession(
id: id,
namespaces: map,
relayProtocol: relay.protocol,
);
} catch (e) {
debugPrint("id: $id approveSession error: $e");
}
Subsequent events cannot be received

There is a small chance that it will pass. Most of them will make an error

this is class Pairing;

But there was a strange problem. When I'm in debug breakpoint mode, I get the result, but if I don't break the point, I don't get the result

Looks like there was some kind of process mix-up
It succeeds because the breakpoint stops, allowing the other code to go first.
Without breakpoints, there is a problem with the process

Does deleting that await actually resolve the problem? Or does it still exist?
I was aware of this issue, and thought that I had fixed it with my most recent changed (At least, I had some tests where they would fail because of it, but 2.0.7 fixed those).
So, I guess, does deleting the await actually fix the problem without the breakpoints?
I can't imagine that it would.

I need more information.
Please provide the following:

The platform your dApp/wallet is running on
The dApp/wallet you are trying to communicate with
Flutter and dart version you are using

I ran some more tests.
If there is a breakpoint, the message can be received smoothly.
If there is no breakpoint, it cannot be received.
I initially thought it was because the breakpoint was affecting the asynchronous flow,
But when I put the breakpoint on any line, I also get a message.
This strikes me as strange.
It works on ios, but andoird will have problems
I run the wallet
I am communicating with DApp demo of WalletConnect's official website,
I also corresponded with my own DApp
Flutter 3.10.1 • channel stable • https://github.com/flutter/flutter.git
Framework • revision d3d8effc68 (2 weeks ago) • 2023-05-16 17:59:05 -0700
Engine • revision b4fb11214d
Tools • Dart 3.0.1 • DevTools 2.23.1

Does deleting that await actually resolve the problem? Or does it still exist?
I was aware of this issue, and thought that I had fixed it with my most recent changed (At least, I had some tests where they would fail because of it, but 2.0.7 fixed those). When I was resolving the issue it, it was caused because the response from the relay would be received before I could even wait for its response, which is why the relayClient.publish is not awaited.
So, I guess, does deleting the await actually fix the problem without the breakpoints? I can't imagine that it would.

Delete wait, cannot solve problem...
Because I added a break point. I thought it was working

have breakpoint:
_onMessageEvent: eb735c803c7dc1599b293fa05ec460ec3a416c02359a3b4687a241fcf47b3b0e AMwixcbBBVoUZbvbxbwuvkk/SzPdoCNQusBjJFnzQpJHsE+gYzp3FN/g0MXgFRrgqq5EtWJKdUPP26YQ+GjU4kcPP6GMD5dgO9rxmvsYKX+oRGuev07JDG7+URYq/3YBGVfHvSB4ck79ziHb11CqrFOKy9RJ1dRPiEFTy/qHqNDW815NxSM0BvaqeLR+jPuguylFi+ERtEok4Go9CLtxszUHcGgGtQXI58MZs3qANvoxipjKU1wxaVVeqrh6uVvMx7NosJmYpBljcXx/kyU/bJggIiXJvhJAK7QSste/+oTlQd57VKL2Nl/xVS/s2vXLACWthqHeWK/D8SSF+VmpozQLnD5omOCcbBeG0XpNZ4N4WQ25RRtWYE0C6/rxhpyE1FA1fecU903dpluIGAqs2fChUeTTa1wngemcFwNNN29WiqmSHMltKEgo/P8B9cavnQRX8sSehNZS9PVYvvCoUV4Ul0WL+OPtkexJxBXJKXx5k2kHvrK0TCRbucx7uPRehqvGrDnsO0ibQtEdNxo/qavIr/CVZ4QqCHBVDJgSbVHcb5ppP4P1rWzNsTIcIBhFwqMKkjyZ1sSfL9Pn3XBWQum8KwIFu9R2vS4ziNpvhghq6mP0qKVux0zQt94NVgJWmOFbL+uMcPhA2P3kfmooVE/Go/OQaoT6dh5b3VcZS1D6hC04j67PmHU9uNO+srBBYQ1SGfKTg6gkuOL2IzLDUps+DEKXAdMyityjLeTnNEeNY3KTWnkINPEpJpXavkpf1jBqY/YiIYlhtcGOYcYJxwzeqTC6UA6iQXZpj11W6F+n124WokIIgb8YWnnNdXA2Sy+y0y5Hicn9v9xknHTfnX8Bk9oEYhLAMqc3ThxzTXAcay6PGdNhEHosOTtwFNAfohLNilUNLRrxPAaiQ2Y6mt<…>
flutter: {"id":1685632991206264,"jsonrpc":"2.0","method":"wc_sessionPropose","params":{"requiredNamespaces":{"eip155":{"chains":["eip155:5"],"methods":["eth_sign","personal_sign","eth_accounts","wallet_watchAsset","wallet_switchEthereumChain","wallet_addEthereumChain","net_version","eth_sendTransaction","eth_signTransaction","eth_signTypedData","wallet_requestPermissions","eth_requestAccounts"],"events":["accountsChanged","chainChanged","disconnect"],"rpcMap":{"5":"https://rpc.walletconnect.com/v1/?chainId=eip155:5&projectId=ccfa173e846329cc001e23fa3ce2e3de"}}},"optionalNamespaces":{"eip155":{"chains":["eip155:5"],"methods":["eth_sign","personal_sign","eth_accounts","wallet_watchAsset","wallet_switchEthereumChain","wallet_addEthereumChain","net_version","eth_sendTransaction","eth_signTransaction","eth_signTypedData","wallet_requestPermissions","eth_requestAccounts"],"events":["accountsChanged","chainChanged","disconnect"],"rpcMap":{"5":"https://rpc.walletconnect.com/v1/?chainId=eip155:5&project<…>

The content is different. I don't know why

@LvDj Do you have a public access point for your dapp I could use?

I justed pushed out version 2.0.8, please check if it has resolved the issue.

我刚刚推出了2.0.8版本，请检查它是否解决了问题。

no,still have this problem

@BrianCliton
Does it happen for every dapp you work with?
Please provide examples that I can test with. I need more information.

I can run this app: https://react-app.walletconnect.com/
Along with the example wallet and the connection is established and the session is created.
I can then request from the dapp and sign with the example wallet.
Every dapp I have tested with (That supports v2) that my example wallet can connect to establishes a connection.
So far I haven't been able to recreate this issue.
So I need more information.
Please provide the dapp you are using along with the steps you are taking to break things.

@LvDj @BrianCliton I also encountered this issue. Starting from last week, I conducted a lot of repetitive and tedious tests and found that the wc_sessionSettle request sometimes does not receive any response, causing the entire future to wait at this step without progressing, which results in the session content not being saved. Therefore, I submitted a pull request to solve this issue and hope that you can help test it out. I am looking forward to your response.
dependency_overrides:
  walletconnect_flutter_v2:
    git:
      url: https://github.com/iota9star/WalletConnectFlutterV2.git
      ref: "4c8a147"

What did you use to test it?
The changes you've made will improve the function (Based on my understanding of them), but will not actually resolve the issue of no wc_sessionSettle.
Please give me the tools you were using to test this. I have been unable to reproduce this on my end.

Didn't mean to close this, but I merged the changes.
I don't think this is actually resolved by the changes, I believe there is a deeper issue somewhere.

I think the deeper issue is that WebSocket relies heavily on network stability and code robustness to successfully send and receive messages. To complete a request during the pending process, Completer/Promise is used. If a response cannot be received, it will wait here indefinitely. In fact, we can easily identify the problem from the code.

The code above is before submitting the PR, and we can see the part highlighted in red circle which completes the session request. After it finishes the request, it will execute the part in the green circle below. However, a problem arises here: completing the part in the red circle does not necessarily mean that the DApp has successfully received the message, or even if it has received the message, it may not yet have the topic held locally. When the request in the green circle arrives and cannot find the corresponding topic, the DApp will not respond. At this point, the green part will never get a response and will continue to wait indefinitely in this location.

I think it's necessary for us to add timeout interrupts to some critical methods in WalletConnect, so that even if there are problems, the code can continue to run normally instead of waiting indefinitely.

I can run this app: react-app.walletconnect.com Along with the example wallet and the connection is established and the session is created. I can then request from the dapp and sign with the example wallet.
Every dapp I have tested with (That supports v2) that my example wallet can connect to establishes a connection.
So far I haven't been able to recreate this issue.
So I need more information.
Please provide the dapp you are using along with the steps you are taking to break things.

It is easy to reproduce this issue in areas where the WalletConnect network node is not very stable. If I do not use a VPN tool, then out of ten requests, this problem may occur three or four times.

I have never had this happen and I've tested hundreds of times. I wonder why that is.
I understand unstable internet connections make things rough, but using websocket/TCP should remove this issue. We use them because they ensure the complete arrival of a packet.
I believe it is more of a race condition as you've described it.
I'll mark this as closed, but I still feel like the underlying issue hasn't been resolved, the fact that it fails 30-40% of the time is not promising to me.

@Luzzotica I am in China and need vpn to connect to walletconnect. But you must have a direct Internet connection, so I don't know if that has anything to do with it

I can confirm that calling Web3Wallet.approveSession sometimes returns a result and sometimes it does not.
We are in the Netherlands where the (inhouse) dapp and wallet app run on the same top quality internet connection.
I can see the DApp receiving the approve session message but the wallet remains hanging waiting for the response from the Web3Wallet.approveSession call.
This happens 4 out of 10 times approx.


Client sent an HTTP request to an HTTPS server.

Hello! I'm a big fan of this project, but have a question, not a bug.
I use ubuntu-16.04
npm 6.14.4
node v12.16.2
go version go1.13.4 linux/amd64
chrome version 81.0.4044.122
I build and run server without TLS certificate successfully.
But when I add TLS on my server
openssl req -nodes -x509 -newkey rsa:4096 -keyout key.pem -subj "/C=US/ST=Oregon/L=Portland/O=Company Name/OU=Org/CN=dupeljan.fvds.ru:3000" -out cert.pem -days 365
I got answer from http://dupeljan.fvds.ru:3000/ like
Client sent an HTTP request to an HTTPS server.
browser log:
dupeljan.fvds.ru/:1 Failed to load resource: the server responded with a status of 400 (Bad Request)
dupeljan.fvds.ru/:1 Unchecked runtime.lastError: The message port closed before a response was received.
dupeljan.fvds.ru/:1 Unchecked runtime.lastError: The message port closed before a response was received.
:3000/favicon.ico:1 Failed to load resource: the server responded with a status of 400 (Bad Request)
dupeljan.fvds.ru/:1 Failed to load resource: the server responded with a status of 400 (Bad Request)
DevTools failed to load SourceMap: Could not load content for chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/include.preload.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
DevTools failed to load SourceMap: Could not load content for chrome-extension://gighmmpiobklfepjocnamgkkbiglidom/include.postload.js.map: HTTP error: status code 404, net::ERR_UNKNOWN_URL_SCHEME
How to prevent this?

Just realize, that  I used http://dupeljan.fvds.ru:3000/  instead of https://dupeljan.fvds.ru:3000/
It took long time to find out. Sorry for spamming.


retry scenario

At the end of a scenario - run a checkup to ensure validity.
In case the checkup fail, enable running the scenario again

I believe this can be supported by a REPL feature


Added information about Prettier

Looks good to me. A couple of notes:

I tried doing the npx prettier --write <filename> and the first time I got this message:

Need to install the following packages:
<EMAIL_ADDRESS>Ok to proceed? (y)

It worked fine when I said "y". So should the instructions tell us to install that - or just warn that this prompt will happen?

Where the instructions mention running prettier on all files. Maybe we don't want people to do that until we have done a pass on all the files and committed that? I'm not sure how we are planning to go about this to avoid mixing formatting changes with other changes that need reviewing. We have talked about contributors maybe updating their own files? Though some files are common.

I removed the section about updating all files. I also added a note that they may be asked to install Prettier when they run the command.


Node registration changes wip cluster

@jwhonce includes the changes from https://github.com/jwhonce/openshift-ansible/pull/5, has reworked node configuration and registration changes for latest build, and adds update support to bin/cluster for gce.
@jwhonce the aws playbooks will still need to be udpated for these changes as well.

@jwhonce I should note, that I will be submitting a PR for the node registration changes to the master branch, just wanted to get you unblocked by getting the gce changes to you first.


Having test spec name as test name in browserstack

I want to set the test spec name as the test name in browserstack. Below is my browserstack stack config file. I am using protractor.
 exports.makeDefaultCapabilities = function(that) {
  return {
    browserName: 'chrome',
    chromeOptions: {
      prefs: {
        credentials_enable_service: false,
      args: [
        'disable-infobars=true',
      ]
    },
    loggingPrefs: {
      driver: 'WARNING',
      server: 'WARNING',
      browser: 'INFO'
    },
    'browserstack.user': 'xx'
    'browserstack.key': 'xxx',
    'browserstack.debug': true,
  };
};

exports.config = {

  suites: {
    smoke: [
      '*/*.js'
    ]
  },

  SELENIUM_PROMISE_MANAGER: false,
  baseUrl: undefined,
  framework: 'jasmine',
  allScriptsTimeout: 100000,
  getPageTimeout: 100000,
  maxSessions: 1,
  seleniumAddress: 'https://hub-cloud.browserstack.com/wd/hub',

  getMultiCapabilities: function() {
    let that = this;
    return new Promise(function(resolve) {
      let defaults = exports.makeDefaultCapabilities(that);

      let capabilities = [];

      capabilities.push({
        os: 'OS X',
        os_version: 'High Sierra'
      });

      _.forEach(capabilities, function(capability) {
        _.defaultsDeep(capability, defaults);
      });

      resolve(capabilities);
    });
  },

  beforeSession: function(config, capabilities, specs) {
    capabilities.name = specs && specs[0].split('/').pop() || undefined;
  },

  onPrepare: function() {
    jasmine.getEnv().addReporter(failFast.init());
    let reporter = new SpecReporter();
    jasmine.getEnv().addReporter(reporter);
  }
};

The beforeSession hook doesn't update the test name in browserstack as the test spec name. Looking forward for any suggestion. Appreciate your help.
Thanks

Hi, @uinest ! As I understand now results of all specs displayed as one test on BrowserStack?

@IgorSasovets  , the test name is shown as the browser base url. For Instance,  if my test name is login.spec then it is now displayed as xxxx-master.com , I instead want it as login.spec.js

Try to remove baseUrl option from your config file and add shardTestFiles: true to your capabilities

It helped me in similar case but with Sauce Labs


Opening DevTools Console with F12 causes requests to fail when using setRequestInterception(true)

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.8.0
Platform / OS version: Mac OS High Sierra 10.13.6 (17G65)
URLs (if applicable): Multiple (https://cloud.google.com, https://www.evo.com)
Node.js version: v8.11.3

What steps will reproduce the problem?
When running in {headless:false} mode and using setRequestInterception(true),  requests will fail if the DevTools console is opened from within Chromium using F12. The request timeout does not occur if the console is opened at launch using the devtools:true configuration, and does not occur if the setInterceptionRequest(true) is not set.
This issue does not appear to occur in earlier versions (v1.6.2).
(async () => {
    try {
        const browser = await puppeteer.launch({ headless: false });
        var pages = await browser.pages()
        const page = pages[0];

        await page.setRequestInterception(true);
        page.on('request', (req) => { req.continue(); });
        await page.goto('https://cloud.google.com/');
    }
    catch(e) {
        // handle uncaught promise errors
        console.log(e)
    }

})();

Launch puppeteer with headless:false
After initial page load, open devtools console with F12
Refresh page

What is the expected result?
Requests complete.
What happens instead?
Requests fail, typically with Navigation Timeout Exceeded error.

seeing same behavior

@clwheeler works just fine for me with Puppeteer v1.17.0. Since v1.8.0, we changed a lot in request interception - so please give it another try.

seeing same behavior, cant intercept posts

@nhhockeyplayer I'd appreciate if you file a separate issue with a code snippet that reproduces the behavior for you, together with the node.js / puppeteer / chrome versions information. Thanks!

This seems to be resolved in 1.17. Thank you!


Latest Version(4.0.7)can't return the total progress number when load remote pdf file but can return total progress number when load local pdf file

 - vue-pdf version ( 4.0.7 )
 - vue.js version ( 2.5.2 )
 - webpack version ( 3.6.0 )
 - browser version ( chrome 74.0.3729.169 )
 - OS version ( windows 10 )

Hi, FranckFreiburger! I got a problem,  I can't get the total progress number when use "createLoadingTask" to load remote pdf file, but can return total progress number when load local pdf file . When load remote pdf file, total number is undefined , and when it done, total return a number.
this is the log when load remote file
this is the log when load local file
Because my pdf file contains chinese font,  so I have to use "createLoadingTask" to load pdf file. The part of code is as follows：(I use '/' to split the editor sensitive tags, like '<div' or '<//pdf>' etc)
------------------------------------template
'</div
style="background-color: green; color: white; text-align: center"
:style="{ width: loadedRatio * 100 + '%' }">{{ Math.floor(loadedRatio * 100) }}%
<//div>
<pdf
ref="myPdfComponent"
:src="src"
:page="currentPage"
@num-pages="pageCount = $event"
@page-loaded="currentPage = $event"
@loaded="initPage()"
@progress="loadedRatio = $event"
style="width: 100%"><//pdf>'
--------------------------------------script
import CMapReaderFactory from 'vue-pdf/src/CMapReaderFactory.js'
mounted () {
var loadingTask = pdf.createLoadingTask({
url: './static/pdfFileName.pdf',
CMapReaderFactory
})
loadingTask.onProgress = progressData => {
console.log(progressData)
this.loadedRatio = progressData.loaded / progressData.total
}
this.src = loadingTask
}
Is it won't support return progress number when load remote pdf file?
Thank you for your time！
I'm sorry for my poor typesetting, because it's the first time to use GitHub to ask questions, I haven't learned to use it yet, and my English is not very good.

Has this problem been solved?


Any idea when the PAFPN neck will be released?

Just curious otherwise I can submit a PR myself on this.

Just curious otherwise I can submit a PR myself on this.

Do you achieve better results using Path Aggregation Network?
I also tried expect for adaptive ROI pooling, but got no gains on r50 baseline.

Sorry for the delay and our team is now busy with the CVPR deadline. We will release PAFPN as well as some other components (RetinaNet, Cascade R-CNN, etc.) after CVPR.
For the performance issue, we may need to seek help from the authors. Btw, the authors released an official repo of PANet, which uses GroupNorm and achieves better performance.

@iceload123 @CrazySherman @hellock Have you reproduce the results of PANet on mmdetection ?
It seems PAFPN  only bring 0.1 gain on bbox AP and mask AP,  how about your codes?  how much gain can PAFPN and  adaptive ROI pooling  bring respectively?

Any updates or any ideas about the performance of pafpn?
recently, I test the pafpn in my code, but get 0.1~0.2 gain on bbox, It confused me.
I noticed that, the resolution of the test image is bigger than usual, which is 1000 as the smaller input.

Hi, could anyone provide the pafpn implementation for mmdetection? I'm not able to find it on the official repo. thanks!

@cqliheping I try to reproduce the PANet, but I get on gain on Faster RCNN. I add the bottom up path, 3x3 conv w/ GN, but still get on gain.

Already support PAFPN after https://github.com/open-mmlab/mmdetection/pull/2392.


Missing dependencies for gs datastore

If you configure METAFLOW_DEFAULT_DATASTORE: "gs" (and of course set up a GCS bucket as datastore root) and then run the metaflow service, metaflow fails on some google package imports.
AFAIK this is impacting DAG and log viewing in the UI, for anyone using GCP.
Example error (copied from UI)
Traceback (most recent call last):
  File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main
    "__main__", mod_spec)
  File "/usr/lib/python3.7/runpy.py", line 85, in _run_code
    exec(code, run_globals)
  File "/root/services/ui_backend_service/data/cache/client/cache_server.py", line 307, in <module>
    cli(auto_envvar_prefix='MFCACHE')
  File "/opt/latest/lib/python3.7/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/opt/latest/lib/python3.7/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/opt/latest/lib/python3.7/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/opt/latest/lib/python3.7/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/root/services/ui_backend_service/data/cache/client/cache_server.py", line 301, in cli
    Scheduler(store, max_actions).loop()
  File "/root/services/ui_backend_service/data/cache/client/cache_server.py", line 199, in __init__
    maxtasksperchild=512,  # Recycle each worker once 512 tasks have been completed
  File "/usr/lib/python3.7/multiprocessing/context.py", line 119, in Pool
    context=self.get_context())
  File "/usr/lib/python3.7/multiprocessing/pool.py", line 176, in __init__
    self._repopulate_pool()
  File "/usr/lib/python3.7/multiprocessing/pool.py", line 241, in _repopulate_pool
    w.start()
  File "/usr/lib/python3.7/multiprocessing/process.py", line 112, in start
    self._popen = self._Popen(self)
  File "/usr/lib/python3.7/multiprocessing/context.py", line 277, in _Popen
    return Popen(process_obj)
  File "/usr/lib/python3.7/multiprocessing/popen_fork.py", line 20, in __init__
    self._launch(process_obj)
  File "/usr/lib/python3.7/multiprocessing/popen_fork.py", line 74, in _launch
    code = process_obj._bootstrap()
  File "/usr/lib/python3.7/multiprocessing/process.py", line 297, in _bootstrap
    self.run()
  File "/usr/lib/python3.7/multiprocessing/process.py", line 99, in run
    self._target(*self._args, **self._kwargs)
  File "/usr/lib/python3.7/multiprocessing/pool.py", line 121, in worker
    result = (True, func(*args, **kwds))
  File "/root/services/ui_backend_service/data/cache/client/cache_worker.py", line 29, in execute_action
    execute(tempdir, action_cls, request)
  File "/root/services/ui_backend_service/data/cache/client/cache_worker.py", line 56, in execute
    invalidate_cache=req.get('invalidate_cache', False))
  File "/root/services/ui_backend_service/data/cache/get_log_file_action.py", line 143, in execute
    results = {**existing_keys}
  File "/usr/lib/python3.7/contextlib.py", line 130, in __exit__
    self.gen.throw(type, value, traceback)
  File "/root/services/ui_backend_service/data/cache/utils.py", line 130, in streamed_errors
    get_traceback_str()
  File "/root/services/ui_backend_service/data/cache/utils.py", line 124, in streamed_errors
    yield
  File "/root/services/ui_backend_service/data/cache/get_log_file_action.py", line 136, in execute
    current_hash = log_provider.get_log_hash(task, logtype)
  File "/root/services/ui_backend_service/data/cache/get_log_file_action.py", line 270, in get_log_hash
    return get_log_size(task, logtype)
  File "/root/services/ui_backend_service/data/cache/get_log_file_action.py", line 177, in get_log_size
    return task.stderr_size if logtype == STDERR else task.stdout_size
  File "/opt/latest/lib/python3.7/site-packages/metaflow/client/core.py", line 1317, in stdout_size
    return self._get_logsize("stdout")
  File "/opt/latest/lib/python3.7/site-packages/metaflow/client/core.py", line 1438, in _get_logsize
    return self._log_size(stream, meta_dict)
  File "/opt/latest/lib/python3.7/site-packages/metaflow/client/core.py", line 1525, in _log_size
    ds_type, ds_root, stream, attempt, *self.path_components
  File "/opt/latest/lib/python3.7/site-packages/metaflow/client/filecache.py", line 148, in get_log_size
    return task_ds.get_log_size(LOG_SOURCES, logtype)
  File "/opt/latest/lib/python3.7/site-packages/metaflow/datastore/task_datastore.py", line 45, in method
    return f(self, *args, **kwargs)
  File "/opt/latest/lib/python3.7/site-packages/metaflow/datastore/task_datastore.py", line 413, in get_log_size
    sizes = [self._storage_impl.size_file(p) for p in paths]
  File "/opt/latest/lib/python3.7/site-packages/metaflow/datastore/task_datastore.py", line 413, in <listcomp>
    sizes = [self._storage_impl.size_file(p) for p in paths]
  File "/opt/latest/lib/python3.7/site-packages/metaflow/plugins/datastores/gs_storage.py", line 195, in size_file
    import google.api_core.exceptions

ModuleNotFoundError: No module named 'google'

It seems to me that the UI backend service is missing google-cloud-storage from its requirements.txt. I applied this change and built a version of the metaflow service image myself, this resolved the issue for me.

@jbvaningen would you like to submit a PR?


FOV maybe?

Works perfectly.
Any chance to implement game FOV change in a similar manner?
Thank you

No plans for this atm, FOV change wouldn't be that important, since it's not a fps game

Low fov is one of the main complaints about the game outside of locked fps.
That’s why i asked.
Or camera distance to be precise.
Currently the camera is really close to the character, which is find on a tv and quite uncomfortable on a pc monitor.

I see. But still, I don't have any plans for that at the moment.

I've seen screenshots without fog back when 1.0 dropped.

FoV options would be great

Is that what you guys mean?

Yes.

I might release that tomorrow then.

This is what I got: https://www.youtube.com/watch?v=cvZf11vtuaw

This is what I got: https://www.youtube.com/watch?v=cvZf11vtuaw Github: https://github.com/lanylow/genshin-utility

Not a big fan of detouring but gj nonetheless, and I heard that there may be a console check in their ac, but I don't know how true is that tho, didn't have time bother reversing

I doubt it, also I think there is no other way of changing the field of view so.

This is what I got: https://www.youtube.com/watch?v=cvZf11vtuaw Github: https://github.com/lanylow/genshin-utility

Are you a god? This look's great.
Thanks!

I doubt it, also I think there is no other way of changing the field of view so.

there is, but still requires detour plus some shellcode

I doubt it, also I think there is no other way of changing the field of view so.

how long have you been using this tho? if its safe for over a week then I might add it with shellcode

I've made it yesterday.


Multi-backend rendering / null backend

I'm currently working on a small cross-plattform rendering framework to cook up small, private projects. One of the core concepts required for this is the possibility to switch rendering backends on-the-fly.
The first step to this is https://github.com/go-gl/gl/issues/85, which allows to have multiple OpenGL versions "initialized" at the same time. However, the deal breaker is this binding at the moment. As it stands, applications can only be compiled with either OpenGL 2 or 3 (+ glfw vs sdl) support - not both.
The long-term solution would be to move the rendering backends around (e.g. to a new backends package, with an unique naming stretegy), so that they can be used in conjunction (they cant at the moment due to deliberately same method names, kept disjunct only by build tags).
A possible short term solution would be to provide a (default?) build tag to compile no rendering backend at all - this would prompt the lib-user to write his or her own, but would also grant more freedom.
Combining both long and short term solutions could prompt extraction of the rendering backends to own projects, which can be maintained on their own (e.g. the planed(?) vulkan backend).

Unfortunately for Nuklear backend is more than just drawing API, it's also input handler with its own logic (e.g. map touch input to X-scroll event), I'm too lazy to refactor the package to move to interfaces. I'd rather will be busy on working on pure-Go UI library which is in developement.

A possible short term solution would be to provide a (default?) build tag to compile no rendering backend at all

Ok, we can add a build tag for that, but since the package is go-getable the default will still be OpenGL3. Would you suggest the name?

which can be maintained on their own (e.g. the planed(?) vulkan backend).

Vulkan backend will be merged here, it won't be a separate package.

Ok, we can add a build tag for that, but since the package is go-getable the default will still be OpenGL3. Would you suggest the name?

Fine by me. Probably something like "nobackend"?

busy on working on pure-Go UI library which is in development

How far along are you with that? /me is wondering.

@tcurdt sorry, not even moved. I have floating focus on things, UI is currently out of focus and I forgot most of the ideas I had in September :(

@tcurdt it's just announced that Cairo now supports GLESv3 rendering backend and may target Vulkan in the future. This triggers me, I think I will take this as my holiday project for end of the year :)
https://blogs.s-osg.org/introducing-cairo-gl-es-v3/


Removal of ISSUE_TEMPLATE

@germa89 @clatapie you should remove the ISSUE_TEMPLATE folder in favor of the pyansys/.github one. That way you'll get the common templates for all PyAnsys libraries. Highly recommended.

I rather not.

I'm happy to port over the other templates (documentation and examples) though.

Why not propose these changes on the main issue template but in a more generalizad way?

The other option would be cooy-pasting the rest of the issue template from our pyansys/.github repo... But I'd personally avoid doing that.. We should try to provide an homogeneous template to all PyAnsys repos...

@RobPasMue the issue is quite specific to help to user to check some stuff first prior to submit the issue. The idea is to alleviate the developers workload. If you have a suggestion on how to use the general template while keeping the detailed information about PyMAPDL, I'm happy to have a look.
I can't really think of a way to be honest. For example the link to the troubleshooting section. It wont be a link then.

There is no way to do that. But the whole point of templates is that all PyAnsys packages use the same templates. It is a matter of being consistent and homogeneous across all packages....
Anyway, if you don't want to change it, you can of course keep it. But in that case, I recommend that you copy-paste the rest of the templates in your folder, because otherwise you won't have access to them...

Close #1888


Adding an option to disable an option to set flow priority as admin only role

This will allow to enable this feature by setting azkaban.disable.admin.only.permission.for.flow.priority to true.
Once this property is set, users who have rights to execute or schedule a flow, will be able to set flowPriority as flow parameter.

Pull Request Test Coverage Report for Build 5326

6 of 12 (50.0%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 40.81%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

azkaban-web-server/src/main/java/azkaban/webapp/servlet/ExecutorServlet.java
0
2
0.0%

azkaban-web-server/src/main/java/azkaban/webapp/servlet/ScheduleServlet.java
0
4
0.0%

Totals

Change from base Build 5322:
0.07%

Covered Lines:
13203

Relevant Lines:
32352

💛  - Coveralls

Because the use of this property is restricted to Azkaban admins only at the time this feature was implemented for the new Dispatch logic (#2140) it was decided to not take into consideration starvation of low priority executions. If more users will have permissions to change priority of an execution I believe we should provide a fix for this issue or at least a way to detect/monitor occurrences of it.
Please refer to #2140 (comment) for one possible solution for starvation of low priority executions.

Good to know!


.aoc join does not have any feedback

Right now, at the Advent of Code season, we have many users doing .aoc join. But did it go through? Was there any error? We do not know, specially if the bot is offline / we have unhandled exception.
My proposal is that, after doing .aoc join for example, the bot will react with a ✅ for example, to tell the user ( and us ) that it was done successfully.
Example:
Instead of this

It will be this

I'm slightly concerned that a green checkmark may convey the impression that the user has now successfully joined the event, instead of conveying that they should have received a DM with instructions on how to actually join the event. We have already had (at least) one user that was slightly confused by what the command did, although this case could be explained by them using the web interface with sounds turned off causing them to not notice the DM.
Why don't we add an :incoming_envelope: (or similar) reaction?

That is true, the green checkmark can be misleading, an envelop / email sending ( like 📧
📨 ) reaction will be much more suitable!

Should we also add a reaction on failure? The bot will already respond with a message on discord.errors.Forbidden, but add_reaction can raise other exceptions as well.

That is actually a good call, I just look at the code ( finally ) and in bot/seasons/christmas/adventofcode.py#L193:L206 it is only catching and handling discord.errors.Forbidden.
One may argue, however, that if the bot does not add a reaction for successfully doing its job, it will be failing, so the reaction for when it fails will be redundant.

Sorry, I'm not sure why I linked add_reaction, I meant to link send.
I'd say it may be worth it to also catch discord.HTTPException and add a ❌. We can then re-raise to make sure the exception propagates to the error handler. I'm not sure.

Adding a red cross can be quite confusing since it is used to delete messages, maybe a crossed emoji (like for the error message if the dm of an infraction failed) will suit better

On a second thought I think I agree with @ikuyarihS - let's just add an envelope reaction if the message successfully dispatches. I will work on this then if that's ok, since people are still joining.


add coverage report

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@1d232e4). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             master     #8   +/-   ##
=======================================
  Coverage          ?   100%
=======================================
  Files             ?      4
  Lines             ?    177
  Branches          ?      0
=======================================
  Hits              ?    177
  Misses            ?      0
  Partials          ?      0

Continue to review full report at Codecov.

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


A problem about clin_ct_body_composition

When I use clin_ct_body_composition, I find that the result will show up as a slice (similar to [ : , : ,20] ).  I don't know why I got this result, can I get the whole body result? It's some logs about my operations.
E:\Anaconda\envs\moose\lib\site-packages\nnunetv2\inference\predict_from_raw_data.py:84: FutureWarning: You are usingtorch.loadwithweights_only=False(the current default value), which uses the default pickle module implicitly. It is possible to construct malicious pickle data which will execute arbitrary code during unpickling (See https://github.com/pytorch/pytorch/blob/main/SECURITY.md#untrusted-models for more details). In a future release, the default value forweights_onlywill be flipped toTrue. This limits the functions that could be executed during unpickling. Arbitrary objects will no longer be allowed to be loaded via this mode unless they are explicitly allowlisted by the user via torch.serialization.add_safe_globals. We recommend you start setting weights_only=True` for any use case where you don't have full control of the loaded file. Please open an issue on GitHub for any issues related to this experimental feature.
checkpoint = torch.load(join(model_training_output_dir, f'fold_{f}', checkpoint_name),
E:\Anaconda\envs\moose\lib\site-packages\nnunetv2\utilities\plans_handling\plans_handler.py:37: UserWarning: Detected old nnU-Net plans format. Attempting to reconstruct network architecture parameters. If this fails, rerun nnUNetv2_plan_experiment for your dataset. If you use a custom architecture, please downgrade nnU-Net to the version you implemented this or update your implementation + plans.
warnings.warn("Detected old nnU-Net plans format. Attempting to reconstruct network architecture "
Predicting image of shape torch.Size([1, 207, 69, 119]):
perform_everything_on_device: True
sending off prediction to background worker for resampling
Done with image of shape torch.Size([1, 207, 69, 119]):
E:\Anaconda\envs\moose\lib\site-packages\nnunetv2\inference\predict_from_raw_data.py:84: FutureWarning: You are using torch.load with weights_only=False (the current default value), which uses the default pickle module implicitly. It is possible to construct malicious pickle data which will execute arbitrary code during unpickling (See https://github.com/pytorch/pytorch/blob/main/SECURITY.md#untrusted-models for more details). In a future release, the default value for weights_only will be flipped to True. This limits the functions that could be executed during unpickling. Arbitrary objects will no longer be allowed to be loaded via this mode unless they are explicitly allowlisted by the user via torch.serialization.add_safe_globals. We recommend you start setting weights_only=True for any use case where you don't have full control of the loaded file. Please open an issue on GitHub for any issues related to this experimental feature.
checkpoint = torch.load(join(model_training_output_dir, f'fold_{f}', checkpoint_name),
E:\Anaconda\envs\moose\lib\site-packages\nnunetv2\utilities\plans_handling\plans_handler.py:37: UserWarning: Detected old nnU-Net plans format. Attempting to reconstruct network architecture parameters. If this fails, rerun nnUNetv2_plan_experiment for your dataset. If you use a custom architecture, please downgrade nnU-Net to the version you implemented this or update your implementation + plans.
warnings.warn("Detected old nnU-Net plans format. Attempting to reconstruct network architecture "
Predicting image of shape torch.Size([1, 110, 139, 237]):
perform_everything_on_device: True
sending off prediction to background worker for resampling
Done with image of shape torch.Size([1, 110, 139, 237]):

2024-11-07 19:26:35,159 INFO     [system.py:108] ----------------------------------------------------------------------------------------------------
2024-11-07 19:26:35,159 INFO     [system.py:108]                                      STARTING MOOSE-Z V.3.0.0
2024-11-07 19:26:35,159 INFO     [system.py:108] ----------------------------------------------------------------------------------------------------
2024-11-07 19:26:35,161 INFO     [system.py:108]  SETTING UP MODEL WORKFLOWS:
2024-11-07 19:26:35,161 INFO     [system.py:108]  - Model name: clin_ct_body_composition
2024-11-07 19:26:35,163 INFO     [system.py:108]     - A local instance of clin_ct_body_composition has been detected.
2024-11-07 19:26:35,164 INFO     [system.py:108]     - A local instance of clin_ct_fast_vertebrae has been detected.
2024-11-07 19:26:35,166 INFO     [system.py:108]
2024-11-07 19:26:35,166 INFO     [system.py:108] - Main directory: C:\Users\admin\moose\MOOSEv2_data
2024-11-07 19:26:35,166 INFO     [system.py:108]
2024-11-07 19:26:35,172 INFO     [system.py:108]  Required modalities: ['CT'] | No. of modalities: 1 | Required prefix for non-DICOM files: ['CT_']
2024-11-07 19:26:35,172 INFO     [system.py:108]  Skipping subjects without the required modalities (check file prefix).
These subjects will be excluded from analysis and their data will not be used.
2024-11-07 19:26:35,172 INFO     [system.py:108] - Custom trainer: Custom trainer already installed: E:\Anaconda\envs\moose\Lib\site-packages\nnunetv2\training\nnUNetTrainer\variants\MOOSE_custom_trainers.py.
2024-11-07 19:26:35,202 INFO     [system.py:108]
2024-11-07 19:26:35,202 INFO     [system.py:108]  STANDARDIZING INPUT DATA TO NIFTI:
2024-11-07 19:26:35,202 INFO     [system.py:108]
2024-11-07 19:26:35,209 INFO     [system.py:108]  Standardization complete.
2024-11-07 19:26:35,210 INFO     [system.py:108]  Number of moose compliant subjects: 1 out of 2
2024-11-07 19:26:35,212 INFO     [system.py:108]
2024-11-07 19:26:35,212 INFO     [system.py:108]  PERFORMING PREDICTION:
2024-11-07 19:26:35,213 INFO     [system.py:108]
2024-11-07 19:26:35,213 INFO     [system.py:108]  SUBJECT: S2
2024-11-07 19:26:35,213 INFO     [system.py:108]
2024-11-07 19:26:35,213 INFO     [system.py:108]  SETTING UP MOOSE-Z DIRECTORY:
2024-11-07 19:26:35,213 INFO     [system.py:108]
2024-11-07 19:26:35,214 INFO     [system.py:108]  MOOSE directory for subject S2 at: C:\Users\admin\moose\MOOSEv2_data\S2\moosez-2024-11-07-19-26-35
2024-11-07 19:26:35,214 INFO     [system.py:108]
2024-11-07 19:26:35,214 INFO     [system.py:108]  RUNNING PREDICTION:
2024-11-07 19:26:35,214 INFO     [system.py:108]
2024-11-07 19:26:35,215 INFO     [system.py:108]    Image loaded. Orientation: LPS
2024-11-07 19:26:35,277 INFO     [system.py:108]    Image converted to SimpleITK.
2024-11-07 19:26:35,551 INFO     [system.py:108]  - Resampling at 3.0x3.0x3.0 took: 0.27s
2024-11-07 19:26:35,552 INFO     [system.py:108]    - Model clin_ct_body_composition
2024-11-07 19:26:48,471 INFO     [system.py:108]      - Writing segmentation for clin_ct_body_composition
2024-11-07 19:26:48,476 INFO     [system.py:108]      - Prediction complete for clin_ct_body_composition within 0.2 min.
2024-11-07 19:26:48,476 INFO     [system.py:108]      - Extracting volume statistics for clin_ct_body_composition
2024-11-07 19:26:50,513 INFO     [system.py:108]  Prediction done for S2 using 1 models: clin_ct_body_composition! | Elapsed time: 0.2 min
2024-11-07 19:26:50,592 INFO     [system.py:108]
2024-11-07 19:26:50,592 INFO     [system.py:108]  ALL SUBJECTS PROCESSED
2024-11-07 19:26:50,592 INFO     [system.py:108]   - Number of Subjects: 1
2024-11-07 19:26:50,592 INFO     [system.py:108]   - Number of Models:   1
2024-11-07 19:26:50,592 INFO     [system.py:108]   - Time (total):       0.3min
2024-11-07 19:26:50,592 INFO     [system.py:108]   - Time (per subject): 0.26min
2024-11-07 19:26:50,592 INFO     [system.py:108]   - Time (per model):   0.26min
2024-11-07 19:26:50,592 INFO     [system.py:108] ----------------------------------------------------------------------------------------------------
2024-11-07 19:26:50,592 INFO     [system.py:108]                                      FINISHED MOOSE-Z V.3.0.0
2024-11-07 19:26:50,593 INFO     [system.py:108] ----------------------------------------------------------------------------------------------------
`

Hi. This is intended. The body_composition model extracts fat and muscle tissue around the L3 region of the body. So, the approximate 20 slices you describe sound perfectly fine.
We got rid of the old model as it was wildly inaccurate. The new model performs better at correctly differentiating muscle and fat.

Thanks for your answer. Forgive me, I want to ask again, if I want to get a full body result, I have to use the old model? Thanks again

Thanks for your answer. Forgive me, I want to ask again, if I want to get a full body result, I have to use the old model? Thanks again

ok, I find the KEY_LIMIT_FOV parameter in source code，I have been solving this problem, thank your again.


migration plan " New dataset models " can't execute properly

A clear and concise description of what the bug is.
How to reproduce the bug

add new dataset using virtual query with bigquery
the sql is  as below

SELECT
  project_id,
  user_email,
  creation_time,
  total_bytes_billed,
  query
FROM `region-us`.INFORMATION_SCHEMA.JOBS_BY_PROJECT
WHERE job_type = "QUERY"

go to console call superset db upgrade

Expected results
success
Actual results
Traceback (most recent call last):
File "/usr/local/lib/python3.8/site-packages/pybigquery/sqlalchemy_bigquery.py", line 839, in _get_table
table = client.get_table(table_ref)
File "/usr/local/lib/python3.8/site-packages/google/cloud/bigquery/client.py", line 1008, in get_table
api_response = self._call_api(
File "/usr/local/lib/python3.8/site-packages/google/cloud/bigquery/client.py", line 756, in _call_api
return call()
File "/usr/local/lib/python3.8/site-packages/google/api_core/retry.py", line 283, in retry_wrapped_func
return retry_target(
File "/usr/local/lib/python3.8/site-packages/google/api_core/retry.py", line 190, in retry_target
return target()
File "/usr/local/lib/python3.8/site-packages/google/cloud/_http/init.py", line 480, in api_request
raise exceptions.from_http_response(response)
google.api_core.exceptions.NotFound: 404 GET https://bigquery.googleapis.com/bigquery/v2/projects/xxx_projectId/datasets/INFORMATION_SCHEMA/tables/JOBS_BY_PROJECT?prettyPrint=false: Not found: Table xxx_projectId:INFORMATION_SCHEMA.JOBS_BY_PROJECT
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/usr/local/bin/superset", line 33, in
sys.exit(load_entry_point('apache-superset', 'console_scripts', 'superset')())
File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1128, in call
return self.main(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 601, in main
return super().main(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1053, in main
rv = self.invoke(ctx)
File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
return _process_result(sub_ctx.command.invoke(sub_ctx))
File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1395, in invoke
return ctx.invoke(self.callback, **ctx.params)
File "/usr/local/lib/python3.8/site-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/click/decorators.py", line 26, in new_func
return f(get_current_context(), *args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 445, in decorator
return __ctx.invoke(f, *args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/click/core.py", line 754, in invoke
return __callback(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/flask_migrate/cli.py", line 149, in upgrade
_upgrade(directory, revision, sql, tag, x_arg)
File "/usr/local/lib/python3.8/site-packages/flask_migrate/init.py", line 98, in wrapped
f(*args, **kwargs)
File "/usr/local/lib/python3.8/site-packages/flask_migrate/init.py", line 185, in upgrade
command.upgrade(config, revision, sql=sql, tag=tag)
File "/usr/local/lib/python3.8/site-packages/alembic/command.py", line 294, in upgrade
script.run_env()
File "/usr/local/lib/python3.8/site-packages/alembic/script/base.py", line 490, in run_env
util.load_python_file(self.dir, "env.py")
File "/usr/local/lib/python3.8/site-packages/alembic/util/pyfiles.py", line 97, in load_python_file
module = load_module_py(module_id, path)
File "/usr/local/lib/python3.8/site-packages/alembic/util/compat.py", line 184, in load_module_py
spec.loader.exec_module(module)
File "", line 843, in exec_module
File "", line 219, in _call_with_frames_removed
File "/app/superset/extensions/../migrations/env.py", line 126, in
run_migrations_online()
File "/app/superset/extensions/../migrations/env.py", line 118, in run_migrations_online
context.run_migrations()
File "", line 8, in run_migrations
File "/usr/local/lib/python3.8/site-packages/alembic/runtime/environment.py", line 813, in run_migrations
self.get_context().run_migrations(**kw)
File "/usr/local/lib/python3.8/site-packages/alembic/runtime/migration.py", line 561, in run_migrations
step.migration_fn(**kw)
File "/app/superset/migrations/versions/b8d3a24d9131_new_dataset_models.py", line 624, in upgrade
after_insert(target=dataset)
File "/app/superset/migrations/versions/b8d3a24d9131_new_dataset_models.py", line 422, in after_insert
tables = load_or_create_tables(
File "/app/superset/migrations/versions/b8d3a24d9131_new_dataset_models.py", line 282, in load_or_create_tables
column_metadata = inspector.get_columns(table.table, schema=table.schema)
File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/reflection.py", line 390, in get_columns
col_defs = self.dialect.get_columns(
File "/usr/local/lib/python3.8/site-packages/pybigquery/sqlalchemy_bigquery.py", line 872, in get_columns
table = self._get_table(connection, table_name, schema)
File "/usr/local/lib/python3.8/site-packages/pybigquery/sqlalchemy_bigquery.py", line 841, in _get_table
raise NoSuchTableError(table_name)
sqlalchemy.exc.NoSuchTableError: JOBS_BY_PROJECT
Screenshots
If applicable, add screenshots to help explain your problem.
Environment
(please complete the following information):
current superset version is helm install lastest version, I think is 1.4.2-rc1

browser type and version:
superset version: superset version
python version: python --version
node.js version: node -v
any feature flags active:

Checklist
Make sure to follow these steps before submitting your issue - thank you!

[ y] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[ y] I have reproduced the issue with at least the latest released version of superset.
[ y] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

I'm having a similar problem, where the New dataset models migration isn't executed. But no error message appears. If I run superset db upgrade at the console, the process just stops (with status code 1) after printing:
INFO  [alembic.runtime.migration] Running upgrade 5afbb1a5849b -> b8d3a24d9131, New dataset models

Is there anything I can do to diagnose what is causing this failure?
Further history (that may or may not be related): At first I was getting a message like unable to parse query with sqloxide (unfortunately I forgot to copy the whole thing before it went away from my terminal history), right after that message. That was from the superset-init container output, not directly from the superset db upgrade command. After I commented out the offending query directly on the database, I would just keep getting these silent errors, both from the init container output and from running the upgrade command directly.
Superset version: master branch (1b4d8ddf7103f3fa18683a0f23dff6d532ad7efa)

######################################################################

Init Step 1/4 [Starting] -- Applying DB migrations

######################################################################

logging was configured successfully
2022-04-07 13:21:51,928:INFO:superset.utils.logging_configurator:logging was configured successfully
2022-04-07 13:21:51,994:INFO:root:Configured event logger of type <class 'superset.utils.log.DBEventLogger'>
Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
2022-04-07 13:21:52,081:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `FILTER_STATE_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
2022-04-07 13:21:52,185:WARNING:superset.utils.cache_manager:Falling back to the built-in cache, that stores data in the metadata database, for the followinng cache: `EXPLORE_FORM_DATA_CACHE_CONFIG`. It is recommended to use `RedisCache`, `MemcachedCache` or another dedicated caching backend for production deployments
INFO  [alembic.runtime.migration] Context impl PostgresqlImpl.
INFO  [alembic.runtime.migration] Will assume transactional DDL.
INFO  [alembic.runtime.migration] Running upgrade 5fd49410a97a -> 5afbb1a5849b, add_embedded_dahshoard_table
INFO  [alembic.runtime.migration] Running upgrade 5afbb1a5849b -> b8d3a24d9131, New dataset models
Loaded your LOCAL configuration at [/run/secrets/superset_config.py]
Traceback (most recent call last):
  File "/usr/local/bin/superset", line 33, in <module>
    sys.exit(load_entry_point('apache-superset', 'console_scripts', 'superset')())
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1128, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 601, in main
    return super().main(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 445, in decorator
    return __ctx.invoke(f, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/flask_migrate/cli.py", line 149, in upgrade
    _upgrade(directory, revision, sql, tag, x_arg)
  File "/usr/local/lib/python3.8/site-packages/flask_migrate/__init__.py", line 98, in wrapped
    f(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/flask_migrate/__init__.py", line 185, in upgrade
    command.upgrade(config, revision, sql=sql, tag=tag)
  File "/usr/local/lib/python3.8/site-packages/alembic/command.py", line 294, in upgrade
    script.run_env()
  File "/usr/local/lib/python3.8/site-packages/alembic/script/base.py", line 490, in run_env
    util.load_python_file(self.dir, "env.py")
  File "/usr/local/lib/python3.8/site-packages/alembic/util/pyfiles.py", line 97, in load_python_file
    module = load_module_py(module_id, path)
  File "/usr/local/lib/python3.8/site-packages/alembic/util/compat.py", line 184, in load_module_py
    spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 843, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/app/superset/extensions/../migrations/env.py", line 126, in <module>
    run_migrations_online()
  File "/app/superset/extensions/../migrations/env.py", line 118, in run_migrations_online
    context.run_migrations()
  File "<string>", line 8, in run_migrations
  File "/usr/local/lib/python3.8/site-packages/alembic/runtime/environment.py", line 813, in run_migrations
    self.get_context().run_migrations(**kw)
  File "/usr/local/lib/python3.8/site-packages/alembic/runtime/migration.py", line 561, in run_migrations
    step.migration_fn(**kw)
  File "/app/superset/migrations/versions/b8d3a24d9131_new_dataset_models.py", line 632, in upgrade
    after_insert(target=dataset)
  File "/app/superset/migrations/versions/b8d3a24d9131_new_dataset_models.py", line 430, in after_insert
    tables = load_or_create_tables(
  File "/app/superset/migrations/versions/b8d3a24d9131_new_dataset_models.py", line 291, in load_or_create_tables
    column_metadata = inspector.get_columns(table.table, schema=table.schema)
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/reflection.py", line 390, in get_columns
    col_defs = self.dialect.get_columns(
  File "<string>", line 2, in get_columns
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/reflection.py", line 52, in cache
    ret = fn(self, con, *args, **kw)
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/dialects/postgresql/base.py", line 3037, in get_columns
    table_oid = self.get_table_oid(
  File "<string>", line 2, in get_table_oid
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/reflection.py", line 52, in cache
    ret = fn(self, con, *args, **kw)
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/dialects/postgresql/base.py", line 2952, in get_table_oid
    raise exc.NoSuchTableError(table_name)
sqlalchemy.exc.NoSuchTableError: time_created

I have same problem on container init running (e5bab00c)

Same problem for us.
We were testing release version 1.5
INFO  [alembic.runtime.migration] Running upgrade 5afbb1a5849b -> b8d3a24d9131, New dataset models
Traceback (most recent call last):
  File "/usr/local/bin/superset", line 33, in <module>
    sys.exit(load_entry_point('apache-superset', 'console_scripts', 'superset')())
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 586, in main
    return super(FlaskGroup, self).main(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/click/decorators.py", line 21, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/flask/cli.py", line 426, in decorator
    return __ctx.invoke(f, *args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/flask_migrate/cli.py", line 149, in upgrade
    _upgrade(directory, revision, sql, tag, x_arg)
  File "/usr/local/lib/python3.8/site-packages/flask_migrate/__init__.py", line 98, in wrapped
    f(*args, **kwargs)
  File "/usr/local/lib/python3.8/site-packages/flask_migrate/__init__.py", line 185, in upgrade
    command.upgrade(config, revision, sql=sql, tag=tag)
  File "/usr/local/lib/python3.8/site-packages/alembic/command.py", line 294, in upgrade
    script.run_env()
  File "/usr/local/lib/python3.8/site-packages/alembic/script/base.py", line 490, in run_env
    util.load_python_file(self.dir, "env.py")
  File "/usr/local/lib/python3.8/site-packages/alembic/util/pyfiles.py", line 97, in load_python_file
    module = load_module_py(module_id, path)
  File "/usr/local/lib/python3.8/site-packages/alembic/util/compat.py", line 184, in load_module_py
    spec.loader.exec_module(module)
  File "<frozen importlib._bootstrap_external>", line 843, in exec_module
  File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
  File "/app/superset/extensions/../migrations/env.py", line 126, in <module>
    run_migrations_online()
  File "/app/superset/extensions/../migrations/env.py", line 118, in run_migrations_online
    context.run_migrations()
  File "<string>", line 8, in run_migrations
  File "/usr/local/lib/python3.8/site-packages/alembic/runtime/environment.py", line 813, in run_migrations
    self.get_context().run_migrations(**kw)
  File "/usr/local/lib/python3.8/site-packages/alembic/runtime/migration.py", line 561, in run_migrations
    step.migration_fn(**kw)
  File "/app/superset/migrations/versions/b8d3a24d9131_new_dataset_models.py", line 632, in upgrade
    after_insert(target=dataset)
  File "/app/superset/migrations/versions/b8d3a24d9131_new_dataset_models.py", line 430, in after_insert
    tables = load_or_create_tables(
  File "/app/superset/migrations/versions/b8d3a24d9131_new_dataset_models.py", line 291, in load_or_create_tables
    column_metadata = inspector.get_columns(table.table, schema=table.schema)
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/reflection.py", line 390, in get_columns
    col_defs = self.dialect.get_columns(
  File "<string>", line 2, in get_columns
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/reflection.py", line 52, in cache
    ret = fn(self, con, *args, **kw)
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/dialects/postgresql/base.py", line 3037, in get_columns
    table_oid = self.get_table_oid(
  File "<string>", line 2, in get_table_oid
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/engine/reflection.py", line 52, in cache
    ret = fn(self, con, *args, **kw)
  File "/usr/local/lib/python3.8/site-packages/sqlalchemy/dialects/postgresql/base.py", line 2952, in get_table_oid
    raise exc.NoSuchTableError(table_name)
sqlalchemy.exc.NoSuchTableError: get_periodfacts

Here get_periodfacts is a function in the postgres database, used in a dataset definition in superset datasets.
@amitmiran137 , @villebro

@jayakrishnankk this should have been fixed in 1.5.1. Can you try again?

This fixed it for me. I was able to finish the migrations and get the application working again! :)

@ktmud - we were able to successfully upgrade 1.5 afterwards. We are good here.