[python3] Upgrade to 3.9.0

This upgrades the python3 port to 3.9.0. Per #13741, configuring python failed on macOS Big Sur beta. According to the python release notes, that particular bug was fixed in 3.8.4 rc1. However, complete support for Big Sur was not promised until 3.9.0. Therefore we skip the bugfix updates to the 3.8 series and go directly to 3.9.0.

What does your PR fix? Fixes #13741

Which triplets are supported/not supported? Have you updated the CI baseline? No change.

Does your PR follow the maintainer guide? Yes

As I know, the compatibility of different versions of python is very poor, so will the upgrade be risky?

Reverting to draft status due to excessive CI failures by ports depending on vcpkg_find_acquire_program(PYTHON3).

As I know, the compatibility of different versions of python is very poor, so will the upgrade be risky?

Compatibility between Python versions is generally very good. The different library names (python38 vs python39) are because the ABI does not remain stable between versions. This update should be relatively pain-free. However, 3.10 may be a different story because some deprecated APIs will be removed. That version won't come out for another year though.
Re: CI failures -- this is my fault. I initially pushed a flawed commit for the update to vcpkg_find_acquire_program that has poisoned the Python 3.9.0 tool on the CI machines. If a kind maintainer could delete downloads\tools\python\python-3.9.0-x86 and downloads\tools\python\python-3.9.0-x64, then re-run CI, it should succeed.
I think I have fixed all the issues. I'll keep an eye out for the CI re-run after the tool issue gets fixed. And, of course, please let me know if you see any more problems!

Wow, more regressions. Such as:
[1/4] cmd.exe /C "cd /D D:\buildtrees\glad\src\2f4fb681b3-78068df8f5.clean && D:\downloads\tools\python\python-3.9.0-x64\python.exe -m glad --profile=compatibility --out-path=D:/buildtrees/glad/x64-windows-dbg --api= --generator=c-debug --extensions= --spec=gl --reproducible"
FAILED: src/glad.c include/glad/glad.h
cmd.exe /C "cd /D D:\buildtrees\glad\src\2f4fb681b3-78068df8f5.clean && D:\downloads\tools\python\python-3.9.0-x64\python.exe -m glad --profile=compatibility --out-path=D:/buildtrees/glad/x64-windows-dbg --api= --generator=c-debug --extensions= --spec=gl --reproducible"
D:\downloads\tools\python\python-3.9.0-x64\python.exe: No module named glad
ninja: build stopped: subcommand failed.

@JackBoosY Those regressions are due to the poisoned python-3.9.0-x86 and python-3.9.0-x64 tools on the CI machines. I had an error in the vcpkg_find_acquire_program commit that prevents python from importing 3rd party modules. If someone with access to the machines could delete that and rerun CI, they will be fixed.

@BillyONeal can you please take a look?

Sorry for the inconvenience :cry:

Unfortunately in the general case we don't have the ability to, like, "run some command on all the build nodes" -- nobody, not even we, can log in to those boxes. They are heavily firewalled because they run arbitrary code submitted in these github PRs and we didn't want someone to be able to write a PR that turns our build lab into a spam fleet, for example.
On the plus side though, the machines are regularly "nuked from orbit" and the VMs are automatically deleted when we don't get lots of incoming build load. I observe that the failures above occurred on BUILD0003H3, BUILD0003H9, and BUILD0003H4, but all the VMs currently alive are BUILD003I? or BUILD003J?, so all the machines on which the failure occurred should long since have been deleted.

Great, so a rebase and push should get us going. Thanks for the clarification!

CI failures will be fixed by #14571.

Depends on #14579.

The remaining CI failures appear to be false-negatives related to downloads.

/azp run

The failure on arm64_windows is unrelated to this port, which does not function on arm.

Thanks @Hoikas :)

However, python 3.9 does not support win 7, causing some packages fail to build

Hmm... I missed that in the release notes, but sure enough, Python 3.9 dropped support for Windows 7. Windows 7 reached end-of-life on January 14, 2020, so to me, that's a non-issue, especially when the Python release notes are explicitly guaranteeing Big Sur (recent, supported OS) support in 3.9.0. I personally have a dim view of supporting in any way an OS that receives no security patches.
Tangentially related, but it is important for the PYTHON3 tool and python3 port to have the same major.minor version level so that ports providing python extensions will build correctly. So, if we wanted to revert to 3.8, we'd want to back out all but ce20ea6. Then pray that all of the Big Sur changes have been backported to Python 3.8.

If Windows 7 is no longer supported by vcpkg, then the Readme needs an update because it still states "Windows 7 or newer" which is evidently no longer true.
I just tried build skia and ran into some issues with Python (even after installing Python 3.8 hoping it would use that instead of the one from the downloads folder). I was confused since it was working months ago the last time I used it and Win 7 still seemed supported (see Readme). Had to dig through the cmake file to realize it explicitly requests 3.9.

@Borgleader vcpkg supports Windows 7. Not every library in vcpkg supports Windows 7. If Python dropped support for it that's largely outside of our control.

I undid the Python upgrade locally and I was able to build Skia without issues (I have been able to draw some text and some shapes based on their SDL2 demo code). So while some libraries may not support Win7 due to Python 3.9 requirement, it doesn't seem to be the case for this one.

For those Win 7 users, edit vcpkg_find_acquire_program.cmake to downgrade python to 3.8

For those Win 7 users, edit vcpkg_find_acquire_program.cmake to downgrade python to 3.8

Be aware that if you do this without reverting the python3 port itself, you may introduce non-determinant behavior to ports that consume python3.

we need a versioning design in vcpkg badly  !!!

@hunt978 #15172 work in progress now.


Fact errors during "Preparing Operations" mark host as failed even if fact will later succeed

Describe the bug
bauen1:
Okay, using facts does work, kind of, they are evaluated at the right time, but if I now have a fact that will error if run at the beginning, then that prevents the deployment from running, even if a later fact collection (in my case /etc/krb5.keytab population) would be successful probably user error
bauen1:
Actually, not so certain it's my fault anymore, the fact is loaded during --> Preparing Operations... and not _run_fact_operations so apply_failed_hosts=False, isn't set like it should be ?
bauen1:
if that is actually a bug then I'll happily make an issue, I'm just not entirely sure if it's my own fault yet
fizzadar:
Hm is the fact command failing during the "preparing operations" stage? If the command executed returns a nonzero status that'll be counted as a failure, two options here: pass _ignore_errors=True to the operation/fact call or make the command "truthy" ie something like command-that-fails || true
bauen1:
Yes it is, I tried passing _ignore_errors=True to host.get_fact but that was rejected as unknown kwarg.
I'll have to test this a bit more, but I'd say this is a bug in pyinfra, I'm just not entirely sure where yet

To Reproduce
Have a fact that will error during the "Preparing Operations" stage, but not during later execution, e.g. by examining a file that will only be created during execution.
Expected behavior
A fact error should not mark the host as failed during this stage, as the fact may later succeed during actual execution.
Meta

Include output of pyinfra --support.

    If you are having issues with pyinfra or wish to make feature requests, please
    check out the GitHub issues at https://github.com/Fizzadar/pyinfra/issues .
    When adding an issue, be sure to include the following:

    System: Linux
      Platform: Linux-6.6.8-amd64-x86_64-with-glibc2.36
      Release: 6.6.8-amd64
      Machine: x86_64
    pyinfra: v3.0b0
    Executable: /usr/local/bin/pyinfra
    Python: 3.11.2 (CPython, GCC 12.2.0)

How was pyinfra installed (source/pip)?
Include pyinfra-debug.log (if one was created)
Consider including output with -vv and --debug.

So, after a bit of thinking, I suspect this to be a good old case of user error and unclear documentation.
There's nothing per se wrong with the code, but the documentation is a bit unclear about when Facts failing will mark the host as failed, and I think c89e21142523b540ba8cf18dc8d54daf5113773c might fix this particular case where even _ignore_errors wasn't able to allow pyinfra to proceed.


Submit v1.2 release

Create this tag and release when all pending major features are completed.

https://github.com/nicoqueijo/Android-Currency-Converter/releases/tag/v1.2


get user not work correctly

Hi...
I love this library
but I tried this..
const options = Instamancer.IOptions = {
total: 0
}
let getPost = async () => {
const userData = Instamancer.user("global_66", options);
for await (let user of userData) {
console.log(user);
}
}
getPost()
"only return 15 scraped posts", but on the ig are 27 post
node v10.15.3

Instamancer works by listening to API requests that an Instagram page makes, and because the page comes pre-loaded with some posts,  these posts are never requested and thus ignored.
If having an exhaustive list of posts from a user is important to you, then you might be better off with another tool. At this stage, I don't plan on modifying Instamancer to extract posts from the first page.

Fized in v1.4.0

Fixed in v1.4.0

perfect!


Forward/Back Buttons for documentation

It would be nice to have a forward/back button for the documentation.  If you follow the links in the official docs there is no way to easily get back to what you were reading.

Found this looking through old issues and agree this is poor usability. I'll be fixing this shortly


Adding NotFound page when user entered wrong url

It will look good if we add notfound page when user entered wrong url.

can you assign this issue to me with labels gssoc-ext and hacktoberfest

@G-Rajashekar The design should be decent; otherwise, it will not qualify as a valid contribution for 'GSSOC-ext' or 'Hacktoberfest-accepted.'

Feature Description:
Can make a better UI by redirecting if user entered Wrong URL.
Provide a detailed description of the feature
By adding the better provison that  enhances the UI and glow of website were website becomes more user friendly.
Please assign this to me , I am ready for this
Thankyou!
By submitting this issue, you agree to
I agree to follow this project's Code of Conduct
I’ve read all the issues in the issue section,
Other Information

[ ]  I'm a GSSoC '24 Extended contributor
[ ]  I'm a Hacktoberfest '24 contributor
[ ]  I am willing to work on this feature


Foward signals to all child (and adopted) processes

Hi,
Thank you for tini !
During my tests with Docker, I noticed tini:

starts the process given as the argument as the "first child"
forwards received signals to the "first child" only (or the sub-process branch if -g is used)
returns the exit code of the "first child"

In the case where some process has been orphaned and adopted by tini, is it possible to make tini forward signals to these running child processes as well ?
I noticed on an Ubuntu VM, that traditional init seems to ask "all remaining processes to terminate" by sending SIGTERM. I'd like to reproduce this behaviour in order to gracefully stop every child process, even adopted ones.
Thank you for your help.

I'm not certain this would be as useful as you'd hope. Tini won't wait for those other processes to exit anyway, so it's already pretty far from traditional init.
Can you expand a little bit on your use case here? If you need advanced init functionality, it's possible Tini may not be the right choice you.

Thank you for your reply.
For a specific usage, we need to start graphical environment in a Docker container.
Let’s consider an opened graphical mate-terminal with a bash session executing an app (let’s say a sleeping app which waits 3sec after receiving a SIGTERM then touch a file when it’s properly close).
When you docker stop [container], what I understood so far is:

dockerd sends SIGTERM to tini
tini sends SIGTERM to supervisord
supervirsord sends SIGTERM to mate-session
mate-session sends SIGTERM to mate-terminal
mate-terminal sends a SIGHUP to bash
app receives signal and is about to terminates (sleeping 3 sec, doing some cleaning stuff, but taking long time)...
mate-session terminates
app is still running as orphans process and is adopted by init
other supervisord processes are finally terminated
supervisord terminates
as PID 1, init terminates
docker cleans the container namespace
app receives a SIGKILL

In this scenario, if we set a a “sleeping 5sec” subprocess for supervisord to add latency, the app has the time to terminate properly and touch the file. :+1:
We tried this scenario in a traditional ubuntu machine, the init process does an “asking all remaining processes to terminate” action before halting the system.
Is it the expected behavior of tini or did we miss an option or something ? Do you suggest another process manager or PID 1 init manager ?

I came across the same problem. In my quick tests https://github.com/fpco/pid1 works better with this. The scenario I have been testing is running an executable from a bash script (something I see quiet often), which listens to term signals and does a cleanup + exit. With pid1 you will see the executable have the time for a gracefull shutdown, with tini the executable won't have time.

@johnmarcou

Is it the expected behavior of tini or did we miss an option or something ?

This is indeed the expected behavior, yes.
Tini is designed to be an init for containers, where the best practice is to run single-process systems.
If you need a more traditional init system, then Tini is probably not what you're looking for (supporting desktop environment like Mate is definitely out of scope for Tini).

Do you suggest another process manager or PID 1 init manager ?

If what you need is a traditional init system, I would suggest using one 😄
I believe you can actually run Upstart in a Docker container (Upstart used to be Ubuntu's default init system), and it looks like you could even run systemd there (systemd being Ubuntu's current init system).
That said, it sounds like @pvanderlinden has a lighter-weight suggestion for you: pid1. I can't say I have any direct experience with it, though.

I think this would be useful to run double forking processes under tini. Seems like tini exits as soon as the first child dies at the moment.
It would be great if there were a flag where tini would wait for all children to exit, and return the first non-zero exit code. Combined with -g this might be a neat solution, and would allow more esoteric daemons to run under it.

@lmb forking (and double forking) is evil in this context. Prevent it whenever you can. If you can't, then you need specific behavior for specific case, because the process may launch several small programs (utilities) to get some info about system and then do the double-fork. Those utilities may also fork, without waiting for their children, because init should do this.

I made another init system for Docker, dinit, which tries to address exactly this: having multiple children processes, sending signal to them when the container (PID 1) gets the signal, and then waiting for all to finish. If some process does not finish, then it is left to the container's supervisor (i.e., Docker) to kill all processes.

Thanks for sharing, congrats on releasing, it’s always good to have options
for folks that would like a fuller-featured init system in their containers
:)
On Fri, 14 Jul 2023 at 15:20, Mitar @.***> wrote:

I made another init system for Docker, dinit
https://gitlab.com/tozd/dinit, which tries to address exactly this:
having multiple children processes, sending signal to them when the
container (PID 1) gets the signal, and then waiting for all to finish. If
some process does not finish, then it is left to the container's supervisor
(i.e., Docker) to kill all processes.
—
Reply to this email directly, view it on GitHub
https://github.com/krallin/tini/issues/95#issuecomment-1635856904, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AANIHVRDXVYY74EIMVMIBXDXQFBQDANCNFSM4DR43XIA
.
You are receiving this because you commented.Message ID:
@.***>


scrapy jupyter webkit not showing

i am having the same issue as mentioned previously by @genius001  #361 and #376 whereby webkit is not showing up (installed using the manual way). Is there anway i can do to make this work?
I have also tried the docker way but an error message displayed was shown below
No protocol specified
QXcbConnection: Could not connect to display unix:0

I solved this by running
xhost +local:docker
to give docker the relevant permissions

@acowpy this solution worked for me too! Thanks :D

It may be worth covering in the documentation.

Fixed by #903


Key Vault integration

This should also work:
Connect-EntraService -ClientID $clientID -TenantID $tenantID -VaultName myvault -SecretName mysecret

Automagically retrieving the secret, determining whether it is a CLientSecret or a Certificate and then use the appropriate authentication flow.

Stage 1: Use Az.KeyVault for that
Stage 2: Use an existing Azure Resource Manager service connection

Implemented in 1.1.11


Add native method for creating object from pairs

See also: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/fromEntries

Thank you, @robinpokorny 👍


DBZ-8409 Update Quarkus Outbox Extension to Quarkus 3.16.3

https://issues.redhat.com/browse/DBZ-8409

@Naros Applied, thanks


Fixes #4554 - Add support for supporting countries for WLM

Description (required)
Fixes #4554 and location marker issue.
What changes did you make and why?

For WLM uploads reverse geocode and see if the country code is supported -only then is the WLM upload flow triggered, otherwise usual nearby uploads happen
Bug Fix - Current Location marker and area

Tests performed (required)
Tested  betaDebug on API 29

Hey @ashishkumar468 , is there any list to see WLM active countries, so that we can try them during test?

Yes NES, for now we had only enabled for Australia, Ireland and India

@neslihanturan To clarify, Ashish is only adding a basic framework in this PR. We don't have the actual list yet because the WLM organizers haven't finalized it yet, and it will only be finalized close to the start date of WLM. So when it is, I can edit the list to update it.

@ashishkumar468  just realized that the same PR handles both issues. Can we split them into two? Because the location marker fix needs to be merged ASAP before alpha, whereas the country checks actually can't be merged until after alpha.


Does not work when Full Screen Mode activated

There is a jquery plugin which allows you to display a portion of the page in Full Screen mode. However, when I put the browser in Full Screen Mode, ZeroClipboard no longer functions.
Using the Chrome's "Inspect Element" I was able to determine that the embedded SWF flash objects were still on the page, but showing up behind the HTML elements they were supposed to cover. Tried changing CSS z-index without any luck. Moved the Flash object from the document.body to the DIV that is being displayed in full screen but that only worked for one of the two buttons glued by ZeroClipbard. Also need to move back to the document.body and re-intialize when they leave full screen mode.
Any advice for getting this ZeroClipboard to work in Full Screen Mode?
Tested on Chrome 30 and Firefox 24 on Win 7 with Flash 11.9.900

I'm going to close this for now as there is no way to resolve the conflict with the HTML TopLayer specification without altering our embedding strategy [which, as discussed, as other potential negative implications but can be achieved independently by interested parties by extending ZeroClipboard.Core].
I've created and applied a new label of "HTML TopLayer" so that this issue can be easily found and revisited once browsers start implementing the HTML Clipboard API (see #171).


AST+ (Part1)

This diff contains some first parts of AST+ work :

Define an AST+ datatype by copying from latest ocaml trunk
Change the parse to parse into AST+
define conversion functions to convert AST+ to AST@(4.2.3). Unfortunately there is no magic to do it in a clean way, just some tedious work produced by some tediuos emacs scripts.

Work left to do:

We've only finished the parser part (parse into AST+, convert to AST@4.2.3). We also want to do the symmatric part for printing (convert from<EMAIL_ADDRESS>to AST+, print AST+).
Need to do the same thing for 4.3.0 -- would be relatively easy with CPPO support I believe.
#706

This is fully functional now. Both parser and printer has support for the latest AST from OCaml/trunk, but can be fed into OCaml 4.2 compiler
The next step is to support OCaml 4.3 using CPPO

Rebased on top of jsx

Closing this in favor of https://github.com/let-def/migrate-parsetree, which is a more generic implementation that can benefit the whole community.


add a Noise codepoint

Analogous to https://github.com/multiformats/go-multiaddr/pull/153, we also want to be able express Noise addresses, e.g. /ip4/<IP_ADDRESS>/tcp/4001/noise.
cc @mxinden

Approved.
Could you update https://github.com/multiformats/multiaddr/blob/master/protocols.csv as well @marten-seemann? I am not sure which of multiformats/multicodec and multiformats/multiaddr is the source of truth.

Friendly ping @marten-seemann.

@mxinden Sorry for the delay. https://github.com/multiformats/multiaddr/pull/112


Get our OIDC work merged into Archivematica

I've had a request from Jesús at Artefactual to rebase our OIDC PRs, so they can be merged for Archivematica 1.12: https://github.com/archivematica/Issues/issues/1053#issuecomment-665182273
It’s been a while since I looked at Helen‘s code, but at a quick glance I reckon it’s maybe half a day of work.

[x] https://github.com/artefactual/archivematica/pull/1536
[x] https://github.com/artefactual/archivematica-storage-service/pull/517
[x] https://github.com/artefactual/archivematica-docs/pull/342

Looks like all three PRs have been merged, so closing.


tests: added unit tests for the new mention for channel_mention, user_mention, role_mention and emoji_mention in utility the namespace

all looks good to me!


In poem_openapi, allow a Query to have additional parameters

I'm trying to implement an OAuth 2.0 compliant authorization server, and for one of the endpoints you should return a 308 permanent redirect to an URL with the same query that was sent in (maybe changing the values of a few of them).
Is there an "additional parameters" option for a Query or a way to get those additional parameters? Is there a way to make Query reject queries that have repeated keys? Is there a way to turn the query into a String?
I'm assuming not, and that I'd need to make a new query struct myself. Would this be possible at all? What traits would I need to implement for it to be usable in place of poem_api::param::Query (or poem::web::Query)?

I have figured out a lot. I'm pretty sure those options don't exist, and I'd just need to write a parser myself and implement a method to turn it into a string.

How could I make sure that it was still is all documented under OpenAPI?


Free upgrades!  Replacement items not removed from inventory.

Describe the Bug
Mouseover upgrade planner is free; installed items are not removed after upgrading via upgrade planner + mouseover.
To Reproduce
This applies to any items, but we'll use belts for this example.

Acquire 5 yellow belts and 5 red belts
Install a row of 5 yellow belts
Use the upgrade planner to mark yellow belts for upgrade to red belts
Mouseover the yellow belts, upgrading them to red belts
The 5 red belts are installed. In your inventory, you now have 5 yellow belts AND 5 red belts.
The 5 red belts should have been removed from your inventory.

Proposed solution:
In control.lua, in the upgrading section (approximately line 85), add the following line to remove the upgraded item after a successful upgrade.  I believe this will solve the issue.  Thanks!
                if upgraded_entity then
                  player.play_sound{
                    path = "entity-build/"..upgraded_entity.name,
                    position = upgraded_entity.position
                  }
>>>               inventory.remove(use_item)
                end

How did I forget that? Thanks, fixed for the next release.


The Host Header should be configurable when generating OAuth tokens

Currently, the Host header is always set to edgex, which will fail if the user is attempting to create the OAuth token over HTTPS and uses a SNI/hostname setting other than edgex, as the certificate validation will fail. This setting should be configurable.

will switch from hardcode to snis section of [secretservice] section in the configuration file. This will be addressed in Delhi dot release.

address in PR #47

I will propose to remove host header as it is not gaining any benefit. Besides based on my testing on KONG 1.0.3 it seems there is a bug with combination of custom header and JWT/OAuth2 auth plugin.

close this issue per my comments above.


zuki-themes: 3.24.2017-06-26 -> 3.24-2

Motivation for this change

Update to version 3.24-2, released on 2017 Aug 3

Remove versions for GNOME 3.22 and 3.20. The version for 3.24 should
work with them as well.

Things done

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

[x] NixOS
[ ] macOS
[ ] Linux

[ ] 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 nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Rebased to master in 6319210b8af4d002b5bf56b26451a5f24b279074. Thanks!


Stored & Reflected XSS in Exhibitor v1.5.6

I found that the following string can be added to the node explorer, allowing an attacker to create a stored cross site scripting (XSS) that can be seen under the logs tab.
Payload : "><img+src=x+onerror=alert('XSS')>.

Attached some screenshots

Hi, thanks for the very detailed report.
I'm not very familiar with how to prevent this type of attack (and web dev in general).
A pull request would be greatly appreciated.

Hi @xiaochuanyu ,
Thanks for Response. This issue can be fixed by validating all the input that is coming from various components of the website like the database, end user, a web service, forms, hidden form fields, cookies, query strings etc. This can be ensured in two ways:
•	Validating the input fields: The most effective method of addressing XSS vulnerabilities is to only accept and process data that is considered valid and reject everything else. This process entails White-List validation by permitting only those characters that may be legitimate input for a given field. For example, if the field is meant to accept a telephone number it should filter out or escape out all characters other than [0-9] and -. : <,>,”,’,%,;,&,(,),+.
•	Escaping All Output: This process entails HTML Encoding all characters to prevent any execution. For example, if the < character is encoded to &lt then it will not be interpreted by the browser as the start of a tag and would simply be displayed as <.
Let me know anything else you required.

Hi @xiaochuanyu ,
Any update on Fixes.

For the Explore tab, the root cause seems to be that DynaTree (the library used to generate the tree of znodes in the Explore tab) does not escape its input.
Fancytree, dynatree's sequel, is able to escape its input via the escapeTitles parameter.
For the Log tab, see issue #331 .


Update README.md

Updating Readme to add the website app that creates a video from popularity filtered images.

Looks great! This is so awesome -- excited to share this with more people on campus.


[Feature Suggestion]: Hex to Decimal Converter in MMIO Whitelist

Today I was looking into Booter/MmioWhitelist and noticed that this section would benefit from a HEX To DEC converter at the bottom of the window, similar to the one in the ACPI/Patch section.
Greetings.

Ok, that's recorded. I'll implement it when I'm free.
Thanks for the advice.

I just checked that the "Address" field in this "whitelist" is an integer, so it does not involve hexadecimal conversion. Please check it again, thank you.

Well, the MMIO regions contained in the OpenCore bootlog are in hex and need to be converted to decimal first in order to add them to the whitelist. That's why the converter would be useful. Here's how it works: https://github.com/5T33Z0/OC-Little-Translated/blob/main/12_MMIO_Whitelist/README.md


Expected behavior
Behavior in 3.11.x should be the same as 3.12.x in this case. Many code formatters/linters/editors/etc prefer a blank line at the end of a file.

@nebrius A single newline at the end of your file shouldn't produce this error (it doesn't for us anyways). I think you have a blank line and then an additional new line after that blank line in your files - essentially there's an extra blank line sitting around.
A single newline is standard for the end of a file, but I've never heard of having a blank line before that newline - it seems redundant. Could you point me to any resources/examples of code where this is typically done?

@JKillian Ahh, I see what happened now. We had an editor config set to hide the last newline, so it wasn't readily apparent there were two newlines, and the previous bug that was fixed in 3.12.0 obscured this was happening. Thanks!


With WSL2's Mirror Network Mode, Services on the Windows Host are Inaccessible, but the Reverse is Possible

Windows Version
Microsoft Windows [Version 10.0.22631.4602]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[x] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-1
Distro Version
Debian 12
Other Software
No response
Repro Steps

The content of .wslconfig is as follows, with other options set to default::

[wsl2]
networkingMode=mirrored

On Windows host: Run command python -m http.server 8000 in a directory only containing an index.html file:
in WSL2: run command wget <IP_ADDRESS>:8000
Result: Connecting to <IP_ADDRESS>:8000...

I tested all available network modes in WSL2. I was able to access the host service using both NAT and virtioProxy, but mirror mode (using <IP_ADDRESS>) did not work.
However, when I run the command python3 -m http.server 8100 in the WSL2 distro and then run wget <IP_ADDRESS>:8100 in PowerShell, it works fine.
Interestingly, on another laptop with the same WSL2 and Windows version, the setup works as expected. I'm confident the issue lies with some misconfiguration, but despite trying various approaches, I haven't been able to resolve it.
Expected Behavior
in WSL2: run command wget <IP_ADDRESS>:8000 it works fine.
Actual Behavior
Connecting to <IP_ADDRESS>:8000...
Diagnostic Logs
_No responseWslLogs-2024-12-21_12-17-00.zip
WslNetworkingLogs-2024-12-21_12-18-20.zip
_

I have looked at similar issues in this project and found a solution: enabling the WiFi hotspot on my laptop. I'm curious why this works.

Workaround: Use Windows local IP address.
WSL version: <IP_ADDRESS>
Kernel version: <IP_ADDRESS>-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.19045.5247


Package import error but indeed program runs normally

What version of Go are you using (go version)?

$ go version
go version go1.15.5 linux/amd64

Does this issue reproduce with the latest release?
Yes.
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/username/.cache/go-build"
GOENV="/home/username/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/username/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/username/go"
GOPRIVATE=""
GOPROXY="https://goproxy.io,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/username/workspace/projects/http2socks5/go.mod"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build039276181=/tmp/go-build -gno-record-gcc-switches"

Besides, I use the vscode remote-ssh extension.
What did you do?

I just import a package golang.org/x/net/proxy.
What did you expect to see?
The program runs properly without any notifcation.
What did you see instead?
The program is running properly.
However, the extension go nightly tells me that the complier noticed that I have a package loading error.
It does not influence the program's performence, but the notifcation is kind of annoying.

CC @hyangah

@fourdim thanks for the report - can you please capture the gopls log following the instruction here? https://github.com/golang/tools/blob/master/gopls/doc/troubleshooting.md#capturing-logs
We need the trace from the beginning.
@stamblerre this error message is strange - it reports that there is no main module, but according to the go env output, there IS a go.mod file in the same directory as main.go.

gopls server Output
[Trace - 14:27:17.255 PM] Sending request 'initialize - (0)'.
Params: {"processId":31580,"clientInfo":{"name":"vscode","version":"1.51.1"},"rootPath":"/home/username","rootUri":"file:///home/username","capabilities":{"workspace":{"applyEdit":true,"workspaceEdit":{"documentChanges":true,"resourceOperations":["create","rename","delete"],"failureHandling":"textOnlyTransactional"},"didChangeConfiguration":{"dynamicRegistration":true},"didChangeWatchedFiles":{"dynamicRegistration":true},"symbol":{"dynamicRegistration":true,"symbolKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]},"tagSupport":{"valueSet":[1]}},"executeCommand":{"dynamicRegistration":true},"configuration":true,"workspaceFolders":true,"semanticTokens":{"refreshSupport":true}},"textDocument":{"publishDiagnostics":{"relatedInformation":true,"versionSupport":false,"tagSupport":{"valueSet":[1,2]},"codeDescriptionSupport":true,"dataSupport":true},"synchronization":{"dynamicRegistration":true,"willSave":true,"willSaveWaitUntil":true,"didSave":true},"completion":{"dynamicRegistration":true,"contextSupport":true,"completionItem":{"snippetSupport":true,"commitCharactersSupport":true,"documentationFormat":["markdown","plaintext"],"deprecatedSupport":true,"preselectSupport":true,"tagSupport":{"valueSet":[1]},"insertReplaceSupport":true,"resolveSupport":{"properties":["documentation","detail","additionalTextEdits"]}},"completionItemKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25]}},"hover":{"dynamicRegistration":true,"contentFormat":["markdown","plaintext"]},"signatureHelp":{"dynamicRegistration":true,"signatureInformation":{"documentationFormat":["markdown","plaintext"],"parameterInformation":{"labelOffsetSupport":true},"activeParameterSupport":true},"contextSupport":true},"definition":{"dynamicRegistration":true,"linkSupport":true},"references":{"dynamicRegistration":true},"documentHighlight":{"dynamicRegistration":true},"documentSymbol":{"dynamicRegistration":true,"symbolKind":{"valueSet":[1,2,3,4,5,6,7,8,9,10,11,12,13,14,15,16,17,18,19,20,21,22,23,24,25,26]},"hierarchicalDocumentSymbolSupport":true,"tagSupport":{"valueSet":[1]},"labelSupport":true},"codeAction":{"dynamicRegistration":true,"isPreferredSupport":true,"disabledSupport":true,"dataSupport":true,"resolveSupport":{"properties":["edit"]},"codeActionLiteralSupport":{"codeActionKind":{"valueSet":["","quickfix","refactor","refactor.extract","refactor.inline","refactor.rewrite","source","source.organizeImports"]}}},"codeLens":{"dynamicRegistration":true},"formatting":{"dynamicRegistration":true},"rangeFormatting":{"dynamicRegistration":true},"onTypeFormatting":{"dynamicRegistration":true},"rename":{"dynamicRegistration":true,"prepareSupport":true,"prepareSupportDefaultBehavior":true},"documentLink":{"dynamicRegistration":true,"tooltipSupport":true},"typeDefinition":{"dynamicRegistration":true,"linkSupport":true},"implementation":{"dynamicRegistration":true,"linkSupport":true},"colorProvider":{"dynamicRegistration":true},"foldingRange":{"dynamicRegistration":true,"rangeLimit":5000,"lineFoldingOnly":true},"declaration":{"dynamicRegistration":true,"linkSupport":true},"selectionRange":{"dynamicRegistration":true},"callHierarchy":{"dynamicRegistration":true},"semanticTokens":{"dynamicRegistration":true,"tokenTypes":["namespace","type","class","enum","interface","struct","typeParameter","parameter","variable","property","enumMember","event","function","member","macro","keyword","modifier","comment","string","number","regexp","operator"],"tokenModifiers":["declaration","definition","readonly","static","deprecated","abstract","async","modification","documentation","defaultLibrary"],"formats":["relative"],"requests":{"range":true,"full":{"delta":true}}}},"window":{"workDoneProgress":true}},"initializationOptions":{"allExperiments":true},"trace":"off","workspaceFolders":[{"uri":"file:///home/username","name":"username"}]}
[Trace - 14:27:17.256 PM] Received response 'initialize - (0)' in 1ms.
Result: {"capabilities":{"textDocumentSync":{"openClose":true,"change":2,"save":{}},"completionProvider":{"triggerCharacters":["."]},"hoverProvider":true,"signatureHelpProvider":{"triggerCharacters":["(",","]},"definitionProvider":true,"typeDefinitionProvider":true,"implementationProvider":true,"referencesProvider":true,"documentHighlightProvider":true,"documentSymbolProvider":true,"codeActionProvider":{"codeActionKinds":["quickfix","refactor.extract","refactor.rewrite","source.fixAll","source.organizeImports"]},"codeLensProvider":{},"documentLinkProvider":{},"workspaceSymbolProvider":true,"documentFormattingProvider":true,"documentOnTypeFormattingProvider":{"firstTriggerCharacter":""},"renameProvider":{"prepareProvider":true},"foldingRangeProvider":true,"executeCommandProvider":{"commands":["gopls.generate","gopls.fill_struct","gopls.regenerate_cgo","gopls.test","gopls.tidy","gopls.undeclared_name","gopls.add_dependency","gopls.upgrade_dependency","gopls.remove_dependency","gopls.vendor","gopls.extract_variable","gopls.extract_function","gopls.gc_details","gopls.generate_gopls_mod"]},"callHierarchyProvider":true,"workspace":{"workspaceFolders":{"supported":true,"changeNotifications":"workspace/didChangeWorkspaceFolders"}}},"serverInfo":{"name":"gopls","version":"{"path":"golang.org/x/tools/gopls","version":"v0.5.4-pre.1","sum":"h1:ac/2M/1ezJQ9o/F52BHM8yHYOU/W5wKFWeb3rXt5/JA=","deps":[{"path":"github.com/BurntSushi/toml","version":"v0.3.1","sum":"h1:WXkYYl6Yr3qBf1K79EBnL4mak0OimBfB0XUf9Vl28OQ="},{"path":"github.com/google/go-cmp","version":"v0.5.1","sum":"h1:JFrFEBb2xKufg6XkJsJr+WbKb4FQlURi5RUcBveYu9k="},{"path":"github.com/sergi/go-diff","version":"v1.1.0","sum":"h1:we8PVUC3FE2uYfodKH/nBHMSetSfHDR6scGdBi+erh0="},{"path":"golang.org/x/mod","version":"v0.3.0","sum":"h1:RM4zey1++hCTbCVQfnWeKs9/IEsaBLA8vTkd0WVtmH4="},{"path":"golang.org/x/sync","version":"v0.0.0-20201020160332-67f06af15bc9","sum":"h1:SQFwaSi55rU7vdNs9Yr0Z324VNlrF+0wMqRXT4St8ck="},{"path":"golang.org/x/tools","version":"v0.0.0-20201123203206-735e963e909b","sum":"h1:U8XGResmZKfdo8rCjWPsuiB4cu7N0PJSpQwc9lZr9Rg="},{"path":"golang.org/x/xerrors","version":"v0.0.0-20200804184101-5ec99f83aff1","sum":"h1:go1bK/D/BFZV2I8cIQd1NKEZ+0owSTG1fDTci4IqFcE="},{"path":"honnef.co/go/tools","version":"v0.0.1-2020.1.6","sum":"h1:W18jzjh8mfPez+AwGLxmOImucz/IFjpNlrKVnaj2YVc="},{"path":"mvdan.cc/gofumpt","version":"v0.0.0-20200927160801-5bfeb2e70dd6","sum":"h1:z+/YqapuV7VZPvBb3GYmuEJbA88M3PFUxaHilHYVCpQ="},{"path":"mvdan.cc/xurls/v2","version":"v2.2.0","sum":"h1:NSZPykBXJFCetGZykLAxaL6SIpvbVy/UFEniIfHAa8A="}]}"}}
[Trace - 14:27:17.268 PM] Sending notification 'initialized'.
Params: {}
[Trace - 14:27:17.268 PM] Received request 'window/workDoneProgress/create - (1)'.
Params: {"token":"*******************"}
[Trace - 14:27:17.269 PM] Sending response 'window/workDoneProgress/create - (1)' in 1ms.
Result:
[Trace - 14:27:17.269 PM] Received notification '$/progress'.
Params: {"token":"*******************","value":{"kind":"begin","title":"Setting up workspace","message":"Loading packages..."}}
[Trace - 14:27:17.270 PM] Received request 'workspace/configuration - (2)'.
Params: {"items":[{"scopeUri":"file:///home/username","section":"gopls"}]}
[Trace - 14:27:17.274 PM] Sending response 'workspace/configuration - (2)' in 4ms.
Result: [null]
[Trace - 14:27:17.317 PM] Received notification 'window/logMessage'.
Params: {"type":3,"message":"2020/12/01 14:27:17 go env for /home/username\n(root /home/username)\n(go version go version go1.15.5 linux/amd64)\n(valid build configuration = false)\n(build flags: [])\nGOPATH=/home/username/go\nGO111MODULE=on\nGONOSUMDB=\nGOMODCACHE=/home/username/go/pkg/mod\nGONOPROXY=\nGOPROXY=https://goproxy.io,direct\nGOROOT=/usr/local/go\nGOFLAGS=\nGOINSECURE=\nGOMOD=/dev/null\nGOCACHE=/home/username/.cache/go-build\nGOSUMDB=sum.golang.org\nGOPRIVATE=\n\n"}
[Info  - 2:27:17 PM] 2020/12/01 14:27:17 go env for /home/username
(root /home/username)
(go version go version go1.15.5 linux/amd64)
(valid build configuration = false)
(build flags: [])
GOPATH=/home/username/go
GO111MODULE=on
GONOSUMDB=
GOMODCACHE=/home/username/go/pkg/mod
GONOPROXY=
GOPROXY=https://goproxy.io,direct
GOROOT=/usr/local/go
GOFLAGS=
GOINSECURE=
GOMOD=/dev/null
GOCACHE=/home/username/.cache/go-build
GOSUMDB=sum.golang.org
GOPRIVATE=
[Trace - 14:27:17.317 PM] Received request 'client/registerCapability - (3)'.
Params: {"registrations":[{"id":"workspace/didChangeWatchedFiles-0","method":"workspace/didChangeWatchedFiles","registerOptions":{"watchers":[{"globPattern":"**/*.{go,mod,sum}","kind":7}]}}]}
[Trace - 14:27:17.321 PM] Sending response 'client/registerCapability - (3)' in 3ms.
Result:
[Trace - 14:27:17.321 PM] Received request 'client/registerCapability - (4)'.
Params: {"registrations":[{"id":"workspace/didChangeConfiguration","method":"workspace/didChangeConfiguration"},{"id":"workspace/didChangeWorkspaceFolders","method":"workspace/didChangeWorkspaceFolders"}]}
[Trace - 14:27:17.322 PM] Sending response 'client/registerCapability - (4)' in 0ms.
Result:
[Trace - 14:27:17.326 PM] Received notification 'window/logMessage'.
Params: {"type":1,"message":"2020/12/01 14:27:17 go/packages.Load: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./ builtin]: exit status 1: go: cannot find main module; see 'go help modules'\n\n\tsnapshot=0\n\tdirectory=/home/username\n\tquery=[./ builtin]\n\tpackages=0\n"}
[Error - 2:27:17 PM] 2020/12/01 14:27:17 go/packages.Load: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./ builtin]: exit status 1: go: cannot find main module; see 'go help modules'
snapshot=0
directory=/home/username
query=[./ builtin]
packages=0

[Trace - 14:27:17.328 PM] Received notification 'window/logMessage'.
Params: {"type":1,"message":"2020/12/01 14:27:17 initial workspace load failed: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./ builtin]: exit status 1: go: cannot find main module; see 'go help modules'\n: packages.Load error\n"}
[Trace - 14:27:17.328 PM] Received notification '$/progress'.
Params: {"token":"*******************","value":{"kind":"end","message":"Finished loading packages."}}
[Error - 2:27:17 PM] 2020/12/01 14:27:17 initial workspace load failed: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./ builtin]: exit status 1: go: cannot find main module; see 'go help modules'
: packages.Load error
[Trace - 14:27:17.340 PM] Received notification 'window/logMessage'.
Params: {"type":1,"message":"2020/12/01 14:27:17 go/packages.Load: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules'\n\n\tsnapshot=0\n\tdirectory=/home/username\n\tquery=[./]\n\tpackages=0\n"}
[Error - 2:27:17 PM] 2020/12/01 14:27:17 go/packages.Load: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules'
snapshot=0
directory=/home/username
query=[./]
packages=0

[Trace - 14:27:17.510 PM] Received request 'window/workDoneProgress/create - (5)'.
Params: {"token":"8674665223082153551"}
[Trace - 14:27:17.511 PM] Sending response 'window/workDoneProgress/create - (5)' in 0ms.
Result:
[Trace - 14:27:17.511 PM] Received notification '$/progress'.
Params: {"token":"8674665223082153551","value":{"kind":"begin","title":"Error loading workspace","message":"go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules' : packages.Load error"}}
[Trace - 14:27:17.511 PM] Received notification 'window/logMessage'.
Params: {"type":1,"message":"2020/12/01 14:27:17 errors diagnosing workspace: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules'\n: packages.Load error\n\tsnapshot=0\n\tdirectory=file:///home/username\n"}
[Error - 2:27:17 PM] 2020/12/01 14:27:17 errors diagnosing workspace: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules'
: packages.Load error
snapshot=0
directory=file:///home/username
[Trace - 14:27:22.859 PM] Sending notification 'textDocument/didOpen'.
Params: {"textDocument":{"uri":"file:///home/username/workspace/projects/http2socks5/main.go","languageId":"go","version":1,"text":"package main\n\nimport (\n\t"bytes"\n\t"fmt"\n\t"io"\n\t"log"\n\t"net"\n\t"net/url"\n\t"strings"\n\n\t"golang.org/x/net/proxy"\n)\n\nfunc main() {\n\tlog.SetFlags(log.LstdFlags | log.Lshortfile)\n\tl, err := net.Listen("tcp", "<IP_ADDRESS>:8080")\n\tif err != nil {\n\t\tlog.Panic(err)\n\t}\n\n\tfor {\n\t\tclient, err := l.Accept()\n\t\tif err != nil {\n\t\t\tlog.Panic(err)\n\t\t}\n\n\t\tgo handleClientRequest(client)\n\t}\n}\n\nfunc handleClientRequest(client net.Conn) {\n\tif client == nil {\n\t\treturn\n\t}\n\tdefer client.Close()\n\n\tvar b [1024]byte\n\tn, err := client.Read(b[:])\n\tif err != nil {\n\t\tlog.Println(err)\n\t\treturn\n\t}\n\tvar method, host, address string\n\tfmt.Sscanf(string(b[:bytes.IndexByte(b[:], '\n')]), "%s%s", &method, &host)\n\tfmt.Println(host)\n\thostPortURL, err := url.Parse(host)\n\tif err != nil {\n\t\tlog.Println(err)\n\t\treturn\n\t}\n\n\tif hostPortURL.Opaque == "443" { //https\n\t\taddress = hostPortURL.Scheme + ":443"\n\t} else { //http\n\t\tif strings.Index(hostPortURL.Host, ":") == -1 { //http port 80 by default\n\t\t\taddress = hostPortURL.Host + ":80"\n\t\t} else {\n\t\t\taddress = hostPortURL.Host\n\t\t}\n\n\t}\n\n\tscoks5Dialer, err := proxy.SOCKS5("tcp", "<IP_ADDRESS>:51837", nil, proxy.Direct)\n\tif err != nil {\n\t\tlog.Println(err)\n\t\treturn\n\t}\n\tserver, err := scoks5Dialer.Dial("tcp", address)\n\tif err != nil {\n\t\tlog.Println(err)\n\t\treturn\n\t}\n\tif method == "CONNECT" {\n\t\tfmt.Fprint(client, "HTTP/1.1 200 Connection established\n\n")\n\t} else {\n\t\tserver.Write(b[:n])\n\t}\n\n\tgo io.Copy(server, client)\n\tio.Copy(client, server)\n}\n"}}
[Trace - 14:27:22.859 PM] Sending request 'textDocument/documentLink - (1)'.
Params: {"textDocument":{"uri":"file:///home/username/workspace/projects/http2socks5/main.go"}}
[Trace - 14:27:22.859 PM] Sending request 'textDocument/codeAction - (2)'.
Params: {"textDocument":{"uri":"file:///home/username/workspace/projects/http2socks5/main.go"},"range":{"start":{"line":0,"character":0},"end":{"line":0,"character":0}},"context":{"diagnostics":[]}}
[Trace - 14:27:22.859 PM] Sending request 'textDocument/documentSymbol - (3)'.
Params: {"textDocument":{"uri":"file:///home/username/workspace/projects/http2socks5/main.go"}}
[Trace - 14:27:22.859 PM] Sending notification '$/cancelRequest'.
Params: {"id":3}
[Trace - 14:27:22.859 PM] Sending request 'textDocument/documentSymbol - (4)'.
Params: {"textDocument":{"uri":"file:///home/username/workspace/projects/http2socks5/main.go"}}
[Trace - 14:27:22.870 PM] Received notification 'window/logMessage'.
Params: {"type":1,"message":"2020/12/01 14:27:22 go/packages.Load: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules'\n\n\tsnapshot=0\n\tdirectory=/home/username\n\tquery=[./]\n\tpackages=0\n"}
[Error - 2:27:22 PM] 2020/12/01 14:27:22 go/packages.Load: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules'
snapshot=0
directory=/home/username
query=[./]
packages=0

[Trace - 14:27:22.981 PM] Received notification 'window/logMessage'.
Params: {"type":3,"message":"2020/12/01 14:27:22 go/packages.Load\n\tsnapshot=1\n\tdirectory=/home/username\n\tquery=[file=/home/username/workspace/projects/http2socks5/main.go]\n\tpackages=1\n"}
[Trace - 14:27:22.982 PM] Received notification 'window/logMessage'.
Params: {"type":3,"message":"2020/12/01 14:27:22 go/packages.Load\n\tsnapshot=1\n\tpackage_path="command-line-arguments"\n\tfiles=[/home/username/workspace/projects/http2socks5/main.go]\n"}
[Info  - 2:27:22 PM] 2020/12/01 14:27:22 go/packages.Load
snapshot=1
directory=/home/username
query=[file=/home/username/workspace/projects/http2socks5/main.go]
packages=1
[Info  - 2:27:22 PM] 2020/12/01 14:27:22 go/packages.Load
snapshot=1
package_path="command-line-arguments"
files=[/home/username/workspace/projects/http2socks5/main.go]
[Trace - 14:27:22.988 PM] Received notification 'window/logMessage'.
Params: {"type":3,"message":"2020/12/01 14:27:22 go/packages.Load\n\tsnapshot=1\n\tpackage_path="command-line-arguments"\n\tfiles=[/home/username/workspace/projects/http2socks5/main.go]\n"}
[Trace - 14:27:22.988 PM] Received notification 'window/logMessage'.
Params: {"type":3,"message":"2020/12/01 14:27:22 go/packages.Load\n\tsnapshot=1\n\tdirectory=/home/username\n\tquery=[file=/home/username/workspace/projects/http2socks5/main.go]\n\tpackages=1\n"}
[Info  - 2:27:22 PM] 2020/12/01 14:27:22 go/packages.Load
snapshot=1
package_path="command-line-arguments"
files=[/home/username/workspace/projects/http2socks5/main.go]
[Info  - 2:27:22 PM] 2020/12/01 14:27:22 go/packages.Load
snapshot=1
directory=/home/username
query=[file=/home/username/workspace/projects/http2socks5/main.go]
packages=1
[Trace - 14:27:23.032 PM] Sending request 'textDocument/codeLens - (5)'.
Params: {"textDocument":{"uri":"file:///home/username/workspace/projects/http2socks5/main.go"}}
[Trace - 14:27:23.035 PM] Received notification 'window/logMessage'.
Params: {"type":1,"message":"2020/12/01 14:27:23 command-line-arguments: no dep handle for golang.org/x/net/proxy: no metadata for golang.org/x/net/proxy\n\tsnapshot=1\n"}
[Error - 2:27:23 PM] 2020/12/01 14:27:23 command-line-arguments: no dep handle for golang.org/x/net/proxy: no metadata for golang.org/x/net/proxy
snapshot=1
[Trace - 14:27:23.037 PM] Received notification 'window/logMessage'.
Params: {"type":1,"message":"2020/12/01 14:27:23 command-line-arguments: no dep handle for golang.org/x/net/proxy: no metadata for golang.org/x/net/proxy\n\tsnapshot=1\n"}
[Error - 2:27:23 PM] 2020/12/01 14:27:23 command-line-arguments: no dep handle for golang.org/x/net/proxy: no metadata for golang.org/x/net/proxy
snapshot=1
[Trace - 14:27:23.078 PM] Sending request 'textDocument/foldingRange - (6)'.
Params: {"textDocument":{"uri":"file:///home/username/workspace/projects/http2socks5/main.go"}}
[Trace - 14:27:23.230 PM] Received notification 'textDocument/publishDiagnostics'.
Params: {"uri":"file:///home/username/workspace/projects/http2socks5/main.go","version":1,"diagnostics":[{"range":{"start":{"line":11,"character":1},"end":{"line":11,"character":25}},"severity":1,"source":"compiler","message":"could not import golang.org/x/net/proxy (no package for import golang.org/x/net/proxy)"}]}
[Trace - 14:27:23.230 PM] Received response 'textDocument/documentLink - (1)' in 371ms.
Result: [{"range":{"start":{"line":3,"character":2},"end":{"line":3,"character":7}},"target":"https://pkg.go.dev/bytes?utm_source=gopls"},{"range":{"start":{"line":4,"character":2},"end":{"line":4,"character":5}},"target":"https://pkg.go.dev/fmt?utm_source=gopls"},{"range":{"start":{"line":5,"character":2},"end":{"line":5,"character":4}},"target":"https://pkg.go.dev/io?utm_source=gopls"},{"range":{"start":{"line":6,"character":2},"end":{"line":6,"character":5}},"target":"https://pkg.go.dev/log?utm_source=gopls"},{"range":{"start":{"line":7,"character":2},"end":{"line":7,"character":5}},"target":"https://pkg.go.dev/net?utm_source=gopls"},{"range":{"start":{"line":8,"character":2},"end":{"line":8,"character":9}},"target":"https://pkg.go.dev/net/url?utm_source=gopls"},{"range":{"start":{"line":9,"character":2},"end":{"line":9,"character":9}},"target":"https://pkg.go.dev/strings?utm_source=gopls"},{"range":{"start":{"line":11,"character":2},"end":{"line":11,"character":24}},"target":"https://pkg.go.dev/golang.org/x/net/proxy?utm_source=gopls"},{"range":{"start":{"line":16,"character":30},"end":{"line":16,"character":44}},"target":"https://<IP_ADDRESS>:8080"},{"range":{"start":{"line":63,"character":43},"end":{"line":63,"character":58}},"target":"https://<IP_ADDRESS>:51837"}]
[Error - Received] 14:27:23.231 PM #3 JSON RPC cancelled
[Trace - 14:27:23.231 PM] Received response 'textDocument/codeAction - (2)' in 372ms.
Result: null
[Trace - 14:27:23.231 PM] Received response 'textDocument/documentSymbol - (4)' in 372ms.
Result: [{"name":"main","detail":"()","kind":12,"range":{"start":{"line":14,"character":0},"end":{"line":29,"character":1}},"selectionRange":{"start":{"line":14,"character":5},"end":{"line":14,"character":9}}},{"name":"handleClientRequest","detail":"(client net.Conn)","kind":12,"range":{"start":{"line":31,"character":0},"end":{"line":81,"character":1}},"selectionRange":{"start":{"line":31,"character":5},"end":{"line":31,"character":24}}}]
[Trace - 14:27:23.232 PM] Received response 'textDocument/codeLens - (5)' in 199ms.
Result: null
[Trace - 14:27:23.232 PM] Received response 'textDocument/foldingRange - (6)' in 153ms.
Result: [{"startLine":2,"startCharacter":8,"endLine":11,"endCharacter":25,"kind":"imports"},{"startLine":14,"startCharacter":13,"endLine":28,"endCharacter":2},{"startLine":17,"startCharacter":16,"endLine":18,"endCharacter":16},{"startLine":21,"startCharacter":6,"endLine":27,"endCharacter":32},{"startLine":23,"startCharacter":17,"endLine":24,"endCharacter":17},{"startLine":31,"startCharacter":43,"endLine":80,"endCharacter":24},{"startLine":32,"startCharacter":19,"endLine":33,"endCharacter":8},{"startLine":39,"startCharacter":16,"endLine":41,"endCharacter":8},{"startLine":47,"startCharacter":16,"endLine":49,"endCharacter":8},{"startLine":52,"startCharacter":33,"endLine":53,"endCharacter":39},{"startLine":54,"startCharacter":9,"endLine":59,"endCharacter":3},{"startLine":55,"startCharacter":49,"endLine":56,"endCharacter":37},{"startLine":57,"startCharacter":10,"endLine":58,"endCharacter":29},{"startLine":64,"startCharacter":16,"endLine":66,"endCharacter":8},{"startLine":69,"startCharacter":16,"endLine":71,"endCharacter":8},{"startLine":73,"startCharacter":25,"endLine":74,"endCharacter":63},{"startLine":75,"startCharacter":9,"endLine":76,"endCharacter":21}]
[Trace - 14:27:23.440 PM] Received notification 'window/logMessage'.
Params: {"type":1,"message":"2020/12/01 14:27:23 go/packages.Load: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules'\n\n\tsnapshot=1\n\tdirectory=/home/username\n\tquery=[./]\n\tpackages=0\n"}
[Error - 2:27:23 PM] 2020/12/01 14:27:23 go/packages.Load: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules'
snapshot=1
directory=/home/username
query=[./]
packages=0

[Trace - 14:27:23.614 PM] Received notification '$/progress'.
Params: {"token":"8674665223082153551","value":{"kind":"report","message":"go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules' : packages.Load error"}}
[Trace - 14:27:23.615 PM] Received notification 'window/logMessage'.
Params: {"type":1,"message":"2020/12/01 14:27:23 errors diagnosing workspace: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules'\n: packages.Load error\n\tsnapshot=1\n\tdirectory=file:///home/username\n"}
[Error - 2:27:23 PM] 2020/12/01 14:27:23 errors diagnosing workspace: go [-e -json -compiled=true -test=true -export=false -deps=true -find=false -- ./]: exit status 1: go: cannot find main module; see 'go help modules'
: packages.Load error
snapshot=1
directory=file:///home/username
[Trace - 14:27:23.769 PM] Sending request 'textDocument/codeAction - (7)'.
Params: {"textDocument":{"uri":"file:///home/username/workspace/projects/http2socks5/main.go"},"range":{"start":{"line":0,"character":0},"end":{"line":0,"character":0}},"context":{"diagnostics":[]}}
[Trace - 14:27:23.770 PM] Received response 'textDocument/codeAction - (7)' in 0ms.
Result: null
[Trace - 14:27:31.975 PM] Sending request 'textDocument/codeAction - (8)'.
Params: {"textDocument":{"uri":"file:///home/username/workspace/projects/http2socks5/main.go"},"range":{"start":{"line":16,"character":46},"end":{"line":17,"character":16}},"context":{"diagnostics":[]}}
[Trace - 14:27:31.976 PM] Received response 'textDocument/codeAction - (8)' in 0ms.
Result: null
[Trace - 14:27:33.485 PM] Sending request 'textDocument/codeAction - (9)'.
Params: {"textDocument":{"uri":"file:///home/username/workspace/projects/http2socks5/main.go"},"range":{"start":{"line":17,"character":16},"end":{"line":17,"character":16}},"context":{"diagnostics":[]}}
[Trace - 14:27:33.485 PM] Received response 'textDocument/codeAction - (9)' in 0ms.
Result: null
[Trace - 14:27:53.236 PM] Received notification 'window/logMessage'.
Params: {"type":3,"message":"2020/12/01 14:27:53 background imports cache refresh starting\n"}
[Info  - 2:27:53 PM] 2020/12/01 14:27:53 background imports cache refresh starting
[Trace - 14:27:53.274 PM] Received notification 'window/logMessage'.
Params: {"type":3,"message":"2020/12/01 14:27:53 background refresh finished after 42.990432ms\n"}
[Info  - 2:27:53 PM] 2020/12/01 14:27:53 background refresh finished after 42.990432ms

Besides, I found something that the error only occurred when I open the whole home directory as the workspace in vscode.
Whenever I only open the project folder as the workspace, it won't occur.
It seems that the gopls treats my home directory as the project folder.
However, the gopls should not tell me that it cannot import golang.org/x/net as the gopath was already defined in the PATH.
It is hard for me to accept that I should only open my project folder as a workspace as an answer to this issue.
I'm using remote-ssh extension.
For me, I would like to have my whole home directory to be the workspace as the vscode will become a file explorer.
I can not always open a project folder as the workspace. Whenever I'm opening something else, the gopls will run automatically to generate a notification.
Thanks for your help. I do hope that you would fix this issue.

@fourdim Thanks for sharing the trace.
VS Code and language server assume the open folder as the project root. For people who want to work on multiple related projects,  VS Code supports multi-root workspace mode.
Since there is no main module, the error message is not completely wrong IMHO, but I agree that better error message that explains why users are getting those errors would be helpful.
gopls/v0.5.4 adds support for opening a directory above the main module but this is activated only when there is only one module in a subdirectory. It's common to have multiple project directories under home directory; I don't think this feature is applicable to users who open the entire home directory.
I don't think the experimentalWorkspaceModule feature is applicable to this use case either - the feature assumes all the modules in the folders are somewhat related, but in this particular case, that's not necessarily true.
BTW VSCode remote-ssh extension allows to open a target folder or vscode workspace, so it doesn't limit you to open only from the home directory. I myself use remote-ssh often and usually use VSCode's "Open Folder" function that allows me to navigate the remote directory and open a separate window per each project. VSCode caches the directory configuration so I can easily resume my work by choosing it when reconnecting. By keeping the workspace project-scoped, vscode and language server becomes more performant - the language server and the vscode index all the symbols and references, set up file watchers, and do many things for everything under the folder.
gopls/v0.5.4 should support the case where only one subdirectory contains a project https://github.com/golang/tools/releases/tag/gopls%2Fv0.5.4

https://golang.org/cl/272346 will improve these error messages, but yes, in this case, the best course of action would be to add each module as its own workspace folder.

@hyangah @stamblerre Thanks for your reply. You can close this issue according to your need.


Add region_alias support for multiple aliases in a single region

Multiple region_aliases can now be in the same region, and with
the prepend_region_alias_to_stack_names flag set to true, the region_alias
will be part of the stack name for easier readability.
prepend_region_alias_to_stack_names: true
region_alias:
  - production: us-east-1
stacks:
  production:
    vpc:
      template: vpc.json

The config above would create a stack named "production-vpc"
It would also resolve parameters from:
parameters/vpc.json
parameters/us-east-1/vpc.json
parameters/production/vpc.json

Will this break how we currently define region aliases (as a hash)? It would be great if we could handle both to avoid having to upgrade previously written stack_master.yml files..

I think that was a typo in my example, but let me check. I can also rebase this now that s3 is merged in. And in the next week or so I should be able to work out the test failures.

Hi @flyinbutrs and @stevehodgkiss
I chanced upon this pull-request, and this feature would really be useful to me too, as I need the ability to prefix the stack-names with prod/dev/test etc.
Just thought I'd touch base to ask if you were able to work out the test failures etc.
A big +1 from my side for this feature :-)

I'd honestly rather see a breaking change to just get rid of stack master using regions as keys or aliases.
I have never seen any project deal in terms of "regions" for separate stacks and I've always seen stacks separated in terms of environment (dev, staging, prod).
I highly suggest that stack master be overhauled to kill the region alias key in a major breaking release and move to using environments.  Make region just an attribute of the stack so that an environment can be multi region if needed.

I highly suggest that stack master be overhauled to kill the region alias key in a major breaking release and move to using environments. Make region just an attribute of the stack so that an environment can be multi region if needed.

I agree, but I think we need to come up with a better way of handling "environments" before that can happy. Open to opinions!

This seems to have been super-seeded by #221

This PR is quite stale and has been superseeded. Closing for now but re-open when/if you're ready.


create z: order migration tool

Used to flip the z: order, and will also make a list of widgets with negative z and will change them to postive but will not add targets in the widget player since it won't know the intended target. But it can generate a list that users can use to manually add those.

decided not to do this


texelFetchOffset is not supported in Metal

Using texelFetchOffset when generating a metal shader will fail, because the read function only takes 2 arguments.
program_source:139:34: error: no matching member function for call to \'read\'
    float4 texel0 = tRenderTasks.read(uint2(uv), 0, int2(0));
                    ~~~~~~~~~~~~~^~~~
/System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3802/Libraries/lib/clang/802.4/include/metal/metal_texture:1669:24: note: candidate function not viable: requires at most 2 arguments, but 3 were provided
  METAL_FUNC vec<T, 4> read(ushort2 coord, ushort lod = 0) const thread
                       ^
/System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3802/Libraries/lib/clang/802.4/include/metal/metal_texture:1677:24: note: candidate function not viable: requires at most 2 arguments, but 3 were provided
  METAL_FUNC vec<T, 4> read(uint2 coord, uint lod = 0) const thread
                       ^
/System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3802/Libraries/lib/clang/802.4/include/metal/metal_texture:1686:24: note: candidate function not viable: requires at most 2 arguments, but 3 were provided
  METAL_FUNC vec<T, 4> read(ushort2 coord, ushort lod = 0) const device
                       ^
/System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3802/Libraries/lib/clang/802.4/include/metal/metal_texture:1694:24: note: candidate function not viable: requires at most 2 arguments, but 3 were provided
  METAL_FUNC vec<T, 4> read(uint2 coord, uint lod = 0) const device
                       ^
/System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3802/Libraries/lib/clang/802.4/include/metal/metal_texture:1704:24: note: candidate function not viable: requires at most 2 arguments, but 3 were provided
  METAL_FUNC vec<T, 4> read(ushort2 coord, ushort lod = 0) const constant
                       ^
/System/Library/PrivateFrameworks/GPUCompiler.framework/Versions/3802/Libraries/lib/clang/802.4/include/metal/metal_texture:1712:24: note: candidate function not viable: requires at most 2 arguments, but 3 were provided
  METAL_FUNC vec<T, 4> read(uint2 coord, uint lod = 0) const constant

I'm not totally sure if this is a spirv_cross or an application error, because this:
texelFetchOffset(sampler, position, lod, offset)
can be replaced with this:
texelFetch(sampler, position + offset, lod)
but would require some unnecessary guarding for platforms.

I guess the MSL backend just doesn't consider this as a special case. Should be easy to fix. MSL codegen can apply the offset in the shader.


Overlapping datapoints in two consecutive osf file.

When reading/ parsing two consecutive osf files, there is over lapping data points that exists at the end of the first .osf file and the begining of the second .osf.
Is it designed to be like this when creating the osf file? Or is there an error here ?
We are experiencing this at Enginius Tec.
Here is an example:

but the record already exists in the database

The OSF format allows something like this.  There is basically no restriction on the time base in the format. Can you provide us with sample files for this and a small code example?

Here is an example:
I am looking at device<PHONE_NUMBER>
Date: 22.02.2024
Last value in OSFZ file "202402022_232832.osfz"

First value in OSFZ file "20240222_233333.osfz"

A code example is not really useful here, since we are facing the described error not during decoding but we stubbled upon it when we tried pushing the data of the OSF files to a database.


create pull request in main branch and merge

create a new branch "develop"

title "First release to production"


Addition of WindTunnel Executer

This PR implements connects the WindTunnel scenario simulation to its own executer on the backend. In practice, we just need to change on the client the name of the api_method to call on the backend, which is changed inside the scenario without users configuration. In this sense, no interference occurs on the user side!
Previously, the backend for OpenFOAM was hard-coded to support simulations of the WindTunnel. However, this implies that no other CFD simulations can be run with OpenFOAM. The next step is to add the low-level implementation of OpenFOAM to run all possible/available commands (like GROMACs) through the use of the Commands&Flags methodology.
A PR on the backend will follow!
Disclaimer: The perfect solution we are working towards is a Pipe of commands run always under the same input folder. However, this will still take some time and practical discussion. Therefore, in the meantime we do not compromise both the low-level and the WindTunnel.

Ok, thanks Ivan.


Add 0x Protocol V2 ExchangeWrapper

https://blog.0xproject.com/introducing-0x-protocol-v2-9f5bda04d38d
Projected Launch: Late July 2018

We should consider adding multi-order support when we implement v2


Load the app in console

I was poking around the console and wanted to check out the routes. @jodosha had mentioned I could access them by using MyApp::Routes but I kept getting a missing constant error.
@joneslee85 informed me in chat that I had to actually load the app, which would mount the Routes. He suggested I run MyApp::Container.new which did make Routes available.
It'd be nice if I didn't have to do that when poking around the console. It would also be nice to figure out a way to expose routes for routing specs, but that is a separate issue.

@jc00ke @joneslee85 would you mind to try w/ the referenced PR?
% lotus new bookshelf --lotus-head=true

Then amend the generated Gemfile like this:
gem 'lotusrb', github: 'lotus/lotus', branch: 'preload-apps-in-console'

% bundle
% bundle exec lotus console
irb(main):001:0> Web::Routes
=> #<Lotus::Routes:0x007fd8b9bdf990 @routes=#<Lotus::Router:0x007fd8ba94bd90 @router=#<HttpRouter:0x3fec5d4a5eb4 number of routes (0) ignore_trailing_slash? (true) redirect_trailing_slash? (false)>
================================================================================================================
Root (0 matchers)>>


cross-platform: protect stack on xplat

We have __declspec(guard(overflow)) in place for Windows. Adding -fstack-protector flag
for a similar expectation on xplat

Hi @obastemur - I don't think -fstack-protector is the same as __declspec(guard(overflow))- i think its more analogous to https://msdn.microsoft.com/en-us/library/8dbf701c.aspx. However, it's probably goodness to have anyway, so LGTM- would be nice if @curtisman or @LouisLaf take a look before merging too

Yes, -fstack-protector is more like /GS.  Please change the commit message.
Also, should we use -fstack-protector-strong instead?

We do not use Linux branch anymore.
Closing this one an going to send it again to master


Cannot use from behind a firewall

I'm a corporate user and have no authority to open firewall ports. Please add proxy server support.
The error I'm getting is:
F0909 17:08:40.408103   14144 connector.go:73] Failed to start XMPP conversation: Failed to dial XMPP service: Failed to connect to XMPP server: dial tcp [2404:6800:4003:c02::7d]:443: i/o timeout
FYI, I was able to run connector-init fine, so proxy for HTTP requests already seems to work.
Thanks.

There is a bug open for adding proxy server support. I'll get started on that later this week.

I'm finishing up local-only support, which means that no Internet connection is actually needed. This works when all users are on the same subnet because it uses mDNS to announce/discover. I'm guessing that this isn't appropriate for your corporate environment, but it's worth mentioning.

Thanks Jacob

@wcruppel Let's continue this conversation over at #58


Password authentication problem for Chef Bootstrapping process

Hi There,
Gaffoor here....!!
I am trying to execute Knife Bootstrap command prompt for Ubuntu node,
Used:
" knife bootstrap <IP_ADDRESS> -U ubuntu -i ./chef/gaffoor.pem --sudo -N ip-172-31-15-139.us-east-2.compute.internal "
Placed
.Pem : C:\Practice\Chef\chef-repo
starter kit : C:\Practice\Chef\chef-repo
chefdk : C:\Practice
But asking " Password Authentication ".
Attached SS for reference.

Hi ,
Here it was unable to find your aws machine  pem key file , make sure of
your pem file path or place it in Chef-repo folder and just specify
./xyz.pem , please update the issue accordingly
On Fri, 22 Nov, 2019, 12:15 PM Tomcruise69<EMAIL_ADDRESS>wrote:

Hi There,
Gaffoor here....!!
I am trying to execute ,
Used:
" knife bootstrap <IP_ADDRESS> -U ubuntu -i ./chef/gaffoor.pem --sudo -N
ip-172-31-15-139.us-east-2.compute.internal "
Placed
.Pem : C:\Practice\Chef\chef-repo
starter kit : C:\Practice\Chef\chef-repo
chefdk : C:\Practice
But asking " Password Authentication ".
Attached SS for reference.
[image: Chef paasword]
https://user-images.githubusercontent.com/46358830/69403560-e593ba80-0d20-11ea-9fbd-190ddde77de4.PNG
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/QT-DevOps/DevOpsIssues/issues/654?email_source=notifications&email_token=ALT4PAATPT4U4ULA4MM3MZ3QU55XTA5CNFSM4JQMQGJKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4H3JVSEA,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALT4PAC2LB6AACYRIAVOVULQU55XTANCNFSM4JQMQGJA
.

Hi
but there is a connection timeout issue and SSH connection failed issue.

Is 22 port of your node open for all requests

you did a mistake in highlighted text please correct with .\chef\gaffoor.pem
because in windows path are seperated by \ (back slash) in linux paths are seperated by / (forward slash)
knife bootstrap <IP_ADDRESS> -U ubuntu -i  ./chef/gaffoor.pem --sudo -N ip-172-31-15-139.us-east-2.compute.internal
I thinks this information helpful to you if not please ignore
if you done already please close the issue

please pass node pemfile  with location
knife bootstarp ip --sudo -i pemfile-withlocation -x ubuntu -N name


Windows: is Python 2.7 support planned?

Good evening! Are you planning to support Python 2.7 on Windows? It may be very useful.

@gunan and @mmry can correct me if I'm wrong - but we don't have any immediate plans to add Python 2 support for Windows.

CC @mrry (corrected username)
AFAIK, unless we build python 2.7 from sources using Visual studio 2015 or 2017, it is not possible to build tensorflow with python 2.7.
Therefore, we will not support python 2.7 on windows.

Any custom Python 2.7 libraries can easily be built with VS 2015, even if Python 2.7 is built with VS2008.

Even if that might work (and I have been able to run simple TensorFlow programs using Python 2.7 on Windows), I don't think we'd want to support such a configuration. Some of the issues discussed here are relevant:
http://siomsystems.com/mixing-visual-studio-versions/


Dockerize

To make hosting the bot easier, a Docker image containing the bot and the PostgreSQL database has to be created.

Is the database not hosted separately already?

The database is indeed currently hosted separately, but it will be much easier to manage if it is all contained within a single Docker container.

From: Tony @.>
Sent: 11 October 2022 23:50
To: martinmladenov/RankingBot @.>
Cc: Martin Mladenov @.>; Author @.>
Subject: Re: [martinmladenov/RankingBot] Dockerize (Issue #103)
Is the database not hosted separately already?
—
Reply to this email directly, view it on GitHubhttps://github.com/martinmladenov/RankingBot/issues/103#issuecomment-1275312036, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AHHYA7HCIYAVYAV4LHG4GK3WCXOJTANCNFSM6AAAAAARCUIXYA.
You are receiving this because you authored the thread.Message ID: @.***>

I remember having a bad time trying to do that at some point with a Redis cache. I feel like this would make more sense with a compose file or with something like SQLite maybe but having them hosted separately is definitely easier.

Docker Compose would be ideal I think.

I'll look into it in the foreseeable future 👍


Add MAVEN_CENTRAL_OVERRIDE_URL_PROPERTY and GOOGLE_OVERRIDE_URL_PROPERTY

Expected Behavior
Similar to PLUGIN_PORTAL_OVERRIDE_URL_PROPERTY, please provide a MAVEN_CENTRAL_OVERRIDE_URL_PROPERTY property and a GOOGLE_OVERRIDE_URL_PROPERTY
See https://github.com/gradle/gradle/blob/be698f4d3787fb0a96566703c210c439d43a2371/subprojects/dependency-management/src/main/java/org/gradle/api/internal/artifacts/BaseRepositoryFactory.java#L29
Implementation would be here:
https://github.com/gradle/gradle/blob/49e767c3f0b25154927fe2bf6a9b4db2c4a4cf56/subprojects/dependency-management/src/main/java/org/gradle/api/internal/artifacts/repositories/DefaultBaseRepositoryFactory.java#L142-L176
Current Behavior (optional)
The URLs for mavenCentral() and google() are hard coded with no way to override them.
https://github.com/gradle/gradle/blob/49e767c3f0b25154927fe2bf6a9b4db2c4a4cf56/subprojects/core-api/src/main/java/org/gradle/api/artifacts/ArtifactRepositoryContainer.java#L52-L53
Context
This would allow a work around for gradle init which uses mavenCentral()
https://github.com/gradle/gradle/issues/4195

Yes please! And while you are at it, please promote these variables as a stable feature and officially document them.

Thank you for your interest in Gradle.
This is very unlikely to happen. We do not want an ability to have declared repositories actually talk to a different URL than what Gradle advertises.
However we are aware that configuring repository for both the open world and a company internal repository is not as easy as it could be.
If you think we are missing a reason for considering this feature, please explain your use case.

However we are aware that configuring repository for both the open world and a company internal repository is not as easy as it could be.

@ljacomet, are there any resources on how to set a project up to work both in the open world and internally? My team is preparing to open-source a Gradle project, and we're struggling to figure out how to offer a clean version of the codebase that can be run in the "real world" while also ensuring that we can internally override the repositories with our private mirror. Something like this feature request, along with properties to optionally provide credentials, would make our use case massively more intuitive and easier.

@ljacomet, are there any documentation resources on how to set a project up to work both in the open world and internally with the current capabilities?

For most cases, this can help: https://docs.gradle.org/current/userguide/init_scripts.html#sec:init_script_plugins - you'd have your code set up so that it can build externally, but override the repos in an init script.
Or, your could parametrise your repo definition to allow for overrides with if / else statements.


How to implement a single whispercpp with qnn on Qualcomm SoC?

Thanks for your work. I am new on using Qualcomm SoC systems. Just curious how can we implement whisper or llama cpp separately from this project?

I don't know what's the meaning you said.

I'd like to close this opening issue accordingly. of course, you can re-open it in the future as your need.thanks for your understanding.


total file size must be under 10MiB

(I mentioned on discord too, but I'll write it here too so its easier to keep track)
RuneLite only allows external plugins under 10MiB, and clearly thats an issue becuase the English dialogue transcipt is larger than 10MB by itself.
the solution is to download transcripts from a github repository on start. (so download pt_br files if thats the selected language)
I have already made a similar system for my japanese plugin, which downloaded files from a data repository i made for the plugin
My idea is to use runelingual-transcript repository that iakee made already if thats fine, but it can be made on a completely new repository too
for now im working on it here, ill post things here when I have updates
please post any concerns and anything else

downloading from the transcript repository should solve this issue


Fix IME on chromium apps and wayland

Tweaks chrome flags to fix wayland IME
prev flags contain --ozone-platform-hint=auto
*Update _IM_MODULE since raplced KDE with GNOME
Revert "prev flags contain --ozone-platform-hint=auto"
Revert "Tweaks chrome flags to fix wayland IME"
Add wayland feature flag for chrome as written in fcitx wiki
Add some fcitx config for gtk and gnome
gkt module only exsits in home-manager
Missing enable gtk

Fixes #689

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3751#note_2202629

Initial support for text-input-v3 in chromium should be there from M129 onwards, which can be enabled using the "Wayland text-input-v3" (#wayland-text-input-v3) experimental feature flag from chrome://flags/ or command line switches --enable-wayland-ime --wayland-text-input-version=3, provided ozone/wayland is enabled already.

Oh... I don't need to wait v130?
> google-chrome-stable --version
Google Chrome 129.0.6668.58

Worked in chrome!
But not in vscode. I think I need to wait for electron updates for them.

Yeah, using chromium 124 as written in https://www.electronjs.org/docs/latest/tutorial/electron-timelines


Region hiding freezes screen when mouse is moving over the region

Describe the bug
It happens when annotating an image, for example with rectangles.
When a rectangle is hidden while the mouse is moving over it, the screen freezes for a few seconds. It can only happen when using the shortcut (to have the mouse moving over the region while hiding it)
To Reproduce
Steps to reproduce the behavior:

Open a task with an image to label
add a region, for example a rectangle. Select that region
use the shortcut alt+h to make the region appear and disappear. Don't move the mouse. It should work as intended
keep doing 3 while moving the mouse over the region. The screen will freeze and hiding the rectangle will take a few seconds. The freeze stops when the rectangle is finally hidden. The freeze doesn't happen when the mouse is not moving or when the mouse is moving anywhere other than over the selected region.

Expected behavior
Screen should not freeze when moving over a region that is being hidden.
Screenshots
In this video, I'm hitting alt+h non stop, at constant pace, from 0:13 to 0:28
https://github.com/user-attachments/assets/97cef024-b6cb-43f1-a01b-045a418cee07
Environment (please complete the following information):

OS: observed on Mac and Ubuntu
Label Studio Version:  1.12.X and develop branch

Additional context
This happens to me all the time when I'm adding missing element(s) to a pre-annotated image.

Hi @LouisJULIEN - thanks for this report, running it by some frontend folks on the team :+1:

/jira create

I just realised that this also happens on region deletion. The procedure to reproduce the bug is the same, only that the region should be deleted instead of hidden.

Hello, do you have any update on that issue? I encounter it on a daily basis, I don't think I'm the only one.

up @jombooth

up @jombooth


Added workflow to backup postgres database

Context
We require regular backups of the production database as part of our DR strategy.
Changes proposed in this pull request
Adds a workflow that backups up the production database on a schedule.
Guidance to review

Review test run here.

Checklist

[ ] Attach to Trello card
[ ] Rebased main
[ ] Cleaned commit history

 Setup deploy pipeline for Refer serious misconduct


TypeError: Cannot read property 'elementTypes' of undefined

It's great to finally see an actively maintained documentation generator for TypeScript! But I tried running typedoc on my project, doppio on its new-objects branch, and it failed:
$ typedoc --out doc/ --mode file --module commonjs --target ES3 src/

Using TypeScript 1.4.1 from /usr/local/lib/node_modules/typedoc/node_modules/typescript/bin

/usr/local/lib/node_modules/typedoc/bin/typedoc.js:1297
                if (node.elementTypes) {
                        ^
TypeError: Cannot read property 'elementTypes' of undefined
    at extractTupleType (/usr/local/lib/node_modules/typedoc/bin/typedoc.js:1297:25)
    at extractType (/usr/local/lib/node_modules/typedoc/bin/typedoc.js:1271:28)
    at visitVariableDeclaration (/usr/local/lib/node_modules/typedoc/bin/typedoc.js:1768:41)
    at visit (/usr/local/lib/node_modules/typedoc/bin/typedoc.js:1499:32)
    at /usr/local/lib/node_modules/typedoc/bin/typedoc.js:1928:25
    at Array.forEach (native)
    at visitObjectLiteral (/usr/local/lib/node_modules/typedoc/bin/typedoc.js:1927:37)
    at visitVariableDeclaration (/usr/local/lib/node_modules/typedoc/bin/typedoc.js:1760:37)
    at visit (/usr/local/lib/node_modules/typedoc/bin/typedoc.js:1499:32)
    at /usr/local/lib/node_modules/typedoc/bin/typedoc.js:1928:25

Here's what you can do to reproduce the error (note: will take awhile due to repository size; build time is slow the first time because it needs to grab and extract a large file):
git clone https://github.com/plasma-umass/doppio
cd doppio
git checkout new-objects
bower install
npm install
grunt dev-cli
typedoc --out doc/ --mode file --module commonjs --target ES3 src/

Note that the grunt dev-cli step is required to generate includes/JVMTypes.d.ts, which is an 8MB declaration file containing TypeScript interface files for JVM objects (you'll notice the build system will first do a build that fails to typecheck due to the missing declarations -- required for bootstrapping :) ).
Let me know if there are any options I might be missing! Hopefully we can get typedoc working as beautifully on this new branch as it does on the master branch.

Hi jvilk, nice to hear from you. I've checked the error location and found a trivial error. However I can currently not check it against you project as I'm not able to install it. On Windows the execSync dependency fails and on my Mac I cannot run the javac task. Would you mind to share your JVMTypes.d.ts with me?

On Windows the execSync dependency fails and on my Mac I cannot run the javac task.

Ahh yeah, the dreaded outdated execSync package! They've yet to accept my PR fixing the issue...
I believe this version is up-to-date; let me know if it fails to compile!

Thank you for sharing this one with me. I've tested the fix against your project and it seems to work right now. Well, as far as I can tell as doppio looks like a massive project. Kudos!

Thanks! It's bigger than the average JS project, and I'm hoping to improve the internal documentation so it looks nice in typedoc-generated documentation. :smile:
I look forward to the next release w/ the fix!

Hey @sebastian-lenz, when are you planning to make a release with this fix?

:tada:
v0.3 is now on available on npm.

And it works! Thanks!

Great to hear. Thanks!


Update translations from Fedora Weblate

Update translations from Fedora Weblate

[ ] po-refresh

#882 is newer version


Prevent 'meta' namespace collision fixes #368

meta is too generic and causes namespace collisions with many existing input documents. This should be considered a bug and we need to fix this in order for LokiJS to be usable with todays API outputs.

How can the test fail? I think the test must have failed before I made changes.

I was wrong. Testing on master is fine. I don't know what I missed.

i'm not the owner of this project, but i see you're investigating and on the case.  :+1:

Failure is in memory adapter paging size tests... you probably increased the size of the objects just enough that two of them couldn't fit into one '128byte page'... test.
I should probably tweak the page size to just ensure only 1 object will fit on a page and raise expect to 5.

@obeliskos I shouldn't have tried to PR on top of a project that is heavily optimized. :stuck_out_tongue_winking_eye:
Is this a relatively easy fix I can apply on top?

no its a ridiculously small page so that i could test paging with only a few test documents but apparently just big enough that more than one serialized document was able to fit with in it before but not after... i'll try to make fix that in a min.

ok, i forgot to reference this pr or related issue, but i have checked in changes to that unit test so that it would pass (both) before and after pr.
as mentioned though this would have to be a collection or database level option like :
// either
var coll = db.addCollection("users", { useAlternateMeta: true });
// or
var coll = db.addCollection("users", { alternateMeta: '$lokimeta' });
// or
var db = new loki('test.db', { useAlternateMeta: true });
// or
var db = new loki('test.db', { alternateMeta: '$lokimeta' });

(option names are just examples)
i am up for hearing pros and cons, i might go for user provided name prop on collection if it were me but this would have to be repeated everywhere in that case, if at db level you would probably need module global variable to keep setting/value in or inject into collection options in collection constructor.

Hey @Redsandro , were you planning on revisiting this or should we close this?

I was planning to revisit, but more pressing matters keep falling on my path.
I will suspend this for now. I might open a new PR sometime in the future, but I encourage anyone to beat me to it.

Ok, thanks... I certainly understand.   So to summarize as we put this on hold :
For this particular case where you are inserting documents which may already have conflicting meta properties, we would need a pr like this to allow defining alternate meta property name.
I'll add that for other use cases which are only concerned with our meta properties when extracting from a loki database, we have a 'removeMeta' option you can pass to chained data() call to remove $loki and meta properties from results.

Hi @obeliskos, yes you are correct. But also, I wanted to (investigate if Loki works properly when we) stop meta from being created in the first place.
I'm having a performance-critical app, and I think in my case the metadata is irrelevant. Every time I insert 10000 documents, Loki will iterate all that and create 10000 new keys on them, with some dates. Does it also create 10000 objects (meta)? Or does it make 1 object and assign it's reference to the objects that are inserted?
All I really want is to do everything by reference. Not add objects on insert, and force clones on result data.
This probably breaks database storage adapters, but I'm using Loki with read-only live generated data.

So we might want to more officially support this later but this can sort of be done now if you are willing to take responsibility over collection (meaning this is currently unsupported and you could mess up collection integrity of you mix this method with other insert/update/remove methods)
I have created a loki sandbox gist for utilizing standalone collections as 'snapshots' whereby you :

manually construct the collection outside of the context of a 'loki' database object instance
you manually assign the documents to the internal 'data' property
you manually apply any indices (if needed)
you perform your queries
you only use that collection instance again for querying
the example gist uses detached collections, instances via 'new loki.Collection' which is safer than attempting this within a database instance which you might want to persist.  If you never need persistence you could probably aggregate them within a single database using loki.addCollection method.

This looks rather interesting @obeliskos, thank you for writing up this gist.
Do I need to create an index manually to immitate what happens when I would insert a collection "by the book"?

Normally indices are maintained as you insert/update/remove, but since this method circumvents that process, you will need to run ensureIndex to update binary indices after every time you 'set' or modify the 'data' document array.
Normally on insert, we create $loki and meta properties.  The $loki has its own unique index which is leveraged by calls to collection.get().  The method i described adds neither $loki nor meta properties.
Preferably you would might want to 'bring you own' unique id in your document and apply an unique index on that column.  With a unique index you would perform a collection 'by()' to lookup by a unique key defined by collection.ensureUniqueIndex(propertyName) invoked after changing data array  :
coll.ensureUniqueIndex("id");

So I guess I would verify how you were using the $loki id before if you were not persisting the database. Do you have another uniquely identifiable property you can make unique?

@obeliskos thank you for your elaborate response.

I would verify how you were using the $loki id before

I'm not sure how it was used internally, but my simplified usage is:

loki.insert([a bulk of documents])

once

loki.chain().find().compoundsort().offset().limit().data().map()

Dozens of times, with non-predictable find and sort parameters

(PS - using map because mapReduce has a reduce stage which I don't need)

Do you have another uniquely identifiable property you can make unique?

Yes, but they are of type string, in some cases like ObjectID from MongoDB.

BTW, can I do this to make separate collections?
let coll1 = db.addCollection('foo', {clone: false})
let coll2 = db.addCollection('foo', {clone: false})
let coll3 = db.addCollection('foo', {clone: false})

Or does foo need to be unique because db links them internally?
(An unknown number of collections is made on the fly. Not sure if I need to randomize the collection name)


Added description on how to create the virtual environment

The description is needed to avoid the headache caused by Microsoft Visual Studio changes and package installation fails.

Hello @geniusbabak. Thanks for your contribution!
I believe that the requirement is for "Microsoft Visual C++ 14.0", not "Visual Studio 2019". And besides, this seems to be a requirement only on Windows. Could you check if "Microsoft Visual C++ 14.0" is required on Linux systems as well?

https://stackoverflow.com/questions/68960510/i-am-trying-to-install-pypesq-and-pesq-but-i-keep-getting-stuck-with-this-py
https://blog.karatos.in/a?ID=01650-9b50dede-c174-42c6-b849-01b2abc8088d
https://blog.csdn.net/k741696755/article/details/105561665

Please modify the PR to describe if this is a Windows/Linux requirement accordingly.


DecimalField inferred as Any

Hello! Many thanks to your effort on trying to make django-stubs compatible with Pylance.
I tried this package and the intelliSense for Foreignkey works nicely. However, the other fields such as DecimalField, PositiveSmallIntegerField, etc. are still interferred to Any when being called.
I've added django-autotyping to INSTALLED_APPS, and run the command generate_stubs. The stubs for my models are generated under the folder typings. I then add typings to Pylance's settings python.analysis.stubPath.
Is there anything I missed? Thank you.

Hello, thanks for the feedback. I'm planning on fixing the issue you are describing directly in the stubs. I have a pending PR for this: https://github.com/typeddjango/django-stubs/pull/1900.
Unfortunately, it requires non trivial changes in the mypy plugin, and I would also like to use a better solution (something as described in https://github.com/microsoft/pyright/discussions/6914), but would require mypy to support https://github.com/python/mypy/issues/3737.

I'll see if I can add a temporary rule in django-autotyping to basically applies the pending changes I have in the stubs.


Check that imports use the same letter-case as module name (derived from file name)

@dagtveit stumbled upon issue related to having two instances of the same module that was intended to be singleton:

I am trying to share a service class across nested custom elements. but the service class dosnt have the same values.

He found out that it was caused by inconsistent letter-cases

it was due to that i wrote small d in documentData in one of the imports and big D in the other one. laaaaaaaaalllalalalal hhehehehe

It reminded me, that I had made the same mistake once, and it took me also a bit time to figure out the problem.
It would be nice, if the linter would detect this issue as well.

May be better to issue an warning if the case of the file name is not exactly the same as what was requested. For one, that in itself could be a problem on linux installations set up to be case sensitive.
Either way, its easier to check for this in the reworked code.