[🐞] History navigation inconsistent behavior: RequestHandler (onGet, onRequest) and routeLoader$ don't execute similarly in MPA and SPA

Which component is affected?
Qwik City (routing)
Describe the bug
When using history navigation, whether by using the browser back/forward buttons, or window.history (ex: window.history.back()), RequestHandler (onGet, onRequest) and routeLoader$ aren't executed depending on what API has been used for prior navigation.
Example:

if you click the browser's back button after SPA navigation, whether by using <Link> tags or useNavigate(), RequestHandler (onGet, onRequest) and routeLoader$ are executed.
if you click the browser's back button after MPA navigation, whether by using <a> tags, window.location.href = '/path', server redirects, or by manually changing URLs, RequestHandler (onGet, onRequest) and routeLoader$ are not executed.

Reason:
When using window.history after MPA navigation, the browser retrieves the page from the disk cache and therefore doesn't go to the server to serve the page.
This happens when no cacheControl headers are set (in RequestHandlers or even vite.config), and when cacheControl is set with noCache or staleWhileRevalidate with maxAge or sMaxAge.
Expected behavior:
Having the browser serve a web page from the disk cache makes sense if it is a static page, but not so much if it is dynamic with SSR. This unreliable behavior and is quite hard to comprehend, especially when trying to set up authentication with redirects or different UI based on whether or not the user is logged in. Probably like many developers coming from a React background with client-side routing and authentication, I am not used to dealing with browsers and servers caching, so that doesn't make things easier. If all of this is normal behavior, we will have to improve documentation on caching to educate newcomers.
Current workarounds:

Set chacheControl in onRequest or onGet to noStore = true - This prevents the browser from caching pages to disk cache and therefore forces it to request the page from the server, but it prevents using other caching mechanisms (e.g. stale-while-revalidate), or at least doesn't make using other caching mechanisms easy.
Use SPA navigation when possible - This will work for  tags by converting them to  tags and for window.location.href by converting it to useNavigate(), but server-side redirects and manually changing URLs will still suffer from this issue.

Potential solutions:

Change cachedFetch in packages/qwik-city/runtime/src/service-worker/cached-fetch.ts to take into account history navigation
If this is expected behavior, improve documentation and create examples and tutorials on strategies to deal with browser caching.

Reproduction
https://github.com/maieulchevalier/qwik-cache-repro
Steps to reproduce
This repro showcases the difference between history navigation (back/forward) after  SPA and MPA navigation.
You can play with the app in prod at https://qwik-cache-repro.vercel.app/.

Clone repo
Install dependencies
Setup env vars for Auth.js or comment out the redirect in the onRequest handler in layout.tsx. I used Discord provider, you can set it up here: https://discord.com/developers/applications.
Run npm run preview (None of this happens in dev mode)

You will have to test the app with developer tools opened in network tab, and the terminal visible so that you can see what happens (the logs) when you navigate. Play with the buttons and see for yourself described behavior explained above. Pay attention when using going back after MPA navigation, you will see that the browser uses the disk cache, and that no logs from onRequest, onGet and routeLoader$ are printed out on your console.
One good way to understand the importance of this issue, is to sign in, then sign out, and then click on the back button. You will see the previous page, which should now be protected, still with the signout button.
System Info
System:
    OS: Linux 6.3 Fedora Linux 38 (Workstation Edition)
    CPU: (16) x64 13th Gen Intel(R) Core(TM) i5-1340P
    Memory: 21.06 GB / 31.05 GB
    Container: Yes
    Shell: 3.6.1 - /usr/bin/fish
  Binaries:
    Node: 18.16.1 - /usr/local/bin/node
    npm: 9.7.2 - /usr/local/bin/npm
    pnpm: 8.6.7 - ~/.local/share/pnpm/pnpm
  Browsers:
    Chrome: 114.0.5735.198
  npmPackages:
    @builder.io/qwik: ^1.2.6 => 1.2.6
    @builder.io/qwik-auth: ~0.1.0 => 0.1.0
    @builder.io/qwik-city: ^1.2.6 => 1.2.6
    undici: 5.22.1 => 5.22.1
    vite: 4.4.0 => 4.4.0

Additional Information
Tested only in chrome.

Thanks for your input. That helped me better understand the issue. In the first place, I was trying to set up authentication with cache-control headers set to staleWhileRevalidate and maxAge = 5 (those enabled by default in the starter app), which will keep sending the previously fetched page until 5 seconds have passed. Therefore with such a configuration, I had Signout buttons showing up even after signing out, and Signin buttons even after signing in. This was very odd to me as I didn't understand that caching was the problem, and this led me to try out different workarounds that ended up adding complexity to this issue.
So in the end it seems that the issue is more about finding a way to properly setup authentication and caching together. I find it pretty hard to do and saw someone else pretty lost by the behavior on Discord. I'll experiment a bit with it, so I think I will close for now and open another issue (feature request) or PR (documentation) that is scoped to authentication and caching later.

Thanks for your input. That helped me better understand the issue. In the first place, I was trying to set up authentication with cache-control headers set to staleWhileRevalidate and maxAge = 5 (those enabled by default in the starter app), which will keep sending the previously fetched page until 5 seconds have passed. Therefore with such a configuration, I had Signout buttons showing up even after signing out, and Signin buttons even after signing in. This was very odd to me as I didn't understand that caching was the problem, and this led me to try out different workarounds that ended up adding complexity to this issue.
So in the end it seems that the issue is more about finding a way to properly setup authentication and caching together. I find it pretty hard to do and saw someone else pretty lost by the behavior on Discord. I'll experiment a bit with it, so I think I will close for now and open another issue (feature request) or PR (documentation) that is scoped to authentication and caching later.


Export attribute don't work

Windows 10 with a fresh build with mono from today
Issue description:
[Export] attribute don't work... I can't made it appear in the editor. It used to work with oldest build.
I don't know if I am the only one.. :/ I had try to reboot godot , build the project with visual studio.
Project-GQ.zip

cc @neikeq, when issue was open the newest commit was 82ad05a20ef4420122b18eadf3835c4a8a49ba19

I rebuild the source again, and now it's working ! I don't know how but.. resolve now ! work fine !


installing npm install woor/discord.io#gateway_v6 --save and found the error

I have install git but does the directory affects it?

@Niellol your second screenshot makes it look like you've successfully installed git and put it in your $PATH (or %PATH% if that's still what window's calls it.)
Your new error looks more like your https request is being stopped before getting to github.com. (The only example I can think of that's not a messed up network config or attack is getting on some coffeeshop wifis requires you to click yes, and they're willing to redirect all HTTP(s) to themselves til you do.)
Can you reach https://github.com in a browser?
If so, perhaps you should try using the package.json that this repo uses, which is slightly different from the blog instructions you're following:
don't know if this actually works -- it could go to the same place, but I've not tested this npm syntax on this package:
npm install https://github.com/woor/discord.io/tarball/gateway_v6

But this does work as of today:
npm install github:woor/discord.io#gateway_v6

BEFORE you install the above, I recommend you delete node_modules and remove all references to discord.io from package.json dependencies. The below is exactly what your dependencies section should be after running the above:
    "dependencies": {
        "discord.io": "github:woor/discord.io#gateway_v6",
        "winston": "^3.0.0"
    }

Using the new syntax I got another bug though I can still download it by copy and paste it in the browser as you can see

@Niellol
Yes, it's because you're putting your project under program files. Program Files\Git should only be for the git binary, not anything else like git config or project files.
That windows directory has extra security that blocks apps from writing to it, and NPM is just another app.
Projects like this work better under something like c:\code\mydiscordbot


Feature: remove nested style objects

This PR adds a plugin for removing nested style definitions. For some background have a look at #634
Nested objects with a custom toString implementation are not removed.

Coverage increased (+0.06%) to 96.236% when pulling 06fbcf5bdf02d023c22b6a4173e9381551104953 on jfschwarz:feature-remove-objects into c7d33e413929f9f507cf181a6edf494438a14857 on FormidableLabs:master.

Looks great, thanks for your contribution!
May you please also update the docs: https://github.com/FormidableLabs/radium/tree/master/docs/api#configplugins

@ianobermiller, thanks, I did.

Coverage increased (+0.06%) to 96.236% when pulling 0b19ff31d0e42b1f88785ce8e2b3a4600e0612e7 on jfschwarz:feature-remove-objects into c7d33e413929f9f507cf181a6edf494438a14857 on FormidableLabs:master.

Have just come across this plugin and it resolves an issue we're having. Any progress on when it'll be fixed and merged? Cheers.


/bin/sh: 1: forge: not found

Description
/bin/sh: 1: forge: not found

Motivation
Adding the check still fails.
steps:
      - uses: actions/checkout@v3
        with:
          token: ${{ secrets.GH_TOKEN_CD_CONTRACTS }}
      - name : Install Foundry
        uses : foundry-rs/foundry-toolchain@v1
        with :
          version : nightly

      - name: Verify Foundry Installation
        run: forge --version

Can you share a run?

Optimistically marking as resolved, feel free to leave a comment @mrhouzlane if you are still experiencing issues around this


Ensure HTTP request outcome is 'success' before trying to read the response (read-attribute function) and add other functionality

Added an 'error check' in the read_attributes function, and also simplified a few other function's return call

I am not able to accept this PR, since both Good and Bad responses are covered by https://github.com/cenx-cf/wildfly-py/blob/master/wildfly/client.py#L42

Well, we can receive a 200 OK, but the JSON data doesn't have a "result" key since the command was invalid. This is what prompted me to submit this fix.

If we want to change from 2 to 4 space intents then we would need to change all modules in package. As both maestro-ng and docker-compose use 4 space indents, I think we should follow suite.

Lines of Function should not be longer than 20 lines though not in PEP8.

Formating issue has been addressed in https://github.com/cenx-cf/wildfly-py/pull/9.
Would you mind fix the conflicts or send another PR without your format fixes?

I reverted the commit that changes 2-spaces to 4.

@bkhouri Can you please turn off or change log level for some function in your PR?
2016-07-29 22:27:30,554 |    INFO | wildfly.client | line: 222 | Retrieving server name for host 'wildfly-apps1'.
2016-07-29 22:27:30,691 |    INFO | wildfly.client | line: 227 | Retrieved server name for wf host wildfly-apps1.  Response is {u'outcome': u'success', u'result': [{u'outcome': u'success', u'result': {}, u'address': [{u'host': u'wildfly-apps1'}, {u'server': u'wildfly-apps1-1'}]}]}
2016-07-29 22:27:31,036 |    INFO | wildfly.client | line: 260 | WildFly host wildfly-apps1 and server wildfly-apps1-1 has a server-group of A
2016-07-29 22:27:31,131 |    INFO | wildfly.client | line: 284 | WildFly host wildfly-apps1 and server wildfly-apps1-1 has a hostname of wildfly-apps1
2016-07-29 22:27:31,131 |    INFO | wildfly.api.host | line:  65 | WildFly host wildfly-apps1 and server wildfly-apps1-1 has a server group A and qualified_hostname of wildfly-apps1
2016-07-29 22:27:31,132 |    INFO | wildfly.api.host | line:  74 | The Hostname map is {u'wildfly-apps1': {u'wildfly-apps1-1': {u'A': u'wildfly-apps1'}}}

Some of those should probably be "debug" instead of "info".  I'll create a new PR for this.


coveralls: Add COVERALLS_GIT_BRANCH

This does pass the ref, but not just the branch name, the whole ref, i.e refs/head/master.
This is an short-term fix until we switch to the official action.
Refs #29457

I switched to the coveralls action. Works properly, but the build ID is not a number anymore. But a fixed thing is that coveralls now will again run for PRs.
We can remove the secret also from the repo settings.
I'll keep this open for a while, but we should switch to the official action as soon as the issues are fixed upstream.

I'm gonna split the action switch to a new PR

@mdo can you check why the merge button is disabled here?


Error when trying to run libvips for Jekyll-Picture-Tag

/github/workspace/vendor/bundle/ruby/2.7.0/gems/ffi-1.15.5/lib/ffi/library.rb:145:in `block in ffi_lib': Could not open library 'vips.so.42': vips.so.42: cannot open shared object file: No such file or directory. (LoadError)
Could not open library 'libvips.so.42': libvips.so.42: cannot open shared object file: No such file or directory

1_build_and_deploy.txt

1_build_and_deploy.txt

Solved by installing LibVips via Pre-build commands

seems that the repo owner need to reinstall jeykll picture tag and rebuild it against latest libvips.so

Hi @shinwookim
Have you settled down this issue?
Thanks & Regards

Same issue. Works on local but failing on github actions. I did what was said but it didn't work.

Hi @kKerem , could you share me your action YAML file? so that I can help you check what happened.

Hi @kKerem , could you share me your action YAML file? so that I can help you check what happened.

https://github.com/kKerem/kkerem.github.io/blob/main/.github/workflows/jekyll.yml
https://github.com/kKerem/kkerem.github.io/actions/runs/3855864257/jobs/6571392481

Are you actually using jekyll-deploy-action? can't see it in this .yml

Are you actually using jekyll-deploy-action? can't see it in this .yml

Agree with you.

I put the wrong yaml file my bad im quite new on this things. Its working now but im struggling with cache issue. My jekyll page still showing the first commit. Do I need to do something else? I couldn't figure it out.
updated yaml https://github.com/kKerem/kkerem.github.io/blob/main/.github/workflows/jekyll.yml
https://github.com/kKerem/kkerem.github.io/blob/gh-pages/index.html#L236
https://kkerem.github.io/


Add option to write diagnostics to a file to provide more information to tools

Bug/issue #, if applicable: rdar://105181169
Summary
This PR adds the option to write diagnostics to a file to have the ability to provide more diagnostic information to tools than what's available in the command line output format.
To request the diagnostics file output, tools can pass the new --diagnostics-file option.
To know what version of the docc executable supports the diagnostics file output, DocC now has a "features.json" file with the same format as Swift. This file is installed at usr/share/docc/features.json when running the "install" action in build-script-helper.py.
This PR also separates the formatting intended for tools and formatting intended for people in DiagnosticConsoleWriter. As part of this separation, behavior that was implicitly ties to this formatting is deprecated in favor of explicit formatting.
With the future possibility of making a common line output format for people that isn't limited by tool parsing, the goal is to always present diagnosis solutions in some form. To prepare for this, the --emit-fixits flag is renamed to --ide-console-output. (If you have feedback on that flag name, now is a good time.)
Dependencies
None
Testing
With any documentation project that produce some warnings (for example the test bundle at "Tests/SwiftDocCTests/Test Bundles/TestBundle.docc")

Build documentation passing the --emit-fixits flag:
swift run docc convert ./Tests/SwiftDocCTests/Test\ Bundles/TestBundle.docc --emit-fixits

The common line output should be formatted for tools to parse (including fixits)

Build documentation passing the --ide-console-output flag:
swift run docc convert ./Tests/SwiftDocCTests/Test\ Bundles/TestBundle.docc --ide-console-output

The common line output should be formatted for tools to parse (including fixits)

Build documentation passing the path to write a diagnostics file to:
swift run docc convert ./Tests/SwiftDocCTests/Test\ Bundles/TestBundle.docc --diagnostics-file ./test-diagnostics.json

The common line output should be formatted for tools to parse (including fixits)
The diagnostics file should list all the emitted diagnostics with information about their related solutions and notes.

Checklist
Make sure you check off the following items. If they cannot be completed, provide a reason.

[x] Added tests
[x] Ran the ./bin/test script and it succeeded
[x] Updated documentation if necessary

@swift-ci please test

@swift-ci please test

@swift-ci please test

I verified the features.json install location with https://github.com/apple/swift/pull/64038
$ find usr -name "features.json"
usr/share/clang/features.json
usr/share/swift/features.json
usr/share/docc/features.json


apply plugin alias supported?

Thank you for your interest in Gradle!
This issue lacks information and/or a reproducer to track down the problem. Unless you provide that information over the next 7 days, this issue will be closed.

apply {
  plugin(libs.plugins.spotless.get().getPluginId())
}


IdType can't be null

In the case we want a nullable IdType currently GraphQL is converting null in empty string (""). I think it's a bug.
In IdType.php the current code:
    public function serialize($value)
    {
        return (string)$value;
    }

The fix:
    public function serialize($value)
    {
        if (null === $value) {
            return null;
        }
        return (string)$value;
    }

Can someone confirm me it's a bug or if there are a reason for this ?
Thank you.

@seb2411, you're right, it's a bug.
We'll try to fix it soon.
Thank you for your interest.

Can I create a PR for this ?

Of course, it would be nice.

Done:
https://github.com/Youshido/GraphQL/pull/185

@seb2411 , thank you very much.
We'll collect more changes and then add new tag.


Hash API

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

73 of 97 (75.26%)  changed or added relevant lines in 3 files are covered.
18 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.007%) to 2.722%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

dataplane/server.go
17
21
80.95%

dataplane/saiserver/routing.go
55
75
73.33%

Files with Coverage Reduction
New Missed Lines
%

bgp/gobgp.go
2
47.46%

dataplane/server.go
16
62.6%

Totals

Change from base Build<PHONE_NUMBER>:
0.007%

Covered Lines:
17728

Relevant Lines:
651295

💛  - Coveralls


Extra Argument

I have been using this library for a while however I cannot for the life of me figure out how to pass an EXTRA argument. Any arguments I append to the end of the install command are dropped.
The Service Path Should be: C:\MyService.exe action:run arg1:MyArg
Please Help

Sorry, I am kind of swamped right now so I wasn't able to look into this. what I suggest is cloning the repo and giving it a go locally. It's fairly simple, if there's a big you should be able to spot it no probs. I myself never needed this functionality therefore I just added it "blindly" so it might not be working properly. It would be weird though cause there's quite a few people using it and I would be surprised if you were the first one to try this. But you never know. Worst case I'll give it a go in few days/weeks as time allows

I was able to get it working, it looks like there is a minor bug... there is some code that drops the 1st argument if the App is a standalone exe (opposed to .dll). I believe this was mistakenly dropping my extra argument. I was able to work around the issue by passing 2 extra arguments, the 1st is dropped and the 2nd makes it through. Not pretty but it works.

ah yeah, I remember that, the first argument normally is the path to the dll. Or at least was when I've written it. Hence I dropped it it wasn't necessary. Ok thanks for looking into it, I'll fix it when I get to it. Good to know that you can at least work for now with that hack.

Fixed by https://github.com/PeterKottas/DotNetCore.WindowsService/releases/tag/v2.0.7. Feel free to reopen if you find any issues with the current solution.

Hello, I'm using this versión of lib:

I launch this command to register the service:
"SePro TS OPCUASwitch Client Service.exe" "name:SeP..." action:install uno dos tres
The service has two parameters and "one" parameter is lost:

Thank you for this library :-)


File and Folder permissions

Ability to alter permissions and grant TAPIS roles to users on specific files and folders.

BLOCKER: Requires new functionality in TAPIS v3 to list all permissions assigned to a file object

BLOCKER: Requires new functionality in TAPIS v3 to list all permissions assigned to a file object

This is being implemented - support already exists in the security kernel in TAPIS v3 but the associated functionality must be implemented in Files service.

Defering until later


SQL server manager doesn't allow changes unless the database is dropped and recreated

I tried using the designer but the command required to drop and recreate the table

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

ID: 76507156-d85c-e9f0-a214-3a9f1eb0f1fc
Version Independent ID: 045c9c15-fbf9-abf9-c48a-904733e7ab42
Content: Change Column Order in a Table - SQL Server
Content Source: docs/relational-databases/tables/change-column-order-in-a-table.md
Product: sql
Technology: table-view-index
GitHub Login: @stevestein
Microsoft Alias: sstein

@lypolyzo -- Thanks for your feedback; we appreciate it. To make sure we have all the information needed to triage your issue, please provide more context around your general task.

Hello,
Thank you for reaching out to me!
I was trying to upload a video but the maximum size was 4MB so it didn’t got sent.
I did the following steps:
Select the table
Right click Design
Then in the Design tab I dragged up the column I wanted to change its order
I pressed CTRL+S to save the changes
I got an exception: Saving changes is not permitted. The changes you have made require the following tables to be dropped and re-created. You have either made changes to a table that can't be recreated or enabled the option Prevent saving changes that require the table to be re-created.
Thank you,
Lydia
From: William Anton Rohm<EMAIL_ADDRESS>Sent: Monday, December 16, 2019 10:17 PM
To: MicrosoftDocs/sql-docs<EMAIL_ADDRESS>Cc: Lydia Polyzou<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/sql-docs] SQL server manager doesn't allow changes unless the database is dropped and recreated (#3815)
Importance: High
@lypolyzohttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Flypolyzo&data=02|01|Lydia.Polyzou%40microsoft.com|0b7e71b92b324445b26408d7828ed446|72f988bf86f141af91ab2d7cd011db47|1|0|637121422272674456&sdata=0uAPhZALHRUs70fZf4%2FQM%2F9yqULRjEmmXRdVhiouKmo%3D&reserved=0 -- Thanks for your feedback; we appreciate it. To make sure we have all the information needed to triage your issue, please provide more context around your general task.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fsql-docs%2Fissues%2F3815%3Femail_source%3Dnotifications%26email_token%3DAJBHJZ6HQWLLYCEM75JEPATQZASBBA5CNFSM4J3KJAIKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHAZNVA%23issuecomment-566335188&data=02|01|Lydia.Polyzou%40microsoft.com|0b7e71b92b324445b26408d7828ed446|72f988bf86f141af91ab2d7cd011db47|1|0|637121422272674456&sdata=EqkHW3uGQYfAGJkNWuiad1YxucPkmiESA3zcd3SKgts%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAJBHJZZLXHVCKKMD6GOBCADQZASBBANCNFSM4J3KJAIA&data=02|01|Lydia.Polyzou%40microsoft.com|0b7e71b92b324445b26408d7828ed446|72f988bf86f141af91ab2d7cd011db47|1|0|637121422272674456&sdata=ahEDu6aFlyckmAHu4R97xTTvkvpCzzbByrs4YRsmCOU%3D&reserved=0.

@lypolyzo -- Lydia, thank you for clarifying.
@stevestein -- Steve, please look into this issue 3815.

@lypolyzo - thanks for the feedback!
Hi Lydia,
Try unchecking Prevent saving changes that require table re-creation in Tools>Options>Designers:

Thanks,
Steve

@lypolyzo it has been over 2 months - so, I am going to assume that Steve's answer on January 4 solved your issue. Closing. If I am incorrect, please re-open.
Cheers, Carl

@stevestein @carlrabeler I came here with the same issue and this solution worked like a charm so take it as a yes! Thanks!!

excellent!


compute similar subgraphs

The definition of similarity is hard. We can start by requiring identical structure and relations. Relations that extend outside the subgraph should be handled with care. "monitors" and "loadBalances" should have the same source resource. "runs" may have a different source node. "contains" must have equivalent source and target resources.

Eran
We should discuss whether similarity detection should be in open source or
a proprietary backend we develop as a product. I suggest deleting this
issue in github until we make that decision and get Jeromy's approval.
Vas
On Mar 30, 2015, at 7:23 PM, Eran Gabber<EMAIL_ADDRESS>wrote:
The definition of similarity is hard. We can start by requiring identical
structure and relations. Relations that extend outside the subgraph should
be handled with care. "monitors" and "loadBalances" should have the same
source resource. "runs" may have a different source node. "contains" must
have equivalent source and target resources.
—
Reply to this email directly or view it on GitHub
https://github.com/google/cluster-insight/issues/27.


NO notebook document for 'file://*.ipynb'

Type: Bug
Can't reliably reproduce. When I'm working in a Jupyter notebook, in the past few days, after executing 1-20 cells, I'm getting the error "NO notebook document for 'file://*.ipynb'" and then the "Go To" button at the top keeps on spinning, hitting Interrupt does nothing, and Restart is grayed out. My only recourse is to restart VS Code completely. It happens even after rebooting my machine, fully updating WSL (I'm connecting to the WSL remote), and ensuring VS Code and its extensions are fully updated. This is very disruptive; please help! Thanks!

Python Extension Version: 2023.18.0.
Platform: linux (x64).
Workspace folder ~/src/my_project, Home = /home/my_user/
21:00:09.563 [info] User belongs to experiment group 'NewJupyterSession'
21:00:14.898 [info] Start refreshing Kernel Picker<PHONE_NUMBER>898)
21:00:14.943 [info] Using Pylance
21:00:18.675 [info] Starting Kernel startUsingPythonInterpreter, .jvsc74a57bd07597a5efbd94c847325424dfc8686c4d158a7360d95467620d1c15956fe54889.~mambaforge/envs/phylo/python.~mambaforge/envs/phylo/python.-m#ipykernel_launcher  (Python Path: ~/mambaforge/envs/phylo/bin/python, Conda, phylo, 3.10.11) for '~/src/my_project/drafts.ipynb' (disableUI=true)
21:00:22.750 [info] End refreshing Kernel Picker<PHONE_NUMBER>898)
21:00:49.168 [info] Process Execution: ~/mambaforge/envs/phylo/bin/python -c "import ipykernel; print(ipykernel.__version__); print("5dc3a68c-e34e-4080-9c3e-2a532b2ccb4d"); print(ipykernel.__file__)"
21:00:49.320 [info] Process Execution: ~/mambaforge/envs/phylo/bin/python -m ipykernel_launcher --ip=<IP_ADDRESS> --stdin=9013 --control=9011 --hb=9010 --Session.signature_scheme="hmac-sha256" --Session.key=b"112f0e50-6c10-4c71-88b5-244853ce0ce3" --shell=9012 --transport="tcp" --iopub=9014 --f=~.local/share/jupyter/runtime/kernel-v2-2387175TuBKqu1eZg8b.json
    > cwd: ~/src/my_project
21:00:52.526 [info] ipykernel version & path 6.19.2, ~/mambaforge/envs/phylo/lib/python3.10/site-packages/ipykernel/__init__.py for ~/mambaforge/envs/phylo/bin/python
21:00:53.351 [warn] StdErr from Kernel Process ~mambaforge/envs/phylo/lib/python3.10/site-packages/traitlets/traitlets.py:2544: FutureWarning: Supporting extra quotes around strings is deprecated in traitlets 5.0. You can use 'hmac-sha256' instead of '"hmac-sha256"' if you require traitlets >=5.
  warn(
21:00:53.355 [warn] StdErr from Kernel Process ~mambaforge/envs/phylo/lib/python3.10/site-packages/traitlets/traitlets.py:2495: FutureWarning: Supporting extra quotes around Bytes is deprecated in traitlets 5.0. Use '112f0e50-6c10-4c71-88b5-244853ce0ce3' instead of 'b"112f0e50-6c10-4c71-88b5-244853ce0ce3"'.
  warn(
21:00:53.579 [info] Process Execution: ~/mambaforge/envs/phylo/bin/python -m pip list
21:00:54.284 [info] Process Execution: ~/mambaforge/envs/phylo/bin/python ~.vscode-server/extensions/ms-toolsai.jupyter-2023.9.1102792234-linux-x64/pythonFiles/printJupyterDataDir.py
21:00:57.185 [info] Handle Execution of Cells 0 for ~/src/my_project/drafts.ipynb
21:00:57.316 [info] Kernel acknowledged execution of cell 0 @<PHONE_NUMBER>314
21:01:08.327 [info] End cell 0 execution @<PHONE_NUMBER>326, started @<PHONE_NUMBER>314, elapsed time = 11.012s
...
21:04:47.310 [info] Handle Execution of Cells 55 for ~/src/my_project/drafts.ipynb
21:04:47.345 [info] Kernel acknowledged execution of cell 55 @<PHONE_NUMBER>344
21:04:56.233 [info] End cell 56 execution @<PHONE_NUMBER>233, started @<PHONE_NUMBER>344, elapsed time = 8.889s
21:05:02.892 [info] Dispose Kernel '~/src/my_project/drafts.ipynb' associated with '~/src/my_project/drafts.ipynb'
21:05:02.895 [info] Dispose Kernel process 2387391.
21:05:03.713 [error] Notebook not found for Cell ~src/my_project/drafts.ipynb

I'll note that I don't have to restart VSCode completely, but have to reload the window to relaunch my notebook.

Just faced this issue a few minutes ago. I realized that using the autoreload magic function is causing the issue for me. If I remove the magic function, it works fine. This is definitely not convenient but is a temporary workaround. No idea what the exact cause for this is.
Specifically, removing the following two lines of code helped:
%load_ext autoreload
%autoreload 2

Also hitting this frequently.

yep same here... similar setup to andrew

I'm encountering this issue in a GitHub codespace.

A similar issue here when running VS Code locally and connect to a workstation via VSCode remote. Resources should not be an issue in my case. (128GB RAM remote with enough disk space)
"NO notebook document for ..."
Local: Windows 11 Pro
Remote: Ubuntu 22.04

Same here.

Hitting this as well since a couple hours ago. Very difficult to repro - but its happening to me when I add a new cell that calls the pytorch conv2d method. Not sure if the logic in the cell is relevant to the crash or not, it's just what I was doing in a new cell when I hit this issue

Hi @msukkari @dummyindex @cmditch @JackElsey any workaround this you guys found? Please help.

Same here; have tried to use an older version of Jupyter plugin (released in Sept.) and the same bug happened.

Disabling pylance works.
This could be a possible reason : any of you guys have the huggingface code completion llm-vscode enabled?
I was getting a side pop-up saying that the free-teir service has ended, maybe it's interrupting pylance and crashing!
Not 100% sure.

Disabling pylance works. This could be a possible reason : any of you guys have the huggingface code completion llm-vscode enabled? I was getting a side pop-up saying that the free-teir service has ended, maybe it's interrupting pylance and crashing! Not 100% sure.

Yeah it seems to be a pylance issue; switch to an older version of pylance solve this for now.

Same here, just happened recently.

Same here, within the last several hours. Turning off the pylance seems to help.

Disabling pylance works. This could be a possible reason : any of you guys have the huggingface code completion llm-vscode enabled? I was getting a side pop-up saying that the free-teir service has ended, maybe it's interrupting pylance and crashing! Not 100% sure.

This works for now, thank you!

Same annoying issue here

Same issue starting today.

Same issues on WSL

same issue .....

Getting this since a few hours, wasn't an issue before. Turning off Pylance as workaround seems to work

same issue :(

Same here.

Same issue here, deactivating pylance seems to have done the trick.

Same here. How to downgrade pylance?

Go to Extensions > Pylance > Dropdown besides "Uninstall" > Install Another Version

Same here. How to downgrade pylance?

Go to Extensions > Pylance > Dropdown besides "Uninstall" > Install Another Version

Same issue here. Switched to pylance 2023.10.40 from 2023.10.50, hopefully this will fix it (will report back after a while).

Install Another Version

https://marketplace.visualstudio.com/items?itemName=ms-python.vscode-pylance
find 2023.10.40 download and put inside vscode
right click, install vsix extension

The above solution works for me. Thanks a lot to all!

Could someone please open an associated issue on the Pylance repo? https://github.com/microsoft/pylance-release
I couldn't find any similar issues reported (searching issues for "NO notebook document for"), and I think it might be worth linking that issue to this thread since so many people are having the issue.
I've got a deadline today so can't gather all the logs/info and wait for the error again to file a proper issue (https://github.com/microsoft/pylance-release/blob/main/TROUBLESHOOTING.md#filing-an-issue), but can do this next week if no-one else gets to it 👍

same issue

Same issue

Hi @msukkari @dummyindex @cmditch @JackElsey any workaround this you guys found? Please help.

As mentioned above, rolling back pylance to the previous release (2023.10.40) has fixed the issue.

Inside VSCODE extension; rollbacking pylance to the previous release (2023.10.40) has proven to be a workaround !

Same issue

Same issue

The same thing happened to me starting yesterday. I have to restart VScode; sometimes, I add .copy() after the variable will solve this problem. But I'm confused about why this happened.

Same thing happening to me

Same thing here, started today

Same issue here, since today

Me too

Same issue，i try to downgrade

Spend whole day restarting the kernel. Turns out there was a problem with the newly updated pylance. Rolling back to 2023.10.40 is effective~

Same issue！

Same error.

Same.
At first I didn't get that notification, so I waited forever for the added cell to start running.
Sometimes a reload window would fix it.

If only there was a button you could press to express that you're having the same issue...
Seriously, commenting "same" a million times helps nobody. It buries the comments trying to be helpful.

Same here! When I'm working in a Jupyter notebook, in the past few days, after executing 1-20 cells I'm getting the error "NO notebook document for 'file://*.ipynb'" and then the "Go To" button at the top keeps on spinning, hitting Interrupt does nothing, and Restart is grayed out. My only recourse is to restart VS Code completely, but the problem occured again. It's a real develop envirenment, so that's a wide problem?

Same issue here! I have restarted my jupyter many times today and it's annoying. And my pip list doesn't contain the 'pylance' module, so it should be another issue... What's wrong?

The solution to downgrade the VS code extension Pylance worked for me too.
As specified by tszslovewanpu:
Spend whole day restarting the kernel. Turns out there was a problem with the newly updated pylance. Rolling back to 2023.10.40 is effective~

Just don't use Notebooks. Everyday using ipynb and not pure py is a disaster...

:point_right:  Visual solution to how to workaround this issue:

Go to Extensions
Select Pylance
Dropdown on uninstall and select Switch to another version
Select v2023.10.40

:warning:  The solution has been already posted multiple times (thanks to contributors):
https://github.com/microsoft/vscode/issues/196740#issuecomment-1783747152,
https://github.com/microsoft/vscode/issues/196740#issuecomment-1783219049,
https://github.com/microsoft/vscode/issues/196740#issuecomment-1782913039,
https://github.com/microsoft/vscode/issues/196740#issuecomment-1783147505,
https://github.com/microsoft/vscode/issues/196740#issuecomment-1782800860,
https://github.com/microsoft/vscode/issues/196740#issuecomment-1782196400
:stop_sign:  So PLEASE stop saying same issue here (or similar)

This problem may be caused by the accumulated visualized outputs that you made.
Clear all outputs in your .ipynb!!

If anybody is having this issue, can you try the prerelease version of the Pylance extension: 2023.10.53. We think we've fixed the issue there (we were able to reproduce this problem with a codespace) and the issue no longer reproduces with 2023.10.53.
Thanks and sorry for the bug.

Confirm same symptoms and errors as well as disabling pylance fixes errors.

Confirm same symptoms and errors as well as disabling pylance fixes errors.

@hasush Can you try upgrading pylance to 2023.10.53?

@rchiodo I have updated to 2023.10.53 and I'm still getting this error.

@jgbos the output from the 'Python Language Server' output tab would help.

@rchiodo Doesn't seem to be anything useful in that:
2023-10-30 14:57:47.200 [info] [Info  - 2:57:47 PM] (1914568) Pylance language server 2023.10.53 (pyright d7012d0d) starting
2023-10-30 14:57:47.205 [info] [Info  - 2:57:47 PM] (1914568) Server root directory: /home/justin/.vscode-server/extensions/ms-python.vscode-pylance-2023.10.53/dist
2023-10-30 14:57:47.206 [info] [Info  - 2:57:47 PM] (1914568) Starting service instance "myenv"
2023-10-30 14:57:47.247 [info] [Info  - 2:57:47 PM] (1914568) Setting pythonPath for service "myenv": "/home/gridsan/JU17693/.conda/envs/othr/bin/python"
2023-10-30 14:57:47.247 [info] [Info  - 2:57:47 PM] (1914568) Setting environmentName for service "myenv": "3.11.5 (myenvconda)"
2023-10-30 14:57:47.289 [info] [Info  - 2:57:47 PM] (1914568) Assuming Python version 3.11
2023-10-30 14:57:47.638 [info] [Info  - 2:57:47 PM] (1914568) Found 80 source files

When I first load everything works as normal, after a few minutes this error pops up and I can no longer execute any notebooks.
I do see a Dispose Kernel message in the Jupyter output.

When we repro'd the problem locally we saw a number of debug assertions in the Pylance log. That was a known bug in 2023.10.50 and may not have had anything to do with the root cause of this problem.

@rchiodo , Thanks for the fast bug fix! I updated to the latest pylance version (2023.10.53). So far, it seems to have resolved the problem. I've only been coding for about 1 hour, though. I put an updated of the "No file" problem comes back

@jgbos when you reproduce this issue again, can you please open Dev Tools (F1 -> Toggle Developer Tools) and share the logs from the Dev Tools with us?

@jgbos try removing pylance altogether instead of downgrading or downgrade to even older version, and see if you still get the issue. Make sure you reload vscode for the changes to make effect every time you install/uninstall/downgrade pylance.

Can confirm 2023.10.53 fixes the issue, at least up to now.

Switching to the pre-release version didn't fix the issue for me. Removing Pylance worked.

Same issue. Hate this. please fix.

@rchiodo,  If possible, I'd recommend switching pylance, v2023.10.53  from "Pre-Release" to "Release". You'd be helping out a lot of people.

If anybody is having this issue, can you try the prerelease version of the Pylance extension: 2023.10.53. We think we've fixed the issue there (we were able to reproduce this problem with a codespace) and the issue no longer reproduces with 2023.10.53.
Thanks and sorry for the bug.

It was fine in the morning when I changed it to 2023.10.53, but now the same error has reappeared.

Switched to pylance 2023.10.40 in vscode, it work for me

I have the same problem, but I have not pylance installed.

Switched to pylance 2023.10.40 in vscode, it work for me

This also seems works for me.

@ilgaribaldy

@jgbos try removing pylance altogether instead of downgrading or downgrade to even older version, and see if you still get the issue. Make sure you reload vscode for the changes to make effect every time you install/uninstall/downgrade pylance.

It looks like reverting to an older version has fixed the problem.

I have reverted to an older version of PyLance, and it did fix the problem. Thanks to @hjerpe and @Matesanz

I started to had the same problem today and just switched to PyLance 2023.10.40 and it solved the issue. Thanks!

I have the same issue. I tried to switch to pylance 2023.10.40 and it is still there. For me the issue is triggered by copy pasting content within and between cells.

I think the problem is related to URI conversions. I can't reproduce the message about the 'No notebook document' but I can get the kernel to stop running.
Reproduction steps:

Open VS code from WSL
Create notebook
Save to disk
Def a function in a cell
Call function from another cell
Run all the cells
Goto def for the function - new notebook should open that looks like the same tab
Run cells in the other notebook
Close the other notebook
Go back to running cells in the original tab
Cells don't run. You can then see this in the 'Jupyter' output tab:

19:35:14.592 [error] Notebook not found for Cell ~/test/test_pyright/test.ipynb
I believe this is caused by recent changes in Pylance to support virtual workspaces. We're testing a fix at the moment.

Same issue here. Looking forward to the fix going forward rather than simply downgrading the Pylance extension

To the ones who say they still have the issue in 2023.10.40: Check and make sure you are in the environment in which you downgraded. In my case, for example, I re-encountered the issue while being in another instance (Docker dev environment). First I thought the issue now also reappeared in 2023.10.40. Then however realized that I am in another environment and need to downgrade there as well. I can imagine this circumstance could also happen using different profiles.

Same issue here with WSL and VS Code - happening to be multiple times a day at the moment.

A similar issue here when running VS Code locally and connect to a workstation via VSCode remote. Resources should not be an issue in my case. (128GB RAM remote with sufficient disk space) "NO notebook document for ..."
Local: Windows 11 Pro Remote: Ubuntu 22.04 Start date: 10/26 EST, not sure if it is due to updates
Update: switching pylance version works for me. Extension -> pylance -> uninstall drop-down -> switch version (in my case pylance v2023.9.30). Thanks to @charchit7 for the solution below.

Same problem. It works for me.

I am working on a server via Remote-SSH.

Although there are several reports of people fixing this by rolling to 2023.10.40. I remember having this issue before that was released.

Downgrading to v2023.10.40 works for me. I'm working on a server via Remote-SSH.

Hope there's a fix soon, I'm having to close and restart VS Code a couple of dozen times a day at the moment because of this issue.

Same issue in Win11 and WSL Debian, reinstalling older version of pylance==v2023.10.30 has fixed the issue.

It works for me when I disable Pylance for the workspace.

Also facing this issue working on a remote server via Remote-SSH. Disabling pylance and restarting VSCode immediately fixes the issue (didn't try downgrading pylance 🤷)

@nVentis Thanks!

I encounter the same issue when working on SSH. It's quite annoying that after disabling Pylance, I can't navigate to functions.

This should be fixed in the latest release for Pylance that went out last night.

With 2023.11.11, I encountered the following errors. I am not sure this is related or not.
Error: Debug Failure. Cell path not found for cell vscode-notebook-cell://ssh-remote%XXX/sim_gen.ipynb#X66sdnNjb2RlLXJlbW90ZQ%3D%3D
    at _0x5e8922.getNotebookCellPath (/XXX/.vscode-server/extensions/ms-python.vscode-pylance-2023.11.11/dist/server.bundle.js:1:261668)
    at _0x8f195a.decodeTextDocumentUri (/XXX/.vscode-server/extensions/ms-python.vscode-pylance-2023.11.11/dist/server.bundle.js:1:230980)
    at _0x45a7e7.onDidCloseTextDocument (/XXX/.vscode-server/extensions/ms-python.vscode-pylance-2023.11.11/dist/server.bundle.js:1:901599)
    at /XXX/.vscode-server/extensions/ms-python.vscode-pylance-2023.11.11/dist/pyright.bundle.js:1:1144202
    at /XXX/.vscode-server/extensions/ms-python.vscode-pylance-2023.11.11/dist/vendor.bundle.js:2:1234062
    at oe (/XXX/.vscode-server/extensions/ms-python.vscode-pylance-2023.11.11/dist/vendor.bundle.js:2:1234284)
    at /XXX/.vscode-server/extensions/ms-python.vscode-pylance-2023.11.11/dist/vendor.bundle.js:2:1230224
    at Immediate.<anonymous> (/XXX/.vscode-server/extensions/ms-python.vscode-pylance-2023.11.11/dist/vendor.bundle.js:2:1230244)
    at processImmediate (node:internal/timers:476:21)

2023-11-03 17:01:28.024 [info] [Error - 5:01:28 PM] Server process exited with code 1.
2023-11-03 17:01:28.026 [info] [Info  - 5:01:28 PM] Connection to server got closed. Server will restart.
2023-11-03 17:01:28.026 [info] true
2023-11-03 17:01:28.499 [info] [Info  - 5:01:28 PM] (9864) Pylance language server 2023.11.11 (pyright 64c9c3ff) starting
2023-11-03 17:01:28.499 [info] [Info  - 5:01:28 PM] (9864) Server root directory: /XXX/.vscode-server/extensions/ms-python.vscode-pylance-2023.11.11/dist
2023-11-03 17:01:28.506 [info] [Error - 5:01:28 PM] Server initialization failed.
2023-11-03 17:01:28.506 [info]   Message: Request initialize failed with message: You may install and use any number of copies of the software only with Microsoft Visual Studio, Visual Studio for Mac, Visual Studio Code, Azure DevOps, Team Foundation Server, and successor Microsoft products and services (collectively, the “Visual Studio Products and Services”) to develop and test your applications. The software is licensed, not sold. This agreement only gives you some rights to use the software. Microsoft reserves all other rights. You may not: work around any technical limitations in the software that only allow you to use it in certain ways; reverse engineer, decompile or disassemble the software, or otherwise attempt to derive the source code for the software, except and to the extent required by third party licensing terms governing use of certain open source components that may be included in the software; remove, minimize, block, or modify any notices of Microsoft or its suppliers in the software; use the software in any way that is against the law or to create or propagate malware; or share, publish, distribute, or lease the software (except for any distributable code, subject to the terms above), provide the software as a stand-alone offering for others to use, or transfer the software or this agreement to any third party.

----- [2809a1f5f679fe8602c339647a7242b44b9ec6790ed196d53b7e0d47ccd7cb23]

  Code: -32603

Thanks for the feedback. That should be a dupe of this error:
https://github.com/microsoft/pylance-release/issues/5071


[iOS] Unable to import Wallet

With your latest iOS app I am unable to import a Wallet under the File/Text tab. When long-pressing and selecting the paste option, nothing happens.
I have copied the contents of my private Wallet (64kB large) in another app and fail to paste here.
Known bug?

Hey binarykitchen,
The Bitcoin.com Wallet has changed significantly since you created this issue, we are currently on V4.8.0 - If you can test this again for me I would really appreciate it.
If this is still an issue please do reach out,
Regards,
Ornn.

nope, still can't paste plain text code to import wallet. upon paste nothing happens, no error, no text, just nothing.

Reporting this to the development team binarykitchen, if I need further information I'll reach out.


Does the library manage instances?

Hi, for our use case (having an encrypted storage per user), we are looking into this library.
We want to be able to access the instance from anywhere in our code.
We are wondering if we need to manage this instance ourself? (e.g. singleton pattern)
What will happen if we create a new instance with an existing id? For example:
const instance = new MMKV({ id: 'user-storage' }); // a storage with this id already exists, will it open or override it?

Does the database get overwritten, or does it open the existing database?
In other words I guess - does the library manage the instances on the native side or do we have to do that ourselves?

After testing this I have found that the database does not get overwritten. Closing this.


Host Header service require between pod

Kuberntes: v1.13.2
Istio: 1.0.5
Hi,
I have a simple configuration with an Nginx  who proxy_pass to a service like this:
      upstream oauth {
        server oauth;

        keepalive 2;
      }

        location /oauth/token {
          proxy_set_header Host $host;
          proxy_pass http://oauth/oauth/token;
}

Without an ISTIO running, the service work great.
Here my problem is when I push istio with sidecar, the service returns a 404 Not Found.
I know this is a known bug and if I set the  proxy_set_header Host with the service name oauth it worked.
The problem is in my workflow, I need to have the default header Host for some verification.
I have tried to follow the solution found on https://github.com/istio/istio/issues/9107 but without success.
I have set the nginx.ingress.kubernetes.io/service-upstream: "true" on my ingress:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    kubernetes.io/ingress.allow-http: "false"
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/client-max-body-size: 5m
    nginx.ingress.kubernetes.io/proxy-body-size: 5m
    nginx.ingress.kubernetes.io/service-upstream: "true"
  name: dev-gateway
  namespace: istio-system
spec:
  rules:
  - host: graphql-istio.kube.test.gg
    http:
      paths:
      - backend:
          serviceName: istio-ingressgateway
          servicePort: 80
  tls:
  - hosts:
    - graphql-istio.kube.test.gg
    secretName: wildcard-kube-test-gg-tls
status:
  loadBalancer:
    ingress:
    - {}

Add the host into my virtualservices:
apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: oauth
  namespace: test
spec:
  hosts:
  - oauth
  - graphql-istio.kube.test.gg
  http:
  - route:
    - destination:
        host: oauth
        subset: v1

apiVersion: networking.istio.io/v1alpha3
kind: VirtualService
metadata:
  name: gateway
  namespace: test
  hosts:
  - gateway
  - graphql-istio.kube.test.gg
  http:
  - route:
    - destination:
        host: gateway
        subset: v1

My istio gateway:
apiVersion: v1
items:
- apiVersion: networking.istio.io/v1alpha3
  kind: Gateway
  metadata:
    name: test-gateway
    namespace: test
  spec:
    selector:
      istio: ingressgateway
    servers:
    - hosts:
      - graphql-istio.kube.test.gg
      port:
        name: http
        number: 80
        protocol: HTTP
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

But with this config I still have a 404.
Does it exists a configuration where the Host header can be bypass easily?
Am I missing something?
Thanks for your help.

Hi,
I'm guessing you're using the oauth-proxy image.
Unfortunately I found it to be very inflexible, especially when it comes to getting oauth-proxy, istio and ingress-nginx to work in harmony.
In the ended, I ended up writing my own version of oauth-proxy (it's pretty simple really) to resolve the problem because as you say, istio/envoy do need the correct outbound headers.
Karl

@Stono So I imagine there is no solution today to passthrough Host headers easily via istio/envoy? :crying_cat_face:
I have two services pods with my nginx-gateway in front used to proxy-pass the traffic so to modify my VirtualService to have host entries for the external addresses does not work well when 2 services are involved and I need to have the external header host.
Is it not possible to modify Envoy configuration to set the ScopeKeyBuilder config who would only need to deal with a 'virtual-host' header? (https://github.com/envoyproxy/envoy/issues/4690)
I don't know if it is reliable in this use-case. :thinking:

Was there ever a solution to this problem?


Add testing documentation for package tests

AWS_REGION=localstack AWS_ACCESS_KEY_ID=999999 AWS_SECRET_KEY=1231

This needs to be included when running package tests.

Fixed in #332


failed to encode args[2]: unable to encode &geom.Point{geom0:geom.geom0{layout:1, stride:2, flatCoords:[]float64{38.8951, 77.0364}, srid:0}} into text format for unknown type (OID 17977): cannot find encode plan

Version
1.26.0
What happened?
I am trying to simply store geometry data using postgis.
The insert currently does not work. I have tried following https://docs.sqlc.dev/en/stable/reference/datatypes.html#using-github-com-twpayne-go-geom but currently failing to insert into my DB.
Relevant log output
failed to encode args[2]: unable to encode &geom.Point{geom0:geom.geom0{layout:1, stride:2, flatCoords:[]float64{38.8951, 77.0364}, srid:0}} into text format for unknown type (OID 17977): cannot find encode plan

Database schema
BEGIN;

CREATE EXTENSION IF NOT EXISTS "postgis";

-- Create tables
CREATE TABLE "observation" (
    "id" BIGINT GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
    "uid" UUID DEFAULT uuid_generate_v4(),
    "user_id" BIGINT NOT NULL,
    "location" GEOMETRY(POINT, 4326) NOT NULL,
    "created_at" TIMESTAMPTZ NOT NULL DEFAULT (CURRENT_TIMESTAMP),
    "facility_name" VARCHAR(255) NOT NULL
);

-- Add foreign keys
ALTER TABLE "observation" ADD CONSTRAINT "observation_user_id_fkey" FOREIGN KEY ("user_id") REFERENCES "user" ("id");

-- Add indexes
CREATE UNIQUE INDEX "observation_uid_idx" ON "observation" USING BTREE ("uid");
CREATE INDEX "observation_user_id_idx" ON "observation" USING BTREE ("user_id");

COMMIT;

// Code generated by sqlc. DO NOT EDIT.
// versions:
//   sqlc v1.26.0
// source: observation.sql

package pgsqlc

import (
	"context"

	go_geom "github.com/twpayne/go-geom"
)

const createObservation = `-- name: CreateObservation :exec
INSERT INTO "observation" (
    "user_id",
    "facility_name",
    "location"
    )
VALUES (
    $1,
    $2,
    $3
    )
`

type CreateObservationParams struct {
	UserID       int64
	FacilityName string
	Location     *go_geom.Point
}

func (q *Queries) CreateObservation(ctx context.Context, arg CreateObservationParams) error {
	_, err := q.db.Exec(ctx, createObservation, arg.UserID, arg.FacilityName, arg.Location)
	return err
}

const getObservationByID = `-- name: GetObservationByID :one
SELECT id, uid, user_id, location, created_at, facility_name FROM "observation"
WHERE "id" = $1 LIMIT 1
`

func (q *Queries) GetObservationByID(ctx context.Context, id int64) (Observation, error) {
	row := q.db.QueryRow(ctx, getObservationByID, id)
	var i Observation
	err := row.Scan(
		&i.ID,
		&i.UID,
		&i.UserID,
		&i.Location,
		&i.CreatedAt,
		&i.FacilityName,
	)
	return i, err
}

const getObservationsByUserID = `-- name: GetObservationsByUserID :many
SELECT id, uid, user_id, location, created_at, facility_name FROM "observation"
WHERE "user_id" = $1
`

func (q *Queries) GetObservationsByUserID(ctx context.Context, userID int64) ([]Observation, error) {
	rows, err := q.db.Query(ctx, getObservationsByUserID, userID)
	if err != nil {
		return nil, err
	}
	defer rows.Close()
	items := []Observation{}
	for rows.Next() {
		var i Observation
		if err := rows.Scan(
			&i.ID,
			&i.UID,
			&i.UserID,
			&i.Location,
			&i.CreatedAt,
			&i.FacilityName,
		); err != nil {
			return nil, err
		}
		items = append(items, i)
	}
	if err := rows.Err(); err != nil {
		return nil, err
	}
	return items, nil
}

SQL queries
-- name: CreateObservation :exec
INSERT INTO "observation" (
    "user_id",
    "facility_name",
    "location"
    )
VALUES (
    $1,
    $2,
    $3
    );

-- name: GetObservationByID :one
SELECT * FROM "observation"
WHERE "id" = $1 LIMIT 1;

-- name: GetObservationsByUserID :many
SELECT * FROM "observation"
WHERE "user_id" = $1;

Configuration
version: "2"
sql:
  - schema: "db/postgres/migration"
    queries: "db/postgres/query"
    engine: "postgresql"
    gen:
      go:
        package: "pgsqlc"
        out: "internal/infrastructure/persistence/pgsqlc"
        sql_package: "pgx/v5"
        emit_json_tags: false
        emit_interface: true
        emit_empty_slices: true
        rename:
          uid: "UID"
          client_ip: "ClientIP"
        overrides:
          - db_type: "timestamptz"
            go_type: "time.Time"
          - db_type: "timestamptz"
            go_type: "time.Time"
            nullable: true
          - db_type: "uuid"
            go_type: "github.com/google/uuid.UUID"
          - db_type: "uuid"
            go_type: "github.com/google/uuid.UUID"
            nullable: true
          - db_type: "geometry"
            go_type:
              import: "github.com/twpayne/go-geom"
              pointer: true
              type: "Point"
          - db_type: "geometry"
            go_type:
              import: "github.com/twpayne/go-geom"
              pointer: true
              type: "Point"
            nullable: true

Playground URL
No response
What operating system are you using?
macOS
What database engines are you using?
PostgreSQL
What type of code are you generating?
Go

To make this simpler, I have followed this playground: https://play.sqlc.dev/p/f19156612c3d4875ee51893bd8204c484be6818a0162cb9f40f02f80a43fc157
So I am overriding like so:
- db_type: "geometry"
- go_type: "github.com/cridenour/go-postgis.Point"

The table is created like so:
CREATE TABLE "observation" (
    "id" BIGINT GENERATED ALWAYS AS IDENTITY PRIMARY KEY,
    "uid" UUID DEFAULT uuid_generate_v4(),
    "user_id" BIGINT NOT NULL,
    "location" geometry(Point, 4326) NOT NULL,
    "created_at" TIMESTAMPTZ NOT NULL DEFAULT (CURRENT_TIMESTAMP),
    "facility_name" VARCHAR(255) NOT NULL
);

Then, my generated model looks like so:
type Observation struct {
	ID           int64         `json:"id"`
	UID          uuid.UUID     `json:"uid"`
	UserID       int64         `json:"user_id"`
	Location     postgis.Point `json:"location"`
	CreatedAt    time.Time     `json:"created_at"`
	FacilityName string        `json:"facility_name"`
}

The INSERT SQL is:
-- name: CreateObservation :one
INSERT INTO observation (
    user_id,
    facility_name,
    location
    )
VALUES (
    $1,
    $2,
    $3
)
RETURNING *;

And I attempt to insert like so:
func (u *ObservationManagementService) CreateObservation(ctx context.Context, newObservation ports.NewObservation) (pgsqlc.Observation, error) {
	args := pgsqlc.CreateObservationParams{
		UserID:       newObservation.UserID,
		FacilityName: newObservation.FacilityName,
		Location: postgis.Point{
			X: newObservation.Long,
			Y: newObservation.Lat,
		},
	}

	o, err := u.store.CreateObservation(ctx, args)

	return o, err
}

I am getting this error when trying to insert:
ERROR: parse error - invalid geometry (SQLSTATE XX000)

Not sure it is directly relevant but this issue popped up for me when I ran into a similar issue. The problem I had was that PGX had no idea about my custom type when I was using a postgres array.
To solve this, I added an AfterConnect function to my config which told PGX about my custom type. An example of how to set this up is on the PGX issue board - https://github.com/jackc/pgx/issues/1601#issuecomment-1591237100
I am not sure if this should be fixed in SQLC. Maybe you are already doing this, but not adding the array version, I haven't dug deep into your code.


Pose graph format generated from service dump

Dear @koide3,
I would like to clarify if the pose graph generated (graph.g2o) from the rosservice /hdl_graph_slam/dump is the optimized pose graph after loop closure.
If so, may i know what format is each line of the output in? Following is a snippet:
VERTEX_SE3:QUAT 3 -0.421949 0.820959 0.00217435 -0.0177581 -0.00476316 0.906195 0.422459  VERTEX_SE3:QUAT 4 -1.24384 1.42655 0.0073593 -0.015512 0.00142036 0.988524 0.150256  VERTEX_SE3:QUAT 5 -2.27197 1.49608 0.00940595 -0.0131559 0.00596053 0.999626 0.0232131
I would like to compare this optimized trajectory with another trajectory in TUM format:
timestamp tx ty tz qx qy qz qw using the EVO repo.
Any help would be appreciated. Thank you in advance.

Hi @nyangshawbin ,
One line about an SE3 vertex indicates vertex_type vertex_id x y z qx qy qz qw. You can see this page and this for the detail of g2o's graph format.

Appreciate for the help, thanks!

@nyangshawbin
Hey, what approach you used to accomplish this? how you implemented the timestamp data?
I'm also trying to do comparison between multiple estimations and ground truth using EVO repo.
Really appriciate any help
Regards,

------------hdl_graph_slam_nodelet.cpp----------------
bool save_traj_service(hdl_graph_slam::SaveTrajRequest& req, hdl_graph_slam::SaveTrajResponse& res) {
std::vectorKeyFrameSnapshot::Ptr snapshot;
keyframes_snapshot_mutex.lock();
snapshot = keyframes_snapshot;
keyframes_snapshot_mutex.unlock();
outFile2.open(req.destination, std::ios::out | std::ios::trunc);
for(KeyFrameSnapshot::Ptr kf : snapshot){
// cloud->header.stamp = snapshot.back()->cloud->header.stamp;
double pose_stamp = kf->cloud->header.stamp/1000000;
Eigen::Matrix4f apose = kf->pose.matrix().cast();
float tx = apose(0,3);
float ty = apose(1,3);
float tz = apose(2,3);
Eigen::Quaternionf pose_quat(apose.block<3,3>(0,0));
float qw = pose_quat.w();
float qx = pose_quat.x();
float qy = pose_quat.y();
float qz = pose_quat.z();
outFile2<<pose_stamp<<","
<<tx<<","<<ty<<","<<tz<<","
<<qx<<","<<qy<<","<<qz<<","<<qw;
outFile2<<std::endl;
}
res.success = true;
return true;
}
add above code to hdl_graph_slam_nodelet.cpp, check and modify the code related to srv.Call this service, you can get a trajectory for evo repo.

Is it possible to get more detailed instructions on this?
i tried implementing the code but i recieved erros messages regarding it. my c++ skills are not up to date unfortunately


Publish a crate?

I couldn't find a published crate for shame, but maybe it's under an unexpected name? Or is there some other plan for distribution or this just hasn't been done yet?

thx for asking,
it's not on crates.io so far. For now you'd have to write
shame = { git = "https://github.com/RayMarch/shame.git", tag = "v1.0.1" }

into your Cargo.toml,
I haven't had the time yet to read up on crates.io publishing and also getting the docs on docs.rs.

Publishing to crates-io is pretty easy in my experience. docs: https://doc.rust-lang.org/cargo/commands/cargo-publish.html
Once published, docs will get built automatically and posted on docs.rs.
You may have already seen this, but if you want some expert guidance on writing rust apis check out the excellent rust api guidelines.
Couple more things you might want to consider before publishing

Rust crates use semantic versioning. Once you publish a version "1.0.0" users will expect the api not to change in any backwards-incompatible way except when updating to version "2.*.*". Since this crate is new, I suggest starting at "0.1.0" and only publishing "1.0.0" when you are sure the api is stable. Some crates take years to reach "1.0.0". There's no rush :)
Rust comes with standard code formatter called rustfmt. Rustfmt will make it easier for others to read an contribute to your project. To use it, run cargo fmt at the root of the repository. It's a high quality formatter; it won't break any of your code. The easiest time to start using rustfmt is when a project is new.
Did you know cargo can review your code for you? Try running cargo clippy. It gives very good advice.

By the way, This library looks super cool. I've been wanting something like this for a while. I look forward to trying it out.

Thank you for the recommendations, i have actually not seen those api recommendations yet!
I really should have run rustfmt before publishing, thats my bad.
Do you recommend turning the version number back to below 1.0.0? I heard online that theres a certain "1.0.0 shyness" in the community.
I am also unsure about how to handle the git version tag. Should all the crates in the repository always match the git tag, or should the all crates each have different version numbers and be bumped separately based on the changes?
Thx for taking interest in the library. Make sure to post your experiences/suggestions in the community discord, i'd love to hear them.

Do you recommend turning the version number back to below 1.0.0? I heard online that theres a certain "1.0.0 shyness" in the community.

I can see why someone might say that. Lot's of widely-used pre "1.0.0" crates out in the ecosystem. Maybe it's not such a bad thing though; it shows that those crate authors are serious about semver compliance. I do recommend changing the version number for shame to something below "1.0.0". The way I see it, your options with respect to versioning are:

make "1.0._" your initial release, bump the major version whenever making a breaking changes

there is a way to do preleases on crates.io but I don't know the specifics

make "1.0._" your initial release, don't respect semver. (users won't like this)
make "0.1.0" your initial release, this will allow you to iterate and make breaking changes before posting a version "1.*.*"

I am of course assuming you'll want to be able to make breaking changes. It would be pretty impressive if you designed the api perfectly first try :)

I am also unsure about how to handle the git version tag. Should all the crates in the repository always match the git tag, or should the all crates each have different version numbers and be bumped separately based on the changes?

Not sure if there is a standard way of doing this. I usually keep all crates in the workspace at the same version and tag that version in git. Makes it easy to reason about. (fyi there is tool that can set the versions of all crates in the workspace cargo set-version --workspace '0.1.0')

oh don't worry,  i do appreciate the guidance!
The reason theres not much visible progress right now is because i'm trying to implement for loops and break/continue statements, which touch a bunch of code. After that is merged i'll run rustfmt and think more about the semver situation.
The whole shame_graph crate is kind of like an internal api that shame uses and wraps static rust typing around.
During development it became clear that shame_graph is pretty much necessary to enable users to properly write generic shame code, because otherwise the trait bound overhead gets out of hand (see bounds like CanBeMultiplied).
So on the one hand i want shame_graph to be a quickly iterable internal api, on the other hand its really nice for users to have access to it in the odd case where they need it.
This makes me not quite sure how to deal with the semver of shame_graph.


Ok branch

We could do that... but I will have to refactor my repo too
On Thu, Jun 9, 2022 at 4:32 PM Yuanqing Wang @.***>
wrote:

Hi @okara83 https://github.com/okara83 , thanks for this!
since this material is huge, do you think it would make more sense if we
simply provide a link to your own repository rather than copy everything
here? this repo is for the purpose of rendering the website and the these
files wouldn't render
—
Reply to this email directly, view it on GitHub
https://github.com/yuanqing-wang/scotch/pull/3#issuecomment-1151591456,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAU7T2IXFOZAPGY3C2P4EILVOJIGTANCNFSM5YLJH5GQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Solid Pauschism ~ It doesn't matter how well you polish the underside of
the banister.


Object placed in wrong folder

Archi 4.6.0 Build<PHONE_NUMBER>42 on Windows 10
Expected Behaviour
Imported objects in one folder (from BiZZdesign) all end up in one folder in Archi
Actual Behaviour
Imported objects with child objects end up in the parent folder. The child objects end up in an unnamed subfolder. See the screenshots for better understanding.
Steps to Reproduce the Behaviour

Create an export file with BiZZdesign ES

in BiZZdesign you can create a hierarchi of objects. Not with folders, but by dragging an object in the model tree 'over' another object.
in the model tree the object is now a child of the other object. See the business functions in the screenshot

Import the BiZZdesign export with Archi

Objects without child-objects are all placed in their respective folders
Objects with child-objects are placed in their parent folder.
The child-objects are placed in an unnamed subfolder. See the screenshot

The BiZZdesing Archimate export XML file
objects and folders hierarchi.zip
Suggested behavior
As Archi doesn't support parent-child objects in the model tree, I think it's best to ignore this. My suggested sollution is to place parent and child objects all in the same folder.
The current behavior is to place the child-objects in an unnamed folders. When there are many parent-child objects in one folder, this results in many unnamed subfolders. Hard to find the right subfolder ..

The import algorithm could probably do with some refining in cases like this. I don't have time to do this before Archi 4.6 final release.
For reference, this is the code https://github.com/archimatetool/archi/blob/c1615b72e9e112ce5756c54e29909251b8d8fcad/org.opengroup.archimate.xmlexchange/src/org/opengroup/archimate/xmlexchange/XMLModelImporter.java#L373

Ok, thanks for looking into this so quick.

It's an awkward use case. I think the algorithm determines the parent item to be a folder because it has a child item and ignores the id-reference to the element. The algorithm needs to catch this case.


Lyrics don't show up when listening along with someone

🧐 Have you read the FAQ and viewed similar issues?

[ ] I have read the FAQ
[X] I have checked older issues, open and closed
[X] I did a clean install of SpotX as described in the FAQ

Сountry of your account
USA
What is your Spotify Plan?
Premium
Do you have Spicetify installed?
No
ℹ Computer information
- Spotify: <IP_ADDRESS>2.g01893f92
- Windows: 10 22H2 1904X.5131
- PowerShell: 5.1.19041.5129

📝 Description

lyrics doesn't show up when listening along on discord however it works fine in old theme

hope it get fixed any next updates cause i like new theme
📸 Screenshots

here while listening with someone
(can't press on  now playing view)

here if i listen to song by myself i can click on it

I'm sure this problem is not related to spotx
check the problem in the native client

i tried to add -old_lyrics parameter and it works fine with new theme


Correction for raw affiliation Department of Cyber Security School of Engineering and Computing, De Montfort University, Dubai, United Arab Emirates

Correction needed for raw affiliation Department of Cyber Security School of Engineering and Computing, De Montfort University, Dubai, United Arab Emirates
raw_affiliation_name: Department of Cyber Security School of Engineering and Computing, De Montfort University, Dubai, United Arab Emirates
new_rors: 0312pnr83
previous_rors:
works_examples: W4283593304
contact: a5ab0da5dfd10c964eb28163847f8382:1a0195 @ dmu.ac.uk

This issue was accepted and ingested by the OpenAlex team on 2024-12-19. The new affiliations should be visible within the next 7 days.


Table of contents of the jupyter book

In these lines of the workflow the _toc.yml file for the jupyter book is generated on the fly. To control what enters in which order you should include an own _toc.yml file and omit this overwriting here.
https://github.com/materialdigital/PMD-workflow-workshop/blob/32f0282e92eed9f99cb679c1f31788ba914d2d6f/.github/workflows/book.yml#L27-L28

Great. Thank a lot, @niklassiemer. So I will replace the _toc.yml file as you mentioned.

@niklassiemer, after a few iteration, I found out (in the link below) that the order of the notebooks, in the navigation sidebar, is alphabetical. Then I gave up and renamed my notebooks.
https://jupyterbook.org/customize/toc.html#automatically-generate-your-toc-yml-file

@muh-hassani If you want control about the ordering, you have to write the toc yourself. E.g.
- file: README.md
- file: 1stNotebook.ipynb
- file: 2ndNotebook.ipynb

However, renaming notebooks to be in alphabetical order is also fine.


Rewrite Local Hub to Go

Description

Consider https://github.com/dosco/graphjin
Implement 1:1 features that we already support in Local Hub already
vMake Local Hub to use PostgreSQL (Install Bitnami PostgreSQL Helm chart)
Remember that in future we will extend it with multiple backends
Do not support upgrade and migration from 0.5.0
Extend TypeInstance GraphQL API with the TypeInstance.spec.backend field

Related issues
See epic #604 for reason and use cases.

Investigations showed that rewriting doesn't make sense at the current stage, for more info check #626


Support for GitHub markdown

Currently, ZenPen uses other than GitHub markdown when saving to local file.
I'd like to request a new feature - to add support for GitHub markdown.

:+1:


Why did the Tabla class get split into type families?

This seems to have changed in commit 630c6bd68ce88b7d741640e485b5758c7e160ae0: changed api a lot
One advantage of the class representation is that sensible defaults can be given for fields such as SchemaName.
A slightly related issue: #12

Yeah, that commit reorganized much stuff.
In practice, I don't think there's much difference between the standalone type families vs. the typeclass and associated types approach. I tried both, and the current one seemed a bit cleaner.
That thing you mention about things like SchemaName having a default is a minor but interesting point. I actually don't like the idea of providing a default here. With tisch, I'm trying to make it as hard as possible to shot yourself in the foot, and being explicit about things is a good way to achieve that. Granted, having a default schema name is not a big deal, but still I'd prefer people to understand where their tables are found so that they can better relate to the generated SQL, error messages, and such.

That's understandable regarding defaults.
One nice thing about doing this in a class is that there's one central place for the user to see what they need to define for their table to work.
If you say that it's cleaner this way I'm happy :)


Govee Light Strip turns on then changes brightness

What issue do you have? Please be as thorough and explicit as possible.
When an automation turns on my Govee light strip, it turns on first and then changes settings second, so if it's at night it might be very bright white at first before switching to it's dim red settings.
Details of your setup.

Do you use (1) Homebridge (+ config-ui), (2) Homebridge (CLI) or (3) HOOBS?
Homebridge (+ config-ui)

Which version of Homebridge/HOOBS do you have?
1.3.4

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.
os x 10.15 iMac
Node.js Version  v14.16.0
NPM Version v6.14.11

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?
v2.13.2

Which Govee devices do you have that are causing issues? Please include product models if applicable.
LED Light strip  - H6117-F867
Firmware 1.04.06

Please paste any relevant logs below.

 [37m[3/17/2021, 10:24:06 AM] [Govee] [v2.13.2] initialised. Syncing with Govee.
[3/17/2021, 10:24:06 AM] [eWeLink] [v5.5.0] initialised. Syncing with eWeLink.
[3/17/2021, 10:24:06 AM] [Govee] [H6117_F867] initialised with id 69:B3:A4:C1:38:8F:F8:67.
[3/17/2021, 10:24:06 AM] [Govee] ✓ Setup complete. Interested in sponsoring this plugin? https://github.com/sponsors/bwp91
...
 [37m[3/16/2021, 11:43:16 PM] [Bed Light Timer] Setting switch to true
[3/16/2021, 11:43:16 PM] [Govee] [H6117_F867] current state [on].
[3/16/2021, 11:43:17 PM] [Govee] [H6117_F867] current brightness [2%].

This behaviour will be 'fixed' in the next release of the plugin 👍


Stackdriver doesn't provide a sum, but it does provide a mean and a count.

By multiplying the mean * count we can get back to the sum.

Thanks @bytheway


FirebaseApp: Notifying background state change listeners.

Step 1: Platform details

Android device: Moto X play and Moto G2
Android OS version: 6.0.1 and 6.0
Google Play Services version: 9.8.77
Firebase/Play Services SDK version: 9.6.1

Step 2: Describe the problem:
I have a hybrid app on cordova and I am trying to implement push plugin with FCM. The only issue I am facing is when the app is in background then the push.on("notification") listener function is not getting called after clicking the push notification from the notification tray. Its only called on foreground. Also this issue is only for android. For iOS its working as expected.
I read that this can be achieved only when push notification are triggered via API. From backend, I am using python's pyfcm API to send the notification but same issue.
Also I checked the logs on Android studio. They just show this line "D/FirebaseApp: Notifying background state change listeners." whenever app goes in background and comes back in foreground.
Please let me know how can I call the notification listener when app is on background.
Steps to reproduce:

Install the app
Press home button so that app goes in background.
Send a push notification.
Click on the push notification from the notification tray

Observed Results:

The push.on("notification") listener function not getting called (I am using this cordova push plugin)

Expected Results:

The push.on("notification") listener function should have been called after clicking the notification.

Hi @kroikie,
Can you please help me on this. I am really stuck on this badly.
Thanks in advance!

@sunil-jhamnani from the description it sounds like this problem could be part of "pyfcm" or the cordova push plugin.  Neither of those is something written by Google/Firebase so it's going to be very hard for us to troubleshoot.
I would suggest posting this on StackOverflow or a forum specific to those libraries as it's not an issue with the Android quickstart code presented here.


Add Dev permission for escoem and MCardenas

Requesting dev permission for Emilio Escobar and Manuel Cardenas as commented with @oleg-nenashev.

@MCardenasBlanco To clarify, this grants permission to release to the Maven repo. GitHub commit permissions are separate.

LGTM :+1: waiting for @oleg-nenashev ack

Probably better if @jglick or @stephenc approved as Oleg is unresponsive.

I confirm there is an agreement to handover the ownership of the plugin. According to our discussion with @escoem and @MCardenasBlanco, the first steps for them will be to make several contributions to the plugin in order to study the Code base. This step does not actually require the release permission. I am fine with granting it, but IMHO it is not a blocker for the initial ramp-up

I am fine with granting it

There we go. Thanks @oleg-nenashev


#3114 backslash anywhere in a line is treated like a continuation charac...

...ter in properties mode

Thanks! Merged as 4485ae7


docs(readme) add go report and license badges, spelling GitHub

What this PR does / why we need it: added Go Report and license badges to README, spelling Github -> GitHub
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #
Special notes for your reviewer:

Codecov Report

Merging #175 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #175   +/-   ##
=======================================
  Coverage   15.31%   15.31%
=======================================
  Files          34       34
  Lines        2820     2820
=======================================
  Hits          432      432
  Misses       2350     2350
  Partials       38       38

Continue to review full report at Codecov.

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

@anatolyyyyyy While badges are good and positive for this repository, we would like to keep them to a minimum at this point. We're doing some heavy refactoring of the code and it's under constant flux under the hood. The metrics shown by Go report will probably not reflect correctly. Though, we will welcome this change at some point in future.


[wip] Rely on propagated findXMLCatalogs hook

Motivation for this change
We want to rely propagated findXMLCatalogs hook instead of manually specifying XML catalog paths all the time. Cherry-picked from #30457.
Things done
Needs to be tested.

[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
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

Looks good to me, can it be merged now (since it's still marked as [wip])?

I have not yet tested that the packages build. Will to need to do it one by one since otherwise it wants to rebuild everything.

Okay, I built all the packages successfully.
However, there is an issue that the propagatedNativeBuildInputs actually does not make the hook populate the environment variable.
https://github.com/NixOS/nixpkgs/blob/ef5a977a53453dceebc3879f481ea79cd1014a04/pkgs/data/sgml%2Bxml/schemas/xml-dtd/docbook/generic.nix#L7
https://github.com/NixOS/nixpkgs/blob/ef5a977a53453dceebc3879f481ea79cd1014a04/pkgs/build-support/setup-hooks/find-xml-catalogs.sh#L21
Should we change it to propagateBuildInputs like docbook-xsl does?
https://github.com/NixOS/nixpkgs/blob/ff5601a7d64a340f1e26f7e7a3e3f9a0c5ae2bbe/pkgs/data/sgml%2Bxml/stylesheets/xslt/docbook-xsl/default.nix#L15
--- a/pkgs/os-specific/linux/nftables/default.nix
+++ b/pkgs/os-specific/linux/nftables/default.nix
@@ -1,5 +1,5 @@
 { stdenv, fetchurl, pkgconfig, docbook2x, docbook_xml_dtd_45
-, flex, bison, libmnl, libnftnl, gmp, readline }:
+, flex, bison, libmnl, libnftnl, gmp, readline, findXMLCatalogs }:

 stdenv.mkDerivation rec {
   version = "0.9.0";
@@ -15,7 +15,11 @@
     "DB2MAN=docbook2man"
   ];

-  nativeBuildInputs = [ pkgconfig docbook2x docbook_xml_dtd_45 flex bison ];
+  postPatch = ''
+    echo "%%%%%%%%%%%%%%%%%%%" $XML_CATALOG_FILES
+  '';
+
+  nativeBuildInputs = [ pkgconfig docbook2x (docbook_xml_dtd_45.overrideAttrs (attrs: { propagatedBuildInputs = [findXMLCatalogs]; })) flex bison ];
   buildInputs = [ libmnl libnftnl gmp readline ];

   meta = with stdenv.lib; {


compiler hangs when an Interface and File name don't match

example:
# In Thing.roc
interface OtherThing
    exposes []
    imports []

This causes the compiler to hang and prints no output. I tried passing -- --nocapture and there also wasn't any output.
I imagine we probably want to give an error message to the user when this happens?

I'm closing this due to inactivity, but feel free to reopen it!


Extreme low-power mode on NRF5340

This is not so much an issues as a discussion, before we start implementation, since I couldn't find a forum for this.
We would like to completely disable Nimble and the net-core on the NRF5340 for long periods. When needed, the Nimble
stack (and Net-core) should be restarted and used for communications. Nimble itself doesn't appear to have deinit() functions (yet).
What we plan to do is:

Net-core: wait for Radio to be idle and then disable the Radio (and all other used peripherals). Then signal app-core
App-core: wait until net-core is done with shutdown and then really shut it down.
App-core Nimble stack: stop tasks, stop timer, remove queues (or clear), reset some static global structs to zero.

The idea is that we dont have to modify the init steps this way, so future merges remain easy.
Am I missing something with this approach?

Are any special configuration settings needed for this? I'm using the default Peripheral app for testing now, but it seems to use around 6.3 mA on avg (with energy 2 spikes per second).


chore: Silence Pydantic UserWarning

Silences backend pydantic warnings that were not useful
AI Description

This PR introduces a new import, warnings, to suppress UserWarnings clogging logs.

A new import, warnings, is added to the list of imports.
The warnings.filterwarnings("ignore", category=UserWarning, module="pydantic") line is added to suppress UserWarnings clogging logs.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 79.27%. Comparing base (8fd8cf1) to head (445ae78).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #846   +/-   ##
=======================================
  Coverage   79.27%   79.27%
=======================================
  Files         251      251
  Lines       10652    10654    +2
=======================================
+ Hits         8444     8446    +2
  Misses       2208     2208

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles


New Package: Peltoche/lsd/0.23.1

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

manifest v1.4 with zip

v1.4 with zip

Add 32-bit executable: https://github.com/Peltoche/lsd/releases/download/0.23.1/lsd-0.23.1-i686-pc-windows-msvc.zip

done~

Continued in #95485


double-beep: Watch BeckyaRobertson

double-beep requests the watch of the watch_keyword BeckyaRobertson. See the MS search here and the Stack Exchange search here.

BeckyaRobertson has been seen in 1 true positive, 0 false positives, and 0 NAAs.

I doubt that this is going to come back up again; we've only seen it once, and the medium user only has a single post. If we're likely to see another spam post from the same blog, the blog usually has several spam posts; but this one doesn't.

@angussidney the reason I don't request to watch also medium\.com (i.e. medium\.com/username) is that a few users have the same username in other spammy sites. Or even they have it in format user-name, so I usually do watch user\W*name.

If you are intending this to be a watch of other possible places that the person is using the same username, then you should use a regex that's more generic and would actually cover the other examples you provide (e.g. Beckya\W*Robertson would detect your other examples).
Personally, I'd prefer not to do that, unless we see more than one example of spam using an alternate representation (or different uses in the same spam), but I'm not dead-set against it. If you can show some examples where watching a more generic version of a medium.com username would have resulted in us detecting some spam which we otherwise would have missed, that would significantly change my opinion.
I'm going to close this, as I feel that it should either be more specific (i.e. detect only medium.com/@BeckyaRobertson), or more generic (i.e. detect the other possibilities you mentioned).


Week10 Project Assignment Feedback

It should be a constant variable, not a global variable
https://github.com/YYB-SOA/CafeMap/blob/47e59debac0689823171edb103577ffeb6bedc04/app/controllers/app.rb#L67

Please remove these commented out code
https://github.com/YYB-SOA/CafeMap/blob/47e59debac0689823171edb103577ffeb6bedc04/app/controllers/app.rb#L143

Please remove this useless file
https://github.com/YYB-SOA/CafeMap/blob/presentation/dev.db::InfoOrm

All fixed. Much appreciated!


Hello world project with two apps

Learning objectives
Implement a connection between a Ruby on Rails back-end and React front-end.
Understand pros and cons of different approaches of connecting Ruby on Rails back-end with React front-end.
Link to frontend:
https://github.com/eerapheal/frontends
Built with:

RonR
React/Redux
Cors

@Reem-lab Thanks for the comment but this is hello rails backend and react front end. Deployment of the project is required.

@Reem-lab checks is giving me issues for days now.

Hello @eerapheal if it is required then you can add the deployed link ✨✨🔥

@Reem-lab kindly point out for me where deployment is required.
[Project requirement]https://github.com/microverseinc/curriculum-rails/blob/main/connect-frontend-frameworks/hello_world_two_apps.md)

Hello @eerapheal i didn't say that it is required I said you should remove the live demo section since there is no deployed link or no requirements says that you should deploy it so just remove that section 🔥✨🙏🏻 if there is any issues please let me know

Hi @eerapheal
Can you remove this aspect from from your ReadMe asap!

Please, also do the same for the frontend!
Cheers!

@rloterh done. Thanks.

Oh one more ..let correct here too!

Please do the same correction for your forntend repo as well. Thanks 🙏

@eerapheal
Key Features in your ReadMe is still blank
Kindly add some features of your project under your Key Features section
I urge you to also ensure that the MIT license link is not broken
Cheers!


KP page - ask teams to add their KP information

This issue is to suggest that you (or Tursynay) send a request to each KP primary owner to populate this page with their KP's information: https://translator-developer-documentation.readthedocs.io/en/latest/architecture/kp/.

OK, thanks for the recommendation Kara.

@karafecho, after looking again at the given page, I note that it has links to the Git repositories. I get the sense visiting those Git repositories, that each team is documenting their KP (or ARA) there, locally, probably thoroughly enough. This may suffice for now. Maybe Chris B.'s opinion on this might help.

So, I see an incomplete list of Git repos? FWIW, Andy C. and I thought that we could point to the Translator wiki pages (see Exposures Providers entries for examples). We (Translator team members) are supposed to be keeping these pages up to date anyway. Thoughts?

A related issue #44 is created for follow up by the Biothings team with respect to the Service Provider KP wrapper.

So, I see an incomplete list of Git repos? FWIW, Andy C. and I thought that we could point to the Translator wiki pages (see Exposures Providers entries for examples). We (Translator team members) are supposed to be keeping these pages up to date anyway. Thoughts?

I did a little bit of work on this some weeks ago. I guess the KP teams need to pick up the ball from here.

I'm getting a 404 error when trying to access the link at the top of this issue. Assuming you are leveraging the wiki pages here, then yes, the KP teams should probably be responsible for keeping them up to date. Perhaps we should ping the contacts listed for each page, just to remind them?

Hi @karafecho and @RichardBruskiewich wouldn't it make sense to have such information about the Team tools and services in one place? Otherwise it will be too hard to update for the teams, will  duplicate the documentation effort, and be confusing for the readers ("where do I find how to query this specific Team? Was it the wiki or the dev doc or else?")
Imo it would make sense to migrate all the pages from the Translator-All/wiki to this website, so that all technical documentations on how to access the Translator infrastructure and its different components are available on this website, making it easier to find and update things
It would be easy and fast to move all wiki pages here, then we would just need to announce to all teams that the new place to update their tools/services info is this repository
If we want to add more detailed instructions on how to use a team service or tool, then those could be added either in the README of the tool itself, or in the Team page
What do you think?

I agree that this is a good idea, @vemonet . However, we'd need to receive approval from NCATS, the UI team, and the Biolink team, as: NCATS 'owns' the Translator wiki pages and requested that teams use these to describe (in a user-friendly manner) team composition/role and components (separately from teams, but perhaps cross-linked); the UI team is using the wiki URLs to provide users with information on primary knowledge sources to aid in edge interpretation; and the Biolink team is housing those URLs in the InfoRes Catalog, which is being used as ground truth for the UI team to find the appropriate URLs.
Note that the process I'm describing here has evolved quite a bit from the intent of my original post back in March, which likely (but unfortunately) may have introduced some confusion and lack of coordination across team. (Apologies!)
@sstemann @Genomewide @sierra-moxon : What do you think?

By 'this website' do we mean the UI?

If it is not about how to use the UI, but is about the details of using the rest of the Translator tools, then I think it could be confusing to have that on the current UI.  I would prefer not to have that.

I believe there are two issues here:

Whether the UI should include a link to the developer documentation. Andy and I suggest that we do not do that.
The second issue is whether the Translator wiki pages should be moved to the developer documentation. This is a decision that will need approval from NCATS, the UI team, and the Biolink team.

Hope this helps ...

In the world of basic science, links to the more technical aspects of a (bio)informatic resource would make sense, but this is not a typical basic science resource, so yes... no direct link to developer docs. Of course, as part of future sustainability and outreach of the project, NCATS should likely host a suitable landing page at their end that points interested technical parties to the details under the hood, including the tech docs, etc.

So, it sounds like folks agree to leave things as is for now, with NCATS hosting the wiki pages and the UI including links to scientific publications, blogs, etc, but NOT the developer documentation.
Closing this ticket and opening another one to suggest a solution for the developer documentation that I think will address the initial suggestion put forward by @vemonet without changing the way we are managing wiki pages, displaying content on the UI, etc.


More contrast for text colors

Didn't check with W3C guidelines, but just darkened some relevant ones a bit.

Have you tested this on all default themes?

Have you tested this on all default themes?

Good point. I now tested with the themes on the demo instance and noticed Morning and Zenburn need to be tweaked so they override the color in one place like so:
#chat .join .content,
#chat .kick .content,
#chat .mode .content,
#chat .nick .content,
#chat .part .content,
#chat .quit .content,
#chat .topic .content,
#chat .topic_set_by .content {
	color: #999;
}

Well, change them as you please. I would never use differing contrast to communicate a difference in a chat context, but that is a personal preference.

Closing this as author has no intent of changing it.


CRAYSAT-1626: Document workaround for sat bootsys bug

Description
Document a workaround for a sat bootsys bug that occurs when waiting for the hms-discovery Kubernetes cronjob to be scheduled.
Based on my testing with a reproducer script on shandy, it seems that the issue occurs with the first time waiting on the hms-discovery cronjob to be scheduled after it is resumed (suspend set to false). The last schedule time reported by K8s for the cronjob is unreliable during that period. Afterwards, it seems to fix itself, so it should be fine to just run the sat bootsys command again.
Checklist Before Merging

[x] If I added any command snippets, the steps they belong to follow the prompt conventions (see example).
[x] If I added a new directory, I also updated .github/CODEOWNERS with the corresponding team in Cray-HPE.
[x] My commits or Pull-Request Title contain my JIRA information, or I do not have a JIRA.

Looks good to me. FWIW for the spelling failure, I added "S-8031" to the .spelling file on main and release/1.3 in #2845 and #2838, but not on release/1.2 as I didn't backport the change there.

Just did the same here, thanks. I'm not sure why it is suddenly failing here. Perhaps the spell check was added after the last time this file was modified, or people are just ignoring that failed check when merging?


Correctly handle non-default binary name

qlever-control now works correctly even if the binaries don't have the default names ServerMain and IndexBuilderMain. This scenario might arise when packaging qlever, because the current binary names are not suitable for that. This PR is not quite finished yet, the string replacement on the cmdline_regex is still very hacky.
Fixes #101

Postponed until new names for the binaries (necessitated by packaging) are decided.